Opened 15 years ago

Last modified 10 months ago

#4755 new bug

ICH7, 8 & 9 Audio Not working with Alpha — at Version 20

Reported by: kvdman Owned by: korli
Priority: normal Milestone: Unscheduled
Component: Drivers/Audio/HDA Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by diver)

I don't know whether this is known or not, but by looking at hardware profiles on Haikuware, it seems ICH7-9 audio isn't working with the Haiku alpha images. One user claimed that after installing OSS they got sound working (ICH7).

Is there a way to have OSS installed/used when an ICH7-9 soundcard is detected?

It seems one user has access to a lot of hardware and has submitted several reports, perhaps he could help debugging.

Not working:

[http://www.haikuware.com/details/compaq-610]
device Multimedia controller (Audio device) [4|3|0]
  vendor 8086: Intel Corporation
  device 284b: 82801H (ICH8 Family) HD Audio Controller

[http://www.haikuware.com/details/compaq-dx2400]
device Multimedia controller (Audio device) [4|3|0]
  vendor 8086: Intel Corporation
  device 293e: 82801I (ICH9 Family) HD Audio Controller

Works after installing OSS:

[http://www.haikuware.com/details/nc10]
device Multimedia controller (Audio device) [4|3|0]
  vendor 8086: Intel Corporation
  device 27d8: 82801G (ICH7 Family) High Definition Audio Controller

Change History (26)

comment:1 by axeld, 15 years ago

At least device 27d8 definitely works here (ICH-7). So your mileage might vary.

comment:2 by axeld, 15 years ago

Component: Audio & VideoDrivers/Audio/HDA
Owner: changed from nobody to korli

comment:3 by korli, 15 years ago

Description: modified (diff)

http://www.haikuware.com/details/compaq-6910p seems to state audio is working through internal speakers.

comment:4 by kvdman, 15 years ago

@korli, oh indeed you're right.

here's two more examples with the Intel HD audio:

http://www.haikuware.com/details/macbook-pro-early-2008 device Multimedia controller (Audio device) [4|3|0]

vendor 8086: Intel Corporation device 284b: 82801H (ICH8 Family) HD Audio Controller

http://www.haikuware.com/details/compaq-dx2400 device Multimedia controller (Audio device) [4|3|0]

vendor 8086: Intel Corporation device 293e: 82801I (ICH9 Family) HD Audio Controller

The user made all these reports and has access to a lot of hardware. I've recently added file uploads to the hardware database and indicated how to add syslogs. Perhaps they would be of further use.

comment:5 by jrash, 15 years ago

I double checked the 6910p today and I think the issue with that machine was a corrupt MP3 file, I probably forgot to set Binary mode in the ftp client before I downloaded the audio files. It was able to play an MP3 and WAV file fine. I also retested my MacBook Pro 4,1 but was unable to get the audio to work, I'll attach the syslog, listimage, and MediaPlayer output.

by jrash, 15 years ago

Attachment: MacBookPro41_syslog.txt added

MacBook Pro 4,1 Syslog (Booted from ISO)

by jrash, 15 years ago

Attachment: MacBookPro41_listimage.txt added

MacBook Pro 4,1 listimage output (Booted from ISO)

by jrash, 15 years ago

MediaPlayer playing the MP3 from the command line

comment:6 by jrash, 15 years ago

I also tried my MacBook Pro with the 33601 GCC2 nightly but still no audio.

comment:7 by korli, 14 years ago

Could you try again with the MacBookPro 4.1 please ? (hrev34355+)

comment:8 by jrash, 14 years ago

I played an mp3 and couldn't hear any sound using a hrev34523 gcc2 live CD

comment:9 by korli, 14 years ago

Could you try again with hrev34570 ?

comment:10 by kvdman, 14 years ago

I've tried with one of today's revisions.

I have a Macbook 2,1 (where the built-in keyboard and mouse don't work).

I tried an audio CD, *aiff file and *.mp3 in CD Player and Media Player. I could not produce any sound from the speakers or headphone, although the hardware did show up.

This book has the ICH7 multimedia chipset.

comment:11 by jrash, 14 years ago

Still no luck with hrev34586

comment:12 by korli, 14 years ago

Could you please try with a current revision ? Thanks

comment:13 by kvdman, 14 years ago

I've tried with hrev35693 on my MacBook. Still no sound. Tried playing an MP3 and Wav file through media player. Also tried with headphones; no sound.

comment:14 by korli, 14 years ago

Could you provide a syslog please ?

in reply to:  14 comment:15 by jrash, 14 years ago

Replying to korli:

Could you provide a syslog please ?

No sound for me either.

by jrash, 14 years ago

Attachment: syslog.macbookpro added

Mar 4 2010 syslog for hrev35752 (macbookpro4,1)

by kvdman, 14 years ago

Attachment: syslog added

Macbook 2,1

comment:16 by korli, 14 years ago

Sorry after looking both syslogs I don't have a clue about the lack of sound on macbooks.

comment:17 by kvdman, 14 years ago

I installed OSS, and deleted the HDA driver. No sound either, eventhough Intel HD Audio showed up as the driver under media preferences. Oddly, under 'channel' there were 4 different channels available. I tried all four (changing the channels and restarting the media server locked the machine), and it would not produce any sound.

I'm attaching the syslog with the OSS driver installed.

I did find this line in the syslog when the audio tried to start

hdaudio_mac_gpio

http://manuals.opensound.com/sources/hdaudio_gpio_handlers.c.html

by kvdman, 14 years ago

Attachment: syslog-oss added

comment:18 by kvdman, 14 years ago

Right after the driver gets loaded there's a USB error.

4938 KERN: iMac Sigmatel hdaudio initialization 4939 KERN: hdaudio_mac_GPIO_init() entered, afg=1, subdevice=0x106b2200, codec=0x83847680 4940 KERN: loaded driver /boot/home/config/add-ons/kernel/drivers/dev/oss_loader 4941 KERN: usb error uhci 0: error while setting device address

This is the laptop where the internal trackpad and keyboard don't work. I was told you had to enable USB polling in order to get the trackpad and mouse to work. I wonder if sound would also work in this case? I'm not sure how to enable this though.

comment:19 by kvdman, 14 years ago

Hello,

I thought this info may be useful? Perhaps you already know this:

http://www.haiku-os.org/community/forum/hardware_compatibility_wiki

The situation with Intel HDA is that it's a class standard, like VGA or USB storage.

So in theory you write one driver which implements the software side of the standard according to the documentation, and all conforming hardware will work. The Haiku driver roughly follows this approach, its probe function matches any PCI device which has the class information indicating it implements Intel HDA. Thus probably anyone with a modern Intel HDA device (which is most new laptops and desktops) gets this driver selected.

However, the HDA specification itself represents the codec (the bit that actually converts between PCM data and any form of sound output or input connector) as a separately programmed component. It is often the case that additional code is needed for a particular vendor's codec, or for some applications (ie specific models of computer or sound cards) of that codec. The Haiku code includes some examples of such additional code, covering some very popular devices, but it looks rather less than comprehensive. So for some users the outcome is likely that Haiku's driver seems to work, except that no sound comes out (it is playing, but to some unconnected pins deep inside their laptop, not to the speakers), or the volume controls don't work, or the speakers on their laptop always play sound even with headphones plugged in, that sort of thing.

The codecs have unique hardware identifiers similar to PCI devices, so that the OS need only load driver software for the codecs used in the installed device. e.g. ALSA identifies the codec in this laptop and loads a driver for 'snd-hda-codec-id:14f15051' a Conexant chip. So if Haiku actually had the new Windows 95 style driver model, this information could have been gathered too. But it might not be that helpful, at a certain point you do have to rely on user feedback on whether it really works. The same Conexant chip that works fine in this laptop might be wired up differently in another model, leaving the microphone non-functional by default.

comment:20 by diver, 13 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.