Created attachment 30030 [details] My kernel config file I am using a custom (Zen - http://zen-sources.org, #zen-sources in freenode) kernel, however I know that I have merged all of the nouveau DRM stuff from the freedesktop git as a head into my kernel. That said, I have had these same errors with the same addresses since version .30 and Zen is now on revision .31-zen2, which means that this has gone on for 3 if not more kernel revisions (even by mainline vanilla standards). Any chance of fixing this? Previously, nouveau worked like a dream! I'm using an NV40 (Geforce Go 6150) on an HP DV9205US laptop, with the Archlinux distro. I'm sure I have everything setup correctly in .config, it's the same as it always has been. The exact errors go as follows: C51 misaligned reg 0x00001305 not verified C51 misaligned reg 0x00001401 not verified C51 misaligned reg 0x00001405 not verified C51 misaligned reg 0x00001409 not verified C51 misaligned reg 0x0000140D not verified Followed by nouveau detecting display outputs before crapping out and stopping the boot process. I can't boot kernels unless I don't build nouveau...and I'm using the nv driver now. And...out of curiosity, is there any chance of separating nouveau to only build the driver for the card that a person needs? Rather than building for all nv40, 50, 60, etc, have the user choose those he/she needs? I'd prefer that, it would strip out unnecessary code and speed the build, shrink the kernel, and also avoid needless bugs.
The unverified registers you're seeing have nothing to do with your display issues. There's other known issues on C51 chipsets that have yet to be resolved however. If you could attach your /var/log/messages from after a failed boot with KMS enabled, or if you can ssh into the machine or something during a failed boot, the output of the "dmesg" command. And yes, there is a possibility of doing that, there's no good reason whatsoever to do so however. You'll gain nothing in terms of stability or runtime speed, all the per-chipset code is separated out and largely independent of each other with the exception that the code for the "new" chipsets utilise the functions for "old" chipsets where the hardware didn't change.
That said, could you tell me where I can find information on this issue with the C51? As for the whole building each driver separately, I was just talking splitting up only the things that were specific, not the header files or the nouveau components that are used by all. I'm just talking splitting it up so that I don't have to build the specific files for each GPU, rather only build for my NV40. I already did it myself. It's just to reduce kernel size a teeny tiny tiny bit, that code I do not need.
I have seen where you've patched and added the errors about the misaligned regs back in July. I guess I can't really use nouveau until they're ironed out, correct? I can't boot with nouveau enabled. I remove it from the kernel and it boots fine. Sad thing is, it worked back on 2.6.29...though the console size wasn't correct...
(In reply to comment #2) > That said, could you tell me where I can find information on this issue with > the C51? > > As for the whole building each driver separately, I was just talking splitting > up only the things that were specific, not the header files or the nouveau > components that are used by all. I'm just talking splitting it up so that I > don't have to build the specific files for each GPU, rather only build for my > NV40. I already did it myself. It's just to reduce kernel size a teeny tiny > tiny bit, that code I do not need. > And yes, of course you're right. It's late and I'm not thinking clearly.
Ben asked for logs, but no appropriate reaction from reporter for over one year. I'm closing this as invalid. If the problem still persists with recent nouveau code, please reopen and attach needed logs.
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.