Tag: Arch Linux

  • SBOX K-14 Unboxing: Is This €6 Keyboard Any Good?

    SBOX K-14 Unboxing: Is This €6 Keyboard Any Good?

    Can a €6 Keyboard Be Any Good? SBOX K-14 Unboxing and First Impressions.


    The SBOX K-14 is one of the cheapest new keyboards I could find. I purchased it from TechTrade for only €6.71, which made me curious about what such a low-cost keyboard could actually offer.

    I wanted to find out whether it could be used for gaming, writing OpenBootLab posts and basic everyday tasks, or whether its extremely low price would make it frustrating to use.

    My immediate reaction after removing it from the box was simple: this keyboard is unbelievably light. The plastic feels very cheap, and the entire body flexes significantly with little pressure. That was not completely unexpected for €6.70, but the amount of flex still surprised me.

    Build quality is only one part of the experience, however. The real question is whether the SBOX K-14 can still function as a usable keyboard despite feeling so inexpensive.

    Watch the complete SBOX K-14 unboxing below:


    The SBOX K-14 is a basic full-size wired keyboard designed for everyday computer use. According to the specifications listed by TechTrade, it offers:

    • 105-key full-size layout
    • Slovenian/Croatian key layout
    • Membrane switches
    • Rated lifetime of three million presses per key
    • USB 2.0 connection
    • 1.35-metre fixed cable
    • 5 V / 100 mA USB power
    • Dimensions of 445 × 156 × 22 mm
    • Weight of approximately 530 g
    • Official compatibility with Windows XP, Vista, 7, 8 and 10
    • 12-month warranty

    The official compatibility list appears dated and does not mention Windows 11 or Linux. However, as a standard USB keyboard, it should work as a plug-and-play input device on most modern operating systems. I tested it on Arch Linux and will cover the results later in the post.

    There is no backlighting, wireless connectivity, software suite or gaming-focused feature set. This is a conventional membrane keyboard focused on providing the most basic functionality at the lowest possible price.


    he SBOX K-14 has a traditional full-size layout with a function-key row, navigation keys, arrow keys and a numeric keypad. One positive aspect is its relatively compact outer frame. There is very little unnecessary plastic surrounding the keys, so it does not occupy more desk space than a full-size keyboard actually needs.

    Its construction immediately reveals where the low price comes from. The plastic feels very cheap, the keyboard is extremely light, and the chassis flexes significantly with little pressure. It does not feel particularly sturdy, although that is not entirely surprising for a keyboard costing only €6.70.

    There are fold-out legs underneath, allowing the keyboard to be raised to a more comfortable typing angle. However, it has no rubber feet to grip the desk. Combined with its low weight, this means the keyboard slides around with very little force. The underside also includes several drainage holes. These should allow small amounts of spilled liquid to pass through the keyboard instead of remaining trapped inside, although I did not deliberately test this feature.

    The permanently attached 1.35-metre USB cable also feels thin and inexpensive. It should be long enough for a typical desktop setup, but its durability will only become clear after longer use.

    Overall, the K-14 offers a sensible and space-efficient full-size form factor, but its materials, flex and lack of grip make it obvious that keeping the price as low as possible was the main priority.


    The SBOX K-14 uses membrane switches, and the keys feel very mushy when pressed. Despite that, they are reasonably responsive for normal typing, and the keyboard is more comfortable to use than its extremely cheap construction initially suggested.

    The plastic does not feel pleasant beneath the fingers and constantly reminds you that this is a €6.70 keyboard. The larger keys, including Space and Enter, feel and sound fairly average. They are not particularly good, but they also do not stand out as a major problem.

    I made a few typing mistakes while testing it, although the number of missed or incorrect presses was not bad enough to make the keyboard frustrating. With more time, I would probably become more accustomed to its feel.

    One of its strongest qualities is how quiet it is. The K-14 produces very little noise during normal typing, which could make it suitable for a shared room, a quiet office or late-night use.

    If this were the only keyboard I had, I could comfortably use it to write multiple OpenBootLab posts and complete everyday tasks. However, if I had more money available, I would choose something with better materials and a more precise typing feel.

    The video below demonstrates how the SBOX K-14 sounds during normal typing and when pressing several individual keys. No background music was added, allowing the keyboard itself to be heard clearly.


    I tested the SBOX K-14 with my main desktop running Arch Linux and with my laptop running Windows 11 Pro.

    The keyboard was recognised immediately on both systems. I only had to connect the USB cable, and it was ready to use within seconds. No drivers, additional software or manual configuration were required—which is exactly what I expected from a standard wired USB keyboard.

    All the keys I tested worked correctly, including the Slovenian and Croatian characters Č, Š, Ž and Đ. The numeric keypad and the rest of the full-size layout also worked without any problems.

    Although the product information only officially lists older Windows versions, the K-14 worked normally with Windows 11 Pro and Arch Linux during my testing. Its simple plug-and-play compatibility is one of the areas where this inexpensive keyboard delivers exactly what it should.


    I mainly play single-player games rather than competitive multiplayer titles, and for that kind of gaming, the SBOX K-14 is good enough.

    Basic movement and normal controls work without any major problems. However, when moving and pressing several keys very quickly, the keyboard can occasionally fail to register an input. This is unlikely to be a serious issue in slower single-player games, but it could become frustrating in fast or competitive titles where every keypress matters.

    The lack of rubber feet is also more noticeable while gaming. Because the keyboard is extremely light, it can slide across the desk during more intense moments.

    This is clearly not a gaming keyboard, and anyone who needs reliable multi-key input should look for something better. However, if the SBOX K-14 is the only new keyboard you can afford, it is still sufficient for casual gaming and everyday computer use.

    I am also writing this post on the K-14, which proves that it is usable beyond a short test. And if a particularly frustrating game ever causes it to meet an unfortunate end, at least replacing a €6.70 keyboard will not be too painful.


    So, can a €6.70 keyboard actually be any good? The answer depends entirely on what you expect from it.

    The SBOX K-14 feels extremely cheap. Its plastic is unpleasant, the chassis flexes considerably, the cable is thin, and the lack of rubber feet allows it to slide around the desk. The keys are also very mushy, and fast combinations are not always registered correctly.

    Despite those weaknesses, the keyboard is still functional. It is comfortable enough for writing, extremely quiet, compatible with both Arch Linux and Windows 11 Pro, and usable for basic tasks and casual single-player gaming. I even wrote this post using it.

    I would not choose the K-14 if I had enough money for a better keyboard. However, for someone who needs the cheapest possible new keyboard, a temporary replacement, or a spare for troubleshooting computers, it does the job.

    For €6.70, I cannot call it impressive—but I also cannot call it useless. It is exactly what it promises to be: an extremely cheap keyboard that works.

    Would you use a keyboard this inexpensive as your main keyboard, or would you keep it only as a spare?


  • Getting the Radeon R9 280X Working on Modern Linux

    Running a Radeon R9 280X on a modern Linux system sounds straightforward, but this old Tahiti GPU turned into one of the first real troubleshooting experiments on Mainframe.

    What started as occasional crashes eventually led me through different kernels, the legacy Radeon driver, AMDGPU, Vulkan and RADV before I arrived at the configuration I’m currently using.


    After installing Arch Linux on Mainframe, everything initially appeared to be working normally. The R9 280X was detected, the desktop worked and I could use the system without any obvious problems.

    Things started getting interesting when I began using the machine more heavily. I started experiencing seemingly random crashes where the graphical session would suddenly disappear and I would be thrown back to the login screen. At first, I wasn’t sure whether the problem was related to XFCE, the graphics driver or even the old hardware itself.

    Looking through the system logs eventually pointed me towards the GPU. The kernel was reporting graphics ring timeouts, VM faults and repeated GPU resets. One particularly telling message reported that VRAM had been lost following a GPU reset.

    Some of the messages recorded in the logs included:

    The crashes also appeared in connection with graphical processes such as Xorg and, during gaming tests, Steam’s steamwebhelper. At this point, the problem was clearly pointing towards the graphics stack rather than simply being an XFCE issue.


    Since the crashes appeared to be related to the graphics stack, one of the first things I wanted to test was whether the problem was specific to the current Arch Linux kernel. At the time, Mainframe was running the regular Arch kernel, so I installed the Linux LTS kernel to compare the behaviour without changing the rest of the system.

    After booting the LTS kernel, I checked which driver was actually controlling the R9 280X.

    The important output from the troubleshooting was:

    This immediately revealed an important difference. Under the LTS kernel, the Tahiti GPU had bound to the older radeon kernel driver instead of amdgpu.

    That created another problem. Vulkan through RADV was no longer working correctly. When I tried to test Vulkan, it failed with:

    This was important because I wanted Mainframe to be capable of running games through Steam and Proton. For this old AMD GPU, having working Vulkan support was therefore more than just an interesting experiment—it was something I actually needed.


    The LTS kernel gave me another useful clue. The R9 280X was capable of using AMDGPU, but the system was loading the older Radeon driver instead. Since I wanted working Vulkan support through RADV, I decided to explicitly tell the kernel which driver should handle the card.

    The R9 280X is based on AMD’s Tahiti architecture, which belongs to the Southern Islands generation. On this hardware, Linux can expose both the radeon and amdgpu kernel modules, so I needed to disable Southern Islands support in Radeon and enable it in AMDGPU.

    I did this by adding the following kernel parameters:

    Because Mainframe uses GRUB, I added these parameters to /etc/default/grub. My final configuration looked like this:

    Before regenerating the GRUB configuration, I also checked the file for syntax errors:

    After rebooting into the LTS kernel, I checked the GPU driver again. This time the result was exactly what I wanted:

    The R9 280X was now running on AMDGPU while using the LTS kernel. The next question was whether Vulkan and RADV were working correctly again.


    With the R9 280X now running on AMDGPU, the next step was to check whether Vulkan was working again. This was especially important for Mainframe because Vulkan is required by DXVK when running many Windows games through Steam and Proton.

    I tested the Vulkan installation using:

    This time, instead of the VK_ERROR_INCOMPATIBLE_DRIVER error I had encountered while using the Radeon driver, Vulkan successfully detected the R9 280X through Mesa’s RADV driver.

    The important part of the output showed:

    The device was also reporting Vulkan API 1.3 support, confirming that the old Tahiti GPU was now successfully running with the modern AMDGPU and RADV graphics stack.

    Seeing Vulkan working on a graphics card from this generation was one of those moments that reminded me why I started the Mainframe project in the first place. The R9 280X may be old hardware, but with the right Linux configuration it can still use a surprisingly modern graphics stack.

    TESTING STEAM

    The next test was Steam. Earlier, Deus Ex: Human Revolution Director’s Cut had failed to start because Proton and DXVK couldn’t find a usable Vulkan device while the card was running on the Radeon driver.

    After switching back to AMDGPU, Steam began building Vulkan shaders for the game, which was a good indication that RADV was now being detected correctly by the gaming stack.


    Mainframe is currently running the Linux LTS kernel with the R9 280X using AMDGPU and RADV. Vulkan is working again, and the system can use the modern Linux gaming stack despite the age of the GPU.

    I’m continuing to use and test the system to see how stable this configuration remains over time.

    Check back once in a while to see if anything changes.