Forums

Resolved
-1 votes
ClearOS Community 6.6 2.6.32-584.8.1.v6.x86_64


I was hoping this would fix it but it does not:
Peter Baldwin wrote:
We seem to be having another round of blank screens in ClearOS 6.6. If possible, try changing the contents of /etc/X11/xorg.conf.d/vm.conf to:


Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "800x600" "640x480"
EndSubsection
EndSection


And then reboot.


I've re-installed the os multiple times as at first I thought maybe it was just the onboard Geforce 8300 not being liked... turns out I was wrong even with a PCI-E AMD Radeon 6450 it still not posting after the splash screen.

I've tried all the examples out there i've even edited the grub boot script pre boot after disabling nouveau and changing video=vesafb to video=nvidia and the splash screen goes crystal clear in 1080p on my TV over HDMI and then just locks up on the splash screen and ALT+F(1-7) return nothing, rebooting and hitting esc during splash screen to display verbose mode shows 0 errors other than the nforce2 smb error (that i'm hoping is irrelevant) loads up everything marks [ OK ] and then the blank screen where I should see a "first time setup" or a login or something... and Alt+F[1-7] works i can login to root from any of the 'screens' except for 1 and 7 2-6 are text.

I've even tried using a regular LCD 17" over DVI with both cards and still nothing (even after a fresh install over DVI with either card)

the only problem starts after

>startx:

Loading extension GLX
(EE)
Fatal Server Error:
(EE) no screens found(EE)
(EE)
Please consult the RED HAT, Inc support
at https://www.redhat.com/apps/support/
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.
Thursday, March 19 2015, 02:37 AM
Share this post:
Responses (13)
  • Accepted Answer

    Friday, April 10 2015, 11:47 AM - #Permalink
    Resolved
    0 votes
    Thanks Nick couldn't figure out what I was doing wrong link in previous post now
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 10 2015, 11:35 AM - #Permalink
    Resolved
    0 votes
    All images must be less than 800*800px to post on the forum.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 10 2015, 11:31 AM - #Permalink
    Resolved
    0 votes
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 10 2015, 11:28 AM - #Permalink
    Resolved
    0 votes
    here is a screen shot of the error I get.
    I have been able to log in to the web interface now and have configured the server. I would however like to have the web-gui displayed.
    http://i1306.photobucket.com/albums/s575/ghendoaus/Photobucket%20Desktop%20-%20Graemes%20MacBook%20Pro/Photobucket/error_zpsas0t4zby.jpg
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 10 2015, 09:52 AM - #Permalink
    Resolved
    0 votes
    I have tried what Peter Baldwin suggested:

    Peter Baldwin wrote:
    We seem to be having another round of blank screens in ClearOS 6.6. If possible, try changing the contents of /etc/X11/xorg.conf.d/vm.conf to:

    Code:

    Section "Screen"
    Identifier "Default Screen"
    Monitor "Configured Monitor"
    Device "Configured Video Device"
    DefaultDepth 24
    Subsection "Display"
    Depth 24
    Modes "800x600" "640x480"
    EndSubsection
    EndSection


    And then reboot.

    The result is that the screen goes blank more quickly and I can now ctrl+alt+F2 to an alternate shell
    The reply is currently minimized Show
  • Accepted Answer

    Friday, April 10 2015, 09:32 AM - #Permalink
    Resolved
    0 votes
    Hi I have a similar situation my COS 6.6 fresh install on Hyper-V 2012 R2 hangs with
    clearos 6.6 /usr/sbin/gconsole-setup: line 14: 1648 aborted
    I tried Test 2 as above and now the screen goes black after starting syswatch - I set it up with a fixed ip and cannot ping it - cannot get to the web interface to configure it there either not sure what to do.
    The reply is currently minimized Show
  • Accepted Answer

    Hans
    Hans
    Offline
    Wednesday, March 25 2015, 09:25 PM - #Permalink
    Resolved
    0 votes
    Re-installed my OS on my bare metal HP Microserver N40L.
    Just like in Igor's case, Test 2 fixed the blank screen issue.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, March 23 2015, 12:44 PM - #Permalink
    Resolved
    2 votes
    Dave Loper wrote:
    Hans,


    ======= Test 2 =======
    Switch to an alternate text console (Ctrl+Alt+F2) and login as root. Run the following:

    rm -f /etc/X11/xorg.conf.d/vm.conf
    touch /etc/X11/xorg.conf.d/vm.conf
    reboot

    If this test passes then your driver is fine and the Xorg configure is over-analyzing your situation.

    Let me know how this goes.


    I had the same problem.
    TEST 2 fixed it thank you very much!
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 20 2015, 07:21 PM - #Permalink
    Resolved
    0 votes
    Hans wrote:


    I then tried the reconfigure method
    /usr/bin/Xorg -configure
    and also did not work after reboot.
    In the end I went into grub.conf and edited vga=0x314 into vga=917. I also removed "rhgb" since I like to see what's happening during boot when the monitor is connected.

    Not sure the last thing did the trick but I now have a visual. I'm okay. Sorry for not having proper test results. :S


    I had to re-install the same day because I went app crazy and installed a bunch of apps at once these apps are neat since the last time I used this OS was when it was ClarkeConnect Community 4.0.

    upon second time of fresh install I once again had no screen on first boot so I first tried to edit the grub on boot to vga=791 nomodeset and that did not help so then I did the xorg replace


    /usr/bin/Xorg -configure


    rebooted and did not reedit the grub on boot and I still had once again no screen so reboot and edit grub with vga=791 nomodeset and bam I get visuals again.

    So really this bug has to do with vm.conf and vga=0x314, is there a way on first boot you can issue /usr/bin/Xorg -configure to self populate a vm.conf that is catered to each system? also I have no idea why changing vga to '791' plays a big roll also doesn't matter if the display is a Widescreen Monitor over VGA/DVI or a 4:3 LCD Monitor or an 1080p TV over VGA/HDMI vga=791 fixes it as long as you rebuild the vm.conf.
    The reply is currently minimized Show
  • Accepted Answer

    Hans
    Hans
    Offline
    Friday, March 20 2015, 03:42 PM - #Permalink
    Resolved
    0 votes
    Dave,
    Before I read your anwser I've tried one or two things.
    One solution from the other thread did not work:

    Peter Baldwin wrote:
    We seem to be having another round of blank screens in ClearOS 6.6. If possible, try changing the contents of /etc/X11/xorg.conf.d/vm.conf to:


    Section "Screen"
    Identifier "Default Screen"
    Monitor "Configured Monitor"
    Device "Configured Video Device"
    DefaultDepth 24
    Subsection "Display"
    Depth 24
    Modes "800x600" "640x480"
    EndSubsection
    EndSection


    And then reboot.


    I then tried the reconfigure method
    /usr/bin/Xorg -configure
    and also did not work after reboot.
    In the end I went into grub.conf and edited vga=0x314 into vga=917. I also removed "rhgb" since I like to see what's happening during boot when the monitor is connected.

    Not sure the last thing did the trick but I now have a visual. I'm okay. Sorry for not having proper test results. :S
    The reply is currently minimized Show
  • Accepted Answer

    Friday, March 20 2015, 01:31 PM - #Permalink
    Resolved
    0 votes
    Hans,

    Please attach a copy of the /etc/X11/xorg.conf.d/vm.conf file.

    Then, perform these separate tests:

    ======= Test 1 Baseline =======
    Switch to an alternate text console (Ctrl+Alt+F2) and login as root. Run the following:

    rm -f /etc/X11/xorg.conf.d/vm.conf
    /usr/bin/Xorg -configure
    mv /root/xorg.conf.new /etc/X11
    reboot

    Let me know the results of this test. It will probably fail because this is what the script does. But if it works then that is a clue.

    ======= Test 2 =======
    Switch to an alternate text console (Ctrl+Alt+F2) and login as root. Run the following:

    rm -f /etc/X11/xorg.conf.d/vm.conf
    touch /etc/X11/xorg.conf.d/vm.conf
    reboot

    If this test passes then your driver is fine and the Xorg configure is over-analyzing your situation.

    Let me know how this goes.
    The reply is currently minimized Show
  • Accepted Answer

    Hans
    Hans
    Offline
    Friday, March 20 2015, 10:59 AM - #Permalink
    Resolved
    0 votes
    I have the same issue; blank screen after first boot. I can logon via PuTTY client remotely.
    My hardware is:
    [ul]
  • HP N40L Microserver,

  • Dell 2005FPW screen via VGA
  • [/ul]
The reply is currently minimized Show
  • Accepted Answer

    Thursday, March 19 2015, 03:55 AM - #Permalink
    Resolved
    0 votes
    Fixed with help from:

    Dave Loper wrote:
    Our upstream linux distribution changed some fundamental things which renders the Xconsole a bit wonky. In the past we had included a config that was very stripped down and very basic. That doesn't seem to work here now for some and some users (even some users of ClearBOX) will end up with an invalid Screen set. We will have a fix for the mainline code that should work and we need people to test the update that fixes this. Peter will give some info for testers.

    If you really, really need a quick fix you can remove the vm.conf file and recreate one that works with your monitor. Perform the following steps to do a manual intervention of your Clearconsole:

    1) Exit the console session to another screen by typing Ctrl+Alt+F2.
    2) Log into this console as 'root'
    3) Kill the Xwindows session with 'killall xinit'
    4) move the vm.conf file:
    mv /etc/X11/xorg.conf.d/vm.conf /root/vm.conf.bad

    5) recreate a new config:
    /usr/bin/Xorg -configure

    6) Move this new file into place:
    mv /root/xorg.conf.new /etc/X11/xorg.conf.d/vm.conf

    7) Switch back to the Text console by pressing typing 'exit' and Enter. Then type Ctrl+Alt+F1
    8) Log into the TUI console by supplying the root password for the 'Administrator' login.
    9) "Launch Graphics-mode Console" by pressing F2 or by pressing <Enter> with that option highlighted.


    But the real magic is having to change/add "vga=791 nomodeset" and bam screen shows up. so far only edited during boot have to hardcorded it I guess.


    System:
  • Motherboard: XFX MDA72P7509 AM2+/AM2 NVIDIA nForce 750a

  • CPU: AMD Athlon X2 x64 2.5Ghz

  • RAM: 8GB OCZ 800Mhz DDR2

  • 2 NIC: TP-Link TG-3468
  • The reply is currently minimized Show
    Your Reply