[SOLVED] YubiKey logon in Arch Linux

I have a YubiKey NEO which I use for secure one time passwords, and I'm looking for a way to use this to replace (or maybe, in addition to) my Arch login password. Using Google, I see a few methods that use it for logging in with SSH, but I'm looking for something would work with my everyday logon.
Last edited by adeligen (2012-10-31 20:12:05)

I use this...
http://www.securixlive.com/yubipam/index.php
I don't know why the heck this package has not gotten more love? This will alow you to authenticate OTP on your computer. Then you just edit your /etc/pam.d files and you can use OTP to log into your laptop, sudo, su, kscreensaver, sshd .... anything that supports PAM auth.
That yubico-pam sucks, and dose not let you do what you want i.e. PAM auth with OTP localy
Last edited by hunterthomson (2012-10-31 22:27:21)

Similar Messages

  • [SOLVED]System Hang in Arch Linux

    I have tried distributions like ubuntu and fedora in hope for finding a stable system . So I move on to Arch Linux
    But this problem also exist on Arch. While using my Arch Linux (including ubuntu and fedora) my system hangs with a black screen with something written on the whole screen which cannot be pasted here as my system hangs and I have to push power button to restart.
    So I check my errors.log file and found these errors
    Jul  8 22:59:24 localhost kernel: [    1.680013] ata3: softreset failed (device not ready)
    Jul  8 22:59:24 localhost kernel: [    7.298612] SP5100 TCO timer: mmio address 0xfec000f0 already in use
    Jul  8 22:59:31 localhost kdm_greet[792]: Cannot load /usr/share/apps/kdm/faces/.default.face: No such file or directory
    I have a HCL K21 pdc notebook
    Note: In Ubuntu my notebook start with ata1: softreset failed error at boot time
    Most often this error occur while watching videos or listening music with VLC
    Last edited by Manuj19 (2011-07-09 10:13:24)

    ewaller wrote:It might be better to just post the output of lspci -nn  It will tell us a great deal more about the hardware related to the PCI bus, including specific chip set identifiers.
    Thanks for suggestion
    Here is output of lspci -nn
    00:00.0 Host bridge [0600]: ATI Technologies Inc Device [1002:5a31] (rev 01)
    00:01.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a3f]
    00:04.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a36]
    00:05.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a37]
    00:06.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a38]
    00:07.0 PCI bridge [0604]: ATI Technologies Inc RS480 PCI Bridge [1002:5a39]
    00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA [1002:4380]
    00:13.0 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI0) [1002:4387]
    00:13.1 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI1) [1002:4388]
    00:13.2 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI2) [1002:4389]
    00:13.3 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI3) [1002:438a]
    00:13.4 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI4) [1002:438b]
    00:13.5 USB Controller [0c03]: ATI Technologies Inc SB600 USB Controller (EHCI) [1002:4386]
    00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 13)
    00:14.1 IDE interface [0101]: ATI Technologies Inc SB600 IDE [1002:438c]
    00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383]
    00:14.3 ISA bridge [0601]: ATI Technologies Inc SB600 PCI to LPC Bridge [1002:438d]
    00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384]
    01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RC410 [Radeon Xpress 200M] [1002:5a62]
    02:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5001 Wireless Network Adapter [168c:001c] (rev 01)
    08:01.0 CardBus bridge [0607]: Ricoh Co Ltd RL5c476 II [1180:0476] (rev b3)
    08:01.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C552 IEEE 1394 Controller [1180:0552] (rev 08)
    08:01.2 SD Host controller [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter [1180:0822] (rev 17)
    08:01.3 System peripheral [0880]: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter [1180:0592] (rev 08)
    08:07.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
    Last edited by Manuj19 (2011-07-09 07:20:08)

  • [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] Mount Points In Arch Linux

    When I performed my initial testing install of Arch Linux today, and I was setting up mount points after I finished partitioning with Cfdisk, I was surprised to see that one of the precanned mount points in the Installer was /etc. On OpenBSD, we were warned against having /etc on its own partition, probably because so much important stuff lives there (like the fstab). I was also surprised to see /var wasn't in the precanned list.
    Anyway, my question is, can you really have /etc on it's own partition? And does the exclusion of /var indicate a problem with it being on its own partition?
    Last edited by NerveJessen (2010-04-02 12:50:38)

    NerveJessen wrote:
    It almost sounds like /var was accidently replaced by /etc.
    EDIT: I'll look into the bug reporting procedures.
    http://bugs.archlinux.org/
    There is the FLySpray link, and there is a button at the top right of your screen as well.
    Post back within this thread with your bug report, so other users may vote for the task once it has been assigned to a developer.
    Welcome to Arch!

  • [SOLVED] Cookie settings for Arch Linux forum

    I really do like the Arch Linux forum.
    It is fast, plain and simple; perfect for a distro which is the same
    But one thing is bothering me; the cookies.
    The arch forum is the only forum for me where the 'new post' colored picture at the left side of the forum parts is not unmarked after reading the new posts.
    After I have read all new posts, I do 'mark all topics as read' (the link at the right top) to have this result.
    For example phpbb forums do have cookie settings where the forums which are read, automatically turn the 'new post' icon off; it is not colored but the normal color again.
    Can it be that some forum settings are not completely right and this should be also the case at the Arch forums?
    Hope I have explained it that way you can understand what I mean.
    Jan
    Last edited by Lontronics (2007-03-03 17:07:04)

    Yes, and it has nothing to do with the cookie (except a session).. at least i hope it doesn't cuz that would just make me twice as glad that we switched away from that horrid chunk of code called phpbb.
    And on that note, search around a bit, because this has already been explained like three times.

  • [SOLVED] 'sl' package in arch linux?

    Hello, I'm a former Ubuntu user. In Ubuntu I was able to install 'sl' package via
    aptitute install sl
    Now I use arch linux, and I'm unable to install sl package:
    [user@myhost ~]$ sudo pacman -S sl
    error: 'sl': could not find or read package
    [user@myhost ~]$
    Can you help pls? Thanks
    Last edited by Pontorez (2010-07-21 14:09:22)

    karol wrote:[slightly OT]
    wonder, how do you search for things like 'sl', 'ne' : via the web interface or you use some AUR helper?
    $ slurpy -i sl
    Repository : aur
    Name : sl
    Version : 3.03-4
    URL : http://www.tkl.iis.u-tokyo.ac.jp/~toyoda/index_e.html
    AUR Page : http://aur.archlinux.org/packages.php?ID=12473
    Category : games
    Licenses : unknown
    Number of Votes : 164
    Out of Date : No
    Description : SL (Steam Locomotive) runs across your terminal when you type "sl" as you meant to type "ls".

  • [Solved] Cannot ping my Arch linux pc from other devices

    My newly installed arch linux pc is connected to my home network via wifi. I can successfully connect to the Internet. Also, I can successfully ping other devices on my network. However, I am unable to connect to my Arch linux pc from any other device on the network. As I said, I cannot even ping it from these other devices.
    Does anyone have an idea as to what would cause this?
    Last edited by mc33 (2015-05-12 20:29:06)

    ewaller wrote:I have a hunch that the router does not know how to find your machine.  Routers need to know to find which each IP address that is attached.  Yours might not be smart enough to remember that an address that it did not assign talked to it over the wireless.  When other computers try to talk to your address, it is clueless that you are on the wireless segment of the network, cannot find it on any wired ports, and (if it is not smart enough to figure out that it is not routable) will send it up stream or (if it is smart) will drop the packet.   Try DHCP, or, ensure that the router itself knows that the static address has been assigned to your MAC.  To do that, you will need to go into the router setup.
    I switched my Arch box to Dhcp. I thought the problem had resolved, but the issue has come back even with Dhcp enabled. I have isolated the problem to the wireless router. If I refresh Dhcp on the router, I can then ping my Arch box from other devices again. Is there anything I can do to the router to resolve this? Again, the wireless router is an Asus RT-N66U.

  • [SOLVED]How to install Arch Linux UEFI to dual-boot?

    Hey,
    so I have a Lenovo G50-70 on which I want to have a Windows-Arch dualboot. I followed the Beginner's Guide, installed Arch but ended up with an inaccessible Windows. I could boot into Windows from the BIOS utility, but not from the gummiboot bootloader.
    The guide said if I wanted to dual-boot, I must leave windows EFI partition alone, which I did. I have my Windows partitions set up the Windows way, with the system reserved and EFI and recovery partitions, and I have my Windows partition of course and a data partition. After that I have some unallocated space, on which I made the Arch partitions, /dev/sda6 as an ESP partition for the EFI files, /dev/sda7 as root, /dev/sda8 as swap and /dev/sda9 as /home. The install process went without any error, then I made some configurations and installed dosfstools & efibootmgr. After that, I installed gummiboot and ran "gummiboot --path=/boot install". After that I created the configuration files exactly like in the guide, unmounted the partitions, rebooted and saw that there's no (easy) way getting into Windows. So my question is: how can I install Arch to have a working dual-boot system?
    Thanks for any help in advance!
    Regards, Matteussz
    Last edited by Matteussz (2015-02-11 20:41:37)

    Hey,
    Writing to you on my working dual-boot with ArchLinux (Windows 8.1 64-Bit, UEFI)
    So first step I've done is creating free space of an existing partition in the windows disk management (windows button and r and then type diskmgmt.msc). At this step, you have to record which partition your efi partition is (just take a look at your efi partition and remember the mb of this partition for later)
    Then go into the uefi settings (bios) and disable secure boot as well as fast boot, otherwise it could cause data crash.
    Boot your Arch Live CD and follow the beginners guide all the way along till you reach the disk management.
    If you want to have swap, you can create yours right now, should be a primary partition of about 4gigs.
    Next partition is gonna be your home, system partition (I've didn't created two partitions for home and for the system but you could do this as well as just go with one partition) this partition gonna be formatted in ext4
    Next step, you have to mount your windows-efi partition in /boot/efi but don't format it dont remeber if it asks you how to use the partition but if so, just use as fat32.
    After the disk management go ahead with your arch installation and follow the beginners guide. (Make sure you're using the grub bootloader)
    After finishing the installation, restart your system, hopefully you will recognize the opening grub menu. (but dont scare, windows wont show in the grub menu at this time so you have to boot your arch)
    Arrived in arch linux type the command
    grub-mkconfig -o /boot/grub/grub.cfg
    Reboot and your done with your Arch Linux, Windows 8 dual boot, hopefully

  • [Solved] RAID 0 with Arch Linux and Intel Matrix Storage Manager

    I just bought a brand new DELL Studio desktop and it has 2 500 HD's which I would like to run in RAID 0. I've setup the BIOS to run the RAID 0. Now I want the arch linux installation to recognise the volume. I followed the guide on the wikipage
    http://wiki.archlinux.org/index.php/Ins … _Fake-RAID
    but /dev/mapper doesn't show anything after modprobing the modules and installing dmraid. My controller is a intel matrix storage controller, so what module should I modprobe because sata_sil isn't the right one.
    Regards
    André
    Last edited by fettouhi (2008-12-15 10:57:18)

    you have a separate /boot partition, so your menu.lst must say :
    root (hd0,0) # the partition including /boot
    kernel /vmlinuz26 ... # without leading /boot
    initrd /kernel26.img # without leading /boot
    (in grub, / is the root of the partition that was set with the root command, your vmlinuz26 and kernel26.img are in (hd0,0)/, not in (hd0,0)/boot/)
    did you install from core CD or from FTP ?
    there was a dmraid update few weeks ago that modified device names that dmraid creates :
    it add "p" before the number of the partition (your iws...Volume0 don't change, but your iws...Volume0# change to iws...Volume0p#)
    if you installed from core CD, you will only need to add this "p" when you will upgrade dmraid (or the full system)
    (you will then need to edit both /boot/grub/menu.lst and /etc/fstab)
    if you installed from FTP, you need to add this "p" now, as you installed last version of dmraid

  • [SOLVED] Trying to install Arch Linux from harddisk using /dev/sda2

    Hi
    I'm trying to install Arch using my swap partition, following this wiki entry: https://wiki.archlinux.org/index.php/Ha … stallation
    What I've done:
    Downloaded ISO: archlinux-2010.05-netinstall-i686.iso
    Command: swapoff /dev/sda2
    Command: fdisk /dev/sda and changed the system type to 83 (Linux) on /dev/sda2
    Now it looks like:
    Command (m for help): p
    Disk /dev/sda: 250.1 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders, total 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 identifier: 0x00017e5b
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 1060289 530144+ 83 Linux
    /dev/sda2 1060290 3164804 1052257+ 83 Linux
    /dev/sda3 3164805 105579179 51207187+ 83 Linux
    /dev/sda4 105579180 488392064 191406442+ 83 Linux
    It complained about device was busy, but it still seemed to have changed the system type, so I did partprobe as it wrote.
    WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
    The kernel still uses the old table. The new table will be used at
    the next reboot or after you run partprobe(8) or kpartx(8)
    Syncing disks.
    [root@swamp ~]# partprobe
    <no output>
    Next I did:
    [root@swamp ~]# dd if=archlinux-2010.05-netinstall-i686.iso of=/dev/sda2
    327680+0 records in
    327680+0 records out
    167772160 bytes (168 MB) copied, 4.3025 s, 39.0 MB/s
    [root@swamp ~]# mkdir /mnt/sda2
    [root@swamp ~]# mount /dev/sda2 /mnt/sda2
    mount: warning: /mnt/sda2 seems to be mounted read-only.
    [root@swamp ~]# ls -al /mnt/sda2
    total 150466
    dr-xr-xr-x 3 root root 240 May 16 15:54 .
    drwxr-xr-x 6 root root 4096 Nov 5 01:40 ..
    dr-xr-xr-x 3 root root 556 May 16 15:52 boot
    -r--r--r-- 1 root root 448 May 16 15:54 isomounts
    -r--r--r-- 1 root root 8192 May 16 15:54 overlay.sqfs
    -r--r--r-- 1 root root 154058752 May 16 15:54 root-image.sqfs
    And unmounted it again.
    The wiki page says to type: fsck -f /dev/sda2fsck, but I get no such file while trying to open sda2fsck.
    [root@swamp ~]# fsck -f /dev/sda2fsck
    fsck from util-linux-ng 2.18
    e2fsck 1.41.12 (17-May-2010)
    fsck.ext2: No such file or directory while trying to open /dev/sda2fsck
    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>
    Can I ignore the above and continue modifying grub?
    Thanks :-)
    Last edited by valvet (2010-11-08 14:49:07)

    fsck -f /dev/sda2fsck makes no sense because /dev/sda2fsck is not a deivce. If the wiki says that, then it is wrong. It's only doing a fsck anyway so probably not really needed. If you are just formatting th swap partition then use, mkfs.ext{234}.
    edit:
    from the wiki
    # fsck -f /dev/sda2fsck 1.40.8 (13-Mar-2008)
    e2fsck 1.40.8 (13-Mar-2008)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 3A: Optimizing directories
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    /dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
    /dev/sda2: 243/78936 files (8.2% non-contiguous), 310519/314880 blocks
    The first like should just be
    # fsck -f /dev/sda2
    Last edited by sand_man (2010-11-05 06:46:01)

  • [SOLVED] Configuring XFCE on Arch Linux to Use Uswsusp

    Hello, first time Archer and I am quickly loving it more than the other distros I have been using over the years.
    I have an oldish MacBook Pro (6,2 model, 3-4 years old) I have running Arch with base, base-devel, a variety of selected apps, and now XFCE.  I got uswsusp working, and I just usually open the Linux terminal or a terminal emulator and run `sudo s2disk`.  How do I configure XFCE buttons from the Logout menu to allow s2disk and s2ram?  I have seen a little documentation of the xfconf-query tool and using it, for example, to completely disable such icons for kiosk mode from the official XFCE forum, but I cannot figure out how to choose the suspend and hibernate commands.
    Anyone know how?
    Last edited by ajstein (2014-03-11 11:27:27)

    I assume no one is going to help with this, but rereading the instructions from the wiki regarding using uswsusp with the pm-utils section and using the FreeDesktop component one would use via dbus-send does not work, because it is dated.
    [me@laptop ~]$ dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Suspend
    Error org.freedesktop.UPower.GeneralError: Method is deprecated, please port to org.freedesktop.login1.Manager.Suspend
    I am looking into how to fix this up.  Sorry if I am being bothersome.

  • [SOLVED]Gnome 2 in Arch Linux ??

    Hi all
    after installing the base system "Arch" it's time to setup the graphical interface so my question is :
    how to install Gnome 2 classic , I have installed Gnome before with this command :
    pacman -S install Gnome Gnome-extra
    but I got the Gnome shell not the classic 1.
    so what's the command to get the Gnome classic "version 2.3 or later".
    I wanted to run Compiz on Arch but I couldn't use it because of the Gnome shell.
    Last edited by YYaaSSeeRR (2012-09-16 05:47:45)

    YYaaSSeeRR wrote:
    tomk wrote:
    Please try to understand at least the basics of Arch. Arch uses the latest stable versions from upstream projects - gnome 2 does not qualify.
    Have a look at Mate, it might satisfy your need to turn back the clock.
    thanks for the reply.
    I'm learning day after day.
    I have tried openSUSE and other distros but I really feel like I'm not learning anything with these distros because they have everything done for you just like Windows 7.
    Learning is good. Just don't expect that the community here will fill the Windows 7-like gap in your computing life; read the wiki and search the web before posting.

  • [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] Ndiswrapper, NetworkManager 0.7 and 64-bit Arch Linux

    Hi there!
    I am having problems configuring my wireless card. I know I have to use Ndiswrapper, and this is what I have tried to do; however, it didn't go quite well.
    This is rather odd because it worked perfectly in the 32-bit version of Arch Linux, but now it doesn't work.
    So, here comes the code.
    valandil ~ $ lspci | grep Network
    0b:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
    I really use ndiswrapper and have already installed what I think is the proper driver (it seems that the list the official ndiswrapper site had has somehow disappeared.
    sudo ndiswrapper -l
    Password:
    bcmwl5 : driver installed
    device (14E4:4311) present (alternate driver: ssb)
    Here's iwconfig:
    valandil ~ $ iwconfig
    lo no wireless extensions.
    eth0 no wireless extensions.
    wmaster0 no wireless extensions.
    wlan0 IEEE 802.11bg ESSID:""
    Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
    Tx-Power=0 dBm
    Retry min limit:7 RTS thr:off Fragment thr=2352 B
    Power Management:off
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    I use NetworkManager 0.7 and have configured properly:
    rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="localtime"
    USEDIRECTISA="no"
    TIMEZONE="America/Vancouver"
    KEYMAP="cf"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(fuse ndiswrapper fglrx !b44 !mii bcm43xx !snd_pcsp snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !pcspkr)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="cipher"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    eth0="dhcp"
    INTERFACES=(lo !eth0 !wlan0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.1.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(@stbd httpd !network syslog-ng netfs crond alsa hal dhcdbd networkmanager fam gdm)
    hosts file :
    # /etc/hosts: static lookup table for host names
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost cipher
    # End of file
    /etc/NetworkManager/nm-system-settings.conf:
    GNU nano 2.0.9 File: /etc/NetworkManager/nm-system-settings.conf
    [main]
    plugins=keyfile
    [keyfile]
    hostname=cipher
    I hope you can solve this problem; wireless is really crucial.
    Thanks for any help,
    Last edited by valandil (2012-05-02 18:27:09)

    Alleluia!!!
    I think I will write a new rule for myself to follow :
    Thou shalt never use ndiswrapper again.
    Thanks a lot, wonder, and thanks to you too, Xyne.
    FYI, I tried to use something else than ndiswrapper before, but it didn't yield satisfying results. Anyway, thanks.

  • [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.

Maybe you are looking for