WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Installing on a Tatung TWN-5213 CU  (Read 5039 times)

Offline peasthope

  • Newbie
  • *
  • Posts: 19
Re: Installing on a Tatung TWN-5213 CU
« Reply #30 on: June 24, 2026, 08:26:46 PM »
After booting from that installation, which had loglevel=8, the display ends here.

pei_bus 0000:00: resource
pei_bus 0000:00: resource
pci_bus 0000:01: resource
pei_bus 0000:01: resource
pei_bus 0000:01: resource
pei_bus 0000:01: resource
pei_bus 0000:05: resource
pei_bus 0000:05: resource 1 [io Oxic00-Oxicff]
pei_bus 0000:05: resource 2 [men 0x54000000-Ox5S7ffffff pref]
pei_bus 0000:05: resource 3 [mem 0x58000000-Ox5Sbffrffff]
pci 0000:00:00.0: Fixup for MNediaGX/Geode Slave Disconnect Boundary (@x41=@x10)
PCI: CLS 16 bytes, default 32
platforn rtc_cmos: registered platform RTC device (no PNP device found)
Trying to unpack rootfs image as initranfs...
apn: BIOS version 1.2 Flags 0x8? (Driver version 1.i6ac)
workingset: timestanp_bits=30 max_order=15 bucket_order=0
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
nfs4filelayout_init: NFSuv4 File Layout Driver Registering...
nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
fuse: init CAPI version 7.45)
cryptd: max_cpu_qlen set to 1600
randon: crng init done

Converted a photo to text with Tesseract and edited to correct some errors.
May have missed a few.  If you want to see the photo, can post it.

Any insights?

Thanks,                  ... P.
 

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12867
Re: Installing on a Tatung TWN-5213 CU
« Reply #31 on: Today at 12:57:31 AM »
Hi peasthope
... Any insights?
Nothing stands out, sorry.

Offline gadget42

  • Hero Member
  • *****
  • Posts: 1050
Re: Installing on a Tatung TWN-5213 CU
« Reply #32 on: Today at 06:14:11 AM »
** WARNING: connection is not using a post-quantum kex exchange algorithm.
** This session may be vulnerable to "store now, decrypt later" attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html
** Also see: post quantum internet 2025 - https://blog.cloudflare.com/pq-2025/

Offline peasthope

  • Newbie
  • *
  • Posts: 19
Re: Installing on a Tatung TWN-5213 CU
« Reply #33 on: Today at 09:05:22 AM »
Hello gadget42,

Thanks for replying.

does this help?

Unfortunately hardware details are minimal.  For example, the serial port
has an unusual Hirose connector for which the pinout is not specified.

Might solve the serial port by working with a breakout box.  Also, open
the case and inspect the board.

Thx,                         ... P.



Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12867
Re: Installing on a Tatung TWN-5213 CU
« Reply #34 on: Today at 09:26:48 AM »
Hi peasthope
I just reread this thread and realized something.

Since you used another machine to install onto the CF card, you
don't need to rerun the install program or use qemu every time
to try different boot codes.

Just plug the CF card into the machine, mount it, and find the
extlinux.conf file, probably under the CFs boot directory.
You can then edit the extlinux.conf file directly.

In reply #7 you stated the  "acpi=off"  boot code removed this error:
Code: [Select]
ACPI BIOS Error (bug): A valid RSDP was not found (20250807tbxfroot-222)I would leave that boot code in there.

Try adding these one at a time:
Code: [Select]
use_crs nocrs

Offline gadget42

  • Hero Member
  • *****
  • Posts: 1050
Re: Installing on a Tatung TWN-5213 CU
« Reply #35 on: Today at 05:48:01 PM »
I don't suppose you can access the BIOS on this device.

Haven't found a way in.   No hint on the screen after power up.

Five buttons and a rocker on the bezel.  A procedure with those
might open the BIOS but there are many possible combinations.

@peasthope, the user manual does show advanced boot options/procedures in section 5.3(page-17)

here is a direct link to that page for your convenience:
https://usermanual.wiki/Tatung/TWN5213/User-Guide-273866-Page-17.png
** WARNING: connection is not using a post-quantum kex exchange algorithm.
** This session may be vulnerable to "store now, decrypt later" attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html
** Also see: post quantum internet 2025 - https://blog.cloudflare.com/pq-2025/