mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux@treblig.org
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 18:45:30 +0100	[thread overview]
Message-ID: <1064079929.22995.7.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <20030920163835.GA723@gallifrey>

On Sad, 2003-09-20 at 17:38, Dr. David Alan Gilbert wrote:
>   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

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.

> 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 ?

> 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.


  reply	other threads:[~2003-09-20 17:47 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 [this message]
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=1064079929.22995.7.camel@dhcp23.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@treblig.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®