So what step did I miss upgrading my Debian kernel?

As root (either via "su -" or "sudo su -" or "sudo command")
apt-get install grub
That will install grub for you onto your booting drive.

Then Debian provides you with a Nice little "menu.lst" generator that works on many levels. As long as you have "Debian based kernels" You know "linux-image" or "kernel-image" stuffs, it basically removes all problems associated with the change over.

first, remove or rename /boot/grub/menu.lst (or remove it if it is a symlink, if non-existant, no biggy)

Then run (as root) update-grub

It'll be something like this stuff below.

king:~# update-grub\nSearching for GRUB installation directory ... found: /boot/grub\nTesting for an existing GRUB menu.list file ...\n\nCould not find /boot/grub/menu.lst file. Would you like /boot/grub/menu.lst generated for you? (y/N) y\nSearching for splash image ... none found, skipping ...\nFound kernel: /vmlinuz-2.6.15-1-k7\nFound kernel: /vmlinuz-2.6.14-1-k7\nFound kernel: /memtest86+.bin\nUpdating /boot/grub/menu.lst ... done\n\nking:~#

That is literally the whole shooting match.

There is only one issue that may come up if you are using XFS for your filesystem format on your "root partition for grub" (if only / then /. If /boot is seperate the only /boot). During the "xfs_freeze" stage of writing the journal out during the Master-Boot-Record or during the initial placing of the grub booting stages files it could go bad. This is a known problem, is fixed in the XFS code repository for the XFS kernel module, but not for "Official" Linux. There is some debate as to if the "fix" in its current form will ever make it into the Linux Tree.

Post #248,769 by drewk 3/21/06 7:16:27 PM Reply	So what step did I miss upgrading my Debian kernel? I installed `kernel-image-2.6.8-2-686`. I re-ran lilo (yes, I should switch to Grub, one thing at a time, if I hork this I have no backup to look things up with). I symlinked `/initrd.img -> /boot/initrd.img-2.6.8-2-686` and `/vmlinuz -> /boot/vmlinuz-2.6.8-2-686`. Lilo stanza is image=/vmlinuz\n label=Linux\n initrd=/initrd.img\n read-only Soon as I select that option in Lilo, it hangs on a blank screen. What am I missing? === Purveyor of Doc Hope's [link\|http://DocHope.com\|fresh-baked dog biscuits and pet treats]. [link\|http://DocHope.com\|http://DocHope.com]
Post #248,804 by CRConrad 3/22/06 2:24:24 AM Reply	Can Linux really boot from symlinks? I mean, I don't know fuck about this, but I'm guessing that maybe it can only follow symlinks to their actual counterparts after it's booted. Which would mean that you'd have to do a physical copy of those files to their new names/locations. Take this advice with about a lorry's worth of grains of salt. [link\|mailto:MyUserId@MyISP.CountryCode\|Christian R. Conrad] (I live in Finland, and my e-mail in-box is at the Saunalahti company.) Yes Mr. Garrison, genetic engineering lets us correct God's horrible, horrible mistakes, like German people. - [link\|http://maxpages.com/southpark2k/Episode_105\|Mr. Hat]
Post #248,808 by pwhysall 3/22/06 3:00:39 AM Reply	GRUB can and does. Peter [link\|http://www.no2id.net/\|Don't Let The Terrorists Win] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Home] Use P2P for legitimate purposes!
Post #248,816 by CRConrad 3/22/06 4:55:06 AM Reply	Ah, OK, thanks. BTW, is guildenstern down...
Post #248,818 by pwhysall 3/22/06 7:10:43 AM Reply	It's deader than your dress sense at the moment. See thread in Internet for reasons and possibility of replacement/revival. Peter [link\|http://www.no2id.net/\|Don't Let The Terrorists Win] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Home] Use P2P for legitimate purposes!
Post #248,809 by pwhysall 3/22/06 3:01:15 AM Reply	LILO follows them and goes to the pointed-to thing. Peter [link\|http://www.no2id.net/\|Don't Let The Terrorists Win] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Home] Use P2P for legitimate purposes!
Post #248,817 by CRConrad 3/22/06 4:56:28 AM Reply	...or is there any other reason why your pic won't show?
Post #248,810 by pwhysall 3/22/06 3:02:03 AM Reply	apt-get install grub Yes, it's that easy. No more excuses! No prevaricating over other people's punctuation! Begone! Do not return until you're GRUBed! Peter [link\|http://www.no2id.net/\|Don't Let The Terrorists Win] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Home] Use P2P for legitimate purposes!
Post #248,822 by folkert 3/22/06 7:30:52 AM Reply	Especially on Debian As root (either via "su -" or "sudo su -" or "sudo command") `apt-get install grub` That will install grub for you onto your booting drive. Then Debian provides you with a Nice little "menu.lst" generator that works on many levels. As long as you have "Debian based kernels" You know "linux-image" or "kernel-image" stuffs, it basically removes all problems associated with the change over. first, remove or rename /boot/grub/menu.lst (or remove it if it is a symlink, if non-existant, no biggy) Then run (as root) `update-grub` It'll be something like this stuff below. king:~# update-grub\nSearching for GRUB installation directory ... found: /boot/grub\nTesting for an existing GRUB menu.list file ...\n\nCould not find /boot/grub/menu.lst file. Would you like /boot/grub/menu.lst generated for you? (y/N) y\nSearching for splash image ... none found, skipping ...\nFound kernel: /vmlinuz-2.6.15-1-k7\nFound kernel: /vmlinuz-2.6.14-1-k7\nFound kernel: /memtest86+.bin\nUpdating /boot/grub/menu.lst ... done\n\nking:~# That is literally the whole shooting match. There is only one issue that may come up if you are using XFS for your filesystem format on your "root partition for grub" (if only / then /. If /boot is seperate the only /boot). During the "xfs_freeze" stage of writing the journal out during the Master-Boot-Record or during the initial placing of the grub booting stages files it could go bad. This is a known problem, is fixed in the XFS code repository for the XFS kernel module, but not for "Official" Linux. There is some debate as to if the "fix" in its current form will ever make it into the Linux Tree. -- [link\|mailto:greg@gregfolkert.net\|greg], [link\|http://www.iwethey.org/ed_curry\|REMEMBER ED CURRY!] @ *i_wethey* Freedom is not FREE. Yeah, but 10s of Trillions of US Dollars? SELECT * FROM scog WHERE ethics > 0; 0 rows returned.
Post #248,887 by drewk 3/22/06 1:23:27 PM Reply	Just did that Grub was already installed, but Lilo was still doing its thing. Is there something else I need to do to make Grub take over? Will go try rebooting now to see if It Just Works while I wait for a reply. === Purveyor of Doc Hope's [link\|http://DocHope.com\|fresh-baked dog biscuits and pet treats]. [link\|http://DocHope.com\|http://DocHope.com]
Post #248,896 by Yendor 3/22/06 1:45:10 PM Reply	If LILO is still doing its thing... `apt-get remove --purge lilo` -YendorMike "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759 Historical Review of Pennsylvania
Post #248,902 by pwhysall 3/22/06 3:11:29 PM Reply	grub-install hd0 Peter [link\|http://www.no2id.net/\|Don't Let The Terrorists Win] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Home] Use P2P for legitimate purposes!
Post #248,928 by drewk 3/22/06 6:50:00 PM Reply	p3t4h \|5 t3h r0Xx0Rz Now I just have to figure out why KDM is failing. It shows the line saying it's starting, the screen blanks, then I'm back at a terminal login. I log in, do `sudo /etc/init.d/kdm start` and it works fine. Also, when I [ctrl][alt][f2] to switch to a different tte, the keyboard goes flooey. Looks like I'm typing unicode characters. Well, one thing at a time. At least I'm on a 2.6 kernel now. === Purveyor of Doc Hope's [link\|http://DocHope.com\|fresh-baked dog biscuits and pet treats]. [link\|http://DocHope.com\|http://DocHope.com]
Post #248,968 by pwhysall 3/23/06 12:56:51 AM Reply	have a look in /etc/x11 There's a file in there that shows what your current display manager is - prefdm or somesuch. Wanna bet a pint that it doesn't say "kdm"? Peter [link\|http://www.no2id.net/\|Don't Let The Terrorists Win] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Home] Use P2P for legitimate purposes!
Post #248,970 by pwhysall 3/23/06 1:13:33 AM Reply	Also, check your alternatives update-alternatives --config x-display-manager Peter [link\|http://www.no2id.net/\|Don't Let The Terrorists Win] [link\|http://www.kuro5hin.org\|There is no K5 Cabal] [link\|http://guildenstern.dyndns.org\|Home] Use P2P for legitimate purposes!
Post #248,976 by drewk 3/23/06 2:24:29 AM Reply	Nothing for x-display-manager Though x-window-manager is set to /usr/bin/kwin. I manually went into `/etc/rc3.d/` and added an entry for kdm back when I switched from Gnome and it started working. That entry seems to be gone now. Hmmm ... Oh, and: drook@drookenstein:~$ cat /etc/X11/default-display-manager\n/usr/bin/kdm Like I said, I see the line where kdm tries to start, it just doesn't actually start. === Purveyor of Doc Hope's [link\|http://DocHope.com\|fresh-baked dog biscuits and pet treats]. [link\|http://DocHope.com\|http://DocHope.com]

Welcome to IWETHEY!