From: Vincent van de Camp <vncnt@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.x] Asus K8S-MX very unstable with Linux
Date: Tue, 03 May 2005 20:33:12 -0400 [thread overview]
Message-ID: <42781848.6080309@verizon.net> (raw)
In-Reply-To: <20050503181433.17423.qmail@web88004.mail.re2.yahoo.com>
I've had this board for a couple of months now. The only problem I have
is that the onboard NIC doesn't work with the sis900 module. And then
there's some messages in dmesg that have so far not caused me any problems:
SIS_IDE: probe of 0000:00:02.5 failed with error -1
Losing some ticks... checking if CPU frequency changed.
With some kernels (I'm sure about the one that came with ubuntu, but
also with at least one other x86_64 distribution) dhcpcd didn't work
with the tulip card that's in there now.
I've never had panics though. I'm running vanilla and gentoo 2.6.11 and
12-rc3 sources on this board.
Vincent
Shawn Starr wrote:
>Anyone have this board? I'm about to try 2.6.12-rc3 on
>it to see if DMA works (if not there is fix on
>kerneltrap), if the onboard NIC works, If the onboard
>SATA controller is detected or not.
>
>It's a very new board and I'm experiencing serious
>failures (3 different kernel panics from a RHEL4
>kernel alone).
>
>I'm curious to know if anyone else has had problems
>with this board.
>
>Thanks,
>
>Shawn.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
prev parent reply other threads:[~2005-05-04 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 18:14 [2.6.x] Asus K8S-MX very unstable with Linux Shawn Starr
2005-05-04 0:33 ` Vincent van de Camp [this message]
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=42781848.6080309@verizon.net \
--to=vncnt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.