From morganw at chemikals.org Mon Sep 1 00:13:16 2008 From: morganw at chemikals.org (Wes Morgan) Date: Mon Sep 1 00:13:22 2008 Subject: TECRA A9-S9017 -- Idles too hot -- Hardware Support In-Reply-To: <20080831223722.GC2191@WORKSTATION.guice.ath.cx> References: <489E9531.2090200@guice.ath.cx> <20080825025833.GB3301@WORKSTATION.guice.ath.cx> <20080826002657.B14827@sola.nimnet.asn.au> <20080825191804.GA6846@WORKSTATION.guice.ath.cx> <20080826182124.O14827@sola.nimnet.asn.au> <20080830210736.GA4521@WORKSTATION.guice.ath.cx> <20080831223722.GC2191@WORKSTATION.guice.ath.cx> Message-ID: On Sun, 31 Aug 2008, freebsd_user@guice.ath.cx wrote: > In addition to the above URL, other findings: > > hw.acpi.toshiba.cpu_speed=7 > hw.acpi.toshiba.force_fan=1 > hw.acpi.thermal.min_runtime=30 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.user_override=1 > hw.acpi.thermal.tz0.temperature: 61.0C # On 6.3-RELEASE -p3 - > # this value is bogus > > hw.acpi.thermal.tz0.active: -1 # Can not change > hw.acpi.thermal.tz0.passive_cooling: 0 # Can not change > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV=10.0C # passive_cooling will- > # activate @ this temp. > # Above, passive_cooling > # currently N/A. Have you tried 7.0 instead of 6.3? I can't think of any compelling reason to stick with 6.x on a laptop. > With that being said, please allow me this one (1) rhetorical > question; how is a common end-user supposed to keep his machine > running and maintain her/his sanity chasing after issues such as > we've discussed here? When dealing with a piece of hardware that was designed from the ground up with only Microsoft Windows XP or even Vista in mind, I would say that we're doing pretty well. That the two frequencies for each core disagree, could be simply rounding difference or the core may actually report differently, as you may notice that your true frequency is not 2200mhz. The ACPI temperature may be measured in a different location than the "coretemp". On my system there is not even a sysctl for the frequency of the second core. I imagine that setting each core to a different frequency could be advantageous if the scheduler was able to take advantage of this, but I wonder if some applications might be adversely effected. I would try installing 7-stable and rerunning the tests, perhaps posting the results with slightly less verbosity as each message is becoming inordinately long and cluttered with too much information. From raj at csub.edu Mon Sep 1 05:22:41 2008 From: raj at csub.edu (Russell Jackson) Date: Mon Sep 1 05:22:50 2008 Subject: Heat issues on the IBM/Lenovo T60 resolved In-Reply-To: <200808300950.51698.josh@tcbug.org> References: <200808300950.51698.josh@tcbug.org> Message-ID: <48BB74CB.4000401@csub.edu> Josh Paetzel wrote: > I've been relatively happy with my T60, with the exception of the heat issues > it's had since day one. The fan would run full out pretty much all the time, > and it would frequently reach 99-100C when doing anything cpu intensive, > regardless of OS. If there was any obstruction to the air vents it would > shutdown due to overheating. > > It turns out this is not an uncommon problem with the T60/T61, people either > complain of them being loud, or too hot, or sometimes both. > > After going down the road of OS tweaks and BIOS flashes I started burning up > phone lines at Lenovo, and I was finally able to talk to someone who said > they had some assembly problems that resulted in far too much thermal paste > being applied to the cpu and heatsink. > > So, I disassembled my laptop, and sure enough, the thermal paste was applied > much like a 3 year old applies grape jelly to a sandwich. I cleaned the > heatsink, cpu, and gpu and applied some generic thermal paste I found at Best > Buy. (caveat: The GPU uses a thermal pad that accomodates cooling the > memory chips, which are at a different height. I cut out the area where the > GPU makes contact and used thermal paste there, leaving the rest of the > thermal pad in place to contact the ram) > > Upon reassembly I loaded up both cores with make buildworld and cpuburn, and > initially feared I had damaged the fan speed sensor, as FreeBSD reported 0 > rpm. The cpu temps very slowly climbed to 60C, where the fan spun up to a > nearly inaudible 2000 rpm > > If I leave it at full CPU utilization the fan will eventually spin up to > 3000rpm, and temps stabilize at 66-69C. Under normal use the fan rarely > runs, a welcome change from it running full out all the time, especially on > battery. > > I have a friend that was having similar problems with his T61, and has had > similar success after reapplying the thermal paste. > > Fow what it's worth, Lenovo said the issue was covered under warranty, I just > disn't feel like going through the hassle of shipping the laptop to them. > Apple had the exact same issue with the Mac Books when they first came out. I just ordered a t400 yesterday (very giddy about getting rid of my Dell Inspiron POS). I'm hoping it'll just work right out of the box without having to disassemble it first. Thanks for the data point. -- Russell A. Jackson Network Analyst California State University, Bakersfield Memory fault -- brain fried From smithi at nimnet.asn.au Mon Sep 1 14:59:37 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Mon Sep 1 14:59:43 2008 Subject: TECRA A9-S9017 -- Idles too hot -- Hardware Support In-Reply-To: References: <489E9531.2090200@guice.ath.cx> <20080825025833.GB3301@WORKSTATION.guice.ath.cx> <20080826002657.B14827@sola.nimnet.asn.au> <20080825191804.GA6846@WORKSTATION.guice.ath.cx> <20080826182124.O14827@sola.nimnet.asn.au> <20080830210736.GA4521@WORKSTATION.guice.ath.cx> <20080831223722.GC2191@WORKSTATION.guice.ath.cx> Message-ID: <20080902001541.G12899@sola.nimnet.asn.au> On Sun, 31 Aug 2008, Wes Morgan wrote: > On Sun, 31 Aug 2008, freebsd_user@guice.ath.cx wrote: [..] > > hw.acpi.thermal.tz0.temperature: 61.0C # On 6.3-RELEASE -p3 - > > # this value is bogus [..] > Have you tried 7.0 instead of 6.3? I can't think of any compelling reason to > stick with 6.x on a laptop. Indeed. Getting a bit bored with this, I hunted back through the -acpi archives tonight to find the exact issue .. a refresh cycle for failing memory :) http://lists.freebsd.org/pipermail/freebsd-acpi/2008-January/thread.html has several mentions of this: the PR+patch, tested, MFC'd to 7-STABLE: http://lists.freebsd.org/pipermail/freebsd-acpi/2008-January/004380.html http://lists.freebsd.org/pipermail/freebsd-acpi/2008-January/004441.html among others, and especially: http://www.freebsd.org/cgi/query-pr.cgi?pr=114722 [..] > I would try installing 7-stable and rerunning the tests, perhaps posting the > results with slightly less verbosity as each message is becoming inordinately > long and cluttered with too much information. Too right. I expect that the chances of interesting anyone to work on merging much of the recent ACPI work back into the 6.X tree are fairly close to zero. That's all from me on this one .. cheers, Ian From webmaster at kibab.com Thu Sep 4 10:13:29 2008 From: webmaster at kibab.com (Ilya Bakulin) Date: Thu Sep 4 10:13:37 2008 Subject: [sarumont@sigil.org: Re: fprint (finger print sensor framework) port ready for testing] In-Reply-To: <20080710171907.GG1106@snobol> References: <20080710171907.GG1106@snobol> Message-ID: <20080904095751.bfd489b7.webmaster@kibab.com> On Thu, 10 Jul 2008 12:19:07 -0500 Richard Kolkovich wrote: > Forgot to reply to all... > > ----- Forwarded message from Richard Kolkovich ----- > > Date: Thu, 10 Jul 2008 10:19:09 -0500 > From: Richard Kolkovich > To: Simon Barner > Subject: Re: fprint (finger print sensor framework) port ready for testing > User-Agent: Mutt/1.5.17 (2007-11-01) > > On Mon, Apr 14, 2008 at 08:07:40PM +0200, Simon Barner wrote: > > Hi, > > > > I did a port [2] of the fprint finger print sensor framework [1] > > and would like to receive some feedback before I commit it. > > > > It comes with a PAM module for finger print based authentication, a > > graphical (fprint_demo) and a console (pam_fprint_enroll) application > > for finger print enrollment. > > > > I did my tests with the UPEK sensor found in Lenovo's T61. > > > > Simon > > > > (M'fup2 ports@) > > > > [1] http://www.reactivated.net/fprint/wiki/Main_Page > > [2] http://home.leo.org/~barner/freebsd/fprint.tar.gz > > > > -- > > Best regards / Viele Gr??e, barner@FreeBSD.org > > Simon Barner barner@gmx.de > > > Anyone had success with this on the T43p? fprint_demo doesn't detect any devices. The kernel sees it as follows: > > ugen0: on uhub2 > > From the looks of it, the STM device is not supported by fprint, but I can't find anything online that confirms or denies this. > > Thanks, > > -- > > Richard Kolkovich > sarumont@sigil.org > > > > ----- End forwarded message ----- > > -- > > Richard Kolkovich > sarumont@sigil.org > Just want to confirm, fprint-* ports work OK on Dell Vostro 1310: ugen1: on uhub0 kibab@kibab-nb%usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: full speed, power 100 mA, config 1, Biometric Coprocessor(0x2016), STMicroelectronics(0x0483), rev 0.01 After adding devfs rules and enrolling fingerprints PAM module works like a charm, thanks :-) -- Ilya Bakulin -------------- 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/20080904/60d7b2e0/attachment.pgp From engywook at gmail.com Fri Sep 5 17:42:40 2008 From: engywook at gmail.com (Daniel Andersson) Date: Fri Sep 5 17:42:46 2008 Subject: ral0: device timeout Message-ID: <24adbbc00809051017s7817323dj8e2454a78228a578@mail.gmail.com> Hi! I tried to set up my ral nic as an AP. It doesn't work though, I get: "engy# dmesg | tail ral0: device timeout ral0: device timeout ral0: device timeout ral0: device timeout ral0: device timeout ral0: device timeout ral0: device timeout ral0: device timeout ral0: device timeout ral0: device timeout" I read found some posts and a bug report (misc/117655) with the same problem I'm having but they didn't get any replies so I'm trying here. Here's a link to a bug report: http://freebsd.monkey.org/freebsd-bugs/200710/msg00374.html I'm running 7.0 Release. "engy# vmstat -i interrupt total rate irq16: em0 66100435 54 irq17: em1 938188957 780 irq18: ral0+ 32773446 27 irq20: ohci0+ 182929022 152 cpu0: timer 2404332470 1999 Total 3624324330 3014" Is there anything I can do? Upgrade to stable or current? Thanks! Daniel Andersson From torfinn.ingolfsen at broadpark.no Fri Sep 5 21:05:27 2008 From: torfinn.ingolfsen at broadpark.no (Torfinn Ingolfsen) Date: Fri Sep 5 21:05:33 2008 Subject: ral0: device timeout In-Reply-To: <24adbbc00809051017s7817323dj8e2454a78228a578@mail.gmail.com> References: <24adbbc00809051017s7817323dj8e2454a78228a578@mail.gmail.com> Message-ID: <20080905220523.3170d480.torfinn.ingolfsen@broadpark.no> On Fri, 05 Sep 2008 19:17:11 +0200 Daniel Andersson wrote: > I tried to set up my ral nic as an AP. It doesn't work though, I get: Do you have any timeouts if you run the card as a normal interface? > Here's a link to a bug report: > http://freebsd.monkey.org/freebsd-bugs/200710/msg00374.html This link works better: http://www.freebsd.org/cgi/query-pr.cgi?pr=117655 -- Regards, Torfinn Ingolfsen From engywook at gmail.com Sat Sep 6 11:32:00 2008 From: engywook at gmail.com (Daniel Andersson) Date: Sat Sep 6 11:32:06 2008 Subject: ral0: device timeout Message-ID: <24adbbc00809060431i7394f312md63b1d2f396fa27a@mail.gmail.com> >Do you have any timeouts if you run the card as a normal interface? No. I don't have access to any other AP's though so I haven't really been able to test it. > This link works better: > http://www.freebsd.org/cgi/query-pr.cgi?pr=117655 Hmm. Might be power related. The current PSU is 300W iirc. The only things connected to the box are 3 hdds, 3 nics and a geforce 2 MX. It should be able to handle it? Thanks for the reply! Daniel From raj at csub.edu Sun Sep 7 18:51:29 2008 From: raj at csub.edu (Russell Jackson) Date: Sun Sep 7 18:51:37 2008 Subject: ThinkPad T400 Message-ID: <48C41BD1.6070903@csub.edu> I received my t400 at last, and I thought I'd share my experiences with it so far. Very nice piece of hardware --to me anyway; this is my first ThinkPad. Either I'm lucky or the assembly line problems have been worked out because I'm not having the heat problems that other's have been reporting with the t4x/6x series. It runs comfortably --maybe a little warm-- on my lap even during a long compile run (under Linux; see below). This is in contrast to my previous --Dell-- laptop which would get scorching hot under the same load. Unfortunately, 7.0-RELEASE will not boot with ACPI enabled. Though it will boot without ACPI, neither the em nor ath drivers successfully probe their respective hardware. Without ACPI, I didn't even bother continuing with the installation. I tried the August 8.0-CURRENT snapshot which booted with ACPI, and the em driver seemed to support for the NIC as I was able to get a DHCP lease from sysinstall. Unfortunately --again--, the August snapshot has a bug in gnutar that prevents sysinstall from working, so I didn't actually get past sysinstall. The bug is supposedly fixed in HEAD, but there isn't a September snapshot yet. I can't figure another convenient way to get CURRENT on here; so, FreeBSD is dead in the water for me at this point unless I want build my own snapshot or somebody has a better idea... I've been running Ubuntu for the last couple of days which has more or less been working flawlessly. Suspend even works... most of the time. The only major issues I had were with madwifi and the intel xorg driver. The HAL from madwifi didn't support my card, but that was fixed building a patched snapshot that included the newly released HAL that did. The other issue was with the intel video driver hanging when using the Xv extension. That was solved by building a newer release from source. I've been impressed with the Intel video; I've never had such good quality and performance from an opensource xfree86/xorg driver before. It's nice being free from the nvidia binary blob. This laptop also has an ATI Radeon 3470 in addition to the GM45 Intel graphics, but the radeonhd driver is not yet practical, and the fglrx binary driver crashed just starting the X server. Bleh. Battery life has been incredible compared to what I was getting with my old Dell; I'd be lucky to an hour out of it tops. I'm getting 2 hours plus doing real work on this bad boy even with the tiny 4-cell battery. I'm still waiting for the 9-cell to come in. Apparently there's a world wide battery shortage causing delays. I've attached the Linux dmesg boot output and lspci -vv output for now. When I can get a working FreeBSD configuration, I'll post their equivalents. -------------- next part -------------- 00:00.0 Host bridge: Intel Corporation Cantiga Memory Controller Hub (rev 07) Subsystem: Lenovo Unknown device 20e0 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <64ns, L1 <1us Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1 Link: Latency L0s <1us, L1 <4us Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- Link: Speed 2.5Gb/s, Width x0 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+ Slot: Number 0, PowerLimit 6.500000 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Unknown, PwrInd Unknown, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Address: fee0300c Data: 41c9 Capabilities: [90] Subsystem: Lenovo Unknown device 20f3 Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <64ns, L1 <1us Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 2 Link: Latency L0s <256ns, L1 <4us Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x1 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+ Slot: Number 1, PowerLimit 6.500000 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Unknown, PwrInd Unknown, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Address: fee0300c Data: 41d1 Capabilities: [90] Subsystem: Lenovo Unknown device 20f3 Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <64ns, L1 <1us Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 4 Link: Latency L0s <1us, L1 <4us Link: ASPM L0s L1 Enabled RCB 64 bytes CommClk- ExtSynch- Link: Speed 2.5Gb/s, Width x0 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+ Slot: Number 3, PowerLimit 6.500000 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ Slot: AttnInd Unknown, PwrInd Unknown, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Address: fee0300c Data: 41d9 Capabilities: [90] Subsystem: Lenovo Unknown device 20f3 Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <64ns, L1 <1us Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 5 Link: Latency L0s <1us, L1 <4us Link: ASPM L0s L1 Enabled RCB 64 bytes CommClk- ExtSynch- Link: Speed 2.5Gb/s, Width x0 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+ Slot: Number 4, PowerLimit 6.500000 Slot: Enabled AtnBtn+ PwrFlt- MRL- PresDet+ CmdCplt- HPIrq- Slot: AttnInd Unknown, PwrInd Unknown, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [80] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Address: fee0300c Data: 41e1 Capabilities: [90] Subsystem: Lenovo Unknown device 20f3 Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo Unknown device 20f0 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [50] Subsystem: Lenovo Unknown device 20f4 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) Subsystem: Lenovo Unknown device 20f5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) (prog-if 10 [OHCI]) Subsystem: Lenovo Unknown device 20c7 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 4096 [ 0.000000] Normal 4096 -> 229376 [ 0.000000] HighMem 229376 -> 772608 [ 0.000000] Movable zone start PFN for each node [ 0.000000] early_node_map[1] active PFN ranges [ 0.000000] 0: 0 -> 772608 [ 0.000000] On node 0 totalpages: 772608 [ 0.000000] DMA zone: 32 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 4064 pages, LIFO batch:0 [ 0.000000] Normal zone: 1760 pages used for memmap [ 0.000000] Normal zone: 223520 pages, LIFO batch:31 [ 0.000000] HighMem zone: 4244 pages used for memmap [ 0.000000] HighMem zone: 538988 pages, LIFO batch:31 [ 0.000000] Movable zone: 0 pages used for memmap [ 0.000000] DMI present. [ 0.000000] ACPI: RSDP signature @ 0xC00F6550 checksum 0 [ 0.000000] ACPI: RSDP 000F6550, 0024 (r2 LENOVO) [ 0.000000] ACPI: XSDT BC96A4DE, 009C (r1 LENOVO TP-7U 1130 LTP 0) [ 0.000000] ACPI: FACP BC96A600, 00F4 (r3 LENOVO TP-7U 1130 LNVO 1) [ 0.000000] ACPI: DSDT BC96A9DB, F190 (r1 LENOVO TP-7U 1130 MSFT 3000000) [ 0.000000] ACPI: FACS BC98E000, 0040 [ 0.000000] ACPI: SSDT BC96A7B4, 0227 (r1 LENOVO TP-7U 1130 MSFT 3000000) [ 0.000000] ACPI: ECDT BC979B6B, 0052 (r1 LENOVO TP-7U 1130 LNVO 1) [ 0.000000] ACPI: APIC BC979BBD, 0078 (r1 LENOVO TP-7U 1130 LNVO 1) [ 0.000000] ACPI: MCFG BC979C35, 003C (r1 LENOVO TP-7U 1130 LNVO 1) [ 0.000000] ACPI: HPET BC979C71, 0038 (r1 LENOVO TP-7U 1130 LNVO 1) [ 0.000000] ACPI: SLIC BC979DC2, 0176 (r1 LENOVO TP-7U 1130 LTP 0) [ 0.000000] ACPI: BOOT BC979F38, 0028 (r1 LENOVO TP-7U 1130 LTP 1) [ 0.000000] ACPI: ASF! BC979F60, 00A0 (r16 LENOVO TP-7U 1130 PTL 1) [ 0.000000] ACPI: SSDT BC98D213, 054F (r1 LENOVO TP-7U 1130 INTL 20050513) [ 0.000000] ACPI: TCPA BC707000, 0032 (r0 0 0) [ 0.000000] ACPI: DMAR BC706000, 00C0 (r1  1 0) [ 0.000000] ACPI: SSDT BC6D3000, 0655 (r1 PmRef CpuPm 3000 INTL 20050624) [ 0.000000] ACPI: SSDT BC6D2000, 0274 (r1 PmRef Cpu0Tst 3000 INTL 20050624) [ 0.000000] ACPI: SSDT BC6D1000, 0242 (r1 PmRef ApTst 3000 INTL 20050624) [ 0.000000] ACPI: PM-Timer IO Port: 0x1008 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [ 0.000000] Processor #0 7:7 APIC version 20 [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [ 0.000000] Processor #1 7:7 APIC version 20 [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) [ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23 [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.000000] ACPI: IRQ0 used by override. [ 0.000000] ACPI: IRQ2 used by override. [ 0.000000] ACPI: IRQ9 used by override. [ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.000000] Using ACPI (MADT) for SMP configuration information [ 0.000000] Allocating PCI resources starting at c0000000 (gap: bf000000:21000000) [ 0.000000] swsusp: Registered nosave memory region: 000000000009e000 - 000000000009f000 [ 0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000 [ 0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 00000000000dc000 [ 0.000000] swsusp: Registered nosave memory region: 00000000000dc000 - 0000000000100000 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 766572 [ 0.000000] Kernel command line: root=/dev/mapper/sys-root ro quiet splash [ 0.000000] mapped APIC to ffffb000 (fee00000) [ 0.000000] mapped IOAPIC to ffffa000 (fec00000) [ 0.000000] Enabling fast FPU save and restore... done. [ 0.000000] Enabling unmasked SIMD FPU exception support... done. [ 0.000000] Initializing CPU#0 [ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes) [ 0.000000] Detected 2261.022 MHz processor. [ 10.042713] Console: colour VGA+ 80x25 [ 10.042719] console [tty0] enabled [ 10.043177] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 10.043734] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 10.359307] Memory: 3048256k/3090432k available (2177k kernel code, 37092k reserved, 1006k data, 368k init, 2169252k highmem) [ 10.359322] virtual kernel memory layout: [ 10.359324] fixmap : 0xfff4b000 - 0xfffff000 ( 720 kB) [ 10.359327] pkmap : 0xff800000 - 0xffc00000 (4096 kB) [ 10.359329] vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB) [ 10.359331] lowmem : 0xc0000000 - 0xf8000000 ( 896 MB) [ 10.359333] .init : 0xc0421000 - 0xc047d000 ( 368 kB) [ 10.359335] .data : 0xc03204c4 - 0xc041bdc4 (1006 kB) [ 10.359337] .text : 0xc0100000 - 0xc03204c4 (2177 kB) [ 10.359344] Checking if this processor honours the WP bit even in supervisor mode... Ok. [ 10.359409] SLUB: Genslabs=11, HWalign=64, Order=0-1, MinObjects=4, CPUs=2, Nodes=1 [ 10.359537] hpet clockevent registered [ 10.439386] Calibrating delay using timer specific routine.. 4527.61 BogoMIPS (lpj=9055225) [ 10.439423] Security Framework initialized [ 10.439433] SELinux: Disabled at boot. [ 10.439455] AppArmor: AppArmor initialized [ 10.439463] Failure registering capabilities with primary security module. [ 10.439477] Mount-cache hash table entries: 512 [ 10.439681] Initializing cgroup subsys ns [ 10.439689] Initializing cgroup subsys cpuacct [ 10.439709] CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0008e3fd 00000000 00000001 00000000 [ 10.439722] monitor/mwait feature present. [ 10.439726] using mwait in idle threads. [ 10.439733] CPU: L1 I cache: 32K, L1 D cache: 32K [ 10.439738] CPU: L2 cache: 3072K [ 10.439742] CPU: Physical Processor ID: 0 [ 10.439745] CPU: Processor Core ID: 0 [ 10.439749] CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0008e3fd 00000000 00000001 00000000 [ 10.439766] Compat vDSO mapped to ffffe000. [ 10.439789] Checking 'hlt' instruction... OK. [ 10.456206] SMP alternatives: switching to UP code [ 10.459840] Early unpacking initramfs... done [ 11.241752] ACPI: Core revision 20070126 [ 11.241924] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found. [ 11.271538] CPU0: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz stepping 06 [ 11.271567] SMP alternatives: switching to SMP code [ 11.273183] Booting processor 1/1 eip 3000 [ 11.284137] Initializing CPU#1 [ 11.361541] Calibrating delay using timer specific routine.. 4522.08 BogoMIPS (lpj=9044171) [ 11.361554] CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0008e3fd 00000000 00000001 00000000 [ 11.361564] monitor/mwait feature present. [ 11.361569] CPU: L1 I cache: 32K, L1 D cache: 32K [ 11.361573] CPU: L2 cache: 3072K [ 11.361577] CPU: Physical Processor ID: 0 [ 11.361579] CPU: Processor Core ID: 1 [ 11.361582] CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0008e3fd 00000000 00000001 00000000 [ 11.363051] CPU1: Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz stepping 06 [ 11.363089] Total of 2 processors activated (9049.69 BogoMIPS). [ 11.363277] ENABLING IO-APIC IRQs [ 11.363490] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 11.509434] checking TSC synchronization [CPU#0 -> CPU#1]: passed. [ 11.529425] Brought up 2 CPUs [ 11.529465] CPU0 attaching sched-domain: [ 11.529469] domain 0: span 03 [ 11.529473] groups: 01 02 [ 11.529479] CPU1 attaching sched-domain: [ 11.529482] domain 0: span 03 [ 11.529486] groups: 02 01 [ 11.529891] net_namespace: 64 bytes [ 11.529904] Booting paravirtualized kernel on bare hardware [ 11.530793] Time: 1:59:04 Date: 09/07/08 [ 11.530843] NET: Registered protocol family 16 [ 11.531211] EISA bus registered [ 11.531219] ACPI: bus type pci registered [ 11.532078] PCI: PCI BIOS revision 3.00 entry at 0xfddc7, last bus=24 [ 11.532083] PCI: Using configuration type 1 [ 11.532100] Setting up standard PCI resources [ 11.537873] ACPI: EC: EC description table is found, configuring boot EC [ 11.548221] ACPI: BIOS _OSI(Linux) query ignored [ 11.548226] ACPI: DMI System Vendor: LENOVO [ 11.548230] ACPI: DMI Product Name: 2764CTO [ 11.548233] ACPI: DMI Product Version: ThinkPad T400 [ 11.548236] ACPI: DMI Board Name: 2764CTO [ 11.548238] ACPI: DMI BIOS Vendor: LENOVO [ 11.548241] ACPI: DMI BIOS Date: 08/19/2008 [ 11.548244] ACPI: Please send DMI info above to linux-acpi@vger.kernel.org [ 11.548249] ACPI: If "acpi_osi=Linux" works better, please notify linux-acpi@vger.kernel.org [ 11.548573] ACPI: EC: non-query interrupt received, switching to interrupt mode [ 11.628037] ACPI: Interpreter enabled [ 11.628042] ACPI: (supports S0 S3 S4 S5) [ 11.628076] ACPI: Using IOAPIC for interrupt routing [ 11.704381] ACPI: EC: GPE = 0x11, I/O: command/status = 0x66, data = 0x62 [ 11.704387] ACPI: EC: driver started in poll mode [ 11.704751] ACPI: PCI Root Bridge [PCI0] (0000:00) [ 11.707710] PCI: Transparent bridge - 0000:00:1e.0 [ 11.707859] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 11.708307] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP0._PRT] [ 11.708589] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT] [ 11.708885] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP3._PRT] [ 11.709173] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP4._PRT] [ 11.709461] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] [ 11.717506] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11) [ 11.717962] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11) [ 11.718414] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11) [ 11.718865] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11) [ 11.719316] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 *11) [ 11.719767] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11) [ 11.720218] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 *11) [ 11.720669] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 *11) [ 11.721007] ACPI: EC: non-query interrupt received, switching to interrupt mode [ 11.721161] ACPI: Power Resource [PUBS] (on) [ 11.721296] Linux Plug and Play Support v0.97 (c) Adam Belay [ 11.721354] pnp: PnP ACPI init [ 11.721369] ACPI: bus type pnp registered [ 11.744401] pnpacpi: exceeded the max number of mem resources: 12 [ 11.788706] pnp: PnP ACPI: found 10 devices [ 11.788712] ACPI: ACPI bus type pnp unregistered [ 11.788717] PnPBIOS: Disabled by ACPI PNP [ 11.789207] PCI: Using ACPI for IRQ routing [ 11.789213] PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report [ 12.028224] NET: Registered protocol family 8 [ 12.028228] NET: Registered protocol family 20 [ 12.028290] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0 [ 12.028299] hpet0: 4 64-bit timers, 14318180 Hz [ 12.029357] AppArmor: AppArmor Filesystem Enabled [ 12.032204] Time: tsc clocksource has been installed. [ 12.032223] Switched to high resolution mode on CPU 0 [ 12.032407] Switched to high resolution mode on CPU 1 [ 12.048170] system 00:00: iomem range 0x0-0x9ffff could not be reserved [ 12.048176] system 00:00: iomem range 0xc0000-0xc3fff could not be reserved [ 12.048182] system 00:00: iomem range 0xc4000-0xc7fff could not be reserved [ 12.048187] system 00:00: iomem range 0xc8000-0xcbfff has been reserved [ 12.048192] system 00:00: iomem range 0xcc000-0xcffff has been reserved [ 12.048198] system 00:00: iomem range 0xd0000-0xd3fff could not be reserved [ 12.048203] system 00:00: iomem range 0x0-0x0 could not be reserved [ 12.048208] system 00:00: iomem range 0x0-0x0 could not be reserved [ 12.048213] system 00:00: iomem range 0xdc000-0xdffff has been reserved [ 12.048219] system 00:00: iomem range 0xe0000-0xe3fff could not be reserved [ 12.048224] system 00:00: iomem range 0xe4000-0xe7fff could not be reserved [ 12.048229] system 00:00: iomem range 0xe8000-0xebfff could not be reserved [ 12.048242] system 00:02: ioport range 0x164e-0x164f has been reserved [ 12.048248] system 00:02: ioport range 0x1000-0x107f has been reserved [ 12.048253] system 00:02: ioport range 0x1180-0x11ff has been reserved [ 12.048258] system 00:02: ioport range 0x800-0x80f has been reserved [ 12.048264] system 00:02: ioport range 0x15e0-0x15ef has been reserved [ 12.048269] system 00:02: ioport range 0x1600-0x1641 has been reserved [ 12.048274] system 00:02: ioport range 0x1600-0x161b has been reserved [ 12.048281] system 00:02: iomem range 0xe0000000-0xefffffff could not be reserved [ 12.048287] system 00:02: iomem range 0xfed1c000-0xfed1ffff could not be reserved [ 12.048293] system 00:02: iomem range 0xfed10000-0xfed13fff could not be reserved [ 12.048299] system 00:02: iomem range 0xfed18000-0xfed18fff could not be reserved [ 12.048305] system 00:02: iomem range 0xfed19000-0xfed19fff could not be reserved [ 12.048311] system 00:02: iomem range 0xfed45000-0xfed4bfff could not be reserved [ 12.079081] PCI: Bridge: 0000:00:1c.0 [ 12.079085] IO window: disabled. [ 12.079093] MEM window: disabled. [ 12.079099] PREFETCH window: disabled. [ 12.079107] PCI: Bridge: 0000:00:1c.1 [ 12.079110] IO window: disabled. [ 12.079118] MEM window: f4300000-f43fffff [ 12.079124] PREFETCH window: disabled. [ 12.079132] PCI: Bridge: 0000:00:1c.3 [ 12.079137] IO window: 2000-2fff [ 12.079145] MEM window: f8000000-f9ffffff [ 12.079152] PREFETCH window: f4000000-f40fffff [ 12.079160] PCI: Bridge: 0000:00:1c.4 [ 12.079165] IO window: 3000-3fff [ 12.079173] MEM window: fa000000-fbffffff [ 12.079180] PREFETCH window: f4100000-f41fffff [ 12.079195] PCI: Bus 22, cardbus bridge: 0000:15:00.0 [ 12.079198] IO window: 00004000-000040ff [ 12.079206] IO window: 00004400-000044ff [ 12.079213] PREFETCH window: f0000000-f3ffffff [ 12.079221] MEM window: c0000000-c3ffffff [ 12.079228] PCI: Bridge: 0000:00:1e.0 [ 12.079233] IO window: 4000-7fff [ 12.079241] MEM window: f4800000-f7ffffff [ 12.079248] PREFETCH window: f0000000-f3ffffff [ 12.079290] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 20 (level, low) -> IRQ 16 [ 12.079301] PCI: Setting latency timer of device 0000:00:1c.0 to 64 [ 12.079334] ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 21 (level, low) -> IRQ 17 [ 12.079343] PCI: Setting latency timer of device 0000:00:1c.1 to 64 [ 12.079376] ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 23 (level, low) -> IRQ 18 [ 12.079386] PCI: Setting latency timer of device 0000:00:1c.3 to 64 [ 12.079417] ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 20 (level, low) -> IRQ 16 [ 12.079426] PCI: Setting latency timer of device 0000:00:1c.4 to 64 [ 12.079446] PCI: Setting latency timer of device 0000:00:1e.0 to 64 [ 12.079470] ACPI: PCI Interrupt 0000:15:00.0[A] -> GSI 16 (level, low) -> IRQ 19 [ 12.079495] NET: Registered protocol family 2 [ 12.116075] IP route cache hash table entries: 32768 (order: 5, 131072 bytes) [ 12.116508] TCP established hash table entries: 131072 (order: 8, 1048576 bytes) [ 12.117336] TCP bind hash table entries: 65536 (order: 7, 524288 bytes) [ 12.117712] TCP: Hash tables configured (established 131072 bind 65536) [ 12.117717] TCP reno registered [ 12.128161] checking if image is initramfs... it is [ 13.662416] Freeing initrd memory: 7911k freed [ 13.662635] Simple Boot Flag at 0x35 set to 0x1 [ 13.663800] audit: initializing netlink socket (disabled) [ 13.663821] audit(1220752744.921:1): initialized [ 13.664223] highmem bounce pool size: 64 pages [ 13.668060] VFS: Disk quotas dquot_6.5.1 [ 13.668200] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 13.668435] io scheduler noop registered [ 13.668439] io scheduler anticipatory registered [ 13.668443] io scheduler deadline registered [ 13.668465] io scheduler cfq registered (default) [ 13.668484] Boot video device is 0000:00:02.0 [ 13.668882] PCI: Setting latency timer of device 0000:00:1c.0 to 64 [ 13.668958] assign_interrupt_mode Found MSI capability [ 13.669023] Allocate Port Service[0000:00:1c.0:pcie00] [ 13.669089] Allocate Port Service[0000:00:1c.0:pcie02] [ 13.669239] PCI: Setting latency timer of device 0000:00:1c.1 to 64 [ 13.669313] assign_interrupt_mode Found MSI capability [ 13.669374] Allocate Port Service[0000:00:1c.1:pcie00] [ 13.669435] Allocate Port Service[0000:00:1c.1:pcie02] [ 13.669584] PCI: Setting latency timer of device 0000:00:1c.3 to 64 [ 13.669659] assign_interrupt_mode Found MSI capability [ 13.669720] Allocate Port Service[0000:00:1c.3:pcie00] [ 13.669780] Allocate Port Service[0000:00:1c.3:pcie02] [ 13.669941] PCI: Setting latency timer of device 0000:00:1c.4 to 64 [ 13.670016] assign_interrupt_mode Found MSI capability [ 13.670076] Allocate Port Service[0000:00:1c.4:pcie00] [ 13.670142] Allocate Port Service[0000:00:1c.4:pcie02] [ 13.670588] isapnp: Scanning for PnP cards... [ 14.024522] isapnp: No Plug & Play device found [ 14.075010] Real Time Clock Driver v1.12ac [ 14.075178] hpet_resources: 0xfed00000 is busy [ 14.075253] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled [ 14.077784] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize [ 14.077907] input: Macintosh mouse button emulation as /devices/virtual/input/input0 [ 14.078088] PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 [ 14.086527] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 14.086537] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 14.105108] mice: PS/2 mouse device common for all mice [ 14.105318] EISA: Probing bus 0 at eisa.0 [ 14.105327] Cannot allocate resource for EISA slot 1 [ 14.105333] Cannot allocate resource for EISA slot 2 [ 14.105337] Cannot allocate resource for EISA slot 3 [ 14.105341] Cannot allocate resource for EISA slot 4 [ 14.105345] Cannot allocate resource for EISA slot 5 [ 14.105349] Cannot allocate resource for EISA slot 6 [ 14.105353] Cannot allocate resource for EISA slot 7 [ 14.105362] EISA: Detected 0 cards. [ 14.105368] cpuidle: using governor ladder [ 14.105371] cpuidle: using governor menu [ 14.105509] NET: Registered protocol family 1 [ 14.105557] Using IPI No-Shortcut mode [ 14.105600] registered taskstats version 1 [ 14.105813] Magic number: 8:89:963 [ 14.105822] hash matches device ttyb4 [ 14.105886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [ 14.105890] EDD information not available. [ 14.106200] Freeing unused kernel memory: 368k freed [ 14.109678] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 [ 15.525849] fuse init (API version 7.9) [ 15.570344] ACPI: SSDT BC6D6C20, 02C8 (r1 PmRef Cpu0Ist 3000 INTL 20050624) [ 15.570962] ACPI: SSDT BC6D4020, 087A (r1 PmRef Cpu0Cst 3001 INTL 20050624) [ 15.576767] Monitor-Mwait will be used to enter C-1 state [ 15.576774] Monitor-Mwait will be used to enter C-2 state [ 15.576779] Monitor-Mwait will be used to enter C-3 state [ 15.577075] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) [ 15.577085] ACPI: Processor [CPU0] (supports 8 throttling states) [ 15.577855] ACPI: SSDT BC6D5CA0, 01CF (r1 PmRef ApIst 3000 INTL 20050624) [ 15.578599] ACPI: SSDT BC6D5F20, 008D (r1 PmRef ApCst 3000 INTL 20050624) [ 15.582760] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3]) [ 15.582770] ACPI: Processor [CPU1] (supports 8 throttling states) [ 15.582800] ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126] [ 15.582821] ACPI Exception (processor_core-0816): AE_NOT_FOUND, Processor Device is not present [20070126] [ 15.586814] ACPI: Thermal Zone [THM0] (39 C) [ 15.589995] ACPI: Thermal Zone [THM1] (30 C) [ 15.625052] device-mapper: uevent: version 1.0.3 [ 15.625162] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com [ 15.964306] usbcore: registered new interface driver usbfs [ 15.964349] usbcore: registered new interface driver hub [ 15.976187] usbcore: registered new device driver usb [ 15.988203] USB Universal Host Controller Interface driver v3.0 [ 15.988292] ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 20 (level, low) -> IRQ 16 [ 15.988309] PCI: Setting latency timer of device 0000:00:1a.0 to 64 [ 15.988317] uhci_hcd 0000:00:1a.0: UHCI Host Controller [ 15.988648] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 1 [ 15.988692] uhci_hcd 0000:00:1a.0: irq 16, io base 0x00001860 [ 15.988938] usb usb1: configuration #1 chosen from 1 choice [ 15.988983] hub 1-0:1.0: USB hub found [ 15.988993] hub 1-0:1.0: 2 ports detected [ 16.092075] ACPI: PCI Interrupt 0000:00:1a.1[B] -> GSI 21 (level, low) -> IRQ 17 [ 16.092094] PCI: Setting latency timer of device 0000:00:1a.1 to 64 [ 16.092102] uhci_hcd 0000:00:1a.1: UHCI Host Controller [ 16.092143] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 2 [ 16.092185] uhci_hcd 0000:00:1a.1: irq 17, io base 0x00001880 [ 16.092396] usb usb2: configuration #1 chosen from 1 choice [ 16.092441] hub 2-0:1.0: USB hub found [ 16.092451] hub 2-0:1.0: 2 ports detected [ 16.195891] ACPI: PCI Interrupt 0000:00:1a.2[C] -> GSI 22 (level, low) -> IRQ 20 [ 16.195909] PCI: Setting latency timer of device 0000:00:1a.2 to 64 [ 16.195917] uhci_hcd 0000:00:1a.2: UHCI Host Controller [ 16.195959] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 3 [ 16.195999] uhci_hcd 0000:00:1a.2: irq 20, io base 0x000018a0 [ 16.196209] usb usb3: configuration #1 chosen from 1 choice [ 16.196255] hub 3-0:1.0: USB hub found [ 16.196265] hub 3-0:1.0: 2 ports detected [ 16.299658] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 19 [ 16.299677] PCI: Setting latency timer of device 0000:00:1d.0 to 64 [ 16.299685] uhci_hcd 0000:00:1d.0: UHCI Host Controller [ 16.299732] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 4 [ 16.299775] uhci_hcd 0000:00:1d.0: irq 19, io base 0x000018c0 [ 16.299996] usb usb4: configuration #1 chosen from 1 choice [ 16.300043] hub 4-0:1.0: USB hub found [ 16.300053] hub 4-0:1.0: 2 ports detected [ 16.403449] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 21 [ 16.403468] PCI: Setting latency timer of device 0000:00:1d.1 to 64 [ 16.403476] uhci_hcd 0000:00:1d.1: UHCI Host Controller [ 16.403524] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 5 [ 16.403565] uhci_hcd 0000:00:1d.1: irq 21, io base 0x000018e0 [ 16.403778] usb usb5: configuration #1 chosen from 1 choice [ 16.403825] hub 5-0:1.0: USB hub found [ 16.403835] hub 5-0:1.0: 2 ports detected [ 16.435234] usb 2-2: new full speed USB device using uhci_hcd and address 2 [ 16.507276] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 22 [ 16.507296] PCI: Setting latency timer of device 0000:00:1d.2 to 64 [ 16.507304] uhci_hcd 0000:00:1d.2: UHCI Host Controller [ 16.507349] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 6 [ 16.507389] uhci_hcd 0000:00:1d.2: irq 22, io base 0x00001c00 [ 16.507602] usb usb6: configuration #1 chosen from 1 choice [ 16.507651] hub 6-0:1.0: USB hub found [ 16.507662] hub 6-0:1.0: 2 ports detected [ 16.597414] usb 2-2: configuration #1 chosen from 1 choice [ 16.611442] ACPI: PCI Interrupt 0000:00:1a.7[D] -> GSI 23 (level, low) -> IRQ 18 [ 16.611465] PCI: Setting latency timer of device 0000:00:1a.7 to 64 [ 16.611472] ehci_hcd 0000:00:1a.7: EHCI Host Controller [ 16.611534] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 7 [ 16.615445] ehci_hcd 0000:00:1a.7: debug port 1 [ 16.615455] PCI: cache line size of 32 is not supported by device 0000:00:1a.7 [ 16.615473] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfc226c00 [ 16.631824] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 [ 16.632019] usb usb7: configuration #1 chosen from 1 choice [ 16.632068] hub 7-0:1.0: USB hub found [ 16.632078] hub 7-0:1.0: 6 ports detected [ 16.733114] SCSI subsystem initialized [ 16.736116] ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 19 (level, low) -> IRQ 23 [ 16.736138] PCI: Setting latency timer of device 0000:00:1d.7 to 64 [ 16.736145] ehci_hcd 0000:00:1d.7: EHCI Host Controller [ 16.736200] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 8 [ 16.740133] ehci_hcd 0000:00:1d.7: debug port 1 [ 16.740143] PCI: cache line size of 32 is not supported by device 0000:00:1d.7 [ 16.740158] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfc227000 [ 16.755574] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 [ 16.755768] usb usb8: configuration #1 chosen from 1 choice [ 16.755817] hub 8-0:1.0: USB hub found [ 16.755827] hub 8-0:1.0: 6 ports detected [ 16.801176] libata version 3.00 loaded. [ 16.859713] ACPI: PCI Interrupt 0000:15:00.1[B] -> GSI 17 (level, low) -> IRQ 21 [ 16.912406] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[f4801000-f48017ff] Max Packet=[2048] IR/IT contexts=[4/4] [ 16.917732] ahci 0000:00:1f.2: version 3.0 [ 16.917770] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 19 [ 16.917833] ahci 0000:00:1f.2: nr_ports (4) and implemented port map (0x3) don't match, using nr_ports [ 16.917839] ahci 0000:00:1f.2: forcing PORTS_IMPL to 0xf [ 17.027096] usb 2-2: USB disconnect, address 2 [ 17.266579] usb 2-2: new full speed USB device using uhci_hcd and address 3 [ 17.436774] usb 2-2: configuration #1 chosen from 1 choice [ 17.917289] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0xf impl SATA mode [ 17.917299] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part [ 17.917309] PCI: Setting latency timer of device 0000:00:1f.2 to 64 [ 17.917833] scsi0 : ahci [ 17.918241] scsi1 : ahci [ 17.918553] scsi2 : ahci [ 17.918834] scsi3 : ahci [ 17.920611] ata1: SATA max UDMA/133 abar m2048@0xfc226000 port 0xfc226100 irq 219 [ 17.920618] ata2: SATA max UDMA/133 abar m2048@0xfc226000 port 0xfc226180 irq 219 [ 17.920624] ata3: SATA max UDMA/133 abar m2048@0xfc226000 port 0xfc226200 irq 219 [ 17.920629] ata4: SATA max UDMA/133 abar m2048@0xfc226000 port 0xfc226280 irq 219 [ 18.185468] ieee1394: Host added: ID:BUS[0-00:1023] GUID[00061b032a2f8c15] [ 18.231616] Clocksource tsc unstable (delta = -19337252550 ns) [ 18.235700] Time: hpet clocksource has been installed. [ 18.256351] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 18.256826] ata1.00: ATA-8: HITACHI HTS722016K9SA00, DCDZC75A, max UDMA/133 [ 18.256834] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 18.257603] ata1.00: configured for UDMA/133 [ 18.307144] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 18.325927] ata2.00: ATAPI: HL-DT-STCD-RW/DVD DRIVE MU10N, 1.05, max UDMA/33 [ 18.339787] ata2.00: configured for UDMA/33 [ 18.373737] ata3: SATA link down (SStatus 0 SControl 0) [ 18.413413] ata4: SATA link down (SStatus 0 SControl 0) [ 18.413724] scsi 0:0:0:0: Direct-Access ATA HITACHI HTS72201 DCDZ PQ: 0 ANSI: 5 [ 18.415407] scsi 1:0:0:0: CD-ROM HL-DT-ST RW/DVD MU10N 1.05 PQ: 0 ANSI: 5 [ 18.439317] Driver 'sd' needs updating - please use bus_type methods [ 18.439449] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [ 18.439472] sd 0:0:0:0: [sda] Write Protect is off [ 18.439477] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 18.439509] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 18.439592] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [ 18.439613] sd 0:0:0:0: [sda] Write Protect is off [ 18.439618] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 18.439651] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 18.439657] sda:<4>Driver 'sr' needs updating - please use bus_type methods [ 18.492532] sda1 sda2 sda3 < sda5 sda6 > [ 18.501693] sd 0:0:0:0: [sda] Attached SCSI disk [ 18.511859] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 18.511898] sr 1:0:0:0: Attached scsi generic sg1 type 5 [ 18.521885] sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray [ 18.521893] Uniform CD-ROM driver Revision: 3.20 [ 18.521983] sr 1:0:0:0: Attached scsi CD-ROM sr0 [ 18.968072] Attempting manual resume [ 18.968079] swsusp: Resume From Partition 254:1 [ 18.968082] PM: Checking swsusp image. [ 18.968334] PM: Resume from disk failed. [ 18.998663] kjournald starting. Commit interval 5 seconds [ 18.998684] EXT3-fs: mounted filesystem with ordered data mode. [ 22.319047] Linux agpgart interface v0.102 [ 22.405483] agpgart: Detected an Intel Intel Integrated Graphics Device Chipset. [ 22.409662] agpgart: Detected 32252K stolen memory. [ 22.542592] e1000e-ich9m: Intel(R) PRO/1000 Network Driver - 0.2.9.5 [ 22.542599] e1000e-ich9m: Copyright (c) 1999-2008 Intel Corporation. [ 22.590446] agpgart: AGP aperture is 256M @ 0xd0000000 [ 22.591199] ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 16 [ 22.591219] PCI: Setting latency timer of device 0000:00:19.0 to 64 [ 22.712887] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:21:86:61:30:eb [ 22.712894] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection [ 22.712930] 0000:00:19.0: eth0: MAC: 5, PHY: 8, PBA No: 1008ff-0ff [ 22.794113] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 22.862240] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 23.689484] input: Power Button (FF) as /devices/virtual/input/input2 [ 23.713135] ACPI: Power Button (FF) [PWRF] [ 23.713260] input: Lid Switch as /devices/virtual/input/input3 [ 23.713588] ACPI: Lid Switch [LID] [ 23.713728] input: Sleep Button (CM) as /devices/virtual/input/input4 [ 23.732048] ACPI: Sleep Button (CM) [SLPB] [ 24.316076] ACPI: WMI-Acer: Mapper loaded [ 24.697020] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input5 [ 24.719071] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [ 24.722204] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:07/LNXVIDEO:01/input/input6 [ 24.754974] ACPI: Video Device [VID1] (multi-head: yes rom: no post: no) [ 24.940079] ACPI: PCI Interrupt 0000:00:1b.0[B] -> GSI 17 (level, low) -> IRQ 21 [ 24.940115] PCI: Setting latency timer of device 0000:00:1b.0 to 64 [ 25.009014] ath_hal: module license 'Proprietary' taints kernel. [ 25.042486] ath_hal: 0.10.5.6 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) [ 25.190130] wlan: svn r3698 [ 25.332839] ath_pci: svn r3698 [ 25.333029] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 21 [ 25.333048] PCI: Setting latency timer of device 0000:03:00.0 to 64 [ 25.823519] MadWifi: ath_attach: HAL managed transmit power control (TPC) disabled. [ 25.823545] MadWifi: ath_attach: Interference mitigation is supported. Currently disabled. [ 25.910460] ACPI: AC Adapter [AC] (off-line) [ 25.991931] ACPI: Battery Slot [BAT0] (battery present) [ 26.560209] Bluetooth: Core ver 2.11 [ 26.578403] NET: Registered protocol family 31 [ 26.578408] Bluetooth: HCI device and connection manager initialized [ 26.578415] Bluetooth: HCI socket layer initialized [ 26.622265] Bluetooth: HCI USB driver ver 2.9 [ 26.623927] usbcore: registered new interface driver hci_usb [ 27.332933] input: PC Speaker as /devices/platform/pcspkr/input/input7 [ 27.727802] MadWifi: ath_attach: Switching rfkill capability off. [ 27.795861] ath_rate_sample: 1.2 (svn r3698) [ 27.797309] wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps [ 27.797320] wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps [ 27.797338] wifi0: H/W encryption support: WEP AES AES_CCM TKIP [ 27.797347] wifi0: Atheros AR2425 chip found (MAC 14.2, PHY SChip 7.0, Radio 10.2) [ 27.797357] wifi0: Use hw queue 1 for WME_AC_BE traffic [ 27.797361] wifi0: Use hw queue 0 for WME_AC_BK traffic [ 27.797365] wifi0: Use hw queue 2 for WME_AC_VI traffic [ 27.797369] wifi0: Use hw queue 3 for WME_AC_VO traffic [ 27.797372] wifi0: Use hw queue 4 for XR traffic [ 27.797376] wifi0: Use hw queue 7 for UAPSD traffic [ 27.797380] wifi0: Use hw queue 8 for CAB traffic [ 27.797383] wifi0: Use hw queue 9 for beacons [ 27.812134] Non-volatile memory driver v1.2 [ 27.851039] ath_pci: wifi0: Atheros 5424/2424: mem=0xf4300000, irq=21 [ 27.851098] Yenta: CardBus bridge found at 0000:15:00.0 [17aa:20c6] [ 27.977251] Yenta: ISA IRQ mask 0x0cb8, PCI irq 19 [ 27.977258] Socket status: 30000006 [ 27.977263] pcmcia: parent PCI bridge I/O window: 0x4000 - 0x7fff [ 27.977268] cs: IO port probe 0x4000-0x7fff: clean. [ 27.979399] pcmcia: parent PCI bridge Memory window: 0xf4800000 - 0xf7ffffff [ 27.979404] pcmcia: parent PCI bridge Memory window: 0xf0000000 - 0xf3ffffff [ 28.297779] Synaptics Touchpad, model: 1, fw: 7.0, id: 0x1c0b1, caps: 0xd04791/0xb00000 [ 28.297791] serio: Synaptics pass-through port at isa0060/serio1/input0 [ 28.339270] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8 [ 28.390215] thinkpad_acpi: ThinkPad ACPI Extras v0.17 [ 28.390220] thinkpad_acpi: http://ibm-acpi.sf.net/ [ 28.390224] thinkpad_acpi: ThinkPad BIOS 7UET43WW (1.13 ), EC 7VHT12WW-1.01 [ 28.390228] thinkpad_acpi: Lenovo ThinkPad T400 [ 28.390833] thinkpad_acpi: radio switch found; radios are enabled [ 28.399727] thinkpad_acpi: standard ACPI backlight interface available, not loading native one... [ 28.400176] input: ThinkPad Extra Buttons as /devices/virtual/input/input9 [ 29.860364] cs: IO port probe 0x100-0x3af: clean. [ 29.862635] cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [ 29.863634] cs: IO port probe 0x820-0x8ff: clean. [ 29.864427] cs: IO port probe 0xc00-0xcf7: clean. [ 29.865498] cs: IO port probe 0xa00-0xaff: clean. [ 30.009920] loop: module loaded [ 30.091379] lp: driver loaded but no devices found [ 30.357025] Adding 4194296k swap on /dev/mapper/sys-swap. Priority:-1 extents:1 across:4194296k [ 30.416903] EXT3 FS on dm-0, internal journal [ 30.586262] kjournald starting. Commit interval 5 seconds [ 30.587542] EXT3 FS on sda2, internal journal [ 30.587556] EXT3-fs: mounted filesystem with ordered data mode. [ 30.599247] kjournald starting. Commit interval 5 seconds [ 30.599548] EXT3 FS on dm-3, internal journal [ 30.599560] EXT3-fs: mounted filesystem with ordered data mode. [ 30.606631] kjournald starting. Commit interval 5 seconds [ 30.608631] EXT3 FS on dm-4, internal journal [ 30.608642] EXT3-fs: mounted filesystem with ordered data mode. [ 30.615583] kjournald starting. Commit interval 5 seconds [ 30.615937] EXT3 FS on dm-2, internal journal [ 30.615948] EXT3-fs: mounted filesystem with ordered data mode. [ 31.522261] ip_tables: (C) 2000-2006 Netfilter Core Team From barisgerze at gmail.com Sat Sep 13 00:08:18 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Sat Sep 13 00:08:24 2008 Subject: Pavilion BTX boot Problem Message-ID: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> I am using AMD 64 bit pavilion laptop. ( dv6xxxx series ) with amd64bit edition it works ( boot and install ) but with i386 edition i cannot boot coz gives me BTX error I both tried with ACPI enabled and disabled but resulting same error.. The same error was fixed with FreeBSD 7.0 Stable brunch so why it still continue with 7.1 again? What is work around and how can i Report it to FreeBSD GNAT Error database? could you give me the link ? Thx From jhs at berklix.org Sat Sep 13 13:49:22 2008 From: jhs at berklix.org (Julian Stacey) Date: Sat Sep 13 13:49:31 2008 Subject: Pavilion BTX boot Problem In-Reply-To: Your message "Sat, 13 Sep 2008 02:38:52 +0300." <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> Message-ID: <200809131330.m8DDU1bt079176@fire.js.berklix.net> > ........................how can i Report it to FreeBSD GNAT Error database? > could you give me the link ? run man dmesg ; dmesg Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From gaijin.k at gmail.com Sat Sep 13 13:50:26 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sat Sep 13 13:50:32 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <20080828002919.GA54169@alpha.local> References: <20080828002919.GA54169@alpha.local> Message-ID: <1221313811.1305.15.camel@RabbitsDen> On Thu, 2008-08-28 at 01:29 +0100, Rui Paulo wrote: > Hi, > We've updated ath_hal in HEAD to 0.10.5.10. This supports a couple of > new chips, namely those on the Asus Eee PC, MacBooks and other laptops. > > If you have an Atheros or Atheros based card, I really wanted you to > test it. We were unable to test this in several Atheros chipsets, so > if you find a regression, please contact me or Sam Leffler > (sam@freebsd.org) ASAP. > So, please give it a try :-) I don't know if it is necessarily useful thing to report, but I have pulled it into RELENG_7 (as of August 29th) and so far I have not seen lookups, which were my regular fare with 0.9.20.3 and powerd. I see a lot of "bogus rix..." and "bogus ndx0..." messages flying by, but since nobody promised that this should work on RELENG_7, I don't think they are worth reporting ;) My hardware is ThinkPad X60: Sep 13 09:30:26 RabbitsDen kernel: ath_hal: 0.10.5.10 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) Sep 13 09:30:27 RabbitsDen kernel: ath0: mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on pci3 Sep 13 09:30:27 RabbitsDen kernel: ath0: [ITHREAD] Sep 13 09:30:27 RabbitsDen kernel: ath0: WARNING: using obsoleted if_watchdog interface Sep 13 09:30:27 RabbitsDen kernel: ath0: Ethernet address: xx:xx:xx:xx:xx:xx Sep 13 09:30:27 RabbitsDen kernel: ath0: mac 10.3 phy 6.1 radio 10.2 > > Unfortuntely, this will only make 7.1 if the release date slips. So, > don't expect this to be MFCed any time soon. Those having troubles with 0.9.x.x should be able to pull it in without much difficulty, at least to give it a try. Thank you very much for doing this work! -- Alexandre "Sunny" Kovalenko (????????? ?????????) From rpaulo at FreeBSD.org Sat Sep 13 14:54:27 2008 From: rpaulo at FreeBSD.org (Rui Paulo) Date: Sat Sep 13 14:54:38 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <1221313811.1305.15.camel@RabbitsDen> References: <20080828002919.GA54169@alpha.local> <1221313811.1305.15.camel@RabbitsDen> Message-ID: <20080913145145.GA13435@alpha.local> On Sat, Sep 13, 2008 at 09:50:11AM -0400, Alexandre Sunny Kovalenko wrote: > On Thu, 2008-08-28 at 01:29 +0100, Rui Paulo wrote: > > Hi, > > We've updated ath_hal in HEAD to 0.10.5.10. This supports a couple of > > new chips, namely those on the Asus Eee PC, MacBooks and other laptops. > > > > If you have an Atheros or Atheros based card, I really wanted you to > > test it. We were unable to test this in several Atheros chipsets, so > > if you find a regression, please contact me or Sam Leffler > > (sam@freebsd.org) ASAP. > > So, please give it a try :-) > I don't know if it is necessarily useful thing to report, but I have > pulled it into RELENG_7 (as of August 29th) and so far I have not seen > lookups, which were my regular fare with 0.9.20.3 and powerd. Yes, I think I had them too sometimes. > I see a lot of "bogus rix..." and "bogus ndx0..." messages flying by, > but since nobody promised that this should work on RELENG_7, I don't > think they are worth reporting ;) They happen to me on HEAD too (but I think they are harmless). Regards, -- Rui Paulo From freebsd_user at guice.ath.cx Sun Sep 14 00:00:16 2008 From: freebsd_user at guice.ath.cx (freebsd_user@guice.ath.cx) Date: Sun Sep 14 00:00:23 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO Message-ID: <20080913234149.GA2420@6281.guice.ath.cx> MACHINE: THINKPAD T61P MACHINE TYPE: 6459-CTO NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) - FreeBSD 7.0-RELEASE i386 <== fresh install - ==> What FreeBSD see's: ==> /var/run/dmesg.boot ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: mem 0xd7df0000-0xd7dfffff irq 17 at device 0.0 on pci3 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:1f:3a:4d:45:d1 ath0: mac 10.3 phy 6.1 radio 10.2 ==> pciconf -l -v |grep -i atheros vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' ==> kldstat Id Refs Address Size Name 1 4 0xc0400000 906518 kernel 2 2 0xc0d07000 6a32c acpi.ko 3 1 0xc70e9000 5000 acpi_ibm.ko ==> Attempting to get the wireless nic online: ==> We're not sure what chipset is involved here. All we have in the way of identification for this wireless device is what we see from another machine with windows installed. ath0: flags=8843 metric 0 mtu 1500 ether 00:1f:3a:4d:45:d1 inet 192.168.1.111 netmask 0xe1ffff00 broadcast 222.168.1.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: no carrier ssid SORRY channel 34 (5170 Mhz 11a) authmode OPEN privacy OFF txpower 31.5 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 burst This machine has both and led for bluetooth and wireless nic; both are hardware controlled with a power switch to simultanesously turn them off and on. While this hardware switch is 'on' during boot/reboot, the 'bluetooth' led is lit while the wireless nic led is off. In an attempt to get the wireless nic (Atheros) online/connected we did the following: sysctl dev.acpi_ibm.0.bluetooth=1 dev.acpi_ibm.0.bluetooth: 1 -> 0 # Bluetooth led goes off; wireless nic remains off; fn+f5 key doesn't do a thing even though acpi_ibm is loaded. The device continues to not connect to the LAN via the ath0 (Atheros). From smithi at nimnet.asn.au Sun Sep 14 03:48:17 2008 From: smithi at nimnet.asn.au (Ian Smith) Date: Sun Sep 14 03:48:25 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO In-Reply-To: <20080913234149.GA2420@6281.guice.ath.cx> References: <20080913234149.GA2420@6281.guice.ath.cx> Message-ID: <20080914133429.B439@sola.nimnet.asn.au> On Sat, 13 Sep 2008, freebsd_user@guice.ath.cx wrote: > MACHINE: THINKPAD T61P > MACHINE TYPE: 6459-CTO > NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) > - > FreeBSD 7.0-RELEASE i386 <== fresh install > - > ==> What FreeBSD see's: > ==> /var/run/dmesg.boot > > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > ath0: mem 0xd7df0000-0xd7dfffff irq 17 at device 0.0 on pci3 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:1f:3a:4d:45:d1 > ath0: mac 10.3 phy 6.1 radio 10.2 > > ==> pciconf -l -v |grep -i atheros > vendor = 'Atheros Communications Inc.' > device = 'AR5212 Atheros AR5212 802.11abg wireless' > > ==> kldstat > Id Refs Address Size Name > 1 4 0xc0400000 906518 kernel > 2 2 0xc0d07000 6a32c acpi.ko > 3 1 0xc70e9000 5000 acpi_ibm.ko > > ==> Attempting to get the wireless nic online: > ==> We're not sure what chipset is involved here. All > we have in the way of identification for this wireless > device is what we see from another machine with windows > installed. Looks rather like an Atheros AR5212 :) > ath0: flags=8843 metric 0 mtu 1500 > ether 00:1f:3a:4d:45:d1 > inet 192.168.1.111 netmask 0xe1ffff00 broadcast 222.168.1.255 For starters, this netmask (and thus, broadcast address) is rubbish. What's your ifconfig setup for this interface in /etc/rc.conf? cheers, Ian > media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) > status: no carrier > ssid SORRY channel 34 (5170 Mhz 11a) > authmode OPEN privacy OFF txpower 31.5 bmiss 7 scanvalid 60 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 burst [..] From oberman at es.net Sun Sep 14 04:23:36 2008 From: oberman at es.net (Kevin Oberman) Date: Sun Sep 14 04:23:42 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO In-Reply-To: Your message of "Sat, 13 Sep 2008 19:43:01 EDT." <20080913234149.GA2420@6281.guice.ath.cx> Message-ID: <20080914041229.85F1B4500F@ptavv.es.net> > Date: Sat, 13 Sep 2008 19:43:01 -0400 > From: freebsd_user@guice.ath.cx > Sender: owner-freebsd-mobile@freebsd.org > > MACHINE: THINKPAD T61P > MACHINE TYPE: 6459-CTO > NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) > - > FreeBSD 7.0-RELEASE i386 <== fresh install > - > ==> What FreeBSD see's: > ==> /var/run/dmesg.boot > > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > ath0: mem 0xd7df0000-0xd7dfffff irq 17 at device 0.0 on pci3 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:1f:3a:4d:45:d1 > ath0: mac 10.3 phy 6.1 radio 10.2 > > ==> pciconf -l -v |grep -i atheros > vendor = 'Atheros Communications Inc.' > device = 'AR5212 Atheros AR5212 802.11abg wireless' > > ==> kldstat > Id Refs Address Size Name > 1 4 0xc0400000 906518 kernel > 2 2 0xc0d07000 6a32c acpi.ko > 3 1 0xc70e9000 5000 acpi_ibm.ko > > ==> Attempting to get the wireless nic online: > ==> We're not sure what chipset is involved here. All > we have in the way of identification for this wireless > device is what we see from another machine with windows > installed. Looks like an Atheros AR5212. Same as the one in my Thinkpad. > ath0: flags=8843 metric 0 mtu 1500 > ether 00:1f:3a:4d:45:d1 > inet 192.168.1.111 netmask 0xe1ffff00 broadcast 222.168.1.255 > media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) > status: no carrier > ssid SORRY channel 34 (5170 Mhz 11a) > authmode OPEN privacy OFF txpower 31.5 bmiss 7 scanvalid 60 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 burst How are you configuring this? The netmask is bogus. e1ffff00? Very weird! If it is a static address, try "ifconfig ath0 192.168.1.111/24". You may also need to set the default route with "route add default 192.168.1.1" (The last digit may need to be changed if your router is not at .1) If it is DHCP configured, fix your DHCP server! > This machine has both and led for bluetooth and > wireless nic; both are hardware controlled with a power > switch to simultanesously turn them off and on. While > this hardware switch is 'on' during boot/reboot, the > 'bluetooth' led is lit while the wireless nic led is > off. > > In an attempt to get the wireless nic (Atheros) > online/connected we did the following: > > sysctl dev.acpi_ibm.0.bluetooth=1 > dev.acpi_ibm.0.bluetooth: 1 -> 0 > > # Bluetooth led goes off; wireless nic remains off; > fn+f5 key doesn't do a thing even though acpi_ibm is > loaded. Nope, turning the bluetooth off and on will have no effect on the atheros and, unlike on Windows, the ath driver only turns on the LED when it is transmitting, so, if it's misconfigured so that it does not transmit, the LED will not light at all. > > The device continues to not connect to the LAN via the > ath0 (Atheros). With that configuration, I would not expect it to do so. -- 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080914/99cc5c19/attachment.pgp From freebsd_user at guice.ath.cx Sun Sep 14 06:51:42 2008 From: freebsd_user at guice.ath.cx (freebsd_user@guice.ath.cx) Date: Sun Sep 14 06:51:48 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO In-Reply-To: <20080914133429.B439@sola.nimnet.asn.au> References: <20080913234149.GA2420@6281.guice.ath.cx> <20080914133429.B439@sola.nimnet.asn.au> Message-ID: <20080914065050.GA16724@WORKSTATION.guice.ath.cx> On Sun, Sep 14, 2008 at 01:48:13PM +1000, Ian Smith wrote: > On Sat, 13 Sep 2008, freebsd_user@guice.ath.cx wrote: > > MACHINE: THINKPAD T61P > > MACHINE TYPE: 6459-CTO > > NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) > > - > > FreeBSD 7.0-RELEASE i386 <== fresh install > > - > > ==> pciconf -l -v |grep -i atheros > > vendor = 'Atheros Communications Inc.' > > device = 'AR5212 Atheros AR5212 802.11abg wireless' > > > > Looks rather like an Atheros AR5212 :) > > > ath0: flags=8843 metric 0 mtu 1500 > > ether 00:1f:3a:4d:45:d1 > > inet 192.168.1.111 netmask 0xe1ffff00 broadcast 222.168.1.255 > > For starters, this netmask (and thus, broadcast address) is rubbish. > > What's your ifconfig setup for this interface in /etc/rc.conf? Nothing for 'ath0' in /etc/rc.conf. I configured from the CLI: ifconfig ath0 inet 192.168.1.111 netmask 255.255.255.0 I was doing so while my em0 was connected to the same LAN with an ip of: 192.168.1.6 netmask 255.255.255.0 <== this is not the way I planned on using the devices. I only want to use the 'ath0' unless the situation calls for cable. I'm also not sure what to read about setting up 'WPA' and/or 'WEP' or, if the device/driver will auto-detect. I've even went as far as to disconnect the 'em0' with no positive results from the 'ath0'. From lambert at lambertfam.org Sun Sep 14 07:53:22 2008 From: lambert at lambertfam.org (Scott Lambert) Date: Sun Sep 14 07:53:29 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO In-Reply-To: <20080914065050.GA16724@WORKSTATION.guice.ath.cx> References: <20080913234149.GA2420@6281.guice.ath.cx> <20080914133429.B439@sola.nimnet.asn.au> <20080914065050.GA16724@WORKSTATION.guice.ath.cx> Message-ID: <20080914071603.GA2463@sysmon.tcworks.net> On Sun, Sep 14, 2008 at 02:50:50AM -0400, freebsd_user@guice.ath.cx wrote: > On Sun, Sep 14, 2008 at 01:48:13PM +1000, Ian Smith wrote: > > On Sat, 13 Sep 2008, freebsd_user@guice.ath.cx wrote: > > > MACHINE: THINKPAD T61P > > > MACHINE TYPE: 6459-CTO > > > NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) > > > - > > > FreeBSD 7.0-RELEASE i386 <== fresh install > > > - > > > ==> pciconf -l -v |grep -i atheros > > > vendor = 'Atheros Communications Inc.' > > > device = 'AR5212 Atheros AR5212 802.11abg wireless' > > > > > > > Looks rather like an Atheros AR5212 :) > > > > > ath0: flags=8843 metric 0 mtu 1500 > > > ether 00:1f:3a:4d:45:d1 > > > inet 192.168.1.111 netmask 0xe1ffff00 broadcast 222.168.1.255 > > > > For starters, this netmask (and thus, broadcast address) is rubbish. > > > > What's your ifconfig setup for this interface in /etc/rc.conf? > > Nothing for 'ath0' in /etc/rc.conf. I configured from the CLI: > ifconfig ath0 inet 192.168.1.111 netmask > 255.255.255.0 Unfortunately, you seem to have made a small typographical error in the first octet of the netmask and actually entered: ifconfig ath0 inet 192.168.1.111 netmask 225.255.255.0 > I was doing so while my em0 was connected to > the same LAN with an ip of: 192.168.1.6 netmask > 255.255.255.0 <== this is not the way I planned > on using the devices. I only want to use the > 'ath0' unless the situation calls for cable. > > I'm also not sure what to read about setting up > 'WPA' and/or 'WEP' or, if the device/driver > will auto-detect. Run 'man 8 ifconfig' to begin with. You may want to follow that up with 'apropos wpa' to get a list of man pages which deal with WPA. > I've even went as far as to disconnect the > 'em0' with no positive results from the 'ath0'. Due to the typographical error, you didn't have much chance of it working. You don't say that you set the default route once you disconnected the LAN cable. That will be necessary for access beyond the LAN. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org From freebsd_user at guice.ath.cx Sun Sep 14 08:04:32 2008 From: freebsd_user at guice.ath.cx (freebsd_user@guice.ath.cx) Date: Sun Sep 14 08:04:38 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO In-Reply-To: <20080914071603.GA2463@sysmon.tcworks.net> References: <20080913234149.GA2420@6281.guice.ath.cx> <20080914133429.B439@sola.nimnet.asn.au> <20080914065050.GA16724@WORKSTATION.guice.ath.cx> <20080914071603.GA2463@sysmon.tcworks.net> Message-ID: <20080914080421.GA1668@6281.guice.ath.cx> > > > > MACHINE: THINKPAD T61P > > > > MACHINE TYPE: 6459-CTO > > > > NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) > > > > - > > > > FreeBSD 7.0-RELEASE i386 <== fresh install > > > > - > > > > ==> pciconf -l -v |grep -i atheros > > > > vendor = 'Atheros Communications Inc.' > > > > device = 'AR5212 Atheros AR5212 802.11abg wireless' > > > > > > > > > > I was doing so while my em0 was connected to > > the same LAN with an ip of: 192.168.1.6 netmask > > 255.255.255.0 <== this is not the way I planned > > on using the devices. I only want to use the > > 'ath0' unless the situation calls for cable. > > > > I'm also not sure what to read about setting up > > 'WPA' and/or 'WEP' or, if the device/driver > > will auto-detect. > > > You don't say that you set the default route once you disconnected the > LAN cable. That will be necessary for access beyond the LAN. What I post below was currently done without disconnecting the LAN cable. FreeBSD 7.0-RELEASE-p4 i386 GENERIC == /etc/rc.conf | grep route defaultrouter="192.168.1.1" == Not configured ath0: flags=8802 metric 0 mtu 1500 ether 00:1f:3a:4d:45:d1 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 Mhz 11b) authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11b 7 roam:rate11b 1 burst bintval 0 ifconfig ath0 "DHCP" <== assigned my external IP to the ath0 :-\ ath0: flags=8843 metric 0 mtu 1500 ether 00:1f:3a:4d:45:d1 inet 72.225.169.69 netmask 0xff000000 broadcast 72.255.255.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) status: no carrier ssid SORRY channel 42 (5210 Mhz 11a) authmode OPEN privacy OFF txpower 31.5 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 burst With regard to the above IP being set to 72.225.169.69; the routers' DHCP server appears to be working fine with other machines using cable and one (1) windows machine (another T61p Atheros 5212) on the same network. Its only this one, topic of discuss machine, that gets the external IP assigned to it when in fact the outside world see's this 72.225.169.69. ifconfig ath0 inet 192.168.1.111 netmask 255.255.255.0 ssid SORRY ath0: flags=8843 metric 0 mtu 1500 ether 00:1f:3a:4d:45:d1 inet 192.168.1.111 netmask 0xffffff00 broadcast 192.168.1.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) status: no carrier ssid SORRY channel 40 (5200 Mhz 11a) authmode OPEN privacy OFF txpower 31.5 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 roam:rate11a 12 burst I trust there are no typo's in this msg. Thank you for pointing out ... From gaijin.k at gmail.com Sun Sep 14 13:54:55 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sun Sep 14 13:55:02 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO In-Reply-To: <20080914080421.GA1668@6281.guice.ath.cx> References: <20080913234149.GA2420@6281.guice.ath.cx> <20080914133429.B439@sola.nimnet.asn.au> <20080914065050.GA16724@WORKSTATION.guice.ath.cx> <20080914071603.GA2463@sysmon.tcworks.net> <20080914080421.GA1668@6281.guice.ath.cx> Message-ID: <1221400388.1305.40.camel@RabbitsDen> On Sun, 2008-09-14 at 04:04 -0400, freebsd_user@guice.ath.cx wrote: > > > > > MACHINE: THINKPAD T61P > > > > > MACHINE TYPE: 6459-CTO > > > > > NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) > > > > > - > > > > > FreeBSD 7.0-RELEASE i386 <== fresh install > > > > > - > > > > > ==> pciconf -l -v |grep -i atheros > > > > > vendor = 'Atheros Communications Inc.' > > > > > device = 'AR5212 Atheros AR5212 802.11abg wireless' > > > > > > > > > > > > > > I was doing so while my em0 was connected to > > > the same LAN with an ip of: 192.168.1.6 netmask > > > 255.255.255.0 <== this is not the way I planned > > > on using the devices. I only want to use the > > > 'ath0' unless the situation calls for cable. > > > > > > I'm also not sure what to read about setting up > > > 'WPA' and/or 'WEP' or, if the device/driver > > > will auto-detect. > > > > > > You don't say that you set the default route once you disconnected the > > LAN cable. That will be necessary for access beyond the LAN. > > What I post below was currently done without disconnecting the LAN cable. > > FreeBSD 7.0-RELEASE-p4 i386 GENERIC > == > /etc/rc.conf | grep route > defaultrouter="192.168.1.1" > == > > Not configured > ath0: flags=8802 metric 0 mtu 1500 > ether 00:1f:3a:4d:45:d1 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 Mhz 11b) > authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi11b 7 roam:rate11b 1 burst > bintval 0 > > ifconfig ath0 "DHCP" <== assigned my external IP to the ath0 :-\ > ath0: flags=8843 > metric 0 mtu 1500 > ether 00:1f:3a:4d:45:d1 > inet 72.225.169.69 netmask 0xff000000 broadcast > 72.255.255.255 > media: IEEE 802.11 Wireless Ethernet autoselect > (OFDM/36Mbps) > status: no carrier > ssid SORRY channel 42 (5210 Mhz 11a) > authmode OPEN privacy OFF txpower 31.5 bmiss 7 > scanvalid 60 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 > roam:rate11a 12 burst > > With regard to the above IP being set to 72.225.169.69; > the routers' DHCP server appears to be working fine with other > machines using cable and one (1) windows machine (another T61p > Atheros 5212) on the same network. Its only this one, > topic of discuss machine, that gets the external IP > assigned to it when in fact the outside world see's > this 72.225.169.69. > > ifconfig ath0 inet 192.168.1.111 netmask 255.255.255.0 ssid SORRY > ath0: flags=8843 metric 0 mtu 1500 > ether 00:1f:3a:4d:45:d1 > inet 192.168.1.111 netmask 0xffffff00 broadcast 192.168.1.255 > media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) > status: no carrier What does 'ifconfig ath0 list scan' say? Do you know parameters of the base station you are trying to associate with? Few notes: -- on my ThinkPad X60, I have not seen wireless led lit up yet, which never prevented wireless from working ;) -- there is a setting for Fn-F5 (only available through Windows), I always keep it as "Turn all radios on or of" or some such thing. -- there is a slider switch located at the front of my X60 which does kill all radios, I do not know whether T61 has one or not. If it does, you might want to check its position. -- Alexandre "Sunny" Kovalenko (????????? ?????????) From sam at freebsd.org Sun Sep 14 20:07:50 2008 From: sam at freebsd.org (Sam Leffler) Date: Sun Sep 14 20:07:56 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO In-Reply-To: <1221400388.1305.40.camel@RabbitsDen> References: <20080913234149.GA2420@6281.guice.ath.cx> <20080914133429.B439@sola.nimnet.asn.au> <20080914065050.GA16724@WORKSTATION.guice.ath.cx> <20080914071603.GA2463@sysmon.tcworks.net> <20080914080421.GA1668@6281.guice.ath.cx> <1221400388.1305.40.camel@RabbitsDen> Message-ID: <48CD6F15.5050004@freebsd.org> Alexandre "Sunny" Kovalenko wrote: > On Sun, 2008-09-14 at 04:04 -0400, freebsd_user@guice.ath.cx wrote: > >>>>> > MACHINE: THINKPAD T61P >>>>> > MACHINE TYPE: 6459-CTO >>>>> > NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) >>>>> > - >>>>> > FreeBSD 7.0-RELEASE i386 <== fresh install >>>>> > - >>>>> > ==> pciconf -l -v |grep -i atheros >>>>> > vendor = 'Atheros Communications Inc.' >>>>> > device = 'AR5212 Atheros AR5212 802.11abg wireless' >>>>> > >>>>> >>>>> >>>> I was doing so while my em0 was connected to >>>> the same LAN with an ip of: 192.168.1.6 netmask >>>> 255.255.255.0 <== this is not the way I planned >>>> on using the devices. I only want to use the >>>> 'ath0' unless the situation calls for cable. >>>> >>>> I'm also not sure what to read about setting up >>>> 'WPA' and/or 'WEP' or, if the device/driver >>>> will auto-detect. >>>> >>> You don't say that you set the default route once you disconnected the >>> LAN cable. That will be necessary for access beyond the LAN. >>> >> What I post below was currently done without disconnecting the LAN cable. >> >> FreeBSD 7.0-RELEASE-p4 i386 GENERIC >> == >> /etc/rc.conf | grep route >> defaultrouter="192.168.1.1" >> == >> >> Not configured >> ath0: flags=8802 metric 0 mtu 1500 >> ether 00:1f:3a:4d:45:d1 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> ssid "" channel 1 (2412 Mhz 11b) >> authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 bgscan >> bgscanintvl 300 bgscanidle 250 roam:rssi11b 7 roam:rate11b 1 burst >> bintval 0 >> >> ifconfig ath0 "DHCP" <== assigned my external IP to the ath0 :-\ >> ath0: flags=8843 >> metric 0 mtu 1500 >> ether 00:1f:3a:4d:45:d1 >> inet 72.225.169.69 netmask 0xff000000 broadcast >> 72.255.255.255 >> media: IEEE 802.11 Wireless Ethernet autoselect >> (OFDM/36Mbps) >> status: no carrier >> ssid SORRY channel 42 (5210 Mhz 11a) >> authmode OPEN privacy OFF txpower 31.5 bmiss 7 >> scanvalid 60 bgscan >> bgscanintvl 300 bgscanidle 250 roam:rssi11a 7 >> roam:rate11a 12 burst >> >> With regard to the above IP being set to 72.225.169.69; >> the routers' DHCP server appears to be working fine with other >> machines using cable and one (1) windows machine (another T61p >> Atheros 5212) on the same network. Its only this one, >> topic of discuss machine, that gets the external IP >> assigned to it when in fact the outside world see's >> this 72.225.169.69. >> >> ifconfig ath0 inet 192.168.1.111 netmask 255.255.255.0 ssid SORRY >> ath0: flags=8843 metric 0 mtu 1500 >> ether 00:1f:3a:4d:45:d1 >> inet 192.168.1.111 netmask 0xffffff00 broadcast 192.168.1.255 >> media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) >> status: no carrier >> > What does 'ifconfig ath0 list scan' say? Do you know parameters of the > base station you are trying to associate with? > > Few notes: > -- on my ThinkPad X60, I have not seen wireless led lit up yet, which > never prevented wireless from working ;) > -- there is a setting for Fn-F5 (only available through Windows), I > always keep it as "Turn all radios on or of" or some such thing. > -- there is a slider switch located at the front of my X60 which does > kill all radios, I do not know whether T61 has one or not. If it does, > you might want to check its position. > > If you have a 5416/5418 part I think the led is driven by the driver using the gpio pins. If you have the 0.10.5.10 hal you can try: sysctl dev.ath.0.softled=1 It may also be necessary to toggle the polarity of the gpio pins; if the led doesn't operate right away (when wireless is working) then check the nearby sysctl knobs. rfkill processing has never been fully implemented in the ath driver. Vendors implement this in various ways and sometimes it's wired s.t. the driver is not involved. On some laptops the rfkill switch is wired to a gpio pin and pushing the button generates an interrupt that ath can field--but when I tried to get it working on Robert Watson's laptop long ago it didn't work right so I never committed the mods. Sam From freebsd_user at guice.ath.cx Sun Sep 14 21:00:15 2008 From: freebsd_user at guice.ath.cx (freebsd_user@guice.ath.cx) Date: Sun Sep 14 21:00:22 2008 Subject: ATHEROS -- 802.11a/b/g Wireless Lan Mini PCI Express -- 6459-CTO In-Reply-To: <48CD6F15.5050004@freebsd.org> References: <20080913234149.GA2420@6281.guice.ath.cx> <20080914133429.B439@sola.nimnet.asn.au> <20080914065050.GA16724@WORKSTATION.guice.ath.cx> <20080914071603.GA2463@sysmon.tcworks.net> <20080914080421.GA1668@6281.guice.ath.cx> <1221400388.1305.40.camel@RabbitsDen> <48CD6F15.5050004@freebsd.org> Message-ID: <20080914205951.GA5030@6281.guice.ath.cx> On Sun, Sep 14, 2008 at 01:07:49PM -0700, Sam Leffler wrote: > Alexandre "Sunny" Kovalenko wrote: > >On Sun, 2008-09-14 at 04:04 -0400, freebsd_user@guice.ath.cx wrote: > > > >>>>> > MACHINE: THINKPAD T61P > >>>>> > MACHINE TYPE: 6459-CTO > >>>>> > NETWORK ADAPTER: 11a/b/g Wireless Lan Mini PCI Express (windows) > >>>>> > - > >>>>> > FreeBSD 7.0-RELEASE i386 <== fresh install FreeBSD 7.0-RELEASE-p4 i386 GENERIC > >>>>> > - > >>>>> > ==> pciconf -l -v |grep -i atheros > >>>>> > vendor = 'Atheros Communications Inc.' > >>>>> > device = 'AR5212 Atheros AR5212 802.11abg wireless' > >>== > >>/etc/rc.conf | grep route > >>defaultrouter="192.168.1.1" > >>== > >> > >> > >What does 'ifconfig ath0 list scan' say? Do you know parameters of the > >base station you are trying to associate with? ifconfig ath0 list scan: lists numerous access points including the one of which We're attempting to connect. > > > >Few notes: > >-- on my ThinkPad X60, I have not seen wireless led lit up yet, which > >never prevented wireless from working ;) This is a good thing; working :-) > >-- there is a setting for Fn-F5 (only available through Windows), This is news to me, thank you. > > I always keep it as "Turn all radios on or of" or some such thing. > >-- there is a slider switch located at the front of my X60 which does > >kill all radios, I do not know whether T61 has one or not. If it does, > >you might want to check its position. Switch (all radios) is on, this is why the 'bluetooth' led lights. > > > > > If you have a 5416/5418 part I think the led is driven by the driver > using the gpio pins. If you have the 0.10.5.10 hal you can try: When you say 5416/5418 I'm assuming your speaking about the Atheros device? If so this machine has a 5212. > > sysctl dev.ath.0.softled=1 > > It may also be necessary to toggle the polarity of the gpio pins; if the > led doesn't operate right away (when wireless is working) then check the > nearby sysctl knobs. The above 'softled' knob had no affect. there were at least 2-other knobs that did have an affect on the 'led' only. I'd rather concentrate on the tx/rx of the device itself. It now appears the device is partially functioning because the 'list scan' sees other access points nearby... Agreed? > rfkill processing has never been fully implemented in the ath driver. > Vendors implement this in various ways and sometimes it's wired s.t. the > driver is not involved. On some laptops the rfkill switch is wired to a > gpio pin and pushing the button generates an interrupt that ath can > field--but when I tried to get it working on Robert Watson's laptop long > ago it didn't work right so I never committed the mods. > > Sam ==> On this T61p mach-type 6459-CTO, here are the sysctl knobs that have had a visible effect (off/flicker/on) for the wireless nic led only (Atheros) and not the bluetooth led. Once I toggled these knobs the hardware switch was not able to turn the led off again and neither were the knobs that turned the wireless nic's led on. I'll see what happens after rebooting the machine; whether the led returns to 'off'. At this point I'll assume the device is working while in FreeBSD and I'll try and configure WPA to see if this is the current issue I need to resolve, that is unless you see something here I have overlooked. > > _______________________________________________ > 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 hpcharles at gmail.com Mon Sep 15 14:30:36 2008 From: hpcharles at gmail.com (Henri-Pierre Charles) Date: Mon Sep 15 14:30:42 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <20080828002919.GA54169@alpha.local> References: <20080828002919.GA54169@alpha.local> Message-ID: <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> Hi, On Thu, Aug 28, 2008 at 2:29 AM, Rui Paulo wrote: > We've updated ath_hal in HEAD to 0.10.5.10. This supports a couple of > new chips, namely those on the Asus Eee PC, MacBooks and other laptops. It's included into 8.0-CURRENT-200809-i386 snapshot if I understand correctly. > If you have an Atheros or Atheros based card, I really wanted you to > test it. We were unable to test this in several Atheros chipsets, so > if you find a regression, please contact me or Sam Leffler > (sam@freebsd.org) ASAP. I've tried 7.1-BETA and 8.0-CURRENT-200809 on my eeepc model 701 7.1 does not recognize ath0, as expected, but 8.0-CURRENT does. The corresponding dmesg can be found here : * http://www.prism.uvsq.fr/~hpc/pmwiki/uploads/Data/dmesg-7.1-BETA.txt * http://www.prism.uvsq.fr/~hpc/pmwiki/uploads/Data/dmesg-8.0-200809.txt The 8.0-CURRENT-200809-i386 contain ath_hal 0.10.5.10 but I was unable to use the interface. "dhclient ath0" never give up. Let me know if I can try something. In the past I had success with 7.0 code base + madwifi-ng-r2756+ar5007.hal I was able to use ath with dhclient and wpa_supplicant. And what about the rj45 interface for eee 701 ? Any chance to be supported in a near future ? -- HPC From jhb at freebsd.org Mon Sep 15 19:28:44 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Sep 15 19:28:51 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> Message-ID: <200809151412.23403.jhb@freebsd.org> On Friday 12 September 2008 07:38:52 pm Baris Gerze wrote: > I am using AMD 64 bit pavilion laptop. ( dv6xxxx series ) > > with amd64bit edition it works ( boot and install ) > > but with i386 edition i cannot boot coz gives me BTX error > > I both tried with ACPI enabled and disabled but resulting same error.. > > The same error was fixed with FreeBSD 7.0 Stable brunch > > so why it still continue with 7.1 again? Do you have more details on how it was broken and then fixed in 7.0? -- John Baldwin From barisgerze at gmail.com Tue Sep 16 00:46:03 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Tue Sep 16 00:46:33 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <200809151412.23403.jhb@freebsd.org> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809151412.23403.jhb@freebsd.org> Message-ID: <28e7ba930809151745x3684c694i30847bcf04422abc@mail.gmail.com> Two or three months ago I tried to boot from FBSD 7.0-STABLE install CD , it boots but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of some characters such as 00 12 12 00 12 12 00 00 etc.. all tests were made with i386 version of fbsd. laptop is amd64 pavilion. when booting ubuntu linux it also says something like PCI BUG found in the first screen but then boots normally you could trace the error by comparing 7.0 stable with 7.1 ( i386 ) FBSD install iso images.. On Mon, Sep 15, 2008 at 9:12 PM, John Baldwin wrote: > On Friday 12 September 2008 07:38:52 pm Baris Gerze wrote: > > I am using AMD 64 bit pavilion laptop. ( dv6xxxx series ) > > > > with amd64bit edition it works ( boot and install ) > > > > but with i386 edition i cannot boot coz gives me BTX error > > > > I both tried with ACPI enabled and disabled but resulting same error.. > > > > The same error was fixed with FreeBSD 7.0 Stable brunch > > > > so why it still continue with 7.1 again? > > Do you have more details on how it was broken and then fixed in 7.0? > > -- > John Baldwin > From barisgerze at gmail.com Tue Sep 16 00:46:56 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Tue Sep 16 00:47:07 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809151745x3684c694i30847bcf04422abc@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809151412.23403.jhb@freebsd.org> <28e7ba930809151745x3684c694i30847bcf04422abc@mail.gmail.com> Message-ID: <28e7ba930809151746l6be88a89u24d7cf5e7e7754af@mail.gmail.com> I also submitted this to http://www.freebsd.org/cgi/query-pr.cgi?pr=127337 thx for your concern On Tue, Sep 16, 2008 at 3:45 AM, Baris Gerze wrote: > > Two or three months ago I tried to boot from FBSD 7.0-STABLE install CD , > it boots > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of some > characters > such as > 00 12 12 00 > 12 12 00 00 etc.. > > all tests were made with i386 version of fbsd. > laptop is amd64 pavilion. > > when booting ubuntu linux it also says something like PCI BUG found in the > first screen but then boots normally > > you could trace the error by comparing 7.0 stable with 7.1 ( i386 ) FBSD > install iso images.. > > > > > On Mon, Sep 15, 2008 at 9:12 PM, John Baldwin wrote: > >> On Friday 12 September 2008 07:38:52 pm Baris Gerze wrote: >> > I am using AMD 64 bit pavilion laptop. ( dv6xxxx series ) >> > >> > with amd64bit edition it works ( boot and install ) >> > >> > but with i386 edition i cannot boot coz gives me BTX error >> > >> > I both tried with ACPI enabled and disabled but resulting same error.. >> > >> > The same error was fixed with FreeBSD 7.0 Stable brunch >> > >> > so why it still continue with 7.1 again? >> >> Do you have more details on how it was broken and then fixed in 7.0? >> >> -- >> John Baldwin >> > > From hpcharles at gmail.com Tue Sep 16 09:23:31 2008 From: hpcharles at gmail.com (Henri-Pierre Charles) Date: Tue Sep 16 09:23:42 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> References: <20080828002919.GA54169@alpha.local> <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> Message-ID: <4734a3ed0809160223p6ddc6fd5pacb901ea9dfccfe3@mail.gmail.com> Hello, (I reply to myself) On Mon, Sep 15, 2008 at 3:59 PM, Henri-Pierre Charles wrote: > Hi, > > On Thu, Aug 28, 2008 at 2:29 AM, Rui Paulo wrote: >> We've updated ath_hal in HEAD to 0.10.5.10. This supports a couple of >> new chips, namely those on the Asus Eee PC, MacBooks and other laptops. > > It's included into 8.0-CURRENT-200809-i386 snapshot if I understand correctly. > I've tried 7.1-BETA and 8.0-CURRENT-200809 on my eeepc model 701 > > 7.1 does not recognize ath0, as expected, but 8.0-CURRENT does. > The corresponding dmesg can be found here : > > * http://www.prism.uvsq.fr/~hpc/pmwiki/uploads/Data/dmesg-7.1-BETA.txt > * http://www.prism.uvsq.fr/~hpc/pmwiki/uploads/Data/dmesg-8.0-200809.txt > > The 8.0-CURRENT-200809-i386 contain ath_hal 0.10.5.10 but I was unable > to use the interface. "dhclient ath0" never give up. Let me know if I > can try something. I discover a "new" way to configure network interface, with wlan I have tried to put in my rc.conf: wlans_ath0=wlan0 ifconfig_wlan0="WPA DHCP" And .. it works, with a WPA2 configuration and also with only DHCP. Conclusion 8-0-CURRENT-200809 work out of the box for the eeepc 701. The only documentation I have found is http://people.freebsd.org/~sam/BSDCan2005.pdf . Is there something more substantial ? > And what about the rj45 interface for eee 701 ? Any chance to be supported > in a near future ? Any tips ? H-P -- HPC From vince at unsane.co.uk Tue Sep 16 09:52:19 2008 From: vince at unsane.co.uk (Vincent Hoffman) Date: Tue Sep 16 09:52:38 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <4734a3ed0809160223p6ddc6fd5pacb901ea9dfccfe3@mail.gmail.com> References: <20080828002919.GA54169@alpha.local> <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> <4734a3ed0809160223p6ddc6fd5pacb901ea9dfccfe3@mail.gmail.com> Message-ID: <48CF81CE.2070608@unsane.co.uk> Henri-Pierre Charles wrote: > Hello, (I reply to myself) > > On Mon, Sep 15, 2008 at 3:59 PM, Henri-Pierre Charles > wrote: > >> Hi, >> >> On Thu, Aug 28, 2008 at 2:29 AM, Rui Paulo wrote: >> >>> We've updated ath_hal in HEAD to 0.10.5.10. This supports a couple of >>> new chips, namely those on the Asus Eee PC, MacBooks and other laptops. >>> >> It's included into 8.0-CURRENT-200809-i386 snapshot if I understand correctly. >> I've tried 7.1-BETA and 8.0-CURRENT-200809 on my eeepc model 701 >> >> 7.1 does not recognize ath0, as expected, but 8.0-CURRENT does. >> The corresponding dmesg can be found here : >> >> * http://www.prism.uvsq.fr/~hpc/pmwiki/uploads/Data/dmesg-7.1-BETA.txt >> * http://www.prism.uvsq.fr/~hpc/pmwiki/uploads/Data/dmesg-8.0-200809.txt >> >> The 8.0-CURRENT-200809-i386 contain ath_hal 0.10.5.10 but I was unable >> to use the interface. "dhclient ath0" never give up. Let me know if I >> can try something. >> > > I discover a "new" way to configure network interface, with wlan > I have tried to put in my rc.conf: > wlans_ath0=wlan0 > ifconfig_wlan0="WPA DHCP" > > And .. it works, with a WPA2 configuration and also with only DHCP. > Conclusion 8-0-CURRENT-200809 work out of the box for the eeepc 701. > > The only documentation I have found is > http://people.freebsd.org/~sam/BSDCan2005.pdf . Is there something > more substantial ? > > /usr/src/UPDATING check the 20080420 entry. Always check this when updating your sources unless you read every mail on the current@ mailing list and even then its worth checking it. Vince >> And what about the rj45 interface for eee 701 ? Any chance to be supported >> in a near future ? >> > > Any tips ? > > H-P > > From jhb at freebsd.org Tue Sep 16 19:49:16 2008 From: jhb at freebsd.org (John Baldwin) Date: Tue Sep 16 19:52:09 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809151745x3684c694i30847bcf04422abc@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809151412.23403.jhb@freebsd.org> <28e7ba930809151745x3684c694i30847bcf04422abc@mail.gmail.com> Message-ID: <200809161124.55683.jhb@freebsd.org> On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: > Two or three months ago I tried to boot from FBSD 7.0-STABLE install CD , it > boots > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of some > characters > such as > 00 12 12 00 > 12 12 00 00 etc.. I would need the screen dump (a photo can work) to debug this at all. > all tests were made with i386 version of fbsd. > laptop is amd64 pavilion. > > when booting ubuntu linux it also says something like PCI BUG found in the > first screen but then boots normally > > you could trace the error by comparing 7.0 stable with 7.1 ( i386 ) FBSD > install iso images.. I don't have the hardware, so I can't debug this using that method. Can you narrow down approximately when 7.x broke? -- John Baldwin From barisgerze at gmail.com Tue Sep 16 20:54:15 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Tue Sep 16 21:00:15 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <200809161124.55683.jhb@freebsd.org> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809151412.23403.jhb@freebsd.org> <28e7ba930809151745x3684c694i30847bcf04422abc@mail.gmail.com> <200809161124.55683.jhb@freebsd.org> Message-ID: <28e7ba930809161354q174673f2sd0973d57dba3e756@mail.gmail.com> Image files attached. I dont know the exact fix date for FREEBSD 7.0 - Stable brunch for the boot problem What can cause the problem ? with / without acpi result is the same.. On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin wrote: > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: > > Two or three months ago I tried to boot from FBSD 7.0-STABLE install CD , > it > > boots > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of some > > characters > > such as > > 00 12 12 00 > > 12 12 00 00 etc.. > > I would need the screen dump (a photo can work) to debug this at all. > > > all tests were made with i386 version of fbsd. > > laptop is amd64 pavilion. > > > > when booting ubuntu linux it also says something like PCI BUG found in > the > > first screen but then boots normally > > > > you could trace the error by comparing 7.0 stable with 7.1 ( i386 ) FBSD > > install iso images.. > > I don't have the hardware, so I can't debug this using that method. Can > you > narrow down approximately when 7.x broke? > > -- > John Baldwin > From jhb at freebsd.org Wed Sep 17 17:44:01 2008 From: jhb at freebsd.org (John Baldwin) Date: Wed Sep 17 17:44:08 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809161354q174673f2sd0973d57dba3e756@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809161124.55683.jhb@freebsd.org> <28e7ba930809161354q174673f2sd0973d57dba3e756@mail.gmail.com> Message-ID: <200809171318.25679.jhb@freebsd.org> On Tuesday 16 September 2008 04:54:08 pm Baris Gerze wrote: > Image files attached. > > I dont know the exact fix date for FREEBSD 7.0 - Stable brunch for the boot > problem > > What can cause the problem ? > with / without acpi result is the same.. Err, not having 'device pci' in your kernel is not likely to give a working kernel in general. Are you booting from a 7.1 kernel you built or from a 7.1 install CD? Can you try booting from GENERIC? > On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin wrote: > > > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: > > > Two or three months ago I tried to boot from FBSD 7.0-STABLE install CD , > > it > > > boots > > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of some > > > characters > > > such as > > > 00 12 12 00 > > > 12 12 00 00 etc.. > > > > I would need the screen dump (a photo can work) to debug this at all. > > > > > all tests were made with i386 version of fbsd. > > > laptop is amd64 pavilion. > > > > > > when booting ubuntu linux it also says something like PCI BUG found in > > the > > > first screen but then boots normally > > > > > > you could trace the error by comparing 7.0 stable with 7.1 ( i386 ) FBSD > > > install iso images.. > > > > I don't have the hardware, so I can't debug this using that method. Can > > you > > narrow down approximately when 7.x broke? > > > > -- > > John Baldwin > > > -- John Baldwin From barisgerze at gmail.com Wed Sep 17 19:53:04 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Wed Sep 17 19:53:14 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <200809171318.25679.jhb@freebsd.org> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809161124.55683.jhb@freebsd.org> <28e7ba930809161354q174673f2sd0973d57dba3e756@mail.gmail.com> <200809171318.25679.jhb@freebsd.org> Message-ID: <28e7ba930809171253k7c36c994j4f71aa684e661a@mail.gmail.com> I am booting from FreeBSD 7.1 - Beta Install CD... how can I boot from GENERIC.. I do wanna fresh install from install boot cd... On Wed, Sep 17, 2008 at 8:18 PM, John Baldwin wrote: > On Tuesday 16 September 2008 04:54:08 pm Baris Gerze wrote: > > Image files attached. > > > > I dont know the exact fix date for FREEBSD 7.0 - Stable brunch for the > boot > > problem > > > > What can cause the problem ? > > with / without acpi result is the same.. > > Err, not having 'device pci' in your kernel is not likely to give a working > kernel in general. Are you booting from a 7.1 kernel you built or from a > 7.1 > install CD? Can you try booting from GENERIC? > > > On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin wrote: > > > > > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: > > > > Two or three months ago I tried to boot from FBSD 7.0-STABLE install > CD , > > > it > > > > boots > > > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of some > > > > characters > > > > such as > > > > 00 12 12 00 > > > > 12 12 00 00 etc.. > > > > > > I would need the screen dump (a photo can work) to debug this at all. > > > > > > > all tests were made with i386 version of fbsd. > > > > laptop is amd64 pavilion. > > > > > > > > when booting ubuntu linux it also says something like PCI BUG found > in > > > the > > > > first screen but then boots normally > > > > > > > > you could trace the error by comparing 7.0 stable with 7.1 ( i386 ) > FBSD > > > > install iso images.. > > > > > > I don't have the hardware, so I can't debug this using that method. > Can > > > you > > > narrow down approximately when 7.x broke? > > > > > > -- > > > John Baldwin > > > > > > > > > -- > John Baldwin > From barisgerze at gmail.com Wed Sep 17 20:30:42 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Wed Sep 17 20:30:50 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809171253k7c36c994j4f71aa684e661a@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809161124.55683.jhb@freebsd.org> <28e7ba930809161354q174673f2sd0973d57dba3e756@mail.gmail.com> <200809171318.25679.jhb@freebsd.org> <28e7ba930809171253k7c36c994j4f71aa684e661a@mail.gmail.com> Message-ID: <28e7ba930809171330rf3ecdb2nbd0a86491a52680d@mail.gmail.com> John, Please look at, you can find previos fix for 7.0-stable brunch... http://www.nabble.com/HP-Pavilion-dv2000-laptop-wont-boot-off-install-cd-td18479606.html Thx On Wed, Sep 17, 2008 at 10:53 PM, Baris Gerze wrote: > > I am booting from FreeBSD 7.1 - Beta Install CD... > how can I boot from GENERIC.. I do wanna fresh install from install boot > cd... > > > > On Wed, Sep 17, 2008 at 8:18 PM, John Baldwin wrote: > >> On Tuesday 16 September 2008 04:54:08 pm Baris Gerze wrote: >> > Image files attached. >> > >> > I dont know the exact fix date for FREEBSD 7.0 - Stable brunch for the >> boot >> > problem >> > >> > What can cause the problem ? >> > with / without acpi result is the same.. >> >> Err, not having 'device pci' in your kernel is not likely to give a >> working >> kernel in general. Are you booting from a 7.1 kernel you built or from a >> 7.1 >> install CD? Can you try booting from GENERIC? >> >> > On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin wrote: >> > >> > > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: >> > > > Two or three months ago I tried to boot from FBSD 7.0-STABLE install >> CD , >> > > it >> > > > boots >> > > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of some >> > > > characters >> > > > such as >> > > > 00 12 12 00 >> > > > 12 12 00 00 etc.. >> > > >> > > I would need the screen dump (a photo can work) to debug this at all. >> > > >> > > > all tests were made with i386 version of fbsd. >> > > > laptop is amd64 pavilion. >> > > > >> > > > when booting ubuntu linux it also says something like PCI BUG found >> in >> > > the >> > > > first screen but then boots normally >> > > > >> > > > you could trace the error by comparing 7.0 stable with 7.1 ( i386 ) >> FBSD >> > > > install iso images.. >> > > >> > > I don't have the hardware, so I can't debug this using that method. >> Can >> > > you >> > > narrow down approximately when 7.x broke? >> > > >> > > -- >> > > John Baldwin >> > > >> > >> >> >> >> -- >> John Baldwin >> > > From jhb at freebsd.org Wed Sep 17 21:18:28 2008 From: jhb at freebsd.org (John Baldwin) Date: Wed Sep 17 21:18:35 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809171253k7c36c994j4f71aa684e661a@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809171318.25679.jhb@freebsd.org> <28e7ba930809171253k7c36c994j4f71aa684e661a@mail.gmail.com> Message-ID: <200809171622.14451.jhb@freebsd.org> On Wednesday 17 September 2008 03:53:01 pm Baris Gerze wrote: > I am booting from FreeBSD 7.1 - Beta Install CD... > how can I boot from GENERIC.. I do wanna fresh install from install boot > cd... Erm, the install CD's are using GENERIC. I have no idea why it thinks your kernel doesn't include 'device pci'. I think you must have a corrupted CD or some such. > On Wed, Sep 17, 2008 at 8:18 PM, John Baldwin wrote: > > > On Tuesday 16 September 2008 04:54:08 pm Baris Gerze wrote: > > > Image files attached. > > > > > > I dont know the exact fix date for FREEBSD 7.0 - Stable brunch for the > > boot > > > problem > > > > > > What can cause the problem ? > > > with / without acpi result is the same.. > > > > Err, not having 'device pci' in your kernel is not likely to give a working > > kernel in general. Are you booting from a 7.1 kernel you built or from a > > 7.1 > > install CD? Can you try booting from GENERIC? > > > > > On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin wrote: > > > > > > > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: > > > > > Two or three months ago I tried to boot from FBSD 7.0-STABLE install > > CD , > > > > it > > > > > boots > > > > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of some > > > > > characters > > > > > such as > > > > > 00 12 12 00 > > > > > 12 12 00 00 etc.. > > > > > > > > I would need the screen dump (a photo can work) to debug this at all. > > > > > > > > > all tests were made with i386 version of fbsd. > > > > > laptop is amd64 pavilion. > > > > > > > > > > when booting ubuntu linux it also says something like PCI BUG found > > in > > > > the > > > > > first screen but then boots normally > > > > > > > > > > you could trace the error by comparing 7.0 stable with 7.1 ( i386 ) > > FBSD > > > > > install iso images.. > > > > > > > > I don't have the hardware, so I can't debug this using that method. > > Can > > > > you > > > > narrow down approximately when 7.x broke? > > > > > > > > -- > > > > John Baldwin > > > > > > > > > > > > > > > -- > > John Baldwin > > > -- John Baldwin From jhb at freebsd.org Wed Sep 17 21:18:40 2008 From: jhb at freebsd.org (John Baldwin) Date: Wed Sep 17 21:18:52 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809171330rf3ecdb2nbd0a86491a52680d@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <28e7ba930809171253k7c36c994j4f71aa684e661a@mail.gmail.com> <28e7ba930809171330rf3ecdb2nbd0a86491a52680d@mail.gmail.com> Message-ID: <200809171708.18852.jhb@freebsd.org> On Wednesday 17 September 2008 04:30:39 pm Baris Gerze wrote: > John, > Please look at, you can find previos fix for 7.0-stable brunch... > > > http://www.nabble.com/HP-Pavilion-dv2000-laptop-wont-boot-off-install-cd-td18479606.html If you read that whole thread, you can see that the laptop has a bug in the BIOS/hardware that causes it to read corrupted data off of the CD during boot. You have to break into the BIOS boot menu and wait for the CD to stop spinning and then boot off of the CD. -- John Baldwin From barisgerze at gmail.com Wed Sep 17 21:21:26 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Wed Sep 17 21:21:33 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <200809171622.14451.jhb@freebsd.org> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809171318.25679.jhb@freebsd.org> <28e7ba930809171253k7c36c994j4f71aa684e661a@mail.gmail.com> <200809171622.14451.jhb@freebsd.org> Message-ID: <28e7ba930809171421t7397b85at739a5221a206da90@mail.gmail.com> nope i do not have corrupted install CD. coz i have downloaded from 2-3 different sites + md5 checksum.. all the same :( I am quite sure about the previous 7.0 stable it was fixed.. did you look the link i have sent ? On Wed, Sep 17, 2008 at 11:22 PM, John Baldwin wrote: > On Wednesday 17 September 2008 03:53:01 pm Baris Gerze wrote: > > I am booting from FreeBSD 7.1 - Beta Install CD... > > how can I boot from GENERIC.. I do wanna fresh install from install boot > > cd... > > Erm, the install CD's are using GENERIC. I have no idea why it thinks your > kernel doesn't include 'device pci'. I think you must have a corrupted CD > or > some such. > > > On Wed, Sep 17, 2008 at 8:18 PM, John Baldwin wrote: > > > > > On Tuesday 16 September 2008 04:54:08 pm Baris Gerze wrote: > > > > Image files attached. > > > > > > > > I dont know the exact fix date for FREEBSD 7.0 - Stable brunch for > the > > > boot > > > > problem > > > > > > > > What can cause the problem ? > > > > with / without acpi result is the same.. > > > > > > Err, not having 'device pci' in your kernel is not likely to give a > working > > > kernel in general. Are you booting from a 7.1 kernel you built or from > a > > > 7.1 > > > install CD? Can you try booting from GENERIC? > > > > > > > On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin > wrote: > > > > > > > > > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: > > > > > > Two or three months ago I tried to boot from FBSD 7.0-STABLE > install > > > CD , > > > > > it > > > > > > boots > > > > > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of > some > > > > > > characters > > > > > > such as > > > > > > 00 12 12 00 > > > > > > 12 12 00 00 etc.. > > > > > > > > > > I would need the screen dump (a photo can work) to debug this at > all. > > > > > > > > > > > all tests were made with i386 version of fbsd. > > > > > > laptop is amd64 pavilion. > > > > > > > > > > > > when booting ubuntu linux it also says something like PCI BUG > found > > > in > > > > > the > > > > > > first screen but then boots normally > > > > > > > > > > > > you could trace the error by comparing 7.0 stable with 7.1 ( i386 > ) > > > FBSD > > > > > > install iso images.. > > > > > > > > > > I don't have the hardware, so I can't debug this using that method. > > > Can > > > > > you > > > > > narrow down approximately when 7.x broke? > > > > > > > > > > -- > > > > > John Baldwin > > > > > > > > > > > > > > > > > > > > > -- > > > John Baldwin > > > > > > > > > -- > John Baldwin > From barisgerze at gmail.com Wed Sep 17 21:31:34 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Wed Sep 17 21:31:42 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809171421t7397b85at739a5221a206da90@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <200809171318.25679.jhb@freebsd.org> <28e7ba930809171253k7c36c994j4f71aa684e661a@mail.gmail.com> <200809171622.14451.jhb@freebsd.org> <28e7ba930809171421t7397b85at739a5221a206da90@mail.gmail.com> Message-ID: <28e7ba930809171431rba5766bsa8cf9929349ce7cf@mail.gmail.com> Ok I understood and it worked now... when i boot i get boot prompt and go take coffee and waiting CD/DVD spin off.. and then type "boot" :) but it was fixed with 7.0 stable and moreover ubuntu linux says PCI bug and overcome the situation.. do you have plan to fix before 7.1 RELEASE? yes i know it is not a stopper bug but it was fixed before... On Thu, Sep 18, 2008 at 12:21 AM, Baris Gerze wrote: > nope i do not have corrupted install CD. coz i have downloaded from 2-3 > different sites > + md5 checksum.. all the same :( > > I am quite sure about the previous 7.0 stable it was fixed.. > did you look the link i have sent ? > > > > > > On Wed, Sep 17, 2008 at 11:22 PM, John Baldwin wrote: > >> On Wednesday 17 September 2008 03:53:01 pm Baris Gerze wrote: >> > I am booting from FreeBSD 7.1 - Beta Install CD... >> > how can I boot from GENERIC.. I do wanna fresh install from install boot >> > cd... >> >> Erm, the install CD's are using GENERIC. I have no idea why it thinks >> your >> kernel doesn't include 'device pci'. I think you must have a corrupted CD >> or >> some such. >> >> > On Wed, Sep 17, 2008 at 8:18 PM, John Baldwin wrote: >> > >> > > On Tuesday 16 September 2008 04:54:08 pm Baris Gerze wrote: >> > > > Image files attached. >> > > > >> > > > I dont know the exact fix date for FREEBSD 7.0 - Stable brunch for >> the >> > > boot >> > > > problem >> > > > >> > > > What can cause the problem ? >> > > > with / without acpi result is the same.. >> > > >> > > Err, not having 'device pci' in your kernel is not likely to give a >> working >> > > kernel in general. Are you booting from a 7.1 kernel you built or >> from a >> > > 7.1 >> > > install CD? Can you try booting from GENERIC? >> > > >> > > > On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin >> wrote: >> > > > >> > > > > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: >> > > > > > Two or three months ago I tried to boot from FBSD 7.0-STABLE >> install >> > > CD , >> > > > > it >> > > > > > boots >> > > > > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of >> some >> > > > > > characters >> > > > > > such as >> > > > > > 00 12 12 00 >> > > > > > 12 12 00 00 etc.. >> > > > > >> > > > > I would need the screen dump (a photo can work) to debug this at >> all. >> > > > > >> > > > > > all tests were made with i386 version of fbsd. >> > > > > > laptop is amd64 pavilion. >> > > > > > >> > > > > > when booting ubuntu linux it also says something like PCI BUG >> found >> > > in >> > > > > the >> > > > > > first screen but then boots normally >> > > > > > >> > > > > > you could trace the error by comparing 7.0 stable with 7.1 ( >> i386 ) >> > > FBSD >> > > > > > install iso images.. >> > > > > >> > > > > I don't have the hardware, so I can't debug this using that >> method. >> > > Can >> > > > > you >> > > > > narrow down approximately when 7.x broke? >> > > > > >> > > > > -- >> > > > > John Baldwin >> > > > > >> > > > >> > > >> > > >> > > >> > > -- >> > > John Baldwin >> > > >> > >> >> >> >> -- >> John Baldwin >> > > From Juergen.Dankoweit at T-Online.de Thu Sep 18 10:26:30 2008 From: Juergen.Dankoweit at T-Online.de (Juergen Dankoweit) Date: Thu Sep 18 10:26:36 2008 Subject: Thinkap T43 suspend/resume only once Message-ID: <1221732390.1279.1.camel@t43.juergendankoweit.net> Hello to the list. On my Thinkpad T43 every component works great with FreeBSD 7.0 and 7.1 PRERELEASE. But there is one point that does not work correctly. When I press the Fn+F4 buttons the first time after booting the system, ACPI mode S3 is called correctly and the notebook goes into suspend mode. After pressing Fn alone the notebook resumes perfekt. But when I press Fn+F4 the next time, nothing happens. Entering "acpiconf -s 3" suspends the notebook and resuming is no problem Where is the problem? If this is the wrong list, please tell me. Many thanks for your answers. Best regards J.D. Here the configuration files: /boot/loader.conf ---------------- # fuer T43 acpi_ibm_load="YES" # Sound-Modul laden snd_ich_load="YES" # Bluetooth ng_ubt_load="YES" # ATi-Radeon-Module fuer X300 radeon_load="YES" # fuer Mono kern.ipc.semmni=40 kern.ipc.semmns=300 # fuer gamin kern.maxfiles="25000" /etc/sysctl.conf ---------------- # ACPI fuer Thinkpad T43 # hw.acpi.reset_video=1 hw.acpi.lid_switch_state=S3 hw.acpi.sleep_button_state=S3 hw.acpi.power_button_state=S5 hw.acpi.sleep_delay=3 hw.acpi.verbose=1 dev.acpi_ibm.0.events=1 hw.syscons.sc_no_suspend_vtswitch=0 /etc/devd.conf (the relevant entry): ------------------------------------ # Suspend fuer IBM Thinkpad T43 notify 10 { match "system" "ACPI"; match "subsystem" "IBM"; match "notify" "0x04"; action "logger -t Fn+F4 && /etc/rc.suspend"; }; uname -a says: -------------- FreeBSD t43.juergendankoweit.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Sun Sep 14 09:24:44 CEST 2008 juergen@t43.juergendankoweit.net:/usr/obj/usr/src/sys/GENERIC i386 From markir at paradise.net.nz Thu Sep 18 11:54:48 2008 From: markir at paradise.net.nz (Mark Kirkwood) Date: Thu Sep 18 11:54:54 2008 Subject: Wpi keep disconnecting In-Reply-To: <489C7263.1040209@fastmail.fm> References: <489C625F.3020605@fastmail.fm> <489C70E8.2080800@freebsd.org> <489C7263.1040209@fastmail.fm> Message-ID: <48D23D9B.6010803@paradise.net.nz> Alberto Rizzi wrote: > Sam Leffler ha scritto: >> Check for a firmware update for your router. >> >> Sam >> > It already has the latest firmware (maybe 4 years old). > Unfortunately I don't have other routers to try with. I would seriously doubt this is a router problem - I see the same thing with an Asus laptop using wpi driver + WPA encryption. In my case disabling the encryption was a workaround (a very poor one I know). This appears to be a Freebsd issue AFAIK, as for instance under Ubuntu I can have WPA enabled with such disconnection occurring. regards Mark From markir at paradise.net.nz Thu Sep 18 11:56:55 2008 From: markir at paradise.net.nz (Mark Kirkwood) Date: Thu Sep 18 11:57:01 2008 Subject: Wpi keep disconnecting In-Reply-To: <48D23D9B.6010803@paradise.net.nz> References: <489C625F.3020605@fastmail.fm> <489C70E8.2080800@freebsd.org> <489C7263.1040209@fastmail.fm> <48D23D9B.6010803@paradise.net.nz> Message-ID: <48D23E19.5020205@paradise.net.nz> I wrote: > > This appears to be a Freebsd issue AFAIK, as for instance under Ubuntu > I can have WPA enabled *with such disconnection occurring*. > Should read: with *no* such disconnection occurring... stupid typo sorry. From davidb at boothscientific.com Thu Sep 18 12:49:10 2008 From: davidb at boothscientific.com (David Booth) Date: Thu Sep 18 12:49:17 2008 Subject: Wpi keep disconnecting In-Reply-To: <48D23D9B.6010803@paradise.net.nz> References: <489C625F.3020605@fastmail.fm> <489C7263.1040209@fastmail.fm> <48D23D9B.6010803@paradise.net.nz> Message-ID: <200809180713.42287.davidb@boothscientific.com> On Thursday 18 September 2008, Mark Kirkwood wrote: > Alberto Rizzi wrote: > > Sam Leffler ha scritto: > >> Check for a firmware update for your router. > >> > >> Sam > > > > It already has the latest firmware (maybe 4 years old). > > Unfortunately I don't have other routers to try with. > > I would seriously doubt this is a router problem - I see the same > thing with an Asus laptop using wpi driver + WPA encryption. In my > case disabling the encryption was a workaround (a very poor one I > know). This appears to be a Freebsd issue AFAIK, as for instance > under Ubuntu I can have WPA enabled with such disconnection > occurring. > > regards > > Mark I have a similar experience with wpi in a dell laptop running 7 stable i386. Without encryption, the connection will stay up without fail. If I enable WPA, it disconnects at seeming random intervals that are shortened by doing large file transfers. Sometimes it will go for a full day without disconnecting; however, if I do a file ftp of a few hundred megs, it may disconnect after a just a few minutes. I do not think that it is a hardware problem in either the card or the router as when I boot the laptop into windows and use the same router and same WPA settings, the connection remains rock solid even with successive large file transfers. From sarumont at sigil.org Thu Sep 18 14:13:04 2008 From: sarumont at sigil.org (Richard Kolkovich) Date: Thu Sep 18 14:13:10 2008 Subject: Thinkap T43 suspend/resume only once In-Reply-To: <1221732390.1279.1.camel@t43.juergendankoweit.net> References: <1221732390.1279.1.camel@t43.juergendankoweit.net> Message-ID: <20080918135804.GP17537@snobol> On Thu, Sep 18, 2008 at 12:06:30PM +0200, Juergen Dankoweit wrote: > Hello to the list. > > On my Thinkpad T43 every component works great with FreeBSD 7.0 and 7.1 > PRERELEASE. > But there is one point that does not work correctly. > When I press the Fn+F4 buttons the first time after booting the system, > ACPI mode S3 is called correctly and the notebook goes into suspend > mode. After pressing Fn alone the notebook resumes perfekt. > > But when I press Fn+F4 the next time, nothing happens. Entering > "acpiconf -s 3" suspends the notebook and resuming is no problem > > Where is the problem? If this is the wrong list, please tell me. > I had this exact same problem on my t43p. You'll need to remove 'device apic' from your kernel config. That was the resolution I discovered with the help of other Thinkpad users on this list. :) > Many thanks for your answers. > > Best regards > > J.D. > > Here the configuration files: > > /boot/loader.conf > ---------------- > # fuer T43 > acpi_ibm_load="YES" > > # Sound-Modul laden > snd_ich_load="YES" > > # Bluetooth > ng_ubt_load="YES" > > # ATi-Radeon-Module fuer X300 > radeon_load="YES" > > # fuer Mono > kern.ipc.semmni=40 > kern.ipc.semmns=300 > > # fuer gamin > kern.maxfiles="25000" > > /etc/sysctl.conf > ---------------- > # ACPI fuer Thinkpad T43 > # > hw.acpi.reset_video=1 > hw.acpi.lid_switch_state=S3 > hw.acpi.sleep_button_state=S3 > hw.acpi.power_button_state=S5 > hw.acpi.sleep_delay=3 > hw.acpi.verbose=1 > > dev.acpi_ibm.0.events=1 > > hw.syscons.sc_no_suspend_vtswitch=0 > > /etc/devd.conf (the relevant entry): > ------------------------------------ > # Suspend fuer IBM Thinkpad T43 > notify 10 { > match "system" "ACPI"; > match "subsystem" "IBM"; > match "notify" "0x04"; > action "logger -t Fn+F4 && /etc/rc.suspend"; > }; > > > uname -a says: > -------------- > FreeBSD t43.juergendankoweit.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE > #0: Sun Sep 14 09:24:44 CEST 2008 > juergen@t43.juergendankoweit.net:/usr/obj/usr/src/sys/GENERIC i386 > > _______________________________________________ > 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" -- Richard Kolkovich sarumont@sigil.org -------------- 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/20080918/4d147ca1/attachment.pgp From oberman at es.net Thu Sep 18 17:36:35 2008 From: oberman at es.net (Kevin Oberman) Date: Thu Sep 18 17:36:42 2008 Subject: Wpi keep disconnecting In-Reply-To: Your message of "Thu, 18 Sep 2008 07:13:42 CDT." <200809180713.42287.davidb@boothscientific.com> Message-ID: <20080918173634.CE1844500E@ptavv.es.net> > From: David Booth > Date: Thu, 18 Sep 2008 07:13:42 -0500 > Sender: owner-freebsd-mobile@freebsd.org > > On Thursday 18 September 2008, Mark Kirkwood wrote: > > Alberto Rizzi wrote: > > > Sam Leffler ha scritto: > > >> Check for a firmware update for your router. > > >> > > >> Sam > > > > > > It already has the latest firmware (maybe 4 years old). > > > Unfortunately I don't have other routers to try with. > > > > I would seriously doubt this is a router problem - I see the same > > thing with an Asus laptop using wpi driver + WPA encryption. In my > > case disabling the encryption was a workaround (a very poor one I > > know). This appears to be a Freebsd issue AFAIK, as for instance > > under Ubuntu I can have WPA enabled with such disconnection > > occurring. > > > > regards > > > > Mark > > I have a similar experience with wpi in a dell laptop running 7 stable > i386. Without encryption, the connection will stay up without fail. > If I enable WPA, it disconnects at seeming random intervals that are > shortened by doing large file transfers. Sometimes it will go for a > full day without disconnecting; however, if I do a file ftp of a few > hundred megs, it may disconnect after a just a few minutes. I do not > think that it is a hardware problem in either the card or the router > as when I boot the laptop into windows and use the same router and > same WPA settings, the connection remains rock solid even with > successive large file transfers. This is a bit of a shot in the dark, but I happen to be on a WPA connection today and I hit this one or something very similar. Since I am on an Atheros, it may be different, but I made the problem "go awa" with 'ifconfig ath0 -bgscan'. bgscan should not interfere in any way with normal operation, but I have seen issues from it for some time and al most always turn off bgscan as the first attempt to "fix" mystery disconnects. -- 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080918/906c4a92/attachment.pgp From Juergen.Dankoweit at t-online.de Thu Sep 18 17:44:45 2008 From: Juergen.Dankoweit at t-online.de (=?ISO-8859-1?Q?J=FCrgen?= Dankoweit) Date: Thu Sep 18 17:44:52 2008 Subject: Thinkap T43 suspend/resume only once In-Reply-To: <20080918135804.GP17537@snobol> References: <1221732390.1279.1.camel@t43.juergendankoweit.net> <20080918135804.GP17537@snobol> Message-ID: <1221759861.1423.3.camel@t43.juergendankoweit.net> Hello Richard, Am Donnerstag, den 18.09.2008, 08:58 -0500 schrieb Richard Kolkovich: > On Thu, Sep 18, 2008 at 12:06:30PM +0200, Juergen Dankoweit wrote: > > Hello to the list. > > > > On my Thinkpad T43 every component works great with FreeBSD 7.0 and 7.1 > > PRERELEASE. > > But there is one point that does not work correctly. > > When I press the Fn+F4 buttons the first time after booting the system, > > ACPI mode S3 is called correctly and the notebook goes into suspend > > mode. After pressing Fn alone the notebook resumes perfekt. > > > > But when I press Fn+F4 the next time, nothing happens. Entering > > "acpiconf -s 3" suspends the notebook and resuming is no problem > > > > Where is the problem? If this is the wrong list, please tell me. > > > > I had this exact same problem on my t43p. You'll need to remove 'device apic' from your kernel config. That was the resolution I discovered with the help of other Thinkpad users on this list. :) Thanks for your answer. If I disable APIC I have the chance to suspend the notebook a second and third time. BUT: at the third time it doesn't resume any more... Therefore I have to live with that problem and I will do a normal logout and shutdown. Best regards J.D. From jhugo at meraka.csir.co.za Thu Sep 18 18:18:59 2008 From: jhugo at meraka.csir.co.za (Johann Hugo) Date: Thu Sep 18 18:19:07 2008 Subject: Wpi keep disconnecting In-Reply-To: <20080918173634.CE1844500E@ptavv.es.net> References: <20080918173634.CE1844500E@ptavv.es.net> Message-ID: <200809182018.55084.jhugo@meraka.csir.co.za> On Thursday 18 September 2008, Kevin Oberman wrote: > > From: David Booth > > Date: Thu, 18 Sep 2008 07:13:42 -0500 > > Sender: owner-freebsd-mobile@freebsd.org > > > > On Thursday 18 September 2008, Mark Kirkwood wrote: > > > Alberto Rizzi wrote: > > > > Sam Leffler ha scritto: > > > >> Check for a firmware update for your router. > > > >> > > > >> Sam > > > > > > > > It already has the latest firmware (maybe 4 years old). > > > > Unfortunately I don't have other routers to try with. > > > > > > I would seriously doubt this is a router problem - I see the same > > > thing with an Asus laptop using wpi driver + WPA encryption. In my > > > case disabling the encryption was a workaround (a very poor one I > > > know). This appears to be a Freebsd issue AFAIK, as for instance > > > under Ubuntu I can have WPA enabled with such disconnection > > > occurring. > > > > > > regards > > > > > > Mark > > > > I have a similar experience with wpi in a dell laptop running 7 stable > > i386. Without encryption, the connection will stay up without fail. > > If I enable WPA, it disconnects at seeming random intervals that are > > shortened by doing large file transfers. Sometimes it will go for a > > full day without disconnecting; however, if I do a file ftp of a few > > hundred megs, it may disconnect after a just a few minutes. I do not > > think that it is a hardware problem in either the card or the router > > as when I boot the laptop into windows and use the same router and > > same WPA settings, the connection remains rock solid even with > > successive large file transfers. > > This is a bit of a shot in the dark, but I happen to be on a WPA > connection today and I hit this one or something very similar. Since I > am on an Atheros, it may be different, but I made the problem "go awa" > with 'ifconfig ath0 -bgscan'. bgscan should not interfere in any way > with normal operation, but I have seen issues from it for some time > and al most always turn off bgscan as the first attempt to "fix" mystery > disconnects. I've got a Dell 1720 with a wpi wireless adapter in it. It was also droping the connection very often, until I added -bgscan to my ifconfig line. Now it stays connected all the time. except if my AP reboots then it does not want to reconnect automatically. From jhb at freebsd.org Thu Sep 18 18:35:00 2008 From: jhb at freebsd.org (John Baldwin) Date: Thu Sep 18 18:35:15 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <28e7ba930809171431rba5766bsa8cf9929349ce7cf@mail.gmail.com> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <28e7ba930809171421t7397b85at739a5221a206da90@mail.gmail.com> <28e7ba930809171431rba5766bsa8cf9929349ce7cf@mail.gmail.com> Message-ID: <200809181036.38782.jhb@freebsd.org> On Wednesday 17 September 2008 05:31:26 pm Baris Gerze wrote: > Ok I understood and it worked now... when i boot i get boot prompt and go > take coffee > and waiting CD/DVD spin off.. and then type "boot" :) > > but it was fixed with 7.0 stable and moreover ubuntu linux says PCI bug and > overcome the > situation.. do you have plan to fix before 7.1 RELEASE? > > yes i know it is not a stopper bug but it was fixed before... This is _not_ a FreeBSD bug. I think you just got lucky with 7.0, maybe the BIOS bug only corrupts data read from certain sectors on the CD and the kernel for 7.0 was in a different location on the CD. This is a bug in your machine's _BIOS_. FreeBSD can _not_ fix your broken BIOS. Please understand, the reason you are having problems is that when the FreeBSD boot code asks the BIOS in your machine to read files off the CD, the BIOS is corrupting the files that are being read in some cases. If it corrupts the kernel, then of course you are going to run into issues. However, there is nothing FreeBSD can really do about this. We depend on a minimum subset of the BIOS functioning correctly, including reading files off of disk drives. > On Thu, Sep 18, 2008 at 12:21 AM, Baris Gerze wrote: > > > nope i do not have corrupted install CD. coz i have downloaded from 2-3 > > different sites > > + md5 checksum.. all the same :( > > > > I am quite sure about the previous 7.0 stable it was fixed.. > > did you look the link i have sent ? > > > > > > > > > > > > On Wed, Sep 17, 2008 at 11:22 PM, John Baldwin wrote: > > > >> On Wednesday 17 September 2008 03:53:01 pm Baris Gerze wrote: > >> > I am booting from FreeBSD 7.1 - Beta Install CD... > >> > how can I boot from GENERIC.. I do wanna fresh install from install boot > >> > cd... > >> > >> Erm, the install CD's are using GENERIC. I have no idea why it thinks > >> your > >> kernel doesn't include 'device pci'. I think you must have a corrupted CD > >> or > >> some such. > >> > >> > On Wed, Sep 17, 2008 at 8:18 PM, John Baldwin wrote: > >> > > >> > > On Tuesday 16 September 2008 04:54:08 pm Baris Gerze wrote: > >> > > > Image files attached. > >> > > > > >> > > > I dont know the exact fix date for FREEBSD 7.0 - Stable brunch for > >> the > >> > > boot > >> > > > problem > >> > > > > >> > > > What can cause the problem ? > >> > > > with / without acpi result is the same.. > >> > > > >> > > Err, not having 'device pci' in your kernel is not likely to give a > >> working > >> > > kernel in general. Are you booting from a 7.1 kernel you built or > >> from a > >> > > 7.1 > >> > > install CD? Can you try booting from GENERIC? > >> > > > >> > > > On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin > >> wrote: > >> > > > > >> > > > > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: > >> > > > > > Two or three months ago I tried to boot from FBSD 7.0-STABLE > >> install > >> > > CD , > >> > > > > it > >> > > > > > boots > >> > > > > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump of > >> some > >> > > > > > characters > >> > > > > > such as > >> > > > > > 00 12 12 00 > >> > > > > > 12 12 00 00 etc.. > >> > > > > > >> > > > > I would need the screen dump (a photo can work) to debug this at > >> all. > >> > > > > > >> > > > > > all tests were made with i386 version of fbsd. > >> > > > > > laptop is amd64 pavilion. > >> > > > > > > >> > > > > > when booting ubuntu linux it also says something like PCI BUG > >> found > >> > > in > >> > > > > the > >> > > > > > first screen but then boots normally > >> > > > > > > >> > > > > > you could trace the error by comparing 7.0 stable with 7.1 ( > >> i386 ) > >> > > FBSD > >> > > > > > install iso images.. > >> > > > > > >> > > > > I don't have the hardware, so I can't debug this using that > >> method. > >> > > Can > >> > > > > you > >> > > > > narrow down approximately when 7.x broke? > >> > > > > > >> > > > > -- > >> > > > > John Baldwin > >> > > > > > >> > > > > >> > > > >> > > > >> > > > >> > > -- > >> > > John Baldwin > >> > > > >> > > >> > >> > >> > >> -- > >> John Baldwin > >> > > > > > -- John Baldwin From iwasaki at jp.FreeBSD.org Thu Sep 18 19:02:03 2008 From: iwasaki at jp.FreeBSD.org (Mitsuru IWASAKI) Date: Thu Sep 18 19:02:11 2008 Subject: Thinkap T43 suspend/resume only once In-Reply-To: <1221732390.1279.1.camel@t43.juergendankoweit.net> References: <1221732390.1279.1.camel@t43.juergendankoweit.net> Message-ID: <20080919.032334.54135277.iwasaki@jp.FreeBSD.org> Hi, Please try this patch. http://people.freebsd.org/~iwasaki/acpi/subr_bus.c-fix-20080919.diff Thanks > On my Thinkpad T43 every component works great with FreeBSD 7.0 and 7.1 > PRERELEASE. > But there is one point that does not work correctly. > When I press the Fn+F4 buttons the first time after booting the system, > ACPI mode S3 is called correctly and the notebook goes into suspend > mode. After pressing Fn alone the notebook resumes perfekt. > > But when I press Fn+F4 the next time, nothing happens. Entering > "acpiconf -s 3" suspends the notebook and resuming is no problem > > Where is the problem? If this is the wrong list, please tell me. > > Many thanks for your answers. > > Best regards > > J.D. > > Here the configuration files: > > /boot/loader.conf > ---------------- > # fuer T43 > acpi_ibm_load="YES" > > # Sound-Modul laden > snd_ich_load="YES" > > # Bluetooth > ng_ubt_load="YES" > > # ATi-Radeon-Module fuer X300 > radeon_load="YES" > > # fuer Mono > kern.ipc.semmni=40 > kern.ipc.semmns=300 > > # fuer gamin > kern.maxfiles="25000" > > /etc/sysctl.conf > ---------------- > # ACPI fuer Thinkpad T43 > # > hw.acpi.reset_video=1 > hw.acpi.lid_switch_state=S3 > hw.acpi.sleep_button_state=S3 > hw.acpi.power_button_state=S5 > hw.acpi.sleep_delay=3 > hw.acpi.verbose=1 > > dev.acpi_ibm.0.events=1 > > hw.syscons.sc_no_suspend_vtswitch=0 > > /etc/devd.conf (the relevant entry): > ------------------------------------ > # Suspend fuer IBM Thinkpad T43 > notify 10 { > match "system" "ACPI"; > match "subsystem" "IBM"; > match "notify" "0x04"; > action "logger -t Fn+F4 && /etc/rc.suspend"; > }; > > > uname -a says: > -------------- > FreeBSD t43.juergendankoweit.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE > #0: Sun Sep 14 09:24:44 CEST 2008 > juergen@t43.juergendankoweit.net:/usr/obj/usr/src/sys/GENERIC i386 > > _______________________________________________ > 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 Juergen.Dankoweit at T-Online.de Thu Sep 18 19:12:49 2008 From: Juergen.Dankoweit at T-Online.de (Juergen Dankoweit) Date: Thu Sep 18 19:12:56 2008 Subject: Thinkap T43 suspend/resume only once In-Reply-To: <20080919.032334.54135277.iwasaki@jp.FreeBSD.org> References: <1221732390.1279.1.camel@t43.juergendankoweit.net> <20080919.032334.54135277.iwasaki@jp.FreeBSD.org> Message-ID: <1221765147.1437.8.camel@t43.juergendankoweit.net> Hi, Am Freitag, den 19.09.2008, 03:23 +0900 schrieb Mitsuru IWASAKI: > Hi, > > Please try this patch. > > http://people.freebsd.org/~iwasaki/acpi/subr_bus.c-fix-20080919.diff > > Thanks Thanks for the patch, but the file subr_bus.c is already patched. Best regards Juergen > > > On my Thinkpad T43 every component works great with FreeBSD 7.0 and 7.1 > > PRERELEASE. > > But there is one point that does not work correctly. > > When I press the Fn+F4 buttons the first time after booting the system, > > ACPI mode S3 is called correctly and the notebook goes into suspend > > mode. After pressing Fn alone the notebook resumes perfekt. > > > > But when I press Fn+F4 the next time, nothing happens. Entering > > "acpiconf -s 3" suspends the notebook and resuming is no problem > > > > Where is the problem? If this is the wrong list, please tell me. > > > > Many thanks for your answers. > > > > Best regards > > > > J.D. > > > > Here the configuration files: > > > > /boot/loader.conf > > ---------------- > > # fuer T43 > > acpi_ibm_load="YES" > > > > # Sound-Modul laden > > snd_ich_load="YES" > > > > # Bluetooth > > ng_ubt_load="YES" > > > > # ATi-Radeon-Module fuer X300 > > radeon_load="YES" > > > > # fuer Mono > > kern.ipc.semmni=40 > > kern.ipc.semmns=300 > > > > # fuer gamin > > kern.maxfiles="25000" > > > > /etc/sysctl.conf > > ---------------- > > # ACPI fuer Thinkpad T43 > > # > > hw.acpi.reset_video=1 > > hw.acpi.lid_switch_state=S3 > > hw.acpi.sleep_button_state=S3 > > hw.acpi.power_button_state=S5 > > hw.acpi.sleep_delay=3 > > hw.acpi.verbose=1 > > > > dev.acpi_ibm.0.events=1 > > > > hw.syscons.sc_no_suspend_vtswitch=0 > > > > /etc/devd.conf (the relevant entry): > > ------------------------------------ > > # Suspend fuer IBM Thinkpad T43 > > notify 10 { > > match "system" "ACPI"; > > match "subsystem" "IBM"; > > match "notify" "0x04"; > > action "logger -t Fn+F4 && /etc/rc.suspend"; > > }; > > > > > > uname -a says: > > -------------- > > FreeBSD t43.juergendankoweit.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE > > #0: Sun Sep 14 09:24:44 CEST 2008 > > juergen@t43.juergendankoweit.net:/usr/obj/usr/src/sys/GENERIC i386 > > > > _______________________________________________ > > freebsd-mobile@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" From barisgerze at gmail.com Thu Sep 18 20:30:51 2008 From: barisgerze at gmail.com (Baris Gerze) Date: Thu Sep 18 20:30:58 2008 Subject: Pavilion BTX boot Problem In-Reply-To: <200809181036.38782.jhb@freebsd.org> References: <28e7ba930809121638r3c0df525i113f4e353b9baebf@mail.gmail.com> <28e7ba930809171421t7397b85at739a5221a206da90@mail.gmail.com> <28e7ba930809171431rba5766bsa8cf9929349ce7cf@mail.gmail.com> <200809181036.38782.jhb@freebsd.org> Message-ID: <28e7ba930809181330p7ae1279bw79c9913f6f05a156@mail.gmail.com> I understand about the situation clearly, but you must also consider freebsd must spread. i installed freebsd on pavilion right now. no problem for me but others may also want to try bsd on their laptops.. so linux installing, windows installing, even open solaris installing on the hardware.. I have been using freebsd about 14 years and i think it must spread because it deserves it... anyway thx for help On Thu, Sep 18, 2008 at 5:36 PM, John Baldwin wrote: > On Wednesday 17 September 2008 05:31:26 pm Baris Gerze wrote: > > Ok I understood and it worked now... when i boot i get boot prompt and go > > take coffee > > and waiting CD/DVD spin off.. and then type "boot" :) > > > > but it was fixed with 7.0 stable and moreover ubuntu linux says PCI bug > and > > overcome the > > situation.. do you have plan to fix before 7.1 RELEASE? > > > > yes i know it is not a stopper bug but it was fixed before... > > This is _not_ a FreeBSD bug. I think you just got lucky with 7.0, maybe > the > BIOS bug only corrupts data read from certain sectors on the CD and the > kernel for 7.0 was in a different location on the CD. This is a bug in > your > machine's _BIOS_. FreeBSD can _not_ fix your broken BIOS. Please > understand, the reason you are having problems is that when the FreeBSD > boot > code asks the BIOS in your machine to read files off the CD, the BIOS is > corrupting the files that are being read in some cases. If it corrupts the > kernel, then of course you are going to run into issues. However, there is > nothing FreeBSD can really do about this. We depend on a minimum subset of > the BIOS functioning correctly, including reading files off of disk drives. > > > On Thu, Sep 18, 2008 at 12:21 AM, Baris Gerze > wrote: > > > > > nope i do not have corrupted install CD. coz i have downloaded from 2-3 > > > different sites > > > + md5 checksum.. all the same :( > > > > > > I am quite sure about the previous 7.0 stable it was fixed.. > > > did you look the link i have sent ? > > > > > > > > > > > > > > > > > > On Wed, Sep 17, 2008 at 11:22 PM, John Baldwin > wrote: > > > > > >> On Wednesday 17 September 2008 03:53:01 pm Baris Gerze wrote: > > >> > I am booting from FreeBSD 7.1 - Beta Install CD... > > >> > how can I boot from GENERIC.. I do wanna fresh install from install > boot > > >> > cd... > > >> > > >> Erm, the install CD's are using GENERIC. I have no idea why it thinks > > >> your > > >> kernel doesn't include 'device pci'. I think you must have a > corrupted > CD > > >> or > > >> some such. > > >> > > >> > On Wed, Sep 17, 2008 at 8:18 PM, John Baldwin > wrote: > > >> > > > >> > > On Tuesday 16 September 2008 04:54:08 pm Baris Gerze wrote: > > >> > > > Image files attached. > > >> > > > > > >> > > > I dont know the exact fix date for FREEBSD 7.0 - Stable brunch > for > > >> the > > >> > > boot > > >> > > > problem > > >> > > > > > >> > > > What can cause the problem ? > > >> > > > with / without acpi result is the same.. > > >> > > > > >> > > Err, not having 'device pci' in your kernel is not likely to give > a > > >> working > > >> > > kernel in general. Are you booting from a 7.1 kernel you built or > > >> from a > > >> > > 7.1 > > >> > > install CD? Can you try booting from GENERIC? > > >> > > > > >> > > > On Tue, Sep 16, 2008 at 6:24 PM, John Baldwin > > >> wrote: > > >> > > > > > >> > > > > On Monday 15 September 2008 08:45:55 pm Baris Gerze wrote: > > >> > > > > > Two or three months ago I tried to boot from FBSD 7.0-STABLE > > >> install > > >> > > CD , > > >> > > > > it > > >> > > > > > boots > > >> > > > > > but both 7.0-RELEASE and 7.1-BETA BTX loader gives me dump > of > > >> some > > >> > > > > > characters > > >> > > > > > such as > > >> > > > > > 00 12 12 00 > > >> > > > > > 12 12 00 00 etc.. > > >> > > > > > > >> > > > > I would need the screen dump (a photo can work) to debug this > at > > >> all. > > >> > > > > > > >> > > > > > all tests were made with i386 version of fbsd. > > >> > > > > > laptop is amd64 pavilion. > > >> > > > > > > > >> > > > > > when booting ubuntu linux it also says something like PCI > BUG > > >> found > > >> > > in > > >> > > > > the > > >> > > > > > first screen but then boots normally > > >> > > > > > > > >> > > > > > you could trace the error by comparing 7.0 stable with 7.1 ( > > >> i386 ) > > >> > > FBSD > > >> > > > > > install iso images.. > > >> > > > > > > >> > > > > I don't have the hardware, so I can't debug this using that > > >> method. > > >> > > Can > > >> > > > > you > > >> > > > > narrow down approximately when 7.x broke? > > >> > > > > > > >> > > > > -- > > >> > > > > John Baldwin > > >> > > > > > > >> > > > > > >> > > > > >> > > > > >> > > > > >> > > -- > > >> > > John Baldwin > > >> > > > > >> > > > >> > > >> > > >> > > >> -- > > >> John Baldwin > > >> > > > > > > > > > > > > -- > John Baldwin > From davidb at boothscientific.com Thu Sep 18 21:29:26 2008 From: davidb at boothscientific.com (David Booth) Date: Thu Sep 18 21:29:33 2008 Subject: Wpi keep disconnecting In-Reply-To: <200809182018.55084.jhugo@meraka.csir.co.za> References: <20080918173634.CE1844500E@ptavv.es.net> <200809182018.55084.jhugo@meraka.csir.co.za> Message-ID: <200809181629.24662.davidb@boothscientific.com> On Thursday 18 September 2008, Johann Hugo wrote: > On Thursday 18 September 2008, Kevin Oberman wrote: > > > From: David Booth > > > Date: Thu, 18 Sep 2008 07:13:42 -0500 > > > Sender: owner-freebsd-mobile@freebsd.org > > > > > > On Thursday 18 September 2008, Mark Kirkwood wrote: > > > > Alberto Rizzi wrote: > > > > > Sam Leffler ha scritto: > > > > >> Check for a firmware update for your router. > > > > >> > > > > >> Sam > > > > > > > > > > It already has the latest firmware (maybe 4 years old). > > > > > Unfortunately I don't have other routers to try with. > > > > > > > > I would seriously doubt this is a router problem - I see the > > > > same thing with an Asus laptop using wpi driver + WPA > > > > encryption. In my case disabling the encryption was a > > > > workaround (a very poor one I know). This appears to be a > > > > Freebsd issue AFAIK, as for instance under Ubuntu I can have > > > > WPA enabled with such disconnection occurring. > > > > > > > > regards > > > > > > > > Mark > > > > > > I have a similar experience with wpi in a dell laptop running 7 > > > stable i386. Without encryption, the connection will stay up > > > without fail. If I enable WPA, it disconnects at seeming random > > > intervals that are shortened by doing large file transfers. > > > Sometimes it will go for a full day without disconnecting; > > > however, if I do a file ftp of a few hundred megs, it may > > > disconnect after a just a few minutes. I do not think that it > > > is a hardware problem in either the card or the router as when > > > I boot the laptop into windows and use the same router and same > > > WPA settings, the connection remains rock solid even with > > > successive large file transfers. > > > > This is a bit of a shot in the dark, but I happen to be on a WPA > > connection today and I hit this one or something very similar. > > Since I am on an Atheros, it may be different, but I made the > > problem "go awa" with 'ifconfig ath0 -bgscan'. bgscan should not > > interfere in any way with normal operation, but I have seen > > issues from it for some time and al most always turn off bgscan > > as the first attempt to "fix" mystery disconnects. > > I've got a Dell 1720 with a wpi wireless adapter in it. It was also > droping the connection very often, until I added -bgscan to my > ifconfig line. Now it stays connected all the time. except if my AP > reboots then it does not want to reconnect automatically. I will give it a try, but my memory is that bgscan is not supported in the wpi driver yet anyway, but I may be wrong. As far as reconnecting automatically, it never did that anyway, so I have nothing to loose. From davidb at boothscientific.com Thu Sep 18 22:27:47 2008 From: davidb at boothscientific.com (David Booth) Date: Thu Sep 18 22:27:54 2008 Subject: Wpi keep disconnecting In-Reply-To: <200809182018.55084.jhugo@meraka.csir.co.za> References: <20080918173634.CE1844500E@ptavv.es.net> <200809182018.55084.jhugo@meraka.csir.co.za> Message-ID: <200809181727.40517.davidb@boothscientific.com> On Thursday 18 September 2008, Johann Hugo wrote: > On Thursday 18 September 2008, Kevin Oberman wrote: > > > From: David Booth > > > Date: Thu, 18 Sep 2008 07:13:42 -0500 > > > Sender: owner-freebsd-mobile@freebsd.org > > > > > > On Thursday 18 September 2008, Mark Kirkwood wrote: > > > > Alberto Rizzi wrote: > > > > > Sam Leffler ha scritto: > > > > >> Check for a firmware update for your router. > > > > >> > > > > >> Sam > > > > > > > > > > It already has the latest firmware (maybe 4 years old). > > > > > Unfortunately I don't have other routers to try with. > > > > > > > > I would seriously doubt this is a router problem - I see the > > > > same thing with an Asus laptop using wpi driver + WPA > > > > encryption. In my case disabling the encryption was a > > > > workaround (a very poor one I know). This appears to be a > > > > Freebsd issue AFAIK, as for instance under Ubuntu I can have > > > > WPA enabled with such disconnection occurring. > > > > > > > > regards > > > > > > > > Mark > > > > > > I have a similar experience with wpi in a dell laptop running 7 > > > stable i386. Without encryption, the connection will stay up > > > without fail. If I enable WPA, it disconnects at seeming random > > > intervals that are shortened by doing large file transfers. > > > Sometimes it will go for a full day without disconnecting; > > > however, if I do a file ftp of a few hundred megs, it may > > > disconnect after a just a few minutes. I do not think that it > > > is a hardware problem in either the card or the router as when > > > I boot the laptop into windows and use the same router and same > > > WPA settings, the connection remains rock solid even with > > > successive large file transfers. > > > > This is a bit of a shot in the dark, but I happen to be on a WPA > > connection today and I hit this one or something very similar. > > Since I am on an Atheros, it may be different, but I made the > > problem "go awa" with 'ifconfig ath0 -bgscan'. bgscan should not > > interfere in any way with normal operation, but I have seen > > issues from it for some time and al most always turn off bgscan > > as the first attempt to "fix" mystery disconnects. > > I've got a Dell 1720 with a wpi wireless adapter in it. It was also > droping the connection very often, until I added -bgscan to my > ifconfig line. Now it stays connected all the time. except if my AP > reboots then it does not want to reconnect automatically. I gave it a try and that did not do the trick. It died less than two minutes into an ftp session with less than 300 MB transferred. After restarting, it died in less than a minute. The only logged error messages for the interface are the usual messages about Timeout resetting TX ring 3 or 4. > _______________________________________________ > 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 gautham at lisphacker.org Fri Sep 19 01:02:01 2008 From: gautham at lisphacker.org (Gautham Ganapathy) Date: Fri Sep 19 01:02:08 2008 Subject: Wpi keep disconnecting In-Reply-To: <200809181727.40517.davidb@boothscientific.com> References: <20080918173634.CE1844500E@ptavv.es.net> <200809182018.55084.jhugo@meraka.csir.co.za> <200809181727.40517.davidb@boothscientific.com> Message-ID: On Fri, Sep 19, 2008 at 3:57 AM, David Booth wrote: > On Thursday 18 September 2008, Johann Hugo wrote: > > On Thursday 18 September 2008, Kevin Oberman wrote: > > > > From: David Booth > > > > Date: Thu, 18 Sep 2008 07:13:42 -0500 > > > > Sender: owner-freebsd-mobile@freebsd.org > > > > > > > > On Thursday 18 September 2008, Mark Kirkwood wrote: > > > > > > > > > > I would seriously doubt this is a router problem - I see the > > > > > same thing with an Asus laptop using wpi driver + WPA > > > > > encryption. In my case disabling the encryption was a > > > > > workaround (a very poor one I know). This appears to be a > > > > > Freebsd issue AFAIK, as for instance under Ubuntu I can have > > > > > WPA enabled with such disconnection occurring. > > > > > > > > > > regards > > > > > > > > > > Mark > > > > > > > > I have a similar experience with wpi in a dell laptop running 7 > > > > stable i386. Without encryption, the connection will stay up > > > > without fail. If I enable WPA, it disconnects at seeming random > > > > intervals that are shortened by doing large file transfers. > > > > Sometimes it will go for a full day without disconnecting; > > > > however, if I do a file ftp of a few hundred megs, it may > > > > disconnect after a just a few minutes. I do not think that it > > > > is a hardware problem in either the card or the router as when > > > > I boot the laptop into windows and use the same router and same > > > > WPA settings, the connection remains rock solid even with > > > > successive large file transfers. > > > > > > This is a bit of a shot in the dark, but I happen to be on a WPA > > > connection today and I hit this one or something very similar. > > > Since I am on an Atheros, it may be different, but I made the > > > problem "go awa" with 'ifconfig ath0 -bgscan'. bgscan should not > > > interfere in any way with normal operation, but I have seen > > > issues from it for some time and al most always turn off bgscan > > > as the first attempt to "fix" mystery disconnects. > > > > I've got a Dell 1720 with a wpi wireless adapter in it. It was also > > droping the connection very often, until I added -bgscan to my > > ifconfig line. Now it stays connected all the time. except if my AP > > reboots then it does not want to reconnect automatically. > > I gave it a try and that did not do the trick. It died less than two > minutes into an ftp session with less than 300 MB transferred. After > restarting, it died in less than a minute. The only logged error > messages for the interface are the usual messages about Timeout > resetting TX ring 3 or 4. > > _______________________________________________ > have you tried updating to 7-stable? I have a dell laptop (inspiron 9400) with a wpi based adapter connected to a router (Linksys WRT54G f/w rev 7) over WPA. I normally have no problems with disconnections (w/ 7-stable, not 7.0-release), even with multiple long downloads using parallel connections (upto 10 per file). It works fine without any disconnections or problems until I run the Deluge bittorrent client. Once this start running, after a few minutes, all connections except Deluge stop (Deluge still runs fine). I cannot even ping the router. If I stop Deluge, other connections start working after a few minutes. Not sure if this is related, but I do have a problem when freebsd starts up. For some reason, the ip address and the route do not get setup when it boots up, although I can see the config scripts running. After I login, I neet to run /etc/netstart again before the ip address gets assigned. it gives a message 'invalid authmode' in both cases -- Gautham Ganapathy http://lisphacker.org From davidb at boothscientific.com Fri Sep 19 01:12:52 2008 From: davidb at boothscientific.com (David Booth) Date: Fri Sep 19 01:12:59 2008 Subject: Wpi keep disconnecting Message-ID: <200809182012.50149.davidb@boothscientific.com> On Thursday 18 September 2008, you wrote: > On Fri, Sep 19, 2008 at 3:57 AM, David Booth wrote: > > On Thursday 18 September 2008, Johann Hugo wrote: > > > On Thursday 18 September 2008, Kevin Oberman wrote: > > > > > From: David Booth > > > > > Date: Thu, 18 Sep 2008 07:13:42 -0500 > > > > > Sender: owner-freebsd-mobile@freebsd.org > > > > > > > > > > On Thursday 18 September 2008, Mark Kirkwood wrote: > > > > > > I would seriously doubt this is a router problem - I see > > > > > > the same thing with an Asus laptop using wpi driver + WPA > > > > > > encryption. In my case disabling the encryption was a > > > > > > workaround (a very poor one I know). This appears to be a > > > > > > Freebsd issue AFAIK, as for instance under Ubuntu I can > > > > > > have WPA enabled with such disconnection occurring. > > > > > > > > > > > > regards > > > > > > > > > > > > Mark > > > > > > > > > > I have a similar experience with wpi in a dell laptop > > > > > running 7 stable i386. Without encryption, the connection > > > > > will stay up without fail. If I enable WPA, it disconnects > > > > > at seeming random intervals that are shortened by doing > > > > > large file transfers. Sometimes it will go for a full day > > > > > without disconnecting; however, if I do a file ftp of a > > > > > few hundred megs, it may disconnect after a just a few > > > > > minutes. I do not think that it is a hardware problem in > > > > > either the card or the router as when I boot the laptop > > > > > into windows and use the same router and same WPA settings, > > > > > the connection remains rock solid even with successive > > > > > large file transfers. > > > > > > > > This is a bit of a shot in the dark, but I happen to be on a > > > > WPA connection today and I hit this one or something very > > > > similar. Since I am on an Atheros, it may be different, but I > > > > made the problem "go awa" with 'ifconfig ath0 -bgscan'. > > > > bgscan should not interfere in any way with normal operation, > > > > but I have seen issues from it for some time and al most > > > > always turn off bgscan as the first attempt to "fix" mystery > > > > disconnects. > > > > > > I've got a Dell 1720 with a wpi wireless adapter in it. It was > > > also droping the connection very often, until I added -bgscan > > > to my ifconfig line. Now it stays connected all the time. > > > except if my AP reboots then it does not want to reconnect > > > automatically. > > > > I gave it a try and that did not do the trick. It died less than > > two minutes into an ftp session with less than 300 MB > > transferred. After restarting, it died in less than a minute. > > The only logged error messages for the interface are the usual > > messages about Timeout resetting TX ring 3 or 4. > > > > > _______________________________________________ > > have you tried updating to 7-stable? > > I have a dell laptop (inspiron 9400) with a wpi based adapter > connected to a router (Linksys WRT54G f/w rev 7) over WPA. I > normally have no problems with disconnections (w/ 7-stable, not > 7.0-release), even with multiple long downloads using parallel > connections (upto 10 per file). It works fine without any > disconnections or problems until I run the Deluge bittorrent > client. Once this start running, after a few minutes, all > connections except Deluge stop (Deluge still runs fine). I cannot > even ping the router. If I stop Deluge, other connections start > working after a few minutes. > > Not sure if this is related, but I do have a problem when freebsd > starts up. For some reason, the ip address and the route do not get > setup when it boots up, although I can see the config scripts > running. After I login, I neet to run /etc/netstart again before > the ip address gets assigned. it gives a message 'invalid authmode' > in both cases I have the same hardware you do (inspiron 9400, intel 3945) running 7-stable (really 7.1 pre-release at this point) . I have no problem at startup connecting to a linksys wrv200 using wpa-psk using wpa_supplicant, but I get the seemingly random disconnects. When I get the disconnect, ifconfig looks good except that the status shows not associated. Executing /etc/rc.d/netif restart will usually get a reconnect on the first try. It seems to be a wpa issue as using WEP on the same hardware results in a stable connection. On another note, can you get your notebook to suspend (S3)? From vbotka at suse.cz Fri Sep 19 07:54:33 2008 From: vbotka at suse.cz (Vladimir Botka) Date: Fri Sep 19 07:54:40 2008 Subject: Thinkap T43 suspend/resume only once In-Reply-To: <1221765147.1437.8.camel@t43.juergendankoweit.net> References: <1221732390.1279.1.camel@t43.juergendankoweit.net> <20080919.032334.54135277.iwasaki@jp.FreeBSD.org> <1221765147.1437.8.camel@t43.juergendankoweit.net> Message-ID: <20080919093447.136f79dc@vlado.netng.org> On Thu, 18 Sep 2008 21:12:27 +0200 Juergen Dankoweit wrote: > Hi, > > Am Freitag, den 19.09.2008, 03:23 +0900 schrieb Mitsuru IWASAKI: > > Hi, > > > > Please try this patch. > > > > http://people.freebsd.org/~iwasaki/acpi/subr_bus.c-fix-20080919.diff > > > > Thanks > > > Thanks for the patch, but the file subr_bus.c is already patched. > > Best regards > > Juergen > > > > > > > On my Thinkpad T43 every component works great with FreeBSD 7.0 > > > and 7.1 PRERELEASE. > > > But there is one point that does not work correctly. > > > When I press the Fn+F4 buttons the first time after booting the > > > system, ACPI mode S3 is called correctly and the notebook goes > > > into suspend mode. After pressing Fn alone the notebook resumes > > > perfekt. > > > > > > But when I press Fn+F4 the next time, nothing happens. Entering > > > "acpiconf -s 3" suspends the notebook and resuming is no problem > > > > > > Where is the problem? If this is the wrong list, please tell me. > > > > > > Many thanks for your answers. > > > > > > Best regards > > > > > > J.D. > > > > > > Here the configuration files: > > > > > > /boot/loader.conf > > > ---------------- > > > # fuer T43 > > > acpi_ibm_load="YES" > > > > > > # Sound-Modul laden > > > snd_ich_load="YES" > > > > > > # Bluetooth > > > ng_ubt_load="YES" > > > > > > # ATi-Radeon-Module fuer X300 > > > radeon_load="YES" > > > > > > # fuer Mono > > > kern.ipc.semmni=40 > > > kern.ipc.semmns=300 > > > > > > # fuer gamin > > > kern.maxfiles="25000" > > > > > > /etc/sysctl.conf > > > ---------------- > > > # ACPI fuer Thinkpad T43 > > > # > > > hw.acpi.reset_video=1 > > > hw.acpi.lid_switch_state=S3 > > > hw.acpi.sleep_button_state=S3 > > > hw.acpi.power_button_state=S5 > > > hw.acpi.sleep_delay=3 > > > hw.acpi.verbose=1 > > > > > > dev.acpi_ibm.0.events=1 > > > > > > hw.syscons.sc_no_suspend_vtswitch=0 > > > > > > /etc/devd.conf (the relevant entry): > > > ------------------------------------ > > > # Suspend fuer IBM Thinkpad T43 > > > notify 10 { > > > match "system" "ACPI"; > > > match "subsystem" "IBM"; > > > match "notify" "0x04"; > > > action "logger -t Fn+F4 && /etc/rc.suspend"; > > > }; > > > > > > > > > uname -a says: > > > -------------- > > > FreeBSD t43.juergendankoweit.net 7.1-PRERELEASE FreeBSD > > > 7.1-PRERELEASE #0: Sun Sep 14 09:24:44 CEST 2008 > > > juergen@t43.juergendankoweit.net:/usr/obj/usr/src/sys/GENERIC i386 > > > > > > _______________________________________________ > > > freebsd-mobile@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > > > To unsubscribe, send any mail to > > > "freebsd-mobile-unsubscribe@freebsd.org" > > > > > _______________________________________________ > > freebsd-mobile@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > > To unsubscribe, send any mail to > > "freebsd-mobile-unsubscribe@freebsd.org" > > _______________________________________________ > 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" > Hello, here are my configuration files which worked on T42 and now after migration in X31. HTH. # cat /freebsd/etc/sysctl.conf # kern.random.sys.seeded=0 kern.random.sys.harvest.point_to_point=0 hw.acpi.lid_switch_state=S3 dev.acpi_ibm.0.events=1 hw.snd.maxautovchans=4 vfs.usermount=1 compat.linux.osrelease=2.6.16 # cat /freebsd/boot/loader.conf acpi_load="YES" # acpi_ibm_load="YES" snd_ich_load="YES" # # T42 # if_iwi_load="YES" # iwi_bss_load="YES" # iwi_ibss_load="YES" # iwi_monitor_load="YES" # # wlan_load="YES" # firmware_load="YES" # # copyright Intel # legal.intel_iwi.license_ack=1 BTW I had to add "/etc/rc.d/moused restart" into the rc.resume Have fun, :) -- -vlado Vladimir Botka From Juergen.Dankoweit at T-Online.de Fri Sep 19 11:13:23 2008 From: Juergen.Dankoweit at T-Online.de (Juergen Dankoweit) Date: Fri Sep 19 11:13:24 2008 Subject: Thinkap T43 suspend/resume only once In-Reply-To: <20080919093447.136f79dc@vlado.netng.org> References: <1221732390.1279.1.camel@t43.juergendankoweit.net> <20080919.032334.54135277.iwasaki@jp.FreeBSD.org> <1221765147.1437.8.camel@t43.juergendankoweit.net> <20080919093447.136f79dc@vlado.netng.org> Message-ID: <1221822777.1905.28.camel@t43.juergendankoweit.net> Hello, thanks for your hints. Am Freitag, den 19.09.2008, 09:34 +0200 schrieb Vladimir Botka: > Hello, > > here are my configuration files which worked on T42 and now after > migration in X31. HTH. > > # cat /freebsd/etc/sysctl.conf > # kern.random.sys.seeded=0 > kern.random.sys.harvest.point_to_point=0 > hw.acpi.lid_switch_state=S3 > dev.acpi_ibm.0.events=1 > hw.snd.maxautovchans=4 > vfs.usermount=1 > compat.linux.osrelease=2.6.16 > > # cat /freebsd/boot/loader.conf > acpi_load="YES" > # acpi_ibm_load="YES" > snd_ich_load="YES" Why did comment out acpi_ibm_load="YES"? I thought this is needed for: dev.acpi_ibm.0.events=1 > # > # T42 > # if_iwi_load="YES" > # iwi_bss_load="YES" > # iwi_ibss_load="YES" > # iwi_monitor_load="YES" > # > # wlan_load="YES" > # firmware_load="YES" > # > # copyright Intel > # legal.intel_iwi.license_ack=1 > > BTW I had to add "/etc/rc.d/moused restart" into the rc.resume I have changed the flags for the psm driver in /boot/device.hints: hint.psm.0.flags="0x2000" This has a similar effect. Thanks again for your hints Juergen From 0ac5 at packet-pushers.com Fri Sep 19 23:21:01 2008 From: 0ac5 at packet-pushers.com (Duane Wessels) Date: Fri Sep 19 23:21:07 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> References: <20080828002919.GA54169@alpha.local> <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> Message-ID: <20080919155900.P29264@life-gone-hazy.com> On Mon, 15 Sep 2008, Henri-Pierre Charles said: > I've tried 7.1-BETA and 8.0-CURRENT-200809 on my eeepc model 701 > > 7.1 does not recognize ath0, as expected, but 8.0-CURRENT does. For the record, the same is true for my Acer Aspire One. After updating sys/contrib/dev/ath to HEAD I now have a working ath0. hooray! Duane W. From frank at exit.com Sat Sep 20 00:21:26 2008 From: frank at exit.com (Frank Mayhar) Date: Sat Sep 20 00:21:29 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <20080919155900.P29264@life-gone-hazy.com> References: <20080828002919.GA54169@alpha.local> <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> <20080919155900.P29264@life-gone-hazy.com> Message-ID: <1221868355.63110.2.camel@jill.exit.com> On Fri, 2008-09-19 at 16:02 -0700, Duane Wessels wrote: > > On Mon, 15 Sep 2008, Henri-Pierre Charles said: > > > I've tried 7.1-BETA and 8.0-CURRENT-200809 on my eeepc model 701 > > > > 7.1 does not recognize ath0, as expected, but 8.0-CURRENT does. > > For the record, the same is true for my Acer Aspire One. After > updating sys/contrib/dev/ath to HEAD I now have a working ath0. > hooray! On the other hand, mine doesn't. I have a brand new Lifebook E8420 and I believe the Atheros wireless chipset is an a/g/n chipset. It lists as: none0@pci0:32:0:0: class=0x028000 card=0x147c10cf chip=0x002a168c rev=0x01 hdr=0x00 I read somewhere that this chipset is supported by the new ath9k Linux driver but, of course, I run FreeBSD. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From sam at freebsd.org Sat Sep 20 00:57:36 2008 From: sam at freebsd.org (Sam Leffler) Date: Sat Sep 20 00:57:41 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <1221868355.63110.2.camel@jill.exit.com> References: <20080828002919.GA54169@alpha.local> <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> <20080919155900.P29264@life-gone-hazy.com> <1221868355.63110.2.camel@jill.exit.com> Message-ID: <48D44A6F.1020408@freebsd.org> Frank Mayhar wrote: > On Fri, 2008-09-19 at 16:02 -0700, Duane Wessels wrote: > >> On Mon, 15 Sep 2008, Henri-Pierre Charles said: >> >> >>> I've tried 7.1-BETA and 8.0-CURRENT-200809 on my eeepc model 701 >>> >>> 7.1 does not recognize ath0, as expected, but 8.0-CURRENT does. >>> >> For the record, the same is true for my Acer Aspire One. After >> updating sys/contrib/dev/ath to HEAD I now have a working ath0. >> hooray! >> > > On the other hand, mine doesn't. I have a brand new Lifebook E8420 and > I believe the Atheros wireless chipset is an a/g/n chipset. It lists > as: > > none0@pci0:32:0:0: class=0x028000 card=0x147c10cf chip=0x002a168c rev=0x01 hdr=0x00 > > I read somewhere that this chipset is supported by the new ath9k Linux > driver but, of course, I run FreeBSD. > That's a merlin part (aka 9280); I've got untested changes to support it. Unfortunately I don't have a card so it may take a while to get something out. Unfortunately it's not feasible for me to send out test code to try until I can actually work w/ a card. Sam From frank at exit.com Sat Sep 20 05:12:14 2008 From: frank at exit.com (Frank Mayhar) Date: Sat Sep 20 05:12:23 2008 Subject: HEADS UP: ath_hal updated to 0.10.5.10 -- PLEASE TEST In-Reply-To: <48D44A6F.1020408@freebsd.org> References: <20080828002919.GA54169@alpha.local> <4734a3ed0809150659n438a5b20r59278908f4032a45@mail.gmail.com> <20080919155900.P29264@life-gone-hazy.com> <1221868355.63110.2.camel@jill.exit.com> <48D44A6F.1020408@freebsd.org> Message-ID: <1221887499.64423.1.camel@jill.exit.com> On Fri, 2008-09-19 at 17:57 -0700, Sam Leffler wrote: > Frank Mayhar wrote: > > On Fri, 2008-09-19 at 16:02 -0700, Duane Wessels wrote: > > > >> On Mon, 15 Sep 2008, Henri-Pierre Charles said: > >> > >> > >>> I've tried 7.1-BETA and 8.0-CURRENT-200809 on my eeepc model 701 > >>> > >>> 7.1 does not recognize ath0, as expected, but 8.0-CURRENT does. > >>> > >> For the record, the same is true for my Acer Aspire One. After > >> updating sys/contrib/dev/ath to HEAD I now have a working ath0. > >> hooray! > >> > > > > On the other hand, mine doesn't. I have a brand new Lifebook E8420 and > > I believe the Atheros wireless chipset is an a/g/n chipset. It lists > > as: > > > > none0@pci0:32:0:0: class=0x028000 card=0x147c10cf chip=0x002a168c rev=0x01 hdr=0x00 > > > > I read somewhere that this chipset is supported by the new ath9k Linux > > driver but, of course, I run FreeBSD. > > > That's a merlin part (aka 9280); I've got untested changes to support > it. Unfortunately I don't have a card so it may take a while to get > something out. Unfortunately it's not feasible for me to send out test > code to try until I can actually work w/ a card. I would happily pay for a card if that would help. Just pick out the one you want and let me know. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From niktychina at gmail.com Sun Sep 21 17:29:13 2008 From: niktychina at gmail.com (Nikolay Tychina) Date: Sun Sep 21 17:29:16 2008 Subject: Aser Aspire 5520's ACPI asl Message-ID: Hello, i have problems with acpi on my Acer Aspire 5520. If anybody hasn't annoying console acpi error messages and has acpi works well, please, send me your .asl : # acpidump -dt > *name*-*system*.asl I will try compile it and use new DSDT. TNA, Nikolay. From jhay at meraka.org.za Mon Sep 22 13:25:05 2008 From: jhay at meraka.org.za (John Hay) Date: Mon Sep 22 13:25:07 2008 Subject: setting bssid in adhoc mode Message-ID: <20080922132500.GA25677@zibbi.meraka.csir.co.za> Hi I'm trying out the new ath/wlan stuff in current. Should one still be able to set the bssid in adhoc mode? We normally lock the bssid in an adhoc network because of problems that the network split and does not merge, if you do not do it. What I have done is this: # ifconfig wlan0 create wlandev ath0 wlanmode adhoc # ifconfig wlan0 ssid ptamesh up Up to here works well. It will scan and if it finds another node with the same ssid, it will "lock" on that channel and use the correct bssid. If it does not find another node with the same ssid, it will start it own thing on channel 10. But it looks like one cannot set the bssid. # ifconfig wlan0 bssid 02:07:ca:fe:ba:be ifconfig: 02:07:ca:fe:ba:be: bad value So should it work or should I do it in a different way? I saw a wlanbssid command in the ifconfig man page, but it does not seem to do anything. I tried it like this: # ifconfig wlan0 create wlandev ath0 wlanmode adhoc wlanbssid 02:07:ca:fe:ba:be It did not give an error, but also did not lock the bssid. John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From sam at freebsd.org Mon Sep 22 15:48:23 2008 From: sam at freebsd.org (Sam Leffler) Date: Mon Sep 22 15:48:25 2008 Subject: setting bssid in adhoc mode In-Reply-To: <20080922132500.GA25677@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> Message-ID: <48D7BE46.10306@freebsd.org> John Hay wrote: > Hi > > I'm trying out the new ath/wlan stuff in current. Should one still be > able to set the bssid in adhoc mode? We normally lock the bssid in > an adhoc network because of problems that the network split and does > not merge, if you do not do it. > > What I have done is this: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > # ifconfig wlan0 ssid ptamesh up > > Up to here works well. It will scan and if it finds another node with the > same ssid, it will "lock" on that channel and use the correct bssid. > > If it does not find another node with the same ssid, it will start it > own thing on channel 10. But it looks like one cannot set the bssid. > > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > ifconfig: 02:07:ca:fe:ba:be: bad value > > So should it work or should I do it in a different way? I saw a > wlanbssid command in the ifconfig man page, but it does not seem to > do anything. I tried it like this: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc wlanbssid 02:07:ca:fe:ba:be > > It did not give an error, but also did not lock the bssid. > > It should be possible to alter the bssid. wlanbssid is used to fix the bssid/mac address of the vap at create. Sam From jakub_lach at mailplus.pl Wed Sep 24 01:08:27 2008 From: jakub_lach at mailplus.pl (Jakub Lach) Date: Wed Sep 24 01:08:30 2008 Subject: 7 STABLE on Fujitsu Siemens E8420/E8410 /Lenovo T61 Message-ID: <19639964.post@talk.nabble.com> Hi. I'm going to buy notebook soon. My basic requirments are: -robust construction -FreeBSD amd64 7 STABLE OS -2GB+/4GB RAM, preferably DDR3 -working sound, wifi -working PCMCIA -working Speedstep -working temperature monitoring (mbmon or similar) -moderate power consumption -fast core 2 penryn cpu Since nvidia driver doesn't support amd64, their cards are out of question. Moreover, there are heat/voltage problems with them recently. E8420 is using Intel GMA X4500 HD, will it work with FreeBSD? I've found this: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-intel.git;a=commit;h=1cfe769c74d1a3a392bf1aaaf5c2dcc8273daf66 Any thoughts are appreciated, I've already read "Laptop suggestions?" by Frank Mayhar-2 regards -Jakub Lach -- View this message in context: http://www.nabble.com/7-STABLE-on-Fujitsu-Siemens-E8420-E8410--Lenovo-T61-tp19639964p19639964.html Sent from the freebsd-mobile mailing list archive at Nabble.com. From jakub_lach at mailplus.pl Thu Sep 25 00:16:46 2008 From: jakub_lach at mailplus.pl (Jakub Lach) Date: Thu Sep 25 00:16:52 2008 Subject: ThinkPad T400 In-Reply-To: <48C41BD1.6070903@csub.edu> References: <48C41BD1.6070903@csub.edu> Message-ID: <19660745.post@talk.nabble.com> Russell Jackson-3 wrote: > > I received my t400 at last, and I thought I'd share my experiences with > it so far. > > ----8<-----snip--- > > Any progress with FreeBSD? It would be nice to have Montevina FreeBSD laptop. /I'm looking for a notebook that would have: nice finish like T Thinkpads, Intel integrated graphicscard, running 7 STABLE amd64, 4GB DDR3, Fast Penryn, working sound and wifi/ regards -Jakub Lach -- View this message in context: http://www.nabble.com/ThinkPad-T400-tp19361215p19660745.html Sent from the freebsd-mobile mailing list archive at Nabble.com. From frank at exit.com Thu Sep 25 04:45:49 2008 From: frank at exit.com (Frank Mayhar) Date: Thu Sep 25 04:45:56 2008 Subject: Atheros wireless problems. Message-ID: <1222317948.1740.10.camel@jill.exit.com> So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I believe) Atheros chipset in it; it's an a/b/g card. This is to use while the chipset embedded in my laptop isn't supported. It came today, I installed it tonight and, well, problems. I can get it to associate and, sometimes, even to get an IP address, but as soon as I start trying to actually pass traffic on it, all hell breaks loose. It starts timing out and the ath_hal starts complaining. Essential information: ath0@pci0:57:0:0: class=0x020000 card=0x3a631186 chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' class = network subclass = ethernet ath0: flags=8843 metric 0 mtu 2290 ether 00:13:46:11:6b:41 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:13:46:11:6b:41 inet6 fe80::213:46ff:fe11:6b41%wlan0 prefixlen 64 scopeid 0x4 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid Unwired channel 1 (2412 Mhz 11g) bssid 00:1f:33:82:2f:6d regdomain FCC indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 18 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst ff roaming MANUAL >From the dmesg: ath0: mem 0xf2110000-0xf211ffff irq 17 at device 0.0 on cardbus0 ath0: [ITHREAD] ath0: WARNING: using obsoleted if_watchdog interface ath0: mac 5.9 phy 4.3 radio 3.6 wlan0: Ethernet address: 00:13:46:11:6b:41 Then from /var/log/messages: Sep 24 21:14:11 kernel: ath0: device timeout Sep 24 21:14:11 kernel: ath0: ath_reset: unable to reset hardware; hal status 3230480741 I've also seen: Sep 24 21:03:55 auton kernel: ath0: unable to reset hardware; hal status 3310983360 Sep 24 21:02:35 auton kernel: ath0: unable to reset hardware; hal status 0 But it has only been those messages. I haven't yet tried turning on bootverbose but I can if you would like. Any ideas? Any suggestions? As I sit here (using the wired em0 instead of ath0) the lights on the card are happily blinking but it's not doing anything at all. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From onemda at gmail.com Thu Sep 25 13:25:43 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Sep 25 13:25:49 2008 Subject: Atheros wireless problems. In-Reply-To: <1222317948.1740.10.camel@jill.exit.com> References: <1222317948.1740.10.camel@jill.exit.com> Message-ID: <3a142e750809250559h4f45bea0w524e1cb32b015ac6@mail.gmail.com> On 9/25/08, Frank Mayhar wrote: > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > believe) Atheros chipset in it; it's an a/b/g card. This is to use > while the chipset embedded in my laptop isn't supported. It came today, > I installed it tonight and, well, problems. > > I can get it to associate and, sometimes, even to get an IP address, but > as soon as I start trying to actually pass traffic on it, all hell > breaks loose. It starts timing out and the ath_hal starts complaining. What version of ath_hal are you using? Try one from CURRENT. From frank at exit.com Thu Sep 25 13:38:03 2008 From: frank at exit.com (Frank Mayhar) Date: Thu Sep 25 13:38:09 2008 Subject: Atheros wireless problems. In-Reply-To: <3a142e750809250559h4f45bea0w524e1cb32b015ac6@mail.gmail.com> References: <1222317948.1740.10.camel@jill.exit.com> <3a142e750809250559h4f45bea0w524e1cb32b015ac6@mail.gmail.com> Message-ID: <1222349881.1740.13.camel@jill.exit.com> On Thu, 2008-09-25 at 14:59 +0200, Paul B. Mahol wrote: > On 9/25/08, Frank Mayhar wrote: > > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > > believe) Atheros chipset in it; it's an a/b/g card. This is to use > > while the chipset embedded in my laptop isn't supported. It came today, > > I installed it tonight and, well, problems. > > > > I can get it to associate and, sometimes, even to get an IP address, but > > as soon as I start trying to actually pass traffic on it, all hell > > breaks loose. It starts timing out and the ath_hal starts complaining. > > What version of ath_hal are you using? Try one from CURRENT. Sorry, I forgot to mention that I am actually running 8-current: ath_hal: 0.10.5.10 (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425, RF2417) -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From onemda at gmail.com Thu Sep 25 14:41:32 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Sep 25 14:41:38 2008 Subject: setting bssid in adhoc mode In-Reply-To: <20080922132500.GA25677@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> Message-ID: <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> On 9/22/08, John Hay wrote: > Hi > > I'm trying out the new ath/wlan stuff in current. Should one still be > able to set the bssid in adhoc mode? We normally lock the bssid in > an adhoc network because of problems that the network split and does > not merge, if you do not do it. > > What I have done is this: > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > # ifconfig wlan0 ssid ptamesh up > > Up to here works well. It will scan and if it finds another node with the > same ssid, it will "lock" on that channel and use the correct bssid. > > If it does not find another node with the same ssid, it will start it > own thing on channel 10. But it looks like one cannot set the bssid. > > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > ifconfig: 02:07:ca:fe:ba:be: bad value I had similar experience with STA mode, instead I use ap (ap is alias for bssid, at least it works in STA mode) I never bothered is this bug in manual page, ifconfig or in something else ... From sam at freebsd.org Thu Sep 25 15:53:33 2008 From: sam at freebsd.org (Sam Leffler) Date: Thu Sep 25 15:53:38 2008 Subject: Atheros wireless problems. In-Reply-To: <1222317948.1740.10.camel@jill.exit.com> References: <1222317948.1740.10.camel@jill.exit.com> Message-ID: <48DBB3EF.3060909@freebsd.org> Frank Mayhar wrote: > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > believe) Atheros chipset in it; it's an a/b/g card. This is to use > while the chipset embedded in my laptop isn't supported. It came today, > I installed it tonight and, well, problems. > > I can get it to associate and, sometimes, even to get an IP address, but > as soon as I start trying to actually pass traffic on it, all hell > breaks loose. It starts timing out and the ath_hal starts complaining. > > Essential information: > > ath0@pci0:57:0:0: class=0x020000 card=0x3a631186 chip=0x0013168c rev=0x01 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR5212, AR5213 802.11a/b/g Wireless Adapter' > class = network > subclass = ethernet > ath0: flags=8843 metric 0 mtu 2290 > ether 00:13:46:11:6b:41 > media: IEEE 802.11 Wireless Ethernet autoselect mode 11g > status: associated > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:13:46:11:6b:41 > inet6 fe80::213:46ff:fe11:6b41%wlan0 prefixlen 64 scopeid 0x4 > media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g > status: associated > ssid Unwired channel 1 (2412 Mhz 11g) bssid 00:1f:33:82:2f:6d > regdomain FCC indoor ecm authmode WPA2/802.11i privacy ON > deftxkey UNDEF TKIP 2:128-bit txpower 18 bmiss 7 scanvalid 450 bgscan > bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS > wme burst ff roaming MANUAL > > >From the dmesg: > ath0: mem 0xf2110000-0xf211ffff irq 17 at device 0.0 on cardbus0 > ath0: [ITHREAD] > ath0: WARNING: using obsoleted if_watchdog interface > ath0: mac 5.9 phy 4.3 radio 3.6 > wlan0: Ethernet address: 00:13:46:11:6b:41 > > Then from /var/log/messages: > Sep 24 21:14:11 kernel: ath0: device timeout > Sep 24 21:14:11 kernel: ath0: ath_reset: unable to reset hardware; hal status 3230480741 > > I've also seen: > Sep 24 21:03:55 auton kernel: ath0: unable to reset hardware; hal status 3310983360 > Sep 24 21:02:35 auton kernel: ath0: unable to reset hardware; hal status 0 > > But it has only been those messages. I haven't yet tried turning on > bootverbose but I can if you would like. > > Any ideas? Any suggestions? As I sit here (using the wired em0 instead > of ath0) the lights on the card are happily blinking but it's not doing > anything at all. > The status codes look bogus. In 0.10.5.10 there is a code path through reset where status is not set if the chip is not brought out of low power mode. Why this might happen is beyond me (could be a cardbus problem) but if you initialize status to a known value before the hal calls that are failing this might confirm that as the problem. I've fixed the hal fwiw. Sam From jhay at meraka.org.za Thu Sep 25 16:13:42 2008 From: jhay at meraka.org.za (John Hay) Date: Thu Sep 25 16:13:48 2008 Subject: setting bssid in adhoc mode In-Reply-To: <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> Message-ID: <20080925161338.GA69284@zibbi.meraka.csir.co.za> On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: > On 9/22/08, John Hay wrote: > > Hi > > > > I'm trying out the new ath/wlan stuff in current. Should one still be > > able to set the bssid in adhoc mode? We normally lock the bssid in > > an adhoc network because of problems that the network split and does > > not merge, if you do not do it. > > > > What I have done is this: > > > > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > > # ifconfig wlan0 ssid ptamesh up > > > > Up to here works well. It will scan and if it finds another node with the > > same ssid, it will "lock" on that channel and use the correct bssid. > > > > If it does not find another node with the same ssid, it will start it > > own thing on channel 10. But it looks like one cannot set the bssid. > > > > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > > ifconfig: 02:07:ca:fe:ba:be: bad value > > I had similar experience with STA mode, instead I use ap (ap is alias > for bssid, at least it works in STA mode) > I never bothered is this bug in manual page, ifconfig or in something else ... Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. Just do not try to unset it with "ifconfig wlan0 ap -". That is an alias for "panic now" :-) So it looks like ifconfig is getting confused with the many different uses of the keyword bssid. I must say I still do not understand what the other use for bssid is. Close to the end of ifconfig/ifieee80211.c there are these: DEF_CMD_ARG("bssid", set80211bssid), DEF_CMD_ARG("ap", set80211bssid), ... DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), So my guess is that I was hitting the clone version when in fact I needed the other version. Luckily ap does not have a clone version. So when should the clone version be used? And how does ifconfig decide which one to use? John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From raj at csub.edu Thu Sep 25 17:50:55 2008 From: raj at csub.edu (Russell Jackson) Date: Thu Sep 25 17:51:03 2008 Subject: ThinkPad T400 In-Reply-To: <19660745.post@talk.nabble.com> References: <48C41BD1.6070903@csub.edu> <19660745.post@talk.nabble.com> Message-ID: <48DBCF7E.9080005@csub.edu> Jakub Lach wrote: > > Russell Jackson-3 wrote: >> I received my t400 at last, and I thought I'd share my experiences with >> it so far. >> >> ----8<-----snip--- >> >> > > Any progress with FreeBSD? It would be nice to have Montevina FreeBSD > laptop. > > > /I'm looking for a notebook that would have: nice finish like T Thinkpads, > Intel integrated graphicscard, running 7 STABLE amd64, 4GB DDR3, Fast > Penryn, working sound and wifi/ > I noticed there was a new September CURRENT snapshot, but I haven't had time to try it. The other problem is that Ubuntu has been working too well which makes me hesitant to start all over from scratch ;-). -- Russell A. Jackson Network Analyst California State University, Bakersfield Confidence is the feeling you have before you understand the situation. From onemda at gmail.com Thu Sep 25 18:59:38 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Thu Sep 25 18:59:45 2008 Subject: setting bssid in adhoc mode In-Reply-To: <20080925161338.GA69284@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> Message-ID: <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> On 9/25/08, John Hay wrote: > On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >> On 9/22/08, John Hay wrote: >> > Hi >> > >> > I'm trying out the new ath/wlan stuff in current. Should one still be >> > able to set the bssid in adhoc mode? We normally lock the bssid in >> > an adhoc network because of problems that the network split and does >> > not merge, if you do not do it. >> > >> > What I have done is this: >> > >> > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >> > # ifconfig wlan0 ssid ptamesh up >> > >> > Up to here works well. It will scan and if it finds another node with >> > the >> > same ssid, it will "lock" on that channel and use the correct bssid. >> > >> > If it does not find another node with the same ssid, it will start it >> > own thing on channel 10. But it looks like one cannot set the bssid. >> > >> > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >> > ifconfig: 02:07:ca:fe:ba:be: bad value >> >> I had similar experience with STA mode, instead I use ap (ap is alias >> for bssid, at least it works in STA mode) >> I never bothered is this bug in manual page, ifconfig or in something else >> ... > > Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. > Just do not try to unset it with "ifconfig wlan0 ap -". That is an > alias for "panic now" :-) Well, on my system it doesnt panic here. So more info to debug "your" panic is required ... > > So it looks like ifconfig is getting confused with the many different > uses of the keyword bssid. > > I must say I still do not understand what the other use for bssid is. > Close to the end of ifconfig/ifieee80211.c there are these: > > DEF_CMD_ARG("bssid", set80211bssid), > DEF_CMD_ARG("ap", set80211bssid), > ... > DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), > DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), > > So my guess is that I was hitting the clone version when in fact I > needed the other version. Luckily ap does not have a clone version. > So when should the clone version be used? And how does ifconfig > decide which one to use? From jhay at meraka.org.za Fri Sep 26 05:55:25 2008 From: jhay at meraka.org.za (John Hay) Date: Fri Sep 26 05:55:32 2008 Subject: setting bssid in adhoc mode In-Reply-To: <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> Message-ID: <20080926055522.GA13842@zibbi.meraka.csir.co.za> On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: > On 9/25/08, John Hay wrote: > > On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: > >> On 9/22/08, John Hay wrote: > >> > Hi > >> > > >> > I'm trying out the new ath/wlan stuff in current. Should one still be > >> > able to set the bssid in adhoc mode? We normally lock the bssid in > >> > an adhoc network because of problems that the network split and does > >> > not merge, if you do not do it. > >> > > >> > What I have done is this: > >> > > >> > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc > >> > # ifconfig wlan0 ssid ptamesh up > >> > > >> > Up to here works well. It will scan and if it finds another node with > >> > the > >> > same ssid, it will "lock" on that channel and use the correct bssid. > >> > > >> > If it does not find another node with the same ssid, it will start it > >> > own thing on channel 10. But it looks like one cannot set the bssid. > >> > > >> > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be > >> > ifconfig: 02:07:ca:fe:ba:be: bad value > >> > >> I had similar experience with STA mode, instead I use ap (ap is alias > >> for bssid, at least it works in STA mode) > >> I never bothered is this bug in manual page, ifconfig or in something else > >> ... > > > > Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. > > Just do not try to unset it with "ifconfig wlan0 ap -". That is an > > alias for "panic now" :-) > Well, on my system it doesnt panic here. > So more info to debug "your" panic is required ... I'll have to see if I can reproduce it. > > So it looks like ifconfig is getting confused with the many different > > uses of the keyword bssid. > > > > I must say I still do not understand what the other use for bssid is. > > Close to the end of ifconfig/ifieee80211.c there are these: > > > > DEF_CMD_ARG("bssid", set80211bssid), > > DEF_CMD_ARG("ap", set80211bssid), > > ... > > DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), > > DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), > > > > So my guess is that I was hitting the clone version when in fact I > > needed the other version. Luckily ap does not have a clone version. > > So when should the clone version be used? And how does ifconfig > > decide which one to use? I looked into the ifconfig code a bit more. I think that with the current code in the ifconfig() and cmd_lookup() functions, it is imposssible to have two different keywords that share the same keyword. cmd_lookup() will always search until it finds the first instance in the list and return that. The first instance in this case being the last one added. So either the code must change or one of the bssid keywords have to change. My suggestion would be to keep the bssid for which ap is an alias and change the other one. Anybody have a suggestion of what to change it to? John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From waynehendricks at gmail.com Fri Sep 26 06:29:54 2008 From: waynehendricks at gmail.com (Wayne Hendricks) Date: Fri Sep 26 06:30:02 2008 Subject: Hostapd network issue In-Reply-To: <3b965dec0809252258t15722eecn29494431bced3061@mail.gmail.com> References: <3b965dec0809252258t15722eecn29494431bced3061@mail.gmail.com> Message-ID: <3b965dec0809252302j2534db24j1666626f3340090d@mail.gmail.com> I have been trying to make hostapd work with the wifi card in my gateway box. WPA stays working for only a short time before hostapd locks up and needs to be restarted. I believe the hosapd config is fine, shows no errors. Running 7.0-RELEASE-p4 amd64 with mini-pci Atheros 5212 chipset. ath0 and bge1 are bridged to bridge0. I have included the hostapd debug output below. What is this ioctl[SIOCS80211] weirdness? Configuration file: /etc/hostapd.conf ctrl_interface_group=0 (from group name 'wheel') bsd_set_iface_flags: dev_up=0 BSS count 1, BSSID mask ff:ff:ff:ff:ff:ff (0 bits) ath0: IEEE 802.11 Fetching hardware channel/rate support not supported. Flushing old station entries bsd_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3 Deauthenticate all stations bsd_set_privacy: enabled=0 Mode: IEEE 802.11g Channel: 11 Frequency: 0 MHz bsd_del_key: addr=00:00:00:00:00:00 key_idx=0 bsd_del_key: addr=00:00:00:00:00:00 key_idx=1 bsd_del_key: addr=00:00:00:00:00:00 key_idx=2 bsd_del_key: addr=00:00:00:00:00:00 key_idx=3 bsd_get_ssid: ssid="bsdap" Using interface ath0 with hwaddr 00:90:96:6b:0f:c6 and ssid 'bsdap' SSID - hexdump_ascii(len=9): 52 4e 73 65 63 75 72 65 47 bsdap PSK (ASCII passphrase) - hexdump_ascii(len=12): 65 74 68 65 72 61 70 65 31 31 31 36 mypassphrase PSK (from passphrase) - hexdump(len=32): 17 ae 54 6a a7 c4 fc ce e2 d4 2e 07 0d 08 09 56 41 d3 a4 6a d2 18 26 d1 36 22 56 fe a0 af 26 43 bsd_set_ieee8021x: enabled=1 bsd_configure_wpa: group key cipher=TKIP (1) bsd_configure_wpa: pairwise key ciphers=0xa bsd_configure_wpa: key management algorithms=0x2 bsd_configure_wpa: rsn capabilities=0x0 bsd_configure_wpa: enable WPA= 0x1 bsd_set_iface_flags: dev_up=1 WPA: group state machine entering state GTK_INIT (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 bsd_set_privacy: enabled=1 ath0: Setup of interface done. ath0: STA 00:1e:c2:bf:74:60 IEEE 802.11: associated New STA ath0: STA 00:1e:c2:bf:74:60 WPA: event 1 notification bsd_del_key: addr=00:1e:c2:bf:74:60 key_idx=0 ath0: STA 00:1e:c2:bf:74:60 WPA: start authentication WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:1e:c2:bf:74:60 key_idx=0 bsd_set_sta_authorized: addr=00:1e:c2:bf:74:60 authorized=0 ath0: STA 00:1e:c2:bf:74:60 IEEE 802.1X: unauthorizing port WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state AUTHENTICATION WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state AUTHENTICATION2 WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state INITPSK WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKSTART ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0 encr=0) TX EAPOL - hexdump(len=113): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 88 8e 02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 9f 2b fa 4e 6e 00 d2 a0 fd 9e f0 c1 fd be 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 IEEE 802.1X: 123 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=119 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/4 Pairwise) WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKCALCNEGOTIATING PMK - hexdump(len=32): [REMOVED] PTK - hexdump(len=64): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKCALCNEGOTIATING2 WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKINITNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:1e:c2:bf:74:60 WPA: sending 3/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=1 ack=1 install=1 pairwise=8 kde_len=28 keyidx=0 encr=0) TX EAPOL - hexdump(len=141): 00 1e c2 bf 74 60 00 00 96 6b 0f c6 88 8e 02 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd be 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 cf 86 6a 87 74 59 72 dc 2f 01 f9 8b b4 20 51 1f 00 1c dd 1a 00 50 f2 0 1 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (4/4 Pairwise) WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state PTKINITDONE bsd_set_key: alg=CCMP addr=00:1e:c2:bf:74:60 key_idx=0 bsd_set_sta_authorized: addr=00:1e:c2:bf:74:60 authorized=1 ath0: STA 00:1e:c2:bf:74:60 IEEE 802.1X: authorizing port bsd_sta_clear_stats: addr=00:1e:c2:bf:74:60 ath0: STA 00:1e:c2:bf:74:60 WPA: pairwise key handshake completed (WPA) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 3b 0f c6 88 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 24 d8 ba b9 34 15 fd ae 04 7c 59 05 d4 08 70 4c 00 28 36 25 48 ae 3c 8 d ad 9b 27 20 45 68 36 d7 57 ba 57 49 0f 7d e9 2b 1d 6b b5 21 c1 a4 e5 77 fc 57 fd 57 c1 90 be a2 50 a4 ath0: STA 00:1e:c2:bf:74:60 WPA: EAPOL-Key timeout WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 46 6b 0f c6 88 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 04 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0 3a d0 8a fd 74 2d 9a cf ba eb 75 56 26 71 63 00 28 36 25 48 ae 3c 8 d ad 9b 27 20 45 68 36 d7 57 ba 57 49 0f 7d e9 2b 1d 6b b5 21 c1 a4 e5 77 fc 37 fd 57 c1 00 be a2 50 a4 IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:1e:c2:bf:74:60 WPA: group key handshake completed (WPA) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: STA 00:21:e9:6e:98:d0 IEEE 802.11: associated New STA ath0: STA 00:21:e9:6e:98:d0 WPA: event 1 notification bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 ath0: STA 00:21:e9:6e:98:d0 WPA: start authentication WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=0 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: unauthorizing port WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state IDLE WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state AUTHENTICATION WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state AUTHENTICATION2 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITPSK WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKSTART ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0 encr=0) TX EAPOL - hexdump(len=113): 00 21 e9 6e 68 d0 00 90 96 6b 0f c6 58 8e 02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bf 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 IEEE 802.1X: 123 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=119 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (2/4 Pairwise) WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKCALCNEGOTIATING PMK - hexdump(len=32): [REMOVED] PTK - hexdump(len=64): [REMOVED] WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKCALCNEGOTIATING2 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKINITNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 3/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=1 ack=1 install=1 pairwise=8 kde_len=28 keyidx=0 encr=0) TX EAPOL - hexdump(len=141): 00 21 e9 6e 98 d0 00 90 96 6b 0f c5 88 8e 02 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bf 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e2 55 c7 5a e3 2d 7a 54 f2 6d f0 7b 9f cc ca b3 00 1c dd 1a 00 50 f2 0 1 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 50 f2 02 IEEE 802.1X: 99 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (4/4 Pairwise) WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKINITDONE bsd_set_key: alg=CCMP addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=1 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: authorizing port bsd_sta_clear_stats: addr=00:21:e9:6e:98:d0 ath0: STA 00:21:e9:6e:98:d0 WPA: pairwise key handshake completed (WPA) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 21 e9 6e 98 d0 00 90 96 6b 0f c6 68 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bb 76 69 1b 31 76 d5 81 87 d1 fb f5 ac 85 f1 d7 00 28 f6 9f 0d ca 6e 4 b 9c 54 56 98 09 75 79 a1 35 b0 90 a2 77 33 48 3e 5c 5d 03 cc 8e 6b 1c 10 cd af a5 66 58 5f d2 fb 3d 48 ath0: STA 00:21:e9:6e:98:d0 WPA: EAPOL-Key timeout WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 21 e9 6e 98 d0 00 90 96 6b 0f c6 88 8e 02 03 00 47 fe 03 92 00 20 00 00 00 00 00 00 00 04 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd bd 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ec 85 4f 9e d0 f7 89 9c a5 aa da f7 94 32 96 1b 00 28 f6 9f 0d ca 6e 4 b 9c 54 56 98 09 75 79 a1 35 b0 90 a2 77 33 48 3e 5c 5d 03 cc 3e 6b 1c 10 cd af a5 96 58 5f d2 fb 3d 48 IEEE 802.1X: 99 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:21:e9:6e:98:d0 WPA: group key handshake completed (WPA) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state IDLE ath0: STA 00:21:e9:6e:98:d0 IEEE 802.11: deassociated ath0: STA 00:21:e9:6e:98:d0 WPA: event 2 notification bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state DISCONNECTED WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=0 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: unauthorizing port Could not set station 00:21:e9:6e:98:d0 flags for kernel driver (errno=22). ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=2 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 3b 0f c6 88 8e 02 03 00 87 fe 03 a2 00 20 00 00 00 00 00 00 00 05 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 21 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2e 4a 9b 73 a4 2a 85 58 43 ea 4b 26 39 52 da 0b 00 28 97 d8 b5 38 1a 9 9 dc 43 65 b5 bd ac 8c 7e 35 2c 12 7c 55 d4 79 0a 54 68 4c 5c 59 36 5b f6 69 31 ad 4a 90 ff 81 be c6 4f IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:1e:c2:bf:74:60 WPA: group key handshake completed (WPA) WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 76 6b 0f c6 88 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 06 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 16 82 a2 6d 95 4d 6b 3c ce 5b 05 47 76 55 00 28 7a a2 9a 85 ef a f a9 be 86 56 94 45 a3 ab b8 a5 b3 d5 44 3b a4 d3 9f 7b 3d ea 97 e6 c3 ed 9e 42 da 4b 91 2d fd 7f 1e 8d IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:1e:c2:bf:74:60 WPA: group key handshake completed (WPA) WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: STA 00:21:e9:6e:98:d0 IEEE 802.11: associated New STA ath0: STA 00:21:e9:6e:98:d0 WPA: event 1 notification bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 ath0: STA 00:21:e9:6e:98:d0 WPA: start authentication WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=0 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: unauthorizing port WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state IDLE WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state AUTHENTICATION WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state AUTHENTICATION2 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITPSK WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKSTART ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=0 ack=1 install=0 pairwise=8 kde_len=0 keyidx=0 encr=0) TX EAPOL - hexdump(len=113): 00 21 e9 6e 98 d0 00 30 96 6b 0f c6 88 8e 02 03 00 5f fe 00 8a 00 10 00 00 00 00 00 00 00 01 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 3b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 IEEE 802.1X: 123 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=119 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (2/4 Pairwise) WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKCALCNEGOTIATING PMK - hexdump(len=32): [REMOVED] PTK - hexdump(len=64): [REMOVED] WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKCALCNEGOTIATING2 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKINITNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 3/4 msg of 4-Way Handshake WPA: Send EAPOL(secure=0 mic=1 ack=1 install=1 pairwise=8 kde_len=28 keyidx=0 encr=0) TX EAPOL - hexdump(len=141): 00 21 e9 6e 78 d0 00 90 96 6b 0f c6 88 8e 02 03 00 7b fe 01 ca 00 10 00 00 00 00 00 00 00 02 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 19 95 a0 4e 64 c6 43 6c e9 8c 02 ef 75 27 f9 e5 00 1c dd 1a 00 50 f2 0 1 01 00 00 50 f2 02 02 00 00 50 f2 04 00 50 f2 02 01 00 00 40 f2 02 IEEE 802.1X: 99 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (4/4 Pairwise) WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state PTKINITDONE bsd_set_key: alg=CCMP addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=1 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: authorizing port bsd_sta_clear_stats: addr=00:21:e9:6e:98:d0 ath0: STA 00:21:e9:6e:98:d0 WPA: pairwise key handshake completed (WPA) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYNEGOTIATING bsd_get_seqnum: addr=00:00:00:00:00:00 idx=1 ath0: STA 00:21:e9:6e:98:d0 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 21 e9 6e 08 d0 00 90 96 6b 0f c6 88 5e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 03 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 50 dc 19 fc 24 e2 56 37 16 14 5a 0b 00 25 c2 47 00 28 78 92 48 df 3b e f 3c d7 25 82 34 d2 32 7d 1f cc 12 d1 4e c0 89 dc 29 80 88 45 95 27 13 49 b0 da ef f9 c9 fd f0 52 a9 b5 IEEE 802.1X: 99 bytes from 00:21:e9:6e:98:d0 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:21:e9:6e:98:d0 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:21:e9:6e:98:d0 WPA: group key handshake completed (WPA) WPA: 00:21:e9:6e:98:d0 WPA_PTK_GROUP entering state IDLE ath0: STA 00:21:e9:6e:98:d0 IEEE 802.11: deassociated ath0: STA 00:21:e9:6e:98:d0 WPA: event 2 notification bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state DISCONNECTED WPA: 00:21:e9:6e:98:d0 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:21:e9:6e:98:d0 key_idx=0 bsd_set_sta_authorized: addr=00:21:e9:6e:98:d0 authorized=0 ath0: STA 00:21:e9:6e:98:d0 IEEE 802.1X: unauthorizing port Could not set station 00:21:e9:6e:98:d0 flags for kernel driver (errno=22). Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=2 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 78 8e 02 03 00 87 fe 03 a2 00 20 00 00 00 00 00 00 00 07 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0 00 be eb 48 36 b5 ad 1f 17 bc 64 ca 6b c8 ca 00 28 8a 2b 24 9f ee 4 4 0f e7 4a ad a8 55 62 cd b9 d0 69 cc af e4 94 01 aa d8 e9 cf cc a7 ed 6e e0 90 b5 3c 35 1a ae 2e 32 d7 IEEE 802.1X: 99 bytes from 00:1e:c2:bf:74:60 IEEE 802.1X: version=1 type=3 length=95 ath0: STA 00:1e:c2:bf:74:60 WPA: received EAPOL-Key frame (2/2 Group) WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYESTABLISHED ath0: STA 00:1e:c2:bf:74:60 WPA: group key handshake completed (WPA) WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active Checking STA 00:1e:c2:bf:74:60 inactivity: Station has been active ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 40 00 90 96 6b 0f c6 88 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 08 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c1 50 c3 fa 32 83 f8 05 c4 c3 78 e5 cf 48 25 79 00 28 10 4a c3 91 12 2 f 91 69 e3 84 e2 61 25 ce e9 b8 38 53 7f 8d f8 53 ec ac 90 43 41 5c b9 ec 97 54 a3 60 a9 d7 73 20 6d f1 ath0: STA 00:1e:c2:bf:74:60 WPA: EAPOL-Key timeout WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 88 8e 02 03 00 87 fe 03 92 00 10 00 00 00 00 00 00 00 09 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 29 b1 39 72 aa d0 25 02 a4 5b 01 55 a9 c6 5b cf 00 28 10 4a c3 91 12 2 f 91 69 e3 84 e2 61 25 ce e9 b8 38 53 7f 8d f8 53 ec ac 90 43 41 5c b9 ec 57 54 a3 60 a9 d7 73 20 6d f1 ath0: STA 00:1e:c2:bf:74:60 WPA: EAPOL-Key timeout WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 98 8e 02 03 00 87 fe 03 92 00 20 00 00 00 00 00 00 00 0a 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 94 79 9c 20 34 dd 26 28 c7 c2 6f a3 1c a4 03 44 00 28 10 4a c3 91 12 2 f 91 69 e3 84 e2 61 25 ce e9 b8 38 53 7f 8d f8 53 ec ac 90 43 41 5c b9 ec 57 54 a3 60 a9 d7 73 20 6d f1 ath0: STA 00:1e:c2:bf:74:60 WPA: EAPOL-Key timeout WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state REKEYNEGOTIATING ath0: STA 00:1e:c2:bf:74:60 WPA: sending 1/2 msg of Group Key Handshake WPA: Send EAPOL(secure=1 mic=1 ack=1 install=0 pairwise=0 kde_len=32 keyidx=1 encr=1) Plaintext EAPOL-Key Key Data - hexdump(len=40): [REMOVED] TX EAPOL - hexdump(len=153): 00 1e c2 bf 74 60 00 90 96 6b 0f c6 88 8e 02 03 00 87 fe 03 02 00 20 00 00 00 00 00 00 00 0b 1c c4 37 85 45 86 e9 2a 99 5c 65 8c 8b d0 b8 63 31 04 1f 2b fa 4e 8e 00 d2 a0 fd 9e f0 c1 fd c4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 91 86 ea b0 4b 7f c5 2b 2c 9c b2 94 67 d4 e6 14 00 28 10 4a c3 91 12 2 f 91 69 e3 84 e2 61 25 ce e9 b8 38 53 7f 8d f8 53 ec ac 90 43 41 5c b9 ec 57 54 a3 60 a8 d7 73 20 6d f1 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state KEYERROR WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state DISCONNECT hostapd_wpa_auth_disconnect: WPA authenticator requests disconnect: STA 00:1e:c2:bf:74:60 reason 2 bsd_sta_deauth: addr=00:1e:c2:bf:74:60 reason_code=2 WPA: 00:1e:c2:bf:74:60 WPA_PTK_GROUP entering state IDLE WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state DISCONNECTED WPA: 00:1e:c2:bf:74:60 WPA_PTK entering state INITIALIZE bsd_del_key: addr=00:1e:c2:bf:74:60 key_idx=0 bsd_set_sta_authorized: addr=00:1e:c2:bf:74:60 authorized=0 ath0: STA 00:1e:c2:bf:74:60 IEEE 802.1X: unauthorizing port Could not set station 00:1e:c2:bf:74:60 flags for kernel driver (errno=22). ath0: STA 00:1e:c2:bf:74:60 IEEE 802.11: deauthenticated due to local deauth request GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2 ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=2 ath0: WPA rekeying GTK WPA: group state machine entering state SETKEYS (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=TKIP addr=00:00:00:00:00:00 key_idx=1 ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: Invalid argument ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: Invalid argument ioctl[SIOCS80211]: No such file or directory ioctl[SIOCS80211]: Invalid argument Signal 2 received - terminating Flushing old station entries bsd_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code=3 Deauthenticate all stations bsd_set_privacy: enabled=0 bsd_set_ieee8021x: enabled=0 bsd_set_iface_flags: dev_up=0 From johnseth_2007 at yahoo.com Fri Sep 26 14:20:56 2008 From: johnseth_2007 at yahoo.com (john seth) Date: Fri Sep 26 16:05:25 2008 Subject: facility for mobile DDR RAM Message-ID: <688762.55289.qm@web45203.mail.sp1.yahoo.com> Hi friends, ???? I want to know whether there is facility for mobile DDR RAM, so that we can switch of a bank(s) without loosing the data in other bank(s). Thanks. From onemda at gmail.com Fri Sep 26 17:12:15 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Fri Sep 26 17:12:21 2008 Subject: setting bssid in adhoc mode In-Reply-To: <20080926055522.GA13842@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> Message-ID: <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> On 9/26/08, John Hay wrote: > On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: >> On 9/25/08, John Hay wrote: >> > On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >> >> On 9/22/08, John Hay wrote: >> >> > Hi >> >> > >> >> > I'm trying out the new ath/wlan stuff in current. Should one still be >> >> > able to set the bssid in adhoc mode? We normally lock the bssid in >> >> > an adhoc network because of problems that the network split and does >> >> > not merge, if you do not do it. >> >> > >> >> > What I have done is this: >> >> > >> >> > # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >> >> > # ifconfig wlan0 ssid ptamesh up >> >> > >> >> > Up to here works well. It will scan and if it finds another node with >> >> > the >> >> > same ssid, it will "lock" on that channel and use the correct bssid. >> >> > >> >> > If it does not find another node with the same ssid, it will start it >> >> > own thing on channel 10. But it looks like one cannot set the bssid. >> >> > >> >> > # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >> >> > ifconfig: 02:07:ca:fe:ba:be: bad value >> >> >> >> I had similar experience with STA mode, instead I use ap (ap is alias >> >> for bssid, at least it works in STA mode) >> >> I never bothered is this bug in manual page, ifconfig or in something >> >> else >> >> ... >> > >> > Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >> > Just do not try to unset it with "ifconfig wlan0 ap -". That is an >> > alias for "panic now" :-) >> Well, on my system it doesnt panic here. >> So more info to debug "your" panic is required ... > > I'll have to see if I can reproduce it. I managed to reproduce panic on recent CURRENT, with two cards in adhoc mode. rum0 (usb2) & ndis0 (personal hacked version without usb code) I typed "ifconfig wlan0 ap -" several times. bt: db:0:kdb.enter.unknown> run lockinfo db:1:lockinfo> show locks db:1:locks> show alllocks Process 1471 (ifconfig) thread 0xc4028690 (100048) Process 477 (syslogd) thread 0xc402b8c0 (100058) db:1:alllocks> show lockedvnods Locked vnodes db:0:kdb.enter.unknown> show pcpu cpuid = 1 curthread = 0xc4028690: pid 1471 "ifconfig" curpcb = 0xe64e1d90 fpcurthread = none idlethread = 0xc3cb1d20: pid 10 "idle: cpu1" APIC ID = 1 currentldt = 0x50 spin locks held: db:0:kdb.enter.unknown> bt Tracing pid 1471 tid 100048 td 0xc4028690 ieee80211_ht_adjust_channel(c46a8000,0,2,2,80000002,...) at ieee80211_ht_adjust_channel+0x30 adhoc_pick_bss(c4053000,c4113800,c0a1ebc3,23a,c3dd0108,...) at adhoc_pick_bss+0x100 ieee80211_check_scan(c4113800,2,7fffffff,0,0,...) at ieee80211_check_scan+0x20d ieee80211_check_scan_current(c4113800,4,c0a1fb47,6c,c4113800,...) at ieee80211_check_scan_current+0x45 adhoc_newstate(c4113800,1,0,648,e64e1aa0,...) at adhoc_newstate+0x219 ieee80211_new_state_locked(c4113800,0,c0a1e64c,49c,0,...) at ieee80211_new_state_locked+0xc4 ieee80211_init(c4113800,c0a24a64,6,c41adc00,1b9,...) at ieee80211_init+0x45 ieee80211_ioctl_set80211(c3e1ec00,801c69ea,c48c4240,c0709084,c4028690,...) at ieee80211_ioctl_set80211+0xe5 in_control(c4158188,801c69ea,c48c4240,c3e1ec00,c4028690,...) at in_control+0xdc4 ifioctl(c4158188,801c69ea,c48c4240,c4028690,801c69ea,...) at ifioctl+0x34a soo_ioctl(c43c9d90,801c69ea,c48c4240,c41adc00,c4028690,...) at soo_ioctl+0x397 kern_ioctl(c4028690,3,801c69ea,c48c4240,504110,...) at kern_ioctl+0x1dd ioctl(c4028690,e64e1cf8,c,c06d3f58,c0702bf0,...) at ioctl+0x134 syscall(e64e1d38) at syscall+0x283 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281a9a43, esp = 0xbfbfe48c, ebp = 0xbfbfe4d8 --- here is panic message: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0a0c5b0 stack pointer = 0x28:0xe64e1980 frame pointer = 0x28:0xe64e1990 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1471 (ifconfig) exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 (0xc46a8014) locked @ /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 (0xc46a8014) locked @ /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 exclusive lockmgr bufwait (bufwait) r = 0 (0xd7d083c0) locked @ /usr/src/sys/kern/vfs_bio.c:2443 exclusive lockmgr ufs (ufs) r = 0 (0xc41a2058) locked @ /usr/src/sys/kern/vfs_vnops.c:593 0xc41a2000: tag ufs, type VREG usecount 1, writecount 1, refcount 4 mountedhere 0 flags () v_object 0xc413aaa8 ref 0 pages 7 lock type ufs: EXCL by thread 0xc402b8c0 (pid 477) ino 164881, on dev ad4s1d From sam at freebsd.org Fri Sep 26 17:51:11 2008 From: sam at freebsd.org (Sam Leffler) Date: Fri Sep 26 17:51:17 2008 Subject: setting bssid in adhoc mode In-Reply-To: <20080926055522.GA13842@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> Message-ID: <48DD210E.6050300@freebsd.org> John Hay wrote: > On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: > >> On 9/25/08, John Hay wrote: >> >>> On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >>> >>>> On 9/22/08, John Hay wrote: >>>> >>>>> Hi >>>>> >>>>> I'm trying out the new ath/wlan stuff in current. Should one still be >>>>> able to set the bssid in adhoc mode? We normally lock the bssid in >>>>> an adhoc network because of problems that the network split and does >>>>> not merge, if you do not do it. >>>>> >>>>> What I have done is this: >>>>> >>>>> # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >>>>> # ifconfig wlan0 ssid ptamesh up >>>>> >>>>> Up to here works well. It will scan and if it finds another node with >>>>> the >>>>> same ssid, it will "lock" on that channel and use the correct bssid. >>>>> >>>>> If it does not find another node with the same ssid, it will start it >>>>> own thing on channel 10. But it looks like one cannot set the bssid. >>>>> >>>>> # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >>>>> ifconfig: 02:07:ca:fe:ba:be: bad value >>>>> >>>> I had similar experience with STA mode, instead I use ap (ap is alias >>>> for bssid, at least it works in STA mode) >>>> I never bothered is this bug in manual page, ifconfig or in something else >>>> ... >>>> >>> Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >>> Just do not try to unset it with "ifconfig wlan0 ap -". That is an >>> alias for "panic now" :-) >>> >> Well, on my system it doesnt panic here. >> So more info to debug "your" panic is required ... >> > > I'll have to see if I can reproduce it. > > >>> So it looks like ifconfig is getting confused with the many different >>> uses of the keyword bssid. >>> >>> I must say I still do not understand what the other use for bssid is. >>> Close to the end of ifconfig/ifieee80211.c there are these: >>> >>> DEF_CMD_ARG("bssid", set80211bssid), >>> DEF_CMD_ARG("ap", set80211bssid), >>> ... >>> DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), >>> DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), >>> >>> So my guess is that I was hitting the clone version when in fact I >>> needed the other version. Luckily ap does not have a clone version. >>> So when should the clone version be used? And how does ifconfig >>> decide which one to use? >>> > > I looked into the ifconfig code a bit more. I think that with the > current code in the ifconfig() and cmd_lookup() functions, it is > imposssible to have two different keywords that share the same > keyword. cmd_lookup() will always search until it finds the first > instance in the list and return that. The first instance in this > case being the last one added. > Correct. > So either the code must change or one of the bssid keywords have > to change. My suggestion would be to keep the bssid for which ap > is an alias and change the other one. Anybody have a suggestion > of what to change it to? > > I prefer to change the code to handle this ambiguity within ifieee80211.c. You cannot use both together or at least they are redundant. I'll look at it when I've got time; but don't let me distract you. Sam From sam at freebsd.org Fri Sep 26 17:55:10 2008 From: sam at freebsd.org (Sam Leffler) Date: Fri Sep 26 17:55:16 2008 Subject: setting bssid in adhoc mode In-Reply-To: <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> Message-ID: <48DD21FB.6060300@freebsd.org> Paul B. Mahol wrote: > On 9/26/08, John Hay wrote: > >> On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: >> >>> On 9/25/08, John Hay wrote: >>> >>>> On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >>>> >>>>> On 9/22/08, John Hay wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> I'm trying out the new ath/wlan stuff in current. Should one still be >>>>>> able to set the bssid in adhoc mode? We normally lock the bssid in >>>>>> an adhoc network because of problems that the network split and does >>>>>> not merge, if you do not do it. >>>>>> >>>>>> What I have done is this: >>>>>> >>>>>> # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >>>>>> # ifconfig wlan0 ssid ptamesh up >>>>>> >>>>>> Up to here works well. It will scan and if it finds another node with >>>>>> the >>>>>> same ssid, it will "lock" on that channel and use the correct bssid. >>>>>> >>>>>> If it does not find another node with the same ssid, it will start it >>>>>> own thing on channel 10. But it looks like one cannot set the bssid. >>>>>> >>>>>> # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >>>>>> ifconfig: 02:07:ca:fe:ba:be: bad value >>>>>> >>>>> I had similar experience with STA mode, instead I use ap (ap is alias >>>>> for bssid, at least it works in STA mode) >>>>> I never bothered is this bug in manual page, ifconfig or in something >>>>> else >>>>> ... >>>>> >>>> Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >>>> Just do not try to unset it with "ifconfig wlan0 ap -". That is an >>>> alias for "panic now" :-) >>>> >>> Well, on my system it doesnt panic here. >>> So more info to debug "your" panic is required ... >>> >> I'll have to see if I can reproduce it. >> > > I managed to reproduce panic on recent CURRENT, with two cards in adhoc mode. > rum0 (usb2) & ndis0 (personal hacked version without usb code) > > I typed "ifconfig wlan0 ap -" several times. > > > bt: > > db:0:kdb.enter.unknown> run lockinfo > db:1:lockinfo> show locks > db:1:locks> show alllocks > Process 1471 (ifconfig) thread 0xc4028690 (100048) > Process 477 (syslogd) thread 0xc402b8c0 (100058) > db:1:alllocks> show lockedvnods > Locked vnodes > db:0:kdb.enter.unknown> show pcpu > cpuid = 1 > curthread = 0xc4028690: pid 1471 "ifconfig" > curpcb = 0xe64e1d90 > fpcurthread = none > idlethread = 0xc3cb1d20: pid 10 "idle: cpu1" > APIC ID = 1 > currentldt = 0x50 > spin locks held: > db:0:kdb.enter.unknown> bt > Tracing pid 1471 tid 100048 td 0xc4028690 > ieee80211_ht_adjust_channel(c46a8000,0,2,2,80000002,...) at > ieee80211_ht_adjust_channel+0x30 > adhoc_pick_bss(c4053000,c4113800,c0a1ebc3,23a,c3dd0108,...) at > adhoc_pick_bss+0x100 > ieee80211_check_scan(c4113800,2,7fffffff,0,0,...) at ieee80211_check_scan+0x20d > ieee80211_check_scan_current(c4113800,4,c0a1fb47,6c,c4113800,...) at > ieee80211_check_scan_current+0x45 > adhoc_newstate(c4113800,1,0,648,e64e1aa0,...) at adhoc_newstate+0x219 > ieee80211_new_state_locked(c4113800,0,c0a1e64c,49c,0,...) at > ieee80211_new_state_locked+0xc4 > ieee80211_init(c4113800,c0a24a64,6,c41adc00,1b9,...) at ieee80211_init+0x45 > ieee80211_ioctl_set80211(c3e1ec00,801c69ea,c48c4240,c0709084,c4028690,...) > at ieee80211_ioctl_set80211+0xe5 > in_control(c4158188,801c69ea,c48c4240,c3e1ec00,c4028690,...) at in_control+0xdc4 > ifioctl(c4158188,801c69ea,c48c4240,c4028690,801c69ea,...) at ifioctl+0x34a > soo_ioctl(c43c9d90,801c69ea,c48c4240,c41adc00,c4028690,...) at soo_ioctl+0x397 > kern_ioctl(c4028690,3,801c69ea,c48c4240,504110,...) at kern_ioctl+0x1dd > ioctl(c4028690,e64e1cf8,c,c06d3f58,c0702bf0,...) at ioctl+0x134 > syscall(e64e1d38) at syscall+0x283 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281a9a43, esp = > 0xbfbfe48c, ebp = 0xbfbfe4d8 --- > > here is panic message: > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0a0c5b0 > stack pointer = 0x28:0xe64e1980 > frame pointer = 0x28:0xe64e1990 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1471 (ifconfig) > exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 > (0xc46a8014) locked @ > /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 > exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 > (0xc46a8014) locked @ > /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 > exclusive lockmgr bufwait (bufwait) r = 0 (0xd7d083c0) locked @ > /usr/src/sys/kern/vfs_bio.c:2443 > exclusive lockmgr ufs (ufs) r = 0 (0xc41a2058) locked @ > /usr/src/sys/kern/vfs_vnops.c:593 > > 0xc41a2000: tag ufs, type VREG > usecount 1, writecount 1, refcount 4 mountedhere 0 > flags () > v_object 0xc413aaa8 ref 0 pages 7 > lock type ufs: EXCL by thread 0xc402b8c0 (pid 477) > > ino 164881, on dev ad4s1d > Looks like adhoc_pick_channel returned NULL which was unexpected. Don't have a quick fix but it's possible no channel may be selected so the code is wrong. I rarely touch adhoc mode so this stuff is lightly tested. Sam From onemda at gmail.com Fri Sep 26 22:17:01 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Fri Sep 26 22:17:07 2008 Subject: setting bssid in adhoc mode In-Reply-To: <48DD21FB.6060300@freebsd.org> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> <48DD21FB.6060300@freebsd.org> Message-ID: <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> On 9/26/08, Sam Leffler wrote: > Paul B. Mahol wrote: >> On 9/26/08, John Hay wrote: >> >>> On Thu, Sep 25, 2008 at 08:59:37PM +0200, Paul B. Mahol wrote: >>> >>>> On 9/25/08, John Hay wrote: >>>> >>>>> On Thu, Sep 25, 2008 at 04:41:30PM +0200, Paul B. Mahol wrote: >>>>> >>>>>> On 9/22/08, John Hay wrote: >>>>>> >>>>>>> Hi >>>>>>> >>>>>>> I'm trying out the new ath/wlan stuff in current. Should one still be >>>>>>> able to set the bssid in adhoc mode? We normally lock the bssid in >>>>>>> an adhoc network because of problems that the network split and does >>>>>>> not merge, if you do not do it. >>>>>>> >>>>>>> What I have done is this: >>>>>>> >>>>>>> # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >>>>>>> # ifconfig wlan0 ssid ptamesh up >>>>>>> >>>>>>> Up to here works well. It will scan and if it finds another node with >>>>>>> the >>>>>>> same ssid, it will "lock" on that channel and use the correct bssid. >>>>>>> >>>>>>> If it does not find another node with the same ssid, it will start it >>>>>>> own thing on channel 10. But it looks like one cannot set the bssid. >>>>>>> >>>>>>> # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >>>>>>> ifconfig: 02:07:ca:fe:ba:be: bad value >>>>>>> >>>>>> I had similar experience with STA mode, instead I use ap (ap is alias >>>>>> for bssid, at least it works in STA mode) >>>>>> I never bothered is this bug in manual page, ifconfig or in something >>>>>> else >>>>>> ... >>>>>> >>>>> Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >>>>> Just do not try to unset it with "ifconfig wlan0 ap -". That is an >>>>> alias for "panic now" :-) >>>>> >>>> Well, on my system it doesnt panic here. >>>> So more info to debug "your" panic is required ... >>>> >>> I'll have to see if I can reproduce it. >>> >> >> I managed to reproduce panic on recent CURRENT, with two cards in adhoc >> mode. >> rum0 (usb2) & ndis0 (personal hacked version without usb code) >> >> I typed "ifconfig wlan0 ap -" several times. >> >> >> bt: >> >> db:0:kdb.enter.unknown> run lockinfo >> db:1:lockinfo> show locks >> db:1:locks> show alllocks >> Process 1471 (ifconfig) thread 0xc4028690 (100048) >> Process 477 (syslogd) thread 0xc402b8c0 (100058) >> db:1:alllocks> show lockedvnods >> Locked vnodes >> db:0:kdb.enter.unknown> show pcpu >> cpuid = 1 >> curthread = 0xc4028690: pid 1471 "ifconfig" >> curpcb = 0xe64e1d90 >> fpcurthread = none >> idlethread = 0xc3cb1d20: pid 10 "idle: cpu1" >> APIC ID = 1 >> currentldt = 0x50 >> spin locks held: >> db:0:kdb.enter.unknown> bt >> Tracing pid 1471 tid 100048 td 0xc4028690 >> ieee80211_ht_adjust_channel(c46a8000,0,2,2,80000002,...) at >> ieee80211_ht_adjust_channel+0x30 >> adhoc_pick_bss(c4053000,c4113800,c0a1ebc3,23a,c3dd0108,...) at >> adhoc_pick_bss+0x100 >> ieee80211_check_scan(c4113800,2,7fffffff,0,0,...) at >> ieee80211_check_scan+0x20d >> ieee80211_check_scan_current(c4113800,4,c0a1fb47,6c,c4113800,...) at >> ieee80211_check_scan_current+0x45 >> adhoc_newstate(c4113800,1,0,648,e64e1aa0,...) at adhoc_newstate+0x219 >> ieee80211_new_state_locked(c4113800,0,c0a1e64c,49c,0,...) at >> ieee80211_new_state_locked+0xc4 >> ieee80211_init(c4113800,c0a24a64,6,c41adc00,1b9,...) at >> ieee80211_init+0x45 >> ieee80211_ioctl_set80211(c3e1ec00,801c69ea,c48c4240,c0709084,c4028690,...) >> at ieee80211_ioctl_set80211+0xe5 >> in_control(c4158188,801c69ea,c48c4240,c3e1ec00,c4028690,...) at >> in_control+0xdc4 >> ifioctl(c4158188,801c69ea,c48c4240,c4028690,801c69ea,...) at ifioctl+0x34a >> soo_ioctl(c43c9d90,801c69ea,c48c4240,c41adc00,c4028690,...) at >> soo_ioctl+0x397 >> kern_ioctl(c4028690,3,801c69ea,c48c4240,504110,...) at kern_ioctl+0x1dd >> ioctl(c4028690,e64e1cf8,c,c06d3f58,c0702bf0,...) at ioctl+0x134 >> syscall(e64e1d38) at syscall+0x283 >> Xint0x80_syscall() at Xint0x80_syscall+0x20 >> --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281a9a43, esp = >> 0xbfbfe48c, ebp = 0xbfbfe4d8 --- >> >> here is panic message: >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0x0 >> fault code = supervisor read, page not present >> instruction pointer = 0x20:0xc0a0c5b0 >> stack pointer = 0x28:0xe64e1980 >> frame pointer = 0x28:0xe64e1990 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 1471 (ifconfig) >> exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 >> (0xc46a8014) locked @ >> /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 >> exclusive sleep mutex ndis0_com_lock (ndis0_com_lock) r = 1 >> (0xc46a8014) locked @ >> /usr/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:570 >> exclusive lockmgr bufwait (bufwait) r = 0 (0xd7d083c0) locked @ >> /usr/src/sys/kern/vfs_bio.c:2443 >> exclusive lockmgr ufs (ufs) r = 0 (0xc41a2058) locked @ >> /usr/src/sys/kern/vfs_vnops.c:593 >> >> 0xc41a2000: tag ufs, type VREG >> usecount 1, writecount 1, refcount 4 mountedhere 0 >> flags () >> v_object 0xc413aaa8 ref 0 pages 7 >> lock type ufs: EXCL by thread 0xc402b8c0 (pid 477) >> >> ino 164881, on dev ad4s1d >> > Looks like adhoc_pick_channel returned NULL which was unexpected. Don't > have a quick fix but it's possible no channel may be selected so the > code is wrong. I rarely touch adhoc mode so this stuff is lightly tested. On further investigation it appears to be locking problem - I was not able to reproduce panic with kern.smp.disabled=1 From jhay at meraka.org.za Sat Sep 27 07:10:49 2008 From: jhay at meraka.org.za (John Hay) Date: Sat Sep 27 07:10:55 2008 Subject: setting bssid in adhoc mode In-Reply-To: <48DD210E.6050300@freebsd.org> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <48DD210E.6050300@freebsd.org> Message-ID: <20080927071046.GA94774@zibbi.meraka.csir.co.za> > >>>>> > >>>>>I'm trying out the new ath/wlan stuff in current. Should one still be > >>>>>able to set the bssid in adhoc mode? We normally lock the bssid in > >>>>>an adhoc network because of problems that the network split and does > >>>>>not merge, if you do not do it. > >>>>> > >>>>>What I have done is this: > >>>>> > >>>>># ifconfig wlan0 create wlandev ath0 wlanmode adhoc > >>>>># ifconfig wlan0 ssid ptamesh up > >>>>> > >>>>>Up to here works well. It will scan and if it finds another node with > >>>>>the > >>>>>same ssid, it will "lock" on that channel and use the correct bssid. > >>>>> > >>>>>If it does not find another node with the same ssid, it will start it > >>>>>own thing on channel 10. But it looks like one cannot set the bssid. > >>>>> > >>>>># ifconfig wlan0 bssid 02:07:ca:fe:ba:be > >>>>>ifconfig: 02:07:ca:fe:ba:be: bad value > >>>>> > >>>>I had similar experience with STA mode, instead I use ap (ap is alias > >>>>for bssid, at least it works in STA mode) > >>>>I never bothered is this bug in manual page, ifconfig or in something > >>>>else > >>>>... > >>>> > >>>Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. > >>>Just do not try to unset it with "ifconfig wlan0 ap -". That is an > >>>alias for "panic now" :-) > >>> > >>Well, on my system it doesnt panic here. > >>So more info to debug "your" panic is required ... > >> > > > >I'll have to see if I can reproduce it. > > > > > >>>So it looks like ifconfig is getting confused with the many different > >>>uses of the keyword bssid. > >>> > >>>I must say I still do not understand what the other use for bssid is. > >>>Close to the end of ifconfig/ifieee80211.c there are these: > >>> > >>>DEF_CMD_ARG("bssid", set80211bssid), > >>>DEF_CMD_ARG("ap", set80211bssid), > >>>... > >>>DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), > >>>DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), > >>> > >>>So my guess is that I was hitting the clone version when in fact I > >>>needed the other version. Luckily ap does not have a clone version. > >>>So when should the clone version be used? And how does ifconfig > >>>decide which one to use? > >>> > > > >I looked into the ifconfig code a bit more. I think that with the > >current code in the ifconfig() and cmd_lookup() functions, it is > >imposssible to have two different keywords that share the same > >keyword. cmd_lookup() will always search until it finds the first > >instance in the list and return that. The first instance in this > >case being the last one added. > > > > Correct. > > >So either the code must change or one of the bssid keywords have > >to change. My suggestion would be to keep the bssid for which ap > >is an alias and change the other one. Anybody have a suggestion > >of what to change it to? > > > > > I prefer to change the code to handle this ambiguity within > ifieee80211.c. You cannot use both together or at least they are > redundant. I'll look at it when I've got time; but don't let me > distract you. So what should the behaviour be? How should ifconfig know which bssid function to use? Should the clone variant be used when it is used on the same line as create? And the other if there is not a create on the line? Or some other way? And should the other DEF_CLONE... keywords also be handled the same way? John -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org From onemda at gmail.com Sat Sep 27 13:02:07 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Sat Sep 27 13:02:14 2008 Subject: setting bssid in adhoc mode In-Reply-To: <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> <48DD21FB.6060300@freebsd.org> <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> Message-ID: <3a142e750809270602k10afc4f9l660feaa3c142cbf1@mail.gmail.com> On 9/27/08, Paul B. Mahol wrote: > On further investigation it appears to be locking problem - I was not > able to reproduce panic with kern.smp.disabled=1 Wrong, kernel still panic in same place when putting wlan0 several time up and down. (without adding "ap -" at all) So adhoc is broken in CURRENT. From sam at freebsd.org Sat Sep 27 19:16:04 2008 From: sam at freebsd.org (Sam Leffler) Date: Sat Sep 27 19:16:15 2008 Subject: setting bssid in adhoc mode In-Reply-To: <20080927071046.GA94774@zibbi.meraka.csir.co.za> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <48DD210E.6050300@freebsd.org> <20080927071046.GA94774@zibbi.meraka.csir.co.za> Message-ID: <48DE8670.60606@freebsd.org> John Hay wrote: >>>>>>> I'm trying out the new ath/wlan stuff in current. Should one still be >>>>>>> able to set the bssid in adhoc mode? We normally lock the bssid in >>>>>>> an adhoc network because of problems that the network split and does >>>>>>> not merge, if you do not do it. >>>>>>> >>>>>>> What I have done is this: >>>>>>> >>>>>>> # ifconfig wlan0 create wlandev ath0 wlanmode adhoc >>>>>>> # ifconfig wlan0 ssid ptamesh up >>>>>>> >>>>>>> Up to here works well. It will scan and if it finds another node with >>>>>>> the >>>>>>> same ssid, it will "lock" on that channel and use the correct bssid. >>>>>>> >>>>>>> If it does not find another node with the same ssid, it will start it >>>>>>> own thing on channel 10. But it looks like one cannot set the bssid. >>>>>>> >>>>>>> # ifconfig wlan0 bssid 02:07:ca:fe:ba:be >>>>>>> ifconfig: 02:07:ca:fe:ba:be: bad value >>>>>>> >>>>>>> >>>>>> I had similar experience with STA mode, instead I use ap (ap is alias >>>>>> for bssid, at least it works in STA mode) >>>>>> I never bothered is this bug in manual page, ifconfig or in something >>>>>> else >>>>>> ... >>>>>> >>>>>> >>>>> Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. >>>>> Just do not try to unset it with "ifconfig wlan0 ap -". That is an >>>>> alias for "panic now" :-) >>>>> >>>>> >>>> Well, on my system it doesnt panic here. >>>> So more info to debug "your" panic is required ... >>>> >>>> >>> I'll have to see if I can reproduce it. >>> >>> >>> >>>>> So it looks like ifconfig is getting confused with the many different >>>>> uses of the keyword bssid. >>>>> >>>>> I must say I still do not understand what the other use for bssid is. >>>>> Close to the end of ifconfig/ifieee80211.c there are these: >>>>> >>>>> DEF_CMD_ARG("bssid", set80211bssid), >>>>> DEF_CMD_ARG("ap", set80211bssid), >>>>> ... >>>>> DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), >>>>> DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), >>>>> >>>>> So my guess is that I was hitting the clone version when in fact I >>>>> needed the other version. Luckily ap does not have a clone version. >>>>> So when should the clone version be used? And how does ifconfig >>>>> decide which one to use? >>>>> >>>>> >>> I looked into the ifconfig code a bit more. I think that with the >>> current code in the ifconfig() and cmd_lookup() functions, it is >>> imposssible to have two different keywords that share the same >>> keyword. cmd_lookup() will always search until it finds the first >>> instance in the list and return that. The first instance in this >>> case being the last one added. >>> >>> >> Correct. >> >> >>> So either the code must change or one of the bssid keywords have >>> to change. My suggestion would be to keep the bssid for which ap >>> is an alias and change the other one. Anybody have a suggestion >>> of what to change it to? >>> >>> >>> >> I prefer to change the code to handle this ambiguity within >> ifieee80211.c. You cannot use both together or at least they are >> redundant. I'll look at it when I've got time; but don't let me >> distract you. >> > > So what should the behaviour be? How should ifconfig know which bssid > function to use? Should the clone variant be used when it is used on > the same line as create? And the other if there is not a create on the > line? Or some other way? And should the other DEF_CLONE... keywords > also be handled the same way? > > John > Try the attached change. It looked easier to fix this for all possible usage instead of complicating the 802.11 stuff. The change forces all keywords marked "DEF_CLONE" to come first on the command line followed by keywords that are marked !DEF_CLONE. At some point it's likely we'll need to stick a real parser in ifconfig but I think this change is small enough to just do it this way (it also slightly cleans up the hack for pushing the clone operation out before parsing/handling subsequent cmd line args). Sam -------------- next part -------------- Index: ifconfig.c =================================================================== --- ifconfig.c (revision 183416) +++ ifconfig.c (working copy) @@ -392,14 +392,21 @@ } static const struct cmd * -cmd_lookup(const char *name) +cmd_lookup(const char *name, int iscreate) { #define N(a) (sizeof(a)/sizeof(a[0])) const struct cmd *p; for (p = cmds; p != NULL; p = p->c_next) - if (strcmp(name, p->c_name) == 0) - return p; + if (strcmp(name, p->c_name) == 0) { + if (iscreate) { + if (p->c_iscloneop) + return p; + } else { + if (!p->c_iscloneop) + return p; + } + } return NULL; #undef N } @@ -437,6 +444,7 @@ ifconfig(int argc, char *const *argv, int iscreate, const struct afswtch *afp) { const struct afswtch *nafp; + const struct cmd *p; struct callback *cb; int s; @@ -452,9 +460,38 @@ err(1, "socket(family %u,SOCK_DGRAM", ifr.ifr_addr.sa_family); while (argc > 0) { - const struct cmd *p; - - p = cmd_lookup(*argv); + p = cmd_lookup(*argv, iscreate); + if (iscreate && p == NULL) { + /* + * Push the clone create callback so the new + * device is created and can be used for any + * remaining arguments. + */ + cb = callbacks; + if (cb == NULL) + errx(1, "internal error, no callback"); + callbacks = cb->cb_next; + cb->cb_func(s, cb->cb_arg); + iscreate = 0; + /* + * Handle any address family spec that + * immediately follows and potentially + * recreate the socket. + */ + nafp = af_getbyname(*argv); + if (nafp != NULL) { + argc--, argv++; + if (nafp != afp) { + close(s); + afp = nafp; + goto top; + } + } + /* + * Look for a normal parameter. + */ + continue; + } if (p == NULL) { /* * Not a recognized command, choose between setting @@ -463,33 +500,6 @@ p = (setaddr ? &setifdstaddr_cmd : &setifaddr_cmd); } if (p->c_u.c_func || p->c_u.c_func2) { - if (iscreate && !p->c_iscloneop) { - /* - * Push the clone create callback so the new - * device is created and can be used for any - * remaining arguments. - */ - cb = callbacks; - if (cb == NULL) - errx(1, "internal error, no callback"); - callbacks = cb->cb_next; - cb->cb_func(s, cb->cb_arg); - iscreate = 0; - /* - * Handle any address family spec that - * immediately follows and potentially - * recreate the socket. - */ - nafp = af_getbyname(*argv); - if (nafp != NULL) { - argc--, argv++; - if (nafp != afp) { - close(s); - afp = nafp; - goto top; - } - } - } if (p->c_parameter == NEXTARG) { if (argv[1] == NULL) errx(1, "'%s' requires argument", From sam at freebsd.org Sat Sep 27 19:16:37 2008 From: sam at freebsd.org (Sam Leffler) Date: Sat Sep 27 19:16:43 2008 Subject: setting bssid in adhoc mode In-Reply-To: <3a142e750809270602k10afc4f9l660feaa3c142cbf1@mail.gmail.com> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> <48DD21FB.6060300@freebsd.org> <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> <3a142e750809270602k10afc4f9l660feaa3c142cbf1@mail.gmail.com> Message-ID: <48DE8693.3000107@freebsd.org> Paul B. Mahol wrote: > On 9/27/08, Paul B. Mahol wrote: > >> On further investigation it appears to be locking problem - I was not >> able to reproduce panic with kern.smp.disabled=1 >> > > Wrong, kernel still panic in same place when putting wlan0 several > time up and down. > (without adding "ap -" at all) > > So adhoc is broken in CURRENT. > _______________________________________________ > Well if you're telling me I'm wrong then I'll happily leave the issue to you. Sam From onemda at gmail.com Sat Sep 27 20:14:15 2008 From: onemda at gmail.com (Paul B. Mahol) Date: Sat Sep 27 20:14:22 2008 Subject: setting bssid in adhoc mode In-Reply-To: <48DE8693.3000107@freebsd.org> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <3a142e750809261012r73e33b43w5996fa2f61dabd82@mail.gmail.com> <48DD21FB.6060300@freebsd.org> <3a142e750809261517r13d317e4ie533741ba74bc4d8@mail.gmail.com> <3a142e750809270602k10afc4f9l660feaa3c142cbf1@mail.gmail.com> <48DE8693.3000107@freebsd.org> Message-ID: <3a142e750809271314k6e9a75euc8952bda6fc5e61d@mail.gmail.com> On 9/27/08, Sam Leffler wrote: > Paul B. Mahol wrote: >> On 9/27/08, Paul B. Mahol wrote: >> >>> On further investigation it appears to be locking problem - I was not >>> able to reproduce panic with kern.smp.disabled=1 >>> >> >> Wrong, kernel still panic in same place when putting wlan0 several >> time up and down. >> (without adding "ap -" at all) >> >> So adhoc is broken in CURRENT. >> _______________________________________________ >> > Well if you're telling me I'm wrong then I'll happily leave the issue to > you. No, you are correct. channel list seems to be populated with nulls, because there are free channels but null is still picked. From mav at FreeBSD.org Sat Sep 27 21:43:09 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Sat Sep 27 21:43:20 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements Message-ID: <48DEA8E7.2080503@FreeBSD.org> Hi. I would like to present initial revision of my generic PCI SD Host Controller driver (sdhci). It support PCI devices with class 8 and subclass 5 according to SD Host Controller Specification. With some limitations it successfully works on my Acer TM6292 notebook with ENE CB714 card reader. Things that are working now: - PIO mode single and multiple block read and write, - 1 and 4 bits bus width support. In PIO mode with 4GB SD card on 30MHz 4bit bus I have reached about 3.5MB/s (limited by CPU) linear read and 7MB/s (limited by card) linear write. Small blocks read/write performance limited by card. Things that are not working yet: - DMA modes (code is written, but as my controller looks like has broken DMA I have no ability to debug it), - card insert/remove detection (need more thinking), you should reload mmc module to rescan cards, - SDHC and MMC cards (have no such cards now to debug that code), only standard capacity SD Memory cards up to 4GB size are supported now, - high speed (double rate) bus mode (need more thinking and DMA support). Also to get such results I have improved existing mmc and mmcsd drivers a bit. mmc driver got: - 4 bit bus width support, - write protection switch support, - cards with more then 2GB capacity support. mmcsd driver got: - multiple block read and write support, - cards with more then 2GB capacity support, - I/O error reporting, - write protection switch support. Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found at: http://people.freebsd.org/~mav/sdhci/ I will be grateful for any feedbacks, comments and support. -- Alexander Motin From gonzo at bluezbox.com Sat Sep 27 21:52:34 2008 From: gonzo at bluezbox.com (Oleksandr Tymoshenko) Date: Sat Sep 27 21:52:46 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <48DEA8E7.2080503@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> Message-ID: <48DEA4EC.3030300@bluezbox.com> Alexander Motin wrote: > Hi. > > Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found > at: > http://people.freebsd.org/~mav/sdhci/ Thanks! That's just what I was looking for about three weeks ago :) > > I will be grateful for any feedbacks, comments and support. 7.1 requires s/kproc/kthread/ but otherwise works fine: sdhci0: mem 0xff9fb800-0xff9fb8ff irq 9 at device 1.2 on pci2 sdhci0: 1 slot(s) allocated sdhci0: [ITHREAD] mmc0: on sdhci0 mmc0: SD card: 507379712 bytes mmcsd0: 483MB (read-only) at mmc0 mmc0: setting transfer rate to 30.000MHz mmc0: setting bus width to 4 bits GEOM_LABEL: Label for provider mmcsd0s1 is msdosfs/SD. From rpaulo at fnop.net Sat Sep 27 22:59:13 2008 From: rpaulo at fnop.net (Rui Paulo) Date: Sat Sep 27 22:59:19 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <48DEA8E7.2080503@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> Message-ID: <9D33158B-B28D-4D22-B3BF-A7CE376FCAD1@freebd.org> On 27 Sep 2008, at 22:43, Alexander Motin wrote: > Hi. > > I would like to present initial revision of my generic PCI SD Host > Controller driver (sdhci). It support PCI devices with class 8 and > subclass 5 according to SD Host Controller Specification. With some > limitations it successfully works on my Acer TM6292 notebook with > ENE CB714 card reader. > > Things that are working now: > - PIO mode single and multiple block read and write, > - 1 and 4 bits bus width support. > > In PIO mode with 4GB SD card on 30MHz 4bit bus I have reached about > 3.5MB/s (limited by CPU) linear read and 7MB/s (limited by card) > linear write. Small blocks read/write performance limited by card. > > Things that are not working yet: > - DMA modes (code is written, but as my controller looks like has > broken DMA I have no ability to debug it), > - card insert/remove detection (need more thinking), you should > reload mmc module to rescan cards, > - SDHC and MMC cards (have no such cards now to debug that code), > only standard capacity SD Memory cards up to 4GB size are supported > now, > - high speed (double rate) bus mode (need more thinking and DMA > support). > > Also to get such results I have improved existing mmc and mmcsd > drivers a bit. mmc driver got: > - 4 bit bus width support, > - write protection switch support, > - cards with more then 2GB capacity support. > mmcsd driver got: > - multiple block read and write support, > - cards with more then 2GB capacity support, > - I/O error reporting, > - write protection switch support. > > Latest patches against 8-CURRENT (should also fit 7-STABLE) may be > found at: > http://people.freebsd.org/~mav/sdhci/ > > I will be grateful for any feedbacks, comments and support. Well, here's my support: Great work! :-) -- Rui Paulo From frank at exit.com Sun Sep 28 00:06:48 2008 From: frank at exit.com (Frank Mayhar) Date: Sun Sep 28 00:06:54 2008 Subject: Atheros wireless problems. In-Reply-To: <48DBB3EF.3060909@freebsd.org> References: <1222317948.1740.10.camel@jill.exit.com> <48DBB3EF.3060909@freebsd.org> Message-ID: <1222560406.89800.10.camel@jill.exit.com> On Thu, 2008-09-25 at 08:53 -0700, Sam Leffler wrote: > Frank Mayhar wrote: > > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > > believe) Atheros chipset in it; it's an a/b/g card. This is to use > > while the chipset embedded in my laptop isn't supported. It came today, > > I installed it tonight and, well, problems. > The status codes look bogus. In 0.10.5.10 there is a code path through > reset where status is not set if the chip is not brought out of low > power mode. Why this might happen is beyond me (could be a cardbus > problem) but if you initialize status to a known value before the hal > calls that are failing this might confirm that as the problem. I've > fixed the hal fwiw. That's definitely not the problem, it seems. I modified the driver to zero 'status' in each of the routines that emit the message. When I ran it today, it emitted the 'device timeout' and 'unable to reset hardware' messages: Sep 27 14:33:59 auton kernel: ath0: device timeout Sep 27 14:33:59 auton kernel: ath0: ath_reset: unable to reset hardware; hal status 19600117 Sep 27 14:34:21 auton kernel: ath0: device timeout Sep 27 14:34:21 auton kernel: ath0: ath_reset: unable to reset hardware; hal status 19600117 The only difference was that this time the status was always 19600117. A verbose boot, btw, gets this: Sep 27 14:38:43 auton kernel: ath0: mem 0xf2110000-0xf211ffff irq 17 at device 0.0 on cardbus0 Sep 27 14:38:43 auton kernel: ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf2110000 Sep 27 14:38:43 auton kernel: cbb0: Opening memory: Sep 27 14:38:43 auton kernel: cbb0: Normal: 0xf2110000-0xf211ffff Sep 27 14:38:43 auton kernel: ath0: [MPSAFE] Sep 27 14:38:43 auton kernel: ath0: [ITHREAD] Sep 27 14:38:43 auton kernel: ath0: hal channel 2412/a0 -> 1 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2412/c0 -> 1 maxpow 36 minpow -2 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2417/a0 -> 2 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2417/c0 -> 2 maxpow 36 minpow -2 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2422/a0 -> 3 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2422/c0 -> 3 maxpow 36 minpow -2 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2427/a0 -> 4 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2427/c0 -> 4 maxpow 36 minpow -2 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2432/a0 -> 5 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2432/c0 -> 5 maxpow 36 minpow -2 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2437/a0 -> 6 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2437/c0 -> 6 maxpow 36 minpow -2 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2437/d0 -> 6 maxpow 32 minpow -2 maxreg 20 Sep 27 14:38:43 auton kernel: ath0: hal channel 2442/a0 -> 7 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2442/c0 -> 7 maxpow 36 minpow -1 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2447/a0 -> 8 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2447/c0 -> 8 maxpow 36 minpow -1 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2452/a0 -> 9 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2452/c0 -> 9 maxpow 36 minpow -1 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2457/a0 -> 10 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2457/c0 -> 10 maxpow 36 minpow -1 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2462/a0 -> 11 maxpow 36 minpow -3 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 2462/c0 -> 11 maxpow 36 minpow -1 maxreg 27 Sep 27 14:38:43 auton kernel: ath0: hal channel 5180/140 -> 36 maxpow 34 minpow -8 maxreg 17 Sep 27 14:38:43 auton kernel: ath0: hal channel 5200/140 -> 40 maxpow 34 minpow -8 maxreg 17 Sep 27 14:38:43 auton kernel: ath0: hal channel 5200/150 -> 40 maxpow 32 minpow -8 maxreg 17 Sep 27 14:38:43 auton kernel: ath0: hal channel 5210/2150 -> 42 maxpow 32 minpow -7 maxreg 17 Sep 27 14:38:43 auton kernel: ath0: hal channel 5220/140 -> 44 maxpow 34 minpow -7 maxreg 17 Sep 27 14:38:43 auton kernel: ath0: hal channel 5240/140 -> 48 maxpow 34 minpow -7 maxreg 17 Sep 27 14:38:43 auton kernel: ath0: hal channel 5240/150 -> 48 maxpow 32 minpow -7 maxreg 17 Sep 27 14:38:43 auton kernel: ath0: hal channel 5250/2150 -> 50 maxpow 32 minpow -7 maxreg 23 Sep 27 14:38:43 auton kernel: ath0: hal channel 5260/140 -> 52 maxpow 34 minpow -7 maxreg 23 Sep 27 14:38:43 auton kernel: ath0: hal channel 5280/140 -> 56 maxpow 34 minpow -6 maxreg 23 Sep 27 14:38:43 auton kernel: ath0: hal channel 5280/150 -> 56 maxpow 32 minpow -6 maxreg 23 Sep 27 14:38:43 auton kernel: ath0: hal channel 5290/2150 -> 58 maxpow 32 minpow -6 maxreg 23 Sep 27 14:38:43 auton kernel: ath0: hal channel 5300/140 -> 60 maxpow 34 minpow -6 maxreg 23 Sep 27 14:38:43 auton kernel: ath0: hal channel 5320/140 -> 64 maxpow 34 minpow -5 maxreg 23 Sep 27 14:38:43 auton kernel: ath0: hal channel 5745/140 -> 149 maxpow 34 minpow 10 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: hal channel 5760/2150 -> 152 maxpow 32 minpow 10 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: hal channel 5765/140 -> 153 maxpow 34 minpow 11 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: hal channel 5765/150 -> 153 maxpow 32 minpow 11 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: hal channel 5785/140 -> 157 maxpow 34 minpow 11 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: hal channel 5800/2150 -> 160 maxpow 32 minpow 12 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: hal channel 5805/140 -> 161 maxpow 34 minpow 12 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: hal channel 5805/150 -> 161 maxpow 32 minpow 12 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: hal channel 5825/140 -> 165 maxpow 34 minpow 13 maxreg 30 Sep 27 14:38:43 auton kernel: ath0: WARNING: using obsoleted if_watchdog interface Sep 27 14:38:43 auton kernel: ath0: bpf attached Sep 27 14:38:43 auton kernel: ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps36Mbps 48Mbps 54Mbps Sep 27 14:38:43 auton kernel: ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Sep 27 14:38:43 auton kernel: ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Sep 27 14:38:43 auton kernel: ath0: turboA rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Sep 27 14:38:43 auton kernel: ath0: sturboA rates: Sep 27 14:38:43 auton kernel: ath0: mac 5.9 phy 4.3 radio 3.6 Sep 27 14:38:43 auton kernel: ath0: Use hw queue 1 for WME_AC_BE traffic Sep 27 14:38:43 auton kernel: ath0: Use hw queue 0 for WME_AC_BK traffic Sep 27 14:38:43 auton kernel: ath0: Use hw queue 2 for WME_AC_VI traffic Sep 27 14:38:43 auton kernel: ath0: Use hw queue 3 for WME_AC_VO traffic Sep 27 14:38:43 auton kernel: ath0: Use hw queue 8 for CAB traffic Sep 27 14:38:43 auton kernel: ath0: Use hw queue 9 for beacons Sep 27 14:38:52 auton kernel: ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xf2110000 Anything else I might try? -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From unixmania at gmail.com Sun Sep 28 06:01:28 2008 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Sun Sep 28 06:01:35 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <48DEA4EC.3030300@bluezbox.com> References: <48DEA8E7.2080503@FreeBSD.org> <48DEA4EC.3030300@bluezbox.com> Message-ID: On Sat, Sep 27, 2008 at 6:26 PM, Oleksandr Tymoshenko wrote: > Alexander Motin wrote: >> >> Hi. > >> >> Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found >> at: >> http://people.freebsd.org/~mav/sdhci/ > > Thanks! That's just what I was looking for about three weeks ago :) >> >> I will be grateful for any feedbacks, comments and support. > > 7.1 requires s/kproc/kthread/ but otherwise works fine: > > sdhci0: mem 0xff9fb800-0xff9fb8ff irq 9 at device 1.2 on > pci2 > sdhci0: 1 slot(s) allocated > sdhci0: [ITHREAD] > > mmc0: on sdhci0 > mmc0: SD card: 507379712 bytes > mmcsd0: 483MB (read-only) at mmc0 > mmc0: setting transfer rate to 30.000MHz > mmc0: setting bus width to 4 bits > GEOM_LABEL: Label for provider mmcsd0s1 is msdosfs/SD. It did not detect the hardware on my Compaq 6910p: none2@pci0:2:6:3: class=0x080500 card=0x30be103c chip=0x08221180 rev=0x20 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' class = base peripheral none3@pci0:2:6:4: class=0x088000 card=0x30be103c chip=0x08431180 rev=0x10 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh MMC Host Controller' class = base peripheral Suggestions are welcome. :-) -- cd /usr/ports/sysutils/life make clean From unixmania at gmail.com Sun Sep 28 06:12:27 2008 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Sun Sep 28 06:12:34 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: References: <48DEA8E7.2080503@FreeBSD.org> <48DEA4EC.3030300@bluezbox.com> Message-ID: On Sun, Sep 28, 2008 at 2:35 AM, Carlos A. M. dos Santos wrote: > On Sat, Sep 27, 2008 at 6:26 PM, Oleksandr Tymoshenko > wrote: >> Alexander Motin wrote: >>> >>> Hi. >> >>> >>> Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found >>> at: >>> http://people.freebsd.org/~mav/sdhci/ >> >> Thanks! That's just what I was looking for about three weeks ago :) >>> >>> I will be grateful for any feedbacks, comments and support. >> >> 7.1 requires s/kproc/kthread/ but otherwise works fine: >> >> sdhci0: mem 0xff9fb800-0xff9fb8ff irq 9 at device 1.2 on >> pci2 >> sdhci0: 1 slot(s) allocated >> sdhci0: [ITHREAD] >> >> mmc0: on sdhci0 >> mmc0: SD card: 507379712 bytes >> mmcsd0: 483MB (read-only) at mmc0 >> mmc0: setting transfer rate to 30.000MHz >> mmc0: setting bus width to 4 bits >> GEOM_LABEL: Label for provider mmcsd0s1 is msdosfs/SD. > > It did not detect the hardware on my Compaq 6910p: > > none2@pci0:2:6:3: class=0x080500 card=0x30be103c chip=0x08221180 > rev=0x20 hdr=0x00 > vendor = 'Ricoh Company, Ltd.' > device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' > class = base peripheral > none3@pci0:2:6:4: class=0x088000 card=0x30be103c chip=0x08431180 > rev=0x10 hdr=0x00 > vendor = 'Ricoh Company, Ltd.' > device = 'unknown Ricoh MMC Host Controller' > class = base peripheral > > Suggestions are welcome. :-) Here goes a good suggestion: do not forget to load the module, you dumb ass! Now I got this: sdhci0: mem 0xe4103000-0xe41030ff irq 19 at device 6.3 on pci2 sdhci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xe4103000 sdhci0: 1 slot(s) allocated sdhci0: [MPSAFE] sdhci0: [ITHREAD] mmc0: on sdhci0 mmc0: Reset 0x6 never completed - 0x6. mmc0: ============== REGISTER DUMP ============== mmc0: Sys addr: 0x00000000 | Version: 0x00000400 mmc0: Blk size: 0x00000000 | Blk cnt: 0x00000000 mmc0: Argument: 0x00000000 | Trn mode: 0x00000000 mmc0: Present: 0x01f20000 | Host ctl: 0x00000000 mmc0: Power: 0x0000000f | Blk gap: 0x00000000 mmc0: Wake-up: 0x00000000 | Clock: 0x00008007 mmc0: Timeout: 0x00000000 | Int stat: 0x00000000 mmc0: Int enab: 0x00ff00fb | Sig enab: 0x00ff00fb mmc0: AC12 err: 0x00000000 | Slot int: 0x00000000 mmc0: Caps: 0x018021a1 | Max curr: 0x00000040 mmc0: =========================================== mmc0: Reset 0x6 never completed - 0x6. mmc0: ============== REGISTER DUMP ============== mmc0: Sys addr: 0x00000000 | Version: 0x00000400 mmc0: Blk size: 0x00000000 | Blk cnt: 0x00000000 mmc0: Argument: 0x00000000 | Trn mode: 0x00000000 mmc0: Present: 0x01f20000 | Host ctl: 0x00000000 mmc0: Power: 0x0000000f | Blk gap: 0x00000000 mmc0: Wake-up: 0x00000000 | Clock: 0x00008007 mmc0: Timeout: 0x00000000 | Int stat: 0x00000000 mmc0: Int enab: 0x00ff00fb | Sig enab: 0x00ff00fb mmc0: AC12 err: 0x00000000 | Slot int: 0x00000000 mmc0: Caps: 0x018021a1 | Max curr: 0x00000040 mmc0: =========================================== mmc0: setting transfer rate to 33.000MHz mmc0: Reset 0x6 never completed - 0x6. mmc0: ============== REGISTER DUMP ============== mmc0: Sys addr: 0x00000000 | Version: 0x00000400 mmc0: Blk size: 0x00000000 | Blk cnt: 0x00000000 mmc0: Argument: 0x00000000 | Trn mode: 0x00000000 mmc0: Present: 0x01f20000 | Host ctl: 0x00000000 mmc0: Power: 0x0000000f | Blk gap: 0x00000000 mmc0: Wake-up: 0x00000000 | Clock: 0x00000007 mmc0: Timeout: 0x00000000 | Int stat: 0x00000000 mmc0: Int enab: 0x00ff00fb | Sig enab: 0x00ff00fb mmc0: AC12 err: 0x00000000 | Slot int: 0x00000000 mmc0: Caps: 0x018021a1 | Max curr: 0x00000040 mmc0: =========================================== Much better. However, I got a system crash and reboot attempting to unload the module. -- cd /usr/ports/sysutils/life make clean From imp at bsdimp.com Sun Sep 28 09:30:45 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sun Sep 28 09:31:03 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <48DEA8E7.2080503@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> Message-ID: <20080928.032929.-1264103837.imp@bsdimp.com> In message: <48DEA8E7.2080503@FreeBSD.org> Alexander Motin writes: : Hi. : : I would like to present initial revision of my generic PCI SD Host : Controller driver (sdhci). It support PCI devices with class 8 and : subclass 5 according to SD Host Controller Specification. With some : limitations it successfully works on my Acer TM6292 notebook with ENE : CB714 card reader. : : Things that are working now: : - PIO mode single and multiple block read and write, : - 1 and 4 bits bus width support. : : In PIO mode with 4GB SD card on 30MHz 4bit bus I have reached about : 3.5MB/s (limited by CPU) linear read and 7MB/s (limited by card) linear : write. Small blocks read/write performance limited by card. : : Things that are not working yet: : - DMA modes (code is written, but as my controller looks like has : broken DMA I have no ability to debug it), : - card insert/remove detection (need more thinking), you should reload : mmc module to rescan cards, : - SDHC and MMC cards (have no such cards now to debug that code), only : standard capacity SD Memory cards up to 4GB size are supported now, : - high speed (double rate) bus mode (need more thinking and DMA support). : : Also to get such results I have improved existing mmc and mmcsd drivers : a bit. mmc driver got: : - 4 bit bus width support, : - write protection switch support, : - cards with more then 2GB capacity support. : mmcsd driver got: : - multiple block read and write support, : - cards with more then 2GB capacity support, : - I/O error reporting, : - write protection switch support. : : Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found at: : http://people.freebsd.org/~mav/sdhci/ : : I will be grateful for any feedbacks, comments and support. I'll take a look at the driver and post a code review... Warner From admin at lissyara.su Sun Sep 28 11:01:32 2008 From: admin at lissyara.su (Alex Keda) Date: Sun Sep 28 11:01:39 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: <48DEA8E7.2080503@FreeBSD.org> References: <48DEA8E7.2080503@FreeBSD.org> Message-ID: <48DF5C9D.2000702@lissyara.su> Alexander Motin ?????: > Hi. > > I would like to present initial revision of my generic PCI SD Host > Controller driver (sdhci). It support PCI devices with class 8 and > subclass 5 according to SD Host Controller Specification. With some > limitations it successfully works on my Acer TM6292 notebook with ENE > CB714 card reader. > > Things that are working now: > - PIO mode single and multiple block read and write, > - 1 and 4 bits bus width support. > > In PIO mode with 4GB SD card on 30MHz 4bit bus I have reached about > 3.5MB/s (limited by CPU) linear read and 7MB/s (limited by card) linear > write. Small blocks read/write performance limited by card. > > Things that are not working yet: > - DMA modes (code is written, but as my controller looks like has > broken DMA I have no ability to debug it), > - card insert/remove detection (need more thinking), you should reload > mmc module to rescan cards, > - SDHC and MMC cards (have no such cards now to debug that code), only > standard capacity SD Memory cards up to 4GB size are supported now, > - high speed (double rate) bus mode (need more thinking and DMA support). > > Also to get such results I have improved existing mmc and mmcsd drivers > a bit. mmc driver got: > - 4 bit bus width support, > - write protection switch support, > - cards with more then 2GB capacity support. > mmcsd driver got: > - multiple block read and write support, > - cards with more then 2GB capacity support, > - I/O error reporting, > - write protection switch support. > > Latest patches against 8-CURRENT (should also fit 7-STABLE) may be found > at: > http://people.freebsd.org/~mav/sdhci/ > > I will be grateful for any feedbacks, comments and support. > Thanks! It work =) I have Acer Aspire 5101 but, when I attempt unload module - system hangs ========= messages ====== Sep 28 14:25:24 acer kernel: sdhci0: mem 0xd0210800-0xd02108ff irq 23 at device 4.2 on pci6 Sep 28 14:25:24 acer kernel: sdhci0: 1 slot(s) allocated Sep 28 14:25:24 acer kernel: sdhci0: [ITHREAD] Sep 28 14:25:24 acer kernel: mmc0: on sdhci0 Sep 28 14:25:24 acer kernel: mmc0: setting transfer rate to 33.000MHz Sep 28 14:25:24 acer kernel: sdhci1: at device 4.4 on pci6 Sep 28 14:25:24 acer kernel: sdhci1: 1 slot(s) allocated Sep 28 14:25:24 acer kernel: sdhci1: [ITHREAD] Sep 28 14:25:24 acer kernel: mmc1: on sdhci1 Sep 28 14:25:25 acer kernel: mmc1: SD card: 31129600 bytes Sep 28 14:25:25 acer kernel: mmcsd0: 29MB at mmc1 Sep 28 14:25:25 acer kernel: mmc1: setting transfer rate to 30.000MHz Sep 28 14:25:25 acer kernel: mmc1: setting bus width to 4 bits ========== pciconf -lv ============= cbb0@pci0:6:4:0: class=0x060700 card=0x009f1025 chip=0x14121524 rev=0x10 hdr=0x02 vendor = 'ENE Technology Inc' device = 'CB-712/714 CardBus Controller' class = bridge subclass = PCI-CardBus none1@pci0:6:4:1: class=0x050100 card=0x009f1025 chip=0x05301524 rev=0x01 hdr=0x00 vendor = 'ENE Technology Inc' device = 'CB-712/714/810 Memory Stick Card Reader' class = memory subclass = flash sdhci0@pci0:6:4:2: class=0x080501 card=0x009f1025 chip=0x05501524 rev=0x01 hdr=0x00 vendor = 'ENE Technology Inc' device = 'CB-712/714/810 Secure Digital Card Reader' class = base peripheral none2@pci0:6:4:3: class=0x050100 card=0x009f1025 chip=0x05201524 rev=0x01 hdr=0x00 vendor = 'ENE Technology Inc' device = 'PCI SmartMedia / xD Card Reader Controller' class = memory subclass = flash sdhci1@pci0:6:4:4: class=0x050100 card=0x009f1025 chip=0x05511524 rev=0x01 hdr=0x00 vendor = 'ENE Technology Inc' device = 'PCI SD/MMC Card Reader Controller' class = memory subclass = flash acer$ ============ uname -a =========== FreeBSD acer.lissyara.int.otradno.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sat Sep 27 16:35:08 MSD 2008 lissyara@acer.lissyara.int.otradno.ru:/usr/obj/usr/src/sys/color-console amd64 =========== kldstat ========== acer$ kldstat Id Refs Address Size Name 1 71 0xffffffff80100000 da1698 kernel (/boot/kernel/kernel) 2 2 0xffffffff80ea2000 759b8 sound.ko (/boot/kernel/sound.ko) 3 1 0xffffffff80f18000 21ae0 snd_hda.ko (/boot/kernel/snd_hda.ko) 4 1 0xffffffff80f3a000 2cf0 umodem.ko (/boot/kernel/umodem.ko) 5 1 0xffffffff80f3d000 6360 acpi_video.ko (/boot/kernel/acpi_video.ko) 6 1 0xffffffff80f44000 5538 atapicam.ko (/boot/kernel/atapicam.ko) 7 1 0xffffffff80f4a000 2f58 acpi_aiboost.ko (/boot/kernel/acpi_aiboost.ko) 8 1 0xffffffff80f4d000 3eb8 acpi_dock.ko (/boot/kernel/acpi_dock.ko) 9 1 0xffffffff80f51000 6e20 ng_bt3c.ko (/boot/kernel/ng_bt3c.ko) 10 5 0xffffffff80f58000 15bf8 netgraph.ko (/boot/kernel/netgraph.ko) 11 1 0xffffffff80f6e000 39660 ng_btsocket.ko (/boot/kernel/ng_btsocket.ko) 12 3 0xffffffff80fa8000 2da0 ng_bluetooth.ko (/boot/kernel/ng_bluetooth.ko) 13 1 0xffffffff80fab000 bec8 ng_ubt.ko (/boot/kernel/ng_ubt.ko) 14 1 0xffffffff80fb7000 2938 ubtbcmfw.ko (/boot/kernel/ubtbcmfw.ko) 15 1 0xffffffff80fba000 17890 ng_l2cap.ko (/boot/kernel/ng_l2cap.ko) 16 1 0xffffffff80fd2000 3fc8 iicbb.ko (/boot/kernel/iicbb.ko) 17 2 0xffffffff80fd6000 3f48 iicbus.ko (/boot/kernel/iicbus.ko) 19 1 0xffffffff80ff1000 14db0 tmpfs.ko (/boot/kernel/tmpfs.ko) 20 1 0xffffffff81222000 a48c ipfw.ko (/boot/kernel/ipfw.ko) 21 1 0xffffffff8122d000 b8ba fuse.ko (/usr/local/modules/fuse.ko) 22 1 0xffffffff81239000 3652 vkbd.ko (/boot/kernel/vkbd.ko) 23 1 0xffffffff8123d000 754 rtc.ko (/usr/local/modules/rtc.ko) 24 1 0xffffffff8123e000 1ab19 linux.ko (/boot/kernel/linux.ko) 25 1 0xffffffff81259000 24fd3 radeon.ko (/boot/kernel/radeon.ko) 26 1 0xffffffff8127e000 10341 drm.ko (/boot/kernel/drm.ko) 27 1 0xffffffff8128f000 2a02 mmc.ko (/boot/modules/mmc.ko) 28 1 0xffffffff81292000 b97 mmcsd.ko (/boot/modules/mmcsd.ko) 29 1 0xffffffff81293000 2a28 sdhci.ko (/boot/modules/sdhci.ko) From lme at FreeBSD.org Sun Sep 28 13:49:01 2008 From: lme at FreeBSD.org (Lars Engels) Date: Sun Sep 28 13:49:07 2008 Subject: Atheros wireless problems. In-Reply-To: <1222560406.89800.10.camel@jill.exit.com> References: <1222317948.1740.10.camel@jill.exit.com> <48DBB3EF.3060909@freebsd.org> <1222560406.89800.10.camel@jill.exit.com> Message-ID: <20080928134858.GO89204@e.0x20.net> On Sat, Sep 27, 2008 at 05:06:46PM -0700, Frank Mayhar wrote: > On Thu, 2008-09-25 at 08:53 -0700, Sam Leffler wrote: > > Frank Mayhar wrote: > > > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > > > believe) Atheros chipset in it; it's an a/b/g card. This is to use > > > while the chipset embedded in my laptop isn't supported. It came today, > > > I installed it tonight and, well, problems. > > The status codes look bogus. In 0.10.5.10 there is a code path through > > reset where status is not set if the chip is not brought out of low > > power mode. Why this might happen is beyond me (could be a cardbus > > problem) but if you initialize status to a known value before the hal > > calls that are failing this might confirm that as the problem. I've > > fixed the hal fwiw. > > That's definitely not the problem, it seems. I modified the driver to > zero 'status' in each of the routines that emit the message. When I ran > it today, it emitted the 'device timeout' and 'unable to reset hardware' > messages: > [...] > Anything else I might try? Are you running hald? I have the same error messages and can work around that problem by inserting the wireless card after hald is started. -------------- 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/20080928/e660698c/attachment.pgp From frank at exit.com Sun Sep 28 20:52:21 2008 From: frank at exit.com (Frank Mayhar) Date: Sun Sep 28 20:52:27 2008 Subject: Atheros wireless problems. In-Reply-To: <20080928134858.GO89204@e.0x20.net> References: <1222317948.1740.10.camel@jill.exit.com> <48DBB3EF.3060909@freebsd.org> <1222560406.89800.10.camel@jill.exit.com> <20080928134858.GO89204@e.0x20.net> Message-ID: <1222635140.46610.0.camel@jill.exit.com> On Sun, 2008-09-28 at 15:48 +0200, Lars Engels wrote: > On Sat, Sep 27, 2008 at 05:06:46PM -0700, Frank Mayhar wrote: > > On Thu, 2008-09-25 at 08:53 -0700, Sam Leffler wrote: > > > Frank Mayhar wrote: > > > > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I > > > > believe) Atheros chipset in it; it's an a/b/g card. This is to use > > > > while the chipset embedded in my laptop isn't supported. It came today, > > > > I installed it tonight and, well, problems. > > > The status codes look bogus. In 0.10.5.10 there is a code path through > > > reset where status is not set if the chip is not brought out of low > > > power mode. Why this might happen is beyond me (could be a cardbus > > > problem) but if you initialize status to a known value before the hal > > > calls that are failing this might confirm that as the problem. I've > > > fixed the hal fwiw. > > > > That's definitely not the problem, it seems. I modified the driver to > > zero 'status' in each of the routines that emit the message. When I ran > > it today, it emitted the 'device timeout' and 'unable to reset hardware' > > messages: > > > > [...] > > > Anything else I might try? > > Are you running hald? I have the same error messages and can work around > that problem by inserting the wireless card after hald is started. How very very weird. That worked. Why might this be? It's quite clearly a driver/application problem of some kind... -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From mav at FreeBSD.org Sun Sep 28 21:01:01 2008 From: mav at FreeBSD.org (Alexander Motin) Date: Sun Sep 28 21:01:08 2008 Subject: RFC: PCI SD host controller driver & mmc/mmcsd modules improvements In-Reply-To: References: <48DEA8E7.2080503@FreeBSD.org> <48DEA4EC.3030300@bluezbox.com> Message-ID: <48DFFE9A.9070302@FreeBSD.org> Carlos A. M. dos Santos wrote: > Here goes a good suggestion: do not forget to load the module, you > dumb ass! Now I got this: > > sdhci0: mem 0xe4103000-0xe41030ff irq 19 at device 6.3 on pci2 > sdhci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xe4103000 > sdhci0: 1 slot(s) allocated > sdhci0: [MPSAFE] > sdhci0: [ITHREAD] > mmc0: on sdhci0 > mmc0: Reset 0x6 never completed - 0x6. Looks like there is several version of this controller requiring special driver quirks. At least Linux driver includes several. I have implemented some, so you can try to play with them. > Much better. However, I got a system crash and reboot attempting to > unload the module. I have rewritten detach function. PS: Also I have implemented card insert/remove in a way specific for this device via mmc bus attach/detach. Not sure it is the best way for mmc subsystem generally, but it recommended by SD Host controller specification and works for now. -- Alexander Motin From lme at FreeBSD.org Mon Sep 29 05:51:11 2008 From: lme at FreeBSD.org (Lars Engels) Date: Mon Sep 29 05:51:18 2008 Subject: Atheros wireless problems. In-Reply-To: <1222635140.46610.0.camel@jill.exit.com> References: <1222317948.1740.10.camel@jill.exit.com> <48DBB3EF.3060909@freebsd.org> <1222560406.89800.10.camel@jill.exit.com> <20080928134858.GO89204@e.0x20.net> <1222635140.46610.0.camel@jill.exit.com> Message-ID: <20080929075110.8f6vo3zus08kwss0@0x20.net> Quoting Frank Mayhar : > On Sun, 2008-09-28 at 15:48 +0200, Lars Engels wrote: >> On Sat, Sep 27, 2008 at 05:06:46PM -0700, Frank Mayhar wrote: >> > On Thu, 2008-09-25 at 08:53 -0700, Sam Leffler wrote: >> > > Frank Mayhar wrote: >> > > > So I obtained a D-Link DWL-AG660 cardbus card, which has a 5213 (I >> > > > believe) Atheros chipset in it; it's an a/b/g card. This is to use >> > > > while the chipset embedded in my laptop isn't supported. It >> came today, >> > > > I installed it tonight and, well, problems. >> > > The status codes look bogus. In 0.10.5.10 there is a code path through >> > > reset where status is not set if the chip is not brought out of low >> > > power mode. Why this might happen is beyond me (could be a cardbus >> > > problem) but if you initialize status to a known value before the hal >> > > calls that are failing this might confirm that as the problem. I've >> > > fixed the hal fwiw. >> > >> > That's definitely not the problem, it seems. I modified the driver to >> > zero 'status' in each of the routines that emit the message. When I ran >> > it today, it emitted the 'device timeout' and 'unable to reset hardware' >> > messages: >> > >> >> [...] >> >> > Anything else I might try? >> >> Are you running hald? I have the same error messages and can work around >> that problem by inserting the wireless card after hald is started. > > How very very weird. That worked. Why might this be? It's quite > clearly a driver/application problem of some kind... I don't know. I brought this up some time ago but noone had a clue... It would be nice to find out how to prevent hald probing the cardbus, so you could insert the card before starting hald. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Digitale PGP-Unterschrift Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20080929/05924430/attachment.pgp From jhay at meraka.org.za Mon Sep 29 13:49:58 2008 From: jhay at meraka.org.za (John Hay) Date: Mon Sep 29 13:50:06 2008 Subject: setting bssid in adhoc mode In-Reply-To: <48DE8670.60606@freebsd.org> References: <20080922132500.GA25677@zibbi.meraka.csir.co.za> <3a142e750809250741j7b9003e4q539618d1c9407def@mail.gmail.com> <20080925161338.GA69284@zibbi.meraka.csir.co.za> <3a142e750809251159p3f5f3bam11243b3f144859c2@mail.gmail.com> <20080926055522.GA13842@zibbi.meraka.csir.co.za> <48DD210E.6050300@freebsd.org> <20080927071046.GA94774@zibbi.meraka.csir.co.za> <48DE8670.60606@freebsd.org> Message-ID: <20080929134954.GA69530@zibbi.meraka.csir.co.za> On Sat, Sep 27, 2008 at 12:16:00PM -0700, Sam Leffler wrote: > John Hay wrote: > >>>>>>>I'm trying out the new ath/wlan stuff in current. Should one still be > >>>>>>>able to set the bssid in adhoc mode? We normally lock the bssid in > >>>>>>>an adhoc network because of problems that the network split and does > >>>>>>>not merge, if you do not do it. > >>>>>>> > >>>>>>>What I have done is this: > >>>>>>> > >>>>>>># ifconfig wlan0 create wlandev ath0 wlanmode adhoc > >>>>>>># ifconfig wlan0 ssid ptamesh up > >>>>>>> > >>>>>>>Up to here works well. It will scan and if it finds another node with > >>>>>>>the > >>>>>>>same ssid, it will "lock" on that channel and use the correct bssid. > >>>>>>> > >>>>>>>If it does not find another node with the same ssid, it will start it > >>>>>>>own thing on channel 10. But it looks like one cannot set the bssid. > >>>>>>> > >>>>>>># ifconfig wlan0 bssid 02:07:ca:fe:ba:be > >>>>>>>ifconfig: 02:07:ca:fe:ba:be: bad value > >>>>>>> > >>>>>>> > >>>>>>I had similar experience with STA mode, instead I use ap (ap is alias > >>>>>>for bssid, at least it works in STA mode) > >>>>>>I never bothered is this bug in manual page, ifconfig or in something > >>>>>>else > >>>>>>... > >>>>>> > >>>>>> > >>>>>Ah, thanks yes, "ifconfig wlan0 ap 02:07:ca:fe:ba:be" works just fine. > >>>>>Just do not try to unset it with "ifconfig wlan0 ap -". That is an > >>>>>alias for "panic now" :-) > >>>>> > >>>>> > >>>>Well, on my system it doesnt panic here. > >>>>So more info to debug "your" panic is required ... > >>>> > >>>> > >>>I'll have to see if I can reproduce it. > >>> > >>> > >>> > >>>>>So it looks like ifconfig is getting confused with the many different > >>>>>uses of the keyword bssid. > >>>>> > >>>>>I must say I still do not understand what the other use for bssid is. > >>>>>Close to the end of ifconfig/ifieee80211.c there are these: > >>>>> > >>>>>DEF_CMD_ARG("bssid", set80211bssid), > >>>>>DEF_CMD_ARG("ap", set80211bssid), > >>>>>... > >>>>>DEF_CLONE_CMD("bssid", 1, set80211clone_bssid), > >>>>>DEF_CLONE_CMD("-bssid", 0, set80211clone_bssid), > >>>>> > >>>>>So my guess is that I was hitting the clone version when in fact I > >>>>>needed the other version. Luckily ap does not have a clone version. > >>>>>So when should the clone version be used? And how does ifconfig > >>>>>decide which one to use? > >>>>> > >>>>> > >>>I looked into the ifconfig code a bit more. I think that with the > >>>current code in the ifconfig() and cmd_lookup() functions, it is > >>>imposssible to have two different keywords that share the same > >>>keyword. cmd_lookup() will always search until it finds the first > >>>instance in the list and return that. The first instance in this > >>>case being the last one added. > >>> > >>> > >>Correct. > >> > >> > >>>So either the code must change or one of the bssid keywords have > >>>to change. My suggestion would be to keep the bssid for which ap > >>>is an alias and change the other one. Anybody have a suggestion > >>>of what to change it to? > >>> > >>> > >>> > >>I prefer to change the code to handle this ambiguity within > >>ifieee80211.c. You cannot use both together or at least they are > >>redundant. I'll look at it when I've got time; but don't let me > >>distract you. > >> > > > >So what should the behaviour be? How should ifconfig know which bssid > >function to use? Should the clone variant be used when it is used on > >the same line as create? And the other if there is not a create on the > >line? Or some other way? And should the other DEF_CLONE... keywords > >also be handled the same way? > > > >John > > > Try the attached change. It looked easier to fix this for all possible > usage instead of complicating the 802.11 stuff. The change forces all > keywords marked "DEF_CLONE" to come first on the command line followed > by keywords that are marked !DEF_CLONE. At some point it's likely we'll > need to stick a real parser in ifconfig but I think this change is small > enough to just do it this way (it also slightly cleans up the hack for > pushing the clone operation out before parsing/handling subsequent cmd > line args). Thanks, I have tried it on my notebook and some Avila ARM boards and it works well. Together with your fix for resetting the bssid, things are looking well. Scanning in adhoc mode is also working again. BTW. I have tried my 4 atheros cards in an Avila again and it is working! I think it was the interrupt fixes by Rafal. John > Sam > > Index: ifconfig.c > =================================================================== > --- ifconfig.c (revision 183416) > +++ ifconfig.c (working copy) > @@ -392,14 +392,21 @@ > } > > static const struct cmd * > -cmd_lookup(const char *name) > +cmd_lookup(const char *name, int iscreate) > { > #define N(a) (sizeof(a)/sizeof(a[0])) > const struct cmd *p; > > for (p = cmds; p != NULL; p = p->c_next) > - if (strcmp(name, p->c_name) == 0) > - return p; > + if (strcmp(name, p->c_name) == 0) { > + if (iscreate) { > + if (p->c_iscloneop) > + return p; > + } else { > + if (!p->c_iscloneop) > + return p; > + } > + } > return NULL; > #undef N > } > @@ -437,6 +444,7 @@ > ifconfig(int argc, char *const *argv, int iscreate, const struct afswtch *afp) > { > const struct afswtch *nafp; > + const struct cmd *p; > struct callback *cb; > int s; > > @@ -452,9 +460,38 @@ > err(1, "socket(family %u,SOCK_DGRAM", ifr.ifr_addr.sa_family); > > while (argc > 0) { > - const struct cmd *p; > - > - p = cmd_lookup(*argv); > + p = cmd_lookup(*argv, iscreate); > + if (iscreate && p == NULL) { > + /* > + * Push the clone create callback so the new > + * device is created and can be used for any > + * remaining arguments. > + */ > + cb = callbacks; > + if (cb == NULL) > + errx(1, "internal error, no callback"); > + callbacks = cb->cb_next; > + cb->cb_func(s, cb->cb_arg); > + iscreate = 0; > + /* > + * Handle any address family spec that > + * immediately follows and potentially > + * recreate the socket. > + */ > + nafp = af_getbyname(*argv); > + if (nafp != NULL) { > + argc--, argv++; > + if (nafp != afp) { > + close(s); > + afp = nafp; > + goto top; > + } > + } > + /* > + * Look for a normal parameter. > + */ > + continue; > + } > if (p == NULL) { > /* > * Not a recognized command, choose between setting > @@ -463,33 +500,6 @@ > p = (setaddr ? &setifdstaddr_cmd : &setifaddr_cmd); > } > if (p->c_u.c_func || p->c_u.c_func2) { > - if (iscreate && !p->c_iscloneop) { > - /* > - * Push the clone create callback so the new > - * device is created and can be used for any > - * remaining arguments. > - */ > - cb = callbacks; > - if (cb == NULL) > - errx(1, "internal error, no callback"); > - callbacks = cb->cb_next; > - cb->cb_func(s, cb->cb_arg); > - iscreate = 0; > - /* > - * Handle any address family spec that > - * immediately follows and potentially > - * recreate the socket. > - */ > - nafp = af_getbyname(*argv); > - if (nafp != NULL) { > - argc--, argv++; > - if (nafp != afp) { > - close(s); > - afp = nafp; > - goto top; > - } > - } > - } > if (p->c_parameter == NEXTARG) { > if (argv[1] == NULL) > errx(1, "'%s' requires argument", -- John Hay -- John.Hay@meraka.csir.co.za / jhay@FreeBSD.org