I think this is the driver for the WiFi part of the Mediatek 7921 chip:
https://github.com/torvalds/linux/tree/master/drivers/net/wireless/mediatek/mt76/mt7921
No idea if this also is the home of the bluetooth driver, but I suspect
it is, because I couldn't find any mention of the 7921 chip else
I removed bluetooth support from the laptop on April 10 2023, and WLAN
provided by the Mediatek 7921 chip has been working flawlessly since
then for, at the time of writing, 28 days, with numerous suspends and
resumes.
To me this strongly indicates that using bluetooth was the problem,
especially
Package: src:linux
Version: 6.1.12-1~bpo11+1
Severity: normal
X-Debbugs-Cc: s...@dod.no
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I bought a Logitech MX Master 3S wireless mouse.
The mouse came with both an
I have had two kernel upgrades since I reported this bug:
linux-image-4.8.0-0.bpo.2-amd64 4.8.15-2~bpo8+2
linux-image-4.9.0-0.bpo.1-amd64-unsigned 4.9.2-2~bpo8+1
Both kernels have had the same symptoms:
- Get the display during boot, so that I can access the Grub menu and
choose the
> Ben Hutchings :
> But this motherboard apparently doesn't have a DisplayPort. Perhaps
> the driver is confused about this.
> Which type of connector is the monitor really plugged into?
A VGA connector.
Here is the /var/log/Xorg.0.log file from the black screen situation:
[ 4.620]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[ 4.620] X Protocol Version 11, Revision 0
[ 4.620] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 4.620] Current Operating System: Linux lor
Package: src:linux
Version: 4.8.11-1~bpo8+1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
"apt-get dist-upgrade" pulled in a new kernel and after the reboot the display
was completely black
> Ben Hutchings :
> Which package and version were you previously using?
I don't know the exact package, but the kernel version was Linux 4.0.0-2-686-pae
(the one that had been up for 64 days in the uprecords output below):
# Uptime | System
Package: src:linux
Version: 4.2.1-2
Severity: grave
Justification: renders package unusable
"apt-get dist-upgrade" installed the kernel
linux-image-4.2.0-1-686-pae (4.2.1-2) on Sun Oct 4 2015, 12:06:36.
Since then, the system has frozen twice.
When frozen, the system is completely unresponsive
New kernel installed by apt-get dist-upgrade on Nov 1 2014
(linux-image-3.2.0-4-686-pae 3.2.63-2+deb7u1), but looks like the same
crash (same stack trace).
This was in /var/log/kern.log and on the computer's console, after the
crash:
Nov 12 16:43:49 doohan kernel: [976755.030051] [ cut
Package: src:linux
Version: 3.2.60-1+deb7u3
Severity: normal
Dear Maintainer,
* What led up to the situation?
The computer was running as a NAT bridge and firewall between the
internet and my home LAN.
The computer crashed with the following output in /var/log/kern.log and on the
computers c
>>>>> Steinar Bang :
> I then installed Bjørn's kernel with
> dpkg --install linux-image-3.2.0-4-686-pae_3.2.39-2a~test_i386.deb
> At the time of writing I have been running this kernel for 10 hours and
> 40 minutes.
I have now been running a kernel with Bjørn&
> Bjørn Mork :
> I am attaching a proposed fix on top of the 655152 patch, which I have
> not tested at all on actual Debian kernel sources. Might need context
> adjustments. I'd appreciate it if anyone with crashing hardware could
> test it.
FYI: I have failing hardware and am in the proce
> Ben Hutchings :
> Please send a readable photograph of this text.
The problem occurred for the third time, and I couldn't find the camera,
so I'm typing in what's shown on the console.
This time it had happened while the macine was sitting unmanned and I
can't say it had anything to do wit
Package: src:linux
Version: 3.2.32-1
Severity: important
Dear Maintainer,
Twice, since apt-get dist-upgrade installed this kernel, the machine
has crashed when coming out of screen saver. That's twice in a short
number of days.
What's shown is a screen of text, saying something about "Panic
exi
> Bastian Blank <[EMAIL PROTECTED]>:
> No, it is usualy not the same. The Cisco client defaults to NAT
> traversal.
The client machine is a laptop with Ubuntu Feisty, which has vpnc
0.4.0.
"vpnc -h" gives me the following information on nat-t:
...
--natt-mode
NAT Traversal Mode
Package: linux-image-2.6.18-5-686
Version: 2.6.18.dfsg.1-13etch1
Severity: important
The debian machine functions as a gateway between my home LAN (using a
10.10.10.* private network), and the outside world. When the gateway
was using sarge and a 2.4 kernel, VPNC from inside clients worked
withou
Package: kernel-image-2.6.8-1
Version: 2.6.8-10
After an upgrade from whatever previous version of kernel-image-2.6.8-1
was on my system (APT really should have some logging) to version
2.6.8-10, the touchpad mouse became unresponsive, and keyboard input
became sluggish. So sluggish that it was u
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
>> Platform: Intel Pentium M (Dell Latitude D600),
>> debian sarge (testing/unstable),
>> VMware-workstation-4.5.1-7568,
>> kernel-image-2.6.3-1-686 2.6.3-2
>>
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> Platform: Intel Pentium M (Dell Latitude D600),
> debian sarge (testing/unstable),
> VMware-workstation-4.5.1-7568,
> kernel-image-2.6.3-1-686 2.6.3-2
> kernel-headers-2.6.3-1 2.6.3-2
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> The installation failed with trying to compile the headers. The
> relevant parts of the output from the installation script, is attached
> below.
Some comments on the error messages:
> Your kernel was built with &qu
Platform: Intel Pentium M (Dell Latitude D600),
debian sarge (testing/unstable),
VMware-workstation-4.5.1-7568,
kernel-image-2.6.3-1-686 2.6.3-2
kernel-headers-2.6.3-1 2.6.3-2
kernel-headers-2.6.3-1-686 2.6.3-2
libc6 2.3.2.ds1-11
22 matches
Mail list logo