Here is all the information. again lost all my account settings in Evolution. :( -------------------------------- bart@bart-vast:~$ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.17. bart@bart-vast:~$ uname -r 2.6.27-9-generic bart@bart-vast:~$ sudo tail -f /var/log/messages > /home/bart/error.txt bart@bart-vast:~$ sudo modprobe agrmodem bart@bart-vast:~$ sudo modprobe agrserial bart@bart-vast:~$ sudo ln -s /dev/ttyAGS3 /dev/modem bart@bart-vast:~$ sudo agrsm-test I can't give you the exact output, but it is something 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 ----- crash!!! -------------- bart@bart-vast:~$ cat error.txt Jan 7 21:13:37 bart-vast -- MARK -- Jan 7 21:33:37 bart-vast -- MARK -- Jan 7 21:53:37 bart-vast -- MARK -- Jan 7 22:00:30 bart-vast kernel: [11240.627546] ati_remote: Weird data, len=5 20 b0 44 20 10 00 ... Jan 7 22:13:37 bart-vast -- MARK -- Jan 7 22:23:18 bart-vast kernel: [12609.034640] * Hello Agere Driver ** Jan 7 22:23:19 bart-vast kernel: [12609.047995] pci 0000:02:05.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 Jan 7 22:23:32 bart-vast kernel: [12622.104195] ttyAGS3 at I/O 0x8004 (irq = 16) is a AgereModem Jan 7 22:23:32 bart-vast kernel: [12622.106152] Loading module Agere Modem Interface driver version 2.1.80.0 (2008-10-31) Jan 7 22:33:37 bart-vast -- MARK -- bart@bart-vast:~$ --------------------------- Does this help? Bart Verbeek Op woensdag 07-01-2009 om 17:49 uur [tijdzone -0400], schreef Bjorn Wielens: > 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 > >>>>>>>>> > >>> > > > > >
