[email protected] wrote: > On Tue, Dec 25, 2012 at 08:56:56AM -0600, Bruce Hill wrote: > >> I would suggest you run "lspci -nnk" with your running 3.6.10 kernel and save >> that output. Then go into the kernel source directory for 3.7.1, run "make >> mrproper" then "make defconfig" and enable all the kernel drivers listed in >> the "lspci -nnk" output, as well as the drivers for your IDE/SATA >> controllers, >> and / filesystem. That kernel should boot you, and will get rid of a lot of >> the cruft from the present bloated kernels. > Made a minimal 3.7.1 kernel, much smaller and compiled nice and fast. > Hung just like the bloated one, drat. > > So I guess I will read up on bisecting. I know the principle, but > have never tried it. I suppose one starting point is make sure a > pure-vanilla 3.6.10 kernel boots. >
This is what I would try: Do a lspci -k from whatever Linux you can boot, sysrescue CD or stick comes to mind here. That should list the drivers you need for hardware. Then mount partitions so you can get to /usr/src/<kernel here> and cat the config file and make sure the results from lspci are built INTO the kernel, not modules but built INTO the kernel. You could even do: 'cat .config | grep -i <driver name from lspci -k here>' Repeat that for each driver. Remember, arrow up keys for that one. Saves you some typing. lol If you have those built in, the only thing to check then is that the file system for / is also built INTO the kernel. That has always got me to at least a console login. Some other hardware may not work but you can boot and fix from inside the OS instead of booting DVD, USB stick or whatever and having to mount and such. That is such a pain to do. Maybe that will help. At least get you to a console. That alone makes fixing something else easier. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
