On Saturday 11 November 2006 22:43, Craig White wrote: [...] >> >Now I agree with you that getting rid of the xen kernel solves this >> >problem. I don't agree with you a bit that it wasn't a udev problem >> >because if you again read Comment #5 on the above referenced bugzilla >> >entry, it is obvious that Bill Nottingham believes it is a udev >> > related problem. >> >> I still don't see what, if anything, udev could do about it when the >> hardware has not been detected. Does it have some sort of a magic >> twanger for that case that we common mortals don't know about? I'm >> now looking at that #5 comment, but have no clue because theres no >> preamble describing where to put those commands, which I assume would >> go in /.etc/udev/rules.d/50-udev.rules, but it contains no similar >> rules. Those in the know will I assume know where in that file, but to >> me thats not a usable fix without the whole story. But with some use >> of a figurative shovel to dig a little deeper it seems to indicate it >> should be added into /etc/udev/rules.d/05-udev-early-rules. It would >> be more at home there by far. >> >> Is this correct? > >---- >http://www.reactivated.net/writing_udev_rules.html > >this is where I always refer to when thinking about udev changes > >this suggests your own rule in /etc/udev/rules.d/10-whavever > >05-udev-early-rules might be OK So the way to define this is to add this to the bottom of the 05-udev-early rules and reboot to the xen enabled kernel. I may do that tomorrow, its been a long day now, cleaning up after taking 2 trees down in my front yard yesterday, a 20 year old 35 foot maple and a smaller dogwood. And my chainsaw managed to choose yesterday to kill its ignition module, so much of the trimming was done with a dewalt recipro saw. My hands are numb. And tomorrow, if the weather is dry, a pile of scraps gets fed thru my chipper, and thats another hand burner. >> There is a second reason I didn't pursue that angle, any attempt to >> modprobe anything 8250 related failed due to undefined labels in the >> module(s). Which brings me back to square one, what can udev do >> about it when the kernel can't find the hardware in the first place? > >---- >I honestly don't know for sure - that was Bill Nottingham's suggestion >and he is obviously in a much better position to know these things than >I. I am no expert in udev myself. >---- I would have recognized who that was if it had been Greg KH. Bill I wasn't that familiar with, although I have the corpus of all those lkml messages that flew by fast & furious when udev was under active development a year or so ago. [...] >> Sorry I'm so dense in your opinion. If it will make you feel better, >> I'll plead oldtimers since I had a birthday last month, having made it >> to 72. > >---- >You are who you are. I didn't make any characterization whatsoever. I >helped you fix your serial port and you don't say thanks...ok...that's >fine. I guess I tend to say thanks when the problem is solved, and that time I screwed up because of the frustration over what should have been a simple item. But now I'll say it, many thanks. [...] -- Cheers, Gene
