| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 42492 | 2004-02-12 19:51:00 | Bloody Linux!!!!!!!1 | mark.p (383) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 214918 | 2004-02-12 19:51:00 | Now that I've got your attentention ;). For some reason BootMagic decided that it would vanish from my hda1(C; in doze speak) and would not give me the menu to boot into Linux or Windows with just the option boot the default active partition that happened to load Win98. "Oh alright" I says I'll just use the trusty RH8 boot disk everyone creates on installation and visit my fav comp forum. So smuggly I reboot with said disk in fdd. It boots up with all these module errors and kadzu decides my comp doesn't have a sound card (wiich it does) and prompts for the removel of the drivers. F(*&^ OFF! YOU WILL NOT!! so I chose to keep them. Upon ready my trusty WindowMaker desktop Lineinhorhood wouldn't show my networked PCs and KPPP wouldn't run "unexpected error". Hmmmmmmm Back to win98, yes everthing is working as it should. DON'T PANIC!! -was thinking I would have reinstall the whole shibang again but no. To cut the story short I downloaded XOSL, which is a free boot manager, installed and set it up and here I am -a happy wee chappy with a crappy in his nappy. Now can anyone explain why the Linux bootdisk did not give me a fully functioning system as I would have expected? Thanks for the imput in advance. |
mark.p (383) | ||
| 214919 | 2004-02-13 01:40:00 | Did you test your boot disk before you needed it? Did you compile a new kernel without making a new boot disk? You don't have any modules on the boot floppy...that's just enough to start a basic kernel.If you want to go from to a full catastrophe GUI, it needs to load modukes ... from the HD. If the versions of the modules on the HD don't match the version of the kernel which you booted from, the kernel starts to complain. Quite right, too. :D Keep your boot floppy uptodate. You'd get away with using the single user emergency boot (command line) to restore the grub or lilo boot manager.:D |
Graham L (2) | ||
| 214920 | 2004-02-13 01:41:00 | Did you test your boot disk before you needed it? Did you compile a new kernel without making a new boot disk? You don't have any modules on the boot floppy...that's just enough to start a basic kernel.If you want to go from to a full catastrophe GUI, it needs to load modukes ... from the HD. If the versions of the modules on the HD don't match the version of the kernel which you booted from, the kernel starts to complain. Quite right, too. :D Keep your boot floppy uptodate. You'd get away with using the single user emergency boot (command line) to restore the grub or lilo boot manager.:D Bloody users.;-) |
Graham L (2) | ||
| 214921 | 2004-02-13 03:25:00 | Lol thanks GL. Yes I did test the boot floppy previously after installation, a while back now though. Didn't take much notice of any errors at the time though. Was happy to try someting new. The impression I got was that the boot floppy (created during installation) actually passed command over to the kernal on hdc then fired up "the works"- (getting the hang of geek speeak ;) -it appears to imply that on bootup too. Kadzu throwing a wobbly doesn't make sence at all. The GUI started fine btw . All fixed now anyway I prefer to have GRuB on hdc's mbr and use another bootloader so if I stuff up Linux I can access you good folk via Win98;). Can create an XOSL emergency disk to boot linux if hda goes tits up. Thank GL Mark OS/2 v4 FP15-Using piccies as window backdrops since 1996! |
mark.p (383) | ||
| 214922 | 2004-02-13 03:41:00 | That boot floppy is a kernel . :D These days, it's probably made from the initrd file(a cutdown kernel with only the devices needed to load the full kernel) because the vmlinuz or bzImage (or whatever) has become a bit too bloated to fit in a floppy . All compressed kernels actually contain a floppy boot sector . Most of the boot floppies I have made have been done with dd if=/boot/vmlinuz of=/dev/fd0 bs=72k . Probably it's best to use the rescue mode of an installation CD for fixing problems . |
Graham L (2) | ||
| 214923 | 2004-02-13 04:17:00 | Hey thanks for the support. Will give it a go. | mark.p (383) | ||
| 214924 | 2004-02-14 09:30:00 | Can also make a boot disk with this command: mkbootdisk --device /dev/fd0 2.4.20-8 replace the kernel version with your one. |
JohnD (509) | ||
| 214925 | 2004-02-14 09:36:00 | >Probably it's best to use the rescue mode of an installation CD for fixing problems. If the boot manager stuffs up, place your first install CD into the drive and type: linux rescue at the prompt. You eventually get to a full working version of your system within another directory. For things to work properly you need to issue the command: chroot name_of_directory_installed_into You can then rewrite either LILO or GRUB to the master boot record. |
JohnD (509) | ||
| 214926 | 2004-02-14 09:52:00 | Thanks John. I have had a play with linux single-I saw somewhere on the "net:" a while back about training MS sales folk to use it to convince perspective Linux implementers that Linux isn't secure. Mind one can use NTFSDOS on a dos boot disk to veiw NTFS volume. Read only but..............;) | mark.p (383) | ||
| 214927 | 2004-02-14 10:21:00 | Linux single user mode isnt that hard to disable should you so desire.... Id say go with John's advice and chroot off the CD. Chill. |
Chilling_Silently (228) | ||
| 1 2 | |||||