I got this oops, too. It looks like netif_queue_stopped gets called before the network-device is registered. Please try the attached patch. The module loads without oops for me now, but I didn't test the functionality of the access point.

Wolfram

I had similar problems and traced them down to different architecture numbers. The shipped u-boot and kernel use a different architecture number (see arch/arm/tools/mach-types in kernel sources) than the official kernel and u-boot.
Using the original u-boot with a shipped kernel and vice versa fails because the kernel doesn't know the right board it runs on and therefore cannot initialize.

Wolfram

My guru-heater is now running for 19 hours with an usb hard drive and two ethernet connections (on 230V AC). As I already wrote I opened the case and pulled out the board a little bit. I just checked it: The heat-sink on the board is really hot, too hot in my eyes. The power supply isn't hot.

For me it looks like the heat-sink is too small and there's not enough air convection in a closed case. The power supply doesn't seem to be the source of the problem. Maybee its even a victom of the hot heat-sink.

Any other opinions or observations?

Wolfram

Hello,

I've problems with overheating, too. After some time the guru plug server plus becomes too hot and starts rebooting over and over again. I opened the case and pulled out the board a litte bit. Now its working fine but opening the case is not really a good solution.

I'm thinking about an external power supply (5V 3A?). But I'm unshure whether this would help.

Wolfram

Hello,

I miss the file 80211d_domain.conf on my guru plug server plus. Its needed by uaputl for configuring 802.11d (uaputl sys_cfg_80211d). Does anyone have this file?

BTW: Is the source of uaputl available?

Wolfram