Ask Your Question

whitepeony's profile - activity

2017-03-08 11:40:22 -0500 received badge  Famous Question (source)
2017-02-21 10:58:56 -0500 received badge  Notable Question (source)
2017-02-12 12:10:19 -0500 received badge  Notable Question (source)
2017-01-26 14:03:43 -0500 received badge  Nice Question (source)
2017-01-15 19:44:16 -0500 received badge  Popular Question (source)
2017-01-06 20:09:30 -0500 answered a question new guy unable to load Nvidia

You have three options for drivers:

  • Nouveau
  • RPM Fusion
  • NVIDIA (proprietary)

Nouveau is the default driver and should already be configured for you. Other answers have addressed the RPM Fusion driver, so I will ignore that.

If you would like to use the proprietary NVIDIA drivers, then I suggest that you carefully read and follow this guide. You do NOT have to reinstall the proprietary NVIDIA drivers with every kernel update as long as you properly configure dynamic kernel module support (DKMS), as detailed in the guide. However, you WILL have to reboot with graphics disabled in order to run the installer.

2017-01-06 19:38:08 -0500 commented answer new guy unable to load Nvidia

The proprietary drivers do not have to be reinstalled with every kernel update IF you use dynamic kernel module support.

2016-12-29 06:22:19 -0500 received badge  Nice Answer (source)
2016-12-29 04:50:38 -0500 received badge  Teacher (source)
2016-12-28 15:29:35 -0500 answered a question How can I change default Operating System in start up boot menu?

Step 1

Use the following command and find the name of the Windows entry:

$ less /boot/grub2/grub.cfg

For example, my output includes this line:

menuentry 'Windows 10 (loader) (on /dev/sdb1)' --class windows --class os $menuentry_id_option 'osprober-chain-53FBAC8F384D3675' {

You're looking for your equivalent to 'Windows 10 (loader) (on /dev/sdb1)'. Copy the entire part that's in quotes (from your output, not mine).

Step 2

As root, make a copy of "/etc/default/grub". For example:

# cp /etc/default/grub /etc/default/grub-backup

Step 3

As root, enter the following command:

# grub2-set-default MENU_ENTRY

Replace "MENU_ENTRY" with the entry name that you copied. Make sure it is in double quotes. For example:

# grub2-set-default "Windows 10 (loader) (on /dev/sdb1)"

Sources

(Yes, these are Ubuntu websites, but we're working with the Grub boot-loader rather than Fedora/Ubuntu, and I tested the above commands/paths on Fedora 25)

2016-12-28 11:27:18 -0500 asked a question Fedora 25: Unable to log in after logging out (Wayland)

Description

I can log into a Wayland session just fine after a reboot. I can also log in with Xorg after logging out, regardless of what type of session I had before. However, every time I try to log in with Wayland after having already logged out, I get kicked back to the login screen.

I am not sure if any of these are relevant, but here are all of the "important" entries from the system log:

11:59:40 AM spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
11:59:26 AM gnome-session-b: Unrecoverable failure in required component org.gnome.Shell.desktop
11:59:20 AM gnome-session-b: Unrecoverable failure in required component org.gnome.Shell.desktop
11:59:12 AM gnome-session-b: Unrecoverable failure in required component org.gnome.Shell.desktop
11:58:30 AM pulseaudio: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
11:58:29 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:29 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:29 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:29 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:29 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:28 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:28 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:28 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:28 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:58:28 AM gnome-session-b: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
11:40:47 AM krita: krita.core: Missing name attribute for tag  "date"
11:34:39 AM spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

Specifications

Memory: 31.4GiB

Processor: Intel® Core™ i7-6700K CPU @ 4.00GHz × 8

OS Type: 64-bit

Graphics: GeForce GTX 980/PCIe/SSE2

NVIDIA Driver Version: 375.26

GNOME: Version 3.22.2

Disk: 475.3 GB

2016-12-23 22:12:09 -0500 answered a question Fedora 24: Configuring Wacom Cintiq 24 HD touch

Updating to Fedora 25 has given me a new button in the Wacom Tablet applet: "Map Buttons". This provides a graphical interface for customizing the button mapping on my Cintiq 24 HD touch.

2016-12-22 22:24:03 -0500 commented answer Fedora 24: Configuring Wacom Cintiq 24 HD touch

I just checked and I already have input-wacom (v2.00), xf86-input-wacom (xorg-x11-drv-wacom-0.32.0-2.fc24.x8664), and libwacom (libwacom-0.21-1.fc24.x8664).

2016-12-22 22:14:02 -0500 received badge  Notable Question (source)
2016-12-22 22:14:02 -0500 received badge  Famous Question (source)
2016-12-02 15:36:01 -0500 received badge  Popular Question (source)
2016-08-23 17:27:34 -0500 asked a question Fedora 24: Configuring Wacom Cintiq 24 HD touch

Question

How can I map the buttons on my Wacom Cintiq 24 HD touch?

Description

I have a Wacom Cintiq 24 HD touch. It has 10 buttons as well as 2 touch rings which each have three buttons for switching modes (e.g. pan, zoom, rotate, etc). Additionally, it has dedicated buttons for help/info, the virtual keyboard, and turning touch off/on. At the time of writing, none of the buttons or touch rings perform any functions (unless I'm on Windows).

The Wacom Tablet manager in GNOME does not appear to allow mapping for them: Wacom Tablet manager in GNOME: has options to calibrate, adjust display resolution, and remap stylus

For the record: the pen pad, touch screen, and stylus all work fantastically well. However, I would like to know if there is an easy way to map the buttons and touch rings.

Thanks.

Additional Details

/usr/share/libwacom/cintiq-24hd-touch.tablet

# Wacom
# Cintiq 24HD touch
# DTH-2400
#
# Button Map:
# (A=1, B=2, C=3, ...)
#
#       *-----------------------*
#       |                       |
#  A    |                       |    I
#  B    |                       |    J
#  C    |        DISPLAY        |    K
#  DEFF |                       | NNML
#  DEGG |                       | OOML
#  DEHH |                       | PPML
#       |                       |
#       *-----------------------*
#
# Touch Ring Map:
# (A=1st ring, B=2nd ring, ...)
#
#    *-----------------------*
#    |                       |
#  A |        DISPLAY        | B
#    |                       |
#    *-----------------------*
#
# LED Map:
# (XY=Bank X, LED Y; *=Invisible)
#
#     *-----------------------*
#     |                       |
#  10 |                       | 00
#  11 |                       | 01
#  12 |        DISPLAY        | 02
#  1* |                       | 0*
#     |                       |
#     *-----------------------*
#
# Note: touch data comes through the usb:056a:00f6 interface

[Device]
Name=Wacom Cintiq 24HD touch
DeviceMatch=usb:056a:00f8
Class=Cintiq
Width=21
Height=13
Layout=cintiq-24hd.svg
Styli=0x802;0x804;0x80a;0x80c;0x902;0x90a;0x100802;0x100804;0x10080a;0x10080c;0x100902;0x10090a;0x120802;0x140802;0x14080a;0x160802;0x16080a;
IntegratedIn=Display

[Features]
Stylus=true
Reversible=false
Touch=true
Buttons=16
Ring=true
Ring2=true
StatusLEDs=Ring2;Ring

[Buttons]
Left=A;B;C;D;E;F;G;H
Right=I;J;K;L;M;N;O;P

Ring=A;B;C
Ring2=I;J;K

xinput list

⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Logitech USB-PS/2 Optical Mouse           id=9    [slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 24HD touch Finger            id=12   [slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 24HD touch Pen stylus        id=13   [slave  pointer  (2)]
⎜   ↳ Wacom Cintiq 24HD touch Pen eraser        id=16   [slave  pointer  (2)]
⎣ Virtual core keyboard                     id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Power Button                              id=7    [slave  keyboard (3)]
    ↳ Sleep Button                              id=8    [slave  keyboard (3)]
    ↳ daskeyboard                               id=10   [slave  keyboard (3)]
    ↳ daskeyboard                               id=11   [slave  keyboard (3)]
    ↳ Wacom Cintiq 24HD touch Pad               id=14   [slave  keyboard (3)]
    ↳ Logitech Logitech G35 Headset             id=15   [slave  keyboard (3)]

xsetwacom --list devices

Wacom Cintiq 24HD touch Pen stylus  id: 13  type: STYLUS    
Wacom Cintiq 24HD touch Pen eraser  id: 16  type: ERASER

xsetwacom --list parameters

Area             - Valid tablet area in device coordinates. 
Button           - X11 event to which the given button should be mapped. 
ToolDebugLevel   - Level of debugging trace for individual tools (default is 0 [off]). 
TabletDebugLevel - Level of debugging statements applied to shared code paths between all tools associated with the same tablet (default is 0 [off]). 
Suppress         - Number of points trimmed (default is ...
(more)
2016-08-23 17:09:24 -0500 received badge  Popular Question (source)
2016-07-14 05:05:03 -0500 received badge  Famous Question (source)
2016-07-12 14:51:22 -0500 commented answer Fedora 24: Stuck in endless boot cycle

NVIDIA drivers seem to have fixed the issue. Since I was on a fresh Fedora install, I went ahead and reinstalled Fedora 23. Then I got the RPM Fusion akmod-nvidia packages, followed the DNF system upgrade process, and found Fedora 24 working normally.

There was one strange problem that I don't know how to diagnose. On the automatic reboot following the Fedora 24 upgrade, I got stuck on a black screen with strobing white text which I could not read or capture; it looked like the same kind of text in my screenshot above. I performed a hard shutdown and was able to boot to Fedora 24 just fine.

2016-07-08 19:57:55 -0500 commented question Fedora 24: Stuck in endless boot cycle
2016-07-07 21:31:12 -0500 received badge  Editor (source)
2016-07-07 21:30:27 -0500 asked a question Fedora 24: Stuck in endless boot cycle

I recently (within the last two weeks) updated from Fedora 23 to Fedora 24 and can no longer get to the login screen. I see this instead:

image description

The first two lines read:

[1.506982] nouveau 0000:01:00.0: gr: failed to load fecs_inst
[1.510675] nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid

After a moment the screen goes blank and the cursor appears. There's also horizontal tearing sometimes. Then it returns to a checklist like in the picture. This problem affects Fedora 24, my backup versions of Fedora 23, and even my Fedora Live USB. The symptoms are identical regardless of which I try to load.

My system specifications:

  • Memory: 31.4 GiB
  • CPU: Intel® Core™ i7-6700K @ 4.00GHz × 8
  • GPU: NVIDIA GTX GeForce 980
  • OS Type: 64-bit
2016-05-18 05:52:43 -0500 received badge  Notable Question (source)
2016-05-10 20:51:20 -0500 received badge  Popular Question (source)
2016-03-24 10:14:06 -0500 received badge  Supporter (source)
2016-03-24 01:58:20 -0500 received badge  Student (source)
2016-03-23 20:10:21 -0500 received badge  Scholar (source)
2016-03-23 19:10:30 -0500 commented answer Fedora23: slow performance with Wayland

Is there a way to disable Wayland on the login screen?

2016-03-22 13:17:34 -0500 asked a question Fedora23: slow performance with Wayland

Description

This issue is present on the login screen or when logged in with Wayland. GNOME without Wayland works fine.

Mouse/keyboard input and graphical output (e.g. animations) freeze at consistent intervals. I get a few seconds of responsiveness followed by a period of waiting.

As long as I do not move the mouse or interact with the interface, I can type into the password field without experiencing any lag whatsoever. This lack of lag does not carry over to other text fields, though, including the terminal, GNOME search, and gedit (when logged in with Wayland).

Specifications

Fresh install of Fedora23. System last updated 22 March 2016

  • Memory: 31.4 GiB
  • CPU: Intel® Core™ i7-6700K @ 4.00GHz × 8
  • GPU: NVIDIA GTX GeForce 980
  • OS Type: 64-bit
  • Graphics: Gallium 0.4 on llvmpipe (LLVM 3.7, 256 bits)
  • GNOME: Version 3.18.2