Re: graphics/drm-61-kmod build failure for main-n276560-83dcc133c876

commit a3a88ed appears to have removed the function(s) needed by drm kmod to build and run :-( Michael On 4/19/25 09:06, David Wolfskill wrote: Running: FreeBSD g1-118.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #445 main-n276537-7121e9414f29: Fri Apr 18 12:36:30 UTC 2025 r

Re: Reply: ISO build broken?

On 3/20/25 13:46, Ed Maste wrote: On Tue, 18 Mar 2025 at 22:39, Michael Butler wrote: Ah .. thanks for the hint .. trying with WITHOUT_LLVM_BINUTILS set now, Thanks for the report - I've opened https://reviews.freebsd.org/D49425 to address this. And just to confirm .. a

Re: =?UTF-8?Q?Reply:=20ISO=20build=20broken??=

Ah .. thanks for the hint .. trying with WITHOUT_LLVM_BINUTILS set now, Michael On 3/18/25 22:29, yu shan wei wrote: Is it because of LLVM-BINUTILS? Sender： Time：Wednesday, March 19, 2025, 3:04 Recipient： Subject：ISO build broken? Is anyone else seeing this when building ISOs with

ISO build broken?

Is anyone else seeing this when building ISOs with release/release.sh? --- bootonly --- --- realinstall_subdir_usr.bin --- --- _proginstall --- --- disc1 --- install -N /usr/src/etc -o root -g wheel -m 444 DH_set_method.3.gz /usr/obj/usr/src/amd64.amd64/release/disc1/usr/share/openssl/man/man3/

Re: Empty structures have sizeof(1) in C++ now ?

hat the addresses of two different objects will be different. For the same reason, "new" always returns pointers to distinct objects. -m -- Michael Gmelin

Re: Difference in "netstat -rn" output in the last 2 months

this ring a bell for someone? > If there had been "iocage" in the subject, I would've looked into it earlier :) I'll produce a PR on the repo based on the issue you opened and also apply it to the port. Cheers -- Michael Gmelin

upgrade llvm19 broke drm-6.1 kmod

It seems there are some additional constraints about non-existent directories that now count as errors .. --- sync_file.o --- cc -O2 -pipe -fno-strict-aliasing -DLINUXKPI_VERSION=60100 '-DKBUILD_MODNAME="dmabuf"' -DCONFIG_DRM_AMDGPU_CIK -DCONFIG_DRM_AMDGPU_SI -DCONFIG_DRM_AMD_DC -DCONFIG_DRM_

Re: weekly locate error Was: September 2024 stabilization week

have been introduced earlier. Manual run of the periodic job doesn't reproduce the problem :( Backing out commit f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9 resolves it for me, Michael

Re: September 2024 stabilization week

t installs. It seems to have started with commit f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9 Michael

Re: RTL8125: wont stay up

> On 20. Aug 2024, at 04:15, Larry Rosenman wrote: > > shows up, doesn't ping -- ifconfig up brings it back for ~4 packets > > ifconfig_re0="DHCP" > ifconfig_re0_ipv6="inet6 accept_rtadv" > ipv6_activate_all_interfaces="AUTO" > rtsold_enable="YES" > > 15-CURRENT as of just now, port of net/

Re: filemon

> being added to the boot loader. It should almost always be empty or w> just drm-mod these days (unless you somehow have special needs). w> w> By adding uhid last to this list in this way, you're guaranteeing w> you'll hit this bug because it's not after ums, and that things w> won't work. w> w> Warner Cheers -- Michael Gmelin

Re: exited on signal 11 (no core dump - other error)

9s > > ukbd0: detached > > uhub0: detached > > ---<>--- > > > > IIUC all processes will get signal to quit on system reboot. But what > does the > > signal 11 mean ? Is it EDEADLK in sys/sys/errno.h ? > I think signal 11 refers to SIGSEGV (segmentation violation). > However, I have no idea why a bunch of processes would do that during > shutdown? > > rick > > > > > If yes, then why they get dead locked ? > > > > > > Best regards, > > Zhenlei > > > > > > -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion'

Re: Heads-up: ifconfig address without a mask/width to become an error

> On 17. Jun 2024, at 20:34, Shawn Webb wrote: > > On Mon, Jun 17, 2024 at 10:54:29AM -0400, Ed Maste wrote: >> It is currently possible to specify an IPv4 address without a >> netmask/width to ifconfig or in rc.conf, e.g.: >> >>ifconfig_igb0="192.168.0.2" >> >> phk recently discovered[

Re: Heads-up: ifconfig address without a mask/width to become an error

;known issues", which those of us who read the release notes can stumble over and check? This would be useful in general, as it seems like doing ENs is a lot of overhead. Also, if that process would be fast, users would be warned early - especially in a case like this, where the workaround/long term fix is actually fairly trivial (add a netmask to your ifconfig_xxx line). Best Michael -- Michael Gmelin

Re: 14.1-R rc.conf/ifconfig netmask issue was really hard to figure out

On Wed, 12 Jun 2024 15:35:58 + "Poul-Henning Kamp" wrote: > ---- > Michael Gmelin writes: > > > @phk From which version did you upgrade? > > To be totally honest: I'm not entirely sure. Probably 13.x > @Bjoern I checked again, I'm pre

Re: 14.1-R rc.conf/ifconfig netmask issue was really hard to figure out

On Wed, 12 Jun 2024 15:11:14 + (UTC) "Bjoern A. Zeeb" wrote: > On Wed, 12 Jun 2024, Bjoern A. Zeeb wrote: > > > On Wed, 12 Jun 2024, Michael Gmelin wrote: > > > >> > >> > >> On Wed, 12 Jun 2024 14:36:35 + > >> &

Re: 14.1-R rc.conf/ifconfig netmask issue was really hard to figure out

estingly, `ifconfig vtnet0 10.0.0.1` uses "/24" whereas 192.168.87.11 uses "/8". This dates back to: https://cgit.freebsd.org/src/commit/?id=4bf44dd73bc0a -m -- Michael Gmelin

Re: 14.1-R rc.conf/ifconfig netmask issue was really hard to figure out

On Wed, 12 Jun 2024 11:28:38 + "Poul-Henning Kamp" wrote: > ---- > Michael Gmelin writes: > > > You can do an interface route hack > > I think you misunderstand the situation. I completely understand the situation and I can feel your pain, I just

Re: 14.1-R rc.conf/ifconfig netmask issue was really hard to figure out

4 -interface bla0" sysrc route_default="default 1.2.3.4" This is actually quite useful in some setups, but in the context of deciding on default behavior when no mask is given this is probably not very helpful. Cheers -- Michael Gmelin

pkg scripts need updating

After commit aa48259f337100e79933d660fec8856371f761ed to src which removed security_daily_compat_var, I get these warnings daily.. aaron.protected-networks.net login failures: aaron.protected-networks.net refused connections: /usr/local/etc/periodic/security/405.pkg-base-audit: security_daily_

Re: Alt+Fn isn't functional. Has this been removed?

> On 30. Mar 2024, at 07:30, Chris wrote: > > On 2024-03-29 23:06, Michael Schuster wrote: >> Two ideas: >> - does CTL-ALT-Fn work? > Thanks. But no, I tried that. > >> - perhaps the number of predefined ttys was overwritten/set to 0 somewhere? > I'm

kernel build w/o DDB broken after c21bc6f

When a kernel is built without KDB and DDB, it fails with: --- kernel.full --- linking kernel.full ld: error: undefined symbol: db_ctf_lookup_typename >>> referenced by kern_ctf.c:329 (/usr/src/sys/kern/kern_ctf.c:329) >>> link_elf_obj.o:(link_elf_ctf_lookup_typename) >>> referenced

after commit 5e248c2, kernel module build is broken

Building /usr/obj/usr/src/amd64.amd64/sys/VM01-new/modules/usr/src/sys/modules/vmm/machine machine -> /usr/src/sys/amd64/include Building /usr/obj/usr/src/amd64.amd64/sys/VM01-new/modules/usr/src/sys/modules/vmm/x86 x86 -> /usr/src/sys/x86/include Building /usr/obj/usr/src/amd64.amd64/sys/VM01

commit f74352f breaks world

Moving these definitions breaks world outside the kernel :-( building shared library libmapper_std.so.5 Building /usr/obj/usr/src/amd64.amd64/lib/libiconv_modules/mapper_zone/libmapper_zone.so.5 building shared library libmapper_zone.so.5 Building /usr/obj/usr/src/amd64.amd64/lib/libstats/tcp

Re: WITHOUT_CASPER ghost?

k my build option testing? If so, what syntax would use __REQUIRED_OPTIONS and what branches support it? Michael

WITHOUT_CASPER ghost?

d5 1 error I am tracking the build options here: https://callfortesting.org/results/bos-ci/ My apologies if this is a false positive. Michael

Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: request" leads to panic

On 2/12/24 13:44, Michael Butler wrote: On 2/12/24 12:36, John Baldwin wrote:  [ .. trimmed .. ] Short of a stack trace, you can at least use lldb or gdb to lookup the source line associated with the faulting instruction pointer (as long as it isn't in a kernel module), e.g. for gd

Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: request" leads to panic

atic inline void 88 counter_u64_add(counter_u64_t c, int64_t inc) 89 { 90 91 KASSERT(IS_BSP() || c != EARLY_COUNTER, ("EARLY_COUNTER used on AP")); 92 zpcpu_add(c, inc); 93 } 94 95 #endif /* ! __MACHINE_COUNTER_H__ */ 96 Michael

Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: request" leads to panic

On 2/12/24 12:36, John Baldwin wrote: On 2/10/24 2:09 PM, Michael Butler wrote: I have stability problems with anything at or after this commit (b377ff8) on an amd64 laptop. While I see the following panic logged, no crash dump is preserved :-( It happens after ~5-6 minutes running in KDE (X

Re: Recent commits reject RPi4B booting: pcib0 vs. pcib1 "rman_manage_region: request" leads to panic

I have stability problems with anything at or after this commit (b377ff8) on an amd64 laptop. While I see the following panic logged, no crash dump is preserved :-( It happens after ~5-6 minutes running in KDE (X). Reverting to 36efc64 seems to work reliably (after ACPI changes but before the

Re: Proposal: Disable compression of newsyslog by default

> On 23. Dec 2023, at 16:10, Enji Cooper wrote: > >  >> On Dec 22, 2023, at 23:18, Xin Li wrote: >> >> Hi, >> >> Inspired by D42961, I propose that we move forward with disabling the >> compression by default in newsyslog, as implemented in >> https://reviews.freebsd.org/D43169 >> >> H

mrsas scatter/gather tunable?

ioctl data mem" messages. This seems to be as a result of running into the 16 s/g buffer limit for pass-through IOCTLs used by smartd and/or storcli. There doesn't appear to be any data corruption, just annoying log lines. Has anyone else run into this? Michael

status of openssl 3.0.11 in stable/14?

hose files stored in git after import? Sorry, I am still not understanding git repositories well enough. Thanks and regards, Michael

WITHOUT_CAPSICUM|CASPER option ignored: it is no longer supported

ying to be reimplemented? Thank you! Michael

Re: something magic about the size of a ports tree

> On 3. Oct 2023, at 18:27, Matthias Apitz wrote: > > El día martes, octubre 03, 2023 a las 06:14:23p. m. +0200, Olivier Certner > escribió: > >> Hi Matthias, >> >> Some ZFS dataset with zstd compression on jet, and no compression on >> c720-1400094? >> > > Yes, on jet it is ZFS: > > r

Re: changes to ps -d?

> On 19. Sep 2023, at 12:30, Ronald Klop wrote: > > Hi, > > In current the way ps -p works has been changed [1]. > I could use "ps axd -p " to see the process tree of some ongoing task. > In current this has changed to always need an extra option "ps axd -p > -D down". Can this become the d

freebsd-current@freebsd.org

just wanted to note that two things had changed in my testing, microcode and CPUTYPE, not just one, Michael

freebsd-current@freebsd.org

On 8/8/23 13:50, Michael Butler wrote: On 8/8/23 10:56, Tomoaki AOKI wrote: On Tue, 8 Aug 2023 17:02:32 +0300 Konstantin Belousov wrote:  [ .. snip .. ] The workaround is switched on automatically, when kernel detects 'small cores' reported by CPUID. If I read the code

Re: CURRRENT snapshot won't boot due missing ZFS feature

14 """ You can find thew whole thread here: https://lists.freebsd.org/archives/freebsd-current/2023-June/003835.html Best Michael On Sat, 16 Sep 2023 17:22:20 +0100 Warner Losh wrote: > On Sat, Sep 16, 2023 at 5:11 PM Toomas Soome wrote: > > > > &

Re: 14.0-CURRENT boots fine but keyboard does not work

> On 4. Sep 2023, at 19:34, Matthias Apitz wrote: > > El día lunes, septiembre 04, 2023 a las 07:29:41p. m. +0200, Michael Gmelin > escribió: > >> >> >>>> On 4. Sep 2023, at 19:23, Matthias Apitz wrote: >>> >>> 

Re: 14.0-CURRENT boots fine but keyboard does not work

ould you please Cc me on it? Do you know which version of FreeBSD was the last that worked for you? Cheers > > >> El día lunes, septiembre 04, 2023 a las 06:55:52p. m. +0200, Michael Gmelin >> escribió: >> >> >> >> On Mon, 4 Sep 2023 18:43:11 +020

Re: 14.0-CURRENT boots fine but keyboard does not work

cause keyboard/mouse freezes on some hardware, please set loader tunable hw.atkbd.hz=1 as workaround and report the issue. So you could try to set hw.atkbd.hz=1 (or hw.atkbd.hz=10) in /boot/loader.conf, then reboot and see if it helps. Best Michael -- Michael Gmelin

Re: kernel 100% CPU, and ports-mgmt/poudriere-devel 'Inspecting ports tree for modifications to git checkout...' for an extraordinarily long time

d.org/ports.git` work for you? (currently it's not working from where I am). Maybe related. Best Michael -- Michael Gmelin

Re: periodic daily produces ridiculously huge report files

Michael Grimm wrote > Ever since either upgrading to MAIN or WITHOUT_INET6=yes [1] I noticed that > periodic daily still runs in the morning failing to mail ridiculously huge > report files (>= 90 *GB*). > > [1] Can't remember when this started. FTR: It started

periodic daily produces ridiculously huge report files

r of "netstat -i -d -W"? Anyone with WITHOUT_INET6=yes willing to test this? Regards, Michael

freebsd-current@freebsd.org

Compilation reattempts (mostly) succeed. Initially, I put this down to an inadequate power-supply but setting vm.pmap.pcid_enabled=0 seems to have stabilised it. I guess there's another dragon in there .. :-( Michael

[SOLVED] 14-CURRENT | alternatives for defunct /usr/lib/pam_opie.so?

Dag-Erling Smørgrav wrote: > Michael Grimm writes: >> I'm currently in the process to prepare for upcoming 14-STABLE. Thus, >> I upgraded one of my sytems from 13-STABLE to 14-CURRENT. > > Did you run etcupdate? I was just about to report that I somehow managed

14-CURRENT | alternatives for defunct /usr/lib/pam_opie.so?

ves to pam_opie should I investigate? Reason: I want to get rid of security/opie Thanks and regards, Michael

Re: make buildworld puts legacy tools into the /usr/obj/... tree

On 6. Aug 2023, at 18:12, Warner Losh wrote:On Sun, Aug 6, 2023 at 10:05 AM Matthias Apitz wrote:El día domingo, agosto 06, 2023 a las 09:58:32a. m. -0600, Warner Losh escribió: > On Sun, Aug 6, 2023 at 7:58 AM Matthias Apitz wrote: > > > > > I did, based o

Re: poudriere && git

-c -j stable -m src=/usr/src poudriere jail -l JAILNAME VERSION ARCH METHOD TIMESTAMP PATH stable 13.2-STABLE 1302507 amd64 src=/usr/src 2023-08-05 15:01:13 /usr/home/poudriere/jails/stable Updating: poudriere jail -u -j stable Regards, Michael

Re: poudriere && git

be built unless -b is given. It is expected that it is already built and maps to a corresponding /usr/obj directory. HTH and regards, Michael

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Thu, 8 Jun 2023 11:32:19 -0600 Warner Losh wrote: > On Thu, Jun 8, 2023, 11:18 AM Michael Gmelin > wrote: > > > > > > > Tried today's snaphot, same problem. > > > > > > # reboot > > > Waiting (max 60 seconds) for system pr

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Thu, 8 Jun 2023 19:06:23 +0200 Michael Gmelin wrote: > On Thu, 8 Jun 2023 16:20:12 + > Glen Barber wrote: > > > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote: > > > Hi, > > > > > > I didn't dig into this yet. > &

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Thu, 8 Jun 2023 16:20:12 + Glen Barber wrote: > On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote: > > Hi, > > > > I didn't dig into this yet. > > > > After installing the current 14-snapshot (June 1st) in a bhyve-vm, I > > g

CURRRENT snapshot won't boot due missing ZFS feature

Hi, I didn't dig into this yet. After installing the current 14-snapshot (June 1st) in a bhyve-vm, I get this on boot: ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 (booting stops at this point) Seems like the boot loader is missing this recently added feature. Best Mi

Re: Delay in 14.0-RELEASE cycle and blocking items

Am 2023-05-15 um 22:36 schrieb Yuri: Yuri wrote: Michael Osipov wrote: Am 2023-05-15 um 22:19 schrieb Yuri: Michael Osipov wrote: Am 2023-05-15 um 21:37 schrieb Glen Barber: On Mon, May 15, 2023 at 09:15:52PM +0200, Michael Osipov wrote: Glen, do you see any chance to get this finally

Re: Delay in 14.0-RELEASE cycle and blocking items

Am 2023-05-15 um 22:19 schrieb Yuri: Michael Osipov wrote: Am 2023-05-15 um 21:37 schrieb Glen Barber: On Mon, May 15, 2023 at 09:15:52PM +0200, Michael Osipov wrote: Glen, do you see any chance to get this finally merged: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236204 ? It

Re: Delay in 14.0-RELEASE cycle and blocking items

Am 2023-05-15 um 21:37 schrieb Glen Barber: On Mon, May 15, 2023 at 09:15:52PM +0200, Michael Osipov wrote: Glen, do you see any chance to get this finally merged: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236204 ? It seriously affects people (in enterprises) behind a proxy, curl will

Re: Delay in 14.0-RELEASE cycle and blocking items

Glen, do you see any chance to get this finally merged: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236204 ? It seriously affects people (in enterprises) behind a proxy, curl will be a problem and py-requests is already a serious problem. Michael

Boot failure on a ThinkPad T14/Ryzen 7 Pro 6850U

mory (width 8) R/W 0 Address=70F3 ... nsxfeval-0386 EvaluateObject : Null handle with relative pathname [_PRW] nsxfeval-0386 EvaluateObject... Related suggestion: Should 'options ACPI_DEBUG' be built into the snapshot kernels along with WITNESS etc? Any additional suggestions? Thank you! Michael

Re: ntpd fails on recent -current/arm64

] While I can't suggest a fix, I discovered this workaround until one is found; edit /etc/ntp.conf to include .. interface ignore wildcard interface listen lo0 interface listen em0 .. or whichever interfaces are required on the host, Michael

Re: Reducing SIGINFO verbosity

On Thu, 23 Jun 2022 11:15:55 -0600 Warner Losh wrote: > On Sun, Jun 19, 2022 at 6:06 AM Michael Gmelin > wrote: > > > > > > > On Fri, 21 May 2021 08:36:49 -0600 > > Warner Losh wrote: > > > > > On Fri, May 21, 2021 at 7:38 AM Ceri Davies &

FreeBSD 13.2-stable crash in /usr/src/sys/amd64/include/pcpu_aux.h:55

only thing that was occurring which is not a normal thing for me to is I was moving TB's worth of data between directly attached two zpools. Regards, Michael Jung

Re: Tooling Integration and Developer Experience

> On 31. Jan 2023, at 22:44, Kurt Jaeger wrote: > > Hi! > This can be as easy as moving everything into Phabricator. >>> There's the issue that Phabricator itself is no longer supported >>> upstream: > [...] >>> https://we.phorge.it/ > >> Should be no harder than regular update. They e

witness_lock_list_get: witness exhausted

without adding the sysctl knobs I do that also - I am not kernel savvy. I will make sure and test an updated patch should one be made available or advise whether to increment these values or ignore the warnings. Regards, Michael Jung CONFIDENTIALITY NOTE: This message is intended onl

smartpqi0 "panic: Segment size is not aligned" Related panic on savecore?

size is not aligned" panic: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259541 https://reviews.freebsd.org/D30182 Should I update that second PR? Have any suggestions for verifying the issue? All the best, Michael

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

On Sun, 28 Aug 2022 03:21:24 -0700 Cy Schubert wrote: > In message <16b4-76a1-4e46-b7c3-60492d379...@freebsd.org>, > Michael Gmelin w > rites: > > > > > > > > > On 28. Aug 2022, at 10:42, free...@oldach.net wrote: > > >=20 > >

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

ports would be more clear. Another advantage would be that directories are only created for services that are actually enabled/started. Cheers Michael

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

> On 27. Aug 2022, at 15:18, free...@oldach.net wrote: > > Michael Gmelin wrote on Sat, 27 Aug 2022 15:02:04 +0200 (CEST): >> (you're removing /var/run, which shouldn't be removed > > Not quite. It's actually not uncommon to boot with an empty /var. Ple

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

> On 27. Aug 2022, at 12:54, FreeBSD User wrote: > > Am Sat, 27 Aug 2022 11:21:40 +0200 > Michael Gmelin schrieb: > >>>> On 27. Aug 2022, at 08:31, FreeBSD User wrote: >>> >>> Hello, >>> >>> I'm referencing to Bug 259

Re: security/clamav: /ar/run on TMPFS renders the port broken by design

> It is really hard to always chenge our local repository and patch whenever > clamav has been > patched and modified for what reason ever. > > Tahanks for reading, > Why don’t you simply add an rc script to your appliance that creates the missing directory/directories on boot before clamav is started? Best Michael

Re: main-n257625-587649902329-dirty?

log/2017/10/12/check-git-dirty/ Cheers Michael

Re: ZFS: cannot import zroot: I/O error

, this situation can be prevented (or at least made less likely) by disabling "IgnoreFlush" - depending on the virtual device emulated this could be something like: VBoxManage setextradata VM-name "VBoxInternal/Devices/ahci/0/LUN#[0]/Config/IgnoreFlush" 0 or VBoxManage setextradata VM-name "VBoxInternal/Devices/piix3ide/0/LUN#[x]/Config/IgnoreFlush" 0 See also: https://www.virtualbox.org/manual/ch12.html#ts_ide-sata-flush It’s highly recommended for ZFS in case your VM isn’t a throwaway CI thing. Best Michael

Re: bhyve core dump related to llvm 14

d reproduction steps and the debug output in this bug report: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265749 Michael

Re: pkg: Newer FreeBSD version for package... but why?

tem. You can point it to checking another file by setting ABI_FILE[0] in the environment or ignore the check by setting IGNORE_OSVERSION (like advised). The "running kernel:" label seems a bit misleading. Cheers Michael -- Michael Gmelin

Re: Accessibility in the FreeBSD installer and console

> On 9. Jul 2022, at 03:22, Klaus Küchemann wrote: > >  >> Am 07.07.2022 um 19:32 schrieb Hans Petter Selasky : >> >> Hi, >> >> The only argument I've heard from some non-sighted friends about not using >> FreeBSD natively is that ooh, MacOSX is so cool. It starts speaking from the >> sta

Re: Accessibility in the FreeBSD installer and console

> On 8. Jul 2022, at 14:48, Hans Petter Selasky wrote: > > On 7/8/22 14:34, David Chisnall wrote: > Snipsnap > Hi, > > I've updated my patch a little bit, so please re-fetch it. > > I tried: > > action "echo -- $text | rtprio 8 > /usr/local/bin/flite_cmu_us_slt" > > And i

Re: iichid/hms keyboard/mouse wrongly reattached to uhid/ums

ers loaded, even > >though ums is a generic driver. > > >Try loading all relevant drivers in /boot/loader.conf . Then the > >attach order shouldn't matter. > > >--HPS > > > Hi Michael > > Yes , hw.usb.usbhid.enable="1" is in loa

Re: iichid/hms keyboard/mouse wrongly reattached to uhid/ums

w.usb.usbhid.enable="1" in /boot/loader.conf, or by using the sysctl? If you don't do it yet, I'd recommend the former. Cheers Michael > > Thanks > > --tzk > -- Michael Gmelin

Re: Posting netiquette: HTML, attachments etc.

rmatting (it looked like outlook, no quoting, top posting like exchanging written letters, using various font types and sizes). So if we could eliminate these kind of emails, I would be happy. Cheers Michael p.s. I’m pretty sure top posting is also against netiquette - unless *you* do it o

Re: Posting netiquette: HTML, attachments etc.

> On 26. Jun 2022, at 09:37, grarpamp wrote: > >  >> >> https://github.com/freebsd/freebsd-doc/blob/main/documentation/content/en/books/handbook/eresources/_index.adoc >> >> FreeBSD Handbook: Appendix C: updates and corrections >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264754 >>

Re: Reducing SIGINFO verbosity

t; > I plan on changing the default for non-INVARIANT kernels back to > the old behavior. > > INVARIANT kernels will keep this behavior because it's a debugging > kernel and this is one more thing to help debugging problems. > Did this ever happen? I just installed a fresh

Re: SAS/SATA controllers: 8 port that support 8TB Drives

> On 18. Jun 2022, at 15:10, Larry Rosenman wrote: > >  > On 06/18/2022 3:54 am, Michael Gmelin wrote: > > [SNIP] > > > Subvendor is Fujitsu Siemens - so I guess this is integrated into a system by > them. > > Seems like flashing the 2108 to an I

Re: SAS/SATA controllers: 8 port that support 8TB Drives

> On 18. Jun 2022, at 01:31, Larry Rosenman wrote: > On 06/17/2022 6:20 pm, Michael Gmelin wrote: >>>> On 18. Jun 2022, at 00:57, Larry Rosenman wrote: >>> On 06/17/2022 5:48 pm, Michael Gmelin wrote: >>>>> On 18. Jun 2022, at 00:31, Alexander Motin

Re: SAS/SATA controllers: 8 port that support 8TB Drives

> On 18. Jun 2022, at 00:57, Larry Rosenman wrote: > On 06/17/2022 5:48 pm, Michael Gmelin wrote: >>> On 18. Jun 2022, at 00:31, Alexander Motin wrote: >>>  >>>> On 17.06.2022 18:24, Alexander Motin wrote: >>>>> On 17.06.2022 18:16

Re: How to supress prompt on bc 5.3.1,Re: How to supress prompt on bc 5.3.1

On 6/15/22 18:47, Masachika ISHIZUKA wrote: I updated to master-n256084-5dd1f6f1441 (1400061) and this leads to bc to 5.3.1. Previosly, 'BC-ENV-APRG=-P' or 'bc -P' were working but it doesn't work on 5.3.1. Is there any way to supress prompt ? This is fixed in 5.3.2: This version is al

commit 695052e is incomplete

After 695052e, the directories compat, dtrace, engines, flua, i18n and libxo now get created under /usr. This is one level higher than they should be. The fix appears to be something like .. diff --git a/etc/mtree/BSD.usr.dist b/etc/mtree/BSD.usr.dist index 9f934976b77..95a711a4418 100644 ---

Re: git question: How do I push a cherry-pick of someone else's commit?

What is the error message? Did you try “git push -f” > On 9. Jun 2022, at 21:33, Rick Macklem wrote: > > I just tried to MFC a commit done to fix my commit by imp@ > and it won't let be push the cherry-pick. > > What's the trick to doing this? > Or do I need to get Warner to do it? > If so, i

Re: commit 99902b1 causes kernel panics

On 6/5/22 02:09, Hans Petter Selasky wrote: On 6/4/22 23:21, Michael Butler wrote: On a Dell E6430 laptop with an i5-3340M CPU on-board but no additional video adapter, this commit causes a panic when i915kms is loaded :-( This adapter does not use any additional firmware. Does the

commit 99902b1 causes kernel panics

On a Dell E6430 laptop with an i5-3340M CPU on-board but no additional video adapter, this commit causes a panic when i915kms is loaded :-( This adapter does not use any additional firmware. Reverting only this change allows me to run way past it - up to commit 00b0158d2ca, so far. All modul

Re: Bulld failure of editors/libreoffoce only on main (aka -current)

rever with CPUTYPE set to "native". I just found this last night but setting CPUTYPE to "ivybridge" or leaving it unset allows it to run to completion, Michael

Re: FreeBSD, boot environments and /dev

On Sat, May 14, 2022, 21:40 Michael Schuster wrote: > > On Thu, May 12, 2022 at 9:21 AM Dave Cottlehuber wrote: > > > > On Thu, 12 May 2022, at 07:12, Michael Schuster wrote: > > > On Wed, May 11, 2022 at 11:38 PM Dave Cottlehuber > > > wrote: > >

Re: FreeBSD, boot environments and /dev

On Sat, May 14, 2022 at 10:30 PM Mark Millard wrote: > > Michael Schuster wrote on > Date: Sat, 14 May 2022 21:40:56 +0200 : > > > findings: > > 1) temporary activation doesn't work for me: bectl accepts the option > > but there's no effec

Re: FreeBSD, boot environments and /dev

On Thu, May 12, 2022 at 9:21 AM Dave Cottlehuber wrote: > > On Thu, 12 May 2022, at 07:12, Michael Schuster wrote: > > On Wed, May 11, 2022 at 11:38 PM Dave Cottlehuber > > wrote: > >> On Wed, 11 May 2022, at 14:58, Michael Schuster wrote: > >> > I th

Re: FreeBSD, boot environments and /dev

On Wed, May 11, 2022 at 11:38 PM Dave Cottlehuber wrote: > On Wed, 11 May 2022, at 14:58, Michael Schuster wrote: > > I then created a new BE, mounted it on /mnt, removed /mnt/dev/* (only > > regular files and empty directories). Booting into that BE didn't work > >

Re: FreeBSD, boot environments and /dev

On Mon, May 9, 2022 at 10:04 AM Dave Cottlehuber wrote: > > On Mon, 9 May 2022, at 06:25, Michael Schuster wrote: > > On Fri, May 6, 2022 at 12:15 AM Wes Maag wrote: > >> > >> > >> On Thu, May 5, 2022 at 4:10 PM Michael Schuster > >> wrote: >

Re: FreeBSD, boot environments and /dev

On Fri, May 6, 2022 at 12:15 AM Wes Maag wrote: > > > On Thu, May 5, 2022 at 4:10 PM Michael Schuster > wrote: > >> Hi all, >> >> while still working (slowly) on an answer to my own question on the >> right workflow to keep current up to date reliably wi

Re: FreeBSD, boot environments and /dev

Hi Wes, finally I get round to responding (below) ... On Fri, May 6, 2022 at 12:15 AM Wes Maag wrote: > > > > On Thu, May 5, 2022 at 4:10 PM Michael Schuster > wrote: >> >> Hi all, >> >> while still working (slowly) on an answer to my own question on t

FreeBSD, boot environments and /dev

arent requirement to mount devfs separately not so long ago ... definitely this year, while I've been experimenting with boot environments for quite a bit longer. Was I just lucky all along, or did something change ... and, more importantly, how do I make my boot environments bootable again

Re: "pkg upgrade" failing with "Fail to create temporary file: ... Not a directory"

On Thu, Apr 28, 2022 at 10:43 AM Christoph Moench-Tegeder wrote: > > ## Michael Schuster (michaelspriv...@gmail.com): > > > $subject happened to me just now on current. I researched it on the > > internet, > > Don't look that far, the answer is in UPDATING: &g

  1   2   3   4   5   6   7   8   9   10   >