Re: Seeking Mac testers, was Re: Linux Mac68k v4.1.39 test kernel build is available
On Sun, 2 Apr 2017, Laurent Vivier wrote:
> Le 22/03/2017 à 01:56, Finn Thain a écrit :
> >
> > On Tue, 21 Mar 2017, Laurent Vivier wrote:
> >
> >>
> >> Tested on my Quadra 800. ADB/SCSI/Ethernet work fine.
> >>
> >> I've also tested with Q800 implementation in QEMU and works fine too.
> >>
> >
> > Thanks Laurent!
>
> It is up now for 11 days.
>
> $ uname -a
> Linux q800 4.1.39-mac_scsi-egret-etc+ #2 Fri Mar 17 10:35:58 AEDT 2017
> m68k GNU/Linux
> $ uptime
> 12:14:01 up 11 days, 19:41, 2 users, load average: 0.00, 0.07, 0.07
>
Well, this suggests that both the emulator and the kernel are stable.
> >
> > This looks like a very convenient way to test certain patches. Did you use
> > upstream QEMU or your QEMU fork at https://github.com/vivier/qemu-m68k
> > ?
>
> You can build one from:
>
> git clone -b q800-dev https://github.com/vivier/qemu-m68k.git
>
> ./configure --target-list=m68k-softmmu
>
make
> ./m68k-softmmu/qemu-system-m68k -M q800 \
> -serial none -serial mon:stdio -m 1000M \
> -drive file=./virtm68k-etch.qcow2,format=qcow2 -net nic,model=dp83932,addr=09:00:07:12:34:57 \
> -net bridge,helper=/usr/libexec/qemu-bridge-helper,br=virbr0 \
> -append "root=/dev/sda2 rw console=ttyS0 console=tty" \
> -kernel vmlinux-4.8.0-2-m68k \
> -initrd initrd.img-4.8.0-2-m68k \
> -g 1024x768x24
>
Thanks for these hints.
I created a bridge.conf with "allow virbr0" and then I was able to boot my
usual initramfs without any issues. Too easy! I will try booting an NFS
rootfs when I get time.
> >> You can find attached the both dmesg.
> >>
> >
> > Interesting... the QEMU log says:
> >
> > Slot 9:
> > Board resource not found!
> >
> > This is a bit surprising because it seems to suggest that
> > nubus_probe_slot() found a meaningful bytelanes value. That logic got
> > changed in this patch series.
> >
> > I wonder whether the vmlinux-4.1.39-mac_scsi-egret+ build on
> > sourceforge produces the same messages (?)
>
> With a 4.8.0-2, I've got:
>
> [ 0.180000] NuBus: Scanning NuBus slots.
> [ 0.180000] Now probing slot 9 at f9ffffff
> [ 0.180000] Slot 9:
> [ 0.180000] Board resource not found!
> [ 0.180000] Now probing slot A at faffffff
> [ 0.180000] Now probing slot A at fafffffe
> [ 0.180000] Now probing slot A at fafffffd
> [ 0.180000] Now probing slot A at fafffffc
> [ 0.180000] Now probing slot B at fbffffff
> [ 0.180000] Now probing slot B at fbfffffe
> [ 0.180000] Now probing slot B at fbfffffd
> [ 0.180000] Now probing slot B at fbfffffc
> [ 0.180000] Now probing slot C at fcffffff
> [ 0.180000] Now probing slot C at fcfffffe
> [ 0.180000] Now probing slot C at fcfffffd
> [ 0.180000] Now probing slot C at fcfffffc
> [ 0.180000] Now probing slot D at fdffffff
> [ 0.180000] Now probing slot D at fdfffffe
> [ 0.180000] Now probing slot D at fdfffffd
> [ 0.180000] Now probing slot D at fdfffffc
> [ 0.180000] Now probing slot E at feffffff
> [ 0.180000] Now probing slot E at fefffffe
> [ 0.180000] Now probing slot E at fefffffd
> [ 0.180000] Now probing slot E at fefffffc
>
> Slot 9 is the graphic card:
>
> (qemu) info qtree
> bus: main-system-bus
> type System
> dev: mac-nubus-bridge, id ""
> mmio 0000000060000000/0000000090000000
> mmio 00000000f0000000/000000000f000000
> bus: nubus-bus.0
> type nubus-bus
> dev: nubus-macfb, id ""
> width = 800 (0x320)
> height = 600 (0x258)
> depth = 16 (0x10)
> ...
>
> This can be a bad Nubus emulation in qemu.
>
Maybe not... FWIW, I found the following in an old log file from a
PowerBook Duo 280c. (Perhaps this was with a mini dock fitted...)
NuBus: Scanning NuBus slots.
Slot E, format block at 0xfeffffec
Format block: 00fe 0014 0000 0000 bb60 e2e9 0101 5a93 2bc7 000f
Slot E:
Board resource not found!
Anyway, thanks for confirming that the "not found" message was not a
regression caused by the Nubus patches in my queue.
--
> Thanks,
> Laurent
>
>
Reply to: