From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.2[12] v VIA Rhine and VIA82x audio (working with a fight)
Date: Sat, 20 Sep 2003 20:05:16 +0100 [thread overview]
Message-ID: <20030920190516.GA796@gallifrey> (raw)
In-Reply-To: <1064079929.22995.7.camel@dhcp23.swansea.linux.org.uk>
* Alan Cox (alan@lxorguk.ukuu.org.uk) wrote:
>
> I've done some work on this for -ac. I thought 2.4.22 had enough stuff
> to deal with it (at least for the non ACPI case). VIA v-bus cares that
> both PCI_INTERRUPT_PIN and PCI_INTERRUPT_LINE are both set.
Well I do wonder whether it is just a very buggy BIOS etc not being helpful.
> > 2) Audio
> >
> > This was much more of a fight. The standard 2.4.21/22 via82xxx drivers
> > were very problematic. For example random hanging apps, buzzing when
> > an app had sound open but wasn't actually sending stuff, and a complete
> > failure to have any sound input.
>
> Do you have VIA 8233 or 8235 hardware ?
It isn't entirely obvious from the PCI dumps; I think its the 8235 from the
first entry for the device:
Bus 0, device 17, function 0:
ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge (rev 0).
Bus 0, device 17, function 1:
IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 6).
Master Capable. Latency=32.
I/O at 0xdc00 [0xdc0f].
Bus 0, device 17, function 5:
Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 80).
IRQ 5.
I/O at 0xe000 [0xe0ff].
ALSA seems to think its an 8235.
> > Except for playing CDs - which don't do anything - I suspect that might
> > be hardware, but am not sure.
>
> Check there is an analog cable fitted on the CD->Sound. Many new WinXP
> boxes are shipped with XP configured to digitally rip the CD data and no
> audio link cable. If so you need to pick a different CD player app or
> fit the cable.
Nod - I've heard it play a few times; so I'm wondering about a loose cable; although
my normal solution of these problems (buy a Soundblaster) has failed when I got the
machine home to find it had a sticker over the back of the case saying if I opened
it I'd break the warranty.
Dave
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2003-09-20 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 16:38 Dr. David Alan Gilbert
2003-09-20 17:45 ` Alan Cox
2003-09-20 19:05 ` Dr. David Alan Gilbert [this message]
2003-09-20 20:09 ` Jamie Lokier
2003-09-20 22:14 ` Alan Cox
2003-09-21 13:05 ` Stephan Maciej
2003-09-21 13:16 ` Alan Cox
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=20030920190516.GA796@gallifrey \
--to=gilbertd@treblig.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®