Recovering Arch from Grub prompt (GRUB4DOS)
Long story short, I needed to install Windows 8 with my Arch already installed, wiping out the bootloader (I don't get what actually happens so I might be wrong here on the technical side).
I've tried different methods, from using programs like EasyBCD to command-line work (detailed here https://bbs.archlinux.org/viewtopic.php … #p1344396), and I've reached the conclusion that perhaps I need to work on the GRUB prompt itself. As described in that link, I might have been on to something with
root (hd0, 2)
setup (hd0)
except that the command setup cannot be found.
Also, I'd like to point out that sometimes my computer boots into a black-and-white list (kinda like GRUB), and sometimes it uses the metro-style "Choose an Operating System", the one with the light blue background.
Any help please? I'd just like to get my Arch setup back.
Last edited by jddantes (2013-11-06 11:56:37)
I ran it again, and it showed other devices:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sda.
=> Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Windows/System32/winload.exe
sda3: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: vfat
Boot sector type: SYSLINUX 4.04 2011-04-18
Boot sector info: Syslinux looks at sector 1053216 of /dev/sdb1 for its
second stage. SYSLINUX is installed in the directory.
The integrity check of the ADV area failed. No errors
found in the Boot Parameter Block.
Operating System:
Boot files: /syslinux/syslinux.cfg /ldlinux.sys
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 718,847 716,800 7 NTFS / exFAT / HPFS
/dev/sda2 718,848 155,650,047 154,931,200 7 NTFS / exFAT / HPFS
/dev/sda3 155,650,048 228,614,143 72,964,096 83 Linux
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 7731 MB, 7731314688 bytes
237 heads, 1 sectors/track, 63714 cylinders, total 15100224 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 * 2,048 15,099,903 15,097,856 b W95 FAT32
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda1 2A7699B97699866B ntfs System Reserved
/dev/sda2 7044B3C644B38CFA ntfs
/dev/sda3 31df11a9-14a7-44f7-80c9-763ee40106c5 ext4 LFS Partition
/dev/sdb1 8E5A-F18E vfat MYLINUXLIVE
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/loop0 /rofs squashfs (ro,noatime)
/dev/sdb1 /cdrom vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
=================== sda3: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
= boot/grub/stage2 1
========================= sdb1/syslinux/syslinux.cfg: ==========================
# D-I config version 2.0
include menu.cfg
default vesamenu.c32
prompt 0
timeout 300
ui gfxboot bootlogo
================= sdb1: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
?? = ?? ldlinux.sys 1
?? = ?? syslinux/chain.c32 1
?? = ?? syslinux/gfxboot.c32 1
?? = ?? syslinux/syslinux.cfg 1
?? = ?? syslinux/vesamenu.c32 1
============== sdb1: Version of COM32(R) files used by Syslinux: ===============
syslinux/chain.c32 : COM32R module (v4.xx)
syslinux/gfxboot.c32 : COM32R module (v4.xx)
syslinux/vesamenu.c32 : COM32R module (v4.xx)
=============================== StdErr Messages: ===============================
awk: cmd. line:36: Math support is not compiled in
./bootinfoscript: line 1646: [: 2.73495e+09: integer expression expected
No volume groups found
Similar Messages
-
Would I be able to load Arch from wubi based grub [solved]
Hello,
This one of my experience where I am trying to see if I can load Arch (installed on partition not like lookback disk) from grub that is installed on wubi installed ubuntu file.
So far, I could install Arch on disk without installing grub and added entries as follows. But somewhere I am missing something, it is not able to boot when I select option of Arch in the boot.
Could you help me.
Few additional details required to debug this issue:
1. grub.cfg file of ubuntu grub
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-fc296be2-8c59-4f21-a3f8-47c38cd0d537' {
gfxmode $linux_gfx_mode
insmod gzio
insmod ntfs
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 01CD7BB998DB0870
else
search --no-floppy --fs-uuid --set=root 01CD7BB998DB0870
fi
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-3.5.0-19-generic root=UUID=01CD7BB998DB0870 loop=/ubuntu/disks/root.disk ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.5.0-19-generic
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-fc296be2-8c59-4f21-a3f8-47c38cd0d537' {
menuentry 'Ubuntu, with Linux 3.5.0-19-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-19-generic-advanced-fc296be2-8c59-4f21-a3f8-47c38cd0d537' {
gfxmode $linux_gfx_mode
insmod gzio
insmod ntfs
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 01CD7BB998DB0870
else
search --no-floppy --fs-uuid --set=root 01CD7BB998DB0870
fi
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
echo 'Loading Linux 3.5.0-19-generic ...'
linux /boot/vmlinuz-3.5.0-19-generic root=UUID=01CD7BB998DB0870 loop=/ubuntu/disks/root.disk ro quiet splash $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.5.0-19-generic
menuentry 'Ubuntu, with Linux 3.5.0-19-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-19-generic-recovery-fc296be2-8c59-4f21-a3f8-47c38cd0d537' {
insmod gzio
insmod ntfs
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 01CD7BB998DB0870
else
search --no-floppy --fs-uuid --set=root 01CD7BB998DB0870
fi
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
echo 'Loading Linux 3.5.0-19-generic ...'
linux /boot/vmlinuz-3.5.0-19-generic root=UUID=01CD7BB998DB0870 loop=/ubuntu/disks/root.disk ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.5.0-19-generic
### END /etc/grub.d/10_lupin ###
menuentry 'Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-0f490b6c-e92d-42f0-88e1-0bd3c0d27641'{
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8 0f490b6c-e92d-42f0-88e1-0bd3c0d27641
else
search --no-floppy --fs-uuid --set=root 0f490b6c-e92d-42f0-88e1-0bd3c0d27641
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=0f490b6c-e92d-42f0-88e1-0bd3c0d27641 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-0f490b6c-e92d-42f0-88e1-0bd3c0d27641' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8 0f490b6c-e92d-42f0-88e1-0bd3c0d27641
else
search --no-floppy --fs-uuid --set=root 0f490b6c-e92d-42f0-88e1-0bd3c0d27641
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=0f490b6c-e92d-42f0-88e1-0bd3c0d27641 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
2. lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 39.2M 0 part
├─sda2 8:2 0 19.8G 0 part
├─sda3 8:3 0 205.1G 0 part
├─sda4 8:4 0 1K 0 part
├─sda5 8:5 0 333.7G 0 part /host
├─sda6 8:6 0 233.4G 0 part
├─sda7 8:7 0 100.4G 0 part
├─sda8 8:8 0 100M 0 part
├─sda9 8:9 0 14.7G 0 part
├─sda10 8:10 0 21.4G 0 part
└─sda11 8:11 0 3G 0 part
sr0 11:0 1 1024M 0 rom
loop0 7:0 0 29G 0 loop /
3. blkid
/dev/loop0: UUID="fc296be2-8c59-4f21-a3f8-47c38cd0d537" TYPE="ext4"
/dev/sda1: SEC_TYPE="msdos" LABEL="DellUtility" UUID="5450-4444" TYPE="vfat"
/dev/sda2: LABEL="RECOVERY" UUID="78C4FAC1C4FA80A4" TYPE="ntfs"
/dev/sda3: LABEL="OS" UUID="DACEFCF1CEFCC6B3" TYPE="ntfs"
/dev/sda5: UUID="01CD7BB998DB0870" TYPE="ntfs"
/dev/sda6: UUID="01CD7BB99CA3F750" TYPE="ntfs"
/dev/sda7: LABEL="Windows 8" UUID="01CDBFB52F925F40" TYPE="ntfs"
/dev/sda8: UUID="cdbb5770-d29c-401d-850d-ee30a048ca5e" TYPE="ext2"
/dev/sda9: UUID="0f490b6c-e92d-42f0-88e1-0bd3c0d27641" TYPE="ext2"
/dev/sda10: UUID="2e7682e5-8917-4edc-9bf9-044fea2ad738" TYPE="ext2"
/dev/sda11: UUID="6081da70-d622-42b9-b489-309f922b284e" TYPE="swap
Any help is appreciated
Last edited by ameyjah (2012-12-19 14:20:25)If sda8 is a separate boot partition for Arch, you don't need /boot for the linux and initrd lines in the grub entry. E.g.
linux /vmlinuz-linux root=UUID=0f490b6c-e92d-42f0-88e1-0bd3c0d27641 ro quiet
initrd /initramfs-linux-fallback.img
Removing "quiet" will result in more informative failures. (There are debug options which will get even more info.) -
How to Restore Arch's grub after Ubuntu install to 2nd disk
I installed Ubuntu to sdb after installing Arch to sda. Ubuntu was installed with LVM, though Arch does not use LVM.
I want to wipe out ubuntu now, but it seems to be in control of my boot process, and as a newb, I'm not quite sure how that process transpires. I have read the Grub article on Arch's Wiki site, but that doensn't help me.
After booting into Arch and running:
# grub-mkconfig -o /boot/grub/grub.cfg
and then rebooting, I still have the Ubuntu Grub menu on the next boot. My Arch /etc/default/grub is the same one that I used before installing Ubuntu - I'm not concerned about adding Ubuntu to the menu, so that's not an issue.
What do I need to do to get Arch back in control of the boot process?
Thanks in advance!Kilz wrote:Here is an option in case you cant figure it out. Rename the /boot directory in the ubuntu install and copy the /boot directory from Arch in its place. Reboot, if everything works fine delete everything in the Ubuntu partition but /boot. Rename the /boot directory in the Arch install then shrink the ubuntu partition and mount it in the arch install as /boot. in the end you will just have a separate boot partition that will take up little space.
Thanks again. I finally got it working, but via a different, somewhat convoluted route.
I screwed things up and ended up with only a grub prompt at boot. Following instructions found online, I was able to boot my arch disk (sda), then ran grub-install and grub-mkconfig. The install ran without errors (as before) but grub-mkconfig reported errors. I had been disregarding these errors, because I thought they were related to the custom font and background in my /etc/default/grub file, and another source explained that I could ignore errors when setting fonts and background there (not sure if that source was reliable). But one of the errors on grub-mkinstall reported it couldn't find device.map. There was no device.map in /boot/grub.
Also of note, I had renamed the old /boot/grub/grub.cfg and left the /boot/grub directory without a proper grub.cfg file - probably why I got a grub menu at boot!
In the end, I created a device.map in /boot/grub/ and re-ran grub-mkconfig, but still got an error. So I commented out the font and background lines in /etc/default/grub and also renamed my old backup /boot/grub/grub.cfg-backup to the proper "grub.cfg", then re-ran grub-mkconfig. This time there were not errors reported from grub-mkconfig and with a quick glance at the contents, I was able to figure out that the menu entries looked good.
I was able to reboot with the appropriate arch menu at this point! While I'm not sure which step "fixed" my problem, I wanted to at least record my steps here for future users - perhaps one of the options above will help someone else. Worth mentioning is that the ubuntu (sdb) drive was LVM, and I think that might have played into some of my difficulties, but I'm not sure about that.
The device.map that I created looked like this, where sda is my arch disk and sdb is the ubuntu installation (still not sure if it is needed, though):
(hd0) /dev/sda
(hd1) /dev/sdb
Last edited by stringchopper (2013-02-14 08:38:52) -
Dual boot , windows 7 keep restart after select from grub section
Hello everyone, i am new here.
I want to make a dual boot in my computer.
I am using a same hardisk to install both OS.
1st, I install arch linux , after install working well from grub.
2nd, I install windows 7, after install , it skip the grub section , directly load windows 7.
I boot my archlinux live cd.
Go to grub .
type root (hd0, and press tab to make sure my partition.
setup (hd0).
The grub section was recover and success to login arch linux.
but fail to login windows 7 , then i modify /boot/grub/menu.lst . modify the windows (hd0, 1).
My trouble probem is here, after i select the windows section , my com just like restart computer.
Even i try change to (hd0, 2 or 3 ) also same problem, windows 7 restart computer.I have try to install dual boot for more than 5 time, first i install windows then only come to arch linux, but always fail to boot up windows.
Thank for helping me ^^
This is my fdisk -l
I have 2 hardisk, but i install both Os in the same hardisk.
Device Boot Start End Block ID System
/dev/sdb1 1 24 192742+ 83 Linux
/dev/sdb2 25 37 102400 7 HPFS/NTFS
Partition 2 does not end on cylinder boundry
/dev/sdb3 37 8243 65939456 7 HPFS/NTFS
/dev/sdb4 8247 14593 50982277+ 5 Extended
/dev/sdb5 8247 8368 979933+ 83 Linux
/dev/sdb6 8364 10858 20000893+ 83 Linux
/dev/sdb7 10859 14593 20001356 82 Linux Swap / Solaris
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/sd5 ro
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/sd5 ro
initrd /kernel26_fallback.img
# (2) windows
title windows 7
rootnoverify (hd0, 1)
makeactive
chainloader +1 -
[SOLVED] After latest upgrad. Boots to grub prompt
Hi,
I just upgraded my Thinkpad T61 following
https://www.archlinux.org/news/binaries … ervention/
After completeing the upgrade I got an error "Unable to start shell:/bin/bash" in Terminator. I commented out /dev/pts in /etc/fstab following
https://bbs.archlinux.org/viewtopic.php?id=169076
the problem did not go away. I decided to reboot After which the computer boots only to a grub prompt.
I'm posting this after booting with a linuxmint USB stick so Ihave access to the / partition on the laptop.
I've been on systemd for a while now. However I now suspect that I was not fully migrated to systemd. I did do a pacman -R initscripts during the latest upgrade.
Does anybody know how I can recover from this?
need all the help I can get on this one!
Last edited by emk (2013-09-02 03:22:05)Trilby, you are correct the empty /boot was because I neglected to mount the /boot partition. My mistake.
2. I did have errors as per https://www.archlinux.org/news/binaries … ervention/ i.e the upgrade failed because /bin /sbin were still in the filesystem. I followed the steps in the link and found some files that were holding things up.
I removed the following files
pacman -R gen-init-cpio wlan-ng26-utils consolekit dcron hpoj initscripts tcp_wrappers
I boot via systemd though I suspect now I was not fully migrated.
3. Output of ls on boot partition:
mint e3beb7a9-4c88-4688-8a2d-a00946489a3f # ls -l
total 21258
drwxr-xr-x 2 root root 1024 Sep 2 00:22 grub
-rw-r--r-- 1 root root 14869898 Sep 2 00:25 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 3010076 Sep 2 00:25 initramfs-linux.img
lrwxrwxrwx 1 root root 28 Aug 21 2011 kernel26-fallback.img -> initramfs-linux-fallback.img
lrwxrwxrwx 1 root root 19 Aug 21 2011 kernel26.img -> initramfs-linux.img
drwx------ 2 root root 12288 May 11 2010 lost+found
drwxr-xr-x 2 root root 1024 Sep 2 00:28 syslinux
lrwxrwxrwx 1 root root 13 Aug 21 2011 vmlinuz26 -> vmlinuz-linux
-rw-r--r-- 1 root root 3783360 Aug 30 09:33 vmlinuz-linux
mint e3beb7a9-4c88-4688-8a2d-a00946489a3f #
4. You are probably right. I have both grub 0.97 and grub 2 in the pacman pkg cache
5. I did follow the steps except that trying to close a terminal once the bash error croped up led to my being logged out before I could run the last two commands 'pacman -S bash and Pacman -Su'
Thanks Trilby. I feel like my Linux chops are evaporating the older I get :0 -
Booting into empty grub prompt and slow GDM
Hello,
I haven't performed update for long time and I did last day. I had issues related to /sbin exists etc which I have resolved by following the instructions posted in the Arch linux website. However after a successful update, I have the following issues.
(1) - When I log in back, it puts me into an empty grub prompt. I figured out that pacman changed menu.lst to menu.lst.pacsave. So from the grub prompt, I did
configfile /grub/menu.lst.pacsave
and I got the arch linux boot screen.
(2) - It started booting and loaded GDM with the login screen. Login and key strokes are very slow here. Even after login, I don't see GNOME shell. I don't see any errors while booting.
Any help to fix these issues would be good.
Cheers
NavaneethWhat exactly did you do when following the instructions? That is, following them is good, but it would be better if people could make sure there was no misunderstanding which might be causing issues.
You need to go back further through the news as you have evidently ignored various changes to Arch.
For example, legacy grub has not been in the official repos for some time. When you updated, grub2 (which is now called grub) replaced grub (legacy). Hence the pacsave. But you still have grub legacy installed as your boot loader. If you want to keep using it, install the AUR package which has been updated to work with the new filesystem package. Otherwise, configure and install grub (i.e. grub2) or install an alternative such as syslinux.
You are likely to have other pacnew and pacsave files. You need to look through pacman's output (/var/log/pacman.log) and follow the instructions there to ensure that your system is properly configured in light of the updates.
Arch is meant to be updated frequently. If that isn't an option, you would be better served by a different distro. -
Macbook Air Mid 2011 - Stuck in Grub Prompt
Hi Archers,
I am trying to install Arch on an Mid 2011 Macbook Air. So far it looks ok, I am following the Wiki and this guide. The bootloader stuff is confusing me a little. I do not want to replace the bootloader from OSx, so I do not use rEFInd, right? I want to use the "Press alt while booting"-method, so does the above guide.
First problem:
While generating the standalone "boot.efi" file the "-C" option is not recognized.
grub-mkstandalone -o boot.efi -d usr/lib/grub/x86_64-efi -O x86_64-efi -C xz boot/grub/grub.cfg
It complains that -C is not a valid parameter, so I just skipped it.
After deleting the boot partition in OSx and creating the directories and files and copying the boot.efi file I am able to boot from this partition. Problem #2: After booting the partition I am stuck in a Grub prompt. It recognizes HD0 and 1 and after fiddling around with
ls (hd0)
ls (hd1)
ls (hd0,4)
It always complains about an unrecognized partition type.
Any help appreciated. Will I get it working in this state?
Booting from USB and installing the base system worked like a charm, I have a feeling I nearly got it but the bootloader stuff is just plain confusing.
Thanks in advance.
Last edited by Urfaust (2014-01-29 18:55:29)Ok, I cannot find another guide which uses the OSx Bootloader. I installed rEFInd, reformated /boot with mkfs.ext2, chrooted to the base system and:
# pacman -S grub-efi-x86_64
# mkdir -p /boot/efi
# mount -t vfat /dev/sda1 /boot/efi
# modprobe dm-mod
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck --debug
# mkdir -p /boot/grub/locale
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
The boot partition is recognized in rEFind, if I choose to boot from it Grub is firing up, I can see 2 menu entries (normal and fallback) after choosing the first I get:
error: no such device: someUID
Loading Linux core repo kernel ...
error: no such partition
Loading initial ramdiks ...
unaligned pointer 0x22
Aborted. Press any key to exit
Why won't Grub find the partition?
Last edited by Urfaust (2014-01-30 16:14:39) -
[Solved] Booted into grub prompt
Hello,
I've followed the wiki to the last step but couldn't get booted into Arch:
https://wiki.archlinux.org/index.php/Beginners%27_guide
After I've generated the grub.cfg and rebooted.
I got a grub prompt.
I don't know what I am missing so please tell me what to do and I'll post the result.
I'm installing it on qemu. The image is archlinux-2014.11.01-dual.iso
fdisk result of the image:
Disk /shosts/arch.img: 17 GB, 17179869184 bytes
4 heads, 32 sectors/track, 262144 cylinders, total 33554432 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/shosts/arch.img1 34 2047 1008 83 Linux
/shosts/arch.img2 2048 411647 204736 83 Linux
/shosts/arch.img3 411648 31868927 15728576 83 Linux
/shosts/arch.img4 31868928 33554398 842688 82 Linux Swap / Solaris
Warning: Partition 4 does not end on cylinder boundary.
arch.imgX is actually /dev/vdaX
Regards.
Last edited by tgckpg (2014-11-24 07:10:31)After googling and such.
I tried to use the grub command to boot it manually but couldn't get it work.
I noticed some files are missing in /boot folder.
( Not sure, but from the look of it it seemed
there is no such file initramfs-linux.img and vmlinuz-linux for me to run initrd or linux command in grub )
So I boot back into the CD and ran "pacstrap -i base base_devel" & "grub-mkconfig -o /boot/grub/grub.cfg" again.
And the file is there!
And I booted into Arch!
cheers:) -
I was updating my menu.lst file and then thought I had to run grub-install so I ran the following command
sudo grub-install --root-directory=/boot hd0
No Errors.
But when I rebooted I was presented not with my menu.lst, but the GRUB prompt.
I manually ran the menu.lst commands into grub and then booted successfully.
But every time that I reboot I get the grub prompt.
I have a separate boot partition on /dev/sda1 (I only have one hardisk).Firstly, you don't have to run grub-install after editing menu.lst. -- I know that now . . .
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/hda (hd0)
# /dev/hdb2 (hd1,1)
# /dev/hda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro vga=773
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26-fallback.img
# (1) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1
/dev/sda3 on / type ext3 (rw)
none on /dev type ramfs (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
none on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext2 (rw)
/dev/sda4 on /home type ext3 (rw)
I do understand about the grub prompt. I am becoming better and better at it. -
Trying to boot arch from win7 with EasyBCD; "boot device not found"
EDIT: title was 'Dual boot with Win7, easybcd + syslinux, getting "Boot error"'. Narrowed down the issue to something unrelated to Arch, and felt this was more accurate. The Arch install is sound, it's getting win7/EasyBCD to load it that's the issue.
I got a new work computer and am trying to recreate my formerly successful setup, which I documented here some time ago. Unfortunately... I'm having issues. Just a note up front from scouring the internet for ideas: I cannot use syslinux (or any other bootloader) to chainload Win7 vs. the other way around! The computer drive is encrypted with McAfee Endpoint Encryption, and doing anything whatsoever with the MBR from outside of Windows will brick my computer. Just wanted to add that, as almost all issues involving dual boot inevitably bring about the suggestion to "just chainload windows from grub/syslinux/etc."
With that out of the way, here's the process I used:
drive setup
Here's the partition scheme:
- /dev/sda1: SYSTEM (pre-existing)
- /dev/sda2: C:, Win7 (pre-existing)
- /dev/sda3: /boot, ext2 (created)
- /dev/sda4: /, encrypted Arch root, cryptsetup/ext4 (created)
My process for creating the partitions is as follows:
- shrunk C: down from the Win7 built-in partition utility
- created two unformatted partitions with no drive letter using Minitool Partition Wizard, setting the partition ID to 0x83 for both
- booted from USB drive of the Arch installation .iso (downloaded Friday 5/29)
- booted x86_64 arch
# fdisk -l
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1e6513b3
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2101247 2099200 1G 7 HPFS/NTFS/exFAT
/dev/sda2 2101248 177278975 175177728 83.5G 7 HPFS/NTFS/exFAT
/dev/sda3 177278976 177541119 262144 128M 83 Linux
/dev/sda4 177541120 500103167 322562048 153.8G 83 Linux
# modprobe dm_crypt
# cryptsetup -c aes-xts-plain64 -s 512 -h sha512 -i 5000 -y luksFormat /dev/sda4
# cryptsetup open /dev/sda4 root
# mkfs.ext4 /dev/mapper/root
# mkfs.ext2 /dev/sda3
installation
I just followed the Arch installation guide but documented my steps to a text file just to be sure...
# mount /dev/mapper/root /mnt
# mkdir /mnt/boot
# mount /dev/sda3 /mnt/boot
### connect to internet
# pacstrap /mnt base
# genfstab -p /mnt >> /mnt/etc/fstab
# arch-chroot /mnt
# echo arch_zbook > /etc/hostname
# ln -sf /usr/share/zoneinfo/America/Chicago /etc/localtime
### uncomment en_US.utf-8 in /etc/locale.gen
# locale-gen
# echo LANG=en_US.UTF-8 > /etc/locale.conf
### add encrypt before "filesystem" in /etc/mkinitcpio.conf hooks
# mkinitcpio -p linux
# passwd
# pacman -S syslinux
# cp -r /usr/lib/syslinux/bios/*.c32 /boot/syslinux
# extlinux -i /boot
### the above echoes "/boot is device /dev/sda3"
Then I edited /boot/syslinux/syslinux.cfg:
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/mapper/root cryptdevice=/dev/sda4:root crypto=sha512:aes-xts-plain64:512:: rw
INITRD ../initramfs-linux.img
EDIT: I deleted the contents of /boot, reinstalled syslinux, linux, and mkinitcpio, and repeated the above with `extlinux -i /boot/syslinux`, noting that syslinux.cfg points to ../vmlinuz-linux. Same result.
Just to double check proper syslinux setup, here's the dir contents:
# ls /boot
initramfs-linux-fallback.img
initramfs-linux.img
ldlinux.c32
ldlinux.sys
lost+found
syslinux
vmlinuz-linux
# ls /boot/syslinux
cat.c32
chain.c32
cmd.c32
cmenu.c32
config.c32
cptime.c32
cpu.c32
cpuid.c32
cpuidtest.c32
debug.c32
dhcp.c32
disk.c32
dmi.c32
dmitest.c32
elf.c32
ethersel.c32
gfxboot.c32
gpxecmd.c32
hdt.c32
hexdump.c32
host.c32
ifcpu64.c32
ifcpu.c32
ifmemdsk.c32
ifplop.c32
kbdmap.c32
kontron_wdt.c32
ldlinux.c32
lfs.c32
libcom32.c32
libgpl.c32
liblua.c32
libmenu.c32
libutil.c32
linux.c32
ls.c32
lua.c32
mboot.c32
meminfo.c32
menu.c32
pci.c32
pcitest.c32
pmload.c32
poweroff.c32
prdhcp.c32
pwd.c32
pxechn.c32
reboot.c32
rosh.c32
sanboot.c32
sdi.c32
sysdump.c32
syslinux.c32
syslinux.cfg
vesa.c32
vesainfo.c32
vesamenu.c32
vpdtest.c32
whichsys.c32
zzjson.c32
EasyBCD and boot attempt
At this point, exited the arch-chroot, unmounted/closed my partitions, and rebooted into Win7. Using EasyBCD, I added a entry for a syslinux bootloader, pointing it to "Partition 3 (Linux - 128MiB)."
I reboot, get the EasyBCD menu, but then the lone words "Boot error" on a black screen. Any key press takes me to some sort of BIOS boot thingy which tells me to "Please install an operating system!" I think this is something built into the laptop BIOS, not anything from the syslinux side. Selecting "Boot existing OS" from the Arch install USB doesn't give me any options at all.
From what I can tell, I'm using the same procedure that I ended up with on this former troubleshooting exercise.
Thoughts
I'm really struggling to understand what I'm doing wrong. I originally had a couple variations on logical/extended partitions since I need my eventual setup to hold a shared TrueCrypt partition so I can access my work files from both Win7 and arch. I tried /boot as primary and Arch/TC as logicals, as well as a primary TC partition with boot/root as a logical drive combination. I've simplified to just primary partitions (as shown above) to troubleshoot.
It's quite difficult to troubleshoot as I don't know if this is an installation issue or an EasyBCD one. Is there a way to manually try and boot my HD arch install from the install USB? I wanted to try that using the "Boot existing OS" option, but am wondering if it fails since only /dev/sda1 features a bootable flag and it's encrypted so only the HP BIOS can handle it? I thought about making /dev/sda3 bootable, but from my reading I can only have one bootable flag on a Windows system.
On that note, I checked my BIOS settings and the MBR is set to "Legacy mode" vs. the othe UEFI alternatives, so I don't think that's an issue. I also used blkid to confirm that it's using an MBR (output was "dos").
I will try UUIDs in /etc/fstab and syslinux next, as there are some other posts (example) talking about this as a potential issue (and, indeed, I sometimes get my HD as /dev/sdb* when booting from the arch USB drive. I can also try grub2 in case it's a syslinux issue.
Thanks for any ideas/suggestions. Does anything look awry in my description/setup above? I can chroot and do stuff just fine... so I think the install appears to be sound; it's just booting it!
Last edited by jwhendy (2015-06-06 04:38:09)A bit of progress, though this couldn't be much more awful in my opinion. Installed Arch to an sdcard to use as a bootloader, only to find that I can't boot from an sdcard, even though the HP docs say there's an sdcard boot option in the BIOS (which there's not). If the BIOS were in UEFI mode, there is an sdcard option listed in the boot order, but not in legacy mode. Sigh.
I don't have another sdcard laying around that's big enough to install Arch on, as I'm using my sole 8g drive for the installation media (and no optical drive). Sigh.
I did, however, through trial and error get my sdd arch install to boot using the installation drive's "boot existing OS" option! Took me a while to figure it out. In my opinion the drive/partition numbering is quite odd. Using the Hardware Information tool, the usb stick shows up as the first drive (so I'd assume hd0), but it can't be as "hd0 3" got me into the sdd installation. I'd have assumed hd0 0 was /dev/sda1, but that must be incorrect, as hd0 3 is /dev/sda3.
So, where I'm at now:
- going to re-partition how I originally intended (with truecrypt shared storage as a primary partition and boot/root as logical partitions)
- reinstall arch
- try to boot using the above procedure from the installation media
If that goes well, I'll try to find some teensy tiny usb stick to use as a bootloader device unless someone has any insights on why I can't boot by chainloading from Windows. I think at this point I've narrowed it down to a BIOS or drive numbering or EasyBCD issue, so maybe this post isn't a good fit for the Arch forums after all. Sorry for all the noise/updates... just wanted to provide the updated information as I uncovered it.
Thanks if you have any ideas or things I could try. -
[SOLVED] Unable to Boot Windows 7 from GRUB
I recently reinstalled Arch onto my laptop (Lenovo Thinkpad t520) and have been having problems with Grub. For the last week I've been having trouble getting it to run grub at boot at all, only being able to run windows 7 by flagging it as the bootable drive. The other day I finally got it to boot into grub, and from grub I can boot into Arch. However, I can not boot into windows 7 through grub. When I attempt to, it throws an error:
Invalid EFI file path
I'm somewhat new to arch, and especially new to efi bootloading and such. Right now the only way I can get into windows is either booting from the arch install disk > boot other os and specifying partition 2 (where I have windows installed) or by pressing f12 at boot. When I do this (not sure what the term is, if anyone knows please tell me), it brings up a menu asking where I want to boot with "arch_efi" "cd drive" "Hard drive" etc. I choose hard drive and it will then boot to windows by default. Booting normally takes me to grub where I can boot into arch but not windows. If there's any more info you need please let me know and I'll try to provide it. Thanks in advance.
Also, here is my current partition setup
/dev/sda1 /boot/efi
/dev/sda2 Windows7
/dev/sda3 Extended partition containing sda 5,6, & 7
/dev/sda4 swap
/dev/sda5 /boot
/dev/sda6 /
/dev/sda7 /home
UPDATE
Terminator seems to be right (still on a roll!), so I wiped the partition I had grub on, removed grub, and installed syslinux. Now I have another problem that I'm hoping can be solved in the same thread to avoid another. It boots to syslinux no problem, and I can boot to windows from there all good, but when I select arch I get:
Root device mounted successfully but /sbin/init does not exist
I haven't been able to look for solutions too much on my own, but any help would be appreciated, thank you.
Last edited by IamFuzzles (2012-08-22 04:20:56)Terminator wrote:If I understand it correctly, what you are trying is impossible: you are trying to boot windows using UEFI on a disk with MBR partitioning. Windows 7 only supports UEFI on discs with GPT partitioning but AFAIK, extended partitions only exist in MBR partitioning.
i also saw this in the arch wiki, but i have a brand new lenovo ideapad y570 running windows 7 64-bit that i'm in the process of setting up for someone, and it has what i think is an efi system partition but the disk uses mbr partitioning. does anyone know why this might be, or is there a way i can verify that the system is actually being booted via bios-mbr?
Last edited by e_tank (2012-08-21 11:56:15) -
[SOLVED] Grub Problems Can boot Arch w/ grub edits only
I had 3 Linux OS's installed on this computer, Arch and 2 versions of Ubuntu on one hard drive.
The MBR belonged to Ubuntu, using grub2. I decided to get rid of the older Ubuntu (sda8 and 9) and add it's HDD space to my Arch home (sda12). Used the current Gparted live to modify the partitions and all went well, but of course, the numbers changed getting rid of 2 partitions.
No boot upon restart so I decided to get Arch's grub back to the MBR with the new partition numbering scheme.
Using a live CD, I used the grub shell, find /boot/grub/stage1.....etc, etc. and after a bit of fumbling, grub indicated success in the shell. When I was through though, a reboot was not successful, although the current stable grub was now written to the MBR. I edited the lines using grub edit option, and got Arch to boot, and figured out the correct partition numbers. Next I edited the menu.lst to reflect the new sda numbers.
Now rebooting results in a long delay when grub should be on the screen, and the numbers on the Arch entries reflect the old numbers still!! I double checked thinking I forgot to save the edits to the menu.lst file, but they are correct. I can boot Arch, but have to edit the lines each time.
The current partitions are as follows. I edited the terminal output to show details.
[jeff@Arch2009p2 ~]$ sudo fdisk -l
Password:
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000383e7
Device Boot Start End Blocks Id System
/dev/sda1 * 1 91201 732572001 5 Extended
/dev/sda5 1 255 2048224+ 82 Linux swap / Solaris
/dev/sda6 (ubuntu /) 256 1471 9767488+ 83 Linux
/dev/sda7 (ubuntu /home) 1472 22321 167477593+ 83 Linux
/dev/sda8 (arch boot) 22322 22325 32098+ 83 Linux
/dev/sda9 (arch /) 22326 23627 10458283+ 83 Linux
/dev/sda10 (arch /home) 23628 91201 542788123+ 83 Linux
I have a few questions regarding a separate boot partition for Arch.
Should the grub> root (hd0.0) command be directed to the root or boot partition.
My handy printed emergency guide says: Set grubs root device to the partition containing the boot directory.
OK.....Writing it out now, it seems clear, so I'll try reinstalling grub from a live CD.
Why does grub have incorrect partition numbers even though the menu.lst is correct?
There are only 2 OS's on this box now, and one contains grub2.
Is current grub able to interact with grub 2 if I screwed something up on the install?
Last edited by jeff story (2010-05-24 20:05:06)OK
I managed to fix the problem of grub not reading/using the menu.lst file. Not sure WTF it was reading and where that file was located!
The problem seems to have been the most insignificant detail.
When using the grub terminal, I did not execute the quit command when I was through. I just closed the terminal and rebooted.
After repeating the following code via live CD a few times:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
Grub still didn't read the current menu.lst.
This morning I got things to work correctly and grub to read the current menu.lst by adding a quit command and returning to the linux shell prior to rebooting.
I used the following commands:
$ sudo grub
grub> find /grub/stage1
grub> root (hd0,7)
grub> setup (hd0)
grub> quit -
DRMK when booting to W7 from grub
Hi.
I've got myself a brand new Precision M4600 laptop, and decided to dual boot Archie and Windows 7. So I received the Precision with w7 installed, btw i've got a 256gb SSD which is partitioned as shown:
[ama@ama-precision ~]$ sudo fdisk -l
Disk /dev/sda: 256.1 GB, 256060514304 bytes
255 heads, 63 sectors/track, 31130 cylinders, total 500118192 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4e92f42b
Device Boot Start End Blocks Id System
/dev/sda1 * 63 80324 40131 6 FAT16
/dev/sda2 81920 1622015 770048 7 HPFS/NTFS/exFAT
/dev/sda3 1622016 266729471 132553728 7 HPFS/NTFS/exFAT
/dev/sda4 266729472 500103449 116686989 5 Extended
/dev/sda5 266729535 275517026 4393746 83 Linux
/dev/sda6 275517090 324338561 24410736 83 Linux
/dev/sda7 324338625 500103449 87882412+ 83 Linux
I installed GRUB on the mbr, install goes fine, arch goes fine (posting this message from arch, met some issues though but nvm) but when i try to boot to w7 from grub, it shows:
Booting Windows 7
rootnoverify (hd0,0)
chainloader +1
Loading DRMK V8.00...
DRMK Version 8.00
COMMAND.COM Build 37 - Jul 20, 2008
DRMK KERNEL Build 15 - Aug 8, 2008
Copyright (c) 2006-2008 Dell Inc. All rights reserved.
C:\>
so wtf is this dell drmk thing ? Googling didn't help me that much...
Oh and here's my menu.lst
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,1)
# /dev/sda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# for more details and different resolutions see
# http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
title Arch Linux
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6 ro
initrd /boot/kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6 ro
initrd /boot/kernel26-fallback.img
# (2) Windows
title Windows 7
rootnoverify (hd0,0)
#makeactive
chainloader +1
i've also tried uncommenting the makeactive line but no help.
thanks for your help.rootnoverify (hd0,0) = /dev/sda1
rootnoverify (hd0,1) = /dev/sda2
see whitch one is your windows installed sda2 or sda3 and point that into /boot/grub/menu.lst
aka..
# (2) Windows
title Windows 7
rootnoverify (hd0,1)
#makeactive
chainloader +1
or
# (2) Windows
title Windows 7
rootnoverify (hd0,2)
#makeactive
chainloader +1 -
Installed, but stuck at GRUB prompt
After 4 tries, I have managed to install 0.8. On the reboot, however, I only get as far as a "GRUB>" prompt.
If I put the install disk in the drive, enter "reboot" at the GRUB prompt, and choose the option "Run installed system (/boot on a separate partition)", I am able to get a login prompt and start what appears to be a functional (base) system. But I have clearly missed something in the installation. I have a /boot/grub/menu.lst file; the noncommented lines are as follows:
timeout 5
default 0
color light-blue/black light-cyan/blue
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26-fallback.img
kernel26.img and kernel26-fallback.img are both in the /boot directory.
What do I need to fix to make the system boot without a rescue disk?If you indeed have a boot partition on first partition of first drive (hd0,0; sda1) and a root one on third partition of a first drive (sda3), then your grub config seems to be alright. The example above is appropriate if there's no separate /boot partition.
When you're in a GRUB prompt, try entering those root/kernel/initrd lines by hand and check the output.
Last edited by lucke (2007-04-08 15:51:32) -
[Solved] Removing multiple entries from grub
Hi
There are many entries in my arch's grub boot loader:
Arch Linux pkg-linux kernel
*Arch Linux pkg-linux kernel (fallback initramfs)
Arch Linux
Advanced options for Arch Linux
Linux Mint 15
Advanaced options for Linux Mint 15
Microsoft Windows 7 Professional
But I also want to keep following three entries:
Arch Linux
Linux Mint 15
Microsoft Windows 7 Professional
How can I remove remaining entries from grub menu?
Regards
Last edited by zetrotrack000 (2014-03-11 20:01:45)Grub2 menu entries are created by a set of scripts in /etc/grub.d
Your first 2 entries are standard for arch and are generated by the 10_archlinux script. The 10_archlinux script is distributed by arch. It exists because the standard 10_linux script does not always create reliable menu entries for arch.
Your other linux entries are generated by the 10_linux script which is distributed by grub upstream.
Your windows entry is generated by the os-prober script. That can just be left alone.
To sort out the redundant linux entries you could try disabling either of the linux scripts and regenerating the menu.
Alternatively, you could disable both linux scripts and define your menu entries manually in the 40_custom script. The syntax for custom menu entries is similar to that of grub legacy. See the grub wiki article for info.
Hope this helps!
Last edited by Chazza (2014-03-10 22:45:18)
Maybe you are looking for
-
Office 2010 mail merge with section breaks printing problem
Afternoon all, We have an issue and I was wondering if anyelse has come across this and has a solution Our office staff do many mail merges and once the merge is complete they then can print the whole document with no problems or select one page and
-
Put another way, how can I find out which plugin updates Firefox or Mozilla recommends for my computer?
-
I have an IPhone 4S. All my color pictures and icons turned to looking like a negative. No color! How do I get the color back on my phone?
-
IC Webclient: Blank Page
Hello Friends, In last days, for the first time, we are trying to launch a 2007 IC Webclient application in a machine with SP2. However, when we try to load it and after we choose the profile, we get a blank page. We searched and searched in this for
-
After installing the latest driver update for my nVidia GT 330, I couldn't hear voice on my LG plasma TV when I conntected it to laptop through HDMI, so I rolled back the driver to the earlier version and the sound returned back. Any solution for tha