[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#272443: marked as done (Sarge installer report - SATA drives not detected on Sis180 chip, Asus p4s800d-e board)

Your message dated Wed, 08 Sep 2010 03:57:39 +0000
with message-id <E1OtBn1-000429-IP@ravel.debian.org>
and subject line Closing old installation report #272443
has caused the Debian Bug report #272443,
regarding Sarge installer report - SATA drives not detected on Sis180 chip, Asus p4s800d-e board
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

272443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272443
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 2-Sep-2004 sarge snapshot (dvd)


I'm running the installer off of a dvd 'testing' image from 2-Sep-2004 on a machine with an Asus P4S800D-E deluxe board and two SATA Western Digital drives connected to the board via the Sis180 chip's sata ports. Processor is an Intel 3.2Ghz.

During both a default installation and a linux26 installation, the problem occurs at the partitioning stage. Manual partitioning is the only option because no drives or partitions are detected. The drives are known to be functional since an existing commercial OS exists on one of the drives and is bootable.

I had believed that the libata driver supported the Sis chip for sata in the 2.6.7 kernel, but a linux26 install exhibits the same behavior.

Hope this helps,
James Todd

--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
- it was reported with a pre-lenny version of Debian
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful

The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---

Reply to: