From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 15 04:03:05 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 580AB10656BA for ; Sun, 15 Mar 2009 04:03:05 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id D17168FC0A for ; Sun, 15 Mar 2009 04:03:04 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LihYz-00037o-P8 for freebsd-hardware@freebsd.org; Sun, 15 Mar 2009 04:03:01 +0000 Received: from 201.170.58.90 ([201.170.58.90]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Mar 2009 04:03:01 +0000 Received: from gamaral by 201.170.58.90 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Mar 2009 04:03:01 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Guillermo Antonio Amaral Bastidas Date: Sat, 14 Mar 2009 20:02:49 -0800 Organization: gamaral Lines: 32 Message-ID: <867i2r302e.fsf@daedalus.amaral.com.mx> References: <1237011798.00086627.1237000202@10.7.7.3> <49BB767C.4040701@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 201.170.58.90 OpenPGP: id=76FE7D5A; url=http://dl.guillermoamaral.com/public.asc Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAgMAAAAqbBEUAAAADFBMVEUAAQD O34n12NX///+rPyiWAAAAlklEQVQoz2P4jwQYaMv5w8Bgw4yVc4ABCJixcD4w 4OKA2RoM/Ng4TKuaVhDB0Vq1agUDAwbnA1AVEDRg5axgamACmYDB0Vqh1dSEl QM0oGkVbk4DVg7QLVpYOSB1DTCHInMCQO5ZIcIaj8b5GhoawqDB1CAaGkqAE+ rAwMAIpOJROaEgkMGgCaKwcMJfTcXF+QskvqJyACeIOObMWMUAAAAAAElFTkS uQmCC X-Face: U-N6j@c-%I&pS%x|oz,K@6(4U`)GhIMhqdii7+l~I.L8kN*gCxTh#D%CH #9#=@xCGn4u{%#K'U8ITAd)3]?.X3FhtEql|P4M+Wck[]dNeuMr$\DYi;S2mg xNmd+![ User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) Cancel-Lock: sha1:TO7u5rjA6yYhsOU3I9/IboPTIQU= Sender: news Subject: Re: Getting jack automute working in M1330 + SND_HDA + 7.1-p3 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Mar 2009 04:03:05 -0000 Alexander Motin writes: > Hi. > > Guillermo Antonio Amaral Bastidas wrote: >> My GF keeps bugging me because I can't mute the internal speakers in >> my Dell M1330 and she doesn't dig the sweet sweet sounds of heavy >> metal ( not at 2 AM anyway ), I have tried many hints to try and get >> it working but I think the examples found on the interwebs are a bit >> dated or my install might be I'm really not sure compared to what I >> get back from the snd_hda driver in my install. >> >> It would be wonderfull if I could get jack sense working but just >> muting the speakers will do for now. >> >> * uname -a: >> >> FreeBSD localhost 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #0: Wed Mar >> 11 12:33:44 PST 2009 root@localhost:/usr/obj/usr/src/sys/GENERIC >> i386 > > Update your system to recent 7-STABLE. New snd_hda driver imported > there is much more suitable in this and many other aspects. Read > updated man page if any questions. SWEET! Thanks :D Will Try -- Guillermo Antonio Amaral Bastidas (gamaral) Free/Libre/Open-Source Software Developer : http://www.guillermoamaral.com/ KDE Developer & KDE e.V. Member : http://www.kde.org/ GPG Fingerprint: E068 811D 4AA2 7FDA A327 38BD 640D 014C 76FE 7D5A From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 15 06:28:28 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A8C7106566B for ; Sun, 15 Mar 2009 06:28:28 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 94C4D8FC08 for ; Sun, 15 Mar 2009 06:28:27 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Lijph-0007xi-UA for freebsd-hardware@freebsd.org; Sun, 15 Mar 2009 06:28:25 +0000 Received: from 201.170.58.90 ([201.170.58.90]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Mar 2009 06:28:25 +0000 Received: from gamaral by 201.170.58.90 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Mar 2009 06:28:25 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Guillermo Antonio Amaral Bastidas Date: Sat, 14 Mar 2009 22:28:11 -0800 Organization: gamaral Lines: 34 Message-ID: <864oxv47wk.fsf@daedalus.amaral.com.mx> References: <1237011798.00086627.1237000202@10.7.7.3> <49BB767C.4040701@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 201.170.58.90 OpenPGP: id=76FE7D5A; url=http://dl.guillermoamaral.com/public.asc Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAgMAAAAqbBEUAAAADFBMVEUAAQD O34n12NX///+rPyiWAAAAlklEQVQoz2P4jwQYaMv5w8Bgw4yVc4ABCJixcD4w 4OKA2RoM/Ng4TKuaVhDB0Vq1agUDAwbnA1AVEDRg5axgamACmYDB0Vqh1dSEl QM0oGkVbk4DVg7QLVpYOSB1DTCHInMCQO5ZIcIaj8b5GhoawqDB1CAaGkqAE+ rAwMAIpOJROaEgkMGgCaKwcMJfTcXF+QskvqJyACeIOObMWMUAAAAAAElFTkS uQmCC X-Face: U-N6j@c-%I&pS%x|oz,K@6(4U`)GhIMhqdii7+l~I.L8kN*gCxTh#D%CH #9#=@xCGn4u{%#K'U8ITAd)3]?.X3FhtEql|P4M+Wck[]dNeuMr$\DYi;S2mg xNmd+![ User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) Cancel-Lock: sha1:xCdy0MwclLl2ZaAwNO3ZRdmw1rE= Sender: news Subject: Re: Getting jack automute working in M1330 + SND_HDA + 7.1-p3 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Mar 2009 06:28:28 -0000 Alexander Motin writes: > Hi. > > Guillermo Antonio Amaral Bastidas wrote: >> My GF keeps bugging me because I can't mute the internal speakers in >> my Dell M1330 and she doesn't dig the sweet sweet sounds of heavy >> metal ( not at 2 AM anyway ), I have tried many hints to try and get >> it working but I think the examples found on the interwebs are a bit >> dated or my install might be I'm really not sure compared to what I >> get back from the snd_hda driver in my install. >> >> It would be wonderfull if I could get jack sense working but just >> muting the speakers will do for now. >> >> * uname -a: >> >> FreeBSD localhost 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #0: Wed Mar >> 11 12:33:44 PST 2009 root@localhost:/usr/obj/usr/src/sys/GENERIC >> i386 > > Update your system to recent 7-STABLE. New snd_hda driver imported > there is much more suitable in this and many other aspects. Read > updated man page if any questions. Oh I must have done something wrong, it seems by trying to update to 7-STABLE I actually downgraded my system some how. Could be cuz I was running 7.1 p3 before. oh my now I need to try and upgrade again. -- Guillermo Antonio Amaral Bastidas (gamaral) Free/Libre/Open-Source Software Developer : http://www.guillermoamaral.com/ KDE Cheese Nacho : http://www.kde.org/ GPG Fingerprint: E068 811D 4AA2 7FDA A327 38BD 640D 014C 76FE 7D5A From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 15 20:01:24 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86BFA106566C for ; Sun, 15 Mar 2009 20:01:24 +0000 (UTC) (envelope-from alaric@metrocast.net) Received: from proofpoint3.metrocast.net (proofpoint3.metrocast.net [65.175.128.159]) by mx1.freebsd.org (Postfix) with ESMTP id 3EDC68FC1F for ; Sun, 15 Mar 2009 20:01:24 +0000 (UTC) (envelope-from alaric@metrocast.net) Received: from [10.24.32.10] (babcom.com [216.246.132.90]) by proofpoint3.metrocast.net (8.13.8/8.13.8) with ESMTP id n2FJhtpv023764 for ; Sun, 15 Mar 2009 19:43:56 GMT Message-ID: <49BD5A7B.9040405@metrocast.net> Date: Sun, 15 Mar 2009 15:43:55 -0400 From: Phil Stracchino Organization: Babylon Communications User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Proofpoint-Virus-Version: vendor=fsecure engine=4.65.7400:2.4.4, 1.2.40, 4.0.164 definitions=2009-03-15_02:2009-03-13, 2009-03-15, 2009-03-15 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=3.1.0-0810130000 definitions=main-0903150129 Subject: Boot failure, 7.1R-amd64 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Mar 2009 20:01:24 -0000 I wish to report, and seek advice on, a 7.1R-amd64 boot failure on a machine that should be perfectly capable of running it. I have a 3U storage box here with two Intel Xeon 3.2GHz CPUs (0xf41; I believe they're Irwindales, NetBurst microarchitecture with amd64 support) on a Tyan Tiger i7320R-S5350 board with 4GB of RAM. Boot is a mirrored (with gmirror) pair of Seagate ST980811AS 2.5" SATA disks. Main storage is twelve Maxtor 300GB SATA disks on a 3Ware 9500S-12 SATA-RAID controller, exported in JBOD mode. I've just updated the system BIOS to the latest S5350-108 image. This machine happily runs Solaris 10 x86. It happily runs OpenBSD 4.4 amd64. It runs FreeBSD 7.1R-i386, as long as it is booted without acpi. FreeBSD babylon4.babcom.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 (still running generic kernel at this time, as you can see) However, it will not boot FreeBSD 7.1R-amd64, although all reason says it should. Booted from 7.1R-amd64 cd1 with ACPI enabled, it gets as far as: ... vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 uhub3: on uhub0 uhub3: 4 ports with 4 removable, self powered Timecounters tick every 1.000 msec md0: Preloaded image 4194034 bytes at 0xffffffff80c4be40 ad0: 76319MB at ata0-master SATA150 ad1: 76319MB at ata0-slave SATA150 ...at which point it hangs. With acpi disabled: ... vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 uhub3: on uhub0 uhub3: 4 ports with 4 removable, self powered Timecounter "TSC" frequency 3192019456 Hz quality 800 Timecounters tick every 1.000 msec md0: Preloaded image 4194034 bytes at 0xffffffff80c4be40 Trying to mount root from ufs:/dev/md0 ...and hang. Verbose logging adds the following additional information at the hang point: ... uhub3: 4 ports with 4 removable, self powered Device configuration finished. Reducing kern.maxvnodes 235635 -> 100000 procfs registered lapic: Divisor 2, frequency 99750485 Hz Timecounter "TSC" frequency 3192019456 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached hptrr: no controller detected md0: Preloaded image 4194034 bytes at 0xffffffff80c4be40 (probe12:twa0:0:12:7): error 22 (probe12:twa0:0:12:7): Unretryable error (probe13:twa0:0:13:7): error 22 (probe13:twa0:0:13:7): Unretryable error (probe14:twa0:0:14:7): error 22 (probe14:twa0:0:14:7): Unretryable error (probe15:twa0:0:15:7): error 22 (probe15:twa0:0:15:7): Unretryable error [repeat until probe31] (probe0:twa0:0:0:7): error 22 (probe0:twa0:0:0:7): Unretryable error (probe1:twa0:0:1:7): error 22 (probe1:twa0:0:1:7): Unretryable error ... (probe11:twa0:0:11:7): error 22 (probe11:twa0:0:11:7): Unretryable error [repeat probe0-probe11 sequence 8 times in total [hang] dmesg, booted from onboard 7.1R-i386: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x641d AMD Features=0x20100000 Logical CPUs per core: 2 real memory = 3623288832 (3455 MB) avail memory = 3541639168 (3377 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 24 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) pcib0: pcibus 0 on motherboard pci0: on pcib0 pcib0: unable to route slot 2 INTA pcib0: unable to route slot 3 INTA pcib1: irq 5 at device 2.0 on pci0 pci1: on pcib1 bge0: mem 0xd d100000-0xdd10ffff irq 16 at device 0.0 on pci1 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-F DX, auto bge0: Ethernet address: 00:e0:81:30:de:88 bge0: [ITHREAD] pcib2: irq 5 at device 3.0 on pci0 pci2: on pcib2 bge1: mem 0xd d200000-0xdd20ffff irq 16 at device 0.0 on pci2 miibus1: on bge1 brgphy1: PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-F DX, auto bge1: Ethernet address: 00:e0:81:30:de:89 bge1: [ITHREAD] pcib3: at device 28.0 on pci0 pci3: on pcib3 3ware device driver for 9000 series storage controllers, version: 3.70.05.001 twa0: <3ware 9000 series Storage Controller> port 0x2000-0x20ff mem 0xdd300000-0 xdd3000ff,0xdf800000-0xdfffffff irq 24 at device 3.0 on pci3 twa0: [ITHREAD] twa0: INFO: (0x15: 0x1300): Controller details:: Model 9500S-12, 12 ports, Firmw are FE9X 2.08.00.005, BIOS string not found uhci0: port 0x1400-0x141f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1420-0x143f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered pci0: at device 29.4 (no driver attached) ehci0: mem 0xdd000400-0xdd0007ff irq 23 at de vice 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 4 ports with 4 removable, self powered pcib4: at device 30.0 on pci0 pci4: on pcib4 vgapci0: port 0x3000-0x30ff mem 0xde000000-0xdeffffff,0 xdd400000-0xdd400fff irq 17 at device 3.0 on pci4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0 x376,0x1470-0x147f at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) cpu0 on motherboard p4tcc0: on cpu0 cpu1 on motherboard p4tcc1: on cpu1 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: [FILTER] sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: [FILTER] vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (memory) unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (memory) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) uhub3: on uhub0 uhub3: 4 ports with 4 removable, self powered Timecounters tick every 1.000 msec ad0: 76319MB at ata0-master SATA150 ad1: 76319MB at ata0-slave SATA150 acd0: CDROM at ata1-master UDMA33 GEOM_MIRROR: Device mirror/gm0 launched (2/2). da0 at twa0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 100.000MB/s transfers da0: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da1 at twa0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 100.000MB/s transfers da1: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da2 at twa0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 100.000MB/s transfers da2: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da3 at twa0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 100.000MB/s transfers da3: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da4 at twa0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 100.000MB/s transfers da4: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da5 at twa0 bus 0 target 5 lun 0 da5: Fixed Direct Access SCSI-3 device da5: 100.000MB/s transfers da5: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da6 at twa0 bus 0 target 6 lun 0 da6: Fixed Direct Access SCSI-3 device da6: 100.000MB/s transfers da6: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da7 at twa0 bus 0 target 7 lun 0 da7: Fixed Direct Access SCSI-3 device da7: 100.000MB/s transfers da7: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da8 at twa0 bus 0 target 8 lun 0 da8: Fixed Direct Access SCSI-3 device da8: 100.000MB/s transfers da8: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da9 at twa0 bus 0 target 9 lun 0 da9: Fixed Direct Access SCSI-3 device da9: 100.000MB/s transfers da9: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da10 at twa0 bus 0 target 10 lun 0 da10: Fixed Direct Access SCSI-3 device da10: 100.000MB/s transfers da10: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) da11 at twa0 bus 0 target 11 lun 0 da11: Fixed Direct Access SCSI-3 device da11: 100.000MB/s transfers da11: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C) SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/mirror/gm0s1a This module (opensolaris) contains code covered by the Common Development and Distribution License (CDDL) see http://opensolaris.org/os/licensing/opensolaris_license/ WARNING: ZFS is considered to be an experimental feature in FreeBSD. ZFS filesystem version 6 ZFS storage pool version 6 -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric@caerllewys.net alaric@metrocast.net phil@co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 17 18:31:05 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 552E1106566B for ; Tue, 17 Mar 2009 18:31:05 +0000 (UTC) (envelope-from alaric@caerllewys.net) Received: from prydain.caerllewys.net (babcom.com [216.246.132.90]) by mx1.freebsd.org (Postfix) with ESMTP id 259BF8FC08 for ; Tue, 17 Mar 2009 18:31:04 +0000 (UTC) (envelope-from alaric@caerllewys.net) Received: by prydain.caerllewys.net (Postfix, from userid 1000) id AF035E8186; Tue, 17 Mar 2009 14:12:44 -0400 (EDT) Date: Tue, 17 Mar 2009 14:12:44 -0400 From: Brother Railgun of Reason To: freebsd-hardware@freebsd.org Message-ID: <20090317181244.GA23459@prydain.caerllewys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-ICBM-Targeting: 43.56068N 71.35502W X-PGP-Fingerprint: 2105 C6FC 945D 2A7A 0738 9BB8 D037 CE8E EFA1 3249 X-PGP-Key-FTP-URL: ftp://ftp.babcom.com/pub/pgpkeys/alaric.asc X-PGP-Key-HTTP-URL: http://www.babcom.com/alaric/pgp.html X-UCE-Policy: No unsolicited commercial email is accepted at this site. All senders of UCE will be immediately and permanently blocked. Organization: The Interesting Times Gang User-Agent: Mutt/1.5.10i Subject: Re: Boot failure, 7.1R-amd64 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2009 18:31:06 -0000 Dieter, Yes, my ISP has a badly broken antispam system in place. See if this address works any better. > acpi or apic ? > > With apic disabled, you need > > device atpic > > in your config file. Someone yanked it starting in 7.0 thinking that > amd64 systems would never need it. If apic always worked properly > maybe you wouldn't need it. No, I did mean ACPI, not APIC. Disabling ACPI is necessary even to boot 7.1R-i386. I haven't touched APIC. -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric@caerllewys.net alaric@metrocast.net phil@co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 19 15:21:02 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B82341065676 for ; Thu, 19 Mar 2009 15:21:02 +0000 (UTC) (envelope-from andre@albsmeier.net) Received: from outside.albsmeier.net (outside.albsmeier.net [80.81.31.28]) by mx1.freebsd.org (Postfix) with ESMTP id 275FE8FC1A for ; Thu, 19 Mar 2009 15:21:01 +0000 (UTC) (envelope-from andre@albsmeier.net) Received: from schlappy.albsmeier.net (57.44.166.190.f.p.codetel.net.do [190.166.44.57] (may be forged)) (authenticated bits=128) by outside.albsmeier.net (8.14.2/8.14.3) with ESMTP id n2JF9YSx031409; Thu, 19 Mar 2009 16:09:36 +0100 (CET) (envelope-from andre@albsmeier.net) Received: from schlappy.albsmeier.net (schlappy.albsmeier.net [127.0.0.1]) by schlappy.albsmeier.net (8.14.3/8.14.3) with ESMTP id n2JF9WU2006697; Thu, 19 Mar 2009 16:09:32 +0100 (CET) (envelope-from andre@schlappy.albsmeier.net) Received: (from andre@localhost) by schlappy.albsmeier.net (8.14.3/8.14.3/Submit) id n2JF9WXB006696; Thu, 19 Mar 2009 16:09:32 +0100 (CET) (envelope-from andre) Date: Thu, 19 Mar 2009 16:09:32 +0100 From: Andre Albsmeier To: freebsd-hardware@freebsd.org, won.derick@yahoo.com Message-ID: <20090319150932.GA2174@schlappy.albsmeier.net> References: <800496.48763.qm@web45816.mail.sp1.yahoo.com> <200902141838.n1EIcwQX009259@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200902141838.n1EIcwQX009259@lurza.secnetix.de> X-Echelon: PGP, r00t, Fax, 747, VHF X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Subject: Re: Hardware clock is not SYNC'ed with kernel clock by ntpdate? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Mar 2009 15:21:03 -0000 On Sat, 14-Feb-2009 at 19:38:58 +0100, Oliver Fromme wrote: > Won De Erick wrote: > > ... > > > However, how should I make this automatic, something that will update > > the CMOS clock everytime the kernel clock is syncronized with a NTP > > server? Do I need to make changes on the variables below? > > You seem to misunderstand. The CMOS clock _is_ always > updated when you run ntpd. You do not have to change > anything. Hmm, my experience is different here. I have 17 FreeBSD machines which are all running ntpd (btw, no /etc/wall_cmos_clock). When being rebooted, they sync the time with ntpdate before starting ntpd. Somtimes I noticed the time being stepped by several seconds (up to 50). I observed that the higher the previous uptime had been, the bigger the stepping during the following reboot was. While ntpd keeps the kernel time perfectly in sync with our stratum-1 server the CMOS clocks slowly drift away. The higher the uptime, the bigger the drift. I am now using this ugly hack to sync the kernel time to the CMOS clock (settimeofday() sets both) before reboot and the problem never appeared again: #include #include #include #include int main( void ) { struct timeval tv; if( gettimeofday( &tv, NULL ) != 0 ) err( EX_DATAERR, "gettimeofday" ); if( settimeofday( &tv, NULL ) != 0 ) err( EX_DATAERR, "settimeofday" ); return 0; } A cleaner way might be to call resettodr() in subr_clock.c just before rebooting. If there are easier/cleaner ways to keep CMOS time in sync, I will be happy about any suggestions. -Andre From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 19 17:00:00 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C20F10656E2 for ; Thu, 19 Mar 2009 17:00:00 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C3A408FC20 for ; Thu, 19 Mar 2009 16:59:59 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA10130; Thu, 19 Mar 2009 18:47:55 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <49C2773A.8080801@icyb.net.ua> Date: Thu, 19 Mar 2009 18:47:54 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.19 (X11/20090110) MIME-Version: 1.0 To: Andre Albsmeier , Oliver Fromme References: <800496.48763.qm@web45816.mail.sp1.yahoo.com> <200902141838.n1EIcwQX009259@lurza.secnetix.de> <20090319150932.GA2174@schlappy.albsmeier.net> In-Reply-To: <20090319150932.GA2174@schlappy.albsmeier.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: won.derick@yahoo.com, freebsd-hardware@freebsd.org Subject: Re: Hardware clock is not SYNC'ed with kernel clock by ntpdate? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Mar 2009 17:00:02 -0000 on 19/03/2009 17:09 Andre Albsmeier said the following: > On Sat, 14-Feb-2009 at 19:38:58 +0100, Oliver Fromme wrote: >> Won De Erick wrote: >> >> ... >> >> > However, how should I make this automatic, something that will update >> > the CMOS clock everytime the kernel clock is syncronized with a NTP >> > server? Do I need to make changes on the variables below? >> >> You seem to misunderstand. The CMOS clock _is_ always >> updated when you run ntpd. You do not have to change >> anything. Oliver, if this is not misquoted then you are not correct. Sorry, I noticed this thread too late, so I have to follow up in this fashion. RTC ("CMOS clock") is updated via resettodr function and you can search kernel sources yourself to see how many times and where it called. I reported the problem myself once upon a time: http://lists.freebsd.org/pipermail/freebsd-hackers/2005-August/013383.html > Hmm, my experience is different here. I have 17 FreeBSD machines > which are all running ntpd (btw, no /etc/wall_cmos_clock). When > being rebooted, they sync the time with ntpdate before starting > ntpd. Somtimes I noticed the time being stepped by several seconds > (up to 50). I observed that the higher the previous uptime had been, > the bigger the stepping during the following reboot was. > While ntpd keeps the kernel time perfectly in sync with our > stratum-1 server the CMOS clocks slowly drift away. The higher > the uptime, the bigger the drift. > > I am now using this ugly hack to sync the kernel time to the > CMOS clock (settimeofday() sets both) before reboot and > the problem never appeared again: > > #include > #include > #include > #include > > int main( void ) > { > struct timeval tv; > > if( gettimeofday( &tv, NULL ) != 0 ) > err( EX_DATAERR, "gettimeofday" ); > > if( settimeofday( &tv, NULL ) != 0 ) > err( EX_DATAERR, "settimeofday" ); > > return 0; > } > > > A cleaner way might be to call resettodr() in subr_clock.c > just before rebooting. > > If there are easier/cleaner ways to keep CMOS time in sync, > I will be happy about any suggestions. I think that ideally RTC time should be updated when discrepancy between it and kernel time exceeds certain threshold. Also, we can could have a kernel self-rescheduling callout that would update hardware clock every half an hour (or whatever, configurable). Periodic - because we not always have a graceful shutdown (crashes, power loss, etc). For time beng I am using this hack: #save OS clock value to time-of-day register (x86 CMOS) 10 0-2,4-23 * * * /usr/local/sbin/resettodr.sh $ cat /usr/local/sbin/resettodr.sh #!/bin/sh # ATTENTION: run this script only at time when you are sure that no # timezone change (daylight savings time) could possibly occur. # Otherwise you risk race with adjkerntz -e run from /etc/crontab. # Time between 06:00 and 23:59 should be safe. trigger_sysctl_name="machdep.adjkerntz" sysctl_command="/sbin/sysctl" $sysctl_command `$sysctl_command -e $trigger_sysctl_name` > /dev/null Calling this at shutdown would be a bonus. -- Andriy Gapon From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 20 00:44:29 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA7DE106564A for ; Fri, 20 Mar 2009 00:44:29 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from n23.bullet.mail.mud.yahoo.com (n23.bullet.mail.mud.yahoo.com [68.142.206.162]) by mx1.freebsd.org (Postfix) with SMTP id 9F7CE8FC17 for ; Fri, 20 Mar 2009 00:44:29 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from [68.142.194.244] by n23.bullet.mail.mud.yahoo.com with NNFMP; 20 Mar 2009 00:44:29 -0000 Received: from [68.142.201.243] by t2.bullet.mud.yahoo.com with NNFMP; 20 Mar 2009 00:44:29 -0000 Received: from [127.0.0.1] by omp404.mail.mud.yahoo.com with NNFMP; 20 Mar 2009 00:44:29 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 19559.75695.bm@omp404.mail.mud.yahoo.com Received: (qmail 2753 invoked by uid 60001); 20 Mar 2009 00:44:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1237509868; bh=qsoOlcyCyzlsxDpDikXAO7K5XF94tu5M/ZkG32knvi0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=WOWsFPiiB0tno/AOGAt/9sKt4rLlZqmuSjcE0FPkqzfCU/UMxVfm79IIjKDG8CGdWwweT5uqH/tklgSYfPkhILhtDv3+fRo6/GyefXRBuRC0/BEKAdBNVIzCe8YyFdJDUFeTdeesoNRMe5mtAVEw2XjDxDtT49ENUvbNqtV9EJ0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=UpnOpFpQgriqCcKlRQUNnbXCBXQZrhyEFOTNwe0H5YHEZEtB5yHrOlkG0hYUkkt2CTKzwfQwLcdHATPYVifE19b6ER4tn7WgnPde4Fx9YP0R6YtB9OMAztjjH8a6yP/AMHS6HtI7KMZscERdrUuZ43YGse5lZPmMw28cRo/G8gA=; Message-ID: <402443.1503.qm@web45812.mail.sp1.yahoo.com> X-YMail-OSG: zvlR2M4VM1mKf0MfExh3r_2GgmcvT6.qKf7q_DLD9E_v2Yj7E9VGnaMkX1yen2BO.Fjh6bGdcIzCHEzkNIZ_NK.J8xxekvQa.GCMMDAglq8GyteppE1vPtj2rkn_iFlIydUfo97uotHxfjMDfUb0mcNRbf8UVlC7jIKaLriwjUGf2PY6H6X9aZkSPbXpAqtqC8wvQrdQsmcAZbqT_Oo3eGXWsospeZtC8rBsjrNHKa.I8JSZohthY_.sfwsi7fRKstQXdt2RFomT1QCUOGgJY3J.fXPSKtw- Received: from [58.71.34.137] by web45812.mail.sp1.yahoo.com via HTTP; Thu, 19 Mar 2009 17:44:27 PDT X-Mailer: YahooMailClassic/5.1.20 YahooMailWebService/0.7.289.1 Date: Thu, 19 Mar 2009 17:44:27 -0700 (PDT) From: Won De Erick To: Andre Albsmeier , Oliver Fromme , Andriy Gapon MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-hardware@freebsd.org Subject: Re: Hardware clock is not SYNC'ed with kernel clock by ntpdate? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 00:44:30 -0000 --- On Thu, 3/19/09, Andriy Gapon wrote: > on 19/03/2009 17:09 Andre Albsmeier said the following: > > On Sat, 14-Feb-2009 at 19:38:58 +0100, Oliver Fromme > > wrote: > >> Won De Erick > >> wrote: > >> > >> ... > >> > >> > However, how should I make this > >> > automatic, something that will update > >> > the CMOS clock everytime the kernel > >> > clock is syncronized with a NTP > >> > server? Do I need to make changes on > >> > the variables below? > >> > >> You seem to misunderstand. The CMOS clock > >> _is_ always > >> updated when you run ntpd. You do not have > >> to change > >> anything. > > Oliver, if this is not misquoted then you are not correct. > Sorry, I noticed this thread too late, so I have to follow > up in this fashion. > RTC ("CMOS clock") is updated via resettodr function and > you can search kernel > sources yourself to see how many times and where it > called. > I reported the problem myself once upon a time: > http://lists.freebsd.org/pipermail/freebsd-hackers/2005-August/013383.html > > > Hmm, my experience is different here. I have 17 > > FreeBSD machines > > which are all running ntpd (btw, no > > /etc/wall_cmos_clock). When > > being rebooted, they sync the time with ntpdate before > > starting > > ntpd. Somtimes I noticed the time being stepped by > > several seconds > > (up to 50). I observed that the higher the previous > > uptime had been, > > the bigger the stepping during the following reboot > > was. > > While ntpd keeps the kernel time perfectly in sync > > with our > > stratum-1 server the CMOS clocks slowly drift away. > > The higher > > the uptime, the bigger the drift. > > > > I am now using this ugly hack to sync the kernel time > > to the > > CMOS clock (settimeofday() sets both) before reboot > > and > > the problem never appeared again: > > > > #include > > #include > > #include > > #include > > > > int main( void ) > > { > > struct timeval tv; > > > > if( gettimeofday( &tv, NULL ) != 0 ) > > err( EX_DATAERR, > > "gettimeofday" ); > > > > if( settimeofday( &tv, NULL ) != 0 ) > > err( EX_DATAERR, > > "settimeofday" ); > > > > return 0; > > } > > > > > > A cleaner way might be to call resettodr() in > > subr_clock.c > > just before rebooting. > > > > If there are easier/cleaner ways to keep CMOS time in > > sync, > > I will be happy about any suggestions. > > I think that ideally RTC time should be updated when > discrepancy between it and > kernel time exceeds certain threshold. > Also, we can could have a kernel self-rescheduling callout > that would update > hardware clock every half an hour (or whatever, > configurable). > Periodic - because we not always have a graceful shutdown > (crashes, power loss, etc). > > For time beng I am using this hack: > #save OS clock value to time-of-day register (x86 CMOS) > 10 0-2,4-23 > * * > * > /usr/local/sbin/resettodr.sh > > $ cat /usr/local/sbin/resettodr.sh > #!/bin/sh > > # ATTENTION: run this script only at time when you are sure > that no > # timezone change (daylight savings time) could possibly > occur. > # Otherwise you risk race with adjkerntz -e run from > /etc/crontab. > # Time between 06:00 and 23:59 should be safe. > > > trigger_sysctl_name="machdep.adjkerntz" > sysctl_command="/sbin/sysctl" > > $sysctl_command `$sysctl_command -e $trigger_sysctl_name` > > /dev/null > > Calling this at shutdown would be a bonus. > > -- > Andriy Gapon > Cool! From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 20 01:51:36 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93E8B106564A for ; Fri, 20 Mar 2009 01:51:36 +0000 (UTC) (envelope-from gmpillai@hotmail.com) Received: from blu0-omc1-s19.blu0.hotmail.com (blu0-omc1-s19.blu0.hotmail.com [65.55.116.30]) by mx1.freebsd.org (Postfix) with ESMTP id 5F44B8FC13 for ; Fri, 20 Mar 2009 01:51:36 +0000 (UTC) (envelope-from gmpillai@hotmail.com) Received: from BLU129-W34 ([65.55.116.8]) by blu0-omc1-s19.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 19 Mar 2009 18:39:35 -0700 Message-ID: X-Originating-IP: [87.194.74.39] From: Mohan Pillai To: Date: Fri, 20 Mar 2009 01:39:34 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 20 Mar 2009 01:39:35.0016 (UTC) FILETIME=[B942D680:01C9A8FC] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: PCI-e wireless cards with Atheros chipsets? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2009 01:51:36 -0000 Hello All=2C I'm basically after a PCI-e wireless card (desktop) with an atheros chipset= which has a connector for an arial? I'm trying to find some using the FreeBSD hardware compatability list=2C bu= t it's proving fairly difficult to find one. I'm unable to use a PCI as all my PCI slots have been taken up and I only h= ave 2 PCI-e slots available. I'd much appreciate any input. Many thanks in advance :) Mo=2C _________________________________________________________________ 25GB of FREE Online Storage =96 Find out more http://clk.atdmt.com/UKM/go/134665320/direct/01/=