Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
On Mon, 2023-11-20 at 11:21 +0100, to...@tuxteam.de wrote: > (and oh, it hasn't been mentioned: make super-sure some smart and > overly helpful automounter has got hold of the USB). That's a good point. I tend to use an Ubuntu live image to do things like cloning my main disk, and I've wasted quite a few hours after not noticing it's auto-mounting the disk I'm copying too and so trashing my clone. (I find out the copy is bad when doing a binary compare after the multi-hour copying is done.) -- Tixy
Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
On Mon, Nov 20, 2023 at 11:27:45AM +0100, Thomas Schmitt wrote: [...] > to...@tuxteam.de wrote: [...] > > all blocks of the block device get overwritten, > > Not all. Only as far as the new image reaches. That's how the GPT backup > can survive (xorriso-dd-target would explicitely overwrite the last block > by zeros). > EFI firmwares are not known to react on GPT backups, although this cannot > be ruled out completely. Indeed, thanks for the correction :-) Cheers -- t "all generalizations suck" signature.asc Description: PGP signature
Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
Hi, Zenaan Harkness wrote: > > > all of the grub menu options (Graphical > > > install, Graphical expert install, Expert install, etc) give 2 errors: > > > 1) "..invalid buffer alignment... " with some long number beginning with > > > minus. > > > 2) kernel fail to load error, presumably due to error 1 Before discussing the tanget about copying bootable ISOs to USB stick: I suspect that something is wrong with the software in the ISO or with the hardware or with the involved firmware. The mailing list for such problems would be debian...@lists.debian.org but some maintainers of debian-cd are subscribed to debian-user, too. Tom Furie wrote: > > You can't just copy the iso to the stick and get it to boot. to...@tuxteam.de wrote: > Actually... if you copy to the whole device (not to a partition), as > OP seems to have done, it should work. Indeed. The only pitfall would be a GPT backup block at the end of the device's writable capacity. Some software could take it as indication that a clueless user damaged the GPT. Perky software might try to re-create the old GPT and thus hide the EFI partiton of the ISO. But since Zenaan Harkness reports GRUB to have started and offering the expected installation menu, it's improbable that such a mishap occured. > all blocks of the block device get overwritten, Not all. Only as far as the new image reaches. That's how the GPT backup can survive (xorriso-dd-target would explicitely overwrite the last block by zeros). EFI firmwares are not known to react on GPT backups, although this cannot be ruled out completely. Have a nice day :) Thomas
Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
On Mon, Nov 20, 2023 at 11:17:15AM +0100, to...@tuxteam.de wrote: [...] > For reference, what I do is > > sudo dd if=image.file of=/dev/sdX bs=1M oflag=sync status=progress (and oh, it hasn't been mentioned: make super-sure some smart and overly helpful automounter has got hold of the USB). Cheers -- t signature.asc Description: PGP signature
Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
On Mon, Nov 20, 2023 at 09:13:01PM +1100, Zenaan Harkness wrote: > On Monday, November 20, 2023, wrote: > > On Mon, Nov 20, 2023 at 08:59:02AM +, Tom Furie wrote: > >> Zenaan Harkness writes: > >> > >> > Attempting a fresh Debian stable install with > >> > debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp > >> > deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the > >> > >> You can't just copy the iso to the stick and get it to boot. > > > > Actually... if you copy to the whole device (not to a partition), as > ... > > Thank you both. I tried dd first, then cp, then ubuntu-disk-creator (?) -- > then I tried a different usb stick. For reference, what I do is sudo dd if=image.file of=/dev/sdX bs=1M oflag=sync status=progress Cheers -- t signature.asc Description: PGP signature
Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
On Monday, November 20, 2023, wrote: > On Mon, Nov 20, 2023 at 08:59:02AM +, Tom Furie wrote: >> Zenaan Harkness writes: >> >> > Attempting a fresh Debian stable install with >> > debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp >> > deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the >> >> You can't just copy the iso to the stick and get it to boot. > > Actually... if you copy to the whole device (not to a partition), as ... Thank you both. I tried dd first, then cp, then ubuntu-disk-creator (?) -- then I tried a different usb stick. Used that old stick many times and never had a problem before now... Thanks heaps, I'm on track again now. (Last night ubuntu snapd would not start, so ffox, chrome, blender, nothing worked. apt update, snap refresh, reboot. Had to wait till the bug got fixed in the repos today! That was the straw that broke this camel's back... returning to debian)
Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
On Mon, Nov 20, 2023 at 08:59:02AM +, Tom Furie wrote: > Zenaan Harkness writes: > > > Attempting a fresh Debian stable install with > > debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp > > deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the > > You can't just copy the iso to the stick and get it to boot. Actually... if you copy to the whole device (not to a partition), as OP seems to have done, it should work. The only advantage of dd over cp is that you have more control over the buffer cache (oflag=sync). > This stick > must have already had an image written to it, the leftovers of which is > getting as far as GRUB. ...no: all blocks of the block device get overwritten, including the boot loader. > I noticed you posted a follow-up saying you're on Ubuntu - in which case > you should be able to use dd to write the image to the stick. Cp should be the same than dd; with dd you can control block size (with sticks, my experience is that bs=1M is much faster than the default of 512), turn off buffer cache (oflag=sync), so no more waiting for a sync to come back without knowing how long it's going to take) and a progress indicator (status=progress), which is nice. The result should be the same (if you wait for sync to finish its job, that is). Cheers -- t signature.asc Description: PGP signature
Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
Zenaan Harkness writes: > Attempting a fresh Debian stable install with > debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp > deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the You can't just copy the iso to the stick and get it to boot. This stick must have already had an image written to it, the leftovers of which is getting as far as GRUB. I noticed you posted a follow-up saying you're on Ubuntu - in which case you should be able to use dd to write the image to the stick. Cheers, Tom
Re: debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
In case it's useful, my laptop is currently running Ubuntu - I'm wondering if it's possible to do some sort of chroot from Ubuntu into the USB stick, so that I can format the laptop's SSD and begin the install process that way? Surely that has been thought of before? (That said, I ought ensure I can boot the USB stick, so that I can do a rescue install if needed for any fat finger reason...) I notice the package debian-installer-launcher - should I be able to use that, with the debian netinst image, and by using that, can I get a "clean" install i.e format the laptop's SSD? On 11/20/23, Zenaan Harkness wrote: > Attempting a fresh Debian stable install with > debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp > deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the > grub graphical screen, but all of the grub menu options (Graphical > install, Graphical expert install, Expert install, etc) give 2 errors: > > 1) "..invalid buffer alignment... " with some long number beginning with > minus. > 2) kernel fail to load error, presumably due to error 1 > > Any ideas of how I can boot this usb stick and install debian? > > I'm on a laptop... >
debian-12.2.0-amd64-netinst.iso usb grub boot error "invalid buffer alignment"
Attempting a fresh Debian stable install with debian-12.2.0-amd64-netinst.iso (latest default amd64 boot image), `cp deiban-...iso /dev/sdX; sync`, and rebooted to the usb stick with the grub graphical screen, but all of the grub menu options (Graphical install, Graphical expert install, Expert install, etc) give 2 errors: 1) "..invalid buffer alignment... " with some long number beginning with minus. 2) kernel fail to load error, presumably due to error 1 Any ideas of how I can boot this usb stick and install debian? I'm on a laptop...
Kerberos boot error - no log file
Anyone knows where this kerberos detailed log might be. I can't find it. Failed to start Kerberos 5 Key Distribution Center. See 'systemctl status krb5-kdc.service' for details. I found this on the boot.log And the following somewhere else: Mar 8 11:04:35 G0 systemd[1]: Starting Kerberos 5 Key Distribution Center... Mar 8 11:04:36 G0 krb5kdc[493]: krb5kdc: cannot initialize realm ATHENA.MIT.EDU - see log file for details Mar 8 11:04:36 G0 systemd[1]: krb5-kdc.service: Control process exited, code=exited status=1 Mar 8 11:04:36 G0 systemd[1]: Failed to start Kerberos 5 Key Distribution Center. Mar 8 11:04:36 G0 systemd[1]: krb5-kdc.service: Unit entered failed state. Mar 8 11:04:36 G0 systemd[1]: krb5-kdc.service: Failed with result 'exit-code'. -- "The most violent element in society is ignorance" rEG
Re: Boot Error on new PowerPC Mac Mini Installation
On 24/07/15 12:24 PM, Nathaniel Nelson wrote: Hello! I hope this is the proper way to seek Debian support, and that I'm not making a mistake/emailing the wrong list/whatever. I've never used Debian before, and I'm trying to install it on an old Mac Mini with a PowerPC G4 processor. I downloaded the PowerPC iso file (debian-8.1.0-powerpc-netinst.iso) and burned it to an empty CD. I was able to successfully navigate the installation process. A couple points of interest: * I chose to use the entire available hard drive space and set up LVM (unencrypted). So I wiped Mac OS and all my old files from the computer. * I chose to use a single partition (the recommended/default choice) and after writing partition changes to the hard drive I received a warning that Yaboot would need its own partition. It asked if I wanted to return to the menu, so I did, assuming I would be able to make this change after reversing the changes (as there was a menu option to do so). However the "reverse changes" button seemed to do nothing, and I couldn't return to an earlier step to specify different partition settings, so I simply continued and wrote the changes again. (Probably should have read the manual before starting... sorry) I'm not sure what size the HD is but I'm assuming it's small by today's standards. Fortunately yaboot doesn't seem to need much space. From a google search I came up with: #type name length base ( size ) system /dev/sda1 Apple_partition_map Apple 63 @ 1 ( 31.5k) Partition map /dev/sda2 Apple_Bootstrap bootstrap 1600 @ 64 (800.0k) NewWorld bootblock /dev/sda3 Apple_UNIX_SVR2 myLinux 85852160 @ 1664 ( 40.9G) Linux native /dev/sda4 Apple_UNIX_SVR2 swap 8000820 @ 202238668 ( 3.8G) Linux swap * At the end I was prompted to choose a partition for installing Yaboot. Although I had chosen to create only one partition, it offered me two choices: sda2 and sba1 (IIRC). Not knowing the difference I chose sda2, the first one from the list, and installation completed and the computer began to boot in Debian. The yaboot boot log displays, with a notable error flashing by that I paraphrase here: [FAILED] Failed to load Linux Kernel Modules Probably couldn't install past yaboot due to insufficient space. It looks like Apple uses a partition (sda1) for its partition map, so sda2 should only be large enough to hold yaboot and you should install to sda3. Swap partitions are optional. You can always create a swap file later instead of a partition. This is easier to resize than a swap partition. No other failures appear in the log. After everything finishes and the screen goes black, instead of a login screen, I get this message fullscreen: "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." First I assumed this was due to a mistake when I chose to install Yaboot in sda2, so I ran a full installation again from the CD. Everything went the same, however there was no prompt to choose a partition and pick sba1 instead. And after the install finished, I got the same error message. Googling, I read that I could open a terminal from this error window with Ctrl+Alt+F1. This works, and then I read that I should log in as root and run the command startx. And that the error should be fixed by installing x-window-system if the startx command isn't found. However, the startx command *is* found, xorg is already installed, and when it runs, this again triggers the fullscreen "Oh no!" warning. I read that the installer isn't meant to install on top of another full installation, and that most problems such as this can be fixed without a full reinstall, so I haven't made a third attempt at reinstallation. What else could potentially be the issue here? The potential issue is that the system could have conflicting settings. If you have separate / and /home partitions, you can always reformat / and keep your current /home. With smaller drives however you can run out of space in one or the other fairly easily. My advice is not to worry about it. If your drive is only 50G or so, don't use a separate /home partition. If you've got 100G or more, then create a / with about 20G - 30G and leave the rest for /home. Thanks for any help. I can also supply more logs if you direct me to which ones might be helpful. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55b3a283.60...@torfree.net
Re: Boot Error on new PowerPC Mac Mini Installation
Should have re-read before I posted. On Sat, Jul 25, 2015 at 1:36 PM, Joel Rees wrote: > [...] but I've generally had the best success using the > Mac OS 10 partitioning tool to set up the three Mac OS style > partitions I use for debian, one for yaboot, one for the root > partition, and one for all the LVM stuff. Call that, not three partitions, but one partition and an unpartitioned region. I was trying to send you down two different roads at once. Sorry about that. :-( > [...] -- Joel Rees Be careful when you look at conspiracy. Arm yourself with knowledge of yourself, as well: http://reiisi.blogspot.jp/2011/10/conspiracy-theories.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAAr43iNj8NqfaeC3KAD0JVFQd=pwH-=y5wrzzj+kjpfiedw...@mail.gmail.com
Re: Boot Error on new PowerPC Mac Mini Installation
2015/07/25 1:42 "Nathaniel Nelson" : > > Hello! I hope this is the proper way to seek Debian support, and that I'm not > making a mistake/emailing the wrong list/whatever. > There is a better list. I've cross-posted, but I haven't set the reply header. > I've never used Debian before, and I'm trying to install it on an old Mac > Mini with a PowerPC G4 processor. I'd suggest that you not do that, but I've been there, done that, so it would be a bit hypocritical of me to do so. If you have a spare AMD64 or x86 box, you'll find the road a little smoother to play with debian on either of those first. But it isn't an absolute requirement. > I downloaded the PowerPC iso file (debian-8.1.0-powerpc-netinst.iso) and > burned it to an empty CD. I was able to successfully navigate the > installation process. A couple points of interest: > > * I chose to use the entire available hard drive space and set up LVM > (unencrypted). So I wiped Mac OS and all my old files from the computer. > I have often found myself needing to boot Mac OS 10 for odd reasons. If you have the disk space, I'd recommend leaving a Mac OS 10 install of about 6 to 20 GB. > * I chose to use a single partition (the recommended/default choice) and > after writing partition changes to the hard drive I received a warning that > Yaboot would need its own partition. > I don't know about the "default/recommended" partition scheme on Jessie, but I can't imagine single partition ever being a good idea on a powerPC Mac. Unless you really like using openfirmware commands to set the boot partition. Unless things have drastically changed, yaboot, needs its own very small partition. Small can be a problem, too. Incidentally, I don't know about Jessie, but I've generally had the best success using the Mac OS 10 partitioning tool to set up the three Mac OS style partitions I use for debian, one for yaboot, one for the root partition, and one for all the LVM stuff. > [... stuff that you should forget for the time being.] > > I read that the installer isn't meant to install on top of another full > installation, and that most problems such as this can be fixed without a full > reinstall, so I haven't made a third attempt at reinstallation. What else > could potentially be the issue here? > Don't ask that question now. > Thanks for any help. I can also supply more logs if you direct me to which > ones might be helpful. Wipe it with the Mac OS 10 installer. Use the Mac OS 10 install to cut a partition for Mac OS 10, and leave the rest unformatted. If you have a 30G disk, cut the Mac OS 10 partition at about 6G. if you have 60G or more, give the Mac OS 10 partition 10G. Again, leave the rest unformatted. Make sure Mac OS 10 still boots. Boot the Debian installer, do not let it autoformat the whole disk, do not let it install single partition. Use the custom partition option, have it make a partition for yaboot. It should get the size right if you tell it to make the partition for yaboot. Then have it make a partition for root, in the range of 8G or more. Partition the rest to LVM, and use your favorite partition scheme for that. But be aware that a separate /usr partition is currently militated against, so don't do that. Not this time. Install, get it to boot, use it for a while, get used to the weirdness of dual-booting with Mac OS 10, then re-install it for real. You'll have a better idea what to the third time around. Joel Rees Computer memory is just fancy paper, CPUs just fancy pens. All is a stream of text flowing from the past into the future. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAAr43iPwG_E8wd5Of+hrKuK-FuwsZ=SzZqTsT7mxjWRGs=u...@mail.gmail.com
Boot Error on new PowerPC Mac Mini Installation
Hello! I hope this is the proper way to seek Debian support, and that I'm not making a mistake/emailing the wrong list/whatever. I've never used Debian before, and I'm trying to install it on an old Mac Mini with a PowerPC G4 processor. I downloaded the PowerPC iso file (debian-8.1.0-powerpc-netinst.iso) and burned it to an empty CD. I was able to successfully navigate the installation process. A couple points of interest: * I chose to use the entire available hard drive space and set up LVM (unencrypted). So I wiped Mac OS and all my old files from the computer. * I chose to use a single partition (the recommended/default choice) and after writing partition changes to the hard drive I received a warning that Yaboot would need its own partition. It asked if I wanted to return to the menu, so I did, assuming I would be able to make this change after reversing the changes (as there was a menu option to do so). However the "reverse changes" button seemed to do nothing, and I couldn't return to an earlier step to specify different partition settings, so I simply continued and wrote the changes again. (Probably should have read the manual before starting... sorry) * At the end I was prompted to choose a partition for installing Yaboot. Although I had chosen to create only one partition, it offered me two choices: sda2 and sba1 (IIRC). Not knowing the difference I chose sda2, the first one from the list, and installation completed and the computer began to boot in Debian. The yaboot boot log displays, with a notable error flashing by that I paraphrase here: [FAILED] Failed to load Linux Kernel Modules No other failures appear in the log. After everything finishes and the screen goes black, instead of a login screen, I get this message fullscreen: "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." First I assumed this was due to a mistake when I chose to install Yaboot in sda2, so I ran a full installation again from the CD. Everything went the same, however there was no prompt to choose a partition and pick sba1 instead. And after the install finished, I got the same error message. Googling, I read that I could open a terminal from this error window with Ctrl+Alt+F1. This works, and then I read that I should log in as root and run the command startx. And that the error should be fixed by installing x-window-system if the startx command isn't found. However, the startx command *is* found, xorg is already installed, and when it runs, this again triggers the fullscreen "Oh no!" warning. I read that the installer isn't meant to install on top of another full installation, and that most problems such as this can be fixed without a full reinstall, so I haven't made a third attempt at reinstallation. What else could potentially be the issue here? Thanks for any help. I can also supply more logs if you direct me to which ones might be helpful.
Re: puzzling boot error
On Fri, 6 Jun 2014 13:55:23 -0600 Glenn English wrote: > I get "ERST:Failed to get Error Log Address Range" when I boot the > new server I'm preparing. This recent thread: https://lists.debian.org/debian-kernel/2014/05/msg00213.html suggest that the Debian kernel's involved. So, I would say, either try with a newer installation iso or an older one. Some others mention to check the BIOS is up to date and to use GPT if some partition(s) are > 2.2 TB. -- bleiziruz: A computer without Windows it's like a chocolate cake without mustard… -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140607012954.74eeaa3b@anubis.defcon1
puzzling boot error
I get "ERST:Failed to get Error Log Address Range" when I boot the new server I'm preparing. There is very little on the net about it -- one that almost says not to worry about and some others that imply there might be an incorrectly configured kernel (this is an untouched Wheezy kernel, updated this morning and the update does the same as the original). Can anyone tell me what might be going on? -- Glenn English -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/6de432ae-9737-49a8-86bf-5bf5a4541...@slsware.net
[solved] RE: I have a boot error. concerning not finding acl.end
From: billnick...@hotmail.com To: t@gmx.de; debian-user@lists.debian.org Subject: RE: I have a boot error. concerning not finding acl.end Date: Sat, 23 Oct 2010 18:55:00 -0500 Thanks, a perfect fix. > To: debian-user@lists.debian.org > From: t@gmx.de > Subject: Re: I have a boot error. concerning not finding acl.end > Date: Sat, 23 Oct 2010 21:58:23 +0200 > > Bill Nickels wrote the following on 23.10.2010 21:36 > > > The system continues to boot without errors and no indications of problems. > > Linux debianhp 2.6.32-5-amd64. Squeeze.dmesg doesn't reference it > > http://bugs.debian.org/600446 > > cheers > > -- > bye Thilo > > 4096R/0xC70B1A8F > 721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F > > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/i9veov$sn...@dough.gmane.org >
RE: I have a boot error. concerning not finding acl.end
Thanks, a perfect fix. > To: debian-user@lists.debian.org > From: t@gmx.de > Subject: Re: I have a boot error. concerning not finding acl.end > Date: Sat, 23 Oct 2010 21:58:23 +0200 > > Bill Nickels wrote the following on 23.10.2010 21:36 > > > The system continues to boot without errors and no indications of problems. > > Linux debianhp 2.6.32-5-amd64. Squeeze.dmesg doesn't reference it > > http://bugs.debian.org/600446 > > cheers > > -- > bye Thilo > > 4096R/0xC70B1A8F > 721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F > > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/i9veov$sn...@dough.gmane.org >
Re: I have a boot error. concerning not finding acl.end
Bill Nickels wrote the following on 23.10.2010 21:36 > The system continues to boot without errors and no indications of problems. > Linux debianhp 2.6.32-5-amd64. Squeeze.dmesg doesn't reference it http://bugs.debian.org/600446 cheers -- bye Thilo 4096R/0xC70B1A8F 721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/i9veov$sn...@dough.gmane.org
I have a boot error. concerning not finding acl.end
The system continues to boot without errors and no indications of problems. Linux debianhp 2.6.32-5-amd64. Squeeze.dmesg doesn't reference it
Re: Grub Boot Error on Lenny
On Feb 8, 2008 5:27 PM, Michael D. Norwick <[EMAIL PROTECTED]> wrote: > Raj Kiran Grandhi wrote: > > Schiz0 wrote: > >> I have Lenny running on a laptop. I selected to use grub version 2 > >> when it prompted me (back when I first installed grub). > >> > >> I just now updated my apt sources and ran a upgrade. It upgraded the > >> grub package, and I rebooted. > >> > >> Now, after the bios tests, the text "Grub loading kernel" flashes up > >> for about a second. Then I get an endless flood of the text "invalid > >> command" or something like that (it scrolls by way too fast). > >> > >> How can I fix this? > > > > Please post your menu.lst file > > > > Alternatively, replace the menu.lst file with an example file after > > making the appropriate changes specific to your system. > Please see the post I just made entitled "Re: Success: Grub2 on Dell > Optiplex". > > #>/etc/grub-install /dev/hda > and > #>/etc/update-grub > > from a Debian boot CD. > > Michael > That fixed the problem. Thank you for your time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Grub Boot Error on Lenny
Raj Kiran Grandhi wrote: Schiz0 wrote: I have Lenny running on a laptop. I selected to use grub version 2 when it prompted me (back when I first installed grub). I just now updated my apt sources and ran a upgrade. It upgraded the grub package, and I rebooted. Now, after the bios tests, the text "Grub loading kernel" flashes up for about a second. Then I get an endless flood of the text "invalid command" or something like that (it scrolls by way too fast). How can I fix this? Please post your menu.lst file Alternatively, replace the menu.lst file with an example file after making the appropriate changes specific to your system. Please see the post I just made entitled "Re: Success: Grub2 on Dell Optiplex". #>/etc/grub-install /dev/hda and #>/etc/update-grub from a Debian boot CD. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Grub Boot Error on Lenny
I observed the same here Schiz0 wrote: I have Lenny running on a laptop. I selected to use grub version 2 when it prompted me (back when I first installed grub). I just now updated my apt sources and ran a upgrade. It upgraded the grub package, and I rebooted. Now, after the bios tests, the text "Grub loading kernel" flashes up for about a second. Then I get an endless flood of the text "invalid command" or something like that (it scrolls by way too fast). How can I fix this? Thanks for your time, ~Steve -- Jerome BENOIT jgmbenoit_at_mailsnare_dot_net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Grub Boot Error on Lenny
Schiz0 wrote: I have Lenny running on a laptop. I selected to use grub version 2 when it prompted me (back when I first installed grub). I just now updated my apt sources and ran a upgrade. It upgraded the grub package, and I rebooted. Now, after the bios tests, the text "Grub loading kernel" flashes up for about a second. Then I get an endless flood of the text "invalid command" or something like that (it scrolls by way too fast). How can I fix this? Please post your menu.lst file Alternatively, replace the menu.lst file with an example file after making the appropriate changes specific to your system. -- Raj Kiran Grandhi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Grub Boot Error on Lenny
I have Lenny running on a laptop. I selected to use grub version 2 when it prompted me (back when I first installed grub). I just now updated my apt sources and ran a upgrade. It upgraded the grub package, and I rebooted. Now, after the bios tests, the text "Grub loading kernel" flashes up for about a second. Then I get an endless flood of the text "invalid command" or something like that (it scrolls by way too fast). How can I fix this? Thanks for your time, ~Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error
On Sat, Aug 25, 2007 at 12:09:34PM -0400, Frank McCormick wrote: > Took your advice here and re-installed Hal...at least the error > message goes away. I have no idea which package was still referring > to Haldaemonhow would I track that down ? > I suppose the brute-force method would be an rgrep haldaemon from / There's got to be a better way. But if not, consider something like ionice. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error
On Sat, 25 Aug 2007 15:42:45 +0200 Florian Kulzer <[EMAIL PROTECTED]> wrote: > On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote: > > On Sat, 25 Aug 2007 10:23:54 +0200 > > Florian Kulzer wrote: > > [...] > > > > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote: > > > > > > For the past few weeks I've been seeing an error message fly by > > > > > > (doesn't seem to affect anything) and I curious what's going on. > > > > > > > > > > > > the message is: > > > > > > > > > > > > dbus unknown username "haldemon" in message bus configuration file. > The fact that hal is not installed causes the message. Something else > seems to assume that the haldaemon user exists. You can either ignore > the message, or install hal (why did you purge it?), Took your advice here and re-installed Hal...at least the error message goes away. I have no idea which package was still referring to Haldaemonhow would I track that down ? Cheers Frank -- Change the world one loan at a time - visit Kiva.org to find out how -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error
On Sat, 25 Aug 2007 15:42:45 +0200 Florian Kulzer <[EMAIL PROTECTED]> wrote: > On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote: > > On Sat, 25 Aug 2007 10:23:54 +0200 > > Florian Kulzer wrote: > > [...] > > > > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote: > > > > > > For the past few weeks I've been seeing an error message fly by > > > > > > (doesn't seem to affect anything) and I curious what's going on. > > > dpkg -l hal\* > > > pn hal (no description > > available) > > pn hal-device-manager (no description > > available) > > pn hal-doc (no description > > available) > > pn hal-info(no description > > available) > > pn halibut (no description > > available) > > > > Not there. What else could cause the problem ?? > > The fact that hal is not installed causes the message. Something else > seems to assume that the haldaemon user exists. You can either ignore > the message, or install hal (why did you purge it?), As I recall I didn't purge it - it was removed when some other stuff got installed during a Kernel update. Again as I recall Hal wasn't (isn't??) compatible with something else kernel-related. or find out which > configuration file on your system contains a reference to haldaemon and > file a bug against the corresponding package. (I assume that if another > package has a configuration file that refers to the haldaemon user then > it should depend or maybe even pre-depend on the hal package.) > Well since the error seems to come from dbus, I would think it would be one of its config files...but there is no reference to hal or haldaemon in them. Very strange. Cheers Frank -- Change the world one loan at a time - visit Kiva.org to find out how -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error
On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote: > On Sat, 25 Aug 2007 10:23:54 +0200 > Florian Kulzer wrote: [...] > > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote: > > > > > For the past few weeks I've been seeing an error message fly by > > > > > (doesn't seem to affect anything) and I curious what's going on. > > > > > > > > > > the message is: > > > > > > > > > > dbus unknown username "haldemon" in message bus configuration file. [...] > > Then maybe you are not using the "hal" package at all. What is the > > output of "dpkg -l hal\*"? > > dpkg -l hal\* [...] > pn hal (no description > available) > pn hal-device-manager (no description > available) > pn hal-doc (no description > available) > pn hal-info(no description > available) > pn halibut (no description > available) > > Not there. What else could cause the problem ?? The fact that hal is not installed causes the message. Something else seems to assume that the haldaemon user exists. You can either ignore the message, or install hal (why did you purge it?), or find out which configuration file on your system contains a reference to haldaemon and file a bug against the corresponding package. (I assume that if another package has a configuration file that refers to the haldaemon user then it should depend or maybe even pre-depend on the hal package.) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error
On Sat, 25 Aug 2007 10:23:54 +0200 Florian Kulzer <[EMAIL PROTECTED]> wrote: > On Fri, Aug 24, 2007 at 20:46:22 -0400, Frank McCormick wrote: > > On Fri, 24 Aug 2007 15:07:49 +0200 Florian Kulzer wrote: > > > n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote: > > > > For the past few weeks I've been seeing an error message fly by > > > > (doesn't seem to affect anything) and I curious what's going on. > > > > > > > > the message is: > > > > > > > > dbus unknown username "haldemon" in message bus configuration file. > > > > > > It should be "haldaemon". (I assume this is just a typo since you > > > probably could not copy/paste the message directly.) The relevant > > > configuration file is /etc/dbus-1/system.d/hal.conf: > > > > > > $ grep -A2 haldaemon /etc/dbus-1/system.d/hal.conf > > > > > > > > > > > > > > > >I have no hal.conf in that directory ?? > > [...] > > > > The post-installation script of the hal > > > package is supposed to create the haldaemon user and group if they do > > > not exist. You can check if the user exists: > > > > > > $ grep hal /etc/passwd > > > >and no hal or haldaemon user??? > > Then maybe you are not using the "hal" package at all. What is the > output of "dpkg -l hal\*"? dpkg -l hal\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description ++ +--- pn hal (no description available) pn hal-device-manager (no description available) pn hal-doc (no description available) pn hal-info(no description available) pn halibut (no description available) Not there. What else could cause the problem ?? Thanks Cheers Frank -- Change the world one loan at a time - visit Kiva.org to find out how -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error
On Fri, Aug 24, 2007 at 20:46:22 -0400, Frank McCormick wrote: > On Fri, 24 Aug 2007 15:07:49 +0200 Florian Kulzer wrote: > > n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote: > > > For the past few weeks I've been seeing an error message fly by > > > (doesn't seem to affect anything) and I curious what's going on. > > > > > > the message is: > > > > > > dbus unknown username "haldemon" in message bus configuration file. > > > > It should be "haldaemon". (I assume this is just a typo since you > > probably could not copy/paste the message directly.) The relevant > > configuration file is /etc/dbus-1/system.d/hal.conf: > > > > $ grep -A2 haldaemon /etc/dbus-1/system.d/hal.conf > > > > > > > > > >I have no hal.conf in that directory ?? [...] > > The post-installation script of the hal > > package is supposed to create the haldaemon user and group if they do > > not exist. You can check if the user exists: > > > > $ grep hal /etc/passwd > >and no hal or haldaemon user??? Then maybe you are not using the "hal" package at all. What is the output of "dpkg -l hal\*"? -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error
On Fri, 24 Aug 2007 15:07:49 +0200 Florian Kulzer <[EMAIL PROTECTED]> wrote: > n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote: > > For the past few weeks I've been seeing an error message fly by > > (doesn't seem to affect anything) and I curious what's going on. > > > > the message is: > > > > dbus unknown username "haldemon" in message bus configuration file. > > It should be "haldaemon". (I assume this is just a typo since you > probably could not copy/paste the message directly.) The relevant > configuration file is /etc/dbus-1/system.d/hal.conf: > > $ grep -A2 haldaemon /etc/dbus-1/system.d/hal.conf > > > > I have no hal.conf in that directory ?? > > Hald, the daemon that manages the Hardware Abstraction Layer, used to > run as the system user "hal". About a year ago (version 0.5.7.1-1) > this was changed to user "haldaemon" (maybe to free "hal" as a name > for normal users). It seems that this transition was not carried out > correctly on your system. The post-installation script of the hal > package is supposed to create the haldaemon user and group if they do > not exist. You can check if the user exists: > > $ grep hal /etc/passwd and no hal or haldaemon user??? Cheers Frank -- Change the world one loan at a time - visit Kiva.org to find out how pgpiDa1ktTPgE.pgp Description: PGP signature
Re: boot error
On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote: > For the past few weeks I've been seeing an error message fly by (doesn't > seem to affect anything) and I curious what's going on. > > the message is: > > dbus unknown username "haldemon" in message bus configuration file. It should be "haldaemon". (I assume this is just a typo since you probably could not copy/paste the message directly.) The relevant configuration file is /etc/dbus-1/system.d/hal.conf: $ grep -A2 haldaemon /etc/dbus-1/system.d/hal.conf > I'm running Sid...so it shouldn't surprise me :) Hald, the daemon that manages the Hardware Abstraction Layer, used to run as the system user "hal". About a year ago (version 0.5.7.1-1) this was changed to user "haldaemon" (maybe to free "hal" as a name for normal users). It seems that this transition was not carried out correctly on your system. The post-installation script of the hal package is supposed to create the haldaemon user and group if they do not exist. You can check if the user exists: $ grep hal /etc/passwd hal:x:112:112:Hardware abstraction layer,,,:/var/run/hal:/bin/false haldaemon:x:104:115:Hardware abstraction layer,,,:/var/run/hal:/bin/false (As you can see, my 4 year old installation still has the legacy "hal" user. I should probably delete it...) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
boot error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 For the past few weeks I've been seeing an error message fly by (doesn't seem to affect anything) and I curious what's going on. the message is: dbus unknown username "haldemon" in message bus configuration file. I'm running Sid...so it shouldn't surprise me :) Cheers Frank -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGzjOJzWG7ldLG6fIRAuDlAKCC1M8rqZa7fFi3uXkWXGwGjEycsgCfQ2kt A2lZpdPYLpLvuR9mr/5vXLE= =qsMy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Got a boot error when starting up
On Thu, Jun 14, 2007 at 01:00:03PM -0700, yong lee wrote: > I am not a Linux expert. I hope someone would kindly > help me or give me some suggestions to fix the > problem. > > I just installed a pre-made/customized Linux 2.6.x > kernel. I converted its installation package from the > .rpm format to a .deb format using alien command. > After the installation and a reboot, the machine hung > and shrew the following errors: > > VFS: Cannot open root device "sda1" or > unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic- not syncing: VFS: Unable to mount root > fs on unknown-block(0,0) > Its bad enough to try to use non-debian applications (rpms) but to try to use a non-debian kernel rpm when the debian fhs will likely differ? The problem in this case is probably a mismatch in the initrd: the kernel doesn't have the module to mount the root device built-in. Backup. Why do you need a non-debian-standard kernel? What problem are you trying to solve? Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Got a boot error when starting up
yong lee <[EMAIL PROTECTED]>: > > I am not a Linux expert. I hope someone would kindly help me or > give me some suggestions to fix the problem. > > I just installed a pre-made/customized Linux 2.6.x kernel. I > converted its installation package from the .rpm format to a .deb > format using alien command. After the installation and a reboot, Why? alien can be useful, but it's not a magic bullet. See Bob Proulx' (sp?) recent post for an excellent exposition as to why. If you still have the sources, try re-building with make-kpkg, or use kernel.org kernel sources. Or just install Debian kernel source and make-kpkg. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://www.spots.ab.ca/~keeling Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Got a boot error when starting up
On Thu, 14 Jun 2007 13:00:03 -0700 (PDT) yong lee <[EMAIL PROTECTED]> wrote: > Hi, > > I am not a Linux expert. I hope someone would kindly > help me or give me some suggestions to fix the > problem. > > I just installed a pre-made/customized Linux 2.6.x > kernel. I converted its installation package from the > .rpm format to a .deb format using alien command. > After the installation and a reboot, the machine hung > and shrew the following errors: > > VFS: Cannot open root device "sda1" or > unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic- not syncing: VFS: Unable to mount root > fs on unknown-block(0,0) > > Please help. Many thanks > > Yong > SCSI Hardisk? I think that in terms or Kernel Update rpm2deb facility it's slighly dangeorus, but in fact this can be several problems one at the time, one it's that the root partition couldn't be mounted because the /etc/fstab dosn't point to the right partition, another it's the type of hardisk, if you know what partition is, then in the boot screen of grub edit the kernel line and add the right partition, for example kernel /boot/webdeveloper2.6.21.1 root=/dev/sda5 vga=791 where sda5 it's the right partition, if it doesn't work then might be that the kernel couldn't detect properly your hard drive (something strange ut could happen), what kind of disk is? Orestes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Got a boot error when starting up
Hi, I am not a Linux expert. I hope someone would kindly help me or give me some suggestions to fix the problem. I just installed a pre-made/customized Linux 2.6.x kernel. I converted its installation package from the .rpm format to a .deb format using alien command. After the installation and a reboot, the machine hung and shrew the following errors: VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic- not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Please help. Many thanks Yong Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error messages with custom kernel
David Fuchs wrote: thanks for the help. as I mentioned, the modules.dep file is there - but not in the initrd image that's created. I've addressed that same issue: http://lists.debian.org/debian-user/2007/03/msg00772.html and never got an answer. modules.dep is not in the initrd of kernels that do *not* get that message either, so that is not it. however, I've solved it by recompiling the kernel with the parallel port driver as a module rather than into the kernel. it seems it was this driver that tried to load some additional modules too early. How did you figure that out? Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error messages with custom kernel
thanks for the help. as I mentioned, the modules.dep file is there - but not in the initrd image that's created. however, I've solved it by recompiling the kernel with the parallel port driver as a module rather than into the kernel. it seems it was this driver that tried to load some additional modules too early. cheers, - Dave. On 5/22/07, Greg Folkert <[EMAIL PROTECTED]> wrote: On Mon, 2007-05-21 at 22:33 +0200, David Fuchs wrote: > hi all, > > I want to have a grsecurity enabled kernel and thus compiled my own. > while doing so, I also removed tons of modules from the kernel config > (drivers I know I'll never need), and chose to compile some into the > kernel instead of modules (e.g., drivers for my sata disks). > > I followed the directions found at > http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package. > > now, during the boot process, just after the kernel boots, I get some > error messages: > > FATAL: Could not load /lib/modules/2.6.19.2-grsec.1/modules.dep: No > such file or directory > > apart from this, the system boots perfectly fine and runs normal. the > file /lib/modules/2.6.19.2-grsec.1/modules.dep does exist, but there > is no such file in the generated initrd image (neither is there in the > default kernel's). > > so, why exactly is it looking for this file, and how do I get rid of the error? It is looking for the file created and/or updated by "depmod" while running the following command: depmod -e -F /boot/System.map-`uname -r` -v `uname -r` Supposedly, as far as everything is there, yours should look like this: depmod -e -F /boot/System.map-2.6.19.2-grsec.1 -v 2.6.19.2-grsec.1 That should update and give you the following files in /lib/modules/2.6.19.2-grsec.1/: modules.alias modules.ccwmap modules.dep modules.ieee1394map modules.inputmap modules.isapnpmap modules.ofmap modules.pcimap modules.seriomap modules.symbols modules.usbmap Here is hoping. -- greg, [EMAIL PROTECTED] PGP key: 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C Alternate Fingerprint: 09F9 1102 9D74 E35B D841 56C5 6356 88C0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot error messages with custom kernel
On Mon, 2007-05-21 at 22:33 +0200, David Fuchs wrote: > hi all, > > I want to have a grsecurity enabled kernel and thus compiled my own. > while doing so, I also removed tons of modules from the kernel config > (drivers I know I'll never need), and chose to compile some into the > kernel instead of modules (e.g., drivers for my sata disks). > > I followed the directions found at > http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package. > > now, during the boot process, just after the kernel boots, I get some > error messages: > > FATAL: Could not load /lib/modules/2.6.19.2-grsec.1/modules.dep: No > such file or directory > > apart from this, the system boots perfectly fine and runs normal. the > file /lib/modules/2.6.19.2-grsec.1/modules.dep does exist, but there > is no such file in the generated initrd image (neither is there in the > default kernel's). > > so, why exactly is it looking for this file, and how do I get rid of the > error? It is looking for the file created and/or updated by "depmod" while running the following command: depmod -e -F /boot/System.map-`uname -r` -v `uname -r` Supposedly, as far as everything is there, yours should look like this: depmod -e -F /boot/System.map-2.6.19.2-grsec.1 -v 2.6.19.2-grsec.1 That should update and give you the following files in /lib/modules/2.6.19.2-grsec.1/: modules.alias modules.ccwmap modules.dep modules.ieee1394map modules.inputmap modules.isapnpmap modules.ofmap modules.pcimap modules.seriomap modules.symbols modules.usbmap Here is hoping. -- greg, [EMAIL PROTECTED] PGP key: 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C Alternate Fingerprint: 09F9 1102 9D74 E35B D841 56C5 6356 88C0 signature.asc Description: This is a digitally signed message part
boot error messages with custom kernel
hi all, I want to have a grsecurity enabled kernel and thus compiled my own. while doing so, I also removed tons of modules from the kernel config (drivers I know I'll never need), and chose to compile some into the kernel instead of modules (e.g., drivers for my sata disks). I followed the directions found at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package. now, during the boot process, just after the kernel boots, I get some error messages: FATAL: Could not load /lib/modules/2.6.19.2-grsec.1/modules.dep: No such file or directory apart from this, the system boots perfectly fine and runs normal. the file /lib/modules/2.6.19.2-grsec.1/modules.dep does exist, but there is no such file in the generated initrd image (neither is there in the default kernel's). so, why exactly is it looking for this file, and how do I get rid of the error? thanks, - Dave. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
lvm boot error
hi I have a system with sarge stable up to date Because the driver's reason, I update the kernel to 2.6.14.5. Everything is OK, except some error in /var/log/boot: Tue Jan 10 18:42:30 2006: Setting up LVM Volume Groups...Tue Jan 10 18:42:30 2006: Reading all physical volumes. This may take a while...Tue Jan 10 18:42:30 2006: Found volume group "ftpdata" using metadata type lvm2 Tue Jan 10 18:42:30 2006: Found volume group "vg_oradata" using metadata type lvm1Tue Jan 10 18:42:30 2006: Found volume group "data" using metadata type lvm1Tue Jan 10 18:42:30 2006: /dev/ftpdata: opendir failed: No such file or directory Tue Jan 10 18:42:30 2006: /dev/vg_oradata: opendir failed: No such file or directoryTue Jan 10 18:42:30 2006: /dev/vg_oradata: opendir failed: No such file or directoryTue Jan 10 18:42:30 2006: /dev/vg_oradata: opendir failed: No such file or directory Tue Jan 10 18:42:30 2006: /dev/data: opendir failed: No such file or directoryTue Jan 10 18:42:30 2006: 1 logical volume(s) in volume group "ftpdata" now activeTue Jan 10 18:42:30 2006: 3 logical volume(s) in volume group "vg_oradata" now active Tue Jan 10 18:42:30 2006: 1 logical volume(s) in volume group "data" now active  I found the problem is in /etc/init.d/lvmThe line which have: vgscan --mknodes  If vgscan have parameter "--mknodes", it will report "opendir failed ", and no "/dev/[nodes]" indeed. After vgchange -a y, /dev/ automaticly appeared.  When i delete "--mknodes", no error report.  I have doubt that is udev's ploblem, but after system boot, I manually input:vgchange -a nvgscan --mknodes It report error "opendir failed..." also. Command mknod works fine google about this problem: only useful URL:http://www.mailarchives.org/list/deb...msg/2005/00451  I have delete --mknodes in /etc/init.d/lvm, no problem. But I want to know if it bring other problem? thanks Â
Re: boot error (?)
Marco Calviani wrote: >i've got an error (maybe a warning) during the boot up process, as > written in /var/log/boot: > Cleaning /tmpfind: warning: you have specified the -maxdepth option > after a non-option argument -perm, but options are not positi > onal (-maxdepth affects tests specified before it as well as those > specified after it). Please specify options before other argumentsboo > find: warning: you have specified the -depth option after a non-option > argument !, but options are not positional (-depth affects > tests specified before it as well as those specified after it). > Please specify options before other arguments. > find: warning: you have specified the -depth option after a > non-option argument !, but options are not positional (-depth affects > tests specified before it as well as those specified after it). > Please specify options before other arguments. > What might be the cause? It's /etc/init.d/bootclean.sh from the initscripts package. There are already some bugreports about this. If you don't want to wait until it gets fixed in a new version of the package you could edit /etc/init.d/bootclean.sh yourself and change the order of the find arguments. -- Thomas Weinbrenner pgpNakasJQVTs.pgp Description: PGP signature
boot error (?)
Hi, i've got an error (maybe a warning) during the boot up process, as written in /var/log/boot: Cleaning /tmpfind: warning: you have specified the -maxdepth option after a non-option argument -perm, but options are not positi onal (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other argumentsboo find: warning: you have specified the -depth option after a non-option argument !, but options are not positional (-depth affects tests specified before it as well as those specified after it). Please specify options before other arguments. find: warning: you have specified the -depth option after a non-option argument !, but options are not positional (-depth affects tests specified before it as well as those specified after it). Please specify options before other arguments. What might be the cause? Thanks, MC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: boot error -> cdrom: open failed.?
Oops... sends message in sucky outlook... sorry. See below for the rest of my message... -Original Message- From: Michael Kahle Sent: Wednesday, March 03, 2004 11:27 AM To: Debian User List Subject: boot error -> cdrom: open failed.? Hello. I recently built a 2.6.3 custom kernel for my debian/unstable machine. I am using the unstable kernel-source package. When booting my computer now I get a strange error: cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. Now I did some googling for the error and I found a myriad of solutions related to this. Among them, and things I've tried are: Recompile the kernel to not include "Kernel automounter support" Use the noauto option in fstab: # /dev/cdrw/cdrwautoro, user, noauto00 /dev/dvdrw/dvdrwautoro, user, noauto00 There was also a suggestion that this could be an indication that the drive is bad? Could someone explain (or confirm) this? Please let me know if you need more information. Thank you. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
boot error -> cdrom: open failed.?
Hello. I recently built a 2.6.3 custom kernel for my debian/unstable machine. I am using the unstable kernel-source package. When booting my computer now I get a strange error: cdrom: open failed. cdrom: open failed. cdrom: open failed. cdrom: open failed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: usbdevfs boot error
On Wed, 28 May 2003 18:10:23 +0200 Adam Majer <[EMAIL PROTECTED]> wrote: > On Fri, May 09, 2003 at 12:22:48PM +, Guldo K wrote: > > Hello everybody :-) > > > > usb_control/bulk_msg: timeout > > usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 > > This means that you have some USB device that either broken or > the driver for it is broken. Some IN endpoint (EP: 5 IN ) is not > getting data from the device. > > What USB devices do you have plugged in? What kernel are you using? Linux 2.4.20 Alcatel speedtouch ADSL modem HP deskjet 656c I have to say those errors came out just as I removed kdm: update-rc.d -f kdm remove > > I have to say I use ADSL, and set up modem_run to be run at startup. > > I then run 'ppp0 call adsl' when needed. > > I also get (b4 those errors) an error for starting 'hoplug subsystem'. > > What does it say? What error? Starting hotplug subsystem: usb** can't synthesize root hub events. Thanks a lot! Guldo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: usbdevfs boot error
On Fri, May 09, 2003 at 12:22:48PM +, Guldo K wrote: > Hello everybody :-) > > usb_control/bulk_msg: timeout > usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 This means that you have some USB device that either broken or the driver for it is broken. Some IN endpoint (EP: 5 IN ) is not getting data from the device. What USB devices do you have plugged in? What kernel are you using? > I have to say I use ADSL, and set up modem_run to be run at startup. > I then run 'ppp0 call adsl' when needed. > I also get (b4 those errors) an error for starting 'hoplug subsystem'. > > Could anyone help me with this? What does it say? What error? - Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel modprobe boot error
No, I have all the programs updated as of today. Everything is as required. I'll try reconfiguring the kernel Barbara Michael Wagner wrote: On Mittwoch, 12. Dez. 2001 at 12:36:35, Barbara Pfieffer wrote: When I boot the new kernel, it starts to boot, then I get over a screenful of the same error message: kmod: failed to exec /sbin/modprobe -s -k binfmt-464c, errno = 8 Where did I go wrong? Hello Barbara, you didn't read the /Documentation/Changes which programs you must update when you change to kernel 2.4.x. Read it and all your problems go away. Hth Michael
Re: Kernel modprobe boot error
On Mittwoch, 12. Dez. 2001 at 12:36:35, Barbara Pfieffer wrote: >When I boot the new kernel, it starts to boot, then I get over a >screenful of the same error message: > >kmod: failed to exec /sbin/modprobe -s -k binfmt-464c, errno = 8 > >Where did I go wrong? Hello Barbara, you didn't read the /Documentation/Changes which programs you must update when you change to kernel 2.4.x. Read it and all your problems go away. Hth Michael -- Registred Linux-User: 183712 GnuPG Key: B3F038DC GnuPG-fingerprint: 21A7 B384 6629 F320 8AFC A2B5 4071 E5C3 B3F0 38DC
Kernel modprobe boot error
I'm currently running Woody, with kernel 2.2.19pre17. I wanted to try the newest kernel 2.4.16. I downloaded the kernel source and the pcmicia source, since this is a laptop with a pcmcia network card. I unpack them, run make menuconfig, being sure to put pcmcia in as a module. I run make-kpkg kernel_image modules_image and it works great. I do dpkg -i kernel-image. and it installs fine. Lilo runs and I make sure I can boot to the old kernel as well. When I boot the new kernel, it starts to boot, then I get over a screenful of the same error message: kmod: failed to exec /sbin/modprobe -s -k binfmt-464c, errno = 8 Where did I go wrong? Thanks Barbara
Re: new lilo installed and boot error
According to Donald R. Spoon on Wed, Nov 28, 2001 at 04:28:17AM -0600: > See comments in your text copied below. > Thank you for a complete and very informative answer - Well I have not managed to "Fix" the /boot for my 2.4 kernel, i did manage for the previous 2.19 though. I re-installed the kernel-image for 2.4, lilo and mbr The kernel-image complained there was no mbr and I should reinstall that package but that did not give me any mbr in the /boot dir. I am now booting off a 2.19 floppy and have a reasonably working system as we talk. I am sure it will all come right - its just burning a lot of time. The error with 2.4: request-module[block-major-3] root fs not mounted VFS: cannot open root device "303" or 03:3 Please append a correct "root=" boot option unable to mount root fs on 03:03 or some rant to that effect. Then with some more uninstalling and reinstalling of the above 3 mentioned packages in both kernel falcours i now get a flashing 40 40 over the screen when I try to boot either kernel. So why is this so difficult, I though a package install that you allow to overwrite broken configurations just fixed things and worked ;) Anyway FWIW, here are the tortured results of my "efforts": /boot: total 5540 -rw-r--r--1 root root24232 Apr 8 2001 config-2.2.19-ide -rw-r--r--1 root root 613339 Apr 8 2001 vmlinuz-2.2.19-ide -rw-r--r--1 root root 213840 Apr 8 2001 System.map-2.2.19-ide -rw-r--r--1 root root14685 Oct 25 05:31 config-2.2.19pre17 -rw-r--r--1 root root 272592 Oct 25 05:31 System.map-2.2.19pre17 -rw-r--r--1 root root 512 Oct 25 05:38 boot.0300.bak -rw-r--r--1 root root33506 Nov 9 11:20 config-2.4.14-586 -rwxr-xr-x1 root root 587996 Nov 9 14:36 vmlinuz-2.4.14-586 -rw-r--r--1 root root 382516 Nov 9 14:36 System.map-2.4.14-586 lrwxrwxrwx1 root root 23 Nov 17 22:38 initrd -> /boot/initrd-2.4.14-586 -rw-r--r--1 root root 656 Nov 20 01:30 os2_d.b -rw-r--r--1 root root 728 Nov 20 01:30 chain.b -rw-r--r--1 root root 5920 Nov 20 01:30 boot-text.b -rw-r--r--1 root root 7680 Nov 20 01:30 boot-menu.b -rw-r--r--1 root root 5920 Nov 20 01:30 boot-compat.b -rw-r--r--1 root root 7708 Nov 20 01:30 boot-bmp.b -rw---1 root root 512 Nov 27 23:47 boot.0303.1.bak -rw-r--r--1 root root 512 Nov 28 01:46 boot.0303.bak -rw-r--r--1 root root 512 Nov 28 16:51 boot.0300 -rw-rw-r--1 root root 14 Nov 28 16:56 bootmess.txt -rw-r--r--1 root root 512 Nov 28 17:21 boot.0303 lrwxrwxrwx1 root root 11 Nov 28 19:59 boot.b -> boot-menu.b -rw-r--r--1 root root 3407872 Nov 28 21:46 initrd-2.4.14-586 -rw---1 root root 6144 Nov 28 21:48 map.old lrwxrwxrwx1 root root 11 Nov 28 23:42 vmlinuz-2.2.19pre17 -> vmlinuz.old -rw---1 root root 5120 Nov 29 2001 map /: lrwxrwxrwx1 root root 23 Nov 28 21:46 /vmlinuz.old -> boot/vmlinuz-2.4.14-586 lrwxrwxrwx1 root root 24 Nov 28 23:45 /vmlinuz -> /boot/vmlinuz-2.2.19-ide /etc/lilo.conf: boot=/dev/hda3 root=/dev/hda3 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=hohohoh read-only Thanx Don for your help - wish it was alla lot easier though. > Cheers, > -Don Spoon- > > Eric Smith <[EMAIL PROTECTED]> wrote: > > > I installed the new lilo and let debconf create a new > > lilo.conf and add a boot sector. Before restarting, > > however I added an entry for Windows, then /sbin/lilo -v > > which reported nothing abnormal. > > > > However when i tried to reboot, I get: > > > > unable to mount root fs > > add a root= entry (or something to that effect) > > See my comment on /etc/lilo.conf "boot" command below > > > enclosed is the relevant lilo.conf which does show the root fs > > pointing to /dev/hda3, which is correct (as per original > > lilo.conf. > > > > Here are the contents of the /boot - however I must admit that i > > seem to have lost the map file while trying to correct the > > problem :( > > > > It isn't lost...you still seem to have it listed. Is it the wrong "map" > file?? > > > Is it possible to copy the files I need to the /boot directory > > and recover the boot? > > > > Yes. You will have to boot up using a "rescue" disk, mount /dev/hda3 > and "chroot" to that mounted directory. You can then edit your > /etc/lilo.conf and re-run lilo to install the new (modified per below) > lilo to the MBR. Be careful... your paths will be all screwed up, so > use the FULL path to the file you want to run. This mainly applies to > running /sbin/lilo. Also, you may have limited choice of editors > available...hope you can run vi . > > > > Thanx > > > > tota
Re: new lilo installed and boot error
See comments in your text copied below. Cheers, -Don Spoon- Eric Smith <[EMAIL PROTECTED]> wrote: > I installed the new lilo and let debconf create a new > lilo.conf and add a boot sector. Before restarting, > however I added an entry for Windows, then /sbin/lilo -v > which reported nothing abnormal. > > However when i tried to reboot, I get: > > unable to mount root fs > add a root= entry (or something to that effect) See my comment on /etc/lilo.conf "boot" command below > enclosed is the relevant lilo.conf which does show the root fs > pointing to /dev/hda3, which is correct (as per original > lilo.conf. > > Here are the contents of the /boot - however I must admit that i > seem to have lost the map file while trying to correct the > problem :( > It isn't lost...you still seem to have it listed. Is it the wrong "map" file?? > Is it possible to copy the files I need to the /boot directory > and recover the boot? > Yes. You will have to boot up using a "rescue" disk, mount /dev/hda3 and "chroot" to that mounted directory. You can then edit your /etc/lilo.conf and re-run lilo to install the new (modified per below) lilo to the MBR. Be careful... your paths will be all screwed up, so use the FULL path to the file you want to run. This mainly applies to running /sbin/lilo. Also, you may have limited choice of editors available...hope you can run vi . > Thanx > > total 5656 > -rwxr-xr-x 1 root root 1001473 Oct 25 03:31 vmlinuz-2.2.19pre17 > -rw-r--r-- 1 root root 272592 Oct 25 03:31 System.map-2.2.19pre17 > -rw-r--r-- 1 root root14685 Oct 25 03:31 config-2.2.19pre17 > -rw-r--r-- 1 root root 512 Oct 25 03:38 boot.0300 > -rw-r--r-- 1 root root33506 Nov 9 10:20 config-2.4.14-586 > -rw-r--r-- 1 root root 382516 Nov 9 13:36 System.map-2.4.14-586 The above is your "map" file for your new 2.4.14 kernel. You can edit your /lilo.conf file to point to this file or just create a symlink in this directory to /boot/map or just copy this file to "/boot/map". I notice that a "map" file already exists further below in this listingI wouldn't touch anything here until you get some complaints about it on bootup. > -rw-r--r-- 1 root root 587996 Nov 9 13:36 vmlinuz-2.4.14-586 Do you have a symlink in your root directory to the above kernel?? (The new one). A "ls -l" should show "vmlinuz --> /boot/vmlinuz-2.4.14-596". This symlink MUST exist because that is where the "root=/dev/hda3" command in /etc/lilo.conf is saying a kernel resides. > lrwxrwxrwx 1 root root 17 Nov 13 10:55 boot.b -> > /boot/boot-menu.b > -rw-r--r-- 1 root root 3407872 Nov 17 21:38 initrd-2.4.14-586 > lrwxrwxrwx 1 root root 23 Nov 17 21:38 initrd -> > /boot/initrd-2.4.14-586 > -rw-r--r-- 1 root root 7708 Nov 20 00:30 boot-bmp.b > -rw-r--r-- 1 root root 7680 Nov 20 00:30 boot-menu.b > -rw-r--r-- 1 root root 5920 Nov 20 00:30 boot-text.b > -rw-r--r-- 1 root root 5920 Nov 20 00:30 boot-compat.b > -rw-r--r-- 1 root root 656 Nov 20 00:30 os2_d.b > -rw-r--r-- 1 root root 728 Nov 20 00:30 chain.b > -rw-rw-r-- 1 root root0 Nov 27 22:31 bootmess.txt > -rw--- 1 root root 512 Nov 27 22:47 boot.0303 > -rw--- 1 root root 6656 Nov 27 22:49 map This is the "/boot/map" I was talking about above. > > -- > Eric Smith > > lba32 > # Generated by liloconfig > > # Specifies the boot device > boot=/dev/hda3 This command puts the lilo boot-loader info on the "Superblock" of hda3. I does NOT put it into the MBR. There are occasions (few) where you would want to do this... essentially if you are using another boot-loader and want to call lilo for some reason. On my machine this line reads: "boot=/dev/hda". > --snip-- < > image=/vmlinuz > label=Linux > read-only > > image=/dev/hdc1 > label=Windows I suggest you get rid of the second "image" stanza for Windows and use the notation below...i.e. uncomment the "other" line and make the appropriate edits for the HD used and the "label" you want. > > # 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/hda2 > # label=dos
Re: sid - new lilo installed and boot error - SOLUTION?
Could some one please advise whether this is the best / safest way to recover a bootable system? backup the / partition. reinstall a base system - upgrade this to sid - copy back the / omitting /boot (I actually have /boot on another partition). Thanks for an answer. According to Eric Smith on Wed, Nov 28, 2001 at 01:01:34AM +0100: > I installed the new lilo and let debconf create a new > lilo.conf and add a boot sector. Before restarting, > however I added an entry for Windows, then /sbin/lilo -v > which reported nothing abnormal. > > However when i tried to reboot, I get: > > unable to mount root fs > add a root= entry (or something to that effect) > > enclosed is the relevant lilo.conf which does show the root fs > pointing to /dev/hda3, which is correct (as per original > lilo.conf. > > Here are the contents of the /boot - however I must admit that i > seem to have lost the map file while trying to correct the > problem :( > > Is it possible to copy the files I need to the /boot directory > and recover the boot? > > Thanx > > total 5656 > -rwxr-xr-x 1 root root 1001473 Oct 25 03:31 vmlinuz-2.2.19pre17 > -rw-r--r-- 1 root root 272592 Oct 25 03:31 System.map-2.2.19pre17 > -rw-r--r-- 1 root root14685 Oct 25 03:31 config-2.2.19pre17 > -rw-r--r-- 1 root root 512 Oct 25 03:38 boot.0300 > -rw-r--r-- 1 root root33506 Nov 9 10:20 config-2.4.14-586 > -rw-r--r-- 1 root root 382516 Nov 9 13:36 System.map-2.4.14-586 > -rw-r--r-- 1 root root 587996 Nov 9 13:36 vmlinuz-2.4.14-586 > lrwxrwxrwx 1 root root 17 Nov 13 10:55 boot.b -> > /boot/boot-menu.b > -rw-r--r-- 1 root root 3407872 Nov 17 21:38 initrd-2.4.14-586 > lrwxrwxrwx 1 root root 23 Nov 17 21:38 initrd -> > /boot/initrd-2.4.14-586 > -rw-r--r-- 1 root root 7708 Nov 20 00:30 boot-bmp.b > -rw-r--r-- 1 root root 7680 Nov 20 00:30 boot-menu.b > -rw-r--r-- 1 root root 5920 Nov 20 00:30 boot-text.b > -rw-r--r-- 1 root root 5920 Nov 20 00:30 boot-compat.b > -rw-r--r-- 1 root root 656 Nov 20 00:30 os2_d.b > -rw-r--r-- 1 root root 728 Nov 20 00:30 chain.b > -rw-rw-r-- 1 root root0 Nov 27 22:31 bootmess.txt > -rw--- 1 root root 512 Nov 27 22:47 boot.0303 > -rw--- 1 root root 6656 Nov 27 22:49 map > > -- > Eric Smith > lba32 > # Generated by liloconfig > > # Specifies the boot device > boot=/dev/hda3 > > # 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/hda3 > > # 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=60 > > # 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). > # use the corresponding text mode. A list of available modes > # can be obtained by booting with vga=ask and pressing [Enter]. > vga=ask > > image=/vmlinuz > label=Linux > read-only > > image=/dev/hdc1 > label=Windows > > # 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/hda2 > # label=dos > -- Eric Smith Fruitcom.com Benelux Phone: +31 70 313 0240 Mobile:+31 6 551 76300
sid - new lilo installed and boot error
I installed the new lilo and let debconf create a new lilo.conf and add a boot sector. Before restarting, however I added an entry for Windows, then /sbin/lilo -v which reported nothing abnormal. However when i tried to reboot, I get: unable to mount root fs add a root= entry (or something to that effect) enclosed is the relevant lilo.conf which does show the root fs pointing to /dev/hda3, which is correct (as per original lilo.conf. Here are the contents of the /boot - however I must admit that i seem to have lost the map file while trying to correct the problem :( Is it possible to copy the files I need to the /boot directory and recover the boot? Thanx total 5656 -rwxr-xr-x 1 root root 1001473 Oct 25 03:31 vmlinuz-2.2.19pre17 -rw-r--r-- 1 root root 272592 Oct 25 03:31 System.map-2.2.19pre17 -rw-r--r-- 1 root root14685 Oct 25 03:31 config-2.2.19pre17 -rw-r--r-- 1 root root 512 Oct 25 03:38 boot.0300 -rw-r--r-- 1 root root33506 Nov 9 10:20 config-2.4.14-586 -rw-r--r-- 1 root root 382516 Nov 9 13:36 System.map-2.4.14-586 -rw-r--r-- 1 root root 587996 Nov 9 13:36 vmlinuz-2.4.14-586 lrwxrwxrwx 1 root root 17 Nov 13 10:55 boot.b -> /boot/boot-menu.b -rw-r--r-- 1 root root 3407872 Nov 17 21:38 initrd-2.4.14-586 lrwxrwxrwx 1 root root 23 Nov 17 21:38 initrd -> /boot/initrd-2.4.14-586 -rw-r--r-- 1 root root 7708 Nov 20 00:30 boot-bmp.b -rw-r--r-- 1 root root 7680 Nov 20 00:30 boot-menu.b -rw-r--r-- 1 root root 5920 Nov 20 00:30 boot-text.b -rw-r--r-- 1 root root 5920 Nov 20 00:30 boot-compat.b -rw-r--r-- 1 root root 656 Nov 20 00:30 os2_d.b -rw-r--r-- 1 root root 728 Nov 20 00:30 chain.b -rw-rw-r-- 1 root root0 Nov 27 22:31 bootmess.txt -rw--- 1 root root 512 Nov 27 22:47 boot.0303 -rw--- 1 root root 6656 Nov 27 22:49 map -- Eric Smith lba32 # Generated by liloconfig # Specifies the boot device boot=/dev/hda3 # 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/hda3 # 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=60 # 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). # use the corresponding text mode. A list of available modes # can be obtained by booting with vga=ask and pressing [Enter]. vga=ask image=/vmlinuz label=Linux read-only image=/dev/hdc1 label=Windows # 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/hda2 # label=dos
Re: Boot error (PCMCIA Modules)
Try #> dmesg to read boot messages at your leisure. The remaining pcmcia messages probably come from scripts in etc/rc*.d/ directories. Try #> ls -l /etc/rc*.d/ | grep pcmcia to see which such scripts are softlinked there. I should be 'OK' to remove those links as well as the corresponding script in /etc/init.d
Re: Boot error (PCMCIA Modules)
dpkg --purge pcmcia-cs Eileen Orbell wrote: > > Thank you that removed most of the errors. When I ran that command I did > receive the following errors though: > directory not empty so it could not remove all reference.. > can I delete these directories??? > I still get some reference to pcmcia on boot... > > Thanks > > At 01:41 AM 12/5/2000 +0100, you wrote: > >On Mon, Dec 04, 2000 at 07:21:38PM -0500, Eileen Orbell wrote: > > > I reconfig my kernel and now on boot I get about 5 -6 lines of error re > > > PCMICIA modules. Because it boots fast I cannot read them all but I am > > > assuming I am missing the modules. I do not have any PCMCIA hardware > > > anyway so can I remove this? I did not see any reference to it in make > > > xconfig?? > >apt-get --purge remove pcmcia-cs > > > >-- > >,---. > > > Name: Alson van der Meulen < > > > Personal: [EMAIL PROTECTED] < > > > School: [EMAIL PROTECTED]< > >`---' > >We don't support that. We won't support that. > >- > > > > > >-- > >To UNSUBSCRIBE, email to [EMAIL PROTECTED] > >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > Eileen Orbell > Software & Internet Applications > Capitol College > mailto:[EMAIL PROTECTED] > mailto:[EMAIL PROTECTED] > Don't Fear the Penguin. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
Re: Boot error (PCMCIA Modules)
Thank you that removed most of the errors. When I ran that command I did receive the following errors though: directory not empty so it could not remove all reference.. can I delete these directories??? I still get some reference to pcmcia on boot... Thanks At 01:41 AM 12/5/2000 +0100, you wrote: On Mon, Dec 04, 2000 at 07:21:38PM -0500, Eileen Orbell wrote: > I reconfig my kernel and now on boot I get about 5 -6 lines of error re > PCMICIA modules. Because it boots fast I cannot read them all but I am > assuming I am missing the modules. I do not have any PCMCIA hardware > anyway so can I remove this? I did not see any reference to it in make > xconfig?? apt-get --purge remove pcmcia-cs -- ,---. > Name: Alson van der Meulen < > Personal: [EMAIL PROTECTED] < > School: [EMAIL PROTECTED]< `---' We don't support that. We won't support that. - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Eileen Orbell Software & Internet Applications Capitol College mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Don't Fear the Penguin.
Boot error (PCMCIA Modules)
I reconfig my kernel and now on boot I get about 5 -6 lines of error re PCMICIA modules. Because it boots fast I cannot read them all but I am assuming I am missing the modules. I do not have any PCMCIA hardware anyway so can I remove this? I did not see any reference to it in make xconfig?? Hope I made some sence here.. Thanks Eileen Orbell Software & Internet Applications Capitol College mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Don't Fear the Penguin.
Re: Boot error (PCMCIA Modules)
On Mon, Dec 04, 2000 at 07:21:38PM -0500, Eileen Orbell wrote: > I reconfig my kernel and now on boot I get about 5 -6 lines of error re > PCMICIA modules. Because it boots fast I cannot read them all but I am > assuming I am missing the modules. I do not have any PCMCIA hardware > anyway so can I remove this? I did not see any reference to it in make > xconfig?? apt-get --purge remove pcmcia-cs -- ,---. > Name: Alson van der Meulen < > Personal: [EMAIL PROTECTED] < > School: [EMAIL PROTECTED]< `---' We don't support that. We won't support that. -
Boot error (PCMCIA Modules)
I reconfig my kernel and now on boot I get about 5 -6 lines of error re PCMICIA modules. Because it boots fast I cannot read them all but I am assuming I am missing the modules. I do not have any PCMCIA hardware anyway so can I remove this? I did not see any reference to it in make xconfig?? Hope I made some sence here.. Thanks Eileen Orbell Software & Internet Applications Capitol College mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Don't Fear the Penguin.
Boot error (PCMCIA Modules)
I reconfig my kernel and now on boot I get about 5 -6 lines of error re PCMICIA modules. Because it boots fast I cannot read them all but I am assuming I am missing the modules. I do not have any PCMCIA hardware anyway so can I remove this? I did not see any reference to it in make xconfig?? Hope I made some sence here.. Thanks Eileen Orbell Software & Internet Applications Capitol College mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Don't Fear the Penguin.
Potato boot error
Hello, the list! I just upgraded from slink up to potato and am now getting a nice error on bootup that's slowing things down a big. I can't seem to find the error in my logs anywhere, but it says something about my boot sector not matching what's saved, gives a bunch of sector numbers, then says it's not going to fix it. I _suspect_ that it's due to my using Partition Magic's Boot Magic program to switch between Linux & the unmentionable OS, in which case I'm not worried...but I'd like to know how to get rid of the message. I know I'm being a little vague here, but if anyone has any suggestions I'd appreciate it. -- [EMAIL PROTECTED] [] Bababooey Dragon [] <-==UDIC==-> "The stupider it looks, the more important it probably is." -- J. R. "Bob" Dobbs -- Babylon Five Addict [] DEVOlved [] Dirty old man in training
Re: boot error
On Tue, Jun 20, 2000 at 10:32:31AM +0100, Moore, Paul wrote: > But the message comes at bootup. AFAIK, the root FS is always mounted > read-only in the first instance, and is then remounted read-write later in > the boot sequence. I think this is so. > So this looks like a problem in the base Debian boot sequence, trying to > insmod unix.o too early in the boot process, before root is remounted. Yup. > BTW, I have this problem too, so I can confirm that it occurs in a clean > Potato (unofficial CDs from about 25th May) install. Mine too is a clean install of potato using the disk-set available from one of debian's mirror sites. > See bugs #51379 (seems to imply that it's fixed in modutils 2.3.7-1, but > it's still there in my version, 2.3.11-6), #50921 (similar), #49059 > (different, but also ksymoops and the boot sequence). Any news on this? > PS Is there really no search facility in the bug tracking system? I had to > get a full listing, and then use my browser's search. And that only finds > bugs with the word in the title :-( Also, when searching mailing lists, it's annoying to have to load so much stuff (links to all the lists sorted by dates...) until you can just go to the search form located at the bottom of the page. Cheers -- S. Burgener Powered by Debian GNU/Linux 2.2
RE: boot error
AFAIK, the root filesystem is mounted read-write and remounted read-only on errors... Ron On Tue, 20 Jun 2000, Moore, Paul wrote: > From: Ron Rademaker [mailto:[EMAIL PROTECTED] > > On Mon, 19 Jun 2000, Sven Burgener wrote: > > > > > Anyone know why do I get the following error upon bootup: > > > > > > insmod: /lib/modules/2.2.15/misc/unix.o cannot create > > > /var/log/ksymoops/2619212757.ksyms Read Only Filesystem > > > > > Looks like your root file system is mounted read only, try to do (as > > root): touch /a (if no error occurs, don't forget to do rm > > /a). If it's mounted read only, you can remount it read-write, but > > you better check out your /etc/fstab. > > But the message comes at bootup. AFAIK, the root FS is always mounted > read-only in the first instance, and is then remounted read-write later in > the boot sequence. > > So this looks like a problem in the base Debian boot sequence, trying to > insmod unix.o too early in the boot process, before root is remounted. > > BTW, I have this problem too, so I can confirm that it occurs in a clean > Potato (unofficial CDs from about 25th May) install. > > See bugs #51379 (seems to imply that it's fixed in modutils 2.3.7-1, but > it's still there in my version, 2.3.11-6), #50921 (similar), #49059 > (different, but also ksymoops and the boot sequence). > > Paul. > > PS Is there really no search facility in the bug tracking system? I had to > get a full listing, and then use my browser's search. And that only finds > bugs with the word in the title :-( > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
RE: boot error
From: Ron Rademaker [mailto:[EMAIL PROTECTED] > On Mon, 19 Jun 2000, Sven Burgener wrote: > > > Anyone know why do I get the following error upon bootup: > > > > insmod: /lib/modules/2.2.15/misc/unix.o cannot create > > /var/log/ksymoops/2619212757.ksyms Read Only Filesystem > > > Looks like your root file system is mounted read only, try to do (as > root): touch /a (if no error occurs, don't forget to do rm > /a). If it's mounted read only, you can remount it read-write, but > you better check out your /etc/fstab. But the message comes at bootup. AFAIK, the root FS is always mounted read-only in the first instance, and is then remounted read-write later in the boot sequence. So this looks like a problem in the base Debian boot sequence, trying to insmod unix.o too early in the boot process, before root is remounted. BTW, I have this problem too, so I can confirm that it occurs in a clean Potato (unofficial CDs from about 25th May) install. See bugs #51379 (seems to imply that it's fixed in modutils 2.3.7-1, but it's still there in my version, 2.3.11-6), #50921 (similar), #49059 (different, but also ksymoops and the boot sequence). Paul. PS Is there really no search facility in the bug tracking system? I had to get a full listing, and then use my browser's search. And that only finds bugs with the word in the title :-(
Re: boot error
Looks like your root file system is mounted read only, try to do (as root): touch /a (if no error occurs, don't forget to do rm /a). If it's mounted read only, you can remount it read-write, but you better check out your /etc/fstab. Ron Rademaker On Mon, 19 Jun 2000, Sven Burgener wrote: > Hi all > > Anyone know why do I get the following error upon bootup: > > insmod: /lib/modules/2.2.15/misc/unix.o cannot create > /var/log/ksymoops/2619212757.ksyms Read Only Filesystem > > Indeed that file doesn't exist. Should I create it using /dev/null > or what? > > If I should post more infos, please let me know. Oh yes, almost forgot: > running up-to-date potato here. > > TIA > Sven > -- > Powered by Debian GNU/Linux 2.2 > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
boot error
Hi all Anyone know why do I get the following error upon bootup: insmod: /lib/modules/2.2.15/misc/unix.o cannot create /var/log/ksymoops/2619212757.ksyms Read Only Filesystem Indeed that file doesn't exist. Should I create it using /dev/null or what? If I should post more infos, please let me know. Oh yes, almost forgot: running up-to-date potato here. TIA Sven -- Powered by Debian GNU/Linux 2.2
Re: Boot error
On Sat, 12 Jun 1999, Kevin A. Foss wrote: > On Thu, Jun 10, 1999 at 07:55:58AM -0700, Lazar Fleysher wrote: > > Hi everyone, > > > > I have noticed that sometimes I get this boot error: > > mktime() failed unexpectedly (rc -1). Aborting. > > Could someone tell what and how dengerous it is? > > This is probably from hwclock, it will say this if your bios returns > what appears to be an invalid time. (Until quite recently hwclock > was rather strict about where the century byte should be -- more > strict than the bios manufacturers.) Try running hwclock and see > what happens. > > I've gotten this error on every original IBM machine I've tried -- > both PS/2s and Valuepoints. I'm not sure why you would get this > only 'sometimes' however, it should really be everytime. > Thanks Kevin This is exactly what happened. The bios clock was showing 2099 :) I have seen this on several pentium machines (not running linux).. 'sometimes' is because I have noticed it and fixed the bios date back to 1999 :) Thanks again ZORO Take these broken wings and learn to fly... ///|\\\ 0 0 ( . )http://pages.nyu.edu/~rqf6512 - | |
Re: Boot error
On Thu, Jun 10, 1999 at 07:55:58AM -0700, Lazar Fleysher wrote: > Hi everyone, > > I have noticed that sometimes I get this boot error: > > mktime() failed unexpectedly (rc -1). Aborting. > > Could someone tell what and how dengerous it is? This is probably from hwclock, it will say this if your bios returns what appears to be an invalid time. (Until quite recently hwclock was rather strict about where the century byte should be -- more strict than the bios manufacturers.) Try running hwclock and see what happens. I've gotten this error on every original IBM machine I've tried -- both PS/2s and Valuepoints. I'm not sure why you would get this only 'sometimes' however, it should really be everytime. If it is hwclock (and I'm almost sure it is) -- the latest versions of util-linux in unstable have a fixed version of hwclock. The danger is minimal, an improperly patched hwclock could potentially screw up your BIOS checksum, but the Debian packaged versions shouldn't. -Kevin -- Kevin A. Foss [EMAIL PROTECTED]
Boot error
Hi everyone, I have noticed that sometimes I get this boot error: mktime() failed unexpectedly (rc -1). Aborting. Could someone tell what and how dengerous it is? Thanks ZORO Take these broken wings and learn to fly... ///|\\\ 0 0 ( . )http://pages.nyu.edu/~rqf6512 - | |
Boot Error Message after potato upgrade.
Hi All, Just installed Gimp1.1 from potato using apt-get and got 11.4M of upgrade. I'm using kernel 2.2.5 (F%$ HOSTILE!! aka Rules). Anyway, after the gimp upgrade I get this error on boot. initd 2.76 booting could not initalize It hangs for sometime the boots. Everything seems find, but is it? Rod.. BTW..for anyone wondering what happened to my Debian support idea, I'm in the works of refining it. I think it might lead to my total liberation from the use of NT in that I gotten offer to start a Linux based support company...
kernel 2.2.1 boot error, help.
I finally got a new kernel compiled. But when I boot it I get this error. kmod: failed to exec /sbin/modprobe -s -k binfmt -464c errno=8 request_modle[binfmt-464c]:fork failed errno=11 it scroll up the screen and all I can do is crtl+alt+del, to reboot and stop it. Luckly I can still bot my old kernel. Any idea on what this is and how to correct it! Roddie Rod 'Man is the greatest cancer ever to be seen' -Entombed 'Contempt'
Re: TIOCSER?WILD Boot Error!
Lindsay Allen writes: > >IIRC that is fixed by installing the latest setserial. > >> >> Ever since I switched to the dev kernel, I've had the following >> >> message on boot: >> >> >> >> TIOCSER?WILD ioctl obsolete, ignored Yup, that fixed it. Thanks!
Re: TIOCSER?WILD Boot Error!
IIRC that is fixed by installing the latest setserial. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Lindsay Allen <[EMAIL PROTECTED]> Perth, Western Australia voice +61 8 9316 2486 32.0125S 115.8445Evk6lj Debian Linux =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= On Thu, 10 Dec 1998, Daniel Elenius wrote: > Ossama Othman writes: > >Hi, > > > >> Ever since I switched to the dev kernel, I've had the following > >> message on boot: > >> > >> TIOCSER?WILD ioctl obsolete, ignored > >> > >> I doesn't sound dangerous or anything, but a boot error just doesn't > >> look good. So does anyone know how I could fix this? Is it a bug, just > >> like the SIOCADDR thingy? > > > >It was my understanding that the SIOCADDR boot error was not a bug in the > >kernel since the dev kernel now sets up routing automatically and an > >explicit call to "route" is no longer needed. Perhaps your TIOCSER* > >problem is related. Check out the Documentation directory in your kernel > >source directory. It may contain files that explain the error/warning. > > I've noticed now that the message has something to do with the serial > ports. I find nothing in the kernel docs. What file(s) in init.d (or > elsewhere) do stuff with the serial ports? I do not use the serial > ports, as I don't have a modem connection nor a serial mouse. > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
Re: TIOCSER?WILD Boot Error!
Ossama Othman writes: >Hi, > >> Ever since I switched to the dev kernel, I've had the following >> message on boot: >> >> TIOCSER?WILD ioctl obsolete, ignored >> >> I doesn't sound dangerous or anything, but a boot error just doesn't >> look good. So does anyone know how I could fix this? Is it a bug, just >> like the SIOCADDR thingy? > >It was my understanding that the SIOCADDR boot error was not a bug in the >kernel since the dev kernel now sets up routing automatically and an >explicit call to "route" is no longer needed. Perhaps your TIOCSER* >problem is related. Check out the Documentation directory in your kernel >source directory. It may contain files that explain the error/warning. I've noticed now that the message has something to do with the serial ports. I find nothing in the kernel docs. What file(s) in init.d (or elsewhere) do stuff with the serial ports? I do not use the serial ports, as I don't have a modem connection nor a serial mouse.
Re: TIOCSER?WILD Boot Error!
Hi, > Ever since I switched to the dev kernel, I've had the following > message on boot: > > TIOCSER?WILD ioctl obsolete, ignored > > I doesn't sound dangerous or anything, but a boot error just doesn't > look good. So does anyone know how I could fix this? Is it a bug, just > like the SIOCADDR thingy? It was my understanding that the SIOCADDR boot error was not a bug in the kernel since the dev kernel now sets up routing automatically and an explicit call to "route" is no longer needed. Perhaps your TIOCSER* problem is related. Check out the Documentation directory in your kernel source directory. It may contain files that explain the error/warning. -Ossama __ Ossama Othman <[EMAIL PROTECTED]> 58 60 1A E8 7A 66 F4 44 74 9F 3C D4 EF BF 35 88 1024/8A04D15D 1998/08/26
TIOCSER?WILD Boot Error!
Ever since I switched to the dev kernel, I've had the following message on boot: TIOCSER?WILD ioctl obsolete, ignored I doesn't sound dangerous or anything, but a boot error just doesn't look good. So does anyone know how I could fix this? Is it a bug, just like the SIOCADDR thingy?
Re: RAMDISK boot error
On Mon, 15 Dec 1997, Aaron Walker wrote: > I just setup this experimental system to run Debian 1.3.1: > > 486SX/25 > 4MB RAM > CL3424 w/512K > > A real POWER-HOUSE!!! I just put this machine together to test Debian > 2.0 aka hamm. > Anyways... When I try to boot the rescue disk, I get the message: > RAMDISK: Compressed image found at block 0 > It hanges for ever when this message pops up. Could it be from > low-memory? I though you were able to run Debian w/4MB RAM. Please > HELP! Have you used the "lowmem" series of bootdisks? I think the difference is that those have a rootdisk on floppy, where the default "rescue" disk tries to load the rootdisk into ram (and then mounts its root from that ramdisk.) IIRC this is mentioned in the installation document. Cheers, Joost -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
RAMDISK boot error
I just setup this experimental system to run Debian 1.3.1: 486SX/25 4MB RAM CL3424 w/512K A real POWER-HOUSE!!! I just put this machine together to test Debian 2.0 aka hamm. Anyways... When I try to boot the rescue disk, I get the message: RAMDISK: Compressed image found at block 0 It hanges for ever when this message pops up. Could it be from low-memory? I though you were able to run Debian w/4MB RAM. Please HELP! Thanks. -- ` Aaron Walker Work: Site: http://www.iconmedia.com Email: [EMAIL PROTECTED] Personal: Site: http://www.iconmedia.com/aaron Email: [EMAIL PROTECTED] `` -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
BOOT ERROR?
I get this error message when I boot everytime. I didn't mean to put a MBR on the drive, but I redid the one on hda. It is the secind HD on IDE. Before I put the MBR on hdb, I didn't get the message. Anyone have any suggestions about fixing the problem? hdb: [DM6:MBR] [remap [DM6:MBR]] [656/128/63] hdb1 hdb2 < hdb5 hdb6 hdb7 hdb8 > hdb3 hdb4 Thanks JoKeR -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
boot error messages
Hello again... I have been noticing some error messages during boot, that I have been wondering about. I wonder if someone can tell me whether or not I should be worried about these. The thing that is odd about this is that my system seems to be working fine, as far as I can see. Here are the error messages: Initialization of hpfs failed Initialization of isofs failed lp: unable to get major 6 Unable to get major 11 for SCSI-CD Initialization of sr_mod failed I don't recall trying to configure hpfs or isofs into my kernel, so I am not sure why those messages appear. What is the lp error? lpr works fine. My SCSI cdrom works fine too, as far as I can tell. Should I just ignore these errors and stay fat, dumb and happy? Thanks! -- Ken Gaugler N6OSK Santa Clara, California email: [EMAIL PROTECTED] URL: http://www.wco.com/~keng "The life of a Repo Man is always INTENSE..."
