On Tuesday, June 8, 2021, 7:07:47 PM EDT, Dan Ritter
wrote:
Try:
rfkill list
-dsr-
root@debian:~# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Long Wind wrote:
> Thank Dan!i run dmesg:
> [ 5.169069] usb 1-1: reset high-speed USB device number 2 using ehci-pci
> [ 5.326955] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3070, rev
> 0201 detected
> [ 5.359584] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
> [
On Ma, 08 iun 21, 12:05:21, Thom Castermans wrote:
>
> - Installed non-free firmware (used the unofficial image [1]) during
> installation and installed the intel-microcode package after installation
> in an attempt to fix the error displayed in [4] ("[Firmware Bug]:
> TSC_DEADLINE d
On Tuesday 08 June 2021 18:09:34 Martin McCormick wrote:
> I did it! It works!
>
> Okay. Here's the short story. I read some more stuff
> about building a boot drive for another system than the one being
> used for the rescue. In this thread were the usual tales of woe
> which I have als
I did it! It works!
Okay. Here's the short story. I read some more stuff
about building a boot drive for another system than the one being
used for the rescue. In this thread were the usual tales of woe
which I have also experienced when misusing grub such as "Oh
#%^*! Now I've got 2 s
Long Wind wrote:
> https://wiki.debian.org/rt2800usb
> i've set up driver above many times, they all work except this time
> this time it's installed on stretch for i386below is setup in interfaces file
>
> iface wlx0022c0001a95 inet dhcp
> wpa-ssid WiFi-950
> wpa-key-mgmt NONE
> i run "ifup wlx
https://wiki.debian.org/rt2800usb
i've set up driver above many times, they all work except this time
this time it's installed on stretch for i386below is setup in interfaces file
iface wlx0022c0001a95 inet dhcp
wpa-ssid WiFi-950
wpa-key-mgmt NONE
i run "ifup wlx0022c0001a95"
Internet Systems Con
[Wanderer wrote:]
> It really does sound like he's been doing multiple reinstalls, and even
> probably reinstalled buster after the latest failed install of testing (snip)
This is correct: I reinstalled Bullseye a few times and am currently using a
fresh Buster install (with non-free firmware).
Hi.
On Tue, Jun 08, 2021 at 04:44:35PM +0500, Alexander V. Makartsev wrote:
> > How can I debug this problem? My suspicion is that this has to do with the
> > kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>
> The way I would approach this problem is by making
On Tue, Jun 08, 2021 at 04:44:35PM +0500, Alexander V. Makartsev wrote:
> There was an intention from a systemd developers to make persistent logs the
> default, but I'm unsure if that change made it into Debian already.
Unless something changed that I'm unaware of, new installs of bullseye
should
On Tue, Jun 08, 2021 at 07:43:30AM -0400, The Wanderer wrote:
> On 2021-06-08 at 07:27, Greg Wooledge wrote:
> > The first and most obvious thing you should try is booting the buster
> > kernel, and seeing whether the problem still occurs. This will let
> > you know whether the problem is in the k
On 08.06.2021 15:05, Thom Castermans wrote:
Dear Debian users,
Recently I installed Debian on an ASUS UX501J laptop. Debian stable (Buster)
works flawlessly (I'm using that now), but when I tried to upgrade to testing,
things started going wrong. I would get random kernel panics and other errors
On 2021-06-08 at 07:27, Greg Wooledge wrote:
> On Tue, Jun 08, 2021 at 12:05:21PM +0200, Thom Castermans wrote:
>
>> How can I debug this problem? My suspicion is that this has to do with the
>> kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>>
>> Things I have tried
On Tue, Jun 08, 2021 at 12:05:21PM +0200, Thom Castermans wrote:
> How can I debug this problem? My suspicion is that this has to do with the
> kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>
> Things I have tried so far:
> - Ran smartctl test on the SSD: no issues
Dear Debian users,
Recently I installed Debian on an ASUS UX501J laptop. Debian stable (Buster)
works flawlessly (I'm using that now), but when I tried to upgrade to testing,
things started going wrong. I would get random kernel panics and other errors
on boot. Thinking I may have done something w
On Mon, 7 Jun 2021 18:11:13 -0400
Greg Wooledge wrote:
> On Mon, Jun 07, 2021 at 06:08:39PM -0400, rhkra...@gmail.com wrote:
> > Thanks for the reply -- not quite, comments interspersed below:
> >
> > On Monday, June 07, 2021 04:38:24 PM Greg Wooledge wrote:
> > > On Mon, Jun 07, 2021 at 04:28
16 matches
Mail list logo
