@Jades. You should post dmesg result after you have booted to the desktop:
dmesg > dmesg.gz and post the file to the forum. It should show the wireless load attempt and what the failure is and also what firmware does it try to load, even the name of the firmware with version numbers.
Other way is to run pmodemdiag command and post the created tar ball here.

@micko. If you check with: modinfo carl9170 , you get the firmwares which it wants and then check the /all-firmware/carl9170 folder if there is some firmware missing. You get the firmwares from kernel org:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

Edit. Except the carl9170 does not seem to be in kernel org firmware tar ball.
There is only one firmware dependency for it in my kernel: firmware: carl9170-1.fwEdited_time_total

@Jades. You should post dmesg result after you have booted to the desktop:
dmesg > dmesg.gz and post the file to the forum. It should show the wireless load attempt and what the failure is and also what firmware does it try to load, even the name of the firmware with version numbers.

I've attached the resulting reports, one from a start without a savefile (chose 0 option at file selection prompt) and one using one which is fairly old and been upgraded a few times. The latter was working properly with 5.3.3 before its most recent upgrade.

pemasu wrote:

Other way is to run pmodemdiag command and post the created tar ball here.

I'll get back to you on that, I want to check its output for stuff like passwords and MAC addresses before posting.

When I used the usb install, when you goto select the iso image(to install sys from), if I have to search for the iso image on another drive in the file browser, and goto select it, then click ok, I get an error(i forgot what it said exactly-something to the effect, couldnt do it).

But if the iso image is in the initial folder(I can copy the iso image over), and then select it, everything is ok.

When I used the usb install, when you goto select the iso image(to install sys from), if I have to search for the iso image on another drive in the file browser, and goto select it, then click ok, I get an error(i forgot what it said exactly-something to the effect, couldnt do it).

But if the iso image is in the initial folder(I can copy the iso image over), and then select it, everything is ok.

Hope this is helpful.

I have found this is normal results.
What I find that works is to mount the device the iso file is on.
In a file manager, go to location of the iso file.
Left click on iso file to mount it.
Now run the USB install.
it seems now able to find the iso file._________________I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected

Try the firmware pet attached. If it works fine I'll merge it with the main build.

Thanks. I've given it a go and the news is somewhat mixed.

On the bright side, as soon as the Pet had installed, and I disconnected and reconnected the dongle, the WN111v2 was visible and I could set it up. Settings have remained over several boots now. When it is working the speed seems to be normal.

Unfortunately, I'm still getting an odd problem which I saw in 5.3.2.1 where the connection seems to stop working after a while. The desktop icon still shows it as connected, but if I ping the router or other devices on the network then nothing happens. Hitting Ctrl-C to exit ping shows 100% packet loss, and trying to ping the machine from another computer on the network gives a Host is Down error.

This is a driver issue with the kernel module.I had the exact issue several years ago with the rtl8187 driver but over the years the devs fixed it.

Thought that might be the case, I have had issues with the WN111v2 and Slacko before. On 5.3.1 and the test builds leading up to it, it worked - sort of, chucked out a load of interference on audio and was very slow. The connection stayed up, however.

01micko wrote:

Does this work well with other kernels?

Now's as good a time as any to further confess to not being up with the finer points of Linux (still!), do you mean you want me to try the pet you posted earlier with other versions of Puppy?

FWIW, the dongle works out of the box with all Lupu releases from 501 [1] to 528 005 inclusive. Also works perfectly on Slacko 533. I assume the solution is not a simple case of just using the drivers off that.

01micko wrote:

There is a work-around you can employ. I suggested it earlier in this thread here. Give it a try.

I'll have a look and get back to you, hopefully sometime tomorrow if I have time.

01micko wrote:

Thanks for your report.

My pleasure. Glad to help, even if sometimes it seems to me that my 'help' means I prod something and go "It's wrong!"

Notes:-

1. In fact, the excellent performance of Puppy on the Pentium D machine meant I abandoned the original idea of only using Puppy on the K6-2 500 and using something like Ubuntu on the former machine._________________Zhaan - AMD K6 2 500, 512MB RAM, ATI Rage 128 VR. Full install Wary 5.5 HardInfo Report
Merlin - Core i5-4590, 8GB RAM, Radeon R9 270X. Slacko 5.7.0

Just to confirm, is the effect of this command to add a line to rc.local which throttles the speed of wlan0 to 5.5Mbps, and which is only executed after reboot? I know it should be obvious, but thought I'd check first. Don't want to waste your time with reports of "barely crawls along at 5.5Mbps" if that was the intended effect.

Quote:

I know it seems slow but it's probably faster than your internet so the only time it will affect is on LAN browsing/transfers. You can try 11 instead of 5.5 or even higher if you are adventurous.