Re: devd nomatch does not load uslcom anymore

b28f81521: Thu May 16 07:54:05 CEST 2024 > > Today I noticed my USB serial cable to my RPI3 was not available anymore. > It hadn't loaded 'uslcom' at boot. > Adding 'hw.bus.devctl_nomatch_enabled=1' to /boot/loader.conf resolves the > issue for now. > > The proper output du

devd nomatch does not load uslcom anymore

was not available anymore. It hadn't loaded 'uslcom' at boot. Adding 'hw.bus.devctl_nomatch_enabled=1' to /boot/loader.conf resolves the issue for now. The proper output during boot is: Starting devd. Autoloading module: uslcom uslcom0 on uhub1 uslcom0: on usbus0 Does anybody need more information about

Re: Move u2f-devd into base?

David Chisnall wrote on Date: Mon, 08 Jan 2024 17:12:06 UTC : > On 8 Jan 2024, at 16:30, Tomoaki AOKI wrote: > > > > So it should be in ports to adapt for latest products more quickly than > > in base, I think. > > We push out a new release of each of the -STABLE branches every 6 months

Re: Move u2f-devd into base?

n, Jan 8, 2024, 7:55〓AM Christian Weisgerber >> >> wrote: >> >> >> >>> We have FIDO/U2F support for SSH in base. >> >>> >> >>> We also have a group "u2f", 116, in the default /etc/group file. >> >>> >> >

Re: Move u2f-devd into base?

a group "u2f", 116, in the default /etc/group file. >>> >>> Why do we keep the devd configuration (to chgrp the device nodes) >>> in a port, security/u2f-devd? Can't we just add this to base, too? >>> It's just another devd configuration file. >>> >&

Re: Move u2f-devd into base?

e have FIDO/U2F support for SSH in base. > >>> > >>> We also have a group "u2f", 116, in the default /etc/group file. > >>> > >>> Why do we keep the devd configuration (to chgrp the device nodes) > >>> in a port, security/u2f-

Re: Move u2f-devd into base?

gt; We have FIDO/U2F support for SSH in base. > >>> > >>> We also have a group "u2f", 116, in the default /etc/group file. > >>> > >>> Why do we keep the devd configuration (to chgrp the device nodes) > >>> in a port, security/u2f-

Re: Move u2f-devd into base?

On Mon, Jan 8, 2024 at 7:19 AM Warner Losh wrote: > > > On Mon, Jan 8, 2024, 7:55 AM Christian Weisgerber > wrote: > >> We have FIDO/U2F support for SSH in base. >> >> We also have a group "u2f", 116, in the default /etc/group file. >> &

Re: Move u2f-devd into base?

On 8 Jan 2024, at 16:30, Tomoaki AOKI wrote: > > So it should be in ports to adapt for latest products more quickly than > in base, I think. We push out a new release of each of the -STABLE branches every 6 months and can do ENs if a product ships and becomes popular in under six months. This

Re: Move u2f-devd into base?

On 1/8/24 10:30, Tomoaki AOKI wrote: On Mon, 8 Jan 2024 08:18:38 -0700 Warner Losh wrote: On Mon, Jan 8, 2024, 7:55〓AM Christian Weisgerber wrote: We have FIDO/U2F support for SSH in base. We also have a group "u2f", 116, in the default /etc/group file. Why do we kee

Re: Move u2f-devd into base?

On Mon, 8 Jan 2024 08:18:38 -0700 Warner Losh wrote: > On Mon, Jan 8, 2024, 7:55〓AM Christian Weisgerber > wrote: > > > We have FIDO/U2F support for SSH in base. > > > > We also have a group "u2f", 116, in the default /etc/group file. > > > >

Re: Move u2f-devd into base?

On Mon, Jan 8, 2024, 7:55 AM Christian Weisgerber wrote: > We have FIDO/U2F support for SSH in base. > > We also have a group "u2f", 116, in the default /etc/group file. > > Why do we keep the devd configuration (to chgrp the device nodes) > in a port, security/

Move u2f-devd into base?

We have FIDO/U2F support for SSH in base. We also have a group "u2f", 116, in the default /etc/group file. Why do we keep the devd configuration (to chgrp the device nodes) in a port, security/u2f-devd? Can't we just add this to base, too? It's just another devd configur

Re: snapshot 1st aarcch64 boot got devd error message: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"

On Dec 25, 2022, at 15:55, Warner Losh wrote: > Most likely MK_HYPERV is defaulting to no for aarch64? Or there is a bogus if > MACHINE_ARCH == "amd64" somewhere. Well, seems more is missing for aarch64 if devd hyperv is to be enabled: # grep -r MK_HYPERV /usr/main-src/

Re: snapshot 1st aarcch64 boot got devd error message: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"

Most likely MK_HYPERV is defaulting to no for aarch64? Or there is a bogus if MACHINE_ARCH == "amd64" somewhere. Warner On Sun, Dec 25, 2022, 4:28 PM Mark Millard wrote: > From the Dec 24 main [so: 14] snaphot for an aarch64 RPi* > system: > > . . . > Starting d

snapshot 1st aarcch64 boot got devd error message: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"

From the Dec 24 main [so: 14] snaphot for an aarch64 RPi* system: . . . Starting devd. genet0: link state changed to UP sh: /usr/libexec/hyperv/hyperv_vfattach: not found Starting dhclient. . . . This seems to be from /etc/devd/hyperv.conf : notify 10 { match "system"

Re: POLLHUP detected on devd socket

On Fri, Jan 28, 2022 at 02:54:25AM +, tech-lists wrote: On Sun, Jan 23, 2022 at 10:38:09PM +0300, Dima Panov wrote: Will try to play with zfsd disabled, as suggested. since reporting the issue and disabling zfsd, the problem has not re-occurred so far at this time (28th Jan) It's

Re: POLLHUP detected on devd socket

On Sun, Jan 23, 2022 at 10:38:09PM +0300, Dima Panov wrote: Will try to play with zfsd disabled, as suggested. since reporting the issue and disabling zfsd, the problem has not re-occurred so far at this time (28th Jan) -- J. signature.asc Description: PGP signature

Re: POLLHUP detected on devd socket

On Sun, Jan 23, 2022 at 1:07 PM Dima Panov wrote: > Moin! > > > I saw a such issue on amd64, both 13.0-RELEASE and -CURRENT. > Both hosts have zfsd enabled, and after devd die by signal 15 all other > daemons such as sshd, crond, syslogd (almost all runned daemons) stopeed

Re: POLLHUP detected on devd socket

On 23/01/2022 07:40, Daniel O'Connor wrote: It is very strange that devd dying would kill anything else running Because most likely it's a correlation, not causation. Many things die and among them devd. -- Andriy Gapon

Re: POLLHUP detected on devd socket

Moin! I saw a such issue on amd64, both 13.0-RELEASE and -CURRENT. Both hosts have zfsd enabled, and after devd die by signal 15 all other daemons such as sshd, crond, syslogd (almost all runned daemons) stopeed by signal 15 too. At least, as it shows by system logs. Will try to play with zfsd

Re: POLLHUP detected on devd socket

On Sun, Jan 23, 2022 at 04:10:40PM +1030, Daniel O'Connor wrote: Is it reproducible? ie can you trigger it post boot? It is very strange that devd dying would kill anything else running - I have stopped and started it a lot while testing devd scripts and I haven't seen anything else break

Re: POLLHUP detected on devd socket

> On 23 Jan 2022, at 01:04, tech-lists wrote: > context is a usb3-booting rpi4 running main-n252544-7406ec4ea99 > > I see this in /var/log/daemon.log: > > Jan 22 13:24:54 redacted zfsd[886]: POLLHUP detected on devd socket. > Jan 22 13:24:54 redacted zfsd[886]: Disconnec

POLLHUP detected on devd socket

Hi, context is a usb3-booting rpi4 running main-n252544-7406ec4ea99 I see this in /var/log/daemon.log: Jan 22 13:24:54 redacted zfsd[886]: POLLHUP detected on devd socket. Jan 22 13:24:54 redacted zfsd[886]: Disconnecting from devd. Jan 22 13:24:54 redacted zfsd[886]: ConnectToDevd: Connecting

HEADS UP: coming changes to a devd event

Greetings I just pushed https://svnweb.freebsd.org/changeset/base/364725 into -current. In documenting all the messages that devd can receive from the kernel, I noticed an inconsistency I'd like to correct. We currently have both system=kernel and system=kern generated by the kernel. This makes

Re: Inconsistent behavior with wpa / devd / network interfaces

On 5/30/19 1:25 PM, Miroslav Lachman wrote: > Greg Rivers wrote on 2019/05/30 18:37: > > [...] > >>> Do I have something weird in my setup causing this? I don't recall ever >>> having this issue when not using failover lagg. Running recent >>> 13-CURRENT. >>> >> I think there's a (unknown?)

Re: Inconsistent behavior with wpa / devd / network interfaces

This sounds like handbook material ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.

Re: Inconsistent behavior with wpa / devd / network interfaces

Greg Rivers wrote on 2019/05/30 18:37: [...] Do I have something weird in my setup causing this? I don't recall ever having this issue when not using failover lagg. Running recent 13-CURRENT. I think there's a (unknown?) problem that makes lagg(4) incompatible with bridge(4). I've never been

Re: Inconsistent behavior with wpa / devd / network interfaces

t;>>> ifconfig_bridge0="inet 192.168.8.1/24 addm lagg0 up" >>>> >>>> # Ethernet/WiFi failvoer >>>> ifconfig_em0="up" >>>> wlans_iwm0="wlan0" >>>> ifconfig_wlan0="WPA up" >>>> create_args_wlan0=&q

Re: Inconsistent behavior with wpa / devd / network interfaces

gt; # Ethernet/WiFi failvoer > >> ifconfig_em0="up" > >> wlans_iwm0="wlan0" > >> ifconfig_wlan0="WPA up" > >> create_args_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" > >> ifconfig_lagg0="laggproto failover laggport em

Re: Inconsistent behavior with wpa / devd / network interfaces

gs_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" >> ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP up" >> >> When I move between home and work networks and plug in the network cable >> it sometimes reconfigure and sometimes (mostly) not. Lookin

Re: Inconsistent behavior with wpa / devd / network interfaces

aggport em0 laggport wlan0 DHCP up" > > When I move between home and work networks and plug in the network cable > it sometimes reconfigure and sometimes (mostly) not. Looking at devd > output from a failed occasion and I can see that it calls dhclient on > em0 and not lagg0. But it si

Inconsistent behavior with wpa / devd / network interfaces

"wlan0" ifconfig_wlan0="WPA up" create_args_wlan0="wlanaddr xx:xx:xx:xx:xx:xx" ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP up" When I move between home and work networks and plug in the network cable it sometimes reconfigure and sometimes

Re: Devd / devmatch(8) -- netif race 12-RC1

Warner Losh writes: > coretemp is a CPU device, and so I'm not sure we have the right PNP > information for the CPU bus for it to even load. The coretemp device is not really a device, it's just a couple of MSRs. As such, it is not attached to an enumerable bus, or any bus at all that devd's

Re: Devd / devmatch(8) -- netif race 12-RC1

On Wed, Nov 21, 2018, 11:43 PM Dan Partelly wireless lagg initialization is broken in this scenario, all-right. The > init/rc system as it is now can’t cope easily with a modern asynchronous > initialization sequence. Sure you could probably find an order which works, > only to find yourself in

Re: Devd / devmatch(8) -- netif race 12-RC1

We're missing a fair bit of information to come to any conclusion yet. Cy, did you used it when loading the wifi drivers automatically with devmatcher ? Cause if you run GENERIC, chances are that you will not see any weird behavior. Most wifi drivers are compiled in kernel in this case.

Re: Devd / devmatch(8) -- netif race 12-RC1

In message <798c848d-5f32-4bf9-87e0-add4f9b74...@rdsor.ro>, Dan Partelly writes : > wireless lagg initialization is broken in this scenario, all-right. The init/ > rc system as it is now can’t cope easily with a modern asynchronous initial > ization sequence. Sure you could probably find an

Re: Devd / devmatch(8) -- netif race 12-RC1

wireless lagg initialization is broken in this scenario, all-right. The init/rc system as it is now can’t cope easily with a modern asynchronous initialization sequence. Sure you could probably find an order which works, only to find yourself in trouble next time you want add some modern

Re: Devd / devmatch(8) -- netif race 12-RC1

On 20 Nov 2018, at 8:17, dan_parte...@rdsor.ro wrote: No, that's not what's happening. wlan0 isn't racing anything, because it's no longer listed in ifconfig But when is created lagg0 ? Acording rc output on screen , creation of cloned interface lagg0 takes place before wlan0 is created.

Re: Devd / devmatch(8) -- netif race 12-RC1

failover on a machine running free-bsd. After reboot the system cannot complete the initialization sequence OK with devmatcher. The devd/devmatch(8) combo correctly identified the wireless card and loaded required drivers and firmware. rcorder(8) reports that devd(8) runs after netif. As far as I

Re: Devd / devmatch(8) -- netif race 12-RC1

On Mon, Nov 19, 2018 at 7:48 PM Dan Partelly wrote: > Hello, > > Today I tried a simple wireless failover on a machine running free-bsd. > After reboot the system cannot complete the initialization sequence OK with > devmatcher. > The devd/devmatch(8) combo correctly ident

Devd / devmatch(8) -- netif race 12-RC1

Hello, Today I tried a simple wireless failover on a machine running free-bsd. After reboot the system cannot complete the initialization sequence OK with devmatcher. The devd/devmatch(8) combo correctly identified the wireless card and loaded required drivers and firmware. rcorder(8) reports

Re: devd on head -r338675 on aarch64 (Pine64+ 2GB example) gets during booting: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"

On 9/14/18 11:24 AM, Mark Millard via freebsd-arm wrote: > From the boot of the Pine64+ 2GB for -r338675: > > . . . > Starting devd. > sh: /usr/libexec/hyperv/hyperv_vfattach: not found > add host 127.0.0.1: gateway lo0 fib 0: route already in table > . . . I got the same

devd on head -r338675 on aarch64 (Pine64+ 2GB example) gets during booting: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"

>From the boot of the Pine64+ 2GB for -r338675: . . . Starting devd. sh: /usr/libexec/hyperv/hyperv_vfattach: not found add host 127.0.0.1: gateway lo0 fib 0: route already in table . . . This seems to result from: # grep -r hyperv_vfattach /etc/ | more /etc/devd/hyperv.conf:# For transpar

netif not started by devd?

with latest current, but can tell when this stopped working, the wifi dongle is recognised, ie there is a net.wlan.devices, depending on the dongle it’s run0 or rtwn0 but only if I type service netif start does it become operational. so what am I missing? cheers, danny

Re: svn commit: r335753 - head/sbin/devd [ broke the ci.freebsd.org FreeBSD-head-{mips,mip64,powerpcpowerpc64,powerpcspe,sparc64}-build ]

D-head-powerpc64-build/6261/consoleText > > --- all_subdir_sbin/devd --- > /usr/src/sbin/devd/devd.cc: In member function 'std::string > config::shell_quote(const std::string&)': > /usr/src/sbin/devd/devd.cc:652: error: a function-definition is not allowed > here before '

Re: svn commit: r335753 - head/sbin/devd [ broke the ci.freebsd.org FreeBSD-head-{mips,mip64,powerpcpowerpc64,powerpcspe,sparc64}-build ]

On Wed, Jun 27, 2018, 7:27 PM Mark Millard wrote: > These are the gcc/g++ 4.2.1 based targets. > > For example . . . > > https://ci.freebsd.org/job/FreeBSD-head-powerpc64-build/6261/consoleText > > --- all_subdir_sbin/devd --- > /usr/src/sbin/devd/devd.cc: In memb

Re: gcc/g++ 4.2.1 -r334125 is getting devd related build failures on ci.freebsd.org

On 24 May 2018 at 03:34, Mark Millard wrote: > [This submittal is in part an experiment with how Eitan's > MUA classifies the Email using an alternate yahoo.com > address. Eitan: the subject and this note are all unique > to this message.] > > Gmail still considers all your

gcc/g++ 4.2.1 -r334125 is getting devd related build failures on ci.freebsd.org

[This submittal is in part an experiment with how Eitan's MUA classifies the Email using an alternate yahoo.com address. Eitan: the subject and this note are all unique to this message.] I've reported to Eitan that the gcc/g++ 4.2.1 architectures are failing for devd build failures. Examples

Re: gcc/g++ 4.2.1 -r334125 is getting devd related build failures on ci.freebsd.org

t; to this message.] > > I've reported to Eitan that the gcc/g++ 4.2.1 architectures > are failing for devd build failures. > > Examples include: > > --- all_subdir_sbin --- > cc1plus: warnings being treated as errors > /usr/obj/usr/src/sparc64.sparc64/tmp/usr/include/c++/4.2/bi

Re: r329501 devd doesn't find USB devices

;>>> loaded.  It's not clear from UPDATING whether I >>>> needed to do anything >>>> beyond building and installing kernel and world as >>>> well as updating >>>>

Re: r329501 devd doesn't find USB devices

>> On Feb 17, 2018 8:24 PM, "Ian FREISLICH" <ian.freisl...@capeaugusta.com> >>> wrote: >>> >>> Hi >>> >>> Since devmatch some of my USB devices no longer get their drivers >>> loaded. It's not clear from UPDATING whether I needed

Re: r329501 devd doesn't find USB devices

their drivers >>> loaded.  It's not clear from UPDATING whether I needed >>> to do anything >>> beyond building and installing kernel and world as well >>> as updating >>> /etc.  There

Re: r329501 devd doesn't find USB devices

It's not clear from UPDATING whether I needed to do > >>> anything > >>> beyond building and installing kernel and world as well as > >>> updating > >>> /etc.  There was reference to removing /etc/devd/usb.conf in >

Re: r329501 devd doesn't find USB devices

ded to do anything >> beyond building and installing kernel and world as well as updating >> /etc. There was reference to removing /etc/devd/usb.conf in another >> thread but its presence or lack thereof makes no difference. >> >> >> I assume you've fully updated includ

Re: r329501 devd doesn't find USB devices

Since devmatch some of my USB devices no longer get >> their drivers >> >>>      loaded.  It's not clear from UPDATING whether I needed to do >> >>> anything >> >>> beyond building and installing kernel and world as well

Re: r329501 devd doesn't find USB devices

ATING whether I needed to do >> anything >> beyond building and installing kernel and world as well as >> updating >> /etc.  There was reference to removing /etc/devd/usb.conf in >> another >> thread but its presence o

Re: r329501 devd doesn't find USB devices

of my USB devices no longer get their drivers > loaded. It's not clear from UPDATING whether I needed to do anything > beyond building and installing kernel and world as well as updating > /etc. There was reference to removing /etc/devd/usb.conf in another > thread but its presence or lac

Re: r329501 devd doesn't find USB devices

>>> loaded. It's not clear from UPDATING whether I needed to do > >>> anything > >>> beyond building and installing kernel and world as well as > >>> updating > >>> /etc. There was reference to removing /etc/devd/usb.conf in

Re: r329501 devd doesn't find USB devices

gt; >>> wrote: >>> >>> Hi >>> >>> Since devmatch some of my USB devices no longer get their drivers >>> loaded.  It's not clear from UPDATING whether I needed to do >>> anything >>> beyond building a

Re: r329501 devd doesn't find USB devices

ir drivers loaded.  It's not clear from UPDATING whether I needed to do anything beyond building and installing kernel and world as well as updating /etc.  There was reference to removing /etc/devd/usb.conf in another thread but its presence or lack thereof makes no difference.

Re: r329501 devd doesn't find USB devices

> loaded.  It's not clear from UPDATING whether I needed to do anything > beyond building and installing kernel and world as well as updating > /etc.  There was reference to removing /etc/devd/usb.conf in another > thread but its presence or lack thereof makes no differe

Re: r329501 devd doesn't find USB devices

as updating /etc. There was reference to removing /etc/devd/usb.conf in another thread but its presence or lack thereof makes no difference. I assume you've fully updated including /etc. if_ure: ugen0.6: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (72mA) bLength = 0x0012 bDescrip

r329501 devd doesn't find USB devices

Hi Since devmatch some of my USB devices no longer get their drivers loaded.  It's not clear from UPDATING whether I needed to do anything beyond building and installing kernel and world as well as updating /etc.  There was reference to removing /etc/devd/usb.conf in another thread but its

Re: devd in r329188M don't start

make snide comments like this, along with drive by commits to >> devmatch without even discussing the problems with me. It's really pissing >> me off. >> > > Are you using a different shell then? It did not work for me, and several > others. Did you also check you've remo

Re: devd in r329188M don't start

pissing me off. Are you using a different shell then? It did not work for me, and several others. Did you also check you've removed the old /etc/devd/usb.conf ?? And did you check no errors were in the console? --HPS ___ freebsd-current@freebsd.org

Re: devd in r329188M don't start

On Sat, Feb 17, 2018 at 6:31 AM, Hans Petter Selasky wrote: > On 02/17/18 11:38, Alex V. Petrov wrote: > >> 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: >> on boot multilines: >> >> devmatch: Malformed NOMATCH string: ''?'' >> >> > Can you try these two patches: > >

Re: devd in r329188M don't start

On 02/17/18 15:22, Alex V. Petrov wrote: Sorry, prev msg this only afrer one patch. Now is all OK. There is one more, but not so important: https://svnweb.freebsd.org/changeset/base/329458 Thank for your testing! --HPS ___

Re: devd in r329188M don't start

Sorry, prev msg this only afrer one patch. Now is all OK. 17.02.2018 21:18, Hans Petter Selasky пишет: > On 02/17/18 14:51, Alex V. Petrov wrote: >> devmatch: Malformed NOMATCH string: ''?'' persists >> >> > > Did you reinstall /etc ? > > --HPS > > -- - Alex.

Re: devd in r329188M don't start

On 02/17/18 14:51, Alex V. Petrov wrote: devmatch: Malformed NOMATCH string: ''?'' persists Did you reinstall /etc ? --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe,

Re: devd in r329188M don't start

devmatch: Malformed NOMATCH string: ''?'' persists 17.02.2018 20:31, Hans Petter Selasky пишет: > On 02/17/18 11:38, Alex V. Petrov wrote: >> 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: >> on boot multilines: >> >> devmatch: Malformed NOMATCH string: ''?'' >> > > Can you try these

Re: devd in r329188M don't start

On 02/17/18 11:38, Alex V. Petrov wrote: 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: on boot multilines: devmatch: Malformed NOMATCH string: ''?'' Can you try these two patches: https://svnweb.freebsd.org/changeset/base/329455 https://svnweb.freebsd.org/changeset/base/329456

Re: devd in r329188M don't start

ine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.ko was loaded by devd before. >> > > Hi, > > This is a known issue. > > Can you try the attached patch? > > Rebuild devmatch(8) and reinst

Re: devd in r329188M don't start

My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd before. Hi, This is a known issue. Can you try the attached patch? Rebuil

Re: devd in r329188M don't start

devmatch. Now I have >>> to 'kldload ums' manually. >>> >>> Same for USB audio, snd_uaudio.ko was loaded by devd before. >>> >>> >> Hi, >> >> This is a known issue. >> >> Can you try the attached patch? >> >>

Re: devd in r329188M don't start

Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky: On 02/13/18 10:47, Jakob Alvermark wrote: +1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd before. Hi, This is a known issue

Re: devd in r329188M don't start

On 13/02/2018 23:50, Hans Petter Selasky wrote: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.k

Re: devd in r329188M don't start

Yes, it seems to be working. Thanks! Jakob On 02/13/18 13:50, Hans Petter Selasky wrote: On 02/13/18 10:47, Jakob Alvermark wrote: +1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd

Re: devd in r329188M don't start

Yes, for me it works. Thank you. 13.02.2018 19:50, Hans Petter Selasky пишет: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB

Re: devd in r329188M don't start

On 02/13/18 10:47, Jakob Alvermark wrote: +1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd before. Hi, This is a known issue. Can you try the attached patch? Rebuild devmatch(8

Re: devd in r329188M don't start

+1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd before. Jakob On 02/13/18 10:34, Alex V. Petrov wrote: Why is not the driver loaded when the mouse is connected? 13.02.2018 16:19

Re: devd in r329188M don't start

Why is not the driver loaded when the mouse is connected? 13.02.2018 16:19, Hans Petter Selasky пишет: > On 02/13/18 10:20, Alex V. Petrov wrote: >> usb.conf is not found anywhere in the system. This is normal? > > devmatch is supposed to replace usb.conf . The contents of usb.conf is > now part

Re: devd in r329188M don't start

On 02/13/18 10:20, Alex V. Petrov wrote: usb.conf is not found anywhere in the system. This is normal? devmatch is supposed to replace usb.conf . The contents of usb.conf is now part of the linker hints, /boot/kernel/linker.hints . --HPS ___

Re: devd in r329188M don't start

Mouse start work only after handly: kldload ums usb.conf is not found anywhere in the system. This is normal? 13.02.2018 15:08, Hans Petter Selasky пишет: > On 02/13/18 09:02, Alex V. Petrov wrote: >> after update, devd don't starting with: >> devd: Cannot parse /etc/devd/devmat

Re: devd in r329188M don't start

In /var/log/messages: devd: line 13: }: syntax error File /etc/devd/devmatch.conf (11-13 lines): nomatch 100 { action "service devmatch start" }; 13.02.2018 15:08, Hans Petter Selasky пишет: > On 02/13/18 09:02, Alex V. Petrov wrote: >> after update, devd don't sta

Re: devd in r329188M don't start

On 02/13/18 09:02, Alex V. Petrov wrote: after update, devd don't starting with: devd: Cannot parse /etc/devd/devmatch.conf at line 13 (file default!) If I disable it, don't work mouse in xorg. https://svnweb.freebsd.org/changeset/base/329194 --HPS

Re: devd in r329188M don't start

On 02/13/18 09:02, Alex V. Petrov wrote: after update, devd don't starting with: devd: Cannot parse /etc/devd/devmatch.conf at line 13 (file default!) If I disable it, don't work mouse in xorg. I think there is a missing ";" at the end of line 13. Try adding o

devd in r329188M don't start

after update, devd don't starting with: devd: Cannot parse /etc/devd/devmatch.conf at line 13 (file default!) If I disable it, don't work mouse in xorg. -- - Alex. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman

D12420 fix the misleading log facility used in devd/zfs.conf

https://reviews.freebsd.org/D12420 Who would be the best people to review this change? Where are they lurking? Please point me towards them or add yourself as a reviewer if you are one of them :) Thanks! -- Andriy Gapon ___ freebsd-current@freebsd.org

Re: Where should I put devd related scripts?

Hi. Usually, you should put configuration files (looked in by devd) on /usr/local/etc/devd, and actual executables (specified by the configuration files) on /usr/local/sbin/. sysutils/automount would be a good example. See its port Makefile. Don't forget that actual installation directory

Where should I put devd related scripts?

Hi all, Where should I put devd related scripts? Thanks, sephe -- Tomorrow Will Never Die ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-cu

Re: devd limitations -- was [CFT] packaging the base system with pkg(8)

> Ideally, when the automounter daemon starts, it should > connect to devd via an IPC channel and request notification of the specific > events that it wants I was under the impression that devd.seqpacket.pipe accomplishes this. Am I right in assuming that the issue is that devd for

devd problem after recent upgrade

I just upgraded to svn r263756 and have a major problem, the system has no mouse. When I reboot I see the following message on the console: devd:devctl sysctl missing from kernel then /etc/rc.d failed to start devd, and also I had to run dhclient em0 to get the network started. I have

Re: devd problem after recent upgrade

On Tue, Mar 25, 2014 at 09:31:57PM -0400, AN wrote: I just upgraded to svn r263756 and have a major problem, the system has no mouse. When I reboot I see the following message on the console: devd:devctl sysctl missing from kernel then /etc/rc.d failed to start devd, and also I had

Re: devd problem after recent upgrade

kernel then /etc/rc.d failed to start devd, and also I had to run dhclient em0 to get the network started. I have not added to or changed any config files. Has anyone else seen strange behavior like this recently? Any help would be appreciated. That's my fault, I'll fix

Re: devd problem after recent upgrade

on the console: devd:devctl sysctl missing from kernel then /etc/rc.d failed to start devd, and also I had to run dhclient em0 to get the network started. I have not added to or changed any config files. Has anyone else seen strange behavior like this recently? Any help would be appreciated. That's

r255763/i386 cannot start devd with default config, network doesn't work too, because DHCP is started by devd, sshd complains about config, passwd could not change password

it doesn't contains any leftovers. devd cannot start with strange diagnostic: devd: Cannot parse /etc/devd.conf at line 202 Line 202 is: == 201 nomatch 10 { 202 match bus pccard[0-9]+; 203 action logger Unknown PCCARD device: manufacturer $manufacturer \ 204

devd or dhclient or ifconfig behavior seems broken

00:05:04 laptop-kargl devd: Executing '/etc/rc.d/dhclient quietstart wlan0 So, devd is firing off a new dhclient. This has never occurred before. But, to make matters worse. The new dhclient appears to be nuking /etc/resolv.conf. Has anyone seen such behavior? How do I stop devd

Re: devd or dhclient or ifconfig behavior seems broken

Check the man page for dhclient.conf. You can use the supercede functionality to always force the settings you prefer. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to

Re: devd or dhclient or ifconfig behavior seems broken

On Thu, Jul 04, 2013 at 08:50:21AM -0500, Mark Felder wrote: Check the man page for dhclient.conf. You can use the supercede functionality to always force the settings you prefer. Thanks for the suggestion. I was trying to use resolvconf.conf to put specific nameservers into resolv.conf, but

  1   2   3   >