Re: ndis no longer detects netgear wg311v2
I am reminded of Fri, Jul 01, 2005 at 03:53:59PM +0200 when [EMAIL PROTECTED] said: > On 1 Jul, Phil Bowens wrote: > > FWIW, I am having the *exact* same problem starting today. I hadn't > > updated my STABLE machine since April. NDIS was working fine (save a > > frew crashes) before I updated last night.. and now NDIS will not even > > talk about the card. There is also a slight freeze on the machine > > after the if_ndis module is loaded. > > > > I will do some more investigating, but now there's at least two of us. > > Did you ever find a fix? > > > > I had a similar problem with a recent system update two days ago. > I noticed that the if_ndis.ko was half smaller and there was not any > reference to my NIC anymore. > After a few search I noticed that ndisgen is a tool able to generate a > specific loadable module based on .inf and .sys. > So I used ndisgen, copied the generated ko to /boot/kernel and manually > kldload it : my NIC was back. > > Unfortunately, I haven't been able to find a good resource about the > correct procedure to generate the module but I have a bigger problem > than this one at the moment :( > > Hope that helps. > > Phil. Okay, so if you take a look at cvsweb, you'll find some information in a commit message somewhere. I'm not going to make you look for it, don't worry. The procedure for creating the kernel module has changed. For some reason this never made it to updating, and appears to only be documented in the commit message. The commit message references ndisgen(8). It could have been some other number, but it doesn't matter because the man page doesn't exist anywhere anyway. Luckily, ndisgen is basically self-documenting. You just run it, maybe choose to read the explanation text, and choose the option to create the kernel module. It will prompt you for your sys and inf files, along with any firmware files you might need. You should be warned though, that you'll want to have the paths to your files available because there's no file browser functionality and if you suspend ndisgen while you look up the path, ^L won't redraw the screen. It would be handy to have a non-interactive version again, but oh well. -- Evan Dower Software Development Engineer Amazon.com, Inc. Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ndis no longer detects netgear wg311v2
I recently moved, and for some reason my computer started crashing when I tried to make it associate with my new wireless network. (It worked fine on the old wireless network.) I figured the first thing I should do to fix the problem is update my sources, since it may have already been fixed. Unfortunately the updated sources don't recognize my wireless card at all. Before the update (hand-transcribed): # uname -a FreeBSD lojak.washington.edu 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Sat Apr 2 11:50:53 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM i386 # kldload FwRad16.bin.ko # kldload ndis # kldload if_ndis ndis0: mem 0xfb02-0xfb03,0xfb04-0xfb041fff irq 16 at device 4.0 on pci2 ndis0: NDIS API version: 5.1 ndis0: Ethernet address: 00:09:5b:ba:da:ef ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps # ifconfig ndis0 ndis0: flags=8802 mtu 1500 ether 00:09:5b:da:ef media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid "" channel -1 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode OFF weptxkey 1 # wicontrol ndis0 -l 0 stations: # ifconfig ndis0 ssid "The Penthouse" channel 11 up ndis0: link up # dhclient ndis0 ndis0: link up <<< I can't see the whole panic screen, but here's the bottom: >>> panic: page fault cpuid = 0 boot() called on cpu#0 Uptime: 11m20s Dumping 1023 MB Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address= 0x0 fault code = supervisor read, page not present intruction pointer = 0x8:0x0 stack pointer= 0x10:0xe4e1fcec frame pointer= 0x10:0xe4e1fd0c code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 5 (thread taskq) trap number = 12 I can work on getting the crash dump if that's useful, but the behavior seems to have changed in the last couple of months. Now I get: # uname -a FreeBSD lojak.washington.edu 5.4-STABLE FreeBSD 5.4-STABLE #0: Sat Jun 14:20:40 PDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM i386 # kldload FwRad16.bin.ko # kldload ndis warning: KLD '/boot/kernel/if_ndis.ko' is newer than the linker.hints file # kldload if_ndis kldload: can't load if_ndis: File exists # kldstat Id Refs AddressSize Name 1 10 0xc040 4a42f0 kernel 2 14 0xc08a5000 56270acpi.ko 31 0xc2e83000 14000FwRad16.bin.ko 41 0xc2e97000 9000 if_ndis.ko 51 0xc2ea 12000ndis.ko 61 0xc2ec5000 b000 pccard.ko # ifconfig ndis0 ifconfig: interface ndis0 does not exist # kldunload if_ndis # kldload if_ndis # ifconfig ndis0 ifconfig: interface ndis0 does not exist I haven't seen anything in UPDATING that accounts for this. Does anyone have any idea of where to look for clues? Thanks very much, -- Evan Dower Software Development Engineer Amazon.com, Inc. Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSHD and FTPD, can't connect
I am reminded of Mon, Jun 06, 2005 at 06:40:23PM -0400 when Lowell Gilbert said: > Please don't top-post. > > "Matt Smith" <[EMAIL PROTECTED]> writes: > > > Where is the sshd debugger? > > There are a couple of ways to get extra logging information out of > it. See the "LogLevel" option in the manual for sshd_config(5) or the > "-d" option in the manual for sshd(8). > And don't forget the -v (or -vv or -vvv) option to ssh. Even that could be helpful. -- Evan Dower Undergraduate, Computer Science University of Washington Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Recent NDIS Panics Appear To Be Solved
I recently experienced panics with dhclient ndis0 (ndis swi), and I saw that others had noticed similar problems. There is a PR or two about it at the moment. CVSUPping today solved the problem for me. So for those who had the problems, you may find them solved now. Ciao, -- Evan Dower Undergraduate, Computer Science University of Washington Public key: http://students.washington.edu/evantd/pgp-pub-key.txt Key fingerprint = D321 FA24 4BDA F82D 53A9 5B27 7D15 5A4F 033F 887D ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
