Re: Difficulties dual-booting 2 Linux OS's - esp. re. LILO
From: Scruffy Eagle (this_cant_at_be.spammed)
Date: 11/19/04
- Next message: John Bahran: "Re: Directories"
- Previous message: Scott G: "Re: newbie question connecting to the internet"
- In reply to: Peter T. Breuer: "Re: Q. re. dual-boot of 2 Linux OS's - esp. re. LILO"
- Next in thread: Nico Kadel-Garcia: "Re: Difficulties dual-booting 2 Linux OS's - esp. re. LILO"
- Reply: Nico Kadel-Garcia: "Re: Difficulties dual-booting 2 Linux OS's - esp. re. LILO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 19 Nov 2004 04:27:34 -0600
"Peter T. Breuer" <ptb@lab.it.uc3m.es> wrote in message
news:ua9m62-q9u.ln1@news.it.uc3m.es...
>
> What is it with you? Can't you get a single thing straight?
>
> Peter
======================
Yah, hey dere, Peter!
As for why I can't "get a single thing straight",...
I'm a guy who spent the past 15 years working w/ MSDOS & Windows, but has
had absolutely no experience whatsoever with Linux or Unix. I'd been toying
with the idea of changing over to Linux for quite a while now, to get MS's
hand out of my pocket & their spyware out of my daily activities. But - it
was an idle pursuit in rare spare moments, up until a couple of weeks ago,
when my main machine crashed. Up till then, I'd had a functional Windows OS
to work & play with. I've tried to fix it, & even sought advice - but, I
don't see that machine being fixed any time soon, because I've become about
95% certain that it's either a blown video chip or a blown P4 CPU. I can't
afford to fix the thing, so my attention has shifted to my "backup"
machine - a HP 6360 that never worked right under Windows. (A bad purchase,
5 years ago - got burned by Comp USA on a "rehabbed" system.) So, there it
is - I'M A NEWBIE who's RTFM a couple of hours each day, & doing his best to
learn what he needs to know to get a functional Linux system up & running. I
haven't even figured out yet, how to format a floppy! In MSDOS or Windows,
it's easy - but, Linux? I feel like it's fighting me every step of the way.
Today's study time, after tweaking & testing time, was spent tracking down
the GRUB documentation (maybe I should switch boot loaders?) - and then,
ended up focusing on learning what I could about how to use the "Info"
utility; i.e., organization of info docs, commands, keystrokes, etc. Every
bit of documentation I transfer into these posts about the HP 6360 machine
is done via laboriously (heavy arthritis) handwriting to copy stuff from the
HP 6360's monitor, then typing it in on a Windows machine when I can borrow
some time on that. So, please don't tell me that I'm "acting crazy" (an item
I intentionally ignored, from your 1st response to me) - that's rude and
unfair. A month ago, "cat" only referred to a feline or a piece of
earth-moving equipment. I'm doing what I can with what I've got - and, if
you can't understand that and treat me with respect, well,... plonk you.
Now, if after all that, you're still interested in helping me, here's what
I've been up to lately in my attempts at setting up a dual-boot system:
(I should mention that the only reason I'm so intent on trying to set up a
dual-boot system, is that even though the Knoppix installation is fully
functional (90%?), its documentation sucks and there's no firewall. The
Woody setup's screwed up & won't initiate a Xwindows session - but, the
documentation's all there for me to learn from. That's why I need both
setups readily available. Sooner or later, I'll have learned enough from the
Woody installation's documentation that I'll be ready, and can import the
firewall from the Woody CD's into the Knoppix Debian OS; or, conversely,
will have learned enough to be able to tweak the Woody setup into fully
functional order. Really, I could care less, which partition's OS & version
of LILO controls the booting - as long as both partitions are available for
booting to a command prompt.)
==========================
The machine I'm working with is a HP 6360. It has 128 MB RAM, AMD-K6 333 MHz
CPU, 10 GB HD. I've got the HD partitions set up as:
300 MB = hda1 = swap
4 GB = hda2 = mainstream debian (woody/testing)
kernel image on hda2 = /hda2/boot/vmlinuz-2.4.18-k6
initrd image on hda2 = /hda2/boot/initrd.img-2.4.18-k6
3 GB = hda3 = Knoppix (SID/experimental)
1st kernel image on hda3 = /hda3/boot/vmlinuz-2.4.26
1st initrd image on hda3 = /hda3/boot/initrd.img-2.4.26
2nd kernel image on hda3 = /hda3/boot/vmlinuz-2.6.6
2nd initrd image = /hda3/boot/initrd.img-2.6.6
3 GB = free space at end of drive hda
----------------------------------------
Here's the hda3 (Knoppix) partition's lilo.conf as it was when I began
yesterday:
----------------
lba32
boot=/dev/hda
bitmap=/usr/share/lilo/contrib/debian.bmp
bmp-colors=1,,0,2,,0
bmp-table=120p,173p,1,15,17
bmp-timer=254p,432p,1,0,0
install=bmp
vga=normal
prompt
delay=30
timeout=100
default="Knx_Cmd-Ln"
read-only
image=/boot/vmlinuz
label="Knx_Cmd-Ln"
root=/dev/hda3
initrd=/boot/initrd.img
append="2 ramdisk_size=100000 lang=us apm=power-off nomce"
image=/boot/vmlinuz
label="Knx_KDE"
root=/dev/hda3
initrd=/boot/initrd.img
append="ramdisk_size=100000 lang=us apm=power-off nomce"
image=/boot/vmlinuz-2.4.26
label="K-Linux(2.4.26)"
root=/dev/hda3
initrd=/boot/initrd.img
append="ramdisk_size=100000 lang=us apm=power-off nomce"
image=/boot/vmlinuz-2.6.6
label="K-Linux(2.6.6)"
root=/dev/hda3
initrd=/boot/initrd.img
append="ramdisk_size=100000 lang=us apm=power-off nomce"
image=/mnt/hda2/vmlinuz
label="Woody-Linux"
root=/mnt/hda2
initrd=/mnt/hda2/boot/initrd.img-2.4.26-k6
append="2 devfs=mount"
----------------
Today, I began by mounting hda2, via
"mount /dev/hda2 /".
In the mount output it showed:
"/dev/hda2 on / type ext2 (rw)"
I changed the Woody-Linux stanza to become:
image=/dev/hda2/boot/vmlinuz-2.4.18-k6
label="Woody-Linux"
root=/dev/hda2
initrd=/dev/hda2/boot/initrd.img-2.4.18-k6
It wouldn't write the new LILO. Instead it gave error ouput:
"Fatal : open /dev/hda2/boot/vmlinuz-2.4.18-k6 : Not a directory"
-----------------
I rebooted and used the mount command,
"mount /dev/hda2 /mnt"
Output from mount<Enter> became,
/dev/hda3 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /proc/bus/usb type usbdevfs (rw)
automount (pid477) on /mnt/auto type autofs
(rw,fd=5,pgrp=477,minproto=2,maxproto=4)
/dev/hda2 on /mnt type ext2 (rw)
- - -
I changed the Woody stanza to become:
image=/mnt/boot/vmlinuz-2.4.26-k6
label="Woody-Linux"
root=/mnt
initrd=/mnt/boot/initrd.img-2.4.26-k6
- - -
The stuff left visible on the screen after a reboot into Woody attempt, was:
modprobe: Can't locate module *
Note: /etc/modules.conf is more recent than
/lib/modules/2.4.18-k6/modules.dep
NET4: Unix domain sockets 1.0SMP for LInux NET4.0
Journalled block device driver loaded
insmod: Note: /etc/modules.conf is more recent than
/lib/modules/2.4.18-k6/modules.dep
mount: /dev2/root is not a valid block device
insmod: Note: /etc/modules.conf is more recent than
/lib/modules/2.4.18-k6/modules.dep
mount: /dev2/root is not a valid block device
insmod: Note: /etc/modules.conf is more recent than
/lib/modules/2.4.18-k6/modules.dep
mount: /dev2/root is not a valid block device
insmod: Note: /etc/modules.conf is more recent than
/lib/modules/2.4.18-k6/modules.dep
mount: /dev2/root is not a valid block device
insmod: Note: /etc/modules.conf is more recent than
/lib/modules/2.4.18-k6/modules.dep
mount: /dev2/root is not a valid block device
mount: /dev2/root is not a valid block device
warning: can't open /etc/mtab: No such file or directory
pivot_root: No such file or directory
/sbin/init: cannot open dev/console : no such file
Kernel panic: Attempted to kill init!
- - -
As you can see, it's still doing that "/dev2" stuff. How does it come up
with that?
===========================================
When that failed, I decided I'd make an attempt at setting up dual-booting
from the other partition's setup (hda2's lilo.conf).
I rebooted into hda2 via the boot floppy, & re-wrote the LILO to make that
copy the default/active copy.
I used the command,
"mount /dev/hda3 /mnt
The output from "mount<Enter>" became:
/dev/hda2 on / type ext2 (rw,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
usbdevfs on proc/bus/usb type usbdevfs (rw)
/dev/hda3 on /mnt type ext3 (rw)
- - -
I wrote a Knoppix command-line stanza, using what was in the other lilo.conf
(as per booting "Knx_Cmd-Ln", at beginning of this post) as template:
image=/mnt/boot/vmlinuz-2.4.26
label=Knx_Cmd-Ln
root=/mnt
initrd=/mnt/boot/initrd.img-2.4.26
append="2 ramdisk_size=100000 lang=us apm=power-off nomce"
- - -
It wrote the hda2 LILO okay, but rebooting for the sake of testing left the
following visible on the screen:
ide: late registration of driver
SCSI subsystem driver Revision: 1.00
Kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter,errno=2
Kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter,errno=2
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP,UDP,TCP,IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 3407 freed
VFS: Mounted root (ext2 filesystem)
Freeing unused kernel memory: 140K freed
initrd-tools : 0.1.68
mount: fs type devfs not supported by kernel
Journalled Block Device driver loaded
umount : devfs : not mounted
/scripts/ext3-add-journal.sh: 32: arith : syntax error: "0x"
mount: proc already mounted or proc busy
mount: fs type devfs not supported by kernel
/sbin/init: 417: arith: syntax error: "0x"
Kernel panic: Attempted to kill init!
- - -
The one item from this output that stands out to me, is that the
"VFS: Mounted root (ext2 filesystem)"
line is specifying ext2, when it should have been booting an ext3
partition's map.
===================================================
Any suggestions?
Scruffy
http://scruffyeagle.com
- Next message: John Bahran: "Re: Directories"
- Previous message: Scott G: "Re: newbie question connecting to the internet"
- In reply to: Peter T. Breuer: "Re: Q. re. dual-boot of 2 Linux OS's - esp. re. LILO"
- Next in thread: Nico Kadel-Garcia: "Re: Difficulties dual-booting 2 Linux OS's - esp. re. LILO"
- Reply: Nico Kadel-Garcia: "Re: Difficulties dual-booting 2 Linux OS's - esp. re. LILO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
