Date: Thu, 14 Dec 2017 15:20:47 +0800 From: blubee blubeeme <gurenchan@gmail.com> To: Shane Ambler <FreeBSD@shaneware.biz> Cc: freebsd-multimedia@freebsd.org Subject: Re: FreeBSD amd64 GENERIC kernel Message-ID: <CALM2mE=88_a-9FF3-e49TMPm1pGzwQn1h_wx2gofHK-NRKOpZA@mail.gmail.com> In-Reply-To: <aa346744-94c9-98a4-4de6-c5e956bf096c@ShaneWare.Biz> References: <CALM2mEnnXKAyF_ti_zKYt=1m-ZTfjH5di1cayYjGM4hi9dOxRQ@mail.gmail.com> <aa346744-94c9-98a4-4de6-c5e956bf096c@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 14, 2017 at 1:57 PM, Shane Ambler <FreeBSD@shaneware.biz> wrote: > On 14/12/2017 01:22, blubee blubeeme wrote: > > What sources do kernel modules pull in? > > > > I'm looking at the generic kernel config for am64: > > > > # Sound support > > device sound # Generic sound driver (required) > > device snd_cmi # CMedia CMI8338/CMI8738 > > device snd_csa # Crystal Semiconductor CS461x/428x > > device snd_emu10kx # Creative SoundBlaster Live! and Audigy > > device snd_es137x # Ensoniq AudioPCI ES137x > > device snd_hda # Intel High Definition Audio > > device snd_ich # Intel, NVidia and other ICH AC'97 Audio > > device snd_via8233 # VIA VT8233x Audio > > > > > > The device "sound" is required, does that mean if I totally uncomment out > > all the device including sound, then the machine won't boot? > > > > Does required mean a breaking kernel or just no sound? > > Required means any of the following snd_* devices require it to build. > > Commenting all devices you have listed results in a kernel that allows > the module from audio/oss to be loaded. > > Having experimented with this a few days ago - while the sound and snd_* > loadable modules are built, they are also permanently linked into the > generic kernel which means we can't unload them after startup or prevent > them loading in loader.conf, so to use the audio/oss kernel module a > custom kernel needs to be built with these disabled. > > It is also possible to add > WITHOUT_MODULES=sound snd_cmi snd_csa snd_emu10kx snd_es137x snd_hda > snd_ich snd_via8233 > to /etc/make.conf. > > Note that this leads to a generic kernel without sound that can be > confusing later when you have forgotten. I would recommend using the > custom kernel config with a descriptive name "ident NO_SOUND" so that > later you know why sound stops working. > > I like to keep generic installed as kernel and give custom kernels > different names - > > make buildkernel KERNCONF=NO_SOUND > make installkernel KERNCONF=NO_SOUND KODIR=/boot/kernel.no_sound > > Add kernel="kernel.no_sound" to loader.conf to load it at boot. > Add kernels="kernel,kernel.no_sound" to easily choose between them in > the boot screen. > > I must admit to a lack of documentation regarding the install and use of > audio/oss. While I didn't get far with config, I can contribute the > above to installation. > > -- > FreeBSD - the place to B...Software Developing > > Shane Ambler > > Hi Shane thanks for the tips, I just built a kernel with all of those sound drivers commented out. There was no problem, except for the total lack of sound, which is expected. My sound does make that default *beep* when I delete on an empty terminal though. My goal is to port OSS 4.2 to get rid of all the patches and legacy OSS stuff. OSS has ALSA emulation so I should be able to test /ports/audio packages to see what needs patching, updating etc... Once OSS 4.2 is in FreeBSD then I can work on adding OSS backends for Chromium and other software that I use. Chromium OSS feature request from 2009: https://bugs.chromium.org/p/chromium/issues/detail?id=19470 Would they still accept an OSS backend today?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALM2mE=88_a-9FF3-e49TMPm1pGzwQn1h_wx2gofHK-NRKOpZA>