I don't have a network adapter, but I have a USB wireless...

[danielb]

Its loading over NFS.
If you want me to that tmpfs thing explain me how...

[Mega Man]

Start it without the WLAN stick and enter the command:
mount -t tmpfs tmpfs /lib/firmware
Then copy the firmware to /lib/firmware.
Now you can plug in the WLAN stick.
I am assuming that /lib/firmware is the directory where you copied the firmware in the previous tests.

[danielb]

Same error -22
Its possible the problem is the ps2_ohci module?

[Mega Man]

Ths ps2_ohci is in general the same driver as the normal ohci, but has a different configuration. Special DMA memory is used which is located on the IOP side.

There is an error message which I didn't checked before: "ath9k_htc: Unable to allocate URBs". This means that it can't allocate memory for the USB bulk transfers. It tries to allocate:
8 x 32KByte + 8 x 16kByte + several other stuff
The special design of the function kmalloc() leads to the allocation of:
16 x 64KByte + 16 x 32KByte + several other stuff
So it allocates at least 768KByte. For a simple driver and the PS2 this is already heavy. There are 2 problems which can occur:
1. Not enough memory.
2. Heavy memory fragementation.
The NFS already has problems with memory leaks which increases both problems. If there is enough memory free, but the memory is fragmented, it will not be able to allocate it. If one of the 2 problems occur, it is not possible to use the driver.

What can be done to fix the problem?
1. Use a swap partition. This can help with memory fragmentation.
2. Load the driver as early as possible and connect the WLAN stick as early as possible.
3. Maybe it is working if you don't use NFS.
4. Fix the problem in the driver. There can be vmalloc() used instead of kmalloc(), but I don't know if USB needs physically contiguous memory.

The module can be linked into the kernel, but the kernel needs to stay small enough to be able to load it (smaller than 6MByte or less if VGA is used). Then the WLAN stick needs to be connected at boot time. If you disconnect it and reconnect it, you can get the error again.

[danielb]

Ths ps2_ohci is in general the same driver as the normal ohci, but has a different configuration. Special DMA memory is used which is located on the IOP side.

There is an error message which I didn't checked before: "ath9k_htc: Unable to allocate URBs". This means that it can't allocate memory for the USB bulk transfers. It tries to allocate:
8 x 32KByte + 8 x 16kByte + several other stuff
The special design of the function kmalloc() leads to the allocation of:
16 x 64KByte + 16 x 32KByte + several other stuff
So it allocates at least 768KByte. For a simple driver and the PS2 this is already heavy. There are 2 problems which can occur:
1. Not enough memory.
2. Heavy memory fragementation.
The NFS already has problems with memory leaks which increases both problems. If there is enough memory free, but the memory is fragmented, it will not be able to allocate it. If one of the 2 problems occur, it is not possible to use the driver.

What can be done to fix the problem?
1. Use a swap partition. This can help with memory fragmentation.
2. Load the driver as early as possible and connect the WLAN stick as early as possible.
3. Maybe it is working if you don't use NFS.
4. Fix the problem in the driver. There can be vmalloc() used instead of kmalloc(), but I don't know if USB needs physically contiguous memory.

The module can be linked into the kernel, but the kernel needs to stay small enough to be able to load it (smaller than 6MByte or less if VGA is used). Then the WLAN stick needs to be connected at boot time. If you disconnect it and reconnect it, you can get the error again.

1- I already setup swap when i login .bashrc
2- Also I already did that the fast as possible, same...
3- I will try with usb then
If you can get me a kernel with the module i can test. I wont use any GUI so i think that wont be a problem

Currently im out of home i only be back in 2 days!

[Mega Man]

Putting the new module into the kernel seems to be complicated. Earlier or later I will switch to a newer kernel then it will be possible.

Currently you need to try the other possibitlies.

[danielb]

I cant get it to boot from USB!
Here is a screen:

I have: root=/dev/sda2 autostart=10
sda1 fat32
sda2 ext3
sda3 swap

[Mega Man]

You need to use the old initrd.usb2.gz with newroot=/dev/sda2.

[danielb]

Either i'm doing something wrong or the usb wifi isn't working with usb root.

I have extracted the modules, copied the firmware files connected the wifi and the system doest load the driver ....
i tried modprobe ath9k and it loaded sucessfuly but still the device is not detected!
And yes i did that depmod command

[Mega Man]

This sounds like that you used the old modules. Maybe you extracted the old tar archive.