Wireless Blacklisted In 2.6.24.4?

[maemorandum]

Thank you 2or0 again for the development of the kernels.

Actually I use the 2.6.23.9 kernel and jpmatrix's customization tarballrootfs for my debian network programs.
I was very happy to use the debian network diagnostic software on my zaurus. Unfortunately, there is only one option to load this kernel: uboot. The debian system on the zaurus has a lot of interesting packages and works stable - and - veeeeeeery slow. The consequence is, that if i want to use a pim-application or want to play with multimedia i have to use the cacko-rom/pdaxrom/weexpc. So, for now i use debian on a sl-c3200 and cacko on a sl-c1000. ---> I need a dualbooting environment!

For dualbooting i need the sharp bootloader. So i decided to use the actual 2.6.24.4 kernel with iptables included.
This kernel works perfectly on both zaurus. Dualbooting with a sharp-zImage did work, too. But there is be a problem with wireless cf-cards!: Activating any wireless cf-card in 2.6.24.4 ends in error messages and finally in a kernel panic. - bump! -

Code: [Select]

ifconfig wlan0 up --> kernel panic
Driver-changes from hostap too orinocco and blacklisting didnt help. Moreover, the zaurus has problems with ipv6 loading while booting. So far i have still no wireless cf-card working on the 2.6.24.4 kernel. To my suprise, the critical flashing of any wlan cf-card with new firmware works perfect.

I dont know if there is a general network-problem on the new kernel, hope, somebody can help me to get any wireless cf-card working on the new kernel.

[xamindar]

Yep, if you use the modules from the iptables package the network ones are all messed up. Just use the previous group of modules listed on the 2.6.24-4 kernel page.

[maemorandum]

Yep, if you use the modules from the iptables package the network ones are all messed up. Just use the previous group of modules listed on the 2.6.24-4 kernel page.

OK. thank you very much xamindar. Ive tested this - this kernel works with the wlan cf-cards.   Thank you.

Unfortunately i need the ip-tables-related modules, like in the 2.6.23.9-Kernel.

[xamindar]

Unfortunately i need the ip-tables-related modules, like in the 2.6.23.9-Kernel.

Why don't you just take the iptables modules out of the most recent archive and then the rest of the modules from the previous working archive of modules? Others have talked about doing that on here. Or better yet, just compile all your own modules, not that hard. Of course, I did that on my Z once and it took a good 5 hours.

[maemorandum]

Why don't you just take the iptables modules out of the most recent archive and then the rest of the modules from the previous working archive of modules?

Thank you, xamindar, that sounds very close to my wishes.

Do you know where the ip-related modules are - and will a simple

Code: [Select]

depmod -a afterwards be enough?

[xamindar]

Why don't you just take the iptables modules out of the most recent archive and then the rest of the modules from the previous working archive of modules?

Thank you, xamindar, that sounds very close to my wishes.

Do you know where the ip-related modules are - and will a simple

Code: [Select]

depmod -a afterwards be enough?

hmm, I just untarred the iptables modules, then untarred the older package over them. That should do it. Though, I didn't test them. And yes, after unpacking them a simple "depmod -a" should be good (and a reboot to load them fresh).

[maemorandum]

Why don't you just take the iptables modules out of the most recent archive and then the rest of the modules from the previous working archive of modules?

Thank you, xamindar, that sounds very close to my wishes.

Do you know where the ip-related modules are - and will a simple

Code: [Select]

depmod -a afterwards be enough?

hmm, I just untarred the iptables modules, then untarred the older package over them. That should do it. Though, I didn't test them. And yes, after unpacking them a simple "depmod -a" should be good (and a reboot to load them fresh).

Ive tested it and - it doesnt work

[scottlfa]

I found the new kernel with 2.6.24.4 modules seems to panic my system too, stepping back to the older 2.6.24-4 modules did just fine, no panics.  For me the issue was with the new injected features in the 2.6.24.4 kernel and modules.  Perhaps this is your issue too?
Hope this helps.

[maemorandum]

I found the new kernel with 2.6.24.4 modules seems to panic my system too, stepping back to the older 2.6.24-4 modules did just fine, no panics.  For me the issue was with the new injected features in the 2.6.24.4 kernel and modules.  Perhaps this is your issue too?
Hope this helps.

The old 2.6.24.4 modules work fine, but the main problem is, that i need the iptables-modules.
So, now i am using the 2.6.23.9 modules - which unfortuately need uboot (not-dualbooting).