Josh, The bootup diagnostics have no indication of the modem hardward being interrogated. So without an interrupt (IRQ) assigned to it, the CPU is latter completely unaware of its existence. >From http://linmodems.technion.ac.il/packages/ download the unloading.gz and under Linux $ gunzip unloading.gz $ chmod +x unloading to be used in necessary latter. Shut down Please try detaching all non-essential external devices (USB, pcmcia, memory cards, etc) to minimize any related reservation of resources. Reboot Try the driver pair loading and wvdialconf test again, If the modem is not detected, unload the drivers $ sudo modprobe -r agrserial $ sudo modprobe -r agrmodem The unloading script does a coarse job of unloading non-essential resources during: $ sudo ./unloading Hopefully this will not crash your System Afterward again run the $ sudo modprobe agrmodem $ sudo modprobe agrserial $ sudo wvdialconf /etc/wvdial.conf If the modem is not thus detected, the last several lines from the output of $ dmesg will have info on the driver loading. Copy those out and send them to us. MarvS http://linmodems.technion.ac.il/packages/ On Sat, Feb 23, 2008 at 2:55 PM, Josh Smith <josh.a.smitty@xxxxxxxxx> wrote: > Alright, here is an updated ModemData.txt and dmesg.txt, I hope you > mean send this to discuss@xxxxxxxxxxxxxx Thanks!!! > > > > On 2/23/08, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > Alexei, > > > > RE: > > ================ > > For candidate card in slot 02:02.0, firmware information and bootup > > diagnostics are: > > PCI slot PCI ID SubsystemID Name > > ---------- --------- --------- -------------- > > 02:02.0 11c1:0620 11c1:0620 Communication controller: Agere Systems > > Unknown device 0620 > > > > Modem interrupt assignment and sharing: > > --- Bootup diagnostics for card in PCI slot 02:02.0 ---- > > (no 02:02.0 lines detected in dmesg buffer ) > > ================ > > In several cases like this, it seems that the bootup diagnostics fail > > to detect the agrmodem card at all!!. THis is with your acpi patch in > > the code. Any suggestions??? > > > > Josh, > > Just after a bootup do: > > $ dmesg > dmesg.txt > > Send the List the dmesg.txt and a fresh ModemData.txt > > We need more detail on events during the bootup. > > > > MarvS > > > > > > On Sat, Feb 23, 2008 at 12:12 AM, Josh Smith <josh.a.smitty@xxxxxxxxx> > > wrote: > > > I have now also tried moving the modem to all other PCI slots and ran > > > the tests for each one, still displaying the same message. Any > > > suggestions? > > > > > > > > > > > > > > > ---------- Forwarded message ---------- > > > From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> > > > Date: Fri, Feb 22, 2008 at 2:16 PM > > > Subject: Re: Josh, Canada, kernel 2.6.22-14-generic > > > To: Josh Smith <josh.a.smitty@xxxxxxxxx>, discussions@xxxxxxxxxxxxx > > > > > > > > > Josh, > > > > > > All you have done is technically OK > > > ----------- > > > josh@Rusty:~$ sudo modprobe agrmodem > > > josh@Rusty:~$ sudo modprobe agrserial > > > josh@Rusty:~$ sudo ln -s /dev/ttyAGS3 /dev/ttySAGR > > > josh@Rusty:~$ sudo ln -s /dev/ttyAGS3 /dev/modem > > > josh@Rusty:~$ lsmod | grep agr > > > agrserial 13984 0 > > > agrmodem 1188644 1 agrserial > > > josh@Rusty:~$ sudo wvdialconf /etc/wvdial.conf > > > Editing `/etc/wvdial.conf'. > > > > > > Scanning your serial ports for a modem. > > > > > > Modem Port Scan<*1>: S0 S1 S2 S3 > > > ttySAGR<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > > > ttySAGR<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > > > ttySAGR<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > > > ------------------- > > > > > > You are encountering the typical problem with this modem. > > > If possible, try changing the PCI slot in which the modem is seated and > > retest. > > > Please send to the List, Not direct to me, as others have more > > > expertise with this modem > > > > > > MarvS > > > > > > > > > > > > On Fri, Feb 22, 2008 at 2:59 PM, Josh Smith <josh.a.smitty@xxxxxxxxx> > > wrote: > > > > So far I have had no luck detecting my modem. I've checked > > > > /lib/modules/2.2.6.22-14-generic/extras/ and both agrmodem.ko and > > > > agrserial.ko are present. I've also tried adding pci=noacpi to the > > > > end of the kernel line in menu.lst In the txt file I've attached is > > > > the readout from the terminal in trying to get my modem detected. > > > > > > > > > > > > > > > > On Thu, Feb 21, 2008 at 6:49 PM, Marvin Stodolsky > > > > <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > Jacques > > > > > The http://linmodems.technion.ac.il/ seems to be down. > > > > > > > > > > Josh > > > > > > > > > > For candidate modem in PCI bus: 02:02.0 > > > > > Class 0780: 11c1:0620 Communication controller: Agere Systems > > > > > Unknown device 0620 > > > > > Primary PCI_id 11c1:0620 > > > > > Support type needed or chipset: Agere.SV2P > > > > > > > > > > At http://linmodems.technion.ac.il/packages/ltmodem/sv92/ > > > > > you need the agrsm-20070804.tar.gz > > > > > Download it into your Linux partition. > > > > > Unpack with > > > > > $ tar zxf agr*.tar.gz > > > > > which will create a agrsm folder. Move in with > > > > > $ cd agrsm > > > > > Look around > > > > > $ ls > > > > > Browse the doumentation. Compile with: > > > > > $ make clean > > > > > $ make > > > > > will compile the components > > > > > $ sudo make install > > > > > installs the components. Read the agrsm-howto.txt for setup > > details > > > > > > > > > > Write back if you need help. > > > > > > > > > > MarvS > > > > > scanModem maintainer > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Feb 21, 2008 at 1:17 PM, Josh Smith > > > <josh.a.smitty@xxxxxxxxx> wrote: > > > > > > Hey, I'm completely new to linux. I'd really appreciate it if > > you > > > > > > could help me out by directing me to what drivers I need and > > how to > > > > > > compile them if I need to. Thanks!!! > > > > > > > > > > > > > > > > > > > > >
