USB 'key' in UCCX 8.X / Linux 2.4 .. Upgrading to 8.x on HP DL-380-G6

So my upgrade from 7.X to 8.X IPCC failed because Cisco isn't (yet) supporting the hardware (DL380G6) they told me buy for 7.x...     My regional Cisco rep said they are seeing that the latest version says should work (but TAC doesn't agree/ know this)..  but since its not..  they told me to send the failed upgrade logs to USB and to them
Well, I've tried 5 different USB keys..  tried formating FAT, FAT32, NTFS, and exFAT..  and they all say USB Key not found ...    I was told I needed to be W95 FAT32 and Linux 2.4 compatible.. but from what i've read....    everY FAT32 should work... and i can't believe that 5 different brands of USB flash drives don't work..
any help is appreciated!!!

Sorry no idea on the USB key part, but I am running on a
DL380G6. Did you get yours to load?

Similar Messages

  • Installing Arch Linux on USB key: error while booting

    Hello,
    first of all, I must say I've followed the steps from this article on arch wiki to install archlinux on my USB key: https://wiki.archlinux.org/index.php/In … _a_USB_key
    So what I did is to use one of my 2 usb keys to INSTALL linux, and the second one to RUN linux. I used dd to write on the 1st usb, eveything worked fine when booting, then I do install arch on the my second usb following the stept from the link above, everything works until I get this error while booting (at the middle):
    Waiting 10 seconds for device /dev/sdc/
    Root device '/dev/sdc' doesn't exist. Attempting to create it.
    ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid/lotsofnumbers'
    You are being dropped to a recovery shell
    Type 'exit' to try and continue booting
    /bin/sh: Can't contact tty; job control turned off
    [ramfs /]#
    To summarize I'll show you my conf files that could help you to resolve my problem:
    /etc/fstab.conf
    /dev/sdc1 /boot ext2 defaults 0 1
    /dev/sdc2 / ext3 defaults 0 1
    /dev/sdc3 /home ext3 defaults 0 1
    So here I've sdc1 boot 32MB partition; sdc2 root 3GB partition; sdc3 home 978MB partition for a total of 4GB USB key~
    I didn't make a swap partition as in the tutorial they are writing it's unnecessary for some kind of reasons.
    /etc/mkinitcpio.conf
    HOOKS="base udev usb autodetect pata scsi sata filesystems"
    I've added to here, "usb" to the hooks
    installed GRUB on my sdc, here is the menu.ist:
    # (0) Arch Linux
    title Arch Linux (USB)
    root (hd0,0)
    kernel /vmlinuz26 root=/dev/sdc ro vga=773
    initrd /kernel26.img
    So, I boot GRUB without problems, start Arch Linux, but then I got this error above.
    I've searched alot on some forums and read many stuffs, but sitll can't fix it and it seems complicated.
    I've tried to boot with UUID, also, but didn't make difference. I tried to remove some parameter from the hooks, but unfortunately this wasn't working still. I've read somewhere to use chroot, but I didn't catch on how to do that and what was the use of chroot, I'm still noob user of arch linux and currently learning. Maybe it's the problem, as some forum were talking about creating a new image, but I still don't know how to make it. By the way, I'm not sure this could have fixed my current problem. I've also read somewhere it could be due to my lack of space, but I wrote you how I did partition my USB key, let me know if you have any suggestion please.

    1. What I did is re-installing entirely from my installation disk or USB to test out different setting in  my config files, because I don't know how to edit my .conf as I can't really finish to boot to the end and get in terminal mode? If there is a quicker way to edit files from any terminal to go into my current USB sdc to modify directly my file from there, I'd enjoy probably. So rebuilding the initpio, no, I just re-installed to test out different configs.
    2. Yes, same error.
    3. Tested out by-id/by-path and uuid = no difference
    4. Didn't know about larch, it seems to be a nice tool, I'll check it out

  • Is it suitable install Arch Linux on a USB key?

    I want to install Arch Linux on a USB  key following the wiki https://wiki.archlinux.org/index.php/In … _a_USB_key
    But I now heard that Arch Linux will be very very slow than LiveUSB because of USB's bad I/O speed. Is it real?
    Forgive my poor English, thank you!

    Actually I spent some times to study USB, and I concluded out that it is relate with USB's performance, as example, USB 3.0 is better than USB 2.0, SLC is better than MLC.
    So the better performance of USB the more suitable to install Arch Linux. However, it will costs me much money to buy expensive USB:)
    @Mr Green What's your blog? Is this http://archbang.org/?

  • X server won't start (Arch Linux installed on USB key)

    Hi,
    I installed Arch Linux on a USB key (see the original thread: https://bbs.archlinux.org/viewtopic.php?id=185441).
    The problem is that X doesn't start on all machines.
    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 .. .. .. ..".
    - 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).
    What happens if you uninstall nvidia and use nouveau?
    I installed all video drivers recommended here: https://wiki.archlinux.org/index.php/In … eo_drivers
    So I was using nouveau in the first place. I already tried to uninstall the open source driver (xf86-video-nouveau, nouveau-dri) to use the default driver (I think this is xf86-video-vesa) with no effect.
    The poor tty resolution is to be expected if the closed-source nvidia drivers are installed, because they don't support KMS.
    I have never tried to install the proprietary driver (and actually don't want to use the proprietary driver).
    Also have you looked in /etc/X11 ?
    Yes. I don't think that my configuration contains anything preventing X from starting using the NVIDIA graphics card (but I'm not sure what to look for).
    I'm starting X using "startx" or "xinit -- :0 -nolisten tcp vt$XDG_VTNR". Here's my ~/.xinitrc:
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    exec startxfce4
    Last edited by The Infinity (2014-08-14 21:17:41)

    I figured out where the problem comes from. It is actually the screen (which has a resolution of 1920x1080 pixel). When using a screen (with a smaller resolution) I'm getting a decent resolution in the terminal and - more imporant -  X starts and seems to use the Nouveau driver (which I have installed again). When plugging my normal screen again (while X is running) I'm able to use this screen with the maximum resolution without problems (so only starting with this screen does not work). Now I have a reference point to fix the problem.
    The other thread might be interesting as well.
    Last edited by The Infinity (2014-08-17 02:36:57)

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

  • Having trouble installing Arch Linux to USB key

    Hello,
    I have read the wiki article, but it doesn't answer my question. I am having trouble installing Arch to a USB key (8GB Sandisk Cruzer). I installled GRUB correctly, it booted, but the flash drive was write-protected. In the fstab file, I have the defaults and noatime flags in there. I have never experienced an error like this, and I don't know how to fix it. I have tried to reboot into the Arch CD and mounted the USB, but it just stalls and displays no output. Obviously, if I boot into my USB (you can still boot into it), and do "nano /etc/fstab", it says that I cannot write. In case you were wondering, I am using the root user. Thank you for all your help!
    EDIT: I have Syslinux, the kernel parameters is RW. If I run mount -o remount,rw /dev/sda1, it tells me something like:
    ata3.00: status: {DRDY ERR}
    ata3.00: error: {IDNF}
    end_request: I/O error, dev sda, sector 21
    Buffer I/o error on device sda1, logical block 0
    EXT4-fs error (device sda1): ext4_remount:4665: Abort forced by user
    I did NOT hit CTRL+C.
    Last edited by aqua123 (2013-09-07 02:01:30)

    I'm a nub, and I think I'll piggy back of aqua's post.  Perhaps we have the same problem
    I have an Asus UX31A with Xubuntu (with grub) currently installed.  I created the bootable USB as per the Arch Wiki UEFI bootable usb page.  I can boot into the main prompt where you can choose "Arch Linux Iso", "shell v1", "shell v2" and "Default prompt."
    Choosing the first option (to get to the the command prompt and begin installing) makes the screen flash once, then just hangs black.  Before the flash I think I see three text lines in the upper left corner, but they flash so fast I can't read them.
    Choosing either of the shell options presents the error:
    "Error loading \EFI\shellx64_v1.efi: Unsupported"  (replace "v1" with "v2" for the other option)
    Any thoughts?

  • Issue on linux live usb key boot

    Hi all,
    I ve several laptops at home : X40, T30, T42p and a Dell D410. I ve a Corasair mini voyager 4Go usb key.
    A live ubuntu 9. is intalled on the usb key. I ve made this installation with this tool : Linux Live Usb Creator. This works on the dell D410, i get the linux live booting fine on the usb key. On the three IBM I got the same error message "Boot Error".
    The three IBM laptops have an up to date bios thanks to Thinkvantage System Update
    I ve set the Bios Config->USB->Enable
    Have you already experience this boot issue ?
    Have you any idea to solve this issue ?
    Regards
    Pierr0t

    I have had that error. I can burn a cd or create live usb pen drive and it will work on another machine but not on my dell desktop. It also comes up with boot ( and root) error. Strange thing is sometimes with a live cd it does and sometimes with others it doesnot...hmm
    Ideas anyone?

  • Home directory on USB key?

    Hi all,
    A friend suggested this idea and it seems like a good idea, I was wondering if something similar already exists or what your opinion of it would be.
    The idea is as follows: suppose you could have your home directory on a USB key. To log in on a computer, you'd just have to plug it in, and ta-da! you would be working on your own desktop, with your own files and configuration.
    Now I know distros-on-a-stick exist, but the idea would be to only have your home directory on your key, not the full OS. That way you wouldn't have to reboot, and you'd be pretty much architecture-agnostic, and mostly distro-independent.
    So is this somehow already possible? The problems I see is the dynamic user account creation - you'd have to create a temporary user each time a person logs in with his key. Also, of course, there would be the problem of user applications, since not all user applications would probably be installed on the computer.

    Can't really see the use for this, I'm afraid. I'd rather have an OS on a stick, than a /home on a stick. And you don't have to reboot, you could use virtualisation, right? Like qemu is used for DSL.
    The fact that not all applications you need might be installed, applications might be of different versions, config files might get screwed up in the process, and that you need a linux computer in the first place are all negatives.

  • [SOLVED] Many modules are not loaded in the Arch USB key installation.

    Hello!
    I installed Arch Linux on my USB key. I did it few months ago and it worked, I had portable arch.
    Yesterday I decided to make a fresh installation. Unfortunately after booting it from my USB key
    most of the modules were not loaded. Because of that I couldn't start the X server and connect to
    the internet (ethernet card was not detected).
    Even after loading the module which corresponds to my ethernet card manually (modprobe e1000e) it was not
    displayed in the lsmod list.
    I though "maybe I screwed something up during the installation?". To find out I used GParted to copy
    my OS partition (perfectly working Arch Linux installed on the hard drive) to the USB key. Of course I changed the UUID of the USB partition.
    After booting it I was suprised because the situation did not change - modules that are loaded on my main system for some
    reason were not loaded on it's exact copy placed on the USB key.
    I have no idea why my portable OS is acting like this.
    Commands below were executed on another PC so don't look for the e1000e module.
    $ lsmod
    Module Size Used by
    ext4 474699 2
    crc16 1367 1 ext4
    mbcache 6082 1 ext4
    jbd2 83440 1 ext4
    usb_storage 48007 2
    ata_generic 3378 0
    pata_acpi 3395 0
    hid_generic 1161 0
    usbhid 40577 0
    hid 90742 2 hid_generic,usbhid
    sr_mod 14898 0
    cdrom 34848 1 sr_mod
    sd_mod 30821 3
    pata_atiixp 4819 0
    ehci_pci 4000 0
    ohci_pci 4040 0
    ohci_hcd 23905 1 ohci_pci
    ehci_hcd 59252 1 ehci_pci
    usbcore 180104 6 usb_storage,ohci_hcd,ohci_pci,ehci_hcd,ehci_pci,usbhid
    ahci 23056 0
    libahci 21642 1 ahci
    usb_common 1656 1 usbcore
    libata 171112 5 ahci,pata_acpi,libahci,ata_generic,pata_atiixp
    scsi_mod 130669 4 usb_storage,libata,sd_mod,sr_mod
    nouveau 904702 0
    button 4677 1 nouveau
    video 11196 1 nouveau
    mxm_wmi 1475 1 nouveau
    wmi 8419 2 mxm_wmi,nouveau
    i2c_algo_bit 5399 1 nouveau
    drm_kms_helper 36254 1 nouveau
    ttm 63507 1 nouveau
    drm 238238 3 ttm,drm_kms_helper,nouveau
    i2c_core 24164 4 drm,drm_kms_helper,i2c_algo_bit,nouveau
    $ ip link
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    $ lspci #Just a fragment
    02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
    Subsystem: Gigabyte Technology Co., Ltd Motherboard
    Flags: bus master, fast devsel, latency 0, IRQ 10
    I/O ports at de00 [size=256]
    Memory at fdaff000 (64-bit, prefetchable) [size=4K]
    Memory at fdaf8000 (64-bit, prefetchable) [size=16K]
    [virtual] Expansion ROM at fda00000 [disabled] [size=128K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Endpoint, MSI 01
    Capabilities: [ac] MSI-X: Enable- Count=4 Masked-
    Capabilities: [cc] Vital Product Data
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Virtual Channel
    Capabilities: [160] Device Serial Number 07-00-00-00-68-4c-e0-00
    $ cat /etc/X11/xorg.conf
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 331.38 (buildmeister@swio-display-x64-rhel04-15) Wed Jan 8 19:53:14 PST 2014
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    EndSection
    Section "Files"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    $ cat /var/log/Xorg.0.log
    [ 59.424]
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    [ 59.424] X Protocol Version 11, Revision 0
    [ 59.424] Build Operating System: Linux 3.12.5-1-ARCH x86_64
    [ 59.424] Current Operating System: Linux sanguine 3.12.7-2-ARCH #1 SMP PREEMPT Sun Jan 12 13:09:09 CET 2014 x86_64
    [ 59.425] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=2c39c1f9-de3e-4907-93dc-8b77422a07a1 rw
    [ 59.425] Build Date: 09 January 2014 08:47:24AM
    [ 59.425]
    [ 59.425] Current version of pixman: 0.32.4
    [ 59.425] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 59.425] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 59.425] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 13 12:55:56 2014
    [ 59.433] (==) Using config file: "/etc/X11/xorg.conf"
    [ 59.433] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 59.437] (==) ServerLayout "Layout0"
    [ 59.437] (**) |-->Screen "Screen0" (0)
    [ 59.437] (**) | |-->Monitor "Monitor0"
    [ 59.441] (**) | |-->Device "Device0"
    [ 59.441] (**) |-->Input Device "Keyboard0"
    [ 59.441] (**) |-->Input Device "Mouse0"
    [ 59.441] (==) Automatically adding devices
    [ 59.441] (==) Automatically enabling devices
    [ 59.441] (==) Automatically adding GPU devices
    [ 59.456] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 59.456] Entry deleted from font path.
    [ 59.456] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 59.456] Entry deleted from font path.
    [ 59.457] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 59.457] Entry deleted from font path.
    [ 59.457] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 59.457] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 59.457] Entry deleted from font path.
    [ 59.457] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 59.457] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 59.457] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 59.457] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 59.457] (WW) Disabling Keyboard0
    [ 59.457] (WW) Disabling Mouse0
    [ 59.457] (II) Loader magic: 0x804c80
    [ 59.457] (II) Module ABI versions:
    [ 59.457] X.Org ANSI C Emulation: 0.4
    [ 59.457] X.Org Video Driver: 15.0
    [ 59.457] X.Org XInput driver : 20.0
    [ 59.457] X.Org Server Extension : 8.0
    [ 59.459] (--) PCI:*(0:1:5:0) 1002:796e:1458:d000 rev 0, Mem @ 0xd8000000/134217728, 0xfdfe0000/65536, 0xfde00000/1048576, I/O @ 0x0000ee00/256
    [ 59.459] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 59.460] Initializing built-in extension Generic Event Extension
    [ 59.460] Initializing built-in extension SHAPE
    [ 59.460] Initializing built-in extension MIT-SHM
    [ 59.460] Initializing built-in extension XInputExtension
    [ 59.461] Initializing built-in extension XTEST
    [ 59.461] Initializing built-in extension BIG-REQUESTS
    [ 59.461] Initializing built-in extension SYNC
    [ 59.461] Initializing built-in extension XKEYBOARD
    [ 59.461] Initializing built-in extension XC-MISC
    [ 59.461] Initializing built-in extension SECURITY
    [ 59.461] Initializing built-in extension XINERAMA
    [ 59.461] Initializing built-in extension XFIXES
    [ 59.461] Initializing built-in extension RENDER
    [ 59.461] Initializing built-in extension RANDR
    [ 59.463] Initializing built-in extension COMPOSITE
    [ 59.466] Initializing built-in extension DAMAGE
    [ 59.468] Initializing built-in extension MIT-SCREEN-SAVER
    [ 59.470] Initializing built-in extension DOUBLE-BUFFER
    [ 59.472] Initializing built-in extension RECORD
    [ 59.475] Initializing built-in extension DPMS
    [ 59.477] Initializing built-in extension Present
    [ 59.479] Initializing built-in extension DRI3
    [ 59.481] Initializing built-in extension X-Resource
    [ 59.483] Initializing built-in extension XVideo
    [ 59.485] Initializing built-in extension XVideo-MotionCompensation
    [ 59.487] Initializing built-in extension XFree86-VidModeExtension
    [ 59.490] Initializing built-in extension XFree86-DGA
    [ 59.492] Initializing built-in extension XFree86-DRI
    [ 59.494] Initializing built-in extension DRI2
    [ 59.494] (II) LoadModule: "glx"
    [ 59.502] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 60.382] (II) Module glx: vendor="NVIDIA Corporation"
    [ 60.388] compiled for 4.0.2, module version = 1.0.0
    [ 60.388] Module class: X.Org Server Extension
    [ 60.388] (II) NVIDIA GLX Module 331.38 Wed Jan 8 19:10:17 PST 2014
    [ 60.401] Loading extension GLX
    [ 60.401] (II) LoadModule: "nvidia"
    [ 60.401] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 60.455] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 60.455] compiled for 4.0.2, module version = 1.0.0
    [ 60.455] Module class: X.Org Video Driver
    [ 60.462] (II) NVIDIA dlloader X Driver 331.38 Wed Jan 8 18:51:00 PST 2014
    [ 60.462] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 60.464] (++) using VT number 1
    [ 60.464] (EE) No devices detected.
    [ 60.464] (EE)
    Fatal server error:
    [ 60.464] (EE) no screens found(EE)
    [ 60.464] (EE)
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 60.464] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 60.465] (EE)
    Last edited by Skitter (2014-02-16 20:57:21)

    Please post the output of:
    dmesg -c
    modprobe e1000e
    dmesg

  • [SOLVED] Attempting to boot from USB key in UEFI mode

    I am attempting to boot from a USB Key in UEFI mode to dual boot windows 8 and arch linux.  I'm unsuccessful in getting the USB key to boot in UEFI mode. 
    I am following the guide on page: https://wiki.archlinux.org/index.php/Un … _Interface due to the fact that I am receiving error " No loader found. Configuration files in /loader/entries/*.conf are needed."
    I am attempting to use the archiso media and have created refind.conf according to https://bugs.archlinux.org/task/31894#comment102233 in (USB)/EFI/boot/refind.conf
    However, I'm stuck on the initial step from the wiki: Install refind-efi pkg. In the usb's filesystem, overwrite the file EFI/boot/bootx64.efi with /usr/lib/refind/refind_x64.efi.
    My question is: How do I install the refind-efi package onto the USB key using an arch linux host machine and the USB plugged into the machine.
    Last edited by tonysoprano (2013-02-13 04:09:56)

    swordfish wrote:1. Might be possible, that the uefi integration is pretty bad. Have you already looked for an update of the uefi bios?
    This is my thought, too. The "memory map has changed" message sounds like the firmware is messing with the way memory is laid out in the middle of the boot process. A firmware update, if available, is likely to be the best way to deal with this problem. If not, trying Fedora's patched GRUB Legacy and GRUB 2 are also worth doing; it's conceivable that one of them includes a workaround for the problem.
    2. In your first posting you mention Windows 8 on this machine. Is W8 starting in uefi mode?
    This is important, but if the disk uses GPT partitioning, then Windows is starting in EFI mode.
    3. If W8 is starting in uefi mode, are you sure that secure boot is disabled?
    It is; if it weren't, neither rEFInd nor ELILO could start -- or even if they were configured to start in Secure Boot mode, ELILO doesn't launch its kernels in a way that respects Secure Boot, so the ELILO failure can't be caused by Secure Boot. Also, when launched with Secure Boot active, rEFInd returns a clear error message about a security violation and then returns to its main menu; it doesn't hang the computer.
    One possible workaround occurs to me if all else fails: Have rEFInd launch a BIOS version of GRUB. The setup procedure, in outline, is as follows:
    Create a BIOS Boot Partition on the disk.
    Install the BIOS version of GRUB 2.
    Configure rEFInd to include a scan for BIOS-mode boot loaders by uncommenting the "scanfor" line in refind.conf and adding "hdbios" to it.
    Thereafter, you'll see a new "generic" icon, which should launch GRUB, which should launch Linux in BIOS mode, even though Windows launches in EFI mode. This will work on most modern UEFI-based computers with a single hard disk, but things get trickier with multiple disks and with some UEFI implementations that lack the necessary firmware features. If a future firmware update fixes the problem, or if a future kernel's EFI stub loader includes a workaround, the EFI-mode booting will become an option once again.

  • [SOLVED] install i686 on USB key from x86_64 : how ?

    Hi.
    As written in the title, I'm trying to install an Arch system on an usb stick, with i686 architecture, from the Arch x86_64 system on my computer.
    I would like to do it without copying the iso to an extra usb key.
    From the wiki : "If you are already running Arch, simply install arch-install-scripts and proceed with the installation guide just like you would from the iso, [...]"
    1) I'm not sure about what it means : can I actually do the install using arch-install-script, without using the iso or the bootstrap image ? Is that correct ?? (english is not my native language).
    2) Anyway, it didn't work. So I downloaded the bootstrap(s) image(s).
    Tried the i686 one, then the x86_64 one.
    For each, I changed the architecture in pacman.conf from "architecture = auto" to "architecture = i686".
    [~/tmp] tar xzf ~/downloads/archlinux-bootstrap-2015.03.01-x86_64.tar.gz
    [~/tmp] vi root.x86_64/etc/pacman.conf
    [~/tmp] vi root.x86_64/etc/pacman.d/mirrorlist
    [~/tmp] sudo root.x86_64/bin/arch-chroot root.x86_64/
    sh-4.3#
    sh-4.3# pacman-key --init
    sh-4.3# pacman-key --populate archlinux
    sh-4.3# lsblk
    sh-4.3# mount /dev/sdc2 /mnt
    sh-4.3# pacstrap -c /mnt base base-devel
    (I tried with and without the -c option)
    will give :
    ==> Creating install root at /mnt
    ==> Installing packages to /mnt
    :: Synchronizing package databases...
    core is up to date
    extra is up to date
    community is up to date
    :: There are 50 members in group base:
    :: There are 25 members in group base-devel:
    warning: skipping target: file
    warning: skipping target: findutils
    warning: skipping target: gawk
    warning: skipping target: gettext
    warning: skipping target: grep
    warning: skipping target: gzip
    warning: skipping target: pacman
    warning: skipping target: sed
    warning: skipping target: texinfo
    warning: skipping target: util-linux
    warning: skipping target: which
    error: failed to prepare transaction (package architecture is not valid)
    :: package bash-4.3.033-1-x86_64 does not have a valid architecture
    :: package bzip2-1.0.6-5-x86_64 does not have a valid architecture
    [same message with coreutils-8.23-1-x86_64 cryptsetup-1.6.6-1-x86_64
    and more than 50 other packages, up to sudo-1.8.12-1-x86_64]
    Same with the i686 bootstrap image :
    [~/tmp] tar xzf ~/downloads/archlinux-bootstrap-2015.03.01-i686.tar.gz
    [~/tmp] sudo cp /etc/pacman.d/mirrorlist root.i686/etc/pacman.d/mirrorlist
    [~/tmp]♭ sudo root.i686/bin/arch-chroot root.i686/
    sh-4.3# pacman-key --init
    sh-4.3# pacman-key --populate archlinux
    sh-4.3# lsblk
    sh-4.3# mount /dev/sdc2 /mnt
    sh-4.3# pacstrap /mnt base base-devel
    error: failed to prepare transaction (package architecture is not valid)
    :: package bash-4.3.033-1-x86_64 does not have a valid architecture
    Thanks.
    Last edited by Tétrapyle (2015-03-23 21:27:30)

    Thanks for your reply. I just updated the whole system.
    Then
    [~]$ sudo mount /dev/sdc2 /mnt
    [~]$ sudo vi /etc/pacman.conf
    My system is x86_64. I'm trying to install from that an i686 system.
    If I run pacstrap now, it'll run ok but obviously it'll install an x86_64 system.
    So, in pacman.conf, I changed Architecture from auto to i686 and I commented out the Multilib lines.
    It seems it's not enough.
    [~]$ sudo pacstrap -c /mnt
    error: failed to prepare transaction (package architecture is not valid)
    :: package bash-4.3.033-1-x86_64 does not have a valid architecture
    :: package bzip2-1.0.6-5-x86_64 does not have a valid architecture
    :: package coreutils-8.23-1-x86_64 does not have a valid architecture
    :: package cryptsetup-1.6.6-1-x86_64 does not have a valid architecture
    :: package device-mapper-2.02.116-1-x86_64 does not have a valid architecture
    :: package dhcpcd-6.7.1-1-x86_64 does not have a valid architecture
    :: package pkg-config-0.28-2-x86_64 does not have a valid architecture
    :: package sudo-1.8.12-1-x86_64 does not have a valid architecture
    ==> ERROR: Failed to install packages to new root
    Where do these x86_64 come from ? Could it be they stand for the $arch in the Server line from /etc/pacman.d/mirrorlist ?

  • How to partition a USB flash-drive to install Arch Linux?

    Good afternoon,
    Could anyone please guide me in the right direction, how would I go about partitioning my USB flash-drive in order to install Arch Linux onto my Acer Aspire One? I've found guides, but none of them are specific enough - the static assumption being that the OS is already partitioned onto your flash-drive, and that is not the case for me.
    Much appreciated,
    A Swiftly Tilting Planet

    assuming your usb key is /dev/sdz
    # dd if=/dev/zero of=/dev/sdz
    //cleans the usb drive
    # fdisk /dev/sdz
    // press m and read the help, make a partition, make it bootable
    // you have to press (double check anyway):
    // n, p, 1, <enter>, <enter>, a, 1, t, b, w
    # mkfs.vfat /dev/sdz1
    // formatting
    The first passage can actually replaced to something more modest, like:
    # dd if=/dev/zero of=/dev/sdz bs=1024 count=1
    Last edited by ezzetabi (2009-01-03 16:37:04)

  • USB key for flash 2900 routers

    Gi/Gals
    We have been using USB keys to update the firmware on routers  and to provide backup copies of ios (usbflash:). It seems that the 2900 series routers are a bit more selective about what USB keys they will accept, where the 2800s don't seem to care. I have tried partitioning, and a range of different formats, but other than buying the USBs from Cisco, non-Cisco USB keys don't seem to work. Does anyone have any tips here that might allow me to use  non-Cisco USB keys.
    thanks
    Rob

    I've been using non-Cisco USB thumb drive (and non-Cisco CF) since 2007. 
    Not all USB thumb drives are supported.  It gets even worst.  Let's say you have a Lexar 2Gb thumb drive that works.  So you get a bigger one of the same "model", a 4 Gb or 8Gb or 16Gb.  Guess what, they may or may not work.  The 8Gb may work but the 4Gb and 16Gb may not (or in some other insane combination). 
    The main reason is because Lexar, Toshiba, 3M, etc ... They don't manufacture the thumb drives they sell.  They buy them direct from the manufacturer.  Whether or not these manufacturers follow the standard (the ones supported by Cisco), doesn't matter as long as their products can be recognized by UNIX/Linux, Apple and MS that's good enough for the companies that stamp their brand and shape. 
    Recently, I found a Sandisk Cruzer Facet 8Gb and it seems to work on 3560CG and 2960S so I would assume it would work on our routers as well. 

  • Mac in the shop -- how to access encrypted FS image on USB key?

    My Mac is in the repair shop (it's a G4 PowerBook, circa Titanium). In the meantime, I've got a USB key with a UFS file system created by 10.3.9, on which resides an AES-128-encrypted disk image (.dmg file).
    I can mount the USB key's UFS file system from Linux, using 'mount -t ufs -o ro,ufstype=openstep /dev/sdb3 /mnt/<whatever>', so I can see the encrypted disk image (as well as my non-encrypted files). I believe I know the password for the encrypted disk image. But what file system type is it? Is it also ufs/openstep?
    The basic question is, when creating an AES-128 encrypted disk image using Disk Utility, what is the file system type underneath the encryption?
    Thanks!

    Hm. Well, when I use Disk Utility on 10.3.9 to create an encrypted disk image, it doesn't give me any choice as to the file system format. It allows me to choose what directory to create it in, how big it should be, and whether or not to use AES128 encryption -- that's it. Maybe there are more choices on Tiger/Leopard.
    So, what file system type will Disk Utility on 10.3.9 create?

  • Installing Arch on a USB Key Partition

    I'm new to Arch Linux, and installed it on a partition on my USB Key to try it out (it's cool!.... so far).  One problem though.  It's an 8GB drive with two partitions.  I installed Arch on the first partition (2.5GB) and the rest is for storage.  This is fine on computers that run Linux, but Windows only recognizes the first partition and does not see the storage partition.
    Is there a way I could copy my entire Arch filesystem so I could reformat my USB Key with the partitions in the correct order?  I was looking into Partimage and CloneZilla.  I am also open to other solutions.

    Clonezilla worked fine!  For anyone else who wants to restore an image of a partition to a different partition, make sure you read this:
    http://drbl.org/faq/fine-print.php?path … tition.faq
    Last edited by zangderak (2011-09-10 01:19:20)

Maybe you are looking for

  • Form Data Order in XML

    How can you organize form data exported via XML Email Submit button? I would expect this data to follow the order within the XDP object heirarcy, however the results jump from object to object on different pages. Forget about mapping this to a databa

  • Events in Interactive reports

    hi gurus, i want detailed explanation each n every event of standard report... Regards baskar

  • Multiple Queues - Dequeueing resources?

    We have multiple queues on our database which have been configured to be automatically processed by registering stored procedures with each of the queues. The processing of messages works fine, however if we have messages in both queues then it appea

  • Finally switching from pc to mac..few questions.

    I got a macbook pro, slowly gearing up to migrate everything over. I'm going to use Detto to do the migration. They assured me my entire itunes library and playlist would transfer. I have iphone, and 3 ipods. My itunes library on computer is much lar

  • BT Infinity resync

    We have used BT Infinity for a while and performance is good when it works. The problem we have is that the router seems to disconnect all wireless connections for a short period and I can only assume that this is because the system is resynching wit