LinuxQuestions.org - [SOLVED] Radeon Xpress 200 problem on Debian squeeze (kernel 2.6.30)

- Debian (https://www.linuxquestions.org/questions/debian-26/)

- - Radeon Xpress 200 problem on Debian squeeze (kernel 2.6.30) (https://www.linuxquestions.org/questions/debian-26/radeon-xpress-200-problem-on-debian-squeeze-kernel-2-6-30-a-756271/)

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.

At this moment, no fglrx packages are installed.

System is Toshiba laptop.

I do not think ATI dropped support, however, even without fglrx, nothing works.

Any information will be appreciated.

Happy Penguins!

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.

Hya,

Thanks, but...

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.

I am not sure if EDID message is related.

Any suggestions will be appreciated.

Happy Penguins!

Perhaps try:

* 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.

can you insmod fglrx.ko?

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:

bash@debian # X -configure ~/xorg.conf.new

If you get a textured background, the new:

xorg.conf.new

file works. Then:

bash@debian # sudo cp ~/xorg.conf.new /etc/X11/xorg.conf

But if you do that, you'll blow away your original:

/etc/X11/xorg.conf

You might be sorry if you don't back up the existing:

/etc/X11/xorg.conf

to:

/etc/X11/xorg.conf.bak

bash@debian # sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

If you are sure that your card is still supported by fglrx, you will need fglrx 9.9 to make it work with 2.6.30.

I would go with radeon though and remove fglrx. I think your card is fairly old to be supported by it.

Hya,

Thanks, AwesomeMachine.

My penguin made one step ahead with your suggestion. (X -configure, X -config /where/ever/xorg.conf.new)
However, mouse was dead, so was keyboard.

Log says that AllowEmptyInput is on, so they are disabled.

I added

Code:

        Option "AutoAddDevices" "False"

        Option "AllowEmptyInput" "False"

to Xorg.conf suggested by this post.

Now my penguin looks happy with X.

Drivers by ATI do not compile with 2.6.30. fglrx source by Debian does not either.

Happy Penguins!

Hya.

Follow up (?) maybe not.

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.)

Happy Penguins!