Re: /dev/ttS?? modules
on Mon, 1 Oct 2001 00:30:30 -0700, Vineet Kumar wrote:
>* Joe Barnett (jbarnett@Stanford.EDU) [010930 23:12]:
>> Hi there,
>> > Whenever I boot up, i get messages from the kernel complaining that
it
>> cannot find ttS?? modules, or /dev/ttS?? modules.
>it would be very helpful if you could post the exact complaint that the
>kernel gives you. If you can't copy and paste it at that moment, it
>should show up in the output of dmesg once the system is up.
hmm... the message is not anywhere in my system logs...
if i recall correctly, there are 3 errors that occur right after each
other, with the second 2 being the same:
modprobe: cannot find module ttS??
modprobe: cannot find module /dev/ttS?? needed by ttS??
modprobe: cannot find module /dev/ttS?? needed by ttS??
(if its apprecialby different from that next time i reboot, i'll post
and let you know)
>> I've gone through kernel configuration options, but cannot seem to
find
>> the option that enables the building of these modules. I would like
to
>> be able to use my serial port, and so was wondering which options I
>> should enable.
>you should just need CONFIG_SERIAL (listed in menuconfig as
>"Standard/generic serial support". This is on (built-in) by default,
and
>there's really no reason it should have been turned off or modularized.
>Did you build a custom kernel and disable it? What version are you
>running? (can be found from 'uname -r'). If you did build a custom
>kernel, did you use the kernel-package tools? if yes, or you're using a
>non-custom (stock) debian kernel, please also give us 'dpkg -l
>"kernel-image-*"', and 'grep CONFIG_SERIAL /boot/config-`uname-r`'.
i'm running a custom compilation of the 2.4.10 kernel build with the
kernel package tools (make-kpkg kernel_image and make-kpkg modules_image
for alsa/nvidia/openafs drivers), and I'm pretty sure that I've got
Standard/generic serial support enabled:
here's output from the grep command:
$ grep CONFIG_SERIAL /boot/config-`uname -r`
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y #these next 3 i added while trying to make it
CONFIG_SERIAL_EXTENDED=y #work, i initially only had CONFIG_SERIAL set
CONFIG_SERIAL_MANY_PORTS=y
# CONFIG_SERIAL_SHARE_IRQ is not set
# CONFIG_SERIAL_DETECT_IRQ is not set
# CONFIG_SERIAL_MULTIPORT is not set
# CONFIG_SERIAL_NONSTANDARD is not set
and here's what the dpkg list spits out:
$ dpkg -l kernel-image-*
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version Description
+++-================-================-================================================
un kernel-image-2.0 <none> (no description available)
un kernel-image-2.0 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.2 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
ii kernel-image-2.4 custom.2.4.10.1 Linux kernel binary image for
version 2.4.10.
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
un kernel-image-2.4 <none> (no description available)
>Also, see what you can see in the output of 'ls -l /dev/ttyS*'. Go
ahead
>and post that here, too, so we can make sure it's correct.
$ ls -l /dev/ttyS*
ls: /dev/ttyS*: No such file or directory
>Sorry, a flowchart would be helpful for my series of questions! I know
I
>ask a lot, but these things will help us figure out what your problem
is
>and how to solve it.
>
>good times,
>
>--
>Vineet
not a problem. I've looked into all of these issues myself, and haven't
found anything that seems to underly the problem. Thanks a bunch
-Joe
Reply to: