Puppy Linux Discussion Forum

vtpup · Posted: Sun 01 Feb 2009, 21:42 Post subject:

Fromthe other thread, Rerwin wrote:

vtpup · Posted: Sun 01 Feb 2009, 22:27 Post subject:

I feel like I'm spinning my wheels here, rerwin. I've put about 6 hours into testing this thing, and I'm trying to guess what you want me to do, and what changes have been made to 4.1 that I don't know about or don't understand, Obviously there's a procedure required to get this thing to work.

I'm happy to test this even though I don't use the modem anymore, but I ask that you provide me with exact test steps to follow on a Thinkpad 600E,

It seems that at least two dotpets have to be loaded and possibly the Bootmanager needs modules loaded and parameters passed, according to your prior post.

Rather than guess at the order of loading, whether I need to somehow manually clean out the last failed dotpet, or start with a fresh install, please let me know in a numbered step process exactly what test steps you want, and I'll do exactly that. We'll get a lot more accomplished that way in a lot less time.

Thanks!

tempestuous · Joined: 10 Jun 2005 Posts: 4944 Location: Australia

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

vtpup,
Sorry for the jerk-arounds. But all is not lost. It struck me this morning that the modem dotpet works only on the standard kernel, due to the big changes. So, don't try to use it in the retro -- but no harm done since it failed anyway. The fix is easier than that. The retro puppys still uses the /etc/rc.d/MODULESCONFIG file to cause loading of mwave (and the other modems in the dotpet). Puppy 4.1 and 4.1.1 contain the necessary lines in MODULESCONFIG. (I had them removed from 4.1.2 because the standard no longer needs them, but I did not consider the retro version.)

So you are OK where you are with the mwave dotpet, but need only to add the following line between lines 10 an 11 of /etc/rc./MODULESCONFIG:

vtpup · Posted: Mon 02 Feb 2009, 14:54 Post subject:

Line 11, if you are counting blank lines, and expand Geany out not to linewrap has a single apostrophe in it at present. Don't quite understand the function of that, but anyway, look:

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

vtpup,
Yes, you concluded correctly. I just assumed that everyone knows how to make geany display line numbers (View > Show Line Numbers). Or maybe you are not using geany. Anyway, you may want to wait a bit.

I have been fixing the modem-fix dotpet beyond just getting rid of the "+" in its name. I am making it support the retro puppys, too. However, I have discovered an old bug that may impact you. I think I have solved it for the standard kernel, but need to also fix the script for the retro pups. To keep things simple, I will tell you the file and line to edit, but will hold off until I verify it on a retro installation. The symptom was that the driver (actually just the init script, for mwave - a special case) still doesn't load. (I test with an Intel modem that needs the same override logic that mwave gets.)

Because I expect to be distracted until Tuesday afternoon, please be patient.
Thanks.
Richard

vtpup · Posted: Mon 02 Feb 2009, 19:36 Post subject:

No problem. I don't use the modem anyway -- I'm just doing this to help out.

I've also got this going on a frugal install playground, so it isn't impacting my main install.

Thanks for your work.

ottershaw · Joined: 07 Apr 2007 Posts: 4

There are at least 3 other people (besides myself) that are waiting for modem support for Thinkpad (600 & 600E) wave modems to be fixed in puppy.

I really hope you guys succeed. Please let me know when you need help testing your next attempt.

Gordon

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

vtpup and ottershaw,
Thanks for continuing your interest. I have good news! I was worried about nothing. The modem-controller dotpet works just fine with the 4.1.2 retro kernel. You can use the version already posted, even though it downloads as modem%2Bcardbus_fix-4.1.3.tar.gz. Just edit the name to replace "%2B" with "+", then click on it to install.

The dotpet installer expects the .pet to have the same name as the top directory within it. And that directory is modem+cardbus_fix-4.1.3. Give it a try at your leisure. I will be out of action, as mentioned above, but eager to hear how far you get without fiddling (except perhaps for your BIOS)..

BTW: The modem-controller fix will work only on 4.1.2 until I update it. This exercise yielded a bug fix for two scripts. I erroneously assumed the a retro puppy also used the puppy-lite version of uevent handling, but apparently not. Maybe the non-udev alternative is obsolete, so need not be fixed. Or I can fix it but not test it, although it is exactly the same code change for both.
Richard

vtpup · Posted: Mon 02 Feb 2009, 22:58 Post subject:

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

vtpup,
Back, at last. I just now downloaded, renamed, and installed successfully the modem fix from the bugs forum, into both standard and retro puppys. The checksum is:
# md5sum modem+cardbus_fix-4.1.3.pet
3840775cfce2b88228afa843ec8bb3ad modem+cardbus_fix-4.1.3.pet
#
It is the same for the file with the %2B in the name.

One thing I forgot to note for when you use the modem dotpet is that you cannot make that mwave update to the MODULESCONFIG file. The bug I found prevents that override from loading the module. I found that the module name gets set to the entire line, so is an invalid call to modprobe. If I edit the guilty command to use only the first field of that line, the loading succeeds.

With a fresh puppy you should install only the modem+cardbus and mwave dotpets. If you are tired of messing with this, please give me some time to get straight my ultimate modem+ fix, so that it is compatible with the non-udev configuration (that I misunderstood to be related to retro).
Richard

vtpup · Posted: Tue 03 Feb 2009, 21:02 Post subject:

Not a problem to test again, but I'm not sure what you just said.

Can we just clarify the steps you want performed? I'm guessing the following -- please correct where needed:

1.) Boot 4.1.2 retro and delete the old personal save file.
2.) Shut down and create a new personal save file so that we are starting fresh.
3.).Boot from 4.1.2 retro CD
4.) Download modem+cardbus_fix-4.1.3.pet
5..) Compare md5 checksum to 3840775cfce2b88228afa843ec8bb3ad
6.) Install modem+cardbus_fix-4.1.3.pet
7.) Download mwavem-1.0.2-patched.pet (no MD5 given)
8.) Install
9.) Reboot?
10.)Open PupDial and probe. Determine if modem is recognized.

Is that correct? No editing in Geany -- or console commands needed in the above steps?

rerwin · Joined: 24 Aug 2005 Posts: 1318 Location: Maine, USA

vtpup,
You are close. But it can be done more simplyg. So step 1 could be:
1.) Boot 4.1.2 retro with boot command "puppy pfix=ram". When booted up, delete the old personal save file.

Delete steps 2 and 3 and download the dotpets (step 4+). editing the %2B part of the name to "+".

Note that dotpets already check their md5sums and refuse to install if wrong. My guess is that that is what you are seeing.

Yes, step 9 is "reboot".

But step 10 should be:
10.) Click on the Connect icon and observe whether "no modem detected" or one is detected. (ttyS0?).

11) Click on button for "Internet by dialup analog modem". If pupdial shows a modem detected, set your dialup values and try to connect. Otherwise, try "Probe > probe". If you get a modem, try dialing it.

If things don't work out, please report whether file /etc/init.d/mwaved exists and, if so, whether /usr/bin/mwavem exists. If so, post the contents of /etc/wvdial.conf and /tmp/pupdial.log files (or attach them). Also check with lsmod to see if the mwave driver is loaded.

We can work from there.
Richard

vtpup · Posted: Wed 04 Feb 2009, 20:56 Post subject:

vtpup · Posted: Thu 05 Feb 2009, 11:42 Post subject:

Additional info:

Looks like the modem+cardbus_fix-4.1.3.pet also doesn't install properly.

The Puppy Package Manager does give the successful installation message and the 2 .pets are shown installed in the manager when I open it again.

However, in the manager, the modem+cardbus_fix-4.1.3.pet Description reads:
"undetected device rules".

mwaved is not found at all anywhere in the filesystem..
mwavem locations from Pfind in attached screenshot.