January 2018 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] kernel-default-base-2.6.29-5.2.x86_64 rpm errors
by Dave Plater 18 Jul '24

18 Jul '24

Hi, I'm busy updating to the latest factory kernel and have received the following errors from kernel-default-base installation (I did insert a blank dvd during the installation of the rpm by zypper):- WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol register_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_ioctl WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_media_changed WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_get_media_event WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_release WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_open WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol unregister_cdrom WARNING: /lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sr_mod.ko needs unknown symbol cdrom_number_of_slots And then these errors which I think IIRC happened before when the kernel was first split into three:- Kernel image: /boot/vmlinuz-2.6.29-rc8-5-default Initrd image: /boot/initrd-2.6.29-rc8-5-default Root device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part3 (/dev/sda3) (mounted on / as xfs) Resume device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part2 (/dev/sda2) FATAL: Module processor not found. WARNING: no dependencies for kernel module 'processor' found. FATAL: Module thermal not found. WARNING: no dependencies for kernel module 'thermal' found. FATAL: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. FATAL: Module piix not found. WARNING: no dependencies for kernel module 'piix' found. FATAL: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. FATAL: Module fan not found. WARNING: no dependencies for kernel module 'fan' found. FATAL: Module xfs not found. WARNING: no dependencies for kernel module 'xfs' found. FATAL: Module usbhid not found. WARNING: no dependencies for kernel module 'usbhid' found. Kernel Modules: scsi_mod libata ata_piix edd ahci sd_mod usbcore ohci-hcd ehci-hcd uhci-hcd WARNING: /dev/shm/mkinitramfs.0drQsZ/mnt/lib/modules/2.6.29-rc8-5-default/kernel/drivers/scsi/sd_mod.ko needs unknown symbol crc_t10dif Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 22669 blocks Should I open a bug report about the errors which are possibly from inserting a dvd while the kernel rpm was installing? Regards Dave P -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org

2 2

[opensuse-kernel] [PATCH] config: arm64: Enable Aardvark PCIe controller
by Matwey V. Kornilov 16 Feb '18

16 Feb '18

Aardvark PCIe controller is a part of Marvel Armada 3700 SoC. This option is required to support PCIe for JeOS-espressobin. Signed-off-by: Matwey V. Kornilov <matwey.kornilov(a)gmail.com> --- config/arm64/default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/arm64/default b/config/arm64/default index 38a262c426..e6bc10b65e 100644 --- a/config/arm64/default +++ b/config/arm64/default @@ -480,7 +480,7 @@ CONFIG_PCIE_KIRIN=y # # PCI host controller drivers # -# CONFIG_PCI_AARDVARK is not set +CONFIG_PCI_AARDVARK=y CONFIG_PCIE_XILINX_NWL=y CONFIG_PCI_TEGRA=y CONFIG_PCI_HOST_COMMON=y -- 2.13.6 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 3

[opensuse-kernel] [PATCH] Add patches.suse/0001-ARM-dts-bcm283x-Add-vchiq-DT-node-to-be-able-to-use-.patch
by Guillaume GARDET 01 Feb '18

01 Feb '18

This patch is for stable and master branches. Signed-off-by: Guillaume GARDET <guillaume.gardet(a)free.fr> --- ...283x-Add-vchiq-DT-node-to-be-able-to-use-.patch | 39 ++++++++++++++++++++++ series.conf | 2 ++ 2 files changed, 41 insertions(+) create mode 100644 patches.suse/0001-ARM-dts-bcm283x-Add-vchiq-DT-node-to-be-able-to-use-.patch diff --git a/patches.suse/0001-ARM-dts-bcm283x-Add-vchiq-DT-node-to-be-able-to-use-.patch b/patches.suse/0001-ARM-dts-bcm283x-Add-vchiq-DT-node-to-be-able-to-use-.patch new file mode 100644 index 0000000000..6a7e4aa81a --- /dev/null +++ b/patches.suse/0001-ARM-dts-bcm283x-Add-vchiq-DT-node-to-be-able-to-use-.patch @@ -0,0 +1,39 @@ +From 56704b86391fc63b5626eccbc009228fdfd004ee Mon Sep 17 00:00:00 2001 +From: Guillaume GARDET <guillaume.gardet(a)free.fr> +Date: Tue, 30 Jan 2018 15:21:20 +0100 +Subject: [PATCH] ARM: dts: bcm283x: Add vchiq DT node to be able to use vchiq + staging driver +Patch-mainline: No, this for a staging driver + +With this vchiq DT node, we are able to use the vchiq interface on bcm383x SoC. +It has been tested succesfuly on RPi2 with omxplayer to decode 480p and 1080p +h.264 movies. + +Signed-off-by: Guillaume GARDET <guillaume.gardet(a)free.fr> + +--- + arch/arm/boot/dts/bcm2835-rpi.dtsi | 8 ++++++++ + 1 file changed, 8 insertions(+) + +diff --git a/arch/arm/boot/dts/bcm2835-rpi.dtsi b/arch/arm/boot/dts/bcm2835-rpi.dtsi +index e36c392a2b8f..65cdc3066b0d 100644 +--- a/arch/arm/boot/dts/bcm2835-rpi.dtsi ++++ b/arch/arm/boot/dts/bcm2835-rpi.dtsi +@@ -27,6 +27,14 @@ + firmware = <&firmware>; + #power-domain-cells = <1>; + }; ++ ++ vchiq { ++ compatible = "brcm,bcm2835-vchiq"; ++ reg = <0x7e00b840 0xf>; ++ interrupts = <0 2>; ++ cache-line-size = <32>; ++ firmware = <&firmware>; ++ }; + }; + }; + +-- +2.13.6 + diff --git a/series.conf b/series.conf index 6d2c1c1132..141281854c 100644 --- a/series.conf +++ b/series.conf @@ -1632,6 +1632,8 @@ ######################################################## # ARM ######################################################## + # Add vchiq DT node for bcm283x for staging vchiq driver + patches.suse/0001-ARM-dts-bcm283x-Add-vchiq-DT-node-to-be-able-to-use-.patch ######################################################## # S/390 -- 2.13.6 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 2

[opensuse-kernel] https://en.opensuse.org/Kernel omits desktop-base
by Felix Miata 18 Jan '18

18 Jan '18

kernel-default-base on the mirrors runs very roughly 40% the size of kernel-default. Who is the smaller designed for? What does the larger have that the smaller doesn't? The page doesn't say. Can a simple/minimal EXT4 *86 PC installation get by on just the smaller? Last edit there was 2013, so it still includes kernel-desktop. :-( -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 1

[opensuse-kernel] kernel-devel conflicts on update from 4.14.12-1.x to 4.14.12-1.8
by Andrei Borzenkov 17 Jan '18

17 Jan '18

See https://forums.opensuse.org/showthread.php/529126-Zypper-dup-failure-file-c…. Suddenly zypper dup started to complain about file conflicts in kernel-devel. Now we know it is impossible to multiversion two rebuilds of the same RPM, but zypper has explicit workaround for kernel-default and kernel-default-devel. Has something changed in kernel packaging recently? Or is it zypper? localhost:~ # zypper in -D kernel-default kernel-default-devel kernel-devel Loading repository data... Reading installed packages... Resolving package dependencies... The following 3 NEW packages are going to be installed: kernel-default-4.14.12-1.8 kernel-default-devel-4.14.12-1.8 kernel-devel-4.14.12-1.8 The following 2 packages are going to be REMOVED: kernel-default-4.14.12-1.4 kernel-default-devel-4.14.12-1.4 3 new packages to install, 2 to remove. Overall download size: 75.5 MiB. Already cached: 0 B. After the operation, additional 56.5 MiB will Continue? [y/n/...? shows all options] (y): n -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 2

[opensuse-kernel] Trouble with module e1000e on Leap 42.3
by Giacomo Comes 17 Jan '18

17 Jan '18

Hi, I have the following systems that use the e1000e ethernet module: Dell Optiplex 7010 with: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04) and Dell Optiplex 7040 with: 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I219-LM [8086:15b7] (rev 31) Both were working ok with Leap 42.2. Recently I have update them to Leap 42.3 and I have encountered the following problem: After a reboot one of the following happens: - the network works - the network does not work, the link is down as if no ethernet cable is plugged And when the network works one of the following happens: - the network continues to work - after some time the link goes down and stays down until the machine is rebooted Suspecting a kernel/driver issue I decided to upgrade the e1000e driver using the one from: https://downloadcenter.intel.com/download/15817 I have used version 3.3.6 and now I'm using version 3.4.0.2. Since the upgrade, I don't have network trouble anymore. I'm not filing a bugreport because I'm not sure opensuse bugzilla is the right place to do it. I think Intel should take care of it, by upgrading the e1000e kernel driver. The e1000e driver in the kernel source is version 3.2.6-k I sent this email just make you aware of the issue. Giacomo -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 2

[opensuse-kernel] kexec with secure boot enabled?
by Ludwig Nussel 10 Jan '18

10 Jan '18

Hi, In bug https://bugzilla.opensuse.org/show_bug.cgi?id=1075051#c3 Steffen suspects different settings for kexec with secure boot enabled in Leap 15 vs TW. Is that that case? If so, intentional? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 7