reassign 301255 xserver-xfree86 quit sorry i should have seperated your problem from the rest of the bug report before closing. Thanks to have reopened another one so the problem can be fixed.
i may need more information: do you have /dev/nvidiactl file ? dmesg output (if you can cut only the part regarding nvidia) and some xfree86 logs : [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more informtion is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1 $ mailx -s "Re: Bug#301255" [EMAIL PROTECTED] < /tmp/output If you do not have a "mailx" command on your system, you can get by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you'r receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <[EMAIL PROTECTED]>. Thank you! Alban Browaeys For future reference i paste your previous mail here (was in unrelated http://bugs.debian.org/289749 bug report) : Package: xfree86-common Version: 4.3.0.dfsg.1-12 Followup-For: Bug #289749 I am having problems loading the nvidia module. I modprobed for it and it loads just fine. However insmod can't find the module and the log file also states the nvidia module can not be found. I hope this helps. some log below.. (II) Setting vga for screen 0. (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 (==) NVIDIA(0): RGB weight 888 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) (--) NVIDIA(0): Linear framebuffer at 0xD8000000 (--) NVIDIA(0): MMIO registers at 0xE8000000 (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (EE) Screen(s) found, but none have a usable configuration. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xfree86-common depends on: ii debconf 1.4.46 Debian configuration management sy ii debianutils 2.13.1 Miscellaneous utilities specific t -- debconf information: xfree86-common/experimental_packages:Package: xfree86-common Version: 4.3.0.dfsg.1-12 Followup-For: Bug #289749 I am having problems loading the nvidia module. I modprobed for it and it loads just fine. However insmod can't find the module and the log file also states the nvidia module can not be found. I hope this helps. some log below.. (II) Setting vga for screen 0. (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 (==) NVIDIA(0): RGB weight 888 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) (--) NVIDIA(0): Linear framebuffer at 0xD8000000 (--) NVIDIA(0): MMIO registers at 0xE8000000 (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! (EE) NVIDIA(0): *** Aborting *** (II) UnloadModule: "nvidia" (EE) Screen(s) found, but none have a usable configuration. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xfree86-common depends on: ii debconf 1.4.46 Debian configuration management sy ii debianutils 2.13.1 Miscellaneous utilities specific t -- debconf information: xfree86-common/experimental_packages: And my answer: hi this bug should have been reported about nvidia packages ... anyway you mix "X failed to initialized nvidia kernel module" (X needs the kernel module to be loaded and it is not) and 'cannot find the module' from insmod (insmod require the full path to the module , you cannot "insmod nvidia" , this is what modprobe is for . And you just told it worked with modprobe). PS/ you should not need insmod, it not only need the full path to the module but also is unable to manage dependencies in case the module you want to load need another one. This is an advanced tool when modprobe is for common use. I just did not understood if you had the error in X (cannot initialise nvidia kernel module ) even when loading "nvidia" with modprobe before starting X. If you look in nvidia-kernel-source and nvidia-glx bugs you ll find that the nvidia module not being loaded automatigically is a known issue. The common fix is to add it to /etc/modules (or load it with modconf which will add it in /etc/modules) Cheers Alban PS: this issue have nothing to do with the submitter bug report which was about a ati card driver using the free dri 3d driver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
