Re: 16.04 can't get gt540m to work

[pete340]

Hi guys,
I'm sorry if this appear to many as a question already asked, I have been through a ton of posts with similar issues, and yes i'm quite new to the platform. for almost two years my 14.04 installation worked like a charm, then one failed update when system ran out of space messed up everything, so hoping to repair after resizing partitions instead of clean install I upgraded to 16.04 but my normal x windows did not come back and I'm lost now. Currently in kernel 4.10 I'm able to startx from tty1 where my booting sequence takes me. X appear to be using nouveau but the resolution is very low and I have no sound . when I tried to install manually or in graphic mode-additional drivers the result is always no display found startx fails , after purging nvidia* and reboot I can startx in low res. Surely I'm doing something or everything wrong I just cant seem to be able to figure out what. If anyone could point me in the right direction, I would very much appreciate it. At least some point to point description for novice users, how to assess what state my system is in? maybe its not the driver that needs fixing but xserver or something I'm not even aware of ?
Thanks everyone for advice in advance.
kernels 4.4.101 4.9 same situ.
systemctl graphical.target does nothing for me . which gdm nothing.

also ctrl+alt+f7 takes me to blank screen with blinking cursor, any nvidia driver after installation and reboot ends in xserver failed, after trying startx or xinit

[Bashing-om]

pete340; Hello - Welcome to the forum.

Let's take a gander at what the system thinks:
post back - Between Code Tags - the outputs of terminal commands :
code tag tutorial:
http://ubuntuforums.org/showthread.php?t=2171721&p=12776168#post12776168


sudo lshw -C display
cat /var/log/Xorg.0.log
cat /var/log/gpu-manager.log

As you can start the GUI even degraded - says the issue is within that GUI layer .



gotta start somewhere



here looks good to me

[pete340]

Hi Bashing-om,
thanks for your response



pete@pete-VPCF23P1E:~$ sudo lshw -C display
[sudo] password for pete:
*-display UNCLAIMED
description: VGA compatible controller
product: GF108M [GeForce GT 540M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list
configuration: latency=0
resources: memory:f4000000-f4ffffff memory:d0000000-dfffffff memory:e0000000-e1ffffff ioport:d000(size=128) memory:c0000-dffff



xorg log is so long i cant post it .. it throws me an error



pete@pete-VPCF23P1E:~$ cat /var/log/gpu-manager.log
log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.10.0-40-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.10.0-40-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? yes
Is fglrx loaded? no
Was fglrx unloaded? no
Is fglrx blacklisted? no
Is intel loaded? no
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is nouveau loaded? no
Is nouveau blacklisted? yes
Is fglrx kernel module available? no
Is nvidia kernel module available? no
Vendor/Device Id: 10de:df4
BusID "PCI:1@0:0:0"
Is boot vga? yes
Error: can't access /sys/bus/pci/devices/0000:01:00.0/driver
The device is not bound to any driver. Skipping...
Error : Failed to open /dev/dri
Error : Failed to open /dev/dri
Error : Failed to open /dev/dri
Error : Failed to open /dev/dri
Does it require offloading? no
last cards number = 1
Has amd? no
Has intel? no
Has nvidia? no
How many cards? 0
The number of cards has changed!
Has the system changed? Yes
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is nvidia enabled? no
Is nvidia egl enabled? no
Is fglrx enabled? no
Is mesa enabled? yes
Is mesa egl enabled? yes
Is pxpress enabled? no
Is prime enabled? no
Is prime egl enabled? no
Is nvidia available? no
Is nvidia egl available? no
Is fglrx available? no
Is fglrx-core available? no
Is mesa available? yes
Is mesa egl available? yes
Is pxpress available? no
Is prime available? no
Is prime egl available? no
System configuration has changed



xorg log as odt

[mc4man]

Maybe (for info) install inxi & run/post

inxi -Fx
Was the iGPU disabled by you (in bios/setup) or by the manufacturer?

[Bashing-om]

pete340; Well - Not


^^
As we seek additional info .
we know:


*-display UNCLAIMED

we have a problem installing the proprietary driver.



the rest of the story

[pete340]

as far as I'm aware by manufacturer, I believe the only gpu is the gt540m soldered to the MB (I might be wrong, but even in Win I only ever seen nvidia, and bios has no switch for graphics chip)




pete@pete-VPCF23P1E:~$ inxi -Fx
System: Host: pete-VPCF23P1E Kernel: 4.10.0-40-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Gnome 3.18.5 (Gtk 3.18.9-1ubuntu3.3)
Distro: Ubuntu 16.04 xenial
Machine: System: Sony (portable) product: VPCF23P1E v: C609XFE1
Mobo: Sony model: VAIO
Bios: American Megatrends v: R2150V3 date: 07/22/2011
CPU: Quad core Intel Core i7-2670QM (-HT-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 17560
clock speeds: max: 3100 MHz 1: 1699 MHz 2: 1699 MHz 3: 1699 MHz
4: 1710 MHz 5: 1532 MHz 6: 1636 MHz 7: 1638 MHz 8: 1689 MHz
Graphics: Card: NVIDIA GF108M [GeForce GT 540M] bus-ID: 01:00.0
Display Server: X.Org 1.19.3 drivers: vesa (unloaded: fbdev) FAILED: nouveau
Resolution: 1024x768@61.00hz
GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits)
GLX Version: 3.0 Mesa 17.0.7 Direct Rendering: Yes
Audio: Card-1 NVIDIA GF108 High Definition Audio Controller
bus-ID: 01:00.1
Card-2 Intel 6 Series/C200 Series Family High Definition Audio Controller
bus-ID: 00:1b.0
Network: Card-1: Qualcomm Atheros AR9485 Wireless Network Adapter
driver: ath9k bus-ID: 02:00.0
IF: wlan0 state: up mac: 94:39:e5:b0:0d:9d
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: 9000 bus-ID: 05:00.0
IF: eth0 state: down mac: f0:bf:97:e0:d7:7b
Drives: HDD Total Size: 500.1GB (84.9% used)
ID-1: /dev/sda model: Samsung_SSD_850 size: 500.1GB temp: 0C
Partition: ID-1: / size: 59G used: 8.6G (16%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 1.5G used: 1.3G (83%) fs: fuseblk dev: /dev/sda6
ID-3: swap-1 size: 4.19GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 63.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 258 Uptime: 2:10 Memory: 3074.0/16025.6MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35


not being able to install the prop. driver seemed to be the main problem to me, but my knowledge is insufficient to figure out why this keeps happening, with several versions of nvidia drivers I tried to install.. they all fail

[Bashing-om]

pete340;

Confirmed we have but the single GPU.


Secure boot ? Make sure secure boot is disabled in bios !!


Let's try and purge re-install the driver.


sudo apt purge nvidia*
sudo rm /etc/X11/xorg.conf
sudo apt update
sudo ubuntu-drivers autoinstall


autoinstall to have the system choose what it thinks best ,, where I do expect it to pick the 384 version driver.
reboot to see the effect.
---------------------------


with several versions of nvidia drivers I tried to install.. they all fail

maybe what we have here is with several versions still installed the system is all confused as to what driver to load. Take a look at what is installed:


dpkg -l | grep -i nvidia

just for curiosities sake .. as the above will clean house and install anew .



maybe yes

[pete340]

could I have uninstalled some vital component(s) for gui in my attempts? why does the boot process always take me to tty1 ?



pete@pete-VPCF23P1E:~$ dpkg -l | grep -i nvidia
ii bbswitch-dkms 0.8-3ubuntu1 amd64 Interface for toggling the power on NVIDIA Optimus video cards
ii bumblebee 3.2.1-93~trustyppa1 amd64 NVIDIA Optimus support





pete@pete-VPCF23P1E:~$ sudo apt purge nvidia*
[sudo] password for pete:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'nvidia-325-updates' for glob 'nvidia*'
Note, selecting 'nvidia-346-updates' for glob 'nvidia*'
Note, selecting 'nvidia-driver-binary' for glob 'nvidia*'
Note, selecting 'nvidia-331-dev' for glob 'nvidia*'
Note, selecting 'nvidia-304-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-384-dev' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-346-updates' for glob 'nvidia*'
Note, selecting 'nvidia-340-updates-uvm' for glob 'nvidia*'
Note, selecting 'nvidia-331-updates-uvm' for glob 'nvidia*'
Note, selecting 'nvidia-glx' for glob 'nvidia*'
Note, selecting 'nvidia-cg-toolkit' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-340-updates' for glob 'nvidia*'
Note, selecting 'nvidia-384-updates' for glob 'nvidia*'
Note, selecting 'nvidia' for glob 'nvidia*'
Note, selecting 'nvidia-driver' for glob 'nvidia*'
Note, selecting 'nvidia-367-updates' for glob 'nvidia*'
Note, selecting 'nvidia-modprobe' for glob 'nvidia*'
Note, selecting 'nvidia-texture-tools' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-340xx-vdpau-driver' for glob 'nvidia*'
Note, selecting 'nvidia-349-updates' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-686-pae' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-304-updates' for glob 'nvidia*'
Note, selecting 'nvidia-310-updates' for glob 'nvidia*'
Note, selecting 'nvidia-331-updates' for glob 'nvidia*'
Note, selecting 'nvidia-352-dev' for glob 'nvidia*'
Note, selecting 'nvidia-vdpau-driver' for glob 'nvidia*'
Note, selecting 'nvidia-346-dev' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-331-updates' for glob 'nvidia*'
Note, selecting 'nvidia-smi' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-361-updates' for glob 'nvidia*'
Note, selecting 'nvidia-313-updates' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-340xx-kernel-dkms' for glob 'nvidia*'
Note, selecting 'nvidia-334-updates' for glob 'nvidia*'
Note, selecting 'nvidia-331-uvm' for glob 'nvidia*'
Note, selecting 'nvidia-prime' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-dkms' for glob 'nvidia*'
Note, selecting 'nvidia-current-updates' for glob 'nvidia*'
Note, selecting 'nvidia-340-dev' for glob 'nvidia*'
Note, selecting 'nvidia-387-dev' for glob 'nvidia*'
Note, selecting 'nvidia-nsight' for glob 'nvidia*'
Note, selecting 'nvidia-common' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-346-updates' for glob 'nvidia*'
Note, selecting 'nvidia-352-updates' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-amd64' for glob 'nvidia*'
Note, selecting 'nvidia-current-dev' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-352-updates' for glob 'nvidia*'
Note, selecting 'nvidia-381-dev' for glob 'nvidia*'
Note, selecting 'nvidia-355-updates' for glob 'nvidia*'
Note, selecting 'nvidia-375-dev' for glob 'nvidia*'
Note, selecting 'nvidia-current' for glob 'nvidia*'
Note, selecting 'nvidia-profiler' for glob 'nvidia*'
Note, selecting 'nvidia-375-updates' for glob 'nvidia*'
Note, selecting 'nvidia-337-updates' for glob 'nvidia*'
Note, selecting 'nvidia-358-updates' for glob 'nvidia*'
Note, selecting 'nvidia-367-dev' for glob 'nvidia*'
Note, selecting 'nvidia-cuda-toolkit' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-304xx-driver' for glob 'nvidia*'
Note, selecting 'nvidia-378-updates' for glob 'nvidia*'
Note, selecting 'nvidia-340-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-319-updates' for glob 'nvidia*'
Note, selecting 'nvidia-304-dev' for glob 'nvidia*'
Note, selecting 'nvidia-331-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-visual-profiler' for glob 'nvidia*'
Note, selecting 'nvidia-persistenced' for glob 'nvidia*'
Note, selecting 'nvidia-current-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-361-dev' for glob 'nvidia*'
Note, selecting 'nvidia-settings-binary' for glob 'nvidia*'
Note, selecting 'nvidia-361-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-304' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-331' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-340' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-346' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-352' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-361' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-367' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-375' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-381' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-384' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-387' for glob 'nvidia*'
Note, selecting 'nvidia-kernel-486' for glob 'nvidia*'
Note, selecting 'nvidia-352-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-331-updates' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-352-updates' for glob 'nvidia*'
Note, selecting 'nvidia-304-updates' for glob 'nvidia*'
Note, selecting 'nvidia-340-uvm' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-340xx-driver' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-304-updates' for glob 'nvidia*'
Note, selecting 'nvidia-cuda-dev' for glob 'nvidia*'
Note, selecting 'nvidia-cuda-doc' for glob 'nvidia*'
Note, selecting 'nvidia-340-updates' for glob 'nvidia*'
Note, selecting 'nvidia-361-updates' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-dev' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-dev' for glob 'nvidia*'
Note, selecting 'nvidia-legacy-304xx-kernel-dkms' for glob 'nvidia*'
Note, selecting 'nvidia-cg-dev' for glob 'nvidia*'
Note, selecting 'nvidia-cg-doc' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-340-updates' for glob 'nvidia*'
Note, selecting 'nvidia-libopencl1-361-updates' for glob 'nvidia*'
Note, selecting 'nvidia-381-updates' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-304' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-331' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-340' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-346' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-352' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-361' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-367' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-375' for glob 'nvidia*'
Note, selecting 'nvidia-cuda-gdb' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-304' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-381' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-384' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd-387' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-310' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-313' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-319' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-325' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-331' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-334' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-337' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-340' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-343' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-346' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-349' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-352' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-355' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-358' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-304-dev' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-361' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-364' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-367' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-375' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-378' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-381' for glob 'nvidia*'
Note, selecting 'nvidia-experimental-384' for glob 'nvidia*'
Note, selecting 'nvidia-343-updates' for glob 'nvidia*'
Note, selecting 'nvidia-364-updates' for glob 'nvidia*'
Note, selecting 'nvidia-304' for glob 'nvidia*'
Note, selecting 'nvidia-310' for glob 'nvidia*'
Note, selecting 'nvidia-313' for glob 'nvidia*'
Note, selecting 'nvidia-319' for glob 'nvidia*'
Note, selecting 'nvidia-325' for glob 'nvidia*'
Note, selecting 'nvidia-331' for glob 'nvidia*'
Note, selecting 'nvidia-334' for glob 'nvidia*'
Note, selecting 'nvidia-337' for glob 'nvidia*'
Note, selecting 'nvidia-340' for glob 'nvidia*'
Note, selecting 'nvidia-343' for glob 'nvidia*'
Note, selecting 'nvidia-346' for glob 'nvidia*'
Note, selecting 'nvidia-349' for glob 'nvidia*'
Note, selecting 'nvidia-352' for glob 'nvidia*'
Note, selecting 'nvidia-355' for glob 'nvidia*'
Note, selecting 'nvidia-358' for glob 'nvidia*'
Note, selecting 'nvidia-361' for glob 'nvidia*'
Note, selecting 'nvidia-364' for glob 'nvidia*'
Note, selecting 'nvidia-367' for glob 'nvidia*'
Note, selecting 'nvidia-375' for glob 'nvidia*'
Note, selecting 'nvidia-378' for glob 'nvidia*'
Note, selecting 'nvidia-381' for glob 'nvidia*'
Note, selecting 'nvidia-384' for glob 'nvidia*'
Note, selecting 'nvidia-387' for glob 'nvidia*'
Note, selecting 'nvidia-346-updates-dev' for glob 'nvidia*'
Note, selecting 'nvidia-settings' for glob 'nvidia*'
Note, selecting 'nvidia-opencl-icd' for glob 'nvidia*'
Note, selecting 'nvidia-settings' instead of 'nvidia-settings-binary'
Package 'nvidia-libopencl1-dev' is not installed, so not removed
Package 'nvidia-libopencl1' is not installed, so not removed
Package 'nvidia-vdpau-driver' is not installed, so not removed
Package 'nvidia-legacy-340xx-vdpau-driver' is not installed, so not removed
Package 'nvidia-driver' is not installed, so not removed
Package 'nvidia-glx' is not installed, so not removed
Package 'nvidia-kernel-dkms' is not installed, so not removed
Package 'nvidia-kernel-amd64' is not installed, so not removed
Package 'nvidia-kernel-686-pae' is not installed, so not removed
Package 'nvidia-kernel-486' is not installed, so not removed
Package 'nvidia' is not installed, so not removed
Package 'nvidia-310' is not installed, so not removed
Package 'nvidia-310-updates' is not installed, so not removed
Package 'nvidia-experimental-310' is not installed, so not removed
Package 'nvidia-313' is not installed, so not removed
Package 'nvidia-313-updates' is not installed, so not removed
Package 'nvidia-experimental-313' is not installed, so not removed
Package 'nvidia-319' is not installed, so not removed
Package 'nvidia-319-updates' is not installed, so not removed
Package 'nvidia-experimental-319' is not installed, so not removed
Package 'nvidia-325' is not installed, so not removed
Package 'nvidia-325-updates' is not installed, so not removed
Package 'nvidia-experimental-325' is not installed, so not removed
Package 'nvidia-experimental-331' is not installed, so not removed
Package 'nvidia-334' is not installed, so not removed
Package 'nvidia-334-updates' is not installed, so not removed
Package 'nvidia-experimental-334' is not installed, so not removed
Package 'nvidia-337' is not installed, so not removed
Package 'nvidia-337-updates' is not installed, so not removed
Package 'nvidia-experimental-337' is not installed, so not removed
Package 'nvidia-experimental-340' is not installed, so not removed
Package 'nvidia-343' is not installed, so not removed
Package 'nvidia-343-updates' is not installed, so not removed
Package 'nvidia-experimental-343' is not installed, so not removed
Package 'nvidia-experimental-346' is not installed, so not removed
Package 'nvidia-349' is not installed, so not removed
Package 'nvidia-349-updates' is not installed, so not removed
Package 'nvidia-experimental-349' is not installed, so not removed
Package 'nvidia-experimental-352' is not installed, so not removed
Package 'nvidia-355' is not installed, so not removed
Package 'nvidia-355-updates' is not installed, so not removed
Package 'nvidia-experimental-355' is not installed, so not removed
Note, selecting 'libnvtt-bin' instead of 'nvidia-texture-tools'
Package 'nvidia-legacy-340xx-driver' is not installed, so not removed
Package 'nvidia-legacy-304xx-driver' is not installed, so not removed
Package 'nvidia-legacy-340xx-kernel-dkms' is not installed, so not removed
Package 'nvidia-legacy-304xx-kernel-dkms' is not installed, so not removed
Package 'nvidia-358' is not installed, so not removed
Package 'nvidia-358-updates' is not installed, so not removed
Package 'nvidia-experimental-358' is not installed, so not removed
Package 'nvidia-experimental-361' is not installed, so not removed
Package 'nvidia-364' is not installed, so not removed
Package 'nvidia-364-updates' is not installed, so not removed
Package 'nvidia-experimental-364' is not installed, so not removed
Package 'nvidia-367-updates' is not installed, so not removed
Package 'nvidia-experimental-367' is not installed, so not removed
Package 'nvidia-375-updates' is not installed, so not removed
Package 'nvidia-experimental-375' is not installed, so not removed
Package 'nvidia-378' is not installed, so not removed
Package 'nvidia-378-updates' is not installed, so not removed
Package 'nvidia-experimental-378' is not installed, so not removed
Package 'nvidia-381-updates' is not installed, so not removed
Package 'nvidia-experimental-381' is not installed, so not removed
Package 'nvidia-384-updates' is not installed, so not removed
Package 'nvidia-experimental-384' is not installed, so not removed
Package 'nvidia-prime' is not installed, so not removed
Package 'nvidia-340-updates-uvm' is not installed, so not removed
Package 'nvidia-346' is not installed, so not removed
Package 'nvidia-346-dev' is not installed, so not removed
Package 'nvidia-346-updates' is not installed, so not removed
Package 'nvidia-346-updates-dev' is not installed, so not removed
Package 'nvidia-352' is not installed, so not removed
Package 'nvidia-352-dev' is not installed, so not removed
Package 'nvidia-352-updates' is not installed, so not removed
Package 'nvidia-352-updates-dev' is not installed, so not removed
Package 'nvidia-361-updates' is not installed, so not removed
Package 'nvidia-361-updates-dev' is not installed, so not removed
Package 'nvidia-current-updates' is not installed, so not removed
Package 'nvidia-current-updates-dev' is not installed, so not removed
Package 'nvidia-experimental-304' is not installed, so not removed
Package 'nvidia-experimental-304-dev' is not installed, so not removed
Package 'nvidia-cg-dev' is not installed, so not removed
Package 'nvidia-cg-doc' is not installed, so not removed
Package 'nvidia-cg-toolkit' is not installed, so not removed
Package 'nvidia-cuda-dev' is not installed, so not removed
Package 'nvidia-cuda-doc' is not installed, so not removed
Package 'nvidia-cuda-gdb' is not installed, so not removed
Package 'nvidia-cuda-toolkit' is not installed, so not removed
Package 'nvidia-libopencl1-346' is not installed, so not removed
Package 'nvidia-libopencl1-346-updates' is not installed, so not removed
Package 'nvidia-libopencl1-352' is not installed, so not removed
Package 'nvidia-libopencl1-352-updates' is not installed, so not removed
Package 'nvidia-libopencl1-361-updates' is not installed, so not removed
Package 'nvidia-modprobe' is not installed, so not removed
Package 'nvidia-nsight' is not installed, so not removed
Package 'nvidia-opencl-dev' is not installed, so not removed
Package 'nvidia-opencl-icd-346' is not installed, so not removed
Package 'nvidia-opencl-icd-346-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-352' is not installed, so not removed
Package 'nvidia-opencl-icd-352-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-361-updates' is not installed, so not removed
Package 'nvidia-persistenced' is not installed, so not removed
Package 'nvidia-profiler' is not installed, so not removed
Package 'nvidia-visual-profiler' is not installed, so not removed
Package 'nvidia-361' is not installed, so not removed
Package 'nvidia-361-dev' is not installed, so not removed
Package 'nvidia-367' is not installed, so not removed
Package 'nvidia-367-dev' is not installed, so not removed
Package 'nvidia-libopencl1-367' is not installed, so not removed
Package 'nvidia-opencl-icd-361' is not installed, so not removed
Package 'nvidia-opencl-icd-367' is not installed, so not removed
Package 'nvidia-common' is not installed, so not removed
Package 'nvidia-libopencl1-361' is not installed, so not removed
Package 'nvidia-settings' is not installed, so not removed
Package 'nvidia-current' is not installed, so not removed
Package 'nvidia-current-dev' is not installed, so not removed
Package 'nvidia-304' is not installed, so not removed
Package 'nvidia-304-dev' is not installed, so not removed
Package 'nvidia-304-updates' is not installed, so not removed
Package 'nvidia-304-updates-dev' is not installed, so not removed
Package 'nvidia-331' is not installed, so not removed
Package 'nvidia-331-dev' is not installed, so not removed
Package 'nvidia-331-updates' is not installed, so not removed
Package 'nvidia-331-updates-dev' is not installed, so not removed
Package 'nvidia-libopencl1-331-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-331-updates' is not installed, so not removed
Package 'nvidia-331-updates-uvm' is not installed, so not removed
Package 'nvidia-libopencl1-331' is not installed, so not removed
Package 'nvidia-opencl-icd-331' is not installed, so not removed
Package 'nvidia-331-uvm' is not installed, so not removed
Package 'nvidia-libopencl1-304' is not installed, so not removed
Package 'nvidia-opencl-icd-304' is not installed, so not removed
Package 'nvidia-libopencl1-304-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-304-updates' is not installed, so not removed
Package 'nvidia-340' is not installed, so not removed
Package 'nvidia-340-dev' is not installed, so not removed
Package 'nvidia-libopencl1-340' is not installed, so not removed
Package 'nvidia-opencl-icd-340' is not installed, so not removed
Package 'nvidia-340-uvm' is not installed, so not removed
Package 'nvidia-340-updates' is not installed, so not removed
Package 'nvidia-340-updates-dev' is not installed, so not removed
Package 'nvidia-libopencl1-340-updates' is not installed, so not removed
Package 'nvidia-opencl-icd-340-updates' is not installed, so not removed
Package 'nvidia-375-dev' is not installed, so not removed
Package 'nvidia-375' is not installed, so not removed
Package 'nvidia-libopencl1-375' is not installed, so not removed
Package 'nvidia-opencl-icd-375' is not installed, so not removed
Package 'nvidia-381-dev' is not installed, so not removed
Package 'nvidia-381' is not installed, so not removed
Package 'nvidia-libopencl1-381' is not installed, so not removed
Package 'nvidia-opencl-icd-381' is not installed, so not removed
Package 'nvidia-384-dev' is not installed, so not removed
Package 'nvidia-384' is not installed, so not removed
Package 'nvidia-libopencl1-384' is not installed, so not removed
Package 'nvidia-opencl-icd-384' is not installed, so not removed
Package 'nvidia-387-dev' is not installed, so not removed
Package 'nvidia-387' is not installed, so not removed
Package 'nvidia-libopencl1-387' is not installed, so not removed
Package 'nvidia-opencl-icd-387' is not installed, so not removed
The following packages were automatically installed and are no longer required:
libjansson4 libxnvctrl0 screen-resolution-extra
Use 'sudo apt autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.





pete@pete-VPCF23P1E:~$ sudo rm /etc/X11/xorg.conf
rm: cannot remove '/etc/X11/xorg.conf': No such file or directory




pete@pete-VPCF23P1E:~$ sudo apt update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:2 http://gb.archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial InRelease
Get:4 http://gb.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 Metadata [62.4 kB]
Get:7 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [62.6 kB]
Get:8 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 DEP-11 Metadata [51.4 kB]
Get:9 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [80.2 kB]
Get:10 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 Metadata [307 kB]
Get:11 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 Icons [213 kB]
Get:12 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 DEP-11 Metadata [185 kB]
Get:13 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe DEP-11 64x64 Icons [261 kB]
Get:14 http://gb.archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 DEP-11 Metadata [5,888 B]
Get:15 http://gb.archive.ubuntu.com/ubuntu xenial-backports/main amd64 DEP-11 Metadata [3,328 B]
Get:16 http://gb.archive.ubuntu.com/ubuntu xenial-backports/universe amd64 DEP-11 Metadata [4,676 B]
Fetched 1,543 kB in 0s (1,584 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up-to-date.
pete@pete-VPCF23P1E:~$ sudo ubuntu-drivers autoinstall
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libcuda1-387 nvidia-opencl-icd-387 nvidia-settings
The following NEW packages will be installed
libcuda1-387 nvidia-387 nvidia-opencl-icd-387 nvidia-settings
0 to upgrade, 4 to newly install, 0 to remove and 0 not to upgrade.
Need to get 81.4 MB/82.3 MB of archives.
After this operation, 375 MB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial/main amd64 nvidia-387 amd64 387.34-0ubuntu0~gpu16.04.2 [74.5 MB]
Get:2 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial/main amd64 libcuda1-387 amd64 387.34-0ubuntu0~gpu16.04.2 [3,397 kB]
Get:3 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial/main amd64 nvidia-opencl-icd-387 amd64 387.34-0ubuntu0~gpu16.04.2 [3,493 kB]
Fetched 81.4 MB in 1min 32s (877 kB/s)
Selecting previously unselected package nvidia-387.
(Reading database ... 362000 files and directories currently installed.)
Preparing to unpack .../nvidia-387_387.34-0ubuntu0~gpu16.04.2_amd64.deb ...
Unpacking nvidia-387 (387.34-0ubuntu0~gpu16.04.2) ...
Selecting previously unselected package libcuda1-387.
Preparing to unpack .../libcuda1-387_387.34-0ubuntu0~gpu16.04.2_amd64.deb ...
Unpacking libcuda1-387 (387.34-0ubuntu0~gpu16.04.2) ...
Selecting previously unselected package nvidia-opencl-icd-387.
Preparing to unpack .../nvidia-opencl-icd-387_387.34-0ubuntu0~gpu16.04.2_amd64.deb ...
Unpacking nvidia-opencl-icd-387 (387.34-0ubuntu0~gpu16.04.2) ...
Selecting previously unselected package nvidia-settings.
Preparing to unpack .../nvidia-settings_387.22-0ubuntu0~gpu16.04.1_amd64.deb ...
Unpacking nvidia-settings (387.22-0ubuntu0~gpu16.04.1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Setting up nvidia-387 (387.34-0ubuntu0~gpu16.04.2) ...
update-alternatives: using /usr/lib/nvidia-387/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in auto mode
update-alternatives: using /usr/share/nvidia-387/glamor.conf to provide /usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode
INFO:Enable nvidia-387
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
Adding system user `nvidia-persistenced' (UID 127) ...
Adding new group `nvidia-persistenced' (GID 137) ...
Adding new user `nvidia-persistenced' (UID 127) with group `nvidia-persistenced' ...
Not creating home directory `/'.
Loading new nvidia-387-387.34 DKMS files...
First Installation: checking all kernels...
Building only for 4.10.0-40-generic
Building for architecture x86_64
Building initial module for 4.10.0-40-generic
Done.

nvidia_387:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.10.0-40-generic/updates/dkms/

nvidia_387_modeset.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.10.0-40-generic/updates/dkms/

nvidia_387_drm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.10.0-40-generic/updates/dkms/

nvidia_387_uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.10.0-40-generic/updates/dkms/

depmod....

DKMS: install completed.
Setting up libcuda1-387 (387.34-0ubuntu0~gpu16.04.2) ...
Setting up nvidia-opencl-icd-387 (387.34-0ubuntu0~gpu16.04.2) ...
Setting up nvidia-settings (387.22-0ubuntu0~gpu16.04.1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...



going to reboot, might have to purge again if I cant startx, or should i try to load previous kernell ? if this one fails ?

oh and yes, I previously realised that I had no xorg conf and could not create one .. nvidia-config did not work command not found

so apt update installed 387.34 but after reboot it went to tty1 startx failed, xserver failed again so i purged it in order to get back to the basic gui

also I could not find secureboot in bios ( passwords all clear) but i realized there is a switch for intel virtualization technology, is that to allow the intel graphics of the i7 ?

[Bashing-om]

pete340; Oh I see -

Said the blind man:


ii bumblebee


a conflict with nvidia-prime !
bumblebee is depreciated in favor of nvidia-prime.

once more with feeling.


sudo apt-get purge bumble*
sudo apt purge nvidia
sudo ubuntu-drivers autoinstall



reboot once more to see the effect.

[pete340]

blind man sees very well,already love you , purging bumble, made a world of a difference... now I'm in full hd again. Still the 387.34 that automatically installed did not work, I had to purge nvidia* as I could not start any of the older kernells either. is there something else perhaps I need to get rid of that might fight the nvidia drivers ?



pete@pete-VPCF23P1E:~$ sudo lshw -C display
[sudo] password for pete:
*-display
description: VGA compatible controller
product: GF108M [GeForce GT 540M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nouveau latency=0
resources: irq:35 memory:f4000000-f4ffffff memory:d0000000-dfffffff memory:e0000000-e1ffffff ioport:d000(size=128) memory:c0000-dffff



i guess I'm running on nouveau now? is that right ? still getting thrown into tty1 at boot and have to starx manually . is that easily fixed ?



pete@pete-VPCF23P1E:~$ dpkg -l | grep -i nvidia
ii bbswitch-dkms 0.8-3ubuntu1 amd64 Interface for toggling the power on NVIDIA Optimus video cards

[Bashing-om]

pete340; Uh Huh .

show us :


ls -al .ICEauthority .Xauthority


'startx' has limited applications ... what Desktop Environment do we have here ? xfce4 ?? .. sudo'n here is guaranteed to make root the owner of your environment . Then nope a GUI will not start .

prior to seeking elsewhere for the fault.




gotta be a reason.

[pete340]

pete@pete-VPCF23P1E:~$ ls -al .ICEauthority .Xauthority
-rwxrwxrwx 1 root root 64838 Dec 5 03:23 .ICEauthority
-rwxrwxrwx 1 root root 275 Nov 24 12:45 .Xauthority

[Bashing-om]

pete340; Uh Huh ..

root owns your desktop ! "you" do not have the access rights .

change the access to you:


sudo chown pete:pete .ICEauthority
sudo chown pete:pete .Xauthority


like unto this - mine:


sysop@x1604:~$ ls -al .ICEauthority .Xauthority
-rw------- 1 sysop sysop 5652 Dec 4 11:11 .ICEauthority
-rw------- 1 sysop sysop 50 Dec 4 11:11 .Xauthority
sysop@x1604:

where "I" am sysop in this instance.

And still .. what is the DE we are working with here ?




one step at a time --- but



making progress

[mc4man]

Try viewing this laptop as if it was a desktop machine. ( could be Ubuntu treats it as an optimus machine which won't work.
So possibly -
boot with nomodeset, then try installing nvidia drivers
or
purge out all nvidia*, the bbswitch-dkms package (used by nvidia-prime) & install the nvidia blob from the run file
(- instructions for installing from the run file are around.., do remember nouveau has to be blacklisted, ect.

I had a somewhat similar laptop (sys76), it had a desktop cpu & nvidia. As far as nvidia drivers it worked fine, as far as a desktop cpu it was a joke, (heat), so returned after 30 min. use.. I believe it used sys76 patched drivers though.

[pete340]

that didn't appear to work, or do i need to reboot
how do i know which DE do I have , I originally installed pure ubuntu 14.04 no flavours if that helps ?



pete@pete-VPCF23P1E:~$ ls -al .ICEauthority .Xauthority
-rwxrwxrwx 1 root root 64838 Dec 5 03:23 .ICEauthority
-rwxrwxrwx 1 root root 275 Nov 24 12:45 .Xauthority
pete@pete-VPCF23P1E:~$ sudo chown pete:pete .ICEauthority
[sudo] password for pete:
pete@pete-VPCF23P1E:~$ sudo chown pete:pete .Xauthority
pete@pete-VPCF23P1E:~$ ls -al .ICEauthority .Xauthority
-rwxrwxrwx 1 root root 64838 Dec 5 03:23 .ICEauthority
-rwxrwxrwx 1 root root 275 Nov 24 12:45 .Xauthority



why won't they change ownership? i tried restart, no change

[Bashing-om]

pete340; Yeah

the change will not take effect until you reboot ( in this case ) .
The display manager:
what shows:


cat /etc/X11/default-display-manager


Find out how we are to approach the desktop . be one more step in the right direction .


@ mc4man - to this time we have not seen a sign of optimus hardware. My thought is to keep this simple and finally let the logs do the talking. Your knowledge and experience is highly valued :)




'buntu



together we can

[pete340]

@mc4man (https://ubuntuforums.org/member.php?u=320715)


I purged nvidia*, haven't separately purge bbswitch-dkms, never realised Ubuntu diferentiates how it runs on laptop and desktop, while my 14.04 ran well I had the fan running a bit high sometimes, but I'm terrible with closing things so I ended up often with dozens of browser tabs and at least half a dozen other apps so can't blame the cpu for running hot



pete@pete-VPCF23P1E:~$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3

[Bashing-om]

why won't they change ownership? i tried restart, no change

do not know yet :)
maybe this is lightdm .. and root also owns " /var/run/lightdm/root/" ?? maybe else .

Maybe we got to go deeper - what returns:


ls -ld ../pete /home




sometimes I do wonder

[pete340]

@ mc4man - to this time we have not seen a sign of optimus hardware. My thought is to keep this simple and finally let the logs do the talking. Your knowledge and experience is highly valued :)



'buntu


together we can








yeah, and my knowledge is just a steap learning curve :)) kind of dancing near the edge of my unix/linux/ubuntu understanding



pete@pete-VPCF23P1E:~$ ls -ld ../pete /home
drwxrwxrwx 1 root root 4096 Nov 21 12:43 /home
drwxrwxrwx 1 root root 8192 Dec 5 04:18 ../pete


seems everything is owned by root... hmmmm what have I done , and how ?

[Bashing-om]

pete@pete-VPCF23P1E:~$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3



Hummm .. beats me .. gdm3 in 16.04 .
verify what we have here !
show us


lsb_release -a
ls -al /usr/share/xsessions/

Be amazed what I do not know . but gdm3 I expect in the 17 release series .



ain't out of the woods yet

[pete340]

I moved /home to a different partition , perhaps I should have checked the ownership afterwards ? does it need to be owned by me ?



pete@pete-VPCF23P1E:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
pete@pete-VPCF23P1E:~$ ls -al /usr/share/xsessions/
total 36
drwxr-xr-x 2 root root 4096 Nov 5 01:18 .
drwxr-xr-x 425 root root 20480 Dec 5 03:20 ..
-rw-r--r-- 1 root root 236 Feb 10 2016 gnome-classic.desktop
-rw-r--r-- 1 root root 207 Aug 22 2016 gnome.desktop
-rw-r--r-- 1 root root 204 Aug 22 2016 ubuntu.desktop

[Bashing-om]

pete@pete-VPCF23P1E:~$ ls -ld ../pete /home
drwxrwxrwx 1 root root 4096 Nov 21 12:43 /home
drwxrwxrwx 1 root root 8192 Dec 5 04:18 ../pete


seems everything is owned by root... hmmmm what have I done , and how ?

wait for the postings to settle out .. and we go chmod'n again and get your /home to you .



may take a bit .. but we will in the end ,,, we will we will :)

[pete340]

I may have installed gdm3 by mistake trying various and random 'fixes' from other posts .. vaguely recall something not sure


wait for the postings to settle out .. and we go chmod'n again and get your /home to you .


may take a bit .. but we will in the end ,,, we will we will :)



I appreciate you taking your time to untangle this mess I seem to have created

[Bashing-om]

pete340; Ho Kay ..

We have 3 desktops installed .. still awaiting confirmation of the release:


lsb_release -a


and then we do some more checking .



get our ducks in a row

[pete340]

pete@pete-VPCF23P1E:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

[Bashing-om]

pete340; K ..

next up is to get your /home permissions corrected:


sudo chmod -R a+rwX,o-w /home/$USER

where:
All subdirectories will be marked rwx for user, group, and others. The big "X" will also not make files executable unless they were executable to begin with. There is no way to reproduce this using octal notation. The big "X" will make folders 777 and files 666 except those files that were marked as executable to begin with.
chmod'ing with an odd number in octal mode isn't smart enough to differentiate between a file and folder and makes everything executable; so in this instance we DO NOT do the octal thing to effect permissions.

re-set .ICEauthority and .Xauthority to "you" .

Get out of your mind that 'startx' to start the display is of any value to you in this use case .
16.04 is systemd and the command to start the display from TTY will be something like:


sudo systemctl start lightdm ##unity DE
sudo systemctl start gdm ## classic gnome DE
sudo systemctl start gdm3 ## new gnome DE
sudo systemctl start graphical.target ## what is set for default


reboot to see the effect .. with the thought that we may have yet to reconfigure the display manager . Of the 3 DMs that you have which do you want as the default ?



see where we go from here :)

[pete340]

pete@pete-VPCF23P1E:~$ sudo chmod -R a+rwX,o-w /home/$USER
[sudo] password for pete:
Sorry, try again.
[sudo] password for pete:
pete@pete-VPCF23P1E:~$ sudo chown pete:pete .ICEauthority
pete@pete-VPCF23P1E:~$ sudo chown pete:pete .Xauthority
pete@pete-VPCF23P1E:~$ ls -al .ICEauthority .Xauthority
-rwxrwxrwx 1 root root 64838 Dec 5 04:18 .ICEauthority
-rwxrwxrwx 1 root root 275 Nov 24 12:45 .Xauthority
pete@pete-VPCF23P1E:~$ sudo systemctl start lightdm ##unity DE
Failed to start lightdm.service: Unit lightdm.service not found.
pete@pete-VPCF23P1E:~$ sudo systemctl start gdm ## classic gnome DE
pete@pete-VPCF23P1E:~$ sudo systemctl start gdm3 ## new gnome DE
pete@pete-VPCF23P1E:~$ sudo systemctl start graphical.target ## what is set for default



reboot still goes to tty1 startx takes me back to gui :(

not sure about which dm to want , I guess the one that is most likely to work :D

[Bashing-om]

reboot still goes to tty1 startx takes me back to gui :(

How many times do I have to say do not do startx ??
In your case it does not do what you think it does . Have a read :


cat /usr/bin/startx


I can accept that doing the startup command startx in your environment does mess up the permissions.

Back up a bit and see what we now have:


ls -ld ../pete /home


see what we have here . Once we can set the proper permissions then we reconfigure the display manager .



we can do this

[pete340]

sorry I dont know how else to get into a graphic mode than startx.. can I just start firefox without startx ?



pete@pete-VPCF23P1E:~$ ls -ld ../pete /home
drwxrwxrwx 1 root root 4096 Nov 21 12:43 /home
drwxrwxrwx 1 root root 8192 Dec 5 06:15 ../pete

[Bashing-om]

pete340; Morning -

Let's address:


can I just start firefox without startx ?

as the 1st priority.

How one starts the display depends on which manager is employed in the desktop.

verify presently the display-manager. Post back:


cat /etc/X11/default-display-manager


Then I pass a command that "should" start the desktop from terminal.

When booting, what do you boot to ? To the login screen and from there you activate a console interface ( ctl+alt+F1 ) ?
Or are there deeper problems than just the GUI ?
//
While on my mind; how are you restarting the system when these permissions are re-set properly ?
from terminal the command:


systemctl reboot

will serve nicely.

To shut down from terminal:


systemctl poweroff





which way did he go, George

[pete340]

pete@pete-VPCF23P1E:~$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3


I have been restarting with either the restart button in the gui, or reboot from terminal.. I'll use systemctl reboot from now on... when I reboot, the system goes straight to tty1 login: and then password straight away , no graphics at all. obviously it shows loading all the bits and statuses mostly OK.
if i try ctrl+alt+f7 then i only get something like several lines of nubers followed with '.....nv50_base_image_set ' and '...nv50_base_update' .. cant enter anything

ah and Hi Bashing-om, thanks for comming back to me

[Bashing-om]

pete@pete-VPCF23P1E:~$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3


I have been restarting with either the restart button in the gui, or reboot from terminal.. I'll use systemctl reboot from now on... when I reboot, the system goes straight to tty1 login: and then password straight away , no graphics at all. obviously it shows loading all the bits and statuses mostly OK.
if i try ctrl+alt+f7 then i only get something like several lines of nubers followed with '.....nv50_base_image_set ' and '...nv50_base_update' .. cant enter anything

ah and Hi Bashing-om, thanks for comming back to me

pete340; Hey -

In this for the long haul; long as your patience holds out .

OK, let's prepare to re-install the unity desktop - as you can not even get to the login screen. 1st order is to get these permissions set correctly for "you" .
Now I have to question that pete is that primary account that has sudo privileges . Maybe pete not the primary is why the permissions do not change ?

show:


egrep ':[0-9]{4}:' /etc/passwd
getent passwd pete


again

gots to be a reason

[pete340]

pete@pete-VPCF23P1E:~$ egrep ':[0-9]{4}:' /etc/passwd
pete:x:1000:1000:pete,,,:/home/pete:/bin/bash

pete@pete-VPCF23P1E:~$ getent passwd pete
pete:x:1000:1000:pete,,,:/home/pete:/bin/bash


i think the reason is mostly me experimenting with a little broken system (after update fail due to no space) breaking it more with non systematic aproach.. It is hard to admit to myself that this system is far more complex and takes longer to master than what ms ever released, i was allways able to fix those.

[Bashing-om]

pete340; Uh Huh ...

I am convinced that pete is what is . So we proceed and try try again.

As to "far more complex and takes longer" .. well for sure linux is different and does take a spell to learn and/or adjust. It is, however. open and you have full access to the operating system . It is yours to do with as you wish and can .

OK .. onward with the permissions issue.

ONLY run


sudo chmod -R a+rwX,o-w /home/pete

as a variation where 'pete' is explicitly declared .
reboot

And now what, upon the coming back up, shows for permissions ?


ls -ld ../pete /home
ls -al /home/pete/


keep in mind we have to get "you" access to your user account before we can do anything else.



one step at a time

[pete340]

did the chmod from graphic interface as well as tty1 straight after reboot .. not sure which permissions are the ones we need at the mo ..



pete@pete-VPCF23P1E:~$ ls -ld ../pete /home
drwxrwxrwx 1 root root 4096 Nov 21 12:43 /home
drwxrwxrwx 1 root root 8192 Dec 6 00:20 ../pete
pete@pete-VPCF23P1E:~$ ls -al /home/pete/
total 719
drwxrwxrwx 1 root root 8192 Dec 6 00:20 .
drwxrwxrwx 1 root root 4096 Nov 21 12:43 ..
drwxrwxrwx 1 root root 0 Nov 23 2015 .adobe
-rwxrwxrwx 1 root root 12790 Dec 6 00:12 .bash_history
-rwxrwxrwx 1 root root 220 Nov 22 2015 .bash_logout
-rwxrwxrwx 1 root root 3637 Nov 22 2015 .bashrc
drwxrwxrwx 1 root root 4096 Dec 6 00:20 .cache
drwxrwxrwx 1 root root 0 Nov 22 2015 .compiz
drwxrwxrwx 1 root root 8192 Nov 24 15:54 .config
drwxrwxrwx 1 root root 0 Jul 3 2016 .dbus
drwxrwxrwx 1 root root 0 Apr 25 2017 deja-dup
drwxrwxrwx 1 root root 4096 Oct 5 20:28 Desktop
-rwxrwxrwx 1 root root 25 Apr 24 2016 .dmrc
drwxrwxrwx 1 root root 4096 Jun 13 2016 Documents
drwxrwxrwx 1 root root 0 Jul 25 2016 .dosbox
drwxrwxrwx 1 root root 28672 Dec 5 02:04 Downloads
-rwxrwxrwx 1 root root 3768 Nov 23 2015 .drirc
drwxrwxrwx 1 root root 4096 Nov 24 09:36 .dropbox
drwxrwxrwx 1 root root 0 Jun 26 20:17 .dropbox-dist
-rwxrwxrwx 1 root root 8980 Nov 22 2015 examples.desktop
drwxrwxrwx 1 root root 4096 Aug 26 12:11 .fotoxx
-rwxrwxrwx 1 root root 226 Nov 5 02:50 .fuse_hidden0000002000000015
-rwxrwxrwx 1 root root 69 Jun 28 16:15 .gammurc
drwxrwxrwx 1 root root 0 Dec 6 00:20 .gconf
drwxrwxrwx 1 root root 4096 Sep 22 09:12 .gimp-2.8
-rwxrwxrwx 1 root root 0 Dec 5 13:34 .gksu.lock
drwxrwxrwx 1 root root 0 Feb 17 2016 .gnome
drwxrwxrwx 1 root root 0 Nov 14 2016 .gnome2
drwxrwxrwx 1 root root 0 Nov 14 2016 .gnome2_private
drwxrwxrwx 1 root root 0 Jul 3 22:34 .gnome-commander
drwxrwxrwx 1 root root 4096 Nov 14 21:21 .gnupg
drwxrwxrwx 1 root root 0 Aug 26 2016 GNUstep
drwxrwxrwx 1 root root 0 Jun 26 11:38 .gphoto
drwxrwxrwx 1 root root 0 Oct 23 22:38 .gstreamer-0.10
-rwxrwxrwx 1 root root 958 Jan 22 2017 .gtk-recordmydesktop
drwxrwxrwx 1 root root 0 May 25 2017 .gvfs
drwxrwxrwx 1 root root 0 Feb 7 2017 .hplip
-rwxrwxrwx 1 root root 64838 Dec 6 00:20 .ICEauthority
drwxrwxrwx 1 root root 0 Sep 15 2016 .java
drwxrwxrwx 1 root root 0 Jun 28 2016 .kde
drwxrwxrwx 1 root root 4096 Sep 15 2016 .latexdraw
drwxrwxrwx 1 root root 0 Nov 22 2015 .local
drwxrwxrwx 1 root root 0 Nov 23 2015 .macromedia
drwxrwxrwx 1 root root 0 Nov 19 21:10 .mozilla
drwxrwxrwx 1 root root 0 Nov 22 2015 Music
drwxrwxrwx 1 root root 0 Nov 6 13:33 .nano
drwxrwxrwx 1 root root 0 Nov 23 2015 .nv
-rwxrwxrwx 1 root root 477 Nov 24 13:27 .nvidia-settings-rc
drwxrwxrwx 1 root root 4096 Nov 23 16:54 Pictures
drwxrwxrwx 1 root root 0 Feb 16 2016 .pki
-rwxrwxrwx 1 root root 675 Nov 22 2015 .profile
drwxrwxrwx 1 root root 0 Sep 15 2016 Public
drwxrwxrwx 1 root root 4096 Sep 3 22:54 .Skype
drwxrwxrwx 1 root root 0 Nov 14 21:18 .ssh
-rwxrwxrwx 1 root root 0 Nov 5 13:05 .sudo_as_admin_successful
drwxrwxrwx 1 root root 0 Nov 22 2015 Templates
drwxrwxrwx 1 root root 0 Oct 24 22:59 The.Big.Bang.Theory.S09E19.720p.HDTV.X264-DIMENSION[ettv]
drwxrwxrwx 1 root root 0 Sep 15 2016 .thumbnails
drwxrwxrwx 1 root root 4096 Mar 12 2016 .thunderbird
drwxrwxrwx 1 root root 0 Nov 22 2015 Videos
-rwxrwxrwx 1 root root 753 Jun 28 16:23 .Wammu
-rwxrwxrwx 1 root root 275 Nov 24 12:45 .Xauthority
-rwxrwxrwx 1 root root 2522 Nov 6 21:34 xorg.conf.new
-rwxrwxrwx 1 root root 500201 Dec 6 00:20 .xsession-errors
-rwxrwxrwx 1 root root 719 Nov 3 17:09 .xsession-errors.old
-rwxrwxrwx 1 root root 8223 Aug 28 02:09 zamer.odt



I tried at tty1 right afterr sysctl reboot:


start service gdm3

the response said something like:
start: Name "com.Ubuntu.Upstart" does not exist
not sure that's relevant to anything, just remembered seing the service start command somewhere.. perhaps wrong syntax

[Bashing-om]

pete340; Ouch ..

Still with root owning your home and the .ICEauthotity/.Xauthority files . Can not get to far like this ./ I am at a loss to explain and I am calling in some better help .



I can do that much

[pete340]

ok Bashing-om, thanks for that, gotta go offline now, have a flight to catch in few hours. hope someone will be able to chip in. I'd really like to get it working again without a fresh install

[Bashing-om]

pete340; Hey -

After scratching our heads on this permission issue we have 2 conclusions.
1) not a linux file system on the target.
show us:


sudo fdisk -lu


2) file system is mounted read only.
show:


cat /proc/mounts


and verify that you can write to the file system:
do in terminal:


touch /home/pete/test
ls -al /home/pete/test

is the file test created in your /home ?
screaming and hollering what ? permission denied ? or a read only file system ?



gots to be a reason !

[pete340]

pete@pete-VPCF23P1E:~$ sudo fdisk -lu
[sudo] password for pete:
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0bcdd322

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 124807167 124805120 59.5G 83 Linux
/dev/sda2 * 124807168 227205119 102397952 48.8G 7 HPFS/NTFS/exFAT
/dev/sda3 227207166 872187903 644980738 307.6G 5 Extended
/dev/sda4 872187904 976771071 104583168 49.9G 7 HPFS/NTFS/exFAT
/dev/sda5 227207168 235384379 8177212 3.9G 82 Linux swap / Solaris
/dev/sda6 235386880 238528511 3141632 1.5G 7 HPFS/NTFS/exFAT
/dev/sda7 238530560 872185855 633655296 302.2G 7 HPFS/NTFS/exFAT

Partition table entries are not in disk order.







pete@pete-VPCF23P1E:~$ cat /proc/mounts
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=8182572k,nr_inodes=2045643 ,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode= 000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=1641024k,mode=755 0 0
/dev/sda1 / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs rw,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agen t=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,clone_child ren 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event,release _agent=/run/cgmanager/agents/cgm-release-agent.perf_event 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb,release_ag ent=/run/cgmanager/agents/cgm-release-agent.hugetlb 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids,release_agent =/run/cgmanager/agents/cgm-release-agent.pids 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxp roto=5,direct,pipe_ino=18457 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/dev/sda6 /home fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksi ze=4096 0 0
/dev/sda2 /media/sda2 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksi ze=4096 0 0
/dev/sda4 /media/sda4 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksi ze=4096 0 0
/dev/sda7 /media/sda7 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksi ze=4096 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
cgmfs /run/cgmanager/fs tmpfs rw,relatime,size=100k,mode=755 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1641024k,mode=700,ui d=1000,gid=1000 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0 0



so sda1 is is the main linux partition (ext4) but I moved /home to sda6 which is ntfs .. could that be the problem ?
sda2 and sda6 are win7 and win 10, sda2 also has the bootloader



pete@pete-VPCF23P1E:~$ touch /home/pete/test
pete@pete-VPCF23P1E:~$ ls -al /home/pete/test
-rwxrwxrwx 1 root root 0 Dec 6 13:11 /home/pete/test


just out of curiosity, wouldn't chown be worth a shot? or is it not what we're after now ?

Should I move /home back to sda1 ? or try to convert sda6 to ext4 ?

[Bashing-om]

pete340; Yepper ..

You called it .. sda6 as ubuntu /home on a Windows file system / NTFS is not posit compliant and as such the chmod commands will not effect !

I am not Windows literate and all I can recommend or suggest at this time is save your data on that sda6 NTFS partition // and re-partition sda6 to ext4 ; then copy the data back and hope it works out . I do have serious doubts about keeping the symlinks sane in that move event . Let us keep ubuntu file systems as linux type and compliant .

As to the level of difficulty entailed to change that partition I can not say . I have never attempted such. In this case you might be better served to just backup your data / change the sda6 file system type to ext4 / and re-install ubuntu .



if I knew better I would



do better

[pete340]

Bashing-om, Hi

So even if I manage to move /home format ext4 and move /home back killing the few symlinks that may have survived the original move ( there was a lot of errors which I did not understand at the time), it is not going to be possible to salvage my current installation and the only way is re-install ?

[Bashing-om]

pete340; Welp;

Ya got the better of me here - I have no experience in this event . I have always set up my /home at the time of installation .
For your consideration:
https://help.ubuntu.com/community/Partitioning/Home/Moving
https://ubuntuforums.org/showthread.php?t=2337233&page=3
http://www.howtogeek.com/116742/how-to-create-a-separate-home-partition-after-installing-ubuntu/

While I agree it is possible to fix - I do think the expedient thing to do is change the partition type to ext4 and do a clean fresh install .
As to how you want to interact with Windows .. I do not have a clue . I have not ever had to interact with Windows on ubuntu ; and do not know what tools will be required - install linux tools on Windows to allow Windows to read the linux file system ?

But hey, I am always open to a learning experience;


we do as you decide