[SOLVED] Radeon Xpress 200 problem on Debian squeeze (kernel 2.6.30)
DebianThis forum is for the discussion of Debian 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.
Radeon Xpress 200 problem on Debian squeeze (kernel 2.6.30)
Hya,
Problem is: After dist-upgrade a few days ago, X refuses to kick in.
Xorg.0.log reads
Code:
(II) Loading extension DRI2
(II) LoadModule: "fglrx"
(WW) Warning, couldn't open module fglrx
(II) UnloadModule: "fglrx"
(EE) Failed to load module "fglrx" (module does not exist, 0)
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.1.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(EE) No drivers available.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
lshw reads that Xpress 200M is claimed by radeonfb driver.
Install the fglrx-driver package, and take a look at your Xorg.conf to make sure there isn't a silly "Use a driver I don't actually want to use." type directive. Or download the fglrx and build your own module for the (whichever) kernel you're now using.
Basically though, I suspect you've fallen into this sequence of events:
* build/install fglrx from native binary package on ATi site.
* upgrade kernel to something the fglrx module wasn't built for
* have a bad time.
I recompiled kernel and reinstalled all modules, furthermore all xorg packages were reinstalled.
Things don't go well...
dmesg says
Code:
radeonfb 0000:01:05.0: power state changed by ACPI to D0
radeonfb 0000:01:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
radeonfb: Retrieved PLL infos from BIOS
radeonfb: Reference=14.32 MHz (RefDiv=6) Memory=300.00 Mhz, System=266.00 MHz
radeonfb: PLL min 20000 max 40000
Non-DDC laptop panel detected
i2c-adapter i2c-2: unable to read EDID block.
i2c-adapter i2c-2: unable to read EDID block.
i2c-adapter i2c-2: unable to read EDID block.
radeonfb: Monitor 1 type LCD found
radeonfb: Monitor 2 type no found
radeonfb: panel ID string: LPL
radeonfb: detected LVDS panel size from BIOS: 1280x800
radeondb: BIOS provided dividers will be used
radeonfb: Dynamic Clock Power Management enabled
Console: switching to colour frame buffer device 160x50
radeonfb (0000:01:05.0): ATI Radeon 5a62 "Zb"
ACPI: EC: non-query interrupt received, switching to interrupt mode
ACPI: AC Adapter [ACAD] (on-line)
Marking TSC unstable due to TSC halts in idle
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
processor ACPI_CPU:00: registered as cooling_device0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux agpgart interface v0.103
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized radeon 1.30.0 20080528 for 0000:01:05.0 on minor 0
and again lshw says that display is claimed by radeonfb. X log is same.
* statically specifying the devide id in Xorg.conf.
* blacklist the offending readonfb module in /etd/modprobe.d/blacklist
* make sure fglrx is mentioned in Xorg.conf.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
The RadeonFB driver in the kernel interferes with ATI's driver. It's the same thing with nVidia's fb driver. I think you need to uncheck the RadeonFB option in the kernel config. But here's what you can do:
CTRL+ALT+F1 to a terminal, and run:
bash@debian # X -configure
That will place a new:
xorg.conf.new
file in the home directory of whatever user you are logged in as. Then try:
While I was playing around with i2c, (hardware sensor related), X windows got unstable. (Exactly same setting, sometimes works, sometimes does not work at all. When it does not work, even killing X does not restore screen.)
So, make sure that i2c is set up, so that SMbus works correct. (I have not studied in detail.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.