ndis0 does not associate since update to RELENG_6
I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network It worked fine with 5.4 and was recognised as ndis0: Intel(R) PRO/Wireless 2200BG Network Connection mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci ndis0: NDIS API version: 5.0 ndis0: Ethernet address: 00: ... :00 ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps On 6.0 it is still recognised, but the last two lines are missing. I'm using GENERIC, the driver module was generated with ndisgen out of w22n51.inf and w22n50.sys. This is the combination I alway used. ndis0 can scan for access points, but can't associate with or without WEP encryption. [EMAIL PROTECTED] ~ $ifconfig ndis0 list scan SSIDBSSID CHAN RATE S:N INT CAPS ec60bfg3b4 00: ... :a8 11 54M 149:0 100 EP ??? ??? ??? ??? ??? ??? WME [EMAIL PROTECTED] ~ $ifconfig ndis0 ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80: ... :7500%ndis0 prefixlen 64 scopeid 0x5 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid channel 1 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS I found a similar problem which should be fixed in current, but I don't know if the changes already hit stable. http://freebsd.rambler.ru/bsdmail/freebsd-current_2005/msg11802.html My problem is not exactly the same though, I have no trouble setting the bssid. Additionally I can't set the mode to 11g: [EMAIL PROTECTED] ~ #ifconfig ndis0 mode 11g ifconfig: SIOCSIFMEDIA (media): Invalid argument mode 11b is accepted but only leads to (DS/1Mbps). I can associate to the access point with ath0 and wi0 (at least for a short time). Is anybody else using this device with FreeBSD 6.0? Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: ndis0 does not associate since update to RELENG_6
Fabian Keil [EMAIL PROTECTED] wrote: I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network I found a work around. It still works with /usr/ports/net/iwi-firmware/: [EMAIL PROTECTED] ~ $ifconfig iwi0 iwi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 inet6 fe ... :7500%iwi0 prefixlen 64 scopeid 0x5 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (OFDM/48Mbps) status: associated ssid ec60bfg3b4 channel 11 bssid 00:...:a8 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS bintval 100 Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Fwd: wpa not working with ndis? [EMAIL PROTECTED]
Hey,
I have my laptop using ndis with a d-link dwl-g650+
i tested it using only nothing (means no wpa, no wep) - and this works
without problems.
now, i configured wpa_supplicant to use wpa - so:
on my 1st box, wpa_supplicant crashes the systems
on my 2nd box, wpa does not do anything.
i start it using 'wpa_supplicant -indis0 -c/etc/wpa.conf -Bw
this works on my linux box without any problem.
my wpa.conf is as follows:
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
network={
ssid=MyHome
scan_ssid=1
psk=MyVeryVeryVerySecretPassphraseYouNeverGuess:-D
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
Thanks for any help.
Roger
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 4.11 Stable 3ware AEN: twed0: degraded unit
This morning I received a message from my 3ware raid card and I wanted to know if there is a way to rebuild the raid with out having to reboot and use the 3ware bios. I know in Linux there is a way to view the software raid by using the proc. Is there something similar in Freebsd for hardware or will I have to reboot and use the 3ware bios? twe0: AEN: twed0: rebuild done twed0: drive timeouttwe0: AEN: twed0: degraded unit BTW, I'm going to replace the problem drive too I just wanted to know if I can access any of this via the Freebsd. Thanks for any assistance you offer. Hardware: 3ware 5800 8 port raid card. Here's some info from the dmesg: FreeBSD 4.11-STABLE FreeBSD 4.11-STABLE #0: Thu Dec 8 12:24:06 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 twe0: 3ware Storage Controller driver ver. 1.40.01.002 port 0xb400-0xb40f irq 10 at device 11.0 on pci0 twe0: 8 ports, Firmware V4.77 , BIOS V1.02.055 twed0: Unit 0, TwinStor, Rebuilding on twe0 twed0: 76318MB (156299440 sectors) twe0: AEN: twed0: rebuild done twed0: drive timeouttwe0: AEN: twed0: degraded unit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 4.11 Stable 3ware AEN: twed0: degraded unit
At 11:25 AM 17/01/2006, Eric Marquez wrote: This morning I received a message from my 3ware raid card and I wanted to know if there is a way to rebuild the raid with out having to reboot and use the 3ware bios. Hardware: 3ware 5800 8 port raid card. Here's some info from the dmesg: The 5xxx series are certainly not hot swappable so I am not sure how you could rebuild it with a new drive. If you think the problem drive is really ok, you could in the 3dmd program remove the bad drive, add it back, select the array and rebuild. However, not sure if the currently 3dmd program supports such an old controller. Really, your best bet is to do it in the BIOS. It will rebuild in the backupground ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0 does not associate since update to RELENG_6
in message [EMAIL PROTECTED], wrote Fabian Keil thusly... Fabian Keil [EMAIL PROTECTED] wrote: I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network I found a work around. It still works with /usr/ports/net/iwi-firmware/: I also found the same about ndis driver. I was not even able to assign a ssid, mode, or a channel to a ndis0 interface. At least net/iwi-firmware works w/ WPA (even if the interface causes freeze after waking up from long sleep on IBM Thinkpad T42; or after some time of good/stable connectivity, ping to Linksys WRT54G (router, running as a AP/switch) goes unanswered). BTW, when i read that you found a work around, i was expecting a work around to make ndis work. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 4.11 Stable 3ware AEN: twed0: degraded unit
Eric Marquez wrote: This morning I received a message from my 3ware raid card and I wanted to know if there is a way to rebuild the raid with out having to reboot and use the 3ware bios. I know in Linux there is a way to view the software raid by using the proc. Is there something similar in Freebsd for hardware or will I have to reboot and use the 3ware bios? The 3ware disk manager is in /usr/ports/sysutils/3dm including a web ui, etc. Not sure what it'll support on the older generation cards. On my 8506-4LP, it supports rebuild from inside FreeBSD Regards, Gary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
regression on aac driver from 5.4 to 6.0 (system locks up on boot)
I just posted a PR regarding a regression in the aac driver which locks up on a Dell PowerEdge 800 with the CERC SATA RAID card. Has anyone else had any luck with this system? http://www.freebsd.org/cgi/query-pr.cgi?pr=91910 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0 does not associate since update to RELENG_6
Parv [EMAIL PROTECTED] wrote: in message [EMAIL PROTECTED], wrote Fabian Keil thusly... Fabian Keil [EMAIL PROTECTED] wrote: I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network I found a work around. It still works with /usr/ports/net/iwi-firmware/: I also found the same about ndis driver. I was not even able to assign a ssid, mode, or a channel to a ndis0 interface. At least net/iwi-firmware works w/ WPA (even if the interface causes freeze after waking up from long sleep on IBM Thinkpad T42; Did you try to load and unload if_iwi.ko in /etc/rc.resume and /etc/rc.suspend? BTW, when i read that you found a work around, i was expecting a work around to make ndis work. I'm sorry for my misleading wording then. Of course it's just a work around to get the PRO/Wireless 2200BG working at all. It's just that I had forgotten about the existence of iwi. The last days I was using em0 to connect my Laptop to the network. Getting if_iwi to work after my initial posting was a relief. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: ndis0 does not associate since update to RELENG_6
I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network It worked fine with 5.4 and was recognised as ndis0: Intel(R) PRO/Wireless 2200BG Network Connection mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci ndis0: NDIS API version: 5.0 ndis0: Ethernet address: 00: ... :00 ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps On 6.0 it is still recognised, but the last two lines are missing. That's normal. I'm using GENERIC, the driver module was generated with ndisgen out of w22n51.inf and w22n50.sys. This is the combination I alway used. ndis0 can scan for access points, but can't associate with or without WEP encryption. What command do you type to try to get it to associate? [EMAIL PROTECTED] ~ $ifconfig ndis0 list scan SSIDBSSID CHAN RATE S:N INT CAPS ec60bfg3b4 00: ... :a8 11 54M 149:0 100 EP ??? ??? ??? ??? ??? ??? WME [EMAIL PROTECTED] ~ $ifconfig ndis0 ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80: ... :7500%ndis0 prefixlen 64 scopeid 0x5 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid channel 1 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS I found a similar problem which should be fixed in current, but I don't know if the changes already hit stable. http://freebsd.rambler.ru/bsdmail/freebsd-current_2005/msg11802.html My problem is not exactly the same though, I have no trouble setting the bssid. You should be able to do: # ifconfig ndis0 ssid ec60bfg3b4 wepmode on wepkey 0123456789123 up You don't state what command you actually use. You should have specified it in your e-mail. Note that usually the WEP key has to be either 5 or 13 characters. Additionally I can't set the mode to 11g: You don't have to do that. It'll associate with 11g automatically. Is anybody else using this device with FreeBSD 6.0? I've tested the 2200BG myself with the NDISulator 6.0 and I've been able to get it to associate with 11g networks. I don't know what's wrong in your case. -Bill -- = -Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu [EMAIL PROTECTED] | Wind River Systems = adamw you're just BEGGING to face the moose = ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0 does not associate since update to RELENG_6
Parv [EMAIL PROTECTED] wrote: in message [EMAIL PROTECTED], wrote Fabian Keil thusly... Fabian Keil [EMAIL PROTECTED] wrote: I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network I also found the same about ndis driver. I was not even able to assign a ssid, mode, or a channel to a ndis0 interface. I forgot to confirm that I can't assign ssid and channel as well. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Re: ndis0 does not associate since update to RELENG_6
in message [EMAIL PROTECTED], wrote Fabian Keil thusly... Parv [EMAIL PROTECTED] wrote: in message [EMAIL PROTECTED], wrote Fabian Keil thusly... Fabian Keil [EMAIL PROTECTED] wrote: I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network I found a work around. It still works with /usr/ports/net/iwi-firmware/: I also found the same about ndis driver. I was not even able to assign a ssid, mode, or a channel to a ndis0 interface. At least net/iwi-firmware works w/ WPA (even if the interface causes freeze after waking up from long sleep on IBM Thinkpad T42; Did you try to load and unload if_iwi.ko in /etc/rc.resume and /etc/rc.suspend? No, i hadn't; currently i am doing it manually when i am not sure about the length of the sleep state. I should look in to it, hunh.? BTW, when i read that you found a work around, i was expecting a work around to make ndis work. I'm sorry for my misleading wording then. Of course it's just a work around to get the PRO/Wireless 2200BG working at all. No problem. Actually, i myself am happy as long as there is some way to have a secure (semi-)stable wireless connection, on FreeBSD, w/ not-too-expensive hardware. It's just that I had forgotten about the existence of iwi. The last days I was using em0 to connect my Laptop to the network. Getting if_iwi to work after my initial posting was a relief. Same here, almost. I had not looked particularly hard in iwi or ndis -- but was aware of both -- until my sister's nagging broke me to buy a wireless AP/router. - Parv -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: System or file system panic on FreeBSD 5.x
Thats a simple answer your HD is failing purchase a new one backup and reinstall freebsd on new drive Looks like hardware - you could install the smartmontools port and check your disk to see. Thanks for your help, I shall try replacing ad1 in this weekend. Regards, pongthep ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0 does not associate since update to RELENG_6
[EMAIL PROTECTED] (Bill Paul) wrote: I fail to get the following device working since my update from RELENG_5 to RELENG_6 a few days ago: [EMAIL PROTECTED]:2:0: class=0x028000 card=0x27128086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class= network It worked fine with 5.4 and was recognised as ndis0: Intel(R) PRO/Wireless 2200BG Network Connection mem 0xc0214000-0xc0214fff irq 11 at device 2.0 on pci ndis0: NDIS API version: 5.0 ndis0: Ethernet address: 00: ... :00 ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps On 6.0 it is still recognised, but the last two lines are missing. That's normal. I'm using GENERIC, the driver module was generated with ndisgen out of w22n51.inf and w22n50.sys. This is the combination I alway used. ndis0 can scan for access points, but can't associate with or without WEP encryption. What command do you type to try to get it to associate? kldload wlan_wep.ko kldload w22n50_sys.ko ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ deftxkey 1 wepmode on ifconfig ndis0 inet 192.168.0.32 up [EMAIL PROTECTED] ~ $ifconfig ndis0 list scan SSIDBSSID CHAN RATE S:N INT CAPS ec60bfg3b4 00: ... :a8 11 54M 149:0 100 EP ??? ??? ??? ??? ??? ??? WME [EMAIL PROTECTED] ~ $ifconfig ndis0 ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 192.168.0.32 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80: ... :7500%ndis0 prefixlen 64 scopeid 0x5 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid channel 1 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpowmax 100 protmode CTS I found a similar problem which should be fixed in current, but I don't know if the changes already hit stable. http://freebsd.rambler.ru/bsdmail/freebsd-current_2005/msg11802.html My problem is not exactly the same though, I have no trouble setting the bssid. You should be able to do: # ifconfig ndis0 ssid ec60bfg3b4 wepmode on wepkey 0123456789123 up It was my experience that ifconfig on 6.0 will not chose the first key by default. I always have to add deftxkey 1. I can't use your exact command because I know my wepkey only in hexadecimal. But if I disable WEP in the access point and use ifconfig ndis0 ssid ec60bfg3b4 up it fails to associate (or even to set the ssid) as well: [EMAIL PROTECTED] ~ #ifconfig ndis0 ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe ... 7500%ndis0 prefixlen 64 scopeid 0x3 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid channel 1 authmode OPEN privacy OFF txpowmax 100 protmode CTS You don't state what command you actually use. You should have specified it in your e-mail. Note that usually the WEP key has to be either 5 or 13 characters. You're right, sorry. I use the hexadecimal notation and my key is correctly recognised as 104-bit. ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ deftxkey 1 wepmode on ifconfig ndis0 inet 192.168.0.32 up The two commands above work for iwi0, wi0 and ath0. I use the same shell script I used on 5.4. The only change I made was adding deftxkey 1 which wasn't needed before. Is anybody else using this device with FreeBSD 6.0? I've tested the 2200BG myself with the NDISulator 6.0 and I've been able to get it to associate with 11g networks. I don't know what's wrong in your case. Is there a way I can provide more information? Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
Creating a system RAID-10 device
I hope this is the appropriate mailing list for this question, if not please redirect me as needed. My goal is to create a filesystem consisting of a striped raid array over 3 mirror raid arrays that would encompass the entire filesystem including the /boot and root partitions. Generally I would create a RAID10 from 6 disks as follows: gmirror label -v -b round-robin md1 da0 da1 gmirror label -v -b round-robin md2 da2 da3 gmirror label -v -b round-robin md3 da4 da5 gstripe label -v -s 131072 md0 /dev/mirror/md1 /dev/mirror/md2 /dev/mirror/md3 newfs /dev/stripe/md0 naturally the problem here is that it cannot be done on a system that booted from da0. I have seen the example of setting up a mirrored system drive (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html ) which won't quite work for my case either. Using this method I could probably get the one mirror (md1) to work, but I know of no way of then adding the other 2 mirror sets and then redoing the system to stripe across all 3 mirrored sets. The only thing I could think of was to boot from the livecd and create the 6-disk array and then trying to install FreeBSD onto this filesystem. In order to do this the installer would have to recognize /dev/stripe/md0 as a valid drive -- is there any way to have this happen? Sven ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Creating a system RAID-10 device
On Tue, January 17, 2006 15:09, Sven Willenberger wrote: My goal is to create a filesystem consisting of a striped raid array over 3 mirror raid arrays that would encompass the entire filesystem including the /boot and root partitions. Check out: http://www.onlamp.com/pub/a/bsd/2005/11/10/FreeBSD_Basics.html I don't see why you couldn't modify Dru's instructions to build your array. -- Regards, Doug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Creating a system RAID-10 device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sven Willenberger wrote: I hope this is the appropriate mailing list for this question, if not please redirect me as needed. My goal is to create a filesystem consisting of a striped raid array over 3 mirror raid arrays that would encompass the entire filesystem including the /boot and root partitions. Generally I would create a RAID10 from 6 disks as follows: gmirror label -v -b round-robin md1 da0 da1 gmirror label -v -b round-robin md2 da2 da3 gmirror label -v -b round-robin md3 da4 da5 gstripe label -v -s 131072 md0 /dev/mirror/md1 /dev/mirror/md2 /dev/mirror/md3 newfs /dev/stripe/md0 naturally the problem here is that it cannot be done on a system that booted from da0. I have seen the example of setting up a mirrored system drive (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html ) which won't quite work for my case either. Using this method I could probably get the one mirror (md1) to work, but I know of no way of then adding the other 2 mirror sets and then redoing the system to stripe across all 3 mirrored sets. The only thing I could think of was to boot from the livecd and create the 6-disk array and then trying to install FreeBSD onto this filesystem. In order to do this the installer would have to recognize /dev/stripe/md0 as a valid drive -- is there any way to have this happen? Sven I've done this for a server in our office. I used four disks, and did the following : Split each disk on 2 parts, one about 60M for /boot, and the other part to the end of the disk. Then i created geom_mirror from the four 60M slices. (yah, mirror from 4 devices, it wastes a little space, but so what disks are cheap) and then with the big slices i created two geom_mirrors with 2 slices each, and then mirrored them. It looks something like this : [EMAIL PROTECTED] mount /dev/mirror/gm0 on /boot_mirror (ufs, local, noatime, synchronous) /dev/stripe/gs0a on / (ufs, local, noatime, with quotas, soft-updates) [EMAIL PROTECTED] gmirror status NameStatus Components mirror/gm0 COMPLETE da0s1a da1s1a da2s1a da3s1a mirror/gm1 COMPLETE da0s1d da1s1d mirror/gm2 COMPLETE da2s1d da3s1d [EMAIL PROTECTED] gstripe status Name Status Components stripe/gs0 UP mirror/gm1 mirror/gm2 [EMAIL PROTECTED] [EMAIL PROTECTED] cat /boot/loader.conf geom_mirror_load=YES geom_stripe_load=YES vfs.root.mountfrom=ufs:/dev/stripe/gs0a [EMAIL PROTECTED] ls -lad /boot* lrwxr-xr-x 1 root wheel 16 Jun 25 2005 /boot - boot_mirror/boot drwxr-xr-x 4 root wheel 512 Jun 25 2005 /boot_mirror Then i can boot a RAID-10 software array with GEOM on FreeBSD and also have the added bonus that i can boot from any of the four disks if any fails. (well, i guess i still will have to chose other disk for boot from the scsi bios) Regards, - --niki -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDzXC+HNAJ/fLbfrkRAlKyAJ9bhXwCQe2ZuLI6KL32yRGWCrnhsACfVSrM TkQzpNM4UVy9V0OSNAk9RLY= =NNNa -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
fxp0: device timeout and sk0: watchdog timeout problems
Hi, I'm having problem with sk and fxp NIC. I get fxp0: device timeout and sk0: watchdog timeout problems and network stops responding. gw# uname -an FreeBSD xx.xx.xx 6.0-STABLE FreeBSD 6.0-STABLE #2: Mon Jan 16 12:09:59 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GATEWAY i386 Message log: Jan 17 18:15:22 gw kernel: fxp0: device timeout Jan 17 18:15:25 gw kernel: sk0: watchdog timeout Jan 17 18:15:25 gw kernel: sk0: link state changed to DOWN Jan 17 18:15:41 gw kernel: sk0: watchdog timeout Jan 17 18:15:53 gw kernel: fxp0: device timeout Jan 17 18:16:29 gw kernel: fxp0: device timeout Jan 17 18:17:07 gw kernel: fxp0: device timeout Jan 17 18:17:19 gw kernel: sk0: watchdog timeout Jan 17 18:17:42 gw kernel: fxp0: device timeout Jan 17 18:17:59 gw kernel: sk0: watchdog timeout Jan 17 18:18:19 gw kernel: sk0: watchdog timeout Jan 17 18:18:53 gw kernel: sk0: watchdog timeout pciconf -lv output: [EMAIL PROTECTED]:1:0: class=0x02 card=0x4c001186 chip=0x4c001186 rev=0x11 hdr=0x00 vendor = 'D-Link System Inc' device = 'DGE-530T Gigabit Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:2:0: class=0x02 card=0x01f11014 chip=0x12298086 rev=0x0c hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class= network subclass = ethernet dmesg.boot: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-STABLE #2: Mon Jan 16 12:09:59 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GATEWAY ACPI APIC Table: IBMSERMOHIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (548.54-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 536854528 (511 MB) avail memory = 515850240 (491 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: IBM SERMOHIC on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xfe88-0xfe8b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 skc0: D-Link DGE-530T Gigabit Ethernet port 0x2000-0x20ff mem 0xfebfc000-0xfebf irq 18 at device 1.0 on pci0 skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x1) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:11:95:e1:7d:16 miibus0: MII bus on sk0 e1000phy0: Marvell 88E1000 Gigabit PHY on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto ahc0: Adaptec aic7895 Ultra SCSI adapter port 0x2200-0x22ff mem 0xfebfb000-0xfebfbfff irq 16 at device 6.0 on pci0 ahc1: [GIANT-LOCKED] aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/253 SCBs pci0: display, VGA at device 10.0 (no driver attached) isab0: PCI-ISA bridge port 0xfe00-0xfe0f at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: GENERIC ATA controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 18 at device 15.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 ohci0: OHCI (generic) USB controller mem 0xff70-0xff700fff irq 18 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib1: ACPI Host-PCI bridge on acpi0 pci1: ACPI PCI bus on pcib1 fxp0: Intel 82550 Pro/100 Ethernet port 0x4b00-0x4b3f mem 0xc0fdf000-0xc0fd,0xc0fa-0xc0fb irq 19 at device 2.0 o n pci1 miibus1: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:03:47:e0:64:3c atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Standard parallel printer port port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: Parallel port bus on ppc0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0
hptmv, Verify a raid5 array panics
Verifying a raid5 array from High-Points CLI results in a panic. It has always from the beginning of the driver behaved like this. I dare what happens if a disk fail and I need a rebuild. Did the authors verify these vital functions? Does other have the same problem? I have waited out the maturing of the driver without success. I have tried to ask Highpoint about this also, but I only get stupid from the support questions about the latest bios, which I have etc. After answering I get the usual when the support does not care/wait until the problem solves when the client are tierd enough and forgets silence. Before I submit dumps etc I want to know if any one else has experienced the same problems. B.R. A tired Kenneth Home server with my modest needs and also serving (for free) counter-strike with some web services: (writing this to prevent answerslike ; Why don't you get an expensive Areca card instead?) (and I have you tried Vinum/Gvinum before?)* Iwill DH800 2* Xeon 2.4GHz High-Point (low-crap?) 1820a 4*Maxtor 200G *Lukas Ertl did get some dumps about this a year ago. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout and sk0: watchdog timeout problems
On Wed, Jan 18, 2006 at 09:27:09AM +0800, Ganbold wrote: Hi, I'm having problem with sk and fxp NIC. I get fxp0: device timeout and sk0: watchdog timeout problems and network stops responding. gw# uname -an FreeBSD xx.xx.xx 6.0-STABLE FreeBSD 6.0-STABLE #2: Mon Jan 16 12:09:59 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GATEWAY i386 Message log: Jan 17 18:15:22 gw kernel: fxp0: device timeout Jan 17 18:15:25 gw kernel: sk0: watchdog timeout Jan 17 18:15:25 gw kernel: sk0: link state changed to DOWN Jan 17 18:15:41 gw kernel: sk0: watchdog timeout Jan 17 18:15:53 gw kernel: fxp0: device timeout Jan 17 18:16:29 gw kernel: fxp0: device timeout Jan 17 18:17:07 gw kernel: fxp0: device timeout Jan 17 18:17:19 gw kernel: sk0: watchdog timeout Jan 17 18:17:42 gw kernel: fxp0: device timeout Jan 17 18:17:59 gw kernel: sk0: watchdog timeout Jan 17 18:18:19 gw kernel: sk0: watchdog timeout Jan 17 18:18:53 gw kernel: sk0: watchdog timeout pciconf -lv output: [EMAIL PROTECTED]:1:0: class=0x02 card=0x4c001186 chip=0x4c001186 rev=0x11 hdr=0x00 vendor = 'D-Link System Inc' device = 'DGE-530T Gigabit Ethernet Adapter' class= network subclass = ethernet [EMAIL PROTECTED]:2:0: class=0x02 card=0x01f11014 chip=0x12298086 rev=0x0c hdr=0x00 vendor = 'Intel Corporation' device = '82550/1/7/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class= network subclass = ethernet dmesg.boot: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-STABLE #2: Mon Jan 16 12:09:59 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GATEWAY ACPI APIC Table: IBMSERMOHIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (548.54-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 536854528 (511 MB) avail memory = 515850240 (491 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: IBM SERMOHIC on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xfe88-0xfe8b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 skc0: D-Link DGE-530T Gigabit Ethernet port 0x2000-0x20ff mem 0xfebfc000-0xfebf irq 18 at device 1.0 on pci0 skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x1) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:11:95:e1:7d:16 miibus0: MII bus on sk0 e1000phy0: Marvell 88E1000 Gigabit PHY on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto ahc0: Adaptec aic7895 Ultra SCSI adapter port 0x2200-0x22ff mem 0xfebfb000-0xfebfbfff irq 16 at device 6.0 on pci0 ahc1: [GIANT-LOCKED] aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/253 SCBs pci0: display, VGA at device 10.0 (no driver attached) isab0: PCI-ISA bridge port 0xfe00-0xfe0f at device 15.0 on pci0 isa0: ISA bus on isab0 atapci0: GENERIC ATA controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 18 at device 15.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 ohci0: OHCI (generic) USB controller mem 0xff70-0xff700fff irq 18 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib1: ACPI Host-PCI bridge on acpi0 pci1: ACPI PCI bus on pcib1 fxp0: Intel 82550 Pro/100 Ethernet port 0x4b00-0x4b3f mem 0xc0fdf000-0xc0fd,0xc0fa-0xc0fb irq 19 at device 2.0 o n pci1 miibus1: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:03:47:e0:64:3c atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: Standard parallel printer port
Re: hptmv, Verify a raid5 array panics
Their support is useless and I will never use their cards again we have multiple 5 * 400GB disk arrays on 1820a's and they all fail when doing rsync's dropping one disk then a second crashing the box. Online rebuild crashes the machine, offline ( BIOS ) works. The performance is good but of no consequence if normal usage is not possible. I've looked though the code and can find no obvious issues the machine always panics after multiple drives have been dropped as though a drive is failing but full diagnostics have been performed and there are no issues,always seems to be drive 4 which is dropped first here, even when the disks are swapped round. I suspect a firmware or hardware issue under high load / queue length which results in an DMA timeout type error. Highpoint support raised it with their engineering department but I've never heard anything back even after months and many calls to their main support line in the US from the UK i.e. they binned the problem. Very disappointed and I'll never use their devices again. Steve - Original Message - From: Kenneth [EMAIL PROTECTED] To: freebsd-stable@freebsd.org Sent: Wednesday, January 18, 2006 1:53 AM Subject: hptmv, Verify a raid5 array panics Verifying a raid5 array from High-Points CLI results in a panic. It has always from the beginning of the driver behaved like this. I dare what happens if a disk fail and I need a rebuild. Did the authors verify these vital functions? Does other have the same problem? I have waited out the maturing of the driver without success. I have tried to ask Highpoint about this also, but I only get stupid from the support questions about the latest bios, which I have etc. After answering I get the usual when the support does not care/wait until the problem solves when the client are tierd enough and forgets silence. Before I submit dumps etc I want to know if any one else has experienced the same problems. B.R. A tired Kenneth Home server with my modest needs and also serving (for free) counter-strike with some web services: (writing this to prevent answerslike ; Why don't you get an expensive Areca card instead?) (and I have you tried Vinum/Gvinum before?)* Iwill DH800 2* Xeon 2.4GHz High-Point (low-crap?) 1820a 4*Maxtor 200G *Lukas Ertl did get some dumps about this a year ago. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout and sk0: watchdog timeout problems
At 09:55 AM 1/18/2006, you wrote: inet 127.0.0.1 netmask 0xff00 I used new if_sk codes from Pyun YongHyeon but after 2 days I got same problem device timeout. fxp is also timing out and I don't know why. Any idea? If sk(4) is the cause of problem fxp wouldn't be affected. I guess so. But fxp also times out almost at same time as sk does. Of course it's possible for sk(4) to corrupt kernel memory structure but the possibility is low. While fixing sk(4) I pushed sk(4) to the limit on sparc64. I never met such timeouts. atm I have no clue. How about updated sk(4)? http://people.freebsd.org/~yongari/sk/if_sk.c http://people.freebsd.org/~yongari/sk/if_skreg.h Is it new update? Because I used your update dated on Jan 12 2006. Is it newer than that? Disabling sk(4) remedy your issue? There is another on-board pcn NIC, I will try if problem exists with sk driver. Ganbold. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fxp0: device timeout and sk0: watchdog timeout problems
On Wed, Jan 18, 2006 at 10:28:43AM +0800, Ganbold wrote: At 09:55 AM 1/18/2006, you wrote: inet 127.0.0.1 netmask 0xff00 I used new if_sk codes from Pyun YongHyeon but after 2 days I got same problem device timeout. fxp is also timing out and I don't know why. Any idea? If sk(4) is the cause of problem fxp wouldn't be affected. I guess so. But fxp also times out almost at same time as sk does. Of course it's possible for sk(4) to corrupt kernel memory structure but the possibility is low. While fixing sk(4) I pushed sk(4) to the limit on sparc64. I never met such timeouts. atm I have no clue. How about updated sk(4)? http://people.freebsd.org/~yongari/sk/if_sk.c http://people.freebsd.org/~yongari/sk/if_skreg.h Is it new update? Because I used your update dated on Jan 12 2006. Is it newer than that? Yes. Disabling sk(4) remedy your issue? There is another on-board pcn NIC, I will try if problem exists with sk driver. Ok. Thank you. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SUMMARY: Fast releases demand binary updates..
On Thu, 12 Jan 2006 00:08:56 -0800, Jo Rhett [EMAIL PROTECTED] said: 12 or so honest queries on the mailing list about why make buildworld or the freebsd-update mechanism doesn't work for me. Which I try to answer in detail, even when the questioner was insulting me. Why doesn't make buildworld work for you? I find myself replacing binary packages with source more often than not, to effect a better tracking with cvs. I'm guessing, but it sounds like you're after some sort of replacement to the cvs approach in binary form. Right? -- Aluminium Oxide [EMAIL PROTECTED] -- http://www.fastmail.fm - One of many happy users: http://www.fastmail.fm/docs/quotes.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ndis0 does not associate since update to RELENG_6
What command do you type to try to get it to associate? kldload wlan_wep.ko kldload w22n50_sys.ko ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ deftxkey 1 wepmode on ifconfig ndis0 inet 192.168.0.32 up [...] It was my experience that ifconfig on 6.0 will not chose the first key by default. I always have to add deftxkey 1. I can't use your exact command because I know my wepkey only in hexadecimal. But if I disable WEP in the access point and use ifconfig ndis0 ssid ec60bfg3b4 up it fails to associate (or even to set the ssid) as well: [EMAIL PROTECTED] ~ #ifconfig ndis0 ndis0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet6 fe ... 7500%ndis0 prefixlen 64 scopeid 0x3 ether 00: ... :00 media: IEEE 802.11 Wireless Ethernet autoselect status: no carrier ssid channel 1 authmode OPEN privacy OFF txpowmax 100 protmode CTS You don't state what command you actually use. You should have specified it in your e-mail. Note that usually the WEP key has to be either 5 or 13 characters. You're right, sorry. I use the hexadecimal notation and my key is correctly recognised as 104-bit. ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0xhexkey \ deftxkey 1 wepmode on ifconfig ndis0 inet 192.168.0.32 up The two commands above work for iwi0, wi0 and ath0. I use the same shell script I used on 5.4. The only change I made was adding deftxkey 1 which wasn't needed before. Is anybody else using this device with FreeBSD 6.0? I've tested the 2200BG myself with the NDISulator 6.0 and I've been able to get it to associate with 11g networks. I don't know what's wrong in your case. Is there a way I can provide more information? You haven't said yet what manufacturer/model your access point is. You also haven't said what Windows driver version you're using, but you need to cheat a bit to figure that out. I usually do: % strings -e l foo.sys or % strings -e l foo_sys.ko Near the end of the output, there should be a bunch of version information, including the vendor name of whoever built the driver (in this case Intel). You might try downloading the latest driver from Intel. (They have a generic one for their Centrino wireless devices.) You also haven't said what sort of laptop this is. Wouldn't hurt to know that either. Unfortunately, this is the sort of thing that can only be debugged with the system sitting in front of me. I can't do it by remote control, and I can't know exactly what information to ask you. I have to experiment, and I can't do that from here. You should turn WEP off completely, make sure the AP is set for open authentication mode, and try getting it to authenticate without WEP first. It's one less variable to worry about. Try using the following: # ifconfig ndis0 ssid up # ifconfig ndis0 ssid yourssid bssid BSSID of your AP up Don't fiddle with the channel setting. Windows drivers don't let you set the channel unless you're in ad-hoc mode. (Some drivers erroneously process channel selectin requests in infrastructure mode too, but the results can be unpredictable.) -Bill -- = -Bill Paul(510) 749-2329 | Senior Engineer, Master of Unix-Fu [EMAIL PROTECTED] | Wind River Systems = adamw you're just BEGGING to face the moose = ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
