SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If the 2.6.35.10 kernel is broken with the Radeon, I sure hope that the next release of Slackware is delayed until it's fixed. Since the compiler has just been upgraded, why not switch to a more reliable kernel, like 2.6.38 ... Why? I need my Hauppauge remote to work and major new parts of the open source Radeon driver will be included. Personally, I can wait another month or two for a new Slackware release. I actually want a release which works in all respects ... I don't blame Pat and his team, but I AM growing a bit tired of dealing with incomplete and broken kernels... In the meantime, I'll just stick with 2.6.35.7 ....
Of course, it could just be an issue with 2.6.35.10 + HD4850 + my particular motherboard. I'd be interested in knowing if others are having the same problem.
Of course, it could just be an issue with 2.6.35.10 + HD4850 + my particular motherboard. I'd be interested in knowing if others are having the same problem.
Adam
Since I have an HD2600, I'm tempted to take a chance... Understand, though, that the current Catalyst 10.12 driver doesn't work with the current release of SDLMESS * so if the Radeon driver is broken when I upgrade the kernel to 2.6.35.10, I'm between a rock and a hard spot.... I think I'll wait until ATI/AMD releases a new Catalyst driver (should be less than two weeks) and test it with SDLMESS before upgrading to 2.6.35.10 ...
ATI HD4200 motherboard here and I'm not getting those lines in dmesg. The radeon and drm modules are loaded but I have no access to KDE dektop effects at all. It's been like that for a while on -current. I do notice a Xorg.0.log entry calling out libdrm-2.6.0 or newer required. Maybe I'll give that a spin.
Quote:
[ 34.849] (II) VESA: driver for VESA chipsets: vesa
[ 34.849] (++) using VT number 7
[ 34.859] (II) [KMS] Kernel modesetting enabled.
[ 34.859] (WW) Falling back to old probe method for vesa
[ 34.860] (II) RADEON(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 34.860] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
[ 34.860] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 34.860] (==) RADEON(0): Default visual is TrueColor
[ 34.860] (==) RADEON(0): RGB weight 888
[ 34.860] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
[ 34.860] (--) RADEON(0): Chipset: "ATI Radeon HD 4200" (ChipID = 0x9710)
[ 34.860] (II) RADEON(0): PCI card detected
[ 34.860] drmOpenDevice: node name is /dev/dri/card0
[ 34.860] drmOpenDevice: open result is 9, (OK)
[ 34.860] drmOpenByBusid: Searching for BusID pci:0000:01:05.0
[ 34.860] drmOpenDevice: node name is /dev/dri/card0
[ 34.860] drmOpenDevice: open result is 9, (OK)
[ 34.860] drmOpenByBusid: drmOpenMinor returns 9
[ 34.860] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[ 34.860] drmOpenByBusid: drmGetBusid reports pci:0000:01:05.0
[ 34.860] (II) RADEON(0): R6xx+ KMS Color Tiling requires radeon drm 2.6.0 or newer
[ 34.860] (II) RADEON(0): KMS Color Tiling: disabled
[ 34.888] (II) RADEON(0): Output VGA-0 has no monitor section
[ 34.942] (II) RADEON(0): Output DVI-0 has no monitor section
[ 34.956] (II) RADEON(0): EDID for output VGA-0
[ 35.010] (II) RADEON(0): EDID for output DVI-0
Of course, it could just be an issue with 2.6.35.10 + HD4850 + my particular motherboard. I'd be interested in knowing if others are having the same problem.
Same problem here with HD4350.
Downgrading kernel back to 2.6.35.7 helped.
Of course, it could just be an issue with 2.6.35.10 + HD4850 + my particular motherboard. I'd be interested in knowing if others are having the same problem.
Adam
Same here with an hd3470. Was fine in 2.6.35.7 - not so in 2.6.35.10. Built 2.6.37, radeon works for anything 2d. 3d is a mess, maybe I'll look into upgrading libdrm.
My x1600 agp runs acceptably on 2.6.35.7. Braid, Aquaria, WoP ...
Yes 2.6.35.10 is broken with radeon. Bug reports abound all over the place. Sadly this was fixed in both 2.6.36 and 2.6.37, but never back ported to the long term supported kernel. Maybe in .11.
I've attached the patch from Fedora that fixes this. https://bugzilla.redhat.com/show_bug.cgi?id=664206 IMO, considering you would have to patch .10, and recompile, it might be worth while to just use a working kernel (2.6.35.7), or upgrade and compile a newer non 2.6.35.x series kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Why? I need my Hauppauge remote to work and major new parts of the open source Radeon driver will be included. Personally, I can wait another month or two for a new Slackware release. I actually want a release which works in all respects ... I don't blame Pat and his team, but I AM growing a bit tired of dealing with incomplete and broken kernels... In the meantime, I'll just stick with 2.6.35.7 ....
