Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Florian Ernst wrote: MicheleM wrote: all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. [...] But what did it happen? I think there is a bug somewhere. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? I upgraded a machine running lilo and debconf mailed me the following information: Subject: Debconf: Configuring lilo -- Deprecated parameters in LILO configuration Deprecated files have been found on your system. You must update the 'install=' parameter in your LILO configuration file (/etc/lilo.conf) in order to properly upgrade the package. The new 'install=' options are: 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 -- Debconf, running at discord.proulx.com [ Debconf was not configured to display this note, so it mailed it to you. ] Reading that message I took care of the problem (by installing grub) before rebooting the system. But I can't help but wonder if something similar occurred with the original poster? It was mailed to me because I had set my debconf to 'critical' only and so it was prevented from showing me a dialog box. Although for something like this it would justify a critical rating. Bob signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello again, On Thu, Jun 09, 2005 at 02:54:32PM -0700, MicheleM wrote: this is the output: anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat Name: lilo/runme Template: lilo/runme Owners: lilo [...] no more. Hm, strange, to me it looks like this question was never asked. I guess it's best to ask the lilo maintainers [EMAIL PROTECTED] about this, or you could send a bugreport against upgrade-reports... I personally don't use lilo myself, so I wouldn't dare venture any deeper into this problem. Cheers, Flo signature.asc Description: Digital signature
Release upgrade from Woody to Sarge failed reboot lilo problem
Hi there, yesterday I tried to upgrade my Woody production server to Sarge after reading and following step by step the relase notes under: http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. No way to boot the machine. I solved the problem with a knoppix live cd, I mounted the root partition, chrooted into it, mounted /boot partition and run lilo. After reboot the server was uprunning. But what did it happen? I think there is a bug somewhere. I post my ls -l /boot: total 4513 -rw-r--r-- 1 root root 512 2005-01-25 00:50 boot.0800 lrwxrwxrwx 1 root root 11 2005-01-25 00:48 boot.b - boot-menu.b -rw-r--r-- 1 root root 308326 2005-06-09 01:00 coffee.bmp -rw-r--r-- 1 root root3342 2005-01-25 00:45 config-2.4.28-bf2.4 -rw-r--r-- 1 root root 26684 2005-02-08 20:06 config-2.4.29 lrwxrwxrwx 1 root root 15 2005-06-09 01:00 debian.bmp - /boot/sarge.bmp -rw-r--r-- 1 root root 153720 2005-06-09 01:00 debianlilo.bmp -rw--- 1 root root 46080 2005-06-09 14:19 map -rw-r--r-- 1 root root 23662 2005-06-09 01:00 sarge.bmp -rw-r--r-- 1 root root 24116 2005-06-09 01:00 sid.bmp -rw-r--r-- 1 root root 568549 2005-01-25 00:45 System.map-2.4.28-bf2.4 -rw-r--r-- 1 root root 668419 2005-02-08 20:11 System.map-2.4.29 -rw-r--r-- 1 root root 1298076 2005-01-25 00:45 vmlinuz-2.4.28-bf2.4 -rw-r--r-- 1 root root 1477532 2005-02-08 20:11 vmlinuz-2.4.29 and the /etc/lilo.conf # /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/sda # Specifies the device that should be mounted as root. (`/') # root=/dev/sda4 # 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 # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # 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 # 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 timeout=150 # prompt # single-key # delay=100 # timeout=100 # Specifies the VGA
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello *, On Thu, Jun 09, 2005 at 08:23:39AM -0700, MicheleM wrote: yesterday I tried to upgrade my Woody production server to Sarge after reading and following step by step the relase notes under: http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. No way to boot the machine. I solved the problem with a knoppix live cd, I mounted the root partition, chrooted into it, mounted /boot partition and run lilo. After reboot the server was uprunning. But what did it happen? I think there is a bug somewhere. [...] I made a typescript's upgrade too but I don't think it's notable, of course you'll can ask me it. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? Cheers, Flo signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
On Thu, Jun 09, 2005 at 08:08:08PM +0200, Florian Ernst wrote: Hello *, all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. No way to boot the machine. I solved the problem with a knoppix live cd, I mounted the root partition, chrooted into it, mounted /boot partition and run lilo. After reboot the server was uprunning. But what did it happen? I think there is a bug somewhere. [...] I made a typescript's upgrade too but I don't think it's notable, of course you'll can ask me it. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? Why do people insist on using LILO? Just install grub, set it up once with symlinks and *never* mess with it again. In case anyone cares, here is my configuration: default 0 timeout 5 color cyan/blue white/blue title Debian GNU/Linux root(hd0,1) kernel /vmlinuz root=/dev/hda3 ro vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux (recovery mode) root(hd0,1) kernel /vmlinuz root=/dev/hda3 ro single vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux, OLD root(hd0,1) kernel /vmlinuz.old root=/dev/hda3 ro vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux, OLD (recovery mode) root(hd0,1) kernel /vmlinuz.old root=/dev/hda3 ro single vga=normal ide0=ata66 ide1=ata66 boot I installed it *one* time to the MBR. I have only since had to mess with it to replace the failed harddrive in the machine. If you have /boot on a separate partition, as I do, you will want to add 'do_symlinks = No' to /etc/kernel-img.conf. Trust me on this. It is really nice to have a boot loader that can actually read your filesystem. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgpOSyrM8YMun.pgp Description: PGP signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello *, On Thu, Jun 09, 2005 at 04:46:32PM -0400, Roberto C. Sanchez wrote: Why do people insist on using LILO? Just install grub, [...] Advocacy is one thing, trying to find out why a bug has occurred another. Let's try not to mix things up. Cheers, Flo signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hi Flo, this is the output: anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat Name: lilo/runme Template: lilo/runme Owners: lilo Name: lilo/upgrade Template: lilo/upgrade Owners: lilo I grep the upgrade's typescript searching for the lilo prompt but this is what I found: anjuna:~# cat /backup/typescript |grep lilo libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr Get:493 http://debian.fastweb.it sarge/main lilo 1:22.6.1-6.2 [343kB] Get:494 http://debian.fastweb.it sarge/main mbr 1.1.5-2 [20.4kB] Preparing to replace lilo 1:22.2-3 (using .../lilo_1%3a22.6.1-6.2_i386.deb) ... Unpacking replacement lilo ... Setting up lilo (22.6.1-6.2) ... no more. thanks Flo Mik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LILO problem
I partitioned my hard drive in such a way that i can install 2 OS. The partition goes like this: /dev/hda1 - Linux (ext3)- Bootable /dev/hda5 - Linux Swap /dev/hda3 - Linux (reiserfs) /dev/hda1 has Knoppix3.3 (LiveOIO) and /dev/hda3 has Knoppix 3.6. I configured /dev/hda3's lilo.conf by putting /dev/hda1 in the other line. Upon restarting lilo, an Invalid boot signature in /dev/hda1 error was displayed. Typing lilo -P -fix does not solve the problem either. What went wrong? Thanks! Post the version of lilo.conf that you last used to generate the MBR. I.e. the /etc/lilo.conf from which ever OS you last ran 'lilo' from. Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
LILO problem
I partitioned my hard drive in such a way that i can install 2 OS. The partition goes like this: /dev/hda1 - Linux (ext3)- Bootable /dev/hda5 - Linux Swap /dev/hda3 - Linux (reiserfs) /dev/hda1 has Knoppix3.3 (LiveOIO) and /dev/hda3 has Knoppix 3.6. I configured /dev/hda3's lilo.conf by putting /dev/hda1 in the other line. Upon restarting lilo, an Invalid boot signature in /dev/hda1 error was displayed. Typing lilo -P -fix does not solve the problem either. What went wrong? Thanks! Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lilo problem after upgrade on sid
hi i've been running sid and after an apt-get -f upgrade yesterday morning, i found that my lilo hangs. the letters LIL.. come up and it simply freezes. i read through several man-pages and lists and figured that the lilo may be pointing to incorrect map or something simply wrong with the MBR. several people have mentioned creating a boot-floppy using mkboot. can i create a boot-floppy on another sid machine using this utility (by specifying the correct boot partition?) if i point to a boot partition like /dev/hda5, how will it work since that device may not be created at boot (on mine its something like /dev/ide/bus0/target0/.../part5). i also bumped into this location, is that all thats needed? ftp://ftp.debian.org/debian/dists/sid/main/installer-i386/current/images/floppy/access/ the second alternative was that i install grub or lilo again. is there a way to do this via the installation CD? i find the option to install grub but am afraid that it looks like the installation will reformat the partition (the help on installation says any partition with a :) will retain data but the rest will be erased). is there an installation version that will allow me to just mount formatted partitions and install grub or lilo? thanks -- -- praveen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo problem after upgrade on sid
[EMAIL PROTECTED] wrote: hi i've been running sid and after an apt-get -f upgrade yesterday morning, i found that my lilo hangs. the letters LIL.. come up and it simply freezes. i read through several man-pages and lists and figured that the lilo may be pointing to incorrect map or something simply wrong with the MBR. several people have mentioned creating a boot-floppy using mkboot. can i create a boot-floppy on another sid machine using this utility (by specifying the correct boot partition?) if i point to a boot partition like /dev/hda5, how will it work since that device may not be created at boot (on mine its something like /dev/ide/bus0/target0/.../part5). i also bumped into this location, is that all thats needed? ftp://ftp.debian.org/debian/dists/sid/main/installer-i386/current/images/floppy/access/ Make a GRUB boot floppy. You don't have to install GRUB on your system as your boot loader, and the GRUB floppy will allow you to boot to any kernel on your system (as long as GRUB understands the filesystem). Pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo problem after upgrade on sid
On Wed, Jun 30, 2004 at 01:12:14PM -0400, Patrick Ouellette wrote: [EMAIL PROTECTED] wrote: hi i've been running sid and after an apt-get -f upgrade yesterday morning, i found that my lilo hangs. the letters LIL.. come up and it simply freezes. i read through several man-pages and lists and figured that the lilo may be pointing to incorrect map or something simply wrong with the MBR. several people have mentioned creating a boot-floppy using mkboot. can i create a boot-floppy on another sid machine using this utility (by specifying the correct boot partition?) if i point to a boot partition like /dev/hda5, how will it work since that device may not be created at boot (on mine its something like /dev/ide/bus0/target0/.../part5). i also bumped into this location, is that all thats needed? ftp://ftp.debian.org/debian/dists/sid/main/installer-i386/current/images/floppy/access/ Make a GRUB boot floppy. You don't have to install GRUB on your system as your boot loader, and the GRUB floppy will allow you to boot to any kernel on your system (as long as GRUB understands the filesystem). Pat you were right patrick. all i had to do was boot from the grub-floppy, set root to the partition which contained my vmlinuz, set kernel=/vmlinuz, and fire boot. back in business. thanks. -- praveen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian/Lilo problem
Try placing the root= in your mkinitrd.conf. # If this is set to probe mkinitrd will try to figure out what's needed to # mount the root file system. This is equivalent to the old PROBE=on setting. ROOT=/dev/hdb1 ext3 substitute your file system, ext2, etc. Quotes are necessary for correct parsing. probe does not work any more On Sunday 16 May 2004 22:50, [EMAIL PROTECTED] wrote: VFS: Cannot open root device 305 or 03:05 Please append a correct root= boot option Kernel panic: VFS:Unable to mount root fs on 03:05 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian/Lilo problem
I am trying to get a Debian system 3.0 to use a 2.4.16-k7 kernel I have added the kernel to lilo.conf entered the command lilo but get a error (I do not get the error if I try using the 2.2.20-idepci kernel) the error is:- request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 305 or 03:05 Please append a correct root= boot option Kernel panic: VFS:Unable to mount root fs on 03:05 If you have ANY clues please let me know as I have spent 3 days on this now or if you can tell me where I can find an ISO 2.4cd that will install using a network install it would save me hours of work. And I need this working by AM tomorrow ! Thanks Denis -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Marvin the E-Mail scanner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian/Lilo problem
Hello, Denis, On Sun, May 16, 2004 at 07:02:27PM +0100, Denis Croombs wrote: I am trying to get a Debian system 3.0 to use a 2.4.16-k7 kernel I have added the kernel to lilo.conf entered the command lilo but get a error (I do not get the error if I try using the 2.2.20-idepci kernel) the error is:- request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 305 or 03:05 Please append a correct root= boot option Kernel panic: VFS:Unable to mount root fs on 03:05 Are you using initrd and is your filesystem type supported at the moment of mounting? With kind regards, Baurjan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian/Lilo problem
On Sun, May 16, 2004 at 07:17:23PM +0100, Denis Croombs wrote: I am using ext2 I have tried with and without initrd ! Is ext2 compiled into your kernel? If it is a module, you might need to add it to your initrd. If you have a serial console, a full boot output would help. Is it a standard Debian kernel? With kind regards, Baurjan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian/Lilo problem
in lilo.conf , enter line root=/dev/*d** for example root=/dev/hda1 cheers, http://www.axeltabs.com/ __ axel --- Denis Croombs [EMAIL PROTECTED] wrote: I am trying to get a Debian system 3.0 to use a 2.4.16-k7 kernel I have added the kernel to lilo.conf entered the command lilo but get a error (I do not get the error if I try using the 2.2.20-idepci kernel) the error is:- request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 305 or 03:05 Please append a correct root= boot option Kernel panic: VFS:Unable to mount root fs on 03:05 If you have ANY clues please let me know as I have spent 3 days on this now or if you can tell me where I can find an ISO 2.4cd that will install using a network install it would save me hours of work. And I need this working by AM tomorrow ! Thanks Denis -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Marvin the E-Mail scanner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Do you Yahoo!? SBC Yahoo! - Internet access at a great low price. http://promo.yahoo.com/sbc/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian installieren mit debootstrap LILO Problem
Hallo, ich möchte ein Debian mit Hilfe eines debootstrap installieren. dazu stecke ich die Platte auf die das neue Debian soll (kann alternativ auch einfach ein zweites System auf einer anderen Partition sein). in den Rechner, mache mit cfdisk die Partitionen die ich will und mit mkfs.ext3 das Filesystem. Dann mounte ich die Partition und spiele mit debootstrap das System drauf (woody,sarge oder sid). Soweit klappt das auch gut. Ich kann nun auch mit chroot rein und innerhalb des Systems normal arbeiten und weitere Software installieren. Nur wenn ich jetzt einen Kernel installiere kriege ich Probleme wegen lilo. Die Map sei nicht vorhanden. Das reinkopieren der Files aus einem funktionierenden System will irgendwie auch nicht klappen. Was mache ich hier falsch, oder wie kriege ich die für lilo notwendigen Dateien da rein ? MFG Rainer Brosi -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
[kernel 2.6.3] lilo-problem
Hi Leute Ich habe hier auf meiner debian-Kiste den Kernel 2.6.3 kompiliert/installiert. Jetzt habe ich allerdings probleme mit lilo: # lilo Warning: '/proc/partitions' does not match '/dev' directory structure. Name change: '/dev/nbd0' - '/tmp/dev.0' Warning: '/dev' directory structure is incomplete; device (43, 0) is missing. Warning: '/dev' directory structure is incomplete; device (43, 1) is missing. Warning: '/dev' directory structure is incomplete; device (43, 2) is missing. Warning: '/dev' directory structure is incomplete; device (43, 3) is missing. Warning: '/dev' directory structure is incomplete; device (43, 4) is missing. Warning: '/dev' directory structure is incomplete; device (43, 5) is missing. Warning: '/dev' directory structure is incomplete; device (43, 6) is missing. Warning: '/dev' directory structure is incomplete; device (43, 7) is missing. Warning: '/dev' directory structure is incomplete; device (43, 8) is missing. Warning: '/dev' directory structure is incomplete; device (43, 9) is missing. Warning: '/dev' directory structure is incomplete; device (43, 10) is missing. Warning: '/dev' directory structure is incomplete; device (43, 11) is missing. Warning: '/dev' directory structure is incomplete; device (43, 12) is missing. Warning: '/dev' directory structure is incomplete; device (43, 13) is missing. Warning: '/dev' directory structure is incomplete; device (43, 14) is missing. Warning: '/dev' directory structure is incomplete; device (43, 15) is missing. Warning: '/dev' directory structure is incomplete; device (43, 16) is missing. Warning: '/dev' directory structure is incomplete; device (43, 17) is missing. Warning: '/dev' directory structure is incomplete; device (43, 18) is missing. Warning: '/dev' directory structure is incomplete; device (43, 19) is missing. Warning: '/dev' directory structure is incomplete; device (43, 20) is missing. Warning: '/dev' directory structure is incomplete; device (43, 21) is missing. Warning: '/dev' directory structure is incomplete; device (43, 22) is missing. Warning: '/dev' directory structure is incomplete; device (43, 23) is missing. Warning: '/dev' directory structure is incomplete; device (43, 24) is missing. Warning: '/dev' directory structure is incomplete; device (43, 25) is missing. Warning: '/dev' directory structure is incomplete; device (43, 26) is missing. Warning: '/dev' directory structure is incomplete; device (43, 27) is missing. Warning: '/dev' directory structure is incomplete; device (43, 28) is missing. Warning: '/dev' directory structure is incomplete; device (43, 29) is missing. Warning: '/dev' directory structure is incomplete; device (43, 30) is missing. Warning: '/dev' directory structure is incomplete; device (43, 31) is missing. Warning: '/dev' directory structure is incomplete; device (43, 32) is missing. Warning: '/dev' directory structure is incomplete; device (43, 33) is missing. Warning: '/dev' directory structure is incomplete; device (43, 34) is missing. Warning: '/dev' directory structure is incomplete; device (43, 35) is missing. Warning: '/dev' directory structure is incomplete; device (43, 36) is missing. Warning: '/dev' directory structure is incomplete; device (43, 37) is missing. Warning: '/dev' directory structure is incomplete; device (43, 38) is missing. Warning: '/dev' directory structure is incomplete; device (43, 39) is missing. Warning: '/dev' directory structure is incomplete; device (43, 40) is missing. Warning: '/dev' directory structure is incomplete; device (43, 41) is missing. Warning: '/dev' directory structure is incomplete; device (43, 42) is missing. Warning: '/dev' directory structure is incomplete; device (43, 43) is missing. Warning: '/dev' directory structure is incomplete; device (43, 44) is missing. Warning: '/dev' directory structure is incomplete; device (43, 45) is missing. Warning: '/dev' directory structure is incomplete; device (43, 46) is missing. Warning: '/dev' directory structure is incomplete; device (43, 47) is missing. Warning: '/dev' directory structure is incomplete; device (43, 48) is missing. Warning: '/dev' directory structure is incomplete; device (43, 49) is missing. Warning: '/dev' directory structure is incomplete; device (43, 50) is missing. Fatal: Failed to create a temporary device Kernel-Version: 2.6.3 (mit vorangehenden Versionen hatte ich keine Probleme) devfs ist nicht drin (demnach auch kein devfsd) greets sd -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
[Kernel 2.6.3] lilo Problem
Hi Leute Ich habe hier auf meiner debian-Kiste den Kernel 2.6.3 kompiliert/installiert. Jetzt habe ich allerdings probleme mit lilo: # lilo Warning: '/proc/partitions' does not match '/dev' directory structure. Name change: '/dev/nbd0' - '/tmp/dev.0' Warning: '/dev' directory structure is incomplete; device (43, 0) is missing. Warning: '/dev' directory structure is incomplete; device (43, 1) is missing. Warning: '/dev' directory structure is incomplete; device (43, 2) is missing. Warning: '/dev' directory structure is incomplete; device (43, 3) is missing. Warning: '/dev' directory structure is incomplete; device (43, 4) is missing. Warning: '/dev' directory structure is incomplete; device (43, 5) is missing. Warning: '/dev' directory structure is incomplete; device (43, 6) is missing. Warning: '/dev' directory structure is incomplete; device (43, 7) is missing. Warning: '/dev' directory structure is incomplete; device (43, 8) is missing. Warning: '/dev' directory structure is incomplete; device (43, 9) is missing. Warning: '/dev' directory structure is incomplete; device (43, 10) is missing. Warning: '/dev' directory structure is incomplete; device (43, 11) is missing. Warning: '/dev' directory structure is incomplete; device (43, 12) is missing. Warning: '/dev' directory structure is incomplete; device (43, 13) is missing. Warning: '/dev' directory structure is incomplete; device (43, 14) is missing. Warning: '/dev' directory structure is incomplete; device (43, 15) is missing. Warning: '/dev' directory structure is incomplete; device (43, 16) is missing. Warning: '/dev' directory structure is incomplete; device (43, 17) is missing. Warning: '/dev' directory structure is incomplete; device (43, 18) is missing. Warning: '/dev' directory structure is incomplete; device (43, 19) is missing. Warning: '/dev' directory structure is incomplete; device (43, 20) is missing. Warning: '/dev' directory structure is incomplete; device (43, 21) is missing. Warning: '/dev' directory structure is incomplete; device (43, 22) is missing. Warning: '/dev' directory structure is incomplete; device (43, 23) is missing. Warning: '/dev' directory structure is incomplete; device (43, 24) is missing. Warning: '/dev' directory structure is incomplete; device (43, 25) is missing. Warning: '/dev' directory structure is incomplete; device (43, 26) is missing. Warning: '/dev' directory structure is incomplete; device (43, 27) is missing. Warning: '/dev' directory structure is incomplete; device (43, 28) is missing. Warning: '/dev' directory structure is incomplete; device (43, 29) is missing. Warning: '/dev' directory structure is incomplete; device (43, 30) is missing. Warning: '/dev' directory structure is incomplete; device (43, 31) is missing. Warning: '/dev' directory structure is incomplete; device (43, 32) is missing. Warning: '/dev' directory structure is incomplete; device (43, 33) is missing. Warning: '/dev' directory structure is incomplete; device (43, 34) is missing. Warning: '/dev' directory structure is incomplete; device (43, 35) is missing. Warning: '/dev' directory structure is incomplete; device (43, 36) is missing. Warning: '/dev' directory structure is incomplete; device (43, 37) is missing. Warning: '/dev' directory structure is incomplete; device (43, 38) is missing. Warning: '/dev' directory structure is incomplete; device (43, 39) is missing. Warning: '/dev' directory structure is incomplete; device (43, 40) is missing. Warning: '/dev' directory structure is incomplete; device (43, 41) is missing. Warning: '/dev' directory structure is incomplete; device (43, 42) is missing. Warning: '/dev' directory structure is incomplete; device (43, 43) is missing. Warning: '/dev' directory structure is incomplete; device (43, 44) is missing. Warning: '/dev' directory structure is incomplete; device (43, 45) is missing. Warning: '/dev' directory structure is incomplete; device (43, 46) is missing. Warning: '/dev' directory structure is incomplete; device (43, 47) is missing. Warning: '/dev' directory structure is incomplete; device (43, 48) is missing. Warning: '/dev' directory structure is incomplete; device (43, 49) is missing. Warning: '/dev' directory structure is incomplete; device (43, 50) is missing. Fatal: Failed to create a temporary device Kernel-Version: 2.6.3 (mit vorangehenden Versionen hatte ich keine Probleme) devfs ist nicht drin (demnach auch kein devfsd) greets sd -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
lilo problem!!!!!!!
Hello I need to install lilo on a HD on a machine that see it as /dev/sdc and use it to boot linux (root=/dev/sdc1) on a machine that see it as /dev/hdc (root=/dev/hdc1). My problem is that second machine realy is not a PC, so I must create disk on a PC. Can you give me a clue??? Thank you for all Angel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel lilo problem
Guten Abend zusammen, auf hoffnung bessere Hardware unterstützung zu bekommen natürlich mal an dem wirklichen Schrauben des Systems zu drehen, habe ich mich dran gemach (mit anweisungen auf http://www.stud.uni-karlsruhe.de/~usge/kernel-compile.html) den 2.4.22Kernel zu installieren. Es läut alles so lange gut, bis das System lilo ausführen muss. Dann heist es, das Fehler aufgetreten sind und ich die lilo.conf evtl. editieren soll und lilo ausführen soll. Zu editiren gibt es meiner meinung nach nichts. Als führe ich lilo aus und bekomme den folgenden Fehler: part_nowrite: read:: No such file or directory Weis jemand mir zu helfen? Gruss, Michael signature.asc Description: This is a digitally signed message part
Re: kernel lilo problem
Hi, Es läut alles so lange gut, bis das System lilo ausführen muss. Dann heist es, das Fehler aufgetreten sind und ich die lilo.conf evtl. editieren soll und lilo ausführen soll. Zu editiren gibt es meiner meinung nach nichts. Wie sieht sie denn aus, die lilo.conf? Als führe ich lilo aus und bekomme den folgenden Fehler: part_nowrite: read:: No such file or directory Greets Holger -- === Created with Sylpheed 0.7.4-claws under Debian GNU LINUX 3.0 Woody. Registered LinuxUser #311290 === -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: kernel lilo problem
Moin moin, Am Friday 07 November 2003 19:43 schrieb M.Kiberu: [...] http://www.stud.uni-karlsruhe.de/~usge/kernel-compile.html) den 2.4.22Kernel zu installieren. Es läut alles so lange gut, bis das System lilo ausführen muss. Dann heist es, das Fehler aufgetreten sind und ich die lilo.conf evtl. editieren soll und lilo ausführen soll. Zu editiren gibt es meiner meinung nach Hmm, ich ediere immer das Makefile lilo.conf! Darin setze ich EXTRAVERSION und INSTALLPATH. Nach dem edieren des MAkefiles lege ich INSTALLPATH im Dateisystem an. Beispiel: Makefile: EXTRAVERSION=rev1.0 INSTALLPATH=/boot/2.4.22/rev1.0 mkdir -p /boot/2.4.22/rev1.0 Nun den Ablageort des neuen Kernel in lilo.conf eintragen. -- image = /boot/2.4.22/rev1.0/vmlinuz root = /dev/hdb1 label = 2.4.22rev1.0 -- Die Vorarbeit ist nun gemacht ;) [EMAIL PROTECTED]:~$ make menuconfig [EMAIL PROTECTED]:~$ make dep clean bzImage [EMAIL PROTECTED]:~$ make modules modules_install [EMAIL PROTECTED]:~$ make install nichts. Als führe ich lilo aus und bekomme den folgenden Fehler: part_nowrite: read:: No such file or directory Huuu, den Fehler habe ich noch nicht gehabt. Bist Du Dir sicher, das Du nichts an lilo.conf machen musst? Die obigen Beispiele sind real aus meinen Woody System und funktioniert z.B. auch mit suse und den Kerneln von ftp.kernel.org Ciao Andre -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
lilo problem
Hello! I have entries in my lilo.conf like these: image=/boot/linux-2.4.22 label=D-Woody read-only other=/dev/hda5 label=D-Sarge other=/dev/hda6 label=Red-Hat 9 When I run the 'lilo' command it says: Fatal: First sector of /dev/hda6 doesn't have a valid boot signature Ok, but what should I do now? How can I make a valid boot signature to that partition? I have installed RH9 on it, and it seems it didn't create that onto that partition. How can I boot that partition then? It is a logical partition, not primary, but I toggled the Bootable flag on it with cfdisk. Is this the problem? Thanks for the help! Daniel -- LeVA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo problem
LeVA wrote: When I run the 'lilo' command it says: Fatal: First sector of /dev/hda6 doesn't have a valid boot signature Ok, but what should I do now? How can I make a valid boot signature to that partition? I have installed RH9 on it, and it seems it didn't create that onto that partition. How can I boot that partition then? It is a logical partition, not primary, but I toggled the Bootable flag on it with cfdisk. Is this the problem? Thanks for the help! Daniel You need to either boot to /dev/hda6 with a boot disk, or chroot into it and install grub or lilo to the first sector of the partition. I don't know how grub works, but for lilo, just make sure you have boot=/dev/hda6 -Robeto pgp0.pgp Description: PGP signature
Re: lilo problem
[EMAIL PROTECTED] wrote: Thanks for the help everyone, especially Michael. With your help I managed to get it working :) On Wed, 2003-09-17 at 15:03, Michael Bellears wrote: Ensure that /vmlinuz exists. It does on /dev/hdc8 Please show the output of mount. Cool, now that you've been through that and got it working, ever looked at Grub? * You don't have to run /sbin/grub every time you install a new kernel * If you forget to add the new config entry describing your new kernel you can still load the new kernel on reboot from the grub command line. ** Because of those features, if you had purged the kernel package for your configured boot kernel, you would still have a chance of booting into Debian, as long as some version of the kernel is installed. Although the method of defining drives is different than /dev/hd*, once you get the knack of it, the config file isn't that hairy. Just install grub-doc with grub and read the documentation. # By default, boot the second entry. default 1 # Boot default automatically after 30 seconds timeout 30 # Fallback to the first entry if the default fails fallback 0 # Debian Sid, Woody bf2.4 kernel title Debian Sid install kernel root (hd0,2) kernel /boot/vmlinuz-2.4.18-bf2.4 ro root=/dev/hda3 # Debian Sid 2.4.20-3-k7 title Debian Sid 2.4.20-3-k7 with Alsa root (hd0,2) kernel /boot/vmlinuz-2.4.20-3-k7 ro root=/dev/hda3 initrd /boot/initrd.img-2.4.20-3-k7 # Debian Sid 2.4.21-4-k7 title Debian Sid 2.4.21-4-k7 no sound root (hd0,2) kernel /boot/vmlinuz-2.4.21-4-k7 ro root=/dev/hda3 initrd /boot/initrd.img-2.4.21-4-k7 -- Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo problem
In linux.debian.user, you wrote: Hi, I have installed debain (woody) next to my current dist (mandrake 9.1). I added entries to mandrakes lilo.conf so that I could boot both debian and mandrake, I am sick of mandrake and want to completely switch to debian. I get the following error message when running lilo (on mandrake): Added linux * Added linux-nonfb Added failsafe Added windows Added floppy Added OldMandrake Fatal: open /vmlinuz: No such file or directory The last two entries in (mandrakes) /etc/lilo.conf: image=/boot/vmlinuz label=OldMandrake root=/dev/hdc1 initrd=/boot/initrd-2.4.21-0.13mdk.img read-only image=/vmlinuz label=Debian root=/dev/hdc8 boot=/dev/hdc8 install=/boot/boot.b map=/boot/map read-only What should I do? You are running this while in Mandrake; so mount hdc8 so that lilo can get to the kernel. I don't know about putting that boot=/dev/hdc8 in there. I would take that and map=/boot/map out of there as well as the install=/boot/boot.b. Change the first part of the stanza to: image=/mnt/vmlinuz (that is most likely a link to the kernel in /boot) Then mount /dev/hdc8 /mnt And try /sbin/lilo again. I usually just copy the kernel and the System.map from /boot of the second distro into /boot of the one I am using to do lilo. Then my line for all of them is image=/boot/vmlinuz-whatever-it-is. Anita -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: lilo problem
Thanks for the help everyone, especially Michael. With your help I managed to get it working :) On Wed, 2003-09-17 at 15:03, Michael Bellears wrote: Ensure that /vmlinuz exists. It does on /dev/hdc8 Please show the output of mount. MB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lilo problem
Hi, I have installed debain (woody) next to my current dist (mandrake 9.1). I added entries to mandrakes lilo.conf so that I could boot both debian and mandrake, I am sick of mandrake and want to completely switch to debian. I get the following error message when running lilo (on mandrake): Added linux * Added linux-nonfb Added failsafe Added windows Added floppy Added OldMandrake Fatal: open /vmlinuz: No such file or directory The last two entries in (mandrakes) /etc/lilo.conf: image=/boot/vmlinuz label=OldMandrake root=/dev/hdc1 initrd=/boot/initrd-2.4.21-0.13mdk.img read-only image=/vmlinuz label=Debian root=/dev/hdc8 boot=/dev/hdc8 install=/boot/boot.b map=/boot/map read-only What should I do? Thanks very much. Cheers Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: lilo problem
Fatal: open /vmlinuz: No such file or directory image=/vmlinuz ^^ label=Debian root=/dev/hdc8 boot=/dev/hdc8 install=/boot/boot.b map=/boot/map read-only What should I do? Pretty self explanatory: Ensure that /vmlinuz exists. Regards, MB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: lilo problem
Ensure that /vmlinuz exists. It does on /dev/hdc8 I imagine that /vmlinuz exists on all debian installs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: lilo problem
Ensure that /vmlinuz exists. It does on /dev/hdc8 Please show the output of mount. MB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: lilo problem
On Wed, 2003-09-17 at 15:03, Michael Bellears wrote: Ensure that /vmlinuz exists. It does on /dev/hdc8 Please show the output of mount. No output. It mounts without any problems, I am currently chrooted into it. Thanks for trying to find a solution :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 16 September 2003 07:07 pm, [EMAIL PROTECTED] wrote: On Wed, 2003-09-17 at 15:03, Michael Bellears wrote: Ensure that /vmlinuz exists. It does on /dev/hdc8 Please show the output of mount. No output. It mounts without any problems, I am currently chrooted into it. Thanks for trying to find a solution :) I use the following to get to my other install, I don't run initrd.img's so these two lines work for me. Maybe you are confusing lilo with to much info :) other=/dev/sda8 label=Sid(sda8) - -- Greg Madden Debian GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Z9Ovk7rtxKWZzGsRAnORAJ0aQeN2pN2BYjAlOgLbw3cNOh8KHgCgoPsM Be25DPBvQCnw91Pv1G+dSmY= =Rdxk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LILO problem
Thanks, It's work for me. Regards, Victor, - Original Message - From: Andrés Roldán [EMAIL PROTECTED] To: Victory [EMAIL PROTECTED] Cc: Debian-User [EMAIL PROTECTED] Sent: Monday, September 08, 2003 7:55 PM Subject: Re: LILO problem Change boot=/dev/sda1 for boot=/dev/sda and rerun /sbin/lilo Victory [EMAIL PROTECTED] writes: I use Noton Ghost 2003 to create disk to CD images then restored from CD Image to another disk, After done I the reboot to new disk and after MBR it support to start LILO 22.2 but it show all 01 number all over the screen, I think my MBR LILO is screw-up, search and found that Symantec say boot to the rescue disk and run LILO no further information. I am using Debian 3.0r1 kernel 2.4.18-bf2.4, any one run into same problem and know how to fix it? Here's my lilo.conf : boot=/dev/sda1 root=/dev/sda1 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label = Linux read-only Regards, Victor, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Andres Roldan [EMAIL PROTECTED] http://people.fluidsignal.com/~aroldan CSO, Fluidsignal Group -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
LILO problem
I use Noton Ghost 2003 to create disk to CD images then restored from CD Image to another disk, After done I the reboot to new disk and after MBR it support to start LILO 22.2 but it show all 01 number all over the screen, I think my MBR LILO is screw-up, search and found that Symantec say boot to the rescue disk and run LILO no further information. I am using Debian 3.0r1 kernel 2.4.18-bf2.4, any one run into same problem and know how to fix it? Here's my lilo.conf : boot=/dev/sda1 root=/dev/sda1 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label = Linux read-only Regards, Victor, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LILO problem
Change boot=/dev/sda1 for boot=/dev/sda and rerun /sbin/lilo Victory [EMAIL PROTECTED] writes: I use Noton Ghost 2003 to create disk to CD images then restored from CD Image to another disk, After done I the reboot to new disk and after MBR it support to start LILO 22.2 but it show all 01 number all over the screen, I think my MBR LILO is screw-up, search and found that Symantec say boot to the rescue disk and run LILO no further information. I am using Debian 3.0r1 kernel 2.4.18-bf2.4, any one run into same problem and know how to fix it? Here's my lilo.conf : boot=/dev/sda1 root=/dev/sda1 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label = Linux read-only Regards, Victor, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Andres Roldan [EMAIL PROTECTED] http://people.fluidsignal.com/~aroldan CSO, Fluidsignal Group -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
lilo problem
alles wieder in ordnung man sollte seinem default kernel auch den namen geben den er hat!! -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Lilo problem
Hi all, I copied a working debian installation from one hard disk to another, except i had to make a new kernel and install it. I copied the new bzImage into /boot, and updated lilo.conf. /boot contains the new kernel and nothing else. When i run lilo, it gives an error message: Fatal: open /boot/boot-menu.b: No such file or directory I thought lilo was meant to create this boot loader. /boot is in its own 50MB partition on hda1, and root is hda3. I can't see anything wrong with the way the file systems are mounted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lilo problem
Russell wrote: Hi all, I copied a working debian installation from one hard disk to another, except i had to make a new kernel and install it. I copied the new bzImage into /boot, and updated lilo.conf. /boot contains the new kernel and nothing else. When i run lilo, it gives an error message: Fatal: open /boot/boot-menu.b: No such file or directory I thought lilo was meant to create this boot loader. /boot is in its own 50MB partition on hda1, and root is hda3. I can't see anything wrong with the way the file systems are mounted. Fixed: re-install lilo to get new copies of boot-text.b, boot-menu.b, etc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian3.0, Win2000 and LILO problem
On Sun, 17 Nov 2002, Elimar Riesebieter wrote: On Sun, 17 Nov 2002 the mental interface of Jan Krupa told: Thanks for answer. On Sun, 17 Nov 2002, Elimar Riesebieter wrote: Hi Jan, On Sun, 17 Nov 2002 the mental interface of Jan Krupa told: [...] # Boot up Linux by default. # default=Win2000(hda1) ^ What do you want as your default? I want win2k to be deafault so I put default=Win2000(hda1) So everything you need in your lilo.conf is: boot = /dev/hda This line causes to remove the W2k loader doesn't it? If so how to recover it not to install W2k again? With lilo. man lilo # lilo -u /dev/hda Or repair the bootsektor with your W2K CD. Installing lilo in the mbr is not a problem. I a running one maschine with deb suse and w2k booting from mbr with lilo ;) First I had: boot = /dev/hda3 it worked for two days but when it finished to work I tried: boot=/dev/hda3 Can't see a diffrence? I am sorry I made mistake. There should be: it worked for two days but when it finished to work I tried: boot=/dev/hda It's a little bit better but still not enough well (see below). It's a little bit better but still not enough well (see below). What is better boot=/dev/hda3 or boot=/dev/hda3. lilo.conf accepts blanks or not. That is not the point and makes no different ;-) I am sorry agian for my mistake. When I put boot=/dev/hda3 and then the command lilo the following message appeared boot=/dev/hda3 lilo mel219:~# lilo Warning: Int 0x13 function 8 and function 0x48 return different head/sector geometries for BIOS drive 0x80 Added Linux Added Win2000(hda1) * After rebooting the system the following happens during booting process: --- Verifying DMI Pool Data ... After one day when I switch on the computer I saw the following: Verifying DMI Pool Data Boot from CD: MBR 3FA: --- and computer hanged. Then when I push enter the coloured LILO's menu appears and then the booting process goes correctly. Another strange thinks: when I try to load Linux from booting floppy first the kernel is not loading. Instead 'boot:0000...so on' appears (the zeros after 3 lines finish to appear). Then when I push enter the booting process goes correctly. Any clue? Jan See man lilo.conf Uff -- The way to source is always uphill! -unknown- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian3.0, Win2000 and LILO problem
I have Pentium IV, HD 40 GB. First Windows2000 professional was installed on first 30 GB of the HD (on hda1). Then on hda3 (10GB ) I installed Debian3.0 (current stable) using compact floppies and then via ftp. I chose (in the end of the installation process) to use menu version of LILO and to install it (LILO's boot block) in /dev/hda3. Linux was loaded default and Win2000 as other. I changed it manually editing lilo.conf so Win200 was loaded default and Linux as other. It worked fine. I compiled the kernel-2.4.18 ( from resources ) and run lilo and still it worked fine (I mean Win2000 and Linux was loaded properly). After one day when I switch on the computer I saw the following: Verifying DMI Pool Data Boot from CD: MBR 3FA: and computer hanged. (in BIOS the sequence boot is: floppy, CD, HH0). I tried to use the boot floppy to load linux but it did not work, instead sequence of zeros appeared: 0000...so on. The rescue floppy did not work either (the same behavior as in case of boot floppy, boot: 0...so on). But when I used Backspace to delete the appeared zeros they did not appeared again and boot: rescue root=/dev/hda3 worked and the linux kernel was loaded. When I tried to run lilo I got the following message: -- Warning: Int 0x13 function 8 and function 0x48 return different head/sector geometries for BIOS drive 0x80 Added Linux Added Win2000(hda1) * -- But it changed nothing. So I run: 'lilo -u' to uninstall LILO and change in lilo.conf the line boot=/dev/hda3 to be boot=/dev/hda. I run lilo (got the message as above: Warning: Int 0x13 function 8 and ...) but now something changed: The coloured LILO menu appeared, after the line (on the screen) boot: sequence of zeros appeared: 0000...so on but when I used Backspace to delete the appeared zeros they did not appeared again and I could choose which OS to load and they both seem to load properly. Question: Could someone please to help to configure LILO properly and get rid off the ''problem of zeros'' and to make happy LILO not to complain: Warning: Int 0x13 function 8 and ...? TIA Jan P.S. My lilo.conf without most comments. # /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/hda3 install=/boot/boot-menu.b # Specifies the location of the map file # # map=/boot/map # delay=20 prompt # timeout=150 # 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 # append= # Boot up Linux by default. # default=Win2000(hda1) image=/vmlinuz label=Linux root=/dev/hda3 read-only # restricted # alias=1 # image=/vmlinuz.old # label=LinuxOLD # 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 other=/dev/hda1 label=Win2000(hda1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian3.0, Win2000 and LILO problem
Hi Jan, On Sun, 17 Nov 2002 the mental interface of Jan Krupa told: [...] # /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/hda3 install=/boot/boot-menu.b # Specifies the location of the map file # # map=/boot/map # delay=20 prompt # timeout=150 # prompt # single-key # delay=100 # timeout=100 ^ why not? # Specifies the VGA text mode at boot time. (normal, extended, ask, mode) # # vga=ask # vga=9 # vga=normal # append= # Boot up Linux by default. # default=Win2000(hda1) ^ What do you want as your default? image=/vmlinuz label=Linux root=/dev/hda3 read-only # restricted # alias=1 # image=/vmlinuz.old # label=LinuxOLD # 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 other=/dev/hda1 label=Win2000(hda1) So everything you need in your lilo.conf is: boot = /dev/hda read-only lba32 prompt timeout = 100 install=/boot/boot-menu.b image=/vmlinuz label=Linux root=/dev/hda3 vga=normal other=/dev/hda1 optional label=Win2000(hda1) -- .~. /V\ L I N U X /( )\ Phear the Penguin ^^-^^ msg13469/pgp0.pgp Description: PGP signature
Re: Debian3.0, Win2000 and LILO problem
On Sun, 17 Nov 2002 the mental interface of Jan Krupa told: Thanks for answer. On Sun, 17 Nov 2002, Elimar Riesebieter wrote: Hi Jan, On Sun, 17 Nov 2002 the mental interface of Jan Krupa told: [...] # Boot up Linux by default. # default=Win2000(hda1) ^ What do you want as your default? I want win2k to be deafault so I put default=Win2000(hda1) So everything you need in your lilo.conf is: boot = /dev/hda This line causes to remove the W2k loader doesn't it? If so how to recover it not to install W2k again? With lilo. man lilo # lilo -u /dev/hda Or repair the bootsektor with your W2K CD. Installing lilo in the mbr is not a problem. I a running one maschine with deb suse and w2k booting from mbr with lilo ;) First I had: boot = /dev/hda3 it worked for two days but when it finished to work I tried: boot=/dev/hda3 Can't see a diffrence? It's a little bit better but still not enough well (see below). What is better boot=/dev/hda3 or boot=/dev/hda3. lilo.conf accepts blanks or not. That is not the point and makes no different ;-) See man lilo.conf Uff -- The way to source is always uphill! -unknown- msg13514/pgp0.pgp Description: PGP signature
Re: LILO problem.
On Thu, Jun 06, 2002 at 10:40:31PM +0200, Joachim Fahnenmueller wrote: Hi, there is only _one_ boot sector for the whole harddisk (e. g. hda). So you have the following options: 1. Install lilo in the harddisk's MBR. It can boot windoze as well, as Paul explained. Uh, you *can* install LILO into the parition rather than the MBR- but if you do, you need to bootstrap into the partition. So IMHO you might as well put it in the MBR, as you recommend. SRH -- Steve Haslam http://www.arise.demon.co.uk/ [EMAIL PROTECTED] Debian GNU/Linux Maintainer [EMAIL PROTECTED] but I won't admit to needing you I'll never say that's true, not to you [sister machine gun] pgpgaeEpYp8ap.pgp Description: PGP signature
LILO problem.
Hi, All, Here is my problem: I am installing the testing version of debian. during the installation of LILO, I choose to install it in the boot sector of hda2, which is my Linux root partition (hda1 is windows 98). after that, it asks me whether I want to install a new boot manager in the MBR, I thought that the purpose of not installing LILO in MBR is to leave that untouched, so I answered no, and then marked hda2 bootable in cfdisk (toggled off the bootable flag of hda1 at the same time). then reboot, It says missing operating system. so It seems to me that the DOS MBR is not finding hda2's boot sector, I thought that it is supposed to find that and hand the controll over to LILO. Can anyone tell me what I am doing wrong here? could it be the problem with my DOS MBR, which can only load hda1? Thanks a lot. = Ming Feng Gu Center for Space Research MIT, NE80-6083 617-258-5928 [EMAIL PROTECTED] = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LILO problem.
Ming Feng Gu wrote: Hi, All, Here is my problem: I am installing the testing version of debian. during the installation of LILO, I choose to install it in the boot sector of hda2, which is my Linux root partition (hda1 is windows 98). after that, it asks me whether I want to install a new boot manager in the MBR, I thought that the purpose of not installing LILO in MBR is to leave that untouched, so I answered no, and then marked hda2 bootable in cfdisk (toggled off the bootable flag of hda1 at the same time). then reboot, It says missing operating system. so It seems to me that the DOS MBR is not finding hda2's boot sector, I thought that it is supposed to find that and hand the controll over to LILO. Can anyone tell me what I am doing wrong here? could it be the problem with my DOS MBR, which can only load hda1? Yes. You will need some boot manager. lilo will work just fine for this. I used BootMagic until I switched to lilo. These lines in /etc/lilo.conf will set up the 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 These lines will boot your W98: # 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=Windows98 HTH, Paul Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LILO problem.
On Thu, Jun 06, 2002 at 11:12:48AM -0400, Ming Feng Gu wrote: ( ... ) I am installing the testing version of debian. during the installation of LILO, I choose to install it in the boot sector of hda2, which is my Linux root partition (hda1 is windows 98). Hi, there is only _one_ boot sector for the whole harddisk (e. g. hda). So you have the following options: 1. Install lilo in the harddisk's MBR. It can boot windoze as well, as Paul explained. 2. Install lilo on floppy only. (You should make a boot floppy anyway.) 3. Use loadlin instead. IMO, the 1st option is most convenient. If you don't want it anymore, you can restore the old MBR with the DOS command fdisk /mbr . HTH, Joachim -- Joachim Fahnenmüller Lehrer für Mathematik und Physik Herder-Gymnasium Kattowitzer Straße 52 51065 Köln -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo problem
Hello, I got sid working! *jump* Thanks to Alvin! -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org - keyserverID=24DC49C6 - http://www.zeus.rug.ac.be Private mail with incorrect quoting behavior will remain unanswered The backbone of surprise is fusing speed with secrecy. - Von Clausewitz (1780-1831)
Re: lilo problem
- Original Message - From: Rudy Gevaert [EMAIL PROTECTED] To: Alvin Oga [EMAIL PROTECTED] Cc: Rudy Gevaert [EMAIL PROTECTED]; debian-user@lists.debian.org Sent: Friday, February 22, 2002 3:47 PM Subject: Re: lilo problem Wel, I removed the initrd line from lilo.conf, and redhat boots fine, but when I try to boot Sid I get a kernel panic, no init found... try passing init= ...etc. This is my lilo.conf: image=/boot/vmlinuz-2.2.19 label=DebianSid read-only root=/dev/hdc1 I thought you had install Sid (and its kernel) on its own partition. So the Sid kernel surely isn't in the /boot directory of your Red Hat ! Try to mount you Sid (if its kernel is on /dev/hdc1) : mkdir /mnt/sid ; mount /dev/hdc1 /mnt/sid Then edit your Red Hat lilo.conf : image=/mnt/sid/boot/vmlinuz label = DebianSid root=/dev/hdc1 read-only Then do : lilo -v (to see the results of your command), reboot and i thik it will be good for you... Francis
Re: lilo problem - / problem
On Fri, Feb 22, 2002 at 06:07:58PM -0800, Alvin Oga wrote: cut Thanks for the tips, I'll try it Mondag asap! (I'm now home and dont have acces to my computer at uni) -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org - keyserverID=24DC49C6 - http://www.zeus.rug.ac.be Private mail with incorrect quoting behavior will remain unanswered Imitation is the sincerest form of television. - Fred Allen (1894-1956)
Re: lilo problem
hi ya I thought you had install Sid (and its kernel) on its own partition. So the Sid kernel surely isn't in the /boot directory of your Red Hat ! just many ways to skinn the cat... while booted on say /dev/hda1...( deb ) put all your kernels in /boot of the distro you wanna run lilo from if you want to always run lilo from slackware... than all the other kernels is in /boot of slackware... or a mounted dir as you've done with /mnt/xxx/boot/other_kernel ( but why run lilo from any distro... lot more lilo'ing to ( copy around vi /etc/lilo.conf ( if you dont want to mount the other distro before liloing ) ( where the kernels was copied from the other distro boot=/dev/hda ... image=/boot/vmlinux-2.2.20 root=/dev/hda1 label=Debian ... # copy the kernel over from slackware that was compiled on hdb1 image=/boot/vmlinuz-2.4.17 root=/dev/hdb1 label=slackware ... # copy the kernel over from redhat that was compiled on hdc1 image=/boot/vmlinuz-2.4.7-10 root=/dev/hdc1 label=redhat ... # # if you wanted windoze... on C: # other=/dev/hda1 # table=/dev/hda # label=windoze # Try to mount you Sid (if its kernel is on /dev/hdc1) : mkdir /mnt/sid ; mount /dev/hdc1 /mnt/sid Then edit your Red Hat lilo.conf : image=/mnt/sid/boot/vmlinuz label = DebianSid root=/dev/hdc1 read-only that works too .. to mount the other distro...before lilo'ing c ya alvin Then do : lilo -v (to see the results of your command), reboot and i thik it will be good for you... Francis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo problem
Hello, Due to some workload I've only had the time to look at this now. On Thu, Feb 21, 2002 at 05:12:12AM -0800, Alvin Oga wrote: hi ya if it hands on ramdisk... remove that initrd line... and/or make sure the file exists as typed Wel, I removed the initrd line from lilo.conf, and redhat boots fine, but when I try to boot Sid I get a kernel panic, no init found... try passing init= ...etc. This is my lilo.conf: [EMAIL PROTECTED] /root]# cat /etc/lilo.conf boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 linear default=nieuwekernel image=/boot/2.4.17 label=nieuwekernel read-only image=/boot/vmlinuz-2.2.19 label=DebianSid read-only root=/dev/hdc1 other=/dev/hda1 label=dos initrd is not needed if your kernel has all the hardware drivers needed to boot... So this explains why I get that error? Because it is still the standard kernel from Sid? for to install make, and want to install it if you're referring to redhats simple install.. - just boot the cdrom and tell it upgrade and it will go thru what you got ant ask you what else you want No, I'm referring to Debians install, when you can choosse: Simple or advanced install. ;) How do I get that screen back? Or, what packages do I have to install to get make etc? (I guess gcc ...?) rh is such a pita aint it??? Yes! But let me explain, when I got my new pc and started university I wanted GNU/Linux... and redhat was the only one I knew. After a couple of months I got to know Debian (they used it in my studentgroup (don't know the right translation...), and I wiped windows out at home and installed debian. On my new pc I had suffered 4 months to configure my dualhead that I didn't dare to install debian yet.. but now I bought a new hd; so the time has come to switch to debian :). Thanks for the help up till now, I hope you can help me with the rest :) Cheers, -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org - keyserverID=24DC49C6 - http://www.zeus.rug.ac.be Private mail with incorrect quoting behavior will remain unanswered While one person hesitates because he feels inferior, the other is busy making mistakes and becoming superior -- Henry C. Link
Re: lilo problem
I'm just coming into the thread, but if you had your initrd= in the main section of lilo.conf, try putting it in the image section of your Sid kernel. That way, no other kernel will try to use it. Bob On Fri, Feb 22, 2002 at 03:47:53PM +0100, Rudy Gevaert wrote: Hello, Due to some workload I've only had the time to look at this now. On Thu, Feb 21, 2002 at 05:12:12AM -0800, Alvin Oga wrote: hi ya if it hands on ramdisk... remove that initrd line... and/or make sure the file exists as typed Wel, I removed the initrd line from lilo.conf, and redhat boots fine, but when I try to boot Sid I get a kernel panic, no init found... try passing init= ...etc. This is my lilo.conf: [EMAIL PROTECTED] /root]# cat /etc/lilo.conf boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 linear default=nieuwekernel image=/boot/2.4.17 label=nieuwekernel read-only image=/boot/vmlinuz-2.2.19 label=DebianSid read-only root=/dev/hdc1 other=/dev/hda1 label=dos initrd is not needed if your kernel has all the hardware drivers needed to boot... So this explains why I get that error? Because it is still the standard kernel from Sid? for to install make, and want to install it if you're referring to redhats simple install.. - just boot the cdrom and tell it upgrade and it will go thru what you got ant ask you what else you want No, I'm referring to Debians install, when you can choosse: Simple or advanced install. ;) How do I get that screen back? Or, what packages do I have to install to get make etc? (I guess gcc ...?) rh is such a pita aint it??? Yes! But let me explain, when I got my new pc and started university I wanted GNU/Linux... and redhat was the only one I knew. After a couple of months I got to know Debian (they used it in my studentgroup (don't know the right translation...), and I wiped windows out at home and installed debian. On my new pc I had suffered 4 months to configure my dualhead that I didn't dare to install debian yet.. but now I bought a new hd; so the time has come to switch to debian :). Thanks for the help up till now, I hope you can help me with the rest :) Cheers, -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org - keyserverID=24DC49C6 - http://www.zeus.rug.ac.be Private mail with incorrect quoting behavior will remain unanswered While one person hesitates because he feels inferior, the other is busy making mistakes and becoming superior -- Henry C. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lilo problem
On Fri, Feb 22, 2002 at 12:48:05PM -0500, Bob Thibodeau wrote: I'm just coming into the thread, but if you had your initrd= in the main section of lilo.conf, try putting it in the image section of your Sid kernel. That way, no other kernel will try to use it. Where should I put the init image? On hda or hdc? (hdc has sid, hda has redhat, and my sidkernel is in hda) Thanks in advance, -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org - keyserverID=24DC49C6 - http://www.zeus.rug.ac.be Private mail with incorrect quoting behavior will remain unanswered University politics are vicious precisely because the stakes are so small. - Henry Kissinger (1923-)
Re: lilo problem - / problem
hi ya rudy if you use a precompiled kernel... you have to tell it where / is on the new machine... otherwise you do get those kernel panics and no init found - i always make a kernel on the target... and copy it around but if you copy that kernel to flippy... that floppy should boot your system w/ the correct distro/kernel dd if=/..kernel.. of=/dev/fd0 rdev /dev/fd0 /dev/hda1 or /dev/hdc1 if you want it to boot into /dev/hdc if the floppy tests works.. than (if it can be done), you'd need to rdev your kernel rdev /boot/kernel /dev/hdc1 ( donno if this works ) where /boot is the one on /dev/hda1 - recompiling a new kernel on hdc1 and copying to hda1 works to lilo it and boot it and get into hdc1 have fun alvin On Fri, 22 Feb 2002, Rudy Gevaert wrote: Hello, Due to some workload I've only had the time to look at this now. On Thu, Feb 21, 2002 at 05:12:12AM -0800, Alvin Oga wrote: hi ya if it hands on ramdisk... remove that initrd line... and/or make sure the file exists as typed Wel, I removed the initrd line from lilo.conf, and redhat boots fine, but when I try to boot Sid I get a kernel panic, no init found... try passing init= ...etc. This is my lilo.conf: [EMAIL PROTECTED] /root]# cat /etc/lilo.conf boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 linear default=nieuwekernel image=/boot/2.4.17 label=nieuwekernel read-only image=/boot/vmlinuz-2.2.19 label=DebianSid read-only root=/dev/hdc1 other=/dev/hda1 label=dos initrd is not needed if your kernel has all the hardware drivers needed to boot... So this explains why I get that error? Because it is still the standard kernel from Sid? for to install make, and want to install it if you're referring to redhats simple install.. - just boot the cdrom and tell it upgrade and it will go thru what you got ant ask you what else you want No, I'm referring to Debians install, when you can choosse: Simple or advanced install. ;) How do I get that screen back? Or, what packages do I have to install to get make etc? (I guess gcc ...?) rh is such a pita aint it??? Yes! But let me explain, when I got my new pc and started university I wanted GNU/Linux... and redhat was the only one I knew. After a couple of months I got to know Debian (they used it in my studentgroup (don't know the right translation...), and I wiped windows out at home and installed debian. On my new pc I had suffered 4 months to configure my dualhead that I didn't dare to install debian yet.. but now I bought a new hd; so the time has come to switch to debian :). Thanks for the help up till now, I hope you can help me with the rest :) Cheers, -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org - keyserverID=24DC49C6 - http://www.zeus.rug.ac.be Private mail with incorrect quoting behavior will remain unanswered While one person hesitates because he feels inferior, the other is busy making mistakes and becoming superior -- Henry C. Link
Re: lilo problem
hi ya rudy - first test that the sid kernel boots and oyu have sid running... by putting it onto floppy...and boot off floppy - sometimes it might not boot till you rdev the boot floppy ( the part i am wondering about for your kernel system - once you know sid boots and redhat also boots... than we can fix lilo ... - it doesnt matter where you put the kernel... it doesnt matter where boot=/dev/xxx references - lilo will warn you if you pick hdc instead of hda - it does matter that rh kernel can find /dev/hda1 it does matter that sid kernel can find /dev/hdc1 ( or wherever you have / partition for each distro ) - rdev is a way to force it easily on floppy.. ( to know that the kernel works fine as does the distro - i dont know if you can rdev a kernel file ( i think you can )... and if not.. youhave to make your own kernel on hdc1 and copy it to hda1 - you'd need initrd if the kernel doesnt have all its drivers for the hardware the kernel needs to read from since the kernel is on disks it does not yet know how to read -- catch-22 problem - scsi and usb-drives probably needs initrd until you've made your own kernel w/ all its drivers built in have fun lilo'ing alvin On Fri, 22 Feb 2002, Rudy Gevaert wrote: On Fri, Feb 22, 2002 at 12:48:05PM -0500, Bob Thibodeau wrote: I'm just coming into the thread, but if you had your initrd= in the main section of lilo.conf, try putting it in the image section of your Sid kernel. That way, no other kernel will try to use it. Where should I put the init image? On hda or hdc? (hdc has sid, hda has redhat, and my sidkernel is in hda)
lilo problem
Hello, I just installed a new hd (hdc), and put Sid on it. Because I have some bad experiences with lilo (always my mistake), I boot now from floppy to get to my Sid. This is what I have on hdc: /dev/hdc6 / /dev/hdc1 /boot /dev/hdc7 swap /dev/hdc2 /usr /dev/hdc3 /home /dev/hdc5 /var On hda I have a working redhat and winblows. I currently still use Redhat because I haven't fine tuned my Sid yet (still more problems left to fix). This is hda: /dev/hda6 / /dev/hda2 /boot /dev/hda1 /win /dev/hda5 swap Lilo is on the redhat system, on hda6! This is my lilo.conf: boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 linear default=nieuwekernel image=/boot/vmlinuz-2.2.14-5.0 label=linux initrd=/boot/initrd-2.2.14-5.0.img read-only root=/dev/hda6 image=/boot/nieuwek label=nieuwekernel read-only image=/boot/2.4.17 label=nnk read-only other=/dev/hda1 label=dos What should I add to my lilo.conf to get Sid booting? Thanks in advance, -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org - keyserverID=24DC49C6 - http://www.zeus.rug.ac.be Private mail with incorrect quoting behavior will remain unanswered It is unbecoming for young men to utter maxims. - Aristotle (384-322 B.C.)
Re: lilo problem
jo ua to get sid running ... for simplicity, just add these lines to lilo.conf on hda ( redhat's lilo ) # # boot sid instead # copy hdc:/boot/vmlinuz-2.4.xx to hda:/boot # image=/boot/vmlinuz-2.4.xxx label=DebianSid initrd=/boot/initrd-2.2.14-5.0.img read-only root=/dev/hdc1 have fun alvin On Thu, 21 Feb 2002, Rudy Gevaert wrote: Hello, I just installed a new hd (hdc), and put Sid on it. Because I have some bad experiences with lilo (always my mistake), I boot now from floppy to get to my Sid. This is what I have on hdc: /dev/hdc6 / /dev/hdc1 /boot /dev/hdc7 swap /dev/hdc2 /usr /dev/hdc3 /home /dev/hdc5 /var On hda I have a working redhat and winblows. I currently still use Redhat because I haven't fine tuned my Sid yet (still more problems left to fix). This is hda: /dev/hda6 / /dev/hda2 /boot /dev/hda1 /win /dev/hda5 swap Lilo is on the redhat system, on hda6! This is my lilo.conf: boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 linear you'd want to change liner to lba32 if it wasnt working right all the time default=nieuwekernel insert debian sid stanza here if you want debian to be deafult image=/boot/vmlinuz-2.2.14-5.0 label=linux initrd=/boot/initrd-2.2.14-5.0.img read-only root=/dev/hda6 image=/boot/nieuwek label=nieuwekernel read-only image=/boot/2.4.17 label=nnk read-only other=/dev/hda1 label=dos What should I add to my lilo.conf to get Sid booting?
Re: lilo problem
On Thu, Feb 21, 2002 at 04:08:43AM -0800, Alvin Oga wrote: jo ua to get sid running ... for simplicity, just add these lines to lilo.conf on hda ( redhat's lilo ) # # boot sid instead #copy hdc:/boot/vmlinuz-2.4.xx to hda:/boot # image=/boot/vmlinuz-2.4.xxx label=DebianSid initrd=/boot/initrd-2.2.14-5.0.img read-only root=/dev/hdc1 Ok; thanks for the tip, but when I do this I can boot into sid, but it hangs on Found Ramdisk at I previously had this problem (whan I accidentially erased my /boot on hda when installing Sid) when booting into Redhat 6.2 with the standard kernel. I fixed the problem by installing RedHat again (only updating) so I got a new /boot, but this didn't help and I finally installed a new kernel. So I think the problem now will be solved if I install a new kernel in Sid. So I tried that, but it can't find make :). Well I forgot to take the simple install (when installing) and I checked nothing. Does anyone know how I can get this install menu back ... so I can check simple... or what packages must I install to get make en stuff? Thanks in advance, -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.webworm.org - keyserverID=24DC49C6 - http://www.zeus.rug.ac.be Private mail with incorrect quoting behavior will remain unanswered The man who goes alone can start today; but he who travels with another must wait till that other is ready. - Henry David Thoreau (1817-1862)
Re: lilo problem
hi ya if it hands on ramdisk... remove that initrd line... and/or make sure the file exists as typed initrd is not needed if your kernel has all the hardware drivers needed to boot... i dont think a new kernel in sid ( hdc ) will solve anything for redhat stuff in hda... if you're referring to redhats simple install.. - just boot the cdrom and tell it upgrade and it will go thru what you got ant ask you what else you want rh is such a pita aint it??? my fav comment is its designed to generate $300/incident tech support phone calls... - especailly things that used to work gets broken... ( simple and everyday stuff.. apache, pop3, nfs, etc c ya alvin On Thu, 21 Feb 2002, Rudy Gevaert wrote: On Thu, Feb 21, 2002 at 04:08:43AM -0800, Alvin Oga wrote: jo ua to get sid running ... for simplicity, just add these lines to lilo.conf on hda ( redhat's lilo ) # # boot sid instead # copy hdc:/boot/vmlinuz-2.4.xx to hda:/boot # image=/boot/vmlinuz-2.4.xxx label=DebianSid initrd=/boot/initrd-2.2.14-5.0.img read-only root=/dev/hdc1 Ok; thanks for the tip, but when I do this I can boot into sid, but it hangs on Found Ramdisk at I previously had this problem (whan I accidentially erased my /boot on hda when installing Sid) when booting into Redhat 6.2 with the standard kernel. I fixed the problem by installing RedHat again (only updating) so I got a new /boot, but this didn't help and I finally installed a new kernel. So I think the problem now will be solved if I install a new kernel in Sid. So I tried that, but it can't find make :). Well I forgot to take the simple install (when installing) and I checked nothing. Does anyone know how I can get this install menu back ... so I can check simple... or what packages must I install to get make en stuff?
LILO problem on recent 2.4.x kernels
Recently I have been receiving a number of bug reports of LILO upgrades unexpectedly resulting in a non-bootable system. I have just received the following message which purports to explain it. If your system matches the below description (2.4.10 kernel with first partition being Ext2 and having /boot for booting with LILO) then I suggest doing the following: 1) Put LILO on hold if you haven't upgraded already. 2) Prepare an upgrade to 2.4.12 or a downgrade to 2.4.9 (kernels before 2.4.9 had security problems). 3) If you have already run lilo from kernel 2.4.10 or suspect that you have then either create a rescue floppy running a non 2.4.10 kernel or put your boot files on a different partition (one good option in such situations is to run swapoff and then mkfs your swap partition). 4) After booting from a better kernel immidiately run lilo to get a good boot map. Please note that I have not yet reproduced this on my own systems. However it may take some time for me to find a spare hard drive, format it as ext2, etc so I decided to warn you first. -- Forwarded Message -- Subject: Re: [reiserfs-list] Reiserfs-Fix in 2.4.12-ac2 Date: Tue, 23 Oct 2001 11:13:46 +0200 From: Jens Benecke [EMAIL PROTECTED] To: Russell Coker [EMAIL PROTECTED] LILO boot sector bug? Well, if you run 2.4.10 and your first partition contains the /boot stuff, and you run LILO, LILO's kernel position information will be overwritten with file system data the next time you write to that partition (i.e. _during_ LILOs run because it updates /boot/map). The fix is to move /boot, mount / read-only, run LILO, then reboot (with / still read-only). This only affects ext2 systems (wish I had updated to ReiserFS when I had the machine here). -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page Attachment: 1 Description: PGP signature
Re: LILO problem on recent 2.4.x kernels
Better not downgrade to 2.4.9, as it is also vulnerable. See below. Regards, Stefan Quoting Russell Coker [EMAIL PROTECTED] [23 Oct-01 19:08]: On Tue, 23 Oct 2001 15:23, you wrote: Quoting Russell Coker [EMAIL PROTECTED] [23 Oct-01 15:08]: 2) Prepare an upgrade to 2.4.12 or a downgrade to 2.4.9 (kernels before 2.4.9 had security problems). 2.4.9 is also vulnerable, according to http://www.securityfocus.com/cgi-bin/archive.pl?id=1mid=20011018173540.A66 [EMAIL PROTECTED]threads=1 There are two bugs present in Linux kernels 2.2.x, x=19 and 2.4.y, y=9. Damn. Please follow-up to my list posting to correct this (if you haven't already).
LILO problem on Woody
I see from the archives that there have been problems with LILO and Woody. Have they been resolved? I took my (text only) 2.2r3 + 2.4.5 upgrade system which worked quite happily and tried to upgrade to Woody. Using dselect failed (template parse errors) but using apt-get upgrade and then apt-get dist-upgrade seemed to work, BUT when I came to reboot it is as though the boot sector has been trashed. I can boot from floppy and the disk is fine in all other respects. There are no error messages if I simply run lilo but if I run lilo -v it does mention that /boot/boot.300 already exists, so no backup copy made. I think that LILO was upgraded as part of the woody upgrade, but I am not sure (is there a log kept somewhere?). LILO reports itself as being 21.7-5 built on 16th July at 15:55:37, which is very close to the time that boot-compat.b, boot-menu.b and boot-text.b were created, but I can not remember if they existed before the upgrade. boot.b is symlinked to boot-menu.b. Any ideas? begin:vcard n:Goodenough;David x-mozilla-html:FALSE org:D.G.A. ltd adr:;; version:2.1 email;internet:[EMAIL PROTECTED] x-mozilla-cpt:;0 fn:David Goodenough end:vcard
lilo problem
hello! i'm a fourth-yr comp. sci. student from the university of the phils. manila. i've just installed debian gnu/linux a month ago, and i'm very satisfied not to see another BSOD from windows again. After tinkering the pc, here are some of the stumbling blocks i encountered: 1.)i just upgraded (force-overwrite) libc6-2.1.3 and libdb2 that comes with the debian 2.2r3 with the testing packages of libc6-2.2.3 and libdb2-2.7. after that i recompiled kernel 2.4.7pre3. when i ran lilo, it flashed out a message open /vmlinuz - no such file or directory when i used whereis open - open was still there. I couldn't use lilo because of this. Then i made the mistake of uninstalling lilo, so when i rebooted the pc, LI instead of LILO: appeared (meaning LILO is damaged?). i'm triple-booting QNX4, Win98 and Debian GNU/Linux 2.2r3 on my system. i went to the point of ridding lilo from the mbr just to use an OS (Win98 then loadlin-ing the kernel). How do I fix this? 2.)Also, how do i install a kernel 2.4.x in potato? i hear that one needs to make kpkg the kernel source. can't i just copy the kernel image and install the sources (make bzImage; make modules; make modules_install) or do I really need to make kpkg the source just to make the system detect the modules? if so, how do i do it and what do i need? 3.)Do i need to upgrade pppd if i use kernel 2.4.x? wvdial won't connect - something like invalid argument reflects in the /var/logs/message file. what do i need to do? is there a better way to connect via dial-up than wvdial? if so, how? thank you, and god bless! Paolo Alexis D. Falcone University of the Philippines Manila __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
Re: lilo problem
hi, 1.)i just upgraded (force-overwrite) libc6-2.1.3 and libdb2 that comes with the debian 2.2r3 with the testing packages of libc6-2.2.3 and libdb2-2.7. after that i recompiled kernel 2.4.7pre3. when i ran lilo, it flashed out a message open /vmlinuz - no such file or directory when i used whereis open - open was still there. I couldn't use lilo because of this. Then i made the mistake of uninstalling lilo, so when i rebooted the pc, LI instead of LILO: appeared (meaning LILO is damaged?). i'm triple-booting QNX4, Win98 and Debian GNU/Linux 2.2r3 on my system. i went to the point of ridding lilo from the mbr just to use an OS (Win98 then loadlin-ing the kernel). How do I fix this? check the enteries of lilo.conf if there are pointing to the correct enteries and then reinstall lilo by running lilo at command line. 2.)Also, how do i install a kernel 2.4.x in potato? i hear that one needs to make kpkg the kernel source. can't i just copy the kernel image and install the sources (make bzImage; make modules; make modules_install) or do I really need to make kpkg the source just to make the system detect the modules? if so, how do i do it and what do i need? kernel-package provides a good way of compiling the kernel and building a deb file. of course you can go thru the make bzImage way. it is just that using make-kpkg is an easier way. it does the whole job for you. 3.)Do i need to upgrade pppd if i use kernel 2.4.x? wvdial won't connect - something like invalid argument reflects in the /var/logs/message file. what do i need to do? is there a better way to connect via dial-up than wvdial? if so, how? check the version requirement of pppd. the minimum requirement is 2.4.0 for a 2.4.x kernel. regards harsha
Re: lilo problem
On Sun, Jul 22, 2001 at 01:31:20AM -0700, Fallen Lord wrote:
1.)i just upgraded (force-overwrite) libc6-2.1.3 and
libdb2 that comes with the debian 2.2r3 with the
testing packages of libc6-2.2.3 and libdb2-2.7.
Be very careful with any of the --force options to dpkg, they're not
supposed to be needed, so if you use them, something is likely wrong
somewhere and you might be making it even worse only.
Use dselect for package management. Learn to understand the concepts
behind the debian package management system and you'll find that dselect
is a fine tool. Don't be scared by people who say that it is too hard
to use, they just don't understand the packaging system. If you don't
understand the packaging system, you're likely to nuke your system
somehow some day anyway.
after that i recompiled kernel 2.4.7pre3. when i ran
lilo, it flashed out a message open /vmlinuz - no
such file or directory when i used whereis open -
open was still there. I couldn't use lilo because of
Perhaps this was only an error message by lilo that the call to open
/vmlinuz failed (i.e. open returned with a failure). The open
that it complains about is probably not the open that you find when
you use which. Check out the differences between the open(1), the
open(2) and the fopen(3) manual pages.
If your /etc/lilo.conf lists an image with the name /vmlinuz, and
that file does not actually exist in your filesystem, lilo cannot
setup the boot block to point to a place on your disk where that file
is supposed to be (but isn't). If /vmlinuz is a symbolic link, eg.
to /boot/vmlinuz-2.2.19, then the file, that the link is pointing to,
must also exist.
Read the lilo.conf manual page to find how to setup the right boot image
for your system.
this. Then i made the mistake of uninstalling lilo, so
No need to remove lilo from your system, I would think? Unless you want
to switch to grub as your bootloader, but I don't expect so and it would
only create more confusion.
when i rebooted the pc, LI instead of LILO: appeared
(meaning LILO is damaged?). i'm triple-booting QNX4,
You rebooted the machine whilst it did not have a valid lilo bootloader.
H... One way of getting back in is to boot from a installation
floppy with the boot parameters:
rescue root=/dev/your debian root partition
Then login as root and reinstall lilo, fix the /etc/lilo.conf and this
time, run lilo -v -v (I always do that) so you can see more exactly what
is going on. After all, the results of little mistakes are relatively
large, so a little more attention is appropriate.
You also need to understand the difference between /sbin/lilo, which
is also called the boot block installer, and the little piece of code
called the boot block, which is installed by /sbin/lilo onto special
places on your harddisk. The boot block is what actually gets executed
by the bios when your pc boots and it in turn loads the linux kernel.
When /sbin/lilo is run, it updates the boot block's notion of where to
find the kernels listed in /etc/lilo.conf.
Win98 and Debian GNU/Linux 2.2r3 on my system. i went
to the point of ridding lilo from the mbr just to use
an OS (Win98 then loadlin-ing the kernel). How do I
fix this?
If you do a lot of rebooting and os switching, then loadlin.exe might not
be such a bad idea after all, as long as you are diligent in making sure
that a bootable kernel is always available as a file in the windows98
filesystem.
Use the debian rescue floppy to boot into your system and read the lilo
documentation (there's an awful lot of good details in /usr/doc/lilo if
you care) and fix the boot loader.
Alternatively, create a simple bootfloppy:
cat /vmlinuz /dev/fd0
rdev /dev/fd0 $( rdev | awk '{ print $1 }' )
Voila, you have a bootdisk that always works, if the disk is any good,
that is, and if you make it read-only. Make two if you want to be sure.
And make sure that /vmlinuz is indeed the kernel that you want to boot.
Use another filename if you like, there is nothing that says that your
kernel must always be named vmlinuz or be in places like / or /boot.
After all, if you cat it to a raw floppy, it doesn't have a name or a
place either, since there is no filesystem.
BTW, the rescue disk does have a FAT filesystem, so it can be read
by windows as well, and the linux kernel is named linux. Be careful
when you replace it, because it needs to be a kernel that can do special
tricks, called initrd, so the installer can read the basic programs it
needs from another file on the floppy. You do not need those for your
own simple bootfloppy created by cat'ting your current kernel to /dev/fd0.
2.)Also, how do i install a kernel 2.4.x in potato? i
hear that one needs to make kpkg the kernel source.
can't i just copy the kernel image and install the
sources (make bzImage; make modules; make
modules_install) or do I really need to make kpkg the
source just to make the system detect the modules? if
so, how do i do it and what do i
Re: lilo problem
Fallen Lord wrote: 3.)Do i need to upgrade pppd if i use kernel 2.4.x? wvdial won't connect - something like invalid argument reflects in the /var/logs/message file. what do i need to do? is there a better way to connect via dial-up than wvdial? if so, how? Check out the Debian Website. There is a link to Bunk's site. He has made packages for poato to run Kernel 2.4.x (it's not just pppd that should be upgradet). Follow the instruction and you can install Kernel 2.4.5 via apt-get. Frank
lilo problem after kernel install: LIL-
Hello all, I recently upgraded all packages necessary to install a 2.4.x kernel on my Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5 kernel I rebooted and was greeted with a screen reading only LIL-. I have a boot floppy made when I originally installed and was able to reboot the machine using that and re-ran lilo after editing lilo.conf to use the older (2.2.17) kernel, but this didn't fix the problem. I would just boot off of the floppy and be done with it but unfortunately the kernel on the floppy does not support my pcmcia ethernet adapter. Now I am in the unenviable position of running Win2k on an old laptop (painfully slow) so I can get a network connection. If anybody knows how to fix this problem I would appreciate the help. Here is some further information about the setup if any of it is useful. Dual Boot Windows 2000 Pro. - Debian GNU/Linux 2.2 Windows boot manager gets control first, hands it off to lilo if you choose Linux Linux boot device is /dev/hda2 -- Anthony Fairchild
Re: lilo problem after kernel install: LIL-
On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote: | Hello all, | | I recently upgraded all packages necessary to install a 2.4.x kernel on my | Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5 | kernel I rebooted and was greeted with a screen reading only LIL-. ... | If anybody knows how to fix this problem I would appreciate the help. Here is | some further information about the setup if any of it is useful. | | Dual Boot Windows 2000 Pro. - Debian GNU/Linux 2.2 I would highly recommend grub. I first tried it on a test machine at work that has Win2k and I was asked to install RH6.2 as dual-boot on it. I tried with lilo first, because it is default. The docs on linuxdoc.org indicate that chainloading windows from lilo is a bit complicated, in addition to the fact that RH was above the 1024 cylinder limit. I then tried grub, just for a change. It is ridiculously simple to chainload any other boot loader (including itself ;-)) and has no 1024 cylinder limit. (I have since heard that the 'lba32' option to lilo also removes this restriction) After that experience I tried grub at home (loadlin run from autoexec.bat even though Win98 was rarely booted anymore) and it worked great. Previosly lilo couldn't boot linux from /dev/hdc. HTH, -D
Re: lilo problem after kernel install: LIL-
On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote: Hello all, I recently upgraded all packages necessary to install a 2.4.x kernel on my Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5 kernel I rebooted and was greeted with a screen reading only LIL-. I have a boot floppy made when I originally installed and was able to reboot the machine using that and re-ran lilo after editing lilo.conf to use the older (2.2.17) kernel, but this didn't fix the problem. I would just boot off of the floppy and be done with it but unfortunately the kernel on the floppy does not support my pcmcia ethernet adapter. Now I am in the unenviable position of running Win2k on an old laptop (painfully slow) so I can get a network connection. If anybody knows how to fix this problem I would appreciate the help. Here is some further information about the setup if any of it is useful. Dual Boot Windows 2000 Pro. - Debian GNU/Linux 2.2 Windows boot manager gets control first, hands it off to lilo if you choose Linux Linux boot device is /dev/hda2 From /usr/share/doc/lilo/Manual.txt.gz LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. I'm hesitating a bit here because I haven't worked with Win2k yet but if this were a Win98 box I would try booting with a windows boot disk containing fdisk and run - fdisk /mbr which will rewrite the code for you're mbr. Then boot back into debian with your boot disk and rerun /sbin/lilo. If that doesn't work you could totally blow away your your boot-block with - dd if=/dev/zero of=/dev/hda bs=512 count=1 under debian. Then use fdisk /mbr again and then try installing lilo again. I want to stress I can't guarantee the results of this. Make sure you have a backup of you're info on your Windows side before trying. hth, kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
Re: lilo problem after kernel install: LIL-
On Mon, Jun 11, 2001 at 08:04:16PM -0500, ktb wrote: On Mon, Jun 11, 2001 at 04:54:04PM +, Anthony Fairchild wrote: Hello all, I recently upgraded all packages necessary to install a 2.4.x kernel on my Debian 2.2 laptop. After downloading, compiling, and installing the 2.4.5 kernel I rebooted and was greeted with a screen reading only LIL-. I have a boot floppy made when I originally installed and was able to reboot the machine using that and re-ran lilo after editing lilo.conf to use the older (2.2.17) kernel, but this didn't fix the problem. I would just boot off of the floppy and be done with it but unfortunately the kernel on the floppy does not support my pcmcia ethernet adapter. Now I am in the unenviable position of running Win2k on an old laptop (painfully slow) so I can get a network connection. If anybody knows how to fix this problem I would appreciate the help. Here is some further information about the setup if any of it is useful. Dual Boot Windows 2000 Pro. - Debian GNU/Linux 2.2 Windows boot manager gets control first, hands it off to lilo if you choose Linux Linux boot device is /dev/hda2 From /usr/share/doc/lilo/Manual.txt.gz LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. I'm hesitating a bit here because I haven't worked with Win2k yet but if this were a Win98 box I would try booting with a windows boot disk containing fdisk and run - fdisk /mbr which will rewrite the code for you're mbr. Then boot back into debian with your boot disk and rerun /sbin/lilo. If that doesn't work you could totally blow away your your boot-block with - dd if=/dev/zero of=/dev/hda bs=512 count=1 under debian. Then use fdisk /mbr again and then try installing lilo again. I want to append to this. If you completely blow away your boot-block - dd if=/dev/zero of=/dev/hda bs=512 count=1 you will have to repartition and format. Use only as a last resort. kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
weird lilo problem
i have encountered an odd lilo problem. i have a scsi HD (linux) and an IDE HD (win2k). i configure lilo, run lilo, and it reports no errors. reboot, and lilo hangs. unplug IDE drive, run lilo again, and it reports no errors. plug IDE drive back in, and lilo boots linux normally. in fact, i can even mount the IDE drive and read form it. so basically, i just have to unplug my ide drive each time i run lilo to keep things working. in the bios i can select to boot from scsi or IDE first, which is how i switch from linux to win2k. this seems like a rather odd bug, and it is frustrating because i would like to be able to boot win2k from the lilo prompt (currently i cant, because the idea drive must be disconnected when i run lilo). any ideas? jason [EMAIL PROTECTED] jason.pepas.com Mail2Web - Check your email from the web at http://www.mail2web.com/ .
Re: weird lilo problem
On Thu, May 24, 2001 at 03:15:08AM -0400, [EMAIL PROTECTED] wrote: i have encountered an odd lilo problem. i have a scsi HD (linux) and an IDE HD (win2k). i configure lilo, run lilo, and it reports no errors. reboot, and lilo hangs. unplug IDE drive, run lilo again, and it reports no errors. plug IDE drive back in, and lilo boots linux normally. in fact, i can even mount the IDE drive and read form it. so basically, i just have to unplug my ide drive each time i run lilo to keep things working. in the bios i can select to boot from scsi or IDE first, which is how i switch from linux to win2k. this seems like a rather odd bug, and it is frustrating because i would like to be able to boot win2k from the lilo prompt (currently i cant, because the idea drive must be disconnected when i run lilo). any ideas? Yeah, I was confused by this problem recently too. Except in my situation I had 2 ide drives but trying to do basically the same thing as you. What I needed to do was put the following into my lilo.conf file: drive=/dev/hdc bios=0x80 I think the first one was drive - not 100% sure and can't check from this computer. The bios line tells lilo to treat the 3rd ide drive (in this case) hdc as the boot one. hth Mark.
Re: weird lilo problem
Can you mail your /etc/lilo.conf? Once upon a time, [EMAIL PROTECTED] [EMAIL PROTECTED] found a keyboard. And typed: i have encountered an odd lilo problem. i have a scsi HD (linux) and an IDE HD (win2k). i configure lilo, run lilo, and it reports no errors. reboot, and lilo hangs. unplug IDE drive, run lilo again, and it reports no errors. plug IDE drive back in, and lilo boots linux normally. in fact, i can even mount the IDE drive and read form it. so basically, i just have to unplug my ide drive each time i run lilo to keep things working. in the bios i can select to boot from scsi or IDE first, which is how i switch from linux to win2k. this seems like a rather odd bug, and it is frustrating because i would like to be able to boot win2k from the lilo prompt (currently i cant, because the idea drive must be disconnected when i run lilo). any ideas? jason [EMAIL PROTECTED] jason.pepas.com Mail2Web - Check your email from the web at http://www.mail2web.com/ . -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -_-_-_-_End of Original Message-_-_-_-_-_-_-Know Gnu, Know Freedom_ -V.Suresh. Sureshvatusersdotsourceforgedotnet Http://www16.brinkster.com/vsuresh -- ---Powered by Debian Potato- 6:55pm up 4:42, 3 users, load average: 1.02, 1.27, 1.20 Created with Mutt, Sent by Exim - No Microsoft Products Used
Lilo problem after kernel reinstall: LIL-
Hey all... I recompiled my kernel 2.4.2, and did all of the System.map, vmlinuz copying, then ran LILO (which seemed quite happy). However, when I boot the computer, I get the following prompt, after which it freezes: LIL- Any ideas about this? I have more than one kernel on the system, so it seems to me that the problem is with the boot block LILO writes. Any quick and dirty means of getting around this, or am I condemned to rescue disks? Cheers Tiarnan __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Re: Lilo problem after kernel reinstall: LIL-
On Thu, Apr 26, 2001 at 03:14:16AM -0700, Tiarnan O'Corrain wrote: Hey all... I recompiled my kernel 2.4.2, and did all of the System.map, vmlinuz copying, then ran LILO (which seemed quite happy). However, when I boot the computer, I get the following prompt, after which it freezes: LIL- as /usr/share/doc/lilo/Manual.txt.gz states: LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. Well.. better boot up with your rescue disc/cd and check your lilo.conf again, rerun lilo with 'lilo -v -v' to see what's really happening and carefully check the output -- Mark Janssen Unix Consultant @ SyConOS IT E-mail: [EMAIL PROTECTED]GnuPG Key Id: 357D2178 http: markjanssen.homeip.net and markjanssen.[com|net|org|nl] Fax/VoiceMail: +31 84 8757555 Finger for GPG and GeekCode pgpEfTkuuvKy3.pgp Description: PGP signature
Re: Lilo problem after kernel reinstall: LIL-
Tiarnan O'Corrain wrote: Hey all... I recompiled my kernel 2.4.2, and did all of the System.map, vmlinuz copying, then ran LILO (which seemed quite happy). However, when I boot the computer, I get the following prompt, after which it freezes: LIL- I had a similar problem. Mine was due to a corrupt boot sector. I fixed it by running fdsk /mbr (or something like that I can't exactly recall) from a windoz startup disk. This will kill your boot sector and fix it. After that you need to reinstall lilo, edit lilo.conf, run lilo, and your golden. Andy
Re: Lilo problem after kernel reinstall: LIL-
On Thursday 26 April 2001 15:37, Andrew D Dixon wrote: Tiarnan O'Corrain wrote: Hey all... I recompiled my kernel 2.4.2, and did all of the System.map, vmlinuz copying, then ran LILO (which seemed quite happy). However, when I boot the computer, I get the following prompt, after which it freezes: LIL- I had a similar problem. Mine was due to a corrupt boot sector. I fixed it by running fdsk /mbr (or something like that I can't exactly recall) from a windoz startup disk. This will kill your boot sector and fix it. After that you need to reinstall lilo, edit lilo.conf, run lilo, and your golden. There should not be a need to reinstall lilo unless files in the lilo package (such as /boot/*.b) are corrupted. Editing lilo.conf should not be necessary if the only problem is a corrupted boot sector or file. -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
Re: Lilo problem after kernel reinstall: LIL-
On Thursday 26 April 2001 12:14, Tiarnan O'Corrain wrote: I recompiled my kernel 2.4.2, and did all of the System.map, vmlinuz copying, then ran LILO (which seemed quite happy). However, when I boot the computer, I get the following prompt, after which it freezes: LIL- Any ideas about this? I have more than one kernel on the system, so it seems to me that the problem is with the boot block LILO writes. Any quick and dirty means of getting around this, or am I condemned to rescue disks? From /usr/share/doc/lilo/Manual.gz: LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. If you just ran lilo before rebooting then the only way that /boot/map could have been corrupted is if you were running 2.4.1 (a file-system eating kernel). Another issue is geometry. But without knowing a lot more about your machine I can't advise on that. Probably the easiest thing to do is to use another machine to compile a kernel with the driver for your hard drive and do the following: cat vmlinuz /dev/fd0 rdev /dev/fd0 /dev/hda1 Replace /dev/hda1 with whatever your root device is. Then boot the machine from that disk and it'll hopefully work to a stage that allows you to fix the problem! -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
Re: Lilo problem after kernel reinstall: LIL- SOLVED
Thanks to all who replied. Here's what I did in the end (not having a rescue disk and being too ashamed to admit it)... Downloaded Tom's Root and Boot disk http://www.toms.net/rb/ Booted using tomsrtbt and since I had no concrete idea what the partition table looked like (head once more bowed in shame), I mounted each of the partitions under /mnt to find out which one was the root filesystem. Tried to run lilo (/mnt/sbin/lilo -v -v) but got a file not found error. Scratched head and looked confused. Rebooted the system, and passed root=/dev/hdax to tomsrtbt. It happily booted my system, apart from some errors which I assumed were due to the 2.0 series kernel (I run 2.4.2). Ran lilo very verbosely (lilo -v -v), saw it pass with no errors. Rebooted system. Joy! Many thanks to all those who made suggestions (which were no doubt extremely relevant to sensible people who keep rescue disks/cds, and know which partition is which on their system -- I shall endeavour to become one of them). Cheers Tiarnan __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
Re: Lilo problem after kernel reinstall: LIL- SOLVED
On Thu, Apr 26, 2001 at 07:59:15AM -0700, Tiarnan O'Corrain wrote: Thanks to all who replied. Here's what I did in the end (not having a rescue disk and being too ashamed to admit it)... You do not need rescue disk made during installation for this. If you have boot floppy for installation or CD-ROM, you can do what you did with debian bootCD/FD. (I am sure you have these.) At boot prompt of debian install CD/FD press tab to find choices, if its rescue then Boot: rescue root=/dev/hda1 or where ever your root partition. Good luck. Osamu -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://www.aokiconsulting.com/quick/+
Lilo problem
hi i have installed linux many times but there is just one problem that i am facing, that is writing lilo to the mbr. every time the installation is successful the lio prompt does not show up when the pc reboots , but it only comes up with the boot floppy. how can i write lilo to the mbr as i donot want to start with the boot floppy. __ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/
Re: Lilo problem
On Wed, 24 Jan 2001, Omar Shuja Siddiqui wrote: hi i have installed linux many times but there is just one problem that i am facing, that is writing lilo to the mbr. every time the installation is successful the lio prompt does not show up when the pc reboots , but it only comes up with the boot floppy. how can i write lilo to the mbr as i donot want to start with the boot floppy. __ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Make sure that your /boot is in the first 8.4gig of HD. This problem can be solved by moving the /boot partition (hard) or by simply upgrading to latest lilo, i.e. 21.* or newer. RAccess #geeks/irc.openprojects.net -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS GIT GP d- s+: a-- C+++ ULSB+++ P+ L+++ E+ W+++ N+ o K- w--- O- M-- V- PS+ PE Y+ PGP++ t++ 5-- X++ R* tv-- b+ DI+ D- G++ e h! r* !y+ --END GEEK CODE BLOCK--
Re: Lilo problem
On Wed, Jan 24, 2001 at 02:13:22PM -0800, Omar Shuja Siddiqui wrote: hi i have installed linux many times but there is just one problem that i am facing, that is writing lilo to the mbr. every time the installation is successful the lio prompt does not show up when the pc reboots , but it only comes up with the boot floppy. how can i write lilo to the mbr as i donot want to start with the boot floppy. Edit /etc/lilo.conf to reflect your setup and run /sbin/lilo.conf from the command line. You can use liloconfig to generate a /etc/lilo.conf file. Check out the man pages for more info. There is also good documentation including examples in the /usr/share/doc/lilo directory. hth, kent -- I'd really love ta wana help ya Flanders but... Homer Simpson
Woody Lilo problem
Hi, I just updated my debian woody (testing) installation with dselect and when it tries to install the new lilo-version, I get the following errors: Configuring packages ... /var/lib/debconf//config.1295: /usr/sbin/lilo_find_mbr: No such file or directory lilo failed to configure, with exit code 127 Use of uninitialized value at /var/lib/debconf//config.1295 line 64, STDIN chunk 3. Use of uninitialized value at /var/lib/debconf//config.1295 line 94, STDIN chunk 7. Is that a known problem or could it be that I have an SCSI-system? Is there any way of preventing lilo from being installed (I start with a boot-floppy - I know that is lame...). Thanx, Gery -- - Gernot Bauer, University of Linz, Austria [EMAIL PROTECTED] - The answer is yes, me.
Re: LILO Problem
On Thu, Jan 11, 2001 at 07:57:58PM -0800, Dale Morris wrote: Big learning curve here. Actually, it's not as bad it seems. :-) I just checked and it is on the secondary controller. What now? Good. Moving the drive should be fairly straightforward. Excuse me if it is a bit longish. Easier to give you detailed info now just in case you run into a problem. 1. You need to have working floppy boot/rescue disk. Debian's CD or root/rescue floppy set are ideal. Make sure they work as a rescue disk! Pass root=what_your_root_partition_is at the lilo prompt. 2. Backup /etc/fstab and /etc/lilo.conf 3. Edit (carefully) /etc/fstab. Change all references to hdcX (where X is the partition) to hdaX. No need to change the partition number. It *is* a good idea to write down what mount point each partiton goes with just in case. 4. Edit (carefully) /etc/lilo.conf. Change any references to hdc to hda. Same as above. DON'T run lilo! 5. Shutdown the machine, open it up and move the drive. 6. Make sure your BIOS sees the drive as master on the primary controller and will boot from it. 7. Boot with the Debian CD/rescue disk, passing it the root *Linux* partition. If it was /dev/hdc1 before the move, it is /dev/hda1 now, e.g. root=/dev/hda1 8. You should be back into your system. You should be able to run lilo and not have it complain. If it complains, fix /etc/lilo.conf as needed Reboot the machine to be sure all is good. That's it! Suppose step 8 didn't work. You could not get back into the machine. Maybe a typo in /etc/fstab. Go to Plan B, starting after #6 above... 9. Boot using the Debian CD/floppy set, choose new install. configure the keyboard. When you get to main menu STOP. (That's the one where you can partitiion/mount/format the hard drive, etc.) 10. Be careful here!!! You want to 'mount previously initialized partition'. Here's where the notes you made in #3 come in handy. You should only need to mount the root Linux partition. 11. Do an ALT-F2 to get a shell. Run 'mount'. Debian install mounts the partitions under /target as I recall, but double-check. 12. Do 'chroot /target' (or whatever mount point root is on). Doing 'ls' should show the root Linux partition of your hard drive. Use the '/bin/ae' editor to modify /etc/fstab and/or /etc/lilo.conf as needed. 13. Run '/sbin/lilo -v'. Fix any complaints. 14. Do an ALT-F1 to get back to the Debian install and choose 'reboot system'. The world should be happy again! With more experience, you can get away with using only Plan B. But play it safe the first time. Hopefully, you won't need Plan B. :-) thanks for your help you guys are great Glad to help out. Hey, and we didn't even ask for your credit card number first or put you on hold forever. :-) Good luck and let us know how you make out. bob -- bob billson email: [EMAIL PROTECTED]ham: kc2wz [EMAIL PROTECTED] Linux geek/) Níl aon tinteán mar do thinteán féin. beekeeper -8|||} --Dorothy\) Athbhliain faoi Shéan agus faoi Shona Dhuit!
Re: LILO Problem
Bob Billson wrote: On Fri, Jan 12, 2001 at 08:05:13AM +0700, Oki DZ wrote: well actually two questions. First, is it easy to pass parameters to the kernel like with lilo.conf's 'append='? Yes, just press c when grub's menu shows (spending time for the defined delay). Sorry, guess I didn't make myself clear. I should have said does grub have the equivalent of lilo's /etc/lilo.conf where an equivalent 'append=' line goes? That avoids have to press 'c' and entry to info. Yes, it's the /boot/grub/menu.lst. You can have: title mylinux kernel (hd0,0)/vmlinuz root=/dev/hda1 single other kernel params in the menu.lst. Well, at least that's what I think (I don't use Lilo that much). BTW, speaking about reiserfs, I just noticed that the Grub on stable Debian doesn't have support for reiserfs; Woody Grub has it. Oki
Re: LILO Problem
On Fri, Jan 12, 2001 at 04:05:49PM +0700, Oki DZ wrote: Sorry, guess I didn't make myself clear. I should have said does grub have the equivalent of lilo's /etc/lilo.conf where an equivalent 'append=' line goes? That avoids have to press 'c' and entry to info. Yes, it's the /boot/grub/menu.lst. Thanks! That answers my question. Looks like I'll have do so playing with grub! :-) bob -- bob billson email: [EMAIL PROTECTED]ham: kc2wz [EMAIL PROTECTED] Linux geek/) Níl aon tinteán mar do thinteán féin. beekeeper -8|||} --Dorothy\) Athbhliain faoi Shéan agus faoi Shona Dhuit!
Re: LILO Problem
To quote Dale Morris [EMAIL PROTECTED], # I'm having a problem with LILO. I have windows installed in the first # partition on my hd but somehow have wiped out the mbr. I've also tried to # compile the new 2.4 kernel, but am getting the following error: # cat bzImage /vmlinuz # cp /usr/src/linux/System.map / # if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi # Fatal: open /dev/hda1: Device not configured # make[1]: *** [zlilo] Error 1 # make[1]: Leaving directory /usr/src/linux/arch/i386/boot' # make: *** [bzlilo] Error 2 # # I've read the man page, but still am not having any luck. Thanks in advance. For some reason, lilo is looking in /dev/hda1 for something. My bet would be your lilo.conf has an other = /dev/hda1 line, and it can't use it any more for some reason. However, since you lilo.conf attachment didn't make it through, there's very little anyone can do :( Dave David Barclay Harris, Clan Barclay Aut agere, aut mori. (Either action, or death.)
Re: LILO Problem
duh.. I forgot to attach the lilo.conf file. I'll try again. When I try to boot from the hard drive, all that happens is I get a screenfull of zeros. here's how my hd is partitioned: hdc1=windows hdc3=/ hdc5=/home hdc6=/usr hdc4=swap thanks for replying. David B. Harris [EMAIL PROTECTED] wrote: To quote Dale Morris [EMAIL PROTECTED], # I'm having a problem with LILO. I have windows installed in the first # partition on my hd but somehow have wiped out the mbr. I've also tried to # compile the new 2.4 kernel, but am getting the following error: # cat bzImage /vmlinuz # cp /usr/src/linux/System.map / # if [ -x /sbin/lilo ]; then /sbin/lilo; else /etc/lilo/install; fi # Fatal: open /dev/hda1: Device not configured # make[1]: *** [zlilo] Error 1 # make[1]: Leaving directory /usr/src/linux/arch/i386/boot' # make: *** [bzlilo] Error 2 # # I've read the man page, but still am not having any luck. Thanks in advance. For some reason, lilo is looking in /dev/hda1 for something. My bet would be your lilo.conf has an other = /dev/hda1 line, and it can't use it any more for some reason. However, since you lilo.conf attachment didn't make it through, there's very little anyone can do :( Dave David Barclay Harris, Clan Barclay Aut agere, aut mori. (Either action, or death.) # Generated by liloconfig # Specifies the boot device boot=/dev/hdc1 # Specifies the device that should be mounted as root. # If the special name CURRENT is used, the root device is set to the # device on which the root file system is currently mounted. If the root # has been changed with -r , the respective device is used. If the # variable ROOT is omitted, the root device setting contained in the # kernel image is used. It can be changed with the rdev program. root=/dev/hdc3 # Enables 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. compact # Install the specified file as the new boot sector. # If INSTALL is omitted, /boot/boot.b is used as the default. install=/boot/boot.b # 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 # 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=normal image=/vmlinuz label=Linux read-only # If you have another OS on this machine (say DOS), # you can boot if by uncommenting the following lines # (Of course, change /dev/hda2 to wherever your DOS partition is.) other=/dev/hdc1 label=windows
Re: LILO Problem
On Thu, Jan 11, 2001 at 07:15:37AM -0800, Dale Morris wrote: here's how my hd is partitioned: hdc1=windows hdc3=/ hdc5=/home hdc6=/usr hdc4=swap Assuming you didn't make a typo and meant hdc not hda, what is on hda (master drive, primary controller)? My brother looking over my shoulder just pointed out something. Are primarily a Windows user? Are you thinking hdc = C:? If so, that is likely your problem. (My brother says don't feel bad. It took him a while get it right in his head.) Linux maps drives like this: MSDOSLinux ~~ C: hda(master, primary controller) D: hdb(secondary, primary controller) E: hdc(master, secondary controller) F: hdd(secondary, secondary controller) (and so on) If this is what you are doing, your drives are really partition like this: hda1=windows hda3=/ hda5=/home hda6=/usr hda4=swap If this is the case, make the appropriate changes in lilo.conf, i.e. change all hdc to hda and lilo should be happy. Let us know how you make out. bob -- bob billson email: [EMAIL PROTECTED]ham: kc2wz [EMAIL PROTECTED] Linux geek/) Níl aon tinteán mar do thinteán féin. beekeeper -8|||} --Dorothy\) Athbhliain faoi Shéan agus faoi Shona Dhuit!
Re: LILO Problem
Hi Bob, When I change hdc to hda and run /sbin/lilo I get the following message: lymond:/# /sbin/lilo Fatal: open /dev/hda1: Device not configured I am not sure now why these are listed as hdc, this install comes from libranet 1.8.2 (althought I don't know why that would make any difference). I'm confused, that's for sure. thanks Bob Billson [EMAIL PROTECTED] wrote: On Thu, Jan 11, 2001 at 07:15:37AM -0800, Dale Morris wrote: here's how my hd is partitioned: hdc1=windows hdc3=/ hdc5=/home hdc6=/usr hdc4=swap Assuming you didn't make a typo and meant hdc not hda, what is on hda (master drive, primary controller)? My brother looking over my shoulder just pointed out something. Are primarily a Windows user? Are you thinking hdc = C:? If so, that is likely your problem. (My brother says don't feel bad. It took him a while get it right in his head.) Linux maps drives like this: MSDOSLinux ~~ C: hda(master, primary controller) D: hdb(secondary, primary controller) E: hdc(master, secondary controller) F: hdd(secondary, secondary controller) (and so on) If this is what you are doing, your drives are really partition like this: hda1=windows hda3=/ hda5=/home hda6=/usr hda4=swap If this is the case, make the appropriate changes in lilo.conf, i.e. change all hdc to hda and lilo should be happy. Let us know how you make out. bob -- bob billson email: [EMAIL PROTECTED]ham: kc2wz [EMAIL PROTECTED] Linux geek/) Níl aon tinteán mar do thinteán féin. beekeeper -8|||} --Dorothy\) Athbhliain faoi Shéan agus faoi Shona Dhuit! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- If you only have a hammer, you tend to see every problem as a nail. -- Maslow
Re: LILO Problem
On Thu, Jan 11, 2001 at 07:55:56AM -0800, Dale Morris wrote: Hi Dale... I forgot to ask how many drives are in your machine? Partition check: hdc: hdc1 hdc2 hdc5 hdc6 hdc3 hdc4 This it the only drive the kernel finds when booting? Seems like it. The kernel should report all IDE devices (hard/CD drives, tape drives, etc.) it finds. From the looks of it, you have only one hard drive which set to be master and plugged into the secondary controller. Does your BIOS agree with this? You need at least one drive which is master on the primary controller. Your BIOS might allow you to boot from any drive or auto-detect any single drive and say Guess I'll use this. I don't know. So before you go any further...how many drive does your machine have? If just this one, where does your BIOS say it is. DON'T move the drive around yet! If your /etc/fstab isn't right, you won't be able to reboot! bob -- bob billson email: [EMAIL PROTECTED]ham: kc2wz [EMAIL PROTECTED] Linux geek/) Níl aon tinteán mar do thinteán féin. beekeeper -8|||} --Dorothy\) Athbhliain faoi Shéan agus faoi Shona Dhuit!
Re: LILO Problem
On Thu, Jan 11, 2001 at 10:44:20AM -0500, Bob Billson wrote: | Linux maps drives like this: |MSDOSLinux |~~ | C: hda(master, primary controller) | D: hdb(secondary, primary controller) | E: hdc(master, secondary controller) | F: hdd(secondary, secondary controller) | (and so on) | Close but not exactly. In MSDOS/Windows C:, D:, etc refer to partitions. This may or may not coincide with the physical drives. Also, in Linux, hda, hdb, etc refer to the entire drive rather than any single partition. Take for example a system with 2 drives on the primary conroller with 2 partitions each (all vfat). The mapping would be: C: hda1 D: hda2 E: hdb1 F: hdb2 Now suppose you have the same 2 drives, but now 2 partitions aren't vfat (say ext2 instead). C: hda1 D: hdb2 Windows doesn't label the other partitions since it doesn't know about them. | If this is what you are doing, your drives are really partition like this: |hda1=windows |hda3=/ |hda5=/home |hda6=/usr |hda4=swap In this setup, if I assume that all Linux partitions are ext2, then in MSDOS you have C: only. No other drives (for harddrive, CD comes after last HD). Linux uses different letters for different drive types. A: usually refers to /dev/fd0. SCSI drives are something like /dev/sd0 (but I don't have SCSI so I probably don't have it quite right) This is just to clear up a possible misunderstanding. HTH, -D
Re: LILO Problem
On Thu, 11 Jan 2001 12:44:18 EST, D-Man writes: C: hda1 D: hda2 E: hdb1 F: hdb2 DOS values primary partitions higher than everything else, so that would be: C: hda1 D: hdb1 E: hda2 F: hdb2 eg when you have 3 partitions per drive: C: hda1 D: hdb1 E: hda2 F: hda3 G: hdb2 H: hdb3 just to be picky ;) rw -- / Ing. Robert Waldner | Network Engineer | T: +43 1 89933 F: x533 \ \ [EMAIL PROTECTED] |KPNQwest/AT | Diefenbachg. 35, A-1150 /
