Re: Add compatible laptops to the wiki
El 6/6/24 a las 18:56, Théophile Dudreuilh escribió: Hello, Hi Théophile, that would be a very good idea as the current Wiki page is a bit poor. It would be nice when you are looking for a computer that works fine in NetBSD. We wait for the experts to answer. Regards. I would like to know if it is possible to add laptops to the list on the wiki (https://wiki.netbsd.org/laptops/). I have several laptops that are relatively compatible with NetBSD 10.0, and it would be nice to have a slightly refreshed list for x64. Here is the hw-probe link for the test I did on Dell Precision 7520 i7-7920HQ a few months ago, among others. https://bsd-hardware.info/?probe=48232bd1d6 Ethernet, Wifi, Display, Sound... All basic functionalities are OK on these laptops (the 7720 i7-7820HQ and i7-7920HQ are good too). As always, disable "Switchable Graphics" in UEFI/BIOS beforehand... I have plenty of other laptops that run well, for which I will publish the tests on bsdhardware if needed. I regularly test quite a lot of hardware. Best regards, Théophile Dudreuilh (majekla on UnitedBSD)
Re: getconf LONG_BIT in NetBSD
El 21 de mayo de 2024 17:05:12 CEST, Rhialto escribió: >On Mon 20 May 2024 at 22:20:30 +0200, Ramiro Aceves wrote: >> AC_PREREQ(2.50) >> AC_INIT(xmain.c) >> AC_MSG_CHECKING([OS]) >> AC_CONFIG_FILES([Makefile]) >> AC_CONFIG_FILES([ft245.c]) >> BITS=`(getconf LONG_BIT)` <<<<Here >> AC_SUBST(BITS) > Thanks Rihalto for answering. Sorry for delay, no free time to play with NetBSD in the last days. >I have also seen some programs that just want to know the "bitness" so >that they can call the library they produced "libfoo32" or "libfoo64" Yes, you are right, I think that is the reason. >That seems to be out of some sort of habit for MSWindows or even Linux >programs. But for NetBSD this is almost never relevant since pretty much >all programs you build and run are for the "natural" size. In my case, I >had to teach the packages to just create and use "libfoo" without >numbers. > >If this is the case for this package, you could try and do the same. > >If the packge wants to know the bitness so that it can use the right >types for typedefs or something like that, then you could change it to >use int32_t and int64_t unconditionally. > >In both cases I would call this bugs and would report upstream. Even if >you only determine that one of these scenarios is what's happening, and >you don't manage to fix it. > >-Olaf. After talking with upstream we agreed making the fewest changes in the code just to make it work. Upstream suggested to add fixes to make it work under FreeBSD cause years ago it worked in that OS (they have a port for an older version) first and after that, try NetBSD. In the former I could get it work at least partially. So we are moving towards the goal...not too much free time, we move slowly. Learning many thinks, I am very newbie in every aspect. Regards. Ramiro.
Re: getconf LONG_BIT in NetBSD
On 5/20/24 19:16, Greg A. Woods wrote: At Sun, 19 May 2024 22:08:27 +0200, Ramiro Aceves wrote: Subject: getconf LONG_BIT in NetBSD I have been playing with an autoconf ./configure script that I want get running in several OSes. The script uses "getconf LONG_BIT" to get the bits of the system. What is the purpose of this test in the context where it is needed? I would think that if it's a C program then there's no need ever for any autoconf test. Just write pure portable C that uses properly. Hello Greg, thanks for answering. If you want to take a look: https://www.sm5bsz.com/linuxdsp/archive/lir05-02.zip It is a very good SDR radio receiver program. It works in Linux and in Windows (MinGW) with several commercial radio receivers. configure.ac: AC_PREREQ(2.50) AC_INIT(xmain.c) AC_MSG_CHECKING([OS]) AC_CONFIG_FILES([Makefile]) AC_CONFIG_FILES([ft245.c]) BITS=`(getconf LONG_BIT)` ... 3630 lines of very long configure.ac script that uses $BITS variable several times to make some decisions. ... ... ... Regards. Ramiro. -- Greg A. Woods Kelowna, BC +1 250 762-7675 RoboHack Planix, Inc. Avoncote Farms
Re: getconf LONG_BIT in NetBSD
On 5/20/24 07:38, PHO wrote:
On 5/20/24 12:28, Aryabhata wrote:
The `limits.h` header file in C provides the necessary information
about system limits, including `LONG_BIT`. You can write a small C
program to print the value of `LONG_BIT`.
Create a simple C program that includes the `limits.h` header and
prints the value of `LONG_BIT`.
#include
#include
int main() {
printf("LONG_BIT: %d\n", LONG_BIT);
return 0;
}
This will output the number of bits in a "long" integer on your system.
Or use AC_COMPUTE_INT. You can do something like
AC_COMPUTE_INT([var], [LONG_BIT], [#include ])
Hello PHO,
Many thanks, I have not tried it yet, not free time today but it seems
to be a very good solution.
Regards!
Re: getconf LONG_BIT in NetBSD
On 5/20/24 05:28, Aryabhata wrote:
The `limits.h` header file in C provides the necessary information about
system limits, including `LONG_BIT`. You can write a small C program to
print the value of `LONG_BIT`.
Create a simple C program that includes the `limits.h` header and prints
the value of `LONG_BIT`.
#include
#include
int main() {
printf("LONG_BIT: %d\n", LONG_BIT);
return 0;
}
This will output the number of bits in a "long" integer on your system.
Hello Aryabhata,
Thanks so much for the suggestion!
Regards.
On Mon, 20 May, 2024, 1:38 am Ramiro Aceves, <mailto:ea1...@gmail.com>> wrote:
Hello,
I have been playing with an autoconf ./configure script that I want get
running in several OSes. The script uses "getconf LONG_BIT" to get the
bits of the system.
I see that "getconfg LONG_BIT" works in other systems such as Linux
and
FreeBSD but in NetBSD I have tried it and it does not work:
netbsd-nuc$ getconf LONG_BIT
getconf: LONG_BIT: unknown variable
I read this on limits (3) man page about LONG_BIT:
XSI Limits
Also the X/Open System Interface Extension (XSI) specifies few
limits. In NetBSD these are limited to LONG_BIT (the number of bits in
long), WORD_BIT (the number of bits in a “word”), and few limits
related
to float and double.
How can I get the value of the LONG_BIT variable?
Thanks you very much.
Regards.
Re: getconf LONG_BIT in NetBSD
On 5/20/24 00:47, Valery Ushakov wrote:
On Sun, May 19, 2024 at 22:08:27 +0200, Ramiro Aceves wrote:
I see that "getconf LONG_BIT" works in other systems such as Linux and
FreeBSD but in NetBSD I have tried it and it does not work:
netbsd-nuc$ getconf LONG_BIT
getconf: LONG_BIT: unknown variable
I read this on limits (3) man page about LONG_BIT:
XSI Limits
Also the X/Open System Interface Extension (XSI) specifies few limits.
In NetBSD these are limited to LONG_BIT (the number of bits in long),
WORD_BIT (the number of bits in a “word”), and few limits related to float
and double.
How can I get the value of the LONG_BIT variable?
Pedantically speaking, LONG_BIT is not a "conf" variable, so the
question is where you draw the line for getconf(1)? What should be
returned for LONG_BIT on a system that can run both 32-bit and 64-bit
code (amd64/i386, sparc64/sparc, etc).
Thanks UWE for the explanation.
I have a Debian and a FreeBSD installation along with NetBSD in the same
computer and both return 64 bits for the LONG_INT variable.
Looking a bit closer at the Open Group text for getconf(1) and
friends, I think they intend this kind of stuff to be onbtained via
POSIX_V7_WIDTH_RESTRICTED_ENVS getconf/confstr() and getconf -v
argument.
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/getconf.html
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/c99.html#tag_20_11_13_04
We don't support getconf -v and it seems a bit clunky and posixy
anyway. What's wrong with doing it the autoconf way by running the
compiler you are going to use? :)
The configure.ac script that has the "getconf LONG_BIT" belongs to this
program:
https://www.sm5bsz.com/linuxdsp/archive/lir05-02.zip
This software works for Windows (MinGW) and Linux. I have been trying to
compile it also in FreeBSD and NetBSD. I have had preliminary compiling
success in both OS. Once $BITS variable is obtained is used many times
to do conditional programing along the script.
AC_PREREQ(2.50)
AC_INIT(xmain.c)
AC_MSG_CHECKING([OS])
AC_CONFIG_FILES([Makefile])
AC_CONFIG_FILES([ft245.c])
BITS=`(getconf LONG_BIT)` <<<<Here
AC_SUBST(BITS)
#setterm -term linux -back white
#setterm -term linux -fore black
OS=`uname`
AC_SUBST(OS, "${OS}")
MACHINE=$(uname -m)
CPU="CPU_INTEL"
if test "$MACHINE" = "armv5l"; then
CPU="CPU_ARM"
fi
if test "$MACHINE" = "armv6l"; then
CPU="CPU_ARM"
fi
if test "$MACHINE" = "armv7l"; then
CPU="CPU_ARM"
fi
if test "$MACHINE" = "aarch64"; then
CPU="CPU_ARM"
fi
if test "$MACHINE" = "evbarm"; then <<<<< Added for NetBSD in the RPi
CPU="CPU_ARM"
fi
if test "$MACHINE" = "armv8l"; then
...
...
...
Regards.
Ramiro.
-uwe
Re: getconf LONG_BIT in NetBSD
On 5/20/24 00:27, Greg Troxel wrote: Not that this is super helpful, but posix says: https://pubs.opengroup.org/onlinepubs/9699919799/ All of the following variables shall be supported: The names of the symbolic constants listed under the headings ``Maximum Values'' and ``Minimum Values'' in the description of the header in the Base Definitions volume of POSIX.1-2017, without the enclosing braces. and, in limits.h: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html LONG_BIT appears under "Numerical Limits", not max or min. and therefore, your friendly but unhelpful language lawyer says that NetBSD's behavior is not improper. LONG_BIT is defined in limits.h. It is straightforward to write a program to print it, and run that from configure (at the expense of cross). It's also straightforward to add it to the getconf sources, and rebuild, but that doesn't help packaging. You could also insert a bit of shell that if uname is netbsd, looks at uname -p and has a table. gross, but pretty easy. Maybe somebody else knows a better way Hello Greg, Many thanks for the explanation about LONG_BIT. It makes sense. Regards.
getconf LONG_BIT in NetBSD
Hello, I have been playing with an autoconf ./configure script that I want get running in several OSes. The script uses "getconf LONG_BIT" to get the bits of the system. I see that "getconfg LONG_BIT" works in other systems such as Linux and FreeBSD but in NetBSD I have tried it and it does not work: netbsd-nuc$ getconf LONG_BIT getconf: LONG_BIT: unknown variable I read this on limits (3) man page about LONG_BIT: XSI Limits Also the X/Open System Interface Extension (XSI) specifies few limits. In NetBSD these are limited to LONG_BIT (the number of bits in long), WORD_BIT (the number of bits in a “word”), and few limits related to float and double. How can I get the value of the LONG_BIT variable? Thanks you very much. Regards.
Re: Intel Wireless fatal error
El mar, 7 may 2024 a las 11:13, Martin Husemann () escribió: > > On Tue, May 07, 2024 at 08:16:18AM +, Riccardo Mottola wrote: > > [ 3574.054462] iwi0: autoconfiguration error: fatal error > > The message is bogus, it has nothing to do with autoconfiguration. > > "Fatal error" is a bit in the interrupt cause register of the intel > chipset. The driver can not do anything about it and resets the device > (simmilar to a "ifconfig iwi0 down). This is not a good error handling > strategy, as you have noticed - and it is also done very wrong in the > iwi_softintr handler. > > The driver should clear the interrupt, schedule a reset and ignore all > other activity untill the reset has happened. Of course the reset should > include bringing up the device to full working state again. > > However, this is obviously not easy to test and debug, as you will have to > be in a setup where this happens often enough (like your's). > If you have patience and would be able to help with this: compile your > kernel with "options IWI_DEBUG" and see if that enables enough login to > give us a hint about the cause. If that is not enough you would need to > raise iwi_debug to more than the default level of 4, but that would > spam your log with every received packet. > > Please file a PR and lets collect data there. > > Martin I remember such messages in my old Compal Electronics laptop i386 machine with iwi0 several months before NetBSD 10 release, at the very early moments after installing. I did not dig into that cause I ended using the more trusty ethernet, but it was very frustrating. If you think I can help with that I can compile the kernel with IWI_DEBUG as said before. It is a computer that I do not use regulary so plenty of space to do experiments. Regards. Ramiro.
Re: need your advice before new Raspberry Pi purchase
El 24/4/24 a las 6:39, Ramiro Aceves escribió: Hello, My RPi4 arrived yesterday and everything worked and booted fine from the 128 GB SD using UEFI. Network was working fine also through ethernet without configuring anything. 3GB limit disabled. Today I will continue configuring the OS. The only nasty thing was that SD card reader in my NUC8i7 did not work in NetBSD and needed to flash it under Linux. I think I will buy a card reader for the next time. Should I fill a bug report? Thanks guys! Regards. Ramiro. Hello, I made the suggested somewhere symbolic link to avoid the "bwfm0: autoconfiguration error: NVRAM file not available", even that I am not going to use the WIFI interface. lrwxr-xr-x 1 root wheel 44 Apr 27 11:54 brcmfmac43455-sdio.Raspberry Pi 4 Model B.txt -> brcmfmac43455-sdio.raspberrypi,4-model-b.txt Will that fix be applied in next 10.1 release? Thanks. Ramiro
NetBSD Nightly Trouble Ticket Report broken?
Hello, I am receiving empty email reports. Thanks.
Re: webserver with PHP support
El 23 de abril de 2024 21:07:58 CEST, Alexey escribió: >Hello list, >tell me please what's the difference between > >/usr/pkg/libexec/cgi-bin/php >and >/usr/pkg/bin/php > >I mean that this works: >/usr/libexec/httpd -b -U nobody -C .php >/usr/pkg/libexec/cgi-bin/php /var/www/ > >and this does not: >/usr/libexec/httpd -b -U nobody -C .php /usr/pkg/bin/php /var/www/ > Hello, I think /usr/pkg/bin/php is the command line interface and /usr/pkg/libexec/cgi-bin/php the CGI command. Regards Ramiro.
Re: nice program to make sound
El 23 de abril de 2024 15:01:43 CEST, Todd Gruhn escribió: >I did: > > vlc file:///file.mp3 --play-and-exit > >I works -- but I dont want the GUI on the screen. > >Is there another program to do this? cvlc perhaps?
Re: need your advice before new Raspberry Pi purchase
Hello, My RPi4 arrived yesterday and everything worked and booted fine from the 128 GB SD using UEFI. Network was working fine also through ethernet without configuring anything. 3GB limit disabled. Today I will continue configuring the OS. The only nasty thing was that SD card reader in my NUC8i7 did not work in NetBSD and needed to flash it under Linux. I think I will buy a card reader for the next time. Should I fill a bug report? Thanks guys! Regards. Ramiro. El 22 de abril de 2024 22:16:09 CEST, Ramiro Aceves escribió: > > >El 22/4/24 a las 20:09, John Klos escribió: >> Hi, >> >>> Cause lighttpd was familar to me, I have used it under raspbian and Debian. >>>> Lighttpd Web server, home minidlna film server. >> >> If your usage is simple, then bozohttpd's setup will be very simple. For >> instance, my setup is just four lines in /etc/inetd.conf (two each for IPv4 >> and IPv6 http, and two for https). >> >> I'm interested in minidlna. Currently I can send web links to mp4 files and >> people know how to Airplay them to their TVs, but I'd love to be able to set >> up a simple media server that'd let people browse their media straight from >> their TVs. >> >> BTW - here's my Raspberry Pi 4 server: >> >> https://www.reddit.com/r/raspberry_pi/comments/w3yaes/my_updated_1u_raspberry_pi_4_server/ > >Oh, beautiful 1U server, well done! > >Minidlna seems simple to configure. I have only used it to serve films for my >wife and daughter at home, nothing exotic. > >About bozohttpd. I use lighttpd for very simple experimental WEB pages using >https, PHP and digest auth sha256 authentication. I think that bozohttpd >server only support basic authentication: > > HTTP BASIC AUTHORIZATION > bozohttpd has support for HTTP Basic Authorization. If a file named > .htpasswd exists in the directory of the current request, bozohttpd will > restrict access to documents in that directory using the RFC 2617 HTTP > "Basic" authentication scheme. > > Note: This does not recursively protect any sub-directories. > >I have to experiment. > >Thanks so much. >Ramiro. > > > > > >> >> John
Re: RPi 4b Wifi Device
Hello Thomas, I do not know what happens and if this has something to do or not. I have seen this advice in pftf/RPi4 in GitHub: Note: Booting from USB or from ESP requires a recent-enough version of the Pi EEPROM (as well as a recent version of the UEFI firmware). If you are using the latest UEFI firmware and find that booting from USB or from ESP doesn't work, please visit https://github.com/raspberrypi/rpi-eeprom/releases to update your EEPROM. My RPi4 arrived yesterday and everything worked and booted from the SD using UEFI. Regards. Ramiro. El 23 de abril de 2024 22:12:47 CEST, "Thomas D. Dean" escribió: >On 4/23/24 08:54, Justin Parrott wrote: >> this is what i was talking about, i don't like booting an sbc from stick >> >> even if you can hit disk >> >> can net run on sbc? >> > >I can boot NetBSD 10 on an RPi 4b from an SD card . It seems to run fine. >Seems lots faster than RPi OS booted from the same type SD card. > >I can > 1. access the network > 2. ssh into the RPi > 3. build applications >on a RPi 4B running NetBSD 10 booted from an SD card. > >What I can not do is get the RPi 4b to boot NetBSD from a USB-3 flash drive. > >I can get the RPi 4b to boot RPi OS from the USB-3 flask drive. > >Tom Dean
Re: need your advice before new Raspberry Pi purchase
El 22/4/24 a las 20:09, John Klos escribió: Hi, Cause lighttpd was familar to me, I have used it under raspbian and Debian. Lighttpd Web server, home minidlna film server. If your usage is simple, then bozohttpd's setup will be very simple. For instance, my setup is just four lines in /etc/inetd.conf (two each for IPv4 and IPv6 http, and two for https). I'm interested in minidlna. Currently I can send web links to mp4 files and people know how to Airplay them to their TVs, but I'd love to be able to set up a simple media server that'd let people browse their media straight from their TVs. BTW - here's my Raspberry Pi 4 server: https://www.reddit.com/r/raspberry_pi/comments/w3yaes/my_updated_1u_raspberry_pi_4_server/ Oh, beautiful 1U server, well done! Minidlna seems simple to configure. I have only used it to serve films for my wife and daughter at home, nothing exotic. About bozohttpd. I use lighttpd for very simple experimental WEB pages using https, PHP and digest auth sha256 authentication. I think that bozohttpd server only support basic authentication: HTTP BASIC AUTHORIZATION bozohttpd has support for HTTP Basic Authorization. If a file named .htpasswd exists in the directory of the current request, bozohttpd will restrict access to documents in that directory using the RFC 2617 HTTP "Basic" authentication scheme. Note: This does not recursively protect any sub-directories. I have to experiment. Thanks so much. Ramiro. John
Re: need your advice before new Raspberry Pi purchase
Cause lighttpd was familar to me, I have used it under raspbian and Debian. El 22/4/24 a las 16:03, Justin Parrott escribió: why do you choose lighttpd over the one distributed with n? On Sun, Apr 21, 2024 at 4:08 PM Ramiro Aceves <mailto:ea1...@gmail.com>> wrote: El 21/4/24 a las 20:33, Justin Parrott escribió: > what do you use it for? Lighttpd Web server, home minidlna film server. > > On Sat, Apr 20, 2024 at 2:24 PM Ramiro Aceves mailto:ea1...@gmail.com> > <mailto:ea1...@gmail.com <mailto:ea1...@gmail.com>>> wrote: > > Hello, > > I am thinking about buying a more powerful Raspberry Pi than my actual > Raspberry Pi ZeroW. I like very much how NetBSD operating system is > working although I was a bit dissapointed with WIFI driver for the > builtin WIFI device, I feel that I can control the OS and it is the > OS I > was looking for, simple and straightforward without bells and whistles. > > In general NetBSD works fine in the Pi once you get used to it, > everything makes sense soon, you fell confortable and why not to say, I > am in a new world after many years using Linux and needed new > sensations. On the Zero W WIFI bwfm driver did not work well and > overcome that buying a USB WIFI dongle with RTL 8188EU chip that works > almost ok (with no channel switching in the router). Now I am going to > use only ethernet network connection so WIFI will not be a problem. > > > I have been reading > https://wiki.netbsd.org/ports/evbarm/raspberry_pi/ <https://wiki.netbsd.org/ports/evbarm/raspberry_pi/> > <https://wiki.netbsd.org/ports/evbarm/raspberry_pi/ <https://wiki.netbsd.org/ports/evbarm/raspberry_pi/>> > but information is a bit confusing. > > "As of early 2024, NetBSD does not support the Raspberry Pi 5." > > Reading that I inmediatly discarded the Raspberry Pi 5 choice. Being > realistic I think It does not work in NetBSD 10 now and I estimate it > will not work well for perhaps some years. Life is short, I cannot wait > and so I think RaspberryPi 4 should be my buying target. > > > "NetBSD 10" > > "RPI4 general support (but there are issues)" > > Seems explained below. > > > "RPI4 ethernet (Broadcom GENETv5) (but the man page for > genet(4) is > missing)" > > Can I be sure that ethernet will work fine and reliable? Network speed? > > > "builtin bluetooth on RPI3 (RPI0W? RPI4?)" > > Does bluetooth work on the Pi4? > > > "builtin WiFi on RPI0W, RPI3 and RPI4 - bwfm(4)" > > Does WIFI bwfm driver work as badly as in the ZeroW? Not relevant for > my future use of the Pi 4 cause I will use it through ethernet but that > will be a bonus, just curious. > > > "RPI4 xhci does not work with a straight netbsd-10 install" > > I seems that below is the explanation. > > "RPI4 hardware rng does not work with a straight netbsd-10 > install" > > I seems that below is the explanation. > > > The following chapter is very confusing for me: > > > "Issues and Workarounds" > "RPI4 xhci" > > "With the netbsd-10 arm64.img on a RPI4 (most of them), the pci driver > is missing and therefore xhci will not attach, so the USB ports will > not > work. One workaround is to switch to UEFI, but that leads to a 3GB > memory limit and needing a monitor. Another is to add kernel config. > One > can also add the hardware rng. Adding the following to GENERIC64.local > results in both working; you likely also need a dtb that includes the > RNG. \todo Explain why this isn't in GENERIC64 or link to a PR. > > GENERIC64 > > bcm2838pcie* at fdt? # STB PCIe host controller > bcm2838rng* at fdt? # RPI4 RNG > > There is some need to load firmware for the xhci driver, but apparently > that works, once the above is added" > &
Re: need your advice before new Raspberry Pi purchase
Hi John El dom, 21 abr 2024 a las 23:44, John Klos () escribió: > > Hi, > > > "As of early 2024, NetBSD does not support the Raspberry Pi 5." > > I've lost interest in any new Raspberry Pi models since the > corporatization of the Raspberry Pi Foundation. For higher performance ARM > machines than the Raspberry Pi 4 hardware I already have, I'd go for a > Rock Pro 5 or Orange Pi 5. Interesting... > > >"RPI4 ethernet (Broadcom GENETv5) (but the man page for genet(4) is > > missing)" > > > > Can I be sure that ethernet will work fine and reliable? Network speed? > > There were some issues last year with npf which I observed on one of my > RPi 4 systems, but that's been addressed(-ish - not fixed, but mitigated). > Fine > I've been running a RPi 4 with an uptime of 225 days as an NFS server for > a fleet of machines that're running pkgsrc bulk builds. Good! > > > "Issues and Workarounds" > > "RPI4 xhci" > > I've never run any RPi 4 hardware without UEFI, although I tried a few > times and don't remember any successes. I will do it with UEFI as everybody says it is the way to go. Perhaps the Install document should document this better in https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.0/evbarm-aarch64/INSTALL.html, showing the different booting options. > > One of the things that UEFI does provide is that it makes having a serial > console very easy. My colocated RPi 4 was connected to an RPi 3 so that I > could boot the 4 with a serial console, get access to UEFI menus, boot > single user, et cetera. This, together with a GPIO on the RPi3 wired to be > able to reset the RPi 4, makes the RPi very useful as a remote server. That is a good tip, one Rpi can resurrect the other in case of hang. > > > What is your final opinion about NetBSD in that board? Are there better > > supported boards perhaps? > > I think different hardware has different uses. For almost instant booting, > low power and small size, I use NanoPi Neo. For hardware-based VPN, > for NAT / IPv6 / DNS / DHCP, et cetera, I use NanoPi R2S. For systems that > need PCIe, I use RockPro64. > > I picked the Raspberry Pi 4 with a Flirc case for my 1U server because at > the time it was not easy to find boards with 8 gigs of memory and with two > USB 3 ports. I'm using the USB 3 ports to connect two large (8 TB) > spinning rust disks in a raidframe mirror. For this configuration, it was > ideal. > > What do you plan to use your Pi for? Well, lighhttpd little personal web server, minidlna film server for home. I am also thinking to use the RPi 4 to record audio from amateur radio receivers with external USB cards (amateur radio and electronics is my other hobby) or data from SDR network receivers. Also GPIO for some automated tasks. > > > Many thanks and sorry for so many questions, just I want to be sure that I > > am > > going to make a good and useful purchase. If I purchase a Rpi 4 instead of > > Rpi 5 to have NetBSD support and It does not work ok, it will be a absolute > > nonsense. > > Indeed. It's no fun to get something we can't use. The RPi 4 is very > usable with NetBSD, although all of my experiences with things working > very well is based on using UEFI. Having received several positive reviews from you and others, I have just ordered my new RPi4, is coming home on thursday. I think I am going to have fun with it!. We'll keep in touch, I will share the experience. Regards. Ramiro. > > > I appreciate your work very much and your comments and advice will be > > welcome > > and very valuable for me. > > :) > > John Klos
Re: need your advice before new Raspberry Pi purchase
El 21/4/24 a las 20:33, Justin Parrott escribió: what do you use it for? Lighttpd Web server, home minidlna film server. On Sat, Apr 20, 2024 at 2:24 PM Ramiro Aceves <mailto:ea1...@gmail.com>> wrote: Hello, I am thinking about buying a more powerful Raspberry Pi than my actual Raspberry Pi ZeroW. I like very much how NetBSD operating system is working although I was a bit dissapointed with WIFI driver for the builtin WIFI device, I feel that I can control the OS and it is the OS I was looking for, simple and straightforward without bells and whistles. In general NetBSD works fine in the Pi once you get used to it, everything makes sense soon, you fell confortable and why not to say, I am in a new world after many years using Linux and needed new sensations. On the Zero W WIFI bwfm driver did not work well and overcome that buying a USB WIFI dongle with RTL 8188EU chip that works almost ok (with no channel switching in the router). Now I am going to use only ethernet network connection so WIFI will not be a problem. I have been reading https://wiki.netbsd.org/ports/evbarm/raspberry_pi/ <https://wiki.netbsd.org/ports/evbarm/raspberry_pi/> but information is a bit confusing. "As of early 2024, NetBSD does not support the Raspberry Pi 5." Reading that I inmediatly discarded the Raspberry Pi 5 choice. Being realistic I think It does not work in NetBSD 10 now and I estimate it will not work well for perhaps some years. Life is short, I cannot wait and so I think RaspberryPi 4 should be my buying target. "NetBSD 10" "RPI4 general support (but there are issues)" Seems explained below. "RPI4 ethernet (Broadcom GENETv5) (but the man page for genet(4) is missing)" Can I be sure that ethernet will work fine and reliable? Network speed? "builtin bluetooth on RPI3 (RPI0W? RPI4?)" Does bluetooth work on the Pi4? "builtin WiFi on RPI0W, RPI3 and RPI4 - bwfm(4)" Does WIFI bwfm driver work as badly as in the ZeroW? Not relevant for my future use of the Pi 4 cause I will use it through ethernet but that will be a bonus, just curious. "RPI4 xhci does not work with a straight netbsd-10 install" I seems that below is the explanation. "RPI4 hardware rng does not work with a straight netbsd-10 install" I seems that below is the explanation. The following chapter is very confusing for me: "Issues and Workarounds" "RPI4 xhci" "With the netbsd-10 arm64.img on a RPI4 (most of them), the pci driver is missing and therefore xhci will not attach, so the USB ports will not work. One workaround is to switch to UEFI, but that leads to a 3GB memory limit and needing a monitor. Another is to add kernel config. One can also add the hardware rng. Adding the following to GENERIC64.local results in both working; you likely also need a dtb that includes the RNG. \todo Explain why this isn't in GENERIC64 or link to a PR. GENERIC64 bcm2838pcie* at fdt? # STB PCIe host controller bcm2838rng* at fdt? # RPI4 RNG There is some need to load firmware for the xhci driver, but apparently that works, once the above is added" Does it mean that using "traditional booting" you end with non working USB ports? Will you even end without keyboard? I mainly will use the Pi headless via ssh but need the keyboard in the first configuring steps. After switching to UEFI you will make USB ports work but 8 GB RapberryPi will be reduced to 3 GB only with no workaround? What do "needing a monitor" mean? Why? If the fix for USB and rng is recompiling the KERNEL, why is not enabled by default in the standard image? "RPI4 UEFI 3 GB" "To work around bugs in hardware (that may or may not be fixed in recent RPI4) and because not all OSes have workarounds, the UEFI firmware's default is to limit RAM to 3GB. NetBSD 10 can be used with more, so this needs to be configured in UEFI." That should be explained more in detail for newcomers. Last questions: Do GPIO pins work ok? Does I2C work? That is important for me cause I plan to read some sensors. Does HDMI output work or should I use serial console? traditional boot vs UEFI difference in this matter? What is your final opinion about NetBSD in that board? Are there better supported boards perhaps? Many thanks and sorry for so many questions, just I want to be sure that I am going to make a good and useful purchase. If I purchase a Rpi 4 instead of Rpi 5 to have NetBSD support and It does
Re: need your advice before new Raspberry Pi purchase
El 21/4/24 a las 2:24, Michael escribió: Hello, On Sat, 20 Apr 2024 11:46:51 +0200 Ramiro Aceves wrote: "As of early 2024, NetBSD does not support the Raspberry Pi 5." Reading that I inmediatly discarded the Raspberry Pi 5 choice. Being realistic I think It does not work in NetBSD 10 now and I estimate it will not work well for perhaps some years. Life is short, I cannot wait and so I think RaspberryPi 4 should be my buying target. Not sure what's missing - there is now at least beta UEFI firmware for the Pi5. "NetBSD 10" "RPI4 general support (but there are issues)" I've been using an 8GB Pi4 and a Pi400 with UEFI for a while now. "RPI4 ethernet (Broadcom GENETv5) (but the man page for genet(4) is missing)" Can I be sure that ethernet will work fine and reliable? Network speed? Works fine on mine, good enough for NetBSD and pkgsrc builds with sources over NFS. "builtin bluetooth on RPI3 (RPI0W? RPI4?)" Does bluetooth work on the Pi4? Never tried. "builtin WiFi on RPI0W, RPI3 and RPI4 - bwfm(4)" Does WIFI bwfm driver work as badly as in the ZeroW? Not relevant for my future use of the Pi 4 cause I will use it through ethernet but that will be a bonus, just curious. IIRC I got it to connect to my router but never really stress tested it. I prefer wired ethernet wherever practical. "RPI4 xhci does not work with a straight netbsd-10 install" I seems that below is the explanation. Both my Pi4* boot from USB3 disks connected to USB3 ports. After switching to UEFI you will make USB ports work but 8 GB RapberryPi will be reduced to 3 GB only with no workaround? What do "needing a monitor" mean? Why? The 3GB limit is on by default for some old linux kernels that don't have the DMA workaround. It takes about 10 seconds to get into the UEFI setup menu and turn it off. [ 1.00] NetBSD 10.99.7 (GENERIC64) #0: Thu Aug 24 06:18:05 EDT 2023 [ 1.00] ml@paddy:/disk/build/obj_earm64/sys/arch/evbarm/compile/GENERIC64 [ 1.00] total memory = 8029 MB [ 1.00] avail memory = 7740 MB [ 1.00] entropy: ready [ 1.00] ptyfs_hashinit: 0001feef5b00 [ 1.00] timecounter: Timecounters tick every 10.000 msec [ 1.00] armfdt0 (root) [ 1.00] armfdt0: using EFI runtime services for RTC [ 1.00] simplebus0 at armfdt0: Raspberry Pi Foundation Raspberry Pi 4 Model B [ 1.00] simplebus1 at simplebus0 [ 1.00] acpifdt0 at simplebus0 [ 1.00] acpifdt0: SMBIOS rev. 3.3.0 @ 0x371d ... Does HDMI output work or should I use serial console? traditional boot vs UEFI difference in this matter? I'm typing this on a Pi400 with a monitor hooked to it. My Pi400 even came with a micro-HDMI to regular HDMI cable. have fun Michael Thanks so much Michael for the details about de RPi4 working in NetBSD. Nice to see that UEFI is the way to go. Nice also to see that 3 GB limit can be eliminated. I have also received other people direct positive feedback. Chances to buy it are increasing. Thanks. Ramiro.
need your advice before new Raspberry Pi purchase
Hello, I am thinking about buying a more powerful Raspberry Pi than my actual Raspberry Pi ZeroW. I like very much how NetBSD operating system is working although I was a bit dissapointed with WIFI driver for the builtin WIFI device, I feel that I can control the OS and it is the OS I was looking for, simple and straightforward without bells and whistles. In general NetBSD works fine in the Pi once you get used to it, everything makes sense soon, you fell confortable and why not to say, I am in a new world after many years using Linux and needed new sensations. On the Zero W WIFI bwfm driver did not work well and overcome that buying a USB WIFI dongle with RTL 8188EU chip that works almost ok (with no channel switching in the router). Now I am going to use only ethernet network connection so WIFI will not be a problem. I have been reading https://wiki.netbsd.org/ports/evbarm/raspberry_pi/ but information is a bit confusing. "As of early 2024, NetBSD does not support the Raspberry Pi 5." Reading that I inmediatly discarded the Raspberry Pi 5 choice. Being realistic I think It does not work in NetBSD 10 now and I estimate it will not work well for perhaps some years. Life is short, I cannot wait and so I think RaspberryPi 4 should be my buying target. "NetBSD 10" "RPI4 general support (but there are issues)" Seems explained below. "RPI4 ethernet (Broadcom GENETv5) (but the man page for genet(4) is missing)" Can I be sure that ethernet will work fine and reliable? Network speed? "builtin bluetooth on RPI3 (RPI0W? RPI4?)" Does bluetooth work on the Pi4? "builtin WiFi on RPI0W, RPI3 and RPI4 - bwfm(4)" Does WIFI bwfm driver work as badly as in the ZeroW? Not relevant for my future use of the Pi 4 cause I will use it through ethernet but that will be a bonus, just curious. "RPI4 xhci does not work with a straight netbsd-10 install" I seems that below is the explanation. "RPI4 hardware rng does not work with a straight netbsd-10 install" I seems that below is the explanation. The following chapter is very confusing for me: "Issues and Workarounds" "RPI4 xhci" "With the netbsd-10 arm64.img on a RPI4 (most of them), the pci driver is missing and therefore xhci will not attach, so the USB ports will not work. One workaround is to switch to UEFI, but that leads to a 3GB memory limit and needing a monitor. Another is to add kernel config. One can also add the hardware rng. Adding the following to GENERIC64.local results in both working; you likely also need a dtb that includes the RNG. \todo Explain why this isn't in GENERIC64 or link to a PR. GENERIC64 bcm2838pcie* at fdt?# STB PCIe host controller bcm2838rng* at fdt? # RPI4 RNG There is some need to load firmware for the xhci driver, but apparently that works, once the above is added" Does it mean that using "traditional booting" you end with non working USB ports? Will you even end without keyboard? I mainly will use the Pi headless via ssh but need the keyboard in the first configuring steps. After switching to UEFI you will make USB ports work but 8 GB RapberryPi will be reduced to 3 GB only with no workaround? What do "needing a monitor" mean? Why? If the fix for USB and rng is recompiling the KERNEL, why is not enabled by default in the standard image? "RPI4 UEFI 3 GB" "To work around bugs in hardware (that may or may not be fixed in recent RPI4) and because not all OSes have workarounds, the UEFI firmware's default is to limit RAM to 3GB. NetBSD 10 can be used with more, so this needs to be configured in UEFI." That should be explained more in detail for newcomers. Last questions: Do GPIO pins work ok? Does I2C work? That is important for me cause I plan to read some sensors. Does HDMI output work or should I use serial console? traditional boot vs UEFI difference in this matter? What is your final opinion about NetBSD in that board? Are there better supported boards perhaps? Many thanks and sorry for so many questions, just I want to be sure that I am going to make a good and useful purchase. If I purchase a Rpi 4 instead of Rpi 5 to have NetBSD support and It does not work ok, it will be a absolute nonsense. I appreciate your work very much and your comments and advice will be welcome and very valuable for me. Thanks in advance. Ramiro.
Re: NetBSD vs. smartphones?
El 19 de marzo de 2024 16:55:49 CET, Brad Spencer escribió: >"John D. Baker" writes: > >> The smartphone I have can appear as any one of three types of devices >> when plugged into another computer system via USB: >> >> mass storage >> MTP device >> PTP device >> >> It is currently set to identify as a mass storage device. >> >> When I plug it into any of my NetBSD systems, NetBSD reports it as >> >> umodeswitch >> >> that the device is a mass storage device and that it is disabling >> umass support. >> >> If I reboot the system and drop into userconf to disable umodeswitch, >> the umass driver attaches and reports a device but that it is offline. >> It doesn't matter whether the phone is locked or unlocked at the time >> of attachment, the system reports the drive as offline. >> >> Without divulging information that might make my (or others) phone open to >> compromise, has anyone else dealt with a situation like this? > > >libmtp is in pkgsrc and I have use it and the associated utilities it >contains to talk MTP to a smartphone... a long time ago... but it did >work.. > > Hello, last weekend I was trying to make libmtp work but I couldn't. Next week end when I will have free time I will try again. Regards Ramiro
Re: mbrlabel question
El 3/15/24 a las 14:07, Michael van Elst escribió:
ea1...@gmail.com (Ramiro Aceves) writes:
The following options are available:
-f Force an update, even if there has been no change.
-q Performs operations in a quiet fashion.
-r In conjunction with -w, also update the on-disk label.
-s sector Specifies the logical sector number that has to be read from
the disk in order to find the MBR. Useful if the disk has
remapping drivers on it and the MBR is located in a non-
standard place. Defaults to 0.
-w Update the in-core label if it has been changed. See also -r.
I do not know the difference between the in-core and on-disk options,
what I should use and if I can break something with it.
The BSD partition information (aka "disklabel") exists in memory ("in-core")
and is also written to disk ("on-disk").
If you change only in-core, the change is temporary and volatile. When
the disk is no longer in use, or after a reboot, the changes are gone.
For permanent changes you need to write the on-disk label.
I.e. use
mbrlabel wd0
to show how the disklabel would look like, and use
mbrlabel -rw wd0
to actually change the disklabel permanently.
Many thanks Michael for the great explanation.
I issued mbrlabel -rw wd0 and worked as expected.
Regards.
Ramiro.
mbrlabel question
Hello, I have NetBSD installed in a Acer Aspire One laptop (MBR). Debian GNU Linux was installed first in this computer. I would like to mount the Linux partition inside NetBSD to copy some files using fuse-ext2 package. netbsd-acer# fdisk wd0 Disk: /dev/rwd0 NetBSD disklabel disk geometry: cylinders: 465141, heads: 16, sectors/track: 63 (1008 sectors/cylinder) total sectors: 468862128, bytes/sector: 512 BIOS disk geometry: cylinders: 1023, heads: 255, sectors/track: 63 (16065 sectors/cylinder) total sectors: 468862128 Partitions aligned to 2048 sector boundaries, offset 2048 Partition table: 0: Linux native (sysid 131) start 2048, size 307703808 (150246 MB, Cyls 0-19153/204/59) PBR is not bootable: All bytes are identical (0x00) 1: Linux swap or Prime or Solaris (sysid 130) start 307705856, size 7727104 (3773 MB, Cyls 19153/204/60-19634/202/24) PBR is not bootable: All bytes are identical (0x00) 2: NetBSD (sysid 169) start 315435008, size 153427120 (74916 MB, Cyls 19634/234/57-29185/80/63), Active 3: First active partition: 2 Drive serial number: 3245312946 (0xc16f8bb2) netbsd-acer# disklabel /dev/wd0 # /dev/wd0: type: unknown disk: wd label: fictious flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 465141 total sectors: 468862128 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 4 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a: 149253312 315435008 4.2BSD 0 0 0 # (Cyl. 312931*- 461000*) b: 4173808 464688320 swap # (Cyl. 461000*- 465140) c: 153427120 315435008 unused 0 0# (Cyl. 312931*- 465140) d: 468862128 0 unused 0 0# (Cyl. 0 - 465140) netbsd-acer# There is not an entry for the Linux ext4 partition and Linux swap partition. I discovered mbrlabel command: netbsd-acer# mbrlabel /dev/wd0 Found Linux Ext2 partition; size 307703808 (150246 MB), offset 2048 adding Linux Ext2 partition to slot e. Found swap partition; size 7727104 (3773 MB), offset 307705856 adding swap partition to slot f. Found 4.2BSD partition; size 153427120 (74915 MB), offset 315435008 skipping existing unused partition at slot c. 6 partitions: #sizeoffset fstype [fsize bsize cpg/sgs] a: 149253312 315435008 4.2BSD 0 0 0 # (Cyl. 312931*- 461000*) b: 4173808 464688320 swap # (Cyl. 461000*- 465140) c: 153427120 315435008 unused 0 0# (Cyl. 312931*- 465140) d: 468862128 0 unused 0 0# (Cyl. 0 - 465140) e: 307703808 2048 Linux Ext2 0 0# (Cyl. 2*- 305263*) f: 7727104 307705856 swap # (Cyl. 305263*- 312929*) Not updating disk label. netbsd-acer# I think this command can add the labels of the Linux and swap partitions as wd0e and wd0f, but reading the man page the subject is not clear to me. Before issuing the actual mbrlabel command I want to understand it well and be sure I am not going to break anything. The following options are available: -f Force an update, even if there has been no change. -q Performs operations in a quiet fashion. -r In conjunction with -w, also update the on-disk label. -s sector Specifies the logical sector number that has to be read from the disk in order to find the MBR. Useful if the disk has remapping drivers on it and the MBR is located in a non- standard place. Defaults to 0. -w Update the in-core label if it has been changed. See also -r. I do not know the difference between the in-core and on-disk options, what I should use and if I can break something with it. Thanks so much. Ramiro
Re: kern/57992: urtwn (and athn) driver lost network when WIFI router changes channel
El domingo, 3 de marzo de 2024, Michael van Elst escribió: > The following reply was made to PR kern/57992; it has been noted by GNATS
Re: Raspberry Pi Zero W almost useless (TL-WN725N very good!)
netbsd-raspa# ifconfig urtwn0 urtwn0: flags=0x8843 mtu 1500 ssid MiFibra-3422 nwkey 65536:"",0xc8000336c6e2b40b047cd2f5ef44,"","" powersave off bssid 60:8d:26:32:34:24 chan 1 address: e4:fa:c4:52:ac:4c media: IEEE802.11 autoselect (OFDM54 mode 11g) status: active inet6 fe80::e6fa:c4ff:fe52:ac4c%urtwn0/64 flags 0 scopeid 0x1 inet 192.168.1.230/24 broadcast 192.168.1.255 flags 0 netbsd-raspa# I have been downloading many times the same 3.6 GB file from the internet with no failures just for testing. I have made a CVS checkout of the base system source and pkgsrc source fine. Also have watched a 1h 30 m film using minidlna server in VLC over the local network with no failures at all. With bwfm driver that was just impossible. Great work! Regards. Hello, After a week using the driver I can say that it works well downloading files massively but I noticed I have lost ssh connection two times (both 04:00 to 05:00 in the morning when the system was not doing anything but sending 15s interval pings) (I left a 15 s interval ping script that logged it in a file).Also investigating the logs of my other Zero W with Raspbian I could see that at the precise time the network was lost in the NetBSD ZeroW, the Raspbian ZeroW recorded an association event to the router. Investigating further I noticed that they could be related to router WIFI channel change. "service network restart" a few times luckly restores connection but not always works. I tried also ifconfig urtwn0 up and down manually with no luck. "service wpa_supplicant" restart does not work either. I have systematically reproduced the problem forcing a WIFI channel change from the router and network is always lost after that. If you return the router to the original channel it returns working sometimes. (Raspbian ZeroW always negociate ok channel changes) Leaving the router at a fixed channel could be a "dirty" fix. A channel change seems to be not very frequent, so the rebooting script when network fails could make sense...I do not know. A bit tired of testing and out of ideas... Regards. Ramiro.
Re: Raspberry Pi Zero W almost useless (TL-WN725N very good!)
El 9/2/24 a las 15:20, Michael escribió: Hello, On Fri, 9 Feb 2024 06:25:56 +0100 Ramiro Aceves wrote: I have also the same problem that I had with the chineese 8188FTV, as soon I connect it to the raspberry pi it reboots inmediately. In the next reboot it works fine. It occurs the same in another Zero W that I own with Raspbian and a different power supply. So I doubt that the culprit is the power supply. The Zero W seems to be a very flaky device in terms of power supply. A powered hub should fix that, when a device is plugged directly into the raspberry pis usb (IIRC only 300mA is available) it can cause reboots. Oh yes, that would be a right technical fix for the problem but it's a bit of an aberration in terms of cost and size to use a powered HUB with its own power supply to fix a little thing like the ZeroW, you know ;-) Just use the hub to power the Pi. I used to do that wit the Pi1 and 2. have fun Michael Hello. Just want to share with you that TP-LINK TL-WN725N works very well with the raspberrypi Zero W. netbsd-raspa# uname -a NetBSD netbsd-raspa 10.0_RC3 NetBSD 10.0_RC3 (RPI) #0: Tue Jan 16 08:28:51 UTC 2024 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/RPI evbarm netbsd-raspa# netbsd-raspa# dmesg |grep urtwn [ 1.710793] urtwn0 at uhub0 port 1 [ 1.710793] urtwn0: Realtek (0x0bda) 802.11n NIC (0x8179), rev 2.00/0.00, addr 2 [ 1.770890] urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R, address e4:fa:c4:52:ac:4c [ 1.770890] urtwn0: 1 rx pipe, 2 tx pipes [ 1.740843] urtwn0 at uhub0 port 1 [ 1.740843] urtwn0: Realtek (0x0bda) 802.11n NIC (0x8179), rev 2.00/0.00, addr 2 [ 1.800940] urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R, address e4:fa:c4:52:ac:4c [ 1.800940] urtwn0: 1 rx pipe, 2 tx pipes netbsd-raspa# netbsd-raspa# ifconfig urtwn0 urtwn0: flags=0x8843 mtu 1500 ssid MiFibra-3422 nwkey 65536:"",0xc8000336c6e2b40b047cd2f5ef44,"","" powersave off bssid 60:8d:26:32:34:24 chan 1 address: e4:fa:c4:52:ac:4c media: IEEE802.11 autoselect (OFDM54 mode 11g) status: active inet6 fe80::e6fa:c4ff:fe52:ac4c%urtwn0/64 flags 0 scopeid 0x1 inet 192.168.1.230/24 broadcast 192.168.1.255 flags 0 netbsd-raspa# I have been downloading many times the same 3.6 GB file from the internet with no failures just for testing. I have made a CVS checkout of the base system source and pkgsrc source fine. Also have watched a 1h 30 m film using minidlna server in VLC over the local network with no failures at all. With bwfm driver that was just impossible. Great work! Regards.
Re: Raspberry Pi Zero W almost useless
El 9/2/24 a las 10:22, Michael van Elst escribió: ea1...@gmail.com (Ramiro Aceves) writes: Oh yes, that would be a right technical fix for the problem but it's a bit of an aberration in terms of cost and size to use a powered HUB with its own power supply to fix a little thing like the ZeroW, you know ;-) RPI0-3 models all have issues with power. Especially on the original RPI1 and RPI0 variants you shouldn't consider USB as being "hot pluggable". For the other models hot-plugging low power USB devices (i.e. using 100mA or less) should be fine. Unfortunately that might rule out things like many gaming keyboards and also some WLAN dongles. Thanks for the explanation Michael.
Re: Raspberry Pi Zero W almost useless
El 9/2/24 a las 15:20, Michael escribió: Hello, On Fri, 9 Feb 2024 06:25:56 +0100 Ramiro Aceves wrote: I have also the same problem that I had with the chineese 8188FTV, as soon I connect it to the raspberry pi it reboots inmediately. In the next reboot it works fine. It occurs the same in another Zero W that I own with Raspbian and a different power supply. So I doubt that the culprit is the power supply. The Zero W seems to be a very flaky device in terms of power supply. A powered hub should fix that, when a device is plugged directly into the raspberry pis usb (IIRC only 300mA is available) it can cause reboots. Oh yes, that would be a right technical fix for the problem but it's a bit of an aberration in terms of cost and size to use a powered HUB with its own power supply to fix a little thing like the ZeroW, you know ;-) Just use the hub to power the Pi. I used to do that wit the Pi1 and 2. have fun Michael It is a good idea, I never thought it could work. Many thanks
Re: Raspberry Pi Zero W almost useless
El 9/2/24 a las 1:41, Nat Sloss escribió: On Fri, 9 Feb 2024 06:05:46 Ramiro Aceves wrote: El 8/2/24 a las 16:48, Nat Sloss escribió: Hi, There's a little more required to add support for the FTV variant judging by changes made to openbsd's if_urtwn.c. There's new firware that needs to be uploaded to the device. And new power on and rssi functions (It seems judging by the changes they've made it some what is similar to the 8188EUS). I'm going to see if I can get one of these adaptors on ebay. I't will be awhile though before I try to get it working. This is best done on the new wifi stack, so I doubt it will get backported to -10. In the meantime if you search for an 8192eu variant that will work with -10 and -9. Best regards, Nat Hello Nat, Thanks for your great explanation, I understand. I then abandon the tests with the 8188FTV and wait for your improvements. They will be appreciated. I cannot fix anything, the driver world seems to be a hell! :-) I have just received today from Amazon a TL-WN725N USB WIFI adaptor and it just work in the raspberry Pi Zero W: [ 1.710793] urtwn0 at uhub0 port 1 [ 1.710793] urtwn0: Realtek (0x0bda) 802.11n NIC (0x8179), rev 2.00/0.00, addr 2 [ 1.770890] urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R, address e4:fa:c4:52:ac:4c [ 1.770890] urtwn0: 1 rx pipe, 2 tx pipes netbsd-raspa# ifconfig urtwn0: flags=0x8843 mtu 1500 ssid MiFibra-3422 nwkey 65536:"",0xc8000336c6e2b40b047cd2f5ef44,"","" powersave off bssid 60:8d:26:32:34:24 chan 1 address: e4:fa:c4:52:ac:4c media: IEEE802.11 autoselect (OFDM54 mode 11g) status: active inet6 fe80::e6fa:c4ff:fe52:ac4c%urtwn0/64 flags 0 scopeid 0x1 inet 192.168.1.230/24 broadcast 192.168.1.255 flags 0 lo0: flags=0x8049 mtu 33176 status: active inet6 ::1/128 flags 0x20 inet6 fe80::1%lo0/64 flags 0 scopeid 0x2 inet 127.0.0.1/8 flags 0 bwfm0: flags=0x8802 mtu 1500 ssid "" nwkey 65536:"","","","" powersave off address: b8:27:eb:ed:85:47 media: IEEE802.11 autoselect status: no network netbsd-raspa# I have also the same problem that I had with the chineese 8188FTV, as soon I connect it to the raspberry pi it reboots inmediately. In the next reboot it works fine. It occurs the same in another Zero W that I own with Raspbian and a different power supply. So I doubt that the culprit is the power supply. The Zero W seems to be a very flaky device in terms of power supply. A powered hub should fix that, when a device is plugged directly into the raspberry pis usb (IIRC only 300mA is available) it can cause reboots. Oh yes, that would be a right technical fix for the problem but it's a bit of an aberration in terms of cost and size to use a powered HUB with its own power supply to fix a little thing like the ZeroW, you know ;-) I am going to test it during several days to see if it works better than the flaky bwfm driver for the built in WIFI. I do not know if I have to disable the bwfm driver to avoid any interaction or I can leave it as is. You shouldn't have to disable bwfm(4) just dont bring up it's interface. Thanks, I will let it as is now. Many thanks for all, I'm learning a lot of things along the way. Regards. Ramiro. Thanks so much. Ramiro. Best regards, Nat
Re: Raspberry Pi Zero W almost useless
El 8/2/24 a las 16:48, Nat Sloss escribió: Hi, There's a little more required to add support for the FTV variant judging by changes made to openbsd's if_urtwn.c. There's new firware that needs to be uploaded to the device. And new power on and rssi functions (It seems judging by the changes they've made it some what is similar to the 8188EUS). I'm going to see if I can get one of these adaptors on ebay. I't will be awhile though before I try to get it working. This is best done on the new wifi stack, so I doubt it will get backported to -10. In the meantime if you search for an 8192eu variant that will work with -10 and -9. Best regards, Nat Hello Nat, Thanks for your great explanation, I understand. I then abandon the tests with the 8188FTV and wait for your improvements. They will be appreciated. I cannot fix anything, the driver world seems to be a hell! :-) I have just received today from Amazon a TL-WN725N USB WIFI adaptor and it just work in the raspberry Pi Zero W: [ 1.710793] urtwn0 at uhub0 port 1 [ 1.710793] urtwn0: Realtek (0x0bda) 802.11n NIC (0x8179), rev 2.00/0.00, addr 2 [ 1.770890] urtwn0: MAC/BB RTL8188EU, RF 6052 1T1R, address e4:fa:c4:52:ac:4c [ 1.770890] urtwn0: 1 rx pipe, 2 tx pipes netbsd-raspa# ifconfig urtwn0: flags=0x8843 mtu 1500 ssid MiFibra-3422 nwkey 65536:"",0xc8000336c6e2b40b047cd2f5ef44,"","" powersave off bssid 60:8d:26:32:34:24 chan 1 address: e4:fa:c4:52:ac:4c media: IEEE802.11 autoselect (OFDM54 mode 11g) status: active inet6 fe80::e6fa:c4ff:fe52:ac4c%urtwn0/64 flags 0 scopeid 0x1 inet 192.168.1.230/24 broadcast 192.168.1.255 flags 0 lo0: flags=0x8049 mtu 33176 status: active inet6 ::1/128 flags 0x20 inet6 fe80::1%lo0/64 flags 0 scopeid 0x2 inet 127.0.0.1/8 flags 0 bwfm0: flags=0x8802 mtu 1500 ssid "" nwkey 65536:"","","","" powersave off address: b8:27:eb:ed:85:47 media: IEEE802.11 autoselect status: no network netbsd-raspa# I have also the same problem that I had with the chineese 8188FTV, as soon I connect it to the raspberry pi it reboots inmediately. In the next reboot it works fine. It occurs the same in another Zero W that I own with Raspbian and a different power supply. So I doubt that the culprit is the power supply. The Zero W seems to be a very flaky device in terms of power supply. I am going to test it during several days to see if it works better than the flaky bwfm driver for the built in WIFI. I do not know if I have to disable the bwfm driver to avoid any interaction or I can leave it as is. Thanks so much. Ramiro.
Re: Raspberry Pi Zero W almost useless
Hello Martin, Thanks so much for the tip! Kernel compilation was ok now I rebooted with the new kernel and I could see the new urtwn0 interface! I wanted to test the interface but I have lost ssh connection (I am at work and the machine is at home, using ethernet driver). netbsd-nuc# ifconfig wm0: flags=0x8843 mtu 1500 capabilities=0x7ff80 capabilities=0x7ff80 capabilities=0x7ff80 enabled=0 ec_capabilities=0x17 ec_enabled=0x2 address: 1c:69:7a:0a:83:9d media: Ethernet autoselect (1000baseT full-duplex,flowcontrol,rxpause,txpause) status: active inet6 fe80::1e69:7aff:fe0a:839d%wm0/64 flags 0 scopeid 0x1 inet 192.168.1.200/24 broadcast 192.168.1.255 flags 0 urtwn0: flags=0x8802 mtu 1500 ssid "" powersave off address: 00:ff:38:30:32:2e media: IEEE802.11 autoselect status: no network lo0: flags=0x8049 mtu 33624 status: active inet6 ::1/128 flags 0x20 inet6 fe80::1%lo0/64 flags 0 scopeid 0x3 inet 127.0.0.1/8 flags 0 netbsd-nuc# ifconfig urtwn0 up ^[[B^[[A I logged in again and: NetBSD 10.0_RC3 (MYKERNEL) #0: Thu Feb 8 13:19:32 CET 2024 Welcome to NetBSD! This is a release candidate for NetBSD. Bug reports: https://www.NetBSD.org/support/send-pr.html Donations to the NetBSD Foundation: https://www.NetBSD.org/donations/ netbsd-nuc$ su Password: netbsd-nuc# ifconfig wm0: flags=0x8843 mtu 1500 capabilities=0x7ff80 capabilities=0x7ff80 capabilities=0x7ff80 enabled=0 ec_capabilities=0x17 ec_enabled=0x2 address: 1c:69:7a:0a:83:9d media: Ethernet autoselect (1000baseT full-duplex,flowcontrol,rxpause,txpause) status: active inet6 fe80::1e69:7aff:fe0a:839d%wm0/64 flags 0 scopeid 0x1 inet 192.168.1.200/24 broadcast 192.168.1.255 flags 0 ^C And it hangs there. Entering again: Welcome to NetBSD! This is a release candidate for NetBSD. Bug reports: https://www.NetBSD.org/support/send-pr.html Donations to the NetBSD Foundation: https://www.NetBSD.org/donations/ netbsd-nuc$ su Password: netbsd-nuc# dmesg | grep urtwn [ 9.228818] urtwn0 at uhub7 port 4 [ 9.228818] urtwn0: Realtek (0x0bda) 802.11n (0xf179), rev 2.00/0.00, addr 14 [ 9.318814] urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 00:ff:38:30:32:2e [ 9.318814] urtwn0: 1 rx pipe, 2 tx pipes [ 576.771445] urtwn0: autoconfiguration error: timeout waiting for firmware readiness [ 616.782378] urtwn0: cannot assign link-local address I will play at home in front of the machine. Thanks! Ramiro El jue, 8 feb 2024 a las 12:33, Martin Husemann () escribió: > > On Thu, Feb 08, 2024 at 12:06:51PM +0100, Ramiro Aceves wrote: > > Hello, > > > > > > I started playing tweaking usbdevs file in the Intel Nuc 8i7BEH > > NetBSD-10_RC3 amd64- I added the line: > > > > product REALTEK RTL8188FTV 0xf179 RTL8188FTV > > You need to regnerate a few files after changes in sys/dev/usbdevs. > Try something like: > > cd src/sys/dev/usb > make -f Makefile.usbdevs USETOOLS=never > > or use nbmake-$arch from $TOOLDIR instead and remove the USETOOLS=... part. > > Martin
Re: Raspberry Pi Zero W almost useless
Hello,
I started playing tweaking usbdevs file in the Intel Nuc 8i7BEH
NetBSD-10_RC3 amd64- I added the line:
product REALTEK RTL8188FTV 0xf179 RTL8188FTV
then tried adding a line in if_urtwn.c file just to see what happened:
#define URTWN_DEV(v,p) { { USB_VENDOR_##v, USB_PRODUCT_##v##_##p }, 0 }
#define URTWN_RTL8188E_DEV(v,p) \
{ { USB_VENDOR_##v, USB_PRODUCT_##v##_##p }, FLAG_RTL8188E }
#define URTWN_RTL8192EU_DEV(v,p) \
{ { USB_VENDOR_##v, USB_PRODUCT_##v##_##p }, FLAG_RTL8192E }
static const struct urtwn_dev {
struct usb_devnodev;
uint32_tflags;
#define FLAG_RTL8188E __BIT(0)
#define FLAG_RTL8192E __BIT(1)
} urtwn_devs[] = {
URTWN_DEV(ABOCOM, RTL8188CU_1),
...
...
URTWN_DEV(REALTEK, RTL8188FTV),
...
...
};
#undef URTWN_DEV
#undef URTWN_RTL8188E_DEV
#undef URTWN_RTL8192EU_DEV
...
...
Started kernel compilation and ended with error:
...
...
# compile MYKERNEL/if_urtwn.o
gcc -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -mno-avx
-msoft-float -mindirect-branch=thunk -mindirect-branch-register
-ffreestanding -fno-zero-initialized-in-bss
-fno-delete-null-pointer-checks -g -O2 -fno-omit-frame-pointer
-fstack-protector -Wstack-protector --param ssp-buffer-size=1
-fstack-usage -Wstack-usage=3584 -fno-strict-aliasing -fno-common
-std=gnu99 -Werror -Wall -Wno-main -Wno-format-zero-length
-Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes
-Wold-style-definition -Wswitch -Wshadow -Wcast-qual -Wwrite-strings
-Wno-unreachable-code -Wno-pointer-sign -Wno-attributes
-Wno-type-limits -Wextra -Wno-unused-parameter -Wold-style-definition
-Wno-sign-compare -Walloca -Wno-address-of-packed-member -Damd64
-Dx86_64 -I. -I../../../../external/mit/xen-include-public/dist/
-I../../../../external/bsd/libnv/dist
-I../../../../external/bsd/acpica/dist
-I../../../../../common/lib/libx86emu
-I../../../../../common/lib/libc/misc -I../../../../../common/include
-I../../../../arch -I../../../.. -nostdinc -DCOMPAT_UTILS
-D__XEN_INTERFACE_VERSION__=0x3020a -DCOMPAT_44 -D_KERNEL
-D_KERNEL_OPT -std=gnu99
-I../../../../lib/libkern/../../../common/lib/libc/quad
-I../../../../lib/libkern/../../../common/lib/libc/string
-I../../../../lib/libkern/../../../common/lib/libc/arch/x86_64/string
-I../../../../lib/libkern/../../../common/lib/libc/arch/x86_64/atomic
-I../../../../lib/libkern/../../../common/lib/libc/hash/sha3
-D_FORTIFY_SOURCE=2 -I../../../../external/isc/atheros_hal/dist
-I../../../../external/isc/atheros_hal/ic
-I../../../../../common/include
-I../../../../external/bsd/acpica/dist/include
-I../../../../external/bsd/libnv/dist -c
../../../../dev/usb/if_urtwn.c -o if_urtwn.o
../../../../dev/usb/if_urtwn.c:122:44: error:
'USB_PRODUCT_REALTEK_RTL8188FTV' undeclared here (not in a function);
did you mean 'USB_PRODUCT_REALTEK_RTL8188CTV'?
122 | #define URTWN_DEV(v,p) { { USB_VENDOR_##v, USB_PRODUCT_##v##_##p }, 0 }
|^~~~
../../../../dev/usb/if_urtwn.c:187:2: note: in expansion of macro 'URTWN_DEV'
187 | URTWN_DEV(REALTEK, RTL8188FTV),
| ^
../../../../dev/usb/if_urtwn.c:187:2: error: missing initializer for
field 'ud_product' of 'struct usb_devno'
[-Werror=missing-field-initializers]
In file included from ../../../../dev/usb/if_urtwn.c:72:
../../../../dev/usb/usbdi.h:234:11: note: 'ud_product' declared here
234 | uint16_t ud_product;
| ^~
cc1: all warnings being treated as errors
*** Error code 1
Stop.
make: stopped in /usr/src/sys/arch/amd64/compile/MYKERNEL
303.39 real 258.65 user27.95 sys
netbsd-nuc#
soon realized that usbdevs.h file was not automatically updated as I
thought and I did not found the #define line of the chip I added in
usbdevs file.
Reading usbdevs.h said that make -f Makefile.usbdevs should be executed:
netbsd-nuc# cd /usr/src/sys/dev/usb
netbsd-nuc# make -f Makefile.usbdevs
/bin/rm -f usbdevs.h usbdevs_data.h
/usr/src/tooldir.NetBSD-10.0_RC3-amd64/bin/nbawk -f
/usr/src/sys/dev/usb/../devlist2h.awk usbdevs
make: exec(/usr/src/tooldir.NetBSD-10.0_RC3-amd64/bin/nbawk) failed
(No such file or directory)
*** Error code 1
Stop.
make: stopped in /usr/src/sys/dev/usb
netbsd-nuc#
I am stuck now. Perhaps should I build everything, userland and
kernel? I think I am missing many things :-(
Thanks.
Ramiro.
El mié, 7 feb 2024 a las 19:21, Rhialto () escribió:
>
> On Wed 07 Feb 2024 at 10:44:04 +0100, Ramiro Aceves wrote:
> > The problem is to change /usr/src/dev/usb/if_urtwn.c without knowing
> > what I am exactly doing ;-)
>
> I don't know either, but I spot a list of these USB ids (starting with
>
> } urtwn_devs[] = {
> URTWN_DEV(ABOCOM, RTL8188CU_1),
> URTWN_DEV(ABOCOM, RTL8188CU_2),
> ). You could add yours to the list (it has 3 parts so maybe you have to
> apply some guesswork in which part it fits best).
Re: Xorg garbage mouse pointer in window edges and corners (NetBSD 10.0_RC3)
Thanks so much for the interesting findings, Olaf. I take notes. Ramiro. El dom, 4 feb 2024 a las 20:17, Rhialto () escribió: > > On Thu 01 Feb 2024 at 11:50:43 +0100, Ramiro Aceves wrote: > > # X -configure > > I noticed that with 10.0, this generates a different config file than > what's actually used! There is a difference in the mouse configuration. > > The actual mouse protocol that is used by default is > > Driver "ws" > > but it generates > > Driver "mouse" > > and I noticed that on my thinkpad, the touchpad scroll function was only > supported by the "ws" driver and not the "mouse" driver. > > Also these days it is apparently better to have > > Section "InputClass" > Identifier "system-keyboard" > MatchIsKeyboard "on" > Option "XkbOptions" > "ctrl:swapcaps,compose:menu,terminate:ctrl_alt_bksp" > EndSection > > than > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > Option "XkbOptions" > "ctrl:swapcaps,compose:menu,terminate:ctrl_alt_bksp" > EndSection > > which is the style that is generated. > And similar for the mouse: > > Section "InputClass" > Identifier "Mouse1" > MatchIsPointer "on" > Driver "ws" > Option "Protocol" "wsmouse" > Option "Device" "/dev/wsmouse" > Option "ZAxisMapping" "4 5 6 7" > EndSection > > -Olaf. > -- > ___ Olaf 'Rhialto' Seibert > \X/ There is no AI. There is just someone else's work. --I. Rose
Re: Raspberry Pi Zero W almost useless
Hello Lwazi, Thanks for the tip. I know how to recompile a kernel but I doubt I could do such modification in the source with chances of success without knowing the internals of driver programming. ;-) Only know the basics of C. I have been watching /usr/src/dev/usb/usbdevs and it seems easy to change. Then it says that usbdevs.h will be regenerated automatically. I believe that I have to add the following line with the RTL8188FTV product ID (Realtek vendor ID is ok in the usbdevs file): product REALTEK RTL8188FTV 0xf179 Realtek RTL8188FTV The problem is to change /usr/src/dev/usb/if_urtwn.c without knowing what I am exactly doing ;-) Another thing I am thinking about is the firmware... Too few chances of success, I think. Thanks. Ramiro El mar, 6 feb 2024 a las 19:27, Lwazi Dube () escribió: > > On Mon, 5 Feb 2024 at 06:51, Ramiro Aceves wrote: >> >> >> Hello, >> I bought two of other seller, rtl8188 but I think it is not supported. >> I have two problems. As soon as I connect it the raspberry inmediatly >> reboots. I think it has something to do with some inrush current. In >> raspbian also it reboots inmediatley. >> >> Once the system reboots, it finds the dongle but cannot be configured: >> Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7408840] ugen0 at uhub0 port 1 >> Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7408840] ugen0: Realtek >> (0x0bda) 802.11n (0xf179), rev 2.00/0.00, addr 2 >> Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7408840] uhub0: >> autoconfiguration error: illegal enable change, port 1 >> Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7408840] swwdog0: software >> watchdog initialized >> Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7609300] WARNING: 1 error >> while detecting hardware; check system log. >> >> I have googled and perhaps it is rtl8188FTV, I think it is not >> supported by the driver. >> > The RTL8188FTV product id seems to be missing in usbdevs and if_urtwn.c. You > need to add the id and rebuild the kernel before you test.
Re: Raspberry Pi Zero W almost useless
El jue, 25 ene 2024 a las 11:28, Matthew Widup () escribió: > > I use one of these > https://www.ebay.com/itm/113774031117?mkcid=16=1=711-127632-2357-0=HZuLHORZQWm=4429486=rkGEi8qyQi6=_ver=artemis=COPY > > which is nearly as small as possible, and ridiculously cheap. I don't > normally advocate buying cheap things. > > Granted I don't use it with a Pi. I use it with my Pinebook Pro (actually > multiples of them). But it should work for the Pi just the same. > Hello, I bought two of other seller, rtl8188 but I think it is not supported. I have two problems. As soon as I connect it the raspberry inmediatly reboots. I think it has something to do with some inrush current. In raspbian also it reboots inmediatley. Once the system reboots, it finds the dongle but cannot be configured: Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.2002810] ld0: 60874 MB, 7760 cyl, 255 head, 63 sec, 512 bytes/sect x 124669952 sectors Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.2002810] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.3004040] sdmmc1: 4-bit width, 50.000 MHz Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.3004040] bwfm0 at sdmmc1 function 1 Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.3104370] (manufacturer 0x2d0, product 0xa9a6) at sdmmc1 function 2 not configured Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7408840] ugen0 at uhub0 port 1 Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7408840] ugen0: Realtek (0x0bda) 802.11n (0xf179), rev 2.00/0.00, addr 2 Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7408840] uhub0: autoconfiguration error: illegal enable change, port 1 Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7408840] swwdog0: software watchdog initialized Feb 4 21:58:55 netbsd-raspa /netbsd: [ 1.7609300] WARNING: 1 error while detecting hardware; check system log. I have googled and perhaps it is rtl8188FTV, I think it is not supported by the driver. Thanks.
Re: Xorg garbage mouse pointer in window edges and corners (NetBSD 10.0_RC3)
El 1/2/24 a las 15:56, RVP escribió: On Thu, 1 Feb 2024, Ramiro Aceves wrote: I am not using any xorg.conf file. Ithink I will have to generate w new one with: # X -configure And place in /etc/X11/xorg.conf then add the option Option "SWcursor" "on" You don't need the whole thing; just a fragment like this will do: ``` $ cat /etc/X11/xorg.conf.d/modesetting.conf Section "Device" Identifier "Card0" Driver "modesetting" Option "SWcursor" "on" EndSection $ ``` -RVP Hello RVP, Thanks for the tip. I found that I was indeed using a xorg.conf file product of old experiments: netbsd-nuc# cat xorg.conf-backup-modesetting Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/X11R7/lib/modules" FontPath "/usr/X11R7/lib/X11/fonts/misc/" FontPath "/usr/X11R7/lib/X11/fonts/TTF/" FontPath "/usr/X11R7/lib/X11/fonts/Type1/" FontPath "/usr/X11R7/lib/X11/fonts/75dpi/" FontPath "/usr/X11R7/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "dri" Load "dri2" Load "glx" #Load "shadow" EndSection Section "DRI" Group "wheel" Mode 0660 EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "wsmouse" Option "Device" "/dev/wsmouse" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" Identifier "Card0" #Driver "wsfb" Driver "modesetting" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection If I use no xorg.conf file at all, it picks intel driver and there are no problems in window edges and corners. If I use your config file it works fine!, no problems on the corners and edges and modesetting driver is used: netbsd-nuc# cat /etc/X11/xorg.conf Section "Device" Identifier "Card0" Driver "modesetting" Option "SWcursor" "on" EndSection Thanks so much. Ramiro.
Re: Xorg garbage mouse pointer in window edges and corners (NetBSD 10.0_RC3)
El jue, 1 feb 2024 a las 11:38, RVP () escribió: > > On Thu, 1 Feb 2024, Ramiro Aceves wrote: > > > When I place mouse pointer over the edges or corners of xorg windows > > to resize them (same XFCE and CTWM), mouse pointer icon starts to > > show garbage drawing until it ends well shaped after 1 or 2 seconds. > > > > If you run the `modesetting` Xorg display-driver, you can try: > > Option "SWcursor" "on" > > -RVP Hello RVP, many thanks for the tip. I am at work now and I cannot test until arrive home. Yes I am using modesetting driver. If I recall correctly, I am not using any xorg.conf file. Ithink I will have to generate w new one with: # X -configure And place in /etc/X11/xorg.conf then add the option Option "SWcursor" "on" is not it? Just to have things clear in my mind before trying. Thanks. Regards.
Re: Xorg garbage mouse pointer in window edges and corners (NetBSD 10.0_RC3)
El jue, 1 feb 2024 a las 11:38, RVP () escribió: > > On Thu, 1 Feb 2024, Ramiro Aceves wrote: > > > When I place mouse pointer over the edges or corners of xorg windows > > to resize them (same XFCE and CTWM), mouse pointer icon starts to > > show garbage drawing until it ends well shaped after 1 or 2 seconds. > > > > If you run the `modesetting` Xorg display-driver, you can try: > > Option "SWcursor" "on" > > -RVP Hello RVP, many thanks for the tip. I am at work now and I cannot test until arrive home. Yes I am using modesetting driver. If I recall correctly, I am not using any xorg.conf file. Ithink I will have to generate w new one with: # X -configure And place in /etc/X11/xorg.conf then add the option:
Xorg garbage mouse pointer in window edges and corners (NetBSD 10.0_RC3)
Hello, I have been experiencing this problem since I installed NeBSD on my intel Nuc 8i7BEH (Same 10.0_RC1, RC2 and RC3). When I place mouse pointer over the edges or corners of xorg windows to resize them (same XFCE and CTWM), mouse pointer icon starts to show garbage drawing until it ends well shaped after 1 or 2 seconds. I can live with it but it is very annoying to resize windows. I do not know if I have to fill a bug PR. Thanks in advance. Ramiro.
Re: Raspberry Pi Zero W almost useless
Hello again: El 27/1/24 a las 13:29, Bartek Krawczyk escribió: On 25.01.2024 11:05, Ramiro Aceves wrote: I see that WIFI bwfm driver works the same as bad as in 10.0_RC1. I have read that WIFI drivers are not very stable but I do not know whether what I am experiencing is normal or not. My system is doing nearly "nothing", at 30 minutes interval cron runs a wget command to download a little 2 byte file from https://ipv4.cloudns.net/ just to inform the DDNS system of my actual IP address. From time to time I loose network and I cannot longer have ssh access. In order to overcome that, I wrote a service that reboots the operating system when network does not work (better than nothing). The service registers in a file the uptime just before issuing the reboot command: Earlier I experienced the same on a Raspberry PI 3 however not sure if it was as often as every 30mins. https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=57308 Hi again. I have tried to restart wpa_supplicant service but it does not resurrect network. "bwfm: could not set mpc" message goes out of the kernel. I have transcribed manually the information on the TV screen: netbsd-raspa# service wpa_supplicant restart Stopping wpa_supplicant. Jan 17 16:15:17 netbsd-raspa wpa_supplicant[293]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address Starting wpa_supplicant. netbsd-raspa#Jan 27 16:15:08 netbsd-raspa wpa_supplicant[1304]: ioctl[SIOCG80211, op=16, arg_len=0:Inappropiate ioctl for device. [687.4366422] bwfm: could not set mpc Thanks Ramiro.
Re: Raspberry Pi Zero W almost useless
El 27/1/24 a las 13:29, Bartek Krawczyk escribió: On 25.01.2024 11:05, Ramiro Aceves wrote: I see that WIFI bwfm driver works the same as bad as in 10.0_RC1. I have read that WIFI drivers are not very stable but I do not know whether what I am experiencing is normal or not. My system is doing nearly "nothing", at 30 minutes interval cron runs a wget command to download a little 2 byte file from https://ipv4.cloudns.net/ just to inform the DDNS system of my actual IP address. From time to time I loose network and I cannot longer have ssh access. In order to overcome that, I wrote a service that reboots the operating system when network does not work (better than nothing). The service registers in a file the uptime just before issuing the reboot command: Earlier I experienced the same on a Raspberry PI 3 however not sure if it was as often as every 30mins. https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=57308 Thanks Bartek for the tips. Here I do not use dhcpcd, I use static IP address. I think in the past I tried to reload wpasupplicant service with no luck but I do not remember well. I think I can try it know. I am going to try "service wpa_supplicant restart" trick and see what happens. Ramiro.
Re: Raspberry Pi Zero W almost useless
El 25/1/24 a las 11:28, Matthew Widup escribió: I use one of these https://www.ebay.com/itm/113774031117?mkcid=16=1=711-127632-2357-0=HZuLHORZQWm=4429486=rkGEi8qyQi6=_ver=artemis=COPY which is nearly as small as possible, and ridiculously cheap. I don't normally advocate buying cheap things. Granted I don't use it with a Pi. I use it with my Pinebook Pro (actually multiples of them). But it should work for the Pi just the same. Hello Matthew, Thanks for the suggested wifi interface. I have ordered two of them (from another seller with lower shipping charges) and we'll see what happens. They are so cheap that I think it makes sense to try. The only problem is that Zero W has only 1 USB port and I will not be able to connect a keyboard at the same time. I normally do not use the keyboard, I think I will be able to do config it. Thanks so much. Ramiro. Sent with Proton Mail secure email. On Thursday, January 25th, 2024 at 4:05 AM, Ramiro Aceves wrote: Hello, I have upgraded my raspberry pi Zero W board operating system to NetBSD-10.0_RC3 using sysupgrade for the sets. Previously I manually upgraded the kernel, firmware and dtbs (a bit tricky). No problem at all with that, but do you know if there are plans in the future to do kernel, dtb and firmware easier upgrades without having to vndconfig the installation image, mounting it and copy manually the files? Just curious... I see that WIFI bwfm driver works the same as bad as in 10.0_RC1. I have read that WIFI drivers are not very stable but I do not know whether what I am experiencing is normal or not. My system is doing nearly "nothing", at 30 minutes interval cron runs a wget command to download a little 2 byte file from https://ipv4.cloudns.net/ just to inform the DDNS system of my actual IP address. From time to time I loose network and I cannot longer have ssh access. In order to overcome that, I wrote a service that reboots the operating system when network does not work (better than nothing). The service registers in a file the uptime just before issuing the reboot command: netbsd-raspa# cat /root/network_conn_test.log |grep day 4:01AM up 3 days, 12:10, 0 users, load averages: 0.00, 0.00, 0.00 12:43PM up 4 days, 23:43, 1 user, load averages: 1.00, 1.00, 0.91 4:01AM up 1 day, 15:18, 0 users, load averages: 0.00, 0.00, 0.00 11:28AM up 1 day, 7:27, 1 user, load averages: 0.24, 0.32, 0.16 2:01AM up 2 days, 22:33, 0 users, load averages: 0.00, 0.02, 0.00 3:01AM up 1 day, 1 hr, 0 users, load averages: 0.03, 0.05, 0.02 5:01AM up 2 days, 2 hrs, 0 users, load averages: 0.00, 0.00, 0.00 2:01AM up 2 days, 20:59, 0 users, load averages: 0.00, 0.00, 0.00 2:01AM up 1 day, 0 users, load averages: 0.00, 0.00, 0.00 5:01AM up 4 days, 2:59, 0 users, load averages: 0.00, 0.00, 0.04 5:02AM up 2 days, 0 users, load averages: 0.00, 0.00, 0.00 2:43PM up 1 day, 9:41, 0 users, load averages: 0.02, 0.05, 0.02 4:01AM up 2 days, 10:57, 0 users, load averages: 0.00, 0.00, 0.00 9:25AM up 1 day, 5:23, 0 users, load averages: 0.08, 0.11, 0.05 4:01AM up 3 days, 11:27, 0 users, load averages: 0.00, 0.00, 0.00 2:01AM up 2 days, 22 hrs, 0 users, load averages: 0.00, 0.00, 0.00 5:01AM up 2 days, 3 hrs, 0 users, load averages: 0.00, 0.00, 0.00 12:01PM up 1 day, 7:49, 1 user, load averages: 0.10, 0.14, 0.13 System do not last more than 4 days without loosing network. Sometimes it breaks in a few minutes: netbsd-raspa# cat /root/network_conn_test.log |grep min 3:28AM up 2 mins, 0 users, load averages: 0.38, 0.24, 0.10 9:30AM up 5 mins, 1 user, load averages: 0.03, 0.08, 0.04 12:18PM up 49 mins, 0 users, load averages: 0.00, 0.00, 0.00 4:11AM up 2 mins, 0 users, load averages: 0.20, 0.16, 0.07 12:04PM up 3 mins, 1 user, load averages: 0.23, 0.21, 0.09 1:28PM up 20 mins, 1 user, load averages: 0.22, 0.40, 0.25 netbsd-raspa# It is difficult to download big files from the internet. If you try to download a for example 1 GB file, it is very probable that it breaks before 1/3 of the file transfer. That can be solved using wget -c option but it is very annoying. It is very difficult to find a useful task for this board using NetBSD. For example I would like to setup a minidlna server to watch films but I have done that and it breaks after a few minutes. If you setup a lighttpd WEB server it will be anoying for the user if it reboots on the middle of WEB surfing... I do not see anything useful in dmesg. Only the messages that follow the forced reboot issued by mi service: ... ... [ 1.410723] bwfm0: Found NVRAM file: brcmfmac43430-sdio.raspberrypi,model-zero-w.txt [ 1.410723] bwfm0: CLM file default: brcmfmac43430-sdio.clm_blob [ 1.410723] bwfm0: CLM file model-spec: brcmfmac43430-sdio.raspberrypi,model-zero-w.clm_blob [ 3.132473] bwfm0: CHIPACTIVE [ 3.232559] bwfm0: address b8:27:eb:ed:85:47 [ 3.232559] bwfm0: wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f [ 14.405464] wsdisplay0: screen 4 added (default, vt100
Raspberry Pi Zero W almost useless
Hello, I have upgraded my raspberry pi Zero W board operating system to NetBSD-10.0_RC3 using sysupgrade for the sets. Previously I manually upgraded the kernel, firmware and dtbs (a bit tricky). No problem at all with that, but do you know if there are plans in the future to do kernel, dtb and firmware easier upgrades without having to vndconfig the installation image, mounting it and copy manually the files? Just curious... I see that WIFI bwfm driver works the same as bad as in 10.0_RC1. I have read that WIFI drivers are not very stable but I do not know whether what I am experiencing is normal or not. My system is doing nearly "nothing", at 30 minutes interval cron runs a wget command to download a little 2 byte file from https://ipv4.cloudns.net/ just to inform the DDNS system of my actual IP address. From time to time I loose network and I cannot longer have ssh access. In order to overcome that, I wrote a service that reboots the operating system when network does not work (better than nothing). The service registers in a file the uptime just before issuing the reboot command: netbsd-raspa# cat /root/network_conn_test.log |grep day 4:01AM up 3 days, 12:10, 0 users, load averages: 0.00, 0.00, 0.00 12:43PM up 4 days, 23:43, 1 user, load averages: 1.00, 1.00, 0.91 4:01AM up 1 day, 15:18, 0 users, load averages: 0.00, 0.00, 0.00 11:28AM up 1 day, 7:27, 1 user, load averages: 0.24, 0.32, 0.16 2:01AM up 2 days, 22:33, 0 users, load averages: 0.00, 0.02, 0.00 3:01AM up 1 day, 1 hr, 0 users, load averages: 0.03, 0.05, 0.02 5:01AM up 2 days, 2 hrs, 0 users, load averages: 0.00, 0.00, 0.00 2:01AM up 2 days, 20:59, 0 users, load averages: 0.00, 0.00, 0.00 2:01AM up 1 day, 0 users, load averages: 0.00, 0.00, 0.00 5:01AM up 4 days, 2:59, 0 users, load averages: 0.00, 0.00, 0.04 5:02AM up 2 days, 0 users, load averages: 0.00, 0.00, 0.00 2:43PM up 1 day, 9:41, 0 users, load averages: 0.02, 0.05, 0.02 4:01AM up 2 days, 10:57, 0 users, load averages: 0.00, 0.00, 0.00 9:25AM up 1 day, 5:23, 0 users, load averages: 0.08, 0.11, 0.05 4:01AM up 3 days, 11:27, 0 users, load averages: 0.00, 0.00, 0.00 2:01AM up 2 days, 22 hrs, 0 users, load averages: 0.00, 0.00, 0.00 5:01AM up 2 days, 3 hrs, 0 users, load averages: 0.00, 0.00, 0.00 12:01PM up 1 day, 7:49, 1 user, load averages: 0.10, 0.14, 0.13 System do not last more than 4 days without loosing network. Sometimes it breaks in a few minutes: netbsd-raspa# cat /root/network_conn_test.log |grep min 3:28AM up 2 mins, 0 users, load averages: 0.38, 0.24, 0.10 9:30AM up 5 mins, 1 user, load averages: 0.03, 0.08, 0.04 12:18PM up 49 mins, 0 users, load averages: 0.00, 0.00, 0.00 4:11AM up 2 mins, 0 users, load averages: 0.20, 0.16, 0.07 12:04PM up 3 mins, 1 user, load averages: 0.23, 0.21, 0.09 1:28PM up 20 mins, 1 user, load averages: 0.22, 0.40, 0.25 netbsd-raspa# It is difficult to download big files from the internet. If you try to download a for example 1 GB file, it is very probable that it breaks before 1/3 of the file transfer. That can be solved using wget -c option but it is very annoying. It is very difficult to find a useful task for this board using NetBSD. For example I would like to setup a minidlna server to watch films but I have done that and it breaks after a few minutes. If you setup a lighttpd WEB server it will be anoying for the user if it reboots on the middle of WEB surfing... I do not see anything useful in dmesg. Only the messages that follow the forced reboot issued by mi service: ... ... [ 1.410723] bwfm0: Found NVRAM file: brcmfmac43430-sdio.raspberrypi,model-zero-w.txt [ 1.410723] bwfm0: CLM file default:brcmfmac43430-sdio.clm_blob [ 1.410723] bwfm0: CLM file model-spec: brcmfmac43430-sdio.raspberrypi,model-zero-w.clm_blob [ 3.132473] bwfm0: CHIPACTIVE [ 3.232559] bwfm0: address b8:27:eb:ed:85:47 [ 3.232559] bwfm0: wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f [14.405464] wsdisplay0: screen 4 added (default, vt100 emulation) [ 1197.386358] syncing disks... done [ 1197.436478] unmounting file systems... [ 1197.436478] unmounted tmpfs on /var/shm type tmpfs [ 1197.436478] unmounted procfs on /proc type procfs [ 1197.436478] unmounted ptyfs on /dev/pts type ptyfs [ 1197.436478] unmounted /dev/ld0e on /boot type msdos [ 1.00] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, [ 1.00] 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, [ 1.00] 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, [ 1.00] 2024 [ 1.00] The NetBSD Foundation, Inc. All rights reserved. [ 1.00] Copyright (c) 1982, 1986, 1989, 1991, 1993 [ 1.00] The Regents of the University of California. All rights reserved. [ 1.00] NetBSD 10.0_RC3 (RPI) #0: Tue Jan 16 08:28:51 UTC 2024 [ 1.00]
Re: Why I screwed up my NetBSD system?
On 12/8/23 18:59, Alan Corey wrote: You guys have too much fun. Yes! On Fri, Dec 8, 2023, 11:38 AM Manuel Bouyer <mailto:bou...@antioche.eu.org>> wrote: On Fri, Dec 08, 2023 at 05:03:21PM +0100, Ramiro Aceves wrote: > [...] > What was my mistake? Sorry for the lack of detail but is what I can recall > from my poor memory. Just want to know what I did wrong and never do it in > the future. NetBSD 10.99 to 10.0_RC1 is not an upgrade but a downgrade actually. This is not supported. What probably happended is that some 10.99 dynamic libraries were still around (because they have a higher number than their 10.0 counterpart), but a 10.0 kernel would not support them Thanks so much Manuel for the explanation. I misunderstood releases. http://www.netbsd.org/images/graphs/release-graph.gif After seeing that graph everything is more clear to me. Thanks. Ramiro. -- Manuel Bouyer mailto:bou...@antioche.eu.org>> NetBSD: 26 ans d'experience feront toujours la difference --
Why I screwed up my NetBSD system?
Hello, Yesterday I think I did something weird. I was running NetBSD 10.99 in my raspberrypi Zero W. I decided to do an upgrade to NetBSD 10-RC1 using sysupgrade utility. I configured sysupgrade configuration file to download the sets from: https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.0_RC1/evbarm-earmv6hf/ # sysupgrade fetch I downloaded the sets. As there is no automated way of upgrading dtb files, firmware and kernel, I downloaded this: https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.0_RC1/evbarm-earmv6hf/binary/gzimg/rpi.img.gz I gunziped and vndconfig the image and mounted the MSDOS partition just to extract the kernel, firmware and rest of stuff, and I put everything in /boot. I did someting like cp -a * /boot. I inspected /boot directory and everything apeared to be fine in place. # sysupgrade kernel (I think it puts a kernel in / but raspberry pi does not use that. # sysupgrade modules # reboot System rebooted from the RC1 kernel but I could not access the RPI from ssh anymore, and I connected a TV set to see what happened and rebooted again. System started but wpasupplicant sent an error, something like failed a system call. I could not make the network work. # sysupgrade sets Sets where untared ok in place. # sysupgrade etcupdate just fine if I recalled correctly. # sysupgrade postinstall Many errors that I do not recall. # reboot reboot command did not work, shutdown -p now did not work. I did /rescue/reboot and paniced. I rebooted the system removing power supply. The kernel started and showed the usual booting testing drivers. It stopped with init process paniced and kernel debug console appeared. I broke every think and could not know how to fix it. I extracted SD card and mounted in other computer. I think there were many "core dump" files in / I copyied useful files (etc, var, home, root, just important things) in my Intel Nuc 10-RC1 NetBSD system and installed a fresh 10-RC1 system into the SD. Now raspberrypi it is working fine in NetBSD 10RC1 after restoring everything. What was my mistake? Sorry for the lack of detail but is what I can recall from my poor memory. Just want to know what I did wrong and never do it in the future. Thanks so much. Ramiro.
Re: I do not understand modstat command (bwfm driver)
> > Just curious: why I cannot see bwfm driver in modstat output? > > > > Thanks. > > Ramiro. > > It's not a "module". Thanks so much Jonathan. Regards.
Raspberrypi ZeroW activity LED does not blink
Hello, I am using NetBSD on my raspberrypi Zero W. raspa-netbsd# uname -a NetBSD raspa-netbsd 10.99.9 NetBSD 10.99.9 (RPI) #0: Wed Sep 27 09:44:10 UTC 2023 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/RPI evbarm Just curious, activity LED on the PCB does not blink on SD card activity like Raspbian Linux does. Is that feature missing? Thanks so much. Ramiro.
I do not understand modstat command (bwfm driver)
Hello, I am using NetBSD on my RaspberryPi Zero W board. raspa-netbsd# uname -a NetBSD raspa-netbsd 10.99.9 NetBSD 10.99.9 (RPI) #0: Wed Sep 27 09:44:10 UTC 2023 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/evbarm/compile/RPI I am using the bwfm wireless driver: raspa-netbsd# ifconfig lo0: flags=0x8049 mtu 33176 status: active inet6 ::1/128 flags 0x20 inet6 fe80::1%lo0/64 flags 0 scopeid 0x1 inet 127.0.0.1/8 flags 0 bwfm0: flags=0x8843 mtu 1500 ssid MiFibra-3422 nwkey 65536:"",0x4a97636f1d8c7a070d1fe6e79f88cada,"","" powersave off bssid 60:8d:26:32:34:24 chan 1 address: b8:27:eb:ed:85:47 media: IEEE802.11 autoselect (HT mode 11ng) status: active inet6 fe80::ba27:ebff:feed:8547%bwfm0/64 flags 0 scopeid 0x2 inet 192.168.1.230/24 broadcast 192.168.1.255 flags 0 raspa-netbsd# raspa-netbsd# modstat NAME CLASSSOURCE FLAG REFSSIZE REQUIRES adiantum misc builtin -0 - aes,chacha aes misc builtin -2 - - aes_ccm misc builtin -0 - aes aio misc builtin -0 - - au8522 driver builtin -1 - i2cexec audiodriver builtin -3 - - auvitek driver builtin -0 - au8522,xc5k blake2s misc builtin -0 - - blowfish misc builtin -2 - - bpf driver builtin -1 - bpf_filter bpf_filter misc builtin -2 - - bufq_disksortbufq builtin -0 - - bufq_fcfsbufq builtin -2 - - bufq_priocscan bufq builtin -0 - - camellia misc builtin -1 - - cast128 misc builtin -1 - - cd9660 vfs builtin -0 - - cgd driver builtin -0 - blowfish,des,dk_subr,bufq_fcfs chacha misc builtin -1 - - cir driver builtin -1 - ir clockctl driver builtin -0 - - compat_100 exec builtin -2 - - compat_43exec builtin -1 - compat_sysctl_09_43,compat_util,compat_60 compat_60exec builtin -2 - compat_70 compat_70exec builtin -1 - compat_80 compat_80exec builtin -3 - compat_90 compat_90exec builtin -2 - compat_100 compat_netbsd32 exec builtin -9 - ksem,compat_util,exec_elf32 compat_netbsd32_100 exec builtin -1 - compat_netbsd32,compat_100 compat_netbsd32_43 exec builtin -0 - compat_netbsd32,compat_43 compat_netbsd32_60 exec builtin -0 - compat_netbsd32_80,compat_60 compat_netbsd32_80 exec builtin -1 - compat_netbsd32_90,compat_80 compat_netbsd32_90 exec builtin -1 - compat_netbsd32_100,compat_90 compat_netbsd32_coredump misc builtin -0 - compat_netbsd32,compat_netbsd32_ptrace,coredump compat_netbsd32_mqueue exec builtin -0 - mqueue,compat_netbsd32 compat_netbsd32_nfssrv exec builtin -0 - nfsserver,compat_netbsd32 compat_netbsd32_ptrace exec builtin -1 - compat_netbsd32,ptrace_common compat_netbsd32_quotaexec builtin -0 - compat_netbsd32 compat_netbsd32_raid exec builtin -0 - raid,compat_netbsd32 compat_netbsd32_sysvipc exec builtin -0 - compat_netbsd32,sysv_ipc compat_raid_80 exec builtin -0 - raid,compat_80 compat_sysctl_09_43 exec builtin -1 - - compat_util misc builtin -2 - - cons driver builtin -0 - - coredump misc builtin -1 - - crypto driver builtin -0 - opencrypto des misc builtin -2 - - dk_subr misc builtin -3 - - drvctl driver builtin -0 - - dtv driver builtin -0 - - dtv_math misc builtin -1 - - efs vfs builtin -0 - - emdtvdriver builtin -0 - cir,lg3303,xc3028 exec_aoutexec builtin -0 - - exec_elf32 exec
upgrading a system to NetBSD 10 using sysinst vs sysupgrade
Hello, I have some doubts about the NetBSD upgrading procedure, now that we are closer to NetBSD release I want to do things right. I installed NetBSD 9.3 in my Intel Nuc 8i7 but I had some problems to get Xorg Modesetting driver working so I decided to upgrade the system to NetBSD-Current using sysutils/sysupgrade program. Everything went ok in Xorg as I told in this mailing list. Days after, I was trying to compile some programs and decided to install the Xorg source set. I run #sysinst program from the running system to install several sets. Also by mistake I installed kernel, base (I believed that they will be uninstalled if not marked selected on the screen). But I also installed the /etc set over my /etc files and everything screwed up :-) I believed that the /etc set would mix carefully with the existing files as sysupgrade did but it simply copied over them, deleting configuration files. Of course /etc/rc.conf was destroyed. :-) After reading the chapter "rescuing a system" could fix it. Great! http://www.netbsd.org/docs/misc/index.html#why-single-user It was a good learning experience, indeed. Now uname says I am at NetBSD 10.0_RC1. Reading the NetBSD Guide I see that upgrades can be done using sysinst (a bit more confortable than sysupgrade) but says that: " To do the upgrade, you must have some form of bootable media (CD-ROM, USB drive, floppy, etc.) available and at least the base and kern distribution sets. " My doubt is: can sysint be executed from the running system and upgraded from the internet using the configured system network? Or upgrade must be run from the bootable media? Thanks in advance. Ramiro.
(solved) Re: rc.local nightmare
On 10/30/23 08:25, Michael van Elst wrote: ea1...@gmail.com (Ramiro Aceves) writes: My script says on the console "Network connectivity to $TARGET is OK." several times before the script dies. So ping works fine. (I have set INTERVAL=3 seconds just to speed things up during testing. Your script shouldn't create output from a background process. When booting, output is piped through a logging process, and when that exits, the next output will abort your process. Thanks so much Michael for the tips. It is working now redirecting stdout and stderr. Now that it is working and I know the reason of what was happening, it is time to learn how to make a simple NetBSD service. nohup doesn't help, it only redirects terminal output. Ideally you should not print anything directly in a background process but write a log file (or use logger / syslog). To avoid any accidential problem, you should also redirect all three standard handles (e.g. to /dev/null). N.B. the connectivity check is a bit sensitive. I suggest to probe with more than 1 packet and to also set a deadline (-w) which allows for one extra second, e.g. ping -n -c 3 -w 4. Thanks for that tip! Ramiro
(solved) Re: rc.local nightmare
On 10/30/23 07:50, RVP wrote: On Sun, 29 Oct 2023, Ramiro Aceves wrote: if [ -x /root/nettest ]; then /root/nettest & fi Many thanks RVP for the superb explanation. It works fine now. If I had had to guess it myself, I think I would never have discovered it. Many thanks! Ramiro. Redirect the output of your script somewhere and then it shoould be OK: ``` if [ -x /root/nettest ]; then /root/nettest >/root/nettest.log 2>&1 & fi ``` (Or, use logger(1) on all output within the script.) What's happening here can be understood if you look at the 2nd last line of /etc/rc which is: ``` rc_real_work "$@" 2>&1 | rc_postprocess ``` The rc_real_work() function runs all the rc scripts in /etc/rc.d/ including /etc/rc.local (via /etc/rc.d/local), and _all_ output is, as you can see, piped to rc_postprocess() When all the scripts finish, /etc/rc exits, and so does the RHS of that pipeline ie. whatever's running rc_postprocess(). So, anything started by rc_real_work() will get a SIGPIPE as soon as it tries to write stuff to its stdout/stderr. The nohup command also didn't work for the same reason. The nohup man-page says: If the standard output is a terminal, the standard output is appended to the file nohup.out in the current directory. If standard error is a terminal, it is directed to the same place as the standard output. Well, here the output of _all_ the scripts is a pipe, so nohup doesn't redirect the output of your command into a nohup.out file and here too it gets a SIGPIPE. HTH, -RVP
Re: rc.local nightmare
On 10/29/23 23:59, Brad Spencer wrote: Ramiro Aceves writes: Hi all, [snip] The script works fine if I run manually: #/root/nettest or even If I do this it works fine: #service local restart But If I reboot the machine the script starts during booting but I dies very soon. I do not understand what is happening here. I know that the proper way is writing a rc.d service but I am just curious to know the reason. Thanks so much. Regards. Ramiro. The NIC on the RPI can take a while to actually come available depending on what it is connected to. This seems to be especially true if dhcp is being used. What may be happening is that the network isn't available yet when rc.local runs and your scripts thinks it can't get anywhere. I noticed this because /etc/rc.d/ntpdate wasn't setting the date and time because the device couldn't get anywhere (yet). I dealt with this by adding some sleep to /etc/rc.d/ntpdate to slow the boot down a bit and allow the NIC and network to settle. You may want to do something simular another method to consider is to keep some more state around for your script and only allow it to do the reboot check if it had succeeded in getting out on the network once. Hello Brad. Thanks for the tip. I do not use DHCP, I use static address. I think that network is working fine before rc.local starts to run. My script says on the console "Network connectivity to $TARGET is OK." several times before the script dies. So ping works fine. (I have set INTERVAL=3 seconds just to speed things up during testing. Thanks so much. Ramiro.
Re: rc.local nightmare
Hi On 10/29/23 20:43, Manuel Bouyer wrote: On Sun, Oct 29, 2023 at 08:39:54PM +0100, Ramiro Aceves wrote: Hi all, I am using a raspberrypi and NetBSD 10-BETA and as we all know the flaky bwfm wifi driver is not very stable. Sometimes network fails and "ifconfig bwfm0 down" and "ifconfig bwfm0 up" does not fix it, so the raspberrypi remains unreachable from SSH, needing a physical reboot. I have written a little script that checks ping to a known site and reboots the machine if it fails after several retries: *** netbsd-nuc# cat /etc/rc.local # $NetBSD: rc.local,v 1.32 2008/06/11 17:14:52 perry Exp $ # originally from: @(#)rc.local 8.3 (Berkeley) 4/28/94 # # This file is (nearly) the last thing invoked by /etc/rc during a # normal boot, via /etc/rc.d/local. # # It is intended to be edited locally to add site-specific boot-time # actions, such as starting locally installed daemons. # # An alternative option is to create site-specific /etc/rc.d scripts. # echo -n 'Starting local daemons:' # Add your local daemons here, eg: # #if [ -x /path/to/daemon ]; then # /path/to/daemon args #fi if [ -x /root/nettest ]; then /root/nettest & fi maybe: nohup /root/nettest & ? Thanks so much Manuel. I have just tested and it does not work. /root/nettest dies after several seconds. Regards.
rc.local nightmare
Hi all,
I am using a raspberrypi and NetBSD 10-BETA and as we all know the flaky
bwfm wifi driver is not very stable. Sometimes network fails and
"ifconfig bwfm0 down" and "ifconfig bwfm0 up" does not fix it, so the
raspberrypi remains unreachable from SSH, needing a physical reboot.
I have written a little script that checks ping to a known site and
reboots the machine if it fails after several retries:
***
netbsd-nuc# cat /etc/rc.local
# $NetBSD: rc.local,v 1.32 2008/06/11 17:14:52 perry Exp $
# originally from: @(#)rc.local 8.3 (Berkeley) 4/28/94
#
# This file is (nearly) the last thing invoked by /etc/rc during a
# normal boot, via /etc/rc.d/local.
#
# It is intended to be edited locally to add site-specific boot-time
# actions, such as starting locally installed daemons.
#
# An alternative option is to create site-specific /etc/rc.d scripts.
#
echo -n 'Starting local daemons:'
# Add your local daemons here, eg:
#
#if [ -x /path/to/daemon ]; then
# /path/to/daemon args
#fi
if [ -x /root/nettest ]; then
/root/nettest &
fi
echo '.'
***
This is the script:
***
netbsd-nuc# cat /root/nettest
#!/bin/sh
PATH=/sbin:/usr/sbin:/bin:/usr/bin
# Define the IP address or hostname to test connectivity to
TARGET="www.netbsd.org"
# Define the number of retries before rebooting
RETRIES=2
# Define the time interval (in seconds) between each retry
INTERVAL=10
# Counter to keep track of failed attempts
FAILED=0
# Function to test network connectivity
check_connectivity() {
if ping -c 1 $TARGET > /dev/null 2>&1; then
echo "Network connectivity to $TARGET is OK."
return 0
else
echo "Network connectivity to $TARGET is not available."
return 1
fi
}
# Main loop
while [ $FAILED -lt $RETRIES ]; do
if check_connectivity; then
# If connectivity is successful, reset the failed counter
FAILED=0
else
# If connectivity fails, increment the failed counter
FAILED=$((FAILED + 1))
echo "Retry $FAILED of $RETRIES..."
fi
sleep $INTERVAL
done
# If we reach here, all connectivity retries failed, so reboot the machine
echo "All connectivity retries failed..."
echo "logging date and uptime..."
touch /root/network_conn_test.log
echo "reboot at:" >> /root/network_conn_test.log
date >> /root/network_conn_test.log
uptime >> /root/network_conn_test.log
echo "All connectivity retries failed. Rebooting..."
shutdown -r now
***
The script works fine if I run manually:
#/root/nettest
or even If I do this it works fine:
#service local restart
But If I reboot the machine the script starts during booting but I dies
very soon.
I do not understand what is happening here. I know that the proper way
is writing a rc.d service but I am just curious to know the reason.
Thanks so much.
Regards.
Ramiro.
Re: NetBSD 9.3 amd64 Intel Nuc 8i7BEH xorg problem
El 11/10/23 a las 16:01, Benny Siegert escribió: Yes, that's the correct procedure, but, I've never tried an update like that using `sysupgrade'--I generally do a fresh install from scratch. I have used this procedure recently (with 10_BETA), and it worked flawlessly. And, unless you're fine with compiling your applications from source, I would hold off on the upgrade until the binary packages for 10.x arrive: Technically, you can also stop after the kernel upgrade, continue using a 9.x userland, and use binary packages compiled for NetBSD-9. The kernel must be the same version or newer than the userland, but nothing says they need to be exact matches. Thanks Benny for the tip!. I should have done it, but now it is too late. ;-) But no problem, I am compiling everything as needed. It is not an everyday use computer. Just to learn. Waiting for the NetBSD 10 to arrive! Thanks so much. Regards I did that for a while on a Pinebook Pro, to avoid having to build my own packages.
Re: NetBSD 9.3 amd64 Intel Nuc 8i7BEH xorg problem (solved)
Hi On 10/8/23 01:41, RVP wrote: On Sat, 7 Oct 2023, Ramiro Aceves wrote: Just to be sure before breaking everyting ;-), is this right procedure to upgrade as The NetBSD Guide says? "When upgrading between major releases (e.g. between NetBSD 8.2 and 9.2), take care to first upgrade the kernel and modules: # sysupgrade fetch https://cdn.NetBSD.org/pub/NetBSD/NetBSD-9.2/amd64 # sysupgrade kernel # sysupgrade modules # reboot # sysupgrade sets # sysupgrade etcupdate # sysupgrade postinstall # sysupgrade clean # reboot " Yes, that's the correct procedure, but, I've never tried an update like that using `sysupgrade'--I generally do a fresh install from scratch. And, unless you're fine with compiling your applications from source, I would hold off on the upgrade until the binary packages for 10.x arrive: https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/ but changing the URL to this?: http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/latest/ Thank so much. sorry, this one: http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/202310051300Z/amd64/ Use the URL with `latest' in it. -RVP Hello RVP Thanks for answering. Before you answered I could not wait and was so excited that I did a sysupgrade to NetBSD 10.0_BETA and I can say It has been a very good learning experience. Only the sysupgrade etcupdate was a bit boring but It went ok. Now I can use the modesetting driver in Xorg and everything is smooth watching videos. I did not realize that there were no precompiled packages ;-) I have been compiling XFCE, Firefox, Libreoffice. VLC, Vim, etca bit slow and boring but not problem. This is an experimental system just to learn the OS and practice. Many thanks for all. I will continue learning. Regards. Ramiro.
Re: NetBSD 9.3 amd64 Intel Nuc 8i7BEH xorg problem
but changing the URL to this?: http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/latest/ Thank so much. sorry, this one: http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/202310051300Z/amd64/
Re: NetBSD 9.3 amd64 Intel Nuc 8i7BEH xorg problem
On 10/7/23 10:03, RVP wrote: On Fri, 6 Oct 2023, Ramiro Aceves wrote: I do not know if I am doing something wrong or NetBSD 9.3 simply cannot work properly with the Iris Plus 655 Intel Graphics card of the Nuc. The DRMKMS driver in 9.x doesn't support Iris Plus 655 i.e Coffee Lake cards. See: https://wiki.netbsd.org/laptops/ (section: Graphics) Try the latest 10-BETA. -RVP Thanks so much for your replay. Just to be sure before breaking everyting ;-), is this right procedure to upgrade as The NetBSD Guide says? "When upgrading between major releases (e.g. between NetBSD 8.2 and 9.2), take care to first upgrade the kernel and modules: # sysupgrade fetch https://cdn.NetBSD.org/pub/NetBSD/NetBSD-9.2/amd64 # sysupgrade kernel # sysupgrade modules # reboot # sysupgrade sets # sysupgrade etcupdate # sysupgrade postinstall # sysupgrade clean # reboot " but changing the URL to this?: http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/latest/ Thank so much.
NetBSD 9.3 amd64 Intel Nuc 8i7BEH xorg problem
Hello, I am a NetBSD newbye with only two months experience, and I installed NetBSD 9.3 on an Intel Nuc 8i7BEH computer. I am having trouble in getting Xorg graphics work properly. Automatic Xorg configuration with no xorg.conf file ends using wsfb driver with 800x600 resolution. After reading this document: http://wiki.netbsd.org/tutorials/x11/how_to_use_wsfb_uefi_bios_framebuffer/ I have it working at 1290x1080 pixels but no acceleration by using the following commands >gop list >gop 0 >boot at the bootloader prompt. It works well (no acceleration) but I am not able to use "modesetting" driver as I think I should be. X -configure command ends with error and manual configuration also fails using modesetting driver. I do not know if I am doing something wrong or NetBSD 9.3 simply cannot work properly with the Iris Plus 655 Intel Graphics card of the Nuc. Thanks very much in advance. I really appreciate your advice. Regards. Ramiro.
