Ubuntu :: Suspend Not Working, And Grub Menu Gone?
Mar 3, 2011
I have two problems, that I can live with, but they are just annoying for tha afact that I don't know how to fix them.1. My suspend does not work. Hibernation works - after I turn on after the hibernation, screen is blank, I have to move the mouse for the login window to appear. For Suspend, I get to the black screen, but then nothing happens - when I move the mouse or Ctrl+Alt+Backspace, nothing. It is a laptop, if that makes a difference.2. When booting, I get a table of choices - the new kernel, the old kernel, memtests and the long gone windows partition. There is no /etc/grub/menu.lst and I've got no idea how to change this.
I just installed OpenSuse 11.1 alongside of Ubuntu 9.10. After finishing up the installation I find that I can't get into Ubuntu. I have tried adding Ubuntu to the OpenSuse /boo/grub/menu.lst but it doesn't seem to be working.
I have Debian Jessie 8.0 amd-64 installed. It is a dual boot system with Widnows 8.1 alongside. Both the systems work fine with a few glitches coming at times on jessie. But I assume it should get stabilised with time.
Problem is:
The usb keyboard is no longer detected until the GRUB stage crosses.
* This implies I am unable to press F2 to enter into BIOS * I am unable to chose Windows 8.1 by using arrow key on the keyboard.
When the default system (first in the grub list), in this case Debian is selected after time runs out then the keyboard comes back to life and works properly thereafter.
So far I have tried the possible solution given at [URL] .... but it did not work.
Some Information ================
$ lsb_release -a No LSB modules are available. Distributor ID:Debian Description:Debian GNU/Linux testing (jessie) Release:testing Codename:jessie
I am testing my crash recovery strategy for my linux system and I am having trouble with GRUB. I am basically restoring my backup (i.e. tar) unto a different hard drive, but I am having problems getting the machine to boot without me having to type the GRUB commands at the GRUB prompt that is presented when the machine boots up off the new hard drive. I have tried to restore the MBR in two ways (the 2nd one is the one that gets me to the GRUB prompt):
1. Get the MBR off the original drive and write it unto the new drive (all via dd), but that did not work at all: the machine hangs right away during boot up. It seems to hang right at the point where the BIOS tries to read the MBR.
Code:
On original drive:
# dd if=/dev/sda of=mbr+part.bin bs=512 count=1
On new drive (new drive is now in place of original drive):
reboot and remove FEDORA CD Using the 2nd option above, I get the GRUB> prompt during bootup. I can then boot into the system by issuing the commands that are in the menu.lst file, followed by the "boot" command. However, I would like for those commands to happen automatically, just like in the original configuration. It seems to me that GRUB is actually finding all its stage files because I doubt the GRUB program (the one displaying the prompt) fits entirely in the 446 bytes it has on the MBR. So, it must be loading its stage 2 (and stage 1.5??) files from my /boot partition. However, if GRUB is loading its stage files off the boot partition, why does it not load/read the menu.lst/grub.conf contained in the boot partition also?
my Setup is Fedora 14 x64 + radeon hd 4830 i've downloaded .run package from ati site with latest driver for x64 systems. installed it, but didn't edited grub.conf becouse i didn't understood anything there (probably didn't spent enough time to get things understand) Now i've lost possibility to enter my Fedora system. during boot it lost it's modern blue boot screen (with filling drop), it was replaced by standard old boot screen with triple-color stripe. after this boot screen monitor start blinking going on and off. and on last step i'm getting "Fedora 14 boot bla bla bla something" on screen. nothing works except Ctrl+Alt+Delete. system reboots showing successful daemons shutting sequence. How can i edit grub menu from initial grub screen is it possible to it's own 'e' option or 'c' from grub command line?
9.10 has no menu.lst file and hitting ESC to does not bring up the grub menu. How can we set bootup options or boot an alternate kernel? I would really like to set the resolution at boot time so that my console (Ctrl-Alt-F5, for example) has 80 columns instead of 40. (What a stupid default, gigantic Commodore-64-like text!) It would also be nice if the Login screen could be set to the resolution that I want.
In previous releases, there were ways to do this. In 9.10, I haven't been able to figure out how.
Is there a document explaining all of the radical changes?
9.10 has no menu.lst file and hitting ESC to does not bring up the grub menu. How can we set bootup options or boot an alternate kernel? I would really like to set the resolution at boot time so that my console (Ctrl-Alt-F5, for example) has 80 columns instead of 40. (What a stupid default, gigantic Commodore-64-like text!) It would also be nice if the Login screen could be set to the resolution that I want. In previous releases, there were ways to do this. In 9.10, I haven't been able to figure out how.
Running Debian Squeeze and OpenBox. I added the command: "gdm-control --suspend" to my OBmenu but nothing happens. When I run the command from the terminal, also, nothing happens. Yes, I did actually Google. Anyway, proper suspend command from the OpenBox menu?
I got ubuntu 10.04 lucid lynx along with windows (dual boot) and using Grub. On my computer, I have my C:/ (programs) and D:/ (data). I've never used my D:/ before that day that I've lost my windows partition on my grub menu. I usually use my D:/ with windows. The first time I used my D:/ to store data with linux, I lost my windows option in my grub menu. I'm not sure what I did wrong but I do want to restore my windows option in my grub menu.
After "fdisk -l",
I checked in /boot/grub and there is no menu.lst to modify. how I can get back my windows option in my grub menu ?
The first is I seem to have 3 GRUB installs. So whilst I update the one from my live session, the change does not appear in the boot up menu. I had installed 10.10 from a CD into a different partition (sda6), but that will not boot, so I have just deleted this and done another grub install and update. The kernel I am using has just been updated from 10.04 to 10.10 too, and it is this that I use and the Grub I have been working on (sda5).
When I start the computer the boot menu doesn't prompt, when I try to load it manually it doesn't prompt neither, it just reset the command line.The grub.cfg was generated by update-grub.It's really annoying to load the kernel manually each time the computer starts.
and I rebooted and grub menu not coming now. I have a dual boot with Win7. Ubuntu 10.04 is installed with WUBI. I can run WIN7 but can't run Ubuntu now.
I've got myself the curious situation where, when I boot the system, I can get grub to start, but it always drops to the prompt.
I can run:configfile /grub/menu.lst
and this brings up the menu with no problems, and from there I can boot the system to either linux or windows. What I don't understand is why it wont go to the menu in the first place?As far as I can tell, grub/Kubuntu got confused when installing, as each of the hd#,# settings in the menu.lst have needed tweaking to let the system boot. (e.g. windows is actually hd0, but the original install had it at hd2. Likewise linux is on hd1, but the menu.lst had it at hd0). I've happily tweaked these to make the system boot, but would appreciate any help in convincing grub to actually load the menu without me having to use the prompt.
I started another thread about this to get help booting into openSUSE after Fedora rewrote my bootloader and deleted all other entries. I managed to fix it but I never did find out why the following commands caused my system to boot to the grub shell instead of the grub menu.
Code: grub root (hd0,3) setup (hd0) quit reboot
Can anyone explain to me why these commands caused my system to boot directly to a grub shell? It's as if there were no /boot/grub/menu.lst files for it to use, but after I got everything back to normal, the files were still there.
If it helps, this is how the drive was setup before and now, except Fedora was on /dev/sda4 and has since been deleted.
Code: Device Boot Start End Blocks Id System /dev/sda1 1 262 2104483+ 82 Linux swap / Solaris /dev/sda2 263 13316 104856255 83 Linux /dev/sda3 * 13317 14621 10482412+ 83 Linux
I have a used PC that came pre-installed with suse 11.2.Unfortunately, I do not have the install disk to use in case of whatever.I already know that when configuring a dual boot with Windows and Linux, it is recommended to install Windows first.I do not have that luxury now as 11.2 is installed and GRUB is the boot loader.Question is, if I boot the Windows 98 install disk on boot, how to not mess up GRUB and still add Windows 98 to GRUB menu?
One hard drive only here. 98gb free.It seems that W98 install will overwrite GRUB in this situation - causing problems. Maybe not, I don't really know for sure.I just need to install windows 98 on the same hard drive and if possible, have suse and w98 visible on boot in GRUB.
I loaded GRUB, and now when I reboot it goes straight into the 'grub>' command line. Initially GRUB had the root as (hd0,2), whereas the boot is on (hd0,1)...(hd0,2) is my '/home' partition, and (hd0,1) is my '/' partition... So on a bootup I ran...
Code:
root (hd0,1) setup (hd0)
Now when I boot I still get the 'grub>' command line, but now the root is correct.
From 'grub>' I can type...
Code:
grub> configfile /boot/grub/menu.lst
GRUB will then show the menu, and I can click the listings to load them. All's fine, but why doesn't GRUB just load the menu.lst without my prompting? How can I automate this process of typing 'configfile /boot/grub/menu.lst' each time I boot?
Now i've lost possibility to enter my Fedora system. during boot it lost it's modern blue boot screen (with filling drop), it was replaced by standard old boot screen with triple-color stripe. after this boot screen monitor start blinking going on and off. and on last step i'm getting "Fedora 14 boot bla bla bla something" on screen....nothing works except Ctrl+Alt+Delete....system reboots showing successful daemons shutting sequence. How can i edit grub menu from initial grub screen is it possible to it's own 'e' option or 'c' from grub command line?
Karmic 2.6.31-22-generic, Asus M3N78-EM, MCE remote with USB/IR dongle, latest Bios, Bios PM enable and set for suspend S3. IT will suspend but I need to depress case power button for it to resume. I want to use my remote control, I also can not get it to resume from Keyboard/mouse (See Note Below). Only suspend and power button work.
$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I just built my new desktop yesterday, I got elementary Jupiter (built on Ubuntu 10.10) installed and running fine on it, everything works... except for when I tell it to suspend
Upon selecting suspend, the monitor goes black for all of about a second and then comes straight back to the lock screen, pretty damn irritating.
After suspending my computer, the battery icon doesn't work anymore (nothing happens when I put my mouse over it and it doesn't detect wether the computer is plugged in or not). Also, the brightness of the computer doesn't change when I plug/unplug the computer. All of that works fine before i suspend the computer.
Computer is an ACER Power F6, BIOS AMI F6, XPPro installed, C only 80 Gygabites, 2 Gyg RAM, 3000MHZ Pentium4.today I installed 10.0.4 from Canonical 32 bit, all was ok,I followed the suggested dual boot partition and proceedings,which gave XP 44 Gyga and Ubuntu 37 Gyga ,successfully finished install,rebooted and began updating and customizing with great zest as I was really happy about this new version. then I decided to make a break of an hour and thought : 'let's try now the suspend function as i read about it not working properly sometimes'.....so an hour later i tried to revive from suspension,but the pc remains utterly insensitive and black.Tried Del to get into BIOS,F12 to get to boot config,BART PE disk i made for an XP machine in the past, and tried to boot again from the live Ubuntu Cd .....all in vain.I suspect it might be the fact the BIOS was set by me for
1st Floppy 2nd CDROM 3rd HD or PenDrive
as this machine I inherited since a few days dates back to 2006 and has no burner only CD-DVD reader and Floppy is disabled in BIOS.After Ubuntu install the machine stopped for a long time on a black screen with white reading about errors during install,then I reset it and it seemed like a good install anyway.Apart from checking if the HD is still ok,what can I do or try in such a situation?
When I try either one I just get the lock screen where I have to enter my password to return to my session, but the computer never suspends or hibernates.
After upgrade from Hardy to Lucid, wireless card (Atheros Communications Inc. AR5212 ) was extremely slow and not really functional. I installed the madwifi driver following the instructions from Ubuntu Wiki and wireless works now. But, after suspend Network Manager nor Wicd could scan for any wirelss networks.
I found a workaround: in console, run "dhclient" and, magically, while the scan for Ip address is going on, suddenly also Network Manager starts connecting to my default access point!
EDIT: I found my problem--the box next to headphone box had been unticked, and I feel like a total doof for not having found that during my first two hours of trying to fix this. But I could still use some help figuring out my suspend problems issue--I've heard constantly turning a compy on and off is bad for it somehow.
A couple days ago I attempted to put my computer into suspend mode. When I used regular Ubuntu, this seldom worked. My hard drive would continue spinning, and the computer would not come out of this state until I cut the power and restarted. I thought it might be worth giving a try in Xubuntu, but I ran into the same problems, only this time, the audio would not work when I booted up.
I'm using the 64-bit version of Xubuntu, and this is a relatively fresh install (within the past two weeks) from the version 10.10 DVD, so I haven't had too much time to fudge up the settings yet, so I think it might not be entirely my fault. (: I've checked the hardware, and everything is plugged in and turned on, and I'm getting sound when I boot up Windows.
I may have done something afterwards, though. My first attempt at fixing the problem was to follow these instructions, but I really didn't understand entirely what I was doing. I tried fiddling around with the alsa mixer, but that didn't help me at all, and now it has even disappeared from the upper right-hand corner of my screen--on the toolbar. (If there's a way I could get that back and restore the default settings, [EDIT: I found alsamixer in the applications menu.]
I'd like to have audio working again, but I'm not really sure what's wrong or how to fix it. I'm still reading through Introduction to the Command Line, but as my previous attempt to solve this issue shows, I'm not smart enough to be afraid of entering commands in that I completely do not understand (yet).
I have ubuntu 10.04 installed. I have a problem when my usb IR receiver is connected, than suspend mode isn't working. System will jump into black screen and that's all. Only hard reset works. I tested this problem also on ubuntu 9.04 and situation is the same.Is there any way how to force suspend mode without "looking" on this device? Do you need any log file to trace reason of this problem ?
I have a headless 10.04 ubuntu server ( running at home. Because I am a student I want to save some power by suspending the server when I really don't need it (school, sleep etc.). I have gotten WOL to work for me, BUT the suspend does not work.
I have tried pm-suspend and s2ram, but they both have same result; I lose all control (seems like a freeze) from my SSH, but it does not disconnect, and the server responds to pings. But I cant connect via ssh, or use the fileserver or any of the roles it has. I assume there might be something locking it when it tries to suspend, but I really don't know where to start looking (logs and stuff). I have googled quite a bit, but almost all failed suspends are some funky laptop issues, and this is not...
