[SOLVED]blank screen

[feng]

hi!

anyway to disable blank screen?

thanks a lot. :p

[Ahau]

Which version are you using (32 or 64 bit, version 0.9, or V1.0, alpha or beta), and when does the blank screen occur? Does porteus continue to boot into your desktop (KDE or LXDE), or is it frozen and requires a reboot? We'll need some more info to help.

Thanks!

[Blaze]

I have a blank screen in Porteus 32 bit beta when i boot up with kde (don't use cheatcodes). With LXDE all ok.
My video card is Nvidia GeForce 8600

[Hamza]

I have a blank screen in Porteus 32 bit beta when i boot up with kde (don't use cheatcodes). With LXDE all ok.
My video card is Nvidia GeForce 8600

Try to recompile the kernel with your driver.

[Ahau]

I have a blank screen in Porteus 32 bit beta when i boot up with kde (don't use cheatcodes). With LXDE all ok.
My video card is Nvidia GeForce 8600

Do you have the splash cheatcode enabled? KMS blacklisting enabled? Do you use nouveau or the nVidia driver?

I have an nVidia card too, but I don't use the splash cheatcode. I get lines of text scrolling while porteus gets set up, and then my screen goes blank and flashes a little garbage for about a second, and then kdm starts right up with a login prompt.

[feng]

Which version are you using (32 or 64 bit, version 0.9, or V1.0, alpha or beta), and when does the blank screen occur? Does porteus continue to boot into your desktop (KDE or LXDE), or is it frozen and requires a reboot? We'll need some more info to help.

Thanks!

hi!

i am running porteus v09 32-bit.
i think "blank screen" is a feature in slackware only. no matter in X or in terminal.
what i meant "blank screen" is not frozen or dead. it is kind like screen saver.
the screen will come back if you press any key or move your mouse.
i dont like this if i want to watch movie or news...

thank you. :-p

[Blaze]

Hamza, so I start with my video card on LXDE, but i can't start Porteus on KDE.

Ahau,

• I use splash=silent
• KMS (blacklist nouveau) enabled in /etc/modprobe.d/BLACKLIST-KMS.conf
• Yes, i have a little garbage and then blank screen - kdm & kde does not start up, only with LXDE is work.

BTW in VMware Workstation all (kde & lxde) works fine.

Cheers

[fanthom]

@feng
in Kmenu go to:
Settings -> Peripherials -> Display
enable Display Power Management and then disable all services. if that wont help then edit your /etc/X11/xorg.conf in section Monitor and comment out DPMS feature like in this example:

Section "Monitor"
#DisplaySize 380 300 # mm
Identifier "Monitor0"
VendorName "ACR"
ModelName "Acer AL1912"
HorizSync 30.0 - 83.0
VertRefresh 55.0 - 75.0
#Option "DPMS"
EndSection

if you dont use 'changes=' cheatcode then use /rootcopy to save your settings.
Cheers

EDIT:\\
@Blaze
do you get the same error in 64bits as well? maybe it's a modesetting driver issue? which driver is shown in /etc/X11/xorg.conf?

[Ahau]

@blaze that is strange. Have you tried vesa mode and/or the nVidia driver? I'm trying to think of where the problem could be...I'm coming up short lol.

[Blaze]

Note. My video card is Nvidia GeForce 8600

do you get the same error in 64bits as well?

no, but my cursor is broken

My Xorg.0.log of porteus-v1.0_beta-x86_64 -> pastebin.com/zUJr3vuE

I don't use Nvidia driver.

Ahau, vesa mode work for me and text mode too (xconf + startx).
My Xorg.0.log of porteus-v1_beta-i486 -> pastebin.com/yeNJLHWt

Code: Select all

.....
[   467.241] 	GeForce 7   (G7x)
[   467.241] 	GeForce 8   (G8x)
[   467.241] (--) using VT number 7
.....
[   470.330] (EE) NOUVEAU(0): Error creating GPU channel: -22
[   470.330] (EE) NOUVEAU(0): Error initialising acceleration.  Falling back to NoAccel

Offtopic.
I think need to cut this line

Code: Select all

cups: started scheduler

from:

Code: Select all

Warning! root is still using default toor password provide new one or press enter to skip:
cups: started scheduler
_

[fanthom]

@Blaze
1) not sure about 32bits but for 64 you are using 'modesetting' driver which i forgot to remove. please try Service Pack 2 which should fix this issue.
2) yes - cups is jumping sometimes down that Warning line, i will disable this notification completely in rc.M

[Blaze]

try Service Pack 2 which should fix this issue.

You are right - it help me. I see a normal cursor pointer but a problem with 32 bit is still remained. Thanks.