Bug 232899

Can you please check packages alsa-lib-1.0.14, alsa-utils-1.0.14 from devel or
from my test page? (http://people.redhat.com/stransky/alsa/)

After updating alsa-lib and alsa-utils to 1.0.14-0.1.rc1.fc6, the problem remains
even worse (no sound on the let headphone)

I've asked you to update to rc3/rc2, 1.0.14-0.1.rc1.fc6 are packages from fc6.

With
 alsa-lib-1.0.14-0.1.rc3
 alsa-utils-1.0.14-0.1.rc2
 kernel 2.6.20-1.2937.fc6
the problem remains, there is not sound even on the left headphone

Please note that
 alsa-lib-1.0.14-0.1.rc3
 alsa-utils-1.0.14-0.1.rc2
 kernel 2.6.20-1.2937.fc6
solve a  similar problem (bug #231414 ) on a chip ATI SB450 but
the Acer Ferrari-1000 has an ATI RS485 

Can you please attach /root/scsconfig.log? (it's generated by
system-config-soundcard, on the "System" page)

Created attachment 154899 [details]
scsconfig.log file

You have installed user-space packages alsa-lib-1.0.14-0.1.rc3,
alsa-lib-1.0.14-0.1.rc1.fc6 and kernel drivers 1.0.14rc1.

So please remove your user-space packages, check my page
(http://people.redhat.com/stransky/alsa/) and install the rc4 ones (kernel,
alsa-lib and alsa-utils packages).

Created attachment 155443 [details]
new scsconfig.log file after the changes

After doing that, the problem remains.
Please find attached the new scsconfig.log file
(Note that although I have installed the alsa-driver-1.0.14-60_rc4.fc6 ,
alsa-driver-devel-1.0.14-60_rc4.fc6 and
alsa-kmdl-2.6.20-1.2948.fc6-1.0.10-60_rc4.fc6 it appears the alsa-driver
1.0.14rc3 in the scsconfig.log)

yep, you still use the 1.0.14rc3 driver.
please try to compile it by yourself, from tarball (but I'm not sure if it
really helps you)

(In reply to comment #10)
> yep, you still use the 1.0.14rc3 driver.
> please try to compile it by yourself, from tarball (but I'm not sure if it
> really helps you)

I have compiled from tarball the alsa-driver-1.0.14rc4, and installed 
with make , make install but the 1.0.14rc3 driver is there and it appears again
in he scsconfig.log ¿what is wrong?.

did you reboot your box?

(In reply to comment #12)
> did you reboot your box?
yes, several times. 

Created attachment 155466 [details]
new scsconfig.log  (with the driver 1.0.14rc4)

After the compilation of
alsa-driver-1.0.14-60_rc4.fc6 , make install puts the drivers in
/lib/modules/2.6.20-1.2948.fc6/kernel/sound
whereas the system loks at /lib/modules/2.6.20-1.2948.fc6/updates/sound
So I copied /lib/modules/2.6.20-1.2948.fc6/kernel/sound to
/lib/modules/2.6.20-1.2948.fc6/updates/sound 
and now system-config-soundcard recognizes the 1.0.14rcd drivers.
But there is not sound. I send you the new scsconfig.log file

Can you please check the latest drivers? (1.0.14 final, from
http://people.redhat.com/stransky/alsa/)

Created attachment 157992 [details]
new scsconfig.lof file with the asla-driver-1.0.14 and alsa-lib-1.0.14a-0.6

No sound again. Please find attached the new scsconfig.log file.

I suspect that all is due to a problem with the 64bit kernel. In fact
there is some one who claims that has not problems with the sound on an Acer
Ferrari 1000 with ubuntu-7.04 and that has installed the official WindowsXP
Ferrari 1000  wlan broadcom driver using ndiswrapper
(rbak.demon.nl/ubuntu/acer_ferrari.php). But when I try to install the same
driver I get a message:

--kernel is 64 bit, but Windows driver is not 64-bit.
-- couldn't load driver bcmwl5 

So, surely he (she) has installed the 32 bit kernel.

hm. I'll move it to kernel because it looks like a regression there. It would be
great if you can confirm that the old kernel still works fine for you.

Latest kernel is now 2962, was that tested?

No, but:
1) Ruurt Bak (see rbak.demon.nl/ubuntu/acer_ferrari.php) has not problems with
the sound but he told me that he is using  the ubuntu 32-bit version.
2) Another user told me that he is using his own compilation of the 2.6.20-1.2952   
64-bit kernel and that has sound
So probably the problem is on the Fedora rpm that has mis configured somthing ?

(In reply to comment #20)
> No, but:
> 1) Ruurt Bak (see rbak.demon.nl/ubuntu/acer_ferrari.php) has not problems with
> the sound but he told me that he is using  the ubuntu 32-bit version.
> 2) Another user told me that he is using his own compilation of the
2.6.20-1.2952   
> 64-bit kernel and that has sound

Was that one tested? Major Intel hda fixes went into that version...

With the 2.6.20-1.2962 fedora kernel, things are even worse.

I have re installed the alsa-1.0.14 drivers (since the redhat kernel comes with
the oldest .rc1 version). Please see attached the new scsconfig.log file.
 
Now I can't use the camera even after recompiling the gspcav1 drivers and the
spcaview fron Michael Xhaard which worked normally  with the 2952 kernel. 
By the way, there is another problem with the wifi because the windows driver
for the amd_64 uses more memory than that of the fedora kernel so ndiswrapper
gets out of memory (but as I have seen on the net this is a general problem with
fedora an the windows drivers that need more than 4M).

Created attachment 158330 [details]
new scsconfig.log with the 2962 kernel and 0.14 alsa-drivers

Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.