From octavian.covalschi at gmail.com  Tue Mar  3 18:10:42 2009
From: octavian.covalschi at gmail.com (Octavian Covalschi)
Date: Tue Mar  3 18:10:48 2009
Subject: Spin down HDD after disk sync or before power off
Message-ID: <c0f49ea0903031744r319457ap43183fef9592ce2e@mail.gmail.com>

Hi everyone.

Is it possible to spin down HDD before it is powered off?

My problem/concern is that when I call "shutdown -p now", the HDD is powered
off at it's _full_ speed
and as a result I hear a noise, which really concerns me. I'm afraid that
this kind of shutdown  will damage HDD.

It's a new HDD, it works fine in Windows, I mean it shuts down w/o this
noise.

What I need(at least think I do) is to spin down or put into sleep mode HDD
right before system will be powered off.

I've tried to use atacontrol spindown but sync-ing disks wakes HDD again. I
also tried  ataidle -s my_dev
which puts hdd into sleep mode, but again, same result, when it syncs disks
it HDD is waken...

Are there any solutions?

Thank you in advance.
From desars at gmail.com  Tue Mar  3 21:46:03 2009
From: desars at gmail.com (Emmanuel de Sars)
Date: Tue Mar  3 21:46:09 2009
Subject: Gigabit Ethernet controller support (Intel 82563)
Message-ID: <49AE1263.2010702@gmail.com>

Hi fellas,

looking for a clear answer about the Intel 82563 eth. controller support 
in FreeBSD,
I found testimonias dating back to 2006 in which no conclusion could be 
drawn about
the support status.  Since the controller is not one of those supported 
by the em(4)
driver (expected to implement the support when looking at the hardware 
notes/man page),
should I give it a try or forget about it ?



Regards,
E.S
From olli at lurza.secnetix.de  Wed Mar  4 02:44:36 2009
From: olli at lurza.secnetix.de (Oliver Fromme)
Date: Wed Mar  4 02:44:44 2009
Subject: Gigabit Ethernet controller support (Intel 82563)
In-Reply-To: <49AE1263.2010702@gmail.com>
Message-ID: <200903041044.n24AiWDF037984@lurza.secnetix.de>

Emmanuel de Sars wrote:
 > looking for a clear answer about the Intel 82563 eth. controller support 
 > in FreeBSD,

As far as I can tell, the intel 82563 is _not_ an Ethernet
controller, but a MAC/PHY chip.  It is supported by FreeBSD.

If you want to kow if your Ethernet controller is supported,
we need to know what controller it is (e.g. vendor ID and
product ID from "pciconf -lv" output).  I think that the
support for intel NICs is very good, thanks to Jack Vogel,
so yours will probably work fine with either the em(4) or
igb(4) driver.

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

"Python tricks" is a tough one, cuz the language is so clean. E.g.,
C makes an art of confusing pointers with arrays and strings, which
leads to lotsa neat pointer tricks; APL mistakes everything for an
array, leading to neat one-liners; and Perl confuses everything
period, making each line a joyous adventure <wink>.
        -- Tim Peters
From roy.badami at globalgraphics.com  Wed Mar  4 03:55:07 2009
From: roy.badami at globalgraphics.com (Roy Badami)
Date: Wed Mar  4 03:55:13 2009
Subject: SIIG Cyber Serial 4S and system hang
In-Reply-To: <18837.37036.643000.795911@erbium.cam.harlequin.co.uk>
References: <18837.37036.643000.795911@erbium.cam.harlequin.co.uk>
Message-ID: <OF8D882AD2.3113146F-ON8025756F.0040EFC3-8025756F.0041770F@harlequin.co.uk>

> 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.

I spoke too soon.  Although things seemed to be working, SMS Server Tools 
would lose communication with the serial-attached GSM terminal after a few 
hours.

Bottom line is that it appears that for whatever reason the uart(4) driver 
can't reliably drive the SIIG CyberSerial 4S (16550-based) card.

After a bit of Googling I followed the advice of others who have had 
problems with the uart(4) driver not working well with their hardware, and 
built a kernel without it.  In that case, puc(4) will drive the card with 
the sio(4) driver instead.

Running in this configuration the system has been rock solid for two 
weeks, with all devices (thermometer, GSM terminal and two UPSs) attached 
to the SIIG card.

I'll raise a PR.

-roy

From ken at kdm.org  Wed Mar  4 14:52:45 2009
From: ken at kdm.org (Kenneth D. Merry)
Date: Wed Mar  4 14:52:52 2009
Subject: Extremely slow read/write speed, 7.1 Release on Intel ICH9 SATA
In-Reply-To: <ee705d4a0902260857g6cffb3a0t13d3b2afb11ffdb6@mail.gmail.com>
References: <ee705d4a0902260857g6cffb3a0t13d3b2afb11ffdb6@mail.gmail.com>
Message-ID: <20090304223310.GA35737@nargothrond.kdm.org>

On Thu, Feb 26, 2009 at 18:57:48 +0200, Rusu Silviu wrote:
> Extremely slow read/write speed, 7.1 Release on Intel ICH9 SATA
> 
> Should i send this to freebsd-fs list?
> 
> Have 3 HDDs
> - 160G Seagate Serial ATA v1.0, 3 partitions: 1 - system, 2 - data, 3 -
> storage, soft updates on for all partitions
> - 750G Samsung Serial ATA II, 1 partition, soft updates on
> - 1000G Samsung Serial ATA II, 1 partition, soft updates on
> 
> hw.ata.wc=1
> 
> Mobo is an ASUS P5KR, P35/ICH9
> Buyed it cause `man ata' says ICH9 is supported
> There are also Jmicron eSATA/PATA controller, that i actually disabled
> No overclocking
> 
> dd if=/dev/ad4 of=/dev/null
> iostat -w1 ad4
>       tty             ad4             cpu
>  tin tout  KB/t tps  MB/s  us ni sy in id
>   47   48  1.65 252  0.40   6  0  1  1 92
>    1  251  0.50 12650  6.18   2  0 15 14 69
>    0   88  0.50 12583  6.15   3  0 18 12 67
>    0   87  0.50 12641  6.17   3  0 18 12 68
[ ... ]

You should specify a blocksize with dd.  By default, it uses 512 byte
blocks, which will result in very slow transfer speeds.

Try this instead:

dd if=/dev/ad4 of=/dev/null bs=1m

Ken
-- 
Kenneth Merry
ken@kdm.org
From wowens1 at qwest.net  Tue Mar 10 15:08:11 2009
From: wowens1 at qwest.net (William Owens)
Date: Tue Mar 10 15:08:18 2009
Subject: parallel ata with disk and DVD-RW on same cable
Message-ID: <20090310220810.92B431A981F@mpls-qmqp-01.inet.qwest.net>

Good Day,

I have long had problems with putting disk drives and old CD-ROM drives 
on the same parallel IDE cable and have avoided doing so with more 
current DVD-RW drives till now. Is this to be expected or must I presume 
that IDE drives and ATAPI drives just cannot coexist on the same cable?  I 
have a particular need to put both on a single cable. Do I have a chance?  

Currently I have (from 'atacontrol')
atacontrol reinit ata1
Master:  ad2 <<ST3300831A/3.03> ATA/ATAPI revision 7
Slave:  acd0 <<NEC DVD RW ND-3550A/1.07> ATA/ATAPI revision 0

Because the NEC DVD drive is capable of UDMA33 as a maximum 
I have tried a 40 pin cable to limit both devices to UDMA33.
FreeBSD 7.1 recognizes this and prints a message. The problem
exists with either 40 ping or 80 cables.

If I write to the NEC DVD from the ad2 disk, both get very slow.
Writing from other devices to the DVD also causes the DVD drive
to sometimes get very slow ( ~ 1.3 Mb/sec ). The writing is done 
with 'growisofs' and uses the atapicam kernel module which turns 
/dev/acd0 into the SCSI device /dev/cd0.

Resetting with the 'atacontrol' command brings back a more normal 
speed (4-9 Mb/sec) for a time.  

So, the question, Do I have any right to expect disk drives and 
DVD (atapi) drives on the same parallel cable to work?

Thanks for your consideration.

Will Owens

From gamaral at amaral.com.mx  Fri Mar 13 20:05:13 2009
From: gamaral at amaral.com.mx (Guillermo Antonio Amaral Bastidas)
Date: Fri Mar 13 20:05:20 2009
Subject: Getting jack automute working in M1330 + SND_HDA + 7.1-p3
Message-ID: <86wsasho9e.fsf@daedalus.amaral.com.mx>


  Hi Guys,

  First off, I'm sorry if I say or ask something stupid. I'm a reforming
  Linuxholic and I'm trying to see the light and switch fully to
  FreeBSD.

  My GF keeps bugging me because I can't mute the internal speakers in
  my Dell M1330 and she doesn't dig the sweet sweet sounds of heavy
  metal ( not at 2 AM anyway ), I have tried many hints to try and get
  it working but I think the examples found on the interwebs are a bit
  dated or my install might be I'm really not sure compared to what I
  get back from the snd_hda driver in my install.

  It would be wonderfull if I could get jack sense working but just
  muting the speakers will do for now.

  * uname -a:

    FreeBSD localhost 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #0: Wed Mar
    11 12:33:44 PST 2009 root@localhost:/usr/obj/usr/src/sys/GENERIC
    i386

  * pciconf -lv

    pcm0@pci0:0:27:0:       class=0x040300 card=0x02091028
    chip=0x284b8086 rev=0x02 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82801H &SUBSYS_81EC1043&REV_02\3&11583659&0&D8'
    class      = multimedia

  * dmesg output

pcm0: <Intel 82801H High Definition Audio Controller> mem 0xf6dfc000-0xf6dfffff irq 21 at device 27.0 on pci0
pcm0: TCSEL: 0x00 -> 0x00
pcm0: DMA Coherency: Uncacheable / vendor=0x8086
pcm0: [MPSAFE]
pcm0: [ITHREAD]
pcm0: hdac_dma_alloc: size=1024 -> roundsz=1024
pcm0: hdac_dma_alloc: size=2048 -> roundsz=2048
pcm0: HDA_DEBUG: HDA Config: on=0x00000000 off=0x00000000
pcm0: HDA_DEBUG: Starting CORB Engine...
pcm0: HDA_DEBUG: Starting RIRB Engine...
pcm0: HDA_DEBUG: Enabling controller interrupt...
pcm0: HDA_DEBUG: Scanning HDA codecs [start index=0] ...
pcm0: HDA_DEBUG: Probing codec: 0
pcm0: HDA_DEBUG: 	startnode=1 endnode=2
pcm0: HDA_DEBUG: 	Found AFG nid=1 [startnode=1 endnode=2]
pcm0: HDA_DEBUG: Parsing AFG nid=1 cad=0
pcm0:        Vendor: 0x00008384
pcm0:        Device: 0x00007616
pcm0:      Revision: 0x00000004
pcm0:      Stepping: 0x00000002
pcm0: PCI Subvendor: 0x02091028
pcm0:         Nodes: start=2 endnode=37 total=35
pcm0:     CORB size: 256
pcm0:     RIRB size: 256
pcm0:       Streams: ISS=4 OSS=4 BSS=0
pcm0:          GPIO: 0xc0000003
pcm0:                NumGPIO=3 NumGPO=0 NumGPI=0 GPIWake=1 GPIUnsol=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=7 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=8 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=9 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=10 entries=2 found=2
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=11 entries=2 found=2
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=12 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=13 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=14 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=15 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=16 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=17 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=21 entries=9 found=9
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=22 entries=9 found=9
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=23 entries=9 found=9
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=24 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=25 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=26 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=27 entries=3 found=3
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=28 entries=3 found=3
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=29 entries=3 found=3
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=32 entries=1 found=1
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=33 entries=5 found=5
pcm0: HDA_DEBUG: hdac_widget_connection_parse: nid=36 entries=4 found=4
pcm0: HDA_DEBUG: Parsing Ctls...
pcm0: HDA_DEBUG: Parsing vendor patch...
pcm0: HDA_DEBUG: Building AFG tree...
pcm0: HDA_DEBUG: HWiP: HDA Widget Parser - Revision 1
pcm0: HDA_DEBUG: HWiP: 0 DAC path found! Retrying parser using HDA_PARSE_DIRECT strategy.
pcm0: HDA_DEBUG: HWiP: Found 4 DAC path using HDA_PARSE_DIRECT strategy.
pcm0: HDA_DEBUG: AFG commit...
pcm0: HDA_DEBUG: Ctls commit...
pcm0: [ 3] Ctl nid=4 Bind to NONE
pcm0: [ 5] Ctl nid=6 Bind to NONE
pcm0: [ 9] Ctl nid=24 childnid=21 Bind to NONE
pcm0: [10] Ctl nid=25 childnid=22 Bind to NONE
pcm0: [11] Ctl nid=26 childnid=23 Bind to NONE
pcm0: HDA_DEBUG: PCMDIR_PLAY setup...
pcm0: HDA_DEBUG: PCMDIR_REC setup...
pcm0: HDA_DEBUG: OSS mixer initialization...
pcm0: HDA_DEBUG: Forcing Soft PCM volume
pcm0: Mixer "vol": child=0x00000010
pcm0: Mixer "pcm": parent="vol"
pcm0: Mixer "speaker":
pcm0: Mixer "mic":
pcm0: Mixer "rec":
pcm0: Soft PCM mixer ENABLED
pcm0: HDA_DEBUG: Registering PCM channels...
pcm0: clone manager: deadline=750ms flags=0x8000001e
pcm0: hdac_dma_alloc: size=4096 -> roundsz=4096
pcm0: sndbuf_setmap 27694000, 4000; 0xe775d000 -> 27694000
pcm0: hdac_dma_alloc: size=4096 -> roundsz=4096
pcm0: sndbuf_setmap 962a0000, 4000; 0xe7761000 -> 962a0000
pcm0: <HDA Codec: Sigmatel (Unknown)>
pcm0: <HDA Codec ID: 0x83847616>
pcm0: <HDA Driver Revision: 20080420_0052>
pcm0: 
pcm0: HDA config/quirks: softpcmvol forcestereo ivref50 ivref80 ivref100 ivref
pcm0: 
pcm0: +-------------------+
pcm0: | DUMPING HDA NODES |
pcm0: +-------------------+
pcm0: 
pcm0: Default Parameter
pcm0: -----------------
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:          IN amp: 0x00050e00
pcm0:         OUT amp: 0x80027f7f
pcm0: 
pcm0:             nid: 2 [ANALOG]
pcm0:            name: audio output
pcm0:      widget_cap: 0x000d0c05
pcm0:     Parse flags: 0x00000001
pcm0:       Ctl flags: 0x00000011
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:      Output amp: 0x80027f7f
pcm0:                  mute=1 step=127 size=2 offset=127
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 3 [ANALOG]
pcm0:            name: audio output
pcm0:      widget_cap: 0x000d0c05
pcm0:     Parse flags: 0x00000001
pcm0:       Ctl flags: 0x00000011
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:      Output amp: 0x80027f7f
pcm0:                  mute=1 step=127 size=2 offset=127
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 4 [ANALOG]
pcm0:            name: audio output
pcm0:      widget_cap: 0x000d0c05
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:      Output amp: 0x80027f7f
pcm0:                  mute=1 step=127 size=2 offset=127
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 5 [ANALOG]
pcm0:            name: audio output
pcm0:      widget_cap: 0x000d0c05
pcm0:     Parse flags: 0x00000001
pcm0:       Ctl flags: 0x00000011
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:      Output amp: 0x80027f7f
pcm0:                  mute=1 step=127 size=2 offset=127
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 6 [ANALOG]
pcm0:            name: vendor widget
pcm0:      widget_cap: 0x00fd0c05
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:      Output amp: 0x80027f7f
pcm0:                  mute=1 step=127 size=2 offset=127
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 7 [ANALOG]
pcm0:            name: audio input
pcm0:      widget_cap: 0x001d0541
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000800
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=27 [audio selector]
pcm0: 
pcm0:             nid: 8 [ANALOG]
pcm0:            name: audio input
pcm0:      widget_cap: 0x001d0541
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000800
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=28 [audio selector]
pcm0: 
pcm0:             nid: 9 [ANALOG]
pcm0:            name: audio input
pcm0:      widget_cap: 0x001d0541
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000800
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=29 [audio selector]
pcm0: 
pcm0:             nid: 10 [ANALOG]
pcm0:            name: pin: headphones out (jack)
pcm0:      widget_cap: 0x00400181
pcm0:     Parse flags: 0x00000001
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x0000173f
pcm0:                  ISC TRQD HP OUT IN VREF[ 50 80 GROUND HIZ ] : UNSOL
pcm0:      Pin config: 0x0221101f
pcm0:     Pin control: 0x000000c0 HP OUT
pcm0:     connections: 2
pcm0:           |
pcm0:           + <- nid=2 [audio output] (selected)
pcm0:           |
pcm0:           + <- nid=3 [audio output]
pcm0: 
pcm0:             nid: 11 [ANALOG] [DISABLED]
pcm0:            name: pin: other (none)
pcm0:      widget_cap: 0x00400181
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x0000173f
pcm0:                  ISC TRQD HP OUT IN VREF[ 50 80 GROUND HIZ ] : UNSOL
pcm0:      Pin config: 0x40f000f0
pcm0:     Pin control: 0x000000e0 HP IN OUT
pcm0:     connections: 2
pcm0:           |
pcm0:           + <- nid=2 [audio output]
pcm0:           |
pcm0:           + <- nid=3 [audio output]
pcm0: 
pcm0:             nid: 12 [ANALOG] [DISABLED]
pcm0:            name: pin: other (none)
pcm0:      widget_cap: 0x00400181
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00001737
pcm0:                  ISC TRQD OUT IN VREF[ 50 80 GROUND HIZ ] : UNSOL
pcm0:      Pin config: 0x40f000f1
pcm0:     Pin control: 0x00000060 IN OUT
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=3 [audio output]
pcm0: 
pcm0:             nid: 13 [ANALOG]
pcm0:            name: pin: speaker (fixed)
pcm0:      widget_cap: 0x00400181
pcm0:     Parse flags: 0x00000001
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x0000173f
pcm0:                  ISC TRQD HP OUT IN VREF[ 50 80 GROUND HIZ ] : UNSOL
pcm0:      Pin config: 0x90170110
pcm0:     Pin control: 0x00000040 OUT
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=2 [audio output]
pcm0: 
pcm0:             nid: 14 [ANALOG]
pcm0:            name: pin: Mic in (jack)
pcm0:      widget_cap: 0x00400181
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000080
pcm0:         Pin cap: 0x00001737
pcm0:                  ISC TRQD OUT IN VREF[ 50 80 GROUND HIZ ] : UNSOL
pcm0:      Pin config: 0x02a11030
pcm0:     Pin control: 0x00000024 IN
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=4 [audio output]
pcm0: 
pcm0:             nid: 15 [ANALOG]
pcm0:            name: pin: line out (jack)
pcm0:      widget_cap: 0x00400181
pcm0:     Parse flags: 0x00000001
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00001737
pcm0:                  ISC TRQD OUT IN VREF[ 50 80 GROUND HIZ ] : UNSOL
pcm0:      Pin config: 0x02011020
pcm0:     Pin control: 0x00000040 OUT
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=5 [audio output]
pcm0: 
pcm0:             nid: 16 [ANALOG] [DISABLED]
pcm0:            name: pin: other (none)
pcm0:      widget_cap: 0x00400181
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00000037
pcm0:                  ISC TRQD OUT IN : UNSOL
pcm0:      Pin config: 0x40f000f2
pcm0:     Pin control: 0x00000060 IN OUT
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=4 [audio output]
pcm0: 
pcm0:             nid: 17 [ANALOG] [DISABLED]
pcm0:            name: pin: other (none)
pcm0:      widget_cap: 0x00400181
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00000037
pcm0:                  ISC TRQD OUT IN : UNSOL
pcm0:      Pin config: 0x40f000f3
pcm0:     Pin control: 0x00000060 IN OUT
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=3 [audio output]
pcm0: 
pcm0:             nid: 18 [ANALOG] [DISABLED]
pcm0:            name: pin: other (none)
pcm0:      widget_cap: 0x00400001
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00000020
pcm0:                  IN
pcm0:      Pin config: 0x40f000f4
pcm0:     Pin control: 0x00000020 IN
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 19 [ANALOG]
pcm0:            name: pin: Mic in (fixed)
pcm0:      widget_cap: 0x00400001
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00000020
pcm0:                  IN
pcm0:      Pin config: 0x90a60040
pcm0:     Pin control: 0x00000020 IN
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 20 [ANALOG] [DISABLED]
pcm0:            name: pin: other (none)
pcm0:      widget_cap: 0x00400001
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00000020
pcm0:                  IN
pcm0:      Pin config: 0x40f000f5
pcm0:     Pin control: 0x00000020 IN
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 21 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x0030010d
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000080
pcm0:      Output amp: 0x00270400
pcm0:                  mute=0 step=4 size=39 offset=0
pcm0:     connections: 9
pcm0:           |
pcm0:           + <- nid=14 [pin: Mic in (jack)] (selected)
pcm0:           |
pcm0:           + <- nid=18 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=15 [pin: line out (jack)]
pcm0:           |
pcm0:           + <- nid=11 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=12 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=13 [pin: speaker (fixed)]
pcm0:           |
pcm0:           + <- nid=10 [pin: headphones out (jack)]
pcm0:           |
pcm0:           + <- nid=16 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=17 [pin: other (none)] [DISABLED]
pcm0: 
pcm0:             nid: 22 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x0030010d
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000080
pcm0:      Output amp: 0x00270400
pcm0:                  mute=0 step=4 size=39 offset=0
pcm0:     connections: 9
pcm0:           |
pcm0:           + <- nid=14 [pin: Mic in (jack)] (selected)
pcm0:           |
pcm0:           + <- nid=18 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=15 [pin: line out (jack)]
pcm0:           |
pcm0:           + <- nid=11 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=12 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=13 [pin: speaker (fixed)]
pcm0:           |
pcm0:           + <- nid=10 [pin: headphones out (jack)]
pcm0:           |
pcm0:           + <- nid=16 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=17 [pin: other (none)] [DISABLED]
pcm0: 
pcm0:             nid: 23 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x0030010d
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000080
pcm0:      Output amp: 0x00270400
pcm0:                  mute=0 step=4 size=39 offset=0
pcm0:     connections: 9
pcm0:           |
pcm0:           + <- nid=14 [pin: Mic in (jack)] (selected)
pcm0:           |
pcm0:           + <- nid=18 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=15 [pin: line out (jack)]
pcm0:           |
pcm0:           + <- nid=11 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=12 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=13 [pin: speaker (fixed)]
pcm0:           |
pcm0:           + <- nid=10 [pin: headphones out (jack)]
pcm0:           |
pcm0:           + <- nid=16 [pin: other (none)] [DISABLED]
pcm0:           |
pcm0:           + <- nid=17 [pin: other (none)] [DISABLED]
pcm0: 
pcm0:             nid: 24 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x00300103
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000000
pcm0:       Input amp: 0x00050e00
pcm0:                  mute=0 step=14 size=5 offset=0
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=21 [audio selector]
pcm0: 
pcm0:             nid: 25 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x00300103
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000000
pcm0:       Input amp: 0x00050e00
pcm0:                  mute=0 step=14 size=5 offset=0
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=22 [audio selector]
pcm0: 
pcm0:             nid: 26 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x00300103
pcm0:     Parse flags: 0x00000002
pcm0:       Ctl flags: 0x00000000
pcm0:       Input amp: 0x00050e00
pcm0:                  mute=0 step=14 size=5 offset=0
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=23 [audio selector]
pcm0: 
pcm0:             nid: 27 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x0030090d
pcm0:     Parse flags: 0x00000006
pcm0:       Ctl flags: 0x00000800
pcm0:      Output amp: 0x80000000
pcm0:                  mute=1 step=0 size=0 offset=0
pcm0:     connections: 3
pcm0:           |
pcm0:           + <- nid=24 [audio selector] (selected)
pcm0:           |
pcm0:           + <- nid=19 [pin: Mic in (fixed)]
pcm0:           |
pcm0:           + <- nid=20 [pin: other (none)] [DISABLED]
pcm0: 
pcm0:             nid: 28 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x0030090d
pcm0:     Parse flags: 0x00000006
pcm0:       Ctl flags: 0x00000800
pcm0:      Output amp: 0x80000000
pcm0:                  mute=1 step=0 size=0 offset=0
pcm0:     connections: 3
pcm0:           |
pcm0:           + <- nid=25 [audio selector] (selected)
pcm0:           |
pcm0:           + <- nid=19 [pin: Mic in (fixed)]
pcm0:           |
pcm0:           + <- nid=20 [pin: other (none)] [DISABLED]
pcm0: 
pcm0:             nid: 29 [ANALOG]
pcm0:            name: audio selector
pcm0:      widget_cap: 0x0030090d
pcm0:     Parse flags: 0x00000006
pcm0:       Ctl flags: 0x00000800
pcm0:      Output amp: 0x80000000
pcm0:                  mute=1 step=0 size=0 offset=0
pcm0:     connections: 3
pcm0:           |
pcm0:           + <- nid=26 [audio selector] (selected)
pcm0:           |
pcm0:           + <- nid=19 [pin: Mic in (fixed)]
pcm0:           |
pcm0:           + <- nid=20 [pin: other (none)] [DISABLED]
pcm0: 
pcm0:             nid: 30 [DIGITAL] [DISABLED]
pcm0:            name: audio output
pcm0:      widget_cap: 0x00040211
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:      Stream cap: 0x00000005
pcm0:          Format: AC3 PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 31 [DIGITAL] [DISABLED]
pcm0:            name: vendor widget
pcm0:      widget_cap: 0x00f30201
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 32 [DIGITAL] [DISABLED]
pcm0:            name: audio input
pcm0:      widget_cap: 0x00140311
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:      Stream cap: 0x00000005
pcm0:          Format: AC3 PCM
pcm0:         PCM cap: 0x000e0160
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 96
pcm0:     connections: 1
pcm0:           |
pcm0:           + <- nid=34 [pin: other (none)] [DISABLED]
pcm0: 
pcm0:             nid: 33 [DIGITAL] [DISABLED]
pcm0:            name: pin: SPDIF out (jack)
pcm0:      widget_cap: 0x00400301
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00000010
pcm0:                  OUT
pcm0:      Pin config: 0x01442170
pcm0:     Pin control: 0x00000040 OUT
pcm0:     connections: 5
pcm0:           |
pcm0:           + <- nid=30 [audio output] [DISABLED]
pcm0:           |
pcm0:           + <- nid=31 [vendor widget] [DISABLED]
pcm0:           |
pcm0:           + <- nid=27 [audio selector]
pcm0:           |
pcm0:           + <- nid=28 [audio selector]
pcm0:           |
pcm0:           + <- nid=29 [audio selector]
pcm0: 
pcm0:             nid: 34 [DIGITAL] [DISABLED]
pcm0:            name: pin: other (none)
pcm0:      widget_cap: 0x00430681
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:         Pin cap: 0x00010024
pcm0:                  IN EAPD : UNSOL
pcm0:      Pin config: 0x40f000f7
pcm0:     Pin control: 0x00000020 IN
pcm0:            EAPD: 0x00000002
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 35 [ANALOG]
pcm0:            name: beep widget
pcm0:      widget_cap: 0x0070000c
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000021
pcm0:      Output amp: 0x00170303
pcm0:                  mute=0 step=3 size=23 offset=3
pcm0:     connections: 0
pcm0: 
pcm0:             nid: 36 [ANALOG]
pcm0:            name: volume widget
pcm0:      widget_cap: 0x00600000
pcm0:     Parse flags: 0x00000000
pcm0:       Ctl flags: 0x00000000
pcm0:     connections: 4
pcm0:           |
pcm0:           + <- nid=2 [audio output] (selected)
pcm0:           |
pcm0:           + <- nid=3 [audio output]
pcm0:           |
pcm0:           + <- nid=4 [audio output]
pcm0:           |
pcm0:           + <- nid=5 [audio output]
pcm0: 
pcm0: +------------------------+
pcm0: | DUMPING HDA AMPLIFIERS |
pcm0: +------------------------+
pcm0: 
pcm0:   1: nid=2 dir=0x1 index=0 ossmask=0x00000011 ossdev=4 [DISABLED]
pcm0:   2: nid=3 dir=0x1 index=0 ossmask=0x00000011 ossdev=4 [DISABLED]
pcm0:   3: nid=4 dir=0x1 index=0 ossmask=0x00000000 ossdev=0
pcm0:   4: nid=5 dir=0x1 index=0 ossmask=0x00000011 ossdev=4 [DISABLED]
pcm0:   5: nid=6 dir=0x1 index=0 ossmask=0x00000000 ossdev=0
pcm0:   6: nid=21 dir=0x1 index=0 ossmask=0x00000080 ossdev=7
pcm0:   7: nid=22 dir=0x1 index=0 ossmask=0x00000080 ossdev=7
pcm0:   8: nid=23 dir=0x1 index=0 ossmask=0x00000080 ossdev=7
pcm0:   9: nid=24 cnid=21 dir=0x2 index=0 ossmask=0x00000000 ossdev=0
pcm0:  10: nid=25 cnid=22 dir=0x2 index=0 ossmask=0x00000000 ossdev=0
pcm0:  11: nid=26 cnid=23 dir=0x2 index=0 ossmask=0x00000000 ossdev=0
pcm0:  12: nid=27 dir=0x1 index=0 ossmask=0x00000800 ossdev=0
pcm0:  13: nid=28 dir=0x1 index=0 ossmask=0x00000800 ossdev=0
pcm0:  14: nid=29 dir=0x1 index=0 ossmask=0x00000800 ossdev=0
pcm0:  15: nid=35 dir=0x1 index=0 ossmask=0x00000021 ossdev=5
pcm0: 
pcm0: +-----------------------------------+
pcm0: | DUMPING HDA AUDIO/VOLUME CONTROLS |
pcm0: +-----------------------------------+
pcm0: 
pcm0: Master Volume (OSS: vol)
pcm0:    |
pcm0:    +-  nid: 35 index:  0           mute: 0 step:   3 size:  23 off:   3 dir=0x1 ossmask=0x00000021
pcm0: 
pcm0: Microphone Volume (OSS: mic)
pcm0:    |
pcm0:    +-  nid: 21 index:  0           mute: 0 step:   4 size:  39 off:   0 dir=0x1 ossmask=0x00000080
pcm0:    |
pcm0:    +-  nid: 22 index:  0           mute: 0 step:   4 size:  39 off:   0 dir=0x1 ossmask=0x00000080
pcm0:    |
pcm0:    +-  nid: 23 index:  0           mute: 0 step:   4 size:  39 off:   0 dir=0x1 ossmask=0x00000080
pcm0: 
pcm0: Recording Level (OSS: rec)
pcm0:    |
pcm0:    +-  nid: 27 index:  0           mute: 1 step:   0 size:   0 off:   0 dir=0x1 ossmask=0x00000800
pcm0:    |
pcm0:    +-  nid: 28 index:  0           mute: 1 step:   0 size:   0 off:   0 dir=0x1 ossmask=0x00000800
pcm0:    |
pcm0:    +-  nid: 29 index:  0           mute: 1 step:   0 size:   0 off:   0 dir=0x1 ossmask=0x00000800
pcm0: 
pcm0: Speaker/Beep (OSS: speaker)
pcm0:    |
pcm0:    +-  nid: 35 index:  0           mute: 0 step:   3 size:  23 off:   3 dir=0x1 ossmask=0x00000021
pcm0: 
pcm0: Playback path:
pcm0: 
pcm0:     nid=10 [pin: headphones out (jack)]
pcm0:       ^
pcm0:       |
pcm0:       +-----<------+
pcm0:                    ^
pcm0:                    |
pcm0:                  nid=2 [audio output]
pcm0: 
pcm0:     nid=13 [pin: speaker (fixed)]
pcm0:       ^
pcm0:       |
pcm0:       +-----<------+
pcm0:                    ^
pcm0:                    |
pcm0:                  nid=2 [audio output]
pcm0: 
pcm0:     nid=15 [pin: line out (jack)]
pcm0:       ^
pcm0:       |
pcm0:       +-----<------+
pcm0:                    ^
pcm0:                    |
pcm0:                  nid=5 [audio output]
pcm0: 
pcm0: Recording sources:
pcm0: 
pcm0:     nid=27 [audio selector]
pcm0:       |
pcm0:       + <- nid=24 [audio selector]
pcm0:       |
pcm0:       + <- nid=19 [pin: Mic in (fixed)]
pcm0: 
pcm0:     nid=28 [audio selector]
pcm0:       |
pcm0:       + <- nid=25 [audio selector]
pcm0:       |
pcm0:       + <- nid=19 [pin: Mic in (fixed)]
pcm0: 
pcm0:     nid=29 [audio selector]
pcm0:       |
pcm0:       + <- nid=26 [audio selector]
pcm0:       |
pcm0:       + <- nid=19 [pin: Mic in (fixed)]
pcm0: 
pcm0: +--------------------------------------+
pcm0: | DUMPING PCM Playback/Record Channels |
pcm0: +--------------------------------------+
pcm0: 
pcm0:    PCM Playback: 1
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:             DAC: 2 3 5
pcm0: 
pcm0:      PCM Record: 1
pcm0:      Stream cap: 0x00000001
pcm0:          Format: PCM
pcm0:         PCM cap: 0x000e07e0
pcm0:        PCM size: 16 20 24
pcm0:        PCM rate: 44 48 88 96 176 192
pcm0:             ADC: 7 8 9


  If anybody can guide me I will really appreciate it, if I can't get
 this thing working soon I will need to cut the internal speaker cables
 but I really don't want to.. :(


 Cheers,
  GA

-- 
Guillermo Antonio Amaral Bastidas (gamaral)
Free/Libre/Open-Source Software Developer : http://www.guillermoamaral.com/
KDE Bending Unit : http://www.kde.org/
GPG Fingerprint: E068 811D 4AA2 7FDA A327 38BD 640D 014C 76FE 7D5A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20090314/751cd99a/attachment.pgp
From mav at FreeBSD.org  Sat Mar 14 03:18:58 2009
From: mav at FreeBSD.org (Alexander Motin)
Date: Sat Mar 14 03:19:04 2009
Subject: Getting jack automute working in M1330 + SND_HDA + 7.1-p3
In-Reply-To: <1237011798.00086627.1237000202@10.7.7.3>
References: <1237011798.00086627.1237000202@10.7.7.3>
Message-ID: <49BB767C.4040701@FreeBSD.org>

Hi.

Guillermo Antonio Amaral Bastidas wrote:
>   My GF keeps bugging me because I can't mute the internal speakers in
>   my Dell M1330 and she doesn't dig the sweet sweet sounds of heavy
>   metal ( not at 2 AM anyway ), I have tried many hints to try and get
>   it working but I think the examples found on the interwebs are a bit
>   dated or my install might be I'm really not sure compared to what I
>   get back from the snd_hda driver in my install.
> 
>   It would be wonderfull if I could get jack sense working but just
>   muting the speakers will do for now.
> 
>   * uname -a:
> 
>     FreeBSD localhost 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #0: Wed Mar
>     11 12:33:44 PST 2009 root@localhost:/usr/obj/usr/src/sys/GENERIC
>     i386

Update your system to recent 7-STABLE. New snd_hda driver imported there 
is much more suitable in this and many other aspects. Read updated man 
page if any questions.

-- 
Alexander Motin
From gamaral at amaral.com.mx  Sat Mar 14 21:03:05 2009
From: gamaral at amaral.com.mx (Guillermo Antonio Amaral Bastidas)
Date: Sat Mar 14 21:03:14 2009
Subject: Getting jack automute working in M1330 + SND_HDA + 7.1-p3
References: <1237011798.00086627.1237000202@10.7.7.3>
	<49BB767C.4040701@FreeBSD.org>
Message-ID: <867i2r302e.fsf@daedalus.amaral.com.mx>

Alexander Motin <mav@FreeBSD.org> writes:

> Hi.
>
> Guillermo Antonio Amaral Bastidas wrote:
>>   My GF keeps bugging me because I can't mute the internal speakers in
>>   my Dell M1330 and she doesn't dig the sweet sweet sounds of heavy
>>   metal ( not at 2 AM anyway ), I have tried many hints to try and get
>>   it working but I think the examples found on the interwebs are a bit
>>   dated or my install might be I'm really not sure compared to what I
>>   get back from the snd_hda driver in my install.
>>
>>   It would be wonderfull if I could get jack sense working but just
>>   muting the speakers will do for now.
>>
>>   * uname -a:
>>
>>     FreeBSD localhost 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #0: Wed Mar
>>     11 12:33:44 PST 2009 root@localhost:/usr/obj/usr/src/sys/GENERIC
>>     i386
>
> Update your system to recent 7-STABLE. New snd_hda driver imported
> there is much more suitable in this and many other aspects. Read
> updated man page if any questions.

  SWEET! Thanks :D Will Try

-- 
Guillermo Antonio Amaral Bastidas (gamaral)
Free/Libre/Open-Source Software Developer : http://www.guillermoamaral.com/
KDE Developer & KDE e.V. Member : http://www.kde.org/
GPG Fingerprint: E068 811D 4AA2 7FDA A327 38BD 640D 014C 76FE 7D5A

From gamaral at amaral.com.mx  Sat Mar 14 23:28:28 2009
From: gamaral at amaral.com.mx (Guillermo Antonio Amaral Bastidas)
Date: Sat Mar 14 23:28:34 2009
Subject: Getting jack automute working in M1330 + SND_HDA + 7.1-p3
References: <1237011798.00086627.1237000202@10.7.7.3>
	<49BB767C.4040701@FreeBSD.org>
Message-ID: <864oxv47wk.fsf@daedalus.amaral.com.mx>

Alexander Motin <mav@FreeBSD.org> writes:

> Hi.
>
> Guillermo Antonio Amaral Bastidas wrote:
>>   My GF keeps bugging me because I can't mute the internal speakers in
>>   my Dell M1330 and she doesn't dig the sweet sweet sounds of heavy
>>   metal ( not at 2 AM anyway ), I have tried many hints to try and get
>>   it working but I think the examples found on the interwebs are a bit
>>   dated or my install might be I'm really not sure compared to what I
>>   get back from the snd_hda driver in my install.
>>
>>   It would be wonderfull if I could get jack sense working but just
>>   muting the speakers will do for now.
>>
>>   * uname -a:
>>
>>     FreeBSD localhost 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #0: Wed Mar
>>     11 12:33:44 PST 2009 root@localhost:/usr/obj/usr/src/sys/GENERIC
>>     i386
>
> Update your system to recent 7-STABLE. New snd_hda driver imported
> there is much more suitable in this and many other aspects. Read
> updated man page if any questions.

  Oh I must have done something wrong, it seems by trying to update to
 7-STABLE I actually downgraded my system some how. Could be cuz I was
 running 7.1 p3 before. oh my now I need to try and upgrade again.

-- 
Guillermo Antonio Amaral Bastidas (gamaral)
Free/Libre/Open-Source Software Developer : http://www.guillermoamaral.com/
KDE Cheese Nacho : http://www.kde.org/
GPG Fingerprint: E068 811D 4AA2 7FDA A327 38BD 640D 014C 76FE 7D5A

From alaric at metrocast.net  Sun Mar 15 13:01:24 2009
From: alaric at metrocast.net (Phil Stracchino)
Date: Sun Mar 15 13:01:32 2009
Subject: Boot failure, 7.1R-amd64
Message-ID: <49BD5A7B.9040405@metrocast.net>

I wish to report, and seek advice on, a 7.1R-amd64 boot failure on a
machine that should be perfectly capable of running it.


I have a 3U storage box here with two Intel Xeon 3.2GHz CPUs (0xf41; I
believe they're Irwindales, NetBurst microarchitecture with amd64
support) on a Tyan Tiger i7320R-S5350 board with 4GB of RAM.  Boot is a
mirrored (with gmirror) pair of Seagate ST980811AS 2.5" SATA disks.
Main storage is twelve Maxtor 300GB SATA disks on a 3Ware 9500S-12
SATA-RAID controller, exported in JBOD mode.  I've just updated the
system BIOS to the latest S5350-108 image.

This machine happily runs Solaris 10 x86.  It happily runs OpenBSD 4.4
amd64.  It runs FreeBSD 7.1R-i386, as long as it is booted without acpi.

FreeBSD babylon4.babcom.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan
 1 14:37:25 UTC 2009
root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

(still running generic kernel at this time, as you can see)


However, it will not boot FreeBSD 7.1R-amd64, although all reason says
it should.  Booted from 7.1R-amd64 cd1 with ACPI enabled, it gets as far as:

...
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
uhub3: <vendor 0x0451 product 0x1446, class 9/0, rev 1.10/1.10, addr 2>
on uhub0
uhub3: 4 ports with 4 removable, self powered
Timecounters tick every 1.000 msec
md0: Preloaded image </boot/mfsroot> 4194034 bytes at 0xffffffff80c4be40
ad0: 76319MB <Seagate ST980811AS 3.BHE> at ata0-master SATA150
ad1: 76319MB <Seagate ST980811AS 3.BHE> at ata0-slave SATA150

...at which point it hangs.

With acpi disabled:

...
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
uhub3: <vendor 0x0451 product 0x1446, class 9/0, rev 1.10/1.10, addr 2>
on uhub0
uhub3: 4 ports with 4 removable, self powered
Timecounter "TSC" frequency 3192019456 Hz quality 800
Timecounters tick every 1.000 msec
md0: Preloaded image </boot/mfsroot> 4194034 bytes at 0xffffffff80c4be40
Trying to mount root from ufs:/dev/md0

...and hang.

Verbose logging adds the following additional information at the hang point:

...
uhub3: 4 ports with 4 removable, self powered
Device configuration finished.
Reducing kern.maxvnodes 235635 -> 100000
procfs registered
lapic: Divisor 2, frequency 99750485 Hz
Timecounter "TSC" frequency 3192019456 Hz quality 800
Timecounters tick every 1.000 msec
lo0: bpf attached
hptrr: no controller detected
md0: Preloaded image </boot/mfsroot> 4194034 bytes at 0xffffffff80c4be40
(probe12:twa0:0:12:7): error 22
(probe12:twa0:0:12:7): Unretryable error
(probe13:twa0:0:13:7): error 22
(probe13:twa0:0:13:7): Unretryable error
(probe14:twa0:0:14:7): error 22
(probe14:twa0:0:14:7): Unretryable error
(probe15:twa0:0:15:7): error 22
(probe15:twa0:0:15:7): Unretryable error

[repeat until probe31]

(probe0:twa0:0:0:7): error 22
(probe0:twa0:0:0:7): Unretryable error
(probe1:twa0:0:1:7): error 22
(probe1:twa0:0:1:7): Unretryable error
...
(probe11:twa0:0:11:7): error 22
(probe11:twa0:0:11:7): Unretryable error

[repeat probe0-probe11 sequence 8 times in total

[hang]



dmesg, booted from onboard 7.1R-i386:

Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-RELEASE #0: Thu Jan  1 14:37:25 UTC 2009
    root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.02-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf41  Stepping = 1

Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x641d<SSE3,DTES64,MON,DS_CPL,CNXT-ID,CX16,xTPR>
  AMD Features=0x20100000<NX,LM>
  Logical CPUs per core: 2
real memory  = 3623288832 (3455 MB)
avail memory = 3541639168 (3377 MB)
MPTable: <INTEL    Lindenhurst >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  6
ioapic0: Assuming intbase of 0
ioapic1: Assuming intbase of 24
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
pcib0: <MPTable Host-PCI bridge> pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
pcib0: unable to route slot 2 INTA
pcib0: unable to route slot 3 INTA
pcib1: <MPTable PCI-PCI bridge> irq 5 at device 2.0 on pci0
pci1: <PCI bus> on pcib1
bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4101>
mem 0xd
d100000-0xdd10ffff irq 16 at device 0.0 on pci1
miibus0: <MII bus> on bge0
brgphy0: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-F
DX, auto
bge0: Ethernet address: 00:e0:81:30:de:88
bge0: [ITHREAD]
pcib2: <MPTable PCI-PCI bridge> irq 5 at device 3.0 on pci0
pci2: <PCI bus> on pcib2
bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4101>
mem 0xd
d200000-0xdd20ffff irq 16 at device 0.0 on pci2
miibus1: <MII bus> on bge1
brgphy1: <BCM5750 10/100/1000baseTX PHY> PHY 1 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-F
DX, auto
bge1: Ethernet address: 00:e0:81:30:de:89
bge1: [ITHREAD]
pcib3: <MPTable PCI-PCI bridge> at device 28.0 on pci0
pci3: <PCI bus> on pcib3
3ware device driver for 9000 series storage controllers, version:
3.70.05.001
twa0: <3ware 9000 series Storage Controller> port 0x2000-0x20ff mem
0xdd300000-0
xdd3000ff,0xdf800000-0xdfffffff irq 24 at device 3.0 on pci3
twa0: [ITHREAD]
twa0: INFO: (0x15: 0x1300): Controller details:: Model 9500S-12, 12
ports, Firmw
are FE9X 2.08.00.005, BIOS string not found
uhci0: <UHCI (generic) USB controller> port 0x1400-0x141f irq 16 at
device 29.0
on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0x1420-0x143f irq 19 at
device 29.1
on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
pci0: <base peripheral> at device 29.4 (no driver attached)
ehci0: <Intel 6300ESB USB 2.0 controller> mem 0xdd000400-0xdd0007ff irq
23 at de
vice 29.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: EHCI version 1.0
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <Intel 6300ESB USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
uhub2: 4 ports with 4 removable, self powered
pcib4: <MPTable PCI-PCI bridge> at device 30.0 on pci0
pci4: <PCI bus> on pcib4
vgapci0: <VGA-compatible display> port 0x3000-0x30ff mem
0xde000000-0xdeffffff,0
xdd400000-0xdd400fff irq 17 at device 3.0 on pci4
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel 6300ESB SATA150 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0
x376,0x1470-0x147f at device 31.2 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
cpu0 on motherboard
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1 on motherboard
p4tcc1: <CPU Frequency Thermal Control> on cpu1
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff pnpid ORM0000 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model Generic PS/2 mouse, device ID 0
fdc0: <Enhanced floppy controller> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2
on isa0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
ppbus0: [ITHREAD]
plip0: <PLIP network interface> on ppbus0
plip0: WARNING: using obsoleted IFF_NEEDSGIANT flag
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ppc0: [GIANT-LOCKED]
ppc0: [ITHREAD]
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio0: [FILTER]
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio1: [FILTER]
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
unknown: <PNP0c02> can't assign resources (memory)
unknown: <PNP0c02> can't assign resources (memory)
unknown: <PNP0c01> can't assign resources (memory)
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0c02> can't assign resources (memory)
unknown: <PNP0f13> can't assign resources (irq)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0700> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0400> can't assign resources (port)
uhub3: <vendor 0x0451 product 0x1446, class 9/0, rev 1.10/1.10, addr 2>
on uhub0
uhub3: 4 ports with 4 removable, self powered
Timecounters tick every 1.000 msec
ad0: 76319MB <Seagate ST980811AS 3.BHE> at ata0-master SATA150
ad1: 76319MB <Seagate ST980811AS 3.BHE> at ata0-slave SATA150
acd0: CDROM <SONY CD-ROM CDU5215/7YS1> at ata1-master UDMA33
GEOM_MIRROR: Device mirror/gm0 launched (2/2).
da0 at twa0 bus 0 target 0 lun 0
da0: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da0: 100.000MB/s transfers
da0: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da1 at twa0 bus 0 target 1 lun 0
da1: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da1: 100.000MB/s transfers
da1: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da2 at twa0 bus 0 target 2 lun 0
da2: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da2: 100.000MB/s transfers
da2: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da3 at twa0 bus 0 target 3 lun 0
da3: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da3: 100.000MB/s transfers
da3: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da4 at twa0 bus 0 target 4 lun 0
da4: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da4: 100.000MB/s transfers
da4: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da5 at twa0 bus 0 target 5 lun 0
da5: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da5: 100.000MB/s transfers
da5: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da6 at twa0 bus 0 target 6 lun 0
da6: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da6: 100.000MB/s transfers
da6: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da7 at twa0 bus 0 target 7 lun 0
da7: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da7: 100.000MB/s transfers
da7: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da8 at twa0 bus 0 target 8 lun 0
da8: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da8: 100.000MB/s transfers
da8: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da9 at twa0 bus 0 target 9 lun 0
da9: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da9: 100.000MB/s transfers
da9: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da10 at twa0 bus 0 target 10 lun 0
da10: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da10: 100.000MB/s transfers
da10: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
da11 at twa0 bus 0 target 11 lun 0
da11: <AMCC 9500S-12   DISK 2.08> Fixed Direct Access SCSI-3 device
da11: 100.000MB/s transfers
da11: 286092MB (585916416 512 byte sectors: 255H 63S/T 36471C)
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/mirror/gm0s1a
This module (opensolaris) contains code covered by the
Common Development and Distribution License (CDDL)
see http://opensolaris.org/os/licensing/opensolaris_license/
WARNING: ZFS is considered to be an experimental feature in FreeBSD.
ZFS filesystem version 6
ZFS storage pool version 6



-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric@caerllewys.net   alaric@metrocast.net   phil@co.ordinate.org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.
From alaric at caerllewys.net  Tue Mar 17 11:31:06 2009
From: alaric at caerllewys.net (Brother Railgun of Reason)
Date: Tue Mar 17 11:31:13 2009
Subject: Boot failure, 7.1R-amd64
Message-ID: <20090317181244.GA23459@prydain.caerllewys.net>

Dieter,
Yes, my ISP has a badly broken antispam system in place.  See if this 
address works any better.

> acpi or apic ?
> 
> With apic disabled, you need
> 
> device atpic
> 
> in your config file.  Someone yanked it starting in 7.0 thinking that
> amd64 systems would never need it.  If apic always worked properly
> maybe you wouldn't need it.

No, I did mean ACPI, not APIC.  Disabling ACPI is necessary even to boot 
7.1R-i386.  I haven't touched APIC.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric@caerllewys.net   alaric@metrocast.net   phil@co.ordinate.org
         Renaissance Man, Unix ronin, Perl hacker, Free Stater
                 It's not the years, it's the mileage.
From andre at albsmeier.net  Thu Mar 19 08:21:03 2009
From: andre at albsmeier.net (Andre Albsmeier)
Date: Thu Mar 19 08:21:11 2009
Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate?
In-Reply-To: <200902141838.n1EIcwQX009259@lurza.secnetix.de>
References: <800496.48763.qm@web45816.mail.sp1.yahoo.com>
	<200902141838.n1EIcwQX009259@lurza.secnetix.de>
Message-ID: <20090319150932.GA2174@schlappy.albsmeier.net>

On Sat, 14-Feb-2009 at 19:38:58 +0100, Oliver Fromme wrote:
> Won De Erick <won.derick@yahoo.com> wrote:
>
> ...
> 
>  > However, how should I make this automatic, something that will update
>  > the CMOS clock everytime the kernel clock is syncronized with a NTP
>  > server? Do I need to make changes on the variables below?
> 
> You seem to misunderstand.  The CMOS clock _is_ always
> updated when you run ntpd.  You do not have to change
> anything.

Hmm, my experience is different here. I have 17 FreeBSD machines
which are all running ntpd (btw, no /etc/wall_cmos_clock). When
being rebooted, they sync the time with ntpdate before starting
ntpd. Somtimes I noticed the time being stepped by several seconds
(up to 50). I observed that the higher the previous uptime had been,
the bigger the stepping during the following reboot was.
While ntpd keeps the kernel time perfectly in sync with our
stratum-1 server the CMOS clocks slowly drift away. The higher
the uptime, the bigger the drift.

I am now using this ugly hack to sync the kernel time to the
CMOS clock (settimeofday() sets both) before reboot and
the problem never appeared again:

#include <sys/time.h>
#include <stdlib.h>
#include <err.h>
#include <sysexits.h>

int main( void )
{
  struct timeval tv;

  if( gettimeofday( &tv, NULL ) != 0 )
    err( EX_DATAERR, "gettimeofday" );

  if( settimeofday( &tv, NULL ) != 0 )
    err( EX_DATAERR, "settimeofday" );

  return 0;
}


A cleaner way might be to call resettodr() in subr_clock.c
just before rebooting.

If there are easier/cleaner ways to keep CMOS time in sync,
I will be happy about any suggestions.

	-Andre
From avg at icyb.net.ua  Thu Mar 19 10:00:02 2009
From: avg at icyb.net.ua (Andriy Gapon)
Date: Thu Mar 19 10:00:08 2009
Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate?
In-Reply-To: <20090319150932.GA2174@schlappy.albsmeier.net>
References: <800496.48763.qm@web45816.mail.sp1.yahoo.com>	<200902141838.n1EIcwQX009259@lurza.secnetix.de>
	<20090319150932.GA2174@schlappy.albsmeier.net>
Message-ID: <49C2773A.8080801@icyb.net.ua>

on 19/03/2009 17:09 Andre Albsmeier said the following:
> On Sat, 14-Feb-2009 at 19:38:58 +0100, Oliver Fromme wrote:
>> Won De Erick <won.derick@yahoo.com> wrote:
>>
>> ...
>>
>>  > However, how should I make this automatic, something that will update
>>  > the CMOS clock everytime the kernel clock is syncronized with a NTP
>>  > server? Do I need to make changes on the variables below?
>>
>> You seem to misunderstand.  The CMOS clock _is_ always
>> updated when you run ntpd.  You do not have to change
>> anything.

Oliver, if this is not misquoted then you are not correct.
Sorry, I noticed this thread too late, so I have to follow up in this fashion.
RTC ("CMOS clock") is updated via resettodr function and you can search kernel
sources yourself to see how many times and where it called.
I reported the problem myself once upon a time:
http://lists.freebsd.org/pipermail/freebsd-hackers/2005-August/013383.html

> Hmm, my experience is different here. I have 17 FreeBSD machines
> which are all running ntpd (btw, no /etc/wall_cmos_clock). When
> being rebooted, they sync the time with ntpdate before starting
> ntpd. Somtimes I noticed the time being stepped by several seconds
> (up to 50). I observed that the higher the previous uptime had been,
> the bigger the stepping during the following reboot was.
> While ntpd keeps the kernel time perfectly in sync with our
> stratum-1 server the CMOS clocks slowly drift away. The higher
> the uptime, the bigger the drift.
> 
> I am now using this ugly hack to sync the kernel time to the
> CMOS clock (settimeofday() sets both) before reboot and
> the problem never appeared again:
> 
> #include <sys/time.h>
> #include <stdlib.h>
> #include <err.h>
> #include <sysexits.h>
> 
> int main( void )
> {
>   struct timeval tv;
> 
>   if( gettimeofday( &tv, NULL ) != 0 )
>     err( EX_DATAERR, "gettimeofday" );
> 
>   if( settimeofday( &tv, NULL ) != 0 )
>     err( EX_DATAERR, "settimeofday" );
> 
>   return 0;
> }
> 
> 
> A cleaner way might be to call resettodr() in subr_clock.c
> just before rebooting.
> 
> If there are easier/cleaner ways to keep CMOS time in sync,
> I will be happy about any suggestions.

I think that ideally RTC time should be updated when discrepancy between it and
kernel time exceeds certain threshold.
Also, we can could have a kernel self-rescheduling callout that would update
hardware clock every half an hour (or whatever, configurable).
Periodic - because we not always have a graceful shutdown (crashes, power loss, etc).

For time beng I am using this hack:
#save OS clock value to time-of-day register (x86 CMOS)
10      0-2,4-23        *       *       *       /usr/local/sbin/resettodr.sh

$ cat /usr/local/sbin/resettodr.sh
#!/bin/sh

# ATTENTION: run this script only at time when you are sure that no
# timezone change (daylight savings time) could possibly occur.
# Otherwise you risk race with adjkerntz -e run from /etc/crontab.
# Time between 06:00 and 23:59 should be safe.


trigger_sysctl_name="machdep.adjkerntz"
sysctl_command="/sbin/sysctl"

$sysctl_command `$sysctl_command -e $trigger_sysctl_name` > /dev/null

Calling this at shutdown would be a bonus.

-- 
Andriy Gapon
From won.derick at yahoo.com  Thu Mar 19 17:44:30 2009
From: won.derick at yahoo.com (Won De Erick)
Date: Thu Mar 19 17:44:36 2009
Subject: Hardware clock is not SYNC'ed with kernel clock by ntpdate?
Message-ID: <402443.1503.qm@web45812.mail.sp1.yahoo.com>


--- On Thu, 3/19/09, Andriy Gapon <avg@icyb.net.ua> wrote:
> on 19/03/2009 17:09 Andre Albsmeier said the following:
> > On Sat, 14-Feb-2009 at 19:38:58 +0100, Oliver Fromme
> > wrote:
> >> Won De Erick <won.derick@yahoo.com>
> >> wrote:
> >>
> >> ...
> >>
> >>  > However, how should I make this
> >>  > automatic, something that will update
> >>  > the CMOS clock everytime the kernel
> >>  > clock is syncronized with a NTP
> >>  > server? Do I need to make changes on
> >>  > the variables below?
> >>
> >> You seem to misunderstand.  The CMOS clock
> >> _is_ always
> >> updated when you run ntpd.  You do not have
> >> to change
> >> anything.
> 
> Oliver, if this is not misquoted then you are not correct.
> Sorry, I noticed this thread too late, so I have to follow
> up in this fashion.
> RTC ("CMOS clock") is updated via resettodr function and
> you can search kernel
> sources yourself to see how many times and where it
> called.
> I reported the problem myself once upon a time:
> http://lists.freebsd.org/pipermail/freebsd-hackers/2005-August/013383.html
> 
> > Hmm, my experience is different here. I have 17
> > FreeBSD machines
> > which are all running ntpd (btw, no
> > /etc/wall_cmos_clock). When
> > being rebooted, they sync the time with ntpdate before
> > starting
> > ntpd. Somtimes I noticed the time being stepped by
> > several seconds
> > (up to 50). I observed that the higher the previous
> > uptime had been,
> > the bigger the stepping during the following reboot
> > was.
> > While ntpd keeps the kernel time perfectly in sync
> > with our
> > stratum-1 server the CMOS clocks slowly drift away.
> > The higher
> > the uptime, the bigger the drift.
> > 
> > I am now using this ugly hack to sync the kernel time
> > to the
> > CMOS clock (settimeofday() sets both) before reboot
> > and
> > the problem never appeared again:
> > 
> > #include <sys/time.h>
> > #include <stdlib.h>
> > #include <err.h>
> > #include <sysexits.h>
> > 
> > int main( void )
> > {
> >   struct timeval tv;
> > 
> >   if( gettimeofday( &tv, NULL ) != 0 )
> >     err( EX_DATAERR,
> > "gettimeofday" );
> > 
> >   if( settimeofday( &tv, NULL ) != 0 )
> >     err( EX_DATAERR,
> > "settimeofday" );
> > 
> >   return 0;
> > }
> > 
> > 
> > A cleaner way might be to call resettodr() in
> > subr_clock.c
> > just before rebooting.
> > 
> > If there are easier/cleaner ways to keep CMOS time in
> > sync,
> > I will be happy about any suggestions.
> 
> I think that ideally RTC time should be updated when
> discrepancy between it and
> kernel time exceeds certain threshold.
> Also, we can could have a kernel self-rescheduling callout
> that would update
> hardware clock every half an hour (or whatever,
> configurable).
> Periodic - because we not always have a graceful shutdown
> (crashes, power loss, etc).
> 
> For time beng I am using this hack:
> #save OS clock value to time-of-day register (x86 CMOS)
> 10      0-2,4-23       
> *       *   
>    *   
>    /usr/local/sbin/resettodr.sh
> 
> $ cat /usr/local/sbin/resettodr.sh
> #!/bin/sh
> 
> # ATTENTION: run this script only at time when you are sure
> that no
> # timezone change (daylight savings time) could possibly
> occur.
> # Otherwise you risk race with adjkerntz -e run from
> /etc/crontab.
> # Time between 06:00 and 23:59 should be safe.
> 
> 
> trigger_sysctl_name="machdep.adjkerntz"
> sysctl_command="/sbin/sysctl"
> 
> $sysctl_command `$sysctl_command -e $trigger_sysctl_name`
> > /dev/null
> 
> Calling this at shutdown would be a bonus.
> 
> -- 
> Andriy Gapon
> 

Cool!


      

From gmpillai at hotmail.com  Thu Mar 19 18:51:36 2009
From: gmpillai at hotmail.com (Mohan Pillai)
Date: Thu Mar 19 18:51:43 2009
Subject: PCI-e wireless cards with Atheros chipsets?
Message-ID: <BLU129-W3431F58BE8CFA6FC5D90A3D4970@phx.gbl>








Hello All,

I'm basically after a PCI-e wireless card (desktop) with an atheros chipset which has a connector for an arial?

I'm trying to find some using the FreeBSD hardware compatability list, but it's proving fairly difficult to find one.

I'm unable to use a PCI as all my PCI slots have been taken up and I only have 2 PCI-e slots available.

I'd much appreciate any input.

Many thanks in advance :)

Mo,

_________________________________________________________________
 25GB of FREE Online Storage ? Find out more
http://clk.atdmt.com/UKM/go/134665320/direct/01/
From craig.ward at gmail.com  Mon Mar 23 07:30:55 2009
From: craig.ward at gmail.com (Craig Ward)
Date: Mon Mar 23 07:31:22 2009
Subject: Dell DRAC 5 with FreeBSD 7.1 remote and local keyboard fail
Message-ID: <4eebdcab0903230705i14c67428m11a17c79aeb8c90e@mail.gmail.com>

Hi,

I'm trying to get a DRAC5 card working with FreeBSD on a poweredge 2950. The
remote and local keyboard (USB) work fine until I get past the FreeBSD boot
screen then they both fail to work.

I've tried messing around with set hint atkbd but to no avail. I've had a
look at the mailing lists and found similar problems but no solutions as of
yet:1

http://lists.freebsd.org/pipermail/freebsd-hardware/2006-August/003722.html
http://lists.freebsd.org/pipermail/freebsd-current/2004-September/038879.html

Anyone using DRAC5 with 7.1 successfully?

Thanks,
Craig.
From d.nostra at gmail.com  Mon Mar 23 08:07:15 2009
From: d.nostra at gmail.com (Michel de Nostredame)
Date: Mon Mar 23 08:07:21 2009
Subject: Dell DRAC 5 with FreeBSD 7.1 remote and local keyboard fail
In-Reply-To: <4eebdcab0903230705i14c67428m11a17c79aeb8c90e@mail.gmail.com>
References: <4eebdcab0903230705i14c67428m11a17c79aeb8c90e@mail.gmail.com>
Message-ID: <454d328c0903230736v70c1f2e6r619aca0b4f4115fd@mail.gmail.com>

Hi,

I did use DRAC5 to install FreeBSD 7.1-RELEASE on DELL 2950 remotely
without any problem.


--
Michel~




On Mon, Mar 23, 2009 at 10:05 PM, Craig Ward <craig.ward@gmail.com> wrote:
> Hi,
>
> I'm trying to get a DRAC5 card working with FreeBSD on a poweredge 2950. The
> remote and local keyboard (USB) work fine until I get past the FreeBSD boot
> screen then they both fail to work.
>
> I've tried messing around with set hint atkbd but to no avail. I've had a
> look at the mailing lists and found similar problems but no solutions as of
> yet:1
>
> http://lists.freebsd.org/pipermail/freebsd-hardware/2006-August/003722.html
> http://lists.freebsd.org/pipermail/freebsd-current/2004-September/038879.html
>
> Anyone using DRAC5 with 7.1 successfully?
>
> Thanks,
> Craig.
> _______________________________________________
> 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 lnb at freebsdsystems.com  Mon Mar 23 11:37:07 2009
From: lnb at freebsdsystems.com (Lanny Baron)
Date: Mon Mar 23 11:37:14 2009
Subject: Dell DRAC 5 with FreeBSD 7.1 remote and local keyboard fail
In-Reply-To: <4eebdcab0903230705i14c67428m11a17c79aeb8c90e@mail.gmail.com>
References: <4eebdcab0903230705i14c67428m11a17c79aeb8c90e@mail.gmail.com>
Message-ID: <49C7D08C.4010309@freebsdsystems.com>

Hi Craig,

I presume you are trying to do that which is shown on the following page:

http://www.freedomtc.com/ipmi2.php

If in fact that is what you are trying to accomplish, I would contact 
the vendor soon.
Regards,
___________________________________________________
Lanny Baron

FreeBSD Systems / Freedom Technologies Corporation
Toll Free: 1.877.963.1900

High Performance Servers and RAID Storage Systems

http://www.FreeBSDsystems.COM
___________________________________________________

Craig Ward wrote:
> Hi,
> 
> I'm trying to get a DRAC5 card working with FreeBSD on a poweredge 2950. The
> remote and local keyboard (USB) work fine until I get past the FreeBSD boot
> screen then they both fail to work.
> 
> I've tried messing around with set hint atkbd but to no avail. I've had a
> look at the mailing lists and found similar problems but no solutions as of
> yet:1
> 
> http://lists.freebsd.org/pipermail/freebsd-hardware/2006-August/003722.html
> http://lists.freebsd.org/pipermail/freebsd-current/2004-September/038879.html
> 
> Anyone using DRAC5 with 7.1 successfully?
> 
> Thanks,
> Craig.
> _______________________________________________
> 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 ivoras at freebsd.org  Tue Mar 24 03:52:19 2009
From: ivoras at freebsd.org (Ivan Voras)
Date: Tue Mar 24 03:52:30 2009
Subject: Dell DRAC 5 with FreeBSD 7.1 remote and local keyboard fail
In-Reply-To: <4eebdcab0903230705i14c67428m11a17c79aeb8c90e@mail.gmail.com>
References: <4eebdcab0903230705i14c67428m11a17c79aeb8c90e@mail.gmail.com>
Message-ID: <gqae0i$64d$1@ger.gmane.org>

Craig Ward wrote:
> Hi,
> 
> I'm trying to get a DRAC5 card working with FreeBSD on a poweredge 2950. The
> remote and local keyboard (USB) work fine until I get past the FreeBSD boot
> screen then they both fail to work.
> 
> I've tried messing around with set hint atkbd but to no avail. I've had a
> look at the mailing lists and found similar problems but no solutions as of
> yet:1

So the screen (video) works but keyboard and mouse don't?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20090324/217b4831/signature.pgp
From bseklecki at collaborativefusion.com  Tue Mar 24 07:44:56 2009
From: bseklecki at collaborativefusion.com (Brian A. Seklecki)
Date: Tue Mar 24 07:45:03 2009
Subject: Dell DRAC 5 with FreeBSD 7.1 remote and local keyboard fail
In-Reply-To: <454d328c0903230736v70c1f2e6r619aca0b4f4115fd@mail.gmail.com>
References: <4eebdcab0903230705i14c67428m11a17c79aeb8c90e@mail.gmail.com>
	<454d328c0903230736v70c1f2e6r619aca0b4f4115fd@mail.gmail.com>
Message-ID: <1237904292.4331.85.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com>




On Mon, 2009-03-23 at 22:36 +0800, Michel de Nostredame wrote:
> Hi,
> 
> I did use DRAC5 to install FreeBSD 7.1-RELEASE on DELL 2950 remotely
> without any problem.


We run an R2/R3 2950 on 7.1 p-whatever w/o incident.

Do you have the latest DRAC5 firmware from Dell?  Are you running AMD64
and not i386?  Did you nuke any old loader.conf settings from the 5.x
days?  ~BAS
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-hardware/attachments/20090324/1ffa074c/attachment.pgp
From paul.g.webster at googlemail.com  Sat Mar 28 10:48:35 2009
From: paul.g.webster at googlemail.com (Paul Webster)
Date: Sat Mar 28 10:48:42 2009
Subject: Asus EEEpc 1000 Wireless Nic
Message-ID: <3b6e2a2e0903281023n5dc41a09p87bc13f07d84355@mail.gmail.com>

Good day all I am going to attempt to write a driver for the RaLink RT2860,
before I begin has anyone started before me and made any progress?
From invite+i-w3imii at facebookmail.com  Tue Mar 31 15:56:25 2009
From: invite+i-w3imii at facebookmail.com (Paul Webster)
Date: Tue Mar 31 15:56:32 2009
Subject: Take a look at my photos on Facebook
Message-ID: <8bde9c79c27423d49fdb421c7d0edbab@register.facebook.com>

Hi Freebsd-hardware,

I set up a Facebook Profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile.

Thanks,
Paul

To join Facebook, please follow the link below:
http://www.facebook.com/p.php?i=1684206320&k=4VC22XQ4P6WM5D1IVDY6WS&r


This email may contain promotional materials. If you do not wish to receive future commercial mailings from Facebook, please click on the link below. Facebook's offices are located at 156 University Ave., Palo Alto, CA 94301.
http://www.facebook.com/o.php?k=57e38d&u=1649766367&mid=3c9942G62556fdfG0G8