Now that we have cleared up the separate issues of tubby's modem problem, we can move on to wifi.

tubby wrote:

The wifi interface is listed as MPC13A-20 the FCC ID:CJ6PA3070WL

I just Googled for details about that wifi device, and apparently it's a miniPCI wifi card with an Agere/Orinoco chipset. Puppy should probably support this device with either the orinoco_pci driver or hostap_pci driver.

tubby wrote:

If you can shed some light on why it is detected and initialized ok in Dingo but no other 4series it would no doubt help other puppy users who have the same interfaces.

Well you could help diagnose the problem by running this command immediately after boot up -

Code:

lspci -n

and paste the results here.

Now activate the switch that you referred to earlier, off, then on, and run the same command again.
This is almost certainly a wifi switch, not a modem switch as you first reported!
Paste the second set of results here.

Hopefully we will see the wifi device listed ... if not in both sets of results, at least in the second set of results.

/usr/sbin/net-setup.sh: line 1672: /sys/class/net/eth1/device/device: No such file or directory
/usr/sbin/net-setup.sh: line 1674: /sys/class/net/eth1/device/vendor: No such file or directory
/usr/sbin/net-setup.sh: line 991: 12806 Terminated gtkdialog3 --program NETWIZ_Connecting_DIALOG
sed: can't read /etc/network-wizard/wireless/profiles/00:1F:9F:88:BC:7D.Open.conf: No such file or directory

The above is xerrs.log after connecting via setup wizard,after switching off then on. Even with the above message i now have an internet connection.

Well in both cases no wifi device is listed.
So this is low-level problem, related to how the kernel interacts with your laptop's bios.
I suggest you first check your bios and see if there is an option for "Pnp OS = YES/NO". If so, set it for "NO". This is a well-known and important setting to run Linux on older hardware.
Now run "lspci -n" again and hopefully you will see a new listing for the wifi device.

If there is no such bios setting, then you should try the following boot options, one at a time:
pci=biosirq
acpi=noirq
acpi=strict
pci=nosort
irqpoll routeirq

But I see on the web that your Agere/Orinoco wifi device is known to create resource conflicts under Windows 2000, too. I suggest that a thorough solution would be to replace this miniPCI device with a more modern wifi device, one with G-mode or even N-mode wifi support. My own preference would be for a Ralink-based device.

Thank you for your ideas and comments Tempestuous, i will try what you suggest and post results.
I am still a bit concerned that the hardware is detected and initallised in Dingo4 at boot but not in any of the later distros, there must have been a change in the way hardware is detected at boot surely?.

It looks like it was the kernel, i am using the pup-431-k2.6.25.16-intel_modems.iso on a live cd and it connected without any problem.
I am now going to do a frugal install to see if it still connects ok.
Many thanks for your help Tempestuous and i hope this helps other puppy users.

HI,
I'm very happy with 4.30 full version. I even got my cheap ($8.95) ebay wireless card to work!

I have an annoyance with the sound though.
I am happy that ALSA finds my sound card, and assigns to it, driver snd_es1968. When I run ALSA, it always picks it up, and it works, with all the bells and whistles. BUT, as soon as I reboot, it's gone, and I have to re-run ALSA. I never hear a bark on bootup (I noticed that with Lighthouse, I would always hear "hello". I really like Lighthouse, but my puppypc would not behave with it).

I am using kernel 2.6.30.5, along with the zp430305.sfs. I only see one intel driver in /lib/module/2.6.30.5/intelmodem: Intel536.ko.

This in my trusty Micron Trek 2, with PII, 256RAM, 10G hd. Oh, the sound-card is an ESS Maestro 2.

I've seen a few threads on similar issues, and have tried some of the fixes, but no luck. I'm not sure if this can be considered a BUG, though.

I use an nvidia GeForce FX 5200 PCI graphics card on my main system The card is 32 bit and clock: 66MHz. My mainboard is MSI with an Intel 64 Bit CPU and 2 gigs of memory. Monitor is HP w1907 connected with DVI cable.

Puppy 4.2 and earlier was a no brainer to select xvesa and set my resolution, yet with 4.3 (haven't tried 4.3.1 yet) any resolution I choose does not show JWM tray. I can get by this way but it is inconvenient. Ideas? Opinions? Am I an idiot? I know the answer to '3'.

Hi Tempestuous, i have now done a frugal install and network settings are saved and blinky loads in the tray, however there is still no connection.
I have solved the issue by installing dhcp and dhclient, then placing a symlink to dhclient in the startup folder.
This method does not work on the later kernel.