From owner-freebsd-mobile@FreeBSD.ORG Sun Feb 10 15:06:39 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F24116C2; Sun, 10 Feb 2013 15:06:38 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id BE58820A; Sun, 10 Feb 2013 15:06:37 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id r1AF6ZcM078005; Mon, 11 Feb 2013 02:06:36 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 11 Feb 2013 02:06:35 +1100 (EST) From: Ian Smith To: Kevin Oberman Subject: Re: Notes; Lenovo T400 In-Reply-To: Message-ID: <20130211001022.R71572@sola.nimnet.asn.au> References: <20130204020335.U87033@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Adrian Chadd , freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2013 15:06:39 -0000 On Fri, 8 Feb 2013 22:52:13 -0800, Kevin Oberman wrote: > On Sun, Feb 3, 2013 at 7:10 AM, Ian Smith wrote: > > On Sat, 2 Feb 2013 22:46:26 -0800, Kevin Oberman wrote: > > > On Fri, Feb 1, 2013 at 5:36 PM, Adrian Chadd wrote: > > > > Yeah I commented it out to make it work. > > > > > > > > Try booting to single user mode and then try a suspend/resume pass. > > > > > > > > > > > > > > > > Adrian > > > > > > > > > > > > On 1 February 2013 17:34, Kevin Oberman wrote: > > > >> Adrian, > > > >> > > > >> Can I assume that you did NOT have the '#' in the sysctl.conf? (Still > > > >> hoping to et my T520 to resume some day.) > > > >> > > > >> On Wed, Jan 30, 2013 at 9:35 PM, Adrian Chadd wrote: > > > >>> Hi, > > > >>> > > > >>> It turns out my Lenovo T400 issue? It was because in /etc/sysctl.conf > > > >>> I had this: > > > >>> > > > >>> # hw.acpi.reset_video=1 > > > >>> > > > >>> .. don't do that. > > > >>> > > > >>> > > > >>> > > > >>> Adrian > > > > > > Almost worked. I saw several acpi power state errors as the system > > > suspended. On resume, the system came back up, but the display > > > remained off (no backlight). I was able to type 'shutdown -r now' and > > > do a clean reboot. Of course, the number of differences between single > > > and multi-user are substantial, but this eliminates a LOT of things. > > > > > > I then tried coming up to multi-user, but not starting X (Gnome). > > > Again, it suspended and resumed with no display. My network came up > > > and I sshed into the system from my phone. Then I got an interrupt > > > from my greyhounds. Time to brush their teeth. I was away from the > > > laptop for about 10 minutes. When I came back, it was dead. My ssh > > > session was hung and I could no longer ping it. :-( > > > > > > Weird. It's getting really close, but not quite. I suspect that the > > > video ties into it in some way. I also mount a couple of FUSE NTFS > > > partitions when I start X (Gnome auto-mounts them). When I suspend in > > > Gnome, the network never comes back up and the power LED pulses just > > > like it does while suspended, so it really does not finish the resume. Sounds more like it doesn't or scarcely begins the resume in the latter case; powering up from S3 sleep sufficiently to run resume code is pretty low level BIOS stuff I'd have thought, power LED and such? I clearly know nothing about video issues these days, but 'blank screen on resume' seems to come up pretty often. Maybe more on acpi@? > > > I think I can now eliminate the wireless (iwn), at least. > > > > > > Thanks for the suggestions! > > > > Kevin, have you tried doing suspend/resume after booting with verbose > > messages? If you can get in eg ssh as above, you can dmesg > file and > > even if you can't, it should all be there in /var/log/messages .. I've > > found it handy to see all the blow-by-blow disabling of devices then > > reenabling after resume for working out what happened (or didn't :) > > > > You can also increase ACPI verbosity, but I've rarely needed to. > > Finally gave it a try, but nothing looks very odd to me. It stays > responsive for about a couple of minutes and then stops responding to > either the ssh session or the keyboard. > > Here are the contents of messages for the suspend and the resume. I > don't really see anything very bad. Looks like firewire has a problem. Just a few likely unhelpful observations .. First thing I noticed was the lack of my very old friend, the 'wakeup from sleeping state (slept hh:mm:ss)' line, which marks wakeup, busses ablaze, before device reconfig. Is this on -current? > Feb 8 22:26:17 rogue console-kit-daemon[1509]: WARNING: kvm_getenvv failed: > Feb 8 22:26:17 rogue kernel: blanktime screensaver > Feb 8 22:26:17 rogue kernel: splash: image decoder found: logo_saver I guess you've tried disabling screensavers? Recalling older issues .. > Feb 8 22:26:21 rogue ntpd[1351]: time reset -1.063975 s > Feb 8 22:26:24 rogue login: ROOT LOGIN (root) ON ttyv0 > Feb 8 22:26:45 rogue acpi: suspend at 20130208 22:26:45 > Feb 8 22:26:48 rogue kernel: acpi_timer0: switching timecounter, > TSC-low -> ACPI-fast Switching timecounters is news; I must read more commit messages! :) > Feb 8 22:26:48 rogue kernel: (ada0:ahcich0:0:0:0): spin-down > Feb 8 22:26:49 rogue kernel: (ada1:ahcich1:0:0:0): spin-down > Feb 8 22:27:03 rogue kernel: acpi_lid0: wake_prep enabled for \_SB_.LID_ (S3) > Feb 8 22:27:03 rogue kernel: acpi_button0: wake_prep enabled for > \_SB_.SLPB (S3) > Feb 8 22:27:03 rogue kernel: uhub0: at usbus0, port 1, addr 1 (disconnected) > Feb 8 22:27:03 rogue kernel: ugen0.2: at usbus0 (disconnected) > Feb 8 22:27:03 rogue kernel: uhub2: at uhub0, port 1, addr 2 (disconnected) > Feb 8 22:27:03 rogue kernel: ugen0.3: > at usbus0 (disconnected) > Feb 8 22:27:03 rogue kernel: pci0:0:28:0: Transition from D0 to D3 > Feb 8 22:27:03 rogue kernel: wlan0: link state changed to DOWN > Feb 8 22:27:03 rogue kernel: pci0:3:0:0: Transition from D0 to D3 > Feb 8 22:27:03 rogue kernel: pci0:0:28:1: Transition from D0 to D3 > Feb 8 22:27:03 rogue kernel: pci0:0:28:3: Transition from D0 to D3 > Feb 8 22:27:03 rogue kernel: fwohci0: fwohci_pci_suspend > Feb 8 22:27:03 rogue kernel: pci0:13:0:0: Transition from D0 to D3 > Feb 8 22:27:03 rogue kernel: pci0:13:0:3: Transition from D0 to D3 > Feb 8 22:27:03 rogue kernel: pci0:0:28:4: Transition from D0 to D3 > Feb 8 22:27:03 rogue kernel: uhub1: at usbus1, port 1, addr 1 (disconnected) > Feb 8 22:27:03 rogue kernel: ugen1.2: at usbus1 (disconnected) > Feb 8 22:27:03 rogue kernel: uhub3: at uhub1, port 1, addr 2 (disconnected) No surprises, without knowing your device mapping .. > Feb 8 22:27:03 rogue kernel: vga0: saving 6724 bytes of video state > Feb 8 22:27:03 rogue kernel: vga0: saving color palette Less than twice the size of state saved by my lil' S3 Savage card :) > Feb 8 22:27:03 rogue kernel: pci0: failed to set ACPI power state D2 > on \_SB_.PCI0.EXP1: AE_BAD_PARAMETER > Feb 8 22:27:03 rogue kernel: pci0: failed to set ACPI power state D2 > on \_SB_.PCI0.EXP2: AE_BAD_PARAMETER > Feb 8 22:27:03 rogue kernel: pci0: failed to set ACPI power state D2 > on \_SB_.PCI0.EXP4: AE_BAD_PARAMETER > Feb 8 22:27:03 rogue kernel: pci0: failed to set ACPI power state D2 > on \_SB_.PCI0.EXP5: AE_BAD_PARAMETER Card reader I guess? I get the same messages on 9.1 for both cardbus bridges. All below are on the resume path after the wakeup. > Feb 8 22:27:03 rogue kernel: acpi_lid0: run_prep cleaned up for \_SB_.LID_ > Feb 8 22:27:03 rogue kernel: acpi_button0: run_prep cleaned up for \_SB_.SLPB > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.VID_ I wish I knew something about how X resumes graphic video state, or what triggers it to .. I guess it has its own resume method? Is that suspect? > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.IGBE > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EHC2 > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.HDEF > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EXP1 > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EXP2 > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EXP4 > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EXP5 I see the above four repeated below, plus .EXP5.SLOT. I don't get that. > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EHC1 > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.LPC_ > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.SAT1 > Feb 8 22:27:03 rogue kernel: pci0:0:22:0: Transition from D0 to D3 Hmm, what is pci0:0:22:0 and why is it going back to sleep? firewire? > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EXP1 > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EXP2 > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EXP4 > Feb 8 22:27:03 rogue kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.EXP5 > Feb 8 22:27:03 rogue kernel: pci13: set ACPI power state D0 on > \_SB_.PCI0.EXP5.SLOT A card in one of the slots? > Feb 8 22:27:03 rogue kernel: fwohci0: Phy 1394a available S400, 1 ports. > Feb 8 22:27:03 rogue kernel: fwohci0: Link S400, max_rec 2048 bytes. > Feb 8 22:27:03 rogue kernel: fwohci0: Initiate bus reset > Feb 8 22:27:03 rogue kernel: vga0: calling BIOS POST > Feb 8 22:27:03 rogue kernel: fwohci0: fwohci_intr_core: BUS reset > Feb 8 22:27:03 rogue kernel: fwohci0: fwohci_intr_core: > node_id=0x00000000, SelfID Count=1, CYCLEMASTER mode > Feb 8 22:27:03 rogue kernel: firewire0: 1 nodes, maxhop <= 0 cable > IRM irm(0) (me) > Feb 8 22:27:03 rogue kernel: firewire0: bus manager 0 > Feb 8 22:27:03 rogue kernel: fwohci0: unrecoverable error Yes it looks unhappy. BIOS POST amidst that is probably coincidence. > Feb 8 22:27:03 rogue kernel: hdaa0: Headphones redirection for > association 0 nid=25 using unsolicited responses. > Feb 8 22:27:03 rogue kernel: ahcich0: AHCI reset... > Feb 8 22:27:03 rogue kernel: ahcich0: SATA connect time=1000us status=00000123 > Feb 8 22:27:03 rogue kernel: ahcich0: AHCI reset: device found > Feb 8 22:27:03 rogue kernel: ahcich1: AHCI reset... > Feb 8 22:27:03 rogue kernel: ahcich1: SATA connect time=1000us status=00000123 > Feb 8 22:27:03 rogue kernel: ahcich1: AHCI reset: device found > Feb 8 22:27:03 rogue kernel: ahcich3: AHCI reset... > Feb 8 22:27:03 rogue kernel: ahcich3: SATA connect timeout > time=10000us status=00000000 > Feb 8 22:27:03 rogue kernel: ahcich3: AHCI reset: device not found > Feb 8 22:27:03 rogue kernel: ahcich4: AHCI reset... > Feb 8 22:27:03 rogue kernel: ahcich4: SATA connect timeout > time=10000us status=00000000 > Feb 8 22:27:03 rogue kernel: ahcich4: AHCI reset: device not found > Feb 8 22:27:03 rogue kernel: atkbd: the current kbd controller > command byte 0047 > Feb 8 22:27:03 rogue kernel: atkbd: keyboard ID 0x54ab (2) > Feb 8 22:27:03 rogue kernel: kbdc: RESET_KBD return code:00fa > Feb 8 22:27:03 rogue kernel: kbdc: RESET_KBD status:00aa > Feb 8 22:27:03 rogue kernel: kbdc: TEST_AUX_PORT status:0000 > Feb 8 22:27:03 rogue kernel: kbdc: RESET_AUX return code:00fa > Feb 8 22:27:03 rogue kernel: kbdc: RESET_AUX status:00aa > Feb 8 22:27:03 rogue kernel: kbdc: RESET_AUX ID:0000 All that looks 'normal' from here, given AHCI/SATA rather than ATA/PATA. > Feb 8 22:27:03 rogue kernel: firmware: 'iwn6000g2afw' version 0: > 444128 bytes loaded at 0xffffffff8183c0b0 > Feb 8 22:27:03 rogue kernel: battery0: battery initialization start > Feb 8 22:27:03 rogue kernel: uhub0: rev 2.00/1.00, addr 1> on usbus1 > Feb 8 22:27:03 rogue kernel: uhub1: rev 2.00/1.00, addr 1> on usbus0 > Feb 8 22:27:03 rogue kernel: ahcich0: AHCI reset: device ready after 800ms > Feb 8 22:27:03 rogue kernel: ahcich1: AHCI reset: device ready after 1200ms > Feb 8 22:27:03 rogue kernel: uhub0: 3 ports with 3 removable, self powered > Feb 8 22:27:03 rogue kernel: uhub1: 3 ports with 3 removable, self powered > Feb 8 22:27:03 rogue kernel: ugen1.2: at usbus1 > Feb 8 22:27:03 rogue kernel: uhub2: class 9/0, rev 2.00/0.00, addr 2> on usbus1 > Feb 8 22:27:03 rogue kernel: ugen0.2: at usbus0 > Feb 8 22:27:03 rogue kernel: uhub3: class 9/0, rev 2.00/0.00, addr 2> on usbus0 > Feb 8 22:27:03 rogue kernel: uhub3: 6 ports with 6 removable, self powered > Feb 8 22:27:03 rogue kernel: battery0: battery initialization done, > tried 1 times > Feb 8 22:27:03 rogue kernel: wlan0: link state changed to UP > Feb 8 22:27:03 rogue kernel: uhub2: 8 ports with 8 removable, self powered > Feb 8 22:27:03 rogue kernel: (ada0:ahcich0:0:0:0): resume > Feb 8 22:27:03 rogue kernel: (ada1:ahcich1:0:0:0): resume Seems uneventful. > Feb 8 22:27:03 rogue kernel: acpi_timer0: restoring timecounter, > ACPI-fast -> TSC-low I'm curious about this. Note the next log timestamp is at least 13 seconds earlier, but maybe that's why we're using TSC-low instead? Yes, looks like wireless is working below .. The fact that it resumed, sans backlight - is there anything that could poke that from /etc/rc.resume? DPMS? - but then died inside 10 minutes seems a bit spooky. I remember from DOS days - the screensaver dun it! cheers, Ian > Feb 8 22:26:50 rogue wpa_supplicant[538]: CTRL-EVENT-DISCONNECTED > bssid=00:26:b8:67:c3:2d reason=0 > Feb 8 22:26:50 rogue wpa_supplicant[538]: Failed to initiate AP scan. > Feb 8 22:26:53 rogue last message repeated 3 times > Feb 8 22:26:57 rogue wpa_supplicant[538]: Trying to associate with > 00:26:b8:67:c3:2d (SSID='babcom' freq=2437 MHz) > Feb 8 22:26:57 rogue wpa_supplicant[538]: Associated with 00:26:b8:67:c3:2d > Feb 8 22:26:57 rogue wpa_supplicant[538]: WPA: Key negotiation > completed with 00:26:b8:67:c3:2d [PTK=CCMP GTK=CCMP] > Feb 8 22:26:57 rogue wpa_supplicant[538]: CTRL-EVENT-CONNECTED - > Connection to 00:26:b8:67:c3:2d completed (reauth) [id=1 id_str=] > Feb 8 22:27:03 rogue acpi: resumed at 20130208 22:27:03 > Feb 8 22:27:03 rogue dhclient: New IP Address (wlan0): 192.168.1.5 > Feb 8 22:27:03 rogue dhclient: New Subnet Mask (wlan0): 255.255.255.0 > Feb 8 22:27:03 rogue dhclient: New Broadcast Address (wlan0): 192.168.1.255 > Feb 8 22:27:03 rogue dhclient: New Routers (wlan0): 192.168.1.1 > Feb 8 22:27:03 rogue root: Unknown USB device: vendor 0x04f2 product > 0xb217 bus uhub3 > Feb 8 22:27:03 rogue kernel: ugen0.3: at usbus0 > Feb 8 22:27:03 rogue root: Unknown USB device: vendor 0x04f2 product > 0xb217 bus uhub3 > Feb 8 22:27:41 rogue sudo: oberman : TTY=pts/0 ; > PWD=/usr/home/oberman ; USER=root ; COMMAND=/bin/csh > Feb 8 22:27:52 rogue wpa_supplicant[538]: WPA: Group rekeying > completed with 00:26:b8:67:c3:2d [GTK=CCMP] > -- > R. Kevin Oberman, Network Engineer > E-mail: kob6558@gmail.com From owner-freebsd-mobile@FreeBSD.ORG Sun Feb 10 20:59:28 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2D60D2DF for ; Sun, 10 Feb 2013 20:59:28 +0000 (UTC) (envelope-from mmbsd1982@yahoo.com) Received: from nm26.bullet.mail.ne1.yahoo.com (nm26.bullet.mail.ne1.yahoo.com [98.138.90.89]) by mx1.freebsd.org (Postfix) with ESMTP id A30DE1D8 for ; Sun, 10 Feb 2013 20:59:27 +0000 (UTC) Received: from [98.138.90.57] by nm26.bullet.mail.ne1.yahoo.com with NNFMP; 10 Feb 2013 20:56:26 -0000 Received: from [98.138.89.196] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 10 Feb 2013 20:56:26 -0000 Received: from [127.0.0.1] by omp1054.mail.ne1.yahoo.com with NNFMP; 10 Feb 2013 20:56:26 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 444493.43176.bm@omp1054.mail.ne1.yahoo.com Received: (qmail 44648 invoked by uid 60001); 10 Feb 2013 20:56:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1360529786; bh=SUioHdV687Pd4JrqvjUC/uoKeNFodP5iMDefy3naqUU=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=IJlIFV67w/p7O1SWu4NKSAkA+XxIRZSUcomTT065ZJ5gNVRcWCzGdk+CpwsR+ZXdm/IE0P8DoBGmdch/+5U4IQS9XBp2/Td7VzNwcsizUV5rwanyINMiWp1aYdRfyocFqCW5aKyTzoP5PXQa3aDyBZbdpASO5UXxKtyuMTOmTwo= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=cc35kS17qxeHUNAw52Q6iMPWsU3cIiH7CpRQMpo4gKXpELPsPag613Fpg/CVb5Cf4/qYV4wnCBv8/h9yfbl9YLabe760X5nEYYpcaEQfFkLSIFu8pEv7gEHVcVZMap+WWzqGa5zNbJBSQv5ScPM3ewYcV4Ou8LeW6h6jWriTZ4k=; X-YMail-OSG: jALqDpQVM1l2qlXJ03muwMAk68pQUsHPLQLHu3jvUKBzSHm d4KhpXzxwLwCdhygzChbbKWGMNgabFt4qBMqVOggOYYA2AGwzKtMozTcO0Oi 0NHpBJ0lnWX0SS4G2jU7jch84ywcCkWem6geAd8MAMp4sJrpFkog9DZi4wJp 1bZ04Khhzb.QZHKChXolfrT89v9CsEZoEiERsaeij0jQ.BfypHM3LJIMmyN. S2fnuxoTKYblZMgpnow7EsfPxjwhBXtFD9otsnFTqJ5bgDn5jR6s1UNWnjtD c8Zs3.wjRRqOIwauGTP.8oA1tTph9wfMagxjicEESHyliCiBXNjfD39jWe4_ d_FJDf_1My9g2oNxLor_gre0h7YNXPnYp6FEeJpptzSuyBrfuiPPanCF3l2Y U.hTk2mixX0SFK8uIHXyAJ__lMQHUdj1q6kpOezl_eqJKefmwosZEJMM5 Received: from [12.202.173.2] by web126105.mail.ne1.yahoo.com via HTTP; Sun, 10 Feb 2013 12:56:26 PST X-Rocket-MIMEInfo: 001.001, VGhlIE1vdG9yb2xhIERyb2lkIFJBWlIgaSAoYSB2YXJpYW50IG9mIHRoZSBSQVpSIG0pIGhhcyBhbiBpbnRlbCBhdG9tIHoyNDYwIHByb2Nlc3NvciBpbiBpdC4KClVubGVzcyBJIGFtIG1pc3Rha2VuLCB0aGlzIGlzIGFuIGFtZDY0IGNvbXBhdGlibGUgY2hpcCB0aGF0IG1haW5saW5lIEZyZWVCU0QgY291bGQgcnVuIG9uLCB5ZXMgPwoKV2l0aG91dCBnZXR0aW5nIGludG8gdGhlIHNwZWNpZmljcyBvZiBsb2FkaW5nIHRoZSBzeXN0ZW0gKGFuZCB1c2luZyBhIHRvdWNoc2NyZWVuIGFzIGlucHV0KSwgd291bGQBMAEBAQE- X-Mailer: YahooMailClassic/15.1.2 YahooMailWebService/0.8.132.503 Message-ID: <1360529786.27432.YahooMailClassic@web126105.mail.ne1.yahoo.com> Date: Sun, 10 Feb 2013 12:56:26 -0800 (PST) From: Mm Bsd Subject: FreeBSD on Motorola Droid RAZR i ... Intel Atom ... To: freebsd-mobile@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2013 20:59:28 -0000 The Motorola Droid RAZR i (a variant of the RAZR m) has an intel atom z2460 processor in it. Unless I am mistaken, this is an amd64 compatible chip that mainline FreeBSD could run on, yes ? Without getting into the specifics of loading the system (and using a touchscreen as input), would plain old amd64 FreeBSD run on this device ? From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 00:41:35 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5723BBF9 for ; Mon, 11 Feb 2013 00:41:35 +0000 (UTC) (envelope-from enzo@itatiaia.net) Received: from mail.waimax.net (mail.waimax.net [187.115.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 01E6FAE8 for ; Mon, 11 Feb 2013 00:41:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.waimax.net (Postfix) with ESMTP id 00D9248C1EB for ; Sun, 10 Feb 2013 22:24:45 -0200 (BRST) X-Virus-Scanned: amavisd-new at waimax.net Received: from mail.waimax.net ([127.0.0.1]) by localhost (mail.waimax.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7TEUMpw1w7_M for ; Sun, 10 Feb 2013 22:24:45 -0200 (BRST) Received: from localhost (localhost [127.0.0.1]) by mail.waimax.net (Postfix) with ESMTP id 9228248C242 for ; Sun, 10 Feb 2013 22:24:45 -0200 (BRST) X-Virus-Scanned: amavisd-new at waimax.net Received: from mail.waimax.net ([127.0.0.1]) by localhost (mail.waimax.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id m4I75MHblMqm for ; Sun, 10 Feb 2013 22:24:44 -0200 (BRST) Received: from Reloaded-PC (unknown [41.82.134.126]) by mail.waimax.net (Postfix) with ESMTPA id 09DA348C1EB for ; Sun, 10 Feb 2013 22:24:41 -0200 (BRST) Date: Mon, 11 Feb 2013 00:31:47 GMT Mime-version: 1.0 Subject: Can we be friends? From: Rachie Hunters To: Freebsd-mobile Message-Id: <211031.QLQJANAT@itatiaia.net> X-Mailer: MBM 5.7.1-US Original-recipient: rfc822;freebsd-mobile@freebsd.org Content-type: text/plain; charset="ISO-8859-1"; format=flowed Content-transfer-encoding: quoted-printable X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: rachie87ar@rediffmail.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 00:41:35 -0000 Hi; Rachael is my name, I will like to be your friend. I will tell you more about me and send you my photo, as soon as you tell me= little about you. I believe distance,age,sex and race does not matter to me, but care, honest= y and respect. I will be waiting for your mail. Have a nice time. Rachie From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 10:59:09 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 13189E71; Mon, 11 Feb 2013 10:59:09 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id C94951AD1; Mon, 11 Feb 2013 10:59:08 +0000 (UTC) Received: from irix.bris.ac.uk ([137.222.10.39] helo=ncs.bris.ac.uk) by dirj.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1U4r6A-0003sd-6D; Mon, 11 Feb 2013 10:59:00 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncs.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1U4r6A-0003uW-0Z; Mon, 11 Feb 2013 10:58:58 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6) with ESMTP id r1BAwvgm064224; Mon, 11 Feb 2013 10:58:57 GMT (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6/Submit) id r1BAwvhw064223; Mon, 11 Feb 2013 10:58:57 GMT (envelope-from mexas) Date: Mon, 11 Feb 2013 10:58:57 GMT From: Anton Shterenlikht Message-Id: <201302111058.r1BAwvhw064223@mech-cluster241.men.bris.ac.uk> To: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org Subject: on amd64 r246552: iwn0: : fatal firmware error X-Spam-Score: -3.2 X-Spam-Level: --- X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 10:59:09 -0000 This is a T61p 6459 laptop with (from pciconf -lv): iwn0@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 4965 AG or AGN [Kedron] Network Connection' class = network or (from dmesg): iwn0: mem 0xdf2fe000-0xdf2fffff irq 17 at device 0.0 on pci3 I use it with device iwn # Intel 4965/1000/5000/6000 wireless NICs. device iwn4965fw in the kernel. >From time to time, and I think under some load, e.g. rsync a partition in one windown and svn up /usr/ports in another, I get this failure: iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00008370000004C2 interrupt link = 0x000006DA000018B8 time = 2858416859 driver status: tx ring 0: qid=0 cur=96 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=16 queued=0 tx ring 4: qid=4 cur=163 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=14 I then have to restart the network via "/etc/rc.d/netif restart" and it's back to normal. >From ifconfig: iwn0: flags=8843 metric 0 mtu 2290 ether 00:21:5c:50:68:c3 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:21:5c:50:68:c3 inet 172.21.222.82 netmask 0xfffffc00 broadcast 255.255.255.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g status: associated ssid eduroam channel 1 (2412 MHz 11g) bssid 00:3a:98:62:cd:a0 country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 14 bmiss 10 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme roaming MANUAL I use it with wpa_supplicant: /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant.conf -D bsd -P /var/run/wpa_supplicant/wlan0.pid Please advise Thanks Anton From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 11:08:37 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C57667FC; Mon, 11 Feb 2013 11:08:37 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qe0-f46.google.com (mail-qe0-f46.google.com [209.85.128.46]) by mx1.freebsd.org (Postfix) with ESMTP id 771621D1A; Mon, 11 Feb 2013 11:08:37 +0000 (UTC) Received: by mail-qe0-f46.google.com with SMTP id 1so2527279qec.33 for ; Mon, 11 Feb 2013 03:08:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Ex450t87I5l2zEgGTj1aUafN9ITTYWZx1tHzm0x2ZMg=; b=Lj4ZCAdvWuYnvlpksFt+rYR38DRXqjP7x4l9D0gSBbkfbaB9/WREIv/vvGRfVVfby8 xWdkXKBiC78La1sC9DRK0kKwaq5DYJUsutzxMWhHmY8vgcu39iF7D0h5EqR/nKL7I0LS lGMmgSftL4Rw+sE+UUaTwsIJb/TgJPzSC0D7nVCSwZfKsjLeucaHe+5VFT7zJNSUu1pI F1GBgSxivt3K/0HSpE/CKsFjN4fWLNw5AyxJj3vlCN8ZdQ5RDAudf5qRV01GVReR95ql y8UujOKsrsszaiJDUk68BX6hOqbm5fCR20SA4Do2ipQfYIPFTming16n/b9M8wb/37bs 1zjw== MIME-Version: 1.0 X-Received: by 10.224.209.193 with SMTP id gh1mr5377861qab.86.1360580910894; Mon, 11 Feb 2013 03:08:30 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Mon, 11 Feb 2013 03:08:30 -0800 (PST) In-Reply-To: <201302111058.r1BAwvhw064223@mech-cluster241.men.bris.ac.uk> References: <201302111058.r1BAwvhw064223@mech-cluster241.men.bris.ac.uk> Date: Mon, 11 Feb 2013 12:08:30 +0100 X-Google-Sender-Auth: V9THKZIyLucC96sMEeLUvAn3zss Message-ID: Subject: Re: on amd64 r246552: iwn0: : fatal firmware error From: CeDeROM To: mexas@bristol.ac.uk Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 11:08:37 -0000 Yesterday I had something similar - it was cause by a radio switch flip: iwn0: RF switch: radio disabled ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ugen1.4: at usbus1 (disconnected) ubt0: at uhub3, port 7, addr 4 (disconnected) iwn0: iwn_intr: fatal firmware error firmware error log: error type = "SYSASSERT" (0x00000005) program counter = 0x0001EFD8 source line = 0x0000012E error data = 0x0000000000000000 branch link = 0x0001EEE40001EEE4 interrupt link = 0x0000153200000000 time = 767402829 driver status: tx ring 0: qid=0 cur=194 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=18 queued=0 tx ring 4: qid=4 cur=58 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 tx ring 16: qid=16 cur=0 queued=0 tx ring 17: qid=17 cur=0 queued=0 tx ring 18: qid=18 cur=0 queued=0 tx ring 19: qid=19 cur=0 queued=0 rx ring: cur=1 FreeBSD mercury 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Fri Feb 8 23:26:37 CET 2013 root@mercury:/usr/obj/usr/src/sys/CeDeROM-MERCURY amd64 % pciconf -lv iwn0@pci0:2:0:0: class=0x028000 card=0x13218086 chip=0x422c8086 rev=0x35 hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Advanced-N 6200' class = network Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 11:18:56 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 53DE8185; Mon, 11 Feb 2013 11:18:56 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 0BD0D1E29; Mon, 11 Feb 2013 11:18:55 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirj.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1U4rPT-0005Oe-3c; Mon, 11 Feb 2013 11:18:55 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1U4rPS-0001Ex-OG; Mon, 11 Feb 2013 11:18:54 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6) with ESMTP id r1BBIsJM064360; Mon, 11 Feb 2013 11:18:54 GMT (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6/Submit) id r1BBIsFH064359; Mon, 11 Feb 2013 11:18:54 GMT (envelope-from mexas) Date: Mon, 11 Feb 2013 11:18:54 GMT From: Anton Shterenlikht Message-Id: <201302111118.r1BBIsFH064359@mech-cluster241.men.bris.ac.uk> To: cederom@tlen.pl, mexas@bristol.ac.uk Subject: Re: on amd64 r246552: iwn0: : fatal firmware error In-Reply-To: Cc: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 11:18:56 -0000 From tomek.cedro@gmail.com Mon Feb 11 11:11:23 2013 Yesterday I had something similar - it was cause by a radio switch flip: iwn0: RF switch: radio disabled ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ugen1.4: at usbus1 (disconnected) ubt0: at uhub3, port 7, addr 4 (disconnected) iwn0: iwn_intr: fatal firmware error firmware error log: error type = "SYSASSERT" (0x00000005) program counter = 0x0001EFD8 source line = 0x0000012E error data = 0x0000000000000000 branch link = 0x0001EEE40001EEE4 interrupt link = 0x0000153200000000 time = 767402829 driver status: tx ring 0: qid=0 cur=194 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=18 queued=0 tx ring 4: qid=4 cur=58 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 tx ring 16: qid=16 cur=0 queued=0 tx ring 17: qid=17 cur=0 queued=0 tx ring 18: qid=18 cur=0 queued=0 tx ring 19: qid=19 cur=0 queued=0 rx ring: cur=1 FreeBSD mercury 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Fri Feb 8 23:26:37 CET 2013 root@mercury:/usr/obj/usr/src/sys/CeDeROM-MERCURY amd64 % pciconf -lv iwn0@pci0:2:0:0: class=0x028000 card=0x13218086 chip=0x422c8086 rev=0x35 hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Advanced-N 6200' class = network Best regards, Tomek Yes, I can reproduce this on amd64 -current. I had to flip the switch twice to cause this: iwn0: RF switch: radio disabled wlan0: link state changed to DOWN iwn0: RF switch: radio enabled wlan0: link state changed to UP iwn0: RF switch: radio disabled wlan0: link state changed to DOWN iwn0: RF switch: radio enabled iwn0: iwn_intr: fatal firmware error firmware error log: error type = "NMI_INTERRUPT_WDG" (0x00000004) program counter = 0x0000046C source line = 0x000000D0 error data = 0x0000000207030000 branch link = 0x00008370000004C2 interrupt link = 0x000006DA000018B8 time = 200035 driver status: tx ring 0: qid=0 cur=0 queued=0 tx ring 1: qid=1 cur=0 queued=0 tx ring 2: qid=2 cur=0 queued=0 tx ring 3: qid=3 cur=3 queued=1 tx ring 4: qid=4 cur=97 queued=0 tx ring 5: qid=5 cur=0 queued=0 tx ring 6: qid=6 cur=0 queued=0 tx ring 7: qid=7 cur=0 queued=0 tx ring 8: qid=8 cur=0 queued=0 tx ring 9: qid=9 cur=0 queued=0 tx ring 10: qid=10 cur=0 queued=0 tx ring 11: qid=11 cur=0 queued=0 tx ring 12: qid=12 cur=0 queued=0 tx ring 13: qid=13 cur=0 queued=0 tx ring 14: qid=14 cur=0 queued=0 tx ring 15: qid=15 cur=0 queued=0 rx ring: cur=47 in6_purgeaddr: err=65, destination address delete failed However, in my earlier report I got to this error with no flipping the switch at all. Anton From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 11:24:26 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 972E7352; Mon, 11 Feb 2013 11:24:26 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-qa0-f41.google.com (mail-qa0-f41.google.com [209.85.216.41]) by mx1.freebsd.org (Postfix) with ESMTP id 3A8411E84; Mon, 11 Feb 2013 11:24:25 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id hy16so1118048qab.14 for ; Mon, 11 Feb 2013 03:24:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2SToFvOzxjzrmOACcl8bme32Q8+tbBMEKbARfCw41II=; b=Br2agyA42Pz8OV60ouSXrZuAYsLVaf1CajxYhT7ZdsIVcVMH+v1aq7TOrtG17SKM+8 4wyDEQsRNuWVitqI3ErhzwJC48SEFf4TrPuIwTu31uEcIgVLTzzsncwDwot/QL71PN0u kD99JV+8bnYtCNP0mCf9AoqUZLJ08CftC5rWPNQwyBgTZ//dpU6m+sqmhlxeqsxGQh09 9n9Nt8o4zDenJcMD5d3rXMSuW49DbatF00Rsb3FmJC0MX2smLsRcJNy1WAQ5Nhaa+sQh 5z/O7RFk7YmNbnF3vbCVT8IjkXHCJdcd0fLdeKGPs6PwIegmfP8lso4xY6U90LP4vvjY mghQ== MIME-Version: 1.0 X-Received: by 10.49.14.202 with SMTP id r10mr6133904qec.10.1360581865366; Mon, 11 Feb 2013 03:24:25 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.49.71.204 with HTTP; Mon, 11 Feb 2013 03:24:25 -0800 (PST) In-Reply-To: <201302111118.r1BBIsFH064359@mech-cluster241.men.bris.ac.uk> References: <201302111118.r1BBIsFH064359@mech-cluster241.men.bris.ac.uk> Date: Mon, 11 Feb 2013 12:24:25 +0100 X-Google-Sender-Auth: P8asst1MdMAs7ch0STvZ2OanLO0 Message-ID: Subject: Re: on amd64 r246552: iwn0: : fatal firmware error From: CeDeROM To: mexas@bristol.ac.uk Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 11:24:26 -0000 On Mon, Feb 11, 2013 at 12:18 PM, Anton Shterenlikht wrote: > Yes, I can reproduce this on amd64 -current. > I had to flip the switch twice to cause this: > (..) > However, in my earlier report I got to this > error with no flipping the switch at all. Uhm, on some networks I also very often get information in the dmesg that "wlan0: link state changed to DOWN" and then "wlan0: link state changed to DOWN", maybe this produce issues similar to radio flip switch..? -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 13:15:27 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 59FCC8D0; Mon, 11 Feb 2013 13:15:27 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 03BEE862; Mon, 11 Feb 2013 13:15:26 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirj.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1U4tED-0005FN-9u; Mon, 11 Feb 2013 13:15:25 +0000 Received: from eduroam-222-082.nomadic.bris.ac.uk ([172.21.222.82] helo=zzz) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1U4tEC-0001sp-O5; Mon, 11 Feb 2013 13:15:24 +0000 Received: from zzz (localhost [127.0.0.1]) by zzz (8.14.6/8.14.6) with ESMTP id r1BDFNxw003365; Mon, 11 Feb 2013 13:15:24 GMT (envelope-from mexas@zzz) Received: (from mexas@localhost) by zzz (8.14.6/8.14.6/Submit) id r1BAfVcO018369; Mon, 11 Feb 2013 10:41:31 GMT (envelope-from mexas) Date: Mon, 11 Feb 2013 10:41:31 GMT From: Anton Shterenlikht Message-Id: <201302111041.r1BAfVcO018369@zzz> To: freebsd-questions@freebsd.org, paranormal@isgroup.com.ua Subject: Re: which X driver for NVIDIA Quadro FX 570M? In-Reply-To: <1360113820.90099.11.camel@eva02> Cc: freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:15:27 -0000 From: paranormal Subject: Re: which X driver for NVIDIA Quadro FX 570M? To: freebsd-questions@freebsd.org Date: Wed, 06 Feb 2013 03:23:40 +0200 I have t61p with mentioned card. x11/nvidia-driver works well for me (at least quake, doom, compiz work). Thanks for all the replies. I bought a T61p for 220 GBP - what bliss! BIOS update - no problem HEAD r246552 - no problem wireless with iwn0: - no problem sound with hdac0: - no problem CD-RW with cd0: Removable CD-ROM SCSI-0 device and sysutils/cdrtools-devel - no problem X with nvidia0: and x11/nvidia-driver - no problem flash as per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html (7.2.1.2 Firefox and Adobe Flash Plugin) - no problem In fact, no problems at all! I can't recommend it enough. Anton From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 13:31:16 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7FB31F21; Mon, 11 Feb 2013 13:31:16 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 07A9794E; Mon, 11 Feb 2013 13:31:15 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id r1BDUxmV024593; Tue, 12 Feb 2013 00:30:59 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 12 Feb 2013 00:30:59 +1100 (EST) From: Ian Smith To: Anton Shterenlikht Subject: Re: which X driver for NVIDIA Quadro FX 570M? In-Reply-To: <201302111041.r1BAfVcO018369@zzz> Message-ID: <20130212002934.R71572@sola.nimnet.asn.au> References: <201302111041.r1BAfVcO018369@zzz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: paranormal@isgroup.com.ua, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:31:16 -0000 On Mon, 11 Feb 2013 10:41:31 GMT, Anton Shterenlikht wrote: > From: paranormal > Subject: Re: which X driver for NVIDIA Quadro FX 570M? > To: freebsd-questions@freebsd.org > Date: Wed, 06 Feb 2013 03:23:40 +0200 > > I have t61p with mentioned card. > x11/nvidia-driver works well for me (at least quake, doom, compiz work). > > Thanks for all the replies. > > I bought a T61p for 220 GBP - what bliss! > > BIOS update - no problem > HEAD r246552 - no problem > wireless with iwn0: - no problem > sound with hdac0: - no problem > CD-RW with cd0: Removable CD-ROM SCSI-0 device > and sysutils/cdrtools-devel - no problem > X with nvidia0: and x11/nvidia-driver - no problem > flash as per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html > (7.2.1.2 Firefox and Adobe Flash Plugin) - no problem > > In fact, no problems at all! > > I can't recommend it enough. > > Anton Suspend and resume? cheers, Ian From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 13:53:33 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A50BD5C9; Mon, 11 Feb 2013 13:53:33 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id 603FB175; Mon, 11 Feb 2013 13:53:33 +0000 (UTC) Received: from r56.edvax.de (port-92-195-74-250.dynamic.qsc.de [92.195.74.250]) by mx01.qsc.de (Postfix) with ESMTP id 2AA243D28A; Mon, 11 Feb 2013 14:53:25 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id r1BDrSUj002196; Mon, 11 Feb 2013 14:53:28 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Mon, 11 Feb 2013 14:53:28 +0100 From: Polytropon To: Ian Smith Subject: Re: which X driver for NVIDIA Quadro FX 570M? Message-Id: <20130211145328.3537d061.freebsd@edvax.de> In-Reply-To: <20130212002934.R71572@sola.nimnet.asn.au> References: <201302111041.r1BAfVcO018369@zzz> <20130212002934.R71572@sola.nimnet.asn.au> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: paranormal@isgroup.com.ua, Anton Shterenlikht , freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Polytropon List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 13:53:33 -0000 On Tue, 12 Feb 2013 00:30:59 +1100 (EST), Ian Smith wrote: > On Mon, 11 Feb 2013 10:41:31 GMT, Anton Shterenlikht wrote: > > From: paranormal > > Subject: Re: which X driver for NVIDIA Quadro FX 570M? > > To: freebsd-questions@freebsd.org > > Date: Wed, 06 Feb 2013 03:23:40 +0200 > > > > I have t61p with mentioned card. > > x11/nvidia-driver works well for me (at least quake, doom, compiz work). > > > > Thanks for all the replies. > > > > I bought a T61p for 220 GBP - what bliss! > > > > BIOS update - no problem > > HEAD r246552 - no problem > > wireless with iwn0: - no problem > > sound with hdac0: - no problem > > CD-RW with cd0: Removable CD-ROM SCSI-0 device > > and sysutils/cdrtools-devel - no problem > > X with nvidia0: and x11/nvidia-driver - no problem > > flash as per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html > > (7.2.1.2 Firefox and Adobe Flash Plugin) - no problem > > > > In fact, no problems at all! > > > > I can't recommend it enough. > > > > Anton > > Suspend and resume? I'd be interested in that, too (to possibly transform this knowledge to the T60p I have). And docking station support (if you have it)? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 14:28:33 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 07DDC637; Mon, 11 Feb 2013 14:28:33 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 9FE8636C; Mon, 11 Feb 2013 14:28:32 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirj.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1U4uMx-00029t-DU; Mon, 11 Feb 2013 14:28:31 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1U4uMw-0007J7-Lb; Mon, 11 Feb 2013 14:28:30 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6) with ESMTP id r1BESUfW064918; Mon, 11 Feb 2013 14:28:30 GMT (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6/Submit) id r1BESU0Y064917; Mon, 11 Feb 2013 14:28:30 GMT (envelope-from mexas) Date: Mon, 11 Feb 2013 14:28:30 GMT From: Anton Shterenlikht Message-Id: <201302111428.r1BESU0Y064917@mech-cluster241.men.bris.ac.uk> To: mexas@bristol.ac.uk, smithi@nimnet.asn.au Subject: Re: which X driver for NVIDIA Quadro FX 570M? In-Reply-To: <20130212002934.R71572@sola.nimnet.asn.au> Cc: paranormal@isgroup.com.ua, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 14:28:33 -0000 From smithi@nimnet.asn.au Mon Feb 11 13:49:38 2013 On Mon, 11 Feb 2013 10:41:31 GMT, Anton Shterenlikht wrote: > From: paranormal > Subject: Re: which X driver for NVIDIA Quadro FX 570M? > To: freebsd-questions@freebsd.org > Date: Wed, 06 Feb 2013 03:23:40 +0200 > > I have t61p with mentioned card. > x11/nvidia-driver works well for me (at least quake, doom, compiz work). > > Thanks for all the replies. > > I bought a T61p for 220 GBP - what bliss! > > BIOS update - no problem > HEAD r246552 - no problem > wireless with iwn0: - no problem > sound with hdac0: - no problem > CD-RW with cd0: Removable CD-ROM SCSI-0 device > and sysutils/cdrtools-devel - no problem > X with nvidia0: and x11/nvidia-driver - no problem > flash as per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html > (7.2.1.2 Firefox and Adobe Flash Plugin) - no problem > > In fact, no problems at all! > > I can't recommend it enough. > > Anton Suspend and resume? I guess no... However, I'm very ignorant of suspend/resume, so not sure I'm doing the right thing. - the T61p manual details "standby" and "hibernation" modes. Is this what you refer to by suspend? I can go into standby with Fn+F4, or with "acpiconf -s 3" but can't seem to get back. The disk starts, but the screen is corrupted, kind of black with very few white dots. I have to power off/on. The Fn+F12, hibernation mode code, does not seem to do anything. - I've had a quick look at acpi(4) and apm(8). I have: hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.s4bios: 0 - Anything I should check/test in BIOS? I see that power management is enabled in BIOS. Is that enough? Anton From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 15:19:51 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E224DC2E; Mon, 11 Feb 2013 15:19:51 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id 9C63B89A; Mon, 11 Feb 2013 15:19:51 +0000 (UTC) Received: from r56.edvax.de (port-92-195-74-250.dynamic.qsc.de [92.195.74.250]) by mx01.qsc.de (Postfix) with ESMTP id 4127B3D111; Mon, 11 Feb 2013 16:19:49 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id r1BFJqOg002838; Mon, 11 Feb 2013 16:19:52 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Mon, 11 Feb 2013 16:19:52 +0100 From: Polytropon To: mexas@bristol.ac.uk Subject: Re: which X driver for NVIDIA Quadro FX 570M? Message-Id: <20130211161952.0fa7f717.freebsd@edvax.de> In-Reply-To: <201302111428.r1BESU0Y064917@mech-cluster241.men.bris.ac.uk> References: <20130212002934.R71572@sola.nimnet.asn.au> <201302111428.r1BESU0Y064917@mech-cluster241.men.bris.ac.uk> Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: paranormal@isgroup.com.ua, freebsd-mobile@freebsd.org, smithi@nimnet.asn.au, freebsd-questions@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Polytropon List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 15:19:52 -0000 On Mon, 11 Feb 2013 14:28:30 GMT, Anton Shterenlikht wrote: > I guess no... However, I'm very ignorant of suspend/resume, > so not sure I'm doing the right thing. For those who use the laptop in "transportable mode" (i. e. not on the desktop as a desktop-PC substitute), those features might be interesting in order to save power. > - the T61p manual details "standby" and "hibernation" modes. > Is this what you refer to by suspend? Both are _different_ kinds, if I remember correctly. Standby stores machine states in RAM and buffers it with the battery power. This mode still requires power. This is ACPI states S2 and S3. Hibernate stores machine data somewhere on hard disk or SSD. This mode does not require power. This is ACPI state S4. > I can go into standby with Fn+F4, or with "acpiconf -s 3" > but can't seem to get back. The disk starts, but the > screen is corrupted, kind of black with very few white dots. That seems to indicate that the GPU memory data is lost. A typical problem with those sleep states. > - I've had a quick look at acpi(4) and apm(8). APM is not in use anymore. ACPI has taken that functionality at the point in time when APM has been brought to a fully functional state. > I have: > > hw.acpi.supported_sleep_state: S3 S4 S5 > hw.acpi.s4bios: 0 >From http://static.usenix.org/event/usenix02/tech/freenix/full_papers/watanabe/watanabe_html/node6.html you can see: S3: sleep states. In these states, memory contexts are held but CPU contexts are lost. The differences between S2 and S3 are in CPU re-initialization done by firmware and device re-initialization. S4: a sleep state in which contexts are saved to disk. The context will be restored upon the return to S0. This is identical to soft-off for hardware. This state can be implemented by either OS or firmware. S5: the soft-off state. All activity will stop and all contexts are lost. > - Anything I should check/test in BIOS? The obvious things, but I assume the presets are already fine for a laptop. > I see that power management is enabled in BIOS. > Is that enough? It should be. Note that PM can also include things like spinning down disks or reducing CPU power. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 16:44:47 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4E462AA4; Mon, 11 Feb 2013 16:44:47 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id A4786E18; Mon, 11 Feb 2013 16:44:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id r1BGia1F032800; Tue, 12 Feb 2013 03:44:37 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 12 Feb 2013 03:44:36 +1100 (EST) From: Ian Smith To: Anton Shterenlikht Subject: Re: which X driver for NVIDIA Quadro FX 570M? In-Reply-To: <201302111428.r1BESU0Y064917@mech-cluster241.men.bris.ac.uk> Message-ID: <20130212022810.H71572@sola.nimnet.asn.au> References: <201302111428.r1BESU0Y064917@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: paranormal@isgroup.com.ua, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 16:44:47 -0000 On Mon, 11 Feb 2013 14:28:30 GMT, Anton Shterenlikht wrote: > From smithi@nimnet.asn.au Mon Feb 11 13:49:38 2013 > > On Mon, 11 Feb 2013 10:41:31 GMT, Anton Shterenlikht wrote: > > From: paranormal > > Subject: Re: which X driver for NVIDIA Quadro FX 570M? > > To: freebsd-questions@freebsd.org > > Date: Wed, 06 Feb 2013 03:23:40 +0200 > > > > I have t61p with mentioned card. > > x11/nvidia-driver works well for me (at least quake, doom, compiz work). > > > > Thanks for all the replies. > > > > I bought a T61p for 220 GBP - what bliss! > > > > BIOS update - no problem > > HEAD r246552 - no problem > > wireless with iwn0: - no problem > > sound with hdac0: - no problem > > CD-RW with cd0: Removable CD-ROM SCSI-0 device > > and sysutils/cdrtools-devel - no problem > > X with nvidia0: and x11/nvidia-driver - no problem > > flash as per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html > > (7.2.1.2 Firefox and Adobe Flash Plugin) - no problem > > > > In fact, no problems at all! > > > > I can't recommend it enough. > > > > Anton > > Suspend and resume? > > I guess no... However, I'm very ignorant of suspend/resume, > so not sure I'm doing the right thing. > > - the T61p manual details "standby" and "hibernation" modes. > Is this what you refer to by suspend? > I can go into standby with Fn+F4, or with "acpiconf -s 3" Ok, state S3 is what we call suspend, more precisely suspend to RAM (STR); windows and so most BIOSes call that state standby. > but can't seem to get back. The disk starts, but the > screen is corrupted, kind of black with very few white dots. > I have to power off/on. A common enough tale these days. I try to remain hopeful someone will get a more modern Thinkpad than the T43s (reportedly) or my older T23s (certainly) resuming in one unbroken piece every time again, one day .. > The Fn+F12, hibernation mode code, does not seem to > do anything. > > - I've had a quick look at acpi(4) and apm(8). > I have: > > hw.acpi.supported_sleep_state: S3 S4 S5 > hw.acpi.s4bios: 0 S3 is suspend to RAM; S4 suspend to disk (STD, unsupported by FreeBSD); S5 is power off, should work but may bypass some shutdown(8) processing. S4, STD - 'hibernation' - has two varieties; with s4bios the BIOS itself writes machine state and all RAM to disk, usually a preallocated file in an msdosfs slice. I haven't heard of any new boxes supporting this in BIOS for years; windows (since ~'95) and Linux (I'm told) support STD. > - Anything I should check/test in BIOS? > I see that power management is enabled in BIOS. > Is that enough? It should be, but doesn't seem to work on many. When it resumes with messed up screen, can you ping it, or maybe ssh in, or is it dead? If you boot it but don't start X, can it come back from suspend? Frankly, unless you're _really_ keen to get STR working, this could turn into not just a rabbithole, but the whole warren - you'll have to really want to be the bunny! Sounds like a very nice machine otherwise :) cheers, Ian From owner-freebsd-mobile@FreeBSD.ORG Mon Feb 11 22:44:24 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7D5992DE; Mon, 11 Feb 2013 22:44:24 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA362EA; Mon, 11 Feb 2013 22:44:23 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirg.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1U526j-0006M6-EN; Mon, 11 Feb 2013 22:44:17 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1U526i-0003g1-8x; Mon, 11 Feb 2013 22:44:16 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6) with ESMTP id r1BMiF5n089954; Mon, 11 Feb 2013 22:44:15 GMT (envelope-from mexas@mech-cluster241.men.bris.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.6/8.14.6/Submit) id r1BMiFNL089953; Mon, 11 Feb 2013 22:44:15 GMT (envelope-from mexas) Date: Mon, 11 Feb 2013 22:44:15 GMT From: Anton Shterenlikht Message-Id: <201302112244.r1BMiFNL089953@mech-cluster241.men.bris.ac.uk> To: mexas@bristol.ac.uk, smithi@nimnet.asn.au Subject: Re: which X driver for NVIDIA Quadro FX 570M? In-Reply-To: <20130212022810.H71572@sola.nimnet.asn.au> Cc: paranormal@isgroup.com.ua, freebsd-questions@freebsd.org, freebsd-mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mexas@bristol.ac.uk List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Feb 2013 22:44:24 -0000 From smithi@nimnet.asn.au Mon Feb 11 16:59:49 2013 On Mon, 11 Feb 2013 14:28:30 GMT, Anton Shterenlikht wrote: > From smithi@nimnet.asn.au Mon Feb 11 13:49:38 2013 > > On Mon, 11 Feb 2013 10:41:31 GMT, Anton Shterenlikht wrote: > > From: paranormal > > Subject: Re: which X driver for NVIDIA Quadro FX 570M? > > To: freebsd-questions@freebsd.org > > Date: Wed, 06 Feb 2013 03:23:40 +0200 > > > > I have t61p with mentioned card. > > x11/nvidia-driver works well for me (at least quake, doom, compiz work). > > > > Thanks for all the replies. > > > > I bought a T61p for 220 GBP - what bliss! > > > > BIOS update - no problem > > HEAD r246552 - no problem > > wireless with iwn0: - no problem > > sound with hdac0: - no problem > > CD-RW with cd0: Removable CD-ROM SCSI-0 device > > and sysutils/cdrtools-devel - no problem > > X with nvidia0: and x11/nvidia-driver - no problem > > flash as per http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html > > (7.2.1.2 Firefox and Adobe Flash Plugin) - no problem > > > > In fact, no problems at all! > > > > I can't recommend it enough. > > > > Anton > > Suspend and resume? > > I guess no... However, I'm very ignorant of suspend/resume, > so not sure I'm doing the right thing. > > - the T61p manual details "standby" and "hibernation" modes. > Is this what you refer to by suspend? > I can go into standby with Fn+F4, or with "acpiconf -s 3" Ok, state S3 is what we call suspend, more precisely suspend to RAM (STR); windows and so most BIOSes call that state standby. > but can't seem to get back. The disk starts, but the > screen is corrupted, kind of black with very few white dots. > I have to power off/on. A common enough tale these days. I try to remain hopeful someone will get a more modern Thinkpad than the T43s (reportedly) or my older T23s (certainly) resuming in one unbroken piece every time again, one day .. > The Fn+F12, hibernation mode code, does not seem to > do anything. > > - I've had a quick look at acpi(4) and apm(8). > I have: > > hw.acpi.supported_sleep_state: S3 S4 S5 > hw.acpi.s4bios: 0 S3 is suspend to RAM; S4 suspend to disk (STD, unsupported by FreeBSD); S5 is power off, should work but may bypass some shutdown(8) processing. S4, STD - 'hibernation' - has two varieties; with s4bios the BIOS itself writes machine state and all RAM to disk, usually a preallocated file in an msdosfs slice. I haven't heard of any new boxes supporting this in BIOS for years; windows (since ~'95) and Linux (I'm told) support STD. > - Anything I should check/test in BIOS? > I see that power management is enabled in BIOS. > Is that enough? It should be, but doesn't seem to work on many. When it resumes with messed up screen, can you ping it, or maybe ssh in, or is it dead? yes, I thought of this, but haven't checked yet. I haven't got a static IP allocated yet, and I somehow can never ssh into a box with DHCP allocated address. If you boot it but don't start X, can it come back from suspend? no, with or without X - same result. Frankly, unless you're _really_ keen to get STR working, this could turn into not just a rabbithole, but the whole warren - you'll have to really want to be the bunny! no, certainly not for me. I'm all for helping committers with testing patches and such, but for me suspend/resume is not really an issue. Sounds like a very nice machine otherwise :) yes, it's definitely better than HP Compaq 6715s I used before. cheers, Ian Thanks Anton From owner-freebsd-mobile@FreeBSD.ORG Fri Feb 15 07:22:26 2013 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D2037B3A for ; Fri, 15 Feb 2013 07:22:26 +0000 (UTC) (envelope-from enzo@itatiaia.net) Received: from mail.waimax.net (mail.waimax.net [187.115.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 8CACF835 for ; Fri, 15 Feb 2013 07:22:25 +0000 (UTC) Received: from mail.waimax.net (localhost [127.0.0.1]) by mail.waimax.net (Postfix) with ESMTP id D727D485EEA for ; Fri, 15 Feb 2013 05:14:46 -0200 (BRST) Received: from Reloaded-PC (unknown [41.82.175.146]) by mail.waimax.net (Postfix) with ESMTPA id 8C8924851CD for ; Fri, 15 Feb 2013 05:14:45 -0200 (BRST) Date: Fri, 15 Feb 2013 07:22:11 GMT Mime-version: 1.0 Subject: Can we be friends? From: Rachie Hunters To: Freebsd-mobile Message-Id: <215722.VTMFHXKR@itatiaia.net> X-Mailer: MBM 5.7.1-US Original-recipient: rfc822;freebsd-mobile@freebsd.org Content-type: text/plain; charset="ISO-8859-1"; format=flowed Content-transfer-encoding: quoted-printable X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: rachie87ar@rediffmail.com List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2013 07:22:26 -0000 Hi; Rachael is my name, I will like to be your friend. I will tell you more about me and send you my photo, as soon as you tell me= little about you. I believe distance,age,sex and race does not matter to me, but care, honest= y and respect. I will be waiting for your mail. Have a nice time. Rachie