Thinkpad 600E mwave modem problem (solved)

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

Thinkpad 600E mwave modem problem (solved)

#1 Post by peebee »

Dear All

Help please!! I've followed all the good advice I can find on these forums to try and get the modem in my Thinkpad 600E (type 2645-910) working.

The laptop has Windows 98 installed and I'm live CD working with PuppyLinux 4.0 using the quickboot option
The modem works fine under W98 although I have noticed that the irq configuration is different (COM2 is irq 5).

My current state is:

I've added the mwave module to the system using System - BootManager

Menu - System - Hardinfo shows that the mwave module has installed and

dmesg shows that I've got a 16550A uart at irq 3

setserial confirms that /dev/ttyS1 is 16550A uart at irq3

/proc/tty/driver/serial shows that chars are being TX on the uart

So.....everything seems to check out OK BUT no chars are being RX from the uart and consequently PupDial (/etc/wvdial.conf manually edited modem = /dev/ttyS1; baud = 115200) says:

For Test - Modem - "There is no modem to test"

For Test - Probe - "Sorry, no modem was detected!"

for Connect to Internet - "Modem not responding"

I've also tried modem-stats but nothing seems to come back from the modem

I'd be very grateful if anyone can suggest what to try next as I'm pulling my hair out..............

Thanks
Peter

p.s. I'm frustrated as the rest of PuppyLinux looks great and I'd love to ditch W98 but I do need the modem to work first!

p.p.s I'm using my PC to post to the forum so including dumps from the laptop is not possible
Last edited by peebee on Mon 29 Sep 2008, 22:47, edited 1 time in total.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

Re: Thinkpad 600E mwave modem problem

#2 Post by tempestuous »

peebee wrote:... working with PuppyLinux 4.0 using the quickboot option...
Do you mean the quickboot setting in bios? This should be set to "off" and your hardware will then work better under Linux. This is well documented on the web, especially at thinkwiki.org

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

Re: Thinkpad 600E mwave modem problem

#3 Post by peebee »

tempestuous wrote:
peebee wrote:... working with PuppyLinux 4.0 using the quickboot option...
Do you mean the quickboot setting in bios? This should be set to "off" and your hardware will then work better under Linux. This is well documented on the web, especially at thinkwiki.org
Hi tempestuous

Thanks for your interest - do you think this would cause the problem I've described? I've tried most combinations of quickboot settings - both in the bios setup and also in the Puppy boot sequence (as per system - bootmanager). What should the settings be do you think?

Thanks
Peter

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

Re: Thinkpad 600E mwave modem problem

#4 Post by tempestuous »

peebee wrote:What should the settings be do you think?
tempestuous wrote:Do you mean the quickboot setting in bios? This should be set to "off"

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

Re: Thinkpad 600E mwave modem problem

#5 Post by peebee »

tempestuous wrote:Do you mean the quickboot setting in bios? This should be set to "off"
[/quote]

I've made sure the bios quickboot setting is disabled ("off") and I've also put the bootup back to full probe of hardware-----------

but its made no difference - the modem is still not responding............

The bootup sequence does say something like:

"Analogue modem detected - ttyS1" so a modem is maybe being seen then but is then switched off later somehow???

Cheers
Peter

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#6 Post by tempestuous »

If automatic configuration via Puppy's Wizard fails, you can revert to manual configuration using instructions here
http://dotpups.de/dotpups/Internet/Winm ... README.txt

You will see that attention needs to be paid to the allocation of hardware resources when loading the mwave kernel module.

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

#7 Post by peebee »

Still got problems :cry:

I've used PS2 under W98 to set the interrupts to the standard 10 for the DSP and 3 fro the uart.

As suggested, I've run each part of the setup manually.

the modprobe command seems to work (or at least doesn't give errors) and afterwards /proc/modules has the mwave in it

BUT then mwavem does give an unspecific error and dmesg shows a couple of "worries" about both irq lines being zero and then various other errors.

/etc/mwavem.conf has various traces that can be set - is it worth setting any of these???

Grateful thanks for any further help anyone can offer..........

Cheers
Peter

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#8 Post by tempestuous »

peebee wrote:I've used PS2 under W98 to set the interrupts ...
I suggest you adjust all hardware settings manually in bios. Use the defaults:
uart_irq 3
uart_io 0x2f8
irq 10
io 0x130

And don't forget the setserial command at the end. The example I gave in the README referred to /dev/ttyS0, but the correct serial device may be /dev/ttyS1

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

#9 Post by peebee »

tempestuous wrote:
peebee wrote:I've used PS2 under W98 to set the interrupts ...
I suggest you adjust all hardware settings manually in bios. Use the defaults:
uart_irq 3
uart_io 0x2f8
irq 10
io 0x130
Hi tempestuous

I thought that using P2 was the way to adjust all hardware settings manually in bios?? Is there another way?

I did use the defaults...............

Confused of Malvern, UK

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#10 Post by tempestuous »

peebee wrote:I thought that using P2 was the way to adjust all hardware settings manually in bios?? Is there another way?
The normal way to get into bios is to press (and hold) one of the function keys during bootup. With the TP600E apparently the correct key is F1

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

#11 Post by peebee »

tempestuous wrote:
peebee wrote:I thought that using P2 was the way to adjust all hardware settings manually in bios?? Is there another way?
The normal way to get into bios is to press (and hold) one of the function keys during bootup. With the TP600E apparently the correct key is F1
The F1 key just takes you into Easy-Setup..........
I believe that the P2.EXE program is the way to set the IRQs and this I have done.

How do I find out the details of the mwavem error so that I can fix the cause??

Many thanks
Peter

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

Some diagnostic information

#12 Post by peebee »

I have now discovered that I can transfer info off the Thinkpad on a memory stick in the usb port (another reason for wanting to get puppy to work.......)

Please let me know if there is anything else I can post to solve this perplexing problem - thanks

After manually running modprobe the interrupt files show:

----------------------------------------------------------------------
/proc/tty/driver/serial
serinfo:1.0 driver revision:
0: uart:16550A port:000003F8 irq:4 tx:3 rx:0
1: uart:16550A port:000002F8 irq:3 tx:0 rx:0
2: uart:unknown port:000003E8 irq:4
3: uart:unknown port:000002E8 irq:3

/proc/interrupts
CPU0
0: 272270 XT-PIC-XT timer
1: 360 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
6: 3 XT-PIC-XT floppy
7: 4 XT-PIC-XT parport0
8: 1 XT-PIC-XT rtc
10: 4 XT-PIC-XT mwave_3780i
11: 1410 XT-PIC-XT uhci_hcd:usb1, yenta, yenta
12: 41400 XT-PIC-XT i8042
14: 12878 XT-PIC-XT ide0
15: 73 XT-PIC-XT ide1
NMI: 0
ERR: 0

--------------------------------------------------------------------

So I do seem to have irq3 for the uart and irq10 for the dsp after running modprobe.............

Typical error messages given by dmesg but I'm unsure if these are before or after running modprobe are:

--------------------------------------------------------------------
Sep 24 08:32:00 (none) user.err kernel: mwave: smapi::smapi_query_DSP_cfg: Worry: DSP IRQ line is 0
Sep 24 08:32:00 (none) user.err kernel: mwave: smapi::smapi_query_DSP_cfg: Worry: UART IRQ line is 0
Sep 24 08:32:00 (none) user.err kernel: mwave: tp3780i::tp3780I_CalcResources: Error: Illegal resource setting. Aborting.
Sep 24 08:32:00 (none) user.err kernel: mwave: mwavedd:mwave_init: Error: Failed to calculate resources
Sep 24 08:32:00 (none) user.err kernel: mwave: mwavedd::mwave_init: Error: Failed to initialize
---------------------------------------------------------------------

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#13 Post by tempestuous »

There are some tips about how to enable the modem using the PS2 bios utility here
http://www.seedsforchange.org.uk/vcs/600e#modem

but I suspect you may need a special boot parameter such as "pci=biosirq"
or one of the other boot parameters mentioned here -
http://www.murga-linux.com/puppy/viewto ... 577#216577

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

#14 Post by peebee »

tempestuous wrote:There are some tips about how to enable the modem using the PS2 bios utility here
http://www.seedsforchange.org.uk/vcs/600e#modem

but I suspect you may need a special boot parameter such as "pci=biosirq"
or one of the other boot parameters mentioned here -
http://www.murga-linux.com/puppy/viewto ... 577#216577
Hi there

I've tried all of:
pci=biosirq
acpi=noirq
acpi=strict
pci=nosort
irqpoll
routeirq

and none cure the problem............mwavem still says Error and PupDial says no modem

If I attempt to connect to the modem with:
modemstats -c "AT" /dev/ttyS1

and then look at /proc/tty/driver/serial while modemstats still running this shows:

serinfo:1.0 driver revision:
0: uart:16550A port:000003F8 irq:4 tx:3 rx:0
1: uart:16550A port:000002F8 irq:3 tx:8 rx:0 RTS|DTR
2: uart:unknown port:000003E8 irq:4
3: uart:unknown port:000002E8 irq:3

which seems to indicate that something is happening.............tx but no rx

Does mwavem handle rx??

Any help on deciphering what the Error is from mwavem greatfully received.

Thanks
Peter

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

#15 Post by peebee »

I have found another post in the Fedora forum which appears to be exactly the same symptoms that I am experiencing - unfortunately it ends before a solution is described :cry:

http://www.fedoraforum.org/forum/archiv ... 24771.html

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

Progress of a sort............

#16 Post by peebee »

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/Winm ... -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 :roll: like to get the modem working on 4.0!!!

Cheers
Peter in Malvern, UK

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

Problem solved

#17 Post by peebee »

:D By installing the dotpup from http://dotpups.de/dotpups/Internet/Winm ... -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??

User avatar
vtpup
Posts: 1420
Joined: Thu 16 Oct 2008, 01:42
Location: Republic of Vermont
Contact:

#18 Post by vtpup »

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/viewto ... 368#240368

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

#19 Post by peebee »

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

User avatar
vtpup
Posts: 1420
Joined: Thu 16 Oct 2008, 01:42
Location: Republic of Vermont
Contact:

#20 Post by vtpup »

Thanks Peter,

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

Code: Select all

# mwaved start 
Starting Mwave modem:
    Starting Mwave Manager:done

    Configuring serial port:failed
Seems odd that the setserial line worked while mwaved start reported a failure to configure the serial port.

Actually, why is it trying to configure the port?

This was set by ps2.exe, I thought?

Other points of interest:

1.) doing a pfind for filenames reveals that there are 4 instances of mwaved in the filesystem -- of two different sizes:

mwaved of 8686 bytes located in:
/etc/init.d and
/initrd/pup_rw/etc/init.d/mwaved

-and-

mwaved of 6784 bytes in:
/initrd/pup_rw/root/my-applications/bin/mwaved and
/root/my-applications/bin/mwaved

so I wonder which is being invoked in the console -- and failing.


2.) re:
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 don't have a /root/Startup and there is nothing in /etc/rc.d/rc.local -- possibly a difference in version 3.01 (?)

3.) Opening mwaved in text mode, I noticed the following note:

Code: Select all

# Do not set DSPIO, DSPIRQ, UARTIRQ, or UARTIO if you have configured your Mwave
# modem with PS2.EXE, the ThinkPad Setup utility (Windows NT version), or tpctl
# (hopefully someday).
As a guess, does this mean that the configure serial section of mwaved should be commented out if we have used ps2.exe to set IRQs?

That would seem to be consistent with the configuration error message I got above -- is that a possibility?

Thanks again for your help Peter!

Steve

Post Reply