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

Re: Problem with Lucent winmodem on debian 2.2



On Sat, Sep 30, 2000 at 11:25:30AM -0400, Shaji N V wrote:
> Hi,
> 
> I am trying to configure Lucent Winmodem on my HP Pavillion (6735) box with
> 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 
> loading the driver.
> 
> The following bits should tell the story.. Can someone help me out? The
> modem is working fine with Windows ME.
> 
> I am not able to understand what exactly the problem is. 
> 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)
> 2. Why setserial complains about "No such device"
> 
> 
> Thanks in advance,
> Shaji
> 
Hi,
I have ltmodem working on my Potato boxes ( both laptop and desktop ), and
will try to help. Check also archives of debian-user and debian-laptop :
there have been others thread on this subject with some interesting info.

> 
> >From insmod -f ltmodem
> ----------------------
> Using /lib/modules/2.2.17/misc/ltmodem.o
> Warning: kernel-module version mismatch
>  /lib/modules/2.2.17/misc/ltmodem.o was compiled for kernel version
> 2.2.12-20
>  while this kernel is version 2.2.17
>

BIG PROBLEM : ltmodem.o works fine up to kerner 2.2.14. After that, changes
in ppp.o broke someting. With 2.2.17, I am  able to load
it and to dial, but the kernel panics as soon as ppp.o module is loaded.

There is a 'dirt-trick' whis works for somebody ( not for me, until now ):
it consists of compiling two kernels, say 2.2.17 and 2.2.14, with the same
options, then substitute the ppp.o in 2.2.14 to the ppp.o in 2.2.17.
  
I currentrly use 2.2.13. :-(

Note : when I compile the kernel, I include the following options:

Support more than 4 serial ports
Support for sharing serial interrupts

Dunno if this matters. I checked the options after having seen this message from ltmodem :

Lucent Modem driver version 4.27.5.66 with MANY_PORTS MULTIPORT SHARE_IRQ enabled

 
> /lib/modules/2.2.17/misc/ltmodem.o: init_module: Device or resource busy
> Hint: this error can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters
> 
>
Strange. I currently don't have any option in /etc/modules and the module
install fines ( I do have option for ltmodem on my Laptop, but that has
the ISA version of ltmodem ).


> 
> >From cat /proc/pci
> ------------------
> 
>     Communication controller: Lucent (ex-AT&T) Microelectronics Unknown
> device
> (rev 0).
>       Vendor id=11c1. Device id=44e.
>       Medium devsel.  Fast back-to-back capable.  Master Capable.
> Latency=64.
> Min Gnt=252.Max Lat=14.
>       Non-prefetchable 32 bit memory at 0xf4100000 [0xf4100000].
>       I/O at 0x3400 [0x3401].
>       I/O at 0x3000 [0x3001].


This is mine ( different, but it could be because I have ltmodem loaded):

  Bus  0, device  16, function  0:
    Communication controller: Lucent (ex-AT&T) Microelectronics L56xMF (rev 1).
      Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master Capable.  No bursts.  Min Gnt=252.Max Lat=14.
      Non-prefetchable 32 bit memory at 0xefffff00 [0xefffff00].
      I/O at 0xc400 [0xc401].
      I/O at 0xc000 [0xc001].



> 
> >From /etc/serial.conf
> ---------------------
> 
> # These are two spare devices you can use to customize for
> # some board which is not supported above....
> #
> /dev/ttyS14 uart 16450 port 0x0260 irq 3
> #/dev/ttyS15 uart XXXXX port XXXX irq X
> 


No. I still have both commented. I'd bet this is the problem.



> >From setserial -agv /dev/ttyS*
> ------------------------------
> /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
>  Baud_base: 115200, close_delay: 50, divisor: 0
>  closing_wait: 3000
>  Flags: spd_normal skip_test
> 
> /dev/ttyS1, Line 1, UART: unknown, Port: 0x02f8, IRQ: 3
>  Baud_base: 115200, close_delay: 50, divisor: 0
>  closing_wait: 3000
>  Flags: spd_normal skip_test
> 
> /dev/ttyS14: No such device
> /dev/ttyS2, Line 2, UART: unknown, Port: 0x03e8, IRQ: 4
>  Baud_base: 115200, close_delay: 50, divisor: 0
>  closing_wait: 3000
>  Flags: spd_normal skip_test
> 
> /dev/ttyS3, Line 3, UART: unknown, Port: 0x02e8, IRQ: 3
>  Baud_base: 115200, close_delay: 50, divisor: 0
>  closing_wait: 3000
>  Flags: spd_normal
>

This is mine (skipping unimportant bits):

/dev/ttyS14, Line 14, UART: 16950/954, Port: 0xc000, IRQ: 2
	Baud_base: 115200, close_delay: 50, divisor: 0
	closing_wait: 3000
	Flags: spd_normal skip_test

 
> >From ls -l /dev/ttyS*
> ---------------------
> crw-rw----    1 root     dialout    4,  64 Jul  5 23:14 /dev/ttyS0
> crw-rw----    1 root     dialout    4,  65 Jul  5 23:14 /dev/ttyS1
> crw-rw----    1 root     dialout    62,  78 Sep 28 05:42 /dev/ttyS14
> crw-rw----    1 root     dialout    4,  66 Jul  5 23:14 /dev/ttyS2
> crw-rw----    1 root     dialout    4,  67 Jul  5 23:14 /dev/ttyS3
> 

Here it's mine:

crw-rw-rw-    1 root     tty        4,  14 Mar 25  2000 /dev/tty14


!!Note the difference in minor number.


HIH


Ciao
-- 
FB







Reply to: