Re: I can get no... sound
- To: debian-amd64@lists.debian.org
- Subject: Re: I can get no... sound
- From: Jonathan Kaye <jonathan.kaye@univie.ac.at>
- Date: Fri, 02 Sep 2005 19:28:50 +0200
- Message-id: <[🔎] dfa24q$53s$1@sea.gmane.org>
- References: <20050831143259.GO28551@csclub.uwaterloo.ca> <43163B9A.8040405@free.fr> <20050831160722.GV28551@csclub.uwaterloo.ca> <43164C6B.9050007@free.fr> <20050831164741.GY28551@csclub.uwaterloo.ca> <4316529F.90007@free.fr> <20050831170629.GZ28551@csclub.uwaterloo.ca> <43165846.5070206@free.fr> <20050831173719.GB28551@csclub.uwaterloo.ca> <43167605.3070108@free.fr> <20050831193756.GD28551@csclub.uwaterloo.ca> <43168EAF.8020805@free.fr> <[🔎] df9nks$22t$1@sea.gmane.org> <[🔎] 4318EE88.4060403@free.fr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yannick - Debian/Linux wrote:
> Jonathan Kaye a écrit :
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Yannick - Debian/Linux wrote:
>>
>>
>>
>>
>>>It seems not to find the chip (search with intel or nvidia doesn't give
>>>significant result)
>>>That's all i found... (but i'm not an expert)
>>>
>>>Yannick
>>>
>>>
>>Hi Yannick,
>>I ripped out the 2.6.8-11-amd64-k8 and reinstalled as 2.6.8-10-amd64-k8
>>and now alsa works perfectly. I just had to run alsaconf and the driver
>>installed straight away and there is sound. Perhaps there really is a
>>problem with 2.6.8-11-amd64-k8.
>>Cheers,
>>Jonathan
>>
>>
> As reported here :
> http://david.decotigny.free.fr/wiki/wakka.php?wiki=SargeAMD64
>
> vanilla kernel 2.6.12.4 without patch works too. (see
> http://david.decotigny.free.fr/wiki/upload/SargeAMD64/cfg-2.6.12.4 for
> how config this kernel for mother board asus A8N-E)
>
> Should we post a bug report ?
>
> Regards,
> Yannick
>
>>-----BEGIN PGP SIGNATURE-----
>>Version: GnuPG v1.4.1 (GNU/Linux)
>>
>>iD8DBQFDGGHP64+f0AXUe+4RAgx9AJ4m5fC5ZBsTamETnXVuHdz6/FFVqQCfc688
>>8AwVa99KmR1I2/TLZH2oqKM=
>>=7E7K
>>-----END PGP SIGNATURE-----
Yes, maybe we should. Can you try your system on 2.6.8-10-amd64-k8 and if it
works then it seems it's confirmed as a bug. What do you think?
Cheers,
Jonathan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDGIvX64+f0AXUe+4RAoGuAJ4xz+OBpKfajCjcMZ54+AzirY0oogCgkWFZ
XJj7lXLoFpkEWVQo9LnK5GA=
=noO+
-----END PGP SIGNATURE-----
Reply to: