From: David du Colombier <0intro@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] boot failed
Date: Sat, 27 Aug 2011 14:44:50 +0200 [thread overview]
Message-ID: <20110827144450.7a16915c@zinc.9fans.fr> (raw)
In-Reply-To: <4E58D9EA.6080907@o2.pl>
The result of "lspci -n" would probably be more instructive since
"lspci" doesn't display the VID/DID.
> 00:07.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
However, as far I know, this device is 0x1106/0x0571, which should
be already supported by the sdata driver.
So, I don't understand why it doesn't work in your case.
--
David du Colombier
next prev parent reply other threads:[~2011-08-27 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 13:40 bobas
2011-08-25 14:08 ` erik quanstrom
2011-08-26 14:02 ` bobas
2011-08-26 14:07 ` erik quanstrom
2011-08-26 17:36 ` bobas
2011-08-26 17:48 ` erik quanstrom
2011-08-27 11:50 ` bobas
2011-08-27 12:44 ` David du Colombier [this message]
2011-08-27 17:03 ` bobas
2011-08-28 11:43 ` Bruce Ellis
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=20110827144450.7a16915c@zinc.9fans.fr \
--to=0intro@gmail.com \
--cc=9fans@9fans.net \
/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).