Latest Trimslice update fails to boot

[bmentink]

HI Guys,

Did a "pacman -Syu" and I am finding that gdm/X will not start, it tries to come up (blue login screen) then fails ..
I am getting these errors in the serial console ..

NvRmPrivGetChipIdStub: Could not read Tegra chip id/rev
Expected on kernels without Tegra3 support, using Tegra2
[ 447.515550] vgaarb: this pci device is not a vga device
[ 447.592746] HDMI out enable: 1920x1080 (pclk=148500000)
[ 451.933364] vgaarb: this pci device is not a vga device
[ 452.123899] vgaarb: this pci device is not a vga device
NvRmPrivGetChipIdStub: Could not read Tegra chip id/rev

Anyone have any ideas? I noticed that nvidia-trimslice was updated, did it by chance now support hardware accellerated graphics?

PS: I havn't updated this box for 2 years ..


Thanks

[WarheadsSE]

1- Wow, old.
2- So it's not failing to boot, it is failing to launch X?

[bmentink]

Yep, when it launches GDM it dies and then starts again in a cycle, so I see the errors listed above repeated ..

I tried logging in in the serial console and killing gdm, but I still get the printout so it makes using the console impossible to try and see what is going on.

I might have to boot with the SD card, disable the SSD /etc/initab file from booting X on startup so I can use the console.

ANy ideas' on the errors? Is the graphics driver broke?

[bmentink]

I am having corrupt filesystem issues on the SSD X was failing because it could not write the xorg.0.log file ..... so

Decided to re-install on the SSD drive from scratch .. so followed the install instructions and tried a re-boot, I got this far:

Scanning ext2 usb 0 on prefix /boot/ ...
Loading file "/boot/boot.scr" from usb device 0:1 (usbda1)
331 bytes read
boot.scr found! Executing ...
## Executing script at 00408000
" from usb device 0:1 (usbda1)
** File not found /boot/uImage
bootm - boot application image from memory

I definitely have a uImage file in /boot of the SSD partition so what gives? ....
I presume ext2load can load from an ext3 partition .. anyway it read the boot.scr file

Cheers,
B

[bmentink]

Anyone?

[pepedog]

I think it's the contents of yourn boot.scr file. I will dig one out for you