I've solved a problem,
look at the end of this thread:
Automatic connection to the wireless network
Since then a new problem has arisen.
Startup ends with the message:
init: Id "x1" respawning too fast: disabled for 5 minutes
This error does not always occur, but quite often.
Why?
Can someone help?
Thanks
init: Id "x1" respawning too fast
init: Id "x1" respawning too fast
Supplement:
Do you have to change/add anything to the file /etc/rc.d/rc.4 ?
Do you have to change/add anything to the file /etc/rc.d/rc.4 ?
- Ed_P
- Contributor
- Posts: 5896
- Joined: 06 Feb 2013, 22:12
- Distribution: 4.0 & 5.0rc2 Cinnamon 64 ISOs
- Location: Western NY, USA
init: Id "x1" respawning too fast
It could be related to what you saved with your network module. Does the problem occur when you don't use it?
Also do you boot Windows on the machine? I get a similar error if I don't shut Windows down before rebooting.
Also do you boot Windows on the machine? I get a similar error if I don't shut Windows down before rebooting.
Ed
-
- White ninja
- Posts: 14
- Joined: 16 Apr 2020, 17:42
- Distribution: Porteus OpenBox
init: Id "x1" respawning too fast
I have the same problem and it occurs randomly.
I found that adding a pause of 2-4 seconds at the start of /etc/rc.d/rc.4 allows me to far more consistently boot straight to X.
This happens in Virtualbox, eeePC netbook and some old Toshiba laptop as well. All random.
It's as if X is (re)starting before Porteus finishes some kind of initialisation, because startx always works. Some kind of unaccounted dependency?
5.0 rc2 Openbox. Install on a ext4 partition
I found that adding a pause of 2-4 seconds at the start of /etc/rc.d/rc.4 allows me to far more consistently boot straight to X.
This happens in Virtualbox, eeePC netbook and some old Toshiba laptop as well. All random.
It's as if X is (re)starting before Porteus finishes some kind of initialisation, because startx always works. Some kind of unaccounted dependency?
5.0 rc2 Openbox. Install on a ext4 partition