Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002217]: Problems with ASUS A6Km
Date: Wed, 21 Jun 2006 22:48:52 +0200	[thread overview]
Message-ID: <f3e3f465fe6cc5d14079a2148ea577f6@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2217> 
======================================================================
Reported By:                mafm
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   2217
Category:                   PCI - intel8x0
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               
Kernel Version:             
======================================================================
Date Submitted:             06-18-2006 05:06 CEST
Last Modified:              06-21-2006 22:48 CEST
======================================================================
Summary:                    Problems with ASUS A6Km
Description: 
I have the same problems described here:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1898 , but I'm
opening a new report because I can't find a way to add a comment there.

I tried that asus-a6km-fix.diff but it doesn't work, in fact it doesn't
appear to have any effect at all.
======================================================================

----------------------------------------------------------------------
 mafm - 06-21-06 22:33 
----------------------------------------------------------------------
eNTi: are you using vanilla kernels, or from some distribution? Because all
this mess is quite strange, I never got it working. The combinations that
I tested are 2.6.16.8, 2.6.16.16 and 2.6.17-rc3 from Debian unstable, and
with 2.6.16.20 and 2.6.17 of vanilla kernels (the vanilla kernels with and
without the patch, I tested all combinations).

And which BIOS version are you using? I'm using the last one, from
A6KM210AS.zip, and I can't get the USB mouse working properly (some people
said that it was working with this one, but I never got this to work
either...), that's why I have to use "acpi=ht", to not have to unplug it
while the system boots. The original BIOS version shipped was 208.

Maybe the patches that the distributions apply to their kernels packages
or the BIOS make the difference, because the kernel versions are the same,
and apparently the hardware too...

----------------------------------------------------------------------
 eNTi - 06-21-06 22:48 
----------------------------------------------------------------------
i'm currently using 209A as bios. i never actually had many problems with
usb, even though i read a lot of people do. i also use a fixed dsdt from
acpi.sourceforge.net.

my kernel versions vary from stock arch linux builds, community built to
self made. a self made vanilla+beyond patchset kernel + the patch against
ac97_patch.c made my speakers work. i don't know what it is, that changed
it to non-working again. i'm currently on 2.6.17-ck1 (community built).
maybe i'll compile another kernel tomorrow or so. i'll tell you the
outcome, even though i doubt, that it will work.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
06-18-06 05:06 mafm           New Issue                                    
06-18-06 16:51 ryswic         Issue Monitored: ryswic                      
06-19-06 15:49 mafm           Issue Monitored: mafm                        
06-19-06 15:50 mafm           Note Added: 0010315                          
06-20-06 19:46 tiwai          Note Added: 0010345                          
06-20-06 20:16 mafm           Note Added: 0010354                          
06-21-06 21:37 eNTi           Note Added: 0010405                          
06-21-06 22:24 rlrevell       Note Added: 0010406                          
06-21-06 22:33 mafm           Note Added: 0010407                          
06-21-06 22:48 eNTi           Note Added: 0010408                          
======================================================================



All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642

             reply	other threads:[~2006-06-21 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 20:48 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-26 14:11 [ALSA - driver 0002217]: Problems with ASUS A6Km bugtrack
2006-06-25  9:32 bugtrack
2006-06-24 12:32 bugtrack
2006-06-24  8:26 bugtrack
2006-06-24  7:12 bugtrack
2006-06-23 14:23 bugtrack
2006-06-23 13:27 bugtrack
2006-06-21 22:10 bugtrack
2006-06-21 20:33 bugtrack
2006-06-21 20:24 bugtrack
2006-06-21 19:37 bugtrack
2006-06-20 18:16 bugtrack
2006-06-20 17:46 bugtrack
2006-06-19 13:50 bugtrack
2006-06-18  3:06 bugtrack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f3e3f465fe6cc5d14079a2148ea577f6@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox