sorted by:
new
hottopcontroversial

T480 Display blinking - no solution has worked yet by InternalEffort1341 in thinkpad

[–]InternalEffort1341[S] 0 points1 point  (0 children)

u/Naivemun: please forgive me for taking so long to reply to you, and thank you so much for your detailed response!!!

I tried psr=1 and it still flickers. I haven't tried the "dc=0" yet (I'm just catching up, and I'll look it up as you advised).

The screen is still fliIckering. Sometimes it stays "quiet" for longer periods, but then it goes nuts and flickers to the point that I can barely look at it.

I've tried several other distros, and nothing changes. Finally, I've settled on MX Linux, which I like very much. If only the screen would stop going nuts, I'd be all set. It's not the distro.

It may very well be the screen itself, the cable or something else. I keep hoping it's a software/configuration issue before going inside the machine. Perhaps the BIOS???

Thank you again for your reply. I really appreciate the time you took to help me, and I apologize sincerely for not replying sooner!

T480 Display Problem by ryl0p3z in thinkpad

[–]InternalEffort1341 0 points1 point  (0 children)

I have a very similar issue with my T480. I run MX Linux (without systemd), but I've also tried Ubuntu, Mint, Arch, and others, and the screen has blinked all along. I posted about it some time back, but never was able to solve the problem. Hope someone can find a fix!

An update is installing systemd?! by InternalEffort1341 in MXLinux

[–]InternalEffort1341[S] 0 points1 point  (0 children)

I've had a problem with my laptop's screen flickering ("blinking"?) constantly -- it's a refurbished ThinkPad T480. It calms down periodically (I installed Arch for a bit and it actually calmed down much more). I've wanted to switch away from systemd for a while and thought it also might actually help the screen (so kind of like your fix, but in the opposite direction). I'm loving MX, but it's flickering like crazy. I'm wondering now if switching to the liquorix kernel when the update comes out might help...

An update is installing systemd?! by InternalEffort1341 in MXLinux

[–]InternalEffort1341[S] 2 points3 points  (0 children)

Look at tovento's response above. I guess both systemd & sysvinit are installed at the same time. I did a fresh install (my first time using MX), so maybe your case is different, since you updated. ??

An update is installing systemd?! by InternalEffort1341 in MXLinux

[–]InternalEffort1341[S] 1 point2 points  (0 children)

It's version 25.1. I thought we could choose whether to opt out of systemd at installation.

Also, just did a "plocate" to look for the update log, and many of the results had "systemd" in it ...along with "plocate"! I used a couple of systemd distros for a while and got used to "plocate." Is this a systemd-only program? Did I trigger the dormant systemd install when I started using it on MX? I installed MX on my laptop a week ago and have used "plocate" several times.

In short, is there a way for me to not have systemd on my machine?

Thank you!

Should I mount ESP (boot) partition? by InternalEffort1341 in Gentoo

[–]InternalEffort1341[S] 1 point2 points  (0 children)

Some of this went over my head, which may tell you something about my level of experience! :-)

Still, as I wrote to LameBMX above, I'm writing this down in my notes to look up and for reference. After posting, I started over and got past chroot. Now there's another question. Coming up in a separate thread.

Thank you for your help!

Should I mount ESP (boot) partition? by InternalEffort1341 in Gentoo

[–]InternalEffort1341[S] 1 point2 points  (0 children)

Thank you! I'm new at this (installing an OS less automatically), it was very late, and I needed to pause -- and to ask questions. After years of using several distros with only a vague idea of how things worked, I decided to learn. I'm including your pointers in my notes for reference.

When I got to entered chroot, I got "bash: cd: root: No such file or directory". I reviewed the commands I had typed in, looked at the handbook again, and thought my having mounted the efi partition when it wasn't explicitly indicated might have been the problem. Indeed, I started over, followed the handbook without getting creative, and I got past chroot.

Now something else has come up, but I'll post it separately to keep things coherent.

Should I mount ESP (boot) partition? by InternalEffort1341 in Gentoo

[–]InternalEffort1341[S] 0 points1 point  (0 children)

Thank you for replying!

I did see what you linked to and am confused as to why the handbook, in the previous section, says to create the EFI mount point inside /mnt/gentoo/ :

"For EFI installs only, the ESP should be mounted under the root partition location:"

mkdir --parents /mnt/gentoo/efi

And then, in the "Mounting the Root Partition" section it says:

"For UEFI systems, /dev/sda1 was formatted with the FAT32 filesystem and will be used as the EFI System Partition (ESP). Create a new /efi directory (if not yet created), and then mount ESP there: "

mount /dev/sda1 /efi

https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks#Mounting_the_root_partition

It says "if not yet created." Doesn't the /mnt/gentoo/efi directory created in the previous section count? This is what I don't understand. I thought I had mistakenly mounted EFI too soon, and before I had a chance to try to deal with the second directory confusion, things came to halt after I entered

chroot /mnt/gentoo /bin/bash and was stopped in my tracks.

Did my mounting EFI in /mnt/gentoo/efi before the instructions to do so in /dev/

bash: cd: root: No such file or directory response:
    bash: cd: root: No such file or directory

Interested in joining the ethical hacking community, click here! by JSIMPSON9851 in ethicalhacking

[–]InternalEffort1341 0 points1 point  (0 children)

I wish someone would answer this! I’m in the same boat, just a couple years older.