Thanks Aaron !
dmesg didn't show any Serial driver initializong messages.
cat /proc/ioports did not have any serial information
Digging around I found serial.o in the /lib/modules/2.0.32
and I tried
insmod serial.o - which gave me this:
serial.o kernel module version mismatch
serial.o was compiled for kernel version 2.0.32
while this kernel version 2.0.18
What is weird is:
I did make menuconfig - standard serial support is supposed to be built
in indicated by [*] and it says so. I don't know why it ends up as
module, and to top it all - why do I get a 2.0.18 kernel while I build
it under /usr/src/linux 2.0.32.
I did uname -a and kernel turns out to be a 2.0.18 - I use lilo to load
rh4 (on /dev/hda1) and rh5 (on /dev/hdc1 ) and these kernels are 2.0.18
but different versions.
Am I misssing something in the build process for RH5 ? I've been doing
make clean, make dep, make zImage, make modules, make modules_install
Thanks
-Pradeep
>A few ways I can think of.
>- - run 'dmesg | more' see if there's any serial port inializing
>statments
>- - cat /proc/ioports & look for the lines:
>02f8-02ff : serial(auto)
>03f8-03ff : serial(auto)
>If its compiled as a module but not loaded your won't likely see
>either,
but you can look in /lib/modules/x.y.z/ for the driver.
>On Tue, 19 May 1998, Pradeep Sagam wrote:
>> Is there a way to find out whether the standard serial driver is
>> properly built into the kernel. I have RH 5 but setserial gives
>>'Operation not supported by device' for ttyS* and cua* .
>>
>> Thanks
>>
>> -Pradeep
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
