From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 22 06:57:49 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 6114216A41F for ; Sun, 22 Jan 2006 06:57:49 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF42143D45 for ; Sun, 22 Jan 2006 06:57:48 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k0M6uwVV075943; Sat, 21 Jan 2006 23:57:00 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 21 Jan 2006 23:57:15 -0700 (MST) Message-Id: <20060121.235715.81670800.imp@bsdimp.com> To: eric@schultznet.ca From: "M. Warner Losh" In-Reply-To: References: <20050913095341.GA52017@r0ck.mine.nu> <200509131634.52067.tijl@ulyssis.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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sat, 21 Jan 2006 23:57:00 -0700 (MST) Cc: freebsd-mobile@freebsd.org Subject: Re: Toshiba ToPIC95B not working on 6.0-BETA4 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2006 06:57:49 -0000 In message: Storkman writes: : Tijl Coosemans ulyssis.org> writes: : > : > I used to have a 480CDT which has the same controller. Support for it : > has always been troublesome, but I think it works in FreeBSD 5.x. : > Otherwise PCIC mode should work, but then you need the OLDCARD kernel : > and I'm not sure if FreeBSD 6 still has that. Try compiling a kernel : > without : > : > device cbb : > device pccard : > device cardbus : > : > and instead use : > : > device card : > device pcic : > : > You also need to add 'pccard_enable="YES"' to /etc/rc.conf and since : > you're using a NIC you also have to setup 'pccard_ifconfig'. : : Good afternoon... : : I've got a Toshiba Satellite 2140CDS with the same controller. My problem is : that the ethernet card I use (a 3Com 575) is recognized, get's a DHCP address : (not quickly, but after a few tries), but then can NOT do anything (i.e.: can't : ping, nslookup can't connect to a server, other hosts cannot ping it). : : There is a related thread at BSD forums: : http://www.freebsdforums.org/forums/showthread.php?t=37600 : : My floppy drive is not working either, and I only got my thumbdrive back today : so hopefully I will able to get some info off the machine for further analysis. : : In the BIOS I have set the controller to CardBus because of a tip I read for : (excuse me) Win 95. I will try PCIC tonight/this weekend. : : But I also noticed in man pccbb that the controller was explicitly listed. So : is there a way I can get the kernel to use that driver? If it is a driver?! Or : am up the wrong tree? xl has some issues in releng_6 that have been fixed in -current. These problems were in resource allocation in the pci code. Other cardbus cards won't be affected. Warner From owner-freebsd-mobile@FreeBSD.ORG Sun Jan 22 20:09:57 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 5969816A420 for ; Sun, 22 Jan 2006 20:09:57 +0000 (GMT) (envelope-from eric@schultznet.ca) Received: from dfw002.8inet.com (dfw002.8inet.com [72.232.12.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA32C43D4C for ; Sun, 22 Jan 2006 20:09:56 +0000 (GMT) (envelope-from eric@schultznet.ca) Received: from slip-129-37-171-45.on.ca.prserv.net ([129.37.171.45]) by dfw002.8inet.com with esmtpa (Exim 4.52) id 1F0lX9-0007Mb-ON; Sun, 22 Jan 2006 15:09:56 -0500 Message-ID: <43D3E690.2050901@schultznet.ca> Date: Sun, 22 Jan 2006 15:09:52 -0500 From: Eric Schultz Organization: SchultzNet.ca User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-mobile@freebsd.org References: <20050913095341.GA52017@r0ck.mine.nu> <200509131634.52067.tijl@ulyssis.org> <20060121.235715.81670800.imp@bsdimp.com> In-Reply-To: <20060121.235715.81670800.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PopBeforeSMTPSenders: eric@cameron-schultz.ca,eric@schultznet.ca,schultzn X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - dfw002.8inet.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - schultznet.ca X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: Re: Toshiba ToPIC95B not working on 6.0-BETA4 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2006 20:09:57 -0000 M. Warner Losh wrote: > xl has some issues in releng_6 that have been fixed in -current. > These problems were in resource allocation in the pci code. Other > cardbus cards won't be affected. > Good afternoon... interesting, although without network connectivity I image getting any part of -current would be difficult. I'm also getting the results with a 3Com 3CCFE574BT card (ep driver). Am I way off base thinking I need to get the pccbb driver working instead of other (?) cardbus bridge drivers for my ToPIC95B? -- Headed for the second star to the right and straight on 'til morning... Eric Schultz (aka Storkman) Photos: http://community.webshots.com/user/schultznet Homepage: http://www.schultznet.ca Blog: http://schultznet.blogspot.com/ Using Mozilla's revolutionary e-mail client: http://www.mozilla.org/products/thunderbird/ Using SquirrelMail's revolutionary e-mail client: http://www.squirrelmail.org/ From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 23 04:11:13 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 98F6316A420 for ; Mon, 23 Jan 2006 04:11:13 +0000 (GMT) (envelope-from davidski@deadheaven.com) Received: from geoff.deadheaven.com (geoff.deadheaven.com [216.162.200.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id E945243D49 for ; Mon, 23 Jan 2006 04:11:12 +0000 (GMT) (envelope-from davidski@deadheaven.com) Received: by geoff.deadheaven.com (Postfix, from userid 1001) id 880D91567D2F; Sun, 22 Jan 2006 20:11:39 -0800 (PST) Date: Sun, 22 Jan 2006 20:11:39 -0800 From: "David F. Severski" To: freebsd-mobile@freebsd.org Message-ID: <20060123041139.GB69091@geoff.deadheaven.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: Debugging ath device timeouts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 04:11:13 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Under 6-STABLE, I am encountering intermittent timeouts with an ath device= =20 (Netgear WG311T). Beyond compiling and running 80211watch and 80211stats, I'm at a loss as to where I should be looking to try to track down this problem. Search through the archives for this error don't seem to point at a consistent area within the stack to look for a culprit. Any suggestions as to what could be causing this error? David --uname -a FreeBSD geoff.deadheaven.com 6.0-STABLE FreeBSD 6.0-STABLE #14: Fri Jan 20 11:21:35 PST 2006 root@geoff.deadheaven.com:/usr/obj/usr/src/sys/GEOFF_IP6 i386 --80211watch Sun Jan 22 10:40:48 RTM_IEEE80211: replay failure: src 00:13:ce:56:34:61 dst 00:0f:b5:fb:f6:b4 cipher 3 keyix 4 keyrsc 51064 rsc 51064 Sun Jan 22 10:40:49 RTM_IEEE80211: replay failure: src 00:13:ce:56:34:61 dst 00:0f:b5:fb:f6:b4 cipher 3 keyix 4 keyrsc 51942 rsc 51942 Sun Jan 22 10:41:22 RTM_IEEE80211: replay failure: src 00:13:ce:56:34:61 dst 00:0f:b5:fb:f6:b4 cipher 3 keyix 4 keyrsc 67719 rsc 67719 Sun Jan 22 10:41:40 RTM_IEEE80211: replay failure: src 00:13:ce:56:34:61 dst 00:0f:b5:fb:f6:b4 cipher 3 keyix 4 keyrsc 77014 rsc 77014 Sun Jan 22 10:41:46 RTM_IEEE80211: replay failure: src 00:13:ce:56:34:61 dst 00:0f:b5:fb:f6:b4 cipher 3 keyix 4 keyrsc 79591 rsc 79591 --80211stats 1040 rx discard 'cuz dup 30 rx beacon frames 37 rx element unknown 19 rx frame chan mismatch 3737 rx frame ssid mismatch 115688 rx discard 'cuz port unauthorized 5 rx seq# violation (CCMP) 1 active scans started 2 passive scans started --/var/log/messages Jan 22 10:38:42 geoff kernel: ath0: device timeout --dmesg ath0: mem 0xf4110000-0xf411ffff irq 9 at device 16.0 on pci0 ath0: Ethernet address: 00:0f:b5:fb:f6:b4 ath0: mac 7.9 phy 4.5 radio 5.6 --/etc/hostapd.conf interface=3Dath0 driver=3Dbsd logger_syslog=3D-1 logger_syslog_level=3D2 logger_stdout=3D-1 logger_stdout_level=3D-1 dump_file=3D/tmp/hostapd.dump ctrl_interface=3D/var/run/hostapd ctrl_interface_group=3Dwheel ssid=3DDeadheaven wpa=3D1 wpa_passphrase=3D wpa_key_mgmt=3DWPA-PSK wpa_pairwise=3DCCMP --pciconf -lv ath0@pci0:16:0: class=3D0x020000 card=3D0x5a001385 chip=3D0x0013168c rev=3D= 0x01 hdr=3D0x00 vendor =3D 'Atheros Communications Inc.' device =3D 'AR5212, AR5213 802.11a/b/g Wireless Adapter' class =3D network subclass =3D ethernet --ifconfig ath0 ath0: flags=3D8843 mtu 2290 inet6 fe80::20f:b5ff:fefb:f6b4%ath0 prefixlen 64 scopeid 0x2 inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:0f:b5:fb:f6:b4 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: associated ssid Deadheaven channel 2 bssid 00:0f:b5:fb:f6:b4 authmode WPA privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-b= it txpowmax 0 protmode CTS burst ssid HIDE=20 dtimperiod 1 bintval 100 --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkPUV3sACgkQlTJ+DI1JK1vceQCdEAaKeWEJd5OUTYylVc0iBiyP Y9gAn0m93zplM2gtzI2nXKhfBjSCQD2f =Dmp3 -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 23 14:52:43 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 AEC7316A420 for ; Mon, 23 Jan 2006 14:52:42 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from natsmtp00.rzone.de (natsmtp00.rzone.de [81.169.145.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E81F43D6A for ; Mon, 23 Jan 2006 14:52:23 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from athena.laverenz.de (p5480C002.dip.t-dialin.net [84.128.192.2]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id k0NEqLiU029853 for ; Mon, 23 Jan 2006 15:52:21 +0100 (MET) Received: from localhost (localhost.localdomain [127.0.0.1]) by athena.laverenz.de (Postfix) with ESMTP id 0611FE379FDD for ; Mon, 23 Jan 2006 15:52:21 +0100 (CET) Received: from athena.laverenz.de ([127.0.0.1]) by localhost (athena [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17549-05 for ; Mon, 23 Jan 2006 15:52:19 +0100 (CET) Received: by athena.laverenz.de (Postfix, from userid 2000) id 8B512E379FD0; Mon, 23 Jan 2006 15:52:19 +0100 (CET) Date: Mon, 23 Jan 2006 15:52:19 +0100 From: Uwe Laverenz To: freebsd-mobile@freebsd.org Message-ID: <20060123145219.GF17465@laverenz.de> Mail-Followup-To: freebsd-mobile@freebsd.org References: <20060123041139.GB69091@geoff.deadheaven.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060123041139.GB69091@geoff.deadheaven.com> Organization: private site Sender: uwe@laverenz.de User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at laverenz.de Subject: Re: Debugging ath device timeouts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 14:52:43 -0000 On Sun, Jan 22, 2006 at 08:11:39PM -0800, David F. Severski wrote: > 80211stats, I'm at a loss as to where I should be looking to try to track > down this problem. Search through the archives for this error don't seem > to point at a consistent area within the stack to look for a culprit. Several people with different chipsets/drivers (iwi, ath, ral...) seem to have this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/88793 > Any suggestions as to what could be causing this error? I guess it could be a bug in wpa_supplicant, I started the following session with "wpa_supplicant -i iwi0 -c /etc/wpa_supplicant.conf -d": --- log --- [...] WPA: RX message 1 of Group Key Handshake from 00:13:49:12:02:29 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=1 tx=0). WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP addr=ff:ff:ff:ff:ff:ff key_idx=1 set_tx=0 seq_l en=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Key negotiation completed with 00:13:49:12:02:29 [PTK=TKIP GTK=TKIP] Cancelling authentication timeout EAPOL: External notification - portValid=1 EAPOL: External notification - EAP success=1 EAPOL: SUPP_PAE entering state AUTHENTICATING EAPOL: SUPP_BE entering state SUCCESS EAPOL: SUPP_PAE entering state AUTHENTICATED EAPOL: SUPP_BE entering state IDLE [...several minutes connection ok...] RX EAPOL from 00:13:49:12:02:29 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=127 EAPOL-Key type=254 WPA: RX message 1 of Group Key Handshake from 00:13:49:12:02:29 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=1 tx=0). WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP addr=ff:ff:ff:ff:ff:ff key_idx=1 set_tx=0 seq_len=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Group rekeying completed with 00:13:49:12:02:29 [GTK=TKIP] [...connection still ok...] RX EAPOL from 00:13:49:12:02:29 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=95 EAPOL-Key type=254 WPA: RX message 1 of 4-Way Handshake from 00:13:49:12:02:29 (ver=1) WPA: Renewed SNonce - hexdump(len=32): d3 d6 43 c2 48 d3 a4 1b a7 fd ee 55 49 c2 c6 b9 8c 24 1d 8c 33 b5 fe ea 23 cc ff 23 71 8e 54 7b WPA: PMK - hexdump(len=32): [REMOVED] WPA: PTK - hexdump(len=64): [REMOVED] WPA: EAPOL-Key MIC - hexdump(len=16): 34 01 ba 96 f7 c1 40 08 0d 00 ec f0 3a d9 38 b7 WPA: Sending EAPOL-Key 2/4 RX EAPOL from 00:13:49:12:02:29 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=119 EAPOL-Key type=254 WPA: RX message 3 of 4-Way Handshake from 00:13:49:12:02:29 (ver=1) WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 WPA: Sending EAPOL-Key 4/4 WPA: Installing PTK to the driver. WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP addr=00:13:49:12:02:29 key_idx=0 set_tx=1 seq_len=6 key_len=32 Received 0 bytes of scan results (1 BSSes) Scan results: 1 Selecting BSS from priority group 10 0: 00:13:49:12:02:29 ssid='Nostromo' wpa_ie_len=24 rsn_ie_len=0 selected Already associated with the selected AP. [...connection down...] --- log --- At this point you often get the connection up again with a restart of wpa_supplicant or a "killall -1 wpa_supplicant". It looks like wpa_supplicant thinks everything is fine with the connection when it's not?! This behaviour is reproduceable with two different Access Points (Linksys WRT54G, Zywall 5). I could do some additional tests with a Dlink wireless card (ath-chipset). bye, Uwe From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 23 17:55:01 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 C426616A423 for ; Mon, 23 Jan 2006 17:55:01 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 091FF43D48 for ; Mon, 23 Jan 2006 17:55:00 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k0NHsxo7050935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jan 2006 09:55:00 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43D518D9.6030208@errno.com> Date: Mon, 23 Jan 2006 09:56:41 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Uwe Laverenz References: <20060123041139.GB69091@geoff.deadheaven.com> <20060123145219.GF17465@laverenz.de> In-Reply-To: <20060123145219.GF17465@laverenz.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: Debugging ath device timeouts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 17:55:01 -0000 Uwe Laverenz wrote: > On Sun, Jan 22, 2006 at 08:11:39PM -0800, David F. Severski wrote: > > >>80211stats, I'm at a loss as to where I should be looking to try to track >>down this problem. Search through the archives for this error don't seem >>to point at a consistent area within the stack to look for a culprit. > > > Several people with different chipsets/drivers (iwi, ath, ral...) seem > to have this problem: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/88793 A device timeout in ath means a frame was submitted to the hardware for transmit but no interrupt was received for 5 seconds. I cannot comment on the other drivers but I find it unlikely that the issue is common. The PR has no useful information. > > >>Any suggestions as to what could be causing this error? > > > I guess it could be a bug in wpa_supplicant, I started the following > session with "wpa_supplicant -i iwi0 -c /etc/wpa_supplicant.conf -d": > > --- log --- > [...] > WPA: RX message 1 of Group Key Handshake from 00:13:49:12:02:29 (ver=1) > WPA: Group Key - hexdump(len=32): [REMOVED] > WPA: Installing GTK to the driver (keyidx=1 tx=0). > WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 > wpa_driver_bsd_set_key: alg=TKIP addr=ff:ff:ff:ff:ff:ff key_idx=1 > set_tx=0 seq_l en=6 key_len=32 > WPA: Sending EAPOL-Key 2/2 > WPA: Key negotiation completed with 00:13:49:12:02:29 [PTK=TKIP > GTK=TKIP] > Cancelling authentication timeout > EAPOL: External notification - portValid=1 > EAPOL: External notification - EAP success=1 > EAPOL: SUPP_PAE entering state AUTHENTICATING > EAPOL: SUPP_BE entering state SUCCESS > EAPOL: SUPP_PAE entering state AUTHENTICATED > EAPOL: SUPP_BE entering state IDLE > > [...several minutes connection ok...] > > RX EAPOL from 00:13:49:12:02:29 > EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines > IEEE 802.1X RX: version=1 type=3 length=127 > EAPOL-Key type=254 > WPA: RX message 1 of Group Key Handshake from 00:13:49:12:02:29 (ver=1) > WPA: Group Key - hexdump(len=32): [REMOVED] > WPA: Installing GTK to the driver (keyidx=1 tx=0). > WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 > wpa_driver_bsd_set_key: alg=TKIP addr=ff:ff:ff:ff:ff:ff key_idx=1 > set_tx=0 seq_len=6 key_len=32 > WPA: Sending EAPOL-Key 2/2 > WPA: Group rekeying completed with 00:13:49:12:02:29 [GTK=TKIP] > > [...connection still ok...] > > RX EAPOL from 00:13:49:12:02:29 > EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines > IEEE 802.1X RX: version=1 type=3 length=95 > EAPOL-Key type=254 > WPA: RX message 1 of 4-Way Handshake from 00:13:49:12:02:29 (ver=1) > WPA: Renewed SNonce - hexdump(len=32): d3 d6 43 c2 48 d3 a4 1b a7 fd ee > 55 49 c2 c6 b9 8c 24 1d 8c 33 b5 fe ea 23 cc ff 23 71 8e 54 7b > WPA: PMK - hexdump(len=32): [REMOVED] > WPA: PTK - hexdump(len=64): [REMOVED] > WPA: EAPOL-Key MIC - hexdump(len=16): 34 01 ba 96 f7 c1 40 08 0d 00 ec > f0 3a d9 38 b7 > WPA: Sending EAPOL-Key 2/4 > RX EAPOL from 00:13:49:12:02:29 > EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines > IEEE 802.1X RX: version=1 type=3 length=119 > EAPOL-Key type=254 > WPA: RX message 3 of 4-Way Handshake from 00:13:49:12:02:29 (ver=1) > WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 > 01 00 00 50 f2 02 01 00 00 50 f2 02 > WPA: Sending EAPOL-Key 4/4 > WPA: Installing PTK to the driver. > WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 > wpa_driver_bsd_set_key: alg=TKIP addr=00:13:49:12:02:29 key_idx=0 > set_tx=1 seq_len=6 key_len=32 > Received 0 bytes of scan results (1 BSSes) > Scan results: 1 > Selecting BSS from priority group 10 > 0: 00:13:49:12:02:29 ssid='Nostromo' wpa_ie_len=24 rsn_ie_len=0 > selected > Already associated with the selected AP. > > [...connection down...] > > --- log --- > > At this point you often get the connection up again with a restart of > wpa_supplicant or a "killall -1 wpa_supplicant". The iwi driver has issues unrelated to ath. Comparing the two is unlikely to help. If you provide a complete wpa supplicant log (privately) I can try to understand what you're seeing. From the snippet above it appears wpa_supplicant was notified that the sta associated/reassociated after it had completed re-keying. This likely means that iwi driver is out of sync w/ wpa_supplicant and/or is not properly dispatching events through the net80211 layer to wpa_supplicant. > > It looks like wpa_supplicant thinks everything is fine with the > connection when it's not?! This behaviour is reproduceable with two > different Access Points (Linksys WRT54G, Zywall 5). I could do some > additional tests with a Dlink wireless card (ath-chipset). iwi is totally different from ath. Trying to infer a problem in one using the other is likely to just confuse the matter. If you've got an iwi problem stick with it. Sam From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 23 18:31:07 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 C883A16A423 for ; Mon, 23 Jan 2006 18:31:07 +0000 (GMT) (envelope-from asstec@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BA9C442DB for ; Mon, 23 Jan 2006 18:31:06 +0000 (GMT) (envelope-from asstec@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k0NIUpxW013694; Mon, 23 Jan 2006 16:30:51 -0200 (BRST) (envelope-from asstec@matik.com.br) From: AT Matik Organization: Infomatik To: freebsd-mobile@freebsd.org Date: Mon, 23 Jan 2006 16:30:38 -0200 User-Agent: KMail/1.9.1 References: <20060123041139.GB69091@geoff.deadheaven.com> <20060123145219.GF17465@laverenz.de> <43D518D9.6030208@errno.com> In-Reply-To: <43D518D9.6030208@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200601231630.39009.asstec@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on msrv.matik.com.br X-Virus-Status: Clean Cc: Subject: Re: Debugging ath device timeouts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 18:31:08 -0000 On Monday 23 January 2006 15:56, Sam Leffler wrote: > > A device timeout in ath means a frame was submitted to the hardware for > transmit but no interrupt was received for 5 seconds. I cannot comment > on the other drivers but I find it unlikely that the issue is common. not exactly, this is very common on almost all WL cards and they are very=20 sensitive to this in FreeBSD, and the risk grows while traffic grows, often= =20 it happens after the card was idle also, seems pci-cards are less and PCMCI= A=20 cards more risky the exactly same hardware with linux or staros often do not show this probl= em,=20 booting back to freebsd it appears imediatly wi cards often do not come back but ath card driver seems to be better device_polling helped a lot because seems that other NICs on the PC could b= e=20 taken out so that only the WLcards are interrupt driven it helps also a lot using better MBs with nothing onboard or at least with= =20 good acpi qualities and anything you do not need disabled in the Bios often this points are useless for client stations which often do not can=20 disable sio/lpt or others often helps checking with pciconf -lv or vmstat -i to find a slot order whe= re=20 the WLcard is not sharing any other resource certain MBs work better with and other without acpi enabled Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-mobile@FreeBSD.ORG Mon Jan 23 20:36:45 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 C25D016A41F for ; Mon, 23 Jan 2006 20:36:45 +0000 (GMT) (envelope-from davidski@deadheaven.com) Received: from geoff.deadheaven.com (geoff.deadheaven.com [216.162.200.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B89E43D46 for ; Mon, 23 Jan 2006 20:36:45 +0000 (GMT) (envelope-from davidski@deadheaven.com) Received: by geoff.deadheaven.com (Postfix, from userid 1001) id E8C851567CB5; Mon, 23 Jan 2006 12:37:11 -0800 (PST) Date: Mon, 23 Jan 2006 12:37:11 -0800 From: "David F. Severski" To: freebsd-mobile@freebsd.org Message-ID: <20060123203711.GD69091@geoff.deadheaven.com> References: <20060123041139.GB69091@geoff.deadheaven.com> <20060123145219.GF17465@laverenz.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6zdv2QT/q3FMhpsV" Content-Disposition: inline In-Reply-To: <20060123145219.GF17465@laverenz.de> User-Agent: Mutt/1.5.11 Subject: Re: Debugging ath device timeouts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 20:36:46 -0000 --6zdv2QT/q3FMhpsV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 23, 2006 at 03:52:19PM +0100, Uwe Laverenz wrote: > > Any suggestions as to what could be causing this error? >=20 > I guess it could be a bug in wpa_supplicant, I started the following > session with "wpa_supplicant -i iwi0 -c /etc/wpa_supplicant.conf -d": Interesting. I'm running hostapd and not wpa_supplicant. Do the two share code? I'll try the debug flags to hostapd and see if I can't generate some more interesting logs. David --6zdv2QT/q3FMhpsV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkPVPncACgkQlTJ+DI1JK1sM5QCfbJLD1YcUnm9WKkBURh7QOoSl qeEAnRR5kO84pkAYbzl6m25VK/MpMS4W =VzVw -----END PGP SIGNATURE----- --6zdv2QT/q3FMhpsV-- From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 02:26:59 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 16ECE16A420 for ; Tue, 24 Jan 2006 02:26:59 +0000 (GMT) (envelope-from lparsons@mail.ahc.umn.edu) Received: from lenti.med.umn.edu (lenti.med.umn.edu [128.101.81.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8046043D79 for ; Tue, 24 Jan 2006 02:26:53 +0000 (GMT) (envelope-from lparsons@mail.ahc.umn.edu) Received: from weed.ccgb.umn.edu (weed.ccgb.umn.edu [160.94.109.46]) by lenti.med.umn.edu (8.9.3p2/8.9.1) with ESMTP id UAA16907 for ; Mon, 23 Jan 2006 20:26:52 -0600 (CST) Date: Mon, 23 Jan 2006 20:26:52 -0600 (CST) From: Lee S Parsons To: freebsd-mobile@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: battery less than 10 minutes kills X X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 02:26:59 -0000 Hello I recently upgraded my thinkpad R32 from 5.4 to 6.0 (new hard drive for the new OS). I compiled my kernel with ACPI for power management, which works pretty well for most things. I even got the battery monitor in KDE working correctly, which makes me somewhat proud of myself :) However, my problem is this: when the battery gets to less than 10 minutes run time remaining, X is killed without warning. I'll get a little popup window next to the battery telling me that I have that much battery remaining, and then before I can plug in all my windows are going away and next thing I know I'm back at the console. I don't remember having had this problem in 5.4. I thought 5.4 would let me damn near run the system battery down to nothing in X. I'm not sure if what I'm seeing is a setting from BSD, X, or KDE? I don't see anything useful reported in /var/log/messges, either. I did check my power settings in KDE, and I have it configured to do nothing for low battery. So I don't think its there... thanks, Lee From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 04:14:01 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 755DA16A4CB for ; Tue, 24 Jan 2006 04:13:58 +0000 (GMT) (envelope-from drgerlists@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id C10DE43E5F for ; Tue, 24 Jan 2006 03:41:42 +0000 (GMT) (envelope-from drgerlists@gmail.com) Received: by zproxy.gmail.com with SMTP id 9so1051514nzo for ; Mon, 23 Jan 2006 19:41:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:organization:reply-to:to:subject:message-id:user-agent:mime-version:content-type:content-transfer-encoding; b=aoVZ4ObZGT8aH5alZ0x6Yffgms0FgzS7pis7bHjamC7StuRMmtzFcb7NWEbiaue3iR/udyYgieeYpUwn3CQ+tukbucfRra3oEYrgpiuV8rQbuz+/DIzbDL+18vQDs/RmJwCDnCxeAFj1Ig2sO7DO6XmP3WeuzR/Nf/4Qur57/Qs= Received: by 10.36.101.4 with SMTP id y4mr4348469nzb; Mon, 23 Jan 2006 19:41:42 -0800 (PST) Received: from lmrmac.uhw.utoledo.edu ( [131.183.85.137]) by mx.gmail.com with ESMTP id 39sm1269719nzk.2006.01.23.19.41.41; Mon, 23 Jan 2006 19:41:41 -0800 (PST) Date: Mon, 23 Jan 2006 22:41:40 -0500 From: drgerlists@gmail.com (Dr. Gary E. RAFE) Organization: Dr. Gary E. RAFE To: freebsd-mobile@freebsd.org Message-ID: <43d5a1f4.EU4xdsl9oE8JEkxMUMkwHEdR@lmrmac.uhw.utoledo.edu> User-Agent: nail 11.25 7/29/05 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: ad0: TIMEOUT - READ_DMA retrying ... on a 5.4-RELEASE system X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: drgerlists@gmail.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 04:14:04 -0000 I had a bit of a scare last week when my Toshiba Satellite Pro 6100 running 5.4-RELEASE (since May 2005 without any major difficulties) resumed from an APM suspend with some odd disk behavior, and the rather scary error message: "ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=12578911". Relevent messages from /var/log/message follow: [Power button actuated following overnight APM suspend] Jan 17 09:16:56 MyHost kernel: pir0: ROUTE_INTERRUPT on resume for link 0x62 failed. Jan 17 09:16:56 MyHost kernel: pir0: ROUTE_INTERRUPT on resume for link 0x61 failed. Jan 17 09:16:56 MyHost kernel: pir0: ROUTE_INTERRUPT on resume for link 0x63 failed. Jan 17 09:16:56 MyHost kernel: wakeup from sleeping state (slept 08:22:31) Jan 17 09:16:55 MyHost apmd[324]: apmevent 0003 index 24 Jan 17 09:17:05 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=12578911 Jan 17 09:17:05 MyHost apmd: resumed at 20060117 09:17:05 Jan 17 09:17:05 MyHost kernel: uhci0: port 0xefe0-0xefff irq 11 at device 29.0 on pci0 Jan 17 09:17:05 MyHost kernel: usb0: on uhci0 Jan 17 09:17:05 MyHost kernel: usb0: USB revision 1.0 Jan 17 09:17:05 MyHost kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 17 09:17:05 MyHost kernel: uhub0: 2 ports with 2 removable, self powered Jan 17 09:17:06 MyHost kernel: uhci1: port 0xef80-0xef9f irq 11 at device 29.1 on pci0 Jan 17 09:17:06 MyHost kernel: usb1: on uhci1 Jan 17 09:17:06 MyHost kernel: usb1: USB revision 1.0 Jan 17 09:17:06 MyHost kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 17 09:17:06 MyHost kernel: uhub1: 2 ports with 2 removable, self powered Jan 17 09:17:06 MyHost kernel: uhci2: port 0xef60-0xef7f irq 11 at device 29.2 on pci0 Jan 17 09:17:06 MyHost kernel: usb2: on uhci2 Jan 17 09:17:06 MyHost kernel: usb2: USB revision 1.0 Jan 17 09:17:06 MyHost kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 17 09:17:06 MyHost kernel: uhub2: 2 ports with 2 removable, self powered Jan 17 09:17:08 MyHost kernel: uhub3: Atmel Standard USB Hub, class 9/0, rev 1.10/3.00, addr 2 Jan 17 09:17:08 MyHost kernel: uhub3: 4 ports with 4 removable, bus powered Jan 17 09:17:09 MyHost kernel: ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 3, iclass 3/1 Jan 17 09:17:09 MyHost kernel: ums0: 3 buttons and Z dir. Jan 17 09:17:24 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=52265546 Jan 17 09:17:24 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=52265546 Jan 17 09:17:24 MyHost kernel: ad0: FAILURE - READ_DMA timed out Jan 17 09:18:56 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=53769542 Jan 17 09:19:06 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=53769542 Jan 17 09:19:06 MyHost kernel: ad0: FAILURE - READ_DMA timed out ... When the system was "stable", I ran "shutdown -p now" for a hard boot. Subsequent /var/log/messages from this boot follow: Jan 17 09:21:34 MyHost syslogd: kernel boot file is /boot/kernel/kernel Jan 17 09:21:34 MyHost kernel: Copyright (c) 1992-2005 The FreeBSD Project. Jan 17 09:21:34 MyHost kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 17 09:21:34 MyHost kernel: The Regents of the University of California. All rights reserved. Jan 17 09:21:34 MyHost kernel: FreeBSD 5.4-RELEASE #6: Sat Dec 31 22:59:00 EST 2005 Jan 17 09:21:34 MyHost kernel: root@MyHost:/usr/src/sys/i386/compile/TSP6100B Jan 17 09:21:34 MyHost kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Jan 17 09:21:34 MyHost kernel: CPU: Intel(R) Pentium(R) 4 Mobile CPU 2.00GHz (1993.54-MHz 686-class CPU) Jan 17 09:21:34 MyHost kernel: Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Jan 17 09:21:34 MyHost kernel: Features=0x3febf9ff Jan 17 09:21:34 MyHost kernel: real memory = 536084480 (511 MB) Jan 17 09:21:34 MyHost kernel: avail memory = 519127040 (495 MB) Jan 17 09:21:34 MyHost kernel: npx0: on motherboard Jan 17 09:21:34 MyHost kernel: npx0: INT 16 interface Jan 17 09:21:34 MyHost kernel: cpu0 on motherboard Jan 17 09:21:34 MyHost kernel: apm0: on motherboard Jan 17 09:21:34 MyHost kernel: apm0: found APM BIOS v1.2, connected at v1.2 Jan 17 09:21:34 MyHost kernel: pcib0: pcibus 0 on motherboard Jan 17 09:21:34 MyHost kernel: pir0: on motherboard Jan 17 09:21:34 MyHost kernel: pci0: on pcib0 Jan 17 09:21:34 MyHost kernel: pcib1: at device 1.0 on pci0 Jan 17 09:21:34 MyHost kernel: pci1: on pcib1 Jan 17 09:21:34 MyHost kernel: pci1: at device 0.0 (no driver attached) Jan 17 09:21:34 MyHost kernel: pci0: at device 29.0 (no driver attached) Jan 17 09:21:34 MyHost kernel: pci0: at device 29.1 (no driver attached) Jan 17 09:21:34 MyHost kernel: pci0: at device 29.2 (no driver attached) Jan 17 09:21:34 MyHost kernel: pcib2: at device 30.0 on pci0 Jan 17 09:21:34 MyHost kernel: pci2: on pcib2 Jan 17 09:21:34 MyHost kernel: fxp0: port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2 Jan 17 09:21:34 MyHost kernel: miibus0: on fxp0 Jan 17 09:21:34 MyHost kernel: inphy0: on miibus0 Jan 17 09:21:34 MyHost kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jan 17 09:21:34 MyHost kernel: fxp0: Ethernet address: 00:00:39:xx:xx:xx Jan 17 09:21:34 MyHost kernel: wi0: mem 0xdbdff000-0xdbdfffff irq 11 at device 10.0 on pci2 Jan 17 09:21:34 MyHost kernel: wi0: using RF:PRISM2.5 MAC:ISL3874A(Mini-PCI) Jan 17 09:21:34 MyHost kernel: wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) Jan 17 09:21:34 MyHost kernel: wi0: Ethernet address: 00:02:6f:xx:xx:xx Jan 17 09:21:34 MyHost kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Jan 17 09:21:34 MyHost kernel: cbb0: irq 11 at device 11.0 on pci2 Jan 17 09:21:34 MyHost kernel: cardbus0: on cbb0 Jan 17 09:21:34 MyHost kernel: pccard0: <16-bit PCCard bus> on cbb0 Jan 17 09:21:34 MyHost kernel: cbb1: irq 11 at device 11.1 on pci2 Jan 17 09:21:34 MyHost kernel: cardbus1: on cbb1 Jan 17 09:21:34 MyHost kernel: pccard1: <16-bit PCCard bus> on cbb1 Jan 17 09:21:34 MyHost kernel: pci2: at device 13.0 (no driver attached) Jan 17 09:21:34 MyHost kernel: isab0: at device 31.0 on pci0 Jan 17 09:21:34 MyHost kernel: isa0: on isab0 Jan 17 09:21:34 MyHost kernel: atapci0: port 0xcfa0-0xcfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 11 at device 31.1 on pci0 Jan 17 09:21:34 MyHost kernel: ata0: channel #0 on atapci0 Jan 17 09:21:34 MyHost kernel: ata1: channel #1 on atapci0 Jan 17 09:21:34 MyHost kernel: pcm0: port 0xcdc0-0xcdff,0xce00-0xceff irq 11 at device 31.5 on pci0 Jan 17 09:21:34 MyHost kernel: pcm0: Jan 17 09:21:34 MyHost kernel: pci0: at device 31.6 (no driver attached) Jan 17 09:21:34 MyHost kernel: orm0: at iomem 0xe0000-0xeffff,0xc0000-0xcffff on isa0 Jan 17 09:21:34 MyHost kernel: pmtimer0 on isa0 Jan 17 09:21:34 MyHost kernel: atkbdc0: at port 0x64,0x60 on isa0 Jan 17 09:21:34 MyHost kernel: atkbd0: irq 1 on atkbdc0 Jan 17 09:21:34 MyHost kernel: kbd0 at atkbd0 Jan 17 09:21:34 MyHost kernel: psm0: irq 12 on atkbdc0 Jan 17 09:21:34 MyHost kernel: psm0: model IntelliMouse, device ID 3 Jan 17 09:21:34 MyHost kernel: sc0: at flags 0x100 on isa0 Jan 17 09:21:34 MyHost kernel: sc0: VGA <16 virtual consoles, flags=0x300> Jan 17 09:21:34 MyHost kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jan 17 09:21:34 MyHost kernel: sio0: type 16550A Jan 17 09:21:34 MyHost kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jan 17 09:21:34 MyHost kernel: unknown: can't assign resources (memory) Jan 17 09:21:34 MyHost kernel: speaker0: at port 0x61 on isa0 Jan 17 09:21:34 MyHost kernel: unknown: can't assign resources (port) Jan 17 09:21:34 MyHost kernel: unknown: can't assign resources (irq) Jan 17 09:21:34 MyHost kernel: unknown: can't assign resources (port) Jan 17 09:21:34 MyHost kernel: Timecounters tick every 10.000 msec Jan 17 09:21:34 MyHost kernel: ad0: 57231MB [116280/16/63] at ata0-master UDMA100 Jan 17 09:21:34 MyHost kernel: acd0: CDRW at ata1-master PIO4 Jan 17 09:21:34 MyHost kernel: cd0 at ata1 bus 0 target 0 lun 0 Jan 17 09:21:34 MyHost kernel: cd0: Removable CD-ROM SCSI-0 device Jan 17 09:21:34 MyHost kernel: cd0: 16.000MB/s transfers Jan 17 09:21:34 MyHost kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Jan 17 09:21:34 MyHost kernel: Mounting root from ufs:/dev/ad0s3a Jan 17 09:21:35 MyHost apmd[319]: start Jan 17 09:21:36 MyHost kernel: uhci0: port 0xefe0-0xefff irq 11 at device 29.0 on pci0 Jan 17 09:21:36 MyHost kernel: usb0: on uhci0 Jan 17 09:21:36 MyHost kernel: usb0: USB revision 1.0 Jan 17 09:21:36 MyHost kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 17 09:21:36 MyHost kernel: uhub0: 2 ports with 2 removable, self powered Jan 17 09:21:37 MyHost kernel: uhci1: port 0xef80-0xef9f irq 11 at device 29.1 on pci0 Jan 17 09:21:37 MyHost kernel: usb1: on uhci1 Jan 17 09:21:37 MyHost kernel: usb1: USB revision 1.0 Jan 17 09:21:37 MyHost kernel: uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 17 09:21:37 MyHost kernel: uhub1: 2 ports with 2 removable, self powered Jan 17 09:21:37 MyHost kernel: uhci2: port 0xef60-0xef7f irq 11 at device 29.2 on pci0 Jan 17 09:21:37 MyHost kernel: usb2: on uhci2 Jan 17 09:21:37 MyHost kernel: usb2: USB revision 1.0 Jan 17 09:21:37 MyHost kernel: uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jan 17 09:21:37 MyHost kernel: uhub2: 2 ports with 2 removable, self powered Jan 17 09:21:39 MyHost kernel: uhub3: Atmel Standard USB Hub, class 9/0, rev 1.10/3.00, addr 2 Jan 17 09:21:39 MyHost kernel: uhub3: 4 ports with 4 removable, bus powered Jan 17 09:21:40 MyHost kernel: ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 3, iclass 3/1 Jan 17 09:21:40 MyHost kernel: ums0: 3 buttons and Z dir. Jan 17 09:22:12 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=50817898 Jan 17 09:22:36 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=50819690 Jan 17 09:22:36 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=50817898 Jan 17 09:22:36 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=50819690 Jan 17 09:22:36 MyHost kernel: ad0: FAILURE - READ_DMA timed out Jan 17 09:22:43 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=50807210 Jan 17 09:22:53 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=50803050 Jan 17 09:23:02 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=50803082 Jan 17 09:23:22 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=54088010 Jan 17 09:23:32 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=54088010 Jan 17 09:23:32 MyHost kernel: ad0: FAILURE - READ_DMA timed out Jan 17 09:23:39 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=54088130 Jan 17 09:23:44 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=54087850 Jan 17 09:24:08 MyHost login: ROOT LOGIN (root) ON ttyv0 Jan 17 09:28:32 MyHost kernel: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=99169729 [system suspended here with "apm -z"] The "ad0: TIMEOUT - READ_DMA retrying" errors came back following a reboot later that evening. Since then, the system has behaved more-or-less flawlessly, as though nothing had happened... I'm at a loss to explain what might have happened. If anyone can offer any insight into this (sporadic hiccough, impending hardware failure, etc.), I, and possibly other list readers, will be grateful. -- Dr Gary E RAFE: drgerlists at gmail dot com From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 10:02:45 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 806FC16A41F for ; Tue, 24 Jan 2006 10:02:45 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from natfrord.rzone.de (natfrord.rzone.de [81.169.145.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id D294843D45 for ; Tue, 24 Jan 2006 10:02:44 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from athena.laverenz.de (p5480C002.dip.t-dialin.net [84.128.192.2]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id k0OA2SSM013644; Tue, 24 Jan 2006 11:02:31 +0100 (MET) Received: from localhost (localhost.localdomain [127.0.0.1]) by athena.laverenz.de (Postfix) with ESMTP id 72780E379FE3; Tue, 24 Jan 2006 11:02:23 +0100 (CET) Received: from athena.laverenz.de ([127.0.0.1]) by localhost (athena [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 05499-04-2; Tue, 24 Jan 2006 11:02:23 +0100 (CET) Received: by athena.laverenz.de (Postfix, from userid 2000) id 0051DE379FE2; Tue, 24 Jan 2006 11:02:22 +0100 (CET) Date: Tue, 24 Jan 2006 11:02:22 +0100 From: Uwe Laverenz To: Sam Leffler Message-ID: <20060124100222.GA6497@laverenz.de> Mail-Followup-To: Sam Leffler , freebsd-mobile@freebsd.org References: <20060123041139.GB69091@geoff.deadheaven.com> <20060123145219.GF17465@laverenz.de> <43D518D9.6030208@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D518D9.6030208@errno.com> Organization: private site Sender: uwe@laverenz.de User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at laverenz.de Cc: freebsd-mobile@freebsd.org Subject: Re: Debugging ath device timeouts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 10:02:45 -0000 On Mon, Jan 23, 2006 at 09:56:41AM -0800, Sam Leffler wrote: > transmit but no interrupt was received for 5 seconds. I cannot comment > on the other drivers but I find it unlikely that the issue is common. > The PR has no useful information. I have to apologize for this, I thought the problem occured with all drivers. Last night I tested a DLink DWL-650ag (ath-chipset) and tried to reproduce the problem. The connection stayed up all night, the problems I saw with iwi did not occur with ath. Sorry, Uwe From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 10:04:49 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 3ECE816A487 for ; Tue, 24 Jan 2006 10:04:49 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from natnoddy.rzone.de (natnoddy.rzone.de [81.169.145.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F7F443D48 for ; Tue, 24 Jan 2006 10:04:48 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from athena.laverenz.de (p5480C002.dip.t-dialin.net [84.128.192.2]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id k0OA4kMe005932 for ; Tue, 24 Jan 2006 11:04:46 +0100 (MET) Received: from localhost (localhost.localdomain [127.0.0.1]) by athena.laverenz.de (Postfix) with ESMTP id EF94DE379FE3 for ; Tue, 24 Jan 2006 11:04:45 +0100 (CET) Received: from athena.laverenz.de ([127.0.0.1]) by localhost (athena [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 06531-01 for ; Tue, 24 Jan 2006 11:04:45 +0100 (CET) Received: by athena.laverenz.de (Postfix, from userid 2000) id 43B5FE379FE2; Tue, 24 Jan 2006 11:04:45 +0100 (CET) Date: Tue, 24 Jan 2006 11:04:45 +0100 From: Uwe Laverenz To: freebsd-mobile@freebsd.org Message-ID: <20060124100445.GB6497@laverenz.de> Mail-Followup-To: freebsd-mobile@freebsd.org References: <20060123041139.GB69091@geoff.deadheaven.com> <20060123145219.GF17465@laverenz.de> <20060123203711.GD69091@geoff.deadheaven.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060123203711.GD69091@geoff.deadheaven.com> Organization: private site Sender: uwe@laverenz.de User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at laverenz.de Subject: Re: Debugging ath device timeouts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 10:04:49 -0000 On Mon, Jan 23, 2006 at 12:37:11PM -0800, David F. Severski wrote: > Interesting. I'm running hostapd and not wpa_supplicant. Do the two Sorry, I thought you were running wpa_supplicant. As stated in my reply to Sam I couldn't reproduce the problem with an ath-card. Uwe From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 11:01:17 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 3D55416A41F; Tue, 24 Jan 2006 11:01:17 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5B6243D45; Tue, 24 Jan 2006 11:01:15 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1F1LvG-0006hU-Oa; Tue, 24 Jan 2006 11:01:15 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1F1LvF-0000RN-HJ; Tue, 24 Jan 2006 20:01:13 +0900 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17366.2296.896827.946579@roam.psg.com> Date: Tue, 24 Jan 2006 20:01:12 +0900 To: FreeBSD Current References: <17365.42627.914349.894764@roam.psg.com> Cc: FreeBSD Laptoppers Subject: Re: t41 zzz X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 11:01:17 -0000 > thinkpad t41 running current as of a few hours ago > xorg, gnome 2.21, ... > > if i execute zzz it suspends s3 seemingly quite happily > > when i open lid, there is disk activity, the numlock and > shiftlock lights flash a bit (this was normal behavior > when zzz last worked some weeks back), and the screen > comes back on. but ... > > it never completes the zzz script, i.e. no shell prompt. > if i put an echo in /etc/rc.resume it shows it has been > executed. > > though i can move the cursor with the touchpad, focus > never grabs any window. > > and there is no response to keyboard. > > at kevin oberman's recommendation, i added radionctl > hacks a la > > if [ -x /usr/local/bin/radeontool ]; then > /usr/local/bin/radeontool light on > fi > > to suspend/resume. no effect. > > suggestions on how to fix or even how to debug would > be appreciated. this was fixed, thanks to tobias roth, by removing dri from /etc/XF86Config randy From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 12:27:13 2006 Return-Path: X-Original-To: mobile@freebsd.org 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 DC03416A420 for ; Tue, 24 Jan 2006 12:27:13 +0000 (GMT) (envelope-from roth@droopy.unibe.ch) Received: from mailhub04.unibe.ch (mailhub04.unibe.ch [130.92.9.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2A9343D49 for ; Tue, 24 Jan 2006 12:27:12 +0000 (GMT) (envelope-from roth@droopy.unibe.ch) Received: from localhost (scanhub02-eth0.unibe.ch [130.92.254.66]) by mailhub04.unibe.ch (Postfix) with ESMTP id 1B6161BD00; Tue, 24 Jan 2006 13:27:11 +0100 (CET) Received: from mailhub04.unibe.ch ([130.92.9.71]) by localhost (scanhub02.unibe.ch [130.92.254.66]) (amavisd-new, port 10024) with LMTP id 16402-07-38; Tue, 24 Jan 2006 13:27:09 +0100 (CET) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub04.unibe.ch (Postfix) with ESMTP id ECCEA1BD4E; Tue, 24 Jan 2006 13:27:08 +0100 (CET) Received: from droopy.unibe.ch (droopy [130.92.64.20]) by asterix.unibe.ch (8.12.10+Sun/8.12.10) with ESMTP id k0OCR98Z018233; Tue, 24 Jan 2006 13:27:09 +0100 (MET) Received: (from roth@localhost) by droopy.unibe.ch (8.12.10+Sun/8.12.9/Submit) id k0OCQmF5011031; Tue, 24 Jan 2006 13:26:48 +0100 (MET) Date: Tue, 24 Jan 2006 13:26:48 +0100 From: Tobias Roth To: mobile@freebsd.org Message-ID: <20060124122648.GA11022@droopy.unibe.ch> References: <17365.42627.914349.894764@roam.psg.com> <17366.2296.896827.946579@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17366.2296.896827.946579@roam.psg.com> User-Agent: Mutt/1.4i X-message-flag: Warning! Using Outlook is insecure and promotes virus distribution. Please use a different email client. X-Virus-checked: by University of Berne Cc: Randy Bush Subject: ATI + DRI + Suspend/Resume [was: t41 zzz] X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 12:27:14 -0000 On Tue, Jan 24, 2006 at 08:01:12PM +0900, Randy Bush wrote: > > this was fixed, thanks to tobias roth, by removing > dri from /etc/XF86Config worked around I'd rather say. So, the question remains: Are ATI Cards and DRI usable, when at the same time requiring a working suspend/resume capability? Does anyone know whether the lunux people maybe have found a fix? Thanks, Tobias From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 13:03:19 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 7B83016A41F for ; Tue, 24 Jan 2006 13:03:19 +0000 (GMT) (envelope-from davidski@deadheaven.com) Received: from geoff.deadheaven.com (geoff.deadheaven.com [216.162.200.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A56443D6B for ; Tue, 24 Jan 2006 13:03:15 +0000 (GMT) (envelope-from davidski@deadheaven.com) Received: by geoff.deadheaven.com (Postfix, from userid 1001) id 7D2771567CB5; Tue, 24 Jan 2006 05:03:41 -0800 (PST) Date: Tue, 24 Jan 2006 05:03:41 -0800 From: "David F. Severski" To: freebsd-mobile@freebsd.org Message-ID: <20060124130341.GL69091@geoff.deadheaven.com> References: <20060123041139.GB69091@geoff.deadheaven.com> <20060123145219.GF17465@laverenz.de> <20060123203711.GD69091@geoff.deadheaven.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Tu8ztk+XgTAiG9Id" Content-Disposition: inline In-Reply-To: <20060123203711.GD69091@geoff.deadheaven.com> User-Agent: Mutt/1.5.11 Subject: Re: Debugging ath device timeouts X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 13:03:19 -0000 --Tu8ztk+XgTAiG9Id Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jan 23, 2006 at 12:37:11PM -0800, David F. Severski wrote: > Interesting. I'm running hostapd and not wpa_supplicant. Do the two > share code? I'll try the debug flags to hostapd and see if I can't > generate some more interesting logs. Running hostapd in the foreground with debugging generates multiple copies of the following block: ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS GMK - hexdump(len=32): 63 ae 2d 41 4e 62 0c be cd 3e 7c 8a f9 3d 71 8e 8a 81 a7 43 2d 98 72 97 6c e5 8c cf fb 15 14 dd GTK - hexdump(len=16): 6b d3 d1 1b 77 fc 67 26 7d 13 81 9f f2 96 ce 91 WPA: 00:13:ce:56:34:61 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:13:ce:56:34:61 WPA: sending 1/2 msg of Group Key Handshake Plaintext EAPOL-Key Key Data - hexdump(len=24): 6b d3 d1 1b 77 fc 67 26 7d 13 81 9f f2 96 ce 91 00 00 00 00 00 00 00 00 IEEE 802.1X: 99 bytes from 00:13:ce:56:34:61 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:13:ce:56:34:61 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:13:ce:56:34:61 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:13:ce:56:34:61 WPA: group key handshake completed (WPA) WPA: group state machine entering state SETKEYSDONE bsd_set_key: alg=CCMP addr=00:00:00:00:00:00 key_idx=2 WPA: 00:13:ce:56:34:61 WPA_PTK_GROUP entering state IDLE Checking STA 00:13:ce:56:34:61 inactivity: Station has been active There was one recorded device timeout overnight. As an asside, what syslog facillity/level does hostapd use? I was unable to get hostapd to use syslog and am probably not logging the right messages in my syslog.conf. David --Tu8ztk+XgTAiG9Id Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkPWJa0ACgkQlTJ+DI1JK1uGXQCfY68Z/kpLqH/vSI7h/ceCoVNg x2UAoIFgeyb9shyM9sHuApUpFyDSS6Yp =Qe/0 -----END PGP SIGNATURE----- --Tu8ztk+XgTAiG9Id-- From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 13:09:38 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 B6B6316A41F for ; Tue, 24 Jan 2006 13:09:38 +0000 (GMT) (envelope-from davidski@deadheaven.com) Received: from geoff.deadheaven.com (geoff.deadheaven.com [216.162.200.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5214143D49 for ; Tue, 24 Jan 2006 13:09:34 +0000 (GMT) (envelope-from davidski@deadheaven.com) Received: by geoff.deadheaven.com (Postfix, from userid 1001) id 2C6A31567CB5; Tue, 24 Jan 2006 05:10:01 -0800 (PST) Date: Tue, 24 Jan 2006 05:10:00 -0800 From: "David F. Severski" To: freebsd-mobile@freebsd.org Message-ID: <20060124131000.GM69091@geoff.deadheaven.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PpocKf6TCvdC9BKE" Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: hostapd_cli looking for wrong socket X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 13:09:38 -0000 --PpocKf6TCvdC9BKE Content-Type: multipart/mixed; boundary="DozTQjXnjm3C9Xhk" Content-Disposition: inline --DozTQjXnjm3C9Xhk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Running 6-STABLE, it looks like hostapd_cli is trying to connect to a non existent control socket. The hostapd socket for my ath0 interface looks like the following: ls -l /var/run/hostapd/ total 4 drwxr-x--- 2 root wheel 512 Jan 24 05:03 ./ drwxr-xr-x 12 root wheel 1024 Jan 24 05:03 ../ srwxrwx--- 1 root wheel 0 Jan 24 05:03 ath0= Yet running hostapd_cli with any commands, such as 'hostapd_cli mib dot11', seems to be looking for a socket named 'ath' (note the lack of the 0). As viewed from strace: connect(3, {sa_family=AF_UNIX, path="/var/run/hostapd/ath"}, 22) = -1 ENOENT (No such file or directory) close My hostapd.conf is as follows: interface=ath0 driver=bsd logger_syslog=-1 logger_syslog_level=2 logger_stdout=-1 logger_stdout_level=-1 dump_file=/tmp/hostapd.dump ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel ssid=Deadheaven wpa=1 wpa_passphrase= wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP The full strace file is attached. Have I misconfigured hostapd or hostapd_cli somehow? David --DozTQjXnjm3C9Xhk Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="hostapd_cli.trace" execve(0xbfbfe750, [0xbfbfec40], [/* 0 vars */]) = 0 mmap(0, 3608, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x2806e000 munmap(0x2806e000, 3608) = 0 __sysctl([...], 0x2806a998, 0xbfbfe9f4, NULL, 0) = 0 mmap(0, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0x2806e000 issetugid(0) = 0 open("/etc/libmap.conf", O_RDONLY) = -1 ENOENT (No such file or directory) open("/var/run/ld-elf.so.hints", O_RDONLY) = 3 read(3, "DUMP_REL_PRE\0LD_DUMP_REL_POST\0__"..., 128) = 128 lseek(3, 128, SEEK_SET) = 128 read(3, "/lib:/usr/lib:/usr/lib/compat:/u"..., 110) = 110 close(3) = 0 access("/lib/libc.so.6", F_OK) = 0 open("/lib/libc.so.6", O_RDONLY) = 3 fstat(3, {st_mode=0, st_size=0, ...}) = 0 read(3, "\177ELF\1\1\1\t\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\330"..., 4096) = 4096 mmap(0, 880640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_NOCORE, 3, 0) = 0x28076000 mprotect(0x28134000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0 mprotect(0x28134000, 4096, PROT_READ|PROT_EXEC) = 0 mmap(0x28135000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xbf000) = 0x28135000 mmap(0x2813a000, 77824, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANON, -1, 0) = 0x2813a000 close(3) = 0 sysarch(0xa, 0xbfbfea70) = 0 mmap(0, 376, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x2814d000 munmap(0x2814d000, 376) = 0 mprotect(0x28076000, 782336, PROT_READ|PROT_WRITE|PROT_EXEC) = 0 mmap(0, 22176, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x2814d000 munmap(0x2814d000, 22176) = 0 mprotect(0x28076000, 782336, PROT_READ|PROT_EXEC) = 0 sigprocmask(SIG_BLOCK, ~[ILL TRAP ABRT EMT FPE BUS SEGV SYS], []) = 0 sigprocmask(SIG_SETMASK, [], NULL) = 0 stat("/var/run/hostapd", {st_mode=070170, st_size=0, ...}) = 0 open("/var/run/hostapd", O_RDONLY|O_NONBLOCK) = 3 fstat(3, {st_mode=070170, st_size=0, ...}) = 0 fcntl(3, F_SETFD, FD_CLOEXEC) = 0 readlink("/etc/malloc.conf", 0xbfbfe7a0, 63) = -1 ENOENT (No such file or directory) issetugid(0xe8) = 0 mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0x2814d000 break(0x804d000) = 0 break(0x804e000) = 0 __sysctl([-433864.-433022], 2, "", [4294533432], NULL, 0) = 0 syscall_397(0x3, 0xbfbfe840) = 0 break(0x804f000) = 0 getdirentries(3, /* 3 entries */, 4096, [0]) = 512 fstat(1, {st_mode=0, st_size=0, ...}) = 0 break(0x8050000) = 0 ioctl(1, TIOCGETA, {B0 -opost -isig -icanon -echo ...}) = 0 write(1, "Selected interface \'ath0\'\n", 26) = 26 break(0x8051000) = 0 lseek(3, 0, SEEK_SET) = 0 close(3) = 0 socket(PF_UNIX, SOCK_DGRAM, 0) = 3 getpid() = 70017 (ppid 70016) bind(3, {sa_family=AF_UNIX, path="/tmp/hostapd_ctrl_70017-"}, 26) = 0 connect(3, {sa_family=AF_UNIX, path="/var/run/hostapd/ath"}, 22) = -1 ENOENT (No such file or directory) close(3) = 0 unlink("/tmp/hostapd_ctrl_70017-0") = -1 ENOENT (No such file or directory) writev(2, [{NULL, 0}, {NULL, 0}, {NULL, 0}, {NULL, 0}], 4) = 76 exit(-1) = ? --DozTQjXnjm3C9Xhk-- --PpocKf6TCvdC9BKE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAkPWJygACgkQlTJ+DI1JK1vx5ACeJ4dxy8V6AAsn0w6cvkZx5jlZ v2QAnA6Rw6znXncIwLpx9RNqh+OK0gGe =ZYRN -----END PGP SIGNATURE----- --PpocKf6TCvdC9BKE-- From owner-freebsd-mobile@FreeBSD.ORG Tue Jan 24 13:12:08 2006 Return-Path: X-Original-To: mobile@freebsd.org 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 837AD16A41F for ; Tue, 24 Jan 2006 13:12:08 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 267BC43D45 for ; Tue, 24 Jan 2006 13:12:07 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1F1Nxp-00016Y-00; Tue, 24 Jan 2006 14:12:01 +0100 Date: Tue, 24 Jan 2006 14:12:01 +0100 To: Tobias Roth Message-ID: <20060124131201.GD25245@poupinou.org> References: <17365.42627.914349.894764@roam.psg.com> <17366.2296.896827.946579@roam.psg.com> <20060124122648.GA11022@droopy.unibe.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060124122648.GA11022@droopy.unibe.ch> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: Randy Bush , mobile@freebsd.org Subject: Re: ATI + DRI + Suspend/Resume [was: t41 zzz] X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 13:12:08 -0000 On Tue, Jan 24, 2006 at 01:26:48PM +0100, Tobias Roth wrote: > On Tue, Jan 24, 2006 at 08:01:12PM +0900, Randy Bush wrote: > > > > this was fixed, thanks to tobias roth, by removing > > dri from /etc/XF86Config > > worked around I'd rather say. > > So, the question remains: > > Are ATI Cards and DRI usable, when at the same time requiring > a working suspend/resume capability? There is a need to not only put the video device to a lower power mode, but to restore the different states of the video card, so I think no. > Does anyone know whether the lunux people maybe have found a > fix? There is a support available using the radeon frame buffer but for powerpc achitecture. This was written by ATI people. Some people reported this worked for their i386 based laptops after hacking a little the radeon frame buffer, but other reported the oposite. I don't know why it failed for some with the same kind of video chip. It maybe a problem with the northbridge, but I have no real evidence for this claim, only a rough guess. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-mobile@FreeBSD.ORG Wed Jan 25 01:53:28 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 5575E16A41F for ; Wed, 25 Jan 2006 01:53:28 +0000 (GMT) (envelope-from synack@netspace.net.au) Received: from mail.netspace.net.au (cumulus.netspace.net.au [203.10.110.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0106C43D48 for ; Wed, 25 Jan 2006 01:53:27 +0000 (GMT) (envelope-from synack@netspace.net.au) Received: from [10.242.221.153] (unknown [203.27.130.225]) by mail.netspace.net.au (Postfix) with SMTP id AF9547DA38 for ; Wed, 25 Jan 2006 12:53:21 +1100 (EST) From: "=?ISO-8859-1?Q?Caleb?=" To: freebsd-mobile@freebsd.org Date: 25 Jan 2006 12:53:14 +1000 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset="ISO-8859-1" Content-Transfer-Encoding: QUOTED-PRINTABLE Message-Id: <20060125015321.AF9547DA38@mail.netspace.net.au> Subject: dstumbler wi patch X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 01:53:28 -0000 Hi everyone, I am using 6-STABLE on my laptop and am wondering if the lates= t bsd-airtools(0.3) still requires the dstumbler.diff patch for the wi driv= er=3F Am emailing from my mobile phone, so please cc me if you can help. T= hanks, Brett From owner-freebsd-mobile@FreeBSD.ORG Fri Jan 27 18:23:07 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 B116B16A45F for ; Fri, 27 Jan 2006 18:23:07 +0000 (GMT) (envelope-from dumitru.roman@deri.org) Received: from smtp.uibk.ac.at (lmr1.uibk.ac.at [138.232.1.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 000B343D5A for ; Fri, 27 Jan 2006 18:23:06 +0000 (GMT) (envelope-from dumitru.roman@deri.org) Received: from [172.16.1.19] (c703-fwngw.uibk.ac.at [138.232.65.129]) by smtp.uibk.ac.at (8.12.11/8.12.11/F1) with ESMTP id k0RIN1rx025825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Jan 2006 19:23:02 +0100 Message-ID: <43DA6505.4050904@deri.org> Date: Fri, 27 Jan 2006 19:23:01 +0100 From: Titi Roman User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: CHI-ANNOUNCEMENTS@listserv.acm.org, isworld@lyris.isworld.org, freebsd-mobile@freebsd.org, swws-interest@w3c.or.kr Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: -5.8 () ALL_TRUSTED,RCV_SMTP_UIBK X-Scanned-By: MIMEDefang 2.52 at uibk.ac.at on 138.232.1.140 Cc: Subject: extended deadline: MDM'06 Workshop - Mobile Services and Ontologies (MoSO 2006) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2006 18:23:07 -0000 ***Apologies for multiple postings*** ********************************************** *** New deadline: February 20, 2006 *** ********************************************** Call for Submissions ----------------------------------------------------------------------------------------------- Mobile Services and Ontologies Workshop (MoSO 2006) http://www.deri.at/events/workshops/mdm2006/ at The 7th International Conference on Mobile Data Management (MDM'06) http://www.mdm2006.kddilabs.jp/ May 9, 2006, Nara, Japan -------------------------------------------------------- THEME OF THE WORKSHOP The theme of the workshop is the intersection of three major trends in today’s computing: * mobile computing becomes more and more important. Mobile portable devices have outnumbered already traditional desktop computers and will mould the view of computers future generations will have. * service-oriented computing is viewed by many analysts as the computing paradigm of the near future. It allows for the dynamic integration of functionality provided by different parties. * research on ontologies, in particular in connection with work on the semantic web and semantic web services allows for machine understandable description of functionality and for automatic interaction of devices without the need for human involvement. The proposed workshop investigates how mobile computing can benefit from service-orientation and ontologies and vice versa. The vision is to extend the typically rather limited capabilities of mobile devices by using services offered by other devices, network providers or third parties. Adding ontologies to this scenario allows this extension to be transparent to the human user. GENERAL OVERVIEW Today, computers are changing from big, grey, and noisy things on our desks to small, portable, and ever networked devices most of us are carrying around. This new form of mobility imposes a shift in how we view computers and the way we work with them. In developing countries like India and China ‘Mobile Internet’ can become the only Internet a large portion of population will get access to. Services offer the possibility to overcome the limitations of individual mobile devices by making functionality offered by others available to them on an “as-needed” basis. Thus, using the service-oriented computing paradigm in mobile environments will considerably enlarge the variety of accessible applications and will enable new business opportunities in the mobile space by delivering integrated functionalities across wireless networks. Network hosted mobile services will allow mobile operators and third party mobile services provider to extend their businesses by making their network services available to a broader audience (e.g. developers, service providers, etc.); device hosted service will allow great potential for big innovations for applications and services that can be provided by individual mobile device owners. These mobile services offer functionalities and behaviors that can be described, advertised, discovered, and composed by others. Eventually, they will be able to interoperate even though they have not been designed to work together. This type of interoperability is based on the ability to understand other services and reason about their functionalities and behaviors when necessary. In this respect, mobile services can benefit from marrying the Semantic Web, which provides the infrastructure for the extensive usage of distributed knowledge, to be deployed for modeling services and add meaning, through ontologies, enabling lightweight discovery and composition of mobile services. The ability to appropriately combine mobility and semantic grounded data sharing has generated and is continuously triggering challenging questions in several areas of computer science, engineering and networking. This workshop aims to tackle the research problems around methods, concepts, models, languages and technologies that enable new opportunities in the mobile space through adoption, usage, and integration of mobile services and ontologies. Of particular interest are the methodologies and technologies that would allow automatic tasks to be performed with respect to mobile services and the use of ontologies in this context. This proposed workshop aims to bring together researchers and industry attendees addressing many of these issues, and promote and foster a greater understanding of mobile service and ontologies and their potential in enabling new business opportunities in the mobile space. TOPICS The following indicates the general focus of the workshop. However, related contributions are welcome as well. - architectures for mobile internet services - languages for describing mobile services - discovery and matchmaking of ontology based mobile services - adaptive selection of mobile services - ontology management in mobile environments - contracting and negotiation with ontology-based mobile services (service level agreements) - approaches to composition of ontology based mobile services - invocation, adaptive execution, monitoring, and management of mobile services - interaction protocols and conversation models for mobile services - ontology-based security and privacy issues in mobile services - mobile service applications - analysis and design approaches for mobile services - reasoning with mobile services - ontology-based policies for mobile services - tools for discovery, matchmaking, selection, mediation, composition, management, and monitoring of mobile services - mobile service development - multi agent systems and mobile services WORKSHOP FORMAT AND ATTENDANCE The program will occupy a full day, and will include presentations of papers selected from the full papers category (see 'submissions' below). Please note that at least one author of each accepted submission must attend the workshop. The MDM 2006 conference formalities are applied for fees and respective organizational aspects. Submission of a paper is not required for attendance at the workshop. However, in the event that the workshop cannot accommodate all who would like to participate, those who have submitted a paper (in any category) will be given priority for registration. SUBMISSIONS Two categories of submissions are solicited: (1) Full papers (up to 8 pages). (2) Position papers (up to 2 pages). All submissions should be formatted in the IEEE style. Formatting instructions and LaTeX macros are available on the IEEE computer society site: LaTex macros: ftp://pubftp.computer.org/Press/Outgoing/proceedings/IEEE_CS_Latex.zip Formatting instructions: ftp://pubftp.computer.org/Press/Outgoing/proceedings/instruct.doc ftp://pubftp.computer.org/Press/Outgoing/proceedings/instruct.pdf ftp://pubftp.computer.org/Press/Outgoing/proceedings/instruct.ps All the papers should be submitted in electronic format (pdf version) using the following link: http://www.easychair.org/MOSO06/submit/. Full papers will receive a peer-review. Position statements are intended to present very early or planned future work that is regarded as relevant to the workshop. Position statements are limited to 2 pages; position statements will not receive a peer-review. All accepted full papers as well as all position papers of attendees will be published in post workshop proceedings in IEEE DL. Additionally, authors of selected papers will have the opportunity to submit extended versions of their papers for publication with a major publisher. For these extended versions, an additional review will take place. IMPORTANT DATES Submissions: February 20, 2006 Acceptance: March 20, 2006 Final copy: April 1, 2006 Workshop day: May 9, 2006 ORGANIZING COMMITTEE Christoph Bussler (DERI, Ireland) Birgitta König-Ries (Friedrich-Schiller-Universität Jena, Germany) Dumitru Roman (DERI Innsbruck, Austria) Jari Veijalainen (University of Potsdam, Germany) PROGRAM COMMITTEE (confirmed; to be extended) Nelson Baloyian, University of Chile, Chile Martin Bauer, NEC Europe, Germany Sonia Ben Mokhtar, INRIA, France Richard Benjamins, iSOCO, Spain Yolande Berbers, Katholieke Universiteit Leuven, Belgium Patricia Charlton, Motorola Labs, UK John Domingue, Open University, UK Dieter Fensel, DERI, Austria and Ireland Fabien Gandon, INRIA Sophia Antipolis, France Walter Goix, Telecom Italia, Italy Martin Hepp, DERI Innsbruck, Austria Eero Hyvönen, Helsinki Univ. of Technology, Finland Valérie Issarny, INRIA, France Christian Jensen, Aalborg University, Denmark Qun Jin, Waseda University, Japan Oskar Juhlin, Interactive Institute, Sweden Michael Klein, Universität Karlsruhe, Germany Werner Kuhn, University of Münster, Germany Antonio Liotta, University of Essex, UK Qusay H. Mahmoud, University of Guelph, Canada Mitsuji Matsumoto, Waseda University, Japan Vladimir Oleshchuk, Agder University College, Norway Massimo Paolucci, DoCoMo Euro-Labs, Germany Stefan Poslad, Queen Mary College, UK Tore Risch, Uppsala University, Sweden Brahmananda Sapkota, DERI, Ireland Steffen Staab, University of Koblenz-Landau, Germany Thomas Strang, DLR, Germany / DERI Innsbruck, Austria Do van Thanh, Telenor, Norway Vagan Terziyan, Univ. of Jyvaskyla, Finland Ioan Toma, DERI Innsbruck, Austria Alexander Wahler, NIWA, Austria Matthias Wagner, DoCoMo Euro-Labs, Germany Mathias Weske, HPI, Univ. of Potsdam, Germany Wai Gen Yee, Illinois Institute of Technology, USA Yelena Yesha, University of Maryland, USA Note: Check the workshop web site for frequent updates to the PC members list. From owner-freebsd-mobile@FreeBSD.ORG Sat Jan 28 22:47:13 2006 Return-Path: X-Original-To: freebsd-mobile@freebsd.org 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 D6DA116A422 for ; Sat, 28 Jan 2006 22:47:13 +0000 (GMT) (envelope-from ayleronn@yahoo.com) Received: from web37807.mail.mud.yahoo.com (web37807.mail.mud.yahoo.com [209.191.87.120]) by mx1.FreeBSD.org (Postfix) with SMTP id 2306D43D46 for ; Sat, 28 Jan 2006 22:47:13 +0000 (GMT) (envelope-from ayleronn@yahoo.com) Received: (qmail 99412 invoked by uid 60001); 28 Jan 2006 22:47:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=3vn/GwZCMWQBpHCJVFlpXjNjHz4CXPQO+ezBtswh66LeTmzDiqRTf5NhJee2IG4LHaCuW/XJjOvs64L4nLu1bYFKRL9wwhlCW+1NK4lspnS+KB1WOCYeg99jueTmvcFxxxM4DepfSeXJS67KH8eq1q/CWYXw++J8UluMuAvvV5s= ; Message-ID: <20060128224712.99410.qmail@web37807.mail.mud.yahoo.com> Received: from [67.171.172.113] by web37807.mail.mud.yahoo.com via HTTP; Sat, 28 Jan 2006 14:47:12 PST Date: Sat, 28 Jan 2006 14:47:12 -0800 (PST) From: Marc Frajola To: freebsd-mobile@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: FreeBSD 6.0 on a Compaq Presario V2000 (V2570NR) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2006 22:47:14 -0000 I recently got my Compaq Presario V2570NR (V2000-series) laptop running FreeBSD after battling a couple problems, and wanted to share what I had to do in order to get both FreeBSD 6.0 booting normally and Xorg 6.8.2 running with the screen in the proper 1280x768 resolution. The Presario V2570NR is an AMD Turion 64bit mobile 1.8GHz processor with 512MB RAM, ATI Radeon Xpress 200M graphics (which *appears* to borrow 128M from system RAM), 60GB disk, DVD+/-RW, integrated Broadcom B/G wireless, USB/firewire, and Realtek 10/100 wired LAN. The first hurdle was getting FreeBSD 6.0-RELEASE to boot at all on the machine. It hung right after the "Timecounter" messages during the kernel probe. I was fortunate enough to notice that booting FreeBSD in "safe mode" allowed it to come up into the installer. After installing, it would still only boot from the hard disk in safe mode. I wanted it to boot normally, so made a custom kernel where I removed all unnecessary devices since I figured that the hang was due to one of the device probes mucking something up, which was then causing the kernel hang after "Timecounter...". I first took out all SCSI and RAID controllers, plus all ISA network cards, still hung, but in slightly different random places over a couple boot attempts. I noticed that the serial port was not configuring properly, so I rebuilt another kernel, commenting out all SIO ports, and behold, it booted normally. Since there isn't a directly accessible serial port (at least without getting the I/O port expander), I didn't pursue trying to get a serial port working. The second and more formidable hurdle was trying to get Xorg to work in the native display resolution of 1280x768. The problem is apparently that Xorg can auto-configure VESA, which winds up choosing 1024x768, and the aspect ratio of the display is quite wrong since V2000s are widescreen. I had to do several hours of many different google searches to find the answer on a site other than the freebsd.org site. I would like to reference that link and thank the author of it for the answer: http://forums.bit-tech.net/showthread.php?p=1024307 In short, the ATI Radeon xpress 200m has a ChipID different from the chips officially supported by the Xorg radeon(4) driver. I checked the latest Xorg version, which still doesn't claim to support xpress 200m graphics, so the hack of simply telling Xorg that the display device with ChipId 0x5460 is officially a radeon card, and once the radeon driver loads, it can run the display at the desired resolution. One wart worth noting: If I exit my Xserver normally, it can leave the display in a barely-readable mode. If I exit X by using the famed CTRL-ALT-BACKSPACE, it leaves the display at the proper/readable scan rate. If you have a Radeon Xpress 200m graphics and want the radeon driver to recognize it, simply add "ChipId 0x5460" in the section with BusID "PCI:1:5:0". Commentary: It would *SURE* be nice if ATI would put out native BSD drivers for their cards. The fact that NVidia does have a driver solution that is working and tested on FreeBSD is GREAT in my humble opinion, and my hat is off to NVidia for taking the time and care to make this available to our community. The problem is that extremely FEW commonly available low to middle cost laptops apparently have NVidia graphics chipsets in them, and those that I did find available seemed to have other warts or were just too expensive, so I just gave up on trying to get a decent NVidia-graphics-based laptop. For $899, this Turion laptop seems pretty zippy and it is super-nice to have a dual boot between XP and FreeBSD 6.0. I really appreciate others who came before me and went to some trouble to figure out *and* post to this list about how they got a particular laptop/notebook running with FreeBSD; that made a difference in me being able to get my V2570NR working, and I strongly encourage others to make a quick post about specifics on their particular laptop model, particularly if your laptop has NVidia graphics. Cheers, -Marc __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com