Ubuntu

GDM Crashes on Login on Thinkpad R60

Bug #135861 reported by cullen
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

The system is a IBM Lenovo Thinkpad R60 with nvidia video.

1. After boot the normal GDM login appears.
2. Enter username, password, login continues nomally, with the mouse cursor 'spinner' spinning for a few seconds,
3. then GDM restarts, as if I had pressed ctrl-alt-BS
4. repeat until tired
5. Notice that the Boot messages screen has stopped at "Preparing Thinkpad for use."
6. modprobe -r thinkpad_acpi
7. Login with Gnome Failsafe session
8. use Thinkpad Fn-Lock key
9. GDM restarts in the same manner as before
10. apt-get remove thinkpad_base
11. Reboot
12. Everything is back to normal (except w/o thinkpad_base)
13. Installing updates with 'Update Manager'

This laptop was fine Prior to Tuesday Aug 27, 2007 Having been runnung Gutsy for a few weeks. Will try re-installing thinkpad_base after the updates finish installing.

Some info, maybe helpful

uname -a
Linux lenny 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 GNU/Linux
lspci
00:00.0 Host bridge: Intel Corporation Mobile Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PCI Express Root Port (rev 0c)
00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation Mobile LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation Mobile IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Mobile SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0429 (rev a1)
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 (rev 04)

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the information requested at [WWW] https://help.ubuntu.com/community/DebuggingXAutoconfiguration as separate attachments.

Revision history for this message
cullen (cullen+ubuntu) wrote :

cullen@lenny:~$ sudo discover --disable=parallel,serial,usb,ide,scsi,pcmcia --format="%M\t%S\t%D\t%i\n" video
discover: Bus not found.
// Those "\n" below did not actually appear, but approx. that many real newlines did.
cullen@lenny:~$ sudo xresprobe nvidia
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
id:
res:
freq:
disptype: lcd/lvds
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$
cullen@lenny:~$

Revision history for this message
cullen (cullen+ubuntu) wrote :

Ye olde xorg.conf file

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

cullen:
I'm using a T60 with the Intel chipset here and I am not seeing this particular issue. Just for the record, does switching the driver from nvidia to nv in your xorg.conf help (if it does that narrows things down)?

Your Xorg.0.log says that the card couldn't do "1920x1440". What native resolution is your screen? Your drivers are also on the 100 series - is it possible you recently did an update that changed your from 97xx drivers to the 100 series ones?

(for anyone reading the card being used by the reporter is a Quadro NVS 140M (G86GL))

Revision history for this message
cullen (cullen+ubuntu) wrote :

root@lenny:/home/cullen# ddcprobe
vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: G86 Board - NV_NB8M Chip Rev
memory: 14336kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
edid:
edidfail

Revision history for this message
cullen (cullen+ubuntu) wrote :

Actually, none of that stuff from ddcprobe looks right to me. This is a 1440x900 screen. -Cullen

Revision history for this message
cullen (cullen+ubuntu) wrote :

Stefan : is it possible you recently did an update that changed your from 97xx drivers to the 100 series ones?

yes, I have compiled this driver with the nvidia tools. Before this, X would not start at all. Now X can be started manually, but something seemed to be happening with GDM as I logged in.

The most recent updates finally finished installing, and the system seems much better now.

Revision history for this message
cullen (cullen+ubuntu) wrote :

Another thing that I keep having to do is remove configuration for the wacom (that I assume is in the X series) from the xorg.conf file. This wacom config gets included if I use dpkg-reconfigure -phigh xserver-xorg. There is no wacom in the R Series. I am not confident that the wacom config is the cause though, I simply removed it since I knew it wasn't needed. -Cullen

Revision history for this message
cullen (cullen+ubuntu) wrote :

for everyone's viewing pleasure...

Revision history for this message
cullen (cullen+ubuntu) wrote :

Well,

     who knows? All seems to work fine now. Sorry for all the hub-bub.

Cullen

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

I'd be surprised if the wacom lines had any impact. They're not need unless you have the hardware but to the best of my knowledge they are absolutely harmless.

The moment you switched to the manually installed NVIDIA drivers your support options changed. See https://help.ubuntu.com/community/NvidiaManual for more information. My guess regarding your earlier problems is that your xorg.conf has the following within it:
        Modes "1920x1440"
If you didn't have a screen actually capable of doing that then problems would ensue.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Cullen:
That's alright. I suspect you might have been better off filing a support request over on http://answers.launchpad.net/ as you had manually installed drivers - you may have gotten a faster response. Additionally in the past week the NVIDIA drivers were updated to the 100 series (see Bug #120943 ) which may or may not make your life easier in the future.

If the issue has disappeared I would recommend going to the top of this bug page in launchpad, clicking on Status and changing it to invalid.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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