main-n254654-d4e8207317c on RISC-V rv64imafdc works fine

So this is a RISC-V instance with ZFS only and definately EFI with no problems booting main-n254654-d4e8207317c kernel : admsys@ison:~ $ su - Password: root@ison:~ # zfs list NAMEUSED AVAIL REFER MOUNTPOINT rv64 16.2G 91.4G 96K /rv64 rv64/ROOT

Re: make buildworld broken on RISC-V.

types: > > root@freebsd:/usr/src/lib/clang/headers # file > /usr/obj/usr/src/riscv.riscv64/tmp/legacy/bin/clang-tblgen > /usr/obj/usr/src/riscv.riscv64/tmp/legacy/bin/clang-tblgen: ELF 64-bit > LSB executable, UCB RISC-V, version 1 (SYSV), statically linked, > FreeBSD-style, n

make buildworld broken on RISC-V.

ib/clang/headers # file /usr/obj/usr/src/riscv.riscv64/tmp/legacy/bin/clang-tblgen /usr/obj/usr/src/riscv.riscv64/tmp/legacy/bin/clang-tblgen: ELF 64-bit LSB executable, UCB RISC-V, version 1 (SYSV), statically linked, FreeBSD-style, not stripped root@freebsd:/usr/src/lib/clang/headers #

Re: ELF binary type "0" not known. (while compiling buildworld on risc-v/qemu)

> and the host is Ubuntu 20.04.x LTS. Both qemu 5.1.0 and qemu 6.1.0 are >> compiled from, source, but both OpenSBI and u-boot for risc-v are Ubuntu >> packages provided (to accompany ubuntu provided qemu 4.2.1) >> My issue while compiling both 13 and current is that compilation

Re: ELF binary type "0" not known. (while compiling buildworld on risc-v/qemu)

,filename=/dev/urandom,id=rng -device virtio-rng-device,rng=rng -nographic -append "root=LABEL=rootfs console=ttyS0" and the host is Ubuntu 20.04.x LTS. Both qemu 5.1.0 and qemu 6.1.0 are compiled from, source, but both OpenSBI and u-boot for risc-v are Ubuntu packages provided (to accomp

ELF binary type "0" not known. (while compiling buildworld on risc-v/qemu)

-device virtio-rng-device,rng=rng -nographic -append "root=LABEL=rootfs console=ttyS0" and the host is Ubuntu 20.04.x LTS. Both qemu 5.1.0 and qemu 6.1.0 are compiled from, source, but both OpenSBI and u-boot for risc-v are Ubuntu packages provided (to accompany ubuntu provided qemu 4

Re: Is there any machine RISC-V implemented ?

> On 25. Dec 2020, at 01:43, KIRIYAMA Kazuhiko wrote: > > Hi, all > > I've found RISC-V images in snapshots/ISO-IMAGES. Is there > any machine RISC-V implemented so far ? You mind find some information you need at: https://wiki.freebsd.org/riscv Be

Re: Is there any machine RISC-V implemented ?

On Fri, Dec 25, 2020 at 3:43 AM KIRIYAMA Kazuhiko wrote: > Hi, all > > I've found RISC-V images in snapshots/ISO-IMAGES. Is there > any machine RISC-V implemented so far ? > ___ > > Please , search the following phrase in Go

Is there any machine RISC-V implemented ?

Hi, all I've found RISC-V images in snapshots/ISO-IMAGES. Is there any machine RISC-V implemented so far ? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "fr

Re: RISC-V root device question -> Panic

; > argument should suffice: > > This works great but riscv 12-STABLE using last week's snapshot revision > throws the panic output included below under QEMU and leaves nothing in > /var/crash > > What expectations should I set for RISC-V STABLE and CURRENT? > Hi Michael, sorry for

Re: RISC-V root device question -> Panic

the panic output included below under QEMU and leaves nothing in /var/crash What expectations should I set for RISC-V STABLE and CURRENT? All the best, Michael t[0] == 0xffc0006c9d98 t[1] == 0x40c5 t[2] == 0x40c65000 t[3] == 0x0001 t[4] == 0x

Re: RISC-V root device question

On 12/7/20 2:40 PM, Mitchell Horne wrote: My bad, the extra '=' is a typo. It should be: -append "vfs.root.mountfrom=ufs:/dev/vtbd0p3" That worked perfectly and I added it to the wiki page: https://wiki.freebsd.org/riscv All the best, Michael

Re: RISC-V root device question

hould be: -append "vfs.root.mountfrom=ufs:/dev/vtbd0p3" > I have tried it both there after ...elf and at the end of the string. Is > this perhaps the wrong position? > > > Finally, we do have support for loader.efi on RISC-V, although I have > > not yet documented how to

Re: RISC-V root device question

nd=vfs.root.mountfrom=ufs:/dev/vtbd0p3: invalid option I have tried it both there after ...elf and at the end of the string. Is this perhaps the wrong position? Finally, we do have support for loader.efi on RISC-V, although I have not yet documented how to use it on the wiki page. If you would l

Re: RISC-V root device question

On Mon, Dec 7, 2020 at 4:54 PM Michael Dexter wrote: > > All, > > The FreeBSD wiki page on RISC-V reads: > > If you get mountroot prompt, then indicate to the kernel the location of > rootfs: > > mountroot> ufs:/dev/vtbd0 > > This indeed appears to be remain

RISC-V root device question

All, The FreeBSD wiki page on RISC-V reads: If you get mountroot prompt, then indicate to the kernel the location of rootfs: mountroot> ufs:/dev/vtbd0 This indeed appears to be remain the case on CURRENT as of last week. Specifying a device and partition, or disklabel at the mountr

Re: risc

Thank you for your email. Please note that I am out of the office on business from Monday, September 15th through Friday, September 19th. I will check email and voicemail as often as possible. If your need is urgent, please reach Matt Kellogg at 530-893-1134 or [EMAIL PROTECTED] Thanks