Results 1 to 3 of 3

Thread: Kali 2019-4 Grey Screen (no mouse) after login on Acer Aspire 3 (Ryzen 5)

  1. #1
    Join Date
    2019-Nov
    Location
    Kingston, Ontario
    Posts
    5

    Kali 2019-4 Grey Screen (no mouse) after login on Acer Aspire 3 (Ryzen 5)

    I bought a Acer Aspire 3 (A315-42-R2D9) during the Black Friday Sale. I've been trying to get kali working on using an external USB Drive (before I wipe the hard drive).
    System specs:
    Code:
       8GB Ram, 256GB SDD, Ryzen 5 3500U CPU, Vega 8 Graphics, wired and wifi network.
    Kali Live works fine on it. Both wifi and ethernet chip sets are recognized, advanced trackpad and display all seem to work fine using a 8GB kali live drive. I installed onto a 128GB lear USB 3.0 USB key. The install seemed to work fine. After I boot to the login screen, I can switch to a text terminal with Ctrl-Alt-FnKey, and log in fine. However if I log in on the graphics display, the screen does a momentary glitch and then I get a blank screen. Cntrl-Alt-FnKey does not transfer to a text terminal. I can shut down the system blind by pressing the power key, then the enter then, the power key again.

    I did a test with Ubuntu 180.4LTS using a similar process. Booted the Ubuntu Desktop Live off one USB key, installed the full desktop on a second USB key and then booted from the second USB key. The Installed ubuntu seems to works fine on the machine. Able to run terminals, talk to the network, use the browser.

    Back to Kali. After booting to the xdm login screen, switched to a text terminal. Everything seems to be normal on the text terminal. I have networkacces, and have done apt-get update, apt-get upgrade and apt-get distupgrade to ensure everything is up to date. I've also checked that the upper right pull down menu on the login screen says xfce session, although if you type something in the dialog box to login it sometimes switches back to default and the icon changes from the little circle with xfce to an icon with parallel bars.

    I've done several searches for this issue both on the forums and on the google in general. There are a lot of pages that range from 2016 to mid 2019. Some describe a black screen with a cursor, or with a mouse. A few discuss a simple black screen after login. Some of those talk about Nvidia (as opposed to amd). A few of the ones I've tried are:

    https://patrickmutuku.com/solved-kal...n-after-login/
    https://unix.stackexchange.com/quest...-fresh-install

    I've tried (on the grub line)
    nomodeest
    nouveau.modeset=0
    acpi=off

    I've also tried (based on various web pages):
    apt-get uninstall lightdm
    apt-get purge llightdm
    apt-get install lightdm

    also

    dpkg-reconfigure lightdm

    I've also tried adding a file in /etc/profiile.d/amd.sh with the line 'export AMD_DEBUG=nodcc'

    I've gone back to start and reinstalled from a new live usb onto a new USB key with the same results.

    output of lspci -k | grep -iEAA4 'via|amd'
    Code:
    05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2)
        Subsystem: Acer Incorporated [ALI] Picasso
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu
    05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller
        Subsystem: Acer Incorporated [ALI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller
    output of asmod | grep -i amd
    Code:
    edac_mce_amd           32768  0
    kvm_amd               110592  0
    ccp                   102400  1 kvm_amd
    kvm                   770048  1 kvm_amd
    amdgpu               4698112  5
    gpu_sched              36864  1 amdgpu
    i2c_algo_bit           16384  1 amdgpu
    ttm                   122880  1 amdgpu
    drm_kms_helper        212992  1 amdgpu
    drm                   552960  7 gpu_sched,drm_kms_helper,amdgpu,ttm
    mfd_core               16384  1 amdgpu
    Thehe xsession-error file:
    Code:
    Xsession: X session started for root at Sat Nov 30 11:32:47 EST 2019
    dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/0/bus
    dbus-update-activation-environment: setting DISPLAY=:0
    dbus-update-activation-environment: setting XAUTHORITY=/root/.Xauthority
    localuser:root being added to access control list
    dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
    dbus-update-activation-environment: setting USER=root
    dbus-update-activation-environment: setting LANGUAGE=en_CA:en
    dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
    dbus-update-activation-environment: setting HOME=/root
    dbus-update-activation-environment: setting DESKTOP_SESSION=lightdm-xsession
    dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
    dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/0/bus
    dbus-update-activation-environment: setting QT_QPA_PLATFORMTHEME=gtk2
    dbus-update-activation-environment: setting LOGNAME=root
    dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
    dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
    dbus-update-activation-environment: setting GDM_LANG=en_CA.utf8
    dbus-update-activation-environment: setting _JAVA_OPTIONS=-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
    dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
    dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/0
    dbus-update-activation-environment: setting DISPLAY=:0
    dbus-update-activation-environment: setting LANG=en_CA.UTF-8
    dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=lightdm-xsession
    dbus-update-activation-environment: setting XAUTHORITY=/root/.Xauthority
    dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/root
    dbus-update-activation-environment: setting SHELL=/bin/bash
    dbus-update-activation-environment: setting GDMSESSION=lightdm-xsession
    dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
    dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/0/gnupg/S.gpg-agent:0:1
    dbus-update-activation-environment: setting PWD=/root
    dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/
    /usr/bin/x-session-manager: X server already running on display :0
    xfce4-session-Message: 11:32:48.334: SSH authentication agent is already running
    gpg-agent[1075]: WARNING: "--write-env-file" is an obsolete option - it has no effect
    gpg-agent: a gpg-agent is already running - not starting a new one
    
    (xfce4-session:1010): xfce4-session-WARNING **: 11:32:48.347: gpg-agent returned no PID in the variables
    
    (wrapper-2.0:1210): Gtk-WARNING **: 11:32:49.636: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner GtkToggleButton)
    
    ** (wrapper-2.0:1222): WARNING **: 11:32:49.664: No outputs have backlight property
    
    (wrapper-2.0:1221): GLib-GIO-CRITICAL **: 11:32:49.722: g_file_new_for_path: assertion 'path != NULL' failed
    
    (wrapper-2.0:1221): GLib-GIO-CRITICAL **: 11:32:49.723: g_file_monitor_file: assertion 'G_IS_FILE (file)' failed
    
    (wrapper-2.0:1221): GLib-GObject-WARNING **: 11:32:49.723: invalid (NULL) pointer instance
    
    (wrapper-2.0:1221): GLib-GObject-CRITICAL **: 11:32:49.723: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
    
    (wrapper-2.0:1221): Gtk-WARNING **: 11:32:49.723: Attempting to add a widget with type GtkToggleButton to a container of type XfcePanelPlugin, but the widget is already inside a container of type XfcePanelPlugin, please remove the widget from its existing container first.
    
    (wrapper-2.0:1221): Gtk-WARNING **: 11:32:49.748: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner GtkToggleButton)
    
    (wrapper-2.0:1222): Gtk-WARNING **: 11:32:49.914: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner PowerManagerButton)
    
    (wrapper-2.0:1220): Gtk-WARNING **: 11:32:49.926: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node button, owner PulseaudioButton)
    
    (Thunar:1202): Gtk-CRITICAL **: 11:33:33.105: gtk_main_quit: assertion 'main_loops != NULL' failed
    X connection to :0.0 broken (explicit kill or server shutdown).
    Gdk-Message: 11:33:33.230: polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
    
    Gdk-Message: 11:33:33.234: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

  2. #2
    Join Date
    2019-Nov
    Location
    Kingston, Ontario
    Posts
    5
    Some small typos:
    128GB lexar USB 3.0 USB key
    Ubuntu 18.04LTS
    nomodesest


  3. #3
    Join Date
    2019-Nov
    Location
    Kingston, Ontario
    Posts
    5
    I connected to the ethernet at work and logged in via ssh before logging in on graphics console. kernlog, syslog and messages all start filling up with the copies of the following message from each of the cores.

    Code:
    Dec  2 19:29:01 tomKali kernel: [ 1435.231689] ------------[ cut here ]------------
    Dec  2 19:29:01 tomKali kernel: [ 1435.231786] WARNING: CPU: 0 PID: 1616 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]
    Dec  2 19:29:01 tomKali kernel: [ 1435.231788] Modules linked in: binfmt_misc nls_ascii nls_cp437 vfat fat btusb btrtl btbcm btintel uvcvideo snd_hda_codec_realtek bluetooth ath10k_pci videobuf2_vmalloc snd_hda_codec_generic videobuf2_memops snd_hda_codec_hdmi ledtrig_audio videobuf2_v4l2 ath10k_core snd_hda_intel ath videobuf2_common edac_mce_amd drbg snd_hda_codec ansi_cprng kvm_amd videodev mac80211 snd_hda_core ecdh_generic ccp joydev mc ecc snd_hwdep snd_pcm kvm acer_wmi cfg80211 sparse_keymap irqbypass libarc4 snd_timer sg efi_pstore snd serio_raw soundcore sp5100_tco rfkill hid_multitouch pcspkr k10temp wmi_bmof efivars watchdog evdev tpm_crb tpm_tis tpm_tis_core battery tpm acpi_cpufreq acer_wireless rng_core ac sunrpc efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_mod sd_mod uas usb_storage crct10dif_pclmul crc32_pclmul crc32c_intel hid_generic ghash_clmulni_intel amdgpu gpu_sched i2c_algo_bit aesni_intel ttm ahci libahci aes_x86_64 nvme drm_kms_helper xhci_pci crypto_simd libata
    Dec  2 19:29:01 tomKali kernel: [ 1435.231826]  xhci_hcd cryptd glue_helper scsi_mod drm r8169 usbcore realtek mfd_core i2c_piix4 usb_common libphy nvme_core i2c_hid hid video wmi i2c_designware_platform i2c_designware_core button
    Dec  2 19:29:01 tomKali kernel: [ 1435.231834] CPU: 0 PID: 1616 Comm: kworker/u32:2 Tainted: G        W         5.3.0-kali2-amd64 #1 Debian 5.3.9-3kali1
    Dec  2 19:29:01 tomKali kernel: [ 1435.231834] Hardware name: Acer Aspire A315-42/Sleepy_PK, BIOS V1.05 06/26/2019
    Dec  2 19:29:01 tomKali kernel: [ 1435.231841] Workqueue: events_unbound commit_work [drm_kms_helper]
    Dec  2 19:29:01 tomKali kernel: [ 1435.231918] RIP: 0010:dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]
    Dec  2 19:29:01 tomKali kernel: [ 1435.231922] Code: 83 c8 ff e9 54 1d f8 ff 48 c7 c7 70 bb d1 c0 e8 05 c1 68 f8 0f 0b 83 c8 ff e9 3e 1d f8 ff 48 c7 c7 70 bb d1 c0 e8 ef c0 68 f8 <0f> 0b 80 bb 9f 01 00 00 00 75 05 e9 22 44 f8 ff 48 8b 83 f8 02 00
    Dec  2 19:29:01 tomKali kernel: [ 1435.231925] RSP: 0018:ffff9ddbc2243af0 EFLAGS: 00010246
    Dec  2 19:29:01 tomKali kernel: [ 1435.231927] RAX: 0000000000000024 RBX: ffff8bac754c0000 RCX: 0000000000000006
    Dec  2 19:29:01 tomKali kernel: [ 1435.231927] RDX: 0000000000000000 RSI: 0000000000000082 RDI: ffff8bac88817680
    Dec  2 19:29:01 tomKali kernel: [ 1435.231928] RBP: ffff8bac754c0000 R08: 0000000000002125 R09: 0000000000000004
    Dec  2 19:29:01 tomKali kernel: [ 1435.231929] R10: 0000000000000000 R11: 0000000000000001 R12: ffff8bac7b2d01b8
    Dec  2 19:29:01 tomKali kernel: [ 1435.231929] R13: ffff8bac77f58000 R14: ffff8bac7b2d13f8 R15: 0000000000000004
    Dec  2 19:29:01 tomKali kernel: [ 1435.231930] FS:  0000000000000000(0000) GS:ffff8bac88800000(0000) knlGS:0000000000000000
    Dec  2 19:29:01 tomKali kernel: [ 1435.231931] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Dec  2 19:29:01 tomKali kernel: [ 1435.231931] CR2: 0000000000d915c8 CR3: 00000001c09ec000 CR4: 00000000003406f0
    Dec  2 19:29:01 tomKali kernel: [ 1435.231932] Call Trace:
    Dec  2 19:29:01 tomKali kernel: [ 1435.232001]  dcn10_pipe_control_lock.part.0+0x69/0x70 [amdgpu]
    Dec  2 19:29:01 tomKali kernel: [ 1435.232065]  dc_commit_updates_for_stream+0x1051/0x1440 [amdgpu]
    Dec  2 19:29:01 tomKali kernel: [ 1435.232131]  amdgpu_dm_atomic_commit_tail+0xb68/0x1c50 [amdgpu]
    Dec  2 19:29:01 tomKali kernel: [ 1435.232136]  ? load_balance+0x17d/0xb60
    Dec  2 19:29:01 tomKali kernel: [ 1435.232141]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232142]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232142]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232143]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232145]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232147]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232149]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232150]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232150]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232151]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232152]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232152]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232153]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232154]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232156]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232158]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232160]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232162]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232164]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232165]  ? _cond_resched+0x15/0x30
    Dec  2 19:29:01 tomKali kernel: [ 1435.232167]  ? wait_for_completion_timeout+0x38/0x170
    Dec  2 19:29:01 tomKali kernel: [ 1435.232167]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232168]  ? __switch_to_asm+0x34/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232169]  ? __switch_to_asm+0x40/0x70
    Dec  2 19:29:01 tomKali kernel: [ 1435.232171]  ? __switch_to+0x152/0x3e0
    Dec  2 19:29:01 tomKali kernel: [ 1435.232178]  ? commit_tail+0x3c/0x70 [drm_kms_helper]
    Dec  2 19:29:01 tomKali kernel: [ 1435.232183]  commit_tail+0x3c/0x70 [drm_kms_helper]
    Dec  2 19:29:01 tomKali kernel: [ 1435.232185]  process_one_work+0x1a2/0x340
    Dec  2 19:29:01 tomKali kernel: [ 1435.232187]  worker_thread+0x50/0x3c0
    Dec  2 19:29:01 tomKali kernel: [ 1435.232188]  kthread+0xf9/0x130
    Dec  2 19:29:01 tomKali kernel: [ 1435.232191]  ? process_one_work+0x340/0x340
    Dec  2 19:29:01 tomKali kernel: [ 1435.232194]  ? kthread_park+0x80/0x80
    Dec  2 19:29:01 tomKali kernel: [ 1435.232197]  ret_from_fork+0x22/0x40
    Dec  2 19:29:01 tomKali kernel: [ 1435.232200] ---[ end trace f677b37dcadf5188 ]---
    Dec  2 19:29:01 tomKali kernel: [ 1435.232683] [drm] pstate TEST_DEBUG_DATA: 0x37F60000
    Dec  2 19:29:01 tomKali kernel: [ 1435.232685] ------------[ cut here ]------------

Similar Threads

  1. Grey screen with working mouse after login
    By frequency in forum TroubleShooting Archive
    Replies: 6
    Last Post: 2016-08-11, 13:55
  2. Installing Kali on Acer Aspire Aspire ES1 (E11) 111M eMMC
    By th00r in forum Installing Archive
    Replies: 0
    Last Post: 2015-02-01, 03:33

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •