RPi4 neu mit Buster OS, HM-Cfg-USB und OW server - FHEM nach Restore BU na

Begonnen von Helmi55, 17 August 2019, 22:12:17

Vorheriges Thema - Nächstes Thema

Helmi55

#erledigt# Guten Abend
habe einen neuen RPi4 mit neuer SD Karte mit Buster Light aufgesetzt.
Hier der genaue Vorgang
OS aufspielen

sudo raspi-config


Systemupdate
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt-get autoclean

Unbedingt
sudo apt-get update
und Neustart

sudo apt-get -f install && sudo apt-get install perl libdevice-serialport-perl libio-socket-ssl-perl libwww-perl libxml-simple-perl libjson-perl sqlite3 libdbd-sqlite3-perl libtext-diff-perl -y

JSON installieren
sudo apt-get install libjson-perl

libdatetime (für Wettermodul)
sudo apt-get install libdatetime-format-strptime-perl



NODE.js installieren

curl -o node-v9.9.0-linux-armv6l.tar.gz https://nodejs.org/dist/v9.9.0/node-v9.9.0-linux-armv6l.tar.gz

tar -xzf node-v9.9.0-linux-armv6l.tar.gz

sudo cp -r node-v9.9.0-linux-armv6l/* /usr/local/

Überprüfen mit
node -v
npm -v

sudo apt-get install git


FHEM installieren

sudo wget http://fhem.de/fhem-5.9.deb && sudo dpkg -i fhem-5.9.deb

Nach Fehlermeldung weiter mit:

sudo apt-get install -f

sudo rm fhem-5.9.deb

Rechte

cd /opt
sudo chmod -R a+w fhem
sudo usermod -a -G tty pi && sudo usermod -a -G tty fhem


sudo reboot



OW Server installieren

https://wiki.fhem.de/wiki/OWServer_%26_OWDevice

sudo apt-get install owserver ow-shell owhttpd owftpd

Bei einer Fehlermeldung:   sudo apt-get purge
sudo apt-get update
sudo apt-get dist-upgrade

Version überprüfen
/usr/bin/owhttpd -V

3.2p3
libow version:
3.2p3

Schreibrechte um die owfs.conf zu kopieren
cd /etc
sudo chmod -R 777 owfs.conf

Schreibrechte um 11-onwire.rules nach cd /etc/udev/rulres.d zu kopieren
Cd /etc/udev sudo chmod -R 777 rules.d




HM-Cfg-USB Einrichten

https://wiki.fhem.de/wiki/HM-CFG-USB_USB_Konfigurations-Adapter

cd /opt/

sudo apt-get install build-essential libusb-1.0-0-dev make gcc git-core

sudo git clone git://git.zerfleddert.de/hmcfgusb

cd hmcfgusb
sudo make

Bei Distributionen, die systemd einsetzen (z.B. Debian Stretch) kann folgende Konfigurationsdatei verwendet werden:
[Unit]
Description=Homematic LAN Adapter service
After=network.target
[Service]
ExecStart=/usr/local/bin/hmland -p 1234
[Install]
WantedBy=multi-user.target
Dabei muss dann natürlich der Port (1234) an die eigene Konfiguration angepasst werden und auch der Pfad wo sich der hmland befindet, wenn man sich an oben stehendem Beispiel orientiert wäre das dann /opt/hmcfgusb/
Diese Datei muss dann als hmland.service unter
/etc/systemd/system
abgelegt werden.
Nun muss einmalig der Befehl
systemctl daemon-reload
ausgeführt werden damit die neuen Dateien eingelesen werden. Mit dem Befehl
systemctl enable hmland
wird dafür gesorgt, dass bei einem Systemstart hmland automatisch gestartet wird Mit
systemctl status hmland
kann dann noch geprüft werden ob der Service läuft


Sicher habe ich hier bei den Berechtigungen nicht optimal gehandelt aber es hat funktioniert.

Vor dem Aufspielen von OW Server und Hm-cfg-USB konnte ich FHEM erreichen da ich hier ein update ausgeführt habe.

Habe alles Sticks vom alten abgesteckt und den neuen damit gestartet.

In der Konsole am MAC kann ich den Pi mit ssh erreichen, ein stoppen und neu starten von FHEM mit

sudo systemctl stop fhem
sudo systemctl start fhem

hilft leider auch nicht.

Ein sudo systemctl status fhem liefert das

pi@RPiGarageneu:~ $ sudo systemctl status fhem
● fhem.service - FHEM Home Automation
   Loaded: loaded (/etc/systemd/system/fhem.service; enabled; vendor preset: ena
   Active: failed (Result: exit-code) since Sat 2019-08-17 16:31:36 CEST; 3h 41m

Aug 17 16:31:36 RPiGarageneu systemd[1]: fhem.service: Service RestartSec=100ms
Aug 17 16:31:36 RPiGarageneu systemd[1]: fhem.service: Scheduled restart job, re
Aug 17 16:31:36 RPiGarageneu systemd[1]: Stopped FHEM Home Automation.
Aug 17 16:31:36 RPiGarageneu systemd[1]: fhem.service: Start request repeated to
Aug 17 16:31:36 RPiGarageneu systemd[1]: fhem.service: Failed with result 'exit-
Aug 17 16:31:36 RPiGarageneu systemd[1]: Failed to start FHEM Home Automation.
lines 1-10/10 (END)


Im Logfile sind keine Einträge?


Was mach ich falsch? Wer kann mir bitte weiterhelfen

Danke
LG
Helmut

System1 fhem 6.1 auf RPi 4B mit 4GB, HMUSBConfig, DS9490R-1Wire, Busware USB 868, Pool-Solarsteuerung mit FHEM. System2 fhem 6.1 auf RPi 4B mit 4GB (Bullseye) mit Busware USB 868 und 433 und HMUARTLGW für Haussteuerung

https://www.flickr.com/photos/canonhelmi/

Christoph Morrison

Setzt mal in der fhem.cfg global verbose auf 5 und stacktrace auf 1 und dann startest du den Service neu.
Steht im FHEM-Logfile wirklich gar nichts? Kann ich kaum glauben.

Helmi55

Servus
Da ich auf Fhem nicht komme kann ich nur über die Konsole das editieren?
Oder wie sonst? 
System1 fhem 6.1 auf RPi 4B mit 4GB, HMUSBConfig, DS9490R-1Wire, Busware USB 868, Pool-Solarsteuerung mit FHEM. System2 fhem 6.1 auf RPi 4B mit 4GB (Bullseye) mit Busware USB 868 und 433 und HMUARTLGW für Haussteuerung

https://www.flickr.com/photos/canonhelmi/

Christoph Morrison

Genau. Du musst dazu die fhem.cfg direkt über die Kommandozeile editieren.

Helmi55

Guten Morgen,
ich verstehe das leider nicht mehr.
Habe jetzt mit einem editor - so wie man es nicht machen soll - die fhem.cfg editieren wollen.
Kann aber nicht mehr speichern (auch wenn ich die gesamte Datei herunterladen und wieder hoch)
sudo chmod -R 777 /opt/fhem/fhem.cfg war mein Befehl?
Bekomme immer zurück " Das Dateisystem ist nur lesbar"?

Was mache ich oder habe ich falsch gemacht?
Danke für den Support

LG
Helmut
System1 fhem 6.1 auf RPi 4B mit 4GB, HMUSBConfig, DS9490R-1Wire, Busware USB 868, Pool-Solarsteuerung mit FHEM. System2 fhem 6.1 auf RPi 4B mit 4GB (Bullseye) mit Busware USB 868 und 433 und HMUARTLGW für Haussteuerung

https://www.flickr.com/photos/canonhelmi/

Christoph Morrison

Zitat von: Helmi55 am 18 August 2019, 11:20:36
sudo chmod -R 777 /opt/fhem/fhem.cfg war mein Befehl?

Das kann unmöglich alles gewesen sein, was du getan hast. Poste mal bitte den Output von history (als user und als root).
Wenn ich chmod -R 777 /opt/fhem/fhem.cfg ausführen, ändert das auch nur /opt/fhem/fhem.cfg. -R ist hier auf jeden Fall unnötig.

Helmi55

Ich glaube da hat die SD Karte (neu) etwas abbekommen.
Ich kann auch kein sudo apt-get update mehr ausführen
Bekomme auch hier die Meldung Dateisystem nur lesbar.
Ich glaube das heißt für mich wieder ran an den Start oder ?
Hier die history
pi@RPiGarageneu:~ $ history
    1  sudo raspi-config
    2  sudo apt-get update
    3  sudo apt-get upgrade
    4  sudo apt-get dist-upgrade
    5  sudo apt-get autoclean
    6  sudo apt-get update
    7  sudo reboot
    8  sudo apt-get -f install && sudo apt-get install perl libdevice-serialport-perl libio-socket-ssl-perl libwww-perl libxml-simple-perl libjson-perl sqlite3 libdbd-sqlite3-perl libtext-diff-perl -y
    9  sudo apt-get install libjson-perl
   10  sudo apt-get install libdatetime-format-strptime-perl
   11  curl -o node-v9.9.0-linux-armv6l.tar.gz https://nodejs.org/dist/v9.9.0/node-v9.9.0-linux-armv6l.tar.gz
   12  tar -xzf node-v9.9.0-linux-armv6l.tar.gz
   13  sudo cp -r node-v9.9.0-linux-armv6l/* /usr/local/
   14  node -v
   15  npm -v
   16  sudo apt-get install git
   17  sudo wget http://fhem.de/fhem-5.9.deb && sudo dpkg -i fhem-5.9.deb
   18  sudo apt-get install -f
   19  sudo rm fhem-5.9.deb
   20  cd /opt
   21  sudo chmod -R a+w fhem
   22  sudo usermod -a -G tty pi && sudo usermod -a -G tty fhem
   23  sudo reboot
   24  cd /etc
   25  sudo chmod 777 owfs.conf
   26  cd ..
   27  sudo apt-get install owserver ow-shell owhttpd owftpd
   28  sudo apt-get purge
   29  sudo apt-get update
   30  sudo apt-get dist-upgrade
   31  /usr/bin/owhttpd -V
   32  cd /etc
   33  sudo chmod -R 777 owfs.conf
   34  cd ...
   35  cd ..
   36  sudo reboot
   37  sudo install mc
   38  sudo apt-get install mc -y
   39  mc
   40  cd /etc/udev
   41  sudo chmod -R 777
   42  sudo chmod -R 777 11-onewire.rules
   43  sudo chmod -R 777 rules.d
   44  sudo reboot
   45  mc
   46  cd /opt/
   47  sudo apt-get install build-essential libusb-1.0-0-dev make gcc git-core
   48  git clone git://git.zerfleddert.de/hmcfgusb
   49  sudo git clone git://git.zerfleddert.de/hmcfgusb
   50  cd hmcfgusb
   51  sudo make
   52  sudo reboot
   53  /opt/hmcfgusb/hmland -p 1234 -D
   54  sudo reboot
   55  sudo chmod -R 777 /etc/systemd/system/hmland.service
   56  sudo chmod -R 777 /etc/systemd/system
   57  sudo reboot
   58  systemctl daemon-reload
   59  sudo systemctl daemon-reload
   60  sudo systemctl status hmland
   61  sudo systemctl daemon-reload
   62  sudo systemctl enable hmland
   63  sudo systemctl status hmland
   64  sudo reboot
   65  sudo tar -xvzf /home/pi/FHEM-20190817_161728.tar.gz -C /opt/fhem/
   66  sudo raspi-cobfig
   67  sudo raspi-config
   68  history
pi@RPiGarageneu:~ $


Danke für deine Hilfe und Geduld
LG
Helmut
System1 fhem 6.1 auf RPi 4B mit 4GB, HMUSBConfig, DS9490R-1Wire, Busware USB 868, Pool-Solarsteuerung mit FHEM. System2 fhem 6.1 auf RPi 4B mit 4GB (Bullseye) mit Busware USB 868 und 433 und HMUARTLGW für Haussteuerung

https://www.flickr.com/photos/canonhelmi/

MadMax-FHEM

Gib doch mal 'mount' ein.
Evtl. ist beim Boot etwas "passiert" und dein Dateisystem wurde nur 'ro' (read only) gemountet...

Und warum immer (gleich) mit "Rechtebastelei" auf ein (Linux) System losgegangen wird (nicht nur hier) ist mir ein Rätsel...

Gruß, Joachim
FHEM PI3B+ Bullseye: HM-CFG-USB, 40x HM, ZWave-USB, 13x ZWave, EnOcean-PI, 15x EnOcean, HUE/deCONZ, CO2, ESP-Multisensor, Shelly, alexa-fhem, ...
FHEM PI2 Buster: HM-CFG-USB, 25x HM, ZWave-USB, 4x ZWave, EnOcean-PI, 3x EnOcean, Shelly, ha-bridge, ...
FHEM PI3 Buster (Test)

Christoph Morrison

Als erstes fällt mir auf, dass du FHEM nicht nach der Anleitung von debian.fhem.org - The easy way - installierst. Das solltest du unbedingt tun.
Zweitens installierst du auch node manuell, das solltest du auch nicht tun.
Drittens: 777 sind viel zu liberale Rechte, egal für was. Jeder(!) kann lesen, schreiben, löschen etc. Man muss nur ganz selten etwas an den Rechten ändern.
Viertens: Nirgendwo ist da ein chmod auf /opt/fhem/fhem.cfg zu sehen. Das kann nicht alles sein.
Fünftens: Du spielst eine Sicherung ein. Vermutlich ist ein Problem schon in der Sicherung. Setz lieber neu auf und kopiere Inhalte nur nach genauer Prüfung auf das neue System.

Ich weiß dass das alles viel Zeug ist, aber du schaffst das. Halte dich wo's geht an apt und vermeide 777er Rechte.

Helmi55

Hallo
ok werde nochmals neu beginnen
Bin nach meinen Aufzeichnungen vorgegangen werde jetzt nach Debian.fhem.org vorgehen.
zu 4. Das /opt/fhem/fhem.cfg habe ich auch erst ganz zum Schluss machen wollen und das greift nicht ....
5. Das BU habe ich ganz aktuell von meinem  Produktionssystem gezogen und dort läuft es. Aber du hast recht,
ich werde Stück für Stück kopieren

Und zu 3. - ja mit den Rechten stehe ich auf Kriegsfuss. Das muss ich mir noch genauer ansehen.
Hier in dem Fall mit der Berechtigung für die fhem.cfg wäre es nur darum gegangen die Datei schnell einmal zurück zu kopieren.
denn das ist ja sowie so VERBOTEN

Zum Glück ist der Sonntag noch jung und ich werde mich an die Sache machen.
Danke
Helmut

PS. mount hat auch nix gebracht - Danke für den Hinweis
System1 fhem 6.1 auf RPi 4B mit 4GB, HMUSBConfig, DS9490R-1Wire, Busware USB 868, Pool-Solarsteuerung mit FHEM. System2 fhem 6.1 auf RPi 4B mit 4GB (Bullseye) mit Busware USB 868 und 433 und HMUARTLGW für Haussteuerung

https://www.flickr.com/photos/canonhelmi/

Christoph Morrison

Was mich gerade stutzig macht: Du kommst doch per SSH auf RPiGarageneu. Editiere doch mal auf der Kommandozeile (mit vi, nano oder so) die fhem.cfg und dann startest du neu und postest hier den Log.
Vielleicht ist es ja was ganz triviales.

Was bedeuet eigentlich
ZitatDa ich auf Fhem nicht komme kann ich nur über die Konsole das editieren?
genau?

Mach mal bitte und poste hier die Ausgabe:
stat /opt/fhem/{.,fhem.cfg}

MadMax-FHEM

mount soll ja nichts "bringen" (ändern) sondern hätte halt gezeigt WIE gemountet ist...

Aber mach neu...
...und stückchenweise...

fhem.cfg "außerhalb" bearbeiten (hoffentlich mit dem "richtigen" Editor):

sudo cp /opt/fhem/fhem.cfg .

Wenn man einfach als 'pi' eingeloggt ist.
Dann liegt die fhem.cfg im Home von pi.

sudo chown pi:pi fhem.cfg

Natürlich als User pi dort wo die kopierte fhem.cfg liegt (also eigentlich im Home von pi).

Dann kann man sie entweder per scp auf einen externen Rechner übertragen oder mit entsprechenden Werkzeugen "direkt" bearbeiten...

Dann wieder zurück ins Home von pi (falls auf externen Rechner übertragen)...

Und dann wieder an den ursprünglichen Ort.

sudo cp fhem.cfg /opt/fhem/

Und dann evtl. (aber eigentl. unnötig):

sudo chown fhem: dialout /opt/fhem/fhem.cfg

Aber am einfachsten:

sudo nano /opt/fhem/fhem.cfg

Viel Erfolg, Joachim
FHEM PI3B+ Bullseye: HM-CFG-USB, 40x HM, ZWave-USB, 13x ZWave, EnOcean-PI, 15x EnOcean, HUE/deCONZ, CO2, ESP-Multisensor, Shelly, alexa-fhem, ...
FHEM PI2 Buster: HM-CFG-USB, 25x HM, ZWave-USB, 4x ZWave, EnOcean-PI, 3x EnOcean, Shelly, ha-bridge, ...
FHEM PI3 Buster (Test)

Helmi55

Ich mache gerne weiter
hier das Mount Ergebnis
pi@RPiGarageneu:~ $ mount
/dev/mmcblk0p2 on / type ext4 (ro,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=1867796k,nr_inodes=117771,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=399976k,mode=700,uid=1000,gid=1000)
pi@RPiGarageneu:~ $


und hier die Ausgabe von stat...
pi@RPiGarageneu:~ $ stat /opt/fhem/{.,fhem.cfg}
  Datei: /opt/fhem/.
  Größe: 4096      Blöcke: 8          EA Block: 4096   Verzeichnis
Gerät: b302h/45826d Inode: 62598       Verknüpfungen: 10
Zugriff: (0777/drwxrwxrwx)  Uid: (  999/    fhem)   Gid: (   20/ dialout)
Zugriff    : 2019-08-16 17:20:18.000000000 +0200
Modifiziert: 2019-08-17 16:32:43.833814488 +0200
Geändert   : 2019-08-17 16:32:43.833814488 +0200
Geburt    : -
  Datei: /opt/fhem/fhem.cfg
  Größe: 83631      Blöcke: 168        EA Block: 4096   reguläre Datei
Gerät: b302h/45826d Inode: 59486       Verknüpfungen: 1
Zugriff: (0777/-rwxrwxrwx)  Uid: (  999/    fhem)   Gid: (   20/ dialout)
Zugriff    : 2019-08-17 16:31:15.809999985 +0200
Modifiziert: 2019-08-17 07:01:00.000000000 +0200
Geändert   : 2019-08-17 16:31:15.809999985 +0200
Geburt    : -
pi@RPiGarageneu:~ $


Ich meinte mit komme nicht auf fhem mit:

ich arbeite mit einem mac mit firefox um auf die Oberfläche von fhem zu kommen und wenn ich hier die IP eingebe (http://10.0.0.46:8083/fhem) bekomme ich Verbindung
fehlgeschlagen.
Vom Terminal (sorry habe Konsole geschrieben) kann ich mit ssh pi@10.0.0.46 auf den Pi zugreifen. Wollte dann auch von hier mit sudo systemctl start fhem
fhem starten aber ohne Erfolg.

Ja jetzt werde ich versuchen mit nano über das Terminal die Cfg-USB zu bearbeiten - melde mich gleich wieder
Danke
Helmut
System1 fhem 6.1 auf RPi 4B mit 4GB, HMUSBConfig, DS9490R-1Wire, Busware USB 868, Pool-Solarsteuerung mit FHEM. System2 fhem 6.1 auf RPi 4B mit 4GB (Bullseye) mit Busware USB 868 und 433 und HMUARTLGW für Haussteuerung

https://www.flickr.com/photos/canonhelmi/

MadMax-FHEM

Da siehst du:

Zitat/dev/mmcblk0p2 on / type ext4 (ro,relatime)

Da kannst du mit Rechten rumtun wie du willst...
...'ro' heißt 'ro'...

Warum bleibt die Frage...

Evtl. mal dmesg o.ä. um zu sehen warum...

Gruß, Joachim
FHEM PI3B+ Bullseye: HM-CFG-USB, 40x HM, ZWave-USB, 13x ZWave, EnOcean-PI, 15x EnOcean, HUE/deCONZ, CO2, ESP-Multisensor, Shelly, alexa-fhem, ...
FHEM PI2 Buster: HM-CFG-USB, 25x HM, ZWave-USB, 4x ZWave, EnOcean-PI, 3x EnOcean, Shelly, ha-bridge, ...
FHEM PI3 Buster (Test)

Helmi55

Servus
pi@RPiGarageneu:~ $ sudo dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.58-v7l+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1245 SMP Fri Jul 12 17:31:45 BST 2019
[    0.000000] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 256 MiB at 0x000000001ec00000
[    0.000000] On node 0 totalpages: 1012736
[    0.000000]   DMA zone: 1728 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 196608 pages, LIFO batch:63
[    0.000000]   HighMem zone: 816128 pages, LIFO batch:63
[    0.000000] random: get_random_bytes called from start_kernel+0xc0/0x4e8 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu s39488 r8192 d21952 u69632
[    0.000000] pcpu-alloc: s39488 r8192 d21952 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 1011008
[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M cma=256M  smsc95xx.macaddr=DC:A6:32:07:DB:1D vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 kgdboc=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 3735596K/4050944K available (8192K kernel code, 658K rwdata, 2340K rodata, 2048K init, 850K bss, 53204K reserved, 262144K cma-reserved, 3264512K highmem)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
                   lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0x(ptrval) - 0x(ptrval)   (10208 kB)
                     .init : 0x(ptrval) - 0x(ptrval)   (2048 kB)
                     .data : 0x(ptrval) - 0x(ptrval)   ( 659 kB)
                      .bss : 0x(ptrval) - 0x(ptrval)   ( 851 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 27981 entries in 83 pages
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns
[    0.000005] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
[    0.000022] Switching to timer-based delay loop, resolution 18ns
[    0.000247] Console: colour dummy device 80x30
[    0.000730] console [tty1] enabled
[    0.000782] Calibrating delay loop (skipped), value calculated using timer frequency.. 108.00 BogoMIPS (lpj=540000)
[    0.000825] pid_max: default: 32768 minimum: 301
[    0.001098] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001131] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001889] CPU: Testing write buffer coherency: ok
[    0.002310] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002952] Setting up static identity map for 0x200000 - 0x20003c
[    0.003125] rcu: Hierarchical SRCU implementation.
[    0.003995] smp: Bringing up secondary CPUs ...
[    0.004898] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.005910] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.006883] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.007015] smp: Brought up 1 node, 4 CPUs
[    0.007081] SMP: Total of 4 processors activated (432.00 BogoMIPS).
[    0.007105] CPU: All CPU(s) started in HYP mode.
[    0.007125] CPU: Virtualization extensions available.
[    0.007909] devtmpfs: initialized
[    0.017986] VFP support v0.3: implementor 41 architecture 3 part 40 variant 8 rev 0
[    0.018221] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.018263] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.025583] pinctrl core: initialized pinctrl subsystem
[    0.026430] NET: Registered protocol family 16
[    0.029237] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.030569] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.030601] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.030808] Serial: AMBA PL011 UART driver
[    0.033977] bcm2835-mbox fe00b880.mailbox: mailbox enabled
[    0.069645] bcm2835-dma fe007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
[    0.072071] vgaarb: loaded
[    0.072447] SCSI subsystem initialized
[    0.072659] usbcore: registered new interface driver usbfs
[    0.072725] usbcore: registered new interface driver hub
[    0.072836] usbcore: registered new device driver usb
[    0.090378] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-07-09 14:37, variant start
[    0.100107] raspberrypi-firmware soc:firmware: Firmware hash is d2b1b7fb01475cb3914b2086299e32d724e832f1
[    0.111481] clocksource: Switched to clocksource arch_sys_counter
[    0.188723] VFS: Disk quotas dquot_6.6.0
[    0.188819] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.188982] FS-Cache: Loaded
[    0.189170] CacheFiles: Loaded
[    0.189691] simple-framebuffer: probe of 0.framebuffer failed with error -12
[    0.198734] NET: Registered protocol family 2
[    0.199393] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.199438] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.199520] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.199604] TCP: Hash tables configured (established 8192 bind 8192)
[    0.199736] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.199781] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.200090] NET: Registered protocol family 1
[    0.200625] RPC: Registered named UNIX socket transport module.
[    0.200651] RPC: Registered udp transport module.
[    0.200673] RPC: Registered tcp transport module.
[    0.200694] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.200722] PCI: CLS 0 bytes, default 64
[    0.203252] Initialise system trusted keyrings
[    0.203449] workingset: timestamp_bits=14 max_order=20 bucket_order=6
[    0.212086] FS-Cache: Netfs 'nfs' registered for caching
[    0.212600] NFS: Registering the id_resolver key type
[    0.212639] Key type id_resolver registered
[    0.212660] Key type id_legacy registered
[    0.212690] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.214861] Key type asymmetric registered
[    0.214886] Asymmetric key parser 'x509' registered
[    0.215009] bounce: pool size: 64 pages
[    0.215058] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.215237] io scheduler noop registered
[    0.215260] io scheduler deadline registered
[    0.215415] io scheduler cfq registered (default)
[    0.215438] io scheduler mq-deadline registered
[    0.215460] io scheduler kyber registered
[    0.244114] brcm-pcie fd500000.pcie: dmabounce: initialised - 32768 kB, threshold 0x00000000c0000000
[    0.244158] brcm-pcie fd500000.pcie: could not get clock
[    0.244232] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[    0.244282] brcm-pcie fd500000.pcie:   MEM 0x600000000..0x603ffffff -> 0xf8000000
[    0.301518] brcm-pcie fd500000.pcie: link up, 5.0 Gbps x1 (!SSC)
[    0.301800] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
[    0.301830] pci_bus 0000:00: root bus resource [bus 00-01]
[    0.301860] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])
[    0.301924] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
[    0.302059] pci 0000:00:00.0: PME# supported from D0 D3hot
[    0.304766] PCI: bus0: Fast back to back transfers disabled
[    0.304799] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.304975] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
[    0.305035] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.305203] pci 0000:01:00.0: PME# supported from D0 D3cold
[    0.307820] PCI: bus1: Fast back to back transfers disabled
[    0.307851] pci_bus 0000:01: busn_res: [bus 01] end is updated to 01
[    0.307896] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
[    0.307930] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
[    0.307978] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.308007] pci 0000:00:00.0:   bridge window [mem 0x600000000-0x6000fffff]
[    0.308081] pci 0000:00:00.0: enabling device (0140 -> 0142)
[    0.308117] pci 0000:01:00.0: enabling device (0140 -> 0142)
[    0.311322] iproc-rng200 fe104000.rng: hwrng registered
[    0.311596] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.312112] vc-sm: Videocore shared memory driver
[    0.312524] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
[    0.322417] brd: module loaded
[    0.331904] loop: module loaded
[    0.332660] Loading iSCSI transport class v2.0-870.
[    0.334287] libphy: Fixed MDIO Bus: probed
[    0.334734] bcmgenet fd580000.genet: failed to get enet clock
[    0.334765] bcmgenet fd580000.genet: GENET 5.0 EPHY: 0x0000
[    0.334795] bcmgenet fd580000.genet: failed to get enet-wol clock
[    0.334824] bcmgenet fd580000.genet: failed to get enet-eee clock
[    0.335082] unimac-mdio unimac-mdio.-19: DMA mask not set
[    0.351510] libphy: bcmgenet MII bus: probed
[    0.392199] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus at 0x(ptrval)
[    0.393090] usbcore: registered new interface driver r8152
[    0.393164] usbcore: registered new interface driver lan78xx
[    0.393229] usbcore: registered new interface driver smsc95xx
[    0.393498] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    0.393541] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[    0.395304] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000001000000890
[    0.395487] genirq: irq_chip Brcm_MSI did not update eff. affinity mask of irq 55
[    0.396126] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.396161] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.396191] usb usb1: Product: xHCI Host Controller
[    0.396215] usb usb1: Manufacturer: Linux 4.19.58-v7l+ xhci-hcd
[    0.396239] usb usb1: SerialNumber: 0000:01:00.0
[    0.396751] hub 1-0:1.0: USB hub found
[    0.396815] hub 1-0:1.0: 1 port detected
[    0.397229] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    0.397271] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    0.397309] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    0.397657] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    0.397692] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.397721] usb usb2: Product: xHCI Host Controller
[    0.397745] usb usb2: Manufacturer: Linux 4.19.58-v7l+ xhci-hcd
[    0.397768] usb usb2: SerialNumber: 0000:01:00.0
[    0.398257] hub 2-0:1.0: USB hub found
[    0.398322] hub 2-0:1.0: 4 ports detected
[    0.399449] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.425031] dwc_otg fe980000.usb: base=(ptrval)
[    0.625376] Core Release: 2.80a
[    0.625403] Setting default values for core params
[    0.625445] Finished setting default values for core params
[    0.825778] Using Buffer DMA mode
[    0.825801] Periodic Transfer Interrupt Enhancement - disabled
[    0.825824] Multiprocessor Interrupt Enhancement - disabled
[    0.825848] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.825917] Dedicated Tx FIFOs mode
[    0.826584] WARN::dwc_otg_hcd_init:1045: FIQ DMA bounce buffers: virt = ded30000 dma = 0x00000000ded30000 len=9024
[    0.826632] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.826693] dwc_otg: Microframe scheduler enabled
[    0.826757] WARN::hcd_init_fiq:457: FIQ on core 1
[    0.826790] WARN::hcd_init_fiq:458: FIQ ASM at c07ae224 length 36
[    0.826822] WARN::hcd_init_fiq:497: MPHI regs_base at f0810200
[    0.826871] dwc_otg fe980000.usb: DWC OTG Controller
[    0.826922] dwc_otg fe980000.usb: new USB bus registered, assigned bus number 3
[    0.826979] dwc_otg fe980000.usb: irq 36, io mem 0x00000000
[    0.827044] Init: Port Power? op_state=1
[    0.827064] Init: Power Port (0)
[    0.827321] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.827353] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.827382] usb usb3: Product: DWC OTG Controller
[    0.827406] usb usb3: Manufacturer: Linux 4.19.58-v7l+ dwc_otg_hcd
[    0.827430] usb usb3: SerialNumber: fe980000.usb
[    0.827948] hub 3-0:1.0: USB hub found
[    0.828010] hub 3-0:1.0: 1 port detected
[    0.828594] dwc_otg: FIQ enabled
[    0.828603] dwc_otg: NAK holdoff enabled
[    0.828612] dwc_otg: FIQ split-transaction FSM enabled
[    0.828625] Module dwc_common_port init
[    0.828840] usbcore: registered new interface driver uas
[    0.828963] usbcore: registered new interface driver usb-storage
[    0.829135] mousedev: PS/2 mouse device common for all mice
[    0.830295] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[    0.830500] bcm2835-cpufreq: min=600000 max=1500000
[    0.831096] sdhci: Secure Digital Host Controller Interface driver
[    0.831120] sdhci: Copyright(c) Pierre Ossman
[    0.831590] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe
[    0.831988] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.834962] ledtrig-cpu: registered to indicate activity on CPUs
[    0.835117] hidraw: raw HID events driver (C) Jiri Kosina
[    0.835260] usbcore: registered new interface driver usbhid
[    0.835283] usbhid: USB HID core driver
[    0.836034] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[    0.837624] [vc_sm_connected_init]: start
[    0.845624] [vc_sm_connected_init]: end - returning 0
[    0.846677] Initializing XFRM netlink socket
[    0.846718] NET: Registered protocol family 17
[    0.846812] Key type dns_resolver registered
[    0.847085] Registering SWP/SWPB emulation handler
[    0.847663] registered taskstats version 1
[    0.847692] Loading compiled-in X.509 certificates
[    0.855501] uart-pl011 fe201000.serial: cts_event_workaround enabled
[    0.855581] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 33, base_baud = 0) is a PL011 rev2
[    0.858506] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[    0.859032] brcmstb_thermal fd5d2200.thermal: registered AVS TMON of-sensor driver
[    0.859671] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
[    0.859697] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
[    0.884661] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1
[    0.903908] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.905533] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.907188] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.910083] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.911710] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.919716] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA
[    0.922230] of_cfs_init
[    0.922327] of_cfs_init: OK
[    0.922994] Waiting for root device /dev/mmcblk0p2...
[    0.969261] random: fast init done
[    0.971537] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[    0.981356] mmc1: new high speed SDIO card at address 0001
[    1.024723] mmc0: new ultra high speed DDR50 SDHC card at address aaaa
[    1.025834] mmcblk0: mmc0:aaaa SM32G 29.7 GiB
[    1.027383]  mmcblk0: p1 p2
[    1.051518] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.051728] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.056649] devtmpfs: mounted
[    1.063156] Freeing unused kernel memory: 2048K
[    1.081738] Run /sbin/init as init process
[    1.162911] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.20
[    1.162978] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.163006] usb 1-1: Product: USB2.0 Hub
[    1.164545] hub 1-1:1.0: USB hub found
[    1.164805] hub 1-1:1.0: 4 ports detected
[    1.488252] systemd[1]: System time before build time, advancing clock.
[    1.580348] NET: Registered protocol family 10
[    1.581622] Segment Routing with IPv6
[    1.609816] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    1.610518] systemd[1]: Detected architecture arm.
[    1.621034] systemd[1]: Set hostname to <RPiGarageneu>.
[    1.628713] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
[    1.826253] systemd-fstab-generator[88]: Mount point in is not a valid path, ignoring.
[    1.888822] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[    1.888883] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[    2.139078] systemd[1]: Configuration file /etc/systemd/system/rc-local.service.d/ttyoutput.conf is marked executable. Please remove executable permission bits. Proceeding anyway.
[    2.139143] systemd[1]: Configuration file /etc/systemd/system/rc-local.service.d/ttyoutput.conf is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
[    2.183128] systemd[1]: Configuration file /etc/systemd/system/getty@tty1.service.d/noclear.conf is marked executable. Please remove executable permission bits. Proceeding anyway.
[    2.183191] systemd[1]: Configuration file /etc/systemd/system/getty@tty1.service.d/noclear.conf is marked world-writable. Please remove world writability permission bits. Proceeding anyway.
[    2.235330] random: systemd: uninitialized urandom read (16 bytes read)
[    2.243076] random: systemd: uninitialized urandom read (16 bytes read)
[    2.244087] random: systemd: uninitialized urandom read (16 bytes read)
[    2.740616] systemd-journald[102]: Received request to flush runtime journal from PID 1
[    3.478863] random: crng init done
[    3.478876] random: 7 urandom warning(s) missed due to ratelimiting
[    3.540685] Driver for 1-wire Dallas network protocol.
[    3.574302] gpio-4 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file
[    3.658728] argon-mem feb00000.hevc-decoder: argon-hevcmem initialised: Registers at 0xfeb00000 length 0x0000ffff
[    3.659677] argon-mem feb10000.argon-local-intc: argon-intcmem initialised: Registers at 0xfeb10000 length 0x00000fff
[    3.660344] argon-mem feb20000.h264-decoder: argon-h264mem initialised: Registers at 0xfeb20000 length 0x0000ffff
[    3.660710] argon-mem feb30000.vp9-decoder: argon-vp9mem initialised: Registers at 0xfeb30000 length 0x0000ffff
[    3.758794] media: Linux media interface: v0.10
[    3.786429] videodev: Linux video capture interface: v2.00
[    3.796691] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    3.798110] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    3.798118] [vc_sm_connected_init]: start
[    3.823577] [vc_sm_connected_init]: installed successfully
[    3.833353] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    3.864233] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    3.865072] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    3.866454] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    3.893462] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    3.893468] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[    3.902101] bcm2835_audio soc:audio: card created with 8 channels
[    3.905932] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    3.905941] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[    3.910696] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[    3.910703] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[    3.917479] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
[    3.948644] 8021q: 802.1Q VLAN Support v1.8
[    3.963444] [drm] No displays found. Consider forcing hotplug if HDMI is attached
[    3.963495] vc4-drm soc:gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
[    3.964429] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1
[    3.964435] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    3.964439] [drm] No driver support for vblank timestamp query.
[    3.964443] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL
[    4.005864] uart-pl011 fe201000.serial: no DMA platform data
[    4.011010] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    4.102450] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    4.154564] brcmfmac: F1 signature read @0x18000000=0x15264345
[    4.181123] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    4.182354] usbcore: registered new interface driver brcmfmac
[    4.271766] bcmgenet fd580000.genet: configuring instance for external RGMII (no delay)
[    4.271920] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.406490] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    4.416061] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[    4.580383] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[    4.580398] brcmfmac: power management disabled
[    5.351719] bcmgenet fd580000.genet eth0: Link is Down
[    6.206344] w1_master_driver w1_bus_master1: w1_search: max_slave_count 64 reached, will continue next search.
[    9.511712] bcmgenet fd580000.genet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[    9.511748] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   10.649793] Bluetooth: Core ver 2.22
[   10.649865] NET: Registered protocol family 31
[   10.649875] Bluetooth: HCI device and connection manager initialized
[   10.649895] Bluetooth: HCI socket layer initialized
[   10.649910] Bluetooth: L2CAP socket layer initialized
[   10.649955] Bluetooth: SCO socket layer initialized
[   10.663789] Bluetooth: HCI UART driver ver 2.3
[   10.663803] Bluetooth: HCI UART protocol H4 registered
[   10.663881] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   10.664111] Bluetooth: HCI UART protocol Broadcom registered
[   10.837644] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.837650] Bluetooth: BNEP filters: protocol multicast
[   10.837660] Bluetooth: BNEP socket layer initialized
[   57.036347] w1_master_driver w1_bus_master1: Attaching one wire slave 00.800000000000 crc 8c
[   57.051846] w1_master_driver w1_bus_master1: Family 0 for 00.800000000000.8c is not registered.
[  120.636493] w1_master_driver w1_bus_master1: Attaching one wire slave 00.400000000000 crc 46
[  120.651586] w1_master_driver w1_bus_master1: Family 0 for 00.400000000000.46 is not registered.
[  171.396422] w1_master_driver w1_bus_master1: Attaching one wire slave 00.c00000000000 crc ca
[  171.411589] w1_master_driver w1_bus_master1: Family 0 for 00.c00000000000.ca is not registered.
[  247.836399] w1_master_driver w1_bus_master1: Attaching one wire slave 00.200000000000 crc 23
[  247.849086] w1_master_driver w1_bus_master1: Family 0 for 00.200000000000.23 is not registered.
[  311.436404] w1_master_driver w1_bus_master1: Attaching one wire slave 00.a00000000000 crc af
[  311.451427] w1_master_driver w1_bus_master1: Family 0 for 00.a00000000000.af is not registered.
[  349.356389] w1_master_driver w1_bus_master1: Attaching one wire slave 00.600000000000 crc 65
[  349.368491] w1_master_driver w1_bus_master1: Family 0 for 00.600000000000.65 is not registered.
[  389.836399] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e00000000000 crc e9
[  389.847733] w1_master_driver w1_bus_master1: Family 0 for 00.e00000000000.e9 is not registered.
[  452.836374] w1_master_driver w1_bus_master1: Attaching one wire slave 00.100000000000 crc 9d
[  452.847845] w1_master_driver w1_bus_master1: Family 0 for 00.100000000000.9d is not registered.
[  491.956379] w1_master_driver w1_bus_master1: Attaching one wire slave 00.900000000000 crc 11
[  491.967883] w1_master_driver w1_bus_master1: Family 0 for 00.900000000000.11 is not registered.
[  567.196344] w1_master_driver w1_bus_master1: Attaching one wire slave 00.500000000000 crc db
[  567.217667] w1_master_driver w1_bus_master1: Family 0 for 00.500000000000.db is not registered.
[  619.156386] w1_master_driver w1_bus_master1: Attaching one wire slave 00.d00000000000 crc 57
[  619.172607] w1_master_driver w1_bus_master1: Family 0 for 00.d00000000000.57 is not registered.
[  645.596548] w1_master_driver w1_bus_master1: Attaching one wire slave 00.300000000000 crc be
[  645.608302] w1_master_driver w1_bus_master1: Family 0 for 00.300000000000.be is not registered.
[  694.996395] w1_master_driver w1_bus_master1: Attaching one wire slave 00.b00000000000 crc 32
[  695.007763] w1_master_driver w1_bus_master1: Family 0 for 00.b00000000000.32 is not registered.
[  734.276386] w1_master_driver w1_bus_master1: Attaching one wire slave 00.700000000000 crc f8
[  734.287912] w1_master_driver w1_bus_master1: Family 0 for 00.700000000000.f8 is not registered.
[  786.236390] w1_master_driver w1_bus_master1: Attaching one wire slave 00.f00000000000 crc 74
[  786.247773] w1_master_driver w1_bus_master1: Family 0 for 00.f00000000000.74 is not registered.
[  848.716408] w1_master_driver w1_bus_master1: Attaching one wire slave 00.080000000000 crc c2
[  848.727922] w1_master_driver w1_bus_master1: Family 0 for 00.080000000000.c2 is not registered.
[  901.956381] w1_master_driver w1_bus_master1: Attaching one wire slave 00.880000000000 crc 4e
[  901.967845] w1_master_driver w1_bus_master1: Family 0 for 00.880000000000.4e is not registered.
[  939.796394] w1_master_driver w1_bus_master1: Attaching one wire slave 00.480000000000 crc 84
[  939.808013] w1_master_driver w1_bus_master1: Family 0 for 00.480000000000.84 is not registered.
[  990.476403] w1_master_driver w1_bus_master1: Attaching one wire slave 00.c80000000000 crc 08
[  990.491000] w1_master_driver w1_bus_master1: Family 0 for 00.c80000000000.08 is not registered.
[ 1067.156347] w1_master_driver w1_bus_master1: Attaching one wire slave 00.280000000000 crc e1
[ 1067.177863] w1_master_driver w1_bus_master1: Family 0 for 00.280000000000.e1 is not registered.
[ 1130.676386] w1_master_driver w1_bus_master1: Attaching one wire slave 00.a80000000000 crc 6d
[ 1130.687798] w1_master_driver w1_bus_master1: Family 0 for 00.a80000000000.6d is not registered.
[ 1194.196396] w1_master_driver w1_bus_master1: Attaching one wire slave 00.680000000000 crc a7
[ 1194.207750] w1_master_driver w1_bus_master1: Family 0 for 00.680000000000.a7 is not registered.
[ 1234.596383] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e80000000000 crc 2b
[ 1234.608036] w1_master_driver w1_bus_master1: Family 0 for 00.e80000000000.2b is not registered.
[ 1297.756336] w1_master_driver w1_bus_master1: Attaching one wire slave 00.180000000000 crc 5f
[ 1297.768376] w1_master_driver w1_bus_master1: Family 0 for 00.180000000000.5f is not registered.
[ 1336.956379] w1_master_driver w1_bus_master1: Attaching one wire slave 00.980000000000 crc d3
[ 1336.967712] w1_master_driver w1_bus_master1: Family 0 for 00.980000000000.d3 is not registered.
[ 1386.276690] w1_master_driver w1_bus_master1: Attaching one wire slave 00.580000000000 crc 19
[ 1386.290335] w1_master_driver w1_bus_master1: Family 0 for 00.580000000000.19 is not registered.
[ 1438.316384] w1_master_driver w1_bus_master1: Attaching one wire slave 00.d80000000000 crc 95
[ 1438.329482] w1_master_driver w1_bus_master1: Family 0 for 00.d80000000000.95 is not registered.
[ 1464.836411] w1_master_driver w1_bus_master1: Attaching one wire slave 00.380000000000 crc 7c
[ 1464.847636] w1_master_driver w1_bus_master1: Family 0 for 00.380000000000.7c is not registered.
[ 1514.316391] w1_master_driver w1_bus_master1: Attaching one wire slave 00.b80000000000 crc f0
[ 1514.327899] w1_master_driver w1_bus_master1: Family 0 for 00.b80000000000.f0 is not registered.
[ 1579.036398] w1_master_driver w1_bus_master1: Attaching one wire slave 00.780000000000 crc 3a
[ 1579.048737] w1_master_driver w1_bus_master1: Family 0 for 00.780000000000.3a is not registered.
[ 1631.076389] w1_master_driver w1_bus_master1: Attaching one wire slave 00.f80000000000 crc b6
[ 1631.098406] w1_master_driver w1_bus_master1: Family 0 for 00.f80000000000.b6 is not registered.
[ 1693.716396] w1_master_driver w1_bus_master1: Attaching one wire slave 00.040000000000 crc 61
[ 1693.727708] w1_master_driver w1_bus_master1: Family 0 for 00.040000000000.61 is not registered.
[ 1747.036362] w1_master_driver w1_bus_master1: Attaching one wire slave 00.840000000000 crc ed
[ 1747.047696] w1_master_driver w1_bus_master1: Family 0 for 00.840000000000.ed is not registered.
[ 1810.476391] w1_master_driver w1_bus_master1: Attaching one wire slave 00.440000000000 crc 27
[ 1810.487772] w1_master_driver w1_bus_master1: Family 0 for 00.440000000000.27 is not registered.
[ 1861.236345] w1_master_driver w1_bus_master1: Attaching one wire slave 00.c40000000000 crc ab
[ 1861.247795] w1_master_driver w1_bus_master1: Family 0 for 00.c40000000000.ab is not registered.
[ 1886.156378] w1_master_driver w1_bus_master1: Attaching one wire slave 00.240000000000 crc 42
[ 1886.167555] w1_master_driver w1_bus_master1: Family 0 for 00.240000000000.42 is not registered.
[ 1949.756336] w1_master_driver w1_bus_master1: Attaching one wire slave 00.a40000000000 crc ce
[ 1949.767888] w1_master_driver w1_bus_master1: Family 0 for 00.a40000000000.ce is not registered.
[ 1977.236404] w1_master_driver w1_bus_master1: Attaching one wire slave 00.640000000000 crc 04
[ 1977.247581] w1_master_driver w1_bus_master1: Family 0 for 00.640000000000.04 is not registered.
[ 2027.996340] w1_master_driver w1_bus_master1: Attaching one wire slave 00.e40000000000 crc 88
[ 2028.008123] w1_master_driver w1_bus_master1: Family 0 for 00.e40000000000.88 is not registered.
[ 2091.476387] w1_master_driver w1_bus_master1: Attaching one wire slave 00.140000000000 crc fc
[ 2091.488513] w1_master_driver w1_bus_master1: Family 0 for 00.140000000000.fc is not registered.
[ 2130.596388] w1_master_driver w1_bus_master1: Attaching one wire slave 00.940000000000 crc 70
[ 2130.611249] w1_master_driver w1_bus_master1: Family 0 for 00.940000000000.70 is not registered.
[ 2205.676378] w1_master_driver w1_bus_master1: Attaching one wire slave 00.540000000000 crc ba
[ 2205.698451] w1_master_driver w1_bus_master1: Family 0 for 00.540000000000.ba is not registered.
[ 2257.636388] w1_master_driver w1_bus_master1: Attaching one wire slave 00.d40000000000 crc 36
[ 2257.647631] w1_master_driver w1_bus_master1: Family 0 for 00.d40000000000.36 is not registered.
[ 2335.276382] w1_master_driver w1_bus_master1: Attaching one wire slave 00.340000000000 crc df
[ 2335.287651] w1_master_driver w1_bus_master1: Family 0 for 00.340000000000.df is not registered.
[ 2384.676377] w1_master_driver w1_bus_master1: Attaching one wire slave 00.b40000000000 crc 53
[ 2384.687634] w1_master_driver w1_bus_master1: Family 0 for 00.b40000000000.53 is not registered.
[ 2423.796384] w1_master_driver w1_bus_master1: Attaching one wire slave 00.740000000000 crc 99
[ 2423.817681] w1_master_driver w1_bus_master1: Family 0 for 00.740000000000.99 is not registered.
[ 2475.756379] w1_master_driver w1_bus_master1: Attaching one wire slave 00.f40000000000 crc 15
[ 2475.767659] w1_master_driver w1_bus_master1: Family 0 for 00.f40000000000.15 is not registered.
[ 2538.556374] w1_master_driver w1_bus_master1: Attaching one wire slave 00.0c0000000000 crc a3
[ 2538.567713] w1_master_driver w1_bus_master1: Family 0 for 00.0c0000000000.a3 is not registered.
[ 2591.796367] w1_master_driver w1_bus_master1: Attaching one wire slave 00.8c0000000000 crc 2f
[ 2591.807753] w1_master_driver w1_bus_master1: Family 0 for 00.8c0000000000.2f is not registered.
[ 2629.796376] w1_master_driver w1_bus_master1: Attaching one wire slave 00.4c0000000000 crc e5
[ 2629.807820] w1_master_driver w1_bus_master1: Family 0 for 00.4c0000000000.e5 is not registered.
[ 2680.476396] w1_master_driver w1_bus_master1: Attaching one wire slave 00.cc0000000000 crc 69
[ 2680.487789] w1_master_driver w1_bus_master1: Family 0 for 00.cc0000000000.69 is not registered.
[ 2705.316375] w1_master_driver w1_bus_master1: Attaching one wire slave 00.2c0000000000 crc 80
[ 2705.327637] w1_master_driver w1_bus_master1: Family 0 for 00.2c0000000000.80 is not registered.
pi@RPiGarageneu:~ $ pi@RPiGarapippi@RPiGapipppipi@Rpipi@RPippippipi@RPiGaragpipipipi@pipppi@ppi@RPiGarageneu:~ $



Ich glaub das habe ich ordentlich zerstört........
Denn ich kann eine Datei nicht mal nach /home/pi hochladen....
Dort hin habe ich aber vor dem Restore des BU die backup Datei abgelegt.

Wenn Ihr noch die Geduld habt, wie lautet der richtige Befehl, um z.B. die fhem.cfg in das Verzeichnis /opt/fhem hochzuladen.
Damit ich nur dort die Schreibrechte habe ohne das Gesamtwerk wieder zu zerstören

Danke
Helmut
System1 fhem 6.1 auf RPi 4B mit 4GB, HMUSBConfig, DS9490R-1Wire, Busware USB 868, Pool-Solarsteuerung mit FHEM. System2 fhem 6.1 auf RPi 4B mit 4GB (Bullseye) mit Busware USB 868 und 433 und HMUARTLGW für Haussteuerung

https://www.flickr.com/photos/canonhelmi/