Yes, tried an unsigned kernel of [0] (linux-image-unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb with linux-modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb) and it shows exactly the same behaviour as cosmic's default kernel.
Forgot to mention: w_scan closes with error message
"ERROR: Sorry - i couldn't get any working frequency/transponder
Nothing to scan!!"
Unfortunately the Debian installation where everything went fine was on the same SSD I installed Ubuntu, now. So, I can't verify if the firmware I used there was exactly the same. On the other hand, 4.15 (kind of) works with ubuntu cosmic, so, IMHO and speaking as a layman this looks like a regression to me…
Yes, tried an unsigned kernel of [0] (linux- image-unsigned- 4.19.0- 041900- generic_ 4.19.0- 041900. 201810221809_ amd64.deb with linux-modules- 4.19.0- 041900- generic_ 4.19.0- 041900. 201810221809_ amd64.deb) and it shows exactly the same behaviour as cosmic's default kernel.
Forgot to mention: w_scan closes with error message transponder
"ERROR: Sorry - i couldn't get any working frequency/
Nothing to scan!!"
Unfortunately the Debian installation where everything went fine was on the same SSD I installed Ubuntu, now. So, I can't verify if the firmware I used there was exactly the same. On the other hand, 4.15 (kind of) works with ubuntu cosmic, so, IMHO and speaking as a layman this looks like a regression to me…