search for: nvc0_mc_oclass

...mmiotrace the blob (version 325 or later) to see >>> which registers it fiddles with? Or alternatively, if you have a NVCE >>> card (you never did end up providing the logs which would have made >>> that apparent), could you try replacing nvc3_mc_oclass with >>> nvc0_mc_oclass for the 0xce case in >>> drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without >>> the MSI disabling.) The switch has already been made for NVC8 in >>> 0bae1d61c75 -- perhaps there are more "odd" ones. >>> >>> -ilia >>&...

...t; it. > Any chance you might mmiotrace the blob (version 325 or later) to see > which registers it fiddles with? Or alternatively, if you have a NVCE > card (you never did end up providing the logs which would have made > that apparent), could you try replacing nvc3_mc_oclass with > nvc0_mc_oclass for the 0xce case in > drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without > the MSI disabling.) The switch has already been made for NVC8 in > 0bae1d61c75 -- perhaps there are more "odd" ones. > > -ilia > Fails exactly the same. case 0xc3:...

...chance you might mmiotrace the blob (version 325 or later) to see >> which registers it fiddles with? Or alternatively, if you have a NVCE >> card (you never did end up providing the logs which would have made >> that apparent), could you try replacing nvc3_mc_oclass with >> nvc0_mc_oclass for the 0xce case in >> drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without >> the MSI disabling.) The switch has already been made for NVC8 in >> 0bae1d61c75 -- perhaps there are more "odd" ones. >> >> -ilia >> > Fails exactly th...

...lob (version 325 or later) to see >>>> which registers it fiddles with? Or alternatively, if you have a NVCE >>>> card (you never did end up providing the logs which would have made >>>> that apparent), could you try replacing nvc3_mc_oclass with >>>> nvc0_mc_oclass for the 0xce case in >>>> drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without >>>> the MSI disabling.) The switch has already been made for NVC8 in >>>> 0bae1d61c75 -- perhaps there are more "odd" ones. >>>> >>>>...

On 31/12/13 10:36, Ilia Mirkin wrote: > On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce <sboyce at blueyonder.co.uk> wrote: >> System x86_64 with openSUSE 13.1. >> X.Org version: 1.14.99.905 >> >> openSUSE 12.2 kernels boot successfully into a graphical screen, login to >> KDE4, etc. all normal. >> >> 3.13-rc kernels boot fully with X running but no

...35ad253fe8 introduced > it. Any chance you might mmiotrace the blob (version 325 or later) to see which registers it fiddles with? Or alternatively, if you have a NVCE card (you never did end up providing the logs which would have made that apparent), could you try replacing nvc3_mc_oclass with nvc0_mc_oclass for the 0xce case in drivers/gpu/drm/nouveau/core/engine/device/nvc0.c? (and boot without the MSI disabling.) The switch has already been made for NVC8 in 0bae1d61c75 -- perhaps there are more "odd" ones. -ilia

On Tue, Dec 31, 2013 at 5:14 AM, Sid Boyce <sboyce at blueyonder.co.uk> wrote: > System x86_64 with openSUSE 13.1. > X.Org version: 1.14.99.905 > > openSUSE 12.2 kernels boot successfully into a graphical screen, login to > KDE4, etc. all normal. > > 3.13-rc kernels boot fully with X running but no graphical screen and it > freezes in VC with not all the startup