Luca, RE: Controller-based "Controller-based" is NOT the same as "Controller Chipset" The whole Class 0700 family were "Controller based", but NOT 0780 "Controller Chipset". The functional distinct is that 0780 Controller Chipset modems do all the signal processing on the Modem Card, while for Controller-based modems, much of the processing is done on the CPU. Read the SoftModem.txt for instructions for accessing Device information under Microsoft. It will be interesting to see the Info provided there under about the drivers. I won't have time to examine the code until this evening. MarvS On Wed, Aug 3, 2011 at 11:23 AM, Luca Arzeni <l.arzeni@xxxxxxxxx> wrote: > MarvS, > first of all, thank you very much for your support and time spent on my > problems. > > Second, I cannot explain why the class is 700, I cannot believe that > robotics is lying on their site! > > Regarding " code package", I'm not sure of what code package do you need. > > may be I explained poorly the situation. > >>Incidentally compiled drivers are only useful for the particular kernel >> (resources), they were controlled with. > > Exar gave me the source code for the driver, not the binary. You can > find the file "xr17c15x.c" in the zip that I previously sent to you, > anyway I will attach here for reference. > > I compiled the exar code using my kernel-compiled tree and that went fine. > > It installed ok. > > So it should work. Am I missing something? > > Do you mean the driver? It was in the previous mail, anyway I attach here > again. > > If you want something else, let me know! > > Thanks, Luca > > > > ----- Original Message ----- > > From: Marvin Stodolsky > > Sent: 08/03/11 04:15 PM > > To: Luca Arzeni > > Subject: exar PCI modem > > > > Luca, > > re: Serial controller: U.S. Robotics Device 0152 " > CLASS=0700 > PCIDEV=16ec:0152 > SUBSYS=13a8:0129 > IRQ=18 > > The CLASS=0700 suggests that it is a Winmodem > as Controller Chipset modems are Class 0780 > > Please send me the code package to examine. > > Incidentally compiled drivers are only useful for the particular > kernel (resources), they were controlled with. > > MarvS > > On Wed, Aug 3, 2011 at 6:22 AM, Luca Arzeni <l.arzeni@xxxxxxxxx> wrote: >> Hi MarvS, >> you will find attached the output of scanmodem. >> >> I think it's better to give you other infos to allow a better >> understanding >> of the situation. >> >> 1) This modem (USR Robotics 2891A) is NOT a soft(win)modem but a >> controller >> modem; at least, it's marketed this way, I attach modem specifications >> for >> reference. Actually this was the ONLY reason that made me choose this >> modem! >> >> 2) I was able to find a driver from exar (modem chipset maker); it's >> declared to work for kernel 2.6.37, anyway I compiled a custom kernel >> 2.6.32-5 disabling XR17C152 support, as requested in the readme, and then >> compiled their driver. I installed the custom kernel, and inserted the >> driver in the kernel without problems. I attach the driver if someone >> should >> need in the future. >> >> 3) There were now problems with IRQ sharing, as reported from dmesg: >> root@tiberiade:~# dmesg | grep serial >> [ 5.436146] serial 0000:09:02.0: PCI INT A -> GSI 18 (level, low) -> >> IRQ >> 18 >> [ 5.436153] serial 0000:09:02.0: PCI INT A disabled >> >> I solved this issue poking in the bios, reserving an IRQ for the modem and >> then passing to the kernel the acpi=ht parameter >> >> now dmesg shows: >> >> [ 5.571445] serial 0000:09:02.0: PCI->APIC IRQ transform: INT A -> IRQ >> 18 >> 4) At this point iinstalled the module xr17c15x, and from syslog it seems >> that it's all working fine: >> tiberiade kernel: [ 468.310191] Exar PCI 17c15x serial driver Revision: >> 4.7 >> The main issue, now, is that I cannot see the devices in /dev. >> >> Udev does not detect the driver? >> wvdial does not find the serial. >> >> Can I create manually the device? >> >> I'm stuck at this point. >> >> scanmodem was run with this configuration: custom kernel and custom module >> inserted in the kernel. >> >> That's all. Let me know if you need more info. >> >> From my point of view I am very disappointed with USR Robotics that >> markets >> this modem as fully supported under linux. >> >> I've always rear good reviews of their modem but it seems to me that this >> is >> not true for this model. >> >> Thanks for your help, Luca >> >> >> ----- Original Message ----- >> >> From: Marvin Stodolsky >> >> Sent: 07/29/11 04:15 PM >> >> To: Luca >> >> Subject: Re: cmc, UK kernel 2.6.32-22-generic >> >> Luca >> >> >> Get scanModem from >> http://linmodems.technion.ac.il/ >> and send us the output ModemData.txt >> >> MarvS >> >> On Thu, Jul 28, 2011 at 3:04 PM, Luca <l.arzeni@xxxxxxxxx> wrote: >>> >>> >>> Craig McLaren <craigmc35 <at> googlemail.com> writes: >>> >>> > >>> > Hello All, Please can someone advise what steps are necessary to get >>> > the USR802981-OEM modem working. I have two of these which I plan on >>> > using with Hylafax if they ever work. At the moment the serial port >>> > does not appear to have been created although the device is listed >>> > when I run lspci. I'm assuming they are compatible with Linux in some >>> > way as this is what it says on USR website:- >>> > >>> > http://www.usr.com/support/product-template.asp?prod=oem#2980 >>> > >>> > Any help greatly appreciated. >>> > >>> >>> >>> Hi there, I know that exar released a driver for kernel 2.6.21, but then >>> no >>> other driver come from them. >>> >>> >>> I'm using debian squeeze under AMD-64 (2.6.32-5-amd64) architecture. >>> >>> Have you any success with your attempt? >>> >>> Thanks, Luca >>> >>> >>> >>> >>> >> >> > >
