Bug#990127: mt76x0 crashes repeatedly
reassign 990127 linux 4.19.181-1 tags 990127 moreinfo stop > Package: firmware-misc-nonfree > Version: 20190114-2 > kernel module: mt76x0 The firmware did not change for ages, hence reassigning to linux. > Following an update recently, this driver stopped working correctly. I can > now only get a working WiFi connection for a few seconds after reboot, or > after waiting several minutes, making anything that requires the internet > almost impossible. This was working fine until the update. the Linux version in buster you are using is outdated, there exists 4.19.194-3 and in buster backports 5.10.46-4~bpo10+1. > Once the interface is up, the driver crashes almost immediately. It does > not matter whether I use NetworkManager or do things manually with > /etc/network/interfaces and then ifup. please try to reproduce with up to date kernel, thank you.
Bug#989087: rtw_8822ce: firmware crash
tags 989087 moreinfo stop the updated firmware got into 20210716 verison, which is included in latest unstable package. Could you please test it out if it improves your situation? thank you. -- maks
Bug#987116: firmware-iwlwifi: AX20* bluetooth random disconnects
On Thu, Jun 17, 2021 at 03:25:11PM +0200, Maxime Brugidou wrote: > Arch users found that the more recent firmware fixes the issue > > See https://bbs.archlinux.org/viewtopic.php?id=263040=4 > Firmware has been updated on 2021-04-26 > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=fa0efeff4894e36b9c3964376f2c99fae101d147 > > This firmware version is not available yet on firmware-iwlwifi package This morning I uploaded to unstable the newer 20210427-1 Could you try it out? signature.asc Description: PGP signature
Bug#991943: klibc: please consider including machine-readable copyright file
On Wed, Aug 11, 2021 at 02:40:20PM +0200, Andrej Shadura wrote: > On 11/08/2021 14:30, Andrej Shadura wrote: > > On Fri, 06 Aug 2021 14:31:26 +0200 Andrej Shadura > > wrote: > >> Please consider including the attached machine-readable copyright file. > >> I tried to make it as precise as I can based on the information in the > >> source and accompanying text files; improve it as you see fit. > > > > I’ve noticed a few issues with the proposed copyright file. I have fixed > > them; please find the attached patch to the packaging. > > Of course, once again I’ve forgotten something: > > Files: debian/* > Copyright: > 2005 Jeff Bailey > 2005-2014 maximilian attems > 2015-2021 Ben Hutchings > > I’m not sure what the license of the packaging is. please use whatever is canonical, I'm fine with GPL as well as BSD, as it is mostly glue to just bring things to the enduser. please use this email adress of mine, thank you. also the patch should be submitted to klibc upstream ;)
Bug#986151: please unblock firmware-nonfree 20210315-2
Package: release.debian.org Thanks For latest amd gpu support and newer iwlwifi firmware. Please find attached the source diff, which is mainly removal from upstreamed patches in 20210208-4. There are two known issues, which have no known upstream fix yet: 1) Raspberry Pi 4 5 Ghz failure #985632 (new cypress firmware regression, old brcm worked, raspberry pi distro has a newer firmware that is not pushed upstream yet) 3) iwlwifi still behaves like a bad boy in several setups #963025 thank you for giving it a pass into testing after 10d (: warm greetings! diff --git a/debian/changelog b/debian/changelog index 5dfb071..ef12a05 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,41 @@ +firmware-nonfree (20210315-2) unstable; urgency=medium + + * Support Cubietech Cubietruck and Jumper EZpad mini 3 tablet +(closes: #985740, #844056) + * Add firmware-atheros recommends to firmware-qcom-soc (closes: #985743) +Thanks to Andreas Beckmann + * Add missing brcmfmac4366c firmware. + * Add more missing BCM4334, BCM43340 and BCM43430 NVRAMS. + + -- maximilian attems Sat, 27 Mar 2021 13:03:31 +0100 + +firmware-nonfree (20210315-1) unstable; urgency=medium + + * Unstable upload of green sardine support (closes: #984874) + + -- maximilian attems Sat, 20 Mar 2021 19:14:23 +0100 + +firmware-nonfree (20210315-1~exp1) experimental; urgency=medium + + * New upstream version: +- rtw88: RTL8822C: Update normal firmware to v9.9.5 (closes: #983255) +- amdgpu: add initial firmware for green sardine (closes: #984852) +- silabs: add new firmware for WF200 +- brcm: Fix Raspberry Pi 4B NVRAM file +- Add symlink for BananaPi M2 to brcmfmac43430-sdio config +- WHENCE: add missing symlink for BananaPi M3 +- rtw89: 8852a: add firmware v0.9.12.2 +- linux-firmware: add frimware for mediatek bluetooth chip (MT7921) +- iwlwifi: update 7265D firmware +- iwlwifi: update 9000-family firmwares (closes: #963025) +- iwlwifi: add new FWs from core59-66 release +- rtw88: 8822c: Update normal firmware to v9.9.6 +- linux-firmware: Update firmware file for Intel Bluetooth AX201 +- linux-firmware: Update firmware file for Intel Bluetooth AX200 +- linux-firmware: Update firmware file for Intel Bluetooth AX210 + + -- maximilian attems Tue, 16 Mar 2021 16:56:56 +0100 + firmware-nonfree (20210208-4) unstable; urgency=medium * List MediaTek mt8183 firmware. diff --git a/debian/config/amd-graphics/defines b/debian/config/amd-graphics/defines index 0027f0d..e86494b 100644 --- a/debian/config/amd-graphics/defines +++ b/debian/config/amd-graphics/defines @@ -39,6 +39,17 @@ files: amdgpu/fiji_smc.bin amdgpu/fiji_uvd.bin amdgpu/fiji_vce.bin + amdgpu/green_sardine_asd.bin + amdgpu/green_sardine_ce.bin + amdgpu/green_sardine_dmcub.bin + amdgpu/green_sardine_me.bin + amdgpu/green_sardine_mec2.bin + amdgpu/green_sardine_mec.bin + amdgpu/green_sardine_pfp.bin + amdgpu/green_sardine_rlc.bin + amdgpu/green_sardine_sdma.bin + amdgpu/green_sardine_ta.bin + amdgpu/green_sardine_vcn.bin amdgpu/hainan_ce.bin amdgpu/hainan_k_smc.bin amdgpu/hainan_mc.bin @@ -731,6 +742,39 @@ version: 1.87.12 [amdgpu/fiji_vce.bin_base] desc: "Fiji" VCE firmware +[amdgpu/green_sardine_asd.bin_base] +desc: AMD RYZEN 5000 ASD firmware + +[amdgpu/green_sardine_ce.bin_base] +desc: AMD RYZEN 5000 CE firmware + +[amdgpu/green_sardine_dmcub.bin_base] +desc: AMD RYZEN 5000 DMCUB firmware + +[amdgpu/green_sardine_me.bin_base] +desc: AMD RYZEN 5000 ME firmware + +[amdgpu/green_sardine_mec2.bin_base] +desc: AMD RYZEN 5000 MEC2 firmware + +[amdgpu/green_sardine_mec.bin_base] +desc: AMD RYZEN 5000 MEC firmware + +[amdgpu/green_sardine_pfp.bin_base] +desc: AMD RYZEN 5000 PFP firmware + +[amdgpu/green_sardine_rlc.bin_base] +desc: AMD RYZEN 5000 RLC firmware + +[amdgpu/green_sardine_sdma.bin_base] +desc: AMD RYZEN 5000 SDMA firmware + +[amdgpu/green_sardine_ta.bin_base] +desc: AMD RYZEN 5000 TA firmware + +[amdgpu/green_sardine_vcn.bin_base] +desc: AMD RYZEN 5000 VCN firmware + [amdgpu/hainan_ce.bin_base] desc: Radeon HD 8500M series and R5 M200 CE microcode diff --git a/debian/config/brcm80211/defines b/debian/config/brcm80211/defines index ddba14d..522b4eb 100644 --- a/debian/config/brcm80211/defines +++ b/debian/config/brcm80211/defines @@ -14,11 +14,16 @@ files: brcm/brcmfmac43242a.bin brcm/brcmfmac4329-sdio.bin brcm/brcmfmac4330-sdio.bin + brcm/brcmfmac4330-sdio.Prowise-PT301.txt + brcm/brcmfmac43340-sdio.meegopad-t08.txt + brcm/brcmfmac43340-sdio.pov-tab-p1006w-data.txt brcm/brcmfmac4334-sdio.bin brcm/brcmfmac4335-sdio.bin brcm/brcmfmac43340-sdio.bin brcm/brcmfmac43362-sdio.bin + brcm/brcmfmac43362-sdio.cubietech,cubietruck.txt brcm/brcmfmac43362-sdio.lemaker,bananapro.txt + brcm/brcmfmac43430a0-sdio.jumper-ezpad-mini3.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt brcm/brcmfmac43430-sdio.si
Bug#963025: fixed in firmware-nonfree 20210315-1~exp1
reopen 963025 found -1 20210315-2 tags -1 moreinfo stop > [18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: GW > 5.10.0-5-amd64 #1 Debian 5.10.24-1 > [18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS N2IET81W > (1.59 ) 11/29/2019 Please could you upgrade the BIOS to latest for T490, 1.72 2021/03/17 to exclude this guy fault.
Bug#772917: iwlwifi: iwl4965 crashes when network usage is intense
tags 772917 moreinfo stop > [584941.834142] iwl4965 :03:00.0: Loaded firmware version: 228.61.2.24 Can you reproduce this with an up to date debian testing? thank you.
Bug#885958: hostapd: iwlwifi 5GHz hw_mode=a causes microcode fault
tags 885958 moreinfo stop > [51085.431413] iwlwifi :03:00.0: Loaded firmware version: 29.541020.0 Can you reproduce this with up to date Debian testing? thank you for your report.
Bug#969264: firmware-iwlwifi:
tags 969264 moreinfo stop > Version: 20200721-1 > Wi-Fi connection has been behaving erratically, lots of lags - for > instance - in LAN-SSH connections. > $ lspci | grep "Network controller" > 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 > [Taylor Peak] (rev 34) Is this reproducible with current Debian testing? thank you for your report.
Bug#839662: [firmware-atheros] ath10k_pci firmware crashes when ap changes bandwith
tags 839662 moreinfo stop > The same problem here with firmware-atheros version 20170823-1~bpo9+1 > and kernel 4.14.0-2-amd64. > It's a dell xps 13 8th gen, with a: Is this reproducible with an up to date Debian Testing? Sorry for the late reply and thank you for the reports.
Bug#920937: firmware-atheros: Firmware QCA6174 crashes on wakeup from suspend
> I seem to have the same problem with version 20190717 (debian testing > 5.4.13-1 amd64). How about firmware 20210208-4, which should have an upgrade and latest linux in Debian Bullseye? thanks for your reports.
Bug#973529: firmware-atheros: Link wifi rate limited at 1MB/s
tags 973529 moreinfo stop > Version: 20200918-1 How about latest Debian testing version, is that still the case? thank you.
Bug#985627: firmware-linux-free: firmware....ver imagen
reassign 985627 firmware-iwlwifi tags 985627 moreinfo stop Buenas tardes, La imagen no dice mucho, cual es la version de Debian? (y de firmware-iwlwifi) cuando funcionó? Ademas la error esta reproducible?
Bug#921004: AMD Radeon RX 580: no GL display, "amdgpu: The CS has been cancelled because the context is lost"
tags 921004 moreinfo stop can you still reproduce this trouble with uptodate Debian 11 Testing? thank you for your report and sorry for the late reply.
Bug#802937: firmware-linux-nonfree: radeon tahiti firmware fails to load
tags 802937 moreinfo stop > Several months ago I got a new case that allowed me to reinstall the > graphics card. The old case wasn't big enough to accommodate the card + > the disk drives so I used an older, shorter card. Can you reproduce with uptodate Debian bullseye? sorry for the late reply and thank you for your report.
Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine
Dear Ryutaroh, > It is Raspberry Pi 4B 8GB model. I see thank you for all the dmesg. > > please show affected dmesg output working and non working, > > the difference between 20210208-3 20210208-4 is minimal, > > hence it should be easy to find out what broke? > > Not at all, unfortunately. > 20210208-3 was completely broken on RPi4B as > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984489 > 20210208-1 to 20210208-3 were broken... > The last working version was 20201218-3, and I apt-mark-holded > firmware-brcm80211. > I unhold it in the weekend and found this issue. please excuse my ignorance first, but are you sure that these bootflags are still adequate for the latest cypress firmware? concerning bluetooth unfortunately this seems missing firmware in latest upstream firmware git (see #962038 ) or possible wget info https://wiki.debian.org/RaspberryPi4#Bluetooth > I attach dmesg of 20201218-3, 20210208-4, and 20210315-1. > It was also interesting that installation of 20210315-1 causes boot failure > and showed "Give root password for maintainance"... > Should I file a separete report against 20210315-1? > 20210315-1~exp1 was booted fine... this should not be reproducible as 20210315-1 and 20210315-1~exp1 are unchanged (just uploaded into experimental before unstable). Thank you for your report! maximilian
Bug#985632: firmware-brcm80211: [REGRESSION] RPi4B 5GHz WiFi stopped working with 20210208-4, 20201218-3 was fine
severity 985632 important tags 985632 moreinfo stop On Sun, Mar 21, 2021 at 09:59:45AM +0900, Ryutaroh Matsumoto wrote: > Package: firmware-brcm80211 > Version: 20210208-4 > Severity: grave > Tags: sid bullseye > Justification: renders package unusable please provide info on the affected hardware, also using apropriate bug levels would be nice. > 5GHz WiFi stopped working with 20210208-4. > iw wlan0 scan does not show SSID of 5GHz WiFi. > With 20201218-3, 5GHz worked fine, > provided that vc4.ko is blacklisted (see #981616). please show affected dmesg output working and non working, the difference between 20210208-3 20210208-4 is minimal, hence it should be easy to find out what broke? thank you for your report + kind regards, signature.asc Description: PGP signature
Bug#913711: firmware-brcm80211: firmware failed to load: NULL pointer dereference with brcmfmac4356
tags 913711 moreinfo stop > Version: 20161130-4 There has been quite some updates since. > latest firmware blobs from linux-firmare git, but only a downgrade to > firmware-brcm80211:20161130-3 allowed the firmware to be correctly > loaded. Is this still reproducible with current Debian Testing (upcoming Bullseye)? Thank you for your report and sorry for the late reply.
Bug#922559: Firmware locks up on Vega 8
tags 922559 moreinfo stop > Version: 20180825+dfsg-1~bpo9+1 Is this still reproducible with current Testing, upcoming bullseye release? If so can you produce the corresponding log? Thank you for your report and sorry for the late reply.
Bug#910272: firmware-amd-graphics: Error raised in amdgpu module
tags 910272 moreinfo stop > Version: 20180825+dfsg-1 > I have HP EliteBook 755 G5, with AMD Ryzen 7 PRO 2700U w/ Radeon Vega > Mobile Is this still reproducible with current Debian Testing? Sorry for the late reply and thank you for the report!
Bug#949973: firmware-realtek: kernel error caught
tags 949973 moreinfo stop > Version: 20190114-2 Can you still reproduce with newest testing? Sorry for the late reply and thank you for your report. -- maks
Bug#942173: firmware-amd-graphics: seg fault with ati picasso grafic card and libqt5 software
tags 942173 moreinfo stop > Version: 20190717-2~bpo10+1 This should have seen quite some updates since, is this still reproducible? Sorry for the late reply, thank you for your report!
Bug#963025: firmware-iwlwifi: Microcode SW error detected / 9000-pu-b0-jf-b0-46.ucode
> Some context: > * the error occured right after laptop boot > * My Wifi setup: AP was forced to use frequency of 5240GHz and offered > 20/40/80MHz channel width. Moving AP to 5180GHz solve the issue. > > My understanding: > It *seems* that iwlwifi could have issues with DFS frequencies, not with > channel width. > My last report was also linked to DFS channels being used. > Moving away from DFS channel solve the issue, at least for me. Upstream says this should be fixed in unstable linux version with latest 20210315 iwlwifi firmare. If not please let us know.
Bug#985306: please unblock firmware-nonfree 20210208-4 upload
Package: release.debian.org
Thanks
please unblock firmware-nonfree 20210208-4
it has minimal differences to 20210208-3:
* fixes Raspberry Pi 4 Wifi firmware loading
* 2 additional symlinks for config files
* adds a missing mediatek firmware
see attached source diff.
As upstream just realeased 20210315, it is planed
to upload that soonish to unstable to push it into testing.
It adds to above newer iwlwifi + intel bluetooth + amd green sardine
hardware support.
thank you.
--
maks
diff --git a/debian/changelog b/debian/changelog
index 6e42b05..5dfb071 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+firmware-nonfree (20210208-4) unstable; urgency=medium
+
+ * List MediaTek mt8183 firmware.
+ * Update to linux-support 5.10.0-4.
+ * Add upstream fix for Raspberry Pi 4B. (closes: #984489)
+ * Support BananaPi M2 ultra and BananaPi M3. (closes: #982579)
+Thanks to Ben Hutchings ,
+ Bernhard
+
+ -- maximilian attems Sat, 13 Mar 2021 13:23:22 +0100
+
firmware-nonfree (20210208-3) unstable; urgency=medium
* misc-nonfree: Add missing config files for cxgb4 (closes: #983561)
diff --git a/debian/config/brcm80211/defines b/debian/config/brcm80211/defines
index bbd9d88..ddba14d 100644
--- a/debian/config/brcm80211/defines
+++ b/debian/config/brcm80211/defines
@@ -21,6 +21,8 @@ files:
brcm/brcmfmac43362-sdio.lemaker,bananapro.txt
brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt
brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt
+ brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt
+ brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt
brcm/brcmfmac4339-sdio.bin
brcm/brcmfmac43430-sdio.bin
brcm/brcmfmac43430-sdio.clm_blob
diff --git a/debian/config/misc-nonfree/defines b/debian/config/misc-nonfree/defines
index 3ae0477..96af121 100644
--- a/debian/config/misc-nonfree/defines
+++ b/debian/config/misc-nonfree/defines
@@ -176,6 +176,7 @@ files:
mediatek/mt7915_rom_patch.bin
mediatek/mt8173/vpu_d.bin
mediatek/mt8173/vpu_p.bin
+ mediatek/mt8183/scp.img
mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin
mediatek/WIFI_RAM_CODE_MT7961_1.bin
moxa/moxa-1110.fw
diff --git a/debian/patches/0001-brcm-Fix-Raspberry-Pi-4B-NVRAM-file.patch b/debian/patches/0001-brcm-Fix-Raspberry-Pi-4B-NVRAM-file.patch
new file mode 100644
index 000..6630b50
--- /dev/null
+++ b/debian/patches/0001-brcm-Fix-Raspberry-Pi-4B-NVRAM-file.patch
@@ -0,0 +1,31 @@
+From 58825f74eb0156822065c449a770644a69044d88 Mon Sep 17 00:00:00 2001
+From: Matthias Brugger
+Date: Tue, 16 Feb 2021 20:35:23 +0100
+Subject: [PATCH 1/6] brcm: Fix Raspberry Pi 4B NVRAM file
+
+NVRAM file set's boarflags3 to 0x48200100 which indicates the firmware
+that an external LPO is present. But on the RPi4 no external LPO exists.
+
+Fixes: 870b805 ("brcm: Update Raspberry Pi 3B+/4B NVRAM for downstream changes")
+Signed-off-by: Matthias Brugger
+Signed-off-by: Josh Boyer
+---
+ brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt b/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
+index d5bd530..8dda168 100644
+--- a/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
b/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt
+@@ -7,7 +7,7 @@ aa5g=1
+ AvVmid_c0=1,165,2,100,2,100,2,100,2,100
+ boardflags=0x00480201
+ boardflags2=0x4080
+-boardflags3=0x48200100
++boardflags3=0x44200100
+ boardrev=0x1304
+ boardtype=0x6e4
+ btc_mode=1
+--
+2.30.1
+
diff --git a/debian/patches/0002-Add-symlink-for-BananaPi-M2-to-brcmfmac43430-sdio-co.patch b/debian/patches/0002-Add-symlink-for-BananaPi-M2-to-brcmfmac43430-sdio-co.patch
new file mode 100644
index 000..ffc9f28
--- /dev/null
+++ b/debian/patches/0002-Add-symlink-for-BananaPi-M2-to-brcmfmac43430-sdio-co.patch
@@ -0,0 +1,34 @@
+From aa6c6e75b44b90bf9e46f3ebed95e25b0ceda8ec Mon Sep 17 00:00:00 2001
+From: maximilian attems
+Date: Tue, 16 Feb 2021 19:44:21 +0100
+Subject: [PATCH 2/6] Add symlink for BananaPi M2 to brcmfmac43430-sdio config
+
+Fixes ( Debian bug #982579 [1]):
+ [ 10.514530] brcmfmac mmc2:0001:1: firmware: direct-loading firmware brcm/brcmfmac43430-sdio.bin
+ [ 10.514732] brcmfmac mmc2:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt ( -2)
+
+Refs:
+[1] https://bugs.debian.org/982579
+
+Reported-by: Bernhard
+Signed-off-by: maximilian attems
+Signed-off-by: Josh Boyer
+---
+ WHENCE | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/WHENCE b/WHENCE
+index aa96404..11c0970 100644
+--- a/WHENCE
b/WHENCE
+@@ -2716,6 +2716,7 @@ File: "brcm/brcmfmac43430a0-sdio.ONDA-V80 PLUS.txt"
+ File: "brcm/brcmfmac43430-sdio.AP6212.txt"
+ Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt -> brcmfmac43430-sdio.AP6212.txt
+ Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt -> brcmfmac43430-sdio.AP6212.txt
++Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt -> brcm
Bug#983255: firmware-realtek: Direct firmware load for rtw88/rtw8821c_fw.bin failed with error -2
tags 983255 moreinfo stop On Tue, Feb 23, 2021 at 09:20:30AM +0100, maximilian attems wrote: > > lspci | grep -i wire > > 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE > > 802.11ac PCIe Wireless Network Adapter > > > > dmesg contains these lines: > > > > [4.938468] rtw_8821ce :02:00.0: Direct firmware load for > > rtw88/rtw8821c_fw.bin failed with error -2 > > [4.938472] rtw_8821ce :02:00.0: failed to request firmware > > [4.938543] rtw_8821ce :02:00.0: failed to load firmware > > [4.938571] rtw_8821ce :02:00.0: failed to setup chip efuse info > > [4.938599] rtw_8821ce :02:00.0: failed to setup chip information > > [4.939514] rtw_8821ce: probe of :02:00.0 failed with error -22 > > > > tried to install also latest firmware-realtek from unstable > > ii firmware-realtek20210208-1 > > all Binary firmware for Realtek wired/wifi/BT adapters > > but this did also not change anything. > > there is a newer version of this firmware v9.9.5 in the upstream repository, > could you test commit 80cb579614ee576ae74e650fa0b43d9f7c212039 > in linux-firmware git: > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Have you tried the newer firmware? -- maks
Bug#984852: firmware-amd-graphics: Please add cezanne ("green sardine")
severity 984852 important tags 984852 pending thanks > Package: firmware-amd-graphics > Version: 20210208-3 > > I've received my new laptop with a Ryzen R7 5800U and the display stopped > updating as soon as amdgpu took over, and it never came back. > The firmware is needed of course, and as a side note, it could be nice if the > kernel could fail more gracefully, somehow bringing the display back (it > works fine with amdgpu blacklisted, just no acceleration) such that it takes > me less than two days to figure it all out. this is a linux bug, you might want to submit it upstream to AMD guys. > The relevant files are amdgpu/green_sardine_* right, they only got pushed upstream in linux-firmware git on 11/2/2021 after the latest 20210208 release, hence unfortunately they miss out the next debian release https://release.debian.org/bullseye/freeze_policy.html They will land in the next upstream release upload of 202103XX to experimental, backports and then after bullseye release to unstable (plus next testing). Thank you for your report! -- maks signature.asc Description: PGP signature
Bug#984834: unblock firmware-nonfree 20210208-3 upload
Package: release.debian.org Thanks please unblock firmware-nonfree 20210208-3 it is the version that has the relevant firmware packages for the targeted version of linux in bullseye. It will need a small amount of fixes on top that are preprared in git and will be uploaded as soon it has migrated. thank you. -- maks signature.asc Description: PGP signature
Bug#980205: #980205 installation missing "non free" drivers.
On Thu, Mar 04, 2021 at 10:08:39AM -0800, Dave Dyer wrote: > > I no longer have the (damaged and useless) installation attempt > that led to this report. I recall that when I succeeded in > supplying brcmfmac43340-sdio.bin, the next installation attempt > presented the same type of error message, asking for brcmfmac43340-sdio.txt missing brcmfmac43340-sdio.txt depends on the device, see for example https://bugs.debian.org/982579 -- snipp > [ 10.534664] brcmfmac mmc2:0001:1: Direct firmware load for > brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt failed with error -2 > [ 10.551207] brcmfmac mmc2:0001:1: firmware: failed to load > brcm/brcmfmac43430-sdio.txt (-2) -- if you have still the device around let us know, otherwise the bug report will closed. > I found a file with that name on github, and there was some evidence > that it worked. I believe it's attacked to the bug report thread. I relooked for it but didn't see the error log message. thank you for your prompt reply. -- maks signature.asc Description: PGP signature
Bug#980205: #980205 installation missing "non free" drivers.
tags 980205 moreinfo thanks > Yes. brcm/brcmfmac43340-sdio.bin is not currently part of the package > either, and I think there's no logic to copy .txt files even if they > are present. The file you mentioned is the ancient firmware that got updated with the cypress one fixing amongst other things (CVE-2019-15126): Link: brcm/brcmfmac43340-sdio.bin -> ../cypress/cyfmac43340-sdio.bin This symlink is inside of firmware-brcm80211_20210208-3_all.deb (shipped in unstable and soon in testing). Now the open question is which configuration file where you missing, could you please post the error message of that? Without the filename/path of the needed config this report will not help to improve the firmware packages. thank you + kind regards -- maks
Bug#984489: firmware-brcm80211: newer versions fail to load on raspberry pi 4b with "brcmf_sdio_htclk: HT Avail timeout"
Dear Andres, > > [ 12.471809] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): > clkctl 0x50 > > > You can specifically see that the driver times out after one second > with that error message, then times out again with the error and gives > up. No wlan0 is available. > > There are some pretty major firmware updates between those two > versions, and they are generally Good. However, there's also some minor > updates to the raspi4 board file > /lib//firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt > > If we revert the line "boardflags3=0x48200100" in that file back to > what was in the 20201218-3 version (so it would instead be > "boardflags3=0x44200100"), and then reboot, the driver now loads: upstream indeed resets this line too, boardflags3=0x44200100 seen in 58825f74eb0156822065c449a770644a69044d88 of linux-firmware.git. > [ 23.961230] br0: port 3(wlan1) entered blocking state > [ 23.963358] br0: port 3(wlan1) entered disabled state > [ 23.966488] device wlan1 entered promiscuous mode > [ 29.417766] br0: port 2(wlan0) entered blocking state > [ 29.419853] br0: port 2(wlan0) entered forwarding state > > > > I'm not sure if the driver needs fixing, or if the boardflags need > fixing, but the boardflags thing seems to be a functional workaround > for users hitting this issue. Thanks to Steev Klimaszewski for helping > me figure out the workaround. I will upload -4 with that fix as soon as -3 finaly hits testing to push that minor change to upcoming release. Thank you for your report! -- maks
Bug#982579: Solution for loading firmware
> Both patches applied and pushed out. great thank you. > In the future, could you please send the patches either as direct > emails or as attachments or as pull requests? When you embed them in > the body of the email I have to manually adjust them to get the commit > log properly included. sure, will do as pull request.
Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others
On Fri, Feb 26, 2021 at 12:17:50PM +0100, Cyril Brulebois wrote: > kibi@tokyo:~/debian-kernel/firmware-nonfree.git$ > ./debian/bin/check_upstream.py | sort | grep 'in any binary package' > I: amd/amd_sev_fam17h_model0xh.sbin is not included in any binary package > I: amd/amd_sev_fam17h_model3xh.sbin is not included in any binary package need to recheck if those are not meant to be in the microcode amd64 guy. > I: cadence/mhdp8546.bin is not included in any binary package hmm > → I: cxgb4/configs/t4-config-default.txt is not included in any binary > package > → I: cxgb4/configs/t5-config-default.txt is not included in any binary > package > I: cxgb4/configs/t5-config-hashfilter.txt is not included in any binary > package > → I: cxgb4/configs/t6-config-default.txt is not included in any binary > package > I: cxgb4/configs/t6-config-hashfilter.txt is not included in any binary > package fixed. > I: inside-secure/eip197_minifw/ifpp.bin is not included in any binary > package > I: inside-secure/eip197_minifw/ipue.bin is not included in any binary > package no idea. > I: intel/dsp_fw_cnl_v1191.bin is not included in any binary package > I: intel/fw_sst_0f28_ssp0.bin is not included in any binary package > I: intel/irci_irci_ecr-master_20161208_0213_20170112_1500.bin is not > included in any binary package > I: iwlwifi-9000-pu-b0-jf-b0-43.ucode is not included in any binary package > I: iwlwifi-9260-th-b0-jf-b0-43.ucode is not included in any binary package will fix soonish. > I: mediatek/mt7622_n9.bin is not included in any binary package > I: mediatek/mt7622_rom_patch.bin is not included in any binary package > I: mediatek/mt8183/scp.img is not included in any binary package hmm. > I: mellanox/mlxsw_spectrum2-29.2000.2308.mfa2 is not included in any > binary package mellanox is kind of excluded irc. > I: meson/vdec/g12a_h264.bin is not included in any binary package > I: meson/vdec/g12a_hevc_mmu.bin is not included in any binary package > I: meson/vdec/g12a_vp9.bin is not included in any binary package > I: meson/vdec/gxbb_h264.bin is not included in any binary package > I: meson/vdec/gxl_h263.bin is not included in any binary package > I: meson/vdec/gxl_h264.bin is not included in any binary package > I: meson/vdec/gxl_hevc.bin is not included in any binary package > I: meson/vdec/gxl_hevc_mmu.bin is not included in any binary package > I: meson/vdec/gxl_mjpeg.bin is not included in any binary package > I: meson/vdec/gxl_mpeg12.bin is not included in any binary package > I: meson/vdec/gxl_mpeg4_5.bin is not included in any binary package > I: meson/vdec/gxl_vp9.bin is not included in any binary package > I: meson/vdec/gxm_h264.bin is not included in any binary package > I: meson/vdec/sm1_hevc_mmu.bin is not included in any binary package > I: meson/vdec/sm1_vp9_mmu.bin is not included in any binary package > I: microchip/mscc_vsc8574_revb_int8051_29e8.bin is not included in any > binary package > I: microchip/mscc_vsc8584_revb_int8051_fb48.bin is not included in any > binary package another hmm > I: qca/nvm_00230302.bin is not included in any binary package > I: qca/nvm_00440302_eu.bin is not included in any binary package > I: qca/nvm_00440302_i2s_eu.bin is not included in any binary package > I: qca/nvm_usb_0302_eu.bin is not included in any binary package those I'll fix too. > I: qed/qed_init_values_zipped-8.37.7.0.bin is not included in any binary > package > I: r8a779x_usb3_v1.dlmem is not included in any binary package > I: r8a779x_usb3_v2.dlmem is not included in any binary package > I: r8a779x_usb3_v3.dlmem is not included in any binary package > I: rtw88/README is not included in any binary package > I: ti-keystone/ks2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin is not included in > any binary package oh well none of those appear to generate much attention. thank you! -- maks signature.asc Description: PGP signature
Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others
On Fri, Feb 26, 2021 at 12:08:55PM +0100, Cyril Brulebois wrote: > > > > Link: cxgb4/t4-config.txt -> configs/t4-config-default.txt > > Link: cxgb4/t5-config.txt -> configs/t5-config-default.txt > > Link: cxgb4/t6-config.txt -> configs/t6-config-default.txt > > debian/config/misc-nonfree/defines looks like it might be missing the > targets of the symlinks (cxgb4/configs/t?-config-default.txt), meaning > the File entries get installed in the build directory through the WHENCE > processing, but those files aren't listed in the FILES variable when > building the binary package, so they don't end up being actually shipped, > hence the broken symlinks? thank you a lot for the prompt look and indeed those config files were not added, updated the repo to fix that in next upload. are there other dangling symlinks besides this three mentioned ones? best, -- maks signature.asc Description: PGP signature
Bug#983561: firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt and others
> Usertags: adequate broken-symlink > X-Debbugs-Cc: t...@mirbsd.de > > firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t4-config.txt -> > configs/t4-config-default.txt > firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t5-config.txt -> > configs/t5-config-default.txt > firmware-misc-nonfree: broken-symlink /lib/firmware/cxgb4/t6-config.txt -> > configs/t6-config-default.txt why is this a broken symlink? this is what upstream wants in WHENCE: Link: cxgb4/t4-config.txt -> configs/t4-config-default.txt Link: cxgb4/t5-config.txt -> configs/t5-config-default.txt Link: cxgb4/t6-config.txt -> configs/t6-config-default.txt -- maks
Bug#983255: firmware-realtek: Direct firmware load for rtw88/rtw8821c_fw.bin failed with error -2
> lspci | grep -i wire > 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE > 802.11ac PCIe Wireless Network Adapter > > dmesg contains these lines: > > [4.938468] rtw_8821ce :02:00.0: Direct firmware load for > rtw88/rtw8821c_fw.bin failed with error -2 > [4.938472] rtw_8821ce :02:00.0: failed to request firmware > [4.938543] rtw_8821ce :02:00.0: failed to load firmware > [4.938571] rtw_8821ce :02:00.0: failed to setup chip efuse info > [4.938599] rtw_8821ce :02:00.0: failed to setup chip information > [4.939514] rtw_8821ce: probe of :02:00.0 failed with error -22 > > tried to install also latest firmware-realtek from unstable > ii firmware-realtek20210208-1 > all Binary firmware for Realtek wired/wifi/BT adapters > but this did also not change anything. there is a newer version of this firmware v9.9.5 in the upstream repository, could you test commit 80cb579614ee576ae74e650fa0b43d9f7c212039 in linux-firmware git: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git It only says "Refine firmware to improve performance." so if it still does not work upstream realtek should be informed. >* What outcome did you expect instead? > > wlan working as before. > > Thank you for your report. signature.asc Description: PGP signature
Bug#982579: Solution for loading firmware
please also add BananaPi M3 support. >From 216a0bda280e7b361c335f545156e86a059d9551 Mon Sep 17 00:00:00 2001 From: maximilian attems Date: Mon, 22 Feb 2021 22:18:36 +0100 Subject: [PATCH 2/2] WHENCE: add missing symlink for BananaPi M3 Fixes (Debian bug #982579): > [ 11.957171] brcmfmac mmc2:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt (-2) > [ 11.967106] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware > [ 11.977035] brcmfmac mmc2:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.txt (-2) > [ 12.994756] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50 Reported-by: Bernhard Signed-off-by: maximilian attems --- WHENCE | 1 + 1 file changed, 1 insertion(+) diff --git a/WHENCE b/WHENCE index 11c0970..b569990 100644 --- a/WHENCE +++ b/WHENCE @@ -2717,6 +2717,7 @@ File: "brcm/brcmfmac43430-sdio.AP6212.txt" Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt -> brcmfmac43430-sdio.AP6212.txt Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt -> brcmfmac43430-sdio.AP6212.txt Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt -> brcmfmac43430-sdio.AP6212.txt +Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt -> brcmfmac43430-sdio.AP6212.txt File: "brcm/brcmfmac43430-sdio.Hampoo-D2D3_Vi8A1.txt" File: "brcm/brcmfmac43430-sdio.MUR1DX.txt" File: "brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt" -- 2.30.0
Bug#982579: Solution for loading firmware
> The additional symlink bpi-m3 is for an additional device. > > This is for the Banana Pi M3. great, please post the dmesg error message, happy to submit upstream. (: > Should i create an additional Bug report? no need, this bug report can be cloned.
Bug#982579: Solution for loading firmware
> > 1. Copy file brcmfmac43430-sdio.AP6212.txt from upstream to > > lib/firmware/brcm > > so indeed it is a bug that we don't ship this one from upstream, > will fix this in next Debian upload. this needs to go in the debian git, will do soonish. (: > > 2. Create symbolic link named brcmfmac43430-sdio.sinovoip.bpi-m3.txt to the > > AP6212-file I am confused by this, as you did *not* submit an error log that showed a request for this file, is this to add support to another device, please be specific. > > 3. Create symbolic link named brcmfmac43430-sdio.sinovoip.bpi-m2-ultra.txt > > to the AP6212-file > this should be reported upstream, so that everyone takes advantage of > it, hence adding linux-firmware mailinglist on Cc, happy to cook up > a patch next 24hs. sent, to add that symlink upstream. thank you! -- maks signature.asc Description: PGP signature
Bug#982579: Solution for loading firmware
please find patch to add banana ultra support below >From b549a10838edc4f97d4a3b49b572fc613c7c703d Mon Sep 17 00:00:00 2001 From: maximilian attems Date: Tue, 16 Feb 2021 19:35:27 +0100 Subject: [PATCH] Add symlink for BananaPi M2 to brcmfmac43430-sdio config Fixes ( Debian bug #982579 [1]): [ 10.514530] brcmfmac mmc2:0001:1: firmware: direct-loading firmware brcm/brcmfmac43430-sdio.bin [ 10.514732] brcmfmac mmc2:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt ( -2) Refs: [1] https://bugs.debian.org/982579 Reported-by: Bernhard Signed-off-by: maximilian attems --- WHENCE | 1 + 1 file changed, 1 insertion(+) diff --git a/WHENCE b/WHENCE index aa96404..11c0970 100644 --- a/WHENCE +++ b/WHENCE @@ -2716,6 +2716,7 @@ File: "brcm/brcmfmac43430a0-sdio.ONDA-V80 PLUS.txt" File: "brcm/brcmfmac43430-sdio.AP6212.txt" Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt -> brcmfmac43430-sdio.AP6212.txt Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt -> brcmfmac43430-sdio.AP6212.txt +Link: brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt -> brcmfmac43430-sdio.AP6212.txt File: "brcm/brcmfmac43430-sdio.Hampoo-D2D3_Vi8A1.txt" File: "brcm/brcmfmac43430-sdio.MUR1DX.txt" File: "brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt" -- 2.30.0
Bug#982757: firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)
severity 982757 critical stop > Version: 20201218-3 > Severity: normal thank you for the report, oh boy this one is opens a can of trouble. It seems I was blissfully unaware that the Debian packaging did not take into account the symlinks of upstream linux-firmware WHENCE file. So this means we are missing a *lot* - all the symlinks!?!? > after latest update wifi stopped working and I saw that > brcm/brcmfmac43340-sdio.bin was missing, right it was replaced by newer cypress version and there should be a symlink of that guy from the older name: Link: brcm/brcmfmac43340-sdio.bin -> ../cypress/cyfmac43340-sdio.bin Could you please test latest 2021 upstream package with this symlink? kind regards, -- maks signature.asc Description: PGP signature
Bug#982579: Solution for loading firmware
Dear Bernhard, Thank you very much for your clear and helpful report! > I tested the following: > > 1. Copy file brcmfmac43430-sdio.AP6212.txt from upstream to lib/firmware/brcm so indeed it is a bug that we don't ship this one from upstream, will fix this in next Debian upload. > 2. Create symbolic link named brcmfmac43430-sdio.sinovoip.bpi-m3.txt to the > AP6212-file > 3. Create symbolic link named brcmfmac43430-sdio.sinovoip.bpi-m2-ultra.txt to > the AP6212-file this should be reported upstream, so that everyone takes advantage of it, hence adding linux-firmware mailinglist on Cc, happy to cook up a patch next 24hs. > After that, the wlan0 interface is available and scanning of the WLAN-ESSIDs > works. great! > Please either do it like described above or add the files directly instead of > the symbolic links. The symbolic links are better than duplicated files, but there seem to be on the Debian side an opened can of trouble on them, see #982757 (I'll post there soonish) Thank you for the kind words, the test and your report! -- maks signature.asc Description: PGP signature
Bug#982579: Failed to load firmware brcmfmac43430-sdio at BananaPi M2
> > [ 10.514530] brcmfmac mmc2:0001:1: firmware: direct-loading firmware > > brcm/brcmfmac43430-sdio.bin > > [ 10.514732] brcmfmac mmc2:0001:1: firmware: failed to load > > brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt ( > > -2) this txt file is missing upstream, once someone (preferrably its author submits it to linux-firmware) w appropriate license we are happy to ship it -> latest git is here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git > Please add the corresponding firmware. once it is upstream, sure. please feel free to bug the bpi m2 guys to do so. thank you, -- maks
Bug#893912: missing rtl_bt/rtl8821a_config.bin
Dear Yang, Would it be possible to add rtl8821a_config.bin config file? According to two bug reports, current state results in the following failure: -- [2.574742] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [2.575137] bluetooth hci0: firmware: failed to load rtl_bt/rtl8821a_config.bin (-2) [2.575143] bluetooth hci0: Direct firmware load for rtl_bt/rtl8821a_config.bin failed with error -2 [2.575145] Bluetooth: hci0: Failed to load rtl_bt/rtl8821a_config.bin -- According to bug reporter symlink of rtl8821c_config.bin to rtl8821a_config.bin ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893912#32 ) solves the issue. Or do you have this specific files and could push it upstream to linux-firmware? Thank you in advance. -- maks signature.asc Description: PGP signature
Bug#962038: Processed: firmware-nonfree: Add brcm-bluetooth (for RaspberryPi)
> Bug #962038 [raspi-firmware] firmware-nonfree: Add brcm-bluetooth (for > RaspberryPi) that be very possible to add and create a firmware package for that, but first this https://github.com/RPi-Distro/bluez-firmware/tree/master/broadcom would have to land upstream in linux-firmware. Have you tried to submit them, phil? signature.asc Description: PGP signature
Bug#981005: linux-image-5.10.0-2-amd64: Bluetooth stopped working
> After upgrading to Linux 5.10, Bluetooth no longer works. Bluetooth > adapter still shows up in rfkill: > > When booting from Linux 5.9, Bluetooth works fine. > > During start-up with Linux 5.10, there's an error message about > Bluetooth firmware. please provide 5.10.9 dmesg.
Bug#973454: firmware-iwlwifi: firmware does not load with error -110 with Intel 8260
On Fri, Jan 22, 2021 at 10:16:36PM +0100, Paweł Różański wrote: > On 22.01.2021 21:44, maximilian attems wrote: > > > Version: 20200918-1 > > > > > [ 12.411452] iwlwifi :01:00.0: Failed to start INIT ucode: -110 > > > [ 12.411500] iwlwifi :01:00.0: Collecting data: trigger 16 fired. > > > [ 13.566350] iwlwifi :01:00.0: Failed to run INIT ucode: -110 > > > uanme -rvm > > > 5.9.0-1-amd64 #1 SMP Debian 5.9.1-1 (2020-10-17) x86_64 > > > (also tested on 5.7.0-2-amd64 #1 SMP Debian 5.7.10-1 (2020-07-26) x86_64 > > > - the same) > > > > > > Used to work fine before reboot with 5.7 kernel. > > > Can provide additional information if needed. > > > > Is this still happening with 5.10 linux and newer iwlwifi version >= > > 202011? > > > Using 5.10.0-1-amd64 and 20200918-1 till now. Just upgraded to 20201218-2, > but didn't reboot yet. > Issue never repeated since I sent this report. thanks for patience and prompt report, this looks like to be fixed in iwlwifi then. I'll leave it open for a week and will then proceed to close unless repeatable.
Bug#963025: firmware-iwlwifi: Microcode SW error detected / 9000-pu-b0-jf-b0-46.ucode
> Firmware 9000-pu-b0-jf-b0-46.ucode stops working when used with > hostapd as soon as a wireless client connects. Is that still happening with latest 5.10 linux and newer firmware-iwlwifi version >= 202011? thank you.
Bug#973454: firmware-iwlwifi: firmware does not load with error -110 with Intel 8260
> Version: 20200918-1 > [ 12.411452] iwlwifi :01:00.0: Failed to start INIT ucode: -110 > [ 12.411500] iwlwifi :01:00.0: Collecting data: trigger 16 fired. > [ 13.566350] iwlwifi :01:00.0: Failed to run INIT ucode: -110 > uanme -rvm > 5.9.0-1-amd64 #1 SMP Debian 5.9.1-1 (2020-10-17) x86_64 > (also tested on 5.7.0-2-amd64 #1 SMP Debian 5.7.10-1 (2020-07-26) x86_64 - > the same) > > Used to work fine before reboot with 5.7 kernel. > Can provide additional information if needed. Is this still happening with 5.10 linux and newer iwlwifi version >= 202011? thank you.
Bug#970395: firmware-nonfree: Please add AMD-SEV firmware files (amd-folder) to close CVE-2019-9836 on specific EPYC-CPUs
Dear Henrique, It be great to get your input, hence repinging (; Especially as linux-firmware is the common upstream source, it be ideal to ship the amd64 mircrocode out of our firmware packages. Thanks for letting us know. kind regards, maximilian On Sun, Sep 20, 2020 at 10:36:12AM +0200, maximilian attems wrote: > Dear Henrique, dear debian kernel maintainers, Cc: Michael, > > Would you agree to generate the amd64-firmware packages directly out of the > debian > linux-firmware source package? > > This way the microcode would be updated on every linux-firmware non-free > upload? > I am asking as it keeps nugging me to have to outcomment the updates of that > microcode in the changelog (there is again a new one for the upcoming > 20200918). > > Would you want to be added in counterpart to the uploaders of > firmware-nonfree? > > Thank you very much for your amd64 microcode work. > > kind regards, > maximilian > > On Tue, Sep 15, 2020 at 04:55:43PM +0200, Michael Musenbrock wrote: > > Source: firmware-nonfree > > Severity: important > > > > Dear maintainer, > > > > first of all thanks for maintaining and packaging the linux-firmware files > > repository as debian packages. > > > > We currently need to manually obtain the > > linux-firmware.git:amd/amd_sev_fam17h_model3xh.sbin [1] file on > > our AMD EPYC servers. The firmware files containing the AMD SEV firmware > > closing security vulnerabilities [2] > > and fixes bugs and adds improvements to the AMD SEV implementation. > > > > I'm most likely unqualified for legal questions but the LICENSE.amd-sev [3] > > reads quite similar to the already > > added amdgpu license [4]. So I hope this is not the reason, why those files > > were not added in the past. > > > > The severity was choosen because it fixes a security vulnerability, please > > change accordingly if you think > > it is wrong. > > > > Thanks in advance. Best regards, > > michael > > > > [1] > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amd > > [2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9836 > > [3] > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENSE.amd-sev > > [4] > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENSE.amdgpu > > signature.asc Description: PGP signature
Bug#970395: firmware-nonfree: Please add AMD-SEV firmware files (amd-folder) to close CVE-2019-9836 on specific EPYC-CPUs
Dear Henrique, dear debian kernel maintainers, Cc: Michael, Would you agree to generate the amd64-firmware packages directly out of the debian linux-firmware source package? This way the microcode would be updated on every linux-firmware non-free upload? I am asking as it keeps nugging me to have to outcomment the updates of that microcode in the changelog (there is again a new one for the upcoming 20200918). Would you want to be added in counterpart to the uploaders of firmware-nonfree? Thank you very much for your amd64 microcode work. kind regards, maximilian On Tue, Sep 15, 2020 at 04:55:43PM +0200, Michael Musenbrock wrote: > Source: firmware-nonfree > Severity: important > > Dear maintainer, > > first of all thanks for maintaining and packaging the linux-firmware files > repository as debian packages. > > We currently need to manually obtain the > linux-firmware.git:amd/amd_sev_fam17h_model3xh.sbin [1] file on > our AMD EPYC servers. The firmware files containing the AMD SEV firmware > closing security vulnerabilities [2] > and fixes bugs and adds improvements to the AMD SEV implementation. > > I'm most likely unqualified for legal questions but the LICENSE.amd-sev [3] > reads quite similar to the already > added amdgpu license [4]. So I hope this is not the reason, why those files > were not added in the past. > > The severity was choosen because it fixes a security vulnerability, please > change accordingly if you think > it is wrong. > > Thanks in advance. Best regards, > michael > > [1] > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amd > [2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9836 > [3] > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENSE.amd-sev > [4] > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENSE.amdgpu > signature.asc Description: PGP signature
Bug#960788: ITP: alsa-sof-firmware -- Intel SOF audio firmware and topology
On Mon, Sep 07, 2020 at 09:43:33AM +0200, Hector Oron wrote: > Hello intrigeri, > > Missatge de intrigeri del dia ds., 5 de set. > 2020 a les 8:21: > > > So we could close this ITP (#960788, since in the end no new source > > package will be introduced) in favor of #949019 and #962134, which > > could themselves be merged, right? I'm happy to do the BTS paperwork > > if this makes sense to you folks :) > > Sounds great to me with thanks! after rethinking that upstream shows no interest in merging their binaries with linux-firmware and that in the future we might be able to compile them, I think it is better to have a separated package. With the experimental pulseaudio, latest sof and 5.8 the X1 nicely plays sound, so I have a good test bench. Due to moving around I plan to upload next weekend. so please keep the ITP open and for now it will be a binary upload. thanks! -- maks
Bug#969961: firmware-amd-graphics: amdgpu requires firmware installed even it already has been installed
>* What led up to the situation? > None, just boot up. >* What exactly did you do (or not do) that was effective (or > ineffective)? > 1. Go to tty2, login. Enter "sudo modprobe -r amdgpu" > 2. Then, Enter "sudo modprobe -i amdgpu" >* What was the outcome of this action? > None graphics shows up..Startx failed too. >* What outcome did you expect instead? > No error shows and graphics shows up. Have you tried newer amd microcode (as far as I remember Debian has an 2019 outdated one)? also linux 5.8 in unstable would be worth a try. thanks. -- maks
Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system
On Wed, Sep 09, 2020 at 08:34:16PM +0200, Seb wrote: > > > > Package: src:linux > > > Version: 4.19.67-2+deb10u2 > > [...] > > This version is 10 months old; please upgrade and try again as the bug > > may have been fixed already. > > OK, I will, but I do not know how to properly upgrade the kernel on a > Debain-stable system (which is up-to-date with respect to "apt upgrade"). > Could you enlighten me and say which kernel version I should try? How about: apt-get dist-upgrade What is its output? of course reboot after upgrade. best, -- maks
Bug#960788: ITP: alsa-sof-firmware -- Intel SOF audio firmware and topology
hello, On Sat, Sep 05, 2020 at 08:16:26AM +0200, intrigeri wrote: > > Missatge de Jordi Mallach del dia dj., 3 de set. > > 2020 a les 16:48: > > > >> After claiming it and looking at the source, I resolved this probably > >> belongs as part of linux-firmware or whatever the source name is, as > >> Ubuntu did. zumbi@ has been talking to the kernel people about this but > >> right now I'm unsure what the status is. > > > > That is correct, we have been discussing it at the #debian-kernel IRC > > channel and Maximilian was planning to add this SOF-bin to the > > firmware-nonfree package. > > Great news, thanks a lot for the summary! > > So we could close this ITP (#960788, since in the end no new source > package will be introduced) in favor of #949019 and #962134, which > could themselves be merged, right? I'm happy to do the BTS paperwork > if this makes sense to you folks :) please for now leave the options open, until final upload. working on it hopefully for this week or otherwise next week. genorig of linux-firmware will need some massage (2nd git source repo), if we just add it in. > > I believe Lenovo is supportive and is going to send a machine to > > Maximilian to be able to test it out. > > This is great news too. With my Tails hat on I'll suppose this will > take some time on the Debian/Lenovo side. I got the laptop and have bullseye nicely installed and also latest 5.8 kernel, need to see to get a sound now (: alsa seem to have recognised the card with the latest sof binaries, but didn't hear a beep yet.. best greetings, -- maks
Bug#783620: initramfs-tools: initramfs broken on first boot into Jessie, Unable to mount root fs on unknown-block(0, 0)
On Wed, Apr 29, 2015 at 01:06:07PM +0200, Bernhard Schmidt wrote: Hi, [ copied from debian-user again ] --- Got another system with the symptoms and managed to get a snapshot. It is really extremely weird. The kernel output is List of all partitions: No filesystem could mount root, tried: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) This is reproducible. To fix it it is enough to boot into the Wheezy kernel (even with init=/bin/sh), then reboot. It apparently does something to the root-fs (fsck?) which allows the Jessie kernel to boot. I have asked our Windows guys to make a screencast, it is uploaded here. http://users.birkenwald.de/~berni/volatile/783620.mkv We still have the snapshot available, if you have an idea please drop me a note. this means linux didn't get the initramfs passed by the bootloader. In the old days this happened when lilo was not run, these days it could be some grub modules out of sync (very wild guess). did you try before botting into that image to run install-grub in it? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748753: Upload xxv-intel 2.99.x to sid?
On Tue, Apr 28, 2015 at 03:02:37AM -0700, Vincent Cheng wrote: Hi, Now that jessie is out and the freeze is over, would anyone object if I were to upload xserver-xorg-video-intel from experimental to sid now? 3.0 is supposed to be an imminent release [1] anyways. isn't this imminent status given since a year? -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748753: Upload xxv-intel 2.99.x to sid?
On Tue, Apr 28, 2015 at 03:50:02PM +0200, Søren Holm wrote: Probably, but why keep it in experimental just because the number scheme is a little bit off. see previous discussions on this mailinglist. once there is a proper release I'm all for it. Ask intel why they don't!? -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781932:
tags 781932 moreinfo stop hello, Please do stop producing entropy. The bug severity is up to the judgment of the maintainers in the regular case that the bug submitter misunderstood it (which is the case here). It would be more helpful to narrow down which newer package version starts to work for this laptop (as from this one could narraw down the possible patches). Which versions of intel on http://snapshot.debian.org/ did you try? best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778588: Linux 4.0 compat
On Sat, Apr 04, 2015 at 07:30:11PM +0200, Lukas Wunner wrote: FWIW, the attached patch enables compatibility with 4.0. The plan is to upload the next 3.19 stable as soon as it is out, and then jump to 4.0 to experimental and soon unstable (after 8.0 release). best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781002: initramfs-tools: no kernel modules are insert into initrd
On Wed, Apr 01, 2015 at 06:10:05PM -0700, Marc MERLIN wrote: Could I make a few suggestions while we're at it? 1) I sometimes build an initrd for a kernel I haven't installed yet. Yes, it's a mistake, but it happily succeeds and creates an initrd without any modules which then creates a non booting system. = initramfs should abort if its generated /lib/modules/kernel is empty I thought this was caught. 2) initramfs creates a temporary directory where it puts everything, and then deletes it before you can inspect it for debugging. = Add a --debug that leaves that directory behind for inspection. Right now I have to unpack the initrd image which is more and more of a pain as it becomes a bundled binary of concatenated cpio images and god knows what. -k :P as usual read the nice man mkinitramfs (; 3) document the binwalk method of unpacking initrd to debug if needed (somewhere in the manpage): http://unix.stackexchange.com/questions/163346/why-is-it-that-my-initrd-only-has-one-directory-namely-kernel . Or for the archives: legolas [mc]# binwalk initrd.img pick up the offset of the 2nd initrd image, and unpack like so: legolas [mc]# cd subdir; dd if=../initrd.img bs=21136 skip=1 | gunzip | cpio -idv lsinitramfs shows you the content. sunny greetings, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779799: linux: Older patches causing FTBFS on armhf
On Wed, Mar 04, 2015 at 09:29:43PM +, B.R. Oake wrote: Source: linux Version: 3.19-1~exp1 Justification: fails to build from source Severity: serious Hello, The two patches: features/arm/dts-sun7i-Add-spi0_pins_a-pinctrl-setting.patch features/arm/dts-sun7i-Add-uart3_pins_b-pinctrl-setting.patch are no longer needed in 3.19-1~exp1 because they were accepted upstream in v3.19 as these commits: 2dad53b54a 0510e4b52a Keeping the patches means getting duplicate nodes in the device tree which causes this build failure on armhf: https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armhfver=3.19-1~exp1stamp=1424044478 Please could you remove the patches from the next experimental version? they are already removed in the repository for experimental, waiting for 3.19.X for the next upload. in any case thanks for the details. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772602: [sh4]: Please use default compiler instead of gcc-4.7
On Tue, Dec 09, 2014 at 01:44:42AM +0100, John Paul Adrian Glaubitz wrote: On sh4, the kernel package is still built with gcc-4.7 by default since both gcc-4.8 and gcc-4.9 were not built on sh4 until recently. This has now been resolved and both gcc-4.8 and gcc-4.9 are now readily available on sh4 to build the kernel. I assume it should just be necessary to drop the compiler statement in /debian/ config/sh4/defines. It would be nice to have this fixed for the next upload. the compiler change better be boot tested, was it? thank you. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765969: Bug#771133: xserver-xorg-video-intel: colored line on right side / bottom of video
On Thu, Nov 27, 2014 at 02:03:14AM +0100, Dirk Griesbach wrote: With vlc 2.2.x I'm getting a color distorted pixel row at the bottom and/or a column at the right side of a video if using hardware accelerated overlay xvideo output. This was reported as #765969 [1] against vlc but for now is considered a driver bug: ,[ Rémi Denis-Courmont ]- | troubleshooting it on an affected system and so far it does seem like a | driver bug: the driver is blending the last line of visible pixels with | the first line of pixels outside the visible area. All zeroes | corresponds to dark green in YUV colours space. ` So here I am. This happens in fullscreen and windowed mode and the color pattern of the line is changing if, e.g. I move a second window around. Test case: Big Buck Bunny[2] is a nice example: I tried the video in 854x480 and both mp4 and ogg give me a color-distorted column at the right side. If I try the 1920x1080-version the bottom row is affected. Screenshots from the other bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=50;filename=bottom.png;att=1;bug=765969 https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=50;filename=rightside.png;att=2;bug=765969 On another occasion I saw two rows affected where the bottom row is a more solid color and the row above it is only slightly tainted with the actual content shining through. xf86-video-intel upstream says: it's a bug in vlc. they are supplying an image larger than the surface they wish to scale and then complain when the extra pixels are sampled during scaling. the issue is that they are not initialising those extra pixels correctly - it should be padded. -ickle Hence keep bugging vlc guys, will close xorg driver bug report. best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770507: xserver-xorg-video-intel: short delay between key press and screen refresh in gnome-terminal
On Fri, Nov 21, 2014 at 09:40:44PM +0100, Johan Kröckel wrote: Affected keys: numbers and letters alone and together with shift. arrow keys to move the cursor sometimes (move to or from a letter?) delete and remove sometimes (delete a letter, not a newline?) space Unaffected keys: shortcuts like ctrl-k and ctrl-u in nano newline (enter) pos1 and end tabulator reporting against xserver-xorg-video-intel because occured after upgrading of it from 2:2.21.15-2+b2 to 2:2.99.916-1~exp1 because of 766506. other programms are not affected even xterm is unaffected. can't reproduce, please try latest git packaged in experimental aka version 2:2.99.916+git20141119-1~exp1 thanks. -- maks signature.asc Description: Digital signature
Bug#769072: gnome-shell: GNOME Shell crashing with Oh no, something went wrong
On Sat, Nov 15, 2014 at 02:13:58PM +0100, Julien Cristau wrote: On Sat, Nov 15, 2014 at 12:30:34 +0100, Janusz S. Bien wrote: Quote/Cytat - Julien Cristau jcris...@debian.org (sob, 15 lis 2014, 10:48:51): On Fri, Nov 14, 2014 at 23:42:37 +, Simon McVittie wrote: I think the problem here is that something is not right in the dependencies for the i965_dri.so and swrast_dri.so drivers, so you don't have any OpenGL support (not even software rendering) and GNOME Shell can't run: [...] Janusz, what's the output of 'ldd /usr/lib/xorg/modules/extensions/libglx.so'? jsbien@cauda:~$ ldd /usr/lib/xorg/modules/extensions/libglx.so linux-gate.so.1 (0xb77b8000) libGL.so.1 = /usr/lib/i386-linux-gnu/libGL.so.1 (0xb7626000) libpthread.so.0 = /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb760a000) libdl.so.2 = /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xb7604000) libaudit.so.1 = /lib/i386-linux-gnu/libaudit.so.1 (0xb75de000) libm.so.6 = /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xb7598000) libc.so.6 = /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb73ed000) libnvidia-tls.so.340.46 = /usr/lib/i386-linux-gnu/tls/libnvidia-tls.so.340.46 (0xb73e8000) libnvidia-glcore.so.340.46 = /usr/lib/i386-linux-gnu/libnvidia-glcore.so.340.46 (0xb4e55000) libX11.so.6 = /usr/lib/i386-linux-gnu/libX11.so.6 (0xb4d03000) libXext.so.6 = /usr/lib/i386-linux-gnu/libXext.so.6 (0xb4cee000) /lib/ld-linux.so.2 (0xb77bb000) libxcb.so.1 = /usr/lib/i386-linux-gnu/libxcb.so.1 (0xb4cc8000) libXau.so.6 = /usr/lib/i386-linux-gnu/libXau.so.6 (0xb4cc4000) libXdmcp.so.6 = /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xb4cbd000) Looks like nvidia took over libGL but not the server-side libglx.so. That can't possibly work; can the nvidia packages not do that? why would that box need nvidia packages? seems like a bad dependency too. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763620: initramfs depends on DEVTMPFS now?
On Mon, Oct 06, 2014 at 11:15:46AM +0200, Michal Hocko wrote: I have reverted to 0.116 which works just fine. I am perfectly OK with staying with this version but maybe the newer version should depend on systemd so the reason for this requirement is clear. you mix udev and systemd, so no it doesn't need full systemd. It needs the devices to show up. And yes udev is part nowadays of systemd. Also you may want to just fix your config setup. (; best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764073: xserver-xorg-input-synaptics: bcm5974 (Apple unibody trackpad) fails after extended idle
On Sun, Oct 05, 2014 at 02:43:23PM +0200, Julien Cristau wrote: Control: reassign -1 src:linux 3.14.15-2 Last night, I left my computer by turning down the screen brighness to zero and the keyboard's to about 20%. could you please reproduce on latest linux image 3.16.3-2? thanks. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760127: [PATCH initramfs-tools 0/3] Fix module dependency generation when running non-modular kernel
On Tue, Sep 30, 2014 at 01:23:50PM +0100, Ben Hutchings wrote: On Sun, 2014-09-28 at 04:10 +0100, Ben Hutchings wrote: This patch series addresses bug #760127 and related problems. Following these changes, I could build a working MODULES=dep initramfs for 3.16-2-amd64 on a libvirt VM while running a non-modular kernel. I've merged these to master. thanks! -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632627: Re[2]: Bug#632627: uswsusp patches for initramfs-tools (was: Bug#632627: Re[2]: resume file)
On Sun, Aug 31, 2014 at 04:11:07AM +0400, Askar Safin wrote: Sun, 31 Aug 2014 02:04:41 +0200 от Michael Prokop m...@debian.org: Are you willing to work on this? :) No, I'm just bug reporter :) uswsusp has been outdated 2y ago and hasn't improved yet. The support was removed in dracut in 2010. Please just close that, alternatively reassign to uswsusp, if it would be maintained the maintainer can/should lift that. thanks for your work! -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652459: initramfs-tools: [patch] Please support mounting of /usr in the initramfs
On Sun, Aug 31, 2014 at 02:06:46AM +0200, Michael Prokop wrote: * Roger Leigh [Sat Aug 30, 2014 at 11:19:42PM +0100]: On Sun, Aug 31, 2014 at 12:13:29AM +0200, Michael Prokop wrote: * Michael Prokop [Thu Jul 31, 2014 at 05:30:53PM +0200]: I've rebased the patchset against current git master and a preliminary and *untested*(!) package is available at: https://people.debian.org/~mika/initramfs-tools/ [...] This sounds good to me, is there any chance that either you, Roger Leigh or someone else would be willing to provide the according patchset (without the /etc-mount feature) rebased against our current git master and possibly while at it also take care of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652459#89 ? If so please ping me (either by mail, IRC or at DebConf), any help is really appreciated. I'm afraid I can't commit to any work at present. But regarding the mounting of /etc, that's just one or two commits at the end of the patchset. Just drop them to remove the feature. But do note that the feature is entirely harmless even if left in--it's not used by default. Thanks for additional information and the fast reply, then it would be even easier for me to integrate it since it's already there. If someone has objections please let me/us know NOW. yes scrap the /etc handling that was never acked, the rest had only codingstyle issues if i remember correctly. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759323: linux-image-3.16-trunk-amd64 : Xorg freezes or the system reboots under glxgears
On Tue, Aug 26, 2014 at 11:25:54AM +0200, Alain Rpnpif wrote: Severity: critical nope, unless affects thousands of boxes. no point to inflate. we'll update to 3.16.1 soonish, what's the fix for it from there? did you bisect? best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756810: linux-image-3.16-rc6-armmp: HDMI on wandboard/cubox-i no longer works
On Mon, Aug 11, 2014 at 11:43:15PM -0700, Vagrant Cascadian wrote: On 2014-08-11, Vagrant Cascadian wrote: I think this is caused by dropping CONFIG_DRM_IMX_IPUV3_CORE=m, which was moved out of staging into drivers/gpu/ipu-v3/Kconfig. And the configuration option was also renamed to CONFIG_IMX_IPUV3_CORE... I've tested that the following patch on a Cubox-i works: diff --git a/config/armhf/config.armmp b/config/armhf/config.armmp thank you, applied! (will be in next 3.16 upload, very likely for sid) happy hacking. (: -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757982: xserver segmentation fault
severity 757982 important stop On Wed, Aug 13, 2014 at 02:37:03AM +0200, repron wrote: Package: xserver-xorg-video-radeon Version: 1:7.4.0-2 Severity: grave and no a single failure is not grave. Dear Maintainer, With installed packages: xserver-xorg-video-radeon xserver-xorg-video-ati firmware-linux-nonfree very often randomly X-server freezes with the error: segmentation fault. I use X-window system: xfce4. This didn't happen when I had installed debian non-free driver: fglrx-driver for my Radeon HD6670 graphic card. thank your for your report, can you please test against 3.16 linux from experimental (currently hold up due to upcoming Debian Installer release) and see if you can reproduce after reboot? -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757805: linux: linux-3.14.13/drivers/gpu/drm/i915/intel_panel.c:696 i9xx_enable_backlight+0xd4/0x100 [i915]()
On Mon, Aug 11, 2014 at 04:30:01PM +0300, Martin-Éric Racine wrote: Package: src:linux Version: 3.14.13-2 Severity: normal File: linux While debugging something else, I found the following in syslog: can you reproduce with latest 3.16 (should be in exp). thank you. Aug 10 11:17:10 suomi kernel: [2.743921] fbcon: inteldrmfb (fb0) is primary device Aug 10 11:17:10 suomi kernel: [2.762046] [drm] Setting output timings on SDVOB failed Aug 10 11:17:10 suomi kernel: [2.924020] [ cut here ] Aug 10 11:17:10 suomi kernel: [2.924093] WARNING: CPU: 0 PID: 64 at /build/linux-sud87B/linux-3.14.13/drivers/gpu/drm/i915/intel_panel.c:696 i9xx_enable_backlight+0xd4/0x100 [i915]() Aug 10 11:17:10 suomi kernel: [2.924094] backlight already enabled Aug 10 11:17:10 suomi kernel: [2.924116] Modules linked in: dell_laptop rfkill dcdbas ata_piix(+) firewire_ohci sdhci_pci sdhci mmc_core firewire_core crc_itu_t libata scsi_mod ehci_pci(+) uhci_hcd(+) ehci_h cd tg3 ptp pps_core libphy usbcore usb_common i915(+) i2c_algo_bit drm_kms_helper video thermal wmi button drm i2c_core thermal_sys Aug 10 11:17:10 suomi kernel: [2.924121] CPU: 0 PID: 64 Comm: systemd-udevd Not tainted 3.14-2-686-pae #1 Debian 3.14.13-2 Aug 10 11:17:10 suomi kernel: [2.924123] Hardware name: Dell Inc. Latitude D430 /07, BIOS A01 06/20/2007 Aug 10 11:17:10 suomi kernel: [2.924130] 0009 c142f0e4 f6555864 c105069e f8aa5995 f655587c 0040 f8a9f2ac Aug 10 11:17:10 suomi kernel: [2.924136] 02b8 f8a66c14 f8a66c14 f4e08000 f65bdc00 f657ec00 0296 c10506f3 Aug 10 11:17:10 suomi kernel: [2.924141] 0009 f6555864 f8aa5995 f655587c f8a66c14 f8a9f2ac 02b8 f8aa5995 Aug 10 11:17:10 suomi kernel: [2.924142] Call Trace: Aug 10 11:17:10 suomi kernel: [2.924152] [c142f0e4] ? dump_stack+0x3e/0x4e -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754965:
could any of your affected guys test this synaptic package (built against latest xorg server): http://charm.itp.tuwien.ac.at/~mattems/xserver-xorg-input-synaptics_1.8.0-2_amd64.deb if you need it gpg signed, cry. thanks. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752878: lsinitramfs: fails to list contents with recent kernels
On Fri, Jun 27, 2014 at 02:24:33PM +0200, Reinhard Karcher wrote: I have no problems listing /boot/initrd.img-3.14-1-amd64 using lsinitramfs 0.115. My system is nearly the same, with the exception of udev (204-12 from testing) and kernel (3.15-trunk-amd64 from experimental) The bug has already been reported. It has to do, wether microcode-foo is installed or not. Happy if anyone cares enough to fix it. best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750661: uninstallable
On Sat, Jun 28, 2014 at 03:38:57PM +0200, Vincent Bernat wrote: ❦ 28 juin 2014 15:02 +0200, maximilian attems m...@stro.at : OK, I understood only later that the bug was reported against an unknown package. I suppose that the original submitter did try to install kernel headers some time after installing the kernel package itself. read ml for why not provided, in any case OOT modules are not recommended. I suppose the answer is in this message: https://lists.debian.org/debian-kernel/2014/06/msg00255.html It doesn't say much why the package is not in experimental while this was the case in the past. It seems that this bug is recurrent so I yes it is, please go back later in time with messages from waldi too. In any case it is experimental and OOT modules are severly discouraged. We might soon jump to 2.16-rcX, don't assume experimental stays on 2.15. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752701: initramfs-tools: Does not load firmware for in kernel wireless drivers
On Thu, Jun 26, 2014 at 10:31:45AM +0100, John Talbut wrote: Wed, 25 Jun 2014 22:43:56 +0200 maximilian attems wrote: This is a general problem that I have had now with three different wireless drivers. The problem is that the built in wireless driver starts working before the disk file systems have been mounted, and hence the firmware is not available. linux images by Debian have no built in wireless. again this is a user support question, please ask on mailing list not by bug report. best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748753:
On Mon, Jun 23, 2014 at 02:32:56PM -0700, Keshav Kini wrote: So can we please have a newer version of xserver-xorg-video-intel in sid soon? please install the one from experimental for now. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751385: newer python interfers with matplotlib
Package: python3 Version: 3.4.1-1 Severity: normal cat /tmp/test.py import matplotlib.pyplot as plt python3 /tmp/test.py Traceback (most recent call last): File /tmp/test.py, line 1, in module import matplotlib.pyplot as plt File /usr/lib/python3/dist-packages/matplotlib/pyplot.py, line 98, in module _backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup() File /usr/lib/python3/dist-packages/matplotlib/backends/__init__.py, line 28, in pylab_setup globals(),locals(),[backend_name],0) File /usr/lib/python3/dist-packages/matplotlib/backends/backend_tkagg.py, line 11, in module import matplotlib.backends.tkagg as tkagg File /usr/lib/python3/dist-packages/matplotlib/backends/tkagg.py, line 2, in module from matplotlib.backends import _tkagg ImportError: cannot import name '_tkagg' according to the github thread Ubuntu has fixes for this: https://github.com/matplotlib/matplotlib/issues/3093 thanks. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751385: newer python interfers with matplotlib
resassign 751385 python-mathplotlib merge 751385 750630 stop On Thu, Jun 12, 2014 at 12:52:24PM +0200, Matthias Klose wrote: why is this filed for python3? right duplicate too, sorry, I'm lost in userland. (; http://packages.qa.debian.org/m/matplotlib.html has the ubuntu specific changes listed. a Debian fix/upload would be very appreciated. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750630: Bug#751385: newer python interfers with matplotlib
Having to plot thingies, this is my workaround for the moment:
+import matplotlib
+matplotlib.use('GTK')
import matplotlib.pyplot as plt
--
maks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741695: xserver-xorg-video-intel: xv completely broken on HD 4400
On Tue, Jun 10, 2014 at 10:38:24PM +0200, Alex Mestiashvili wrote: I am experiencing the same trouble with my i3-4130T CPU and Intel HD 4400. It works fine with 3.13, but doesn't work on 3.14 and 3.15-rc8 kernels. The symptoms are the same, I see only a picture or short line of a video while the rest is static. adding Option AccelMethod sna didn't help me. Also works fine via OpenGL. did you try latest experimental xserver-xorg-video-intel with = 3.14 linux? best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750925: make deb-pkg produces a non-installable package on the s390x architecture
On Sun, Jun 08, 2014 at 09:30:23AM -0400, Stephen Powell wrote: Package: linux Version: 3.14.4-1 Severity: normal make deb-pkg, when issued on the s390x architecture, produces a non-installable package. The package is built for the s390 architecture, not the s390x architecture, and dpkg won't allow it to be installed, even if the package file is renamed to the expected naming convention (*_s390x.deb). see scripts/package/builddeb: s390*) debarch=s390 ;; this debarch setting very likely predates s390x -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750605: screen goes berserk, had to downgrade
On Thu, Jun 05, 2014 at 05:33:21PM +0800, 積丹尼 Dan Jacobson wrote: VC == Vincent Cheng vch...@debian.org writes: VC Section Device VC Identifier Intel Graphics VC Driver intel VC Option AccelMethod uxa VC EndSection Indeed, that fixes it. Newer snapshat has sna fixes, please test 2:2.99.911+git20140607-1~exp1 (without uxa fallback) thanks. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750860: xorg crashes randomly, floating point exception (synaptics' fault?)
On Sat, Jun 07, 2014 at 07:02:11PM +0200, niky wrote: Kernel version (/proc/version): --- Linux version 3.6-trunk-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-11) ) #1 SMP Debian 3.6.9-1~experimental.1 please upgrade your linux-image-amd64, this one is totaly outdated and not supported. Once you rebooted in newer, report back. regards, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750860: xorg crashes randomly, floating point exception (synaptics' fault?)
staying on random old packages is not supported, stable has lots of fixes on top of 3.2.0 On Sat, Jun 07, 2014 at 08:54:29PM +0200, niky 45 wrote: oh. I thought that since the kernel in stable is the 3.2.0, mine (3.6.9) wouldn't be too outdated... also randomly mixing stable and testing is no good, please either switch to one distribution or the other. while you are it there is a new synpatics driver in experimental, which goes with the xorg from testing. No idea about the cpufreq blurb. best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750360: systemd-sysv: breaks NFS root systems
On Tue, Jun 03, 2014 at 11:17:40AM +0200, Dominik George wrote: Control: tags -1 + patch initramfs-tools could just use a check like chroot /root test -x /sbin/init Then it doesn't matter whether it's a relative or absolute symlink. I made the needed fix in the script and tested in our terminal server environment. It works as expected and I do not see any side effects. Therefore, I propose this as a fix to be included in initramfs-tools, kindly sponsored by Teckids. no need of nmu games, I am following this. in any case, did you test it with klibc chroot too? meaning disabling BUSYBOX for the initramfs. thanks. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750360: systemd-sysv: breaks NFS root systems
On Tue, Jun 03, 2014 at 12:00:32PM +0200, Dominik George wrote: no need of nmu games, I am following this. Huh? I build a local version by using dch -n, which appends an NMU version, and then I use debdiff to create a patch. If you feel offended by a standard workflow, then bring in your own fix :)! Just saying that this is a package that shouldn't be NMU'd (; Can you please answer the !busybox question? thank you very much -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750360: systemd-sysv: breaks NFS root systems
Hello Michael! On Tue, Jun 03, 2014 at 06:19:23PM +0200, Michael Biebl wrote: On Tue, Jun 03, 2014 at 11:36:25AM +0200, maximilian attems wrote: in any case, did you test it with klibc chroot too? meaning disabling BUSYBOX for the initramfs. I quickly tested /usr/lib/klibc/bin/chroot, and that worked fine. So if the udeb versions aren't fundametally different, that should work. thank you very much, pushed out to initramfs repo: http://anonscm.debian.org/gitweb/?p=kernel/initramfs-tools.git will upload soonish. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750360: systemd-sysv: breaks NFS root systems
On Tue, Jun 03, 2014 at 08:03:16PM +0200, Sven Joachim wrote: Is this test going to work for systems with a separate /usr ? , | $ which test | /usr/bin/test ` dash or bash or POSIX shells have builtin test too. so yes it should just work. -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748753: closed by maximilian attems m...@debian.org (Bug#748753: fixed in xserver-xorg-video-intel 2:2.99.911+git20140529-1~exp1)
On Fri, May 30, 2014 at 11:52:39AM +0100, Chris Bainbridge wrote: I’m unsure if we want to upload random snapshot releases to sid, which is why I didn’t do that. Feel free to upload it to experimental, though. I wasn't actually suggesting making a random snapshot of the git source from upstream. Whatever you personally wish is fine for your own, but may not be for a distribution. In any case this is still only an experimental upload. The chosen version is a Maintainers decision and I didn't see you step up to such responsibility. The latest stable release from Intel is 2014Q1 which includes video-intel-2.99.910. Yes, it is a snapshot, but it is not a random one - it is the same one being used by Intel in the stable 1.0.5 release of their official Intel Graphics Installer. If it is good enough for Intel to use in a stable release of their graphics installer, then imho it ought to be good enough for Debian Unstable/Testing. 2.99.910 is also the version used in Ubuntu 14.04, which means it has already received much wider testing than any possible alternative snapshot. A newer snapshot was deemed to have better hardware support thanks to all fixes piled up in git, both for Haswell and beyond. kind regards, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749060: klibc: ppc64el needs static binaries as well
Hi, On Fri, May 23, 2014 at 10:57:31AM -0300, Mauricio Faria de Oliveira wrote: The ppc64el port needs klibc's static binaries, like ppc64. This segfaulting is a bug in klibc that needs investigation. This patch enables the ARCH=ppc64 make env var in debian/rules, in order for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too. I have no problem to merge this for Debian as workaround for now, but this is not the solution. Effort in making shared binary working too is appreciated. It is probably a wrong syscall API. Thank you. -- maks Index: klibc-2.0.3/debian/rules === --- klibc-2.0.3.orig/debian/rules +++ klibc-2.0.3/debian/rules @@ -33,7 +33,7 @@ ifeq ($(DEB_HOST_ARCH),sh4) DEB_MAKE_ENVVARS := ARCH=sh endif -ifeq ($(DEB_HOST_ARCH),ppc64) +ifneq (,$(findstring $(DEB_HOST_ARCH),ppc64 ppc64el)) DEB_MAKE_ENVVARS := ARCH=ppc64 endif -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743488: xserver-xorg-input-synaptics: new upstream version
The new upstream 1.7.99.1 version makes the touchpad working for new Lenovo devices that sport a Thinkpad sticker like the X1 Carbon 2nd generation or T540, T440, X240 and the Helix, Yoga laptops. An upload to sid or exp would be really appreciated. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744884: add ppc64el support
On Tue, Apr 15, 2014 at 03:38:02PM -0300, Mauricio Faria de Oliveira wrote: May you please include these 2 patches from klibc, in order to support the ppc64el architecture? [klibc] ppc64: Add ppc64le support [klibc] ppc64: build with -mcmodel=small A new upstream release with klibc 2.0.3 would resolve this as well. thanks for the reminder, will do that this week. best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741241: Support mips64 of klibc
On Tue, Mar 11, 2014 at 02:25:19PM +0800, Yunqiang Su wrote: Thank you very much. http://www.zytor.com/pipermail/klibc/2014-March/003538.html This got some comments: Like telling what the patch does and why, plus how it got tested? This are useful things to add to the patch description. Once those are addressed the patch/patches will land upstream and i'll release a newer version for Debian. Thank you for your effort. Best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741241: Support mips64 of klibc
Dear Yunqiang, Thank you very much for your patch. Usually we only take patches that have been reviewed upstream and landed in the klibc git. On Mon, Mar 10, 2014 at 06:22:14PM +0800, Yunqiang Su wrote: This patch add mips64(el) support for klibc, please consider to merge it. Please send it to kl...@zytor.com for review. Best, -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741241: Support mips64 of klibc
On Mon, Mar 10, 2014 at 06:29:26PM +0800, Yunqiang Su wrote: Which format should I send it there? git mail or just a attachment? git mail will be just fine indeed. it is the preferred form. But please base on klibc git (and hence no debian directory): https://git.kernel.org/cgit/libs/klibc/klibc.git/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735496: initramfs-tools fails because of missing keyutils package
reassign 735496 cryptsetup stop On Wed, Jan 15, 2014 at 07:45:06PM +, fdupoux wrote: Package: initramfs-tools Version: 0.115~bpo70+1 Severity: normal I am using wheezy mostyle stable and also backports packages (such as initramfs-tools) I have multiple volumes encrypted using dm_crypt (3 LVM Physical Volumes) using the same passphrase I do not want to type the passphrase three times hence I am using the following option in /etc/crypttab luks,keyscript=decrypt_keyctl The problem is update-initramfs fails because /bin/keyctl is required but it is not installed. It works after I installed keyutils but I had to debug the script to figure out what had to be installed. A package dependency should make sure this program is already installed to avoid this problem. # cat /etc/crypttab luks-0d020ecb-9fae-40fb-9ddf-8a75c8830d9c UUID=0d020ecb-9fae-40fb-9ddf- 8a75c8830d9c none luks,keyscript=decrypt_keyctl luks-182a31c7-38da-4c7f-9bf6-3568c0dbf1d4 UUID=182a31c7-38da-4c7f- 9bf6-3568c0dbf1d4 none luks,keyscript=decrypt_keyctl luks-d1c60f39-a178-46f9-824d-6353b97158c3 UUID=d1c60f39-a178-46f9-824d- 6353b97158c3 none luks,keyscript=decrypt_keyctl # cat /etc/debian_version 7.3 The main update-initramfs command fails: # update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 E: /usr/share/initramfs-tools/hooks/cryptkeyctl failed with return 1. update-initramfs: failed for /boot/initrd.img-3.2.0-4-amd64 with 1. The internal commands which fails: # mkinitramfs -o /boot/initrd.img-3.2.0-4-amd64.new 3.2.0-4-amd64 E: /usr/share/initramfs-tools/hooks/cryptkeyctl failed with return 1. dpkg -S /usr/share/initramfs-tools/hooks/cryptkeyctl would tell, which package that files belongs too, hence reassigned. # bash -x /usr/share/initramfs-tools/hooks/cryptkeyctl + set -e + PREREQ=cryptroot + case $1 in + . /usr/share/initramfs-tools/hook-functions + '[' '!' -x /lib/cryptsetup/scripts/decrypt_keyctl ']' + copy_exec /bin/keyctl + local src target x nonoptlib + local libname dirname + src=/bin/keyctl + target=/bin/keyctl + '[' -f /bin/keyctl ']' + return 1 The missing program is /bin/keyctl: # ls -lh /bin/keyctl ls: cannot access /bin/keyctl: No such file or directory The solution is to install the missing package: # apt-get install keyutils Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: keyutils 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 36.2 kB of archives. After this operation, 86.0 kB of additional disk space will be used. Get:1 http://ftp.uk.debian.org/debian/ wheezy/main keyutils amd64 1.5.5-3 [36.2 kB] Fetched 36.2 kB in 0s (125 kB/s) Selecting previously unselected package keyutils. (Reading database ... 125426 files and directories currently installed.) Unpacking keyutils (from .../keyutils_1.5.5-3_amd64.deb) ... Processing triggers for man-db ... Setting up keyutils (1.5.5-3) ... Finally it works: thanks. # update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64 -- maks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728024: git-annex: git annex is not syncing git repositories
Package: git-annex Version: 4.20131024 Severity: wishlist Hello, I tried to sync some work folder across several boxes with git annex, unfortunately it seems to ignore git repositories inside the directories. These are separte git directories deep inside that are for separate projects and hence have different histories. I assume that annex ignores any .git, but why could it only ignore the toplevel .git? These .git in lower level directories do need to be treated just as usual files for git-annex to be useful syncing the work across boxes. Currently I fall back to rsync, which is less practical as it requires manual intervention. Thank you. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-annex depends on: ii curl7.33.0-1 ii git 1:1.8.4~rc3-1 ii libc6 2.17-93 ii libffi6 3.0.13-4 ii libgmp102:5.1.2+dfsg-3 ii libgnutls26 2.12.23-8 ii libgsasl7 1.8.0-2 ii libicu484.8.1.1-13 ii libidn111.28-1 ii libxml2 2.9.1+dfsg1-3 ii libyaml-0-2 0.1.4-2 ii openssh-client 1:6.2p2-6 ii rsync 3.0.9-4 ii wget1.14-4 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages git-annex recommends: ii bind9-host 1:9.8.4.dfsg.P1-6+nmu3 ii git-remote-gcrypt 0.20130908-5 ii gnupg 1.4.15-1.1 ii lsof 4.86+dfsg-1 ii quvi 0.4.2-1 ii ssh-askpass1:1.2.4.1-9 Versions of packages git-annex suggests: pn bup none ii graphviz 2.26.3-15+b1 ii libnss-mdns 0.10-3.2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
