[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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 issue. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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 thus a stable serial console was prioritized over out-of-the-box Bluetooth support (note: I don't work on Ubuntu MATE; that's something separate). Bluetooth can be enabled by installing the "pi-bluetooth" package and switching a line in "syscfg.txt" on the boot partition from "include nobtcfg.txt" to "include "btcfg.txt". A tool to manage the hardware configuration on the Pi (including Bluetooth) is being developed, but I didn't have time to finish it for Eoan. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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 running is the new kernel, please upload the output of 'uname -a' and dmesg. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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 kernel yet, so if you install the kernel from ubuntu sources, the usb host issue is not fixed. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
@Rohit, Got it, thx, and please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1849369/comments/1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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 and armhf kernels on Pi4 without HDMI monitor, everything works well. Could anybody help test these two kernels on Pi4 with HDMI monitor, Pi3 and Pi2 if you have any of them? After verifying the kernel will not introduce regression on Pi4/3/2, I will submit the patches to UBUNTU kernel. The new kernel could be downloaded: https://people.canonical.com/~hwang4/rpiv2/ To install and test the kernel: copy arm64 or armhf folders to rootfs of Pi, sudo dpkg -i linux-modules-.deb; sudo dpkg -i linux-image-xxx.deb;sudo reboot thx -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
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 and armhf kernels on Pi4 without HDMI monitor, everything works well. Could anybody help test these two kernels on Pi4 with HDMI monitor, Pi3 and Pi2 if you have any of them? After verifying the kernel will not introduce regression on Pi4/3/2, I will submit the patches to UBUNTU kernel. The new kernel could be downloaded: https://people.canonical.com/~hwang4/rpiv2/ To install and test the kernel: copy arm64 or armhf folders to rootfs of Pi, sudo dpkg -i linux-modules-.deb; sudo dpkg -i linux-image-xxx.deb;sudo reboot thx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848247] Re: 3A+ boot failure on Eoan
So far, what I got from investigation is: After setting vc4-fkms-v3d, the fb driver's sequence is bootloader -> simplefb -> drm_vc4 fb Without vc4-fkms-v3d, the sequence is bootloader -> simplefb -> bcm2708_fb (the screen will flicker when bcm2708_fb takeover the display) I will continue looking at the bcm2708_fb. And for 3A+ booting issue, after adding vc4-fkms-v3d, the system need much memory, but 3A+ only have 512M physical memory, looks like the 512M is not enough for drm_vc4, so the kernel crash with "out of memory errors". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848247 Title: 3A+ boot failure on Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1848247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848247] Re: 3A+ boot failure on Eoan
I mean the simplefb driver in the kernel in the #3, I didn't know there is a simplefb driver in the uboot too. So it looks like: uboot.simplefb ---> kernel.simplefb works fine uboot.simplefb ---> kernel.simplefb > drm_vc4_fb works fine (but RPI3A+ crash) uboot.simplefb ---> kernel.simplefb ---> kernel.bcm2708_fb makes the screen flicker -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848247 Title: 3A+ boot failure on Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1848247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
I reproduced this bug on my rpi4 board. ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => High ** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
The testing kernel in the #12 is for fixing the internal mic, so no need to test external mic plugging (#13). For #14, it is internal mic, could you record sound with internal mic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
** Description changed: - The EOAN kernel has alsa/sof driver, we need to enable SOF_HDA link and - codec, then the sof can work with legacy HDA driver to enable audio - output and input on LENOVO and DELL machines. + + [Impact] + We tested the EOAN kernel on the LENOVO or Dell machines which have + dmic directly connnected to PCH, the dmic didn't work. + + [Fix] + We need to enable SOF_HDA link and codec, then the sof driver + and Legacy HDA driver work together to make the dmic work. + + [Test Case] + Install the latest 19.10 image, build a new kernel with this + patch and replace the existing kernel, After installing the blacklist + package (blacklist snd_hda_intel and snd_soc_skl) and ucm package, + the dmic and all output devices (speaker/hdmi) work. + + [Regression Risk] + Low, these configs are already enabled in the oem-b-osp1 kernel + for a long time, and we tested it on many lenovo/dell machines witch + have or have no dmic, all worked well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848490] [NEW] eoan: alsa/sof: Enable SOF_HDA link and codec
Public bug reported: The EOAN kernel has alsa/sof driver, we need to enable SOF_HDA link and codec, then the sof can work with legacy HDA driver to enable audio output and input on LENOVO and DELL machines. ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847250] Re: update firmware for sound sof driver to fix the hang issue on several Dell machines
** Tags added: verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838599] Re: alsa/sof: need to update the firmware of sound sof driver
** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838599 Title: alsa/sof: need to update the firmware of sound sof driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1838599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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], just like below: [pi4] kernel=uboot_rpi_4.bin max_framebuffers=2 total_mem=3072 Then reboot, you could you the usb keyboard now, after installing the testing kernel, you could remove total_mem=3072. And another way to login is to use ssh. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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, 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
And also Pi 3 Model A Plus is not in the all.db. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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 Ubuntu. https://bugs.launchpad.net/bugs/1848703 Title: Raspberry Pi 4 - USB Bus not detecting any devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847596] Re: rpi3b+: corrupted screen on hdmi
And this bug will be fixed with https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623 And there is a testing kernel, we could install this testing kernel and remove the vc4-fkms-v3d from the config.txt. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/comments/11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847596 Title: rpi3b+: corrupted screen on hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848075] Re: eoan server image does not boot on RPI3-A+
*** This bug is a duplicate of bug 1848247 *** https://bugs.launchpad.net/bugs/1848247 About the root cause and fix for this bug, please refer to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/comments/9 https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/comments/10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848075 Title: eoan server image does not boot on RPI3-A+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847596] Re: rpi3b+: corrupted screen on hdmi
This problem is fixed by this commit, it is in the
https://github.com/raspberrypi/linux.git
(the data structure does not match the firmware definition)
commit 26f64fa81357f4b18192432eb8023f99c7eb5cf7 (HEAD ->
26f64fa81357f4b18192432eb8023f99c7eb5cf7)
Author: Michael Brown
Date: Sun Sep 22 21:51:29 2019 +0100
bcm2708_fb: Fix layout of struct vc4_display_settings_t
The display parameters returned by the VC4 firmware in response to the
RPI_FIRMWARE_FRAMEBUFFER_GET_DISPLAY_SETTINGS tag do not match the
layout of struct vc4_display_settings_t: the colour depth and row
pitch are erroneously swapped in the kernel definition. This can
trigger a kernel warning from pixel_to_pat(), such as:
pixel_to_pat(): unsupported pixelformat 7296
Fix by adjusting the layout of struct vc4_display_settings_t to match
the layout as used by the VC4 firmware.
Signed-off-by: Michael Brown
diff --git a/drivers/video/fbdev/bcm2708_fb.c b/drivers/video/fbdev/bcm2708_fb.c
index 4da577c8a0d8..59443f79f228 100644
--- a/drivers/video/fbdev/bcm2708_fb.c
+++ b/drivers/video/fbdev/bcm2708_fb.c
@@ -88,8 +88,8 @@ struct vc4_display_settings_t {
u32 display_num;
u32 width;
u32 height;
- u32 pitch;
u32 depth;
+ u32 pitch;
u32 virtual_width;
u32 virtual_height;
u32 virtual_width_offset;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847596
Title:
rpi3b+: corrupted screen on hdmi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
@Rohit, I will take a look at the issue of kvm, and do you know if the 18.04 support kvm on rpi3/2? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
Well noted, thanks, And Intel sent an email about this issue to us yesterday, we will fix this issue according to you and Intel's suggestion. On 2019/10/22 上午3:03, Paul van Schayck wrote: > I can confirm this is currently an issue on the Lenovo X1 Carbon 7th > gen. I did some testing with the current 19.10 kernel > (5.3.0-18-generic), and posted my results to this github issue for the > SOF project [1]. > > They confirmed this is most likely an issue with the kernel config for > Ubuntu. And also posted some suggestions for the required kernel configs > to fix this [2]. > > I also did manual changes to the alsa ucm package, blacklist the > snd_hda_intel and snd_soc_skl module and install the topology provided > by Lenovo. > > [1] https://github.com/thesofproject/sof/issues/1885#issuecomment-544252992 > [2] https://github.com/thesofproject/sof/issues/1885#issuecomment-544498765 > > ** Bug watch added: github.com/thesofproject/sof/issues #1885 > https://github.com/thesofproject/sof/issues/1885 > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849369] Re: Ubuntu 19.10 ARM64 kernel has KVM disabled by default
*** This bug is a duplicate of bug 1783961 *** https://bugs.launchpad.net/bugs/1783961 I built a testing kernel which enabled the KVM, please test it on rpi4/3 (arm64) and rpi4/3/2 (armhf) boards. https://people.canonical.com/~hwang4/pi4kvm/ thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849369 Title: Ubuntu 19.10 ARM64 kernel has KVM disabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
I built a testing kernel which enabled the KVM, please test it on rpi4/3 (arm64) and rpi4/3/2 (armhf) boards. https://people.canonical.com/~hwang4/pi4kvm/ thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
According to #20, there is no change for external mic plugging, so we could not fix it by ourselves. The best way is to notify the XiaoMi and let them ask for help from realtek. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
** Description changed: + [Impact] + With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT + is set to Y, then it will make the legacy intel soc driver fail, and + moreover the current sof driver can't support broadwell well, as a + result, many broadwell computers with I2S codec can't support sound anymore. + + [Fix] + Intel submitted a patch, it will make those two kconfig options exclusive, + and the legacy soc's option has higher priority, if both of them are + enabled, sof's option will be disabled. + + [Test Case] + Build the kernel and check the debian/build/$buidling_dir/.config, the + SND_SOC_SOF_BROADWELL_SUPPORT is disabled. + + [Regression Risk] + Low, so far, the sof driver can't support broadwell machine well, so + there is no machine use this driver yet. + + Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64
[Bug 1852510] Re: IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel)
** Summary changed: - IO errors when writing large amounts of data to USB storage in eoan on RPI + IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852510] Re: IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel)
** Description changed: + [Impact] + On the RPI2/3 boards with eoan armhf kernel, if we copy large size + files to usb stick, the usb host driver dwc_otg will fail and print + lots of IO errors in the dmesg. + + [Fix] + To support rpi4, we enabled the LPAE/HIGHMEM/VMSPLIT_3G in the armhf + kernel, the dwc_otg has some problem with highmem enabled. If the + urb's buffer is in the highmem region, the enqueue function will return + the -EINVALID unconditionally, as a result, it can't handle the urb + which contains the highmem buffer. But the driver itself can handle the + highmem buffer, we just need to do a little change. + + [Test Case] + With the patch applied, I tested armhf and arm64 kernel on rpi2/3/4, + all worked well, no regression and the usb driver works well. + + [Regression Risk] + Low, the upstream already looked at my patch and agreed with my + change, and I tested the patch on rpi2/3/4 with armhf and arm64 + kernels, all worked well. + + Kernel tested: Linux ubuntu 5.3.0-1012-raspi2 #14-Ubuntu SMP Mon Nov 11 10:08:39 UTC 2019 armv7l armv7l armv7l GNU/Linux I've only been able to reproduce this with the armhf kernel and on the following devices: RPI3B+ RPI3B RPI2 At the moment, it does not appear that arm64 is affected, nor are RPI3A+ and RPI4 (at least not the 2GB version) Steps to reproduce: - Insert and mount a USB storage device - cp a large file to it (300-600MB recommended - smaller files will sometimes not trigger it) - sync After running the sync, a lot of IO errors will show up in dmesg like: [ 176.129299] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 176.129326] sd 0:0:0:0: [sda] tag#0 CDB: Write(10) 2a 00 00 2e 24 b0 00 00 f0 00 [ 176.129349] blk_update_request: I/O error, dev sda, sector 3024048 op 0x1:(WRITE) flags 0x4000 phys_seg 15 prio class 0 [ 176.883968] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg [ 177.079960] usb 1-1.1.2: reset high-speed USB device number 8 using dwc_otg It eventually finishes, and if you unmount/remount the device, the checksum will be different from the original file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
Thanks for your testing, I will post the remaining issues to upstream and let us wait for the fixes for the remaining issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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 as /boot/firmware. I don't know why you couldn't see mmcblk0p1/2. Could you use ethernent, if yes, you could upgrade the kernel to 1012, to do so: sudo apt-get update sudo apt install linux-image-5.3.0-1012-raspi2 sudo reboot If you still can't see mmcblk0p1/p2, could you please upload the complete dmesg to lp? thx. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853789] [NEW] Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel
Public bug reported: We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed kernel, then we got lots of reports from users that this driver is not stable, it will crash randomly, so let us disable this driver again and wait for the upstream branch rpi-5.3.y has the fixes for it. Users report crash of this driver via: #1852035 and #1850876 This bug is for tracking the reverting the fix of #1850876. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853789 Title: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853791] [NEW] External microphone can't work on some dell machines with the codec alc256 or alc236
Public bug reported: tracking purpose ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853791 Title: External microphone can't work on some dell machines with the codec alc256 or alc236 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
*** This bug is a duplicate of bug 1850876 *** https://bugs.launchpad.net/bugs/1850876 Got it, thanks, We will disable the driver v3d again in the kernel until the branch rpi-5.3.y has the perfect fix for this driver. And set this bug duplicated to #1850876. ** This bug has been marked a duplicate of bug 1850876 CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842998] Re: alsa/hda/realtek: The microphone and mic of headset are uesless on a ThinkCentre
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842998 Title: alsa/hda/realtek: The microphone and mic of headset are uesless on a ThinkCentre To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1842998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel
** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853789 Title: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853791] Re: External microphone can't work on some dell machines with the codec alc256 or alc236
** Tags added: originate-from-1852542 somerville ** Tags added: originate-from-1849286 ** Tags added: originate-from-1849075 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853791 Title: External microphone can't work on some dell machines with the codec alc256 or alc236 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847596] Re: rpi3b+: corrupted screen on hdmi
** Changed in: linux-raspi2 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847596 Title: rpi3b+: corrupted screen on hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853789] Re: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel
** Description changed: We enabled this driver in the linux-image-5.3.0-1013-raspi2 proposed kernel, then we got lots of reports from users that this driver is not stable, it will crash randomly, so let us disable this driver again and wait for the upstream branch rpi-5.3.y has the fixes for it. Users report crash of this driver via: #1852035 and #1850876 This bug is for tracking the reverting the fix of #1850876. + + [Impact] + According to the #1852035 and #1850876, users reported that the driver + v3d will crash under desktop, then I checked the upstream kernel, the + branch rpi-5.3.y was merged some fixes for v3d driver on Nov 11, I + tested this branch myself, found the driver still has some problem. + I also applied those patches to eoan kernel and built a testing + kernel, users reported similar problems with this testing kernel. + + So the safest way is to disable this driver in the kernel agian, until + the branch rpi-5.3.y has the fixes for this driver. Or we could + investigate and backport fixes from rpi-4.19.y later. + + [Fix] + Revert a patch in the 1013 kernel. + + + [Test Case] + Users tested 1012 kernel a lot, they didn't report the unstable issues, + and before the 1013, this driver was always disabled. + + [Regression Risk] + Low, just revert a new enabled driver in the 1013 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853789 Title: Need to disable CONFIG_DRＭ_V3D in the raspi2 eoan kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853791] Re: External microphone can't work on some dell machines with the codec alc256 or alc236
** Description changed: - tracking purpose + [Impact] + The external microphone can't work on some dell machines with the + codec alc256 or alc236 + + [Fix] + Need to apply the ALC255_FIXUP_DELL1_MIC_NO_PRESENCE, instead of + adding a new pintbl in the quirk table, we use fallback table this + time. + + [Test Case] + tested the kernel with these patches, the external mic worked well. + + [Regression Risk] + Low, just make the quirk applying more generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853791 Title: External microphone can't work on some dell machines with the codec alc256 or alc236 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
@Ian, "rock solid WITH acceleration when using Gentoo", could you please tell me what is the kernel version for Gentoo? Or could you paste the output of 'uname -a' under Gentoo? I tested the branch rpi-5.3.y of upstream kernel (https://github.com/raspberrypi/linux.git), the v3d driver is better now, but still has some problems. So I guess the Gentoo uses 4.19 kernel? BTW, we have another bug to track this issue https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035, from the comment #14 and #15 of that bug, we could see even applying the latest patches of v3d, the driver still has some problems. So we need to disable the driver v3d in the kernel until the branch rpi-5.3.y has the perfect fix for this driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
On 2019/11/29 下午11:15, Mark Dunn wrote: > short version: > > With raspberry pi 4: > your binaries applied (https://people.canonical.com/~hwang4/v3d-fix/) > The screen flickers then blanks > I installed an built the latest mesa > The screen flickers then blanks > Back to the raspberry pi kernel (4.19) > Which still works... > > long version: > > downloaded ubuntu-19.10-preinstalled-server-arm64+raspi3.img and > restored it to sdcard > > sudo apt update > sudo apt upgrade > sudo apt install ubuntu-desktop > > wget > https://people.canonical.com/~hwang4/v3d-fix/linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > wget > https://people.canonical.com/~hwang4/v3d-fix/linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > wget > https://people.canonical.com/~hwang4/v3d-fix/linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > wget > https://people.canonical.com/~hwang4/v3d-fix/linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > > sudo dpkg -i linux-modules-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > sudo dpkg -i linux-image-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > sudo dpkg -i linux-buildinfo-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > > sudo dpkg -i linux-headers-5.3.0-1013-raspi2_5.3.0-1013.15+v3d_arm64.deb > linux-headers-5.3.0-1013-raspi2 depends on linux-raspi2-headers-5.3.0-1013; > however: >Package linux-raspi2-headers-5.3.0-1013 is not installed. > sudo apt --fix-broken install > The following packages will be REMOVED: >linux-headers-5.3.0-1013-raspi2 > > sudo reboot > sudo apt-get install mesa-utils > > glxinfo -B > > name of display: :0 > display: :0 screen: 0 > direct rendering: Yes > Extended renderer info (GLX_MESA_query_renderer): > Vendor: Broadcom (0x14e4) > Device: V3D 4.2 (0x) > Version: 19.2.1 > Accelerated: yes > Video memory: 3791MB > Unified memory: yes > Preferred profile: compat (0x2) > Max core profile version: 0.0 > Max compat profile version: 2.1 > Max GLES1 profile version: 1.1 > Max GLES[23] profile version: 3.0 > OpenGL vendor string: Broadcom > OpenGL renderer string: V3D 4.2 > OpenGL version string: 2.1 Mesa 19.2.1 > OpenGL shading language version string: 1.20 > > OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.1 > OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 > > glxgears > > Running synchronized to the vertical refresh. The framerate should be > approximately the same as the monitor refresh rate. > 348 frames in 5.0 seconds = 69.440 FPS > 247 frames in 5.0 seconds = 49.358 FPS > 301 frames in 5.0 seconds = 60.029 FPS > 301 frames in 5.0 seconds = 60.019 FPS > 300 frames in 5.0 seconds = 59.999 FPS > 300 frames in 5.0 seconds = 59.992 FPS > 256 frames in 5.0 seconds = 51.041 FPS > 300 frames in 5.0 seconds = 59.989 FPS > 301 frames in 5.0 seconds = 60.011 FPS > X connection to :0 broken (explicit kill or server shutdown). Are your sure you booted the system with the v3d-fix kernel? I remember with that kernel, the glxgears at least could run without crash or system hang, of course the v3d-fix has some other problems. So could you please run 'uname -a' to check the kernel you are running? And our plan is to disable this driver temporarily, we will report bug to usptream against rpi-5.3.y, and we will look for fixes from 4.19 branch too. Thanks, Hui. > > Eventually screen starts to flicker then blanks... > built and installed latest mesa - no change > > sudo nano /etc/apt/sources.list (commented in all sources) > sudo apt update > sudo apt-get build-dep mesa > > mkdir git > cd git > sudo apt-get build-dep mesa > sudo apt-get install -y pkg-config bison flex > > git clone https://gitlab.freedesktop.org/mesa/drm.git > cd drm > meson build --prefix=/usr --libdir=/usr/lib/aarch64-linux-gnu > ninja -C build > sudo ninja -C build install > cd .. > > git clone https://gitlab.freedesktop.org/mesa/mesa.git > cd mesa > meson build \ > --prefix=/usr \ > --libdir=/usr/lib/aarch64-linux-gnu \ > -Dbuildtype=release \ > -Dplatforms=x11,drm,surfaceless \ > -Ddri-drivers= \ > -Dgallium-drivers=vc4,v3d,kmsro > ninja -C build > sudo ninja -C build install > > sudo reboot > > flickers and then blanks :( > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices
*** 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] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-08-15 12:03, variant start [0.110122] raspberrypi-firmware soc:firmware: Firmware hash is 9f8431fb7839c7f00f52b81f5822ddab2b31d0db And there are not errors about firmware, but your dmesg is different. the 2nd one is about mmc-bcm2835 driver, your kernel always report: mmc-bcm2835 fe30.mmcnr: could not get clk, deferring probe That is different from my board, on my board, it only reports that message once, Then the driver could get the clk successfully. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854620] Re: Kernel crash on RasPi 3B+ (ARM64)
You built the kernel "4.14.66-chainsx-cxcore+ (r...@myhost.nopad.org)" yourself? Looks like it is not a canonical's kernel. According to the log, It looks like some userspace apps make the kernel crash, it is weird since usually userspace can't crash kernel. And the calltrace doesn't show which driver or kernel module is called before crashing, so far my idea is to disable kernel drivers little by little until the crash doesn't happen. First, you could disable wifi (you could use ethernet if you need network) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854620 Title: Kernel crash on RasPi 3B+ (ARM64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849623] Re: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea)
** Changed in: linux-raspi2 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849623 Title: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852070] Re: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0]
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852070 Title: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1852070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
I just followed your steps to do the test, I followed all steps except step 7, since on my board, no need to run "netplan try" and "netplan apply", the eth0 and wlan0 already can get the ip from my router. Other steps are same. I can't reproduce your problem, with the new installed 1012 kernel, no matter I plug ethernet or not, I can ssh to wlan0 always. I don't know why you have problem. When problem happens, you could check the /var/log/syslog, it should contain the log about getting the ip for eth0 and wlan0, maybe you could find sth is not correct in that log. for example: Nov 24 07:17:04 ubuntu systemd-networkd[1098]: eth0: Gained carrier Nov 24 07:17:04 ubuntu systemd-networkd[1098]: eth0: DHCPv4 address 192.168.1.106/24 via 192.168.1.1 Nov 24 07:17:04 ubuntu systemd-timesyncd[1141]: Network configuration changed, trying to establish connection. Nov 24 07:17:03 ubuntu systemd-resolved[1139]: Using degraded feature set (UDP) for DNS server 202.106.46.151. Nov 24 07:17:03 ubuntu dbus-daemon[1208]: [system] AppArmor D-Bus mediation is enabled Nov 24 07:17:06 ubuntu wpa_supplicant[1097]: wlan0: WPA: Key negotiation completed with 50:bd:5f:ff:68:12 [PTK=CCMP GTK=CCMP] Nov 24 07:17:06 ubuntu wpa_supplicant[1097]: wlan0: CTRL-EVENT-CONNECTED - Connection to 50:bd:5f:ff:68:12 completed [id=0 id_str=] Nov 24 07:17:06 ubuntu systemd-networkd[1098]: wlan0: Gained carrier Nov 24 07:17:06 ubuntu systemd[1]: Started Snappy daemon. Nov 24 07:17:06 ubuntu systemd[1]: Starting Wait until snapd is fully seeded... Nov 24 07:17:06 ubuntu systemd-networkd[1098]: wlan0: DHCPv4 address 192.168.1.107/24 via 192.168.1.1 Nov 24 07:17:06 ubuntu pollinate[1242]: client verified challenge/response with [https://entropy.ubuntu.com/] Nov 24 07:17:06 ubuntu pollinate[1242]: client hashed response from [https://entropy.ubuntu.com/] Nov 24 07:17:06 ubuntu lxd.activate[1243]: => Starting LXD activation Nov 24 07:17:06 ubuntu lxd.activate[1243]: ==> Loading snap configuration Nov 24 07:17:06 ubuntu lxd.activate[1243]: ==> Checking for socket activation support Nov 24 07:17:06 ubuntu pollinate[1242]: client successfully seeded [/dev/urandom] Nov 24 07:17:06 ubuntu systemd[1]: pollinate.service: Succeeded. Nov 24 07:17:06 ubuntu systemd[1]: Started Pollinate to seed the pseudo random number generator. Nov 24 07:17:06 ubuntu systemd[1]: Starting OpenBSD Secure Shell server... Nov 24 07:17:06 ubuntu systemd[1]: Started Wait until snapd is fully seeded. Nov 24 07:17:06 ubuntu systemd[1]: Starting Apply the settings specified in cloud-config... Nov 24 07:17:06 ubuntu systemd[1]: Condition check resulted in Auto import assertions from block devices being skipped. Nov 24 07:17:07 ubuntu lxd.activate[1243]: ==> Setting LXD socket ownership Nov 24 07:17:07 ubuntu lxd.activate[1243]: ==> LXD never started on this system, no need to start it now Nov 24 07:17:07 ubuntu systemd[1]: snap.lxd.activate.service: Succeeded. Nov 24 07:17:07 ubuntu systemd[1]: Started Service for snap application lxd.activate. Nov 24 07:17:07 ubuntu systemd[1]: Started OpenBSD Secure Shell server. Nov 24 07:17:07 ubuntu systemd[1]: Reached target Multi-User System. Nov 24 07:17:07 ubuntu systemd[1]: Reached target Graphical Interface. Nov 24 07:17:07 ubuntu systemd[1]: Starting Update UTMP about System Runlevel Changes... Nov 24 07:17:07 ubuntu systemd[1]: systemd-update-utmp-runlevel.service: Succeeded. Nov 24 07:17:07 ubuntu systemd[1]: Started Update UTMP about System Runlevel Changes. Nov 24 07:17:07 ubuntu systemd-resolved[1139]: Using degraded feature set (UDP) for DNS server 202.106.46.151. Nov 24 07:17:08 ubuntu systemd-networkd[1098]: wlan0: Gained IPv6LL Nov 24 07:17:08 ubuntu systemd-networkd[1098]: wlan0: Configured -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
The upstream has some fixes for v3d driver, I applied them to the kernel and built a testing kernel: https://people.canonical.com/~hwang4/v3d-fix/ Please also monitor the dmesg, to see if there are some "gpu mmc pte errors" in the dmesg. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854401] Re: headphone has noise as not mute on dell machines with alc236/256
** Description changed: - tracking purpose + [Impact] + There is noise in the headphone on some dell machines with the + codec alc256 or alc236 + + [Fix] + Realtek provide a patch to disable PCBEEP_IN to heapdhone. + + [Test Case] + tested the kernel with this patch, the noise disappeared. + + [Regression Risk] + Low, Realtek provided the patch, and it is limited to apply + to alc236 and 256, and just disable the PCBEEP_IN to headphone.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854401 Title: headphone has noise as not mute on dell machines with alc236/256 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854401] [NEW] headphone has noise as not mute on dell machines with alc236/256
Public bug reported: tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1853952 somerville ** Tags added: originate-from-1853952 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854401 Title: headphone has noise as not mute on dell machines with alc236/256 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
@Askshay, This is the new image you could have a try with. http://cdimage.ubuntu.com/ubuntu-server/eoan/daily- preinstalled/20191126.2/ And "100% happen" means it will freeze every time you reboot and input the password to login. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
@Erik, Dave Jones is working on the flash-kernel, and I remember there is already a bug to track this issue. Let Dave answer your question. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel: edit the $rpi_rootfs/etc/apt/sources.list and add: deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse boot the rpi board, then run: sudo apt-get update sudo apt install linux-image-5.3.0-1013-raspi2 sudo reboot Then you could do the test with the proposed kernel. At least the 1013 kernel fixed these bugs compared with 1012 kernel: https://bugs.launchpad.net/bugs/1850876 https://bugs.launchpad.net/bugs/1852510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel: edit the $rpi_rootfs/etc/apt/sources.list and add: deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse boot the rpi board, then run: sudo apt-get update sudo apt install linux-image-5.3.0-1013-raspi2 sudo reboot Then you could do the test with the proposed kernel. At least the 1013 kernel fixed these bugs compared with 1012 kernel: https://bugs.launchpad.net/bugs/1850876 https://bugs.launchpad.net/bugs/1852510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847596] Re: rpi3b+: corrupted screen on hdmi
We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel: edit the $rpi_rootfs/etc/apt/sources.list and add: deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse boot the rpi board, then run: sudo apt-get update sudo apt install linux-image-5.3.0-1013-raspi2 sudo reboot Then you could do the test with the proposed kernel. At least the 1013 kernel fixed these bugs compared with 1012 kernel: https://bugs.launchpad.net/bugs/1850876 https://bugs.launchpad.net/bugs/1852510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847596 Title: rpi3b+: corrupted screen on hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel: edit the $rpi_rootfs/etc/apt/sources.list and add: deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse boot the rpi board, then run: sudo apt-get update sudo apt install linux-image-5.3.0-1013-raspi2 sudo reboot Then you could do the test with the proposed kernel. At least the 1013 kernel fixed these bugs compared with 1012 kernel: https://bugs.launchpad.net/bugs/1850876 https://bugs.launchpad.net/bugs/1852510 ** Summary changed: - USB not working under arm64 on Pi4 + USB not working under arm64 on Pi4 with 4G ram -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 with 4G ram To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852510] Re: IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel)
We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel: edit the $rpi_rootfs/etc/apt/sources.list and add: deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse boot the rpi board, then run: sudo apt-get update sudo apt install linux-image-5.3.0-1013-raspi2 sudo reboot Then you could do the test with the proposed kernel. At least the 1013 kernel fixed these bugs compared with 1012 kernel: https://bugs.launchpad.net/bugs/1850876 https://bugs.launchpad.net/bugs/1852510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI2/3 (armhf kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
We are going to release a new kernel soon, right now it is in the proposed channel, Welcome to test with the new kernel: edit the $rpi_rootfs/etc/apt/sources.list and add: deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed main restricted deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed universe deb http://ports.ubuntu.com/ubuntu-ports eoan-proposed multiverse boot the rpi board, then run: sudo apt-get update sudo apt install linux-image-5.3.0-1013-raspi2 sudo reboot Then you could do the test with the proposed kernel. At least the 1013 kernel fixed these bugs compared with 1012 kernel: https://bugs.launchpad.net/bugs/1850876 https://bugs.launchpad.net/bugs/1852510 ** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852510] Re: IO errors when writing large amounts of data to USB storage in eoan on RPI
** Changed in: linux-raspi2 (Ubuntu Eoan) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852510] Re: IO errors when writing large amounts of data to USB storage in eoan on RPI
I reproduced this problem on the rpi3B+ and rpi2Bv1.1 with armhf kernel. This problem is introduced by enabling two kernel configs for arm32 kernel, they are HIGHMEM and VMSPLIT_3G. We need to use a single arm32 kernel to support rpi2/3/4, while rpi4 has 1G/2G/4G ram, to support 2G and 4G ram, we have to enable HIGHMEM and VMSPLIT_3G, otherwise we can't get 2G/4G memory in the system. The upstream kernel of https://github.com/raspberrypi/linux.git also has this issue. some explanation: These two configs are specific to 32bit kernel, so we can't reproduce this issue on arm64 kernel. The usb ports on rpi4 are routed to xhci host controller instead of dwc_otg host controller, so we can't reproduce this issue on rpi4 even with armhf kernel. On rpi3A+ board, there are only 512M physical memory, there is no ram to map to highmemory region, so we can't reproduce this problem on rpi3A+. I guess the problem is in the dwc_otg usb host driver, it depends on dma to work, but dma gets a highmem buffer then it can't work normally anymore. I will report this issue to rpi community and try a find a fix asap. so far, the workaround is to set total_mem=512 in the config.txt for rpi2/3 working with 32bit kernel , then there is no memory mapped to highmem region. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852510 Title: IO errors when writing large amounts of data to USB storage in eoan on RPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok.
To install the testing kernel: sudo dpkg -i linux-modules-xxx.deb sudo dpkg- i linux-image-xxx.deb sudo dpkg -i linux-modules-extra-xxx.deb reboot To choose the kernel: you could press ESC button during the grub (bootloader) stage, then there is a menu you could choose the kernel. After booting up, you could run uname -a to verify the kernel you are running. To uninstall the testing kernel: sudo dpkg -p linux-modules-extra-xxx.deb (run dpkg --list | grep linux-modules-extra*, then you will konw the full name of linux-modules-extra-xxx.deb) sudo dpkg -p linux-image-xxx.deb sudo dpkg -p linux-modules-xxx.deb. reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok.
following the #5, the testing kernel is at: https://people.canonical.com/~hwang4/conexant-test/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok.
Please test this kernel, let us see if the kernel fixes the problem or not. If not, please upload a new alsa-info.txt. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845677] Re: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen
About the hdmi audio on the dock, with the current kernel, it can't work. And Intel is working on it, kernel patches are ready, but they need to modify the ucm. After they finish them, we will integrate them into the ubuntu linux. Please wait for 1 month or about 2 months. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845677 Title: volume control doesn't work (it's just on/off) on Lenovo ThinkPad X1 Carbon 7th gen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853030] Re: No connection through SSH over WIfi after kernel update
It is weird, my router is very old, it only supports 2.4G, and I can't reproduce the problem under 2.4G. (This is my laptop, it connects to my old router too.) hwang4@hwang4-Vostro-5390:~$ sudo iwlist wlp0s20f3 frequency wlp0s20f3 32 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Channel 36 : 5.18 GHz Channel 40 : 5.2 GHz Channel 44 : 5.22 GHz Channel 48 : 5.24 GHz Channel 52 : 5.26 GHz Channel 56 : 5.28 GHz Channel 60 : 5.3 GHz Channel 64 : 5.32 GHz Channel 100 : 5.5 GHz Channel 104 : 5.52 GHz Channel 108 : 5.54 GHz Channel 112 : 5.56 GHz Channel 116 : 5.58 GHz Channel 120 : 5.6 GHz Channel 124 : 5.62 GHz Channel 128 : 5.64 GHz Channel 132 : 5.66 GHz Channel 136 : 5.68 GHz Channel 140 : 5.7 GHz Current Frequency=2.412 GHz (Channel 1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853030 Title: No connection through SSH over WIfi after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1853030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
Do you mean the you can't hear sound from headphone or lineout jack? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846988] Re: [Audio playback] No 'Speaker - Built-in Audio'
Please test mainline kernel v5.3, let us see if this kernel works or not. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846988 Title: [Audio playback] No 'Speaker - Built-in Audio' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847192] [NEW] drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms
Public bug reported: [Reproduce Steps] 1. Enter s2idle 2. Press power button to wake up the system 3. The Select Audio Device dialog show up [Results] Expected: There is no dialog show up Actual: The Select Audio Device dialog show up ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: originate-from-1842025 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1842025 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847192 Title: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847500] Re: Full RAM on Pi4 isn't accessible when using u-boot
This is the log of armhf kernel + armhf uboot: MMC: emmc2@7e34: 0, mmcnr@7e30: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Net: Net Initialization Skipped No ethernet found. Unknown command 'usb' - try 'help' Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 777 bytes read in 47 ms (15.6 KiB/s) ## Executing script at 0240 7315968 bytes read in 1424 ms (4.9 MiB/s) 20730891 bytes read in 3932 ms (5 MiB/s) Kernel image @ 0x100 [ 0x00 - 0x6fa200 ] ## Flattened Device Tree blob at 0300 Booting using the fdt blob at 0x300 Using Device Tree in place at 0300, end 0300d350 Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 5.3.0-1004-raspi2 (root@hwang4-Vostro-5390) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #5 SMP Wed Sep 18 23:44:29 CST 2019 (Ubuntu 5.3.0-1004.5-raspi2 5.3.0) [0.00] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d [0.00] CPU: div instructions available: patching division code [0.00] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [0.00] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1 [0.00] Memory policy: Data cache writealloc ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.3.0-1004-raspi2 #5 SMP Wed Sep 18 23:44:29 CST 2019 armv7l armv7l armv7l GNU/Linux ubuntu@ubuntu:~$ free totalusedfree shared buff/cache available Mem:3916244 145836 3600732 21912 169676 3704604 Swap: 0 0 0 ubuntu@ubuntu:~$ sudo ifconfig wlan0 up ubuntu@ubuntu:~$ sudo iwlist wlan0 scanning wlan0 Scan completed : Cell 01 - Address: 58:C8:76:6B:C3:11 Channel:36 Frequency:5.18 GHz (Channel 36) Quality=34/70 Signal level=-76 dBm Encryption key:on ESSID:"CMCC-T69d-5G" Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf= Extra: Last beacon: 4ms ago IE: Unknown: 000C434D43432D543639642D3547 IE: Unknown: 01088C129824B048606C IE: Unknown: 030124 IE: Unknown: 05040001000C IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : TKIP CCMP Authentication Suites (1) : PSK IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : TKIP CCMP Authentication Suites (1) : PSK IE: Unknown: DD270050F204104A000110104400010210470010BC329E001DD811B2860158C8766BC311103C000102 IE: Unknown: 2D1AEF0117010C00 IE: Unknown: 3D1624050400 IE: Unknown: BF0C3000C031FAFF0C03FAFF0C03 IE: Unknown: C005012A00FAFF IE: Unknown: 7F080040 IE: Unknown: DD180050F202010103A427A442435E0062322F00 IE: Unknown: 200100 IE: Unknown: C304020F0F00 IE: Unknown: DD07000C430400 IE: Unknown: DD07000CE7 Cell 02 - Address: 68:D1:BA:17:A2:E1 Channel:44 Frequency:5.22 GHz (Channel 44) Quality=27/70 Signal level=-83 dBm Encryption key:on ESSID:"CMCC-2wzy-5G" Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf= Extra: Last beacon: 4ms ago IE: Unknown: 000C434D43432D32777A792D3547 IE: Unknown: 01088C129824B048606C IE: Unknown: 03012C IE: Unknown: 0706555320240D14 IE: Unknown: 050400010002 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : TKIP CCMP Authentication Suites (1) : PSK IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847500 Title: Full RAM on Pi4 isn't
[Bug 1847500] Re: Full RAM on Pi4 isn't accessible when using u-boot
So let us do a comparison according to #4, maybe we could find sth different between yours and mine. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847500 Title: Full RAM on Pi4 isn't accessible when using u-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1847500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847500] Re: Full RAM on Pi4 isn't accessible when using u-boot
The uboot of armhf and configs I used for testing are:
https://github.com/agherzan/u-boot.git commit
a671dabc696fc9505641b418f473ce6c6792af93 (HEAD -> v2019.07-rpi4-wip,
origin/ag/v2019.07-rpi4-wip)
hwang4@hwang4-Vostro-5390:~/work/uboot/u-boot$ cat boot.cmd
setenv fdt_addr_r 0x0300
fdt addr ${fdt_addr_r}
fdt get value bootargs /chosen bootargs
setenv bootargs "coherent_pool=1M 8250.nr_uarts=1 cma=64M
bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1
smsc95xx.macaddr=DC:A6:32:0E:9B:C4 vc_mem.mem_base=0x3ec0
vc_mem.mem_size=0x4000 dwc_otg.fiq_fix_enable=2 console=ttyS0,115200
console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 fsck.repair=yes rootwait
rootflags=noload net.ifnames=0"
setenv kernel_addr_r 0x0100
setenv ramdisk_addr_r 0x0310
fatload mmc 0:1 ${kernel_addr_r} Image
fatload mmc 0:1 ${ramdisk_addr_r} initrd.img
setenv initrdsize $filesize
bootz ${kernel_addr_r} ${ramdisk_addr_r}:${initrdsize} ${fdt_addr_r}
hwang4@hwang4-Vostro-5390:~/work/uboot/u-boot$ cat
/media/hwang4/system-boot/config.txt
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
enable_uart=1
#kernel=Image
kernel=u-boot.bin
device_tree_address=0x0300
dtparam=i2c_arm=on
dtparam=spi=on
ramfsfile=initrd.img
ramfsaddr=0x310
#total_mem=2048
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
disable_audio_dither=on
hwang4@hwang4-Vostro-5390:~/work/uboot/u-boot$ cat
/media/hwang4/system-boot/cmdline.txt
dwc_otg.fiq_fix_enable=2 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2
rootfstype=ext4 rootwait rootflags=noload net.ifnames=0
snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1
snd_bcm2835.enable_compat_alsa=1 initrd=0x310,0x13c540b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847500
Title:
Full RAM on Pi4 isn't accessible when using u-boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1847500/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847500] Re: Full RAM on Pi4 isn't accessible when using u-boot
For WiFi, I remember I found the firmware from someplace, then the WiFi worked. ubuntu@ubuntu:~$ ls /lib/firmware/brcm/brcmfmac43455-sdio.* -la -rw-r--r-- 1 root root 600487 Sep 1 05:45 /lib/firmware/brcm/brcmfmac43455-sdio.bin -rw-r--r-- 1 root root 14036 Sep 1 05:45 /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob -rw-r--r-- 1 root root 2054 Sep 1 05:45 /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt -rw-r--r-- 1 root root 2054 Sep 1 05:45 /lib/firmware/brcm/brcmfmac43455-sdio.txt ubuntu@ubuntu:~$ ls /lib/firmware/brcm/brcmfmac43455-sdio.* | xargs md5sum 963eb0d4903040974ee88b4f85cb1f4f /lib/firmware/brcm/brcmfmac43455-sdio.bin c5aeca0e33de4ae870986c517963fef7 /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob 7b983812a8aee7bf701460436c686226 /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt 7b983812a8aee7bf701460436c686226 /lib/firmware/brcm/brcmfmac43455-sdio.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847500 Title: Full RAM on Pi4 isn't accessible when using u-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1847500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839950] Re: drm/i915: revert the patch of "set disable_power_well=0 for icl temporarily"
** Description changed: + This is for resend: + + [Impact] + We sent the patch to set disable_power_well=0, this is + because we found sometimes the hdmi audio driver printed out the timeout + errors when accessing the codec. But after the fix of #1847192 is + merged, this issue will not happen anymore, so this patch is useless now, + and it add power consumption to graphic drivers, let us revert this patch. + + + [Fix] + Revert the patch. + + [Test Case] + Tested on the new icl laptops, we have not reproduce the timeout errors, + and The PC can enter PC10. + + [Regression Risk] + Low. We have done many tests. + + ＝＝＝ [Impact] Two weeks ago, we sent the patch to set disable_power_well=0, this is because we found sometimes the hdmi audio driver printed out the timeout errors when accessing the codec. But recently the ODM told us those machines had some HW or BIOS issues, we can't reproduce the timeout errors on the new machines anymore even without this patch. And moreover we need put the CPU into PC10 power state to meet the E-star starndard, we need to revert this patch. [Fix] Revert the patch. [Test Case] Tested on the new icl laptops, we have not reproduce the timeout errors, and The PC can enter PC10. [Regression Risk] Low. We have done many tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839950 Title: drm/i915: revert the patch of "set disable_power_well=0 for icl temporarily" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1839950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
According to #11, it didn't detect the plugging on the headphone jack. please run sudo hdajacksensetest -a before headphone jack is plugged, then plug a headphone in the headphone jack, rerun the sudo hdajacksensetest -a and compare which pin is changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
Do you have normal headset which is used on most phones? Before plugging the headset to the headphone jack, please run alsa-info, then collect alsa-info.txt_before_plug, Then plug the headset to the headphone jack. run alsa-info again to generate alsa-info.txt_after_plug. upload both of them, let us see if the driver can detect your headphone plugging or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847596] Re: rpi3b+: corrupted screen on hdmi
If I don't add dtoverlay=vc4-fkms-v3d in the config.txt, the rpi4 board will have the same corrupted screen as the #1 for armhf kernel + armhf uboot. On the rpi3 B+ board, if booting with the same uboot without dtoverlay=vc4-fkms-v3d + 4.15/5.0 raspi2 kernel, the hdmi display doesn't have this issue, it proves that the eoan kernel for raspi2 introduces a new issue, will find the root cause for this new issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847596 Title: rpi3b+: corrupted screen on hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
If there is no change for any pins after plugging the headset, probably it is a hw design issue or a codec coeff setting issue, we couldn't handle it. Please test the latest mainline kernel https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.4-rc2/ If it doesn't work too. please test with windows. If windows doesn't work, probably it is a HW design issue. If windows works, please file a bug on the bugzilla of mainline kernel, maybe realtek engineer will look at this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847596] Re: rpi3b+: corrupted screen on hdmi
** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847596 Title: rpi3b+: corrupted screen on hdmi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847615] Re: After upgrading Ubuntu 19.10 sound not working
Probably you forgot to install the package of linux-modules-extra that contains kernel modules of the audio driver. >From the dmesg, there is no any audio driver loaded or trying to be loaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847615 Title: After upgrading Ubuntu 19.10 sound not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
Download linux-image-unsigned-5.4.0-050400rc2-generic_5.4.0-050400rc2.201910062030_amd64.deb Download linux-modules-5.4.0-050400rc2-generic_5.4.0-050400rc2.201910062030_amd64.deb sudo dpkg -i linux-modules-5.4.0-050400rc2-generic_5.4.0-050400rc2.201910062030_amd64.deb sudo dpkg -i linux-image-unsigned-5.4.0-050400rc2-generic_5.4.0-050400rc2.201910062030_amd64.deb reboot To uninstall the kernel 5.4 sudo dpkg -p linux-image-unsigned-5.4.0-... linux-modules-5.4.0- reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
According to #17, still can't detect the plugging event on headphone jack. So please open a bug on bugzilla for mainline kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
According to the logs in the #1, there is no obvious errors. Please open the gnome-sound-setting, then plug a headphone, does the headphone shows up in the UI after you plug the headphone. If a headphone shows up, then select that headphone from UI, and play some sound to headphone, if there is no sound from headphone, please run alsa-info and pactl list, then upload two logs to lp. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846692] Re: PCI/internal sound card not detected
If we use 5.0 generic kernel, the kernel should load the legacy hda driver because there is no sof driver in the 5.0 generic kernel. For this problem, the legacy hda driver is not loaded, maybe users forget to install linux-modules-extra- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846692 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
Did you plug the headphone to the headphone jack or lineout jack? from the log of #5, they are not plugged or the plugging is not detected (all not available). Porte: analog-output-lineout: Line-Out (priority: 9900, not available) analog-output-headphones: Cuffie analogiche (priority: 9000, not available) Porta attiva: analog-output-lineout -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847192] Re: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms
** Description changed: - [Reproduce Steps] - 1. Enter s2idle - 2. Press power button to wake up the system - 3. The Select Audio Device dialog show up + Since Bionic kernel doesn't support ICL platforms (i915), so these two + patches will not be sent to Bionic kernel. - [Results] - Expected: There is no dialog show up - Actual: The Select Audio Device dialog show up + [Impact] + On the ICL platforms, the hdmi can't work well, the audio driver + will print "azx_get_response timeout" randomly, then the whole + audio doesn't work anymore. + + [Fix] + Intel provide these two fixes to us, and we tested these two + patches, it really fixed the issue. + + [Test Case] + Boot and check the hdmi audio, then suspend and resume, check + the hdmi audio, all work well. + + [Regression Risk] + Low, Only enable the audio PIN and enable the clock for ICL. we + tested on both ICL and non-ICL, all worked well as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847192 Title: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847250] [NEW] update firmware for sound sof driver to fix the hang issue on several Dell machines
Public bug reported: 1. the issue can be duplicated after re-SWDL. 2. can enter into system when we disable audio in BIOS interface. 3. Can enter into system when we uninstall the audio driver. 4. Can enter into system when we remove Chipset driver in GCF and re- preload. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1841562 originate-from-1845415 somerville ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1845415 somerville ** Tags added: originate-from-1841562 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847250] Re: update firmware for sound sof driver to fix the hang issue on several Dell machines
** Description changed: - 1. the issue can be duplicated after re-SWDL. + We expect this firmware update could be released with 19.10 - 2. can enter into system when we disable audio in BIOS interface. + [Impact] + We have a couple of Dell machines, after installing the system, it + will hang randomly, and this issue was reported by factory, they met + this issue a couple of times. Then we tried to reproduce this issue, + finally reproduced it. - 3. Can enter into system when we uninstall the audio driver. + [Fix] + Intel debugged this issue as well, and they provided 4 kernel patches + and a new firmware, we tested them, they really can fix the issue. + And the patches were sent the SRU already, now it is time to update + firmware. - 4. Can enter into system when we remove Chipset driver in GCF and re- - preload. + [Test Case] + Install the system repeatedly and there is no hang issue anymore. + + [Regression Risk] + Low, Intel told us there is no ABI change for the firmware, so + it is safe to run this firmware both with the old driver (not applied + those 4 patches) and the new driver (applied those 4 patches). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
There is no any internal mic or external mic defined according to the init verb. Does those mics work under windows? If yes, please collect the log under windows. ** Attachment added: "RtHDDump_V226.zip" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5293871/+files/RtHDDump_V226.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836752] Re: input/mouse: alps trackpoint-only device doesn't work
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836752 Title: input/mouse: alps trackpoint-only device doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
Could you please have try with the latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3/ If that kernel doesn't work, let us have a try with replacing the current graphic driver amdgpu to the amdgpu-pro. I will update a new comment to explain how to install amdgpu-pro if the kernel v5.3 is confirmed to not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
BTW, you could manually copy the UCM and then do a test on internal mic https://github.com/alsa-project/alsa-ucm-conf/tree/import/ucm Two important folders are: https://github.com/alsa-project/alsa-ucm-conf/tree/import/ucm/sof-skl_hda_card https://github.com/alsa-project/alsa-ucm-conf/tree/import/ucm/LENOVO- 20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845678] Re: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work
@Jonathan, Don't use the oem-osp1 kernel. To make the internal mic work, we need to integrate UCM files, we are trying to submit the files to ubuntu 19.10, but not finished. After the UCM is integrated, bot 5.3 kernel and oem-osp1 kernel will work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845678 Title: Lenovo ThinkPad X1 Carbon 7th Generation built-in microphone doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842265] Re: No sound inputs from the external microphone and headset on a Dell machine
** Tags removed: verification-needed-bionic verification-needed-disco ** Tags added: verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842265 Title: No sound inputs from the external microphone and headset on a Dell machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1842265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1847500] Re: Full RAM on Pi4 isn't accessible when using u-boot
On 2019/10/11 下午10:18, Dave Jones wrote: >> For WiFi, I remember I found the firmware from someplace, then the > WiFi worked. > >> ubuntu@ubuntu:~$ ls /lib/firmware/brcm/brcmfmac43455-sdio.* -la >> -rw-r--r-- 1 root root 600487 Sep 1 05:45 >> /lib/firmware/brcm/brcmfmac43455-sdio.bin >> -rw-r--r-- 1 root root 14036 Sep 1 05:45 >> /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob >> -rw-r--r-- 1 root root 2054 Sep 1 05:45 >> /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt >> -rw-r--r-- 1 root root 2054 Sep 1 05:45 >> /lib/firmware/brcm/brcmfmac43455-sdio.txt >> ubuntu@ubuntu:~$ ls /lib/firmware/brcm/brcmfmac43455-sdio.* | xargs md5sum >> 963eb0d4903040974ee88b4f85cb1f4f /lib/firmware/brcm/brcmfmac43455-sdio.bin >> c5aeca0e33de4ae870986c517963fef7 >> /lib/firmware/brcm/brcmfmac43455-sdio.clm_blob >> 7b983812a8aee7bf701460436c686226 >> /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt >> 7b983812a8aee7bf701460436c686226 /lib/firmware/brcm/brcmfmac43455-sdio.txt > Most of those hashes match the latest-but-one variant of the wifi > firmware from Raspbian. Unfortunately, updating to the very latest is > tricky for us as the firmware blobs appear split between linux-firmware > (which holds the *.bin files) and linux-firmware-raspi (which holds the > *.txt and *.clm_blob) files. After a bit of experimentation I've found > that updating just the 43455 clm_blob and txt files fixes wifi for the > Pi4 without breaking wifi on any of the earlier versions. > > I'll open a separate ticket for this with a link to a PPA package and > see if I can get it sponsored. OK, thanks for sharing this information. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847500 Title: Full RAM on Pi4 isn't accessible when using u-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1847500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
Could you ask the Acer what is the hardware design for the internal mic on this machine? Does the internal mic connect to the realtek codec or directly connect to the DSP in the PCH? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853791] Re: External microphone can't work on some dell machines with the codec alc256 or alc236
verification done. thx. ** Tags removed: verification-needed-bionic verification-needed-disco verification-needed-eoan ** Tags added: verification-done-bionic verification-done-disco verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853791 Title: External microphone can't work on some dell machines with the codec alc256 or alc236 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
