https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255584
Bug ID: 255584
Summary: freebsd-release13.0 for arm64 could not enter
multi-user mode
Product: Base System
Version: 13.0-RELEASE
Hardware: arm64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: arm
Assignee: [email protected]
Reporter: [email protected]
My env.
windows10 host, and using QEMU aarch64 system emulation,
QEMU is executed under cygwin-terminal
Release 13.0 was booted and can enter single user mode ,but could not enter
multi-user mode. QEMU is quit.
startup script:
# for freebsd arm
imgfile='.\\FreeBSD-13.0-RELEASE-arm64-aarch64.qcow2'
#imgfile='.\\FreeBSD-12.2-RELEASE-arm64-aarch64.qcow2'
fmt=qcow2
biosf='.\\QEMU_EFI.fd'
#biosf=edk2-aarch64-code.fd
$qemusys \
-m 4096M -cpu cortex-a72 -M virt,highmem=off -k ja -smp 2 \
-bios $biosf \
-drive if=none,file=$imgfile,format=$fmt,id=hd0 \
-device virtio-blk-device,drive=hd0 \
-device qemu-xhci \
-device usb-kbd \
-netdev tap,id=net0,ifname=$tap -net nic,macaddr=$mymac,netdev=net0 \
-serial mon:stdio \
-nographic \
---------------
Under single user mode, there is no ttyv(0...) virtual terminal device file.
During boot sequence to multi-user mode, following cons message found,
...
Starting devd.
eval: cannot open /dev/ttyv0: No such file or directory
eval: cannot open /dev/ttyv0: No such file or directory
Starting dhclient.
...
I think due to lack of ttyv? device file, init could not open virtual terminal
by getty.
Is there any workaround?
regards;
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.