| View previous topic :: View next topic |
| Author |
Message |
3PO
Veteran
Joined: 26 Nov 2006
Posts: 1110
Location: Schwabenländle
|
 Posted: Fri Mar 08, 2019 3:14 pm Post subject: [open-rc] Meldungen während boot ausgeben? |
 |
|
Hallo Zusammen,
ich habe hier ein seltsames Problem, ich habe mein Mainboard getauscht und seit dem werden während des Bootvorgangs keine init-Ausgaben von Open-RC mehr angezeigt.
Nach dem Kernellog kommt noch "starting open-rc ....", dann wird der Bildschirm schwarz und erst der Login Screen wird wieder angezeigt.
Alles Anders scheint zu funktionieren.
Weiß Jemand, wo ich da suchen muss? |
|
| Back to top |
|
 |
haegar87
Apprentice
Joined: 08 Jan 2006
Posts: 164
|
| Posted: Fri Mar 08, 2019 8:02 pm Post subject: |
|
|
Ist jetzt nur ein Schuss ins Blaue, aber könnte vielleicht irgendwie quiet als Bootoption reingerutscht sein?
Wäre so auf Anhieb das einzige was mir einfällt, was sämtliche Bootmeldungen unterdrücken könnte.
Muss aber dazusagen, dass ich seit systemd kein OpenRC mehr angefasst habe...
_________________
"Spielt man die Windows CD rückwärts ab, hört man satanistische Texte!" - "Das ist ja noch harmlos! Wenn man sie vorwärts abspielt, installiert sich das Teufelszeug!" |
|
| Back to top |
|
|
3PO
Veteran
Joined: 26 Nov 2006
Posts: 1110
Location: Schwabenländle
|
| Posted: Fri Mar 08, 2019 8:05 pm Post subject: |
|
|
Das ist es leider nicht: 
| Code: | vdr01_64 ~ # cat /proc/cmdline
BOOT_IMAGE=/kernel-4.20.6-gentoo root=/dev/nvme0n1p3 ro usbhid.quirks=0x15c2:0x30c0:0x04 HOME=/root pcie_aspm=off video=1920x1080 rootfstype=ext4 acpi_enforce_resources=lax
vdr01_64 ~ # |
|
|
| Back to top |
|
|
Max Steel
Advocate
Joined: 12 Feb 2007
Posts: 2229
Location: My own world! I and Gentoo!
|
| Posted: Fri Mar 08, 2019 8:07 pm Post subject: |
|
|
Boardwechsel... zufällig auch mit anderer Grafik weil der interne Chipsatz wechselte? und damit fehlende Unterstützung für den FB im Kernel?...
Oder fehler durch nachladen von modulen durch openrc und damit die probleme?...
_________________
mfg
Steel
___________________
Heim-PC: AMD Ryzen 5950X, 64GB RAM, GTX 1080
Laptop: Intel Core i5-4300U, 16GB RAM, Intel Graphic
Arbeit-PC: Intel i5-1145G7, 16GB RAM, Intel Iris Xe Graphic (leider WSL2) |
|
| Back to top |
|
|
3PO
Veteran
Joined: 26 Nov 2006
Posts: 1110
Location: Schwabenländle
|
| Posted: Fri Mar 08, 2019 8:16 pm Post subject: |
|
|
Ich sehe nicht auffälliges:
| Code: | rc sysinit logging started at Fri Mar 8 20:42:31 2019
OpenRC 0.38.3 is starting up Gentoo Linux (x86_64)
* Mounting /proc ...
[ ok ]
* Mounting /run ...
* /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Caching service dependencies ...
[ ok ]
sysfs | * Mounting /sys ...
devfs | * Remounting devtmpfs on /dev ...
[ ok ]
[ ok ]
sysfs | * Mounting security filesystem ...
[ ok ]
sysfs | * Mounting debug filesystem ...
[ ok ]
devfs | * Mounting /dev/pts ...
sysfs | * Mounting config filesystem ...
[ ok ]
[ ok ]
devfs | * Mounting /dev/shm ...
[ ok ]
cgroups | * Mounting cgroup filesystem ...
[ ok ]
opentmpfiles-dev | * Setting up tmpfiles.d entries for /dev ...
[ ok ]
udev | * Starting udev ...
udev |starting version 239
[ ok ]
udev | * Generating a rule to create a /dev/root symlink ...
[ ok ]
udev | * Populating /dev with existing devices through uevents ...
[ ok ]
udev | * Waiting for uevents to be processed ...
fsck | * fsck: waiting for udev (50 seconds)
root | * root: waiting for udev (50 seconds)
udev-trigger | * udev-trigger: waiting for udev (50 seconds)
fsck | * fsck: waiting for udev (41 seconds)
root | * root: waiting for udev (41 seconds)
udev-trigger | * udev-trigger: waiting for udev (41 seconds)
fsck | * fsck: waiting for udev (32 seconds)
root | * root: waiting for udev (32 seconds)
udev-trigger | * udev-trigger: waiting for udev (32 seconds)
fsck | * fsck: waiting for udev (23 seconds)
root | * root: waiting for udev (23 seconds)
udev-trigger | * udev-trigger: waiting for udev (23 seconds)
fsck | * fsck: waiting for udev (14 seconds)
root | * root: waiting for udev (14 seconds)
udev-trigger | * udev-trigger: waiting for udev (14 seconds)
fsck | * fsck: waiting for udev (5 seconds)
root | * root: waiting for udev (5 seconds)
udev-trigger | * udev-trigger: waiting for udev (5 seconds)
fsck | * fsck: timed out waiting for udev
root | * root: timed out waiting for udev
udev-trigger | * udev-trigger: timed out waiting for udev
udev-trigger | * ERROR: cannot start udev-trigger as udev would not start
fsck | * Checking local filesystems ...
fsck |/dev/nvme0n1p3: sauber, 1523895/6496256 Dateien, 13945175/25982801 Blcke
fsck |/dev/nvme0n1p1: sauber, 518/32768 Dateien, 63924/131072 Blcke
fsck |/sbin/fsck.xfs: XFS file system.
[ ok ]
root | * Remounting root filesystem read/write ...
[ ok ]
root | * Remounting filesystems ...
[ ok ]
[ !! ]
udev | * Device initiated services: net.eno1
rc sysinit logging stopped at Fri Mar 8 20:42:31 2019
rc boot logging started at Fri Mar 8 20:42:31 2019
automount | * Starting Automount ...
modules | * Loading kernel modules ...
[ ok ]
modules |insmod /lib/modules/4.20.6-gentoo/kernel/drivers/hwmon/hwmon-vid.ko
modules |insmod /lib/modules/4.20.6-gentoo/kernel/drivers/hwmon/nct6775.ko
modules |modprobe: ERROR: could not insert 'nct6775': No such device
[ ok ]
hwclock | * Setting system clock using the hardware clock [UTC] ...
[ ok ]
sysctl | * Configuring kernel parameters ...
loopback | * Bringing up network interface lo ...
swap | * Activating swap devices ...
procfs | * Mounting misc binary format filesystem ...
[ ok ]
hostname | * Setting hostname to vdr01_64 ...
mtab | * Updating /etc/mtab ...
mtab | * Creating mtab symbolic link
[ ok ]
[ ok ]
[ ok ]
[ ok ]
[ ok ]
binfmt | * Loading custom binary format handlers ...
[ ok ]
localmount | * Mounting local filesystems ...
[ ok ]
gen2vdr | * Gen2VDR Init ...
opentmpfiles-setup | * Setting up tmpfiles.d entries ...
urandom | * Initializing random number generator ...
[ ok ]
gen2vdr |logger: Socket /dev/log: Datei oder Verzeichnis nicht gefunden
gen2vdr |logger: Socket /dev/log: Datei oder Verzeichnis nicht gefunden
[ ok ]
[ ok ]
lircd | * Starting lircd ...
[ ok ]
bootmisc | * Creating user login records ...
[ ok ]
bootmisc | * Wiping /tmp directory ...
[ ok ]
termencoding | * Setting terminal encoding [UTF-8] ...
dbus | * Starting dbus ...
metalog | * Starting metalog ...
[ ok ]
alsasound | * Restoring Mixer Levels ...
[ ok ]
[ ok ]
[ ok ]
net.lo | * Bringing up interface lo
net.lo | * Caching network module dependencies
gpm | * Starting gpm ...
[ ok ]
consolefont | * Setting console font [default8x16] ...
acpid | * Starting acpid ...
[ ok ]
keymaps | * Setting keyboard mode [UTF-8] ...
g2vgui | * Starting Gen2VDR GUI ...
net.lo |need dbus
net.lo | * 127.0.0.1/8 ...
[ ok ]
net.lo | * Adding routes
net.lo | * 127.0.0.0/8 via 127.0.0.1 ...
[ ok ]
[ ok ]
[ ok ]
keymaps | * Loading key mappings [de] ...
[ ok ]
[ ok ]
net.eno1 | * Bringing up interface eno1
net.eno1 | * 192.168.177.52 ...
[ ok ]
net.eno1 | * Adding routes
net.eno1 | * default via 192.168.177.1 ...
[ ok ]
[ ok ]
avahi-daemon | * Starting avahi-daemon ...
vdr | * Starting vdr ...
vdr |<13>Mar 8 20:42:33 root: Starting <openvt -c 8 -f -- /etc/vdr/runvdr>
[ ok ]
[ ok ]
rc boot logging stopped at Fri Mar 8 20:42:34 2019
rc default logging started at Fri Mar 8 20:42:34 2019
rpc.pipefs | * Setting up RPC pipefs ...
[ ok ]
lm_sensors | * Initializing sensors ...
[ ok ]
fail2ban | * Starting fail2ban ...
vdradmin | * Starting vdradmin ...
distccd | * Starting distccd ...
vnstatd | * Starting vnstatd ...
atd | * Starting atd ...
xinetd | * Starting xinetd ...
samba | * samba -> start: smbd ...
[ ok ]
fritzwatch | * Starting FritzWatch ...
netmount | * Mounting network filesystems ...
[ ok ]
[ ok ]
[ ok ]
ntp-client | * Setting clock via the NTP client 'ntpdate' ...
[ ok ]
mysql | * Checking mysqld configuration for mysql ...
[ ok ]
sshd | * Starting sshd ...
sensord | * Starting sensord ...
[ ok ]
mysql | * Starting mysql ...
[ ok ]
samba | * samba -> start: nmbd ...
[ ok ]
fail2ban |Server ready
[ ok ]
[ ok ]
[ ok ]
[ ok ]
apache2 | * Starting apache2 ...
[ ok ]
[ ok ]
rpc.idmapd | * rpc.idmapd: waiting for ntp-client (50 seconds)
vixie-cron |rpc.statd | * * vixie-cron: waiting for ntp-client (50 seconds)rpc.statd: waiting for ntp-client (50 seconds)
rpcbind | * rpcbind: waiting for ntp-client (50 seconds)
nfsclient | * nfsclient: waiting for ntp-client (50 seconds)
nfs | * nfs: waiting for ntp-client (50 seconds)
[ ok ]
local | * local: waiting for ntp-client (50 seconds)
vixie-cron | * Starting vixie-cron ...
rpcbind | * Starting rpcbind ...
[ ok ]
[ ok ]
rpc.idmapd | * Starting idmapd ...
[ ok ]
rpc.statd | * Starting NFS statd ...
[ ok ]
nfsclient | * Starting NFS sm-notify ...
[ ok ]
nfs | * Mounting nfsd filesystem in /proc ...
[ ok ]
nfs | * Exporting NFS directories ...
[ ok ]
nfs | * Starting NFS mountd ...
[ ok ]
nfs | * Starting NFS daemon ...
[ ok ]
nfs | * Starting NFS smnotify ...
[ ok ]
local | * Starting local ...
[ !! ]
rc default logging stopped at Fri Mar 8 20:42:50 2019
|
|
|
| Back to top |
|
|
3PO
Veteran
Joined: 26 Nov 2006
Posts: 1110
Location: Schwabenländle
|
| Posted: Fri Mar 08, 2019 9:10 pm Post subject: |
|
|
Das Problem scheint gelöst zu sein. 
Ich habe mal "nomodeset" in die Commandline hinzugefügt und nun scheint es zu gehen.
Das Problem ist aber, dass ich meine alte SSD mittels "dd" auf eine m2 SSD geklont habe und die so rasend schnell ist, dass man von den Meldungen nicht allzu viel mitbekommt.  |
|
| Back to top |
|
|
haegar87
Apprentice
Joined: 08 Jan 2006
Posts: 164
|
| Posted: Sat Mar 09, 2019 11:55 pm Post subject: |
|
|
Das kenne ich. Der erste Start nach Wechsel auf eine m2 SSD hat mich auch "überrascht" 
_________________
"Spielt man die Windows CD rückwärts ab, hört man satanistische Texte!" - "Das ist ja noch harmlos! Wenn man sie vorwärts abspielt, installiert sich das Teufelszeug!" |
|
| Back to top |
|
|
|
Deutsches Forum (German)
