Search results

Please try to do the same with "stable_tmp" branch available using this link: https://github.com/vladmovchan/ndisulator/commits/stable_tmp

As I can see only part of ddb commands output has been saved. I suppose some commands were interrupted with "q" key or in some other way. Please try to repeat same steps, but scroll down every command output with space key (just hold it and ddb will scroll until the end).

Your steps seems to be correct. Now lets extend amount data you are gathering from ddb. Please trigger panic one more time and type following commands in ddb prompt: textdump set capture on show allpcpu bt ps alltrace show msgbuf capture off call doadump Or do the same via ddb.conf...

Minimum possible information is just a panic message with a stack trace which consists of list of functions which got called before the panic occurs. This kind of information you will get if you just rebuild the kernel with the options mentioned above and try to kldload the module generated with...

I think this reboot is caused by kernel panic and to dig it any deeper it is necessary to rebuild kernel with at least basic debugging support to see panic message and backtrace. If you are interested - it is necessary to enable following kernel options: options KDB options...

About ndisulator-stable: Please retry the same but without reboot after step 5. Or (if reboot is necessary) execute following commands as root before running ndisgen: cd /path/ndisulator-stable make attach cd - I've just tested ndisgen step in my test environment and it went smooth with...

Thanks for detailed report. I think I found and fixed the reason of kldload: can't load ndis: Exec format error". Please download fresh version of ndisulator from github and retry. What about to Unknown USB device: vendor 0x5986 product 0x0315 bus uhub4. I think this message could be just...

I suppose to make ndis0 interface appear in ifconfig output and make it usable we have to find out what is the reason of kldload error. At this moment I have several ideas: First: please make sure there are no ndis or if_ndis modules loaded after system reboot - I want to make sure there...

G_Nerc, thank you for the kind words. I've finished testing recent FreeBSD current with ndisulator. Here is what I got: In case of FreeBSD current there are two options: First is to use "stable" branch of ndisulator. In this case it is possible to use step-by-step provided few messages...

It took some time to setup test environment on freebsd 9 to check "stable9" branch of ndisulator. I can confirm there was a problem and now it is fixed. I mean now it is possible to use "stable9" on freebsd 9 with steps from above. What about to freebsd current - I need some time to setup and...

I'm sorry for delay with the answer. Original report gives almost no information about the reason of the problem because backtrack contains no even function names related to ndis. If you are still interested in discovering this problem lets try to do this step by step. First lets use...