Trandahl, Steve wrote:
I am having trouble with some of my modules at during
boot-up. I can see the error messages fly by, but when I use dmesg,
I don't see the errors. How can I find out what these errors and/or
warning messages are once Debian has booted?
Thanks in advance!
Steve Trandahl
s for your help
> Kent West wrote:
> I've found that if you have xdm/gdm/kdm/wdm (I'm not sure
> which one(s)
> cause the problem) starting X automatically, about the only
> way to find
> these module errors is to look in the log files for the
> individual modules
> "Kent" == Kent West <[EMAIL PROTECTED]> writes:
Kent> A better way, is to disable xdm/gdm/kdm/wdm, then
Kent> reboot. When you get logged in, you can then Shift-PgUp
Kent> through the error messages.
That's correct so far.
Kent> (For some reason, xdm/gdm/kdm/wdm seems to cl
ndahl
Cotelligent, Inc
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
I've found that if you have xdm/gdm/kdm/wdm (I'm not sure which one(s)
cause the problem) starting X automatically, about the only way to find
these module errors is to look in the log files for the individua
I am having trouble with some of my modules at during boot-up. I can see
the error messages fly by, but when I use dmesg, I don't see the errors.
How can I find out what these errors and/or warning messages are once Debian
has booted?
Thanks in advance!
Steve Trandahl
Cotelligent, Inc
[EMAIL PRO
I'm running SID and recently upgraded the kernel from the Potato 2.2.17
to kernel-image-2.2.18. Now I'm getting all these weird errors about
modules being out of date. I'm also getting no response when I try to
"ping localhost" (which is probaly why junkbuster no longer works). I
can connect to the
Quoting Robb Kidd ([EMAIL PROTECTED]):
> Bernd Worsch wrote:
>
> > In case your feeling lonely your quite right, the messages
> > seem to be nowhere in the logs. Which is quite unsatisfactory.
>
> It's to do with what goes on in /etc/init.d/modutils. I'm not savvy
> enough to
> tell you whe
They don't show up in my syslog.
On Tue, 26 Sep 2000 15:44:03 -0500 (CDT), Brent Buchholz wrote:
>On Tue, 26 Sep 2000, Kent West wrote:
>
>>I know "dmesg" will show the boot-up messages generated (by the
>>kernel?); however, this apparently doesn't show the errors generated by
>>modules being
Bernd Worsch wrote:
> In case your feeling lonely your quite right, the messages
> seem to be nowhere in the logs. Which is quite unsatisfactory.
It's to do with what goes on in /etc/init.d/modutils. I'm not savvy enough
to
tell you where to do it, but if you've a mind to, start figuring ou
%% Moritz Schulte <[EMAIL PROTECTED]> writes:
ms> ehm, you can scroll on the linux console with shift+page_down/page_up.
You can only do this up until you switch to a different console, for any
reason. Once that happens, all history on the first one is gone.
For example, if you use XDM or GDM
Quoting Kent West ([EMAIL PROTECTED]):
> Moritz Schulte wrote:
> >
> > Kent West <[EMAIL PROTECTED]> writes:
> >
> > > I know "dmesg" will show the boot-up messages generated (by the
> > > kernel?); however, this apparently doesn't show the errors generated by
> > > modules being loaded. These me
In case your feeling lonely your quite right, the messages
seem to be nowhere in the logs. Which is quite unsatisfactory.
Thanx for posting this, i wondered where to find them
quite a while already.
How about filing this as a bug :)
Cheers
Bernd
--
--
Moritz Schulte wrote:
>
> Kent West <[EMAIL PROTECTED]> writes:
>
> > I know "dmesg" will show the boot-up messages generated (by the
> > kernel?); however, this apparently doesn't show the errors generated by
> > modules being loaded. These messages go by too fast to catch, and then I
> > haven'
Brent Buchholz wrote:
>
> On Tue, 26 Sep 2000, Kent West wrote:
>
> >I know "dmesg" will show the boot-up messages generated (by the
> >kernel?); however, this apparently doesn't show the errors generated by
> >modules being loaded. These messages go by too fast to catch, and then I
> >haven't be
On Tue, 26 Sep 2000, Kent West wrote:
>I know "dmesg" will show the boot-up messages generated (by the
>kernel?); however, this apparently doesn't show the errors generated by
>modules being loaded. These messages go by too fast to catch, and then I
>haven't been able to find a way to read them
Kent West <[EMAIL PROTECTED]> writes:
> I know "dmesg" will show the boot-up messages generated (by the
> kernel?); however, this apparently doesn't show the errors generated by
> modules being loaded. These messages go by too fast to catch, and then I
> haven't been able to find a way to read
I know "dmesg" will show the boot-up messages generated (by the
kernel?); however, this apparently doesn't show the errors generated by
modules being loaded. These messages go by too fast to catch, and then I
haven't been able to find a way to read them again.
Can anyone clue me in as to how I
On Tue, Apr 25, 2000 at 03:55:36AM -, Pollywog wrote:
> I just started getting these errors after updating potato:
>
> Apr 25 03:17:00 lilypad insmod: Note: /etc/modules.conf is more
> recent than /lib/modules/2.2.14/modules.dep
> Apr 25 03:17:00 lilypad insmod: Note: /etc/modules.conf is more
I just started getting these errors after updating potato:
Apr 25 03:17:00 lilypad insmod: Note: /etc/modules.conf is more
recent than /lib/modules/2.2.14/modules.dep
Apr 25 03:17:00 lilypad insmod: Note: /etc/modules.conf is more
recent than /lib/modules/2.2.14/modules.dep
Apr 25 03:17:00 lilypad
On Wed, 3 Mar 1999, Pollywog wrote:
>
> I don't believe I saw anything like that. The errors are about modules such
> as IP forwarding, the modules I installed when I recompiled the kernel.
> I believe another error is about SLIP or PPP but both seem to work.
If you compile something into the ke
On 03-Mar-99 Shaleh wrote:
>
> On 03-Mar-99 Pollywog wrote:
>> I have Debian 2.0 (Hamm) installed (2.0.35 kernel) and I have one small
>> problem that might not really be a problem. If I reboot the machine, I get
>> several errors about not finding modules, yet everything (including IP
>> Masque
>Date: Wed, 03 Mar 1999 13:38:53 -0500 (EST)
>Reply-To: [EMAIL PROTECTED]
>From: Shaleh <[EMAIL PROTECTED]>
>To: Pollywog <[EMAIL PROTECTED]>
>Subject: RE: module errors
>Cc: debian-user@lists.debian.org
>
>
>On 03-Mar-99 Pollywog wrote:
>> I have Debi
On 03-Mar-99 Pollywog wrote:
> I have Debian 2.0 (Hamm) installed (2.0.35 kernel) and I have one small
> problem that might not really be a problem. If I reboot the machine, I get
> several errors about not finding modules, yet everything (including IP
> Masquerade) is working. Why do I see thes
I have Debian 2.0 (Hamm) installed (2.0.35 kernel) and I have one small
problem that might not really be a problem. If I reboot the machine, I get
several errors about not finding modules, yet everything (including IP
Masquerade) is working. Why do I see these errors? I would copy the errors
if
On Fri, 7 Mar 1997, Thought wrote:
> Do you or does anyone else get these errors right after installing Debian?
> I would imagine that at least for the first day or so most everything
> would be error free and ready to go, but maybe not? The only thing I can
> think of that would cause ME to ha
Thought wrote:
> Do you or does anyone else get these errors right after installing Debian?
This happens if you compile a new kernel of the same version (2.0.27).
Modules are copied to /lib/modules/[version], so existing modules are
overwritten if you compiled them again but they aren't deleted.
Do you or does anyone else get these errors right after installing Debian?
I would imagine that at least for the first day or so most everything
would be error free and ready to go, but maybe not? The only thing I can
think of that would cause ME to have these errors and nobody else would be
that
On Thu, 6 Mar 1997, Thought wrote:
> Whenever I run /sbin/depmod -a, I get the following errors:
>
>
> and on and on and on for about 100 more lines... What should I do about
> that? (Oh, and other than /sbin/depmod -a, I followed all of the steps
> you mentioned in the previous reply to the
On Thu, 6 Mar 1997, Kael Rowan - CPTS666 wrote:
> 3c59x ether_setup: wrong version or undefined
> register_netdev: wrong version or undefined
> dev_kfree_skb: wrong version or undefined
> dev_alloc_skb: wrong version or undefined
> eth_type_trans: wrong version or undefined
> netif_rx: wrong ver
Whenever I run /sbin/depmod -a, I get the following errors:
*** Unresolved symbols in module /lib/modules/2.0.27/misc/atixlmouse.o
*** Unresolved symbols in module /lib/modules/2.0.27/misc/busmouse.o
*** Unresolved symbols in module /lib/modules/2.0.27/misc/icn.o
*** Unresolved symbols in module /
On Thu, 6 Mar 1997, Kael Rowan - CPTS666 wrote:
> I just installed a fresh version of Debian 1.2 on my Pentium 166 with
> hardly any modifications to the recommended setup in dselect, (except I
> chose to install the kernel source), and I just recompiled the kernel
> using it's default options alm
I just installed a fresh version of Debian 1.2 on my Pentium 166 with
hardly any modifications to the recommended setup in dselect, (except I
chose to install the kernel source), and I just recompiled the kernel
using it's default options almost exactly (except no SCSI support, etc),
and keep getti
32 matches
Mail list logo
