Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p
On Sun, Jan 22, 2017 at 3:18 AM, John M.wrote: > > It took forever to build (i.e., about three hours just for amd64), but yes, > after applying those two patches I can boot properly ("journalctl -b -k" > messages attached). Thanks for the verification! You're lucky that it just takes 2-3 hours on amd64. There's platform that take days to build the kernel [0] (look at "Build time" column). :-P [0] https://buildd.debian.org/status/logs.php?pkg=linux=sh4 On Sun, Jan 22, 2017 at 2:30 AM, Ben Hutchings wrote: > > Please add this bug number to the changelog so it gets closed. Thanks for the remind! Fixed. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#852132: linux-latest: Add support for Hardkernel Odroid-C2
Package: linux-latest Severity: wishlist Dear Maintainer, please, add support for the Hardkernel Odroid C2 to the kernel configuration. For 4.9 kernels this involves: CONFIG_ARCH_MESON=y CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_MESON_GXBB_WATCHDOG=y CONFIG_PWM_MESON=m CONFIG_RESET_MESON=y CONFIG_MESON_SM=y CONFIG_COMMON_CLK_AMLOGIC=y For 4.10 kernels this involves CONFIG_ARCH_MESON=y CONFIG_DWMAC_MESON=y CONFIG_MESON_GXL_PHY=y CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_MESON_GXBB_WATCHDOG=y CONFIG_MESON_WATCHDOG=y CONFIG_DRM_MESON=m CONFIG_MMC_MESON_GX=y CONFIG_PWM_MESON=m CONFIG_RESET_MESON=y CONFIG_PHY_MESON8B_USB2=m CONFIG_MESON_SM=y CONFIG_COMMON_CLK_AMLOGIC=y The following patch is essential. It is queued for 4.10-rc6: ARM64: dts: meson-gx: Add firmware reserved memory zones https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ecb88f3001ed9ee8c53450d971de8c18bcbf7925 Best regards Heinrich Schuchardt -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.10.0-rc3-R001-arm64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
linux_3.16.39-1~bpo70+1_multi.changes ACCEPTED into wheezy-backports->backports-policy, wheezy-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 12 Jan 2017 23:35:51 + Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-0.bpo.4 linux-libc-dev linux-headers-3.16.0-0.bpo.4-all linux-headers-3.16.0-0.bpo.4-all-amd64 kernel-image-3.16.0-0.bpo.4-amd64-di nic-modules-3.16.0-0.bpo.4-amd64-di nic-wireless-modules-3.16.0-0.bpo.4-amd64-di nic-shared-modules-3.16.0-0.bpo.4-amd64-di serial-modules-3.16.0-0.bpo.4-amd64-di usb-serial-modules-3.16.0-0.bpo.4-amd64-di ppp-modules-3.16.0-0.bpo.4-amd64-di pata-modules-3.16.0-0.bpo.4-amd64-di cdrom-core-modules-3.16.0-0.bpo.4-amd64-di firewire-core-modules-3.16.0-0.bpo.4-amd64-di scsi-core-modules-3.16.0-0.bpo.4-amd64-di scsi-modules-3.16.0-0.bpo.4-amd64-di scsi-common-modules-3.16.0-0.bpo.4-amd64-di scsi-extra-modules-3.16.0-0.bpo.4-amd64-di loop-modules-3.16.0-0.bpo.4-amd64-di btrfs-modules-3.16.0-0.bpo.4-amd64-di ext4-modules-3.16.0-0.bpo.4-amd64-di isofs-modules-3.16.0-0.bpo.4-amd64-di jfs-modules-3.16.0-0.bpo.4-amd64-di ntfs-modules-3.16.0-0.bpo.4-amd64-di xfs-modules-3.16.0-0.bpo.4-amd64-di fat-modules-3.16.0-0.bpo.4-amd64-di md-modules-3.16.0-0.bpo.4-amd64-di multipath-modules-3.16.0-0.bpo.4-amd64-di usb-modules-3.16.0-0.bpo.4-amd64-di usb-storage-modules-3.16.0-0.bpo.4-amd64-di pcmcia-storage-modules-3.16.0-0.bpo.4-amd64-di fb-modules-3.16.0-0.bpo.4-amd64-di input-modules-3.16.0-0.bpo.4-amd64-di event-modules-3.16.0-0.bpo.4-amd64-di mouse-modules-3.16.0-0.bpo.4-amd64-di nic-pcmcia-modules-3.16.0-0.bpo.4-amd64-di pcmcia-modules-3.16.0-0.bpo.4-amd64-di nic-usb-modules-3.16.0-0.bpo.4-amd64-di sata-modules-3.16.0-0.bpo.4-amd64-di core-modules-3.16.0-0.bpo.4-amd64-di acpi-modules-3.16.0-0.bpo.4-amd64-di i2c-modules-3.16.0-0.bpo.4-amd64-di crc-modules-3.16.0-0.bpo.4-amd64-di crypto-modules-3.16.0-0.bpo.4-amd64-di crypto-dm-modules-3.16.0-0.bpo.4-amd64-di efi-modules-3.16.0-0.bpo.4-amd64-di ata-modules-3.16.0-0.bpo.4-amd64-di mmc-core-modules-3.16.0-0.bpo.4-amd64-di mmc-modules-3.16.0-0.bpo.4-amd64-di nbd-modules-3.16.0-0.bpo.4-amd64-di squashfs-modules-3.16.0-0.bpo.4-amd64-di speakup-modules-3.16.0-0.bpo.4-amd64-di virtio-modules-3.16.0-0.bpo.4-amd64-di uinput-modules-3.16.0-0.bpo.4-amd64-di sound-modules-3.16.0-0.bpo.4-amd64-di hyperv-modules-3.16.0-0.bpo.4-amd64-di udf-modules-3.16.0-0.bpo.4-amd64-di fuse-modules-3.16.0-0.bpo.4-amd64-di linux-headers-3.16.0-0.bpo.4-common linux-image-3.16.0-0.bpo.4-amd64 linux-headers-3.16.0-0.bpo.4-amd64 linux-image-3.16.0-0.bpo.4-amd64-dbg xen-linux-system-3.16.0-0.bpo.4-amd64 linux-headers-3.16.0-0.bpo.4-all-armel kernel-image-3.16.0-0.bpo.4-kirkwood-di nic-modules-3.16.0-0.bpo.4-kirkwood-di nic-shared-modules-3.16.0-0.bpo.4-kirkwood-di usb-serial-modules-3.16.0-0.bpo.4-kirkwood-di ppp-modules-3.16.0-0.bpo.4-kirkwood-di cdrom-core-modules-3.16.0-0.bpo.4-kirkwood-di scsi-core-modules-3.16.0-0.bpo.4-kirkwood-di loop-modules-3.16.0-0.bpo.4-kirkwood-di btrfs-modules-3.16.0-0.bpo.4-kirkwood-di ext4-modules-3.16.0-0.bpo.4-kirkwood-di isofs-modules-3.16.0-0.bpo.4-kirkwood-di jfs-modules-3.16.0-0.bpo.4-kirkwood-di fat-modules-3.16.0-0.bpo.4-kirkwood-di minix-modules-3.16.0-0.bpo.4-kirkwood-di md-modules-3.16.0-0.bpo.4-kirkwood-di multipath-modules-3.16.0-0.bpo.4-kirkwood-di usb-modules-3.16.0-0.bpo.4-kirkwood-di usb-storage-modules-3.16.0-0.bpo.4-kirkwood-di fb-modules-3.16.0-0.bpo.4-kirkwood-di input-modules-3.16.0-0.bpo.4-kirkwood-di event-modules-3.16.0-0.bpo.4-kirkwood-di mouse-modules-3.16.0-0.bpo.4-kirkwood-di nic-usb-modules-3.16.0-0.bpo.4-kirkwood-di sata-modules-3.16.0-0.bpo.4-kirkwood-di core-modules-3.16.0-0.bpo.4-kirkwood-di crc-modules-3.16.0-0.bpo.4-kirkwood-di crypto-modules-3.16.0-0.bpo.4-kirkwood-di crypto-dm-modules-3.16.0-0.bpo.4-kirkwood-di mmc-modules-3.16.0-0.bpo.4-kirkwood-di nbd-modules-3.16.0-0.bpo.4-kirkwood-di squashfs-modules-3.16.0-0.bpo.4-kirkwood-di uinput-modules-3.16.0-0.bpo.4-kirkwood-di leds-modules-3.16.0-0.bpo.4-kirkwood-di udf-modules-3.16.0-0.bpo.4-kirkwood-di fuse-modules-3.16.0-0.bpo.4-kirkwood-di kernel-image-3.16.0-0.bpo.4-orion5x-di nic-modules-3.16.0-0.bpo.4-orion5x-di nic-shared-modules-3.16.0-0.bpo.4-orion5x-di usb-serial-modules-3.16.0-0.bpo.4-orion5x-di ppp-modules-3.16.0-0.bpo.4-orion5x-di cdrom-core-modules-3.16.0-0.bpo.4-orion5x-di scsi-core-modules-3.16.0-0.bpo.4-orion5x-di loop-modules-3.16.0-0.bpo.4-orion5x-di ipv6-modules-3.16.0-0.bpo.4-orion5x-di btrfs-modules-3.16.0-0.bpo.4-orion5x-di ext4-modules-3.16.0-0.bpo.4-orion5x-di isofs-modules-3.16.0-0.bpo.4-orion5x-di jffs2-modules-3.16.0-0.bpo.4-orion5x-di jfs-modules-3.16.0-0.bpo.4-orion5x-di fat-modules-3.16.0-0.bpo.4-orion5x-di minix-modules-3.16.0-0.bpo.4-orion5x-di md-modules-3.16.0-0.bpo.4-orion5x-di multipath-modules-3.16.0-0.bpo.4-orion5x-di usb-modules-3.16.0-0.bpo.4-orion5x-di usb-storage-modules-3.16.0-0.bpo.4-orion5x-di event-modules-3.16.0-0.bpo.4-orion5x-di
Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p
On Sat, 2017-01-21 at 16:33 +0900, Roger Shimizu wrote: > Control: tag -1 + patch upstream > Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=191 > 121 > > On Fri, Jan 20, 2017 at 11:26 AM, JWMwrote: > > Package: src:linux > > Version: 4.9.2-2 > > Severity: normal > > > > Dear Maintainer, > > > > After upgrading my Thinkpad T440p to linux-image-amd64 from > > unstable (along > > with linux-headers-amd64, linux-doc, linux-perf, linux-source and > > linux-tools), > > I am unable to boot with the 4.9.2 kernel. > > > > Right after GRUB times out, the screen goes blank and nothing > > happens. > > > > According to this page > > > > https://bugzilla.kernel.org/show_bug.cgi?id=191121 > > The report implies the following two commits, which already applied > in > linus tree, can fix this issue. > - http://git.kernel.org/linus/20b1e22d01a4b0b11d3a1066e9feb04be38607 > ec > - http://git.kernel.org/linus/0100a3e67a9cef64d72cd3a1da86f3ddbee503 > 63 > > Is it convenient for you to confirm? > > Cheers, Hi, It took forever to build (i.e., about three hours just for amd64), but yes, after applying those two patches I can boot properly ("journalctl -b -k" messages attached). -- John -- Logs begin at Mon 2016-08-08 16:33:01 COT, end at Sat 2017-01-21 13:14:32 COT. -- Jan 21 12:58:05 walrus-edge kernel: Linux version 4.9.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.2.1 20161124 (Debian 6.2.1-5) ) #1 SMP Debian 4.9.2-2a~test (2017-01-21) Jan 21 12:58:05 walrus-edge kernel: Command line: BOOT_IMAGE=/vmlinuz-4.9.0-1-amd64 root=UUID=6509d59d-a080-4e59-bd0e-e83cacba4369 ro quiet splash resume=UUID=e2031b87-4394-4219-8d65-761dcff59e0f acpi_backlight=vendor Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jan 21 12:58:05 walrus-edge kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Jan 21 12:58:05 walrus-edge kernel: x86/fpu: Using 'eager' FPU context switches. Jan 21 12:58:05 walrus-edge kernel: e820: BIOS-provided physical RAM map: Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x-0x00057fff] usable Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x00058000-0x00058fff] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x00059000-0x0009bfff] usable Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0009c000-0x0009cfff] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0009d000-0x0009dfff] usable Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0009e000-0x000b] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0010-0xb1760fff] usable Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xb1761000-0xb1962fff] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xb1963000-0xbbe99fff] usable Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbbe9a000-0xbc099fff] type 20 Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbc09a000-0xbcbbafff] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbcbbb000-0xbcc0afff] ACPI NVS Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbcc0b000-0xbcc73fff] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbcc74000-0xbce7efff] ACPI NVS Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbce7f000-0xbcefefff] ACPI data Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbceff000-0xbcef] usable Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xbcf0-0xbf9f] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xf80f8000-0xf80f8fff] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0xfed1c000-0xfed1] reserved Jan 21 12:58:05 walrus-edge kernel: BIOS-e820: [mem 0x0001-0x00023e5f] usable Jan 21 12:58:05 walrus-edge kernel: NX (Execute Disable) protection: active Jan 21 12:58:05 walrus-edge kernel: efi: EFI v2.31 by Lenovo Jan 21 12:58:05 walrus-edge kernel: efi: ACPI=0xbcefe000 ACPI 2.0=0xbcefe014 SMBIOS=0xbcc73000 ESRT=0xbc1c8000 Jan 21 12:58:05 walrus-edge kernel: efi: [Firmware Bug]: Invalid EFI memory map entries: Jan 21 12:58:05 walrus-edge kernel: efi: mem40: [Reserved | | | | | | | | | | | | ] range=[0x-0x] (invalid) Jan 21 12:58:05 walrus-edge kernel: efi: mem41: [Reserved | | | | | | | | | | | | ]
Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p
On Sun, 2017-01-22 at 02:04 +0900, Roger Shimizu wrote: > Control: tag -1 +pending > > On Sat, Jan 21, 2017 at 4:33 PM, Roger Shimizum> wrote: > > > > The report implies the following two commits, which already applied > > in > > linus tree, can fix this issue. > > - http://git.kernel.org/linus/20b1e22d01a4b0b11d3a1066e9feb04be386 > > 07ec > > - http://git.kernel.org/linus/0100a3e67a9cef64d72cd3a1da86f3ddbee5 > > 0363 > > The above 2 patches are in 4.9.5, so you'll have it on next unstable > release. Please add this bug number to the changelog so it gets closed. Ben. -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette' signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p
Processing control commands: > tag -1 +pending Bug #851928 [src:linux] linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p Added tag(s) pending. -- 851928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#851928: linux-image-4.9.0-1-amd64: Kernel 4.9 fails to boot on Thinkpad T440p
Control: tag -1 +pending On Sat, Jan 21, 2017 at 4:33 PM, Roger Shimizuwrote: > > The report implies the following two commits, which already applied in > linus tree, can fix this issue. > - http://git.kernel.org/linus/20b1e22d01a4b0b11d3a1066e9feb04be38607ec > - http://git.kernel.org/linus/0100a3e67a9cef64d72cd3a1da86f3ddbee50363 The above 2 patches are in 4.9.5, so you'll have it on next unstable release. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Processed: Re: Bug#851963: linux: enable SENSORS_ADM1031
Processing control commands: > tag -1 -moreinfo +pending Bug #851963 [src:linux] linux: enable SENSORS_ADM1031 Removed tag(s) moreinfo. Bug #851963 [src:linux] linux: enable SENSORS_ADM1031 Added tag(s) pending. -- 851963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#851963: linux: enable SENSORS_ADM1031
Control: tag -1 -moreinfo +pending On Sat, Jan 21, 2017 at 8:23 PM, James Cowgillwrote: > On 21/01/17 10:29, Roger Shimizu wrote: >>> I see this module already exists in the kernel you're using. Can you help to confirm? >>> >>> I'm pretty certain it's not enabled. It is already enabled on x86 however. >> >> Sorry, I just looked at amd64. >> So you're asking for mips64 octeon support, right? > > Yes I am (although this isn't really MIPS specific, the board I have > just happens to use it). Current status: $ grep -r SENSORS_ADM1031 debian/config debian/config/alpha/config:CONFIG_SENSORS_ADM1031=m debian/config/kernelarch-mips/config.malta:CONFIG_SENSORS_ADM1031=m debian/config/kernelarch-powerpc/config:CONFIG_SENSORS_ADM1031=m debian/config/kernelarch-sparc/config:# CONFIG_SENSORS_ADM1031 is not set debian/config/kernelarch-x86/config:CONFIG_SENSORS_ADM1031=m So I added an entry in: debian/config/kernelarch-mips/config.octeon Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#851963: linux: enable SENSORS_ADM1031
On 21/01/17 10:29, Roger Shimizu wrote: > On Sat, Jan 21, 2017 at 6:05 PM, James Cowgillwrote: >> Hi, >> >> On 21/01/17 08:05, Roger Shimizu wrote: >>> Control: tag -1 +moreinfo >>> >>> On Fri, Jan 20, 2017 at 9:17 PM, James Cowgill wrote: Source: linux Version: 4.9.2-2 Severity: wishlist Hi, Please can you enable CONFIG_SENSORS_ADM1031 as a module. I have a Cavium Octeon board which needs this driver to be able to read the CPU temperature / fan sensors. >>> >>> I see this module already exists in the kernel you're using. >>> Can you help to confirm? >> >> I'm pretty certain it's not enabled. It is already enabled on x86 however. > > Sorry, I just looked at amd64. > So you're asking for mips64 octeon support, right? Yes I am (although this isn't really MIPS specific, the board I have just happens to use it). James signature.asc Description: OpenPGP digital signature
Processed: notfound 847343 in 20161130-2~bpo8+1
Processing commands for cont...@bugs.debian.org: > notfound 847343 20161130-2~bpo8+1 Bug #847343 {Done: Ben Hutchings} [firmware-misc-nonfree] firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed Ignoring request to alter found versions of bug #847343 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#851963: linux: enable SENSORS_ADM1031
On Sat, Jan 21, 2017 at 6:05 PM, James Cowgillwrote: > Hi, > > On 21/01/17 08:05, Roger Shimizu wrote: >> Control: tag -1 +moreinfo >> >> On Fri, Jan 20, 2017 at 9:17 PM, James Cowgill wrote: >>> Source: linux >>> Version: 4.9.2-2 >>> Severity: wishlist >>> >>> Hi, >>> >>> Please can you enable CONFIG_SENSORS_ADM1031 as a module. >>> >>> I have a Cavium Octeon board which needs this driver to be able to read >>> the CPU temperature / fan sensors. >> >> I see this module already exists in the kernel you're using. >> Can you help to confirm? > > I'm pretty certain it's not enabled. It is already enabled on x86 however. Sorry, I just looked at amd64. So you're asking for mips64 octeon support, right? Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#851963: linux: enable SENSORS_ADM1031
Hi, On 21/01/17 08:05, Roger Shimizu wrote: > Control: tag -1 +moreinfo > > On Fri, Jan 20, 2017 at 9:17 PM, James Cowgillwrote: >> Source: linux >> Version: 4.9.2-2 >> Severity: wishlist >> >> Hi, >> >> Please can you enable CONFIG_SENSORS_ADM1031 as a module. >> >> I have a Cavium Octeon board which needs this driver to be able to read >> the CPU temperature / fan sensors. > > I see this module already exists in the kernel you're using. > Can you help to confirm? I'm pretty certain it's not enabled. It is already enabled on x86 however. James signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#851963: linux: enable SENSORS_ADM1031
Processing control commands: > tag -1 +moreinfo Bug #851963 [src:linux] linux: enable SENSORS_ADM1031 Added tag(s) moreinfo. -- 851963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#851963: linux: enable SENSORS_ADM1031
Control: tag -1 +moreinfo On Fri, Jan 20, 2017 at 9:17 PM, James Cowgillwrote: > Source: linux > Version: 4.9.2-2 > Severity: wishlist > > Hi, > > Please can you enable CONFIG_SENSORS_ADM1031 as a module. > > I have a Cavium Octeon board which needs this driver to be able to read > the CPU temperature / fan sensors. I see this module already exists in the kernel you're using. Can you help to confirm? Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Bug#851821: linux: Please enable CONFIG_TOUCHSCREEN_GOODIX
Control: tag -1 +pending On Thu, Jan 19, 2017 at 12:40 PM, russm-debian-bugswrote: > Source: linux > Version: 4.9.2-2 > Severity: wishlist > Tags: patch > > Dear Maintainer, > > Please enable CONFIG_TOUCHSCREEN_GOODIX, for use on devices that have > this touchscreen hardware installed. Added, and will be applied on next debian kernel release. Thanks for your contribution! Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1
Processed: Re: Bug#851821: linux: Please enable CONFIG_TOUCHSCREEN_GOODIX
Processing control commands: > tag -1 +pending Bug #851821 [src:linux] linux: Please enable CONFIG_TOUCHSCREEN_GOODIX Added tag(s) pending. -- 851821: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems