[SOLVED] New installation of xfce 64 and 32 bit fails to start xserver after d-u

[vilde]

I did try a 32 bit installation a few days ago, I was just playing around the and didn't care but today I tried a 64 bit installation and got the same fault so now I need help. Fresh installation, xfce 64 bit, after d-u without visible trouble the xserver is not starting. When logging in as user or root and trying to startx it fails also.

On boot I am able to quickly see some red lines "failed......" before being dropped in init 3

Now I am on old installation on the same computer but another hard disk so I will be able to reach the logfiles from the new and not working instalation, please tell me what you want to see?

[convbsd]

Hello,

What xfce release have you installed ?
cat /etc/siduction-version

Thank you

[towo]

What xfce release have you installed ?

Which is installed release, is the smallest problem.
No one knows one point about the used hardware and drivers!
We have not seen any relevant logfile!

[vilde]

What xfce release have you installed ?

Which is installed release, is the smallest problem.
No one knows one point about the used hardware and drivers!
We have not seen any relevant logfile!

I asked for what logfile(s) you want, I have no idea?

The following is, inxi -v3., from my old installation on the same computer there you can see the hardware. It works good with my old installation, it's the new installed on another hard disk that fails after d-u. I think it's a d-u problem, long time from release till now. AND I had far as a could understand the same fault on a 32 bit installation but on an older computer (T60) so it's not specific to this hardware.

Code Select Expand

System:    Host: T410 Kernel: 3.16-3.towo-siduction-686 i686 (32 bit gcc: 4.9.1)
           Desktop: Xfce 4.10.2 (Gtk 2.24.18)
           Distro: siduction 13.2.1 December - xfce - (201401272212)
Machine:   System: LENOVO product: 25223FG v: ThinkPad T410
           Mobo: LENOVO model: 25223FG
           Bios: LENOVO v: 6IET85WW (1.45 ) date: 02/14/2013
CPU:       Dual core Intel Core i7 M 620 (-HT-MCP-) cache: 4096 KB
           flags: (lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10642
           clock speeds: max: 2667 MHz 1: 1199 MHz 2: 1199 MHz 3: 1199 MHz
           4: 1199 MHz
Graphics:  Card: NVIDIA GT218M [NVS 3100M] bus-ID: 01:00.0
           Display Server: X.Org 1.16.1 drivers: nouveau (unloaded: fbdev,vesa)
           Resolution: 1440x900@60.06hz
           GLX Renderer: Gallium 0.4 on NVA8
           GLX Version: 3.0 Mesa 10.2.6 Direct Rendering: Yes
Network:   Card-1: Intel 82577LM Gigabit Network Connection
           driver: e1000e v: 2.3.2-k port: 1820 bus-ID: 00:19.0
           IF: eth0 state: down mac: 00:26:2d:f3:8e:a0
           Card-2: Intel Centrino Ultimate-N 6300
           driver: iwlwifi v: in-tree: bus-ID: 03:00.0
           IF: wlan0 state: up mac: 00:24:d7:06:72:fc
Drives:    HDD Total Size: 360.1GB (17.8% used) ID-1: model: KINGSTON_SV300S3
           ID-2: model: Crucial_CT240M50
Info:      Processes: 209 Uptime: 2:26 Memory: 405.2/3029.3MB
           Init: systemd runlevel: 5 Gcc sys: 4.9.1
           Client: Shell (bash 4.3.27

[absolut]

with xserver not starting, the relevant logfile is --->  /var/log/Xorg.0.log

[vilde]

with xserver not starting, the relevant logfile is --->  /var/log/Xorg.0.log

Ok, here is that logfile http://paste.siduction.org/20141009130223

[towo]

The x-log from a start with an old kernel does not help many.

[vilde]

The x-log from a start with an old kernel does not help many.

towo, it would be nice if you help me by telling me what you want to have a look at instead of telling me whats not of any help, I never use logfiles because I don't understand them anyway.  I have no idea where and what to look at.........

[michaa7]

What towo is telling you means (presumably): The first thing you need to do before looking for whatever log files is to update the kernel (your's is 3.12., newest siduction is 3.17.0)

[vilde]

What towo is telling you means (presumably): The first thing you need to do before looking for whatever log files is to update the kernel (your's is 3.12. , newest siduction is 3.17.0)

My first post tells that the new installation is fully updated without any visible problem, and therefore it probably have the newest kernel. If the logfile from x is not showing that, it would probably mean (as I think as an amateur) that x never even manage to start after the d-u so far that there was written any new logfile.

[vilde]

After checking and trying a little things I found out that it looks like the filesystem is not writeable. I'm not able to write anything eve loged in as root.  And after trying startx again, one of the the last messages is "could not create lock file......" Can the problem be that the filesystem is not write able by some reason???

[devil]

a workaround is to do as root: mount -o remount,rm /dev/whatever_your_root_is. That will start X.


I have the same problem on my notebook, with the same error message, but have no time atm to look for a fix.


greetz
devil

[vilde]

a workaround is to do as root: mount -o remount,rm /dev/whatever_your_root_is. That will start X.


I have the same problem on my notebook, with the same error message, but have no time atm to look for a fix.


greetz
devil

are you sure you wrote that right devil? and shall I put my root partition last? "Doing mount -o remount,rm /dev/sdb1" is not recognized, doing "mount -o remount, rm /dev/sdb1" is ok as command but returns that "sdb1 is not mounted or bad something"

[devil]

Sorry, typo: mount -o remount,rw /dev/sdb1


greetz
devil

[michaa7]

Code Select Expand

uname -r