Jump to content

Chunchunmaru_

Member
  • Posts

    452
  • Joined

  • Last visited

Everything posted by Chunchunmaru_

  1. Pretty much you ran into the main Ubuntu LTS issue, your hardware is too new. You are supposed to use the latest version of Ubuntu or even a development one for such new hardware, I'm even surprised you got video working. Linux drivers for that new hardware are available only in non-lts distributions, the issue here it's rather the slow driver cycle because hardware vendors primarily support Windows. You may try PopOS which has some patches for supporting new hardware, but honestly I don't remember, they got two distributions. I'm sure the situation would REALLY improve if you try Ubuntu 19.10 Eoan. Also, don't even try to use Nouveau (the open source driver installed by default) The first thing you should do is installing the Nvidia proprietary one through the driver manager right after installing your system. (which idk how you get it installed if you say it doesn't support nvme??)
  2. I hate making Postfix servers so much

  3. Android runs on a custom Java VM and the RAM allocated you see in Linux using htop isn't even remotely the same as the one you see on a Linux desktop. The android VM is ALWAYS allocating more memory for programs even if they don't use it
  4. Ubuntu, or some red-hat based distros like Fedora since some applications are more torwards supporting it.
  5. What is the need for using a different subnet, if I could ask? Couldn't you just bridge those interfaces? EDIT: Sorry, I didn't read carefully, but anyway couldn't bridging those two interfaces be the solution? Or maybe set those 3 on a different network (as long those 3 devices are the only present on the entire network, otherwise I suppose you have to configure the routes on the ISP router which is set as the default gateway)
  6. I can think of a VPN... Check if both your routers support it, you can choose IPSec or OpenVPN
  7. Obviously the latest windows update had to break something.

    1. lewdicrous

      lewdicrous

      "If it's not broken, it's not Windows" their slogan, probably.

  8. I never configured a dd-wrt so I don't know what specific settings to look for, btw yes it should it's just like a Linux host with a wireless interface connected to the main AP called wlan0, which will have the IP address and gateway configured like a normal host, then it has another interface, called eth0 where you connect, with another IP address range, and since the dd-wrt is already connected to the main AP it will see that interface as "directly connected" so will make the route for another network (first the main AP, then the internet) just make sure the gateway is configured as dd-wrt for clients connecting from eth0
  9. The default gateway must be the host on the same network which knows the route for other networks (because he is directly connected to another network), so for your dd-wrt which is connected to the main AP it would be the default gateway of the AP network for that interface, as for your hosts on the dd-wrt that should be the dd-wrt itself, just think of the dd-wrt with two interfaces, one that faces the main AP and the other one who faces your internal DD wrt hosts Your main AP should be already configured with the correct gateway, otherwise it wouldn't even get to the internet, and the dd-wrt itself with the interface connected to the AP should be good because it probably just got a DHCP address with the correct information I said DHCP pool because I assume you configured the addresses on the host you connect to the dd-wrt, which contains all that information such as the IP address you want to assign, DNS servers, default gateway, etc
  10. Have you set the default gateway on the dd-wrt? What is the DHCP pool used on the dd-wrt?
  11. You got pretty much unlucky with that Realtek chipset WIFI adapter, it's one of the few having issues with Linux because their drivers are not in mainline
  12. It's power delivery that supports charging up to 100W on both USB C and thunderbolt 3 ports, which uses the same socket, probably they are just the same https://www.usb.org/usb-charger-pd For example my Dell XPS does not support power delivery via the Thunderbolt 3 port at all
  13. High mouse DPI and low sens in game, because software sens causes laggy movements
  14. damn crickets don't you dare enter my room while I sleep

    1. Cyberspirit

      Cyberspirit

      Spiders: Oh cool, we are allowed in then, eh?

      xD

       

    2. Windows7ge
  15. Uhm... I probably understand why I have noticed you are using a Vega GPU, this is fairly new and Debian probably doesn't have the right kernel driver. Mint is based on an Ubuntu LTS and I imagine you are using Ubuntu 19.04 for your test, so the issue was probably about the kernel driver rather than the firmware
  16. Just following the gentoo documentation isn't a bad idea tbh, it's not that difficult once you know what is needed What was the problem?
  17. Could you give the logs again after you installed that firmware? Also what does "apt-cache search firmware" show
  18. just change the symlink for /sbin/init, but be sure to completely configure the init...
  19. I did, has some limitations though For now only Turing has no power draw when in "Optimus" mode, means it's basically useless for power save. Also, the only successful "optimus" tests I made were with glxgears and glxinfo, vkcube refused to load (but probably some 19.10 regression since it doesn't run at all) but any steam game i tried with or without Proton or OpenGL were still running on the Intel
  20. That thing just needs a good firewall
  21. Pretty much what it says... It's not going to work, why don't you just buy a certificate?
  22. 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
  23. 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
  24. You are missing the GPU firmware, you need the raven_gpu_info.bin in /lib/firmware/amdgpu
×