From: Stephen Wille Padnos <stephen.willepadnos@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: 2.5.51 - Strange UP APIC / 8139too / USB issues
Date: Wed, 11 Dec 2002 15:58:46 -0500 [thread overview]
Message-ID: <3DF7A706.3020600@verizon.net> (raw)
Hi all.
I have a system with an Abit AT7 motherboard: VIA KT333, single Athlon,
512M RAM, onboard RTL8139 network, USB, USB2, 1394. *NO* onboard PS/2
keyboard or mouse ports.
Other: IDE HD, CD-RW, and DVD. Radeon 8500DV (will try getting that
working later :)
I have used the system successfully with 2.4, and have been trying to
get 2.5 to work. Until now, I haven't been able to get the USB keyboard
to work. It is initialized by the BIOS, and is usable by GRUB for
selecting boot images.
I finally found the culprit - "Local APIC Support on Uniprocessors" and
"IO-APIC on uniprocessors". If both items are enabled, the network
functions, but USB doesn't work. If not both are enabled (neither, or
Local APIC but not IO-APIC), then the USB system works, but the network
doesn't. :(
I am not using modules.
these are the only differences in .config:
multimedia linux-2.5.51 # diff -u working_network
working_usbkeyboard_config3
--- working_network 2002-12-11 15:43:31.000000000 -0500
+++ working_usbkeyboard_config3 2002-12-11 15:15:53.000000000 -0500
@@ -63,9 +63,8 @@
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
CONFIG_X86_UP_APIC=y
-CONFIG_X86_UP_IOAPIC=y
+# CONFIG_X86_UP_IOAPIC is not set
CONFIG_X86_LOCAL_APIC=y
-CONFIG_X86_IO_APIC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
I can send complete configs, lspci / lsusb / whatever else anyone wants.
Thanks
- Steve
next reply other threads:[~2002-12-11 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 20:58 Stephen Wille Padnos [this message]
2002-12-12 5:04 ` Stephen Wille Padnos
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=3DF7A706.3020600@verizon.net \
--to=stephen.willepadnos@verizon.net \
--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
Powered by JetHome