(old)Puppy Linux Discussion Forum

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

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/viewto ... &start=585

Read P1 for instructions

Aitch

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...)

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

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

you are entering the puplet zone.......

mike

Thank you for your assessment...
(I edited my last post deleting a nonsensical line in the last console quotation which I copied into my post by mistake, I apologize...)

mikeb wrote:you are entering the puplet zone.......

yes, and this is how I feel sometimes [attached].....you can almost hear the appropriate background music

Aitch

(I can connect with no problem in 4.3-k2.6.30.5, but cannot in 4.3-k2.6.25.16, which seems to approve my guess I deal with a driver issue in 4.21.)

cichlasoma

sounds right, so unless you really need 4.2.1, which I seem to get lots of network support calls on, ....stay with the working 4.3

Aitch

Hmm.. Do you think, it's definitely beyond a newbie's capabilities to force Puppy to use a Windows driver with a wrapper? (I don't know whether to try playing with it for Asus EEEPC's wifi and ACER Travelmate's touchpad.)

sounds right, so unless you really need 4.2.1, which I seem to get lots of network support calls on, ....stay with the working 4.3

The general feedback I noticed was a problem with dchp and puppy 4.20/21....ie i can connect but not browse symptoms.

mike

I'm sorry for the previous post. I noticed first thereafter the wrapper wizard integrated into the Puppy network connection wizard. With the help of it, It's pretty easy to set up wireless connection using wrapped windows driver. And I can browse web in Puppy using wireless connection on my EEEPC!!! :-):-)

Here are additional links (not neaded when using the wizard actually).
http://wiki.eeeuser.com/howto:installpuppylinux
http://wiki.eeeuser.com/howto:configurendiswrapper

ok im a complete newb and i have a eee 900hd and it cant pick up any wireless network at all which drivers do i need for this munchkin of a netbook any help will be appreciated

Apparently your 900HD has the Realtek RTL8187SE wifi chipset, so the necessary driver is attached to the 6th post in this thread ...
but this is the forum thread for the older kernel.

You should probably be using Puppy 4.3 with the latest kernel (2.6.30.5), for which the necessary rtl8187se driver is here -
http://www.murga-linux.com/puppy/viewto ... 449#346449

tempestuous wrote:Here is the "sn9c20x" webcam driver for various models of microdia webcams, including models branded "Lifecam".
The source code is from http://groups.google.com/group/microdia ... iver-draft
After installing this dotpet, reboot. Puppy may automatically load this module, but if not load it manually as such -

Code: Select all

modprobe sn9c20x

Apparently this driver provides the video image in a pixelformat that most video/webcam applications cannot handle, so the libv4l library is required, also attached. The README will install to /root/my-applications/libv4l-README.txt
Instructions for use with the MPlayer, using MPlayer's v4l2 interface:
Install libv4l-0.5.8.pet
Before launching MPlayer, run this command -

Code: Select all

export LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so

Now launch MPlayer like this -

Code: Select all

mplayer tv:// -tv driver=v4l2:width=352:height=288:device=/dev/video0

UPDATE:
It's important that MPlayer (or XawTV, or Skype, or whatever application you choose) is launched from the same xterminal that ran the "export LD_PRELOAD ..." command.

Hi tempestuous,

If you have the source handy, will you please compile sn9c20x and lib4vl for Puppy 4.3.1?

Thanks!

kuapao

OK, done -
http://www.murga-linux.com/puppy/viewto ... 459#346459

... I presume the sn9c20x webcam driver/libv4l library works?!
Generally I only hear reports when something's not working!

tempestuous wrote:OK, done -
http://www.murga-linux.com/puppy/viewto ... 459#346459

... I presume the sn9c20x webcam driver/libv4l library works?!
Generally I only hear reports when something's not working!

tempestuous,

It worked for me in Puppy 4.2.1 (and using either xorg or xvesa) with
export LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so before running skype.

Will test the driver you just sent for Puppy 4.3.1 (kernel version 2.6.30.5). I have no doubt it will work though.

I will be posting a question, though, how to get the built-in mic working in the very same webcam (Lifecam NX-6000). Am trying it in Puppy 4.3.1, though I haven't checked with older Puppy/kernel versions yet.

Thanks!
kuapao

i want bsnl 3G usb datacard of teracom drivers
this is company website
http://www.teracom.in/htmls/3G.html
http://www.teracom.in/htmls/3g1.pdf

JIGNESH_MODI

I appreciate you want to get something going but spamming the forum with requests is not the way to go about it. On some googling your device seems that it may be supported by most puppies out of the box.
http://antojose.com/content/quick-how-t ... 0-maverick
According to that article your device ID is 19d2:2000 which is listed in the udev rules for usb_modeswitch in puppy.
Try pupdial, and if you have problems search for a solution. If you still have problems search for an appropriate thread to ask for help, which this one is not.
Puppy has very good support for a large variety of 3G modems in all kernels for a few years now.
Cheers

Gamepad devices are generally supported in Puppy 4.1/4.2 by the usbhid driver, but the "force feedback" function of this driver is not enabled in Puppy.

Now attached is the usbhid driver, upgraded with force feedback support, for the following gamepad devices:
- Logitech WingMan Cordless RumblePad
- Logitech WingMan Cordless RumblePad 2
- Logitech WingMan Force 3D
- Logitech Formula Force EX
- Logitech MOMO Force wheel
- Microsoft Sidewinder Force Feedback 2
- PantherLord/GreenAsia game controller
- Thrustmaster FireStore Dual Power 2
- Thurstmaster Ferrari GT Rumble Force
- Zeroplus game controller

After installing this dotpet, reboot. Run "lsmod" to check that the new usbhid module, plus evdev module, have automatically loaded. If not, load them both manually, as such - Hopefully force feedback will now work. To test, you can install the joystick-utils dotpet, then run this command - The joystick-utils dotpet package also contains these utilities:
evtest
inputattach
jstest
jscal
ffset