Avatar

đŸ§Ÿâ€â™‚ïž Cadaver

Ashiette@lemmy.one
Joined
0 posts ‱ 20 comments

Here for the lolz

Direct message

Might be that you didn’t install intel-ucode or amd-ucode.

Did you use btrfs ? Did you encrypt with luks ? Because if so, you have to add the hooks to /etc/mkinitcpio.conf.

If you didn’t encrypt your drive or use btrfs, have you installed GRUB beforehands ? Because that screen might be from your old GRUB. If so, you need to install GRUB.

If so, reboot to your liveISO. Mount /, mount /boot then do :

arch-chroot

grub-mkconfig -o /boot/grub/grub.cfg

grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=GRUB

If that does not make sense or you need help figuring out, just reply to the comment. Arch is hard to install the first time. It often takes several tries to get it right. It becomes easy the second time round.

permalink
report
reply

đŸ”„ Hot take : Liftoff is better than Thunder considering it just is.

permalink
report
reply

Core Training III : Live Free or Die Hard

permalink
report
reply

Okay first question is : is MATE absolutely necessary ?

If not, I would advise you to switch to a distro that uses GNOME or KDE. I’d go for Zorin OS which is really perfect for anyone beginning on Linux.

In any case, I have a solution that should work no matter the device. It requires you to have libinput and libinput-gestures installed (rather than fusuma which I found buggy and laggy)

You can find it here : https://lemmy.one/comment/2189433

I tried my best to make it beginner-friendly — even if it is not. Don’t read the first paragraph which is KDE specific.

permalink
report
reply

Try to disable your swap. You don’t need a 16Gb swap partition. If you really need to hibernate, try switching to a swapfile instead, but that can cause resume errors.

permalink
report
parent
reply

Super. Merci de la prĂ©cision. Ça peut en effet ĂȘtre super intĂ©ressant, c’est le genre de choses qui pourraient aussi m’intĂ©resser d’apprendre si j’avais le temps/les compĂ©tences.

Je vais essayer de faire tourner ton programme un peu les prochains jours. Comment poster les hashs ?

permalink
report
parent
reply

That’s the thing ! It’s not linux specific.

How it works :

USB 1 and 2 use a set of 4 pins. It can only use those 4pins to transmit data.

USB 3 uses 9 pins : the 4 original pins and 5 more pins. It is backwards compatible with USB 1 and 2 because it can only use those four pins instead of the full array.

USB-C, however, uses 24 pins (2*12 pins to be exact). However, what makes no sense, is when using a USB-A to USB-C cable it does work only in one direction : from USB-A to USB-C.

But rest assured, you are not alone onnthis issue. I’ve had it, even when I did not want to tranfer data but just power : it does not work, whether on Windows or Linux


permalink
report
reply

Looks promising ! I really wanna try it

permalink
report
reply

You might be the dumbest man alive but Laura Les sure is the dumbest girl alive !

permalink
report
reply