Walt In addition to the modem drivers there is needed packages through: http://packages.ubuntu.com/gutsy/i386/linux-libc-dev/download http://packages.ubuntu.com/gutsy/libc6-dev http://packages.ubuntu.com/gutsy/i386/binutils http://packages.ubuntu.com/gutsy/i386/linux-headers-2.6.22-14 http://packages.ubuntu.com/gutsy/i386/linux-headers-2.6.22-14-generic --- Once imported to a Linux folder, they can all be installed by: $ sudo dpkg -i *.deb This preparation is actually the worst part of the total job: After getting http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/martian-full-20071011.tar.gz Unpack with: $ tar zxf martain*.tar.gz move into the new folder $ cd martian-full-20071011 look around $ ls prepare to compile: $ make clean Compie with: $ make Install with $ sudo make install Browse the documentation in the package. Load the driver: $ sudo modprobe martian_dev Get more info: $ martian_modem --help Activate the modem with: $ sudo martian_modem --country=us Open a 2nd console and $ sudo wvdialconf /etc/wvdial.conf should find the modem and write /etc/wvdial.conf Edit in your dialout info with: $ sudo gedit /etc/wvdial.conf also adding a line: Carrier Check = no Then dialout with: $ sudo wvdial MarvS On Mon, Mar 10, 2008 at 12:59 PM, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > Folks > Walt has sweated getting through his ModemData.txt to me because discuss > was rejecting his mails. > > He needs the martian driver for a 2.6.22-14-generic [Gutsy, I thought it > would be Feisty but never mind]. > > Has anyone compiled that combination? > > Walt: if you want to try on your own, start with > http://martian.barrelsoutofbond.org/ , read background and instructions > Download > http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/martian-full-20071011.tar.gz > (more recent that last at http://martian.barrelsoutofbond.org/) > Also you probably have a Lucent.txt or Agere.txt in the Modem directory > where ModemData.txt was generated, > > Good luck, don't give up, and we continue to be here to help you. > FYI linmodems.org is not my site, we have no control of it except the owner, > > Jacques > > > Walt wrote: > > I've used Ubuntu Dapper for about 1 year. Winmodem was automagically detected and useable without a thought. > > > > I've had attempted to upgrade Dapper > Edgy > Feisty > Gutsy via Synaptic following the recommended click the buttons to upgrade. > > > > Winmodem is not automagically detected in Gutsy. I've strived to locate solutions via Google and forums. Yours is the closest I've found. > > > > I went back and copied the key lines from dmesg for Dapper where finding the modem wasn't an issue: > > [17179595.536000] Loading Lucent Modem Controller driver version 8.26-alk-8 > > [17179595.540000] PCI: Found IRQ 9 for device 0000:02:0b.0 > > [17179595.540000] PCI: Sharing IRQ 9 with 0000:00:1f.4 > > [17179595.540000] Detected Parameters Irq=9 BaseAddress=0xb400 ComAddress=0xb800[17179595.540000] ttyLTM0 at I/O 0xb400 (irq = 9) is a Lucent/Agere Modem > > [17179595.564000] bttv: driver version 0.9.16 loaded > > > > I can see lines within ModemData.txt with 'matching' data: > > =========================================================== > > For candidate card in slot 02:0b.0, firmware information and bootup diagnostics are: > > PCI slot PCI ID SubsystemID Name > > ---------- --------- --------- -------------- > > 02:0b.0 11c1:044e 13e0:0401 Communication controller: Agere Systems LT WinModem > > Modem interrupt assignment and sharing: > > 9: 53384 XT-PIC-XT uhci_hcd:usb2, bttv0, bttv1, bttv2, bttv3, eth0 > > --- Bootup diagnostics for card in PCI slot 02:0b.0 ---- > > [ 30.409339] PCI: Sharing IRQ 9 with 0000:02:0b.0 > > =========================================================== > > > > I am at a point of dizziness from wvdial, wvdialconf, pppconfig, setserial, modprobe, trying to find driver 8.26-alk-8, etc. etc. The latest is your MIME Cop that refuses my online Yahoo email. I feel like I am being forced to an Entropy change: a change to a more disordered state. > > > > It seems like is should be SO easy, but has proven elusive. > > > > A helpful solution would be greatly welcomed. >
