2.4.26 vs. 2.4.29 ???Forum: HD Install Topic: 2.4.26 vs. 2.4.29 ??? started by: polypagan Posted by polypagan on April 06 2005,00:15
CD boots nicely with vga=normal on my eMachine w/64MB. All three of my eth adapters work fine. When I do a HD-install, system starts up and complains it can't find /lib/modules/2.4.29/... which is, indeed, correct. There is however a 2.4.26! I thought just copying that with .29 would fix, but then modprobe fails! No net! what's up? I cannot be the only newbie seeing this.Help! Thanks in advance, polypagan@yahoo.com Posted by tronik on April 06 2005,06:05
You do a hdinstall and it complains about 2.4.29 modules? we dont use a 2.4.29 kernel. so the only modules you should have when you do a new hdinstall is 2.4.26...And no, kernel modules contain symbols which make sure they're loaded with the kernel version they're made for. So, there must be something you're not telling us? Are you trying to install/compile 2.4.29 kernel? Posted by polypagan on April 06 2005,21:50
Thanks for your response.Of course there is a great deal I have not (yet) told you. No, I am too much of a newbie to undertake compiling a kernel just yet. So, that's not it. One major thing I didn't mention is that I have set up a triple booting situation with Lilo: Win98, Slackware 10.1 and DSL. Is that where the 2.4.29 confusion comes from? Seems unlikely, at least until I read your post. Maybe Lilo knows too much? I can pull the drive with win & slack out of the machine and make the DSL hd primary master. then do a new mklilo... worth a try... TFTH Posted by mikshaw on April 07 2005,01:08
well slackware 10.1 does use the 2.4.29 kernel, so it's a possibility that lilo has its wires crossed. Maybe you've got initrd and kernel mixed up between the distros. It shouldn't require reinstallation or pulling drives if that's the case....you can edit lilo.conf and run lilo to update.
Posted by polypagan on April 07 2005,21:56
Thank you both for useful and though-provoking comments.Juggling drives didn't work well -- mostly because systems expect drives/partitions to be where they left them... also no 'vga=normal' line in the mkliloboot output, so my crappy (Optiquest 900S) monitor goes nuts... I looked at lilo.conf, and sure enuf, I had (in ignorance) put the line image=vmlinuz (rather than linux24) in both sections. Ahah! that has to be it! Right? Wrong. When I choose to boot DSL I still see: <tons of stuff> INIT: version 2.78-knoppix booting Running Linux Kernel 2.4.29 <lots of error messages as modprobes fail> login: (and it works nicely, except for missing hardware) I should say I am using Slack to write the lilo, just cause it seems easier. I definitely don't understand every line in lilo.conf, or how entwined lilo is with what it boots. I am (slowly) learning correct mount syntax to get the two systems to see each others filesystems... Possibly (probably?) I am being too ambitious. My idea was to be able to evaluate the two HD-based systems on the same hardware. Hand-holding would be appreciated greatly. Posted by mikshaw on April 07 2005,22:09
with the DSL settings in lilo you might need to use a full path for kernel and initrd lines, or it may try to find them on the active partition. Not sure how it works in Lilo, but i assume it's similar to grub:
In this case hd0,0 is the primary drive, first partition (hda1), and hd0,3 is primary drive, fourth partition (hda4) Posted by polypagan on April 22 2005,22:52
Okay! You guys were very helpful in showing me where to look.My current setup: hda1 fat32 Win98 hda2 ext2 DSL hda3 ext2 Slack hdb1 swap hdb2 ext2 /usr/local The lilo.conf that works looks like this:
I installed it with the command: # lilo Works great! Thanks!!!! |