Fujitsu S series lifebook wifi on

eth0 is your wired lan connection. Your wireless connection should be wlan0.

Ok. Well I was actually trying two different things. The first was to establish an Internet connection and the second was to connect to my other laptop with ssh. lspci shows eth0 being Realtek RTL-8139/8139C/8139+ (doing this from memory so I hope these numbers are right). I have loaded what seemed to be relevant modules....RTL8139c, RTL8139too, ipw2200, etc. For wlan it shows Broadcom device, and again I have loaded relevant modules.....b43, b43-legacy, etc.

?

No, I didn't get an answer yet I have received this email repeatedly asking me to choose the best answer. There was one response and it was hardly an answer.

bmourning,


1) I found that none of the commands I tried from the rfkill man page yielded any results other than error messages.

2) Per your suggestion, I did a bit of digging and found the specs for this particular Fujitsu here.

3) As it turns out, there is some wacky little WLAN on/off switch in the BACK of the computer.



4) while toggling this switch DID enable wlan0 to be raised on one version of PuppyLinux I have on usb, it failed on another, leading me to believe that there is some wvdial configuration issue which is a separate problem, but solvable through the appropriate forum.

Anyway, it works, so thanks for the help.

 

Best answer selected by Dennola4.

Glad to be of service, although I'd be surprised if wvdial is causing an issue here since the toolset is usually used for PPP/dialup type connections, unless you're doing something kinda odd like a wireless connection to a PPPoE-type modem

Ready to do some reading?? :-)

I have several different versions of Puppy on several different usb devices. Most of them are configured to automatically connect to the Internet using my PCMCIA card (Sprint Sierra Wireless Card). After having turned the Fujitsu external switch to the on position, the usb device containing Puppy 4.1.2 successfully raised wlan0 and connected to an open network while the two with LUPU did not. I ran the 4.3.1 live cd and it also successfully raised wlan0 and connected to an open network so I started thinking: maybe there was some /etc file associated with connection which was automatically configured for me as a result of some gui button-push, but my guesses (i.e. wvdial) are just ignorant shots in the dark since I don't fully understand the functionality of these programs.

This all started because my partner's macbook monitor died. While the computer is being fixed I thought I'd dust off of her old Fujitsu (which has a borked HDD) and run Puppy on it from usb. It runs fine but there was an Internet connectivity issue, hence this thread. Unfortunately the open local network we usually connect to provides a very weak signal on the old Fujitsu and is virtually unusable. I find that we can tether it to her mobile device (which becomes a hotspot) but encryption options for the older Puppies is Open and WEP, but not WPA/WPA2.

So to make my Linux-on-old-laptop solution a success, I either need to have her switch her mobile hotspot from WPA encryption to Open (Booooo!!!) or find a way to create an ad hoc network wherby she can connect to my laptop which runs SalixOS 13.1, stays on all day so I can access it remotely from work, and which she is NOT allowed to use. ;-)

Whew. Anyway, thanks again for the help.