i have updated suse to kernel 2.6 but am unable to use dvb as the standard suse version of hotplug has no firmware.agent so i have attempted to update it from various sources including source and rpm with no success. All installs correctly with no errors, and if i call hotplug from the command line there are no errors. But when i reboot, during the hotplug loading sequence i get huge amounts of errors, starting with an error about not being able to hotplug pci bus?? There are so many of them and none of them show up in dmesg. They seam to arrise due to some system paths not being correct but i have no idea what they should be or how to set them. $SYSFS/$DEVPATH seems to be one of the majour ones. Unfotuantley this is causing all kind of systems including networking and sound to have issues and has stopped dhcpd from working. Any help would be greatly appreciated.

Cheers in advance.

I get an error that says something like "unable to synthesise pci hotpluging events" but it's a harmless message that doesn't seem to have any effect. I'm unlikely to unplug any pci devices with the power still on. Have you installed pciutils http://atrey.karlin.mff.cuni.cz/~mj/pciutils.shtml and usbutils http://wwwbode.cs.tum.edu/Par/arch/u...load/usbutils/ ?

Hi thanks
That sounds like the same error i am getting. Plus a hell of a lot more!

I have checked and i have version 2.1.11-98 of pci-utilities but no dev and usbutils version 1.0-678.

Do you think not having the dev version of pci-utilities is the problem. It seems unlikely as the previous version had no issues and there where no problems during the source compile of hotplug.

Arggghhhhhhh it was all going so well, oh well back to the drawing board

Anyone help please. Its driving me madd!!!!!!!!!!!!

does hotplug have to run during boot up? On mandrake, I just disabled it b/c it takes so long and I have no problems. Since you can start it manually w/o problems, you might consider disabling it first and then adding it to rc.local (if it's in rc.local, it will get started after everything else and might be less of a problem; if you can start it manually, it should work in rc.local as well).