August 2015 - 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] Kernel:linux-next: ARM
by Matwey V. Kornilov 06 Oct '15

06 Oct '15

Hi, Could we have ARM builds for Kernel:linux-next? The reason behind is that our kernel in Kernel:HEAD usually not even builds for early rc-s due to carefully applied upstream bugs. It would be great to be able to detect build failures as early as possible and report the problems upstream. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 5

[opensuse-kernel] armv7hl kernel-default config have tegra20 serial output broken
by Misha Komarovskiy 06 Oct '15

06 Oct '15

Hello, I found that latest images for my armv7 board (paz00/ac100) which use kernel-default have kernel panic on start without any output to serial console, but serial output was working last time i tested image back in may. I cloned kernel-source git repo made sequence-patched kernel and recompiled it with enabling DEBUG_LL,TEGRA UART_A and EARLYPRINTK config options added to config/armv7hl/default config, but found that there is no ttyS0 output, only earlycon here is paste: http://paste.opensuse.org/31390203 Recompiling same kernel with multi_v7_defconfig config and same debug/earlyprintk options have no panics and normal serial output: http://paste.opensuse.org/13080662 Maybe kernel-default config require some extra tricks now to have serial output? I want to catch that panic. --- Best Regards, Misha Komarovskiy zombahatgmaildotcom -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 17

[opensuse-kernel] status of kernel-pv? drop-in replacement for kernel-xen?
by robert.devanna＠nospammail.net 05 Oct '15

05 Oct '15

What is the current status of kernel-pv? Is it intended to be a drop-in replacement for Xen DomU guests? My initial tests at 3rd party providers' Guests (e.g. Linode), fail to boot. That's with no changes to the guest. Is it ready? Are there changes required in the guest? Are there specific host/guest version requirements for Xen, etc? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 3

[opensuse-kernel] 32bit 13.2 panic when no apm=off on cmdline
by Felix Miata 20 Sep '15

20 Sep '15

I just spent most of the past several days getting this Intel 2 core E6700 P965/ICH8 RAID1 system switched from 11.4 to 13.1 and 13.2 in multiboot via Grub Legacy on primary partition. To do so, I used a single HD Intel 2 core E7600 mule/testing system with 2 new disks added, using running 13.1's yast to build all RAID devices on the new pair prior to initializing 13.1 installation. I eventually got both 13.1 and 13.2 booting and running satisfactorily, restored an rsync backup of user data to the RAID, then shut down this system and moved the RAID pair to it. 13.1 worked satisfactorily immediately, including NIC config retaining fixed IP on eth0. 13.2 spewed trap/segfault errors in a neverending stream virtually instantly in trying to boot from some cmdline config attempts. Many of the others ended in trap data, blinking keyboard LEDs and frozen screen claiming reboot would occur in 90 seconds. The failsafe stanza provided boot, but during init many errors were spewed on tty1 among normal messages. Before I even thought to try failsafe, I chrooted from 13.1 to zypper up and update kernel from 3.16.6 to 3.16.7, then when that didn't help, TW's 3.18.3, also no help. I booted failsafe taking one more option off cmdline each time about 8 times until the only rescue options left were noresume and apm=off, so apm=off definitely functions to get a working boot, yet not without seeing the error stream on tty1. The last attempt without apm=off produced the frozen screen and keyboard condition. I looked in the mailing list archives and Bugzilla, but didn't find anything I recognized as similar. Is there something journalctl can capture that can help someone help me figure out if this is a 13.2 bug that may have escaped discovery before now? FWIW, installing new kernels via chroot produces 13.2 initrds 50% bigger than those happening on account of zypper up processing. Here out of habit, zypper up/dup excludes adding a new kernel. I zypper al kernel* first, up, unlock, then repeat, so that the new kernel's initrd is guaranteed to be built once only. Also FWIW, 13.1 (like 11.4 did) requires clock=hpet on cmdline to prevent clock apparently overpowering ntp. While asleep last night it gained something like 10 minutes in 6 hours. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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 5

[opensuse-kernel] Evergreen 13.1 kernel - revisited
by Michal Kubecek 14 Sep '15

14 Sep '15

Hello, I'm currently rethinking the decision to base Evergreen 13.1 kernel on SLE12 one; I would like to discuss the option to base it on SLE12-SP1 kernel instead. When I started planning the kernel for Evergreen 13.1, using SLE12 for it was a natural choice: expected end of 13.1 regular support was about half a year after SLE12 release and SLE12 had 3.12 kernel which was close enough to 3.11 we present in 13.1. This kernel is already available for anyone wishing to use it in home:mkubecek:evergreen-13.1 OBS repository and AFAIK some people are running it on their 13.1 systems (me, for instance). However, a few things changed since the original decision and now it looks like 13.1 is going to be supported until shortly after SLE12 SP1 is released. As SLE12-SP1 kernel is also 3.12 (but with many additional backports), basing Evergreen 13.1 kernel on SLE12-SP1 would have some advantages while the transition would be less demanding than moving to a new base version. I tried to gather the pros and cons of the transition: + more backports, mostly drivers but also some "core" functionality + some non-critical fixes that were too intrusive for a maintenance update + longer regular support - current users might encounter some problems (like need to rebuild 3rd party modules) - SLE12 is more mature after more than year, SLE12-SP1 will be relatively fresh If it was only up to me, I would probably go on with the transition to SLE12-SP1. But I would like to hear from current evergreen-13.1 kernel users and users planning to use Evergreen 13.1 when 13.1 regular support finishes. Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

6 10

[opensuse-kernel] [PATCH] config: add FBTFT for arm64/armv6hl/armv7hl
by Stefan Brüns 05 Sep '15

05 Sep '15

set CONFIG_FB_TFT*=m There are several TFT capes/hats/... for all kinds of SBCs, enable these. Tested on RPi B with 3.2" TFT connected over SPI. Signed-off-by: Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- config/arm64/default | 30 +++++++++++++++++++++++++++++- config/arm64/vanilla | 30 +++++++++++++++++++++++++++++- config/armv6hl/default | 32 ++++++++++++++++++++++++++++++-- config/armv6hl/vanilla | 32 ++++++++++++++++++++++++++++++-- config/armv7hl/default | 30 +++++++++++++++++++++++++++++- config/armv7hl/lpae | 30 +++++++++++++++++++++++++++++- config/armv7hl/vanilla | 30 +++++++++++++++++++++++++++++- 7 files changed, 205 insertions(+), 9 deletions(-) diff --git a/config/arm64/default b/config/arm64/default index 08bfa19..950d57b 100644 --- a/config/arm64/default +++ b/config/arm64/default @@ -5767,7 +5767,35 @@ CONFIG_DGNC=m CONFIG_DGAP=m # CONFIG_GS_FPGABOOT is not set CONFIG_COMMON_CLK_XLNX_CLKWZRD=m -# CONFIG_FB_TFT is not set +CONFIG_FB_TFT=m +CONFIG_FB_TFT_AGM1264K_FL=m +CONFIG_FB_TFT_BD663474=m +CONFIG_FB_TFT_HX8340BN=m +CONFIG_FB_TFT_HX8347D=m +CONFIG_FB_TFT_HX8353D=m +CONFIG_FB_TFT_ILI9163=m +CONFIG_FB_TFT_ILI9320=m +CONFIG_FB_TFT_ILI9325=m +CONFIG_FB_TFT_ILI9340=m +CONFIG_FB_TFT_ILI9341=m +CONFIG_FB_TFT_ILI9481=m +CONFIG_FB_TFT_ILI9486=m +CONFIG_FB_TFT_PCD8544=m +CONFIG_FB_TFT_RA8875=m +CONFIG_FB_TFT_S6D02A1=m +CONFIG_FB_TFT_S6D1121=m +CONFIG_FB_TFT_SSD1289=m +CONFIG_FB_TFT_SSD1306=m +CONFIG_FB_TFT_SSD1331=m +CONFIG_FB_TFT_SSD1351=m +CONFIG_FB_TFT_ST7735R=m +CONFIG_FB_TFT_TINYLCD=m +CONFIG_FB_TFT_TLS8204=m +CONFIG_FB_TFT_UC1701=m +CONFIG_FB_TFT_UPD161704=m +CONFIG_FB_TFT_WATTEROTT=m +CONFIG_FB_FLEX=m +CONFIG_FB_TFT_FBTFT_DEVICE=m CONFIG_FSL_MC_BUS=m CONFIG_CHROME_PLATFORMS=y # CONFIG_CROS_EC_CHARDEV is not set diff --git a/config/arm64/vanilla b/config/arm64/vanilla index 7455017..e4c2083 100644 --- a/config/arm64/vanilla +++ b/config/arm64/vanilla @@ -5761,7 +5761,35 @@ CONFIG_DGNC=m CONFIG_DGAP=m # CONFIG_GS_FPGABOOT is not set CONFIG_COMMON_CLK_XLNX_CLKWZRD=m -# CONFIG_FB_TFT is not set +CONFIG_FB_TFT=m +CONFIG_FB_TFT_AGM1264K_FL=m +CONFIG_FB_TFT_BD663474=m +CONFIG_FB_TFT_HX8340BN=m +CONFIG_FB_TFT_HX8347D=m +CONFIG_FB_TFT_HX8353D=m +CONFIG_FB_TFT_ILI9163=m +CONFIG_FB_TFT_ILI9320=m +CONFIG_FB_TFT_ILI9325=m +CONFIG_FB_TFT_ILI9340=m +CONFIG_FB_TFT_ILI9341=m +CONFIG_FB_TFT_ILI9481=m +CONFIG_FB_TFT_ILI9486=m +CONFIG_FB_TFT_PCD8544=m +CONFIG_FB_TFT_RA8875=m +CONFIG_FB_TFT_S6D02A1=m +CONFIG_FB_TFT_S6D1121=m +CONFIG_FB_TFT_SSD1289=m +CONFIG_FB_TFT_SSD1306=m +CONFIG_FB_TFT_SSD1331=m +CONFIG_FB_TFT_SSD1351=m +CONFIG_FB_TFT_ST7735R=m +CONFIG_FB_TFT_TINYLCD=m +CONFIG_FB_TFT_TLS8204=m +CONFIG_FB_TFT_UC1701=m +CONFIG_FB_TFT_UPD161704=m +CONFIG_FB_TFT_WATTEROTT=m +CONFIG_FB_FLEX=m +CONFIG_FB_TFT_FBTFT_DEVICE=m CONFIG_FSL_MC_BUS=m CONFIG_CHROME_PLATFORMS=y # CONFIG_CROS_EC_CHARDEV is not set diff --git a/config/armv6hl/default b/config/armv6hl/default index 6a9ddb2..7221db6 100644 --- a/config/armv6hl/default +++ b/config/armv6hl/default @@ -3995,7 +3995,7 @@ CONFIG_FB_SYS_FOPS=m CONFIG_FB_DEFERRED_IO=y # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set -# CONFIG_FB_BACKLIGHT is not set +CONFIG_FB_BACKLIGHT=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y @@ -4966,7 +4966,35 @@ CONFIG_LNET_MAX_PAYLOAD=1048576 CONFIG_DGAP=m # CONFIG_GS_FPGABOOT is not set # CONFIG_COMMON_CLK_XLNX_CLKWZRD is not set -# CONFIG_FB_TFT is not set +CONFIG_FB_TFT=m +CONFIG_FB_TFT_AGM1264K_FL=m +CONFIG_FB_TFT_BD663474=m +CONFIG_FB_TFT_HX8340BN=m +CONFIG_FB_TFT_HX8347D=m +CONFIG_FB_TFT_HX8353D=m +CONFIG_FB_TFT_ILI9163=m +CONFIG_FB_TFT_ILI9320=m +CONFIG_FB_TFT_ILI9325=m +CONFIG_FB_TFT_ILI9340=m +CONFIG_FB_TFT_ILI9341=m +CONFIG_FB_TFT_ILI9481=m +CONFIG_FB_TFT_ILI9486=m +CONFIG_FB_TFT_PCD8544=m +CONFIG_FB_TFT_RA8875=m +CONFIG_FB_TFT_S6D02A1=m +CONFIG_FB_TFT_S6D1121=m +CONFIG_FB_TFT_SSD1289=m +CONFIG_FB_TFT_SSD1306=m +CONFIG_FB_TFT_SSD1331=m +CONFIG_FB_TFT_SSD1351=m +CONFIG_FB_TFT_ST7735R=m +CONFIG_FB_TFT_TINYLCD=m +CONFIG_FB_TFT_TLS8204=m +CONFIG_FB_TFT_UC1701=m +CONFIG_FB_TFT_UPD161704=m +CONFIG_FB_TFT_WATTEROTT=m +CONFIG_FB_FLEX=m +CONFIG_FB_TFT_FBTFT_DEVICE=m # CONFIG_CHROME_PLATFORMS is not set CONFIG_CLKDEV_LOOKUP=y CONFIG_HAVE_CLK_PREPARE=y diff --git a/config/armv6hl/vanilla b/config/armv6hl/vanilla index 2fa7dac..53dbfad 100644 --- a/config/armv6hl/vanilla +++ b/config/armv6hl/vanilla @@ -3991,7 +3991,7 @@ CONFIG_FB_SYS_FOPS=m CONFIG_FB_DEFERRED_IO=y # CONFIG_FB_SVGALIB is not set # CONFIG_FB_MACMODES is not set -# CONFIG_FB_BACKLIGHT is not set +CONFIG_FB_BACKLIGHT=y CONFIG_FB_MODE_HELPERS=y CONFIG_FB_TILEBLITTING=y @@ -4961,7 +4961,35 @@ CONFIG_LNET_MAX_PAYLOAD=1048576 CONFIG_DGAP=m # CONFIG_GS_FPGABOOT is not set # CONFIG_COMMON_CLK_XLNX_CLKWZRD is not set -# CONFIG_FB_TFT is not set +CONFIG_FB_TFT=m +CONFIG_FB_TFT_AGM1264K_FL=m +CONFIG_FB_TFT_BD663474=m +CONFIG_FB_TFT_HX8340BN=m +CONFIG_FB_TFT_HX8347D=m +CONFIG_FB_TFT_HX8353D=m +CONFIG_FB_TFT_ILI9163=m +CONFIG_FB_TFT_ILI9320=m +CONFIG_FB_TFT_ILI9325=m +CONFIG_FB_TFT_ILI9340=m +CONFIG_FB_TFT_ILI9341=m +CONFIG_FB_TFT_ILI9481=m +CONFIG_FB_TFT_ILI9486=m +CONFIG_FB_TFT_PCD8544=m +CONFIG_FB_TFT_RA8875=m +CONFIG_FB_TFT_S6D02A1=m +CONFIG_FB_TFT_S6D1121=m +CONFIG_FB_TFT_SSD1289=m +CONFIG_FB_TFT_SSD1306=m +CONFIG_FB_TFT_SSD1331=m +CONFIG_FB_TFT_SSD1351=m +CONFIG_FB_TFT_ST7735R=m +CONFIG_FB_TFT_TINYLCD=m +CONFIG_FB_TFT_TLS8204=m +CONFIG_FB_TFT_UC1701=m +CONFIG_FB_TFT_UPD161704=m +CONFIG_FB_TFT_WATTEROTT=m +CONFIG_FB_FLEX=m +CONFIG_FB_TFT_FBTFT_DEVICE=m # CONFIG_CHROME_PLATFORMS is not set CONFIG_CLKDEV_LOOKUP=y CONFIG_HAVE_CLK_PREPARE=y diff --git a/config/armv7hl/default b/config/armv7hl/default index 70b9c76..d1a911e 100644 --- a/config/armv7hl/default +++ b/config/armv7hl/default @@ -6814,7 +6814,35 @@ CONFIG_LNET_MAX_PAYLOAD=1048576 CONFIG_DGAP=m CONFIG_GS_FPGABOOT=m # CONFIG_COMMON_CLK_XLNX_CLKWZRD is not set -# CONFIG_FB_TFT is not set +CONFIG_FB_TFT=m +CONFIG_FB_TFT_AGM1264K_FL=m +CONFIG_FB_TFT_BD663474=m +CONFIG_FB_TFT_HX8340BN=m +CONFIG_FB_TFT_HX8347D=m +CONFIG_FB_TFT_HX8353D=m +CONFIG_FB_TFT_ILI9163=m +CONFIG_FB_TFT_ILI9320=m +CONFIG_FB_TFT_ILI9325=m +CONFIG_FB_TFT_ILI9340=m +CONFIG_FB_TFT_ILI9341=m +CONFIG_FB_TFT_ILI9481=m +CONFIG_FB_TFT_ILI9486=m +CONFIG_FB_TFT_PCD8544=m +CONFIG_FB_TFT_RA8875=m +CONFIG_FB_TFT_S6D02A1=m +CONFIG_FB_TFT_S6D1121=m +CONFIG_FB_TFT_SSD1289=m +CONFIG_FB_TFT_SSD1306=m +CONFIG_FB_TFT_SSD1331=m +CONFIG_FB_TFT_SSD1351=m +CONFIG_FB_TFT_ST7735R=m +CONFIG_FB_TFT_TINYLCD=m +CONFIG_FB_TFT_TLS8204=m +CONFIG_FB_TFT_UC1701=m +CONFIG_FB_TFT_UPD161704=m +CONFIG_FB_TFT_WATTEROTT=m +CONFIG_FB_FLEX=m +CONFIG_FB_TFT_FBTFT_DEVICE=m CONFIG_CHROME_PLATFORMS=y CONFIG_CROS_EC_CHARDEV=m CONFIG_CROS_EC_PROTO=y diff --git a/config/armv7hl/lpae b/config/armv7hl/lpae index 62fbaf7..c40f0e0 100644 --- a/config/armv7hl/lpae +++ b/config/armv7hl/lpae @@ -6483,7 +6483,35 @@ CONFIG_LNET_MAX_PAYLOAD=1048576 CONFIG_DGAP=m # CONFIG_GS_FPGABOOT is not set # CONFIG_COMMON_CLK_XLNX_CLKWZRD is not set -# CONFIG_FB_TFT is not set +CONFIG_FB_TFT=m +CONFIG_FB_TFT_AGM1264K_FL=m +CONFIG_FB_TFT_BD663474=m +CONFIG_FB_TFT_HX8340BN=m +CONFIG_FB_TFT_HX8347D=m +CONFIG_FB_TFT_HX8353D=m +CONFIG_FB_TFT_ILI9163=m +CONFIG_FB_TFT_ILI9320=m +CONFIG_FB_TFT_ILI9325=m +CONFIG_FB_TFT_ILI9340=m +CONFIG_FB_TFT_ILI9341=m +CONFIG_FB_TFT_ILI9481=m +CONFIG_FB_TFT_ILI9486=m +CONFIG_FB_TFT_PCD8544=m +CONFIG_FB_TFT_RA8875=m +CONFIG_FB_TFT_S6D02A1=m +CONFIG_FB_TFT_S6D1121=m +CONFIG_FB_TFT_SSD1289=m +CONFIG_FB_TFT_SSD1306=m +CONFIG_FB_TFT_SSD1331=m +CONFIG_FB_TFT_SSD1351=m +CONFIG_FB_TFT_ST7735R=m +CONFIG_FB_TFT_TINYLCD=m +CONFIG_FB_TFT_TLS8204=m +CONFIG_FB_TFT_UC1701=m +CONFIG_FB_TFT_UPD161704=m +CONFIG_FB_TFT_WATTEROTT=m +CONFIG_FB_FLEX=m +CONFIG_FB_TFT_FBTFT_DEVICE=m CONFIG_CHROME_PLATFORMS=y CONFIG_CROS_EC_CHARDEV=m CONFIG_CROS_EC_PROTO=y diff --git a/config/armv7hl/vanilla b/config/armv7hl/vanilla index f1d3d5d..d2e8de4 100644 --- a/config/armv7hl/vanilla +++ b/config/armv7hl/vanilla @@ -6809,7 +6809,35 @@ CONFIG_LNET_MAX_PAYLOAD=1048576 CONFIG_DGAP=m CONFIG_GS_FPGABOOT=m # CONFIG_COMMON_CLK_XLNX_CLKWZRD is not set -# CONFIG_FB_TFT is not set +CONFIG_FB_TFT=m +CONFIG_FB_TFT_AGM1264K_FL=m +CONFIG_FB_TFT_BD663474=m +CONFIG_FB_TFT_HX8340BN=m +CONFIG_FB_TFT_HX8347D=m +CONFIG_FB_TFT_HX8353D=m +CONFIG_FB_TFT_ILI9163=m +CONFIG_FB_TFT_ILI9320=m +CONFIG_FB_TFT_ILI9325=m +CONFIG_FB_TFT_ILI9340=m +CONFIG_FB_TFT_ILI9341=m +CONFIG_FB_TFT_ILI9481=m +CONFIG_FB_TFT_ILI9486=m +CONFIG_FB_TFT_PCD8544=m +CONFIG_FB_TFT_RA8875=m +CONFIG_FB_TFT_S6D02A1=m +CONFIG_FB_TFT_S6D1121=m +CONFIG_FB_TFT_SSD1289=m +CONFIG_FB_TFT_SSD1306=m +CONFIG_FB_TFT_SSD1331=m +CONFIG_FB_TFT_SSD1351=m +CONFIG_FB_TFT_ST7735R=m +CONFIG_FB_TFT_TINYLCD=m +CONFIG_FB_TFT_TLS8204=m +CONFIG_FB_TFT_UC1701=m +CONFIG_FB_TFT_UPD161704=m +CONFIG_FB_TFT_WATTEROTT=m +CONFIG_FB_FLEX=m +CONFIG_FB_TFT_FBTFT_DEVICE=m CONFIG_CHROME_PLATFORMS=y CONFIG_CROS_EC_CHARDEV=m CONFIG_CROS_EC_PROTO=y -- 2.1.4 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

5 6

[opensuse-kernel] Why suse still choose SLAB as the default?
by Navin Parakkal 03 Sep '15

03 Sep '15

Hi, I would like to know why SUSE through SLES and openSUSE still uses CONFIG_SLAB as the allocator instead of CONFIG_SLUB ?. I've seen worst case scenarios locking up buffer_head when there is fragmentation and the number of slabs are in millions. Any particular case where it performs better than SLUB . I'm not investigating on low end systems where SLOB is another option. Regards, Navin -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

10 21

[opensuse-kernel] wrong version for update virtualbox-host-kmp-deskltop
by Giacomo Comes 22 Aug '15

22 Aug '15

Four days ago there was a kernel update for 13.2. In the update the packages virtualbox-{guest,host}-kmp-<flavor> were missing. Today virtualbox was updated as well, but the version is wrong. The last kernel version is 3.16.7-24.1. The version for the virtualbox-{guest,host}-kmp-<flavor> update should be 4.3.30_k3.16.7_24-17.1 but instead it is 4.3.30_k3.16.7_21-17.1 (incompatible with kernel 3.16.7-24.1). Giacomo -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

9 26

[opensuse-kernel] [PATCH 1/1] config: armv7hl: Disable Exynos IOMMU
by Misha Komarovskiy 20 Aug '15

20 Aug '15

Enabling DRM Exynos IOMMU is currently broken, source commit: 6562f3bd396a ("ARM: exynos_defconfig: Disable IOMMU support"). Signed-off-by: Misha Komarovskiy <zombah(a)gmail.com> --- config/armv7hl/default | 4 +--- config/armv7hl/lpae | 4 +--- config/armv7hl/vanilla | 4 +--- 3 files changed, 3 insertions(+), 9 deletions(-) diff --git a/config/armv7hl/default b/config/armv7hl/default index 5455416..1e1af7f 100644 --- a/config/armv7hl/default +++ b/config/armv7hl/default @@ -5130,7 +5130,6 @@ CONFIG_DRM_NOUVEAU_BACKLIGHT=y # CONFIG_DRM_SAVAGE is not set CONFIG_DRM_VGEM=m CONFIG_DRM_EXYNOS=y -CONFIG_DRM_EXYNOS_IOMMU=y CONFIG_DRM_EXYNOS_FIMD=y # CONFIG_DRM_EXYNOS7_DECON is not set CONFIG_DRM_EXYNOS_DPI=y @@ -6832,8 +6831,7 @@ CONFIG_OMAP_IOMMU_DEBUG=y CONFIG_ROCKCHIP_IOMMU=y CONFIG_TEGRA_IOMMU_GART=y CONFIG_TEGRA_IOMMU_SMMU=y -CONFIG_EXYNOS_IOMMU=y -# CONFIG_EXYNOS_IOMMU_DEBUG is not set +# CONFIG_EXYNOS_IOMMU is not set CONFIG_SHMOBILE_IPMMU=y CONFIG_SHMOBILE_IPMMU_TLB=y CONFIG_SHMOBILE_IOMMU=y diff --git a/config/armv7hl/lpae b/config/armv7hl/lpae index acf6b5a..b4412a3 100644 --- a/config/armv7hl/lpae +++ b/config/armv7hl/lpae @@ -4891,7 +4891,6 @@ CONFIG_DRM_NOUVEAU_BACKLIGHT=y # CONFIG_DRM_SAVAGE is not set CONFIG_DRM_VGEM=m CONFIG_DRM_EXYNOS=m -CONFIG_DRM_EXYNOS_IOMMU=y CONFIG_DRM_EXYNOS_FIMD=y # CONFIG_DRM_EXYNOS7_DECON is not set CONFIG_DRM_EXYNOS_DPI=y @@ -6474,8 +6473,7 @@ CONFIG_OMAP_IOMMU=y CONFIG_OMAP_IOMMU_DEBUG=y CONFIG_ROCKCHIP_IOMMU=y CONFIG_TEGRA_IOMMU_SMMU=y -CONFIG_EXYNOS_IOMMU=y -# CONFIG_EXYNOS_IOMMU_DEBUG is not set +# CONFIG_EXYNOS_IOMMU is not set CONFIG_SHMOBILE_IPMMU=y CONFIG_SHMOBILE_IPMMU_TLB=y CONFIG_SHMOBILE_IOMMU=y diff --git a/config/armv7hl/vanilla b/config/armv7hl/vanilla index 6041043..53e92ef 100644 --- a/config/armv7hl/vanilla +++ b/config/armv7hl/vanilla @@ -5126,7 +5126,6 @@ CONFIG_DRM_NOUVEAU_BACKLIGHT=y # CONFIG_DRM_SAVAGE is not set CONFIG_DRM_VGEM=m CONFIG_DRM_EXYNOS=y -CONFIG_DRM_EXYNOS_IOMMU=y CONFIG_DRM_EXYNOS_FIMD=y # CONFIG_DRM_EXYNOS7_DECON is not set CONFIG_DRM_EXYNOS_DPI=y @@ -6827,8 +6826,7 @@ CONFIG_OMAP_IOMMU_DEBUG=y CONFIG_ROCKCHIP_IOMMU=y CONFIG_TEGRA_IOMMU_GART=y CONFIG_TEGRA_IOMMU_SMMU=y -CONFIG_EXYNOS_IOMMU=y -# CONFIG_EXYNOS_IOMMU_DEBUG is not set +# CONFIG_EXYNOS_IOMMU is not set CONFIG_SHMOBILE_IPMMU=y CONFIG_SHMOBILE_IPMMU_TLB=y CONFIG_SHMOBILE_IOMMU=y -- 1.8.4.5 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

7 9

[opensuse-kernel] ARM kernel config wrongly reverted on 4.2-rc6 update
by Guillaume Gardet 17 Aug '15

17 Aug '15

Hi Jeff, On your 4.2-rc6 kernel config update you reverted 2 commits from Andreas Färber, done after 4.2-rc5. See commit 4a2cf4a409b54e75f8ac4cd7a19fa8e8bc516aca: http://kernel.opensuse.org/cgit/kernel-source/commit/?id=4a2cf4a409b54e75f8… I guess this is an error? Guillaume -- 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] openSUSE GIT kernel repo broken?
by Guillaume Gardet 17 Aug '15

17 Aug '15

Hi, I have a clone of openSUSE GIT kernel and kernel-source repositories and found a problem on master branch. While kernel-source is at 4.2-rc6, kernel repo is only at 4.1.1 and git log shows lots of commit with the following message: ********************************************************************** Note: This patch series did not apply ********************************************************************** Any idea what is going on? Guillaume -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 8

[opensuse-kernel] CONFIG_IPV6_SIT_6RD ?
by PGNd 13 Aug '15

13 Aug '15

I need in-kernel 6RD support to setup a tunnel to an upstream ISP (AT&T/Uverse). Checking current Kernel:Stable on OpenSUSE 13.2, grep -i 6RD /boot/config-4.1.4-1.ga37e14f-default # CONFIG_IPV6_SIT_6RD is not set In this thread CONFIG_IPV6_SIT_6RD http://lists.opensuse.org/opensuse-kernel/2011-01/msg00001.html the option had been enabled for 11.4 kernel. Is there a kernel branch with the option enabled? Or, was there a reason it was disabled? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

6 11

[opensuse-kernel] kernel-obs-build
by Bruno Friedmann 11 Aug '15

11 Aug '15

I was a bit surprised to not have seen kernel-obs-build with no increment version since kernel-obs-build-3.19.2-2.1.g6c3d33f.x86_64.rpm 23-Mar-2015 13:47 in kernel:stable repo. Having a look on obs, it seems that both kernel-obs-build and kernel-obs-qa are only build for QA target. Did I miss something, or what is the reason to not have anymore kernel-obs-build build for standard target ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 7

[opensuse-kernel] CONFIG_EFI_MIXED (x86_64 kernel vs. 32-bit UEFI)
by Michal Kubecek 01 Aug '15

01 Aug '15

Current openSUSE kernels have CONFIG_EFI_MIXED (support for 32-bit UEFI in x86_64 kernel) disabled. This was set when the option was introduced in 3.15 with comment "do we use a bootloader that can support it?" However, while grub2 can boot x86_64 kernel under 32-bit UEFI even without CONFIG_EFI_MIXED, the option is needed for kernel to access efivars (needed for efibootmgr and therefore grub2-install) and UEFI services. So I would like to suggest enabling CONFIG_EFI_MIXED; it's only available on x86_64 but I'm not sure which flavours: default, desktop, debug and vanilla should have it, xen and ec2 can't; I'm not sure about pv: would support for EFI mixed mode make any sense there? Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

4 13