From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 9 23:43:27 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 902A410656BC for ; Mon, 9 Feb 2009 23:43:27 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id F0D3B8FC25 for ; Mon, 9 Feb 2009 23:43:26 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by ewy14 with SMTP id 14so3459287ewy.19 for ; Mon, 09 Feb 2009 15:43:25 -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:cc:content-type :content-transfer-encoding; bh=T4n8diV/5MWWUtTlgU0gqScBBy3f5KGBN4TxQSR7F3M=; b=HT4aQW1ZZQVQPEay5RsO2OSVjoHwKfZruvOKjAl/eeccWnZrS1melU4pLNuNfQIGzF 8F3rEFmf6oVQhm9fQBLChlj+oMgfDyHjfJ2wtUCRTh8rG6+7QW5EW3OY2HM0737D33Wy BV3fpk5JmHo5oBKI6sAK8YsQLMhOqLzm8O7Zs= 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 :cc:content-type:content-transfer-encoding; b=t7qJMP9yYuIDQbnIUuDkvrPzZTrk0S1gg0xfeY+TFJkfEWx7/3NwLa+Bw/Bbqj5A/A qhhR5foa53MBhmP1/NFkqFFtBrCIqsv33lNgUVPAnuukb+Kku1lJhndufkThGbc80Izb EAyXZDgI3+sU+j4MGdng1e8AtQvLUS4Onmm+0= MIME-Version: 1.0 Received: by 10.210.45.17 with SMTP id s17mr4230392ebs.93.1234221188209; Mon, 09 Feb 2009 15:13:08 -0800 (PST) In-Reply-To: References: Date: Tue, 10 Feb 2009 00:13:08 +0100 Message-ID: <3a142e750902091513h745bf9ah7b33f456a8580b95@mail.gmail.com> From: "Paul B. Mahol" To: Andreas Nilsson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: ipw3945 problems 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, 09 Feb 2009 23:43:28 -0000 On 2/4/09, Andreas Nilsson wrote: > Hi, > > I've been experiencing some weird behavior with the ipw3945 on my laptop > running FreeBSD 7.1-RELEASE. When running on AC the card works as expected, > but when running unplugged the interface keeps going down and up and down. I > get ~10 consecutive pings before it goes down. > > The networks I have tested are encrypted with some WPA protocol. > > When starting on battery there are also some other strange behavior, there > are some lock-ups in the gui and xorg uses some 14% cpu @1.2GHz doing > nothing, When the mouse has been idle for some seconds it takes a bit of > movement to activate again. After a plug and unplug of the AC everything > seems to work as it is supposed to. > > I realize this isn't very much to go on... Any logs that would help? > > The laptop in question is a Lenovo Thinkpad t61p. > > Best regards > Andreas Nilsson > _______________________________________________ > 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" > Are you using powerd? Perhaps CPU cx states are changed? -- Paul From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 10 08:40:44 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 91D5D1065670 for ; Tue, 10 Feb 2009 08:40:44 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-bw0-f163.google.com (mail-bw0-f163.google.com [209.85.218.163]) by mx1.freebsd.org (Postfix) with ESMTP id E119B8FC22 for ; Tue, 10 Feb 2009 08:40:43 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by bwz7 with SMTP id 7so2618064bwz.19 for ; Tue, 10 Feb 2009 00:40:43 -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:cc:content-type; bh=0NZCdKg7OqcH7tEurdxifZcsJxaDOzmvNhfuzgumZkk=; b=riMZ3WszX4fIOSBeYDCNYFRMMyKG198ZJKwhi17fVC2ttZAFc7xfNAX2TmhGg1d2uZ u3U9xFlkIe2mUlnRtjPQXWWG4u2zbFEU8rVgtXXXW44iKk72Tz90z0wzVgjdRoSW7oGh 5ANTgjY15WLRDGODVxcJJFnd9mBNChzMVRTd8= 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 :cc:content-type; b=N+D/mlaSmeiIRWxwqXw0jodpu9WTxLJF/p03KbsSdG9cMrFm4PYe+1OjirsYnT1s1g ww/EGjscqFPUGz8h1ayhBlD89AeN9inIm1erSr5+Cp+AU3JCRsfsNkPalkOhtokE4alC AYEiyAPGRbNAFly2QU0yfMPXeRATbjKXxnif8= MIME-Version: 1.0 Received: by 10.181.148.13 with SMTP id a13mr1400540bko.20.1234255242411; Tue, 10 Feb 2009 00:40:42 -0800 (PST) In-Reply-To: <3a142e750902091513h745bf9ah7b33f456a8580b95@mail.gmail.com> References: <3a142e750902091513h745bf9ah7b33f456a8580b95@mail.gmail.com> Date: Tue, 10 Feb 2009 09:40:42 +0100 Message-ID: From: Andreas Nilsson To: "Paul B. Mahol" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: ipw3945 problems 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, 10 Feb 2009 08:40:44 -0000 On Tue, Feb 10, 2009 at 12:13 AM, Paul B. Mahol wrote: > On 2/4/09, Andreas Nilsson wrote: > > Hi, > > > > I've been experiencing some weird behavior with the ipw3945 on my laptop > > running FreeBSD 7.1-RELEASE. When running on AC the card works as > expected, > > but when running unplugged the interface keeps going down and up and > down. I > > get ~10 consecutive pings before it goes down. > > > > The networks I have tested are encrypted with some WPA protocol. > > > > When starting on battery there are also some other strange behavior, > there > > are some lock-ups in the gui and xorg uses some 14% cpu @1.2GHz doing > > nothing, When the mouse has been idle for some seconds it takes a bit of > > movement to activate again. After a plug and unplug of the AC everything > > seems to work as it is supposed to. > > > > I realize this isn't very much to go on... Any logs that would help? > > > > The laptop in question is a Lenovo Thinkpad t61p. > > > > Best regards > > Andreas Nilsson > > _______________________________________________ > > 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" > > > > Are you using powerd? Perhaps CPU cx states are changed? > > -- > Paul > I am using powerd, and CPU cx states are probably beeing changed. I set the corresponding tunables to allow the CPUs (cores) to reach C3. Before I started using C3 on a regular basis I did some tesing and I didn't notice any difference in connectivity. When running on AC the connection works for a while ( a random amount of time ) , but then the carrier is lost. When running in school I get really low transfer speed, somewhere around 200Kb/s from a computer in a room next door. When running on linux I get around 1+Mb/s from the same computer. Best regards Andreas Nilsson From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 10 09:01:03 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 2173C1065672 for ; Tue, 10 Feb 2009 09:01:03 +0000 (UTC) (envelope-from nicolas@goralski.fr) Received: from mail.monmel.org (srv.goralski.fr [193.43.214.193]) by mx1.freebsd.org (Postfix) with ESMTP id D63D38FC12 for ; Tue, 10 Feb 2009 09:01:02 +0000 (UTC) (envelope-from nicolas@goralski.fr) Received: from localhost (unknown [192.168.210.10]) by mail.monmel.org (Postfix) with ESMTP id 8DEF5C210C0 for ; Tue, 10 Feb 2009 09:49:12 +0100 (CET) X-Virus-Scanned: amavisd-new at fox-services.com Received: from mail.monmel.org ([192.168.210.10]) by localhost (mail.goralski.fr [192.168.210.10]) (amavisd-new, port 10024) with ESMTP id h1g+ZApqnAZA for ; Tue, 10 Feb 2009 09:49:10 +0100 (CET) Received: from www.goralski.fr (unknown [192.168.210.11]) (Authenticated sender: nicolas.goralski@fox-informatique.com) by mail.monmel.org (Postfix) with ESMTPA id 88935C210BA for ; Tue, 10 Feb 2009 09:49:10 +0100 (CET) MIME-Version: 1.0 Date: Tue, 10 Feb 2009 09:49:10 +0100 From: Nicolas GORALSKI To: freebsd-hardware@freebsd.org Message-ID: X-Sender: nicolas@goralski.fr Received: from 195.177.83.221 [195.177.83.221] with HTTP/1.1 (POST); Tue, 10 Feb 2009 09:49:10 +0100 User-Agent: RoundCube Webmail/0.1 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Subject: Looking for ethernet expresscard 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, 10 Feb 2009 09:01:03 -0000 Hi everybody I've a laptop with a sis191 ethernet card and it doesn't work. NDIS with (XP|2K|98) drivers make my kernel crash. So i was thinking about an network expresscard. Does anybody know about a model that will work ? From owner-freebsd-hardware@FreeBSD.ORG Wed Feb 11 08:33: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 4E9F1106566C for ; Wed, 11 Feb 2009 08:33:40 +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 8EA508FC17 for ; Wed, 11 Feb 2009 08:33:39 +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 n1B8XbQG096838; Wed, 11 Feb 2009 09:33:37 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n1B8XbLo096837; Wed, 11 Feb 2009 09:33:37 +0100 (CET) (envelope-from olli) Date: Wed, 11 Feb 2009 09:33:37 +0100 (CET) Message-Id: <200902110833.n1B8XbLo096837@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG 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]); Wed, 11 Feb 2009 09:33:38 +0100 (CET) Cc: Subject: SATA PCI adapter recommendation 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: Wed, 11 Feb 2009 08:33:40 -0000 Hi, I plan to put a SATA drive in an old PATA-only PC, so I'm looking for an appropriate adapter card. A cheap card should suffice, I do not need RAID, and it does not have to be SATA-300. (This machine has only standard PCI slots anyway, so it wouldn't be able to saturate SATA-300.) I'm currently looking at these, all of which are about 20 Euro around here: 1. Based on Silicon Image Sil-3x12 chip: http://www.digital-data.de/download/datasheets/111816_Datasheet.pdf 2. Based on Initio INIC1620 chip: http://www.digital-data.de/download/datasheets/111817_Datasheet.pdf 3. Some VIA chip (probably VT6421A, but not 100% clear): http://www.delock.de/view/pdf/70156/A/1943/ I've read a few scary things about SIL chips on the lists, so I guess I'd better try to avoid that one. But how about the Initio and VIA ones? Do they work well with FreeBSD? Any good or bad experiences? Finally, a small question: I assume that all of those SATA controllers do have their own BIOS, so I can boot from them, right? It would be annoying to have to keep an old PATA disk in that box just to be able to boot. Thanks! 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 "Perl will consistently give you what you want, unless what you want is consistency." -- Larry Wall From owner-freebsd-hardware@FreeBSD.ORG Wed Feb 11 10:15:11 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 E9EE71065674 for ; Wed, 11 Feb 2009 10:15:11 +0000 (UTC) (envelope-from ricardo.meb.jesus@gmail.com) Received: from gate.criticalsoftware.com (gate.criticalsoftware.com [212.13.37.242]) by mx1.freebsd.org (Postfix) with ESMTP id A6B3C8FC1C for ; Wed, 11 Feb 2009 10:15:11 +0000 (UTC) (envelope-from ricardo.meb.jesus@gmail.com) Received: from [192.168.1.21] (unknown [192.168.1.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gate.criticalsoftware.com (Postfix) with ESMTP id 4ED4FE8703; Wed, 11 Feb 2009 09:43:59 +0000 (WET) Message-ID: <49929DE2.6070200@gmail.com> Date: Wed, 11 Feb 2009 09:44:02 +0000 From: Ricardo Jesus User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Oliver Fromme References: <200902110833.n1B8XbLo096837@lurza.secnetix.de> In-Reply-To: <200902110833.n1B8XbLo096837@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: SATA PCI adapter recommendation X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ricardo.m.jesus@criticalsoftware.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2009 10:15:12 -0000 Oliver Fromme wrote: > Hi, > > I plan to put a SATA drive in an old PATA-only PC, so I'm > looking for an appropriate adapter card. A cheap card > should suffice, I do not need RAID, and it does not have > to be SATA-300. (This machine has only standard PCI slots > anyway, so it wouldn't be able to saturate SATA-300.) > > I'm currently looking at these, all of which are about > 20 Euro around here: > > 1. Based on Silicon Image Sil-3x12 chip: > http://www.digital-data.de/download/datasheets/111816_Datasheet.pdf > > 2. Based on Initio INIC1620 chip: > http://www.digital-data.de/download/datasheets/111817_Datasheet.pdf > > 3. Some VIA chip (probably VT6421A, but not 100% clear): > http://www.delock.de/view/pdf/70156/A/1943/ > > I've read a few scary things about SIL chips on the lists, > so I guess I'd better try to avoid that one. > But how about the Initio and VIA ones? Do they work well > with FreeBSD? Any good or bad experiences? > > Finally, a small question: I assume that all of those > SATA controllers do have their own BIOS, so I can boot > from them, right? It would be annoying to have to keep > an old PATA disk in that box just to be able to boot. > > Thanks! > > Best regards > Oliver > I have a SATA card with the Initio1662 chip and it isn't supported, which is a shame :( From owner-freebsd-hardware@FreeBSD.ORG Wed Feb 11 10:47:14 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 3F5081065715 for ; Wed, 11 Feb 2009 10:47:14 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from smtp3.clear.net.nz (smtp3.clear.net.nz [203.97.33.64]) by mx1.freebsd.org (Postfix) with ESMTP id 016848FC2E for ; Wed, 11 Feb 2009 10:47:13 +0000 (UTC) (envelope-from markir@paradise.net.nz) Received: from zmori.markir.net (121-73-165-228.dsl.telstraclear.net [121.73.165.228]) by smtp3.clear.net.nz (CLEAR Net Mail) with ESMTP id <0KEW000FND9KQJ20@smtp3.clear.net.nz> for freebsd-hardware@freebsd.org; Wed, 11 Feb 2009 23:32:09 +1300 (NZDT) Date: Wed, 11 Feb 2009 23:32:08 +1300 From: Mark Kirkwood In-reply-to: <200902110833.n1B8XbLo096837@lurza.secnetix.de> To: Oliver Fromme Message-id: <4992A928.6080308@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <200902110833.n1B8XbLo096837@lurza.secnetix.de> User-Agent: Thunderbird 2.0.0.19 (X11/20090117) Cc: freebsd-hardware@freebsd.org Subject: Re: SATA PCI adapter recommendation 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: Wed, 11 Feb 2009 10:47:15 -0000 Oliver Fromme wrote: > Hi, > > I plan to put a SATA drive in an old PATA-only PC, so I'm > looking for an appropriate adapter card. A cheap card > should suffice, I do not need RAID, and it does not have > to be SATA-300. (This machine has only standard PCI slots > anyway, so it wouldn't be able to saturate SATA-300.) > > I'm currently looking at these, all of which are about > 20 Euro around here: > > 1. Based on Silicon Image Sil-3x12 chip: > http://www.digital-data.de/download/datasheets/111816_Datasheet.pdf > > 2. Based on Initio INIC1620 chip: > http://www.digital-data.de/download/datasheets/111817_Datasheet.pdf > > 3. Some VIA chip (probably VT6421A, but not 100% clear): > http://www.delock.de/view/pdf/70156/A/1943/ > > I've read a few scary things about SIL chips on the lists, > so I guess I'd better try to avoid that one. > But how about the Initio and VIA ones? Do they work well > with FreeBSD? Any good or bad experiences? > > Finally, a small question: I assume that all of those > SATA controllers do have their own BIOS, so I can boot > from them, right? It would be annoying to have to keep > an old PATA disk in that box just to be able to boot. > > I'd forget those and buy a 3ware card - supported and reliable. Possibly a little more expensive... but they are available 2nd hand on ebay, which should help: http://cgi.ebay.com/hardware-raid-card-3ware-8006-2LP-2-port-SATA-RAID_W0QQitemZ140300178432QQcmdZViewItemQQptZPCC_Drives_Storage_Internal?hash=item140300178432&_trksid=p3286.c0.m14&_trkparms=72%3A1234|66%3A2|65%3A12|39%3A1|240%3A1318|301%3A0|293%3A1|294%3A50 regards Mark From owner-freebsd-hardware@FreeBSD.ORG Wed Feb 11 15:18:15 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 5E10D106566C for ; Wed, 11 Feb 2009 15:18:15 +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 C68228FC13 for ; Wed, 11 Feb 2009 15:18:14 +0000 (UTC) (envelope-from om-lists-bsd@omx.ch) Received: (qmail 21421 invoked from network); 11 Feb 2009 14:51:32 -0000 Received: from [192.168.1.170] ([80.254.166.203]) by ibox.insign.ch ([195.134.143.207]) with ESMTP via TCP; 11 Feb 2009 14:51:32 -0000 From: Olivier Mueller To: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain Date: Wed, 11 Feb 2009 15:51:31 +0100 Message-Id: <1234363891.15909.35.camel@ompc.insign.local> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: 7bit Cc: Subject: 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: Wed, 11 Feb 2009 15:18:15 -0000 Hello, This afternoon I wanted to upgrade to 7.1 two good old dell PowerEdge servers which were running FreeBSD 6.x. It went fine and quickly on the poweredge 1950, but it failed completely on the poweredge 1850. Facts: - boot cd and setup / operation of freebsd 6.x or 7.0 is fine Message log abstract: $ uname -v FreeBSD 7.0-RELEASE-p7 #0: Sun Dec 21 08:31:52 UTC 2008 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC $ dmesg|grep amr 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) Trying to mount root from ufs:/dev/amrd0s1a - boot cd of 7.1 fails because the installed doesn't see any harddisk. Message log abstract: amr0: adapter is busy amr0: adapter is busy amr0: delete logical drives supported by controller I also tried to setup 7.0, and then upgrade to 7.1 with freebsd-update, but then it fails exactly like with the 7.1 boot CD (7.1-RELEASE-amd64-disc1.iso). Screenshot: http://omx.ch/om/stuff/pe1850bsd71error.jpg BIOS Message about the Controller on system startup: PowerEdge Expandable RAID COntroller BIOS, (c) 2006 LSI Logic Corporation I'm not sure what I can try next... I'd still like to be able to run 7.1 on this host as well as on several other old but still fine 1850. Is my system simply too old? Why is my adapter "busy" under 7.1? What would you try? I checked the relnotes as well, but saw nothing helpful about my problem there. regards & thanks in advance for any feedback, Olivier From owner-freebsd-hardware@FreeBSD.ORG Wed Feb 11 15:54:08 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 0ABF91065675; Wed, 11 Feb 2009 15:54:08 +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 CE1078FC14; Wed, 11 Feb 2009 15:54:07 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from localhost (localhost [127.0.0.1]) by mail.digitalfreaks.org (Postfix) with ESMTP id 53DBE797826; Wed, 11 Feb 2009 10:38:32 -0500 (EST) Received: from mail.digitalfreaks.org ([127.0.0.1]) by localhost (mail.digitalfreaks.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 65381-48; Wed, 11 Feb 2009 10:38:30 -0500 (EST) Received: from [192.168.2.170] (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.digitalfreaks.org (Postfix) with ESMTPSA id 8DE60797829; Wed, 11 Feb 2009 10:38:30 -0500 (EST) From: "Brian A. Seklecki" To: Olivier Mueller In-Reply-To: <1234363891.15909.35.camel@ompc.insign.local> References: <1234363891.15909.35.camel@ompc.insign.local> Content-Type: text/plain Date: Wed, 11 Feb 2009 10:38:29 -0500 Message-Id: <1234366709.3500.62.camel@ingress.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.24.2 (2.24.2-1.fc10) Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.2a mail.digitalfreaks 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: Wed, 11 Feb 2009 15:54:08 -0000 On Wed, 2009-02-11 at 15:51 +0100, Olivier Mueller wrote: > Hello, > This afternoon I wanted to upgrade to 7.1 two good old dell PowerEdge > servers which were running FreeBSD 6.x. It went fine and quickly on the 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. Tracking the megarc memory corruption (and general amr(4) problems with the PERC4) at: http://www.freebsd.org/cgi/query-pr.cgi?pr=128082 ~BAS > poweredge 1950, but it failed completely on the poweredge 1850. > > Facts: > > - boot cd and setup / operation of freebsd 6.x or 7.0 is fine > Message log abstract: > $ uname -v > FreeBSD 7.0-RELEASE-p7 #0: Sun Dec 21 08:31:52 UTC 2008 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > $ dmesg|grep amr > 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) > Trying to mount root from ufs:/dev/amrd0s1a > > - boot cd of 7.1 fails because the installed doesn't see any harddisk. > Message log abstract: > amr0: adapter is busy > amr0: adapter is busy > amr0: delete logical drives supported by controller > > > I also tried to setup 7.0, and then upgrade to 7.1 with freebsd-update, > but then it fails exactly like with the 7.1 boot CD > (7.1-RELEASE-amd64-disc1.iso). Screenshot: > http://omx.ch/om/stuff/pe1850bsd71error.jpg > > BIOS Message about the Controller on system startup: > PowerEdge Expandable RAID COntroller BIOS, (c) 2006 LSI Logic > Corporation > > I'm not sure what I can try next... I'd still like to be able to run > 7.1 on this host as well as on several other old but still fine 1850. Is > my system simply too old? Why is my adapter "busy" under 7.1? What > would you try? I checked the relnotes as well, but saw nothing helpful > about my problem there. > > regards & thanks in advance for any feedback, > Olivier > > > _______________________________________________ > 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 Thu Feb 12 05:09:10 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 4C323106564A for ; Thu, 12 Feb 2009 05:09:10 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-173-50-231-101.ptldor.fios.verizon.net [173.50.231.101]) by mx1.freebsd.org (Postfix) with ESMTP id A6C758FC21 for ; Thu, 12 Feb 2009 05:09:09 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: by sopwith.solgatos.com (Postfix, from userid 66) id A4FD1B64F; Wed, 11 Feb 2009 21:08:08 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id SAA18166; Wed, 11 Feb 2009 18:59:22 GMT Message-Id: <200902111859.SAA18166@sopwith.solgatos.com> To: freebsd-hardware@freebsd.org In-reply-to: Your message of "Wed, 11 Feb 2009 09:33:37 +0100." <200902110833.n1B8XbLo096837@lurza.secnetix.de> Date: Wed, 11 Feb 2009 10:59:22 +0000 From: Dieter Subject: Re: SATA PCI adapter recommendation 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, 12 Feb 2009 05:09:10 -0000 > I plan to put a SATA drive in an old PATA-only PC, so I'm > looking for an appropriate adapter card. A cheap card > should suffice, I do not need RAID, and it does not have > to be SATA-300. > 1. Based on Silicon Image Sil-3x12 chip: > http://www.digital-data.de/download/datasheets/111816_Datasheet.pdf > I've read a few scary things about SIL chips on the lists, > so I guess I'd better try to avoid that one. The bad things I've read are all regarding the first generation SIL chips with FreeBSD. They work fine with NetBSD (and other OSes) so the problem is with the FreeBSD device driver. I haven't seen anything (pro or con) about the 2nd generation chips e.g. Sil 3124 with FreeBSD. The 2nd gen chips are supposed to be much better and faster than the 1st gen chips. Does anyone have experience to report with the Sil 3124 (PCI), Sil 3132 (PCIe) or other 2nd generation Sil chip with FreeBSD? > Finally, a small question: I assume that all of those > SATA controllers do have their own BIOS, so I can boot > from them, right? It would be annoying to have to keep > an old PATA disk in that box just to be able to boot. This may depend on the firmware on the mainboard? From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 12 08:53: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 EC124106566B for ; Thu, 12 Feb 2009 08:53:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id BA5B28FC0A for ; Thu, 12 Feb 2009 08:53:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id f6so252192rvb.43 for ; Thu, 12 Feb 2009 00:53:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=KQnvN886B9zr1rPxj59SEofeyJS14cgJlN3oPQHuSDc=; b=PkNaDSw3zDb3iZTH+DopaUGkjoqQnsihpPo9uCUOR1xEmEEJ6pstoOjEl7ijH0iKE7 +LzA3wBiLLxion81GaCQlxZT8sQ9DOSlVFHoCggRym5P9/TQJ2FbUFJdUenIHPWfKBX1 63z4GZnc1aTA5nGXiEIjDCpTrN7gGLPSsW578= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=hzP67jGl5YNkIUXG19jD/nXgCKwSgVLEZZCr2IElACQ6zgQAgrTSHWBb2i0dJw9TzL yaCPDE4/8J7WZkiebla3c1FoZUjG4U+WWbBHMuQofk6ceN0biExckBY9WudwDD8qzzYn e5AlO70bFCt3B7/Kme7bj20cR/lDMjDBHWk/0= Received: by 10.140.250.14 with SMTP id x14mr417093rvh.278.1234428809491; Thu, 12 Feb 2009 00:53:29 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id f21sm2159794rvb.2.2009.02.12.00.53.26 (version=SSLv3 cipher=RC4-MD5); Thu, 12 Feb 2009 00:53:28 -0800 (PST) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Thu, 12 Feb 2009 17:56:07 +0900 From: Pyun YongHyeon Date: Thu, 12 Feb 2009 17:56:07 +0900 To: Nicolas GORALSKI Message-ID: <20090212085607.GE6313@michelle.cdnetworks.co.kr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-hardware@freebsd.org Subject: Re: Looking for ethernet expresscard X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2009 08:53:30 -0000 On Tue, Feb 10, 2009 at 09:49:10AM +0100, Nicolas GORALSKI wrote: > Hi everybody > > I've a laptop with a sis191 ethernet card and it doesn't work. > NDIS with (XP|2K|98) drivers make my kernel crash. > See http://lists.freebsd.org/pipermail/freebsd-drivers/2008-April/000685.html I don't know whether it supports SiS191 or not. From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 12 13:52:23 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 DB50510656E6 for ; Thu, 12 Feb 2009 13:52:23 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from n61.bullet.mail.sp1.yahoo.com (n61.bullet.mail.sp1.yahoo.com [98.136.44.37]) by mx1.freebsd.org (Postfix) with SMTP id A23578FC13 for ; Thu, 12 Feb 2009 13:52:23 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from [216.252.122.216] by n61.bullet.mail.sp1.yahoo.com with NNFMP; 12 Feb 2009 13:52:23 -0000 Received: from [69.147.84.102] by t1.bullet.sp1.yahoo.com with NNFMP; 12 Feb 2009 13:52:23 -0000 Received: from [127.0.0.1] by omp206.mail.sp1.yahoo.com with NNFMP; 12 Feb 2009 13:52:23 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 424248.14405.bm@omp206.mail.sp1.yahoo.com Received: (qmail 37812 invoked by uid 60001); 12 Feb 2009 13:52:23 -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:MIME-Version:Content-Type:Message-ID; b=JRLU1YYn+8kdUCjocPPKku4QYghhNvQO4SsCjAZpSpZVzSwm+rt+HwPYO6YWM+dsoHZfw2jKXfM9JHCg0SRVp7fMZbRbhlhhGqC4x5x1pWx8/N59n7u87gaqCH3FjavgAV1Njt+T8xW3oss9jRw4q/Wh14vKigOHSIPnlUffCy4=; X-YMail-OSG: iHrXH_wVM1nx2Vt_m06acmi9M08vnprzk7mEg87jY3xB26kL9NTW6zdR8etVtacQc2nYYYet.WG4h9xJPNAaFbkrjMPZVLKLEStcyE5yEmCEp6hXUdCySpG5O7.0d6KzqIGN0G2VWvWnxzh22k40BW2r3WwMN6bRJqQw79Vy8UtL2OHXHpJ_._ezFw-- Received: from [58.71.34.137] by web45806.mail.sp1.yahoo.com via HTTP; Thu, 12 Feb 2009 05:52:22 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Thu, 12 Feb 2009 05:52:22 -0800 (PST) From: Won De Erick To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <243201.37742.qm@web45806.mail.sp1.yahoo.com> Subject: 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: Thu, 12 Feb 2009 13:52:24 -0000 Hi All, I've done the following procedure to verify the unstable date/time being recorded in the hardware clock. I'm using IBM x343 with FreeBSD 6.2: 1. Rebooted the box. Entered a wrong date/time as: Date: December 1, 2008 Time: 12:00:00 2. When the box was UP'ed, displayed the date (the box is sync'ed with an NTP server during start-up). #date Thu Feb 12 15:37:57 PHT 2009 It seems correct. 3. Change with a wrong date/time again, then displayed. # date 0812301200 Tue Dec 30 12:00:00 PHT 2008 # date Tue Dec 30 12:00:14 PHT 2008 It seems correct. 4. Synchronized the date/time with an NTP Server. Then, displayed the date. # ntpdate ph.pool.ntp.org 12 Feb 15:40:59 ntpdate[3094]: step time server 202.92.128.201 offset 3814728.167216 sec # date Thu Feb 12 15:41:33 PHT 2009 It seems correct. 5. Rebooted the box, then verified the system date/time at the BIOS config. System Time 07:43:50 System Date Thu 02/12/2009 Wrong TIME? I think the hardware clock was not properly SYNCed with the kernel clock. I've verified this with other box, and same thing happened. Is there any issues on using date and ntpdate? Thanks, Won From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 12 14:34:43 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 31602106564A for ; Thu, 12 Feb 2009 14:34:43 +0000 (UTC) (envelope-from guy@crossflight.co.uk) Received: from bc30o.crossflight.co.uk (bc30o.crossflight.co.uk [195.172.72.196]) by mx1.freebsd.org (Postfix) with ESMTP id AACFD8FC0A for ; Thu, 12 Feb 2009 14:34:42 +0000 (UTC) (envelope-from guy@crossflight.co.uk) X-ASG-Debug-ID: 1234448210-499c003a0000-e7p9Ku X-ASG-Debug-ID: 1234448210-499c003a0000-e7p9Ku X-Barracuda-URL: http://195.172.72.196:8000/cgi-bin/mark.cgi Received: from vsmtpe.crossflight.co.uk (vsmtpe.crossflight.co.uk [195.172.72.209]) by bc30o.crossflight.co.uk (Spam Firewall) with ESMTP id 11B7D4F2C7; Thu, 12 Feb 2009 14:16:50 +0000 (GMT) Received: from vsmtpe.crossflight.co.uk (vsmtpe.crossflight.co.uk [195.172.72.209]) by bc30o.crossflight.co.uk with ESMTP id O2LSZn77CJQkLzof; Thu, 12 Feb 2009 14:16:50 +0000 (GMT) Received: from [172.16.72.7] (northropi.crossflight.co.uk [172.16.72.7]) by vsmtpe.crossflight.co.uk (8.14.2/8.14.2) with ESMTP id n1CEGo6V067955; Thu, 12 Feb 2009 14:16:50 GMT (envelope-from guy@crossflight.co.uk) Message-ID: <49942F54.4040201@crossflight.co.uk> Date: Thu, 12 Feb 2009 14:16:52 +0000 From: Guy Dawson User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: won.derick@yahoo.com X-ASG-Orig-Subj: Re: Hardware clock is not SYNC'ed with kernel clock by ntpdate? References: <243201.37742.qm@web45806.mail.sp1.yahoo.com> In-Reply-To: <243201.37742.qm@web45806.mail.sp1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Barracuda-Connect: vsmtpe.crossflight.co.uk[195.172.72.209] X-Barracuda-Start-Time: 1234448211 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at crossflight.co.uk X-Barracuda-Spam-Score: -1002.00 X-Barracuda-Spam-Status: No, SCORE=-1002.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=1000.0 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: Thu, 12 Feb 2009 14:34:43 -0000 Does the hardware clock show the correct UTC time? Your time zone appears to be PHT but the harware clock should be keeping UTC time. Guy Won De Erick wrote: > Hi All, > > I've done the following procedure to verify the unstable date/time being recorded in the hardware clock. > > I'm using IBM x343 with FreeBSD 6.2: > > 1. Rebooted the box. Entered a wrong date/time as: > Date: December 1, 2008 > Time: 12:00:00 > > 2. When the box was UP'ed, displayed the date (the box is sync'ed with an > NTP server during start-up). > > #date > Thu Feb 12 15:37:57 PHT 2009 > > It seems correct. > > 3. Change with a wrong date/time again, then displayed. > # date 0812301200 > Tue Dec 30 12:00:00 PHT 2008 > > # date > Tue Dec 30 12:00:14 PHT 2008 > > It seems correct. > > 4. Synchronized the date/time with an NTP Server. Then, displayed the date. > > # ntpdate ph.pool.ntp.org > 12 Feb 15:40:59 ntpdate[3094]: step time server 202.92.128.201 > offset 3814728.167216 sec > > # date > Thu Feb 12 15:41:33 PHT 2009 > > It seems correct. > > 5. Rebooted the box, then verified the system date/time at the BIOS config. > > System Time 07:43:50 > System Date Thu 02/12/2009 > > > Wrong TIME? I think the hardware clock was not properly SYNCed with the kernel clock. I've verified this with other box, and same thing happened. > > Is there any issues on using date and ntpdate? > > Thanks, > > Won > > > > > > > _______________________________________________ > 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" -- Guy -- -------------------------------------------------------------------- Guy Dawson I.T. Systems Manager Crossflight Ltd guy@crossflight.co.uk 07973 797819 01753 776104 ******************************************************************* This message contains the views and opinions of a Crossflight Limited employee and at this stage are in no way a direct representation of Crossflight Limited. Crossflight Limited is an international express courier, mailing and logistics service provider, and is authorised and regulated by the Financial Services Authority to conduct General Insurance Business. This communication and any attachments are confidential and may be protected from disclosure. We endorse no advice or opinion contained in this communication that is not the subject of a contract between the recipient and ourselves. If you have received it in error please notify us immediately and note that any storage, use or disclosure is strictly prohibited and may be unlawful. Those communicating with us by electronic mail will be deemed to have accepted the risks associated with interception, amendment, loss and late or incomplete delivery. They will also be deemed to have consented to our intercepting and monitoring such communications. This footnote also confirms that this message has been checked for the presence of computer viruses. We strongly recommend that you check this email with your own virus software as Crossflight Limited will not be held responsible for any damage caused by viruses as a result of opening this email. ******************************************************************* From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 12 14:37:17 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 4B1A0106568C for ; Thu, 12 Feb 2009 14:37:17 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from n22.bullet.mail.mud.yahoo.com (n22.bullet.mail.mud.yahoo.com [68.142.206.161]) by mx1.freebsd.org (Postfix) with SMTP id 135068FC24 for ; Thu, 12 Feb 2009 14:37:16 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from [68.142.200.227] by n22.bullet.mail.mud.yahoo.com with NNFMP; 12 Feb 2009 14:37:16 -0000 Received: from [68.142.201.73] by t8.bullet.mud.yahoo.com with NNFMP; 12 Feb 2009 14:37:16 -0000 Received: from [127.0.0.1] by omp425.mail.mud.yahoo.com with NNFMP; 12 Feb 2009 14:37:16 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 668580.99677.bm@omp425.mail.mud.yahoo.com Received: (qmail 20571 invoked by uid 60001); 12 Feb 2009 14:37:16 -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:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=gNv/c9s30+WMkbLBo9B/0SotQFHsz/680gspEr60k0u2j3OZg74a6uaZGxCduSKKGP6B0fz6ZuywOcRWfwRDPyyRP7u/UN3wbtfuFI7I1GXPsvwJAs2u6WRGGUjfCb/+ZowyPXK3dW/hDjrpjFS8iijnu7Hi+s4Wo8u78NOt23E=; X-YMail-OSG: jCOoyyUVM1ljyVr58Et.IH2HiFe6bvVqFSIyOgxtNQFW.oqohi5zlJA276Lc4wHZgGPoViwt7FFri2HjMDWl.DM_Nb3MhyJhIBdrw9vU4h1lCcSlWLHZmHylDfHsmqOuj0KMJaHhjVKoaASCYdJPf9py1DusFX_5s7tsjkaP1_mMvfjpnuJGGNzhzA-- Received: from [58.71.34.137] by web45809.mail.sp1.yahoo.com via HTTP; Thu, 12 Feb 2009 06:37:15 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Thu, 12 Feb 2009 06:37:15 -0800 (PST) From: Won De Erick To: Guy Dawson In-Reply-To: <49942F54.4040201@crossflight.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <167460.20536.qm@web45809.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: Thu, 12 Feb 2009 14:37:17 -0000 --- On Thu, 2/12/09, Guy Dawson wrote: > Does the hardware clock show the correct UTC time? > > Your time zone appears to be PHT but the harware clock > should be keeping UTC time. This is what I only saw in the BIOS config: System Time 07:43:50 System Date Thu 02/12/2009 No setting for time zone. > > Guy > > Won De Erick wrote: > > Hi All, > > > > I've done the following procedure to verify the > unstable date/time being recorded in the hardware clock. > > > > I'm using IBM x343 with FreeBSD 6.2: > > > > 1. Rebooted the box. Entered a wrong date/time as: > > Date: December 1, 2008 > > Time: 12:00:00 > > > > 2. When the box was UP'ed, displayed the date (the > box is sync'ed with an NTP server during start-up). > > #date > > Thu Feb 12 15:37:57 PHT 2009 > > > > It seems correct. > > > > 3. Change with a wrong date/time again, then > displayed. # date 0812301200 > > Tue Dec 30 12:00:00 PHT 2008 > > # date > > Tue Dec 30 12:00:14 PHT 2008 > > > > It seems correct. > > > > 4. Synchronized the date/time with an NTP Server. > Then, displayed the date. > > # ntpdate ph.pool.ntp.org > > 12 Feb 15:40:59 ntpdate[3094]: step time server > 202.92.128.201 offset 3814728.167216 sec > > # date > > Thu Feb 12 15:41:33 PHT 2009 > > > > It seems correct. > > > > 5. Rebooted the box, then verified the system > date/time at the BIOS config. System Time 07:43:50 > > System Date Thu 02/12/2009 > > > > Wrong TIME? I think the hardware clock was not > properly SYNCed with the kernel clock. I've verified > this with other box, and same thing happened. > > > > Is there any issues on using date and ntpdate? > > > > Thanks, > > > > Won > > > > > > > > > > > > _______________________________________________ > > 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" > > > -- Guy > -- > -------------------------------------------------------------------- > Guy Dawson I.T. Systems Manager > Crossflight Ltd > guy@crossflight.co.uk 07973 797819 > 01753 776104 > > > ******************************************************************* > This message contains the views and opinions of a > Crossflight > Limited employee and at this stage are in no way a direct > representation of Crossflight Limited. > > Crossflight Limited is an international express courier, > mailing > and logistics service provider, and is authorised and > regulated by > the Financial Services Authority to conduct General > Insurance > Business. This communication and any attachments are > confidential > and may be protected from disclosure. We endorse no advice > or > opinion contained in this communication that is not the > subject of > a contract between the recipient and ourselves. > > If you have received it in error please notify us > immediately and > note that any storage, use or disclosure is strictly > prohibited and > may be unlawful. Those communicating with us by electronic > mail > will be deemed to have accepted the risks associated with > interception, amendment, loss and late or incomplete > delivery. > They will also be deemed to have consented to our > intercepting and > monitoring such communications. > > This footnote also confirms that this message has been > checked for > the presence of computer viruses. We strongly recommend > that you > check this email with your own virus software as > Crossflight > Limited will not be held responsible for any damage caused > by > viruses as a result of opening this email. > ******************************************************************* From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 13 01:50:39 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 5F13C10656D4 for ; Fri, 13 Feb 2009 01:50:39 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from n28.bullet.mail.mud.yahoo.com (n28.bullet.mail.mud.yahoo.com [68.142.206.223]) by mx1.freebsd.org (Postfix) with SMTP id 1A15F8FC13 for ; Fri, 13 Feb 2009 01:50:38 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from [68.142.194.244] by n28.bullet.mail.mud.yahoo.com with NNFMP; 13 Feb 2009 01:50:38 -0000 Received: from [68.142.201.73] by t2.bullet.mud.yahoo.com with NNFMP; 13 Feb 2009 01:50:38 -0000 Received: from [127.0.0.1] by omp425.mail.mud.yahoo.com with NNFMP; 13 Feb 2009 01:50:38 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 515692.83354.bm@omp425.mail.mud.yahoo.com Received: (qmail 36599 invoked by uid 60001); 13 Feb 2009 01:50:37 -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:Message-ID; b=Yk+9JNhL1RmIZxFg7QlD8A9/w/46lUfMES0rdS6ITbvjaN290o0+KGl8GfSYKVikgTMfvdY91efOZlAIUWBSNjNL5hKJfnLjnQ10cXQLZRomtNptGmUAbO+qF44gkKpBw0Yfyxel1gfxB6e5RWtKCaPQQ6GOclijlRYVKA7vdD8=; X-YMail-OSG: z7US.PsVM1nuNa9wciZ5NUHUURJbNA91iSjFRPRkrUZhDcFQDpVNDVsmXuUIdGNjFevoMFRL1S5mYS4aClf4_wKwBzQuw0omVu4nZd9AqJEo14Y.YJslv_hGyrHIERriIvP5nuR7EAb_gPxxsAvDQ5OUDq4Ag6fkwdrm0eoR3p_w9hZ.j2BQ5uLY_z.5hwURGvzP5_L2jlPMDpwZw8SInUQ15p8- Received: from [58.71.34.137] by web45815.mail.sp1.yahoo.com via HTTP; Thu, 12 Feb 2009 17:50:37 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Thu, 12 Feb 2009 17:50:37 -0800 (PST) From: Won De Erick To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <752190.34892.qm@web45815.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: Fri, 13 Feb 2009 01:50:39 -0000 Does anyone know what is going on with my system? --- On Thu, 2/12/09, Won De Erick wrote: > From: Won De Erick > --- On Thu, 2/12/09, Guy Dawson wrote: > > Does the hardware clock show the correct UTC time? > > > > Your time zone appears to be PHT but the harware clock > > should be keeping UTC time. > > This is what I only saw in the BIOS config: > > System Time 07:43:50 > System Date Thu 02/12/2009 > > No setting for time zone. > > > > > Guy > > > > Won De Erick wrote: > > > Hi All, > > > > > > I've done the following procedure to verify the > > > unstable date/time being recorded in the hardware clock. > > > > > > I'm using IBM x343 with FreeBSD 6.2: > > > > > > 1. Rebooted the box. Entered a wrong date/time as: > > > Date: December 1, 2008 > > > Time: 12:00:00 > > > > > > 2. When the box was UP'ed, displayed the date (the > > > box is sync'ed with an NTP server during > > > start-up). > > > #date > > > Thu Feb 12 15:37:57 PHT 2009 > > > > > > It seems correct. > > > > > > 3. Change with a wrong date/time again, then > > > displayed. # date 0812301200 > > > Tue Dec 30 12:00:00 PHT 2008 > > > # date > > > Tue Dec 30 12:00:14 PHT 2008 > > > > > > It seems correct. > > > > > > 4. Synchronized the date/time with an NTP Server. > > > Then, displayed the date. > > > # ntpdate ph.pool.ntp.org > > > 12 Feb 15:40:59 ntpdate[3094]: step time > > > server > > > 202.92.128.201 offset 3814728.167216 sec > > > # date > > > Thu Feb 12 15:41:33 PHT 2009 > > > > > > It seems correct. > > > > > > 5. Rebooted the box, then verified the system > > > date/time at the BIOS config. System Time > > > 07:43:50 > > > System Date Thu 02/12/2009 > > > > > > Wrong TIME? I think the hardware clock was not > > > properly SYNCed with the kernel clock. I've > > > verified > > > this with other box, and same thing happened. > > > > > > Is there any issues on using date and ntpdate? > > > > > > Thanks, > > > > > > Won > > > > > > > > > > > > > > > > > > _______________________________________________ > > > 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" > > > > > > -- Guy > > -- > > > -------------------------------------------------------------------- > > Guy Dawson I.T. Systems Manager > > > Crossflight Ltd > > guy@crossflight.co.uk 07973 797819 > > > 01753 776104 > > > > > > From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 13 03:04: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 7E72B106566B for ; Fri, 13 Feb 2009 03:04:28 +0000 (UTC) (envelope-from olivier@gautherot.net) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 39BC88FC17 for ; Fri, 13 Feb 2009 03:04:27 +0000 (UTC) (envelope-from olivier@gautherot.net) Received: by yw-out-2324.google.com with SMTP id 2so630766ywt.13 for ; Thu, 12 Feb 2009 19:04:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.150.158.10 with SMTP id g10mr1577014ybe.209.1234492907369; Thu, 12 Feb 2009 18:41:47 -0800 (PST) In-Reply-To: <752190.34892.qm@web45815.mail.sp1.yahoo.com> References: <752190.34892.qm@web45815.mail.sp1.yahoo.com> Date: Thu, 12 Feb 2009 23:41:47 -0300 Message-ID: From: Olivier Gautherot To: won.derick@yahoo.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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, 13 Feb 2009 03:04:28 -0000 Hi Won, On Thu, Feb 12, 2009 at 10:50 PM, Won De Erick wrote: > Does anyone know what is going on with my system? > > > --- On Thu, 2/12/09, Guy Dawson wrote: > > > Does the hardware clock show the correct UTC time? > > > > > > Your time zone appears to be PHT but the harware clock > > > should be keeping UTC time. I back Guy's comment: the difference you see is indeed the time difference between UTC and PHT. If both your systems reboot in UTC, I would bet on the timezone you set in sysinstall more than the RTC. Please refer to section 2.10.8 in this (RTC in UTC - answer "yes" to the second question): http://www.freebsd.org/doc/en/books/handbook/install-post.html It may solve your problems. > > > > This is what I only saw in the BIOS config: > > > > System Time 07:43:50 > > System Date Thu 02/12/2009 > > > > No setting for time zone. BIOS generally do not have timezone setting . Hope it helps Cheers -- Olivier Gautherot olivier@gautherot.net Cel:+56 98 730 9361 www.gautherot.net http://www.linkedin.com/in/ogautherot From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 13 09:15:46 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 B9FC1106566B for ; Fri, 13 Feb 2009 09:15:46 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from n78.bullet.mail.sp1.yahoo.com (n78.bullet.mail.sp1.yahoo.com [98.136.44.42]) by mx1.freebsd.org (Postfix) with SMTP id 992898FC1C for ; Fri, 13 Feb 2009 09:15:46 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from [69.147.84.145] by n78.bullet.mail.sp1.yahoo.com with NNFMP; 13 Feb 2009 09:00:08 -0000 Received: from [69.147.65.163] by t8.bullet.mail.sp1.yahoo.com with NNFMP; 13 Feb 2009 09:15:46 -0000 Received: from [127.0.0.1] by omp408.mail.sp1.yahoo.com with NNFMP; 13 Feb 2009 09:15:46 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 317500.27202.bm@omp408.mail.sp1.yahoo.com Received: (qmail 40996 invoked by uid 60001); 13 Feb 2009 09:15:46 -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:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=DChKyVSQ1Z/57icfR3c/3/WI9T1Dx3tw35ydtCpBvX5uYHDzDzGN8CzJkFqvsqJWutihyRzzocz/B+0vXJ/gCfGBTjYZjMmYGhSnHfaIaA5Z+yPGY1F+KM+4fQ75qCqrMwtJ7NPFkk2L2xSu+dNDrB2kQtmgfuxiqk8Mx1zub00=; X-YMail-OSG: QjpAOS4VM1kVJWFwz5AZSdKu2d0vkvg1.Id4Cv1Aew90JAc0Z1gXjoHC7eKYZM6oGAuHfT3gHeI75.4eG8MxKA7tDlcOjKP89f9mwjf3gf460jq0zq09WBom2a_dCa.b4mR4ammjb_zeTl0oP6ShBT7qJz7Ms5VhEDP5A.B5cHTEu2Du44dqchlieQ-- Received: from [58.71.34.137] by web45805.mail.sp1.yahoo.com via HTTP; Fri, 13 Feb 2009 01:15:46 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Fri, 13 Feb 2009 01:15:46 -0800 (PST) From: Won De Erick To: Olivier Gautherot In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <228216.40672.qm@web45805.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: Fri, 13 Feb 2009 09:15:47 -0000 --- On Fri, 2/13/09, Olivier Gautherot wrote: > Hi Won, > > On Thu, Feb 12, 2009 at 10:50 PM, Won De Erick > wrote: > > > Does anyone know what is going on with my system? > > > > > --- On Thu, 2/12/09, Guy Dawson > > > wrote: > > > > Does the hardware clock show the correct UTC > > > > Dtime? > > > > > > > > Your time zone appears to be PHT but the > > > > harware clock > > > > should be keeping UTC time. > > > I back Guy's comment: the difference you see is indeed > the time difference > between UTC and PHT. I understand this. > If both your systems reboot in UTC, I would bet on the > timezone you set in > sysinstall more than the RTC. > Can you elaborate more on this? I was expecting that when I did the ff: # ntpdate ph.pool.ntp.org 12 Feb 15:40:59 ntpdate[3094]: step time server 202.92.128.201 offset 3814728.167216 sec # date Thu Feb 12 15:41:33 PHT 2009 the time displayed will be reflected on the hardware. However, what I've got is the UTC-based. System Time 07:43:50 System Date Thu 02/12/2009 > Please refer to section 2.10.8 in this (RTC in UTC - answer > "yes" to the > second question): > http://www.freebsd.org/doc/en/books/handbook/install-post.html > It may solve your problems. > > > > > > > > > This is what I only saw in the BIOS config: > > > > > > System Time 07:43:50 > > > System Date Thu 02/12/2009 > > > > > > No setting for time zone. > > > BIOS generally do not have timezone setting . > > Hope it helps > Cheers > -- > Olivier Gautherot > olivier@gautherot.net > Cel:+56 98 730 9361 > www.gautherot.net > http://www.linkedin.com/in/ogautherot > _______________________________________________ > 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 Fri Feb 13 10:45:58 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 AFEF11065738 for ; Fri, 13 Feb 2009 10:45:58 +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 2DE208FC16 for ; Fri, 13 Feb 2009 10:45:57 +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 n1DAjt6p031129; Fri, 13 Feb 2009 11:45:56 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n1DAjtxw031128; Fri, 13 Feb 2009 11:45:55 +0100 (CET) (envelope-from olli) Date: Fri, 13 Feb 2009 11:45:55 +0100 (CET) Message-Id: <200902131045.n1DAjtxw031128@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG, won.derick@yahoo.com In-Reply-To: <243201.37742.qm@web45806.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]); Fri, 13 Feb 2009 11:45:56 +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: Fri, 13 Feb 2009 10:45:59 -0000 Hello, Do you have a file /etc/wall_cmos_clock on your system? If so, that would explain the behaviour very well. If you want your CMOS clock run at UTC instead of local time, you have to remove that file. Apart from the Handbook you might also have a look at the adjkerntz(8) manual page. It explains the mechanism used to maintain the time zone difference (if any) between FreeBSD and the CMOS clock. 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 "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 13 15:47: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 664EC1065675 for ; Fri, 13 Feb 2009 15:47:00 +0000 (UTC) (envelope-from roy.badami@globalgraphics.com) Received: from queeg.cam.harlequin.co.uk (queeg.cam.harlequin.co.uk [82.1.12.146]) by mx1.freebsd.org (Postfix) with ESMTP id E16F98FC21 for ; Fri, 13 Feb 2009 15:46:59 +0000 (UTC) (envelope-from roy.badami@globalgraphics.com) Received: from post.cam.harlequin.co.uk (post.cam.harlequin.co.uk [172.16.130.105]) by queeg.cam.harlequin.co.uk (8.13.8/8.13.8) with ESMTP id n1DFOTOK006894 for ; Fri, 13 Feb 2009 15:24:29 GMT (envelope-from roy.badami@globalgraphics.com) Received: from erbium.cam.harlequin.co.uk (dhcp-vlan200-cam404.cam.harlequin.co.uk [172.16.159.148]) by post.cam.harlequin.co.uk (8.12.10/8.12.10) with ESMTP id n1DFOSev020585; Fri, 13 Feb 2009 15:24:28 GMT (envelope-from roy.badami@globalgraphics.com) From: Roy Badami MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18837.37036.643000.795911@erbium.cam.harlequin.co.uk> Date: Fri, 13 Feb 2009 15:24:28 +0000 To: freebsd-hardware@freebsd.org X-Mailer: VM 7.11 under Emacs 21.2.1 Subject: SIIG Cyber Serial 4S and system hang 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, 13 Feb 2009 15:47:01 -0000 Can't find anyone else having the same problem as me, so I'm hoping this is the right place to post... The short version: I have a FreeBSD 7.1-RELEASE-p2 machine with a SIIG CyberSerial 4S card (one of the ones with the 10x clock) and I can fairly consistently make the machine hang by accessing the serial port. The long version: The machine is an Intel D815EEA ('Easton') motherboard with an 866 MHz Pentium III processor, and is running FreeBSD 7.1-RELEASE-p2. The kernel configuration is identical to GENERIC except that device puc has been uncommented. The machine has one serial port on the back (not sure if there's a second on the motherboard which isn't brought out) and I've installed a SIIG CyberSerial 4S card which identifies itself as: puc0: port 0xcf20-0xcf3f,0xcf00-0xcf1f mem 0xfc9fc000-0xfc9fcfff,0xfc9fb000-0xfc9fbfff irq 11 at device 11.0 on pci1 I believe this is one of the cards with the 10x clock, the patches for which finally made it to prime time in 7.1 (this card didn't work at all for me in 7.0). Initially I had smstools-3.1.3_1 running on cuad0 (m/b serial port) talking to an external GSM terminal for sending SMS messages and this worked fine. I then attached a serial-attached thermometer (that we built ourselves) to cuau0 (the first port on the CyberSerial) and started the temperature monitoring daemon, thermd (a perl script we wrote ourselves). When I started the temperature monitoring daemon from the command line, the system pretty consistently immediately locked up - both my ssh session and the physical console stopped responding - the Caps Lock light wouldn't even toggle. The really odd thing though is that now I swapped the two applications round, so the thermometer is on cuad0 and the GSM terminal is on cuau0 then everything is working fine. I've attached the thermd script in case the way it accesses the tty sheds any light as to what was going on, but unfortunately it's not possible to reproduce the hang without the (custom built) thermometer attached to the serial port. Although things seem to be working, I'd like to get to the bottom of this so that I can be confident that the machine won't freeze again in the future - and I have more serial applications I need to run on this server. Any suggestions as to how to proceed - short of changing to a different model of serial card? Thanks, -roy -------------------- #!/usr/local/bin/perl5 $ALERT_TEMP = 26; #$ALERT_TEMP = 32; $ALERT_INTERVAL = 60*20; $ALERT_THRESHOLD_FALLING = 2; $ALERT_THRESHOLD_RISING = 2; $ALERT = 'alert_hall'; $tempfile = '/usr/local/etc/temperature'; $pager = '/usr/local/bin/pager'; $debug = 0; use POSIX; use Fcntl; die "No tty specified" unless $ARGV[0]; $tty=$ARGV[0]; $tty = "/dev/$tty" unless $tty =~ m'/'; &open_tty(\*TTY, $tty); open TEMP, "+> $tempfile" or die "Can't open $tempfile"; &daemon unless $debug; for (;;) { until (&check_thermometer(\*TTY)) { print STDERR "Error communicating with thermometer" unless $error; $error = 1; #No need to wait, since there's a wait in check_thermometer } print STDERR "Communication established" if $error; $error = 0; for (;;) { $temp = &read_thermometer(\*TTY); if (!defined($temp)) { print STDERR "Error reading thermometer"; $error = 1; last; } &process_temp($temp); sleep 10; } } exit; sub open_tty { my ($FILE, $tty) = @_; my ($termios,$iflag,$oflag,$cflag,$lflag); open $FILE, "+> $tty" or die "Can't open $tty"; $termios = POSIX::Termios->new; $termios->getattr(fileno $FILE); #iflag $iflag = $termios->getiflag; $iflag &= ~(BRKINT|PARMRK|ISTRIP|INLCR|IGNCR|ICRNL|IXON|IXOFF|IXANY|IMAXBEL); $iflag |= (IGNBRK|IGNPAR|INPCK); $termios->setiflag($iflag); #oflag $oflag = $termios->getoflag; $oflag &= ~OPOST; $termios->setoflag($oflag); #cflag $cflag = $termios->getcflag; $cflag = ($cflag & ~CSIZE) | CS8; $cflag &= ~(CSTOPB|PARENB|HUPCL|CCTR_OFLOW|CRTS_IFLOW|MDMBUF); $cflag |= (CREAD|CLOCAL); $termios->setcflag($cflag); #lflag $lflag = $termios->getlflag; $lflag &= ~(ECHO|ECHOCTL|ISIG|ICANON|IEXTEN); $termios->setlflag($lflag); #reads time out after 2 seconds $termios->setcc(VMIN, 0); $termios->setcc(VTIME, 20); #baud rate $termios->setispeed(B9600); $termios->setospeed(B9600); #doit! $termios->setattr(fileno $FILE, TCSANOW); } sub check_thermometer { my ($TTY) = @_; my ($fl, $buffer, $result); $fl = fcntl $TTY, &F_GETFL, 0; $fl |= &O_NONBLOCK; fcntl $TTY, &F_SETFL, $fl; sysread $TTY, $buffer, 8192; $fl &= ~&O_NONBLOCK; fcntl $TTY, &F_SETFL, $fl; defined(syswrite $TTY, 'S', 1) or die "Error writing to tty"; defined(sysread $TTY, $buffer, 1) or die "Error reading from tty"; #Allow thermometer to recover sleep 1; $result = ($buffer eq 'S'); if ($debug) { print 'check_thermometer: ', ($result?'OK':'Failed'), "\n"; } $result; } sub read_thermometer { my ($TTY) = @_; my ($buffer, $res_string); defined(syswrite $TTY, 'T', 1) or die "Error writing to tty"; defined(sysread $TTY, $buffer, 1) or die "Error reading from tty"; sleep 1; $res_string = ($buffer?sprintf("%03d",ord($buffer)):'ERR'); lseek (fileno TEMP, 0, &SEEK_SET); syswrite (TEMP, $res_string, 3); if ($debug) { print "read_thermometer: $res_string\n" } $buffer ? ord($buffer) : undef; } sub process_temp { my ($temp) = @_; my ($time); $time = time; if ($temp >= $ALERT_TEMP && (!$alert || ($temp >= $last_alert_temp + $ALERT_THRESHOLD_RISING && $time-$last_alert_time > $ALERT_INTERVAL))) { if ($alert) { &alert("Temperature rising, now ${temp}C"); } else { &alert("Over temperature alarm: ${temp}C"); } $alert = 1; $last_alert_temp = $temp; $last_alert_time = $time; } elsif ($alert && $temp <= ($last_alert_temp - $ALERT_THRESHOLD_FALLING)) { if ($temp < $ALERT_TEMP) { &alert("Temperature now normal at ${temp}C"); $alert = 0; } elsif ($time-$last_alert_time > $ALERT_INTERVAL) { &alert("Temperature dropping, now ${temp}C"); $last_alert_temp = $temp; $last_alert_time = $time; } } } sub alert { my ($msg) = @_; print STDERR "thermometer: $msg\n"; system ("$pager -p $ALERT $msg"); } sub daemon { my ($pid); if ($daemon) { return } $daemon = 1; open NULL, "/dev/null" or die "Can't open /dev/null"; open CONSOLE, "/dev/console" or die "Can't open /dev/console"; $pid = fork; die "Can't fork" unless defined $pid; exit if $pid; # Parent setsid(); close STDIN; close STDOUT; close STDERR; open STDIN, "<&NULL"; open STDOUT, ">&NULL"; open STDERR, ">&CONSOLE"; close NULL; close CONSOLE; } From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 13 16:30: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 0FD9110656C1 for ; Fri, 13 Feb 2009 16:30:18 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: from mail-gx0-f224.google.com (mail-gx0-f224.google.com [209.85.217.224]) by mx1.freebsd.org (Postfix) with ESMTP id C30CB8FC24 for ; Fri, 13 Feb 2009 16:30:17 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: by gxk24 with SMTP id 24so951741gxk.19 for ; Fri, 13 Feb 2009 08:30:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=bE8eMdxjtbGStqb1owbPxOyaLQmRlr9F7p6q/FMEQGs=; b=TqqEFDo8vxZ4P9JBqKZc67fvrr2Go8g3UtQkfcDwj0tMK1OxEQRx/WhIBTUr7ExLd1 fic5LXKJ7guhffhjJT5TZPNiVcmh+U3UVfv3g+11bQCV2KL1DIPFKvSqekhIA6lFxMYI mD9K9VMlR6w7xcE7O0Rhm0OcwwLfq47xDvZTw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=EBEHSXByBuW23bGqWiCH3NK4LwitdOUj+/OMj5RIArbFE9R3mGuo521Nq1BKT7PN0r mHwwEhY3b4axwBpird5AoyLIkbtVTO1C9b4mXVOCxn8QCEUhH25mR1hFXEo9IuS+Gcpi 2Oc78ImPsHYIkXXFYnvPSAoM7+5CSLI5s+fuE= MIME-Version: 1.0 Received: by 10.220.76.149 with SMTP id c21mr666719vck.66.1234540933803; Fri, 13 Feb 2009 08:02:13 -0800 (PST) Date: Sat, 14 Feb 2009 11:32:13 +1930 Message-ID: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> From: Alberto Mijares To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: 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: Fri, 13 Feb 2009 16:30:18 -0000 Hello everybody, I have an Enfora EDG1228 GSM/GPRM modem, which should be used to send SMS. Seems not to be natively supported by FreeBSD 7.0: #dmesg [...] ugen0: on uhub0 #usbdevs [...] addr 3: SA-EL USB, Silicon Labs [...] Can't find any successful history of anyone getting it to work... Any suggestion? Thanks in advance. Regards Alberto Mijares Any suggestion about it? From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 13 18:04:27 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 B2FF6106566C for ; Fri, 13 Feb 2009 18:04:27 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe14.swipnet.se [212.247.155.161]) by mx1.freebsd.org (Postfix) with ESMTP id 47E038FC14 for ; Fri, 13 Feb 2009 18:04:27 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=kw03RjmKpLm8ql5X2xOdcA==:17 a=yqd5Ex2tL5ZBtI8PS4YA:9 a=iNBnhKgshinJzLcWDk3xWbEyYYAA:4 a=LY0hPdMaydYA:10 Received: from [85.19.218.115] (account mc467741@c2i.net HELO laptop) by mailfe14.swip.net (CommuniGate Pro SMTP 5.2.6) with ESMTPA id 453051580; Fri, 13 Feb 2009 19:04:25 +0100 From: Hans Petter Selasky To: freebsd-hardware@freebsd.org Date: Fri, 13 Feb 2009 19:06:49 +0100 User-Agent: KMail/1.9.7 References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> In-Reply-To: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902131906.51725.hselasky@c2i.net> 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: Fri, 13 Feb 2009 18:04:27 -0000 On Friday 13 February 2009, Alberto Mijares wrote: > Hello everybody, > > I have an Enfora EDG1228 GSM/GPRM modem, which should be used to send > SMS. Seems not to be natively supported by FreeBSD 7.0: > > #dmesg > [...] > ugen0: on uhub0 > > > Alberto Mijares > > Any suggestion about it? Can you dump the USB descriptors with /usr/ports/sysutils/udesc_dump ? --HPS From owner-freebsd-hardware@FreeBSD.ORG Sat Feb 14 07:06:09 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 6F547106566C for ; Sat, 14 Feb 2009 07:06:09 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from n11b.bullet.mail.mud.yahoo.com (n11b.bullet.mail.mud.yahoo.com [209.191.125.178]) by mx1.freebsd.org (Postfix) with SMTP id 10C698FC32 for ; Sat, 14 Feb 2009 07:06:08 +0000 (UTC) (envelope-from won.derick@yahoo.com) Received: from [68.142.200.221] by n11.bullet.mail.mud.yahoo.com with NNFMP; 14 Feb 2009 07:06:08 -0000 Received: from [68.142.201.66] by t9.bullet.mud.yahoo.com with NNFMP; 14 Feb 2009 07:06:08 -0000 Received: from [127.0.0.1] by omp418.mail.mud.yahoo.com with NNFMP; 14 Feb 2009 07:06:08 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 306398.98843.bm@omp418.mail.mud.yahoo.com Received: (qmail 52665 invoked by uid 60001); 14 Feb 2009 07:06:07 -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=m7b48TSkVeRDYoCrtTwRc1EEAh9CYN5Ne5gVh7ADE1O9Ncs5b9P3GxrMT/12zIcpLke+p4Y9k+ckUKhl7yZYJP6WYHresEeAkpyri5fIR9Rq1EPMupeTkr5IUPWUea4B55r5BDiKHiaS5vpNWqrcaA+zm2Kv5Cve+OtxyYiKDA8=; X-YMail-OSG: 4GH6VwoVM1nGbkA0n8eOYUswEUIuTqyy0ePdn23bUo6JRPJiSklZJEGegceDb0gXcyQA9y_gEaPrCYPaydRmall8YcnG0MBaS1QNpNeG0i9jcT.byiHv8nyZ0e2SPsmmIXbR1.FOYcj4bzjN4f5LP7bGwkNnmDybnbghEdCxxHr9_MxS6EaAgxHz6_66MBE- Received: from [58.71.34.137] by web45816.mail.sp1.yahoo.com via HTTP; Fri, 13 Feb 2009 23:06:07 PST X-Mailer: YahooMailWebService/0.7.260.1 Date: Fri, 13 Feb 2009 23:06:07 -0800 (PST) From: Won De Erick To: freebsd-hardware@FreeBSD.ORG In-Reply-To: <200902131045.n1DAjtxw031128@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <800496.48763.qm@web45816.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: Sat, 14 Feb 2009 07:06:09 -0000 Hi Oliver, Thanks for the help. This file /etc/wall_cmos_clock was missing, so I created an empty one.=20 The CMOS clock was successfully updated when I invoked 'adjkerntz -a'. However, how should I make this automatic, something that will update the C= MOS clock everytime the kernel clock is syncronized with a NTP server? Do I= need to make changes on the variables below? # sysctl -a machdep machdep.adjkerntz: 0 machdep.disable_rtc_set: 0 machdep.wall_cmos_clock: 0 machdep.conrclk: 1843200 machdep.gdbspeed: 9600 machdep.conspeed: 9600 .... --- On Fri, 2/13/09, Oliver Fromme wrote: > Hello, >=20 > Do you have a file /etc/wall_cmos_clock on your system? > If so, that would explain the behaviour very well. > If you want your CMOS clock run at UTC instead of local > time, you have to remove that file. >=20 > Apart from the Handbook you might also have a look at > the adjkerntz(8) manual page. It explains the mechanism > used to maintain the time zone difference (if any) > between FreeBSD and the CMOS clock. >=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 > "UNIX was not designed to stop you from doing stupid > things, > because that would also stop you from doing clever > things." > -- Doug Gwyn > _______________________________________________ > 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 Sat Feb 14 09:11: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 C32D4106566B for ; Sat, 14 Feb 2009 09:11:32 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183]) by mx1.freebsd.org (Postfix) with ESMTP id 7C9028FC08 for ; Sat, 14 Feb 2009 09:11:32 +0000 (UTC) (envelope-from amijaresp@gmail.com) Received: by el-out-1112.google.com with SMTP id r27so1405700ele.13 for ; Sat, 14 Feb 2009 01:11:31 -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=9W0xGatNSEyxx4hmb2Lod2vrUgEnyjg2iTRmjp6WXNc=; b=AMv9NN7TmXnp9s+EKea5aM0SV5lBygs6nLjUKsudrYcz5TZT6wq25a2iEQWTC5Bl+4 Cfzykb/IUkfARToB/gPOJ6AM3x2KF/gOMD+fuodG+/9574zvxoLvm4hl1+kzDlKi8eAU ijYaV1M7CPcXYGhu4DqFBQk0krQkbtuia5IFI= 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=wT0wfcsJMAvQ55yUwSOnJ4vTHncoC1jT/V9E5CrDmmR1f7bA8WZh0s0cwDSTCAKHxq UYcXdonlDW9PQwwX4wrJ954clSos94BMmJc+niIi/Kg/tMVv6B01HtZaQqUe/Fx8zKoL J4N1ymYikPgkxBFCGB1UkqaWxNJRhRDXggNYw= MIME-Version: 1.0 Received: by 10.220.74.135 with SMTP id u7mr905379vcj.4.1234602691790; Sat, 14 Feb 2009 01:11:31 -0800 (PST) In-Reply-To: <200902132209.52793.hselasky@c2i.net> References: <286906750902130802q2ec86267ye5ae0832ab9a3aa4@mail.gmail.com> <200902131906.51725.hselasky@c2i.net> <286906750902131226y22605e4ag41dcab90a6f7cf57@mail.gmail.com> <200902132209.52793.hselasky@c2i.net> Date: Sun, 15 Feb 2009 04:41:31 +1930 Message-ID: <286906750902140111i62d94f78w3921951f072cb930@mail.gmail.com> From: Alberto Mijares To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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: Sat, 14 Feb 2009 09:11:33 -0000 [...] > 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 From owner-freebsd-hardware@FreeBSD.ORG Sat Feb 14 16:08: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 9D5AB106566B for ; Sat, 14 Feb 2009 16:08:20 +0000 (UTC) (envelope-from admin@vfemail.net) Received: from mail.vfemail.net (mail.vfemail.net [69.11.239.68]) by mx1.freebsd.org (Postfix) with ESMTP id 4439D8FC0C for ; Sat, 14 Feb 2009 16:08:19 +0000 (UTC) (envelope-from admin@vfemail.net) Received: (qmail 90266 invoked by uid 0); 14 Feb 2009 15:41:37 -0000 Received: by simscan 1.1.0 ppid: 90259, pid: 90263, t: 0.1033s scanners:none Received: from unknown (HELO ?172.16.100.99?) (cmlja0BoYXZva21vbi5jb20=@NjkuMTEuMjM5LjY4) by mail.vfemail.net with ESMTPA; 14 Feb 2009 15:41:36 -0000 From: Rick Romero To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=cp1252 Organization: VF IT Services Date: Sat, 14 Feb 2009 09:41:17 -0600 Message-Id: <1234626078.5736.121.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: Sat, 14 Feb 2009 16:08:20 -0000 Me Too! I have TWO identical systems with Asus M3A78-CM Motherboards, and an ARC-1200 in each that is having this problem. Removing that controller allows the install CD to boot. Merely removing the drives from the controller does not. I've upgraded the BIOS, moved the controller to another slot, futzed in the BIOS (disabling/enabling,etc) - to no avail. I also upgraded the controller BIOS. I've booted 7.0R, 7.1R, 8.0Current(12/08), and 6.4R. 6.4R just 'hangs' at 'Waiting 5 seconds for SCSI devices to settle' (which is just before the kernel dump on 7 and 8), the rest crash with the below error. Obviously 8.0 has more data, but the jist is the same. I also found this link from 2007 which seems similar: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2007-04/msg00237.html Thoughts? suggestions? If you would like more info, I'd be happy to provide it. The controller has worked fine in OpenSolaris 2008.11, and I booted Ubuntu 8.10 for giggles and it worked there as well. Should I install onto a MotherBoard connected disk, then plug in the areca? Would that provide a dump point to get you guys more data? I want the areca as RAID 1 boot, and the SATA connected to the motherboard as JBOD for ZFS (hence the OpenSolaris above). Rick ---------------------------------------------- Attachment not getting throuh. Panic transcribed below. /Eirik On Jan 21, 2009, at 20:53, Eirik Øverby wrote: > Hi folks, > > see attached screenshot for panic screen. This happens when booting > from 7.1-release CD. The box is a Sun X2200 M2, the controller is a > 2-port SATA-II controller with 128mb cache memory. One drive is set > as single drive (RAID-0), another as passthrough (to get hold of > some data from pre-areca times). > > Another Areca controller in another box (different controller model > (4-chan sata) and box (tyan transport)) works just fine. > > Input welcome. > > /Eirik (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 From owner-freebsd-hardware@FreeBSD.ORG Sat Feb 14 18:39:01 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 2826B106564A for ; Sat, 14 Feb 2009 18:39:01 +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 98DBA8FC0A for ; Sat, 14 Feb 2009 18:39:00 +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 n1EIcw11009260; Sat, 14 Feb 2009 19:38:58 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n1EIcwQX009259; Sat, 14 Feb 2009 19:38:58 +0100 (CET) (envelope-from olli) Date: Sat, 14 Feb 2009 19:38:58 +0100 (CET) Message-Id: <200902141838.n1EIcwQX009259@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG, won.derick@yahoo.com In-Reply-To: <800496.48763.qm@web45816.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]); Sat, 14 Feb 2009 19:38:59 +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: Sat, 14 Feb 2009 18:39:01 -0000 Won De Erick wrote: > This file /etc/wall_cmos_clock was missing, so I created an empty one. 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. 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. 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. > 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. The only question is at which time zone the CMOS clock runs, as I've explained above. 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. 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 "The ITU has offered the IETF formal alignment with its corresponding technology, Penguins, but that won't fly." -- RFC 2549