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/viewtopic.php?p=322455#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??)

peebee,
Thanks for the links to Barry's blog items about the Agere driver. Here is the key to the problem:

Quote:

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.

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

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

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

The version of the "alsactl" utility does not necessarily represent the version of ALSA libraries.
The correct way of determining ALSA version is to run this command -

Code:

cat /proc/asound/version

rerwin wrote:

Therefore, to get the driver to work we must return lupu528 to running with ALSA 1.0.21

ALSA was upgraded at some point in the 5.2.x series. I suggest you test your modem driver in Puppy 5.1.1, which should still have ALSA 1.0.21.
Then if it works, it's quite possible to downgrade ALSA to the standard version in the 2.6.33.2 kernel source (ALSA 1.0.21). In fact, I still use Lucid 5.1 as my kernel development box, so I have the older ALSA libraries. Let me know if you want me to package these.

The version of the "alsactl" utility does not necessarily represent the version of ALSA libraries.
The correct way of determining ALSA version is to run this command -

Code:

cat /proc/asound/version

. . .
ALSA was upgraded at some point in the 5.2.x series. I suggest you test your modem driver in Puppy 5.1.1, which should still have ALSA 1.0.21.
Then if it works, it's quite possible to downgrade ALSA to the standard version in the 2.6.33.2 kernel source (ALSA 1.0.21). In fact, I still use Lucid 5.1 as my kernel development box, so I have the older ALSA libraries. Let me know if you want me to package these.

It appears I jumped to two wrong conclusions and got the facts all scrambled. Thank you for straightening me out. I am back to being confused about how to identify that ALSA has been "upgraded" -- exactly what does that mean? Lupu 5.2.8 shows

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

How do we identify which ALSA version "came with the kernel"? And in what way would we "revert to the old version?" In the kernel source or in the operational ALSA utilities version, or what else?

And thank you very much for your offer of help in making some progress. I will probably need it to understand more about this.

For testing, it is actually peebee whom I will depend on for that with 5.1.1. I think I will put together a package for that test, that adds the updated agrsm firmware tarball, if it is not up to date in 5.1.1.
Richard

tempestuous, peebee,
I have what appears to be good news! I have remastered 5.1.1 with the latest modem-modprobe package (to make it look more like 5.2.8 internally) and the three main "dialup modem" packages (other than the Intel 537s) and seem to run with a healthy HDA modem. The catch is that I do not have such a modem; I only forced loading of the agrmodem module for the test. But the indication is good.

When I run the test on 5.2.8, I see certain error indications. On Wary I see different messages that look like success. (I have an HSF modem installed, which might be fooling puppy into thinking the HDA modem is there.) When I run the test on my new upgraded 5.1.1 installation, I see the same messages as in Wary. This tells me that the modem might actually work in this setup.

However, the two ALSA versions are not the same -- /proc/asound: 1.0.21 and alsactl: 1.0.22. So we need peebee to try this with his real HDA modem, to be sure. If that works, it confirms that the alsactl version is unimportant for our purposes.

What I did:
downloaded 5.1.1 iso
downloaded the 2 pets you specified (only the 11c11040 modem pet)
installed 5.1.1 manual frugal by opening the iso and copying the 3 files to a test directory
booted 5.1.1
closed down and created a savefile
rebooted
installed 2 pets
rebooted
checked alsa versions - result = 1.0.21 and 1.0.22 so 5.1.1 alsa version is higher than kernel??
issued the modem-stats -c "ATI3" /dev/ttyAGS3 command in a terminal
said "Killed"

peebee,
Apparently, my test is not valid as an indication that the driver is working correctly. Instead of entering the modemstats command, could you simply boot up and then find the messages in /var/log/messages that pertain to the driver? I search on "agr" and find only a couple of lines in both wary and lupu 5.1.1, but only that the module was "registered" in lupu 5.2.8. In lupu 5.2.8, the ttyAGR3 node does not get generated, whereas both wary and lupu 5.1.1 generate it automatically.

Remember, my test uses forced loading of agrmodem, set in the boot manager as an "added module." The bottom line is that there is a difference in behavior between 5.2.8 and 5.1.1, with 5.1.1 matching the behavior of wary 5.1.3. That is all I can go on.

As a last gasp, could you boot up with lupu 5.1.1 + the 2 added packages and save off the /var/log/messages file for attachment to a posting. Also do the same on whatever version of Wary you have. Then we can compare the agr-related messages for clues.

Maybe we still have an ALSA mismatch of some sort, but the details of that are not obvious, unless the difference in the reported versions is significant. What bothers me is that lupu 5.2.8 reports that is has ALSA 1.0.21 even though both playdayz and tempestuous state that ALSA was "upgraded", is some sense. Maybe the upgrade omitted setting the correct version in /proc/asound/version. Here is where we need tempestuous' assistance.
Richard

As a last gasp, could you boot up with lupu 5.1.1 + the 2 added packages and save off the /var/log/messages file for attachment to a posting. Also do the same on whatever version of Wary you have. Then we can compare the agr-related messages for clues.
Richard

Hi Richard

Attached please find messages files with added .gz to make them postable for:

The two lupus are essentially the same, derailed by a null pointer reference. So lupu 5.1.1 is not the solution. What next, tempestuous?

BTW, I compared the md5sums of the 11c11040 module between compilations with both the generic puppy version of the 2.6.33.2 source package and the one playdayz used for lucid pup -- they were the same. So, I conclude that the choice of source code package was not a factor. Is there a way to create a dot-pet package that restores the 1.0.21 versions of the ALSA components that got "upgraded"? Or is it messier than that?
Richard

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum