search for: jamespharvey20

On 7 October 2016 at 15:41, james harvey <jamespharvey20 at gmail.com> wrote: > y this into a systemd .service file which would auto-run > after boot. You wouldn't need sudo anymore, and you wouldn't want the > reboot command or it would auto reboot during the boot > Thanks for the quick reply! My understanding of that script a...

...Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: jamespharvey20 at gmail.com QA Contact: xorg-team at lists.x.org I experience a complete lockup every 1-3 days, except the mouse cursor still moves. Keyboard LED's don't flash. Num/Caps/Scroll Lock doesn't toggle the keyboard LED's. Can't switch to text tty's. Can't ping i...

Hi, I am currently using isolinux (syslinux-6.03) in a clonezilla setup. It boots fine, however I want to have a setup where the default boot selection alternates every boot. * First boot : Default is menu item 0 * Second boot : Default is menu item 1 * Third boot : Default is menu item 0 ... The idea is that when it is booted into clonezilla the clonezilla script checks if the system needs to

"Changes in 4.02" includes: btrfs: print a comprehensive error message if compressed or encrypted files are encountered (neither is currently supported.) I don't see a changelog since saying support for btrfs compressed filesystems was added. Is this something in the works, or unlikely to be added?

> No Syslinux variant can load items outside the current file system > space, yet. SYSLINUX can't load anything outside its current block > file system. ISOLINUX can't load anything outside its current ISO > image. PXELINUX can only load network files. Similar rules apply for > Syslinux EFI based on where it was loaded from. There's a patchset > that will be put

Attempting to install syslinux on a multi-device (raid1) btrfs volume gives the head-scratching error of: ============================= /boot/syslinux is device /dev/sda1 extlinux: path /boot/syslinux doesn't match device /dev/sda1 ============================= extlinux/main.c::validate_device_btrfs()::line 1247 returns -1 along with all of the other error conditions, causing this set of

Not sure iso/syslinux directly has a way to do this, but I did find a way to have a system act like you're saying. I don't want it to automatically alternate, I want to have a command to run that will change the default. (Remote system.) ===== #!/bin/bash sudo bash -c "sed -i '0,/^DEFAULT .*$/{s/^DEFAULT .*/DEFAULT terra-snapper/}' /boot/syslinux/syslinux.cfg" sudo

managedsave/start appears to work, but VM is unusable due to non-stop repeating uhci_hcd errors. I can't remove the USB controller from QEMU, but I CAN remove it through virsh edit. Doing so eliminates the USB controller in the guest, preventing non-stop repeating uhci_hcd errors. (QEMU only lets you remove the USB redirection entries, which didn't help.) Using libvirt 1.2.18 (-1 Arch)

If I manually delete the Q35 USB Controllers, I can use managedsave/start, but I start getting tty errors that don't happen before the managedsave/start. Using libvirt 1.2.18 (-1 Arch) and QEMU git-master (2.4.0.r40384.2d69736). Installed using Q35 chipset. I'm running QEMU git, which allows SCSI controller migration, so I can attempt doing this. I started my guest, and waited for 15

Using libvirt 1.2.18 (-1 Arch) and QEMU git-master (2.4.0.r40384.2d69736). pm-utils 1.4.1-6. acpid 2.0.23-4 Installed using Q35 chipset. I can perform virsh # shutdown <vmname>, and watching the client VM console see a graceful shutdown. On host: ===== # systemctl reboot {{{ client VM console immediately blanks out - I do NOT see a graceful shutdown }}} libvirt-guests.sh: Running guests

I have LVM volumes: /dev/disk1/main /dev/disk1/mainboot /dev/disk1/other /dev/disk1/otherboot I can boot main by using syslinux with syslinux.cfg including: LABEL main MENU LABEL Main LINUX ../vmlinuz-linux APPEND root=UUID={UUID} {kernel parameters} INITRD ../initramfs-linux.img (1) I see a lot of places saying syslinux can't boot a kernel on another partition, and that you have

How do I "enable" qemu-ga on a guest to be able to (I think this means have a success-response:true) for: guest-suspend-hybrid; guest-suspend-ram; guest-suspend-disk; and guest-shutdown? At least I think that's my question. http://wiki.stoney-cloud.org/wiki/Qemu_Guest_Agent_Integration shows these same 4 as false, so I'm not sure if they're always supposed to be that way.