Reinstalling kernel went smooth after editing vconsole.conf and setting KEYMAP=ro_std
@joekamprad I guess you are right,
sudo localectl set-keymap --no-convert ro_stdwould do the trick even better than just editing vconsole.conf (in case there are other places where the KEYMAP is being stored)
@manuel thanks for your input. your questions lead me in the right direction.
HOOKS="base udev autodetect modconf block keyboard keymap filesystems fsck"
Been doing a bit of research starting off from your question above (googled “HOOKS keymap”), and found
/etc/vconsole.conf to have the following content:
$ cat /etc/vconsole.conf KEYMAP=ro-std FONT=ter-v14b
After even more research (googled “vconsole.conf KEYMAP”) :
$ localectl list-keymaps | grep ro croat cz-lat2-prog dvorak-programmer euro euro1 euro2 mac-euro mac-euro2 ro ro_std ro_win sk-prog-qwerty sk-prog-qwertz
Apparently there is a typo in vconsole.conf as it requests ro-std instead of ro_std (this was automatically added during language install I guess, so must be a bug)
I’ve noticed lately this warning issued during kernel update. While the system is functional I was wondering if there is something I can do to stop the warning from ocuring.
I’m concerned about the line
cannot open file ro-std.
Here is a screenshot of my keyboard settings:
And here is the
LANG=en_US.utf8 LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE=en_US.UTF-8 LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL=
`.-/::/-`` .-/osssssssso/. :osyysssssssyyys+- OS: Antergos `.+yyyysssssssssyyyyy+. Kernel: x86_64 Linux 4.19.24-1-lts `/syyyyyssssssssssyyyyys-` Uptime: 34m `/yhyyyyysss++ssosyyyyhhy/` Packages: 1115 .ohhhyyyyso++/+oso+syy+shhhho. Shell: bash 5.0.0 .shhhhyso-/+++/-ss+++yyy+shhhhs. Resolution: 3520x1080 -yhhhh-/+++++/-ssso+++yyys+ohhddy: DE: XFCE4 4.12 -yddhhy-/+++/-syyss++++yyyyooyhdddy- WM: Xfwm4 .yddddhso++osyyyyys+++++yyhhsoshddddy` WM Theme: Cyanogen `odddddhyosyhyyyyyy++++++yhhhyosddddddo GTK Theme: Numix-Frost-Light [GTK2] .dmdddddhhhhhhhyyyo+++++shhhhhohddddmmh. Icon Theme: Papirus-Maia ddmmdddddhhhhhhhso++++++yhhhhhhdddddmmdy Font: Segoe UI 10 dmmmdddddddhhhyso++++++shhhhhddddddmmmmh CPU: Intel Core i5-3317U @ 4x 2.6GHz [55.0°C] -dmmmdddddddhhyso++++oshhhhdddddddmmmmd- GPU: Mesa DRI Intel(R) Ivybridge Mobile .smmmmddddddddhhhhhhhhhdddddddddmmmms. RAM: 2221MiB / 11631MiB `+ydmmmdddddddddddddddddddmmmmdy/. `.:+ooyyddddddddddddyyso+:.`
@rpallen in my bios there was a “Legacy and UEFI” entry, allowing any of them to be booted (citing from memory here). The mixed mode I was advising against.
USB ports are usually blue (the plastic inside the port is blue instead of the customary white or black).
See here: http://www.euask.com/topic/3768-How-to-tell-USB-20-from-USB-30-ports
The only way I managed to get past a similar issue was to boot from the live Antergos USB, format all Linux partitions, not touching /boot and /boot/efi and reinstall Antergos. I’ve tried all sorts of uefi recovery solutions first, but nothing worked. Not saying you will not eventually solve it (as I was trying it myself with just google).
Also something to keep in mind, on my Laptop, the system would only boot from the USB2 port, not from the other ports. Also, when using a mouse on USB3 port and a USB stick, one or the other would stop working. These are just some things I’ve stumbled upon that might, or might not apply yo your case.
What I would do in your case is to disable legacy and UEFI mode and keep just the UEFI mode in BIOS. You don’t want a mix of those, rather aim for a full UEFI system. It will simplify things in the long run and give you better performance.
Well, the love ended after seeing Budgie going down-river. Settings started to disappear, Budgie specific controls stopped working. In the end I abandoned it and after a bit of customization found Cinnamon to do exactly what Budgie was doing minus bugs +nice extra tools and ton-loads of support.
I’ve been using Budgie happily for more than half a year now (resting after half a year of distro hopping). Antergos + Budgie being my first distro/DE combo that never made me look back at whatever else is out there.
Yesterday however, budgie wouldn’t run. It would try to launch but then I would be thrown back at the login screen. Luckily I also have Gnome installed so I can login into it and do my work.
I would however like to recover Budgie, as I like it and have customized it to fit my style and usage pattern.
The system is up to date, I think a recent update might have crashed the system. I always update everything that is being offered by the Update Center.
I have tried reinstalling budgie-desktop.
I have also tried running budgie-desktop from a tty with command
The output there is pretty verbose, I figure it would enlighten someone more knowledgeable than me, so I have captured all output into a file and have linked it here.
Anyone any clues how I can fix this?