[haiku-bugs] Re: [Haiku] #7680: No sound with HDA on intel N10 (NM10 Express chipset)

  • From: "6foot3" <trac@xxxxxxxxxxxx>
  • Date: Sat, 11 Jun 2011 09:36:40 -0000

#7680: No sound with HDA on intel N10 (NM10 Express chipset)
---------------------------------+----------------------------
   Reporter:  6foot3             |      Owner:  korli
       Type:  bug                |     Status:  new
   Priority:  normal             |  Milestone:  R1
  Component:  Drivers/Audio/HDA  |    Version:  R1/Development
 Resolution:                     |   Keywords:
 Blocked By:                     |   Blocking:
Has a Patch:  0                  |   Platform:  x86
---------------------------------+----------------------------

Comment (by 6foot3):

 Not #4492, no sound from either headphones or internal speakers and
 different chipset (Intel 82801G). Not #4635, again Intel 82801G. #4755?
 Maybe but, the creator of that ticket did not supply a listdev output so,
 without digging through the syslogs, we really don't know what hardware
 haiku thinks is there. The last comment as of 2011-06-11 seems to
 summarize the problem/challenge.[[BR]]

 Not #6213 as this relates to one of the desktop versions of the
 cpu/chipset family. I've used both an earlier version (Intel D945GCLF2)
 and a more recent version (Intel D525MW) of the same cpu/chipset with
 absolutely no issues apart from an intel_extreme driver issue that was
 fixed some time ago. I seriously doubt that this ticket is still valid. I
 last used my D525MW motherboard based system yesterday with r42061 and
 AFAIK the only difference between the D510 and the D525 is the speed, 1.66
 vs 1.80 GHz.[[BR]]

 #7144 is pretty much an exact match but, the last comment suggests using
 the opensound optional package as a workaround.[[BR]]

 I guess this ticket should be marked as a duplicate of #7144.

 I also have a full size latop which was the subject of ticket #5866 that
 also has this problem. That ticket had to do with IO-APIC issues that have
 now been solved. Would IO-APIC issus affect the ability of the HDA driver
 to interact with the hardware? If so, maybe it's time to revisit the HDA
 driver since the amount of systems affected by this issue is potentially
 huge.


 In terms of different hadware affected by the same bug, is it useful for
 the devs to have listdev outputs and syslogs for more than one computer
 that experiences a similar bug? I'm getting a new charger for my laptop
 today and want to know if the listdev output and the latest syslog would
 be of use to anyone?

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/7680#comment:2>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: