Summary: | Geforce 8400M GS (id 0x427) support | ||
---|---|---|---|
Product: | xorg | Reporter: | Hervé Cauwelier <debian> |
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Description
Hervé Cauwelier
2007-10-17 05:33:01 UTC
My mistake, X didn't start at all, and Ubuntu started in fail-safe (VESA) mode. I don't think you're interested in VESA bugs. The kernel module failed to insert because of unresolved symbols. I will drop the Ubuntu packages and compile it myself for a more accurate bug report. Created attachment 12193 [details]
Xorg log of nouveau driver on a GeForce 8400M GS
After git clones of drm and nouveau, compiling and installing, I restarted. I had to manually load the new drm module instead of the default one and... it worked! The native resolution of 1280x800 was enabled by default. My first impression is how the refreshing is slow. Some output from xrandr: Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 1280 VGA1 disconnected DVI1 disconnected LVDS connected 1280x800+0+0 0mm x 0mm 1280x800 0.0*+ 60.0 1280x768 60.0 1024x768 60.0 800x600 60.3 640x480 59.9 640x400 120.0 640x384 120.2 512x384 120.0 I connected a screen on VGA1 but nothing changed. But I expected it to be named VGA. I attach the Xorg log. What do you need now to help improve support? Forgot to update the summary. NV50 support is far from perfect, i'm trying to get switching back to a VT to work. The slowness is to be expected and likely involves text rendering. Come to our irc channel (#nouveau on freenode) if your interested in helping out. Created attachment 12248 [details]
a new X log from git head f75e36a901fd47bbd9164242c408e9f8b0e03e2c
Created attachment 12249 [details]
the same head with the nv50.patch
I tried your nv50.patch. Without it, I switch to the first virtual console and get a black screeN. I switch back to X and get back my desktop. Nothing crashed. With your patch, this is exactly the same behaviour. I tend to think I missed a step, so here is my bash history: cd xf86-video-nouveau/ git-apply nv50.patch make sudo make install I saw nv50_display.c compiling, so the driver must be updated. I consider that patch(nv50.patch) a dead end, it doesn't work. I may give it a try in the future, but not soon, since i lack an nv50. Thanks for warning me :^) Anytime you have a patch to test on G80, attach it to this bug report and assign it to me. Created attachment 12321 [details]
Xorg log of git head 7054de29c589a7be0a6b027f3067ae2c02e2fc45
The screen is black but the system is still responsive.
I updated drm & nouveau, and now the screen is black. I can still use the keyboard though. I attached the X log. Git head 5ca10da0c7dd2fd689cc4369e37ed385a0c10d21 fixed the black screen, which retrospectively was probably the screen switching off to prevent any damage. AIGLX is deactivated in my xorg.conf at the moment. But I still have the default frequency at 0 Hz. See xrandr output: Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 1280 VGA1 disconnected DVI1 disconnected LVDS connected 1280x800+0+0 0mm x 0mm 1280x800 0.0*+ 60.0 1280x768 60.0 1024x768 60.0 800x600 60.3 640x480 59.9 640x400 120.0 640x384 120.2 512x384 120.0 I'm eager to test hotplug. Created attachment 12362 [details]
Xorg log of working git head b36fbf174849b04928efda2909c461b6c1688cdc
Working but default frequency is 0 Hz.
I'm very confused, i see one or two debug statements from the pre-G80 driver in your log, also why that commit fixed your situation is unknown, it's impossible, or it should be. Also hotplugged screens are not detected. I can't tell you the magic behind, but I still can try git-bisect between 7054de29c589a7be0a6b027f3067ae2c02e2fc45 and HEAD. This is a Dell manufactured adapter. I hope this is not some rework of a G70 design! I've fixed the small leak of pre-G80 code into G80, but this did not touch the commit you mentioned. Should this be closed? (ignoring the wider scope/lacking good g80 support) Yes, at least the original reason why I opened this bug is fixed. |
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.