On Sun 05 Mar 2023 at 20:57:25 (+), Albretch Mueller wrote:
> On 3/5/23, David Wright wrote:
> >
> > I run installed systems, so wifi passwords are either in individual
> > /var/lib/iwd/.psk files (with iwd), or collectively in
> > /etc/wpa_supplicant/.conf (with
David Wright writes:
> So what was wrong with using a .link file like:
>
> [Match]
> Type=wwan
> [Link]
> NamePolicy=keep kernel
>
> or
>
> [Match]
> Type=wwan
> [Link]
> Name=my4g
>
> Did this not work?
Nothing was wrong but I just added a few lines to my management script
to
On 3/5/23, David Wright wrote:
> On Sun 05 Mar 2023 at 02:42:46 (+), Albretch Mueller wrote:
>> On 3/4/23, David Wright wrote:
>> > Also, now that the firmware is in place, if you repeat those steps,
>> > you're /likely/ to find that ath10k_pci is busy, because the link
>> > will be
On Sun 05 Mar 2023 at 21:22:10 (+0200), Anssi Saari wrote:
> Curt writes:
>
> > * UNPREDICTABILITY
> > it turns out even after all this [**an enumeration of complications and
> > corner
> > cases**] there are still reported cases of interfaces changing their name
> > on a
> > reboot.
>
> I
On Sun 05 Mar 2023 at 02:42:46 (+), Albretch Mueller wrote:
> On 3/4/23, David Wright wrote:
> > Also, now that the firmware is in place, if you repeat those steps,
> > you're /likely/ to find that ath10k_pci is busy, because the link
> > will be configured automatically in the first few
I thought “unpredictability” was the name of my daily drama show, but
apparently “I am not the only one”. Yes, I know javascript is the
primary vector they use to mess with whomever they choose, regardless
of if they wear a “tiny tin hat” or expensive shoes.
In my case, among many other things,
On Sun, Mar 05, 2023 at 09:22:10PM +0200, Anssi Saari wrote:
> I have just this fun kind of unpredictability in my router's 4G
> module. Mostly, it comes up as wwan0 but sometimes it's wwx. So
> I put something in my 4G management script to rename such interface if
> there's no wwan0.
If you're
Curt writes:
> * UNPREDICTABILITY
> it turns out even after all this [**an enumeration of complications and corner
> cases**] there are still reported cases of interfaces changing their name on a
> reboot.
I have just this fun kind of unpredictability in my router's 4G
module. Mostly, it comes
2023-03-04, Jeffrey Walton wrote:
> On Sat, Mar 4, 2023 at 12:12 PM David Wright wrote:
>>
>> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
>> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
>> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
>> > > >
On 3/4/23, David Wright wrote:
> Also, now that the firmware is in place, if you repeat those steps,
> you're /likely/ to find that ath10k_pci is busy, because the link
> will be configured automatically in the first few seconds after
> booting up.
I would always go into exposed mode using a DL
On Sat, Mar 4, 2023 at 12:12 PM David Wright wrote:
>
> On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> > On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
> > > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > > The 'p' is a pci bus, the 's' is a slot
On Sat 04 Mar 2023 at 01:02:54 (-0500), Jeffrey Walton wrote:
> On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
> > On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > > does not move around once
On Sat 04 Mar 2023 at 00:03:16 (+), Albretch Mueller wrote:
> On 3/3/23, David Wright wrote:
> >
> > Try removing the atheros module with:
> >
> > # rmmod ath10k_pci
> >
> > (check its name in /proc/modules), and then reload it with
> >
> > # modprobe ath10k_pci
> >
> > and check dmesg
On 3/3/23, Dan Ritter wrote:
> ... the messages you
> are seeing are from the first 88.2 seconds after boot.
Most probably and luckily no one has reported such problems, but from
the corner from which I see reality it may as well be not "after
boot". I haven't exactly timed it (I will when I
On Fri, Mar 03, 2023 at 06:09:40PM -0500, Greg Wooledge wrote:
> On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > does not move around once installed, the interface will always have
> > the same name like
On Fri, Mar 3, 2023 at 6:10 PM Greg Wooledge wrote:
>
> On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> > The 'p' is a pci bus, the 's' is a slot number. Since the interface
> > does not move around once installed, the interface will always have
> > the same name like 'enp4s0'.
On 3/3/23, David Wright wrote:
>
> Try removing the atheros module with:
>
> # rmmod ath10k_pci
>
> (check its name in /proc/modules), and then reload it with
>
> # modprobe ath10k_pci
>
> and check dmesg again.
Bingo! Those were the steps that enable me to see the wireless
network with
On Fri, Mar 3, 2023 at 6:36 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
>
>
> On Fri, Mar 3, 2023 at 4:45 PM Albretch Mueller wrote:
>
>> since it was included in the Linux kernel anyway I (apparently
>> wrongly) thought I didn't have to install any packages. After
>>
On Fri, Mar 3, 2023 at 4:45 PM Albretch Mueller wrote:
> since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
>
> $ sudo dpkg --install
On Fri, Mar 03, 2023 at 05:45:54PM -0500, Jeffrey Walton wrote:
> The 'p' is a pci bus, the 's' is a slot number. Since the interface
> does not move around once installed, the interface will always have
> the same name like 'enp4s0'.
That's a wonderful idea, but it doesn't quite work in
On Fri, Mar 3, 2023 at 10:46 AM Albretch Mueller wrote:
>
> [...]
> $ sudo lshw -class network
> *-network DISABLED
>description: Ethernet interface
>product: RTL810xE PCI Express Fast Ethernet controller
>vendor: Realtek Semiconductor Co., Ltd.
>physical id: 0
On Fri 03 Mar 2023 at 21:45:27 (+), Albretch Mueller wrote:
> since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
>
> $ sudo dpkg --install
Albretch Mueller wrote:
> since it was included in the Linux kernel anyway I (apparently
> wrongly) thought I didn't have to install any packages. After
> downloading and installing the required firmware:
>
> $ sudo dpkg --install firmware-atheros_20210315-3_all.deb
> Selecting previously
since it was included in the Linux kernel anyway I (apparently
wrongly) thought I didn't have to install any packages. After
downloading and installing the required firmware:
$ sudo dpkg --install firmware-atheros_20210315-3_all.deb
Selecting previously unselected package firmware-atheros.
Am Fri, Mar 03, 2023 at 05:01:49PM + schrieb Albretch Mueller:
> On 3/3/23, Timothy M Butterworth wrote:
> > Just run `ip link` or `ip address` and it will show you the name.
In addition what Tim suggests:
You could run dmesg and search for ath, wifi, wlan, wlp or so.
In my case the output
On Fri, Mar 3, 2023 at 12:01 PM Albretch Mueller wrote:
> On 3/3/23, Timothy M Butterworth wrote:
> > Just run `ip link` or `ip address` and it will show you the name.
>
> I had already done so, but I don't see the "logical name" or the IP
> of the wireless interface on my very "temperamental"
On 3/3/23, Timothy M Butterworth wrote:
> Just run `ip link` or `ip address` and it will show you the name.
I had already done so, but I don't see the "logical name" or the IP
of the wireless interface on my very "temperamental" DELL Inspiron
which seems to have a mind of its own. I only see
On Fri, Mar 3, 2023 at 10:46 AM Albretch Mueller wrote:
> $ sudo lspci | grep --ignore-case Wireless
> 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless
> Network Adapter (rev 31)
> $
>
> $ sudo lshw -class network
> *-network DISABLED
>description: Ethernet
28 matches
Mail list logo
