[Dapper] - XServer Crash on multi-boot

Bug #42801 reported by CrazyMenConnected
10
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This might seem odd but XServer Crashes every time i switch from windows on to ubunto (dapper drake flight 6).

I have a IMB Thinkpad R32 Type 2658 with 256MB Ram, with a toshiba 40GB disk.

I have dual boot on this machine because i have installed Windows XP Pro and Dapper Drake.

This is exactly what happens:
I turn on the computer;
GNU Grub 0.97 launches;
I Choose to run Windows;
Do whatever i like in windows;
Reboot the system from windows, i actually dont shutdown the computer i just restart;
GNU Grub 0.97 launches;
I Choose to run Dapper Drake Kernel 2.6.15-21-386;
The OS starts loading with the graphical boot;
When it's time to load X (i suppose), it simply crashes, freizes the computer. No login screen, noting... the screen black out.

The solution for me is to shut down the computer and start ubuntu directly from it. But im reporting this bug because in oter distribuitions os ubuntu this didn't happen in the same machine!

Well that's all, Thank you for you time!
And thanks for Ubuntu.

Revision history for this message
Angelo Lisco (angystardust-gmail) wrote :

Hi! I saw from here (http://thinkwiki.org/wiki/Category:R32) that the graphic card on your laptop is an ATI Mobility Radeon 7000...can you confirm this? Which driver are you using for it? In case you're using the ati driver, can you try booting in 'safe mode' and change the configuration of your X server in order to use the vesa driver?

Thanks

Revision history for this message
CrazyMenConnected (crazymenconnected) wrote :

Hello, and thanks for the quick reply.
The laptop realy uses the 16MB RADEON 7000 ATI Mobility chipset.
The /etc/X11/xorg.conf, the device section as the folowing lines:

Section "Device"
 Identifier "ATI Technologies, Inc. Radeon Mobility M6 LY [Radeon Mobility 9000]"
 Driver "ati"
 BusID "PCI:1:0:0"
EndSection

Might this be the problem?
The Identifier does not match the graphic card, and the driver is in fact the ati driver.

What do you recomend?
Thank you for your time!

Revision history for this message
Angelo Lisco (angystardust-gmail) wrote :

Sorry for my late reply...can you try to change the "Device" section in your xorg.conf this way?

Section "Device"
 Identifier "ATI Technologies, Inc. Radeon Mobility M6 LY [Radeon Mobility 9000]"
 Driver "vesa"
 BusID "PCI:1:0:0"
EndSection

Can you reproduce the bug with this configuration?

Revision history for this message
CrazyMenConnected (crazymenconnected) wrote :

I've changed the configuration like you recommended and i cannot reproduce de bug anymore.
I have not even noticed any changes on X server, gnome, etc...
Probably all it was was just a faulty driver.
Thank you very mutch for you help.
If you need something else, feel free to contact me!

Revision history for this message
Angelo Lisco (angystardust-gmail) wrote :

So the problem seems to be caused by the ati driver...i will subscribe the X-SWAT team so they will help us to find a real fix and not a workaround like the one I gave you.

By the way, I'm really happy to help you...

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

CrazyMenConnected:

can you reproduce this bug using 7.10beta or newer, using radeon driver (not vesa)?

Changed in xserver-xorg-video-ati:
status: Confirmed → Incomplete
Revision history for this message
CrazyMenConnected (crazymenconnected) wrote :

I have not tried it yet.
I was on vacation i did not had time to install 7.10.
Later on tonight i will install and then ill report back here.

Thx

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

No reply, closing the bug. Reopen if you still have problems with 7.10 or Hardy.

Changed in xserver-xorg-video-ati:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.