Public bug reported:
Using the Kernel Modesetting in 2.6.30-rc1 and going to Rescue Mode, the
kernel modesetting driver is loaded and the screen display goes blank.
The computer is still working, but the internal LVDS encoder is not
associated with the LVDS screen in the driver. I've noted this u
Public bug reported:
Using the Kernel Modesetting in 2.6.30-rc1 and going to Rescue Mode, the
kernel modesetting driver is loaded and the screen display goes blank.
The computer is still working, but the internal LVDS encoder is not
associated with the LVDS screen in the driver. I've noted this u
Public bug reported:
Using the Kernel Modesetting in 2.6.30-rc1 and going to Rescue Mode, the
kernel modesetting driver is loaded and the screen display goes blank.
The computer is still working, but the internal LVDS encoder is not
associated with the LVDS screen in the driver. I've noted this u
Public bug reported:
Using the Kernel Modesetting in 2.6.30-rc1 and going to Rescue Mode, the
kernel modesetting driver is loaded and the screen display goes blank.
The computer is still working, but the internal LVDS encoder is not
associated with the LVDS screen in the driver. I've noted this u
Public bug reported:
Using the Kernel Modesetting in 2.6.30-rc1 and going to Rescue Mode, the
kernel modesetting driver is loaded and the screen display goes blank.
The computer is still working, but the internal LVDS encoder is not
associated with the LVDS screen in the driver. I've noted this u
Public bug reported:
Using the Kernel Modesetting in 2.6.30-rc1 and going to Rescue Mode, the
kernel modesetting driver is loaded and the screen display goes blank.
The computer is still working, but the internal LVDS encoder is not
associated with the LVDS screen in the driver. I've noted this u
