Re: Boot Errors
When you get the "invalid argument" error do you see something in the output of "dmesg"? Can you try to mount it from another distro live-USB or from the Debian installer rescue mode? Enviado desde Outlook Mobile<https://aka.ms/blhgte> From: Michael Lee Sent: Thursday, March 2, 2023 4:30:47 PM To: debian-user@lists.debian.org Subject: Boot Errors While running the stable branch of 64-bit Debian, rebooted into an alternative OS, but forgot to unmount a USB device beforhand. Shutdown was taking too long, so forced it anyway. Now when I try to start Linux, I get these error messages: [1.922640] platform gpio_ich.2.auto: failed to claim resource 0:[io 0x0480-0x04ff] [8.934607] BTRFS error (device sdc2): parent transid verify faild on 176160768 wanted 680981 found 680979 [8.934649] BTRFS error (device sdc2): failed to read block groups 1 - 5 [8.935724] BTRFS error (device sdc2): open_ctree failed mount: mounting /dev/sdc2 on /root failed: invalid argument failed to mount /dev/sdc2 as root file system Then the initramfs command prompt appears. A little hard to find much on that. Read in the btrfs wiki that <-o ro,usebackuproot> with the mount command could help when the "wanted" and "found" numbers were not too far apart. mount -t btrfs -o ro,usebackuproot /dev/sdc2 TRIED with: /sysroot GOT: mount: mounting /dev/sdc2 on /sysroot failed: invalid argument TRIED with: / GOT: mount: mounting /dev/sdc2 on / failed: invalid argument TRIED with: /root GOT: mount: mounting /dev/sdc2 on /root failed: invalid argument Is this a GRUB issue, a btrfs issue, or must I reinstall the operating system, and if so where can I find out which files must be preserved in order to maintain continuity?
Boot Errors
While running the stable branch of 64-bit Debian, rebooted into an alternative OS, but forgot to unmount a USB device beforhand. Shutdown was taking too long, so forced it anyway. Now when I try to start Linux, I get these error messages: [1.922640] platform gpio_ich.2.auto: failed to claim resource 0:[io 0x0480-0x04ff] [8.934607] BTRFS error (device sdc2): parent transid verify faild on 176160768 wanted 680981 found 680979 [8.934649] BTRFS error (device sdc2): failed to read block groups 1 - 5 [8.935724] BTRFS error (device sdc2): open_ctree failed mount: mounting /dev/sdc2 on /root failed: invalid argument failed to mount /dev/sdc2 as root file system Then the initramfs command prompt appears. A little hard to find much on that. Read in the btrfs wiki that <-o ro,usebackuproot> with the mount command could help when the "wanted" and "found" numbers were not too far apart. mount -t btrfs -o ro,usebackuproot /dev/sdc2 TRIED with: /sysroot GOT: mount: mounting /dev/sdc2 on /sysroot failed: invalid argument TRIED with: / GOT: mount: mounting /dev/sdc2 on / failed: invalid argument TRIED with: /root GOT: mount: mounting /dev/sdc2 on /root failed: invalid argument Is this a GRUB issue, a btrfs issue, or must I reinstall the operating system, and if so where can I find out which files must be preserved in order to maintain continuity?
Re: Boot errors
On Sb, 07 mai 11, 20:12:24, Frank McCormick wrote: By the way I am more interested in the errors themselves than in the fact they are not logged. Not sure what you mean by this. Can you try to reproduce the errors at least from memory, or take a picture of your screen while booting ;) My guess is you're seeing the /run/whatever not writable, falling back to /dev/.udev/ which seems to be rather a notice, not an error. BTW, if you're brave you might want to test 'initscripts' from experimental, which adds the support for /run. Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Boot errors
On Sat, 07 May 2011 20:12:24 -0400, Frank McCormick wrote: On Sat, 07 May 2011 18:34:23 -0400 Frank McCormick debianl...@videotron.ca wrote: On Sat, 07 May 2011 21:28:34 + (UTC) Camaleón noela...@gmail.com wrote: How about enabling the boot log at /etc/default/ bootlogd (BOOTLOGD_ENABLE=Yes)? :-? It is enabled. By the way I am more interested in the errors themselves than in the fact they are not logged. Then I'd also worry about a phantom message. Messages on boot should go to some place (they're splitted into /var/log/dmesg and/or /var/log/ boot), but they need to be registered. Anyway, to start debugging the problem, you need to know the exact messages you get. Greetings, -- Camaleón -- 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/pan.2011.05.08.10.03...@gmail.com
Re: Boot errors
On Sun, 08 May 2011 11:28:04 +0300 Andrei Popescu andreimpope...@gmail.com wrote: On Sb, 07 mai 11, 20:12:24, Frank McCormick wrote: By the way I am more interested in the errors themselves than in the fact they are not logged. Not sure what you mean by this. Can you try to reproduce the errors at least from memory, or take a picture of your screen while booting ;) My guess is you're seeing the /run/whatever not writable, falling back to /dev/.udev/ which seems to be rather a notice, not an error. Yes those are the ones. They started several weeks ago after an update change which I now don't remember (Hell I can't remember what I had for breakfast :))) BTW, if you're brave you might want to test 'initscripts' from experimental, which adds the support for /run. Ummm...well maybe not. Right now I'm having enough trouble just keeping up with the problems I create, never mind what others can do. Thanks for the help Andrei! -- -- Frank -- -- 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/20110508080022.d4489c4a.debianl...@videotron.ca
Re: Boot errors
On Sun, 08 May 2011 10:03:57 + (UTC) Camaleón noela...@gmail.com wrote: On Sat, 07 May 2011 20:12:24 -0400, Frank McCormick wrote: On Sat, 07 May 2011 18:34:23 -0400 Frank McCormick debianl...@videotron.ca wrote: On Sat, 07 May 2011 21:28:34 + (UTC) Camaleón noela...@gmail.com wrote: How about enabling the boot log at /etc/default/ bootlogd (BOOTLOGD_ENABLE=Yes)? :-? It is enabled. By the way I am more interested in the errors themselves than in the fact they are not logged. Then I'd also worry about a phantom message. Messages on boot should go to some place (they're splitted into /var/log/dmesg and/or /var/log/ boot), but they need to be registered. Then come right at the very start of the boot process...I guess before there is anyplace to write except for the screen. Anyway, to start debugging the problem, you need to know the exact messages you get. They are the udevd can't exec messages which Andrei Popescu told me in another message are not really errors, there are more informative. -- -- Frank -- -- 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/20110508080339.3af1d716.debianl...@videotron.ca
Re: Boot errors
Frank McCormick wrote: I am still seeing a bunch of errors related to udev when I boot this machine running Sid up-to-date. The errors come from udev but are not logged anywhere. I suspect they are related to the situation weeks ago when an update created a situation which needed a new directory off the root which didn't yet exist. The solution (which I implemented) was to delete the /run directory in the root. Does anyone else see these udev errors? They don't seem to affect the operation of Sid. I see them. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624145 Hgo -- 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/iq6e7r$9vq$1...@dough.gmane.org
Re: Boot errors
On Sun, 08 May 2011 10:52:26 -0500 Hugo Vanwoerkom hvw59...@care2.com wrote: Frank McCormick wrote: I am still seeing a bunch of errors related to udev when I boot this machine running Sid up-to-date. The errors come from udev but are not logged anywhere. I suspect they are related to the situation weeks ago I see them. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624145 Had a look at it. Seems it's the old it's a bug, no, it's not a bug, yes it is a bug. I guess it'll all work itself out in the end. Thanks for the confirmation Huge, -- -- Frank -- -- 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/20110508134055.984f6e8f.debianl...@videotron.ca
Boot errors
I am still seeing a bunch of errors related to udev when I boot this machine running Sid up-to-date. The errors come from udev but are not logged anywhere. I suspect they are related to the situation weeks ago when an update created a situation which needed a new directory off the root which didn't yet exist. The solution (which I implemented) was to delete the /run directory in the root. Does anyone else see these udev errors? They don't seem to affect the operation of Sid. -- -- Frank -- -- 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/20110507164212.e3c303ec.debianl...@videotron.ca
Re: Boot errors
On Sat, 07 May 2011 16:42:12 -0400, Frank McCormick wrote: I am still seeing a bunch of errors related to udev when I boot this machine running Sid up-to-date. The errors come from udev but are not logged anywhere. (...) How about enabling the boot log at /etc/default/ bootlogd (BOOTLOGD_ENABLE=Yes)? :-? Greetings, -- Camaleón -- 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/pan.2011.05.07.21.28...@gmail.com
Re: Boot errors
On Sat, 07 May 2011 21:28:34 + (UTC) Camaleón noela...@gmail.com wrote: On Sat, 07 May 2011 16:42:12 -0400, Frank McCormick wrote: I am still seeing a bunch of errors related to udev when I boot this machine running Sid up-to-date. The errors come from udev but are not logged anywhere. (...) How about enabling the boot log at /etc/default/ bootlogd (BOOTLOGD_ENABLE=Yes)? :-? It is enabled. -- -- Frank -- -- 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/20110507183423.37fe1a00.debianl...@videotron.ca
Re: Boot errors
On Sat, 07 May 2011 18:34:23 -0400 Frank McCormick debianl...@videotron.ca wrote: On Sat, 07 May 2011 21:28:34 + (UTC) Camaleón noela...@gmail.com wrote: On Sat, 07 May 2011 16:42:12 -0400, Frank McCormick wrote: I am still seeing a bunch of errors related to udev when I boot this machine running Sid up-to-date. The errors come from udev but are not logged anywhere. (...) How about enabling the boot log at /etc/default/ bootlogd (BOOTLOGD_ENABLE=Yes)? :-? It is enabled. By the way I am more interested in the errors themselves than in the fact they are not logged. -- -- Frank -- -- 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/20110507201224.35863b58.debianl...@videotron.ca
Re: boot errors with new debian kernel
Hi, Scott. Note that I'm not any expert in these questions, but as noone responds, I'll try to give it a shot: On Tue, Dec 23, 2003 at 03:53:57PM -0600, Scott wrote: I'm trying to upgrade my debian woody kernel. I was trying to do it the simple way, using a prebuilt kernel image. My original install Woody kernel didn't work, either so I built my own to get it going. Now, I'd like to get in-sysc if possible and use the standard kernel. Or at least figure out why it won't work for my Redhat to Debian education's sake. I haven't manage to understand the Debian way of kernelling for some three years I've been with Linux. But messing with kernel always was a deep-insider thing, wasn't it? Via dselect, I installed the kernel-image-2.4.18-1-686 but I can't get it to work correctly. It appears to be related to module problems (a guess). I'd paste the results of the boot messages, but I can't find them logged anywhere. I looked in dmesg, /var/log/syslog, etc. Nowhere do I see the Use a pencil. If they go off-screen too quickly, stop the tty output by XOFF (Ctrl-S on i386 vt). Resume by XON (Ctrl-Q). If they are pushed off the dmesg buffer, try to boot into singleuser/use the `init=' kernel parameter. message about Can't locate module in any /var/log/* file. (As an aside, I'd like to know where to look for that if possible.) The jist of the error messages is shown in quotes below. They are interspersed with the rest of the boot messages. The problems see to start right after the mtab note. Note: can't open /etc/mtab (but it's there and exists as far as I can see) Who is the originator of that message? What is the context? What are the mtab's permissions? Probably, they mean opening for writing, so readonly filesystem would be a problem. Note: /etc/modules.conf is newer than /lib/modules/2.4.18-1-686/modules.dep (so I booted with this kernel, then I ran depmod -a, got no errors, then rebooted, did not fix) Yes. This is one of the things I don't understand. modprobe: Can't locate module * Here it really helps to spell out. Generally, these are missing entries in /etc/modules.conf. I get the newer than messages a dozen or so more times. System boots, but at least the network card is not up. It is listed as a module I believe in the modules net dir. Boot with my kernel, all works OK. Boot with the pre-built, all kinds of err messages. Spell out. The Debian way of editing /etc/modules.conf is modconf(8), AFAIUI. But maybe I'm wrong, really. P.S. As a side question, how do I tell if I have the matching kernel source that is correlated to say the 2.4.18-1-686 image? Is kernel-source-2.4.18 always in-sync witht the latest similar (2.4.18) kernel? The docs should tell you. If they don't, it's a bug :-) -- Jan Minar Please don't CC me, I'm subscribed. x 4 pgp0.pgp Description: PGP signature
boot errors with new debian kernel
Greetings: I'm trying to upgrade my debian woody kernel. I was trying to do it the simple way, using a prebuilt kernel image. My original install Woody kernel didn't work, either so I built my own to get it going. Now, I'd like to get in-sysc if possible and use the standard kernel. Or at least figure out why it won't work for my Redhat to Debian education's sake. Via dselect, I installed the kernel-image-2.4.18-1-686 but I can't get it to work correctly. It appears to be related to module problems (a guess). I'd paste the results of the boot messages, but I can't find them logged anywhere. I looked in dmesg, /var/log/syslog, etc. Nowhere do I see the message about Can't locate module in any /var/log/* file. (As an aside, I'd like to know where to look for that if possible.) The jist of the error messages is shown in quotes below. They are interspersed with the rest of the boot messages. The problems see to start right after the mtab note. Note: can't open /etc/mtab (but it's there and exists as far as I can see) Note: /etc/modules.conf is newer than /lib/modules/2.4.18-1-686/modules.dep (so I booted with this kernel, then I ran depmod -a, got no errors, then rebooted, did not fix) modprobe: Can't locate module * insmod: Note: /etc/modules.conf is newer than /lib/modules/2.4.18-1-686/modules.dep I get the newer than messages a dozen or so more times. System boots, but at least the network card is not up. It is listed as a module I believe in the modules net dir. Boot with my kernel, all works OK. Boot with the pre-built, all kinds of err messages. Any help much appreciated! Thanks, Scott P.S. As a side question, how do I tell if I have the matching kernel source that is correlated to say the 2.4.18-1-686 image? Is kernel-source-2.4.18 always in-sync witht the latest similar (2.4.18) kernel? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot errors
I'm installing debian-potato, and i'm incountering some errors. I have a AIC7890 scsi card taht is built on to my asus m/b, and for some reason i get scsi errors when booting of the boot disk. I installed the base2_1.tgz from a dos partition and when it used the kernel image then it had no problems booting up, but as soon as i use my boot disk to boot up into the part where i acutally install the base system, and other things i get a scsi error that looks like this Scsi disk error: host 0 channel 0 id 2 lun 0 return code 2802 extra data not valid Curent error sd 08:11: sense key Hardware error. Now i'm not sure why i'm getting this but i really hope that you guys can help me cause i'm really looking forward to using Debian
boot errors
I have 1 2 gig drive separted into 4 partitions. One is win95 boot
partition, another is 650 meg, and the last two are for Linux, one 800 meg
Linux native, and one 45 meg swap file. I mount them in /etc/fstab like
this:
# file system mount point type options dump
pass
/dev/hda6 / ext2defaults,errors=remount-ro 0
1
/dev/hda7 noneswapsw 0 0
/dev/hda1 /mnt/c vfatdefaults,rw 0 1
/dev/hda5 /mnt/e vfatdefaults,rw 0 1
/dev/hdc1 /mnt/d vfatdefaults,rw 0 1
/dev/hdd/cdrom iso9660 defaults,ro 0 1
but when I boot, I get these errors:
Jul 18 17:21:45 Obereon kernel: Unable to load NLS charset
cp437(nls_cp437)
Jul 18 17:21:45 Obereon kernel: Unable to load NLS charset
iso8859-1(nls_iso8859
_1)
Jul 18 17:21:45 Obereon kernel: Unable to load NLS charset
cp437(nls_cp437)
Jul 18 17:21:45 Obereon kernel: Unable to load NLS charset
iso8859-1(nls_iso8859
_1)
Jul 18 17:21:45 Obereon kernel: VFS: Disk change detected on device 16:01
Jul 18 17:21:45 Obereon kernel: hdc: hdc1
Jul 18 17:21:45 Obereon kernel: VFS: Disk change detected on device 16:01
Jul 18 17:21:45 Obereon kernel: hdc: hdc1
Jul 18 17:21:45 Obereon kernel: Unable to load NLS charset
cp437(nls_cp437)
Jul 18 17:21:45 Obereon kernel: Unable to load NLS charset
iso8859-1(nls_iso8859
_1)
Jul 18 17:21:45 Obereon kernel: hdd: media changed
Jul 18 17:21:45 Obereon kernel: VFS: Disk change detected on device 16:40
Jul 18 17:21:45 Obereon kernel: ISO9660 Extensions: Microsoft Joliet Level
3
Jul 18 17:21:45 Obereon kernel: Max size:332569 Log zone size:2048
Jul 18 17:21:45 Obereon kernel: First datazone:27 Root inode number
55296
Jul 18 17:21:45 Obereon kernel: Unable to load NLS charset
iso8859-1(nls_iso8859
_1)
Jul 18 17:23:11 Obereon kernel: registered device ppp0
Jul 18 21:39:35 Obereon kernel: hdd: media changed
Jul 18 21:39:35 Obereon kernel: VFS: Disk change detected on device 16:40
Jul 18 21:39:36 Obereon kernel: ISO9660 Extensions: Microsoft Joliet Level
3
Jul 18 21:39:36 Obereon kernel: Max size:332940 Log zone size:2048
Jul 18 21:39:36 Obereon kernel: First datazone:27 Root inode number
55296
Jul 19 01:32:12 Obereon kernel: Kernel logging (proc) stopped.
Jul 19 01:34:57 Obereon kernel: Kernel logging (proc) stopped.
Jul 20 21:25:38 Obereon kernel: registered device ppp0
Jul 20 22:17:41 Obereon kernel: hdd : tray open or drive not ready
Jul 20 22:17:43 Obereon last message repeated 2 times
Jul 20 22:17:44 Obereon kernel: hdd: media changed
Jul 20 22:17:44 Obereon kernel: VFS: Disk change detected on device 16:40
Jul 20 22:17:47 Obereon kernel: ISO9660 Extensions: Microsoft Joliet Level
3
Jul 20 22:17:47 Obereon kernel: Max size:332569 Log zone size:2048
Jul 20 22:17:47 Obereon kernel: First datazone:27 Root inode number
55296
Jul 21 06:44:23 Obereon kernel: hdc: read_intr: status=0x51 { DriveReady
SeekCom
plete Error }
Jul 21 06:44:23 Obereon kernel: hdc: read_intr: error=0x40 {
UncorrectableError
}, LBAsect=101, sector=38
Jul 21 06:44:23 Obereon kernel: end_request: I/O error, dev 16:01, sector
38
Jul 21 06:44:23 Obereon kernel: bread in fat_access failed
Jul 21 06:44:23 Obereon kernel: Filesystem panic (dev 16:01, mounted on
03:06:12
201)
Jul 21 06:44:23 Obereon kernel: FAT error
Jul 21 06:44:23 Obereon kernel: File system has been set read-only
Jul 21 06:44:24 Obereon kernel: hdc: read_intr: status=0x51 { DriveReady
SeekCom
plete Error }
Jul 21 06:44:24 Obereon kernel: hdc: read_intr: error=0x40 {
UncorrectableError
}, LBAsect=101, sector=38
Jul 21 06:44:24 Obereon kernel: end_request: I/O error, dev 16:01, sector
38
Jul 21 06:44:24 Obereon kernel: bread in fat_access failed
Jul 21 06:44:24 Obereon
Boot Errors
When I boot I get the following errors all one after the other: SIOCSIFADDR: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device SIOCADDRTL: Network is unreachable SIOCADDRT: Network is unreachable It does not seem to be affecting the performance of my system but I would like to know what it is a try to fix it. Any Ideas? __ Get Your Private, Free Email at http://www.hotmail.com -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Boot Errors
Acutally I don't even have a ethernet card. All that I have is a ISP connection via modem. Obviously my system is trying to configure something that doesn't have to. How do I set up /etc/init.d/network so this does not happen. (I am assuming that /etc/init.d/network is something that my system has to execute on startup for local loop back network stuff?) From [EMAIL PROTECTED] Sat Jul 18 18:05:32 1998 Received: from localhost ([127.0.0.1]) by shorelink.com with smtp (ident grep using rfc1413) id m0yxhut-001CabC (Debian Smail-3.2 1996-Jul-4 #2); Sat, 18 Jul 1998 18:05:31 -0700 (PDT) Date: Sat, 18 Jul 1998 18:05:30 -0700 (PDT) From: George Bonser [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Mark Yobb [EMAIL PROTECTED] cc: debian-user@lists.debian.org Subject: Re: Boot Errors In-Reply-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] X-No-Archive: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It looks like it is executing the stuff in /etc/init.d/network but can't for some reason. Maybe you have the ethernet disconnected? Maybe there is some stuff in there that can't work unless you are connected to a network? On Sat, 18 Jul 1998, Mark Yobb wrote: When I boot I get the following errors all one after the other: SIOCSIFADDR: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device SIOCADDRTL: Network is unreachable SIOCADDRT: Network is unreachable It does not seem to be affecting the performance of my system but I would like to know what it is a try to fix it. Any Ideas? __ Get Your Private, Free Email at http://www.hotmail.com -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null George Bonser Microsoft! Which end of the stick do you want today? __ Get Your Private, Free Email at http://www.hotmail.com -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
boot errors!
Yo- I just compiled a new kernel and I get the following error messages on boot. I can't decipher them. If some knows what is wrong I appreciate your help. --- 4] EFLAGS: 00010202 eax: 0010 ebx: 05cec018 ecx: 0680c5da edx: ea60 esi: edi: 05cea000 ebp: 05ce9fbc esp: 05ce9f60 ds: 0018 es: 0018 fs: 0010 gs: 002b ss: 0018 Process insmod (pid: 37, process nr: 16, stackpage=05ce9000) Stack: 001a002b c000 05ce9fbc 05cecc0c 0680 0700 0680 05ce0018 00112062 001a6f30 05ce9fbc 00111d94 05d6af24 002a 05d99618 05d99398 0010a8fc 05ce9fbc 0100 Call Trace: [001a002b] [0680] [0700] [0680] [00112062] [00111d94] [0010a8fc] [0680c548] [06800018] [0680c5da] [0680c548] Code: 64 8a 04 0e 0f a1 88 c2 81 e2 ff 00 00 00 89 54 24 10 52 68 Unable to handle kernel paging request at virtual address c680c5f1 current-tss.cr3 = 05d6f000, %cr3 = 05d6f000 *pde = 0009e067 *pte = Oops: CPU:0 EIP:0010:[0680c5f1] - The above is repeated 3 times in dmesg. Any ideas. Thanks as usual! -Ian _ Ian K. Setford [EMAIL PROTECTED] H: 940.566.0461 Pgr: 817.901.0255 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
boot errors
I receive these errors during boot-up (I included the /dev/... entries to let you know at what point in the boot process the errors come up): Mounting local file systems ... /dev/hda1 on /win type vfat (rw) /dev/hdb1 on /windoze type vfat (rw) /dev/hdb2 on /extra type ext2 (rw) /dev/sda4 on /zip type vfat (rw) SIOCSIFADDR: Operation not supported by device SIOCSIFNETMASK: Operation not supported by device SIOCSIFBRDADDR: Operation not supported by device SIOCADDRT: Network is unreachable SIOCADDRT: Network is unreachable ...is this something I should care or worry about and if so, what is the best way to remedy it? thanks, matty Matt Thompson MZI, Inc. v-206.430.3726 707 S. Grady Wayf-206.430.3420 Renton, WA 98055 [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
I receive these errors during boot-up (I included the /dev/... entries to
let you know at what point in the boot process the errors come up):
Mounting local file systems ...
/dev/hda1 on /win type vfat (rw)
/dev/hdb1 on /windoze type vfat (rw)
/dev/hdb2 on /extra type ext2 (rw)
/dev/sda4 on /zip type vfat (rw)
Nothing to do with the above.
SIOCSIFADDR: Operation not supported by device
SIOCSIFNETMASK: Operation not supported by device
SIOCSIFBRDADDR: Operation not supported by device
SIOCADDRT: Network is unreachable
SIOCADDRT: Network is unreachable
This is all in regards to ifconfig/route. Take a look at
/etc/init.d/network and see if you can see anything obviously wrong.
Even better, send it to me and I'll tell you what to fix
okeedokee...:) here's the 'less':
#! /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=208.154.103.130
NETMASK=255.255.255.0
NETWORK=208.154.103.0
BROADCAST=208.154.103.255
GATEWAY=208.154.100.1
ifconfig ppp ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
[ ${GATEWAY} ] route add default gw ${GATEWAY} metric 1
/etc/init.d/network (END)
...is this something I should care or worry about and if so, what is the
best way to remedy it?
I'd worry about it if you want to use a network, yes.. :)
the only network i connect to is the internet, and that works just fine.
:)
thanks,
matty
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
Lawrence [EMAIL PROTECTED] writes:
David R Baker wrote:
I believe the no /usr/bin/X11/xfs found ... error is referring to
a running font server, not the file. The font server does not run
unless you configure it to run. This is merely a nuisance message.
I do not know about the others.
It is a fresh 1.3.1 install and I found that the xfs is called by rc*.d,
I am not using xdm, is it the cause of the problem?
You can simply remove this message by changing /etc/init.d/xfs using
this patch:
--- xfs.old Wed Sep 24 22:34:27 1997
+++ xfs Wed Sep 24 22:34:54 1997
@@ -29,7 +29,10 @@
fi
;;
stop)
+if [ $run_xfs = 1 ]
+then
start-stop-daemon --stop --verbose --exec /usr/bin/X11/xfs
+fi
;;
*)
echo Usage: /etc/init.d/xfs {start|stop}
Torsten
--
What a depressingly stupid machine
The Restaurant at the End of the Universe
PGP Public Key is available
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
Torsten Hilbrich wrote:
Lawrence [EMAIL PROTECTED] writes:
David R Baker wrote:
I believe the no /usr/bin/X11/xfs found ... error is referring to
a running font server, not the file. The font server does not run
unless you configure it to run. This is merely a nuisance message.
I do not know about the others.
It is a fresh 1.3.1 install and I found that the xfs is called by rc*.d,
I am not using xdm, is it the cause of the problem?
You can simply remove this message by changing /etc/init.d/xfs using
this patch:
--- xfs.old Wed Sep 24 22:34:27 1997
+++ xfs Wed Sep 24 22:34:54 1997
@@ -29,7 +29,10 @@
fi
;;
stop)
+if [ $run_xfs = 1 ]
+then
start-stop-daemon --stop --verbose --exec /usr/bin/X11/xfs
+fi
;;
*)
echo Usage: /etc/init.d/xfs {start|stop}
Torsten
I found it and did that yesterday already. Thanks anyway,
Lawrence
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
boot errors
I have restalled debian 1.3. When I boot it, I found the following errors after the PPP copyright mesg. SIOCIFADDR no such device SIOCIFNETMASK no such device SIOCIFBRDADDR no such device Also, when I reboot the computer, I always get the following error. no /usr/bin/X11/xfs found; non killed I checked the path and the path is correct. Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
Hi, Lawrence wrote: I have restalled debian 1.3. When I boot it, I found the following errors after the PPP copyright mesg. SIOCIFADDR no such device SIOCIFNETMASK no such device SIOCIFBRDADDR no such device Also, when I reboot the computer, I always get the following error. no /usr/bin/X11/xfs found; non killed I checked the path and the path is correct. Lawrence I believe the no /usr/bin/X11/xfs found ... error is referring to a running font server, not the file. The font server does not run unless you configure it to run. This is merely a nuisance message. I do not know about the others. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
On Wed, 24 Sep 1997, Lawrence wrote: I have restalled debian 1.3. When I boot it, I found the following errors after the PPP copyright mesg. SIOCIFADDR no such device SIOCIFNETMASK no such device SIOCIFBRDADDR no such device I see these too. I don't think it's anything to worry about. It has to do with lack of a network device. Like myself your machine probably has no ethernet card and relies on ppp for its net connection. As ppp is not active during this portion of the boot, these errors result from the this attempt. Also, when I reboot the computer, I always get the following error. no /usr/bin/X11/xfs found; non killed I checked the path and the path is correct. The path is correct. The message is because there was no xfs daemon to kill. Reporting the path is somewhat confusing as the path exists even when the daemon is not running. Luck, Dwarf -- _-_-_-_-_-_- _-_-_-_-_-_-_- aka Dale Scheetz Phone: 1 (904) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors.
Hi, I have restalled debian 1.3. I resemble that remark ;-) Sorry, couldn't resist temptation. Regards, Dave Restall mail/debian/970924.tx debian-user@lists.debian.org -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors.
sorry, it should be I have re-installed debian 1.3, my brain beating faster than my fingers:) Dave Restall wrote: Hi, I have restalled debian 1.3. I resemble that remark ;-) Sorry, couldn't resist temptation. Regards, Dave Restall mail/debian/970924.tx debian-user@lists.debian.org -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
David R Baker wrote: Hi, Lawrence wrote: I have restalled debian 1.3. When I boot it, I found the following errors after the PPP copyright mesg. SIOCIFADDR no such device SIOCIFNETMASK no such device SIOCIFBRDADDR no such device Also, when I reboot the computer, I always get the following error. no /usr/bin/X11/xfs found; non killed I checked the path and the path is correct. Lawrence I believe the no /usr/bin/X11/xfs found ... error is referring to a running font server, not the file. The font server does not run unless you configure it to run. This is merely a nuisance message. I do not know about the others. It is a fresh 1.3.1 install and I found that the xfs is called by rc*.d, I am not using xdm, is it the cause of the problem? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
Also, when I reboot the computer, I always get the following error. no /usr/bin/X11/xfs found; non killed I checked the path and the path is correct. Then, who's wrong? it is a fresh install and I think it should be configured properly, when I install xbase, it didn't ask me anything about the xfs daemon. Once it finishs the boot process, I check the running processes using 'ps aux' and couldn't find xfs(???) Is it possible to get rid of this silly message. Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
I have restalled debian 1.3. When I boot it, I found the following errors after the PPP copyright mesg. SIOCIFADDR no such device SIOCIFNETMASK no such device SIOCIFBRDADDR no such device I see these too. I don't think it's anything to worry about. It has to do with lack of a network device. Like myself your machine probably has no ethernet card and relies on ppp for its net connection. As ppp is not active during this portion of the boot, these errors result from the this attempt. Should I configure the ip address, netmask and broadcast address if I am only using dialup PPP? Lawrence -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
On Wed, 24 Sep 1997, Lawrence wrote: Also, when I reboot the computer, I always get the following error. no /usr/bin/X11/xfs found; non killed I checked the path and the path is correct. Then, who's wrong? it is a fresh install and I think it should be configured properly, when I install xbase, it didn't ask me anything about the xfs daemon. Once it finishs the boot process, I check the running processes using 'ps aux' and couldn't find xfs(???) Is it possible to get rid of this silly message. Well, you could configure X to run the xfs file server (daemon). Then there would be something to shut down when you reboot, but I don't think you need to do this. You should be getting a similar message for xdm when that daemon is not running also. The shutdown routines are trying to bring everything down gracefully. The fact that you don't have everything running on your machine that could be results in these kinds of errors. The best I can say is, Don't worry about it, the error gets cleared from the screen on reboot anyway ;-). Luck, Dwarf -- _-_-_-_-_-_- _-_-_-_-_-_-_- aka Dale Scheetz Phone: 1 (904) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
On Wed, 24 Sep 1997, Lawrence wrote: I have restalled debian 1.3. When I boot it, I found the following errors after the PPP copyright mesg. SIOCIFADDR no such device SIOCIFNETMASK no such device SIOCIFBRDADDR no such device I see these too. I don't think it's anything to worry about. It has to do with lack of a network device. Like myself your machine probably has no ethernet card and relies on ppp for its net connection. As ppp is not active during this portion of the boot, these errors result from the this attempt. Should I configure the ip address, netmask and broadcast address if I am only using dialup PPP? Well, that will not help, and may cause difficulties for the pppd daemon. Those items should be configured in the options file for pppd, but only if they are not determined by your ISP. In any case this will not quiet these error messages, but you should not be concerned about them either. Luck, Dwarf -- _-_-_-_-_-_- _-_-_-_-_-_-_- aka Dale Scheetz Phone: 1 (904) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
Dale Scheetz wrote: On Wed, 24 Sep 1997, Lawrence wrote: I have restalled debian 1.3. When I boot it, I found the following errors after the PPP copyright mesg. SIOCIFADDR no such device SIOCIFNETMASK no such device SIOCIFBRDADDR no such device I see these too. I don't think it's anything to worry about. It has to do with lack of a network device. Like myself your machine probably has no ethernet card and relies on ppp for its net connection. As ppp is not active during this portion of the boot, these errors result from the this attempt. Should I configure the ip address, netmask and broadcast address if I am only using dialup PPP? Well, that will not help, and may cause difficulties for the pppd daemon. Those items should be configured in the options file for pppd, but only if they are not determined by your ISP. In any case this will not quiet these error messages, but you should not be concerned about them either. Eventually I quiet those three messages by commenting out the IF/Netmask/Broadcast setting in the /etc/init.d/network. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: boot errors
Lawrence wrote: David R Baker wrote: snip It is a fresh 1.3.1 install and I found that the xfs is called by rc*.d, I am not using xdm, is it the cause of the problem? I also did a fresh install of 1.3.1 and do not use xdm (old computer, one of the things I like about X is it's optional) I do not think it is a real problem. I believe the /usr/doc/XFree86 docs describe how to set up xfs, or you could find the script that trying to stop and edit that. I just ignore the message. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: various boot errors and module problems!
On Wed, 1 May 1996, Brian K Servis wrote: When booting I get the following errors when calculating dependencies. *** Unresolved symbols in module /lib/modules/1.2.13/net/3c501.o *** Unresolved symbols in module /lib/modules/1.2.13/net/3c509.o *** Unresolved symbols in module /lib/modules/1.2.13/net/8390.o [...deleted...] This all started after I recompiled the 1.2.13 kernel to set it up for my tastes. After make zImage and modifing /etc/lilo.conf and running lilo, I rebooted and did make modules then make modules_install. Does anything look familiar? If you need more info please ask and I will get you what you need. I am running my linux box at home with no real network connection but I am wanting to connect to a dial in account running slirp. I compiled in network support but no drivers for any protocols, just load a module when I want to connect. I've seen something like this before. Looks like you've got a lot of old modules from a previous compilation of the kernel...maybe from the kernel image which came with your debian install disks. Try cleaning out /lib/modules/1.2.13/* and then: cd /usr/src/linux make modules make modules_install reboot Craig
various boot errors and module problems!
Hi, I could really use someones help. When booting I get the following errors when calculating dependencies. *** Unresolved symbols in module /lib/modules/1.2.13/net/3c501.o *** Unresolved symbols in module /lib/modules/1.2.13/net/3c509.o *** Unresolved symbols in module /lib/modules/1.2.13/net/8390.o *** Unresolved symbols in module /lib/modules/1.2.13/net/apricot.o *** Unresolved symbols in module /lib/modules/1.2.13/net/arcnet.o *** Unresolved symbols in module /lib/modules/1.2.13/net/bsd_comp.o *** Unresolved symbols in module /lib/modules/1.2.13/net/de4x5.o *** Unresolved symbols in module /lib/modules/1.2.13/net/de600.o *** Unresolved symbols in module /lib/modules/1.2.13/net/de620.o *** Unresolved symbols in module /lib/modules/1.2.13/net/depca.o *** Unresolved symbols in module /lib/modules/1.2.13/net/dummy.o *** Unresolved symbols in module /lib/modules/1.2.13/net/eexpress.o *** Unresolved symbols in module /lib/modules/1.2.13/net/ewrk3.o *** Unresolved symbols in module /lib/modules/1.2.13/net/plip.o *** Unresolved symbols in module /lib/modules/1.2.13/net/ppp.o *** Unresolved symbols in module /lib/modules/1.2.13/net/slip.o Then when the network is initiated I get socket: Invalid argument socket: Invalid argument This is from the network script in /etc/init.d. I have not touched it since install. The two command in the script are: ifconfig lo 127.0.0.1 route add 127.0.0.1 Then after entering runlevel 2 I get the following error starting /sbin/syslogd starting /sbin/klogd syslogd: syslog: Unknown protocol, suspending inet service: Invalid argument The only thing I have edited in the /etc/syslogd.conf file is to comment the 3 lines for the news.* log files, and the above command was happening before I did that. Then once booted if I try and load the PPP module using modprobe ppp I get the following errors: tty_register_ldisc: wrong version dev_close: wrong version slhc_free: wrong version slhc_init: wrong version slhc_toss: wrong version alloc_skb: wrong version netif_rx: wrong version slhc_uncompress: wrong version slhc_remember: wrong version kill_fasync: wrong version n_tty_ioctl: wrong version slhc_compress: wrong version dev_kfree_skb: wrong version register_netdev: wrong version unregister_netdev: wrong version Failed to load module! The symbols from kernel 1.2.13 don't match 1.2.13 This all started after I recompiled the 1.2.13 kernel to set it up for my tastes. After make zImage and modifing /etc/lilo.conf and running lilo, I rebooted and did make modules then make modules_install. Does anything look familiar? If you need more info please ask and I will get you what you need. I am running my linux box at home with no real network connection but I am wanting to connect to a dial in account running slirp. I compiled in network support but no drivers for any protocols, just load a module when I want to connect. Thanks. Brian Servis Mechanical Engineering Purdue University [EMAIL PROTECTED] http://widget.ecn.purdue.edu/~servis
Re: various boot errors and module problems!
During make config (second or third line) there is a line about config mod version or something to that effect. You want to choose no for this option then the modules should load correctly. Luck, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
