<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Claudio Cambra on Medium]]></title>
        <description><![CDATA[Stories by Claudio Cambra on Medium]]></description>
        <link>https://medium.com/@claudio.cambra?source=rss-e2bc2ee656ce------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*AukkGj649DXrJBXTCY-Xmw.jpeg</url>
            <title>Stories by Claudio Cambra on Medium</title>
            <link>https://medium.com/@claudio.cambra?source=rss-e2bc2ee656ce------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:18:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@claudio.cambra/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Troubleshooting Manjaro Linux on your 2019 HP Omen 15 gaming laptop (August 2020)]]></title>
            <link>https://medium.com/@claudio.cambra/troubleshooting-manjaro-linux-on-your-2019-hp-omen-15-gaming-laptop-august-2020-c570ced15ca8?source=rss-e2bc2ee656ce------2</link>
            <guid isPermaLink="false">https://medium.com/p/c570ced15ca8</guid>
            <category><![CDATA[hp]]></category>
            <category><![CDATA[troubleshooting]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[laptop]]></category>
            <dc:creator><![CDATA[Claudio Cambra]]></dc:creator>
            <pubDate>Sat, 08 Aug 2020 16:37:02 GMT</pubDate>
            <atom:updated>2020-08-14T15:53:02.168Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KSnyz6U20HqQAAkuEzWOQg.png" /><figcaption>Bliss.</figcaption></figure><p>So you bought yourself a new gaming laptop. That’s great. But you were just about to install Windows on it. Not so great. Then you decided you would give this new OS everybody is talking about a try. Now, that’s even better.</p><p>Unfortunately, certain manufacturers are a lot less inclined to make their hardware play nice under Linux than others. When I tried to install Manjaro on my 2019 HP Omen 15, I was immediately met with a host of issues. That’s okay though — with just a little bit of elbow grease (and a few quick terminal commands) you can get everything working even better than on Windows.</p><h3>Issue 1: WTF happened to my sound?</h3><p>Some newer laptops use digital microphone arrays to pick up your screaming during a match of Counter Strike. Unfortunately, support for this is not available out of the box. This shouldn’t be the case in a few months, but for now all you need to do is punch in a few terminal commands and you’ll be ready to go.</p><p>These are taken from the tutorial <a href="https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/PulseAudioFromGit/">here</a> as well as from various posts in the Manjaro community forums, an insanely useful resource for troubleshooting.</p><p>First we are going to check what kernel version you’re on. You can find this by:</p><ul><li>Opening the <em>System Settings</em> app.</li><li>Under the <em>Manjaro</em> section, click on <em>Ker</em>nel.</li><li>Here are the available kernels. <br>As of writing, the latest stable kernel is version <em>5.7.9</em>, and that’s the one you want to click and install (that is, if you’re not running it already.)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8Z_QjjpR-T7OlWRcJ62uw.png" /><figcaption>Kernel version 5.7.9 is locked and loaded.</figcaption></figure><p>Then you will need a cute little package called <em>sof-firmware</em> which will enable both your internal audio and microphone array. You can get this through Manjaro’s application manager Pamac, or by pasting the following command into the terminal:</p><p>sudo pacman -S sof-firmware</p><p>Let it do its thing. Now, we need to install a developmental version of Linux’s audio server <em>PulseAudio</em> that works with this driver package. We will need to build it from its source code, and while that may sound scary, all you need to do is stick to the following terminal commands.</p><p>First, open a terminal window and download the source code onto your computer using this command:</p><pre>git clone <a href="https://gitlab.freedesktop.org/pulseaudio/pulseaudio.git">https://gitlab.freedesktop.org/pulseaudio/pulseaudio.git</a></pre><p>This will create a new folder with the name “pulseaudio”. To enter this folder in your terminal, punch this command in:</p><p>cd pulseaudio</p><p>Once that’s done, we are going to run some commands to build PulseAudio:</p><pre>./bootstrap.sh<br>make</pre><p>Let each command do its thing. It might take a while. Once they both finish, all we need to do is install PulseAudio, which can be done with:</p><pre>sudo make install<br>sudo ldconfig</pre><p>Reboot your system, and TA-DA! You should have working audio and microphones on your laptop.</p><h3>Issue 2: I installed graphics drivers and now everything looks HUGE. Why are all the menus, applications, and fonts so massive?!</h3><p>Nvidia drivers choose to screw with your system’s DPI settings, but luckily this is a simple fix. We’re going to have to use the terminal, though, so pay attention to the commands below!</p><ul><li>Open up your terminal and paste this into it: <br>sudo vim /etc/X11/mhwd.d/nvidia.conf<br>This will open up a text editor that works through the terminal.</li><li>Use the arrow keys to scroll down until you find the line <em>Section “Monitor”</em>.</li><li>Now, press the ‘i’ key on your keyboard. This will put the text editor into <em>INSERT</em> mode.</li></ul><p>From this point on, take care — touch something that shouldn’t be touched, and you might break your system! If you make an accident, however, it’s not a huge deal: just make sure you hit the colon ‘:’ key and type ‘q’ (:q) and you will exit the text editor without any changes being saved.</p><ul><li>Above the <em>EndSection</em> line, add a new line and type: Option “DPI” “96x96”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*QuoEDmnSUgsf-FQvbwUNmw.png" /><figcaption>Your Section “Monitor” should look something like this.</figcaption></figure><ul><li>Press the colon ‘:’ key and write ‘wq’. On the bottom of your screen you should see ‘:wq’. This will save your changes and quit the text editor.</li><li>Reboot your PC and voila, everything is back to a normal size.</li></ul><h3>Issue 3: now everything looks a little small…</h3><p>That’s okay. We can now change your DPI settings into something more reasonable.</p><ul><li>Open the <em>System Settings</em> app.</li><li>Under the <em>Hardware</em> section, click on <em>Display and Monitor</em>.</li><li>This should default to opening <em>Display Configuration</em>. Find <em>Global scale</em> and set it to a setting you feel comfortable with — for me, that was 125%.</li><li>Reboot and enjoy your human-sized interface.</li></ul><p>This will change everything on your desktop. Your login screen on boot-up, handled by SDDM, will still however be sized for ants. To fix this we will use <em>vim</em>, the terminal text editor, again.</p><ul><li>Open the terminal.</li><li>Paste the following command in: sudo vim /etc/sddm.conf</li><li>Use the arrow keys to scroll down until you find the line <em>[X11]</em></li><li>Now, press the ‘i’ key on your keyboard. This will put the text editor into <em>INSERT</em> mode. Again, be careful when you do this.</li><li>Below the last line of the section, add a new line and add this text: ServerArguments=-dpi 125</li><li>Press the colon ‘:’ key and write ‘wq’. On the bottom of your screen you should see ‘:wq’. This will save your changes and quit the text editor.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/1*ItCxZf3rXC9ZhqDRTpfLDA.png" /><figcaption>This is what the [X11] section should look like in /etc/sddm.conf</figcaption></figure><p>From now on your login screen will be human-sized too.</p><h3>Issue 4: I have a high refresh-rate screen but even after installing my graphics drivers my desktop isn’t running at 144fps/240fps!</h3><p>Kwin, a component of KDE Plasma, fails to properly detect the refresh rate of high refresh rate displays. The fix for this is quite easy, however.</p><ul><li>Open Dolphin (the file browser) and press CTRL+H which will show the hidden folders in your Home directory.</li><li>Go to the folder <em>.config</em> and open the file <em>kwinrc</em>.</li><li>Under the <em>[Compositing]</em> section, add a new line with the following text:</li><li>MaxFPS=240 -- the number should match your refresh rate.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P5rW-8_R2I4zUqgKihFXjQ.jpeg" /><figcaption>Your file should now look something like this.</figcaption></figure><ul><li>Save the file, and restart your computer.</li></ul><p>After this is done, you can enjoy the buttery smoothness of Plasma.</p><p><a href="https://www.reddit.com/r/kde/comments/brsmqc/gnome_still_handles_highrefresh_rate_monitors/"><em>Credit to this reddit post.</em></a></p><h3>Issue 5: I want to enjoy the buttery smoothness of KDE Plasma, but it keeps stuttering!</h3><p>This is an issue with Plasma’s Vsync settings. To fix this:</p><ul><li>Open the <em>System Settings</em> app.</li><li>Under the <em>Hardware</em> section, click on <em>Display and Monitor</em>.</li><li>Under the <em>Display and Monitor</em> panel, click on <em>Compositor</em>.</li><li>Find <em>Tearing prevention (“vsync”)</em>, click on the drop-down menu, and select <em>Never</em>.</li><li>Enjoy Plasma’s buttery smoothness.</li></ul><h3>Issue 6: Great, everything is now buttery smooth. Except Firefox, which feels like it’s still scrolling at a lower refresh rate.</h3><p>Yeah, we have to change some settings there too. This one is easy, though.</p><ul><li>Open up Firefox and type <em>about:config</em> in the web browser’s search bar.</li><li>Click <em>Accept the Risk and Continue</em>.</li><li>In the website’s search bar, type <em>gfx.webrender.enabled</em>.</li><li>Double click <em>false</em>, which should turn into <em>true</em>.</li><li>Close Firefox and reopen it.</li><li>Enjoy buttery smoothness.</li></ul><h3>Okay. Everything is working now. But that seemed like a lot of trouble to go through.</h3><p>Sure, Linux distributions take a bit of time to adapt to the newest hardware that comes out as its community of volunteers and enthusiasts works to get everything working. But it’s not like you have to break your back to get stuff working here: all it took us was a few commands and menu items here and there. Within a few months, these issues will have likely been resolved.</p><p>In the meantime, these fixes exist. So you can still enjoy gaming on your laptop without being forced to use a proprietary, bloated, and privacy-violating operating system.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c570ced15ca8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 things I learnt as an intern, or how to avoid fetching Tim’s coffee]]></title>
            <link>https://medium.com/@claudio.cambra/4-things-i-learnt-as-an-intern-or-how-to-avoid-fetching-tims-coffee-bcdbd0cb110c?source=rss-e2bc2ee656ce------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcdbd0cb110c</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Claudio Cambra]]></dc:creator>
            <pubDate>Fri, 06 Sep 2019 14:31:34 GMT</pubDate>
            <atom:updated>2019-09-06T14:31:34.182Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4AURSdz77Hocss1n2A7Pug.jpeg" /></figure><h4>My last day at Codethink was on Friday, August 30th.</h4><p>It was the last day I hammered away at the keyboard of a Thinkpad, on a table covered in the dozens of yellow Metrolink tram tickets I’d collected over my 3 months in Manchester.</p><p>That was a week ago. I swapped 7.30AM alarms and brisk walks to Cornbrook Tram Station for 12PM wake-ups and bleary-eyed trips to the fridge for the glass of milk I call breakfast. Not that I’m complaining — I was never fond of wrestling with my umbrella on the cold, damp walks to the tram — but sitting in bed with nothing to do while the hours tick-tock by has filled me with boredom.</p><p>Rather than queue up the umpteenth episode of Supernatural, then, I’ve decided to use one of my few marketable skills and write about my time at Codethink. Here are the things I learnt there.</p><h3>You might get used to 7.30AM alarms, but you’ll never get used to 5 hours of sleep</h3><p>Late sleepers take note: it’s possible to get up early. But it’s impossible to make it through an 8-hour work day, 5 times a week, on under 6 hours of pillow-time.</p><p>This was my first wake-up call, and yes, that pun was absolutely intentional. Part of the shift from a student life to a -slaving- working life is learning from your parents; that means going to bed early and getting up early, just like mom and dad.</p><p>Coffee will become an indispensable ally. That’s assuming you haven’t already developed a caffeine addiction during exam season.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sOm4ZwU3lkh26n0vmzxktg.jpeg" /><figcaption><em>I take my coffee black, no sugar. No water, either.</em></figcaption></figure><h3>Things are usually the way they are because reasons</h3><p>By the end of my very first week, I had already developed a laundry list of complaints about the way things were done at my new workplace. My supervisor, Tim Pockney, had to listen to me rant and rave about all of them. Why does the website look like *that?* Why do we not have a Facebook page? Why, in the name of all that is holy, *do we have to use GitLab to upload new blog posts instead of a tool like Wordpress?*</p><p>That last one still grinds my gears. But now I know the reasons why all of those things are the way they are, and it’s not due to incompetency. It’s usually the case that:</p><p>A) there are more pressing issues that take priority, or <br>B) people have a set of reasons for doing things (or using certain tools) the way they do.</p><p>Poor Tim was keenly aware of each issue I raised; but one has to weigh the benefit of pulling a programmer off a client’s project for the sake of updating the website, whether the time invested in setting up a Facebook page will lead to acquiring new clients, or, and I say this through gritted teeth, whether the convenience of using WordPress is worth dealing with its many security vulnerabilities.</p><p>In the eyes of people far more experienced, far more business-savvy, and in far higher positions in the company, these trade-offs were simply not worth it. That’s not to say that the feedback was not appreciated — in fact, most of them agreed to some extent with the problems I raised, even if they did not agree with the solutions — but it’s important to recognise that things are usually the way they are for a number of very good reasons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*IrepWSMHcvV98ZDiKTf7Dg.jpeg" /></figure><h3>Bring more than just your ass to work</h3><p>Chances are, unless you work a job straight out of Dirty Jobs, you were employed not just for the sake of filling a role but to also provide value to the company in question.</p><p>Pumping out text, code, or numbers is just one of the ways you provide value to your employer, and more often than not it’s not a particularly effective way of doing so. /That’s not to say you should stop doing your job,/ but you are far more valuable as an employee that contributes to and builds upon the way the company conducts its business. This could be as simple as giving your superiors ideas that could increase productivity, efficiency, or income, even if these improvements are marginal.</p><p>My ‘big brain’ idea was to post the articles I wrote for Codethink on Reddit, which resulted in the number of average monthly unique visitors to Codethink’s blog growing over twofold in respect to the prior 5 months of 2019. Before patting myself on the back too hard, I must give other factors their due credit; Tim’s expertise with LinkedIn and Twitter was one contributor to those figures, and the inroads he’d made with the company blog in early 2019 certainly helped grow the website’s traffic.</p><p>I will say, though, that something as simple as posting articles on Reddit provided a noticeable boost to traffic — and it is thanks to ideas like these that Tim grew to see me as more than just a whiny, snotty, know-it-all intern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*ISHFQpMKJrhkKuaa7j98_A.jpeg" /></figure><h3>Bigger isn’t always better (or Micro =/= soft 😉)</h3><p>I’ll preface this by saying that Codethink is not a small company. By the time I had left it employed over 100 people.</p><p>But some of the other companies I’d applied to intern for had employee counts in the hundreds of thousands. That’s a lot. One of them had almost as many employees as my hometown, and I’ll let you figure out which company this is by yourself.</p><p>Sure, those names would look very impressive on your CV. Trying to be heard at such a company, however, is like trying to make small talk with someone at a Metallica concert. The chances of you making any significant contribution as an intern are very, very small.</p><p>When I got plopped into the Sales office at 35 Dale Street, that was because there wasn’t such a thing as a Marketing department — me and Tim were pretty much it. That’s scary as hell, and rewarding as hell, for pretty much the same reason: your work is much more visible. The good thing is if you do it well, the compliments, job opportunities, and recognition start to pile up in your inbox.</p><p>At least that’s what I’ve been told. My mom says my work is very good anyway.</p><h3>One last thing</h3><p>I’ve cracked a lot of genuinely unfunny jokes over the last couple of paragraphs, and I apologise for wasting your time. But I must also extend my apologies to everyone in Codethink’s Manchester offices, and especially to the Sales office, my fellow interns, and Tim, who had to endure me the most. I’ll miss bothering you very much, and I’ll miss the tea and biscuits in the break room even more.</p><p>Oh, and I almost forgot. Thanks for the internship! ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcdbd0cb110c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>