Comments

This profile is from a federated server and may be incomplete. Browse more on the original instance.

Romkslrqusz, (edited ) to linux in need help fixing a hardware problem using linux

Awesome breakdown and troubleshooting so far!

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.

Romkslrqusz, to linux in Dell Latitude Frustration

A software approach to a hardware problem is an exercise in futility.

Test your memory with Memtest86

Test your disks too. badblocks is a Linux utility. I like the Victoria and HDDScan Windows programs because they’re less pass/fail in their reporting - you can see that a disk is degraded even if all of the sectors technically respond.

Romkslrqusz, to asklemmy in What's a quote that has stuck with you for your whole life?

Cheat on their partner with you as “the other person”

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • localhost
  • All magazines
    •
    200 @ user_comments
    HTTP status 200 OK
    Controller UserFrontController :: comments
    Route name user_comments
    Has session yes
    Stateless Check no
    Time 452 ms
    Total time 452 ms
    Initialization time 98 ms
    Memory 16.0 MiB
    Peak memory usage 16.0 MiB
    PHP memory limit 128 MiB
    Logger 86
    Errors 0
    Warnings 0
    Deprecations 86
    Cache 33 in 22.04 ms
    Cache Calls 33
    Total time 22.04 ms
    Cache hits 30 / 41 (73.17%)
    Cache writes 7
    3
    Default locale en
    Missing messages 3
    Fallback messages 0
    Defined messages 123
    Security n/a
    Authenticated No
    Firewall name main
    Twig 247 ms
    Entry View user/comments.html.twig
    Render Time 247 ms
    Template Calls 83
    Block Calls 16
    Macro Calls 0
    57 in 110 ms
    settings_row_switch 15
    date 4
    user_settings_row_switch 4
    entry_comment 3
    user_inline 3
    date_edited 3
    magazine_inline 3
    entry_inline 3
    user_avatar 3
    vote 3
    boost 3
    settings_row_enum 2
    user_actions 1
    related_magazines 1
    active_users 1
    related_categories 1
    related_posts 1
    related_entries 1
    support_us_block 1
    featured_magazines 1
    18 in 112.16 ms
    Database Queries 18
    Different statements 16
    Query time 112.16 ms
    Invalid entities 0
    Cache hits 20
    Cache misses 1
    Cache puts 2
    6.4.0
    Profiler token be98fb
    Environment dev
    Debug enabled
    PHP version 8.2.26   View phpinfo()
    PHP Extensions Xdebug ✗ APCu ✓ OPcache ✓
    PHP SAPI apache2handler
    Resources Read Symfony 6.4.0 Docs
    Help Symfony Support Channels