Here's the one with my L470 (xml + txt). I will provide the ones with
my Ryzen later.
** Attachment added: "l470_i3_7100u.zip"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+attachment/5332646/+files/l470_i3_7100u.zip
--
You received this bug notification because you are a
Sorry, too haste, seems like it works a bit different than Raspbian.
Using your new kernel with this set in usercfg.txt, OTG mode is working fine.
dtoverlay=dwc2,dr_mode=peripheral
though with Raspbian, only "dtoverlay=dwc2" is needed, which was what I
was using.
--
You received this bug
Thanks Hui for the new kernel. It is not fully working yet though. I
attach the two "dmesg --color=always" output for your comparison.
Using your new kernel, my Pi 4B can load g_ether successfully with
Ubuntu. However, OTG mode is still not working as expected. Connected
to my L470 running
Thanks for quick reply. It is the same USB-C power supply port which
can also work as OTG port. I tried Raspbian Buster + g_ether with USB
cable connecting to my machine (Lenovo L470 on docking), and it is
detected. On both Raspbian and my L470 running Ubuntu 19.10, usb0 are
created when I do
Public bug reported:
I am using Raspberry Pi 4B (4GB) and want to make use of the OTG
functionality (g_ether). I cross checked with Raspbian to make sure it
is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with
latest updates applied as of Jan 26th, 2020 via "apt-get update" and
some configuration I'd tried:
1. dtoverlay=dwc_otg, or comment out = no difference
2. with no other dtoverlay, I actually set "dtoverlay=vc4-fkms-v3d" in
syscfg.txt, and comment it out or not also make no difference
I didn't grab every dmesg, but without both dwc_otg and vc4-fkms-v3d,
here you
Hi Hui, just in case I tried again, but no it won't work if I put
"dtoverlay=dwc2" w/o dr_mode. I remember dwc2 should be new code and
should be used, hence why I use that instead of dwc_otg.
Anyway, if we use "dtoverlay=dwc2" only, I guess the actual "dr_mode"
value may not be init properly in
For me I would still prefer using "dtoverlay=dwc2,dr_mode=peripheral" as
it is more reliable at the moment: if pi4 is rebooted remotely, it will
come up with the necessary interface as I added g_cdc to
/etc/modprobe.d/modules.
On my setup it should not be power related, as I'm using a cable that
sorry, typo above: /etc/modules instead of /etc/modprobe.d/modules.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861070
Title:
Raspberry Pi 4B: USB OTG is not working
To manage notifications
Public bug reported:
As of 5.4.0-0ubuntu5 on Ubuntu 19.10 x86_64, available CPU model
selection as I can see from virt-manager is still missing some CPU
models. Here's some info based on running "virsh capabilities"
Host: Lenovo L470 (UEFI=1.71), i3-7100u ==> I cannot select SkyLake-whatever in
** Package changed: libvirt (Ubuntu) => linux-raspi2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864132
Title:
g_ether missing eem support
To manage notifications about this bug go to:
Public bug reported:
I am looking into enabling EEM with g_ether by module option use_eem=1,
and g_ether won't be loaded because it has no EEM support compiled.
Expected: EEM is compiled with g_ether (no such option for g_cdc) so
that it can be enabled by use_eem=1.
My
Here's the other machine's info as requested with AMD CPU.
** Attachment added: "b450m_pro4_ryzen_3600.zip"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1861643/+attachment/5335713/+files/b450m_pro4_ryzen_3600.zip
--
You received this bug notification because you are a member of
Public bug reported:
There is an issue with g_ether after warm reboot.
Hardware I used for testing:
Thinkpad L470 + Dock, Ubuntu 19.10
USB 3.0 "A male-plug Y-cable" + USB-A to USB-C adapter
Pi4 4GB powered by Y-cable connecting to dock and separate USB PSU, Ubuntu 19.10
sorry for delays.
for both of my machines, kvm-ok =>
INFO: /dev/kvm exists
KVM acceleration can be used
and for QMP output, pls. see attachments.
** Attachment added: "amp output for both machines"
Public bug reported:
Problem: erratic host behaviour after "kernel NULL pointer dereference" appears
Config:
host = Ryzen 3600 w/2x16GB, ZFS RAIDZ1 5 vdevs
guest = Windows 7 w/16GB, zvol 64GB+512GB, QXL 16MB (planning for vfio-GPU-pt)
Behavior: per dmesg, seems related to THP compacting + ARC
Confirmed to work now after upgrading to linux-image-5.4.0-1012-raspi,
which also fixed the warm boot issue I'd reported in 1871977.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861070
Title:
*** This bug is a duplicate of bug 1861070 ***
https://bugs.launchpad.net/bugs/1861070
I just updated kernel to have OTG working again as per #1861070, and can
tell that EEM support is still missing.
/sys/module/g_ether/parameters has no entry of use_eem has per "modinfo
g_ether" mentioned.
Sorry I cannot tell, as the OTG issue just come back after I upgraded to
Focal via do-release-upgrade. Pls. refer to bug #1861070
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864132
Title:
I just upgraded to Focal and yes, the issue just come back.
## from dmesg ##
[5.722325] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using
dummy regulator
[5.722385] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using
dummy regulator
[5.722541] dwc2
Sorry OTG is not working on my Pi4 after upgrade to Focal, so I cannot
tell. Again, pls. refer to bug #1861070
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871977
Title:
g_ether not working
Public bug reported:
I am trying QEMU on Raspberry Pi 4 B 4GB and is encountering an issue
trying to start a VM using machine type raspi3b.
OS: Ubuntu 21.04, 5.11.0-1007-raspi
Sample libvirt domain xml (tried to be minimal)
raspi3b
1048576
1048576
4
hvm
destroy
Thanks for looking into it.
1. raspi3b or similar ARM machines do not support ACPI, so the
snippet should not exist in libvirt VM's domain XML, or it will complain
this or that, refusing to start just as you'd tried. That's also why my
example machine XML does not have it.
2. without the
Hi Dann,
Thanks for looking into it. I am trying pi 3b emulation at the moment,
as I want to try things out with VMs instead of the real SBC. My target
is to try things out before deploying to the real SBC, hence why I want
to use emulation of specific machine type. I see that most tutorial
Public bug reported:
My problem is similarly described in this old thread:
https://unix.stackexchange.com/questions/742360/
journalctl message: one of the many related logs
Apr 09 15:37:40.096850 ** kernel: Linux version 6.5.0-26-lowlatency
(buildd@lcy02-amd64-109) (x86_64-linux-gnu-gcc-12
25 matches
Mail list logo
