This is my first time messing with Linux so please forgive my ignorance.

I have an HP Elitebook 840 G8 that I’ve installed Ubi server on. I was trying to install a GUI on it, so I tried pulling the SLiM package from the web, but got "Temporary Failure resolving ‘Archive.ubuntu.com’.

This laptop doesn’t have an Ethernet Port, so I have to use a Microsoft USB-Ethernet dongle. But I haven’t been successful in getting that to work.

Is there a way for me to manually download the driver on a USB, then load it that way?

  • chi-chan~@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    6 months ago

    If you have NetworkManager installed (you should have), you can use nmtui, TUI tool.

    TUI is <u>T</u>erminal <u>U</u>ser <u>I</u>nterface, and IMO very user-friendly.

    • SecretSauces@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      When I try [sudo nmtui] it gives me "Command nmtui not found, but can be installed with: [sudo apt install network-manager].

      Which circles me back to my original problem where I don’t have network connectivity.

      • boredsquirrel@slrpnk.net
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        So the question is what the hell is “Ubi server” and why doesnt it preinstall network-manager?

        I would install both tools.

        • SecretSauces@lemmy.worldOP
          link
          fedilink
          arrow-up
          0
          ·
          6 months ago

          Ubi is just my short-hand for Ubuntu. And I’d love to be able to install Network-Manager, but I can’t/dont know a work-around

          • fluckx@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            6 months ago

            That would’ve helped to add in the original message. I dont think I’ve ever heard of “ubi” servers.

            You can try installing the deb file I guess? If you google it I’m sure you can find it somewhere.

          • boredsquirrel@slrpnk.net
            link
            fedilink
            arrow-up
            0
            ·
            6 months ago

            If you have an android phone and a usb cable for it, use usb tethering!

            Connect it to the PC, and in android under connections switch to “usb tethering” under usb options.

            But if you dont even have networkmanager installed (which is really really odd) then no idea if autoconnect works, likely not.

          • scrion@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            6 months ago

            As a general rule, maybe don’t use shorthand terms you invented in posts that are supposed to provide information to the people trying to help you, just so you don’t confuse them any further.

    • Successful_Try543@feddit.de
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      The first question which arises before proceeding with network manager: is the USB Ethernet dongle recognised?

      You can check the output of sudo dmesg shortly after you plug in the dongle into the USB port.

          • SecretSauces@lemmy.worldOP
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            6 months ago

            I dont see anything standing out.

            usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd
            
            usb 4-2: new USB device found: idVendor , idProduct, bcdDevice
            
            usb 4-2: new USB Device Strings: mfr=1 product=2, serialnumber=6
            
            usb 4-2: Product: Ethernet Adapter
            
            usb 4-2: Manufacturer: Microsoft
            
            usb 4-2: SerialNumber: xxxxxxxxxx
            
            usbcore: registered new device driver r8152-cfgselector
            
            r8152-cfgselector 4-2: reset SuperSpeed USB Device number 2 using xhci_hcd
            
            r8152 4-2:1.0: load rtl8153b-2 v2 successfully
            
            r8152 4-2:1.0 eth0: v1.12.13
            
            usbcore: registered new interface driver r8152
            
            usbcore: registered new interface driver cdc_ether
            
            r8152 4-2:1.0 enx949aa22353: renamed from eth0