AFAIK systemd still utilizes modprobe and honors anything listed in /etc/modprobe.d/*. If you could pastebin the output of "dmesg" and:
sudo su -c 'journalctl -b'
then perhaps I or someone else could dig through and see if something sticks out.
Last edited by mynis01 (2013-06-29 04:21:28)
Found the part in dmesg where the driver is being loaded:
[ 10.667736] [drm] Initialized drm 1.1.0 20060810 [ 10.805695] usb 3-1.4: New USB device found, idVendor=2232, idProduct=1029 [ 10.805702] usb 3-1.4: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 10.805706] usb 3-1.4: Product: WebCam SC-13HDL11939N [ 10.805709] usb 3-1.4: Manufacturer: Generic [ 10.805712] usb 3-1.4: SerialNumber: 200901010001 [ 10.835670] [drm] Memory usable by graphics device = 2048M [ 10.835673] checking generic (d0000000 580000) vs hw (d0000000 10000000) [ 10.835674] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver [ 10.835684] Console: switching to colour dummy device 80x25
Nothing in journalctl appears to be relevant, all though I did take note that you removed udev. Give me the output of this:
lsmod | grep uvcvideo
Just a quick note that a newer version of systemd came to the experimental repos last week (version 204, much newer than the old version 44-1). I have installed it on my Sid system and it is working very well. Bootup times are marginally faster, shutdowns take very nearly no time. I've had no problems at all with it.
A warning - I just tried this with a new Waldof install. The boot times were no faster with systemd, and rebooting was disabled (system just hung at "tty1 login"). I tried to get sysvinit back on and get rid of systemd, but that now just results in a kernel panic whenever I try to boot. I'm currently trying to decide between a fresh install (it was only 1 day old anyway) or accessing the drive via another method to try to undo the damage.
System back up and running now, but rebooting is still a problem. Can anyone describe how to set sysvinit back to how it is in "vanilla" Waldorf before the changes made by installing systemd and systemd-sysv? I've reinstalled the package, but that on its own hasn't put things back to normal.
Last edited by KFC (2013-07-26 15:02:12)
I've now go rid of systemd and the machine boots up without any obvious problems (wasn't using autologin previously so can't confirm that issue), but shutdown and reboot still make the system halt at the tty1/login screen then freeze there. I'm looking for instructions on how to get sysvinit running exactly as it is in a fresh #! install, but all the sites I find only describe installing systemd, not removing it
Update: Did a fresh install, I think the shutdown issue is actually related to mounting network drives in fstab - with that turned off, the shutdown and reboot work again, so I'll just have to stick to Thunars network tool rather than a DIY method. With regard to systemd, my boots were under 15 seconds with or without it (stopwatch timed, not the artificially reduced numbers from systemd-analyze most people seem to be using), so I don't see the sense in taking the risk of removing core packages.
Last edited by KFC (2013-07-27 11:32:51)
I tried this, and decided against keeping it after SLIM started acting up. I had to use the following commands to get back sysvinit.
echo systemd-sysv purge | sudo dpkg --set-selections sudo apt-get update && sudo apt-get dist-upgrade sudo shutdown -r now
Fast boots and shutdowns are nice, but I use a laptop. Most of the time I just put her to sleep by closing the lid. If I'm actually booting, something went wrong.