Re: RES: RES: usb mouse not work on boot
18.05.24 21:39, Ivan Quitschal: Not sure, im on 14-current because of my synergy insists on crashing after version synergy-1.14.0.4,3 But that’s pretty simple to check Just do a # grep ‘return (BUS_PROBE_’ /user/src/sys/dev/usb/input/usbhidc in your own kernel source tree to see what line is there That's from my source tree: root@thinkpad:/usr/src # grep 'return (BUS_PROBE_' /usr/src/sys/dev/usb/input/usbhid.c return (BUS_PROBE_DEFAULT + 1);
Re: RES: usb mouse not work on boot
18.05.24 19:29, Ivan Quitschal: Hi Warner / WBR / Oleksandr Im not sure if that’s the case with this uhid.ko, but you guys remember I had a priority issue with this module and Vladimir made me a patch to fix the attach priority? Warner, was it fixed since then? Let me show the patch I use to this very day important line is this, the patch might be wrong , because im still on 14-current +// return (BUS_PROBE_GENERIC + 1); return (BUS_PROBE_DEFAULT + 1); diff --git a/sys/dev/usb/input/usbhid.c b/sys/dev/usb/input/usbhid.c index 174e1c28ae96..7b19d713c943 100644 --- a/sys/dev/usb/input/usbhid.c +++ b/sys/dev/usb/input/usbhid.c @@ -802,6 +802,7 @@ usbhid_probe(device_t dev) if (hid_test_quirk(&sc->sc_hw, HQ_HID_IGNORE)) return (ENXIO); +// return (BUS_PROBE_GENERIC + 1); return (BUS_PROBE_DEFAULT + 1); } If I correctly understand this patch alredy in main with 975407b1d8dcceac2b54e2c4df96aadec7dc4c3a
Re: usb mouse not work on boot
18.05.24 16:06, Warner Losh:
On Sat, May 18, 2024, 6:51 AM Oleksandr Kryvulia
wrote:
18.05.24 12:59, Oleksandr Kryvulia:
18.05.24 12:55, Dag-Erling Smørgrav:
Oleksandr Kryvulia <mailto:shur...@shurik.kiev.ua>
writes:
Gary Jennejohn <mailto:ga...@gmx.de> writes:
Try adding uhid_load="YES" to your /boot/loader.conf. With that
added the module should be automatically loaded during the kernel
boot.
As workaround I already have kld_list+="uhid" in /etc/rc.conf.
I hope you don't mean that literally, because /etc/rc.conf is a shell
script and += is not valid shell syntax. On the other hand, something
like
kld_list="${kld_list} uhid"
Yes, you are right. I mean
sysrc kld_list+="uhid"
One more correction. Via kld_list I need load ums(4), loading only
uhid(4) does not solve a problem.
You don't need to change kld_list. In fact, you should undo any
changes you've made there. Undo everything in loader.conf you've done.
This is a bug in the boot optimization stuff. Or rather, this exposes
a long standing bug in the USB code where there's an asymmetry between
the nomatch events and the bus tree it presents to devctl causing
devmatch to fail when the nomatch events aren't present on boot.
Just set hw.bus.devctl_nomatch_enabled=1 in /boot/loader.conf and
reboot. Or update to the change I'm about to make.
Thanks for the detailed explanation, Warner. Interesting that on my
system hw.bus.devctl_nomatch_enabled=1 is set by /etc/rc.d/devmatch but
only explicit set it in /boot/loader.conf did the trick. That is why I
think this sysctl don't work in my case.
Re: usb mouse not work on boot
18.05.24 12:59, Oleksandr Kryvulia:
18.05.24 12:55, Dag-Erling Smørgrav:
Oleksandr Kryvulia writes:
Gary Jennejohn writes:
Try adding uhid_load="YES" to your /boot/loader.conf. With that
added the module should be automatically loaded during the kernel
boot.
As workaround I already have kld_list+="uhid" in /etc/rc.conf.
I hope you don't mean that literally, because /etc/rc.conf is a shell
script and += is not valid shell syntax. On the other hand, something
like
kld_list="${kld_list} uhid"
Yes, you are right. I mean
sysrc kld_list+="uhid"
One more correction. Via kld_list I need load ums(4), loading only
uhid(4) does not solve a problem.
Re: usb mouse not work on boot
18.05.24 12:55, Dag-Erling Smørgrav:
Oleksandr Kryvulia writes:
Gary Jennejohn writes:
Try adding uhid_load="YES" to your /boot/loader.conf. With that
added the module should be automatically loaded during the kernel
boot.
As workaround I already have kld_list+="uhid" in /etc/rc.conf.
I hope you don't mean that literally, because /etc/rc.conf is a shell
script and += is not valid shell syntax. On the other hand, something
like
kld_list="${kld_list} uhid"
Yes, you are right. I mean
sysrc kld_list+="uhid"
Re: usb mouse not work on boot
18.05.24 12:42, Tomek CEDRO: does it also affect usb keyboard in single boot mode? Good question. I don't have usb keyboerd right now and will check it a bit later.
Re: usb mouse not work on boot
18.05.24 10:26, Gary Jennejohn: On Sat, 18 May 2024 09:20:24 +0300 Oleksandr Kryvulia wrote: After 6437872c1d665c2605f54e8ff040b0ba41edad07 my usb mouse no longer works on boot because uhid(4) is not autoloaded. To make it work I need manualy load uhid or replug my usb mouse. Try adding uhid_load="YES" to your /boot/loader.conf. With that added the module should be automatically loaded during the kernel boot. As workaround I already have kld_list+="uhid" in /etc/rc.conf. But IMHO it some regression.
usb mouse not work on boot
After 6437872c1d665c2605f54e8ff040b0ba41edad07 my usb mouse no longer works on boot because uhid(4) is not autoloaded. To make it work I need manualy load uhid or replug my usb mouse.
Re: suspend to idle support
16.01.24 20:29, Warner Losh: On Mon, Jan 15, 2024 at 10:24 AM Oleksandr Kryvulia wrote: Hello, What is a status of support suspend to idle? I found only two related reviews D17675 and D17676 and no more any information. It is a very desirable thing on modern laptops, where s3 is not supported like my X1 Carbon gen11[1]. [1] https://wiki.freebsd.org/Laptops/Thinkpad_X1_Carbon It works for me on my Lenovo Yoga that's a couple of years old, modulo the build-in wifi card. On my X1: hw.acpi.supported_sleep_state: S4 S5 So no S3 state and no suspend-resume support. The erlier versions have a settings in BIOS which allow to enable S3 support, but not mine. Can you share your experience with how you set it up?
suspend to idle support
Hello, What is a status of support suspend to idle? I found only two related reviews D17675 and D17676 and no more any information. It is a very desirable thing on modern laptops, where s3 is not supported like my X1 Carbon gen11[1]. [1] https://wiki.freebsd.org/Laptops/Thinkpad_X1_Carbon
Re: openzfs and block cloning question
24.11.23 10:17, Alexander Leidinger: Am 2023-11-24 08:10, schrieb Oleksandr Kryvulia: Hi, Recently cperciva@ published in his twitter [1] that enabling block cloning feature tends to data lost on 14. Is this statement true for the current? Since I am using current for daily work and block cloning enabled by default how can I verify that my data is not affected? Thank you. Block cloning may have an issue, or it does things which amplifies an old existing issue, or there are two issues... The full story is at https://github.com/openzfs/zfs/issues/15526 To be on the safe side, you may want to have vfs.zfs.dmu_offset_next_sync=0 (loader.conf / sysctl.conf) for the moment. Thanks for clarification!
Re: What is rc.d/opensm?
24.11.23 12:20, Alexander Leidinger: Hi, for my work on service jails (https://reviews.freebsd.org/D40370) I try to find out what opensm is. On my amd64 system I don't have a man page nor the binary (and man.freebsd.org doesn't know either about opensm). Bye, Alexander. See man /usr/src/contrib/ofed/opensm/man/opensm.8 and https://wiki.freebsd.org/InfiniBand
openzfs and block cloning question
Hi, Recently cperciva@ published in his twitter [1] that enabling block cloning feature tends to data lost on 14. Is this statement true for the current? Since I am using current for daily work and block cloning enabled by default how can I verify that my data is not affected? Thank you.
Re: Thinkpad X1 Carbon gen11 - suspend not work
05.10.23 11:06, Li-Wen Hsu: On Thu, Oct 5, 2023 at 4:00 PM Oleksandr Kryvulia wrote: Hi, I have Thinkpad X1 Carbon gen11 where s3 is not available: # sysctl hw.acpi.supported_sleep_state hw.acpi.supported_sleep_state: S4 S5 FreeBSD 15.0-CURRENT #47 main-n265480-95a4709b2cca-dirty, latest available bios. What can be done to investigate? I'm not sure about gen11, but for the earlier generations, the sleep state can be adjusted in BIOS. This is what on my gen6: https://twitter.com/lwhsu/status/1039711710913945601 Unfortunately, I did not find these settings in BIOS. P.S. I try ubuntu livecd and suspend-resume works.
Thinkpad X1 Carbon gen11 - suspend not work
Hi, I have Thinkpad X1 Carbon gen11 where s3 is not available: # sysctl hw.acpi.supported_sleep_state hw.acpi.supported_sleep_state: S4 S5 FreeBSD 15.0-CURRENT #47 main-n265480-95a4709b2cca-dirty, latest available bios. What can be done to investigate?
Re: service routing restart, service dhclient restart (was: Unreliability with DHCP)
06.08.23 19:23, Graham Perrin пише: Thanks, On 06/08/2023 08:36, Oleksandr Kryvulia wrote: … In my case default route is assigned by dhclient, so 'service routing restart' must be run quickly after 'service netif restart' - before we receive dhcp offer. Is this documented and explained somewhere, or did you learn through trial and error? It's my own expirience + reading /etc/rc.d/routing Another option is to run 'service dhclient restart wlan0' after routing restart. … Is there, similarly, a need to rush the two commands? I can't answer for sure, you need to try different options and choose the one that works. If you're using typical network configuration, you'll probably be fine with routing restart + dhclient restart only. This works for me in most cases until I configured lagg interface. <https://reviews.freebsd.org/P602$27> no route; <https://reviews.freebsd.org/P602$28-33> /etc/rc.d/dhclient: WARNING: failed to start dhclient
Re: service routing restart (was: Unreliability with DHCP)
06.08.23 01:35, Graham Perrin пише: On 05/08/2023 23:16, Graham Perrin wrote: On 05/08/2023 12:39, Oleksandr Kryvulia wrote: 04.08.23 19:07, Graham Perrin пише: … As dirty workaround I have in my /etc/rc.resume service netif restart service routing restart … 'service routing restart' can be problematic. Please, see, for example, <https://pastebin.com/raw/mXmVPruq>; I had something similar a few minutes ago. After 'service routing restart' (alone), should 'route show default' find a route? Only if you have static route configuration. In my case default route is assigned by dhclient, so 'service routing restart' must be run quickly after 'service netif restart' - before we receive dhcp offer. Another option is to run 'service dhclient restart wlan0' after routing restart. I have lagg with em0 and wlan0 - thats why I need 'service netif restart' instead.
Re: Fwd: Unreliability with DHCP
04.08.23 19:07, Graham Perrin пише: Can anyone from freebsd-net@ help? Forwarded Message Subject:Unreliability with DHCP Date: Sun, 30 Jul 2023 16:17:43 +0100 From: Graham Perrin Organisation: FreeBSD To: FreeBSD CURRENT 1. Sleep (suspend) whilst connected to one network 2. connect to a network elsewhere 3. wake (resume). Result: /etc/resolv.conf frequently contains outdated information. In some (maybe all) such cases, the IPv4 inet address is outdated; and so on. Which /etc/rc.d/ file(s) should I attempt to fix? I imagine using the resume keyword, which is currently used by only one script: % rcorder -k resume /etc/rc.d/* /etc/rc.d/ntpd % I routinely run the command below to work around the bug (and observe the states of things) – run _after_ the bug bites. I'd prefer a fix, to prevent the bites. ls /var/run/resolvconf/interfaces/ ; route delete default ; ifconfig wlan0 down && ifconfig em0 down && sleep 5 ; ls /var/run/resolvconf/interfaces/ ; ifconfig em0 up && sleep 15 ; ls /var/run/resolvconf/interfaces/ ; cat /etc/resolv.conf ; ping -c 2 -4 freshports.org As dirty workaround I have in my /etc/rc.resume service netif restart service routing restart
Re: CFT: fwget(8)
11.05.23 10:59, Emmanuel Vadot пише:
Hello,
Recently I've adde the fwget(8) utility, see
https://cgit.freebsd.org/src/commit/?id=d198b8774d2cfb6f140893e1c6236af9e97d1497
The goal of this program is to scan the hardware and download the
needed firmwares, for now it only do that for Intel GPUs and recent AMD
GPUs (the one supported by amdgpu.ko).
I'd like to know if I handled correctly the mapping between ids on
Intel and AMD GPUs (for i915kms and amdgpu drm module).
I'm pretty sure that Intel is correct but I could have messed up some
AMD ones. Also for some AMD GPUs you need two firmware generations and
it's hard to know by looking at the code. It would be good to fix any
bugs/miss-match before 14.0
The best way to test if everything works is :
1/ pkg delete gpu-firmware-\*
2/ (optional) pkg install drm-515-kmod/drm-510-kmod (if you had the
meta package drm-kmod installed it would have been removed in step 1)
3/ fwget
4/ kldload i915kms/amdgpu
For i915kms just check dmesg for lines saying something like
"drmn0: successfully loaded firmware image ...", this means that
everything is correct for your hardware.
If you see a line like
"drmn0: could not load firmware image ..."
please open a PR on bugzilla with dmesg and pciconf -vl attached.
Note that firmware for i915kms are optional, they only help with power
management and suspend/resume.
For amdgpu the driver will fail to attach and you will loose the
display if the firmwares aren't present so you will need to ssh into
the machine to check for similar lines like i915kms.
Thanks,
Hi,
for me it correctly detects needed package
gpu-firmware-intel-kmod-kabylake, but not install it.
Propposed fix:
- pkg install -q ${package}
+ pkg install -qy ${package}
Re: Could not change brightness anymore with i915kms & acpi_video modules c 202211
31.01.23 09:52, parv/FreeBSD пише: Since around 2022-11, I am unable to change display brightness of the display of a Framework laptop (Intel i5-1135G7, Iris Xe iGPU) with "i915kms" module (from "drm-510-kmod" package/port) & "acpi_video" (FreeBSD) kernel module. Earlier I was able to change brightness via "hw.acpi.video" MIB ... # - Need to have both "i915kms" & "acpi_video" modules already loaded. # # 20221120 - These MIBs do not work anymore as they are missing. hw.acpi.video.lcd0.economy=10 hw.acpi.video.lcd0.fullpower=40 hw.acpi.video.lcd0.brightness=15 ... now the whole of "hw.acpi.video" stub is missing. Nothing has changed in terms of how/when "i915kms" & "acpi_video" are loaded (via "kld_list" variable via "/etc/rc.conf" in that order). What am I missing? Does backlight(8) works for you?
Re: Outdated IX intel driver in /usr/src tree
08.12.22 02:09, Dan The Man пише: ix-3.3.32 is on intel website since back in July. https://www.intel.com/content/www/us/en/download/14303/intel-network-adapters-driver-for-pcie-10-gigabit-network-connections-under-freebsd.html /usr/src/sys/dev/ixgbe seems to be behind. Currently having issues with Intel 520 DA card hitting 10 gigabit speeds, last night booted same machine with Rocky Linux 9 on USB stick, no problem hitting 10gigabit with iperf3. Tried booting even a 13 release FreeBSD same issues, so nothing related to CURRENT. I've played with /boot/loader.conf and /etc/sysctl.conf tuning parameters to no avail, nothing seems to work, perhaps the updated driver may fix this? I notice there are new sysctl parameters under newest driver. router:/usr/src/sys/modules # uname -a FreeBSD router.sunsaturn.com 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-n259557-4fa1e855be60: Sun Dec 4 22:28:09 CST 2022 d...@router.sunsaturn.com:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 router:/usr/src/sys/modules # Standard Dell r720 server. Hi, can you try net/intel-ix-kmod from ports?
Re: DRM Report 2020-08-31
On 06.09.20 17:02, Emmanuel Vadot wrote: > The second one contains modification to the base tree and the > drm-devel-ports to have the backlight subsystem built > (https://reviews.freebsd.org/D26250 and child revisions). > The TLDR on backlight is that you don't need acpi_video or > intel-backlight to control your screen backlight anymore, simply use > backlight(8). This should work on all Intel or AMD laptops while other > ways (acpi_video or intel-backlight) don't always works. I intend to > commit this next week. Hi! When will this be added to the base system? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: -CURRENT and drm-devel-kmod
11.07.20 01:03, Emmanuel Vadot пишет: On Fri, 10 Jul 2020 23:57:52 +0200 Andreas Nilsson wrote: Hello, I've been running -CURRENT on my x1 yoga 1st gen for a long time, with drm-current-kmod. As I understand it that port is no longer recommended and one should run drm-devel-kmod . I don't think that somebody ever said that. For now use current if that works for you. However, when I load i915kms from -devel the console stops refreshing. It only refreshes when I switch (Ctrl+alt+Fx). I see it refresh and display the new content just before switching to the requested console. add hw.i915kms.enable_psr=0 to /boot/loader.conf This is a bug that none of my hardware have and I don't really know what's happening for now. X behaves the same way. Has anyone experienced this? I have the same issue in console, but X11 session works fine. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: editors/libreoffice PDF export/printing broken
22.06.20 20:21, Gleb Popov пишет: On Mon, Jun 22, 2020 at 9:04 PM Kostya Berger wrote: r362292In editors/libreoffice 6.4.4 PDF export is broken, including also PDF print to file. Tried with locally built 6.4.4 and pre-built package 6.4.4.2 from official repo (separate installation for testing purposes). Symptoms: of all content only graphics/tables elements get exported to PDF. No text. PS printing is all right.As regards PDF printing to file in general, it still works fine in Firefox. Only LO is affected. I filed a bug report as well. Hum, can't reproduce this on my side. Can you do `pkg upgrade`, maybe some dependency is out of date? I can confirm this problem on r362465 with latest editors/libreoffice from packages. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
