The kernel release notes @ uk.linux.org seem to
suggest that the module needs to be re-compiled.
Lucent actually got in a 3rd party developer to do
it in the 1st place, & he indicated, when he gave the
driver to linmodems.org, that Lucent were only
interested in dialog with actual manufacturers, not
end users. So it looks like getting the module
re-compiled will mean hassleing the maker of the
modem. Hopefully you'll be able to locate yours,
as mine is made by some obscure Taiwanese Co.
HTH
-WBD
----- Original Message -----
From: "Tom Massey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 20, 2000 11:04 AM
Subject: [expert] LT winmodem with MDK 7.1?
> Hi, I was wondering if anybody has managed to get the Lucent
> linux568.zip driver working with MDK 7.1, kernel 2.2.15-4mdk? Worked
> fine in MDK 6, 6.1, 7, but I can't get it going with 7.1.
>
> Running the ltinst script (as root) gives:
>
> insmod: ltmodem: no module by that name found
>
> Though the script seems to put the module in
> /lib/modules/2.2.15-4mdk/misc, and make the link to /dev/modem etc, just
> doesn't load the module. Strangely, I don't get the usual error message
> about 'kernal mismatch' when running the script. I do get '***unresolved
> symbols in module' at boot when it checks for module dependencies.
>
> But in dmesg I find:
>
> PPP: version 2.3.7 (demand dialling)
> PPP line discipline registered.
> Lucent Modem driver version 4.27.5.66 with MANY_PORTS MULTIPORT
> SHARE_IRQ enabled
> ttyS14 at 0x1000 (irq = 11) is a Lucent
> registered device ppp0
> PPP BSD Compression module registered
> PPP Deflate Compression module registered
>
> Which seems to me to indicate it's detecting and loading it OK, but when
> I try to use it, it dials OK, but then PPPD dies with the error message
> 'Unable to handle kernel NULL pointer dereference'. Anybody know what
> that means? Would I be better off going back to the MDK 7 kernel - and
> if so, does anybody know what works in the new kernel that won't with
> the old one (eg Reiser FS). I'd prefer not to go back to my 14.4
> modem....
>
> Thanks,
> Tom Massey
>
