Porteus

Hello.
A few days ago my pendrive installation of Porteus stopped working. Instead of booting into MATE, it's stuck at the terminal after the welcome message, with a login prompt. After a while, this message appears:
Id "x1" respawning too fast: disabled for 5 minutes

I've been able to transfer the log files over WiFi, but I can't figure out where's the issue. I've looked through the /var/messages file, which I'm attaching below, but I couldn't notice anything pertraining to the graphics drivers or WM.
I hope some of you fine folks can point me in the right direction with this.
https://drive.google.com/file/d/0B1E3Ej ... sp=sharing

Also, for some reason this forum logs me out every second page I open. Windows 10, Chrome on Stable branch.

^ Tried?

Log me on automatically each visit

Bogomips wrote:^ Tried?

Log me on automatically each visit

Yup, it didn't make a difference. However it's in the past now, it seemed to be an issue for only half of an hour, oddly enough.

Just as a possible explanation... I received this same error message the other day while experimenting with Porteus booting from an NTFS partition.

Turned out the reason was that my save.dat file was too small. After resizing this, the message disappeared.

tmsg wrote:Just as a possible explanation... I received this same error message the other day while experimenting with Porteus booting from an NTFS partition.

Turned out the reason was that my save.dat file was too small. After resizing this, the message disappeared.

I thought of the same at first. I haven't been maintaining the system for a while, after checking by using the find command, it seems that I haven't made the changes reside in a .dat file. I was able to browse to the /changes/ subfolders and I saw my files. From df -h it also seems I've got only 6 GiB out of 30GiB of space taken.

However it's in the past now, it seemed to be an issue for only half of an hour, oddly enough.

Why is this marked FAA?

^ From 22/11 to 24/11 no response to problem. No mod able to dealt with it. Is it now solved?

anijatsu wrote:After a while, this message appears:
Id "x1" respawning too fast: disabled for 5 minutes

I've been able to transfer the log files over WiFi, but I can't figure out where's the issue.

brokenman wrote:Why is this marked FAA?

I actually don't know. I don't remember putting this in the title. Google's cache confirms it.

Bogomips wrote:^ From 22/11 to 24/11 no response to problem. No mod able to dealt with it. Is it now solved?

It is not.

^ Prepended FAA in order to flag problem For Attention of Admins. In your case, a request to devs to help you out.

Please use porteus settings centre to generate a full system report and upload it to pasebin then plaste a link here. Specifically video card is of importance.
Also please try to boot in fresh mode with no extra modules added and no changes. Vanilla porteus. Does it work?

brokenman wrote:Please use porteus settings centre to generate a full system report and upload it to pasebin then plaste a link here. Specifically video card is of importance.
Also please try to boot in fresh mode with no extra modules added and no changes. Vanilla porteus. Does it work?

Sorry for the late reply. Fresh mode started up successfully. Since I'm unable to get into MATE normally /w the changes, I could have only saved the Porteus Settings Centre log from fresh mode. Link is below:
http://pastebin.com/NMXY7nuP
Should I tar the /var/log folder after trying to boot the system normally to show it to you?

Everything looks good in your logs. We can rule out the graphics driver. It is loading and waiting. Can you please boot into text mode (at the blue menu option) and then issue: If it fails and you are dumped to a console again then get the output in /tmp/out

brokenman wrote:Everything looks good in your logs. We can rule out the graphics driver. It is loading and waiting. Can you please boot into text mode (at the blue menu option) and then issue:

Code: Select all

startx 2>/tmp/out

If it fails and you are dumped to a console again then get the output in /tmp/out

It does startup normally after typing the command. What can I do about this?

Then the DM (desktop manager) is causing the problem. Not entirely sure how to resolve this since nobody else has had this problem. I will hunt around for an answer.

IBM Think Pad x100e

Boot always fresh solved this by resizing my dat file to another location: sda1 to sda2 with more room.
Copied original and deleted old dat file during resize
changed porteus boot file form sda1 to 2

Worked fine.

No I don't know why.