Comment # 5
on bug 92858
from Darren
Thanks you again for the guide--it was simple and human-readable and I understood the directions, I think. Sadly, as of thus far, every kernel I've compiled panics at bootup, with a message like this, or similar: "kernel panic. vfs unable to mount root on unknown block (0,0)". I'd take a screencapture but there's no way to do so until X is up, and this is before X is started. I've used a config file I built myself via make menuconfig, the default ubuntu 4.3 kernel config file, and the distro's current running kernel (4.1.12) config, obtaining by "zcat /proc/config.gz > .config. The same message occurred under all three of the kernels I built. I'll keep on compiling in the meantime until I isolate the problem, but I did have one question: Let's assume the first kernel I compile boots and acceleration works. After I get the kernel to compile and boot, do I need to run "make clean" in the source tree directory after "git bisect good," or is that going to strip away files that git bisect needs in order to keep a record of good and bad commits?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
