Puppy Linux Discussion Forum

[peebee]

Hi Richard

I've downloaded and installed onto a pristine pup431 the latest versions that I could find of:

[BarryK]

[BarryK]

If anyone is interested, I am positioning Wary as the replacement for Puppy 4.3.1, well for the entire 4.x series.

Wary 0.9 already has all of rerwin's PETs, so is ready to test. What I have not applied is his latest patch-3 for agere modems:

http://murga-linux.com/puppy/viewtopic.php?t=57290&start=45

Note that I was not able to compile the agrsm driver with the 2.6.35.7 kernel. Rerwin sent me links to a couple of other agrsm drivers, that cover some of the agere chips, and I was able to compile those but did not put them into Wary.

If you want to know what modem drivers I managed to compile with the 2.6.35.7 kernel (and are in Wary), see here:

http://bkhome.org/sources/kernel-2.6.35.7/

us#er#na#me: pu#pp#y pa#ss#wo#rd: li#nu#x

...click on the "kernel-compile-2.6.35.7.txt" file.

Wary 0.9 has also been built with the 2.6.30.5 kernel.

See Wary 0.9 announcement here:

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

[peebee]

[rerwin]

Agere modem testers with Wary09 (peebee),
I have posted a consolidated package in the wary09 bugs thread, to simplify upgrading the Agere support: http://www.murga-linux.com/puppy/viewtopic.php?p=457382#457382

Install that package, then the "agrsm" packages from the earlier posting in this thread. That sequence should avoid the warnings peebee described. Let me know if they still appear. Thanks.
Richard

[peebee]

[rerwin]

peebee,
Thanks. Since they are warnings, I think they can be ignored. I suspect they are related to the difference in versions of ALSA. Does the modem still work?

I am changing my scheme for implementing the Agere stuff because it does not work in wary. I think I can make minor changes to fix that. In the meantime, I think the wary package should still work as long as you install only one of the variants of agrsm.
Richard

[peebee]

Hi Richard

The warnings seem to stop the modules being loaded - so no - the modem does not work in wary 090 k2.6.30.5

I could try the --force parameter to modprobe? although this hasn't worked in the past.

Has alsa version changed between pup431 and wary090 even though they are both k2.6.30.5? Should I try reverting to the pup431 alsa? Is this even possible?

I'm still a bit bemused as to why wary060 k2.6.32.15 worked so well whereas subsequent wary's have problems....any ideas why?

Would be great to help you to get this to work.
Thanks
Peter

[rerwin]

[peebee]

[rerwin]

peebee,
Thanks for your report. The packages you installed are correct. But there should be no add-list entries for the agr modules. I assume you added them later, but how did three entries each get in there. The additional entries are ignored. And they should not get generated automatically, in case you did not put them there yourself.

Please try again and get me a pmodemdiag file. You can use your current setup, but remove the agr entries in the BootManager, re-run pupdial-CHOOSE>ERASE, and re-run depmod-FULL. Then reboot, click the connect icon. At that point, if no modem detected, do the following in a console:
- Run this command:

[peebee]

[rerwin]

peebee,
Thanks for the diag file. Yes, it provides a clue. The agr modules don't load because of a constraint in pup_event_backend_modprobe that prevents loading of a module if the device is already associated with another module, in this case snd_hda_intel. It makes an exception for usb-storage for the hybrid USB modems. I think an exception is needed for snd_hda_intel, as well.

With your current setup, please run (copy and paste) the following edit command in a console, to add the exception:

(Code removed to protect the updated version of the pup_event_backend_modprobe script. To get that fix, download and install the pup_event_backend_modprobe fix 5.7 from the first message in this thread.)

Then reboot and see what happens.
Richard

[peebee]

[rerwin]

Thank you, peebee, for verifying that final fix for the Ageres. The change is now in the new pup_event_backend_modprobe...5.7 package, and in the woof patch.
Richard