I have a serious problem with a PowerMac G5/1.8GHz 7.2 (A1047).When booting 3.12 or 3.13 boot.img from SATA-HD (ide.device), all SATA-drives disappears after kernel takes over the system and bootprocess stops. I can boot flawless from 2nd.ide.device (CD-ROM or Compactflash-Card) to 3.12/3.13 - system (Ambient), but no ide.device can be seen (HD-Tools, Mounter, etc.). That has nothing to do with the filesystem on HD - because the whole ide.device is gone....
This problem do not occur in MOS 3.11 or earlier versions! (and, of course, MacOS X is also running perfect).
Please, can anybody with the same Powermac veryfy that?
This is a early PowerMAC G5 (Dual), 1,8GHz, identifies as 7.2. Should be a A1047. Firmware-version is 5.15f0. Firmware version is shown by typing dump-properties in Firmwareconsole.

I have the same G5 (1.8 dual 7,2 A1047) firmware version 5.1.2f2. I never had this problem.

Thank you. Helps me to search in other directions. I have a sneaking suspicion that it could be a timing problem in initializing pci.device (but I've no idea how to change that). When I installed MOS3.12 for the first time it boots mostly (sometimes 2 or 3 resets needed), but after a while more and more tries needed to boot, and now it boots never. During this time nothing has been changed on hardware, nor any new progs where installed. In OpenFirmware I can see the device and the HD (Kernel even boots from there).
What I'll try next, is to connect HD to second channel (unit 1) and to try a different HD, but I have not much hope that this will work, because I even cannot see the device under MOS! In case the HD has a fault and doesn't spin up quick enough: where dammed is the device going?
This G5 is not at my home, so next access to it is on weekend.
If anyone knows a source of newer firmware for this G5, please let me know (would be the last exit if nothing else works).

Could you try adding FD after boot.img in the bootinfo.txt? Just remember to issue 'HFSSetMacBoot boot:bootinfo.txt' in a shell before you reboot. It's a long shot, but maybe there's some conflict with Firewire...

I boot normaly from a Boot-Menue. I added FD like this:

I did this test-boot just manualy directly in OF:
boot cd1:,\boot.img BD=CF-Sys FD BM correct? If yes: does'nt change anything....pci.device does'nt appear.
I've installed MOS3.13 on a CF-Card which is connected to 2nd.pci.device. Therfore the CD1!

One interessting thing: I connected the HD to 2nd chanel (lower drive in drive-bay). And thats now astonishing: pci.device does not appear in boot-menue, but scoutNG finds it (only the device - no drives) !?!
Connecting HD to chanel 1, even scoutNG nothing finds....




[ Editiert durch Amigaharry2 20.02.2020 - 14:24 ]

A few minutes ago I tried to boot MOS3.13 - and, surprise, all drives appeared! But only till the next reboot comes - then it was the same crab: no pci-drives!! There seems really to be a serious timing-problem.

Try booting with ed=init. Either from OF prompt or by adding that to bootinfo.txt (remember to hfssetmacboot the file after saving).

Succsess! Tried several boots and PCI-HD always appears! Thank you!
What does that boot command?

Will change now installation on HD to MOS3.13......

That just enables a lot of logs at startup, effectively slowing your boot down a bit. Means the drives not showing is likely down to timings...

Ah, OK! So seems my drive is too slow and not recognized during boot. Now I understand, that nobody with the same G5-configuration has this problem, because they probably use quicker HDs.....
That's a usable solution for now, but is it planned to add a special command to slow down booting for such cases?

You can force a boot device using something like bd=dh0 in bootinfo.txt. That ought to make early startup wait for volume to come online. Mind it cannot be the volume label.

That has no effect - I did that in the past. Here my bootcommand in OF:

boot hd:,\boot.img ramdebug BD=SYS_OS

SYS_OS is the partition-name in HD-Toolbox. Including ed=init to that line works fine.

Maybe you can add a delay in OF, something like Code:.

There are possibilities for delay in OF, but that does'nt solve the problem. The delay is needed when MOS-kernel is taking over the system and initialising the devices. Such a delay can only be a special boot-command for the kernel (boot.img) itself. That is what the ed=init command does, though it was not designed for that purpose.....

What Brand and model is the Drive?
That would bei very intresting for all of us to avoid that Drive.

Takes a bit time to answer, because I don't have allways access to that maschine (it's not at my home). Hope one of the next weekends I can post it - if it is really the drive. Unfortunately I have no other drive (at moment) to test.

@Amigaharry2,

I can/could get from a friend, pc user, a 500 gb hard disk 3"1/2 for your powermac g5. It will certainly be rotating at 7200 rpm will have 16 32 or 64 mb of buffers. I will verify from the french poste or mondial relay for shipping cost. Tell me if you want it or if you can find one by yourself.

Brumiga

[ Edité par Brumiga 04.03.2020 - 08:22 ]

@Brumiga:

Thank you very much, but with above described ed=init - command are no more problems - it works with my HD now without problems. There is also no sigificant recognizable delay in booting - so I don't want to change a running system now....

Quote:

I suspected that it was a hardware problem with your system, either one of the drives, the cables, or a damaged connector to the motherboard. Glad you got it sorted out, but since this is the first time this problem has been reported on any MorphOS version or system that I can remember, I doubt that the MorphOS Dev. Team will slow down the boot process in future versions, just to fix the problem of a perhaps older Hard Drive that is not performing at 100% anymore.

Enjoy your G5 and MorphOS!

Thank you. MorphOS-Team knows about that issue (Jacadcaps and F.Mariak as well).
It was really a bit tricky to find out, what's the matter with this "special" G5. It is the only 7.2. I have 3 G5 - the others are newer generation and have newer Firmware too. You may have read in another discussion my issuse with USB-Sticks in Firmware on this G5: This version allows only max. 4GB storage-devices on USB-port. On the other hand it starts with only one CPU installed (which newer FW doesn't).
So I wasn't sure, if there are any combinations of reasons for that strange behviour, - and unfortunately this G5 is 100km anway from my home in my other office - so no way for quick actions (change HD with other G5, etc.). But now it works :)


[ Editiert durch Amigaharry2 04.03.2020 - 18:13 ]

Quote:

Now I had time to look for (not a really common one....):

It is a MAXTOR 7Y250MO

Remember: This behavior starts with 3.12. No problems before.





[ Editiert durch Amigaharry2 14.03.2020 - 16:33 ]

Quote:

I hope you are able to swap hard drives some time in the near future to find out if the problem is your hard drive, or the way MorphOS is starting up so fast, that is causing the issue. I'm betting that your hard drive is just not working 100%, and if you install a brand new drive, or SSD, you won't have the problem any more.