I would conclude from this that your dc-dc converter is out of whack and only works stable enough for a small range of input voltages. This hardware issue might require a hardware fix at a repair shop :/
thanks for the input. so no amount of tweaking and kernel switches and MSRs and what not can be utilized to lower or alter the performance so that it behaves? the repair route isn’t likely unfortunately
Would you notice if it doesn’t? The screen flickering is obvious, what if your ram and ssd flicker, too? You can tinker with that laptop and try to reduce 3.3 or 5v power rail load with kernel flags, but until someone checks those power rails electrically I wouldn’t trust that laptop to be reliable for anything but a tinkering exercise. We sadly don’t get redundant power IC’s you could switch to, but the failure is common and the involved parts cheap. I wish competent repair shops were more common.
sure, it’s a decade old device worth like $100, if that. of course this is a tinkering exercise. but I’m referring to the fact that it works perfectly without battery, it obviously has some power limiting then (no speedstep, no turbo). so I was looking to recreate that behavior with the battery.
Is UI mimics ms office and has comparability with word files.
Not open-source and has some limitations without paying but works on windows and Linux. Can even be self hosted yourself to provide a web UI for access to your own files Google docs style.
There is still an older version of Scrivener available for free, from when they were beta testing it on Linux. It still worked well last time I checked. The Windows version also runs really well in WIne, although it takes a bit of setting up initially.
I love Wayland until I don’t. I honestly don’t think about it, it gets out of my way and my system is stable, until I go to use something like scrcpy that just doesn’t work at all. Luckily, the amount of things that straight up don’t work is shrinking.
It’s super impressive to see Wayland having its big breakthrough moment. I remember reading about Wayland 10 years ago and worrying it was going to end up as a dead project.
I wonder if the previous owner removed the battery because of this issue in the first place.
The fact that the flickering is full-width bands that don’t appear in screenshots indicates to me that this is a signal issue to or through the display.
An important variable to pay attention to and experiment with is the display’s refresh rate. It’s possible that is what is changing with and without the battery, though you most likely would have noticed if that were the case.
Since the problem varies based on battery presence, it would be appropriate to source a replacement battery - especially if you purchased a cheap aftermarket battery. The real deal for your system is available for $80USD from Parts People compared to $20-$40USD for low quality Amazon junk.
After the battery, my main suspicion is a fault on the mainboard leaking voltage from the battery circuit and affecting the display signals. Even without the infrequency of the problem that would be tricky to isolate and remedy.
Overall, this screams hardware issue and I don’t believe you will find a software trace of it. The problem is not visible in screenshots, so the software environment does not know that it exists.
Why shoot with the phone and bother mounting it, if such a solution existed, instead of using the phone as a phone and the camera as a camera separately without mounting
Yeah, it works fine. You might want to tinker with the packages as others have suggested but it’s exactly what you expect from Fedora. The only difference is it’s Plasma instead of GNOME.
I had the same experience with GNOME on the family computer. I had to add extensions to make it more accessible. Then when they auto update you get dumped into vanilla GNOME until you log out and back in to re-enable extensions. I would get called over every time that happened. I switched it to Plasma and everyone is happy.
One thing worth pointing out is the dash to dock/panel, just perfection and appindicator GNOME extensions are all in the Fedora repository. When you install them from there, you don’t get that janky behavior during updates where you have to re-enable them. Those extensions go a long way towards making GNOME more accessible to users coming from Windows or Mac. Default GNOME is great if you use keyboard shortcuts but it’s not very intuitive when you’re starting out.
I don’t think you could have explained this any better… yeah, this exactly. I don’t want to get a phone call every time the update the damn system. Gnome can be different, simple, that’s fine, but it has to do that and get out of the way. If you make changes to it, it has to respect those changes. Everything else is garbage.
Firstly, hats off to you for trying to properly diagnose the problem and trying everything that you did. Hope you find the solution soon. Some random suggestions if you haven’t already tried - clean the battery contacts (I’m not sure of the best method to do so but I’m sure you can find something online), check to see if the problem exists in different screen refresh rates, turn off auto brightness if its on.
nah, tried that when I had windows on it. that and a bunch of other stuff from the unhelpfulest site on the webz - dell.com. screen rates and resolutions and auto brightness as well. the battery contacts are way too tiny for me to do anything meaningful there. besides, I’m thinking that if the battery is the problem, then there shouldn’t be any issues when running the thing on external power; it’s not like the battery is powering the laptop when connected to external power, it’s running on external power and using the surplus to charge the battery.
Wayland on an Intel iGPU runs flawlessly and has for several years. However, that’s a matter of drivers. AMD is in the forefront regarding having dGPU support, while NVIDIA is playing catch-up.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.