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?

Ian

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

On Tue, 28 Mar 2006 17:40:07 +0100, 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?
Yes.
>
> Ian
>
Note: comment inline.

It seems like you are doing things right. These type of things can get
frustrating.

Did the second drive ever work or has this drive been recently
added? What size is the new drive?

Things to check:
1. Drive spins up.
2. Drive is jumpered correctly.
3. Drive cable is known good.
4. Drive is recognized by the motherboard/controller. BIOS set for LBA
mode.
5. Drive is recognized by the kernel at boot.

The next thing to do is swap drive positions temporarily. One way to do
this is to replace your existing hard disk (either hda or hdb) and boot
with a rescue cd.

--
Douglas Mayne

On 2006-03-28, Douglas Mayne <doug@slackware-3.localnet> wrote:
> On Tue, 28 Mar 2006 17:40:07 +0100, Ian Bell wrote:
>
>
> It seems like you are doing things right. These type of things can get
> frustrating.
>
> Did the second drive ever work or has this drive been recently
> added? What size is the new drive?
>
> Things to check:
> 1. Drive spins up.
> 2. Drive is jumpered correctly.
> 3. Drive cable is known good.
> 4. Drive is recognized by the motherboard/controller. BIOS set for LBA
> mode.
> 5. Drive is recognized by the kernel at boot.
>
> The next thing to do is swap drive positions temporarily. One way to do
> this is to replace your existing hard disk (either hda or hdb) and boot
> with a rescue cd.
>

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.

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.

I suspect the OP's problems is bios centered as well as mine, but can't seem
to track down the bios issue.

ken

Op Tue, 28 Mar 2006 17:40:07 +0100, schreef Ian Bell:

> 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?
>
> Ian

you can check the output of the following :

dmesg |grep -i ide
(to see if the kernel sees your ide controllers.)

dmesg |grep -i hd
(...if kernel sees drives)

/sbin/fdisk -l
(....and all partitions on all drives)

cashmir

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.

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).

Best regards, Paul
--
Paul Sherwin Consulting http://paulsherwin.co.uk

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?
Yes

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.

Robert
>
> Ian

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?

>I suspect the OP's problems is bios centered as well as mine, but can't seem
>to track down the bios issue.

Did you check for later BIOS on 'net?

Grant.
--
Memory fault -- brain fried

On 2006-03-29, Grant <bugsplatter@gmail.com> 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?

Yeah, I'll try a different cdrom....must have one or two extras in the
garage someplace, maybe I'll just buy one. I still have an old 5 1/2 inch
floppy drive, someplace. I still think they're going to make a comeback,
someday.

>
>>I suspect the OP's problems is bios centered as well as mine, but can't seem
>>to track down the bios issue.
>
> Did you check for later BIOS on 'net?

Not yet, that's next on my list...although there is some info on the slack
disks about cdroms hooked up to soundblaster cards...have to read the docs
with the slack disks.

ken

Douglas Mayne wrote:
> On Tue, 28 Mar 2006 17:40:07 +0100, 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?
> Yes.
> >
> > Ian
> >
> Note: comment inline.
>
> It seems like you are doing things right. These type of things can get
> frustrating.
>

Apologies for posting via google but my ISP news server is having
problems.

> Did the second drive ever work or has this drive been recently
> added? What size is the new drive?

It works fine. I connectd it in the hda postion and loaded a zenwalker
on it OK.

>
> Things to check:
> 1. Drive spins up.
> 2. Drive is jumpered correctly.
> 3. Drive cable is known good.
> 4. Drive is recognized by the motherboard/controller. BIOS set for LBA
> mode.

Yes to all the above.

> 5. Drive is recognized by the kernel at boot.
>

NO. That's the first indication that something is wrong.

> The next thing to do is swap drive positions temporarily. One way to do
> this is to replace your existing hard disk (either hda or hdb) and boot
> with a rescue cd.
>

See above.

The only thing I can think of is the plug and play OS setting in the
BIOS. I'll try changing that.
Thanks for the input.

Ian