SOLVED: Beowulf: quite good, but ......

HevyDevy · 2020-06-25 00:09:39

Head_on_a_Stick wrote:

HevyDevy wrote:
Tseems xserver-xorg-video-intel package provides the free as in freedom i915 driver
No, that package provides the Intel DDX driver. The kernel provides the i915 driver.
HevyDevy wrote:
you can go further and enable non-free drivers if you like from package firmware-misc-nonfree
There are no non-free Intel drivers. The firmware-misc-nonfree package provides the non-free firmware that is required by all recent Intel cards for full performance.
The parameters you are applying are for framebuffer compression (fbc, to reduce power consumption and memory bandwidth needed for screen refreshes) and to enable GuC/HuC firmware loading. Note that GuC/HuC firmware can cause freezing on some systems, which is why it is disabled by default.

Okay, so as it states in debian packages one could safely disregard xserver-xorg-video-intel if installed?

https://packages.debian.org/buster/xser … ideo-intel
The use of this driver is discouraged if your hw is new enough (ca. 2007 and newer). You can try uninstalling this driver and let the server use its builtin modesetting driver instead.

I should have said binary blob firmware not driver you are correct there. Ive not noticed any freezing on my system and it has been on for over 8 hours. But yes as a precaution that gist i linked to says...

You will note that many options default to -1, resulting in per-chip power-saving defaults. It is however possible to configure more aggressive powersaving by using module options. Warning: Diverting from the defaults will mark the kernel as tainted from Linux 3.18 onwards. This basically implies using other options than the per-chip defaults is considered experimental and not supported by the developers.

berni51 · 2020-06-25 10:44:30

So it was probably better, that I had no time yesterday.
Today ist the 3rd day my Beowulf is running nonstop. Looks like the new kernel has solved the problem. OK, now I have crazy messages in dmesg like "udev[464]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14", but however everthing works.
Does anybody know what my Brother scanner has to do with udev?

Debuser2018 · 2020-06-25 11:22:08

With Beowulf, boot time takes almost 3 minutes due to udev waiting and time out. This happens with kernel 5.6 from beowuf-backports. I've posted here:https://dev1galaxy.org/viewtopic.php?pid=22907
No clues why this is happening.

berni51 · 2020-06-25 15:58:39

Have installed the 5.5 kernel and the systems boots very fast, less than 1 minute.

rolfie · 2020-06-25 17:00:25

Debuser2018 wrote:

With Beowulf, boot time takes almost 3 minutes due to udev waiting and time out. This happens with kernel 5.6 from beowuf-backports. I've posted here:https://dev1galaxy.org/viewtopic.php?pid=22907
No clues why this is happening.

Got Beowulf on kernel 5.6 running fine on two desktop machines. You must have individual hickups, hardware problems or a device that having issues.

rolfie

Debuser2018 · 2020-06-25 17:08:43

Kernel 4.19 boots fine. But, it is the 5.6 bpo that is having udev worker timing out.

Head_on_a_Stick · 2020-06-25 20:26:39

HevyDevy wrote:

Okay, so as it states in debian packages one could safely disregard xserver-xorg-video-intel if installed?

The Intel DDX driver is reportedly buggy but it does have advantages over the modesetting driver — xbacklight only works with xserver-xorg-video-intel, performance is (slightly) better and it offers a TearFree option to eliminate screen tearing (which can be a problem with Intel video cards), unlike the modesetting driver.

PedroReina · 2020-06-26 08:50:35

berni51 wrote:

Does anybody know what my Brother scanner has to do with udev?

https://support.brother.com/g/b/faqend. … 100604_000
and search for udev...

berni51 · 2020-06-26 10:49:49

Thanks for the recherche, Pedro. Even if I do not really know, what I did, I followed the hints for Debian 6. This modification reduced the error messages dramatically.
Now I only get this durig startup:
5.119158] udevd[459]: specified group 'kvm' unknown
[ 5.121437] udevd[459]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9
[ 5.121559] udevd[459]: invalid rule '/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9'
[ 5.122021] udevd[459]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14
[ 5.122138] udevd[459]: invalid rule '/etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14'

However Brother printers and scanners work perfect.

Last edited by berni51 (2020-06-26 10:56:19)

PedroReina · 2020-06-26 14:41:57

berni51 wrote:

Thanks for the recherche, Pedro.

Not really a recherche. I've spend my time in support Brother pages because I have a bunch of Brother devices.

berni51 wrote:

However Brother printers and scanners work perfect.

Indeed. That is the very reason of buying again. Remember: "put your money where your mouth is".

berni51 wrote:

[ 5.121437] udevd[459]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9
[ 5.121559] udevd[459]: invalid rule '/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9'
[ 5.122021] udevd[459]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14
[ 5.122138] udevd[459]: invalid rule '/etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14'

Could you quote here these two offending files?

berni51 · 2020-06-26 18:02:01

Yes Sir. Here are the two files:

/etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules
=============================================================
#
# udev rules
#

ACTION!="add", GOTO="brother_mfp_end"
SUBSYSTEM=="usb", GOTO="brother_mfp_udev_1"
SUBSYSTEM!="usb_device", GOTO="brother_mfp_end"
LABEL="brother_mfp_udev_1"
SYSFS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
ATTRS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
GOTO="brother_mfp_end"
LABEL="brother_mfp_udev_2"
ATTRS{bInterfaceClass}!="0ff", GOTO="brother_mfp_end"
ATTRS{bInterfaceSubClass}!="0ff", GOTO="brother_mfp_end"
ATTRS{bInterfaceProtocol}!="0ff", GOTO="brother_mfp_end"
#MODE="0666"
#GROUP="scanner"
ENV{libsane_matched}="yes"
#SYMLINK+="scanner-%k"
LABEL="brother_mfp_end"
--------------------------------------------------------------
/etc/udev/rules.d/60-brother-libsane-type1-inst.rules
=========================================================
#
# udev rules sample for Brother MFP
# version 1.0.2-0
#
# Copyright (C) 2012-2017 Brother. Industries, Ltd.
#
# copy to /etc/udev/rules.d or /lib/udev/rules.d
#

ACTION!="add", GOTO="brother_mfp_end"
SUBSYSTEM=="usb", GOTO="brother_mfp_udev_1"
SUBSYSTEM!="usb_device", GOTO="brother_mfp_end"
LABEL="brother_mfp_udev_1"
SYSFS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
ATTRS{idVendor}=="04f9", GOTO="brother_mfp_udev_2"
GOTO="brother_mfp_end"
LABEL="brother_mfp_udev_2"
ATTRS{bInterfaceClass}!="0ff", GOTO="brother_mfp_end"
ATTRS{bInterfaceSubClass}!="0ff", GOTO="brother_mfp_end"
ATTRS{bInterfaceProtocol}!="0ff", GOTO="brother_mfp_end"
#MODE="0666"
#GROUP="scanner"
ENV{libsane_matched}="yes"
#SYMLINK+="scanner-%k"
LABEL="brother_mfp_end"

It must be mentioned that the Brother printers (5 x DCPJ525W) are all connected by Wifi, not via USB. The Beowulf machine serves the printers for that machines, which don't have drivers for the printers, e.g. computers with OpenBSD and NetBSD.
That works fine, independent from the error messages in the logfile.

Last edited by berni51 (2020-06-26 18:11:05)

PedroReina · 2020-06-26 21:14:23

berni51 wrote:

udevd[459]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-brscan4-libsane-type1.rules:9

IMHO, Brother has not changed the syntax of these files:
http://www.planet-libre.org/index.php?post_id=10937

i.e.: change 'SYSFS' by 'ATTR'. Could you try?

I know that you know, but may be some newbie is reading this: do a backup before edit the files!

berni51 · 2020-06-27 08:08:25

Change by ATTR or ATTRS?

berni51 · 2020-06-27 08:17:22

Changing to ATTR now brings again one error message less than before:

[ 2.607622] udevd[132]: starting version 3.2.7
[ 2.610145] udevd[133]: starting eudev-3.2.7
[ 5.010561] udevd[461]: starting version 3.2.7
[ 5.025778] udevd[461]: specified group 'kvm' unknown
[ 5.028777] udevd[461]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14
[ 5.028904] udevd[461]: invalid rule '/etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14'
[ 5.073976] udevd[461]: starting eudev-3.2.7

Last edited by berni51 (2020-06-27 08:18:41)

PedroReina · 2020-06-27 09:32:10

berni51 wrote:

Changing to ATTR now brings again one error message less than before:
[ 5.028777] udevd[461]: unknown key 'SYSFS{idVendor}' in /etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14
[ 5.028904] udevd[461]: invalid rule '/etc/udev/rules.d/60-brother-libsane-type1-inst.rules:14'
[ 5.073976] udevd[461]: starting eudev-3.2.7

Time to change syntax in 60-brother-libsane-type1-inst.rules too.

berni51 · 2020-06-27 09:44:25

I did so and now .....perfect, Pedro! No more error messages from Brother drivers. Thanks a lot.

PedroReina · 2020-06-27 14:22:05

berni51 wrote:

I did so and now .....perfect, Pedro! No more error messages from Brother drivers. Thanks a lot.

I'm glad to know. Happy to help

golinux · 2020-06-27 14:29:13

Congrats! Please mark as solved then.

The officially official Devuan Forum!

#26 2020-06-25 00:09:39

Re: SOLVED: Beowulf: quite good, but ......

#27 2020-06-25 10:44:30

Re: SOLVED: Beowulf: quite good, but ......

#28 2020-06-25 11:22:08

Re: SOLVED: Beowulf: quite good, but ......

#29 2020-06-25 15:58:39

Re: SOLVED: Beowulf: quite good, but ......

#30 2020-06-25 17:00:25

Re: SOLVED: Beowulf: quite good, but ......

#31 2020-06-25 17:08:43

Re: SOLVED: Beowulf: quite good, but ......

#32 2020-06-25 20:26:39

Re: SOLVED: Beowulf: quite good, but ......

#33 2020-06-26 08:50:35

Re: SOLVED: Beowulf: quite good, but ......

#34 2020-06-26 10:49:49

Re: SOLVED: Beowulf: quite good, but ......

#35 2020-06-26 14:41:57

Re: SOLVED: Beowulf: quite good, but ......

#36 2020-06-26 18:02:01

Re: SOLVED: Beowulf: quite good, but ......

#37 2020-06-26 21:14:23

Re: SOLVED: Beowulf: quite good, but ......

#38 2020-06-27 08:08:25

Re: SOLVED: Beowulf: quite good, but ......

#39 2020-06-27 08:17:22

Re: SOLVED: Beowulf: quite good, but ......

#40 2020-06-27 09:32:10

Re: SOLVED: Beowulf: quite good, but ......

#41 2020-06-27 09:44:25

Re: SOLVED: Beowulf: quite good, but ......

#42 2020-06-27 14:22:05

Re: SOLVED: Beowulf: quite good, but ......

#43 2020-06-27 14:29:13

Re: SOLVED: Beowulf: quite good, but ......

Board footer