Peppermint OS Community Forum

Support => Advanced Topics => Topic started by: Ralph on January 31, 2018, 02:26:49 pm

Title: Desktop Issue After Boot (Solved)
Post by: Ralph on January 31, 2018, 02:26:49 pm
I
inxi -Fz
System:    Host: ag Kernel: 4.13.0-32-generic x86_64 (64 bit) Desktop: N/A
           Distro: Peppermint Eight
Machine:   Mobo: ASRock model: Z370M-ITX/ac
           Bios: American Megatrends v: P1.70 date: 01/11/2018
CPU:       Quad core Intel Core i3-8100 (-MCP-) cache: 6144 KB
           clock speeds: max: 3600 MHz 1: 3600 MHz 2: 3600 MHz 3: 3600 MHz
           4: 3600 MHz
Graphics:  Card: Intel Device 3e91
           Display Server: X.Org 1.19.5 drivers: fbdev (unloaded: vesa)
           Resolution: 1920x1080@77.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)
           GLX Version: 3.0 Mesa 17.0.2
Audio:     Card Intel Device a2f0 driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-32-generic
Network:   Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e
           IF: enp0s31f6 state: down mac: <filter>
           Card-2: Intel I211 Gigabit Network Connection driver: igb
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-3: Intel Device 24fb driver: iwlwifi
           IF: wlp3s0 state: down mac: <filter>
Drives:    HDD Total Size: 525.1GB (4.1% used)
           ID-1: /dev/sda model: Crucial_CT525MX3 size: 525.1GB
Partition: ID-1: / size: 466G used: 5.1G (2%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 16.83GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 23.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 164 Uptime: 18 min Memory: 441.5/15715.5MB
           Client: Shell (bash) inxi: 2.2.35
[close]

I have just built this computer and installed P8r. During installation all went as usual until it came time to restart. After clicking on the restart button the display told me to remove install media and press enter.  I did. After 20 plus minutes the computer did not restart. I ended up using a hard shutdown. I immediately restarted the computer and it started up as usual. I then went to Software & Update Settings and checked source code and both Canonical Partners and after that  I did all the update,upgrade, and dist-upgrade stuff. After the dist-upgrade I shut down completely. After about 10 minutes or so I restarted and that is when the issues started.
I always use auto log on. The first screen I see is a log in screen. (See picture) https://imgur.com/a/cFFF1
So I just rebooted and I got my normal desktop. At that point I added Thunderbird and edited my profile and added Gparted. That is it.
Over the next few days,every time after I completely shutdown, the next time I start the computer I get a weird desktop. Sometimes it is the log screen and other times is like this.
 https://imgur.com/a/z7iB5
It seems that all I have to do is reboot and I go to my normal desktop.
Does anyone know how to correct this situation?
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on January 31, 2018, 02:47:45 pm
According to Phoronix, Coffee Lake CPU's with the UHD 630 graphics need a kernel boot parameter (i915.alpha_support=1) adding.
https://www.phoronix.com/scan.php?page=article&item=coffee-uhd-graphics&num=1

So open a terminal and run:
Code: [Select]
gksudo xed /etc/default/grub
when it opens, find the line that reads:-
Code: [Select]
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
and change it to read:-
Code: [Select]
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"
SAVE the file and close the text editor.

Back in the terminal run:
Code: [Select]
sudo update-grub
the REBOOT to test.

Once rebooted, can you then post the output from:
Code: [Select]
inxi -Fz
again please,



The only other option is to use the 4.15 kernel which supports Coffee Lake graphics OOTB .. the problem with this is AFAIK there's no pre-compiled 4.15 kernel for Ubuntu (and derivatives) yet with all the Meltdown/Spectre patches yet .. so best to stick to the default kernel and use the boot parameter instead.
Title: Re: Desktop Issue After Boot
Post by: Ralph on January 31, 2018, 04:24:25 pm
I have done as you have prescribed. I shutdown for awhile and when I restarted P8r went to the log on screen.  (The first photo OP.) This time I logged in. It gave me my desktop so  I went right to this forum. I am going to test for awhile. I am going to shutdown and wait for a half hour or so. Just to see what P8 does.

inxi -Fz
System:    Host: ag Kernel: 4.13.0-32-generic x86_64 (64 bit) Desktop: N/A
           Distro: Peppermint Eight
Machine:   Mobo: ASRock model: Z370M-ITX/ac
           Bios: American Megatrends v: P1.70 date: 01/11/2018
CPU:       Quad core Intel Core i3-8100 (-MCP-) cache: 6144 KB
           clock speeds: max: 3600 MHz 1: 3600 MHz 2: 3600 MHz 3: 3600 MHz
           4: 3600 MHz
Graphics:  Card: Intel Device 3e91
           Display Server: X.Org 1.19.5 drivers: (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)
           GLX Version: 3.0 Mesa 17.0.2
Audio:     Card-1 Intel Device a2f0 driver: snd_hda_intel
           Card-2 C-Media CM108 Audio Controller driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.13.0-32-generic
Network:   Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e
           IF: enp0s31f6 state: down mac: <filter>
           Card-2: Intel I211 Gigabit Network Connection driver: igb
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-3: Intel Device 24fb driver: iwlwifi
           IF: wlp3s0 state: down mac: <filter>
Drives:    HDD Total Size: 525.1GB (4.1% used)
           ID-1: /dev/sda model: Crucial_CT525MX3 size: 525.1GB
Partition: ID-1: / size: 466G used: 5.1G (2%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 16.83GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 24.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 173 Uptime: 12 min Memory: 531.8/15715.5MB
           Client: Shell (bash) inxi: 2.2.35
[close]
Title: Re: Desktop Issue After Boot
Post by: Ralph on January 31, 2018, 05:12:31 pm
It worked this time. Everything seemed to load like I am use to. I am going to continue to test for a few days and if all is well I will mark this solved.
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on January 31, 2018, 05:30:26 pm
Okay please let us know how you get on :)
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 01, 2018, 07:14:48 am
Last evening I tested and I was greeted with a desktop like  the top picture.  https://imgur.com/a/z7iB5
 :( This morning when I started up the computer I was greeted with this desktop: https://imgur.com/a/Ynras
With that desktop I had no network connection. Audio did not load. Chromium home page would not start. I could not shutdown with ctrl+alt+delete, or through the menu, and I could not even use the terminal. I used the reset button to restart and upon completion all looked like one would expect.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 01, 2018, 08:47:35 am
After reading the link you provided I have searching around the net. All indications point to your fix. So I'm posting the grub you asked me to modify. Maybe you can see what I possibly mucked up.
grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
[close]

Also while looking around the net I found this under the Intel site: https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Data-File?product=126688
So I go to the file manager open the  root folder under the etc and I can't find any firmware folder. So I'll just wait for some guidance.
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 01, 2018, 09:16:47 am
That looks fine to me, try running
Code: [Select]
sudo update-pciids
then rebooting.



The intel microcode can be applied through:-

Menu > Preferences > Additional Drivers

Put a tick in "Using Processor microcode for Intel CPU's from intel-microcode (open-source)"

And click the "Apply Changes" button.

Once it's finished .. REBOOT to apply the microcode.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 01, 2018, 10:57:08 am
 :(  So I have done what you have asked yet still need to reboot after a startup to get to a normal desktop.
After doing all the above I shut down and waited about 45 minutes.
When I start I got this desktop.  https://imgur.com/a/HztrA
  The gray  box is from the network notification
   Note not all the icons in the lower left panel showed up.
Upon opening the file manager folder and moving it  I got this mess. https://imgur.com/a/Cl1sq
I then rebooted and P8r went right to the usual and customary desktop.  :'(
Do you have anymore ideas?
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 01, 2018, 11:17:23 am
What happens if you boot to the screwed up desktop, then log off/on ?

Or boot to the screwed up desktop, then run:
Code: [Select]
sudo service lightdm restart
?
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 01, 2018, 12:01:16 pm
After about 15 minutes shutdown. When I restarted I got a log on screen like this one. ( Note the imperfection)   https://imgur.com/a/cFFF1   
I logged on and it went to my desired desktop. ( note the imperfections are gone)   Remember I did not install P8r to have to log on. It should go right to the desktop.
After this is posted I will have to wait for about an hour to try sudo service lightdm restart.
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 01, 2018, 12:15:08 pm
If you're ending up at the login screen even though you chose to autologin I can only assume the x session crashed (which will dump you back at the login screen).

Is there any clues in the logs at
Code: [Select]
xed ~/.xsession-errors
or
Code: [Select]
xed /var/log/Xorg.0.log
or
Code: [Select]
xed /var/log/Xorg.1.log
?



We could try the 4.15 kernel .. but this option is risky as it's not currently fully patched against Spectre.
Title: Re: Desktop Issue After Boot
Post by: DAMIEN1307 on February 01, 2018, 12:24:40 pm
i have no idea if this will help you at all...[wait for PCNetSpec, pin or other moderator or trusted user to weigh in first before doing this]...i have bootup-manager installed on my system because i was having problems on previous mint installation...(im now all peppermint on my systems)...i too had login screen coming up at different times even though i wanted direct login...(also have this bootup-manager on my peppermints as well...sudo apt-get install bum...once installed i run it and unclick "lightdm" on startup...as well as other things i do not need at startup...that was the end of my problem...as a side note i also unclicked all samba entries, as well as cups, avahi daemons etc. etc. and all works fine here including printers and other peripherals... the only things i have enabled at startup are...rsyslog...uuidd...thermald...hddtemp...ntp...and...irqbalance...just those 7 items only and everything just works when i need it...again wait for others to weigh in here since my usage may be way different than yours
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 01, 2018, 01:55:28 pm
The Other half

Spoiler (click here to view / hide)
[     5.128] (II) Loading /usr/lib/xorg/modules/libfb.so
[     5.128] (II) Module fb: vendor="X.Org Foundation"
[     5.128]    compiled for 1.19.5, module version = 1.0.0
[     5.128]    ABI class: X.Org ANSI C Emulation, version 0.4
[     5.128] (II) Loading sub module "shadow"
[     5.128] (II) LoadModule: "shadow"
[     5.128] (II) Loading /usr/lib/xorg/modules/libshadow.so
[     5.128] (II) Module shadow: vendor="X.Org Foundation"
[     5.128]    compiled for 1.19.5, module version = 1.1.0
[     5.128]    ABI class: X.Org ANSI C Emulation, version 0.4
[     5.128] (II) UnloadModule: "fbdev"
[     5.128] (II) Unloading fbdev
[     5.128] (II) UnloadSubModule: "fbdevhw"
[     5.128] (II) Unloading fbdevhw
[     5.128] (II) UnloadModule: "vesa"
[     5.128] (II) Unloading vesa
[     5.128] (==) Depth 24 pixmap format is 32 bpp
[     5.129] (==) modeset(0): Backing store enabled
[     5.129] (==) modeset(0): Silken mouse enabled
[     5.129] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[     5.183] (==) modeset(0): DPMS enabled
[     5.183] (--) RandR disabled
[     5.186] (II) SELinux: Disabled on system
[     5.186] (II) AIGLX: Screen 0 is not DRI2 capable
[     5.186] (EE) AIGLX: reverting to software rendering
[     5.187] (II) IGLX: enabled GLX_MESA_copy_sub_buffer
[     5.188] (II) IGLX: Loaded and initialized swrast
[     5.188] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[     5.188] (II) modeset(0): Damage tracking initialized
[     5.188] (II) modeset(0): Setting screen physical size to 508 x 285
[     5.212] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[     5.212] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     5.212] (II) LoadModule: "evdev"
[     5.212] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[     5.213] (II) Module evdev: vendor="X.Org Foundation"
[     5.213]    compiled for 1.19.3, module version = 2.10.5
[     5.213]    Module class: X.Org XInput Driver
[     5.213]    ABI class: X.Org XInput driver, version 24.1
[     5.213] (II) Using input driver 'evdev' for 'Power Button'
[     5.213] (**) Power Button: always reports core events
[     5.213] (**) evdev: Power Button: Device: "/dev/input/event2"
[     5.213] (--) evdev: Power Button: Vendor 0 Product 0x1
[     5.213] (--) evdev: Power Button: Found keys
[     5.213] (II) evdev: Power Button: Configuring as keyboard
[     5.213] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[     5.213] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     5.213] (**) Option "xkb_rules" "evdev"
[     5.213] (**) Option "xkb_model" "pc105"
[     5.213] (**) Option "xkb_layout" "us"
[     5.213] (II) config/udev: Adding input device Video Bus (/dev/input/event6)
[     5.213] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[     5.214] (II) Using input driver 'evdev' for 'Video Bus'
[     5.214] (**) Video Bus: always reports core events
[     5.214] (**) evdev: Video Bus: Device: "/dev/input/event6"
[     5.214] (--) evdev: Video Bus: Vendor 0 Product 0x6
[     5.214] (--) evdev: Video Bus: Found keys
[     5.214] (II) evdev: Video Bus: Configuring as keyboard
[     5.214] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6/event6"
[     5.214] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[     5.214] (**) Option "xkb_rules" "evdev"
[     5.214] (**) Option "xkb_model" "pc105"
[     5.214] (**) Option "xkb_layout" "us"
[     5.214] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[     5.214] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     5.214] (II) Using input driver 'evdev' for 'Power Button'
[     5.214] (**) Power Button: always reports core events
[     5.214] (**) evdev: Power Button: Device: "/dev/input/event1"
[     5.214] (--) evdev: Power Button: Vendor 0 Product 0x1
[     5.214] (--) evdev: Power Button: Found keys
[     5.214] (II) evdev: Power Button: Configuring as keyboard
[     5.214] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[     5.214] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[     5.214] (**) Option "xkb_rules" "evdev"
[     5.214] (**) Option "xkb_model" "pc105"
[     5.214] (**) Option "xkb_layout" "us"
[     5.214] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[     5.214] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[     5.214] (II) Using input driver 'evdev' for 'Sleep Button'
[     5.214] (**) Sleep Button: always reports core events
[     5.214] (**) evdev: Sleep Button: Device: "/dev/input/event0"
[     5.214] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[     5.214] (--) evdev: Sleep Button: Found keys
[     5.214] (II) evdev: Sleep Button: Configuring as keyboard
[     5.214] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[     5.214] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[     5.214] (**) Option "xkb_rules" "evdev"
[     5.214] (**) Option "xkb_model" "pc105"
[     5.214] (**) Option "xkb_layout" "us"
[     5.215] (II) config/udev: Adding input device C-Media Electronics Inc.       USB PnP Sound Device (/dev/input/event5)
[     5.215] (**) C-Media Electronics Inc.       USB PnP Sound Device: Applying InputClass "evdev keyboard catchall"
[     5.215] (II) Using input driver 'evdev' for 'C-Media Electronics Inc.       USB PnP Sound Device'
[     5.215] (**) C-Media Electronics Inc.       USB PnP Sound Device: always reports core events
[     5.215] (**) evdev: C-Media Electronics Inc.       USB PnP Sound Device: Device: "/dev/input/event5"
[     5.215] (--) evdev: C-Media Electronics Inc.       USB PnP Sound Device: Vendor 0xd8c Product 0x13c
[     5.215] (--) evdev: C-Media Electronics Inc.       USB PnP Sound Device: Found keys
[     5.215] (II) evdev: C-Media Electronics Inc.       USB PnP Sound Device: Configuring as keyboard
[     5.215] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.3/0003:0D8C:013C.0002/input/input5/event5"
[     5.215] (II) XINPUT: Adding extended input device "C-Media Electronics Inc.       USB PnP Sound Device" (type: KEYBOARD, id 10)
[     5.215] (**) Option "xkb_rules" "evdev"
[     5.215] (**) Option "xkb_model" "pc105"
[     5.215] (**) Option "xkb_layout" "us"
[     5.216] (II) config/udev: Adding input device 2.4GHz 2way RF Receiver (/dev/input/event4)
[     5.216] (**) 2.4GHz 2way RF Receiver: Applying InputClass "evdev pointer catchall"
[     5.216] (**) 2.4GHz 2way RF Receiver: Applying InputClass "evdev keyboard catchall"
[     5.216] (II) Using input driver 'evdev' for '2.4GHz 2way RF Receiver'
[     5.216] (**) 2.4GHz 2way RF Receiver: always reports core events
[     5.216] (**) evdev: 2.4GHz 2way RF Receiver: Device: "/dev/input/event4"
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Vendor 0x12c9 Product 0x1001
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Found 12 mouse buttons
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Found scroll wheel(s)
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Found relative axes
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Found x and y relative axes
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Found absolute axes
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Found absolute multitouch axes
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Fake MT device detected
[     5.216] (II) evdev: 2.4GHz 2way RF Receiver: Forcing absolute x/y axes to exist.
[     5.216] (--) evdev: 2.4GHz 2way RF Receiver: Found keys
[     5.216] (II) evdev: 2.4GHz 2way RF Receiver: Configuring as mouse
[     5.216] (II) evdev: 2.4GHz 2way RF Receiver: Configuring as keyboard
[     5.216] (II) evdev: 2.4GHz 2way RF Receiver: Adding scrollwheel support
[     5.216] (**) evdev: 2.4GHz 2way RF Receiver: YAxisMapping: buttons 4 and 5
[     5.216] (**) evdev: 2.4GHz 2way RF Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[     5.216] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:12C9:1001.0001/input/input4/event4"
[     5.216] (II) XINPUT: Adding extended input device "2.4GHz 2way RF Receiver" (type: KEYBOARD, id 11)
[     5.216] (**) Option "xkb_rules" "evdev"
[     5.216] (**) Option "xkb_model" "pc105"
[     5.216] (**) Option "xkb_layout" "us"
[     5.216] (II) evdev: 2.4GHz 2way RF Receiver: initialized for relative axes.
[     5.216] (WW) evdev: 2.4GHz 2way RF Receiver: ignoring absolute axes.
[     5.216] (**) 2.4GHz 2way RF Receiver: (accel) keeping acceleration scheme 1
[     5.216] (**) 2.4GHz 2way RF Receiver: (accel) acceleration profile 0
[     5.216] (**) 2.4GHz 2way RF Receiver: (accel) acceleration factor: 2.000
[     5.216] (**) 2.4GHz 2way RF Receiver: (accel) acceleration threshold: 4
[     5.216] (II) config/udev: Adding input device 2.4GHz 2way RF Receiver (/dev/input/mouse0)
[     5.216] (II) No input driver specified, ignoring this device.
[     5.216] (II) This device may have been added with another device file.
[     5.217] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event10)
[     5.217] (II) No input driver specified, ignoring this device.
[     5.217] (II) This device may have been added with another device file.
[     5.217] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
[     5.217] (II) No input driver specified, ignoring this device.
[     5.217] (II) This device may have been added with another device file.
[     5.217] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event12)
[     5.217] (II) No input driver specified, ignoring this device.
[     5.217] (II) This device may have been added with another device file.
[     5.217] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event13)
[     5.217] (II) No input driver specified, ignoring this device.
[     5.217] (II) This device may have been added with another device file.
[     5.217] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event14)
[     5.217] (II) No input driver specified, ignoring this device.
[     5.217] (II) This device may have been added with another device file.
[     5.218] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=9 (/dev/input/event15)
[     5.218] (II) No input driver specified, ignoring this device.
[     5.218] (II) This device may have been added with another device file.
[     5.218] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=10 (/dev/input/event16)
[     5.218] (II) No input driver specified, ignoring this device.
[     5.218] (II) This device may have been added with another device file.
[     5.218] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event7)
[     5.218] (II) No input driver specified, ignoring this device.
[     5.218] (II) This device may have been added with another device file.
[     5.218] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event8)
[     5.218] (II) No input driver specified, ignoring this device.
[     5.218] (II) This device may have been added with another device file.
[     5.218] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event9)
[     5.218] (II) No input driver specified, ignoring this device.
[     5.218] (II) This device may have been added with another device file.
[     5.219] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[     5.219] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[     5.219] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[     5.219] (**) AT Translated Set 2 keyboard: always reports core events
[     5.219] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event3"
[     5.219] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[     5.219] (--) evdev: AT Translated Set 2 keyboard: Found keys
[     5.219] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[     5.219] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input3/event3"
[     5.219] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
[     5.219] (**) Option "xkb_rules" "evdev"
[     5.219] (**) Option "xkb_model" "pc105"
[     5.219] (**) Option "xkb_layout" "us"
[     5.696] (II) modeset(0): EDID vendor "SAM", prod id 3117
[     5.696] (II) modeset(0): Using EDID range info for horizontal sync
[     5.696] (II) modeset(0): Using EDID range info for vertical refresh
[     5.696] (II) modeset(0): Printing DDC gathered Modelines:
[     5.696] (II) modeset(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[     5.696] (II) modeset(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[     5.696] (II) modeset(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[     5.696] (II) modeset(0): Modeline "720x576"x0.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[     5.696] (II) modeset(0): Modeline "720x480"x0.0   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[     5.696] (II) modeset(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[     5.696] (II) modeset(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[     5.696] (II) modeset(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[     5.696] (II) modeset(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[     5.696] (II) modeset(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[     5.696] (II) modeset(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[     5.696] (II) modeset(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[     5.696] (II) modeset(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[     5.696] (II) modeset(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[     5.696] (II) modeset(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[     5.696] (II) modeset(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[     5.696] (II) modeset(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[     5.696] (II) modeset(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[     5.696] (II) modeset(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[     5.696] (II) modeset(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[     5.696] (II) modeset(0): Modeline "1280x720"x60.0   74.48  1280 1336 1472 1664  720 721 724 746 -hsync +vsync (44.8 kHz e)
[     5.696] (II) modeset(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[     5.696] (II) modeset(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[     5.696] (II) modeset(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[     5.696] (II) modeset(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
[     5.696] (II) modeset(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[     5.696] (II) modeset(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[     5.696] (II) modeset(0): Modeline "1920x1080"x0.0   74.25  1920 2558 2602 2750  1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[     5.696] (II) modeset(0): Modeline "1920x1080i"x0.0   74.25  1920 2448 2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[    15.649] (II) modeset(0): EDID vendor "SAM", prod id 3117
[    15.649] (II) modeset(0): Using hsync ranges from config file
[    15.649] (II) modeset(0): Using vrefresh ranges from config file
[    15.649] (II) modeset(0): Printing DDC gathered Modelines:
[    15.649] (II) modeset(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[    15.649] (II) modeset(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[    15.649] (II) modeset(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[    15.649] (II) modeset(0): Modeline "720x576"x0.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[    15.649] (II) modeset(0): Modeline "720x480"x0.0   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[    15.649] (II) modeset(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    15.649] (II) modeset(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    15.649] (II) modeset(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    15.649] (II) modeset(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    15.649] (II) modeset(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    15.649] (II) modeset(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    15.649] (II) modeset(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    15.649] (II) modeset(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[    15.649] (II) modeset(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    15.649] (II) modeset(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    15.649] (II) modeset(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    15.649] (II) modeset(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    15.649] (II) modeset(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    15.649] (II) modeset(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    15.649] (II) modeset(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    15.649] (II) modeset(0): Modeline "1280x720"x60.0   74.48  1280 1336 1472 1664  720 721 724 746 -hsync +vsync (44.8 kHz e)
[    15.649] (II) modeset(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[    15.649] (II) modeset(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[    15.649] (II) modeset(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[    15.649] (II) modeset(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
[    15.649] (II) modeset(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[    15.649] (II) modeset(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[    15.649] (II) modeset(0): Modeline "1920x1080"x0.0   74.25  1920 2558 2602 2750  1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
[    15.649] (II) modeset(0): Modeline "1920x1080i"x0.0   74.25  19
[close]

Title: Re: Desktop Issue After Boot
Post by: Ralph on February 01, 2018, 01:55:55 pm
xed /var/log/Xorg.0.log
[     4.857]
X.Org X Server 1.19.5
Release Date: 2017-10-12
[     4.857] X Protocol Version 11, Revision 0
[     4.857] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
[     4.857] Current Operating System: Linux ag 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64
[     4.857] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=3998c457-965c-442e-bf6a-932139b377e0 ro quiet splash i915.alpha_support=1 vt.handoff=7
[     4.857] Build Date: 24 November 2017  09:44:25AM
[     4.857] xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support)
[     4.857] Current version of pixman: 0.33.6
[     4.857]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[     4.857] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     4.857] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb  1 12:13:21 2018
[     4.857] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     4.857] (==) No Layout section.  Using the first Screen section.
[     4.857] (==) No screen section available. Using defaults.
[     4.857] (**) |-->Screen "Default Screen Section" (0)
[     4.857] (**) |   |-->Monitor "<default monitor>"
[     4.857] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[     4.857] (**) Option "BlankTime" "0"
[     4.857] (**) Option "StandbyTime" "0"
[     4.857] (**) Option "SuspendTime" "0"
[     4.857] (**) Option "OffTime" "0"
[     4.857] (==) Automatically adding devices
[     4.857] (==) Automatically enabling devices
[     4.857] (==) Automatically adding GPU devices
[     4.857] (==) Automatically binding GPU devices
[     4.857] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     4.857] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     4.857]    Entry deleted from font path.
[     4.857] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[     4.857]    Entry deleted from font path.
[     4.857] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[     4.857]    Entry deleted from font path.
[     4.857] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[     4.857]    Entry deleted from font path.
[     4.857] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[     4.857]    Entry deleted from font path.
[     4.857] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[     4.857]    Entry deleted from font path.
[     4.857] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   built-ins
[     4.857] (==) ModulePath set to "/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[     4.857] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[     4.857] (II) Loader magic: 0x563d69635e00
[     4.857] (II) Module ABI versions:
[     4.857]    X.Org ANSI C Emulation: 0.4
[     4.857]    X.Org Video Driver: 23.0
[     4.857]    X.Org XInput driver : 24.1
[     4.857]    X.Org Server Extension : 10.0
[     4.858] (++) using VT number 7

[     4.858] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     4.858] (II) xfree86: Adding drm device (/dev/dri/card0)
[     4.867] (--) PCI:*(0:0:2:0) 8086:3e91:1849:3e91 rev 0, Mem @ 0xde000000/16777216, 0xc0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[     4.867] (II) LoadModule: "glx"
[     4.867] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     4.873] (II) Module glx: vendor="X.Org Foundation"
[     4.873]    compiled for 1.19.5, module version = 1.0.0
[     4.873]    ABI class: X.Org Server Extension, version 10.0
[     4.873] (==) Matched modesetting as autoconfigured driver 0
[     4.873] (==) Matched fbdev as autoconfigured driver 1
[     4.873] (==) Matched vesa as autoconfigured driver 2
[     4.873] (==) Assigned the driver to the xf86ConfigLayout
[     4.873] (II) LoadModule: "modesetting"
[     4.873] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     4.873] (II) Module modesetting: vendor="X.Org Foundation"
[     4.873]    compiled for 1.19.5, module version = 1.19.5
[     4.873]    Module class: X.Org Video Driver
[     4.873]    ABI class: X.Org Video Driver, version 23.0
[     4.873] (II) LoadModule: "fbdev"
[     4.873] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[     4.873] (II) Module fbdev: vendor="X.Org Foundation"
[     4.873]    compiled for 1.19.3, module version = 0.4.4
[     4.873]    Module class: X.Org Video Driver
[     4.873]    ABI class: X.Org Video Driver, version 23.0
[     4.873] (II) LoadModule: "vesa"
[     4.873] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     4.873] (II) Module vesa: vendor="X.Org Foundation"
[     4.873]    compiled for 1.19.3, module version = 2.3.4
[     4.873]    Module class: X.Org Video Driver
[     4.873]    ABI class: X.Org Video Driver, version 23.0
[     4.873] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     4.873] (II) FBDEV: driver for framebuffer: fbdev
[     4.873] (II) VESA: driver for VESA chipsets: vesa
[     4.883] (II) modeset(0): using drv /dev/dri/card0
[     4.883] (WW) Falling back to old probe method for fbdev
[     4.883] (II) Loading sub module "fbdevhw"
[     4.883] (II) LoadModule: "fbdevhw"
[     4.883] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     4.883] (II) Module fbdevhw: vendor="X.Org Foundation"
[     4.883]    compiled for 1.19.5, module version = 0.0.2
[     4.883]    ABI class: X.Org Video Driver, version 23.0
[     4.883] (WW) Falling back to old probe method for vesa
[     4.883] (II) modeset(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[     4.883] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[     4.883] (==) modeset(0): RGB weight 888
[     4.883] (==) modeset(0): Default visual is TrueColor
[     4.883] (II) Loading sub module "glamoregl"
[     4.883] (II) LoadModule: "glamoregl"
[     4.883] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[     4.890] (II) Module glamoregl: vendor="X.Org Foundation"
[     4.890]    compiled for 1.19.5, module version = 1.0.0
[     4.890]    ABI class: X.Org ANSI C Emulation, version 0.4
[     4.890] (II) glamor: OpenGL accelerated X.org driver based.
[     4.936] (II) glamor: EGL version 1.4 (DRI2):
[     4.936] EGL_MESA_drm_image required.
[     4.937] (EE) modeset(0): glamor initialization failed
[     4.937] (II) modeset(0): ShadowFB: preferred YES, enabled YES
[     4.937] (II) modeset(0): Double-buffered shadow updates: off
[     5.016] (II) modeset(0): Output HDMI-1 has no monitor section
[     5.024] (II) modeset(0): Output HDMI-2 has no monitor section
[     5.024] (II) modeset(0): Output DP-1 has no monitor section
[     5.032] (II) modeset(0): Output HDMI-3 has no monitor section
[     5.110] (II) modeset(0): EDID for output HDMI-1
[     5.110] (II) modeset(0): Manufacturer: SAM  Model: c2d  Serial#: 1515864910
[     5.110] (II) modeset(0): Year: 2016  Week: 33
[     5.110] (II) modeset(0): EDID Version: 1.3
[     5.110] (II) modeset(0): Digital Display Input
[     5.110] (II) modeset(0): Max Image Size [cm]: horiz.: 48  vert.: 27
[     5.110] (II) modeset(0): Gamma: 2.20
[     5.110] (II) modeset(0): DPMS capabilities: Off
[     5.110] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[     5.111] (II) modeset(0): First detailed timing is preferred mode
[     5.111] (II) modeset(0): redX: 0.646 redY: 0.333   greenX: 0.321 greenY: 0.626
[     5.111] (II) modeset(0): blueX: 0.157 blueY: 0.061   whiteX: 0.312 whiteY: 0.329
[     5.111] (II) modeset(0): Supported established timings:
[     5.111] (II) modeset(0): 720x400@70Hz
[     5.111] (II) modeset(0): 640x480@60Hz
[     5.111] (II) modeset(0): 640x480@67Hz
[     5.111] (II) modeset(0): 640x480@72Hz
[     5.111] (II) modeset(0): 640x480@75Hz
[     5.111] (II) modeset(0): 800x600@56Hz
[     5.111] (II) modeset(0): 800x600@60Hz
[     5.111] (II) modeset(0): 800x600@72Hz
[     5.111] (II) modeset(0): 800x600@75Hz
[     5.111] (II) modeset(0): 832x624@75Hz
[     5.111] (II) modeset(0): 1024x768@60Hz
[     5.111] (II) modeset(0): 1024x768@70Hz
[     5.111] (II) modeset(0): 1024x768@75Hz
[     5.111] (II) modeset(0): 1280x1024@75Hz
[     5.111] (II) modeset(0): 1152x864@75Hz
[     5.111] (II) modeset(0): Manufacturer's mask: 0
[     5.111] (II) modeset(0): Supported standard timings:
[     5.111] (II) modeset(0): #0: hsize: 1152  vsize 864  refresh: 75  vid: 20337
[     5.111] (II) modeset(0): #1: hsize: 1280  vsize 720  refresh: 60  vid: 49281
[     5.111] (II) modeset(0): #2: hsize: 1280  vsize 800  refresh: 60  vid: 129
[     5.111] (II) modeset(0): #3: hsize: 1280  vsize 1024  refresh: 60  vid: 32897
[     5.111] (II) modeset(0): #4: hsize: 1440  vsize 900  refresh: 60  vid: 149
[     5.111] (II) modeset(0): #5: hsize: 1600  vsize 900  refresh: 60  vid: 49321
[     5.111] (II) modeset(0): #6: hsize: 1680  vsize 1050  refresh: 60  vid: 179
[     5.111] (II) modeset(0): Supported detailed timing:
[     5.111] (II) modeset(0): clock: 148.5 MHz   Image Size:  477 x 268 mm
[     5.111] (II) modeset(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[     5.111] (II) modeset(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
[     5.111] (II) modeset(0): Supported detailed timing:
[     5.111] (II) modeset(0): clock: 74.2 MHz   Image Size:  477 x 268 mm
[     5.111] (II) modeset(0): h_active: 1280  h_sync: 1390  h_sync_end 1430 h_blank_end 1650 h_border: 0
[     5.111] (II) modeset(0): v_active: 720  v_sync: 725  v_sync_end 730 v_blanking: 750 v_border: 0
[     5.111] (II) modeset(0): Ranges: V min: 50 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 175 MHz
[     5.111] (II) modeset(0): Monitor name: S22E310
[     5.111] (II) modeset(0): Supported detailed timing:
[     5.111] (II) modeset(0): clock: 74.2 MHz   Image Size:  477 x 268 mm
[     5.111] (II) modeset(0): h_active: 1280  h_sync: 1720  h_sync_end 1760 h_blank_end 1980 h_border: 0
[     5.111] (II) modeset(0): v_active: 720  v_sync: 725  v_sync_end 730 v_blanking: 750 v_border: 0
[     5.111] (II) modeset(0): Supported detailed timing:
[     5.111] (II) modeset(0): clock: 27.0 MHz   Image Size:  477 x 268 mm
[     5.111] (II) modeset(0): h_active: 720  h_sync: 732  h_sync_end 796 h_blank_end 864 h_border: 0
[     5.111] (II) modeset(0): v_active: 576  v_sync: 581  v_sync_end 586 v_blanking: 625 v_border: 0
[     5.111] (II) modeset(0): Supported detailed timing:
[     5.111] (II) modeset(0): clock: 27.0 MHz   Image Size:  477 x 268 mm
[     5.111] (II) modeset(0): h_active: 720  h_sync: 736  h_sync_end 798 h_blank_end 858 h_border: 0
[     5.111] (II) modeset(0): v_active: 480  v_sync: 489  v_sync_end 495 v_blanking: 525 v_border: 0
[     5.111] (II) modeset(0): Number of EDID sections to follow: 1
[     5.111] (II) modeset(0): EDID (in hex):
[     5.111] (II) modeset(0):    00ffffffffffff004c2d2d0c4e435a5a
[     5.111] (II) modeset(0):    211a010380301b782a9561a55552a028
[     5.111] (II) modeset(0):    0f5054bfef80714f81c0810081809500
[     5.111] (II) modeset(0):    a9c0b3000101023a801871382d40582c
[     5.111] (II) modeset(0):    4500dd0c1100001e011d007251d01e20
[     5.111] (II) modeset(0):    6e285500dd0c1100001e000000fd0032
[     5.111] (II) modeset(0):    4b1e5111000a202020202020000000fc
[     5.111] (II) modeset(0):    00533232453331300a2020202020018a
[     5.111] (II) modeset(0):    020311b14690041f13120365030c0010
[     5.111] (II) modeset(0):    00011d00bc52d01e20b8285540dd0c11
[     5.111] (II) modeset(0):    00001e8c0ad090204031200c405500dd
[     5.111] (II) modeset(0):    0c110000188c0ad08a20e02d10103e96
[     5.111] (II) modeset(0):    00dd0c11000018000000000000000000
[     5.111] (II) modeset(0):    00000000000000000000000000000000
[     5.111] (II) modeset(0):    00000000000000000000000000000000
[     5.111] (II) modeset(0):    00000000000000000000000000000050
[     5.111] (II) modeset(0): Printing probed modes for output HDMI-1
[     5.111] (II) modeset(0): Modeline "1920x1080"x60.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[     5.111] (II) modeset(0): Modeline "1920x1080"x50.0  148.50  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[     5.111] (II) modeset(0): Modeline "1920x1080"x59.9  148.35  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[     5.111] (II) modeset(0): Modeline "1680x1050"x59.9  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[     5.111] (II) modeset(0): Modeline "1600x900"x60.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync +vsync (60.0 kHz e)
[     5.111] (II) modeset(0): Modeline "1280x1024"x75.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[     5.111] (II) modeset(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[     5.111] (II) modeset(0): Modeline "1440x900"x59.9   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[     5.111] (II) modeset(0): Modeline "1280x800"x59.9   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[     5.111] (II) modeset(0): Modeline "1152x864"x75.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[     5.111] (II) modeset(0): Modeline "1280x720"x60.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[     5.111] (II) modeset(0): Modeline "1280x720"x50.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[     5.111] (II) modeset(0): Modeline "1280x720"x59.9   74.18  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[     5.111] (II) modeset(0): Modeline "1024x768"x75.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[     5.111] (II) modeset(0): Modeline "1024x768"x70.1   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[     5.111] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[     5.111] (II) modeset(0): Modeline "832x624"x74.6   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[     5.111] (II) modeset(0): Modeline "800x600"x72.2   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[     5.111] (II) modeset(0): Modeline "800x600"x75.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[     5.111] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[     5.111] (II) modeset(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[     5.111] (II) modeset(0): Modeline "720x576"x50.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[     5.111] (II) modeset(0): Modeline "720x480"x60.0   27.03  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[     5.111] (II) modeset(0): Modeline "720x480"x59.9   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[     5.111] (II) modeset(0): Modeline "640x480"x75.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[     5.111] (II) modeset(0): Modeline "640x480"x72.8   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[     5.111] (II) modeset(0): Modeline "640x480"x66.7   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[     5.111] (II) modeset(0): Modeline "640x480"x60.0   25.20  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[     5.111] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[     5.111] (II) modeset(0): Modeline "720x400"x70.1   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[     5.120] (II) modeset(0): EDID for output HDMI-2
[     5.120] (II) modeset(0): EDID for output DP-1
[     5.128] (II) modeset(0): EDID for output HDMI-3
[     5.128] (II) modeset(0): Output HDMI-1 connected
[     5.128] (II) modeset(0): Output HDMI-2 disconnected
[     5.128] (II) modeset(0): Output DP-1 disconnected
[     5.128] (II) modeset(0): Output HDMI-3 disconnected
[     5.128] (II) modeset(0): Using exact sizes for initial modes
[     5.128] (II) modeset(0): Output HDMI-1 using initial mode 1920x1080 +0+0
[     5.128] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[     5.128] (==) modeset(0): DPI set to (96, 96)
[     5.128] (II) Loading sub module "fb"
[     5.128] (II) LoadModule: "fb"
20 2448 2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[close]


This is just half
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 01, 2018, 02:06:53 pm
What you asked for
xed ~/.xsession-errors
** Message: main.vala:99: Session is Peppermint
** Message: main.vala:100: DE is LXDE
** Message: main.vala:131: log directory: /home/buz/.cache/lxsession/Peppermint
** Message: main.vala:132: log path: /home/buz/.cache/lxsession/Peppermint/run.log
[close]

So I waited an hour and upon restarting I got an all black screen with the bottom panel on the left missing the audio,network, and update icons.
On the left none of the shortcuts worked.
The menu displayed the whisker menu but nothing worked.
Using ctrl+alt+delete turned the all black screen to gray and after a time I got this screen: https://imgur.com/a/eoVGC

This request [xed /var/log/Xorg.1.log] displayed nothing

Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 01, 2018, 03:49:11 pm
Do you want instructions to try the 4.15 kernel ?



Can you also explain why you say you have to wait an hour between tests ?
(does this only happen if the computer is stone cold or something )
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 01, 2018, 05:48:02 pm
The short answer is yes.
When I start from a stone cold computer absolutely nothing responds. I have to hard shutdown. After a reboot everything work as you would expect.
When I wait just 10 mins. I usually see the the log on screen or something else as shown in the picture. When it is something else, I can access the internet,files,and the terminal. Most things work but my wallpaper doesn't show or any desktop icons until I reboot and then everything works fine. When I do get the log on and I log on everything works as you would expect.
It make no sense to me but in a nutshell that's what is happening. I wished I could explain it better.
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 01, 2018, 06:03:40 pm
Okay if you want to try the 4.15 kernel, open a terminal and run these commands in sequence.
Code: [Select]
gksudo xed /etc/default/grub
find the line that reads:-
Code: [Select]
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"
and make it read:-
Code: [Select]
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
SAVE the file and exit the text editor.

Back in the terminal run:
Code: [Select]
sudo update-grub
then:
Code: [Select]
mkdir ~/4.15-kernel
then
Code: [Select]
cd ~/4.15-kernel
then
Code: [Select]
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500_4.15.0-041500.201802011154_all.deb
then
Code: [Select]
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-headers-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb
then
Code: [Select]
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb
then
Code: [Select]
sudo apt-get install ./*.deb
if/when that command finishes .. REBOOT to test.

Then post the output from:
Code: [Select]
inxi -Fz
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 02, 2018, 07:23:36 am
This morning when I started from a cold start I got the all black screen with the bottom panel minus only the update icon. Everything seemed to work. The black screen turned to all gray after I closed Chromium. When opening the synaptic Package Manager I log in to it and gave me this error screen.  https://imgur.com/a/o5OhD

Now to the kernel update. Copied and pasted all commands, When It came time to install I got the same error as the photo above.
sudo apt-get install ./*.deb
buz@ag ~/4.15-kernel $ sudo apt-get install ./*.deb
[sudo] password for buz:
Reading package lists... Error!
E: Problem parsing dependency Depends
E: Error occurred while processing libkjsembed4 (NewVersion2)
E: Problem with MergeList /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_xenial-updates_universe_binary-i386_Packages
E: The package lists or status file could not be parsed or open
[close]


Wow! Something new. Can't seem to update anything. Just running the apt-get update command from a new CLI throws the same errors.

Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 02, 2018, 08:04:27 am
run:
Code: [Select]
sudo mv -v /var/lib/apt/lists /var/lib/apt/lists-broken
then
Code: [Select]
sudo mkdir -vp /var/lib/apt/lists/partial
now do you get any errors from:
Code: [Select]
sudo apt-get update
?



[EDIT]

I'm beginning to think there may be an underlying hardware issue here .. have you tried running memtest86+ from the GRUB menu to test the RAM ?

This corruption of the apt lists could be purely coincidental (or caused by something else), but it can't hurt to run the test.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 02, 2018, 08:54:37 am
apt-get install ./*.deb
sudo apt-get install ./*.deb
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'linux-headers-4.15.0-041500' instead of './linux-headers-4.15.0-041500_4.15.0-041500.201802011154_all.deb'
Note, selecting 'linux-headers-4.15.0-041500-generic' instead of './linux-headers-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb'
Note, selecting 'linux-image-4.15.0-041500-generic' instead of './linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb'
The following packages were automatically installed and are no longer required:
  gir1.2-networkmanager-1.0 gir1.2-nma-1.0 libido3-0.1-0
Use 'sudo apt autoremove' to remove them.
Suggested packages:
  fdutils linux-doc-4.15.0 | linux-source-4.15.0 linux-tools
The following NEW packages will be installed:
  linux-headers-4.15.0-041500 linux-headers-4.15.0-041500-generic
  linux-image-4.15.0-041500-generic
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/64.4 MB of archives.
After this operation, 326 MB of additional disk space will be used.
Get:1 /home/buz/4.15-kernel/linux-headers-4.15.0-041500_4.15.0-041500.201802011154_all.deb linux-headers-4.15.0-041500 all 4.15.0-041500.201802011154 [10.9 MB]
Get:2 /home/buz/4.15-kernel/linux-headers-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb linux-headers-4.15.0-041500-generic amd64 4.15.0-041500.201802011154 [1,049 kB]
Get:3 /home/buz/4.15-kernel/linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb linux-image-4.15.0-041500-generic amd64 4.15.0-041500.201802011154 [52.5 MB]
Selecting previously unselected package linux-headers-4.15.0-041500.
(Reading database ... 331433 files and directories currently installed.)
Preparing to unpack .../linux-headers-4.15.0-041500_4.15.0-041500.201802011154_all.deb ...
Unpacking linux-headers-4.15.0-041500 (4.15.0-041500.201802011154) ...
Selecting previously unselected package linux-headers-4.15.0-041500-generic.
Preparing to unpack .../linux-headers-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb ...
Unpacking linux-headers-4.15.0-041500-generic (4.15.0-041500.201802011154) ...
Selecting previously unselected package linux-image-4.15.0-041500-generic.
Preparing to unpack .../linux-image-4.15.0-041500-generic_4.15.0-041500.201802011154_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
Done.
Unpacking linux-image-4.15.0-041500-generic (4.15.0-041500.201802011154) ...
Setting up linux-headers-4.15.0-041500 (4.15.0-041500.201802011154) ...
Setting up linux-headers-4.15.0-041500-generic (4.15.0-041500.201802011154) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
Setting up linux-image-4.15.0-041500-generic (4.15.0-041500.201802011154) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
update-initramfs: Generating /boot/initrd.img-4.15.0-041500-generic
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.15.0-041500-generic /boot/vmlinuz-4.15.0-041500-generic
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found background image: grub-background.png
Found linux image: /boot/vmlinuz-4.15.0-041500-generic
Found initrd image: /boot/initrd.img-4.15.0-041500-generic
Found linux image: /boot/vmlinuz-4.13.0-32-generic
Found initrd image: /boot/initrd.img-4.13.0-32-generic
Found linux image: /boot/vmlinuz-4.10.0-40-generic
Found initrd image: /boot/initrd.img-4.10.0-40-generic
Adding boot menu entry for EFI firmware configuration
done
 
[close]

So as you can see I was able to update and install the new kernel.  I happened to notice these two lines. I hope that it won't be a problem.
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915

inxi -Fz
inxi -Fz
System:    Host: ag Kernel: 4.15.0-041500-generic x86_64 (64 bit) Desktop: N/A
           Distro: Peppermint Eight
Machine:   Mobo: ASRock model: Z370M-ITX/ac
           Bios: American Megatrends v: P1.70 date: 01/11/2018
CPU:       Quad core Intel Core i3-8100 (-MCP-) cache: 6144 KB
           clock speeds: max: 3600 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz
Graphics:  Card: Intel Device 3e91
           Display Server: X.Org 1.19.5 drivers: (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)
           GLX Version: 3.0 Mesa 17.0.2
Audio:     Card-1 Intel 200 Series PCH HD Audio driver: snd_hda_intel
           Card-2 C-Media CM108 Audio Controller driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.15.0-041500-generic
Network:   Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e
           IF: enp0s31f6 state: down mac: <filter>
           Card-2: Intel I211 Gigabit Network Connection driver: igb
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-3: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
           IF: wlp3s0 state: down mac: <filter>
Drives:    HDD Total Size: 525.1GB (4.3% used)
           ID-1: /dev/sda model: Crucial_CT525MX3 size: 525.1GB
Partition: ID-1: / size: 466G used: 5.9G (2%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 16.83GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 25.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 189 Uptime: 1 min Memory: 532.2/15715.3MB
           Client: Shell (bash) inxi: 2.2.35
[close]

I'm going to run the memory test now. How long would you run that?
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 02, 2018, 10:07:02 am
Okay to fix the missing firmware for the 4.15 kernel, run these commands in sequence:
Code: [Select]
cd /lib/firmware/i915
then
Code: [Select]
sudo wget https://peppermintos.info/misc/missing-firmware-for-kernel-4.15.tar.gz
then
Code: [Select]
sudo tar xvf missing-firmware-for-kernel-4.15.tar.gz
then
Code: [Select]
sudo update-initramfs -uk all
if you got no errors, the firmware is installed properly.



As for how long to run the memory test .. your call, as long as possible .. but normally errors on an unstable system will show up on the first cycle through the tests.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 02, 2018, 03:53:43 pm
Spoiler (click here to view / hide)
buz@ag ~ $ cd /lib/firmware/i915
buz@ag /lib/firmware/i915 $ sudo wget https://peppermintos.info/misc/missing-firmware-for-kernel-4.15.tar.gz
[sudo] password for buz:
Sorry, try again.
[sudo] password for buz:
--2018-02-02 14:40:00--  https://peppermintos.info/misc/missing-firmware-for-kernel-4.15.tar.gz
Resolving peppermintos.info (peppermintos.info)... 98.158.179.106
Connecting to peppermintos.info (peppermintos.info)|98.158.179.106|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 137363 (134K) [application/x-gzip]
Saving to: ‘missing-firmware-for-kernel-4.15.tar.gz’

missing-firmware-for- 100%[=======================>] 134.14K   713KB/s    in 0.2s   

2018-02-02 14:40:00 (713 KB/s) - ‘missing-firmware-for-kernel-4.15.tar.gz’ saved [137363/137363]

buz@ag /lib/firmware/i915 $ sudo tar xvf missing-firmware-for-kernel-4.15.tar.gz
kbl_guc_ver9_14.bin
bxt_guc_ver8_7.bin
buz@ag /lib/firmware/i915 $ sudo update-initramfs -uk all
update-initramfs: Generating /boot/initrd.img-4.15.0-041500-generic
update-initramfs: Generating /boot/initrd.img-4.13.0-32-generic
update-initramfs: Generating /boot/initrd.img-4.10.0-40-generic
buz@ag /lib/firmware/i915 $
[close]
The above spoiler is all the commands for the firmware install. I see no errors.
I have run the Memtest86 for two full passes over 5 hours with no errors. 
Tomorrow when I boot up I will see what happens.
BTW I could not find the grub menu with the memtest86+. Holding the shift at boot got me nowhere a half dozen times. Found a ubuntu site that said use the Esc which got me there but no memtest. Finally gave up and used the install media but instead of UEFI I just used the old usb setup.
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 02, 2018, 04:43:29 pm
Cool .. fingers crossed then.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 03, 2018, 12:06:54 pm
Well it still is not working.  :'( :(
This morning when I started up I got the all black screen. I ran in the terminal this command sudo service lightdm restart. When it restarted I saw the desktop as it should be. I thought then that maybe we are narrowing it down.  I shutdown and waited a good half hour. This time I got the all gray screen. I could get to the terminal using the keyboard but the lightdm restart command would not work. Just saying something like it timed out. I ended up doing the hard shutdown.
I have noticed that sometime during all this adventure at startup I have seen error messages flash across the boot screen. And I mean flash. There were 3 distinct flashes of messages. I captured them. The first one is here: https://imgur.com/a/2HRQ5
If you would like to see the other two I will post. They look to me to be quite similar.
Sometimes even when it loads to a workable desktop I get errors that say the panel couldn't load either the keyboard or pulse audio. Here's a snapshot: https://imgur.com/a/C7SqB

I have no idea what's going on. It seems the newer kernel is no better than the older kernel. I really hope you can come up with something.
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 03, 2018, 12:51:34 pm
Have you tried any other 16.04 based distro on this machine ?

[EDIT]

Where did you get BIOS version 1.70 ? .. this:
https://www.asrock.com/MB/Intel/Z370M-ITXac/index.asp#BIOS
only shows BIOS's up to 1.60
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 03, 2018, 01:26:33 pm
I was thinking about it but no. Since finding Peppermint I have stuck with it since 4.

That bios version came from using the bios updater over the network from within the bios itself.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 03, 2018, 02:30:35 pm
I have installed the 1.60 firmware.
inxi -Fz
System:    Host: ag Kernel: 4.15.0-041500-generic x86_64 (64 bit) Desktop: N/A
           Distro: Peppermint Eight
Machine:   Mobo: ASRock model: Z370M-ITX/ac
           Bios: American Megatrends v: P1.60 date: 11/30/2017
CPU:       Quad core Intel Core i3-8100 (-MCP-) cache: 6144 KB
           clock speeds: max: 3600 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz
Graphics:  Card: Intel Device 3e91
           Display Server: X.Org 1.19.5 drivers: (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)
           GLX Version: 3.0 Mesa 17.0.2
Audio:     Card-1 Intel 200 Series PCH HD Audio driver: snd_hda_intel
           Card-2 C-Media CM108 Audio Controller driver: USB Audio
           Sound: Advanced Linux Sound Architecture v: k4.15.0-041500-generic
Network:   Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e
           IF: enp0s31f6 state: down mac: <filter>
           Card-2: Intel I211 Gigabit Network Connection driver: igb
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-3: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
           IF: wlp3s0 state: down mac: <filter>
Drives:    HDD Total Size: 525.1GB (4.3% used)
           ID-1: /dev/sda model: Crucial_CT525MX3 size: 525.1GB
Partition: ID-1: / size: 466G used: 6.0G (2%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 16.83GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 26.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 190 Uptime: 3 min Memory: 550.9/15715.3MB
           Client: Shell (bash) inxi: 2.2.35
[close]
Do you think I should try reinstalling from scratch P8r again now that supposedly I have the right firmware for the bios?
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 03, 2018, 02:42:47 pm
Can't hurt to try ;)
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 03, 2018, 03:51:28 pm
I went to install Peppermint 8 respin. When I booted to the usb install media all those errors showed up while loading. I know for a fact I checked the Md5sum to verify the download following the directions from the Peppermint website.
I decided not to install the respin and instead installed P8. No error messages. I did all the usual and customary updates and rebooted. Again no errors. The only errors if they are errors is during the dist-upgrade I saw this:
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section table?
I don't know if it means anything or not.
I will test tomorrow to see if all is right. Here's hoping.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 06, 2018, 01:40:04 pm
Here's an update of this issue which I seem to be the only one having. Peppermint 8 reacts the same as 8 respin but without the errors when I start to boot. Following the suggestion to try other distros in no particular order I tried Ubuntu, Mint, Manjaro, and Netrunner.  All of these had the same issue I have been experiencing and all showed the same error message at boot that I was seeing in P8r.
The last distro I tried and I'm currently trying to iron out on this new Coffee Lake build is Debian 9.3-xface. It seems to work just fine. It throws the errors at startup but boots right to the desktop from a stone cold start. Why it is working I don't have a clue. The only thing I observed is the kernel is 4.09 vs. 4.13 and there is no quiet splash. I think it takes longer to boot. Probably because there is so many crap applications I don't need. I really don't like it as much as Peppermint. I have had to work much harder to get things set up. Like wifi, bluetooth,and the printer just to name a few.
I hope that in time I can switch back to Peppermint on this new build. If anyone could venture to guess why this Debian is working while the others do not I would like to know.  Also, I was just wondering if I switch back to kernel 4.09 with Peppermint if that would have worked. Again Just wondering.
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 06, 2018, 02:55:25 pm
Can you post the output from:
Code: [Select]
uname -a
and
Code: [Select]
lshw -C display
in Debian
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 06, 2018, 03:38:25 pm
your request
buz@buz:~$ su
Password:
root@buz:/home/buz# uname -a
Linux buz 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux
root@buz:/home/buz# lshw -C display
  *-display UNCLAIMED       
       description: VGA compatible controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:de000000-deffffff memory:c0000000-cfffffff ioport:f000(size=64) memory:c0000-dffff
root@buz:/home/buz#
[close]
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 06, 2018, 05:40:53 pm
Out of interest, have you got a graphics card you can put in that PC just as a test ?
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 07, 2018, 07:12:22 am
I have a Nvidia GTX 750 installed on another machine that I put there for no reason other than I had it. To put it in this SilverStone SUGO Series SG13  on this mitx board may prove to be a task. Things are somewhat cramped in there. I think it would fit but it may not.
If I except this challenge and all goes well, I assume you would want me to try Peppermint 8 respin again. True?
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 07, 2018, 10:12:22 am
Basically I'm trying to figure out if it **IS** actually a graphics and therefore kernel issue or something else entirely that we're overlooking .. so yes please.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 07, 2018, 10:23:44 am
I will get back. This will take some time. Thanks for your patience.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 07, 2018, 02:12:07 pm
I have installed the GTX 750 and reinstalled Peppermint 8 respin.  I have not installed the nvidia drivers as of yet. I wait for what you would like me to try next.

inxi -Fz
System:    Host: agstone Kernel: 4.13.0-32-generic x86_64 (64 bit) Desktop: N/A
           Distro: Peppermint Eight
Machine:   Mobo: ASRock model: Z370M-ITX/ac
           Bios: American Megatrends v: P1.60 date: 11/30/2017
CPU:       Quad core Intel Core i3-8100 (-MCP-) cache: 6144 KB
           clock speeds: max: 3600 MHz 1: 3600 MHz 2: 3600 MHz 3: 3600 MHz
           4: 3600 MHz
Graphics:  Card: NVIDIA GM107 [GeForce GTX 750]
           Display Server: X.org 1.19.5 drivers: nouveau (unloaded: fbdev,vesa)
           tty size: 86x26 Advanced Data: N/A for root
Audio:     Card-1 NVIDIA Device 0fbc driver: snd_hda_intel
           Card-2 Intel 200 Series PCH HD Audio driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.13.0-32-generic
Network:   Card-1: Intel Ethernet Connection (2) I219-V driver: e1000e
           IF: enp0s31f6 state: down mac: <filter>
           Card-2: Intel I211 Gigabit Network Connection driver: igb
           IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-3: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
           IF: wlp4s0 state: down mac: <filter>
Drives:    HDD Total Size: 525.1GB (3.9% used)
           ID-1: /dev/sda model: Crucial_CT525MX3 size: 525.1GB
Partition: ID-1: / size: 466G used: 4.1G (1%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 17.11GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 23.0C mobo: N/A gpu: 18.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 171 Uptime: 8 min Memory: 532.9/15975.5MB
           Client: Shell (sudo) inxi: 2.2.35
[close]

uname-a
uname -a
Linux agstone 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[close]
lshw
*-display               
       description: VGA compatible controller
       product: GM107 [GeForce GTX 750]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a2
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:123 memory:de000000-deffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:e000(size=128) memory:c0000-dffff
[close]
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 07, 2018, 02:14:19 pm
Are you still getting the issue(s) ?
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 07, 2018, 03:17:11 pm
I had to wait an hour and I just started it up and  :'( :( :-\ YES. Dang
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 07, 2018, 03:25:56 pm
Okay so it's not graphics .. I'll see what I can find online about problems with coffee lake and/or your motherboard in Ubuntu, but on my travels so far I'd not spotted anything :-\

Did we ever try the 4.4 kernel in Peppermint (or any other *buntu) ?
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 07, 2018, 03:51:57 pm
No. I didn't know there was such an animal.
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 07, 2018, 05:40:00 pm
Okay, what's the output from:
Code: [Select]
dpkg -l | grep 4.13.0
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 08, 2018, 06:35:33 am
grep 4.13.0
dpkg -l | grep 4.13.0
ii  linux-generic-hwe-16.04                     4.13.0.32.52                                                amd64        Complete Generic Linux kernel and headers
ii  linux-headers-4.13.0-32                     4.13.0-32.35~16.04.1                                        all          Header files related to Linux kernel version 4.13.0
ii  linux-headers-4.13.0-32-generic             4.13.0-32.35~16.04.1                                        amd64        Linux kernel headers for version 4.13.0 on 64 bit x86 SMP
ii  linux-headers-generic-hwe-16.04             4.13.0.32.52                                                amd64        Generic Linux kernel headers
ii  linux-image-4.13.0-32-generic               4.13.0-32.35~16.04.1                                        amd64        Linux kernel image for version 4.13.0 on 64 bit x86 SMP
ii  linux-image-extra-4.13.0-32-generic         4.13.0-32.35~16.04.1                                        amd64        Linux kernel extra modules for version 4.13.0 on 64 bit x86 SMP
ii  linux-image-generic-hwe-16.04               4.13.0.32.52                                                amd64        Generic Linux kernel image
ii  linux-signed-generic-hwe-16.04              4.13.0.32.52                                                amd64        Complete Signed Generic Linux kernel and headers
ii  linux-signed-image-4.13.0-32-generic        4.13.0-32.35~16.04.1                                        amd64        Signed kernel image generic
ii  linux-signed-image-generic-hwe-16.04        4.13.0.32.52                                                amd64        Signed Generic Linux kernel image
[close]

Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 08, 2018, 07:26:00 am
Okay to remove the HWE and go back to the default 16.04 kernel (4.4.0) run these commands in sequence:
(these commands are rather long so will scroll off the page to the right .. be sure to get the entire command .. also DO NOT reboot until told to do so)
Code: [Select]
sudo apt-get install linux-generic linux-signed-generic xserver-xorg xserver-xorg-core xserver-xorg-legacy xserver-xorg-video-all xserver-xorg-video-intel xserver-xorg-video-qxl xserver-xorg-input-all libgl1-mesa-dri:i386 libgl1-mesa-glx:i386
then if that command finishes without error:
Code: [Select]
sudo apt-get remove --purge linux-headers-4.13.0-32 linux-headers-4.13.0-32-generic linux-image-4.13.0-32-generic linux-image-extra-4.13.0-32-generic linux-signed-generic-hwe-16.04 linux-signed-image-4.13.0-32-generic linux-signed-image-generic-hwe-16.04
if those two commands ran without error .. REBOOT.

Once rebooted, check you're running the 4.4.0 kernel with:
Code: [Select]
uname -a
If you are, go to:-

Menu > System Tools > Synaptic Package Manager

In Synaptic, on the left hand column select the "Status" button .. select the "Not Installed (residual config)" category .. then mark all displayed packages as "Mark for Complete Removal", and click the "Apply" button.

Once those packages are gone, close Synaptic.

Back in the terminal run:
Code: [Select]
sudo apt-get install --reinstall linux-generic linux-signed-generic xserver-xorg xserver-xorg-core xserver-xorg-legacy xserver-xorg-video-all xserver-xorg-video-intel xserver-xorg-video-qxl xserver-xorg-input-all libgl1-mesa-dri:i386 libgl1-mesa-glx:i386
this will replace any config files removed previously with the correct ones.

Okay, all done, so test your computer for the issues you've been having.

If you're having no problems, post the output (if any) from:
Code: [Select]
dpkg -l | grep hwe-16.04
and
Code: [Select]
dpkg -l | grep 4.13.0
so we can see if anything was left behind that shouldn't have been.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 08, 2018, 08:07:27 am
Just a reminder, that output is from a clean install with just the usual update upgrade and dist upgrade done once. The earlier modification to the grub has not been done.
Should I put that on this install as it did nothing to help?
Which graphics card do you want me to work with before doing as you requested?
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 08, 2018, 09:01:20 am
Don't change GRUB yet

and whichever graphics card you wish .. I no longer think that's the root of the issue.
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 08, 2018, 12:02:03 pm
I removed the Nvidia card.
Followed all your instructions.
Shutdown and let it sit for over 2 hours.
When I fired it up  :) :D ;D :P
So tomorrow if all goes well I can mark this solved. Thank you so much for all your effort.
Can you link to whatever showed you this solution? I would love to read more about it.

dpkg+uname
~ $ dpkg -l | grep hwe-16.04
buz@agstone ~ $ dpkg -l | grep 4.13.0
buz@agstone ~ $ uname -a
Linux agstone 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[close]
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 08, 2018, 12:35:47 pm
Okay the output shows there's nothing to clean up.

Can you link to whatever showed you this solution? I would love to read more about it.

Sorry but there's no link .. I just noticed that you said the 4.9 kernel worked in Debian, so I wondered if there was some kind of kernel regression in the 4.13 (and possibly later) kernel series, and/or a regression in the later version of the xorg stack which is also updated by hwe-16.04. Now considering the default (non-HWE) kernel for Ubuntu 16.04 (so therefore Peppermint 7 and 8 ) is the 4.4 series, I figured lets test that kernel and xorg stack because they'll continue to get security updates automagically.

Basically we undid the changes applied by the "Hardware Enablement" track for 16.04 (hwe-16.04) as used in Peppermint 8 Respin (and Ubuntu 16.04.3, or distros based on it). So you now have Peppermint 8 built on Ubuntu 16.04 instead of 16.04.3

Sadly this "guess" at what might fix the problem doesn't identify what the actual kernel regression is, or what hardware you have that's triggering the regression :( .. but I guess it's better than nothing ?
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 09, 2018, 09:29:08 am
So it seems as though my OP is solved. I have tried it three time and it starts as one would expect.
But with one problem solved another has popped up. This motherboard has wireless built in and it won't connect. Looking in the forum under networking I found this post that looks like what I am experiencing.   https://forum.peppermintos.com/index.php/topic,5980.0.html

The solution though looks like what I removed. The spoiler shows inxi, iwconfig,and nmcli.

Spoiler (click here to view / hide)
buz@agstone ~ $ iwconfig
enp2s0    no wireless extensions.

lo        no wireless extensions.

enp0s31f6  no wireless extensions.

buz@agstone ~ $ nmcli device status
DEVICE     TYPE      STATE        CONNECTION         
enp2s0     ethernet  connected    Wired connection 2
enp0s31f6  ethernet  unavailable  --                 
lo         loopback  unmanaged    --                 
buz@agstone ~ $ inxi -Fx
System:    Host: agstone Kernel: 4.4.0-112-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: N/A Distro: Peppermint Eight
Machine:   Mobo: ASRock model: Z370M-ITX/ac
           Bios: American Megatrends v: P1.60 date: 11/30/2017
CPU:       Quad core Intel Core i3-8100 (-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28799
           clock speeds: max: 3600 MHz 1: 800 MHz 2: 799 MHz 3: 799 MHz 4: 800 MHz
Graphics:  Card: Intel Device 3e91 bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: fbdev,intel (unloaded: vesa)
           Resolution: 1920x1080@77.00hz
           GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)
           GLX Version: 3.0 Mesa 17.0.2 Direct Rendering: Yes
Audio:     Card Intel 200 Series PCH HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.4.0-112-generic
Network:   Card-1: Intel Ethernet Connection (2) I219-V
           driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6
           IF: enp0s31f6 state: down mac: 70:85:c2:60:ad:d7
           Card-2: Intel I211 Gigabit Network Connection
           driver: igb v: 5.3.0-k port: e000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:60:ad:d5
           Card-3: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] bus-ID: 03:00.0
           IF: N/A state: N/A mac: N/A
Drives:    HDD Total Size: 525.1GB (4.1% used)
           ID-1: /dev/sda model: Crucial_CT525MX3 size: 525.1GB
Partition: ID-1: / size: 466G used: 5.1G (2%) fs: ext4 dev: /dev/sda2
           ID-2: swap-1 size: 17.11GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 22.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 185 Uptime: 26 min Memory: 620.7/15721.8MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35
buz@agstone ~ $
[close]

Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 09, 2018, 10:01:19 am
Can you post the output from:
Code: [Select]
lsusb
and
Code: [Select]
lspci -vnn | grep -i net
and
Code: [Select]
iwlist scan
and
Code: [Select]
rfkill list
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 09, 2018, 11:10:50 am
lsusb
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 12c9:1001 
Bus 001 Device 003: ID 8087:0aa7 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[close]

lspci
lspci -vnn | grep -i net
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-V [8086:15b8]
   Subsystem: ASRock Incorporation Ethernet Connection (2) I219-V [1849:15b8]
02:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
   Subsystem: ASRock Incorporation I211 Gigabit Network Connection [1849:1539]
03:00.0 Network controller [0280]: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:24fb] (rev 10)
[close]

iwlist
iwlist scan
enp2s0    Interface doesn't support scanning.

lo        Interface doesn't support scanning.

enp0s31f6  Interface doesn't support scanning.
[close]

rfkill
buz@agstone ~ $ rfkill list
0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
[close]
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 09, 2018, 12:13:00 pm
Okay now we have a problem.

That network adapter insn't supported until kernel 4.6.

We could easily install that (or the 4.8) kernel but it will NOT get security updates, nor will it be patched against the Meltdown and Spectre vulnerabilities.

So looks like your decision is between an unpatched and static kernel .. or getting a new wireless adapter :(

Just as a matter on interest, can you post the output from:
Code: [Select]
dmesg | grep iwl
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 09, 2018, 12:20:14 pm
dmesg | grep iwl returns nothing.
FYI Debian network work after I added some firmware.  I found this but don't understand where they got the file from. OpenElectric?
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 09, 2018, 02:53:02 pm
The firmware on its own won't help, if it would, that last command I asked you to run would have spit out that the driver couldn't find the firmware. The problem is the kernel doesn't even contain the driver :(
Title: Re: Desktop Issue After Boot
Post by: Ralph on February 09, 2018, 03:06:37 pm
Once again thank you for all you have done. Maybe by the time Peppermint 9 comes out these issues with Coffee Lake and Intels 3168 ac wireless will be addressed. Anyway the ball is in my court.

How would you like me to post the results?  The original post was solved after all. But??? :-\
Title: Re: Desktop Issue After Boot
Post by: PCNetSpec on February 09, 2018, 03:18:29 pm
Just leave the topic open my mate, and let it slide into obscurity .. I'm sure if anyone has the same issue just searching for coffee lake will find it for them .. if not and they post, we'll know the answer now anyway :)

Quote from: Ralph
Once again thank you for all you have done.

You're most welcome Ralph :)
Title: Re: Desktop Issue After Boot
Post by: Ralph on August 21, 2018, 10:03:57 am
Since this goes way back and I thought I'd share what has happen since then. Because I could not use wifi with the solution I got here I thought I would keep looking for another distro that would work better. To make a long story short I settled on Solus Gnome. I tried the Budgie but just didn't like it. I don't know why but SG just worked. The issues I had just disappeared. Solus isn't bad but it's not Peppermint.
This week I installed Peppermint 9 and so far all those issues discussed priviously have not materialised. I really like Peppermint and I'm very pleased to be back using it on this machine.
Title: Re: Desktop Issue After Boot
Post by: scifidude79 on August 21, 2018, 10:08:22 am
Hey, thanks for the update. Have a karma point for remembering this place and returning to Peppermint.  :D
Title: Re: Desktop Issue After Boot
Post by: Slim.Fatz on August 21, 2018, 12:22:21 pm
Hi Ralph,

And a karma point from me too (same reasons)!

Regards,

-- Slim
Title: Re: Desktop Issue After Boot
Post by: Ralph on March 05, 2019, 08:50:15 am
Another update and the last. Earlier, I thought Peppermint 9 solved my original post. As it turned out it did not. When 9 started acting like 8r I was beside myself. What the heck is going on. I have figured out over these past months that booting up on this machine with this hardware setup just doesn't like cool ambient temperatures of around 50 degrees F. (10C.)  I noticed that the issue showed up again during the same months as the original post. So,because rebooting would work every time I thought I would try and delay the boot in the bios leaving the POST screen on for 20 seconds or so. It worked. Default on the POST screen was 1 second. No other computer that I store at that temperature acts like this machine. So all this is hardware related and why it's happening I'll never know.
Title: Re: Desktop Issue After Boot (Solved)
Post by: PCNetSpec on March 05, 2019, 01:34:06 pm
Weird :-\