[CLOSED] Problem with Agere HDA modem on HP550 laptop

Message
Author
User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

[CLOSED] Problem with Agere HDA modem on HP550 laptop

#1 Post by peebee »

[edit5]Closed again after experiments to get the modem working under lupu528 failed. See the post of 5 Oct 2011 on page 3 for advice on using these modems in puppy[/edit4]

[edit4] Reopened to discuss getting the Agere working on lupu528
[/edit4]

[edit3]
A further update - success to report....
jrb has written a wonderful howto http://www.murga-linux.com/puppy/viewtopic.php?t=60180
explaining how to change the kernel version in any puppy. By changing the kernel in Lupu511 to the one used in Wary060 K2.6.32.1 I now have a schizophrenic puppy that starts up as Wary060 but then behaves like Lupu511 EXCEPT that it can talk to my modem - WONDERFUL.
[/edit3]

[edit2]
Just to note that the progress with Wary 060 unfortunately didn't carry over into Wary 070 - but am hopeful that Barry and Rerwin are on the case and it will be solved soon...
[/edit2]

[edit]
SOLVED - partly - see above
I'm pleased to report that after loading the agrmodem and agrserial modules that are included in Wary 0.6 then my Agere HDA modem now works using Wary 0.6.
As Wary and Lucid Puppy use different kernels it isn't possible to move the modules to Lucid Puppy unfortunately but I can live with a dual boot system with both Wary for when I need a modem and Puppy 5 Lucid.
[/edit]



Any clues on how to get this modem working please?

Using Puppy 4.2.1 on an HP550 laptop

Windows Vista comes pre-installed and reports that the modem is an Agere Systems HDA modem on com3 with manufacturer:model id = 11c1:1040

Tried Internet Connection Wizard - couldn't see a modem at all but suggested force loading of agrserial which I've done

Internet Connection Wizard now says that it has detected a modem on /dev/ttyAGS3

However modem-stats /dev/ttyAGS3 says "Segmentation Fault"

and the Internet Connection Wizard cannot access the modem.

dmesg after the modem-stats command reports:

agrmodem: module license 'Proprietary' taints kernel.
agrsm: created 0 infos
Loading module Agere Modem Controller driver version 2.1.60.0.Linspire (2005-11-16)
ttyAGS3 at I/O 0x400 (irq = 3) is a AgereModem
agrserial: Loading module Agere Modem Interface driver version 2.1.60.0.Linspire (2005-11-16)

BUG: unable to handle kernel NULL pointer dereference at 00000004
IP: [<f8e49d23>] :agrmodem:LXSoftModemStart+0x23/0x230
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: snd_pcm_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_mixer_oss agrserial agrmodem(P) arc4 ecb crypto_blkcipher b43 mac80211 cfg80211 ohci_hcd serio_raw ssb pcspkr snd_hda_intel snd_pcm snd_timer snd soundcore snd_page_alloc e1000e intel_agp agpgart video output wmi fan battery container evdev thermal button processor ac fuse aufs nls_iso8859_1 nls_cp437 usbhid usb_storage ehci_hcd uhci_hcd usbcore squashfs

Pid: 31073, comm: modem-stats Tainted: P (2.6.25.16 #1)
EIP: 0060:[<f8e49d23>] EFLAGS: 00210296 CPU: 0
EIP is at LXSoftModemStart+0x23/0x230 [agrmodem]
EAX: 00000008 EBX: e22ce9c0 ECX: fffb6000 EDX: f8abda40
ESI: 00000000 EDI: f8abdf70 EBP: e233fe24 ESP: e233fd9c
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process modem-stats (pid: 31073, ti=e233e000 task=e237daa0 task.ti=e233e000)
Stack: 00000c6c 00000008 f8e847e1 fffffffd fffffffc 00000001 00330000 c04460d4
c14f6260 c14f6260 c14f6260 c01414f2 00000001 00000044 e7b13000 00000000
c04460f0 c04460d4 00000001 00000000 000280d0 c04468ac 00000000 00000001
Call Trace:
[<c01414f2>] get_page_from_freelist+0x262/0x430
[<c014171f>] __alloc_pages+0x5f/0x380
[<f8e452f6>] linux_modem_open+0x26/0x110 [agrmodem]
[<f8d9f3a5>] modemPortOpen+0x5/0x10 [agrmodem]
[<f8abc1d5>] serial8250_startup+0x185/0x260 [agrserial]
[<c0280158>] uart_startup+0x48/0x130
[<c0281bc4>] uart_open+0xe4/0x390
[<c02276ff>] kobject_get+0xf/0x20
[<c026f7a4>] tty_open+0x144/0x2b0
[<c015d10e>] chrdev_open+0x6e/0x140
[<c015d0a0>] chrdev_open+0x0/0x140
[<c0159119>] __dentry_open+0xa9/0x1b0
[<c0159267>] nameidata_to_filp+0x47/0x60
[<c01592d0>] do_filp_open+0x50/0x60
[<c0158fe2>] get_unused_fd_flags+0x42/0xc0
[<c0159330>] do_sys_open+0x50/0xf0
[<c015944c>] sys_open+0x2c/0x40
[<c0104002>] syscall_call+0x7/0xb
[<c0370000>] setup_cpu_cache+0xa0/0x100
=======================
Code: 00 89 d8 eb a7 8d 76 00 55 b8 e1 47 e8 f8 89 e5 57 56 53 83 ec 7c 8b 75 08 89 44 24 08 c7 45 e4 78 56 34 12 8d 46 08 89 44 24 04 <8b> 46 04 89 04 24 e8 e2 13 00 00 85 c0 89 c3 0f 88 68 01 00 00
EIP: [<f8e49d23>] LXSoftModemStart+0x23/0x230 [agrmodem] SS:ESP 0068:e233fd9c
---[ end trace fb65068c4d0e52ee ]---
Attachments
screen230910.jpg
(69.05 KiB) Downloaded 1940 times
Last edited by peebee on Wed 05 Oct 2011, 19:07, edited 6 times in total.

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#2 Post by rerwin »

peebee,
Interesting problem. It appears that support for this modem type is a work in progress. Puppy apparently has an old driver (judging from the 2005 date). I have been working with modem support for a while, but have not attended to the Ageres.

The information I found from the experts (responsible for it) indicate a sound-driver modification is needed, as well as upgrading to a recent agere driver. I am putting this on my to-do list, to update Puppy's drivers, but cannot get to it for some time.

Barry Kauler,
The newest driver is "dkms-agrsm_2.1.80-7_i386.deb" and the Howto for updating the snd-hda-intel alsa driver is "HOWTO-Agere-11c11040-HDA.html", both from http://linmodems.technion.ac.il/package ... /11c11040/
The linuxant patch could also be added to this update. I could work this if I had access to the source for the alsa-driver 1.0.16. In addition, the udev rule for Agere modems probably needs ID 11c1:1040 added to it.
Richard

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Thanks

#3 Post by peebee »

Thanks Richard - if you do get round to it, let me know and i'll be pleased to test it out for you.
The HP550 is a bargain basement laptop - £250 in the UK - (so combines nicely with PuppyLinux) and works great apart from the modem on 4.2.......

Cheers
Peter

dialeddown
Posts: 20
Joined: Mon 26 Apr 2010, 00:39

#4 Post by dialeddown »

rerwin wrote:peebee,
Interesting problem. It appears that support for this modem type is a work in progress. Puppy apparently has an old driver (judging from the 2005 date). I have been working with modem support for a while, but have not attended to the Ageres.

The information I found from the experts (responsible for it) indicate a sound-driver modification is needed, as well as upgrading to a recent agere driver. I am putting this on my to-do list, to update Puppy's drivers, but cannot get to it for some time.

Barry Kauler,
The newest driver is "dkms-agrsm_2.1.80-7_i386.deb" and the Howto for updating the snd-hda-intel alsa driver is "HOWTO-Agere-11c11040-HDA.html", both from http://linmodems.technion.ac.il/package ... /11c11040/
The linuxant patch could also be added to this update. I could work this if I had access to the source for the alsa-driver 1.0.16. In addition, the udev rule for Agere modems probably needs ID 11c1:1040 added to it.
Richard
Hello. Does puppy 4.3.1 have the linuxant patch for alsa? I did not see a udev rule for agere.

I have the same modem as peebee, http://murga-linux.com/puppy/viewtopic.php?t=54805 .

Thank you.

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#5 Post by rerwin »

dialeddown,
As I recall, when I created the agere rules, I apparently gave up on trying to support the Agere HDA modems. Things just didn't look ready. Or I wasn't. It seems a patch is needed to a piece of the ALSA HDA sound driver, that was beyond what I could deal with.

Although I think I saw a later version of the driver, I cannot attack that issue for a while. But the ALSA patch makes things complicated, which is why I am holding off.

Anyway, the obvious rule to add to /etc/udev/rules.d/60-dialup-modem.rules would be:

Code: Select all

ATTR{vendor}=="0x11c1", ATTR{device}=="0x1040", ACTION=="add", RUN+="/sbin/pup_event_backend_modprobe agrserial"
You could try that, to see haw far you get, but I fear the absence of the ALSA-HDA patch will prevent it from working.
Richard

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#6 Post by peebee »

Hi Richard

Many thanks for your continued interest and help.

I am still very interested to get this modem to work on my HP550....

Since my original post I have moved on to Puppy 4.3.1 K2.6.30.5

I have applied the edit you have suggested and have force loaded modules agrserial and agrmodem

The connection wizard says that /dev/ttyAGS3 is detected as a modem but then a Test of the modem says it is not responding

modem-stats no longer crashes but just hangs with no response

relevent lines from dmesg are below

I guess you are right that the ALSA patch (which just seems to export some symbols?? but I'm no expert!) and maybe later driver versions are needed.

Cheers
Peter

dmesg output:
agrmodem: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
agrsm: created 0 infos
Loading module Agere Modem Controller driver version 2.1.60.0.Linspire (2005-11-16)
ttyAGS3 at I/O 0x400 (irq = 3) is a AgereModem
agrserial: Loading module Agere Modem Interface driver version 2.1.60.0.Linspire (2005-11-16)

Modules linked in: parport_pc lp parport snd_pcm_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_mixer_oss rfkill_input agrserial agrmodem(P) arc4 ecb b43 mac80211 input_polldev led_class ohci_hcd rfkill cfg80211 serio_raw pcspkr snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_pcm snd_page_alloc shpchp snd_timer snd pci_hotplug soundcore e1000e intel_agp agpgart video output wmi fan battery container thermal evdev button ac processor fuse aufs nls_iso8859_1 nls_cp437 usbhid usb_storage squashfs ssb uhci_hcd ehci_hcd usbcore

Pid: 6563, comm: modem-stats Tainted: P (2.6.30.5 #1) HP 550
EIP: 0060:[<f8766d53>] EFLAGS: 00210296 CPU: 0
EIP is at LXSoftModemStart+0x23/0x230 [agrmodem]
EAX: 00000008 EBX: f6bac1f8 ECX: fffb6000 EDX: f87eb3c0
ESI: 00000000 EDI: f6bac208 EBP: ed649de4 ESP: ed649d5c
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modem-stats (pid: 6563, ti=ed648000 task=f68e0040 task.ti=ed648000)
Stack:
c15ab620 00000008 f87a182b c01653c5 00000001 00000044 00200246 ed5b1000
00000000 c05a7380 c053cf80 00000001 00000000 00000000 000280d0 c053da6c
00200246 00000000 00000000 00000001 00000000 c053cf80 c053cf80 f6bac1f8
Call Trace:
[<c01653c5>] ? get_page_from_freelist+0x2e5/0x470
[<f8762326>] ? linux_modem_open+0x26/0x110 [agrmodem]
[<c011ea8e>] ? __wake_up+0x3e/0x60
[<f86bc3a5>] ? modemPortOpen+0x5/0x10 [agrmodem]
[<f87e9ae5>] ? serial8250_startup+0x195/0x270 [agrserial]
[<c0300a7c>] ? uart_startup+0x4c/0x150
[<c0302259>] ? uart_open+0x109/0x360
[<c02e9394>] ? check_tty_count+0x14/0xb0
[<c02eb61c>] ? tty_init_dev+0x8c/0x160
[<c02999cf>] ? kobject_get+0xf/0x20
[<c02eb8b9>] ? tty_open+0x1c9/0x430
[<c0189795>] ? chrdev_open+0x95/0x150
[<c0189700>] ? chrdev_open+0x0/0x150
[<c0184c1e>] ? __dentry_open+0xbe/0x240
[<c0185d53>] ? nameidata_to_filp+0x53/0x70
[<c0191272>] ? do_filp_open+0x1e2/0x7a0
[<c01722e9>] ? __do_fault+0x2c9/0x3f0
[<c01849fa>] ? do_sys_open+0x5a/0x100
[<c0184b1c>] ? sys_open+0x2c/0x40
[<c0102e05>] ? syscall_call+0x7/0xb
Code: 00 89 d8 eb a7 8d 76 00 55 b8 2b 18 7a f8 89 e5 57 56 53 83 ec 7c 8b 75 08 89 44 24 08 c7 45 e4 78 56 34 12 8d 46 08 89 44 24 04 <8b> 46 04 89 04 24 e8 e2 13 00 00 85 c0 89 c3 0f 88 68 01 00 00
EIP: [<f8766d53>] LXSoftModemStart+0x23/0x230 [agrmodem] SS:ESP 0068:ed649d5c
CR2: 0000000000000004
---[ end trace 00061c9f96950fc0 ]---

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#7 Post by rerwin »

peebee,
Thanks for trying my suggestion. That result sounds familiar. The dmesg listing shows that the modem-stats program "crashed" trying to communicate with the modem.

About the patch, I have seen a statement that the patch is no longer needed after a driver version ...3, whereas they are now beyond that level. So, I don't know whether is is needed or not. But another killer is that apparently the driver is not ready for the current version of the ALSA driver (1.0.20). There are so many various versions of the driver in the 11c1:1040 download directory, that it is not clear which to use. The latest date may have other constraints. All that will take more digging to sort out.

I hope you now understand why I have had to "back burner" this modem, as I try to keep up with the evolution of the USB wireless modems (not to mention the outside commitments I am delaying to support puppy).
Richard

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#8 Post by peebee »

Hi Richard
Fully understood - but if you have more ideas and suggestions I wait ready to try them out.
Cheers
Peter

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Agere modem still not supported in Puppy 5.0.1

#9 Post by peebee »

Just tried the new Puppy 5.0.1 and it appears that my modem Agere HDA 11c1 1040 is still not supported.

However I also notice that there is at http://linmodems.technion.ac.il/package ... /11c11040/
a source package agrsm-11c11040_20091225_i386.deb which may support for this modem? However compiliing this is beyond my capabilities.....

But maybe somebody can do to provide support for this modem??

Cheers
Peter

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: Agere modem still not supported in Puppy 5.0.1

#10 Post by peebee »

peebee wrote:Just tried the new Puppy 5.0.1 and it appears that my modem Agere HDA 11c1 1040 is still not supported.

However I also notice that there is at http://linmodems.technion.ac.il/package ... /11c11040/
a source package agrsm-11c11040_20091225_i386.deb which may support for this modem? However compiliing this is beyond my capabilities.....

But maybe somebody can do to provide support for this modem??

Cheers
Peter
Now solved with Wary 0.6 (but not yet for Wary 0.7) - see edit to my first post.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: Agere modem still not supported in Puppy 5.0.1

#11 Post by peebee »

peebee wrote:
Now solved with Wary 0.6 (but not yet for Wary 0.7) - see edit to my first post.
Now solved in general by using jrb's how-to swap the kernel in any puppy - see edit3 to first post.

dialeddown
Posts: 20
Joined: Mon 26 Apr 2010, 00:39

Re: Agere modem still not supported in Puppy 5.0.1

#12 Post by dialeddown »

peebee wrote:
peebee wrote:Just tried the new Puppy 5.0.1 and it appears that my modem Agere HDA 11c1 1040 is still not supported.

However I also notice that there is at http://linmodems.technion.ac.il/package ... /11c11040/
a source package agrsm-11c11040_20091225_i386.deb which may support for this modem? However compiliing this is beyond my capabilities.....

But maybe somebody can do to provide support for this modem??

Cheers
Peter
Now solved with Wary 0.6 (but not yet for Wary 0.7) - see edit to my first post.


Hello. Can anyone confirm that this modem chip when mounted on the sound card works, or are people talking about the chip on some other device?

I tried Wary 060 but saw no improvement. Can anyone confirm that a fresh Wary 060 works, or does it need patches and packages added?

Does anyone have instructions for the sound-card version?

Thank you.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Re: Agere modem still not supported in Puppy 5.0.1

#13 Post by peebee »

dialeddown wrote:Hello. Can anyone confirm that this modem chip when mounted on the sound card works, or are people talking about the chip on some other device?
Thank you.
Hi there
wary504 contains support for 2 variants of this modem - see Barry's post:
http://bkhome.org/blog/?viewDetailed=02134

The one NOT supported is: agrsm048pci-2.1.60_20091022

Download wary504 here: http://bkhome.org/blog/?viewDetailed=02146

wary500 which is based on an earlier kernel should support all 3 variants.

Download wary500 here: http://bkhome.org/blog/?viewDetailed=02057
Cheers
Peter

dialeddown
Posts: 20
Joined: Mon 26 Apr 2010, 00:39

#14 Post by dialeddown »

The 504 worked better and says modem initialized but stops at no carrier or modem not responding.

Can someone post their working conf settings or describe the process that worked for them, starting with a fresh 504?

Thank you.

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Need to ask an expert..

#15 Post by peebee »

dialeddown wrote:The 504 worked better and says modem initialized but stops at no carrier or modem not responding.

Can someone post their working conf settings or describe the process that worked for them, starting with a fresh 504?

Thank you.
wary510 has now been released - have you tried the k2.6.31 version??

Suggest you need the help of the modem expert rerwin - best way would be to start a topic in Forum index » Advanced Topics » Hardware » Networking » Dialup

or pm him with the results of pmodemdiag - as he explains to another enquirer here: http://www.murga-linux.com/puppy/viewto ... 096#482971

You will need to give him as much detail of your setup as possible - including details of how and where the modem is connected and which model it is if possible - although pmodemdiag collects this for him.

Cheers
Peter

dialeddown
Posts: 20
Joined: Mon 26 Apr 2010, 00:39

#16 Post by dialeddown »


User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

Problem returns on lupu5.2.8

#17 Post by peebee »

Hi Richard (rerwin)

You asked in the other thread Drivers for Puppy 5.1-5.2.8 with 2.6.33.2 kernel http://www.murga-linux.com/puppy/viewto ... 248#564248:
peebee,
I see your statements of a year ago about success with wary 060 or 070, or such. Where did all that end up? Does wary 5.12 work for you?

BTW, to keep this thread dedicated to providing drivers without the clutter of debugging conversations, we should take this discussion elsewhere. How about to your original thread on this subject?
http://www.murga-linux.com/puppy/viewto ... 455#322455
Richard
I can confirm that all Wary's up to and including Wary 5.1.4.1 have been working fine - it will be interesting to see what happens when 5.2 / Racy is posted as I think Barry is moving to a later kernel there too (but I think Barry has an incentive as he has a laptop with this modem??)

I'll test your alternative driver tonight (got to go to work now).

Cheers
peebee
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#18 Post by BarryK »

peebee,
No, no change in kernel for Wary, it will continue with the 2.6.32.x kernel indefinitely.

Racy is something else, a "Wary on steroids", but because it has recent Xorg and kernel it looses the support for some older hardware that Wary has.
[url]https://bkhome.org/news/[/url]

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#19 Post by peebee »

Hi Richard

I tried the .pet you posted - I'm afraid it crashed just like the previous version.

Perhaps Barry could tell you how he got the Agere code working for Wary??

One difference I notice in Wary is that the modem is called ttyAGS3 in dmesg when its loading but in pupdial its called ttyS_AGS3 ......

This item on Barry's blog http://bkhome.org/blog/?viewDetailed=01890 talks about missing symbols and also some Alsa dependency....

http://bkhome.org/blog/?viewDetailed=01961

Cheers
Peter

dmesg output:

Code: Select all

serial8250_register_ports: BaseAddress 0x4004 Irq 29 
ttyAGS3 at I/O 0x4004 (irq = 29) is a AgereModem
agrserial - ret_val 0, call: lt_modem_ops.init_modem
Loading module Agere Modem Interface driver version 2.1.80.0 (2007-10-01)
==> codecType = 0x32
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<f882c9bb>] AzlDmaAllocation+0x81/0x2f9 [agrmodem]
*pde = 00000000 
Oops: 0002 [#1] SMP 
last sysfs file: /sys/devices/pci0000:00/0000:00:1c.1/0000:10:00.0/ssb0:0/net/wlan0/statistics/tx_bytes
Modules linked in: i915 drm_kms_helper drm i2c_algo_bit i2c_core agrserial arc4 ecb agrmodem b43 mac80211 cfg80211 led_class ohci_hcd snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc serio_raw pcspkr fbcon tileblit font bitblit softcursor shpchp pci_hotplug sg e1000e intel_agp agpgart hp_wmi wmi battery fan container video output thermal evdev button processor ac fuse aufs nls_iso8859_1 nls_cp437 usbhid usb_storage squashfs ssb uhci_hcd ehci_hcd usbcore

Pid: 10792, comm: modem-stats Tainted: P           2.6.33.2 #1 3618/HP 550
EIP: 0060:[<f882c9bb>] EFLAGS: 00210202 CPU: 0
EIP is at AzlDmaAllocation+0x81/0x2f9 [agrmodem]
EAX: 00000001 EBX: 00000000 ECX: f4fccd20 EDX: 00000000
ESI: f88d40c4 EDI: f88d4028 EBP: f03bbd34 ESP: f03bbd0c
 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modem-stats (pid: 10792, ti=f03ba000 task=f4ff0c20 task.ti=f03ba000)
Stack:
 00000000 f88de5f5 f88de5d8 f88de5e0 f03bbd28 f03bbda3 000000ff f88d40c4
 f88d40c4 f88d4028 f03bbd54 f882d2ad f88d40c4 00000000 f88d4028 f03bbdc4
 c128a594 f03bbda3 f03bbdc4 f88161e1 f88d40c4 f88c7048 00000008 00000001
Call Trace:
 [<f882d2ad>] ? CAzlIntelInit+0x381/0x3c4 [agrmodem]
 [<c128a594>] ? printk+0xe/0x11
 [<f88161e1>] ? LXHardwareStart+0x11de/0x13fb [agrmodem]
 [<c1055bcd>] ? __alloc_pages_nodemask+0xd6/0x470
 [<f8811998>] ? linux_modem_open+0x45/0x10e [agrmodem]
 [<c102c857>] ? mod_timer+0xea/0xf3
 [<f876bc11>] ? modemPortOpen+0x5/0xe [agrmodem]
 [<f88e7a6f>] ? serial8250_startup+0x74/0x250 [agrserial]
 [<c11a9348>] ? uart_startup+0x68/0xff
 [<c11a9acd>] ? uart_open+0x10b/0x302
 [<c119a53a>] ? tty_ldisc_setup+0x50/0x58
 [<c11969b9>] ? tty_init_dev+0x17c/0x1e9
 [<c1196d17>] ? tty_open+0x2f1/0x43e
 [<c1073ab0>] ? chrdev_open+0x11f/0x135
 [<c1073991>] ? chrdev_open+0x0/0x135
 [<c107041a>] ? __dentry_open+0x10c/0x1f0
 [<c107058e>] ? nameidata_to_filp+0x29/0x39
 [<c107a6d3>] ? do_filp_open+0x44b/0x82e
 [<c106028a>] ? __do_fault+0x301/0x331
 [<c10616be>] ? handle_mm_fault+0x238/0x4d6
 [<c108168d>] ? alloc_fd+0x52/0xb4
 [<c1070211>] ? do_sys_open+0x49/0xe7
 [<c10184ae>] ? do_page_fault+0x25f/0x275
 [<c10702f3>] ? sys_open+0x1e/0x23
 [<c1002694>] ? sysenter_do_call+0x12/0x26
Code: a5 00 00 89 44 24 08 8d 86 31 a5 00 00 89 44 24 04 c7 04 24 00 00 00 00 e8 63 57 01 00 85 c0 0f 84 71 02 00 00 8b 9e 14 a5 00 00 <c7> 03 01 00 00 00 c7 44 24 04 01 00 00 00 89 34 24 e8 f4 fe fe 
EIP: [<f882c9bb>] AzlDmaAllocation+0x81/0x2f9 [agrmodem] SS:ESP 0068:f03bbd0c
CR2: 0000000000000000
---[ end trace 692ed8da9155f2f2 ]---
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
rerwin
Posts: 2017
Joined: Wed 24 Aug 2005, 22:50
Location: Maine, USA

#20 Post by rerwin »

peebee,
Thanks for the links to Barry's blog items about the Agere driver. Here is the key to the problem:
The problem arose because I upgraded the ALSA drivers to 1.0.23, but the Agere drivers were compiled against the kernel's source ALSA code.

This time though, for the 2.6.31.14 kernel, I have not upgraded ALSA, avoiding this problem.
Lupu's ALSA is 1.0.24.2 whereas the kernel source must be something earlier, perhaps 1.0.16 or 1.0.20! It appears the ALSA version at run time must be the same as contained in the kernel source used for driver compilation. Maybe we can update the kernel-source's version to contain ALSA 1.0.24.2 without recompiling the kernel, but I doubt it. Since we do not want to change the ALSA version from 1.0.24.2, if we cannot change the kernel source successfully, then we are probably stuck.

After reflection: I think I have been using the wrong kernel source package. I will now try with playdayz's sfs file posted at the start of the lupu thread.
EDIT: Rebuilt the HDA-HSF package contents using playdayz's kernel source. However, the md5sums of the old and new agr* driver modules are the same. So that was not the solution.

EDIT: I found the HowTo for building the Agere HDA driver here;
http://linmodems.technion.ac.il/package ... 0-HDA.html
The part we are not complying with is:
For the 11c11040 case you must determine your ALSA drivers version. You MUST be using the version of ALSA that came with your current kernel. If you have since upgraded to a newer version of the ALSA modules, you will need to revert to the old version (or if this is not possible, upgrade your kernel.) To find your ALSA module version, issue in a terminal the command:
cat /proc/asound/version
In lupu5428 this returns:
Advanced Linux Sound Architecture Driver Version 1.0.21.

Our current ALSA version shown by "alsactl --version" is:
alsactl version 1.0.24.2

Therefore, to get the driver to work we must return lupu528 to running with ALSA 1.0.21 -- quite unlikely. We're dead.

But we could continue the experiment by trying the driver on puppy 4.3.1, whose kernel came with ALSA 1.0.20 and also runs with it. The test would entail using my "4.3.1.1." package along with the associated agrsm package. I think peebee may have tried that without success. But that setup holds the best promise for getting it to work outside of wary.
Richard

Post Reply