Raffaele BELARDI <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Mon, 22 Sep 2008 10:27:12 +0200:
> http://bugzilla.kernel.org/show_bug.cgi?id=11599 > > I got an answer within a couple of hours, looks like it is a know hw bug > in the chipset. I was suggested to try with 2.6.27-rc6, I'm downloading > it now. > > Hope I don't hit the same problem Duncan is experiencing when compiling > 2.6.27... FWIW, 2.6.27-rc7 is out now tho I've not tried it yet. ... And my compiling problem turned out to be due to usage of the KBUILD_OUTPUT var to set the output-dir, as detailed in the makefile. That's certainly a bug since it /is/ documented in the makefile, but at least there's a way around it now. (That said, now that I can compile, there's another bug in actually getting -rc6 to run (again I've not yet tried -rc7), grub loads the kernel or I'd have a grub error (I tried it by pointing grub at a non- existent file), but there's no early console output at all from it and it self-reboots pretty quickly, so the init must be failing pretty early. I'm running radeonfb tho, without vgacon even compiled in. I should try it with the standard vgacon and see if that works.) So anyway, as long as you are compiling into the kernel sources tree itself (or, reports are, setting the output dir from the command line instead of by var), you should avoid the compile problem I had, and hopefully you don't hit whatever other bug it is I'm hitting with -rc6, and hopefully it's fixed for me in -rc7. =:^S -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
