[SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

demarsjcd · 2011-11-05 06:26:13

I have searched all over the internet with another computer, because mine is totally f'd. I should have learned not to use third party install from my previous problem with uninstalling gtk. I did a number of modifications so I really dont know where this problem stemmed from.

I have a acer aspire one with liquorix.
Heres what happened:
I ended up going to these two sites and doing these installation.

https://wiki.archlinux.org/index.php/Acer_Aspire_One
I did these modifications that are listed below:
Power management
Regulating the CPU fan(acerhdf)

and this website:
http://wiki.debian.org/DebianAcerOne
Screen resolution: 11 inch model (I think this might be the problem because there is no boot screen after bios. All I get is the welcome to grub and then it goes black with no list of OS')
Touchpad
Faster Graphics Rendering
Quiet Fan
I also think I installed lenny's OS but not sure about what exactly it was.

This problem didn't start until I finally restarted my computer after doing all those installations. I am dual booting with this laptop and I can get hear the fan running, Also I noticed that the shortcut keys(acer specific) keys work such as screen disable and screen brighten and darken.
I know this was stupid to do and I have learned my lesson. So please no critizism. I have been to pretty much every website that I could google and beyond that. I would just like some step by step guide on how I might fix this. I also tried flashing my bios to a newer version to no positive outcome. Thanks in advance!

Last edited by demarsjcd (2011-11-09 18:38:00)

orionthehunter · 2011-11-05 07:07:10

If you have your data backed up, just reinstall. Or will a liveCD not even boot?

demarsjcd · 2011-11-06 02:35:06

I dont think I have it backed up unless it does it automatically. Live cd doesnt work. I think its because of grub resolution set too high.

tmillic · 2011-11-06 07:07:27

Grub shouldn't affect a live-CD though.
You say you were dual-booting. I'll assume the other OS was a (microsoft) windows OS. Hopefully, you don't have to resort to this last-ditch effort, but... Have you tried a windows boot/installation disk? If you boot an installation disk and choose to repair an installed system instead of installing, then use the fixmbr command at the prompt, you can at least boot into the windows part of your system after that. (If someone has a fix that can remedy the grub problem, that would be much better than any of these tips.)
If you had a separate home directory, it should help with a re-install of the linux OS after that point. You'll lose some settings, but not your items in the home directory.

demarsjcd · 2011-11-07 03:36:24

tmillic wrote:

Grub shouldn't affect a live-CD though.
You say you were dual-booting. I'll assume the other OS was a (microsoft) windows OS. Hopefully, you don't have to resort to this last-ditch effort, but... Have you tried a windows boot/installation disk? If you boot an installation disk and choose to repair an installed system instead of installing, then use the fixmbr command at the prompt, you can at least boot into the windows part of your system after that. (If someone has a fix that can remedy the grub problem, that would be much better than any of these tips.)
If you had a separate home directory, it should help with a re-install of the linux OS after that point. You'll lose some settings, but not your items in the home directory.

at this point I'm willing to do anything. I have windows 7 as my other OS. I dont have the windows boot disk because I dont have a cd player on the acer one. I have it on an external hard drive though. Its just hard to get a flash drive right now because I really dont have access to another computer. If I use the fixmbr command do I need the disc?

On another note, I am really suprised there aren't more people offering fixes or people that have had the same problem that I'm having. I'm not trying to be mean. It just seems that if it was as common as it was on ubuntu, then it is bound to happen on other linux OS'. Just a thought. Thanks for everyones help

This is whats on the ubuntu website that explains a simular problem that I'm having... http://ubuntuforums.org/showthread.php?t=1743535

I have no clue as to where to start with fixing this thing with a blank screen...

Are you having these problems?
- Error- "Cannot display this grahics mode"
- GRUB_GXFMODE-auto results in Blank screen problems on Startup? (this includes purple or black screen, flashing cursor, stuck at splash screen...)
- No Grub Menu?

Note: Keep checking back to this post and the next 2, as I'm trying to edit them with the lastest changes and workarounds.
Updated as of: 2011.10.22 (Check Post 2 for Table of Contents)

Preface
Linux distributions such as Ubuntu, basically and simplistically run in layers like this--> You have a Linux kernel running. On top of that layer, you have a terminal session- running to interact with other layers. On top of that, you have an GUI, Xterminal session, X-Wndows or also known as an Xsession running to have a visually interactive session running. In each version of Ubuntu (and of distro's) an honest and earnest attempt is made to make each new version easier to use for a new user, in a way that is pleasing to the eye. Each of these changes does mean underlying changes in how things relate to each other layer... on a base that is trying to cover a myriad of hardware combinations, that users will install that distribution onto. Sometimes all of these combiantions cannot be "foreseen." (For instance when a certain video card type is made by over a dozen different vendors...) These techniques are simular to the same problems unix and Xwindows...

Here is a short quick-reference of Linux short-cuts and hot-keys to help you get around and to help diagnose graphics problems in an Linux Xsession. Some are also helpful later in just everyday kind of tasks. Like I said, this is only an abbreviated list, but I included them here because they do come in handy in diagnostics and the correction of boot and video errors:

<Ctrl><Alt><F1>
Switch to the first text terminal. Under Linux you can have several (6 in standard setup) terminals opened at the same time. Terminals start as tty0 and go up from there. Most of the time the normal boot text console, that is present "under" the GUI or Xsession (in Ubuntu) is tty1, so you would press <Cntrl><Alt><F2> to get to it...

<Ctrl><Alt><Fn> (n=1..6)
Switch to the nth text terminal.

tty<Enter>
Print the name of the terminal in which you are typing this command.

<Ctrl><Alt><F7>
Switch to the first GUI terminal (if X-windows is running on this terminal).

<Ctrl><Alt><Fn> (n=7..12)
Switch to the nth GUI terminal (if a GUI terminal is running on screen n-1). On default, nothing is running on terminals
8 to 12, but you can run another server there.

<Tab>
(In a text terminal) Autocomplete the command if there is only one option, or else show all the available options.
THIS SHORTCUT IS VERY HANDY! This also works at LILO or GRUB prompt!

<ArrowUp>
Scroll and edit the previous command history. You can then use that command as is or edit it to change. Press <Enter> to execute.

<Arrow><Down>
As above, but go back to the next command in history.

<Shift><PgUp>
Scroll terminal output up. Work also at the login prompt in the tty text console, so you can scroll through your bootup messages to find errors and messages. Does not work to see terminal output that has been "cleared."

<Shift><PgDown>
As above, but scrolls terminal output down.

<Ctrl><Alt><+>
(in X-windows) Change to the next X-server resolution (if you set up the X-server to more than one resolution in /etc/X11/XF86Config). For multiple resolutions on my standard SVGA card/monitor, I have the following line in the file /etc/X11/XF86Config (the first resolution starts on default, the largest determines the size of the "virtual screen"):
Modes "1440x900" "1024x768" "800x600" "640x480" "512x384" "480x300" "400x300" "1152x864" Whichever resolution you have as first in this line will be the default.

<Ctrl><Alt><->
(in X-windows) Change to the previous X-server resolution.

<Ctrl><Atl><Backspace>
Linux Ubuntu version 10.10 and previous- Kill the current X-session.

<Alt>-<SysReq>-<k>
Linux Ubuntu version 11.04 and later- Kill the current X-session.

-- The "Linux shortcut keys" are just that, meaning Linux is already booted. to use them-- although "some" of them do work in the Grub CLI. *such as the <Tab> for autocomplete)

Basically, between the grub menu and the GUI GDM, where you are getting a blank screen the only short-cut keys that "may" be available are the <ctrl><alt><F1 the F6> keys and <ctrl><alt><F7> key... which I mentioned, may not work even if you were not having graphical problems.. But if they do, you have some options.

General
Yes, with every new release of a distribution of Ubuntu, there seems to be similar and reoccurring problems that arise with "graphics" when trying the run a LiveCD and after the initial install and fist boot. These are my notes that have help people through the last 5 releases of Ubuntu, up through Ubuntu Natty Narwhal 11.04.

Basically, we want to make sure that the Grub menu boots. then verify that the kernel is booting, then that the Xwindow Session starts and displays.

Troubleshooting Flow Chart
This is to break this down into steps:
Step 1. Do you have a Grub Menu?
- Yes: Go to step 2...
- No: Whiie booting, Press shift key (don't hold down) multiple times to see if the Grub menu will come up
- - If yes on Menu, go to step 2
- - If no, comment out /etc/default/grub/ GRUB_HIDDEN_TIMEOUT=00. and rerun grub-update (from a LiveCD)
- - - If yes on Grub Menu go to Step 2
- - - If No, reinstall grub and Start Step 1 from Beginning... Becuase it seems that Grub is not booting.

Step 2 "Does the Linux Kernel Boot?" At Grub Menu, go into edit mode and boot into a text console (see instructions below)
- Yes. Go to Step 3
- No. Messages will be verbose on what is loading, what are warnings and what are error messages. Shortcut keys will start to work as the kernel modules load. If if stops at an error, you will be able to use the shortcut navigation cuts to review the errors. Depending on the error, if it is a kernel error, you may be able to reinstall or renew the kernel image. If it is a device module, at least you have somewhere to go to reload that device module or driver.,,, Goal is to get a "booting kernel."

Step 3. From the Grub Menu, try to boot in Rescue mode/low graphics.
- If Yes, look for addtional drivers and install recommended driver.
- If No, goto Step 4 to verify that linux kernel will boot.

Step 4. Can you boot a graphical Xseesion from a text console session? From the command line type

Code:
sudo service gdm start- Yes No black screen/No problem... should boot straight from the grub menu.
- No. Reboot and start testing and changing gfx_modes and kernel boot graphical modes, still booting into the text console before you try to start an Xsession. Going this way, you will have more of a possible chance to be able to toogle between a graphical session or text terminal session (sometimes). ...and at a text console, at least you have the abilty to install files and make changes to config files. And if you can get back into a command prompt, you could then stop the gdm service that is locked.

You can stop the gdm service via

Code:
sudo service gdm stop

Digging and opening up the hood:
If you can successfully boot grub, you are at least past point one. You can use grub as a jumping off-point- To test and see what graphical modes do work. Modes in Grub and where the linux kernel boots into does have a direct relationship to mode problems/successes when an Xorg Xsession starts.

Here, I can mention LiveCD'es. See post 3 for notes on using these techniques with a LiveCD. To me, a LiveCD in hand, is a very valuable diagnostics and recovery tool. If you can successfully boot and display a LiveCD on your PC... You are almost there.

A note about temporarily "editing" the kernel boot line...
This is an example of the menu entries of a Ubuntu menu item that will display when you press "e" in a Grub menu:

Code:
recordfail
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ext2
set root='(/dev/sdb,msdos3)'
search --no-floppy --fs-uuid --set=root 32939def-1f4a-4134-9b56-bed2319a9216
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro quiet splash vt.handoff=7
initrd /boot/initrd.img-2.6.38-8-genericThe Linux kernel boot line in indicated above in red.

Note: Something that has changed with Natty and GNU Grub 1.99~rc1... Look at the kernel boot line again, below:

Code:
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro quiet splash vt.handoff=7What we used to do to help display error measages was to remove the options in blue ( quiet splash ) and type in " nosplash --verbose text " at the end of the boot line to boot into a text console (and have all the messages displayed).

Notice the new option in green above (" vt_handoff=7 "). Remove this boot option now also. This new option (from the wiki)

Quote:
For a smooth boot process, we want to display something other than a black screen as early as possible and leave it on screen until the desktop is ready. vt.handoff=7 is part of this. We have the boot loader display an aubergine background (we wanted to have an Ubuntu logo as well, but there are problems with different aspect ratios between the boot loader and the real system, so this is the next best thing). vt.handoff=7 then causes the kernel to maintain the current contents of video memory on virtual terminal 7, which is a new "transparent" VT type. The first time that the kernel is told to switch away from VT 7, either from Plymouth or manually (Alt-F1, etc.), these contents are lost and VT 7 reverts to text mode.

The upshot is that, when everything is working correctly, you get an aubergine background on the way out of the boot loader, then at some point Plymouth displays a logo and a progress indicator on top of that, and then the display manager comes up and smoothly replaces that with a login prompt.

So if we want to see all the error messages, we now also have to remove this from the boot line temporarily while trying to find problems.

So to boot into a text console to verify that the system is booting into Linux, we edit the above kernel boot line to look like this:

Code:
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro nosplash --verbose textAfter editing, press <cntrl><x> and it will try to boot the menu entries. If and after the kernel boots in text mode, you will have more options to change things going into an Xsession.

If the kernel didn't boot, check the displayed error messages. You may have a kernel image problem, where you may have to reinstall the kernel image... or a device driver/module problem.

If you can boot the linux kernel and you know the package name of the driver you need... Reboot and get into the grub menu, cursor to the main boot menu item. press "e" > go to the kernel boot line and append " text " to the end of the line. Press ctrl-x to boot ther kernel... it will boot into a text console mode. Login as you > install the driver via apt-get or aptitude...

Going on
If still no Xsession. I usually check the /home/username/.xsession-errors file for errors. where can see if there is a problem with loading a driver or in acThen I go to grub... Another log to now check is var/log/kernel.log to see if vmap allocation is running out of memory on startup (look at the nvidia tips).

If you are having problems not seeing the grub menu on boot, hold down the "shift" key.. even if the menu is set to "silent" or not to be shown, grub should be listenning for the shift key to interrupt the boot sequence. On some machines, holding the shift key down continuosly will cause a keyboard over flow-- if it does, pess the shift key multiple times instead. If it still doesn't bring up the Grub menu, commenting out /etc/default/grub/ line

Code:

# GRUB_HIDDEN_TIMEOUT=00sometimes helps with that... If it still doesn't bring it up after that, reinstall grub.

Uncommenting the line in the /etc/default/grub that says gfxmode=680x480 "should" work to see graphics in that mode... sometimes.

Here is where a lot of the "blank screen" problems arise:
If no setting is found in /etc/default/grub, Grub2 uses the resolution established in /etc/grub.d/00_header, which is set at default to auto. The else on that is supposed to be that, but if it errors, sets to text mode, which is why some graphics errors just error out to text mode. If it "thinks" it is in a valid mode but actually isn't (or is actually locked up without returning that error code) then it is simply blank.

In simple terms- In "auto" or if a specific graphics mode is not specified "explicitly", it tries different modes until the first one is found that does not return an error code. If that mode happens to be out of range and locks up before it returns that error code, you get a blank screen... If the mode specified is a known supported resolution mode by heigth and width (ex: 800x600), it is still going to roll through the different color depths and it still may be going out of range by an unsupported color depth setting it is trying...

One way to test this would be to press <ctrl><alt><F1> or <cntrl><alt><F2>, then <ctrl><alt><F7>, which is supposed to be the "toggle hot-keys" between a graphics session and a text session... but I'll tell you now, that crtl-alt-F2 does not work on some of the boxes I have here that have "no" existing problems with graphics... So that may not be a valid test. Booting as above instructions noted > Into a text console if this didn't work. This will narrow things down to verify that the kernel has booted and that there “is” an Xsession problem.

To try different kernel boot options, using "e" at the grub menu. Go to the kernel boot line... try these options (one at a time/not together):

Code:

nomodeset
xforcevesa
i915.modeset=0 xforcevesa
vga=xxx # Note- where xxx is a vesa mode that your card supports, such as 771These options, again, would be added near the end of the line, after the kernel name, For other boot options, look here:
http://ubuntuforums.org/showthread.php?t=1613132

Another thing you can try is to drop down the the grub CLI (command line interface) via pressing "c" while in the grub menu... While you are in the Grub CLI, you can use it to test the variable setting, set them to other settings and to see what modes your video supports.-- instead changing things (hard edits) and rebooting to see if it worked... Just just "set" and "unset" viables to change your environment variable from the command line. Such as to set the screen resolution, you should set the variable $vbe_mode before loading vbe and/or gfxmterm (default mode is 0x101 i.e. 640x480 8bpp) Test your graphics... What I last said translates to

Code:

set gfxmode=640x480
load_video
insmod gfxtermFrom the CLI you could use

Code:

GRUB> echo $linux_gfx_modeto see what the video mode it is currently set to... It will most likely be set at "keep". If you then

Code:

echo $gfxmodeit will most likely say "auto' which is the default.

code:
Then use

Code:

GRUB> vbeinfoto get the video modes as grub sees them on your hardware. Get ready with your "pause" key as may get as many as 3 screens of info will go by faster than you can possibly read. When ready to read more, hit the enter key. "vbetest" will tell you what video mode in hex it is currently set to. You can then use these modes in the kernel boot line and append/adding a vga=xxx, where xxx is the mode. Note that this XXX value must correspond to a resolution that you had set the gfxmode to.

Note: The 1915 driver and natty currently have know bugs with vbeinfo and the "vga=xxx" kernel switch. Please use hwinfo (below) instead, then see the i915 notes at the end of this post.

From a Linux text console session, you can use

Code:

sudo hwinfo --framebufferto find vesa video modes that your installed card supports. you may want to use

Code:

sudo hwinfo --framebuffer | moreif the info is more than one page... Or

Code:

sudo hwinfo --framebuffer > ~/video_results.txtTo save the result to a file in your Home Directory. If this program in not already installed, you can easily install in via

Code:
sudo apt-get install hwinfoThis utiltity is very small and it well worth the few bytes of space it uses and the few seconds it takes to install.

If you also use
code
sudo hwinfo --monitor
It will display the modes that the monitor displays.

Alternate method:
If you use the application startup-manager, installed via

Code:
sudo apt-get install startup-managerit will make edits to the grub files for you... For instance, changing the following settings in Startup Manager to:
display resolution 1024x768
color depth 16 bit

and under the advanced tab:
bootloader 1024x768

Changes to grub file section 00_header, line that says "set gfxmode=auto" to "set gfxmode-1024x768" and then add/appends vga-758 to the kernel boot line in 10_linux section... Unfortunately for most who are reading this thread, this program will not help them "until" they get a working graphical Xsession. Once they do, they could use this program to tweak their session or to Customise the default "startup" of their Grub Menu.

After you make changes to any grub file, remember to run update-grub to pick up the changes.

On the info returned from

Code:
sudo hwinfo --framebufferIt returns modes that your installed video card supports in a hex number format. For instance it may say 00x0303, which is 771 decimal. You can then use that the converted decimal number in the kernel boot line with a "vga=xxx" switch such as

Code:
linux /boot/vmlinuz-2.6.38-8-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro nosplash vga=771 textYou can use the info returned in grub using vbeinfo the same way... If you are not sure what to do with these results, post them here, ensuring that you highlight the results and press the "#" button to wrap the results with code tags

All this is too find a Mode that your hardware supports so that you can set them manually. Once you find a mode that work, then you can make it permanent.

Now that I found something that works, how do I make it permanent?
In a terminal:

Code:
cd/etc/default
sudo gedit grubEdit the line "GRUB_CMDLINE_LINUX_DEFAULT". Add your new options, for example:

Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=771"Now in a terminal run

Code:
sudo update-grubNow each time you update grub and in configures the files, it will pick up these changes.

Noteworthy Notes

Notes on for some Laptops:
Will inform your BIOS to use provisions for Linux:

Code:
acpi_osi=LinuxWill fix some backlighting Problems:

Quote:
Originally Posted by glococo
Hi,
The best workaround for solving backlight ISSUE was for me:
Autorun "setpci -s 00:02.0 F4.B=00" each boot.

Steps:
1) edit rc.local

Code:
gksudo gedit /etc/rc.local2) Add the command before EXIT 0

Code:
setpci -s 00:02.0 F4.B-03) Restart.
You should now be able to boot in UNITY where nomodeset was unable.

Notes about nvidia cards and SLI
The "nomodeset" kernel bootline switch usually works for most nVidia cards, but now all.

Especially for nvidia cards, I usually just into a text mode by going to a text console via grub edit ('e") append " text " to the end of the kernel boot line and boot{"ctrl-x') and after a login type

Code:
sudo apt-get update
sudo nvidia-installer --uninstall
sudo apt-get remove nvidia-*
sudo apt-get install 'uname -r'
sudo apt-get install nvidia-current
sudo nvidia-xconfig(Note- This example assumes that you have a GeoForce 6xxx or better card) then try to start the GUI via
Code:
sudo service gdm startFor Unix and Linux, some versions of Xorg will not boot when there are multiple physical instances of the same video card installed (which bridged SLI cards are) until the proprietary video driver is installed. If you have SLI and a LiveCD will not boot: Remove one SLI card > Boot the LiveCD and install the system > Install the video drivers... Install the second physical card.

There is another problem coming up with natty and the Geoforce 9800 where the kernel is misallocating and running out of allocated addressed video memory while trying to boot. This has been resolved by allocating more memory by adding "vmalloc=192MB" to the kernel boot line.

ATI TIPS:
Note that some ATI cards need flgrlx and some do not... If not then this workaround sometimes works:

Steps for ATI users:

1. Get to a terminal session or TTY Console

2. Edit the sources list to include the the Conical Partner Repo's:

Code:
sudo vim /etc/apt/sources.listThen

Code:
sudo sh /usr/share/ati/fglrx-uninstall.sh
sudo apt-get update
sudo apt-get install fglrx
sudo apt-get upgrade
sudo reboot"The above only works for some but not all, depending on what card you have and whether it actually is supported by additional drivers (proprietary). All at the moment, mostl seem to need "nomodeset radeon mode=X", where x= 0 or 1... Some ATI cards are not working with the current natty kernel, but are working with the older 2.6.37 kernel or the proposed 2.6,38.9 kerne (please see post 2)l

Intel i915GM
There is a known bug with this chipset and Natty. Some of the workarounds include using "i915modeset=0" and some "i815modeset=1" in the kernel boot line and going to /etc/default/grub to

Quote:
Andy Whitcroft wrote on 2010-12-02 as part of Launchpad Bug https://bugs.launchpad.net/ubuntu/+s...x/+bug/683775:

As a work-around we can turn this off by adding the line below to /etc/default/grub and running update-grub:
GRUB_GFXPAYLOAD_LINUX=text

There is also an upstream Debian Bug with this driver that says if you try to use a "vga=xxx" switch on a Linux 2.6.x kernel and this driver, you will get a black screen. It further says if you use anything besides the i915's driver's internal framebuffers, it will get a black screen. So-- the "i915modeset=0" also has to be set in the kernel boot line to turn off KMS.

Notes on KMS:

This thread was inspired by the addition of this Wiki entry and how it's application "changed" how things worked or failed:

Quote:
Quoted from the Ubuntu Wiki (editted):
KernelModeSetting

Kernel mode-setting (KMS) shifts responsibility for selecting and setting up the graphics mode from X.org to the kernel. When X.org is started, it then detects and uses the mode without any further mode changes.

Configuring KMS

KMS is enabled by default for the -intel, -ati, and -nouveau drivers. It is not available for any other drivers at this time.

If you need to manually adjust mode settings, the video= boot parameter is used. For example,

video=LVDS-1:d -- Disables the LVDS
video=VGA-1:e -- Enables VGA-1

Turning it off

If you need to turn KMS *off* do the following depending on the hardware in question:

# ATI Radeon:
echo options radeon modeset=0 > /etc/modprobe.d/radeon-kms.conf

# Intel:
echo options i915 modeset=0 > /etc/modprobe.d/i915-kms.conf

# Nvidia (this should revert you to using -nv or -vesa):
echo options nouveau modeset=0 > /etc/modprobe.d/nouveau-kms.conf

For some users (particularly users with encrypted volumes) KMS is enabled very early in the boot process and in order to pick up these changes you need to run sudo update-initramfs -u.

For more "detailed" testing and configuration techniques and options (geared more for the advanced level user), please read this Wiki pages:
https://wiki.ubuntu.com/X/Config/Resolution
https://wiki.ubuntu.com/X/Config#hal

And for a more detailed, consolidated list of Kernel Parameters, please see:
http://www.kernel.org/doc/Documentat...parameters.txt

If All Else Fails? See Post 2--
__________________
Multi-Boot= Various flavours of Windows, Linux and Unix... Ubuntu user # 33563, Linux user # 533637
Boot Info Script courtesy of community member meierfra

machinebacon · 2011-11-07 05:00:00

The problem can be circumvented if you disable the Graphics Mode by adding GRUB_GFXPAYLOAD_LINUX=text to /etc/default/grub - this is also the file where you can add the boot parameters like nomodeset etc.
To do so, we have to use some kind of LiveCD and mount / chroot the partition which is affected.
As next as simple editing of the aforementioned file (mounted in chroot) and a update-grub2 on the affected partition (the location is very important!) will rewrite the new GRUB. If you need steps in detail, let us know. I'm quite sure that this is the easiest way to get GRUB shown again.

Edit: I haven't read the previous post, it's a bit too much big_smile

Last edited by machinebacon (2011-11-07 05:05:02)

demarsjcd · 2011-11-07 06:46:33

machinebacon wrote:

The problem can be circumvented if you disable the Graphics Mode by adding GRUB_GFXPAYLOAD_LINUX=text to /etc/default/grub - this is also the file where you can add the boot parameters like nomodeset etc.
To do so, we have to use some kind of LiveCD and mount / chroot the partition which is affected.
As next as simple editing of the aforementioned file (mounted in chroot) and a update-grub2 on the affected partition (the location is very important!) will rewrite the new GRUB. If you need steps in detail, let us know. I'm quite sure that this is the easiest way to get GRUB shown again.
Edit: I haven't read the previous post, it's a bit too much

LOL. If you give me a step by step that would be awesome. I kind of realized that I needed to edit one of the files but I have no idea where to start. I didnt even know you could edit a file through command. Sorry about the long post, I didn't realize until i scrolled down how long it was. Thanks.

Edit: My flashdrive is MIA and I was wondering if I could use a microsd card to use as a live cd? Otherwise I guess I would have to borrow one or buy one.

Last edited by demarsjcd (2011-11-07 06:48:25)

machinebacon · 2011-11-07 07:16:56

If you can boot from a removable media depends on the computer, in particular check the BIOS for "Boot Order"

http://crunchbanglinux.org/forums/topic … -sd-cards/

The question is also if you can actually create a bootable microsd card (with unetbootin or LiveLinuxInstaller? I have never tried this)

A small 1GB USB stick will be ok. Anyway it is a good idea to have Linux on a stick for rescue or distrohopping purposes.

Edit: The chroot is described here nicely: http://karuppuswamy.com/wordpress/2010/ … ue-prompt/

After Step 6 (chrooting the file system) you would edit the /etc/default/grub and add the 'payload' line, then proceed with Step 7.

If you need details, write wink

Last edited by machinebacon (2011-11-07 07:26:14)

demarsjcd · 2011-11-09 18:37:11

Thanks machine! I got it working again by just using the live cd. Apparently the live cd that I used before wasn't right so I tried a new one and it worked. I just ended up do a new install just so I wouldn't run into that problem again.

CrunchBang Linux

SEARCH

#1 2011-11-05 06:26:13

[SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

#2 2011-11-05 07:07:10

Re: [SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

#3 2011-11-06 02:35:06

Re: [SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

#4 2011-11-06 07:07:27

Re: [SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

#5 2011-11-07 03:36:24

Re: [SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

#6 2011-11-07 05:00:00

Re: [SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

#7 2011-11-07 06:46:33

Re: [SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

#8 2011-11-07 07:16:56

Re: [SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

#9 2011-11-09 18:37:11

Re: [SOLVED]Screen goes black just after "grub, welcome" acer aspire one!!

Board footer