Paul Hartman wrote: > On Thu, Apr 16, 2009 at 2:58 PM, Dale <rdalek1...@gmail.com> wrote: > >> Also, how does one "restart" udev? Does going to "rc single" then back >> to "rc default" restart udev? Surely a person doesn't have to reboot to >> do this. >> > > /etc/init.d/udev restart > > is what i would try :) > > >
Here is the results. I went back to my old gcc and did a "emerge -ev ivman". I ran "revdep-rebuild -i" afterwards to make sure everything was good there. All was well with the links and such. I then rebooted and booted a CD. I made sure my printer was on and hooked up my camera as well. Both devices showed up in the list on "lsusb". That cleared my hardware. Hardware is good. Whew!! I then booted back from the hard drive to my old kernel, 2.6.23. I logged into KDE and after the desktop came up and all my usual windows opened from my saved session, I turned my camera back on. I then went to run lsusb but before I could do that, the icon was on my desktop and shortly after that the pop up window came up. KDE sees my camera and lsusb shows both products. Given the fact that all I did was recompile with the older gcc, I suspect there is something wrong with what the newer gcc was compiling. Here is gcc-config: r...@smoker / # gcc-config -l [1] i686-pc-linux-gnu-4.1.2 * [2] i686-pc-linux-gnu-4.3.2 r...@smoker / # I was using gcc 4.3 but switched back to gcc 4.1. I'm not a developer and I don't feel right about filing a bug since I can't really tell them what is broke but something is wrong somewhere. I have not syncd my tree and it was a reinstall of the same version of packages. No config files were updated or listed that needs to be updated either. Basically, the only difference is the compiler. Ideas? Thoughts? Thanks much for the help too. Dale :-) :-)
