*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
@Pete,
Looks like someone else met the same issue, and already opened a bug in
the upstream, let's track the upstream bug, after it is fixed by
upstream, we will integrate the fix in the ubuntu kernel.
htt
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I don't have the usb hub which is integrated into the keyboard, I just
have two normal usb hubs.
I plugged both the keyboard and the mouse into the hub and plug the hub
into a rpi4's usb port, power up, bot
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I just wanted to report that USB is working for me with the
5.3.0-1014-raspi2 aarch64 kernel, but neither the keyboard not the mouse
works at boot time when I have my mouse (a Microsoft Basic Optical Mouse
v
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I'm now running a 2019-09-26-raspbian-buster-lite.img with 4.19.75-v7l+
kernel and /dev/mmcblk0* are correctly populated.
pi@raspberrypi:~ $ dmesg | grep firmware
[0.090391] raspberrypi-firmware soc:fir
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
About the problem of "there is no /dev/mmcblk0* device", I checked your
dmesg, there are two places are weird
the 1st one is about the raspberrypi-firmware, on my board, the dmesg will show:
[0.100540]
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
Hi @hui.wang,
the RPi4 boots off the sdcard normally but then I use a USB3 enclosure
with disks to assemble a RAID1 BTRFS device to be used as rootfs. At the
end of the boot, there is no /dev/mmcblk0* devic
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
@Avio,
I could see "mmc-bcm2835 fe30.mmcnr: could not get clk, deferring
probe" too, but didn't meet your problem.
After the system boot up, it will mount the mmcblk0p2 as rootfs and mount
mmcblk0p1 a
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I'm testing this new 5.3.0-1008-raspi2 kernel, USB works as expected but
I get a lot of
> mmc-bcm2835 fe30.mmcnr: could not get clk, deferring probe
in dmesg and /dev/mmcblk0p1 and /dev/mmcblk0p2 don't
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
When will be available fix in packages from regular distribution -
applied with apt update/upgrade?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
We have a bug to track the enabling of v3d.ko
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I have tried the v3d.ko with latest stable version of mesa
19.2
Which works well. glxinfo is the application to show everything is working and
it produces
...Accelerated: yes
for a fast graphical
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
OK, got it, will enable the module of v3d.ko in the kernel of next
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
Thank you for your help so far...
I want (and I have got)
dtoverlay=vc4-fkms-v3d
I want (and I have got) the vm4 drm driver
/lib/modules/5.3.0-1008-raspi2/kernel/drivers/gpu/drm/vc4/vc4.ko
I want
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
With the newupdate kernel, you could delete or comment out the
"dtoverlay=vc4-fkms-v3d" on rpi4/3/2, then the system will use the fb
driver of bcm2708_fb, this will not load the vc4 drm driver.
And to inst
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
OK, with your new "roll up" things are looking quite good, however your
config.txt contains
dtoverlay=vc4-fkms-v3d
I can also see the matching device tree binary object
vc4-fkms-v3d.dtbo
In
/bo
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
Thanks.
ubuntu@ubuntu:~$ sudo dpkg -i
linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
(Reading database ... 97816 files and directories currently installed.)
Preparing to unpack
linux-image
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
If you install the modules and kernel in the #26 successfully, the
'uname -a' will show newupdate.
But I can't find the "newupdate" from the output of yours.
And those patches are not merged to ubuntu kern
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
hmm, not what I expected...
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.3.0-1008-raspi2 #9-Ubuntu SMP Fri Oct 18 13:26:35 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
total_mem=3072 still fixes it
** Attachme
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
Sorry, my mistake I missed this:
Ignoring old or unknown version 5.3.0-1008-raspi2 (latest is 5.3.0-1009-raspi2)
/etc/kernel/postinst.d/zz-flash-kernel:
I have proposed in my sources.list so it ignored you
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
reply Mark Dunn,
The kernel you wget and installed already included the patch for 3093,
so in theory, after installed the new kernel, the usb should work with
4G ram.
Please verify the kernel you are runni
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I have a PI 4 (4GB)
I loaded and installed the arm64 eoan
USB didn't work, ssh did
I set total_mem=1024
USB worked
I set total_mem=3072
USB failed
I set total_mem=1024 and loaded the linux image:
wget
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
@Hui Wang,
My pi is all good now, deeply applicateļ¼
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848703
T
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
And this bug will be fixed with
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
And for me, I run commands through serial console, and if you have the
uart->usb converter, you could use serial console too.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
@reply #21,
The simplest workaround is to plug the sd card into a cardreader and
connect the cardreader to computer, then edit $mount_folder/system-
boot/config.txt
Add total_mem=3072 in the section [pi4],
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
@Hui Wang,
But if I can't use the keyborad by USB, how can I type in those cmd?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
@Scott,
About the bluetooth, this is a comment from Dave Jones:
And one thing which isn't a bug:
Bluetooth: we don't support bluetooth out of the box. Ubuntu on Pi
is primarily a server distro and thu
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
@Ricardo,
just download the deb
(https://people.canonical.com/~hwang4/rpiv2/arm64/) to your pi's rootfs
Then run:
sudo dpkg -i linux-modules-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb
sudo dpkg -i
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
@Scott,
We haven't tested the bluetooth both under old kernel and under patched
kernel, do you know how to verify the bluetooth on the pi? And we are
going to look at bluetooth after fixing the usb host iss
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
It works for me, but no Bluetooth. However, I'm not sure if that's
related/caused by this patch or a known issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I'm a noob, can anyone tell me how to use the petch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848703
Ti
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I can confirm as well - verified that the new patch from @hui.wang is
working correctly on my Pi 4 4GB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
The new patch is working fine connected to my HDMI monitor/TV. I also
removed the temp patch using only 3GB ram, rebooted and all my memory is
now available (Pi4 4GB). Will future updates break the patch or
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
I built a testing kernel, not only includes the fix for USB host, but
also includes all new patches from
https://github.com/raspberrypi/linux.git rpi-5.3.y branch (about 107
patches).
I tested both arm64 a
*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790
Please refer to this bug (the same bug as this one) #1848790
And I will submit the fixing patch to ubuntu kernel.
thx.
** This bug has been marked a duplicate of bug 1848790
USB not working under arm6
Setting total_mem=2048 or 3072 in /boot/firmware/usercfg.txt allowed me
to boot Pi4 4GB with 19.10 64bit with working USB. Of course I have less
RAM now, but working USB.
Likely the above patch will fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Package changed: 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/1848703
Title:
Raspberry Pi 4 - USB Bus not detecting any devices
To manage notifications about thi
Fixed links
User on lingon on raspberry pi forum posted the following:
The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the
issue seen earlier that using more RAM than 3072 MB breaks the USB:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=25[/u
Fixed links
User on lingon on raspberry pi forum posted the following:
The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the
issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/v...46766&start=25
The issue was solved by
User on lingon on raspberry pi forum posted the following:
The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the
issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/view ... 6&start=25
The issue was solved by a kernel pat
Reported/Confirmed/Assigned here:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848703
Title:
Raspberry Pi 4 - USB Bus not detect
I can reproduce this on my 4GB Pi4 with the 64bit image as well. There
are no devices detected -
ubuntu@ubuntu:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.
I can reproduce this on my 4GB Pi4 with the 64bit image.
This does not seem to be an issue with the 32bit image in my quick
testing. With the 32 bit image, both the keyboard and external storage
are detected and working.
As you can see here with my USB keyboard and thumb drive attached, they
are
More discussion and users with same problem here:
https://www.raspberrypi.org/forums/viewtopic.php?p=1553904#p1553904
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848703
Title:
Raspberry Pi 4 - US
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848703
Title:
Raspberry Pi
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
46 matches
Mail list logo
