Joshua, Thanks. Shamefully you are correct. There earlier compile must have been a folder in which I experimented with the When I compiled from a fresh package, all was OK, per below. Sadly we still have a few agrmodem users who are still trying to achieve modem recognition by moving the card around and other means. MarvS $ sudo modprobe agrmodem [ 2890.596000] agrsm: created 0 infos $ sudo modprobe agrserial [ 2921.588000] ttyAGS3 at I/O 0x400 (irq = 3) is a AgereModem [ 2921.588000] agrserial: Loading module Agere Modem Interface driver version 2.1.60.0.Linspire (2005-11-16) On Feb 2, 2008 9:54 PM, Joshua Gordon Crawford <jgcrawford@xxxxxxxxx> wrote: > On 02/02/2008, Joshua Gordon Crawford <jgcrawford@xxxxxxxxx> wrote: > > On 02/02/2008, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > 1) You might be able to change IRQs by moving the modem card to a > > > different PCI slot, or by setting the IRQ in the BIOS if it supports > > > that action. > > > > I was hopng there'd be an option I could use with the driver. I'll > > switch slots later today and let you know how it goes. There's no > > setting like that in my BIOS that I've noticed, but I'll have a > > another look when I reboot next. > > No BIOS options for assigning IRQ's, not even to onboard devices like > sound and video. Switching pci slots worked. > > > > 2) It would be interesting to exchange the agrmodemlib.o between the > > > two packages, and check functionality effects. > > > > I'll try this later today also. I'm currently in the middle of a bunch > > of downloads that have piled up during the downtime. > > This results in unresolved symbols, as I've explained further in a > different thread. A sample error log attached. > > > > 3) Since Hugo has function with agrsm package under a Ubuntu 2.6.22, > > > you could try progressively upgrading your kernel to assess where the > > > code breaks under Slackware. Thus you might be able to do a code fix > > > needed for Slack kernels > > > > That'll be a lot of compiling and rebooting. I'll do it after the > > weekend, when I have more time on my hands. > > So it turns out I'm not working this weekend after all, and I've been > trying out different kernels. It works on 2.6.19, 2.6.20 as well as > the 2.6.18 I already reported. Here's where it gets weird though - it > also works on 2.6.21.5, which I compiled from the sources and config > file which came from Slackware 12.0. I repeat - because it sounds > unbelievable - agrsm-20070804 didn't work on the kernel shipped with > Slack 12.0, but does on a kernel compiled from the same source and > config. > > I stopped testing at that point. Frankly, kernel compiles are too time > consuming and rebooting this often is sending my phone bill through > the roof. > > Something I noticed during testing, is that if I remove the modules > (rmmod), then later reload them (modprobe), the modem isn't detected. > When the driver is unloaded the modem makes the click sound like it's > being reset. > > I couldn't get the suse-10-2a driver to work on any of the kernels I > compiled. 2.6.18 had a different error to the later versions. I've > attached some error logs in case Hugo, Alan, or anyone else wants them > for their own info. All attachments were created by "make module 2> > errors.txt" > > -- > Joshua Crawford ... http://geocities.com/mortarn > > http://www.emailcash.com.au/join.asp?refer=G84381 > Emailcash - Free rewards for shopping online >
