Language Selection

English French German Italian Portuguese Spanish

My First 24 Hours With openSUSE Tumbleweed

Filed under
Reviews
SUSE

My understanding is that elementary OS and openSUSE Tumbleweed couldn't be more different. The former is designed to be lean, minimalistic and beginner-friendly, while the latter has a wealth of software bundled in (its 2x larger ISO download size makes that obvious), allows users to choose multiple desktop environments during the installation and can be heavily customized.

[...]

By default, I don't expect to have issues with Linux OS installers. The ones I've reviewed -- such as Deepin and Pop!_OS -- have been attractive, intuitive affairs. For those of you who haven't tried Linux in years, they're incredibly simple compared their past iterations.

The standard graphical installer for openSUSE Tumbleweed, however, threw me a curveball.

Advancing through initial options like network setup, region, packages and desktop environment was straightforward. But then as the install process began I was met with puzzling "Wrong Digest" messages.

Read more

More in Tux Machines

Graphics: GNOME Meets Panfrost, Rob Clark, and More on Radeon Navi

  • GNOME meets Panfrost
  • GNOME Meets Panfrost

    Bring-up of GNOME required improving the driver’s robustness and performance, focused on Mali’s tiled architecture. Typically found in mobile devices, tiling GPU architectures divide the screen into many small tiles, like a kitchen floor, rendering each tile separately. This allows for unique optimizations but also poses unique challenges. One natural question is: how big should tiles be? If the tiles are too big, there’s no point to tiling, but if the tiles are too small, the GPU will repeat unnecessary work. Mali offers a hybrid answer: allow lots of different sizes! Mali’s technique of “hierarchical tiling” allows the GPU to use tiles as small as 16x16 pixels all the way up to 2048x2048 pixels. This “sliding scale” allows different types of content to be optimized in different ways. The tiling needs of a 3D game like SuperTuxKart are different from those of a user interface like GNOME Shell, so this technique gets us the best of both worlds! Although primarily handled in hardware, hierarchical tiling is configured by the driver; I researched this configuration mechanism in order to understand it and improve our configuration with respect to performance and memory usage. Tiled architectures additionally present an optimization opportunity: if the driver can figure out a priori which 16x16 tiles will definitely not change, those tiles can be culled from rendering entirely, saving both read and write bandwidth. As a conceptual example, if the GPU composites your entire desktop while you’re writing an email, there’s no need to re-render your web browser in the other window, since that hasn’t changed. I implemented an initial version of this optimization in Panfrost, accumulating the scissor state across draws within a frame, rendering only to the largest bounding box of the scissors. This optimization is particularly helpful for desktop composition, ideally improving performance on workloads like GNOME, Sway, and Weston.

  • MSM DRM Adding Snapdragon 835 / Adreno 540 Support In Linux 5.3

    Freedreno founder Rob Clark, who is now employed by Google to work on open-source graphics, has sent in the batch of MSM Direct Rendering Manager driver changes to DRM-Next ahead of the Linux 5.3 kernel cycle.  Notable to this feature update is Adreno 540 / Snapdragon 835 support. The Snapdragon 835 has been out since 2016 and has also been found in some of the Snapdragon laptops. The Adreno 540 supports Vulkan 1.1, OpenGL ES 3.2, and its quad-core GPU runs at 710/670MHz with 512 ALUs, 16 TMUs, and 12 ROPs. 

  • Radeon Navi Support Pending For RadeonSI OpenGL Driver With 47k Line Worth Of Changes

    Last week AMD posted more than 400 patches providing the AMD Navi support within their AMDGPU DRM kernel driver while this week has brought dozens of patches amounting to 4,293 lines as a patch for their RadeonSI Gallium3D driver in order to provide OpenGL support on these next-gen GPUs being introduced next month as the Radeon RX 5700 series.  Well known AMD open-source developer Marek Olšák posted the Mesa patches yesterday for providing this initial Navi (10) support to Mesa. As is the case, AMD's Navi enablement is focused on the RadeonSI Gallium3D driver and not the unofficial/community driven RADV Radeon Vulkan driver also within Mesa. The RADV Navi support will be left up to those "community" contributors from the likes of Red Hat, Google, and yes the independent community members. 

Security: Updates, Devices With Default Credentials and Open Ports, Regulatory Compliance and Red Hat Security and More

  • Security updates for Wednesday
  • This Malware Created By A 14-Yr-Old Is Bricking Thousands Of Devices [Ed: "It's targeting any Unix-like system with default login credentials," the original source says.]

    A new malware called Silex is on its way to brick thousands of IoT devices. The malware has been developed by a 14-year old teenager known by the pseudonym Light Leafon. The malware strain is inspired by the infamous malware called BrickerBot, which is notorious for bricking millions of IoT devices way back in 2017.

  • New Silex malware is bricking IoT devices, has scary plans
  • Regulatory Compliance and Red Hat Security

    In today’s interconnected world, data security has never been more important. Virtually every industry, from healthcare to banking and everything in between, has rules for how businesses handle data. Failure to meet regulatory compliance spells serious trouble for your business. Depending on the severity of the infraction, you could end up with fines, loss of reputation/revenue, or jail time. Fortunately, these consequences are avoidable with a few proactive steps. By training your IT staff to keep your systems secure, you can prevent harmful or costly data breaches.

  • Using Quay.io to find vulnerabilities in your container images

    You’ve created a container image that has all the packages that you and your team need to do something useful, or maybe you’ve built a public image that anybody can use. But, what if that image contains packages with known security vulnerabilities? Regardless of the severity of those vulnerabilities, you’ll want to learn more and take steps to mitigate them as soon as possible. Fortunately, your team uses Quay.io* as your registry. When you push an image to Quay.io, it automatically runs a security scan against that image.

Valve release an official statement about the future of Linux support, they "remain committed" to Linux gaming

After the recent upset caused by Canonical's plan to drop 32bit support in Ubuntu, then to turn around and change their plan due to the uproar caused by it, Valve now have a full statement out about their future support of Linux gaming. Firstly, to get it out of the way, there's nothing to worry about here. Valve said they "remain committed to supporting Linux as a gaming platform", they're also "continuing to drive numerous driver and feature development efforts that we expect will help improve the gaming and desktop experience across all distributions" which they plan to talk more about later. On the subject of Canonical's newer plan for Ubuntu 19.10 and onwards in regards to 32bit support, Valve said they're "not particularly excited about the removal of any existing functionality, but such a change to the plan is extremely welcome" and that it "seems likely that we will be able to continue to officially support Steam on Ubuntu". Read more Also: Steam Play updated as Proton 4.2-8 is out, DXVK also sees a new release with 1.2.3

Audio and Video: TLLTS, FLOSS Weekly, ArchBang, Ubuntu and Dirk Hohndel