Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited

Everything posted by Chunchunmaru_

  1. You got a black screen because as you said the X server was not installed, so you were in a netinstall. Or you were missing the X.org vesa driver, which is what you are currently using now, it couldn't work before because your AMD driver is not being used. Then problem in your setup is, obviously the firmware. The one you downloaded may be buggy or outdated, try this one https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20190815.tar.gz which comes directly from upstream. Just be careful to remember which files you copied in that folder, typically you want to touch your system files only with packages
  2. It should be sufficient, but why do you installed the firmware package via deb? doesn't pureos offer the package from their own repository? that should be sufficient
  3. You are missing the GPU firmware, you need the raven_gpu_info.bin in /lib/firmware/amdgpu
  4. Cursed, do not open


  5. what does lsmod show? it should report the amdgpu driver, use lsmod | grep amdgpu then you should also check the X.org logs, in /var/log/Xorg.*.log
  6. I think the best way to try this is compiling a simple binary to test? Even though, you could just use -march=native to be sure to have optimized binaries for your cpu
  7. Yes, you just need to know for which firmware the driver is looking for, copy it from /lib/firmware folder then again in the PureOS /lib/firmware one
  8. Are you talking about the firmware or the driver? You need those two in order to get a working chip. You can download the firmware by extracting it on the internet or by yourself on a working system (even a Windows one) Then it takes place in /lib/firmware but the file name is specific on how the driver is configured, check with "dmesg" any errors and which firmware is the driver looking for
  9. Aliexpress is accurate as always.
    Didn't expect it to be THAT blue


    1. Chunchunmaru_


      (It's also horizontally inverted oh no)

  10. If you need to know probably you should start reading the official Microsoft documentation if you are interested in deploying their implementation https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/ad-ds-getting-started Other free (limited) AD alternatives can be made with Samba or OpenLDAP
  11. He was not talking about kernel upgrades but system upgrades in a server which is totally unrelated to this (also livepatch is not something that should be used on a server)
  12. This really depends. On desktop it's totally harmless, issues can only happen when the specific service you provide has deprecated some config options, or it you are not separating config files you will be prompted to replace configure files (pretty common for ldap) A good practice obviously is splitting most services you can using containers or virtual machines minimizing an eventual negative impact, which anyway a system administrator should know the effects before upgrading anything checking eventual bugs or procedures and the same can be said for Windows (which anyway in my company we have an insane amount of problems on clients rather than Windows servers)
  13. This is a bit strange to say, what specific Linux release are you talking about? Mainline kernel vulnerabilities? LTS? Because obviously an open source project like the Linux Kernel has more "security vulnerabilities", every kernel release is exposed to everyone and it doesn't mean every Linux build is affected Any kernel which isn't an LTS release shouldn't even be considered speaking about servers
  14. It's more about finding vulnerabilities rather than the classic "user" malware like this one Also luckily enough, the security teams working on Linux distributions are a steap forward and system administrators should be quick to apply the latest patches
  15. It's just not Linux, but web servers in general (and mostly in the cases where the web code is rotten and exposes the server to vulnerabilities)
  16. check the bios settings and change the video graphics card option to "Optimus"
  17. Major bugs I can think are only related to AMD chipset where the sound subsystem audio layer is bugged since years, the microphone crackles on every AMD based platform. It's worth saying they are close to solving it in the last year. As for the overclocking, there is sadly no solution to it, Linux is just not windows and not the same overclocking settings applies (considering also that hardware vendors support overclocking from the BIOS only for Windows)
  18. Hi, my company decided to have me configure some XG Firewalls to our customers and I'll attending the Sophos certified architect three days course, and now I'm completing the online assessment. But I do not completely understand how all of that works, what I'll be doing in those three days? Is there another exam to take? Is it hard? Is the minimum score 80% like the online assessment? And again, are there any laboratory exercises? I also heard they will let you use the documentation
  19. is it going to lose Linux support like the other things they touched
  20. Oh god that translation doesn't look correct at all *reads hidden contents* Yes.
  21. Ok so I basically completely discharged it to 0% first, now I'll wait for a Dell answer from facebook
  22. I own an XPS 15 9550, that after 2 years the battery only lose the 22% of the capacity, but the real issue here is that it become suddenly swollen. It's a known defect, and a friend of mine who got the same model got his battery replaced out of warranty. This is what it should look like in a normal state This is mine Do you know if they still replace those batteries for free? But first another question, I immediately removed this battery and put it out my home, I don't want it to blow, do I need to worry anyway? Should I put it back? It still works, after all.
  23. Personally I workarounded the error 43 with passing the actual NVIDIA card bios, previously dumped, then obviously the kvm_hidden state on the libvirt settings There was also a guide on this forum here