Re: Problem with Lucent winmodem on debian 2.2
good luck getting it to work, your best bet is to use the kernel that it
is asking for 2.2.12-20 which probably comes with some version of redhat..
thats one of the problems with binary kernel drivers 99% of the time they
do NOT work on other kernel versions, there is nothing you can do except
ditch the hardware that uses it, or change kernels.
nate
On Sat, 30 Sep 2000, Shaji N V wrote:
nvshaj >Hi,
nvshaj >
nvshaj >I am trying to configure Lucent Winmodem on my HP Pavillion (6735) box with
nvshaj >Debian 2.2. I have followed the instructions from www.linmodems.org for installing the binary only driver provided by Lucent, but still have problems in
nvshaj >loading the driver.
nvshaj >
nvshaj >The following bits should tell the story.. Can someone help me out? The
nvshaj >modem is working fine with Windows ME.
nvshaj >
nvshaj >I am not able to understand what exactly the problem is.
nvshaj >1. Why kernel module is not getting loaded. (Lucent's driver is supposed to support shared IRQ - Shouldn't it probe for the IRQ? Windows ME uses IRQ 3)
nvshaj >2. Why setserial complains about "No such device"
nvshaj >
nvshaj >
nvshaj >Thanks in advance,
nvshaj >Shaji
nvshaj >
nvshaj >
nvshaj >>From insmod -f ltmodem
nvshaj >----------------------
nvshaj >Using /lib/modules/2.2.17/misc/ltmodem.o
nvshaj >Warning: kernel-module version mismatch
nvshaj > /lib/modules/2.2.17/misc/ltmodem.o was compiled for kernel version
nvshaj >2.2.12-20
nvshaj > while this kernel is version 2.2.17
nvshaj >
nvshaj >/lib/modules/2.2.17/misc/ltmodem.o: init_module: Device or resource busy
nvshaj >Hint: this error can be caused by incorrect module parameters, including
nvshaj >invalid IO or IRQ parameters
nvshaj >
nvshaj >
nvshaj >
nvshaj >>From cat /proc/pci
nvshaj >------------------
nvshaj >
nvshaj > Communication controller: Lucent (ex-AT&T) Microelectronics Unknown
nvshaj >device
nvshaj >(rev 0).
nvshaj > Vendor id=11c1. Device id=44e.
nvshaj > Medium devsel. Fast back-to-back capable. Master Capable.
nvshaj >Latency=64.
nvshaj >Min Gnt=252.Max Lat=14.
nvshaj > Non-prefetchable 32 bit memory at 0xf4100000 [0xf4100000].
nvshaj > I/O at 0x3400 [0x3401].
nvshaj > I/O at 0x3000 [0x3001].
nvshaj >
nvshaj >>From /etc/serial.conf
nvshaj >---------------------
nvshaj >
nvshaj ># These are two spare devices you can use to customize for
nvshaj ># some board which is not supported above....
nvshaj >#
nvshaj >/dev/ttyS14 uart 16450 port 0x0260 irq 3
nvshaj >#/dev/ttyS15 uart XXXXX port XXXX irq X
nvshaj >
nvshaj >>From setserial -agv /dev/ttyS*
nvshaj >------------------------------
nvshaj >/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
nvshaj > Baud_base: 115200, close_delay: 50, divisor: 0
nvshaj > closing_wait: 3000
nvshaj > Flags: spd_normal skip_test
nvshaj >
nvshaj >/dev/ttyS1, Line 1, UART: unknown, Port: 0x02f8, IRQ: 3
nvshaj > Baud_base: 115200, close_delay: 50, divisor: 0
nvshaj > closing_wait: 3000
nvshaj > Flags: spd_normal skip_test
nvshaj >
nvshaj >/dev/ttyS14: No such device
nvshaj >/dev/ttyS2, Line 2, UART: unknown, Port: 0x03e8, IRQ: 4
nvshaj > Baud_base: 115200, close_delay: 50, divisor: 0
nvshaj > closing_wait: 3000
nvshaj > Flags: spd_normal skip_test
nvshaj >
nvshaj >/dev/ttyS3, Line 3, UART: unknown, Port: 0x02e8, IRQ: 3
nvshaj > Baud_base: 115200, close_delay: 50, divisor: 0
nvshaj > closing_wait: 3000
nvshaj > Flags: spd_normal
nvshaj >
nvshaj >>From ls -l /dev/ttyS*
nvshaj >---------------------
nvshaj >crw-rw---- 1 root dialout 4, 64 Jul 5 23:14 /dev/ttyS0
nvshaj >crw-rw---- 1 root dialout 4, 65 Jul 5 23:14 /dev/ttyS1
nvshaj >crw-rw---- 1 root dialout 62, 78 Sep 28 05:42 /dev/ttyS14
nvshaj >crw-rw---- 1 root dialout 4, 66 Jul 5 23:14 /dev/ttyS2
nvshaj >crw-rw---- 1 root dialout 4, 67 Jul 5 23:14 /dev/ttyS3
nvshaj >
nvshaj >
:::
http://www.aphroland.org/
http://www.linuxpowered.net/
aphro@aphroland.org
10:02am up 14 days, 17:58, 1 user, load average: 0.16, 0.06, 0.02
Reply to: