[SOLVED] Arch Linux Guest Virtual Box OSE problem

So I am installing my Arch Linux as a Guest in my Ubuntu partition, through Virtual Box OSE (3.2.8). I followed the wiki ( https://wiki.archlinux.org/index.php/Ar … lBox_Guest ) but still have an issue:
sudo pacman -S kernel26-headers xorg gcc make
sudo mount /dev/cdrom /mnt/cdrom
sudo /mnt/cdrom/VBoxLinuxAdditions-x86.run
But It fails on Shared folders, and cannot recognize X:
:: Building the VirtualBox Guest Additions Kernel Modules [BUSY]
:: Building the main Guest Additions module [DONE]
:: Building the shared folder support module [FAIL]
(Look at /var/log/vboxadd-install.log to find otu what went wrong)
:: Warning: Unknown version of the X Window System installed. Not installing X Window System drivers.
:: Installing graphics libraries and desktop services components [Done]
/var/log/vboxadd-install.log states:
/tmp/vbox.0/vfsmod.c:406:9: error: unknown field 'clear_inode' specified in initalizer
/tmp/vbox.0/vfsmod.c:406:9 warning: initalization from incompatible pointer type.
Which is strange, because as far as I know, clear_inode is part of the linux headers.
Any idea why this is happening? Do I just need to update VirtualBox to a newer version?
Last edited by gralamin (2011-03-11 18:22:14)

Updating Virtualbox fixed the issue.

Similar Messages

  • Oracle 10g installation on linux using virtual box.

    Hi,
    Iam trying to install oracle 10g on enterprise linux using virtual box.I downloaded oracle 10g for linux and while running the installer,Iam getting this error
    Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/OraInstall2010-04-16_07-29-46AM/jre/1.4.2/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(Unknown Source)
    at java.lang.ClassLoader.loadLibrary(Unknown Source)
    at java.lang.Runtime.loadLibrary0(Unknown Source)
    at java.lang.System.loadLibrary(Unknown Source)
    at sun.security.action.LoadLibraryAction.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.awt.NativeLibLoader.loadLibraries(Unknown Source)
    at sun.awt.DebugHelper.<clinit>(Unknown Source)
    at java.awt.Component.<clinit>(Unknown Source)
    Please help me to solve this

    user9362721 wrote:
    Hi,
    Iam trying to install oracle 10g on enterprise linux using virtual box.I downloaded oracle 10g for linux and while running the installer,Iam getting this error
    Exception in thread "main" java.lang.UnsatisfiedLinkError: /tmp/OraInstall2010-04-16_07-29-46AM/jre/1.4.2/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directoryHi.
    This question was answered in this forum yesterday. And the day before. And the day before that. And ... (Or at least it feels like we get this every day, and sometimes several times a day.)
    Search for 'xhost'

  • Guide For Installing  Oracle Enterprise Linux in Virtual Box

    Hello,
    Any good tutorial available for installation of Oracle Enterprise Linux in Virtual Box?
    Regards

    Installing Oracle on Virtual box is similar to the one you install on regular Linux box.
    just make sure u have enough memory assigned for VMbox..
    create user, group, directories and change permissions
    change profile
    change all the kernal options listed in install guide and ur good

  • [SOLVED] Guest Arch in Virtual Box Internet Problems

    I have installed Arch a few times already in virtual machines on Virtual Box and each time it is unable to configure the internet connection properly.  Having gone through the beginner wiki-pages on starting with Arch, I have tried "ping -c 3 www.google.com" and get "ping: unknown host www.google.com".  However, IP addresses usually work with 0% packet loss.
    I then followed the "hwdetect" instruction and that yielded "-bash: hwdetect: command not found".  The command "modprobe pcnet32" does not yield an error and returns nothing.
    I have also tried other methods
    http://eligere.wordpress.com/2008/03/05 … i-problem/
    http://bbs.archlinux.org/viewtopic.php?id=55811.
    Thanks.
    Last edited by zeug (2009-05-08 23:03:56)

    Wikimig wrote:
    Hi,
    Pretty much the same here
    That is strange but adding "nameserver 192.168.0.1" to /etc/resolv.conf enables me to access the internet. 192.168.0.1 is of course the IP of the host computer's vitual card but what is strange is: I need to use dhcpcd from guest to be given an IP that isn't even in the same range as 192.168.0.1 (for instance 10.0.2.15)!!
    So to basically, host PC has that virtual ethernet card with static IP 192.168.0.1 and internet connection shared (don't know if this is compulsory though) and guest uses dhcp, is given 10.0.2.15 (don't ask me where it gets it from because I disabled it on VirtualBox). Then I just have to add "nameserver 192.168.0.1" to resolv.conf and I'm good... till dhcpcd rewrites the resolv.conf. How could we set dhcp to use a particular DNS?
    As you can see, I am not a DNS expert. Using static IPs for both would be great but it doesn't work
    Does it help?
    The 10.x.x.x.x address range is assigned because you are most probably using NAT networking on the Virtual Box configuration.
    Try with 'Bridged'.
    If all goes well you shouldn't need to fiddle with /etc/resolv.conf.
    Still, if you still need to change /etc/resolv.conf, put your changes in a file called /etc/resolv.conf.head which will survive
    the changes that sometimes DHCP does on /etc/resolv.conf.
    Mektub

  • [SOLVED] 3d Acceleration on Arch Linux guest

    I've just installed the latest FTP Arch Linux (2009.02) as a Guest running in Virtual Box 3.0.2 in my Windows 7 host, and I cannot get Xorg working at all.
    - 3D Acceleration is enabled for the VM, and 128MB of video memory allocated
    - Guest Additions were installed successfully, added rc.vboxadd to daemons, and everything loads ok on startup.
    Output of 'dmesg | grep vbox':
    vboxadd: Successfully loaded version 3.0.2 (interface 0x0010004)
    vboxvfs: Successfully loaded version 3.0.2 (interface 0x0010004)
    [drm] Initialized vboxvideo 1.0.0 20090303 for 0000:00:02.0 on minor 0
    Here is my .xinitrc:
    /usr/bin/VBoxClient-all
    I've symlinked vboxvideo_dri.so since the installer didn't do it.
    Output of 'ls -l /usr/lib/xorg/modules/dri/vboxvideo_dri.so':
    lrwxrwxrwx 1 root root 19 2009-07-31 22:42 /usr/lib/xorg/modules/dri/vboxvideo_dri.so -> /usr/lib/VBoxOGL.so
    And error when I run 'startx':
    (EE) AIGLX error: dlopen of /usr/lib/xorg/modules/dri/vboxvideo_dri.so failed (libXcomposite.so.1: cannot open shared object file: No such file or directory)
    (EE) AIGLX: reverting to software rendering
    waiting for X server to shut down
    And then it shuts down, without even trying to load swrast_dri.so. But the weirdest part is, that symlink exists, but X is saying it doesn't! I've restarted the VM and still get the same error.
    Here is my xorg.conf (created by installing GA), and I do have HAL up and running, loaded before the rc.vboxadd daemon:
    # Default xorg.conf for Xorg 1.5+ without PCI_TXT_IDS_PATH enabled.
    # This file was created by VirtualBox Additions installer as it
    # was unable to find any existing configuration file for X.
    Section "Device"
    Identifier "VirtualBox Video Card"
    Driver "vboxvideo"
    EndSection
    So... what next? 
    Last edited by timmahcheese (2009-08-03 15:20:55)

    Silly me, I forgot the libxcomposite package. I guess I should read the errors closer.
    Anyway, I'm still getting an error (signal 11) being caused by VBoxClient-all. Here is my Xorg.0.log:
    X.Org X Server 1.6.2
    Release Date: 2009-7-7
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 2.6.30-ARCH i686
    Current Operating System: Linux obi-wan 2.6.30-ARCH #1 SMP PREEMPT Mon Jul 20 11:20:32 UTC 2009 i686
    Build Date: 18 July 2009 08:27:13PM
    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: Sun Aug 2 23:20:02 2009
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) No Layout section. Using the first Screen section.
    (==) No screen section available. Using defaults.
    (**) |-->Screen "Default Screen Section" (0)
    (**) | |-->Monitor "<default monitor>"
    (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    (**) | |-->Device "VirtualBox Video Card"
    (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (WW) The directory "/usr/share/fonts/Type1" does not exist.
    Entry deleted from font path.
    (==) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    built-ins
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (II) Cannot locate a core pointer device.
    (II) Cannot locate a core keyboard device.
    (II) The server relies on HAL to provide the list of input devices.
    If no devices become available, reconfigure HAL or disable AllowEmptyInput.
    (II) Loader magic: 0x7a40
    (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:2:0) 80ee:beef:0000:0000 InnoTek Systemberatung GmbH VirtualBox Graphics Adapter rev 0, Mem @ 0xe0000000/134217728
    (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 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.6.2, 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: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.6.2, 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: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="X.Org Foundation"
    compiled for 1.6.2, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (==) AIGLX enabled
    (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.2, 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: "dri"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri.so
    (II) Module dri: vendor="X.Org Foundation"
    compiled for 1.6.2, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension XFree86-DRI
    (II) LoadModule: "dri2"
    (II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
    (II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.6.2, module version = 1.1.0
    ABI class: X.Org Server Extension, version 2.0
    (II) Loading extension DRI2
    (II) LoadModule: "vboxvideo"
    (II) Loading /usr/lib/xorg/modules/drivers//vboxvideo_drv.so
    (II) Module vboxvideo: vendor="Sun Microsystems, Inc."
    compiled for 1.5.99.901, module version = 1.0.1
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 5.0
    (II) VBoxVideo: guest driver for VirtualBox: vbox
    (II) Primary Device is: PCI 00@00:02:0
    (II) resource ranges after xf86ClaimFixedResources() call:
    [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 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    (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] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) VBoxVideo(0): VirtualBox guest additions video driver version 3.0.2
    (II) Loading sub module "vbe"
    (II) LoadModule: "vbe"
    (II) Loading /usr/lib/xorg/modules//libvbe.so
    (II) Module vbe: vendor="X.Org Foundation"
    compiled for 1.6.2, module version = 1.1.0
    ABI class: X.Org Video Driver, version 5.0
    (II) Loading sub module "int10"
    (II) LoadModule: "int10"
    (II) Loading /usr/lib/xorg/modules//libint10.so
    (II) Module int10: vendor="X.Org Foundation"
    compiled for 1.6.2, module version = 1.0.0
    ABI class: X.Org Video Driver, version 5.0
    (II) VBoxVideo(0): initializing int10
    (II) VBoxVideo(0): Primary V_BIOS segment is: 0xc000
    (II) VBoxVideo(0): VESA BIOS detected
    (II) VBoxVideo(0): VESA VBE Version 2.0
    (II) VBoxVideo(0): VESA VBE Total Mem: 131072 kB
    (II) VBoxVideo(0): VESA VBE OEM: VirtualBox VBE BIOS http://www.virtualbox.org/
    (II) VBoxVideo(0): VESA VBE OEM Software Rev: 0.2
    (II) VBoxVideo(0): VESA VBE OEM Vendor: Sun Microsystems, Inc.
    (II) VBoxVideo(0): VESA VBE OEM Product: VirtualBox VBE Adapter
    (II) VBoxVideo(0): VESA VBE OEM Product Rev: Sun VirtualBox Version 3.0.2
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Module "ramdac" already built-in
    (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.2, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (II) Loading sub module "shadowfb"
    (II) LoadModule: "shadowfb"
    (II) Loading /usr/lib/xorg/modules//libshadowfb.so
    (II) Module shadowfb: vendor="X.Org Foundation"
    compiled for 1.6.2, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.4
    (II) VBoxVideo(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    (==) VBoxVideo(0): Depth 24, (--) framebuffer bpp 32
    (II) VBoxVideo(0): Output VBOX1 has no monitor section
    (II) VBoxVideo(0): The maximum supported resolution is currently 32000x32000
    (II) VBoxVideo(0): Output VBOX1 has no monitor section
    (II) VBoxVideo(0): Output VBOX1 connected
    (II) VBoxVideo(0): Using exact sizes for initial modes
    (II) VBoxVideo(0): Output VBOX1 using initial mode 1024x768
    (==) VBoxVideo(0): RGB weight 888
    (==) VBoxVideo(0): Default visual is TrueColor
    (==) VBoxVideo(0): Using gamma correction (1.0, 1.0, 1.0)
    (==) VBoxVideo(0): DPI set to (96, 96)
    (II) Loading sub module "dri"
    (II) LoadModule: "dri"
    (II) Reloading /usr/lib/xorg/modules/extensions//libdri.so
    (--) 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] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
    [9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (==) VBoxVideo(0): Default visual is TrueColor
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 10, (OK)
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 10, (OK)
    drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 10, (OK)
    drmOpenByBusid: drmOpenMinor returns 10
    drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    (II) [drm] DRM interface version 1.3
    (II) [drm] DRM open master succeeded.
    (II) VBoxVideo(0): [drm] Using the DRM lock SAREA also for drawables.
    (II) VBoxVideo(0): [drm] framebuffer handle = 0xe0000000
    (II) VBoxVideo(0): [drm] added 1 reserved context for kernel
    (II) VBoxVideo(0): X context handle = 0x1
    (II) VBoxVideo(0): [drm] installed DRM signal handler
    (II) VBoxVideo(0): visual configurations initialized
    (==) VBoxVideo(0): Backing store disabled
    (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    (II) VBoxVideo(0): DPMS enabled
    (II) VBoxVideo(0): The VBox video extensions are now enabled.
    (II) VBoxVideo(0): [DRI] installation complete
    (--) RandR disabled
    (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) AIGLX: Screen 0 is not DRI2 capable
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 11, (OK)
    drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 11, (OK)
    drmOpenByBusid: drmOpenMinor returns 11
    drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
    (II) The file referenced, is *NOT* loaded
    (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
    (EE) AIGLX error: vboxvideo does not export required DRI extension
    (EE) AIGLX: reverting to software rendering
    (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/swrast_dri.so
    (II) GLX: Initialized DRISWRAST GL provider for screen 0
    (II) VBoxVideo(0): Setting screen physical size to 270 x 203
    (II) config/hal: Adding input device Macintosh mouse button emulation
    (II) LoadModule: "evdev"
    (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
    (II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.6.1, module version = 2.2.2
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
    (**) Macintosh mouse button emulation: always reports core events
    (**) Macintosh mouse button emulation: Device: "/dev/input/event0"
    (II) Macintosh mouse button emulation: Found 3 mouse buttons
    (II) Macintosh mouse button emulation: Found x and y relative axes
    (II) Macintosh mouse button emulation: Configuring as mouse
    (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
    (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
    (**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
    (**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
    (**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
    (**) Macintosh mouse button emulation: (accel) set acceleration profile 0
    (II) config/hal: Adding input device ImExPS/2 Generic Explorer Mouse
    (**) ImExPS/2 Generic Explorer Mouse: always reports core events
    (**) ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event5"
    (II) ImExPS/2 Generic Explorer Mouse: Found 5 mouse buttons
    (II) ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
    (II) ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
    (II) ImExPS/2 Generic Explorer Mouse: Configuring as mouse
    (**) ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
    (**) ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE)
    (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
    (**) ImExPS/2 Generic Explorer Mouse: (accel) filter chain progression: 2.00
    (**) ImExPS/2 Generic Explorer Mouse: (accel) filter stage 0: 20.00 ms
    (**) ImExPS/2 Generic Explorer Mouse: (accel) set acceleration profile 0
    (II) config/hal: Adding input device AT Translated Set 2 keyboard
    (**) AT Translated Set 2 keyboard: always reports core events
    (**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
    (II) AT Translated Set 2 keyboard: Found keys
    (II) AT Translated Set 2 keyboard: Configuring as keyboard
    (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
    (**) Option "xkb_rules" "evdev"
    (**) Option "xkb_model" "evdev"
    (**) Option "xkb_layout" "us"
    (II) config/hal: Adding input device VirtualBox Guest Service
    (II) LoadModule: "vboxmouse"
    (II) Loading /usr/lib/xorg/modules/input//vboxmouse_drv.so
    (II) Module vboxmouse: vendor="Sun Microsystems Inc."
    compiled for 0.0.0, module version = 1.0.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 4.0
    (**) VirtualBox Guest Service: always reports core events
    (**) VirtualBox Guest Service: Device: "/dev/vboxadd"
    (II) XINPUT: Adding extended input device "VirtualBox Guest Service" (type: MOUSE)
    (**) VirtualBox Guest Service: (accel) keeping acceleration scheme 1
    (**) VirtualBox Guest Service: (accel) filter chain progression: 2.00
    (**) VirtualBox Guest Service: (accel) filter stage 0: 20.00 ms
    (**) VirtualBox Guest Service: (accel) set acceleration profile 0
    (**) VirtualBox Guest Service: Mouse Integration associated with screen 0
    (II) VirtualBox Guest Service: On.
    Backtrace:
    0: /usr/bin/X(xorg_backtrace+0x3b) [0x813154b]
    1: /usr/bin/X(xf86SigHandler+0x9e) [0x80cacee]
    2: [0xb8008400]
    3: /usr/bin/X(Dispatch+0x80) [0x808c350]
    4: /usr/bin/X(main+0x395) [0x8072005]
    5: /lib/libc.so.6(__libc_start_main+0xe6) [0xb7be2a36]
    6: /usr/bin/X [0x80714b1]
    Fatal server error:
    Caught signal 11. Server aborting
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    (II) Macintosh mouse button emulation: Close
    (II) UnloadModule: "evdev"
    (II) ImExPS/2 Generic Explorer Mouse: Close
    (II) UnloadModule: "evdev"
    (II) AT Translated Set 2 keyboard: Close
    (II) UnloadModule: "evdev"
    (II) VirtualBox Guest Service: Off.
    (II) VirtualBox Guest Service: Close
    (II) UnloadModule: "vboxmouse"
    Last edited by timmahcheese (2009-08-03 04:07:48)

  • [SOLVED]Arch Linux running inside GNOME Boxes.

    Hello,
    I wanted to create a vm using GNOME Boxes to run another Arch Linux installation (to test things and avoid to break my main system).
    I did a normal install, then installed gnome-shell and gdm from testing repos. I enabled gdm and NetworkManager and after reboot my box.
    The box don't boot. The main display only see early fsck lines (about /), I can see in the thubnail more lines but can't read messages.
    What is wrong here ?
    Regards,
    Fabien
    Last edited by fbourigault (2014-10-07 11:22:36)

    I can't read it it only show in the thumbnail. I posted here to known if I missed some package installation or if someone already had the problem and solve it !.
    EDIT:
    I installed a new box, using gnome from stable repositories. I installed the same packages but didn't enable anything. I'm starting services by hand to allow me do configuration in the box
    You can find the gdm log here : http://pastebin.com/R5ek3Xwy (full version with multiple failing runs :http://pastebin.com/fCsPxAvb)
    EDIT 2 :
    Problem solved by installing xf86-video-qxl from AUR ! This package should really be in official repos.
    Last edited by fbourigault (2014-10-07 08:41:32)

  • [SOLVED] Arch Linux Duke (2007) Fails to Boot

    Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
    I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch.  It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
    After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
    A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
    RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
    RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
    If you have read this far, you are a trooper.  Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
    :: Loading udev events                [Pass]
    :: Mount root Read-only
    :: Checking file systems
    This is where it stops.
    The next thing I see is:
    /dev/sda6
    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
        E2fsck –b 8193 <device>
    I then get a sort of character based splash screen that says
    **********FILE SYSTEM CHECK FAILED ****************************
    *   Please repair manually and reboot. Note that the root file system
    *   is currently mounted read-only. To remount it read-write, type:
    *   mount –n –o remount,rw /.  When you exit the maintenance
    *   shell, the system will reboot automatically
    Give root password for maintenance
    At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
    /dev/sda6 on / type ext3 (rw)
    This is exactly the root partition that the start up complains about. It is clearly there.  I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
    At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
    Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
    # mknod “/dev/root2” b 3 6   
    (“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
    Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
    All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
    I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
    By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
    image = /boot/vmlinuz26
       root = /dev/sda6
       label = ArchLinux-Duke
       initrd = /boot/kernel26.img
       read-only
    I am stumped. Thanks in advance for any and all pointers you may be able to offer.
    Last edited by mac57 (2014-06-02 17:42:21)

    Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
    At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
    So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
    Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next.  This is my guess anyway.
    I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the  Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
    It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
    Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

  • [SOLVED] Arch Linux on encrypted luks partition on USB key

    Hi
    I've installed Arch Linux on a USB key following this Wiki page: https://wiki.archlinux.org/index.php/In … _a_USB_key
    I also used dm-crypt as described in this Wiki page: https://wiki.archlinux.de/title/Festpla … iante_1.29
    I installed Arch Linux on the USB key using VirtualBox.
    To do that, I created a "rawvmdk":
    vboxmanage internalcommands createrawvmdk -filename ./usb.vmdk -rawdisk /dev/sdd
    Everything works fine when I'm trying to start the system within VirtualBox.
    Syslinux loads Arch using the following kernel command:
    APPEND cryptdevice=UUID=6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf:main root=/dev/mapper/main-root rw
    /etc/mkinitcpio.conf holds the following "HOOKS" configuration:
    HOOKS="base udev autodetect modconf block keyboard keymap encrypt lvm2 filesystems fsch resume"
    As already mentioned the configuration works within VirtualBox. When I'm trying to boot from the USB key on my real computer, I'm getting an error. Syslinux works fine and loads Linux, but Linux is complaining. Here's the log:
    :: running hoock [encrypt]
    Waiting 10 seconds for device /dev/disk/by-uuid/6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf ...
    ERROR: device '/dev/mapper/main-root' not found. Skipping fschk.
    ERROR: Unable to find root device '/dev/mapper/main-root'.
    You are being dropped to a recovery shell
    I'm not getting prompted for the passphrase since the cryptdevice can not be found. But why? It can be found when I'm booting within VirtualBox. What might be different? I successfully installed other Linux distributions (but without encryption and using GRUB as bootloader) previously within VirtualBox and was able to boot from the USB key on a real machine afterwards.
    Some additional information that might help:
    Here's the "lsblk -f output" for the stick:
    sdd
    ├─sdd1 ext4 usbboot bb45e84e-842e-4209-8c44-1af3c7933389
    └─sdd2 crypto_L 6aa73872-3755-4bdf-bee3-d1cd7a3fe0bf
    When I'm running "lsblk" or "blkid" from the recovery shell after the failure, I'm getting no output. "ls /dev/sd*" returns nothing as well. The directory /dev/disk does not even exists in the recovery shell. (I'm not sure if this is normal or not.)
    Thanks for helping.
    Last edited by The Infinity (2014-08-14 20:26:06)

    I still haven't solved the problem:
    When starting the system on a machine with NVIDIA GTX 560Ti graphics card:
    - X doesn't start using startx or xinit and there are no log entries in /var/log/Xorg.*.log (as I haven't tried to start X).
    - I'm getting the message "Waiting for X server to begin accepting connections .. .. .. ..".
    - I already tried to uninstall xf86-video-nouveau and nouveau-dri with no effect.
    - Additionally: The "default terminals tty1/2/3/..." (which I'm using to start X) from have a poor resolution (I think 640x480 pixel).
    When starting the system on a virtual machine or a machine with an ATI Radeon (mobile) graphics card:
    - X starts and runs without any trouble the XFCE desktop environment.
    - Additionally: The default terminals have a proper resolution (I think the maximal resolution of the display).

  • [solved] Arch linux access point with multiple interfaces for the NAT

    Hi, I have a router running Arch linux. It is connected via LAN (let's call it eth0) to the internet. It has a second LAN interface, eth1, and a wireless interface in master mode, wlan0.
    Now, Everything works perfectly except providing network connectivity on eth1 and wlan0 simultaneously. I followed the guide in the "Internet share" wiki article and use dnsmasq/hostapd for the AP. It appears as if all traffic from the router is sent to the wlan0 interface, even if it came in through eth1 (for example, dhcp requests). I cannot really find information how to solve this. The words "bonding" and "iptables" are floating around, but there is not really an easy to understand tutorial for this.
    What do I need to do to use both the eth1 and wlan0 interface (for different clients!) on my router?
    Best regards, and thank you in advance
    Jan Oliver
    /e: This seems to be my problem: http://www.novell.com/support/kb/doc.php?id=7000318 How do I solve this using the usual iptables? (The way described in the article doesn't work: "RTNETLINK answers: No such process" errors.)
    Last edited by janoliver (2013-09-25 22:24:53)

    Or you could bridge eth1 and wlan0, and make dnsmasq bind/listen on that bridge...

  • [SOLVED]Arch Linux / UEFI / BTRFS using Grub2 & Windows 8 in a 2nd HDD

    PROBLEM:
    ====================================================================================
    Dear fellas
    I just purchased an new HP TouchSmart 17.3" laptop that comes with Windows 8.1 pro (1 tb HDD + small SSD for cache only ) and still have space for one more HDD or SSD.
    I Google a lot and read a lot but many questions emerged since seems that no one has the same scenario (maybe I pick the wrong choices) like me.
    The problem is.. I didn't wish to re-install Windows 8.1 since it came with from factory.. so I purchased a 750 gb hdd and put it into the free slot to install Arch Linux in a different HDD.
    As I am not familiar with UEFI what I did was to reorder the hdds. I just put the Windows HDD as second disk and the new disk (For Arch Linux) as primary and changed into Bios from UEFI to compatibility mode and installed Arch Linux into the primary one.
    I reaaaally need help to add to grub the correct "path" to Windows 8.1 disk that came with UEFI..
    Anyone could please help me?
    Thanks in advance!
    ====================================================================================
    SOLUTION:
    A huge thanks to @TheSaint and other users for their help and assistance!
    More sources:
    http://www.kossboss.com/linux---arch-in … -grub-boot
    https://www.youtube.com/watch?v=METZCp_JCec#t=146
    https://bbs.archlinux.org/viewtopic.php … 1#p1390741
    Step by Step Summary:
    Use gdisk to create partitions on /dev/sda:
        - 512MB - EF02 type partition (for EFI boot)
        - 690GB - Linux partition for the BTRFS.
    - Create an EF00 (ESP) with 512mb
    - Create a Linux System partition with the rest of space
    Make the FAT 32 system for EFI boot:
    # mkfs.vfat -F32 /dev/sda1
    Make the BTRFS partition. If it complains about existing filesystems just add a "-f":
    # mkfs.btrfs -L arch -f /dev/sda2
    We will make out a root subvolume for sda1, this will be a folder called root located at the root of sda2. The way we will design this is that When the system boots we will not see /root, we will be inside root. Inside root you will have all of your etc,sys,proc,whatever folders etc.
    # mount /dev/sda2 /mnt
    # cd /mnt
    # btrfs subvolume create /mnt/root
    This should show you your root
    # btrfs subvolume list -a /mnt
    Something like this: ID 256 gen 5 top level 5 path root
    # cd /
    # umount /dev/sda2
    Now we will mount sda2 root subvolume as /mnt and we will dump the arch system into there with pacman. We will also enable compress to utilize btrfs compress feature.
    # mount -o defaults,compress=lzo,subvol=root /dev/sda2 /mnt
    NOTE: the command "mount" will not show which subvolume is mounted, to see how subvolumes are mounted you need to look inside proc (cat /proc/self/mountinfo):
    # cat /proc/self/mountinfo | egrep sda2
    The line for the mount of sda2 looks like this:
    43 21 0:34 /root /mnt rw,relatime shared:30 - btrfs /dev/sda2 rw,compress=zlib,ssd,space_cache
    We can see that the subvolume /root is mounted to /mnt from the device /dev/sda3
    Notice how with regular mount command its missing:
    # mount | egrep sda2
    /dev/sda3 on /mnt type btrfs (rw,relatime,compress=zlib,ssd,space_cache)
    Pacman will dump stuff into a boot folder, so we better mount our sda1 EFI boot partition to it. Or else all of the boot stuff will go to sda3 instead of sda1:
    # cd /
    # pacstrap -i /mnt base base-devel
    Let us create the directory and mount the EFI partition
    # cd /mnt
    # mkdir -p /mnt/boot/efi
    # mount /dev/sda1 /mnt/boot/efi
    Let us generate the FSTAB:
    # genfstab -p /mnt >> /mnt/etc/fstab
    Let us chroot into the arch installation:
    # arch-chroot /mnt /bin/bash
    Change password:
    # passwd
    Then pick the right one like this and associate it with a link to /etc/localtime
    # ln -s /usr/share/zoneinfo/US/Pacific /etc/localtime
    Let us generate the initial RAM disk
    # mkinitcpio -p linux
    Let us setup the bootloader (GRUB)
    # pacman -Syu grub efibootmgr
    Let us generate the grub configuration
    # grub-mkconfig -o /boot/grub/grub.cfg
    Let us install grub into the HDD
    # grub-install /dev/sda
    # umount -R /mnt
    # umount /mnt
    # reboot
    From this step you can go straight and forward with the https://wiki.archlinux.org/index.php/Beginners%27_guide
    Last edited by erickwill (2014-11-21 20:41:06)

    TheSaint wrote:As UEFI BIOS is a boot loader itself. You should make on each HDD an ESP.
    When you want to start win8 you go to BIOS and chose its entry, so will do for Arch the same.
    For this way I suggest you write to boot the kernel directly from the BIOS. It just take some reading on this topic
    Other option you set on you second ESP the boot loader of your liking and it will try to find win8 partition.
    Thanks for your reply.
    For the second option, may I use the compatibility mode and install the booloader into the first partition along with Arch?
    Or in case the first option is still the better option, could you pleaaaase give me some directions from the scratch? Do you have Google Hangout?
    Thanks in advance.
    Last edited by erickwill (2014-11-18 19:54:26)

  • [SOLVED] Arch Linux on Macbook - Can't fix Screen Resolution

    I just installed Arch Linux as a dual-boot on my Macbook.  I really like it so far.  However, I came across a problem that is really bothering me.  It may seem simple, but no matter what I try, I only get "1024x768" and "800x600" resolution options.  What I need is "1280x800."  Here is my xorg.conf file right now:
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "glx"
    Load "dri2"
    Load "extmod"
    Load "dbe"
    Load "dri"
    Load "record"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ### [arg]: arg optional
    #Option "ShadowFB" # [<bool>]
    #Option "DefaultRefresh" # [<bool>]
    #Option "ModeSetClearScreen" # [<bool>]
    Identifier "Card0"
    Driver "vesa"
    VendorName "Intel Corporation"
    BoardName "Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
    BusID "PCI:0:2:0"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Modes "1280x800"
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Modes "1280x800"
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Modes "1280x800"
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Modes "1280x800"
    Depth 15
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Modes "1280x800"
    Depth 16
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Modes "1280x800"
    Depth 24
    EndSubSection
    EndSection
    I just followed the instruction on the Arch Linux - Macbook Wiki page, and everything worked perfectly, except the resolution question.  The only thing I added to the file is the 'Modes    "1280x800"' lines.  This is exactly what I've always done with linux, and it has always worked.  So I'm perplexed, and I can't find any solutions that actually work by googling it.  Has anyone else come across this problem, and even more important, does anyone know what is wrong?
    Thanks.
    Last edited by meolson (2009-09-23 04:44:23)

    Ok.  I figured it out.  I found this forum:
    http://bbs.archlinux.org/viewtopic.php?id=56899
    I found it before, but I had done everything, or so I thought.  At the end, he mentions two things that are important to fix the resolution.  I've repeated them here, and adapted them to what I had before:
    pacman -S xf86-video-intel
    edit /etc/X11/xorg.conf, and change video card driver from 'vesa' to 'intel'
    I thought I had installed xf86-video-intel already, but apparently I hadn't.  So, I followed those two steps, and now, it looks so much better!  Thanks to anyone who tried to looked for a solution.

  • [SOLVED] Arch Linux on Macbook Pro 4.1

    Hey There,
    I'm a 2 years old Arch Linux guy and due to the problems I've had with my HP Pavilion PC, I've bought a Macbook Pro 3-4 months ago.. Because that it's a pain in the ass to install, upgrade and remove software on Mac OS X, especially development software such as Python and its bindings, I'm thinking of migrating to Arch Linux. Any way, I've just installed Arch Linux and dual boot..
    I've installed X, GNOME, NVIDIA so far and when I try to open GNOME (via startx), it opens up a 800x600 or 1024x768 resolution X and shows GNOME.. But I can't move the mouse and no matter what I type no menus show up.. So I'm stuck after GNOME starts.. I can't drop back into the terminal so I hold the power button to shutdown and start the machine...
    It seems that this is the only problem I have for now.. Anyone had this problem before? I've tried it with and without xorg.conf and the result is the same..
    Last edited by T-u-N-i-X (2008-11-30 16:17:11)

    CTRL + ALT + Backspace
    That should close startx.  Also, the user manual has a couple of alternative methods of setting up your xorg.conf file.  I'd try those next.
    http://wiki.archlinux.org/index.php/Beg … phic_Cards
    Last edited by sharpie (2008-11-30 14:05:39)

  • [SOLVED] Arch Linux is zombie infested !!!

    Sigh !
    I don't know what happened but a few minute before when I rebooted my Arch Linux desktop, it started acting weird.
    First thing I do is to start my torrent client Deluge, look there was no icon in the tray for it but it was shown in System-monitor.
    Then I started Firefox, a few minute later the whole thing logged off. I renter my password and then again it logged of within one minute.
    So I rebooted to see if that changes this time, but this time I could see was that firefox was shown as ZOMBIE process and then when I tried to take the screenshot the system hanged
    Some thing I did today was
    Installed Yaourt
    Then installed nautilus-dropbox plugin
    Dropboxd service runs in background, so is there something fishy about the dropbox service. I tried to kill it but it again restarts.
    Please help me from zombie infestation, I am writing this from Ubuntu
    Last edited by visio159 (2008-09-14 08:41:47)

    No one replied !!! huh
    Well good news is that my RAM module needed a dust cleanup. Probably due to corrupt memory it was behaving bad.
    I am impressed that it (linux) logged me off when it detected that there were memory violation and corruptions to prevent any data damage ! Now can anyone explain this to me ? Is it really a feature or was just random occurring ?
    Case solved, learned a lesson too.
    Last edited by visio159 (2008-09-13 05:44:10)

  • [SOLVED] Arch Linux on notebook HP 6735s

    Hi all, i'm new of arch linux, i'm coming from ubuntu.
    I would install this distro over my notebook HP 6735s but i can't boot distro from cd and from usb. I have tried both core and netinstall version, but the pc is ever locked at bios screen.
    I have done checksum of the downloaded distro and writing control of the burning image, and all is ok, i have also tried to use these 2 bootable supports from other 2 desktop pc and i haven't any problem... only with arch linux + hp 6735s. Other distro like ubuntu, knoppix, mandriva can be booting from external supports without problems.
    Do you have any suggestion?
    Thanks
    Last edited by Kenny94 (2010-12-27 16:44:30)

    I had an HP 6xxx laptop that was very picky about USB booting.  The HP seemed to boot only with smaller capacity sticks (2GB or less).  Not sure if this was some sort of power deficiency on the USB ports?  Once booted it would read larger ones fine but it wouldn't boot from them.  Anyway if you're using a larger one, maybe try using a 1 or 2GB stick instead.
    A CD should work as long as it's the first boot device but if it's working in another machine and not that one, it would point to a problem with the drive.
    Last edited by brianhanna (2010-12-27 13:31:45)

  • Installation of linux on Virtual Box

    Hi everyone. Thanks in advance for the help.
    I have installed Virtual Box on my computer, no I need to install Linux and then on Linux I need oracle. I am doping this all because I want to become a DBA and unfortunately I do not have a lot of money to pay to the Training Centers. I recently downloaded and installed Linux Mint v14. Later my friend said this version of Linux does not support Oracle. Can any-you of you please let me know, what I need to download from http://www.centos.org/?

    What does this have to do with java?
    And why do you think you need linux to learn Oracle?

Maybe you are looking for