You start a qemu like this and another VM already started with the same .iso
qemu-system-x86_64 -enable-kvm -m 4096 -cdrom some.iso
But you get this error:
qemu-system-x86_64: Initialization of device ide-hd failed: Failed to get "write" lock
Is another process using the image [some.iso]?
It's odd because the -cdrom by default is read-only and qemu should not want or care about getting write lock on........
You may have been expecting a normal sized kernel but if you don't disable these .config options you may have a kernel that is several gigabytes.
CONFIG_SLUB_DEBUG=no
CONFIG_DEBUG_INFO=no
CONFIG_DEBUG_MISC=no
Rebuild and you should find that the kernel is the normal and as expected size.........
You'll notice that /etc/resolv.conf contains dire warners on most Linux Desktops.
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use........
You can read lots of posts about this issue but there is not much information about why this is the case or how grub determines the root= device name. Some even suggest modifying grub.cfg manually which is a disaster as the next kernel update will cause grub to revert back to the device name.
For most people this won't be an issue but those using template system, automated deployments and working in embedded may run into this issue with custom embedded and created minimal kernel........
You probably didn't do an "update-grub" and grub no longer has any proper menu entries, but before you can fix it let's try to get grub booting anyway.
If you get this lovely black grub screen here's how you can get things booting.
In my case I have a gpt partition with partition 1 and 2. Partion 1 is just my EFI / ESPand partion 2 /dev/sda2 is my root which includes /boot.
You will have to adjust this if you had a separate /boot partition.........
You might assume you have a bad drive or the SATA interface/cable is bad, or the power supply is bad/weak to the drive. These are all possible issues, but definitely check your SATA cable for "twisting". It is a big issue because until the error stops or times out, your system will not boot (in my case this was the case even though the drive with the issue was not part of the OS or booting process at all).
If you run an open rig that you move around often that ha........
You need to disable vsync like this when running glxgears:
vblank_mode=0 glxgears
For Nvidia drivers do this:
__GL_SYNC_TO_VBLANK=0 glxgears
Notice the higher than 59-60 fps results with vblank_mode=0:
ATTENTION: default value of option vblank_mode overridden by environment.
7919 frames in 5.0 seconds = 1583.704 FPS
8187 frames in 5.0 seconds = 1637.266 FPS........
You may have noticed if you are running QEMU/KVMmanually that in Windows the the position of the physical mouse does not match where the mouse is positioned within Windows.
There is an easy command to pass to qemu-kvm or qemu-system (whatever you call your binary):
-usbdevice tablet
The above flag will fix your mouse pointing problems whether you are running Windows 95, 98, NT, XP 2000, 2003, Vista, 7, 8 10 or Server 2000, 2003, 2008, 2012, 2016 or 2........
Your database uses Antelope as the file format. Full UTF-8 support in MySQL and MariaDB requires the Barracuda file format. Please switch to the Barracuda file format. See the documentation MySQL full unicode support for details.
In /etc/my.cnf under [mysqld]
180827 21:43:14 InnoDB: 5.5.59 started; log sequence number 1589339
180827 21:43:14 [ERROR] /usr/libexec/mysqld: unknown variable 'db_file_format=Ba........
You can search for this bug and it seems like it may be related to ecryptfs and is many years old.
The symptoms are that you return to the computer and the screensaver was active or the screen was asleep/black and it doesn't seem to come back. But you check by SSH the computer is running fine and are frustrated you'll lose your running programs and have to reboot.
There is a simple solution:
Ctrl + Alt + F1
Ctrl +Alt + F8
Ba........
You are checking your MySQL logs in /var/log/mysqld.log and come across an error like this:
161222 18:03:40 [ERROR] /usr/libexec/mysqld: Table './eximstats/sends' is marked as crashed and last (automatic?) repair failed
The Solution:
cd /var/lib/mysql/eximstats
myisamchk -r sends.MYI
- recovering (with sort) MyISAM-table 'sends.MYI'
Data records: 71129........
You need to use the Samsung driver but specify it as a CLP-360 (this is what I used for my CLP365) and incidentally most of these units look identical on the outside on inside (I've been buying whatever the latest C300 and now 400 unit for years which all seem the same with slightly different features that I never use).
The solution
Once again try specifying earlier models and revisions if the printer doesn't print (it will say it's been sent to the printer bu........