[Kernel-packages] [Bug 2037716] Re: Core 22 is missing Realtek and TI drivers, that were previously in 20
Hey paul, this issue is about missing kernel modules, not about anything in the core22 snap ... Part of the kernel stuff is being handled already in https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2024443 though ... ** Summary changed: - Core 22 is missing Realtek and TI drivers, that were previously in 20 + Core 22 kernel is missing Realtek and TI drivers, that were previously in 20 ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037716 Title: Core 22 kernel is missing Realtek and TI drivers, that were previously in 20 Status in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Bug description: Please, do not exclude drivers previuosly included in IoT Core 20. IoT requires communication, mainly drivers. Add at least /realtek/rtl818x /realtek/rtl818x/rtl8187 /realtek/rtl8192cu /realtek/rtl8xxxu /realtek/rtlwifi /realtek/rtlwifi/rtl8188ee /realtek/rtlwifi/rtl8192c /realtek/rtlwifi/rtl8192cu and /ti/wl1251 /ti/wl12xx /ti/wl18xx /ti/wlcore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2037716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037712] [NEW] pi-kernel in UC22 missing mt7601u.ko and rtl8192cu.ko
Public bug reported: While included in UC20, the mt7601u.ko and rtl8192cu.ko seem to be missing in UC22 kernels, please move it back in place, our customers that run UC20 or tested with UC20 will expect their hardware to keep working in UC22 installs ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Summary changed: - pi-kernel in UC22 missing mt7601u.ko + pi-kernel in UC22 missing mt7601u.ko and rtl8192cu.ko ** Description changed: - While included in UC20, the mt7601u.ko seems to be missing in UC22 - kernels, please move it back in place, our customers that run UC20 or - tested with UC20 will expect their hardware to keep working in UC22 - installs + While included in UC20, the mt7601u.ko and rtl8192cu.ko seem to be + missing in UC22 kernels, please move it back in place, our customers + that run UC20 or tested with UC20 will expect their hardware to keep + working in UC22 installs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037712 Title: pi-kernel in UC22 missing mt7601u.ko and rtl8192cu.ko Status in linux-raspi package in Ubuntu: New Bug description: While included in UC20, the mt7601u.ko and rtl8192cu.ko seem to be missing in UC22 kernels, please move it back in place, our customers that run UC20 or tested with UC20 will expect their hardware to keep working in UC22 installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024443] [NEW] pi-kernel 5.15 on UC22 is missing most staging modules
Public bug reported: i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna for the RPi since i use this card in various RPi projects ... trying it on UC22 it turns out that the module driving this card is not included in the pi-kernel snap. in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna for the RPi since i use this card on various RPi projects ... - trying it on UC22 it tuns out that the module driving this card is not included in the pi-kernel snap. - in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko mpodule via the linux-modules-extra package. + trying it on UC22 it tuns out that the module driving this card is not included in the pi-kernel snap. + in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. ** Description changed: i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna - for the RPi since i use this card on various RPi projects ... + for the RPi since i use this card in various RPi projects ... - trying it on UC22 it tuns out that the module driving this card is not included in the pi-kernel snap. + trying it on UC22 it turns out that the module driving this card is not included in the pi-kernel snap. in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2024443 Title: pi-kernel 5.15 on UC22 is missing most staging modules Status in linux-raspi package in Ubuntu: New Bug description: i recently recommended a TP-Link TL-WN722N to an UbuntuCore customer asking for a recommendation of a USB wifi adapter with external antenna for the RPi since i use this card in various RPi projects ... trying it on UC22 it turns out that the module driving this card is not included in the pi-kernel snap. in fact the staging dir seems to mostly be empty ... the same kernel on classic includes the needed r8188eu.ko module via the linux-modules-extra package. it seems like we do not include linux-modules-extra in the 5.15 pi- kernel snap at all which is a regression compared to former pi-kernel snaps where this wifi card works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2024443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994126 Title: NULL pointer dereference in power_supply_get_property Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: New Bug description: Ubuntu 22.10 final release boot via usb thumb drive on thinkpad T480 (containing nvidia gpu) reproducible kernel panic during boot backtrace via OCR from picture of kernel panic: Started Periodic ext4 Online Hetadata Check for All Filesystems. Started Discard unused blocks once a week. Started Refresh fuupd metadate regularly. Started Daily rotation of log files. Started Daily man-db regeneration. Started Message of the Day. Started Daily Cleanup of Temporary Directories. Started Ubuntu Advantage Timer for running repeated jobs. Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation Socket. 1 Listening on CUPS Scheduler. 1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation for snappy deeson... Listening on UUID deemon activation socket. 1 Listening on Socket activation for snappy daemon. Reached target Socket Units. 1 Reached target Basic System. 20.300662) BUG: Kernel NULL pointer dereference, address: 20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 WPF: error code (0x0010) - not-present page 20.302458) PGD O P40 0 20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579) CPU: 4 PID: 1 Comm: systemd Tainted: P 0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 20L5000BGE/20L5000BGE, BIOS N24ET7ON (1.45) 07/22/2022 20.304190) 20.304774) RIP: 0010:0N0 20.305376) Code: Unable to access opcode bytes at RIP Oxffd6. 20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202 20.3066231 RAX: RBX: 95538288 RCX: 8c43c1d89800 20.307282) RDX: b17180087cdo RSI: 0004 RDI: 8c43c1d89800 20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09: 0 20.308627) R10: R11: R12: 00 20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15: 9553a288 20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000 20.310762) CS: 0010 DS: ES: CRO: 80050033 20.311491) CR2: fffds CRS: 00011eida002 CR4: 003706e0 20.312241) Call Trace: 20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968469] Re: ILITEK_ILI9881C panel driver missing
** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1968469 Title: ILITEK_ILI9881C panel driver missing Status in linux-raspi package in Ubuntu: Fix Released Bug description: the current 5.15.0-1004-raspi kernel for 22.04 does not enable the CONFIG_DRM_PANEL_ILITEK_ILI9881C=m option, thus such touchscreen panels can not be used the cutiepi (https://cutiepi.io/) project does use this hardware for their pi based tablets. booting ubuntu 22.04 on such a tablet is only possible with an external HDMI monitor attached at this moment. it would be nice if Ubuntu could work OOTB on this hardware. while the jammy kernel seems to already ship the required dtb overlay "cutiepi-panel.dtbo", the modules this overlay uses are not there. below is a Kconfig commit outlining the required options: https://github.com/cutiepi- io/linux/commit/de6774dca11b815e647fa08d71f3eac9009c2dff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968469] [NEW] ILITEK_ILI9881C panel driver missing
Public bug reported: the current 5.15.0-1004-raspi kernel for 22.04 does not enable the CONFIG_DRM_PANEL_ILITEK_ILI9881C=m option, thus such touchscreen panels can not be used the cutiepi (https://cutiepi.io/) project does use this hardware for their pi based tablets. booting ubuntu 22.04 on such a tablet is only possible with an external HDMI monitor attached at this moment. it would be nice if Ubuntu could work OOTB on this hardware. while the jammy kernel seems to already ship the required dtb overlay "cutiepi-panel.dtbo", the modules this overlay uses are not there. below is a Kconfig commit outlining the required options: https://github.com/cutiepi- io/linux/commit/de6774dca11b815e647fa08d71f3eac9009c2dff ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1968469 Title: ILITEK_ILI9881C panel driver missing Status in linux-raspi package in Ubuntu: New Bug description: the current 5.15.0-1004-raspi kernel for 22.04 does not enable the CONFIG_DRM_PANEL_ILITEK_ILI9881C=m option, thus such touchscreen panels can not be used the cutiepi (https://cutiepi.io/) project does use this hardware for their pi based tablets. booting ubuntu 22.04 on such a tablet is only possible with an external HDMI monitor attached at this moment. it would be nice if Ubuntu could work OOTB on this hardware. while the jammy kernel seems to already ship the required dtb overlay "cutiepi-panel.dtbo", the modules this overlay uses are not there. below is a Kconfig commit outlining the required options: https://github.com/cutiepi- io/linux/commit/de6774dca11b815e647fa08d71f3eac9009c2dff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1968469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963919] [NEW] fbtft overlay is missing
Public bug reported: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it gets extremely tricky to even enable the touchscreen input or to use such a TFT with other sensors attached since rpi-display does not allow any re-assignment of the GPIO pins in use. The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. ** Affects: linux-raspi2 (Ubuntu) Importance: Wishlist Status: New ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Wishlist ** Description changed: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it - gets extremely tricky to even enable the touchscreen or use a TFT with - other sensors attached since rpi-display does not allow any re- - assignment of the GPIO pins in use. + gets extremely tricky to even enable the touchscreen input or to use + such a TFT with other sensors attached since rpi-display does not allow + any re-assignment of the GPIO pins in use. - The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. + The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1963919 Title: fbtft overlay is missing Status in linux-raspi2 package in Ubuntu: New Bug description: To attach TFT touchscreens the pi-foundation kernel ships the fbtft devicetree overlay along with rpi-display. While you can attach a stand-alone TFT display just fine when only using rpi-display to provide the drivers with hardcoded GPIO assignments, it gets extremely tricky to even enable the touchscreen input or to use such a TFT with other sensors attached since rpi- display does not allow any re-assignment of the GPIO pins in use. The upstream fbtft driver can make use of the already included rpi-display drivers by defining "rpi-display" in its params. It also allows to freely re-assign the GPIO pins for backlight, D/C and Reset to give you enough flexibility to have the display co-exist with any attached sensors and touch input devices that do not have the ability to re-assign GPIO pins and that clash with the hardcoded numbering of rpi-display. An example with freely assigned GPIOs can be seen in the upstream (rpi-foundation) overlay README file at: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884 Please include fbtft in the ubuntu kernels to allow a more flexible usage of SPI based TFT touchscreens on the Pi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1963919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.ne
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
note that i did never really follow up with that setup in the end but i found out that even modern SSDs (not only rotary HDDs) usually draw more power than the USB3 port can provide, you will need an Y-Cable or external power supply ... while i can not fully confirm (due to lack of time and testing), i do assume it is not a kernel issue at all here, feel free to close it for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Invalid Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: Invalid Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926911] Re: hctosys not reading hardware clock on CM4
hirsute does not have Ubuntu Core images ;) It seems to be solvable via a simple defconfig change according to: https://github.com/raspberrypi/linux/issues/4205 We have at least one UC customer implementing a CM4 baseboard with TPM for Full disk encryption and secureboot in UC20, for this the clock needs to be correct. The module also needs to move into the UC initrd so it can load before mounting disks, i added an ubuntu-core-initramfs task for this ... ** Bug watch added: github.com/raspberrypi/linux/issues #4205 https://github.com/raspberrypi/linux/issues/4205 ** Also affects: ubuntu-core-initramfs Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1926911 Title: hctosys not reading hardware clock on CM4 Status in ubuntu-core-initramfs: New Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: Confirmed Bug description: There is a timing issue when using the CM4 with the official CM4 IO baseboard. The CM4 baseboard comes with a built in rtc and a battery holder by default, to enable it a devicetree overlay needs to be enabled and a matching module gets loaded ... $ tail -2 /run/mnt/ubuntu-seed/config.txt dtparam=i2c_vc=on dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi,addr=0x51 $ lsmod | grep pcf85063 rtc_pcf85063 20480 0 When booting the kernel runs hctosys about 1.5sec into the boot, the rtc module only gets loaded about 10sec later though: $ dmesg|grep rtc [1.593561] hctosys: unable to open rtc device (rtc0) [ 10.767256] rtc-pcf85063 10-0051: registered as rtc0 Looking at the systemd journal the clock does not get set at all, only a network connection actually triggers setting of the clock (note the timestamps in the journal): --- Apr 26 10:27:53 ubuntu kernel: mmc0: SDHCI controller on fe34.emmc2 [fe34.emmc2] using ADMA Apr 26 10:27:53 ubuntu kernel: hctosys: unable to open rtc device (rtc0) Apr 26 10:27:53 ubuntu kernel: of_cfs_init Apr 26 10:27:53 ubuntu kernel: of_cfs_init: OK ... Apr 26 10:28:02 CM4 systemd[1]: Started Network Name Resolution. Apr 26 10:28:02 CM4 kernel: rtc-pcf85063 10-0051: registered as rtc0 Apr 26 10:28:02 CM4 systemd-udevd[459]: Using default interface naming scheme 'v245'. ... Apr 26 10:28:08 CM4 avahi.daemon[593]: Registering new address record for 192.168.2.32 on wlan0.IPv4. Apr 26 10:28:08 CM4 systemd-timesyncd[495]: Network configuration changed, trying to establish connection. May 02 17:14:17 CM4 systemd-timesyncd[495]: Initial synchronization to time server 91.189.89.199:123 (ntp.ubu> May 02 17:14:17 CM4 systemd[1]: Starting Online ext4 Metadata Check for All Filesystems... --- I think the loading of the rtc_pcf85063 module should trigger an additional hctosys call (preferably from the module itself, but worst case a udev rule calling out to hwclock --hctosys might work too)... Just for the record, the hwclock works fine otherwise: $ sudo hwclock 2021-05-02 19:56:11.281975+00:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1926911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926911] [NEW] hctosys not reading hardware clock on CM4
Public bug reported: There is a timing issue when using the CM4 with the official CM4 IO baseboard. The CM4 baseboard comes with a built in rtc and a battery holder by default, to enable it a devicetree overlay needs to be enabled and a matching module gets loaded ... $ tail -2 /run/mnt/ubuntu-seed/config.txt dtparam=i2c_vc=on dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi,addr=0x51 $ lsmod | grep pcf85063 rtc_pcf85063 20480 0 When booting the kernel runs hctosys about 1.5sec into the boot, the rtc module only gets loaded about 10sec later though: $ dmesg|grep rtc [1.593561] hctosys: unable to open rtc device (rtc0) [ 10.767256] rtc-pcf85063 10-0051: registered as rtc0 Looking at the systemd journal the clock does not get set at all, only a network connection actually triggers setting of the clock (note the timestamps in the journal): --- Apr 26 10:27:53 ubuntu kernel: mmc0: SDHCI controller on fe34.emmc2 [fe34.emmc2] using ADMA Apr 26 10:27:53 ubuntu kernel: hctosys: unable to open rtc device (rtc0) Apr 26 10:27:53 ubuntu kernel: of_cfs_init Apr 26 10:27:53 ubuntu kernel: of_cfs_init: OK ... Apr 26 10:28:02 CM4 systemd[1]: Started Network Name Resolution. Apr 26 10:28:02 CM4 kernel: rtc-pcf85063 10-0051: registered as rtc0 Apr 26 10:28:02 CM4 systemd-udevd[459]: Using default interface naming scheme 'v245'. ... Apr 26 10:28:08 CM4 avahi.daemon[593]: Registering new address record for 192.168.2.32 on wlan0.IPv4. Apr 26 10:28:08 CM4 systemd-timesyncd[495]: Network configuration changed, trying to establish connection. May 02 17:14:17 CM4 systemd-timesyncd[495]: Initial synchronization to time server 91.189.89.199:123 (ntp.ubu> May 02 17:14:17 CM4 systemd[1]: Starting Online ext4 Metadata Check for All Filesystems... --- I think the loading of the rtc_pcf85063 module should trigger an additional hctosys call ... Just for the record, the hwclock works fine otherwise: $ sudo hwclock 2021-05-02 19:56:11.281975+00:00 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1926911 Title: hctosys not reading hardware clock on CM4 Status in linux-raspi package in Ubuntu: New Bug description: There is a timing issue when using the CM4 with the official CM4 IO baseboard. The CM4 baseboard comes with a built in rtc and a battery holder by default, to enable it a devicetree overlay needs to be enabled and a matching module gets loaded ... $ tail -2 /run/mnt/ubuntu-seed/config.txt dtparam=i2c_vc=on dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi,addr=0x51 $ lsmod | grep pcf85063 rtc_pcf85063 20480 0 When booting the kernel runs hctosys about 1.5sec into the boot, the rtc module only gets loaded about 10sec later though: $ dmesg|grep rtc [1.593561] hctosys: unable to open rtc device (rtc0) [ 10.767256] rtc-pcf85063 10-0051: registered as rtc0 Looking at the systemd journal the clock does not get set at all, only a network connection actually triggers setting of the clock (note the timestamps in the journal): --- Apr 26 10:27:53 ubuntu kernel: mmc0: SDHCI controller on fe34.emmc2 [fe34.emmc2] using ADMA Apr 26 10:27:53 ubuntu kernel: hctosys: unable to open rtc device (rtc0) Apr 26 10:27:53 ubuntu kernel: of_cfs_init Apr 26 10:27:53 ubuntu kernel: of_cfs_init: OK ... Apr 26 10:28:02 CM4 systemd[1]: Started Network Name Resolution. Apr 26 10:28:02 CM4 kernel: rtc-pcf85063 10-0051: registered as rtc0 Apr 26 10:28:02 CM4 systemd-udevd[459]: Using default interface naming scheme 'v245'. ... Apr 26 10:28:08 CM4 avahi.daemon[593]: Registering new address record for 192.168.2.32 on wlan0.IPv4. Apr 26 10:28:08 CM4 systemd-timesyncd[495]: Network configuration changed, trying to establish connection. May 02 17:14:17 CM4 systemd-timesyncd[495]: Initial synchronization to time server 91.189.89.199:123 (ntp.ubu> May 02 17:14:17 CM4 systemd[1]: Starting Online ext4 Metadata Check for All Filesystems... --- I think the loading of the rtc_pcf85063 module should trigger an additional hctosys call ... Just for the record, the hwclock works fine otherwise: $ sudo hwclock 2021-05-02 19:56:11.281975+00:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1926911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914919] [NEW] UC20 initrd misses modules to boot from USB disk
Public bug reported: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing console output it simply hangs indefinitely with a black screen https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen). + console output it simply hangs indefinitely with a black screen + LP#1914608 ). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen - LP#1914608 ). + console output it simply hangs indefinitely with a black screen #1914608 + ). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. ** Description changed: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing - console output it simply hangs indefinitely with a black screen #1914608 - ). + console output it simply hangs indefinitely with a black screen + https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914919 Title: UC20 initrd misses modules to boot from USB disk Status in linux-raspi package in Ubuntu: New Bug description: Trying to use a default USB boot on a Raspberry Pi using either an USB3 UAS SSD enclosure or even a simple USB 2 stick fails (due to the missing console output it simply hangs indefinitely with a black screen https://bugs.launchpad.net/ubuntu/+source/linux- raspi/+bug/1914608). seemingly neither the usb_storage module nor uas, enclosure or required scsi drivers are included in the initrd, this makes using the UC20 images with a fast USB3 disk impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1914919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914608] [NEW] no console during boot on UC20
Public bug reported: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: Confirmed ** Description changed: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. - this is also required to bring any kind of bootsplash back to UC20 with + this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1914608 Title: no console during boot on UC20 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: New Status in linux-raspi source package in Groovy: New Status in linux-raspi source package in Hirsute: Confirmed Bug description: when booting UC20 on a Pi4 the screen backlight is completely off and no signal is produced. inspecting the boot a little closer it seems the necessary modules for bringing up the vc4 framebuffer are not included in the initramfs on ubuntu core. once they get loaded (after boot) the backlight and signal turn on. The initrd should include the modules and load them during boot. this is also required to bring any kind of bootsplash back to UC20 which is a reason all our digital signage customers currently hold back on going forward to UC20. the modules required are: ogra@ubuntu:~$ lsmod|grep vc4 vc4 290816 3 drm_kms_helper225280 3 vc4 snd_soc_core 262144 1 vc4 snd_pcm 143360 5 vc4,snd_bcm2835,snd_soc_core,snd_pcm_dmaengine drm 565248 7 gpu_sched,drm_kms_helper,v3d,vc4 the loading during boot in the journal is shown below: ogra@ubuntu:~$ sudo journalctl -b | grep vc4 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) Apr 01 17:23:45 ubuntu kernel: fb0: switching to vc4drmfb from simple Apr 01 17:23:45 ubuntu kernel: [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 Apr 01 17:23:45 ubuntu kernel: vc4-drm gpu: fb0: vc4drmfb frame buffer device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-rasp
[Kernel-packages] [Bug 1911943] [NEW] pi-kernel snap: broadcom bluetooth firmware missing from 5.4.0-1027.30
Public bug reported: supposedly the bluetooth firmware from: https://launchpad.net/ubuntu/+source/linux-firmware- raspi2/3-0ubuntu1~20.04.1 should be shipped in the latest pi-kernel snap in the edge/beta channel. the BCM4345C5.hcd (as mentioned in the last changelog entry above) is essential for proper bluetooth audio playback over A2DP. the linux-firmware-raspi2 package from -proposed does not seem to be included in pi-kernel 20/edge as it should. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1911943 Title: pi-kernel snap: broadcom bluetooth firmware missing from 5.4.0-1027.30 Status in linux-raspi package in Ubuntu: New Bug description: supposedly the bluetooth firmware from: https://launchpad.net/ubuntu/+source/linux-firmware- raspi2/3-0ubuntu1~20.04.1 should be shipped in the latest pi-kernel snap in the edge/beta channel. the BCM4345C5.hcd (as mentioned in the last changelog entry above) is essential for proper bluetooth audio playback over A2DP. the linux-firmware-raspi2 package from -proposed does not seem to be included in pi-kernel 20/edge as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1911943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
so this is indeed not an issue with the modules but with the kernel itself and the support for sas, uas or the enclosure services. i test-built all tags from https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux-raspi/+git/focal/refs/tags from 1023.26 going backwards and found that it reliably works until Ubuntu- raspi-5.4.0-1013.13 and reliably hangs with Ubuntu-raspi-5.4.0-1014.14 so somewhere between these two tags the breakage was introduced ... i have now also tried to boot either of the 20.10 images (desktop, server, UC18) and they all expose the same behavior -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905272] Re: Can't get h/w video acceleration on rpi4
the config option seems to be: CONFIG_VIDEO_CODEC_BCM2835=m ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1905272 Title: Can't get h/w video acceleration on rpi4 Status in snapd: New Status in linux-raspi package in Ubuntu: New Bug description: Hi, we've run into an issue where we can't get h/w video acceleration working on rpi4 on ubuntu core 18 (and 20). Our snap is using the following stack: Qt 5 eglfs + gstreamer + mesa. Raspberry's config txt has: dt_overlay=vc4-fkms-v3d, gpu_mem=256. I've enabled all video/opengl related interfaces: - opengl - hardware-observe - framebuffer. Gstreamer can't detect that it has support for h264 h/w decoding using v4l2 plugin. The very same snap unpacked on the raspbian and that is running in a pretty same way it is on the core immediately detects that h264 decoding is available (i.e. I unsquashfs it there, set the LD_LIBRARY_PATH, WEBGL_DRIVERS_PATH, and all other environment variables that are returned from `env` command when running snap run --shell my_snap). Because of that Qt falls back to the GStreamer pipeline with s/w decoder (avdec) and outputs like 0.5 frames per second (I am not sure if OpenGL actually works with h/w acceleration because even then it's so slow). Running on core 20 did not help - I tried running it in devmode as well without any differences. Raspbian, where it works, has 5.5 version of Linux kernel, I did try the beta version of core 20 which had 5.4 kernel version but it made no difference. lsmod on raspbian shows some extra modules related to vc4 not present on the core (not sure how relevant they are though): - v4l2_mem2mem - bcm2835_codec To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1905272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
i'll try over the weekend ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
in fact it seems like in 5.3 USB is not working at all !!! i verified that today ... my self-built kernel uses the focal 5.4 branch where USB works fine then: https://github.com/ogra1/linux-raspberrypi- org/blob/master/snap/snapcraft.yaml -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
also note that the fabrica appliance you linked uses a re-built kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
hmm, i wonder why they dont load then ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Xenial: New Status in linux-raspi2 source package in Bionic: Invalid Status in linux-raspi source package in Focal: New Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881631] Re: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII
this is definitely a regression, mounting partitions should work ... marking as critical. ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881631 Title: arm64 Ubuntu kernel builds missing CONFIG_NLS_ASCII Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options. This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing. Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error. The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Description changed: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the - initrd as modules ? + core initrd as modules ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] Re: USB support missing in initrd makes booting core with writable on USB impossible
** Description changed: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) - adding the following to a re-built kernel makes everything work + adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the core initrd as modules ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881623] [NEW] USB support missing in initrd makes booting core with writable on USB impossible
Public bug reported: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Confirmed ** Description changed: when using a gadget.yaml like: volumes: - pi4-system-boot: - schema: mbr - bootloader: u-boot - structure: - - type: 0C - filesystem: vfat - filesystem-label: system-boot - size: 512M - content: - - source: boot-assets/ - target: / - pi4-usb-writable: - schema: mbr - structure: - - name: writable - type: 83 - filesystem: ext4 - filesystem-label: writable - size: 650M - role: system-data + pi4-system-boot: + schema: mbr + bootloader: u-boot + structure: + - type: 0C + filesystem: vfat + filesystem-label: system-boot + size: 512M + content: + - source: boot-assets/ + target: / + pi4-usb-writable: + schema: mbr + structure: + - name: writable + type: 83 + filesystem: ext4 + filesystem-label: writable + size: 650M + role: system-data - - this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... + this creates two separate img files for a Pi image ... one for SD to + hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - - CONFIG_ENCLOSURE_SERVICES=y - - CONFIG_SCSI_SAS_ATTRS=y - - CONFIG_USB_STORAGE=y - - CONFIG_USB_UAS=y + - CONFIG_ENCLOSURE_SERVICES=y + - CONFIG_SCSI_SAS_ATTRS=y + - CONFIG_USB_STORAGE=y + - CONFIG_USB_UAS=y - can we please have these aither built into the kernel or added to the + can we please have these either built into the kernel or added to the initrd as modules ? ** Summary changed: - USB support missing in initrd makes booting with writable on USB impossible + USB support missing in initrd makes booting core with writable on USB impossible -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1881623 Title: USB support missing in initrd makes booting core with writable on USB impossible Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: when using a gadget.yaml like: volumes: pi4-system-boot: schema: mbr bootloader: u-boot structure: - type: 0C filesystem: vfat filesystem-label: system-boot size: 512M content: - source: boot-assets/ target: / pi4-usb-writable: schema: mbr structure: - name: writable type: 83 filesystem: ext4 filesystem-label: writable size: 650M role: system-data this creates two separate img files for a Pi image ... one for SD to hold the boot files, one for USB that carries the rootfs ... sadly our kernel will then not find the writable partition because it lacks support for usb disks (usb-storage seems to be there but not sufficient) adding the following to a re-built kernel snap makes everything work (verified with USB 3.1 SSD on a pi4 as well as various USB 3.0 keys) - CONFIG_ENCLOSURE_SERVICES=y - CONFIG_SCSI_SAS_ATTRS=y - CONFIG_USB_STORAGE=y - CONFIG_USB_UAS=y can we please have these either built into the kernel or added to the initrd as modules ? To manage notifications abou
[Kernel-packages] [Bug 1876862] Re: Missing v3d driver disables 3D support on RPi4
adding bionic since we're supposed to fully support the pi4 there too ** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1876862 Title: Missing v3d driver disables 3D support on RPi4 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Bionic: New Status in linux-raspi source package in Focal: Confirmed Bug description: Our raspberry pi kernel builds don't include the v3d drm driver (The relevant diff between the raspbian kernel config and ours) -CONFIG_DRM_V3D=m +# CONFIG_DRM_V3D is not set This means 3D acceleration is unavailable on our Pi 4 images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
the included snapcraft.yaml means i need to have the whole tree locally on disk, as someone who maintains a ton of community images for UbuntuCore i prefer to just have the snapcraft.yaml locally so the disk is only cluttered during build. along with that i am trying to build the eoan tree for the core18 Pi4 image i provide, the wlan firmware is not in the linux-firmware package in bionic, so i need overrides ... beyond this, a lot of config options that i require to be builtin are modules and the initramfs handling in snapcraft is still a mess, so i prefer to build in MMC support and USB disk support... along with this we have a good bunch of customers building custom kernels with out-of-tree snapcraft file and brand stores so it helps to know what they experience. :) note that once we have an official core image for the Pi4 i'll drop this work anyway ... closing the bug as invalid ... ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Invalid Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
well, as a user/customer building my own kernel i'd kind of expect the defconfig for a flavour to not be a debug config. but indeed you are correct, i should have taken a look at the included snapcraft.yaml which, despite being for the wrong flavour (generic/pc- kernel), indeed contains CONFIG_DEBUG_INFO=n as a defconfig override ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
ok, this looks a bit more reasonable now ... $ ls -lh pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap -rw-r--r-- 1 ogra ogra 211M Nov 4 17:05 pi4-kernel_raspi2-5.3.0-1011.12_armhf.snap so CONFIG_DEBUG_INFO=y should better be turned off by default for people building snaps from our trees ;) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
yup, seems this is (surprisingly) on by default ... $ grep DEBUG_INFO parts/kernel/build/.config CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_INFO_REDUCED is not set # CONFIG_DEBUG_INFO_SPLIT is not set CONFIG_DEBUG_INFO_DWARF4=y # CONFIG_DEBUG_INFO_BTF is not set i'll try a re-build and override that option from snapcraft.yaml ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
i also tried using the "source-branch: raspi2" argument in the snapcraft.yaml instead of using teh master branch and the "source-tag:" option, but this results in the same big size ... additionally i'd like to remark that due to the transactional nature of UbuntuCore we need to keep the kernel three times on the device for the automatic rollback feature ... the current size would mean 2.1GB for compressed kernels alone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851233] [NEW] building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
Public bug reported: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M/mnt/System.map-5.3.1+ 211K/mnt/config-5.3.1+ 906K/mnt/dtbs 475M/mnt/firmware 4.5M/mnt/initrd-5.3.1+.img 7.0M/mnt/kernel.img 512 /mnt/meta 1.6G/mnt/modules 2.1Gtotal $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Incomplete Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837209] Re: Splash screen fails to display on recent pi core18 images
mir-kiosk is currently the only supported way to get grahical (mostly kiosk) applications up and running on ubuntu core, some of our digital- signage customers use it so currently the overlay is a requirement (until the mir team solves it with a pi specific mir backend or the vc4 driver changes in some way like stated abov) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837209 Title: Splash screen fails to display on recent pi core18 images Status in Snappy: New Status in linux-raspi2 package in Ubuntu: New Bug description: The current core18 image [1] for the raspberry pi fails to display the "Core" splash screen on boot. This is because psplash fails to open the /dev/fb0 framebuffer device, because it doesn't exist. This appears to be due to a lack of supporting kernel modules in the initrd.img (fb_sys_fops, drm, vc4, etc.) which were formerly present but are missing from the version I'm testing (pi-kernel 4.15.0-1041.44, snap rev 42). Steps to reproduce: * Flash the image to a uSD card and boot the pi with it (preferably with a serial console attached). * Note screen remains black instead of displaying the familiar "Core" text under an Ubuntu logo. * If serial console is attached, note "Error opening /dev/fb0" in the output shortly after u-boot starts the kernel; this is output from psplash failing [1] http://cdimage.ubuntu.com/ubuntu-core/18/current/ubuntu- core-18-armhf+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1837209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837209] Re: Splash screen fails to display on recent pi core18 images
the overlay is needed for mir-kiosk to allow it to work at all (unaccelerated though) to have mir-kiosk fully accelerated one needs to use -kms-v3d instead but this in turn disables all video decoding in the vc4 core. i originally picked -fkms-v3d for the gadget since it is the least evil (makes mir semi-work while still allowing to use omxplayer accelerated (see the omxplayer-pi snap for testing)). long term it would be really cool if the graphics overlay selection could be a bit more dynamic (this is indeed orthogonal to this bug though) without the need to hardcode such stuff on boot or if mir-kiosk could simply work on top of vc4 without need for the overlay (the mir team was looking into that but i do not know the current status). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837209 Title: Splash screen fails to display on recent pi core18 images Status in Snappy: New Status in linux-raspi2 package in Ubuntu: New Bug description: The current core18 image [1] for the raspberry pi fails to display the "Core" splash screen on boot. This is because psplash fails to open the /dev/fb0 framebuffer device, because it doesn't exist. This appears to be due to a lack of supporting kernel modules in the initrd.img (fb_sys_fops, drm, vc4, etc.) which were formerly present but are missing from the version I'm testing (pi-kernel 4.15.0-1041.44, snap rev 42). Steps to reproduce: * Flash the image to a uSD card and boot the pi with it (preferably with a serial console attached). * Note screen remains black instead of displaying the familiar "Core" text under an Ubuntu logo. * If serial console is attached, note "Error opening /dev/fb0" in the output shortly after u-boot starts the kernel; this is output from psplash failing [1] http://cdimage.ubuntu.com/ubuntu-core/18/current/ubuntu- core-18-armhf+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1837209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
just as a followup ... better ignore my comment above ... KVM is indeed not KMS ... sorry for causing confusion here -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834039] [NEW] loading bcm2835-v4l2 causes kernel oops with 4.4 kernel
Public bug reported: attaching a raspberry pi camera to the pi camera interface (CSI) works fine when capturing video, pictures and streams directly through the picamera python library. when trying to use software that relies on using /dev/videoX with a camera attached to the CSI interface, the bcm2835-v4l2 module needs to be loaded. loading this module results in an oops like: https://paste.ubuntu.com/p/xB8JcJXGx9/ ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Assignee: Paolo Pisati (p-pisati) Status: New ** Description changed: - attaching a raspeberry pi camera to the pi camera interface (CSI) works + attaching a raspberry pi camera to the pi camera interface (CSI) works fine when capturing video, pictures and streams directly through the picamera python library. when trying to use software that relies on using /dev/videoX with a camera attached to the CSI interface, the bcm2835-v4l2 module needs to be loaded. loading this module results in an oops like: https://paste.ubuntu.com/p/xB8JcJXGx9/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1834039 Title: loading bcm2835-v4l2 causes kernel oops with 4.4 kernel Status in linux-raspi2 package in Ubuntu: New Bug description: attaching a raspberry pi camera to the pi camera interface (CSI) works fine when capturing video, pictures and streams directly through the picamera python library. when trying to use software that relies on using /dev/videoX with a camera attached to the CSI interface, the bcm2835-v4l2 module needs to be loaded. loading this module results in an oops like: https://paste.ubuntu.com/p/xB8JcJXGx9/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1834039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
enabling CONFIG_KVM instead of enabling KVM via the dtb overlay will hard-disable all video acceleration of the upstream proprietary driver of the pi and make it completely unusable for any kind of setup that uses any upstram acceleration features from the raspberry pi foundation (i.e. via /opt/vc4 libs). the proper way to enable KVM support on any pi is to set: dtoverlay=vc4-kms-v3d in the config.txt file of the bootloader, the kernel is specifically set up for this via the included raspberry pi foundation patches. this might be pointless on arm64 which is not supported at all upstream by the raspberry pi foundation (beyond offering completely unsupported 64bit binaries for for developer tinkering) and thus does not offer any video acceleration via the proprietary driver anyway on this architecture. but enabling CONFIG_KVM hardcoded in the kernel config for armhf will be fatal, please make sure this does not happen so users can still use vc4 accelerated video playback by manipulating the upstream-documented dtoverlay values on armhf builds. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen
@gerald: right, there is no way to protect you from turning the device into a brick if this step goes wrong (unlike kernel or rootfs we can not roll back the bootloader) note that the gadget snap from edge will not have a working dtb for the old kernel which will likely make you end up with an unbootable device. sadly on the pi the dtb gets loaded by the binary blob which is why we can not just use it from the kernel snap (which would fix this problem). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen
@anthony ... technically that would be me ... practically the gadget will never update the firmware files (the firmware files as well as the dtb are usually in a dead-lock with the kernel version) i'm waiting for a solution for this from the core team before we can move on ... your best bet is to use edge based images (kernel and gadget) for the moment. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen
@ying-chun the kernel snap only upgrades the kerne, modules and files in /lib/firmware ... the gadget snap only updates the gadget.yaml, snap.yaml and files not in /boot (i.e. it excludes all bootloader bits by default). until there is a solution for potential unbootable systems this will not change i fear. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen
https://github.com/snapcore/pi3-gadget/commit/8b88f06ab5681d0ff41704a7813665a0203cbafc for reference -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1647936] Re: Raspberry Pi 3: a small rainbow square on the top right of screen
the gadget snap in edge has this fix since a while already, it just did not make it into a stable image yet. ** Changed in: snappy Status: New => Fix Committed ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1647936 Title: Raspberry Pi 3: a small rainbow square on the top right of screen Status in Snappy: Fix Committed Status in linux package in Ubuntu: Invalid Bug description: I'm working on the WD/nextcloud project, and found this issue Download the UC16 for Raspberry Pi 3 from http://releases.ubuntu.com/ubuntu-core/16/ubuntu-core-16-pi3.img.xz unxz , dd the image to sd card and boot up the system. There is a small rainbow square on top right of HDMI monitor. From RPI forum: https://www.raspberrypi.org/forums/viewtopic.php?t=82373 If the voltage is under 4.65V, firmware displays a rainbow square on top right of screen and power LED goes off. But for UC16 the rainbow square is always there even the voltage is sufficient, but the power LED works properly. So I also check 1. Ubuntu server for RPI3 from here: https://wiki.ubuntu.com/ARM/RaspberryPi This RPI3 image works properly (if the voltage is not sufficient, rainbow square shows on the top right of screen, if it's sufficient, no rainbow square shows up) 2. Rasbian (jessie lite): https://downloads.raspberrypi.org/raspbian_lite_latest This works properly too, and the official Rasbian was released with the latest firmware, so the rainbow square changes to a lighting icon It looks the firmware might be old in UC16? so the under-voltage warning doesn't display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655411] Re: Cannot enable VC4 graphics driver on RPi 3
ogra@pi3:~$ cd /boot/uboot/ ogra@pi3:~$ sudo tar xvf pi2-kernel_22.snap/dtbs/overlays.tgz then adding "dtoverlay=vc4-kms-v3d" and creating /etc/modules- load.d/vc4.conf with just "vc4" in it seems to get me vc4 loaded and i get: [4.952421] vc-cma: Videocore CMA driver [4.956535] vc-cma: vc_cma_base = 0x [4.961451] vc-cma: vc_cma_size = 0x (0 MiB) [4.967083] vc-cma: vc_cma_initial = 0x (0 MiB) [4.972972] vc-mem: phys_addr:0x mem_base=0x3dc0 mem_size:0x3f00(1008 MiB) ... [6.036262] vc-sm: Videocore shared memory driver [6.036269] [vc_sm_connected_init]: start [6.036676] [vc_sm_connected_init]: end - returning 0 ... [ 10.229614] [drm] Initialized drm 1.1.0 20060810 i assume we also need to set gpu_mem in config.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655411 Title: Cannot enable VC4 graphics driver on RPi 3 Status in linux package in Ubuntu: Incomplete Bug description: It seems the VC4 device tree overlay is not applied by the Rpi firmware. I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding .../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader does not apply the overlay at all. I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility compiled by pulling pieces from (https://github.com/raspberrypi/userland and https://github.com/dgibson/dtc) The result is here: https://github.com/albaguirre/dtmerge With this new device tree binary blob, The VC4 driver (as a module) loads (and you can see /dev/dri/ entries) I also played around with the tip of u-boot tree (git://git.denx.de/u-boot.git) which has support to apply device tree overlays - it applied fine and VC4 is at least recognized but the driver cannot initialize properly. Any idea on what magic incantation is needed for the RPi loaders (start.elf etc) to apply the vc4 overlay? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1655411] Re: Cannot enable VC4 graphics driver on RPi 3
where exactly did you add the overlays in the first paragraph ? only overlays in /boot/uboot/overlays are read by the proprietary bootloader (you need to create the dir) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1655411 Title: Cannot enable VC4 graphics driver on RPi 3 Status in linux package in Ubuntu: Incomplete Bug description: It seems the VC4 device tree overlay is not applied by the Rpi firmware. I tried adding dtoverlay=vc4-kms-v3d and adding a corresponding .../overlays/vc4-kms-v3d.dtbo file but it seems the Rpi bootloader does not apply the overlay at all. I merged vc4-kms-v3d.dtbo into bcm2710-rpi-3-b.dtb using a dtmerge utility compiled by pulling pieces from (https://github.com/raspberrypi/userland and https://github.com/dgibson/dtc) The result is here: https://github.com/albaguirre/dtmerge With this new device tree binary blob, The VC4 driver (as a module) loads (and you can see /dev/dri/ entries) I also played around with the tip of u-boot tree (git://git.denx.de/u-boot.git) which has support to apply device tree overlays - it applied fine and VC4 is at least recognized but the driver cannot initialize properly. Any idea on what magic incantation is needed for the RPi loaders (start.elf etc) to apply the vc4 overlay? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
@markus: not sure, i dont know how the non snappy images set the MAC, technically if they use similar uboot scripts the MAC should come from the first dtb snippet that is read from the ROM/closed bootloader, that part should not be related to the actual dtb address at all... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 Status in flash-kernel package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Hello, I've been running Raspberry Pi 3 with Ubuntu as described here https://wiki.ubuntu.com/ARM/RaspberryPi I've installed Ubuntu 16.04 and then upgraded to 16.10 and have been using this setup successfully since October up until last week. Unfortunately one of the latest kernel updates broke the installation and I found out the same happened for Ubuntu 16.04 LTS - and therefore I can no longer run up-to-date Ubuntu installation (with updated kernel) on my RPI. I am getting this error: Error image is not a fdt - must reset the board to recover I also tried this but it didn't help me: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=168838 Now I know running Ubuntu on RPI3 this way is not officially supported, but since Ubuntu Snappy is supported I thought someone here could know what is going on. Thank you very much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652504] Re: Recent updates broke Ubuntu on Raspberry Pi 3
the newer firmware (start.elf,fixup.dat and bootcode.bin) hard-requires 0x0200 because it initializes the hardware differently in the newer version... looks like linux-firmware-raspi2 was not properly updated alongside with flash-kernel and the kernel itself, there is a hard lockstep between these three packages, it will only work if all of them are upgraded together ... perhaps the linux-raspi2 metapackage should introduce a versioned dependency for the two others to avoid such fallout in the future ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652504 Title: Recent updates broke Ubuntu on Raspberry Pi 3 Status in flash-kernel package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Hello, I've been running Raspberry Pi 3 with Ubuntu as described here https://wiki.ubuntu.com/ARM/RaspberryPi I've installed Ubuntu 16.04 and then upgraded to 16.10 and have been using this setup successfully since October up until last week. Unfortunately one of the latest kernel updates broke the installation and I found out the same happened for Ubuntu 16.04 LTS - and therefore I can no longer run up-to-date Ubuntu installation (with updated kernel) on my RPI. I am getting this error: Error image is not a fdt - must reset the board to recover I also tried this but it didn't help me: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=168838 Now I know running Ubuntu on RPI3 this way is not officially supported, but since Ubuntu Snappy is supported I thought someone here could know what is going on. Thank you very much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1652504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625177] Re: OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625177 Title: OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU: Problem: during installation, before configuring the network interfaces, netconf puts down all the network links and cpsw gets suspended - later on the PM code kicks and tries to access the suspended hardware generating an oops Fix: apply the patches present in: git://git.launchpad.net/~p-pisati/ubuntu/+source/linux x-master_lp1625177 and recompile. How to reproduce: try to install an ubuntu-core image using the above patched kernel trying to assemble a new series 16 ubuntu core image for the beaglebone black i am constantly running into an OOPS on first boot. seemingly related to the NIC driver since the NIC does not work after the OOPS. syslog can be found at http://paste.ubuntu.com/23202737/ a test image exposing the bug can be found at: http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
oh, do you ship mesa in the mir server snap ? i didnt think that would be possible -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1Io3pQvzyBQIpZi2n_hfseNsVOo4LH-BjtNhmdWNijEc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625805] Re: arm64 kernel panic for l2 mmu with unity8 session snap
i assume this is running a snap on a classic image, not on an ubuntu core one ? (since we have no EGL support in teh core image yet) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625805 Title: arm64 kernel panic for l2 mmu with unity8 session snap Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: we are running the unity8 session snap on amd64 without any problems. to setup and reproduce the problem follow the "on Dragonboard" section of https://docs.google.com/document/d/1Io3pQvzyBQIpZi2n_hfseNsVOo4LH-BjtNhmdWNijEc You can also find the panic signature at line 3276 of the attached syslog. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1625805/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625177] Re: OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial
the log is in the pastebin mentioned in the description ... ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625177 Title: OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial Status in linux package in Ubuntu: Confirmed Bug description: trying to assemble a new series 16 ubuntu core image for the beaglebone black i am constantly running into an OOPS on first boot. seemingly related to the NIC driver since the NIC does not work after the OOPS. syslog can be found at http://paste.ubuntu.com/23202737/ a test image exposing the bug can be found at: http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1625177] [NEW] OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial
Public bug reported: trying to assemble a new series 16 ubuntu core image for the beaglebone black i am constantly running into an OOPS on first boot. seemingly related to the NIC driver since the NIC does not work after the OOPS. syslog can be found at http://paste.ubuntu.com/23202737/ a test image exposing the bug can be found at: http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1625177 Title: OOPS on beaglebone on boot of 4.4.0-36-generic under snappy ubuntu core xenial Status in linux package in Ubuntu: Incomplete Bug description: trying to assemble a new series 16 ubuntu core image for the beaglebone black i am constantly running into an OOPS on first boot. seemingly related to the NIC driver since the NIC does not work after the OOPS. syslog can be found at http://paste.ubuntu.com/23202737/ a test image exposing the bug can be found at: http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593134] Re: build squashfs into xenial kernels by default
snapd is seeded in everything but powerpc. images will only be created for i386, amd64, armhf and arm64. we do build generic and module-less initrds at rootfs build time that require hackery to be re-packed when you build a kernel snap, this is what we would like to avoid ... (one expectation is to not have the initrd exceed 2MB) despite the initrd, if snapd is seeded you have it installed and have a requirement for squashfs with the first use of it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593134 Title: build squashfs into xenial kernels by default Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: In Progress Bug description: snapd is seeded in all images in xenial by default and snaps are squashfs files. the snappy images need squashfs available at boot time and use official kernels. currently squashfs is the only module that forces us to re-pack initrds to add it everywhere for snappy images, in that light it would be really helpful to have squashfs built into the kernel instead of it being a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1593134] [NEW] build squashfs into xenial kernels by default
Public bug reported: snapd is seeded in all images in xenial by default and snaps are squashfs files. the snappy images need squashfs available at boot time and use official kernels. currently squashfs is the only module that forces us to re-pack initrds to add it everywhere for snappy images, in that light it would be really helpful to have squashfs built into the kernel instead of it being a module. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1593134 Title: build squashfs into xenial kernels by default Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: snapd is seeded in all images in xenial by default and snaps are squashfs files. the snappy images need squashfs available at boot time and use official kernels. currently squashfs is the only module that forces us to re-pack initrds to add it everywhere for snappy images, in that light it would be really helpful to have squashfs built into the kernel instead of it being a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1552371] Re: Unexpected display on
On the MX4 specifically there is also the issue with the "home" button staying active for about 30sec when the display was turned off, when shoving the phone into your pocket it is easy to create a button press event if you do not wait long enough. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in Mir: New Status in Unity System Compositor: New Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1551747] Re: ubuntu-fan causes issues during network configuration
this looks like wlan0 was brought up just fine seems to mostly be a cosmetic issue that /etc/network/if-up.d/ubuntu-fan doesnt exit quietly -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1551747 Title: ubuntu-fan causes issues during network configuration Status in Snappy: Confirmed Status in ubuntu-fan package in Ubuntu: Confirmed Bug description: it seems that ubuntu-fan is causing issues with network configuration. On 16.04 daily image: root@localhost:~# snappy list NameDate Version Developer canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-02-22 16.04.0-10.armhf canonical I see this when I'm activating a wifi card on a raspberry pi 2. root@localhost:~# ifdown wlan0 ifdown: interface wlan0 not configured root@localhost:~# ifup wlan0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/c4:e9:84:17:31:9b Sending on LPF/wlan0/c4:e9:84:17:31:9b Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e) DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e) DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 (xid=0x5ec9c081) DHCPOFFER of 192.168.0.170 from 192.168.0.251 DHCPACK of 192.168.0.170 from 192.168.0.251 RTNETLINK answers: File exists bound to 192.168.0.170 -- renewal in 17145 seconds. run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 Failed to bring up wlan0. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1551747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1491094] Re: wifi USB dongle fails to work
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - wifi USB dongle fails to work + wifi USB dongle fails to work with musb-hdrc error -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1491094 Title: wifi USB dongle fails to work with musb-hdrc error Status in Snappy: New Status in linux package in Ubuntu: New Bug description: Sep 1 19:03:26 localhost kernel: [ 193.893355] musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_bcon (89, https://bugs.launchpad.net/snappy/+bug/1491094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460399] Re: ivybridge system gets completely unusable after upgrade to vivid thanks to defaulting to immature intel_pstate driver
oops, totally forgot this is still open, the problem turned out to be a completely stuck fan wrapped in filth ... cleaning it ave the system proper values so thermald does the right thing now. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Vivid) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460399 Title: ivybridge system gets completely unusable after upgrade to vivid thanks to defaulting to immature intel_pstate driver Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Invalid Bug description: I finally got around to upgrade my work laptop (first gen dell XPS sputnik system (ivy bridge)) yesterday, to find myself with a completely unusable and sluggish desktop, constantly spinning CPU fans and a hot enough laptop case that you can burn your fingers after the first reboot after install ... the device didn't stay on for more than 10-15min in a row before the BIOS temperature monitor initiated emergency shutdowns. i also noticed a constant load average above 30.00 in htop after a few hours of researching i found that we apparently switched to the intel_pstate driver by default in vivid ... running a very simple script like: while true; do clear cat /proc/cpuinfo |grep MHz sleep 1 done ...revealed that the cores unconditionally switch to something like 133MHz even though there is currently a lot going on in the system (firefox trying to recover 150 tabs after boot, evolution syncing with an IMAP server etc). it looks to me like the intel_pstate driver (at least on ivybridge hardware) is far from being ready for end users and if i wouldn't have known how to do a detailed research on these issues i would most likely have switched to another distro or to a different known working ubuntu release. could we turn this default back to the ondemand cpufreq governor in an SRU until the driver has matured enough, so we do not lose our ivybridge users and do not generate bad press ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ogra 2120 F pulseaudio CurrentDesktop: Unity Date: Sun May 31 11:53:35 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 HibernationDevice: RESUME=UUID=145593f3-8085-4308-99b1-e1ff9c80f273 InstallationDate: Installed on 2013-11-05 (572 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. XPS L322X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=d0a6e4d2-9705-4ce3-97be-8ec33e06f2cb ro quiet splash intel_pstate=disable crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to vivid on 2015-05-30 (0 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460399] Re: ivybridge system gets completely unusable after upgrade to vivid thanks to defaulting to immature intel_pstate driver
one thing i noticed is that after dropping intel_pstate=disable from teh kernel commandline, thermald does not seem to star/run at all .. starting it manually i captured http://paste.ubuntu.com/11541063/ note that the behavior gets minimally better with thermald running, but switching workspaces is still as slow as about 20-30 sec in slow motion ... http://imgur.com/Ukuv34t shows one terminal with the script above and one terminal with htop running ... this is with thermald active ... the CPU normally switches between 800MHz and 2.8GHz with the ondemand governor in use ... with thermald i se it between 133MHz and at very short spikes up to 3.5GHz (but even when the cores run at that sped the system only gets responsive for a few seconds) turning intel_pstate back off gets me a relatively usable system back ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460399 Title: ivybridge system gets completely unusable after upgrade to vivid thanks to defaulting to immature intel_pstate driver Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Bug description: I finally got around to upgrade my work laptop (first gen dell XPS sputnik system (ivy bridge)) yesterday, to find myself with a completely unusable and sluggish desktop, constantly spinning CPU fans and a hot enough laptop case that you can burn your fingers after the first reboot after install ... the device didn't stay on for more than 10-15min in a row before the BIOS temperature monitor initiated emergency shutdowns. i also noticed a constant load average above 30.00 in htop after a few hours of researching i found that we apparently switched to the intel_pstate driver by default in vivid ... running a very simple script like: while true; do clear cat /proc/cpuinfo |grep MHz sleep 1 done ...revealed that the cores unconditionally switch to something like 133MHz even though there is currently a lot going on in the system (firefox trying to recover 150 tabs after boot, evolution syncing with an IMAP server etc). it looks to me like the intel_pstate driver (at least on ivybridge hardware) is far from being ready for end users and if i wouldn't have known how to do a detailed research on these issues i would most likely have switched to another distro or to a different known working ubuntu release. could we turn this default back to the ondemand cpufreq governor in an SRU until the driver has matured enough, so we do not lose our ivybridge users and do not generate bad press ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ogra 2120 F pulseaudio CurrentDesktop: Unity Date: Sun May 31 11:53:35 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 HibernationDevice: RESUME=UUID=145593f3-8085-4308-99b1-e1ff9c80f273 InstallationDate: Installed on 2013-11-05 (572 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. XPS L322X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=d0a6e4d2-9705-4ce3-97be-8ec33e06f2cb ro quiet splash intel_pstate=disable crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to vivid on 2015-05-30 (0 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460399] [NEW] ivybridge system gets completely unusable after upgrade to vivid thanks to defaulting to immature intel_pstate driver
Public bug reported: I finally got around to upgrade my work laptop (first gen dell XPS sputnik system (ivy bridge)) yesterday, to find myself with a completely unusable and sluggish desktop, constantly spinning CPU fans and a hot enough laptop case that you can burn your fingers after the first reboot after install ... the device didn't stay on for more than 10-15min in a row before the BIOS temperature monitor initiated emergency shutdowns. i also noticed a constant load average above 30.00 in htop after a few hours of researching i found that we apparently switched to the intel_pstate driver by default in vivid ... running a very simple script like: while true; do clear cat /proc/cpuinfo |grep MHz sleep 1 done ...revealed that the cores unconditionally switch to something like 133MHz even though there is currently a lot going on in the system (firefox trying to recover 150 tabs after boot, evolution syncing with an IMAP server etc). it looks to me like the intel_pstate driver (at least on ivybridge hardware) is far from being ready for end users and if i wouldn't have known how to do a detailed research on these issues i would most likely have switched to another distro or to a different known working ubuntu release. could we turn this default back to the ondemand cpufreq governor in an SRU until the driver has matured enough, so we do not lose our ivybridge users and do not generate bad press ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ogra 2120 F pulseaudio CurrentDesktop: Unity Date: Sun May 31 11:53:35 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 HibernationDevice: RESUME=UUID=145593f3-8085-4308-99b1-e1ff9c80f273 InstallationDate: Installed on 2013-11-05 (572 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. XPS L322X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=d0a6e4d2-9705-4ce3-97be-8ec33e06f2cb ro quiet splash intel_pstate=disable crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to vivid on 2015-05-30 (0 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460399 Title: ivybridge system gets completely unusable after upgrade to vivid thanks to defaulting to immature intel_pstate driver Status in linux package in Ubuntu: New Bug description: I finally got around to upgrade my work laptop (first gen dell XPS sputnik system (ivy bridge)) yesterday, to find myself with a completely unusable and sluggish desktop, constantly spinning CPU fans and a hot enough laptop case that you can burn your fingers after the first reboot after install ... the device didn't stay on for more than 10-15min in a row before the BIOS temperature monitor initiated emergency shutdowns. i also noticed a constant load average above 30.00 in htop after a few hours of researching i found that we apparently switched to the intel_pstate driver by default in vivid ... running a very simple script like: while true; do clear cat /proc/cpuinfo |grep MHz sleep 1 done ...revealed that the cores unconditionally switch to something like 133MHz even though there is currently a lot going on in the system (firefox trying to recover 150 tabs after boot, evolution syncing with an IMAP server etc). it looks to me like the intel_pstate driver (at least on ivybridge hardware) is far from being ready for end users and if i wouldn't have known how to do a detailed research on these issues i would most likely have switched to another distro or to a different known working ubuntu rel
[Kernel-packages] [Bug 1460399] Re: ivybridge system gets completely unusable after upgrade to vivid thanks to defaulting to immature intel_pstate driver
just for completeness (in case someone looks for a wrokaround), adding intel_pstate=disable to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and running sudo update-grub got me the ondemand driver back and got the system back to behave as stable as in 14.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460399 Title: ivybridge system gets completely unusable after upgrade to vivid thanks to defaulting to immature intel_pstate driver Status in linux package in Ubuntu: New Bug description: I finally got around to upgrade my work laptop (first gen dell XPS sputnik system (ivy bridge)) yesterday, to find myself with a completely unusable and sluggish desktop, constantly spinning CPU fans and a hot enough laptop case that you can burn your fingers after the first reboot after install ... the device didn't stay on for more than 10-15min in a row before the BIOS temperature monitor initiated emergency shutdowns. i also noticed a constant load average above 30.00 in htop after a few hours of researching i found that we apparently switched to the intel_pstate driver by default in vivid ... running a very simple script like: while true; do clear cat /proc/cpuinfo |grep MHz sleep 1 done ...revealed that the cores unconditionally switch to something like 133MHz even though there is currently a lot going on in the system (firefox trying to recover 150 tabs after boot, evolution syncing with an IMAP server etc). it looks to me like the intel_pstate driver (at least on ivybridge hardware) is far from being ready for end users and if i wouldn't have known how to do a detailed research on these issues i would most likely have switched to another distro or to a different known working ubuntu release. could we turn this default back to the ondemand cpufreq governor in an SRU until the driver has matured enough, so we do not lose our ivybridge users and do not generate bad press ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ogra 2120 F pulseaudio CurrentDesktop: Unity Date: Sun May 31 11:53:35 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 HibernationDevice: RESUME=UUID=145593f3-8085-4308-99b1-e1ff9c80f273 InstallationDate: Installed on 2013-11-05 (572 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. XPS L322X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=d0a6e4d2-9705-4ce3-97be-8ec33e06f2cb ro quiet splash intel_pstate=disable crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to vivid on 2015-05-30 (0 days ago) dmi.bios.date: 08/28/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276901] Re: alsa-lib: UCM - hammerhead sound doesn't work
** Changed in: alsa-lib (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1276901 Title: alsa-lib: UCM - hammerhead sound doesn't work Status in “alsa-lib” package in Ubuntu: Fix Released Status in “android” package in Ubuntu: Invalid Bug description: 1.) The release I'm using: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 2.) Paket pkgname kann nicht gefunden werden (package pkgname could not be found) 3.) What I expected to happen: Sound should have worked on hammerhead ootb or after performing the steps below (according to the porting guide) 4.) No sound at all The correct sound driver was not used, so I performed the following steps: 1.) Checked '/proc/asound/cars' so see which sound card is installed 2.) Created the path '/usr/share/alsa/ucm/msm8974-taiko-mtp-snd-card' 3.) Copied the three files from '/usr/share/alsa/ucm/apq8064-tabla-snd-card/' to '/usr/share/alsa/ucm/msm8974-taiko-mtp-snd-card' 4.) Renamed 'apq8064-tabla-snd-card.conf' to 'msm8974-taiko-mtp-snd-card.conf' 5.) Modified the files 'HiFi' and 'VoiceCall'. Find&replaced 'apq8064tablasnd' with 'msm8974taikomtpsnd' I attached dmesg, logcat, syslog, amixer and alsa-info before I made the changes (folder original) and after (folder modification). Thank you for helping to fix. Georg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1276901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276901] Re: alsa-lib: UCM - hammerhead sound doesn't work
I merged this into alsa-lib now so users do not have to apply teh files by hand to teh readonly images, please add further improvements you find here or open a new bug ** Changed in: alsa-lib (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1276901 Title: alsa-lib: UCM - hammerhead sound doesn't work Status in “alsa-lib” package in Ubuntu: Fix Committed Status in “android” package in Ubuntu: Invalid Bug description: 1.) The release I'm using: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 2.) Paket pkgname kann nicht gefunden werden (package pkgname could not be found) 3.) What I expected to happen: Sound should have worked on hammerhead ootb or after performing the steps below (according to the porting guide) 4.) No sound at all The correct sound driver was not used, so I performed the following steps: 1.) Checked '/proc/asound/cars' so see which sound card is installed 2.) Created the path '/usr/share/alsa/ucm/msm8974-taiko-mtp-snd-card' 3.) Copied the three files from '/usr/share/alsa/ucm/apq8064-tabla-snd-card/' to '/usr/share/alsa/ucm/msm8974-taiko-mtp-snd-card' 4.) Renamed 'apq8064-tabla-snd-card.conf' to 'msm8974-taiko-mtp-snd-card.conf' 5.) Modified the files 'HiFi' and 'VoiceCall'. Find&replaced 'apq8064tablasnd' with 'msm8974taikomtpsnd' I attached dmesg, logcat, syslog, amixer and alsa-info before I made the changes (folder original) and after (folder modification). Thank you for helping to fix. Georg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1276901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276901] Re: alsa-lib: UCM - hammerhead sound doesn't work
** Also affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-lib (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1276901 Title: alsa-lib: UCM - hammerhead sound doesn't work Status in “alsa-lib” package in Ubuntu: New Status in “android” package in Ubuntu: Invalid Bug description: 1.) The release I'm using: Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 2.) Paket pkgname kann nicht gefunden werden (package pkgname could not be found) 3.) What I expected to happen: Sound should have worked on hammerhead ootb or after performing the steps below (according to the porting guide) 4.) No sound at all The correct sound driver was not used, so I performed the following steps: 1.) Checked '/proc/asound/cars' so see which sound card is installed 2.) Created the path '/usr/share/alsa/ucm/msm8974-taiko-mtp-snd-card' 3.) Copied the three files from '/usr/share/alsa/ucm/apq8064-tabla-snd-card/' to '/usr/share/alsa/ucm/msm8974-taiko-mtp-snd-card' 4.) Renamed 'apq8064-tabla-snd-card.conf' to 'msm8974-taiko-mtp-snd-card.conf' 5.) Modified the files 'HiFi' and 'VoiceCall'. Find&replaced 'apq8064tablasnd' with 'msm8974taikomtpsnd' I attached dmesg, logcat, syslog, amixer and alsa-info before I made the changes (folder original) and after (folder modification). Thank you for helping to fix. Georg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1276901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus
i cut that down to http://paste.ubuntu.com/6217518/, applied it and built a kernel ... sadly now Mir does not start at all, SurfaceFlinger does, but is very slow and complains: W/SurfaceFlinger( 659): Timed out waiting for hw vsync; faking it so i guess for using this patch some changes on the userspace side to actually use sysfs instead of uevents is required -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234743 Title: omapfb module floods system with udev events on samsung galaxy nexus Status in Upstart: New Status in “linux” package in Ubuntu: Incomplete Status in “powerd” package in Ubuntu: Fix Released Bug description: Playing an mp4 on a Samsung Galaxy Nexus using today's image (3 Oct 2013) for 30 minutes I observed that init is busy and also consuming heap quite rapidly. Attached is the output from running health-check (found in PPA:colin- king/white) on init pid 1114. Key points: 1. messages being read/written at ~600 messages a second, hence the high context switch rate and ~4.9% CPU load. 2. heap consumption: ~30K a second using brk() and 2K a second via mmap To reproduce: Install health-check: sudo add-apt-repository ppa:colin-king/white sudo apt-get update && sudo apt-get install health-check Download a large mp4 to the phone. Keep screen from blanking using: sudo powerd-cli display on bright & then play the mp4: dbus-launch mediaplayer-app test.mp4 --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop --stage_hint=main_stage And then observe that init is busy for 300 seconds: ps -e | grep init 1 ?00:02:56 init 348 ?00:00:00 init 1114 ?00:03:22 init sudo health-check -p 1114 -d 300 Attached are my results for a 30 minute run. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1234743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus
h ! look what i found ! http://review.cyanogenmod.org/#/c/28068/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234743 Title: omapfb module floods system with udev events on samsung galaxy nexus Status in Upstart: New Status in “linux” package in Ubuntu: Incomplete Status in “powerd” package in Ubuntu: Fix Released Bug description: Playing an mp4 on a Samsung Galaxy Nexus using today's image (3 Oct 2013) for 30 minutes I observed that init is busy and also consuming heap quite rapidly. Attached is the output from running health-check (found in PPA:colin- king/white) on init pid 1114. Key points: 1. messages being read/written at ~600 messages a second, hence the high context switch rate and ~4.9% CPU load. 2. heap consumption: ~30K a second using brk() and 2K a second via mmap To reproduce: Install health-check: sudo add-apt-repository ppa:colin-king/white sudo apt-get update && sudo apt-get install health-check Download a large mp4 to the phone. Keep screen from blanking using: sudo powerd-cli display on bright & then play the mp4: dbus-launch mediaplayer-app test.mp4 --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop --stage_hint=main_stage And then observe that init is busy for 300 seconds: ps -e | grep init 1 ?00:02:56 init 348 ?00:00:00 init 1114 ?00:03:22 init sudo health-check -p 1114 -d 300 Attached are my results for a 30 minute run. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1234743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4
adjusting bug description, this is sadly a constant condition, not related to movie playback ** Summary changed: - omapfb module floods system with udev events on samsung galaxy nexus when playing mp4 + omapfb module floods system with udev events on samsung galaxy nexus -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234743 Title: omapfb module floods system with udev events on samsung galaxy nexus Status in Upstart: New Status in “linux” package in Ubuntu: Incomplete Status in “powerd” package in Ubuntu: Fix Released Bug description: Playing an mp4 on a Samsung Galaxy Nexus using today's image (3 Oct 2013) for 30 minutes I observed that init is busy and also consuming heap quite rapidly. Attached is the output from running health-check (found in PPA:colin- king/white) on init pid 1114. Key points: 1. messages being read/written at ~600 messages a second, hence the high context switch rate and ~4.9% CPU load. 2. heap consumption: ~30K a second using brk() and 2K a second via mmap To reproduce: Install health-check: sudo add-apt-repository ppa:colin-king/white sudo apt-get update && sudo apt-get install health-check Download a large mp4 to the phone. Keep screen from blanking using: sudo powerd-cli display on bright & then play the mp4: dbus-launch mediaplayer-app test.mp4 --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop --stage_hint=main_stage And then observe that init is busy for 300 seconds: ps -e | grep init 1 ?00:02:56 init 348 ?00:00:00 init 1114 ?00:03:22 init sudo health-check -p 1114 -d 300 Attached are my results for a 30 minute run. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1234743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1234743] Re: omapfb module floods system with udev events on samsung galaxy nexus when playing mp4
pitti pointed on IRC to https://android.googlesource.com/kernel/msm/+/57195292 ... which doesnt help for our driver, but the problem does not seem to be uniqe -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1234743 Title: omapfb module floods system with udev events on samsung galaxy nexus Status in Upstart: New Status in “linux” package in Ubuntu: Incomplete Status in “powerd” package in Ubuntu: Fix Released Bug description: Playing an mp4 on a Samsung Galaxy Nexus using today's image (3 Oct 2013) for 30 minutes I observed that init is busy and also consuming heap quite rapidly. Attached is the output from running health-check (found in PPA:colin- king/white) on init pid 1114. Key points: 1. messages being read/written at ~600 messages a second, hence the high context switch rate and ~4.9% CPU load. 2. heap consumption: ~30K a second using brk() and 2K a second via mmap To reproduce: Install health-check: sudo add-apt-repository ppa:colin-king/white sudo apt-get update && sudo apt-get install health-check Download a large mp4 to the phone. Keep screen from blanking using: sudo powerd-cli display on bright & then play the mp4: dbus-launch mediaplayer-app test.mp4 --desktop_file_hint=/usr/share/applications/mediaplayer-app.desktop --stage_hint=main_stage And then observe that init is busy for 300 seconds: ps -e | grep init 1 ?00:02:56 init 348 ?00:00:00 init 1114 ?00:03:22 init sudo health-check -p 1114 -d 300 Attached are my results for a 30 minute run. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1234743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
note that touch images do not use unity-panel-service anywhere -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1235649] Re: session upstart leaks massive amounts of memory on Ubuntu Touch
i can definitely make it stop consuming more ram by stopping the upstart-event-bridge session job. this works on both devices. the ram does not get freed but the consumption does not keep rising either anymore then. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1235649 Title: session upstart leaks massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
