Debian Installation :: Fixing Grub2 On A EFI GPT System?
Nov 10, 2015
I installed Debian 8.2 first, then Windows 10 over it (I know, backwards, but I didn't wish to lose my customizations on Debian up to that point, and didn't realize until later that I wanted to Dual Boot). Running from a LiveCD of Debian 8.2:
Code: Select allsudo fdisk -l
Device - Start - End - Sectors - Size - Type
/dev/sda1 - 2048 - 116211711 - 116209664 - 55.4G - Linux filesystem
/dev/sda2Â - 116211712 - 116244479 - 32768 - 16M - Microsoft reserved
/dev/sda3Â - 116244480 - 232421375 - 116176896 - 55.4G - Microsoft basic data
/dev/sda4Â - 232421376 - 234440703 - 2019328 - 986M - EFI System
[code]...
That's where I am stuck. I'm a bit new to Debian & Linux still and I've never dabbled with Grub2, I imagine I can't mount /dev/sda4 because in chrooted into /dev/sda1 and it can't see /dev/sda4 at this point (what I'm thinking anyway). So I try:
Code: Select allroot@debian:/# fdisk -l
fdisk: cannot open /proc/partitions: No such file or directory/I imagine that's what it is, but I don't know a way around that. I want to dual boot Windows 10 & Debian 8.2 on a UEFI (or EFI?) system with a GPT Disk. No guide I have found for fixing Grub2 or getting Dual Booting working with Debian then Windows installed have covered both things at the same time. I just have to be special I guess.
I just installed Ubuntu 10.04 LTS on an external hard drive (USB connected) and I can no longer boot my Windows XP(SP3) from my internal C Drive. Grub gives me the list of boot choices, but when I choose the C drive, I just get these error messages:
GEOM ERROR For Realtek RTL8139(X)/8130/810X PCI fast ethernet controller v2.13 (020326) Client MAC ADDR: 00 13 D3 07 FD F5 GUID: FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF PXE-E53: No boot filename received PXE-NOF: Exiting PXE ROM
(The version of Grub is 1.98-lubuntu5). I don't have a Windows System CD to boot from, but is there something I can do from within Ubuntu itself?
I have been frustrated attempting to get Grub2 to boot a Debian Live system from hard disk. Have set aside a 4gb partition /dev/sda1 to contain the Debian Live and some other recovery tools. I actually have them all working from a 4gb USB stick successfully, but getting it to work on my HDD has proved challenging. On USB, I have PartedMagic, Gparted, Grml, and of course my standard 6.01 Squeeze. I have also managed to get the Debian Live booting from that USB stick. Very slick.
However, I can NOT get Debian Live to boot from my HDD; altho all of the others above boot fine. Have tried it two ways - one using an iSO image, which is how it is done on my USB stick. The other attempt is to copy the entire contents of the ISO to a directory.
Here are my directory structures:
debian_live_gnome_squeeze_i386- contains the following: debian-live-6.0.1-i386-gnome-desktop.iso initrd.gz initrd.img vmlinuz which is how it is laid out on my USB stick debian_live - contains the files from the ISO image The error I get is something like "panic unable to find live filesystem" My grub.cfg snippet for the two methods I have tried - the 2nd menuentry is similar to how it works on the USB stick.
menuentry "Debian 6.01 Live (on /dev/sda1)" { insmod part_msdos insmod ext2 set root=(hd0,msdos1)
[code]....
Probly don't really need to get it working since PartedMagic can do almost everything I need for recovery and I can use the USB for reinstall or whatever else.
Been using Linux for many many years but Grub2 is annoying the heck out of me at the moment.
My home desktop PC is set up as follows:
/dev/sda � 40GB 10k Raptor with Ubuntu 10.10 installed /dev/sdb � 500GB HDD formatted to ext4 /dev/sdc � 500GB HDD split up as follows:
/dev/sdc1 � 80gb NTFS partition with Win7 installed /dev/sdc1 � Remaining drive space NTFS but nothing on it yet
Grub2 refuses to detect that Windows is installed on the 3rd HDD. I've googled and spent hours trying all sorts of things to get it to detect it and add it to my boot menu.
If I disconnect all drives except the Windows drive it boots up straight into Win7, so it's healthy and happy. (as healthy and happy as Windows can be, I need it for work purposes only!)
Does anyone have any tips on what would be the best method to force grub to realise that Windows is sitting there?
As far as I understand, the Win7 partition should be (hd2,1) � does that sound right to you?
I haven't tried booting off an Ubuntu CD and re-installing grub, since I can get into Linux and all the guides seem to be about how to restore grub after a Windows install eats it...
I'm running Debian Squeeze 32-bit with KDE 4. I've got a BenQ T2200HD monitor, and no matter how i try to configure it, fonts will always look crappy. after looking around a bit, I found some patch that is called David Turner's LCD ClearType-like patch. I found the packages- [URL]
I have Lenny in a multi-boot system on a HP Pavilion DV-1000 laptop, and yesterday when I logged in, noticed the red (-) icon on the right of the top panel. Mouse over it gave the message: "An error occurred, please run Package Manager from the right-click menu to see what is ". On doing so, Synaptic came up with "You have 3 broken packages on your system! Use the "Broken" filter to locate them". Selecting "Broken dependencies" resulted in the "base-files", base-passwd", and "dpkg" being listed. All three had "Installed Version" the same as "Latest Version", but marked in red in the check boxes.
Did "Edit"->"Fix Broken Packages" which marked the packages green. Clicking "Apply" gave a summary list: coreutils, gawk, gcc-4.3-base, libacl1, libattr1, libc6, libgcc1, libselinux1, libstdc++6, and izma as the packages that needed to be installed. Clicked "Apply" and got: "E: Internal Error, Could not perform immediate configuration (2) on libc6" A Google search indicated several people had run into this problem, but I could not find one consistent solution that seemed to address the problem completely.
I have created a system using four 2Tb hdd. Three are members of a soft-raid mirrored (RAID1) with a hot spare and the fourth hdd is a lvm hard drive separate from the RAID setup. All hdd are gpt partitioned.
The RAID is setup as /dev/md0 for mirrored /boot partations (non-lvm) and the /dev/md1 is lvm with various logical volumes within for swap space, root, home, etc.
When grub installs, it says it installed to /dev/sda but it will not reboot and complains that "No boot loader . . ."
I have used the supergrubdisk image to get the machine started and it finds the kernel but "grub-install /dev/sda" reports success and yet, computer will not start with "No boot loader . . ." (Currently, because it is running, I cannot restart to get the complete complaint phrase as md1 is syncing. Thought I'd let it finish the sync operation while I search for answers.)
I have installed and re-installed several times trying various settings. My question has become, when setting up gpt and reserving the first gigabyte for grub, users cannot set the boot flag for the partition. As I have tried gparted and well as the normal Debian partitioner, both will NOT let you set the "boot flag" to that partition. So, as a novice (to Debian) I am assuming that "boot flag" does not matter.
Other readings indicate that yes, you do not need a "boot flag" partition. "Boot flag" is only for a Windows partition. This is a Debian only server, no windows OS.
without thinking, reinstalled my windows installation after already having the dual-boot set up and it wrote over the GRUB with Windows MBR. I let my girlfriend's friend borrow the disc before this and decided to just wait it out. Then, when getting the disc back, I carelessly forgot it at their house and have never been able to retrieve it, nor do I think that I ever will.
At this point my only live discs either only have GRUB1 or are corrupted. My only tools now are a netbook with a wubi installation of Xubuntu(no CD drive) and a 1GB flash drive, it seems. Any suggestions on how to access my ubuntu installation?
i initilally installed ubuntu 9.10 then installed windows 7 ,then i recovered grub2 using livecd as told in the post [URL] i did "sudo update-grub" and got windows 7 menu entry but when i select that entry windows 7 does not load but the grub2 is reloaded again. i cant boot to windows 7.
Windows 7 have 100 mb partition "System Reserved" the grub2 points to that partition but still windows 7 not loaded.
sudo fdisk -l Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x3c3a81f5
I went through so many post but I haven't found the proper answer yet hope you have an Idea1. Grub2 saves only Linux OS as last selected no Windows OS2.It is possible to boot into a cdrom (drive)?
I've installed a Squeeze-based distro - Crunchbang - with an encrypted root partition (no LVM), and it won't boot.
Here's what I get: Loading initial ramdisk. Loading, Gave up waiting for root device ALERT! /dev/mapper/hda5_crypt does not exist. Dropping to a shell!
Here's my partition table: hda1 - Windows (Truecrypted) hda2 - GRUB2 hda5 - / hda6 - unused swap
[Code]...
What should I look for? Where do I go from the initramfs shell? Do I chroot? What then? This might be a Crunchbang issue (although others blame LVM which I didn't use, and it's the original Debian installer after all), but there's gotta be a reason it doesn't boot
The way I usually boot Linux distros, and this has worked for every distro I have tried up to Kubuntu 10.10, was to install Grub2 on an extended partition, run "dd if=/dev/sda5 of=linux.bin bs=512 count=1", and then adding that bin file to my Windows boot.ini. What usually happens after is that I get the Grub2 menu after selecting it from the Windows Bootloader.
The problem is, with the latest Squeeze AMD64, all I get when I do this is a static cursor and the computer is frozen and I have to hit the reset button.I mounted the Linux partition with Ext2IFS (mkfs.ext3 -I128 /dev/sda5 to get 128KB inodes), and I can see that the Squeeze installer did indeed install Grub2, because I can see the files in their respective directories.
Whenever I reboot, I get GRUB and the _ pinking, and that's it. With rescue cd I can have chroot shell, to troubleshoot I did the upgrade-from-grub-legacy and installed it to both /dev/sda and /dev/sdb In recovery I redid the upgrade-grub and grub-install commands but still have the same "GRUB and _ blinking".
Because the text "GRUB" and then nothing I didn't enouncter while googling, I need to ask here for further troubleshooting.
I just got a new hard drive and figured I might as well do an installation of Squeeze (and was previously using Lenny). That went fine, and then I decided that I should copy over my old Lenny installation to the new disk -- mostly to have a working backup without bothering to do a new installation on a partition of the new drive. My partition scheme was a smaller /boot partition and then a much larger / partition with everything else standard (and a much larger /data partition rather than storing everything under /home). So I copied /boot over to a new partition on the new disk, and the same with /. That was done from the Squeeze installation, so the Lenny install wasn't active at the time. I modified all the appropriate entries in /etc/fstab to use UUIDs rather than partition numbers and ran an update-grub.
It detected everything on the old and new disks without a problem. When I went to try and boot up the transferred Lenny installation, it hung on trying to activate the root file system (I've forgotten the exact messaging). Not entirely unexpected, mind you. I went and took a look at the grub.cfg file. It does list that the transferred Lenny is on partition sda8 (correct), it has the correct uuid for the boot partition... but it seems to be setting the root incorrectly. Specifically, the root is still set for the old disk (though in its new position of hd1 instead of hd0), and the "linux" line sets a root for the old device. Or more specifically, this is the menu entry I get, with a few // comments.
menuentry "Debian GNU/Linux, kernel 2.6.26-2-amd64 (on /dev/sda8)" { insmod part_msdos insmod ext2 set root='(hd1,msdos2)' // <------ This position is the *current* location of my old Lenny disk/partition search --no-floppy --fs-uuid --set [the correct /boot UUID] linux /vmlinuz-2.6.26-2-amd64 root=/dev/sda5 ro vga=795 // <----- that root=/dev/sda5 line is what it was on the old device. initrd /initrd.img-2.6.26-2-amd64 }
The odd thing there is that it sets the root according to the *current* position of the old install disk (maybe some trickery with detecting the correct UUID before setting the root), but the "linux" line refers to the *old* partition. The two lines will never match up no matter what. Now if I edit grub.cfg manually, I can make it boot (and run) normally, as I've verified. For example, I made a couple manual changes to do this:
menuentry "Debian GNU/Linux, kernel 2.6.26-2-amd64 (on /dev/sda8)" { insmod part_msdos insmod ext2 set root='(hd0,msdos3)' // <----------- First hard drive, partition sda3 is where I put /boot search --no-floppy --fs-uuid --set [the correct /boot UUID] linux /vmlinuz-2.6.26-2-amd64 root=UUID=[the correct / UUID] ro vga=795 // <--- Changed it to the UUID here; could be /dev/sda8 instead initrd /initrd.img-2.6.26-2-amd64 }
And that works perfectly, the installation works just fine. Of course, the problem is that those changes will/would be lost every time I run an update-grub. So my question, in a nutshell, is how can I configure things so that update-grub sets things properly to the new devices? Or in other words, where in the copied installation are the variables I need to change? I did note one thing odd -- the existence of a vga=795 line. For the new Squeeze installation, I'm using gfxpayload and there's no vga=anything line anywhere. My old installation, of course, had its own grub installation where I did use vga=795 to set the console resolution properly.
So my first guess was that update-grub (for Grub2) was pulling config information out of the Lenny /boot/grub folder (grub legacy). Unfortunately I tried several changes there and it made no difference. Then I deleted the entire /boot/grub folder entirely from the copied Lenny installation and ran update-grub again (the Squeeze grub version). It changed absolutely nothing. That's very confusing for me, since I have no clue where it could be getting vga=795 from, *except* the now-deleted Lenny /boot/grub folder. Where in the copied Lenny installation, I can change something to make it so that update-grub picks up the correct information?
I am a relative newbie to Fedora 12, altho did start with OpenSuse. I installed XP first with the games that couldn't run via wine. Then I installed Fedora but I must've done something wrong as although Fedora runs fine with a few personal tweaks with everything I want I can't access XP as it is no longer an option in the boot up. What do you suggest I do. I have a system rescue cd ready but don't know how to access the boot or change it.
Ahm my question is, how can i adjust or redo the size of my hard disk in ubuntu? i mean i have the windowsXP OS then decided to install ubuntu 10.04 so i install it inside windows... i forgot to adjust the size or something?? because every time i boot ubuntu my free storage was 5 gb... but the real size of my HDD is 112gb in HOST directory but when im looking in home directory/home folder its shows that 5gb remaining, so what am i going to do? And what is my mistake?
Was running 10.10 64-bit on Thinkpad X201. I mistakenly clicked on upgrade this morning (really meant to just do a plain old update)... I tried to stop the process, but nothing that I did could get me out of the upgrade loop... so I eventually was forced to go ahead. Machine boots into 11.04; however, keyboard and mouse doesn't work. I have an external keyboard/mouse combo and that will intermittently work, but questionable. I was able to turnoff Unity; however, Classic doesn't seem to work with either external keyboard or laptop builtin.
My root and home are on separate partitions. I have a very fresh copy of home backed up on a separate drive. I don't have a recent backup of root. If I could get Natty working with Classic (including minimize/maximize) I'd be OK...I'd be also OK with going back to 10.10 if I could do it without too much pain. Meanwhile, I'm using another machine with Windows 7 so that I can at least do some work and come back to resurrecting my machine after I've had a bit of a timeout..
I have a laptop with 2 HDDs, 1x SSD (/dev/sda, Windows 10 Pro x64) and 1x HDD (/dev/sdb, 3 primary partitions: boot, root, swap; 1 logical partition: home).I used the Debian Stretch Alpha D1 Netinstall ISO x64 by transfering it to a USB stick with DiskImage Writer.The installation went perfectly fine. I chose GRUB to be installed in the MBR of /dev/sdb, as I want all my Linux Stuff on that second disk. The plan is to boot the second disk manually through the BIOS whenever I want to work with Debian. My Windows disk is kept unaware of anything "linuxy".
After the install was complete and I booted my /dev/sdb through the BIOS, a blinking cursor on a black screen was the result. And I don't mean a GRUB Rescue prompt.IMHO, Grub appears to not have been installed, although I chose it to be installed in the MBR of /dev/sdb at the end of the installation.
I've been reading a little, searching for a bug in the installer, but I found only a vague mentioning of such an issue: Grub missing if Debian installed on a multi-hdd system through USB stick. The solution was to get Super Grub2 Disk, and use it to boot my Debian. It worked as expected and the system booted.
I have a dual boot system. I need dual boot as my dictation software is only available for Windows. In the future I am going to try a virtual machine, but dictation and audio did not work properly the last time I tried in VM. But unfortunately for now I have a dual boot machine with Vista and Debian 6. Unfortunately, I am going to have to reinstall Vista. Or to be more accurate I'm going to install the 64-bit version instead of the 32 bit that came with the computer. I have the 64-bit version that I no longer use from one of my other computers.
Anyway, I have to install Windows which will overwrite my grub2. Is there anyway I can make a backup or reinstall grub2 after I install Windows. I really don't want to reinstall Debian 6 squeeze. Can they make some sort of a backup of gurb2 before I do this. I checked out the Internet and I found something called Super Grub2. It apparently will allow me to boot back into Debain 6 so that I can install grub2 again. Assuming, Super Grub2 even works then how do I reinstall grub2 once a boot into Debian 6? Has anybody tried Super grub2, does it work? It's kind of hard to test it, with a working version of grub2.
How can I restore or reinstall GRUB2 from squeeze installation? I tried various suggestions from various online articles (most of them for ubuntu), but I couldn't find a solution. Is there any solution, specifically for Debian? GRUB reinstallation from install cd, didn't worked as well. Since I couldn't boot at all, I restored GRUB1 and I'm posting from Lenny, but I can't access Squeeze this way (probably because I have squeeze's partition, ext4 formatted).
I have a dual boot PC, tried to upgrade to Lucid Lynx and the upgrade failed. Can't boot into it at all. Windows XP still works fine. I have the live CD for a re-install now. I read this post but don't understand the difference between the instructions for the partitions. Have posted my screen shots below.First screen shows that I have 10.04 and offers me the option to partition further.Screenshot 1 I choose manual partition and then it gives me the right sized partitions. . Then in screenshot 2 I edit and choose the mount point as /, is that right? (screen shot 3). Do I then change that option again to choose /home? because otherwise it takes me straight to screenshot 4, the user name set up.There's No Custom User Title Here
I have /dev/sda with Squeeze and Win 7 on it, and /dev/sdb with Squeeze. I've managed to get Grub 2 to boot from /dev/sdb1, but only by disabling /dev/sda from being a boot option in the BIOS. When it is available to boot, and lower priority than /dev/sdb, grub does not recognize the UUIds of the disks. So, I've disabled it for now and can boot from /dev/sdb no problems. Trouble is I cannot get Win7 to boot. Grub prints:
error: no such device: f0903a3a903a081c error: invalid signature
When I boot into Squeeze and run 'blkid' I can see that:
menuentry "Windows 7 (loader) (on /dev/sda1)" { insmod ntfs set root='(hd0,1)' search --no-floppy --fs-uuid --set f0903a3a903a081c chainloader +1 }
I don't understand how Grub 2 cannot recognize the UUIds. Can Grub 2 to be made to work with volume labels or just plain old /dev/... descriptions? Maybe I should give grub-legacy a go.
This is my specific solution to my specific problem. After updating to Squeeze from my prior Lenny distro (amd64 with whole disk encrytion using LVM2, dm-crypt, LUKS) everything went well - at first. I was duped like so many, thinking that all was well and I could remove the legacy-grub (aka: Grub1) and just use grub-pc (aka: Grub2). As soon as I removed the legacy-grub and rebooted my laptop, I was confronted with:
GRUB Loading stage1.5 GRUB loading, please wait..Error 15 At this point I wasn't sure if it was a Grub problem or a deeper encryption problem - especially after reading that some people had missing packages in Squeeze (lvm2, dm-setup, initramfs-tools, etc.)
Okay, the solution for me.
1. download and burn to disk: debian-live-6.0.0-amd64-rescue.iso[URL]..
2. scroll to and press enter/return on: text rescue
3. choose a root directory - for example: /dev/blah/root (I wrote down the list of possible /dev/.... for reference - this helped me remember where and what I had partitioned in Lenny)
4. choose: Execute a shell in /dev/blah/root
5. once in the shell, I discovered I needed to mount a few of those partitions that I had written down in order to get access to grub-probe, update-grub, grub-install, etc. You may not have to if your partitions are minimal. I you need to use other partitions, type (for example):
I have a Dell PowerEdge SC1425 with two SCSI-disks, that I have tried installing Debian Squeeze on. This machine has previously been running Lenny (with grub 1), and the upgrade was done by booting a live-cd, mounting the root partition and moving everything in / to /oldroot/, then booting the netinstall (from USB), selecting expert install and setting up everything (not formatting the partition).
Both disks have identical partition tables: /dev/sda1 7 56196 de Dell Utility /dev/sda2 8 250 1951897+ fd Linux raid autodetect /dev/sda3 * 251 9726 76115970 fd Linux raid autodetect /dev/sda1 and /dev/sdb1 contain a Dell Utility, that I have left in place. /dev/sda2 and /dev/sdb2 are members of a Raid-1 for swap. /dev/sda3 and /dev/sdb3 are members of a Raid-1 for / formatted with reiserfs.
After installation, grub loads, but fails with the following message: GRUB loading. Welcome to GRUB! error: no such disk. Entering rescue mode... grub rescue>
I can do the following to get grub to boot: set root=(hd0,3) set prefix=(hd0,3)/boot/grub insmod normal normal This will bring me to the grub menu, and the system boots.
It appears that grub has only found md0, which I believe is the swap partition, because ls (md0)/ returns error: unknown filesystem. I have installed grub to both sda, sdb and md1, and tried dpkg-reconfigure grub-pc and dpkg-reconfigure mdadm, as well as update-grub.
I manually added (md1) /dev/md1 to /boot/grub/device.map, but still no result.
I have run the boot_info_script.sh, but unfortunately I cannot attach the RESULTS.txt, because the forum aparently does not allow the txt-extension. Instead I have placed it here: [URL]. I am tempted to go back to grub-legacy, but it seems I am quite close to getting the system working with grub2.
I'm new to fedora, but had installed it once before on machines for my class. I am now trying to install fedora on my PC at home, but every time I run the disk and chose install from the main screen all I get is a bunch of text and then it says "Fixing recursive fault but reboot is needed"
I set my drives up with MY boot loader, and I boot several OSes.I installed Ubuntu and told it to place grub on the / drive, which is where I always put it with any other install and it works fine.I find now that despite telling the install where to put it, you guys have taken it upon yourselves to alter the MBR of the volume ANYWAY!
SO, what I need to do is re-install grub, but I see that you also have no repair facility on this disc either. All I want to do is use MY boot loader. Currently, when I point at the / volume it just hangs with a non-blinking cursor in the upper left.No other Linux installs I have performed over the years do this. I want the drive to boot by merely pointing my bootloader at that volume.It always has in the past, so what did you guys change? I want NO action on my MBR, but I DO want a working grub on the actual root volume, which is NOT the first volume on the drive.
I switched over from Ubuntu because I realized Ubuntu sucks now (lol), but anyways... Now I'm trying to get Grub2 to boot up properly, but this "xputs" error pops up and drops me to the recovery prompt. I tried the grub-install dev/sda and all it did was recognize my Windows 7 OS (as Vista) and added it to the bootloader list and didn't fix the "xputs" issue.
I heard that doing a chroot is the most effective solution. Forgive me, but I don't know what "chroot" means or how effective it is. I can specify more information about where the OS is if needed. I have the boot flag set to the Debian OS at the hd(0,5) or sda5 I think, and Windows is at sda1 (I think). I just want to make sure I can fix this without damaging Windows, and I'll try to get more information.
Right now, I can only get into Windows or Debian with UBCD and Grub2 Super Disk and I know that sometimes Parted Magic could orderly mount the disks differently, so I don't know if it was sdaX or sdbX, but probably sdaX. I'll check again.
I've read the various Grub2 posts and even the guide, but unfortunately for me I can't seem to come up with an answer to my problem. I installed Ubuntu 9.10 on a new hard drive on a friends laptop, but I have problems with the system hanging on the Grub2 bootup.I'll post the screen
recordfail=1 if [ -n ${have_grubenv} ]; then save-env recordfail; fi set quiet=1 insmod ext2 set root=(hd0,1) search --no floppy --fs-uuid --set ac1b1d46-bac1-4140--953e-70a8a61be8b0 linux /boot/vmlinuz-2.6.31-14-generic root=UUI=ac1b1d46-bac1-4140-953e-70a8a61be8b0 ro quiet splash initrd /boot/initrd.img-2.6.31-14-generic
If I hold down the left shift and then press E to edit and remove the search --no floppy line entirely then press ctrl-x the system boots just fine. I then opened up a terminal and did sudo update-grub to try that but it didn't fix it. Is this a problem in my bios looking for a floppy, I tried with the boot from floppy enabled and disabled (but always as the 3rd boot option) the floppy is not installed. Is there anyway to edit the file and save it so it will boot up? I was trying to research that and could not come up with it.
The screen will show a blinking cursor for a few seconds. The keyboard works and a signal is found for the speakers. Then the 'Ubuntu' loading screen will show but at this point the screen would freeze and the keyboard will cease to function. At this point I have to reboot from the on/off switch. It can take several attempts before the desktop will load, or if I'm lucky, it'll load up first time. I've had this problem since 9.10. I'm not quite sure why it's taken me this long to attempt to sort it out.
