[ale] Debian 2.2 + Kernel 2.4

David Corbin dcorbin at imperitek.com
Mon Dec 31 11:14:29 EST 2001


I've reach the conclusion that was caused by me enabling the "serial 
console" when I rebuilt the kernel.  It seemed like a good idea at the 
time, as I don't normally have a monitor attached to this system, but my 
laptop is often nearby.

Thanks.

hirsch at zapmedia.com wrote:

>The errors about respawing too fast are the getty that run on the
>vitural terminals (VTs).  I wonder if you have /dev/tty1, /dev/tty2,
>etc.
>
>Are you logging in directly to X?  If so, what happens if you do
>CTRL-ALT-F1?  Do you get the login prompt?
>
>I wonder if there is a problem with devfs.  I think that is standard
>with 2.4.x, but requires a patch for 2.2.x.  If your system didn't use
>it before but the new kernel does, or vice versa you could get these
>kinds of messages.
>
>--Michael
>
>David Corbin writes:
> > I've a debian 2.2 system.  I need USB support, so I figured I'd upgrade 
> > to Kernel 2.4.17 (the latest).
>
> > 
> > I followed the instructions available from debian, which basically says 
> > to upgrade a bunch of packages.  Built the kernel, and booted.
> > 
> > Everything is functioning OK, from my perspective, but in the syslog 
> > file I find
> > 
> > Dec 30 14:25:12 mercury modprobe: modprobe: Can't locate module char-major-4
> > Dec 30 14:25:43 mercury last message repeated 22 times
> > Dec 30 14:26:43 mercury last message repeated 37 times
> > Dec 30 14:26:52 mercury init: Id "1" respawning too fast: disabled for 5 
> > minutes
> > Dec 30 14:26:52 mercury init: Id "2" respawning too fast: disabled for 5 
> > minutes
> > Dec 30 14:26:52 mercury init: Id "3" respawning too fast: disabled for 5 
> > minutes
> > Dec 30 14:26:52 mercury init: Id "4" respawning too fast: disabled for 5 
> > minutes
> > Dec 30 14:26:53 mercury init: Id "5" respawning too fast: disabled for 5 
> > minutes
> > Dec 30 14:26:53 mercury init: Id "6" respawning too fast: disabled for 5 
> > minutes
> > 
> > Now, I don't KNOW that this started when I upgraded my kernel, but it is 
> > likely.  Anybody want to make any suggestions?
> > 
> > Thanks.
> > David
> > 
> > 
> > ---
> > This message has been sent through the ALE general discussion list.
> > See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
> > sent to listmaster at ale dot org.
>
>
>
>




---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.






More information about the Ale mailing list