Messages in this thread | | | From | "Andrew Rodland" <> | Subject | Re: CML2 funkiness | Date | Wed, 02 Jan 2002 21:05:44 -0500 |
| |
That reminds me, I use vesafb, and I get a just plain black screen on boot, if I use CML2 to configure the kernel. I'd assume it's just because there are one or two FB-related symbols that seem to be getting dropped.
On 02 Jan 2002 17:42:47 -0800 Miles Lane <miles@megapathdsl.net> wrote: > I am seeing other problems. Using CML2 with a > 2.4.18-pre1 > tree, I was unable to create a kernel that would boot. > It kept crashing with messages stating that the rivafb > driver > did not support 8-bit color depth. I tried tweaking my > configuration for a while, but finally reverted to CML2 > and was then able to get a working kernel. I'll > investigate > further and send along a diff of the working and broken > configuration files. > > Another thing I notice is that when I create a > configuration > using CML2, then switch to CML1 and run "make oldconfig" > using the same kernel tree, it appears there are > configuration > options that never got set in the CML2 .config file. > I suppose this may simply be due to CML2 writing out the > options in a different order. > > Miles >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |