Intel High Definition Audio (Azalia) - 6.0 CURRENT

[Milez]

Anyone tried 7-CURRENT with HDA? Is it ok? I need my note for work, so I better install CURRENT versions only if they don't crush whole system...

[MrL0Lz]

I have tried -CURRENT, it does not work. Or at least with mine, which is
none1@pci0:27:0: class=0x040300 card=0x81bb104d chip=0x26688086 rev=0x04
hdr=0x00
vendor = 'Intel Corporation'
device = '82801FB/FR/FW/FRW Intel High DefiNition Audio Controller'
class = multimedia
uhci0@pci0:29:0: class=0x0c0300 card=0x81b9104d chip=0x26588086 rev=0x04

[MrL0Lz]

dev:
Is there a way to set the oss driver to verbose logging. simply statting its "failed" doesnt really say much.......

[dev]

dev:
Is there a way to set the oss driver to verbose logging. simply statting its "failed" doesnt really say much.......

We have been studying the reason why the drivers fail and the only reason we can now come up with is that somehow FreeBSD puts the device in some kind of sleep mode because it's on the PCI-Express bus.

We have OpenBSD 3.8 and NetBSD 3.0 working perfectly on the HDA device
So the reason has got to be something related to FreeBSD's handling of the PCI Express bus - the reason why I say that is because we find similar timeouts in MAudio devices that work perfectly with standard PCI bus machines.

Regards
Dev Mazumdar

[MrL0Lz]

Dev:
I finally managed to a responce back from one the FreeBSD sound developers. While its not entirely helpful, it does give a direction. He had stated to:

"No, I don't know what the problem is. But hardware detection is a task
of the driver. So if there's a problem, it's either a bug in the
driver, or a bug in the low level probing/allocation routines of
FreeBSD. So if 4Front knows what the problem is, a mail to current@freebsd.org
should help (by either fixing the bug in FreeBSD, or by explaining what
to do in the driver)."

I'm almost positive they'll need more than a "failed" message. I'm sure there is a way to all the low level stuff, but I'm not sure what exactly. The link below may provide some assistance
http://www.freebsd.org/doc/en_US.ISO885 ... g-kld.html

[dev]

Dev:
I finally managed to a responce back from one the FreeBSD sound developers. While its not entirely helpful, it does give a direction. He had stated to:

"No, I don't know what the problem is. But hardware detection is a task
of the driver. So if there's a problem, it's either a bug in the
driver, or a bug in the low level probing/allocation routines of
FreeBSD. So if 4Front knows what the problem is, a mail to current@freebsd.org
should help (by either fixing the bug in FreeBSD, or by explaining what
to do in the driver)."

I'm almost positive they'll need more than a "failed" message. I'm sure there is a way to all the low level stuff, but I'm not sure what exactly. The link below may provide some assistance
http://www.freebsd.org/doc/en_US.ISO885 ... g-kld.html

Hi,


We have contacted Scott Long and will be working with him to resolve this issue.


best regards
Dev Mazumdar

[dev]

Turns out that the driver works in FreeBSD 4.11. There are some issues with FreeBSD 6.0 - and looks like a kernel issue rather than OSS.

[MrL0Lz]

Dev:
Its good to hear we are finally getting support! Once it is working I will be more than happy to pay for a license, and a few extra licenses with I dont need. Good support dev, thanks for sticking with it

[Guest]

Dev:
Its good to hear we are finally getting support! Once it is working I will be more than happy to pay for a license, and a few extra licenses with I dont need. Good support dev, thanks for sticking with it

Good news - we finally found the problem and now there's an updated OSS 3.99.3d version that has HDA working.


regards
Dev