Date: Mon, 19 Jan 2026 20:00:09 +0100 From: Roman Bogorodskiy <novel@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: Mark Johnston <markj@freebsd.org>, freebsd-virtualization@freebsd.org, freebsd-arm@freebsd.org Subject: Re: Quartz64: vmm: No vgic found Message-ID: <aW5_OdxyBwd1UL23@tulp> In-Reply-To: <CAJ-Vmo=3JYsUq24twBUVYu%2BieH7U9UvTrq1axf=M=Le9nTqfmQ@mail.gmail.com> References: <aWkm8jwP6SRvT7iW@tulp> <aWqf5qNu_IlMMiEt@nuc> <aWvEs2_2aN0Gz67l@tulp> <aW5KzB0F1QhKf2Om@nuc> <aW5x45wvWb2lSWNy@tulp> <CAJ-Vmo=3JYsUq24twBUVYu%2BieH7U9UvTrq1axf=M=Le9nTqfmQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Adrian Chadd wrote: > On Mon, 19 Jan 2026 at 10:05, Roman Bogorodskiy <novel@freebsd.org> wrote: > > > > I think the eqos driver has no acpi bus support. > > > > Interestingly, the eqos driver has stopped working completely, even in > > the devicetree mode, even with vmm_load commented out in > > /boot/loader.conf. > > > > eqos0: <DesignWare EQOS Gigabit ethernet> mem 0xfe010000-0xfe01ffff irq 27,28 on ofwbus0 > > eqos0: reset timeout! > > device_attach: eqos0 attach returned 60 > > When did it last work? Do you have a dmesg from that? It definitely worked when booting from U-boot, here's the dmesg: https://people.freebsd.org/~novel/misc/quartz64_model_a_dmesg.txt I also *think* it literally worked yesterday, already with booting using EDK2 and using the Devicetree mode. But I may be wrong here, I have rebooted it million times testing various variations of ACPI / ACPI + Devicetree / Devicetree modes, modules loading etc. > > -a > > > > > Not sure if it's directly related to the vmm issue though. > >home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aW5_OdxyBwd1UL23>