Linux Device Hacking - Displays

Re: HOWTO : HP T5325 X11 Gui (LXDE / XFCE)

bodhi — Fri, 24 Jan 2025 15:27:15 -0600

colibri,

> I had installed LXDE on my Stora MS 2000 but the
> GUI doesn't work.

The Stora does not have graphics card. This tutorial can not be used verbatim. Basically, you should learn from this tutorial is how to install LXDE.

But for a headless box, see both tutorials:

Wiki thread

Quote

Debian Desktop

XFCE desktop Pogoplug Debian
Pogoplug Debian with XDM display manager

NOTE: There are some details in these 2 tutorials that are not applicable to the Stora.

Re: HOWTO : HP T5325 X11 Gui (LXDE / XFCE)

colibri — Fri, 24 Jan 2025 04:02:34 -0600

Hi everybody.
I had installed LXDE on my Stora MS 2000 but the GUI doesn't work.

I followed the wiki.

1) from serial consolle i stopped the countdown and I typed:

setenv set_bootargs 'setenv bootargs console=tty0 console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params'
saveenv
reset

2) from a SSH connect on my mac OS:

apt-get update ; apt-get upgrade; apt-get install keyboard-configuration locales tzdata console-data  task-lxde-desktop --install-recommends -f -y

3) there wasn't /etc/X11/xorg.conf (there was etc/X11/xorg.conf.d).
I typed

nano /etc/X11/xorg.conf

and later

ection "Files"
        FontPath        "/usr/share/fonts/X11/misc"
        FontPath        "/usr/share/fonts/X11/cyrillic"
        FontPath        "/usr/share/fonts/X11/100dpi/:unscaled"
        FontPath        "/usr/share/fonts/X11/75dpi/:unscaled"
        FontPath        "/usr/share/fonts/X11/Type1"
        FontPath        "/usr/share/fonts/X11/100dpi"
        FontPath        "/usr/share/fonts/X11/75dpi"
        # path to defoma fonts
        FontPath        "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
        Load    "record"
        Load    "type1"
        Load    "bitmap"
        Load    "dbe"
        Load    "ddc"
        Load    "dri"
        Load    "extmod"
        Load    "freetype"
        Load    "glx"
        Load    "int10"
        Load    "vbe"
EndSection

#Section "InputDevice"
#       Identifier      "Generic Keyboard"
#        Option          "XLeds" "1 2 3"
#       Option          "CoreKeyboard"
#       Option          "XkbRules"      "xorg"
#       Option "XkbModel"       "evdev"
#       Option "XkbLayout"      "us"
#       Option "XkbVariant"     "wincompat"
#       Option "XkbOptions"     "srvrkeys:none"
#       Driver          "evdev"
#       Option          "Device"        "/dev/input/event1"
#EndSection
Section "Monitor"
        Identifier      "Primary Monitor"
        Option          "DPMS"  "true"
        HorizSync       1-10000
        VertRefresh     1-10000
        Option          "NonDDCDefaultMode"             "1280x768@60"
        Option          "PreferredMode" "1280x768"
EndSection
Section "Device"
        Identifier      "Driver0"
        Screen          0
        Driver          "fbdev"
        BoardName       "XGI Volari Z11"
        BusID           "PCI:00:01:0"
        Option          "HWCursor"      "On"
        Option          "SWCursor"      "Off"
        Option          "NoAccel"       "0"
        Option          "DDCMode"       "On"
        Option          "DRI"           "On"
#       Option          "EnableSiSCtrl" "On"
        Option          "AccelMethod"   "EXA"
       Option          "UseFBDev"      "true"
        Option          "RenderAccel"   "true"
        Option          "BusType"       "PCIE"
#       Option          "MergedFB"      "true"
#       Option          "EnablePageFlip" "true"
        Option          "fbdev"         "/dev/fb0"
        Option          "ShadowFB"      "true"
EndSection
Section "Screen"
    Identifier     "Primary Screen"
    Device         "Driver0"
    Monitor        "Primary Monitor"
    DefaultDepth    24
    SubSection     "Display"
        Depth       8
        Modes      "1920x1080" "1280x768" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection     "Display"
        Depth       16
        Modes      "1920x1080" "1280x768" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection     "Display"
        Depth       24
        Modes      "1920x1080" "1280x768" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection
Section "ServerLayout"
        Identifier      "Default Layout"
#       InputDevice     "Generic Keyboard"
        Screen          0 "Primary Screen" 0 0
EndSection
Section "DRI"
        Mode    0666
EndSection
Section "ServerFlags"
        Option "DontVTSwitch" "false"
        Option "DontZap" "false"
        Option "DontZoom" "true"
EndSection

and saved it.

4) edited typing nano /etc/initramfs-tools/modules and wrote:

xgifb
fbcon

5) updated initramfs

update-initramfs -u

6) updated uInitrd

cd /boot
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-6.5.7-kirkwood-tld-1 -d initrd.img-6.5.7-kirkwood-tld-1 uInitrd

7) i edited uncomment the entries about tty1 to tty6 /etc/inittab (only in getty)

But Stora still works in line-command mode.

Where did I go wrong?

My log:


 
 
                                          done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.38.1
[/sbin/fsck.ext3 (1) -- /dev/sda1] fsck.ext3 -a -C0 /dev/sda1
rootfs: clean, 134725/3784704 files, 1385771/15113232 blocks
done.
[   25.291879][  T185] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[   25.451523][  T185] EXT4-fs (sda1): mounted filesystem 5511f184-554a-4846-82f7-0751526f7096 ro with ordered data mode. Quota mode: none.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[   26.569795][    T1] systemd[1]: Inserted module 'autofs4'
[   26.703265][    T1] systemd[1]: systemd 252.33-1~deb12u1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[   26.737216][    T1] systemd[1]: Detected architecture arm.
 
Welcome to Debian GNU/Linux 12 (bookworm)!
 
[   26.753891][    T1] systemd[1]: Hostname set to .
[   29.858642][    T1] systemd[1]: Queued start job for default target graphical.target.
[   29.907742][    T1] systemd[1]: Created slice system-getty.slice - Slice /system/getty.
[  OK  ] Created slice system-getty.slice - Slice /syste[   29.922752][    T1] systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe.
m/getty.
[  OK  ] Created slice system-modpr…lice - Slice /syst[   29.939264][    T1] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty.
em/modprobe.
[  OK  ] Created slice syste[   29.954547][    T1] systemd[1]: Created slice user.slice - User and Session Slice.
m-seria… - Slice /system/s[   29.964993][    T1] systemd[1]: Started ntpsec-systemd-netif.path.
erial-getty.
[  OK     29.974303][    T1] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
0m] Created slice user.slice - User[   29.989694][    T1] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
 and Session Sli[   30.005003][    T1] systemd[1]: Expecting device dev-ttyS0.device - /dev/ttyS0...
ce.
[  OK  ] Start[   30.014405][    T1] systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
ed ntpsec-systemd-netif[   30.027444][    T1] systemd[1]: Reached target nss-lookup.target - Host and Network Name Lookups.
.path.
[  OK  [   30.038651][    T1] systemd[1]: Reached target slices.target - Slice Units.
] Started systemd-ask-p[   30.048203][    T1] systemd[1]: Reached target swap.target - Swaps.
asswo… Request[   30.057140][    T1] systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
s to Wall Directory Watch.
[  OK  ] Set up automount proc-sys-…rmats File System Automount Point.
         Expecting device dev-ttyS0.device - /dev/ttyS0...
[  OK  ] Reached target integrityse…Local Integrity Protected Volumes.
[  OK  ] Reached target nss-lookup.…m - Host and Network Name Lookups.
[  OK  ] Reached target slices.target - Slice Units.
[  OK  ] Reached target swap.target - Swaps.
[  OK  ] Reached target veritysetup… - Local Verity Protected Volumes.
[   30.138168][    T1] systemd[1]: Listening on rpcbind.socket - RPCbind Server Activation Socket.
[  OK  ] Listening on[   30.149987][    T1] systemd[1]: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket.
 rpcbind.socke… RPCbi[   30.161851][    T1] systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
nd Server Activation Socket.
[  OK     30.175885][    T1] systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket.
0m] Listening on systemd-fsckd…sck to[   30.188640][    T1] systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
 fsckd communication Socket.
[  OK     30.202384][    T1] systemd[1]: Listening on systemd-journald.socket - Journal Socket.
0m] Listening on systemd-initc… initctl Compatibility Named Pipe.
[  OK  ] Listening on system[   30.222531][    T1] systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
d-journ…socket - Journal Audit Socket.
[   30.234289][    T1] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[  OK  ] Listening on system[   30.247389][    T1] systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages).
d-journ…t - Journal Socket (/dev/log).
[  OK  ] Listening on systemd-journald.socket - Journal Socket.
[  OK  ] Listening on systemd-udevd….socket - udev Control Socket.
[  OK  ] Listening on systemd-udevd…l.socket - udev Kernel Socket.
[   30.296930][    T1] systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System...
         Mounting dev-mqueue.mount▒▒POSIX Message Queue File System...
[   30.333595][    T1] systemd[1]: Mounting proc-fs-nfsd.mount - NFSD configuration filesystem...
         Mounting proc-fs-nfsd.moun…- NFSD configuration filesystem...
[   30.387016][    T1] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
         Mounting sys-kernel-debug.… - Kernel Debug File System...
[   30.425053][    T1] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
         Mounting sys-k[   30.448142][    T1] systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).
ernel-tracin… - Kernel Trace File System...
[   30.500955][    T1] systemd[1]: Starting fake-hwclock.service - Restore / save the current clock...
         Starting fake-hwclock.serv…estore / save the current clock...
[   30.544606][    T1] systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
         Starting kmod-static-nodes…ate List of Static Device Nodes...
[   30.637805][    T1] systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...
         Starting modprobe@configfs…m - Load Kernel Module configfs...
[   30.707959][    T1] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
         Starting modprobe@dm_mod.s…[0m - Load Kernel Module dm_mod...
[   30.757767][    T1] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
         Starting modprobe@drm.service - Load Kernel Module drm...
[   30.837580][    T1] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
         Starting modprobe@efi_psto…- Load Kernel Module efi_pstore...
[   30.907550][    T1] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...
         Starting modprobe@fuse.ser…e - Load Kernel Module fuse...
[   30.977790][    T1] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
         Starting modprobe@loop.ser…e - Load Kern[   31.010908][    T1] systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root).
el Module loop...
[   31.087506][    T1] systemd[1]: Starting systemd-journald.service - Journal Service...
         Starting systemd-journald.service - Journal Service...
[   31.157790][    T1] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
         Starting systemd-modules-l…rvice - Load Kernel Modules...
[   31.247751][    T1] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
         Starting systemd-remount-f…nt Root and Kernel File Systems...
[   31.357762][    T1] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices...
         Starting systemd-udev-trig…[0m - Coldplug All udev Devices...
[   31.536555][    T1] systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System.
[  OK  ] Mounted dev-mqueue.mount▒▒- POSIX Message Queue File System.
[   31.580414][    T1] systemd[1]: Mounted proc-fs-nfsd.mount - NFSD configuration filesystem.
[  OK  ] Mounted proc-fs-nfsd.mount…m - NFSD configuration filesystem.
[   31.622265][    T1] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System.
[   31.646346][  T243] EXT4-fs (sda1): re-mounted 5511f184-554a-4846-82f7-0751526f7096 r/w. Quota mode: none.
[  OK  ] Mounted sys-kernel-debug.m…nt - Kernel Debug File System.
[   31.703970][    T1] systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System.
[  OK  ] Mounted sys-kernel-tracing…nt[   31.762120][    T1] systemd[1]: Finished fake-hwclock.service - Restore / save the current clock.
 - Kernel Trace File System.
[  OK  ] Finished fake-hwclock.serv… Restore / save the current clock.
[   31.810661][    T1] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes.
[  OK  ] Finished kmod-static-nodes…reate List of Static D[   31.853051][    T1] systemd[1]: modprobe@configfs.service: Deactivated successfully.
evice Nodes.
[   31.896808][    T1] systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs.
[  OK  ] Finished modprobe@configfs…[0m - Load Kernel Module configfs.
[   31.930679][    T1] systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
[   31.968772][    T1] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
[  OK  ] Finished modprobe@dm_mod.s…e [   32.001345][    T1] systemd[1]: modprobe@drm.service: Deactivated successfully.
- Load Kernel Module dm_mod.
[   32.046465][    T1] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
[  OK  ] Finished modprobe@drm.service - Load Kernel Module drm.
[   32.080750][    T1] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
[   32.118759][    T1] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
[  OK  ] Finished modprobe@efi_psto…m - Lo[   32.151506][    T1] systemd[1]: modprobe@fuse.service: Deactivated successfully.
ad Kernel Module efi_pstore.
[   32.188762][    T1] systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.
[  OK  ] Finished modprobe@fuse.service [   32.221485][    T1] systemd[1]: modprobe@loop.service: Deactivated successfully.
- Load Kernel Module fuse.
[   32.268344][    T1] systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
[  OK  ] Finished modprobe@loop.service - Load Kernel Module loop.
[   32.306581][    T1] systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.
[  OK  ] Finished systemd-modules-l…service - Load Kernel Modules.
[   32.341659][    T1] systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.
[  OK  ] Finished systemd-remount-f…ount Root and Kernel File Systems.
[   32.447355][    T1] systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System...
         Mounting sys-fs-fuse-conne… - FUSE Control File System...
[   32.550178][    T1] systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System...
         Mounting sys-k[   32.598755][    T1] systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
ernel-config…ernel Configuration File System...
[   32.687390][    T1] systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
[   32.817208][    T1] systemd[1]: Starting systemd-random-seed.service - Load/Save Random Seed...
         Startin[   32.857857][    T1] systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
g systemd-random-se…ice - Load/Save Random Seed...
[   32.958345][    T1] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
         Starting systemd-sysctl.se…ce - Apply Kernel Variables...
[   33.063398][    T1] systemd[1]: Starting systemd-sysusers.service - Create System Users...
[   33.111335][   T60] random: crng init done
         Starting systemd-sysusers.…rvice - Create System Users...
[   33.262774][    T1] systemd[1]: Started systemd-journald.service - Journal Service.
[  OK  ] Started systemd-journald.service - Journal Service.
[  OK  ] Mounted sys-fs-fuse-connec…nt - FUSE Control File System.
[  OK  ] Mounted sys-kernel-config.… Kernel Configuration File System.
[  OK  ] Finished systemd-random-se…rvice - Load/Save Random Seed.
[  OK  ] Finished systemd-sysctl.service - Apply Kernel Variables.
         Starting systemd-journal-f…h Journal to Persistent Storage...
[  OK  ] Finished systemd-sysusers.service - Create System Users.
         Starting systemd-tmpfiles-…ate Static Device Nodes in /dev...
[   33.874780][  T239] systemd-journald[239]: Received client request to flush runtime journal.
[  OK  ] Finished systemd-udev-trig…e - Coldplug All udev Devices.
         Starting ifupdown-pre.serv…ynchronize boot up for ifupdown...
[  OK  ] Finished systemd-tmpfiles-…reate Static Device Nodes in /dev.
[  OK  ] Reached target local-fs-pr…reparation for Local File Systems.
         Mounting tmp.mount - /tmp...
         Starting systemd-udevd.ser…ger for Device Events and Files...
[  OK  ] Mounted tmp.mount - /tmp.
[  OK  ] Reached target local-fs.target - Local File Systems.
         Starting plymouth-read-wri…mouth To Write Out Runtime Data...
         Starting systemd-binfmt.se…et Up Additional Binary Formats...
[  OK  ] Finished plymouth-read-wri…lymouth To Write Out Runtime Data.
         Mounting proc-sys-fs-binfm…utable File Formats File System...
[  OK  ] Mounted proc-sys-fs-binfmt…ecutable File Formats File System.
[  OK  ] Finished systemd-binfmt.se… Set Up Additional Binary Formats.
[  OK  ] Finished systemd-journal-f…ush Journal to Persistent Storage.
         Starting systemd-tmpfiles-…te System Files and Directories...
[  OK  ] Started systemd-udevd.serv…nager for Device Events and Files.
         Starting plymouth-start.se…[0m - Show Plymouth Boot Screen...
[  OK  ] Started plymouth-start.ser…e - Show Plymouth Boot Screen.
[  OK  ] Started systemd-ask-passwo…uests to Plymouth Directory Watch.
[  OK  ] Reached target cryptsetup.…get - Local Encrypted Volumes.
         Starting modprobe@dm_mod.s…[0m - Load Kernel Module dm_mod...
         Starting modprobe@efi_psto…- Load Kernel Module efi_pstore...
         Starting modprobe@loop.ser…e - Load Kernel Module loop...
[  OK  ] Finished systemd-tmpfiles-…eate System Files and Directories.
[  OK  ] Finished modprobe@dm_mod.s…e - Load Kernel Module dm_mod.
[  OK  ] Finished modprobe@efi_psto…m - Load Kernel Module efi_pstore.
[  OK  ] Finished modprobe@loop.service - Load Kernel Module loop.
         Mounting run-rpc_pipefs.mount - RPC Pipe File System...
[  OK  ] Started resolvconf.service… - Nameserver information manager.
[  OK  ] Reached target network-pre…get - Preparation for Network.
         Starting rpcbind.service - RPC bind portmap service...
         Starting systemd-update-ut…rd System Boot/Shutdown in UTMP...
[  OK  ] Mounted run-rpc_pipefs.mount - RPC Pipe File System.
[  OK  ] Reached target rpc_pipefs.target.
         Starting nfs-blkmap.servic…NFS block layout mapping daemon...
         Starting nfs-idmapd.servic…- NFSv4 ID-name mapping service...
         Starting nfsdcld.service▒▒ - NFSv4 Client Tracking Daemon...
[  OK  ] Reached target nfs-client.target - NFS client services.
[  OK  ] Started rpcbind.service - RPC bind portmap service.
[  OK  ] Started nfs-blkmap.service… pNFS block layout mapping daemon.
[  OK  ] Started nfs-idmapd.service…m - NFSv4 ID-name mapping service.
[  OK  ] Started nfsdcld.service - NFSv4 Client Tracking Daemon.
[  OK  ] Finished systemd-update-ut…cord System Boot/Shutdown in UTMP.
[  OK  ] Reached target remote-fs-p…eparation for Remote File Systems.
[  OK  ] Reached target remote-fs.target - Remote File Systems.
[  OK  ] Reached target rpcbind.target - RPC Port Mapper.
[  OK  ] Reached target sysinit.target - System Initialization.
[  OK  ] Started cups.path - CUPS Scheduler.
[  OK  ] Started anacron.timer - Trigger anacron every hour.
[  OK  ] Started apt-daily.timer - Daily apt download activities.
[  OK  ] Started apt-daily-upgrade.… apt upgrade and clean activities.
[  OK  ] Started dpkg-db-backup.tim… Daily dpkg database backup timer.
[  OK  ] Started e2scrub_all.timer▒▒etadata Check for All Filesystems.
[  OK  ] Started exim4-base.timer - Daily exim4-base housekeeping.
[  OK  ] Started man-db.timer - Daily man-db regeneration.
[  OK  ] Started ntpsec-rotate-stat…mer - Rotate ntpd stats daily.
[  OK  ] Started systemd-tmpfiles-c… Cleanup of Temporary Directories.
[  OK  ] Reached target paths.target - Path Units.
[  OK  ] Reached target timers.target - Timer Units.
[  OK  ] Listening on avahi-daemon.…NS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on cups.socket - CUPS Scheduler.
[  OK  ] Listening on dbus.socket▒▒- D-Bus System Message Bus Socket.
[  OK  ] Reached target sockets.target - Socket Units.
[  OK  ] Reached target basic.target - Basic System.
[  OK  ] Started anacron.service - Run anacron jobs.
         Starting avahi-daemon.serv…e - Avahi mDNS/DNS-SD Stack...
         Starting busybox-syslogd.service - LSB: Starts syslogd...
[  OK  ] Started cron.service -…kground program processing daemon.
         Starting dbus.service - D-Bus System Message Bus...
         Starting dphys-swapfile.se…unmount, and delete a swap file...
         Starting dundee.service - DUN service...
         Starting e2scrub_reap.serv…e ext4 Metadata Check Snapshots...
[  OK  ] Started ntpsec-systemd-netif.service.
         Starting ofono.service - Telephony service...
         Starting systemd-logind.se…ice - User Login Management...
         Starting udisks2.service - Disk Manager...
[  OK  ] Found device dev-ttyS0.device - /dev/ttyS0.
[  OK  ] Finished e2scrub_reap.serv…ine ext4 Metadata Check Snapshots.
[  OK  ] Started busybox-syslogd.service - LSB: Starts syslogd.
         Starting busybox-klogd.service - LSB: Starts klogd...
[  OK  ] Started dbus.service - D-Bus System Message Bus.
[  OK  ] Started busybox-klogd.service - LSB: Starts klogd.
         Starting connman.service - Connection service...
         Starting wpa_supplicant.service - WPA supplicant...
[  OK  ] Started ofono.service - Telephony service.
[  OK  ] Started avahi-daemon.service - Avahi mDNS/DNS-SD Stack.
[  OK  ] Started dundee.service - DUN service.
[  OK  ] Started systemd-logind.service - User Login Management.
[ ***  ] (1 of 5) Job connman.service/start running (26s / 1min 53s)
[   56.617230][  T268] lm75 0-0048: supply vs not found, using dummy regulator
[   56.691115][  T268] hwmon hwmon0: temp1_input not attached to any thermal zone
[   ***] (2 of 5) Job dphys-swapfile.service/start running (27s / no limit)
[    **] (3 of 5) Job wpa_supplicant.service/start running (29s / 1min 53s)
[   59.262417][  T306] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[  OK  ] Listening on systemd-rfkil…l Switch Status /dev/rfkill Watch.
[  *** ] (4 of 5) Job udisks2.service/start running (33s / 1min 50s)
[   63.194115][  T391] Bluetooth: Core ver 2.22
[   63.212022][  T391] NET: Registered PF_BLUETOOTH protocol family
[   63.224655][  T391] Bluetooth: HCI device and connection manager initialized
[   63.233306][  T391] Bluetooth: HCI socket layer initialized
[   63.239695][  T391] Bluetooth: L2CAP socket layer initialized
[   63.245598][  T391] Bluetooth: SCO socket layer initialized
[***   ] (4 of 5) Job udisks2.service/start running (34s / 1min 50s)
[  OK  ] Finished dphys-swapfile.se…t/unmount, and delete a swap file.
[  OK  ] Started wpa_supplicant.service - WPA supplicant.
[  OK  ] Finished ifupdown-pre.serv… synchronize boot up for ifupdown.
         Starting networking.service - Raise network interfaces...
[  OK  ] Started connman.service - Connection service.
         Starting connman-wait-onli…ork to be configured by ConnMan...
         Starting polkit.service - Authorization Manager...
[   78.740611][  T457] bpfilter: Loaded bpfilter_umh pid 461
[   78.756363][  T461] Started bpfilter
[  OK  ] Started polkit.service - Authorization Manager.
         Starting systemd-hostnamed.service - Hostname Service...
[ ***  ] (4 of 4) Job udisks2.service/start running (53s / 1min 50s)
[  OK  ] Started systemd-hostnamed.service - Hostname Service.
[   89.845122][  T497] 8021q: 802.1Q VLAN Support v1.8
[  OK  ] Finished connman-wait-onli…twork to be configured by ConnMan.
[  OK  ] Started udisks2.service - Disk Manager.
[  OK  ] Finished networking.service - Raise network interfaces.
[  OK  ] Reached target network.target - Network.
[  OK  ] Reached target network-online.target - Network is Online.
         Starting cups.service - CUPS Scheduler...
         Starting exim4.service… LSB: exim Mail Transport Agent...
         Starting nfs-mountd.service - NFS Mount Daemon...
         Starting ntpsec.service - Network Time Service...
         Starting rc-local.service▒▒m - /etc/rc.local Compatibility...
         Starting rpc-statd.service…us monitor for NFSv2/3 locking....
         Starting ssh.service - OpenBSD Secure Shell server...
         Starting systemd-user-sess…vice - Permit User Sessions...
[  OK  ] Started nfs-mountd.service - NFS Mount Daemon.
[  OK  ] Started rpc-statd.service▒▒atus monitor for NFSv2/3 locking..
[  OK  ] Started ntpsec.service - Network Time Service.
[  OK  ] Finished systemd-user-sess…ervice - Permit User Sessions.
[  OK  ] Started cups.service - CUPS Scheduler.
[  OK  ] Started cups-browsed.servi…e CUPS printers available locally.
         Starting lightdm.service - Light Display Manager...
         Starting nfs-server.service - NFS server and services...
[  OK  ] Started rc-local.service - /etc/rc.local Compatibility.
         Starting plymouth-quit-wai… until boot process finishes up...
[  OK  ] Started ssh.service - OpenBSD Secure Shell server.
[   ***] (3 of 4) Job plymouth-quit-wait.ser…tart running (1min 36s / no limit)
[  126.190510][  T679] NFSD: Using nfsdcld client tracking operations.
[  OK  ] Finished nfs-server.service - NFS server and services.
         Starting rpc-statd-notify.…- Notify NFS peers of a restart...
[  OK  ] Started rpc-statd-notify.s…m - Notify NFS peers of a restart.
[  OK  ] Created slice user-0.slice - User Slice of UID 0.
         Starting user-runtime-dir@…r Runtime Directory /run/user/0...
[     *] (4 of 4) Job exim4.service/start running (1min 49s / 6min 13s)
[  160.614792][  T912] systemd[912]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
 
Debian GNU/Linux 12 debiandebian login: root
root
Password: root
 
Linux debian 6.5.7-kirkwood-tld-1 #2 PREEMPT Wed Oct 18 21:14:11 PDT 2023 armv5tel
 
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jan 24 01:51:37 PST 2025 from 192.168.0.2 on pts/0
debian
192.168.0.17
NETGEAR MS2000 / MS2110 aka Stora
Linux version 6.5.7-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #2 PREEMPT Wed Oct 18 21:14:11 PDT 2023
Debian 12.9
Fri Jan 24 01:52:38 PST 2025 up 3 minutes
root@debian:~#
 ttyS0
 
debian login:

the code before "done" (at the beginning of the code above) I can't copy it

Re: DisplayLink USB 2.0 FB driver removal

bodhi — Sun, 29 Dec 2024 13:37:48 -0600

Kurlon,

Very nice!

There are countless numbers of USB DisplayLink users out there who will benefit from this.

I'll change the thread subject and make this a sticky thread.

Re: DisplayLink USB 2.0 FB driver removal

Kurlon — Sat, 28 Dec 2024 19:14:26 -0600

My current setup I don't use an xorg conf, I let it auto-detect and it correctly identifies the card as 'modesetting'.

Once the box is booted, you may need to kick the displaylink device to get it out of 'presetup' mode acting like a mass storage device with an antique Windows installer on it an into video mode. I do this via udev rule:

/etc/udev/rules.d/60-displaylink.rules

ATTR{idVendor}=="17e9", ATTR{bConfigurationValue}=="2", RUN+="/usr/bin/dlconfig %p"

/usr/bin/dlconfig

#! /bin/bash
if [ -e /sys$1/bConfigurationValue ]; then
#    /sbin/modprobe udlfb console=1 fb_defio=1 shadow=0
    echo 1 > /sys$1/bConfigurationValue
fi;

The commented line is for getting the older FB driver up and going with a console, but aren't needed for the DRM driver. You can check if your system sees a display with the following:

root@gfn:~# for p in /sys/class/drm/*/status; do con=${p%/status}; echo -n "${con#*/card?-}: "; cat $p; done
VGA-1: connected

In my case the card is live, VGA output. Both of my docs, an HP and Kensington both only claim to have VGA output, even when using DVI-I only devices connected to them. If you get this far but don't have a working video signal, you can force the video mode by adding a kernel command line to uEnv.txt:

/boot/uEnv.txt

custom_params=video=VGA-1:1280x720@60

https://wiki.archlinux.org/title/Kernel_mode_setting has good docs for this, as this is a fully functioning KMS device now, all the tricks work with it. Kernel config attached, it has both the old and new Displaylink drivers added, along with my SIS2VGA.

Because the video device isn't active until later in boot, once udev is live and processing, the normal start routine for say lightdm fires off way too soon to see video, so at the moment I'm logging in via console and just kicking off startx manually. I'll have to chase this a bit later, though really with only 128MB RAM this box is at it's limits trying to be a proper workstation. Also, if you're going to forward X to this machine from remote without an SSH tunnel, you'll need to edit /etc/X11/xinit/xserverrc to change nolisten to listen, and be aware of the giant security hole doing so creates.

Re: DisplayLink USB 2.0 FB driver removal

bodhi — Sat, 28 Dec 2024 18:48:54 -0600

Kurlon,

> So, just went through this battle. I can say, the
> new DRM version of the driver works well, damage
> is supported, screen corruption seems minimal.
> Running Firefox remote to my GoFlex via direct tcp
> X11 (no SSH tunnel) I was able to do full screen
> video at 1280x720.

Cool! it would be great if you can post your kernel and xorg config.

I've not done anything for the Dove DRM on HP T5335z. But if I do in the future, nice to have something DRM to cross reference.

Re: DisplayLink USB 2.0 FB driver removal

Kurlon — Sat, 28 Dec 2024 18:13:27 -0600

So, just went through this battle. I can say, the new DRM version of the driver works well, damage is supported, screen corruption seems minimal. Running Firefox remote to my GoFlex via direct tcp X11 (no SSH tunnel) I was able to do full screen video at 1280x720. Now, on the pain side for some reason the DRM driver seems REALLY dumb about picking outputs and screen modes vs the older FB version that would usually pick something at least usable if not a match to the monitor.

Now, theoretically my old SIS2VGA was depreciated with 6.2... it's still in kernel as of 6.12, still just as slow and undocumented but they haven't nuked it yet. (Note, most distros also blacklist it's modules by default.)

Re: Lilliput USB touch screen

PhilCaas — Tue, 30 Jul 2024 03:19:23 -0500

thanks for letting me know
i need help with this one
https://lilliput.net/monitors/touch/resistive/lilliput-fa1045-npct

Re: Lilliput USB touch screen

dhargens — Mon, 29 Jul 2024 17:31:31 -0500

PhilCaas Wrote:
-------------------------------------------------------
> I'm trying to find the same instructions but for
> the model FA1045-NP/C/T
> this
> one
> can someone help me?

Your link gives a 404 error - the link has too many chars, so deleting the extra "http://"; at the end gets you there.

Re: Lilliput USB touch screen

PhilCaas — Mon, 29 Jul 2024 08:39:13 -0500

I'm trying to find the same instructions but for the model FA1045-NP/C/T this one
can someone help me?

Re: dpf-ax: unsupported dpf - requests

ms1958 — Thu, 18 Jan 2024 12:50:41 -0600

Hello Superelchi,
I bought 3 DPF's on Aliexpress a few years ago.
2 I was able to flash the firmware with your help
fw_sarah_welcome_you.bin on windows.

I couldn't flash the third dpf.

(attached to the dump)

Running on windows - unable to detect flash size
Reading 100000 bytes from flash...
Flash written to file 'fulldump_win_20240118-131337.bin'.

Looking for firmware.............: Found (coby, 320x240 px).
Looking for Openwin..............: Found.
Looking for LcdIniTbl............: Found.
Looking for backlight & contrast.: Found, Found.
Looking for known signatures.....: None.

Sorry, no matching dpf found.

But the following model has a partial signature match: acme_4.
This firmware MAY work for your dpf.

#
I would be very happy about your help!
Greetings, Manfred

Re: HOWTO : HP T5325 X11 Gui (LXDE / XFCE)

bodhi — Sat, 28 Oct 2023 13:48:40 -0500

Hi Gert,

> Realizing this is an old thread but I recently got
> a HP T5325 thin client and managed, following the
> instructions found here, to install Debian 11 on
> it but alas without X
> It looks like the modules xgifb and
> fbcon are not found, maybe with the newer
> kernel they are called differently?
>
> Only way I can access the machine is over the
> inbuilt serial port or network.
> The monitor stays in standby.
>
> Any ideas on this?
>

Unfortunately the new kernels does not directly support frame buffer anymore. So xgifb, which is an old ZGI fb driver, is no longer available.

There is a new simple DRM (Direct Rendering Manager) that supports frame buffer. But I have not got around to test it. So is is not in my released kernel either.

Re: HOWTO : HP T5325 X11 Gui (LXDE / XFCE)

Gert — Sat, 28 Oct 2023 12:09:00 -0500

Hi,

Realizing this is an old thread but I recently got a HP T5325 thin client and managed, following the instructions found here, to install Debian 11 on it but alas without X
It looks like the modules xgifb and fbcon are not found, maybe with the newer kernel they are called differently?

Only way I can access the machine is over the inbuilt serial port or network.
The monitor stays in standby.

Any ideas on this?

Regards,
Gert

root@t5325:~# uname -a                                                          
Linux t5325 5.10.0-26-marvell #1 Debian 5.10.197-1 (2023-09-29) armv5tel GNU/Linux

root@t5325:~# cat /etc/issue                                                    
Debian GNU/Linux 11 \n \l  
  
root@t5325:~# ls /lib/modules/5.10.0-26-marvell/kernel/drivers/video/fbdev/
arkfb.ko  mb862xx   s3fb.ko     tdfxfb.ko  vt8623fb.ko
core      pm3fb.ko  smscufx.ko  udlfb.ko

Re: Recommend most usable movie format etc for digital picture frame?

Gravelrash — Wed, 29 Mar 2023 16:31:00 -0500

try with 800 x 600 - you will have zero joy with 720 unless the box can magically autoscale - id be doing mine around 480 or similar and seeing how thet goes... most of teh time the picture frame stuff works with 640x480 or 320x240

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

bodhi — Mon, 13 Feb 2023 21:38:02 -0600

Added to the Wiki thread.

Quote

Display

dpf-ax
Tritton USB2VGA
HP T5325 X11 GUI (LXDE)
LED daemon for Pogoplug Debian
Netgear ReadyNAS RN104 Front LCD Display

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

bodhi — Sun, 12 Feb 2023 14:32:10 -0600

Very nice!

/* Flash back light */ would be quite useful as a visual indicator for something above threshold that needs a login.

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

tme — Sun, 12 Feb 2023 07:36:44 -0600

I was curious about whether there were further escape sequence codes than just '+' and '-' (back light on and off). Yes, there are:

tme@rn104:/tmp$ wget https://github.com/torvalds/linux/raw/master/drivers/auxdisplay/charlcd.c

tme@rn104:/tmp$ grep "case.**/" charlcd.c
	case 'D':	/* Display ON */
	case 'd':	/* Display OFF */
	case 'C':	/* Cursor ON */
	case 'c':	/* Cursor OFF */
	case 'B':	/* Blink ON */
	case 'b':	/* Blink OFF */
	case '+':	/* Back light ON */
	case '-':	/* Back light OFF */
	case '*':	/* Flash back light */
	case 'f':	/* Small Font */
	case 'F':	/* Large Font */
	case 'n':	/* One Line */
	case 'N':	/* Two Lines */
	case 'l':	/* Shift Cursor Left */
	case 'r':	/* shift cursor right */
	case 'L':	/* shift display left */
	case 'R':	/* shift display right */
	case 'k': {	/* kill end of line */
	case 'I':	/* reinitialize display */
	case 'x':	/* gotoxy : LxXXX[yYYY]; */
	case 'y':	/* gotoxy : LyYYY[xXXX]; */

Scrolling is not supported. Printing New Line ('\n') on the display moves the (by default invisible) cursor to the beginning of the other line (above or below). Shifting left and right works, but isn't very useful since only 16 characters per line are stored in the display.

Of course, not all sequence codes work on the Winstar WH1602G LCD. Clearing the display and moving the cursor to the beginning of the first line does not require an escape sequence, though. Just printing Form Feed ('\f') on the display does the trick.

Reagrds,
Trond Melen

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

tme — Sun, 12 Feb 2023 06:16:22 -0600

Yes, '/dev/lcd' is the correct device, and yes, the hardware interface is direct GPIO.

Quote
Arnaud Ebalard
The LCD module consumes 8 GPIO of the SoC. In order to get additional GPIOs to connect to front buttons and LEDs, NETGEAR has added on the main board an iomuxer connected to the I2C bus, namely a NXP PCA9554. It provides eight additional GPIOs.

I assume 'lcd4linux' is obsolete. None of the display configurations in '/etc/lcd4linux.conf' uses '/dev/lcd' as its "port". 'apt' refused to uninstall the package because '/etc/init.d/lcd4linux stop' failed. I had to modify this script first to be able make 'apt remove' work.

The next important step to learn was how to switch on the backlight. As described in MicroJoe's adventures this may be done by sending an escape sequence to the device. I added this to '/etc/rc.local':

tme@rn104:~$ tail /etc/rc.local

# Running on a box with an LCD display?
if [ -w /dev/lcd ]; then

	# Say something optimistic and switch on the backlight
	/usr/bin/printf '-New boot, new\npossibilities!\n' > /dev/lcd
	/usr/bin/printf '\x1b[L+' > /dev/lcd
fi

exit 0

Then I had to decide what to display. CPU load, memory usage, block IO or network traffic? Very little fits on the display, so one would probably need to login anyhow and to get the real picture. IP address, network connectivity and box temperature? At least complete information fits on the display, but in stead I decided to display boot and current time in the format "2023-02-12 13:14". Boot time will tell me if there has been a crash or power outage, and current time will tell me if the system is frozen or its clock has drifted way off. These are handy pieces of information when deciding if a login is required.

The display is updated every minute through 'crontab':

tme@rn104:~$ sudo crontab -l | tail -1
* * * * * /root/lcd-uptime.sh

tme@rn104:~$ sudo cat /root/lcd-uptime.sh
#!/bin/bash
#
# Script updating the LCD
# To be run by crontab every minute

# Size of display
ncols=16
nrows=2

# Up time exceeds 10 minutes?
up=$( /usr/bin/cut -d. -f1 /proc/uptime )
if (( $up > 600 )); then

	# Info to be displayed
	boot=$( /usr/bin/uptime -s | /usr/bin/cut -c -$ncols )
	curr=$( /bin/date -Im | /usr/bin/tr 'T' ' ' | /usr/bin/cut -c -$ncols )

	# Print info on the display
	if (( $nrows > 1 )); then
		printf "$boot\n" > /dev/lcd
	fi
	printf "$curr\n"  > /dev/lcd
fi

exit 0

Boot and/or current time may of course be substituted by an error message when network connectivity is lost, when the box temperature exceeds some limit or some other issue needs attention, but that's for another post.

Thank You All for Your advice!

Regards,
Trond Melen

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

bodhi — Sat, 11 Feb 2023 17:05:03 -0600

> From my earlier linked article

Quote

Now that the
> hard part — configuring the kernel and the
> device tree — is done, we can very easily print
> stuff on the screen by just writing to the
> /dev/lcd file.
>

>

Yes. That article is clear about how you would write to the LCD. Thumbs up!

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

bodhi — Sat, 11 Feb 2023 16:45:47 -0600

> From my earlier linked article

> Now that the
> hard part — configuring the kernel and the
> device tree — is done, we can very easily print
> stuff on the screen by just writing to the
> /dev/lcd file.

Yes, I saw that it was ready.

auxdisplay {
                compatible = "hit,hd44780";
                data-gpios = <&gpio1 25 GPIO_ACTIVE_HIGH>,
                                <&gpio1 26 GPIO_ACTIVE_HIGH>,
                                <&gpio1 27 GPIO_ACTIVE_HIGH>,
                                <&gpio1 29 GPIO_ACTIVE_HIGH>;
                enable-gpios = <&gpio1 24 GPIO_ACTIVE_HIGH>;
                rs-gpios = <&gpio1 22 GPIO_ACTIVE_HIGH>;
                rw-gpios = <&gpio1 23 GPIO_ACTIVE_HIGH>;
                backlight-gpios = <&gpio1 21 GPIO_ACTIVE_LOW>;
                display-height-chars = <2>;
                display-width-chars = <16>;
        };

And I thought the easiest way to see how it is used is somewhere in stock OS.

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

rayknight — Sat, 11 Feb 2023 16:36:22 -0600

From my earlier linked article

Quote

Now that the hard part — configuring the kernel and the device tree — is done, we can very easily print stuff on the screen by just writing to the /dev/lcd file.

Ray

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

bodhi — Sat, 11 Feb 2023 15:05:38 -0600

> From the pictures mentioned the number of pins on
> the display's header connectors is 4+13=17, but
> the wire count of the connected flat cable is only
> 2+10=12. It may be very well GPIO.

The Kernel Kconfig indicates that there is some GPIO involved

Quote

config HD44780
tristate "HD44780 Character LCD support"
depends on GPIOLIB

If you can boot back to stock OS, look for some scripts that echo the Netgear messages in the init scripts during boot.

Quote

The Netgear ReadyNAS RN104 has a 2 by 16 character display. It's a Winstar WH1602G LCD. Pictures here. U-boot (v2011.12) writes "NETGEAR Storage Welcome" on the display when it starts, and "Booting.." before booting Linux. This latter text sticks since Linux makes no effort to change it.

I imagine they'd want to do this in userspace so it is not needed to hardcode it in kernel build. Also the "Booting..." message most definitely is a userspace message.

=====

Here is where the default string (kernel name) got displayed in the driver code:

drivers/auxdisplay/charlcd.c

=====

Definitely GPIO control.

https://github.com/torvalds/linux/blob/master/drivers/auxdisplay/hd44780.c

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

rayknight — Sat, 11 Feb 2023 13:35:55 -0600

You might want to take a look at HD44780 LCD I²C screen using Linux mainline charlcd driver. That appears to have enough information to be able to determine if lcd4linux already support the device and to add support to lcd4llinux if it does not.

Ray

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

tme — Sat, 11 Feb 2023 10:58:42 -0600

Hi Mijzelf,

From the pictures mentioned the number of pins on the display's header connectors is 4+13=17, but the wire count of the connected flat cable is only 2+10=12. It may be very well GPIO.

Regards,
Trond Melen

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

Mijzelf — Sat, 11 Feb 2023 10:39:02 -0600

Quote

HD44780: open(/dev/lcd) failed: Operation not permitted

What does 'ls -l /dev/lcd*' say?

Quote

What indicates that the LCD display on the RN104 is a USB device and not a parallel port device?

It's not a patallel port device. What was the last time you saw a parallel port? It could be usb, or i2c, or gpio connected, or... . The driver should take care for that.

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

tme — Sat, 11 Feb 2023 10:31:17 -0600

Hi again,

I followed you links and tried the BWCT display configuration, also without success:

root@rn104:~# ls -AlF /dev/lcd*
crw-rw---- 1 root lp 10, 156 Feb 11 12:04 /dev/lcd

root@rn104:~# head -8 /etc/lcd4linux.conf
Display BWCT-16x2 {
    Driver 'BWCT'
    Size '16x2'
    Contrast 220
    asc255bug 1
    Icons 1
#   Port 'libusb'
}

root@rn104:~# lcd4linux -Fv
LCD4Linux 0.11.0-SVN-1193 starting
[DBus] Error connecting to the dbus session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

[MPD] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
[raspi] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
BWCT: $Rev: 975 $
BWCT: scanning USB for BWCT LCD...
BWCT: could not find a BWCT USB LCD
Error initializing driver BWCT: Exit!

The picture linked to in the first post shows a bunch of wires to the display, presumably 14 or 16. What indicates that the LCD display on the RN104 is a USB device and not a parallel port device?

Regards,
Trond Melen

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

tme — Sat, 11 Feb 2023 10:06:44 -0600

Thanks, Mijzelf, for your advice!

I modifyed 'Port' to '/dev/lcd' for all the three displays in 'lcd4linux.conf' and tested. The error message 'No such device or address' switched to 'Operation not permitted'. So still no success:

root@drodle:~# lcd4linux -Fv
LCD4Linux 0.11.0-SVN-1193 starting
[DBus] Error connecting to the dbus session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

[MPD] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
[raspi] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
HD44780: $Rev: 1202 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/lcd
HD44780: open(/dev/lcd) failed: Operation not permitted
HD44780: could not initialize parallel port!
HD44780: start display failed!
Error initializing driver HD44780: Exit!

I'll check your links.

Regards,
Trond Melen

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

Mijzelf — Sat, 11 Feb 2023 09:47:44 -0600

I can't imagine you'd need /dev/parport0. I suppose that is used when you have connected an LCD display to the parallel port, and lcd4linux does the bitbanging in user mode. But you have a driver which should do that work. According to the documentation there should be a /dev/lcd.
This wiki suggests that lcd4linux can also handle that.

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

tme — Sat, 11 Feb 2023 08:32:58 -0600

bodhi has kindly added the driver for the 16 by 2 character LCD display on the front of the Netgear RN104 in his latest Armada 370XP kernel:

root@rn104:~# egrep 'AUXDISPLAY|44780' /boot/config-6.1.8-mvebu-370xp-tld-1 
CONFIG_AUXDISPLAY=y
CONFIG_HD44780_COMMON=y
CONFIG_HD44780=y

I can't find anything about the driver in the boot log, but the display is supported. It says "Linux-6.1.8-mveb" for about 3 seconds early in the boot process. Picture attached. Then it turns dark until it says "Power off." for about 1 second just before the box is shutting down.

Asking the kernel for it's device tree, it says:

root@rn104:~# for i in /proc/device-tree/auxdisplay/*; do echo $i; hexdump -C $i; done
/proc/device-tree/auxdisplay/backlight-gpios
00000000  00 00 00 17 00 00 00 15  00 00 00 01              |............|
0000000c
/proc/device-tree/auxdisplay/compatible
00000000  68 69 74 2c 68 64 34 34  37 38 30 00              |hit,hd44780.|
0000000c
/proc/device-tree/auxdisplay/data-gpios
00000000  00 00 00 17 00 00 00 19  00 00 00 00 00 00 00 17  |................|
00000010  00 00 00 1a 00 00 00 00  00 00 00 17 00 00 00 1b  |................|
00000020  00 00 00 00 00 00 00 17  00 00 00 1d 00 00 00 00  |................|
00000030
/proc/device-tree/auxdisplay/display-height-chars
00000000  00 00 00 02                                       |....|
00000004
/proc/device-tree/auxdisplay/display-width-chars
00000000  00 00 00 10                                       |....|
00000004
/proc/device-tree/auxdisplay/enable-gpios
00000000  00 00 00 17 00 00 00 18  00 00 00 00              |............|
0000000c
/proc/device-tree/auxdisplay/name
00000000  61 75 78 64 69 73 70 6c  61 79 00                 |auxdisplay.|
0000000b
/proc/device-tree/auxdisplay/rs-gpios
00000000  00 00 00 17 00 00 00 16  00 00 00 00              |............|
0000000c
/proc/device-tree/auxdisplay/rw-gpios
00000000  00 00 00 17 00 00 00 17  00 00 00 00              |............|
0000000c

I have installed 'lcd4linux' on the box, but I've not yet figured out how to make it show anything on the display. The default configuration file '/etc/lcd4linux.conf' has no entry for the Winstar WH1602G LCD display (which is probaly similar to the current WH1602A ). Without success, I have tried to adapt some of the avilable displays.

This in my adapted 'lcd4linux.conf' file with 3 different displays to choose from:

root@rn104:~# cat /etc/lcd4linux.conf
Display HD44780-16x2 {
    Driver  'HD44780'
    Model   'generic'
    UseBusy  1
    Port    '/dev/parport0'	
    Size    '16x2'
    Wire {
	RW      'AUTOFD'
	RS      'INIT'
	ENABLE  'STROBE'
	ENABLE2 'GND'
	GPO     'GND'
    }
}

# generic HD44780 display (WinAmp wiring)
Display HD44780-winamp-16x2 {
    Driver 'HD44780'
    Model 'generic'
    UseBusy 1
    Port '/dev/parports/0'      
    Size '16x2'
    asc255bug 1
    Wire {
        RW      'AUTOFD'
        RS      'INIT'
        ENABLE  'STROBE'
        ENABLE2 'GND'
        GPO     'GND'
        POWER   'GND'
    }
    Timing {
        # fuzz timings by value (100 = no change)
        fuzz 100
        # low-level communication [ns]
        CY 1000  # Enable cycle time
        PW  450  # Enable pulse width
        AS  140  # Address setup time
        AH   20  # Address hold time
        # HD44780 execution timings [us]
        INIT1 4100  # first init sequence: 4.1 msec
        INIT2  100  # second init sequence: 100 usec
        EXEC    80  # normal execution time
        WRCG   120  # CG RAM Write
        CLEAR 2250  # Clear Display
        HOME  2250  # Return Cursor Home
        ONOFF 2250  # Display On/Off Control
        # GPO timing [ns]
        GPO_ST  20  # 74HCT573 set-up time
        GPO_PW 230  # 74HCT573 enable pulse width
        # Power supply timing [ms]
        POWER  500  # power-on delay
    }
}

Display SC1602D {
    Driver 'HD44780'
    Port '/dev/parports/0'      
    Bits '8'
    Size '16x2'
    asc255bug 0
    Icons 1
    Wire {
        RW     'GND'
        RS     'AUTOFD'
        ENABLE 'STROBE'
        GPO    'INIT'
        POWER  'GND'
    }
}

Widget CPU {
    class  'Text'
    expression  uname('machine')
    prefix 'CPU '
    width  9
    align  'L'
    update tick
}

Layout Default {
    Row1 {
        Col1 'CPU'
    }
}

Variables {
   tick 500
}

Display 'HD44780-16x2'
#Display 'HD44780-winamp-16x2'
#Display 'SC1602D'

Layout  'Default'

The devices were missing, so I created them manually:

root@rn104:~# mknod /dev/parport0 c 99 0 

root@rn104:~# mkdir /dev/parports

root@rn104:~# mknod /dev/parports/0 c 99 0

root@rn104:~# chgrp lp /dev/parport0 /dev/parports/0

root@rn104:~# chmod g+rw /dev/parport0 /dev/parports/0

root@rn104:~# ls -AlF /dev/parp*
crw-rw-r-- 1 root lp   99, 0 Feb 11 12:07 /dev/parport0

/dev/parports:
total 0
crw-rw-r-- 1 root lp 99, 0 Feb 11 13:13 0

Still, 'lcd4linux' claims the devices do not exist:

root@rn104:~# grep '^Display' /etc/lcd4linux.conf | grep -v '{'
Display 'HD44780-16x2'

root@rn104:~# lcd4linux -Fv
LCD4Linux 0.11.0-SVN-1193 starting
[DBus] Error connecting to the dbus session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

[MPD] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
[raspi] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
HD44780: $Rev: 1202 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/parport0
HD44780: open(/dev/parport0) failed: No such device or address
HD44780: could not initialize parallel port!
HD44780: start display failed!
Error initializing driver HD44780: Exit!

root@rn104:~# nano /etc/lcd4linux.conf

root@rn104:~# grep '^Display' /etc/lcd4linux.conf | grep -v '{'
Display 'HD44780-winamp-16x2'

root@rn104:~# lcd4linux -Fv
LCD4Linux 0.11.0-SVN-1193 starting
[DBus] Error connecting to the dbus session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

[MPD] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
[raspi] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
HD44780: $Rev: 1202 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/parports/0
HD44780: open(/dev/parports/0) failed: No such device or address
HD44780: could not initialize parallel port!
HD44780: start display failed!
Error initializing driver HD44780: Exit!

root@rn104:~# nano /etc/lcd4linux.conf

root@rn104:~# grep '^Display' /etc/lcd4linux.conf | grep -v '{'
Display 'SC1602D'

root@rn104:~# lcd4linux -Fv
LCD4Linux 0.11.0-SVN-1193 starting
[DBus] Error connecting to the dbus session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

[MPD] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
[raspi] WARNING: Plugin is not enabled! (set 'enabled 1' to enable this plugin)
HD44780: $Rev: 1202 $
HD44780: using model 'generic'
HD44780: using parallel port
HD44780: using 1 Controller(s)
HD44780: using 8 bit mode
udelay: using gettimeofday() delay loop
HD44780: using ppdev /dev/parports/0
HD44780: open(/dev/parports/0) failed: No such device or address
HD44780: could not initialize parallel port!
HD44780: start display failed!
Error initializing driver HD44780: Exit!

Suspecting support for parallel port might be the cause, I did:

root@rn104:~# grep -ie 'parport*=m' /boot/config-6.1.8-mvebu-370xp-tld-1
CONFIG_PARPORT=m
CONFIG_PPS_CLIENT_PARPORT=m

root@rn104:~# insmod /lib/modules/5.19.2-mvebu-370xp-tld-1/kernel/drivers/parport/parport.ko
insmod: ERROR: could not insert module /lib/modules/5.19.2-mvebu-370xp-tld-1/kernel/drivers/parport/parport.ko: Invalid module format

root@rn104:~# dmesg | tail -1
[10666.430896] parport: disagrees about version of symbol module_layout

So how to proceed? Should the kernel be configured with 'CONFIG_PARPORT=y'?

Regards,
Trond Melen

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

rayknight — Tue, 17 Jan 2023 21:08:33 -0600

Based on the DTS file I believe you need to include the following config options:

CONFIG_AUXDISPLAY=y
CONFIG_HD44780=y

Ray

Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104

tme — Tue, 17 Jan 2023 02:44:28 -0600

Thanks raynight, for your hints!

'lcd4linux' may become useful:

tme@rn102:~$ sudo apt install -y lcd4linux

tme@rn102:~$ sudo lcd4linux -l | egrep -i 'Winstar|WH1602G|hd44780|hit'
   BWCT                : BWCT USB to HD44780 interface
   HD44780             : generic Noritake Soekris HD66712 LCM-162 
   LCD2USB             : LCD2USB homebrew USB interface for HD44780 text displays
   LCDTerm             : LCDTerm serial-to-HD44780 adapter board
   PHAnderson          : PHAnderson serial-to-HD44780 adapter
   RouterBoard         : HD44780 HD66712

Linux prints nothing on the display, and LCD is not mentioned in the boot log:

tme@rn102:~$ sudo dmesg | grep -i lcd
tme@rn102:~$

Here some possibly relevant kernel configurations:

tme@rn102:~$ egrep -i 'lcd|backlight' /boot/config-5.19.2-mvebu-370xp-tld-1 

# CONFIG_MFD_ATMEL_HLCDC is not set
# CONFIG_DRM_HDLCD is not set
# CONFIG_DRM_TILCDC is not set
# CONFIG_DRM_PANEL_OLIMEX_LCD_OLINUXINO is not set
CONFIG_FB_BACKLIGHT=m
# Backlight & LCD device support
# CONFIG_LCD_CLASS_DEVICE is not set
CONFIG_BACKLIGHT_CLASS_DEVICE=y
# CONFIG_BACKLIGHT_KTD253 is not set
# CONFIG_BACKLIGHT_PWM is not set
# CONFIG_BACKLIGHT_QCOM_WLED is not set
# CONFIG_BACKLIGHT_ADP8860 is not set
# CONFIG_BACKLIGHT_ADP8870 is not set
# CONFIG_BACKLIGHT_PCF50633 is not set
# CONFIG_BACKLIGHT_LM3630A is not set
# CONFIG_BACKLIGHT_LM3639 is not set
# CONFIG_BACKLIGHT_LP855X is not set
# CONFIG_BACKLIGHT_GPIO is not set
# CONFIG_BACKLIGHT_LV5207LP is not set
# CONFIG_BACKLIGHT_BD6107 is not set
# CONFIG_BACKLIGHT_ARCXCNN is not set
# CONFIG_BACKLIGHT_LED is not set
# end of Backlight & LCD device support
CONFIG_HID_PICOLCD=m
CONFIG_HID_PICOLCD_FB=y
CONFIG_HID_PICOLCD_BACKLIGHT=y
CONFIG_HID_PICOLCD_LEDS=y
# CONFIG_HID_PICOLCD_CIR is not set
CONFIG_USB_LCD=m
CONFIG_LEDS_TRIGGER_BACKLIGHT=m
CONFIG_FB_TFT_TINYLCD=m

Maybe I should I try to load the modules corresponding to HID_PICOLCD or CONFIG_FB_TFT_TINYLCD?

Reagards,
Trond Melen