ice while flashing the BIOS.
After "boot-repair" totally cracked up everything (no more GRUB,
whatever I did), the machine now runs 14.10.
Thanks anyway
Wolle
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
PS: If further information is required or useful, don't hesitate to
explicitly tell me what information exactly I should post!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1091464
Title:
Unable to
I can confim this, too.
Machine is a Toshiba Satellite C850D - 119.
Windows 8 has been pre-installed. The regular user isn't satisfied, so a Linux
install was desired. Nevertheless, Windows 8 will still be required. The
regular user is of very poor "computer know-how", so dual-booting via the GR
As I just reviewed this, I wanted to add, that the line
"/usr/sbin/grub-setup: info: »/boot/grub/device.map« kann nicht
geöffnet werden."
in attachment grub-install.log would be
"/usr/sbin/grub-setup: info: »/boot/grub/device.map« cannot be opened"
in English. Usually the file really doesn't
Interesting: unknown boot code (?) on sda2 ??
** Attachment added: "RESULTS.txt"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/574883/+attachment/1811806/+files/RESULTS.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
le of /dev/sda...
Searching sda1 for information...
Searching sda2 for information...
Searching sda5 for information...
Searching sda6 for information...
Searching sda7 for information...
Searching sda8 for information...
Searching sda9 for information...
Finished. The results are in the file RESULTS
Okay, I'll give it a try later this day.
In another discussion on this topic in a forum, I was advised to check
the exit code. The grub-install command as stated above produces exit
code 0.
To speed things up: Would you like to have any other information than
the output of grub-install, the booti
I've got exactly the same problem as stated in posting no. 5.
I can use the mouse with buttons 1 and 2 (left, right), but the mouse
wheel doesn't work at all...
$ uname -a
Linux name-here 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010
x86_64 GNU/Linux
user@name-here ~ $ tail /var/l
In a next attempt, I tried to install SliTaz3.0 into sda1, which brought
its bootloader grub-legacy (installed to MBR of sda). I intended to use
Slitaz for maintainig the main bootloader which would be grub-legacy
then.
Installing grub2 into the PBR of sda6 failed again, exactly the same
results a
The above described obviously does only write parts of GRUB to the
designated PBR.
Performing
start code
insmod chain
chainloader (hd0,6)+1
end code
in order to chainload the partition prepared in the above mentioned way
produces an error message
"Booting a command list" aft
I continued to search for a solution and found:
http://www.gnu.org/software/grub/manual/grub.html#Installing-GRUB-using-grub_002dinstall
The I tried, what the manual proposes for some USB devices (last paragraph of
the refered section):
start code
caelinux@caelinux:~$ sudo -i
root@caeli
I can reproduce exactly the same behaviour.
I installed the bootloader of my choice to MBR and intended to chainload
several other OS from that.
Two of those OS should be Mint10-64bit (based on Ubuntu 10.10 64bit) and
CAELinux (based on Ubuntu 10.04 bit). Installing GRUB2 to their
respective part
12 matches
Mail list logo
