Jump to content

Michael Schuh

Members
  • Posts

    7
  • Joined

  • Last visited

  1. Thanks Rich. It looks like the dbus-user-session package was already installed. michael@oxygen:~$ sudo apt install dbus-user-session Reading package lists... Done Building dependency tree... Done Reading state information... Done dbus-user-session is already the newest version (1.12.20-2ubuntu4). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. By chance do you have any other suggestions? Sorry for being slow to respond. I will try and check this thread more often for updates. Thanks, Michael
  2. I added a new user, "adduser testuser", and was able to run both firefox and chromium from the new user, jim. I logged jim out and logged back in as my user and Firefox appears to be starting and then generate a "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile. ps does not show any other firefox processes and a restart did not solve the problem either. I am tempted to delete my account and remake it. I suspect that would work. chromium runs but generates some output that suggests that all is not well. michael@oxygen:~$ chromium /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) [5612:5775:0501/150818.147981:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [5612:5775:0501/150818.149367:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [5612:5775:0501/150818.150519:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open kms_swrast: /snap/chromium/1975/gnome-platform/usr/lib/aarch64-linux-gnu/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1975/gnome-platform/usr/lib/aarch64-linux-gnu/dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /snap/chromium/1975/gnome-platform/usr/lib/aarch64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1975/gnome-platform/usr/lib/aarch64-linux-gnu/dri) failed to load swrast driver [5612:5721:0501/150822.933079:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration.
  3. I am getting the same error after running apt-get dist-upgrade on aUbuntu 22.04 LTS Jammy system running on an Odroid N2+. How do we fix this? Thanks, Michael
  4. If I boot my Odroid XU4 without the HDMI cable connected, my HDMI display does not work. If I boot with the HDMI cable and monitor connected, the HDMI display works fine even if it is disconnected and reconnected. I am running debian buster. deb http://deb.debian.org/debian buster main contrib non-free I have compared the dmesg output from when HDMI works and does not work and do not see a difference. In case it helps, here are all of the dmesg lines with HDMI in them. root@odroidxu4:~# grep -i hdmi dmesg_hdmi_works_usb_hdmi_plugged_in_at_boot.txt [ 0.000000] Kernel command line: console=ttySAC2,115200n8 console=tty1 consoleblank=0 loglevel=1 root=UUID=494e7783-a94f-45f7-940d-e0ce44ea1455 rootfstype=ext4 rootwait rw smsc95xx.macaddr=00:1e:06:61:7a:55 governor=performance hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=true vout=hdmi usb-storage.quirks= [ 0.000000] hdmi: using HDMI mode [ 4.735974] OF: graph: no port node found in /soc/hdmi@14530000 [ 4.737200] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0cb31ac) I read some other posts that talked about HDMI not working if a USB device was not connected. For both of the attached dmesg output files, the USB keyboard and mouse were connected. In dmesg_hdmi_works_usb_hdmi_plugged_in_at_boot.txt, the HDMI display was plugged in at boot time and works and in dmesg_hdmi_fails_usb_plugged_in_at_boot_no_hdmi_at_boot.txt, the HDMI display was not plugged in at boot time and does not work after it is plugged in. Has anyone seen this behavior and, if so, do you know how to configure the Odriod to boot without the HDMI cable attached and have an HDMI display work after it is attached later? Thanks, Michael
  5. Thanks for the link debianxfce. I figured out that a change we had made to the /etc/modprobe.d/blacklist-odroid.conf file had caused the initrd file to exclude the uas package. Once I reverted that change and rebuilt the initrd file, the system booted fine. If anyone is interested, here are a few more details. After upgrading from the 4.9.30 kernel to the 4.9.33 kernel, the machine would not boot. It was looking for the SSD drive (USB connected) but could not find it. I suspected that the USB module was not loaded. I recovered from this by restoring the 4.9.30 /boot partition to the boot partition on the microSD card. This made it so that the machine would boot again but it was clear that things were not exactly right because the fan stayed on at an annoyingly high speed. A friend helped me downgrade to the 4.9.30 kernel by going to the 5.31 version of the linux-dtb-next-odroidxu4, linux-headers-next-odroidxu4, and linux-image-next-odroidxu4 packages. That did not boot either. This suggested that the problem was not the 4.9.33 upgrade, but something else that was different. We unpacked the initrd files using "zcat /boot/initrd.img-4.9.30-odroidxu4 | cpio -idmv" in /tmp for the version of 4.9.30 that booted and the one that did not boot and found that the /etc/modprobe.d/blacklist-odroid.conf file had "blacklist uas" in it from where we had been trying to fix a problem with the USB bus randomly rebooting a few days earlier. The "blacklist uas" entry was causing the system to try and boot without the USB UAS driver and this was preventing the booting process from finding the USB hard disk. Once we commented out the "blacklist uas" line and rebuilt the initrd file with "update-initramfs -u", the system booted fine on 4.9.30. This fixed the fan noise too. We installed the 4.9.33 kernel and the ODROID XU4 booted fine.
  6. I have my ODROID XU4 configured so that the SD /boot files boot the machine on a SSD formatted to ext4. This works fine with 4.9.30, but fails with the 4.9.33 kernel I installed today. The only useful message I see is that it can't find my SSD's uuid. The uuid is correct so I suspect that the kernel does not have or is not loading a USB driver. Does anyone have a suggestion on how to boot using the 4.9.33 kernel? Thanks, Michael
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines