• 0 Posts
  • 114 Comments
Joined 1 year ago
cake
Cake day: July 18th, 2023

help-circle


  • have you looked at the dells? i think i’m going to get one for work and their specs suggests that it’s compatible.

    short of buying a linux laptop from a linux maker with it’s own disto and it’s own developers to maintain it; there’s no other guaranteed way know (afaik) if they’re compatible ahead of time if no one has had already tried it and shared their results online.

    questions like yours is the reason why i bought that kind of laptop five years ago and the sailing has been so smooth ever since that i now think i need to get a new laptop so that i can understand what choppy waters looks like nowadays with a windows only laptop and trying to get everything to work on it; like i did when i was first learning linux. and dell seems likely to me.




  • i think that eliminates the subnetting netting theory.

    let’s switch to some basic troubleshooting on the network: are you able to get use dhcp on this network to get a lease and; if so; can you do it with dhclient with some verbosity? are there any other hosts on the network that respond to ping? is ping allowed on this network?








  • eldavi@lemmy.mltoLinux@lemmy.mlWireguard ping problem
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    5 days ago

    are you able to get something akin to route -n and ip a or ifconfig like printouts/information that you can copy/paste here to to ascertain your networks’ configuration to help us understand your environment and have a better chance of reaching a resolution.

    i thinking basic routing information like your gateway or your mask might be a decent place to start and i would normally use commands like those in a linux system as a starting point; i’m sure whatever platform you’re using has an analogs.

    at first glance it looks like a subnetting issue; but i’m sure i’m interpreting the information you’ve shared incorrectly and this basic routing information will help clarify that.


  • eldavi@lemmy.mltoLinux@lemmy.mlFedora wifi question mark
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    5 days ago

    too much noise and not obvious errors/failures/timeouts; try filtering by service units with something like journalctl -u ${service-unit-name} and set deeper debugging level with sudo.

    so i think that a list of the relevant service units will be decent place to start and the no-brainers from your copy/paste are audit, kernel, and systemd-${whatever} service units and we need to figure out what else we need to add to that list: maybe gnome-shell since you’ve mentioned nmcli? are you using fedora’s default ndiswrapper and what is it?



  • i’ve been accused of that along with several other slurs like systems engineer and cloud operations engineer and it systems architecture analyst and software engineer. lol

    i’m a software developer atm, but my current gig has a LOT of overlap with all of those other four letter word titles that i dare not repeat in decent company. lol


  • that dated comment was right and i hit that easy button five years ago. also i’m realizing now that doing so has completely removed me from the discourse that happens nowadays when it comes to gpu’s and linux.

    amd had already bought ati by the time i hit that easy button and that distinction that i used wasn’t out of place at the last time i was paying attention and participating; or atleast wasn’t so in my experience.

    there used to be lists of rankings for compatibility for nvidia drivers and open source drivers as well. i wonder how i would go about finding the same for amd.


  • eldavi@lemmy.mltoLinux@lemmy.mlTinkering and Stability
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    5 days ago

    delete everything in /tmp; you’re not really using it anyways and you’ll get more disk space. lol

    i literally used this same logic when i merged the contents of c:\windows & c:\win32 because there were so many duplicate files and folders and i needed to recover the free space.

    sometimes i’m thankful for my cluelessness; examples like this paint me into corners and this particular corner was the impetus behind my exploration into linux; which has sustained my career for the last 25ish years through several once-in-a-lifetime economic recessions and multiple personal setbacks.

    linux is the best mistake i’ve ever made.


  • when you use an xserver, it occupies one of those virtual terminals that i referenced in my last message.

    most distros use 7 virtual terminals and the xserver is usually dedicated to one of them and that means you can use the keyboard shortcuts of alt+ctrl+f1 through alt+ctrl+f7 to switch from your xserver and into a bash prompt where you can then log in without the xserver and execute that command to look at the logs.

    you can toggle between all 7 terminals at any time without impacting each other; you can use those keyboard shortcuts to help you troubleshoot this and all xserver problems in an “alt-tab” like fashion switching back and forth between the xserver and six other terminals where you can do things like execute commands; look at logs; & modify configs.


  • in your shoes: i would run journalctl -f to watch the logs scroll by on screen in one virtual terminal (whatever the systemd equivalent is nowadays; it was alt+ctrl+f1 through f7 back i the sysv-init days) and try to log in again on the base xserver virtual terminal and try to watch for errors/failures/warnings messages from that those scrolling logs.

    journalctl is a unifiied logging system that comes with systemd so your logs are likely to persist there and it has built in tools to help you narrow it down if you see anything in the logs.