From owner-freebsd-hardware@FreeBSD.ORG Sun Feb 15 15:28:40 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 6EC23106566C for ; Sun, 15 Feb 2009 15:28:40 +0000 (UTC) (envelope-from dadans@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 022278FC1D for ; Sun, 15 Feb 2009 15:28:39 +0000 (UTC) (envelope-from dadans@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so185193fgb.35 for ; Sun, 15 Feb 2009 07:28:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=KdqfbjidCAiFRjPwlb4kybycJGp6GpYc+OrEQG38j3I=; b=SZt1i8fwdQuxRK63xG/VC5OTCtV2+AqA9wzf4bTDlnn27jRNdIapYx/+GoqAW9XeGx 6APt1GKqoxD9qvoDVmhJ5IO3RBSFAaoVq3F6lDmUazefjq+vAwjmr7PjpNSG8Q2/L0AQ 7n2gQ8i+/aJ6OikSCgncFzdhzJyhws6P+gubo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ZU8L/OOKrRz1ORJGT5UEItu20V+M5lIfLfkY54WD97wNGKdKq0ZAmifxc7xQs8y1FA 8lA16vxHICKdjjSYD0dE9eHwtZuDtI/whxX+j8T22H7zJ394lLiz1kvx7SU/uZR1U6Ec ijytS9hLAb6kDjDDZcuvFQhjRIk7VDEmeD4cg= MIME-Version: 1.0 Received: by 10.86.3.4 with SMTP id 4mr876555fgc.66.1234710152659; Sun, 15 Feb 2009 07:02:32 -0800 (PST) In-Reply-To: <800496.48763.qm@web45816.mail.sp1.yahoo.com> References: <200902131045.n1DAjtxw031128@lurza.secnetix.de> <800496.48763.qm@web45816.mail.sp1.yahoo.com> Date: Sun, 15 Feb 2009 16:02:32 +0100 Message-ID: From: DadAN To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Sun, 15 Feb 2009 15:28:40 -0000 Hello, > 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 can run it as cron job, for example 1,31 0-5 * * * root adjkerntz -a here is my # sysctl -a machdep machdep.enable_panic_key: 0 machdep.adjkerntz: -3600 machdep.wall_cmos_clock: 1 machdep.disable_rtc_set: 0 machdep.conspeed: 115200 machdep.gdbspeed: 9600 machdep.conrclk: 1843200 machdep.disable_mtrrs: 0 machdep.guessed_bootdev: 2686451712 machdep.cpu_idle_hlt: 1 machdep.hlt_cpus: 0 machdep.prot_fault_translation: 0 machdep.panic_on_nmi: 1 machdep.tsc_freq: 514994590 machdep.i8254_freq: 1193182 machdep.acpi_timer_freq: 3579545 machdep.acpi_root: 1016224 -- DadAN From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 16 01:35:32 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 F34E2106564A for ; Mon, 16 Feb 2009 01:35:31 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from n59.bullet.mail.sp1.yahoo.com (n59.bullet.mail.sp1.yahoo.com [98.136.44.43]) by mx1.freebsd.org (Postfix) with SMTP id CEB7A8FC08 for ; Mon, 16 Feb 2009 01:35:31 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from [216.252.122.219] by n59.bullet.mail.sp1.yahoo.com with NNFMP; 16 Feb 2009 01:35:31 -0000 Received: from [69.147.84.102] by t4.bullet.sp1.yahoo.com with NNFMP; 16 Feb 2009 01:35:31 -0000 Received: from [127.0.0.1] by omp206.mail.sp1.yahoo.com with NNFMP; 16 Feb 2009 01:35:31 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 730166.7086.bm@omp206.mail.sp1.yahoo.com Received: (qmail 95026 invoked by uid 60001); 16 Feb 2009 01:35:31 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=Kx0hgGckJeZ1R0m/ZC9B2Lmt8x3YaiTje4YaAcRxKV70HKmDQ4EMqVjPdRKp7XZ5frJffjnYALCsdfm6mu0cySNgrQGGTCoIWLxotLcrjyN5Xc5/NTUiWLzsuWNhouqp8LbS8F0h/iaJQ22VH/TwGaaQWQDquaVrfx+HuSYvKlY=; X-YMail-OSG: 7jr9osUVM1kwevmHFMsZOWK1BAVWzPV0Fi0ZnMx5Osh95A7MV5WzHpOmkR8z51K85QPmC1nsLJmFgZU_M9MEWWwHJE_MVzBtR7uA5ZyYeCvTCpCamBa8GTqbNMvt6FSUwok1Kc2r9f3oP1oqH2TbqbAW7vBP8rrspZizw8zMDm8jeuiaA_Cpz4jcYhCYXBA- Received: from [58.71.34.137] by web45808.mail.sp1.yahoo.com via HTTP; Sun, 15 Feb 2009 17:35:31 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Sun, 15 Feb 2009 17:35:31 -0800 (PST) From: Won De Erick To: freebsd-hardware@FreeBSD.ORG In-Reply-To: <200902141838.n1EIcwQX009259@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <529764.94153.qm@web45808.mail.sp1.yahoo.com> 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 Reply-To: won.derick@yahoo.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2009 01:35:32 -0000 Thank you very much for the clear explanation. --- On Sat, 2/14/09, Oliver Fromme wrote: > Won De Erick wrote: > > This file /etc/wall_cmos_clock was missing, so I > created an empty one.=20 >=20 > So you _do_ want to run your CMOS clock at local time > instead of UTC? That is only required if you run a > different OS on the same machine (dual-boot), because > Windows expects the CMOS clock to run at local time. >=20 'Not that I want to run at UTC. I wanted to find out how the BMC system eve= nt log (SEL) timestamps are done by the BMC firmware. The IBM x343 box is a= n IPMI v1.5 compliant, and FreeBSD is the only OS installed. I wondered why= I got late datestamps on SEL.=20 > Otherwise, if FreeBSD is the only OS on that machine, > it's better to let the CMOS clock run at UTC (i.e. do > not create /etc/wall_cmos_clock), because it avoids > all the switching back and forth between time zones, > and adjkerntz(8) doesn't have to run all the time. >=20 > As far as ntpd is concerned, it doesn't matter. ntpd > doesn't care about time zones. It always works on UTC > internally and synchronizes the time that way (otherwise > there would be additional complexities using NTP servers > in different time zones). Even the kernel doesn't care > about time zones. Handling time zones is done in the > libc (userland). So, basically, if a program like > date(1) displays the time, it converts UTC to your local > time zone for you. >=20 > > 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? >=20 > You seem to misunderstand. The CMOS clock _is_ always > updated when you run ntpd. You do not have to change > anything. >=20 > The only question is at which time zone the CMOS clock > runs, as I've explained above. >=20 > If your CMOS clock runs at UTC (recommended if FreeBSD > is the only OS on that machine), then the BIOS will > always display a wrong time, because the BIOS doesn't > know your time zone, so it can't convert from UTC to > your time zone. But that's purely a cosmetical issue. > You can ignore that. Your CMOS clock _is_ synchronized > and runs correctly. Only your BIOS doesn't know how > to display it correctly. >=20 This is a cool explanation. This has cleared my assumption that the CMOS cl= ocked is not updated whenever the system is sync'ed with an NTP server. I think this has narrow down the issue. Let me share you the problem that I encountered, which had led me to suspec= t before that CMOS clock was not properly sync'ed. I hope you can give me m= ore hints/explanations for me to come up with a conclusive findings.=20 1. Get the date/time in shell # date Fri Feb 13 14:20:20 PHT 2009 2. Rebooted the box, then entered BIOS config to verify date/time System Time : 06:25:29 # seems correct, it runs at UTC System Date : Fri 02/13/2009 3. Let the system up. 4. Unplugged the power cord to come up with a new event in SEL. I am using = FreeIPMI v0.7.1 to retrieve the logs. 1724:01-Jan-1970 08:00:12:Power Supply Power Supply 2:Presence detected 1744:01-Jan-1970 08:00:12:Power Supply Power Supply 2:Power Supply input lo= st (AC/DC) -------------------> uplug the power. 1764:01-Jan-1970 08:00:12:Power Unit Power Redundancy:Entered from Non-redu= ndant:Insufficient Resources 1784:01-Jan-1970 08:00:41:System Event System Event:Timestamp Clock Synch 1804:12-Feb-2009 14:27:50:System Event System Event:Timestamp Clock Synch 1824:12-Feb-2009 14:28:15:System Event System Event:OEM System Boot Event 1844:12-Feb-2009 14:29:53:System Event System Event:Timestamp Clock Synch 1864:12-Feb-2009 14:29:53:System Event System Event:Timestamp Clock Synch 1884:12-Feb-2009 14:31:55:System Event System Event:OEM System Boot Event -= ------------------> datestamp incorrect Is the datestamp '01-Jan-1970' a sign of a defective CMOS battery? Does the datestamp '12-Feb-2009' being not updated to the correct date (13-= Feb-2009) is a sign of a defective battery too? or other issues like firmwa= re bug? I would be grateful to receive more tips from you. > Best regards > Oliver >=20 > --=20 > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, > 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606,=20 > Gesch=E4ftsfuehrung: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: > Registergericht M=FCn- > chen, HRB 125758, Gesch=E4ftsf=FChrer: Maik Bachmann, Olaf > Erb, Ralf Gebhart >=20 > FreeBSD-Dienstleistungen, -Produkte und mehr:=20 > http://www.secnetix.de/bsd >=20 > "The ITU has offered the IETF formal alignment with > its > corresponding technology, Penguins, but that won't > fly." > -- RFC 2549 > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org"=0A=0A=0A From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 16 14:22: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 9DAFF1065692 for ; Mon, 16 Feb 2009 14:22:05 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: from ibox.insign.ch (ibox.insign.ch [195.134.143.207]) by mx1.freebsd.org (Postfix) with SMTP id E35618FC0C for ; Mon, 16 Feb 2009 14:22:04 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 27271 invoked from network); 16 Feb 2009 14:22:03 -0000 Received: from [192.168.1.170] ([80.254.166.203]) by ibox.insign.ch ([195.134.143.207]) with ESMTP via TCP; 16 Feb 2009 14:22:03 -0000 From: Olivier Mueller To: "Brian A. Seklecki" In-Reply-To: <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> References: <1234363891.15909.35.camel@ompc.insign.local> <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> Content-Type: text/plain Date: Mon, 16 Feb 2009 15:22:02 +0100 Message-Id: <1234794122.22023.76.camel@ompc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy 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: Mon, 16 Feb 2009 14:22:08 -0000 On Wed, 2009-02-11 at 10:38 -0500, Brian A. Seklecki wrote: > There's already discussion about this in the archives. We're aware and > working on it. > > Set: > /boo/loader.conf > kern.cam.scsi_delay=20000 > As a work-around for now. Many thanks for your answer, it fixed the problem for now. Now it looks like that: amr0: mem 0xd80f0000-0xd80fffff,0xdfde0000-0xdfdfffff irq 46 at device 14.0 on pci2 amr0: Using 64-bit DMA amr0: [ITHREAD] amr0: delete logical drives supported by controller amr0: Firmware 521X, BIOS H430, 256MB RAM amr0: delete logical drives supported by controller amrd0: on amr0 amrd0: 69880MB (143114240 sectors) RAID 1 (optimal) ses0 at amr0 bus 0 target 6 lun 0 Trying to mount root from ufs:/dev/amrd0s1a Regards & a nice week to you and the other readers, Olivier From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 16 15:51:33 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 45F6E1065673; Mon, 16 Feb 2009 15:51:33 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from mail.digitalfreaks.org (mail.digitalfreaks.org [216.151.95.156]) by mx1.freebsd.org (Postfix) with ESMTP id CF50D8FC19; Mon, 16 Feb 2009 15:51:32 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: by mail.digitalfreaks.org (Postfix, from userid 1022) id 444FC797821; Mon, 16 Feb 2009 10:51:32 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.digitalfreaks.org (Postfix) with ESMTP id 42DA479781F; Mon, 16 Feb 2009 10:51:32 -0500 (EST) Date: Mon, 16 Feb 2009 10:51:32 -0500 (EST) From: "Brian A. Seklecki" X-X-Sender: lavalamp@vger.digitalfreaks.org To: Olivier Mueller In-Reply-To: <1234794122.22023.76.camel@ompc.insign.local> Message-ID: References: <1234363891.15909.35.camel@ompc.insign.local> <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> <1234794122.22023.76.camel@ompc.insign.local> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: spolyack@gmail.com, freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy 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: Mon, 16 Feb 2009 15:51:34 -0000 > amr0: Firmware 521X, BIOS H430, 256MB RAM > amr0: delete logical drives supported by controller Any time! NOTE: You're using the 4e/Si, which we have as well. We're experiencing random crashes on the 1850/8th gen, as a result of a (believed) DMA bug introduced into 7.x Please let us know if you see kernel panics or unexpected behavior (sig11s) The developer we're working with cannot re-create the problem on the PERC4/Di. ~BAS > amrd0: on amr0 > amrd0: 69880MB (143114240 sectors) RAID 1 (optimal) > ses0 at amr0 bus 0 target 6 lun 0 > Trying to mount root from ufs:/dev/amrd0s1a > > Regards & a nice week to you and the other readers, > Olivier From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 16 17:27:22 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 4FBCD1065675 for ; Mon, 16 Feb 2009 17:27:22 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from mx04.pub.collaborativefusion.com (mx04.pub.collaborativefusion.com [206.210.72.84]) by mx1.freebsd.org (Postfix) with ESMTP id 189DC8FC2B for ; Mon, 16 Feb 2009 17:27:21 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from [192.168.2.164] ([206.210.89.202]) by mx04.pub.collaborativefusion.com (StrongMail Enterprise 4.1.1.4(4.1.1.4-47689)); Mon, 16 Feb 2009 11:38:10 -0500 X-VirtualServerGroup: Default X-MailingID: 00000::00000::00000::00000::::1 X-SMHeaderMap: mid="X-MailingID" X-Destination-ID: freebsd-hardware@freebsd.org X-SMFBL: ZnJlZWJzZC1oYXJkd2FyZUBmcmVlYnNkLm9yZw== Message-ID: <49999672.6020801@comcast.net> Date: Mon, 16 Feb 2009 11:38:10 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: "Brian A. Seklecki" References: <1234363891.15909.35.camel@ompc.insign.local> <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> <1234794122.22023.76.camel@ompc.insign.local> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: spolyack@gmail.com, Olivier Mueller , freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: poweredge 1850 won't boot 7.1? maybe LSI-related : amr0: adapter is busy 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: Mon, 16 Feb 2009 17:27:22 -0000 Brian A. Seklecki wrote: > NOTE: You're using the 4e/Si, which we have as well. We're experiencing > random crashes on the 1850/8th gen, as a result of a (believed) DMA bug > introduced into 7.x > > Just to note, we are only seeing these issues in combination with megarc (/usr/ports/sysutils/megarc) monitoring. From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 16 18:41:18 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 C58B8106567B for ; Mon, 16 Feb 2009 18:41:18 +0000 (UTC) (envelope-from rick@havokmon.com) Received: from mail.vfemail.net (mail.vfemail.net [69.11.239.68]) by mx1.freebsd.org (Postfix) with ESMTP id 73C5E8FC5A for ; Mon, 16 Feb 2009 18:41:17 +0000 (UTC) (envelope-from rick@havokmon.com) Received: (qmail 58812 invoked by uid 0); 16 Feb 2009 18:14:34 -0000 Received: by simscan 1.1.0 ppid: 58805, pid: 58809, t: 0.0107s scanners:none Received: from unknown (HELO ?172.16.100.99?) (cmlja0BoYXZva21vbi5jb20=@NjkuMTEuMjM5LjY2) by mail.vfemail.net with ESMTPA; 16 Feb 2009 18:14:34 -0000 From: Rick Romero To: freebsd-hardware@freebsd.org In-Reply-To: <1234626078.5736.121.camel@rickxp> References: <1234626078.5736.121.camel@rickxp> Content-Type: text/plain; charset=cp1252 Date: Mon, 16 Feb 2009 12:14:12 -0600 Message-Id: <1234808053.5736.157.camel@rickxp> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 8bit Subject: Re: Areca 1200 controller panics 7.1 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: Mon, 16 Feb 2009 18:41:19 -0000 According to: ftp://ftp.areca.com.tw/RaidCards/AP_Drivers/FreeBSD/DRIVER/SourceCode/ There is a driver released 12/10/08. According to SVN for FreeBSD 8.0, the current driver was committed 3 years ago. Unless someone would like to step up and 'pop in' the new version to the current kernel and save me some effort, I will be attempting my first FreeBSD kernel compile after a good 8 years of use. :/ Procedure: 1. Install FreeBSD 7.1 to a system without the Areca 1200 installed. 2. Verify it's still not working after reboot and hardware install. 3. Compile the new kernel with new driver 4. Reboot using new kernel to verify build 5. Reinstall ARC1200 6. Watch what happens. Report back here. Rick > (probe16:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step > arcmsr0: isr get an illegal srb command doneacb=´0xffffffff8124e000´ > srb=0xffff > ffffaeb6c420´ srbacb=´0xffffffff8124e000´ > startdone=0x3c3csrboutstandingcount=-1 > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x34be2988 > fault code = supervisor read data, page not present > instruction pointer = 0x8:0xffffffff807914c3 > stack pointer = 0x10:0xffffffffaecaab60 > frame pointer = 0x10:0xffffffff8124e000 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 36 (irq17: arcmsr0) > trap number = 12 > panic: page fault > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 17 00:53:33 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 B3ADF106566C for ; Tue, 17 Feb 2009 00:53:33 +0000 (UTC) (envelope-from rick@havokmon.com) Received: from mail.vfemail.net (mail.vfemail.net [69.11.239.68]) by mx1.freebsd.org (Postfix) with ESMTP id 4CFAD8FC13 for ; Tue, 17 Feb 2009 00:53:32 +0000 (UTC) (envelope-from rick@havokmon.com) Received: (qmail 74993 invoked by uid 0); 17 Feb 2009 00:53:29 -0000 Received: by simscan 1.1.0 ppid: 74986, pid: 74989, t: 0.1027s scanners:none Received: from unknown (HELO ?172.16.100.99?) (cmlja0BoYXZva21vbi5jb20=@NjkuMTEuMjM5LjY2) by mail.vfemail.net with ESMTPA; 17 Feb 2009 00:53:29 -0000 From: Rick Romero To: freebsd-hardware@freebsd.org In-Reply-To: <1234808053.5736.157.camel@rickxp> References: <1234626078.5736.121.camel@rickxp> <1234808053.5736.157.camel@rickxp> Content-Type: text/plain Date: Mon, 16 Feb 2009 18:53:08 -0600 Message-Id: <1234831988.5736.191.camel@rickxp> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 Content-Transfer-Encoding: 7bit Subject: Re: Areca 1200 controller panics 7.1 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 Feb 2009 00:53:33 -0000 On Mon, 2009-02-16 at 12:14 -0600, Rick Romero wrote: > According to: > ftp://ftp.areca.com.tw/RaidCards/AP_Drivers/FreeBSD/DRIVER/SourceCode/ > > There is a driver released 12/10/08. > > According to SVN for FreeBSD 8.0, the current driver was committed 3 > years ago. False alarm, The latest version in FreeBSD is from 2007, and is numbered higher than the website version. Rick From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 17 16:32:35 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 46F3E1065690 for ; Tue, 17 Feb 2009 16:32:35 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from n54.bullet.mail.sp1.yahoo.com (n54.bullet.mail.sp1.yahoo.com [98.136.44.32]) by mx1.freebsd.org (Postfix) with SMTP id 23ED18FC24 for ; Tue, 17 Feb 2009 16:32:34 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from [69.147.84.145] by n54.bullet.mail.sp1.yahoo.com with NNFMP; 17 Feb 2009 16:32:34 -0000 Received: from [69.147.84.116] by t8.bullet.mail.sp1.yahoo.com with NNFMP; 17 Feb 2009 16:32:34 -0000 Received: from [127.0.0.1] by omp208.mail.sp1.yahoo.com with NNFMP; 17 Feb 2009 16:32:34 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 778689.53283.bm@omp208.mail.sp1.yahoo.com Received: (qmail 47683 invoked by uid 60001); 17 Feb 2009 16:32:34 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=rxphflGqBDRshVW7EWB3PUowMDys3azQqkYtssPLkJRen9yqbX+y1vd/m3p+sECIoavyjaI/YVLXaieQ2RApJC39lWvyyzxatTwzKMBsQqGxyr5WAo19DHJ8Z4kmXqg3wUfI48953vjW7tua83FbNFUVIdXVAEClLNx6W1eUbRE=; X-YMail-OSG: 4m1xYMYVM1lQXIlQhAayszXpD9YNavlBDeMqUZcyf8SB4OsLUspLPmLUz_qGcR91gwiqIqWdLhu.yOz6ZCtUZOyN1AY1WrtmutfXFKr6IFySs_Itsx6lbs.iF3TN3WTozliYTaprYAdKsr3hVol.2G3Mz7E22.HMQOj0qpGqfNuLhmU1wzrTqh5EWOlDpz8- Received: from [58.71.34.137] by web45808.mail.sp1.yahoo.com via HTTP; Tue, 17 Feb 2009 08:32:34 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Tue, 17 Feb 2009 08:32:34 -0800 (PST) From: Won De Erick To: Olivier Gautherot MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <538199.46897.qm@web45808.mail.sp1.yahoo.com> 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 Reply-To: won.derick@yahoo.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 16:32:42 -0000 Hi All, Is this firmware-related bug? tool log parsing error? Thanks in advance. --- On Mon, 2/16/09, Won De Erick wrote: > Thank you very much for the clear explanation. >=20 > --- On Sat, 2/14/09, Oliver Fromme > wrote: > > Won De Erick wrote: > > > This file /etc/wall_cmos_clock was missing, so I > > created an empty one.=20 > >=20 > > So you _do_ want to run your CMOS clock at local time > > instead of UTC? That is only required if you run a > > different OS on the same machine (dual-boot), because > > Windows expects the CMOS clock to run at local time. > >=20 >=20 > 'Not that I want to run at UTC. I wanted to find out > how the BMC system event log (SEL) timestamps are done by > the BMC firmware. The IBM x343 box is an IPMI v1.5 > compliant, and FreeBSD is the only OS installed. I wondered > why I got late datestamps on SEL.=20 >=20 > > Otherwise, if FreeBSD is the only OS on that machine, > > it's better to let the CMOS clock run at UTC (i.e. > do > > not create /etc/wall_cmos_clock), because it avoids > > all the switching back and forth between time zones, > > and adjkerntz(8) doesn't have to run all the time. > >=20 > > As far as ntpd is concerned, it doesn't matter.=20 > ntpd > > doesn't care about time zones. It always works on > UTC > > internally and synchronizes the time that way > (otherwise > > there would be additional complexities using NTP > servers > > in different time zones). Even the kernel doesn't > care > > about time zones. Handling time zones is done in the > > libc (userland). So, basically, if a program like > > date(1) displays the time, it converts UTC to your > local > > time zone for you. > >=20 > > > 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? > >=20 > > You seem to misunderstand. The CMOS clock _is_ always > > updated when you run ntpd. You do not have to change > > anything. > >=20 > > The only question is at which time zone the CMOS clock > > runs, as I've explained above. > >=20 > > If your CMOS clock runs at UTC (recommended if FreeBSD > > is the only OS on that machine), then the BIOS will > > always display a wrong time, because the BIOS > doesn't > > know your time zone, so it can't convert from UTC > to > > your time zone. But that's purely a cosmetical > issue. > > You can ignore that. Your CMOS clock _is_ > synchronized > > and runs correctly. Only your BIOS doesn't know > how > > to display it correctly. > >=20 >=20 >=20 > This is a cool explanation. This has cleared my assumption > that the CMOS clocked is not updated whenever the system is > sync'ed with an NTP server. > I think this has narrow down the issue. >=20 > Let me share you the problem that I encountered, which had > led me to suspect before that CMOS clock was not properly > sync'ed. I hope you can give me more hints/explanations > for me to come up with a conclusive findings.=20 >=20 > 1. Get the date/time in shell > # date > Fri Feb 13 14:20:20 PHT 2009 >=20 > 2. Rebooted the box, then entered BIOS config to verify > date/time >=20 > System Time : 06:25:29 # seems correct, it runs > at UTC > System Date : Fri 02/13/2009 >=20 > 3. Let the system up. > 4. Unplugged the power cord to come up with a new event in > SEL. I am using FreeIPMI v0.7.1 to retrieve the logs. >=20 > 1724:01-Jan-1970 08:00:12:Power Supply Power Supply > 2:Presence detected > 1744:01-Jan-1970 08:00:12:Power Supply Power Supply 2:Power > Supply input lost (AC/DC) -------------------> uplug the > power. > 1764:01-Jan-1970 08:00:12:Power Unit Power > Redundancy:Entered from Non-redundant:Insufficient Resources > 1784:01-Jan-1970 08:00:41:System Event System > Event:Timestamp Clock Synch > 1804:12-Feb-2009 14:27:50:System Event System > Event:Timestamp Clock Synch > 1824:12-Feb-2009 14:28:15:System Event System Event:OEM > System Boot Event > 1844:12-Feb-2009 14:29:53:System Event System > Event:Timestamp Clock Synch > 1864:12-Feb-2009 14:29:53:System Event System > Event:Timestamp Clock Synch > 1884:12-Feb-2009 14:31:55:System Event System Event:OEM > System Boot Event -------------------> datestamp > incorrect >=20 > Is the datestamp '01-Jan-1970' a sign of a > defective CMOS battery? > Does the datestamp '12-Feb-2009' being not updated > to the correct date (13-Feb-2009) is a sign of a defective > battery too? or other issues like firmware bug? I would be > grateful to receive more tips from you. >=20 >=20 > > Best regards > > Oliver > >=20 > > --=20 > > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz > 29, > > 85567 Grafing b. M. > > Handelsregister: Registergericht Muenchen, HRA 74606,=20 > > Gesch=E4ftsfuehrung: > > secnetix Verwaltungsgesellsch. mbH, Handelsregister: > > Registergericht M=FCn- > > chen, HRB 125758, Gesch=E4ftsf=FChrer: Maik Bachmann, > Olaf > > Erb, Ralf Gebhart > >=20 > > FreeBSD-Dienstleistungen, -Produkte und mehr:=20 > > http://www.secnetix.de/bsd > >=20 > > "The ITU has offered the IETF formal alignment > with > > its > > corresponding technology, Penguins, but that won't > > fly." > > -- RFC 2549 > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org"=0A=0A=0A From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 17 17:50:19 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 9D4121065674 for ; Tue, 17 Feb 2009 17:50:19 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1DBA38FC26 for ; Tue, 17 Feb 2009 17:50:18 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n1HHoH5k080382; Tue, 17 Feb 2009 18:50:17 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n1HHoHYG080381; Tue, 17 Feb 2009 18:50:17 +0100 (CET) (envelope-from olli) Date: Tue, 17 Feb 2009 18:50:17 +0100 (CET) Message-Id: <200902171750.n1HHoHYG080381@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG, won.derick@yahoo.com In-Reply-To: <538199.46897.qm@web45808.mail.sp1.yahoo.com> X-Newsgroups: list.freebsd-hardware User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 17 Feb 2009 18:50:18 +0100 (CET) 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 Reply-To: freebsd-hardware@FreeBSD.ORG, won.derick@yahoo.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 17:50:20 -0000 Won De Erick wrote: > Is this firmware-related bug? tool log parsing error? I'm sorry, I don't know for sure. But it looks like a firmware problem. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Whatever happened to the days when hacking started at the cerebral cortex, and not at the keyboard?" -- Sid on userfriendly.org by Illiad, 2007-06-20 From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 17 21:15: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 B518B106564A for ; Tue, 17 Feb 2009 21:15:29 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from cpsmtpo-eml05.kpnxchange.com (cpsmtpo-eml05.KPNXCHANGE.COM [213.75.38.154]) by mx1.freebsd.org (Postfix) with ESMTP id 3C6C78FC12 for ; Tue, 17 Feb 2009 21:15:29 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from cpsmtp-eml110.kpnxchange.com ([10.94.168.110]) by cpsmtpo-eml05.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 17 Feb 2009 22:03:24 +0100 Received: from uitsmijter.van-laarhoven.org ([81.207.207.222]) by cpsmtp-eml110.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 17 Feb 2009 22:03:23 +0100 Received: from van-laarhoven.org (hind.van-laarhoven.org [10.66.0.146]) (authenticated bits=0) by uitsmijter.van-laarhoven.org (8.14.3/8.14.3) with ESMTP id n1HL5NAL052464; Tue, 17 Feb 2009 22:05:23 +0100 (CET) (envelope-from nick@van-laarhoven.org) Received: (nullmailer pid 7781 invoked by uid 1001); Tue, 17 Feb 2009 21:03:19 -0000 From: Nick Hibma To: freebsd-hardware@freebsd.org Date: Tue, 17 Feb 2009 22:03:18 +0100 User-Agent: KMail/1.9.10 References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> <200902132209.52793.hselasky@c2i.net> <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> In-Reply-To: <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902172203.19534.nick@van-laarhoven.org> X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_40 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on uitsmijter.van-laarhoven.org X-OriginalArrivalTime: 17 Feb 2009 21:03:23.0816 (UTC) FILETIME=[2BA9E280:01C99143] Cc: Alberto Mijares Subject: Re: Modem GSM/GPRS 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 Feb 2009 21:15:30 -0000 Alberto, Could you remove u3g again from your kernel, so the device attaches to ugen and then dump its descriptors using usbgen? usbgen -f /dev/ugen0 -D where ugen0 is the device mentioned in the dmesg. Thanks. Nick > [...] > > > Your device seems to use a propritary protocol and is not supported by > > FreeBSD out of the Box. But it might be a very simple one. In > > FreeBSD-7-current you can try adding the idVendor and idProduct to the > > ID-table > > in /sys/dev/usb/u3g.c . > > I've been trying and found this -> > http://people.freebsd.org/~n_hibma/u3g.html > > So, I updated my system (I'm on 7.1 now) and followed instructions. > > now dmesg says: > ucom0: on > uhub0 ucom0: configured 1 serial ports (U0.%d) > (much better, doesn't it) > > and /dev/cuaU0.0 is created when it is plugged in. However, I can't > stablish comunication with the modem. I tried with screen and minicom, > but nothing happens. Even stty reports: > > #stty -f /dev/cuaU0.0 -a > speed 9600 baud; 0 rows; 0 columns; > lflags: icanon isig iexten -echo -echoe -echok -echoke -echonl -echoctl > -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo > -extproc > iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk > brkint -inpck -ignpar -parmrk > oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow > -dtrflow -mdmbuf > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; > eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; > lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; > status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; > > > > This is what I did: > > $ diff u3g.c original > 195,196d194 > < /* PRUEBA SILABS */ > < {{ USB_VENDOR_SILABS, USB_PRODUCT_SILABS_SAEL }, > U3GSP_GPRS, U3GFL_NONE }, > > and > > $ tail -1 usbdevs > product SILABS SAEL 0x8053 SA-EL USB > > > Is there anything else should I try? Any clue is good for me. > > Thank you > > Alberto Mijares > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to > "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 17 22:20:57 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 325881065673 for ; Tue, 17 Feb 2009 22:20:57 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.177]) by mx1.freebsd.org (Postfix) with ESMTP id DCE188FC1C for ; Tue, 17 Feb 2009 22:20:56 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: by el-out-1112.google.com with SMTP id r27so2261628ele.13 for ; Tue, 17 Feb 2009 14:20:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=cJ/RM2vOxBvAWm6c8S6pXXJFM4yBtoOXI3MLX2AVudY=; b=RN+Vmj5Y2mGL+n29DFNo/dHXtdUZV4vFZAArpFphn2nTvQYNCAVLtv71XhM8kvFBkT wlRaz/xLtKEwzLIHI8+oi5xgg/KNklXtf6AZn2IpdTnov2gc8BnRIvPxf164o9QX8tIn joHGPfM0c1Rkt1CcKkMp3AK6L7mISohC3/TNE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=k/yw6k+2wB/NBXtTQ59pu9hYCHDn7PkdxAYVtSWWRNrvcFFIN0ETaUucVbYddf1lho X3moqbTVCcTM5dP4+2K5J2hVr+/MUb3HbmXgVM7UfuLjnUkppbAHC6owQsm0jLzGwZJY LvkxnO882wx53RzKaFebMlPX11ttJ3F9/lLbY= MIME-Version: 1.0 Received: by 10.220.76.81 with SMTP id b17mr520825vck.24.1234909255984; Tue, 17 Feb 2009 14:20:55 -0800 (PST) In-Reply-To: <200902172203.19534.nick@van-laarhoven.org> References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> <200902132209.52793.hselasky@c2i.net> <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> <200902172203.19534.nick@van-laarhoven.org> Date: Wed, 18 Feb 2009 17:50:55 +1930 Message-ID: <286906750902171420h5815eaccp60e20abb0d097c21@mail.gmail.com> From: Alberto Mijares To: Nick Hibma , freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Modem GSM/GPRS 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 Feb 2009 22:20:57 -0000 On Wed, Feb 18, 2009 at 4:33 PM, Nick Hibma wrote: > Alberto, > > Could you remove u3g again from your kernel, so the device attaches to ugen > and then dump its descriptors using usbgen? > > usbgen -f /dev/ugen0 -D > > where ugen0 is the device mentioned in the dmesg. > > Thanks. > > Nick > There is no such usbgen command in my system nor the ports tree (Am I lost in the moon?). Where can I find it? Is the following info useful to you? # udesc_dump /dev/ugen0 Standard Device Descriptor: bLength 18 bDescriptorType 01 bcdUSB 0110 bDeviceClass 00 bDeviceSubClass 00 bDeviceProtocol 00 bMaxPacketSize 64 idVendor 10c4 idProduct 8053 bcdDevice 0100 iManufacturer 1 iProduct 2 iSerialNumber 3 bNumConfigurations 1 Configuration 0: Standard Configuration Descriptor: bLength 9 bDescriptorType 02 wTotalLength 32 bNumInterface 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 80 bMaxPower 250 (500 mA) Standard Interface Descriptor: bLength 9 bDescriptorType 04 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass ff bInterfaceSubClass 00 bInterfaceProtocol 00 iInterface 2 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 81 (in) bmAttributes 02 (Bulk) wMaxPacketSize 64 bInterval 0 Standard Endpoint Descriptor: bLength 7 bDescriptorType 05 bEndpointAddress 01 (out) bmAttributes 02 (Bulk) wMaxPacketSize 64 bInterval 0 Codes Representing Languages by the Device: bLength 4 bDescriptorType 03 wLANGID[0] 0409 String (index 1): Silicon Labs String (index 2): SA-EL USB String (index 3): 280RH70230396 Thank you. Alberto Mijares From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 17 22:45:20 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 74D80106566C for ; Tue, 17 Feb 2009 22:45:20 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 2C3248FC1D for ; Tue, 17 Feb 2009 22:45:20 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: by yw-out-2324.google.com with SMTP id 2so1323405ywt.13 for ; Tue, 17 Feb 2009 14:45:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=mHMzfqA4y1t/MZu432CzRDiCpe4+xMNuL1iKJz44P0g=; b=HNn4V3b4vPnFMZWT8FXqmJ0eC9KLU5U2BmljZ9mXGrrjKxEoIJ+E/hEWStKpIhjYIN e7glwjE913iWjHBprpO6WJob8O3diTil3Q9d5pfbS69DOH3uqLOfSrFM6uYgTjo1Z8S8 OtqoZO7KDLnPYkD5OS0l1D7RYb+gOxOMYiepA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=SY78BjuyA47poQNWzJSLdmFxY98QjHmuaIz5kxT6pVhI8xIhqZigyJSF4FD2lDKVxr UjDrVyGO+Zp1S1CZMSJVtVILZ4GpRrZ5ockMjuBKrvaKwUaCq1bwxpZwtPnGKsVCPdIm NHgApgYQa6itSDYw5+szNoqmpA5a23m4TFqhE= MIME-Version: 1.0 Received: by 10.220.45.142 with SMTP id e14mr1606436vcf.95.1234910719566; Tue, 17 Feb 2009 14:45:19 -0800 (PST) In-Reply-To: <286906750902171420h5815eaccp60e20abb0d097c21@mail.gmail.com> References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> <200902132209.52793.hselasky@c2i.net> <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> <200902172203.19534.nick@van-laarhoven.org> <286906750902171420h5815eaccp60e20abb0d097c21@mail.gmail.com> Date: Wed, 18 Feb 2009 18:15:19 +1930 Message-ID: <286906750902171445s24ab7d29s7cf8f2eedf0fa376@mail.gmail.com> From: Alberto Mijares To: Nick Hibma , freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Modem GSM/GPRS 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 Feb 2009 22:45:20 -0000 On Wed, Feb 18, 2009 at 5:50 PM, Alberto Mijares wrote: > On Wed, Feb 18, 2009 at 4:33 PM, Nick Hibma wrote: >> Alberto, >> >> Could you remove u3g again from your kernel, so the device attaches to ugen >> and then dump its descriptors using usbgen? >> >> usbgen -f /dev/ugen0 -D >> >> where ugen0 is the device mentioned in the dmesg. >> >> Thanks. >> >> Nick >> > > There is no such usbgen command in my system nor the ports tree (Am I > lost in the moon?). Where can I find it? I'm sorry. I've been too lazy last days. I found it already (sysutils/usbutil). Here goes: # usbgen -f /dev/ugen0 -D DEVICE descriptor: bLength=18 bDescriptorType=1 bcdUSB=1.10 bDeviceClass=0 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x10c4 idProduct=0x8053 bcdDevice=100 iManufacturer=1 iProduct=2 iSerialNumber=3 bNumConfigurations=1 Current configuration is number 1 CONFIGURATION descriptor index 0: bLength=9 bDescriptorType=2 wTotalLength=32 bNumInterface=1 bConfigurationValue=1 iConfiguration=0 bmAttributes=80 bMaxPower=500 mA INTERFACE descriptor index 0, alt index 0: bLength=9 bDescriptorType=4 bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=2 bInterfaceClass=255 bInterfaceSubClass=0 bInterfaceProtocol=0 iInterface=2 ENDPOINT descriptor index 0: bLength=7 bDescriptorType=5 bEndpointAddress=1-in bmAttributes=2 wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor index 1: bLength=7 bDescriptorType=5 bEndpointAddress=1-out bmAttributes=2 wMaxPacketSize=64 bInterval=0 Seems the same info... Regards. Alberto Mijares From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 19 18:54:50 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 ADBD41065686 for ; Thu, 19 Feb 2009 18:54:50 +0000 (UTC) (envelope-from lawrence.auster@att.net) Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.123]) by mx1.freebsd.org (Postfix) with ESMTP id 6BBF68FC2E for ; Thu, 19 Feb 2009 18:54:49 +0000 (UTC) (envelope-from lawrence.auster@att.net) Received: from k4k6l ([75.191.169.91]) by cdptpa-omta04.mail.rr.com with ESMTP id <20090219185445.XLRD4162.cdptpa-omta04.mail.rr.com@k4k6l> for ; Thu, 19 Feb 2009 18:54:45 +0000 From: "Lawrence Auster" To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset="US-ASCII" Date: Thu, 19 Feb 2009 19:54:42 +0100 X-Priority: 3 Message-Id: <20090219185445.XLRD4162.cdptpa-omta04.mail.rr.com@k4k6l> Subject: "My race is just nothing": Some thoughts on the political psychology of women X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lawrence.auster@att.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 18:54:51 -0000 "My race is just nothing": Some thoughts on the political psychology of women By Kevin MacDonald February 19, 2009 It seems that the signs of white dispossession are everywhere these days. Edmund Connelly describes how non-Jewish whites are being pushed out of elite institutions like Harvard. An article titled “The end of white America” catalogues the lack of cultural confidence of whites these days. It quotes a student who says “To be white is to be culturally broke." Writing in vdare.com, David A. Yeagley quotes one of his female students saying “Look ... I don’t see anything about my culture to be proud of. It’s all nothing. My race is just nothing.” Yeagley notes the Cheyenne saying, “A nation is never defeated until the hearts of its women are on the ground.” And he places this in the context of the recent election in which 46% of white women voted for Obama compared to 41% of white men. These percentages are somewhat inflated because they include Jews and immigrants, such as South Asians, who are classified as white but do not identify with the European-American majority. Nevertheless, they do point to a significant gender gap. While it is certainly true that voting for McCain-Palin is not a sign of white consciousness — even implicitly, it is also the case that voting for Obama is a good sign of a lack of racial consciousness for European Americans. The good news, of course, is that a majority of white women did not vote for Obama. And, as Steve Sailer has shown for the 2004 election, if one separated out women who are married and have children, the results would show an even greater tendency to vote against Obama. Nevertheless, there is a real problem. Those of us with some acquaintance with European-Americans who do have an explicit ethnic identity and a sense of their ethnic interests are quite aware that there is a very large sex ratio imbalance at gatherings of like-minded people. The attendees are almost all male — an exception being the redoubtable Virginia Abernethy. And there are stories of men who have stopped attending meetings or who provide support only in the most furtive manner, mainly because their wives are afraid that the attitudes of their husbands could become public and ruin their social life. Making such things public is just the sort of thing that organizations like the SPLC and the ADL love to do. Judith Warner of the New York Times describes the result of an informal "email inquiry" on women's reactions to Obama. Some imagined having sex with Obama and replacing Michelle Obama as First Lady. Others imagined themselves at social engagements with Obama. All wanted deeply to have some of the Obama aura rub off on them. Warner's email contacts doubtless reflect her liberal readership, but I wouldn't be at all surprised if they are quite general, especially among white women who voted for Obama. What does an evolutionary psychologist say about all this? Parenthetically, I realize that the great majority of Americans do not believe in evolution. Nevertheless, evolutionary theory is a very powerful and scientifically credible way of looking at human behavior. It is no accident that one of the main strands of Jewish intellectual activism over the last century has been to oppose evolutionary theory as an explanatory tool in the social sciences. Darwin did indeed have a dangerous idea — dangerous to Jews because it provides a rational grounding for the ethnic identity and interests of European-derived people. The evolutionary theory of sex is one of the bedrocks of evolutionary psychology — probably accounting for half of all the research in the field. The basic idea is simple: Females invest a relatively large amount of time and energy in reproduction. In the world we evolved in, the only way for women to reproduce was to endure a 38-week pregnancy and then nurse the child for an even longer period. Even after nursing, child care was mainly a female responsibility. Because women are committed to this very large investment, they become very valuable in the mating game. And because they are valuable, they become discriminating maters: Just as a worker who puts in more time and energy is in a better bargaining position than one who puts in little time and energy, women become the choosers in the mating game. And what do women want? Women are expected to want men who have high social status. From an evolutionary perspective, such men are attractive because they may be willing to provide valuable resources that would help in supporting the mother and raising the children. (When men do contribute resources, they also become choosy, but that's another story.) And even if a wealthy man does not provide resources, he is likely to have good genes — genes that predispose his children to be successful. In any case, women do indeed prefer wealthy, high-status men. For example, a recent study found that wealthy men give women more orgasms: "The pleasure women get from making love is directly linked to the size of their partner’s bank balance." Other research shows that women are likely to choose higher status men than their husbands when they have affairs, resulting in the possibility of a lower status male helping to raise the children of a higher-status male. What about the idea that evolutionary theory implies that people should be attracted to people who are genetically like themselves? Evolutionary theory predicts that women will be attracted to men who are genetically similar to themselves compared to men who are from a different race or ethnic group. For one thing, this makes them more closely related to their own children. The problem is that this attraction to genetically similar mates is only part of the story. It must compete with the tendency to be attracted to wealthy, powerful men. And quite clearly, the phenomenon where large numbers of white women fantasize about having a relationship with Obama reflects his power and social status, not attraction to a genetically similar person. The media is a major part of the hostile elite, so it is not surprising that it has played a leading role in the idolization of Obama — the slobbering love affair between the mainstream media and Obama. It's the same role that Edmund Connelly has called attention to in his writing on the images of blacks created by Hollywood in recent decades. Black action heroes are now household names, and more than one commentator has pointed out that there were several black presidents in the movies and on television long before Obama was elected. These images from the media tap into women's psychological attraction to high-status males. It was probably fairly common for white women to fantasize about having sex with Will Smith or Denzel Washington or even the "wise and saintly" Morgan Freeman long before the world had ever heard of Barack Obama. Another sex difference that contributes to women's political behavior is that women are generally more nurturant, affectionate, empathic, and caring than men. This is another aspect of female psychology that can easily be derived from evolutionary thinking — the vital importance of nurturing children and developing close family relationships in our evolutionary past. Thus it is not surprising that many of Judith Warner's women not only fantasize about having sex with Obama, they see themselves married to him and becoming first lady. They develop a close and caring relationship with him, or they see him as a good friend. I suppose this is also the reason why women are more likely than men to support social programs that promise to aid children and poor people. This relatively greater empathy and nurturance was certainly adaptive in a world of family groups and close relatives. But in the modern world, it can easily lead to maladaptive altruism and ignoring real dangers. For example, white women enamored of images of sexy, high-status black males are not informed by the mainstream media of the very large racial imbalance in crime, particularly black men raping white women. Another problem with women being relatively high in nurturance and empathy is that these traits are linked to greater compliance and greater inclination to seek the approval and affection of others. Again, these are very adaptive traits in the world of small groups and close relatives. But in a world dominated by elites that are hostile to the interests of whites, these traits can lead to mindless acceptance of anti-white cultural norms. Challenging social norms — even ones that are obviously against one's interests — carries a very high psychological cost to people who seek the approval and affection of others. This implies that once the intellectual and political movements described in The Culture of Critique had seized the intellectual and moral high ground, they became difficult indeed to dislodge. Challenging these norms brings accusations of moral turpitude ringing down from the most prestigious political, media and academic institutions of the society. People who seek the approval and affection of others are definitely not inclined to go there. This in turn may well be a large part of the explanation for why there are so few women at gatherings of European-Americans concerned about the future of their people and culture. This paints a fairly bleak picture. But there are some rays of hope. It is likely that at some point the gap between rhetoric and reality in American life will be so large that no one will believe what they are hearing from the hostile elites that dominate public discourse — much like the Soviet Union in the decades before its fall. When that happens, the cultural icons promoted by the media will lose their credibility and allure as well. And because of the internet, the opportunity to hear divergent opinions and become aware of information that is suppressed by the mainstream media has never been better. All around us we can see the collapse and increasing irrelevance of the old media. The internet has already created communities where prestige and social approval can be obtained completely outside the norms created by our hostile elites. And at least some of these communities are dedicated to transforming America by asserting the legitimacy of white identities and interests. The dispossession of whites is already substantial, but it promises to be a whole lot more obvious as time goes on. As whites become a minority, it is difficult to imagine that they won't develop more of a group consciousness and challenge the prevailing anti-white norms. And that includes even the more nurturant and empathic among us. Source with hyperlinks : http://www.theoccidentalobserver.net/articles/MacDonald-Women.html ------------------------------------- You or someone using your email adress is currently subscribed to Lawrence Auster's Newletter. If you wish to unsubscribe from our mailing list, please let us know by calling to 1 212 865 1284 Thanks, Lawrence Auster, 238 W 101 St Apt. 3B New York, NY 10025 Contact : lawrence.auster@att.net -------------------------------------