Re: [arch-general] Nvidia backlight control - acpi_video0/brightness changes - display doesn't?
Well, this won't work for me. I don't have a NVidia. But I will search
the web if there is a module for my Intel Skylake graphics. Although my
brightness script actually works perfect. The only drawback currently:
a few apps (e.g. chromium) reset the brightness to max upon their
startup.
Thanks anyway!
Christian
On Sun, 2016-11-20 at 03:08 -0600, David C. Rankin wrote:
> On 11/19/2016 03:38 AM, Christian Klaue wrote:
> > I am having exactly the same problem with my HP. I went as far as
> > decompiling the ACPI bios. When I tried to compile it again, it
> > threw a
> > huge amount of errors. So I gave up. I didn't find any solution for
> > my
> > problem. I even tried other distros. I am still kind of convinced
> > the
> > error is in the ACPI module(s) of your UEFI. If you try to blame HP
> > (as
> > many people on their forum did before) they will ask you to test on
> > Windows. Unfortunately there it works. The newest BIOS update
> > doesn't
> > fix the problem for my toy.
> >
> > I am lucky to have an OLED. Please keep me updated if you find a
> > solution.
>
> Christian,
>
> You may be in luck. I did find a solution and now my backlight
> functions as
> it should using the nvidiabl kernel module (and a small helper script
> that I
> autostart in KDE, but you could just as easily start it in .xinitrc
> for any
> desktop) Basically, you have to use either of the following two
> packages to
> build a kernel module that will work with the proprietary nvidia
> driver:
>
> nvidia-bl
> https://aur.archlinux.org/packages/nvidia-bl/
>
> nvidiabl
> https://aur.archlinux.org/packages/nvidiabl/
>
> I built them both, but haven't tried nvidia-bl, (even though it was
> easier
> to build and should do the same thing)
>
> To build nvidiabl, just follow the notes on its aur page and it
> builds fine.
> nvidia-bl, builds without issue, just download the tarball, unpack
> it, and
> then a makepkg -s is all that is needed.
>
> Both provide the kernel module:
>
> /usr/lib/modules/extramodules-4.8-ARCH/nvidiabl.ko
>
> Just build, then 'modprobe nvidiabl', and you will have backlight
> control
> through:
>
> /sys/class/backlight/nvidia_backlight/brightness
>
> The kicker is that nothing talks to nvidia_backlight by default,
> instead all
> the normal backlight controls use:
>
> /sys/class/backlight/acpi_video0/brightness
>
> The way to get your controls to work is to watch the
> acpi_video0/brightness
> values and automatically set nvidia_backlight/brightness any time the
> earlier
> one changes value. This is where the helper script comes into play
> (actually 2
> short scripts -- the second just to ease the sudo redirection issue)
>
> The first script just maps values (0-20) from
> acpi_video0/brightness into a
> range of (0-127) for nvidia_backlight/brightness (it calls the second
> script
> as a helper). Just launch the first script in whatever desktop you
> are using,
> and your backlight keys should work. If not, then you just have to
> copy
> whatever value you want for your backlight/brightness to
> nvidia_backlight/brightness, e.g.
>
> # echo 90 > /sys/class/backlight/nvidia_backlight/brightness
>
> Put both scripts in the same directory. You will need to configure
> sudo
> without a password for this to work when called as your normal user
> (as when
> using the laptop keys). The first is a quick modification of the
> xbacklight
> script. It reads the xbacklight value from acpi_video0 and then does
> a rough
> scale for what the nvidia_backlight value should be. Give it some
> name like
> nvbackligh.sh:
>
> #!/bin/sh
>
> path=/sys/class/backlight/acpi_video0
> dest=/sys/class/backlight/nvidia_backlight
> dmax=$(<$dest/max_brightness)
>
> luminance() {
> read -r level < "$path"/actual_brightness
> factor=$((dmax / max))
> nvbrt=$((level * factor))
> case "$nvbrt" in
> [0-9] ) printf "%d" $nvbrt;;
> [0-9][0-9] ) printf "%d" $nvbrt;;
> [1][0-1][0-9] ) printf "%d" $nvbrt;;
> [1][2][0-9] ) printf "127";;
> default ) printf "error: in value conversion\n"
> exit 1;;
> esac
> }
>
> read -r max < "$path"/max_brightness
>
> inotifywait -me modify --format '' "$path"/actual_brightness | while
> read; do
> if [ $UID -eq 0 ]; then
> echo $(luminance) > "$dest"/brightness
> else
> sudo ./nvhelper.sh $(luminance) # helper script
>
Re: [arch-general] Nvidia backlight control - acpi_video0/brightness changes - display doesn't?
Hi, your xrandr --brightness solution only works on oled screens. Those don't have a backlight. From a quick search it looks like you have a LCD, right? I am having exactly the same problem with my HP. I went as far as decompiling the ACPI bios. When I tried to compile it again, it threw a huge amount of errors. So I gave up. I didn't find any solution for my problem. I even tried other distros. I am still kind of convinced the error is in the ACPI module(s) of your UEFI. If you try to blame HP (as many people on their forum did before) they will ask you to test on Windows. Unfortunately there it works. The newest BIOS update doesn't fix the problem for my toy. I am lucky to have an OLED. Please keep me updated if you find a solution. regards, Christian On Sat, 2016-11-19 at 03:09 -0600, David C. Rankin wrote: > On 11/19/2016 02:35 AM, Patrick Burroughs (Celti) via arch-general > wrote: > > acpi_backlight=vendor is the default, acpi_backlight=none is > > invalid. > > The option you are looking for is acpi_backlight=video, which takes > > the > > backlight control away from the vendor driver and hands it back > > over to > > the standard ACPI backlight driver. This will generally solve the > > issue > > you are having. > > > > ~Celti > > Damn, > > And it worked so well that way :( Thank you for identifying the > brightness/backlight issue. The Backlight wiki is where I first got > the > acpi_backlight=none suggestion, see: > > https://wiki.archlinux.org/index.php/Backlight#Kernel_command-line_op > tions > > I've tried the acpi_backlight=video, and still no-joy (at least I > still have > the acpi_video0 sysfs interface with that setting). The nice pop-up > still > appears and shows the brightness adjustment, but the screen never > changes. > (same symptoms as before) > > How is adjusting xrandr --brightness bad compared to adjusting > /sys/class/backlight/acpi_video0/brightness?? I understand setting > xrandr > --brightness greater than 1.0 will draw additional power, etc.., but > how is > setting it between 0.0 and 1.0 different than doing it with acpi? I'm > just > trying to get it sorted out in my mind to understand the difference > between > setting: > > /sys/class/backlight/acpi_video0/brightness > > and > > xrandr --output LVDS-0 --brightness $foo > > I'll go search to see if I can find the difference, but if you have > a > favorite link, I'd appreciate the help. >
Re: [arch-general] [OT] Favorite/best desktop in archlinux
There is no "best enviroment" for everyone. Ask for advantages / disadvantages. Check if the answers still apply nowadays. Let's see for my personal opinion. When I started with linux I started on cinnamon / mate since it is been most closely to windows. It's also been as buggy as windows. Back then. I am sure / I hope it is much more stable nowadays. I tried a few "basic" / "specialized" and "experimental" desktops. (No offence to anyone!). None did fit my personal "one for all" requirements. Other people can't follow my "I paid for a mouse I wan't to use it" philosophy. With such a "noob" philosophy back then there had been KDE, gnome and mate/cinnamon. One aspect is important: no matter which decission you take (KDE or another): GTK and QT can be very well be used in parallel. So an argument like "if you go for gnome you can't use Kaffeine" is bullshit. QT and GTK can coexistent and nowadays with the right themes you won't actually be able to say which app is using what. Back to the 3 major players: . KDE looks close to Windows and fancy. QT is closed sw. In my personal opinion KDE offers too many configurations (early plasma) and is been laggy (KDE 4). . Cinnamon is been wonderful. Unfortunately very buggy. (appr. 3 yrs ago) . Gnome is ugly. Very ugly. Ever seen a "Adwaita"-themed window header? (still valid) Well: I stayed with Gnome. While writing this I still use QT- applications (namely I watch TV using Kaffeine on my second screen). Just give every DE a try and after u decided look out for themes and customizations. There are plenty out there. In most cases for all big players. Eg. yakuake for qt/KDE and guake for gtk. As for Gnome: I use arc-theme and viola, it looks bautiful now. I added guake, dash-to-dock extension and a few other things. Nowadays I would not even consider KDE. Anyway, yours may be still KDE. Or Gnome. Or Cinnamon. Or Enlightment. Or any other. A friend uses enlightment and won't consider any other. Let me know if u have a valid reason for one specific. On Mon, 2016-11-07 at 16:58 -0600, David C. Rankin wrote: > On 11/06/2016 04:12 PM, Maykel Franco via arch-general wrote: > > Hi, what the best desktop envieronment for archlinux? Only is the > > question. > > > > I like very much kde plasma but he used a lot of ram and sometimes > > it > > is very heavy. Do you think? > > > > I agree with the remainder, the choice is yours. That said, I built > TDE (KDE3) for Arch for years after chakra stopped building kdemod3, > and > that was (and still is) my all time favorite. .I've recently started > using Plasma, and while it is a behemoth, it is relatively well > behaved > from a resources standpoint. Gnome, I thoroughly enjoyed gnome 2. My > experience with gnome 3 was much like my experience with KDE4. > > It all boils down to what do you need your desktop to do? Do you > rely > on any of the apps unique to any one desktop? (e.g. I like > kate/kwrite > and I like the tabbed interface to konsole) Were it not for those 3 > apps, I could care less which desktop I use. I like fluxbox as a > minimal > desktop (any of the boxtop desktops are pretty much the same -- > sawfish > is a little too bare bones for me) > > The midlevel desktop goes to XFCE, capable, relatively full suite > of > basic apps, but it too has experienced growing pains over the past > two > years. > > Gnome or KDE - take your pick. Both are essentially a moving target > at > this point. Both are more than capable and both provided just about > all > you need built in. > > Best/Favorite is in the eye of the beholder... >
Re: [arch-general] WLAN
Just a guess: with my Lenovo initially I had a similar problem which turned out to be a missing driver. Installing some 3rd party AUR package it worked fine. Have you checked lspci? Kernel mods? Which module is built in? Ever searched for it? With my HP I am having some bios problems (caused by HP - I will never get any HP anymore). After each reboot I have to wait for approx 3 minutes before it is working. Meanwhile wifi is constantly turned on and off again: there is no hardware button but bios is still reporting it had been turned off and on. Check if there are bios reports on the net. Usually you are not the first. The same error does not appear on windows. unassambling efi and compiling it again threw something like 30 errors on the wifi module in efi... ente On Sun, 2016-11-06 at 22:56 +0100, Silvio Siefke wrote: > Hello, > > i've installed Arch Linux today on Desktop (HP Elitebook 2540p) but > wifi work not. I become message "Wireless networks disabled by > hardware > switch" > > Have someone an idea what can do? > > Thank you > Silvio > > [siefke@sisibox ~]$ rfkill list > 0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: yes > 2: hci0: Bluetooth > Soft blocked: no > Hard blocked: no > > [siefke@sisibox ~]$ iwconfig > lono wireless extensions. > > enp0s25 no wireless extensions. > > wlo1 IEEE 802.11abgn ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx- > Power=off > Retry short limit:7 RTS thr:off Fragment thr:off > Power Management:off > > [siefke@sisibox ~]$ dmesg | grep phy0 > [3.097608] ieee80211 phy0: Selected rate control algorithm 'iwl- > agn-rs' > > [siefke@sisibox ~]$ dmesg | grep wlo1 > [3.306866] iwlwifi :43:00.0 wlo1: renamed from wlan0 > [3.775157] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready > [4.078492] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready > [4.385304] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready > [4.720437] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready > > [siefke@sisibox ~]$ dmesg | grep iwl > [3.051266] iwlwifi :43:00.0: can't disable ASPM; OS doesn't > have ASPM control > [3.051662] iwlwifi :43:00.0: Direct firmware load for > iwlwifi-6000-6.ucode failed with error -2 > [3.051681] iwlwifi :43:00.0: Direct firmware load for > iwlwifi-6000-5.ucode failed with error -2 > [3.056639] iwlwifi :43:00.0: loaded firmware version > 9.221.4.1 build 25532 op_mode iwldvm > [3.075301] iwlwifi :43:00.0: CONFIG_IWLWIFI_DEBUG disabled > [3.075305] iwlwifi :43:00.0: CONFIG_IWLWIFI_DEBUGFS disabled > [3.075307] iwlwifi :43:00.0: CONFIG_IWLWIFI_DEVICE_TRACING > enabled > [3.075309] iwlwifi :43:00.0: Detected Intel(R) Centrino(R) > Advanced-N 6200 AGN, REV=0x74 > [3.075413] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [3.097608] ieee80211 phy0: Selected rate control algorithm 'iwl- > agn-rs' > [3.306866] iwlwifi :43:00.0 wlo1: renamed from wlan0 > [3.775329] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [3.781845] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [3.781936] iwlwifi :43:00.0: Radio type=0x1-0x3-0x1 > [3.993451] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [3.68] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [4.61] iwlwifi :43:00.0: Radio type=0x1-0x3-0x1 > [4.080224] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [4.086756] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [4.086859] iwlwifi :43:00.0: Radio type=0x1-0x3-0x1 > [4.300192] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [4.306715] iwlwifi :43:00.0: L1 Enabled - LTR Disabled > [4.306816] iwlwifi :43:00.0: Radio type=0x1-0x3-0x1 > [6.993231] iwlwifi :43:00.0: RF_KILL bit toggled to disable > radio. > [6.994137] iwlwifi :43:00.0: Not sending command - RF KILL > > [siefke@sisibox ~]$ lspci | grep Network > 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit > Network Connection (rev 05) > 43:00.0 Network controller: Intel Corporation Centrino Advanced-N > 6200 (rev 35)
Re: [arch-general] Updates blocked by ttf-dejavu
I subscribed to the Arch Announcement feed at https://lists.archlinux.o rg/listinfo/arch-announce You almost never get any mail (which I love). It's actually a copy of everything which will be shown on the arch website frontpage. Since I never had any trouble with updates besides those mentioned on this page, it perfectly fits my requirements. Of course you may still run into AUR trouble... but that's kinda another story. With respect to update information: just run a full update on a daily basis. That's what I am doing. Pacman informs me. For gnome there is a neat tool: Arch Linux Update Indicator. It hides the icon if there are no updates. I used to use Kalu (which may be helpful on KDE). Works fine as well but shows the icon all the time. Actually such tools are unnecessary since there is an update available each day for my system. Even if you go for a weekly check, it is not waste of time. So, if I understood your question correct: use pacman + Arch Announcement mailing list. regards, ente On Tue, 2016-11-01 at 13:28 +0100, Peter Nabbefeld wrote: > Thank You. At some time I've subscribed to the arch linux update > feed, > but it doesn't seem very useful, so I'll remove it: > > 1. It seems not all updates are reported > 2. It doesn't show any hints - just like this > > Do You probably know of any other more useful feed(s)? > > Kind regards > Peter > > > Am 01.11.2016 um 09:49 schrieb Christian Klaue: > > See the website for tips on how to update: https://www.archlinux.or > > g/ne > > ws/ttf-dejavu-237-will-require-forced-upgrade/ > > > > pacman -S --force ttf-deja > > > > > > ente > > > > On Tue, 2016-11-01 at 09:47 +0100, Peter Nabbefeld wrote: > > > Hello, > > > > > > cannot update packages, as ttf-dejavu has conflicts. > > > > > > > > > --- > > > Output > > > --- > > > Fehler: Konnte den Vorgang nicht durchführen (In Konflikt > > > stehende > > > Dateien) > > > ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans- > > > mono.conf > > > existiert im Dateisystem > > > ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans.conf > > > existiert > > > im Dateisystem > > > ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-serif.conf > > > existiert im Dateisystem > > > ttf-dejavu: /etc/fonts/conf.d/57-dejavu-sans-mono.conf existiert > > > im > > > Dateisystem > > > ttf-dejavu: /etc/fonts/conf.d/57-dejavu-sans.conf existiert im > > > Dateisystem > > > ttf-dejavu: /etc/fonts/conf.d/57-dejavu-serif.conf existiert im > > > Dateisystem > > > Fehler sind aufgetreten, keine Pakete wurden aktualisiert. > > > > > > --- > > > Translation for output > > > --- > > > Error: Could not proceed (files in conflict) > > > ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans- > > > mono.conf > > > exists in file system > > > ... > > > Errors occured, no packages updated > > > > > > --- > > > > > > Kind regards > > > Peter
Re: [arch-general] Updates blocked by ttf-dejavu
See the website for tips on how to update: https://www.archlinux.org/ne ws/ttf-dejavu-237-will-require-forced-upgrade/ pacman -S --force ttf-deja ente On Tue, 2016-11-01 at 09:47 +0100, Peter Nabbefeld wrote: > Hello, > > cannot update packages, as ttf-dejavu has conflicts. > > > --- > Output > --- > Fehler: Konnte den Vorgang nicht durchführen (In Konflikt stehende > Dateien) > ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf > existiert im Dateisystem > ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans.conf > existiert > im Dateisystem > ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-serif.conf > existiert im Dateisystem > ttf-dejavu: /etc/fonts/conf.d/57-dejavu-sans-mono.conf existiert im > Dateisystem > ttf-dejavu: /etc/fonts/conf.d/57-dejavu-sans.conf existiert im > Dateisystem > ttf-dejavu: /etc/fonts/conf.d/57-dejavu-serif.conf existiert im > Dateisystem > Fehler sind aufgetreten, keine Pakete wurden aktualisiert. > > --- > Translation for output > --- > Error: Could not proceed (files in conflict) > ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf > exists in file system > ... > Errors occured, no packages updated > > --- > > Kind regards > Peter
