after kernel was updated, I messed with vmlinuz, now no worky!
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
after kernel was updated, I messed with vmlinuz, now no worky!
Just yesterday, this Ubuntu Dapper Drake (LTS) laptop was working fine.
then,
...things happened.. and.. .
to try and "correct" the problem, i start tooling around in the terminal, looking for things, that don't exist. then i go to the root ( / )
and I see "vmlinux" and "vmlinux.old", that are 2 symbolic links to booting sequences. "old" points to 2.6.17-11-generic and the new one points to 2.6.17-12-generic . so stupid me, I try to switch the 2. making old be the -12 and the new be -11 using the cp command.
4) now I try to boot, and nothing happens. it can't even boot. get's stuck at the mouse splash screen
5) try to boot on the 2.6.17-12-generic recovery mode, and it gets as far as looking for a root directory aqnd then gets stuck.
6) try to boot with 2.6.17-11-generic and that works. but again, still no wireless connection, and if i look at the vmlinuz files that i messed around with in the root directory, they appear to be back to normal. with vmlinuz back to pointing to 2.6.17-12-generic , as if i never touched them (but there is an extra vmlinux.old2 file there, remnants of me trying to switch both around, and needing a temporary holding spot.)
So as it stands now, there is no wireless (the original problem that i glossed over in this post), and i have to boot with the old kernel version to see anything, and i don't see how i can go back and fix my mistakes, if they appear corrected already (but while booted under the old kernel version, which i think may be significant, but what the hell do i know, at this point?)
Btw, how did you get the wireless to work the first time round? Did you install drivers yourself? If so, they need to be reinstalled after every kernel update - that's just how it works.
Yes, Ubuntu has a liveCD. Unless you installed from the alternate cd, you should already have it. If not, you can the 7.04 cd instead but any liveCD should be fine; you aren't going to install anything, you're just going to do some repairs.
As for the drivers, yes, those need to be reinstalled. Drivers need to match a specific kernel so you can't use those that match one kernel release with the next one. Think of the windows equivalent: installing xp drivers on vista, that wouldn't work either, would it? That's a second advantages of not having to install any drivers oneself: not only do you get none of the fussing and tinkering, they will also get automatically updated when a newer kernel is installed. Btw, video drives will probably need to be reinstalled as well unless you were using the open source driver instead of a proprietary one (wouldn't this explain why you suddenly don't get any display anymore with the newer kernel?).
You could also use the grub shell and load in the kernel and initrd manually. It has autocompletion making typing easier. Enter the actual file instead of the link.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.