Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 01 Aug 2014, 12:02
All times are UTC - 4
 Forum index » Advanced Topics » Hardware » Networking » Wireless
Trouble networking Zyxel g-302v2 Wifi, also Linksys WPC54Gv2
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [16 Posts]   Goto page: 1, 2 Next
Author Message
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Thu 30 Nov 2006, 00:22    Post subject:  Trouble networking Zyxel g-302v2 Wifi, also Linksys WPC54Gv2
Subject description: (NOW FIXED FOR BOTH Zyxel g-302v2 PC AND Linksys WPC54Gv2 LAPTOP!)
 

[ Now online WIRELESSLY with Puppy 2.14!!! See latest posts below.]

Hello folks. I am able to get on the net just fine with Puppy 2.12 using a machine hard-wired to my wireless AP/router (Dlink DI-524 AirPlus G). The trouble is with my secondary PC which has a Zyxel g-302v2 Wifi PCI card. This has the TI ACX (TNET1130) chipset.

I have tried the Puppy Wireless networking wizard to configure things, trying both the built-in ACX driver and loading in my Windows XP .INF with the NDISWrapper. Both approaches show that the wlan0 device is present and detects my WLAN network, but neither seems to work when I try a DHCP request, or I statically assign an IP (same as what the machine normally gets when it boots into Windows XP).

When I view the D-Link AP/router's internal log, I can see that my Puppy computer is associated with the AP, with the correct MAC and a fresh timestamp. But I can't PING the Puppy PC from another PC in the LAN, nor can I PING from Puppy to the router or another PC in my home LAN. And, of course, I don't have any web or other networking functions either. This pretty frustrating because I seem so close!

Here is a dump of ifconfig, iwconfig, route, ping, and some of my kernel messages.

Code:
sh-3.00# 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:193 errors:0 dropped:0 overruns:0 frame:0
          TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:17476 (17.0 KiB)  TX bytes:17476 (17.0 KiB)

wlan0     Link encap:Ethernet  HWaddr <<my WiFi Card's MAC address>>
          inet addr:192.168.0.101  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:102 errors:5 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:5928 (5.7 KiB)
          Interrupt:10

sh-3.00# iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11b+/g+  ESSID:"<<my ESSID>>"  Nickname:"acx v0.3.35"
          Mode:Managed  Frequency:2.427 GHz  Access Point: <<my access point MAC>>   
          Bit Rate:1 Mb/s   Tx-Power=15 dBm   Sensitivity=1/3 
          Retry min limit:7   RTS thr:off   
          Encryption key:off
          Power Management:off
          Link Quality=46/100  Signal level=24/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:5  Invalid misc:0   Missed beacon:0

eth0      no wireless extensions.

sh-3.00# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 wlan0
loopback        *               255.0.0.0       U     0      0        0 lo
default         192.168.0.1     0.0.0.0         UG    0      0        0 wlan0

sh-3.00# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes

--- 192.168.0.1 ping statistics ---
38 packets transmitted, 0 packets received, 100% packet loss


[MESSAGES]
Nov 29 22:53:07 (none) user.warn kernel: scan table: SSID='<<my ESSID>>' CH=4 SIR=22 SNR=0
Nov 29 22:53:07 (none) user.warn kernel: peer_cap 0x0431, needed_cap 0x0001
Nov 29 22:53:07 (none) user.warn kernel: found station with matching ESSID! ('<<my ESSID>>' station, '<<my ESSID>>' config)
Nov 29 22:53:07 (none) user.warn kernel: matching station found: <<my AP's MAC Address>>, joining
Nov 29 22:53:07 (none) user.warn kernel: sending authentication1 request, awaiting response
Nov 29 22:53:07 (none) user.warn kernel: acx_set_status(2):WAIT_AUTH
Nov 29 22:53:07 (none) user.warn kernel: rates_basic:0003, rates_supported:1FFF
Nov 29 22:53:07 (none) user.warn kernel: AUTHEN adev->addr=<<my WEP key info... 128 bits>>
Nov 29 22:53:07 (none) user.warn kernel: algorithm is ok
Nov 29 22:53:07 (none) user.warn kernel: acx_process_authen auth seq step 2
Nov 29 22:53:07 (none) user.warn kernel: acx_set_status(3):AUTHENTICATED
Nov 29 22:53:07 (none) user.warn kernel: sending association request, awaiting response. NOT ASSOCIATED YET
Nov 29 22:53:07 (none) user.warn kernel: association: requesting caps 0x0021, ESSID '<<my ESSID>>'
Nov 29 22:53:07 (none) user.warn kernel: BSS_Type = 2
Nov 29 22:53:07 (none) user.warn kernel: JoinBSSID MAC:<<my AP's MAC Address>>
Nov 29 22:53:07 (none) user.warn kernel: acx_set_status(4):ASSOCIATED
Nov 29 22:53:07 (none) user.warn kernel: ASSOCIATED!
Nov 29 22:53:08 (none) user.warn kernel: acx_i_timer: adev->status=4 (ASSOCIATED)



(Note: I redacted some of my private MAC and ESSID info, but it looks consistent with what I expect). I hope someone out there sees something I should be doing differently or has a good idea for me to try. Thanks for any guidance!
---
Mike Lockmoore

Last edited by MikeLockmoore on Thu 05 Apr 2007, 00:35; edited 4 times in total
Back to top
View user's profile Send private message 
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Mon 04 Dec 2006, 22:32    Post subject:  

I did a bit more research and dug up this person's observations about getting my type of WiFi card to work with Ubuntu:

Quote:
Late May 2006, I bought a really cheap wireless card, the Zyxel ZyAir G-302v2 802.11b+g for a Linux machine. After rebates it only cost $10.

I got it to work under Ubuntu 6.06, kernel 2.6.15-23-386, ndiswrapper 1.8.

Make sure you remove acx Kernel module as this conflicts and does not work. Next Ubuntu release with latest acx Kernel module will probably work.

...

The acx kernel module is located in:

/lib/modules/2.6.15-23-386/kernel/drivers/net/wireless/acx/acx.ko

As this kernel module detects the ZyXEL card, but does not actually work with the card, it conflicts with the working ndiswrapper solution. Hopefully in future Ubuntu releases the acx kernel module will work fine for the card and ndiswrapper won't need to be used.

So just delete the acx kernel module file and load the driver using ndiswrapper and your supplied CDs.


Perhaps the conflict is happening with Puppy Linux too? Is there some modprobe voodo I should try to disable or remove the built-in ACX driver before loading the NDISWrapper version? Thanks for any suggestions, guys.

_________________
Mike Lockmoore
Back to top
View user's profile Send private message 
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Thu 07 Dec 2006, 00:06    Post subject:  

Well, I am still not having any luck with Puppy on wireless. My original post in this thread was based on trying to get my secondary desktop PC running a Puppy 2.12 Live CD to use its Zyxel wireless card.

Since then, I have installed Puppy 2.12 on my Windows XP laptop using the excellent "Lin'N'WinNewB"(http://www.icpug.org.uk/national/linnwin/step01-4steps.htm) instructions. I am posting this with that laptop using a hard-wired connection to my wireless AP/router (eth0). It is working great. But this laptop has a Linsys PCMCIA Wifi adapter that uses the same TI ACX chipset as the Zyxel card, and I am having the same kinds of problems getting any connectivity working over WiFi.

I can't ping other machines in my WiFi LAN, and I can't even ping the router. The initial ROUTE table looks reasonable, and the DMESG statements show the laptop has associated with the router. When I view the router's packet statistics (using a web interface on another PC) during a ping attempt, I can see the wireless packet count increasing at a moderate pace, even though all the packets seem to get dropped. When I break out of the ping, the wireless packet rate drops off sharply, so something is going on. Confused

Please, I hope someone out there has a suggestion to help me diagnose the problem! Thanks.

_________________
Mike Lockmoore
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 7047
Location: Perth, Western Australia

PostPosted: Thu 07 Dec 2006, 07:16    Post subject:  

No, don't delete the acx kernel module. In pup 2.12, at next boot puppy
will just go and fetch it again from the "zdrv" drivers file (after all, he
is a playful puppy dog!).

The easiest thing would be to unmount it. Add this to /etc/rc.d/rc.local:
rmmod acx
Back to top
View user's profile Send private message Visit poster's website 
marksouth2000

Joined: 05 Apr 2006
Posts: 620

PostPosted: Thu 07 Dec 2006, 13:00    Post subject:  

How do you hard-wire your connections, BTW? Also, I'm curious to understand why Cat5 cable doesn't work for you? Government spying??

It sounds fascinating, anyway.
Back to top
View user's profile Send private message 
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Thu 07 Dec 2006, 14:21    Post subject:  

Thanks Barry for the suggestion to use rmmod. I'll do that and see if the NDISWrapper-based device driver behaves any better with my Wifi cards and home network.

The fact that I don't see any error-type messages using DMESG and that my router is getting some kind of wireless packets from my associated PCs leads me to believe it is not the ACX or NDISWrapper driver that is the problem, but I don't know enough so far about the IP route mechanism including forwarding & masquarading to tell if I have a problem with that side of things.

MarkSouth2000: The only reason I use wireless is convenience and cost. My "main" desktop PC is hard-wired into my WirelessAP/router device. I _can_ plug more computers into the router with CAT5 cable, but the secondary desktop PC is far enough away a CAT5 cable would cost about the same if not more than the WiFi card and would be uglier (without running cable behind a baseboard or something). And the point of a laptop (my 3rd machine) is to move it around, right?

Anyway, both the desktop PC with Zyxel card and the Laptop with the Linksys PCMCIA card connect easily and work well over WiFi when using Windows XP (home edition on the desktop and pro on the laptop). Puppy 2.12 connects perfectly from my laptop and from my main PC when they are wired with CAT5 from the Ethernet port to the wireless router, so it seems like I am close to having a WiFi-enabled Puppy. I just need to find and set the "make it work" bit somewhere. Smile

So the bottom line is: I don't want to leash my Puppies with CAT5 if I don't have to!

_________________
Mike Lockmoore
Back to top
View user's profile Send private message 
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Fri 08 Dec 2006, 01:17    Post subject:  

Unfortunately, I am not much farther along.

I was able to remove the acx module as Barry suggested, but when I tried to load the NDIS module, NDISWrapper cannot load a file (I think it is the ACX 111 firmware file that goes into the card's chipset). Does anyone have any ideas on how I can get this to work properly? I don't think the "memory allocation" problem in the kernel messages is related to my main system RAM (which has over 100 MB free), but probably the EEPROM on the Zyxel card. Here is a DMESG dump:
Code:
switching off power LED to save power
removing device wlan0
removing /proc entry driver/acx_wlan0
removing /proc entry driver/acx_wlan0_diag
removing /proc entry driver/acx_wlan0_eeprom
removing /proc entry driver/acx_wlan0_phy
ACPI: PCI interrupt for device 0000:00:06.0 disabled
usbcore: deregistering driver acx_usb
ISO 9660 Extensions: RRIP_1991A
ndiswrapper version 1.26 loaded (preempt=no,smp=no)
ndiswrapper: driver tnet1130 (ZyXEL,12/01/2004,7.0.1.33) loaded
PCI: Enabling device 0000:00:06.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
ndiswrapper (add_bin_file:320): couldn't allocate memory
ndiswrapper (get_bin_file:282): loadndiswrapper failed (59904); check system log for messages from 'loadndisdriver'
ndiswrapper (miniport_init:269): couldn't initialize device: C0000001
ndiswrapper (pnp_start_device:426): Windows driver couldn't initialize the device (C0000001)
unregister_netdevice: device eth%d/d459c000 never was registered
ndiswrapper (miniport_halt:326): device d459c280 is not initialized - not halting
ndiswrapper: device eth%d removed
ACPI: PCI interrupt for device 0000:00:06.0 disabled
ndiswrapper: probe of 0000:00:06.0 failed with error -22
usbcore: registered new driver ndiswrapper


So I went back to trying the ACX driver again after a clean boot so I could look at the info in the /proc/driver/acx_wlan0* virtual files. Here is a copy of the content of /proc/driver/acx_wlan0 and /proc/driver/acx_wlan0_diag. Note the "rx_dropped' item tagged below...
Code:
acx driver version:      v0.3.35
Wireless extension version:   20
chip name:         TNETW1130 (0x03010101)
radio type:         0x16
form factor:         0x01
EEPROM version:         0x05
firmware version:      Rev 1.2.1.34 (0x01020134)
status:         1 (SCANNING)
** Rx buf **
00 empty
01 empty
...
12 empty [tail]
...
** Tx buf (free 15, Linux netqueue STOPPED) **
00 free (C0) [tail]
01 tx   (80) [head]
02 tx   (80)
...

** PCI data **
txbuf_start d1f10000, txbuf_area_size 37536, txbuf_startphy 11f10000
txdesc_size 52, txdesc_start dc992a94
txhostdesc_start d1eb1000, txhostdesc_area_size 896, txhostdesc_startphy 11eb1000
rxdesc_start dc992754
rxhostdesc_start d28a1000, rxhostdesc_area_size 448, rxhostdesc_startphy 128a1000
rxbuf_start d1f20000, rxbuf_area_size 38240, rxbuf_startphy 11f20000

** network status **
dev_state_mask 0x0003
status 1 (SCANNING), mode 2, channel 4, reg_dom_id 0x10, reg_dom_chanmask 0x07FF, ESSID "**********", essid_active 1, essid_len 10, essid_for_assoc "**********", nick "acx v0.3.35"
WEP ena 0, restricted 0, idx 0
dev_addr  00:13:49:**:**:**
bssid     00:11:95:**:**:**
ap_filter FF:FF:FF:FF:FF:FF

** PHY status **
tx_disabled 0, tx_level_dbm 15
sensitivity 1, antenna 0x4A, ed_threshold 0, cca 0, preamble_mode 2
rts_threshold 2312, frag_threshold 2346, short_retry 7, long_retry 4
msdu_lifetime 4096, listen_interval 100, beacon_interval 100

** Firmware **
NOTE: version dependent statistics layout, please report if you suspect wrong parsing!

version "Rev 1.2.1.34"
Rx/Tx:
  tx_desc_overfl 0
  rx_OutOfMem 0, rx_hdr_overfl 0, rx_hw_stuck 0
  >>>>>>>>>> LOOK AT THIS !!! <<<<<<<<<<<<<<<<<<<<<
  rx_dropped_frame 95523, rx_frame_ptr_err 95520, rx_xfr_hint_trig 9660
  rx_aci_events 9660, rx_aci_resets 0
  >>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<
DMA:
  rx_dma_req 33, rx_dma_err 0, tx_dma_req 128, tx_dma_err 0
IRQ:
  cmd_cplt 21993, fiq 105884
  rx_hdrs 0, rx_cmplt 0, rx_mem_overfl 243694, rx_rdys 33
  irqs 0, tx_procs 0, decrypt_done 0
  dma_0_done 33, dma_1_done 129, tx_exch_complet 0
  commands 0, rx_procs 0, hw_pm_mode_changes 0
  host_acks 0, pci_pm 0, acm_wakeups 0
WEP:
  wep_key_count 0, wep_default_key_count 701, dot11_def_key_mib 0
  wep_key_not_found 0, wep_decrypt_fail 0
  wep_pkt_decrypt 0, wep_decrypt_irqs 0
power:
  tx_start_ctr 0, no_ps_tx_too_short 0
  rx_start_ctr 0, no_ps_rx_too_short 0
  lppd_started 0
  no_lppd_too_noisy 0, no_lppd_too_short 0, no_lppd_matching_frame 0
MIC:
  mic_rx_pkts 0, mic_calc_fail 0
AES:
  aes_enc_fail 0, aes_dec_fail 0
  aes_enc_pkts 0, aes_dec_pkts 0
  aes_enc_irq 2313, aes_dec_irq 1
failed at event part (size 32), offset 220 (struct size 240), please report
UNKN220: 6
UNKN224: 0
UNKN228: 0
UNKN232: 0
UNKN236: 0


I don't know why that's a problem, but my current theory is that the driver is not loading appropriate firmware into the wireless card, so all received packets are being dropped instead of passed on to the Linux networking stack.

I read a bit of the sourceforge acx device driver wiki, and it appears there are multiple ACX chipset firmware files (maybe two different ones for the TNET1130 ACX chipset version?) that can be used with the acx driver. Maybe Puppy 2.12 has acx firmware built-in that are not compatible with my two WiFi adapaters? Confused I'm not sure at this point if I can reconfigure the acx driver to use different firmware without recompiling the kernel. Anyone have options for me to try?

Sorry if these posts seem long. I just want to provide details that might be relevant to somebody who has worked through this type of problem before.

_________________
Mike Lockmoore
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5218
Location: Australia

PostPosted: Fri 08 Dec 2006, 10:29    Post subject:  

In /lib/firmware you could rename the existing tiacx111c16 file, then replace it with the alternative version 1.2.0.30 listed here http://acx100.sourceforge.net/wiki/Firmware
Back to top
View user's profile Send private message 
marksouth2000

Joined: 05 Apr 2006
Posts: 620

PostPosted: Fri 08 Dec 2006, 12:02    Post subject:  

MikeLockmoore wrote:
The only reason I use wireless is convenience and cost. My "main" desktop PC is hard-wired into my WirelessAP/router device. I _can_ plug more computers into the router with CAT5 cable, but the secondary desktop PC is far enough away a CAT5 cable would cost about the same if not more than the WiFi card and would be uglier (without running cable behind a baseboard or something). And the point of a laptop (my 3rd machine) is to move it around, right?

OK. I thought when you referred to "hard-wired" that you meant something different from ordinary ethernet cabling, since in electronics the term normally means wiring that can't be plugged and unplugged at will.

I fully agree that laptps should live up to their "portable" tag. And I know what a drag cabling can be, I once had to route a 50m cat5 cable to link two parts of my house. That was before cheap easy wireless Sad

Wireless can be a good solution even for desktops, I currently have a wireless desktop bridging between my main wireless router and a remote subnet in a zone of the home where I would prefer not to have to lay cat5 cable....

Good luck with your setup.
Back to top
View user's profile Send private message 
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Sat 09 Dec 2006, 01:34    Post subject:  

tempestuous: Thanks for a very good idea to try. I tried it with both 1.2.0.30 and 1.2.1.34 versions. I verified in /proc/dirver/acx_wlan0* that the firmware revision was the intended level. Unfortunately, both versions of firmware behaved the same as before... the card appears to just dump all wireless packets it receives into the "bit bucket". Maybe there is an IRQ conflict or some other reason the card never notifies the main system that it has received data? I might try the different firmware version on my laptop with the Linksys card, but I don't have high hopes at this point. Sad

MarkSouth2000: Sorry my terminology was confusing. While I used to dabble in building hardware at the wires / resistors / chips level, my computer network at home is pretty ordinary stuff right now. Unfortunately, I won't get to play with Puppy too much if I can't network my secondary PCs with it easily... the main PC is shared with my DW, who has a lot of Windows-specific stuff to do on it frequently.

_________________
Mike Lockmoore
Back to top
View user's profile Send private message 
Puppynewbie

Joined: 31 Jan 2007
Posts: 17

PostPosted: Wed 31 Jan 2007, 20:27    Post subject:  

Mike,

Did you ever get your ZyCel working?

I too have the same card.
Back to top
View user's profile Send private message 
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Thu 01 Feb 2007, 23:53    Post subject:  

Puppynewbie wrote:
Mike,

Did you ever get your ZyCel working?

I too have the same card.


Unfortunately, no. I tried again with Puppy 2.13 with both the Zyxel (in my 2nd desktop) and Linksys (in my laptop) cards, since the release notes mentioned changes to the networking wizard and the NDISWrapper device driver. Neither card works with either the built-in ACX device driver or the NDISWrapper+Windows combo. Like before, the cards appear to associate with my access point (wireless router), but won't pass any packets up to the higher software layers.

I hope you have better luck if you try it, but I probably won't try much else until there is a new version of the ACX driver available, or at least Puppy 2.14. For now, when I use Puppy, I'm on the 'net with CAT-5 cable. (Ironic, huh?)

_________________
Mike Lockmoore
Back to top
View user's profile Send private message 
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Tue 03 Apr 2007, 22:49    Post subject: Now online with Zyxel g-302v2 Wifi with Puppy 2.14!  

In the process of doing some vesafb graphics experiments, I took a "fresh" 2.14 CD (just the ISO image) and booted Puppy on my PC with a wireless card. After doing the poking around for the graphics experiment, I tried "just for fun" the wireless networking wizard in Puppy 2.14. Much to my delight it worked!

Being able to get it online with my wireless card, I wanted to make a new multi-session CD specifically for use with this PC. Unfortunately, the new CD did not work for wireless. Same general symptoms as before, so I didn't go much further until I saw a comment in this thread (http://www.murga-linux.com/puppy/viewtopic.php?t=16773) that multi-session installations are more problematic.

I went back to my 2.14 master CD and was able to get wireless working again with the wizard... no fuss, no muss. So, to keep my settings for this machine, I now have a pup-save file on a USB stick... only 128 MB on this particular one Sad, but Puppy doesn't need much to get by. Smile and I am able to reboot and get back online instantly.

I don't know yet why this set-up works and the other does not, but I am going to run with it! It sure is nice to have Puppy now available on a second machine that can go online. I can work on Linux and Puppy on one machine the same time my wife works on her Windows stuff on another. Very Happy

_________________
Mike Lockmoore
Back to top
View user's profile Send private message 
jonyo

Joined: 28 Dec 2006
Posts: 2727

PostPosted: Wed 04 Apr 2007, 12:20    Post subject:  

Real glad to hear you got connected; Very Happy pup was my first linux wifi connection. I remember it well & i've certainly run with it Very Happy

Could be many reasons why earlier versions didn't work for you; the net wiz is constantly being upgraded. Sometimes a newer version comes with new bugs & doesn't.work where earlier versions had.

.I think alot of probs come from a learning curve. It was a steep one for me & still is, so I tend to stick to what I know works. I've just recently had my first clean wifi connection straight from booting up

Be sure to fire up the firewall. Also, to back up your setup, make regular copies of your pup save file. I started over many times, when I messed up, before someone mentioned it to me. & I figured out how easy it was to do. I did try the backup feature on one earlier pup version but I couldn't get it to work..

Once you're sure about being able to save your pup system, that'd be good time to try changes (or new things) with less risk. Never hurts to ask questions first.

Last edited by jonyo on Thu 05 Apr 2007, 06:28; edited 1 time in total
Back to top
View user's profile Send private message 
MikeLockmoore


Joined: 26 Nov 2006
Posts: 43
Location: Near Detroit

PostPosted: Thu 05 Apr 2007, 01:09    Post subject: Laptop with Inksys WPC54Gv2 WiFi card now working!  

Like in my previous post about my PC with a WiFi card, by installing Puppy 2.14 on my laptop, I was able to use the wireless networking wizard and get it running with WiFi! Interesting thing, tonight I first tried installing the new 2.15CE release candidate 4. But after booting it, its version of the wireless networking wizard did not get a connection. Sad But that's OK, I like 2.14 just fine. Smile

BTW, getting either Puppy 2.14 or 2.15CE installed on my laptop was not trivial. Unfortunately, this laptop has a broken CDRW drive, so the only easy way to get things into it at this point is by LAN/WiFi (in WinXP) or by USB Flash drive.

Previously, I followed the Lin-n-Win "New-B" instructions for a Puppy 2.13 install, which worked after I tweaked the grub menu.lst file to reference the _second_ partition of my main hard drive, since Dell has placed proprietary system utilities in the first partition. I set up the Puppy 2.14 files in my WinXP "C:" drive in the same way as I did for 2.13, but when I booted it, the initialization process in Puppy 2.14 got lost. I found some forum posts about these types of installations, and noticed some appropriate-looking additional boot parameters that could be passed into the kernel through grub. This seems to put Puppy on the right track to load the main puppy .sfs file from the NTFS partition. BOTTOM LINE: It now boots and automatically connects to my WLAN, so now I can play with Puppy all over my house!

jonyo, I have been fairly careful with my networking setups so far. My WiFi AP / Ethernet router has some firewall features and is configured to require WEP with a long key. I might try WPA in the future. I have used ZoneAlarm on my Windows setups and tested them against the GRC.com service. I don't know as much yet on Linux firewalls, but I get the impression there are a zillion ways to do it, even if there is a standard puppy wizard for it.

_________________
Mike Lockmoore
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [16 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware » Networking » Wireless
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1386s ][ Queries: 11 (0.0061s) ][ GZIP on ]