Re: 13.0-RELEASE Poor performance on Raspberry pi 3 B+
- In reply to: MJ : "Re: 13.0-RELEASE Poor performance on Raspberry pi 3 B+"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 23 Nov 2021 13:49:47 UTC
> I had similar experiences. Do you have any USB devices attached? No USB devices attached. Only hdmi to see what was going on. > I've never tried this. Is this now possible because it's a Tier 1 architecture? Sure, system upgraded from 13.0 to 13.0-p5 (only supported on 13.x, not on 12.x) > Would not memory be a constraint here? I'm not sure, it never shows excessive memory consumption. Only what I'm mentioning about wdrain > And usually they start exhibiting write issues beforehand if they're going to fail. I'll try another microsd later and see what happens. But why does raspios not show this kind of behaviour? > Have you looked in /var/log/messages to see if there's any help there? Mmmm nothing I can find suspicious but let me post the message from a fresh install https://bsd.to/PJgm El mar, 23 nov 2021 a las 0:44, MJ (<mafsys1234@gmail.com>) escribió: > > > On 23/11/2021 1:42 pm, Juan David Hurtado G wrote: > > Hi, I'm trying to use the OS on a Raspberry pi 3 B+ > > > > Boot is pretty slow. It hangs on `ue0: Ethernet addresss: ...` for some > > minutes before showing the `login:` to enter the username. When I enter > it, > > it takes a few seconds to ask for the password. > > > I had similar experiences. Do you have any USB devices attached? > One thing to watch for is any mounting of USB drives. I also had problems > with certain cables connecting USB drives to the Pi but when I placed them > on a powered hub they were fine (not slow to mount). As a reference, > running devuan I had no issues. > > If you have USB drives attached, try this: place hw.usb.no_boot_wait="1" > in /boot/loader.conf > > > > > While doing `freebsd-update fetch install` it took a plenty of minutes, > so > > I canceled the process and then did `freebsd-update fetch` and then > > `freebsd-update install` to see what was going on. > > > > Found that the process was at `wdraid` state. Doing a simple search, I > > found about `vfs.hirunningspace` so I tweaked it to 1Mb and then to 2Mb. > It > > seems to help, but not by much. Look at this: > > > > freebsd@generic:~ % time freebsd-version -kru > > 13.0-RELEASE-p4 > > 13.0-RELEASE-p4 > > 13.0-RELEASE-p5 > > 0.365u 0.045s 0:41.25 0.9% 20+177k 14+0io 0pf+0w > > > > :( > > > > What could I be missing? Maybe I need to tweak partitions and use some > kind > > of configuration/optimization? how? I do appreciate any guidance you can > > provide in order to troubleshoot this. > > I've never tried this. Is this now possible because it's a Tier 1 > architecture? > Would not memory be a constraint here? You definitely wouldn't want to be > using tmpfs system. > > > > > PS: I don't think it is the microsd card since it runs raspios fine. > > > > And usually they start exhibiting write issues beforehand if they're going > to fail. > > Have you looked in /var/log/messages to see if there's any help there? > Matt. > > -- Juan David Hurtado G (+57) 319 252 3773 www.orbiware.com