zanzo

joined 3 years ago
[–] zanzo@lemmy.world 1 points 5 hours ago

I can't recall but I may have followed a similar process before, but I'll go through that once again.

[–] zanzo@lemmy.world 1 points 7 hours ago (2 children)

Kernal 16.17x. I forget what driver is on there now, but it's around 580x.

I did a clean install early on after updating to the Nvidia drivers killed my Linux install the first time. I was fine for about a week and then things crashed again.

For some reason, I can't get dmesg to do anything. I did run journalctrl -b -p err and I got a few error messages. see below.

These look like they occurred during boot. I ran these through AI and it responded that Most likely causes:

GNOME/GDM packages are broken or partially installed Your user runtime/session is failing Bad permissions in your home folder Display driver issue causing GNOME session startup failure Leftover damage from previous repair/driver changes

Jul 07 13:58:14 host gdm3[3615]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISP> Jul 07 13:58:42 host gdm-password] [4192]: gkr-pam: unable to locate daemon control fi> Jul 07 13:58:42 host qdm3[3615]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISP> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkc> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dsec> Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh> Jul 07 13:58:43 Jul 07 13:58:43 host systemd[4203]: Failed to start app-gnome-user\x2ddirs\x2dupdate> Jul 07 13:59:14 host qdm3[3615]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DI>

Jul 07 13:57:52 host thermald[1110]: Thermal DTS or hwmon: No Zones present Need to c>

host systemd[4203]: Failed to start app-gnome-im\x2dlaunch-4737.scope>

[–] zanzo@lemmy.world 1 points 7 hours ago

Exactly same behavior.

[–] zanzo@lemmy.world 1 points 7 hours ago

Looks like I'm running kernal 6.17x so I'll look into downgrading via the bios.

 

Looking for advice on what I suspect is a driver issue with Zorin Linux.

For a few months, I've had issues with suspend, where the computer will wake, but the screen remains black. This happens both when the computer suspends on its own and when I suspend it manually.

Worse, when I force reboot the computer:

  1. only one of my monitors lights up
  2. my keyboard is unresponsive.
  3. Mouse still works.
  4. Internet also dies.

Both monitors are connected to an Nvidia GTX 1070 GPU. The keyboard and mouse are connected via USB.

What I've tired

  • I've used the Accessibility Keyboard (screen keyboard) to log in after a restart and revert to a previous state using Timeshift. This will get the keyboard, Internet and screen to work, but the moment I suspend, the problem returns.

  • I did notice this issue started once I updated my GPU drivers to Nvidia ones (I've tried a couple).

I tried reverting to the Nouveau driver, but the problem returned.

I should probably note that when I orginally tried to install Zorin with Nvidia drivers, the install failed.

Advice

I'm looking for ideas on how to proceed.

At this point, I could start over completely with a fresh install of Zorin.

I could revert to the earliest Timeshift image I have, which would put me back to a fresh install.

I could abandon Zorin for another distro.

Thanks!

[–] zanzo@lemmy.world 1 points 1 day ago (1 children)

Rather, Peter Zeihan. He was forecasting this over a decade before the invasion. It’s about geography, population decline and the desire to create a buffer against possible invaders. Not that anyone was seriously looking to invade Russia. But their history has hardened their perspective on this matter.

[–] zanzo@lemmy.world 32 points 6 months ago (1 children)

Librarian here: Good news is that many libraries are standing up AI literacy programs to show people not only how to judge AI outputs but also how to get better results. If your local library isn’t doing this ask them why not.

[–] zanzo@lemmy.world 1 points 9 months ago