I have the same problem as Bart, and I can provide a bit more information. Obviously there is no guarantee that my extra information applies to Bart's laptop, but I bet it does.
The panic occurs after dhclient starts up and before it prints any messages about any network interfaces. I assume that dhclient is trying to configure the wireless interface, prompting the firmware loader to jump in to action and then we get the panic shortly after that. My laptop (glorious corporate standard laptop that it is) has no way of disabling the wireless card, you can only disable the radio on the wireless card. I removed the wireless card from the laptop and everything worked fine. I couldn't get g4u to boot in single user mode, so I can't get a dmesg report from the wireless card. The howto boot flag of (0x2) seems to be ignored and g4u always seemed to do a normal startup. I expect that suitable workarounds will be to either include the wpi firmware on the miniroot, or remove the wpi driver from the kernel. Cheers, Lloyd ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ g4u-help mailing list g4u-help@feyrer.de https://lists.sourceforge.net/lists/listinfo/g4u-help
