hi @ayyappanmuthu well you installed ubuntu-desktop…
First check etnaviv loaded:
debian@arm:~$ dmesg | grep etnaviv
2nd check it’s running xorg…
cat /var/log/Xorg.0.log
If ubuntu-desktop setup “wayland” vs xorg, good luck! I don’t use wayland…
Regards,
Hi Robert,
PFB,…
ubuntu@arm:~$ dmesg | grep etnaviv
[ 2.667983] etnaviv etnaviv: bound 130000.gpu (ops 0xc0bc6fd4)
[ 2.674335] etnaviv etnaviv: bound 134000.gpu (ops 0xc0bc6fd4)
[ 2.680289] etnaviv-gpu 130000.gpu: model: GC880, revision: 5106
[ 2.686566] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
[ 2.693655] [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0
ubuntu@arm:~$ cat /var/log/Xorg.0.log
[ 32.144] (--) Log file renamed from "/var/log/Xorg.pid-2597.log" to "/var/log/Xorg.0.log"
[ 32.150]
X.Org X Server 1.20.13
X Protocol Version 11, Revision 0
[ 32.152] Build Operating System: linux Ubuntu
[ 32.152] Current Operating System: Linux arm 5.4.154-armv7-x62 #1 SMP PREEMPT Fri Feb 4 11:31:59 IST 2022 armv7l
[ 32.152] Kernel command line: console=ttymxc0 root=PARTUUID=d9e4a558-01 ro rootfstype=ext4 rootwait video=HDMI-A-1:1024x768@60e
[ 32.152] Build Date: 14 December 2021 02:14:13PM
[ 32.152] xorg-server 2:1.20.13-1ubuntu1~20.04.2 (For technical support please see http://www.ubuntu.com/support)
[ 32.153] Current version of pixman: 0.38.4
[ 32.153] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 32.153] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 32.153] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 12 08:32:23 2022
[ 32.165] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 32.172] (==) No Layout section. Using the first Screen section.
[ 32.173] (==) No screen section available. Using defaults.
[ 32.173] (**) |-->Screen "Default Screen Section" (0)
[ 32.173] (**) | |-->Monitor "<default monitor>"
[ 32.174] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 32.174] (==) Automatically adding devices
[ 32.174] (==) Automatically enabling devices
[ 32.174] (==) Automatically adding GPU devices
[ 32.174] (==) Automatically binding GPU devices
[ 32.175] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 32.185] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 32.185] Entry deleted from font path.
[ 32.185] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 32.185] Entry deleted from font path.
[ 32.186] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 32.186] Entry deleted from font path.
[ 32.188] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 32.188] Entry deleted from font path.
[ 32.188] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 32.188] Entry deleted from font path.
[ 32.189] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[ 32.189] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 32.189] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 32.189] (II) Loader magic: 0x57c008
[ 32.189] (II) Module ABI versions:
[ 32.189] X.Org ANSI C Emulation: 0.4
[ 32.189] X.Org Video Driver: 24.1
[ 32.189] X.Org XInput driver : 24.1
[ 32.189] X.Org Server Extension : 10.0
[ 32.211] (++) using VT number 1
[ 32.227] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
[ 32.231] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 32.258] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
[ 32.276] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 32.292] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 paused 0
[ 32.293] (II) no primary bus or device found
[ 32.293] falling back to /sys/devices/platform/etnaviv/drm/card0
[ 32.293] (II) LoadModule: "glx"
[ 32.297] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 32.318] (II) Module glx: vendor="X.Org Foundation"
[ 32.318] compiled for 1.20.13, module version = 1.0.0
[ 32.318] ABI class: X.Org Server Extension, version 10.0
[ 32.318] (==) Matched modesetting as autoconfigured driver 0
[ 32.318] (==) Matched fbdev as autoconfigured driver 1
[ 32.318] (==) Assigned the driver to the xf86ConfigLayout
[ 32.319] (II) LoadModule: "modesetting"
[ 32.319] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 32.325] (II) Module modesetting: vendor="X.Org Foundation"
[ 32.325] compiled for 1.20.13, module version = 1.20.13
[ 32.325] Module class: X.Org Video Driver
[ 32.325] ABI class: X.Org Video Driver, version 24.1
[ 32.325] (II) LoadModule: "fbdev"
[ 32.326] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 32.328] (II) Module fbdev: vendor="X.Org Foundation"
[ 32.329] compiled for 1.20.1, module version = 0.5.0
[ 32.329] Module class: X.Org Video Driver
[ 32.329] ABI class: X.Org Video Driver, version 24.0
[ 32.329] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 32.329] (II) FBDEV: driver for framebuffer: fbdev
[ 32.330] (WW) Falling back to old probe method for modesetting
[ 32.330] (WW) Falling back to old probe method for fbdev
[ 32.330] (II) Loading sub module "fbdevhw"
[ 32.330] (II) LoadModule: "fbdevhw"
[ 32.331] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 32.333] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 32.333] compiled for 1.20.13, module version = 0.0.2
[ 32.333] ABI class: X.Org Video Driver, version 24.1
[ 32.334] (II) FBDEV(0): using default device
[ 32.334] (II) modeset(G0): using drv /dev/dri/card1
[ 32.334] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 32.334] (EE)
Fatal server error:
[ 32.334] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 32.334] (EE)
[ 32.334] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 32.335] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 32.335] (EE)
[ 32.352] (EE) Server terminated with error (1). Closing log file.
ubuntu@arm:~$
Please look into this and reply what is the problem and how to fix it.
Thanks.
Interesting… so in Ubuntu, xorg can’t figure out which is the 2D only vs the 3D only core…
Regards,
How to fix that?
Please help.
Thanks.
Hi Robert,
If this is a new found issue, and takes time to figure out, please suggest a desktop package that is functionally proven, so that I can reformat the sd card and install that for mean while.
Thanks.
Use my Debian 11.x image on the page, then run:
sudo apt update
sudo apt install bbb.io-xfce4-desktop
sudo cp -v /etc/bbb.io/templates/fbdev.xorg.conf /etc/X11/xorg.conf
I can login into xfce with those setting…
Regards,
Hi Robert,
Just noticed on the page that Ubuntu was removed and Debian was updated from 10.9 to 11.
Also kernel versions 4.x are removed.
Is the current 5.4 kernel version same as the previous 5.4 kernel version (or) is there any patches added and do I have to take the 5.4 kernel also from the current page?
Please reply.
Thanks for your effort.
It’s a git repo, any changes you can directly see in the 5.4 branch…
Regards,
Hi Robert,
Now only I got time to use the debian 11 as I was doing my exams.
The debian 11 UI for login screen was up and I can see that in my HDMI display.
But when I connected my USB Keyboard or USB mouse to the wandboard I am not able to give inputs.
In minicom I see the following log when i connect my USB key board to wandboard.
debian@arm:~$ [ 213.236936] usb 1-1: new low-speed USB device number 4 using ci_hdrc
[ 213.405590] usb 1-1: New USB device found, idVendor=1a2c, idProduct=6004, bcdDevice= 1.10
[ 213.413898] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 213.421123] usb 1-1: Product: USB Keyboard
[ 213.425337] usb 1-1: Manufacturer: SEMICO
And when I tried to check keyboard got power by pressing CAPSLOCK/NUMLOCK the led in keyboard is not glowing when the keyboard is connected to wandboard but glowing when key board connected to my laptop.
Is it like
For your Notice : Most probably case 1) might not be the issue as with minimal software of Ubuntu earlier I was able to use the USB keyboard.
Please suggest what can I do. If you need any kind of log I shall take that to debug.
Thanks.
Try sticking a usb 2.0 hub on the WandBoard… I really only have Logitech based keyboard/mice to test with, the keyboard/mice config is a direct copy of what debian ships by defaut.
Regards,
Hi Robert,
I am using usb 2.0 port hub( iball piano 423). Mouse is Logitech wireless mouse it is also 2.0 port specification.
Will there be any specific driver for usb devices like these?
Please help me to diagnose / deduce / corner the root cause of this problem was due to either
it’s a wandboard hardware or
any software related configuration or
driver support.
Please reply.
Thanks.
I’m not currently aware of any issues with the USB port on imx6 based devices… What is the rating of the power supply you are currently using to power the WandBoard?
Regards,
Output of power supply is 5v and 3A
Input is 100-240v , 0.3A , 50-60Hz
That should be fine, i’d expect that work…
Yes, few months back as mentioned in my previous post, I was able to use keyboard in command prompt of Ubuntu minimal rootfs.
Do I have to do any configuration or install any packages/driver in board if possible through minicom?
Do you need any more log to confirm that?
Thanks.
And I have taken the following lsusb -t log
debian@arm:~$ lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
debian@arm:~$ lsusb -t
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
Is the above driver usbhid enough to support the keyboard?
Please reply.
Thanks.
Looks good, if you have an lcd plugged in over hdmi, i’d fully expect to see output change over the video display…
If your expecting to see your keyboard attached to the wandboard, to echo over the serial port, that’s not the way, the Root File system is setup for…
Regards,
Sorry Robert, I am not getting clearly what you say. Please say what shall I try to solve this issue.
Hi @ayyappanmuthu with your usb keyboard plugged into the Wandboard, are you seeing any activity on the HDMI based display plugged into the Wandboard?
Regards,
No, I am not seeing any changes in the hdmi display when giving inputs through keyboard.