OK, I am not giving up. SORRY!

OK, I am not giving up. SORRY!

Post by Christian Bonann » Wed, 15 Mar 2000 04:00:00



The problem seems to be that BootX starts looking for hda and does not
find it. And gives a DMA timeout. I put in the kernal args hda=none
hdb=none and bootx gives up and says that the loader can not find the
root. The root should be at hdd7. the second hard drive on the ata
chain.

More info:

Mac OS 9
Blue and White G3
Two internal ATA drives - I want to install linux on the slave

Bootx version: 1.2.b3
Drive Setup version: 1.8.1

Once I figure this out I will make detailed instructions and post them
on a web page.

I did find this tip:

If you have a Rev.2 G3 and you are installing on or using only a SCSI
drive (not the internal ATA drive) and you don't need access to your ATA
drive from Linux, you should be able to add the "hda=none" and
"hdb=none" settings in the Kernel Arguments to get the machine to boot
properly. You may have to adjust the arguments to  agree with your hard
drive's device names, such as "hdc" or "hdd". You can also apply this to
multiple drives by using "hda=none hdb=none" (adjusting for your drive
names).

  * This tip is no longer needed now that properly compiled kernels for
the Rev.2 machines have been posted and verified. It has been left here
for reference purposes in  case a newer kernel or machine has this
problem.

 
 
 

OK, I am not giving up. SORRY!

Post by Michael Schmit » Wed, 15 Mar 2000 04:00:00



> The problem seems to be that BootX starts looking for hda and does not
> find it. And gives a DMA timeout. I put in the kernal args hda=none
> hdb=none and bootx gives up and says that the loader can not find the
> root. The root should be at hdd7. the second hard drive on the ata
> chain.

OK, some refinement of nomenclature first:

BootX is a Linux boot loader that itself loads as MacOS INIT, displays a
nice screen with buttons and options, lets you pick a kernel to boot,
passes arguments to that kernel when loading it. I assume all of this
above works as advertised for you.

After BootX loads and starts the kernel, it's Linux proper that is
running. BootX only prints a few text messages on the black. The kernel
then clears the screen, displays a penguin logo and prints a bunch of
text messages. Still assuming this works OK in your case?

After a screenful of messages, the IDE driver probes for drives and
prints what it finds. Could you post a copy of these messages here?

The one thing that's odd about your setup is the fact that only hda and
hdd are present. What are the other IDE devices used for? CD-ROM or Zip?
Try inserting a disk there...

And try adding hdc=none as well, maybe that takes you straigt to hdd on
device probe.

        Michael

 
 
 

OK, I am not giving up. SORRY!

Post by Tim R » Fri, 17 Mar 2000 04:00:00



> The problem seems to be that BootX starts looking for hda and does not
> find it. And gives a DMA timeout. I put in the kernal args hda=none
> hdb=none and bootx gives up and says that the loader can not find the
> root. The root should be at hdd7. the second hard drive on the ata
> chain.

so did you add the arg root=/dev/hdd7? if its looking for soemthing on hda
or hdb, then of course it gives up when they're both set to none.
Quote:

> More info:

> Mac OS 9
> Blue and White G3
> Two internal ATA drives - I want to install linux on the slave

> Bootx version: 1.2.b3
> Drive Setup version: 1.8.1

> Once I figure this out I will make detailed instructions and post them
> on a web page.

> I did find this tip:

> If you have a Rev.2 G3 and you are installing on or using only a SCSI
> drive (not the internal ATA drive) and you don't need access to your ATA
> drive from Linux, you should be able to add the "hda=none" and
> "hdb=none" settings in the Kernel Arguments to get the machine to boot
> properly. You may have to adjust the arguments to  agree with your hard
> drive's device names, such as "hdc" or "hdd". You can also apply this to
> multiple drives by using "hda=none hdb=none" (adjusting for your drive
> names).

>   * This tip is no longer needed now that properly compiled kernels for
> the Rev.2 machines have been posted and verified. It has been left here
> for reference purposes in  case a newer kernel or machine has this
> problem.

 
 
 

1. Ok, I am converted, give it to me !!!

I am thinking of buying a Dell Inspiron laptop and sticking Redhat Linux 7.1
on it. Just to save myself download costs, I am also thinking of getting one
of the standard Redhat boxes with the works inside and downoading any recent
updates from various sites. I can pick up copies at PC Bookshop here in
London (see http://www.pcbooks.co.uk/ )(or Amazon UK).

(i) I get confused with all the variations of boxes that RedHat do. I don't
want to miss out on using the C/C++ compiler, at this stage recompiling
Linux is not that important (maybe later). What do I want?

(ii) Is it worth trying Suse, Debian etc and why?

(iii) I am slightly worried that one of Dells laptop devices (like say CD-RW
drive) won't be catered for. Any comments?

Thanks

Stephen Howe

2. Wireless Woe - Please Help

3. Printcap OK, Postscript OK, together NOT OK - HELP!

4. Graphic res different for root & user!

5. Q: Why am I getting "Sorry - PPP is not available on this system"?????

6. wu-ftp log

7. Modem gives "Sorry, modem is not responding"

8. unable to load iptables module

9. Shape Ups,Men's Shape Ups,Men's Skechers Shape Ups - new styles!

10. Modem Problems: dial-out is ok/dial-in is not ok (Solaris 2.6)

11. Ping ok, netscape, gftp, lynx not ok

12. AWE32 NOT DETECTED PNP OK PNP OK