Autor Thema: Boot takes 3 minutes after installing Sundtek USB DVB-S2 driver  (Gelesen 3872 mal)

MikeT23

  • Newbie
  • *
  • Beiträge: 5
    • Profil anzeigen
Boot takes 3 minutes after installing Sundtek USB DVB-S2 driver
« am: Dezember 06, 2014, 08:08:44 Nachmittag »
I have recently updated to OpenSuse 13.2 (complete re-installation) on a 64 bit computer.
After I installed the Sundtek driver for my Sundtek USB DVB-S/S2, booting now takes
3 minutes. If I remove the driver, the boot process is again very fast. With
the same device on the same computer running OpenSuse 12.2, I had no problems, it
installed easily & had no problems.
Can anyone please help or advise what to do?

The boot.log contains:
g for udev Wait for Complete Device Initialization (55s / 2min 59s)
[  *** ] A start job is running for udev Wait for Complete Device Initialization (56s / 2min 59s)
[   ***] A start job is running for udev Wait for Complete Device Initialization (56s / 2min 59s)
[    **] A start job is running for udev Wait for Complete Device Initialization (57s / 2min 59s)
[     *] A start job is running for udev Wait for Complete Device Initialization (57s / 2min 59s)
.....
..... the same for 3 minutes ....
.....
[ ***  ] A start job is running for udev Wait for Complete Device Initialization (2min 58s / 2min 59s)
[***   ] A start job is running for udev Wait for Complete Device Initialization (2min 58s / 2min 59s)
[**    ] A start job is running for udev Wait for Complete Device Initialization (2min 59s / 2min 59s)
[*     ] A start job is running for udev Wait for Complete Device Initialization (2min 59s / 2min 59s)
[FAILED] Failed to start udev Wait for Complete Device Initialization.
See "systemctl status systemd-udev-settle.service" for details.
         Starting Activation of LVM2 logical volumes...
[  OK  ] Started Activation of LVM2 logical volumes.
[  OK  ] Reached target Encrypted Volumes.
         Starting Activation of LVM2 logical volumes...
[  OK  ] Started Activation of LVM2 logical volumes.
[  OK  ] Reached target Local File Systems.
         Starting Shadow /etc/init.d/boot.localfs...
[  OK  ] Started Shadow /etc/init.d/boot.localfs.
         Starting LSB: Set default boot entry if called...
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Trigger Flushing of Journal to Persistent Storage...
         Starting Create Volatile Files and Directories...
[  OK  ] Started Trigger Flushing of Journal to Persistent Storage.
[  OK  ] Started Create Volatile Files and Directories.
         Starting LSB: AppArmor initialization...
         Starting Security Auditing Service...
[  OK  ] Started LSB: Set default boot entry if called.
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Security Auditing Service.
         Starting Update UTMP about System Reboot/Shutdown...
[  OK  ] Started Update UTMP about System Reboot/Shutdown.
[  OK  ] Started LSB: AppArmor initialization.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on Open-iSCSI iscsid Socket.
[  OK  ] Listening on PC/SC Smart Card Daemon Activation Socket.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Timers.
         Starting Restore Sound Card State...
[  OK  ] Reached target Basic System.
         Starting Machine Check Exception Logging Daemon...
[  OK  ] Started Machine Check Exception Logging Daemon.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Permit User Sessions...
         Starting Name Service Cache Daemon...
         Starting WPA Supplicant daemon...
         Starting Modem Manager...
         Starting irqbalance daemon...
[  OK  ] Started irqbalance daemon.
         Starting Sundtek MediaTV...
         Starting /etc/init.d/boot.local Compatibility...
         Starting D-Bus System Message Bus...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started WPA Supplicant daemon.
         Starting SuSEfirewall2 phase 1...
[  OK  ] Started Restore Sound Card State.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Name Service Cache Daemon.
[  OK  ] Started Sundtek MediaTV.
         Starting Authorization Manager...
[  OK  ] Reached target User and Group Name Lookups.
         Starting Login Service...
[  OK  ] Reached target Host and Network Name Lookups.
         Starting X Display Manager...
[  OK  ] Started Sundtek MediaTV.
[  OK  ] Started Login Service.
         Starting Locale Service...
[  OK  ] Started Sundtek MediaTV.
[  OK  ] Started Authorization Manager.
[  OK  ] Started Locale Service.
[  OK  ] Started Modem Manager.
[  OK  ] Started Sundtek MediaTV.
[  OK  ] Started Sundtek MediaTV.
[  OK  ] Started Sundtek MediaTV.
[  OK  ] Started Sundtek MediaTV.
[  OK  ] Started Sundtek MediaTV.
[  OK  ] Started X Display Manager.
[  OK  ] Created slice system-systemd\x2drfkill.slice.
         Starting Load/Save RF Kill Switch Status of rfkill0...
         Starting Bluetooth service...
[  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.
[  OK  ] Started Bluetooth service.
[  OK  ] Reached target Bluetooth.
         Starting Hostname Service...

The Sundtek driver was installed with:

# cd /tmp
# wget http://www.sundtek.de/media/sundtek_netinst.sh
# chmod 777 sundtek_netinst.sh
# sudo ./sundtek_netinst.sh

with no errors:

Wollen Sie fortfahren [J/N]:
y
adding /opt/bin to environment paths
unpacking...
checking system... testing libc OK 2.19.0
64Bit System detected
installing (netinstall mode) ...
Downloading architecture specific driver ... 64bit
Download finished, installing now ...
installing remote control support
finalizing configuration... (can take a few seconds) 
installing libmediaclient interception library
Starting driver...
done.
linux-s7qt:/tmp #

The problem seems to be related to something called systemd-udev-settle.service

mike@linux-s7qt:~> systemctl status systemd-udev-settle.service
systemd-udev-settle.service - udev Wait for Complete Device Initialization
   Loaded: loaded (/usr/lib/systemd/system/systemd-udev-settle.service; static)
   Active: failed (Result: timeout) since Sat 2014-12-06 15:53:03 GMT; 26min ago
     Docs: man:udev(7)
           man:systemd-udevd.service(8)
  Process: 468 ExecStart=/usr/bin/udevadm settle (code=killed, signal=TERM)
 Main PID: 468 (code=killed, signal=TERM)

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 7705
    • Profil anzeigen
Re:Boot takes 3 minutes after installing Sundtek USB DVB-S2 driver
« Antwort #1 am: Dezember 07, 2014, 07:56:03 Nachmittag »
We'll check it within the next days.... it's a systemd configuration issue if it happens.
Sundtek Support Engineer

MikeT23

  • Newbie
  • *
  • Beiträge: 5
    • Profil anzeigen
Re:Boot takes 3 minutes after installing Sundtek USB DVB-S2 driver
« Antwort #2 am: Dezember 14, 2014, 09:30:37 Nachmittag »
Solved.

In openSUSE, there is something called lvm2-activation-generator
which is invoked by 2 service files: lvm2-activation-early.service and
lvm2-activation.service.

I have no idea why installing the Sundtek driver causes a problem with these but as I don't use LVM, I've followed the advice to mask these two services and now my boot time is back to a few seconds.

The commands to disable them (as root):

systemctl mask lvm2-activation-early.service
systemctl mask lvm2-activation.service