For me the problem was solved after updating to kernel 6.1.5
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/
On Sat, 14 Jan 2023 20:39:49 +0100
lejeczek via users wrote:
> I wonder now, if it is possible, nowadays, to "bypass"
> systemd's resolver - except if a separate DNS server is ran
> locally.
Just disable (and mask for belt and suspenders) systemd-resolved.
Then edit /etc/NetworkManager/NetworkM
On 14/01/2023 19:43, Barry wrote:
On 14 Jan 2023, at 17:02, lejeczek via users
wrote:
On 11/01/2023 13:15, Jouk via users wrote:
Hi all,
Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After
rebooting no nameservers are found at the end of
/run/systemd/resoilve/res
> On 14 Jan 2023, at 17:02, lejeczek via users
> wrote:
>
>
>
>> On 11/01/2023 13:15, Jouk via users wrote:
>> Hi all,
>>
>> Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After
>> rebooting no nameservers are found at the end of
>> /run/systemd/resoilve/resolv.conf.
>
On 11/01/2023 13:15, Jouk via users wrote:
Hi all,
Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After
rebooting no nameservers are found at the end of
/run/systemd/resoilve/resolv.conf.
I found 2 ways to get the name resolve work again:
-reboot in kernel 6.0.16
On 12/01/2023 07:17, Jouk via users wrote:
I have check two systems both on 6.0.16-300.fc37.x86_64
Note that with kernel 6.016 I also had no problems. The problems occurred when
booting into kernel 6.0.18.
Both systemd-networkd and NetworkManager machines work with 6.0.18 for me.
What servi
> On 12 Jan 2023, at 07:17, Jouk via users
> wrote:
>
>
>>
>> I have check two systems both on 6.0.16-300.fc37.x86_64
> Note that with kernel 6.016 I also had no problems. The problems occurred
> when booting into kernel 6.0.18.
I will be doing my weekly update tomorrow and will report wh
> I have check two systems both on 6.0.16-300.fc37.x86_64
Note that with kernel 6.016 I also had no problems. The problems occurred when
booting into kernel 6.0.18.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to u
On 11/01/2023 12:15, Jouk via users wrote:
Hi all,
Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After
rebooting no nameservers are found at the end of
/run/systemd/resoilve/resolv.conf.
I found 2 ways to get the name resolve work again:
-reboot in kernel 6.0.16
Hi all,
Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After
rebooting no nameservers are found at the end of
/run/systemd/resoilve/resolv.conf.
I found 2 ways to get the name resolve work again:
-reboot in kernel 6.0.16
-Change the internet adapter configuration from
10 matches
Mail list logo