Re: sbcl question
Quoting Sebastien Marie : Robert Palm writes: Any idea what's wrong here ? tron$ doas pkg_add sbcl quirks-7.48 signed on 2024-09-01T21:44:41Z .libs-sbcl-2.4.4+.libs-sbcl-2.4.6+.libs1-sbcl-2.4.5->sbcl-2.4.7: ok tron$ sbcl --version SBCL 2.4.7.openbsd.sbcl-2.4.7 tron$ pkg_info | grep sbcl sbcl-2.4.7 high performance Common Lisp compiler tron$ sbcl fatal error encountered in SBCL pid 61439 pthread 0x737994863e0: Can't find sbcl.core What does it mean with the older libs? .libs-sbcl-2.4.4+.libs-sbcl-2.4.6+.libs1-sbcl-2.4.5->sbcl-2.4.7: ok sbcl.core file is expected to be at /usr/local/lib/sbcl/sbcl.core so check that the package is properly installed (see pkg_check) old libs-sbcl packages could be deleted, if you didn't create locally program linking to libsbcl.so . (see pkg_delete) additionnally, using 'pkg_add sbcl' is odd if you already have old sbcl installed. 'pkg_add -u' (for update) is the normal way. Regards. -- Sebastien Marie Thanks. It works now again and is properly installed. Don't know why it failed earlier.
sbcl question
Any idea what's wrong here ? tron$ doas pkg_add sbcl quirks-7.48 signed on 2024-09-01T21:44:41Z .libs-sbcl-2.4.4+.libs-sbcl-2.4.6+.libs1-sbcl-2.4.5->sbcl-2.4.7: ok tron$ sbcl --version SBCL 2.4.7.openbsd.sbcl-2.4.7 tron$ pkg_info | grep sbcl sbcl-2.4.7 high performance Common Lisp compiler tron$ sbcl fatal error encountered in SBCL pid 61439 pthread 0x737994863e0: Can't find sbcl.core What does it mean with the older libs? .libs-sbcl-2.4.4+.libs-sbcl-2.4.6+.libs1-sbcl-2.4.5->sbcl-2.4.7: ok
Re: doas tab completion
Thanks a lot for sharing all this great solutions! Am 29. Juli 2024, 17:37, um 17:37, Stuart Henderson schrieb: >On 2024-07-29, Robert Palm wrote: >> >> Hi, >> >> wonder how I can get TAB completion in the shell when using doas ... >> >> Do I need to add something to .profile ? > >pkg_add dmenu, then you can add this: > >set -A complete_doas `dmenu_path` > >(note it will not update automatically if a new program is installed; >either restart the shell, or re-run the 'set' command)
Re: doas tab completion
Quoting Marcus MERIGHI : Hello Robert, develo...@robert-palm.de (Robert Palm), 2024.07.29 (Mon) 09:47 (CEST): wonder how I can get TAB completion in the shell when using doas ... Do I need to add something to .profile ? as I understand your other messages in this thread you are looking for a solution for ksh(1). What you are looking for is "set -A" (or set +A). Example from my .kshrc: set -A complete_ifstat_1 -- iwm0 em0 ure0 athn0 umb0 wg7 set -A complete_ifstat_2 -- up down But, unless you are running a very short list of commands with doas, this will become a fairly long list. Marcus Hi Marcus! Many thanks for your suggestion. You nailed it :) Included now as a starter set -A complete_doas_1 -- sysupgrade pkg_add After reloading with . ~/.kshrc it does exactly what I wanted. Cool.
Re: doas tab completion
Zitat von Jan Stary : On Jul 29 11:44:32, develo...@robert-palm.de wrote: > On Jul 29 09:47:39, develo...@robert-palm.de wrote: > > wonder how I can get TAB completion in the shell when using doas ... echo $SHELL Different shells do (or don't) this differently. > tab completion is not specific to any command. Hm, it does work, e.g. when I start typing $sysu it shows me the commands starting with "sysu" Yes. That is not specific to sysupgrade. But I would like this to happen even if I use $doas sysu If I am not mistaken, command names are only completed as the first (zeroth) argument. Doing this for the second argument would be doas-specific: the shell would need to know that while a command (doas) has already been given, there is still another command to be given, because the first is doas; in other words, the shell would need to know the semantics of the (first) command, which it doesn't. For the > first argument, file names are completed instead, as that is a typical argument to a command (already given). There seems to be a solution for the bash shell (adding following to ~/.bashrc) complete -cf doas but I cannot figure out how to do this for ksh. My workaround is to type in the command (using autocompletion) and then jump to the beginning of the shell again adding doas in front of the cmd. But it would be nice to start with doas and then simply typing in the cmd... Why stop here? It would be "nice" if tab-completion would complete the hostnames from ~/.ssh/known_hosts when you have already said 'ssh'; some shells do that, the OpenBSD ksh doesn't. It is the opposite of siplicity. Understand, thanks. Just wanted to know whether I missed some optional settings.
Re: doas tab completion
Zitat von Jan Stary : On Jul 29 09:47:39, develo...@robert-palm.de wrote: wonder how I can get TAB completion in the shell when using doas ... tab completion is not specific to any command. Hm, it does work, e.g. when I start typing $sysu it shows me the commands starting with "sysu" But I would like this to happen even if I use $doas sysu There seems to be a solution for the bash shell (adding following to ~/.bashrc) complete -cf doas but I cannot figure out how to do this for ksh. My workaround is to type in the command (using autocompletion) and then jump to the beginning of the shell again adding doas in front of the cmd. But it would be nice to start with doas and then simply typing in the cmd...
doas tab completion
Hi, wonder how I can get TAB completion in the shell when using doas ... Do I need to add something to .profile ? Thank you.
Re: gstreamer1 update
Quoting Stuart Henderson : On 2024-05-10, Robert Palm wrote: pkg_check is now clean. gstreamer still complaining. Updates are currently broken for gstreamer1-plugins-good, it will need a fix in the port + new set of packages. If you don't want to wait, pkg_delete gstreamer1-plugins-good, let it remove any packages depending on it, then pkg_add -u and reinstall any deleted packages that you need. Thanks.
Re: gstreamer1 update
I would first run "pkg_info -mz > ~/packages.txt" to bookmark the packages I currently have on my system. Then I would delete all orphaned packages by doing "pkg_delete -a". Do another "pkg_check" and if good, do a "pkg_add -uiv". Then if I lose one of my critical packages I needed, I can just run "pkg_add -l ~/packages.txt" to ensure the latest version of my packages are installed if not present. - Ampie Thanks a lot for the detailed instructions! pkg_check is now clean. gstreamer still complaining. tron$ doas pkg_delete -a .libs1-firefox-121.0.1: ok wpebackend-fdo-1.14.2p0: ok snappy-1.1.10p1: ok .libs3-firefox-119.0.1: ok .libs-spidermonkey102-102.15.1v1: ok .libs1-abseil-cpp-20230802.1: ok .libs-poppler-24.02.0: ok gas-2.31.1p0: ok libltdl-2.4.2p2: ok gnupg-2.4.5:gcr-3.41.1p3: ok .libs-libjxl-0.10.1: ok .libs-libvpx-1.13.1p2v0: ok unicode-ucd-15.1.0: ok .libs1-poppler-24.01.0: ok autoconf-2.69p3: ok .libs1-libavif-0.11.1p0: ok mpfr-4.2.1:libmpc-1.1.0: ok mpfr-4.2.1: ok libwpe-1.16.0: ok .libs1-poppler-23.05.0: ok .libs-libjxl-0.8.2: ok .libs-firefox-122.0.1: ok jsoncpp-1.9.5: ok .libs1-mpg123-1.31.3p1: ok gtest-1.14.0p0:abseil-cpp-20240116.2: ok gtest-1.14.0p0: ok .libs-libxml-2.11.6: ok .libs1-boost-1.83.0v0: ok sdl-1.2.15p12: ok .libs1-boost-1.80.0p3v0: ok .libs-nghttp3-1.0.0p0: ok rhash-1.4.4p0: ok .libs-openjp2-2.5.0: ok .libs1-lcms2-2.15: ok .libs-firefox-123.0.1: ok .libs1-firefox-124.0.2: ok .libs-ngtcp2-1.0.1p0: ok .libs-firefox-119.0.1: ok gcc-libs-11.2.0p13: ok Running tags: ok Read shared items: ok tron$ doas pkg_check Packing-list sanity: ok Direct dependencies: ok Reverse dependencies: ok Files from packages: ok tron$ doas pkg_add -uiv Update candidates: quirks-7.21 -> quirks-7.21 Update candidates: updatedb-0p0 -> updatedb-0p0 quirks-7.21 signed on 2024-05-07T10:33:22Z Update candidates: adwaita-icon-theme-46.0 -> adwaita-icon-theme-46.0 Update candidates: gtk4-update-icon-cache-4.14.4 -> gtk4-update-icon-cache-4.14.4 Update candidates: hicolor-icon-theme-0.17 -> hicolor-icon-theme-0.17 Update candidates: gdk-pixbuf-2.42.11p0 -> gdk-pixbuf-2.42.11p0 Update candidates: png-1.6.43 -> png-1.6.43 Update candidates: glib2-2.80.0 -> glib2-2.80.0 Update candidates: py3-packaging-23.2 -> py3-packaging-23.2 Update candidates: python-3.10.14p0 -> python-3.10.14p0 Update candidates: libffi-3.4.4p1 -> libffi-3.4.4p1 Update candidates: gettext-runtime-0.22.5 -> gettext-runtime-0.22.5 Update candidates: libiconv-1.17 -> libiconv-1.17 Update candidates: xz-5.4.5 -> xz-5.4.5 Update candidates: sqlite3-3.44.2 -> sqlite3-3.44.2 Update candidates: bzip2-1.0.8p0 -> bzip2-1.0.8p0 Update candidates: pcre2-10.37p2 -> pcre2-10.37p2 Update candidates: shared-mime-info-2.4 -> shared-mime-info-2.4 Update candidates: libxml-2.12.6 -> libxml-2.12.6 Update candidates: tiff-4.6.0 -> tiff-4.6.0 Update candidates: jpeg-3.0.2v0 -> jpeg-3.0.2v0 Update candidates: zstd-1.5.6 -> zstd-1.5.6 Update candidates: lz4-1.9.4 -> lz4-1.9.4 Update candidates: librsvg-2.58.0 -> librsvg-2.58.0 Update candidates: pango-1.52.2 -> pango-1.52.2 Update candidates: harfbuzz-8.4.0 -> harfbuzz-8.4.0 Update candidates: graphite2-1.3.14 -> graphite2-1.3.14 Update candidates: cairo-1.18.0 -> cairo-1.18.0 Update candidates: lzo2-2.10p2 -> lzo2-2.10p2 Update candidates: fribidi-1.0.14 -> fribidi-1.0.14 Update candidates: anthy-9100hp3 -> anthy-9100hp3 Update candidates: aom-3.8.2 -> aom-3.8.2 Update candidates: ap2-mod_jk-1.2.49 -> ap2-mod_jk-1.2.49 Update candidates: apache-httpd-2.4.59p0 -> apache-httpd-2.4.59p0 Update candidates: nghttp2-1.61.0 -> nghttp2-1.61.0 Update candidates: jansson-2.14 -> jansson-2.14 Update candidates: apr-util-1.6.3 -> apr-util-1.6.3 Update candidates: apr-1.7.2 -> apr-1.7.2 Update candidates: db-4.6.21p7v0 -> db-4.6.21p7v0 Update candidates: brotli-1.0.9p0 -> brotli-1.0.9p0 Update candidates: curl-8.7.1 -> curl-8.7.1 Update candidates: nghttp3-1.2.0 -> nghttp3-1.2.0 Update candidates: ngtcp2-1.4.0 -> ngtcp2-1.4.0 Update candidates: appstream-1.0.3 -> appstream-1.0.3 Update candidates: libxmlb-0.3.19 -> libxmlb-0.3.19 Update candidates: libyaml-0.2.5 -> libyaml-0.2.5 Update candidates: libstemmer-2.2.0 -> libstemmer-2.2.0 Update candidates: aspell-0.60.8.1 -> aspell-0.60.8.1 Update candidates: at-spi2-core-2.52.0 -> at-spi2-core-2.52.0 Update candidates: dbus-1.14.10v0 -> dbus-1.14.10v0 Update candidates: avahi-glib-0.8p2 -> avahi-glib-0.8p2 Update candidates: avahi-libs-0.8p3 -> avahi-libs-0.8p3 Update candidates: libevent-2.1.12p0 -> libevent-2.1.12p0 Update candidates: bash-5.2.26 -> bash-5.2.26 Update candidates: boost-1.84.0p2v0 -> boost-1.84.0p2v0 Update candidates: icu4c-74.2p0v0 -> icu4c-74.2p0v0 Update candidates: catfish-4.18.0 -> catfish-4.18.0 Update candidates: py3-pexpect-4.9.0 -> py3-pexpect-4.9.0 Update candidates: py3-ptyprocess-0.7.0p3 -> py3-ptyprocess-0.7.0p3 Update candidates: gtk+3-3.24.41 -> gtk+3-3.24.41 Update candidates: libxkbcommon-1.7.0 -> libxkbcommon-1.7.0 Update candi
gstreamer1 update
Hi, any suggestions how to fix this ? tron$ pkg_check Packing-list sanity: ok Direct dependencies: ok Reverse dependencies: ok Files from packages: ok --- consolekit2-1.2.6p4 --- /usr/local/share/polkit-1/rules.d/10-openbsd-consolekit.rules should exist --- dbus-daemon-launch-helper-1.14.10 --- can't read /usr/local/libexec/dbus-daemon-launch-helper --- polkit-124 --- /usr/local/share/polkit-1/rules.d/50-default.rules should exist tron$ doas pkg_add -u quirks-7.21 signed on 2024-05-07T10:33:22Z gstreamer1-1.24.2->1.24.3 forward dependencies: | Dependency of gstreamer1-plugins-base-1.24.2 on gstreamer1-=1.24.2 doesn't match Merging gstreamer1-plugins-base-1.24.2->1.24.3 (ok) gstreamer1+gstreamer1-plugins-base-1.24.2->1.24.3 forward dependencies: | Dependency of gstreamer1-plugins-libav-1.24.2 on gstreamer1-plugins-base-=1.24.2 doesn't match | Dependency of gstreamer1-plugins-good-1.24.2 on gstreamer1-plugins-base-=1.24.2 doesn't match | Dependency of gstreamer1-plugins-bad-1.24.2 on gstreamer1-plugins-base-=1.24.2 doesn't match Merging gstreamer1-plugins-libav-1.24.2->1.24.3 (ok) NOT MERGING: can't find update for [gstreamer1-plugins-good-1.24.2] (ok) Merging gstreamer1-plugins-bad-1.24.2->1.24.3 (ok) Proceed with update anyway ? [y/N/a] N gstreamer1-plugins-base-1.24.2->1.24.3 forward dependencies: | Dependency of gstreamer1-plugins-libav-1.24.2 on gstreamer1-plugins-base-=1.24.2 doesn't match | Dependency of gstreamer1-plugins-bad-1.24.2 on gstreamer1-plugins-base-=1.24.2 doesn't match | Dependency of gstreamer1-plugins-good-1.24.2 on gstreamer1-plugins-base-=1.24.2 doesn't match Merging gstreamer1-plugins-libav-1.24.2->1.24.3 (ok) Merging gstreamer1-plugins-bad-1.24.2->1.24.3 (ok) NOT MERGING: can't find update for [gstreamer1-plugins-good-1.24.2] (ok) Proceed with update anyway ? [y/N/a] N Couldn't find updates for gstreamer1-1.24.2 gstreamer1-plugins-bad-1.24.2 gstreamer1-plugins-base-1.24.2 gstreamer1-plugins-libav-1.24.2 Couldn't install gstreamer1-1.24.3 gstreamer1-plugins-bad-1.24.3 gstreamer1-plugins-base-1.24.3 gstreamer1-plugins-libav-1.24.3 Thanks!
Java question
Morning, compiling with maven / java I get something like java(25567) in free(): bogus pointer (double free?) 0x64e3b86c000 c.f.: https://github.com/eclipse-store/bookstore-demo/issues/1 or java(97509) in free(): bogus pointer (double free?) 0xe1c89941000 Abort trap (core dumped) c.f.: https://github.com/xdev-software/spring-data-eclipse-store/issues/15 Does anyone know why this happens? I am on GENERIC.MP#1646 amd64 tron$ mvn --version Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) Maven home: /home/rpx/Downloads/apache-maven-3.9.6 Java version: 21.0.1, vendor: N/A, runtime: /usr/local/jdk-21 Default locale: en_US, platform encoding: UTF-8 OS name: "openbsd", version: "7.4", arch: "amd64", family: "unix" tron$ java --version openjdk 21.0.1 2023-10-17 OpenJDK Runtime Environment (build 21.0.1+12-2) OpenJDK 64-Bit Server VM (build 21.0.1+12-2, mixed mode, sharing Thanks! Robert
Re: Freetype FT_CONFIG_OPTION_USE_PNG
Is it possible to go with one of the suggestions? https://github.com/libsdl-org/SDL_ttf/issues/321#issuecomment-1872305906 Thanks! Am 22. Dez. 2023, 14:08, um 14:08, Stuart Henderson schrieb: >On 2023/12/22 07:11, Robert Palm wrote: >> Stuart, thank you. >> >> Is it possible to builtin / bundle freetype with sdl2 / sdl2-ttf and >enable this option? >> >> I think op@ did something similar with godot... >> >> Am 21. Dez. 2023, um 22:29, Stuart Henderson > schrieb: >> >> On 2023-12-21, Robert Palm wrote: >> >> I wanted to ask if in xenocaras freetype the >FT_CONFIG_OPTION_USE_PNG >> is enabled. >> >> It's not, afaik it can't be done unless libpng would be moved >from ports to xenocara. >> > >From a quick look it seems that sdl2-ttf already uses a bundled copy of >freetype.
Re: Freetype FT_CONFIG_OPTION_USE_PNG
Stuart, thank you. Is it possible to builtin / bundle freetype with sdl2 / sdl2-ttf and enable this option? I think op@ did something similar with godot... Am 21. Dez. 2023, 22:29, um 22:29, Stuart Henderson schrieb: >On 2023-12-21, Robert Palm wrote: >> >> I wanted to ask if in xenocaras freetype the FT_CONFIG_OPTION_USE_PNG > >> is enabled. > >It's not, afaik it can't be done unless libpng would be moved from >ports to xenocara. > >-- >Please keep replies on the mailing list.
Freetype FT_CONFIG_OPTION_USE_PNG
I wanted to ask if in xenocaras freetype the FT_CONFIG_OPTION_USE_PNG is enabled.
Re: [PossibleSpam] UTF-8 chars
Thanks again to all of you! xterm is now working!!! Still, xfce4-terminal doesn't seem to use this settings. Don't dare to ask where that setting is digged. Quoting Omar Polo : On 2023/12/16 12:08:03 +0100, Nowarez Market wrote: Using xterm, then CTRL + Right click, I add TrueType and I can display the lock: https://5md.es/l/2cc972f Seems you need a TrueType font do display the trick... Yes, the default 'fixed' font has some 'fancy' character in it but not much else. The alternative is to run xterm with -fa 'Font Name' or something like this to your ~/.Xdefaults (and then xrdb -load ~/.Xdefaults dependending on your configuration) XTerm*faceName: xft:DejaVu Sans Mono:pixelsize=10 also... Robert Palm wrote: > > Seems I have no success... > > Did a > > export LC_CTYPE=de_DE.UTF-8 How did you ran this? Running *inside* the terminal emulator won't change anything. I don't know if xfce sets up this var by itself, but usually you'd need it in your ~/.xsession file.
Re: [PossibleSpam] UTF-8 chars
Seems I have no success... Did a export LC_CTYPE=de_DE.UTF-8 and use DejaVu Sans Mono Book 12 as xterm font. Can enter, e.g. Σ with CTRL - SHIFT u 03a3 (or simply copy it in xterm). For 1f512 , i.e. 🔒, still only a blank. Anything else you specified maybe ? I have xfce-terminal 1.1.1 Quoting Omar Polo : On 2023/12/15 15:33:44 -0600, "Jay F. Shachter" wrote: Centuries ago, Nostradamus predicted that Robert Palm would write on Fri Dec 15 15:10:58 2023: > > I am playing with UTF-8 characters and try to display, e.g. a lock > symbol https://www.compart.com/en/unicode/U+1F512 > > I use xfce and set the terminal default character encoding to UTF-8 in > advanced settings. > > Still I cannot get it displayed in xterm or emacs, e.g. by simply > trying to copy paste from the website :-/ > > Emacs gives a box and xterm a blank. This is probably 'just' a font issue. For instance, I'm currently using DejaVu Sans Mono on xterm and it renders the lock icon for me, while on emacs Julia Mono doesn't. Make sure you have a UTF8 locale set too. Does your version of xterm support UTF-8? Uxterm was originally the version of xterm that supported UTF-8. That was a long time ago; on my system, xterm now also supports UTF-8. Maybe on your system you have to install uxterm. xterm on OpenBSD definitely supports and has utf8 enabled.
Re: UTF-8 chars
Thanks a lot for looking into my admittedly exotic question. I will try the font op@ suggested, but wonder about noto (which was my pick). Am 16. Dez. 2023, 04:44, um 04:44, Nowarez Market schrieb: > >I neither can't see the char you show us but about the support of the >unicode\Chinese in OpenBSD.. > >I have the font Noto in my system and I own the following in the >.xinitrc file: > >export LC_CTYPE=zh_CN.UTF-8 > >export GTK_IM_MODULE=xim >export QT_IM_MODULE=xim >export GLFW_IM_MODULE=ibus >export XMODIFIERS="@im=SCIM" >/usr/local/bin/scim -d & > >xconsole -iconic & > >/usr/local/bin/startxfce4 > >Indeed I can now do the following from xfce4-terminal: > >wiz$ pwd >/home/wiz >wiz$ ls > >wiz$ touch 你好.txt >wiz$ ls >你好.txt > >Please not that xfce4-terminal encoding is configured on UTF-8 but it >can use any frontend font like "Monospace Regular 10" and at need seems >to pick up the right font. > >I want to thank everyone worked on the unicode support at system level >for the nice eandover, appreciated. > > >== Nowarez Market > > > >Robert Palm wrote: > >> I am playing with UTF-8 characters and try to display, e.g. a lock >> symbol https://www.compart.com/en/unicode/U+1F512 >> >> I use xfce and set the terminal default character encoding to UTF-8 >> in advanced settings. >> >> Still I cannot get it displayed in xterm or emacs, e.g. by simply >> trying to copy paste from the website :-/ >> >> Emacs gives a box and xterm a blank. >> >> Any hints? Thanks!
UTF-8 chars
I am playing with UTF-8 characters and try to display, e.g. a lock symbol https://www.compart.com/en/unicode/U+1F512 I use xfce and set the terminal default character encoding to UTF-8 in advanced settings. Still I cannot get it displayed in xterm or emacs, e.g. by simply trying to copy paste from the website :-/ Emacs gives a box and xterm a blank. Any hints? Thanks!
Re: Fwd: install74.iso
Thank you. Am 23. Okt. 2023, 21:36, um 21:36, Theo de Raadt schrieb: >In the next few snapshots, an ISO file will start to show up. > >I won't be testing it. You will. Privately let me know how it goes >and >I'll make more tweaks to it. > >There may be problems with bootblocks, etc. At this time I don't know >what >it will take to get it right. > >Robert Palm wrote: > >> Thanks! >> >> Indeed, Dan has a point here as e.g. with hetzner you can easily ask >for an .iso to add for your machine and use that for installation. >> >> With the .img format you need to use the rescue console, dd the .img >yourself and restart which is effort. >> >> So, I would welcome an .iso, too if possible and align with other >archs? >> >> Am 23. Okt. 2023, 21:08, um 21:08, Ampie Niemand > schrieb: >> >On Mon, Oct 23, 2023 at 07:27:18PM +0200, Robert Palm wrote: >> >> As this list is not very active I forward your mail to misc@ >> >> >> >> Am 21. Okt. 2023, 16:59, um 16:59, Dan >> >schrieb: >> >> >Hi folks, >> >> > >> >> >Is there a technical reason why the project is not providing >> >> >installation ISOs for the arm64 architecture? >> > >> >I'm pretty sure install74.img and miniroot74.img is provided >instead. >> >The idea is that you 'burn' that to a USB stick / thumb drive and >boot >> >with >> >that. I think that this category initially had mostly Pi's so there >was >> >no >> >need for CDROMs. >> > >> >> > >> >> >The easiest way to install OpenBSD on a new cloud virtual machine >> >for >> >> >me would be to mount cd74.iso and boot. >> >> > >> >> >Could someone give me some pointers for turning the arm bsd.rd >> >> >installation ramdisk kernel into a minimal CD-ROM image? >> >> > >> >> > >> >> >Thank you, >> >> >Dan >> >> >> > >> >-Ampie >>
Re: Fwd: install74.iso
Thanks! Indeed, Dan has a point here as e.g. with hetzner you can easily ask for an .iso to add for your machine and use that for installation. With the .img format you need to use the rescue console, dd the .img yourself and restart which is effort. So, I would welcome an .iso, too if possible and align with other archs? Am 23. Okt. 2023, 21:08, um 21:08, Ampie Niemand schrieb: >On Mon, Oct 23, 2023 at 07:27:18PM +0200, Robert Palm wrote: >> As this list is not very active I forward your mail to misc@ >> >> Am 21. Okt. 2023, 16:59, um 16:59, Dan >schrieb: >> >Hi folks, >> > >> >Is there a technical reason why the project is not providing >> >installation ISOs for the arm64 architecture? > >I'm pretty sure install74.img and miniroot74.img is provided instead. >The idea is that you 'burn' that to a USB stick / thumb drive and boot >with >that. I think that this category initially had mostly Pi's so there was >no >need for CDROMs. > >> > >> >The easiest way to install OpenBSD on a new cloud virtual machine >for >> >me would be to mount cd74.iso and boot. >> > >> >Could someone give me some pointers for turning the arm bsd.rd >> >installation ramdisk kernel into a minimal CD-ROM image? >> > >> > >> >Thank you, >> >Dan >> > >-Ampie
Fwd: install74.iso
As this list is not very active I forward your mail to misc@ Am 21. Okt. 2023, 16:59, um 16:59, Dan schrieb: >Hi folks, > >Is there a technical reason why the project is not providing >installation ISOs for the arm64 architecture? > >The easiest way to install OpenBSD on a new cloud virtual machine for >me would be to mount cd74.iso and boot. > >Could someone give me some pointers for turning the arm bsd.rd >installation ramdisk kernel into a minimal CD-ROM image? > > >Thank you, >Dan
Re: Network VF 2
Does anyone has the 1.2A version and can provide a .dtb file that works? Try https://download.exigere.com.au/pub/jh7110-starfive-visionfive-2-v1.2a.dtb (built by kettenis@) Below ethernet parts of the two (decompiled) .dtb versions I have. Can anyone make sense out of differences, please ? Many thanks for looking at it. I believe both ports work on the v1.2a, although I don't have one to confirm. The second port on the v1.3b seems to work reliably at 100baseTX full-duplex, although the MTU may need to be lowered (there is still work that needs to be done to get 1Gbps speeds and larger frame sizes working reliabilty), or try forcing half-duplex at 100baseTX. Thank you so much! That v1.2a file does work with me. I can confirm that dwqe1 works. dwqe0 still doesn't seem to receive an IP address, but at least one port works! vf2# ifconfig dwqe1 dwqe1: flags=808843 mtu 1500 lladdr 6c:cf:39:00:1c:2a index 2 priority 0 llprio 3 groups: egress media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.178.38 netmask 0xff00 broadcast 192.168.178.255 vf2# ping www.google.com PING www.google.com (142.250.186.164): 56 data bytes 64 bytes from 142.250.186.164: icmp_seq=0 ttl=110 time=35.270 ms 64 bytes from 142.250.186.164: icmp_seq=1 ttl=110 time=34.687 ms @kettenis How do you create the files ? Will you update them? Seems newer updates are flowing still into linux .dtbs... Really happy it works! Thanks again all.
Re: Network VF 2
Zitat von Matthew Ernisse :
On Mon, Jul 31, 2023 at 06:48:42PM +0200, Robert Palm said:
Cannot get network working on my VisionFive 2 (ping a different machine).
Any ideas? Thanks!
Does either side see ARP traffic for the other? (arp -an) Do you
see traffic leaving your OpenBSD machine? (tcpdump(8) is your
friend) Check for host firewalls on both sides.
FreeBSD machine:
[ snip ]
media: Ethernet autoselect (100baseTX )
100/half is a bit odd these days, is this machine able to
communicate to other things on this ethernet link?
--
Matthew Ernisse
https://www.going-flying.com/
Thanks a lot for your suggestions. I will try to check that.
One thing I did notice is that there exist 2 versions of the VF2.
1.2A
PHY0 YT8531C 2 U6 10/100/1000Mbit/sec
PHY1 YT8512C U39 10/100Mbit/sec
1.3B
PHY0 YT8531C U6 10/100/1000Mbit/sec
PHY1 YT8531C U7 10/100/1000Mbit/sec
https://doc-en.rvspace.org/VisionFive2/PDF/RV002_V1.3B_20230208.PDF
https://doc-en.rvspace.org/VisionFive2/PDF/SCH_RV002_V1.2A_20221216.pdf
I own the 1.2A.
I cannot boot / install OpenBSD using the latest release .dtb file
provided by starfive:
https://github.com/starfive-tech/VisionFive2/releases/download/VF2_v3.1.5/jh7110-visionfive-v2.dtb
So Michael was so kind to send me a
jh7110-starfive-visionfive-2-v1.3b.dtb , c.f.
https://marc.info/?l=openbsd-misc&m=169046816826966&w=2
It works very well to install and boot OpenBSD, but I assume as it is
meant for the 1.3B version the network is causing "problems" with my
version ?
I asked back to Michael and he said network works for him with his
1.3B version.
In general I can see a commit:
* Add support for the Motorcomm YT8521/YT8531 PHYs. Since these PHYs may
need various board-dependent tweaks, pass the device tree node down
to the PHY driver such that we can look at various properties to make
the necessary tweaks. Enable ytphy(4) on riscv64.
So, is the YT8512C supported already ? If not I assume I cannot use my PHY1.
But, the PHY0 should work as it is the same as the 1.3B version uses.
But maybe the .dtb does not fit properly ?
Does anyone has the 1.2A version and can provide a .dtb file that works?
Below ethernet parts of the two (decompiled) .dtb versions I have.
Can anyone make sense out of differences, please ?
Many thanks for looking at it.
jh7110-visionfive-v2.dts:
ethernet@1603 {
compatible = "starfive,dwmac", "snps,dwmac-5.10a";
reg = <0x0 0x1603 0x0 0x1>;
clock-names = "gtx", "tx", "ptp_ref", "stmmaceth", "pclk", "gtxc",
"rmii_rtx";
clocks = <0x8 0x6c 0x8 0xe0 0x8 0x6d 0x8 0xdd 0x8 0xde 0x8
0x6f 0x8 0xdf>;
resets = <0x21 0xa1 0x21 0xa0>;
reset-names = "ahb", "stmmaceth";
interrupts = <0x7 0x6 0x5>;
interrupt-names = "macirq", "eth_wake_irq", "eth_lpi";
max-frame-size = <0x2328>;
phy-mode = "rgmii-id";
snps,multicast-filter-bins = <0x40>;
snps,perfect-filter-entries = <0x80>;
rx-fifo-depth = <0x800>;
tx-fifo-depth = <0x800>;
snps,fixed-burst;
snps,no-pbl-x8;
snps,force_thresh_dma_mode;
snps,axi-config = <0x3c>;
snps,tso;
snps,en-tx-lpi-clockgating;
snps,en-lpi;
snps,write-requests = <0x4>;
snps,read-requests = <0x4>;
snps,burst-map = <0x7>;
snps,txpbl = <0x10>;
snps,rxpbl = <0x10>;
status = "okay";
#address-cells = <0x1>;
#size-cells = <0x0>;
ethernet-phy@0 {
rgmii_sw_dr_2 = <0x0>;
rgmii_sw_dr = <0x3>;
rgmii_sw_dr_rxc = <0x6>;
rxc_dly_en = <0x0>;
rx_delay_sel = <0xa>;
tx_delay_sel_fe = <0x5>;
tx_delay_sel = <0xa>;
tx_inverted_10 = <0x1>;
tx_inverted_100 = <0x1>;
Re: Network VF 2
Zitat von Matthew Ernisse :
On Mon, Jul 31, 2023 at 06:48:42PM +0200, Robert Palm said:
Cannot get network working on my VisionFive 2 (ping a different machine).
Any ideas? Thanks!
Does either side see ARP traffic for the other? (arp -an) Do you
see traffic leaving your OpenBSD machine? (tcpdump(8) is your
friend) Check for host firewalls on both sides.
FreeBSD machine:
[ snip ]
media: Ethernet autoselect (100baseTX )
100/half is a bit odd these days, is this machine able to
communicate to other things on this ethernet link?
--
Matthew Ernisse
https://www.going-flying.com/
Thanks a lot for your suggestions. I will try to check that.
One thing I did notice is that there exist 2 versions of the VF2.
1.2A
PHY0 YT8531C 2 U6 10/100/1000Mbit/sec
PHY1 YT8512C U39 10/100Mbit/sec
1.3B
PHY0 YT8531C U6 10/100/1000Mbit/sec
PHY1 YT8531C U7 10/100/1000Mbit/sec
https://doc-en.rvspace.org/VisionFive2/PDF/RV002_V1.3B_20230208.PDF
https://doc-en.rvspace.org/VisionFive2/PDF/SCH_RV002_V1.2A_20221216.pdf
I own the 1.2A.
I cannot boot / install OpenBSD using the latest release .dtb file
provided by starfive:
https://github.com/starfive-tech/VisionFive2/releases/download/VF2_v3.1.5/jh7110-visionfive-v2.dtb
So Michael was so kind to send me a
jh7110-starfive-visionfive-2-v1.3b.dtb , c.f.
https://marc.info/?l=openbsd-misc&m=169046816826966&w=2
It works very well to install and boot OpenBSD, but I assume as it is
meant for the 1.3B version the network is causing "problems" with my
version ?
I asked back to Michael and he said network works for him with his
1.3B version.
In general I can see a commit:
* Add support for the Motorcomm YT8521/YT8531 PHYs. Since these PHYs may
need various board-dependent tweaks, pass the device tree node down
to the PHY driver such that we can look at various properties to make
the necessary tweaks. Enable ytphy(4) on riscv64.
So, is the YT8512C supported already ? If not I assume I cannot use my PHY1.
But, the PHY0 should work as it is the same as the 1.3B version uses.
But maybe the .dtb does not fit properly ?
Does anyone has the 1.2A version and can provide a .dtb file that works?
I attached both versions I have as .txt. When I do a diff I see lots
of differences.
Tried to attached two pics showing diffs between 1.3B and 1.2A version
of phy0 and phy1 part (but doesn't seem to be delivered to the mailing
list so I removed them).
Can anyone make sense out of it ?
Many thanks for looking at it.
/dts-v1/;
/ {
compatible = "starfive,visionfive-v2", "starfive,jh7110";
#address-cells = <0x2>;
#size-cells = <0x2>;
model = "StarFive VisionFive V2";
osc {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0x16e3600>;
phandle = <0xf>;
};
clk-ext-camera {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0x16e3600>;
phandle = <0x31>;
};
gmac1_rmii_refin {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0x2faf080>;
phandle = <0x10>;
};
gmac1_rgmii_rxin {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0x7735940>;
phandle = <0x11>;
};
i2stx_bclk_ext {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0xbb8000>;
phandle = <0x12>;
};
i2stx_lrck_ext {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0x2ee00>;
phandle = <0x13>;
};
i2srx_bclk_ext {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0xbb8000>;
phandle = <0x14>;
};
i2srx_lrck_ext {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0x2ee00>;
phandle = <0x15>;
};
tdm_ext {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0x2ee>;
phandle = <0x16>;
};
mclk_ext {
compatible = "fixed-clock";
#clock-cells = <0x0>;
clock-frequency = <0xbb8000>;
Network VF 2
Cannot get network working on my VisionFive 2 (ping a different machine). Any ideas? Thanks! FreeBSD machine: $ ifconfig re0 re0: flags=8943 metric 0 mtu 1500 options=8209b ether a8:a1:59:a2:50:45 inet 192.168.10.20 netmask 0xff00 broadcast 192.168.10.255 media: Ethernet autoselect (100baseTX ) status: active nd6 options=29 VF2: vf2# cat /etc/hostname.dwqe1 media media 100baseTX inet autoconf inet6 autoconf Same for dwqe0. vf2# dmesg | grep dwq dwqe0 at simplebus0 gmac 0: rev 0x00, address 6c:cf:39:00:1c:29 ytphy0 at dwqe0 phy 0: YT8531 10/100/1000 PHY, rev. 11 dwqe1 at simplebus0 gmac 1: rev 0x00, address 6c:cf:39:00:1c:2a ukphy0 at dwqe1 phy 0: Generic IEEE 802.3u media interface, rev. 8: OUI 0x00, model 0x0012 vf2# ifconfig dwqe1 dwqe1: flags=a48843 mtu 1500 lladdr 6c:cf:39:00:1c:2a index 2 priority 0 llprio 3 media: Ethernet 100baseTX status: active inet6 fe80::6ecf:39ff:fe00:1c2a%dwqe1 prefixlen 64 scopeid 0x2 vf2# ifconfig dwqe1 192.168.10.30 netmask 255.255.255.0 vf2# ifconfig dwqe1 dwqe1: flags=a48843 mtu 1500 lladdr 6c:cf:39:00:1c:2a index 2 priority 0 llprio 3 media: Ethernet 100baseTX status: active inet6 fe80::6ecf:39ff:fe00:1c2a%dwqe1 prefixlen 64 scopeid 0x2 inet 192.168.10.30 netmask 0xff00 broadcast 192.168.10.255 vf2# ping 192.168.10.20 PING 192.168.10.20 (192.168.10.20): 56 data bytes ping: sendmsg: Host is down ping: wrote 192.168.10.20 64 chars, ret=-1 ping: sendmsg: Host is down ping: wrote 192.168.10.20 64 chars, ret=-1 ping: sendmsg: Host is down ping: wrote 192.168.10.20 64 chars, ret=-1 ^C --- 192.168.10.20 ping statistics --- 9 packets transmitted, 0 packets received, 100.0% packet loss vf2# netstat -rn Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface 224/4 127.0.0.1 URS00 32768 8 lo0 127/8 127.0.0.1 UGRS 00 32768 8 lo0 127.0.0.1 127.0.0.1 UHhl 12 32768 1 lo0 192.168.10/24 192.168.10.30 UCn10 - 4 dwqe1 192.168.10.20 link#2 UHRLc 01 - 3 dwqe1 192.168.10.30 6c:cf:39:00:1c:2a UHLl 0 33 - 1 dwqe1 192.168.10.255 192.168.10.30 UHb00 - 1 dwqe1
Re: Samsung NVMe M.2 SSD 970 EVO Plus fails to attach on VisionFive 2 (JH7110 SoC) board
Zitat von develo...@robert-palm.de: Zitat von "Peter J. Philipp" : [tying in misc@ for this resource] On Fri, Jul 28, 2023 at 03:26:54PM +0200, develo...@robert-palm.de wrote: Many thanks! Please, will you commit it so I can test it with the next snapshot version ? I have already contacted Robert (?) privately, here it is publically. I have exported my QEMU script on github, in case anyone else needs to compile RISCV64 kernels and images (without having to wait on snapshots): https://github.com/pbug44/openbsd-riscv-misc/blob/master/start-rv64.sh I use this config to compile kernels for riscv64 (on a rpi4b it's slow!). Best Regards, -peter -- Over thirty years experience on Unix-like Operating Systems starting with QNX. Yes, many thanks for your script and kind offer! Excited if this will work - would like to figure out how to do it later on by myself, firstly. Did not do any kernel compile yet :) Sorry for delay. I got booting from NVMe working now without recompile. I took a step back to my error after installing OpenBSD onto the nvme (without using the edk2 files). The problem after a reboot is: `** Invalid partition 3 **` `Couldn't find partition nvme 0:3` `Can't set block device` Then I figured out: `StarFive # ls nvme 0:1` `efi/` `0 file(s), 1 dir(s)` But, after booting up from nvme like so: `load` **mmc 1:1** `0x4800 vendor/jh7110-starfive-visionfive-2-v1.3b.dtb` `load` **nvme 0:1** `0x4400 efi/boot/bootriscv64.efi` `bootefi 0x4400 0x4800` I mounted the efi folder on my nvme and the sdcard and copied over the vendor folder from the sdcard to the nvme: `vf2# mount_msdos /dev/sd0i /root/efinvme/` `vf2# mount_msdos /dev/sd1i /root/efisdcard/` `vf2# cp -r /root/efisdcard/vendor/ /root/efinvme/` Now, (after another reboot) I can take out the sdcard and boot directly from nvme like so: `load` **nvme 0:1** `0x4800 vendor/jh7110-starfive-visionfive-2-v1.3b.dtb` `load` **nvme 0:1** `0x4400 efi/boot/bootriscv64.efi` `bootefi 0x4400 0x4800` So I am happy this works now. Maybe I will ask about networking in another post. Does not work for me so far on both ports after and during installation...
