Puppy Linux Discussion Forum

[algyzas]

[Aitch]

that deviceID does correspond to a tascorp usb videocam

http://hardware4linux.info/component/32730/

see also similar problem

http://www.mail-archive.com/fedora-list@redhat.com/msg43436.html

no solution found

Aitch

[chasman666]

I can't get the wireless to work with a Belkin f5d7000 V2 PCI card on Puppy 4.2.1.

I've tried many different modules and read this whole thread about 8 times. The closest I can get is to modprobe b43 (this is what Ubuntu 8.04 auto chose and which works for it) which gives a wlan0 item in ifconfig but when I try to access it via network wizard it: 1) shows as PCMIA not PCI and 2) gives the error:
Failed to raise interface wlan0,
Failed command was: ifconfig wlan0 up
Error returned was:
ifconfig: SIOCSIFFLAGS: No such file or directory

As always any help gratefully received, it's probably something small and simple - just like me, but darned if I can find it!

Cheers,

Charlie

UPDATE
I just tried with 4.2.1Retro and it "worked out-of-the-box" as they say. It is using module bcm43xx.

So I guess that raises two things:
1. I hope that this information may be helpful to someone in the future
2. How can I make it work with the Standard version and future versions?

[tempestuous]

Hermes II/II.5 wifi chipsets
The Lucent/Agere Orinoco wifi chipset was one of the very first wifi chipsets available. It was initially supported by the opensource orinoco Linux driver.
Then the chipset developed further as the "Hermes-I", then under the Intersil company as "Prism2". Several opensource drivers had emerged by this stage, the most advanced being from the hostap project.

The Hermes versions were then updated to Hermes-II and Hermes-II.5, and these rare devices are not compatible with the hostap driver. They are supported only by the proprietary "wlags49" drivers, which are now very old and incompatible with modern kernels ...
but the source code has been updated by Henk de Groot here -
http://home.hetnet.nl/~pe1dnn/linux/
Apparently the driver now supports WPA encryption, via the "wext" interface with wpa_supplicant.

Now attached are the two versions of the updated wlags49 driver:
wlags49_h2_cs
for Hermes-II devices with ID 0156 0003, such as
SpeedTouch 110 PCMCIA card.

wlags49_h25_cs
for Hermes-II.5 devices with ID 0156 0004, such as
Linksys WCF54G CompactFlash card.

After installing this dotpet, reboot.
Puppy should automatically detect your device and load the wlags driver, but if not, you can load it from the Network Wizard.

UPDATE: forum members sweatshirt and space_jazz both report success with the wlags49_h2_cs driver -
http://www.murga-linux.com/puppy/viewtopic.php?p=334843#334843

[space_jazz]

I just downloaded and installed the patched hostap_cs driver and my speedtouch pcmcia wifi still won't work

There's now a network interface in the system (wifi0) but that'a all ... i cant see any network . Even in the control panel when i look to hardware info the network interface wifi0 have hardware adress 00:00:00:00:00.

Anybody can help me to get the thomson speedtouch 110 card to work ?

[tempestuous]

"wifi0" is usually a virtual or placeholder interface, not the true interface.
Run this command -

[tempestuous]

Mwave winmodem
The Mwave 3780i device is found in the IBM Thinkpad 600, 600E and 770/ED/X/Z models.

Puppy 4.1/4.2 already contain the mwave kernel module, but the necessary Mwave utilities are missing. These are now provided as the attached dotpet. They were taken from the zdrv file in Puppy 4.0.
After installing this dotpet, reboot.
At bootup, the Mwave daemon, /etc/init.d/mwaved, should run. Pupdial should now be able to see your modem.

[stevesr0]

I just tried to install this pet on my 4.2.1 frugal install.

The petget window checking appears and then disappears with no error messages.

I looked for an entry in the pet manager, but it isn't listed as installed.

The pet is sitting in my/initrd/pup_rw/mnt/sd3 directory.

What am I doing wrong?

stevesr0

[tempestuous]

I just checked the mwavem-1.0.2.pet now. It installs fine.
Why are you using petget? The simplest way to install dotpets has always been to simply click on the file in ROX.

[stevesr0]

Are we talking about the same pet? You call it mwavem 1.02 and I am referring to the pet named patched snd hd intel that you posted on 13 April.

I tried direct clicking and this did the same thing.

stevesr0

[cichlasoma]

Hi.
I haven't been able to connect to internet with wifi on my Asus EEEPC 1000H (wifi Ralink rt2860sta) in Puppy 4.21. In Internet Connection Wizard, it detects the wifi, finds the lots of available networks, accepts WEP for my one, performs Auto DHCP, reports it it be successful, but obtains an inet addr:169.254.xxx.yyy instead of 192.168.0.xxx and cannot connect to any internet site. When I set a static IP adress in the correct range 192.168.0.1 - 192.168.0.255, ifconfig reports the set address, but ping command to any internet address returns
ping: bad address 'xyz'.
In Puppy 4.25 and 4.76, the connection works all right. Haven't you any idea how I could connect via wifi in 4.21?


Here's a console listing after Auto DHCP command d in Network Wizard:

# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ra0 Link encap:Ethernet HWaddr 00:15:AF:D9:20:F9
inet addr:169.254.12.170 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2867 errors:0 dropped:0 overruns:0 frame:0
TX packets:191 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:299439 (292.4 KiB) TX bytes:4140 (4.0 KiB)
Interrupt:19

[Aitch]

cichlasoma

Sounds like a DNS problem as here

http://www.murga-linux.com/puppy/viewtopic.php?t=46583

Alternately try downloading a later network wizard

http://www.murga-linux.com/puppy/viewtopic.php?t=31522&start=585

Read P1 for instructions

Aitch

[cichlasoma]

Aitch:
Thank you a lot for your reply.
I forgot to write, I can connect via ethernet without any problem.
And I've tried the improved wizard you link with no effect before I asked, I didn't mention it as I thought it has nothing to do with my problem most probably.

Via wifi, I CANNOT ping to any server -
after auto DHCP:

# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ra0 Link encap:Ethernet HWaddr 00:15:AF:D9:20:F9
inet addr:169.254.105.63 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4780 errors:0 dropped:0 overruns:0 frame:0
TX packets:1405 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:631884 (617.0 KiB) TX bytes:6024 (5.8 KiB)
Interrupt:19

# ping 209.85.129.147
PING 209.85.129.147 (209.85.129.147): 56 data bytes
ping: sendto: Network is unreachable

after manually entering static IP address:

# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ra0 Link encap:Ethernet HWaddr 00:15:AF:D9:20:F9
inet addr:192.168.0.178 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13249 errors:0 dropped:0 overruns:0 frame:0
TX packets:1911 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1723861 (1.6 MiB) TX bytes:6024 (5.8 KiB)
Interrupt:19

# ping 209.85.129.147
PING 209.85.129.147 (209.85.129.147): 56 data bytes
^C
--- 209.85.129.147 ping statistics ---
29 packets transmitted, 0 packets received, 100% packet loss


after auto DHCP via ethernet:

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:24:8C:41:0B:D0
inet addr:192.168.0.200 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:2805 (2.7 KiB) TX bytes:0 (0.0 B)
Memory:fbfc0000-fc000000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:91 errors:0 dropped:0 overruns:0 frame:0
TX packets:91 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9148 (8.9 KiB) TX bytes:9148 (8.9 KiB)

# ping 209.85.129.147
PING 209.85.129.147 (209.85.129.147): 56 data bytes
64 bytes from 209.85.129.147: seq=0 ttl=245 time=21.621 ms
64 bytes from 209.85.129.147: seq=1 ttl=245 time=18.922 ms
64 bytes from 209.85.129.147: seq=2 ttl=245 time=20.365 ms
64 bytes from 209.85.129.147: seq=3 ttl=245 time=18.886 ms
64 bytes from 209.85.129.147: seq=4 ttl=245 time=20.112 ms
64 bytes from 209.85.129.147: seq=5 ttl=245 time=18.282 ms
64 bytes from 209.85.129.147: seq=6 ttl=245 time=16.620 ms
64 bytes from 209.85.129.147: seq=7 ttl=245 time=18.635 ms
64 bytes from 209.85.129.147: seq=8 ttl=245 time=16.753 ms
64 bytes from 209.85.129.147: seq=9 ttl=245 time=18.284 ms
64 bytes from 209.85.129.147: seq=10 ttl=245 time=19.641 ms
64 bytes from 209.85.129.147: seq=11 ttl=245 time=20.137 ms
^C
--- 209.85.129.147 ping statistics ---
12 packets transmitted, 12 packets received, 0% packet loss
round-trip min/avg/max = 16.620/19.021/21.621 ms

(Via eth0, I can browse internet without problems.)

(I would guess, the issues is with the wifi driver perhaps changed in the new kernel, as I have no problems in Puppy 4.25. But in fact, I don't understand the stuff at all...)

[Aitch]

cichlasoma

see this thread,

http://www.murga-linux.com/puppy/viewtopic.php?t=41204

and maybe post there, or at least link to here for tempestuous's help

It's outside my knowledge sphere.....driver's/kernels/updates....too many

Aitch

[mikeb]