__
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
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 resou
On Sun, 08 May 2011 10:52:26 -0500
Hugo Vanwoerkom 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 situatio
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
On Sun, 08 May 2011 10:03:57 + (UTC)
Camaleón wrote:
> On Sat, 07 May 2011 20:12:24 -0400, Frank McCormick wrote:
>
> > On Sat, 07 May 2011 18:34:23 -0400
> > Frank McCormick wrote:
> >
> >> On Sat, 07 May 2011 21:28:34 + (UTC) Camaleón
> >> wrote:
>
> >> > How about enabling the bo
On Sun, 08 May 2011 11:28:04 +0300
Andrei Popescu 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
On Sat, 07 May 2011 20:12:24 -0400, Frank McCormick wrote:
> On Sat, 07 May 2011 18:34:23 -0400
> Frank McCormick wrote:
>
>> On Sat, 07 May 2011 21:28:34 + (UTC) Camaleón
>> wrote:
>> > How about enabling the boot log at "/etc/default/ bootlogd"
>> > (BOOTLOGD_ENABLE=Yes)? :-?
>> >
>> >
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 ;)
On Sat, 07 May 2011 18:34:23 -0400
Frank McCormick wrote:
> On Sat, 07 May 2011 21:28:34 + (UTC)
> Camaleón 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
On Sat, 07 May 2011 21:28:34 + (UTC)
Camaleón 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.
>
> (.
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" (BOOTLOG
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'
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
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 lea
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 n
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:
#
/dev/hda6 / ext2defaults,er
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
>
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
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
> > 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 e
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 t
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
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 kno
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 opti
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
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 th
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 proper
> > 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
> wit
> > 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 anythin
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 t
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
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] .
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 a
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 err
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 ki
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/module
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
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/
38 matches
Mail list logo
