Hi @ayyappanmuthu you can use v4.14.x on Debian 11 with no issues…
Regards,
Hi Robert,
With kernel 4.14.x + debian 11 minimal, I am able to use keyboard through out the power on.
But when installed desktop as per your recommendation, login UI screen appears and i could not use keyboard again.
One observation with xfce desktop installed is, that while booting I am able to see the leds in keyboard glowing on pressing numlock/capslock key but after sometime keyboard becomes inactive and could not login.
When i took dmesg log from minicom after installing and rebooting, and do these parts of log may be related to the issue?
[ 0.000000] efi: UEFI not found.
[ 0.082929] EFI services will not be available.
[ 0.594336] vdd1p1: supplied by regulator-dummy
[ 0.594909] vdd3p0: supplied by regulator-dummy
[ 0.595492] vdd2p5: supplied by regulator-dummy
[ 0.596069] vddarm: supplied by regulator-dummy
[ 0.596642] vddpu: supplied by regulator-dummy
[ 0.597265] vddsoc: supplied by regulator-dummy
[ 0.843634] imx-sdma 20ec000.sdma: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2
[ 0.843655] imx-sdma 20ec000.sdma: external firmware not found, using ROM firmware
[ 1.978808] Error: Driver 'tfp410' is already registered, aborting...
[ 2.151832] [drm] No driver support for vblank timestamp query.
[ 2.799235] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
[ 2.840181] coda 2040000.vpu: Direct firmware load for vpu_fw_imx6d.bin failed with error -2
[ 2.880899] sr_init: platform driver register failed for SR
[ 2.881721] coda 2040000.vpu: Direct firmware load for vpu/vpu_fw_imx6d.bin failed with error -2
[ 2.896186] coda 2040000.vpu: Direct firmware load for v4l-coda960-imx6dl.bin failed with error -2
[ 2.907633] coda 2040000.vpu: firmware request failed
[ 2.910879] SW4: disabling
[ 2.918086] SWBST: disabling
[ 2.921642] VGEN1: disabling
Or these log is not relevant to the issue?
If i could make use of all the peripherals’ functionality in board its enough for me and i am not looking for superior performance.
When any desktop is working fine I shall try to install other features on my own.
Please help me to solve these issues.
Thanks.
vpu is for video decode/encode…
I find it strange, that your usb port hasn’t worked for any of the kernel yet…
Do you by chance have a simple usb flash drive… With NO usb hub/etc, just plug it in, to see if the usb port on the Wandboard actually works…
Please run:
lsusb
So we can see it’s output with the flash drive plugged in…
Regards,
Hi Robert,
As you said I directly connected the usb flash drive to USB port of wand board and issued lsusb command.
debian@arm:~$ lsusb
Bus 001 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And I am able to list the files by mounting that usb drive.
Please guide me what to do next…
Thanks.
the above previous steps i did through minicom.
Well the usb port seems to work… So without the Hub, does the usb mouse work in xorg? (aka can you move the mouse around?)
Regards,
No it’s not working even when connected directly without usb hub.
Also in minimal rootfs even when connected through USB hub, the keyboard worked.
Hi Robert,
I would like to understand why we are using bbb.io-xfce4-desktop and why we are manually copying fbdev.xorg.conf to xorg.conf.
I see that bbb.io is for beagle bone and is there any specific reasons to use that, like need for board specific items that were not available in standard packages?
Aren’t there any other working desktop suitable for Wandboard in which we don’t need to take care of manual configuration?
Please reply.
Also When I was installing xfce I got error message as follows
E: Failed to fetch http://deb.debian.org/debian/pool/main/p/pulseaudio/libpulse0_14.2-2_armhf.deb Error reading from server - read (104: Con]
E: Failed to fetch http://deb.debian.org/debian/pool/main/x/xfce4-panel/libxfce4panel-2.0-4_4.16.2-1_armhf.deb Error reading from server - r]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
And I tried by using --fix-missing option and again issued install command and those errors were cleared after that in minicom it showed the following message to select keyboard layout
and I pressed enter it proceeded.
Will there be any issues do you observe in these scenarios.
Please reply.
I was trying to stop the windowing system to check whether it is returning to console mode.
So I issued the following command
debian@arm:~$ systemctl list-units --all
UNIT >
proc-sys-fs-binfmt_misc.automount >
dev-disk-by\x2did-mmc\x2dSA16G_0x31691815.device >
dev-disk-by\x2did-mmc\x2dSA16G_0x31691815\x2dpart1.device >
dev-disk-by\x2dlabel-rootfs.device >
dev-disk-by\x2dpartuuid-5f4e01c5\x2d01.device >
dev-disk-by\x2dpath-platform\x2d2198000.usdhc.device >
dev-disk-by\x2dpath-platform\x2d2198000.usdhc\x2dpart1.device >
dev-disk-by\x2duuid-0ad7f0be\x2de2f4\x2d4185\x2da7d9\x2d58dabed697db.device >
dev-mmcblk1.device >
dev-mmcblk1p1.device >
dev-rfkill.device >
dev-ttymxc0.device >
dev-ttymxc2.device >
dev-ttyS0.device >
dev-ttyS1.device >
dev-ttyS2.device >
dev-ttyS3.device >
dev-ttyS4.device >
dev-ttyS5.device >
sys-devices-platform-serial8250-tty-ttyS0.device >
sys-devices-platform-serial8250-tty-ttyS1.device >
sys-devices-platform-serial8250-tty-ttyS2.device >
sys-devices-platform-serial8250-tty-ttyS3.device >
sys-devices-platform-serial8250-tty-ttyS4.device >
sys-devices-platform-serial8250-tty-ttyS5.device >
sys-devices-soc0-soc-2000000.aips\x2dbus-2000000.spba\x2dbus-2020000.serial-t>
sys-devices-soc0-soc-2100000.aips\x2dbus-2184000.usb-ci_hdrc.0-udc-ci_hdrc.0.>
sys-devices-soc0-soc-2100000.aips\x2dbus-2188000.ethernet-net-eth0.device >
sys-devices-soc0-soc-2100000.aips\x2dbus-2198000.usdhc-mmc_host-mmc1-mmc1:123>
sys-devices-soc0-soc-2100000.aips\x2dbus-2198000.usdhc-mmc_host-mmc1-mmc1:123>
sys-devices-soc0-soc-2100000.aips\x2dbus-21ec000.serial-tty-ttymxc2.device >
sys-devices-virtual-misc-rfkill.device >
sys-module-configfs.device >
sys-module-fuse.device >
sys-subsystem-net-devices-eth0.device >
-.mount >
dev-hugepages.mount >
dev-mqueue.mount >
��● home.mount >
proc-sys-fs-binfmt_misc.mount >
run-user-1000.mount >
UNIT >
proc-sys-fs-binfmt_misc.automount >
dev-disk-by\x2did-mmc\x2dSA16G_0x31691815.device >
dev-disk-by\x2did-mmc\x2dSA16G_0x31691815\x2dpart1.device >
dev-disk-by\x2dlabel-rootfs.device >
dev-disk-by\x2dpartuuid-5f4e01c5\x2d01.device >
dev-disk-by\x2dpath-platform\x2d2198000.usdhc.device >
dev-disk-by\x2dpath-platform\x2d2198000.usdhc\x2dpart1.device >
dev-disk-by\x2duuid-0ad7f0be\x2de2f4\x2d4185\x2da7d9\x2d58dabed697db.device >
dev-mmcblk1.device >
dev-mmcblk1p1.device >
dev-rfkill.device >
dev-ttymxc0.device >
dev-ttymxc2.device >
dev-ttyS0.device >
dev-ttyS1.device >
dev-ttyS2.device >
dev-ttyS3.device >
dev-ttyS4.device >
dev-ttyS5.device >
sys-devices-platform-serial8250-tty-ttyS0.device >
sys-devices-platform-serial8250-tty-ttyS1.device >
sys-devices-platform-serial8250-tty-ttyS2.device >
sys-devices-platform-serial8250-tty-ttyS3.device >
sys-devices-platform-serial8250-tty-ttyS4.device >
sys-devices-platform-serial8250-tty-ttyS5.device >
sys-devices-soc0-soc-2000000.aips\x2dbus-2000000.spba\x2dbus-2020000.serial-t>
sys-devices-soc0-soc-2100000.aips\x2dbus-2184000.usb-ci_hdrc.0-udc-ci_hdrc.0.>
sys-devices-soc0-soc-2100000.aips\x2dbus-2188000.ethernet-net-eth0.device >
sys-devices-soc0-soc-2100000.aips\x2dbus-2198000.usdhc-mmc_host-mmc1-mmc1:123>
sys-devices-soc0-soc-2100000.aips\x2dbus-2198000.usdhc-mmc_host-mmc1-mmc1:123>
sys-devices-soc0-soc-2100000.aips\x2dbus-21ec000.serial-tty-ttymxc2.device >
sys-devices-virtual-misc-rfkill.device >
sys-module-configfs.device >
sys-module-fuse.device >
sys-subsystem-net-devices-eth0.device >
-.mount >
dev-hugepages.mount >
dev-mqueue.mount >
��● home.mount >
proc-sys-fs-binfmt_misc.mount >
run-user-1000.mount >
run-user-113.mount >
sys-fs-fuse-connections.mount >
sys-kernel-config.mount >
sys-kernel-debug.mount >
sys-kernel-tracing.mount >
��● tmp.mount >
systemd-ask-password-console.path >
systemd-ask-password-plymouth.path >
systemd-ask-password-wall.path >
init.scope >
session-2.scope >
session-c1.scope >
��● apparmor.service >
��● auditd.service >
avahi-daemon.service >
cron.service >
dbus.service >
e2scrub_all.service >
e2scrub_reap.service >
emergency.service >
fake-hwclock.service >
fstrim.service >
getty-static.service >
getty@tty1.service >
ifupdown-pre.service >
��● keyboard-setup.service >
kmod-static-nodes.service >
lightdm.service >
logrotate.service >
ModemManager.service >
modprobe@configfs.service >
modprobe@drm.service >
modprobe@fuse.service >
networking.service >
NetworkManager-wait-online.service >
NetworkManager.service >
nginx.service >
plymouth-quit-wait.service >
plymouth-quit.service >
plymouth-read-write.service >
plymouth-start.service >
polkit.service >
rc-local.service >
rescue.service >
rsync.service >
rsyslog.service >
rtkit-daemon.service >
serial-getty@ttymxc0.service >
ssh.service >
systemd-ask-password-console.service >
systemd-ask-password-plymouth.service >
systemd-ask-password-wall.service >
systemd-binfmt.service >
systemd-boot-system-token.service >
systemd-fsck-root.service >
systemd-fsckd.service >
systemd-hwdb-update.service >
systemd-initctl.service >
systemd-journal-flush.service >
systemd-journald.service >
systemd-logind.service >
systemd-machine-id-commit.service >
systemd-modules-load.service >
systemd-pstore.service >
systemd-random-seed.service >
systemd-remount-fs.service >
systemd-rfkill.service >
systemd-sysctl.service >
systemd-sysusers.service >
systemd-timesyncd.service >
systemd-tmpfiles-clean.service >
systemd-tmpfiles-setup-dev.service >
systemd-tmpfiles-setup.service >
systemd-udev-trigger.service >
systemd-udevd.service >
��● systemd-update-done.service >
systemd-update-utmp-runlevel.service >
systemd-update-utmp.service >
systemd-user-sessions.service >
��● systemd-vconsole-setup.service >
udisks2.service >
user-runtime-dir@1000.service >
user-runtime-dir@113.service >
user@1000.service >
user@113.service >
wpa_supplicant.service >
-.slice >
system-getty.slice >
system-modprobe.slice >
system-serial\x2dgetty.slice >
system.slice >
user-1000.slice >
user-113.slice >
user.slice >
avahi-daemon.socket >
dbus.socket >
syslog.socket >
systemd-fsckd.socket >
systemd-initctl.socket >
systemd-journald-audit.socket >
systemd-journald-dev-log.socket >
systemd-journald.socket >
systemd-rfkill.socket >
systemd-udevd-control.socket >
systemd-udevd-kernel.socket >
basic.target >
blockdev@dev-mmcblk2p1.target >
cryptsetup.target >
emergency.target >
UNIT >
proc-sys-fs-binfmt_misc.automount >
dev-disk-by\x2did-mmc\x2dSA16G_0x31691815.device >
dev-disk-by\x2did-mmc\x2dSA16G_0x31691815\x2dpart1.device >
dev-disk-by\x2dlabel-rootfs.device >
dev-disk-by\x2dpartuuid-5f4e01c5\x2d01.device >
dev-disk-by\x2dpath-platform\x2d2198000.usdhc.device >
dev-disk-by\x2dpath-platform\x2d2198000.usdhc\x2dpart1.device >
dev-disk-by\x2duuid-0ad7f0be\x2de2f4\x2d4185\x2da7d9\x2d58dabed697db.device >
dev-mmcblk1.device >
dev-mmcblk1p1.device >
dev-rfkill.device >
dev-ttymxc0.device >
dev-ttymxc2.device >
dev-ttyS0.device >
dev-ttyS1.device >
dev-ttyS2.device >
dev-ttyS3.device >
dev-ttyS4.device >
dev-ttyS5.device >
sys-devices-platform-serial8250-tty-ttyS0.device >
sys-devices-platform-serial8250-tty-ttyS1.device >
sys-devices-platform-serial8250-tty-ttyS2.device >
sys-devices-platform-serial8250-tty-ttyS3.device >
sys-devices-platform-serial8250-tty-ttyS4.device >
sys-devices-platform-serial8250-tty-ttyS5.device >
sys-devices-soc0-soc-2000000.aips\x2dbus-2000000.spba\x2dbus-2020000.serial-t>
sys-devices-soc0-soc-2100000.aips\x2dbus-2184000.usb-ci_hdrc.0-udc-ci_hdrc.0.>
sys-devices-soc0-soc-2100000.aips\x2dbus-2188000.ethernet-net-eth0.device >
sys-devices-soc0-soc-2100000.aips\x2dbus-2198000.usdhc-mmc_host-mmc1-mmc1:123>
sys-devices-soc0-soc-2100000.aips\x2dbus-2198000.usdhc-mmc_host-mmc1-mmc1:123>
sys-devices-soc0-soc-2100000.aips\x2dbus-21ec000.serial-tty-ttymxc2.device >
sys-devices-virtual-misc-rfkill.device >
sys-module-configfs.device >
sys-module-fuse.device >
sys-subsystem-net-devices-eth0.device >
-.mount >
dev-hugepages.mount >
dev-mqueue.mount >
��● home.mount >
proc-sys-fs-binfmt_misc.mount >
run-user-1000.mount >
run-user-113.mount >
sys-fs-fuse-connections.mount >
sys-kernel-config.mount >
sys-kernel-debug.mount >
sys-kernel-tracing.mount >
��● tmp.mount >
systemd-ask-password-console.path >
systemd-ask-password-plymouth.path >
systemd-ask-password-wall.path >
init.scope >
session-2.scope >
session-c1.scope >
��● apparmor.service >
��● auditd.service >
avahi-daemon.service >
cron.service >
dbus.service >
e2scrub_all.service >
e2scrub_reap.service >
emergency.service >
fake-hwclock.service >
fstrim.service >
getty-static.service >
getty@tty1.service >
ifupdown-pre.service >
��● keyboard-setup.service >
kmod-static-nodes.service >
lightdm.service >
logrotate.service >
ModemManager.service >
modprobe@configfs.service >
modprobe@drm.service >
modprobe@fuse.service >
networking.service >
NetworkManager-wait-online.service >
NetworkManager.service >
nginx.service >
plymouth-quit-wait.service >
plymouth-quit.service >
plymouth-read-write.service >
plymouth-start.service >
polkit.service >
rc-local.service >
rescue.service >
rsync.service >
rsyslog.service >
rtkit-daemon.service >
serial-getty@ttymxc0.service >
ssh.service >
systemd-ask-password-console.service >
systemd-ask-password-plymouth.service >
systemd-ask-password-wall.service >
systemd-binfmt.service >
systemd-boot-system-token.service >
systemd-fsck-root.service >
systemd-fsckd.service >
systemd-hwdb-update.service >
systemd-initctl.service >
systemd-journal-flush.service >
systemd-journald.service >
systemd-logind.service >
systemd-machine-id-commit.service >
systemd-modules-load.service >
systemd-pstore.service >
systemd-random-seed.service >
systemd-remount-fs.service >
systemd-rfkill.service >
systemd-sysctl.service >
systemd-sysusers.service >
systemd-timesyncd.service >
systemd-tmpfiles-clean.service >
systemd-tmpfiles-setup-dev.service >
systemd-tmpfiles-setup.service >
systemd-udev-trigger.service >
systemd-udevd.service >
��● systemd-update-done.service >
systemd-update-utmp-runlevel.service >
systemd-update-utmp.service >
systemd-user-sessions.service >
��● systemd-vconsole-setup.service >
udisks2.service >
user-runtime-dir@1000.service >
user-runtime-dir@113.service >
user@1000.service >
user@113.service >
wpa_supplicant.service >
-.slice >
system-getty.slice >
system-modprobe.slice >
system-serial\x2dgetty.slice >
system.slice >
user-1000.slice >
user-113.slice >
user.slice >
avahi-daemon.socket >
dbus.socket >
syslog.socket >
systemd-fsckd.socket >
systemd-initctl.socket >
systemd-journald-audit.socket >
systemd-journald-dev-log.socket >
systemd-journald.socket >
systemd-rfkill.socket >
systemd-udevd-control.socket >
systemd-udevd-kernel.socket >
basic.target >
blockdev@dev-mmcblk2p1.target >
cryptsetup.target >
emergency.target >
first-boot-complete.target >
getty-pre.target >
getty.target >
graphical.target >
local-fs-pre.target >
local-fs.target >
multi-user.target >
network-online.target >
network-pre.target >
network.target >
nss-lookup.target >
nss-user-lookup.target >
paths.target >
remote-fs-pre.target >
remote-fs.target >
rescue.target >
shutdown.target >
slices.target >
sockets.target >
swap.target >
sysinit.target >
time-set.target >
time-sync.target >
timers.target >
umount.target >
usb-gadget.target >
e2scrub_all.timer >
fstrim.timer >
logrotate.timer >
systemd-tmpfiles-clean.timer >
And I could not identify xorg service in that. Is that an issue?
Only lightdm is available…
Please reply.
Hi Robert,
I have decided to use Wifi, bluetooth with command line prompt.
I ensured installing wpa_supplicant by following commands.
sudo apt-get update
sudo apt-get install wpasupplicant
And put ssid and password in /etc/wpa_supplicant.conf as follows
network={
ssid="ssid_name"
psk="password"
}
Now I am trying to get the wifi interface name, so I issued
iwconfig
command in target. It listed only loop back and ethernet interface names alone.
I am using WPA/WPA2 wifi connection.I have connected the antenna.
Am I right, that to enable and use wifi connection, I have to issue following commands?
sudo wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
sudo dhclient wlan0
where wlan0 is interface name and wext is the driver name. If so how can I get interface name and driver name and use that properly?
Can you please help me to use wifi and bluetooth through command line?
Thanks.
Hi @ayyappanmuthu which kernel version (uname -r)? cypress recently changed the driver/firmware/etc…
Regards,
It’s 4.14.232-armv7-x52…
Hi Robert,
Which kernel version shall I use?
Hi Robert,
the broadcom wifi driver was built as a module.
The lsmod command showed no entries.
So I tried
modprobe brcmfmac
But it showed like FATAL:could not find driver in the directory /lib/modules/4.14.xxxx/
But brcmfmac.ko is available in that directory.
Am I using wrong driver name in modprobe command?
I could not get the definition of KBUILD_MODNAME for this driver from the source.
Please help to find the exact driver name if I am using wrong driver name for loading.
Thanks.
Or is this the case rfkill blocking wifi?
I tried
ubuntu@arm:~$ sudo rfkill unblock all
[sudo] password for ubuntu:
sudo: rfkill: command not found
Please guide me.
Thanks.
Hi Robert,
I have copied that firmware to sd card as per the instructions in that page.
Are the firmware files updated/modified recently?
I again downloaded those files. All the four files are same in size with my older ones. Does it has any changes from which I have downloaded around one year back.?
Hi,
I am trying to use audio through command line.
I installed mpg123, pulseaudio and jackd2 in debian 11 of Wandboard.
When I played using the command I get output as follows but no audio from the jack output.
debian@arm:/media/usb$ mpg123 G.mp3
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
version 1.26.4; written and copyright by Michael Hipp and others
free software (LGPL) without any warranty but with best wishes
Terminal control enabled, press 'h' for listing of keys and functions.
Playing MPEG stream 1 of 1: G.mp3 ...
MPEG 1.0 L III cbr128 48000 j-s
I tried increasing the volume but still I don’t hear any audio.
Do I have to do any configurations?
Please reply.
Also I could not use use Wifi as wifi interface is not even listed. Please help for that too if possible.