Porteus 3.1 boots to within sight of desktop then goes blank
Posted: 24 Mar 2016, 09:51
Here are a few problems to sort out. (So go for it!)
When I boot PORTEUS 3.1 Mate off DVD and choose boot Mate it goes through its startup procedure. It gets to text login screen, and continues to autoboot towards a GUI. Then screen goes dark(-er); a mouse appears (but has "mouse-trails"); the cursor turns to spinning blue "wait" disk; later then a desktop pops up for about 1/2 second (ie "looking out of a blue-tiled sewer pipe"), followed by the screen going even darker (to black) - then nothing works. Cannot get keyboard, mouse, alt consoles - nothing.
Notes
1.
If I intervene just prior to screen going dark (ie before mouse cursor) I can get CTRL. Then I can get alt console, login etc. Ten if I return to 1st console (at any time), then the system boot continues (ie screen goes dark followed by mouse cursor etc). Then I can flip back to alt console before that and still have control, but if I leave it I will lose control of system. If I return to 1st console the system will try to continue every time.
2.
When I get to alt console I note that I can press the num-lock, it's light will start, but then disengages. Same with CAPS-lock. Light won't stick.
3.
At kernel arg line I have tried "nomodeset", and mode settings without any changes. Tried VGA=ask but without a fix. Tried VGA=detect but it seems to have no effect. [VGA=xxx (ie a number, 788) will work for altering boot text.]
4.
My system is old. Noteable points are:- the graphics card is AGP SiS-6326; Monitor is LG Model-L196WTQ; CPU is Athlon 1GHz single-core. (I have no plans to change any of this right now because Mageia-5 installed on it without any problems, and works beautifully.)
5.
Porteus is not the only distro I have problems with, but is one of the few that won't get to a "live" setup. I am keen to try Porteus as a lightweight, stable, configurable, supported system. (However, I do NOT like to work at the CLI.)
6.
Yes, I can get to runlevel 3 but I'm not much good at repairing/re-configuring (because without sound "linux-system-knowledge" it's way too complex to muck around with).
Any thoughts?
Regards,
When I boot PORTEUS 3.1 Mate off DVD and choose boot Mate it goes through its startup procedure. It gets to text login screen, and continues to autoboot towards a GUI. Then screen goes dark(-er); a mouse appears (but has "mouse-trails"); the cursor turns to spinning blue "wait" disk; later then a desktop pops up for about 1/2 second (ie "looking out of a blue-tiled sewer pipe"), followed by the screen going even darker (to black) - then nothing works. Cannot get keyboard, mouse, alt consoles - nothing.
Notes
1.
If I intervene just prior to screen going dark (ie before mouse cursor) I can get CTRL. Then I can get alt console, login etc. Ten if I return to 1st console (at any time), then the system boot continues (ie screen goes dark followed by mouse cursor etc). Then I can flip back to alt console before that and still have control, but if I leave it I will lose control of system. If I return to 1st console the system will try to continue every time.
2.
When I get to alt console I note that I can press the num-lock, it's light will start, but then disengages. Same with CAPS-lock. Light won't stick.
3.
At kernel arg line I have tried "nomodeset", and mode settings without any changes. Tried VGA=ask but without a fix. Tried VGA=detect but it seems to have no effect. [VGA=xxx (ie a number, 788) will work for altering boot text.]
4.
My system is old. Noteable points are:- the graphics card is AGP SiS-6326; Monitor is LG Model-L196WTQ; CPU is Athlon 1GHz single-core. (I have no plans to change any of this right now because Mageia-5 installed on it without any problems, and works beautifully.)
5.
Porteus is not the only distro I have problems with, but is one of the few that won't get to a "live" setup. I am keen to try Porteus as a lightweight, stable, configurable, supported system. (However, I do NOT like to work at the CLI.)
6.
Yes, I can get to runlevel 3 but I'm not much good at repairing/re-configuring (because without sound "linux-system-knowledge" it's way too complex to muck around with).
Any thoughts?
Regards,