[SOLVED] Boot Up into gdm failing.

Ben9250 · 2010-08-05 08:40:05

Yesterday I updated and it included kernel26 and kernel26-headers. Which I think is the issue, but when I try to boot into Arch this morning, at startup I saw a message saying error loading wl when it goes through the list of operations saying [done] after each one. Then it fails to boot into gdm and tells me theres errors loading NVIDIA modules. I can't use startx manually either, I just get the same errors. I'm guessing it's going to be a visit to the cache, which thankfully I didn't ever delete. Unless anybody else knows what's going on and knows how to solve this.
Cheers.

Last edited by Ben9250 (2010-08-05 13:27:31)

karol · 2010-08-05 08:43:09

Try to run 'nvidia-xconfig' and 'startx' after that.
Post all the relevant logs, let's see what's going on.
What kernel version are you running?

Ben9250 · 2010-08-05 09:56:22

Ok here's the files. I put them on wgetpaste:

kernel.log: http://pastebin.com/t0jkxzpQ
.xinitrc : http://pastebin.com/TvSkJMXC
xorg.conf: http://pastebin.com/8kp91iWv
xorg.0.log: http://pastebin.com/nae4wCzF

I think these are all the necessary ones.

karol · 2010-08-05 10:25:00

Are you running nvidia or nouveau drivers?
Did you update the drivers too?

Aug  3 20:12:45 ben-laptop kernel: NVRM: API mismatch: the client has the version 256.44, but
Aug  3 20:12:45 ben-laptop kernel: NVRM: this kernel module has the version 256.35.  Please
Aug  3 20:12:45 ben-laptop kernel: NVRM: make sure that this kernel module and all NVIDIA driver
Aug  3 20:12:45 ben-laptop kernel: NVRM: components have the same version.

Last edited by karol (2010-08-05 10:27:48)

Ben9250 · 2010-08-05 10:48:10

As far as I'm aware I am running nvidia drivers. And there was an update to them a few days ago on the 2010-08-03, for version 256.44-2. And there have been several kernel26 and headers updates since then as I understand it, it was moved into core on 2010-08-04. I can try and plug the thing into the wired connection on the router and try do a pacman of nvidia again, but why it would have done this in the first place is a mystery to me.

karol · 2010-08-05 11:00:35

Aug  1 23:49:06 ben-laptop kernel: nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Aug  1 23:49:06 ben-laptop kernel: nouveau 0000:01:00.0: setting latency timer to 64
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Detected an NV50 generation card (0x086700a2)
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN
Aug  1 23:49:06 ben-laptop kernel: b43-phy0: Broadcom 4321 WLAN found (core revision 12)
Aug  1 23:49:06 ben-laptop kernel: b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 5, Type 4, Revision 2)
Aug  1 23:49:06 ben-laptop kernel: b43: probe of ssb0:0 failed with error -95
Aug  1 23:49:06 ben-laptop kernel: Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ]
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: ... appears to be valid
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: BIT BIOS found
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Bios version 60.86.51.00
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: TMDS table revision 2.0 not currently supported
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Found Display Configuration Block version 4.0
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Raw DCB entry 0: 01000323 00010034
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Raw DCB entry 1: 02012300 00000028
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Raw DCB entry 2: 02021312 00020010
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Raw DCB entry 3: 010333f1 00c0c080
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Raw DCB entry 4: 0000000e 00000000
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: DCB connector table: VHER 0x40 5 14 2
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0:   0: 0x00000040: type 0x40 idx 0 tag 0xff
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0:   1: 0x00001161: type 0x61 idx 1 tag 0x07
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0:   2: 0x00000200: type 0x00 idx 2 tag 0xff
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0:   3: 0x00000310: type 0x10 idx 3 tag 0xff
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0:   4: 0x00000311: type 0x11 idx 4 tag 0xff
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0:   5: 0x00000313: type 0x13 idx 5 tag 0xff
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0xC6D1
Aug  1 23:49:06 ben-laptop kernel: Linux video capture interface: v2.00
Aug  1 23:49:06 ben-laptop kernel: [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0xCA48
Aug  1 23:49:06 ben-laptop kernel: uvcvideo: Found UVC 1.00 device Laptop Integrated Webcam (05a9:2640)
Aug  1 23:49:06 ben-laptop kernel: uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.
Aug  1 23:49:06 ben-laptop kernel: input: Laptop Integrated Webcam as /devices/pci0000:00/0000:00:1a.7/usb1/1-1/1-1:1.0/input/input13
Aug  1 23:49:06 ben-laptop kernel: usbcore: registered new interface driver uvcvideo
Aug  1 23:49:06 ben-laptop kernel: USB Video Class driver (v0.1.0)
Aug  1 23:49:06 ben-laptop kernel: [drm]

I'm not an expert, but there's a lot of info about nouveau in the kernel log for someone not using nouveau-drm package.

Ben9250 · 2010-08-05 12:07:43

I've just tried various commands to get it to display information about nouveau using pacman -Qi to see if I have it installed. I never explicitly installed it. And pacman didn't return anything. When I first followed the beginners guide I only installed nvidia. Interestingly, wl also isnt working, and when I try to manually load them with modprobe it says they don't exist on my machine. Even though everything was fine yesterday. Doing a search of the drive partitions though, there are folders and things for nouveau. My guess is something to do with new kernel updates or nvidia updates because I've followed the beginners guide to the letter and haven't had any trouble up to now. I read a website that said nouveau was included in the kernel 2.6.33 (http://www.phoronix.com/scan.php?page=n … &px=Nzc5NQ) now but I don't think that applies to the updates the other day as it's still kernel 2.6.32.17-2.

Ben9250 · 2010-08-05 13:26:56

SOLVED! I managed to reconnect to a wired connection and reinstalled nvidia and the broadcom-wl modules and drivers. Although the mystery of the nouveau messages is still not solved... I'm assuming perhaps they are there as a result of other things I've installed that were necessary.

karol · 2010-08-05 13:33:11

Ben9250 wrote:

SOLVED! I managed to reconnect to a wired connection and reinstalled nvidia and the broadcom-wl modules and drivers. Although the mystery of the nouveau messages is still not solved... I'm assuming perhaps they are there as a result of other things I've installed that were necessary.

I've found nouveau-firmware on one of my systems yesterday although I thought I've removed it along with other things nouveau. I did install it, but I forgot to remove it when I switched to nvidia drivers. It didn't cause any problems.

Glad you got it working.

Arch Linux

#1 2010-08-05 08:40:05

[SOLVED] Boot Up into gdm failing.

#2 2010-08-05 08:43:09

Re: [SOLVED] Boot Up into gdm failing.

#3 2010-08-05 09:56:22

Re: [SOLVED] Boot Up into gdm failing.

#4 2010-08-05 10:25:00

Re: [SOLVED] Boot Up into gdm failing.

#5 2010-08-05 10:48:10

Re: [SOLVED] Boot Up into gdm failing.

#6 2010-08-05 11:00:35

Re: [SOLVED] Boot Up into gdm failing.

#7 2010-08-05 12:07:43

Re: [SOLVED] Boot Up into gdm failing.

#8 2010-08-05 13:26:56

Re: [SOLVED] Boot Up into gdm failing.

#9 2010-08-05 13:33:11

Re: [SOLVED] Boot Up into gdm failing.

Board footer