From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [204.233.198.50] (helo=linserver.complex) by speech.braille.uwo.ca with esmtp (Exim 3.32 #1 (Debian)) id 16Rmrg-0003hg-00 for ; Fri, 18 Jan 2002 23:12:24 -0500 Received: (from gnowak1@localhost) by linserver.complex (8.11.4/8.10.2) id g0J4C1I00490 for speakup@braille.uwo.ca; Fri, 18 Jan 2002 22:12:01 -0600 Date: Fri, 18 Jan 2002 22:12:01 -0600 From: Gregory Nowak To: speakup@braille.uwo.ca Subject: Re: HD not detected Message-ID: <20020118221201.A486@uic.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from shauno@goanna.net.au on Sat, Jan 19, 2002 at 02:33:47PM +1100 Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.7 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: I think someone already mentioned this. Cable select will work only if you have the right ribon for it, and if your controller/drive support it. Greg On Sat, Jan 19, 2002 at 02:33:47PM +1100, Shaun Oliver wrote: > ok chuck first and foremost you must once you've put a new drive in the > machine, always check the bios to ensure that all drives are being > detected. > a good way to ensure that your drives are always seen is to set them all > to auto detect and possibly move the jumper to cable sellect. > the bios if it's recent enough should just pick up the fact that there's > a drive there and assign it according to it's ide channel. > hth > On Fri, 18 > Jan 2002, Charles Hallenbeck wrote: > > > I hope someone may have an explanation or a suggestion for this > > one: > > > > My friend has a Gateway machine with Windows 98 on a 12 GB disk > > which works fine. She wants to move on up to Linux, and purchased > > a second HD, a Maxtor 40 GB disk. She knows even less about > > hardware than I do, and together we proceeded to just put the > > disk in the machine and cable it up, without even looking at its > > jumpers. > > > > The machine now still boots fine into Windows, and Windows can > > see the second drive okay. However, Linux cannot see either the > > old drive or the new one. She is going to install Slackware 8.0 > > on her second disk, but when the installation boot disk and root > > disk are run, and we have the login invitation as root, neither > > fdisk nor cfdisk can 'open' any of the four HD devices, not even > > /dev/hda. > > > > Reviewing the boot messages for the ramdisk installation system, > > there is no mention of any HD either. It does find her CD drive > > on /dev/hdc, but no other /dev/hdx devices are found. > > > > Anybody have any idea where to look for this problem? > > > > Thanks - Chuck > > > > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>* > > Visit me at http://www.mhonline.net/~chuckh > > The Moon is Waxing Crescent (24% of Full) > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > -- > Shaun Oliver > > Marriage is a three ring circus: > engagement ring, wedding ring, and suffering. > -- Roger Price > > Email: shauno@goanna.net.au > Icq: 76958435 > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup