Bugzilla - Modeset - Kernel 3.4 to 3.6 upgrade no longer boots

[Steve T]

Good afternoon,
I have been running my laptop on various versions of FC without a
problem and am currently on FC16 running Gnome 3 in full mode. 
Recently the FC16 Kernel was updated from 3.4.11 to 3.6.2 and my laptop
(Dell Latitude D610 ) would no longer boot - although I could go back to
any  3.4 kernel and it booted ok and worked under Gnome 3. There were no
messages on the failed 3.6.x boot - the screen just went blank. After a
bit of delving it seemed that a similar problem had been reported in
relation to Plymouth and modesetting. Following that track lead me to
'Bug 845745 - kernel version 3.5.0-2 hangs at boot with modesetting:
"conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic
driver" ' on Fedora Bugzilla.
I did try the 'nomodeset', and that does allow a boot under 3.6.2, but
then Gnome 3 goes into fallback mode.

Does anyone know if this will be fixed under FC16, or is this a generic
Kernel fix that will appear across all releases that use that kernel?

[Steve T]

On Mon, 2012-10-29 at 16:15 +0000, Steve T wrote:
>  Good afternoon,
>  I have been running my laptop on various versions of FC without a
>  problem and am currently on FC16 running Gnome 3 in full mode. 
>  Recently the FC16 Kernel was updated from 3.4.11 to 3.6.2 and my
>  laptop (Dell Latitude D610 ) would no longer boot - although I could
>  go back to any  3.4 kernel and it booted ok and worked under Gnome 3.
>  There were no messages on the failed 3.6.x boot - the screen just went
>  blank. After a bit of delving it seemed that a similar problem had
>  been reported in relation to Plymouth and modesetting. Following that
>  track lead me to 'Bug 845745 - kernel version 3.5.0-2 hangs at boot
>  with modesetting: "conflicting fb hw usage radeondrmfb vs VESA VGA -
>  removing generic driver" ' on Fedora Bugzilla.
>  I did try the 'nomodeset', and that does allow a boot under 3.6.2, but
>  then Gnome 3 goes into fallback mode.
>  
>  Does anyone know if this will be fixed under FC16, or is this a
>  generic Kernel fix that will appear across all releases that use that
>  kernel?  
Does anyone know how to get around this issue? Presumably the monitor
must have been recognised by the 3.4 kernels - does anyone know how I
can get the monitor to be recognised by the 3.6 kernels?