dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5227
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Moving Linux kernel to 4.19

Tue Oct 16, 2018 7:45 pm

We are planning to move to the 4.19 kernel in the near future (perhaps a few months).
One advantage is there is more raspberry pi specific support in the newer upstream kernels which reduces the number of downstream raspberry pi patches and so reduces maintenance effort.
The 4.19 kernel is planned to be an LTS kernel (long term support).

Obviously a newer kernel will bring additional kernel features and support for more devices (e.g. USB devices like wifi and dvb).
You can read up on what appeared in 4.15, 4.16 ,4.17, 4.18 and 4.19.

We will do this in a few stages. Starting now, we are updating the "next" firmware branch to the 4.18 kernel.
When the 4.19 kernel leaves release candidate stage we'll switch to 4.19. (Currently on rc8 so should be soon).

Assuming testing is positive, we'll update the master rpi-update firmware branch.
Eventually the 4.19 kernel will appear with "apt upgrade" and on new raspbian images in the future.

The 4.18 kernel has been used in LibreELEC nightly builds for a while (and there are weekly test build of the release candidate version of 4.19).

Update with:

Code: Select all

sudo rpi-update
and reboot. Ideally nothing much will change.
Please report if there are any regressions compared to the 4.14 kernel.

Obviously this release is for testers who like to live on the bleeding edge. It's not intended for beginners, or users who need stability.
Backing up is always advisable. There may be regressions. There may be improvements. But we won't know without testers trying it and reporting back.


EDIT: we are now on the 4.19 tree as upstream kernel has left release candidate stage.
EDIT2: we have now updated master branch of rpi-update to the 4.19 kernel

cjan
Posts: 694
Joined: Sun May 06, 2012 12:00 am

Re: Moving Linux kernel to 4.19

Tue Oct 16, 2018 8:52 pm

since raspbian blacklist rtl8192cu module by default, so use 8192cu and all good.
with 4.18, 8192cu loaded but don't connect anymore.
ps. Edimax EW-7811Un

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5227
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Moving Linux kernel to 4.19

Tue Oct 16, 2018 9:17 pm

cjan wrote:
Tue Oct 16, 2018 8:52 pm
since raspbian blacklist rtl8192cu module by default, so use 8192cu and all good.
with 4.18, 8192cu loaded but don't connect anymore.
ps. Edimax EW-7811Un
To confirm, you have been using the out of tree 8192cu driver on 4.14 (with rtl8192cu blacklisted), but this isn't working on 4.18?
What happens if you blacklist 8192cu and try using the upstream driver? Does that work for you?
(There may have been improvements to upstream driver since 4.14).

cjan
Posts: 694
Joined: Sun May 06, 2012 12:00 am

Re: Moving Linux kernel to 4.19

Tue Oct 16, 2018 9:45 pm

yes, rtl8192cu work with both 4.14 & 4.18.
but didn't like it, cause led indicator not blink, want 8192cu back.

MrEngman
Posts: 3778
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: Moving Linux kernel to 4.19

Tue Oct 16, 2018 11:25 pm

Updated the clone of Linux source to include the new kernel source 4.18.14+ to check and update the wifi drivers I compile to run on kernel 4.18.

However, I am unable to configure the kernel so I can compile the drivers as make modules_prepare fails with an error I'm having problems fixing. Initially had issues re bison and flex but installing bison and flex sorted those and the kernel configuration now runs but terminates with an error.

I'm configuring the kernel using commands

Code: Select all

make mrproper
make bcmrpi_defconfig
make modules prepare
for armv6 and

Code: Select all

make mrproper
make bcm2709_defconfig
make modules_prepare
for armv7.

make modules_prepare initially gets a warning

Code: Select all

  CC      arch/arm/kernel/asm-offsets.s
  UPD     include/generated/asm-offsets.h
  CALL    scripts/checksyscalls.sh
<stdin>:1332:2: warning: #warning syscall io_pgetevents not implemented [-Wcpp]
  HOSTCC  scripts/dtc/dtc.o
  HOSTCC  scripts/dtc/flattree.o
  HOSTCC  scripts/dtc/fstree.o
but then the compile fails with this error

Code: Select all

  HOSTCC  scripts/sortextable
  HOSTCC  scripts/asn1_compiler
  HOSTCC  scripts/extract-cert
scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file or directory
 #include <openssl/bio.h>
                         ^
compilation terminated.
scripts/Makefile.host:90: recipe for target 'scripts/extract-cert' failed
make[1]: *** [scripts/extract-cert] Error 1
Makefile:1062: recipe for target 'scripts' failed
make: *** [scripts] Error 2
Checking the linux source there is no file openssl/bio.h, no directory openssl, but there is a file include/linux/bio.h

The file scripts/extract-cert.c includes several references to files in directory openssl but this directory does not exist. e.g.

Code: Select all

#define _GNU_SOURCE
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <stdbool.h>
#include <string.h>
#include <err.h>
#include <openssl/bio.h>
#include <openssl/pem.h>
#include <openssl/err.h>
#include <openssl/engine.h>
Am I missing something or is it that the openssl directory is missing from the kernel source.

Don't know if it is relevant but I'm compiling on a Pi 3B+ with kernel Stretch 4.14.76-v7+ (raspbian-lite)
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

asavah
Posts: 348
Joined: Thu Aug 14, 2014 12:49 am

Re: Moving Linux kernel to 4.19

Wed Oct 17, 2018 12:58 am

Code: Select all

apt install libssl-dev

MrEngman
Posts: 3778
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: Moving Linux kernel to 4.19

Wed Oct 17, 2018 10:14 am

asavah wrote:
Wed Oct 17, 2018 12:58 am

Code: Select all

apt install libssl-dev
Thanks asavah,

That fixed the issue with openssl/bio.h.
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5227
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Moving Linux kernel to 4.19

Thu Oct 18, 2018 7:02 pm

cjan wrote:
Tue Oct 16, 2018 8:52 pm
since raspbian blacklist rtl8192cu module by default, so use 8192cu and all good.
with 4.18, 8192cu loaded but don't connect anymore.
ps. Edimax EW-7811Un
Can you update and try 8192cu again? I've pulled in a few patches that could help.

MrEngman
Posts: 3778
Joined: Fri Feb 03, 2012 2:17 pm
Location: Southampton, UK

Re: Moving Linux kernel to 4.19

Thu Oct 18, 2018 9:28 pm

dom wrote:
Thu Oct 18, 2018 7:02 pm
cjan wrote:
Tue Oct 16, 2018 8:52 pm
since raspbian blacklist rtl8192cu module by default, so use 8192cu and all good.
with 4.18, 8192cu loaded but don't connect anymore.
ps. Edimax EW-7811Un
Can you update and try 8192cu again? I've pulled in a few patches that could help.
Similar issue here. Updated Pi to 4.18.14+ #1151 and 8192cu loaded but no wifi connection. However, updated to the latest raspberrypi/firmware/next, 4.18.14+ #1153, and 8192cu now appears to be working with Edimax EW-7811Un. At least I now have a wifi connection again.
Simplicity is a prerequisite for reliability. Edsger W. Dijkstra

Please post ALL technical questions on the forum. Please Do Not send private messages.

ejolson
Posts: 2748
Joined: Tue Mar 18, 2014 11:47 am

Re: Moving Linux kernel to 4.19

Thu Oct 18, 2018 11:22 pm

dom wrote:
Tue Oct 16, 2018 7:45 pm
We are planning to move to the 4.19 kernel in the near future (perhaps a few months).
One advantage is there is more raspberry pi specific support in the newer upstream kernels which reduces the number of downstream raspberry pi patches and so reduces maintenance effort.
The 4.19 kernel is planned to be an LTS kernel (long term support).
Nice to see the Pi is keeping up to date with latest kernel developments. For me the latest kernel is important for BTRFS.

Between the 4.9.x series and the 4.14.x series there was a regression that prevented the USB Ethernet Gadget from using jumbo packets. More information is in this thread and confirmed here and further analyzed later in the same thread. As a result, I'm currently stuck with 4.9.x series on this Pi Zero cluster.

If this regression is already fixed upstream that's great, otherwise, if there is anyway to fix this regression downstream for the 4.19.x kernels used for Raspbian that would be wonderful.

cjan
Posts: 694
Joined: Sun May 06, 2012 12:00 am

Re: Moving Linux kernel to 4.19

Fri Oct 19, 2018 1:14 am

dom wrote:
Thu Oct 18, 2018 7:02 pm
cjan wrote:
Tue Oct 16, 2018 8:52 pm
since raspbian blacklist rtl8192cu module by default, so use 8192cu and all good.
with 4.18, 8192cu loaded but don't connect anymore.
ps. Edimax EW-7811Un
Can you update and try 8192cu again? I've pulled in a few patches that could help.
back to 8192cu, traffic led blink blink, thanks.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2126
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Moving Linux kernel to 4.19

Fri Oct 19, 2018 5:48 am

ejolson wrote:
Thu Oct 18, 2018 11:22 pm
Between the 4.9.x series and the 4.14.x series there was a regression that prevented the USB Ethernet Gadget from using jumbo packets.
Opening an issue in our GitHub Linux repo is the best way to report regressions like this.

ejolson
Posts: 2748
Joined: Tue Mar 18, 2014 11:47 am

Re: Moving Linux kernel to 4.19

Fri Oct 19, 2018 4:37 pm

PhilE wrote:
Fri Oct 19, 2018 5:48 am
ejolson wrote:
Thu Oct 18, 2018 11:22 pm
Between the 4.9.x series and the 4.14.x series there was a regression that prevented the USB Ethernet Gadget from using jumbo packets.
Opening an issue in our GitHub Linux repo is the best way to report regressions like this.
I see the list of open problems but no way to add anything. How do I do that?

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2126
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Moving Linux kernel to 4.19

Fri Oct 19, 2018 4:38 pm

Click on the green button labelled "New issue".

ejolson
Posts: 2748
Joined: Tue Mar 18, 2014 11:47 am

Re: Moving Linux kernel to 4.19

Fri Oct 19, 2018 5:21 pm

PhilE wrote:
Fri Oct 19, 2018 4:38 pm
Click on the green button labelled "New issue".
It was a not green + sign on the mobile site and then the submit button was placed invisibly under the text entry form because font size was too big. Issue is submitted now. Thanks!

User avatar
DougieLawson
Posts: 35021
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 9:55 am

With 4.18.14-v7+ my Google AIY HAT isn't working on my 3B+

Code: Select all

[    8.072630] voicehat-codec voicehat-codec: property 'voicehat_sdmode_delay' not found default 5 mS
[    8.105174] snd-rpi-simple soc:sound: Unable to allocate GPIO pin
[    8.105194] voicehat-codec voicehat-codec: ASoC: failed to probe component -2
[    8.105244] snd-rpi-simple soc:sound: ASoC: failed to instantiate card -2
[    8.105362] snd-rpi-simple soc:sound: Failed to register card -2
[    8.105396] snd-rpi-simple: probe of soc:sound failed with error -2
I'll give it a reboot and look for those messages again. If it still doesn't work I'll take that one back to 4.14.77-v7+.
Note: Having anything remotely humorous in your signature is completely banned on this forum.

Any DMs sent on Twitter will be answered next month.

This is a hippy & doctor free zone.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2126
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 11:35 am

@Dougie Add "dtdebug=1" to your config.txt, reboot, then post the output of:

Code: Select all

$ sudo vcdbg log msg |& grep -iv hdmi

User avatar
DougieLawson
Posts: 35021
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 2:49 pm

Code: Select all

010478.826: brfs: File read: /mfs/sd/config.txt
010481.610: brfs: File read: 3177 bytes
011192.549: brfs: File read: /mfs/sd/config.txt
011416.128: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
011517.317: *** Restart logging
011517.393: brfs: File read: 3177 bytes
011964.031: brfs: File read: /mfs/sd/cmdline.txt
011964.139: Read command line from file 'cmdline.txt':
011964.206: 'dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=86c71275-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles'
011964.536: brfs: File read: 187 bytes
018116.861: brfs: File read: /mfs/sd/kernel7.img
018116.927: Loading 'kernel7.img' to 0x8000 size 0x4fb038
018131.998: No kernel trailer - assuming DT-capable
018132.071: Trying Device Tree file 'bcm2710-rpi-3-b-plus.dtb'
018132.139: brfs: File read: 5222456 bytes
018480.924: brfs: File read: /mfs/sd/bcm2710-rpi-3-b-plus.dtb
018480.993: Loading 'bcm2710-rpi-3-b-plus.dtb' to 0x503038 size 0x5fb7
018498.378: dtdebug: delete_node(/__local_fixups__)
018508.094: dtdebug: /aliases:i2c_vc=i2c0
018517.803: dtdebug: /__symbols__:i2c_vc=i2c0
018525.136: dtdebug: /__overrides__:i2c_vc=i2c0
018539.131: dtdebug: /__overrides__:i2c_vc_baudrate=i2c0_baudrate
018543.557: dtdebug: /aliases:i2c=i2c1
018553.433: dtdebug: /__symbols__:i2c=i2c1
018560.842: dtdebug: /__overrides__:i2c=i2c1
018565.298: dtdebug: /aliases:i2c_arm=i2c1
018575.259: dtdebug: /__symbols__:i2c_arm=i2c1
018582.687: dtdebug: /__overrides__:i2c_arm=i2c1
018596.927: dtdebug: /__overrides__:i2c_baudrate=i2c1_baudrate
018611.139: dtdebug: /__overrides__:i2c_arm_baudrate=i2c1_baudrate
018617.966: dtparam: uart0_clkrate=48000000
018623.368: dtdebug: /__overrides__ has no uart0_clkrate property
018623.382: Unknown dtparam 'uart0_clkrate' - ignored
018623.448: brfs: File read: 24503 bytes
018879.342: brfs: File read: /mfs/sd/config.txt
018880.176: dterror: not a valid FDT - err -9
018880.188: Failed to load HAT overlay
018880.255: brfs: File read: 3177 bytes
019292.423: dtdebug: Opened overlay file 'overlays/googlevoicehat-soundcard.dtbo'
019332.286: brfs: File read: /mfs/sd/overlays/googlevoicehat-soundcard.dtbo
019350.648: Loaded overlay 'googlevoicehat-soundcard'
019350.721: dtparam: i2s=on
019351.048: dtdebug: /__overrides__ node not found
019356.171: dtdebug: Found override i2s
019356.207: dtdebug:   override i2s: string target 'status'
019365.147: dtdebug: Found fragment 0 (offset 36)
019375.822: dtdebug: merge_fragment(/soc/i2s@7e203000,/fragment@0/__overlay__)
019375.848: dtdebug:   +prop(status)
019377.912: dtdebug: merge_fragment() end
019377.970: dtdebug: Found fragment 1 (offset 112)
019381.053: dtdebug: merge_fragment(/soc/gpio@7e200000,/fragment@1/__overlay__)
019388.566: dtdebug: merge_fragment(/soc/gpio@7e200000/googlevoicehat_pins,/fragment@1/__overlay__/googlevoicehat_pins)
019388.598: dtdebug:   +prop(brcm,pins)
019391.334: dtdebug:   +prop(brcm,function)
019394.087: dtdebug:   +prop(brcm,pull)
019396.859: dtdebug:   +prop(phandle)
019399.584: dtdebug: merge_fragment() end
019399.618: dtdebug: merge_fragment() end
019399.700: dtdebug: Found fragment 2 (offset 260)
019399.918: dtdebug: merge_fragment(/,/fragment@2/__overlay__)
019414.066: dtdebug: merge_fragment(/voicehat-codec,/fragment@2/__overlay__/voicehat-codec)
019414.096: dtdebug:   +prop(#sound-dai-cells)
019417.197: dtdebug:   +prop(compatible)
019420.118: dtdebug:   +prop(pinctrl-names)
019423.209: dtdebug:   +prop(pinctrl-0)
019426.328: dtdebug:   +prop(sdmode-gpios)
019429.944: dtdebug:   +prop(status)
019433.104: dtdebug: merge_fragment() end
019433.139: dtdebug: merge_fragment() end
019433.222: dtdebug: Found fragment 3 (offset 464)
019452.168: dtdebug: merge_fragment(/soc/sound,/fragment@3/__overlay__)
019452.195: dtdebug:   +prop(compatible)
019453.437: dtdebug:   +prop(i2s-controller)
019455.350: dtdebug:   +prop(status)
019456.607: dtdebug: merge_fragment() end
019456.795: brfs: File read: 1259 bytes
019934.268: dtdebug: Failed to open overlay file 'overlays/i2s-mmap.dtbo'
020502.346: dtdebug: Failed to open overlay file 'overlays/i2s-mmap-overlay.dtb'
021070.298: dtdebug: Failed to open overlay file 'overlays/i2s-mmap.dtb'
021070.311: Failed to load overlay 'i2s-mmap'
021071.072: dtparam: spi=on
021076.294: dtdebug: Found override spi
021076.330: dtdebug:   override spi: string target 'status'
021085.785: dtparam: i2c_arm=on
021090.978: dtdebug: Found override i2c_arm
021091.015: dtdebug:   override i2c_arm: string target 'status'
021114.224: dtparam: uart1=off
021119.455: dtdebug: Found override uart1
021119.492: dtdebug:   override uart1: string target 'status'
022297.247: dtparam: cam0-pwdn-ctrl=28
022302.836: dtdebug: /__overrides__ has no cam0-pwdn-ctrl property
022302.852: Unknown dtparam 'cam0-pwdn-ctrl' - ignored
022302.916: dtparam: cam0-pwdn=5
022308.510: dtdebug: /__overrides__ has no cam0-pwdn property
022308.524: Unknown dtparam 'cam0-pwdn' - ignored
022320.144: dtparam: cam0-led-ctrl=28
022325.760: dtdebug: /__overrides__ has no cam0-led-ctrl property
022325.774: Unknown dtparam 'cam0-led-ctrl' - ignored
022325.838: dtparam: cam0-led=6
022331.434: dtdebug: /__overrides__ has no cam0-led property
022331.448: Unknown dtparam 'cam0-led' - ignored
022331.514: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
022331.604: dtparam: arm_freq=1400000000
022337.060: dtdebug: Found override arm_freq
022337.110: dtdebug:   override arm_freq: cell target clock-frequency @ offset 0 (size 4)
022352.083: dtdebug:   override arm_freq: cell target clock-frequency @ offset 0 (size 4)
022367.217: dtdebug:   override arm_freq: cell target clock-frequency @ offset 0 (size 4)
022382.377: dtdebug:   override arm_freq: cell target clock-frequency @ offset 0 (size 4)
022397.629: dtparam: core_freq=400000000
022403.244: dtdebug: /__overrides__ has no core_freq property
022403.256: Unknown dtparam 'core_freq' - ignored
022415.719: dtdebug: delete_node(/hat)
022460.246: Device tree loaded to 0x2eff9900 (size 0x6631)
024872.861: vchiq_core: vchiq_init_state: slot_zero = 0xf7880000, is_master = 1
024882.679: TV service:host side not connected, dropping notification 0x00000002, 0x00000002, 0x00000051
Note: Having anything remotely humorous in your signature is completely banned on this forum.

Any DMs sent on Twitter will be answered next month.

This is a hippy & doctor free zone.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2126
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 3:07 pm

Here's the problem:

Code: Select all

018880.176: dterror: not a valid FDT - err -9
018880.188: Failed to load HAT overlay
The HAT EEPROM is corrupt or not programmed. Try with "dtoverlay=googlevoicehat-soundcard" instead.

User avatar
DougieLawson
Posts: 35021
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 3:18 pm

That's already in my "unified" /boot/config.txt - I use the same config on all of my Raspberries.

Code: Select all

#
# Unified config.txt @ 28/09/2018 21:43
#

[0xe685c936]
# ** Apollo     : e685c936 **
# ** Raspberry Pi Model B Plus Rev 1.2
dtparam=audio=on
dtoverlay=i2c-rtc,ds1307
max_usb_current=1
gpu_mem=16
initramfs initrd.sda followkernel
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=81

[0x7fbb0a6c]
# ** Beaufort   : 7fbb0a6c **
# ** Raspberry Pi 2 Model B Rev 1.1
dtparam=audio=on
dtoverlay=w1-gpio
dtoverlay=i2c-rtc,pcf8523
dtoverlay=i2c-sensor,bmp180
dtoverlay=i2c-sensor,htu21
max_usb_current=1
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=81

[0x8e8dd26c]
# ** Challenger : 8e8dd26c **
# ** Raspberry Pi 3 Model B Rev 1.2
dtparam=audio=on
#start_x=1
lcd_rotate=2

[0x5a67d427]
# ** Eagle      : 5a67d427 **
# ** Raspberry Pi 2 Model B Rev 1.1
dtparam=audio=on
max_usb_current=1
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=81

[0x18ae9924]
# ** Endeavour  : 18ae9924 **
# ** Raspberry Pi 3 Model B Rev 1.2
dtparam=audio=on
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16

[0xebd5f1e8]
# ** Falcon     : ebd5f1e8 **
# ** Raspberry Pi Zero Rev 1.2
dtparam=audio=on
gpu_mem=64
dtparam=act_led_activelow=on
enable_uart=1
dtoverlay=i2c-sensor,bmp180
#dtoverlay=enc28j60,int_pin=25,speed=20000000
#disable_audio_dither=1
#hdmi_force_hotplug=1
#hdmi_group=1
#hdmi_mode=16

[0x3d5fffed]
# ** Gemini     : 3d5fffed **
# ** Raspberry Pi Model B Rev 2
dtparam=audio=on
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=81

[0x3f3cd8c4]
# ** Hitchhiker : 3f3cd8c4 **
# ** Raspberry Pi 3 Model B Plus Rev 1.3
dtoverlay=googlevoicehat-soundcard
dtparam=i2s=on
dtoverlay=i2s-mmap
start_x=1
gpu_mem=128
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=81

[0xed1519f1]
# ** Intrepid   : ed1519f1 **
# ** Raspberry Pi 3 Model B Rev 1.2
dtparam=audio=on
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=81
dtoverlay=rpi-tv

[0xaf84e8d0]
# ** Mercury    : af84e8d0 **
# ** Raspberry Pi Zero W Rev 1.1
dtparam=audio=on
dtparam=act_led_activelow=on
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=31

[0xc2355259]
# ** Odyssey    : c2355259 **
# ** Raspberry Pi Model B Rev 2
dtparam=audio=on
dtoverlay=lirc-rpi,gpio_in_pin=23,gpio_in_pull=high
gpu_mem=128
start_x=1
disable_camera_led=1
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=81

[0x4800069e]
# ** Pioneer    : 4800069e **
# ** Raspberry Pi Model B Rev 2
dtparam=audio=on
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16

[0x9b930691]
# ** Ranger     : 9b930691 **
# ** Raspberry Pi Model B Rev 2
dtparam=audio=on
dtoverlay=rpi-cirrus-wm5102
dtoverlay=i2s-mmap
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16

[0x62144670]
# ** Saturn     : 62144670 **
# ** Raspberry Pi Model B Rev 2
dtparam=audio=on
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16

[0x5b592f7f]
# ** Viking     : 5b592f7f **
# ** Raspberry Pi Model A Plus Rev 1.1
dtparam=audio=on
gpu_mem=16
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=81

[all]
dtparam=spi=on
dtparam=i2c_arm=on
disable_splash=1
dtdebug=1
The 3B+ with the AIY HAT is 0x3f3cd8c4 (machine is Hitchhiker).
Note: Having anything remotely humorous in your signature is completely banned on this forum.

Any DMs sent on Twitter will be answered next month.

This is a hippy & doctor free zone.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2126
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 3:52 pm

The driver treats the GPIO allocation failure as a fatal error. The Voice HAT only uses a single GPIO - GPIO 16 - and I can't think what else would be using it, but you can probably find out with:

Code: Select all

$ raspi-gpio get 16
$ sudo grep 16 /sys/kernel/debug/pinctrl/3f200000.gpio/{pinmux-,}pins

User avatar
DougieLawson
Posts: 35021
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 4:00 pm

This is what I get on 4.14.77-v7+.

Code: Select all

root@hitchhiker:~ # raspi-gpio get 16
GPIO 16: level=1 fsel=1 func=OUTPUT
root@hitchhiker:~ # grep 16 /sys/kernel/debug/pinctrl/3f200000.gpio/{pinmux-,}pins
/sys/kernel/debug/pinctrl/3f200000.gpio/pinmux-pins:pin 16 (gpio16): voicehat-codec pinctrl-bcm2835:16 function gpio_out group gpio16
/sys/kernel/debug/pinctrl/3f200000.gpio/pins:pin 16 (gpio16) function gpio_out in hi; irq 0 (none)
root@hitchhiker:~ #
I'll go back to 4.18.14-v7+, watch this space.

Code: Select all

root@hitchhiker:~ # raspi-gpio get 16
GPIO 16: level=0 fsel=1 func=OUTPUT
root@hitchhiker:~ # grep 16 /sys/kernel/debug/pinctrl/3f200000.gpio/{pinmux-,}pins
grep: /sys/kernel/debug/pinctrl/3f200000.gpio/pinmux-pins: No such file or directory
grep: /sys/kernel/debug/pinctrl/3f200000.gpio/pins: No such file or directory
root@hitchhiker:~ #

Last edited by DougieLawson on Sun Oct 21, 2018 4:17 pm, edited 1 time in total.
Note: Having anything remotely humorous in your signature is completely banned on this forum.

Any DMs sent on Twitter will be answered next month.

This is a hippy & doctor free zone.

PhilE
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2126
Joined: Mon Sep 29, 2014 1:07 pm
Location: Cambridge

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 4:07 pm

When we first started using Device Tree for pin configuration we found an oddity - that GPIOs and pinctrl (pin function selection) intentionally use orthogonal "name spaces"; it is perfectly permissible to use the same pin from both worlds without generating an error. They later added an option to make the checking strict, but this is not enabled by default.

Perhaps something has changed in this regard, but that would surprise me because Milhouse's LibreElec builds have been on 4.18 for some time and many of those users will be using external soundcards with similar overlays, so should have encountered the same problem.

User avatar
DougieLawson
Posts: 35021
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux kernel to 4.19

Sun Oct 21, 2018 4:19 pm

It's also doing lots of bad things with the WiFi

Code: Select all

[   44.152008] FS-Cache: Duplicate cookie detected
[   44.152021] FS-Cache: O-cookie c=7ccc6197 [p=af949622 fl=222 nc=0 na=1]
[   44.152024] FS-Cache: O-cookie d=553028c3 n=84fc5ba4
[   44.152028] FS-Cache: O-key=[10] '0400020008010a0101e6'
[   44.152051] FS-Cache: N-cookie c=7e98e9f7 [p=af949622 fl=2 nc=0 na=1]
[   44.152054] FS-Cache: N-cookie d=553028c3 n=8c044246
[   44.152057] FS-Cache: N-key=[10] '0400020008010a0101e6'
[   50.287568] fuse init (API version 7.27)
[   56.355905] IPv6: ADDRCONF(NETDEV_CHANGE): wlxb827eb698d91: link becomes ready
[  134.125662] brcmfmac: brcmf_run_escan: error (-52)
[  134.125682] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  135.128161] brcmfmac: brcmf_run_escan: error (-52)
[  135.128176] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  136.130315] brcmfmac: brcmf_run_escan: error (-52)
[  136.130326] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
Note: Having anything remotely humorous in your signature is completely banned on this forum.

Any DMs sent on Twitter will be answered next month.

This is a hippy & doctor free zone.

cjan
Posts: 694
Joined: Sun May 06, 2012 12:00 am

Re: Moving Linux kernel to 4.19

Mon Oct 22, 2018 11:39 am

4.19 is out.

Return to “Advanced users”