[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#298334: marked as done (kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX))



Your message dated Sat, 25 Jul 2009 11:13:38 +0200
with message-id <20090725091338.GA26629@galadriel.inutil.org>
and subject line Re: kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX)
has caused the Debian Bug report #298334,
regarding kernel-image-2.6.10-1-686: volume being listed as an input not an output for CS4299 rev6 (I440MX)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
298334: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298334
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: kernel-image-2.6.10-1-686
Version: 2.6.10-4
Severity: normal


like the usb-audio device i have (a PDT cyberphone with mono
capabilities), my Intel I440MX Cirrus Logic CS4299 (rev 6) has started
being reported with volume as an INPUT device not an OUTPUT.

the I440MX was not until about 2.6.9 detected as a CS4299.

in 2.6.9 it was intermittently detected and reported by userspace
programs as either an I440MX or a CS4299.

when reported as an I440X, the volume was successfully shown on
the output.

after running shockwave flash and some jumbled garbage coming
from the audio (my browser is running the flash plugin at 100%
CPU on this 800Mhz machine and so hasn't got time to feed things
like audio) resulting in ear-howling noise followed by silence,
re-running kmix would definitely show up the device (now silent)
as a CS4299.

prior to shockwave messing things up, the device would show up as
an I440MX.

when running 2.6.10, it's always absolutely 100% guaranteed to
show up as a CS4299 - again, 100% guaranteed to have the volume
as an input.

l.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux highfield 2.6.10-1-686 #1 Tue Jan 18 04:34:19 EST 2005 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages kernel-image-2.6.10-1-686 depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  fileutils                     5.2.1-2    The GNU file management utilities 
ii  initrd-tools                  0.1.77     tools to create initrd image for p
ii  module-init-tools             3.0-pre9-1 tools for managing Linux kernel mo

-- no debconf information



--- End Message ---
--- Begin Message ---
On Wed, Dec 24, 2008 at 04:22:02PM +0100, Moritz Muehlenhoff wrote:
> reassign 298334 linux-2.6
> thanks
> 
> On Sun, Mar 06, 2005 at 08:20:41PM +0000, Luke Kenneth Casson Leighton wrote:
> > Package: kernel-image-2.6.10-1-686
> > Version: 2.6.10-4
> > Severity: normal
> > 
> > 
> > like the usb-audio device i have (a PDT cyberphone with mono
> > capabilities), my Intel I440MX Cirrus Logic CS4299 (rev 6) has started
> > being reported with volume as an INPUT device not an OUTPUT.
> > 
> > the I440MX was not until about 2.6.9 detected as a CS4299.
> > 
> > in 2.6.9 it was intermittently detected and reported by userspace
> > programs as either an I440MX or a CS4299.
> > 
> > when reported as an I440X, the volume was successfully shown on
> > the output.
> > 
> > after running shockwave flash and some jumbled garbage coming
> > from the audio (my browser is running the flash plugin at 100%
> > CPU on this 800Mhz machine and so hasn't got time to feed things
> > like audio) resulting in ear-howling noise followed by silence,
> > re-running kmix would definitely show up the device (now silent)
> > as a CS4299.
> > 
> > prior to shockwave messing things up, the device would show up as
> > an I440MX.
> > 
> > when running 2.6.10, it's always absolutely 100% guaranteed to
> > show up as a CS4299 - again, 100% guaranteed to have the volume
> > as an input.
> 
> Does this error still occur with more recent kernel versions?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz


--- End Message ---

Reply to: