vincent-
Posts: 1
Joined: Sat Jul 25, 2020 6:21 am

Re: STICKY: Buster bug report thread

Sun Jul 26, 2020 6:47 am

The update of raspberrypi-kernel has broken the installation of v4l2loopback-dkms

---------------------------------------------------

v4l2loopback-dkms-0.12.1-1 (current version in Buster) fails to install because the kernel module fails to build for kernels >= 5.1. This has been fixed upstream, and in fact the v4l2loopback-dkms-0.12.5-1 from Bullseye installs just fine.

The problem was introduced by raspberrypi-kernel-1.20200717-1 which started to ship 5.4 kernels instead of 4.19.

I have reported this on GitHub, but I'm not sure if I did it in the right place.

tombsar
Posts: 46
Joined: Wed May 13, 2020 12:40 am

Re: STICKY: Buster bug report thread

Sun Jul 26, 2020 12:54 pm

Everything worked fine last week, and I check for upgrades every couple of days, so I know it was something that changed very recently that introduced the regression. I see from my apt logs that I got two kernel updates (4.19.118 and 5.4.51) within that timeframe, which seem like obvious candidates for the cause.
beta-tester wrote:
Sun Jul 26, 2020 6:30 am
to up- or downgrade to a specific kernel, use ifs commit hash value:

Code: Select all

sudo rpi-update  e1050e94821a70b2e4c72b318d6c6c968552e9a2  # hash of commit  "kernel: Bump to 4.19.118"
sudo reboot
Thanks for this.

Downgrading to kernel 4.19.115 (87fea11838d706311dc3708d67c334967505a292) returned the system to a working state.

Upgrading to kernel 4.19.118 (e1050e94821a70b2e4c72b318d6c6c968552e9a2) it was still working.

Upgrading to kernel 5.4.51 (6ed953db15f863e1c8962a447307628c48946bf6) it is broken.

So I'm pretty confident this is a kernel issue.

If I may vent my frustration a little, I deliberately stayed away from any beta and/or testing versions of the OS because I wanted a stable development system, so it is rather disappointing that such a regression made it through testing; I can't be the only person to have noticed this problem(?).

Is this likely to get fixed, or is the answer that I should wait until the full kms driver is released? I understand fkms is not being as actively maintained as it used to be.

beta-tester
Posts: 1385
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: STICKY: Buster bug report thread

Sun Jul 26, 2020 1:24 pm

in the initial post on this thread is a list where to report issues officially...
Once bugs are confirmed, you should use the github repo to make an official report.

For Linux kernel issues: https://github.com/raspberrypi/linux/issues
For Firmware issues: https://github.com/raspberrypi/firmware/issues
For Userland issues (demo apps etc) : https://github.com/raspberrypi/userland/issues
For Raspbian issue: TBD
For Desktop issues: TBD
... there is the best chance to get a fix.
(but the developers have their priorities that may not fit with ours :? )
tombsar wrote:
Sun Jul 26, 2020 12:54 pm
Upgrading to kernel 4.19.118 (e1050e94821a70b2e4c72b318d6c6c968552e9a2) it was still working.
Upgrading to kernel 5.4.51 (6ed953db15f863e1c8962a447307628c48946bf6) it is broken.
if you wanna make the developer happy, you can try to find the exact two commits of transition from last working commit to first broken/not-working commit...
in between of 4.19.118 and 5.4.5 there are still some other commits.
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

beta-tester
Posts: 1385
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: STICKY: Buster bug report thread

Wed Aug 12, 2020 7:00 pm

is there a repository on github that contains all the source code of modification/customization that were made to debian packages for Raspberry Pi OS?
i don't mean the repositories for linux kernel, firmware or userland.

for example i am looking for the modifications/customizations on the packages firefox-esr and chromium made for Raspbarry Pi OS.
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

trejan
Posts: 2330
Joined: Tue Jul 02, 2019 2:28 pm

Re: STICKY: Buster bug report thread

Wed Aug 12, 2020 7:10 pm

beta-tester wrote:
Wed Aug 12, 2020 7:00 pm
is there a repository on github that contains all the source code of modification/customization that were made to debian packages for Raspberry Pi OS?
The RPT modified Chromium is at https://github.com/RPi-Distro/chromium-browser but I've no idea where the firefox one is. They've said that not all of the RPT Git repos are public and that the official method to get source is to enable the source repo in /etc/apt/sources.list and retrieve the source packages using "apt source packagenamehere"

beta-tester
Posts: 1385
Joined: Fri Jan 04, 2013 1:57 pm
Location: de_DE

Re: STICKY: Buster bug report thread

Wed Aug 12, 2020 7:24 pm

trejan wrote:
Wed Aug 12, 2020 7:10 pm
beta-tester wrote:
Wed Aug 12, 2020 7:00 pm
is there a repository on github that contains all the source code of modification/customization that were made to debian packages for Raspberry Pi OS?
The RPT modified Chromium is at https://github.com/RPi-Distro/chromium-browser but I've no idea where the firefox one is. They've said that not all of the RPT Git repos are public and that the official method to get source is to enable the source repo in /etc/apt/sources.list and retrieve the source packages using "apt source packagenamehere"
thank you...
i expected that there must be more modified packages available... :?
{ I only give negative feedback }
RPi B (256MB), B (512MB), B+, ZeroW; 2B; 3B, 3B+; 4B (4GB)

trejan
Posts: 2330
Joined: Tue Jul 02, 2019 2:28 pm

Re: STICKY: Buster bug report thread

Wed Aug 12, 2020 7:25 pm

beta-tester wrote:
Wed Aug 12, 2020 7:24 pm
i expected that there must be more modified packages available... :?
You'll have to use "apt source" to get those.

fruitoftheloom
Posts: 23875
Joined: Tue Mar 25, 2014 12:40 pm
Location: Delightful Dorset

Re: STICKY: Buster bug report thread

Wed Aug 12, 2020 7:29 pm

beta-tester wrote:
Wed Aug 12, 2020 7:00 pm
is there a repository on github that contains all the source code of modification/customization that were made to debian packages for Raspberry Pi OS?
i don't mean the repositories for linux kernel, firmware or userland.

for example i am looking for the modifications/customizations on the packages firefox-esr and chromium made for Raspbarry Pi OS.


AFAIAA

chromium-browser is where all the development has been undertaken.

firefox-esr is just a standard Debian Package.
Rather than negativity think outside the box !
RPi 4B 4GB (SSD Boot) RaspiOS64 ARM64
Asus ChromeBox 3 Celeron is my other computer...

max11
Posts: 50
Joined: Tue May 14, 2019 12:48 pm

Re: STICKY: Buster bug report thread

Thu Sep 10, 2020 12:42 am

I finally installed Raspian Buster after being a happy user with Stretch.

Version is buster, kernel: Linux 5.4.51-v7+ Kodi Leia 18.7

My Problem is the DVB-C/T2 Astrometa Stick, which is as far as i can see, running fine (after solving the wellknown problems with the frontends)

Driver is 'dvb-demod-mn88473-01.fw'
Tvheadend shows the two adapters DVB-T2 and DVB-C.

If i try to scan nothing happens. Scan hangs and fails.

Connecting the adapter to the board this is shown in dmesg:

pi@raspberrypi:~ $ dmesg
[ 358.997308] usb 1-1.2.3: new high-speed USB device number 9 using dwc_otg
[ 359.237320] usb 1-1.2.3: New USB device found, idVendor=15f4, idProduct=0131, bcdDevice= 1.00
[ 359.237341] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 359.237350] usb 1-1.2.3: Product: dvbt2
[ 359.237360] usb 1-1.2.3: Manufacturer: astrometadvbt2
[ 359.245008] usb 1-1.2.3: dvb_usb_v2: found a 'Astrometa DVB-T2' in warm state
[ 359.324391] usb 1-1.2.3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 359.324438] dvbdev: DVB: registering new adapter (Astrometa DVB-T2)
[ 359.354343] i2c i2c-3: Added multiplexed i2c bus 4
[ 359.354361] rtl2832 3-0010: Realtek RTL2832 successfully attached
[ 359.374115] mn88473 3-0018: Panasonic MN88473 successfully identified
[ 359.374197] usb 1-1.2.3: DVB: registering adapter 5 frontend 0 (Realtek RTL2832 (DVB-T))...
[ 359.374405] usb 1-1.2.3: DVB: registering adapter 5 frontend 1 (Panasonic MN88473)...
[ 359.374642] r820t 4-003a: creating new instance
[ 359.381499] r820t 4-003a: Rafael Micro r820t successfully identified
[ 359.381557] r820t 4-003a: attaching existing instance
[ 359.386376] r820t 4-003a: Rafael Micro r820t successfully identified
[ 359.409249] Registered IR keymap rc-empty
[ 359.409422] rc rc0: Astrometa DVB-T2 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.3/rc/rc0
[ 359.409671] rc rc0: lirc_dev: driver dvb_usb_rtl28xxu registered at minor = 0, raw IR receiver, no transmitter
[ 359.409887] input: Astrometa DVB-T2 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.3/rc/rc0/input12
[ 359.410297] usb 1-1.2.3: dvb_usb_v2: schedule remote query interval to 200 msecs
[ 359.418328] usb 1-1.2.3: dvb_usb_v2: 'Astrometa DVB-T2' successfully initialized and connected
pi@raspberrypi:~ $


With Raspbian Linux 9 (stretch) (kernel: Linux 4.19.66-v/+) and Kodi 18.2 (newer versions aren't available) everything is working fine..

Edit: Don't ask me why, but after disconnecting and reconnecting several times as well as rebooting and restarting Tvheadend several times now all of a sudden the system is recocognized.. scan is working ....

Edit2: It seems to have been a lucky failure, that i was able to scan.... :-( Maybe it worked as i took a backup from a working system (with a Terratec-adapter) and TVheadend didn't realize it in the first moment as both were on the same cable/same networks/same muxes/same services ....

After a reboot TVheadend is not finding anything ... scan pending ... and then fail ...
So let me resume:

The astrometa adapter is working fine with Raspbian stretch
It is recognized under Buster ... it is enabled ....but doesn't work with Buster, only with Stretch.

This seems to be a bug,
Any ideas?

My adapter is not any more scanned

Return to “Raspberry Pi OS”