From owner-freebsd-questions@FreeBSD.ORG Thu Oct 9 00:13:18 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 864141A5 for ; Thu, 9 Oct 2014 00:13:18 +0000 (UTC) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.31.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1666E2C5 for ; Thu, 9 Oct 2014 00:13:17 +0000 (UTC) Received: from [84.131.114.99] (helo=[192.168.42.90]) by smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.84) (envelope-from ) id 1Xc1Kz-0007gd-2C; Thu, 09 Oct 2014 02:12:09 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: How do I tell which driver I need for sound? From: Stephen Riehm In-Reply-To: Date: Thu, 9 Oct 2014 02:12:08 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <19E5161B-5154-48DB-80F6-5E24B2DFB28B@opensauce.de> References: <20141008204214.GA93107@home.parts-unknown.org> <20141008220048.GB39434@home.parts-unknown.org> To: Waitman Gobble X-Mailer: Apple Mail (2.1878.6) X-Df-Sender: bGlzdHNAb3BlbnNhdWNlLmRl Cc: "freebsd-questions@freebsd.org" , David Benfell X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 00:13:18 -0000 Thanks for the tip, but sadly, no dice :-( I just discovered another post which mentioned "dmidecode" - looking = through that I see: On Board Device 3 Information Type: Sound Status: Disabled Description: Realtek High Definition Audio Device ... Onboard Device Reference Designation: AUDIO1 Type: Sound Status: Disabled Type Instance: 1 Bus Address: 0000:00:1b.0 so by the looks of it, the device(s) are disabled in the BIOS (which I = sadly can't access due to a BIOS bug). Thanks anyway, Steve On 09 Oct 2014, at 01:54, Waitman Gobble wrote: > Try ports/audio/oss - it's a much newer version than oss in base. Many = more features, and there's an x mixer that's really great. Caveat - = might not use the drivers in ports/audio/oss if you have any sort of usb = sound device (microphone, speakers, etc.) Last time I experimented with = it would cause bad things to happen. (You can use the mixer and ossinfo = tool without using the drivers in the port., eg. ossxmix and ossinfo) >=20 > Waitman >=20 >=20 >=20 > On Wed, Oct 8, 2014 at 4:28 PM, Stephen Riehm = wrote: > Hi, >=20 > I'm also a bit lost with this. (Yes I've also read the sound-setup = handbook) > My /boot/loader.conf consists of: >=20 > autoboot_delay=3D"2" > zfs_load=3D"YES" > sound_load=3D"YES" # Digital sound subsystem > snd_hda_load=3D"YES" # Intel High Definition Audio = (Controller) > snd_driver_load=3D"YES" # All sound drivers >=20 > and even after multiple reboots, cat /dev/sndstat reports: >=20 > root:~ # cat /dev/sndstat > Installed devices: > root:~ # >=20 > and: >=20 > root:/boot # kldstat > Id Refs Address Size Name > 1 94 0xffffffff80200000 1618b88 kernel > 2 1 0xffffffff81819000 24d888 zfs.ko > 3 2 0xffffffff81a67000 6658 opensolaris.ko > 4 1 0xffffffff81a6e000 3fe8 snd_driver.ko > 5 2 0xffffffff81a72000 89c0 snd_vibes.ko > 6 2 0xffffffff81a7b000 7918 snd_via82c686.ko > 7 2 0xffffffff81a83000 83d0 snd_t4dwave.ko > 8 4 0xffffffff81a8c000 2850 snd_spicds.ko > 9 2 0xffffffff81a8f000 a788 snd_solo.ko > 10 5 0xffffffff81a9a000 60c8 snd_sbc.ko > 11 2 0xffffffff81aa1000 80d0 snd_sb8.ko > 12 2 0xffffffff81aaa000 8120 snd_sb16.ko > 13 2 0xffffffff81ab3000 14e88 snd_neomagic.ko > 14 3 0xffffffff81ac8000 16850 snd_mss.ko > 15 2 0xffffffff81adf000 e7d0 snd_maestro3.ko > 16 2 0xffffffff81aee000 d598 snd_maestro.ko > 17 2 0xffffffff81afc000 7268 snd_fm801.ko > 18 2 0xffffffff81b04000 a8b0 snd_ess.ko > 19 2 0xffffffff81b0f000 c9b8 snd_envy24ht.ko > 20 2 0xffffffff81b1c000 dfd0 snd_envy24.ko > 21 2 0xffffffff81b2a000 fdf8 snd_ds1.ko > 22 2 0xffffffff81b3a000 82b0 snd_cs4281.ko > 23 2 0xffffffff81b43000 a308 snd_atiixp.ko > 24 2 0xffffffff81b4e000 8ee8 snd_als4000.ko > 25 2 0xffffffff81b57000 b880 snd_ad1816.ko >=20 > (no snd_hda in there?) >=20 > I'm running 10.0 STABLE on an Intel NUC D54250WYK (amd64) >=20 > Thanks for any insights! >=20 > Steve >=20 > On 09 Oct 2014, at 01:07, Warren Block wrote: >=20 > > On Wed, 8 Oct 2014, David Benfell wrote: > > > >> On Wed, Oct 08, 2014 at 03:39:57PM -0600, Warren Block wrote: > >>> On Wed, 8 Oct 2014, David Benfell wrote: > >>> > >>>> For some reason, sound has stopped working and I assume I should > >>>> reload the driver. But which one? > >>> > >>> = https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.htm= l > >> > >> Been there. There is no obvious match between the hardware I have = and > >> the kernel modules I have available. > > > > The important part is > > cat /dev/sndstat > > > > But for most motherboards, adding > > snd_hda_load=3D"YES" > > > > to /boot/loader.conf is enough. > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org" >=20 >=20 >=20 > --=20 > Waitman Gobble > San Jose California USA > 510-830-7975