Bug 28846

Summary:	error setting MTRR (base = 0xe0000000, size = 0x10000000, type = 1) Inappropriate ioctl for device (25)
Product:	xorg	Reporter:	MM <44146ca1>
Component:	Driver/Radeon	Assignee:	xf86-video-ati maintainers <xorg-driver-ati>
Status:	RESOLVED INVALID	QA Contact:	Xorg Project Team <xorg-team>
Severity:	major
Priority:	medium
Version:	7.5 (2009.10)
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description MM 2010-06-30 05:39:20 UTC

I'm running Slackware 13.1 x86 which actually Xorg is somewhere between 7.5 and 7.6.

My video chip on a laptop I'm running is a ATI HD3200

On Slackware 13.1 these are the versions of the ATI and Radeon drivers I'm using:

xf86-video-ati-6.13.0
xf86-video-radeonhd-1.3.0

On Slackware I only use OpenBox and when I log out of OpenBox into the console I get this message:

error setting MTRR (base = 0xe0000000, size = 0x10000000, type = 1) Inappropriate ioctl for device (25)

If I use the ati proprietary driver I do not see this message, I only get this message running the X drivers, this has led me to believe this is a bug relating to the X drivers for my HD3200 so I'm filing a bug report.

Thank you.

Comment 1 MM 2010-07-15 18:59:03 UTC

Has anyone looked at this bug report yet?

Is there anything I can do to fix this?


THANKS

Comment 2 Alex Deucher 2010-07-16 08:28:04 UTC

If it's working fine, I wouldn't worry about it.  Are you using kms?  I suspect the xserver is trying to setup an mtrr for the framebuffer but kms already handles that.

Comment 3 MM 2010-07-16 20:14:57 UTC

Actually I wasn't using KMS, now I compiled it in and the firmware R600_rlc.bin I found here:

http://people.freedesktop.org/~agd5f/radeon_ucode/

Then compiled both of those into the kernel.

Now when I start Slack in dmesg I get this message:

[drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD)

Sheesh from one thing to the next.

Any thoughts on this now?


THANKS

Comment 4 Alex Deucher 2010-07-17 09:03:00 UTC

Please attach your dmesg and xorg log.  Also what kernel are you using?

Comment 5 MM 2010-07-18 15:26:49 UTC

Forget my last reply, I got Radeon KMS working good in Slackware 13.1, no error messages in the logs.

The only thing I'd like to see happen next with Radeon KMS is that as soon as the Kernel boots you go straight into the FB mode and you don't see text at first booting at like 640x480, which is my case.

Since I'm running Slackware there is no splash screen and as soon as the kernel loads I get text in 640x480 for like 2 seconds showing about 10 lines and then into the FB mode.

2 seconds is quick but it looks sloppy, I'd love it if as soon as the kernel boots I'm presented with the Tux boot logo and the FB text.

If anyone might be able to shed some light on possibly getting it to boot right away into the FB mode I'd appreciate it, in the meantime I'm filing this as another bug.


THANKS

Comment 6 Adam Jackson 2018-06-12 19:06:39 UTC

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.