Denis wrote: >> I have ran into things like this before, I usually run make mrproper >> from within the kernel directory to make sure there is no old cruft >> laying around in there. > > In my case, it was a fresh install, which made it quite a bit more > painful to fix because I had to go through the procedures twice and > did not have a working kernel to fall back on. It's the scenario I've > always dreaded, and then one day it actually happens. When I re-did > the install, I erased the partition table and started anew, so there > was no old cruft to begin with. > > I'm not sure if this contributed to anything, but I enabled all the > relevant RAID support the second time around. Since I only have one > SATA drive, I simply turned off RAID support initially in the kernel, > but it's possible that this particular combination of hardware was > expecting a RAID driver... > > I'm so clueless sometimes trying to figure out some of these kernel > options... haha. The really technical ones where it's like a foreign > language. I love the "if unsure, say N here." or "if you don't know > what this is, you probably don't need it - say N here." ;-)
Well, when you download the kernel sources, there can be "old cruft" in there. It does seem to start out with some basic options and I was told once a long time ago to run mrproper to be sure to get it all out. It fixed the problem I was having then and I have done it ever since. Funny thing is, I wonder if that would have helped. Most likely not but something to remember next time. I just checked and I have a newer kernel on here. I may compile the new version and boot it next time. I'm on almost 45 days of uptime so don't hold your breath on me rebooting. LOL Glad you got it running though. Dale :-) :-) :-) -- www.myspace.com/-remove-me-dalek1967 Copy n paste then remove the -remove-me- part. -- [EMAIL PROTECTED] mailing list
