Comment # 17 on bug 1089116 from Michal Srb

(In reply to Bit Juggler from comment #16)
> Well, there are still lots of errors in the Xorg.0.log:

As far as I can tell, these errors are harmless (should be considered as
warnings).

> [   567.532] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -19

Following the bumblebee tutorial you blacklisted nouveau and did not install
nvidia. X server sees nvidia GPU and tries to use xf86-video-nouveau, which
tries to open a DRM device for that PCI address, but founds none (there is none
because the nouveau kernel module is blacklisted), so it displays this error
and X server falls back to fbdev.

> [   567.737] (EE) FBDEV(0): FBIOPUTCMAP: Device or resource busy

Here I am less sure on how big issue is it, but I think it should not be
problem either. The fbdev driver failed to set palette for the nvidia's
framebuffer. Perhaps the nvidia's fbdev implementation does not support it. It
may prevent things like setting gamma correction, but the rendering should
still work.

As per comment #4, you do not plan to use fbdev after the installation anyway.

> [   567.744] (EE) AIGLX: reverting to software rendering

This is not a problem. The the GLX extension is enabled so X server will
provide it, but none of its drivers actually supports acceleration (no nvidia
or nouveau), so it has to fallback to software rendering.

(In reply to Bit Juggler from comment #4)
> > Boot from USB-Stick with kernel parameters "acpi_os_name="Linux"
> > nouveau.modeset=0 3"
> 
> Those parameters were only used to boot the installation media for
> installation and to boot the very first time after installation in order to
> install all software necessary to run bumblebee (both times in runlevel 3).
> 
> After that no kernel parameters are used.

So now with the patched X server you were able to boot and get to console
without crashing. If you proceed with the bumblebee setup, do things work
right? If not, the bug is assigned to bumblebee maintainer.