G5 support

[Michael Tuexen]

> On 19. Jun 2018, at 19:03, Rob Ballantyne <robballantyne3 at gmail.com> wrote:
> 
> These messages indicate the system is having trouble figuring out your disk.  It could be a 'bad' disk but I thought I would mention that I had similar problems (I didn't write them down so I can't absolutely confirm they are true) when I tried a new SATA3/flash drive on my system.  It appears that SATA3/flash is not supported currently (I would suspect no hardware support).
I'm using the drives that came with the systems... Just installed FreeBSD on it.

Best regards
Michael
> 
> Regards,
> Rob
> 
> On Tue, Jun 19, 2018 at 7:18 AM Michael Tuexen <Michael.Tuexen at macmic.franken.de> wrote:
> > On 19. Jun 2018, at 15:44, Nathan Whitehorn <nwhitehorn at freebsd.org> wrote:
> > 
> > If they don't boot, what errors do you get, if any? G5s on FreeBSD are usually boringly stable (mine are, certainly, currently running HEAD @ r333927).
> For example the messages end in (typed from screen):
> 
> (aprobe0:ata2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
> (aprobe0:ata2:0:0:0): CAM status: Command timeout
> (aprobe0:ata2:0:0:0): Retrying command, 0 more tries remain
> (aprobe0:ata2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
> (aprobe0:ata2:0:0:0): CAM status: Command timeout
> (aprobe0:ata2:0:0:0): Error 5, retries exhausted
> 
> which then is repeated a couple of times, and then the mountroot prompt shows up.
> 
> I installed FreeBSD on this disk, compiled a kernel, compiled a couple of
> ports...
> 
> Sometimes it boots... Any idea what could be wrong?
> 
> Best regards
> Michael
> > -Nathan
> > 
> > On 06/19/18 06:29, Michael Tuexen wrote:
> >> Dear all,
> >> 
> >> I have a couple of Dual core PowerMacs (PowerMac7,3) and they run Mac OS fine.
> >> Installing FreeBSD head of a couple of days ago also works fine, but the systems
> >> * don't boot reliably
> >> * once they boot they run fine for a while and then they shutdown
> >> Since they are running fine under Mac OS, I don't think there is a hardware
> >> error. Are these issues known? Anything I could try to improve the situation?
> >> 
> >> Best regards
> >> Michael
> >> _______________________________________________
> >> freebsd-ppc at freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"
> >> 
> > 
> > _______________________________________________
> > freebsd-ppc at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"
> 
> _______________________________________________
> freebsd-ppc at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"