Screen Resolution Issue

Head_on_a_Stick · 2018-01-27 17:14:59

^ OK, looks like I forgot about the nouveau blacklist, sorry! :8

This should get your NVIDIA card working (I think):

sudo aptitude reinstall xserver-xorg{,-video-nouveau}

After a reboot the `lscpi` command we used above should now show the nouveau driver in use. Hopefully.

Thanks for your patience with this, I've never owned an NVIDIA card so this is all new to me.

42578 · 2018-01-27 17:33:12

I don't think that actually work:

lspci -knn | grep -A2 '\''[030[02]\]'
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:191b] (rev 06)
Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
Kernel driver in use: i915
--
01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:139b] (rev a2)
Subsystem: ASUSTeK Computer Inc. Device [1043:1c5d]
02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59)

Head_on_a_Stick · 2018-01-27 17:38:04

Is there a blacklist at all?

grep -R nouveau /etc/modprobe.d

Maybe the drivers aren't supposed to be listed in an Optimus machine, I really have no clue.

Unless any other forum members who actually have some experience of NVIDIA cards can offer any assistance then we may have to give up here.

If you want to use Linux (or BSD) then it's probably best to avoid NVIDIA if at all possible, their support for the open source community is atrocious.

42578 · 2018-01-27 17:53:13

Do you know any distro wich is good with the Nvidia Optimus?

I will install Bunsenlabs in other machine.

Head_on_a_Stick · 2018-01-27 18:08:55

42578 wrote:

Do you know any distro wich is good with the Nvidia Optimus?

Try MX Linux 17 — they have a tool which can auto-configure Optimus systems, apparently.

https://mxlinux.org/version/mx-17

I think we may try to port it to BunsenLabs after my dismal failure in this thread... 8.(

42578 · 2018-01-27 18:19:24

Ok. Don't be sad. If you find the solution post here and them I will return to Bunsenlabs, or if Bunsenlabs port the tool.

Any way, thanks for your help. I have learn much things with your help.

Bye

Head_on_a_Stick · 2018-01-27 21:52:46

42578 wrote:

If you find the solution post here and them I will return to Bunsenlabs, or if Bunsenlabs port the tool

Well, you could try installing the MX Linux .deb file for their NVIDIA (and AMD) installer:

http://mxrepo.com/mx/repo/pool/main/d/d … 01_all.deb

Install it with `gdebi` or

sudo dpkg -i ddm-mx*.deb

If it installs, run it with

sudo /usr/local/bin/ddm-mx -i nvidia

Be warned though that I have no idea if this will work at all.

@stevep: sorry!

42578 · 2018-01-30 19:53:58

Don't work... 8.(

Thanks for all.

If you find the solution tell me. For now I will use MX Linux. 8.(

Head_on_a_Stick · 2018-01-30 19:59:02

42578 wrote:

Don't work...

Did the .deb install?

Were there any errors after you ran the command?

For now I will use MX Linux. 8.(

No need to be sad — MX Linux is an awesome distribution

If you have a fresh install, you could try adding our repositories and use

sudo apt install bunsen-meta-all

to install our entire desktop.

But be warned that it might mess up MX Linux's exquisite XFCE setup.

EDIT: if you want to try this with MX-17 then use our Helium-dev repositories:

sudo tee /etc/apt/sources.list.d/helium-dev.list << !
deb https://kelaino.bunsenlabs.org/~johnraff/debian helium main
!
wget -q https://kelaino.bunsenlabs.org/~johnraff/helium-dev.asc -O - | sudo apt-key add -
sudo apt update

Last edited by Head_on_a_Stick (2018-01-30 20:24:29)

42578 · 2018-01-30 20:30:37

Can you please tell me more about that?

Last edited by 42578 (2018-01-30 20:31:14)

Head_on_a_Stick · 2018-01-30 20:32:49

^ Just run the commands in my EDIT above in your MX-17 system and then try to install the bunsen-meta-all package

It may just break the system though so only try it on a fresh install (or if you don't mind restoring from a backup).

42578 · 2018-01-30 20:38:16

I am installing MX Linux right now. I will try this.

42578 · 2018-01-30 21:10:44

I have already run the commands, and now what I make?

Head_on_a_Stick · 2018-01-30 21:19:59

OK, do we have the package installed?

apt-cache policy bunsen-meta-all

If it is then try rebooting, it may be that BL supersedes the MX settings but I really don't know.

Try selecting "openbox-session" in the login screen to get our desktop.

42578 · 2018-01-30 21:37:23

I have an error when I type sudo apt update. When I restart don t appear anything, just default session and xfce session.

Last edited by 42578 (2018-01-30 21:52:14)

Head_on_a_Stick · 2018-01-30 21:49:51

Please post the output of:

apt-cache policy bunsen-meta-all
update-alternatives --list x-session-manager

42578 · 2018-01-30 21:54:09

apt-cache policy bunsen-meta-all

bunsen-meta-all:
  Installed: 8.0-4
  Candidate: 8.0-4
  Version Table:
 *** 8.0-4 500
        500 http://pkg.bunsenlabs.org/debian bunsen-hydrogen / main amd64 Packages
        500 http://pkg.bunsenlabs.org/debian bunsen-hydrogen / main i386 Packages
        100 / var / lib / dpkg / status

update-alternatives --list x-session-manager

/usr/bin/startxfce4
/usr/bin/xfce4-session

Last edited by Head_on_a_Stick (2018-01-30 21:55:29)

42578 · 2018-01-30 21:56:51

I have this error when I type sudo apt update:

sudo apt update
Hit: 1 http://ftp.pt.debian.org/debian stretch-updates InRelease
Ign: 2 http://nl.mxrepo.com/antix/stretch stretch InRelease
Hit: 3 http://security.debian.org stretch / updates InRelease
Ign: 5 http://ftp.pt.debian.org/debian stretch InRelease
Ign: 6 http://nl.mxrepo.com/mx/repo stretch InRelease
Hit: 7 http://ftp.pt.debian.org/debian stretch Release
Hit: 8 http://nl.mxrepo.com/antix/stretch stretch Release
Hit: 9 http://nl.mxrepo.com/mx/repo stretch Release
Get: 4 http://eu.pkg.bunsenlabs.org/debian bunsen-hydrogen InRelease [5167 B]
Err: 4 http://eu.pkg.bunsenlabs.org/debian bunsen-hydrogen InRelease
The following signatures could not be verified because the public key is not available: NO_PUBKEY A0673F72FE62D9C5
Reading package lists ... Ready
E: The / usr / lib / apt / methods / https method driver could not be found.
N: Is the package apt-transport-https installed?
W: GPG error: http://eu.pkg.bunsenlabs.org/debian bunsen-hydrogen InRelease: The following signatures could not be verified because the public key is not available: NO_PUBKEY A0673F72FE62D9C5
E: The repository 'http://pkg.bunsenlabs.org/debian bunsen-hydrogen InRelease' is not signed.
N: Updating from such a repository can not be done securely, and is therefore disabled by default.
N: See apt-secure (8) manpage for repository creation and user configuration details.

42578 · 2018-01-30 22:00:48

..

Last edited by 42578 (2018-01-30 22:06:30)

Head_on_a_Stick · 2018-01-30 22:03:28

You've used the wrong repositories for MX-17, that is based on Debian stretch so we should be using the helium-dev repositories instead of bunsen-hydrogen.

Please delete the bunsen-hydrogen repositories and `apt update` again.

The EDIT in this post has the right instructions for the heliuim-dev repositories:

https://forums.bunsenlabs.org/viewtopic … 475#p67475

Here they are again:

sudo tee /etc/apt/sources.list.d/helium-dev.list << !
deb https://kelaino.bunsenlabs.org/~johnraff/debian helium main
!
wget -q https://kelaino.bunsenlabs.org/~johnraff/helium-dev.asc -O - | sudo apt-key add -
sudo apt update

Then try the new meta package:

sudo aptitude reinstall bunsen-meta-all

#41 2018-01-27 17:14:59

Re: Screen Resolution Issue

#42 2018-01-27 17:33:12

Re: Screen Resolution Issue

#43 2018-01-27 17:38:04

Re: Screen Resolution Issue

#44 2018-01-27 17:53:13

Re: Screen Resolution Issue

#45 2018-01-27 18:08:55

Re: Screen Resolution Issue

#46 2018-01-27 18:19:24

Re: Screen Resolution Issue

#47 2018-01-27 21:52:46

Re: Screen Resolution Issue

#48 2018-01-30 19:53:58

Re: Screen Resolution Issue

#49 2018-01-30 19:59:02

Re: Screen Resolution Issue

#50 2018-01-30 20:30:37

Re: Screen Resolution Issue

#51 2018-01-30 20:32:49

Re: Screen Resolution Issue

#52 2018-01-30 20:38:16

Re: Screen Resolution Issue

#53 2018-01-30 21:10:44

Re: Screen Resolution Issue

#54 2018-01-30 21:19:59

Re: Screen Resolution Issue

#55 2018-01-30 21:37:23

Re: Screen Resolution Issue

#56 2018-01-30 21:49:51

Re: Screen Resolution Issue

#57 2018-01-30 21:54:09

Re: Screen Resolution Issue

#58 2018-01-30 21:56:51

Re: Screen Resolution Issue

#59 2018-01-30 22:00:48

Re: Screen Resolution Issue

#60 2018-01-30 22:03:28

Re: Screen Resolution Issue

Board footer