Am 21.03.2025 um 12:21:37 Uhr schrieb Robert McBroom via users:
> What does it mean that the RTL8812AU device is seen but not enabled?
Check if the kernel module is being loaded.
lsusb -t
--
Gruß
Marco
Send unsolicited bulk mail to 1742556097mu...@cartoonies.org
--
On 3/22/25 7:31 AM, George N. White III wrote:
On Fri, Mar 21, 2025 at 1:22 PM Robert McBroom via users
wrote:
Have two usb wifi adapters using Realtek chips that were noted to be supported
in the recent kernels. One is now seen but the other is not. Both show in the
list from
lsusb
Bus 00
On Fri, Mar 21, 2025 at 1:22 PM Robert McBroom via users
wrote:
>
> Have two usb wifi adapters using Realtek chips that were noted to be
> supported in the recent kernels. One is now seen but the other is not. Both
> show in the list from
>
> lsusb
>
> Bus 001 Device 002: ID 0bda:8812 Realtek Se
On Sun, Sep 29, 2024 at 10:51 AM Zerotwo02
wrote:
> Good day, are these tests only concerned with systems running Fedora 40
> and 39? Or is there any testing needed to be done by systems running on
> Fedora 41?
> Regards
> Vaishnav R
>
>
The testday iso is
https://jforbes.fedorapeople.org/testwee
Hey!
Started to help out a bit on gnome-boxes this morning
the performance test suite is still broken however, and 6.10.2 is not yet
built to test however, but helping out a bit with the 6.10.1 testing
Den lör 27 juli 2024 kl 19:16 skrev Sumantro Mukherjee :
> Hey All,
>
> I would like to invit
On 6/28/24 11:25 AM, Jeffrey Walton wrote:
Another one to avoid: cheap SSDs with duplicate serial numbers. Some
manufacturers repeat (clone?) serial numbers, and when you try to use
them in a RAID configuration, things go badly. A fellow on a Ubuntu
list struggled for months because of it.
That
On 2024-06-28 14:25, Jeffrey Walton wrote:
Another one to avoid: cheap SSDs with duplicate serial numbers. Some
manufacturers repeat (clone?) serial numbers, and when you try to use
them in a RAID configuration, things go badly. A fellow on a Ubuntu
list struggled for months because of it.
At
On Fri, Jun 28, 2024 at 2:10 PM Frank Bures wrote:
>
> On 2024-06-23 11:43, Frank Bures wrote:
> > On 2024-06-23 04:29, Tim wrote:
>
> > I followed
> >
> > https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configuration_on_UEFI_systems
> >
> > and then I tried to run
> > grub2-emu
> >
On 2024-06-23 11:43, Frank Bures wrote:
On 2024-06-23 04:29, Tim wrote:
I followed
https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configuration_on_UEFI_systems
and then I tried to run
grub2-emu
I get the list of installed kernels OK, but any choice for boot returns
error: .
On 2024-06-23 04:29, Tim wrote:
On Sat, 2024-06-22 at 23:54 -0400, Frank Bures wrote:
This is what my efibootmgr returns:
root@ryzen:/# efibootmgr
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,,0001
Boot Fedora
HD(1,GPT,e8838c34-c364-4347-afb7-1c516782b114,0x800,0x12c000)/\EFI\
On Sat, 2024-06-22 at 23:54 -0400, Frank Bures wrote:
> This is what my efibootmgr returns:
>
> root@ryzen:/# efibootmgr
> BootCurrent: 0002
> Timeout: 1 seconds
> BootOrder: 0002,,0001
> Boot Fedora
> HD(1,GPT,e8838c34-c364-4347-afb7-1c516782b114,0x800,0x12c000)/\EFI\FEDORA\SHIMX64.EFI
On 2024-06-22 20:59, Frank Bures wrote:
Hi,
I just did a kernel update and after reboot I ended up in a grub prompt.
I booted from USB F40 and followed instructions at
https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_restoring_the_bootloader_using_the_live_disk
However, what
Helped today, was supposed to help earlier this week, but was too busy
but better late then never as deadline is not until Sunday
Den mån 25 mars 2024 kl 04:44 skrev Sumantro Mukherjee :
>
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 6.8
> Test week is happening fr
Hey!
And happy new year too you too and all other Fedora testers, should be
able to help out with this :)
Den mån 15 jan. 2024 kl 13:29 skrev Sumantro Mukherjee :
>
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 6.7
> Test week is happening from 2024-01-21 to 2024-0
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Wednesday, November 29th, 2023 at 9:28 AM, old sixpack13
wrote:
> ...
>
> > olivares@fedora:~$ sudo dnf remove kernel-6.6*
>
> ...
>
> you should use
> sudo dnf remove kernel-core-x.y.z
>
...
> olivares@fedora:~$ sudo dnf remove kernel-6.6*
...
you should use
sudo dnf remove kernel-core-x.y.z
to get rid of all packages belonging to the kernel
kernel-core is a meta package
===
I also own a RocketLake-S.
No problems here
any error message during kernel install ?
--
On Wed, Nov 29, 2023 at 11:01 AM olivares33561 via users <
users@lists.fedoraproject.org> wrote:
>
> On Wednesday, November 29th, 2023 at 8:49 AM, Patrick O'Callaghan <
> pocallag...@gmail.com> wrote:
>
>
> > On Wed, 2023-11-29 at 14:28 +, olivares33561 via users wrote:
> >
> > > Dear fellow f
g non-free packages with akmods? One common issue with
> command-line updates is rebooting
> before the non-free package install is complete.
>
> --
Your mail to 'users@lists.fedoraproject.org' with the subject
Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs
I
On Wednesday, November 29th, 2023 at 8:49 AM, Patrick O'Callaghan
wrote:
> On Wed, 2023-11-29 at 14:28 +, olivares33561 via users wrote:
>
> > Dear fellow fedora users,
> >
> > upon updating and rebooting the new kernel refuses to boot or just
> > hangs. How do I troubleshoot this issue?
On Wed, Nov 29, 2023 at 10:28 AM olivares33561 via users <
users@lists.fedoraproject.org> wrote:
> Dear fellow fedora users,
>
> upon updating and rebooting the new kernel refuses to boot or just hangs.
> How do I troubleshoot this issue?
> I have to boot 6.5.12-300 so I can use the computer.
>
O
On Wed, 2023-11-29 at 14:28 +, olivares33561 via users wrote:
> Dear fellow fedora users,
>
> upon updating and rebooting the new kernel refuses to boot or just
> hangs. How do I troubleshoot this issue?
> I have to boot 6.5.12-300 so I can use the computer.
Not enough information to go on.
On Wed, 29 Nov 2023 14:28:02 +
olivares33561 via users wrote:
> Dear fellow fedora users,
>
> upon updating and rebooting the new kernel refuses to boot or just
> hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300
> so I can use the computer.
It is possible that the kernel
> Dear fellow fedora users,
>
> upon updating and rebooting the new kernel refuses to boot or just hangs. How
> do I troubleshoot this issue?
> I have to boot 6.5.12-300 so I can use the computer.
>
> Thanks in Advance,
>
>
> Antonio
>
> Sent from ProtonMail, encrypted email based in Switze
And now done with the last kernel testing for this test week :)
Den tors 13 juli 2023 kl 08:26 skrev Luna Jernberg :
>
> Did run a test yesterday, and will run some more tests this week until
> Sunday as much as i have time
>
> Den ons 12 juli 2023 kl 18:03 skrev Sumantro Mukherjee :
> >
> > Hey F
Did run a test yesterday, and will run some more tests this week until
Sunday as much as i have time
Den ons 12 juli 2023 kl 18:03 skrev Sumantro Mukherjee :
>
> Hey Folks,
>
> We are currently running the Fedora Kernel Test Week before we rebase
> 6.4. There is a new
> build 6.4.3 is fresh and yo
6.4.2 testing in progress
Den sön 9 juli 2023 kl 14:56 skrev Luna Jernberg :
>
> Hey!
>
> I can join in and help the testing later today and during next week as
> much as i have time do so :)
>
> Den sön 9 juli 2023 kl 13:27 skrev Sumantro Mukherjee :
> >
> > Hey All,
> >
> > I would like to invit
Hey!
I can join in and help the testing later today and during next week as
much as i have time do so :)
Den sön 9 juli 2023 kl 13:27 skrev Sumantro Mukherjee :
>
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 6.4
> Test week is happening from 2023-07-09 to 2023-07-
On Sunday, May 28, 2023 3:57:44 PM EDT Ranjan Maitra wrote:
> Thanks! It is possible I do not have this set up because I get:
>
> $ sudo journalctl -b -1 -r /soft lockup
> Specifying boot ID or boot offset has no effect, no persistent journal was
> found.
Just use
sudo journalctl -b -1 -r
On 5/28/23 12:57, Ranjan Maitra wrote:
On Sun May28'23 12:41:54PM, Samuel Sieb wrote:
"journalctl -b -1 -r"
Thanks! It is possible I do not have this set up because I get:
$ sudo journalctl -b -1 -r /soft lockup
Specifying boot ID or boot offset has no effect, no persistent journal was
fo
On Sun May28'23 12:41:54PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Sun, 28 May 2023 12:41:54 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: kernel watchdog BUG
>
> On 5/28/23 09:15, stan via users wrote:
On 5/28/23 09:15, stan via users wrote:
On Sun, 28 May 2023 09:52:04 -0500
Ranjan Maitra wrote:
I rebooted in the good old ways of some other OSs, and the problem
has not reared again for now. I did look at /var/log/messages but
found nothing on kernel lockup. Are these some other log files
On Sun, 28 May 2023 09:52:04 -0500
Ranjan Maitra wrote:
> I rebooted in the good old ways of some other OSs, and the problem
> has not reared again for now. I did look at /var/log/messages but
> found nothing on kernel lockup. Are these some other log files I
> should be looking at.
journalctl
On Sat May27'23 07:40:29PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Sat, 27 May 2023 19:40:29 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: kernel watchdog BUG
>
> On 5/27/23 17:48, Ranjan Maitra wrote:
On 5/27/23 17:48, Ranjan Maitra wrote:
Came back to my screen to the following:
Message from syslogd@localhost at May 27 19:19:48 ...
kernel:watchdog: BUG: soft lockup - CPU#0 stuck for 134s! [cifsd:21659]
What is this issue?
Check the logs, there should be more details.
___
On 5/19/23 4:38 AM, Felix Miata wrote:
home user composed on 2023-05-18 20:25 (UTC-0600):
The boot partition has been big enough for over 10 years, including the time
I've had 4 kernels + 1 rescue kernel (since late last year). I'm puzzled about
how the /boot partition is now too small. Has
home user composed on 2023-05-18 20:25 (UTC-0600):
> The boot partition has been big enough for over 10 years, including the time
> I've had 4 kernels + 1 rescue kernel (since late last year). I'm puzzled
> about how the /boot partition is now too small. Has the kernel grown
> significantly?
Just got a new old Thinkpad Edge from 2010 running Fedora 38 with
testing updates, so will help to do some testing on that :)
On Fri, May 5, 2023 at 8:45 AM Sumantro Mukherjee wrote:
>
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 6.3
> Test week is happening from
Hey!
I did help out a bit early and talked to Justin over Matrix yesterday
so Kernel 6.2.2 is tested on my box and results entered on the
testweek page and Bodhi
On 3/3/23, Sumantro Mukherjee wrote:
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 6.2
> Test week is
> On Feb 14, 2023, at 11:42, Bill C wrote:
>
> I know I have used depmod -an and it searches for some time. My system is
> broken though obviously, I used find to go through lib/modules and there was
> no driver that everyone else can find. Specifically the rt2 driver.
If you have the k
I know I have used depmod -a and it searches for some time. My system is
broken though obviously, I used find to go through lib/modules and there
was no driver that everyone else can find. Specifically the rt2 driver.
On Mon, Feb 13, 2023, 4:34 PM Barry Scott wrote:
>
>
> On 13 Feb 2023, at
On Feb 13, 2023, at 07:29, Ralf Corsépius wrote:
>
>> Am 13.02.23 um 04:35 schrieb Bill Cunningham:
>> IDK if anyone is familiar with this series of legacy products/drivers or
>
> I am not familiar with these drivers, but AFAIS, they seem to be in Fedora's
> kernel:
>
> # modinfo rt2800usb
>
insmod is the original low level way to do it and you need the full
path and module filename.
modprobe knows the correct kernel and knows where all modules are
supposed to be install so should just work(assuming a depmod was run
to build the name -> filename mappings).
dmesg | grep -i rt28 and
> On 13 Feb 2023, at 19:12, Bill C wrote:
>
> When I use these tools I get nothing. I ran insmod, that would not install
> anything. I was thinking there are a bunch of dependencies needed. I must
> need to install more packages or I will try the live workstation later.
I have always used mo
When I use these tools I get nothing. I ran insmod, that would not install
anything. I was thinking there are a bunch of dependencies needed. I must
need to install more packages or I will try the live workstation later.
On Mon, Feb 13, 2023, 7:29 AM Ralf Corsépius wrote:
>
>
> Am 13.02.23 um 04
Am 13.02.23 um 14:08 schrieb Bill C:
Ok, I see. That looks like them. Do you just use insmod?
Probably - Definitely something worth trying.
However, in my understanding, the driver should be autoloaded if it
detects a suitable device.
May-be the usb id of your device doesn't match with one
Ok, I see. That looks like them. Do you just use insmod?
On Mon, Feb 13, 2023, 7:29 AM Ralf Corsépius wrote:
>
>
> Am 13.02.23 um 04:35 schrieb Bill Cunningham:
> > IDK if anyone is familiar with this series of legacy products/drivers or
>
> I am not familiar with these drivers, but AFAIS, they
Am 13.02.23 um 04:35 schrieb Bill Cunningham:
IDK if anyone is familiar with this series of legacy products/drivers or
I am not familiar with these drivers, but AFAIS, they seem to be in
Fedora's kernel:
# modinfo rt2800usb
filename:
/lib/modules/6.1.10-200.fc37.x86_64/kernel/drivers/net/
On 2/12/23 19:35, Bill Cunningham wrote:
IDK if anyone is familiar with this series of legacy products/drivers or
not, but I am using of course F37. Now there is some nice source code
and such with these drivers for this USB wifi antenna; but I just want
to load a driver and go at it. I can't e
On 2023-01-08 08:14, Sjoerd Mullender wrote:
and see the difference in behavior. When using "all", the second
round (IPv4) says that bind returns 1 unexpectedly, and the port is
also unexpected. When using "localhost", both IPv6 and IPv4 succeed
and listen to the same port, but using two di
On 08/01/2023 16:14, Sjoerd Mullender wrote:
On 07/01/2023 01.38, Gordon Messmer wrote:
On 2023-01-06 06:17, Sjoerd Mullender wrote:
I have a program that is supposed to listen to the same port on both
IPv4 and IPv6 sockets. In the past, what it did, was basically:
create new socket for IPv6
On 07/01/2023 01.38, Gordon Messmer wrote:
On 2023-01-06 06:17, Sjoerd Mullender wrote:
I have a program that is supposed to listen to the same port on both
IPv4 and IPv6 sockets. In the past, what it did, was basically:
create new socket for IPv6, set option IPV6_V6ONLY to off, bind,
listen;
On 2023-01-06 06:17, Sjoerd Mullender wrote:
I have a program that is supposed to listen to the same port on both
IPv4 and IPv6 sockets. In the past, what it did, was basically:
create new socket for IPv6, set option IPV6_V6ONLY to off, bind,
listen; then create a new socket for IPv4, and also
On 06/01/2023 18.59, Barry wrote:
On 6 Jan 2023, at 14:18, Sjoerd Mullender wrote:
I have a program that is supposed to listen to the same port on both IPv4 and
IPv6 sockets. In the past, what it did, was basically: create new socket for
IPv6, set option IPV6_V6ONLY to off, bind, liste
> On 6 Jan 2023, at 14:18, Sjoerd Mullender wrote:
>
> I have a program that is supposed to listen to the same port on both IPv4
> and IPv6 sockets. In the past, what it did, was basically: create new socket
> for IPv6, set option IPV6_V6ONLY to off, bind, listen; then create a new
> socke
home user composed on 2022-12-15 20:26 (UTC-0700):
>> Alternatively, you could modify /etc/dnf/dnf.conf by entirely excluding
>> kernels
>> from being installed or removed by dnf:
>> exclude=" kernel* "
>> Using this option, dnf will pretend kernels don't exist for purposes of
>> adding o
I wanted to provide an update and say that last night's updates (and a reboot)
potentially mean that I can no longer reproduce my issue. I am not sure what
happened, but I will see if this comes back.
Thanks,
Ranjan
On Sun Nov27'22 10:02:56PM, Ranjan Maitra wrote:
> From: Ranjan Maitra
> Date:
I ran a bunch again, but this time I didn't get back any of the
notifications. I hope they went through.
On Sun, Jun 12, 2022 at 7:35 AM Luna Jernberg wrote:
> done worked on my laptop, had only energy and time to test 1 day of 7,5
> this time around
>
> On Sun, Jun 12, 2022 at 12:19 PM Luna Je
done worked on my laptop, had only energy and time to test 1 day of 7,5
this time around
On Sun, Jun 12, 2022 at 12:19 PM Luna Jernberg
wrote:
> Hey!
>
> Running the tests today (the last day) been having too much to do and not
> feelt the best earlier this and last week
>
> On Mon, Jun 6, 2022
Hey!
Running the tests today (the last day) been having too much to do and not
feelt the best earlier this and last week
On Mon, Jun 6, 2022 at 1:28 PM murph nj wrote:
> I did enough that I should have gotten to Kernel Tester IV in the last
> Kernel test week. I submitted them with my account
I did enough that I should have gotten to Kernel Tester IV in the last
Kernel test week. I submitted them with my account, and got back
the notifications stating that the tests were run.
I'll start working on this round, but it would be good to see that nudged
along.
Thanks,
--murph
On Mon,
On Fri, Jun 3, 2022 at 6:08 PM murph nj wrote:
> Hey there:
>
>
>
>
> On Fri, Jun 3, 2022 at 4:23 AM Sumantro Mukherjee
> wrote:
>
>> Hey All,
>>
>> I would like to invite all of you to participate in the Kernel 5.18
>>
>
>
>> Needless to say, you will get a badge for participating in all
>> act
Will try to help out if i am not to busy with openSUSE and SUSE Conference,
that goes on these 2 weeks (won't promise anything)
On Fri, Jun 3, 2022 at 10:23 AM Sumantro Mukherjee
wrote:
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 5.18
> Test week is happening fr
Hey there:
On Fri, Jun 3, 2022 at 4:23 AM Sumantro Mukherjee
wrote:
> Hey All,
>
> I would like to invite all of you to participate in the Kernel 5.18
>
> Needless to say, you will get a badge for participating in all
> activities talked about in this email!
>
>
>
I don't feel that badges
On Fri, May 6, 2022 at 1:55 AM ja wrote:
> I have been using this repository for building VMWare modules
>
> https://github.com/mkubecek/vmware-host-modules
I tried that as well, but that fails in a slightly different way:
ram@zathras [08:34:09] [~/git/vmware-host-modules] [workstation-16.2.3]
On Thu, 5 May 2022 09:41:31 -0700
Adam Mercer wrote:
> Hi
>
> I had an update to the 5.17.5 kernel ,on my Fedora 35 system, this
> morning but there was no corresponding update to the kernel-headers
> package. As such I'm unable to rebuild the VMWare modules for VMWare
> Workstation. Do I just n
On Thu, 2022-05-05 at 09:41 -0700, Adam Mercer wrote:
> Hi
>
> I had an update to the 5.17.5 kernel ,on my Fedora 35 system, this
> morning but there was no corresponding update to the kernel-headers
> package. As such I'm unable to rebuild the VMWare modules for VMWare
> Workstation. Do I just ne
On Thu, May 5, 2022, at 9:41 AM, Adam Mercer wrote:
> Hi
>
> I had an update to the 5.17.5 kernel ,on my Fedora 35 system, this
> morning but there was no corresponding update to the kernel-headers
> package. As such I'm unable to rebuild the VMWare modules for VMWare
> Workstation. Do I just need
On 4/1/22 05:53, Tim via users wrote:
On Thu, 2022-03-31 at 12:27 -0400, Temlakos wrote:
Today I recorded a video using Open Broadcast Studio (OBS) and a
Logitech BRIO camera with build-in microphone that has delivered
flawless performance to date.
Imagine my shock and chagrin when I played a v
On Thu, 2022-03-31 at 12:27 -0400, Temlakos wrote:
> Today I recorded a video using Open Broadcast Studio (OBS) and a
> Logitech BRIO camera with build-in microphone that has delivered
> flawless performance to date.
>
> Imagine my shock and chagrin when I played a video I had just
> recorded, o
On 01/04/2022 00:27, Temlakos wrote:
Everyone:
Today I recorded a video using Open Broadcast Studio (OBS) and a Logitech BRIO
camera with build-in microphone that has delivered flawless performance to date.
Imagine my shock and chagrin when I played a video I had just recorded, only to
find t
On Thu, 2022-03-31 at 12:27 -0400, Temlakos wrote:
> 1. How do I set DNFDragora to skip a current version and call me
> back when it has a new version of the kernel for me to try out?
Doesn't the "exclude" option let you use the entire package name (with
the version number), or does it just let yo
On 3/31/22 13:41, Samuel Sieb wrote:
On 3/31/22 09:27, Temlakos wrote:
All that to say this: the kernel has a bug, and killed the handling
of sound from microphones. At least in the current version. The last
version handled it without a hitch and still does.
Are you sure? Did you check the s
On 3/31/22 09:27, Temlakos wrote:
All that to say this: the kernel has a bug, and killed the handling of
sound from microphones. At least in the current version. The last
version handled it without a hitch and still does.
Are you sure? Did you check the sound settings?
I have removed that ve
On 2/15/22 2:10 PM, Alex wrote:
Hi,
Here's a bit of the kernel message from dmesg
[ cut here ]
WARNING: CPU: 4 PID: 633983 at kernel/exit.c:739 do_exit+0x37/0xa90
general protection fault, probably for non-canonical address
0xcc2a8cfcb62a56a1: [#1] SMP PTI
CPU: 4 PI
Hi,
> > >> Here's a bit of the kernel message from dmesg
> > >> [ cut here ]
> > >> WARNING: CPU: 4 PID: 633983 at kernel/exit.c:739 do_exit+0x37/0xa90
> > >> general protection fault, probably for non-canonical address
> > >> 0xcc2a8cfcb62a56a1: [#1] SMP PTI
> > >> CP
Hi,
> >> Here's a bit of the kernel message from dmesg
> >> [ cut here ]
> >> WARNING: CPU: 4 PID: 633983 at kernel/exit.c:739 do_exit+0x37/0xa90
> >> general protection fault, probably for non-canonical address
> >> 0xcc2a8cfcb62a56a1: [#1] SMP PTI
> >> CPU: 4 PID: 63
Gordon Messmer writes:
On 2/12/22 14:59, Alex wrote:
Here's a bit of the kernel message from dmesg
[ cut here ]
WARNING: CPU: 4 PID: 633983 at kernel/exit.c:739 do_exit+0x37/0xa90
general protection fault, probably for non-canonical address
0xcc2a8cfcb62a56a1: [#1]
On Sun, 13 Feb 2022 10:41:36 -0800
Gordon Messmer wrote:
> bio_crypt_clone suggests something wrong in an encrypted block device.
> Maybe corrupt data that rsync traverses during the backup?
Perhaps run the same rsync command with a -v option in a terminal
and see if the crash happens on the sa
On 2/12/22 14:59, Alex wrote:
Here's a bit of the kernel message from dmesg
[ cut here ]
WARNING: CPU: 4 PID: 633983 at kernel/exit.c:739 do_exit+0x37/0xa90
general protection fault, probably for non-canonical address
0xcc2a8cfcb62a56a1: [#1] SMP PTI
CPU: 4 PID: 63398
Hi,
On Sat, Feb 12, 2022 at 9:26 PM Joe Zeff wrote:
>
> On 2/12/22 15:59, Alex wrote:
> > Anyone else experiencing similar problems with the latest kernels?
>
> The fact that it happens at the same time every day makes me wonder if
> there's some job that's in process causing it.
Yes, there is
On 2/12/22 15:59, Alex wrote:
Anyone else experiencing similar problems with the latest kernels?
The fact that it happens at the same time every day makes me wonder if
there's some job that's in process causing it.
___
users mailing list -- users@l
On 10/8/21 06:18, Chris Murphy wrote:
5.13.9 is now in koji you might give that a shot.
5.13.5 changelog shows
commit c3eb534eae09de6cdd3e0ff63897b20e1b079cdb
vmxnet3: fix cksum offload issues for tunnels with non-default udp ports
5.13.6 changelog shows several vmware related commits
htt
5.13.9 is now in koji you might give that a shot.
5.13.5 changelog shows
commit c3eb534eae09de6cdd3e0ff63897b20e1b079cdb
vmxnet3: fix cksum offload issues for tunnels with non-default udp ports
5.13.6 changelog shows several vmware related commits
https://cdn.kernel.org/pub/linux/kernel/v5.x
On Fri, Jul 30, 2021 at 12:28 AM jarmo wrote:
>
> Got new kernel and that stil won't work with
> my HP laptop.
> It boots so far, that I get login window, I give passwd
> after that, black window, nothing else happens, except ctl+alt+del
> works.
> What I have last working kernel in that laptop, i
Wed, 26 May 2021 13:21:16 +0800
Ed Greshko kirjoitti:
> ima error communicating to tpm chip
>
> So, maybe look into those? Even though they seem "harmless".
Yes, done "googls" but my knowledge and language limimits
says nothing.
My English is quite level 1.0 from 1969 :) and as known,
compute
On 26/05/2021 13:00, jarmo wrote:
Wed, 26 May 2021 12:19:17 +0800
Ed Greshko kirjoitti:
WARNING: Kernel Errors Present
ima: Error Communicating to ...: 8 Time(s)
Is that the full error?
error communicating to ???
Yes, that's what it has been all the time.
"communicating to ...:"
Wed, 26 May 2021 12:19:17 +0800
Ed Greshko kirjoitti:
> > WARNING: Kernel Errors Present
> > ima: Error Communicating to ...: 8 Time(s)
> Is that the full error?
>
> error communicating to ???
Yes, that's what it has been all the time.
"communicating to ...:"
Jarmo
On 26/05/2021 11:55, jarmo wrote:
Every now and then I find from log
WARNING: Kernel Errors Present
ima: Error Communicating to ...: 8 Time(s)
Just curious, what this means, seems to be no harm?
Fedora 34 xfce4 older intelcore i7.
Is that the full error?
error communicating to ???
On 2020-08-24 03:11, Anthony Joseph Messina wrote:
Strange thing after upgrading a client to kernel-5.7.17, the client is unable
to list files/directories from an NFS server running kernel-5.7.15 (NFS v4.2 /
Kerberos mounted /home). The files/directories seem to be accessible if I type
in their
On Sunday, August 23, 2020 12:11:54 PM CDT Anthony Joseph Messina wrote:
> Strange thing after upgrading a client to kernel-5.7.17, the client is
> unable to list files/directories from an NFS server running kernel-5.7.15
> (NFS v4.2 / Kerberos mounted /home). The files/directories seem to be
> acc
On Sun, 23 Aug 2020 12:11:54 -0500
Anthony Joseph Messina wrote:
> Has anyone else see this?
I haven't seen that specific combination. I have seen a
possibly stranger thing: There is a virtual machine at work
where a test we run does a "cp /nfs/mounted/dir/* ." and
one file from /nfs/mounted/dir
On 7/13/20 12:09 AM, Eshin Kunishima wrote:
I've met kernel hang-up without any stack trace from kernel 5.7.6 in the update
testing repository. I did not find any usable messages in dmesg and
journalctl(It said that its data was corruption after rebooting). Is there any
method of collecting de
On 2020-07-10 18:56, Ed Greshko wrote:
> On 2020-07-10 18:51, Mark Roberts wrote:
>> Thanks Ed,
>>
>> The versions that I have installed (from the rpm command you mentioned are)
>> :
>>
>> kernel-devel-5.7.7-200.fc32.x86_64
>> kernel-5.7.7-200.fc32.x86_64
>> kernel-5.6.19-300.fc32.x86_64
>> kerne
On 2020-07-10 18:51, Mark Roberts wrote:
> Thanks Ed,
>
> The versions that I have installed (from the rpm command you mentioned are) :
>
> kernel-devel-5.7.7-200.fc32.x86_64
> kernel-5.7.7-200.fc32.x86_64
> kernel-5.6.19-300.fc32.x86_64
> kernel-modules-5.6.6-300.fc32.x86_64
> kernel-5.6.6-300.fc
On 2020-07-10 18:20, Mark Roberts wrote:
> I have a Fedora 32 laptop with kernel : 5.6.19-300.fc32.x86_64
>
> This seems to be the latest available.
>
> To use VirtualBox I need to configure it and that requires that I install
> kernel headers. The current version I have installed is :
> kernel-
On 2020-01-18 05:57, Leander Hutton via users wrote:
> On 1/17/20 4:46 PM, Ed Greshko wrote:
>> What is your exact kernel version? An issue similar to the above was
>> reported and fixed.
>> From a response to an earlier post.
>>
>> The issue with the wifi should be fixed in kernel 5.4.8-200.fc31
On 1/17/20 4:46 PM, Ed Greshko wrote:
> What is your exact kernel version? An issue similar to the above was
> reported and fixed.
> From a response to an earlier post.
>
> The issue with the wifi should be fixed in kernel 5.4.8-200.fc31.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1788150
On 2020-01-18 05:27, Leander Hutton via users wrote:
> I'm running Fedora 31 on my laptop with a Killer Wi-Fi 6 AX1650 network
> card. Under 5.3 kernel series my card worked fine but I've noticed that
> under the 5.4 series the firmware fails to load with the following
> kernel message:
>
> iwlwifi
saw a simular error month ago - can't find it anymore -
the solution was to sudo dnf install glibc-static
- don't know if it helps here too -
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedor
Work well on fedora 26, I think kbuild changed and not process ".a" files.
___
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/
1 - 100 of 720 matches
Mail list logo
