LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   kernel panic when trying to load ndiswrapper module (https://www.linuxquestions.org/questions/linux-newbie-8/kernel-panic-when-trying-to-load-ndiswrapper-module-4175471182/)

cristi92b 07-28-2013 02:16 AM

kernel panic when trying to load ndiswrapper module
 
I downloaded TP-LINK TL-WN822N (rtl8192cu) drivers for Windows XP 64-bit, then
Code:

ndiswrapper -i net8192cu.ini
Code:

ndiswrapper -m
I blacklisted rtl8192cu kernel module
rebooted
after reboot, when I type
Code:

modprobe wlan0
or
Code:

modprobe ndiswrapper
I get a kernel panic
http://s22.postimg.org/o7y9z9vqp/photo_3.jpg

I'm using Fedora 19, kernel 3.9.5

Why do I get a kernel panic?

flyinggeorge 07-30-2013 10:04 PM

Maybe try to use gdb to get an error of relevance. Or maybe one was posted to the logs? I don't know if you are an expert but I am sure not. Using gdb is uncomfortable at best for someone who doesn't really get it. I tried to run modprobe under gdb on my machine as an example. I am of course assuming you are able to boot the system, or can chroot to it.

I did something like this: (I don't know if this is the correct procedure check the man page for more info)

Code:

# gdb modprobe
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-slackware-linux".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /sbin/modprobe...(no debugging symbols found)...done.
(gdb) run /sbin/modprobe

I'm not sure if this will give you any useful output as I am not quite sure if you can stick the 'ndiswrapper' on there. Also try checking 'dmesg | tail' sometimes there are clues here. Or you can go and read days worth of logs from dmesg by checking /var/log/dmesg. Hope some of this helps.


All times are GMT -5. The time now is 02:54 AM.