Am Freitag, 22. März 2019 07:15:28 UTC+1 schrieb Foppe de Haan:
> On Thursday, March 21, 2019 at 5:33:36 AM UTC, CooSee wrote:
> > hello,
> > 
> > i'am a long time FunToo (GenToo) User.
> > 
> > I bought a Sapphire Nitro + RX590 and thought this will work perfect with 
> > Qubes OS.
> > 
> > But there were some hiccups, because the kernel is to old including very 
> > old Firmware files.
> > 
> > I could only start installer with ' amdgpu.dpm=0 ' and everything went fine.
> > 
> > After playing around with the System, i decided to reinstall and choose XFS 
> > Filesystem (the System is noticeably faster) and just a little SWAP file 
> > (1024MB), because my System RAM is 32GB.
> > 
> > After some research i somehow managed the Problem regarding not included ' 
> > amdgpu' Driver - just installed it from an old Fedora 25 Repository - and i 
> > also downloaded current available Firmware files from Fedora 31 Repository 
> > and copied to dom0 ;-).
> > 
> > I was happy to see new Kernels, but none of them are working !
> > 
> > On the Lightdm login screen, there are some graphic glitches, just the 
> > backround and after typing my user Password, Lightdm crashs and toss me 
> > back to Login menu.
> > 
> > Only working Kernel without glitches are 4.14.74 and 4.14.103 with 
> > 'amdgpu.dpm=0 and plymouth.ignore-serial-consoles' grub option.
> > 
> > I also tried to compile a kernel with the config from my Funtoo System, but 
> > the behaviour is the same, no login possible or the Desktop just crashs 
> > after some time and i'am back to login screen.
> > 
> > I must admit that RPM based System are PITA including SystemD and XFCE is a 
> > ugly Desktop Environment - i hope MATE will be available in the Future.
> > 
> > And i also hope you switch to Debian (or maybe to GenToo) for dom0, because 
> > it is uncomplicated and APT is very easy to handle.
> > 
> > I'am wondering why all new Kernels don't work on my System - is dom0 just 
> > to old?
> > 
> > here's my System:
> > 
> > ---
> > 
> > bequiet! Silent Base 800 Black
> > 
> > MSI C236A Workstation - Intel Xeon E3-1245v5 - 32GB RAM Kingston - Sapphire 
> > Nitro+ Radeon RX590 8G
> > 
> > Samsung SSD PM961 M.2 128GB - Samsung SSD 840 EVO 120GB - Crucial m4 SSD 
> > 128GB
> > 
> > Creative Sound Blaster RX PCIe - Logitech Speaker System Z623 2.1
> > 
> > Logitech G110 Keyboard - Optical Gaming Mouse G400 
> > 
> > ---
> > 
> > thx
> 
> That seems strange. There was an issue with the firmware not supporting the 
> rx 590 properly due to some last-minute changes, but kernels 4.19 and up 
> should support it just fine, so long as you have the newer one.

thx for reply.

tried yesterday with the current latest kernel, no login possible.

Lightdm kicks me back Login screen.

here's the xsession-errors - with 4.20.3 Kernel :

---

generating cookie with syscall
generating cookie with syscall
generating cookie with syscall
generating cookie with syscall
xfce4-session: No SSH authentication agent found
gpg-agent[5670]: WARNING: "--write-env-file" is an obsolete option - it has no 
effect

(xfce4-session:5664): xfce4-session-WARNING **: gpg-agent returned no PID in 
the variables
gpg-agent[5671]: gpg-agent (GnuPG) 2.1.13 started

(xfce4-session:5664): xfce4-session-WARNING **: xfsm_manager_load_session: 
Something wrong with /home/qubees/.cache/sessions/xfce4-session-dom0:0, Does it 
exist? Permissions issue?
Screen layout change event received

** (xfdesktop:5681): WARNING **: Thumbnailer failed calling GetFlavors
sys-firewall: Sending monitor layout
asyncio: Task exception was never retrieved
future: <Task finished coro=<GUILauncher.send_monitor_layout() done, defined at 
/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py:258> 
exception=FileNotFoundError(2, 'No such file or directory')>
Traceback (most recent call last):
  File "/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step
    result = coro.send(None)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 283, in send_monitor_layout
    with open(self.guid_pidfile(vm.xid)) as pidfile:
FileNotFoundError: [Errno 2] No such file or directory: 
'/var/run/qubes/guid-running.3'
sys-net: Sending monitor layout
asyncio: Task exception was never retrieved
future: <Task finished coro=<GUILauncher.send_monitor_layout() done, defined at 
/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py:258> 
exception=FileNotFoundError(2, 'No such file or directory')>
Traceback (most recent call last):
  File "/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step
    result = coro.send(None)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 283, in send_monitor_layout
    with open(self.guid_pidfile(vm.xid)) as pidfile:
FileNotFoundError: [Errno 2] No such file or directory: 
'/var/run/qubes/guid-running.1'
wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.0.
xfce-polkit: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.0.
xfce4-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.0.

** (xss-lock:5703): CRITICAL **: X connection lost; exiting.
xfwm4: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
xfsettingsd: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.0.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 13 requests (13 known processed) with 0 events remaining.
xfce4-session: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.
xfdesktop: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.0.
Gdk-Message: qrexec-policy-agent: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :0.0.

wrapper-1.0: Fatal IO error 11 (Resource temporarily unavailable) on X server 
:0.0.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 139 requests (139 known processed) with 0 events remaining.
Can't open display :0.0
Invalid MIT-MAGIC-COOKIE-1 keyxprop:  unable to open display ':0.0'
asyncio: Task exception was never retrieved
future: <Task finished coro=<GUILauncher.start_gui() done, defined at 
/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py:238> 
exception=CalledProcessError(1, ['xprop', '-root', '-notype', 'KWIN_RUNNING'])>
Traceback (most recent call last):
  File "/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step
    result = coro.send(None)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 256, in start_gui
    yield from self.start_gui_for_vm(vm, monitor_layout=monitor_layout)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 191, in start_gui_for_vm
    guid_cmd = self.common_guid_args(vm)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 173, in common_guid_args
    guid_cmd += self.kde_guid_args(vm)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 130, in kde_guid_args
    ['xprop', '-root', '-notype', 'KWIN_RUNNING']) == \
  File "/usr/lib64/python3.5/subprocess.py", line 316, in check_output
    **kwargs).stdout
  File "/usr/lib64/python3.5/subprocess.py", line 398, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['xprop', '-root', '-notype', 
'KWIN_RUNNING']' returned non-zero exit status 1
Invalid MIT-MAGIC-COOKIE-1 keyxprop:  unable to open display ':0.0'
asyncio: Task exception was never retrieved
future: <Task finished coro=<GUILauncher.start_gui() done, defined at 
/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py:238> 
exception=CalledProcessError(1, ['xprop', '-root', '-notype', 'KWIN_RUNNING'])>
Traceback (most recent call last):
  File "/usr/lib64/python3.5/asyncio/tasks.py", line 240, in _step
    result = coro.send(None)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 256, in start_gui
    yield from self.start_gui_for_vm(vm, monitor_layout=monitor_layout)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 191, in start_gui_for_vm
    guid_cmd = self.common_guid_args(vm)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 173, in common_guid_args
    guid_cmd += self.kde_guid_args(vm)
  File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start_gui.py", 
line 130, in kde_guid_args
    ['xprop', '-root', '-notype', 'KWIN_RUNNING']) == \
  File "/usr/lib64/python3.5/subprocess.py", line 316, in check_output
    **kwargs).stdout
  File "/usr/lib64/python3.5/subprocess.py", line 398, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['xprop', '-root', '-notype', 
'KWIN_RUNNING']' returned non-zero exit status 1

(wrapper-2.0:5761): libnotify-WARNING **: Failed to connect to proxy
Gdk-Message: wrapper-2.0: Fatal IO error 9 (Bad file descriptor) on X server 
:0.0.

gpg-agent[5671]: SIGTERM received - shutting down ...
gpg-agent[5671]: gpg-agent (GnuPG) 2.1.13 stopped

---

this happens with all new Kernels after 4.14.103 <<< this works, but must use 
amdgpu.dpm=0 !

booting with >> smt=on reboot=acpi acpi_backlight=vendor

thx

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1a9b3fb5-f2b5-4710-8338-9b566447a64c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to