[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Newbie question (long)



I just recompiled my kernel using kernel 2.0.32, and everything seems to
work well, except when I boot I get the following error messages which I
take it means I screwed something up.  (Is this because I configured serial
support as a module?)  Any help would be appreciated.

Apr 15 21:03:05 debian kerneld: started, pid=100, qid=0
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol interruptible_sleep_on_R5f048a24
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol current_set_R05befc2c
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol do_SAK_R05806a11
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol tty_hangup_Rdf445228
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol tty_wait_until_sent_Rbf069f6a
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol wake_up_interruptible_R21a13bff
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol tty_unregister_driver_R23ac7468
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol tty_register_driver_R95283511
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol tty_check_change_Rd5a4b270
Apr 15 21:03:05 debian insmod: /lib/modules/2.0.32/misc/serial.o: unresolved
symbol tty_hung_up_p_Ra25cb81c
Apr 15 21:03:06 debian modprobe: can't locate module binfmt-0
Apr 15 21:03:06 debian modprobe: can't locate module binfmt-0
Apr 15 21:04:18 debian init: Switching to runlevel: 6
Apr 15 21:04:24 debian modprobe: can't locate module binfmt-0
Apr 15 21:04:24 debian modprobe: can't locate module binfmt-0

Cam Vetter
camvet@mia.net
camvettk@uwc.edu
ICQ UIN: 545211


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: