This is a discussion on Second IDE controller within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Steven Saner wrote: > Ian Bell wrote: >> I have an old Celeron PC based on an Intel 815 ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Steven Saner wrote: > Ian Bell wrote: >> I have an old Celeron PC based on an Intel 815 chipset on an ATX >> motherboard. It has 2 IDE controller connectors. The primary one has a >> hard drive and CD writer connected to it. They work fine and I can dual >> boot salck and win98 from the hard drive and see the CD writer. The >> second IDE controller has another hard drive on it. The controller is >> enabled in bios and bios can see the drive. However, neither slack nor >> win98 can see this drive. What am I doing wrong? >> >> The primary hard drive is hda and the cdwriter is hdb. Presumably the >> secondary pair should be hdc and hdd respectively? > > > What kind of partitions are on this drive? What happens if you do fdisk > /dev/hdc from Linux? > > Steve It had a single FAT partition. It works find when swapped into the hda slot so I don't think it is the drive. Ian |
| |||
| No_One wrote: > Copied all the slack files to a second hard drive, installed the second > hd, mounted it manually, but setup insists it's not there though it's > listed when I df. > Strange thing is, I CAN see the drive with setup but not with windows or linux. Ian |
| |||
| Grant wrote: > On Tue, 28 Mar 2006 20:18:30 GMT, No_One <no_one@no_where.com> wrote: > >>Similar problems here for the last few days, as I read the OP's >>comments..my cdrom can boot the install disk, but cannot see the cdrom >>when install time comes. > > Old Dell? Or Samsung CDROM? I had same issue, fixed by replacing CDROM, > to do with faulty linux IDE drivers and DMA settings, dreary. Seems there > are lots of old pII Celeron's coming out s/h? > No it's a brand new Sony DVD/CDRW. Ian |
| |||
| Paul Sherwin wrote: > On Tue, 28 Mar 2006 17:40:07 +0100, Ian Bell <ruffrecords@yahoo.com> > wrote: > >>I have an old Celeron PC based on an Intel 815 chipset on an ATX >>motherboard. It has 2 IDE controller connectors. The primary one has a >>hard drive and CD writer connected to it. They work fine and I can dual >>boot salck and win98 from the hard drive and see the CD writer. The second >>IDE controller has another hard drive on it. The controller is enabled in >>bios and bios can see the drive. However, neither slack nor win98 can see >>this drive. What am I doing wrong? >> >>The primary hard drive is hda and the cdwriter is hdb. Presumably the >>secondary pair should be hdc and hdd respectively? > > Exactly. > > Can the BIOS see the devices on the secondary interface? If not, > you've connected them incorrectly. > BIOS sees both drives and CDRW. > The kernel should probe both IDE interfaces while booting and report > what is connected. What does it say? (You can review the messages with > the 'dmseg' command once the system has booted). > It just reports hda and hdb, nothing else. Ian |
| |||
| Robert Harris wrote: > > Look for hdc and hdd in the output of dmesg ("dmesg | grep hd[cd]"). If > you don't see them, there is probably something wrong with the way your > drive is connected or configured. If you do, look at the disk partition > table with fdisk - win98 only sees FAT partitions while Linux only sees > the partitions it understands. > I tried fdisk /dev/hdc and hdd but I get no such device error. Ian |
| ||||
| Ian Bell wrote: > Robert Harris wrote: >> >> Look for hdc and hdd in the output of dmesg ("dmesg | grep hd[cd]"). If >> you don't see them, there is probably something wrong with the way your >> drive is connected or configured. If you do, look at the disk partition >> table with fdisk - win98 only sees FAT partitions while Linux only sees >> the partitions it understands. >> > > I tried fdisk /dev/hdc and hdd but I get no such device error. > > Ian Problem solved. It was a BIOS thing. Although the device was detected and listed in bios when I selected the drive another screen pops up which said it thought it was a CDROM. Changed this to Auto and everything is OK now. Thanks for everyone's input on this. Ian |