sound card and freebsd v7.0
jlm at caamora.com.au
Fri Sep 26 23:45:17 UTC 2008
thank you for the help ..
On Fri, Sep 26, 2008 at 08:52:42AM +0200, Bernt Hansson wrote:
> jonathan michaels:
> > Sep 26 13:26:46 hostid kernel: pci0: <bridge> at device 4.3 (no driver attached)
> > Sep 26 13:26:46 hostid kernel: csa0: <CS4280/CS4614/CS4622/CS4624/CS4630> mem 0xf4100000-0xf4100fff,0xf4000000-0xf40fffff irq 10 at device 6.0 on pci0
> > Sep 26 13:26:46 hostid kernel: csa: card is Unknown/invalid SSID (CS4614)
> > Sep 26 13:26:46 hostid kernel: csa0: [GIANT-LOCKED]
> > Sep 26 13:26:46 hostid kernel: csa0: [ITHREAD]
> > Sep 26 13:26:46 hostid kernel: pcm0: <CS461x PCM Audio> on csa0
> > Sep 26 13:26:46 hostid kernel: pcm0: <Cirrus Logic CS4297 AC97 Codec>
> > Sep 26 13:26:46 hostid kernel: pcm0: [GIANT-LOCKED]
> > Sep 26 13:26:46 hostid kernel: pcm0: [ITHREAD]
> > i enabled all teh sound drivers on boot and this is what is in teh
> > /var/log/messages said aboutt he sound card.
> How did you enable the sounddriver?
after the initial install, i created/editied a /boot/loader.conf.local
file to enable all teh sound drivers to see which one came up as being
the one .. grin.
then, i plan to redit teh /boot/loader.conf.local file to reflect teh
changes, after testing .. i am at teh testing stage .. still <smile>.
> What is the output of cat /dev/sndstat?
FreeBSD Audio Driver (newpcm: 32bit 2007061600/i386)
pcm0: <CS461x PCM Audio> at irq 10 kld snd_csa [GIANT] (1p:1v/1r:1v channels duplex default)
> What is the output of kldstat?
Id Refs Address Size Name
1 39 0xc0400000 906518 kernel
2 35 0xc0d07000 4a5ac sound.ko
3 1 0xc0d52000 3730 snd_driver.ko
4 2 0xc0d56000 5014 snd_ad1816.ko
5 2 0xc0d5c000 56b0 snd_als4000.ko
6 2 0xc0d62000 72f8 snd_atiixp.ko
7 2 0xc0d6a000 5858 snd_cmi.ko
8 2 0xc0d70000 5820 snd_cs4281.ko
9 3 0xc0d76000 8aec snd_csa.ko
10 2 0xc0d7f000 b890 snd_ds1.ko
11 2 0xc0d8b000 14d04 snd_emu10kx.ko
12 2 0xc0da0000 90b0 snd_envy24.ko
13 4 0xc0daa000 2a58 snd_spicds.ko
14 2 0xc0dad000 80c8 snd_envy24ht.ko
15 2 0xc0db6000 8a5c snd_es137x.ko
16 2 0xc0dbf000 5ba4 snd_ess.ko
17 5 0xc0dc5000 4c44 snd_sbc.ko
18 2 0xc0dca000 4d60 snd_fm801.ko
19 3 0xc0dcf000 c330 snd_mss.ko
20 2 0xc0ddc000 14324 snd_hda.ko
21 2 0xc0df1000 6f88 snd_ich.ko
22 2 0xc0df8000 9220 snd_maestro.ko
23 2 0xc0e02000 a3c4 snd_maestro3.ko
24 2 0xc0e0d000 116a0 snd_neomagic.ko
25 2 0xc0e1f000 532c snd_sb16.ko
26 2 0xc0e25000 4c88 snd_sb8.ko
27 2 0xc0e2a000 5ef4 snd_solo.ko
28 2 0xc0e30000 5a74 snd_t4dwave.ko
29 2 0xc0e36000 7f24 snd_via8233.ko
30 2 0xc0e3e000 4fa8 snd_via82c686.ko
31 2 0xc0e43000 5bc0 snd_vibes.ko
32 1 0xc0e49000 6a32c acpi.ko
33 1 0xc2486000 22000 linux.ko
34 1 0xc26c7000 2000 warp_saver.ko
> > the drive is a 120 gb hitachi deskstar .. linux (several of teh most
> > recent distributions, ubuntu/centos/fedora sees it as a 120 gb, as
> > dose solaris v10/v11 but freebsd calls it a 114 gb drive
> That's quite simple, freebsd calls it for what it is a 114 Gb disk.
sorry, i am a bit nervious with this v7 installation, i had some real
'issues' with the installation of freebsd v6.2 on my hardware and they
seem to being repeated with this v7 .. i am using the basic sysinstall
tool set that provides a basic installation.
i do not understand this .. i mean i do not understant how freebsd can
take a drive with the cylinders/heads/sectors that produces xxx million
sectors that muitiplied by 512 bytes producs 120 gb (real gb) solaris
also identifies this as a 120 gb drive as do several linux distrinutions
(centos and ubuntu based).
one item i forgot to include that freebsd v7 came back with several
different (with several succesive reboots) free space guesses (no
intervention from me just putting in teh dvd and booting .. in several
machines whose bios' all said that this is a 120 (real) gb drive
could this be a "lba" confusion/issue between teh drive/bios/freebsd
interpretation ?? it is a term i recall from earlier, when thes
kinds of drives first appeared and casued significant consternations
for everybody not just freebsd. it is a problems as far as i have
several of thes drives to be putting into several 'server' machines
where this kind of freespace 'loss' would become an issue --- hardware
density, as in drivers per terabyte leading to power consumption/space
and heating conciderations in raid arrays (five and ten drive rack)s
this is not a 'real' problem as 95 gb (whats left after install from a
114 gb start point) is more than enough for this boxes task-load. it is
that i find this a bit confusing/interesting, esp given that fresbie
v1.1 aslo sees this as a 120 gb drive ??? just interested in fiding
out what is going on and if this is a pointer to future hardware
mis-identification --- i understand the difference between "real"
gigabytes and "marketing department" gigabytes
much kind regards and appreciations
powered by ..
QNX, OS9 and freeBSD -- http://caamora com au/operating system
==== === appropriate solution in an inappropriate world === ====
More information about the freebsd-questions