I purged the three 2.6.24-22 kernel modules you specified (Mark for complete removal), and successfully rebooted the Acer Aspire 5100. Then I used Synaptic to re-install the modules. I tried Update Manager first, but it didn't advise me the new modules were available. I clicked the "Check" button, but it still didn't see the new versions. There were nine 8.04 updates pending, but I ignored those, so as not to compromise my test. After the re-installation, I re-booted the machine, and it booted successfully this time with 2.6.24-22. However, I had no wireless capability. The wireless router is one floor below my apartment, so wired ethernet is not an option.
To restore wireless functionality, I had to "make" and "sudo make install" the madwifi-hal-0.10.5.6 software, and I noticed that it updated the 2.6.24-22 kernel modules. When I rebooted with the 2.6.24-22 kernel after the madwifi update, the boot stopped as before, with a blinking caps lock (kernel panic). During the boot, the boot progress bar is displayed, and I can watch the bar progress to about 95% boot completion before the kernel panic. Once my machine locked up (with the kernel panic), I turned it off by holding down the power button, and then I rebooted with the 2.6.24-16 kernel, and that worked successfully. After completion of the boot and my login, the wireless connected automatically, and my VPN definition was still there. This proves that it is the madwifi installation the corrupts the 2.6.24-22 kernel. I don't understand why it is necessary for the madwifi installation to modify the 2.6.24-22 kernel, since the wireless connection works with the unmodified 2.6.24-16 kernel. Obviously the madwifi installation also creates configuration files and/or installs other software to get wireless access working. I wonder if there is a way to partially install madwifi without affecting the 2.6.24-22 kernel, but still enable wireless functionality. Comments? Niels Andersen Belleville, Ontario, Canada You wrote: > > "[...]the only difference between the 'remove' and the 'purge' options (in > the terminal) and between the 'Mark for removal' and 'Mark for complete > removal' options is that with the 'purge' and 'Mark for complete removal' > options you [...]" > > -- > 8.04 blinking caps lock on bootup > https://bugs.launchpad.net/bugs/309311 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Ubuntu: New > > Bug description: > Problem occurs when booting "Ubuntu 8.04.1, kernel 2.6.24-22-generic" (line > copied from /boot/grub/menu.lst) on an Acer Aspire 5100 laptop. After > initial install the boot went ok. I have a configuration document I follow > to perform a fresh install of Ubuntu, and I was nearing the completion of > the install. As the final series of steps, I installed wine and > network-manager-pptp, configured wine, and installed a Windows program under > wine. VPN requires a reboot to enable VPN, and the problem occurs during > the reboot. Based on previous experience, the problem will recur on every > single reboot. The work-around is to boot from "Ubuntu 8.04.1, kernel > 2.6.24-16-generic" instead. I suspect the problem is caused by VPN, and next > time I do a fresh install, I will reboot after each of my install steps, to > confirm the machine will still boot. I am not using Ubuntu 8.10 because I > haven't been able to get wireless to work under 8.10. > -- 8.04 blinking caps lock on bootup https://bugs.launchpad.net/bugs/309311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
