Recommended Cockpit Platform

[mgrouch]

Originally Posted by hpeer

Also, how do I get into File Manger.
I want to type out my code (gedit) and save. But can not figure out how to retrieve.

FILES icon seems obvious but does not respond.

The file manager is called Thunar.
You can also start it from Applications menu (click on foot in left top)

[hpeer]

I see that photo I attached did not come across as intended.

I enter the first line of code and get the message
Warning: apt-key is deprecated. Manage keyring files in trusted gpg instead.

That sounds like the machine is upset with the "apt-key" command. Did you not have this problem?

[mgrouch]

Originally Posted by hpeer

I see that photo I attached did not come across as intended.

I enter the first line of code and get the message
Warning: apt-key is deprecated. Manage keyring files in trusted gpg instead.

That sounds like the machine is upset with the "apt-key" command. Did you not have this problem?

It’s not an error. It’s a warning which can be ignored.
It warns you that next Debian versions might stop working with apt-key.

[mgrouch]

Originally Posted by mgrouch

The file manager is called Thunar.
You can also start it from Applications menu (click on foot in left top)

Regarding your File Manager issue. You might experience this known issue which is minor.
The conditions under which it is stopping to start via icon and workaround see

https://github.com/bareboat-necessit..._gen/issues/49

[hpeer]

OK on file manager. Will look into it later. For now got the other going.

FIRMWARE
UPDATE
The first 3 lines ran with warnings only.

At line 4 it Errors (red E
Unable to locate ed-linux-image-6.¹.58-2712
Next line errors also.

I did send an email to Edatec support.

[hpeer]

Mgrouch, hello. I hope you are still with me.

I have a few things to report.

1. I HAVE been able to run the EDATEC firmware update but I sill do not have the EDATEC screen coming on.

I found the problem. In the written line of code it wraps to a second line on the screen or paper. There is a “space” between words there that is not evident because it is at the end of a line.

That may be obvious to a coder but to one who is not adept at code it is a real stumper.

2. Above you indicated that after you installed the EDATEC firmware update you still had an issue. I got lost in your explanation and what to do about it. I presume you are awaiting something back from Rick????

3. The firmware package online this morning is different from the one you originally linked. I printed the original out and have it in front of me. It has slightly different instructions for the 7” and 10” screens. The online package I just pulled up and ran does NOT have that difference and the package names are new.

I am GUESSING Rick is doing something to address your problem in #2 above???

As before BBC comes up on the attached screen, but the EDATEC screen remains blank.

[hpeer]

BYW, is there anyway to make the Terminal text any bigger.

It was tiny before this last effort, now it is very nearly impossible.

[mgrouch]

Originally Posted by hpeer

Mgrouch, hello. I hope you are still with me.

I have a few things to report.

1. I HAVE been able to run the EDATEC firmware update but I sill do not have the EDATEC screen coming on.

I found the problem. In the written line of code it wraps to a second line on the screen or paper. There is a “space” between words there that is not evident because it is at the end of a line.

That may be obvious to a coder but to one who is not adept at code it is a real stumper.

2. Above you indicated that after you installed the EDATEC firmware update you still had an issue. I got lost in your explanation and what to do about it. I presume you are awaiting something back from Rick????

3. The firmware package online this morning is different from the one you originally linked. I printed the original out and have it in front of me. It has slightly different instructions for the 7” and 10” screens. The online package I just pulled up and ran does NOT have that difference and the package names are new.

I am GUESSING Rick is doing something to address your problem in #2 above???

As before BBC comes up on the attached screen, but the EDATEC screen remains blank.

The last update from Edatec support I received
the issue with touchscreen is still there. They need time to investigate

[hpeer]

Mgrouch,

Thanks very much. Helpful.

Please post here if you hear anything. As will I.

[hpeer]

I received the below last night.

I am traveling now and won’t be able to get to this for a week or more.

Hi Hpeer,

I wish you all the best.

You can execute this command and then reboot device, I think the reason is the wrong kernel:
curl -s 'https://apt.edatec.cn/downloads/202403/kernel-change.sh' | sudo bash -s 6.1.58-rpi7-rpi-2712

Best Regards,
Ray

[hpeer]

Mgrouch,

I finally got settled and continued with this Edatec issue.

Ray had previously sent a PDF with a process.

Latter on the other thread Ray sent a NEW PDF (same name) to the other fellow who was successful. Following the changed instructions I was able to get the Edatec screen to come on. Major improvement.

Now I have a different issue, probably created by using some bad file names in the original PDF, but maybe not. I don’t know.

Anyway, here is a screen shot of where I now am.

I found instructions to run “systemctl status lightdm” with these results.

This response means nothing to me.

Can you help please?

[hpeer]

I should add I was having a hard time reading the screen si I tried to reconfigure the terminal font.

dpkg-reconfigure console-setup

Perhaps that screwed with lightdm?

[mgrouch]

I remember edatec support run into same issue with lightdm not starting, and they found solution to that.

You might ask them what was the solution and if it was added into their documentation.

Cheers

[hpeer]

OK, will do.

[hpeer]

Relay got back but I need a bit of hand holding. I am struggling with a good reference source for editing code.

Ray says;

Remove /etc/udev/rules.d/99-uinput.rules and modify
/usr/share/X11/xorg.conf.d/90-touchinput.conf.

user@lysmarine:~ $ cat /usr/share/X11/xorg.conf.d/90-touchinput.conf
Section "InputClass"
Identifier "calibration"
Driver "evdev"
MatchProduct "4-0014 Goodix Capacitive TouchScreen gt911 Synopsys
DesignWare I2C adapter"
MatchDevicePath "/dev/input/event*"
Option "EmulateThirdButton" "1"
Option "EmulateThirdButtonTimeout" "750"
Option "EmulateThirdButtonMoveThreshold" "30"
EndSection


Best Regards,
Ray[\quote]

When he says “remove” does that mean to use the “remove” command? Rm?
So it would look like?

rm /etc/udev/rules.d/99-uinput.rule

Then for the next bit am I to type this whole thing out or does a menu of some type come up?