From guru at unixarea.de Sun Mar 1 08:13:16 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sun Mar 1 08:13:28 2009 Subject: wpa_supplicant && associates to unknown AP Message-ID: <20090301080310.GA3186@rebelion.Sisis.de> Hello, This lonely Sunday morning I've switched on my laptop at home and while it was booting I went to breakfast; coming back I found that I could not connect to Internet because it associated to a unknown foreign AP in my area (ssid ALICE-WLAN). I'm running wpa_supplicant and of course this is not in my /etc/wpa_supplicant.conf file. My AP is ssid tarara and the entry in wpa_supplicant.conf is: network={ ssid="tarara" scan_ssid=0 key_mgmt=NONE wep_tx_keyidx=0 wep_key0=xxxxxxxxxxxxxxxxxxx } I killed the wpa_supplicant and restarted it, see below the ifconfig output, and it then associated fine to my AP. How is this possible? And what can I do to prevent this? Thx # ifconfig iwi0 iwi0: flags=8843 metric 0 mtu 1500 ether 00:13:ce:a1:e6:81 inet 192.168.2.3 netmask 0xffffff00 broadcast 192.168.2.255 media: IEEE 802.11 Wireless Ethernet autoselect status: associated ssid ALICE-WLAN channel 11 (2462 Mhz 11g) bssid 00:1b:9e:ff:61:0b authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode CTS roaming MANUAL (killing wpa_supplicant) # ifconfig iwi0 iwi0: flags=8843 metric 0 mtu 1500 ether 00:13:ce:a1:e6:81 inet 192.168.2.3 netmask 0xffffff00 broadcast 192.168.2.255 media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps) status: associated ssid tarara channel 7 (2442 Mhz 11g) bssid 00:13:f7:0d:08:48 authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 roam:rate11g 5 protmode CTS roaming MANUAL # ifconfig iwi0 list scan SSID BSSID CHAN RATE S:N INT CAPS ALICE-WLAN 00:1b:9e:ff:61:0b 11 54M 18:0 100 EP tarara 00:13:f7:0d:08:48 7 54M 39:0 100 EPS -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ From sam at freebsd.org Sun Mar 1 09:44:06 2009 From: sam at freebsd.org (Sam Leffler) Date: Sun Mar 1 09:44:12 2009 Subject: wpa_supplicant && associates to unknown AP In-Reply-To: <20090301080310.GA3186@rebelion.Sisis.de> References: <20090301080310.GA3186@rebelion.Sisis.de> Message-ID: <49AAC965.1030903@freebsd.org> Matthias Apitz wrote: > Hello, > > This lonely Sunday morning I've switched on my laptop at home and while > it was booting I went to breakfast; coming back I found that I could not > connect to Internet because it associated to a unknown foreign AP in my > area (ssid ALICE-WLAN). I'm running wpa_supplicant and of course > this is not in my /etc/wpa_supplicant.conf file. My AP is ssid tarara > and the entry in wpa_supplicant.conf is: > > network={ > ssid="tarara" > scan_ssid=0 > key_mgmt=NONE > wep_tx_keyidx=0 > wep_key0=xxxxxxxxxxxxxxxxxxx > } > > I killed the wpa_supplicant and restarted it, see below the ifconfig > output, and it then associated fine to my AP. How is this possible? > And what can I do to prevent this? > Thx > > > # ifconfig iwi0 > iwi0: flags=8843 metric 0 mtu 1500 > ether 00:13:ce:a1:e6:81 > inet 192.168.2.3 netmask 0xffffff00 broadcast 192.168.2.255 > media: IEEE 802.11 Wireless Ethernet autoselect > status: associated > ssid ALICE-WLAN channel 11 (2462 Mhz 11g) bssid 00:1b:9e:ff:61:0b > authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit bmiss 10 > scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 > roam:rate11g 5 protmode CTS roaming MANUAL > > (killing wpa_supplicant) > > # ifconfig iwi0 > iwi0: flags=8843 metric 0 mtu 1500 > ether 00:13:ce:a1:e6:81 > inet 192.168.2.3 netmask 0xffffff00 broadcast 192.168.2.255 > media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps) > status: associated > ssid tarara channel 7 (2442 Mhz 11g) bssid 00:13:f7:0d:08:48 > authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit bmiss 10 > scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11g 7 > roam:rate11g 5 protmode CTS roaming MANUAL > > # ifconfig iwi0 list scan > SSID BSSID CHAN RATE S:N INT CAPS > ALICE-WLAN 00:1b:9e:ff:61:0b 11 54M 18:0 100 EP > tarara 00:13:f7:0d:08:48 7 54M 39:0 100 EPS > > I don't see a wpa_supplicant log. The way iwi works is rather a hack but necessitated by the crappy intel firmware. There is no way to get iwi to just scan but not associate so what's done is we install an "impossible ssid" when we just want to scan then fill in the ssid and tell it to scan on just the channel where the desired ap is located. This has always worked but perhaps you caught ifconfig reporting status that was temporary. Without logs it's impossible to tell. The other possibillity is your wpa_supplicant.conf file allowed association to a "wildcard ap". Can't tell w/o seeing the config file and/or log. Sam From guru at unixarea.de Mon Mar 2 00:02:32 2009 From: guru at unixarea.de (Matthias Apitz) Date: Mon Mar 2 00:02:39 2009 Subject: wpa_supplicant && associates to unknown AP In-Reply-To: <49AAC965.1030903@freebsd.org> References: <20090301080310.GA3186@rebelion.Sisis.de> <49AAC965.1030903@freebsd.org> Message-ID: <20090302080228.GA1989@rebelion.Sisis.de> El d?a Sunday, March 01, 2009 a las 09:44:05AM -0800, Sam Leffler escribi?: > I don't see a wpa_supplicant log. The way iwi works is rather a hack > but necessitated by the crappy intel firmware. There is no way to get > iwi to just scan but not associate so what's done is we install an > "impossible ssid" when we just want to scan then fill in the ssid and > tell it to scan on just the channel where the desired ap is located. > This has always worked but perhaps you caught ifconfig reporting status > that was temporary. Without logs it's impossible to tell. I will try to collect a wpa_supplicant log; this is a bit tricky because wpa_supplicant is launched at boot time with hardcoded flags in /etc/rc.d/wpa_supplicant and it seems it does not log via syslog (at least I don't see how this could be enabled in the man page); > The other possibillity is your wpa_supplicant.conf file allowed > association to a "wildcard ap". Can't tell w/o seeing the config file > and/or log. No, there is no "wildcard ap". Thx for your reply in any case. matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ From sam at freebsd.org Mon Mar 2 08:05:49 2009 From: sam at freebsd.org (Sam Leffler) Date: Mon Mar 2 08:05:58 2009 Subject: wpa_supplicant && associates to unknown AP In-Reply-To: <20090302080228.GA1989@rebelion.Sisis.de> References: <20090301080310.GA3186@rebelion.Sisis.de> <49AAC965.1030903@freebsd.org> <20090302080228.GA1989@rebelion.Sisis.de> Message-ID: <49AC03DB.3090608@freebsd.org> Matthias Apitz wrote: > El d?a Sunday, March 01, 2009 a las 09:44:05AM -0800, Sam Leffler escribi?: > > >> I don't see a wpa_supplicant log. The way iwi works is rather a hack >> but necessitated by the crappy intel firmware. There is no way to get >> iwi to just scan but not associate so what's done is we install an >> "impossible ssid" when we just want to scan then fill in the ssid and >> tell it to scan on just the channel where the desired ap is located. >> This has always worked but perhaps you caught ifconfig reporting status >> that was temporary. Without logs it's impossible to tell. >> > > I will try to collect a wpa_supplicant log; this is a bit tricky because > wpa_supplicant is launched at boot time with hardcoded flags in > /etc/rc.d/wpa_supplicant and it seems it does not log via syslog (at > least I don't see how this could be enabled in the man page); > The no logging is because syslogd is started too late by rc.d. I've brought this up (the ordering is complicated) but haven't had time to fix it myself. To add -d you should be able to just add wpa_supplicant_flags="-s -d" in rc.conf. This will work if you manually start things with /etc/rc.d/netif start ath0 (or similar). > >> The other possibillity is your wpa_supplicant.conf file allowed >> association to a "wildcard ap". Can't tell w/o seeing the config file >> and/or log. >> > > No, there is no "wildcard ap". > > Thx for your reply in any case. > > matthias > > From bees571wax at fastmail.fm Tue Mar 3 17:46:33 2009 From: bees571wax at fastmail.fm (bees571wax@fastmail.fm) Date: Tue Mar 3 17:46:39 2009 Subject: Version of; Difficulty with Presario Compaq Message-ID: <1236129985.20773.1303491585@webmail.messagingengine.com> I have an old laptop I'd like to try FreeBSD on. It is a Compaq Presario 1610 with 80MB Ram and a 1.5GB HD. Can anyone advise me what version of FreeBSD I should try and how many problems I will run into? I looked briefly at In particular I am concerned with: a)continuning to use a yahoo chat client with a little mini cam with drivers that I have only tried on windows 98SE, or I could use any cam with any yahoo compatible chat client as second preference. b) any problems with Tor c) secure web browsers that will run under FreeBSD on this hardware d) cd drivers for this laptop e) any other driver problems either as to obtaining or operation. f) possible use of wireshark g) compatiblity and drivers for a wifi pcmcia card senao knockoff prism 2.5 chipset h) any other problems, especially would like to hear from those that have tried it on this laptop. Also what is the minimum HD space requirements, ram, etc for FreeBSD with the above applications in mind? Thanks for any helpful info. -- bees571wax@fastmail.fm -- http://www.fastmail.fm - IMAP accessible web-mail From guru at unixarea.de Thu Mar 5 04:00:25 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu Mar 5 04:00:32 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP Message-ID: <20090305120022.GA8012@rebelion.Sisis.de> Hello, I'm going frequently to a Greek restaurant in my town to have dinner there or some red wine, and reading stuff; the owner of the restaurant has a Wifi zone and gave me, as its best client, the WEP-key to connect to Internet; the problem is that he does not have the admin password of the AP (some else configured it) and so I can't have a look into the config of the AP; my /etc/wpa_supplicant.conf for the AP is: # Restaurante Odyssey (2007-11-18) # network={ ssid="ConnectionPoint" scan_ssid=0 key_mgmt=NONE wep_tx_keyidx=0 wep_key0=xxxxxxxxxxxxxxxxxxxxxx } and the interface associates fine: # ifconfig ath0 ath0: flags=8843 metric 0 mtu 1500 ether 00:15:af:b2:ae:e6 inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) status: associated ssid ConnectionPoint channel 11 (2462 Mhz 11g) bssid 00:01:e3:0e:97:99 authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpower 31.5 bmiss 7 scanvalid 60 protmode CTS burst roaming MANUAL but a DHCP request does not give me any IP addr; with # tcpdump -n -i ath0 it says: 19:01:01.603869 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:af:b2:ae:e6, length 300 19:01:02.036549 00:01:e3:0e:97:98 Unknown SSAP 0x2c > ff:ff:ff:ff:ff:ff Unknown DSAP 0xa2 Information, send seq 98, rcv seq 39, Flags [Command], length 36 19:01:02.958057 00:01:e3:0e:97:98 ProWay NM > ff:ff:ff:ff:ff:ff Unknown DSAP 0x5c Supervisory, Reject, rcv seq 8, Flags [Response], length 36 19:01:04.186892 00:01:e3:0e:97:98 Unknown SSAP 0xbe > ff:ff:ff:ff:ff:ff Unknown DSAP 0x44 Supervisory, Reject, rcv seq 39, Flags [Final], length 36 19:01:09.606218 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:af:b2:ae:e6, length 300 this situation is already for monthes and I gave up and always use UMTS if I want connect to Internet; until yesterday I was thinking in some kind of MAC addr filter in the AP, but .... yesterday I was there with a friend who has a Nokia mobile E51 device; I gave him the key, he associated like me and got in the next second IP, DNS and all was fine; what is that for a problem? it is not ath0 related because my other laptop with iwi0 does not get IP either; what can I provide as information to nail this down? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ From mobile at freebsd.org Thu Mar 5 13:03:15 2009 From: mobile at freebsd.org (mobile@freebsd.org) Date: Thu Mar 5 13:03:22 2009 Subject: You have a virtual card waiting for you! Message-ID: <200903052019.n25KJjCr074253@downeasthost.com> Hi, jonnik1 stopped by my site, Acadia Images and created a Virtual Card just for you! To pick up your card, simply point your browser at the page listed below. http://www.acadiaimages.com/postcard/mar5-2843874252.html The card will remain on the server for about one week, so please print it out or save it as soon as you can. From sam at freebsd.org Fri Mar 6 16:10:27 2009 From: sam at freebsd.org (Sam Leffler) Date: Fri Mar 6 16:10:34 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <20090305120022.GA8012@rebelion.Sisis.de> References: <20090305120022.GA8012@rebelion.Sisis.de> Message-ID: <49B1BB71.6060000@freebsd.org> Matthias Apitz wrote: > Hello, > > I'm going frequently to a Greek restaurant in my town to have dinner > there or some red wine, and reading stuff; > > the owner of the restaurant has a Wifi zone and gave me, as its best > client, the WEP-key to connect to Internet; the problem is that he does > not have the admin password of the AP (some else configured it) and so I > can't have a look into the config of the AP; > > my /etc/wpa_supplicant.conf for the AP is: > > # Restaurante Odyssey (2007-11-18) > # > network={ > ssid="ConnectionPoint" > scan_ssid=0 > key_mgmt=NONE > wep_tx_keyidx=0 > wep_key0=xxxxxxxxxxxxxxxxxxxxxx > } > > and the interface associates fine: > > # ifconfig ath0 > ath0: flags=8843 metric 0 mtu 1500 > ether 00:15:af:b2:ae:e6 > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) > status: associated > ssid ConnectionPoint channel 11 (2462 Mhz 11g) bssid 00:01:e3:0e:97:99 > authmode OPEN privacy ON deftxkey 1 wepkey 1:104-bit txpower 31.5 > bmiss 7 scanvalid 60 protmode CTS burst roaming MANUAL > > but a DHCP request does not give me any IP addr; with > > # tcpdump -n -i ath0 > > it says: > > 19:01:01.603869 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:af:b2:ae:e6, length 300 > 19:01:02.036549 00:01:e3:0e:97:98 Unknown SSAP 0x2c > ff:ff:ff:ff:ff:ff Unknown DSAP 0xa2 Information, send seq 98, rcv seq 39, Flags [Command], length 36 > 19:01:02.958057 00:01:e3:0e:97:98 ProWay NM > ff:ff:ff:ff:ff:ff Unknown DSAP 0x5c Supervisory, Reject, rcv seq 8, Flags [Response], length 36 > 19:01:04.186892 00:01:e3:0e:97:98 Unknown SSAP 0xbe > ff:ff:ff:ff:ff:ff Unknown DSAP 0x44 Supervisory, Reject, rcv seq 39, Flags [Final], length 36 > 19:01:09.606218 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:15:af:b2:ae:e6, length 300 > > this situation is already for monthes and I gave up and always use UMTS > if I want connect to Internet; until yesterday I was thinking in some > kind of MAC addr filter in the AP, but .... > > yesterday I was there with a friend who has a Nokia mobile E51 device; I > gave him the key, he associated like me and got in the next second IP, > DNS and all was fine; > > what is that for a problem? it is not ath0 related because my other > laptop with iwi0 does not get IP either; > > what can I provide as information to nail this down? > What does athstats show for crypto errors? If the WEP-encrypted packet is dropped by the h/w then you will see the counter bump. Based on the above you are not running HEAD; if you can try that I can help more. Sam From guru at unixarea.de Sat Mar 7 07:29:09 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sat Mar 7 07:29:16 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <20090307133805.GA11596@rebelion.Sisis.de> References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> <20090307133805.GA11596@rebelion.Sisis.de> Message-ID: <20090307152846.GA42059@rebelion.Sisis.de> El d?a Saturday, March 07, 2009 a las 02:38:05PM +0100, Matthias Apitz escribi?: > El d?a Friday, March 06, 2009 a las 04:10:25PM -0800, Sam Leffler escribi?: > > > What does athstats show for crypto errors? If the WEP-encrypted packet > > is dropped by the h/w then you will see the counter bump. > > > > Based on the above you are not running HEAD; if you can try that I can > > help more. > > Sam, when I've built the HEAD kernel last year in August for my EeePC, > my hints file says about: > > ... > Sam's patch for HAL: > > # cd /usr/src/sys/contrib/dev > # mv ath ath.RELENG_7 > # tar xzf ath_hal-20080528.tgz > # mv ath_hal-20080528 ath > > Is this patch still required for RELENG_7, or already in the sourcen whe > I now do 'cvs update -rRELENG_7 src/sys'? It seems so from the age of > the files below /usr/src/sys/contrib/dev/ath after cvs update... argghh :-( no, this does not compile anymore; I have /usr/src/sys on RELENG_7; the wiki about EeePC, http://wiki.freebsd.org/AsusEee says: "...On RELENG_7, this WiFi card requires a new HAL. Copy the contents of the sys/contrib/dev/ath directory from the HEAD (CURRENT) to your RELENG_7 checkout. After that, rebuild your kernel." how do I update sys/contrib/dev/ath to HEAD? I've tried with # cd /usr/src/sys/contrib/dev/ath # cvs update -rHEAD ath ... cvs update: ath/public/xscale-le-elf.hal.o.uu is no longer in the repository cvs update: ath/public/xscale-le-elf.inc is no longer in the repository cvs update: ath/public/xscale-le-elf.opt_ah.h is no longer in the repository but this just let disappear all files there; what I'm doing wrong? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ From guru at unixarea.de Sat Mar 7 09:31:01 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sat Mar 7 09:31:08 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <49B1BB71.6060000@freebsd.org> References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> Message-ID: <20090307133805.GA11596@rebelion.Sisis.de> El d?a Friday, March 06, 2009 a las 04:10:25PM -0800, Sam Leffler escribi?: > What does athstats show for crypto errors? If the WEP-encrypted packet > is dropped by the h/w then you will see the counter bump. > > Based on the above you are not running HEAD; if you can try that I can > help more. Sam, when I've built the HEAD kernel last year in August for my EeePC, my hints file says about: ... Sam's patch for HAL: # cd /usr/src/sys/contrib/dev # mv ath ath.RELENG_7 # tar xzf ath_hal-20080528.tgz # mv ath_hal-20080528 ath Is this patch still required for RELENG_7, or already in the sourcen whe I now do 'cvs update -rRELENG_7 src/sys'? It seems so from the age of the files below /usr/src/sys/contrib/dev/ath after cvs update... Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ From sam at freebsd.org Sat Mar 7 09:33:26 2009 From: sam at freebsd.org (Sam Leffler) Date: Sat Mar 7 09:33:32 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <20090307133805.GA11596@rebelion.Sisis.de> References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> <20090307133805.GA11596@rebelion.Sisis.de> Message-ID: <49B2AFE5.8040101@freebsd.org> Matthias Apitz wrote: > El d?a Friday, March 06, 2009 a las 04:10:25PM -0800, Sam Leffler escribi?: > > >> What does athstats show for crypto errors? If the WEP-encrypted packet >> is dropped by the h/w then you will see the counter bump. >> >> Based on the above you are not running HEAD; if you can try that I can >> help more. >> > > Sam, when I've built the HEAD kernel last year in August for my EeePC, > my hints file says about: > > ... > Sam's patch for HAL: > > # cd /usr/src/sys/contrib/dev > # mv ath ath.RELENG_7 > # tar xzf ath_hal-20080528.tgz > # mv ath_hal-20080528 ath > > Is this patch still required for RELENG_7, or already in the sourcen whe > I now do 'cvs update -rRELENG_7 src/sys'? It seems so from the age of > the files below /usr/src/sys/contrib/dev/ath after cvs update... > Sorry but I don't understand. RELENG_7 wireless hasn't been touched in a long time. I circulated a patch to backport the hal source code but didn't get enough feedback to commit it. Sam From ivakras1 at gmail.com Sat Mar 7 10:35:03 2009 From: ivakras1 at gmail.com (=?utf-8?b?0JTQvNC40YLRgNC40Lkg0JrQvtC70L7RgdC+0LI=?=) Date: Sat Mar 7 10:35:09 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <20090307133805.GA11596@rebelion.Sisis.de> References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> <20090307133805.GA11596@rebelion.Sisis.de> Message-ID: <200903072133.35488.ivakras1@gmail.com> On ??????? 07 ????? 2009 16:38:05 Matthias Apitz wrote: > El d?a Friday, March 06, 2009 a las 04:10:25PM -0800, Sam Leffler escribi?: > > > What does athstats show for crypto errors? If the WEP-encrypted packet > > is dropped by the h/w then you will see the counter bump. > > > > Based on the above you are not running HEAD; if you can try that I can > > help more. > > Sam, when I've built the HEAD kernel last year in August for my EeePC, > my hints file says about: > > ... > Sam's patch for HAL: > > # cd /usr/src/sys/contrib/dev > # mv ath ath.RELENG_7 > # tar xzf ath_hal-20080528.tgz > # mv ath_hal-20080528 ath > > Is this patch still required for RELENG_7, or already in the sourcen whe > I now do 'cvs update -rRELENG_7 src/sys'? It seems so from the age of > the files below /usr/src/sys/contrib/dev/ath after cvs update... > > Thx > > matthias > Just use mad-wifi hal to replace a system one. It worked fine to me. After replacing /usr/src/sys/contrib/dev/ath/ with content of madwifi-hal-0.10.5.6-current.tar.gz/hal (and building a new kernel) my ath0 { ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) ath0: mem 0xf4000000-0xf400ffff irq 16 at device 0.0 on pci2 ath0@pci0:2:0:0: class=0x020000 card=0x04281468 chip=0x001c168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5006 family 802.11abg Wireless NIC' class = network subclass = ethernet } working very fast - burst, dturbo, Atheros Fast Frames modes, and other atheros modes supported wery well! But hardware led not blinking (under u-know-what OS it is blinking when tx or rx is active). From sam at freebsd.org Sat Mar 7 10:41:41 2009 From: sam at freebsd.org (Sam Leffler) Date: Sat Mar 7 10:41:48 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <200903072133.35488.ivakras1@gmail.com> References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> <20090307133805.GA11596@rebelion.Sisis.de> <200903072133.35488.ivakras1@gmail.com> Message-ID: <49B2BFE3.7070709@freebsd.org> ??????? ??????? wrote: > On ?????????????? 07 ?????????? 2009 16:38:05 Matthias Apitz wrote: > >> El d??a Friday, March 06, 2009 a las 04:10:25PM -0800, Sam Leffler escribi??: >> >> >>> What does athstats show for crypto errors? If the WEP-encrypted packet >>> is dropped by the h/w then you will see the counter bump. >>> >>> Based on the above you are not running HEAD; if you can try that I can >>> help more. >>> >> Sam, when I've built the HEAD kernel last year in August for my EeePC, >> my hints file says about: >> >> ... >> Sam's patch for HAL: >> >> # cd /usr/src/sys/contrib/dev >> # mv ath ath.RELENG_7 >> # tar xzf ath_hal-20080528.tgz >> # mv ath_hal-20080528 ath >> >> Is this patch still required for RELENG_7, or already in the sourcen whe >> I now do 'cvs update -rRELENG_7 src/sys'? It seems so from the age of >> the files below /usr/src/sys/contrib/dev/ath after cvs update... >> >> Thx >> >> matthias >> >> > > Just use mad-wifi hal to replace a system one. It worked fine to me. > After replacing /usr/src/sys/contrib/dev/ath/ with content of madwifi-hal-0.10.5.6-current.tar.gz/hal (and building a new kernel) my ath0 > { > ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) > ath0: mem 0xf4000000-0xf400ffff irq 16 at device 0.0 on pci2 > > ath0@pci0:2:0:0: class=0x020000 card=0x04281468 chip=0x001c168c rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5006 family 802.11abg Wireless NIC' > class = network > subclass = ethernet > > } > working very fast - burst, dturbo, Atheros Fast Frames modes, and other atheros modes supported wery well! But hardware led not blinking (under u-know-what OS it is blinking when tx or rx is active). > The source code hal has many bug fixes relative to the binary madwifi hal. Getting it into RELENG_7 is prerequisite for any changes moving from HEAD to RELENG_7. LED blinking is likely just a matter of enabling softled and programming the gpio pin and polarity. Sam From office at lambert.at Sat Mar 7 22:38:49 2009 From: office at lambert.at (office@lambert.at) Date: Sat Mar 7 22:38:57 2009 Subject: Lob & Tadel Message-ID: <200903080612.n286CCS8028679@lambert.at> Herzlichen Dank für Ihre Nachricht! Wir werden sie umgehend an die betroffene Stelle weiterleiten. Die Geschäftsleitung wurde ebenfalls informiert. Sie helfen uns damit, das Angebot und den Service für unsere Kunden permanent zu verbessern. Vielen Dank! Ihr Sanitätshaus Lambert From guru at unixarea.de Sat Mar 7 23:06:51 2009 From: guru at unixarea.de (Matthias Apitz) Date: Sat Mar 7 23:06:57 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <49B2AFE5.8040101@freebsd.org> References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> <20090307133805.GA11596@rebelion.Sisis.de> <49B2AFE5.8040101@freebsd.org> Message-ID: <20090308070636.GA1815@rebelion.Sisis.de> El d?a Saturday, March 07, 2009 a las 09:33:25AM -0800, Sam Leffler escribi?: > >Is this patch still required for RELENG_7, or already in the sourcen whe > >I now do 'cvs update -rRELENG_7 src/sys'? It seems so from the age of > >the files below /usr/src/sys/contrib/dev/ath after cvs update... > > > > Sorry but I don't understand. RELENG_7 wireless hasn't been touched in > a long time. I circulated a patch to backport the hal source code but > didn't get enough feedback to commit it. Hi Sam, Please send me or point me to this patch. I'll give it a try and will send you feedback about. Thanks in advance matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ From sam at freebsd.org Sun Mar 8 11:03:34 2009 From: sam at freebsd.org (Sam Leffler) Date: Sun Mar 8 11:03:40 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <20090308070636.GA1815@rebelion.Sisis.de> References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> <20090307133805.GA11596@rebelion.Sisis.de> <49B2AFE5.8040101@freebsd.org> <20090308070636.GA1815@rebelion.Sisis.de> Message-ID: <49B40874.10108@freebsd.org> Matthias Apitz wrote: > El d?a Saturday, March 07, 2009 a las 09:33:25AM -0800, Sam Leffler escribi?: > > >>> Is this patch still required for RELENG_7, or already in the sourcen whe >>> I now do 'cvs update -rRELENG_7 src/sys'? It seems so from the age of >>> the files below /usr/src/sys/contrib/dev/ath after cvs update... >>> >>> >> Sorry but I don't understand. RELENG_7 wireless hasn't been touched in >> a long time. I circulated a patch to backport the hal source code but >> didn't get enough feedback to commit it. >> > > Hi Sam, > Please send me or point me to this patch. I'll give it a try and will > send you feedback about. Thanks in advance > > matthias > http://article.gmane.org/gmane.os.freebsd.stable/60383/match=cft+ath+hal+src Understand this patch may now be stale. Sam From wahjava.ml at gmail.com Mon Mar 9 16:53:14 2009 From: wahjava.ml at gmail.com (Ashish SHUKLA) Date: Mon Mar 9 16:53:21 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <49B40874.10108@freebsd.org> (Sam Leffler's message of "Sun, 08 Mar 2009 11:03:32 -0700") References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> <20090307133805.GA11596@rebelion.Sisis.de> <49B2AFE5.8040101@freebsd.org> <20090308070636.GA1815@rebelion.Sisis.de> <49B40874.10108@freebsd.org> Message-ID: <871vt68ehq.fsf@chateau.d.lf> Hi, I'm now using 7.1-STABLE (amd64). Sam Leffler writes: [...] > http://article.gmane.org/gmane.os.freebsd.stable/60383/match=cft+ath+hal+src I tried your patch, and the output of wpa_supplicant is same as I used to get earlier with 8-CURRENT, so it needs the fast-frames checks related code which you added to 8-CURRENT. #v+ abbe [~] monte-cristo% sudo wpa_supplicant -Dbsd -iath0 -c/etc/wpa_supplicant.conf Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) Associated with 00:1e:2a:76:f4:60 WPA: 4-Way Handshake failed - pre-shared key may be incorrect CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) Associated with 00:1e:2a:76:f4:60 WPA: 4-Way Handshake failed - pre-shared key may be incorrect CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) Associated with 00:1e:2a:76:f4:60 WPA: 4-Way Handshake failed - pre-shared key may be incorrect CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) Associated with 00:1e:2a:76:f4:60 WPA: 4-Way Handshake failed - pre-shared key may be incorrect CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) Associated with 00:1e:2a:76:f4:60 ^CCTRL-EVENT-TERMINATING - signal 2 received #v- Thanks -- Ashish SHUKLA -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090309/88d8cf10/attachment.pgp From sam at freebsd.org Mon Mar 9 17:12:22 2009 From: sam at freebsd.org (Sam Leffler) Date: Mon Mar 9 17:12:29 2009 Subject: associated to AP (WEP mode) && no IP addr via DHCP In-Reply-To: <871vt68ehq.fsf@chateau.d.lf> References: <20090305120022.GA8012@rebelion.Sisis.de> <49B1BB71.6060000@freebsd.org> <20090307133805.GA11596@rebelion.Sisis.de> <49B2AFE5.8040101@freebsd.org> <20090308070636.GA1815@rebelion.Sisis.de> <49B40874.10108@freebsd.org> <871vt68ehq.fsf@chateau.d.lf> Message-ID: <49B5B063.7010204@freebsd.org> Ashish SHUKLA wrote: > Hi, > > I'm now using 7.1-STABLE (amd64). > > Sam Leffler writes: > > [...] > > >> http://article.gmane.org/gmane.os.freebsd.stable/60383/match=cft+ath+hal+src >> > > I tried your patch, and the output of wpa_supplicant is same as I used > to get earlier with 8-CURRENT, so it needs the fast-frames checks > related code which you added to 8-CURRENT. > > #v+ > abbe [~] monte-cristo% sudo wpa_supplicant -Dbsd -iath0 -c/etc/wpa_supplicant.conf > Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) > Associated with 00:1e:2a:76:f4:60 > WPA: 4-Way Handshake failed - pre-shared key may be incorrect > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys > Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) > Associated with 00:1e:2a:76:f4:60 > WPA: 4-Way Handshake failed - pre-shared key may be incorrect > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys > Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) > Associated with 00:1e:2a:76:f4:60 > WPA: 4-Way Handshake failed - pre-shared key may be incorrect > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys > Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) > Associated with 00:1e:2a:76:f4:60 > WPA: 4-Way Handshake failed - pre-shared key may be incorrect > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys > Trying to associate with 00:1e:2a:76:f4:60 (SSID='18-B-PARVATIYA' freq=2437 MHz) > Associated with 00:1e:2a:76:f4:60 > ^CCTRL-EVENT-TERMINATING - signal 2 received > #v- > Thank you for the reminder. The first step is to get the hal in. Once that's accomplished I'm willing to look at backmerging useful fixes. Unfortunately my ability to make anything but simple changes is very limited as no padding was added to any net80211 data structures so I'm hamstrung. Sam From saifi.khan at twincling.org Mon Mar 9 18:08:07 2009 From: saifi.khan at twincling.org (Saifi Khan) Date: Mon Mar 9 18:08:20 2009 Subject: is there a laptop ? Message-ID: Hi all: i've looked at tuxmobil, bsdgroup.de etc and i don't want to use ndiswrapper, or broadcom or additional PCMCIA card at all. Is there a laptop model (available in market) that experienced members would like to recommend wherein . the WiFi 802.11 a/g (PCI based) . Ethernet port . and ACPI work absolutely fine with FreeBSD 7.x ? thanks Saifi. From takash-i at sophia.ac.jp Mon Mar 9 23:38:51 2009 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Mon Mar 9 23:38:58 2009 Subject: is there a laptop ? In-Reply-To: References: Message-ID: <49B60754.4080301@sophia.ac.jp> Hi, > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > ndiswrapper, or broadcom or additional PCMCIA card at all. > > Is there a laptop model (available in market) that experienced > members would like to recommend wherein > . the WiFi 802.11 a/g (PCI based) > . Ethernet port > . and ACPI > work absolutely fine with FreeBSD 7.x ? If you want to use ACPI suspend/resume, you need to kill one of two core in Core2Duo. If you want the both, choose Linux insted. Cheers, T. I. From taken2k4 at gmail.com Tue Mar 10 05:32:22 2009 From: taken2k4 at gmail.com (Francisco Rivas) Date: Tue Mar 10 05:32:28 2009 Subject: FreeBSD in a Dell Latitude E4300 Message-ID: <2fcf3fa50903100503xe4c7b04na942bcc08c61f68c@mail.gmail.com> Hi :D I bought a new laptop a Dell Latitude E4300 and I want to use FreeBSD but I do not know if my hardware is supported yet. Does somebody installed freebsd in this laptop?... thanks in advance ans best regards. -- Francisco Rivas http://www.vaslibre.org.ve - And on the seventh day God said :wq and then make http://beck3r.wordpress.com/ Linux User (New) : #448324 Linux Machine (New) : 355187 From lists at braisel.com Tue Mar 10 06:36:35 2009 From: lists at braisel.com (=?iso-8859-1?Q?Andr=E9?= Braselmann) Date: Tue Mar 10 06:36:51 2009 Subject: FreeBSD in a Dell Latitude E4300 In-Reply-To: <2fcf3fa50903100503xe4c7b04na942bcc08c61f68c@mail.gmail.com> References: <2fcf3fa50903100503xe4c7b04na942bcc08c61f68c@mail.gmail.com> Message-ID: <20090310133635.GA2125@trashbin.none.lan> On Tue, Mar 10, 2009 at 01:03:41PM +0100, Francisco Rivas wrote: > Hi :D > > I bought a new laptop a Dell Latitude E4300 and I want to use FreeBSD but I > do not know if my hardware is supported yet. Does somebody installed freebsd > in this laptop?... in fact that you bought it, just download/burn/insert a 7.1 Release CD and TRY it. The you'll know. K.Andr? Braselmann -- From saifi.khan at twincling.org Tue Mar 10 11:57:53 2009 From: saifi.khan at twincling.org (Saifi Khan) Date: Tue Mar 10 11:58:00 2009 Subject: is there a laptop ? In-Reply-To: <49B60754.4080301@sophia.ac.jp> References: <49B60754.4080301@sophia.ac.jp> Message-ID: On Tue, 10 Mar 2009, Takashi Inoue wrote: > Hi, > > > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > > ndiswrapper, or broadcom or additional PCMCIA card at all. > > > > Is there a laptop model (available in market) that experienced > > members would like to recommend wherein > > . the WiFi 802.11 a/g (PCI based) > > . Ethernet port . and ACPI > > work absolutely fine with FreeBSD 7.x ? > > If you want to use ACPI suspend/resume, > you need to kill one of two core in Core2Duo. > If you want the both, choose Linux insted. > > Cheers, > T. I. > Are you saying that ACPI implementation in FreeBSD is buggy ? Do you have any suggestions about laptops to make (assuming ACPI is disabled) ? thanks Saifi. From frank at shute.org.uk Tue Mar 10 14:11:15 2009 From: frank at shute.org.uk (Frank Shute) Date: Tue Mar 10 14:11:22 2009 Subject: is there a laptop ? In-Reply-To: References: <49B60754.4080301@sophia.ac.jp> Message-ID: <20090310205304.GA84417@melon.esperance-linux.co.uk> On Wed, Mar 11, 2009 at 12:31:41AM +0000, Saifi Khan wrote: > > On Tue, 10 Mar 2009, Takashi Inoue wrote: > > > Hi, > > > > > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > > > ndiswrapper, or broadcom or additional PCMCIA card at all. > > > > > > Is there a laptop model (available in market) that experienced > > > members would like to recommend wherein > > > . the WiFi 802.11 a/g (PCI based) > > > . Ethernet port . and ACPI > > > work absolutely fine with FreeBSD 7.x ? > > > > If you want to use ACPI suspend/resume, > > you need to kill one of two core in Core2Duo. > > If you want the both, choose Linux insted. > > > > Cheers, > > T. I. > > > > Are you saying that ACPI implementation in FreeBSD is buggy ? > > Do you have any suggestions about laptops to make (assuming ACPI > is disabled) ? > You can still use ACPI, it's just that suspend/resume might not work. If you use ACPI then you can run powerd(8) which will prolong battery life. I bought a Dell XPS1330 on which everything seems to work on 7.1-R; even the fingerprint reader can be made to work (can't remember the port to use). I don't use powerd as I usually have the laptop plugged in. BTW, I've got an old Thinkpad and I much prefer the Trackpoint to the Dell's Touchpad, YMMV. So my advice is to look at the Thinkpads. A lot of BSD users use them & their hardware is well supported by FreeBSD, I believe. > > thanks > Saifi. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html From cwhiteh at onetel.com Wed Mar 11 16:41:49 2009 From: cwhiteh at onetel.com (Chris Whitehouse) Date: Wed Mar 11 16:41:57 2009 Subject: is there a laptop ? In-Reply-To: References: Message-ID: <49B8498B.9080402@onetel.com> Saifi Khan wrote: > Hi all: > > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > ndiswrapper, or broadcom or additional PCMCIA card at all. > > Is there a laptop model (available in market) that experienced > members would like to recommend wherein > . the WiFi 802.11 a/g (PCI based) > . Ethernet port > . and ACPI > work absolutely fine with FreeBSD 7.x ? > > > thanks > Saifi. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > HP nc6320 (google RH383ET) - most things work, including wifi and ethernet, except for the following: - gives a repeated message like acpi_tz0 absurd value ignoring - dmesg shows dvd drive errors on each boot and later hald-addon-storage will start using 100%cpu till it is killed (I think they are connected but haven't really investigated) - with FreeBSD (latest PCBSD) cpu fan comes on more than it did with windows and battery doesn't last as long - haven't tested suspend/resume or internal modem. - don't think the finger print reader or the card reader are recognised. - build quality is probably not as good as the IBM's Sorry not to give exact messages, I'm at a different machine but I can give you dmesg etc later if required. Chris PS don't buy from laptopsdirect.co.uk unless you want to get spammed from them and various associated online shops. From saifi.khan at twincling.org Wed Mar 11 19:51:34 2009 From: saifi.khan at twincling.org (Saifi Khan) Date: Wed Mar 11 19:51:46 2009 Subject: is there a laptop ? In-Reply-To: <49B8498B.9080402@onetel.com> References: <49B8498B.9080402@onetel.com> Message-ID: On Wed, 11 Mar 2009, Chris Whitehouse wrote: > > > HP nc6320 (google RH383ET) - most things work, including wifi and ethernet, > except for the following: > >From HP site, Network Integrated Broadcom NetLink Gigabit Ethernet PCI Controller (10/100/1000 NIC) Wireless Broadcom 802.11a/b/g; Broadcom 802.11b/g; Bluetooth 2.0 It seems to have the US-trash-com chipset ! Do Atheros, Ralink, Realtek, Intel PRO/Wireless chipset work with FreeBSD ? thanks Saifi. From takash-i at sophia.ac.jp Wed Mar 11 20:17:58 2009 From: takash-i at sophia.ac.jp (Takashi Inoue) Date: Wed Mar 11 20:18:04 2009 Subject: is there a laptop ? In-Reply-To: References: <49B60754.4080301@sophia.ac.jp> Message-ID: <49B87EC9.80705@sophia.ac.jp> > Are you saying that ACPI implementation in FreeBSD is buggy ? > > Do you have any suggestions about laptops to make (assuming ACPI > is disabled) ? > I don't know whether the ACPI implementation in FreeBSD is buggy or not. But at least I know it is incompatible with SMP. Cheers, T.I From oberman at es.net Wed Mar 11 21:14:55 2009 From: oberman at es.net (Kevin Oberman) Date: Wed Mar 11 21:15:07 2009 Subject: is there a laptop ? In-Reply-To: Your message of "Thu, 12 Mar 2009 08:25:28 -0000." Message-ID: <20090312041452.64C961CC0B@ptavv.es.net> > Date: Thu, 12 Mar 2009 08:25:28 +0000 (GMT) > From: Saifi Khan > Sender: owner-freebsd-mobile@freebsd.org > > On Wed, 11 Mar 2009, Chris Whitehouse wrote: > > > > > > HP nc6320 (google RH383ET) - most things work, including wifi and ethernet, > > except for the following: > > > > >From HP site, > > Network > Integrated Broadcom NetLink Gigabit Ethernet PCI Controller > (10/100/1000 NIC) > > Wireless > Broadcom 802.11a/b/g; Broadcom 802.11b/g; Bluetooth 2.0 > > > It seems to have the US-trash-com chipset ! > > Do Atheros, Ralink, Realtek, Intel PRO/Wireless chipset work > with FreeBSD ? Atheros - if_ath Ralink - if_ral Realtek - Most if_re and if_rl Intel PRO/Wireless - if_ipw, if_iwi, if_wpi For the exact chips supported, see the man pages for the drivers. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From wahjava.ml at gmail.com Thu Mar 12 06:46:44 2009 From: wahjava.ml at gmail.com (Ashish SHUKLA) Date: Thu Mar 12 06:46:50 2009 Subject: is there a laptop ? In-Reply-To: (Saifi Khan's message of "Thu, 12 Mar 2009 08:25:28 +0000 (GMT)") References: <49B8498B.9080402@onetel.com> Message-ID: <87k56uvop2.fsf@chateau.d.lf> Saifi Khan writes: [...] > Do Atheros, Ralink, Realtek, Intel PRO/Wireless chipset work > with FreeBSD ? Atheros chipsets work great with FreeBSD 8-CURRENT at least. And the driver is FOSS and blob free. No ideas about other chipsets. -- Ashish SHUKLA -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090312/bcf5bd37/attachment.pgp From jw.hendy at gmail.com Thu Mar 12 07:10:23 2009 From: jw.hendy at gmail.com (John Hendy) Date: Thu Mar 12 07:10:55 2009 Subject: is there a laptop ? In-Reply-To: <87k56uvop2.fsf@chateau.d.lf> References: <49B8498B.9080402@onetel.com> <87k56uvop2.fsf@chateau.d.lf> Message-ID: For Atheros, the exact chipset is still important... my Macbook's Atheros AR5008 (aka AR5418) does not work with the FBSD ath driver. i386 works if I ndisgen a kernel module from a WinXP driver, but I have not been able to ndisgen a module successfully for amd64, which is what I'd like to run. The kernel panics every time I load it. I'm using FBSD-7.1-amd64, so I can't speak of the capabilities of 8.0, but the hardware notes do not seem to have changed re the ath driver ( http://www.freebsd.org/relnotes/CURRENT/hardware/support.html#WLAN)... Even though it only states that AR5005VL chips are unsupported, mine still is not picked up and it's definitely an AR5008. - John On Thu, Mar 12, 2009 at 8:46 AM, Ashish SHUKLA wrote: > Saifi Khan writes: > > [...] > > > Do Atheros, Ralink, Realtek, Intel PRO/Wireless chipset work > > with FreeBSD ? > > Atheros chipsets work great with FreeBSD 8-CURRENT at least. And the > driver is FOSS and blob free. No ideas about other chipsets. > > -- > Ashish SHUKLA > From saifi.khan at twincling.org Thu Mar 12 07:29:32 2009 From: saifi.khan at twincling.org (Saifi Khan) Date: Thu Mar 12 07:29:44 2009 Subject: is there a laptop ? In-Reply-To: <87k56uvop2.fsf@chateau.d.lf> References: <49B8498B.9080402@onetel.com> <87k56uvop2.fsf@chateau.d.lf> Message-ID: On Thu, 12 Mar 2009, Ashish SHUKLA wrote: > Saifi Khan writes: > > [...] > > > Do Atheros, Ralink, Realtek, Intel PRO/Wireless chipset work > > with FreeBSD ? > > Atheros chipsets work great with FreeBSD 8-CURRENT at least. And the > driver is FOSS and blob free. No ideas about other chipsets. > > -- > Ashish SHUKLA > There are Atheros chipsets which don't work with FreeBSD ! An OSS (Open Source software) driver is certainly appreciated. I've very good idea about the chipsets dumped in Indian markets, hence the specificity of the question. thanks Saifi KHAN. From sam at freebsd.org Thu Mar 12 08:54:08 2009 From: sam at freebsd.org (Sam Leffler) Date: Thu Mar 12 08:54:14 2009 Subject: is there a laptop ? In-Reply-To: References: <49B8498B.9080402@onetel.com> <87k56uvop2.fsf@chateau.d.lf> Message-ID: <49B9301E.30708@freebsd.org> 5418 has worked for several years in HEAD. At this point the only ath chips not working in HEAD are those I haven't had access to (9280 and 9285) and 9280 support should go in shortly. About the only thing missing for ath is support for 11n (the 802.11 layer has supported 11n on other devices for several years and been used in various products). I can't comment on RELENG_7 support as I don't run it. Sam John Hendy wrote: > For Atheros, the exact chipset is still important... my Macbook's Atheros > AR5008 (aka AR5418) does not work with the FBSD ath driver. i386 works if I > ndisgen a kernel module from a WinXP driver, but I have not been able to > ndisgen a module successfully for amd64, which is what I'd like to run. The > kernel panics every time I load it. > I'm using FBSD-7.1-amd64, so I can't speak of the capabilities of 8.0, but > the hardware notes do not seem to have changed re the ath driver ( > http://www.freebsd.org/relnotes/CURRENT/hardware/support.html#WLAN)... Even > though it only states that AR5005VL chips are unsupported, mine still is not > picked up and it's definitely an AR5008. > > > - John > > On Thu, Mar 12, 2009 at 8:46 AM, Ashish SHUKLA wrote: > > >> Saifi Khan writes: >> >> [...] >> >> >>> Do Atheros, Ralink, Realtek, Intel PRO/Wireless chipset work >>> with FreeBSD ? >>> >> Atheros chipsets work great with FreeBSD 8-CURRENT at least. And the >> driver is FOSS and blob free. No ideas about other chipsets. >> >> -- >> Ashish SHUKLA >> >> > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > > > From jw.hendy at gmail.com Thu Mar 12 09:16:11 2009 From: jw.hendy at gmail.com (John Hendy) Date: Thu Mar 12 09:16:28 2009 Subject: is there a laptop ? In-Reply-To: <49B9301E.30708@freebsd.org> References: <49B8498B.9080402@onetel.com> <87k56uvop2.fsf@chateau.d.lf> <49B9301E.30708@freebsd.org> Message-ID: I've never heard of HEAD... I'm pretty new to freebsd, so that could very well be why! Google is just giving me search results with people doing such and such with 'freebsd-head', not what it is. -John On Thu, Mar 12, 2009 at 10:54 AM, Sam Leffler wrote: > 5418 has worked for several years in HEAD. At this point the only ath > chips not working in HEAD are those I haven't had access to (9280 and 9285) > and 9280 support should go in shortly. About the only thing missing for ath > is support for 11n (the 802.11 layer has supported 11n on other devices for > several years and been used in various products). > > I can't comment on RELENG_7 support as I don't run it. > > Sam > > John Hendy wrote: > >> For Atheros, the exact chipset is still important... my Macbook's Atheros >> AR5008 (aka AR5418) does not work with the FBSD ath driver. i386 works if >> I >> ndisgen a kernel module from a WinXP driver, but I have not been able to >> ndisgen a module successfully for amd64, which is what I'd like to run. >> The >> kernel panics every time I load it. >> I'm using FBSD-7.1-amd64, so I can't speak of the capabilities of 8.0, but >> the hardware notes do not seem to have changed re the ath driver ( >> http://www.freebsd.org/relnotes/CURRENT/hardware/support.html#WLAN)... >> Even >> though it only states that AR5005VL chips are unsupported, mine still is >> not >> picked up and it's definitely an AR5008. >> >> >> - John >> >> On Thu, Mar 12, 2009 at 8:46 AM, Ashish SHUKLA >> wrote: >> >> >> >>> Saifi Khan writes: >>> >>> [...] >>> >>> >>> >>>> Do Atheros, Ralink, Realtek, Intel PRO/Wireless chipset work >>>> with FreeBSD ? >>>> >>>> >>> Atheros chipsets work great with FreeBSD 8-CURRENT at least. And the >>> driver is FOSS and blob free. No ideas about other chipsets. >>> >>> -- >>> Ashish SHUKLA >>> >>> >>> >> _______________________________________________ >> freebsd-mobile@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile >> To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" >> >> >> >> > > From doug at polands.org Thu Mar 12 10:14:43 2009 From: doug at polands.org (Doug Poland) Date: Thu Mar 12 10:14:55 2009 Subject: is there a laptop ? In-Reply-To: <49B8498B.9080402@onetel.com> References: <49B8498B.9080402@onetel.com> Message-ID: <49B935ED.90601@polands.org> Chris Whitehouse wrote: > Saifi Khan wrote: >> Hi all: >> >> i've looked at tuxmobil, bsdgroup.de etc and i don't want to use >> ndiswrapper, or broadcom or additional PCMCIA card at all. >> >> Is there a laptop model (available in market) that experienced >> members would like to recommend wherein . the WiFi 802.11 a/g (PCI >> based) >> . Ethernet port . and ACPI work absolutely fine with FreeBSD 7.x ? >> >> Coming in kinda late on this thread but... I recently came across a Toshiba Satellite L350 (L355D-S7825). It works quite nicely with 7.1-STABLE. The only issues are... * needed to build ath wireless driver based on some stuff I googled * Doesn't recognize on-board bluetooth, modem, or SD card reader. * The touchpad surface is flush with palm rest and triggered too easily * Display only does 1440x900 * 2 hour battery life. Pros: * 7.1-STABLE amd64 runs great! * Radeon video works great * ath wireless and rl0 work great * 2.0GHz AMD dual with 3GB RAM * Only $600 from BestBuy * 17" display * Does Ubuntu 8.10 (amd64) flawlessly, even 64-bit flash This is no high-end HP or Lenovo, but for $600US, it's not a bad laptop for 64-bit FreeBSD. Never tried ACPI features, I just assume suspend/resume will not work and power on/off. YMMV -- Regards, Doug From saifi.khan at twincling.org Thu Mar 12 10:31:11 2009 From: saifi.khan at twincling.org (Saifi Khan) Date: Thu Mar 12 10:31:17 2009 Subject: is there a laptop ? In-Reply-To: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> Message-ID: On Thu, 12 Mar 2009, Maciej Suszko wrote: > Saifi Khan wrote: > > Hi all: > > > > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > > ndiswrapper, or broadcom or additional PCMCIA card at all. > > > > Is there a laptop model (available in market) that experienced > > members would like to recommend wherein > > . the WiFi 802.11 a/g (PCI based) > > . Ethernet port > > . and ACPI > > work absolutely fine with FreeBSD 7.x ? > > I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried the > suspend/resume, firewire port and I suppose the modem is not > going to work. Everything else is working fine for me. > -- > regards, Maciej Suszko. > What is the wireless chipset of your machine ? thanks Saifi. From msuszko at gmail.com Thu Mar 12 10:42:29 2009 From: msuszko at gmail.com (Maciej Suszko) Date: Thu Mar 12 10:42:35 2009 Subject: is there a laptop ? In-Reply-To: References: Message-ID: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> Saifi Khan wrote: > Hi all: > > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > ndiswrapper, or broadcom or additional PCMCIA card at all. > > Is there a laptop model (available in market) that experienced > members would like to recommend wherein > . the WiFi 802.11 a/g (PCI based) > . Ethernet port > . and ACPI > work absolutely fine with FreeBSD 7.x ? I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried the suspend/resume, firewire port and I suppose the modem is not going to work. Everything else is working fine for me. -- regards, Maciej Suszko. From saifi.khan at twincling.org Thu Mar 12 11:13:24 2009 From: saifi.khan at twincling.org (Saifi Khan) Date: Thu Mar 12 11:13:36 2009 Subject: is there a laptop ? In-Reply-To: <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> Message-ID: On Thu, 12 Mar 2009, Paul B. Mahol wrote: > On 3/13/09, Saifi Khan wrote: > > On Thu, 12 Mar 2009, Maciej Suszko wrote: > > > >> Saifi Khan wrote: > >> > Hi all: > >> > > >> > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > >> > ndiswrapper, or broadcom or additional PCMCIA card at all. > >> > > >> > Is there a laptop model (available in market) that experienced > >> > members would like to recommend wherein > >> > . the WiFi 802.11 a/g (PCI based) > >> > . Ethernet port > >> > . and ACPI > >> > work absolutely fine with FreeBSD 7.x ? > >> > >> I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried the > >> suspend/resume, firewire port and I suppose the modem is not > >> going to work. Everything else is working fine for me. > >> -- > >> regards, Maciej Suszko. > >> > > > > What is the wireless chipset of your machine ? > > On mine nx7300 it is broadcom one and works fine via ndis. > Suspend/resume works fine if second core is disabled and vesa is > loaded in kernel > (either via kldload or via custom kernel) > Firewire and bluetooth are supported and should work without problems. > Ethernet works via if_bfe; carbus, drm, sound works fine ... > In short everything is supported on UP kernel except winmodem. > > There are some bugs in BIOS asl which I fixed adding: > > acpi_dsdt_load="YES" > acpi_dsdt_name="/boot/acpi.aml" > > in /boot/loader.conf > > /boot/acpi.aml is modified version of ASL which address "temperature > is absurd, ignored" > type of messages. > > > 8.0 CURRENT i386. > > -- > Paul > Thanks Paul. i'd like to avoid Trash-com chipset at all costs. When Maciej wrote HP nx, i thought here comes another laptop baked with Trash-com chipset cookie. Indian market is filled with these trash-com HP/Compaq laptops. I really don't mind buying something 1-2 yr old, as long as i've got all the stuff working fine. Any suggestions on BenQ R58 ? It's about $ 560 here and atleast one guy claims that it has Ralink chipset. Anybody knows ? thanks Saifi. From onemda at gmail.com Thu Mar 12 11:16:12 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Mar 12 11:16:18 2009 Subject: is there a laptop ? In-Reply-To: References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> Message-ID: <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> On 3/13/09, Saifi Khan wrote: > On Thu, 12 Mar 2009, Maciej Suszko wrote: > >> Saifi Khan wrote: >> > Hi all: >> > >> > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use >> > ndiswrapper, or broadcom or additional PCMCIA card at all. >> > >> > Is there a laptop model (available in market) that experienced >> > members would like to recommend wherein >> > . the WiFi 802.11 a/g (PCI based) >> > . Ethernet port >> > . and ACPI >> > work absolutely fine with FreeBSD 7.x ? >> >> I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried the >> suspend/resume, firewire port and I suppose the modem is not >> going to work. Everything else is working fine for me. >> -- >> regards, Maciej Suszko. >> > > What is the wireless chipset of your machine ? On mine nx7300 it is broadcom one and works fine via ndis. Suspend/resume works fine if second core is disabled and vesa is loaded in kernel (either via kldload or via custom kernel) Firewire and bluetooth are supported and should work without problems. Ethernet works via if_bfe; carbus, drm, sound works fine ... In short everything is supported on UP kernel except winmodem. There are some bugs in BIOS asl which I fixed adding: acpi_dsdt_load="YES" acpi_dsdt_name="/boot/acpi.aml" in /boot/loader.conf /boot/acpi.aml is modified version of ASL which address "temperature is absurd, ignored" type of messages. 8.0 CURRENT i386. -- Paul From onemda at gmail.com Thu Mar 12 12:28:57 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Mar 12 12:29:05 2009 Subject: is there a laptop ? In-Reply-To: <20090312201357.73f6ba86@suszko.eu> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> <20090312201357.73f6ba86@suszko.eu> Message-ID: <3a142e750903121228r27c314d1kc471ef6390c1e21c@mail.gmail.com> On 3/12/09, Maciej Suszko wrote: > "Paul B. Mahol" wrote: >> On 3/13/09, Saifi Khan wrote: >> > On Thu, 12 Mar 2009, Maciej Suszko wrote: >> > >> >> Saifi Khan wrote: >> >> > Hi all: >> >> > >> >> > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use >> >> > ndiswrapper, or broadcom or additional PCMCIA card at all. >> >> > >> >> > Is there a laptop model (available in market) that experienced >> >> > members would like to recommend wherein >> >> > . the WiFi 802.11 a/g (PCI based) >> >> > . Ethernet port >> >> > . and ACPI >> >> > work absolutely fine with FreeBSD 7.x ? >> >> >> >> I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried >> >> the suspend/resume, firewire port and I suppose the modem is not >> >> going to work. Everything else is working fine for me. >> >> -- >> >> regards, Maciej Suszko. >> >> >> > >> > What is the wireless chipset of your machine ? >> >> On mine nx7300 it is broadcom one and works fine via ndis. >> Suspend/resume works fine if second core is disabled and vesa is >> loaded in kernel >> (either via kldload or via custom kernel) >> Firewire and bluetooth are supported and should work without problems. >> Ethernet works via if_bfe; carbus, drm, sound works fine ... >> In short everything is supported on UP kernel except winmodem. >> >> There are some bugs in BIOS asl which I fixed adding: >> >> acpi_dsdt_load="YES" >> acpi_dsdt_name="/boot/acpi.aml" >> >> in /boot/loader.conf >> >> /boot/acpi.aml is modified version of ASL which address "temperature >> is absurd, ignored" >> type of messages. >> >> >> 8.0 CURRENT i386. > > On 7.0, 7.1 and 7-STABLE there is still a little bit annoying message > in dmesg on my nx7300, but i it's harmless as I suppose: > acpi_tz0: _CRT value is absurd, ignored (256.0C) Not for me, it caused livelocks in syscons while using powerd (h)adp mode, making entire session useless and forcing me to reboot machine. -- Paul From maciej at suszko.eu Thu Mar 12 12:29:03 2009 From: maciej at suszko.eu (Maciej Suszko) Date: Thu Mar 12 12:29:16 2009 Subject: is there a laptop ? In-Reply-To: <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> Message-ID: <20090312201357.73f6ba86@suszko.eu> "Paul B. Mahol" wrote: > On 3/13/09, Saifi Khan wrote: > > On Thu, 12 Mar 2009, Maciej Suszko wrote: > > > >> Saifi Khan wrote: > >> > Hi all: > >> > > >> > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > >> > ndiswrapper, or broadcom or additional PCMCIA card at all. > >> > > >> > Is there a laptop model (available in market) that experienced > >> > members would like to recommend wherein > >> > . the WiFi 802.11 a/g (PCI based) > >> > . Ethernet port > >> > . and ACPI > >> > work absolutely fine with FreeBSD 7.x ? > >> > >> I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried > >> the suspend/resume, firewire port and I suppose the modem is not > >> going to work. Everything else is working fine for me. > >> -- > >> regards, Maciej Suszko. > >> > > > > What is the wireless chipset of your machine ? > > On mine nx7300 it is broadcom one and works fine via ndis. > Suspend/resume works fine if second core is disabled and vesa is > loaded in kernel > (either via kldload or via custom kernel) > Firewire and bluetooth are supported and should work without problems. > Ethernet works via if_bfe; carbus, drm, sound works fine ... > In short everything is supported on UP kernel except winmodem. > > There are some bugs in BIOS asl which I fixed adding: > > acpi_dsdt_load="YES" > acpi_dsdt_name="/boot/acpi.aml" > > in /boot/loader.conf > > /boot/acpi.aml is modified version of ASL which address "temperature > is absurd, ignored" > type of messages. > > > 8.0 CURRENT i386. On 7.0, 7.1 and 7-STABLE there is still a little bit annoying message in dmesg on my nx7300, but i it's harmless as I suppose: acpi_tz0: _CRT value is absurd, ignored (256.0C) -- regards, Maciej Suszko. From maciej at suszko.eu Thu Mar 12 12:37:31 2009 From: maciej at suszko.eu (Maciej Suszko) Date: Thu Mar 12 12:37:43 2009 Subject: is there a laptop ? In-Reply-To: References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> Message-ID: <20090312201046.4bec4e8e@suszko.eu> Saifi Khan wrote: > On Thu, 12 Mar 2009, Maciej Suszko wrote: > > > Saifi Khan wrote: > > > Hi all: > > > > > > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > > > ndiswrapper, or broadcom or additional PCMCIA card at all. > > > > > > Is there a laptop model (available in market) that experienced > > > members would like to recommend wherein > > > . the WiFi 802.11 a/g (PCI based) > > > . Ethernet port > > > . and ACPI > > > work absolutely fine with FreeBSD 7.x ? > > > > I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried > > the suspend/resume, firewire port and I suppose the modem is not > > going to work. Everything else is working fine for me. > > -- > > regards, Maciej Suszko. > > > > What is the wireless chipset of your machine ? Here's what pciconf says: wpi0@pci0:16:0:0: class=0x028000 card=0x135c103c chip=0x42228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '10418086 Intel 3945ABG Wireless LAN controller' class = network -- regards, Maciej Suszko. From maciej at suszko.eu Thu Mar 12 12:38:36 2009 From: maciej at suszko.eu (Maciej Suszko) Date: Thu Mar 12 12:38:42 2009 Subject: is there a laptop ? In-Reply-To: <3a142e750903121228r27c314d1kc471ef6390c1e21c@mail.gmail.com> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> <20090312201357.73f6ba86@suszko.eu> <3a142e750903121228r27c314d1kc471ef6390c1e21c@mail.gmail.com> Message-ID: <20090312203830.415e24fd@suszko.eu> "Paul B. Mahol" wrote: > On 3/12/09, Maciej Suszko wrote: > > "Paul B. Mahol" wrote: > >> On 3/13/09, Saifi Khan wrote: > >> > On Thu, 12 Mar 2009, Maciej Suszko wrote: > >> > > >> >> Saifi Khan wrote: > >> >> > Hi all: > >> >> > > >> >> > i've looked at tuxmobil, bsdgroup.de etc and i don't want to > >> >> > use ndiswrapper, or broadcom or additional PCMCIA card at all. > >> >> > > >> >> > Is there a laptop model (available in market) that experienced > >> >> > members would like to recommend wherein > >> >> > . the WiFi 802.11 a/g (PCI based) > >> >> > . Ethernet port > >> >> > . and ACPI > >> >> > work absolutely fine with FreeBSD 7.x ? > >> >> > >> >> I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't > >> >> tried the suspend/resume, firewire port and I suppose the modem > >> >> is not going to work. Everything else is working fine for me. > >> >> -- > >> >> regards, Maciej Suszko. > >> >> > >> > > >> > What is the wireless chipset of your machine ? > >> > >> On mine nx7300 it is broadcom one and works fine via ndis. > >> Suspend/resume works fine if second core is disabled and vesa is > >> loaded in kernel > >> (either via kldload or via custom kernel) > >> Firewire and bluetooth are supported and should work without > >> problems. Ethernet works via if_bfe; carbus, drm, sound works > >> fine ... In short everything is supported on UP kernel except > >> winmodem. > >> > >> There are some bugs in BIOS asl which I fixed adding: > >> > >> acpi_dsdt_load="YES" > >> acpi_dsdt_name="/boot/acpi.aml" > >> > >> in /boot/loader.conf > >> > >> /boot/acpi.aml is modified version of ASL which address > >> "temperature is absurd, ignored" > >> type of messages. > >> > >> > >> 8.0 CURRENT i386. > > > > On 7.0, 7.1 and 7-STABLE there is still a little bit annoying > > message in dmesg on my nx7300, but i it's harmless as I suppose: > > acpi_tz0: _CRT value is absurd, ignored (256.0C) > > Not for me, it caused livelocks in syscons while using powerd (h)adp > mode, making entire session useless and forcing me to reboot machine. I didn't notice such behavior - the only I observed is that running powerd in adaptive mode, the lowest frequency supported by CPU is ,,too low'' - I set 500MHz as the lowest possible via sysctl... but I'll take a closer look on that :) -- regards, Maciej Suszko. From wojtek at wojtek.tensor.gdynia.pl Thu Mar 12 12:47:31 2009 From: wojtek at wojtek.tensor.gdynia.pl (Wojciech Puchar) Date: Thu Mar 12 12:47:37 2009 Subject: is there a laptop ? In-Reply-To: <20090312201357.73f6ba86@suszko.eu> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> <20090312201357.73f6ba86@suszko.eu> Message-ID: >> 8.0 CURRENT i386. > > On 7.0, 7.1 and 7-STABLE there is still a little bit annoying message > in dmesg on my nx7300, but i it's harmless as I suppose: > acpi_tz0: _CRT value is absurd, ignored (256.0C) completely harmless, it's buggy ACPI. From cwhiteh at onetel.com Thu Mar 12 13:26:10 2009 From: cwhiteh at onetel.com (Chris Whitehouse) Date: Thu Mar 12 13:26:24 2009 Subject: is there a laptop ? In-Reply-To: References: <49B8498B.9080402@onetel.com> Message-ID: <49B96FDB.80105@onetel.com> Saifi Khan wrote: > On Wed, 11 Mar 2009, Chris Whitehouse wrote: > >> HP nc6320 (google RH383ET) - most things work, including wifi and ethernet, >> except for the following: >> > >>From HP site, > > Network > Integrated Broadcom NetLink Gigabit Ethernet PCI Controller > (10/100/1000 NIC) > > Wireless > Broadcom 802.11a/b/g; Broadcom 802.11b/g; Bluetooth 2.0 > > > It seems to have the US-trash-com chipset ! > > Do Atheros, Ralink, Realtek, Intel PRO/Wireless chipset work > with FreeBSD ? > > > thanks > Saifi. > What is the US-trash-com chipset and what makes it 'trash'? Is it poorly implemented hardware or problems with drivers? Or something else? This machine uses wpi and bge. Both devices seem to work ok chucking files around a domestic network. wpi0@pci0:8:0:0: class=0x028000 card=0x135c103c chip=0x42228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '10418086 Intel 3945ABG Wireless LAN controller' class = network bge0@pci0:2:14:0: class=0x020000 card=0x30aa103c chip=0x169c14e4 rev=0x03 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5788 Broadcom NetLink (TM) Gigabit Ethernet' class = network Chris From wojtek at wojtek.tensor.gdynia.pl Thu Mar 12 16:37:12 2009 From: wojtek at wojtek.tensor.gdynia.pl (Wojciech Puchar) Date: Thu Mar 12 16:37:25 2009 Subject: is there a laptop ? In-Reply-To: <49B96FDB.80105@onetel.com> References: <49B8498B.9080402@onetel.com> <49B96FDB.80105@onetel.com> Message-ID: > > This machine uses wpi and bge. Both devices seem to work ok chucking files > around a domestic network. at least for wired network i never had a problem with broadcom chips > > wpi0@pci0:8:0:0: class=0x028000 card=0x135c103c chip=0x42228086 > rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '10418086 Intel 3945ABG Wireless LAN controller' > class = network > bge0@pci0:2:14:0: class=0x020000 card=0x30aa103c chip=0x169c14e4 > rev=0x03 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5788 Broadcom NetLink (TM) Gigabit Ethernet' > class = network > > Chris > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > From maciej at suszko.eu Thu Mar 12 23:02:18 2009 From: maciej at suszko.eu (Maciej Suszko) Date: Thu Mar 12 23:02:25 2009 Subject: is there a laptop ? In-Reply-To: References: <49B8498B.9080402@onetel.com> <49B96FDB.80105@onetel.com> Message-ID: <20090313070208.2c1bef5f@suszko.eu> Wojciech Puchar wrote: > > > > This machine uses wpi and bge. Both devices seem to work ok > > chucking files around a domestic network. > > at least for wired network i never had a problem with broadcom chips Neither do I... > > > > wpi0@pci0:8:0:0: class=0x028000 card=0x135c103c > > chip=0x42228086 rev=0x02 hdr=0x00 > > vendor = 'Intel Corporation' > > device = '10418086 Intel 3945ABG Wireless LAN controller' > > class = network > > bge0@pci0:2:14:0: class=0x020000 card=0x30aa103c > > chip=0x169c14e4 rev=0x03 hdr=0x00 > > vendor = 'Broadcom Corporation' > > device = 'BCM5788 Broadcom NetLink (TM) Gigabit Ethernet' > > class = network > > > > Chris -- regards, Maciej Suszko. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090313/9697a988/signature.pgp From nevadadirren at gmail.com Fri Mar 13 16:23:33 2009 From: nevadadirren at gmail.com (Fabian Krook) Date: Fri Mar 13 16:23:41 2009 Subject: Xorg problem/ Nvidia drivers Message-ID: <50f801fe0903131600g66ee743fqe78042c746be1bbc@mail.gmail.com> Hello, it's so that i can't either start X because i don't any device that can fit in i tried look around on nvidia.com and on the ports which i found one but it was for Intel processors and i got an AMD which has an nvidia video card. So do you know where or what might be the problem in case i can send the error. % X -configure X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.1-RELEASE amd64 Current Operating System: FreeBSD Dolk.Belkin 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 11 March 2009 09:40:43PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 13 23:59:09 2009 List of video drivers: ati radeon intel i810 mach64 nv r128 radeonhd via vmware vesa vga No devices to configure. Configuration failed. % startx xauth: creating new authority file /root/.serverauth.29593 xauth: (argv):1: bad display name "Dolk.Belkin:0" in "list" command xauth: (stdin):1: bad display name "Dolk.Belkin:0" in "add" command X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.1-RELEASE amd64 Current Operating System: FreeBSD Dolk.Belkin 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Build Date: 11 March 2009 09:40:43PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 14 00:00:15 2009 (==) Using config file: "/etc/X11/xorg.conf" (EE) Failed to load module "nvidia" (module does not exist, 0) (EE) No drivers available. Fatal server error: no screens found waiting for X server to begin accepting connections giving up. xinit: Software caused connection abort (errno 53): unable to connect to X server xinit: No such process (errno 3): Server error. and i have set nvidia enable as an device. From prabu at hackinthebox.org Fri Mar 13 18:13:31 2009 From: prabu at hackinthebox.org (Praburaajan Selvarajan) Date: Fri Mar 13 18:13:39 2009 Subject: HITB2009 - Dubai: Conference Agenda & Noteworthy Presentations Message-ID: <49BAFE5F.3040805@hackinthebox.org> The agenda for HITBSecConf2009 - Dubai is now online along with details on both the conference keynote sessions. There are still another 4 more weeks to grab your seats to the GCC's premier network security event! Keynote 1 - Philippe Langlois (Founder, Qualys / Intrinsec / TSTF) "From Hacking, Startups to HackLabs: Global Perspective and New Fields" Keynote 2 - Mark Curphey (Director CISG, Microsoft Corp) "Security Cogs and Levers" Other noteworthy papers: # Cross Domain Leakiness: Divulging Sensitive Information and Attacking SSL Sessions - Chris Evans and Billy Rios # VBootKit 2.0 - Attacking Windows 7 via Boot Sectors - Vipin & Nitin Kumar # The Reverse Engineering Intermediate Language REIL and its Applications - Sebastian Porst # Pickpocketing mWallets: A Guide to Looting Mobile Financial Services - The Grugq # Psychotronica: Exposure, Control, and Deceit - Nitesh Dhanjani # NKill - The Internet Killboard - Anthony 'kugutsumen' Zboralski This is a new tool which gives attackers the ability to discover interesting relationships between seemingly unrelated hosts and companies and to pull vulnerable hosts for a specific domain, company or even an entire country! === Conference Agenda: http://conference.hackinthebox.org/hitbsecconf2009dubai/agenda.htm === On a related note, the conference videos from HITB2007 Malaysia that were previously available only through Bit Torrent are now available for streaming direct from Google Video: http://video.google.com/videosearch?q=HITBSecConf2007&emb=0&aq=f#q=HITBSecConf2007+Malaysia From prabu at hackinthebox.org Fri Mar 13 18:13:46 2009 From: prabu at hackinthebox.org (Praburaajan Selvarajan) Date: Fri Mar 13 18:13:52 2009 Subject: HITB2009 - Dubai: Conference Agenda & Noteworthy Presentations Message-ID: <49BAFE6F.9020907@hackinthebox.org> The agenda for HITBSecConf2009 - Dubai is now online along with details on both the conference keynote sessions. There are still another 4 more weeks to grab your seats to the GCC's premier network security event! Keynote 1 - Philippe Langlois (Founder, Qualys / Intrinsec / TSTF) "From Hacking, Startups to HackLabs: Global Perspective and New Fields" Keynote 2 - Mark Curphey (Director CISG, Microsoft Corp) "Security Cogs and Levers" Other noteworthy papers: # Cross Domain Leakiness: Divulging Sensitive Information and Attacking SSL Sessions - Chris Evans and Billy Rios # VBootKit 2.0 - Attacking Windows 7 via Boot Sectors - Vipin & Nitin Kumar # The Reverse Engineering Intermediate Language REIL and its Applications - Sebastian Porst # Pickpocketing mWallets: A Guide to Looting Mobile Financial Services - The Grugq # Psychotronica: Exposure, Control, and Deceit - Nitesh Dhanjani # NKill - The Internet Killboard - Anthony 'kugutsumen' Zboralski This is a new tool which gives attackers the ability to discover interesting relationships between seemingly unrelated hosts and companies and to pull vulnerable hosts for a specific domain, company or even an entire country! === Conference Agenda: http://conference.hackinthebox.org/hitbsecconf2009dubai/agenda.htm === On a related note, the conference videos from HITB2007 Malaysia that were previously available only through Bit Torrent are now available for streaming direct from Google Video: http://video.google.com/videosearch?q=HITBSecConf2007&emb=0&aq=f#q=HITBSecConf2007+Malaysia From henry.hu.sh at gmail.com Sat Mar 14 00:07:41 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Sat Mar 14 00:07:47 2009 Subject: Xorg problem/ Nvidia drivers In-Reply-To: <50f801fe0903131600g66ee743fqe78042c746be1bbc@mail.gmail.com> References: <50f801fe0903131600g66ee743fqe78042c746be1bbc@mail.gmail.com> Message-ID: <53a1e0710903132336x40db3e33he0514a2f9b777c5f@mail.gmail.com> Have you installed x11/nvidia-driver port? On Sat, Mar 14, 2009 at 7:00 AM, Fabian Krook wrote: > Hello, it's so that i can't either start X because i don't any device that > can fit in i tried look around on nvidia.com and on the ports which i found > one but it was for Intel processors and i got an AMD which has an nvidia > video card. So do you know where or what might be the problem in case i can > send the error. > > % X -configure > > X.Org X Server 1.4.2 > Release Date: 11 June 2008 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 7.1-RELEASE amd64 > Current Operating System: FreeBSD Dolk.Belkin 7.1-RELEASE FreeBSD > 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > amd64 > Build Date: 11 March 2009 09:40:43PM > > ?Before reporting problems, check http://wiki.x.org > ?to make sure that you have the latest version. > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > ?(++) from command line, (!!) notice, (II) informational, > ?(WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 13 23:59:09 2009 > List of video drivers: > ?ati > ?radeon > ?intel > ?i810 > ?mach64 > ?nv > ?r128 > ?radeonhd > ?via > ?vmware > ?vesa > ?vga > No devices to configure. Configuration failed. > > % startx > xauth: creating new authority file /root/.serverauth.29593 > xauth: (argv):1: bad display name "Dolk.Belkin:0" in "list" command > xauth: (stdin):1: bad display name "Dolk.Belkin:0" in "add" command > > > X.Org X Server 1.4.2 > Release Date: 11 June 2008 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 7.1-RELEASE amd64 > Current Operating System: FreeBSD Dolk.Belkin 7.1-RELEASE FreeBSD > 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > amd64 > Build Date: 11 March 2009 09:40:43PM > > ?Before reporting problems, check http://wiki.x.org > ?to make sure that you have the latest version. > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > ?(++) from command line, (!!) notice, (II) informational, > ?(WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 14 00:00:15 2009 > (==) Using config file: "/etc/X11/xorg.conf" > (EE) Failed to load module "nvidia" (module does not exist, 0) > (EE) No drivers available. > > Fatal server error: > no screens found > > waiting for X server to begin accepting connections > giving up. > xinit: Software caused connection abort (errno 53): unable to connect to X > server > xinit: No such process (errno 3): Server error. > > and i have set nvidia enable as an device. > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > From ivakras1 at gmail.com Sat Mar 14 00:16:54 2009 From: ivakras1 at gmail.com (=?koi8-r?b?5M3J1NLJyiDrz8zP08/X?=) Date: Sat Mar 14 00:17:00 2009 Subject: Xorg problem/ Nvidia drivers In-Reply-To: <50f801fe0903131600g66ee743fqe78042c746be1bbc@mail.gmail.com> References: <50f801fe0903131600g66ee743fqe78042c746be1bbc@mail.gmail.com> Message-ID: <200903141015.22834.ivakras1@gmail.com> On ??????? 14 ????? 2009 02:00:16 Fabian Krook wrote: > Hello, it's so that i can't either start X because i don't any device that > can fit in i tried look around on nvidia.com and on the ports which i found > one but it was for Intel processors and i got an AMD which has an nvidia > video card. So do you know where or what might be the problem in case i can > send the error. > > % X -configure > > X.Org X Server 1.4.2 > Release Date: 11 June 2008 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 7.1-RELEASE amd64 > Current Operating System: FreeBSD Dolk.Belkin 7.1-RELEASE FreeBSD > 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > amd64 > Build Date: 11 March 2009 09:40:43PM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Fri Mar 13 23:59:09 2009 > List of video drivers: > ati > radeon > intel > i810 > mach64 > nv > r128 > radeonhd > via > vmware > vesa > vga > No devices to configure. Configuration failed. > > % startx > xauth: creating new authority file /root/.serverauth.29593 > xauth: (argv):1: bad display name "Dolk.Belkin:0" in "list" command > xauth: (stdin):1: bad display name "Dolk.Belkin:0" in "add" command > > > X.Org X Server 1.4.2 > Release Date: 11 June 2008 > X Protocol Version 11, Revision 0 > Build Operating System: FreeBSD 7.1-RELEASE amd64 > Current Operating System: FreeBSD Dolk.Belkin 7.1-RELEASE FreeBSD > 7.1-RELEASE #0: Thu Jan 1 08:58:24 UTC 2009 > root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > amd64 > Build Date: 11 March 2009 09:40:43PM > > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 14 00:00:15 2009 > (==) Using config file: "/etc/X11/xorg.conf" > (EE) Failed to load module "nvidia" (module does not exist, 0) > (EE) No drivers available. > > Fatal server error: > no screens found > > waiting for X server to begin accepting connections > giving up. > xinit: Software caused connection abort (errno 53): unable to connect to X > server > xinit: No such process (errno 3): Server error. > > and i have set nvidia enable as an device. > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > In order to use nvidia video card set Driver "nv" in xorg.conf (no glx support) or `cd /usr/posts/x11/nvidia-driver; make install clean` and use Driver "nvidia" in xorg.conf with glx support. I have done it and now using nvidia8400gs with latest nvidia-driver - kde4.2.1 with compositing enabled (all effects used) very fast. From mobile at freebsd.org Sat Mar 14 18:03:35 2009 From: mobile at freebsd.org (jonnik1) Date: Sat Mar 14 18:03:42 2009 Subject: An e-card from jonnik1 for you Message-ID: <1951b1ef437ebfd935558b2a342a1fa1@www.lustmagazine.nl> An e-card from jonnik1 for you ========================================= To view the ecard, copy and paste this url into your browser's address bar:: http://www.lustmagazine.nl/partypics/displayecard.php?data=YTo5OntzOjI6InJuIjtzOjc6Impvbm5pazEiO3M6Mjoic24iO3M6Nzoiam9ubmlrMSI7czoyOiJzZSI7czoxODoibW9iaWxlQGZyZWVic2Qub3JnIjtzOjE6InAiO3M6OTM6Imh0dHA6Ly93d3cubHVzdG1hZ2F6aW5lLm5sL3BhcnR5cGljcy9hbGJ1bXMvMjAwNi8yMDA2MTExMV94dHJhbGFyZ2VyZXVuaW9uL25vcm1hbF9waWN0MDAxLmpwZyI7czoxOiJnIjtzOjk6InV4elJHUnR4WSI7czoxOiJtIjtzOjEyMzA6ImNvbW1lbnQ2LCBbdXJsPWh0dHA6Ly9ob21lLWJhc2VkLWJ1c2luZXNzLXdvcmxkLmNvbS9yc3NjYi9faW1hZ2VzL21pYW1pLWJveXotbW9kZWxzLW5hbWVzL2dhdGV3YXktbTY3NTAuaHRtbF1nYXRld2F5IG02NzUwWy91cmxdLCAgODYxOSwgW3VybD1odHRwOi8vaW50ZXJhY3Rpb25zY291bnNlbGluZy5jb20vZG93bmxvYWRzL19pbWFnZXMvcGl0YnVsbC1rZW5uZWwtc2V0dXAvZm9vZC1zaG9wcGluZy1mcmlnYXRlLWJheS1zdC1raXR0cy5odG1sXWZvb2Qgc2hvcHBpbmcgZnJpZ2F0ZSBiYXkgc3Qga2l0dHNbL3VybF0sICAxMjEzNywgW3VybD1odHRwOi8vcGhpbGJpcnRoLmNvbS9qYXNwZXJncmVlbmUvX2ltYWdlcy9lYXN5LXRvYWQtaW4tdGhlLWhvbGUtcmVjaXBlL2ZlbWNhbi1mYW50YXN5LXN0b3JpZXMuaHRtbF1mZW1jYW4gZmFudGFzeSBzdG9yaWVzWy91cmxdLCAgdGpjLCBbdXJsPWh0dHA6Ly9zdGlua3l idW5ueS5jb20vc3lscGhhci9faW1hZ2VzL29tYXItYWJkZWxrYWZpL2NyYWNrZXItYmFycmVsLWNoaWNrZW4tbi1yaWNlLXJlY2lwZS5odG1sXWNyYWNrZXIgYmFycmVsIGNoaWNrZW4gbiByaWNlIHJlY2lwZVsvdXJsXSwgIDM1NDQ0NiwgW3VybD1odHRwOi8vd3d3LnRjb3dib3lhcnRzLmNvbS9mcmFtZXdvcmsvX2ltYWdlcy9zYXJhaC1qYW5lLWhvbmV5d2VsbC1tYXJyaWVkL2Jlcm5hbGlsbG8tY291bnR5LWRldGVudGlvbi1jZW50ZXItaW5tYXRlLmh0bWxdYmVybmFsaWxsbyBjb3VudHkgZGV0ZW50aW9uIGNlbnRlciBpbm1hdGVbL3VybF0sICAwMjg3MjksIFt1cmw9aHR0cDovL3d3dy5kZXJhbmdlZHdpc3B5ZGVzaWduLmNvbS9zcGhlcml1bWdyb3VwL19pbWFnZXMvZGVmZXJyZWQtY29tcC1vaGlvLTQ1Ny1wbGFuL2Zvb2QtaW4tY29sb25pYWwtZ2VvcmdpYS5odG1sXWZvb2QgaW4gY29sb25pYWwgZ2VvcmdpYVsvdXJsXSwgICZndDs6RERELCBbdXJsPWh0dHA6Ly93d3cuZ2FyZGVudmFsbGV5cmV0aXJlbWVudHZpbGxhZ2UuY29tL05ld3NfZmlsZXMvX2ltYWdlcy9ub3J0b24tYW50aXZpcnVzLTIwMDYtdXBkYXRlci9yb3RpLXByYXRhLXJlY2lwZS5odG1sXXJvdGkgcHJhdGEgcmVjaXBlWy91cmxdLCAgJmd0OzpPTywgW3VybD1odHRwOi8vbm9ydGh0b25vcnRoLmNvbS9tYXloZW0vX2ltYWdlcy9wZXJsYS1mZXJyYXItaHVkc29uL2hpbGxiaWxseS1jYXJ0b29uLWdpZi5odG1sXWhpbGxiaWxseSBj YXJ0b29uIGdpZlsvdXJsXSwgIDhEREQsICI7czozOiJwaWQiO2k6NDtzOjI6InB0IjtzOjA6IiI7czoyOiJwYyI7czowOiIiO30%3D uxzRGRtxY comment6, [url=http://home-based-business-world.com/rsscb/_images/miami-boyz-models-names/gateway-m6750.html]gateway m6750[/url], 8619, [url=http://interactionscounseling.com/downloads/_images/pitbull-kennel-setup/food-shopping-frigate-bay-st-kitts.html]food shopping frigate bay st kitts[/url], 12137, [url=http://philbirth.com/jaspergreene/_images/easy-toad-in-the-hole-recipe/femcan-fantasy-stories.html]femcan fantasy stories[/url], tjc, [url=http://stinkybunny.com/sylphar/_images/omar-abdelkafi/cracker-barrel-chicken-n-rice-recipe.html]cracker barrel chicken n rice recipe[/url], 354446, [url=http://www.tcowboyarts.com/framework/_images/sarah-jane-honeywell-married/bernalillo-county-detention-center-inmate.html]bernalillo county detention center inmate[/url], 028729, [url=http://www.derangedwispydesign.com/spheriumgroup/_images/deferred-comp-ohio-457-plan/food-in-colonial-georgia.html]food in colonial georgia[/url], %3E:DDD, [url=http://www.gardenvalleyretirementvillage .com/News_files/_images/norton-antivirus-2006-updater/roti-prata-recipe.html]roti prata recipe[/url], %3E:OO, [url=http://northtonorth.com/mayhem/_images/perla-ferrar-hudson/hillbilly-cartoon-gif.html]hillbilly cartoon gif[/url], 8DDD, jonnik1 (mobile@freebsd.org) ----------------------------------------- View more pictures !: http://www.lustmagazine.nl/partypics/ From robyn at 116street.com Sat Mar 14 19:36:03 2009 From: robyn at 116street.com (robyn@116street.com) Date: Sat Mar 14 19:36:08 2009 Subject: Your link has expired - please re-submit Message-ID: <20090315023602.61475.qmail@www.maneworldserver.com> Hi, Your link has expired. Please go back to www.116street.com/ffa to re-submit your link. Here are some more programs for getting more traffic: Vinyl Magnetic Signs Removable Bullitin Boards only $30 each ======================================= www.vinyl-decals.com ======================================= Domain Name Decals for your vehicle 2 Stickers for only $10.00 FREE SHIPPING! Vehicle decals can produce up to 1800 impressions daily! That's FREE Advertising! ======================================= www.vinyl-decals.com ======================================= Web Masters Best Kept Secret ! Make 1000's of doorway web pages in 30 seconds ! http://www.boost-web-site-traffic.com =========================================== From onemda at gmail.com Wed Mar 18 03:17:14 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Wed Mar 18 03:17:26 2009 Subject: is there a laptop ? In-Reply-To: <1237368919.4549.36.camel@slate1> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> <1237368919.4549.36.camel@slate1> Message-ID: <3a142e750903180317t71bd142cyc8c76a707a943041@mail.gmail.com> On 3/18/09, Gary Dunn wrote: > On Thu, 2009-03-12 at 18:53 +0100, Paul B. Mahol wrote: >> On 3/13/09, Saifi Khan wrote: >> > On Thu, 12 Mar 2009, Maciej Suszko wrote: >> > >> >> Saifi Khan wrote: >> >> > Hi all: >> >> > >> >> > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use >> >> > ndiswrapper, or broadcom or additional PCMCIA card at all. >> >> > >> >> > Is there a laptop model (available in market) that experienced >> >> > members would like to recommend wherein >> >> > . the WiFi 802.11 a/g (PCI based) >> >> > . Ethernet port >> >> > . and ACPI >> >> > work absolutely fine with FreeBSD 7.x ? >> >> >> >> I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried the >> >> suspend/resume, firewire port and I suppose the modem is not >> >> going to work. Everything else is working fine for me. >> >> -- >> >> regards, Maciej Suszko. >> >> >> > >> > What is the wireless chipset of your machine ? >> >> On mine nx7300 it is broadcom one and works fine via ndis. >> Suspend/resume works fine if second core is disabled and vesa is >> loaded in kernel >> (either via kldload or via custom kernel) >> Firewire and bluetooth are supported and should work without problems. >> Ethernet works via if_bfe; carbus, drm, sound works fine ... >> In short everything is supported on UP kernel except winmodem. >> >> There are some bugs in BIOS asl which I fixed adding: >> >> acpi_dsdt_load="YES" >> acpi_dsdt_name="/boot/acpi.aml" >> >> in /boot/loader.conf >> >> /boot/acpi.aml is modified version of ASL which address "temperature >> is absurd, ignored" >> type of messages. >> >> >> 8.0 CURRENT i386. >> > > Lots of interesting stuff in this thread. I am running 7.1 and Gnome > 2.22 on a Fujitsu T1010. (More at http://wiki.openslate.net) My > experience seems typical, most things work. Issues: > > o Suspend/Resume does not work > > o With powerd configured CPU speed happily throttles up and down > automatically, greatly extending battery life > > o X mouse pointer is usually a square of random noise pixels -- > looks weird but works fine Enable soft cursor in /etc/X11/xorg.conf: Option "SWcursor" "1" inside Device Section. You didn't said what video driver. > > o Built-in WiFi does not work; I use an old Orinoco Gold PC-card, wi > driver works fine it may work with ndisulator(ndisgen(8)) > > o Some thumb drives mount fine, some do not, some mount but do not > unmount. They all work fine in Vista :-( > > o Cannot mount a Sony PCM-D50 digital audio recorder, which works > fine in Vista :-( > > o The Linux-Wacom driver (http://linuxwacom.sourceforge.net/) does > not see the built-in digitizer > > Apparently HEAD == 8.0 CURRENT; I may move up to that to see what is > better. However, running CURRENT is not for the faint of heart. > > Questions: > > 1. Has the SMP issue with ACPI been fixed in HEAD? Not for me, but UP still works. > 2. How does one disable the second CPU? "set kern.smp.disabled=1" from loader prompt or "kern.smp.disabled=1" line in /boot/loader.conf > > 3. ACPI includes commands that be configured to run going into and > coming out of suspend. Can these be used to turn the second CPU off and > on? > > -- > Gary Dunn, Honolulu > osp@aloha.com > http://openslate.net/ > http://e9erust.blogspot.com/ > Sent from Slate001 > > -- Paul From knowtree at aloha.com Wed Mar 18 03:33:57 2009 From: knowtree at aloha.com (Gary Dunn) Date: Wed Mar 18 03:34:03 2009 Subject: is there a laptop ? In-Reply-To: <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> Message-ID: <1237368919.4549.36.camel@slate1> On Thu, 2009-03-12 at 18:53 +0100, Paul B. Mahol wrote: > On 3/13/09, Saifi Khan wrote: > > On Thu, 12 Mar 2009, Maciej Suszko wrote: > > > >> Saifi Khan wrote: > >> > Hi all: > >> > > >> > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > >> > ndiswrapper, or broadcom or additional PCMCIA card at all. > >> > > >> > Is there a laptop model (available in market) that experienced > >> > members would like to recommend wherein > >> > . the WiFi 802.11 a/g (PCI based) > >> > . Ethernet port > >> > . and ACPI > >> > work absolutely fine with FreeBSD 7.x ? > >> > >> I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried the > >> suspend/resume, firewire port and I suppose the modem is not > >> going to work. Everything else is working fine for me. > >> -- > >> regards, Maciej Suszko. > >> > > > > What is the wireless chipset of your machine ? > > On mine nx7300 it is broadcom one and works fine via ndis. > Suspend/resume works fine if second core is disabled and vesa is > loaded in kernel > (either via kldload or via custom kernel) > Firewire and bluetooth are supported and should work without problems. > Ethernet works via if_bfe; carbus, drm, sound works fine ... > In short everything is supported on UP kernel except winmodem. > > There are some bugs in BIOS asl which I fixed adding: > > acpi_dsdt_load="YES" > acpi_dsdt_name="/boot/acpi.aml" > > in /boot/loader.conf > > /boot/acpi.aml is modified version of ASL which address "temperature > is absurd, ignored" > type of messages. > > > 8.0 CURRENT i386. > Lots of interesting stuff in this thread. I am running 7.1 and Gnome 2.22 on a Fujitsu T1010. (More at http://wiki.openslate.net) My experience seems typical, most things work. Issues: o Suspend/Resume does not work o With powerd configured CPU speed happily throttles up and down automatically, greatly extending battery life o X mouse pointer is usually a square of random noise pixels -- looks weird but works fine o Built-in WiFi does not work; I use an old Orinoco Gold PC-card, wi driver works fine o Some thumb drives mount fine, some do not, some mount but do not unmount. They all work fine in Vista :-( o Cannot mount a Sony PCM-D50 digital audio recorder, which works fine in Vista :-( o The Linux-Wacom driver (http://linuxwacom.sourceforge.net/) does not see the built-in digitizer Apparently HEAD == 8.0 CURRENT; I may move up to that to see what is better. However, running CURRENT is not for the faint of heart. Questions: 1. Has the SMP issue with ACPI been fixed in HEAD? 2. How does one disable the second CPU? 3. ACPI includes commands that be configured to run going into and coming out of suspend. Can these be used to turn the second CPU off and on? -- Gary Dunn, Honolulu osp@aloha.com http://openslate.net/ http://e9erust.blogspot.com/ Sent from Slate001 From jnordwick at gmail.com Thu Mar 19 18:53:39 2009 From: jnordwick at gmail.com (Jason Nordwick) Date: Thu Mar 19 18:53:46 2009 Subject: Cannot get Intel/Pro Wireless 3945ABG to work Message-ID: <8D9D8FAF-F0E6-4161-9A92-CCCDDE1DC456@gmail.com> I just installed (after a multiyear hiatus of FreeBSD) on my laptop, but I can't get the wireless to work. I have 4 net devices listed): bfe0, fwe0, fwip0, and lo0. Is fwip the device I want to interact with? When I do an ifconfig fwip0 up scan, I get "unable to get scan results" returned immediately. Makes me think there is some kmod than I'm missing? Thanks, J. From davidb at boothscientific.com Thu Mar 19 19:34:14 2009 From: davidb at boothscientific.com (David Booth) Date: Thu Mar 19 19:34:20 2009 Subject: Cannot get Intel/Pro Wireless 3945ABG to work In-Reply-To: <8D9D8FAF-F0E6-4161-9A92-CCCDDE1DC456@gmail.com> References: <8D9D8FAF-F0E6-4161-9A92-CCCDDE1DC456@gmail.com> Message-ID: <200903192059.53577.davidb@boothscientific.com> On Thursday 19 March 2009, Jason Nordwick wrote: > I just installed (after a multiyear hiatus of FreeBSD) on my > laptop, but I can't get the wireless to work. > > I have 4 net devices listed): bfe0, fwe0, fwip0, and lo0. Is fwip > the device I want to interact with? When I do an ifconfig fwip0 up > scan, I get "unable to get scan results" returned immediately. > Makes me think there is some kmod than I'm missing? > > Thanks, J. > > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to > "freebsd-mobile-unsubscribe@freebsd.org" You need the wpi driver. See man wpi for instructions. From chuckop at gmail.com Thu Mar 19 23:53:35 2009 From: chuckop at gmail.com (Charles Oppermann) Date: Thu Mar 19 23:53:41 2009 Subject: Cannot get Intel/Pro Wireless 3945ABG to work In-Reply-To: <8D9D8FAF-F0E6-4161-9A92-CCCDDE1DC456@gmail.com> References: <8D9D8FAF-F0E6-4161-9A92-CCCDDE1DC456@gmail.com> Message-ID: <200903192331.08612.chuckop@gmail.com> On Thursday 19 March 2009 06:27:06 pm Jason Nordwick wrote: > I just installed (after a multiyear hiatus of FreeBSD) on my laptop, > but I can't get the wireless to work. > I have 4 net devices listed): bfe0, fwe0, fwip0, and lo0. Is fwip the > device I want to interact with? I'm curious, what brand laptop is this on? The fwip0 device is the IP-over-Firewire adapter. I haven't found a use for that yet. The correct driver is wpi, read the wpi(4) man page for details and the changes you have to make to /boot/loader.conf to get the device recognized: man 4 wpi Good luck! From dougb at FreeBSD.org Fri Mar 20 00:15:36 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Mar 20 00:15:42 2009 Subject: Cannot get Intel/Pro Wireless 3945ABG to work In-Reply-To: <8D9D8FAF-F0E6-4161-9A92-CCCDDE1DC456@gmail.com> References: <8D9D8FAF-F0E6-4161-9A92-CCCDDE1DC456@gmail.com> Message-ID: On Thu, 19 Mar 2009, Jason Nordwick wrote: > I just installed (after a multiyear hiatus of FreeBSD) on my laptop, but I > can't get the wireless to work. Welcome back. :) You didn't mention what version you're using, but 'man wpi' should get you the information you want. Assuming you're using at least version 7.1 (and you should be) be sure to pay attention to the information about wlan, that's a big change to our wireless networking in the past couple years. Good luck, Doug -- This .signature sanitized for your protection From jnordwick at gmail.com Fri Mar 20 09:01:07 2009 From: jnordwick at gmail.com (Jason Nordwick) Date: Fri Mar 20 09:01:14 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( Message-ID: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> Thanks for all the help. The problem was just that I couldn't figure out which device I needed to use and the information to turn on the device was in the man page that I didn't know about because it wasn't listed in the device output. Doh. Thank you everybody for your help. It all works now (except I still find it clunky to manage the networks I want to join, but I figure I'll find something out there to help with that or be able to write a script to do it). Now, I just have speed issues. For example, right now I am trying to install some ports, but maxing out the download at about 4-6 k/sec. Did I not include wpi0.makefast="YES" or something? -j From knowtree at aloha.com Fri Mar 20 17:56:49 2009 From: knowtree at aloha.com (Gary Dunn) Date: Fri Mar 20 17:56:59 2009 Subject: is there a laptop ? In-Reply-To: <3a142e750903180317t71bd142cyc8c76a707a943041@mail.gmail.com> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> <1237368919.4549.36.camel@slate1> <3a142e750903180317t71bd142cyc8c76a707a943041@mail.gmail.com> Message-ID: <1237596976.1520.19.camel@slate1> On Wed, 2009-03-18 at 11:17 +0100, Paul B. Mahol wrote: > On 3/18/09, Gary Dunn wrote: > > On Thu, 2009-03-12 at 18:53 +0100, Paul B. Mahol wrote: > >> On 3/13/09, Saifi Khan wrote: > >> > On Thu, 12 Mar 2009, Maciej Suszko wrote: > >> > > >> >> Saifi Khan wrote: > >> >> > Hi all: > >> >> > > >> >> > i've looked at tuxmobil, bsdgroup.de etc and i don't want to use > >> >> > ndiswrapper, or broadcom or additional PCMCIA card at all. > >> >> > > >> >> > Is there a laptop model (available in market) that experienced > >> >> > members would like to recommend wherein > >> >> > . the WiFi 802.11 a/g (PCI based) > >> >> > . Ethernet port > >> >> > . and ACPI > >> >> > work absolutely fine with FreeBSD 7.x ? > >> >> > >> >> I use RELENG_7_1 and RELENG_7 on HP Compaq nx7300. I haven't tried the > >> >> suspend/resume, firewire port and I suppose the modem is not > >> >> going to work. Everything else is working fine for me. > >> >> -- > >> >> regards, Maciej Suszko. > >> >> > >> > > >> > What is the wireless chipset of your machine ? > >> > >> On mine nx7300 it is broadcom one and works fine via ndis. > >> Suspend/resume works fine if second core is disabled and vesa is > >> loaded in kernel > >> (either via kldload or via custom kernel) > >> Firewire and bluetooth are supported and should work without problems. > >> Ethernet works via if_bfe; carbus, drm, sound works fine ... > >> In short everything is supported on UP kernel except winmodem. > >> > >> There are some bugs in BIOS asl which I fixed adding: > >> > >> acpi_dsdt_load="YES" > >> acpi_dsdt_name="/boot/acpi.aml" > >> > >> in /boot/loader.conf > >> > >> /boot/acpi.aml is modified version of ASL which address "temperature > >> is absurd, ignored" > >> type of messages. > >> > >> > >> 8.0 CURRENT i386. > >> > > > > Lots of interesting stuff in this thread. I am running 7.1 and Gnome > > 2.22 on a Fujitsu T1010. (More at http://wiki.openslate.net) My > > experience seems typical, most things work. Issues: > > > > o Suspend/Resume does not work > > > > o With powerd configured CPU speed happily throttles up and down > > automatically, greatly extending battery life > > > > o X mouse pointer is usually a square of random noise pixels -- > > looks weird but works fine > > Enable soft cursor in /etc/X11/xorg.conf: > Option "SWcursor" "1" > inside Device Section. > > You didn't said what video driver. Thank you for your suggestions. I tried setting SWcursor to "1" and "True" but neither was a solution. The behavior changed from a neat square of rippling bits about the same size as a desktop icon that moved with the mouse, to a fully formed, proper mouse pointer AND a steady stream of random bits spewed across the screen. The more I moved the mouse the more bits appeared, threatening to obliterate the entire desktop! Almost a new kind of desktop accessory .. cloud computing! Below is my complete /usr/local/etc/X11/xorg.conf. The wacom stuff is for my unrecognized touch screen. The video problem was present from day one, before I installed the linux-wacom driver. After that I have included a big chunk from /var/log/Xorg.0.log. I tried to limit it to just the Intel video chip stuff. Complete and contiguous within this portion of the log file. I do not have enough experience with X to recognize a problem. Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "stylus" "SendCoreEvents" InputDevice "eraser" "SendCoreEvents" InputDevice "cursor" "SendCoreEvents" InputDevice "pad" "SendCoreEvents" InputDevice "touch" "SendCoreEvents" EndSection Section "Files" RgbPath "/usr/local/share/X11/rgb" ModulePath "/usr/local/lib/xorg/modules" FontPath "/usr/local/lib/X11/fonts/misc/" FontPath "/usr/local/lib/X11/fonts/TTF/" FontPath "/usr/local/lib/X11/fonts/OTF" FontPath "/usr/local/lib/X11/fonts/Type1/" FontPath "/usr/local/lib/X11/fonts/100dpi/" FontPath "/usr/local/lib/X11/fonts/75dpi/" EndSection Section "Module" Load "extmod" Load "record" Load "dbe" Load "glx" Load "GLcore" Load "xtrap" Load "dri" Load "freetype" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [] #Option "SWcursor" # [] #Option "ColorKey" # #Option "CacheLines" # #Option "Dac6Bit" # [] #Option "DRI" # [] #Option "NoDDC" # [] #Option "ShowCache" # [] #Option "XvMCSurfaces" # #Option "PageFlip" # [] Identifier "Card0" Driver "intel" VendorName "Intel Corporation" BoardName "Mobile Integrated Graphics Controller" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "InputDevice" Driver "wacom" Identifier "stylus" Option "Device" "/dev/event0" Option "Type" "stylus" Option "USB" "on" Option "ForceDevice" "ISDV4" EndSection Section "InputDevice" Driver "wacom" Identifier "eraser" Option "Device" "/dev/event0" Option "Type" "eraser" Option "USB" "on" Option "ForceDevice" "ISDV4" EndSection Section "InputDevice" Driver "wacom" Identifier "cursor" Option "Device" "/dev/event0" Option "Type" "cursor" Option "USB" "on" Option "ForceDevice" "ISDV4" EndSection Section "InputDevice" Driver "wacom" Identifier "pad" Option "Device" "/dev/event0" Option "Type" "pad" Option "USB" "on" Option "ForceDevice" "ISDV4" EndSection Section "InputDevice" Driver "wacom" Identifier "touch" Option "Device" "/dev/event0" Option "Type" "touch" Option "USB" "on" Option "ForceDevice" "ISDV4" EndSection =-=-=-=-= (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, Mobile Intel? GM45 Express Chipset, Intel Integrated Graphics Device, G45/G43, Q45/Q43 (II) Primary Device is: PCI 00:02:0 (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) Chipset Mobile Intel? GM45 Express Chipset found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf2701000 - 0xf2701fff (0x1000) MX[B]E [5] -1 0 0xf2700000 - 0xf2700fff (0x1000) MX[B]E [6] -1 0 0xf2600000 - 0xf26fffff (0x100000) MX[B]E [7] -1 0 0xf2500000 - 0xf25fffff (0x100000) MX[B]E [8] -1 0 0xf2a04000 - 0xf2a047ff (0x800) MX[B]E [9] -1 0 0xf2a04c00 - 0xf2a04fff (0x400) MX[B]E [10] -1 0 0xf2a00000 - 0xf2a03fff (0x4000) MX[B]E [11] -1 0 0xf2a04800 - 0xf2a04bff (0x400) MX[B]E [12] -1 0 0xf2400000 - 0xf24fffff (0x100000) MX[B](B) [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [14] -1 0 0xf2000000 - 0xf23fffff (0x400000) MX[B](B) [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [17] -1 0 0x00002000 - 0x000020ff (0x100) IX[B]E [18] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [19] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]E [20] -1 0 0x00001808 - 0x0000180b (0x4) IX[B]E [21] -1 0 0x00001810 - 0x00001817 (0x8) IX[B]E [22] -1 0 0x0000180c - 0x0000180f (0x4) IX[B]E [23] -1 0 0x00001818 - 0x0000181f (0x8) IX[B]E [24] -1 0 0x000018c0 - 0x000018df (0x20) IX[B]E [25] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]E [26] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]E [27] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [28] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]E [29] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [30] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) resource ranges after probing: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf2701000 - 0xf2701fff (0x1000) MX[B]E [5] -1 0 0xf2700000 - 0xf2700fff (0x1000) MX[B]E [6] -1 0 0xf2600000 - 0xf26fffff (0x100000) MX[B]E [7] -1 0 0xf2500000 - 0xf25fffff (0x100000) MX[B]E [8] -1 0 0xf2a04000 - 0xf2a047ff (0x800) MX[B]E [9] -1 0 0xf2a04c00 - 0xf2a04fff (0x400) MX[B]E [10] -1 0 0xf2a00000 - 0xf2a03fff (0x4000) MX[B]E [11] -1 0 0xf2a04800 - 0xf2a04bff (0x400) MX[B]E [12] -1 0 0xf2400000 - 0xf24fffff (0x100000) MX[B](B) [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [14] -1 0 0xf2000000 - 0xf23fffff (0x400000) MX[B](B) [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [20] -1 0 0x00002000 - 0x000020ff (0x100) IX[B]E [21] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [22] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]E [23] -1 0 0x00001808 - 0x0000180b (0x4) IX[B]E [24] -1 0 0x00001810 - 0x00001817 (0x8) IX[B]E [25] -1 0 0x0000180c - 0x0000180f (0x4) IX[B]E [26] -1 0 0x00001818 - 0x0000181f (0x8) IX[B]E [27] -1 0 0x000018c0 - 0x000018df (0x20) IX[B]E [28] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]E [29] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]E [30] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [31] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]E [32] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [33] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) [34] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [35] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/local/lib/xorg/modules//libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/local/lib/xorg/modules//libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.1.0 ABI class: X.Org Video Driver, version 2.0 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/local/lib/xorg/modules//libvgahw.so (II) Module vgahw: vendor="X.Org Foundation" compiled for 1.4.2, module version = 0.1.0 ABI class: X.Org Video Driver, version 2.0 (==) intel(0): Depth 24, (==) framebuffer bpp 32 (==) intel(0): RGB weight 888 (==) intel(0): Default visual is TrueColor (II) intel(0): Integrated Graphics Chipset: Intel(R) Mobile Intel? GM45 Express Chipset (--) intel(0): Chipset: "Mobile Intel? GM45 Express Chipset" (--) intel(0): Linear framebuffer at 0xD0000000 (--) intel(0): IO registers at addr 0xF2000000 (==) intel(0): Write-combining range (0xf2000000,0x80000) was already clear (==) intel(0): Write-combining range (0xf2200000,0x200000) was already clear (II) intel(0): 2 display pipes available. (==) intel(0): Using EXA for acceleration (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/local/lib/xorg/modules//libint10.so (II) intel(0): initializing int10 (==) intel(0): Write-combining range (0xa0000,0x20000) was already clear (==) intel(0): Write-combining range (0xc0000,0x40000) was already clear (WW) intel(0): Bad V_BIOS checksum (II) intel(0): Primary V_BIOS segment is: 0xc000 (==) intel(0): Write-combining range (0x0,0x1000) was already clear (II) intel(0): VESA BIOS detected (II) intel(0): VESA VBE Version 3.0 (II) intel(0): VESA VBE Total Mem: 32704 kB (II) intel(0): VESA VBE OEM: Intel(r)Cantiga Graphics Chip Accelerated VGA BIOS (II) intel(0): VESA VBE OEM Software Rev: 1.0 (II) intel(0): VESA VBE OEM Vendor: Intel Corporation (II) intel(0): VESA VBE OEM Product: Intel(r)Cantiga Graphics Controller (II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0 (==) intel(0): Write-combining range (0x0,0x1000) was already clear (II) Loading sub module "ddc" (II) LoadModule: "ddc"(II) Module "ddc" already built-in (II) Loading sub module "i2c" (II) LoadModule: "i2c"(II) Module "i2c" already built-in (II) intel(0): Output VGA using monitor section Monitor0 (II) intel(0): I2C bus "CRTDDC_A" initialized. (II) intel(0): Output LVDS has no monitor section (II) intel(0): I2C bus "LVDSDDC_C" initialized. (II) intel(0): Attempting to determine panel fixed mode. (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): I2C device "LVDSDDC_C:ddc2" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70. (II) intel(0): No SDVO device found on SDVOB (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed. (II) intel(0): Output HDMI-1 has no monitor section (II) intel(0): I2C bus "HDMIDDC_B" initialized. (II) intel(0): HDMI output 1 detected (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72. (II) intel(0): No SDVO device found on SDVOC (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed. (II) intel(0): Output HDMI-2 has no monitor section (II) intel(0): I2C bus "HDMIDDC_C" initialized. (II) intel(0): HDMI output 2 detected (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): I2C device "LVDSDDC_C:ddc2" removed. (II) intel(0): Output VGA disconnected (II) intel(0): Output LVDS connected (II) intel(0): Output HDMI-1 disconnected (II) intel(0): Output HDMI-2 disconnected (II) intel(0): Output LVDS using initial mode 1280x800 (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear (II) intel(0): Monitoring connected displays enabled (II) intel(0): detected 512 kB GTT. (II) intel(0): detected 32252 kB stolen memory. (==) intel(0): video overlay key set to 0x101fe (==) intel(0): Will not try to enable page flipping (==) intel(0): Triple buffering disabled (==) intel(0): Intel XvMC decoder disabled (==) intel(0): Using gamma correction (1.0, 1.0, 1.0) (==) intel(0): DPI set to (96, 96) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/local/lib/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (II) Loading sub module "exa" (II) LoadModule: "exa" (II) Loading /usr/local/lib/xorg/modules//libexa.so (II) Module exa: vendor="X.Org Foundation" compiled for 1.4.2, module version = 2.2.0 ABI class: X.Org Video Driver, version 2.0 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac"(II) Module "ramdac" already built-in (II) intel(0): Comparing regs from server start up to After PreInit (WW) intel(0): Register 0x61200 (PP_STATUS) changed from 0xc0000008 to 0xd0000009 (WW) intel(0): PP_STATUS before: on, ready, sequencing idle (WW) intel(0): PP_STATUS after: on, ready, sequencing on (WW) intel(0): Register 0x321b (FBC_FENCE_OFF) changed from 0xa5002500 to 0x3a000a00 (==) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xd0000000 - 0xdfffffff (0x10000000) MS[B] [1] 0 0 0xf2000000 - 0xf23fffff (0x400000) MS[B] [2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [6] -1 0 0xf2701000 - 0xf2701fff (0x1000) MX[B]E [7] -1 0 0xf2700000 - 0xf2700fff (0x1000) MX[B]E [8] -1 0 0xf2600000 - 0xf26fffff (0x100000) MX[B]E [9] -1 0 0xf2500000 - 0xf25fffff (0x100000) MX[B]E [10] -1 0 0xf2a04000 - 0xf2a047ff (0x800) MX[B]E [11] -1 0 0xf2a04c00 - 0xf2a04fff (0x400) MX[B]E [12] -1 0 0xf2a00000 - 0xf2a03fff (0x4000) MX[B]E [13] -1 0 0xf2a04800 - 0xf2a04bff (0x400) MX[B]E [14] -1 0 0xf2400000 - 0xf24fffff (0x100000) MX[B](B) [15] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [16] -1 0 0xf2000000 - 0xf23fffff (0x400000) MX[B](B) [17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [20] 0 0 0x00001800 - 0x00001807 (0x8) IS[B] [21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [22] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [23] -1 0 0x00002000 - 0x000020ff (0x100) IX[B]E [24] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [25] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B]E [26] -1 0 0x00001808 - 0x0000180b (0x4) IX[B]E [27] -1 0 0x00001810 - 0x00001817 (0x8) IX[B]E [28] -1 0 0x0000180c - 0x0000180f (0x4) IX[B]E [29] -1 0 0x00001818 - 0x0000181f (0x8) IX[B]E [30] -1 0 0x000018c0 - 0x000018df (0x20) IX[B]E [31] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B]E [32] -1 0 0x00001880 - 0x0000189f (0x20) IX[B]E [33] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [34] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]E [35] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [36] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) [37] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [38] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) (WW) intel(0): /dev/agpgart is either not available, or no memory is available for allocation. Using pre-allocated memory only. drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: Searching for BusID pci:0000:00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card2 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card3 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card4 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card5 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card6 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card7 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card8 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card9 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card10 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card11 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card12 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card13 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card14 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed drmOpenByBusid: drmOpenMinor returns -2 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: open result is -1, (No such file or directory) drmOpenDevice: Open failed [drm] failed to load kernel module "i915" (EE) [drm] drmOpen failed. (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI. (**) intel(0): Framebuffer compression enabled (**) intel(0): Tiling enabled (==) intel(0): Write-combining range (0xf2000000,0x80000) was already clear (==) intel(0): Write-combining range (0xf2200000,0x200000) was already clear (==) intel(0): VideoRam: 32252 KB (II) intel(0): Attempting memory allocation with tiled buffers. (II) intel(0): Tiled allocation successful. (--) intel(0): Xv is disabled because it needs 2D accel and AGPGART. (II) intel(0): Page Flipping disabled (==) intel(0): Write-combining range (0xf2000000,0x80000) was already clear (==) intel(0): Write-combining range (0xf2200000,0x200000) was already clear (==) intel(0): Write-combining range (0xd0000000,0x10000000) (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (==) intel(0): Write-combining range (0xa0000,0x10000) was already clear (II) EXA(0): Offscreen pixmap area of 19660800 bytes (II) EXA(0): Driver registered support for the following operations: (II) Solid (II) Copy (II) Composite (RENDER acceleration) (==) intel(0): Backing store disabled (==) intel(0): Silken mouse enabled (II) intel(0): Initializing HW Cursor (II) intel(0): Fixed memory allocation layout: (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB) (II) intel(0): 0x00020000-0x00083fff: compressed frame buffer (400 kB, 0x000000007e020000 physical ) (II) intel(0): 0x00084000-0x0008dfff: HW cursors (40 kB) (II) intel(0): 0x0008e000-0x00095fff: logical 3D context (32 kB) (II) intel(0): 0x00096000-0x000a7fff: exa G965 state buffer (72 kB) (II) intel(0): 0x000a8000-0x000a8fff: power context (4 kB) (II) intel(0): 0x00100000-0x0073ffff: front buffer (6400 kB) X tiled (II) intel(0): 0x00740000-0x019fffff: exa offscreen (19200 kB) (II) intel(0): 0x10000000: end of aperture (WW) intel(0): PGTBL_CTL (0x00000000) indicates GTT is disabled (WW) intel(0): Existing errors found in hardware state. (II) intel(0): using SSC reference clock of 96 MHz (II) intel(0): Selecting standard 18 bit TMDS pixel format. (II) intel(0): Output configuration: (II) intel(0): Pipe A is off (II) intel(0): Display plane A is now disabled and connected to pipe A. (II) intel(0): Pipe B is on (II) intel(0): Display plane B is now enabled and connected to pipe B. (II) intel(0): Output VGA is connected to pipe none (II) intel(0): Output LVDS is connected to pipe B (II) intel(0): Output HDMI-1 is connected to pipe none (II) intel(0): Output HDMI-2 is connected to pipe none (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. (II) intel(0): using SSC reference clock of 96 MHz (II) intel(0): Selecting standard 18 bit TMDS pixel format. (II) intel(0): direct rendering: Failed (--) RandR disabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension XAccessControlExtension (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/local/lib/xorg/modules/extensions//libGLcore.so (II) Module GLcore: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) GLX: Initialized MESA-PROXY GL provider for screen 0 (II) intel(0): Setting screen physical size to 338 x 211 =-=-=-=-= Thanks again! -- Gary Dunn, Honolulu osp@aloha.com http://openslate.net/ http://e9erust.blogspot.com/ Sent from Slate001 From dougb at FreeBSD.org Fri Mar 20 22:13:07 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Fri Mar 20 22:13:13 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> Message-ID: <49C4775A.4060206@FreeBSD.org> Jason Nordwick wrote: > Thanks for all the help. The problem was just that I couldn't figure out > which device I needed to use and the information to turn on the device > was in the man page that I didn't know about because it wasn't listed in > the device output. Doh. > > Thank you everybody for your help. It all works now (except I still find > it clunky to manage the networks I want to join, but I figure I'll find > something out there to help with that or be able to write a script to do > it). > > Now, I just have speed issues. For example, right now I am trying to > install some ports, but maxing out the download at about 4-6 k/sec. Did > I not include wpi0.makefast="YES" or something? It's impossible to help you diagnose this without a lot more information. What version of FreeBSD are you using? What settings do you have in rc.conf and (if appropriate) /etc/wpa_supplicant.conf? Have you tried the same card with the same AP(s) with another operating system? I have this same card and it works quite well in both FreeBSD and Windows in 11g mode with my Linksys WRT54G AP on 8-current. hth, Doug From onemda at gmail.com Sat Mar 21 04:36:21 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Sat Mar 21 04:36:27 2009 Subject: is there a laptop ? In-Reply-To: <1237596976.1520.19.camel@slate1> References: <49b94250.0c11660a.248d.ffffa80e@mx.google.com> <3a142e750903121053j7f1c4b08tbcd31f8a6d78fd52@mail.gmail.com> <1237368919.4549.36.camel@slate1> <3a142e750903180317t71bd142cyc8c76a707a943041@mail.gmail.com> <1237596976.1520.19.camel@slate1> Message-ID: <3a142e750903210436y1d75b220xe190f664857705b1@mail.gmail.com> On 3/21/09, Gary Dunn wrote: > #Option "NoAccel" # [] Change this one to: Option "NoAccel" "1" > #Option "SWcursor" # [] > #Option "ColorKey" # > #Option "CacheLines" # > #Option "Dac6Bit" # [] > #Option "DRI" # [] and this one to: Option "DRI" "0" > #Option "NoDDC" # [] > #Option "ShowCache" # [] > #Option "XvMCSurfaces" # > #Option "PageFlip" # [] > Identifier "Card0" > Driver "intel" > VendorName "Intel Corporation" > BoardName "Mobile Integrated Graphics Controller" > BusID "PCI:0:2:0" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "Card0" > Monitor "Monitor0" > SubSection "Display" > Viewport 0 0 > Depth 1 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 4 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 8 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 15 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 16 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 24 > EndSubSection > EndSection > > Section "InputDevice" > Driver "wacom" > Identifier "stylus" > Option "Device" "/dev/event0" > Option "Type" "stylus" > Option "USB" "on" > Option "ForceDevice" "ISDV4" > EndSection > > Section "InputDevice" > Driver "wacom" > Identifier "eraser" > Option "Device" "/dev/event0" > Option "Type" "eraser" > Option "USB" "on" > Option "ForceDevice" "ISDV4" > EndSection > > Section "InputDevice" > Driver "wacom" > Identifier "cursor" > Option "Device" "/dev/event0" > Option "Type" "cursor" > Option "USB" "on" > Option "ForceDevice" "ISDV4" > EndSection > > Section "InputDevice" > Driver "wacom" > Identifier "pad" > Option "Device" "/dev/event0" > Option "Type" "pad" > Option "USB" "on" > Option "ForceDevice" "ISDV4" > EndSection > > Section "InputDevice" > Driver "wacom" > Identifier "touch" > Option "Device" "/dev/event0" > Option "Type" "touch" > Option "USB" "on" > Option "ForceDevice" "ISDV4" > EndSection Alternatively, only add this one at and: Section "DRI" Mode 0666 EndSection If you follow 7-STABLE DRM should work without problems on that intel card. -- Paul From jnordwick at gmail.com Sat Mar 21 08:27:07 2009 From: jnordwick at gmail.com (Jason Nordwick) Date: Sat Mar 21 08:27:14 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: <49C4775A.4060206@FreeBSD.org> References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> <49C4775A.4060206@FreeBSD.org> Message-ID: Now that I have wireless working, I can copy and paste into messages, yeah! [jnordwick@jj ~]$ uname -a FreeBSD jj.nordwick.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [jnordwick@jj ~]$ cat /etc/rc.conf # -- sysinstall generated deltas -- # Wed Mar 18 20:34:14 2009 # Created: Wed Mar 18 20:34:14 2009 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname="jj.nordwick.com" ifconfig_bfe0="DHCP" ifconfig_wpi0="ssid mamalinz DHCP" keymap="us.emacs" linux_enable="YES" moused_enable="YES" moused_flags="-3" sshd_enable="YES" And I have no /etc/wpa_supplicant.conf The card works great with windows, and no other machine in the house (including Wii/PS3/PSP/Mac/Windows) have any problems connection or being speedy). For hardware, the machine is a Dell Inspiron E1705 dual core. So could there be SMP issues maybe? When connected by a wire, the download speed is much faster so it seems to be a wireless only problem. -j On Fri, Mar 20, 2009 at 10:12 PM, Doug Barton wrote: > Jason Nordwick wrote: > > Thanks for all the help. The problem was just that I couldn't figure out > > which device I needed to use and the information to turn on the device > > was in the man page that I didn't know about because it wasn't listed in > > the device output. Doh. > > > > Thank you everybody for your help. It all works now (except I still find > > it clunky to manage the networks I want to join, but I figure I'll find > > something out there to help with that or be able to write a script to do > > it). > > > > Now, I just have speed issues. For example, right now I am trying to > > install some ports, but maxing out the download at about 4-6 k/sec. Did > > I not include wpi0.makefast="YES" or something? > > It's impossible to help you diagnose this without a lot more > information. What version of FreeBSD are you using? What settings do > you have in rc.conf and (if appropriate) /etc/wpa_supplicant.conf? > Have you tried the same card with the same AP(s) with another > operating system? > > I have this same card and it works quite well in both FreeBSD and > Windows in 11g mode with my Linksys WRT54G AP on 8-current. > > > hth, > > Doug > From dougb at FreeBSD.org Sat Mar 21 14:26:44 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sat Mar 21 14:26:50 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> <49C4775A.4060206@FreeBSD.org> Message-ID: <49C55B8C.50208@FreeBSD.org> Jason Nordwick wrote: > Now that I have wireless working, I can copy and paste into messages, yeah! > > [jnordwick@jj ~]$ uname -a > FreeBSD jj.nordwick.com 7.1-RELEASE FreeBSD 7.1-RELEASE You should consider upgrading to -stable. There have been a lot of fixes in the 7.x branch since 7.1-release. > [jnordwick@jj ~]$ cat /etc/rc.conf > ifconfig_wpi0="ssid mamalinz DHCP" Try doing this instead: wlans_wpi0=wlan0 ifconfig_wlan0="DHCP ssid mamalinz mode 11g" If your AP doesn't do 11g then leave off that last bit. > And I have no /etc/wpa_supplicant.conf Ok, so no encryption on your network at all? We also need the ifconfig output as someone else mentioned. > The card works great with windows, and no other machine in the house > (including Wii/PS3/PSP/Mac/Windows) have any problems connection or being > speedy). > > For hardware, the machine is a Dell Inspiron E1705 dual core. So could there > be SMP issues maybe? No, my laptop is SMP. Doug -- This .signature sanitized for your protection From ivakras1 at gmail.com Sat Mar 21 15:21:14 2009 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Sat Mar 21 15:21:24 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> Message-ID: <200903220119.33634.ivakras1@gmail.com> On ??????? 20 ????? 2009 19:01:04 Jason Nordwick wrote: > Thanks for all the help. The problem was just that I couldn't figure > out which device I needed to use and the information to turn on the > device was in the man page that I didn't know about because it wasn't > listed in the device output. Doh. > > Thank you everybody for your help. It all works now (except I still > find it clunky to manage the networks I want to join, but I figure > I'll find something out there to help with that or be able to write a > script to do it). > > Now, I just have speed issues. For example, right now I am trying to > install some ports, but maxing out the download at about 4-6 k/sec. > Did I not include wpi0.makefast="YES" or something? > > -j > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > I have bought HP Pavilion dv6840er laptop with 3945ABG wireless onboard. After few month of messing with it i decided to replace it with Atheros based minipci card. The main problem with 3945ABG to me was a massive packet delivery failures - max distance from AP was 30 cm, more far - more packets missing. Atheros chip makes me happy, wpa2 ccmp with aes is supported and no problems anymore! Now it is really WIRELESS! From jnordwick at gmail.com Sun Mar 22 09:39:46 2009 From: jnordwick at gmail.com (Jason Nordwick) Date: Sun Mar 22 09:39:53 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: <49C55B8C.50208@FreeBSD.org> References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> <49C4775A.4060206@FreeBSD.org> <49C55B8C.50208@FreeBSD.org> Message-ID: Thanks for all the help, but this didn't help at all. It is either slow or I get a page of no route to host messages from ping when trying to ping my wireless router (and it does support 11g). I think their might be a syntax error on one of the lines you gave me, but I'm going to just try and run either -current or -stable. (I used to track current daily, so this doesn't bother me too much). Can I install a snapshot release from the ftp site? Sysinstall seems to be having problems finding the snapshots from Main this morning. -j On Mar 21, 2009, at 2:26 PM, Doug Barton wrote: > Jason Nordwick wrote: >> Now that I have wireless working, I can copy and paste into >> messages, yeah! >> >> [jnordwick@jj ~]$ uname -a >> FreeBSD jj.nordwick.com 7.1-RELEASE FreeBSD 7.1-RELEASE > > You should consider upgrading to -stable. There have been a lot of > fixes in the 7.x branch since 7.1-release. > >> [jnordwick@jj ~]$ cat /etc/rc.conf >> ifconfig_wpi0="ssid mamalinz DHCP" > > Try doing this instead: > wlans_wpi0=wlan0 > ifconfig_wlan0="DHCP ssid mamalinz mode 11g" > > If your AP doesn't do 11g then leave off that last bit. > >> And I have no /etc/wpa_supplicant.conf > > Ok, so no encryption on your network at all? We also need the ifconfig > output as someone else mentioned. > >> The card works great with windows, and no other machine in the house >> (including Wii/PS3/PSP/Mac/Windows) have any problems connection or >> being >> speedy). >> >> For hardware, the machine is a Dell Inspiron E1705 dual core. So >> could there >> be SMP issues maybe? > > No, my laptop is SMP. > > > Doug > > -- > > This .signature sanitized for your protection > From dougb at FreeBSD.org Sun Mar 22 12:20:07 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sun Mar 22 12:20:13 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> <49C4775A.4060206@FreeBSD.org> <49C55B8C.50208@FreeBSD.org> Message-ID: <49C68F61.4070204@FreeBSD.org> Jason Nordwick wrote: > Thanks for all the help, but this didn't help at all. It is either slow > or I get a page of no route to host messages from ping when trying to > ping my wireless router (and it does support 11g). I think their might > be a syntax error on one of the lines you gave me, There isn't, read the man page for wpi. BTW, I forgot to add that you should take out the ifconfig_wpi0 line that you had in your rc.conf. >> Try doing this instead: >> wlans_wpi0=wlan0 >> ifconfig_wlan0="DHCP ssid mamalinz mode 11g" If that doesn't work for you, you'll need to upgrade to the latest -stable. If you need help with that check the handbook, and/or ask on freebsd-questions@freebsd.org. Doug -- This .signature sanitized for your protection From nikolay.kanchev at amk-drives.bg Mon Mar 23 08:44:48 2009 From: nikolay.kanchev at amk-drives.bg (Nikolay Kanchev) Date: Mon Mar 23 08:45:19 2009 Subject: Atheros AR5211 802.11a can't send packets Message-ID: <49C7AD17.2080203@amk-drives.bg> Hello list I have trouble with miniPCI Atheros AR5211 based card and 802.11a mode on Freebsd 7.1 and 7.2 PRERELEASE Notebook: Pentium M 1.5GHz from FreeBSD 7.2 generic kernel dmesg ------------------------ ath0: mem 0xe0200000-0xe020ffff irq 10 at device 6.0 on pci2 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: Ethernet address: 00:ff:f3:a0:28:02 ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3 ------------------------ pciconf ------------------------ ath0@pci0:2:6:0: class=0x020000 card=0x7005144f chip=0x0012168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5211 802.11a/b/g Mini-PCI Wireless Adapter' class = network subclass = ethernet ------------------------ When I try to operate in 802.11a mode the card associate with AP but can't send packets. I try ping and check that the packets go through firewall but disappear somewhere, in tcpdump I don't see send packets. I try to ping my notebook from other PC and in tcpdump I see "arp who-has" and other packets from other PC but again no packets from AR5211 card. In 802.11b mode card is working fine. I try the card on windows and its working. ahtstats output: 13 data frames received 2 data frames transmit 65 long on-chip tx retries 4 tx failed 'cuz too many retries 1M current transmit rate 28 beacon miss interrupts 1746 tx management frames 2385 tx frames discarded prior to association 1703 tx frames with no ack marked 884 rx failed 'cuz of bad CRC 30 periodic calibrations 2 rfgain value change 7 avg recv rssi -96 rx noise floor 24 phantom beacon misses 53 tx discarded 'cuz queue is full Antenna profile: [0] tx 1739 rx 0 [1] tx 0 rx 6942 "tx discarded 'cuz queue is full" counter increased with ping packets. I try AR5006 based PCcard and it working fine on FreeBSD 7.1 and 7.2 It seems that only AR5211 driver have problems and can't send packets. -- Best regards, Nikolay Kanchev From nikolay.kanchev at amk-drives.bg Mon Mar 23 08:53:34 2009 From: nikolay.kanchev at amk-drives.bg (Nikolay Kanchev) Date: Mon Mar 23 08:53:40 2009 Subject: Atheros AR5211 802.11a can't send packets Message-ID: <49C7A8E5.2090909@amk-drives.bg> Hello list I have trouble with miniPCI Atheros AR5211 based card and 802.11a mode on Freebsd 7.1 and 7.2 PRERELEASE Notebook: Pentium M 1.5GHz from FreeBSD 7.2 generic kernel dmesg ------------------------ ath0: mem 0xe0200000-0xe020ffff irq 10 at device 6.0 on pci2 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: Ethernet address: 00:ff:f3:a0:28:02 ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3 ------------------------ pciconf ------------------------ ath0@pci0:2:6:0: class=0x020000 card=0x7005144f chip=0x0012168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5211 802.11a/b/g Mini-PCI Wireless Adapter' class = network subclass = ethernet ------------------------ When I try to operate in 802.11a mode the card associate with AP but can't send packets. I try ping and check that the packets go through firewall but disappear somewhere, in tcpdump I don't see send packets. I try to ping my notebook from other PC and in tcpdump I see "arp who-has" and other packets from other PC but again no packets from AR5211 card. In 802.11b mode card is working fine. I try the card on windows and its working. ahtstats output: 13 data frames received 2 data frames transmit 65 long on-chip tx retries 4 tx failed 'cuz too many retries 1M current transmit rate 28 beacon miss interrupts 1746 tx management frames 2385 tx frames discarded prior to association 1703 tx frames with no ack marked 884 rx failed 'cuz of bad CRC 30 periodic calibrations 2 rfgain value change 7 avg recv rssi -96 rx noise floor 24 phantom beacon misses 53 tx discarded 'cuz queue is full Antenna profile: [0] tx 1739 rx 0 [1] tx 0 rx 6942 "tx discarded 'cuz queue is full" counter increased with ping packets. I try AR5006 based PCcard and it working fine on FreeBSD 7.1 and 7.2 It seems that only AR5211 driver have problems and can't send packets. -- Best regards, Nikolay Kanchev From sam at freebsd.org Mon Mar 23 09:29:40 2009 From: sam at freebsd.org (Sam Leffler) Date: Mon Mar 23 09:29:55 2009 Subject: Atheros AR5211 802.11a can't send packets In-Reply-To: <49C7A8E5.2090909@amk-drives.bg> References: <49C7A8E5.2090909@amk-drives.bg> Message-ID: <49C7B8E1.20806@freebsd.org> Nikolay Kanchev wrote: > Hello list > > I have trouble with miniPCI Atheros AR5211 based card and 802.11a mode > on Freebsd 7.1 and 7.2 PRERELEASE > > Notebook: Pentium M 1.5GHz > > from FreeBSD 7.2 generic kernel > dmesg > ------------------------ > ath0: mem 0xe0200000-0xe020ffff irq 10 at device 6.0 on > pci2 > ath0: [ITHREAD] > ath0: WARNING: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:ff:f3:a0:28:02 > ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3 > ------------------------ > > pciconf > ------------------------ > ath0@pci0:2:6:0: class=0x020000 card=0x7005144f chip=0x0012168c > rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5211 802.11a/b/g Mini-PCI Wireless Adapter' > class = network > subclass = ethernet > ------------------------ > > When I try to operate in 802.11a mode the card associate with AP but > can't send packets. > I try ping and check that the packets go through firewall but > disappear somewhere, in tcpdump I don't see send packets. > I try to ping my notebook from other PC and in tcpdump I see "arp > who-has" and other packets from other PC but again no packets from > AR5211 card. > > In 802.11b mode card is working fine. > > I try the card on windows and its working. > > ahtstats output: > > 13 data frames received > 2 data frames transmit > 65 long on-chip tx retries > 4 tx failed 'cuz too many retries > 1M current transmit rate > 28 beacon miss interrupts > 1746 tx management frames > 2385 tx frames discarded prior to association > 1703 tx frames with no ack marked > 884 rx failed 'cuz of bad CRC > 30 periodic calibrations > 2 rfgain value change > 7 avg recv rssi > -96 rx noise floor > 24 phantom beacon misses > 53 tx discarded 'cuz queue is full > Antenna profile: > [0] tx 1739 rx 0 > [1] tx 0 rx 6942 > > "tx discarded 'cuz queue is full" counter increased with ping packets. > I try AR5006 based PCcard and it working fine on FreeBSD 7.1 and 7.2 > It seems that only AR5211 driver have problems and can't send packets. > A single snapshot of athstats isn't very useful; you need to collect stats before and after packets are lost to look for reasons why the packets do not go out. athstats 1 or similar is also useful when digging for problems. Alternatively learn about wlandebug and the debug facilities that let you get console msgs. I don't run RELENG_7 but I test 5211 in 11b and 11a, w/ and w/o security whenever I make hal changes so I doubt there's anything specific to the 5211. You also haven't provided basic info like how your card is configured. Sam From System Administrator Mon Mar 23 11:11:30 2009 From: System Administrator (System Administrator) Date: Mon Mar 23 11:11:36 2009 Subject: Delivery Failure Message-ID: <633734133755916764@smtp-PE3-3-SHARED11.orcsweb.com> Could not deliver message to the following recipient(s): Failed Recipient: org@paragliding.com.do Reason: Remote host said: 550 No such user (org@paragliding.com.do) -- The header and top 20 lines of the message follows -- Received: from pe3-3-shared11.orcsweb.com [127.0.0.1] by smtp-PE3-3-SHARED11.orcsweb.com with SMTP; Mon, 23 Mar 2009 13:56:06 -0400 From: "jonny3 jonny3" To: Org@Paragliding.com.do Subject: Registration Form Date: Mon, 23 Mar 2009 13:56:06 -0400 Message-ID: <20090323-13560662-147ec@pe3-3-shared11.orcsweb.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--=1AF278DD81294235AB15_4C88_4C68_BEAF" ----=1AF278DD81294235AB15_4C88_4C68_BEAF Content-Type: text/plain;charset="iso-8859-1" Content-Transfer-Encoding: 7bit New submission from Paragliding.com.do Names: jonny3 Surnames: jonny3 Country: UNDETERMINED Experience: UNDETERMINED Ranking: UNDETERMINED From jmt at twilley.org Mon Mar 23 12:36:38 2009 From: jmt at twilley.org (Jack Twilley) Date: Mon Mar 23 12:36:45 2009 Subject: RT2860 NDIS needs rate.bin, where is it? Message-ID: <49C7E0F8.9000701@twilley.org> NDIS finally works again in 8.0-CURRENT so I thought I'd try to get my RT2860 wireless working. I built the rt2860_sys.ko using ndisgen and copied rt2860.bin into /compat/ndis and kldloaded the new module. NDIS complains that it can't open /compat/ndis/rate.bin with errno 2. I don't have a rate.bin to give it, there wasn't one in the Windows bundle or the Linux one though it is referenced in the Linux driver source code. I tried copying rt2860.bin to rate.bin but that didn't work. I tried starting wpa_supplicant anyway, and got this: Starting wpa_supplicant. ioctl[SIOCG80211, op 98, len 32]: Invalid argument ELOOP: remaining socket: sock=5 eloop_data=0x28407140 user_data=0x2840e040 handler=0x8069f40 /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Jack. From knowtree at aloha.com Mon Mar 23 13:36:21 2009 From: knowtree at aloha.com (knowtree@aloha.com) Date: Mon Mar 23 13:36:28 2009 Subject: RT2860 NDIS needs rate.bin, where is it? Message-ID: <200903232036.n2NKaGXC016055@yoda.pixi.com> > NDIS finally works again in 8.0-CURRENT Is this the same thing as Project Evil? Gary Dunn Open Slate Project From onemda at gmail.com Mon Mar 23 14:41:54 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Mar 23 14:42:00 2009 Subject: RT2860 NDIS needs rate.bin, where is it? In-Reply-To: <49C7E0F8.9000701@twilley.org> References: <49C7E0F8.9000701@twilley.org> Message-ID: <3a142e750903231441g184fa5d1r57515c77d01e6dd4@mail.gmail.com> On 3/23/09, Jack Twilley wrote: > NDIS finally works again in 8.0-CURRENT so I thought I'd try to get my > RT2860 wireless working. I built the rt2860_sys.ko using ndisgen and > copied rt2860.bin into /compat/ndis and kldloaded the new module. NDIS > complains that it can't open /compat/ndis/rate.bin with errno 2. I > don't have a rate.bin to give it, there wasn't one in the Windows bundle > or the Linux one though it is referenced in the Linux driver source > code. I tried copying rt2860.bin to rate.bin but that didn't work. > > I tried starting wpa_supplicant anyway, and got this: > > Starting wpa_supplicant. > ioctl[SIOCG80211, op 98, len 32]: Invalid argument > ELOOP: remaining socket: sock=5 eloop_data=0x28407140 > user_data=0x2840e040 handler=0x8069f40 > /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant Please, tell me that you start wpa_supplicant with -Dndis flag. -- Paul From onemda at gmail.com Mon Mar 23 14:43:11 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Mon Mar 23 14:43:16 2009 Subject: RT2860 NDIS needs rate.bin, where is it? In-Reply-To: <200903232036.n2NKaGXC016055@yoda.pixi.com> References: <200903232036.n2NKaGXC016055@yoda.pixi.com> Message-ID: <3a142e750903231443u2f0df96vbf66e7318d410992@mail.gmail.com> On 3/23/09, knowtree@aloha.com wrote: >> NDIS finally works again in 8.0-CURRENT > > Is this the same thing as Project Evil? NDISulator a.k.a. Project Evil -- Paul From vince at unsane.co.uk Mon Mar 23 15:04:13 2009 From: vince at unsane.co.uk (Vincent Hoffman) Date: Mon Mar 23 15:04:20 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: <49C68F61.4070204@FreeBSD.org> References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> <49C4775A.4060206@FreeBSD.org> <49C55B8C.50208@FreeBSD.org> <49C68F61.4070204@FreeBSD.org> Message-ID: <49C8075A.2050008@unsane.co.uk> On 22/3/09 19:20, Doug Barton wrote: > Jason Nordwick wrote: > >> Thanks for all the help, but this didn't help at all. It is either slow >> or I get a page of no route to host messages from ping when trying to >> ping my wireless router (and it does support 11g). I think their might >> be a syntax error on one of the lines you gave me, >> > > There isn't, read the man page for wpi. BTW, I forgot to add that you > should take out the ifconfig_wpi0 line that you had in your rc.conf. > > >>> Try doing this instead: >>> wlans_wpi0=wlan0 >>> ifconfig_wlan0="DHCP ssid mamalinz mode 11g" >>> > > If that doesn't work for you, you'll need to upgrade to the latest > -stable. If you need help with that check the handbook, and/or ask on > freebsd-questions@freebsd.org. > > > I dont think the wlan vap stuff has been merged to -STABLE (nothing in UPDATING anyway,) so as far as I know its still ifconfig_wpi0= in -STABLE. Current config is as Doug says and has been since last april. I'm about to update a server at home from 7.1 to -STABLE so I'd be interested to know if i'm wrong. Vince > Doug > > From jmt at twilley.org Mon Mar 23 17:33:18 2009 From: jmt at twilley.org (Jack Twilley) Date: Mon Mar 23 17:33:25 2009 Subject: RT2860 NDIS needs rate.bin, where is it? In-Reply-To: <3a142e750903231441g184fa5d1r57515c77d01e6dd4@mail.gmail.com> References: <49C7E0F8.9000701@twilley.org> <3a142e750903231441g184fa5d1r57515c77d01e6dd4@mail.gmail.com> Message-ID: <49C82A4B.5090108@twilley.org> Paul B. Mahol wrote: > On 3/23/09, Jack Twilley wrote: >> NDIS finally works again in 8.0-CURRENT so I thought I'd try to get my >> RT2860 wireless working. I built the rt2860_sys.ko using ndisgen and >> copied rt2860.bin into /compat/ndis and kldloaded the new module. NDIS >> complains that it can't open /compat/ndis/rate.bin with errno 2. I >> don't have a rate.bin to give it, there wasn't one in the Windows bundle >> or the Linux one though it is referenced in the Linux driver source >> code. I tried copying rt2860.bin to rate.bin but that didn't work. >> >> I tried starting wpa_supplicant anyway, and got this: >> >> Starting wpa_supplicant. >> ioctl[SIOCG80211, op 98, len 32]: Invalid argument >> ELOOP: remaining socket: sock=5 eloop_data=0x28407140 >> user_data=0x2840e040 handler=0x8069f40 >> /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant > > Please, tell me that you start wpa_supplicant with -Dndis flag. > I ran 'sh -x /etc/rc.d/wpa_supplicant start ndis0' to see how the script was starting the program. Here is the original command line: /usr/sbin/wpa_supplicant -s -B -i ndis0 -c /etc/wpa_supplicant.conf -D bsd -P /var/run/wpa_supplicant/ndis0.pid I replaced '-D bsd' with '-D ndis' and still got a return code of 255. I double-checked to ensure the module was loaded, and adding '-dd' did not increase the debug output. I also read the /etc/rc.d/wpa_supplicant script to see how it detected whether or not to use '-D ndis'. Turns out it calls a function named 'is_ndis_interface()' which checks a sysctl named 'net.wlan.${1#wlan}.%parent' but there is no 'net.wlan.ndis0.%parent', nor is there any 'net.wlan.ndis0' keys. There *is* 'net.ndis.0.%parent' which is set to pci1 and 'net.ndis.0.%driver' which is set to ndis -- the latter sounds like a possibly sensible test for '-D ndis' if you ask me. Anyway, the fact that the sysctl wasn't present makes me think the failure to load /compat/ndis/rate.bin might have caused 'ndis_attach()' to not call 'ndis_create_sysctls()', or 'ndis_attach_pci()' to not call 'ndis_attach()', or so on -- but I can't tell where 'NdisOpenFile()' gets called so I'm not sure. Does this sound reasonable? What do you think? Jack. From dougb at FreeBSD.org Mon Mar 23 18:18:36 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Mon Mar 23 18:18:58 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: <49C8075A.2050008@unsane.co.uk> References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> <49C4775A.4060206@FreeBSD.org> <49C55B8C.50208@FreeBSD.org> <49C68F61.4070204@FreeBSD.org> <49C8075A.2050008@unsane.co.uk> Message-ID: <49C834E7.4070601@FreeBSD.org> Vincent Hoffman wrote: > I dont think the wlan vap stuff has been merged to -STABLE Don't guess. As I've said several times in this thread already, read the man page for wpi. Doug -- This .signature sanitized for your protection From onemda at gmail.com Tue Mar 24 00:22:32 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Tue Mar 24 00:22:40 2009 Subject: RT2860 NDIS needs rate.bin, where is it? In-Reply-To: <49C82A4B.5090108@twilley.org> References: <49C7E0F8.9000701@twilley.org> <3a142e750903231441g184fa5d1r57515c77d01e6dd4@mail.gmail.com> <49C82A4B.5090108@twilley.org> Message-ID: <3a142e750903240022n10d8b8cdy3787cc6b423df3c8@mail.gmail.com> On 3/24/09, Jack Twilley wrote: > Paul B. Mahol wrote: >> On 3/23/09, Jack Twilley wrote: >>> NDIS finally works again in 8.0-CURRENT so I thought I'd try to get my >>> RT2860 wireless working. I built the rt2860_sys.ko using ndisgen and >>> copied rt2860.bin into /compat/ndis and kldloaded the new module. NDIS >>> complains that it can't open /compat/ndis/rate.bin with errno 2. I >>> don't have a rate.bin to give it, there wasn't one in the Windows bundle >>> or the Linux one though it is referenced in the Linux driver source >>> code. I tried copying rt2860.bin to rate.bin but that didn't work. >>> >>> I tried starting wpa_supplicant anyway, and got this: >>> >>> Starting wpa_supplicant. >>> ioctl[SIOCG80211, op 98, len 32]: Invalid argument >>> ELOOP: remaining socket: sock=5 eloop_data=0x28407140 >>> user_data=0x2840e040 handler=0x8069f40 >>> /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant >> >> Please, tell me that you start wpa_supplicant with -Dndis flag. >> > > I ran 'sh -x /etc/rc.d/wpa_supplicant start ndis0' to see how the script > was starting the program. Here is the original command line: > > /usr/sbin/wpa_supplicant -s -B -i ndis0 -c /etc/wpa_supplicant.conf -D > bsd -P /var/run/wpa_supplicant/ndis0.pid > > I replaced '-D bsd' with '-D ndis' and still got a return code of 255. > I double-checked to ensure the module was loaded, and adding '-dd' did > not increase the debug output. > > I also read the /etc/rc.d/wpa_supplicant script to see how it detected > whether or not to use '-D ndis'. Turns out it calls a function named > 'is_ndis_interface()' which checks a sysctl named > 'net.wlan.${1#wlan}.%parent' but there is no 'net.wlan.ndis0.%parent', > nor is there any 'net.wlan.ndis0' keys. There *is* 'net.ndis.0.%parent' > which is set to pci1 and 'net.ndis.0.%driver' which is set to ndis -- > the latter sounds like a possibly sensible test for '-D ndis' if you ask > me. > > Anyway, the fact that the sysctl wasn't present makes me think the > failure to load /compat/ndis/rate.bin might have caused 'ndis_attach()' > to not call 'ndis_create_sysctls()', or 'ndis_attach_pci()' to not call > 'ndis_attach()', or so on -- but I can't tell where 'NdisOpenFile()' > gets called so I'm not sure. > > Does this sound reasonable? What do you think? Probably, in my case net.wlan.0.%parent is ndis0 What is displayed on kldload and device attach on console? Try it with sysctl debug.ndis=1. -- Paul From vince at unsane.co.uk Tue Mar 24 02:53:38 2009 From: vince at unsane.co.uk (Vincent Hoffman) Date: Tue Mar 24 02:53:45 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: <49C834E7.4070601@FreeBSD.org> References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> <49C4775A.4060206@FreeBSD.org> <49C55B8C.50208@FreeBSD.org> <49C68F61.4070204@FreeBSD.org> <49C8075A.2050008@unsane.co.uk> <49C834E7.4070601@FreeBSD.org> Message-ID: <49C8AD9B.6010207@unsane.co.uk> On 24/3/09 01:18, Doug Barton wrote: > Vincent Hoffman wrote: > >> I dont think the wlan vap stuff has been merged to -STABLE >> > > Don't guess. As I've said several times in this thread already, read > the man page for wpi. > > Doug > > Sorry Doug -STABLE doesnt use the multi-bss code. It still uses the old style config options http://svn.freebsd.org/viewvc/base/stable/7/share/man/man4/wpi.4?view=markup Is the multi-bss code likely to be MFCed? I assumed it was too big a change but it would be cool if it could. Vince From jmt at twilley.org Tue Mar 24 10:12:29 2009 From: jmt at twilley.org (Jack Twilley) Date: Tue Mar 24 10:12:36 2009 Subject: RT2860 NDIS needs rate.bin, where is it? In-Reply-To: <3a142e750903240022n10d8b8cdy3787cc6b423df3c8@mail.gmail.com> References: <49C7E0F8.9000701@twilley.org> <3a142e750903231441g184fa5d1r57515c77d01e6dd4@mail.gmail.com> <49C82A4B.5090108@twilley.org> <3a142e750903240022n10d8b8cdy3787cc6b423df3c8@mail.gmail.com> Message-ID: <49C91475.9080303@twilley.org> Paul B. Mahol wrote: > On 3/24/09, Jack Twilley wrote: >> Paul B. Mahol wrote: >>> On 3/23/09, Jack Twilley wrote: >>>> NDIS finally works again in 8.0-CURRENT so I thought I'd try to get my >>>> RT2860 wireless working. I built the rt2860_sys.ko using ndisgen and >>>> copied rt2860.bin into /compat/ndis and kldloaded the new module. NDIS >>>> complains that it can't open /compat/ndis/rate.bin with errno 2. I >>>> don't have a rate.bin to give it, there wasn't one in the Windows bundle >>>> or the Linux one though it is referenced in the Linux driver source >>>> code. I tried copying rt2860.bin to rate.bin but that didn't work. >>>> >>>> I tried starting wpa_supplicant anyway, and got this: >>>> >>>> Starting wpa_supplicant. >>>> ioctl[SIOCG80211, op 98, len 32]: Invalid argument >>>> ELOOP: remaining socket: sock=5 eloop_data=0x28407140 >>>> user_data=0x2840e040 handler=0x8069f40 >>>> /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant >>> Please, tell me that you start wpa_supplicant with -Dndis flag. >>> >> I ran 'sh -x /etc/rc.d/wpa_supplicant start ndis0' to see how the script >> was starting the program. Here is the original command line: >> >> /usr/sbin/wpa_supplicant -s -B -i ndis0 -c /etc/wpa_supplicant.conf -D >> bsd -P /var/run/wpa_supplicant/ndis0.pid >> >> I replaced '-D bsd' with '-D ndis' and still got a return code of 255. >> I double-checked to ensure the module was loaded, and adding '-dd' did >> not increase the debug output. >> >> I also read the /etc/rc.d/wpa_supplicant script to see how it detected >> whether or not to use '-D ndis'. Turns out it calls a function named >> 'is_ndis_interface()' which checks a sysctl named >> 'net.wlan.${1#wlan}.%parent' but there is no 'net.wlan.ndis0.%parent', >> nor is there any 'net.wlan.ndis0' keys. There *is* 'net.ndis.0.%parent' >> which is set to pci1 and 'net.ndis.0.%driver' which is set to ndis -- >> the latter sounds like a possibly sensible test for '-D ndis' if you ask >> me. >> >> Anyway, the fact that the sysctl wasn't present makes me think the >> failure to load /compat/ndis/rate.bin might have caused 'ndis_attach()' >> to not call 'ndis_create_sysctls()', or 'ndis_attach_pci()' to not call >> 'ndis_attach()', or so on -- but I can't tell where 'NdisOpenFile()' >> gets called so I'm not sure. >> >> Does this sound reasonable? What do you think? > > Probably, in my case net.wlan.0.%parent is ndis0 > > What is displayed on kldload and device attach on console? > Try it with sysctl debug.ndis=1. > > Here is dmesg output from 'kldload rt2860_sys.ko' after running 'sysctl debug.ndis=1': no match for ZwWriteFile no match for ZwCreateFile no match for ZwReadFile ndis0: <802.11n Wireless LAN Card> mem 0xfbef0000-0xfbefffff irq 19 at device0.0 on pci1 ndis0: [ITHREAD] ndis0: NDIS API version: 5.0 NDIS: open file /compat/ndis/rate.bin failed: 2 attach done. halting done. /var/log/messages doesn't have anything new to add -- an unknown USB device is detected but that's the camera so I'm not worried. Jack. From onemda at gmail.com Tue Mar 24 11:59:58 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Tue Mar 24 12:00:04 2009 Subject: RT2860 NDIS needs rate.bin, where is it? In-Reply-To: <49C91475.9080303@twilley.org> References: <49C7E0F8.9000701@twilley.org> <3a142e750903231441g184fa5d1r57515c77d01e6dd4@mail.gmail.com> <49C82A4B.5090108@twilley.org> <3a142e750903240022n10d8b8cdy3787cc6b423df3c8@mail.gmail.com> <49C91475.9080303@twilley.org> Message-ID: <3a142e750903241159m57464eb7wd50a6e88fd1390c2@mail.gmail.com> On 3/24/09, Jack Twilley wrote: > Paul B. Mahol wrote: >> On 3/24/09, Jack Twilley wrote: >>> Paul B. Mahol wrote: >>>> On 3/23/09, Jack Twilley wrote: >>>>> NDIS finally works again in 8.0-CURRENT so I thought I'd try to get my >>>>> RT2860 wireless working. I built the rt2860_sys.ko using ndisgen and >>>>> copied rt2860.bin into /compat/ndis and kldloaded the new module. NDIS >>>>> complains that it can't open /compat/ndis/rate.bin with errno 2. I >>>>> don't have a rate.bin to give it, there wasn't one in the Windows >>>>> bundle >>>>> or the Linux one though it is referenced in the Linux driver source >>>>> code. I tried copying rt2860.bin to rate.bin but that didn't work. >>>>> >>>>> I tried starting wpa_supplicant anyway, and got this: >>>>> >>>>> Starting wpa_supplicant. >>>>> ioctl[SIOCG80211, op 98, len 32]: Invalid argument >>>>> ELOOP: remaining socket: sock=5 eloop_data=0x28407140 >>>>> user_data=0x2840e040 handler=0x8069f40 >>>>> /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant >>>> Please, tell me that you start wpa_supplicant with -Dndis flag. >>>> >>> I ran 'sh -x /etc/rc.d/wpa_supplicant start ndis0' to see how the script >>> was starting the program. Here is the original command line: >>> >>> /usr/sbin/wpa_supplicant -s -B -i ndis0 -c /etc/wpa_supplicant.conf -D >>> bsd -P /var/run/wpa_supplicant/ndis0.pid >>> >>> I replaced '-D bsd' with '-D ndis' and still got a return code of 255. >>> I double-checked to ensure the module was loaded, and adding '-dd' did >>> not increase the debug output. >>> >>> I also read the /etc/rc.d/wpa_supplicant script to see how it detected >>> whether or not to use '-D ndis'. Turns out it calls a function named >>> 'is_ndis_interface()' which checks a sysctl named >>> 'net.wlan.${1#wlan}.%parent' but there is no 'net.wlan.ndis0.%parent', >>> nor is there any 'net.wlan.ndis0' keys. There *is* 'net.ndis.0.%parent' >>> which is set to pci1 and 'net.ndis.0.%driver' which is set to ndis -- >>> the latter sounds like a possibly sensible test for '-D ndis' if you ask >>> me. >>> >>> Anyway, the fact that the sysctl wasn't present makes me think the >>> failure to load /compat/ndis/rate.bin might have caused 'ndis_attach()' >>> to not call 'ndis_create_sysctls()', or 'ndis_attach_pci()' to not call >>> 'ndis_attach()', or so on -- but I can't tell where 'NdisOpenFile()' >>> gets called so I'm not sure. >>> >>> Does this sound reasonable? What do you think? >> >> Probably, in my case net.wlan.0.%parent is ndis0 >> >> What is displayed on kldload and device attach on console? >> Try it with sysctl debug.ndis=1. >> >> > > Here is dmesg output from 'kldload rt2860_sys.ko' after running 'sysctl > debug.ndis=1': > > no match for ZwWriteFile > no match for ZwCreateFile > no match for ZwReadFile > ndis0: <802.11n Wireless LAN Card> mem 0xfbef0000-0xfbefffff irq 19 at > device0.0 on pci1 > ndis0: [ITHREAD] > ndis0: NDIS API version: 5.0 > NDIS: open file /compat/ndis/rate.bin failed: 2 > attach done. > halting done. > > /var/log/messages doesn't have anything new to add -- an unknown USB > device is detected but that's the camera so I'm not worried. Perhaps rate.bin is already in that firmware. But I dont understand why "dummy called" is not displayed. Either required functions are not implemented or already present one are wrongly implemented. What about of "ktrace kldload ./rt2860_sys.ko"? -- Paul From sam at freebsd.org Tue Mar 24 12:29:33 2009 From: sam at freebsd.org (Sam Leffler) Date: Tue Mar 24 12:29:40 2009 Subject: RT2860 NDIS needs rate.bin, where is it? In-Reply-To: <3a142e750903241159m57464eb7wd50a6e88fd1390c2@mail.gmail.com> References: <49C7E0F8.9000701@twilley.org> <3a142e750903231441g184fa5d1r57515c77d01e6dd4@mail.gmail.com> <49C82A4B.5090108@twilley.org> <3a142e750903240022n10d8b8cdy3787cc6b423df3c8@mail.gmail.com> <49C91475.9080303@twilley.org> <3a142e750903241159m57464eb7wd50a6e88fd1390c2@mail.gmail.com> Message-ID: <49C9349B.4080707@freebsd.org> Paul B. Mahol wrote: > On 3/24/09, Jack Twilley wrote: > >> Paul B. Mahol wrote: >> >>> On 3/24/09, Jack Twilley wrote: >>> >>>> Paul B. Mahol wrote: >>>> >>>>> On 3/23/09, Jack Twilley wrote: >>>>> >>>>>> NDIS finally works again in 8.0-CURRENT so I thought I'd try to get my >>>>>> RT2860 wireless working. I built the rt2860_sys.ko using ndisgen and >>>>>> copied rt2860.bin into /compat/ndis and kldloaded the new module. NDIS >>>>>> complains that it can't open /compat/ndis/rate.bin with errno 2. I >>>>>> don't have a rate.bin to give it, there wasn't one in the Windows >>>>>> bundle >>>>>> or the Linux one though it is referenced in the Linux driver source >>>>>> code. I tried copying rt2860.bin to rate.bin but that didn't work. >>>>>> >>>>>> I tried starting wpa_supplicant anyway, and got this: >>>>>> >>>>>> Starting wpa_supplicant. >>>>>> ioctl[SIOCG80211, op 98, len 32]: Invalid argument >>>>>> ELOOP: remaining socket: sock=5 eloop_data=0x28407140 >>>>>> user_data=0x2840e040 handler=0x8069f40 >>>>>> /etc/rc.d/wpa_supplicant: WARNING: failed to start wpa_supplicant >>>>>> >>>>> Please, tell me that you start wpa_supplicant with -Dndis flag. >>>>> >>>>> >>>> I ran 'sh -x /etc/rc.d/wpa_supplicant start ndis0' to see how the script >>>> was starting the program. Here is the original command line: >>>> >>>> /usr/sbin/wpa_supplicant -s -B -i ndis0 -c /etc/wpa_supplicant.conf -D >>>> bsd -P /var/run/wpa_supplicant/ndis0.pid >>>> >>>> I replaced '-D bsd' with '-D ndis' and still got a return code of 255. >>>> I double-checked to ensure the module was loaded, and adding '-dd' did >>>> not increase the debug output. >>>> >>>> I also read the /etc/rc.d/wpa_supplicant script to see how it detected >>>> whether or not to use '-D ndis'. Turns out it calls a function named >>>> 'is_ndis_interface()' which checks a sysctl named >>>> 'net.wlan.${1#wlan}.%parent' but there is no 'net.wlan.ndis0.%parent', >>>> nor is there any 'net.wlan.ndis0' keys. There *is* 'net.ndis.0.%parent' >>>> which is set to pci1 and 'net.ndis.0.%driver' which is set to ndis -- >>>> the latter sounds like a possibly sensible test for '-D ndis' if you ask >>>> me. >>>> >>>> Anyway, the fact that the sysctl wasn't present makes me think the >>>> failure to load /compat/ndis/rate.bin might have caused 'ndis_attach()' >>>> to not call 'ndis_create_sysctls()', or 'ndis_attach_pci()' to not call >>>> 'ndis_attach()', or so on -- but I can't tell where 'NdisOpenFile()' >>>> gets called so I'm not sure. >>>> >>>> Does this sound reasonable? What do you think? >>>> >>> Probably, in my case net.wlan.0.%parent is ndis0 >>> >>> What is displayed on kldload and device attach on console? >>> Try it with sysctl debug.ndis=1. >>> >>> >>> >> Here is dmesg output from 'kldload rt2860_sys.ko' after running 'sysctl >> debug.ndis=1': >> >> no match for ZwWriteFile >> no match for ZwCreateFile >> no match for ZwReadFile >> ndis0: <802.11n Wireless LAN Card> mem 0xfbef0000-0xfbefffff irq 19 at >> device0.0 on pci1 >> ndis0: [ITHREAD] >> ndis0: NDIS API version: 5.0 >> NDIS: open file /compat/ndis/rate.bin failed: 2 >> attach done. >> halting done. >> >> /var/log/messages doesn't have anything new to add -- an unknown USB >> device is detected but that's the camera so I'm not worried. >> > > Perhaps rate.bin is already in that firmware. But I dont understand > why "dummy called" is not displayed. Either required functions are not > implemented or already present one are wrongly implemented. > > What about of "ktrace kldload ./rt2860_sys.ko"? > It looks very much like the driver is using ZwCreateFile+ZwReadFile to collect the contents of rate.bin. You can try implementing them (google points directly at the msdn entries) but you'll still need the .bin file. Seems like a better solution is to just bring over the 2860 support from obsd. Several people started that before but lost interest. If anyone's motivated they can contact me directly. Sam From dougb at FreeBSD.org Tue Mar 24 14:35:57 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Tue Mar 24 14:36:05 2009 Subject: Intel/Pro Wireless 3945ABG working! now slow :( In-Reply-To: <49C8AD9B.6010207@unsane.co.uk> References: <02EF6260-D64F-4473-A5F6-C95246261BCE@gmail.com> <49C4775A.4060206@FreeBSD.org> <49C55B8C.50208@FreeBSD.org> <49C68F61.4070204@FreeBSD.org> <49C8075A.2050008@unsane.co.uk> <49C834E7.4070601@FreeBSD.org> <49C8AD9B.6010207@unsane.co.uk> Message-ID: <49C95230.7010902@FreeBSD.org> Vincent Hoffman wrote: > Sorry Doug -STABLE doesnt use the multi-bss code. It still uses the old > style config options > http://svn.freebsd.org/viewvc/base/stable/7/share/man/man4/wpi.4?view=markup That man page specifically mentions wlan, although it does go on to use the "older" ifconfig_wpi0=blah examples. Strange. In any case, what I told the OP to do was to _try_ the wlan style configuration since what he was doing wasn't working. He's since reported back that things are sort of working, although since we've never seen the results of an 'ifconfig' I still have no idea what he's actually doing. Feel free to leave me off future replies to this thread. Doug From freemagic at freemagic.it Wed Mar 25 15:48:20 2009 From: freemagic at freemagic.it (freemagic@freemagic.it) Date: Wed Mar 25 15:48:27 2009 Subject: New Submit GFSearc! Message-ID: <20090325222135.26269.qmail@webxc01s11.ad.aruba.it> Welcome to Freemagic Search! We are located at http://www.freemagic.it/cgi-bin/cerca/motore.cgi YOUR SUBMISSION: ------------------------------------------------------------------ URL : http://zhou-rox.com/testing/editor/language/7screen.html Title : XlMmBywufrmhb Description : TkfwokCdaJaLhbyzP Keywords : pkQPcJghGqmsHLUMuI E-mail : mobile@freebsd.org ------------------------------------------------------------------ Anything in this file is e-mailed to visitors who submit their URL to your search engine. To maintain compatibility with older e-mail clients you should limit the length of any line in this file to 70 characters or less.------------------------------------------------------------------ Thanks again, --------------------------------------------- Freemagic Search freemagic\@freemagic.it http://www.freemagic.it/cgi-bin/cerca/motore.cgi --------------------------------------------- Powered by : EasySearch - Copyright 1999 http://www.getperl.com visit: www.gratisfree.it/top100gf/index.shtml visit: www.gratisfree.it/top100patgirl/index.html From guru at unixarea.de Thu Mar 26 04:58:55 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu Mar 26 04:59:22 2009 Subject: acer Aspire one 150L booted -CURRENT Message-ID: <20090326115852.GA36096@rebelion.Sisis.de> Hello, For some other reason I have created an USB key with a -CURRENT kernel (to test something on my EeePC 900). A colleague of me owns an "acer Aspire one 150L" netbook http://en.wikipedia.org/wiki/Aspire_One and I let it boot from the key; it booted fine and WLAN and DHCP came up without any kind of problem; just to let you know if someone is thinking in replacing the Linpus or XP on it; boot msg are attached below; matthias Mar 25 17:09:25 tinyCurrent syslogd: kernel boot file is /boot/kernel/kernel Mar 25 17:09:25 tinyCurrent kernel: Copyright (c) 1992-2009 The FreeBSD Project. Mar 25 17:09:25 tinyCurrent kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 25 17:09:25 tinyCurrent kernel: The Regents of the University of California. All rights reserved. Mar 25 17:09:25 tinyCurrent kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Mar 25 17:09:25 tinyCurrent kernel: FreeBSD 8.0-CURRENT #0: Sun Mar 22 11:47:41 CET 2009 Mar 25 17:09:25 tinyCurrent kernel: root@rebelion.Sisis.de:/usr/src/myHEAD/obj/usr/src/myHEAD/src/sys/GENERIC Mar 25 17:09:25 tinyCurrent kernel: WARNING: WITNESS option enabled, expect reduced performance. Mar 25 17:09:25 tinyCurrent kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Mar 25 17:09:25 tinyCurrent kernel: CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (1599.20-MHz 686-class CPU) Mar 25 17:09:25 tinyCurrent kernel: Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 Mar 25 17:09:25 tinyCurrent kernel: Features=0xbfe9fbff Mar 25 17:09:25 tinyCurrent kernel: Features2=0x40c39d> Mar 25 17:09:25 tinyCurrent kernel: AMD Features2=0x1 Mar 25 17:09:25 tinyCurrent kernel: TSC: P-state invariant Mar 25 17:09:25 tinyCurrent kernel: Logical CPUs per core: 2 Mar 25 17:09:25 tinyCurrent kernel: real memory = 1062141952 (1012 MB) Mar 25 17:09:25 tinyCurrent kernel: avail memory = 1021136896 (973 MB) Mar 25 17:09:25 tinyCurrent kernel: ACPI APIC Table: Mar 25 17:09:25 tinyCurrent kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Mar 25 17:09:25 tinyCurrent kernel: cpu0 (BSP): APIC ID: 0 Mar 25 17:09:25 tinyCurrent kernel: cpu1 (AP/HT): APIC ID: 1 Mar 25 17:09:25 tinyCurrent kernel: ioapic0: Changing APIC ID to 4 Mar 25 17:09:25 tinyCurrent kernel: ioapic0 irqs 0-23 on motherboard Mar 25 17:09:25 tinyCurrent kernel: kbd1 at kbdmux0 Mar 25 17:09:25 tinyCurrent kernel: acpi0: on motherboard Mar 25 17:09:25 tinyCurrent kernel: acpi0: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: acpi0: Power Button (fixed) Mar 25 17:09:25 tinyCurrent kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Mar 25 17:09:25 tinyCurrent kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 Mar 25 17:09:25 tinyCurrent kernel: acpi_ec0: port 0x62,0x66 on acpi0 Mar 25 17:09:25 tinyCurrent kernel: acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Mar 25 17:09:25 tinyCurrent kernel: Timecounter "HPET" frequency 14318180 Hz quality 900 Mar 25 17:09:25 tinyCurrent kernel: acpi_button0: on acpi0 Mar 25 17:09:25 tinyCurrent kernel: acpi_lid0: on acpi0 Mar 25 17:09:25 tinyCurrent kernel: acpi_button1: on acpi0 Mar 25 17:09:25 tinyCurrent kernel: battery0: on acpi0 Mar 25 17:09:25 tinyCurrent kernel: acpi_acad0: on acpi0 Mar 25 17:09:25 tinyCurrent kernel: pcib0: port 0xcf8-0xcff on acpi0 Mar 25 17:09:25 tinyCurrent kernel: pci0: on pcib0 Mar 25 17:09:25 tinyCurrent kernel: vgapci0: port 0x60c0-0x60c7 mem 0x58480000-0x584fffff,0x40000000-0x4fffffff,0x58500000-0x5853ffff irq 16 at device 2.0 on pci0 Mar 25 17:09:25 tinyCurrent kernel: agp0: on vgapci0 Mar 25 17:09:25 tinyCurrent kernel: agp0: detected 7932k stolen memory Mar 25 17:09:25 tinyCurrent kernel: agp0: aperture size is 256M Mar 25 17:09:25 tinyCurrent kernel: vgapci1: mem 0x58400000-0x5847ffff at device 2.1 on pci0 Mar 25 17:09:25 tinyCurrent kernel: pci0: at device 27.0 (no driver attached) Mar 25 17:09:25 tinyCurrent kernel: pcib1: at device 28.0 on pci0 Mar 25 17:09:25 tinyCurrent kernel: pci1: on pcib1 Mar 25 17:09:25 tinyCurrent kernel: pcib2: at device 28.1 on pci0 Mar 25 17:09:25 tinyCurrent kernel: pci2: on pcib2 Mar 25 17:09:25 tinyCurrent kernel: re0: port 0x3000-0x30ff mem 0x51010000-0x51010fff,0x51000000-0x5100ffff irq 17 at device 0.0 on pci2 Mar 25 17:09:25 tinyCurrent kernel: re0: Using 1 MSI messages Mar 25 17:09:25 tinyCurrent kernel: re0: Chip rev. 0x24800000 Mar 25 17:09:25 tinyCurrent kernel: re0: MAC rev. 0x00000000 Mar 25 17:09:25 tinyCurrent kernel: miibus0: on re0 Mar 25 17:09:25 tinyCurrent kernel: rlphy0: PHY 1 on miibus0 Mar 25 17:09:25 tinyCurrent kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Mar 25 17:09:25 tinyCurrent kernel: re0: Ethernet address: 00:1e:68:ea:e4:36 Mar 25 17:09:25 tinyCurrent kernel: re0: [FILTER] Mar 25 17:09:25 tinyCurrent kernel: pcib3: at device 28.2 on pci0 Mar 25 17:09:25 tinyCurrent kernel: pci3: on pcib3 Mar 25 17:09:25 tinyCurrent kernel: ath0: mem 0x55200000-0x5520ffff irq 18 at device 0.0 on pci3 Mar 25 17:09:25 tinyCurrent kernel: ath0: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: ath0: AR2425 mac 14.2 RF5424 phy 7.0 Mar 25 17:09:25 tinyCurrent kernel: pcib4: at device 28.3 on pci0 Mar 25 17:09:25 tinyCurrent kernel: pci4: on pcib4 Mar 25 17:09:25 tinyCurrent kernel: uhci0: port 0x6080-0x609f irq 16 at device 29.0 on pci0 Mar 25 17:09:25 tinyCurrent kernel: uhci0: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: uhci0: LegSup = 0x0f10 Mar 25 17:09:25 tinyCurrent kernel: usbus0: on uhci0 Mar 25 17:09:25 tinyCurrent kernel: uhci1: port 0x6060-0x607f irq 17 at device 29.1 on pci0 Mar 25 17:09:25 tinyCurrent kernel: uhci1: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: uhci1: LegSup = 0x0f00 Mar 25 17:09:25 tinyCurrent kernel: usbus1: on uhci1 Mar 25 17:09:25 tinyCurrent kernel: uhci2: port 0x6040-0x605f irq 18 at device 29.2 on pci0 Mar 25 17:09:25 tinyCurrent kernel: uhci2: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: uhci2: LegSup = 0x0f00 Mar 25 17:09:25 tinyCurrent kernel: usbus2: on uhci2 Mar 25 17:09:25 tinyCurrent kernel: uhci3: port 0x6020-0x603f irq 19 at device 29.3 on pci0 Mar 25 17:09:25 tinyCurrent kernel: uhci3: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: uhci3: LegSup = 0x0f00 Mar 25 17:09:25 tinyCurrent kernel: usbus3: on uhci3 Mar 25 17:09:25 tinyCurrent kernel: ehci0: mem 0x58544400-0x585447ff irq 16 at device 29.7 on pci0 Mar 25 17:09:25 tinyCurrent kernel: ehci0: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: usbus4: EHCI version 1.0 Mar 25 17:09:25 tinyCurrent kernel: usbus4: on ehci0 Mar 25 17:09:25 tinyCurrent kernel: pcib5: at device 30.0 on pci0 Mar 25 17:09:25 tinyCurrent kernel: pci5: on pcib5 Mar 25 17:09:25 tinyCurrent kernel: isab0: at device 31.0 on pci0 Mar 25 17:09:25 tinyCurrent kernel: isa0: on isab0 Mar 25 17:09:25 tinyCurrent kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x60a0-0x60af irq 17 at device 31.2 on pci0 Mar 25 17:09:25 tinyCurrent kernel: ata0: on atapci0 Mar 25 17:09:25 tinyCurrent kernel: ata0: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: ata1: on atapci0 Mar 25 17:09:25 tinyCurrent kernel: ata1: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: pci0: at device 31.3 (no driver attached) Mar 25 17:09:25 tinyCurrent kernel: atrtc1: port 0x70-0x77 on acpi0 Mar 25 17:09:25 tinyCurrent kernel: atrtc1: Warning: Couldn't map I/O. Mar 25 17:09:25 tinyCurrent kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 Mar 25 17:09:25 tinyCurrent kernel: atkbd0: irq 1 on atkbdc0 Mar 25 17:09:25 tinyCurrent kernel: kbd0 at atkbd0 Mar 25 17:09:25 tinyCurrent kernel: atkbd0: [GIANT-LOCKED] Mar 25 17:09:25 tinyCurrent kernel: atkbd0: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: psm0: irq 12 on atkbdc0 Mar 25 17:09:25 tinyCurrent kernel: psm0: [GIANT-LOCKED] Mar 25 17:09:25 tinyCurrent kernel: psm0: [ITHREAD] Mar 25 17:09:25 tinyCurrent kernel: psm0: model Generic PS/2 mouse, device ID 0 Mar 25 17:09:25 tinyCurrent kernel: cpu0: on acpi0 Mar 25 17:09:25 tinyCurrent kernel: est0: on cpu0 Mar 25 17:09:25 tinyCurrent kernel: p4tcc0: on cpu0 Mar 25 17:09:25 tinyCurrent kernel: cpu1: on acpi0 Mar 25 17:09:25 tinyCurrent kernel: est1: on cpu1 Mar 25 17:09:25 tinyCurrent kernel: p4tcc1: on cpu1 Mar 25 17:09:25 tinyCurrent kernel: pmtimer0 on isa0 Mar 25 17:09:25 tinyCurrent kernel: orm0: at iomem 0xcf000-0xcffff pnpid ORM0000 on isa0 Mar 25 17:09:25 tinyCurrent kernel: sc0: at flags 0x100 on isa0 Mar 25 17:09:25 tinyCurrent kernel: sc0: VGA <16 virtual consoles, flags=0x300> Mar 25 17:09:25 tinyCurrent kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Mar 25 17:09:25 tinyCurrent kernel: atrtc0: at port 0x70 irq 8 on isa0 Mar 25 17:09:25 tinyCurrent kernel: atrtc0: Warning: Couldn't map I/O. Mar 25 17:09:25 tinyCurrent kernel: atrtc0: Warning: Couldn't map Interrupt. Mar 25 17:09:25 tinyCurrent kernel: ppc0: parallel port not found. Mar 25 17:09:25 tinyCurrent kernel: Timecounters tick every 1.000 msec Mar 25 17:09:25 tinyCurrent kernel: usbus2: 12Mbps Full Speed USB v1.0 Mar 25 17:09:25 tinyCurrent kernel: usbus3: 12Mbps Full Speed USB v1.0 Mar 25 17:09:25 tinyCurrent kernel: usbus4: 480Mbps High Speed USB v2.0 Mar 25 17:09:25 tinyCurrent kernel: usbus0: 12Mbps Full Speed USB v1.0 Mar 25 17:09:25 tinyCurrent kernel: usbus1: 12Mbps Full Speed USB v1.0 Mar 25 17:09:25 tinyCurrent kernel: ad0: 114473MB at ata0-master SATA150 Mar 25 17:09:25 tinyCurrent kernel: ugen2.1: at usbus2 Mar 25 17:09:25 tinyCurrent kernel: uhub0: on usbus2 Mar 25 17:09:25 tinyCurrent kernel: ugen3.1: at usbus3 Mar 25 17:09:25 tinyCurrent kernel: uhub1: on usbus3 Mar 25 17:09:25 tinyCurrent kernel: ugen4.1: at usbus4 Mar 25 17:09:25 tinyCurrent kernel: uhub2: on usbus4 Mar 25 17:09:25 tinyCurrent kernel: ugen0.1: at usbus0 Mar 25 17:09:25 tinyCurrent kernel: uhub3: on usbus0 Mar 25 17:09:25 tinyCurrent kernel: ugen1.1: at usbus1 Mar 25 17:09:25 tinyCurrent kernel: uhub4: on usbus1 Mar 25 17:09:25 tinyCurrent kernel: SMP: AP CPU #1 Launched! Mar 25 17:09:25 tinyCurrent kernel: WARNING: WITNESS option enabled, expect reduced performance. Mar 25 17:09:25 tinyCurrent kernel: GEOM_LABEL: Label for provider ad0s1 is msdosfs/PQSERVICE. Mar 25 17:09:25 tinyCurrent kernel: GEOM_LABEL: Label for provider ad0s1 is ext2fs/linpus. Mar 25 17:09:25 tinyCurrent kernel: Root mount waiting for: usbus4 usbus3 usbus2 usbus1 usbus0 Mar 25 17:09:25 tinyCurrent kernel: uhub0: 2 ports with 2 removable, self powered Mar 25 17:09:25 tinyCurrent kernel: Root mount waiting for: usbus4 usbus3 usbus1 usbus0 Mar 25 17:09:25 tinyCurrent kernel: uhub1: 2 ports with 2 removable, self powered Mar 25 17:09:25 tinyCurrent kernel: Root mount waiting for: usbus4 usbus1 usbus0 Mar 25 17:09:25 tinyCurrent kernel: uhub3: 2 ports with 2 removable, self powered Mar 25 17:09:25 tinyCurrent kernel: Root mount waiting for: usbus4 usbus1 Mar 25 17:09:25 tinyCurrent kernel: uhub4: 2 ports with 2 removable, self powered Mar 25 17:09:25 tinyCurrent kernel: Root mount waiting for: usbus4 Mar 25 17:09:25 tinyCurrent last message repeated 3 times Mar 25 17:09:25 tinyCurrent kernel: uhub2: 8 ports with 8 removable, self powered Mar 25 17:09:25 tinyCurrent kernel: ugen4.2: at usbus4 Mar 25 17:09:25 tinyCurrent kernel: umass0: on usbus4 Mar 25 17:09:25 tinyCurrent kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000 Mar 25 17:09:25 tinyCurrent kernel: Root mount waiting for: usbus4 Mar 25 17:09:25 tinyCurrent kernel: umass0:0:0:-1: Attached to scbus0 Mar 25 17:09:25 tinyCurrent kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Mar 25 17:09:25 tinyCurrent kernel: da0: Removable Direct Access SCSI-2 device Mar 25 17:09:25 tinyCurrent kernel: da0: 40.000MB/s transfers Mar 25 17:09:25 tinyCurrent kernel: da0: 7712MB (15794176 512 byte sectors: 255H 63S/T 983C) Mar 25 17:09:25 tinyCurrent kernel: Root mount waiting for: usbus4 Mar 25 17:09:25 tinyCurrent kernel: ugen4.3: at usbus4 Mar 25 17:09:25 tinyCurrent kernel: Trying to mount root from ufs:/dev/da0s1a Mar 25 17:09:25 tinyCurrent kernel: wlan0: Ethernet address: 00:23:4d:3c:4b:00 Mar 25 17:09:25 tinyCurrent root: /etc/rc: WARNING: Dump device does not exist. Savecore not run. Mar 25 17:09:37 tinyCurrent login: ROOT LOGIN (root) ON ttyv0 -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ From jnordwick at gmail.com Fri Mar 27 09:31:42 2009 From: jnordwick at gmail.com (Jason Nordwick) Date: Fri Mar 27 09:31:48 2009 Subject: Switching from wired to wireless getting "network down" Message-ID: I just updated to the current -STABLE (7.2-PRERELEASE is the same thing? hopefully). When I boot with the network cable plugged in, but then try to unplug it and up my wireless, it doesn't seem to work although the ifconfig shows I am joined to my wireless network. Is there some magic I need to do to reset the routing tables or something? -j From jnordwick at gmail.com Fri Mar 27 10:04:30 2009 From: jnordwick at gmail.com (Jason Nordwick) Date: Fri Mar 27 10:04:38 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: References: Message-ID: This appears to be the case. "route get 192.168.1.1" (my netgear wireless) shows that it still wants to use bfe0 instead of the wpi0 interface. How do I get it so that when I unplug my cable and my wireless is up, it changes the routing table? -j On Fri, Mar 27, 2009 at 9:31 AM, Jason Nordwick wrote: > I just updated to the current -STABLE (7.2-PRERELEASE is the same thing? > hopefully). > > When I boot with the network cable plugged in, but then try to unplug it > and up my wireless, it doesn't seem to work although the ifconfig shows I am > joined to my wireless network. Is there some magic I need to do to reset the > routing tables or something? > > -j > > From knowtree at aloha.com Fri Mar 27 13:16:36 2009 From: knowtree at aloha.com (knowtree@aloha.com) Date: Fri Mar 27 13:16:43 2009 Subject: Intel 5100AGN ndis driver problem Message-ID: <200903272016.n2RKGZ1m001583@yoda.pixi.com> On 3/21/09, Ganbold wrote: > Paul B. Mahol wrote: >> On 3/19/09, Ganbold wrote: >> >>> Hi, >>> >>> I'm trying to use ndis driver for Intel 5100AGN and got >>> following error: >>> >>> beastie# grep ndis /var/log/messages >>> Mar 19 23:41:21 beastie kernel: ndis0: mem >>> 0xf4300000-0xf4301fff irq 17 at device 0.0 on pci3 >>> Mar 19 23:41:21 beastie kernel: ndis0: [ITHREAD] >>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS API version: 5.1 >>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error) >>> >>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error) >>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x08ff product >>> 0x2810 bus uhub1 >>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x0a5c product >>> 0x2145 bus uhub1 >>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x17ef product >>> 0x1004 bus uhub3 >>> Mar 19 23:41:53 beastie kernel: ugen1.3: at >>> usbus1 (disconnected) >>> Mar 19 23:41:57 beastie kernel: ugen1.3: at usbus1 >>> Mar 19 23:41:57 beastie root: Unknown USB device: vendor 0x0a5c product >>> 0x2145 bus uhub1 >>> Mar 19 23:45:36 beastie kernel: wlan0: Ethernet address: 00:21:6b:9a:23:8e >>> Mar 19 23:52:02 beastie kernel: pid 9861 (initial thread) is using >>> legacy pty devices >>> Mar 20 00:08:06 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error) >>> ... >>> ndis0 at pci0:3:0:0: class=0x028000 card=0x12118086 chip=0x42378086 >>> rev=0x00 hdr=0x00 >>> vendor = 'Intel Corporation' >>> class = network >>> >>> I'm running: >>> beastie# uname -an >>> FreeBSD beastie.micom.mng.net 8.0-CURRENT FreeBSD 8.0-CURRENT #5 >>> r190040M: Thu Mar 19 21:45:37 ULAT 2009 >>> tsgan at beastie.micom.mng.net:/usr/obj/usr/src/sys/DEVIL_WITNESS i386 >>> >>> >>> Any idea how to fix this issue? >>> Please let me know if you need more info. >>> >> >> How you generate ndis module? >> Post whole output _after_ is module loaded >> _not_ just lines containing ndis. >> >> also enable debug.ndis sysctl. >> >I generated module issuing following command: > >ndisgen NETw5x32.inf NETw5x32.sys > >After module is generated, loading modules gives (debug.ndis=1): > > >Mar 21 16:18:33 beastie kernel: no match for KeBugCheck >Mar 21 16:18:33 beastie kernel: ndis0: mem >0xf4300000-0xf4301fff irq 17 at device 0.0 on pci3 >Mar 21 16:18:33 beastie kernel: ndis0: [ITHREAD] >Mar 21 16:18:33 beastie kernel: ndis0: NDIS API version: 5.1 >Mar 21 16:18:33 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error) >Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x08ff product >0x2810 bus uhub1 >Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x0a5c product >0x2145 bus uhub1 >Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x17ef product >0x1004 bus uhub3 >Mar 21 16:18:34 beastie kernel: attach done. >Mar 21 16:18:35 beastie kernel: halting done. > >Ganbold I am seeing the exact same thing on 7.1-RELEASE, minus the USB errors. I have the same Intel chipset in a Fujitsu T1010 laptop. I downloaded the XP driver from Intel, had the same file names as above. When I ran ndisgen it asked me for the names of the files even through I specified them on the command line. Other than that the build process seemed fine. When I used kldload to test it I got the unknown error message but the system seemed happy so I set it up to load from loader.conf and added an entry for it in /etc/rc.conf. When I rebooted the hardware probe hung at the ndis driver. After I managed to boot without the kernel module I tried again to load with kldload. After the NDIS ERROR line I see WARNING: using obsoleted if_watchdog interface Next comes the MAC address, then a page fault followed by a reboot. I tried it several times with same results. Is there anything I can do to help solve this? Again I am running 7.1 not HEAD. Gary Dunn Open Slate Project Honolulu From onemda at gmail.com Fri Mar 27 14:22:37 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Fri Mar 27 14:22:44 2009 Subject: Intel 5100AGN ndis driver problem In-Reply-To: <200903272016.n2RKGZ1m001583@yoda.pixi.com> References: <200903272016.n2RKGZ1m001583@yoda.pixi.com> Message-ID: <3a142e750903271422x6917ff87p663411f27fe63484@mail.gmail.com> On 3/27/09, knowtree@aloha.com wrote: > On 3/21/09, Ganbold wrote: >> Paul B. Mahol wrote: >>> On 3/19/09, Ganbold wrote: >>> >>>> Hi, >>>> >>>> I'm trying to use ndis driver for Intel 5100AGN and got >>>> following error: >>>> >>>> beastie# grep ndis /var/log/messages >>>> Mar 19 23:41:21 beastie kernel: ndis0: mem >>>> 0xf4300000-0xf4301fff irq 17 at device 0.0 on pci3 >>>> Mar 19 23:41:21 beastie kernel: ndis0: [ITHREAD] >>>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS API version: 5.1 >>>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown >>>> error) >>>> >>>> Mar 19 23:41:21 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown >>>> error) >>>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x08ff product >>>> 0x2810 bus uhub1 >>>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x0a5c product >>>> 0x2145 bus uhub1 >>>> Mar 19 23:41:21 beastie root: Unknown USB device: vendor 0x17ef product >>>> 0x1004 bus uhub3 >>>> Mar 19 23:41:53 beastie kernel: ugen1.3: at >>>> usbus1 (disconnected) >>>> Mar 19 23:41:57 beastie kernel: ugen1.3: at >>>> usbus1 >>>> Mar 19 23:41:57 beastie root: Unknown USB device: vendor 0x0a5c product >>>> 0x2145 bus uhub1 >>>> Mar 19 23:45:36 beastie kernel: wlan0: Ethernet address: >>>> 00:21:6b:9a:23:8e >>>> Mar 19 23:52:02 beastie kernel: pid 9861 (initial thread) is using >>>> legacy pty devices >>>> Mar 20 00:08:06 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown >>>> error) >>>> ... >>>> ndis0 at pci0:3:0:0: class=0x028000 card=0x12118086 chip=0x42378086 >>>> rev=0x00 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> class = network >>>> >>>> I'm running: >>>> beastie# uname -an >>>> FreeBSD beastie.micom.mng.net 8.0-CURRENT FreeBSD 8.0-CURRENT #5 >>>> r190040M: Thu Mar 19 21:45:37 ULAT 2009 >>>> tsgan at beastie.micom.mng.net:/usr/obj/usr/src/sys/DEVIL_WITNESS i386 >>>> >>>> >>>> Any idea how to fix this issue? >>>> Please let me know if you need more info. >>>> >>> >>> How you generate ndis module? >>> Post whole output _after_ is module loaded >>> _not_ just lines containing ndis. >>> >>> also enable debug.ndis sysctl. >>> >>I generated module issuing following command: >> >>ndisgen NETw5x32.inf NETw5x32.sys >> >>After module is generated, loading modules gives (debug.ndis=1): >> >> >>Mar 21 16:18:33 beastie kernel: no match for KeBugCheck >>Mar 21 16:18:33 beastie kernel: ndis0: mem >>0xf4300000-0xf4301fff irq 17 at device 0.0 on pci3 >>Mar 21 16:18:33 beastie kernel: ndis0: [ITHREAD] >>Mar 21 16:18:33 beastie kernel: ndis0: NDIS API version: 5.1 >>Mar 21 16:18:33 beastie kernel: ndis0: NDIS ERROR: 40001b7c (unknown error) >>Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x08ff product >>0x2810 bus uhub1 >>Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x0a5c product >>0x2145 bus uhub1 >>Mar 21 16:18:33 beastie root: Unknown USB device: vendor 0x17ef product >>0x1004 bus uhub3 >>Mar 21 16:18:34 beastie kernel: attach done. >>Mar 21 16:18:35 beastie kernel: halting done. >> >>Ganbold > > I am seeing the exact same thing on 7.1-RELEASE, minus the USB errors. I > have the same Intel chipset in a Fujitsu T1010 laptop. I downloaded the XP > driver from Intel, had the same file names as above. When I ran ndisgen it > asked me for the names of the files even through I specified them on the > command line. Other than that the build process seemed fine. When I used > kldload to test it I got the unknown error message but the system seemed > happy so I set it up to load from loader.conf and added an entry for it in > /etc/rc.conf. When I rebooted the hardware probe hung at the ndis driver. > > After I managed to boot without the kernel module I tried again to load > with kldload. After the NDIS ERROR line I see > > WARNING: using obsoleted if_watchdog interface > > Next comes the MAC address, then a page fault followed by a reboot. I tried > it several times with same results. That panic should be fixed in CURRENT, if not, post backtrace from textdump for the start. > Is there anything I can do to help solve this? Again I am running 7.1 not > HEAD. Something in NDISulator initialization code looks to be broken, but current showstopper are error codes that are not documented anywhere. -- Paul From oberman at es.net Fri Mar 27 18:59:47 2009 From: oberman at es.net (Kevin Oberman) Date: Fri Mar 27 18:59:53 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: Your message of "Fri, 27 Mar 2009 10:04:29 PDT." Message-ID: <20090328015944.D382F1CC09@ptavv.es.net> > Date: Fri, 27 Mar 2009 10:04:29 -0700 > From: Jason Nordwick > Sender: owner-freebsd-mobile@freebsd.org > > This appears to be the case. "route get 192.168.1.1" (my netgear wireless) > shows that it still wants to use bfe0 instead of the wpi0 interface. How do > I get it so that when I unplug my cable and my wireless is up, it changes > the routing table? > > -j > > > On Fri, Mar 27, 2009 at 9:31 AM, Jason Nordwick wrote: > > > I just updated to the current -STABLE (7.2-PRERELEASE is the same thing? > > hopefully). > > > > When I boot with the network cable plugged in, but then try to unplug it > > and up my wireless, it doesn't seem to work although the ifconfig shows I am > > joined to my wireless network. Is there some magic I need to do to reset the > > routing tables or something? It make it really hard to follow a thread. > Why not? > > Please don't top post. Depends on your configuration. Do you use DHCP or static network configurations? If it is DHCP, I suspect /etc/rc.d/dhclient restart would do the trick. If it is status: route add default abc.def.gh.ij should do the trick. Going the other way can be a tiny bit more involved. 'ifconfig wlan0 down' first or 'route delete default' to get rid of the current static. (Note: wlan0 on stable needs to be replaced with the name of your wireless interface.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From jpc at porterclark.com Sat Mar 28 09:26:16 2009 From: jpc at porterclark.com (J. Porter Clark) Date: Sat Mar 28 09:26:23 2009 Subject: Switching from wired to wireless getting "network down" References: <1238217783.00093348.1238205603@10.7.7.3> Message-ID: <20090328160858.GA57695@auricle.charter.net> >> Date: Fri, 27 Mar 2009 10:04:29 -0700 >> From: Jason Nordwick >> Sender: owner-freebsd-mobile@freebsd.org >> >> This appears to be the case. "route get 192.168.1.1" (my netgear wireless) >> shows that it still wants to use bfe0 instead of the wpi0 interface. How do >> I get it so that when I unplug my cable and my wireless is up, it changes >> the routing table? >> >> -j >> >> >> On Fri, Mar 27, 2009 at 9:31 AM, Jason Nordwick wrote: >> >> > I just updated to the current -STABLE (7.2-PRERELEASE is the same thing? >> > hopefully). >> > >> > When I boot with the network cable plugged in, but then try to unplug it >> > and up my wireless, it doesn't seem to work although the ifconfig shows I am >> > joined to my wireless network. Is there some magic I need to do to reset the >> > routing tables or something? >Depends on your configuration. Do you use DHCP or static network >configurations? If it is DHCP, I suspect /etc/rc.d/dhclient restart >would do the trick. If it is status: >route add default abc.def.gh.ij >should do the trick. >Going the other way can be a tiny bit more involved. 'ifconfig wlan0 >down' first or 'route delete default' to get rid of the current >static. (Note: wlan0 on stable needs to be replaced with the name of >your wireless interface.) I've been playing around with this sort of setup, too, where I want a command line to change from wired to wireless (at the same IP address, even) and back again. I haven't found the magic solution, particularly one that doesn't have a lot of hardcoded network config in it. I'm also somewhat ticked that "route flush" doesn't really flush all routes like the man page says. 8-) Eventually, I usually arrive at a point where I can't find my way back and have to reboot to get some work done. Some things I've been using are "route delete " and "route add -ifp default". Might be a good idea to "arp -a -d", too. -- J. Porter Clark From sam at freebsd.org Sat Mar 28 09:35:47 2009 From: sam at freebsd.org (Sam Leffler) Date: Sat Mar 28 09:35:54 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <20090328160858.GA57695@auricle.charter.net> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> Message-ID: <49CE51E2.4000807@freebsd.org> J. Porter Clark wrote: >>> Date: Fri, 27 Mar 2009 10:04:29 -0700 >>> From: Jason Nordwick >>> Sender: owner-freebsd-mobile@freebsd.org >>> >>> This appears to be the case. "route get 192.168.1.1" (my netgear wireless) >>> shows that it still wants to use bfe0 instead of the wpi0 interface. How do >>> I get it so that when I unplug my cable and my wireless is up, it changes >>> the routing table? >>> >>> -j >>> >>> >>> On Fri, Mar 27, 2009 at 9:31 AM, Jason Nordwick wrote: >>> >>> >>>> I just updated to the current -STABLE (7.2-PRERELEASE is the same thing? >>>> hopefully). >>>> >>>> When I boot with the network cable plugged in, but then try to unplug it >>>> and up my wireless, it doesn't seem to work although the ifconfig shows I am >>>> joined to my wireless network. Is there some magic I need to do to reset the >>>> routing tables or something? >>>> > > >> Depends on your configuration. Do you use DHCP or static network >> configurations? If it is DHCP, I suspect /etc/rc.d/dhclient restart >> would do the trick. If it is status: >> route add default abc.def.gh.ij >> should do the trick. >> > > >> Going the other way can be a tiny bit more involved. 'ifconfig wlan0 >> down' first or 'route delete default' to get rid of the current >> static. (Note: wlan0 on stable needs to be replaced with the name of >> your wireless interface.) >> > > I've been playing around with this sort of setup, too, where I > want a command line to change from wired to wireless (at the > same IP address, even) and back again. I haven't found the > magic solution, particularly one that doesn't have a lot of > hardcoded network config in it. I'm also somewhat ticked that > "route flush" doesn't really flush all routes like the man page > says. 8-) Eventually, I usually arrive at a point where I can't > find my way back and have to reboot to get some work done. > > Some things I've been using are "route delete " > and "route add -ifp default". Might be a good idea > to "arp -a -d", too. > > If this is 7.x or later, have you tried using lagg(4) to do automatic failover? The man page says wpa doesn't work but after talking to Andrew we think that's no longer true. I haven't had a chance to try it myself. Sam From sam at freebsd.org Sat Mar 28 09:46:27 2009 From: sam at freebsd.org (Sam Leffler) Date: Sat Mar 28 09:47:40 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <20090328164216.GA68623@citylink.fud.org.nz> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <20090328164216.GA68623@citylink.fud.org.nz> Message-ID: <49CE5462.1010105@freebsd.org> Andrew Thompson wrote: > On Sat, Mar 28, 2009 at 09:35:46AM -0700, Sam Leffler wrote: > >> J. Porter Clark wrote: >> >>> >>> >>>> Depends on your configuration. Do you use DHCP or static network >>>> configurations? If it is DHCP, I suspect /etc/rc.d/dhclient restart >>>> would do the trick. If it is status: >>>> route add default abc.def.gh.ij >>>> should do the trick. >>>> >>> >>> >>>> Going the other way can be a tiny bit more involved. 'ifconfig wlan0 >>>> down' first or 'route delete default' to get rid of the current >>>> static. (Note: wlan0 on stable needs to be replaced with the name of >>>> your wireless interface.) >>>> >>>> >>> I've been playing around with this sort of setup, too, where I >>> want a command line to change from wired to wireless (at the >>> same IP address, even) and back again. I haven't found the >>> magic solution, particularly one that doesn't have a lot of >>> hardcoded network config in it. I'm also somewhat ticked that >>> "route flush" doesn't really flush all routes like the man page >>> says. 8-) Eventually, I usually arrive at a point where I can't >>> find my way back and have to reboot to get some work done. >>> >>> Some things I've been using are "route delete " >>> and "route add -ifp default". Might be a good idea >>> to "arp -a -d", too. >>> >>> >>> >> If this is 7.x or later, have you tried using lagg(4) to do automatic >> failover? The man page says wpa doesn't work but after talking to Andrew >> we think that's no longer true. I haven't had a chance to try it myself. >> > > This is becuase lagg(4) will set the interface down/up when grabbing it > and wpa_supplicant does not get restarted. This may work now but looking > through /etc/devd.conf I dont see a rule to handle it (only ATTACH and > LINK_UP events). A new devd event may need to be added to handle this > situation. Patches welcome. > I believe LINK_UP should be sufficient but we need to check. Sam From oberman at es.net Sat Mar 28 09:53:06 2009 From: oberman at es.net (Kevin Oberman) Date: Sat Mar 28 09:53:13 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: Your message of "Sat, 28 Mar 2009 11:08:58 CDT." <20090328160858.GA57695@auricle.charter.net> Message-ID: <20090328165304.B566F1CC09@ptavv.es.net> > Date: Sat, 28 Mar 2009 11:08:58 -0500 > From: "J. Porter Clark" > Sender: owner-freebsd-mobile@freebsd.org > > >> Date: Fri, 27 Mar 2009 10:04:29 -0700 > >> From: Jason Nordwick > >> Sender: owner-freebsd-mobile@freebsd.org > >> > >> This appears to be the case. "route get 192.168.1.1" (my netgear wireless) > >> shows that it still wants to use bfe0 instead of the wpi0 interface. How do > >> I get it so that when I unplug my cable and my wireless is up, it changes > >> the routing table? > >> > >> -j > >> > >> > >> On Fri, Mar 27, 2009 at 9:31 AM, Jason Nordwick wrote: > >> > >> > I just updated to the current -STABLE (7.2-PRERELEASE is the same thing? > >> > hopefully). > >> > > >> > When I boot with the network cable plugged in, but then try to unplug it > >> > and up my wireless, it doesn't seem to work although the ifconfig shows I am > >> > joined to my wireless network. Is there some magic I need to do to reset the > >> > routing tables or something? > > >Depends on your configuration. Do you use DHCP or static network > >configurations? If it is DHCP, I suspect /etc/rc.d/dhclient restart > >would do the trick. If it is status: > >route add default abc.def.gh.ij > >should do the trick. > > >Going the other way can be a tiny bit more involved. 'ifconfig wlan0 > >down' first or 'route delete default' to get rid of the current > >static. (Note: wlan0 on stable needs to be replaced with the name of > >your wireless interface.) > > I've been playing around with this sort of setup, too, where I > want a command line to change from wired to wireless (at the > same IP address, even) and back again. I haven't found the > magic solution, particularly one that doesn't have a lot of > hardcoded network config in it. I'm also somewhat ticked that > "route flush" doesn't really flush all routes like the man page > says. 8-) Eventually, I usually arrive at a point where I can't > find my way back and have to reboot to get some work done. > > Some things I've been using are "route delete " > and "route add -ifp default". Might be a good idea > to "arp -a -d", too. OK. Here is the script I use to switch between the wired and wireless at work. I use it often, so I know it works with 7.1-Stable of early February. It switches between wired (bge0) and wireless (ath0). All addressing is static on bge0 and DHCP on ath0, though this really does not matter if your rc.conf is correct for both interfaces. By using the rc.d scripts, I take care of a lot of annoying details because they already DTRT. #!/usr/bin/perl use strict; my ($data); # Get the current default route interface ($data) = `netstat -rnf inet | grep default`; if (grep /bge0/, $data) { # Move to wireless (ath0) # make sure that the wireless driver is loaded! $data = `kldstat | grep if_ath.ko`; if ($?) {`kldload if_ath`;} # Move to wireless (ath0) ($data) = `/etc/rc.d/routing stop`; print $data; ($data) = `/etc/rc.d/netif stop bge0`; print $data; ($data) = `/etc/rc.d/netif start ath0`; print $data; print "Connected via wireless\n"; } else { # Move to .1 wire (bge0) ($data) = `/etc/rc.d/netif stop ath0`; print $data; ($data) = `route delete default`; print $data; ($data) = `/etc/rc.d/netif start bge0`; print $data; ($data) = `/etc/rc.d/routing start`; print $data; print STDERR "Connected via ESnet on bge0\n"; } -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From jnordwick at gmail.com Sat Mar 28 09:56:22 2009 From: jnordwick at gmail.com (Jason Nordwick) Date: Sat Mar 28 09:56:28 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49CE51E2.4000807@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> Message-ID: That busted my networking. I did: kldload if_lagg ifconfig lagg0 create ifconfig lagg0 lagproto failover lagport bfe0 lagport wpi0 192.168.1.1 netmask 255.255.255.0 Now when I ping 192.168.1.1, I get a "device busy" messages from ping. Oops. I think I need to reboot to clear this up. -j On Sat, Mar 28, 2009 at 9:35 AM, Sam Leffler wrote: > J. Porter Clark wrote: > >> Date: Fri, 27 Mar 2009 10:04:29 -0700 >>>> From: Jason Nordwick >>>> Sender: owner-freebsd-mobile@freebsd.org >>>> >>>> This appears to be the case. "route get 192.168.1.1" (my netgear >>>> wireless) >>>> shows that it still wants to use bfe0 instead of the wpi0 interface. How >>>> do >>>> I get it so that when I unplug my cable and my wireless is up, it >>>> changes >>>> the routing table? >>>> >>>> -j >>>> >>>> >>>> On Fri, Mar 27, 2009 at 9:31 AM, Jason Nordwick >>>> wrote: >>>> >>>> >>>> >>>>> I just updated to the current -STABLE (7.2-PRERELEASE is the same >>>>> thing? >>>>> hopefully). >>>>> >>>>> When I boot with the network cable plugged in, but then try to unplug >>>>> it >>>>> and up my wireless, it doesn't seem to work although the ifconfig shows >>>>> I am >>>>> joined to my wireless network. Is there some magic I need to do to >>>>> reset the >>>>> routing tables or something? >>>>> >>>>> >>>> >> >> >>> Depends on your configuration. Do you use DHCP or static network >>> configurations? If it is DHCP, I suspect /etc/rc.d/dhclient restart >>> would do the trick. If it is status: >>> route add default abc.def.gh.ij >>> should do the trick. >>> >> >> >> >>> Going the other way can be a tiny bit more involved. 'ifconfig wlan0 >>> down' first or 'route delete default' to get rid of the current >>> static. (Note: wlan0 on stable needs to be replaced with the name of >>> your wireless interface.) >>> >>> >> >> I've been playing around with this sort of setup, too, where I >> want a command line to change from wired to wireless (at the >> same IP address, even) and back again. I haven't found the >> magic solution, particularly one that doesn't have a lot of >> hardcoded network config in it. I'm also somewhat ticked that >> "route flush" doesn't really flush all routes like the man page >> says. 8-) Eventually, I usually arrive at a point where I can't >> find my way back and have to reboot to get some work done. >> >> Some things I've been using are "route delete " >> and "route add -ifp default". Might be a good idea >> to "arp -a -d", too. >> >> >> > If this is 7.x or later, have you tried using lagg(4) to do automatic > failover? The man page says wpa doesn't work but after talking to Andrew we > think that's no longer true. I haven't had a chance to try it myself. > > Sam > > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > From jpc at porterclark.com Sat Mar 28 10:05:54 2009 From: jpc at porterclark.com (J. Porter Clark) Date: Sat Mar 28 10:06:06 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49CE5462.1010105@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <20090328164216.GA68623@citylink.fud.org.nz> <49CE5462.1010105@freebsd.org> Message-ID: <20090328170551.GA58425@auricle.charter.net> On Sat, Mar 28, 2009 at 09:46:26AM -0700, Sam Leffler wrote: > > Andrew Thompson wrote: > > On Sat, Mar 28, 2009 at 09:35:46AM -0700, Sam Leffler wrote: > > > >> J. Porter Clark wrote: > >>>> > >>> I've been playing around with this sort of setup, too, where I > >>> want a command line to change from wired to wireless (at the > >>> same IP address, even) and back again. I haven't found the > >>> magic solution, particularly one that doesn't have a lot of > >>> hardcoded network config in it. I'm also somewhat ticked that > >>> "route flush" doesn't really flush all routes like the man page > >>> says. 8-) Eventually, I usually arrive at a point where I can't > >>> find my way back and have to reboot to get some work done. > >>> > >>> Some things I've been using are "route delete " > >>> and "route add -ifp default". Might be a good idea > >>> to "arp -a -d", too. > >>> > >> If this is 7.x or later, have you tried using lagg(4) to do automatic > >> failover? The man page says wpa doesn't work but after talking to Andrew > >> we think that's no longer true. I haven't had a chance to try it myself. > > > > This is becuase lagg(4) will set the interface down/up when grabbing it > > and wpa_supplicant does not get restarted. This may work now but looking > > through /etc/devd.conf I dont see a rule to handle it (only ATTACH and > > LINK_UP events). A new devd event may need to be added to handle this > > situation. Patches welcome. > > I believe LINK_UP should be sufficient but we need to check. FreeBSD-STABLE (says 7.2-PRERELEASE at the moment). I haven't tried lagg(4), because I didn't know it existed, but I will look into it--it sounds like just what I need, if it works! In fact, I am only doing WEP on this network. The laptop that I'm using is an employer-issued Dell Latitude E6500, which has the dreaded Intel 5100AGN among its faults. To get wireless working, I'm ignoring that and using an old Agere Orinoco Gold card (wi), which AFAIK doesn't know how to do WPA--I could be wrong. The reason I'm having to switch between it and the wired interface is that I can get no better than about 3 Mbps through the wireless card, and I actually have 10 Mbps downlink service here. So I do wired when I need performance and wireless when I need mobility, at least until support for the 5100 arrives. -- J. Porter Clark From deischen at freebsd.org Sat Mar 28 10:09:21 2009 From: deischen at freebsd.org (Daniel Eischen) Date: Sat Mar 28 10:09:30 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49CE51E2.4000807@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> Message-ID: On Sat, 28 Mar 2009, Sam Leffler wrote: > J. Porter Clark wrote: >> I've been playing around with this sort of setup, too, where I >> want a command line to change from wired to wireless (at the >> same IP address, even) and back again. I haven't found the >> magic solution, particularly one that doesn't have a lot of >> hardcoded network config in it. I'm also somewhat ticked that >> "route flush" doesn't really flush all routes like the man page >> says. 8-) Eventually, I usually arrive at a point where I can't >> find my way back and have to reboot to get some work done. >> >> Some things I've been using are "route delete " >> and "route add -ifp default". Might be a good idea >> to "arp -a -d", too. >> >> > If this is 7.x or later, have you tried using lagg(4) to do automatic > failover? The man page says wpa doesn't work but after talking to Andrew we > think that's no longer true. I haven't had a chance to try it myself. Yeah, but as far as I can recall, lagg isn't able to change the MAC address on the cloned wlanX interface. lagg with wireless and wired interfaces used to work before wlan cloning was added. I haven't tested it in a while, though. Has this been fixed? -- DE From thompsa at FreeBSD.org Sat Mar 28 10:09:53 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sat Mar 28 10:09:59 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49CE51E2.4000807@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> Message-ID: <20090328164216.GA68623@citylink.fud.org.nz> On Sat, Mar 28, 2009 at 09:35:46AM -0700, Sam Leffler wrote: > J. Porter Clark wrote: >> >>> Depends on your configuration. Do you use DHCP or static network >>> configurations? If it is DHCP, I suspect /etc/rc.d/dhclient restart >>> would do the trick. If it is status: >>> route add default abc.def.gh.ij >>> should do the trick. >> >> >>> Going the other way can be a tiny bit more involved. 'ifconfig wlan0 >>> down' first or 'route delete default' to get rid of the current >>> static. (Note: wlan0 on stable needs to be replaced with the name of >>> your wireless interface.) >>> >> >> I've been playing around with this sort of setup, too, where I >> want a command line to change from wired to wireless (at the >> same IP address, even) and back again. I haven't found the >> magic solution, particularly one that doesn't have a lot of >> hardcoded network config in it. I'm also somewhat ticked that >> "route flush" doesn't really flush all routes like the man page >> says. 8-) Eventually, I usually arrive at a point where I can't >> find my way back and have to reboot to get some work done. >> >> Some things I've been using are "route delete " >> and "route add -ifp default". Might be a good idea >> to "arp -a -d", too. >> >> > If this is 7.x or later, have you tried using lagg(4) to do automatic > failover? The man page says wpa doesn't work but after talking to Andrew > we think that's no longer true. I haven't had a chance to try it myself. This is becuase lagg(4) will set the interface down/up when grabbing it and wpa_supplicant does not get restarted. This may work now but looking through /etc/devd.conf I dont see a rule to handle it (only ATTACH and LINK_UP events). A new devd event may need to be added to handle this situation. Patches welcome. Andrew From sam at freebsd.org Sat Mar 28 10:17:10 2009 From: sam at freebsd.org (Sam Leffler) Date: Sat Mar 28 10:19:09 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> Message-ID: <49CE5B95.1010502@freebsd.org> Daniel Eischen wrote: > On Sat, 28 Mar 2009, Sam Leffler wrote: > >> J. Porter Clark wrote: >>> I've been playing around with this sort of setup, too, where I >>> want a command line to change from wired to wireless (at the >>> same IP address, even) and back again. I haven't found the >>> magic solution, particularly one that doesn't have a lot of >>> hardcoded network config in it. I'm also somewhat ticked that >>> "route flush" doesn't really flush all routes like the man page >>> says. 8-) Eventually, I usually arrive at a point where I can't >>> find my way back and have to reboot to get some work done. >>> >>> Some things I've been using are "route delete " >>> and "route add -ifp default". Might be a good idea >>> to "arp -a -d", too. >>> >>> >> If this is 7.x or later, have you tried using lagg(4) to do automatic >> failover? The man page says wpa doesn't work but after talking to >> Andrew we think that's no longer true. I haven't had a chance to try >> it myself. > > Yeah, but as far as I can recall, lagg isn't able to change the > MAC address on the cloned wlanX interface. lagg with wireless > and wired interfaces used to work before wlan cloning was added. > I haven't tested it in a while, though. Has this been fixed? > You can change the mac address of a wlan ifnet (just verified); the problem is that it needs to be propagated to the physical ifnet as well for it to matter (the right thing happens if you do it when you clone the ifnet but not if you force it after, and I'm not sure you can make it work). I'm starting to remember now about this. Was there a PR filed? I completely forgot about this issue and it's likely to happen again w/o one. Sam From deischen at freebsd.org Sat Mar 28 15:49:46 2009 From: deischen at freebsd.org (Daniel Eischen) Date: Sat Mar 28 15:49:52 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49CE5B95.1010502@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <49CE5B95.1010502@freebsd.org> Message-ID: On Sat, 28 Mar 2009, Sam Leffler wrote: > Daniel Eischen wrote: >> On Sat, 28 Mar 2009, Sam Leffler wrote: >> >>> J. Porter Clark wrote: >>>> I've been playing around with this sort of setup, too, where I >>>> want a command line to change from wired to wireless (at the >>>> same IP address, even) and back again. I haven't found the >>>> magic solution, particularly one that doesn't have a lot of >>>> hardcoded network config in it. I'm also somewhat ticked that >>>> "route flush" doesn't really flush all routes like the man page >>>> says. 8-) Eventually, I usually arrive at a point where I can't >>>> find my way back and have to reboot to get some work done. >>>> >>>> Some things I've been using are "route delete " >>>> and "route add -ifp default". Might be a good idea >>>> to "arp -a -d", too. >>>> >>>> >>> If this is 7.x or later, have you tried using lagg(4) to do automatic >>> failover? The man page says wpa doesn't work but after talking to Andrew >>> we think that's no longer true. I haven't had a chance to try it myself. >> >> Yeah, but as far as I can recall, lagg isn't able to change the >> MAC address on the cloned wlanX interface. lagg with wireless >> and wired interfaces used to work before wlan cloning was added. >> I haven't tested it in a while, though. Has this been fixed? >> > You can change the mac address of a wlan ifnet (just verified); the problem > is that it needs to be propagated to the physical ifnet as well for it to > matter (the right thing happens if you do it when you clone the ifnet but not Right, that's what I meant above - the MAC gets set on wlan0, but not on ath0, for instance. > if you force it after, and I'm not sure you can make it work). I'm starting > to remember now about this. Was there a PR filed? I completely forgot about > this issue and it's likely to happen again w/o one. No, there's no PR as far as I can tell. I'll try and set up a test system to duplicate it again, so I have proper information for a PR. I seem to recall that if wlanX is your primary/first lagg interface, then it uses the MAC address from the underlying interface as lagg's MAC address. In this case it works, but that's not the usual case 'cause you'd rather use a faster wired interface first if it exists. So this works: ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 but this doesn't: ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 In the latter case, lagg only works when bge0 is up. -- DE From sam at freebsd.org Sat Mar 28 15:55:17 2009 From: sam at freebsd.org (Sam Leffler) Date: Sat Mar 28 15:55:23 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <49CE5B95.1010502@freebsd.org> Message-ID: <49CEAAD2.7050203@freebsd.org> Daniel Eischen wrote: > On Sat, 28 Mar 2009, Sam Leffler wrote: > >> Daniel Eischen wrote: >>> On Sat, 28 Mar 2009, Sam Leffler wrote: >>> >>>> J. Porter Clark wrote: >>>>> I've been playing around with this sort of setup, too, where I >>>>> want a command line to change from wired to wireless (at the >>>>> same IP address, even) and back again. I haven't found the >>>>> magic solution, particularly one that doesn't have a lot of >>>>> hardcoded network config in it. I'm also somewhat ticked that >>>>> "route flush" doesn't really flush all routes like the man page >>>>> says. 8-) Eventually, I usually arrive at a point where I can't >>>>> find my way back and have to reboot to get some work done. >>>>> >>>>> Some things I've been using are "route delete " >>>>> and "route add -ifp default". Might be a good idea >>>>> to "arp -a -d", too. >>>>> >>>>> >>>> If this is 7.x or later, have you tried using lagg(4) to do >>>> automatic failover? The man page says wpa doesn't work but after >>>> talking to Andrew we think that's no longer true. I haven't had a >>>> chance to try it myself. >>> >>> Yeah, but as far as I can recall, lagg isn't able to change the >>> MAC address on the cloned wlanX interface. lagg with wireless >>> and wired interfaces used to work before wlan cloning was added. >>> I haven't tested it in a while, though. Has this been fixed? >>> >> You can change the mac address of a wlan ifnet (just verified); the >> problem is that it needs to be propagated to the physical ifnet as >> well for it to matter (the right thing happens if you do it when you >> clone the ifnet but not > > Right, that's what I meant above - the MAC gets set on wlan0, > but not on ath0, for instance. > >> if you force it after, and I'm not sure you can make it work). I'm >> starting to remember now about this. Was there a PR filed? I >> completely forgot about this issue and it's likely to happen again >> w/o one. > > No, there's no PR as far as I can tell. I'll try and set up a > test system to duplicate it again, so I have proper information > for a PR. > > I seem to recall that if wlanX is your primary/first lagg > interface, then it uses the MAC address from the underlying > interface as lagg's MAC address. In this case it works, > but that's not the usual case 'cause you'd rather use a > faster wired interface first if it exists. > > So this works: > > ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 > > but this doesn't: > > ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 > > In the latter case, lagg only works when bge0 is up. > I'm fixing various issues in handling the mac address (in head). I can now use lagg w/o wpa so long as you force the mac address manually. If there had been a PR this problem would not have been lost. Sam From deischen at freebsd.org Sat Mar 28 15:56:39 2009 From: deischen at freebsd.org (Daniel Eischen) Date: Sat Mar 28 15:56:46 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <49CE5B95.1010502@freebsd.org> Message-ID: On Sat, 28 Mar 2009, Daniel Eischen wrote: > No, there's no PR as far as I can tell. I'll try and set up a > test system to duplicate it again, so I have proper information > for a PR. > > I seem to recall that if wlanX is your primary/first lagg > interface, then it uses the MAC address from the underlying > interface as lagg's MAC address. In this case it works, > but that's not the usual case 'cause you'd rather use a > faster wired interface first if it exists. > > So this works: > > ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 > > but this doesn't: > > ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 > > In the latter case, lagg only works when bge0 is up. Also note that lagg(4) still references ath0 in its example instead of wlan0. # ifconfig em0 up # ifconfig ath0 nwid my_net up # ifconfig lagg0 laggproto failover laggport em0 laggport ath0 \ 192.168.1.1 netmask 255.255.255.0 -- DE From deischen at freebsd.org Sat Mar 28 16:01:57 2009 From: deischen at freebsd.org (Daniel Eischen) Date: Sat Mar 28 16:02:04 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49CEAAD2.7050203@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <49CE5B95.1010502@freebsd.org> <49CEAAD2.7050203@freebsd.org> Message-ID: On Sat, 28 Mar 2009, Sam Leffler wrote: > Daniel Eischen wrote: >> On Sat, 28 Mar 2009, Sam Leffler wrote: >> >>> if you force it after, and I'm not sure you can make it work). I'm >>> starting to remember now about this. Was there a PR filed? I completely >>> forgot about this issue and it's likely to happen again w/o one. >> >> No, there's no PR as far as I can tell. I'll try and set up a >> test system to duplicate it again, so I have proper information >> for a PR. >> >> I seem to recall that if wlanX is your primary/first lagg >> interface, then it uses the MAC address from the underlying >> interface as lagg's MAC address. In this case it works, >> but that's not the usual case 'cause you'd rather use a >> faster wired interface first if it exists. >> >> So this works: >> >> ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 >> >> but this doesn't: >> >> ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 >> >> In the latter case, lagg only works when bge0 is up. >> > > I'm fixing various issues in handling the mac address (in head). I can now > use lagg w/o wpa so long as you force the mac address manually. If there > had been a PR this problem would not have been lost. I am sorry :( I do remember trying to figure out how to do this myself and did have an outstanding email with you and/or Andrew that went unanswered. I got side-tracked on something else after that and never got back to it. -- DE From thompsa at FreeBSD.org Sat Mar 28 16:30:28 2009 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Sat Mar 28 16:30:35 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <49CE5B95.1010502@freebsd.org> <49CEAAD2.7050203@freebsd.org> Message-ID: <20090328233023.GA69292@citylink.fud.org.nz> On Sat, Mar 28, 2009 at 07:01:55PM -0400, Daniel Eischen wrote: > On Sat, 28 Mar 2009, Sam Leffler wrote: > >> Daniel Eischen wrote: >>> On Sat, 28 Mar 2009, Sam Leffler wrote: >>>> Daniel Eischen wrote: >>> So this works: >>> >>> ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 >>> >>> but this doesn't: >>> >>> ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 >>> >>> In the latter case, lagg only works when bge0 is up. >>> >> >> I'm fixing various issues in handling the mac address (in head). I can >> now use lagg w/o wpa so long as you force the mac address manually. If >> there had been a PR this problem would not have been lost. > > I am sorry :( I do remember trying to figure out how to do this > myself and did have an outstanding email with you and/or Andrew that > went unanswered. I got side-tracked on something else after that > and never got back to it. Probably me, sorry about that. Andrew From mialinx at gmail.com Sun Mar 29 06:11:08 2009 From: mialinx at gmail.com (Dmitry Smal) Date: Sun Mar 29 06:11:14 2009 Subject: FreeBSD 7.1 RELEASE looses wi-fi connection on Thinkpad R61i (Intel 3945ABG) or even crashes Message-ID: <49CF5F8A.5010700@rambler.ru> Hi all, I have Thinkpad R61i (with Intel(R) PRO/Wireless 3945ABG wi-fi adapter) running FreeBSD 7.1 RELEASE. Access point is ASUS WiFi-AP Solo (embeded in ASUS P5B-MX motherboard) Sometimes (2 - 3 time in hour) FreeBSD loses wifi connection to AP. In some cases connections appears again after 2-3 minutes, in some cases i need to /etc/rc.d/wpa_supplicant restart wpi0 to restart connection, in rare cases system crashes, leaving dump. I had similar problem running Ubuntu 8.10 on the same notebook (exept for crashes), and no problem running windows xp. Could you help me to fix at least crashes of system ? System: FreeBSD nuftop.zunet.ru 7.1-RELEASE FreeBSD 7.1-RELEASE #5: Thu Feb 26 02:06:03 MSK 2009 root@nuftop.zunet.ru:/usr/obj/usr/src/sys/NUF i386 Dmesg: [nuf@nuftop /usr/home/nuf]$ dmesg | grep Intel | grep wpi wpi0: mem 0xdf6ff000-0xdf6fffff irq 17 at device 0.0 on pci3 Loaded modules: [nuf@nuftop /usr/home/nuf]$ uname -a[nuf@nuftop /usr/home/nuf]$ kldstat Id Refs Address Size Name 1 25 0xc0400000 689f30 kernel 2 1 0xc0a8a000 155e4 snd_hda.ko 3 2 0xc0aa0000 4a64c sound.ko 4 1 0xc0aeb000 55d0 acpi_video.ko 5 3 0xc0af1000 6a2c4 acpi.ko 6 1 0xc0b5c000 25f60 wpifw.ko 7 1 0xc0b82000 de14 if_wpi.ko 8 1 0xc0b90000 4f54 acpi_ibm.ko 9 1 0xc435a000 22000 linux.ko 10 1 0xc43da000 4000 logo_saver.ko 11 1 0xc4436000 6000 i915.ko 12 1 0xc4448000 f000 drm.ko Wlan kernel conf: # Wireless NIC cards device wlan # 802.11 support device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device wlan_amrr # AMRR transmit rate control algorithm device wlan_scan_ap # 802.11 AP mode scanning device wlan_scan_sta # 802.11 STA mode scanning Wpa_supplicant.conf: [nuf@nuftop /usr/home/nuf]$ cat /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel eapol_version=1 fast_reauth=0 network={ ssid="TASHA" scan_ssid=1 proto=WPA2 key_mgmt=WPA-PSK pairwise=CCMP group=CCMP psk="nobodyknows" } Stack trace form coredump after crash (dump itself is too big..): (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc06394b7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0639789 in panic (fmt=Variable "fmt" is not available.) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc089beac in trap_fatal (frame=0xe4059ba0, eva=65535) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc089c130 in trap_pfault (frame=0xe4059ba0, usermode=0, eva=65535) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc089caec in trap (frame=0xe4059ba0) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc088295b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc0b8bdfc in wpi_ops (arg0=0xc3c62000, pending=1) at /usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:2411 #8 0xc066c8c5 in taskqueue_run (queue=0xc3c1e900) at /usr/src/sys/kern/subr_taskqueue.c:282 #9 0xc066cacb in taskqueue_thread_loop (arg=0xc3c639b4) at /usr/src/sys/kern/subr_taskqueue.c:401 #10 0xc0615029 in fork_exit (callout=0xc066ca10 , arg=0xc3c639b4, frame=0xe4059d38) at /usr/src/sys/kern/kern_fork.c:804 #11 0xc08829d0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 Typical ifconfig output when connection is up: [nuf@nuftop /usr/home/nuf]$ ifconfig wpi0 wpi0: flags=8843 metric 0 mtu 1500 ether 00:1c:bf:85:cd:3a inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) status: associated ssid TASHA channel 1 (2412 Mhz 11g) bssid 00:15:af:19:85:32 authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 50 bmiss 7 scanvalid 60 protmode CTS roaming MANUAL Thanks! P.S. Sorry for my poor english =( From davidb at boothscientific.com Sun Mar 29 08:11:05 2009 From: davidb at boothscientific.com (David Booth) Date: Sun Mar 29 08:11:12 2009 Subject: FreeBSD 7.1 RELEASE looses wi-fi connection on Thinkpad R61i (Intel 3945ABG) or even crashes In-Reply-To: <49CF5F8A.5010700@rambler.ru> References: <49CF5F8A.5010700@rambler.ru> Message-ID: <200903291010.56432.davidb@boothscientific.com> On Sunday 29 March 2009, Dmitry Smal wrote: > Hi all, > > I have Thinkpad R61i (with Intel(R) PRO/Wireless 3945ABG wi-fi > adapter) running FreeBSD 7.1 RELEASE. > > Access point is ASUS WiFi-AP Solo (embeded in ASUS P5B-MX > motherboard) > > Sometimes (2 - 3 time in hour) FreeBSD loses wifi connection to AP. > In some cases connections appears again after 2-3 minutes, > in some cases i need to /etc/rc.d/wpa_supplicant restart wpi0 to > restart connection, > in rare cases system crashes, leaving dump. > > I had similar problem running Ubuntu 8.10 on the same notebook > (exept for crashes), > and no problem running windows xp. > I had similar experience with the 3945 on my Dell. It would loose connection in FreeBSD, but worked fine in windows. After much experimenting, I found that it was related to the encryption settings. If I switched from using wpa2 to WEP, everything was stable. Then I got another clue when my Mother had the same problem with her McIntosh computer loosing connection with wpa2 and her router. When she got another router, her problems went away. It turned out that the issue was a problem between the implementation of wpa2 in the Netgear access point and FreeBSD. When I got a new access point (a linksys) everything worked fine with wpa2 and I keep connecitons with no difficulties From ivakras1 at gmail.com Sun Mar 29 10:00:44 2009 From: ivakras1 at gmail.com (Dmitry Kolosov) Date: Sun Mar 29 10:00:51 2009 Subject: FreeBSD 7.1 RELEASE looses wi-fi connection on Thinkpad R61i (Intel 3945ABG) or even crashes In-Reply-To: <49CF5F8A.5010700@rambler.ru> References: <49CF5F8A.5010700@rambler.ru> Message-ID: <200903292058.54180.ivakras1@gmail.com> On ??????????? 29 ????? 2009 15:46:18 Dmitry Smal wrote: > Hi all, > > I have Thinkpad R61i (with Intel(R) PRO/Wireless 3945ABG wi-fi adapter) > running FreeBSD 7.1 RELEASE. > > Access point is ASUS WiFi-AP Solo (embeded in ASUS P5B-MX motherboard) > > Sometimes (2 - 3 time in hour) FreeBSD loses wifi connection to AP. > In some cases connections appears again after 2-3 minutes, > in some cases i need to /etc/rc.d/wpa_supplicant restart wpi0 to restart > connection, > in rare cases system crashes, leaving dump. > > I had similar problem running Ubuntu 8.10 on the same notebook (exept > for crashes), > and no problem running windows xp. > > Could you help me to fix at least crashes of system ? > > System: > FreeBSD nuftop.zunet.ru 7.1-RELEASE FreeBSD 7.1-RELEASE #5: Thu Feb 26 > 02:06:03 MSK 2009 root@nuftop.zunet.ru:/usr/obj/usr/src/sys/NUF i386 > > Dmesg: > [nuf@nuftop /usr/home/nuf]$ dmesg | grep Intel | grep wpi > wpi0: mem 0xdf6ff000-0xdf6fffff irq 17 > at device 0.0 on pci3 > > Loaded modules: > [nuf@nuftop /usr/home/nuf]$ uname -a[nuf@nuftop /usr/home/nuf]$ kldstat > Id Refs Address Size Name > 1 25 0xc0400000 689f30 kernel > 2 1 0xc0a8a000 155e4 snd_hda.ko > 3 2 0xc0aa0000 4a64c sound.ko > 4 1 0xc0aeb000 55d0 acpi_video.ko > 5 3 0xc0af1000 6a2c4 acpi.ko > 6 1 0xc0b5c000 25f60 wpifw.ko > 7 1 0xc0b82000 de14 if_wpi.ko > 8 1 0xc0b90000 4f54 acpi_ibm.ko > 9 1 0xc435a000 22000 linux.ko > 10 1 0xc43da000 4000 logo_saver.ko > 11 1 0xc4436000 6000 i915.ko > 12 1 0xc4448000 f000 drm.ko > > Wlan kernel conf: > # Wireless NIC cards > device wlan # 802.11 support > device wlan_wep # 802.11 WEP support > device wlan_ccmp # 802.11 CCMP support > device wlan_tkip # 802.11 TKIP support > device wlan_amrr # AMRR transmit rate control algorithm > device wlan_scan_ap # 802.11 AP mode scanning > device wlan_scan_sta # 802.11 STA mode scanning > > Wpa_supplicant.conf: > [nuf@nuftop /usr/home/nuf]$ cat /etc/wpa_supplicant.conf > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > eapol_version=1 > fast_reauth=0 > network={ > ssid="TASHA" > scan_ssid=1 > proto=WPA2 > key_mgmt=WPA-PSK > pairwise=CCMP > group=CCMP > psk="nobodyknows" > } > > Stack trace form coredump after crash (dump itself is too big..): > (kgdb) bt > #0 doadump () at pcpu.h:196 > #1 0xc06394b7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 > #2 0xc0639789 in panic (fmt=Variable "fmt" is not available.) at > /usr/src/sys/kern/kern_shutdown.c:574 > #3 0xc089beac in trap_fatal (frame=0xe4059ba0, eva=65535) at > /usr/src/sys/i386/i386/trap.c:939 > #4 0xc089c130 in trap_pfault (frame=0xe4059ba0, usermode=0, eva=65535) > at /usr/src/sys/i386/i386/trap.c:852 > #5 0xc089caec in trap (frame=0xe4059ba0) at > /usr/src/sys/i386/i386/trap.c:530 > #6 0xc088295b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 > #7 0xc0b8bdfc in wpi_ops (arg0=0xc3c62000, pending=1) at > /usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:2411 > #8 0xc066c8c5 in taskqueue_run (queue=0xc3c1e900) at > /usr/src/sys/kern/subr_taskqueue.c:282 > #9 0xc066cacb in taskqueue_thread_loop (arg=0xc3c639b4) at > /usr/src/sys/kern/subr_taskqueue.c:401 > #10 0xc0615029 in fork_exit (callout=0xc066ca10 , > arg=0xc3c639b4, frame=0xe4059d38) at /usr/src/sys/kern/kern_fork.c:804 > #11 0xc08829d0 in fork_trampoline () at > /usr/src/sys/i386/i386/exception.s:264 > > > Typical ifconfig output when connection is up: > [nuf@nuftop /usr/home/nuf]$ ifconfig wpi0 > wpi0: flags=8843 metric 0 mtu 1500 > ether 00:1c:bf:85:cd:3a > inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 > media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) > status: associated > ssid TASHA channel 1 (2412 Mhz 11g) bssid 00:15:af:19:85:32 > authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit > AES-CCM 3:128-bit txpower 50 bmiss 7 scanvalid 60 protmode CTS > roaming MANUAL > > > Thanks! > > P.S. Sorry for my poor english =( > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > > After a few month of messing with 3945ABG (same and many more other problems) i threw it out and bought an atheros-based minipci wireless card. From sam at freebsd.org Sun Mar 29 11:14:07 2009 From: sam at freebsd.org (Sam Leffler) Date: Sun Mar 29 11:14:14 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <49CE5B95.1010502@freebsd.org> Message-ID: <49CFBA6D.9070208@freebsd.org> Daniel Eischen wrote: > On Sat, 28 Mar 2009, Daniel Eischen wrote: > >> No, there's no PR as far as I can tell. I'll try and set up a >> test system to duplicate it again, so I have proper information >> for a PR. >> >> I seem to recall that if wlanX is your primary/first lagg >> interface, then it uses the MAC address from the underlying >> interface as lagg's MAC address. In this case it works, >> but that's not the usual case 'cause you'd rather use a >> faster wired interface first if it exists. >> >> So this works: >> >> ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 >> >> but this doesn't: >> >> ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 >> >> In the latter case, lagg only works when bge0 is up. > > Also note that lagg(4) still references ath0 in its example instead > of wlan0. > > # ifconfig em0 up > # ifconfig ath0 nwid my_net up > # ifconfig lagg0 laggproto failover laggport em0 laggport ath0 \ > 192.168.1.1 netmask 255.255.255.0 > r190526 makes it possible to do the wired/wireless failover in HEAD. The only caveat is you must manually set the mac address of the wireless device to match the wired device because lagg's automatic setting of the wlanX ifnet doesn't propagate to the underlying device (the way if_setlladdr works makes it difficult). In the mean time you can do: ifconfig ath0 ether 00:11:22:33:44:55 where the mac address is whatever your wired nic's address is and then setup lagg0 using the wlan; e.g. ifconfig ath0 ether 00:11:22:33:44:55 ifconfig wlan create wlandev ath0 ssid my_net up ifconfig lagg create laggproto failover laggport em0 laggport wlan0 ... I also verified it works with WPA. In fact I tested this on a thinkpad in a docking station and it did the right thing just un-docking and re-docking. My only complaint is my ping running during all this lost one packet in the transition; not sure where. Sam From lists at braisel.com Sun Mar 29 23:51:12 2009 From: lists at braisel.com (=?iso-8859-1?Q?Andr=E9?= Braselmann) Date: Sun Mar 29 23:51:19 2009 Subject: 7.2 PreRelease & Novatel Merlin U740 Message-ID: <20090330065106.GB1169@trashbin.none.lan> Hi there, under 7.1-stable/amd64 my Merlin U740 HSDPA Modem was recognized correctly under /dev/cuaU0. After building the 7.2 Prerelease Kernel ist just ugen0. Were there any changes in the drivers/KLD's, which now should be loaded explicitly? Havn't found anything in UPDATING... TIA. K.Andr? Braselmann -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From volker at vwsoft.com Mon Mar 30 14:22:29 2009 From: volker at vwsoft.com (Volker) Date: Mon Mar 30 14:22:36 2009 Subject: 7.2 PreRelease & Novatel Merlin U740 In-Reply-To: <20090330065106.GB1169@trashbin.none.lan> References: <20090330065106.GB1169@trashbin.none.lan> Message-ID: <49D13337.7060808@vwsoft.com> On 12/23/-58 20:59, wrote: > Hi there, > > under 7.1-stable/amd64 my Merlin U740 HSDPA Modem was recognized > correctly under /dev/cuaU0. > > After building the 7.2 Prerelease Kernel ist just ugen0. > Were there any changes in the drivers/KLD's, which now should be loaded > explicitly? Havn't found anything in UPDATING... > > TIA. > > K.Andr? Braselmann > -- > O< ascii ribbon campaign - stop html mail - www.asciiribbon.org > Andre, the U740 is still supported by ubsa (just checked the sources). Can you please make sure, you've kldload'ed ubsa, at boot and usbdevs lists your device? You should find it there attached to ubsa. Volker From lists at braisel.com Mon Mar 30 22:34:30 2009 From: lists at braisel.com (=?iso-8859-1?Q?Andr=E9?= Braselmann) Date: Mon Mar 30 22:34:37 2009 Subject: 7.2 PreRelease & Novatel Merlin U740 In-Reply-To: <49D13337.7060808@vwsoft.com> References: <20090330065106.GB1169@trashbin.none.lan> <49D13337.7060808@vwsoft.com> Message-ID: <20090331053423.GB952@trashbin.none.lan> On Mon, Mar 30, 2009 at 11:01:43PM +0200, Volker wrote: > Andre, > > the U740 is still supported by ubsa (just checked the sources). Can you > please make sure, you've kldload'ed ubsa, at boot and usbdevs lists your > device? You should find it there attached to ubsa. > --- snip dmesg --- usb4: OHCI version 1.0 usb4: on ohci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered ugen0: on uhub3 --- snip --- kldload says: kldload: can't load ubsa: File exists usbdevs -s: addr 1: OHCI root hub, ATI uhub0 addr 1: OHCI root hub, ATI uhub1 addr 1: EHCI root hub, ATI uhub2 addr 1: OHCI root hub, NEC uhub3 addr 2: Novatel Wireless HSDPA Modem, Novatel Wireless ugen0 addr 1: OHCI root hub, NEC uhub4 So at stepping from 7.1 to 7.2-PR i didn't change any kernel options, except that for the ath0 driver. K.Andr? Braselmann -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From mel.flynn at mailing.thruhere.net Tue Mar 31 02:14:13 2009 From: mel.flynn at mailing.thruhere.net (Mel Flynn) Date: Tue Mar 31 02:14:26 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49CFBA6D.9070208@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <49CFBA6D.9070208@freebsd.org> Message-ID: <200903311054.35181.mel.flynn@mailing.thruhere.net> On Sunday 29 March 2009 20:14:05 Sam Leffler wrote: > Daniel Eischen wrote: > > On Sat, 28 Mar 2009, Daniel Eischen wrote: > >> No, there's no PR as far as I can tell. I'll try and set up a > >> test system to duplicate it again, so I have proper information > >> for a PR. > >> > >> I seem to recall that if wlanX is your primary/first lagg > >> interface, then it uses the MAC address from the underlying > >> interface as lagg's MAC address. In this case it works, > >> but that's not the usual case 'cause you'd rather use a > >> faster wired interface first if it exists. > >> > >> So this works: > >> > >> ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 > >> > >> but this doesn't: > >> > >> ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 > >> > >> In the latter case, lagg only works when bge0 is up. > > > > Also note that lagg(4) still references ath0 in its example instead > > of wlan0. > > > > # ifconfig em0 up > > # ifconfig ath0 nwid my_net up > > # ifconfig lagg0 laggproto failover laggport em0 laggport ath0 \ > > 192.168.1.1 netmask 255.255.255.0 > > r190526 makes it possible to do the wired/wireless failover in HEAD. > The only caveat is you must manually set the mac address of the wireless > device to match the wired device because lagg's automatic setting of the > wlanX ifnet doesn't propagate to the underlying device (the way > if_setlladdr works makes it difficult). In the mean time you can do: > > ifconfig ath0 ether 00:11:22:33:44:55 > > where the mac address is whatever your wired nic's address is and then > setup lagg0 using the wlan; e.g. > > ifconfig ath0 ether 00:11:22:33:44:55 > ifconfig wlan create wlandev ath0 ssid my_net up > ifconfig lagg create laggproto failover laggport em0 laggport wlan0 ... > > I also verified it works with WPA. In fact I tested this on a thinkpad > in a docking station and it did the right thing just un-docking and > re-docking. My only complaint is my ping running during all this lost > one packet in the transition; not sure where. Great! Does this also work for hostap mode now? I'd like to unify my internal network, currently using rum as hostap. If the answer is no, I pledge to file a PR. ;) From sam at freebsd.org Tue Mar 31 09:24:11 2009 From: sam at freebsd.org (Sam Leffler) Date: Tue Mar 31 09:24:17 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <200903311054.35181.mel.flynn@mailing.thruhere.net> References: <1238217783.00093348.1238205603@10.7.7.3> <49CFBA6D.9070208@freebsd.org> <200903311054.35181.mel.flynn@mailing.thruhere.net> Message-ID: <49D243A8.5050601@freebsd.org> Mel Flynn wrote: > On Sunday 29 March 2009 20:14:05 Sam Leffler wrote: >> Daniel Eischen wrote: >>> On Sat, 28 Mar 2009, Daniel Eischen wrote: >>>> No, there's no PR as far as I can tell. I'll try and set up a >>>> test system to duplicate it again, so I have proper information >>>> for a PR. >>>> >>>> I seem to recall that if wlanX is your primary/first lagg >>>> interface, then it uses the MAC address from the underlying >>>> interface as lagg's MAC address. In this case it works, >>>> but that's not the usual case 'cause you'd rather use a >>>> faster wired interface first if it exists. >>>> >>>> So this works: >>>> >>>> ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 >>>> >>>> but this doesn't: >>>> >>>> ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 >>>> >>>> In the latter case, lagg only works when bge0 is up. >>> Also note that lagg(4) still references ath0 in its example instead >>> of wlan0. >>> >>> # ifconfig em0 up >>> # ifconfig ath0 nwid my_net up >>> # ifconfig lagg0 laggproto failover laggport em0 laggport ath0 \ >>> 192.168.1.1 netmask 255.255.255.0 >> r190526 makes it possible to do the wired/wireless failover in HEAD. >> The only caveat is you must manually set the mac address of the wireless >> device to match the wired device because lagg's automatic setting of the >> wlanX ifnet doesn't propagate to the underlying device (the way >> if_setlladdr works makes it difficult). In the mean time you can do: >> >> ifconfig ath0 ether 00:11:22:33:44:55 >> >> where the mac address is whatever your wired nic's address is and then >> setup lagg0 using the wlan; e.g. >> >> ifconfig ath0 ether 00:11:22:33:44:55 >> ifconfig wlan create wlandev ath0 ssid my_net up >> ifconfig lagg create laggproto failover laggport em0 laggport wlan0 ... >> >> I also verified it works with WPA. In fact I tested this on a thinkpad >> in a docking station and it did the right thing just un-docking and >> re-docking. My only complaint is my ping running during all this lost >> one packet in the transition; not sure where. > > Great! Does this also work for hostap mode now? I'd like to unify my internal > network, currently using rum as hostap. > If the answer is no, I pledge to file a PR. ;) I don't understand what you're looking for but it's unlikely this will do what you want. lagg's failover protocol acts like a single-position switch funneling packets to one of several devices (all of which are assigned the same mac address). Sam From fbsd.mobile at rachie.is-a-geek.net Tue Mar 31 10:14:14 2009 From: fbsd.mobile at rachie.is-a-geek.net (Mel Flynn) Date: Tue Mar 31 10:14:21 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49D243A8.5050601@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <200903311054.35181.mel.flynn@mailing.thruhere.net> <49D243A8.5050601@freebsd.org> Message-ID: <200903311859.00642.fbsd.mobile@rachie.is-a-geek.net> On Tuesday 31 March 2009 18:24:08 Sam Leffler wrote: > Mel Flynn wrote: > > Great! Does this also work for hostap mode now? I'd like to unify my > > internal network, currently using rum as hostap. > > If the answer is no, I pledge to file a PR. ;) > > I don't understand what you're looking for but it's unlikely this will > do what you want. lagg's failover protocol acts like a single-position > switch funneling packets to one of several devices (all of which are > assigned the same mac address). What I'd like is my wireless and wired network to be on the same /24 and my hostap/gateway to nat between lagg0 and tun0. As you've now described lagg, this doesn't seem viable and I'll have to look for a different solution. The reason I want it, is that it greatly simplifies my rdr rules and I can seemlessly plug in/out my laptop without having to change default route or getting arp errors if I use lagg on it. Wireless routers (at least my retired Linksys) seem to be able to handle a unified wired/wireless network just fine, is there anything comparable in FreeBSD? -- Mel From sam at freebsd.org Tue Mar 31 12:44:22 2009 From: sam at freebsd.org (Sam Leffler) Date: Tue Mar 31 12:44:29 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <200903311859.00642.fbsd.mobile@rachie.is-a-geek.net> References: <1238217783.00093348.1238205603@10.7.7.3> <200903311054.35181.mel.flynn@mailing.thruhere.net> <49D243A8.5050601@freebsd.org> <200903311859.00642.fbsd.mobile@rachie.is-a-geek.net> Message-ID: <49D27294.9050706@freebsd.org> Mel Flynn wrote: > On Tuesday 31 March 2009 18:24:08 Sam Leffler wrote: >> Mel Flynn wrote: > >>> Great! Does this also work for hostap mode now? I'd like to unify my >>> internal network, currently using rum as hostap. >>> If the answer is no, I pledge to file a PR. ;) >> I don't understand what you're looking for but it's unlikely this will >> do what you want. lagg's failover protocol acts like a single-position >> switch funneling packets to one of several devices (all of which are >> assigned the same mac address). > > What I'd like is my wireless and wired network to be on the same /24 and my > hostap/gateway to nat between lagg0 and tun0. As you've now described lagg, > this doesn't seem viable and I'll have to look for a different solution. > > The reason I want it, is that it greatly simplifies my rdr rules and I can > seemlessly plug in/out my laptop without having to change default route or > getting arp errors if I use lagg on it. > > Wireless routers (at least my retired Linksys) seem to be able to handle a > unified wired/wireless network just fine, is there anything comparable in > FreeBSD? > It sounds like you just want wired+wireless bridged with single dhcp server. So long as your machines aren't simultaneously connected to both it should not be an issue. NAT is irrelevant unless you want to connect the outside world and want only 1 IP address to be exposed. Sam From volker at vwsoft.com Tue Mar 31 13:30:36 2009 From: volker at vwsoft.com (Volker) Date: Tue Mar 31 13:31:00 2009 Subject: 7.2 PreRelease & Novatel Merlin U740 In-Reply-To: <20090331053423.GB952@trashbin.none.lan> References: <20090330065106.GB1169@trashbin.none.lan> <49D13337.7060808@vwsoft.com> <20090331053423.GB952@trashbin.none.lan> Message-ID: <49D27D57.2060708@vwsoft.com> On 03/31/09 07:34, Andr? Braselmann wrote: > On Mon, Mar 30, 2009 at 11:01:43PM +0200, Volker wrote: > >> Andre, >> >> the U740 is still supported by ubsa (just checked the sources). Can you >> please make sure, you've kldload'ed ubsa, at boot and usbdevs lists your >> device? You should find it there attached to ubsa. >> > --- snip dmesg --- > usb4: OHCI version 1.0 > usb4: on ohci3 > usb4: USB revision 1.0 > uhub4: on usb4 > uhub4: 2 ports with 2 removable, self powered > ugen0: 1.10/0.00, addr 2> on uhub3 > --- snip --- > > kldload says: kldload: can't load ubsa: File exists > > usbdevs -s: > addr 1: OHCI root hub, ATI > uhub0 > addr 1: OHCI root hub, ATI > uhub1 > addr 1: EHCI root hub, ATI > uhub2 > addr 1: OHCI root hub, NEC > uhub3 > addr 2: Novatel Wireless HSDPA Modem, Novatel Wireless > ugen0 > addr 1: OHCI root hub, NEC > uhub4 > > > > So at stepping from 7.1 to 7.2-PR i didn't change any kernel options, > except that for the ath0 driver. Andre, by any chance, are you using a U740 with product ID 0x1410? I've found a bug in the driver for this device. Please try the attached patch. Volker -------------- next part -------------- --- sys/dev/usb/ubsa.c.orig 2009-03-31 22:26:22.000000000 +0200 +++ sys/dev/usb/ubsa.c 2009-03-31 22:27:41.000000000 +0200 @@ -224,6 +224,7 @@ { USB_VENDOR_PERACOM, USB_PRODUCT_PERACOM_SERIAL1 }, /* Novatel Wireless Merlin cards */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740 }, + { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U740_2 }, /* Novatel Wireless Merlin v740 */ { USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_V740 }, /* Option Vodafone MC3G */ From Lakhinder at SikhCommunityCenter.org Tue Mar 31 18:07:06 2009 From: Lakhinder at SikhCommunityCenter.org (SikhCommunityCenter.org) Date: Tue Mar 31 18:07:13 2009 Subject: Passing of Dr Surjit Kaur, JBS Bakshi; New Gurudwara Opens Message-ID: PartyDigest.com | 4705 Grand Masters Way | Prince William | VA | 22192 | US This email was sent to mobile@freebsd.org, by Lakhinder@SikhCommunityCenter.org. To unsubscribe from this list - please use this link: http://app.simplycast.com/unsubscribe.asp?outgoing_idno=5441998&e=3089792&gId=5248373. If this message was received in error, please report it to: mailto:reportit@scsend.com?subject=5248373z3089792z5441998 This email was powered by http://www.simplycast.com From fbsd.mobile at rachie.is-a-geek.net Tue Mar 31 23:39:33 2009 From: fbsd.mobile at rachie.is-a-geek.net (Mel Flynn) Date: Tue Mar 31 23:39:40 2009 Subject: Switching from wired to wireless getting "network down" In-Reply-To: <49D27294.9050706@freebsd.org> References: <1238217783.00093348.1238205603@10.7.7.3> <200903311859.00642.fbsd.mobile@rachie.is-a-geek.net> <49D27294.9050706@freebsd.org> Message-ID: <200904010839.30641.fbsd.mobile@rachie.is-a-geek.net> On Tuesday 31 March 2009 21:44:20 Sam Leffler wrote: > Mel Flynn wrote: > > On Tuesday 31 March 2009 18:24:08 Sam Leffler wrote: > >> Mel Flynn wrote: > >>> Great! Does this also work for hostap mode now? I'd like to unify my > >>> internal network, currently using rum as hostap. > >>> If the answer is no, I pledge to file a PR. ;) > >> > >> I don't understand what you're looking for but it's unlikely this will > >> do what you want. lagg's failover protocol acts like a single-position > >> switch funneling packets to one of several devices (all of which are > >> assigned the same mac address). > > > > What I'd like is my wireless and wired network to be on the same /24 and > > my hostap/gateway to nat between lagg0 and tun0. As you've now described > > lagg, this doesn't seem viable and I'll have to look for a different > > solution. > > > > The reason I want it, is that it greatly simplifies my rdr rules and I > > can seemlessly plug in/out my laptop without having to change default > > route or getting arp errors if I use lagg on it. > > > > Wireless routers (at least my retired Linksys) seem to be able to handle > > a unified wired/wireless network just fine, is there anything comparable > > in FreeBSD? > > It sounds like you just want wired+wireless bridged with single dhcp > server. So long as your machines aren't simultaneously connected to > both it should not be an issue. NAT is irrelevant unless you want to > connect the outside world and want only 1 IP address to be exposed. So I can't have this: lagg0 via wpi <-> lagg0 via rum-hostap / \ +-----------+ +--------------+ + laptop + 192.168.1.0/24 + gateway +-- tun0-inet +-----------+ +--------------+ 192.168.1.2 \ / 192.168.1.1 lagg0 via em0 <-> lagg0 via fxp0 And have both connected/disconnected at will. -- Mel