From: Nicolas Mailhot <Nicolas.Mailhot@one2team.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: Re: 2.5.64p5 No USB support when APIC mode enabled
Date: 07 Mar 2003 15:11:56 +0100 [thread overview]
Message-ID: <1047046315.7172.8.camel@ulysse.olympe.o2t> (raw)
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
|Alan Cox wrote :
|
|You need at least 2.4.21-pre5-ac, or 2.5.64-ac (I just sent Linus the
|relevant changes) to use APIC on the VIA chipset systems. You also need
|a BIOS with correct tables, which can also be a little tricky to find
|in uniprocessordom
Well, if it's the same bug as
http://bugzilla.kernel.org/show_bug.cgi?id=15,
I'm certainly seeing it also with 2.5.64-ac1. Old 2.4.-ac kernels used to be
fine, I fear they have nowe been "fixed" to match 2.5.
Maybe you should be cc'd on this bug ?
|And Meino Christian Cramer replied :
|
| Therefore it seems that APIC is working with my VIA board without USB.
| But I cannot live without USB ... my mouse is USBish and X without a
| mouse is a little ... hmmm senseless.
Lucky you. I'm on a 100% hid input setup (mouse *and* keyboard), the
hardware is great on the kernels that support it, but is seems good
Linux support is not here yet:(.
Regards,
--
Nicolas Mailhot
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-03-07 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 14:11 Nicolas Mailhot [this message]
2003-03-07 15:19 ` 2.5.64p5 No USB support when APIC mode enabled Meino Christian Cramer
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 18:57 Nicolas Mailhot
2003-03-08 12:29 ` Meino Christian Cramer
2003-03-08 13:48 ` Nicolas Mailhot
2003-03-06 13:03 2.5.64 - xircom realport no workie well CaT
2003-03-06 13:29 ` Russell King
2003-03-07 7:44 ` 2.5.64p5 No USB support when APIC mode enabled Meino Christian Cramer
2003-03-07 12:52 ` Alan Cox
2003-03-07 13:37 ` Meino Christian Cramer
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=1047046315.7172.8.camel@ulysse.olympe.o2t \
--to=nicolas.mailhot@one2team.com \
--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;
as well as URLs for NNTP newsgroup(s).