Running EasyOS from a hard drive and problems encountered

[Grey]

Hello. Here is how it was. I unpacked easy-2.5.5-amd64.img.gz using the excellent PeaZip archiver. It turned out two .img files, one of which I unpacked and got a structure with initrd, vmlinuz, easy.sfs and others. Then I unpacked the initrd file and changed the lines BOOT_UUID, BOOT_DIR, WKG_UUID and WKG_DIR in the BOOT_SPECS file. I added uuids and folders located on the partition of the hard disk with the ext4 file system. Then I packed initrd back into .cpio format and removed the extension.
Launched easyos with Grub2. initrd warned me that the keyboard might not work and suggested that I wait 5 minutes. This is too long. But that's not the point. Five minutes later, the system started up and a desktop with icons and a window for the first setting appeared. But neither keyboard nor mouse works. The preferences window prompts me to press Tab if the mouse doesn't work, but how do I do that without a working keyboard?
It's a pity, because the system is almost working... Are there any wise advice, instructions?
Also, is it possible to set the BOOT_UUID, BOOT_DIR, WKG_UUID and WKG_DIR parameters in the Grub2 config file? Or edit manually every time inside initrd?
I correctly understood that there are still flaws-problems with input devices, since the initrd and the desktop themselves offer the user ways to solve them?

[BarryK]

This is the first report I have received that keyboard and mouse do not work.

Write the .img.gz file to a usb-stick, using EasyDD, or one of the other USB-stick-writers, or just use 'dd.

Boot the USB-stick and report if keyboard/mouse working. If yes, then that will eliminate EasyOS itself as the cause.

[Grey]

I wrote the image using EasyDD to a Kingston DataTraveler flash drive(USB 2.0, 8Gb). Absolutely the same situation. The keyboard is like this: Rapoo V500S Ice Crystal Backlit Mechanical Keyboard. By the way, when the system suggests waiting 5 minutes, the backlight turns on itself and blinks when you press any key. The keyboard has a backlight controller, the backlight itself is turned on/off by the Fn+SL combination and there are several more operating modes. And mouse: A4Tech Bloody V7. She always blinks

All these pieces of iron work great with Fossapup64. I will try to conduct a few more inhuman experiments on the EasyOS. I still want to run it from the hard drive and so that all peripheral devices work.

By the way, the speed test of the boot device, the line of which appears almost at the beginning of the system startup:
Flash drive = 158
Internal hard drive HGST HTS721010A9 (1TB, 2.5-inch, 7200RPM) = 11

[BarryK]

Hmm, it seems most likely a kernel configuration problem.

You could try the kernel from fossapup:

Replace 'vmlinuz' in the boot-partition of EasyOS with the one from fossapup.

Copy /lib/modules/<kernel-version> from fossapup to the EasyOS working-partition easyos/.session/lib/modules/

Might be a good idea to also copy /lib/firmware from fossapup to easyos/.session/lib/firmware

The you should be able to boot EasyOS.

It will be interesting to know if the kernel loaded a module or firmware for the keyboard:

# dmesg > dmesg.log

Then open dmesg.log in Geany and search for keywords such as "keyboard" and "firmware".

[Grey]

The substitution of vmlinuz + addition of modules and firmware works in the case of a flash drive, but not with a hard disk (swears at mounting aufs).
It works with a flash drive - the system starts with a mouse and keyboard. dmesg doesn't find the 'firmware' keyword, but the keyboard is 'SIGMACHIP':

Code: Select all

usb 1-1.4: New USB device found, idVendor=1c4f, idProduct=0059, bcdDevice= 1.00
usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.4: Product: USB Keyboard
usb 1-1.4: Manufacturer: SIGMACHIP
input: SIGMACHIP USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:1C4F:0059.0004/input/input8
hid-generic 0003:1C4F:0059.0004: input,hidraw3: USB HID v1.11 Keyboard [SIGMACHIP USB Keyboard] on usb-0000:00:1a.0-1.4/input0
input: SIGMACHIP USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:1C4F:0059.0005/input/input9
input: SIGMACHIP USB Keyboard System Control as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:1C4F:0059.0005/input/input10
input: SIGMACHIP USB Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:1C4F:0059.0005/input/input12
hid-generic 0003:1C4F:0059.0005: input,hiddev97,hidraw4: USB HID v1.11 Keyboard [SIGMACHIP USB Keyboard] on usb-0000:00:1a.0-1.4/input1

But the system does not see sound card (and there are several of them) and Sound Wizard says that no sound devices found.
Mmmm ... At this level, the system will scare off the average user