From anton at nikiforov.ru Mon Jun 2 06:04:59 2008 From: anton at nikiforov.ru (Anton Nikiforov) Date: Mon Jun 2 06:05:03 2008 Subject: Toshiba Satelite U305 WiFi/net/acpi problem Message-ID: <48438A25.4010103@nikiforov.ru> Dear All, I have toshiba notebook (U305-S5107) with I4965AGN Wifi and RTL8139 network adapters. When i boot my notebook with ACPI enabled - i have no network support, none of controllers appears in ifconfig output, but when i'm booting with ACPI disabled - i can use re0 (with some strange looses in RX traffic, but it is another story) but completley have no chance to use my WiFi. Maybe it is more ACPI problem, but first i do need to get adapter working and then i'll try to find out whats wrong with ACPI. The kernel is compiled with all available drivers and /boot/loader.conf contains (i tried with one driver, with the other and all combinations): u300# more /boot/loader.conf wpifw_load="YES" legal.intel_wpi.license_ack=1 legal.intel_ipw.license_ack=1 legal.intel_iwi.license_ack=1 acpi_toshiba_load="YES" loader_logo="beastiebw" ipw_load="YES" ipw_bss_load="YES" ipw_ibss_load="YES" ipw_monitor_load="YES" iwi_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" u300# pciconf -lv re0@pci0:4:0:0: class=0x020000 card=0xff501179 chip=0x813610ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8139/810x Family Fast Ethernet NIC' class = network subclass = ethernet none1@pci0:6:0:0: class=0x028000 card=0x11008086 chip=0x42298086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 4965AGN Intel? Wireless WiFi Link 4965AGN(supporting 802.11a/b/g/Draft-N)' class = network u300# uname -a FreeBSD u300.newlines.ru 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #17: Wed May 21 19:26:54 MSD 2008 nanthony@u300.newlines.ru:/data/obj/data/src/sys/U300 i386 Best regards, Anton Nikiforov From tobez at tobez.org Mon Jun 2 07:27:07 2008 From: tobez at tobez.org (Anton Berezin) Date: Mon Jun 2 07:27:10 2008 Subject: Toshiba Satelite U305 WiFi/net/acpi problem In-Reply-To: <48438A25.4010103@nikiforov.ru> References: <48438A25.4010103@nikiforov.ru> Message-ID: <20080602071650.GA37678@heechee.tobez.org> On Mon, Jun 02, 2008 at 09:50:29AM +0400, Anton Nikiforov wrote: > I have toshiba notebook (U305-S5107) with I4965AGN Wifi and RTL8139 network > adapters. I4965AGN is handled by iwn(4), not by ipw(4) nor by iwi(4). The iwn driver is currently only available in FreeBSD CURRENT ("8.0") branch. Cheers, \Anton. -- We're going for 'working' here. 'clean' is for people with skills... -- Flemming Jacobsen From zkolic at sbb.co.yu Mon Jun 2 14:00:54 2008 From: zkolic at sbb.co.yu (Zoran Kolic) Date: Mon Jun 2 14:00:57 2008 Subject: Toshiba Satelite U305 WiFi/net/acpi problem In-Reply-To: <20080602120017.10D3810656FD@hub.freebsd.org> References: <20080602120017.10D3810656FD@hub.freebsd.org> Message-ID: <20080602140109.GA907@faust.net> > I have toshiba notebook (U305-S5107) with I4965AGN Wifi and RTL8139 > network adapters. > When i boot my notebook with ACPI enabled - i have no network support, > none of controllers appears in ifconfig output, but when i'm booting > with ACPI disabled - i can use re0 (with some strange looses in RX > traffic, but it is another story) but completley have no chance to use > my WiFi. This ethernet device should be handled by rl. Not a good adapter, but you have no choice now. > I4965AGN is handled by iwn(4), not by ipw(4) nor by iwi(4). The iwn driver > is currently only available in FreeBSD CURRENT ("8.0") branch. Or you could pick some pcmcia card for the start. Latter, the intel adapter would come to os version you use. Zoran From torfinn.ingolfsen at broadpark.no Mon Jun 2 15:16:51 2008 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Mon Jun 2 15:16:58 2008 Subject: Toshiba Satelite U305 WiFi/net/acpi problem In-Reply-To: <20080602071650.GA37678@heechee.tobez.org> References: <48438A25.4010103@nikiforov.ru> <20080602071650.GA37678@heechee.tobez.org> Message-ID: <20080602171641.f710cfe7.torfinn.ingolfsen@broadpark.no> On Mon, 02 Jun 2008 09:16:50 +0200 Anton Berezin wrote: > On Mon, Jun 02, 2008 at 09:50:29AM +0400, Anton Nikiforov wrote: > > > I have toshiba notebook (U305-S5107) with I4965AGN Wifi and RTL8139 > > network adapters. > > I4965AGN is handled by iwn(4), not by ipw(4) nor by iwi(4). The iwn > driver is currently only available in FreeBSD CURRENT ("8.0") branch. FWIW, I downloaded the Perforce version of the iwn driver with the script from the iwn[1] page, and it compiled and works for me on 7.0-stable Refernces: 1) http://www.clearchain.com/wiki/Iwn -- REgards, Torfinn Ingolfsen From vova at fbsd.ru Mon Jun 2 16:52:11 2008 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Mon Jun 2 16:52:22 2008 Subject: Suspend/resume on T60 - anyone succeeded ? Message-ID: <1212423545.1633.150.camel@localhost> Hi Is there anybody who managed make T60 suspend/resume with either UP or SMP kernel ? If yes, please share your configuration/hints. In my case it does not awakes (tries, but fails). -- Vladimir B. Grebenschikov vova@fbsd.ru From olivier at aixmarseille.com Tue Jun 3 09:33:47 2008 From: olivier at aixmarseille.com (Olivier Fauchon) Date: Tue Jun 3 09:33:52 2008 Subject: Suspend/resume on T60 - anyone succeeded ? In-Reply-To: <1212423545.1633.150.camel@localhost> References: <1212423545.1633.150.camel@localhost> Message-ID: <484508DB.70804@aixmarseille.com> Vladimir Grebenschikov wrote: > Hi > > Is there anybody who managed make T60 suspend/resume with either UP or > SMP kernel ? > > If yes, please share your configuration/hints. > > In my case it does not awakes (tries, but fails). > > Same for Dell D430... (core2duo) Suspend works, but resume make laptop reboot... at least with FreeBSD7 (UP & SMP).... Any info welcome... From jcasquero at gmail.com Mon Jun 9 10:01:58 2008 From: jcasquero at gmail.com (=?ISO-8859-1?Q?Jes=FAs_Casquero?=) Date: Mon Jun 9 10:02:02 2008 Subject: FreeBSD 7: i386 or AMD64 install ?? Message-ID: Hello everybody, I have a question about FreeBSD 7. I have a new laptop (HP Pavillion 6600 series) whose principal function will be programming (Ruby on rails) and a little multimedia and CD,DVD toasting stuff. I have seen there is a FreeBSD/amd64 Project which covers the FreeBSD port to AMD's AMD64 and Intel 64 architecture [1]. The laptop has an Intel Core Duo T8100, 64 bits, processor and 3 GB of memory. Should I install this version or should I switch to the 386 version ? I am looking for good stability compiling with Ruby and enough support of the main devices: Intel Pro 3945 wireless card (through wpi I have read), nvidia driver, etc. These last tips are done with basic funcionality. Is there something that it I have to bear in mind? I have searched the list before posting but I have not found anything definitive Thanks very much in advance. Regards Jesus. [1] http://www.freebsd.org/platforms/amd64.html From jcasquero at gmail.com Mon Jun 9 10:26:47 2008 From: jcasquero at gmail.com (=?ISO-8859-1?Q?Jes=FAs_Casquero?=) Date: Mon Jun 9 10:26:50 2008 Subject: FreeBSD 7: i386 or AMD64 install ?? In-Reply-To: <484D036E.9050005@otenet.gr> References: <484D036E.9050005@otenet.gr> Message-ID: Thanks very much!. I will install the 32bit version. 2008/6/9 Manolis Kiagias : > > > Jes?s Casquero wrote: >> >> Hello everybody, >> >> I have a question about FreeBSD 7. I have a new laptop (HP Pavillion >> 6600 series) whose principal function will be programming (Ruby on >> rails) and a little multimedia and CD,DVD toasting stuff. >> >> I have seen there is a FreeBSD/amd64 Project which covers the >> FreeBSD port to AMD's AMD64 and Intel 64 architecture [1]. The laptop >> has an Intel Core Duo T8100, 64 bits, processor and 3 GB of memory. >> >> Should I install this version or should I switch to the 386 version >> ? I am looking for good stability compiling with Ruby and enough >> support of the main devices: Intel Pro 3945 wireless card (through wpi >> I have read), nvidia driver, etc. These last tips are done with basic >> funcionality. >> >> Is there something that it I have to bear in mind? I have searched >> the list before posting but I have not found anything definitive >> >> Thanks very much in advance. >> Regards >> Jesus. >> >> [1] http://www.freebsd.org/platforms/amd64.html >> >> > > I have a more or less similar laptop. > Notice you will get stuck with the open source "nv" driver. There is no > proprietary nvidia driver for amd64. This will definitely slow down your X > experience. > The 3945 wireless works, although it does have some random problems > (disconnects, error messages etc.). I suggest you do a test install and see > how it goes. You may have other problems (e.g. ACPI related). CD/DVD burning > should be no problem, and mplayer will probably cover your multimedia needs. > But better test and see. > You could also definitely install the 32bit version which will give you best > X performance. > From sonicy at otenet.gr Mon Jun 9 11:38:37 2008 From: sonicy at otenet.gr (Manolis Kiagias) Date: Mon Jun 9 11:38:47 2008 Subject: FreeBSD 7: i386 or AMD64 install ?? In-Reply-To: References: Message-ID: <484D036E.9050005@otenet.gr> Jes?s Casquero wrote: > Hello everybody, > > I have a question about FreeBSD 7. I have a new laptop (HP Pavillion > 6600 series) whose principal function will be programming (Ruby on > rails) and a little multimedia and CD,DVD toasting stuff. > > I have seen there is a FreeBSD/amd64 Project which covers the > FreeBSD port to AMD's AMD64 and Intel 64 architecture [1]. The laptop > has an Intel Core Duo T8100, 64 bits, processor and 3 GB of memory. > > Should I install this version or should I switch to the 386 version > ? I am looking for good stability compiling with Ruby and enough > support of the main devices: Intel Pro 3945 wireless card (through wpi > I have read), nvidia driver, etc. These last tips are done with basic > funcionality. > > Is there something that it I have to bear in mind? I have searched > the list before posting but I have not found anything definitive > > Thanks very much in advance. > Regards > Jesus. > > [1] http://www.freebsd.org/platforms/amd64.html > > I have a more or less similar laptop. Notice you will get stuck with the open source "nv" driver. There is no proprietary nvidia driver for amd64. This will definitely slow down your X experience. The 3945 wireless works, although it does have some random problems (disconnects, error messages etc.). I suggest you do a test install and see how it goes. You may have other problems (e.g. ACPI related). CD/DVD burning should be no problem, and mplayer will probably cover your multimedia needs. But better test and see. You could also definitely install the 32bit version which will give you best X performance. From torfinn.ingolfsen at broadpark.no Mon Jun 9 17:50:33 2008 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Mon Jun 9 17:50:40 2008 Subject: FreeBSD 7: i386 or AMD64 install ?? In-Reply-To: References: Message-ID: <20080609195030.dd00894e.torfinn.ingolfsen@broadpark.no> On Mon, 09 Jun 2008 11:36:08 +0200 Jes?s Casquero wrote: > I have seen there is a FreeBSD/amd64 Project which covers the > FreeBSD port to AMD's AMD64 and Intel 64 architecture [1]. The laptop > has an Intel Core Duo T8100, 64 bits, processor and 3 GB of memory. > > Should I install this version or should I switch to the 386 version > ? I am looking for good stability compiling with Ruby and enough General reccommendation: if your hard drive is large enough, split it in two and install i386 on one partition and amd64 on the other partition. Then you dual-boot and find ut which version suits your best. -- Regards, Torfinn Ingolfsen From jcasquero at gmail.com Tue Jun 10 07:27:31 2008 From: jcasquero at gmail.com (=?ISO-8859-1?Q?Jes=FAs_Casquero?=) Date: Tue Jun 10 07:27:35 2008 Subject: FreeBSD 7: i386 or AMD64 install ?? In-Reply-To: <200806091502.42813.asstec@matik.com.br> References: <200806091502.42813.asstec@matik.com.br> Message-ID: Thanks very much ! :) 2008/6/9 AT Matik : > On Monday 09 June 2008 06:36:08 you wrote: >> Hello everybody, >> >> I have a question about FreeBSD 7. I have a new laptop (HP Pavillion >> 6600 series) whose principal function will be programming (Ruby on >> rails) and a little multimedia and CD,DVD toasting stuff. >> >> I have seen there is a FreeBSD/amd64 Project which covers the >> FreeBSD port to AMD's AMD64 and Intel 64 architecture [1]. The laptop >> has an Intel Core Duo T8100, 64 bits, processor and 3 GB of memory. >> >> Should I install this version or should I switch to the 386 version >> ? I am looking for good stability compiling with Ruby and enough >> support of the main devices: Intel Pro 3945 wireless card (through wpi >> I have read), nvidia driver, etc. These last tips are done with basic >> funcionality. >> >> Is there something that it I have to bear in mind? I have searched >> the list before posting but I have not found anything definitive >> > > Hi J > you should use i386 because for laptop/desktop use amd64 is not good > specially in your case the nv video drievr is shit and hangs the machien trice > a day and the other point, most java applets are bad, faulty or do not work > (Online banking) and thinks like flash and so also not ... so do not wast > your time :) > > Jo?o > > > > -- > > Atenciosamente > > Infomatik Internet Technology > > -- > > Atenciosamente, J.M. > Respons?vel Plant?o Site Support Matik > Infomatik Internet Technology > (18)3551.8155 (18)8112.7007 > http://info.matik.com.br > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. > Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br > From stephen at math.missouri.edu Mon Jun 16 23:00:52 2008 From: stephen at math.missouri.edu (Stephen Montgomery-Smith) Date: Mon Jun 16 23:00:55 2008 Subject: ALPS glidepoint tapping under gnome Message-ID: <4856EC61.3010008@math.missouri.edu> I have a ALPS glidepoint mouse. I dislike that tapping the mouse produces a mouse click. I had the hardest time getting tapping->mouse click to stop working under Gnome. After much experimentation I discovered a solution: Start moused with the additional flag "-m 11=4". I suspect that the number 11 isn't particularly significant, but I think it has to be a fairly large number. I hope this helps other people as well. Stephen From eculp at cloudmaster.info Thu Jun 19 11:26:37 2008 From: eculp at cloudmaster.info (eculp@cloudmaster.info) Date: Thu Jun 19 11:26:41 2008 Subject: Ath0 802.11 comes up with Sam's patch but shows no carrier and I can't make it connect. Message-ID: <20080619061612.39782fyb1v5rcnb4@intranet.cloudmaster.info> On amd64 current I have installed the patch from Sam, http://people.freebsd.org/~sam/ath_hal-20080528.tgz, that seems to fix the hal problem but it still doesn't have carrier and a scan only gets "ifconfig: unable to get scan results" I've even checked the handbook and it says basically what I've done. Any suggestions would be appreciated. More information: # ifconfig ath0 ath0: flags=8843 metric 0 mtu 2290 ether 00:1d:d9:27:5c:e5 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier # uname -a FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #124: Tue Jun 17 18:14:14 CDT 2008 root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO amd64 dmesg ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) ath0: mem 0xf2200000-0xf220ffff irq 19 at device 0.0 on pci5 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: mac 14.2 phy 7.0 radio 10.2 rc.conf if_ath_load="yes" ifconfig_ath0="DHCP" Kernel config in /usr/src/sys/amd64/conf/ENCONTACTO device ath device ath_hal device ath_rate_sample device wlan device wlan_wep device wlan_ccmp device wlan_tkip I don't have anything in the loader.conf. I can't help be feel that I'm missing something here. Thanks for any suggestions, ed From onemda at gmail.com Thu Jun 19 13:31:09 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Jun 19 13:31:13 2008 Subject: Ath0 802.11 comes up with Sam's patch but shows no carrier and I can't make it connect. In-Reply-To: <20080619061612.39782fyb1v5rcnb4@intranet.cloudmaster.info> References: <20080619061612.39782fyb1v5rcnb4@intranet.cloudmaster.info> Message-ID: <3a142e750806190631u4d7e9d6ajd5b85f0a97cbb1d1@mail.gmail.com> Because it looks like you are using CURRENT, first you need to create wlanX interface: ifconfig wlan create wlandev ath0 Read man page of ath (if you did installed new world) and/or entry in /usr/src/UPDATING dated 20080420. On 6/19/08, eculp@cloudmaster.info wrote: > > On amd64 current I have installed the patch from Sam, > http://people.freebsd.org/~sam/ath_hal-20080528.tgz, that seems to fix > the hal problem but it still doesn't have carrier and a scan only gets > "ifconfig: unable to get scan results" > > I've even checked the handbook and it says basically what I've done. > Any suggestions would be appreciated. > > More information: > > # ifconfig ath0 > ath0: flags=8843 metric 0 mtu 2290 > ether 00:1d:d9:27:5c:e5 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > > # uname -a > FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #124: Tue Jun > 17 18:14:14 CDT 2008 > root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO amd64 > > dmesg > > ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, > RF2413, RF5413, RF2133, RF2425, RF2417) > > ath0: mem 0xf2200000-0xf220ffff irq 19 at device > 0.0 on pci5 > ath0: [ITHREAD] > ath0: WARNING: using obsoleted if_watchdog interface > ath0: mac 14.2 phy 7.0 radio 10.2 > > rc.conf > if_ath_load="yes" > ifconfig_ath0="DHCP" > > Kernel config in /usr/src/sys/amd64/conf/ENCONTACTO > device ath > device ath_hal > device ath_rate_sample > device wlan > device wlan_wep > device wlan_ccmp > device wlan_tkip > > I don't have anything in the loader.conf. > > I can't help be feel that I'm missing something here. Thanks for any > suggestions, > > ed > _______________________________________________ > 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 eculp at cloudmaster.info Thu Jun 19 23:25:37 2008 From: eculp at cloudmaster.info (Edwin L. Culp) Date: Thu Jun 19 23:25:41 2008 Subject: Ath0 802.11 comes up with Sam's patch but shows no carrier and I can't make it connect. In-Reply-To: <3a142e750806190631u4d7e9d6ajd5b85f0a97cbb1d1@mail.gmail.com> References: <20080619061612.39782fyb1v5rcnb4@intranet.cloudmaster.info> <3a142e750806190631u4d7e9d6ajd5b85f0a97cbb1d1@mail.gmail.com> Message-ID: <20080619182520.736036jkb7736k8w@intranet.cloudmaster.info> Quoting "Paul B. Mahol" : > Because it looks like you are using CURRENT, first you need to create > wlanX interface: > > ifconfig wlan create wlandev ath0 > > Read man page of ath (if you did installed new world) and/or entry in > /usr/src/UPDATING dated 20080420. Sorry I missed that Paul. Thanks for calling it to my attention. I have tried to follow the instructions in the ath and wlan manual pages and the UPDATING file but my end result hasn't changed - "no carrier". I'm sure that I am still missing something else. My rc.conf has changed from: >> if_ath_load="yes" >> ifconfig_ath0="DHCP" to # ath new config wlans_ath0=wlan0 ifconfig_wlan0="WPA DHCP" The only reference to ath0 being in the wlans_ath0 line. The related parts of my verbose dmesg are: ath_rate: version 1.2 wlan: <802.11 Link Layer> ath0: mem 0xf2200000-0xf220ffff irq 19 at device 0.0 on pci5 ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf2200000 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 64 ath0: [MPSAFE] ath0: [ITHREAD] ath0: hal channel 2412/a0 -> 1 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2412/c0 -> 1 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2417/a0 -> 2 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2417/c0 -> 2 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2422/a0 -> 3 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2422/c0 -> 3 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2427/a0 -> 4 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2427/c0 -> 4 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2432/a0 -> 5 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2432/c0 -> 5 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2437/a0 -> 6 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2437/c0 -> 6 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2442/a0 -> 7 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2442/c0 -> 7 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2447/a0 -> 8 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2447/c0 -> 8 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2452/a0 -> 9 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2452/c0 -> 9 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2457/a0 -> 10 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2457/c0 -> 10 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2462/a0 -> 11 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2462/c0 -> 11 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2467/a0 -> 12 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2467/c0 -> 12 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2472/a0 -> 13 maxpow 32 minpow 0 maxreg 20 ath0: hal channel 2472/c0 -> 13 maxpow 32 minpow 0 maxreg 20 ath0: WARNING: using obsoleted if_watchdog interface ath0: bpf attached ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: mac 14.2 phy 7.0 radio 10.2 ath0: Use hw queue 1 for WME_AC_BE traffic ath0: Use hw queue 0 for WME_AC_BK traffic ath0: Use hw queue 2 for WME_AC_VI traffic ath0: Use hw queue 3 for WME_AC_VO traffic ath0: Use hw queue 8 for CAB traffic ath0: Use hw queue 9 for beacons wlan0: bpf attached wlan0: Ethernet address: 00:1d:d9:27:5c:e5 wlan0: bpf attached Which in my ignorance seem fine. My ifconfig is now: ath0: flags=8802 metric 0 mtu 2290 ether 00:1d:d9:27:5c:e5 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier wlan0: flags=8802 metric 0 mtu 1500 ether 00:1d:d9:27:5c:e5 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 Mhz 11b) regdomain 101 indoor ecm authmode OPEN privacy OFF txpower 16 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 wme burst bintval 0 Both have "no carrier" and neither will do scan ifconfig wlan0 scan seems to be ignored and # ifconfig ath0 scan ifconfig: unable to get results I have been looking for more examples of how to get it up and have tried assigning a AP and ip and it accepts them but still no carrier and no communication. I'm going to erase the previous report because this has changed completely to save space. Thanks to anyone who can give me a bit more guidence. Maybe my rc.conf is missing something or scan no longer works or . . . . ed From thompsa at FreeBSD.org Fri Jun 20 00:11:14 2008 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Fri Jun 20 00:11:19 2008 Subject: Ath0 802.11 comes up with Sam's patch but shows no carrier and I can't make it connect. In-Reply-To: <20080619182520.736036jkb7736k8w@intranet.cloudmaster.info> References: <20080619061612.39782fyb1v5rcnb4@intranet.cloudmaster.info> <3a142e750806190631u4d7e9d6ajd5b85f0a97cbb1d1@mail.gmail.com> <20080619182520.736036jkb7736k8w@intranet.cloudmaster.info> Message-ID: <20080619234045.GC76058@citylink.fud.org.nz> On Thu, Jun 19, 2008 at 06:25:20PM -0500, Edwin L. Culp wrote: > Quoting "Paul B. Mahol" : > >> Because it looks like you are using CURRENT, first you need to create >> wlanX interface: >> >> ifconfig wlan create wlandev ath0 >> >> Read man page of ath (if you did installed new world) and/or entry in >> /usr/src/UPDATING dated 20080420. > > Sorry I missed that Paul. Thanks for calling it to my attention. > > I have tried to follow the instructions in the ath and wlan manual pages > and the UPDATING file but my end result hasn't changed - "no carrier". I'm > sure that I am still missing something else. > > My rc.conf has changed from: >>> if_ath_load="yes" >>> ifconfig_ath0="DHCP" > to > # ath new config > wlans_ath0=wlan0 > ifconfig_wlan0="WPA DHCP" > > My ifconfig is now: > > ath0: flags=8802 metric 0 mtu 2290 > ether 00:1d:d9:27:5c:e5 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > > wlan0: flags=8802 metric 0 mtu 1500 ^^^^^ For some reason your interface is not UP. The dhcp client should do this so make sure its being launched. > ether 00:1d:d9:27:5c:e5 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 Mhz 11b) > regdomain 101 indoor ecm authmode OPEN privacy OFF txpower 16 bmiss 7 > scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 > roam:rate 1 wme burst bintval 0 > > Both have "no carrier" and neither will do scan From eculp at cloudmaster.info Fri Jun 20 09:42:00 2008 From: eculp at cloudmaster.info (Edwin L. Culp) Date: Fri Jun 20 09:42:05 2008 Subject: Ath0 802.11 comes up with Sam's patch but shows no carrier and I can't make it connect. In-Reply-To: <20080619234045.GC76058@citylink.fud.org.nz> References: <20080619061612.39782fyb1v5rcnb4@intranet.cloudmaster.info> <3a142e750806190631u4d7e9d6ajd5b85f0a97cbb1d1@mail.gmail.com> <20080619182520.736036jkb7736k8w@intranet.cloudmaster.info> <20080619234045.GC76058@citylink.fud.org.nz> Message-ID: <20080620044143.88074a97adz57s6c@intranet.cloudmaster.info> Quoting Andrew Thompson : > On Thu, Jun 19, 2008 at 06:25:20PM -0500, Edwin L. Culp wrote: >> Quoting "Paul B. Mahol" : >> >>> Because it looks like you are using CURRENT, first you need to create >>> wlanX interface: >>> >>> ifconfig wlan create wlandev ath0 >>> >>> Read man page of ath (if you did installed new world) and/or entry in >>> /usr/src/UPDATING dated 20080420. >> >> Sorry I missed that Paul. Thanks for calling it to my attention. >> >> I have tried to follow the instructions in the ath and wlan manual pages >> and the UPDATING file but my end result hasn't changed - "no carrier". I'm >> sure that I am still missing something else. >> >> My rc.conf has changed from: >>>> if_ath_load="yes" >>>> ifconfig_ath0="DHCP" >> to >> # ath new config >> wlans_ath0=wlan0 >> ifconfig_wlan0="WPA DHCP" >> >> My ifconfig is now: >> >> ath0: flags=8802 metric 0 mtu 2290 >> ether 00:1d:d9:27:5c:e5 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> >> wlan0: flags=8802 metric 0 mtu 1500 > ^^^^^ > > For some reason your interface is not UP. The dhcp client should do this > so make sure its being launched. Thanks, Andrew. I haven't used wireless on freebsd since 802.11b on maybe 4.? before hostap, etc. etc. I need to get this running to relearn about wifi under freebsd. Unfortunately, I bought a laptop with an unsupported ath card but now that Sam's latest patch brings it and with the help from folks on the list I'm getting closer. You are right, Andrew, dhclient wasn't running so first I tried: # ifconfig wlan0 up ath0 then associated: ath0: flags=8843 metric 0 mtu 2290 ether 00:1d:d9:27:5c:e5 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 pflog0: flags=0<> metric 0 mtu 33160 wlan0: flags=8843 metric 0 mtu 1500 ether 00:1d:d9:27:5c:e5 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 4 (2427 Mhz 11g) regdomain 101 indoor ecm authmode OPEN privacy OFF txpower 16 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst bintval 0 but still no carrier on wlan0 :( so I tried # dhclient wlan0 wlan0: no link .............. giving up Trying # ifconfig wlan0 scan never finishes at least for the 10 minutes that I have left it. Just in case anyone wonders, I have an AP about 3 feet from where I'm working and an iPhone that finds about a 1/2 dozen on accessable AP's so it souldn't be a signal problem although all are using wep for auth. Anyone else have a suggestion? Thanks, ed > >> ether 00:1d:d9:27:5c:e5 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> ssid "" channel 1 (2412 Mhz 11b) >> regdomain 101 indoor ecm authmode OPEN privacy OFF txpower 16 bmiss 7 >> scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 >> roam:rate 1 wme burst bintval 0 >> >> Both have "no carrier" and neither will do scan > _______________________________________________ > 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 eculp at cloudmaster.info Fri Jun 20 13:20:31 2008 From: eculp at cloudmaster.info (Edwin L. Culp) Date: Fri Jun 20 13:20:36 2008 Subject: Ath0 802.11 comes up with Sam's patch but shows no carrier and I can't make it connect. In-Reply-To: <485B7DD6.4000603@byterider.net> References: <20080619061612.39782fyb1v5rcnb4@intranet.cloudmaster.info> <20080619234045.GC76058@citylink.fud.org.nz> <3a142e750806190631u4d7e9d6ajd5b85f0a97cbb1d1@mail.gmail.com> <20080619182520.736036jkb7736k8w@intranet.cloudmaster.info> <20080620044143. <485B7DD6.4000603@byterider.net> Message-ID: <20080620082013.33071pu8p4g77usk@intranet.cloudmaster.info> To close the thread: The ath0: mem 0xf2200000-0xf220ffff irq 19 at device 0.0 on pci5 is WORKING and I'm using it to send this message. I still have a lot of polishing to do at boot time and I may have some conflicts with the nfe network card or having dhclient called for both from rc.conf. For now I will do it manually on boot. The credit goes to: Sam for his patch http://people.freebsd.org/~sam/ath_hal-20080528.tgz Sylwester for giving me another approach. Andrew for reminding me that dhclient wasn't bringing the interface up. Paul for the rtfm, etc. actually the read the NEW ath wlan manuals and UPDATING, that really got me started. Now I have to find how to make the connection far easier than manual and rc.conf and the different authentication. I guess now I would like a nice little window that shows the scan and lets me add the password in X rather than using ifconfig Thanks again, ed Quoting Sylwester : > Edwin L. Culp wrote: >> Quoting Andrew Thompson : >> >>> On Thu, Jun 19, 2008 at 06:25:20PM -0500, Edwin L. Culp wrote: >>>> Quoting "Paul B. Mahol" : >>>> >>>>> Because it looks like you are using CURRENT, first you need to create >>>>> wlanX interface: >>>>> >>>>> ifconfig wlan create wlandev ath0 >>>>> >>>>> Read man page of ath (if you did installed new world) and/or entry in >>>>> /usr/src/UPDATING dated 20080420. >>>> >>>> Sorry I missed that Paul. Thanks for calling it to my attention. >>>> >>>> I have tried to follow the instructions in the ath and wlan manual pages >>>> and the UPDATING file but my end result hasn't changed - "no >>>> carrier". I'm >>>> sure that I am still missing something else. >>>> >>>> My rc.conf has changed from: >>>>>> if_ath_load="yes" >>>>>> ifconfig_ath0="DHCP" >>>> to >>>> # ath new config >>>> wlans_ath0=wlan0 >>>> ifconfig_wlan0="WPA DHCP" >>>> >>>> My ifconfig is now: >>>> >>>> ath0: flags=8802 metric 0 mtu 2290 >>>> ether 00:1d:d9:27:5c:e5 >>>> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >>>> status: no carrier >>>> >>>> wlan0: flags=8802 metric 0 mtu 1500 >>> ^^^^^ >>> >>> For some reason your interface is not UP. The dhcp client should do this >>> so make sure its being launched. >> >> Thanks, Andrew. I haven't used wireless on freebsd since 802.11b on >> maybe 4.? before hostap, etc. etc. I need to get this running to >> relearn about wifi under freebsd. Unfortunately, I bought a laptop with >> an unsupported ath card but now that Sam's latest patch brings it and >> with the help from folks on the list I'm getting closer. >> >> You are right, Andrew, dhclient wasn't running so first I tried: >> # ifconfig wlan0 up >> ath0 then associated: >> ath0: flags=8843 metric 0 mtu 2290 >> ether 00:1d:d9:27:5c:e5 >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >> status: associated >> lo0: flags=8049 metric 0 mtu 16384 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 >> inet6 ::1 prefixlen 128 >> inet 127.0.0.1 netmask 0xff000000 >> pfsync0: flags=0<> metric 0 mtu 1460 >> syncpeer: 224.0.0.240 maxupd: 128 >> pflog0: flags=0<> metric 0 mtu 33160 >> wlan0: flags=8843 metric 0 mtu 1500 >> ether 00:1d:d9:27:5c:e5 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> ssid "" channel 4 (2427 Mhz 11g) >> regdomain 101 indoor ecm authmode OPEN privacy OFF txpower 16 bmiss 7 >> scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 >> roam:rate 5 protmode CTS wme burst bintval 0 >> but still no carrier on wlan0 :( >> >> so I tried >> >> # dhclient wlan0 >> wlan0: no link .............. giving up >> >> Trying >> # ifconfig wlan0 scan >> never finishes at least for the 10 minutes that I have left it. >> >> Just in case anyone wonders, I have an AP about 3 feet from where I'm >> working and an iPhone that finds about a 1/2 dozen on accessable AP's so >> it souldn't be a signal problem although all are using wep for auth. >> >> Anyone else have a suggestion? > > For some reason I had to do the following to assign: > > # ifconfig ath0 down > # ifconfig ath0 ssid "yourssid" > # ifconfig ath0 up > > Works fine with an Atheros AR5BXB63. > >> >> Thanks, >> >> ed >>> >>>> ether 00:1d:d9:27:5c:e5 >>>> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >>>> status: no carrier >>>> ssid "" channel 1 (2412 Mhz 11b) >>>> regdomain 101 indoor ecm authmode OPEN privacy OFF txpower 16 >>>> bmiss 7 >>>> scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 >>>> roam:rate 1 wme burst bintval 0 >>>> >>>> Both have "no carrier" and neither will do scan >>> _______________________________________________ >>> 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" >>> >> >> _______________________________________________ >> 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" >> >> -- >> Posted automagically by a mail2news gateway at muc.de e.V. >> Please direct questions, flames, donations, etc. to news-admin@muc.de > > From matthias.apitz at oclc.org Mon Jun 23 09:14:41 2008 From: matthias.apitz at oclc.org (Matthias Apitz) Date: Mon Jun 23 09:14:46 2008 Subject: ath_hal && eeePC 900 Message-ID: <20080623090232.GA13936@rebelion.Sisis.de> Hello, I followed the hints in http://nighthack.org/wiki/EeeBSD to make the wireless card working in my new eeePC 900 with FreeBSD 7.0R; after compiling and installing the patched kernel it says on boot ... kbd1 at kbdmux0 ath_hal: 0.10.2.2-ATHEROS (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425) hptrr: HPT RocketRAID controller driver v1.1 (May 9 2008 07:23:12) ... but no interface ath0 shows up; any ideas? 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/ b http://gurucubano.blogspot.com/ ?...una sola vez, que es cuanto basta si se trata de verdades definitivas.? ?...only once, which is enough if it has todo with definite truth.? Jos? Saramago, Historia del Cerca de Lisboa From matthias.apitz at oclc.org Mon Jun 23 09:30:22 2008 From: matthias.apitz at oclc.org (Matthias Apitz) Date: Mon Jun 23 09:30:26 2008 Subject: ath_hal && eeePC 900 In-Reply-To: <20080623090232.GA13936@rebelion.Sisis.de> References: <20080623090232.GA13936@rebelion.Sisis.de> Message-ID: <20080623093016.GA14750@rebelion.Sisis.de> El d?a Monday, June 23, 2008 a las 11:02:32AM +0200, Matthias Apitz escribi?: > > Hello, > > I followed the hints in > http://nighthack.org/wiki/EeeBSD > to make the wireless card working in my new eeePC 900 with FreeBSD 7.0R; > > after compiling and installing the patched kernel it says on boot > > ... > kbd1 at kbdmux0 > ath_hal: 0.10.2.2-ATHEROS (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425) > hptrr: HPT RocketRAID controller driver v1.1 (May 9 2008 07:23:12) > ... > > but no interface ath0 shows up; any ideas? thanks in advance I've found it; the wireless card was disabled in the BIOS for some reason; sorry to bother all the people; 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/ ?...una sola vez, que es cuanto basta si se trata de verdades definitivas.? ?...only once, which is enough if it has todo with definite truth.? Jos? Saramago, Historia del Cerca de Lisboa From matthias.apitz at oclc.org Mon Jun 23 12:36:52 2008 From: matthias.apitz at oclc.org (Matthias Apitz) Date: Mon Jun 23 12:36:58 2008 Subject: eeePC 900 && video cam Message-ID: <20080623123649.GA19895@rebelion.Sisis.de> Hello, I followed the hints in http://nighthack.org/wiki/EeeBSD to install FreeBSD 7.0R in my new Asus eeePC 900; attached is a complete installation guide; the (deleted) Linux saw the on board video cam with these messages: [ 11.540000] Linux video capture interface: v2.00 [ 11.560000] uvcvideo: Found UVC 1.00 device CNF7129 (04f2:b071) [ 11.690000] usbcore: registered new interface driver uvcvideo [ 11.690000] USB Video Class driver (SVN r2008.02.27) and it worked nicely; are there any plans or works for supporting this card? thx 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/ b http://gurucubano.blogspot.com/ ?...una sola vez, que es cuanto basta si se trata de verdades definitivas.? ?...only once, which is enough if it has todo with definite truth.? Jos? Saramago, Historia del Cerca de Lisboa -------------- next part -------------- $Id: installEeePC.txt,v 1.1 2008/06/23 07:49:29 guru Exp $ How I have installed FreeBSD 7.0-RELEASE in the Asus eeePC 900 First prepare an USB key with: - a booting FreeBSD 7.0R - the tree of the disk1 below /disk1, as minimum: disk1/7.0-RELEASE disk1/packages How to do this is documented on Internet already, see for example: http://groups.google.com/group/lucky.freebsd.questions/msg/5c759b1c87376b22 The eeePC 900 comes with two separate SSD's which will show up in FreeBSD as /dev/ad2 (4 GByte) /dev/ad3 (16 GByte) even if you can boot /dev/ad3 from the boot-monitor (press ESC after power-on), it seems that the BIOS by its own can only boot from the first SSD, the so called OB (on board) SSD; so we will install the system in /dev/ad2; create a new partition table on /dev/ad2 with a default slice 1 and make it boot-able: # fdisk -BI /dev/ad2 (ignore any errors) label it for booting freebsd: # bsdlabel -wB /dev/ad2s1 edit the disk label and change partition a from "unused" to "4.2BSD" as partition type: # setenv EDITOR /usr/bin/vi # bsdlabel -e /dev/ad2s1 create the future root-filesystem on it and mount it to /mnt for the installation: # newfs -m 0 -o space /dev/ad2s1a # mount /dev/ad3s1a /mnt install freebsd into /mnt; this assumes that you have copied the FreeBSD distribution into your USB key below /disk1/7.0-RELEASE: # setenv DESTDIR /mnt # cd /disk1/7.0-RELEASE # cd base # ./install.sh You are about to extract the base distribution into /mnt - are you SURE you want to do this over your installed system (y/n): y # cd ../manpages # ./install.sh # cd ../catpages # ./install.sh go to the kernels directory and install a kernel of your choice: [default is GENERIC kernel; change to "smp" for smp-machines] # rmdir /mnt/boot/kernel # cd ../kernels; # cat generic.?? | tar --unlink -xpzf - -C /mnt/boot # cd /mnt/boot # mv GENERIC kernel now, tell FreeBSD to mount later the correct root-filesystem: # echo "/dev/ad3s1a / ufs rw,noatime 1 1" >/mnt/etc/fstab create your rc.conf.local in /mnt/etc to redefine some settings: # cat </mnt/etc/rc.conf.local #!/bin/sh tmpmfs="YES" tmpsize="128m" hostname="tiny" keyrate="fast" EOFRCCONF # chmod 0755 /mnt/etc/rc.conf.local set a new root password manually, if you want (default="") # chroot /mnt /usr/bin/passwd root unmount the new root /mnt and reboot the eeePC: # cd # umount /mnt # reboot when the system comes up again, use 'sysinstall' for installation of Xorg mount the USB key as: # mount -o ro /dev/da0s1a /mnt # sysinstall-->Configure-->Distributions-->X.org from installation media 'File System' and pointed to /mnt/disk1; again this assumes that you have copied the FreeBSD distribution into your USB key below /disk1/packages: remove the package 'xf86-video-i810-1.6.5_3' and install correct video drivers for the Intel chip-set; the package must be pulled from FreeBSD web sites, i.e. it is not part of the default 7.0-R distribution CD: # pkg_delete -f xf86-video-i810-1.6.5_3 # cd /mnt/eeePC # pkg_add xf86-video-intel-2.1.1.tbz login again to refresh the PATH only use 'sysinstall' to activate the mouse daemon and configure the X server: # Xorg -configure before deleting the Linux on the eeePC I saved the original xorg.conf and merged the Monitor section into the generated xorg.conf as: Section "Monitor" Identifier "Monitor0" VendorName "ASUS" ModelName "Eee PC P900" Modeline "1024x600" 48.96 1024 1064 1168 1312 600 601 604 622 -HSync +Vsync EndSection # cp xorg.conf.new /etc/X11/xorg.conf adjust /etc/rc.conf file with: syslogd_enable="NO" sendmail_enable="NONE" adjust /boot/loader.conf file with: snd_hda_load="YES" on the second disk /dev/ad3 I created one big UFS and mounted this as /usr/home; on my 'normal' laptop with the same FreeBSD version I created packages of all ports I have installed on this, around 640 ports which are in packages 1.2 GByte; I moved them with the USB key to /usr/home/PKGDIR and installed the KDE environment (and all other stuff) just with: # cd /usr/home/PKGDIR # pkg_add kde-3.5.8.tbz to be continued ... (with the kernel module ath_hal.ko) as said in http://nighthack.org/wiki/EeeBSD fetch the 'ath' update from http://snapshots.madwifi.org/special/madwifi-ng-r2756+ar5007.tar.gz I have updated with this patch the kernel in my 'normal' laptop as: # cd /usr/src/sys/contrib/dev # mv ath ath.orig # mkdir ath # cd /tmp # tar xzf madwifi-ng-r2756+ar5007.tar.gz # cd madwifi-ng-r2756+ar5007/hal # cp -R * /usr/src/sys/contrib/dev/ath/ # cd /usr/src/sys/i386/compile/REBELION # make depend # make # make install # cd /boot # mv kernel kernel.ath # mv kernel.old kernel move over the kernel to the eeePC and unpack it there into /boot: # mount /dev/da0s1a /mnt # tar cfz /mnt/eeePC/kernel.tar.gz kernel.ath # cp /etc/wpa_supplicant.conf /mnt/eeePC # mkdir /mnt/eeePC/usr-local-etc-devd # cp /usr/local/etc/devd/* /mnt/eeePC/usr-local-etc-devd # umount /mnt the ath0 comes up and works normaly with 'wpa_supplicant' and the hooks in devd(8) on IF_UP / IF_DOWN From eculp at cloudmaster.info Fri Jun 27 00:48:29 2008 From: eculp at cloudmaster.info (eculp@cloudmaster.info) Date: Fri Jun 27 00:48:34 2008 Subject: Trying to use my ath wireless with wep. Message-ID: <20080626194816.16432an8womc69c0@cloudmail.cloudmaster.info> Thanks to the help here I have been enjoying my ath for almost a week. It works perfectly with the following in rc.conf wlans_ath0=wlan0 ifconfig_wlan0="DHCP ssid virus2" Now I am trying to get it to connect with wep. I have set the modem open wep pass phrase key to lets say 1122334455 and I have substituted the above ifconfig_wlan0 line for: ifconfig_wlan0="DHCP ssid virus2 wepmode on wepkey 0x1122334455" and I have also tried it with WPA before DHCP but it doesn't connect either way. I'm sure I'm not understanding something here. I also have a related question. Can this not be done on the command line and be prompted for a password after the scan to see which AP is available? What would I do after the scan? Thanks, ed Info: # uname -a FreeBSD ed.local.net.mx 8.0-CURRENT FreeBSD 8.0-CURRENT #126: Thu Jun 19 13:08:54 CDT 2008 root@ed.local.net.mx:/usr/obj/usr/src/sys/ENCONTACTO amd64 From thompsa at FreeBSD.org Fri Jun 27 00:59:15 2008 From: thompsa at FreeBSD.org (Andrew Thompson) Date: Fri Jun 27 00:59:22 2008 Subject: Trying to use my ath wireless with wep. In-Reply-To: <20080626194816.16432an8womc69c0@cloudmail.cloudmaster.info> References: <20080626194816.16432an8womc69c0@cloudmail.cloudmaster.info> Message-ID: <20080627010037.GA60479@citylink.fud.org.nz> On Thu, Jun 26, 2008 at 07:48:16PM -0500, eculp@cloudmaster.info wrote: > Thanks to the help here I have been enjoying my ath for almost a week. It > works perfectly with the following in rc.conf > > wlans_ath0=wlan0 > ifconfig_wlan0="DHCP ssid virus2" > > Now I am trying to get it to connect with wep. I have set the modem open > wep pass phrase key to lets say 1122334455 and I have substituted the above > ifconfig_wlan0 line for: > > ifconfig_wlan0="DHCP ssid virus2 wepmode on wepkey 0x1122334455" > > > and I have also tried it with WPA before DHCP but it doesn't connect either > way. I believe you need to also set 'deftxkey 1', see ifconfig(8). Andrew From eculp at cloudmaster.info Fri Jun 27 01:44:48 2008 From: eculp at cloudmaster.info (eculp@cloudmaster.info) Date: Fri Jun 27 01:44:52 2008 Subject: Trying to use my ath wireless with wep. In-Reply-To: <20080627010037.GA60479@citylink.fud.org.nz> References: <20080626194816.16432an8womc69c0@cloudmail.cloudmaster.info> <20080627010037.GA60479@citylink.fud.org.nz> Message-ID: <20080626204435.85586peh08oj4hs0@cloudmail.cloudmaster.info> Quoting Andrew Thompson : > On Thu, Jun 26, 2008 at 07:48:16PM -0500, eculp@cloudmaster.info wrote: >> Thanks to the help here I have been enjoying my ath for almost a week. It >> works perfectly with the following in rc.conf >> >> wlans_ath0=wlan0 >> ifconfig_wlan0="DHCP ssid virus2" >> >> Now I am trying to get it to connect with wep. I have set the modem open >> wep pass phrase key to lets say 1122334455 and I have substituted the above >> ifconfig_wlan0 line for: >> >> ifconfig_wlan0="DHCP ssid virus2 wepmode on wepkey 0x1122334455" >> >> >> and I have also tried it with WPA before DHCP but it doesn't connect either >> way. > > I believe you need to also set 'deftxkey 1', see ifconfig(8). Thanks, Andrew. I went the weptxkey route that is an alias according to the manual and at the same time caught the space between the : and the key from david's suggestion. Thanks, that makes my life much better. Now to solve my multiple hotspot needs and I will be a happy camper. Thanks again, ed > > > Andrew > _______________________________________________ > 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 eculp at cloudmaster.info Fri Jun 27 10:35:08 2008 From: eculp at cloudmaster.info (eculp@cloudmaster.info) Date: Fri Jun 27 10:35:13 2008 Subject: Trying to use my ath wireless with wep. In-Reply-To: <200806262050.32487.davidb@boothscientific.com> References: <20080626194816.16432an8womc69c0@cloudmail.cloudmaster.info> <200806262003.26539.davidb@boothscientific.com> <20080626204122.183491gyp31lfozm@cloudmail.cloudmaster.info> <200806262050.32487.davidb@boothscientific.com> Message-ID: <20080627053455.917017l4elw9ulog@cloudmail.cloudmaster.info> Quoting David Booth : > On Thursday 26 June 2008, you wrote: >> Quoting David Booth : >> > On Thursday 26 June 2008, you wrote: >> >> Thanks to the help here I have been enjoying my ath for almost a >> >> week. It works perfectly with the following in rc.conf >> >> >> >> wlans_ath0=wlan0 >> >> ifconfig_wlan0="DHCP ssid virus2" >> >> >> >> Now I am trying to get it to connect with wep. I have set the >> >> modem open wep pass phrase key to lets say 1122334455 and I have >> >> substituted the above ifconfig_wlan0 line for: >> >> >> >> ifconfig_wlan0="DHCP ssid virus2 wepmode on wepkey 0x1122334455" >> >> >> >> >> >> and I have also tried it with WPA before DHCP but it doesn't >> >> connect either way. >> >> >> >> I'm sure I'm not understanding something here. >> >> >> >> I also have a related question. Can this not be done on the >> >> command line and be prompted for a password after the scan to >> >> see which AP is available? What would I do after the scan? >> >> >> >> Thanks, >> >> >> >> ed >> > >> > I have found it necessary to specify the wepkey number and also >> > set the weptxkey number, e.g. >> > >> > ifconfig_wlan0="DHCP ssid virus2 wepmode on wepkey 1: >> > 0x1122334455 weptxkey 1" >> >> Hi David, >> >> It worked perfectly but I did have to remove the space between 1: >> and 0x1122334455. I saw that in the ifconfig manual from Andrew >> Thompson's recommendation. >> >> Thanks. Now all I need to find is a tool to connect to the some >> 8-10 offices, hotspots, home etc. That I use weekly. I think I >> will soon get tired of commenting out configurations in rc.local ;) >> >> Hope you all have a great weekend, >> >> ed > > I you should be able to do this with wpa_supplicant. I have not tried > it, but you are supposed to be able to put multiple hot spot > configurations in wpa_suplicant.conf (and can assign priorities) and > it will scan through them until it finds one. See > > man wpa_supplicant.conf > > and > > man wpa_supplicant > Thanks, David. This seems to be exactly what I am looking for. I've already started to configure it with the example in share. With all the tips you have given me I should be able to make all this much more efficiently and not have to add any more noise to the list. I really appreciate it, ed From prabu at hackinthebox.org Sat Jun 28 01:48:56 2008 From: prabu at hackinthebox.org (Praburaajan) Date: Sat Jun 28 01:49:00 2008 Subject: CFP For HITBSecConf2008 - Malaysia Closing Soon Message-ID: <4865904E.9060807@hackinthebox.org> This is a reminder that the Call for Papers for HITBSecConf2008 - Malaysia is closing on the 30th of June. The HITBSecConf series is a deep-knowledge technical conference. Talks that are more technical or that discuss new and never before seen attack methods are of more interest than a subject that has been covered several times before. Details on topics of interest and submission guidelines are listed on the conference page: http://conference.hackinthebox.org/hitbsecconf2008kl/?page_id=72 https://conference.hitb.org/hitbsecconf2008kl/?page_id=72 We look forward to receiving your submissions! From spideyfan1972 at gmail.com Sat Jun 28 06:44:55 2008 From: spideyfan1972 at gmail.com (Isaac MacFarlane) Date: Sat Jun 28 06:44:59 2008 Subject: Acer 4720Z and Atheros wireless card Message-ID: Hello all. I am trying to find a *NIX system that will work with this system. Mandriva calls the card an AR5006 and Vista said it was an AR5007. Vista worked fine for about a month or so, but I have decided I want to go all free on my systems. Mandriva will work with the card but locks up after a few hours requiring a restart. Not really acceptable. And it is the best I found in the Linux world. Would any of the BSD systems work with this card? Any recommendations would be most appreciated. Isaac MacFarlane From sonic2000gr at gmail.com Sat Jun 28 07:21:54 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Sat Jun 28 07:21:58 2008 Subject: Acer 4720Z and Atheros wireless card In-Reply-To: References: Message-ID: <4865E008.4070108@gmail.com> Isaac MacFarlane wrote: > Hello all. I am trying to find a *NIX system that will work with this > system. Mandriva calls the card an AR5006 and Vista said it was an AR5007. > Vista worked fine for about a month or so, but I have decided I want to go > all free on my systems. Mandriva will work with the card but locks up after > a few hours requiring a restart. Not really acceptable. And it is the best I > found in the Linux world. Would any of the BSD systems work with this card? > Any recommendations would be most appreciated. > > Isaac MacFarlane > _______________________________________________ > 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 believe this will work if you follow the instructions to build a custom kernel, as in the eeepc: http://nighthack.org/wiki/EeeBSD However, this will not be the easiest task if you are not familiar with FreeBSD in general. From eculp at cloudmaster.info Sat Jun 28 11:48:19 2008 From: eculp at cloudmaster.info (eculp@cloudmaster.info) Date: Sat Jun 28 11:48:22 2008 Subject: Acer 4720Z and Atheros wireless card In-Reply-To: <4865E008.4070108@gmail.com> References: <4865E008.4070108@gmail.com> Message-ID: <20080628064756.13091leqmql1eu4g@cloudmail.cloudmaster.info> Quoting Manolis Kiagias : > Isaac MacFarlane wrote: >> Hello all. I am trying to find a *NIX system that will work with this >> system. Mandriva calls the card an AR5006 and Vista said it was an AR5007. >> Vista worked fine for about a month or so, but I have decided I want to go >> all free on my systems. Mandriva will work with the card but locks up after >> a few hours requiring a restart. Not really acceptable. And it is the best I >> found in the Linux world. Would any of the BSD systems work with this card? >> Any recommendations would be most appreciated. >> >> Isaac MacFarlane >> _______________________________________________ >> 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 believe this will work if you follow the instructions to build a > custom kernel, as in the eeepc: > > http://nighthack.org/wiki/EeeBSD > > However, this will not be the easiest task if you are not familiar > with FreeBSD in general. As Manolis says, step one would be to install FreeBSD and see if you are confortable with it. Then once you have it all running you will want to use the link that Manolis sent that I found very interesting but didn't work for the atheros that I have in my Acer amd64x2 so I used a freebsd patch that works beautifully. When you get to that point, I or I'm sure other more qualified folks, will be glad to give you a hand. good luck, ed From eculp at cloudmaster.info Sun Jun 29 02:19:40 2008 From: eculp at cloudmaster.info (eculp@cloudmaster.info) Date: Sun Jun 29 02:19:45 2008 Subject: Acer 4720Z and Atheros wireless card In-Reply-To: References: <4865E008.4070108@gmail.com> <20080628064756.13091leqmql1eu4g@cloudmail.cloudmaster.info> Message-ID: <20080628211927.19291rwcfx4c3gbo@cloudmail.cloudmaster.info> Quoting Isaac MacFarlane : > Well, I do have a copy of PCBSD already downloaded. If I understand > correctly that is a branch of the main FreeBSD project. Is that correct? Is > there any reason why I would go with that over the main FreeBSD project? > They both look very nice, but I'm not sure which way to go. They seem to > both support the same software and hardware. Is one more free than the > other? AFAIK, there is little difference but I've never used pcbsd although I have though about trying it but haven't had time. I'm copying to the list so that someone with knowledge of PCBSD can answer this correctly. ed > > On Sat, Jun 28, 2008 at 5:47 AM, wrote: > >> Quoting Manolis Kiagias : >> >> Isaac MacFarlane wrote: >>> >>>> Hello all. I am trying to find a *NIX system that will work with this >>>> system. Mandriva calls the card an AR5006 and Vista said it was an >>>> AR5007. >>>> Vista worked fine for about a month or so, but I have decided I want to >>>> go >>>> all free on my systems. Mandriva will work with the card but locks up >>>> after >>>> a few hours requiring a restart. Not really acceptable. And it is the >>>> best I >>>> found in the Linux world. Would any of the BSD systems work with this >>>> card? >>>> Any recommendations would be most appreciated. >>>> >>>> Isaac MacFarlane >>>> _______________________________________________ >>>> 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 believe this will work if you follow the instructions to build a custom >>> kernel, as in the eeepc: >>> >>> http://nighthack.org/wiki/EeeBSD >>> >>> However, this will not be the easiest task if you are not familiar with >>> FreeBSD in general. >>> >> >> As Manolis says, step one would be to install FreeBSD and see if you are >> confortable with it. Then once you have it all running you will want to use >> the link that Manolis sent that I found very interesting but didn't work for >> the atheros that I have in my Acer amd64x2 so I used a freebsd patch that >> works beautifully. When you get to that point, I or I'm sure other more >> qualified folks, will be glad to give you a hand. >> >> good luck, >> >> ed >> >> >> _______________________________________________ >> 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 matt at ixsystems.com Sun Jun 29 03:47:11 2008 From: matt at ixsystems.com (Matt Olander) Date: Sun Jun 29 03:47:14 2008 Subject: Acer 4720Z and Atheros wireless card In-Reply-To: <20080628211927.19291rwcfx4c3gbo@cloudmail.cloudmaster.info> References: <4865E008.4070108@gmail.com> <20080628064756.13091leqmql1eu4g@cloudmail.cloudmaster.info> <20080628211927.19291rwcfx4c3gbo@cloudmail.cloudmaster.info> Message-ID: <9740caf0806282022i1adced86i49075545cef9006e@mail.gmail.com> On Sat, Jun 28, 2008 at 7:19 PM, wrote: > Quoting Isaac MacFarlane : > >> Well, I do have a copy of PCBSD already downloaded. If I understand >> correctly that is a branch of the main FreeBSD project. Is that correct? >> Is >> there any reason why I would go with that over the main FreeBSD project? >> They both look very nice, but I'm not sure which way to go. They seem to >> both support the same software and hardware. Is one more free than the >> other? > > AFAIK, there is little difference but I've never used pcbsd although I have > though about trying it but haven't had time. The current release version of PC-BSD is based on FreeBSD 6.3. They are exactly the same but PC-BSD has been custom configured to provide a usable desktop from first boot. For that particular card, you will need the hal that is in FreeBSD7. I don't believe it was ever MFC'd back to 6.x. You can either grab FreeBSD 7 or try out the PC-BSD alpha at ftp://ftp.pcbsd.org/pub/alpha-isos/i386/. There will be a new PC-BSD alpha up next week. best, -matt > > I'm copying to the list so that someone with knowledge of PCBSD can answer > this correctly. > > ed >> >> On Sat, Jun 28, 2008 at 5:47 AM, wrote: >> >>> Quoting Manolis Kiagias : >>> >>> Isaac MacFarlane wrote: >>>> >>>>> Hello all. I am trying to find a *NIX system that will work with this >>>>> system. Mandriva calls the card an AR5006 and Vista said it was an >>>>> AR5007. >>>>> Vista worked fine for about a month or so, but I have decided I want to >>>>> go >>>>> all free on my systems. Mandriva will work with the card but locks up >>>>> after >>>>> a few hours requiring a restart. Not really acceptable. And it is the >>>>> best I >>>>> found in the Linux world. Would any of the BSD systems work with this >>>>> card? >>>>> Any recommendations would be most appreciated. >>>>> >>>>> Isaac MacFarlane >>>>> _______________________________________________ >>>>> 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 believe this will work if you follow the instructions to build a >>>> custom >>>> kernel, as in the eeepc: >>>> >>>> http://nighthack.org/wiki/EeeBSD >>>> >>>> However, this will not be the easiest task if you are not familiar with >>>> FreeBSD in general. >>>> >>> >>> As Manolis says, step one would be to install FreeBSD and see if you are >>> confortable with it. Then once you have it all running you will want to >>> use >>> the link that Manolis sent that I found very interesting but didn't work >>> for >>> the atheros that I have in my Acer amd64x2 so I used a freebsd patch that >>> works beautifully. When you get to that point, I or I'm sure other more >>> qualified folks, will be glad to give you a hand. >>> >>> good luck, >>> >>> ed >>> >>> >>> _______________________________________________ >>> 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" >>> >> > > _______________________________________________ > 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" >