I've just started using Puppy on an old PC - version 2.01 - and I would like to get connected to the internet.
The modem is an SM56 Software modem and I've found the following drivers:
http://www.motorola.com/softmodem/driver.htm
Is there a way to convert one of these? Any other ideas? Short of buying an external modem, I don't know what to do.
Thanks!
How to get Motorola SM56 software modem to work?
The link in your post has binaries compiled for specific kernel versions so they wont work. I managed to google a download for source that may work:
http://www.sm56.tk/
http://www.geocities.com/rajeshkizhuvee ... cc3.tar.gz
It has a makefile so if you had the Puppy developer file devx_201.sfs installed you could run the "make" command to compile it. If you're new to linux you will need some help compiling and loading the module or someone may be able to package it for you.
Bill
http://www.sm56.tk/
http://www.geocities.com/rajeshkizhuvee ... cc3.tar.gz
It has a makefile so if you had the Puppy developer file devx_201.sfs installed you could run the "make" command to compile it. If you're new to linux you will need some help compiling and loading the module or someone may be able to package it for you.
Bill
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
If you have never compiled before, that's a tough one to start with - old source code hacked to compile with newer kernels.
I just compiled it in both Puppy1x and Puppy2, but the Puppy2 version (2.6 kernel) looks like it yielded an invalid module format. So I attach a dotpup for Puppy 1.0.9 ... this has a much better chance of working.
After installing the dotpup in Puppy 1.0.9, run these commands in rxvt -
/root/my-applications/sm56makedevices.sh
insmod /root/my-applications/sm56.o country=1
Now your dialer can connect to either /dev/modem or /dev/sm56
For "country=..."
1 = USA
2 = Canada
27 = South Africa
30 = Greece
31 = Netherlands
46 = Sweden
47 = Norway
49 = Germany
52 = Mexico
54 = Argentina
84 = Vietnam
86 = China
90 = Turkey
351 = Portugal
352 = Luxembourg
32 = Belgium
33 = France
34 = Spain
39 = Italy
55 = Brazil
60 = Malaysia
353 = Ireland
354 = Iceland
358 = Finland
852 = Hong Kong
57 = Columbia
58 = Venezuela
41 = Switzerland
42 = Czech Republic
43 = Austria
44 = United Kingdom
45 = Denmark
61 = Australia
64 = New Zealand
65 = Singapore
66 = Thailand
81 = Japan
82 = Korea
886 = Taiwan
962 = Jordan
972 = Israel
I just compiled it in both Puppy1x and Puppy2, but the Puppy2 version (2.6 kernel) looks like it yielded an invalid module format. So I attach a dotpup for Puppy 1.0.9 ... this has a much better chance of working.
After installing the dotpup in Puppy 1.0.9, run these commands in rxvt -
/root/my-applications/sm56makedevices.sh
insmod /root/my-applications/sm56.o country=1
Now your dialer can connect to either /dev/modem or /dev/sm56
For "country=..."
1 = USA
2 = Canada
27 = South Africa
30 = Greece
31 = Netherlands
46 = Sweden
47 = Norway
49 = Germany
52 = Mexico
54 = Argentina
84 = Vietnam
86 = China
90 = Turkey
351 = Portugal
352 = Luxembourg
32 = Belgium
33 = France
34 = Spain
39 = Italy
55 = Brazil
60 = Malaysia
353 = Ireland
354 = Iceland
358 = Finland
852 = Hong Kong
57 = Columbia
58 = Venezuela
41 = Switzerland
42 = Czech Republic
43 = Austria
44 = United Kingdom
45 = Denmark
61 = Australia
64 = New Zealand
65 = Singapore
66 = Thailand
81 = Japan
82 = Korea
886 = Taiwan
962 = Jordan
972 = Israel
-
tempestuous
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Well, it was a long-shot anyway ... winmodem in Linux, old driver source ... happiness was never assured.
You could check a few things: is there an irq conflict with the modem? Run "cat /proc/interrupts" for clues.
Is this a laptop with PCMCIA? Linux PCMCIA configuration can inadvertently assign irq's to PCMCIA devices which conflict with other devices. This can be fixed by modifying /etc/pcmcia/config.opts
Google for answers. Would other winmodem drivers like lucent, smartlink, or HSF/HCF work?
But I think an external hardware modem is the sensible solution.
You could check a few things: is there an irq conflict with the modem? Run "cat /proc/interrupts" for clues.
Is this a laptop with PCMCIA? Linux PCMCIA configuration can inadvertently assign irq's to PCMCIA devices which conflict with other devices. This can be fixed by modifying /etc/pcmcia/config.opts
Google for answers. Would other winmodem drivers like lucent, smartlink, or HSF/HCF work?
But I think an external hardware modem is the sensible solution.
clare,
i don't think the modempup, that tempestuous compiled, will be compatible with the version of puppy that you're running, as it's for pup1.09, which has 2.4.29 kernel, whereas you're using pup2.01 which has 2.6.17 kernel. maybe someone might have success compiling it for 2.6...i don't have that system at the moment.
i don't think the modempup, that tempestuous compiled, will be compatible with the version of puppy that you're running, as it's for pup1.09, which has 2.4.29 kernel, whereas you're using pup2.01 which has 2.6.17 kernel. maybe someone might have success compiling it for 2.6...i don't have that system at the moment.
