[01:10] <philipballew> can someone help me track down a driver for a netgear wpn111
[01:10] <philipballew> usb wifi
[07:50] <Q-FUNK> howdy! is there an official ubuntu method for declaring gfxpayload in Oneric?
[08:00] <Q-FUNK> I still get the warning if I use vga=XXX in the boot options, but no instruction on where to declare the corresponding GFXPAYLOAD
[13:27] <bullgard4> What is the function of the process »netns«? http://lxr.linux.no/#linux+v2.6.35.8/Documentation/ :Filename search: netns did not enlighten me. 
[17:30] <BigWhale> Greetings... Are there any huge differences between 3.0.0-11 and 3.0.0.12 because the latter refuses to boot... It just hangs after it loads initrd ...
[21:51] <Q-FUNK> cjwatson: thanks for your precision about GRUB_GFXPAYLOAD_LINUX=keep, but it still doesn't explain how to transition from vga=mode to gfxpayload.
[23:12] <cjwatson> Q-FUNK: the manual should, providing you know what mode the vga= rune corresponds to
[23:13] <Q-FUNK> cjwatson: the point is, grub complains that vga=mode is obsolete and that "set gfxpayload=XXXxYYY" should be used instead.  it doesn't say where or how.
[23:13] <cjwatson> read the manual
[23:14] <cjwatson> please?
[23:14] <Q-FUNK> cjwatson: it's also a lot more involved than adding GRUB_GFXPAYLOAD_LINUX=keep, as I found out.
[23:15] <Q-FUNK> the manual doesn't document /etc/default/grub afaik.
[23:15] <cjwatson> anyway, my goal was just to correct a misconception in a public bug report as these things have a way of being googleable and confusing others
[23:15] <cjwatson> sure does
[23:15] <cjwatson> http://www.gnu.org/software/grub/manual/grub.html#Simple-configuration
[23:19] <Q-FUNK> cjwatson: ok.  thanks for that pointer.  however, noticed my last comment on that bug?
[23:19] <cjwatson> yes.  we know.
[23:20] <Q-FUNK> ok. why hasn't framebuffer=y become standard, then?
[23:20] <cjwatson> because it slows down boot performance
[23:20] <cjwatson> rock, meet hard place
[23:21] <cjwatson> if you wish to edit things locally such that you still use vga= (the mechanism for doing so is discussed in the manual), feel free
[23:22] <cjwatson> well, not discussed in detail I suppose, it doesn't explain that you need to edit /etc/grub.d/10_linux to do that, which is unfortunate
[23:22] <cjwatson> I don't think most people are best off doing that
[23:23] <cjwatson> and GRUB_GFXPAYLOAD_LINUX=keep is deliberately not retained in recovery mode; that's a recent change because it was causing practical problems
[23:23] <cjwatson> basically none of this is a kernel bug, anyway ...
[23:25] <Q-FUNK> well, it was difficult for me to know whether grub or the kernel was the culprit. as it now appears, those are all deliberate grub design choices.  
[23:25] <cjwatson> sort of
[23:26] <cjwatson> using the 32-bit entry point is a deliberate design choice (better consistency across platforms), which implies vga= not working
[23:26] <Q-FUNK> that those new design ideas turn the process of setting the framebuffer into a much more complex gig and that it's not remotely as simple or accross the board as vga=mode apparently was dismissed.
[23:26] <cjwatson> I'm not going to engage in a debate that takes this tone though
[23:27] <Q-FUNK> using 32-bit is ok.  no longer applying the previous accross the board solution is not.
[23:27] <cjwatson> I was going to explain in detail but not now.
[23:27] <cjwatson> bye.
[23:27] <Q-FUNK> *sigh*