Somebody in the thread at some point said: > Ndiswrapper is not the problem here. The problem is clearly coming from the > Linux kernel itself; messages shows repeated errors being spit out by the > kernel. The regular Fedora kernels just freeze. Hard to be certain about where "the problem" is coming from, "sleeping functions called from invalid contexts" is likely a diagnostic by the kernel "itself" about something ndiswrapper has done. What is the wireless chipset? Maybe there is a better way without ndiswrapper. -Andy -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
