Page: 1, 2  Next

Unable to Remove Nouveau Module
Mr_Bean
Status: New User - Welcome
Joined: 11 Mar 2014
Posts: 4
Reply Quote
Hello,

I'm trying to install the latest NVIDIA drivers on Linux Mint Debian Edition using sgfxi. When the script was running, it said something like:

"Unable to remove the Nouveau module. Please investigate this as your NVIDIA driver may not work"

After the script completed, I rebooted and it just shows a black screen.
Any help will be greatly appreciated. I need to get it working urgently because I need access to OpenGL 4.2 for my graphics course.

Thanks.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
You're not giving any detalis. Post the sgfxi log: /var/logs/sgfxi/sgfxi.log

Also, on some distros that do something unknown, you have to run sgfxi twice, no idea why, never seen that issue on true debian.

The process is supposed to be this:

run sgfxi, it detects nouveau, tells you it is going to blacklist it and that you need to reboot, you reboot, run sgfxi again to actually install the nvidia driver.

If you ignore the reboot and then try to just install nvidia driver without the reboot, then of course it won't work. nouveau and radeon use kvm, which means the kernel runs the stuff, and you have to boot the kernel with the blacklisting installed, sgfxi installs it. So naturally if you reboot and don't follow the directions to then install nvidia, you will get a black screen, since nothing is driving your desktop. Well, actually, I think vesa is, not sure. But if you don't reboot, it won't work to install nvidia.

nouveau and radeon are messy and very inelegant and really broke a core linux kernel feature of never having to reboot for module unload/reload, but that's life.
Back to top
Mr_Bean
Status: New User - Welcome
Joined: 11 Mar 2014
Posts: 4
Reply Quote
Here is the log (not sure if spoiler tags exist):

:: Code ::

=========================================================
START sgfxi LOGGING:
=========================================================
Script started: 2014-03-09-19:43:58
Video Card Information: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
 NVIDIA Corporation GF108M [GeForce GT 520M] (rev a1)
Video Card Type: 10de
Video Card Number: 0df7
Xorg Version: 1.14
Installing driver to kernel: 3.11-2-486
sgfxi script version: 4.23.02
sgfxi start options:
SYSTEM_BASE: debian
SYSTEM_CODENAME: testing
DISTRIB_CODENAME: debian
DISTRIB_ID: linuxmint
DISTRIB_RELEASE: 1
SIS: linuxmint-debian-32
BITS: 32
FG_DISTRIB_CODENAME: sid
FG_DISTRIB_ID: Debian
APT_TYPE: apt-get
LOGIN_PID: 2969
SUDO_START: sudo su -
B_SYSTEMD: true
B_SYSTEMD_GRAPHICAL: false
B_SYSTEMD_SYSINIT: false
B_UPSTART: false
=========================================================
X is Running: true
Current Runlevel: 2
Connection is live (0=true): 0
=========================================================
INSTALL_TO_KERNEL:
KERNEL_FULL: 3.11-2-486
KERNEL_BASE: 3
KERNEL_NUMBER: 3.11
KERNEL_MATH: 11
B_IS_XEN: false
Function: create_x_conf - Primary: Start
  xorg is present with xorg.conf file
Function: create_x_conf - Primary: End
Function: check_package_manager_updated - Utility: Start
  sizeWorking: 20
Function: check_package_manager_updated - Utility: End
Function: check_supported_driver - Utility: Start
Function: check_supported_driver - Utility: End
Function: set_cpu_data - Utility: Start
  BITS: 32 - arch:
Function: set_cpu_data - Utility: End
Function: set_driver_install_version - Primary: Start
Function: check_supported_driver - Utility: Start
  Args: last-check
Function: check_supported_driver - Utility: End
Function: print_information_continue - Utility: Start
  Args: standard The graphics installer will be installing the nvidia driver: 331.49
Function: check_ia32_libs - Utility: Start
  Args: test
Function: check_ia32_libs - Utility: End
Function: print_information_continue - Utility: End
  Installing this driver: 331.49
Function: set_driver_install_version - Primary: End
Function: driver_support_tests - Utility: Start
  Args: supported-driver
Function: driver_version_hacks - Utility: Start
  Args: 331.49
  testData:
Forcing nvidia installer option:
Function: driver_version_hacks - Utility: End
Function: driver_support_tests - Utility: End
Function: check_kernel_headers - Utility: Start
Function: check_package_status - Utility: Start
  Args: linux-headers-3.11-2-486 i
  Package Version: 3.11.8-1
Function: check_package_status - Utility: End
Function: check_package_status - Utility: Start
  Args: linux-headers-3.11-2-486 c
  Package Version: 3.11.8-1
Function: check_package_status - Utility: End
  headerPresent: arch
include
Makefile
Module.symvers
scripts
headerName: linux-headers-3.11-2-486
headerInstalled: 3.11.8-1
headerAvailable: 3.11.8-1
headerFile:
Function: check_kernel_headers - Utility: End
  nvidiaPackages:

  fglrxPackages:

Function: check_run_package_tools - Primary: Start
Function: check_run_package_tools - Primary: End
Function: set_download_info - Primary: Start
  download url: ftp://download.nvidia.com/XFree86/Linux-x86/331.49/ - driver file: NVIDIA-Linux-x86-331.49
Function: set_download_info - Primary: End
Function: test_module_build_ok - Primary: Start
  Args: return
  returnValue: 1
Error Data: No Driver Run Package:
Function: download_extract_driver - Primary: Start
  Args: ftp://download.nvidia.com/XFree86/Linux-x86/331.49/ NVIDIA-Linux-x86-331.49
Function: pre_extract_clean_set_up - Utility: Start
  Args: NVIDIA-Linux-x86-331.49
Function: pre_extract_clean_set_up - Utility: End
Creating directory NVIDIA-Linux-x86-331.49
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86 331.49.......................................................................................................................................................................................................
Function: download_extract_driver - Primary: End
  Function: set_install_directory - set to: /usr/src/sgfxi-downloads/NVIDIA-Linux-x86-331.49
Function: run_driver_patches - Primary: Start
Function: run_driver_patches - Primary: End
Function: x_start_stop_master - Primary: Start
  Args: stop
Function: start_stop_x - Utility: Start
  Args: stop
Function: get_default_display_manager - Utility: Start
  defaultDM: mdm
Function: get_default_display_manager - Utility: End
  default runlevel: 2
current runlevel: 2
  dmanCommand: systemctl stop mdm.service
Failed to get D-Bus connection: No connection to service manager.
  Display manager stop status:
Function: x_is_running - Utility: Start
  X ps aux: root      4678 20.5  1.5 118020 38420 tty9     Ss+  19:43   1:15 /usr/bin/X :0 -audit 0 -auth /var/lib/mdm/:0.Xauth -nolisten tcp vt9
  returnVal: true
Function: x_is_running - Utility: End
  Final X kill reports worked: true
Function: x_is_running - Utility: Start
  X ps aux: root      4678 20.5  0.5  84732 14136 tty9     Ds+  19:43   1:15 /usr/bin/X :0 -audit 0 -auth /var/lib/mdm/:0.Xauth -nolisten tcp vt9
  returnVal: true
Function: x_is_running - Utility: End
  The final X kill has failed.
Function: start_stop_x - Utility: End
Function: x_start_stop_master - Primary: End
Function: check_driver_install_tools - Primary: Start
Function: check_package_status - Utility: Start
  Args: module-assistant i
  Package Version:
Function: check_package_status - Utility: End
Function: check_package_status - Utility: Start
  Args: module-assistant c
  Package Version: 0.11.6
Function: check_package_status - Utility: End
Function: install_package - Utility: Start
  Args: module-assistant
Function: update_package_manager - Utility: Start
  Args: update
  Update apt-get successful
Function: update_package_manager - Utility: End
  Install command for apt-get: install - Extra args:
Function: install_package - Utility: End
Function: check_package_status - Utility: Start
  Args: build-essential i
  Package Version: 11.6
Function: check_package_status - Utility: End
Function: check_driver_install_tools - Primary: End
Function: prep_install - Primary: Start
Function: prep_install - Primary: End
Function: preinstall_cleanup - Primary: Start
  Pre Remove: nvidia.ko files:

Function: list_installed_packages - Utility: Start
  Args: nvidia (libkwinnvidiahack|libgl1-nvidia-glx-ia32|libgl1-nvidia-glx:386|modalias|libvdpau|nvidia-bl-dkms|nvidia-cg-toolkit)
  packageList:
Function: list_installed_packages - Utility: End
  Post Purge/Remove: nvidia.ko files:

Function: remove_module - Primary: Start
  Args: nvidia
  operation outcome: unset
Function: remove_module - Primary: End
Function: remove_module - Primary: Start
  Args: nouveau
FATAL: Module nouveau is in use.
  operation outcome: failed
Function: set_modesetting_off - Primary: End
Function: add_grub_nomodeset_blacklist_item - Utility: Start
  Args: nouveau
Function: get_active_grub_files - Utility: Start
  grub files:  /boot/grub/grub.cfg /etc/default/grub
Function: get_active_grub_files - Utility: End
  /boot/grub/grub.cfg file updated to add nouveau nomodeset: /boot/grub/grub.cfg /etc/default/grub
  File /etc/default/grub updated to add nouveau nomodeset: /etc/default/grub
  File /etc/default/grub updated to add nouveau nouveau.modeset=0: /etc/default/grub
Function: add_grub_nomodeset_blacklist_item - Utility: End
Function: add_modprobe_d_blacklist_item - Utility: Start
  Args: nouveau
  file updated to add nouveau blacklist: /etc/modprobe.d/kms-sg-blacklist.conf
Function: add_modprobe_d_blacklist_item - Utility: End
Function: update_initramfs - Primary: Start
  Args: remove-nouveau
Function: update_initramfs - Primary: End
Function: update_xorgconf_driver_version - Utility: Start
Function: update_xorgconf_driver_version - Utility: End
Function: reboot_now_question - Primary: Start
  Args: nouveau modeset-off
Function: handle_shutdowns - Utility: Start
  Args: halt
  command: systemctl poweroff 2>>/var/log/sgfxi/sgfxi.log || halt
Function: handle_shutdowns - Utility: End
Failed to get D-Bus connection: No connection to service manager.

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
It looks to me like lmde is using a mutant, incomplete version of systemd, or only part of it, or something.

Show me the results of these commands:

systemctl stop mdm.service

systemctl poweroff

I see that a totally non expected scenario is present in lmde, ie, systemd itself is present, but it is NOT used as the init system, and it is NOT running the desktop, so why is it even present in lmde at all? Inquring minds want to know. I will update sgfxi to handle this unexpected situation. There will also be a new inxi out soon that has init system data in it.

The error messages from systemd I am not clear on the meaning of, I know the real systemd stuff I've tested sgfxi on work.

It's possible that something is wrong with either mdm or systemd configuration, for example, you'll note that graphical.target is not present even though the system reports that systemd is the init system.

In other to resolve this, I will need someone technically savy from lmde to figure out why lmde, and only lmde, is failing to do systemd commands, and why it is reporting that systemd is the init system when it may not be.

In other words, I need to know if:

a: the system is started by systemd

You can verify this by doing: /proc/1/comm

that will return one of two values: systemd OR init

if it is systemd, then the reboot command should not have returned errors. If it is init, then the systemd is mutant, since the sgfxi test I believe checks to see what target exists in terms of init start.

If the command: systemctl stop mdm.service
fails, then there is something wrong.

If the command: service stop mdm
works, then systemd isn't running the system, it's a mutant system that is.

The sgfxi/smxi systemd support is new and being worked on and updated, but it looks like it failed on lmde, which isn't surprising to me to be honest.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
I am very glad I added full logging to these features or I would never have been able to figure this one out.

Clem really should have done some real testing on this stuff before recommending sgfxi, and he should have engaged in some communication, had he done so, we would have learned right away that his systemd is mutant, incomplete, and that would trigger issues in sgfxi. systemd support is development, with new fixes being released all the time, when they are called for. Luckily I thought to log all possible systemd conditions in the system, not just the basics.

Anyway, sgfxi is updated to more precisely handle this mutant case, I'm assuming that lmde is using sysvinit at least that is what the logs and errors suggest, so try it again and it may work, we'll see. Why he has systemctl present but nothing else really is beyond me, that's not very smart in my opinion.

If not, I wont' spend more time on it until someone from lmde explains what they have done, and ideally, why, so I don't have to reverse engineer it.
Back to top
Mr_Bean
Status: New User - Welcome
Joined: 11 Mar 2014
Posts: 4
Reply Quote
Wow, thanks for your effort.
I will try again tomorrow and let you know.
Do you still want the output of those commands?
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
sure, just to confirm what the logs suggested.

what happened is that sgfxi/smxi were testing for systemctl, then a subset of things to see if systemd was pid 1, the init to start the system, and if graphical mode existed.

However, I did not use those test results elsewhere, luckily I added them to the logging, which is how I found that what lmde has done is have systemctl present, for some inexplicable reason, but without it actually running the init system, or anything else that I can detect related to what smxi/sgfxi do. Which makes you ask, why is it there in the first place?

However, now smxi/sgfxi explicitly use the pid 1 test result for all shutdown/reboot actions, and also require that for checking shutting off/on daemons like mdm. However, if lmde does NOT use:

service mdm stop/start type commands, then I can't help you until you tell me exactly what has been done in lmde. Whatever it is, it's not standard.
Back to top
Mr_Bean
Status: New User - Welcome
Joined: 11 Mar 2014
Posts: 4
Reply Quote
Sadly, the new version didn't work :(

The result for both commands is:

"failed to get D-bus connection: no connection to service manager"

Should I try Ubuntu instead perhaps?
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3986
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
I cannot say much more, I fixed the things that could conceivably have caused issues. Please post the new /var/log/sgfxi/sgfxi.log

so I can see if everything worked as expected. Remember: "It didn't work" gives me no usable information at all. Ie, what didn't work?

Also post: inxi -bxx

output so I can see the system.

LMDE Is hard to predict because they pull in some random ubuntu packages and tools, that have no place in debian proper. Ubuntu has other issues, some of which have been resolved.

The second set of commands will only show results if they exist:

boot, if you get black screen, use: ctrl alt F1, login to terminal/console, then do this command:
:: Code ::
service mdm stop

and see what the output there is. I can't say what lmde did on this new release in terms of the init system because it doesn't make any sense to me yet, but I'm now assuming they have systemctl installed for some unknowable reason, but that it is not actually hooked into the init or rc system. Why? who the heck knows.

An lmde person will have to provide me with usable data about the failure, a failure I have by the way seen before on ubunty, which makes me think this error is carried over from mint/ubuntu parts.

There's so many tests that need to be run to determine what has happened, and it's all because of irregular setup of lmde, that I won't and can't spend my time figuring out out for them. So if nobody from lmde can tell you why things that almost always work in debian are not working, it's going to be pretty hard for me to do it, unless I install a test lmde 201403, which I won't do, since sgfxi/smxi already support debian, so any failures probably are lmde specific.

For example, is there some irregular handling of nouveau kernel mode setting? I have suspected this in ubuntu for a long time. Did sgfxi correctly detect that nouveau was running, did it apply the proper blacklisting? is lmde respecting that blacklisting? is reboot booting to a console without kms (kernel mode setting), as its supposed to after nouveau is is blacklisted? Is there some totally unrelated issue?

if you start sgfxi, the logging will show me a great deal of this information, though there's a limit to what I can get logged in practical terms.
Back to top
sedonix
Status: Contributor
Joined: 09 Sep 2008
Posts: 56
Location: Sedona, AZ
Reply Quote
Mr Bean - One of my favorites!

In case you are new to Linux.

There are gazillions of people on Aptosid, Siduction or in my case straight Debian sid that use the Nvidia drivers via sgfxi successfully. :-)

You will note I did not include Mint nor Ubuntu. :-(
Back to top
Display posts from previous:   
Page: 1, 2  Next
All times are GMT - 8 Hours