Bugzilla – Bug 104676
YaST must write config status for *all* hardware devices
Last modified: 2005-09-05 10:54:30 UTC
yast should save the hardware config status of every hardware it configures. The reason is that the config files will be saved with the UDI as key (even when yast uses the old UniqueID) and so build a relation between old keys and new UDIs. This is necessary for desktop apps to know that a device has been configured (they use UDIs). For an update, it is possible to do this e.g., via 'hwinfo --pci --block --mouse --save-config=all'
the update is a blocker - otherwise the suseplugger will tell you _a lot_ about your computer you never wanted to know :)
Jiri, the command above should be probably called during update. TV and sound cards write hardware config status of configured/unconfigured cards using SCR::Write(.probe.status.configured, unique, `yes). Klaus, I noticed that you made a change in probe agent to support UDI. Does the above SCR call write also UDI? Or do I need to change the yast hardware modules?
Currently no changes are necessary. libhd maps unique -> udi.
If I understand comment #3 correctly, the command in initial report is the only needed comment. Done in SVN, will submit to STABLE once Beta2 is out (will be fixed in Beta3).
(note: new installation) Saving the config status no longer works in beta-4. KDE will ask confirmation for all kinds of hardware. It is really *really* important that yast stores a config files for every hardware it configures. There's no other way the HAL-based tools know that it is not new hardware and the user will get popups all the time.
And what am I supposed to call durin fresh installation to store the settings? The command in intial comment is supposed to be only for update if I understand correctly.
This sounds to me like a problem of each indiviaual hardware module (during fresh installation). I suggest (unless there is "one command solving all") you should file bugreports to particular module maintainers for the problematic modules/hardware.
I'm talking my mouth off for years now and have given up all hope that the mouse module, for example, will ever save a config file. There seem to be two problems: a) not all modules store a config (e.g. mouse) b) for those that do, it doesn't work properly (for some unknown reason - might be the hardware agent) A very evil band-aid would be to run the above command, added with '--keyboard --isdn' for good measure, and then do [ -d /var/lib/hardware/udi/org/freedesktop/Hal/devices ] && \ perl -pi -e "s/hwinfo.configured = 'new'/hwinfo.configured = 'no'/" \ /var/lib/hardware/udi/org/freedesktop/Hal/devices/* But b) must be researched nevertheless.
Ok, the reason for b) is that hald is not running. I've opened a separate bug for this: bug 114667.
So, why did this work in beta3 and not anymore in beta4?
A good question. There seems to be even another problem (bug 114682).
Since this worked in beta3 and not in beta4, this is not a new feature.
Then its not needed for each and every device ;-)
it never actually worked. I just disabled the check because I was asked to do so to make the beta halfway usable.
ad 14: Jiri, run it at the end of the installation. It'll catch all the devices yast didn't care about.
Jiri, could you do this, please?
Done, yast2-installation and skelcd-control-SUSELinux-Prof have just been submitted to STABLE/NOARCH.