Bug#989152: linux: Mouse wheel support is broken after resume
Le mer. 26 mai 2021 à 23:27, Julien AUBIN a écrit : > > Source: linux > Version: Mouse wheel behaviour is broken after resume > Severity: normal > > Dear Maintainer, > > I've remarked that on a specific laptop the mouse wheel function is not > restored after resume. This is a regression that has been introduced between > Buster and Bullseye, and only occurs on one of my hosts. > > Laptop model : Dell Latitude e6540 > Mouse model : Microsoft Intellimouse 4500 > Desktop environment : KDE > > Steps to reproduce : > DO : boot the computer and open KDE > DO : open whatever application with a scrollbar and use the mouse scroll wheel > EXPECT : the scrolling works. > DO : suspend the computer to RAM for 5 minutes > DO : resume your activity > DO : open whatever application with a scrollbar and use the mouse scroll wheel > EXPECT : the scrolling works. > ACTUAL : the scrolling does not work. > > Workaround : unplug and plug the mouse, or use a tool like resetmsmice (it > would be great to include it in the archive : > https://github.com/paulrichards321/resetmsmice ) Hi, Could you monitor the corresponding input device by the help of "evtest" ? That's a userspace tool that dumps evdev events reported by the kernel to userspace (so we can check if the kernel exposes the scrolling to userspace after resume or not... perhaps that's a kernel issue, perhaps that's an issue in the upper layers) Could you : 1. install evtest : apt install evtest 2. With evtest /dev/input/event locate the device corresponding to your mouse: when you scroll you should see events. Something like: time 1622115506.006606, type 2 (EV_REL), code 8 (REL_WHEEL), value -1 3. Then when you have found the right device, check that the scrolling event is working as expected before resume (via evtest) Now test suspend and check if you see the scrolling event via evtest after resume. Once done, past your result here. Regards, Romain
Bug#970679: wireless-regdb: updating wireless-regdb to 2020.04.29-2~bpo10+1 makes AP mode impossible on ath10k wifi card
On Mon, Sep 21, 2020 at 01:28:53PM +0200, Félix Sipma wrote: > Package: wireless-regdb > Version: 2016.06.10-1 > Severity: normal > > Hello, > > I have an ath10k wireless card, using QCA988X driver in firmware-atheros, > which > worked with wireless-regdb 2016.06.10-1. I tried to update linux-image-amd64 > from 4.19+105+deb10u5 to 5.7.10-1~bpo10+1, which resulted in an updated > wireless-regdb (2020.04.29-2~bpo10+1). From then, The wifi card got > impossible > to use in 5Ghz AP mode (no frequency available). I tried to boot with > 4.19.0-10-amd64, and the same symptoms remained. Finally, downgrading > wireless-regdb to 2016.06.10-1 made the wifi functionnal again. > > Using firmware-atheros from buster-backports or not made no difference. > > Regards, > > > -- System Information: > Debian Release: 10.5 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > wireless-regdb depends on no packages. > > wireless-regdb recommends no packages. > > Versions of packages wireless-regdb suggests: > ii crda 3.18-1 > > -- no debconf information Hi, Could you, please, provide the output of 'dmesg' with the faulty kernel and the faulty wiresless-regdb, it might give us more context and I am wondering if it is not signing issue (perhaps not, just wondering, as we are now two maintainers). Typically one dmesg with kernel 5.7.x and wireless-regdb 2020.04.29, one dmesg with kernel 4.19.x and wireless-regdb 2020.04.29 and one dmesg when it works, would be perfect. Thanks, Romain signature.asc Description: PGP signature
Bug#963033: linux-image-arm64: kexec loses EFI system tables with Debian kernels
On Wed, Jul 22, 2020 at 03:28:39PM -0400, Gabriel Krisman Bertazi wrote: Hi, Well, after an analyze on my side, the EFI mode is detected based on the EFI stub, right ? Then the kernel populates the FDT with EFI properties into its own address space (based on what was previously found from the stub). Kexec simply does not preserve the EFI mode at all for arm64, it is only present for x86. With the original debian patch, we suppose that the "secure-boot" property will always be set in the FDT, simply because this information should be found in the EFI stub (unset, disabled, enabled, etc...), so the corresponding FDT property will always have a value and will always be present. So assume that it is always the case is correct, imho. Now, if the EFI stubs informations are not passed to the second stage kernel, either nor "system table" or "secure-boot" or the rest will be found, explaining the issue of the first comment (read the first comment it is "System table" that is not found). We should have a "setup_efi_info" like it is the case in the kexec-tools code base for x86, except we should have something similar for arm64. Regards, Romain signature.asc Description: PGP signature
Bug#956922: ITP: fsverity -- Userspace utilities for fs-verity
On Fri, Apr 17, 2020 at 07:55:17PM +0200, Romain Perier wrote: > Bastien : why not , I am opened to suggestions. > > Lucas: thanks for your proposal and your feedbacks. I will fix this and I > will keep you in touch. > > Regards, > Romain Hi, Lucas: Everything should be fixed in https://salsa.debian.org/rperier-guest/fsverity-utils. All the current patches will be sent on upstream. Thanks, Regards, Romain > > Le ven. 17 avr. 2020 à 13:29, Bastien ROUCARIES > a écrit : > > > On Thu, Apr 16, 2020 at 9:18 PM Romain Perier > > wrote: > > > > > > Package: wnpp > > > Severity: wishlist > > > Owner: Romain Perier > > > > > > * Package name: fsverity > > > Version : 1.0 > > > Upstream Author : Eric Biggers > > > * URL : > > https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git > > > * License : GPL > > > Programming Lang: C > > > Description : Userspace utilities for fs-verity > > > > > > This is fsverity, a userspace utility for fs-verity. fs-verity is a > > Linux kernel > > > feature that does transparent on-demand integrity/authenticity > > verification of > > > the contents of read-only files, using a hidden Merkle tree (hash tree) > > associated > > > with the file. The mechanism is similar to dm-verity, but implemented at > > the file > > > level rather than at the block device level. The fsverity utility allows > > you to > > > set up fs-verity protected files. > > > > > > This package will be helpful for handling the fsverity feature on a file > > from > > > userspace. > > > > > > I want to maintain this package. As DM, I need someone for the initial > > upload. > > > Packaging is currently hosted here > > https://salsa.debian.org/rperier-guest/fsverity, > > > and will be developed at https://salsa.debian.org/debian/fsverity > > > > I can. Do you plan also to support it under debian install (maybe also > > dm-verify/dm-integrity) > > > > Bastien > > signature.asc Description: PGP signature
Bug#956922: ITP: fsverity -- Userspace utilities for fs-verity
Bastien : why not , I am opened to suggestions. Lucas: thanks for your proposal and your feedbacks. I will fix this and I will keep you in touch. Regards, Romain Le ven. 17 avr. 2020 à 13:29, Bastien ROUCARIES a écrit : > On Thu, Apr 16, 2020 at 9:18 PM Romain Perier > wrote: > > > > Package: wnpp > > Severity: wishlist > > Owner: Romain Perier > > > > * Package name: fsverity > > Version : 1.0 > > Upstream Author : Eric Biggers > > * URL : > https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git > > * License : GPL > > Programming Lang: C > > Description : Userspace utilities for fs-verity > > > > This is fsverity, a userspace utility for fs-verity. fs-verity is a > Linux kernel > > feature that does transparent on-demand integrity/authenticity > verification of > > the contents of read-only files, using a hidden Merkle tree (hash tree) > associated > > with the file. The mechanism is similar to dm-verity, but implemented at > the file > > level rather than at the block device level. The fsverity utility allows > you to > > set up fs-verity protected files. > > > > This package will be helpful for handling the fsverity feature on a file > from > > userspace. > > > > I want to maintain this package. As DM, I need someone for the initial > upload. > > Packaging is currently hosted here > https://salsa.debian.org/rperier-guest/fsverity, > > and will be developed at https://salsa.debian.org/debian/fsverity > > I can. Do you plan also to support it under debian install (maybe also > dm-verify/dm-integrity) > > Bastien >
Bug#956922: ITP: fsverity -- Userspace utilities for fs-verity
Package: wnpp Severity: wishlist Owner: Romain Perier * Package name: fsverity Version : 1.0 Upstream Author : Eric Biggers * URL : https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git * License : GPL Programming Lang: C Description : Userspace utilities for fs-verity This is fsverity, a userspace utility for fs-verity. fs-verity is a Linux kernel feature that does transparent on-demand integrity/authenticity verification of the contents of read-only files, using a hidden Merkle tree (hash tree) associated with the file. The mechanism is similar to dm-verity, but implemented at the file level rather than at the block device level. The fsverity utility allows you to set up fs-verity protected files. This package will be helpful for handling the fsverity feature on a file from userspace. I want to maintain this package. As DM, I need someone for the initial upload. Packaging is currently hosted here https://salsa.debian.org/rperier-guest/fsverity, and will be developed at https://salsa.debian.org/debian/fsverity
Bug#931930: firmware-misc-nonfree: Please, include i915/icl_dmc_ver1_07.bin
On Fri, Jan 31, 2020 at 06:10:01PM -0800, Todd Troxell wrote: > Is there a reason why it's not included? I can make a patch and try it... Hi, icl_dmc_ver1_07.bin and bxt_huc_ver01_8_2893.bin seems to be included already, see https://salsa.debian.org/kernel-team/firmware-nonfree/blob/master/debian/config/misc-nonfree/defines At least in 20190717-1. Messages about "W: Possible missing firmware for module " is thrown by the hook functions of initramfs-tools, when a kmod requires firmware images not found on your systemd in /lib/firmware. Are you sure that your firmware packages are up-to-date ? Regards, Romain signature.asc Description: PGP signature
Bug#946404: tmux 3.0 break configuration compatibility with tmux 2.x
Package: tmux
Version: 3.0-1
Severity: important
Dear Maintainer,
The following configuration file, in attachment, is the configuration I
used with tmux for months. I have configured few key bindings and a
graphical theme that is greatly integrated with my vim setup. Since tmux
3.0 the color scheme and the keys are completly broken. It works
perfectly fine with tmux_2.8-3.
It is a important regression for me, at least a notice in the package
upgrade would be fine with few explanations.
How to reproduce:
- Launch tmux-2.x with this config, is is proper, the key bindings work
- Launch tmux-3.x with this config, it colors are ugly, nothing works
Feel free to ask more details in case,
Regards,
Romain
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tmux depends on:
ii libc6 2.29-3
ii libevent-2.1-7 2.1.11-stable-1
ii libtinfo6 6.1+20191019-1
ii libutempter01.1.6-4
tmux recommends no packages.
tmux suggests no packages.
-- no debconf information
# status bar colors etc
set-option -g status-bg black
set-option -g status-fg blue
set-option -g status-interval 5
set-option -g visual-activity off
set-option -gw xterm-keys on
set-option -g default-shell /bin/zsh
set-option -g default-terminal "screen-256color"
set -ag terminal-overrides ",*:XT@:Tc"
set-window-option -g monitor-activity on
set-window-option -g window-status-current-fg white
# start window indexing at one instead of zero
set -g base-index 1
unbind % # remove default binding since replacing
unbind-key Up
unbind-key Down
unbind-key Right
unbind-key Left
bind v split-window -h
bind h split-window -v
bind -n C-M-t new-window
bind-key Up select-pane -U
bind-key Down select-pane -D
bind-key Right select-pane -R
bind-key Left select-pane -L
# vim copy-paste mode
is_vim='echo "#{pane_current_command}" | grep -iq vim'
setw -g mode-keys vi
bind Escape copy-mode
bind -t vi-copy v begin-selection
bind -t vi-copy y copy-selection
bind -t vi-copy V rectangle-toggle
bind p paste-buffer
# Smart window switching
bind -n S-Right next-window
bind -n S-Left previous-window
# This tmux statusbar config was created by tmuxline.vim
# on ven., 19 févr. 2016
set -g status-bg "colour235"
set -g message-command-fg "colour22"
set -g status-justify "left"
set -g status-left-length "100"
set -g status "on"
set -g pane-active-border-fg "colour148"
set -g message-bg "colour235"
set -g status-right-length "100"
set -g status-right-attr "none"
set -g message-fg "colour252"
set -g message-command-bg "colour148"
set -g status-attr "none"
set -g pane-border-fg "colour22"
set -g status-left-attr "none"
setw -g window-status-fg "colour252"
setw -g window-status-attr "none"
setw -g window-status-activity-bg "colour235"
setw -g window-status-activity-attr "none"
setw -g window-status-activity-fg "colour252"
setw -g window-status-separator ""
setw -g window-status-bg "colour235"
set -g status-left "#[fg=colour235,bg=colour148] #S
#[fg=colour148,bg=colour235,nobold,nounderscore,noitalics]"
set -g status-right
"#[fg=colour22,bg=colour235,nobold,nounderscore,noitalics]#[fg=colour148,bg=colour22]
%Y-%m-%d %H:%M
#[fg=colour148,bg=colour22,nobold,nounderscore,noitalics]#[fg=colour235,bg=colour148]
#h "
setw -g window-status-format "#[fg=colour252,bg=colour235] #I
#[fg=colour252,bg=colour235] #W "
setw -g window-status-current-format "#[fg=colour148,bg=colour235] #I
#[fg=colour148,bg=colour235,nobold,nounderscore,noitalics]#[fg=colour148,bg=colour235]
#W #[fg=colour148,bg=colour235,nobold,nounderscore,noitalics]"
Bug#946402: buster-pu: package raspi3-firmware/1.20190215-1+deb10u2
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Hi stable release managers,
The version 1.20190215-1+deb10u2 fixes an important bug #941974. I have
added the debdiff in attachment.
Thanks,
Regards,
Romain
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru raspi3-firmware-1.20190215/debian/changelog
raspi3-firmware-1.20190215/debian/changelog
--- raspi3-firmware-1.20190215/debian/changelog 2019-08-28 12:31:28.0
+0200
+++ raspi3-firmware-1.20190215/debian/changelog 2019-11-09 09:09:08.0
+0100
@@ -1,3 +1,10 @@
+raspi3-firmware (1.20190215-1+deb10u2) buster; urgency=medium
+
+ * Fix serial console output sent to bluetooth port with kernel 5.x.
+Thanks to Thorsten Glaser (Closes: #941974)
+
+ -- Romain Perier Sat, 09 Nov 2019 09:09:08 +0100
+
raspi3-firmware (1.20190215-1+deb10u1) buster; urgency=medium
* Add support for bcm2837-rpi-cm3-io3.dtb (as generated by the Linux
diff -Nru
raspi3-firmware-1.20190215/debian/kernel/postinst.d/z50-raspi3-firmware
raspi3-firmware-1.20190215/debian/kernel/postinst.d/z50-raspi3-firmware
--- raspi3-firmware-1.20190215/debian/kernel/postinst.d/z50-raspi3-firmware
2019-08-28 12:26:28.0 +0200
+++ raspi3-firmware-1.20190215/debian/kernel/postinst.d/z50-raspi3-firmware
2019-11-09 09:09:08.0 +0100
@@ -88,13 +88,11 @@
cp "$latest_initrd" /boot/firmware/
serial="ttyAMA0,115200"
- kernelmajor=$(echo "${latest_kernel_basename}" | sed 's,^vmlinuz-,,g' | cut
-d. -f 1)
- kernelminor=$(echo "${latest_kernel_basename}" | cut -d. -f 2)
- if [ $kernelmajor -ge 4 ]; then
-if [ $kernelminor -ge 14 ]; then
- # Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
- serial="ttyS1,115200"
-fi
+ kernelmajmin=$(($(echo $latest_kernel_basename | sed -n \
+'s/^vmlinu.-\([0-9]*\)\.\([0-9]*\)\..*$/\1*1000+\2/p')))
+ if [ $kernelmajmin -ge 4014 ]; then
+# Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
+serial="ttyS1,115200"
fi
fi
Bug#924913: trackpad on L480 unusable after upgrade to testing
On Wed, May 29, 2019 at 05:54:22PM +0200, Alois Schlögl wrote: > On 3/26/19 9:03 PM, Romain Perier wrote: > > On Wed, Mar 20, 2019 at 08:24:33AM +0100, Alois Schlögl wrote: > >> On 3/18/19 7:46 PM, Romain Perier wrote: > >>> On Mon, Mar 18, 2019 at 12:43:10PM +0100, Alois Schlögl wrote: > >>>> On 3/18/19 12:20 PM, Romain Perier wrote: > >>>>> Hello, > >>>>> > >>>>> On Mon, Mar 18, 2019 at 11:27:41AM +0100, Alois Schlögl wrote: > >>>>>> Source: linux > >>>>>> Severity: normal > >>>>>> > >>>>>> Dear Maintainer, > >>>>>> > >>>>>> On a Lenovo L480 laptop, I've upgraded Debian from 9 (stretch) to 10 > >>>>>> (testing). > >>>>>> After the upgrade, the touchpad and the trackpoint was not usable > >>>>>> anymore. > >>>>>> > >>>>>> > >>>>>> This already has some bug report here, > >>>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803600 > >>>>>> > >>>>>> As a workaround, one can run the command, > >>>>>> sudo sh -c 'echo -n "elantech"> > >>>>>> /sys/bus/serio/devices/serio1/protocol' > >>>>>> in order to use the touchpad. However, on a GUI Interface and > >>>>>> without > >>>>>> an external mouse, it's impossible to apply this workaround > >>>>>> (switching to the terminal -F1, login, and run the command > >>>>>> above might work) > >>>>>> > >>>>>> I expect to be able to use the touchpad just out of the box, not > >>>>>> needing > >>>>>> to run the above workaround > >>>>>> > >>>>> Could you : > >>>>> > >>>>> - Test with the last kernel uploaded to unstable (4.19.0-4:4.19.28) and > >>>>> confirm or > >>>>> not is the problem still exists ? > >>>> Dear Romain > >>>> > >>>> > >>>> I upgraded the kernel and rebooted: > >>>> > >>>> schloegl@debian10:~$ uname -a > >>>> Linux debian10 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) > >>>> x86_64 GNU/Linux > >>>> > >>>> > >>>> With this kernel the trackpoint is working, the trackpad is still not > >>>> usable. > >>>> > >>>> (This improves the situation because now at least one pointer device is > >>>> available). > >>>> > >>>> > >>> Good, we did some progress :) > >>> > >>>>> - According to the bug on launchpad and to the fix pushed upstream, the > >>>>> fix seems to be an hardware quirks, could you give me the output of > >>>>> the > >>>>> following command : > >>>>> $ /sys/bus/serio/devices/serio1/firmware_id > >>>> root@debian10:~# cat /sys/bus/serio/devices/serio1/firmware_id > >>>> PNP: LEN2036 PNP0f13 > >>>> > >>> Could you test the patch attached to this reply ? > >>> (if you don't know how to do this, I can provide support) > >>> > >>> Regards, > >>> Romain > >> > >> > >> I tried to followed these instructions: > >> > >> https://kernel-team.pages.debian.net/kernel-handbook/ch-comm > >> > >> 4.5. Building a custom kernel from Debian kernel source > >> > >> Specifically using the patched the sources, > >> > >> *scripts/config --disable MODULE_SIG* > >> **scripts/config --disable DEBUG_INFO** > >> ||*|make clean|* ||*|make deb-pkg > >> > >> |* > >> > >> and ended up with a kernel that does not boot (missing HD audio firmware), > >> > >> > >> Which procedure do you recommend to build and install a modified kernel ? > >> > >> > > Hi, > > > > Section 4.2 from > > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official > > , until test-patches should work. For the test-patches script, use the > > flavour and a > > featur
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
On Tue, May 21, 2019 at 09:59:21AM +0200, Diederik de Haas wrote: > Got a new MB BIOS and after installing that, I made a new attempt with > firmware-amd-graphics version 20190502-1. > It failed again, but it got slightly further this time. > I saw a remount message, then a blinking cursor and then blank > screen+freeze+monitor in standby modus. > I figured that would've produced a kern.log and it did; see attachment. > > I have the upstream git repo on my machine and when I did > "git log -- amdgpu/vega10_ce.bin" I noticed commit > 0f22c8527439eaaf5c3fcf87b31c89445b6fa84d with the following message: > Revert "amdgpu: update vega10 fw for 18.50 release" > > This reverts commit ec4b0cd394472ee1491df6ef5f215d1f0953f836. > > This causes GPU hangs for some users. Let's revert for now > while we try and root cause the issue. > > Sounds familiar. > > What I could do is getting the various versions of amdgpu/vega10* from the > upstream git repo and place them in /lib/firmware/amdgpu/ to see which > versions > work and which don't. > Would that be useful? Any specific tests I should do or data to gather > (please > indicate how I should do that) > > Cheers, > Diederik Hi, firmware-amd-graphics 20190502-1 is based onto upstream commit 92e17d0dd2437140fab044ae62baf69b35d7d1fa, that is commit "amdgpu: update vega20 to the latest 19.10 firmware" . Two commits behind there is commit "amdgpu: update vega10 to the latest 19.10 firmware", that is already included in firmware-amd-graphics 20190502-1. Could you try to revert "amdgpu: update vega10 to the latest 19.10 firmware" ? So try to use the firmware for vega10 that is before this commit. Does it work for you ? 1. Use linux-firmware.git with last HEAD in the master branch 2. git checkout 4ea5c73b96ed4a508f90047e22ccbaa477481310 (commit "amdgpu: update polaris11 to the latest 19.10 firmware", that is the commit before bumping vega10 to 19.10) 3. Copy vega10 binary blobs to /lib/firmware/amdgpu Does it work ? Thanks, Regards, Romain > May 21 08:48:40 bagend kernel: [0.00] Linux version 4.19.0-5-amd64 > (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP > Debian 4.19.37-3 (2019-05-15) > May 21 08:48:40 bagend kernel: [0.00] Command line: > BOOT_IMAGE=/vmlinuz-4.19.0-5-amd64 > root=UUID=a2a5e481-0ac6-4e68-818f-38255bf7dd57 ro quiet > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: Supporting XSAVE > feature 0x001: 'x87 floating point registers' > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: Supporting XSAVE > feature 0x002: 'SSE registers' > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: Supporting XSAVE > feature 0x004: 'AVX registers' > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: xstate_offset[2]: > 576, xstate_sizes[2]: 256 > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: Enabled xstate > features 0x7, context size is 832 bytes, using 'compacted' format. > May 21 08:48:40 bagend kernel: [0.00] BIOS-provided physical RAM map: > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x-0x0009d3ff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0009d400-0x0009] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x000e-0x000f] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0010-0x09cf] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x09d0-0x09ff] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0a00-0x0a1f] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0a20-0x0a20afff] ACPI NVS > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0a20b000-0x0aff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0b00-0x0b01] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0b02-0xd873efff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xd873f000-0xdb030fff] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdb031000-0xdb137fff] ACPI data > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdb138000-0xdb244fff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdb245000-0xdb60afff] ACPI NVS > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdb60b000-0xdc68bfff] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdc68c000-0xdeff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem >
Bug#924913: trackpad on L480 unusable after upgrade to testing
On Tue, Mar 26, 2019 at 09:03:59PM +0100, Romain Perier wrote: > On Wed, Mar 20, 2019 at 08:24:33AM +0100, Alois Schlögl wrote: > > On 3/18/19 7:46 PM, Romain Perier wrote: > > > On Mon, Mar 18, 2019 at 12:43:10PM +0100, Alois Schlögl wrote: > > >> On 3/18/19 12:20 PM, Romain Perier wrote: > > >>> Hello, > > >>> > > >>> On Mon, Mar 18, 2019 at 11:27:41AM +0100, Alois Schlögl wrote: > > >>>> Source: linux > > >>>> Severity: normal > > >>>> > > >>>> Dear Maintainer, > > >>>> > > >>>> On a Lenovo L480 laptop, I've upgraded Debian from 9 (stretch) to 10 > > >>>> (testing). > > >>>> After the upgrade, the touchpad and the trackpoint was not usable > > >>>> anymore. > > >>>> > > >>>> > > >>>> This already has some bug report here, > > >>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803600 > > >>>> > > >>>> As a workaround, one can run the command, > > >>>> sudo sh -c 'echo -n "elantech"> > > >>>> /sys/bus/serio/devices/serio1/protocol' > > >>>> in order to use the touchpad. However, on a GUI Interface and > > >>>> without > > >>>> an external mouse, it's impossible to apply this workaround > > >>>> (switching to the terminal -F1, login, and run the command > > >>>> above might work) > > >>>> > > >>>> I expect to be able to use the touchpad just out of the box, not > > >>>> needing > > >>>> to run the above workaround > > >>>> > > >>> Could you : > > >>> > > >>> - Test with the last kernel uploaded to unstable (4.19.0-4:4.19.28) and > > >>> confirm or > > >>> not is the problem still exists ? > > >> Dear Romain > > >> > > >> > > >> I upgraded the kernel and rebooted: > > >> > > >> schloegl@debian10:~$ uname -a > > >> Linux debian10 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) > > >> x86_64 GNU/Linux > > >> > > >> > > >> With this kernel the trackpoint is working, the trackpad is still not > > >> usable. > > >> > > >> (This improves the situation because now at least one pointer device is > > >> available). > > >> > > >> > > > Good, we did some progress :) > > > > > >>> - According to the bug on launchpad and to the fix pushed upstream, the > > >>> fix seems to be an hardware quirks, could you give me the output of > > >>> the > > >>> following command : > > >>> $ /sys/bus/serio/devices/serio1/firmware_id > > >> root@debian10:~# cat /sys/bus/serio/devices/serio1/firmware_id > > >> PNP: LEN2036 PNP0f13 > > >> > > > Could you test the patch attached to this reply ? > > > (if you don't know how to do this, I can provide support) > > > > > > Regards, > > > Romain > > > > > > > > I tried to followed these instructions: > > > > https://kernel-team.pages.debian.net/kernel-handbook/ch-comm > > > > 4.5. Building a custom kernel from Debian kernel source > > > > Specifically using the patched the sources, > > > > *scripts/config --disable MODULE_SIG* > > **scripts/config --disable DEBUG_INFO** > > ||*|make clean|* ||*|make deb-pkg > > > > |* > > > > and ended up with a kernel that does not boot (missing HD audio firmware), > > > > > > Which procedure do you recommend to build and install a modified kernel ? > > > > > > Hi, > > Section 4.2 from > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official > , until test-patches should work. For the test-patches script, use the > flavour and a > featureset as argument, when you invoke it, like this : > > # debian/bin/test-patches -f amd64 -s none > /path/to/0001-Input-elantech-disable-elan-i2c-for-L480.patch > > This will apply the patch on the fly, configure the kernel for amd64 > and build a version with a special changelog entry and a special suffix > version dedicated to the test version you generate. > > > In case of troubles, I can provide another way, from git with few > commands. > > > Hope this helps, > Regards, > Romain Could you also provide the logs of the non booting kernel ? If you want I can also build a kernel for you with the fix and then send you a link via "firefox send" (something secure and free) for example. Regards, Romain signature.asc Description: PGP signature
Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3
On Wed, Mar 27, 2019 at 03:29:21PM +0100, Fabian Pietsch wrote: > Package: src:linux > Version: 4.19.28-2 > Followup-For: Bug #925334 > > Dear Maintainer, > > the bug is still present in the current version. It took a freshly > booted, idle system 3304 seconds for the bug to occur, though, > so this time rather an hour (than 10-30min as stated before). > > After the bug has happened, I get the following information from sysfs: > > | root@rpi3:/sys/bus/platform/drivers/vc4_v3d# for I in enabled status > active_time suspended_time; do echo -n "$I=$(cat > 3fc0.v3d/power/runtime_$I) "; done; echo > | enabled=enabled status=error active_time=16800 suspended_time=55464216 > > And again: > > | enabled=enabled status=error active_time=16800 suspended_time=55479160 > > So vc4_v3d which reported the error seems to be in status=error > and counts as suspended. Manual attempts to get it to resume again, > now that more cma is free again, failed, but there are probably ways > I don't know about. > > "echo on > .../power/control" changed runtime_enabled=forbidden > (and echo auto > control changed it back to runtime_enabled=enabled), > but runtime_status remained at "error". > > Regards, Fabian > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: arm64 (aarch64) > > Kernel: Linux 4.19.0-4-arm64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_CRAP > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), > LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled Hi, As discussed on IRC, thanks for your bug report and for the refresh. Could you test, two stuffs for me ? : 1. The VC4 driver seems to use runtime pm operations, could you try to disable runtime suspend completly (there are kernel parameters for this if I remember correctly) ? 2. Your kernel cmdline are... weird, could you try with minimalistic kernel cmdline ? Only keep console= for logging to uart and/or to your tty0 and keep your rootfs. Thanks, Romain signature.asc Description: PGP signature
Bug#924913: trackpad on L480 unusable after upgrade to testing
On Wed, Mar 20, 2019 at 08:24:33AM +0100, Alois Schlögl wrote: > On 3/18/19 7:46 PM, Romain Perier wrote: > > On Mon, Mar 18, 2019 at 12:43:10PM +0100, Alois Schlögl wrote: > >> On 3/18/19 12:20 PM, Romain Perier wrote: > >>> Hello, > >>> > >>> On Mon, Mar 18, 2019 at 11:27:41AM +0100, Alois Schlögl wrote: > >>>> Source: linux > >>>> Severity: normal > >>>> > >>>> Dear Maintainer, > >>>> > >>>> On a Lenovo L480 laptop, I've upgraded Debian from 9 (stretch) to 10 > >>>> (testing). > >>>> After the upgrade, the touchpad and the trackpoint was not usable > >>>> anymore. > >>>> > >>>> > >>>> This already has some bug report here, > >>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803600 > >>>> > >>>> As a workaround, one can run the command, > >>>> sudo sh -c 'echo -n "elantech"> > >>>> /sys/bus/serio/devices/serio1/protocol' > >>>> in order to use the touchpad. However, on a GUI Interface and without > >>>> an external mouse, it's impossible to apply this workaround > >>>> (switching to the terminal -F1, login, and run the command > >>>> above might work) > >>>> > >>>> I expect to be able to use the touchpad just out of the box, not > >>>> needing > >>>> to run the above workaround > >>>> > >>> Could you : > >>> > >>> - Test with the last kernel uploaded to unstable (4.19.0-4:4.19.28) and > >>> confirm or > >>> not is the problem still exists ? > >> Dear Romain > >> > >> > >> I upgraded the kernel and rebooted: > >> > >> schloegl@debian10:~$ uname -a > >> Linux debian10 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) > >> x86_64 GNU/Linux > >> > >> > >> With this kernel the trackpoint is working, the trackpad is still not > >> usable. > >> > >> (This improves the situation because now at least one pointer device is > >> available). > >> > >> > > Good, we did some progress :) > > > >>> - According to the bug on launchpad and to the fix pushed upstream, the > >>> fix seems to be an hardware quirks, could you give me the output of the > >>> following command : > >>> $ /sys/bus/serio/devices/serio1/firmware_id > >> root@debian10:~# cat /sys/bus/serio/devices/serio1/firmware_id > >> PNP: LEN2036 PNP0f13 > >> > > Could you test the patch attached to this reply ? > > (if you don't know how to do this, I can provide support) > > > > Regards, > > Romain > > > > I tried to followed these instructions: > > https://kernel-team.pages.debian.net/kernel-handbook/ch-comm > > 4.5. Building a custom kernel from Debian kernel source > > Specifically using the patched the sources, > > *scripts/config --disable MODULE_SIG* > **scripts/config --disable DEBUG_INFO** > ||*|make clean|* ||*|make deb-pkg > > |* > > and ended up with a kernel that does not boot (missing HD audio firmware), > > > Which procedure do you recommend to build and install a modified kernel ? > > Hi, Section 4.2 from https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official , until test-patches should work. For the test-patches script, use the flavour and a featureset as argument, when you invoke it, like this : # debian/bin/test-patches -f amd64 -s none /path/to/0001-Input-elantech-disable-elan-i2c-for-L480.patch This will apply the patch on the fly, configure the kernel for amd64 and build a version with a special changelog entry and a special suffix version dedicated to the test version you generate. In case of troubles, I can provide another way, from git with few commands. Hope this helps, Regards, Romain signature.asc Description: PGP signature
Bug#924913: trackpad on L480 unusable after upgrade to testing
On Mon, Mar 18, 2019 at 12:43:10PM +0100, Alois Schlögl wrote:
> On 3/18/19 12:20 PM, Romain Perier wrote:
> > Hello,
> >
> > On Mon, Mar 18, 2019 at 11:27:41AM +0100, Alois Schlögl wrote:
> >> Source: linux
> >> Severity: normal
> >>
> >> Dear Maintainer,
> >>
> >> On a Lenovo L480 laptop, I've upgraded Debian from 9 (stretch) to 10
> >> (testing).
> >> After the upgrade, the touchpad and the trackpoint was not usable
> >> anymore.
> >>
> >>
> >> This already has some bug report here,
> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803600
> >>
> >> As a workaround, one can run the command,
> >> sudo sh -c 'echo -n "elantech">
> >> /sys/bus/serio/devices/serio1/protocol'
> >> in order to use the touchpad. However, on a GUI Interface and without
> >> an external mouse, it's impossible to apply this workaround
> >> (switching to the terminal -F1, login, and run the command
> >> above might work)
> >>
> >> I expect to be able to use the touchpad just out of the box, not needing
> >> to run the above workaround
> >>
> > Could you :
> >
> > - Test with the last kernel uploaded to unstable (4.19.0-4:4.19.28) and
> > confirm or
> > not is the problem still exists ?
>
>
> Dear Romain
>
>
> I upgraded the kernel and rebooted:
>
> schloegl@debian10:~$ uname -a
> Linux debian10 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15)
> x86_64 GNU/Linux
>
>
> With this kernel the trackpoint is working, the trackpad is still not
> usable.
>
> (This improves the situation because now at least one pointer device is
> available).
>
>
Good, we did some progress :)
> > - According to the bug on launchpad and to the fix pushed upstream, the
> > fix seems to be an hardware quirks, could you give me the output of the
> > following command :
> > $ /sys/bus/serio/devices/serio1/firmware_id
>
>
> root@debian10:~# cat /sys/bus/serio/devices/serio1/firmware_id
> PNP: LEN2036 PNP0f13
>
Could you test the patch attached to this reply ?
(if you don't know how to do this, I can provide support)
Regards,
Romain
From 79f7fa6db07e2ddb985c560ef48b5a33ddcaffd7 Mon Sep 17 00:00:00 2001
From: Romain Perier
Date: Mon, 18 Mar 2019 13:36:00 +0100
Subject: [PATCH] Input: elantech - disable elan-i2c for L480
The current implementation of elan_i2c is known to not support this
laptop. Until this is fixed correctly, proceed like for P52 and P72
and disable elan_i2c for the devices we know are not behaving properly.
Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924913
Fixes: df077237cf55 (Input: elantech - detect new ICs and setup Host Notify for them)
Signed-off-by: Romain Perier
---
drivers/input/mouse/elantech.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/input/mouse/elantech.c b/drivers/input/mouse/elantech.c
index a7f8b1614559..faeda9cba813 100644
--- a/drivers/input/mouse/elantech.c
+++ b/drivers/input/mouse/elantech.c
@@ -1781,6 +1781,7 @@ static const char * const i2c_blacklist_pnp_ids[] = {
* These are known to not be working properly as bits are missing
* in elan_i2c.
*/
+ "LEN2036", /* Thinkpad L480 */
"LEN2131", /* ThinkPad P52 w/ NFC */
"LEN2132", /* ThinkPad P52 */
"LEN2133", /* ThinkPad P72 w/ NFC */
--
2.20.1
signature.asc
Description: PGP signature
Bug#924913: trackpad on L480 unusable after upgrade to testing
Hello, On Mon, Mar 18, 2019 at 11:27:41AM +0100, Alois Schlögl wrote: > > Source: linux > Severity: normal > > Dear Maintainer, > > On a Lenovo L480 laptop, I've upgraded Debian from 9 (stretch) to 10 > (testing). > After the upgrade, the touchpad and the trackpoint was not usable > anymore. > > > This already has some bug report here, > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803600 > > As a workaround, one can run the command, > sudo sh -c 'echo -n "elantech"> > /sys/bus/serio/devices/serio1/protocol' > in order to use the touchpad. However, on a GUI Interface and without > an external mouse, it's impossible to apply this workaround > (switching to the terminal -F1, login, and run the command > above might work) > > I expect to be able to use the touchpad just out of the box, not needing > to run the above workaround > Could you : - Test with the last kernel uploaded to unstable (4.19.0-4:4.19.28) and confirm or not is the problem still exists ? - According to the bug on launchpad and to the fix pushed upstream, the fix seems to be an hardware quirks, could you give me the output of the following command : $ /sys/bus/serio/devices/serio1/firmware_id Thanks, Regards, Romain > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled signature.asc Description: PGP signature
Bug#921518: flash-kernel: [PATCHv2] Adding-definition-of-Raspberry-Pi-Family
On Wed, Feb 06, 2019 at 07:08:35PM +, Ben Hutchings wrote: > On Wed, 2019-02-06 at 13:45 +0100, Alexandre GRIVEAUX wrote: > > Package: flash-kernel > > Version: 3.79 > > Severity: normal > > Tags: patch > > > > Adding definition according to: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts?h=v4.20 > > https://packages.debian.org/stretch/armhf/linux-image-4.9.0-8-armmp/filelist > > https://packages.debian.org/stretch/arm64/linux-image-4.9.0-8-arm64/filelist > > > > With adding correction of Raspberry pi 1 to use ARMEL flavour from feedback. > [...] > > "armel" is the name of the Debian architecture that can run on the Pi > 0/1, not the name of a kernel flavour. We do not yet have any kernel > flavour for these yet, and it is unlikely to be "armel". We tend to > use the architecture name as a kernel flavour name only if it can > support most hardware for that architecture. > > Ben. > > -- > Ben Hutchings > Man invented language to satisfy his deep need to complain. > - Lily Tomlin > > Hello, I have recently joined the kernel-team and discussed about this topic with Ben. I am currently working on a kernel flavour for armel that enables support for Raspberry Pi Zero. This should work with both the Pi 1 and the Pi Zero. The kernel is booting and working fine here on my pi zero w. I will open a MR soon. The plan is to merge the feature into kernel-team/linux.git. Regards, Romain
Bug#908632: linux-image-4.19.0-rc3-amd64-unsigned: kernel 4.19 fails to load amdgpu driver on R9 270X.
Hello, On Fri, Sep 21, 2018 at 02:13:27PM -0300, felipe wrote: > Tested again with experimental kernel 4.19-rc4 and the result is the same > (not able to find firmware) as with 4.19-rc3 > and 4.19-rc2. > > Tried reinstalling the firmware-amd-graphics and firmware-linux packages. > > Booting with kernel parameters 'radeon.si_support=0 amdgpu.si_support=1' and > kernel 4.19.rc-4 the system bails and > cannot find the required firmware which is located at '/lib/firmware/radeon'. > > If I copy the contents of '/lib/firmware/radeon' to '/lib/firmware/amdgpu' > and restart, the system boots, loads the > firmware and works. > > Since previous kernels (4.17, 4.18) the system had no problem finding the > correct firmware inside '/lib/firmware/radeon' > when using amdgpu driver. > Yeah that's introduced by commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8eaf2b1faaf4358c6337785f2192055c6ef41e0d Instead of copying all the content of /lib/firmware/radeon into /lib/firmware/amdgpu, could you: 1. Uninstall firmware-amd-graphics properly so /lib/firmware/radeon and /lib/firmware/amdgpu are empty 2. Re-install firmware-amd-graphics properly from archives (so, basically, these two steps undo your changes) 3. Copy only /lib/firmware/radeon/pitcairn_mc.bin to /lib/firmware/amdgpu/pitcairn_mc.bin Does this work for you ? Otherwise try to find messages in dmesg complaining about missing firmware for your amdgpu driver, then copy the right missing firmwares from /lib/firmware/radeon to /lib/firmware/amdgpu and then once it works, please paste a list here. Thanks in advance, Regards, Romain > > > > On 9/13/18 1:44 PM, felipe wrote: > > Today I had some spare time and I did some tests. > > > > On kernel 4.17 and 4.18 I can switch from radeonsi to amdgpu using/removing > > 'radeon.si_support=0 amdgpu.si_support=1' > > and the system finds and loads the relevant firmware in > > /lib/firmware/radeon, giving this system a boost in performance, > > correct HDMI output and no crashes. > > > > Booting kernel 4.19, the system could not load the relevant firmware when I > > tried to use amdgpu, but booted using radeonsi. > > > > Today I did copy all the firmware in '/lib/firmware/radeon' to > > '/lib/firmware/amdgpu' and the system booted in a working > > state and has been stable for the last hour. > > > > Since it is possible to use amdgpu with older GCN cards, the kernel should > > also look for the firmware inside > > '/lib/firmware/radeon' when using 'amdgpu' driver. > > > > > > '$ cat /var/log/syslog' of this working session with kernel 4.19-rc3 and > > 'cp /lib/firmware/radeon/* /lib/firmware/amdgpu'
Bug#908438: cubietruck wifi reversion
Hello, Could you retry with linux-image-4.18.0-1-armmp-lpae, please ? Thanks, Regards, Romain On Sun, Sep 09, 2018 at 06:24:41PM -0400, Joey Hess wrote: > Source: linux > Version: 4.17.17-1 > Severity: normal > > On a cubietruck board, the linux-image-4.17.0-3-armmp-lpae kernel kernel > fails to enable the builtin wifi: > > Sep 09 17:52:52 honeybee kernel: brcmfmac: brcmf_fw_alloc_request: using > brcm/brcmfmac43362-sdio for chip BCM43362/1 > Sep 09 17:52:52 honeybee kernel: usbcore: registered new interface driver > brcmfmac > Sep 09 17:52:52 honeybee kernel: brcmfmac mmc1:0001:1: firmware: > direct-loading firmware brcm/brcmfmac43362-sdio.bin > Sep 09 17:52:52 honeybee kernel: brcmfmac mmc1:0001:1: firmware: > direct-loading firmware brcm/brcmfmac43362-sdio.txt > Sep 09 17:52:55 honeybee kernel: brcmfmac: brcmf_sdio_bus_rxctl: resumed on > timeout > Sep 09 17:52:55 honeybee kernel: brcmfmac: brcmf_bus_started: failed: -110 > Sep 09 17:52:55 honeybee kernel: brcmfmac: brcmf_attach: dongle is not > responding: err=-110 > Sep 09 17:52:55 honeybee kernel: brcmfmac: brcmf_sdio_firmware_callback: > brcmf_attach failed > > This was working using linux-image-4.14.0-3-armmp-lpae and earlier kernels > including stable's, so seems to be a reversion. > > I have firmware-brcm80211 installed. I tried downgrading it to the same > version I was using with the older kernel (20170823-1), but that did not help, > so I don't think it's a problem with the firmware. > > Here it is working with the older kernel, for comparison: > > Sep 09 18:06:10 honeybee kernel: brcmfmac: brcmf_fw_map_chip_to_name: using > brcm/brcmfmac43362-sdio.bin for chip 0x00a962(43362) rev 0x01 > Sep 09 18:06:10 honeybee kernel: usbcore: registered new interface driver > brcmfmac > Sep 09 18:06:10 honeybee kernel: brcmfmac mmc1:0001:1: firmware: > direct-loading firmware brcm/brcmfmac43362-sdio.bin > Sep 09 18:06:10 honeybee kernel: brcmfmac mmc1:0001:1: firmware: > direct-loading firmware brcm/brcmfmac43362-sdio.txt > Sep 09 18:06:10 honeybee kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware > version = wl0: Apr 22 2013 14:50:00 version 5.90.195.89.6 FWID 01-b30a427d > > -- > see shy jo
Bug#908702: linux-image-4.18.0-1-amd64 prevents use of internet (more or less)
Hi, If reportbug is not usable for you, could you: - attach the output of "dmesg" to this bug - attach the output of "lspci" to this bug Please, Thanks, Romain On Wed, Sep 12, 2018 at 01:48:51PM -0400, g...@safe-mail.net wrote: > Package: linux-image-4.18.0-1-amd64 > Version: 4.18.6-1 > Severity: Grave > > > Dear maintainer, > > after today's upgrade from 4.17.0-3 to 4.18.0-1 internet access is hardly > possible anymore. Speed is less than 5 % of what is used to be and for that > reason the browser frequently shows "No internet connection" instead of a > webpage. > > Checking with another system at the same time shows that the internet > connection as such is working fine. Booting the system with the old kernel > 4.17.0-3 the problem does not arise, so the problem most probably is caused > by 4.18.0-1 (or a package used by 4.18.0-1 but not by 4.17.0-3) and not by > jointly used packages or hardware. Log files are identical as far as I can > see and my system is up to date (tracking testing, just missing the most > recent updates of irrelevant packages like libreoffice and vlc). Connection > to the internet is by LAN to a Huawei LTE router. > > Due to bug #908578 I could not use reportbug to file this bug. Sorry if this > means that some information is missing. > > Best regards > G. Heine
Bug#908248: Patch available but not part in mainstream
On Mon, Sep 10, 2018 at 08:15:29PM +, tomas.lac...@binaryx.eu wrote: > Hello team, > > There seems to be patch available, but not part of upstream kernel source yet > (checked against 4.18.7 git), provided by AMD employee. > Applied the patch listed from page below to 4.18.6 kernel from kernel.org and > no issues visible related to udev stuck as reported before. > > https://lore.kernel.org/patchwork/patch/974869/ > (https://lore.kernel.org/patchwork/patch/974869/) > > BRTL Hello, Merge request opened, see https://salsa.debian.org/kernel-team/linux/merge_requests/62 (it depends on previous opened merge request, just focus on the HEAD commit) Thanks, Regards, Romain
Bug#904428: linux-image-4.17.0-1-amd64: sound pops/clicks with snd_hda_intel unless power saving is disabled
Hi, Just to let you know that 4.18.0-1 (that is kernel 4.18.6) is now in sid, so you have to test this and no longer the one present in experimental. Thanks, Romain On Sat, Sep 08, 2018 at 04:27:16PM +0200, Salvatore Bonaccorso wrote: > tags 904428 + moreinfo > thanks > >
Bug#904428: linux-image-4.17.0-1-amd64: sound pops/clicks with snd_hda_intel unless power saving is disabled
Hi, See: 1. https://bugzilla.kernel.org/show_bug.cgi?id=200687 and 2. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/sound/pci/hda/hda_intel.c?id=38d9c12c0a6d41a82fb6d1278d430bbf35301ce5 as Hans de Goede said, this does not seems to be fixed in 4.17.x but it is part of 4.18.x . Could you test with 4.18.5-1~exp1 present in experimental ? If you don't know how to do this, feel free to ask, I can provide feedback. Thanks, Romain On Tue, Jul 24, 2018 at 10:32:26AM +0200, Gard Spreemann wrote: > Package: src:linux > Version: 4.17.8-1 > Severity: important > Tags: upstream > > Dear Maintainer, > > After upgrading from linux-image-4.16.0-2-amd64 to > linux-image-4.17.0-1-amd64, my computer's sound card exhibits an > audible and annoying pop or click when an audio stream is about to > play or stop playing. The pop/click was not present with earlier > kernels. > > Turning off power saving with > > options snd_hda_intel power_save=0 power_save_controller=N > > as per Redhat bug 1525104 [1] works around the problem (no pop/click). > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1525104 > > > -- Package-specific info: > ** Version: > Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version > 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20) > > ** Command line: > BOOT_IMAGE=/boot/vmlinuz-4.17.0-1-amd64 > root=UUID=546f4738-0d40-4e33-b17a-29b58fe436dd ro > > ** Not tainted
Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load
Hi, The last linux kernel in stretch being 4.9.110, could you re-test with this kernel please ? Thanks, Regards, Romain On Thu, Nov 30, 2017 at 11:54:00AM +, Tom Stocker wrote: > Package: src:linux > Version: 4.9.51-1 > Severity: serious > Justification: Policy 2.2.1 > > > > -- Package-specific info: > ** Version: > Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version > 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) > > ** Command line: > BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 > root=/dev/mapper/de--bln--vm--017--vg-root ro quiet > > ** Not tainted > > ** Kernel log: > [1.533757] EXT4-fs (dm-1): mounted filesystem with ordered data mode. > Opts: (null) > [1.847797] ip_tables: (C) 2000-2006 Netfilter Core Team > [1.912833] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT > +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS > +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) > [1.912859] systemd[1]: Detected virtualization vmware. > [1.912863] systemd[1]: Detected architecture x86-64. > [1.914546] systemd[1]: Set hostname to . > [2.058639] random: crng init done > [2.131752] systemd[1]: Set up automount Arbitrary Executable File Formats > File System Automount Point. > [2.131812] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. > [2.131843] systemd[1]: Listening on Syslog Socket. > [2.131885] systemd[1]: Started Forward Password Requests to Wall > Directory Watch. > [2.131920] systemd[1]: Listening on udev Control Socket. > [2.131955] systemd[1]: Started Dispatch Password Requests to Console > Directory Watch. > [2.363268] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro > [2.516531] systemd-journald[833]: Received request to flush runtime > journal from PID 1 > [2.819683] input: Power Button as > /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 > [2.819691] ACPI: Power Button [PWRF] > [2.819819] ACPI: AC Adapter [ACAD] (on-line) > [2.875315] input: PC Speaker as /devices/platform/pcspkr/input/input5 > [2.881700] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 > [2.881767] vmw_vmci :00:07.7: Using capabilities 0xc > [2.882410] Guest personality initialized and is active > [2.882410] VMCI host device registered (name=vmci, major=10, minor=58) > [2.882410] Initialized host personality > [2.930410] [drm] Initialized > [2.941291] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [2.941374] sd 0:0:1:0: Attached scsi generic sg1 type 0 > [2.941446] sd 0:0:2:0: Attached scsi generic sg2 type 0 > [2.941516] sd 0:0:3:0: Attached scsi generic sg3 type 0 > [2.941562] sr 2:0:0:0: Attached scsi generic sg4 type 5 > [3.012775] [drm] DMA map mode: Using physical TTM page addresses. > [3.012868] [drm] Capabilities: > [3.012873] [drm] Rect copy. > [3.012874] [drm] Cursor. > [3.012875] [drm] Cursor bypass. > [3.012876] [drm] Cursor bypass 2. > [3.012877] [drm] 8bit emulation. > [3.012878] [drm] Alpha cursor. > [3.012879] [drm] Extended Fifo. > [3.012880] [drm] Multimon. > [3.012881] [drm] Pitchlock. > [3.012882] [drm] Irq mask. > [3.012883] [drm] Display Topology. > [3.012884] [drm] GMR. > [3.012885] [drm] Traces. > [3.012886] [drm] GMR2. > [3.012887] [drm] Screen Object 2. > [3.012888] [drm] Command Buffers. > [3.012889] [drm] Command Buffers 2. > [3.012890] [drm] Guest Backed Resources. > [3.012891] [drm] DX Features. > [3.012893] [drm] Max GMR ids is 64 > [3.012894] [drm] Max number of GMR pages is 65536 > [3.012895] [drm] Max dedicated hypervisor surface memory is 0 kiB > [3.012896] [drm] Maximum display memory size is 4096 kiB > [3.012898] [drm] VRAM at 0xe800 size is 4096 kiB > [3.012899] [drm] MMIO at 0xfe00 size is 256 kiB > [3.012901] [drm] global init. > [3.013022] [TTM] Zone kernel: Available graphics memory: 60855752 kiB > [3.013023] [TTM] Zone dma32: Available graphics memory: 2097152 kiB > [3.013024] [TTM] Initializing pool allocator > [3.013029] [TTM] Initializing DMA pool allocator > [3.013122] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [3.013127] [drm] No driver support for vblank timestamp query. > [3.013382] [drm] Screen Target Display device initialized > [3.013441] [drm] width 640 > [3.013453] [drm] height 480 > [3.013465] [drm] bpp 32 > [3.014570] [drm] Fifo max 0x0004 min 0x1000 cap 0x077f > [3.015450] [drm] Using command buffers with DMA pool. > [3.015460] [drm] DX: no. > [3.015695] fbcon: svgadrmfb (fb0) is primary device > [3.017598] Console: switching to colour frame buffer device 100x37 > [3.096662] ppdev: user-space parallel port driver > [3.112337] [drm] Initialized vmwgfx 2.12.0
Bug#887102: Please add quirk US_FL_BROKEN_FUA JMS567-based USB3 UAS enclosure (152d:0578) to stretch debian kernels
On Sat, Jan 13, 2018 at 09:29:27PM +0100, Laurent GUERBY wrote: > Package: linux > Version: 4.9.65-3+deb9u > Severity: wishlist > > Hi, > > The quirk US_FL_BROKEN_FUA JMS567-based USB3 UAS enclosure > (152d:0578) has been added by this patch : > > https://patchwork.kernel.org/patch/10120851/ > > It has been included by upstream kernel 4.9.71 and 4.14.8 but isn't > available on released debian kernel stretch and stretch-backports. > > We have a debian stretch machine with this USB3 enclosure and we get > this kind of error which should be fixed by the quirk: > > https://unix.stackexchange.com/questions/237204/filesystem-is-reporting > -a-write-error-on-a-specific-sector-even-after-the-partit > > Thanks in advance for your help, > > Sincerely, > > Laurent Hi, The last linux kernel in stretch being 4.9.110, could you re-test with this kernel please ? Does it solve your problem ? Thanks, Romain
Bug#898267: [firmware-misc-nonfree] Missing firmware i915/kbl_dmc_ver1_04.bin
Hello, could you provide us the kernel logs ? By running dmesg or journalctl -b. Thanks On Wed, May 09, 2018 at 03:55:18PM +0300, Alexander Kernozhitsky wrote: > Package: firmware-misc-nonfree > Version: 20170823-1 > Severity: minor > > Linux kernel shows me the warning at boot time. It looks like "missing > firmware i915/kbl_dmc_ver1_04.bin", but the package contains i915/ > kbl_dmc_ver1_01.bin. A newer kernel requires 1.04 version. Please update the > firmware. > > --- System information. --- > Architecture: > Kernel: Linux 4.16.0-1-amd64 > > Debian Release: buster/sid > 990 testing ftp.by.debian.org > 500 unstableftp.by.debian.org > > --- Package information. --- > Package's Depends field is empty. > > Package's Recommends field is empty. > > Suggests (Version) | Installed > ==-+-=== > initramfs-tools| 0.130 > -- > - > Alexander Kernozhitsky
Bug#897590: linux-image-4.9.0-6-armmp: Missing CONFIG_MFD_TPS65217 may cause hardware damage
Hello, I have proposed a merge request for this at https://salsa.debian.org/kernel-team/linux/merge_requests/12 Thanks, Regards, Romain On Thu, May 03, 2018 at 10:03:14AM +, PA Nilsson wrote: > Package: src:linux > Version: 4.9.82-1+deb9u3 > Severity: grave > > Dear Maintainer, > > When shutting down BeagleBoneBlack, running Debian 9.3, it was > discovered that the system still draws excessive power and puts the > system out of spec with possible hardware damage as a result. > > This is due to the PMIC not shutting down correctly, as described by the > referenced posts: > http://bugs.elinux.org/issues/143 > https://groups.google.com/forum/#%21msg/beagleboard/7sxPePT7wkM/V1Ft-xxh0agJ > > This in turn is due to the driver for the PMIC is not avaialble since > CONFIG_MFD_TPS65217 is missing. > > Setting CONFIG_MFD_TPS65217 will enable the correct shutdown procedure. > > > > -- Package-specific info: > ** Version: > Linux version 4.9.0-6-armmp (debian-ker...@lists.debian.org) (gcc version > 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) > > ** Command line: > console=ttyO0,115200n8 root=/dev/mmcblk1p2 rw rootfstype=ext4 rootwait > > ** Not tainted > > ** Kernel log: > Unable to read kernel log; any relevant messages should be attached > > ** Model information > Hardware : Generic AM33XX (Flattened Device Tree) > Revision : > Device Tree model: TI AM335x BeagleBone Black > > ** Loaded modules: > dm_crypt > dm_mod > xts > gf128mul > algif_skcipher > af_alg > sd_mod > sg > uas > usb_storage > scsi_mod > fuse > snd_soc_simple_card > snd_soc_simple_card_utils > omap_aes > omap_sham > crypto_engine > omap_rng > rng_core > tilcdc > snd_soc_davinci_mcasp > snd_soc_omap > ledtrig_heartbeat > omap_hwspinlock > ledtrig_timer > tda998x > hwspinlock_core > snd_soc_core > snd_pcm_dmaengine > snd_pcm > drm_kms_helper > snd_timer > snd > soundcore > at24 > cppi41 > omap_wdt > drm > leds_gpio > cpufreq_dt > nvmem_core > nf_conntrack_ipv4 > nf_defrag_ipv4 > xt_tcpudp > xt_conntrack > nf_conntrack > iptable_filter > ip_tables > x_tables > autofs4 > ext4 > crc16 > jbd2 > crc32c_generic > fscrypto > ecb > mbcache > smsc > musb_dsps > musb_hdrc > udc_core > davinci_mdio > usbcore > phy_am335x > phy_generic > usb_common > phy_am335x_control > ti_cpsw > cpsw_ale > cpsw_common > davinci_cpdma > omap_hsmmc > musb_am335x > > ** PCI devices: > not available > > ** USB devices: > not available > > > -- System Information: > Debian Release: 9.4 > APT prefers stable > APT policy: (500, 'stable') > Architecture: armhf (armv7l) > > Kernel: Linux 4.9.0-6-armmp (SMP w/1 CPU core) > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C > (charmap=ANSI_X3.4-1968) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages linux-image-4.9.0-6-armmp depends on: > ii initramfs-tools [linux-initramfs-tool] 0.130 > ii kmod23-2 > ii linux-base 4.5 > > Versions of packages linux-image-4.9.0-6-armmp recommends: > pn firmware-linux-free > pn irqbalance > > Versions of packages linux-image-4.9.0-6-armmp suggests: > pn debian-kernel-handbook > pn linux-doc-4.9 > > Versions of packages linux-image-4.9.0-6-armmp is related to: > pn firmware-amd-graphics > pn firmware-atheros > pn firmware-bnx2 > pn firmware-bnx2x > pn firmware-brcm80211 > pn firmware-cavium > pn firmware-intel-sound > pn firmware-intelwimax > pn firmware-ipw2x00 > pn firmware-ivtv > pn firmware-iwlwifi > pn firmware-libertas > pn firmware-linux-nonfree > pn firmware-misc-nonfree > pn firmware-myricom > pn firmware-netxen > pn firmware-qlogic > pn firmware-realtek > pn firmware-samsung > pn firmware-siano > pn firmware-ti-connectivity > pn xen-hypervisor > > -- no debconf information
Bug#897204: linux-image-4.15.0-3-armmp: Please enable CONFIG_DRM_DW_HDMI_AHB_AUDIO=m and CONFIG_DRM_DW_HDMI_CEC=m
Hello, This has been fixed in https://salsa.debian.org/kernel-team/linux/commit/ff277a8c4c916aa022acd9a4201519cc995a1040. It will be part of linux-image-4.16.5-2-armmp. Regards, Romain On Mon, Apr 30, 2018 at 12:24:52AM +, Korbinian Rosenegger wrote: > Package: src:linux > Version: 4.15.17-1+local > Severity: wishlist > > Dear Maintainer, > > please enable these two options for supporting audio and CEC over HDMI on the > SolidRun Cubox-i > > CONFIG_DRM_DW_HDMI_AHB_AUDIO=m > CONFIG_DRM_DW_HDMI_CEC=m > > > At the moment I'm using a self compiled kernel package. > > > Thank you :) > > > Korbi > > > > > -- Package-specific info: > ** Version: > Linux version 4.15.0-3-armmp (debian-ker...@lists.debian.org) (gcc version > 7.3.0 (Debian 7.3.0-15)) #1 SMP Debian 4.15.17-1+local (2018-04-25) > > ** Command line: > root=/dev/mmcblk1p1 ro quiet cma=256M > > ** Tainted: O (4096) > * Out-of-tree module has been loaded. > > ** Kernel log: > Unable to read kernel log; any relevant messages should be attached > > ** Model information > Hardware : Freescale i.MX6 Quad/DualLite (Device Tree) > Revision : > Device Tree model: SolidRun Cubox-i Dual/Quad > > ** Loaded modules: > joydev > hid_generic > usbhid > brcmfmac > brcmutil > dw_hdmi_cec > cfg80211 > hid > dw_hdmi_ahb_audio > cec > rfkill > ahci_imx > libahci_platform > libahci > snd_soc_imx_spdif > snd_soc_fsl_spdif > imx_pcm_dma > libata > snd_soc_core > snd_pcm_dmaengine > ir_lirc_codec > lirc_dev > snd_pcm > scsi_mod > snd_timer > imx2_wdt > snd > soundcore > gpio_ir_recv > dw_hdmi_imx(O) > rc_core > pwm_imx > leds_pwm > imxdrm(O) > dw_hdmi(O) > imx_ipu_v3 > imx6q_cpufreq > etnaviv > tda998x > drm_kms_helper > drm > ip_tables > x_tables > autofs4 > ext4 > crc16 > mbcache > jbd2 > crc32c_generic > fscrypto > ecb > ci_hdrc_imx > ci_hdrc > ehci_hcd > sdhci_esdhc_imx > usbcore > sdhci_pltfm > i2c_imx > udc_core > sdhci > usb_common > usbmisc_imx > phy_mxs_usb > anatop_regulator > evdev > > ** PCI devices: > > ** USB devices: > Bus 002 Device 002: ID 062a:0102 Creative Labs Wireless Keyboard/Mouse Combo > [MK1152WC] > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > -- System Information: > Debian Release: buster/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') > Architecture: armhf (armv7l) > > Kernel: Linux 4.15.0-3-armmp (SMP w/4 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages linux-image-4.15.0-3-armmp depends on: > ii initramfs-tools [linux-initramfs-tool] 0.130 > ii kmod25-1 > ii linux-base 4.5 > > Versions of packages linux-image-4.15.0-3-armmp recommends: > pn apparmor > ii firmware-linux-free 3.4 > ii irqbalance 1.3.0-0.1 > > Versions of packages linux-image-4.15.0-3-armmp suggests: > pn debian-kernel-handbook > pn linux-doc-4.15 > > Versions of packages linux-image-4.15.0-3-armmp is related to: > ii firmware-amd-graphics 20170823-1 > pn firmware-atheros > pn firmware-bnx2 > pn firmware-bnx2x > ii firmware-brcm8021120170823-1 > pn firmware-cavium > pn firmware-intel-sound > pn firmware-intelwimax > pn firmware-ipw2x00 > pn firmware-ivtv > pn firmware-iwlwifi > pn firmware-libertas > ii firmware-linux-nonfree20170823-1 > ii firmware-misc-nonfree 20170823-1 > pn firmware-myricom > pn firmware-netxen > pn firmware-qlogic > pn firmware-realtek > pn firmware-samsung > pn firmware-siano > pn firmware-ti-connectivity > pn xen-hypervisor > > -- no debconf information
Bug#883294:
Hello, Could you : - Retry with linux-image 4.15, that is the current kernel in buster/sid - Instead of not using IO-APIC completly, could you try to boot with kernel parameter "no_timer_check" ? Does it help ? Thanks, Romain
Bug#446526: grub-installer: Patch : Fixed bug #442443
Package: grub-installer Version: 1.26 Severity: normal Tags: patch Please find to this link a patch which closes bug #442443 http://romain.perier.free.fr/debian/d-i_grub-installer_password_fix.patch -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (997, 'unstable'), (995, 'stable'), (993, 'stable'), (992, 'testing'), (990, 'testing'), (988, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442443: grub-installer: Path to fix it
Package: grub-installer Version: 1.26 Followup-For: Bug #442443 Please find to this link a patch to close this bug. http://romain.perier.free.fr/debian/d-i_grub-installer_password_fix.patch -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (997, 'unstable'), (995, 'stable'), (993, 'stable'), (992, 'testing'), (990, 'testing'), (988, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446267: ncurses-bin: missing libtic.so.5 with clear command line
Package: ncurses-bin Version: 5.6+20071006-2 Followup-For: Bug #446267 I've exactly the same problem when i try to launch 'clear' command line : clear: error while loading shared libraries: libtic.so.5: cannot open shared object file: No such file or directory -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (997, 'unstable'), (995, 'stable'), (993, 'stable'), (992, 'testing'), (990, 'testing'), (988, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ncurses-bin depends on: ii libc6 2.6.1-5GNU C Library: Shared libraries ii libncurses5 5.6+20071006-2 Shared libraries for terminal hand ncurses-bin recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#446120: gedit: Depends error on python-pygtksourceview
Package: gedit Version: 2.20.1-1 Severity: grave Justification: renders package unusable When i try to install gedit , apt returns an error dependency. python-pygtksourceview(=2.0.0) can't be found in any branchs. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (997, 'unstable'), (995, 'stable'), (993, 'stable'), (992, 'testing'), (990, 'testing'), (988, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gedit depends on: ii gconf2 2.20.0-1 GNOME configuration database syste ii gedit-common 2.20.1-1 official text editor of the GNOME ii iso-codes 1.5-1 ISO language, territory, currency, ii libart-2.0-2 2.3.19-3 Library of functions for 2D graphi ii libatk1.0-01.20.0-1 The ATK accessibility toolkit ii libc6 2.6.1-5 GNU C Library: Shared libraries ii libenchant1c2a 1.3.0-3+b1a wrapper library for various spel ii libgconf2-42.20.0-1 GNOME configuration database syste ii libglade2-01:2.6.2-1 library to load .glade files at ru ii libglib2.0-0 2.14.1-5 The GLib library of C routines ii libgnome2-02.20.0-1 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.20.0-1 A powerful object-oriented display ii libgnomeprint2.2-0 2.18.2-1 The GNOME 2.2 print architecture - ii libgnomeprintui2.2-0 2.18.1-1 GNOME 2.2 print architecture User ii libgnomeui-0 2.20.0-1 The GNOME 2 libraries (User Interf ii libgnomevfs2-0 1:2.20.0-2GNOME Virtual File System (runtime ii libgtk2.0-02.12.0-2 The GTK+ graphical user interface ii libgtksourceview1.0-0 1.8.5-1 shared libraries for the GTK+ synt ii libpango1.0-0 1.18.2-2 Layout and rendering of internatio ii libx11-6 2:1.0.3-7 X11 client-side library ii libxml22.6.30.dfsg-2 GNOME XML library ii python 2.4.4-6 An interactive high-level object-o ii python-glade2 2.12.0-1 GTK+ bindings: Glade support ii python-gnome2-desktop 2.20.0-1 Python bindings for the GNOME desk ii python-gtk22.12.0-1 Python bindings for the GTK+ widge ii python-support 0.7.4 automated rebuilding support for p ii python2.4 2.4.4-6 An interactive high-level object-o ii scrollkeeper 0.3.14-13 A free electronic cataloging syste Versions of packages gedit recommends: ii libgnomevfs2-bin 1:2.20.0-2 GNOME Virtual File System (support ii python-gnome2 2.20.0-1 Python bindings for the GNOME desk ii zenity2.20.0-2 Display graphical dialog boxes fro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445691: usplash: No usable theme found for 1280x800
Package: usplash-theme-debian Version: 4 Severity: important Tags: patch When i try to boot in vga=791 with quiet splash grub option usplash crashs and print to stdout usplash: No usable theme found for 1280x800 screen init failed. themesetup.sh init script doesn't detect 1280x800 to 16:9 (normally 16:10) but 4:3 (1280 / 16 != 800 / 9). In libusplash.c (usplash-0.5.2-3 source) Line 491 : if (theme-pixmap-height = yres theme-pixmap-width = xres theme-pixmap-height * theme-pixmap-width maxarea theme-ratio == ratio) == ratio aspect for 1280x800 is 1.7 (1.55 -- UPLASH_16_9) but with initial script themesetup.sh ratio aspect for 1280x800 resolution is 4_3 , finally theme-ratio != ratio and htheme refers NULL pointer and theme too. i created an small patch to fix it , it's work ! :) you can find path here : http://romain.perier.free.fr/debian/usplash-theme-debian_fix_ratio.diff -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages usplash depends on: ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy ii initramfs-tools 0.91b tools for generating an initramfs ii libc6 2.6.1-5GNU C Library: Shared libraries ii libusplash0 0.5.2-3userspace bootsplash library ii usplash-theme-debian [usplash 4.tatooDebian usplash theme usplash recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445692: usplash: No usable theme found for 1280x800
Package: usplash-theme-debian Version: 4 Severity: important Tags: patch When i try to boot in 1280x800 resolution with quiet splash grub option usplash print to stdout : usplash: No usable theme found for 12800x800 script init failed So themesetup.sh init script doesn't detect 1280x800 as 16:9 ratio (normally 16:10) but to 4:3. If you refer to libusplash.c in usplash-0.5.2-3 Line 491 : if (theme-pixmap-height = yres theme-pixmap-width = xres theme-pixmap-height * theme-pixmap-width maxarea theme-ratio == ratio) == theme-ratio != ratio Finally htheme refers to NULL pointer and theme too (line 503) that's why i created an small patch to fix it , it's work ! :) please find path here : http://romain.perier.free.fr/debian/usplash-theme-debian_fix_ratio.diff -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages usplash-theme-debian depends on: ii libc6 2.6.1-5GNU C Library: Shared libraries usplash-theme-debian recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443672: /usr/bin/gnome-session-properties: Freeze when i added new programm startup
Package: gnome-session Version: 2.18.3-1 Severity: important File: /usr/bin/gnome-session-properties When i try to add new programm startup (for example gdesklets) on my own session i enter which command line to launch to start programm (i found path in graphical mode) and suddenly gnome-session-properties freeze -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-session depends on: ii gconf2 2.18.0.1-3 GNOME configuration database syste ii gnome-control-center1:2.18.1-1 utilities to configure the GNOME d ii libatk1.0-0 1.18.0-2 The ATK accessibility toolkit ii libbonobo2-02.18.0-2 Bonobo CORBA interfaces library ii libc6 2.6.1-1 GNU C Library: Shared libraries ii libdbus-1-3 1.1.1-3 simple interprocess messaging syst ii libdbus-glib-1-20.74-1 simple interprocess messaging syst ii libesd0 0.2.36-3 Enlightened Sound Daemon - Shared ii libgconf2-4 2.18.0.1-3 GNOME configuration database syste ii libglib2.0-02.14.0-2 The GLib library of C routines ii libgnome-desktop-2 2.18.3-1 Utility library for loading .deskt ii libgnome-keyring0 0.8.1-2 GNOME keyring services library ii libgnome2-0 2.18.0-4 The GNOME 2 library - runtime file ii libgnomeui-02.18.1-2 The GNOME 2 libraries (User Interf ii libgtk2.0-0 2.10.13-1The GTK+ graphical user interface ii libice6 2:1.0.4-1X11 Inter-Client Exchange library ii liborbit2 1:2.14.7-0.1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.18.1-1 Layout and rendering of internatio ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libwrap07.6.dbs-14 Wietse Venema's TCP wrappers libra ii libx11-62:1.0.3-7X11 client-side library ii libxau6 1:1.0.3-2X11 authorisation library ii libxrandr2 2:1.2.2-1X11 RandR extension library Versions of packages gnome-session recommends: ii dbus 1.1.1-3simple interprocess messaging syst ii desktop-base 4.0.3 common files for the Debian Deskto ii gnome-panel 2.18.3-2 launcher and docking facility for ii metacity 1:2.18.5-1 A lightweight GTK2 based Window Ma ii nautilus 2.18.3-3 file manager and graphical shell f -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
