Ubuntu: monitor turning off during boot?


Recommended Posts

Basically I've decided to install linux on my oldish PC downstairs for my mother to use.

Installation was fine, but I seem to have a problem now.

When I turn the computer on, everything happen as it should up until where the boot screen starts. Sometimes It will boot as it should, but most of the time it will not. I usually a blank screen, followed the monitor turning off. Nothing I do makes it turn back on again (unless I restart the PC). It's not the monitor as it works with my other PC (and I've tried my other monitor with this PC and the same happens).

And I don't think its the video card as it worked fine with windows 98 on the same pc.

I've tried Ubuntu and Xubuntu (as it should be faster on older PC's), but the same thing happens. Any ideas?

It's using a Radeon 9200 btw, and I've tried both VGA and DVI.

thanks

Edited by WelshBluebird

Try this if you can. It may help since it turns off all of the power saving features.

  Quote
Edit your /etc/X11/xorg.conf in root mode and add the following lines:

Section "ServerFlags"

#other options can go here

Option "BlankTime" "0"

Option "StandbyTime" "0"

Option "SuspendTime" "0"

Option "OffTime" "0"

EndSection

Under this section just add the "false" after "DPMS" like it shows here.

Section "Monitor"

#other options can go here

Option "DPMS" "false"

EndSection

Right before I tried that, I took out my wireless card, and it seems to be working fine now. Could be a coincidence though, so I'm going to try it with the wireless card back in it now.

Thanks for the input though, I may need a little more help if it won't work with the wifi card (it needs to use wifi, as the distance between the pc and the router is too much for a cable).

edit - so much for that. Put the wifi card in, didn't work. Taken it back out, and still the monitor turns off.

Will try what you suggested if I can get the thing to boot.

Edited by WelshBluebird

If the screen "shuts off", chances are that the video card is outputting a video mode/frequency that the monitor cannot handle.

The quickest, easiest way to toggle resolutions in Linux is to use CTRL + ALT + [num pad plus] or [num pad minus] to step through the allowed modes until you get one that works (usually just a couple times will find one for you).

Hi,

I also have been having the same problem, both with the alt cd and normal live cd both 64. I have tried to run recovery mode and can get to the root command line or whatever its called (im a complete noob, this is my first linux install). I tried to install the nvidia drivers but the program asks me to go into init 3 and then the problems starts again. This time though my monitor flashes a few times and then goes blank but does not turn off.

I also tried to to go to the file "etc/X11/xorg.conf" but when i run recovery mode the file is not there, maybe this is my problem but since this is my first ever install i have no idea, i wouldnt even know how to edit this file if it was there.

I would be very grateful if you have any sugestions.

By the way i have 2 nvdia 8600 GT cards which i normally run in sli mode in windows.

First thing I would suggest to you is to not use the procedure from the nVidia site. While it does work, it does put Linux 'newbies' into modes that they will not be familiar and/or comfortable with.

Get your Linux to boot normally (with default video drivers), then use your package manager to point to the nVidia drivers, and install that way. No mess. No fuss. And keeps itself updated when you update your system. (Y)

Many thanks for that, i shall keep that in mind, problem is i cant get into Ubuntu in the first place even with the default video drivers, my screen just turns itself off or i get a blacnk screen. I only tried to install the nvidia drivers to try and resolve the problem.

i tried to re-install again but the problem is still the same, i tried the alt cd and installation went fine but when you chose to load Ubuntu the screen turns off again. I tried the CTRL + ALT thing but that has not worked. Do you think having 2 graphics cards with SLI bridge on could be possibly causing the problem? if not i have no idea what to do next, i guess ill just have to keep looking.

I have managed to find a few things that have worked for other people but not for me, some suggest changing the splash to nosplash in the GRUB booloader GUI. Others have pointed to editing the menu.lst in the boot directory but when i view mine it completely empty and i dont have a xorg.conf file either.

I know how to navigate through the different directories and edit file using nano now but im now at a complete loss.

Just to confirm what is happening and what ive tried:

I cant run the LIVE x86 amd 64 CD, it just hangs on a blank screen but the monitor remains on

I can install Ubuntu from the alt CD and install seem to go ok uo tp the point it asks you to remove the disk and reboot computer.

Just after the bootloader GUI after selecting Ubuntu the screen turns itself off but the computer seems to carry on loading

I have tried running reovery mode and can get a command prompt, as soon as i type init 3 etc Ubuntu starts to load but then the screen flashes a few times and goes black but stays on

I have tried using the CTRL+ALT+ -/+ to change resolution but nothing, also when i try to use CTRL+ALT+F2/F3/F4 etc i cant bring up any other consoles, CTRL+ALT+f1 is the only one available

xorg.conf is missing and menu.lst is missing.

My system is: AM2 6000, 320gb sata hd, corsiar 2gb 6400 memory, 2 x PCi-E Nvidia 8600gt running in SLI.

My dad has just installed with no problems and since we are both jsut starting to get into linux we want to run the same Linux if possible and i been told Ubuntu is a nice version to start with.

If you can help, thank you in advance.

Peter, I'm pretty sure the nvidia cards are your problem. I have 3 different PC's in my house, each with a different nvidia card, and I have yet to have any distro be able to boot into any sort of graphical interface by default. My suggestion is in the terminal type "sudo dpkg-reconfigure xserver-xorg" answer the questions, and make sure to choose as your driver "vesa" (I've never had the opensource "nv" driver work) Once that's working and you have , enable the restricted drivers, and back in the terminal do "sudo nvidia-xconf". That should set you up for good drivers and all. Hope this helps, and good luck.

Many thanks for that Mitch,

I did find that on another post and i think i set the drivers as VESA. Does that "enable restricted drivers"? I went through the xserver-xorg thing but its possible that I did something wrong in there.

As the only way to get a terminal is through recover, could this be a reason for my boot.lst been empty and xorg.conf missing?

I have also noticed that after you start recovery from the boot GUI you see the text showing whats its doing, An error does show but its so fast that i cant read it properly, i think it has something to with the PCI-E slot, is there a log file somewhere that would tel me what this error is?

this is getting silly now.

I've tried around 5 distro's, and either they don't detect my wireless card, or will choose randomly not to boot.

If it won't boot, the splash screen of the distro will come up. It will start to load the OS, but then the monitor goes blank saying "no input". I've tried it on my other monitor too, so thats not the issue. Any idea? I can kinda see why linux isn't mainstream now.

Yeah the new nvidia cards are a problem with Gutsy. This fix from the Ubuntu forums worked for me which I will copy here:

  Quote
I found a solution that worked for me on kubuntuforums:

(before I did what follows, I used StartupManager to set the boot-splash resolution to 1024x768 16-bit)

edit /etc/initramfs-tools/modules

add the following

vga16fb

fbcon

vesafb

edit /etc/modprobe.d/blacklist-framebuffer

comment out the following (prefix with #)

blacklist vesafb

blacklist vga16fb

last but not least, run the following in a terminal

sudo update-initramfs -u

http://ubuntuforums.org/showpost.php?p=363...amp;postcount=9

This enabled all simple output (not sure of the technical term, ie. without nvidia drivers) to work including the boot screen and ttys. Remember to actually use startupmanager like the post says because I didn't and it broke Gnome somehow.

Ubuntu is probably the best distro for getting wireless to work. In fact I first heard of Ubuntu because of its good wireless support, even though it is all a hack really (a bit like windows).

  • 10 months later...

Something really awesome about ubuntu 8.10 is that it can be installed from windows, so what you can do is:

1) format your pc and install all drivers

2) download ubuntu 8.10, burn it, and run it from windows

3) with just one click you'll get ubuntu installed

4) your system will reboot and will run the live cd (just select there to boot from the next booting device)

5) you will be asked to start from ubuntu or windows (select ubuntu)

6) the system will finish the install

7) there you have ubuntu with all drivers installed

that's the way I did it and that's how it worked for me pretty awesome!

Edit:

btw... http://www.ubuntu.com/getubuntu/download

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Subscribers who pay for Higher Tier pricing (and wealthy power-hungry wh0res in general) don't GAF about the value or having a conscience for their actions/decisions/impacts. They want POWER and authority to do WTF they wanna do, no matter how petty, ludicrous, wasteful, damaging, or useless. Sadly, there are many power-hungry folks out there than truly admit it! They truly believe that their banal requests for Wikipedia regurgitate is truly an academically deep thought experiment warranting any of their oft-untapped Thinking Model usage tokens. As the saying goes, Ya Can't Change Stupid (no matter how wealthy they are or appear to be).
    • New Windows 11 25H2 build moves more Control Panel elements to the Settings app by Taras Buria It is a busy day for Windows 11 Insiders, as Microsoft just dropped a trio of new preview builds in the Dev, Beta, and Canary Channels. Windows 11 build 26200.5742 (Dev) and build 26120.5742 (Beta) are now available for download, with more Control Panel elements making their way to the Settings app in a more modernized form. There are also traditional bug fixes and a redesigned mobile device companion for the Start menu in the Dev Channel. Here are the details. Both Dev and Beta builds introduce new language and date/time options in the Settings app, which previously required using the old Control Panel. Those include the following: You can now add additional clocks from Settings > Time & language > Date & time under the collapsed section which can be expanded for “Show time and date in the system tray”. For those unfamiliar with the feature, these additional clocks display in Notification Center, as well as the tooltip when hovering over the clock in the taskbar. You can now change your time server from Settings > Time & language > Date & time, under “Additional settings”. The formatting settings for date and time have moved from Settings > Time & language > Language & region to Settings > Time & language > Date & time, and you can now change your AM/PM symbol from here as well (along with other existing formatting settings). You can now change number and currency format from Settings > Time & language > Language & region, under the “Region” section. If you’d like to enable Unicode UTF-8 for worldwide language support, there is now a toggle for this under Settings > Time & language > Language & region, under the “Language” section. If needed, you can now copy current user language and region settings to welcome screen and system account, as well as new user accounts, from Settings > Time & language > Language & region, under “Additional settings”. The setting for character repeat delay/rate has moved to Settings > Accessibility > Keyboard. The setting for cursor blink rate has moved to Settings > Accessibility >Text cursor. Keyboard character repeat delay/rate is used to control the character repeat duration and repeat frequency. Cursor blink rate is used to control the cursor blinking frequency. Also, Microsoft redesigned the dialog when the system cannot open a program. And, if you are testing Dev builds, you will get a redesigned mobile device companion in the Start menu, which now lets you scroll to access more recent activity, such as messages, calls, photos, updates, and more. Here is the list of fixes that are gradually rolling out to Windows Insiders with the toggle on: [File Explorer] Fixed an issue where some of the icons in Details, Preview, and navigation panes of File Explorer weren’t properly mirrored when Arabic or Hebrew display languages. Fixed an issue where the tooltips in File Explorer might unexpectedly stay visible. Fixed an issue where duplicating a tab in File Explorer on a maximized window would result in a black flash. Improved support for text scaling on desktop icons, addressing an issue which could lead to overlapping icons and text. Fixed a couple cases where Narrator was unexpectedly not announcing actions in File Explorer (when using the “create new” library option, and when expanding details while copying files). Made some more performance improvements – particularly to help the performance of launching cloud files and loading context menus. [Start menu] Fixed an issue for Insiders with the new Start menu, where they might unexpectedly see a category generated for every letter of the alphabet with blank icons, when opening the Start menu in the “All” section after updating to the previous build. Fixed an issue where Visual Studio wasn’t showing in the correct category. [Task Manager] Fixed a few issues impacting Task Manager reliability, including a recent issue which could cause Task Manager to freeze when going to the performance section for some Insiders. Fixed a few issues impacting accessibility – including adjusting minimum field sizes, improving contrast for the column headers on the Details page when contrast themes are enabled, and addressing a focus issue with the ‘Select Columns’ dialog on the Details page. [Input] Fixed an underlying issue where if you tried to type Chinese with an IME after copying something with CTRL + C could result in the first character getting dropped. Fixed an issue where if you were typing on the touch keyboard with the Changjie, Bopomoji, or Japanese IME wouldn’t work if you had switched to using the previous version of the IME. [Settings] Fixed an issue where if you attempt to add a security key under Settings > Account > Sign-in options could result in Settings crashing. [Other] Fixed an underlying issue with dao360.dll resulting in some apps crashing after the last two builds. Fixed an issue causing a small number of Insiders to experience bugchecks with SYSTEM_SERVICE_EXCEPTION in the latest builds. And here is the list of known issues: [General] Some Windows Insiders may experience a rollback trying to install this update with a 0x80070005 in Windows Update. We’re working on a fix for Windows Insiders impacted. If you are impacted, using Settings > System > Recovery > “Fix issues using Windows update” may resolve the issue. [Click to Do (Preview)] The following known issues will be fixed in future updates to Windows Insiders: [NEW] After updating to Build 26120.5742, text and image actions in Click to Do may not work and Click to Do may crash. This issue will be fixed in the next flight. Windows Insiders on AMD or Intel®-powered Copilot+ PCs may experience long wait times on the first attempt to perform intelligent text actions in Click to Do after a new build or model update. [Start menu] [NEW] For Insiders with the new Start menu, the layout may temporarily show a smaller Start menu (ex. 6 columns of pinned apps instead of 8). This issue will be resolved shortly, and the larger layout will be restored. [File Explorer] In dark mode, the red color used for a low space drive in This PC may be unexpectedly light colored in this build. Some of the other colors may also be incorrect, including that black is used for space remaining instead of a more visible color. [Live Captions] Live captions may crash when attempting to use live translation on a Copilot+ PC. [Xbox Controllers] Some Insiders are experiencing an issue where using their Xbox Controller via Bluetooth is causing their PC to bugcheck. Here is how to resolve the issue. Open Device Manager by searching for it via the search box on your taskbar. Once Device Manager is open, click on “View” and then “Devices by Driver”. Find the driver named “oemXXX.inf (XboxGameControllerDriver.inf)” where the “XXX” will be a specific number on your PC. Right-click on that driver and click “Uninstall”. You can find the official announcement here (Dev) and here (Beta).
    • Word can now read you document overviews like podcasts by Taras Buria If you have a big document and no time to check it, the latest Word feature will help you get it done. Microsoft announced that Microsoft 365 Copilot in Word can now read aloud document overviews, letting you listen to them on the go like podcasts or audiobooks. In addition to reading aloud document overviews, Word lets you customize the experience with reading speed controls, the ability to jump back or forward to key parts of audio, pause, and even save the recording to OneDrive to listen to it later or share with someone else. Voice document overviews are now available in Word on Windows (version 2506, build 18925.20138) and Word for the web. If you have a Microsoft 365 Copilot license, you can try it out by opening a document, clicking the Copilot button in the Home tab, and asking the AI to generate an audio overview. Once the overview is generated, Copilot will present you with a media player and playback controls, such as speed, jump forward/backward, and pause. To save the recording, click the three-dot button and select "Save to OneDrive." Finally, you can access previously-generated overviews in your Microsoft 365 Copilot chat history. For now, audio overviews work only in English (Microsoft promises to add more languages soon), and they require a Microsoft 365 Copilot license. There are also two other limitations: Audio overview only works for online files that are in OneDrive and SharePoint, and not local files that are on your system or external drives. Files require a minimum of 100 words to generate an audio overview. In case you missed it, Microsoft recently announced that the new GPT-5 by OpenAI is now available in Microsoft 365 Copilot, giving you a more powerful and modern AI assistant to help you work with documents. GPT-5 is also available in the Microsoft Copilot app on computers and mobile devices.
  • Recent Achievements

    • One Month Later
      Jaclidio hoy earned a badge
      One Month Later
    • Week One Done
      Yawdee earned a badge
      Week One Done
    • Week One Done
      eugwalker earned a badge
      Week One Done
    • First Post
      Ben Gross earned a badge
      First Post
    • One Month Later
      chiptuning earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      635
    2. 2
      +FloatingFatMan
      176
    3. 3
      ATLien_0
      142
    4. 4
      Xenon
      120
    5. 5
      wakjak
      108
  • Tell a friend

    Love Neowin? Tell a friend!