setxkbmap -layout in -variant eng -verbose 10

I expect this is the layout you had previously. It's called "English (India, with rupee)".

If that command gives you what you expect, then you should make it permanent. The correct way to do this, (assuming you have no keyboard management software that would override it) is this:

/etc/default/keyboard

XKBMODEL="pc104"
XKBLAYOUT="in"
XKBVARIANT="eng"

If there's also an XKBOPTIONS line in there, it's probably best to leave it as-is until you need additional tweaks.

FYI, you were on the right track looking the the xkb/symbols files as they indeed contain keyboard layouts your system has access to. However, each file contains many layouts as "variants", sometimes very different ones even within the same file. The main layout is identified with the name of the file and the variants are named within it.

I have done this recently, but not with a DVD image as the OP suggests. Only the regular 5.0 daedalus repositories need to be set up.

(Aside: I put them in /etc/apt/sources.list.d/daedalus.list instead of the main sources.list so they can be turned off and on by changing the file extension instead of going in and commenting lines.)

Even on a mediocre internet connection it doesn't take that long to pull all the necessary packages.

I am using runit, on multiple systems now.

It's not bug-free, and I got very frustrated when a weird intermittent bug was made infuriatingly hard to investigate due to sorely misleading documentation. (RTFM! - yes, I did! It was bad so I wrote my own.) However, once that was solved it has worked well enough.

The maintainer, forum user @Lorenzo, has to his credit been active and responsive in fixing issues.

It has promise and I like the idea behind it, so I'm stubbornly going ahead because it should work, damn it! However the reality is that I can't recommend it generally because decades (yes, decades!) of neglect from the wider community has left it hard to diagnose and fix whenever something goes wrong.

My old netbook with 2GB RAM runs Devuan with XFCE.

To recap:

You took a dd image of this device. Now your are trying to write that image using dd back to the same device but you are getting the error that there is insufficient space. Correct?

It's natural to blame the device since cards like this are known for failing, and that's if they're even legitimate. However, I'm wondering if something about the image you took is the problem. Maybe it somehow got "padded out".

Exactly how large (in bytes or sectors) is the card, and exactly how large is the image?

Look at the image itself. Is the end filled with zeroes or does it contain data? (I use wxHexEditor for such things but other tools exist)

I believe you're describing the same issue I had. After a kernel update, run:

sudo dpkg-reconfigure nvidia-kernel-dkms

Video is reliant on nvidia dkms modules, which for some reason aren't automatically rebuilt for the new kernel, hence the need to do it manually. dpkg-reconfigure will do it (which is what I use), as will reinstalling the nvidia driver completely (as you found).

Gemini says this will also work:

sudo dkms autoinstall

But I have not tested it.

As to how to do it automatically... one could put together a script which checks whether dkms modules exist for the current kernel, rebuild them if not, and set that script to autorun. But that seems like a lot of work.

The OP was clearly having some dbus issues. There was not enough investigation done to try to fix it, just a switch to a different distro. If OP is satisfied with that, that's good enough for them. However, Steam does work in Devuan as many users, including myself, can confirm.

What actual issue or error are you seeing?

Try these first:

sudo update-desktop-database
update-desktop-database ~/.local/share/applications/

That should pick up mimetype changes. (Though it should've been already done automatically.)

If that has no effect, you can try to manually set the handler:

xdg-mime default '/home/JnvSor/.local/share/applications/steam.desktop' x-scheme-handler/steam

I don't have answers to your questions beyond this.

,
Did you mean not working?

I'm close to certain EDID is not the problem so patching it will do nothing.

I notice the modelines you used are for 50Hz. Try the 60Hz from my post. Probably won't work, but just to confirm.

How exactly are you using these?

Possibly.

HDMI 1.3 officially has a max pixel clock of 340MHz so this monitor's desired clock (241.5Mhz) should be supportable.

The EDID does not seem to be the issue. What does a plain xrandr output? Is 2560x1440 available?

Have you tired adding a custom mode using xrandr?

# 1. Define the new mode using the CVT-RB parameters
xrandr --newmode "2560x1440_60.00"  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync

# 2. Assign the mode to your active display output
xrandr --addmode HDMI-0 "2560x1440_60.00"

# 3. Switch the display to the new resolution
xrandr --output HDMI-0 --mode "2560x1440_60.00"

CD drive should appear in /media/cdrom when there is a readable disc inside.

Regular USB flash drives should also appear under /media but you need the gvfs package installed (which it should be if you picked the typical options during install, basically anything other than minimal).

The camera will depend on how it presents itself. If it's an MTP device you will need the appropriate packages to read from it.