Date: Sat, 13 Oct 2018 16:18:48 -0700 From: Cameron Berkenpas <cam@neo-zeon.de> To: freebsd-ppc@freebsd.org Subject: Re: FreeBSD 12.0-ALPHA4 fails to boot on POWER9/KVM Message-ID: <341c38b5-d319-226c-946e-ecdbeaae1d0c@neo-zeon.de> In-Reply-To: <557519fc-a1f7-4a78-ee77-eae6f96d3a5e@freebsd.org> References: <5d84652d-8b54-19f9-1396-e7c9acbe6c03@neo-zeon.de> <CAHSQbTAgow0yESJo-oV83Oq9ePzwoOL_viUxNirYmeOXy_2zmg@mail.gmail.com> <a9aed989-9ea0-4e34-0619-7d54ddc28ea6@neo-zeon.de> <5f44c6d6-7eec-6732-6fef-123e7e0d3292@freebsd.org> <E610CDE0-7BEE-4E79-BB15-9FB023690BA5@macmic.franken.de> <ff249f1e-9c2d-013a-1a37-cc79a261fbac@freebsd.org> <cd6efedd-627c-1758-1b01-cd1547180e8b@neo-zeon.de> <2b4455f4-37f6-5645-dcba-2cc41c845ae8@neo-zeon.de> <0a970b75-160a-e40e-b360-1b73a753f701@freebsd.org> <c6fb42ef-fba3-9a79-1356-759900cb24d0@blastwave.org> <E23ABDA5-40EA-428C-BF3F-4199096DF7A8@yahoo.com> <573eb381-35f0-5523-3d6a-77a01174bdc8@blastwave.org> <bee737ef-746f-9b3e-4819-6e9011364a4d@neo-zeon.de> <557519fc-a1f7-4a78-ee77-eae6f96d3a5e@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Whoops, that would be: make buildworld buildkernel TARGET=powerpc TARGET_ARCH=powerpc64 make cdrom TARGET=powerpc TARGET_ARCH=powerpc64 Good catch. Turns out that's the bootloader of my install that no longer boots... So you can either manually select to boot from the cd-rom in the firmware, or here's how to boot from the cd-rom via kvm/qemu: qemu-system-ppc64 -enable-kvm -m 2048 -nographic -vga none -boot order=d -cdrom bootonly.iso -drive file=/var/lib/libvirt/images/freebsd-ppc.qcow2,format=qcow2 -mem-prealloc -mem-path /dev/hugepages -smp 2 Then after installing, of course remove the '-boot' option and its argument to boot from the disk. Interestingly, disc1.iso still won't boot: Trying to load: from: /vdevice/v-scsi@71000003/disk@8200000000000000 ... failed to load CHRP boot loader.failed to load CHRP boot loader. E3404: Not a bootable device! There's probably something wrong with my disc1.iso. FreeBSD-12.0-ALPHA9-powerpc-powerpc64-20181009-r339271-disc1.iso boots successfully in spite of the "NOT FOUND" errors. My earlier attempts with bootonly.iso failed due to some foolishness on my part. The above examples will work. However, during the install, I'm getting a checksum error with base.txz. Looking at the MANIFEST, it seems correct. I used the ALPHA9 ISO and was able to install successfully. Anyway, just remember to use the MBR partition scheme or your install won't boot. I still can't get FreeBSD to boot through virt-manager/libvirt, but I'm still trying to see if I get that working too. -Cameron On 10/13/2018 01:08 PM, Nathan Whitehorn wrote: > > On 10/13/18 12:53 PM, Cameron Berkenpas wrote: >> Hello, >> >> Finally had some time to spin up my own ISO from 12-CURRENT. >> Unfortunately, it still fails. Looks like there's no real change from >> before. >> >> # This is how I built the cdrom image: >> make cdrom TARGET=powerpc TARGET_ARCH=powerpc64 >> make cdrom TARGET=powerpc TARGET_ARCH=powerpc64 >> >> I tried this with revision r339340. > [...] > >>>> FreeBSD/powerpc Open Firmware boot block >> Boot path: /pci@800000020000000/scsi@7/disk@100000100000000 >> Boot loader: /boot/loader >> Boot volume: /pci@800000020000000/scsi@7/disk@100000100000000:2 >> Consoles: Open Firmware console >> >> FreeBSD/powerpc64 Open Firmware loader, Revision 0.1 >> (Sun Aug 19 13:30:54 PDT 2018 root@freebsd-ppc) > > I think you aren't using the loader you think you are using judging by > the date above. > -Nathan > >> Memory: 2097152KB >> Booted from: /pci@800000020000000/scsi@7/disk@100000100000000 >> >> >> block-size NOT FOUND >> #blocks NOT FOUND| >> block-size NOT FOUND >> #blocks NOT FOUND\ >> block-size NOT FOUND >> #blocks NOT FOUND >> >> ( 700 ) Program Exception [ 0 ] >> >> >> R0 .. R7 R8 .. R15 R16 .. R23 R24 .. R31 >> 0000000000000040 000000000345cdc4 ffffffffffffffff 0000000002c50468 >> 0000000002c548c0 0000000000000000 0000000002c56ba0 0000000002c513a0 >> 0000000000000000 0000000002c67780 0000000002c56b98 0000000002c51c18 >> 000000000345d8f0 0000000002c67300 0000000002c62200 000000000345d8f0 >> 0000000002c67340 0000000020000048 000000000040e78e 0000000000000000 >> 0000000000000000 0000000000000000 0000000001802118 0000000000000000 >> 0000000000000040 0000000002c4baec 0000000002c71980 0000000000000000 >> 0000000000000040 000000007fffffff 0000000002c5bb84 000000000345d8f0 >> >> CR / XER LR / CTR SRR0 / SRR1 DAR / DSISR >> 80000044 0000000002c02938 0000000000000000 0000000000000000 >> 0000000020040000 0000000000000000 0000000000083000 00000000 >> >> >> e > >> >> Hope this is helpful! >> >> On 10/11/2018 12:00 PM, Dennis Clarke wrote: >>> On 10/11/2018 02:50 PM, Mark Millard wrote: >>>> On 2018-Oct-11, at 11:19 AM, Dennis Clarke <dclarke at >>>> blastwave.org> wrote: >>>> >>>>> On 10/10/2018 11:59 PM, Nathan Whitehorn wrote: >>>>>> The first part of this (all the errors about "NOT FOUND") I just >>>>>> fixed >>>>>> and the fixes will be included in BETA1 and subsequent builds. The >>>>>> remaining issue is that virtio SCSI is not part of the standard >>>>>> kernel >>>>>> on PPC (there are some endian and DMA bugs), so you will need to >>>>>> use an >>>>>> alternative storage backend. The default storage backend (VSCSI) is >>>>>> fine, as are more PC-ish things like AHCI emulation. >>>>>> This command line will work and is otherwise equivalent to the below: >>>>>> qemu-system-ppc64 -enable-kvm -m 2048 -nographic -vga none -cdrom >>>>>> FreeBSD-12.0-ALPHA9-powerpc-powerpc64-20181009-r339271-disc1.iso >>>>>> /var/lib/libvirt/images/freebsd-ppc.qcow2 -mem-prealloc -mem-path >>>>>> /dev/hugepages -smp 2 >>>>>> -Nathan >>>>> >>>>> Has anyone tried this on a PowerMac G5 yet ? >>>> "this"? I'm unsure if the following is addressing what you are >>>> referring to or not. But it might be. >>>> >>>> Until the problems with -r334498 's adjustment to VM_MAX_KERNEL_ADDRESS >>>> are dealt with, PowerMac G5's have boot problems (and possibly other >>>> problems), at least those with multiple sockets (for what I can test). >>>> (I've no access to other forms of PowerMac G5's.) >>>> >>>> See: >>>> >>>> https://lists.freebsd.org/pipermail/freebsd-ppc/2018-October/009669.html >>>> >>>> >>>> and later in that thread. (Earlier in the thread is likely a waste >>>> of time >>>> to read, given what is now known.) >>>> >>>> My G5 contexts are operational by reverting -r334498 . The contexts are >>>> otherwise based on -r339076 currently. >>>> >>>> >>>> Note: >>>> >>>> My boot test on a 8 GiByte, dual-socket, one "CPU" per socket, >>>> PowerMac G5 met the conditions of Andreas Tobler's requested test >>>> conditions and the machine boot fine (VM_MAX_KERNEL_ADDRESS near >>>> the RAM size, on the low side). >>>> >>>> The G5 so-called "Quad Core"s, 4 cores total in each system but >>>> split evenly across 2 sockets in each), one with 12 GiByte and >>>> one with 16 GiByte of RAM, booted fine as well. But >>>> VM_MAX_KERNEL_ADDRESS was somewhat under 8GiByte and so not near >>>> those sizes. >>>> >>> >>> OKay ... that is a lot of good information and I'll sum up as "no". >>> >>> Was merely curious if I should give it a try. >>> >>> Dennis >>> >>> >>> _______________________________________________ >>> freebsd-ppc@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-ppc@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?341c38b5-d319-226c-946e-ecdbeaae1d0c>