From: "Dr. David Alan Gilbert" <gilbertd@arentwildcardswonderfulforspammers.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.2[12] v VIA Rhine and VIA82x audio (working with a fight)
Date: Sat, 20 Sep 2003 17:38:35 +0100 [thread overview]
Message-ID: <20030920163835.GA723@gallifrey> (raw)
Hi,
I thought I'd report some problems (and solutions) I had getting
2.4.21 and 2.4.22 up on a Shuttle Motherboard using a VIA chipset.
1) Ether
The motherboard has onboard via-rhine ether; this wouldn't work
with the first kernels I tried. With 2.4.22 it needs the 'noapic'
option to work (2.4.22 wouldn't build for me single processor).
The errors are timeouts on transmit; the same happens on 2.4.21
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.
In the end I gave up and got ALSA 0.9.6; which seems to work fine for
generated audio and audio input.
Except for playing CDs - which don't do anything - I suspect that might
be hardware, but am not sure.
lspci and any other debug available on request.
Dave (linux @ treblig.org)
-----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 reply other threads:[~2003-09-20 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 16:38 Dr. David Alan Gilbert [this message]
2003-09-20 17:45 ` Alan Cox
2003-09-20 19:05 ` Dr. David Alan Gilbert
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=20030920163835.GA723@gallifrey \
--to=gilbertd@arentwildcardswonderfulforspammers.com \
--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®