01adrianrdgz, (edited )
@01adrianrdgz@lemmy.world avatar
turbowafflz,

Looks like it’s using a video mode the monitor doesn’t support, you’ll need to set the refresh rate as well as the resolution to ones that are supported. Likely candidates are 800x600@75hz or 1024x768@60hz, but it really depends on the monitor, check the manual if you can

01adrianrdgz,
@01adrianrdgz@lemmy.world avatar

thank you but I don’t have the manual, there is no information about this monitor online, I’m currently in BIOS, it’s American Megatrends. https://lemmy.world/pictrs/image/455f58f2-6fcf-4017-afef-532495b76a82.jpeg

turbowafflz,

If it’s a vga monitor you could probably plug it into a modern computer to see the available video modes in the display settings. Then on the old computer just change the video mode with xrandr in your xinit

wmassingham,

The monitor seems to be recommending you use mode 1280x1024. Have you tried that?

01adrianrdgz,
@01adrianrdgz@lemmy.world avatar

there’s no setting for that, the only settings are really basic ones!! I will change the resolution from GRUB then, maybe that will work.

navitux,
@navitux@lemmy.world avatar

Did you solved it?

01adrianrdgz,
@01adrianrdgz@lemmy.world avatar

no, I’m sorry about that, I’m currently flashing Xubuntu and maybe that will work too!!

palordrolap,

That looks like it might be the monitor's own on-screen display rather than anything Puppy related. My guess is that the monitor hasn't been detected properly and Puppy is putting out a resolution that the monitor can't deal with.

Since the message says 1280x1024, either the monitor is 1280x1024 and can't deal with anything else, or it's not 1280x1024 and is being sent 1280x1024 resolution and is complaining about it.

(Or worse, it's a clock frequency error which was a real problem back in the early days of Linux.)

As for how to fix, the answer is going to be different depending on the age of the base Linux under Puppy and the graphical subsystem.

For X/X11/Xorg it's probably going to need use of the xrandr shell command, perhaps to delete the mode that is causing the problem. For Wayland, it appears that each window manager has its own xrandr equivalent. I see talk of a gnome-randr, for example.

To get to a shell in the first place, try the Ctrl+Alt+F1 key-combo. If the computer isn't frozen, that might get a text-based console login prompt. (Puppy might do things differently here though. Not sure.)

Alternatively, look up how to boot to a single-user shell by modifying GRUB options, that is, if no such option is there already.

Caveat: I am no expert. Take this under advisement. Also try web-searching some keywords. It might be there's a really simple fix for this that I don't know about.

01adrianrdgz,
@01adrianrdgz@lemmy.world avatar

thank you so much!!!

selokichtli,

Try booting with kernel flag --nomodeset. If it gets you to the desktop, you could find out more about the graphics card and monitor.

nyan,

Ooh, CRT monitor. And that’s an odd resolution that it’s suggesting. You could try driving it at 1280x1024 at 60Hz. If that doesn’t work, try 800x600 at 60Hz, which is the traditional lowest SVGA resolution (picture may be slightly distorted if it really is a 5:4 monitor). If that doesn’t work, try the traditional VGA resolution of 640x480 just to get something going. I’d recommend using X as Wayland has probably not been tested very much on hardware this old. And it almost certainly has no clue how to deal with a widescreen resolution or a resolution wider than its “Recommend mode”.

(I was still using a 17" CRT with X at 1280x960 up to about five years ago. I had no issues ever.)

vaionko,

1280x1024 is really not that pdd for an old LCD. And yes,to me that looks like an LCD instead of a CRT. Way too flat and matte for a CRT.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • linux@lemmy.ml
  • localhost
  • All magazines
  • 200 @ entry_single
    HTTP status 200 OK
    Route name entry_single
    Has session yes
    Stateless Check no
    Time 1535 ms
    Total time 1535 ms
    Initialization time 119 ms
    Memory 16.0 MiB
    Peak memory usage 16.0 MiB
    PHP memory limit 128 MiB
    Cache 1
    Number of forms 1
    Number of errors 0
    Logger 88
    Errors 0
    Warnings 0
    Deprecations 88
    Cache 73 in 833.60 ms
    Cache Calls 73
    Total time 833.60 ms
    Cache hits 54 / 80 (67.5%)
    Cache writes 21
    641
    Default locale en
    Missing messages 641
    Fallback messages 0
    Defined messages 148
    Security n/a
    Authenticated No
    Firewall name main
    Twig 1263 ms
    Render Time 1263 ms
    Template Calls 201
    Block Calls 82
    Macro Calls 6
    146 in 1005 ms
    date 16
    user_inline 15
    settings_row_switch 15
    date_edited 14
    vote 14
    boost 14
    entry_comment 13
    user_avatar 13
    entry_comments_nested 13
    user_settings_row_switch 4
    settings_row_enum 2
    entry 1
    entries_cross 1
    editor_toolbar 1
    user_actions 1
    magazine_box 1
    magazine_sub 1
    related_magazines 1
    active_users 1
    related_categories 1
    related_posts 1
    related_entries 1
    support_us_block 1
    featured_magazines 1
    20 in 150.99 ms
    Database Queries 20
    Different statements 12
    Query time 150.99 ms
    Invalid entities 0
    Cache hits 26
    Cache misses 2
    Cache puts 2
    6.4.0
    Profiler token 07b09a
    Environment dev
    Debug enabled
    PHP version 8.2.26   View phpinfo()
    PHP Extensions Xdebug ✗ APCu ✓ OPcache ✓
    PHP SAPI apache2handler