[SOLVED] Boot to graphical or terminal via GRUB?

Any idea how to do that?  Right now I start up SLiM using inittab, and I'm using fbsplash for a boot-splash.
Thanks
Last edited by tbgconno (2012-04-12 03:09:43)

Go ahead and edit your first post in the thread.  That gives you the ability to change the thread title.  Just add [SOLVED] to the beginning of the thread title.
We ask you to do it, because only you know when it is truly solved

Similar Messages

  • [SOLVED] Boot 'really' directly, quickly? (using GRUB)

    Hi there, just a silly question: is there a way to boot 'really' directly the OS?
    I mean, I have Arch only on my hd, so I use hiddenmenu and timeout 0, but it seems that GRUB still wastes time loading useless stuff... or not?
    Thank you in advance
    Last edited by metre (2011-03-13 11:43:46)

    tomk wrote:Can you define "useless stuff" please?
    I meant that maybe there was a way to avoid to load all the 'menu.lst' config in order to go straight to the action
    Anyway, I read others' suggestions, thank you very much very interesting indeed
    Last edited by metre (2011-03-13 11:41:57)

  • [Solved] lost booting to graphical interphace

    I've had arch for about a week and I really like it. However today I did some daily configuring and shut down the machine. Now when I opened it later today I see that I couldnt boot into graphical interphace! Arch just throws me straightly to command prompt (I am writing this from Ubuntu).
    Here is my /var/log/Xorg.0.log:
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    X.Org X Server 1.6.1.901 (1.6.2 RC 1)
    Release Date: 2009-5-8
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.30-ARCH i686
    Current Operating System: Linux myhost 2.6.30-ARCH #1 SMP PREEMPT Sat Jul 4 11:13:08 UTC 2009 i686
    Build Date: 28 June 2009 11:20:52AM
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 17 11:14:16 2009
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "X.org Configured"
    (**) |-->Screen "Screen0" (0)
    (**) | |-->Monitor "Monitor0"
    (**) | |-->Device "Device0"
    (**) |-->Input Device "Mouse0"
    (**) |-->Input Device "Keyboard0"
    (**) Option "Xinerama" "0"
    (**) Option "AllowEmptyInput" "False"
    (**) Option "AutoAddDevices" "False"
    (**) Not automatically adding devices
    (==) Automatically enabling devices
    (**) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1,
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1,
    built-ins
    (**) ModulePath set to "/usr/lib/xorg/modules"
    (**) Extension "Composite" is enabled
    (II) Loader magic: 0x640
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 5.0
    X.Org XInput driver : 4.0
    X.Org Server Extension : 2.0
    (II) Loader running on linux
    (++) using VT number 7
    (--) PCI: (0:0:1:3) 10de:0753:1043:82f2 nVidia Corporation MCP78S [GeForce 8200] Co-Processor rev 162, Mem @ 0xf9f80000/524288
    (--) PCI:*(0:2:0:0) 10de:0614:1458:34ae nVidia Corporation GeForce 9800 GT rev 162, Mem @ 0xfd000000/16777216, 0xd0000000/268435456, 0xfa000000/33554432, I/O @ 0x0000ec00/128, BIOS @ 0x????????/131072
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) System resource ranges:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [25] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [27] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [29] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
    (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    (II) "record" will be loaded. This was enabled by default and also specified in the config file.
    (II) "dri" will be loaded by default.
    (II) "dri2" will be loaded. This was enabled by default and also specified in the config file.
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Server Extension
    (II) NVIDIA GLX Module 185.18.14 Wed May 27 03:09:07 PDT 2009
    (II) Loading extension GLX
    (II) LoadModule: "record"
    (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
    (II) Module record: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 1.13.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension RECORD
    (II) LoadModule: "dri2"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
    (II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DRI2
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "nvidia"
    (II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
    (II) Module nvidia: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    Module class: X.Org Video Driver
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
    compiled for 1.6.0, module version = 1.4.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
    compiled for 1.6.0, module version = 1.3.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
    (II) NVIDIA dlloader X Driver 185.18.14 Wed May 27 02:32:54 PDT 2009
    (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    (II) Primary Device is: PCI 02@00:00:0
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (II) Loading sub module "wfb"
    (II) LoadModule: "wfb"
    (II) Loading /usr/lib/xorg/modules//libwfb.so
    (II) Module wfb: vendor="X.Org Foundation"
    compiled for 1.6.1.901, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Module "ramdac" already built-in
    (II) resource ranges after probing:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [25] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [27] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [29] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    (==) NVIDIA(0): RGB weight 888
    (==) NVIDIA(0): Default visual is TrueColor
    (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    (**) NVIDIA(0): Option "TwinView" "0"
    (**) NVIDIA(0): Option "MetaModes" "1680x1050 +0+0"
    (**) NVIDIA(0): Enabling RENDER acceleration
    (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    (II) NVIDIA(0): enabled.
    (II) NVIDIA(0): NVIDIA GPU GeForce 9800 GT (G92) at PCI:2:0:0 (GPU-0)
    (--) NVIDIA(0): Memory: 524288 kBytes
    (--) NVIDIA(0): VideoBIOS: 62.92.6d.00.07
    (II) NVIDIA(0): Detected PCI Express Link width: 16X
    (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    (--) NVIDIA(0): Connected display device(s) on GeForce 9800 GT at PCI:2:0:0:
    (--) NVIDIA(0): LG M1994D-PZ (CRT-1)
    (--) NVIDIA(0): LG M1994D-PZ (CRT-1): 400.0 MHz maximum pixel clock
    (II) NVIDIA(0): Assigned Display Device: CRT-1
    (II) NVIDIA(0): Validated modes:
    (II) NVIDIA(0): "1680x1050+0+0"
    (II) NVIDIA(0): Virtual screen size determined to be 1680 x 1050
    (--) NVIDIA(0): DPI set to (106, 106); computed from "UseEdidDpi" X config
    (--) NVIDIA(0): option
    (==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don't.
    (II) resource ranges after preInit:
    [0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [8] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [12] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [16] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
    [17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [20] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [21] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [23] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [25] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [27] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [29] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (II) NVIDIA(0): Initialized GPU GART.
    (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    (II) NVIDIA(0): configuration option may not be set correctly. When the
    (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    (II) NVIDIA(0): Config Options in the README.
    (II) NVIDIA(0): Setting mode "1680x1050+0+0"
    (II) Loading extension NV-GLX
    (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
    (==) NVIDIA(0): Disabling shared memory pixmaps
    (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
    (==) NVIDIA(0): Backing store disabled
    (==) NVIDIA(0): Silken mouse enabled
    (II) NVIDIA(0): DPMS enabled
    (II) Loading extension NV-CONTROL
    (II) Loading extension XINERAMA
    (==) RandR enabled
    (II) Initializing built-in extension Generic Event Extension
    (II) Initializing built-in extension SHAPE
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension BIG-REQUESTS
    (II) Initializing built-in extension SYNC
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-MISC
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing extension GLX
    (**) Option "Protocol" "auto"
    (**) Option "Device" "/dev/input/mice"
    (II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
    (**) Mouse0: Device: "/dev/input/mice"
    (**) Mouse0: Protocol: "auto"
    (**) Option "CorePointer"
    (**) Mouse0: always reports core events
    (**) Option "Device" "/dev/input/mice"
    (**) Option "Buttons" "7"
    (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
    (**) Option "ZAxisMapping" "4 5 6 7"
    (**) Mouse0: ZAxisMapping: buttons 4, 5, 6 and 7
    (**) Mouse0: Buttons: 11
    (**) Mouse0: Sensitivity: 1
    (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
    (**) Mouse0: (accel) keeping acceleration scheme 1
    (**) Mouse0: (accel) filter chain progression: 2.00
    (**) Mouse0: (accel) filter stage 0: 20.00 ms
    (**) Mouse0: (accel) set acceleration profile 0
    (II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
    (II) Mouse0: ps2EnableDataReporting: succeeded
    (**) Option "CoreKeyboard"
    (**) Keyboard0: always reports core events
    (**) Option "Protocol" "standard"
    (**) Keyboard0: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard0: XkbRules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) Keyboard0: XkbModel: "pc105"
    (**) Option "XkbLayout" "fi"
    (**) Keyboard0: XkbLayout: "fi"
    (WW) Option "XkbVariant" requires an string value
    (**) Option "XkbOptions" "terminate:ctrl_alt_bksp"
    (**) Keyboard0: XkbOptions: "terminate:ctrl_alt_bksp"
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard0: CustomKeycodes disabled
    (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
    I'll provide more details as you ask for them.
    Thanks for everyone in advance!
    Edit: Well when I do "startxfce4", I get the graphical interphace, but there is no internet connection.
    Edit 2: Well, "dhcpcd eth0" brings it . But I really wouldn't want to do those two commands upon every boot.
    Last edited by algorythm (2009-07-18 13:20:24)

    Mr.Elendig wrote:pacman -Qs gnome
    bash-4.0$ sudo powerpill -Qs gnome
    local/alacarte 0.12.1-1 (gnome-extra)
    Menu editor for gnome
    local/banshee 1.4.3-3
    Music management and playback for GNOME
    local/brasero 2.26.3-1
    A disc burning application for Gnome
    local/bug-buddy 2.26.0-2 (gnome-extra)
    A bug reporting tool for GNOME
    local/compiz-decorator-gtk 0.8.2-2 (compiz compiz-gnome)
    Decorator of Compiz for GNOME
    local/deskbar-applet 2.26.2-1 (gnome-extra)
    An all-in-one search bar for the GNOME panel
    local/eel 2.26.0-1
    Eazel Extensions Library is a collection of widgets and extensions for GNOME
    local/ekiga 3.2.4-1 (gnome-extra)
    VOIP/Videoconferencing app with full SIP and H.323 support (GnomeMeeting
    expanded and renamed)
    local/eog 2.26.3-1 (gnome-extra)
    Eye of Gnome: An image viewing and cataloging program
    local/epiphany 2.26.3-1 (gnome)
    A GNOME2 web browser based on the mozilla rendering engine.
    local/evolution-data-server 2.26.3-1
    Evolution Data Server provides a central location for addressbook and
    calendar in the GNOME Desktop
    local/fast-user-switch-applet 2.24.0-1 (gnome-extra)
    An applet for the GNOME panel which provides a menu to switch between users.
    local/file-roller 2.26.3-1 (gnome-extra)
    Archive manipulator for GNOME2
    local/gcalctool 5.26.3-1 (gnome-extra)
    GNOME Scientific calculator
    local/gdm 2.20.10-1 (gnome-extra)
    Gnome Display Manager (a reimplementation of xdm)
    local/gdome2 0.8.1-2
    Gnome DOM Engine
    local/gedit 2.26.3-1 (gnome-extra)
    A text editor for GNOME
    local/glade 3.6.7-1
    user interface builder for GTK+ and GNOME.
    local/gnome-alsamixer 0.9.6-2
    Gnome ALSA mixer
    local/gnome-applets 2.26.3-1 (gnome)
    GNOME Applets
    local/gnome-audio 2.22.0-1 (gnome-extra)
    GNOME Audio files
    local/gnome-backgrounds 2.24.1-1 (gnome)
    Background images and data for GNOME
    local/gnome-control-center 2.26.0-1 (gnome)
    The Control Center for GNOME
    local/gnome-desktop 2.26.3-1 (gnome)
    The GNOME Desktop
    local/gnome-desktop-sharp 2.26.0-1
    GNOME desktop bindings for C#
    local/gnome-doc-utils 0.16.1-1
    Documentation utilities for Gnome
    local/gnome-games 2.26.3-1 (gnome-extra)
    Some Games for GNOME
    local/gnome-games-extra-data 2.26.0-1 (gnome-extra)
    Optional extra data for gnome-games
    local/gnome-icon-theme 2.26.0-1 (gnome)
    Default icon theme for GNOME2
    local/gnome-keyring 2.26.3-1
    GNOME Password Management daemon
    local/gnome-mag 0.15.7-1 (gnome-extra)
    Gnome magnifier
    local/gnome-media 2.26.0-1 (gnome)
    GNOME Media Tools
    local/gnome-menus 2.26.2-1
    GNOME menu specifications
    local/gnome-mime-data 2.18.0-3 (gnome)
    The base MIME and Application database for GNOME
    local/gnome-mount 0.8-1 (gnome)
    GNOME mount program
    local/gnome-netstatus 2.26.0-1 (gnome-extra)
    A GNOME applet that shows network status
    local/gnome-nettool 2.26.2-1 (gnome-extra)
    A Collection of GNOME2 Networking Tools.
    local/gnome-panel 2.26.3-1 (gnome)
    The GNOME Panel
    local/gnome-pilot 2.0.17-1
    Pilot Support for Gnome
    local/gnome-power-manager 2.26.2-1 (gnome-extra)
    Session daemon that makes it easy to manage your laptop or desktop system.
    local/gnome-python 2.26.1-1
    gnome-python is a set of interfaces to gnome-libs.
    local/gnome-python-desktop 2.26.0-1
    Gnome Python interfaces for libraries not part of the core platform
    local/gnome-python-extras 2.25.3-2
    Gnome Python interfaces for libraries not part of the core platform
    local/gnome-screensaver 2.26.1-1 (gnome)
    Screensaver designed to integrate well with the GNOME desktop.
    local/gnome-session 2.26.2-1 (gnome)
    The GNOME Session Handler
    local/gnome-settings-daemon 2.26.1-1 (gnome)
    The GNOME Settings daemon
    local/gnome-sharp 2.24.1-1
    GNOME bindings for C#
    local/gnome-speech 0.4.25-1
    Gnome Text-to-Speech
    local/gnome-subtitles 0.8-6
    Subtitle editor for the GNOME Desktop
    local/gnome-system-monitor 2.26.2-1 (gnome-extra)
    A system monitor for GNOME
    local/gnome-system-tools 2.22.2-1
    Gnome System Configuration Utilities
    local/gnome-terminal 2.26.3.1-1 (gnome-extra)
    The GNOME Terminal Emulator
    local/gnome-themes 2.26.3.1-1 (gnome)
    Default themes for GNOME2
    local/gnome-themes-extras 2.22.0-1
    Extra themes for GNOME2
    local/gnome-utils 2.26.0-1 (gnome-extra)
    Common utilities for GNOME
    local/gnome-vfs 2.24.1-2
    The GNOME Virtual File System
    local/gnome-volume-manager 2.24.1-1 (gnome-extra)
    GNOME daemon to auto-mount and manage media devices
    local/gnome2-user-docs 2.26.2-1 (gnome)
    User documentation for GNOME2
    local/gok 2.26.0-1 (gnome-extra)
    Gnome Onscreen Keyboard
    local/gstreamer0.10-base-plugins 0.10.23-1 (gstreamer0.10-plugins)
    GStreamer Multimedia Framework Base Plugins (gst-plugins-base)
    local/gtksourceview 1.8.5-2
    A text widget adding syntax highlighting and more to GNOME
    local/gtksourceview2 2.6.2-1
    A text widget adding syntax highlighting and more to GNOME
    local/gucharmap 2.26.3.1-1 (gnome-extra)
    Gnome Unicode Charmap
    local/hamster-applet 2.26.3-1 (gnome-extra)
    GNOME time tracking applet
    local/icon-naming-utils 0.8.90-1
    Maps the new names of icons for Tango to the legacy names used by the GNOME
    and KDE desktops.
    local/libcroco 0.6.2-1
    GNOME CSS2 parsing and manipulation toolkit
    local/libgail-gnome 1.20.1-1 (gnome)
    GNOME Accessibility Implementation Library for gnomeui and libbonoboui
    local/libgnome 2.26.0-2
    Common libraries for GNOME
    local/libgnomecanvas 2.26.0-1
    The GNOME Canvas library
    local/libgnomecups 0.2.3-4
    GNOME cups library
    local/libgnomekbd 2.26.0-1
    Gnome keyboard library
    local/libgnomeprint 2.18.6-1
    Printing routines for GNOME
    local/libgnomeprintui 2.18.4-1
    User Interface library for printing with GNOME
    local/libgnomeui 2.24.1-1
    User Interface library for GNOME
    local/libgsf 1.14.14-1
    The GNOME Structured File Library is a utility library for reading and
    writing structured file formats.
    local/libgsf-gnome 1.14.14-1
    Adds gnome support to libgsf
    local/libsoup 2.26.3-1
    Gnome HTTP Library
    local/listen 0.6.2-1
    Music player and management for GNOME
    local/metacity 2.26.0-2 (gnome)
    A window manager for GNOME2
    local/mousetweaks 2.26.3-1 (gnome-extra)
    Mouse accessibility enhancements for the GNOME desktop
    local/nautilus 2.26.3-1 (gnome)
    The GNOME shell and file manager
    local/policykit-gnome 0.9.2-4
    PolicyKit integration for the GNOME desktop
    local/seahorse 2.26.2-1 (gnome-extra)
    GNOME application for managing PGP keys.
    local/system-tools-backends 2.6.0-3
    backends for Gnome System Tools
    local/vinagre 2.26.2-1 (gnome-extra)
    A VNC Client for the GNOME Desktop
    local/vino 2.26.2-2 (gnome-extra)
    a VNC server for the GNOME desktop
    local/xfwm4 4.6.1-1 (xfce4)
    Xfce window manager, compatible with Gnome, Gnome2, KDE2, and KDE3
    local/yelp 2.26.0-3 (gnome)
    A help browser for GNOME
    Do you have hal in your daemons array?
    No I didn't actually !! I just had "(syslog-ng network netfs crond)". Dunno why my rc.conf defaulted to that.. I believe that fixed the problem. I'll boot later today.. but hey, if that did indeed fix the problem: you're the man !
    I myself would never had even thought about that.
    Edit: yep, that fixed this. Thanks again!! -> marking as [Solved].
    Last edited by algorythm (2009-07-18 13:21:42)

  • Dual boot windows from USB via grub?

    HI all:
    I recently had a motherboard failure on an existing PC on which I dual-booted Windows XP and Gentoo.  I replaced that box with a new HP PC preloaded with Vista.  Wiped that immediately, and installed ARCH.  But, I would like to also boot XP, and, since my old hard drive is still OK (I have it in an external USB adapter), I was thinking that I might configure grub to point at an external USB drive like this:
    # Windows XP
    title Windows XP
    root (hd1,0)
    makeactive
    chainloader +1
    where "hd1" (I hope) would point at my old drive, now connected via USB.  In this way, I am really booting from my HDD (where grub lives), but "chain loading" from my USB external.  Can this work??
    -dvh

    dvh wrote:
    I configured as shown in the wiki, but when I try to boot XP, I get a message that says something to the effect of "missing or corrupted <windows root>\system32\ntoskrnl.exe".  I checked the disk and it seems to be there and OK.  I get the feeling that it is either NOT finding the hard disk (or partition) or it cannot interpret the NTFS file system (but grub was able to boot this before,...).  So, two questions...
    1) how do I know what the designator for the external USB hard disk will be?  I have speculated that grub will find it at "hd1", but maybe not?
    2) does the target disk NEED a windows boot loader?  as I said earlier, I used to dual boot it, so there is a grub loader on that disk also.
    ...ok, three questions...
    3) anything else that I should consider??
    Thanks again for any help.
    -dvh
    1) i don'tknow a way to check this, but the
    missing or corrupted <windows root>\system32\ntoskrnl.exe message comes from the windows boot process,
    so it seems grub is configured correctly.
    The main problem is that BOTH grub and windows boot need to have the correct settings.
    Windows takes the settings for boot from the boot.ini file in the root of C:\ , and that probably needs to be changed.
    You will need some way to get read/write access to the windows C-drive partition.
    Install ntfs-3g in archlinux (see NTFS_Write_Support ) and post the contents of boot.ini .

  • [PARTIALLY SOLVED] Arch on MacBook4: can't install GRUB

    I've been running Arch on my MacBook4 (4 years old now) for quite some time in dualboot mode and have already set up GRUB sucessfully several times. I therefore feel kinda bad that I have to open a new thread this time, but after wasting the whole morning on Google, I don't see another solution.
    What has happened is that I had to resize my Linux partitions because there was no space left on my system partition. I have the following partitions:
    sda1 - fat32 EFI partition
    sda2 - hfs+ Mac partition
    sda3 - ext4 Arch system partition
    sda4 - ext4 Arch home partition
    As mentioned, when I first organized my Arch partitions this way, I could successfully set up GRUB, but it was GRUB1 which I had to set up via grub shell. Now, as it looks to me, GRUB1 is not available anymore but only GRUB2 which doesn't use the grub shell anymore. I've not been able to install GRUB2 the last time (that's why I ended up using GRUB1) and I'm still not able to install it this time!
    When I start the MacBook and choose the Linux partition in rEFIt, I get to a black screen displaying GRUB_ and doing nothing more (because I don't have GRUB set up). That's how far I am right now.
    Now can anyone help me with setting up GRUB(2)? Thanks in advance for any help!
    Last edited by cryptkeeper (2012-09-05 06:13:14)

    I've succeeded in working around the problem of installing GRUB2 after I found out that grub-legary is nothing else but GRUB1. So all I had to do to get back a running system was:
    - removing the GRUB2 installation
    - installing grub-legacy
    - copying my old menu.lst to /boot/grub/
    - grub shell: root (hd0,2); setup (hd0); quit
    Now it works like a charm again.
    Still I only consider this thread half solved because I still don't know how to install GRUB2 on my system. It's not of vital interest to me anymore (I don't care too much why, that is, due to which boot loader, my system boots, as long as it boots), but a solution would nonetheless be nice since this thread is opened anyway.
    So: How can GRUB2 be installed on a MacBook dualboot system with rEFIt such as mine?

  • [Solved]Boot from USB HDD - Root device doesn't exist. Major/minor

    My problem is that the kernel seems (or starts) to load, but then I get an error:
    Root device 'UUID=1234 . . .' doesn't exist.
    Attempting to create it.
    ERROR: Unable to determine major/minor number of root device "UUID=1234 . . .'
    You are being dropped into recovery shell
    I found a few links on the web and in the forums, but nothing that really solved it for me. The solved ones usually downgraded the kernel.  I haven't done that yet.  I thought I'd try here first.
    I have a 320GB USB HDD that I have been using to experiment with different linux distros.  I have a few working successfully (OpenSUSE,Mint,Ubuntu,Debian,Fedora,etc).  I'm very new at this but have been reading a lot and putting a lot of time into it.  I have legacy grub loaded on the MBR and use the menu.lst on my openSUSE partition to boot everything.  Because the partitions for some of the distros are so far into the disk I needed to create directories on openSUSE's /boot directory to contain the kernel and initrramfs files (like /boot/fedora).  This seems to work for the other distros.  I did the same thing for Arch.
    So when I installed Arch I haven't used the bootloader section of the installation.
    I'm using the 2011.08.09-netinstall-i686.iso Live CD.
    I tried a few things including:
    1.    changing the HOOKS in /etc/mkinitcpio.conf
        a.    adding usb to the "HOOKS"
        b.    removing and adding autodetect
        c.    adding and removing "sata_sil" (although I'm not even sure if my device uses it)
    2.    changing the kernel line:
        a.    from using "UUID=" to (hd0,1) to sdb1.
        b.    added rootdelay=8
    3.    repartition all of my arch partitions using cfdisk from my Live CD and reinstall. I used gparted on OpenSUSE to do it the first time.
    This may be connected. When I fdisk -l from the Arch Live CD I get extra data and an error for each of my arch partitions (and only my arch partitions):
    Disk does't contain a valid partition table
    When I fdisk -l from OpenSUSE I don't get the data paragraphs or errors about the arch partitions?
    Here is my /etc/fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    UUID=0e7556ef-b832-43e9-a8ba-c68dd2cd6143 /var reiserfs defaults 0 1
    UUID=510bb601-13c1-46ec-87c0-a800dd2efb8b / ext4 defaults 0 1
    UUID=cd78ab04-742d-4ba5-9727-90727de2dd14 swap swap defaults 0 0
    UUID=dc5685e3-35b0-46d4-b259-61f2530ff36a /home ext3 defaults 0 1
    And my HOOKS:
    HOOKS="base udev autodetect pata scsi sata usb filesystems usbinput"
    And my menu.lst:
    1
    default 0
    timeout 32
    gfxmenu (hd0,1)/boot/message
    ###openSUSE on sda2 - legacy grub
    title openSUSE 11.4 - Celadon - gnome
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.37.6-0.7-default root=/dev/disk/by-id/usb-Seagate_FreeAgent_GoFlex_NA0E702X-0:0-part2 resume=/dev/disk/by-id/usb-Seagate_FreeAgent_GoFlex_NA0E702X-0:0-part1 splash=silent quiet showopts nomodeset vga=0x314
    initrd /boot/initrd-2.6.37.6-0.7-default
    ###openSUSE failsafe on sda2 - legacy grub
    title Failsafe -- openSUSE 11.4 - 2.6.37.6-0.7
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.37.6-0.7-default root=/dev/disk/by-id/usb-Seagate_FreeAgent_GoFlex_NA0E702X-0:0-part2 showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x314
    initrd /boot/initrd-2.6.37.6-0.7-default
    ###floppy###
    #title Floppy
    # rootnoverify (fd0)
    # chainloader +1
    ###Fedora on sda5 - legacy grub
    title Fedora 15-Lovelock gnome
    root (hd0,4)
    configfile /boot/grub/grub.conf
    ###Mint on sda6 - grub2
    title Mint 9 Lucid Lynx gnome
    root (hd0,5)
    kernel /boot/grub/core.img
    savedefault
    boot
    ###PCLinux on sda7 - legacy grub
    title PCLinuxOS 2011.6 KDE
    root (hd0,6)
    chainloader +1
    ###Ubuntu on sda8 - grub2
    title Ubuntu 10.04.2 gnome
    root (hd0,7)
    kernel /boot/grub/core.img
    savedefault
    boot
    ####arch on sda10 - legacy grub
    title ARCH
    root (hd0,1)
    #root UUID=XXXXXXXXXX44c5a3cd-dcb5-4cf1-933e-7a8ebac2a992
    kernel /boot/arch/vmlinuz-linux root=UUID=510bb601-13c1-46ec-87c0-a800dd2efb8b ro rootdelay=8
    #kernel /boot/arch/vmlinuz-linux root=(hd0,9)
    #kernel /boot/arch/vmlinuz-linux root=/dev/sda10
    initrd /boot/arch/initramfs-linux.img
    savedefault
    boot
    ###Debian on sda11 - grub2
    title Debian 6.0.2.1 squeeze gnome
    root (hd0,1)
    kernel /boot/debian/vmlinuz-2.6.32-5-686 root=UUID=2b6052e2-ecdf-4796-81c8-b9e9142ca159 ro
    initrd /boot/debian/initrd.img-2.6.32-5-686
    savedefault
    boot
    ###Mandriva on sda12 - legacy grub
    title Mandriva 2011 KDE
    root (hd0,1)
    kernel /boot/mandriva/vmlinuz-2.6.38.7-desktop-1mnb2 root=UUID=5033f7fb-cac7-4db5-920c-c8bd2b51365f ro
    initrd /boot/mandriva/initramfs-2.6.38.7-desktop-1mnb2.img
    savedefault
    boot
    Here is my fdisk -l from OpenSUSE.  I'm not quite swift enough to mount the hard drive and use the script utility from the Live CD yet, at least not tonight:
    Disk /dev/sda: 320.1 GB, 320072932864 bytes
    255 heads, 63 sectors/track, 38913 cylinders, total 625142447 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: 0x000c3bbb
    Device Boot Start End Blocks Id System
    /dev/sda1 2048 4208639 2103296 82 Linux swap / Solaris
    /dev/sda2 4208640 46153727 20972544 83 Linux
    /dev/sda3 46153728 87113727 20480000 83 Linux
    /dev/sda4 87115770 614031755 263457993 5 Extended
    /dev/sda5 87115776 128075775 20480000 83 Linux
    /dev/sda6 128077824 169037823 20480000 83 Linux
    /dev/sda7 169039872 209999871 20480000 83 Linux
    /dev/sda8 210001920 250961919 20480000 83 Linux
    /dev/sda9 250963968 291923967 20480000 83 Linux
    /dev/sda10 291924031 332886015 20480992+ 83 Linux
    /dev/sda11 332888064 373848063 20480000 83 Linux
    /dev/sda12 373848678 414992383 20571853 83 Linux
    /dev/sda13 414994432 435474431 10240000 83 Linux
    /dev/sda14 435474495 455956829 10241167+ 83 Linux
    /dev/sda15 455958528 578881535 61461504 b W95 FAT32
    /dev/sda16 578881599 614031755 17575078+ 83 Linux
    Disk /dev/sdb: 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
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x95aa95aa
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 63 294889139 147444538+ 7 HPFS/NTFS/exFAT
    /dev/sdb2 294889140 312576704 8843782+ 7 HPFS/NTFS/exFAT
    That's it for now.
    Last edited by newbie55 (2011-09-23 22:19:58)

    I'm IN!  Thanks everyone for your suggestions!
    The arch system didn't like the identifier I was using for the root partition. By looking at the /dev/disk/by-id while the arch system was running, I could see what the system wanted me to call the partition.  So after the system error'd-out and I was in the recovery shell at the [ramfs /] prompt:
    # ls -lF /dev/disk/by-id > by-id.txt
    # vi by-id.txt
    I could have used any of the identifiers listed in the by-id (there were 3), by-uuid(1), by-label(1) or by path(1). I tried them all. I had to write these down by hand because it is a ram filesystem.
    The article that finally got me there is:
    https://wiki.archlinux.org/index.php/Pe … ice_naming
    Anyway my openSUSE grub menu.lst ended up like this:
    ####arch on sda10 - legacy grub
    title ARCH
    root (hd0,1)
    kernel /boot/arch/vmlinuz-linux root=/dev/disk/by-uuid/510bb601-13c1-46ec-87c0-a800dd2efb8b ro rootdelay=8 rootfstype=ext4
    initrd /boot/arch/initramfs-linux.img
    savedefault
    boot
    It's easy once you: 1. beat your head against the wall
                        2. read further
                3. repeat 1 and 2
    Back to the "Beginner's Guide",4 Post-Installation.  Yikes!

  • Is it possible to delete the boot/startup volume from Terminal

    Is it possible to delete the boot/startup volume from Terminal?
    What sort of command would/could allow this?

    Is it possible to delete the boot/startup volume from Terminal?
    Do you mean is it possible to destroy your system from the Terminal? Anyone that has spend long enough working with Unix from a command line knows that answer. Yes! And a painful lesson it has been for many of us.
    The real question is, what is your goal?
    If you just want to erase lots of files, then the 'rm' command is available. Once all the files are erased, the rm command will be one of them, and so that is the end of the game. You will not be able to execute any more commands. The file system is still there, and the data in all those files is still on the disk, you have just eliminated the easy way to access that data (via file names).
    If you want to initialize a new file system on the disk, you could most likely do that (diskutil - it will be the last command you run from the terminal, but you could most likely do it). Again, the data is still there, but the file system structure that held all the names and allocation information has been eliminated.
    If you want to securely erase the disk, that is also possible (diskutil), and again, that will be the last command you will run from the terminal. Now nothing is left behind, neither data nor file system structure.
    What sort of command would/could allow this?
    rm and diskutil come to mind (in combination with sudo).
    You could also just boot from the installation DVD, and then from the Menu select the Disk Utility and erase the disk as well as give it a new file system. And since you are running from the OS stored on the DVD, you can do other things after the Disk Utility is finished.

  • My Internal HD became corrupt and it would not boot up so I installed My osx onto a new HD via usb and then inserted into my macbook pro but it wont boot up. It will only boot up if i connect via usb how can i boot it as an internal HD?

    My Internal HD became corrupt and it would not boot up so I installed My osx onto a new HD via usb and then inserted into my macbook pro but it wont boot up. It will only boot up if i connect via usb how can i boot it as an internal HD?

    Shootist007 wrote:
    If the system won't boot from the new drive the OP bought and install OS X on it it certainly won't boot from the original drives Recovery HD partition.
    Sorry genius.....but if the Recovery disk shows up that means the disk cable isn't bad.  Could be he did have a screwed up HDD and when he put the NEW HDD in (after putting the OS on it via USB) the computer didn't reconize it and therefore didn't boot the OS.  Just maybe right genius?  Don't rush to criticize someone's recommendations until you realize other possibilities.  (I did say "if it does")
    Thank you

  • [SOLVED] Booting to SD card (mmcblk0) with Grub2

    I have a laptop with win7/Ubuntu on the hard drive; this laptop also has an SDHC slot.
    For my own reasons I decided to install Arch on an SD card.
    I installed arch according to this very helpful post: http://bbs.archlinux.org/viewtopic.php?pid=398679
    Since the system already boots with Grub2 from the Ubuntu install I skipped the grub install steps.
    My BIOS cannot boot to SD cards (even with the bootable flag set on the mmcblk0p1 partition)
    I booted into Ubuntu and ran update-grub, this added the following entry to the Grub2 boot menu: "Arch (on /dev/mmcblk0p1)"
    Booting to this gives three errors:
    no such device (error lists correct UUID of SD card)
    hd2,1 cannot get C/H/S values
    you need to load the kernel first
    the entry in grub.cfg is:
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Arch (on /dev/mmcblk0p1)" {
    insmod ext2
    set root='(hd2,1)'
    search --no-floppy --fs-uuid --set 7b8f752b-2d7e-46f9-9989-77ff1e481b97
    linux /boot/vmlinuz26 root=/dev/mmcblk0p1
    initrd /boot/kernel26.img
    Last edited by crotonic (2010-05-22 05:23:01)

    I have got the system to boot the way I want and will try to detail it for others
    1) Make a kernel that can boot an SDHC card
    I found this list of needed kernel modules for doing this with ubuntu: http://www.linuxformat.com/forums/viewtopic.php?t=11709
    First I chroot-ed from ubuntu into my sd card according to: http://wiki.archlinux.org/index.php/Ins … ting_Linux
    then using the wiki as my guide: http://wiki.archlinux.org/index.php/Mkinitcpio
    I copied /etc/mkinitcpio.conf to a new file /etc/mkinitcpio-custom.conf
    and edited the modules line to look like so
    MODULES="mmc_core mmc_block sdhci sdhci-pci"
    then ran (still while chroot-ed of course) note that the -k option should match the version that you are using (mine is 2.6.33)
    # mkinitcpio -c /etc/mkinitcpio-custom.conf -g /boot/kernel26-custom.img -k 2.6.33-ARCH
    exit the chroot back to ubuntu
    2) Move the files to the boot partition
    I am using ubuntu's partition as the boot since that is where grub2 is installed
    First I made a copy and renamed vmlinuz26 to vmlinuz26-custom
    and another copy/rename to make System.map26-custom
    NOTE: I am not sure if renaming these helps/hurts/or doesnt matter (feed back appreciated)
    then I moved those 2 files and kernel26-custom.img to the /boot of the ubuntu /
    3) Setup a working grub.cfg
    Since it is recommended to not edit grub.cfg directly in Grub2 I just added the following entry to /etc/grub.d/40_custom
    menuentry "Arch (on /dev/mmcblk0p1) custom" {
    set root='(hd0,5)'
    linux /boot/vmlinuz26-custom root=/dev/mmcblk0p1
    initrd /boot/kernel26-custom.img
    and run this
    update-grub
    hd0,5 is grub2 notation for my ubuntu partition (where /boot is of course)
    This is all I did to get it running that I can remember
    Arch's /etc/fstab is:
    # <file system> <dir> <type> <options> <dump> <pass>
    /dev/mmcblk0p1 / ext2 defaults,noatime 0 1
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid 0 0
    /dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    /dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    /dev/fd0 /media/fl auto user,noauto 0 0
    notice that there is no /boot mount point
    I can boot into Arch using the setup I described above with a totally empty /boot on the Arch partition
    Should I care that it is not mounted?
    I hope this helps other people trying to boot from SD cards

  • [solved] booting from usb

    Hello, I'm not sure if this post should go here but this board seemed the most "generic".
    I have an acer aspire one with 8GB of SDD and no swap partition. That's ok for webbrowsing and some of the tasks I would like a netbook for. When I want to compile large programs boot from an arch installation in an external 500GB HD wich I use to bloat and install programs I will probably use once. This worked for me untill I upgraded to HD to 2.6.27 which I needed in order to use it in the AAO (hardware support). Now the USB won't boot.
    I start the computer with the HD plugged and puch F12, choose to boot from the external drive and grub appear. Now no matter if I choose the first or second option it will start to boot but won't finish. It complains of the partition not existing. It suggest to add rootdelay=8 or greater to menu.lst, which I tried and doesn't work. When in ramfs$ I do
    cd dev
    echo *
    there is no sdb4 which is the root partition nor any sdb? . When I boot my local install it boots ok and I can se /dev/sdb4.
    Any idea?
    Last edited by ore (2009-03-23 17:00:51)

    when grub comes up hit "e"
    then edit initrd line to read like this
    initrd /boot/kernel26-fallback.img
    if that doesnt work try boot of install cd
    http://wiki.archlinux.org/index.php/Boo … recovering
    once in you id say you need to edit /etc/mkinitcpio.conf  make sure usb is in hooks. if you have sata or ide drive inside notebook make sure usb hook is after sata or ide hook otherwise usb gets sda & internal drive gets sdb
    http://wiki.archlinux.org/index.php/Con … mkinitcpio
    then run
    mkinitcpio -g /boot/kernel26.img
    reboot should do it

  • [SOLVED] Dual boot with ubuntu w/o installing GRUB? (YES)

    Hi all -
    This is my first shot at arch, tho I've installed a few other linux distros.
    So far I really appreciate the excellent documentation, especially compared to other linuxes!
    But I can't find a good answer to this question:
    I already have ubuntu installed and would like to dual-boot with arch.  (I also have Win7 but boot it from a separate disk selected via BIOS, and usually leave this disk disconnected anyway, so it's not an issue; grub doesn't know it exists).
    Q:  Before installing, can I make a new LOGICAL ext4 partition (say /dev/sda7),
    - then install arch on that **w/o installing grub** and **without messing with the MBR**,
    - then edit ubuntu's existing menu.lst to add arch to the boot options?
    Current $ fdisk -l
    /dev/sda1    ext4 primary/boot (/ for ubuntu)
    /dev/sda2    extended
    --/dev/sda6  linux-swap
    --/dev/sda5  NTFS (data - mp3s, etc)
    unallocated  480GB  --> Create new ext4 partition /dev/sda7,  (logical or primary? Prefer logical)
    Current menu.lst entry that I normally boot:
    title       Ubuntu 12.04 LTS, kernel 3.2.0-24-generic REGULAR
    uuid        UUIDforSDA1 (file has actual UUID number...)
    kernel      /boot/vmlinuz-3.2.0-24-generic root=UUID=UUIDforSDA1 ro
    initrd      /boot/initrd.img-3.2.0-24-generic
    and add something like this to menu.lst:
    title  Arch Linux
    uuid  UUIDforSDA7
    kernel /boot/vmlinuz-linux root=/dev/sda7/ARCH ro  (??? - from example in arch docs)
    initrd /boot/initramfs-linux.img
    or
    kernel /boot/vmlinuz-linux root=UUID=UUIDforSDA7 ro  (??? - like the ubuntu entry)
    I'd really like to NOT mess up booting ubuntu!  (Another option might be install arch to a separate disk with the ubuntu disk disconnected, then copy the whole install over via a USB adapter...I've done worse!)
    TIA for any help!
    Edit: so I guess there's three questions:
    1 - Can I install arch w/o installing grub & MBR messing-wth?
    2 - What's the correct syntax for menu.lst to access and boot arch?
    3 - Will this work?
    Last edited by Flemur (2012-05-25 15:24:18)

    Well, it worked and booted up first time - no grub install.
    The main hassle was merely creating a new ext4 partitions because "Partition Wizard" boot CD screwed up and I kept getting "Unable to update kernel until reboot" messages until I deleted and rebuilt all the partitions in the extended partition with puppy linux & gparted instead of Partition Wizard.
    In case others stumble upon this trhread, here's some info:
    The entry in the ubuntu (original) menu.lst was this:
       title           Arch Linux
       uuid          af7...etc...9f3c
       kernel        /boot/vmlinuz-linux root=UUID=af7...etc.f3c ro
       initrd          /boot/initramfs-linux.img
    I'm even posting this from arch/fluxbox/Firefox, although getting X set up with nvidia (PITA!) apparently required using a different pacman source:
    File "mirrorlist" now points to
        Server = http://mirror.us.leaseweb.net/archlinux/$repo/os/$arch
    which wasn't in the original file.
    Then
    $ pacman -Su --> "/etc/mtab exists" --> delete it and something else broke,
    so
    $ pacman -Su --force --> worked fine (against official advice)
    Also: needed to install nvidia-utils and xorg-xinit
    Thanks again!

  • [SOLVED] dual booting windows 7 with btrfs on grub-bios -- core.img

    I am trying to install arch in a dual boot configuration with an existing windows 7 partition. I have everything from the beginner's guide done but the bootloader. When I run grub-install it tells me that core.img is too big.
    Some googling tells me that this is relatively common with btrfs, and it seems the only work around is to switch to gpt mode and use a grub bios partition. But the info I've seen indicates that I need to use MBR mode to dual boot windows.
    Is it safe to do this with windows? Is there another workaround? Or will I have to settle for ext4?
    Last edited by jorenko (2013-06-09 03:53:24)

    Well there's your problem, your first partition starts at sector 63.  With recent versions of windows and fdisk (and every other partitioning tool I can think of off the top of my head) things now align themselves correctly.  Also because there is now GPT, the first partition typically starts later as the GPT partition table will typically sit between the MBR and the first partition. 
    On a MBR partitioned system, grub2 will actually use the first 446 bytes like normal, but will then also use the space that is empty where GPT would sit.  This is why when you have a GPT partitioned system, it will require you to create a 1-2MB grub boot partition, as it needs somewhere else to put its bloat.  GPT actually still uses the MBR section, but simply creates one large partition covering the whole disk.  This is so that tools that are not GPT aware will not think that they have a whole free disk to use as they please.
    For comparison, here is whe I get from fdisk:
    # fdisk -l /dev/sda
    sudo fdisk -l /dev/sda
    [sudo] password for curtisshima:
    WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
    Disk /dev/sda: 250.1 GB, 250059350016 bytes, 488397168 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 label type: gpt
    # Start End Size Type Name
    1 2048 2099199 1G EFI System EFI System
    2 2099200 252166798 119.2G Linux filesyste arch-btrfs-1
    3 252168192 488397134 112.7G Linux filesyste arch-btrfs-3
    Note that I do use GPT.  But that is not the point here. What I am trying to show is where my first partition starts.  This is also where fdisk will start partitions these days.  This is to ensure compatibility with 4k advanced format disks.
    If you are not dead set on Grub2, you could try using syslinux.  I really like it much better, though if you are booting more than one Linux, you need to either employ chainloading to various partition boot records, or have a shared /boot.  Having a windows partition doens't really matter, as you are simply chainloading to that funky reserved partition anyway. 
    The other option is to use grub-legacy, which can still be found in the AUR.  I actually liked the orginal Grub, as it provided a nice feature set, but was still configurable by hand and it actually fit into the MBR.

  • Windows (7) boots to blank screen via GRUB

    I have Arch installed as my main OS however now need to get a dual boot working with Windows 7.
    I have installed Windows 7 to a partition as below
    sda 8:0 0 931.5G 0 disk
    ├─sda1 8:1 0 734G 0 part / //Arch Linux Install
    ├─sda2 8:2 0 100M 0 part //Partition windows created?
    └─sda3 8:3 0 197.4G 0 part //main Windows partition
    My Grub.conf has the below section which has been generated by OS-prober
    menuentry 'Windows 7 (loader) (on /dev/sda2)' --class windows --class os $menuentry_id_option 'osprober-chain-EE8401AB840176FD' {
    insmod part_msdos
    insmod ntfs
    set root='hd0,msdos2'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2 --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2 EE8401AB840176FD
    else
    search --no-floppy --fs-uuid --set=root EE8401AB840176FD
    fi
    chainloader +1
    When I boot windows all I get is a blank screen, althought the windows splash sound does play, so im not sure if this is actually a boot issue or perhaps just an issue with windows so wanted to check here first.
    Thanks

    If you're hearing the splash noise, it boots. No issue with GRUB.

  • [SOLVED] Boot into different OS one time using grub

    I have a remote Arch Linux system, that I don't have physical access to too frequently. I wake this system up with WOL and then SSH in. By default, it boots into the first option on the grub menu, which is Arch. I don't want to change the default grub option, but I want to be able to change something while in Arch, reboot, have grub pick the second boot option, use the second OS (which could be any OS, not necessarily Arch), and then when I reboot again, grub would pick the default boot option.
    Is this possible?
    Last edited by gsingh93 (2013-12-12 21:08:45)

    https://wiki.debian.org/GrubReboot#Usage

  • [SOLVED] UEFI system booting from MBR partition table and GRUB legacy

    I'm trying to understand once and for all the process by which Arch can be booted from a system with UEFI firmware and an MBR partition table. Some of the information on the wiki seems conflictual / non-nonsensical at times. Apologies in advance if this has been answered time and time again, but I did search around and all I found was fixes to get Arch to boot rather than comprehensive explanations of the boot process.
    Now, the way I would imagine it works is that it's just completely identical to the way it would work with a BIOS firmware. The UEFI firmware detects an MBR partitioning scheme (or is configured to know it's an MBR partitioning scheme), activates some "legacy" mode and executes the MBR boot code, just like a BIOS firmware would.
    The wiki however, says different. From the Macbook article: "Do not install GRUB onto /dev/sda !!! Doing so is likely to lead to an unstable post-environment."?
    So what is there in the MBR boot sector? Nothing?
    How does the firmware know what to boot if there's no 0xEF BIOS boot partition and no Grub stage 1 in the MBR boot sector?
    Also, how does installing Grub stage 1 to a partition work? Does it have to be at the beginning of the partition? Wouldn't that overwrite some existing data?
    I'm especially puzzled since many guides to installing Vista on a macbook recommend simply formatting as MBR, and installing as normal, which I suppose entails having the Windows installation process write its boot code to the MBR, ie the equivalent of installing grub stage 1 to /dev/sda rather than to the /boot partition, as the Macbook article suggests.
    Any input is appreciated.
    P.S. I realize it's probably simpler, if I just want to dual boot Windows and Arch, to install Windows 7 in UEFI-GPT mode, let it create the EFI System Partition, and then install GRUB 2 to that partition, but I'm still curious about the UEFI-MBR boot process.
    Last edited by padavoine (2012-06-06 09:35:10)

    padavoine wrote:
    CSM in UEFI firmwares do the exact same job as normal BIOS firmware.
    So it's something specific to the Mac that it's able to boot from a partition's VBR while ignoring the MBR?
    The reason that warning is given is because grub-legacy modifies more than just the MBR boot code region.  It can overwrite some parts of GPT header.
    Not true, the instruction is given in the context of an MBR format, not in the context of a GPT format, so there's nothing to overwrite and Stage 1.5 should be safely embeddable in the post-MBR gap.
    In BIOS boot (normal case in non-UEFI firmwares or CSM in UEFI firmwares) does not read the partitition table (atleast it is supposed to be dumb in this regard), it simply launches whatever boot code exists in the 1st 440-byte of the MBR region.
    So again, you're saying it's specific to the Mac UEFI that it lets you choose a partition whose VBR to load, regardless of what's in the MBR?
    I haven't used Macs so I can't comment on Mac firmware behaviour. But normal BIOS firmwares (legacy and CSM) launch only the MBR boot code and not the partition boot code. We need some chainload capable boot manager in the MBR to launch the partition VBR.
    grub-legacy does not know anything about GPT. So when you install grub-legacy to /dev/sda, it install the MBR boot code (stage1) and stage 1.5 code to the (supposed) post MBR gap. Since there is no actual post MBR gap in GPT (which has been taken over by the header and partition table), grub-legacy does not check for GPT and it assumes the post MBR gap actually exists which is invalid in case of GPT. grub-legacy embeds the stage 1.5 code in GPT header and table region (which grub assumes to be unused post MBR gap) and thus corrupts it.
    0xEF is the MBR type code for UEFISYS partition. grub stage 1 (used in grub-legacy, not in grub2) is the 440-byte boot code stored in MBR for use in BIOS boot.
    That's precisely my point: with neither proper executable code in the MBR (since grub was installed to a partition, not to the MBR) nor a UEFI system partition, what does the firmware default to, and how does it know what partition to boot from?
    In that case it might fallback to UEFI Shell (if it exists)  or give an error similar to the case where BIOS does not find any bootable code in 440-byte MBR region.
    So even with bootcamp/CSM, the disk also needs to be MBR partitioned. So Macs use something called "Hybrid GPT/MBR" ( http://rodsbooks.com/gdisk/hybrid.html ) where the MBR table is synced to match the first 3 partitions in the GPT table.
    I know what Bootcamp does, and that's not what I was referring to. I was referring to standalone Vista installs. I wasn't puzzled at the fact that they were using MBR, I was puzzled at the fact that contrary to the recommendations for the standalone Arch install on the wiki (with MBR partitioning, not GPT), they didn't do anything to try and prevent Windows from writing to the MBR.
    You can't prevent Windows from overwriting the MBR region. You have to re-install the bootloader (grub2/syslinux etc.) after installing Windows. That is the reason why it is recommended to install Windows first and linux later.
    Thats not true. I actually find it is much easier to install Windows UEFI-GPT using USB rather than a DVD.
    I haven't done it since the only UEFI system I own has no DVD drive, but I was under the impression that it was simply a matter of choosing DVD UEFI boot in the firmware's boot menu.
    format the USB as FAT32 and extract the iso to it. That it.
    No, thats not it, precisely, it doesn't work out of the box with a standard Windows install USB, you need to fiddle around:
    2.3 Extract bootmgfw.efi from [WINDOWS_x86_64_ISO]/sources/install.wim => [INSTALL.WIM]/1/Windows/Boot/EFI/bootmgfw.efi (using 7-zip aka p7zip for both the files), or copy it from C:\Windows\Boot\EFI\bootmgfw.efi from a working Windows x86_64 installation.
    2.4 Copy the extracted bootmgfw.efi file to [MOUNTPOINT]/efi/microsoft/boot/bootmgfw.efi .
    Most of the Windows isos already have /EFI/BOOT/BOOTX64.EFI file, so no need to extract the bootmgfw.efi file.
    There is no difference between in BIOS booting in UEFI firmwares and BIOS booting with legacy firmware.
    There has to be a difference, at least in the Mac firmware (sorry, I keep switching), since legacy firmware, AFAIK, cannot chainload a bootloader in a partition's VBR without there being some sort of "stage1" code in the MBR.
    No idea about Mac EFI. Apple made a spagetti out of UEFI Spec. To actually understand how Mac firmwares work, read the blog posts by Matthew Garrett of Redhat, about his efforts in getting Fedora to boot in Macs.

Maybe you are looking for