no X after second start, only console

judydudi · 2017-09-22 13:08

hi,
just a fresh install of q4os-live-2.3.5-x64, everything works fine on a Asrock J3455B-itx
(Intel® HD Graphics 500). But at next start i come to console and had to login and start "startx" manually.
Desktop works fine then. Why does it not start automatically? Thanks.

q4osteam · 2017-09-22 13:36

Please try to reboot and run from console:

$ sudo systemctl status tdm.service > /tmp/tdm.log
$ sudo journalctl > /tmp/journal.log
$ tar cvzf /tmp/log.tgz /tmp/journal.log /tmp/tdm.log /var/log/Xorg.0.log

and attach '/tmp/log.gz' file here to analyze. Next run:

$ sudo systemctl restart tdm.service

and report back the result.

judydudi · 2017-09-22 18:15

Thank you,
$ sudo systemctl restart tdm.service
starts the desktop. after reboot still in console.

Attachments:

log.tgz, Size: 45 B, Downloads: 882

q4osteam · 2017-09-22 19:32

The file 'log.tgz' attached is empty for some reason. It should contain following files:
/tmp/journal.log
/tmp/tdm.log
/var/log/Xorg.0.log

You could pack these files manually and attach it here once again.

judydudi · 2017-09-22 20:16

sorry, don't know why. here another try.

Attachments:

log.tgz, Size: 18.5 KiB, Downloads: 918

q4osteam · 2017-09-22 20:43

judydudi wrote:

... Why does it not start automatically? Thanks.

Looks like a hardware compatibility issue, as the graphics drivers seems to get initialized with a delay, just after the display manager service starts. You could try to fix it performing following actions:

1. Install CPU microcode:
$ sudo apt-get install amd64-microcode intel-microcode
$ sudo reboot

2. Upgrade BIOS

3. Try to install newer kernel 4.12 from Stretch backports:
- Add backports, see https://backports.debian.org/Instructions/
$ sudo apt-get -t stretch-backports install linux-image-amd64

You are welcome to report back a result, we will assist you if there will be some more options available.

judydudi · 2017-09-22 21:23

SOLVED!
no changes after install intel microcode or after bios update.
after updating to new kernel from backports, the system starts flawless into desktop and very fast! ;-)
Thank you.

MGPProjectS · 2017-10-28 09:55

Hi Q4os Team,

I have same experience installing i386 without PAE (q4os-2.4-i386-instcd.r2.iso).
Which backport package should I choose?

Thanks

/Mikael

q4osteam · 2017-10-28 10:25

MGPProjectS wrote:

I have same experience installing i386 without PAE (q4os-2.4-i386-instcd.r2.iso).
Which backport package should I choose?

Install CD autodetects cpu type and use PAE or non-PAE kernel accordingly. So, you will need to install 'linux-image-686' or 'linux-image-686-pae' package from backports depending on the system you use. Get the relevant info using following command in terminal:
$ uname -r

MGPProjectS · 2017-10-28 13:26

q4osteam wrote:

MGPProjectS wrote:
I have same experience installing i386 without PAE (q4os-2.4-i386-instcd.r2.iso).
Which backport package should I choose?
Install CD autodetects cpu type and use PAE or non-PAE kernel accordingly. So, you will need to install 'linux-image-686' or 'linux-image-686-pae' package from backports depending on the system you use. Get the relevant info using following command in terminal:
$ uname -r

Kernel is
4.9.0-4-686

I guess that is the correct kernel for older PC's according to Debian web?

It also seem that I am not able to optain root/admin rights with my applied user/pass.

Last edited by MGPProjectS (2017-10-28 13:37)

crosscourt · 2017-10-28 17:30

4.9 kernel wont work with some older cpus but which cpu do you have and what system are you running?

You could try the Orion 1.8.8 live cd and see if it works as it runs an older kernel.

Intel HD graphics 500 or Apollo Lake is a newer design and requires a recent kernel 4.10 or newer I believe.

Knowing what cpu and chipset your using and making sure the kernel supports that hardware.

Sometimes a newer kernel is a must, other times and older kernel is needed.

Last edited by crosscourt (2017-10-28 17:46)

MGPProjectS · 2017-10-28 20:02

It's a very old 1,5GHz singlecore Centrino without PAE support, unfortunately.
Hoewever, it runs very smoothly on Orion ;-)

crosscourt · 2017-10-28 20:56

Id stay with Orion as the 1.5ghz Centrino doesnt have the performance for Scorpion and needs the older kernel thats already available in Orion.

I have many older systems with similar issues and they cant run Scorpion.

MGPProjectS · 2017-10-28 21:01

OK, thanks!

crosscourt · 2017-10-28 21:08

Is it a laptop with the 1.5 centrino?

MGPProjectS · 2017-10-28 21:35

Yes, an old SATELLITE A50-543.

crosscourt · 2017-10-28 22:34

Ok thats why youre having problems as it has a Pentium M 715 with the 855 GME chipset. The older kernel is definitely the way to go with non-pae version. I also wouldnt be surprised if there were some bios issues as Toshiba wasnt real cooperative towards Linux at that time.

Last edited by crosscourt (2017-10-28 22:40)

cris · 2018-01-09 08:30

$ sudo apt-get install amd64-microcode intel-microcode
$ sudo reboot
$ sudo apt-get -t stretch-backports install linux-image-amd64

after all the above still has not solved the xserver
but (?re)installing the 'xserver-xorg-video-intel' , solved my problem

$ sudo apt-get -t stretch-backports install xserver-xorg-video-intel

$ sudo reboot

crosscourt · 2018-01-11 03:24

More often trying a different driver or a newer/older kernel will solve the issue depending on the age of the hardware.

Q4OS Forum

#1 2017-09-22 13:08

no X after second start, only console

#2 2017-09-22 13:36

Re: no X after second start, only console

#3 2017-09-22 18:15

Re: no X after second start, only console

#4 2017-09-22 19:32

Re: no X after second start, only console

#5 2017-09-22 20:16

Re: no X after second start, only console

#6 2017-09-22 20:43

Re: no X after second start, only console

#7 2017-09-22 21:23

Re: no X after second start, only console

#8 2017-10-28 09:55

Re: no X after second start, only console

#9 2017-10-28 10:25

Re: no X after second start, only console

#10 2017-10-28 13:26

Re: no X after second start, only console

#11 2017-10-28 17:30

Re: no X after second start, only console

#12 2017-10-28 20:02

Re: no X after second start, only console

#13 2017-10-28 20:56

Re: no X after second start, only console

#14 2017-10-28 21:01

Re: no X after second start, only console

#15 2017-10-28 21:08

Re: no X after second start, only console

#16 2017-10-28 21:35

Re: no X after second start, only console

#17 2017-10-28 22:34

Re: no X after second start, only console

#18 2018-01-09 08:30

Re: no X after second start, only console

#19 2018-01-11 03:24

Re: no X after second start, only console

Board footer