From: Cory Bell <cory.bell@usa.net>
To: linux-kernel@vger.kernel.org
Cc: Joe Harrington <jh@oobleck.astro.cornell.edu>
Subject: Re: Via KT600 support?
Date: Wed, 12 Nov 2003 09:13:10 -0800 [thread overview]
Message-ID: <1068657190.4255.21.camel@homer.oit.pdx.edu> (raw)
Joe Harrington <jh@oobleck.astro.cornell.edu> wrote:
> I am having show-stopper difficulties getting Linux to run on my Asus
> A7V600 motherboard, which sports the Via KT600 chipset.
I also have an Asus A7V600. I'm unsure of the board revision, but I'm
running BIOS 1005.
> During install of Fedora Core 1, Fedora Core test3, Red Hat 9, and
> Debian 3.0r1, the install fails at a random point, generally during
> the non-interactive package loading phase. The most recent kernel
> with the problem is kernel-2.4.22-1.2115.nptl in the Fedora Core 1
> release. The problem is 100% reproducible.
I installed FC1 from CD with no problems.
> VC messages indicate problems in different programs each time.
> Generally the failure happens during package installation, but
> sometimes it happens earlier. After the first indication of a
> problem, one can generally still switch VCs, but eventually that stops
> working, too. Frequently, there are several programs indicating
> problems in the VC screens.
What are you seeing? Segfaults? Panics? Have you tried the memtest86
boot option (from the FC1 CDs)?
> The hardware:
>
> Asus A7V600 mobo (VIA KT600 chipset)
> AMD 2800+XP CPU
> 1536 MB DDR333 (3 sticks)
> IDE disks (250GB WD)
> IDE CD/DVD reader
I have:
Asus A7V600
Athlon XP 2600+ (Barton)
512MB DDR333 (PC2700)
Lite-On IDE DVD-ROM
Lite-On IDE CD-RW
Maxtor PATA 160GB
Chaintech Geforce 4 Ti4800 (AGP 8x)
No SATA
> Things I have tried:
> noapic nolapic acpi=off pci=noacpi allowcddma nodma
> in various combinations and individually. None worked. I also
> changed "APIC" to "PIC" in the BIOS, to no avail.
Mine works fine in APIC mode and with ACPI.
> I have tested and replaced the hardware extensively over the past
> several months of chasing this problem down. The problem is not
> damaged hardware. I suspect it is a problem with chipset support in
> the kernel. However, I have not been able to find a reliable source
> of information about the support status of various chipsets and
> motherboard features in the kernel.
Everything is supported fine except:
1) The OSS driver doesn't like the onboard AC-97 Audio - I installed
ALSA 0.9.8 with "options snd-via82xx dxs_support=2".
2) The sk98lin driver included in 2.4.22 is very old and doesn't
support the onboard "3Com 3C940" (actually a Syskonnect chip).
2.4.23-rc1 contains the latest driver, or you can patch 2.4.22.
ALSA: http://www.alsa-project.org/
Syskonnect Driver: http://www.syskonnect.com/syskonnect/support/driver/d0102_driver.html
One caveat: It appears that the kernel included with FC1 was not
compiled with the same version of gcc that is included in FC1. This
means you will need to compile your own kernel (or rebuild the FC1
kernel SRPM). I got an instant panic when trying to insert a
locally-compiled sk98lin module into the supplied kernel, so I just
downloaded the latest 2.4.23 test release.
-Cory
next reply other threads:[~2003-11-12 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 17:13 Cory Bell [this message]
2003-11-12 23:12 ` Joe Harrington
2003-11-13 8:02 ` Stefan Smietanowski
2003-11-13 8:16 ` Stefan Smietanowski
-- strict thread matches above, loose matches on Subject: below --
2003-11-11 19:21 Joe Harrington
2003-11-12 9:19 ` Maciej Soltysiak
2003-11-12 15:09 ` Joe Harrington
2003-11-12 23:00 ` Ruth Ivimey-Cook
2003-11-13 7:56 ` Stefan Smietanowski
2003-11-14 0:09 ` Kristian Lyngstøl
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=1068657190.4255.21.camel@homer.oit.pdx.edu \
--to=cory.bell@usa.net \
--cc=jh@oobleck.astro.cornell.edu \
--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®