From dboner at aogsquid.ucsd.edu Tue Sep 1 19:28:10 2009 From: dboner at aogsquid.ucsd.edu (David Horwitt) Date: Tue Sep 1 19:28:17 2009 Subject: netbooks and sdhci Message-ID: <4A9D7336.3050909@aogsquid.ucsd.edu> I recently purchased an Asus Aspire One D250-1151, and am,overall, pleased with it (running 7,2-RELEASE). The alc ethernet is not supported in 7.2 (the ath0 wireless is), and I don't care about the video camera. The '5-in-1' media reader is, unfortunately for me, a USB device. (After some detective work, I determined that it uses a Reaktek RTS5101 or RTS5111). For my purposes (low level SDHC card access), I prefer hardware that is supported by the sdhci/mmc subsystem. So my question is: does anybody know _for sure_ of a hard-disk netbook with a media reader that uses the sdhci interface and is supported by FBSD 7.2 (supported = wireless,X,USB). $USD300 (like the AA1-D250) is the desired price point, but up to about $USD400 is OK (as is FBSD 8.0, if the hardware is right). If you have any pointers, please include the sub-model information, because if it's anything like the Asus, the hardware varies all over the place, and 'Aspire One' means less than 'D250' or 'AO150'. Thank you, David From saifi.khan at datasynergy.org Wed Sep 2 10:15:51 2009 From: saifi.khan at datasynergy.org (Saifi Khan) Date: Wed Sep 2 10:16:01 2009 Subject: netbooks and sdhci In-Reply-To: <4A9D7336.3050909@aogsquid.ucsd.edu> References: <4A9D7336.3050909@aogsquid.ucsd.edu> Message-ID: On Tue, 1 Sep 2009, David Horwitt wrote: > > So my question is: does anybody know _for sure_ of a hard-disk netbook with a > media reader that uses the sdhci interface > and is supported by FBSD 7.2 (supported = wireless,X,USB). $USD300 (like the > AA1-D250) is the desired price point, but > up to about $USD400 is OK (as is FBSD 8.0, if the hardware is right). If you > have any pointers, please > include the sub-model information, because if it's anything like the Asus, the > hardware varies all over the place, and > 'Aspire One' means less than 'D250' or 'AO150'. > > Thank you, > David > Acer Aspire One D150. note 'Acer' ! is what i'd recommend. This is a hard-disk netbook. Here are the complete hardware and installation details http://www.twincling.org/node/451 The website http://www.acer.com/aspireone/about.html In India it costed me about INR 21,500 (or $430) in March 2009. YMMV. thanks Saifi. From fbsd.mobile at rachie.is-a-geek.net Wed Sep 2 12:02:14 2009 From: fbsd.mobile at rachie.is-a-geek.net (Mel Flynn) Date: Wed Sep 2 12:03:11 2009 Subject: Wpi and hostap mode Message-ID: <200909021345.09737.fbsd.mobile@rachie.is-a-geek.net> Hi, wpi(4) doesn't support hostap mode. Is this is hardware, firmware or driver issue? I've glanced at the linux code, but see no mention of hostap there either. -- Mel From onemda at gmail.com Wed Sep 2 14:56:01 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Wed Sep 2 14:56:07 2009 Subject: Wpi and hostap mode In-Reply-To: <200909021345.09737.fbsd.mobile@rachie.is-a-geek.net> References: <200909021345.09737.fbsd.mobile@rachie.is-a-geek.net> Message-ID: <3a142e750909020730w1db161eat5a7703129c5fc290@mail.gmail.com> On 9/2/09, Mel Flynn wrote: > Hi, > > wpi(4) doesn't support hostap mode. Is this is hardware, firmware or driver > issue? > I've glanced at the linux code, but see no mention of hostap there either. http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1585 -- Paul From henry.hu.sh at gmail.com Wed Sep 2 17:59:14 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Wed Sep 2 17:59:21 2009 Subject: Wpi and hostap mode In-Reply-To: <3a142e750909020730w1db161eat5a7703129c5fc290@mail.gmail.com> References: <200909021345.09737.fbsd.mobile@rachie.is-a-geek.net> <3a142e750909020730w1db161eat5a7703129c5fc290@mail.gmail.com> Message-ID: <53a1e0710909021034v17d97673o8171c47c0632e85a@mail.gmail.com> On Wed, Sep 2, 2009 at 10:30 PM, Paul B. Mahol wrote: > On 9/2/09, Mel Flynn wrote: >> Hi, >> >> wpi(4) doesn't support hostap mode. Is this is hardware, firmware or driver >> issue? >> I've glanced at the linux code, but see no mention of hostap there either. > > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1585 Although it seems hard to support the hostap mode, would there be IBSS mode support in the future? > > -- > Paul > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > From onemda at gmail.com Wed Sep 2 19:23:20 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Wed Sep 2 19:23:28 2009 Subject: Wpi and hostap mode In-Reply-To: <53a1e0710909021034v17d97673o8171c47c0632e85a@mail.gmail.com> References: <200909021345.09737.fbsd.mobile@rachie.is-a-geek.net> <3a142e750909020730w1db161eat5a7703129c5fc290@mail.gmail.com> <53a1e0710909021034v17d97673o8171c47c0632e85a@mail.gmail.com> Message-ID: <3a142e750909021223s28d928e1r36f88a301da1fbbd@mail.gmail.com> On Wed, Sep 2, 2009 at 5:34 PM, Henry Hu wrote: > On Wed, Sep 2, 2009 at 10:30 PM, Paul B. Mahol wrote: >> On 9/2/09, Mel Flynn wrote: >>> Hi, >>> >>> wpi(4) doesn't support hostap mode. Is this is hardware, firmware or driver >>> issue? >>> I've glanced at the linux code, but see no mention of hostap there either. >> >> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1585 > > Although it seems hard to support the hostap mode, would there be IBSS > mode support in the future? Depends on contributors. -- Paul From fbsd.mobile at rachie.is-a-geek.net Wed Sep 2 21:31:32 2009 From: fbsd.mobile at rachie.is-a-geek.net (Mel Flynn) Date: Wed Sep 2 21:31:39 2009 Subject: Wpi and hostap mode In-Reply-To: <3a142e750909020730w1db161eat5a7703129c5fc290@mail.gmail.com> References: <200909021345.09737.fbsd.mobile@rachie.is-a-geek.net> <3a142e750909020730w1db161eat5a7703129c5fc290@mail.gmail.com> Message-ID: <200909022331.29137.fbsd.mobile@rachie.is-a-geek.net> On Wednesday 02 September 2009 16:30:00 Paul B. Mahol wrote: > On 9/2/09, Mel Flynn wrote: > > Hi, > > > > wpi(4) doesn't support hostap mode. Is this is hardware, firmware or > > driver issue? > > I've glanced at the linux code, but see no mention of hostap there > > either. > > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1585 Hmm, so since "patches are welcome" leads me to believe the firmware and hardware are capable. -- Mel From oberman at es.net Thu Sep 3 22:28:05 2009 From: oberman at es.net (Kevin Oberman) Date: Thu Sep 3 22:28:11 2009 Subject: ath0 link up/down frequent In-Reply-To: Your message of "Thu, 03 Sep 2009 17:21:57 CDT." <20090903222156.GA6786@magus.portal.sigil.org> Message-ID: <20090903222801.528461CC09@ptavv.es.net> > From: "Richard Kolkovich" > Date: Thu, 3 Sep 2009 17:21:57 -0500 > > On Sat, Aug 22, 2009 at 11:29:13AM -0700, Kevin Oberman wrote: > > > Anything I should look into? > > > > My standard suggestion, which works for me, is to issue an 'ifconfig > > ath0 -bgscan'. Background scanning is not supposed to effect the > > association, but it seems to, at least on my system. > > > > My experience has been much the same. It typically only happens in > areas with a lot of APs, though (i.e. my apartment building). My case is similar. I will see it on occasion at home where I typically see only two or three APs, but is only a real problem when I am at a networking conference and there are a whole raft of APs out there. In those cases the wireless is rendered unusable as I lose association every 5 minutes. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From sarumont at sigil.org Thu Sep 3 22:38:51 2009 From: sarumont at sigil.org (Richard Kolkovich) Date: Thu Sep 3 22:38:57 2009 Subject: ath0 link up/down frequent In-Reply-To: <20090822182913.DE2781CC09@ptavv.es.net> References: <4A90262A.5060103@langille.org> <20090822182913.DE2781CC09@ptavv.es.net> Message-ID: <20090903222156.GA6786@magus.portal.sigil.org> On Sat, Aug 22, 2009 at 11:29:13AM -0700, Kevin Oberman wrote: > > Anything I should look into? > > My standard suggestion, which works for me, is to issue an 'ifconfig > ath0 -bgscan'. Background scanning is not supposed to effect the > association, but it seems to, at least on my system. > My experience has been much the same. It typically only happens in areas with a lot of APs, though (i.e. my apartment building). -- Richard Kolkovich sarumont@sigil.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090903/973883b5/attachment.pgp From scrubby at scrubtheweb.com Sun Sep 6 01:55:15 2009 From: scrubby at scrubtheweb.com (Scrub The Web) Date: Sun Sep 6 01:55:21 2009 Subject: Confirmation Required Message-ID: <200909060155.n861t374030430@scrubby.scrubtheweb.com> CONFIRMATION IS REQUIRED BY SEP 12, 2009 - SEE BELOW! Thanks again for submitting your URL to ScrubTheWeb(tm). Please read this entire email message to complete your no cost submission. The following URL was submitted to ScrubTheWeb.com(tm): http://www.polysemantic.info/media/feb_0051.html The IP address of the "user" who submitted the above URL was: 83.233.165.74. If you wish to CONFIRM, EDIT or DELETE this submission point your browser to: http://www.scrubtheweb.com/confirm/id/d9b43e446ed04115572c05497fec41e3/ IMPORTANT: We do NOT maintain a mailing list of any kind and we do NOT sell, rent or use your email address for any other purpose than this confirmation email. Note: Please do not reply to this email, as your reply will not be received. If you need to contact us for any reason please point your browser to: http://www.scrubtheweb.com/feedback/ Thanks again, Scrub The Web http://www.scrubtheweb.com/ Meta Tag Analyzer http://www.scrubtheweb.com/abs/meta-check.html Meta Tag Builder http://www.scrubtheweb.com/abs/builder.html ------------------- End of Document ------------------- From lars.engels at 0x20.net Tue Sep 8 08:37:07 2009 From: lars.engels at 0x20.net (Lars Engels) Date: Tue Sep 8 08:37:13 2009 Subject: Dell M4400 && power-off the display on Lid close (8-CURRENT / Xorg) In-Reply-To: <20090820081055.GA2962@current.Sisis.de> References: <20090820081055.GA2962@current.Sisis.de> Message-ID: <20090908082123.GR38884@e.0x20.net> On Thu, Aug 20, 2009 at 10:10:55AM +0200, Matthias Apitz wrote: > > Hello, > > I'm running 8-CURRENT and Xorg on the above mentioned laptop. > > I'd like to have powered off the display on Lid close, and powered on > again on open; I watched the devd(8) events in both cases: > > close: > setting system=ACPI > setting subsystem=Lid > setting type=\_SB_.LID_ > setting notify=0x00 > Processing notify event > ... > > open: > setting system=ACPI > setting subsystem=Lid > setting type=\_SB_.LID_ > setting notify=0x01 > Processing notify event > ... > > but they are not estimated in /etc/devd.conf. Any hint for a good > devd.conf entry to make that working? Thx in advance > > Btw: I don't want suspend/resume. Try this: notify 10 { match "system" "ACPI"; match "subsystem" "Lid"; action"$PATH_TO_YOUR_SCRIPT $notify"; }; And in your script you turn off the backlight with xbacklight -set 0 when notify is 0x00 and xbacklight -set 100 for 0x01. HTH Lars -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20090908/c6473723/attachment.pgp From guru at unixarea.de Tue Sep 8 14:40:53 2009 From: guru at unixarea.de (Matthias Apitz) Date: Tue Sep 8 14:40:59 2009 Subject: Dell M4400 && power-off the display on Lid close (8-CURRENT / Xorg) In-Reply-To: <20090908082123.GR38884@e.0x20.net> References: <20090820081055.GA2962@current.Sisis.de> <20090908082123.GR38884@e.0x20.net> Message-ID: <20090908144050.GA6014@current.Sisis.de> El d?a Tuesday, September 08, 2009 a las 10:21:23AM +0200, Lars Engels escribi?: > > but they are not estimated in /etc/devd.conf. Any hint for a good > > devd.conf entry to make that working? Thx in advance > > > > Btw: I don't want suspend/resume. > > Try this: > > notify 10 { > match "system" "ACPI"; > match "subsystem" "Lid"; > action"$PATH_TO_YOUR_SCRIPT $notify"; > }; > > And in your script you turn off the backlight with > xbacklight -set 0 > when notify is 0x00 and > xbacklight -set 100 > for 0x01. Thanks for your hint; I'm using since some time now: cat /usr/local/etc/devd/lid.conf # # When the the Lid is open / closed .... # # , August 2009 # notify 10 { match "system" "ACPI"; match "subsystem" "Lid"; match "notify" "0x00"; action "/usr/local/bin/xset -display :0.0 s 1"; }; notify 10 { match "system" "ACPI"; match "subsystem" "Lid"; match "notify" "0x01"; action "/usr/local/bin/xset -display :0.0 s 120"; }; Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From marka at isc.org Tue Sep 8 23:46:44 2009 From: marka at isc.org (Mark Andrews) Date: Tue Sep 8 23:46:51 2009 Subject: Dell M4400 && power-off the display on Lid close (8-CURRENT / Xorg) In-Reply-To: Your message of "Tue, 08 Sep 2009 16:40:50 +0200." <20090908144050.GA6014@current.Sisis.de> References: <20090820081055.GA2962@current.Sisis.de> <20090908082123.GR38884@e.0x20.net> <20090908144050.GA6014@current.Sisis.de> Message-ID: <200909082346.n88NkaLv040439@drugs.dv.isc.org> In message <20090908144050.GA6014@current.Sisis.de>, Matthias Apitz writes: > El día Tuesday, September 08, 2009 a las 10:21:23AM +0200, Lars Engels escribió > : > > > > but they are not estimated in /etc/devd.conf. Any hint for a good > > > devd.conf entry to make that working? Thx in advance > > > > > > Btw: I don't want suspend/resume. > > > > Try this: > > > > notify 10 { > > match "system" "ACPI"; > > match "subsystem" "Lid"; > > action"$PATH_TO_YOUR_SCRIPT $notify"; > > }; > > > > And in your script you turn off the backlight with > > xbacklight -set 0 > > when notify is 0x00 and > > xbacklight -set 100 > > for 0x01. > > Thanks for your hint; I'm using since some time now: > > cat /usr/local/etc/devd/lid.conf > # > # When the the Lid is open / closed .... > # > # , August 2009 > # > notify 10 { > match "system" "ACPI"; > match "subsystem" "Lid"; > match "notify" "0x00"; > action "/usr/local/bin/xset -display :0.0 s 1"; > }; > notify 10 { > match "system" "ACPI"; > match "subsystem" "Lid"; > match "notify" "0x01"; > action "/usr/local/bin/xset -display :0.0 s > 120"; > }; > > Thx I call this on lid events which works even when X isn't running. :-) Mark notify 10 { match "system" "ACPI"; match "subsystem" "Lid"; action "/etc/rc.lid $notify"; }; /etc/rc.lid: #!/bin/sh # deal with lid switch events if [ "x$1" = x0x00 ]; then /usr/bin/logger -t Lid Closed at `/bin/date` /sbin/sysctl hw.acpi.video.lcd0.active=0 else /usr/bin/logger -t Lid Opened at `/bin/date` /sbin/sysctl hw.acpi.video.lcd0.active=1 fi -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org From mobile at freebsd.org Thu Sep 10 10:28:12 2009 From: mobile at freebsd.org (ValentineLawler) Date: Thu Sep 10 10:28:19 2009 Subject: An e-card from ValentineLawler for you Message-ID: <0f228b0d39721978a1c8e97be8012f6b@gold-music.ru> An e-card from ValentineLawler for you ========================================= To view the ecard, copy and paste this url into your browser's address bar:: http://www.gold-music.ru/gallery/displayecard.php?data=YTo5OntzOjI6InJuIjtzOjE1OiJWYWxlbnRpbmVMYXdsZXIiO3M6Mjoic24iO3M6MTU6IlZhbGVudGluZUxhd2xlciI7czoyOiJzZSI7czoxODoibW9iaWxlQGZyZWVic2Qub3JnIjtzOjE6InAiO3M6NzU6Imh0dHA6Ly93d3cuZ29sZC1tdXNpYy5ydS9nYWxsZXJ5L2FsYnVtcy9KZXJ1c2FsZW0vbm9ybWFsX0plcnVzYWxlbV8wMTcuanBlZyI7czoxOiJnIjtzOjE3OiJoS3BsZFNmaXZnWHNuT2lzYyI7czoxOiJtIjtzOjkyNjoiY29tbWVudDYsIFt1cmw9aHR0cDovL3dlYm1vZGVybmEuY29tL3BvcnRhbC9sYW5ndWFnZS9ob21lc19wX2EuaHRtbF1zaWx2ZXIgYmVhdmVyIGJzYVsvdXJsXSwgIDotUCwgW3VybD1odHRwOi8vd3d3LmRpY2tydXNzZWxsLm9yZy9hcnRpY2xlcy9waGlsbGlwczBfLmh0bWxdbXNuIGdyb3VwcyBudWRlIGNlbGVyaXRpZXNbL3VybF0sICA0ODQ1LCBbdXJsPWh0dHA6Ly93d3cuam95bWFya2Vycy5jb20vRm9vdHByaW50X1RoZW1lLmh0bWxdamVyayBzZWFzb25pbmcgcmVjaXBlWy91cmxdLCAgemxyLCBbdXJsPWh0dHA6Ly9tb25hcmNobG9mdHMuY29tL29sZHNpdGUodGFrZW5kb3duMTAtMjgtMDgpL2xvX2Z0c18uaHRtbF1taXN0cmVzcyBlcXVlc3RyaWFuWy91cmxdLCAgdHR5c3VkLCBbdXJsPWh0dHA6Ly9kYXRhbWFnaWNzb2Z0d2FyZS5jb20vc2l0ZS9nb3RvLmFzcF1teXNwYWNlIGJhY2tncm91bmRzIG! 9mIGhvbmRhIGF0dlsvdXJsXSwgIDk2NjMzLCBbdXJsPWh0dHA6Ly9lc291cmNlZnVsLm5ldC9jbGFzc2lmaWVkcy0yLjQuMC1FdmFsdWF0aW9uL25vdGlmaWNhdGlvbnMvbGFuZ3VhZ2UvZW1haWxfYWRfZXhwaXJlXy5odG1sXW1pbGV5IGN5cnVzIHRvcGxlc3MgcGljdHVyc1svdXJsXSwgIGFmc3VvLCBbdXJsPWh0dHA6Ly93d3cucXNpd29ybGQuY29tL1FTSV9Db250X2NfdFVzLmh0bWxdaHR0cDovL3d3dy5xc2l3b3JsZC5jb20vUVNJX0NvbnRfY190VXMuaHRtbFsvdXJsXSwgIHVkamF4LCBbdXJsPWh0dHA6Ly9jYWx2YXJ5Y3JjLnVzL2VtYWlsL2dvb2dsZWhvc3RlZF9zZXJ2aWNlMS5odG1sXXJlZ2lzdHJ5IG9mIGRlZWRzIHJvY2tpbmdoYW0gbmhbL3VybF0sICAmZ3Q7OlssIFt1cmw9aHR0cDovL3d3dy5zdW5zcGlyaXRzdHVkaW8uY29tL3RoYW5rcy5waHBdcG9ub2dyYXBoaWMgc2V4IGxpdmVbL3VybF0sICAlW1tbLCAiO3M6MzoicGlkIjtpOjIwODtzOjI6InB0IjtzOjA6IiI7czoyOiJwYyI7czowOiIiO30%3D hKpldSfivgXsnOisc comment6, [url=http://webmoderna.com/portal/language/homes_p_a.html]silver beaver bsa[/url], :-P, [url=http://www.dickrussell.org/articles/phillips0_.html]msn groups nude celerities[/url], 4845, [url=http://www.joymarkers.com/Footprint_Theme.html]jerk seasoning recipe[/url], zlr, [url=http://monarchlofts.com/oldsite(takendown10-28-08)/lo_fts_.html]mistress equestrian[/url], ttysud, [url=http://datamagicsoftware.com/site/goto.asp]myspace backgrounds of honda atv[/url], 96633, [url=http://esourceful.net/classifieds-2.4.0-Evaluation/notifications/language/email_ad_expire_.html]miley cyrus topless picturs[/url], afsuo, [url=http://www.qsiworld.com/QSI_Cont_c_tUs.html]http://www.qsiworld.com/QSI_Cont_c_tUs.html[/url], udjax, [url=http://calvarycrc.us/email/googlehosted_service1.html]registry of deeds rockingham nh[/url], >:[, [url=http://www.sunspiritstudio.com/thanks.php]ponographic sex live[/url], %[[[, ValentineLawler (mobile@freebsd.org) ----------------------------------------- View more pictures !: http://www.gold-music.ru/gallery/ From guru at unixarea.de Thu Sep 10 12:15:02 2009 From: guru at unixarea.de (Matthias Apitz) Date: Thu Sep 10 12:15:09 2009 Subject: Dell M4400 && power-off the display on Lid close (8-CURRENT / Xorg) In-Reply-To: <200909082346.n88NkaLv040439@drugs.dv.isc.org> References: <20090820081055.GA2962@current.Sisis.de> <20090908082123.GR38884@e.0x20.net> <20090908144050.GA6014@current.Sisis.de> <200909082346.n88NkaLv040439@drugs.dv.isc.org> Message-ID: <20090910121459.GA5007@current.Sisis.de> El d?a Wednesday, September 09, 2009 a las 09:46:36AM +1000, Mark Andrews escribi?: > I call this on lid events which works even when X isn't running. :-) Would be nice, but ... > notify 10 { > match "system" "ACPI"; > match "subsystem" "Lid"; > action "/etc/rc.lid $notify"; > }; > > /etc/rc.lid: > #!/bin/sh > # deal with lid switch events > > if [ "x$1" = x0x00 ]; then > /usr/bin/logger -t Lid Closed at `/bin/date` > /sbin/sysctl hw.acpi.video.lcd0.active=0 > else > /usr/bin/logger -t Lid Opened at `/bin/date` > /sbin/sysctl hw.acpi.video.lcd0.active=1 > fi ... I don't have 'hw.acpi.video.lcd0.active', only: # sysctl -a | fgrep hw.acpi hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S3 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: NONE hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 hw.acpi.reset_video: 0 hw.acpi.acline: 1 hw.acpi.battery.life: 80 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: 42,5C hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.passive_cooling: 0 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: -1 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 107,0C hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz0._TC1: -1 hw.acpi.thermal.tz0._TC2: -1 hw.acpi.thermal.tz0._TSP: -1 hw.acpi.cpu.cx_lowest: C1 # sysctl -a | fgrep lcd0 matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From oberman at es.net Thu Sep 10 17:28:30 2009 From: oberman at es.net (Kevin Oberman) Date: Thu Sep 10 17:28:36 2009 Subject: Dell M4400 && power-off the display on Lid close (8-CURRENT / Xorg) In-Reply-To: Your message of "Thu, 10 Sep 2009 14:14:59 +0200." <20090910121459.GA5007@current.Sisis.de> Message-ID: <20090910172822.9AF441CC37@ptavv.es.net> > Date: Thu, 10 Sep 2009 14:14:59 +0200 > From: Matthias Apitz > Sender: owner-freebsd-mobile@freebsd.org > > El día Wednesday, September 09, 2009 a las 09:46:36AM +1000, Mark Andrews escribió: > > > I call this on lid events which works even when X isn't running. :-) > > Would be nice, but ... > > > notify 10 { > > match "system" "ACPI"; > > match "subsystem" "Lid"; > > action "/etc/rc.lid $notify"; > > }; > > > > /etc/rc.lid: > > #!/bin/sh > > # deal with lid switch events > > > > if [ "x$1" = x0x00 ]; then > > /usr/bin/logger -t Lid Closed at `/bin/date` > > /sbin/sysctl hw.acpi.video.lcd0.active=0 > > else > > /usr/bin/logger -t Lid Opened at `/bin/date` > > /sbin/sysctl hw.acpi.video.lcd0.active=1 > > fi > > ... I don't have 'hw.acpi.video.lcd0.active', only: > > # sysctl -a | fgrep hw.acpi > hw.acpi.supported_sleep_state: S3 S4 S5 > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S3 > hw.acpi.lid_switch_state: NONE > hw.acpi.standby_state: NONE > hw.acpi.suspend_state: S3 > hw.acpi.sleep_delay: 1 > hw.acpi.s4bios: 1 > hw.acpi.verbose: 0 > hw.acpi.disable_on_reboot: 0 > hw.acpi.handle_reboot: 0 > hw.acpi.reset_video: 0 > hw.acpi.acline: 1 > hw.acpi.battery.life: 80 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 2 > hw.acpi.battery.units: 2 > hw.acpi.battery.info_expire: 5 > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.user_override: 0 > hw.acpi.thermal.tz0.temperature: 42,5C > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.passive_cooling: 0 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: -1 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 107,0C > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.thermal.tz0._TC1: -1 > hw.acpi.thermal.tz0._TC2: -1 > hw.acpi.thermal.tz0._TSP: -1 > hw.acpi.cpu.cx_lowest: C1 > # sysctl -a | fgrep lcd0 Are you loading acpi_video? Even if you do, if you have a Radeon, I am not sure it will turn off the back-light, but, if this is an issue, you can install the radeontool and add the appropriate commands to devd.conf in addition to the sysctl. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From guru at unixarea.de Fri Sep 11 07:06:40 2009 From: guru at unixarea.de (Matthias Apitz) Date: Fri Sep 11 07:06:47 2009 Subject: Dell M4400 && power-off the display on Lid close (8-CURRENT / Xorg) In-Reply-To: <20090910172822.9AF441CC37@ptavv.es.net> References: <20090910121459.GA5007@current.Sisis.de> <20090910172822.9AF441CC37@ptavv.es.net> Message-ID: <20090911070642.GA2253@current.Sisis.de> El d?a Thursday, September 10, 2009 a las 10:28:22AM -0700, Kevin Oberman escribi?: > Are you loading acpi_video? > > Even if you do, if you have a Radeon, I am not sure it will turn off the > back-light, but, if this is an issue, you can install the radeontool and > add the appropriate commands to devd.conf in addition to the sysctl. With loading acpi_video it works now in console mode, i.e. the LCD goes off and on on lid close/open. When I have X11 up and running (the Nvidia driver), the LCD goes off as well, but on return I only see the console message of the X11 startup-session (i.e. the console from where I launched 'startx') and I'm unable to switch to any other virtual screen and also not to the X11 session; zapping X11 with Ctrl-Alt-BS does not work either and I have had to reboot with power-off/on. Any idea? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ People who hate Microsoft Windows use Linux but people who love UNIX use FreeBSD. From eddie at angryeddie.cn Fri Sep 11 18:41:54 2009 From: eddie at angryeddie.cn (Eddie Leisure) Date: Fri Sep 11 18:42:02 2009 Subject: Problem using adhoc mode using the iwn driver. Message-ID: <4AAA96DB.7070501@angryeddie.cn> Followed the instructions per 'man iwn' I'm getting "ifconfig: SIOCIFCREATE2: Operation not supported" when I try to create the wlan0 device in adhoc mode. Environment specific information: uname -a: FreeBSD spectre.mss.iss.net 8.0-BETA3 FreeBSD 8.0-BETA3 #0: Sat Aug 22 02:36:50 UTC 2009 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 pciconf: iwn0@pci0:3:0:0: class=0x028000 card=0x10108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Wireless WiFi Link 4965AGN (Intel 4965AGN)' class = network bar [10] = type Memory, range 64, base 0xdf2fe000, size 8192, enabled cap 01[c8] = powerspec 3 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[e0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) This is what I've done: spectre# ifconfig iwn0 iwn0: flags=8802 metric 0 mtu 2290 ether 00:21:5c:15:74:6d media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier spectre# ifconfig wlan create wlandev iwn0 wlanmode adhoc ssid aenet ifconfig: SIOCIFCREATE2: Operation not supported If I don't use the 'wlanmode adhoc' option, then it works, but doesn't really do what I want. spectre# ifconfig wlan create wlandev iwn0 ssid aenet wlan0 spectre# ifconfig wlan0 up spectre# ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:21:5c:15:74:6d inet 192.168.2.25 netmask 0xffffff00 broadcast 192.168.2.255 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid aenet channel 36 (5180 Mhz 11a) country US authmode OPEN privacy OFF txpower 15 bmiss 10 mcastrate 6 mgmtrate 6 scanvalid 60 wme bintval 0 At this point, I can give it an IP address, etc... but it will say no carrier. This is my first time setting up an adhoc network, but what I can find from my searches is that this _should_ work... I feel like I may be missing something simple though. Any insight would be appreciated. Ed Leisure From onemda at gmail.com Fri Sep 11 20:28:41 2009 From: onemda at gmail.com (Paul B. Mahol) Date: Fri Sep 11 20:28:48 2009 Subject: Problem using adhoc mode using the iwn driver. In-Reply-To: <4AAA96DB.7070501@angryeddie.cn> References: <4AAA96DB.7070501@angryeddie.cn> Message-ID: <3a142e750909111328l5f3813d5xba6cf84d349f30a@mail.gmail.com> On 9/11/09, Eddie Leisure wrote: > Followed the instructions per 'man iwn' > I'm getting "ifconfig: SIOCIFCREATE2: Operation not supported" when I > try to create the wlan0 device in adhoc mode. Look at iwn source code, IBSS cap is commented out. Either this issue should be addressed or man page should be updated. -- Paul From eddie at angryeddie.cn Fri Sep 11 22:33:04 2009 From: eddie at angryeddie.cn (Eddie Leisure) Date: Fri Sep 11 22:33:11 2009 Subject: Problem using adhoc mode using the iwn driver. In-Reply-To: <3a142e750909111328l5f3813d5xba6cf84d349f30a@mail.gmail.com> References: <4AAA96DB.7070501@angryeddie.cn> <3a142e750909111328l5f3813d5xba6cf84d349f30a@mail.gmail.com> Message-ID: <4AAAD01F.1040309@angryeddie.cn> Paul B. Mahol wrote: > Look at iwn source code, IBSS cap is commented out. > Either this issue should be addressed or man page should be updated. Thanks for your help here, it never occurred to me to check the source, I'm still a bit of a newbie at this. Deleted the #if 0...#endif block around the code in if_iwn.c and recompiled. Running it form the console this time and I can see the error "iwn0: IBSS mode not supported" - so it still doesn't seem to be working. I checked over the rest of the source and I don't see anything obvious in the header files either. I think I'm dancing around my limits here, I think I'll just have to find a different way to connect this machine, or just get a usb adapter. Just to make sure I'm on track here, i did a kldunload if_iwn, then ran make, then did a kldload if_iwn - this is the first time for me to recompile a kernel module so I want to make sure I'm not messing this up. It somewhat makes sense for it not to work though, I assume theres a reason it was commented out to begin with. Eddie From sam at freebsd.org Sat Sep 12 02:48:39 2009 From: sam at freebsd.org (Sam Leffler) Date: Sat Sep 12 02:48:46 2009 Subject: Problem using adhoc mode using the iwn driver. In-Reply-To: <4AAAD01F.1040309@angryeddie.cn> References: <4AAA96DB.7070501@angryeddie.cn> <3a142e750909111328l5f3813d5xba6cf84d349f30a@mail.gmail.com> <4AAAD01F.1040309@angryeddie.cn> Message-ID: <4AAB096F.5090702@freebsd.org> Eddie Leisure wrote: > Paul B. Mahol wrote: >> Look at iwn source code, IBSS cap is commented out. >> Either this issue should be addressed or man page should be updated. > Thanks for your help here, it never occurred to me to check the source, > I'm still a bit of a newbie at this. > > Deleted the #if 0...#endif block around the code in if_iwn.c and > recompiled. > Running it form the console this time and I can see the error "iwn0: > IBSS mode not supported" - so it still doesn't seem to be working. I > checked over the rest of the source and I don't see anything obvious in > the header files either. > > I think I'm dancing around my limits here, I think I'll just have to > find a different way to connect this machine, or just get a usb adapter. > > Just to make sure I'm on track here, i did a kldunload if_iwn, then ran > make, then did a kldload if_iwn - this is the first time for me to > recompile a kernel module so I want to make sure I'm not messing this up. > > It somewhat makes sense for it not to work though, I assume theres a > reason it was commented out to begin with. iwn's ibss suport didn't work when I last tried it so I removed the capability. Someone needs to take responsibility for the driver; there are many outstanding issues with the code in the tree (e.g. lack of support for the newer (but now old) parts). Sam From jessemichaelwilson at gmail.com Sat Sep 12 20:27:09 2009 From: jessemichaelwilson at gmail.com (jesse wilson) Date: Sat Sep 12 20:27:24 2009 Subject: hp pavilion dv2500 laptop and "wpi0: radio transmitter is switched off" Message-ID: <63d995660909121259h3f86ac42w8a35f92f6208ca08@mail.gmail.com> Hi all. Just set up freebsd on an hp pavilion dv2500 and after setting up /boot/loader.conf with all the appropriate modules and the intel license agreement line ifconfig wpi0 up brings up a line that says "wpi0: radio transmitter is turned off" even though I know the switch is in the "on" position. The switch is supposed to glow blue when it's on, but it's red. pciconf -lv reports this as my wireless device: 10418086 Intel 3945ABG Wireless LAN controller. I don't have any ethernet cable and I can't get on the internet with the laptop in question right now. After doing sysctl debug.wpi=-2 followed by ifconfig wpi0 up I got this in /var/log/messages: Sep 12 11:54:25 kernel: Watchdog: tick Sep 12 11:54:33 last message repeated 8 times Sep 12 11:54:33 kernel: wpi0: could not lock memory Sep 12 11:54:33 last message repeated 2 times Sep 12 11:54:33 kernel: wpi0: timeout resetting Tx ring 1 Sep 12 11:54:33 kernel: wpi0: could not lock memory Sep 12 11:54:33 kernel: wpi0: could not lock memory Sep 12 11:54:33 kernel: wpi0: timeout resetting Tx ring 3 Sep 12 11:54:33 kernel: wpi0: could not lock memory Sep 12 11:54:33 kernel: wpi0: timeout resetting Tx ring 4 Sep 12 11:54:33 kernel: wpi0: could not lock memory Sep 12 11:54:33 kernel: wpi0: could not lock memory Sep 12 11:54:33 kernel: Disabling Firmware execution Sep 12 11:54:33 kernel: wpi_newstate: SCAN -> INIT Sep 12 11:54:33 kernel: Resetting the card - clearing any uploaded firmware Sep 12 11:54:33 kernel: Attempting Loading Firmware from wpi_fw module Sep 12 11:54:33 kernel: Firmware Version: Major 2, Minor 14, Driver 4, Sep 12 11:54:33 kernel: runtime (text: 80524, data: 32768) init (text: 2668, data 32768) boot (text 900) Sep 12 11:54:33 kernel: rtext 0xf802020 Sep 12 11:54:33 kernel: rdata 0x0 Sep 12 11:54:33 kernel: itext 0xf802020 Sep 12 11:54:33 kernel: idata 0x0 Sep 12 11:54:33 kernel: btext 0xf802020 Sep 12 11:54:33 kernel: Loading microcode size 0x384 Sep 12 11:54:33 kernel: firmware status=0xffff0000, val=0x40400000, result=0x40400000 Sep 12 11:54:33 kernel: Status Match! - ntries = 0 Sep 12 11:54:33 kernel: wpi_ops: command: 4 Sep 12 11:54:33 kernel: notify qid=80 idx=0 flags=0 type=1 len=36 Sep 12 11:54:33 kernel: microcode alive notification version 10e02 alive 1 Sep 12 11:54:33 kernel: notify qid=80 idx=0 flags=0 type=1 len=36 Sep 12 11:54:33 kernel: microcode alive notification version 10e02 alive 1 Sep 12 11:54:33 kernel: notify qid=80 idx=1 flags=0 type=161 len=8 Sep 12 11:54:33 kernel: state changed to 1 Sep 12 11:54:33 kernel: wpi0: Radio transmitter is switched off Sep 12 11:54:33 kernel: Firmware loaded to driver successfully Sep 12 11:54:33 kernel: wpi0: Radio Transmitter is switched off Sep 12 11:54:33 kernel: wpi_newstate: INIT -> SCAN Sep 12 11:54:33 kernel: wpi_cmd 72 size 8 async 1 Sep 12 11:54:33 kernel: wpi_ops: command: 1 Sep 12 11:54:33 kernel: wpi_ops: command: 2 Sep 12 11:54:34 kernel: Watchdog: tick Sep 12 11:55:00 last message repeated 26 times Sep 12 11:55:01 login: ROOT LOGIN (root) ON ttyv1 Sep 12 11:55:01 kernel: Watchdog: tick Sep 12 11:55:29 last message repeated 28 times Any help you can give me with this would be appreciated. From lambert at lambertfam.org Sun Sep 13 06:08:32 2009 From: lambert at lambertfam.org (Scott Lambert) Date: Sun Sep 13 06:08:38 2009 Subject: Problem using adhoc mode using the iwn driver. In-Reply-To: <4AAB096F.5090702@freebsd.org> References: <4AAA96DB.7070501@angryeddie.cn> <3a142e750909111328l5f3813d5xba6cf84d349f30a@mail.gmail.com> <4AAAD01F.1040309@angryeddie.cn> <4AAB096F.5090702@freebsd.org> Message-ID: <20090913054601.GH418@sysmon.tcworks.net> On Fri, Sep 11, 2009 at 07:37:35PM -0700, Sam Leffler wrote: > Eddie Leisure wrote: > > Paul B. Mahol wrote: > >> Look at iwn source code, IBSS cap is commented out. > >> Either this issue should be addressed or man page should be updated. > > Thanks for your help here, it never occurred to me to check the source, > > I'm still a bit of a newbie at this. > > > > Deleted the #if 0...#endif block around the code in if_iwn.c and > > recompiled. > > Running it form the console this time and I can see the error "iwn0: > > IBSS mode not supported" - so it still doesn't seem to be working. I > > checked over the rest of the source and I don't see anything obvious in > > the header files either. > > iwn's ibss suport didn't work when I last tried it so I removed the > capability. Someone needs to take responsibility for the driver; there > are many outstanding issues with the code in the tree (e.g. lack of > support for the newer (but now old) parts). If someone gets interested in playing with iwn, it would be great if they could work on resume. FreeBSD 8 is *wonderful* for S3 suspend and resume. I really appreciate the work which has been done to get it to work. The iwn driver is my only issue. I have put up the verbose dmesg for boot and resume if anyone is interested. http://www.lambertfam.org/~lambert/laptop/TravelMate_5720-6911/ After resume the ifconfig shows "associated" on iwn0 and "no carrier" on wlan0. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org From sam at errno.com Sun Sep 13 14:09:40 2009 From: sam at errno.com (Sam Leffler) Date: Sun Sep 13 14:09:47 2009 Subject: Problem using adhoc mode using the iwn driver. In-Reply-To: <20090913054601.GH418@sysmon.tcworks.net> References: <4AAA96DB.7070501@angryeddie.cn> <3a142e750909111328l5f3813d5xba6cf84d349f30a@mail.gmail.com> <4AAAD01F.1040309@angryeddie.cn> <4AAB096F.5090702@freebsd.org> <20090913054601.GH418@sysmon.tcworks.net> Message-ID: <4AACFD23.50800@errno.com> Scott Lambert wrote: > On Fri, Sep 11, 2009 at 07:37:35PM -0700, Sam Leffler wrote: >> Eddie Leisure wrote: >>> Paul B. Mahol wrote: >>>> Look at iwn source code, IBSS cap is commented out. >>>> Either this issue should be addressed or man page should be updated. >>> Thanks for your help here, it never occurred to me to check the source, >>> I'm still a bit of a newbie at this. >>> >>> Deleted the #if 0...#endif block around the code in if_iwn.c and >>> recompiled. >>> Running it form the console this time and I can see the error "iwn0: >>> IBSS mode not supported" - so it still doesn't seem to be working. I >>> checked over the rest of the source and I don't see anything obvious in >>> the header files either. >> iwn's ibss suport didn't work when I last tried it so I removed the >> capability. Someone needs to take responsibility for the driver; there >> are many outstanding issues with the code in the tree (e.g. lack of >> support for the newer (but now old) parts). > > If someone gets interested in playing with iwn, it would be great if > they could work on resume. FreeBSD 8 is *wonderful* for S3 suspend and > resume. I really appreciate the work which has been done to get it to > work. > > The iwn driver is my only issue. I have put up the verbose dmesg for > boot and resume if anyone is interested. > > http://www.lambertfam.org/~lambert/laptop/TravelMate_5720-6911/ > > After resume the ifconfig shows "associated" on iwn0 and "no carrier" on > wlan0. > > There is suspend/resume support in net80211; probably just requires hooking up to it. OTOH if you want to do a good job (i.e. resume quickly) then take a look at what ath does. Sam From tarkhil at over.ru Sun Sep 13 19:57:04 2009 From: tarkhil at over.ru (Alex Povolotsky) Date: Sun Sep 13 19:57:37 2009 Subject: Working xorg.conf for Radeon HD 3200/amd64? Message-ID: Hello! Does anyone have a working xorg.conf for Radeon HD 3200 (on HP Compaq 615) in amd64 mode? I'd be content with VESA driver, but I need full screen resolution. No 3D acceleration required at all, but 2D would be nice. -- ???????? ? ???????? ??????? ???????? Opera: http://www.opera.com/mail/ From jessemichaelwilson at gmail.com Tue Sep 15 19:48:00 2009 From: jessemichaelwilson at gmail.com (jesse wilson) Date: Tue Sep 15 19:48:07 2009 Subject: hp pavilion dv2500 laptop and "wpi0: radio transmitter is switched off" Message-ID: <63d995660909151247qd0645ecsca6510ea915cb803@mail.gmail.com> I had made an error in my loader.conf, loading ipw drivers instead of wpi. After fixing the error, I still get the same messages. Can anyone help? Would the version from cvs, svn or whatever repository help? Might their be a hack to turn the radio transmitter on? From henry.hu.sh at gmail.com Wed Sep 16 05:11:58 2009 From: henry.hu.sh at gmail.com (Henry Hu) Date: Wed Sep 16 05:13:46 2009 Subject: hp pavilion dv2500 laptop and "wpi0: radio transmitter is switched off" In-Reply-To: <63d995660909151247qd0645ecsca6510ea915cb803@mail.gmail.com> References: <63d995660909151247qd0645ecsca6510ea915cb803@mail.gmail.com> Message-ID: <53a1e0710909152211l4c513a4ena6e2f84cfd3631d2@mail.gmail.com> Is there any option in the bios which can change the state of the radio trasmitter? I have to set this, or else I got the "wpi0: Radio Transmitter is switched off" message too. I remember that long ago I can change the state with the accelerated key, but now I can't change it, so I can only enable the transmitter at startup. On Wed, Sep 16, 2009 at 3:47 AM, jesse wilson wrote: > I had made an error in my loader.conf, loading ipw drivers instead of wpi. After > fixing the error, I still get the same messages. Can anyone help? Would the > version from cvs, svn or whatever repository help? Might their be a hack to turn > the radio transmitter on? > _______________________________________________ > 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" >