Hallo zusammen,
nach du gestern tauchen beim booten Meldungen auf:
udevd[845]: failed to execute '/lib/udev/socket:@/org/freedesktop/hal/udev_event' 'socket:@/org/freedesktop/hal/udev_event': No such file or directory
Pc bootet aber normal weiter und arbeitet scheinbar ohne
Funktionseinschränkung.
inxi:
System: Host: siductionbox Kernel: 3.11-6.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.8.2)
Desktop: KDE 4.11.2 (Qt 4.8.6) Distro: siduction 11.1 One Step Beyond - kde - (201112302141)
Machine: Mobo: ASUSTeK model: P8Z68-V LE version: Rev X.0x serial: MT7018K01502893
Bios: American Megatrends version: 4002 date: 12/14/2012
CPU: Quad core Intel Core i5-2500K CPU (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 26487.5
Clock Speeds: 1: 3597.00 MHz 2: 3696.00 MHz 3: 4158.00 MHz 4: 2244.00 MHz
Graphics: Card: NVIDIA G92 [GeForce GTS 250] bus-ID: 01:00.0
X.org: 1.14.3 driver: nvidia tty size: 112x42 Advanced Data: N/A for root
# apt-cache policy xserver-xorg-video-nvidia
xserver-xorg-video-nvidia:
Installiert: 325.15-2.siduction.1
Installationskandidat: 325.15-2.siduction.1
Gruß, qwerthi.
Hi @qwerthi, deine udevd-Meldungen beziehen sich doch alle auf hal, das nicht mehr gepflegt wird und daher wohl auch bei dir nicht mehr benötigt wird.
Bei mir waren es ca. 100 Meldungen beim Systemstart und alle von hal, dies ist ein bug der bei Debian schon gemeldet ist, Hilfe hierbei schafft eine Deinstallation von hal, eventuell auch noch mit purge Reste entfernen, Abhilfe.
Hi DeKa,
vielen Dank für den Hinweis.
Purgen von hal brachte die Lösung.
qwerthi
Am I understanding correctly that
apt-get remove --purge hal
removes these messages?
YES!
apt-get remove --purge hal -sdoes not show any other package then hal to be removed.
But can I be sure there is none needing it? k3b?
Zitat von: "michaa7"apt-get remove --purge hal -sdoes not show any other package then hal to be removed.
But can I be sure there is none needing it? k3b?
You
cannot be sure! E.g. I like to use the free internet TV of voxnow.de - and alas their DRM system "Flash Access" needs hal to be installed on the customer's linux system!! I've had some debates with the voxnow support about hal being obsolete in modern linux systems but if I want to watch the streams there must be hal on my system, even if no other package references it...
no package in siduction depend on hal, third pary tools can still use it - michaa7, give it a try - btw - no flavour of siduction contain hal for ages.
if hal is installed, one can test if hal is really needed with:
aptitide why hal
Is there some apt aquivalent to "aptitude why hal" (I guess you wanted to write that ;), agaida)?
But without having tested that command as I don't want to install aptitude, I am quite sure it does only reveal dependencies to installed packages. Would it reveal that some sites require it for Flash-DRM checks?
i don't know any apt replacement for that
@agaida
Thanks for that hint. I still wonder if it relies on propper Debian package building (The output of the command suggest that it is depending on what a packer/maintainer not forgetts to add).
So I'd suggest to use it with some caution as it won't analyse the whole bunch of syscalls or whatever it needed to be sure.
@ SP
I don't remember it was me who installed aptitude, but it's there. I'm too lasy to check the respective manifest, but maybe it's installed on your system, too. Anyway, that's the output here:
Zitat# aptitude why hal
i flashplugin-nonfree Schlägt vor hal
In this case it seems aptitude makes a find only within the "suggests" section of the description of one package, and finds nothing that really "depends" on hal (in the sense of 'package only working if it is installed'). And from what one can get from googeling and Debian bug reports, it seems really only flash in combination with tv is affected, as you already noticed.
@agaida: Wow, thanks for the aptitude tip. Where do you dig out all that knowledge??? :shock:
@michaa7: Same here. I'll go to purge hal though . . .
Zitat von: "farinet"@agaida: Wow, thanks for the aptitude tip. Where do you dig out all that knowledge???
working with? Reading "man aptitude"?
And yes, I need such hints, too, because I'm not reading man pages except I have a *particular* reason to do so.
@farinet: michaa7 is right, working with, the need to solve situations where apt-get not fits for. But keep in mind that aptitude can be a beast sometimes, when one use it with sid. Thats why we recommend the usage of apt-get.
The resolver in aptitude is really cool and much more sophisticated in relation to the solver in apt-get. In most of the cases is the aptitude resolver simply to clever for a fast moving target like sid. So be very careful with it or better don't use it when it is not needed.
@michaa7: Thanks for the output of the aptitude command. As aptitude is not installed on my system I guess you have installed it in some "inspired" minute ;).
udevd[438]: failed to execute '/lib/udev/kmod' 'kmod sg': No such file or directory
hal ist nicht installiert
Do not know if resolved, but the appears to be a typo problem.http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0 (http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=f11a2ddeb6a43f99179f2f9d322ee08cb41db5b0)
@LRC62, you can override this udev rule by
cp /lib/udev/rules.d/80-drivers.rules /etc/udev/rules.d/80-drivers.rules
and edit an additional "load" in this /etc/udev/rules.d/80-drivers.rules
(don't forget deleting this file at a certain point in the future!)