Puppy Linux Discussion Forum

MU · Posted: Thu 02 Oct 2008, 21:06 Post subject:

The new Kernel has a completely new architecture for wifi.

The kernel developers started a new project for that.
It offers manufacturers, that free developers write new kernelmodules, if they are sent technical informations from the manufacturers.
This architecture shall get rid of problems with old external modules from manufacturers.

I think that started around a year ago, so the older kernels do not contain these new drivers, and also cannot be upgraded, as far as I know.

So if your old kernel has no support for a chipset, you must upgrade the whole kernel.
For Puppy, this means upgrading to a newer version of Puppy, as the kernel itself can not simply be upgraded with a pet.
For Muppy, I tried to upgrade the existing version with the new kernel.
This seems to work, there are just minor glitches, like that you must create a savefile, or that german äöüß are no longer visible in textmode (what worked with 2.6.21.7). I will try to solve that too this weekend.

Mark

zgp152 · Joined: 08 Nov 2007 Posts: 115

I succeeded with ndiswrapper. Very Happy

1) I went through the ndiswrapper process again in Muppy. In the end of the process the dialog was showing only "unload" and "cancel" as the choices. I decided to select "cancel". I propose that it were renamed "Keep" or "Keep loaded" since it then would tell better what it does. Also, IMHO the added driver or SW layer should be shown in the interface list below the previous ones, as an alternative at least.

I went through the autoprobe process. In the end, the dialog showed that 3 drivers were loaded: B44 Broadcom (for ethernet cable I/F), BCM43xx, ndiswrapper. Before seeing this I was not so sure about it. I saved the profile, since I had read in some place that it helps. I had to add MAC address manually . The rest was then pretty easy. So this setup could bear the coexistence of alternative drivers so that the connection worked.

2) I tried to repeat the same thing with Dingo 4.0. Everything was identical up to the point that ndiswrapper was loaded with the two other drivers. The profile could be well saved and loaded well again, MAC included, so there is an improvement over that of Muppy (3.01 based). However this setup with alternate drivers loaded together did not work.

It seemed that skiplisting was the way to go next.

3) In Dingo, I edited /etc/rc.d/MODULESCONFIG by adding bcm43xx in the end (+one space). At the next wizard session there was no eth1 anymore. After going through the ndiswrapper cycle, I launched searching for new interfaces, and presto, there was wlan0. The name of the I/F was a bit misleading (1390 something). Going forward, the wizard did its job and I was finally connected.

Wow, such an exhaustive effort. On repeated boots, the system autoconnects now in Dingo. Amazing.

In the beginning I expected that using ndiswrapper creates a file that looks like another driver and appears in the list in the same way. That the SW was loaded was not reflected in the GUI in such a comprehensive manner that it would have guided me. The visibility of ndiswrapper and the underlying windriver perhaps could be improved for better usability.

4) In Muppy, I made the same things. Skiplist amendment, then ndiswrapper addition and so on. The wizard in Muppy kept I/F name eth1 and did not change it to wlan0.

The only worry with Muppy and 3.01 is that the MAC address is not saved in the profile. If there is a way to add something (by txt editing) in any of the files to ensure (1) that MAC address is included and (2) to make this 3.01 based system autoconnect, I could try that, while waiting for a 4.1-based Muppy.

Rgds and thnx to all contributors,
Timo

PS added afterwards:
Just to make sure that I am not misleading anyone, my Dingo 4.0 was patched with the improved wizard coming into 4.1rc.

MU · Posted: Sat 04 Oct 2008, 18:19 Post subject:

I use a AVM Fritz wlan USB stick , see:
http://www.murga-linux.com/puppy/viewtopic.php?p=237001#237001

It works in the wizard, but the connection is not established, when Puppy starts.

After some research I found out this:
/etc/rc.d/rc.network
testInterface()

Line 94,

MU · Posted: Sun 05 Oct 2008, 05:27 Post subject:

package removed, newer version available.

BarryK · Posted: Sun 05 Oct 2008, 05:50 Post subject:

MU, Dougal,
MU, I have just seen your patch, haven't looked closely at it. Dougal, do you agree that I should update the Network Wizard with this patch?

I'm planning to build 4.1 final in about 12 hours from now, then several hours intensive testing on my PCs, then if all looks ok will release it.

So, if you would like the Network Wizard to have any mods from the Oct 1st version, kindly let me know within the next 10 - 12 hours (I'll check this thread).

Dougal · Posted: Sun 05 Oct 2008, 05:55 Post subject:

Dougal · Posted: Sun 05 Oct 2008, 05:59 Post subject:

MU · Posted: Sun 05 Oct 2008, 06:04 Post subject:

it should be tested first by others.
Until now, this seemed to be an issue only with the mentioned Fritz Stick.

My Linksys-Stick works as expected without patch.
Rt73 is also detected by ifplugstatus.
current rt73 discussion:
http://www.murga-linux.com/puppy/viewtopic.php?t=34078

I remember there were several reports in the past, that sticks did not connect at startup.
But I think, the latest fixes from dougal could solve that.

Mark

MU · Posted: Sun 05 Oct 2008, 08:33 Post subject:

ok, the damn Fritz Stick is unusable in Muppy with the new Kernel:
http://www.murga-linux.com/puppy/viewtopic.php?p=237187#237187

However, in Dingo 4.1rc (409), it still worked, so I could run some tests.

ethtool wlan0

Dougal · Posted: Sun 05 Oct 2008, 15:44 Post subject:

Another update:
- Add PATH to top of rc.network (in case it is run by acpid etc.).
- Fix the testInterface code in rc.network (up the sleep times to 2 seconds,
like in the wizard) and add use of ethtool (if available).
- In the "Load module" dialog, add a "Ndiswrapper" tab, for better visibility.
- When choosing to use Ndiswrapper, first offer to unload the Linux driver
attached to that hardware!
- Rewrite the Ndiswrapper file selector gui in gtkdialog.

Note that BLACKLIST_FILE has to be modified at the top of net-setup.sh in
order for blaklisting to work.

MU · Posted: Mon 06 Oct 2008, 08:26 Post subject:

package removed, newer version available.

cornbreadly · Joined: 15 Jun 2008 Posts: 8

I am having some newb issues with 4.1rc and i was referred to this thread for some help.

I have an Airlink101 AWLC4130 wireless card (Atheros AR5212 chipset) that i am trying to get working. I upgraded to 4.1rc from macpuppy 4.0 because 4.1rc supports the madwifi .94 drivers and puppy 4.0 does not.

I get alot further in this verision of puppy. Before in macpuppy the interface atho was recognized but i couldn't scan and find any networks. Now in 4.1, I can scan and find networks, but i just can't connect. My home is WPA protected and wpa_supplicant is nowhere to be found.

Also, in 4.1rc, the ath0 interface is the only one recognized. eth0 and wlan0 that were present in macpuppy dont show up and I tried autoprobing. Nothing. All cables are connected.

My troubles are explained at length here.

I would appreciate any help.

cornbreadly · Joined: 15 Jun 2008 Posts: 8

please ignore double post... sorry