Printable View
It seems I've installed Knoppix on a hdd partition correctly, but for some reason, the boot floppy made by the process never works! And now I have the install on the parition, but I can't boot it! I tried GAG, but it doesn't detect a boot sector or something. I installed LILO on the partition so I didnt replace the MBR. So whats up?
Just an idea.....boot from the CD to completion, bring up console, type "sudo su" [without quotes] and run cfdisk. Look at your primary LINUX partition and make sure it is set to bootable. That is the first choice in the several choices at bottom of screen. You could use qtparted, but i am not too familiar with that program. But cfdisk is pretty simple to use. Just look for your PRIMARY LINUX PARTITION......on that same line you should see the word 'boot'. If not, look at bottom of screen. bootable is the first choice. Just hit "enter" then press right arrow key to "write", press enter....then press right arrow key all the way round till you come to QUIT or EXIT. Reboot and cross your fingers! Hope this helps.
And this will allow me to use it in GAG? Or the NT bootloader?
Hi....Unfortunatly I am not familiar with GAG or the NT bootloader as far as a dual boot with LINUX. I know, just from my experiance with KNOPPIX, if you just use the regular installer, knx2hd, you will be prompted to setup LILO, but you have to configure it later by using KWRITE, or any editor to recognize and show you your boot options, as far as choices between Windows, Linux etc. Anyway thats how I did mine.
If you want to use NTldr you can:
- Boot cd
- open a terminal
- type: mount /dev/hdXY /mnt/hdXY (where X is the disk and Y partition for root)
- type: chroot /mnt/hdXY/ /sbin/lilo -v (to change root to and run lilo on the hdinstall)
- type: cd /
- type: dd if=/dev/hdXY of=/bootsect.lnx bs=512 count=1
- copy the file from / to C:\ if it's fat, via floppy or some other if it's ntfs
- type: ctrl-d (to exit from chroot)
- reboot to windows
- add the line C:\bootsect.lnx="Linux" to C:\boot.ini
- reboot again and hope for the best
Markus, I tried your method and it didn't work, do I have to do what bob suggested first?
About the partitions? Yes, you should do it first.
Did you check if you got the file bootsect.lnx in your root partition?
Ok, when I do the cfdisk thing, it only looks at my first hdd. hda2 has the boot flag on. But my linux install is on hdb5! And I can't seem to check it. I type cfdisk /mnt/hdb5 and it says its in read only, even though I mounted the drive, and changed the read-write access. I see my knoppix install in there and everything but it doesnt work. I tried the knoppix bootfromhd thing and it can't find something. And yes, I found the bootsect thing, copied it to a floppy, pasted in C: of windows and put in boot.ini your thing. It just gives me a black screen with the flashing underscore...
Is there something inside bootsect? I opened it in notepad and its empty...
Also, if this doesnt work, how do I dual boot with LILO? Without completely killing my MBR...
Bob:Quote:
Originally Posted by bob58
I just did the "sudo knx2hd" install (after installing Win 98SE first, on its own partition on the same drive) and lilo came up with the windows option for booting. I went ahead and edited the lilo config file to remove some undesirable options (and to rename some of them), but it recognized the Windows partition and booted to it just fine. I was impressed.
Your mileage may vary. . .
Have you read the sticky on top of this Hdd Install section: http://www.knoppix.net/forum/viewtopic.php?t=3311
I don't think notepad will show any characters in bootsect.lnx, haven't checked though.
Try with cfdisk /dev/hdb (notice dev instead of mnt)
Still I believe the easiest way to partition for linux is to pop in a Mandrake install CD, prepare the partitions and abort the installation just to continue with the distro of choise. (oh am I going to get flamed for that one :wink:)
Dual-booting with Lilo in the MBR isn't usually a problem, if it borks up you can restore your MBR. All in the sticky.
Ok, I got cfdisk to work, and I noticed that the first partition on hdb (hdb1, which I use in Windows for extra storage) is set to boot. I guess I leave it like that? I added the boot flag to hdb5, where the linux installation is and it still wouldn't boot. Do I need to redo that bootsect part?
And can LILO work on the MBR and detect Windows on 1 HDD while Linux on another? And how do I check if the linux install even worked? If it will even boot if the boot settings are correct?
You might as well try running Lilo again after chrooting to hdb5. After running Lilo you need to do the dd command again and copy the new file to C:\.
Can't see what might be wrong here though.
That's not a problem for Lilo. I have Lilo in the mbr and it boots fine windows on hda1 and Linux on hdb1.Quote:
And can LILO work on the MBR and detect Windows on 1 HDD while Linux on another?
Hmm, thougher one. If it doesn't boot I have no idea how to check if it works. If chrooting worked I suppose that something must work on the hdinstall if it ran Lilo on it. :?:Quote:
And how do I check if the linux install even worked? If it will even boot if the boot settings are correct?
All in all, I think it's a lot easier to just put Lilo in the MBR. If you want it out of there, just boot with a dos or win98 floppy and write "fdisk /mbr" and lilo is gone.
And LILO wil check both hdd's & set up a dual boot automatically?
At least it checked them automagically for me and should do it by default.
You can always edit /etc/lilo.conf by hand and ensure it has something for windows as in:
Always run /sbin/lilo after editing lilo.conf!Quote:
other=/dev/hda1
label="Windows2K"
I cant believe it, I re-installed linux, this time with LILO in MBR, and it still doesn't work! I don't even think LILO works because I get the NT loader screen, but now, my Knoppix choice, if chosen, causes a restart instead of the flashing thing. Windows still works fortunately... :?
You can delete the line from C:\boot.ini. It won't have any effect now anyway.
Do you have some sort of BIOS protection on the MBR?
Try running lilo again with:
- Boot cd
- open a terminal
- type: mount /dev/hdb5 /mnt/hdb5
- type: chroot /mnt/hdb5/ /sbin/lilo -v
- type: ctrl-d (to exit from chroot)
- reboot
Could you post from your hd-install /etc/lilo.conf?
Well, when I do that chroot thing in my console I get the copyright info, then I get this:
Reading boot sector from /dev/hda
Warning: '/proc/partition' does not exist, disk scan bypassed
Warning: Unable to determine video adapterin use in the present system
Using BITMAP secondary loader
Calling map_insert_data
Warning: The bootsector and map file are on different disks.
Mapping bitmap file...(shows directories)->(more directories shown)
and then it has some stuff like:
Boot image: /boot/vmlinuz -> vmlinuz-2.4.26
Mapping RAM disk /boot/initrd.img -> initrd.img-2.4.26
Added Linux*
and it has 3 of those
Boot other: /dev/hda1, on /dev/hda, loader CHAIN
Added Windows(hda1) (Here I dont get, hda1 is the first partition, but windows is on hda2? Must be the main boot thing)
Boot other:/dev/hda2, on /dev/hda, loader CHAIN
Device 0x0300: Inconsistent partition table, 2nd entry
CHS address in PT: 4:0:1 --> LBA (4032)
LBA address in PT: 64260 --> CHS (63:12:1)
Fatal: Either FIX-TABLE or IGNORE-TABLE must be specified
If not sure, first try IGNORE-TAPLE (-P ignore)
Now how do I check my lilo.conf because from Knoppix live CD it says I have no permission...
Sorry, never seen that one before.Quote:
Device 0x0300: Inconsistent partition table, 2nd entry
CHS address in PT: 4:0:1 --> LBA (4032)
LBA address in PT: 64260 --> CHS (63:12:1)
Fatal: Either FIX-TABLE or IGNORE-TABLE must be specified
If not sure, first try IGNORE-TAPLE (-P ignore)
To check lilo.conf:
- open terminal
- type: sudo kedit /etc/lilo.conf (use any editor you like)
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# Remove this line when you are done configuring. -KK
"! Please edit /etc/lilo.conf before running lilo!"
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda
# Specifies the device that should be mounted as root. (`/')
#
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
#
install=/boot/boot-menu.b
backup=/dev/null
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
# delay=20
timeout=100
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
# single-key
# delay=100
# timeout=100
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
# Boot up Linux by default.
#
default=Knoppix
image=/vmlinuz
append="lang=de apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi vga=791 quiet BOOT_IMAGE=knoppix"
root=/dev/hda5
label=Knoppix
read-write
# restricted
# alias=1
#image=/vmlinuz.old
# label=Linux-OLD
# read-only
# optional
# restricted
# alias=2
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
Here's the on in hdb5 though...
Quote:
# /etc/lilo.conf - See: 'lilo(8)' and 'lilo.conf(5)',
# --------------- 'install-mbr(8)', '/usr/share/doc/lilo/',
# and '/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run 'lilo' after you make changes to this |
# | conffile, '/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run 'lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda
# Specifies the device that should be mounted as root. ('/')
#
root=/dev/hdb5
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using 'compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Default menu for Debian. (Using the images from debian-bootscreen)
# from Philipp Wolfer <[email protected]>.
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 the specified file as the new boot sector.
# LILO supports built in boot sectory, you only need
# to specify the type, choose one from 'text', 'menu' or 'bitmap'.
# new: install=bmp old: install=/boot/boot-bmp.b
# new: install=text old: install=/boot/boot-text.b
# new: install=menu old: install=/boot/boot-menu.b or boot.b
# default: 'menu' is default, unless you have a bitmap= line
# Note: install=bmp must be used to see the bitmap menu.
# install=menu
# install=bmp
install=bmp
# Specifies the number of _tenths_ of a second LILO should
# wait before booting the first image. LILO
# doesn't wait if DELAY is omitted or if DELAY is set to zero.
delay=20
# Prompt to use certaing image. If prompt is specified without timeout,
# boot will not take place unless you hit RETURN
prompt
timeout=50
# Specifies the location of the map file. If MAP is
# omitted, a file /boot/map is used.
map=/boot/map
# Specifies the VGA text mode that should be selected when
# booting. The following values are recognized (case is ignored):
# NORMAL select normal 80x25 text mode.
# EXTENDED select 80x50 text mode. The word EXTENDED can be
# abbreviated to EXT.
# ASK stop and ask for user input (at boot time).
# <number> use the corresponding text mode. A list of available modes
# can be obtained by booting with vga=ask and pressing [Enter].
vga=791
# You can set a password here, and uncomment the 'restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an 'append'
# statement in 'lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like 'Linux init=/bin/sh',
# and thus becoming 'root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use 'install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM 'install-mbr(8)'.
#
# password=tatercounter2000
# You can put a customized boot message up if you like. If you use
# 'prompt', and this computer may need to reboot unattended, you
# must specify a 'timeout', or it will sit there forever waiting
# for a keypress. 'single-key' goes with the 'alias' lines in the
# 'image' configurations below. eg: You can press '1' to boot
# 'Linux', '2' to boot 'LinuxOLD', if you uncomment the 'alias'.
#
# message=/boot/bootmess.txt
# prompt
# single-key
# delay=100
# timeout=100
# Kernel command line options that apply to all installed images go
# here. See: The 'boot-prompt-HOWO' and 'kernel-parameters.txt' in
# the Linux kernel 'Documentation' directory.
#
# append=""
# Boot up Linux by default.
#
default="Linux"
image=/boot/vmlinuz
label="Linux"
initrd=/boot/initrd.img
append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce"
read-only
image=/boot/vmlinuz-2.4.26
label="Linux(2.4)-1"
initrd=/boot/initrd.img-2.4.26
append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce"
read-only
image=/boot/vmlinuz-2.6.5
label="Linux(2.6)-2"
initrd=/boot/initrd.img-2.6.5
append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce"
read-only
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the 'other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
other=/dev/hda1
label="Windows(hda1)"
other=/dev/hda2
label="WinXP/2K(hda2)"
other=/dev/hdb1
label="WinXP/2K(hdb1)"
Yes, it was the one on hdb5 I was interested in.
You can comment out the unnecessary ones for windows:
# other=/dev/hda1
# label="Windows(hda1)"
other=/dev/hda2
label="WinXP/2K(hda2)"
# other=/dev/hdb1
# label="WinXP/2K(hdb1)"
I've always had windows on hda1 so I'm not really sure if you need hda1 or hda2???
You could of course leave them uncommented to try which one boots with:
other=/dev/hda1
label="Windows(hda1)"
other=/dev/hda2
label="WinXP/2K(hda2)"
# other=/dev/hdb1
# label="WinXP/2K(hdb1)"
And then do:
- Boot cd
- open a terminal
- type: mount /dev/hdb5 /mnt/hdb5
- type: sudo su (cr@p! I think I forgot this before)
- type: chroot /mnt/hdb5/
- type: cd /
- type: kedit /etc/lilo.conf (make the changes)
- type: lilo -v
- type: ctrl-d (to exit from chroot)
- type: ctrl-d (to exit from su)
- reboot
What exactly does lilo look like, and why didn't it work the first time? DO you have to enable LILO to start up or something after installing it?
Can't say. Which Knoppix version are you using? Some fixes were made to the installer after the first 3.4 was released. Not sure if Lilo was included in the fixes.Quote:
why didn't it work the first time?
No. It's supposed to run at bootup after being installed.Quote:
DO you have to enable LILO to start up or something after installing it?
If you mean the graphical part of Lilo in action, it's just a splash picture with a menu. Although you can also add some kernel parameters in Lilo.Quote:
What exactly does lilo look like
If you mean mine, this is it after I snipped off some outcommented irrelevant parts:...
Quote:
# /etc/lilo.conf - See: 'lilo(8)' and 'lilo.conf(5)',
# --------------- 'install-mbr(8)', '/usr/share/doc/lilo/',
# and '/usr/share/doc/mbr/'.
# Support LBA for large hard disks.
#
lba32
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda
# Specifies the device that should be mounted as root. ('/')
#
root=/dev/hdb1
# compact
# Default menu for Debian. (Using the images from debian-bootscreen)
# from Philipp Wolfer <[email protected]>.
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
delay=20
prompt
timeout=50
map=/boot/map
vga=normal
default="Windows2K(hda1)"
image=/boot/vmlinuz-2.4.26-mppe-ar
label="Linux(2.4)-1"
append="ramdisk_size=100000 lang=us apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi nomce "
read-only
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the 'other' line to
# where your other OS' partition is.
other=/dev/hda1
label="Windows2K(hda1)"