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-ATT) 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 0xf410 [0xf410]. 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-ATT) 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 0xef00 [0xef00]. 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 X port 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-rw1 root dialout4, 64 Jul 5 23:14 /dev/ttyS0 crw-rw1 root dialout4, 65 Jul 5 23:14 /dev/ttyS1 crw-rw1 root dialout62, 78 Sep 28 05:42 /dev/ttyS14 crw-rw1 root dialout4, 66 Jul 5 23:14 /dev/ttyS2 crw-rw1 root dialout4, 67 Jul 5 23:14 /dev/ttyS3 Here it's mine: crw-rw-rw-1 root tty4, 14 Mar 25 2000 /dev/tty14 !!Note the difference in minor number. HIH Ciao -- FB
Re: Problem with Lucent winmodem on debian 2.2
At 11.25 30/9/00 -0400, Shaji N V ha escrit: 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 In this case, I suggest you the Winmodems-and-LinuxHOWTO. You don't have the kernel version that requires the Lucent driver. I have also a Pavilion... But well, you are lucky, you at least got the Lucent winmodem, not the Conexant as me. Anyway, I hated that -ahem- modem and I ripped it out from the PC. HP are a bunch of... Well... Best, Ignasi ---\ From Barcelona... \ \\___ / / ___\_'_\ Still nationalizing the LAN! /\¬___/ --/ _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Problem with Lucent winmodem on debian 2.2
Hi,I am trying to configure Lucent Winmodem on my HP Pavillion (6735) box withDebian 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? Themodem 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,ShajiFrom insmod -f ltmodem--Using /lib/modules/2.2.17/misc/ltmodem.oWarning: kernel-module version mismatch/lib/modules/2.2.17/misc/ltmodem.o was compiled for kernel version2.2.12-20while this kernel is version 2.2.17/lib/modules/2.2.17/misc/ltmodem.o: init_module: Device or resource busyHint: this error can be caused by incorrect module parameters, includinginvalid IO or IRQ parametersFrom cat /proc/pci-- Communication controller: Lucent (ex-ATT) Microelectronics Unknowndevice(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 0xf410 [0xf410]. I/O at 0x3400 [0x3401]. I/O at 0x3000 [0x3001].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 X port irq XFrom setserial -agv /dev/ttyS*--/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4Baud_base: 115200, close_delay: 50, divisor: 0closing_wait: 3000Flags: spd_normal skip_test/dev/ttyS1, Line 1, UART: unknown, Port: 0x02f8, IRQ: 3Baud_base: 115200, close_delay: 50, divisor: 0closing_wait: 3000Flags: spd_normal skip_test/dev/ttyS14: No such device/dev/ttyS2, Line 2, UART: unknown, Port: 0x03e8, IRQ: 4Baud_base: 115200, close_delay: 50, divisor: 0closing_wait: 3000Flags: spd_normal skip_test/dev/ttyS3, Line 3, UART: unknown, Port: 0x02e8, IRQ: 3Baud_base: 115200, close_delay: 50, divisor: 0closing_wait: 3000Flags: spd_normalFrom ls -l /dev/ttyS*-crw-rw 1 root dialout 4, 64 Jul 5 23:14 /dev/ttyS0crw-rw 1 root dialout 4, 65 Jul 5 23:14 /dev/ttyS1crw-rw 1 root dialout 62, 78 Sep 28 05:42 /dev/ttyS14crw-rw 1 root dialout 4, 66 Jul 5 23:14 /dev/ttyS2crw-rw 1 root dialout 4, 67 Jul 5 23:14 /dev/ttyS3
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-ATT) 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 0xf410 [0xf410]. 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 X port 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-rw1 root dialout4, 64 Jul 5 23:14 /dev/ttyS0 nvshaj crw-rw1 root dialout4, 65 Jul 5 23:14 /dev/ttyS1 nvshaj crw-rw1 root dialout62, 78 Sep 28 05:42 /dev/ttyS14 nvshaj crw-rw1 root dialout4, 66 Jul 5 23:14 /dev/ttyS2 nvshaj crw-rw1 root dialout4, 67 Jul 5 23:14 /dev/ttyS3 nvshaj nvshaj ::: http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED] 10:02am up 14 days, 17:58, 1 user, load average: 0.16, 0.06, 0.02
Re: Problem with Lucent winmodem on debian 2.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A long time ago, in a galaxy far, far way, someone said... 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) Detecting the IRQ isn't the problem. The driver is built for RedHat 6.1 (who has a long history of heavily patching their kernels), and what you're using is a *hell* a lot more recent. I was going to suggest insmod -f, but I see you alreay tried that :) Since that didn't work, I have to say that you're really out of luck. I hope you didn't pay much for the modem... As to why it doesn't work: A good analogy is you're trying to load a driver for Win95 into WinME - the kernels are wy to different for the driver to load. In Linux, the driver is very sensitive to the kernel it's being loaded in to. If someone uses a different compiler from you, or, more importantly, has a different set of patches from you when they built the driver, there's a very good chance that the driver won't load. 2. Why setserial complains about No such device The driver wasn't loaded. 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 /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 [...] - -- - -- Phil Brutsche [EMAIL PROTECTED] GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC GPG key id: 50DE1CFC GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE51jYI/ZTSZFDeHPwRApQ7AKDUe++f4tXNJ2I8H9UYvjWZUbmtigCdHg2A ey7Rw3+6z22vkTf63QuflxY= =wrZJ -END PGP SIGNATURE-
