[gobolinux-users] udevd errors during HAL upgrade

[Michael Homer]

On 10/28/07, Hisham Muhammad <hisham.hm at gmail.com> wrote:
> On 10/25/07, Michael Homer <gobo-users-dufus at wotfun.com> wrote:
> > On 10/25/07, Michael Homer <gobo-users-dufus at wotfun.com> wrote:
> > > On 10/25/07, Hi There <goboster at yahoo.com> wrote:
> > > > I got a bunch of errors when upgrading HAL which was pulled in by upgrading to
> > > > KDE-Base 3.5.8. The errors came from from udevd during HAL (or possibly
> > > > HAL-Info) package installation.
> > > Same here. I don't think I get those specific messages (or any visible
> > > errors at all, come to think of it), but most HAL-related things
> > > didn't work, and the daemon appeared to have died silently at some
> > > points. It's worth noting though that part of the problem seems to be
> > > the KDE packages themselves; rewinding HAL alone didn't fix the
> > > problem.
> > I should clarify what I meant by that; the 3.5.8 packages didn't work,
> > or rather KDM caused X to die trying to load a pci module of some
> > description (startx worked). Symlinking back to 3.5.7 didn't restore
> > old behaviour for automounting or media:/, but did make KDM work. I
> > had to perform the given steps to have that function again. They may
> > not all be necessary, since I've reassembled them from the results of
> > quite a bit of experimenting.
>
> Strange. I haven't tested KDM yet, but the KDE 3.5.8 packages seem to
> work well with HAL here:
I'm going to investigate it further in a couple of days when I get
some time together. It seemed very odd that KDM would cause X to load
additional modules it wouldn't do on its own, so it may be some
configuration quirk on my system. The HAL problems may have had more
to do with an inconsistent system state than anything else, since I
symlinked them out when KDM didn't run. Hopefully I can track them
both down.
-Michael