Moving Linux kernel to 4.19

[cjan]

update to .37, no audio device found?

[dom]

update to .37, no audio device found?

Are you talking about the built in audio (hdmi/headphone socket)? (rather than USB/I2S).

Code: Select all

[email protected]:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
  Subdevices: 7/7
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
  Subdevice #4: subdevice #4
  Subdevice #5: subdevice #5
  Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
[email protected]:~ $ uname -a
Linux domnfs 4.19.37-v7+ #1214 SMP Tue Apr 30 17:20:43 BST 2019 armv7l GNU/Linux

Seems to be here for me.

Do you have dtparam=audio=on in config.txt?

[cjan]

update to .37, no audio device found?

Do you have dtparam=audio=on in config.txt?

yes, and aplay -l
ps. Rpi2

Code: Select all

aplay: device_list:270: no soundcards found...

[dom]

@cjan Can you test again after an rpi-update?

[cjan]

@cjan Can you test again after an rpi-update?

done, thanks.

[MattLate]

Had same audio issue, rpi-update this morning to 4.19.37-v7+ has fixed it. Thanks for the fast response!

[raspberrycake128]

I'd like to report a regression reguarding the kernel module snd_bcm2835, because today I updated to it using the rpi-update tool (which I didn't know any better than that is a test update tool), and that failed to load properly or something, and I wasn't able to get any sound at all, and anything that I used would say things like "No ALSA device found" "*** no soundcards found***", and something about invalid parameters. And when I thought it was the rpi-update tool, I looked up how to revert to previous kernel version, and before it was too late, it had hit me in the head that rpi-update was to blame for my troubles, and that it is pretty much for testing purposes only. So using the --reinstall command of apt, I was able to get back to the stable kernel version, restart, and my old buddy snd_bcm2835 was alive once more.

One things for sure though: I don't think I will ever touch rpi-update for a looong time, and stick with the reccommended sudo apt update and sudo apt upgrade

[ncguk]

As of 1.35pm, 6 May 2019, "sudo rpi-update" gives the error "Invalid git hash specified". Tested on RPi Zero W and RPi3 running stock Raspbian.

[dom]

As of 1.35pm, 6 May 2019, "sudo rpi-update" gives the error "Invalid git hash specified". Tested on RPi Zero W and RPi3 running stock Raspbian.

It's working here. May have been a temporary github issue? Does it still fail?

[jdb]

Github was giving me a whole 300kib/second when cloning today - I would guess they are having internal issues.

[andrum99]

Github was definitely having trouble earlier. The website was giving me unicorns - a minor improvement on the standard HTTP 500 error most websites give in this situation.

[ncguk]

Apologies for the delay in replying. As of this post I'm still receiving the "Invalid git hash specified" message. If no-one else is having the problem, I can only assume something's wonky at my end.

[MrEngman]

Apologies for the delay in replying. As of this post I'm still receiving the "Invalid git hash specified" message. If no-one else is having the problem, I can only assume something's wonky at my end.

I got this error when using rpi-update to update to kernel 4.19.37-v7+ #1215, but shortly after the kernel was updated to 4.19.37-v7+ #1216 and running rpi-update again and it ran OK without the git hash error.

Running rpi-update today updating to kernel 4.19.40-v7+ #1217 and again ran OK without the git hash error.

MrEngman

[ncguk]

Problem solved. Something in my Pi-hole blocklists was causing the problem. Temporarily disabling them caused rpi-update to start working again.

[GizmoGremlin321]

Problem solved. Something in my Pi-hole blocklists was causing the problem. Temporarily disabling them caused rpi-update to start working again.

I found this to be my problem as well. I didn't find anythng blocked in the query log.

[amsterbond]

Thank you guys for suggesting Pi-Hole as the problem, in my query log the following site was blocked in A (ipv4) and AAAA (ipv6) too: codeload.github.com after whitelisted from query log the problem solved (at least in my case). Thank you again, and regards

[ncguk]

Thank you guys for suggesting Pi-Hole as the problem, in my query log the following site was blocked in A (ipv4) and AAAA (ipv6) too: codeload.github.com after whitelisted from query log the problem solved (at least in my case). Thank you again, and regards

I can also confirm that whitelisting codeload.github.com and www.codeload.github.com in Pi-hole enables rpi-update to fetch updated firmware.

[parsingblind]

After upgrading to kernel 4.19, I'm having sound issues in the GUI. (As background, I'm blind, so I use espeakup, speech-dispatcher and orca to get speech in the console and desktop.)

Sound is much more delayed in the console than it was with 4.14, and in the GUI (really, when using PulseAudio), all I hear is a loud buzzing sound.
(Try installing speech-dispatcher and running spd-say "Hello world") as an example).

If there's any more information I can provide to help debug this, I'm all ears.

[Chimneyfactory]

I'm also having audio (and maybe video) issues too.

I've got the 4.19 kernel as updated by apt-get upgrade.

Since the upgrade, HDMI audio is intermittently choppy or distorted in strange ways.

Video playback in VLC also seems choppy or more sluggish, although CPU load is low.

I've a Pi 3B+, with Raspbian installed on an external SSD. It has a large swap file on there, and with this setup I can use it as a desktop computer quite reasonably - even having lots of tabs open in Chrome. It's more responsive than a friend's Windows 10 laptop

I *even* use it for very light video editing, using OpenShot.

Since the update to 4.19, playback of video in Openshot is choppy, and there is occasional sound dropout that wasn't there before.
Playback of MP3's in VLC also has occasional dropout.

Using x-rdp to connect to a Windows computer, the sound comes across very distorted and weird sounding - this was fine (and remarkably usable) in the past.

Is it possible for me to roll back to the previous kernel, to confirm if these problems go away?

Code: Select all

[email protected]:~ $ uname -a
Linux desk 4.19.42-v7+ #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l GNU/Linux

All the above issues have occurred in the last couple of days.

Thanks

[exobuzz]

Not directly related to the kernel update, but just a heads up that your mirror 93.93.128.130 doesn't seem to have updated or has an issue so if that mirror is chosen users will get 404s on the packages.

[DirkS]

Not directly related to the kernel update, but just a heads up that your mirror 93.93.128.130 doesn't seem to have updated or has an issue so if that mirror is chosen users will get 404s on the packages.

Updated with what? The development kernels as discussed here are not on any mirrors AFAIAA
Are you talking about Raspbian mirrors used for regular update/upgrade? If that's the case then you should report it in the Raspbian section if the forum.

[Chimneyfactory]

I'm also having audio (and maybe video) issues too.

I've got the 4.19 kernel as updated by apt-get upgrade.

Since the upgrade, HDMI audio is intermittently choppy or distorted in strange ways.

[...]

To clarify : the above is regarding the kernel that was officially released via apt-get upgrade, not one installed via rpi-update.

I rolled back to what I think was the previous Kernel / firmware release, thus :

Code: Select all

sudo rpi-update a08ece3d48c3c40bf1b501772af9933249c11c5b

giving me

Code: Select all

uname -a
Linux desk 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux

and the audio issues of choppiness and strange sounds have gone, everything is good again.

Thanks

[exobuzz]

Not directly related to the kernel update, but just a heads up that your mirror 93.93.128.130 doesn't seem to have updated or has an issue so if that mirror is chosen users will get 404s on the packages.

Updated with what? The development kernels as discussed here are not on any mirrors AFAIAA
Are you talking about Raspbian mirrors used for regular update/upgrade? If that's the case then you should report it in the Raspbian section if the forum.

the 4.19 kernel is in the repositories now.

[girante]

Since today I am having issues with accessing i2c channel 0, which I fixed by rolling back to kernel 4.14, as suggested by Chimneyfactory (Thanks!)

To clarify : the above is regarding the kernel that was officially released via apt-get upgrade, not one installed via rpi-update.

I rolled back to what I think was the previous Kernel / firmware release, thus :

Code: Select all

sudo rpi-update a08ece3d48c3c40bf1b501772af9933249c11c5b

giving me

Code: Select all

uname -a
Linux desk 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l GNU/Linux

But this is not a long-term solution and it would be nice to be able to, at some point in time, keep up with the latest stable release...

Best regards,
Ricardo

[dom]

Since today I am having issues with accessing i2c channel 0, which I fixed by rolling back to kernel 4.14, as suggested by Chimneyfactory (Thanks!)

Can you create an issue here: https://github.com/raspberrypi/linux/issues
and describe the minimum steps you need to do to see the problem with 4.19 vs 4.14.