hybrid graphics laptop and nouveau
by AV
Hello,
This concerns an Asus Zenbook with hybrid graphics (Intel/Nvidia).
1) There are 2 ways to deactivate the nouveau driver:
by adding 'modprobe.nouveau=0' to the kernel cmd line OR
by adding 'modprobe.blacklist=nouveau rd.blacklist=nouveau'.
Which is to be preferred?
2) I do the above because there is as yet no Nvidia driver that
gives a hybrid solution like under Windows and the Intel driver
is more than enough for my needs.
However when using a solution as described in 1) the Nvidia chip
will still drain power. Is there anyway to deactivate the chip?
(short of removing it from the motherboard if possible).
AV
4 years, 8 months
Thinkpad X301 Trackpoint Sensitivity Setting
by Christopher St. Louis
I booted up my laptop yesterday to find that the Trackpoint sensitivity had
somehow dramatically increased such that a slight nudge sends the mouse pointer
flying across the screen, and clicking on any buttons or menu items requires me
to circle around the selected item like a plane approaching the runway before I
can finally make the selection.
I have no idea what caused this, and to my knowledge I haven't installed
anything manually or through daily updates that would cause such a dramatic
change. This laptop started as a Fedora 26 XFCE installation but I'm using i3wm
for my daily driver. Logging into XFCE and adjusting the Trackpoint ("pointing
stick") sensitivity in xfce4-settings-manager appears to have some
effect while in XFCE; these changes don't follow over to i3 and when I run
Settings under i3 any changes don't appear persist or have any effect (e.g. the
sensitivity defaults to 5; I set it to a more sane 2 and close the window. No
effect on the pointer speed, and re-opening Settings shows the sensitivity back
at 5).
Looking online, there is an enormous amount of vestigial information on just
where the configuration for Trackpoint settings is stored and how it is done,
often with no indication of which is the most recent method or what is
distro-specific. Some instructions are written for Ubuntu or Arch and mention
locations which don't exist. I've seen the solution related to xinput, evdev,
hal, udev; configurations should go in Xorg.conf
or /etc/X11/xorg.conf.d/10-somenamedfile.conf or .xinitrc or...; there are
references to attributes being exposed
at /sys/devices/platform/i8042/serio1/serio2/ which also doesn't exist on my
machine. In general, it's a confusing mess, and it's demanding a
disproportionately ridiculous amount of work just so I'm not constantly
overshooting toolbar buttons in LibreOffice.
I won't even try to diagnose what property might have magically changed in
from one day to the next that turned a perfectly working system into one with
this distracting annoyance; that way lies madness. But can anyone tell me
just WHERE I would go to attempt to change the sensitivity of a Thinkpad
Trackpoint (I suppose this would be the same place as general mouse/touchpad
settings) on a Fedora 26 installation? And more specifically, are there any
X300/301/similar-era Thinkpad users here who have had experiences configuring
your Trackpoint/touchpad in recent Fedora releases?
Thanks in advance.
4 years, 8 months
strange screen tearing effect
by Tim
Since updating to Fedora 26, I get a strange screen tearing effect on
any moving image (scrolling webpages, watching live video, anything
that moves). The effect is unnoticeable on static displayes. The
effect is like this diagram:
http://imgbox.com/TqED2C76
There's a portion at the top of the screen related to one moment in
time, with a dividing line going across the screen, related to another
moment. The really strange thing is that there's a diagonal portion to
this division.
The division slowly rolls down the screen, so it can be seen that the
screen refresh rate is different from the source material (whatever it
may be).
According to driconf, which offers options I know nothing about, and
offers nothing I see related to setting any vertical sync options, the
graphics set is using: NV98 (nouveau)
The display configurator (I'm using Mate) gives me 60 or 75 Hz refresh
rates, and they will change the rate that the dividing line rolls down
the screen, but not eliminate it.
I'm using a LCD screen connected through a DVI cable (both ends, no
conversions). Mate's display configurator says its DVI-I
How can I get rid of this?
--
[tim@localhost ~]$ uname -rsvp
Linux 4.13.5-200.fc26.x86_64 #1 SMP Thu Oct 5 16:53:13 UTC 2017 x86_64
Boilerplate: All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.
Using Windows software is like coating all your handtools with sewage.
4 years, 8 months
FW update from gnome-softwares
by Jeandet Alexis
Hello,
Today I got for the first time a dell Precision 5520 and I saw the
firmware(EFI) update from gnome softwares, this is AWESOME!
I hope more vendors will push their fw in the near future :).
Thanks guys,
Alexis.
4 years, 8 months
Re: f26 to f26 cups sharing problem
by tar＠sonic.net
>Take that entry out of the hosts file, then try "ping liberty.local".
>Does it work? If not, then make sure you have the "nss-mdns" package
>installed.
Well this seems to be on the right track(mdns issue).
I removed the ".local" line from /etc/hosts .
The nss-mdns package is installed, so I decided to test it as suggested in
the README.
On the client, testing for the client address
getent hosts rights.local
returns
192.168.1.4 rights.local
Great, that's what we want fromnss-mdns, so now lets test for the server
address:
getent hosts liberty.local
... times out with no response and returns a status code of 2.
Which seems to match the timeout from "cups-browsed -v"
If I skip the ".local" we get
getent hosts rights
192.168.1.4 rights.localdomain rights
.. correct for the client
getent hosts liberty
192.168.1.6 liberty.localdomain liberty
.. correct for the server
And since this all depends on /etc/nsswitch.conf, the relevant line there is
hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname
I also confirmed that avahi-daemon is running on the client
and that firewalld has mdns allowed (client and server).
Thanks for the good lead, this seems to be the problem area, any ideas on
next things to try/investigate?
4 years, 8 months
