On Thu, 2012-02-16 at 09:53 +0000, Colin Guthrie wrote: > 'Twas brillig, and Robert Fox at 16/02/12 09:49 did gyre and gimble: > > Thanks for the fast response Col - I do still have hal installed, and I > > stopped hald, but didn't seem to help. BTW, it's safe to use > > "drakxservices" to start and stop services even though we are using > > systemd now, right?? > > Try disabling it via systemctl disable hald.service and reboot. > > You can use drakxservices to start/stop but it wont list non-sysvinit > services. We need to port it. It was discussed the other day actually. > > Col >
Removed hal altogether (urpme) - then got a strange list of orphans: The following packages: hal-info-0.0-5.20091130.3.mga1.noarch lib64boolstuff0.1_0-0.1.13-2.mga1.x86_64 lib64ffado2-2.0.1-5.mga2.x86_64 lib64vlccore4-1.1.13-1.mga2.tainted.x86_64 lib64xml++2.6_2-2.34.2-1.mga2.x86_64 quvi-0.4.1-1.mga2.x86_64 radeon-firmware-20110601-4.mga2.nonfree.noarch usbutils-005-1.mga2.x86_64 x11-driver-video-ati-6.14.3-3.mga2.x86_64 x11-driver-video-cirrus-1.3.2-7.mga2.x86_64 x11-driver-video-fbdev-0.4.2-7.mga2.x86_64 x11-driver-video-glint-1.2.6-4.mga2.x86_64 x11-driver-video-intel-2.17.0-3.mga2.x86_64 x11-driver-video-mach64-6.9.0-3.mga2.x86_64 x11-driver-video-mga-1.4.13-6.mga2.x86_64 x11-driver-video-neomagic-1.2.5-6.mga2.x86_64 x11-driver-video-nv-2.1.18-6.mga2.x86_64 x11-driver-video-openchrome-0.2.905-1.mga2.x86_64 x11-driver-video-r128-6.8.1-7.mga2.x86_64 x11-driver-video-radeonhd-1.3.0-6.git20100512.3.mga2.x86_64 x11-driver-video-s3-0.6.3-6.mga2.x86_64 x11-driver-video-s3virge-1.10.4-6.mga2.x86_64 x11-driver-video-savage-2.3.3-3.mga2.x86_64 x11-driver-video-sis-0.10.3-6.mga2.x86_64 x11-driver-video-sisimedia-0.9.1-1.20091203.11.mga2.x86_64 x11-driver-video-sisusb-0.9.4-6.mga2.x86_64 x11-driver-video-tdfx-1.4.3-6.mga2.x86_64 x11-driver-video-trident-1.3.4-6.mga2.x86_64 x11-driver-video-v4l-0.2.0-11.mga2.x86_64 x11-driver-video-vesa-2.3.0-9.mga2.x86_64 x11-driver-video-vmware-11.1.0-1.mga2.x86_64 are now orphaned, if you wish to remove them, you can use "urpme --auto-orphans" Did not remove orphans, but rebooted and problem still exists as before - so most likely NOT a hal issue . . .
