A Internal Winmodem that works on 3.4 but not 6.0?
Posts: 7
Hello Warren and Team,
My Modem is a Dynalink 1456VQH-T4 Agere / Lucent Mars 3.2 Chipset internal Dial-up Modem.
This Modem works fine in Mepis 3.4-3 but drops out before connecting in Mepis 6.0 Final.
I even download Mepis 2004 build around June and it works fine with my modem.
I compared the modem scripts between 3.4 and 6.0 and there wasn't any real difference.
I even copied 3.4's modem scripts into 6.0 with no luck?
Has the change to the Ubuntu base from Debian made the difference?
I hope this will be fixed in Upcoming releases.
One last work is that if it wasn't for Simply Mepis 3.4 I wouldn't or couldn't be a Linux user, So thank you for your hard work and I hope the info above might help towards fixing the problem.
lucent winmodem
Posts: 13
I have a thinkpad a20m with a lucent internal winmodem working from the live CD Mepis 6.0. It also worked on the earlier Mepis 3.4.3 For reference,
lspci reports the following:
Communication controller: Agere Systems WinModem 56k (rev 01)
Unfortunately, I have no Idea why it works for me and not for others. But it does work. See
http://www.mepis.org/node/11783#comment-44191
Though, this will not get yours working.
Confirmation
Posts: 275
Just to confirm a similar experience. My Agere/Lucent modem (not in front of me right now...can't get more specific) worked fine under all versions except when I upgraded to 6.0 b2. It dials and connects but conks out before log-in.
I've done all the tweaking recommended here and elsewhere, but with no luck. Simply Mepis 3.4 and MepisLite both work fine.
--Malanrich