I've been using Linux Mint 17.3 Cinnamon x64 on a Surface Pro 2 for a while now, but it decided to give up the ghost a little while ago. I commissioned an Optimus VII Pro from PCSpecialist to replace it, intending to mimic the dual-boot Windows/Linux setup I had (albeit a little more complex with multiple internal storage devices).
All works OK, grub is able to boot both OSes without exploding, all seems well until I attempt to install the driver for my GPU. Problem is, I tried to follow the guide in the sticky at the top of the forum. Rebooting after reaching the stage where the nouveau driver is disabled causes Cinnamon to hang after login - I have a cursor on a black background, and that is all. Only way to fix it seems to be to wipe / and reinstall. I went back to the post and read that the guide does not work for laptops (for example) that have hybrid GPUs - that is, a discrete NVIDIA chip and one of those horrible Intel HD things in the processor.
Which I believe mine does. So I'm left with a little bit of a conundrum - the information I've found is either out-of-date or not for the correct edition of Mint.
Works for me for Ubuntu 16.04 – JDiMatteo Oct 18 '17 at 17:15 1 apt-get install cheese was sufficient on my ancient HP notebook running 16.04, after that all applications could find the webcam. Je viens d'installer une version d'Ubuntu (cf. Titre pour la version) sur. (II) Using input driver 'evdev' for 'BisonCam, NB Pro: BisonCam, NB.
As a side - if I update to the 4.4 kernel (after a fresh install) the wifi adapter suddenly starts working but I end up with black artefacts on the screen every so often. Right, I think I might have a little more information. After yet another reinstall I have updated the kernel to 4.4.5 (to get the wifi working) and installed all updates from mintupdate.
Tlhe next thing I did was install nvidia-352 and nvidia-settings from the graphics-drivers ppa (as, for some reason, the Driver Manager showed up blank). At this point, after rebooting I noticed the screen was still giving me small black flickers whenever a window was changed in Cinnamon. After this, I installed bumblebee, after spending a good couple of hours tearing my hair out over this, reading that this would be able to manage the two GPUs and their power consumption. Mainly because my BIOS does not give me the option to disable the intel GPU. In /etc/bumblebee/bumblebee.conf I modified the following.
For my 750 Ti, I had to use a relatively older driver version. If your graphics are screwed after installing a driver, try using a full-screen CLI environment by hitting CTRL ALT F1.
Once in that, log in and install the required drivers. It would be best if you could get these drivers via another system then transfer them via USB or other method, but if not I can download versions and then put them into an area where you could easily WGET them. NVidia drivers need the GUI to be terminated. Do this by entering the CLI environment and using the command 'sudo service lightdm stop'.
Then run the drivers'.run file (if it's not executable, use 'sudo chmod +x filename.run' on it. Execute with './filename.run' if you're in the same folder. After the drivers are installed, you should not need to reboot (I never have needed to). Just start the GUI (sudo service lightdm start). You will be automatically switched to it. If all is good, you should see the login screen as normal. If not, download another driver version and run the steps again.
As far as I've known, the driver install will find any other install and ask if you wish to nuke it. Answer yes to this. Code: Using built-in specs. Telvee32 wrote:Final one - drm folder does not exist The /drm folder was not created because no Nvidia kernel module was built during the attempted installation of the Nvidia driver. You have very new hardware so it may not be supported well in Linux at this time.
With the 4.4.5 kernel installed, you can't install a Nvidia driver in Driver Manager, and the drivers downloaded from Nvidia's website should not be installed on Optimus systems (hybrid graphics). Using the command gcc -v gives gcc version 4.8.4, which is the installed version of gcc on your system, and which will be used to build the Nvidia kernel module during the Nvidia driver installation. Using cat /proc/version gives gcc version 5.2.1, which is the version of gcc used to build the 4.4.5 kernel. The versions of gcc (GNU C Compiler) are too different and incompatible.
You have 2 choices before installing a Nvidia driver: 1. Use the kernels in Update Manager View Linux kernels. These kernels will have been built with gcc version 4.8, so the Nvidia driver will install without problems. Install a newer version of gcc first, and then try installing the Nvidia driver in Driver Manager. Nvidia recommends using the same version of the compiler as used to build the running kernel, which is gcc version 5.2.1. Check the info in this post and the ones after it: If that link doesn't work, then check user Michel's post on page 9 of this topic. OK, I did another fresh install, installed all updates and then updated the kernel to 4.2.0-30, which is the latest shown in mintupdate, After that I rebooted and it would again hang on a black screen after login so I rebooted again, switched to tty1 and added nomodeset to /etc/default/grub, then sudo update-grub, rebooted again.
Which disabled video acceleration but it would at least give me a desktop. I then added the graphics-drivers ppa and installed the 361 driver via driver manager, then removed the edit from /etc/default/grub and updated grub, then rebooted.
Upon login Cinnamon immediately crashes (with an error stating that it has crashed). Naturally, restarting Cinnamon causes it to immediately crash again. Elina wrote:You can also download driver by this method.Such as OSpeedy Driver Updater elina, this is not a Windows forum. Telvee32, How are you installing the 4.2 kernel in the Update Manager. From reading your first post, there was no support for your Wi-Fi hardware after installing Mint 17.3. I assumed you downloaded the packages for the 4.4.5 kernel from your Windows installation, and that kernel did support your Wi-Fi. I assumed you would keep that installation and then try installing the 4.2 kernel.
On an Optimus system, you need to install nvidia-prime or Bumblebee before the Nvidia driver can be used. From other topics I've read, some readers report nvidia-prime is automatically installed at the same time the Nvidia driver is installed, but others say they had to install nvidia-prime separately.
Use this command to check that. Code: prime-supported (or 'sudo prime-supported' if that doesn't work) If nvidia-prime is installed, the output is Yes. You will have to decide if you want to use nvidia-prime or Bumblebee, but both should not be installed at the same time. From other recent topics I've read, it appears more users are using nvidia-prime and Bumblebee is giving more installation problems. If the 4.2 kernel does not support your Wi-Fi, then you will need to go back to the 4.4.5 kernel or try the 4.5 kernel. After a fresh installation, if the screen display looks fine and you don't need the extra processing power of the Nvidia GPU, then you can continue just using the intel GPU. If you need the Nvidia GPU, then you will have to update gcc using one of the methods discussed in the links from my previous post, and then install the Nvidia driver from the graphics-drivers PPA.
You can also wait until Mint 18 is released in May or June, which should have the 4.4 kernel. Just as a clarification, Mint 17.3 of course comes with the 3.19 kernel, which does not work with the wifi hardware. 4.4.5 was downloaded externally, the current installation is a fresh one with the 4.2 kernel which was installed via Update Manager (from View - Linux kernels). I just did a fresh install to minimise any issues, I haven't actually been able to do anything with Linux since getting this machine.
The NVIDIA driver version 361 has been installed via Driver Manager after adding the graphics-drivers PPA, but as I said it causes Cinnamon to get stuck in a crashing loop (in fallback mode). I am hence entering the following commands in tty1 as the GUI is not co-operating. I hope it won't actually affect the output. Sudo prime-supported outputs nothing, however running it without root privileges outputs.
Code: rm: cannot remove '/var/log/prime-supported.log': Permission denied /usr/bin/prime-supported: 38: /usr/bin/prime-supported: cannot create /var/log/prime-supported.log: Permission denied sudo apt-get install nvidia-prime reports that nvidia-prime is installed and up-to-date. Bumblebee has not been installed since I did a fresh install. The reason I am so anxious to get the nvidia driver working, aside from performance, is that the nouveau driver causes Cinnamon to hang after login when using the updated kernel, unless I add nomodeset to /etc/default/grub. At that point though I am not sure which GPU is actually being used. However the updated kernel is required for the wifi hardware. So I'm a bit stuck. EDIT: lspci -vnn grep VGA -A 12 outputs this (I have taken a photo as although I could direct the output to a text file I cannot access it from Windows as the Windows partition is not mounted until I login).
It would suggest that the nvidia driver is being used by the kernel as opposed to the intel one from a few posts ago. Roblm wrote:I still don't see how you installed the 4.2 kernel through Update Manager on a new installation without the Wi-Fi working, unless you downloaded the packages from your Windows installation, from the same source you got the 4.4.5 kernel. With an ethernet cable that I obtained.
Yeah, I had to go out and buy one as I realised that trying to fix this without a permanent internet connection was going to be difficult. Cat /var/log/gpu-manager.log again using tty1. That one is curious, has intel?
Xorg log - I used my Live Mint USB to copy this file to my Windows partition as it's rather long. Code: 6.401 (.) FBDEV(0): Depth 24, (-) framebuffer bpp 32 6.401 () FBDEV(0): RGB weight 888 6.401 () FBDEV(0): Default visual is TrueColor 6.401 () FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) 6.401 (II) FBDEV(0): hardware: EFI VGA (video memory: 8128kB) 6.401 (II) FBDEV(0): checking modes against framebuffer device.
6.401 (II) FBDEV(0): checking modes against monitor. 6.401 (-) FBDEV(0): Virtual size is 1920x1080 (pitch 1920) I assumed the intel driver would be enabled first after installing the Nvidia driver, and you would have to switch to the Nvidia driver in the Nvidia Settings utility PRIME Profiles, or perhaps you did that? Would you post the output of these commands. Code: 5.376756 nvidia: module license 'NVIDIA' taints kernel.
5.398925 nvidia: module verification failed: signature and/or required key missing - tainting kernel 5.403432 nvidia 0000:01:00.0: enabling device (0006 - 0007) 5.403567 nvidia-nvlink: Nvlink Core is being initialized, major device number 245 5.403663 drm Initialized nvidia-drm 0.0.0 20150116 for 0000:01:00.0 on minor 0 5.483033 nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 361.28 Wed Feb 3 15:15:17 PST 2016 5.495530 nvidia-uvm: Loaded the UVM driver in lite mode, major device number 244 dpkg -l grep nvidia-prime. There should also be a Places menu next to the Applications menu in the upper left corner when the desktop is in Fallback Mode. Usually when you see an empty Nvidia Settings utility, then there was a problem with the Nvidia driver installation.
The most obvious problem is that the xorg.conf file you posted is incorrect for an Optimus system with nvidia-prime installed. When the intel driver is enabled, there should be no xorg.conf file and when the Nvidia driver is enabled, the file should look like this below.
Copy the lines. Code: Section 'ServerLayout' Identifier 'layout' Screen 0 'nvidia' Inactive 'intel' EndSection Section 'Device' Identifier 'nvidia' Driver 'nvidia' BusID 'PCI:1:0:0' EndSection Section 'Screen' Identifier 'nvidia' Device 'nvidia' Option 'AllowEmptyInitialConfiguration' EndSection Section 'Device' Identifier 'intel' Driver 'modesetting' EndSection Section 'Screen' Identifier 'intel' Device 'intel' EndSection Right click on the desktop and select Open in Terminal. Open the xorg.conf file for editing using this command. Code: gksudo gedit /etc/X11/xorg.conf If there is no right click option, then open the File Manager by clicking the Places menu. On the left side, click File System and the etc folder.
Right click on the X11 folder when it is displayed in the window on the right and select Open as Root, and then open the xorg.conf file. Remove all the lines and then paste the lines you just copied from the xorg.conf file above. Save the file and Logout and back in.
If there is a startup problem and you can't get to the desktop, then reboot and select Recovery Mode at the GRUB boot menu. If no menu shows, then hold down the Shift key while starting, or keep tapping the key. In the menu, select “ root - drop to root shell prompt”. When asked for the root password, just type your user password.
Then change the file permissions to read and write by typing.
Download the latest BisonCam NB Pro driver for your computer's operating system. All downloads available on this website have been scanned by the latest anti-virus software and are guaranteed to be virus and malware-free. Browse the list below to find the driver that meets your needs. To see more matches, use our custom search engine to.
Tech Tip: If you are having trouble deciding which is the right driver, try the. It is a software utility that will find the right driver for you - automatically. DriverGuide maintains an extensive archive of Windows drivers available for free download. We employ a team from around the world. They add hundreds of new drivers to our site every day. Having trouble finding the right driver? Try the, or you can and we will find it for you.
Overall Rating: (3 ratings, 3 reviews) 93 Downloads Submitted Jul 17, 2008 by RajeshP (DG Staff Member): ' COBALT(S96Hm) - BISONCAMERA Driver File' Device Type: Digital Camera Supported OS: Win 7 File Size: 1.0 MB File Name: 86 Downloads Submitted Sep 30, 2011 by Karthika (DG Staff Member): ' Camera Driver File' Source: Manufacturer Website (Official Download) Device Type: Digital Camera (Utility) Supported OS: Win XP Home, Win XP Pro File Version: Version 2.6.0.42 Release Date: 2005-06-24 File Size: 776.3 KB File Name.