Re: ThinkPad R31 - Lucent windmodem woes....
Sorry to hear that you got stuck with an mWave ISDN part. I didn't know such a thing existed. Heh. It's *huge*, it's a full-length ISA card - about the only one I've ever seen, modulo the Archive QIC-02 interfaces I still have... Still, it came with a free IBM NT-1, which is worth more than I paid for the mWave, so I don't feel gouged at all. :) Cheers, AS msg51951/pgp0.pgp Description: PGP signature
Re: ThinkPad R31 - Lucent windmodem woes....
Date: Mon, 25 Nov 2002 10:23:23 -0800 From: Wes Peters [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] P.A.Osborne wrote: On Mon, Nov 25, 2002 at 07:54:32AM -0800, Wes Peters wrote: cual0 (or sio0) is almost certainly NOT your winmodem. I suspect it is an onboard serial or IR port, as is sio1. More reading of the ltmdm documentation might reveal how to discover what sio device node is associated with the winmodem when the module attaches. You'll then need to use the /dev/MAKEDEV script to create /dev entries for that sio node if you don't already have them. Thats the problem exactly! If I *knew* what device it really mapped to then I would be laughing, finding that out seems to be nigh on impossible, hence my mail asking if anyone had been round these hoops and succeeded. The last time I tried ltmdm (quite some time ago) it seemed to take the first non-allocated sio, which would be sio2 in your case. It's at least a good starting point. Or you could do like the rest of us and buy a pccard modem that doesn't suck. ;^) That is something that I don't want to do until I am certain that the winmodem is not an option. If you do get it working you're not likely to be impressed by the through- put or the load imposed on your system. I certainly wasn't. I believe IBM is now using the ICH3 chipset which includes the Agre (nee Lucent) AC'97 WinModem. This is a different beast from the older Lucent WinModems and, unless something has recently changed, it is not supported under FreeBSD with the ltmdm port. FWIW, under Windows, the new modem is vastly superior to my older internal modem on my 600E. I get better data rates and more reliable connections, but it does load the CPU quite a bit. Still, as little as I use a modem, it would be fine if there was an available driver. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ThinkPad R31 - Lucent windmodem woes....
On Mon, Nov 25, 2002 at 10:23:23AM -0800, Wes Peters wrote: If I *knew* what device it really mapped to then I would be laughing, finding that out seems to be nigh on impossible, hence my mail asking if anyone had been round these hoops and succeeded. The last time I tried ltmdm (quite some time ago) it seemed to take the first non-allocated sio, which would be sio2 in your case. It's at least a good starting point. Ok I will give that a go in a bit, thanks. That is something that I don't want to do until I am certain that the winmodem is not an option. If you do get it working you're not likely to be impressed by the through- put or the load imposed on your system. I certainly wasn't. Thats kind of what I am expecting mainly die to the bad press (with good reason) in the past. However the modem runs find under WinXP with no noticeable major increase in load on the CPU - hence I dont't want to buy a real modem unless I have to. Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ThinkPad R31 - Lucent windmodem woes....
On Mon, Nov 25, 2002 at 11:04:20AM -0800, Kevin Oberman wrote: I believe IBM is now using the ICH3 chipset which includes the Agre (nee Lucent) AC'97 WinModem. This is a different beast from the older Lucent WinModems and, unless something has recently changed, it is not supported under FreeBSD with the ltmdm port. Yes thats the beast, in which case: rats! FWIW, under Windows, the new modem is vastly superior to my older internal modem on my 600E. I get better data rates and more reliable connections, but it does load the CPU quite a bit. Still, as little as I use a modem, it would be fine if there was an available driver. Thats my thought exactly - at work the laptop is on the net any way - it would just be nice to be able to dial up on it using FreeBSD than currently being forced to use Windows ( as I am at the moment to ssh to work). Ho hum Paul To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ThinkPad R31 - Lucent windmodem woes....
Sender: [EMAIL PROTECTED] Date: Mon, 25 Nov 2002 13:21:15 -0800 From: Wes Peters [EMAIL PROTECTED] I believe IBM is now using the ICH3 chipset which includes the Agre (nee Lucent) AC'97 WinModem. This is a different beast from the older Lucent WinModems and, unless something has recently changed, it is not supported under FreeBSD with the ltmdm port. FWIW, under Windows, the new modem is vastly superior to my older internal modem on my 600E. I get better data rates and more reliable connections, but it does load the CPU quite a bit. Still, as little as I use a modem, it would be fine if there was an available driver. Thanks for the update. It might be worth checking to see if the new chipset is supported under Linux. Porting the changes for the chipset to FreeBSD may be easier than porting the entire driver. It is supported under Linux with a binary-only driver supplied by Agre. Of course, this driver will not run under FreeBSD, so it will be necessary to write shims similar to those in the ltmdm port. I believe Watanabe-san was either working on these or he was posting information from others working on them on his web page. Because this modem is included in the very popular ICH sets, I am hopeful that it won't take too much longer, but I don't have a clue about Linux kernel modules, so I am not in a position to contribute much to this. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ThinkPad R31 - Lucent windmodem woes....
To rudely follow up my own posts, I have been unable to reach Watanabe-san's web page. At least the English language page seems to have moved or gone away. Also the message I had seen that I thought implied he was working on it really was relating to an issue of a different flavor of Lucent WinModem. At this time I am unsure if anyone is working on this seriously. Larry Rosenman was trying to track something down on this, but I have not seen any recent messages. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ThinkPad R31 - Lucent windmodem woes....
On Tue, 2002-11-26 at 02:24, Wes Peters wrote: luthien# ppp Working in interactive mode Using interface: tun0 ppp ON luthien dial isp Warning: deflink: /dev/cual0: Bad file descriptor ppp ON luthien However the file is there: luthien# ls -la /dev/cual0 crw-rw 1 uucp dialer 228, 128 Nov 25 10:29 /dev/cual0 cual0 (or sio0) is almost certainly NOT your winmodem. I suspect it is an onboard serial or IR port, as is sio1. More reading of the ltmdm documentation might reveal how to discover what sio device node is associated with the winmodem when the module attaches. You'll then need to use the /dev/MAKEDEV script to create /dev entries for that sio node if you don't already have them. Actually, cual0 IS the ltmdm device node name.. (Along with ttyl0) Of course it doesn't work if the driver doesn't attach. If Paul runs dmesg | grep ltmdm he should see a line like - ltmdm0: Lucent Winmodem port 0xe800-0xe8ff,0xecb8-0xecbf mem 0xf8ffec00-0xf8ffecff irq 11 at device 8.0 on pci8 ltmdm0: type Virtual 16550A If not it wasn't detected. In that case it either isn't a lucent winmodem, or, if it is the PCI ID isn't known. BTW while on general principle I don't like win modems etc, these ones DO seem to work quite well. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
