Hi Bart, Looks like you don't have the kernel source package installed? I can see it's using the headers, but you will need to install the full sources for the module to build successfully. Bjorn. Bart Verbeek wrote: > Hi Marvin and Bjorn, > Last message disappeared I think. > > > I took this rpm first: > http://linux.zsolttech.com/linmodem/agrsm/dkms-agrsm-2.1.80-4mdv2009.0.i586.rpm > But extracting gave me errors. There is something wrong with that file. > After that the deb file: > http://linux.zsolttech.com/linmodem/agrsm/dkms-agrsm_2.1.80-5_i386.deb > did extract well. > But sudo make module gave me this error: > > make[2]: *** Er is geen regel om doel 'kernel/bounds.c' te maken, nodig > voor 'kernel/bounds.s'. Gestopt. > make[1]: *** [prepare0] Fout 2 > make[1]: Map '/usr/src/linux-headers-2.6.27-9-generic' wordt verlaten > make: *** [module] Fout 2 > > I'm afraid it is in Dutch, but that won't be a problem for Bjorn I > suppose ;) > (there is no rule to make target 'kernel/bounds.c') > > I have to go a long way to make this modem working! > Does anyone have any suggestions please? > Bart > > > > Op donderdag 08-01-2009 om 08:53 uur [tijdzone -0500], schreef Marvin > Stodolsky: >> Bart, >> Go ahead and test. >> >> Bjorn, >> The deb variants are just conversions from the original rpm format. >> The source packages are at http://linux.zsolttech.com/linmodem/agrsm/ >> For Ubuntu users, I've been doing the compiles and putting the >> compiled drivers in kernel-version specific installer packages. >> >> Marvin >> >> On Thu, Jan 8, 2009 at 7:00 AM, Bjorn Wielens <Uniacke1@xxxxxxxx> wrote: >>> Hi Bart, >>> To my knowledge, that is only a .deb version of the RPM I referred you to. >>> The link for the howto might be too long to paste in an e-mail, so visit >>> this link: >>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ >>> and click the howto... 2nd file down after 'Parent directory'. (first >>> one is in russian) >>> You also shouldn't need to perform any of the steps that deal with >>> modifying the hda_codec.c code/building ALSA either. >>> Hope that helps, >>> Bjorn. >>> >>> >>> >>> Bart Verbeek wrote: >>>> Hi all, >>>> Thanks a lot for all your input in this! >>>> I notice another package in this directory named: >>>> dkms-agrsm_2.1.80-5_i386.deb >>>> This seems to be a newer version?! Could I use that instead? >>>> >>>> I tied this link: >>>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/HOWTO-Agere-11c= >>>> 11040-HDA.html >>>> But it gives me a "not found". >>>> >>>> Bart >>>> >>>> >>>> >>>> Bart, >>>> >>>> The modem's IRQ 11 is not shared with other devices. >>>> So that is not a problem. The drivers I provided in the installer.deb >>>> were compiled with code from the >>>> http://linux.zsolttech.com/linmodem/agrsm/dkms-agrsm-2.1.80-4mdv2009.0.i586.rpm' >>>> >>>> MarvS >>>> >>>> On Wed, Jan 7, 2009 at 6:19 PM, Bart Verbeek <ahverbeek@xxxxxxxxx> >>>> wrote: >>>>> bart@bart-vast:~$ lspci -s 02:05.0 -nv >>>>> 02:05.0 0780: 11c1:0620 >>>>> Subsystem: 11c1:0620 >>>>> Flags: bus master, medium devsel, latency 32, IRQ 11 >>>>> I/O ports at ea00 [size=256] >>>>> Capabilities: [f8] Power Management version 3 >>>>> >>>>> bart@bart-vast:~$ cat /proc/interrupts >>>>> CPU0 CPU1 >>>>> 0: 133 0 IO-APIC-edge timer >>>>> 1: 2 0 IO-APIC-edge i8042 >>>>> 3: 7 0 IO-APIC-edge >>>>> 8: 128 0 IO-APIC-edge rtc0 >>>>> 9: 0 0 IO-APIC-fasteoi acpi >>>>> 12: 4 0 IO-APIC-edge i8042 >>>>> 14: 35340 0 IO-APIC-edge ata_piix >>>>> 15: 0 0 IO-APIC-edge ata_piix >>>>> 16: 302023 0 IO-APIC-fasteoi uhci_hcd:usb4, HDA >>>> Intel, >>>>> nvidia >>>>> 17: 336 0 IO-APIC-fasteoi saa7133[0], saa7133[0] >>>>> 18: 6146 0 IO-APIC-fasteoi uhci_hcd:usb3, eth0 >>>>> 19: 91854 0 IO-APIC-fasteoi uhci_hcd:usb2, >>>> ohci1394, >>>>> ata_piix >>>>> 20: 341 0 IO-APIC-fasteoi saa7133[1], saa7133[1] >>>>> 23: 121385 0 IO-APIC-fasteoi uhci_hcd:usb1, >>>>> ehci_hcd:usb5 >>>>> NMI: 0 0 Non-maskable interrupts >>>>> LOC: 259182 267599 Local timer interrupts >>>>> RES: 12250 13235 Rescheduling interrupts >>>>> CAL: 30977 39244 function call interrupts >>>>> TLB: 2832 3236 TLB shootdowns >>>>> SPU: 0 0 Spurious interrupts >>>>> ERR: 0 >>>>> MIS: 0 >>>>> >>>>> Bart >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Op woensdag 07-01-2009 om 18:15 uur [tijdzone -0500], schreef Marvin >>>>> Stodolsky: >>>>>> Bart, >>>>>> >>>>>> Please return outputs of >>>>>> $ lspci -s 02:05.0 -nv >>>>>> $ cat /proc/interrupts >>>>>> >>>>>> Also try simplying your System by detaching external devices and >>>>>> shutting down as much as possible before testing the modem. >>>>>> >>>>>> MarvS >>>>>> >>>>>> On Wed, Jan 7, 2009 at 4:49 PM, Bjorn Wielens <Uniacke1@xxxxxxxx> >>>> wrote: >>>>>>> Hi Bart, >>>>>>> Yes, it can be built from source, I'll get to that in a moment. >>>>>>> However, can you please attach the error.txt file? I would like to >>>> see >>>>>>> if this is the routine hangup that can happen with some >>>> configurations, >>>>>>> or whether it is something else. >>>>>>> >>>>>>> Also, what is your ALSA version? (found by issuing 'cat >>>>>>> /proc/asound/version') >>>>>>> Thanks! >>>>>>> Bjorn. >>>>>>> >>>>>>> >>>>>>> Bart Verbeek wrote: >>>>>>>> I got now relevant output to this error.txt file. >>>>>>>> It is a total system hangup, caused by the driver/module agrmodem >>>> and/or >>>>>>>> agrserial. As soon as some application directs this module, the >>>> system >>>>>>>> hangs. I should do a disk check now. :-( >>>>>>>> I almost lost some settings and data from evolution because of >>>> this. >>>>>>>> Fortunately I managed to solve that. >>>>>>>> Is there a newer version of this module, or is it possible to >>>> build it >>>>>>>> from source? If so, where do I find this source package? >>>>>>>> Bart >>>>>>>> >>>>>>>> >>>>>>>> Op woensdag 07-01-2009 om 13:33 uur [tijdzone -0400], schreef >>>> Bjorn >>>>>>>> Wielens: >>>>>>>>> Hi Bart, >>>>>>>>> Sounds like the agrsm driver itself may be hanging... >>>>>>>>> You can catch the error message by issuing >>>>>>>>> 'tail -f /var/log/messages > err.txt' before hanging the >>>> system... >>>>>>>>> Upon reboot, then the err.txt file will have the output of >>>>>>>>> /var/log/messages just before it crashed. >>>>>>>>> You can forward that and we'll look at it. >>>>>>>>> HTH, >>>>>>>>> Bjorn. >>>>>>>>> >>>>>>>>> >>>>>>>>> Bart Verbeek wrote: >>>>>>>>>> Hi Jacques, >>>>>>>>>> Thanks for your reply! >>>>>>>>>> It is not only X that hangs. It is strange enough, the whole >>>> system. >>>>>>>>>> First thing I try is CTRL-ALT-F2 or F3. But no response to this >>>> nor Ctrl >>>>>>>>>> +Alt-Backspace. Even the SysRq does not respond. >>>>>>>>>> >>>>>>>>>> I've version 1.60.1+nmu2 installed. Force version is greyed out >>>> in >>>>>>>>>> Synaptic. Any suggestions how to try an older version on Ubuntu >>>> Intrepid >>>>>>>>>> 8.10? >>>>>>>>>> Bart >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Op woensdag 07-01-2009 om 17:37 uur [tijdzone +0200], schreef >>>> Jacques >>>>>>>>>> Goldberg: >>>>>>>>>>> Bart, >>>>>>>>>>> I have seen such things in the past when a then recent, >>>> possibly still >>>>>>>>>>> distributed, version of wvdialconf was starting to search for >>>> USB and >>>>>>>>>>> other more exotic hardware after failing to find >>>> any /dev/ttyS* device. >>>>>>>>>>> I believe that I can suggest a new test with an older version >>>> of wvdialconf. >>>>>>>>>>> I am using 1.54 since long and never felt any need for anything >>>> else. >>>>>>>>>>> Something else: when your machine hangs, have you tried to see >>>> if it >>>>>>>>>>> could be that X11, not the machine, has ceased to respond? >>>>>>>>>>> >>>>>>>>>>> One way is to try to restart it is to CTRL-SHIFT-BACKSPACE. >>>>>>>>>>> An other way, the one I prefer, is to CTRL-SHIFT-F1 to try to >>>> open >>>>>>>>>>> an ASCII pseudo-terminal (console). ps ax then shows all >>>> running >>>>>>>>>>> tasks, making it possible to kill the process which blocks you, >>>> probably >>>>>>>>>>> wvdialconf. >>>>>>>>>>> >>>>>>>>>>> Good luck >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Bart Verbeek wrote: >>>>>>>>>>>> Marv S, >>>>>>>>>>>> I first tried the sudo agrsm-test as suggested by dpkg after >>>> the >>>>>>>>>>>> install. This hanged my system. >>>>>>>>>>>> >>>>>>>>>>>> Then I manually loaded the drivers as described in usages.txt >>>>>>>>>>>> sudo modprobe agrmodem and sudo modprobe agrserial >>>>>>>>>>>> >>>>>>>>>>>> This did not give me a message as expected that /dev/ttyAGS3 >>>> was >>>>>>>>>>>> created. But I checked /dev/ and /dev/ttyAGS3 is actually >>>> there. >>>>>>>>>>>> I created symbolic links: >>>>>>>>>>>> sudo ln -s /dev/ttyAGS3 /dev/ttySAGR and sudo ln >>>>>>>>>>>> -s /dev/ttyAGS3 /dev/modem >>>>>>>>>>>> as described in usages.txt >>>>>>>>>>>> >>>>>>>>>>>> So both sudo agrsm-test and wvdialconf give me a totally >>>> hanged system. >>>>>>>>>>>> I attached a photo from the frozen screen/computer. >>>>>>>>>>>> >>>>>>>>>>>> noacpi did not help me either. I do not get a workable screen >>>> with Xorg >>>>>>>>>>>> then (Nvidia). >>>>>>>>>>>> Is there anything else I could try? >>>>>>>>>>>> Bart >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Op woensdag 07-01-2009 om 08:40 uur [tijdzone -0500], schreef >>>> Marvin >>>>>>>>>>>> Stodolsky: >>>>>>>>>>>>> Bart, >>>>>>>>>>>>> >>>>>>>>>>>>> The drivers likely aren't loaded, or there should be >>>> an /dev/ttySAGR >>>>>>>>>>>>> for wvdialconf to fine. It is the agrsm-tools which provides >>>> for this >>>>>>>>>>>>> symbolic link >>>>>>>>>>>>> Make sure your boot is into 2.6.27-9-generic >>>>>>>>>>>>> >>>>>>>>>>>>> Either >>>>>>>>>>>>> $ sudo agrsm-test >>>>>>>>>>>>> or >>>>>>>>>>>>> $ modprobe agrserial >>>>>>>>>>>>> >>>>>>>>>>>>> $ ls -l /dev/ttySAGR >>>>>>>>>>>>> before the wvdialconf >>>>>>>>>>>>> >>>>>>>>>>>>> Marv S >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Jan 7, 2009 at 7:39 AM, Bart Verbeek >>>> <ahverbeek@xxxxxxxxx> wrote: >>>>>>>>>>>>>> Thanks MarvS, >>>>>>>>>>>>>> I've installed those deb's and did some testing with: >>>>>>>>>>>>>> sudo wvdialconf /etc/wvdial.conf >>>>>>>>>>>>>> If I do this I get an output like this: >>>>>>>>>>>>>> A failure will include lines like: >>>>>>>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: >>>> 9600 baud >>>>>>>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: >>>> 115200 baud >>>>>>>>>>>>>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving >>>> up. >>>>>>>>>>>>>> Modem Port Scan<*1>: S1 S2 S3 >>>>>>>>>>>>>> >>>>>>>>>>>>>> At that point the system hangs totally! Not even the SysRq >>>> is >>>>>>>>>>>>>> responding! >>>>>>>>>>>>>> >>>>>>>>>>>>>> Would pci=noacpi in Grub fix this? >>>>>>>>>>>>>> Bart >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Op woensdag 07-01-2009 om 07:04 uur [tijdzone -0500], >>>> schreef Marvin >>>>>>>>>>>>>> Stodolsky: >>>>>>>>>>>>>>> Bart >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> from >>>> http://phep2.technion.ac.il/linmodems/packages/ltmodem/11c11040/ get >>>>>>>>>>>>>>> agrsm-2.6.27-9-generic_2.6.27-9.14_i386.deb and >>>> agrsm-tools_0.0.1_all.deb >>>>>>>>>>>>>>> Coinstall with: >>>>>>>>>>>>>>> $ sudo dpkg -i agrsm*.deb >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> There will be troubleshooting instructions in >>>>>>>>>>>>>>> /usr/share/doc/agrsm-tools/usage.txt >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> There has been service of modems >>>>>>>>>>>>>>> Communication controller: Agere Systems Device 0620" >>>>>>>>>>>>>>> PCIDEV=11c1:0620 >>>>>>>>>>>>>>> modems under 2.6.24 kernels. Report back presently. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> scanModem should have output this info automatically. >>>>>>>>>>>>>>> I may send you an update to test. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> MarvS >>>>>>>>>>>>>>> scanModem maintainer >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Jan 7, 2009 at 6:31 AM, Bart Verbeek >>>> <ahverbeek@xxxxxxxxx> wrote: >>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>> I've read here: >>>>>>>>>>>>>>>> >>>> http://www.nabble.com/11c1:0620-or-11c1:048c-or-11c1:048f-td20592361.html >>>>>>>>>>>>>>>> That possibly there is a .deb file available to get this >>>> modem working >>>>>>>>>>>>>>>> on Ubuntu?! >>>>>>>>>>>>>>>> Would someone please help me with this modem? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> scanout.02:05.0: >>>>>>>>>>>>>>>> CLASS=0780 >>>>>>>>>>>>>>>> NAME="Communication controller: Agere Systems Device 0620" >>>>>>>>>>>>>>>> PCIDEV=11c1:0620 >>>>>>>>>>>>>>>> SUBSYS=11c1:0620 >>>>>>>>>>>>>>>> IRQ=11 >>>>>>>>>>>>>>>> HDA= >>>>>>>>>>>>>>>> CodecDiagnosed= >>>>>>>>>>>>>>>> slamrTest= >>>>>>>>>>>>>>>> CodecClass= >>>>>>>>>>>>>>>> IDENT=SV2P >>>>>>>>>>>>>>>> SLMODEMD_DEVICE= >>>>>>>>>>>>>>>> OPTS= >>>>>>>>>>>>>>>> Driver=agrmodem+agrserial >>>>>>>>>>>>>>>> DRIVER=agrmodem+agrserial >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Kind regards, >>>>>>>>>>>>>>>> Bart Verbeek >>>>>>>>>>>>>>>> >>>> >>>> --------------060602050400000807030001-- >>>> >>>> >>>> >>> > >
Attachment:
signature.asc
Description: OpenPGP digital signature
