From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 04:00:23 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61E9416A4C0 for ; Sun, 7 Sep 2003 04:00:23 -0700 (PDT) Received: from mailhub02.unibe.ch (mailhub02-skge0.unibe.ch [130.92.9.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7068A43FDD for ; Sun, 7 Sep 2003 04:00:20 -0700 (PDT) (envelope-from roth@iam.unibe.ch) Received: from localhost (localhost [127.0.0.1]) by mailhub02.unibe.ch (Postfix) with ESMTP id 12B4476D58; Sun, 7 Sep 2003 13:00:19 +0200 (MEST) Received: from mailhub02.unibe.ch ([127.0.0.1]) by localhost (mailhub02 [127.0.0.1:10024]) (amavisd-new) with LMTP id 22030-01-99; Sun, 7 Sep 2003 13:00:18 +0200 (MEST) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub02.unibe.ch (Postfix) with ESMTP id 568CF76D65; Sun, 7 Sep 2003 13:00:18 +0200 (MEST) Received: from speedy.unibe.ch (speedy [130.92.64.35]) by asterix.unibe.ch (8.11.6+Sun/8.11.6) with ESMTP id h87B0IK16392; Sun, 7 Sep 2003 13:00:18 +0200 (MET DST) Received: (from roth@localhost) by speedy.unibe.ch (8.11.6+Sun/8.10.2) id h87B0HR15485; Sun, 7 Sep 2003 13:00:17 +0200 (MEST) Date: Sun, 7 Sep 2003 13:00:17 +0200 From: Tobias Roth To: James Earl Message-ID: <20030907110017.GA15472@speedy.unibe.ch> Mail-Followup-To: James Earl , freebsd-mobile@freebsd.org References: <20030906184417.GC752@h24-64-142-219.lb.shawcable.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030906184417.GC752@h24-64-142-219.lb.shawcable.net> User-Agent: Mutt/1.4i X-Operating-System: SunOS speedy 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-80 X-Virus-checked: by University of Berne cc: freebsd-mobile@freebsd.org Subject: Re: Another ThinkPad R40 setup X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2003 11:00:23 -0000 adjusting the bios settings for the irq is the way to go, not just disabling devices. if your R40 is anything like my T30, the settings you will find here (in my comment to Kevins entry for the T30) will help you use all devices at the same time. http://gerda.univie.ac.at/freebsd-laptops/ i already mentioned thise a few times on mobile/current. good luck, t. On Sat, Sep 06, 2003 at 12:44:17PM -0600, James Earl wrote: > >> The first problem was with the fxp device, and "device timeouts." I > >> got past that by commenting out sio and pcmcia related devices in > >> the kernel. I still need to go back and see if it was sio or > >> pcmcia stuff, or part of the pcmcia devices. > > > >Just disable sio1 in /boot/device.hints. No reason to disable stuff > >that you actually have! Just add hint.sio.1.disabled="1". That will > >free up an IRQ. > > I gave that a try, and re-enabled the pcmcia devices and it looks like > disabling sio devices doesn't have any effect in solving the device > timeouts. > > I also tried enabling only some of the pcmcia devices - non of the > configurations solved the problem either. The only thing that fixed > the device timeouts for me so far is completely commenting out pcmcia > devices: > > #device cbb # cardbus (yenta) bridge > #device pcic # ExCA ISA and PCI bridges > #device pccard # PC Card (16-bit) bus > #device cardbus # CardBus (32-bit) bus > > Here's the output from when I do have cbb, pccard, and cardbus built: > > cbb0: irq 11 at device 0.0 on pci2 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb0: [MPSAFE] > cbb0: Unsupported card type detected > > (I noticed TI1510 isn't listed in the pccbb(4) manpage - I'm not sure > what this means?) > > Commenting out pcmcia devices on a notebook isn't really a great > solution, although I'll probably never use a pcmcia card! :) > > Is there any other way I can free an IRQ and still have pcmcia devices > enabled? I tried playing with some of the PCI BIOS settings with no > luck. I can change the irq's of what's listed below (dmesg output) in > the BIOS setup, or change it to "disabled" or "automatic": > > pcib0: slot 29 INTA is routed to irq 11 > pcib0: slot 29 INTB is routed to irq 11 > pcib0: slot 29 INTC is routed to irq 11 > pcib0: slot 29 INTD is routed to irq 11 > pcib0: slot 31 INTB is routed to irq 11 > pcib0: slot 31 INTB is routed to irq 11 > pcib0: slot 31 INTB is routed to irq 11 > > Actually I believe in the BIOS setup it's more like INTA to INTF or > something. All are set to irq 11 currently. > > >> This looks like 5.1-Release. These should be fixed in CURRENT and > >> can be ignored in most cases during RELEASE. (It was a chicken/egg > >> issue that Nate fixed doing some rather "odd" things to get some of > >> the ACPI code to run before it would normally be started.) > > I updated my system to 5.1-CURRENT and the error messages are gone. > Thanks for the tip. It doesn't look like ACPI suspend states work too > hot on this notebook! S5 will almost turn off the notebook, but stops > at "Powering system off using ACPI." S4 just freezes the system. > > Is it mainly the manufacturers that are having a hard time keeping to > the ACPI standards? > > _______________________________________________ > 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 owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 07:19:59 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FBEB16A4BF for ; Sun, 7 Sep 2003 07:19:59 -0700 (PDT) Received: from accms33.physik.rwth-aachen.de (accms33.physik.RWTH-Aachen.DE [137.226.46.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E39C43FE0 for ; Sun, 7 Sep 2003 07:19:58 -0700 (PDT) (envelope-from kuku@accms33.physik.rwth-aachen.de) Received: (from kuku@localhost) by accms33.physik.rwth-aachen.de (8.11.6/8.9.3) id h87EJuK02291 for freebsd-mobile@freebsd.org; Sun, 7 Sep 2003 16:19:56 +0200 Date: Sun, 7 Sep 2003 16:19:56 +0200 From: Christoph Kukulies Message-Id: <200309071419.h87EJuK02291@accms33.physik.rwth-aachen.de> To: freebsd-mobile@freebsd.org Subject: wi woes X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2003 14:19:59 -0000 Besides the still existing busy bit not clear or cmd timeout weirdnesses which make it really a pain to use my notebook an the wlan at the moment I observed another strangeness which might perhaps be more concise and to track down than the other effects, which seem to be independent from whether I have device pcic in kernel or not. The following happened when I inserted the card after the notebook was up: wi0: bad alloc 1fb != 1f8, cur 0 nxt 0 Another effect was that the machine totally froze, no panic, no ctrl-alt-del possible (machine was in vty mode), when I typed in dhclient wi0 Sometimes dhclient came back after a couple of seconds with setting the interface IP, other times it came back immediately with no effect and third, the worst case, it froze the machine. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 09:43:38 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ACBF16A4BF; Sun, 7 Sep 2003 09:43:38 -0700 (PDT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 9A6AC43FDF; Sun, 7 Sep 2003 09:43:36 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Sep 2003 17:43:31 +0100 (BST) To: deischen@freebsd.org In-Reply-To: Your message of "Sat, 06 Sep 2003 04:48:39 EDT." Date: Sun, 07 Sep 2003 17:43:29 +0100 From: Ian Dowse Message-ID: <200309071743.aa44498@salmon.maths.tcd.ie> cc: kuku@physik.rwth-aachen.de cc: "M. Warner Losh" cc: John Birrell cc: freebsd-mobile@freebsd.org Subject: Re: wi0_cmd: busy bit won't clear X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2003 16:43:38 -0000 In message , Daniel Eischen writes: >Hmm, some of us get it in the reverse -- when the machine boots >with the card in, we get that message. Removing and reinserting >the card after boot seems to work better, but perhaps that's >just my imagination -- I still sometimes have the same problem >when reinserting the card. I have found it almost impossible to determine if any particular change helps or not, as invariably when I do find something that survives 5 or 10 removal/reinsert cycles, I get the error again a few days later and the error frequency seems unchanged. FYI, I use the collection of fairly arbitrary changes in the following patch. This does not fix the problem, but it shortens the hard hangs to about 1 second instead of minutes, and I think some of the extra DELAY() calls help to reduce the frequency of the errors, but that may just my imagination too (certainly most of them make no difference whatsoever). The "!= WI_INTERSIL" bit fixes the "bad alloc" errors by reverting revision 1.142. Ian Index: if_wi.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/dev/wi/if_wi.c,v retrieving revision 1.151 diff -u -r1.151 if_wi.c --- if_wi.c 5 Sep 2003 22:29:30 -0000 1.151 +++ if_wi.c 7 Sep 2003 16:17:23 -0000 @@ -502,7 +502,7 @@ WI_LOCK(sc); /* check if device was removed */ - sc->wi_gone = !bus_child_present(dev); + sc->wi_gone |= !bus_child_present(dev); wi_stop(ifp, 0); @@ -751,6 +751,7 @@ } sc->sc_txcur = sc->sc_txnext = 0; + DELAY(10000); /* Enable desired port */ wi_cmd(sc, WI_CMD_ENABLE | sc->sc_portnum, 0, 0, 0); @@ -808,10 +809,14 @@ WI_LOCK(sc); + DELAY(50000); + ieee80211_new_state(ic, IEEE80211_S_INIT, -1); if (sc->sc_enabled && !sc->wi_gone) { CSR_WRITE_2(sc, WI_INT_EN, 0); + DELAY(10000); wi_cmd(sc, WI_CMD_DISABLE | sc->sc_portnum, 0, 0, 0); + DELAY(10000); if (disable) { #ifdef __NetBSD__ if (sc->sc_disable) @@ -983,7 +988,7 @@ int tries; /* Symbol firmware cannot be initialized more than once */ - if (sc->sc_firmware_type != WI_INTERSIL && sc->sc_reset) + if (sc->sc_firmware_type == WI_SYMBOL && sc->sc_reset) return (0); if (sc->sc_firmware_type == WI_SYMBOL) tries = 1; @@ -1002,12 +1007,15 @@ return (error); } + DELAY(10 * 1000); CSR_WRITE_2(sc, WI_INT_EN, 0); CSR_WRITE_2(sc, WI_EVENT_ACK, 0xFFFF); /* Calibrate timer. */ wi_write_val(sc, WI_RID_TICK_TIME, 8); + DELAY(10 * 1000); + return (0); #undef WI_INIT_TRIES } @@ -1597,6 +1605,9 @@ struct ifnet *ifp = &ic->ic_if; int fid, cur; + if (sc->wi_gone) + return; + fid = CSR_READ_2(sc, WI_ALLOC_FID); CSR_WRITE_2(sc, WI_EVENT_ACK, WI_EV_ALLOC); @@ -2363,18 +2374,22 @@ int i, s = 0; static volatile int count = 0; + if (sc->wi_gone) + return (ENODEV); + if (count > 0) panic("Hey partner, hold on there!"); count++; /* wait for the busy bit to clear */ - for (i = 500; i > 0; i--) { /* 5s */ + for (i = 500; i > 0; i--) { /* 500ms */ if (!(CSR_READ_2(sc, WI_COMMAND) & WI_CMD_BUSY)) break; - DELAY(10*1000); /* 10 m sec */ + DELAY(1*1000); /* 1ms */ } if (i == 0) { device_printf(sc->sc_dev, "wi_cmd: busy bit won't clear.\n" ); + sc->wi_gone = 1; count--; return(ETIMEDOUT); } @@ -2411,8 +2426,12 @@ if (i == WI_TIMEOUT) { device_printf(sc->sc_dev, "timeout in wi_cmd 0x%04x; event status 0x%04x\n", cmd, s); + if (s == 0xffff) + sc->wi_gone = 1; return(ETIMEDOUT); } + if (cmd == WI_CMD_INI) + DELAY(5000); return (0); } @@ -2432,6 +2451,8 @@ device_printf(sc->sc_dev, "timeout in wi_seek to %x/%x\n", id, off); sc->sc_bap_off = WI_OFF_ERR; /* invalidate */ + if (status == 0xffff) + sc->wi_gone = 1; return ETIMEDOUT; } DELAY(1); From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 12:11:14 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2D9F16A4C1 for ; Sun, 7 Sep 2003 12:11:14 -0700 (PDT) Received: from pd3mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD77543FBF for ; Sun, 7 Sep 2003 12:11:12 -0700 (PDT) (envelope-from jdearl@telus.net) Received: from pd2mr3so.prod.shaw.ca (pd2mr3so-ser.prod.shaw.ca [10.0.141.108])2003))freebsd-mobile@freebsd.org; Sun, 07 Sep 2003 13:05:26 -0600 (MDT) Received: from pn2ml9so.prod.shaw.ca (pn2ml9so-qfe0.prod.shaw.ca [10.0.121.7]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HKU00B9UYD2EO@l-daemon> for freebsd-mobile@freebsd.org; Sun, 07 Sep 2003 13:05:26 -0600 (MDT) Received: from h24-64-142-219.lb.shawcable.net ([24.64.142.219]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HKU00J0CYD2EV@l-daemon> for freebsd-mobile@freebsd.org; Sun, 07 Sep 2003 13:05:26 -0600 (MDT) Date: Sun, 07 Sep 2003 13:05:18 -0600 From: James Earl In-reply-to: <"from roth"@iam.unibe.ch> To: Tobias Roth Message-id: <20030907190518.GA597@h24-64-142-219.lb.shawcable.net> MIME-version: 1.0 X-Mailer: Balsa 2.0.14 Content-type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline Lines: 38 References: <20030906184417.GC752@h24-64-142-219.lb.shawcable.net> <20030907110017.GA15472@speedy.unibe.ch> cc: freebsd-mobile@freebsd.org Subject: Re: Another ThinkPad R40 setup X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2003 19:11:14 -0000 On 09/07/03 05:00:17, Tobias Roth wrote: > adjusting the bios settings for the irq is the way to go, not just > disabling devices. if your R40 is anything like my T30, the settings > you will find here (in my comment to Kevins entry for the T30) will > help you use all devices at the same time. > > http://gerda.univie.ac.at/freebsd-laptops/ > > i already mentioned thise a few times on mobile/current. > > good luck, t. Thanks for the help. "5,9,10,11,11,9,10,11" didn't work for me, however, you did inspire me to play with the bios settings! Here's what I found when I individually changed the values in the BIOS setup: BIOS FREEBSD BOOT MESSAGE ---- -------------------- INTA Slot 29 INTA INTB Slot 31 INTB Slot 31 INTB Slot 31 INTB INTC Slot 29 INTC INTD Slot 29 INTB INTE ? INTF ? INTG ? INTH Slot 29 INTD Now, while I have no clue what that means :), I was able to find out that if I changed either INTD or INTE in the BIOS setup, the fxp0 device worked and the device timeouts were gone. So my setup right now is: 11,11,11,10,11,11,11,11 Now to setup APM ... From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 15:08:41 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01AED16A4BF for ; Sun, 7 Sep 2003 15:08:41 -0700 (PDT) Received: from white.dogwood.com (white.dogwood.com [66.91.140.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 537D443FEC for ; Sun, 7 Sep 2003 15:08:39 -0700 (PDT) (envelope-from dave@dogwood.com) Received: from keiki.dogwood.com (keiki.dogwood.com [192.168.231.101]) by white.dogwood.com (8.12.9/8.12.9) with ESMTP id h87M8aNn010201 for ; Sun, 7 Sep 2003 12:08:38 -1000 (HST) (envelope-from dave@dogwood.com) Message-Id: <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> X-Sender: dave@white.dogwood.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sun, 07 Sep 2003 12:08:34 -1000 To: freebsd-mobile@freebsd.org From: David Cornejo Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: atheros adhoc mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2003 22:08:41 -0000 Hi, We're evaluating the Soekris 4801 and a 5212 based mini-PCI radio - It works well enough in infrastructure mode, but I'm having problems with adhoc. When the radio is operating in adhoc mode, I see multicast traffic, but no unicast traffic. However, if I run tcpdump on the ath interface I get sporadic traffic. It's possible I'm still misconfigured, but the fact that putting the interface into promiscuous mode changes the behavior of the interface kinda points elsewhere. We have this application running fine on 4521s with both an & wi radios. Is this a known problem? thanks, dave c From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 21:43:45 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79E4016A4BF for ; Sun, 7 Sep 2003 21:43:45 -0700 (PDT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB26E43FAF for ; Sun, 7 Sep 2003 21:43:44 -0700 (PDT) (envelope-from sam@errno.com) Received: from melange.errno.com (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h884gm17076203 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 7 Sep 2003 21:42:51 -0700 (PDT) (envelope-from sam@errno.com) Date: Sun, 07 Sep 2003 21:42:48 -0700 From: Sam Leffler To: David Cornejo , freebsd-mobile@freebsd.org Message-ID: <1224159918.1062970967@melange.errno.com> In-Reply-To: <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> References: <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> X-Mailer: Mulberry/3.0.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: atheros adhoc mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 04:43:45 -0000 > We're evaluating the Soekris 4801 and a 5212 based mini-PCI radio - It > works well enough in infrastructure mode, but I'm having problems with > adhoc. > > When the radio is operating in adhoc mode, I see multicast traffic, but > no unicast traffic. However, if I run tcpdump on the ath interface I get > sporadic traffic. > > It's possible I'm still misconfigured, but the fact that putting the > interface into promiscuous mode changes the behavior of the interface > kinda points elsewhere. We have this application running fine on 4521s > with both an & wi radios. > > Is this a known problem? No, but adhoc mode has not been well tested. 11a or 11b? What version of the software? Have you tried enabling debugging and packet dumping on the interface (ifconfig ath0 debug link2) to see what's happening? If you're getting multicast traffic but not unicast then it sounds like the BSSID isn't setup correctly--which was a very old bug. Sam From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 21:55:12 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7A3F16A4BF for ; Sun, 7 Sep 2003 21:55:12 -0700 (PDT) Received: from white.dogwood.com (white.dogwood.com [66.91.140.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB41E43FB1 for ; Sun, 7 Sep 2003 21:55:11 -0700 (PDT) (envelope-from dave@dogwood.com) Received: from keiki.dogwood.com (keiki.dogwood.com [192.168.231.101]) by white.dogwood.com (8.12.9/8.12.9) with ESMTP id h884t0Nn086967; Sun, 7 Sep 2003 18:55:01 -1000 (HST) (envelope-from dave@dogwood.com) Message-Id: <5.2.0.9.2.20030907184954.030eee98@white.dogwood.com> X-Sender: dave@white.dogwood.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sun, 07 Sep 2003 18:54:58 -1000 To: Sam Leffler , freebsd-mobile@freebsd.org From: David Cornejo In-Reply-To: <1224159918.1062970967@melange.errno.com> References: <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: atheros adhoc mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 04:55:12 -0000 This is from current built within the last week, I see the problem in both B & G mode and all other radios are B, haven't been able to try A yet. I haven't tried the debug yet, I'll try that. I did a search and I think I found the bug you mention, but couldn't find it was fixed. thanks! dave c At 09:42 PM 9/7/2003 -0700, Sam Leffler wrote: > > We're evaluating the Soekris 4801 and a 5212 based mini-PCI radio - It > > works well enough in infrastructure mode, but I'm having problems with > > adhoc. > > > > When the radio is operating in adhoc mode, I see multicast traffic, but > > no unicast traffic. However, if I run tcpdump on the ath interface I get > > sporadic traffic. > > > > It's possible I'm still misconfigured, but the fact that putting the > > interface into promiscuous mode changes the behavior of the interface > > kinda points elsewhere. We have this application running fine on 4521s > > with both an & wi radios. > > > > Is this a known problem? > >No, but adhoc mode has not been well tested. 11a or 11b? What version of >the software? Have you tried enabling debugging and packet dumping on the >interface (ifconfig ath0 debug link2) to see what's happening? > >If you're getting multicast traffic but not unicast then it sounds like the >BSSID isn't setup correctly--which was a very old bug. > > Sam From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 22:06:59 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B08D16A4BF for ; Sun, 7 Sep 2003 22:06:59 -0700 (PDT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id F355B43FDD for ; Sun, 7 Sep 2003 22:06:58 -0700 (PDT) (envelope-from sam@errno.com) Received: from melange.errno.com (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h8856c17076300 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 7 Sep 2003 22:06:44 -0700 (PDT) (envelope-from sam@errno.com) Date: Sun, 07 Sep 2003 22:06:36 -0700 From: Sam Leffler To: David Cornejo , freebsd-mobile@freebsd.org Message-ID: <1225587121.1062972394@melange.errno.com> In-Reply-To: <5.2.0.9.2.20030907184954.030eee98@white.dogwood.com> References: <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> <5.2.0.9.2.20030907184954.030eee98@white.dogwood.com> X-Mailer: Mulberry/3.0.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: atheros adhoc mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 05:06:59 -0000 > This is from current built within the last week, I see the problem in > both B & G mode and all other radios are B, haven't been able to try A > yet. > > I haven't tried the debug yet, I'll try that. > > I did a search and I think I found the bug you mention, but couldn't find > it was fixed. The fix should be in the HAL that's in the tree (just verified). Need more info please. At the very least try sending me config information. I've successfully used 5212-based cards and Prism-based cards in adhoc mode. Sam From owner-freebsd-mobile@FreeBSD.ORG Sun Sep 7 22:58:37 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 800BA16A4BF for ; Sun, 7 Sep 2003 22:58:37 -0700 (PDT) Received: from white.dogwood.com (white.dogwood.com [66.91.140.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id A39D743FE3 for ; Sun, 7 Sep 2003 22:58:36 -0700 (PDT) (envelope-from dave@dogwood.com) Received: from keiki.dogwood.com (keiki.dogwood.com [192.168.231.101]) by white.dogwood.com (8.12.9/8.12.9) with ESMTP id h885wDNn067128; Sun, 7 Sep 2003 19:58:22 -1000 (HST) (envelope-from dave@dogwood.com) Message-Id: <5.2.0.9.2.20030907194059.0315fce0@white.dogwood.com> X-Sender: dave@white.dogwood.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sun, 07 Sep 2003 19:58:11 -1000 To: Sam Leffler , freebsd-mobile@freebsd.org From: David Cornejo In-Reply-To: <1225587121.1062972394@melange.errno.com> References: <5.2.0.9.2.20030907184954.030eee98@white.dogwood.com> <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> <5.2.0.9.2.20030907184954.030eee98@white.dogwood.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: atheros adhoc mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 05:58:37 -0000 I'll get the debug output and the config tomorrow morning when I get into work. thanks for your help, dave c At 10:06 PM 9/7/2003 -0700, Sam Leffler wrote: > > This is from current built within the last week, I see the problem in > > both B & G mode and all other radios are B, haven't been able to try A > > yet. > > > > I haven't tried the debug yet, I'll try that. > > > > I did a search and I think I found the bug you mention, but couldn't find > > it was fixed. > >The fix should be in the HAL that's in the tree (just verified). Need more >info please. At the very least try sending me config information. I've >successfully used 5212-based cards and Prism-based cards in adhoc mode. > > Sam From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 8 08:39:06 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B85C16A4BF for ; Mon, 8 Sep 2003 08:39:06 -0700 (PDT) Received: from wanadoo.fr (ca-sqy-3-169.w80-8.abo.wanadoo.fr [80.8.56.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C68F43FE5 for ; Mon, 8 Sep 2003 08:39:02 -0700 (PDT) (envelope-from dak@wanadoo.fr) Received: from nebula.wanadoo.fr (localhost [127.0.0.1]) by wanadoo.fr (8.12.9/8.12.9) with ESMTP id h88Fc8Zk002863 for ; Mon, 8 Sep 2003 17:38:08 +0200 (CEST) (envelope-from dak@nebula.wanadoo.fr) Received: (from dak@localhost) by nebula.wanadoo.fr (8.12.9/8.12.9/Submit) id h88Fc8jK002862 for mobile@freebsd.org; Mon, 8 Sep 2003 17:38:08 +0200 (CEST) (envelope-from dak) Date: Mon, 8 Sep 2003 17:38:08 +0200 From: Aurelien Nephtali To: mobile@freebsd.org Message-ID: <20030908153808.GA2832@nebula.wanadoo.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: Mouse/ACPI probe problem ; console problem X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 15:39:06 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I've just bought a Compaq Presario 2157 and it works pretty well except the mouse. If the ACPI module is loaded, the mouse isn't probed ... otherwise, if the module isn't loaded, everything's ok. A boot -v with ACPI loaded just gives: psm0: unable to allocate IRQ Many people seem to have this problem on other laptops but each time, there is no fix/workaround :/ Another problem is the console, the screen's width is 30cm and the console's width is ... 19cm! Same problem with the height :/. I've read there is no fix under FreeBSD but it was on old posts, maybe ... ? :) I'm running a 5.1-CURRENT Anybody can help please ? -- Aurelien --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/XKJgDNsbHbt8ok8RAhNHAKCCNSpe8rcBF4PTfJqN/dBvkeY8jwCfaRFU hrTMyFBXy+oc+9l4fckTpBQ= =wXzY -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 8 12:15:19 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E46716A4BF for ; Mon, 8 Sep 2003 12:15:19 -0700 (PDT) Received: from cougar.it.wsu.edu (cougar.it.wsu.edu [134.121.1.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8674043FB1 for ; Mon, 8 Sep 2003 12:15:18 -0700 (PDT) (envelope-from rogerc@wsu.edu) Received: from ialc101.wsu.edu (ialc101.ip.wsu.edu [134.121.118.55]) by cougar.it.wsu.edu (8.12.9/8.12.9) with ESMTP id h88JFC9H170734 for ; Mon, 8 Sep 2003 12:15:12 -0700 (PDT) Message-Id: <5.2.1.1.0.20030908121438.0359c008@mail.wsu.edu> X-Sender: rogerc@mail.wsu.edu X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 08 Sep 2003 12:15:11 -0700 To: freebsd-mobile@freebsd.org From: Roger Crawford Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Spam-Status: No, hits=-0.9 required=6.0 tests=CARRIAGE_RETURNS,FROM_WSU,SPAM_PHRASE_00_01 version=2.43 X-Spam-Level: Subject: Touchpad under X: Fixed! X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 19:15:19 -0000 Changed the protocol from PS/2 to wsmouse. Fixed it. Thanks. From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 8 15:44:30 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20BC616A4BF for ; Mon, 8 Sep 2003 15:44:30 -0700 (PDT) Received: from www.ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2E1343FE0 for ; Mon, 8 Sep 2003 15:44:27 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.8p1/8.12.8) with ESMTP id h88MhcNj038768; Mon, 8 Sep 2003 15:43:38 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.8p1/8.12.8/Submit) id h88MhcGF038767; Mon, 8 Sep 2003 15:43:38 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200309082243.h88MhcGF038767@ambrisko.com> In-Reply-To: <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> To: David Cornejo Date: Mon, 8 Sep 2003 15:43:38 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: freebsd-mobile@freebsd.org Subject: Re: atheros adhoc mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 22:44:30 -0000 David Cornejo writes: | We're evaluating the Soekris 4801 and a 5212 based mini-PCI radio - It | works well enough in infrastructure mode, but I'm having problems with adhoc. | | When the radio is operating in adhoc mode, I see multicast traffic, but no | unicast traffic. However, if I run tcpdump on the ath interface I get | sporadic traffic. | | It's possible I'm still misconfigured, but the fact that putting the | interface into promiscuous mode changes the behavior of the interface kinda | points elsewhere. We have this application running fine on 4521s with both | an & wi radios. | | Is this a known problem? Heh, Dave how's it going? If by chance you are doing ad-hoc to an Aironet card I feel your pain. I have to go into promiscious mode to get the Atheros card to talk to my Aironet ad-hoc network. Even then it drops lots of packets. I'm not doing multicast. I haven't done any debugging. My Aironet cards work just fine it the same ad-hoc network. This is with a relatively recent -current. A week old or so. Doug A. From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 8 16:07:09 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E143516A4BF for ; Mon, 8 Sep 2003 16:07:09 -0700 (PDT) Received: from white.dogwood.com (white.dogwood.com [66.91.140.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB95743FE5 for ; Mon, 8 Sep 2003 16:07:07 -0700 (PDT) (envelope-from dave@dogwood.com) Received: from keiki.dogwood.com (bdsl.66.14.171.32.gte.net [66.14.171.32]) by white.dogwood.com (8.12.9/8.12.9) with SMTP id h88N5bNn018669; Mon, 8 Sep 2003 13:05:43 -1000 (HST) (envelope-from dave@dogwood.com) Message-Id: <5.2.0.9.2.20030908125955.029ac380@white.dogwood.com> X-Sender: dave@white.dogwood.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 08 Sep 2003 13:05:31 -1000 To: Doug Ambrisko From: David Cornejo In-Reply-To: <200309082243.h88MhcGF038767@ambrisko.com> References: <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-mobile@freebsd.org Subject: Re: atheros adhoc mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2003 23:07:10 -0000 At 03:43 PM 9/8/2003 -0700, Doug Ambrisko wrote: >David Cornejo writes: >| We're evaluating the Soekris 4801 and a 5212 based mini-PCI radio - It >| works well enough in infrastructure mode, but I'm having problems with >adhoc. >| >| When the radio is operating in adhoc mode, I see multicast traffic, but no >| unicast traffic. However, if I run tcpdump on the ath interface I get >| sporadic traffic. >| >| It's possible I'm still misconfigured, but the fact that putting the >| interface into promiscuous mode changes the behavior of the interface kinda >| points elsewhere. We have this application running fine on 4521s with both >| an & wi radios. >| >| Is this a known problem? > >Heh, Dave how's it going? If by chance you are doing ad-hoc to an >Aironet card I feel your pain. I have to go into promiscious mode >to get the Atheros card to talk to my Aironet ad-hoc network. Even >then it drops lots of packets. I'm not doing multicast. This is pretty much exactly what I'm seeing, except that I'm using Prism cards with the Atheros cards. I do have an Aironet network operating in the area though. >I haven't done any debugging. My Aironet cards work just fine it >the same ad-hoc network. Unfortunately, my app can't afford the Aironet cards, especially unfortunate with all I know about them. I'm trying to sanitize my config and get the debug stuff that Sam asked for last night and I'll post them ASAP. >This is with a relatively recent -current. A week old or so. > >Doug A. From owner-freebsd-mobile@FreeBSD.ORG Mon Sep 8 17:02:12 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96AE616A4BF for ; Mon, 8 Sep 2003 17:02:12 -0700 (PDT) Received: from white.dogwood.com (white.dogwood.com [66.91.140.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D0E143FF2 for ; Mon, 8 Sep 2003 17:02:11 -0700 (PDT) (envelope-from dave@dogwood.com) Received: from keiki.dogwood.com (bdsl.66.14.171.32.gte.net [66.14.171.32]) by white.dogwood.com (8.12.9/8.12.9) with SMTP id h8901pNn019120; Mon, 8 Sep 2003 14:01:55 -1000 (HST) (envelope-from dave@dogwood.com) Message-Id: <5.2.0.9.2.20030908132806.029c8088@white.dogwood.com> X-Sender: dave@white.dogwood.com X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Mon, 08 Sep 2003 14:01:48 -1000 To: Sam Leffler , freebsd-mobile@freebsd.org From: David Cornejo In-Reply-To: <1224159918.1062970967@melange.errno.com> References: <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> <5.2.0.9.2.20030907120108.03169860@mail.firetide.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: atheros adhoc mode X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2003 00:02:12 -0000 Ok, The kernel was built from CURRENT source checked out at about 17:00 HST on Aug 29 (03:00 Aug 30 GMT). The mirror I use can be as much as three hours delayed from what I see on the commit messages. I attempted to set the debug link2 as suggested and the link became too lossy for our code which then removes all routing through the ath card. I also get lots of "ath0: hardware error; resetting" errors with the debugging set. ifconfig from our ath0: ath0: flags=8a43 mtu 1500 inet 10.0.0.5 netmask 0xffffffff broadcast 10.0.0.5 inet6 fe80::202:6fff:fe20:2881%ath0 prefixlen 64 scopeid 0x4 ether 00:02:6f:20:28:81 media: IEEE 802.11 Wireless Ethernet autoselect status: associated ssid phop 1:phop channel 2 authmode OPEN powersavemode OFF powersavesleep 100 wepmode OFF weptxkey 1 All other cards in this case are wi. A snippet of the output from debug link2: (the hardware errors happen about 3-4 more frequently with this set) ath0: hardware error; resetting NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M 0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 8021 aaaa 0300 0000 0800 4500 0034 9206 0000 0111 3dac 0a00 0005 e000 0002 15b3 15b3 0020 0eb3 0101 fa00 0a4d 0047 0303 fa00 0a00 0059 c0a8 035a 0a4d 004b NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M 0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 9021 aaaa 0300 0000 0800 4500 0034 9506 0000 0111 3aac 0a00 0005 e000 0002 15b3 15b3 0020 0cb3 0101 fb00 0a4d 0047 0303 fb00 0a00 0059 c0a8 035a 0a4d 004b ath0: hardware error; resetting NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M 0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 a021 aaaa 0300 0000 0800 4500 0030 9806 0000 0111 37b0 0a00 0005 e000 0002 15b3 15b3 001c cebe 0100 fc00 0303 fc00 0a4d 0047 0a00 0059 0a4d 004b NODS 00:02:6f:04:2e:1c->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +40 0800 0000 0100 5e00 0002 0002 6f04 2e1c 0202 9f4e 8fd7 30dd aaaa 0300 0000 0800 4500 0024 d6ac 0000 0111 f8c1 0a00 0059 e000 0002 15b3 15b3 0010 3306 0101 ac00 0a00 0005 6ea7 954f NODS 00:02:6f:04:2e:1e->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +11 0800 0000 0100 5e00 0002 0002 6f04 2e1e 0202 9f4e 8fd7 d06a aaaa 0300 0000 0800 4500 0020 6920 0000 0111 6613 0a4d 004b e000 0002 15b3 15b3 000c 57d5 0100 9100 9847 3193 NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M 0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 b021 aaaa 0300 0000 0800 4500 0028 9b06 0000 0111 34b8 0a00 0005 e000 0002 15b3 15b3 0014 e1c1 0100 fd00 0301 fd00 0a4d 0047 ath0: hardware error; resetting NODS 00:02:6f:04:2e:37->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +34 0800 0000 0100 5e00 0002 0002 6f04 2e37 0202 9f4e 8fd7 109e aaaa 0300 0000 0800 4500 0024 9d97 0000 0111 319c 0a4d 0047 e000 0002 15b3 15b3 0010 bdcb 0101 2100 0a00 0005 731d bd04 NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M 0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 c021 aaaa 0300 0000 0800 4500 0028 9e06 0000 0111 31b8 0a00 0005 e000 0002 15b3 15b3 0014 dfc1 0100 fe00 0301 fe00 0a4d 0047 ath0: hardware error; resetting NODS 00:02:6f:04:2e:1c->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +23 0800 0000 0100 5e00 0002 0002 6f04 2e1c 0202 9f4e 8fd7 40df aaaa 0300 0000 0800 4500 0020 d6b5 0000 0111 f8bc 0a00 0059 e000 0002 15b3 15b3 000c 3a14 0100 af00 78fe b21a NODS 00:02:6f:04:2e:1e->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +11 0800 0000 0100 5e00 0002 0002 6f04 2e1e 0202 9f4e 8fd7 e06c aaaa 0300 0000 0800 4500 0030 6929 0000 0111 65fa 0a4d 004b e000 0002 15b3 15b3 001c 0e2e 0100 9400 2702 0000 0a4d 004b 0a4d 0047 0a00 0059 91a1 078d NODS 00:02:6f:04:2e:34->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 11M +33 0800 0000 0100 5e00 0002 0002 6f04 2e34 0202 9f4e 8fd7 e048 aaaa 0300 0000 0800 4500 0020 ebeb 0000 0111 29dd c0a8 035a e000 0002 15b3 15b3 000c ee6a 0100 4100 daab b093 NODS 00:02:6f:20:28:81->01:00:5e:00:00:02(02:02:9f:4e:8f:d7) data 1M 0800 0000 0100 5e00 0002 0002 6f20 2881 0202 9f4e 8fd7 d021 aaaa 0300 0000 0800 4500 0028 a106 0000 0111 2eb8 0a00 0005 e000 0002 15b3 15b3 0014 d564 0102 ff00 0a00 0059 0a4d 004b ath0: hardware error; resetting I don't have a kernel config available, but it's basically GENERIC with the following additions: options HZ=250 options CLK_USE_I8254_CALIBRATION options CONSPEED=19200 options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options MROUTING options NO_SWAPPING At 09:42 PM 9/7/2003 -0700, Sam Leffler wrote: > > We're evaluating the Soekris 4801 and a 5212 based mini-PCI radio - It > > works well enough in infrastructure mode, but I'm having problems with > > adhoc. > > > > When the radio is operating in adhoc mode, I see multicast traffic, but > > no unicast traffic. However, if I run tcpdump on the ath interface I get > > sporadic traffic. > > > > It's possible I'm still misconfigured, but the fact that putting the > > interface into promiscuous mode changes the behavior of the interface > > kinda points elsewhere. We have this application running fine on 4521s > > with both an & wi radios. > > > > Is this a known problem? > >No, but adhoc mode has not been well tested. 11a or 11b? What version of >the software? Have you tried enabling debugging and packet dumping on the >interface (ifconfig ath0 debug link2) to see what's happening? > >If you're getting multicast traffic but not unicast then it sounds like the >BSSID isn't setup correctly--which was a very old bug. > > 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 owner-freebsd-mobile@FreeBSD.ORG Mon Sep 8 21:29:25 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF60716A4BF for ; Mon, 8 Sep 2003 21:29:25 -0700 (PDT) Received: from col-msxproto1.col.missouri.edu (col-msxproto1.col.missouri.edu [128.206.3.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9563343F75 for ; Mon, 8 Sep 2003 21:29:23 -0700 (PDT) (envelope-from dbc63b@mizzou.edu) Received: from helium.bengal.missouri.edu ([128.206.12.182]) by col-msxproto1.col.missouri.edu over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6673); Mon, 8 Sep 2003 23:29:23 -0500 Date: Mon, 8 Sep 2003 23:29:22 -0500 (CDT) From: Dylan Cooper X-X-Sender: dbc63b@helium.bengal.missouri.edu To: freebsd-mobile@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 09 Sep 2003 04:29:23.0093 (UTC) FILETIME=[F1CEC450:01C3768A] Subject: 5.1-CURRENT / A31p / ACPI X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: dbc63b@mizzou.edu List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2003 04:29:25 -0000 Hello all, I've been following the mobile list for a while, now. I thought I would come out of lurk-mode and give some preliminary details about my Thinkpad A31p and my experiences with FreeBSD. First, a few notes: I've been a Linux user for Quite A While Now(tm). I'm most experienced with Debian and Gentoo (albeit less so), so while some of the FreeBSD environment is pretty new, others are relatively familiar (ports). The Unix Rosetta Stone (http://bhami.com/rosetta.html) has been pretty helpful with the transition. Overall, the *BSD method of upgrading a system makes more sense, and I think the wide variation between Linux distros and their configuration methods is what frustrated me the most. I haven't given up Debian for server use (familiarity), but I want to use FreeBSD for my personal systems. Quick guru question: Does FreeBSD have a /dev/nvram that can be polled as in Linux? I've looked around quite a bit before I asked what I feared to be an RTFM question, but haven't found an answer. There is an app called Thinkpad Buttons (tpb) that catches the hardware buttons along the left-hand side of the keyboard and provides functionality. The author of the program has documented the values well, and I tested it while running Debian on my A31p -they all worked. See: http://www.nongnu.org/tpb/ Anyway, on to the A31p. Summary: Installed 5.1-RELEASE (netinstall) and had the usual ACPI problems that have been posted on the list. I did the suggested APM config changes, and everything has been working ok. Because my laptop hasn't had to do real work yet (I toyed with a Debian install between the FreeBSD installs), I throught I would fool around with -CURRENT because I saw something about ACPI being somewhat fixed on another FreeBSD list. I installed from the latest snapshot from snapshots.jp.FreeBSD.org (05 Sept 2003) and did an AnonCVS pull last night (08 Sept 2003). I tweaked with the kernel config (a learning experience) and made both world and kernel. After booting up with ACPI enabled, it appears that there aren't any ACPI errors on my dmesg. Some ACPI events pop up an AE_NOT_FOUND error, but everything seems to be booting up cleanly. I'm currently tinkering around with X / Enlightenment 16.5. I haven't tested the functionality of all the peripherals, yet. I'll get to test the wireless card tomorrow at the university. Hardware: IBM Thinkpad A31p (2653-R9U) BIOS Embedded Controller: 1NHT04WW (20 Dec 2002) BIOS ver: 1NET11WW (04 Aug 2003) Various keys/events: ------------------- Lid switch acpi0: AcpiGetSleepTypeData failed - AE_NOT_FOUND It blanks the screen, but is trying to sleep and can't, I'm guessing. Power Button momentary press = nothing Fn-F3 (lcd off) Not working, no kernel message Fn-F4(sleep) acpi0: AcpiGetSleepTypeData failed - AE_NOT_FOUND Fn-F12(hyb) Not tried - Hybernation file not installed All other hardware Fn keys work: Keyboard light LCD bright/dim No problems switching between X and vtty When the screen blanks under X, it revives with no problems uname -a -------- FreeBSD pod 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Sep 8 18:39:39 CDT 2003 root@pod:/usr/obj/usr/src/sys/A31P i386 kernel config ------------ I can post a follow-up to keep this message from being too long. I'm certain that there are some intricacies I've missed due to n00b-isms. I compiled both apm and acpi in the kernel, even though it states that compiling ACPI in the kernel is depreciated. I supposed that doing so would allow me to flip back and forth via the hints files. A more experienced person could enlighten me, perhaps? Other additions: makeoptions DEBUG=-g options VESA options VESA_DEBUG device agp device radeondrm device apm device acpi options ACPI_DEBUG device.hints ------------ hint.acpi.0.disabled="0" hint.apm.0.disabled="1" loader.conf ----------- hw.pci.allow_unsupported_io_range=1 acpi_load="YES" dmesg ----- ACPI debug layer 0x0 debug level 0x0 Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.1-CURRENT #0: Mon Sep 8 18:39:39 CDT 2003 root@pod:/usr/obj/usr/src/sys/A31P Preloaded elf kernel "/boot/kernel/kernel" at 0xc0588000. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz (1998.32-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebf9ff real memory = 1073152000 (1023 MB) avail memory = 1036607488 (988 MB) Pentium Pro MTRR support enabled VESA: v2.0, 65472k memory, flags:0x1, mode table:0xc04f0b42 (1000022) VESA: ATI MOBILITY RADEON 7500 acpi0: on motherboard acpi_ec0: port 0x66,0x62 on acpi0 pcibios: BIOS version 2.10 Using $PIR table, 14 entries at 0xc00fdeb0 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib0: slot 29 INTA is routed to irq 11 pcib0: slot 29 INTB is routed to irq 11 pcib0: slot 29 INTC is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 pcib0: slot 31 INTB is routed to irq 11 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib1: slot 0 INTA is routed to irq 11 drm0: port 0x3000-0x30ff mem 0xd0100000-0xd010ffff,0xe8000000-0xefffffff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe0000000 64MB info: [drm] Initialized radeon 1.9.0 20020828 on minor 0 uhci0: port 0x1800-0x181f irq 11 at device 29.0 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1820-0x183f irq 11 at device 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 11 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib2: at device 30.0 on pci0 pci2: on pcib2 pcib2: slot 0 INTA is routed to irq 11 pcib2: slot 0 INTB is routed to irq 11 pcib2: slot 0 INTC is routed to irq 11 pcib2: slot 2 INTA is routed to irq 11 pcib2: slot 8 INTA is routed to irq 11 cbb0: mem 0x50000000-0x50000fff irq 11 at device 0.0 on pci2 start (50000000) < sc->membase (d0200000) start (50000000) < sc->pmembase (f0000000) cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [MPSAFE] cbb1: mem 0x50100000-0x50100fff irq 11 at device 0.1 on pci2 start (50100000) < sc->membase (d0200000) start (50100000) < sc->pmembase (f0000000) cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 cbb1: [MPSAFE] fwohci0: mem 0xd0201000-0xd02017ff irq 11 at device 0.2 on pci2 fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:06:1b:00:10:04:cb:1a fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) wi0: mem 0xf8000000-0xf8000fff irq 11 at device 2.0 on pci2 wi0: 802.11 address: 00:20:e0:4d:57:e3 wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.6) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps fxp0: port 0x8000-0x803f mem 0xd0200000-0xd0200fff irq 11 at device 8.0 on pci2 fxp0: Ethernet address 00:02:8a:a4:eb:7a miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1860-0x186f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: at device 31.3 (no driver attached) pci0: at device 31.5 (no driver attached) pci0: at device 31.6 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x3bc-0x3c3 irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_acad0: on acpi0 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface orm0: