Graphics (and other) issues

hi all
i just get the latest stable manjaro with gnome
i quite like it, but have some minor issues, or more probable that -as i use linux at 1st time,- i don’t know how to set up properly
i have a mini pc, beelink x55, j5005 gemini lake intel graphics hd 605
i choose non-free at installation, by misunderstanding, i don’t know if this effects on a bad way, but i don’t think, as in the settings i have only open source driver option, with this under
K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202018-10-19%2011-41-33
if i install video-vesa, i have black out after reboot, i needed to install again.
now i’m confused, as i have no clue if everything is correct. on w10 i have nvidia settings, but here obviously i don’t know how is supposed to be correct (i’m not a w10 and hw specialist too)
at first install i also had here the nvidia settings, but didn’t open the app, now with second install it’s not there anymore. i both used non-free
should i install again with free option?

also i have animation issues, they are extremely slow especially when i open gnome apps. it feels like i have 256mb of ram
w10 boots 10-15 secs, manjaro about a minute. even after type password, it needs to load the desktop again another 15 secs

my question is; what should i do to make sure i have proper driver installed for this pc?

i don’t know if this connected, but also when i open up the file manager, it need like 5 secs to bring it up, while i guess with this pc should fly for these things (but for example gimp takes about same time, even if it should be much heavier app)

sorry, i know well i’m extremely noob with linux, but i need a kickstart :slight_smile:

thanks to anybody who have any idea

Removed

would you explain about i3 openbox with a bit details, please?

in fact it’s not even option, only i can choose open source and only that video-linux works.
i also wrote that i did with misunderstanding (that means after i realized i need the free option) plus also that i’m not specialist
do i need to install again and choose free, or it’s okay like this?

So don’t install that driver. :wink: The best driver for your hardware should be detected during installation.

Do you have NVIDIA graphics? If not, the NVIDIA driver won’t have installed, so you won’t have that application either.

You probably want to switch from the intel driver to modesetting. Essentially, remove xf86-video-intel and reboot.

Paste the output of inxi -Fxxxz so we can get a better idea of your hardware. Also read

and have a browse of the #faq and #technical-issues-and-assistance:tutorials sections.

1 Like

Please don’t suggest to self-professed newbies that using a different window manager is a good option, especially an advanced one like i3, and especially when this doesn’t address the root of the issues raised/questions asked.

Please use full words in your replies. You are not saving any time by shortening them and these “non-words” are impossible for non-native readers to understand or run through a translator. Even native readers find them jarring.

8 Likes
System:
  Host: ii9-pc Kernel: 4.14.74-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 8.2.1 Desktop: Gnome 3.30.1 wm: gnome-shell dm: GDM 3.30.0 
  Distro: Manjaro Linux 
Machine:
  Type: Laptop System: Beelink product: Gemini X v: N/A serial: <filter> 
  Mobo: N/A model: N/A serial: <filter> UEFI: American Megatrends v: 0.08 
  date: 06/19/2018 
CPU:
  Topology: Quad Core model: Intel Pentium Silver J5005 bits: 64 type: MCP 
  arch: Goldmont Plus rev: 1 L2 cache: 4096 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 11984 
  Speed: 799 MHz min/max: 800/2800 MHz Core speeds (MHz): 1: 798 2: 800 
  3: 798 4: 799 
Graphics:
  Device-1: Intel driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3184 
  Display: x11 server: X.org 1.20.1 driver: i915 compositor: gnome-shell 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: Mesa DRI Intel UHD Graphics 605 (Geminilake) 
  v: 4.5 Mesa 18.2.2 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel vendor: Realtek driver: snd_hda_intel v: kernel 
  bus ID: 00:0e.0 chip ID: 8086:3198 
  Sound Server: ALSA v: k4.14.74-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  driver: r8168 v: 8.045.08-NAPI port: e000 bus ID: 02:00.0 
  chip ID: 10ec:8168 
  IF: eno1 state: down mac: <filter> 
  Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel port: e000 
  bus ID: 03:00.0 chip ID: 8086:3165 
  IF: wlp3s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 119.24 GiB used: 9.67 GiB (8.1%) 
  ID-1: /dev/sda vendor: Foresee model: 128GB SSD size: 119.24 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 3 scheme: GPT 
Partition:
  ID-1: / size: 107.92 GiB used: 9.67 GiB (9.0%) fs: ext4 dev: /dev/sda2 
  ID-2: swap-1 size: 8.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:
  System Temperatures: cpu: 59.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 208 Uptime: 2h 43m Memory: 7.62 GiB used: 2.28 GiB (30.0%) 
  Init: systemd v: 239 Compilers: gcc: 8.2.1 Shell: bash v: 4.4.23 
  running in: gnome-terminal inxi: 3.0.26

Yeah - I suspect the GPU is too new or not known to Xorg so it’s falling back to the old i915 driver. Switching to modesetting should fix the graphics issues.

sure thing, i just wrote to give more info

any hint?

thanks

i know i don’t have nvidia, just to make clear. i only said, i had on w10 a settings panel(don’t ask me why).
i just wanted mo make sure if the recent driver is the best, or this lags are normal on any linux/manjaro/gnome
i wrote everything in the 1st post, to give more info, that i thought is needed to my question, next time i try to think twice how i ask.

ah… great at least you can see something out of that unlike me :slight_smile:
well so please explain to me if it’s okay for you, how i do

This is a good opportunity for some research so you can start to become more self-sufficient. Yes, I could write down the exact instructions (yet again) but this has been covered all over the forum and wider web (e.g. the Arch wiki). :wink:

this is how i did until this part, if i have chance not to write in a forum with my crap, i’m the happiest
:slight_smile:
yes, i found out, yes i needed to find out that i need to do with package manager, yes i’m so noob, i never touched linux til yesterday, :slight_smile:

thanks 4 help anyway, i try

Feel free to ask if you’re not sure - but at least you have made a start. :wink:

thanks
anyway i did it, slightly faster, let’s say 5-10%
i guess i need to wait til they work on this “new” hw, right?

1 Like

You can always check your running processes with htop or your GUI task manager to see CPU and/or memory consumption during working with apps.
Also check the logs for errors

journalctl -p3
cat ~/.local/share/xorg/*.log* | grep "(EE)"

hi
not sure if i did well what you said, but if this what you meant, here i go

-- Logs begin at Thu 2018-10-18 20:48:42 CEST, end at Fri 2018-10-19 18:14:22 C>
okt 18 20:48:43 ii9-pc kernel: tpm tpm0: TPM self test failed
okt 18 20:51:44 ii9-pc kernel: usb usb2-port1: cannot disable (err = -32)
okt 18 20:57:47 ii9-pc kernel: usb usb2-port1: cannot disable (err = -32)
okt 18 21:03:01 ii9-pc crond[371]: (root) CAN'T OPEN (/etc/crontab): Nincs ilye>
okt 18 21:46:58 ii9-pc gdm[469]: GLib: g_hash_table_find: assertion 'version ==>
okt 18 21:46:59 ii9-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
okt 18 21:47:17 ii9-pc bluetoothd[357]: Failed to set mode: Blocked through rfk>
okt 18 21:47:28 ii9-pc bluetoothd[357]: RFCOMM server failed for Headset Voice >
okt 18 21:47:28 ii9-pc bluetoothd[357]: RFCOMM server failed for :1.133/Profile>
okt 18 21:47:31 ii9-pc bluetoothd[357]: Failed to set mode: Blocked through rfk>
okt 18 21:47:38 ii9-pc systemd[964]: Failed to start Tracker metadata database >
okt 18 22:36:20 ii9-pc NetworkManager[358]: <error> [1539894980.6258] audit: fa>
okt 18 22:47:19 ii9-pc systemd[964]: Failed to start Tracker metadata database >
okt 18 22:49:26 ii9-pc systemd[964]: Failed to start Tracker metadata database >
okt 18 22:59:56 ii9-pc systemd[964]: Failed to start Tracker metadata database >
okt 18 23:23:59 ii9-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
okt 18 23:24:19 ii9-pc bluetoothd[346]: Failed to set mode: Blocked through rfk>
okt 18 23:24:36 ii9-pc bluetoothd[346]: RFCOMM server failed for Headset Voice >
okt 18 23:24:36 ii9-pc bluetoothd[346]: RFCOMM server failed for :1.133/Profile>
okt 18 23:24:39 ii9-pc bluetoothd[346]: Failed to set mode: Blocked through rfk>
okt 18 23:24:45 ii9-pc systemd[961]: Failed to start Tracker metadata database >
okt 19 00:03:59 ii9-pc systemd[961]: Failed to start Tracker metadata database >
okt 19 00:04:06 ii9-pc kernel: usb usb2-port1: cannot disable (err = -32)
okt 19 00:04:23 ii9-pc gdm[409]: GLib: g_hash_table_find: assertion 'version ==>
-- Reboot --
okt 19 08:31:03 ii9-pc bluetoothd[365]: RFCOMM server failed for Headset Voice >
okt 19 08:31:03 ii9-pc bluetoothd[365]: RFCOMM server failed for :1.136/Profile>
okt 19 08:31:13 ii9-pc systemd[974]: Failed to start Tracker metadata database >
okt 19 09:38:23 ii9-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
okt 19 09:38:47 ii9-pc bluetoothd[368]: RFCOMM server failed for Headset Voice >
okt 19 09:38:47 ii9-pc bluetoothd[368]: RFCOMM server failed for :1.133/Profile>
okt 19 09:38:58 ii9-pc systemd[965]: Failed to start Tracker metadata database >
okt 19 09:45:02 ii9-pc gdm[447]: GLib: g_hash_table_find: assertion 'version ==>
okt 19 09:45:02 ii9-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
okt 19 09:45:27 ii9-pc bluetoothd[333]: RFCOMM server failed for Headset Voice >
okt 19 09:45:27 ii9-pc bluetoothd[333]: RFCOMM server failed for :1.133/Profile>
okt 19 09:45:38 ii9-pc systemd[958]: Failed to start Tracker metadata database >
okt 19 09:54:35 ii9-pc gdm[392]: GLib: g_hash_table_find: assertion 'version ==>
okt 19 09:54:36 ii9-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
okt 19 09:54:59 ii9-pc bluetoothd[375]: RFCOMM server failed for Headset Voice >
okt 19 09:54:59 ii9-pc bluetoothd[375]: RFCOMM server failed for :1.135/Profile>
okt 19 09:55:10 ii9-pc systemd[964]: Failed to start Tracker metadata database >
okt 19 10:05:29 ii9-pc systemd[964]: Failed to start Tracker metadata database >
okt 19 10:07:11 ii9-pc gdm[429]: GLib: g_hash_table_find: assertion 'version ==>
okt 19 10:07:12 ii9-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
okt 19 10:07:45 ii9-pc bluetoothd[360]: RFCOMM server failed for Headset Voice >
okt 19 10:07:45 ii9-pc bluetoothd[360]: RFCOMM server failed for :1.133/Profile>
okt 19 10:07:55 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:05:05 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:10:41 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:11:21 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:27:51 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:29:26 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:40:36 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:40:53 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:41:07 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 11:51:14 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 12:01:10 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 12:13:15 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 12:20:28 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 12:21:00 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 12:44:43 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 13:00:27 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 13:38:18 ii9-pc gdm[412]: GLib: g_hash_table_find: assertion 'version ==>
okt 19 13:38:19 ii9-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
okt 19 13:38:36 ii9-pc bluetoothd[368]: Failed to set mode: Blocked through rfk>
okt 19 13:38:54 ii9-pc bluetoothd[368]: RFCOMM server failed for Headset Voice >
okt 19 13:38:54 ii9-pc bluetoothd[368]: RFCOMM server failed for :1.134/Profile>
okt 19 13:38:57 ii9-pc bluetoothd[368]: Failed to set mode: Blocked through rfk>
okt 19 13:39:04 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 14:43:55 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 15:10:32 ii9-pc systemd[963]: Failed to start Tracker metadata database >
okt 19 15:11:13 ii9-pc systemd[963]: Failed to start Tracker metadata database >
-- Reboot --
okt 19 17:56:10 ii9-pc bluetoothd[332]: RFCOMM server failed for Headset Voice >
okt 19 17:56:10 ii9-pc bluetoothd[332]: RFCOMM server failed for :1.136/Profile>
okt 19 17:56:21 ii9-pc systemd[969]: Failed to start Tracker metadata database >
okt 19 17:59:31 ii9-pc kernel: watchdog: watchdog0: watchdog did not stop!
-- Reboot --
okt 19 17:59:56 ii9-pc bluetoothd[395]: RFCOMM server failed for Headset Voice >
okt 19 17:59:56 ii9-pc bluetoothd[395]: RFCOMM server failed for :1.135/Profile>
okt 19 18:00:06 ii9-pc systemd[960]: Failed to start Tracker metadata database >
okt 19 18:08:45 ii9-pc systemd[960]: Failed to start Tracker metadata database >
lines 69-91/91 (END)
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    16.350] (EE) Failed to load module "intel" (module does not exist, 0)
[    16.351] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    16.351] (EE) Failed to load module "vesa" (module does not exist, 0)
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    16.542] (EE) Failed to load module "intel" (module does not exist, 0)
[    16.543] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    16.544] (EE) Failed to load module "vesa" (module does not exist, 0)

looks not too okay for me :smiley:

It seems your connection HW are blocked, maybe need proper drivers.
For better view please post

journalctl -p3 -b | cat
rfkill list

IIRC the proper cmd. I guess @tbg would better help on this. :wink:

-- Logs begin at Thu 2018-10-18 20:48:42 CEST, end at Sat 2018-10-20 10:40:41 CEST. --
okt 20 10:38:26 ii9-pc bluetoothd[354]: Failed to set mode: Blocked through rfkill (0x12)
okt 20 10:38:39 ii9-pc bluetoothd[354]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
okt 20 10:38:39 ii9-pc bluetoothd[354]: RFCOMM server failed for :1.136/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb: rfcomm_bind: Address already in use (98)
okt 20 10:38:43 ii9-pc bluetoothd[354]: Failed to set mode: Blocked through rfkill (0x12)
okt 20 10:38:50 ii9-pc systemd[4851]: Failed to start Tracker metadata database store and lookup manager.
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

here they r

(a little different thing)
not as important, but as i wanna be able to handle linux
i installed dolphin, cuz for me suits more. i did pin it to the favs, but when i open it, it brings a second icon
K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202018-10-20%2013-42-04

i looked for solution, but did’t find yet
if i undersand well, i should somehow change the name of .desktop
they mean this?
K%C3%A9perny%C5%91k%C3%A9p%20%E2%80%93%202018-10-20%2013-15-45
if yes, obviously the rename is inactive, so i can’t change. as i see it’s the only unknown file, may be that the deal?
pls let me know if i’m going on a good direction, or let me have some hint
thanks

Then why not using KDE Plasma? I mean, Dolphin File Manager in Gnome … it installed so many dependencies and will always open a new instance, but not the Gnome way.
Look at the difference between org.gnome.Nautilus.desktop and org.kde.dolphin.desktop files inside /usr/share/applications
You have to gnomify the dolphin *.desktop file to work the Gnome way (and even so, might not behave as it does at it’s home=KDE Plasma)
Anyway … i appreciate people that are enthusiasts and experiment a lot of things :wink:

Use KDE plasma and customize it look like gnome simple as that

@ii9, I think at this point you are getting information slung at you from everywhere. Most of it is good, but I’m sure it is overwhelming as well.

Perhaps it is time to just step back and examine what is Linux? And what are the available Desktop Environments–how to configure and use them. Separately.

First Base: Manjaro Wiki
Second Base: Using Manjaro - For Beginners
Third Base: Arch Wiki
Home: Pacman Rosetta
Overtime: Desktop Environments

regards

2 Likes