I went hunting in the BIOS for ‘verve‘ which has a ASUS PRIME B550M-A motherboard and I found I needed to change two settings.
The first setting was Advanced -> CPU Configuration -> SVM Mode = Enabled. This enables AMD-V and allows the CPU to function in a hypervisor.
The second setting was Advanced -> Onboard Devices Configuration -> USB power delivery in Soft Off state (SS) = Disabled. This fixes the problem with the power button not working as discussed here: Earth leakage hack.
Man, back on Windows for my new studio computer ‘verve‘. Needed to figure out how to edit C:\Windows\System32\drivers\etc\hosts and that was certainly more difficult than it needed to be.
In the end I used “Method 3” over here to add an “Open in Notepad (Admin)” item to my shell context menu:
Happy New Year! Best wishes to all my friends for 2024.
I have this weird problem with my new studio computer ‘verve‘. When I press the power button, it doesn’t turn on. It does have 15 USB cables plugged into it, and quite a number of those are powered, which seems to affect the system.
The power for most of the devices on my bench goes through a PowerShield Defender 1600VA UPS battery, and then through an Arlec PB91 Residual Current Device (RCD).
The RCD has a test feature so you can press the button on the RCD and it will trip the safety which will disconnect the power. If I do this most of the equipment on my bench will turn off (but, importantly, not my workstation ‘verve’) including all the powered USB devices which are interfering with my computer.
After I trip the RCD I can power on my computer, and then once it’s powered on I can reset the RCD and bench power is restored. It’s a bit fiddly but at least it works!
First: Settings -> Configure Konsole -> General -> Show window title on the titlebar (checked)
Then: System -> Configure Konsole -> Profiles -> [Default] -> Edit… -> Tabs:
Then you need this config and these two shell functions in your .bashrc:
# 2023-12-29 jj5 - if not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac
# 2023-12-29 jj5 - set the Konsole window title
echo -ne "\033]2;$USER@$HOSTNAME\007" >&2
# 2023-12-29 jj5 - intercept ssh and sudo commands to reset window title on exit:
ssh() {
/usr/bin/ssh "$@"
echo -ne "\033]2;$USER@$HOSTNAME\007" >&2
}
sudo() {
/usr/bin/sudo "$@"
echo -ne "\033]2;$USER@$HOSTNAME\007" >&2
}
Well, this took me a few hours to figure out.
If you’re going to be transferring large files using file.managed in your salt state, make sure you specify show_changes: False, otherwise salt will start trying to boil the ocean and calculate the unified diff of your enormous files.
The clue that this is the problem you're having is if one of your CPU cores pegs at 100% and your state doesn't apply in a reasonable amount of time (minutes, I guess).
Also you probably want to make sure you're not trying to use your large file as any sort of template. By default file.managed will assume no template, which is what you want for large files that aren't templates. I've never used large files which are templates, but I suspect if you tried that you'd have a bad time.
My good friend Dubz shouted me another round of Silicon Chip books as can be seen here. I now own all the books which have been marked and I’ve pretty much purchased everything that was left.
For the past month or so I’ve had this intermittent problem where chromium would start crashing and would keep crashing every time I tried to start it until I rebooted.
Today I ran chromium under strace and straightaway discovered that it was trying to use shared memory in /dev/shm and it couldn’t because there was no space left.
There was no space left because I had PHP’s xdebug writing dump files there. I’ve just disabled xdebug while I’m not using it and after clearing out its old files I can now run chromium again.
I added a note about this to my debugging notes for in case this or something like it happens to me again.
There are a couple of decent looking ebook bundles available via Humble Bundle at the moment:
I found this kickass resource: Super Nintendo Development Wiki. See for instance Schematics, Ports, and Pinouts.
One of my YouTube viewers Max donated some stuff to the channel today. How cool is that!? Expect to see some Nintendo awesomeness in the near future. <3
ChatGPT explains “kebab”:
ChatGPT 4
User
please explain shish kebab, doner kebab, and the etymology of the word “kebab”ChatGPT
Shish Kebab and Doner Kebab are two popular dishes that have their roots in Middle Eastern and Turkish cuisine, respectively. They are both variations of the broader concept of “kebab.”Shish Kebab: This dish consists of small pieces of meat, often lamb, beef, chicken, or fish, that are skewered and grilled. The term “shish” refers to the skewer. Vegetables like bell peppers, onions, and mushrooms are also sometimes skewered and cooked alongside the meat. Shish kebabs are known for their smoky flavor and are commonly served with rice, salad, and various dipping sauces.
Doner Kebab: Originating from Turkey, “doner” kebab is made of meat cooked on a vertical rotisserie. The term “doner” means “rotating” in Turkish. Traditionally, lamb is used, but chicken and beef are also common. The cooked meat is then sliced off and served in a flatbread or pita, often accompanied by salads, vegetables, and sauces like yogurt or tahini.
The Etymology of “Kebab”: The word “kebab” is believed to have originated in the Middle East, and its first known mention dates back to a Turkish script of the 14th century. It likely stems from the Arabic word “kabāb,” which originally referred to fried meat, not grilled. Over time, the meaning evolved to refer to meat cooked over an open flame or on a skewer. The term spread with the expansion of the Ottoman Empire, adapting to various languages and culinary traditions. The concept of cooking meat on skewers is ancient, with evidence suggesting that such cooking methods were used in the prehistoric times. The popularity and variations of kebab dishes are a testament to their versatility and enduring appeal in different cultures around the world.