06-12-2008, 02:02 AM
I have done two fresh installs
The error I get and have not as of yet been able to clear is...
Sound server informational message:
Error while initializing the sound driver:
device /dev/dsp can't be opened (No such file or directory)
The sound server will continue, using the null output device.
I have a sound blaster audigy SE card installed.
FreeBSD Audio Driver (newpcm)
none8@pci1:10:0: class=0x040100 card=0x100a1102 chip=0x00071102 rev=0x00 hdr=0x00
vendor = 'Creative Technology LTD.'
device = 'C6SB0410515017656A Audigy SE'
class = multimedia
subclass = audio
Id Refs Address Size Name
1 19 0xc0400000 7ab3a4 kernel
2 3 0xc0bac000 1eed0 linux.ko
3 1 0xc0bcb000 7674 snd_emu10k1.ko
4 2 0xc0bd3000 23908 sound.ko
5 1 0xc0bf7000 3890 ulpt.ko
6 1 0xc0bfb000 80c784 nvidia.ko
7 1 0xc1408000 5c264 acpi.ko
8 1 0xc5b28000 6000 linprocfs.ko
/dev/mixer: No such file or directory
The device file is missing from /dev.
Perhaps you have not installed and started Open Sound System yet
the driver I believe I am suppose to be using is snd_emu10k1.ko
I added this to the boot/loader.conf file, I've tried removing it and adding it manually through nothing provides me with sound thus far.
I've read the forums and followed there suggestions, I'm not seeing any result, so perhaps some one out there has some ideas.
Any and all help provided is appreciated, I have had this same sound card working in linux, as well as windows. In most linux's it works out of box on install, some have required tweaking...
06-12-2008, 08:35 PM
As far as I know the Audigy SE is a CA-0106 card not an EMU10K* card like some of the other Audigy cards.
I don't know of any driver that supports it, maybe someone else here (or someone on daemonforums.org) might know.
I have an Audigy 4 which I'd rather _throw out_ that works well using FreeBSD 6.x and the old emu10kx driver and Linux 2.6 with alsa and their emu10k* drivers last I bothered to boot either on the test machine.
06-12-2008, 11:01 PM
I recall the ca-0106 works fine in linux with this card, I didn't know about daemonforums.org (definitely noting it)...I'm doing the crossover thing from linux to BSD...Can that driver be ported or remade for pc-bsd?
I have integrated sound available on the board (it was scratchy in windows hence the expansion card) I'm using a gigabyte board with the nforce2 chipset, does pc-bsd have a driver for that? if not, what is a good sound chipset to be using with bsd's in general? In linux you couldn't go wrong with intel products...is that same true here?
Audology SE works with OSS drivers form the ports in full duplex mode. I had the card and I used it 6.2 stable. OSS driver from the ports should be one of the packages installed on PC-BSD. Normally on vanilla FreeBSD you would enable it by
editing rc.conf file with
I am clueless how PC-BSD works. By the way in the mean time I got rid of the card and FreeBSD all together. I am OpenBSD user.
Speaking of Linux drivers for sound they are useless as they are based on ALSA standard while BSDs and Solaris use OSS. You can inform yourself why from.
For the answers on your other questions you should read hardware notes.
OSS is dead. Long live OSS!
Sunday, April 8th, 2007
The question often asked from me is: “OSS is deprecated so why are you still developing and maintaining it?”.
This is a short and simple question. However the answer is not short or simple. First of all we need to return some 10 years back in time.
Once upon a time in Linux there was a tiny sound subsystem called VoxWare (formerly known as the Linux Sound Diver). It was maintained by me and released under GPL for Linux (and under the BSD license for FreeBSD and some other Unix variants). That piece of code was included in the Linux kernel source tree. I was working on the code “just for fun”. However it become too difficult to work on the sound stuff in my spare time at the same time when working on some Windows projects for my living. I was contacted by 4Front Technologies and we desided to make our living with a commercial version of OSS.
Unfortunately it took too long time to find the proper procedure to support the GPL/BSD version and the commercial one from the same source tree. So a well known Linux distribution vendor got irritated and hired another person to create another version of OSS for them (without even asking me to do that). The result was rather different than my plans for the future so I had to quit as the maintainer of sound for Linux.
Since that moment the kernel (OSS/Free) and the commercial OSS versions have been maintained by different teams. Unfortunately the Linux kernel version of the API got frozen to the OSS 3.8 version while we continued the development of the official API. In addition the OSS/Free version was (unfortunately) restructured so that most of the common (device independent) code was duplicated in the individual low level drivers. This made it impossible to keep the kernel drivers up to date with the development made to the official OSS version. The result was that the kernel drivers got frozen to the 3.8 version forever, unfortunately.
Then couple of years later a group of fearless programmers had created an entirely different, incompatible and Linux-only sound API called ALSA. They pushed it to the Linux kernel tree and the old OSS/Free version was declared as “deprecated”. It was supposed to become more advanced that OSS/Free 3.8. It was released under GPL (only) so it seemed to be the right thing. However application programmers didn’t like the ASA API and continued to use OSS instead. It was necessary to declare OSS as “deprecated” to push application developers to support ALSA instead of OSS.
However even that was not enough. Application developers still preferred OSS. This was bad for ALSA because they had to provide OSS emulation. In addition the kernel level OSS emulation bypassed some features (such as dmix) that ALSA has implemented in library level. So the OSS emulation was later implemented in library level. However providing OSS emulation in ALSA caused some side effects. Developers of audio applications still refused to convert to ALSA because the OSS API was still available. So some even more agressive policy was needed.
So far the pro-ALSA Borgs have managed to get Linux distributions to compile most audio enabled applications with just the ALSA plugins enabled (all OSS support is stripped). In some cases the distributions even try to prevent users from removing ALSA and installing OSS by keeping ALSA’s mixer interface busy (the Gnome/GTK mixer appled is immediately relaunched if it gets killed). Or the kernel may have been modified to keep parts of kernel’s sound core included even sound support is completely disabled in kernel’s configuration. “We are the ALSA project. Your system will be assimilated. Resistance is futile”. Has anybody ever heard about “freedom of choice”?
ALSA was officially included in the Linux 2.6.0 kernel that was released for more than 3 years ago (December 2003). If ALSA is as great as they claim then shoudn’t it have completely replaced OSS in all applications during that time? Apparently that has not happened so far. Will it happen during next three years? I don’t think so.
There is a relatively small community of ALSA believers who have written most of the currently available ALSA applications (usually called ALSA this or ALSA that). Older applications still support OSS in addtion to OSS. Some newer ones ALSA-only because their developers have been told that the OSS API will disapper tomorrow. However the ALSA API is still almost completely undocumented (after three years of it’s release) so how can anybody expect that programmers could develop good applications based on it.
A funny detail is that even some key developers of ALSA now suggest that developers use the Jack API instead of alsa-lib (btw, Jack has a fully functional OSS plugin). Somehow this is starting to smell like Emperor’s New Clothes.
Back to the subject. The latest Linux 2.6.20 kernel still has the old and obsolete 10+ years old OSS version included. It’s being killed (for a very good reason). However it looks like we are getting a very long funeral. ALSA too has OSS emulation. In fact there are two redundant versions of it: one in the kernel and another implemented in library level. Both of them emulate only the now obsolete 3.8 API version. This is the dead and deprecated OSS.
However this is not the only OSS. We at 4Front have continued working on Open Sound System for all the past years. It has become the real Common Unix and Linux Sound Solution (CULSS). In addtion to Linux it’s now the official sound subsystem for all the Unix variants (other than MacOS). However for many Linux diehards it’s not an alternative because:
* It’s not GPLed (yet). Instead it’s a commercial product by some evil capitalist pigs.
* It’s not in the Linux kernel source tree so it doesn’t exist.
* It’s being used also by the public enemies of Linux.
* It’s “binary only”.
For the above reasons the benefits of OSS are widely ignored:
* It’s based on the widely known Unix/POSIX/Linux device model.
* It’s fully documented (OTOH some parts of the documentation are still under construction).
* The API is simple and compact which makes it very easy to use for programmers.
* It has been there for 15 years so practically all applications already support it.
* It’s kernel only.
* It’s designed to work under general purpose operating systems such as Linux and Unix. There is no need to use any special real time enabled kernels (they can be used but it’s not a requirement).
* The limitations and “idiosyncrasies” referred by ALSA’s marketing propaganda have been fixed years ago.
* Fully dynamic minor/major device number allocation which permits unlimited number of audio/MIDI/mixer devices.
* New device naming that makes applications immune to changes in the device configuration (installing and removing devices).
* Transparent virtual mixing that makes it possible for any number of applications to share the same physical audio device(s). This also works for recording and full duplex.
* Powerful device enumeration support.
Then we have ALSA which is:
* Not documented. Use the Source, Luke!
* The API is not compatible/similar with anything else (past, present or future).
* Very thin device abstraction.
* The API is designed for low/zero latency which makes it very challenging to use in normal applications that don’t have any latency requirements.
* Requires redundant layers libraries in addition to the kernel space code (alsa-lib, Jack). This causes increased memory requirements in embedded systems.
* Has enormous number of functions (1500+ couple of years ago). Majority of the calls have not been used by any applications (even many applications use different functions than any others). Massive number of unnecessary library functions increases the memory footprint even further. And what about the CPU consumption? And will anybody be ever possible to document (or even test) all of them?
* There are multiple (redundant) transfer methods for audio. How does the programmer know which one should be used with given hardware?
* Some devices use interleaved channels (for stereo and multich) while some others use non-interleaved.
* Static minor number assignment that causes waste of the available device/card space. Number of cards, devices and subdevices possible in the system is limited.
* Strange configuration file mechanism that requires degree in LISP programing to understand it.
* Sharing of devices is based on the dmix feature that nobody but experts can configure properly.
* The API is based on callbacks which requires deep programming knowledge from the developers. Gotos have been considered harmful for decades. Callbacks are even worse (in fact they are a re-incarnation of the famous come-from statement).
So which one should be declared as deprecated? As we are talking about APIs the right authority to make the decision are the application developers. They have their “freedom of choice”.
Actually it’s not nice to compare OSS against ALSA in this way so I don’t continue any further. However they have done the same for years (see ALSA’s web page (before they remove that stuff)). So I coudn’t resist. At least we have given them three years of time to discover and fix the above problems but nothing seem to have happened. And I didn’t even mention MIDI yet. Maybe I should do it next…
06-13-2008, 02:24 AM
Still getting the same error, and no sound, the emu10k1.ko is still loading even though I've removed it from the loader.conf file...
Sound subsystem and version: OSS 4.0 (b1015/200804181033) (0x00040003)
Platform: FreeBSD/i386 6.3-RELEASE-p2 FreeBSD 6.3-RELEASE-p2 #7: Thu Apr 17 11:21:34 EDT 2008 root@pcbsd:/usr/obj/usr/src/sys/PCBSD
NOTICE! You don't have any audio devices available.
It looks like your audio hardware was not recognized
by OSS. Please contact 4Front technologies for help
(http://www.opensound.com/support.cgi). Don't forget to
include your soundon.log file to the support request.
Any other ideas?
I have read a similar article about the sound in linux, and the push for alsa, I think it was title the sorry state of audio in linux or something to that summation. I personally wanted to switch to bsd, for the simple fact any one I talk to that runs it loves it. I like linux, I can't say I love it, just wanted to try out the bsd's before throwing in the towel.
You have to disable all kernel audio drivers .ko files. On vanilla FreeBSD they do not load by default so oss_enable="YES" in /etc/rc.conf and reboot will do the trick. You are mixing audio commands for OSS from the base system and the one from the kernel. Go to Front Technologies and look the documentation
are some of the commands for OSS from the ports. On the another hand /dev/mixer is device from the base of the system and
should not exist if you are using OSS from ports. Soundstat, mixer and similar are commands for the kernel drivers.
As I said I do not use PC-BSD so I could not tell you what is going on but as I said earlier your audio card is supported and I used 6-7 months on FreeBSD 6.2 stable before I got read of FreeBSD all together and installed OpenBSD on that machine.
06-13-2008, 08:41 AM
I have done as you suggested with out any further success... Here is most of my system info.
Copyright (c) 1992-2008 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 6.3-RELEASE-p2 #7: Thu Apr 17 11:21:34 EDT 2008
ACPI APIC Table: <Nvidia AWRDACPI>
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 2500+ (1830.01-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0
real memory = 1073676288 (1023 MB)
avail memory = 1028890624 (981 MB)
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <Nvidia AWRDACPI> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0
pci0: <ACPI PCI bus> on pcib0
Correcting nForce2 C1 CPU disconnect hangs
pci0: <memory, RAM> at device 0.1 (no driver attached)
pci0: <memory, RAM> at device 0.2 (no driver attached)
pci0: <memory, RAM> at device 0.3 (no driver attached)
pci0: <memory, RAM> at device 0.4 (no driver attached)
pci0: <memory, RAM> at device 0.5 (no driver attached)
isab0: <PCI-ISA bridge> at device 1.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 1.1 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xea002000-0xea002fff irq 20 at device 2.0 on pci0
usb0: OHCI version 1.0, legacy support
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xea003000-0xea003fff irq 21 at device 2.1 on pci0
usb1: OHCI version 1.0, legacy support
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ehci0: <NVIDIA nForce2 USB 2.0 controller> mem 0xea004000-0xea0040ff irq 22 at device 2.2 on pci0
usb2: EHCI version 1.0
usb2: companion controllers, 4 ports each: usb0 usb1
usb2: <NVIDIA nForce2 USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 6 ports with 6 removable, self powered
pcib1: <ACPI PCI-PCI bridge> at device 8.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <simple comms, generic modem> at device 7.0 (no driver attached)
skc0: <D-Link DGE-530T Gigabit Ethernet> port 0xa400-0xa4ff mem 0xe9000000-0xe9003fff irq 16 at device 8.0 on pci1
skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9)
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:19:5b:2f:0f:9c
miibus0: <MII bus> on sk0
e1000phy0: <Marvell 88E1011 Gigabit PHY> on miibus0
e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
pci1: <multimedia, video> at device 9.0 (no driver attached)
pci1: <multimedia, audio> at device 10.0 (no driver attached)
atapci0: <nVidia nForce2 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 9.0 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pcib2: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci2: <ACPI PCI bus> on pcib2
nvidia0: <Unknown> mem 0xe4000000-0xe4ffffff,0xd0000000-0xdfffffff,0xe5000000-0xe5ffffff irq 19 at device 0.0 on pci2
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0: <ECP parallel printer port> port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
pmtimer0 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
uscanner0: Canon CanoScan, rev 1.10/1.00, addr 2
uhid0: WiseGroup.,Ltd MP-8866 Dual USB Joypad, rev 1.00/2.88, addr 3, iclass 3/0
ums0: Microsoft Microsoft Trackball Optical?, rev 1.10/1.21, addr 2, iclass 3/1
ums0: 5 buttons and Z dir.
Timecounter "TSC" frequency 1830013072 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 190781MB <WDC WD2000JB-00GVA0 08.02D08> at ata0-master UDMA100
acd0: DVDR <HL-DT-STDVD-RAM GSA-H54N/1.00> at ata1-master UDMA66
cd0 at ata1 bus 0 target 0 lun 0
cd0: <HL-DT-ST DVD-RAM GSA-H54N 1.00> Removable CD-ROM SCSI-0 device
cd0: 66.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
Trying to mount root from ufs:/dev/ad0s1a
Jun 12 23:41:09 CPU-JP kernel: Trying to mount root from ufs:/dev/ad0s1a
Jun 12 23:41:12 CPU-JP dhclient: New IP Address (sk0): 192.168.191.110
Jun 12 23:41:12 CPU-JP dhclient: New Subnet Mask (sk0): 255.255.255.0
Jun 12 23:41:12 CPU-JP dhclient: New Broadcast Address (sk0): 192.168.191.255
Jun 12 23:41:12 CPU-JP dhclient: New Routers (sk0): 192.168.191.1
Jun 12 23:41:12 CPU-JP ntpd: ntpd 4.2.0-a Thu Apr 17 10:55:12 EDT 2008 (1)
Jun 12 23:41:14 CPU-JP root: /etc/rc.d/sysctl: WARNING: sysctl hw.snd.pcm0.vchans does not exist.
Jun 12 23:41:14 CPU-JP root: /etc/rc.d/sysctl: WARNING: sysctl hw.snd.maxautovchans does not exist.
Jun 12 23:41:39 CPU-JP sudo: xuser : TTY=unknown ; PWD=/usr/home/xuser ; USER=root ; COMMAND=/PCBSD/SystemUpdater/bin/SystemUpdater.sh
Jun 12 23:41:46 CPU-JP su: xuser to root on /dev/ttyp2
Jun 12 23:41:46 CPU-JP su: xuser to root on /dev/ttyp2
Jun 12 23:49:49 CPU-JP ntpd: time reset +0.254964 s
Jun 12 23:56:44 CPU-JP su: xuser to root on /dev/ttyp5
Jun 12 23:56:44 CPU-JP su: xuser to root on /dev/ttyp5
Jun 13 00:06:28 CPU-JP su: xuser to root on /dev/ttyp3
Jun 13 00:11:13 CPU-JP ntpd: time reset -0.236574 s
Jun 13 00:11:13 CPU-JP ntpd: kernel time sync enabled 2001
Jun 13 00:30:59 CPU-JP su: xuser to root on /dev/ttyp4
Jun 13 00:30:59 CPU-JP su: xuser to root on /dev/ttyp4
Jun 13 02:38:20 CPU-JP su: xuser to root on /dev/ttyp4
# Enable the pcbsd startup / shutdown scripts
#Enable samba server
# Disable LPD
# Enable CUPS
# FSCK Enhancements
# tmpmfs Flags
# Denyhosts Startup
# powerd: adaptive speed while on AC power, adaptive while on battery power
powerd_flags="-a adaptive -b adaptive" # set CPU frequency
# enable HALd
# Enables support for HPLIP
# ntpdate is deprecated and will eventually be removed from the distribution since
# the same functionality is available in ntpd(8).
# Without "ntpd_sync_on_start" option, ntpd refuses to perform an
# initial correction if the clock offset is too large.
# Enable the firewall
Filesystem 1M-blocks Used Avail Capacity Mounted on
/dev/ad0s1a 184278 3569 165966 2% /
devfs 0 0 0 100% /dev
linprocfs 0 0 0 100% /compat/linux/proc
procfs 0 0 0 100% /proc
/dev/md0 771 0 708 0% /tmp
last pid: 68034; load averages: 0.62, 1.65, 2.38 up 0+02:57:59 02:38:26
104 processes: 4 running, 100 sleeping
Mem: 161M Active, 362M Inact, 159M Wired, 1572K Cache, 110M Buf, 301M Free
Swap: 512M Total, 512M Free
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
67966 root 1 97 0 26644K 22720K select 0:01 7.34% kcmshell
1210 root 1 96 0 90004K 69196K select 53:55 3.42% Xorg
67901 xuser 1 105 0 24804K 19944K select 0:00 3.10% kdesu
1423 xuser 1 96 0 31716K 27112K select 0:09 0.49% kdeinit
1522 xuser 3 20 0 49664K 43360K kserel 0:37 0.00% kdeinit
1519 xuser 1 -8 0 24628K 19960K piperd 0:24 0.00% NetworkTray
11667 xuser 1 96 0 59212K 54304K select 0:20 0.00% kdeinit
1401 xuser 1 96 0 30216K 25300K select 0:12 0.00% kdeinit
1259 root 1 96 0 3520K 1964K select 0:07 0.00% hald-addon-mouse-sy
1015 root 1 8 0 1732K 1232K wait 0:07 0.00% sh
1410 xuser 1 96 0 27504K 22080K select 0:07 0.00% kdeinit
2064 xuser 1 60 -36 10864K 8292K select 0:06 0.00% artsd
1262 root 1 96 0 1880K 1464K select 0:05 0.00% hald-addon-storage
1421 xuser 1 96 0 36292K 30864K select 0:05 0.00% kdeinit
1230 haldaemon 1 96 0 5300K 3908K select 0:04 0.00% hald
544 root 1 96 0 1436K 912K select 0:03 0.00% moused
1671 root 1 96 0 36928K 31308K select 0:02 0.00% konqueror
1355 xuser 1 96 0 3832K 2576K select 0:01 0.00% gam_server
Any other ideas? suggestions? I have copies of freeBSD 7.0 ready to go, and desktop bsd...I'm looking for a BSD system capable of offering a nice desktop experience, with multimedia, and gaming in mind.
06-13-2008, 07:48 PM
In regard to how sound works in PC-BSD, as I understand it:
OSS is installed and should be enabled in rc.conf by default.
At boot time one of the 'PC-BSD'isms hooked into the resource configuration system (man rc) uses a flat file xml database to *try* loading a corresponding loadable kernel module (LKMs).
06-13-2008, 10:43 PM
I'm not sure what to say...I reinstalled pcbsd, same issue persisted, I tried installing freebsd and couldn't get to a graphical interface, though I got some good experience in the net install process, and using the ports system, and sysinstall. I now have desktopbsd loaded in the hopes that I could get somewhere further...same issue, no sound, so I'm going to take this card out enable the onboard, and see what happens. There's a huge learning curve on the switch, and I appreciate all the help. Again, Thank you, I'll post back in a bit once I've adjusted my hardware.
06-20-2008, 03:28 AM
I'm using a gigabyte board with the nforce2 chipset, does pc-bsd have a driver for that?
Yes, snd_ich(4) (http://www.freebsd.org/cgi/man.cgi?query=snd_ich&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE+and+Ports&format=html) supports nForce 2.
You can load it with:
# kldload snd_ich
If this works, you can make the change persistent across boots by adding this line to /boot/loader.conf (Create the file if it does not exist):
By the way, PC-BSD (but not FreeBSD) should detect this automagiclly ... Not sure why this doesn't work for you...
vBulletin® v3.8.5, Copyright ©2000-2013, Jelsoft Enterprises Ltd.