I installed x11-base/nouveau-drm-99999999 on my Gentoo linux (which should be git HEAD) to get a more recent kernel module for my 3.0.0 kernel. The kernel starts fine showing the kernel log messages on the DVI connector. But (I guess) after loading the nouveau kernel module the screen gets blank and I have to use the VGA connector, which works fine nevertheless. Also X11 starts fine using the nouveau driver. Before I used nv driver which supported the DVI output, both VT and X11. I'll attach the dmesg.
Created attachment 50264 [details] dmesg output
Created attachment 50473 [details] VBIOS dump As suggested on IRC I added the VBIOS read from /sys/kernel/debug/dri/0/vbios.rom
Created attachment 50978 [details] [review] quirk Does it work with this patch? If it works please attach output of lspci -vvn and test VGA output.
(In reply to comment #3) > Created an attachment (id=50978) [details] > quirk > > Does it work with this patch? > > If it works please attach output of lspci -vvn and test VGA output. No, this doesn't work. DVI is used when in BIOS and GRUB. It is also used when starting the kernel in VESA(?) mode and DVI is disabled when the nouveau module is loaded.
Please attach dmesg with this patch applied and drm.debug=6 in kernel command line. Does Nvidia blob work with this card?
Created attachment 51721 [details] dmesg with drm.debug=6 For nvidia blob the video output stays on DVI until X11 gets started, then it switched to D-SUB.
Created attachment 57301 [details] dmesg with drm.debug=6 This is the dmesg from git kernel with commit 2d44ad2a2a70c3f3a8edf8a4680dd3e15cddbde3 where only DVI is connected. I'm wondering if these entries are related to the extension card: [ 8.982259] [drm] nouveau 0000:00:0d.0: DCB type 4 not known [ 8.982264] [drm] nouveau 0000:00:0d.0: Unknown-1 has no encoders, removing To me it seems the DVI connector type is unknown.
Would be nice if you could confirm that you also have a Sil1364 encoder (I'm guessing the chip is somewhere near the DVI connector), but I'm guessing it's the same situation. *** This bug has been marked as a duplicate of bug 26797 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.