Puppy Linux Discussion Forum

peebee · Joined: 21 Sep 2008 Posts: 931 Location: Malvern, Worcs, UK

Progress report:

1 step back - 1 step forward?

I've installed Puppy 215CE (kernel 2.6.18.1) and then loaded the dotPUP Mwave drivers etc to be found at: http://dotpups.de/dotpups/Internet/Winmodem-drivers-for-Puppy-2.00-and-2.01/ and guess what..............

with a bit of fiddling with the startup scripts, I've madecontact with the modem.

So what's changed in kernel 2.6.21.7 with its built in Mwave support and PuppyLinux 4.0 to stop the Mwave Manager starting up???

Can someone tell me:

- how to disable the built-in Mwave support in 4.0??
- whether the dotPUP drivers should work on 4.0??
- are the dotPUP drivers different to the built in drivers in 4.0??

Many thanks - I'd REALLY Rolling Eyes

like to get the modem working on 4.0!!!

Cheers
Peter in Malvern, UK

peebee · Joined: 21 Sep 2008 Posts: 931 Location: Malvern, Worcs, UK

By installing the dotpup from http://dotpups.de/dotpups/Internet/Winmodem-drivers-for-Puppy-2.00-and-2.01/ onto PuppyLinux 4.0 the modem has sprung into life. Whoopee.
Cheers
Peter
p.s. should I report the distro failure as a bug??

vtpup · Posted: Wed 15 Oct 2008, 22:20 Post_subject:

Seems like you should. Why would you have to install something that is already installed to get the modem to work?

Also, was it the standard 4.01 that worked for you, or the retro version?

I'm trying to get my 3.01 system working. I have a dialup connection (naturally) and downloading 4.01 is not an easy task at this point. I'd really like to get it going with 3.01, since everything else works fine for me.

I also have Ubuntu 7.10, and mwave works fine there, though I did have to change the TP600E interrupts to irq 3 and 10, using ps2.exe.

Any further suggestions for getting it to work on 3.01?

Thanks!

ps. have you seen this:

http://www.murga-linux.com/puppy/viewtopic.php?p=240368#240368

peebee · Joined: 21 Sep 2008 Posts: 931 Location: Malvern, Worcs, UK

Yes - retro - later kernel does not work on Thinkpad 600E - something to do with disk drivers??

USB port works fine so I've downloaded stuff on my PC + broadband and then transferred to the Thinkpad on a USB memory stick........

Just tried 4.1 - Out of the Box version still does not work, but previous reported .PUP does but I've had to move the mwave startup script to after X-windows starts as something is calling another version of mwavem and mwaved. (moved from /etc/rc.d/rc.local to /root/Startup). The call of mwavem must be: /usr/local/sbin/mwavem

I'd suggest trying the PUP on 3.01 and making sure the mwave modprobe and startup occur after the boot sequence - my code is:

## load the Mwave kernel driver modules
modprobe mwave mwave_uart_irq=3 mwave_uart_io=0x2f8 mwave_3780i_irq=10 mwave_3780i_io=0x130 mwave_debug=0x00
## now start the mwave manager daemon
/usr/local/sbin/mwavem
## now configure the serial port
setserial /dev/ttyS1 auto_irq autoconfig
## run mwaved
mwaved start

Good luck!
Cheers
Peter

vtpup · Posted: Thu 16 Oct 2008, 17:39 Post_subject:

Thanks Peter,

I typed your code into the console and each command completed (including setserial) without an error except the last:

peebee · Joined: 21 Sep 2008 Posts: 931 Location: Malvern, Worcs, UK

Did the modem work after doing the manual setup????

You can test it with:

modem-stats -c "ATI3" /dev/ttyS1

which should return:

ThinkPad Modem v4.0
OK

Cheers
Peter

vtpup · Posted: Thu 16 Oct 2008, 19:33 Post_subject:

Sorry, no Peter, the modem didn't work after manual setup.

Also the command, modem-stats -c "ATI3" /dev/ttyS1 simply returned nothing and the console just continued to wait.

also, I have tried using both versions of mwaved on my computer by giving the full path, and following your code anew each time.

There is a difference in the final error message. The longer version of mwaved (the one shipped with Puppy):

vtpup · Posted: Thu 16 Oct 2008, 19:37 Post_subject:

I'm guessing that in the longer version, there may be a bad location reference to mwavem. I'm going to look for that location reference and make sure it points properly.

Steve

vtpup · Posted: Thu 16 Oct 2008, 21:08 Post_subject:

Well, now I really don't know what to say....

I rebooted and all of a sudden the modem was detected automatically. I don't know why. The only change I believe I made at one point today was to make wavem executable -- but now I can't remember which copy of mwavem -- there are several on the system now from all the trial and error and the dotpup download. The important one in the original Puppy distribution is the one at /usr/bin/mwavem.

I apologize to anyone looking for answers here in the future. I wish I could pin down the solution. One thing that was definitely wrong at the start for me was the irq addressing of the modem, as I mentioned much earlier.

I needed to use the MSDOS ps2.exe program (from a floppy disk) to reset the modems irqs to 3 and 10 and also to issue the ps2,exe command "enable" after setting them.

Sorry I can't give a clearer account of what caused it to start working.

vtpup · Posted: Fri 17 Oct 2008, 23:26 Post_subject:

Well, having Puppy see the modem, is not the same thing as getting it to communicate with it.

I now have the modem detected on startup and Pupdial shows ttyS1 when I hit "Probe." This is different than earlier behavior when nothing was detected..

However, when I hit Test TTYS1 in PupDial I get the error message, "Sorry the modem was not detected".

And when I run

vtpup · Posted: Sat 18 Oct 2008, 01:05 Post_subject:

Progress!
It was irq 3. This worked:

peebee · Joined: 21 Sep 2008 Posts: 931 Location: Malvern, Worcs, UK

You MAY have IRQ conflicts - something else may be using IRQ3 on Windows?

You need to disable with PS2 any features you don't use such as the IR port and the docking system.

I also made sure that PCMCIA didn't grab any of the IRQs by putting:

# Resources we should not use, even if they appear to be available

# First built-in serial port
exclude irq 4
# Second built-in serial port
exclude irq 3
# Sound
exclude irq 5
# First built-in parallel port
exclude irq 7
# Mwave irq
exclude irq 10

into /etc/pcmcia/config.opts

Don't know if any of this is essential but auto_irq did work for me.............

Cheers
Peter

vtpup · Posted: Sat 18 Oct 2008, 10:29 Post_subject:

It works! It works! I'm writing this from a modem initiated connection.

Thanks Peter for your additional very helpful suggestions. I didn't need to do anything further, however after last night.

The setserial command to associate irq3 was sticky, so I didn't have to set it again this morning -- just started the computer up and connected to a phone line and issued mwaved start from the console.

I still get an error message after this command stating that mwave couldn't set the serial port (but since it was already correctly set, it doesn't matter) -- and despite the error message, mwave does start up. After that it's simply a matter of using PupDial.

To reply re. the latest suggestions you provided:

BarryK · Posted: Sat 18 Oct 2008, 20:50 Post_subject:

vtpup · Posted: Sat 18 Oct 2008, 20:53 Post_subject:

Okay I believe I've solved it for Puppy's automatic bootup installation.

The problem seems to be in the mwavem executable file packaged with Puppy 3.01.

It looks to be the same executable file as mwavem packaged into the DotPup: mwave-2.0-ACP-modem.pup except that it is a "stripped" version.

If you do a properties on each of the two versions, the 3.01 Puppy version is 499088 Bytes long, and the DotPup version is 567305 bytes long. And from the descriptions, both are the same program version except for the stripping.

I found that if I renamed the Puppy 3.01 (stripped) version /usr/bin/mwavem to something else, so it wouldn't load, and then copied the DotPup (not stripped) version to /usr/bin/mwavem, then Puppy starts up automagically with mwavemodem module loaded and running and the tp600e modem fully functional.

I think that was what was intended.

Hope this helps -- possibly with versions of Puppy other than 3.01, as well.

Best Regards
Steve