ESS Maestro3 no sound

[Pyun YongHyeon]

On Mon, Jul 11, 2005 at 05:03:18PM +0800, Muzaffar Ariff wrote:
 > After much searching on how to do the patching I think i got it right,
 > but it still does not solve my problem. Here is what I did:
 > 
 > 1. Tired to use the patch command and didn't work, because it can't
 > find line 1023  in the original maestro3.c (on my machine). I knew
 > about this but just gave it a try, hoping that I don't have to go the
 > long way :-)
 > 

Sorry. I had to say the patch was for CURRENT.

 > 2. Went to locate my sound driver modules and found it in
 > /usr/src/sys/modules/sound/driver/maestro3. Use to the make command to
 > see what it does.
 > *Q1: Is this the source code for the maestro3?
 > 

Yes.

 > 3. I then located and modified my maestro3.c file in
 > /usr/src/sys/dev/sound/pci/maestro3.c (before that made a copy of the
 > old one). Add and commenting out the stuff that you suggested.
 > 
 > 4. went back to ~/sound/driver/maestro3 and recompiled it again. It
 > compiled without a problem and I then loaded the module by using
 > #kldload snd_driver. Look up /dev/sndstat and it showed the same thing
 > as before:
 > 
 > Installed devices:
 > pcm0: <ESS Technology Maestro3> at io 0xd800 irq 5 kld snd_maestro3
 > (4p/1r/0v channels duplex default)
 > 
 > 5. Restarted my machine by having snd_maestro3_load="YES" loaded into
 > /boot/loader.conf
 > 
 > 6. Tried using xmms and the same problem happened, the xmms plays the
 > song but with no sound. Looked at /var/run/dmesg.boot to see what went
 > wrong and it output the same problem:
 > 
 > pci0: <bridge, PCI-unknown> at device 7.3 (no driver attached)
 > pcm0: <ESS Technology Maestro3> port 0xd800-0xd8ff mem
 > 0xf3ffe000-0xf3ffffff irq 5 at device 8.0 on pci0
 > pcm0: failed: rid 0x10 is ioport, requested 3
 > 

Hmm, I'm afraid you loaded old module again. Please let me know which
FreeBSD version you used. I can make a patch for the specific FreeBSD
version.

 > Q2: Now I might have compiled the code right but did I load the module
 > correctly? (i seem to be at the same conclusion, so I'm guessing it
 > didn't load).

According to the dmesg output, you loaded old module again.

-- 
Regards,
Pyun YongHyeon