linux-headers 2.6.22-14

[Frem]

I'm having problems similar to WenSes. Intel Pentium M 1.6 GHz, ATi Xpress 200m.

I got on IRC and asked for help, and everyone kept telling me "you need to RECOMPILE your DRIVERS. you need to USE GENERIC DRIVERS." (One chap in particular persisted in using that capitalization.) This was extremely frustrating as I didn't compile them to start with and I was using the generic drivers, and noone could accept this.

If I boot into single user mode using the second opion on grub and run "startx", I get X. I can run it using the fglrx, ati, and vesa drivers in xorg.conf
If I boot normally, the entire system jams up when the login screen should start, no matter what graphics driver I use.

Both modes are using the same kernel. Any ideas on how to fix this?

edit: I should probably mention that I've already run "sudo dpkg-reconfigure xserver-xorg", and it didn't make any differance.

[Castaa]

Originally Posted by Frem I'm having problems similar to WenSes. Intel Pentium M 1.6 GHz, ATi Xpress 200m. I got on IRC and asked for help, and everyone kept telling me "you need to RECOMPILE your DRIVERS. you need to USE GENERIC DRIVERS." (One chap in particular persisted in using that capitalization.) This was extremely frustrating as I didn't compile them to start with and I was using the generic drivers, and noone could accept this. If I boot into single user mode using the second opion on grub and run "startx", I get X. I can run it using the fglrx, ati, and vesa drivers in xorg.conf If I boot normally, the entire system jams up when the login screen should start, no matter what graphics driver I use. Both modes are using the same kernel. Any ideas on how to fix this? edit: I should probably mention that I've already run "sudo dpkg-reconfigure xserver-xorg", and it didn't make any differance.

I'm in a same boat as you. I upgrade. I've been using the standard nvidia video driver. I ran sudo dpkg-reconfigure xserver-xorg and reconfigured. The nvidia driver simply does not appear to work for me. I'm not sure what my differences are. I did find that the nv driver at least gives me a non-accelerated video support at resolutions beyond 800x600 that VESA gave me. But I'm still far from where I was before the update. The nvidia driver just crashes the moment I try to test it if the config menu in Gnome.

[confused57]

Originally Posted by Castaa I'm in a same boat as you. I upgrade. I've been using the standard nvidia video driver. I ran sudo dpkg-reconfigure xserver-xorg and reconfigured. The nvidia driver simply does not appear to work for me. I'm not sure what my differences are. I did find that the nv driver at least gives me a non-accelerated video support at resolutions beyond 800x600 that VESA gave me. But I'm still far from where I was before the update. The nvidia driver just crashes the moment I try to test it if the config menu in Gnome.

It's a longshot, but try reinstalling your linux-restricted modules in Synaptic Package Manager...type "linux-restricted" in the SPM Search bar, reinstall Restricted linux modules for generic kernels.

[mtngun]

The header update seriously screwed up my PC.

I've tried most of the suggestions and a few other things.

I can no longer boot into Windows XP, but Ubuntu will boot -- usually, not always.

However, Ubuntu doesn't run right. For example, Wine won't run at all. I uninstalled and then reinstalled Wine but it didn't help. Attempting to start Wine will lock up the PC. Wine was running fine before the header update.

A few files seem to be corrupted on both partitions. While attempting to backup my personal files today, I kept getting hangs, seemingly due to trouble reading or writing files. It acts like a dying hard drive -- except everything was fine prior to the update. I suspect the update scrambled the hard drive.

Perhaps there is a simple fix, but come tomorrow I'll be looking at reformatting and reinstalling. I've already lost most of day's work because of this blasted update.

[Frem]

So, yeah. With the VESA drivers, I can make Ubuntu jump back and forth rapidly between command line and failed X session. Work for about 2 minutes before freezing during which rapid typing revealed no errors in the X logs in /var/log/. Not entirely sure what to do about it, something keeps trying to restart the X server.

Is there any way to disable the stupid "bulletproof X" feature that Gutsy introduced? I need to have X not restart as soon as an error message comes up because I need to read the error!

Alternatively, is there a way to rollback to linux-image-2.6.22-13-generic?

[frodon]

Everyone here you should really fill bug reports otherwise developers might not be aware of your multiple problems :
https://bugs.launchpad.net/ubuntu/+filebug

[Handssolow]

Little progress to report and I'm still mystified.
This morning I couldn't boot either from my Sata's 64 bit or IDE's 32bit getting grub error18 and 21 respectively. So I removed the IDE drive to work just on the Sata which I moved from a Sata2 socket to a Sata1 and after a few changes to the bios eventually getting 64bit 2.6.22-14-generic fired up after a few reboots and xserver configurations. I also ran "sudo grub-install /dev/hda --recheck" to remove references to my IDE drive to keep things separate.

Next working with only the IDE's 32bit in the machine, I used Supergrub on a CD to repair Grub and I'm back to where I was yesterday, able to boot with kernel 2.6.20-16-generic but 2.6.22.14-generic drops me as before to Busybox's line about initramfs.

Is there an issue about the 2.6.22-14 kernel affecting dual boot setups? Also just suppose I had an intermittent fault with my Sata drive (as slave) or even removed it, would these events cause my system to hang when attempting to boot from my IDE's 32bit OS? Is the OS looking for a missing slave drive?

I reinstalled the new headers and restricted modules - yet again and it made no difference.

Help and advice will be much appreciated.

(I'll have to look around for my Launchpad password)

[Tosa]

Originally Posted by frodon @Tosa, alsa-base should be 1.0.14 in gutsy, did you compiled alsa or locked any alsa package. Check what alsa-base version you have installed.

Thanks for answering frodon.

Yes, when I check in Adept it says alsa-base is 1.0.14... And no, I haven't compiled nor blocked anything (I'm just an average Win user ).

What really troubles me is the output of apt-get -f install:

Setting up linux-image-2.6.22-14-generic (2.6.22-14.51) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.22-14-generic
/usr/sbin/mkinitramfs: 13: getopt: not found
Terminating...
update-initramfs: failed for /boot/initrd.img-2.6.22-14-generic
Failed to create initrd image.
dpkg: error processing linux-image-2.6.22-14-generic (--configure):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 linux-image-2.6.22-14-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

Although I don't know what it actually means, I've got a feeling that I won't be able to boot.

[frodon]

Initramfs is the tools which handle your boot image so if it fails your kernel will indeed not boot except if you are lucky.
getopt packages seems not found so you should try to re-install the util-linux package which contain getopt :

sudo apt-get install util-linux

Then update your system (if it works) :

sudo apt-get dist-upgrade && sudo apt-get update

The if this fail you will surely be asked to run the following command :

sudo dpkg --configure -a

[Tosa]

Thanks frodon.

I'm back home and I ran
sudo apt-get install util-linux because apt said that command reinstall didn't exist.

This is the output:

Selecting previously deselected package util-linux.
(Reading database ... 92342 files and directories currently installed.)
Unpacking util-linux (from .../util-linux_2.13-8ubuntu1_amd64.deb) ...
Setting up util-linux (2.13-8ubuntu1) ...

Setting up linux-image-2.6.22-14-generic (2.6.22-14.51) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.22-14-generic
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.22-14.47 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.22-14.47 was configured last, according to dpkg)
Running postinst hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.22-14-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

This seems to be OK now, at least I guess so.

I'll continue with the rest of your suggestions now, and i hope I'd dare to reboot.