From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 00:12:47 2004 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 18A7B16A4CE for ; Sun, 11 Jan 2004 00:12:47 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04BAA43D46 for ; Sun, 11 Jan 2004 00:12:46 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i0B8CU7E029799; Sun, 11 Jan 2004 00:12:34 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401110812.i0B8CU7E029799@gw.catspoiler.org> Date: Sun, 11 Jan 2004 00:12:30 -0800 (PST) From: Don Lewis To: imp@bsdimp.com In-Reply-To: <20040110.231459.102614269.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: mobile@FreeBSD.org Subject: Re: More power patches 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, 11 Jan 2004 08:12:47 -0000 On 10 Jan, M. Warner Losh wrote: > In message: <200401110326.i0B3Qg7E029449@gw.catspoiler.org> > Don Lewis writes: > : This is what I get with just the pci-subtractive patch. > > I'm having trouble reading this. There's a lot of garbage after Phy > 1394a line, but otherwise it looks good to my eye... I get similar looking binary garbage when I boot either an unpatched kernel or a kernel with your pci-subtractive patch. I don't know whether firewire is actually working because I don't have any firewire peripherals. I included this part the boot messages from the pci-subtractive case as a comparison to what I got when I booted a kernel built with power.20040107.diff. With the power patch both fwohci0 and fxp0 failed to properly attach. The boot messages below are where things seem to go wrong. > fwohci0: OHCI version 0.0 (ROM=0) > fwohci0: invalid OHCI version > fwohci0: FireWire init failed with err=6 > device_probe_and_attach: fwohci0 attach returned 5 > fxp0: could not setup irq > inphy0: detached > miibus0: detached > device_probe_and_attach: fxp0 attach returned 22 From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 01:15:58 2004 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 1747E16A4CE; Sun, 11 Jan 2004 01:15:58 -0800 (PST) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id B83C943D39; Sun, 11 Jan 2004 01:15:56 -0800 (PST) (envelope-from lorenzo@cisco.com) Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-3.cisco.com with ESMTP; 11 Jan 2004 01:18:01 +0000 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id i0B9FrQu002718; Sun, 11 Jan 2004 01:15:53 -0800 (PST) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id BAA13952; Sun, 11 Jan 2004 01:15:53 -0800 (PST) Date: Sun, 11 Jan 2004 01:15:53 -0800 From: Lorenzo Vicisano To: Marko Zec Message-ID: <20040111011553.A12385@cisco.com> References: <20040111003426.E0EF55D08@ptavv.es.net> <200401110229.46446.zec@tel.fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401110229.46446.zec@tel.fer.hr> User-Agent: Mutt/1.3.23i cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 11 Jan 2004 09:15:58 -0000 same result: the patch doesn't fix the problem. However after upgrding the Prism firmware (1.1.0 -> 1.1.1) the lock up stopped. Still I cannot get more that 2.5Mb/s Tx from the Prism (as a client) to another client (Aironet). A little better (3 / 3.5) from the Prism to the AP (DI 614+). "wi" is reporting a lot of TX collision, but "an" isn't when I change the direction of the traffic. In this case I get better rate.. but still not optimal as "wi" get conficts on the ACKs. Another anomaly shows up when running dhclient: often the system freezes/slows down for a few fractions of a second (BTW: I've noticed this with the Aironet driver as well). Also acquiring a lease has become more unreliable.. Lorenzo On Sun, Jan 11, 2004 at 02:29:46AM +0100, Marko Zec wrote: > On Sunday 11 January 2004 01:34, Kevin Oberman wrote: > > > > Marko, > > > > I just started re-building my kernel with this patch. I have > > previously reported this under CURRENT and hope that this might fix > > the problem. It has also been reported by several others under > > slightly different circumstances. I'll report what I see. It's pretty > > easy to test...just copy a multi-megabyte file from my laptop to my > > workstation over the wireless. > > > > Whoops... it seems that my hack doesn't fix the problem of outgoing > traffic hosing the wi interface - next time I'll do more testing before > making a post. However, without this patch my wi would lock up every > now and than out of the blue, regardless whether it was associated to > an AP or it was disconnected, and regardless whether there was any > traffic flowing through it or not. The same card (Prism 2.5 mini-PCI) > used to play nicely with 4.8-R, and works quite well with M$ also. > There must be something rotten in the recent wi driver... > > Cheers, > > Marko From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 04:44:28 2004 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 AE1C416A4CE for ; Sun, 11 Jan 2004 04:44:28 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C6D943D1F for ; Sun, 11 Jan 2004 04:44:26 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i0BCiJ7E030491 for ; Sun, 11 Jan 2004 04:44:23 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401111244.i0BCiJ7E030491@gw.catspoiler.org> Date: Sun, 11 Jan 2004 04:44:19 -0800 (PST) From: Don Lewis To: mobile@FreeBSD.org In-Reply-To: <200401110320.i0B3K37E029440@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Subject: Re: More power patches 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, 11 Jan 2004 12:44:28 -0000 With the http://people.freebsd.org/~imp/power.20040107.diff patch: On 10 Jan, Don Lewis wrote: > fwohci0: vendor=104c, dev=8026 > fwohci0: <1394 Open Host Controller Interface> mem 0xc0204000-0xc0207fff,0xc0209000-0xc02097ff irq 11 at device 7.0 on pci2 > fwohci0: Bus reserved 0x800 bytes for rid 0x10 type 3 at 0xc0209000 > fwohci0: OHCI version 0.0 (ROM=0) > fwohci0: invalid OHCI version > fwohci0: FireWire init failed with err=6 > device_probe_and_attach: fwohci0 attach returned 5 > fxp0: port 0x8400-0x843f mem 0xc0208000-0xc0208fff irq 11 at device 8.0 on pci2 > fxp0: Bus reserved 0x1000 bytes for rid 0x10 type 3 at 0xc0208000 > fxp0: Ethernet address 00:06:1b:d4:72:bb > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: could not setup irq > inphy0: detached > miibus0: detached > device_probe_and_attach: fxp0 attach returned 22 I spent some time debugging and tracked the fxp problem to the failure of the following test in ithread_add_handler(): if (!(ih->ih_flags & IH_FAST) && (temp_ih->ih_flags & IH_FAST)) goto fail; Apparently the failure of fwohci0 to attach somehow sets the IH_FLAG on irq 11, which is shared by both fwohci0 and fxp0, and a bunch of other stuff. If I remove firewire from my kernel config, this machine boots normally, and fxp0 is able to get its irq and talk to the net. > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x0 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc44b4047 > stack pointer = 0x10:0xd7411cec > frame pointer = 0x10:0xd7411d10 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 22 (irq11: fwohci0+) > kernel: type 12 trap, code=0 > Stopped at 0xc44b4047: addb %al,0(%eax) > db> tr > _end(c4362600,d7411d48,c085d977,315,0) at 0xc44b4047 > fork_exit(c062abc0,c4362600,d7411d48) at fork_exit+0xb4 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xd7411d7c, ebp = 0 --- If fwohci0 did not attach, why are we executing irq11: fwohci0+)? From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 10:18:57 2004 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 6685516A4CE for ; Sun, 11 Jan 2004 10:18:57 -0800 (PST) Received: from kogut3.o2.pl (kogut3.go2.pl [212.126.20.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFF5F43D49 for ; Sun, 11 Jan 2004 10:18:53 -0800 (PST) (envelope-from mzdyb@o2.pl) Received: from kmz (152-mo3-2.acn.waw.pl [62.121.105.152]) by kogut3.o2.pl (Postfix) with ESMTP id B765277DB6 for ; Sun, 11 Jan 2004 19:18:47 +0100 (CET) Message-ID: <003801c3d86f$a3953520$9869793e@kmz> From: "mzdyb" To: References: <004601c3d7c8$0b658720$9869793e@kmz> <20040110.173047.123637134.imp@bsdimp.com> Date: Sun, 11 Jan 2004 19:20:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: Re: hostap doesn't work 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, 11 Jan 2004 18:18:57 -0000 > Try > ifconfig wi0 ssid my_ap media DS/11Mbps mediaopt hostap > > Warner i've tried all possible syntax combinations. google told me that few other people have this problem with hostap mode too. but i cannot find solution :( michal From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 10:45:48 2004 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 A599716A4CE; Sun, 11 Jan 2004 10:45:48 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BFE443D41; Sun, 11 Jan 2004 10:45:47 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0BIjkET040475; Sun, 11 Jan 2004 11:45:46 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 11 Jan 2004 11:45:22 -0700 (MST) Message-Id: <20040111.114522.54143398.imp@bsdimp.com> To: truckman@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200401110812.i0B8CU7E029799@gw.catspoiler.org> References: <20040110.231459.102614269.imp@bsdimp.com> <200401110812.i0B8CU7E029799@gw.catspoiler.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: mobile@FreeBSD.org Subject: Re: More power patches 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, 11 Jan 2004 18:45:48 -0000 In message: <200401110812.i0B8CU7E029799@gw.catspoiler.org> Don Lewis writes: : With the power patch both : fwohci0 and fxp0 failed to properly attach. The boot messages below are : where things seem to go wrong. : : > fwohci0: OHCI version 0.0 (ROM=0) : > fwohci0: invalid OHCI version : > fwohci0: FireWire init failed with err=6 : > device_probe_and_attach: fwohci0 attach returned 5 : : > fxp0: could not setup irq : > inphy0: detached : > miibus0: detached : > device_probe_and_attach: fxp0 attach returned 22 Yea, I think I have alignment issues. The rman_* functions will allocate N bytes with an alignment of < N. I don't know if this is a bug or a feature. I'm leaning towards 'bug' Warner From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 11:58:56 2004 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 A75B716A4CE for ; Sun, 11 Jan 2004 11:58:56 -0800 (PST) Received: from cwnet5.wirelessnet.de (cwnet5.wirelessnet.de [212.20.170.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A34843D46 for ; Sun, 11 Jan 2004 11:58:54 -0800 (PST) (envelope-from usenet@esct.org) Received: from baldur.asgard (pd9ec2628.dip.t-dialin.net [217.236.38.40]) by cwnet5.wirelessnet.de (Postfix) with ESMTP id E04A11E998 for ; Sun, 11 Jan 2004 20:59:50 +0100 (CET) Received: by baldur.asgard (Postfix, from userid 1001) id 16E52552; Sun, 11 Jan 2004 20:58:50 +0100 (CET) Date: Sun, 11 Jan 2004 20:58:50 +0100 From: Andreas Totlis To: freebsd-mobile@freebsd.org Message-ID: <20040111195849.GP19309@baldur.asgard> Mail-Followup-To: freebsd-mobile@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: T40p - good choice for running FBSD? 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, 11 Jan 2004 19:58:56 -0000 Hi, I've look at a new laptop and the IBM T40p looks like nice. After searching in this list, many employees favorite the IBM brand. Is there any reason why I don't buy a T40p(any experience aside from Lukas Ertl's laptop list)? It looks like the same as T40. How contented the T40p owner? Normally I run -stable of my maschine, is it a better choice to install 5.1(when is 5.2 -stable out)? All sentences, notices, links and informations are welcome! Regards, Andreas From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 13:24:37 2004 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 7930E16A4CE; Sun, 11 Jan 2004 13:24:37 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B278043D1D; Sun, 11 Jan 2004 13:24:35 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0BLOXET042436; Sun, 11 Jan 2004 14:24:34 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 11 Jan 2004 14:23:57 -0700 (MST) Message-Id: <20040111.142357.50578253.imp@bsdimp.com> To: lorenzo@vicisano.net From: "M. Warner Losh" In-Reply-To: <20040111011553.A12385@cisco.com> References: <20040111003426.E0EF55D08@ptavv.es.net> <200401110229.46446.zec@tel.fer.hr> <20040111011553.A12385@cisco.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 11 Jan 2004 21:24:37 -0000 In message: <20040111011553.A12385@cisco.com> Lorenzo Vicisano writes: : However after upgrding the Prism firmware (1.1.0 -> 1.1.1) : the lock up stopped. You really really really want to be using 1.4.5 firmware. Older firmware is known to be buggy. Warner From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 14:00:51 2004 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 D68D316A4CE for ; Sun, 11 Jan 2004 14:00:51 -0800 (PST) Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA1F343D4C for ; Sun, 11 Jan 2004 14:00:50 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 1Afnda-0000zI-00 for freebsd-mobile@freebsd.org; Sun, 11 Jan 2004 17:00:50 -0500 Date: Sun, 11 Jan 2004 17:00:50 -0500 From: Peter Radcliffe To: freebsd-mobile@freebsd.org Message-ID: <20040111220050.GA839@pir.net> Mail-Followup-To: freebsd-mobile@freebsd.org References: <20040111003426.E0EF55D08@ptavv.es.net> <200401110229.46446.zec@tel.fer.hr> <20040111011553.A12385@cisco.com> <20040111.142357.50578253.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040111.142357.50578253.imp@bsdimp.com> User-Agent: Mutt/1.4.1i X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Subject: Re: prism 2.5 timeout in wi_cmd 0x010b X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-mobile@freebsd.org List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2004 22:00:52 -0000 "M. Warner Losh" probably said: > You really really really want to be using 1.4.5 firmware. Older > firmware is known to be buggy. I've got newer firmware but no way to actually upgrade it. IBM doesn;t supply a meanthod to upgrade to anythig newer than I have installed... Got an installer ? P. -- pir From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 14:55:43 2004 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 21B2116A4CE; Sun, 11 Jan 2004 14:55:43 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEE4B43D5D; Sun, 11 Jan 2004 14:55:41 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0BMtfET043427; Sun, 11 Jan 2004 15:55:41 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 11 Jan 2004 15:55:00 -0700 (MST) Message-Id: <20040111.155500.121671029.imp@bsdimp.com> To: nork@freebsd.org From: "M. Warner Losh" In-Reply-To: <20040110.140024.12639654.imp@bsdimp.com> References: <20040107.171023.63338658.imp@bsdimp.com> <20040110093526.13ec4aa5.nork@FreeBSD.org> <20040110.140024.12639654.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: mobile@freebsd.org Subject: Re: More power patches 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, 11 Jan 2004 22:55:43 -0000 In message: <20040110.140024.12639654.imp@bsdimp.com> "M. Warner Losh" writes: : In message: <20040110093526.13ec4aa5.nork@FreeBSD.org> : Norikatsu Shigemura writes: : : cbb1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xe0203d00 : ^^^^^^^ ^^^^^^^^^^ : This is the problem. Notice the alignment of the resource allocated. : This is bogus. I think I have a fix for this, and hope to get an updated patch out... Warner From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 15:21:01 2004 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 0F37716A4CE; Sun, 11 Jan 2004 15:21:01 -0800 (PST) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38F6E43D1F; Sun, 11 Jan 2004 15:20:45 -0800 (PST) (envelope-from lorenzo@cisco.com) Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id i0BNKfQu006697; Sun, 11 Jan 2004 15:20:41 -0800 (PST) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id PAA17074; Sun, 11 Jan 2004 15:20:41 -0800 (PST) Date: Sun, 11 Jan 2004 15:20:40 -0800 From: Lorenzo Vicisano To: "M. Warner Losh" Message-ID: <20040111152040.A16863@cisco.com> References: <20040111003426.E0EF55D08@ptavv.es.net> <200401110229.46446.zec@tel.fer.hr> <20040111011553.A12385@cisco.com> <20040111.142357.50578253.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040111.142357.50578253.imp@bsdimp.com> User-Agent: Mutt/1.3.23i cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 11 Jan 2004 23:21:01 -0000 Warner, On Sun, Jan 11, 2004 at 02:23:57PM -0700, M. Warner Losh wrote: > In message: <20040111011553.A12385@cisco.com> > Lorenzo Vicisano writes: > : However after upgrding the Prism firmware (1.1.0 -> 1.1.1) > : the lock up stopped. > > You really really really want to be using 1.4.5 firmware. Older > firmware is known to be buggy. I was referring to the "primary", as for the "station" I went from 1.4.2 to 1.7.4 .. but does the "station" firmware affect the functionality as a "client" anyways ? Lorenzo From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 15:34:06 2004 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 8CD4A16A4CE; Sun, 11 Jan 2004 15:34:06 -0800 (PST) Received: from mail.tel.fer.hr (zg04-053.dialin.iskon.hr [213.191.137.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD02443D46; Sun, 11 Jan 2004 15:33:56 -0800 (PST) (envelope-from zec@tel.fer.hr) Received: from 192.168.200.114 (marko@dhcp14.katoda.net [192.168.200.114]) by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id i0BNTUi3012101; Mon, 12 Jan 2004 00:29:50 +0100 (CET) (envelope-from zec@tel.fer.hr) From: Marko Zec To: Lorenzo Vicisano Date: Sun, 11 Jan 2004 18:53:04 +0100 User-Agent: KMail/1.5.4 References: <20040111003426.E0EF55D08@ptavv.es.net> <200401110229.46446.zec@tel.fer.hr> <20040111011553.A12385@cisco.com> In-Reply-To: <20040111011553.A12385@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401111853.04005.zec@tel.fer.hr> cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 11 Jan 2004 23:34:06 -0000 On Sunday 11 January 2004 10:15, Lorenzo Vicisano wrote: > same result: the patch doesn't fix the problem. > > However after upgrding the Prism firmware (1.1.0 -> 1.1.1) > the lock up stopped. > > Still I cannot get more that 2.5Mb/s Tx from the Prism (as a client) > to another client (Aironet). A little better (3 / 3.5) from the Prism > to the AP (DI 614+). I'd say that 2.5 Mb/s can be considered a pretty good throughput between two client nodes in an infrastructure-mode environment. Have in mind that the AP operates as a relay in such a case, so each frame has to be "on air" twice. Marko From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 15:34:07 2004 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 9C86116A4CE for ; Sun, 11 Jan 2004 15:34:07 -0800 (PST) Received: from mail.tel.fer.hr (zg04-053.dialin.iskon.hr [213.191.137.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E662443D48 for ; Sun, 11 Jan 2004 15:33:56 -0800 (PST) (envelope-from zec@tel.fer.hr) Received: from 192.168.200.114 (marko@dhcp14.katoda.net [192.168.200.114]) by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id i0BNTUi5012101; Mon, 12 Jan 2004 00:30:39 +0100 (CET) (envelope-from zec@tel.fer.hr) From: Marko Zec To: "Kevin Oberman" , freebsd-mobile@freebsd.org Date: Sun, 11 Jan 2004 18:43:26 +0100 User-Agent: KMail/1.5.4 References: <20040111031605.0097B5D04@ptavv.es.net> In-Reply-To: <20040111031605.0097B5D04@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401111843.26320.zec@tel.fer.hr> Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 11 Jan 2004 23:34:07 -0000 On Sunday 11 January 2004 04:16, Kevin Oberman wrote: > > > I'll report what I see. It's pretty easy to test...just copy a > > > multi-megabyte file from my laptop to my workstation over the > > > wireless. > > > > I've been seeing and reporting that problem too, for a while now. > > It worked for me! I just copied 850 MB of data at an average transfer > rate of 4.3 Mb/s with no problems. I never came close to this in the > past. I hope Warner can comment on it (and commit it if he does not > see a problem!) wi0: mem 0xf8000000-0xf8000fff irq 6 at device 2.0 on pci1 wi0: 802.11 address: 00:05:3c:06:9d:1d wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary 1.01.01, Station 1.07.04 After upgrading the firmware to 1.7.4, the problem is now gone for me as well! However, with my hack the throughput is slightly better (430 KB/s vs 350 KB/s without the hack), it seems that without the hack the card still loses some frames every now and than, yet it doesn't completely lock up as it would with 1.4.9 firmware. Nevertheless, IMO my patch should never be committed, since it was just an empirical experiment, and it is still completely unclear what was the real cause of those intermittent lockups. It would be nice if more knowledgeable people could dig slightly deeper into this... The moral of the story seems to be that firmware 1.4.9 probably shouldn't be used on mini-PCI Prism cards with current FreeBSD drivers. Cheers, Marko From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 15:35:14 2004 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 3C6F116A4CE; Sun, 11 Jan 2004 15:35:14 -0800 (PST) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5171743D31; Sun, 11 Jan 2004 15:35:13 -0800 (PST) (envelope-from lorenzo@cisco.com) Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 11 Jan 2004 15:37:24 +0000 Received: from cisco.com (cypher.cisco.com [171.69.11.143]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0BNZAVM004705; Sun, 11 Jan 2004 15:35:11 -0800 (PST) Received: (from lorenzo@localhost) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) id PAA18010; Sun, 11 Jan 2004 15:35:10 -0800 (PST) Date: Sun, 11 Jan 2004 15:35:10 -0800 From: Lorenzo Vicisano To: Peter Radcliffe Message-ID: <20040111153510.B16863@cisco.com> References: <20040111003426.E0EF55D08@ptavv.es.net> <200401110229.46446.zec@tel.fer.hr> <20040111011553.A12385@cisco.com> <20040111.142357.50578253.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040111.142357.50578253.imp@bsdimp.com> User-Agent: Mutt/1.3.23i cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 11 Jan 2004 23:35:14 -0000 > I've got newer firmware but no way to actually upgrade it. IBM doesn;t > supply a meanthod to upgrade to anythig newer than I have installed... > > Got an installer ? I used the windoze installer and info from http://linux.junsun.net/intersil-prism/index.html Lorenzo From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 15:42:02 2004 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 EAC5C16A4D0; Sun, 11 Jan 2004 15:42:02 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EC5C43DA6; Sun, 11 Jan 2004 15:41:22 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0BNf0ET044005; Sun, 11 Jan 2004 16:41:00 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 11 Jan 2004 16:40:56 -0700 (MST) Message-Id: <20040111.164056.56440437.imp@bsdimp.com> To: lorenzo@vicisano.net From: "M. Warner Losh" In-Reply-To: <20040111152040.A16863@cisco.com> References: <20040111011553.A12385@cisco.com> <20040111.142357.50578253.imp@bsdimp.com> <20040111152040.A16863@cisco.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 11 Jan 2004 23:42:03 -0000 In message: <20040111152040.A16863@cisco.com> Lorenzo Vicisano writes: : Warner, : : On Sun, Jan 11, 2004 at 02:23:57PM -0700, M. Warner Losh wrote: : > In message: <20040111011553.A12385@cisco.com> : > Lorenzo Vicisano writes: : > : However after upgrding the Prism firmware (1.1.0 -> 1.1.1) : > : the lock up stopped. : > : > You really really really want to be using 1.4.5 firmware. Older : > firmware is known to be buggy. : : I was referring to the "primary", as for the "station" : I went from 1.4.2 to 1.7.4 .. but does the "station" : firmware affect the functionality as a "client" anyways ? Yes. It does. I've had reports of problems with newer versions of the firmware... I've been too swamped to try it out. The newer versions implement AP to AP junk, as well as WPA enhancements... Warner From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 15:43:55 2004 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 B213E16A4CE; Sun, 11 Jan 2004 15:43:55 -0800 (PST) Received: from mail.tel.fer.hr (zg04-053.dialin.iskon.hr [213.191.137.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4BD643D31; Sun, 11 Jan 2004 15:43:52 -0800 (PST) (envelope-from zec@tel.fer.hr) Received: from 192.168.200.114 (marko@dhcp14.katoda.net [192.168.200.114]) by mail.tel.fer.hr (8.12.6/8.12.6) with ESMTP id i0BNgKi3012106; Mon, 12 Jan 2004 00:42:40 +0100 (CET) (envelope-from zec@tel.fer.hr) From: Marko Zec To: freebsd-mobile@freebsd.org, Peter Radcliffe Date: Mon, 12 Jan 2004 00:42:50 +0100 User-Agent: KMail/1.5.4 References: <20040111003426.E0EF55D08@ptavv.es.net> <20040111.142357.50578253.imp@bsdimp.com> <20040111220050.GA839@pir.net> In-Reply-To: <20040111220050.GA839@pir.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401120042.50744.zec@tel.fer.hr> cc: freebsd-net@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 11 Jan 2004 23:43:55 -0000 On Sunday 11 January 2004 23:00, Peter Radcliffe wrote: > "M. Warner Losh" probably said: > > You really really really want to be using 1.4.5 firmware. Older > > firmware is known to be buggy. > > I've got newer firmware but no way to actually upgrade it. IBM > doesn;t supply a meanthod to upgrade to anythig newer than I have > installed... > > Got an installer ? On my Prism 2.5 mini-PCI card I managed to upgrade the firmware to 1.1.1 / 1.7.4 using the utilities found here: http://linux.junsun.net/intersil-prism/ First of all, you'll have to boot a M$ OS and install the winupdate utility. Next, in the NIC driver disable the "firmware download" option, as it temporarily loads a new firmware in the NIC RAM, which seems to prevent firmware updates to flash to succeed. You'll have to shut down the machine in order to force a full reset of the NIC. I was kind of paranosic in choosing the appropriate primary / station code, but have latter learned that the "winupdate" utility was smart enough to prevent me from flashing the card with an unappropriate code. Good luck, Marko From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 16:02:33 2004 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 91C1216A4CE; Sun, 11 Jan 2004 16:02:33 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C85EF43D49; Sun, 11 Jan 2004 16:02:30 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i0C02F7E031685; Sun, 11 Jan 2004 16:02:19 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401120002.i0C02F7E031685@gw.catspoiler.org> Date: Sun, 11 Jan 2004 16:02:15 -0800 (PST) From: Don Lewis To: imp@bsdimp.com In-Reply-To: <20040111.155500.121671029.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: nork@FreeBSD.org cc: mobile@FreeBSD.org Subject: Re: More power patches 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, 12 Jan 2004 00:02:33 -0000 On 11 Jan, M. Warner Losh wrote: > In message: <20040110.140024.12639654.imp@bsdimp.com> > "M. Warner Losh" writes: > : In message: <20040110093526.13ec4aa5.nork@FreeBSD.org> > : Norikatsu Shigemura writes: > : : cbb1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xe0203d00 > : ^^^^^^^ ^^^^^^^^^^ > : This is the problem. Notice the alignment of the resource allocated. > : This is bogus. > > I think I have a fix for this, and hope to get an updated patch out... That doesn't appear to be the cause of the breakage I'm seeing ... > fwohci0: <1394 Open Host Controller Interface> mem 0xc0204000-0xc0207fff,0xc0209000-0xc02097ff irq 11 at device 7.0 on pci2 > fwohci0: Bus reserved 0x800 bytes for rid 0x10 type 3 at 0xc0209000 Hmn, maybe that is the problem. I just took a closer look and earlier in the boot I see: > cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xc0209800 I bet cbb0 thinks that it is at 0xc0209000, which might interfere with fwohci0. There is still the issue of the irq breakage caused by the attach failure. From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 16:03:19 2004 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 CA3D016A503; Sun, 11 Jan 2004 16:03:19 -0800 (PST) Received: from postal1.es.net (proxy.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id E08D043D3F; Sun, 11 Jan 2004 16:03:09 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Sun, 11 Jan 2004 16:03:08 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 03D445D08; Sun, 11 Jan 2004 16:03:08 -0800 (PST) To: Lorenzo Vicisano In-Reply-To: Message from Lorenzo Vicisano of "Sun, 11 Jan 2004 01:15:53 PST." <20040111011553.A12385@cisco.com> Date: Sun, 11 Jan 2004 16:03:08 -0800 From: "Kevin Oberman" Message-Id: <20040112000308.03D445D08@ptavv.es.net> cc: freebsd-net@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: prism 2.5 timeout in wi_cmd 0x010b 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, 12 Jan 2004 00:03:19 -0000 > Date: Sun, 11 Jan 2004 01:15:53 -0800 > From: Lorenzo Vicisano > > same result: the patch doesn't fix the problem. > > However after upgrding the Prism firmware (1.1.0 -> 1.1.1) > the lock up stopped. > > Still I cannot get more that 2.5Mb/s Tx from the Prism (as a client) > to another client (Aironet). A little better (3 / 3.5) from the Prism > to the AP (DI 614+). > > "wi" is reporting a lot of TX collision, but "an" isn't when I change > the direction of the traffic. In this case I get better rate.. but > still not optimal as "wi" get conficts on the ACKs. > > Another anomaly shows up when running dhclient: often the system > freezes/slows down for a few fractions of a second (BTW: I've noticed > this with the Aironet driver as well). Also acquiring a lease > has become more unreliable.. Odd. I have 1.1.0/1.4.9 firmware on my card and it works like a champ with Marko's patch. I was not aware that newer firmware was available. Guess I need to go look for the new firmware. I saw much better performance than this on my system. I moved over 850 MB of data at an average of 531 MB/sec and a peak of 622 MB/sec. That translates to a peak over 5 Mb/s and an average of over 4.3 Mb/s. This was with scp. With ttcp I see transmit speed of 4.1 Mb/s but a receive speed of only 1.3 Mb/s. This is to an AP. The problems seemed to start for me after the upgrade to 1.4.9 so maybe the latest will get things back to normal. I don't often use dhclient, but I have seen no problems when I do. (I use Lars Eggert's location.sh to set up my network for my "normal" wireless access.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 16:26:42 2004 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 F3FD516A4CE; Sun, 11 Jan 2004 16:26:41 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96B9243D2D; Sun, 11 Jan 2004 16:26:40 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0C0QeET044702; Sun, 11 Jan 2004 17:26:40 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 11 Jan 2004 17:26:27 -0700 (MST) Message-Id: <20040111.172627.84647422.imp@bsdimp.com> To: truckman@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <200401120002.i0C02F7E031685@gw.catspoiler.org> References: <20040111.155500.121671029.imp@bsdimp.com> <200401120002.i0C02F7E031685@gw.catspoiler.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: nork@FreeBSD.org cc: mobile@FreeBSD.org Subject: Re: More power patches 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, 12 Jan 2004 00:26:42 -0000 In message: <200401120002.i0C02F7E031685@gw.catspoiler.org> Don Lewis writes: : On 11 Jan, M. Warner Losh wrote: : > In message: <20040110.140024.12639654.imp@bsdimp.com> : > "M. Warner Losh" writes: : > : In message: <20040110093526.13ec4aa5.nork@FreeBSD.org> : > : Norikatsu Shigemura writes: : > : : cbb1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xe0203d00 : > : ^^^^^^^ ^^^^^^^^^^ : > : This is the problem. Notice the alignment of the resource allocated. : > : This is bogus. : > : > I think I have a fix for this, and hope to get an updated patch out... : : That doesn't appear to be the cause of the breakage I'm seeing ... : : > fwohci0: <1394 Open Host Controller Interface> mem 0xc0204000-0xc0207fff,0xc0209000-0xc02097ff irq 11 at device 7.0 on pci2 : > fwohci0: Bus reserved 0x800 bytes for rid 0x10 type 3 at 0xc0209000 : : Hmn, maybe that is the problem. I just took a closer look and earlier : in the boot I see: : : > cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xc0209800 : : I bet cbb0 thinks that it is at 0xc0209000, which might interfere with : fwohci0. Yes. That would, since both of them are trying to decode 0xc0209000. : There is still the issue of the irq breakage caused by the attach : failure. I don't understand that one at all.. Unless it is a failure message is a cut-n-pasto or something weird is happening. Warner From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 17:09:25 2004 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 66B5716A4CE for ; Sun, 11 Jan 2004 17:09:25 -0800 (PST) Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2748743D1F for ; Sun, 11 Jan 2004 17:09:24 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 1Afqa3-0002JG-00 for freebsd-mobile@freebsd.org; Sun, 11 Jan 2004 20:09:23 -0500 Date: Sun, 11 Jan 2004 20:09:23 -0500 From: Peter Radcliffe To: freebsd-mobile@freebsd.org Message-ID: <20040112010923.GA8718@pir.net> Mail-Followup-To: freebsd-mobile@freebsd.org References: <20040111003426.E0EF55D08@ptavv.es.net> <20040111.142357.50578253.imp@bsdimp.com> <20040111220050.GA839@pir.net> <200401120042.50744.zec@tel.fer.hr> <20040111003426.E0EF55D08@ptavv.es.net> <200401110229.46446.zec@tel.fer.hr> <20040111011553.A12385@cisco.com> <20040111.142357.50578253.imp@bsdimp.com> <20040111153510.B16863@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200401120042.50744.zec@tel.fer.hr> <20040111153510.B16863@cisco.com> User-Agent: Mutt/1.4.1i X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Subject: Re: prism 2.5 timeout in wi_cmd 0x010b X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-mobile@freebsd.org List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2004 01:09:25 -0000 Lorenzo Vicisano probably said: > I used the windoze installer and info from > http://linux.junsun.net/intersil-prism/index.html Marko Zec probably said: > On my Prism 2.5 mini-PCI card I managed to upgrade the firmware to > 1.1.1 / 1.7.4 using the utilities found here: > > http://linux.junsun.net/intersil-prism/ Thanks for the pointer, guys. I got my minipci card upgraded fine; wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary 1.01.01, Station 1.07.04 Ta, P. -- pir From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 18:33:17 2004 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 8C13C16A4D0 for ; Sun, 11 Jan 2004 18:33:17 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6BC643D46 for ; Sun, 11 Jan 2004 18:32:51 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com) by ran.psg.com with esmtp (Exim 4.24; FreeBSD) id 1Afrso-000MRf-3n; Sun, 11 Jan 2004 18:32:50 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andreas Totlis References: <20040111195849.GP19309@baldur.asgard> Message-Id: Date: Sun, 11 Jan 2004 18:32:50 -0800 cc: freebsd-mobile@freebsd.org Subject: Re: T40p - good choice for running FBSD? 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, 12 Jan 2004 02:33:17 -0000 i have a t40p. the big problem is resume locks up the box with an ata error. oh, and then there is the problem of screen staying blank and having to do teh vty hack to get it back. but you can get it back from that, unlike the resuyme lock up. otherwise ok with X, gnome, ... in stable and current. randy From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 19:15:29 2004 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 5031116A4CE for ; Sun, 11 Jan 2004 19:15:29 -0800 (PST) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44BE443D1F for ; Sun, 11 Jan 2004 19:15:28 -0800 (PST) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i0C3FE7E032034; Sun, 11 Jan 2004 19:15:18 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200401120315.i0C3FE7E032034@gw.catspoiler.org> Date: Sun, 11 Jan 2004 19:15:14 -0800 (PST) From: Don Lewis To: imp@bsdimp.com In-Reply-To: <20040111.172627.84647422.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: mobile@FreeBSD.org Subject: Re: More power patches 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, 12 Jan 2004 03:15:29 -0000 On 11 Jan, M. Warner Losh wrote: > In message: <200401120002.i0C02F7E031685@gw.catspoiler.org> > Don Lewis writes: > : There is still the issue of the irq breakage caused by the attach > : failure. > > I don't understand that one at all.. Unless it is a failure message > is a cut-n-pasto or something weird is happening. There is something wierd happening. The problem appears to be in ithread_remove_handler() or ithread_loop(). ithread_remove_handler() is executing the if (!TD_AWAITING_INTR(ithread->it_td)) { condition and setting the IH_DEAD flag. If this flag is set, ithread_remove_handler() should msleep() to wait for the thread to do the removal. The problem is that ithread_remove_handler() doesn't appear to sleep for any significant amount of time, and ithread_loop() never seems to execute the the block of code that detects IH_DEAD and executes TAILQ_REMOVE(). When ithread_remove_handler() calls ithread_update() after the msleep() call, ithread_update() is still finding the handler on the list, and then ithread_remove_handler() proceeds to free the handler back to the heap where it is undoubtably getting stomped on and causing havoc later on. Is there a problem with calling msleep() this early in the boot sequence? From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 11 23:06:41 2004 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 D0BF016A4CE for ; Sun, 11 Jan 2004 23:06:41 -0800 (PST) Received: from web40808.mail.yahoo.com (web40808.mail.yahoo.com [66.218.78.185]) by mx1.FreeBSD.org (Postfix) with SMTP id 1716643D3F for ; Sun, 11 Jan 2004 23:06:41 -0800 (PST) (envelope-from rhythin@yahoo.com) Message-ID: <20040112070640.87077.qmail@web40808.mail.yahoo.com> Received: from [142.103.39.12] by web40808.mail.yahoo.com via HTTP; Sun, 11 Jan 2004 23:06:40 PST Date: Sun, 11 Jan 2004 23:06:40 -0800 (PST) From: Rui Li To: freebsd-mobile@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: PCCARD unrecogonized by FreeBSD 5.1-RELEASE on IBM Thinkpad 600 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, 12 Jan 2004 07:06:41 -0000 I just installed FreeBSD 5.1-RELEASE (root@wv1u.btc.adaptec.com:/usr/obj/user/src/sys/GENERIC i386) on my old IBM Thinkpad 600. The system can't see any pccard. I found this in the dmesg after I added 'hw.pccard.cis_debug="1", hw.pci.allow_unsupported_io_range="1", hw.cbb.start_memory="0x20000000"' as suggested by some posting here: cbb0: mem 0x21301000-0x2130fff at device 2.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12cbb0: mem 0x21301000-0x2130fff at device 2.1 on pci0 cardbus1: on cbb0 pccard1: <16-bit PCCard bus> on cbb0 cbb: Unable to map IRQ... device_probe_and_attach: cbb0 attach returned 12 And when I run pccardd I got this error: "pccardd[659]: fatal error: no PC_CARD slots". Any suggestion? __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 07:49:01 2004 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 9414816A4CE for ; Mon, 12 Jan 2004 07:49:01 -0800 (PST) Received: from indicium.fit.edu (indicium.fit.edu [163.118.131.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4849643D41 for ; Mon, 12 Jan 2004 07:48:58 -0800 (PST) (envelope-from rresnick@fit.edu) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 12 Jan 2004 10:48:56 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Sony PCG-R505DL success running 5.1-release Thread-Index: AcPZI1bjnQV1nlErQBaE8bIefbWNQgAACNdQ From: "Rhian B. Resnick" To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Sony PCG-R505DL success running 5.1-release 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, 12 Jan 2004 15:49:01 -0000 I'm new to posting to the lists but since I had a hard time finding information on the Sony PCG-R505DL here what I did to get it working. The following are for 5.1-release only. I know they have changed for 5.2-rc2 and I will update my website http://my.fit.edu/~rresnick/ when I get 5.2 installed. The following items get the computer running, smoothly except that X crashes when you restart the X Server and corrupts the display. The only solution I found is to restart the machine. To get sound to work you need to run the following every time the machine starts up. pciconf -w -b pci0:31:0 0x61 9=20 You need to insert the following in /boot/loader.conf=20 # Sound Stuff=20 snd_pcm_load=3D"YES"=20 snd_driver_load=3D"YES"=20 # PCMCIA Stuff=20 hw.pci.allow_unsupported_io_range=3D"1"=20 #DVD Stuff=20 hw.ata.atapi_dma=3D"1"=20 hw.ata.ata_dma=3D"1"=20 You need to insert the following in /etc/sysctr.conf=20 #For DVD and KDE Sound=20 kern.ipc.shmmax=3D67108864=20 kern.ipc.shmall=3D32768=20 hw.snd.pcm0.vchans=3D4=20 hw.snd.maxautovchans=3D4 Rhian Resnick Manager of Information Technology, Evans Library=20 Florida Institute of Technology From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 08:07:11 2004 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 909D516A4CE for ; Mon, 12 Jan 2004 08:07:11 -0800 (PST) Received: from leviathan.inethouston.com (leviathan.inethouston.com [209.198.171.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4263543D48 for ; Mon, 12 Jan 2004 08:07:07 -0800 (PST) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (dwcjr [192.168.2.20]) by leviathan.inethouston.com (Postfix) with SMTP id A53BC2C9018; Mon, 12 Jan 2004 10:07:01 -0600 (CST) Message-ID: <0eda01c3d926$6c1d25a0$1402a8c0@dwcjr> From: "David W. Chapman Jr." To: "Gunnar Flygt" References: <20040108152242.GA29980@minubian.inethouston.net> <20040112160104.GB2727@sr.se> Date: Mon, 12 Jan 2004 10:09:14 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: mobile@freebsd.org Subject: Re: Laptop won't boot on 5.X 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, 12 Jan 2004 16:07:11 -0000 > On Thu, Jan 08, 2004 at 09:22:42AM -0600, David W. Chapman Jr. wrote: > > I'm trying to install 5.x, I've tried 5.1 and 5.2RC2 with no luck. > > The kernel starts to load and it locks up after probing for devices. I've tried loading with and without ACPI, it makes no difference. Thanks for the suggestion though. From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 08:17:16 2004 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 E58AE16A4CE for ; Mon, 12 Jan 2004 08:17:16 -0800 (PST) Received: from hotmail.com (law9-f71.law9.hotmail.com [64.4.9.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33FF543D31 for ; Mon, 12 Jan 2004 08:17:16 -0800 (PST) (envelope-from douglcarter@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 12 Jan 2004 08:17:15 -0800 Received: from 66.139.38.91 by lw9fd.law9.hotmail.msn.com with HTTP; Mon, 12 Jan 2004 16:17:15 GMT X-Originating-IP: [66.139.38.91] X-Originating-Email: [douglcarter@hotmail.com] X-Sender: douglcarter@hotmail.com From: "Doug Carter" To: mobile@freebsd.org Date: Mon, 12 Jan 2004 10:17:15 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 12 Jan 2004 16:17:15.0828 (UTC) FILETIME=[8B2A8F40:01C3D927] Subject: Firewire, Dell Lattitude X200, 5.1R 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, 12 Jan 2004 16:17:17 -0000 I can't see my Firewire CD plugged directly into this laptop. From DMSEG I see: fwohci0: mem 0xe0200000-0xe02007ff irq 11 at device 3.1 on pci2 fwohci0: Could not map memory device_probe_and_attach: fwohci0 attach returned 6 ...suggesting that fwohci is seeing the controller chip but can't map its memory. I've no idea what return error 6 is... Any suggestion? Otherwise (aside from acpi quirks) 5.1R is performing very well on this laptop. Thanks for the help, _________________________________________________________________ Find out everything you need to know about Las Vegas here for that getaway. http://special.msn.com/msnbc/vivalasvegas.armx From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 11:37:36 2004 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 9744016A4CE for ; Mon, 12 Jan 2004 11:37:36 -0800 (PST) Received: from infidyne.com (io.infidyne.com [212.112.161.72]) by mx1.FreeBSD.org (Postfix) with SMTP id A6D9A43D39 for ; Mon, 12 Jan 2004 11:37:06 -0800 (PST) (envelope-from peter.schuller@infidyne.com) Received: (qmail 2446 invoked from network); 12 Jan 2004 19:37:14 -0000 Received: from localhost (HELO scode.mine.nu) (scode@127.0.0.1) by localhost with SMTP; 12 Jan 2004 19:37:14 -0000 Received: from localhost (localhost [127.0.0.1]) by scode.mine.nu (Postfix) with ESMTP id 7BD8959B51; Mon, 12 Jan 2004 20:37:18 +0100 (CET) From: Peter Schuller To: Andreas Totlis , freebsd-mobile@freebsd.org Date: Mon, 12 Jan 2004 20:37:17 +0100 User-Agent: KMail/1.5.4 References: <20040111195849.GP19309@baldur.asgard> In-Reply-To: <20040111195849.GP19309@baldur.asgard> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401122037.17836.peter.schuller@infidyne.com> Subject: Re: T40p - good choice for running FBSD? 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, 12 Jan 2004 19:37:36 -0000 Hello, > I've look at a new laptop and the IBM T40p looks like nice. > After searching in this list, many employees favorite the IBM brand. > Is there any reason why I don't buy a T40p(any experience aside from > Lukas Ertl's laptop list)? > It looks like the same as T40. How contented the T40p owner? The p has a higher resolution IIRC; sligtly higher cpu frequency and built-in bluetooth by default. Also a different wireless chipset IIRC, but not sure. As for buying or not... there are a few rough edges but overall I'm quite happy with FreeBSD 5 on my T40p. I have put some notes up here that you might find worth reading: http://www.scode.org/freebsdt40p.html Short summary of things that dont quite work (though I may be forgetting something): * Having an extra battery in the "ultra bay" (or something; don't remember what they call it) results in hangs during shutdown and just about any kind of ACPI event coming from the hardware (swithing keyboard LEDs on/off etc). This was on CURRENT a while back though; it may be fixed by now. * Suspend/resume never did work right for me with ACPI, though its working now with APM given that (1) you're not in X (though X may be running on another VC) and (2) a patched em0 driver to prevent it from breaking after a resume. Sometimes you can get hangs on resume, but I think it has something to do with disc activity. Running with APM turned on, but apmd turned *off*, I don't have a problem in practice. * Bluetooth was wokring fine for me up until recently. Not sure where the problem lies though, so it may still be working and its just a configuration issue. I haven't had time to look at it in a while. Otherwise I think things are working fine. No problems with the wireless card (assuming 5.1+ CURRENT or 5.2 since the atheros driver is very new), cd burner works fine, X works fine (though no AGP)... -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 12:00:08 2004 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 71A1916A4CE for ; Mon, 12 Jan 2004 12:00:08 -0800 (PST) Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2328E43D31 for ; Mon, 12 Jan 2004 12:00:06 -0800 (PST) (envelope-from ripper@eskimo.com) Received: from eskimo.com (ripper@eskimo.com [204.122.16.13]) by mx1.eskimo.com (8.9.3/8.8.8) with ESMTP id MAA22229 for ; Mon, 12 Jan 2004 12:00:02 -0800 Received: (from ripper@localhost) by eskimo.com (8.9.1a/8.9.1) id MAA09250 for freebsd-mobile@freebsd.org; Mon, 12 Jan 2004 12:00:01 -0800 (PST) Date: Mon, 12 Jan 2004 12:00:00 -0800 From: Ross Lippert To: freebsd-mobile@freebsd.org Message-ID: <20040112120000.B5579@eskimo.eskimo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i WWW-Home-Page: http://www.eskimo.com/~ripper Subject: wirelss card & cardbus 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, 12 Jan 2004 20:00:08 -0000 I just bought a new wireless card for my laptop, which was cardbus, and it seems that that means it is unsupported (but it is not like I could tell from the distributor's site that it was cardbus or not). So, as I package this guy up for a return, I ask, does anyone have a recommendation for a card with at least 128-bit WEP and support for at least 802.11b if not g, for FBSD 4.X? -r PS Not subscribed PPS why is cardbus so miserably unsupported anyhow? From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 12:35:25 2004 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 BE97316A4CE for ; Mon, 12 Jan 2004 12:35:25 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CFDD43D81 for ; Mon, 12 Jan 2004 12:35:22 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i0CKXsET058291; Mon, 12 Jan 2004 13:33:55 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 12 Jan 2004 13:33:51 -0700 (MST) Message-Id: <20040112.133351.30983791.imp@bsdimp.com> To: rhythin@yahoo.com From: "M. Warner Losh" In-Reply-To: <20040112070640.87077.qmail@web40808.mail.yahoo.com> References: <20040112070640.87077.qmail@web40808.mail.yahoo.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-mobile@freebsd.org Subject: Re: PCCARD unrecogonized by FreeBSD 5.1-RELEASE on IBM Thinkpad 600 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, 12 Jan 2004 20:35:25 -0000 In message: <20040112070640.87077.qmail@web40808.mail.yahoo.com> Rui Li writes: : I just installed FreeBSD 5.1-RELEASE Try 5.2 : cbb0: mem : 0x21301000-0x2130fff at device 2.0 on pci0 : cardbus0: on cbb0 : pccard0: <16-bit PCCard bus> on cbb0 : cbb: Unable to map IRQ... Bummer. Unless the underlying PCI code (ACPI or PCIBIOS) can route/map the interrupt, you aren't going to get very far. :-( Warner From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 12:36:04 2004 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 939AB16A4D0 for ; Mon, 12 Jan 2004 12:36:04 -0800 (PST) Received: from hotmail.com (law9-f82.law9.hotmail.com [64.4.9.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id C619B43D6B for ; Mon, 12 Jan 2004 12:35:19 -0800 (PST) (envelope-from douglcarter@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 12 Jan 2004 12:33:50 -0800 Received: from 66.139.38.91 by lw9fd.law9.hotmail.msn.com with HTTP; Mon, 12 Jan 2004 20:33:50 GMT X-Originating-IP: [66.139.38.91] X-Originating-Email: [douglcarter@hotmail.com] X-Sender: douglcarter@hotmail.com From: "Doug Carter" To: mobile@freebsd.org Date: Mon, 12 Jan 2004 14:33:50 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 12 Jan 2004 20:33:50.0475 (UTC) FILETIME=[631745B0:01C3D94B] Subject: 5.1R, cron job "system-entropy" sending error email every 11 minutes 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, 12 Jan 2004 20:36:04 -0000 Rather tedious... The error email contains "ifconfig: not found" four times; running system-entropy in trace mode I can see it executing commands from /etc/rc.conf and ifconfig is bombing on these: + ifconfig wi0 ssid WAP1 ifconfig: not found + ifconfig wi0 stationname x200 ifconfig: not found + ifconfig wi0 wep ifconfig: not found What is further odd is that these commands work fine when the system boots and if I execute them from my shell. Any suggestion? --one week into Un?x and treading water... _________________________________________________________________ Find high-speed ‘net deals — comparison-shop your local providers here. https://broadband.msn.com From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 12:47:14 2004 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 12B3416A4CE for ; Mon, 12 Jan 2004 12:47:14 -0800 (PST) Received: from freek.com (freek.com [206.252.131.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4F3F43D55 for ; Mon, 12 Jan 2004 12:47:10 -0800 (PST) (envelope-from dorqus@freek.com) Received: by freek.com (Postfix, from userid 1000) id 877399E789; Mon, 12 Jan 2004 15:47:10 -0500 (EST) Date: Mon, 12 Jan 2004 15:47:10 -0500 From: dorqus To: mobile@freebsd.org Message-ID: <20040112204710.GH20470@freek.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Subject: Re: 5.1R, cron job "system-entropy" sending error email every 11 minutes 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, 12 Jan 2004 20:47:14 -0000 Doug Carter wrote... > The error email contains "ifconfig: not found" four times; running > system-entropy in trace mode I can see it executing commands from > /etc/rc.conf and ifconfig is bombing on these: > > + ifconfig wi0 ssid WAP1 > ifconfig: not found > + ifconfig wi0 stationname x200 > ifconfig: not found > + ifconfig wi0 wep > ifconfig: not found > > What is further odd is that these commands work fine when the system boots > and if I execute them from my shell. > > Any suggestion? Yes. Put the path to ifconfig into your shell script/cronjob/whatever. That will solve you problem. -- josh There are 10 types of people. Those that understand binary, and those that don't. From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 13:22:29 2004 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 9961C16A4CE for ; Mon, 12 Jan 2004 13:22:29 -0800 (PST) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5FD443D77 for ; Mon, 12 Jan 2004 13:22:13 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Mon, 12 Jan 2004 13:22:12 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id D46E75D07; Mon, 12 Jan 2004 13:22:11 -0800 (PST) To: Ross Lippert In-Reply-To: Message from Ross Lippert <20040112120000.B5579@eskimo.eskimo.com> Date: Mon, 12 Jan 2004 13:22:11 -0800 From: "Kevin Oberman" Message-Id: <20040112212211.D46E75D07@ptavv.es.net> cc: freebsd-mobile@freebsd.org Subject: Re: wirelss card & cardbus 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, 12 Jan 2004 21:22:29 -0000 > Date: Mon, 12 Jan 2004 12:00:00 -0800 > From: Ross Lippert > Sender: owner-freebsd-mobile@freebsd.org > > I just bought a new wireless card for my laptop, which was cardbus, > and it seems that that means it is unsupported (but it is not like I > could tell from the distributor's site that it was cardbus or not). > > So, as I package this guy up for a return, I ask, does anyone have a > recommendation for a card with at least 128-bit WEP and support for > at least 802.11b if not g, for FBSD 4.X? You can always run 5.2, just released a few minutes ago. It supports CardBus and many 'g' cards. For non-SMP systems, it's really pretty solid. There are many 16-bit 802.11b cards that will work fine with V4, but it's often hard to get the right one as manufacturers seem to change the chip used without changing the model number and often not even showing a revision number. Any card with a Intersil Prism chip should work. I've been running V5 on my laptop for some time and I'm not too sure of the state of 'G' support in STABLE. If the ath driver is in STABLE, Atheros chips should work. Most 'B' Cisco cards are also supported. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 13:30:41 2004 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 2B84116A4D4 for ; Mon, 12 Jan 2004 13:30:41 -0800 (PST) Received: from mail.devrandom.org.uk (82-68-135-38.dsl.in-addr.zen.co.uk [82.68.135.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC73F43D5D for ; Mon, 12 Jan 2004 13:30:39 -0800 (PST) (envelope-from howells@kde.org) Received: from 0-c-6e-e5-27-1.middleearth (0-c-6e-e5-27-1.middleearth [192.168.1.183]) by mail.devrandom.org.uk (Postfix) with ESMTP id 79F20133BC for ; Mon, 12 Jan 2004 21:30:38 +0000 (GMT) From: Chris Howells Organization: K Desktop Environment To: freebsd-mobile@freebsd.org Date: Mon, 12 Jan 2004 21:30:11 +0000 User-Agent: KMail/1.5.94 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200401122130.11472.howells@kde.org> Subject: Re: 5.1R, cron job "system-entropy" sending error email every 11 minutes 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, 12 Jan 2004 21:30:41 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 12 January 2004 20:33, Doug Carter wrote: > What is further odd is that these commands work fine when the system boots > and if I execute them from my shell. /sbin isn't in $PATH. Run /sbin/ifconfig, rather than just ifconfig, or as= =20 another poster said, add /sbin to $PATH. Though personally I prefer the=20 former solution. =2D --=20 Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAAxHjF8Iu1zN5WiwRAguJAJ0VnRGVfaLent0RnneujGWbp9///wCfcuzG SL66M/4sdf/8knDTwvJVSMg=3D =3D2Cd1 =2D----END PGP SIGNATURE----- From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 18:02:17 2004 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 9D2C116A4CE for ; Mon, 12 Jan 2004 18:02:17 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 677D743D3F for ; Mon, 12 Jan 2004 18:02:16 -0800 (PST) (envelope-from jerry@thehutt.org) Received: from risus.thehutt.org (pcp08562308pcs.alxndr01.va.comcast.net[68.86.31.94]) by comcast.net (rwcrmhc13) with ESMTP id <2004011302021601500b5ep2e>; Tue, 13 Jan 2004 02:02:16 +0000 Received: from jerry by risus.thehutt.org with local (Exim 4.22) id 1AgDsV-0002Cn-J3; Mon, 12 Jan 2004 21:01:59 -0500 Date: Mon, 12 Jan 2004 21:01:59 -0500 From: Jerry A! To: Kevin Oberman Message-ID: <20040113020159.GA8426@risus.thehutt.org> References: <20040112120000.B5579@eskimo.eskimo.com> <20040112212211.D46E75D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040112212211.D46E75D07@ptavv.es.net> Organization: Broken Toys Unlimited User-Agent: Mutt/1.5.5i Sender: Jerry A! cc: Ross Lippert cc: freebsd-mobile@freebsd.org Subject: Re: wirelss card & cardbus 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, 13 Jan 2004 02:02:17 -0000 On Mon, Jan 12, 2004 at 01:22:11PM -0800, Kevin Oberman wrote: : You can always run 5.2, just released a few minutes ago. It supports : CardBus and many 'g' cards. For non-SMP systems, it's really pretty : solid. : : There are many 16-bit 802.11b cards that will work fine with V4, but : it's often hard to get the right one as manufacturers seem to change the : chip used without changing the model number and often not even showing a : revision number. My recommendation for what's currently on the market is the Microsoft MN-520. It's the only pcmcia card I've found that's also prism2.5. : Any card with a Intersil Prism chip should work. I've been running V5 on : my laptop for some time and I'm not too sure of the state of 'G' support : in STABLE. If the ath driver is in STABLE, Atheros chips should : work. Most 'B' Cisco cards are also supported. Watch out. I banged my head into a brick wall w/some of the newer prism3 cards--specifically the D-Link 650. The newest ones are indeed prism3. Unfortunately, they won't work b/c they upload the code via serial eeprom (which FreeBSD currently doesn't support). --Jerry -- "Barbie would also be tired of Microsoft's licensing bullshit." -- Maury Cesterino, Chief Software Architect, Mattel, Inc. From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 18:10:17 2004 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 A11F616A4CE for ; Mon, 12 Jan 2004 18:10:17 -0800 (PST) Received: from Espresso.NEEBU.Net (espresso.neebu.net [66.166.158.130]) by mx1.FreeBSD.org (Postfix) with SMTP id B50DC43D53 for ; Mon, 12 Jan 2004 18:10:14 -0800 (PST) (envelope-from khuon@Espresso.NEEBU.Net) Received: from Espresso.NEEBU.Net (khuon@localhost [127.0.0.1]) by Espresso.NEEBU.Net (8.12.10/8.12.10) with ESMTP id i0D2AD7v002578 for ; Mon, 12 Jan 2004 18:10:13 -0800 (PST) Received: from Espresso.NEEBU.Net (khuon@localhost)i0D2AD7Y002577 for ; Mon, 12 Jan 2004 18:10:13 -0800 (PST) Message-Id: <200401130210.i0D2AD7Y002577@Espresso.NEEBU.Net> From: "Jake Khuon" To: freebsd-mobile@freebsd.org Dcc: Action: Expires: Precedence: Priority: Normal X-Face: "(e&e|OIYrcV1x8y?txN%k1E2f[qWLjRjOn+a30)3>x`Wx%_9XiXs\IO2#G5L1m=c/|^h|z29wJ#]D/.?Ks,Mw1 X-URI: http://Espresso.NEEBU.Net/~khuon/ X-Organisation: Network Engineers for Effective Bandwidth Utilisation X-Header: /usr/include gives great headers X-System: Sun UltraSPARCstation2/2300MP running SunOS Release 5.8 X-Shell: tcsh 6.07.02 (Astron) 1996-10-27 (sparc-sun-solaris) options 8b,nls,dl,al,ng,rh X-Chtorr: History is full of revisionists. Where it used to say "THOU SHALT NOT KILL" it now says, "except as specified in section III-B, Paragraph 12, Sub-section D, Schedule 3." If that still doesn't suit you, wait till next year's commandments come out and trade it in for something that does. X-Mailer: MH 6.8.4 #4[UCI] (Espresso.NEEBU.Net) of Mon Feb 19 15:14:03 EST 1996 Date: Mon, 12 Jan 2004 18:10:13 -0800 Sender: khuon@Espresso.NEEBU.Net Subject: modified wmwave for Aironet driver X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Reply-To: Jake Khuon List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 02:10:17 -0000 When I used to have a laptop with an Orinoco card, one of my most treasured dockapps was wmwave. Since moving on to a Cisco 350 MPI card, I have hunted high and low for something similar to no avail. I tried wmWiFi but all it did was spit out ioctl() failures and I really did prefer the look of wmwave. So after looking at the differences between the driver header files, I decided last night to just hack wmwave. I must admit that I was lazy and didn't bother to formally convert this port. I just simply hacked the main file. Perhaps when I have more time I'll clean things up and make it nicer. Of course if someone wants to do that for me, I'm not going to stop them. |8^) The file can be found at: http://www.neebu.net/~khuon/codebits/wmwave.c Here's a summary of the list of changes I made: [0] I grabbed a copy of the net/wmwave ports and extracted it into /tmp to do the work while not contaminating my own ports tree. [a] I just performed a make (not make install) to get the files into a state for hacking. [b] After I finished, I renamed wmwave to wmairo and copied it manually to /usr/local/bin instead of doing a make install. As I said above, if I happen to find some copious free time, I'll make this a nice and clean port. [1] Most of the definitions were similar so I started out doing a global replace on a lot of variable and structure names. [2] For some reason the signal cache (ANCACHE) for the aironet drivers never get properly populated. Either that or I'm interrogating the structure wrong. However "ancontrol -i an0 -Q" always returns a blank for me. After playing around with it for a while, I ditched the idea and just grabbed the information out of the an_ltv_status structure instead. [a] The signal quality seemed to be reversed. Even ancontrol reports what I think is opposite. In other words, as I move closer to the AP, I saw the value of an_cur_signal_quality going down. I decided to do a quick hack on the value to reverse it. It now _seems_ correct. [b] The scaling seemed wrong with the original code. Perhaps it was correct given values as reported in wi_sigcache. I removed all the scaling modifiers and the values seem to line up better. [3] I changed the name of the labels so that they make a little more sense. [a] The general status label used to show either "Quality" (card present) or "No Card" (card not available) followed by a coloured dot to indicate general signal quality (red = bad, yellow = mediocre, green = good). The actual "Link" bargraph showed the quality in a more graduated manner. I decided I could make better use of the label area so I added some code to display the channel number (an_cur_channel) instead. It will still display "No Card" when a card can't be found. My intent was to give me a better sense of which AP I was associated with. I thought about using the value of an_ap_name but my experi4ence is that it's unreliable. Many APs don't have it properly set and actually my config tools for my APs don't seem to have a way to set them. Additionally, I'm not sure they're ever transmitted. Then again I'm not an 802.11 guru. I also thought about using the MAC address off the AP but I didn't think it would fit nicely. [b] I renamed "Level" to say "Strength" since I'm grabbing the value of an_normalized_strength and thus seemed to make more sense. I also fixed scaling. [c] I left the "Noise" label alone but I'm not sure I'm retrieving the correct element. I'm looking at an_noise_prev_sec_pc which should be giving me the noise in percentage but I've never seen it anything but 1% although every once in a while I will see a slight flash to around 20% but that may just be an anomaly in the polling. Perhaps I should try firing up one of my cordless phones and sticking it next to my laptop. I also added the ability to report SNR instead of noise. Compile with -DSNR to enable this. Well, I think that's about it... I hope it's useful to someone other than me. -- /*===================[ Jake Khuon ]======================+ | Packet Plumber, Network Engineers /| / [~ [~ |) | | --------------- | | for Effective Bandwidth Utilisation / |/ [_ [_ |) |_| N E T W O R K S | +=========================================================================*/ From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 18:56:19 2004 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 B643716A4CE for ; Mon, 12 Jan 2004 18:56:19 -0800 (PST) Received: from hotmail.com (law9-f124.law9.hotmail.com [64.4.9.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id B550343D49 for ; Mon, 12 Jan 2004 18:56:18 -0800 (PST) (envelope-from douglcarter@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 12 Jan 2004 18:56:18 -0800 Received: from 66.139.38.91 by lw9fd.law9.hotmail.msn.com with HTTP; Tue, 13 Jan 2004 02:56:18 GMT X-Originating-IP: [66.139.38.91] X-Originating-Email: [douglcarter@hotmail.com] X-Sender: douglcarter@hotmail.com From: "Doug Carter" To: mobile@freebsd.org Date: Mon, 12 Jan 2004 20:56:18 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 13 Jan 2004 02:56:18.0575 (UTC) FILETIME=[D13971F0:01C3D980] Subject: Re: 5.1R, cron job "system-entropy" sending error email every 11minutes - SOLVED 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, 13 Jan 2004 02:56:19 -0000 Turns out that the cron job should not have been trying to execute ifconfig anyway. I mistakenly put the configuration commands for my wireless card in /etc/rc.conf instead of creating and using /etc/start_if.wi0 for the ifconfig commands solved the problem. Still clueless about getting the Firewire CD R/W to work though.... ----Original Message Follows---- From: Chris Howells To: freebsd-mobile@freebsd.org Subject: Re: 5.1R, cron job "system-entropy" sending error email every 11minutes Date: Mon, 12 Jan 2004 21:30:11 +0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 12 January 2004 20:33, Doug Carter wrote: > What is further odd is that these commands work fine when the system boots > and if I execute them from my shell. /sbin isn't in $PATH. Run /sbin/ifconfig, rather than just ifconfig, or as another poster said, add /sbin to $PATH. Though personally I prefer the former solution. - -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAAxHjF8Iu1zN5WiwRAguJAJ0VnRGVfaLent0RnneujGWbp9///wCfcuzG SL66M/4sdf/8knDTwvJVSMg= =2Cd1 -----END PGP SIGNATURE----- _______________________________________________ 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" _________________________________________________________________ Find out everything you need to know about Las Vegas here for that getaway. http://special.msn.com/msnbc/vivalasvegas.armx From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 20:22:38 2004 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 A542116A4CE for ; Mon, 12 Jan 2004 20:22:38 -0800 (PST) Received: from mail.lambertfam.org (www.lambertfam.org [216.223.208.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9743843D4C for ; Mon, 12 Jan 2004 20:22:37 -0800 (PST) (envelope-from lambert@lambertfam.org) Received: from laptop.lambertfam.org (ool-182db8f6.dyn.optonline.net [24.45.184.246]) by mail.lambertfam.org (Postfix) with ESMTP id 0826134D2D for ; Mon, 12 Jan 2004 23:22:37 -0500 (EST) Received: by laptop.lambertfam.org (Postfix, from userid 1001) id 3462FC0E7; Mon, 12 Jan 2004 23:22:34 -0500 (EST) Date: Mon, 12 Jan 2004 23:22:34 -0500 From: Scott Lambert To: freebsd-mobile@freebsd.org Message-ID: <20040113042234.GD2853@laptop.lambertfam.org> Mail-Followup-To: freebsd-mobile@freebsd.org References: <20040112120000.B5579@eskimo.eskimo.com> <20040112212211.D46E75D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040112212211.D46E75D07@ptavv.es.net> User-Agent: Mutt/1.5.5.1i Subject: Re: wirelss card & cardbus 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, 13 Jan 2004 04:22:38 -0000 On Mon, Jan 12, 2004 at 01:22:11PM -0800, Kevin Oberman wrote: > > Date: Mon, 12 Jan 2004 12:00:00 -0800 > > From: Ross Lippert > > Sender: owner-freebsd-mobile@freebsd.org > > > > I just bought a new wireless card for my laptop, which was cardbus, > > and it seems that that means it is unsupported (but it is not like I > > could tell from the distributor's site that it was cardbus or not). > > > > So, as I package this guy up for a return, I ask, does anyone have a > > recommendation for a card with at least 128-bit WEP and support for > > at least 802.11b if not g, for FBSD 4.X? > > You can always run 5.2, just released a few minutes ago. It supports > CardBus and many 'g' cards. For non-SMP systems, it's really pretty > solid. Even many of the unsupported wireless cards are supported in 5.2-CURRENT. My new laptop has a built-in "HP WLAN 54g W450 Network Adapter", which is apparantly a Broadcom chip. With the NDIS driver in -CURRENT, it works just great. :-) -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 21:28:43 2004 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 D4AA216A4CE for ; Mon, 12 Jan 2004 21:28:43 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 895D643D1F for ; Mon, 12 Jan 2004 21:28:42 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id CC2BF307CE; Tue, 13 Jan 2004 00:28:41 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 278D21D1DAF; Mon, 29 Sep 2003 21:59:49 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16248.58260.560180.809655@canoe.dclg.ca> To: freebsd-mobile@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid Subject: ATH driver doesn't associate with turbo. 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: , Date: Tue, 13 Jan 2004 05:28:43 -0000 X-Original-Date: Mon, 29 Sep 2003 21:59:48 -0400 X-List-Received-Date: Tue, 13 Jan 2004 05:28:43 -0000 If I put my access point in turbo mode, the ath driver won't associate with it. Additionally, the documentation for my card says that it should support upto 108Mbps in turbo mode, but the ath driver doesn't detect this. This is somewhat of a datapoint, since I don't know if this is supposed to work. My card probes as: Preloaded elf module "/boot/kernel/if_ath.ko" at 0xc084836c. Preloaded elf module "/boot/kernel/ath_hal.ko" at 0xc0848418. ath0: mem 0xfafd0000-0xfafdffff irq 11 at device 3.0 on pci2 ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps 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: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 802.11 address: 00:02:6f:20:5a:23 I've also noticed that the driver will stop receiving packets every once in awhile (one or two dropped pings) ... but I nailed down what causes that yet. The access point is a Netgear HE 102 (a-only) that I got for $26.96 Cdn. I also have a FreeBSD 802.11b access point in the area. When I put the Netgear into turbo "enabled" mode, the ath card associates only with my 802.11b point. If I force the ssid to the a-only ssid, the ath card doesn't associate. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 12 21:44:56 2004 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 C66B816A4CE for ; Mon, 12 Jan 2004 21:44:56 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F94B43D5A for ; Mon, 12 Jan 2004 21:44:55 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id i0D5iqHQ026189 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 12 Jan 2004 21:44:53 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: David Gilbert , freebsd-mobile@freebsd.org Date: Mon, 12 Jan 2004 21:49:06 -0800 User-Agent: KMail/1.5.3 References: <16248.58260.560180.809655@canoe.dclg.ca> In-Reply-To: <16248.58260.560180.809655@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401122149.06369.sam@errno.com> Subject: Re: ATH driver doesn't associate with turbo. 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, 13 Jan 2004 05:44:56 -0000 On Monday 29 September 2003 06:59 pm, David Gilbert wrote: > If I put my access point in turbo mode, the ath driver won't associate > with it. Additionally, the documentation for my card says that it > should support upto 108Mbps in turbo mode, but the ath driver doesn't > detect this. > What do you base this on? The turbo rates happen to be printed as 1/2 the actual speed.because the actual rate is done by overclocking and not by negotiating a different xmit rate. I've thought about artificially printing them as 2x values so people stop complaining. :) As to not being able to associate in turbo mode; you don't show how you configured the interface. Atheros-based AP's that support "SuperG" use a proprietary protocol handshake to negotiate use of turbo mode. The current driver doesn't support this though I recently got the info I need to add it. For "old turbo" mode you have to manually enable it with ifconfig before the 802.11 layer will assoociate with a turbo AP. I've considered changing this but adding turbo mode channels to the scan list would more often than not just lengthen the scanning process and rarely be used. > This is somewhat of a datapoint, since I don't know if this is > supposed to work. My card probes as: > > Preloaded elf module "/boot/kernel/if_ath.ko" at 0xc084836c. > Preloaded elf module "/boot/kernel/ath_hal.ko" at 0xc0848418. > ath0: mem 0xfafd0000-0xfafdffff irq 11 at device 3.0 on pci2 > ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 > ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > 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: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps > 24Mbps 36Mbps 48Mbps 54Mbps ath0: 802.11 address: 00:02:6f:20:5a:23 > > I've also noticed that the driver will stop receiving packets every > once in awhile (one or two dropped pings) ... but I nailed down what > causes that yet. > I just committed some new stuff to sourceforge (the Linux version of the driver) and will get the equivalent updates into FreeBSD soon. These changes should improve reliability and performance for 5212-based cards. > The access point is a Netgear HE 102 (a-only) that I got for $26.96 > Cdn. I also have a FreeBSD 802.11b access point in the area. When I > put the Netgear into turbo "enabled" mode, the ath card associates > only with my 802.11b point. If I force the ssid to the a-only ssid, > the ath card doesn't associate. Yes, because setting turbo mode effectively removes the 11a channel set. If you set both AP and station into turbo mode you should be able to associate. Sam From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 01:33:40 2004 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 A866416A4CF for ; Tue, 13 Jan 2004 01:33:40 -0800 (PST) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6607F43D49 for ; Tue, 13 Jan 2004 01:33:37 -0800 (PST) (envelope-from c.widger@comcast.net) Received: from 204.127.197.116 ([204.127.197.116]) by comcast.net (rwcrmhc11) with SMTP id <20040113093337013006cejde>; Tue, 13 Jan 2004 09:33:37 +0000 Received: from [24.5.158.1] by 204.127.197.116; Tue, 13 Jan 2004 09:33:36 +0000 From: c.widger@comcast.net To: freebsd-mobile@freebsd.org Date: Tue, 13 Jan 2004 09:33:36 +0000 Message-Id: <011320040933.1330.4d53@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 27 2003) X-Authenticated-Sender: Yy53aWRnZXJAY29tY2FzdC5uZXQ= Subject: Wireless 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, 13 Jan 2004 09:33:40 -0000 Hi, I recently purchased a D-Link DWL-650 16-bit pcmcia card. When I put the card in on my 5.2rc1 laptop it told me card unsuported. I looked arround on the Internet and found my card had a prism3 chipset, good but bad. Since the name of the card, when read by pccardd, is a little different I put the card in my 4.9 laptop and added a line to /etc/pccard.conf. When the card went in the wi driver was loaded, but this came up: pccard: card inserted, slot 0 pccardd[42]: Card "D-Link"("DWL-650 Wireless PC Card RevP" ) [ISL37101P-10] [A3] matched "D-Link" (DWL-650 Wireless PC Card RevP") [(null) ] [(null)] wi0 at port 0x280-0x2ff irq 3 slot 0 on pccard0 wi0: timeout in wi_cmd 0x0000; event status 0x0000 wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: init failed wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: mac read failed 5 device_probe_and attach: wi0 attach returned 5 /kernel: stray irq 3 pccardd[42]: driver allocation failed for D-Link(DWL-650 W ireless PC Card RevP): Input/output error Warner, The help you give the people on this list is excelent. Thank you for sharing your wide knowledge. >Message: 21 >Date: Mon, 12 Jan 2004 12:00:00 -0800 >From: Ross Lippert >Subject: wirelss card & cardbus >To: freebsd-mobile@freebsd.org >Message-ID: <20040112120000.B5579@eskimo.eskimo.com> >Content-Type: text/plain; charset=us-ascii > >I just bought a new wireless card for my laptop, which was cardbus, >and it seems that that means it is unsupported (but it is not like I >could tell from the distributor's site that it was cardbus or not). > >So, as I package this guy up for a return, I ask, does anyone have a >recommendation for a card with at least 128-bit WEP and support for >at least 802.11b if not g, for FBSD 4.X? > > > >-r >PS Not subscribed >PPS why is cardbus so miserably unsupported anyhow? The Lucent Wavelan cards work fine, the one I have is sold as an Avaya (Avaya Wireless World Card 11 Mb/s GOLD) but it's the same thing. It works instantly under 4.X and even 5.2rc2. From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 06:01:44 2004 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 CE10716A4CE for ; Tue, 13 Jan 2004 06:01:44 -0800 (PST) Received: from sizone.org (mortar.sizone.org [65.126.154.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C6DD43D5E for ; Tue, 13 Jan 2004 06:01:40 -0800 (PST) (envelope-from dgilbert@daveg.ca) Received: by sizone.org (Postfix, from userid 66) id 99817307D1; Tue, 13 Jan 2004 09:01:39 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id D99271D1E34; Tue, 13 Jan 2004 07:28:51 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16387.58499.587197.601294@canoe.dclg.ca> Date: Tue, 13 Jan 2004 07:28:51 -0500 To: Sam Leffler In-Reply-To: <200401122149.06369.sam@errno.com> References: <16248.58260.560180.809655@canoe.dclg.ca> <200401122149.06369.sam@errno.com> X-Mailer: VM 7.17 under 21.4 (patch 14) "Reasonable Discussion" XEmacs Lucid cc: freebsd-mobile@freebsd.org cc: David Gilbert Subject: Re: ATH driver doesn't associate with turbo. 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, 13 Jan 2004 14:01:44 -0000 >>>>> "Sam" == Sam Leffler writes: Sam> On Monday 29 September 2003 06:59 pm, David Gilbert wrote: >> If I put my access point in turbo mode, the ath driver won't >> associate with it. Additionally, the documentation for my card >> says that it should support upto 108Mbps in turbo mode, but the ath >> driver doesn't detect this. Sam> What do you base this on? The turbo rates happen to be printed Sam> as 1/2 the actual speed.because the actual rate is done by Sam> overclocking and not by negotiating a different xmit rate. I've Sam> thought about artificially printing them as 2x values so people Sam> stop complaining. :) Fair enough. If this is the case, then things are correct. Sam> As to not being able to associate in turbo mode; you don't show Sam> how you configured the interface. Atheros-based AP's that Sam> support "SuperG" use a proprietary protocol handshake to Sam> negotiate use of turbo mode. The current driver doesn't support Sam> this though I recently got the info I need to add it. For "old Sam> turbo" mode you have to manually enable it with ifconfig before Sam> the 802.11 layer will assoociate with a turbo AP. I've Sam> considered changing this but adding turbo mode channels to the Sam> scan list would more often than not just lengthen the scanning Sam> process and rarely be used. The access point is an A-only unit made by Netgear. It advertises turbo modes only upto 72 megabit in it's documentation. Concerning your 'rarely used' comment, is it that access points based on Athros are rare or that turbo mode itself is not that useful? Maybe it would be sufficient to have a mode 11a-turbo in addition to mode 11a that is not part of the automatic scan. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can only be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 07:43:40 2004 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 86D8E16A4CE for ; Tue, 13 Jan 2004 07:43:40 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD67B43D3F for ; Tue, 13 Jan 2004 07:43:24 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com) by ran.psg.com with esmtp (Exim 4.24; FreeBSD) id 1AgQhO-00014c-Fa; Tue, 13 Jan 2004 07:43:22 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Sam Leffler References: <16248.58260.560180.809655@canoe.dclg.ca> <200401122149.06369.sam@errno.com> <16387.58499.587197.601294@canoe.dclg.ca> Message-Id: Date: Tue, 13 Jan 2004 07:43:22 -0800 cc: freebsd-mobile@freebsd.org Subject: Re: ATH driver doesn't associate with turbo. 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, 13 Jan 2004 15:43:40 -0000 thinkpad t40p current as of 6 jan (real current has fatal ata crashes) ath0: mem 0xc0210000-0xc021ffff irq 11 at device 2.0 on pci2 ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3 ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 802.11 address: 00:05:4e:41:ee:cd nokia ap with orinoco gold card on chan 11 netgear he102 802.11a ap on chan 52 (5.26GHz) all on same ssid sometimes ath0 associates with one ap, sometimes the other, and it will switch from 11a to 11b and not come back to 11a. e.g., right now it says # ifconfig ath0 ath0: flags=8843 mtu 1500 inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:05:4e:41:ee:cd media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid rgnet-home 1:rgnet-home channel 11 authmode OPEN powersavemode OFF powersavesleep 100 wepmode OFF weptxkey 1 wepkey 1:104-bit i suspect the ath driver, as i do not see similar issues in winxp. but of course, when debugging, i am not sure of anything. randy From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 08:09:56 2004 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 0D76B16A4CE for ; Tue, 13 Jan 2004 08:09:56 -0800 (PST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10A4943D48 for ; Tue, 13 Jan 2004 08:09:54 -0800 (PST) (envelope-from jerry@thehutt.org) Received: from risus.thehutt.org (pcp08562308pcs.alxndr01.va.comcast.net[68.86.31.94]) by comcast.net (sccrmhc13) with ESMTP id <2004011316095301600t527oe>; Tue, 13 Jan 2004 16:09:53 +0000 Received: from jerry by risus.thehutt.org with local (Exim 4.22) id 1AgR72-0003dB-Vd; Tue, 13 Jan 2004 11:09:52 -0500 Date: Tue, 13 Jan 2004 11:09:52 -0500 From: Jerry A! To: c.widger@comcast.net Message-ID: <20040113160952.GB13821@risus.thehutt.org> References: <011320040933.1330.4d53@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <011320040933.1330.4d53@comcast.net> Organization: Broken Toys Unlimited User-Agent: Mutt/1.5.5i Sender: Jerry A! cc: freebsd-mobile@freebsd.org Subject: Re: Wireless 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, 13 Jan 2004 16:09:56 -0000 On Tue, Jan 13, 2004 at 09:33:36AM +0000, c.widger@comcast.net wrote: : Hi, : : I recently purchased a D-Link DWL-650 16-bit pcmcia card. When I put the card in on my 5.2rc1 laptop it told me card unsuported. I looked arround on the Internet and found my card had a prism3 chipset, good but bad. Since the name of the card, when read by pccardd, is a little different I put the card in my 4.9 laptop and added a line to /etc/pccard.conf. When the card went in the wi driver was loaded, but this came up: : : pccard: card inserted, slot 0 : pccardd[42]: Card "D-Link"("DWL-650 Wireless PC Card RevP" : ) [ISL37101P-10] [A3] matched "D-Link" (DWL-650 Wireless PC Card RevP") [(null) : ] [(null)] : wi0 at port 0x280-0x2ff irq 3 slot 0 on pccard0 : wi0: timeout in wi_cmd 0x0000; event status 0x0000 : wi0: wi_cmd: busy bit won't clear. : wi0: wi_cmd: busy bit won't clear. : wi0: init failed : wi0: wi_cmd: busy bit won't clear. : wi0: wi_cmd: busy bit won't clear. : wi0: mac read failed 5 : device_probe_and attach: wi0 attach returned 5 : /kernel: stray irq 3 : pccardd[42]: driver allocation failed for D-Link(DWL-650 W : ireless PC Card RevP): Input/output error : : Warner, : : The help you give the people on this list is excelent. Thank you for : sharing your wide knowledge. Return it!!! I banged my head against the wall w/that card. It is indeed a prism3. However, when I did some digging in the Linux mailing lists, I found out that it loads it's firmware via serial eeprom when the card is initialized. Those guys are still working on getting that part working. From what digging around I did, I didn't see any support for such operations in FreeBSD. --Jerry -- "In Jersey anything's legal, as long as you don't get caught" -- The Travelling Wilburys 'Tweeter And The Monkeyman' From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 09:36:31 2004 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 B2BAD16A4CE for ; Tue, 13 Jan 2004 09:36:31 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBE1443D48 for ; Tue, 13 Jan 2004 09:36:27 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id i0DHa9HQ029055 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 13 Jan 2004 09:36:11 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: David Gilbert Date: Tue, 13 Jan 2004 09:40:23 -0800 User-Agent: KMail/1.5.3 References: <16248.58260.560180.809655@canoe.dclg.ca> <200401122149.06369.sam@errno.com> <16387.58499.587197.601294@canoe.dclg.ca> In-Reply-To: <16387.58499.587197.601294@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401130940.23993.sam@errno.com> cc: freebsd-mobile@freebsd.org Subject: Re: ATH driver doesn't associate with turbo. 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, 13 Jan 2004 17:36:31 -0000 On Tuesday 13 January 2004 04:28 am, David Gilbert wrote: > >>>>> "Sam" == Sam Leffler writes: > > Sam> On Monday 29 September 2003 06:59 pm, David Gilbert wrote: > >> If I put my access point in turbo mode, the ath driver won't > >> associate with it. Additionally, the documentation for my card > >> says that it should support upto 108Mbps in turbo mode, but the ath > >> driver doesn't detect this. > > Sam> What do you base this on? The turbo rates happen to be printed > Sam> as 1/2 the actual speed.because the actual rate is done by > Sam> overclocking and not by negotiating a different xmit rate. I've > Sam> thought about artificially printing them as 2x values so people > Sam> stop complaining. :) > > Fair enough. If this is the case, then things are correct. > > Sam> As to not being able to associate in turbo mode; you don't show > Sam> how you configured the interface. Atheros-based AP's that > Sam> support "SuperG" use a proprietary protocol handshake to > Sam> negotiate use of turbo mode. The current driver doesn't support > Sam> this though I recently got the info I need to add it. For "old > Sam> turbo" mode you have to manually enable it with ifconfig before > Sam> the 802.11 layer will assoociate with a turbo AP. I've > Sam> considered changing this but adding turbo mode channels to the > Sam> scan list would more often than not just lengthen the scanning > Sam> process and rarely be used. > > The access point is an A-only unit made by Netgear. It advertises > turbo modes only upto 72 megabit in it's documentation. > This is a 5210-based product. Turbo mode, if I recall, didn't work all that great. Just fyi. > Concerning your 'rarely used' comment, is it that access points based > on Athros are rare or that turbo mode itself is not that useful? > Turbo mode is an Atheros-proprietary feature. Until we have the auto-negotiation handshake in place in FreeBSD you must manually configure it on both the AP and client and when you do that you cannot fallback to non-turbo operation (in 11a). This makes it a nuisance to use and so I believe it will be "rarely used". > Maybe it would be sufficient to have a mode 11a-turbo in addition to > mode 11a that is not part of the automatic scan. Turbo was done a modified bit because it actually can be used in both 11a and 11g operation. I need to fix the 802.11 support to handle it better. But that won't happen for a while unless someone else does it. Sam From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 09:38:41 2004 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 BF4E016A4CE for ; Tue, 13 Jan 2004 09:38:41 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EA6443D5A for ; Tue, 13 Jan 2004 09:38:40 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id i0DHcdHQ029078 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 13 Jan 2004 09:38:40 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: Randy Bush Date: Tue, 13 Jan 2004 09:42:54 -0800 User-Agent: KMail/1.5.3 References: <16248.58260.560180.809655@canoe.dclg.ca> <16387.58499.587197.601294@canoe.dclg.ca> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401130942.54979.sam@errno.com> cc: freebsd-mobile@freebsd.org Subject: Re: ATH driver doesn't associate with turbo. 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, 13 Jan 2004 17:38:41 -0000 [Please do not send me mail and cc a mailing list; I read most fbsd mailing lists.] On Tuesday 13 January 2004 07:43 am, Randy Bush wrote: > thinkpad t40p current as of 6 jan (real current has fatal ata crashes) > ath0: mem 0xc0210000-0xc021ffff irq 11 at device 2.0 on > pci2 ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3 > ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > ath0: 802.11 address: 00:05:4e:41:ee:cd > nokia ap with orinoco gold card on chan 11 > netgear he102 802.11a ap on chan 52 (5.26GHz) > > all on same ssid > > sometimes ath0 associates with one ap, sometimes the other, and it > will switch from 11a to 11b and not come back to 11a. e.g., right > now it says > > # ifconfig ath0 > ath0: flags=8843 mtu 1500 > inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:05:4e:41:ee:cd > media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) > status: associated > ssid rgnet-home 1:rgnet-home > channel 11 authmode OPEN powersavemode OFF powersavesleep 100 > wepmode OFF weptxkey 1 > wepkey 1:104-bit > > i suspect the ath driver, as i do not see similar issues in winxp. > but of course, when debugging, i am not sure of anything. The 802.11 code scans all channels by default. It does not, for example, stick to a band where it finds an AP. If you want to constrain it's search to a particular band use something like ifconfig ath0 mode 11a If that doesn't answer what you were asking try adding a "?" somewhere :) Sam From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 09:44:13 2004 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 5D4E816A4CE for ; Tue, 13 Jan 2004 09:44:13 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8AB843D45 for ; Tue, 13 Jan 2004 09:44:04 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id i0DHhpHQ029113 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 13 Jan 2004 09:43:52 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: David Gilbert Date: Tue, 13 Jan 2004 09:48:06 -0800 User-Agent: KMail/1.5.3 References: <16248.58260.560180.809655@canoe.dclg.ca> <16387.58499.587197.601294@canoe.dclg.ca> <200401130940.23993.sam@errno.com> In-Reply-To: <200401130940.23993.sam@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401130948.06429.sam@errno.com> cc: freebsd-mobile@freebsd.org Subject: Re: ATH driver doesn't associate with turbo. 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, 13 Jan 2004 17:44:13 -0000 On Tuesday 13 January 2004 09:40 am, Sam Leffler wrote: > Turbo was done a modified bit because it actually can be used in both 11a > and 11g operation. I need to fix the 802.11 support to handle it better. > But that won't happen for a while unless someone else does it. Gah, fractured typing: "Turbo was done with a modifier bit..." Sam From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 09:57:50 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 1E98716A52B; Tue, 13 Jan 2004 09:57:49 -0800 (PST) To: freebsd-mobile@freebsd.org Date: Tue, 13 Jan 2004 09:57:49 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20040113175749.1E98716A52B@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Subject: Sony TR2A and FreeBSD -- any comments? 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, 13 Jan 2004 17:57:50 -0000 I currently own a Sony PCG-C1VP Picturebook laptop which has served me well for about two years now (in spite of its disk dying on me recently). I'm contemplating upgrading it to a Sony TR2A, but I'd prefer not to plunk down the money on it only to encounter unexpected problems trying to get FreeBSD running on it. Unfortunately, I don't know anyone who has one of these things, and I can't easily experiment on the demo models in the local computer stores, so I'm hoping someone here has some experience with one of these and can answer some questions. Has anyone tried running FreeBSD 5.x on one of these yet? Does it actually boot up and run correctly? Does the cardbus bridge work? (Hi Warner!) Does the ATA controller work? And, most important of all, does anyone know if the built-in camera can be made to work? In the Picturebook, the camera is a PCI device, and I have a special capture utility installed to operate it. However the camera in the TR2A appears to be a USB device, and I have no idea what chip it uses. It has been suggested that it might work with gphoto, but I have no proof of this one way or the other. All the other hardware in the TR2A should work with FreeBSD and XFree86, except possibly for the modem. It has two USB 2.0 ports, firewire, built-in Intel 82559 10/100 ethernet, Intel 82852/82855 graphics, Centrino 802.11b wireless, DVD-ROM/CD-RW drive, and a 40GB disk. About the only thing I don't like about it is the fact that it doesn't come with a recovery media DVD. Instead, it has a recovery 'partition' on the disk, and somewhere there is an option to burn your own set of recovery CDs -- _nine_ of them! Any info anyone can offer would be much appreciated. I would love to get one of these things running with FreeBSD 5.2-RELEASE on it. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 10:48:16 2004 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 8E98716A4CE for ; Tue, 13 Jan 2004 10:48:16 -0800 (PST) Received: from cwnet5.wirelessnet.de (cwnet5.wirelessnet.de [212.20.170.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65F5243D5A for ; Tue, 13 Jan 2004 10:48:13 -0800 (PST) (envelope-from usenet@esct.org) Received: from baldur.asgard (pd9ec29ef.dip.t-dialin.net [217.236.41.239]) by cwnet5.wirelessnet.de (Postfix) with ESMTP id 9636C18C77 for ; Tue, 13 Jan 2004 19:49:21 +0100 (CET) Received: by baldur.asgard (Postfix, from userid 1001) id 998CA267; Tue, 13 Jan 2004 19:48:10 +0100 (CET) Date: Tue, 13 Jan 2004 19:48:10 +0100 From: Andreas Totlis To: freebsd-mobile@freebsd.org Message-ID: <20040113184810.GS19309@baldur.asgard> Mail-Followup-To: freebsd-mobile@freebsd.org References: <20040111195849.GP19309@baldur.asgard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040111195849.GP19309@baldur.asgard> User-Agent: Mutt/1.4i Subject: Re: T40p - good choice for running FBSD? 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, 13 Jan 2004 18:48:16 -0000 Thanks for all helpful comments! Today I've ordered a T41p. I'm curious about it. Regards, Andreas From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 10:52:48 2004 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 3CFB316A4CE for ; Tue, 13 Jan 2004 10:52:48 -0800 (PST) Received: from wolfe.bbn.com (wolfe.bbn.com [128.89.80.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF82E43D3F for ; Tue, 13 Jan 2004 10:52:31 -0800 (PST) (envelope-from gdt@bbn.com) Received: from wolfe.bbn.com (localhost [127.0.0.1]) by wolfe.bbn.com (Postfix) with ESMTP id 22FBC2051D; Tue, 13 Jan 2004 13:52:31 -0500 (EST) To: Rui Li References: <20040112070640.87077.qmail@web40808.mail.yahoo.com> From: Greg Troxel In-Reply-To: <20040112070640.87077.qmail@web40808.mail.yahoo.com> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Jan 2004 13:52:31 -0500 Sender: gdt@bbn.com Message-Id: <20040113185231.22FBC2051D@wolfe.bbn.com> cc: freebsd-mobile@freebsd.org Subject: Re: PCCARD unrecogonized by FreeBSD 5.1-RELEASE on IBM Thinkpad 600 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, 13 Jan 2004 18:52:48 -0000 You have mangled the dmesg output by linewrapping it. Please try to avoid this. I have a 600 (2645-41U), and run NetBSD on it, but I think my NetBSD experience will be helpful. The key point is that the irq for the cbb was unconfigured, and the kernel patched it to 11, and then everything was fine. If I don't try to use the cbb, and let the kernel probe the pcmcia controller in ISA mode, all works fine (with 16-bit cards). Probing cbb, I get a problem with "unconfigured IRQ". Turning on various PCIBIOS options (in NetBSD), I found that the IRQ in the PIR was set to -1, which means that the BIOS failed to configure the device properly. I set a PCIBIOS_FIXUP_INTR option (actually many): options PCIBIOS # PCI BIOS support options PCIBIOSVERBOSE # PCI BIOS verbose info options PCIBIOS_ADDR_FIXUP # fixup PCI I/O addresses options PCIBIOS_BUS_FIXUP # fixup PCI bus numbering options PCIBIOS_INTR_FIXUP # fixup PCI interrupt routing options PCIBIOS_IRQS_HINT=0x0a00 # PCI interrupts hint. IRQ 9 or 11 options PCIBIOS_INTR_GUESS # see pcibios(4) The kernel then patched the irq: BIOS32 rev. 0 found at 0xfd820 PCI BIOS rev. 2.1 found at 0xfd880 pcibios: config mechanism [1][x], special cycles [1][x], last bus 6 PCI IRQ Routing Table rev. 1.0 found at 0xf9e10, size 96 bytes (4 entries) PCI Interrupt Router at 000:07:0 PCI Exclusive IRQs: 11 PIR Entry 0: Bus: 0 Device: 7 INTA: link 0x60 bitmap 0xdef8 INTB: link 0x00 bitmap 0x0000 INTC: link 0x00 bitmap 0x0000 INTD: link 0x63 bitmap 0xdef8 PIR Entry 1: Bus: 0 Device: 2 INTA: link 0x60 bitmap 0xdef8 INTB: link 0x61 bitmap 0xdef8 INTC: link 0x00 bitmap 0x0000 INTD: link 0x00 bitmap 0x0000 PIR Entry 2: Bus: 0 Device: 3 INTA: link 0x60 bitmap 0xdef8 INTB: link 0x00 bitmap 0x0000 INTC: link 0x00 bitmap 0x0000 INTD: link 0x00 bitmap 0x0000 PIR Entry 3: Bus: 0 Device: 4 INTA: link 0x60 bitmap 0xdef8 INTB: link 0x61 bitmap 0xdef8 INTC: link 0x62 bitmap 0xdef8 INTD: link 0x63 bitmap 0xdef8 pciintr_link_fixup: PIRQ 0x00 already connected to IRQ 11 pciintr_link_fixup: PIRQ 0x03 already connected to IRQ 11 pciintr_link_fixup: PIRQ 0x01 already connected to IRQ 11 pciintr_link_fixup: PIRQ 0x02 not connected pciintr_link_fixup (stage 2): assigning IRQ 11 to PIRQ 0x02 pciintr_link_route: route of PIRQ 0x00 -> IRQ 11 preserved BIOS setting pciintr_link_route: route of PIRQ 0x03 -> IRQ 11 preserved BIOS setting pciintr_link_route: route of PIRQ 0x01 -> IRQ 11 preserved BIOS setting ------------------------------------------ device vendor product pin PIRQ IRQ stage ------------------------------------------ 000:02:0 0x104c 0xac16 A 0x00 11 0 fixed up 000:02:1 0x104c 0xac16 B 0x01 11 0 fixed up 000:03:0 0x10c8 0x0004 A 0x00 11 0 already assigned 000:07:2 0x8086 0x7112 D 0x03 11 0 already assigned ------------------------------------------ PCI fixup examining 8086:7192 PCI fixup examining 104c:ac16 PCI bridge 0: primary 0, secondary 1, subordinate 1 PCI fixup examining 104c:ac16 PCI bridge 1: primary 0, secondary 2, subordinate 2 PCI fixup examining 10c8:04 PCI fixup examining 8086:7110 PCI fixup examining 8086:7111 PCI fixup examining 8086:7112 PCI fixup examining 8086:7113 PCI bus #2 is the last bus Then, cbb0/1 were attached ok: cbb0 at pci0 dev 2 function 0: Texas Instruments PCI1250 PCI-CardBus Bridge (rev. 0x02) (chipflags 3) cbb0: socket base address 0x20301000 cbb0: intrpin A, intrtag 11 cbb1 at pci0 dev 2 function 1: Texas Instruments PCI1250 PCI-CardBus Bridge (rev. 0x02) (chipflags 3) cbb1: socket base address 0x20300000 cbb1: intrpin B, intrtag 11 CardBus latency timer 0xb0 (b0010100) PCI latency timer 0xa8 (82a808) pccbb_power: CARDBUS_VCC_0V and CARDBUS_VPP_0V [44] cbb0: interrupting at irq 11 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 1 device 0 pcmcia0 at cardslot0 and finally: ex0 at cardbus1 dev 0 function 0: 3Com 3c575B-TX Ethernet Also a 16-bit card works too. -- Greg Troxel From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 10:55:41 2004 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 CF21816A4CE for ; Tue, 13 Jan 2004 10:55:41 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49E4743D64 for ; Tue, 13 Jan 2004 10:55:36 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com) by ran.psg.com with esmtp (Exim 4.24; FreeBSD) id 1AgThP-0006N9-GR; Tue, 13 Jan 2004 10:55:35 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Sam Leffler References: <16248.58260.560180.809655@canoe.dclg.ca> <16387.58499.587197.601294@canoe.dclg.ca> <200401130940.23993.sam@errno.com> <200401130948.06429.sam@errno.com> Message-Id: Date: Tue, 13 Jan 2004 10:55:35 -0800 cc: freebsd-mobile@freebsd.org Subject: Re: ATH driver doesn't associate with turbo. 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, 13 Jan 2004 18:55:41 -0000 it seems mode 11b is preferred. if i boot in the presense of both kinds of APs, it seems to choose the 11b. i can then say ifconfig ath0 mode 11a and it will happily switch to 11a ( and to with turbo. real wireless users eat turbot for lunch :-) randy From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 11:32:09 2004 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 ECE8416A4CE for ; Tue, 13 Jan 2004 11:32:09 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47D5943D72 for ; Tue, 13 Jan 2004 11:31:56 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id i0DJVtHQ029657 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 13 Jan 2004 11:31:55 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: Randy Bush Date: Tue, 13 Jan 2004 11:36:10 -0800 User-Agent: KMail/1.5.3 References: <16248.58260.560180.809655@canoe.dclg.ca> <200401130948.06429.sam@errno.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401131136.10692.sam@errno.com> cc: freebsd-mobile@freebsd.org Subject: Re: ATH driver doesn't associate with turbo. 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, 13 Jan 2004 19:32:10 -0000 On Tuesday 13 January 2004 10:55 am, Randy Bush wrote: > it seems mode 11b is preferred. if i boot in the presense > of both kinds of APs, it seems to choose the 11b. i can > then say > > ifconfig ath0 mode 11a > > and it will happily switch to 11a 11b is not preferred. AP selection is done according to various criteria like compatibility (e.g. station wants WEP and AP is using WEP). If you do ifconfig ath0 debug you will see what's going on. The AP with the best rssi is typically selected. To lock on to a particular AP you have to steer the algorithm by constraining the choices. This issue comes up often--it would be great if there were a connection between the 802.11 layer and a user app that would help users select an AP based on scan results but I don't know of anything like this for *bsd. Windows users are used to have a "site survey" app that does a scan and presents a list of AP's to choose. Sam From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 13 14:54:04 2004 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 0F7CB16A4CE for ; Tue, 13 Jan 2004 14:54:04 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16EBC43D41 for ; Tue, 13 Jan 2004 14:53:59 -0800 (PST) (envelope-from freebsd-mobile@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AgXQ5-0002xk-00 for ; Tue, 13 Jan 2004 23:53:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-mobile@freebsd.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AgXQ3-0002xc-00 for ; Tue, 13 Jan 2004 23:53:55 +0100 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AgXQ3-0007XV-00 for ; Tue, 13 Jan 2004 23:53:55 +0100 From: Jesse Guardiani Date: Tue, 13 Jan 2004 17:53:52 -0500 Organization: WingNET Lines: 664 Message-ID: References: <20040110.172705.107216603.imp__30021.5326635682$1073780875@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: Subset of power patch: subtractive decoding X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2004 22:54:04 -0000 M. Warner Losh wrote: > I've teased out the subtractive bridge decoding patches from the > larger power patches. Please test them and let me know how things > go. This eliminates hw.pci.allow_unsupported_io_range by fixing the > underlying problem this was kludging around. Please test it and let > me know how it is working for you. It should only make things better, > and make nothing worse. > > This won't fix the other problems that the more complete power patches > attempt to fix. > > http://people.freebsd.org/~imp/pci-subtractive.diff > > Warner > _______________________________________________ > 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" Well, on my IBM A30p this patch mostly works. However, if I try to boot with my pcmcia 56k 3Com Megahertz 3CXM756 installed the machine hangs. In fact, if I insert the card after a successfull boot the machine hangs, but removing the card immediately fixes the hang. Here's the message it prints before it hangs: pcib2: device pccard0 requested decoded memory range 0xc0200000-0xcfffffff And here's my verbose dmesg.boot: 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.2-RC1 #1: Tue Jan 13 17:06:09 EST 2004 jesse@trevarthan.int.wingnet.net:/usr/src/sys/i386/compile/TREVARTHAN Preloaded elf kernel "/boot/kernel/kernel" at 0xc086c000. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc086c278. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc086c324. Preloaded elf module "/boot/kernel/apm.ko" at 0xc086c3d0. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc086c478. Calibrating clock(s) ... i8254 clock: 1193165 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1198987285 Hz CPU: Intel(R) Pentium(R) III Mobile CPU 1200MHz (1198.99-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383f9ff real memory = 402063360 (383 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c26000 - 0x000000001788bfff, 382099456 bytes (93286 pages) avail memory = 380850176 (363 MB) bios32: Found BIOS32 Service Directory header at 0xc00f7420 bios32: Entry = 0xfd7e0 (c00fd7e0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd770+0x18e pnpbios: Found PnP BIOS data at 0xc00f7480 pnpbios: Entry = f0000:a15c Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: wlan: <802.11 Link Layer> null: random: mem: Pentium Pro MTRR support enabled npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: Other PM system enabled. pci_open(1): mode 1 addr port (0x0cf8) is 0x8000f904 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=35758086) pcibios: BIOS version 2.10 Using $PIR table, 14 entries at 0xc00fdeb0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 0 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 0 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 0 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 2 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 2 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 1 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 1 0 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 2 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 2 0 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 2 0 C 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 1 2 2 A 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 1 2 2 B 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 D 0x63 3 4 5 6 7 9 10 11 12 14 15 slot 2 9 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 slot 2 9 0 B 0x61 3 4 5 6 7 9 10 11 12 14 15 slot 2 9 0 C 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 2 9 0 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 9 1 A 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 9 2 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 9 2 B 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 8 A 0x68 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 B 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 D 0x6b 3 4 5 6 7 9 10 11 12 14 15 embedded 0 31 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 31 B 0x61 3 4 5 6 7 9 10 11 12 14 15 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 pcib0: at pcibus 0 on motherboard pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base d0000000, size 28, enabled found-> vendor=0x8086, dev=0x3575, revid=0x02 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3576, revid=0x02 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x60 (2880 ns), mingnt=0x0c (3000 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00001800, size 5, enabled pci_cfgintr_valid: BIOS irq 9 is valid pci_cfgintr: 0:29 INTA BIOS irq 9 found-> vendor=0x8086, dev=0x2482, revid=0x01 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 map[20]: type 4, range 32, base 00001820, size 5, enabled pci_cfgintr_valid: BIOS irq 11 is valid pci_cfgintr: 0:29 INTB BIOS irq 11 found-> vendor=0x8086, dev=0x2484, revid=0x01 bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[20]: type 4, range 32, base 00001840, size 5, enabled pci_cfgintr_valid: BIOS irq 9 is valid pci_cfgintr: 0:29 INTC BIOS irq 9 found-> vendor=0x8086, dev=0x2487, revid=0x01 bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=9 found-> vendor=0x8086, dev=0x2448, revid=0x41 bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x248c, revid=0x01 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 4, range 32, base 000001f0, size 3, enabled map[14]: type 4, range 32, base 000003f4, size 2, enabled map[18]: type 4, range 32, base 00000170, size 3, enabled map[1c]: type 4, range 32, base 00000374, size 2, enabled map[20]: type 4, range 32, base 00001860, size 4, enabled found-> vendor=0x8086, dev=0x248a, revid=0x01 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type 4, range 32, base 00001880, size 5, enabled pci_cfgintr_valid: BIOS irq 5 is valid pci_cfgintr: 0:31 INTB BIOS irq 5 found-> vendor=0x8086, dev=0x2483, revid=0x01 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[10]: type 4, range 32, base 00001c00, size 8, port disabled map[14]: type 4, range 32, base 000018c0, size 6, enabled pci_cfgintr_valid: BIOS irq 5 is valid pci_cfgintr: 0:31 INTB BIOS irq 5 found-> vendor=0x8086, dev=0x2485, revid=0x01 bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[10]: type 4, range 32, base 00002400, size 8, port disabled map[14]: type 4, range 32, base 00002000, size 7, enabled pci_cfgintr_valid: BIOS irq 5 is valid pci_cfgintr: 0:31 INTB BIOS irq 5 found-> vendor=0x8086, dev=0x2486, revid=0x01 bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 agp0: mem 0xd0000000-0xdfffffff at device 0.0 on pci0 agp0: allocating GATT for aperture of size 228M pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x3000-0x3fff pcib1: memory decode 0xc0100000-0xc01fffff pcib1: prefetched decode 0xe0000000-0xe7ffffff pci1: on pcib1 pci1: physical bus=1 map[10]: type 3, range 32, base e0000000, size 27, enabled map[14]: type 4, range 32, base 00003000, size 8, enabled map[18]: type 1, range 32, base c0100000, size 16, enabled pci_cfgintr_valid: BIOS irq 9 is valid pci_cfgintr: 1:0 INTA BIOS irq 9 found-> vendor=0x1002, dev=0x4c59, revid=0x00 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0387, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x42 (1980 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 2 supports D0 D1 D2 D3 current D0 pci1: at device 0.0 (no driver attached) uhci0: port 0x1800-0x181f irq 9 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 ums0: Logitech USB Receiver, rev 1.10/16.00, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. uhci2: port 0x1840-0x185f irq 9 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 pcib2: secondary bus 2 pcib2: subordinate bus 8 pcib2: I/O decode 0x4000-0x8fff pcib2: memory decode 0xc0200000-0xcfffffff pcib2: prefetched decode 0xe8000000-0xf00fffff pcib2: Subtractively decoded bridge. pci2: on pcib2 pci2: physical bus=2 map[10]: type 1, range 32, base 50000000, size 12, enabled pci_cfgintr_valid: BIOS irq 9 is valid pci_cfgintr: 2:0 INTA BIOS irq 9 found-> vendor=0x1180, dev=0x0478, revid=0xa0 bus=2, slot=0, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0107, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=9 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 50100000, size 12, enabled pci_cfgintr_valid: BIOS irq 5 is valid pci_cfgintr: 2:0 INTB BIOS irq 5 found-> vendor=0x1180, dev=0x0478, revid=0xa0 bus=2, slot=0, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0107, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns) intpin=b, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base c0201000, size 11, enabled pci_cfgintr_valid: BIOS irq 9 is valid pci_cfgintr: 2:0 INTC BIOS irq 9 found-> vendor=0x1180, dev=0x0522, revid=0x00 bus=2, slot=0, func=2 class=0c-00-10, hdrtype=0x00, mfdev=1 cmdreg=0x0106, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x02 (500 ns), maxlat=0x04 (1000 ns) intpin=c, irq=9 powerspec 2 supports D0 D3 current D0 map[10]: type 3, range 32, base f0000000, size 12, enabled pci_cfgintr_valid: BIOS irq 9 is valid pci_cfgintr: 2:2 INTA BIOS irq 9 found-> vendor=0x1260, dev=0x3873, revid=0x01 bus=2, slot=2, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base c0200000, size 12, enabled map[14]: type 4, range 32, base 00008000, size 6, enabled pci_cfgintr_valid: BIOS irq 10 is valid pci_cfgintr: 2:8 INTA BIOS irq 10 found-> vendor=0x8086, dev=0x1031, revid=0x41 bus=2, slot=8, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x42 (1980 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 cbb0: mem 0x50000000-0x50000fff irq 9 at device 0.0 on pci2 pcib2: device cbb0 requested decoded memory range 0x50000000-0x50000fff cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [MPSAFE] cbb0: PCI Configuration space: 0x00: 0x04781180 0x02100107 0x060700a0 0x00824000 0x10: 0x50000000 0x020000dc 0xb0050302 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x07000109 0x40: 0x01841014 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x04800001 0x00000000 0x04630464 0x00000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x000a0000 0x00000000 0x00f00000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x01841014 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 cbb1: mem 0x50100000-0x50100fff irq 5 at device 0.1 on pci2 pcib2: device cbb1 requested decoded memory range 0x50100000-0x50100fff cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 cbb1: [MPSAFE] cbb1: PCI Configuration space: 0x00: 0x04781180 0x02100107 0x060700a0 0x00824000 0x10: 0x50100000 0x020000dc 0xb0080602 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x07000205 0x40: 0x01841014 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x04800001 0x00000000 0x04630464 0x00000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x000a0000 0x00000000 0x00f00000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x01841014 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 pci2: at device 0.2 (no driver attached) wi0: mem 0xf0000000-0xf0000fff irq 9 at device 2.0 on pci2 pcib2: device wi0 requested decoded memory range 0xf0000000-0xf0000fff wi0: 802.11 address: 00:20:e0:8a:90:61 wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.2) wi0: bpf attached wi0: bpf attached wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wi0: bpf attached fxp0: port 0x8000-0x803f mem 0xc0200000-0xc0200fff irq 10 at device 8.0 on pci2 pcib2: device fxp0 requested decoded memory range 0xc0200000-0xc0200fff fxp0: using memory space register mapping fxp0: Ethernet address 00:d0:59:aa:70:ec fxp0: PCI IDs: 8086 1031 1014 0209 0041 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached 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: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 mask=03 stat0=50 stat1=00 devices=0x1 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1-master: stat=0x00 err=0x01 lsb=0x14 msb=0xeb ata1-slave: stat=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 mask=03 stat0=00 stat1=00 devices=0xc ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] ichsmb0: port 0x1880-0x189f irq 5 at device 31.3 on pci0 smbus0: on ichsmb0 smb0: on smbus0 pcm0: port 0x18c0-0x18ff,0x1c00-0x1cff irq 5 at device 31.5 on pci0 pcm0: pcm0: Codec features headphone, 20 bit DAC, 18 bit ADC, 6 bit master volume, Crystal Semi 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, AMAP pcm0: sndbuf_setmap 2c1000, 4000; 0xe38ed000 -> 2c1000 pcm0: sndbuf_setmap 2c5000, 4000; 0xe38f1000 -> 2c5000 pci0: at device 31.6 (no driver attached) eisa0: on motherboard eisa0: unknown card @H@0000 (0x01000000) at slot 1 pnpbios: 23 devices, largest 238 bytes PNP0c02: adding io range 0x10-0x1f, size=0x10, align=0x1 PNP0c02: adding io range 0x24-0x25, size=0x2, align=0x1 PNP0c02: adding io range 0x28-0x29, size=0x2, align=0x1 PNP0c02: adding io range 0x2c-0x2d, size=0x2, align=0x1 PNP0c02: adding io range 0x30-0x31, size=0x2, align=0x1 PNP0c02: adding io range 0x34-0x35, size=0x2, align=0x1 PNP0c02: adding io range 0x38-0x39, size=0x2, align=0x1 PNP0c02: adding io range 0x3c-0x3d, size=0x2, align=0x1 PNP0c02: adding io range 0x50-0x53, size=0x4, align=0x1 PNP0c02: adding io range 0x72-0x73, size=0x2, align=0x1 PNP0c02: adding io range 0x74-0x75, size=0x2, align=0x1 PNP0c02: adding io range 0x76-0x77, size=0x2, align=0x1 PNP0c02: adding io range 0x80-0x80, size=0x1, align=0x1 PNP0c02: adding io range 0x90-0x91, size=0x2, align=0x1 PNP0c02: adding io range 0x92-0x92, size=0x1, align=0x1 PNP0c02: adding io range 0x93-0x9f, size=0xd, align=0x1 PNP0c02: adding io range 0xa4-0xa5, size=0x2, align=0x1 PNP0c02: adding io range 0xa8-0xa9, size=0x2, align=0x1 PNP0c02: adding io range 0xac-0xad, size=0x2, align=0x1 PNP0c02: adding io range 0xb0-0xb1, size=0x2, align=0x1 PNP0c02: adding io range 0xb2-0xb3, size=0x2, align=0x1 PNP0c02: adding io range 0xb4-0xb5, size=0x2, align=0x1 PNP0c02: adding io range 0xb8-0xb9, size=0x2, align=0x1 PNP0c02: adding io range 0xbc-0xbd, size=0x2, align=0x1 PNP0c02: adding io range 0x15e0-0x15ef, size=0x10, align=0x8 PNP0c02: adding io range 0x1600-0x167f, size=0x80, align=0x8 PNP0c02: adding fixed memory32 range 0xffc00000-0xffffffff, size=0x400000 pnpbios: handle 1 device ID PNP0c02 (020cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xe0000-0xfffff, size=0x20000 PNP0c01: adding fixed memory32 range 0x100000-0x17ffffff, size=0x17f00000 pnpbios: handle 2 device ID PNP0c01 (010cd041) PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 pnpbios: handle 3 device ID PNP0200 (0002d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: adding irq mask 0x1 pnpbios: handle 5 device ID PNP0100 (0001d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 PNP0b00: adding irq mask 0x100 pnpbios: handle 6 device ID PNP0b00 (000bd041) PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: adding irq mask 0x2 pnpbios: handle 7 device ID PNP0303 (0303d041) PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 pnpbios: handle 8 device ID PNP0c04 (040cd041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 pnpbios: handle 9 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 pnpbios: handle 10 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0c02: adding io range 0x1000-0x105f, size=0x60, align=0x1 PNP0c02: adding io range 0x1060-0x107f, size=0x20, align=0x1 PNP0c02: adding io range 0x1180-0x11bf, size=0x40, align=0x1 pnpbios: handle 11 device ID PNP0c02 (020cd041) INT0800: adding fixed memory32 range 0xffb80000-0xffbfffff, size=0x80000 INT0800: adding fixed memory32 range 0xffb00000-0xffb7ffff, size=0x80000 INT0800: adding fixed memory32 range 0xffa80000-0xffafffff, size=0x80000 INT0800: adding fixed memory32 range 0xffa00000-0xffa7ffff, size=0x80000 INT0800: adding fixed memory32 range 0xff980000-0xff9fffff, size=0x80000 INT0800: adding fixed memory32 range 0xff900000-0xff97ffff, size=0x80000 INT0800: adding fixed memory32 range 0xff880000-0xff8fffff, size=0x80000 INT0800: adding fixed memory32 range 0xff800000-0xff87ffff, size=0x80000 INT0800: adding fixed memory32 range 0xff000000-0xff07ffff, size=0x80000 pnpbios: handle 12 device ID INT0800 (0008d425) PNP0c02: adding memory32 range 0xdc000-0xdffff, size=0x4000, align=0x4000 pnpbios: handle 13 device ID PNP0c02 (020cd041) pnpbios: handle 14 device ID PNP0c02 (020cd041) PNP0c02: adding fixed memory32 range 0xd2000-0xd3fff, size=0x2000 pnpbios: handle 15 device ID PNP0c02 (020cd041) PNP0680: adding io range 0x1f0-0x1f7, size=0x8, align=0x1 PNP0680: adding io range 0x3f6-0x3f6, size=0x1, align=0x1 PNP0680: adding irq mask 0x4000 PNP0680: adding io range 0x1860-0x1867, size=0x8, align=0x1 pnpbios: handle 16 device ID PNP0680 (8006d041) PNP0680: adding io range 0x170-0x177, size=0x8, align=0x1 PNP0680: adding io range 0x376-0x376, size=0x1, align=0x1 PNP0680: adding irq mask 0x8000 PNP0680: adding io range 0x1868-0x186f, size=0x8, align=0x1 pnpbios: handle 17 device ID PNP0680 (8006d041) IBM3780: adding irq mask 0x1000 pnpbios: handle 18 device ID IBM3780 (80374d24) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x10 pnpbios: handle 19 device ID PNP0501 (0105d041) IBM0071: adding dma mask 0x8 IBM0071: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 IBM0071: adding irq mask 0x8 pnpbios: handle 20 device ID IBM0071 (71004d24) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 pnpbios: handle 21 device ID PNP0700 (0007d041) PNP0400: adding io range 0x3bc-0x3bf, size=0x4, align=0x4 PNP0400: adding irq mask 0x80 pnpbios: handle 23 device ID PNP0400 (0004d041) pnpbios: handle 26 device ID PNP0e03 (030ed041) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: