Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
Heads up. After today's updates I get black unresponsive screens. OK in 6.0.15 ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 37 hangs after graphical login
Hello, since yesterday i do have a big problem. After some updates and a succesfull reboot, i first could not login anymore. Alsways a wrong password. I solved this with resetting root password and my two user passwords. Now i could login. Root account works, one user account (the empty one) also. But my usually working account freezes, after i login. If i login via terminal Ctrl-Alt-F3 it works. So i think that something is crashed during the load after graphical login. How could i See, what is going on after graphical login? The different steps and programs i mean. Any logfiles? I know that one of the first thing is loading gdm? Or am i wrong? Btw: i use wayland and GNOME. An update via dnf brings nothing. Hope someone does have an idea. Thanks Jens ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
kernel bug? listening on same port with IPv4 and IPv6
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 bind and listen. The first bind is either to a specific port, or to port 0 to let the system assign a port. The second bind uses the port that the first one used (i.e. what the system assigned). With the latest kernel, this still works if listening to localhost ([::1]/127.0.0.1) only, but not when listening to [::]/0.0.0.0. In that case, the second bind gets a different port number assigned to it. Moreover, the second bind system call returns 1, which it is not supposed to do according to the manual. Bind is supposed to return 0 on success and -1 on error. What is going on? Is this a kernel bug, or is this the future? Kernel is 6.0.16-300.fc37.x86_64, i.e. the latest Fedora 37 kernel. -- Sjoerd Mullender ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: kernel bug? listening on same port with IPv4 and IPv6
> 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 > socket for IPv4, and also bind and listen. The first bind is either to a > specific port, or to port 0 to let the system assign a port. The second bind > uses the port that the first one used (i.e. what the system assigned). Are you sure that this is behaviour you can depend on? Is it documented? It seems that there is a possibility that the 2nd bind with port 0 can race against other processes. Why should you get the same port bound? If I was writing this code I would take the port allocated on the 1st bind and use it explicitly in the 2nd bind. Would that work and be deterministic? I recall working on code that needed two ports N and N+1. The algorithm looped until the N and N+1 condition was met. Barry > > With the latest kernel, this still works if listening to localhost > ([::1]/127.0.0.1) only, but not when listening to [::]/0.0.0.0. In that > case, the second bind gets a different port number assigned to it. Moreover, > the second bind system call returns 1, which it is not supposed to do > according to the manual. Bind is supposed to return 0 on success and -1 on > error. > > What is going on? Is this a kernel bug, or is this the future? > > Kernel is 6.0.16-300.fc37.x86_64, i.e. the latest Fedora 37 kernel. > > -- > Sjoerd Mullender > ___ > 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/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: kernel bug? listening on same port with IPv4 and IPv6
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, listen; then create a new socket for IPv4, and also bind and listen. The first bind is either to a specific port, or to port 0 to let the system assign a port. The second bind uses the port that the first one used (i.e. what the system assigned). Are you sure that this is behaviour you can depend on? Is it documented? It seems that there is a possibility that the 2nd bind with port 0 can race against other processes. Why should you get the same port bound? If I was writing this code I would take the port allocated on the 1st bind and use it explicitly in the 2nd bind. Would that work and be deterministic? That's exactly what I do. I recall working on code that needed two ports N and N+1. The algorithm looped until the N and N+1 condition was met. Barry With the latest kernel, this still works if listening to localhost ([::1]/127.0.0.1) only, but not when listening to [::]/0.0.0.0. In that case, the second bind gets a different port number assigned to it. Moreover, the second bind system call returns 1, which it is not supposed to do according to the manual. Bind is supposed to return 0 on success and -1 on error. What is going on? Is this a kernel bug, or is this the future? Kernel is 6.0.16-300.fc37.x86_64, i.e. the latest Fedora 37 kernel. -- Sjoerd Mullender ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- Sjoerd Mullender ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 37 hangs after graphical login
Am Fr, 2023-01-06, 14:33 +0100, Karlderletzte schrieb: hello, i find out some additional info. if i disable network before login, then the graphical login works. perhaps someting with my autofs. but i dont know how to read something in logs. > Hello, since yesterday i do have a big problem. > After some updates and a succesfull reboot, i first could not login > anymore. Alsways a wrong password. > I solved this with resetting root password and my two user passwords. > Now i could login. > Root account works, > one user account (the empty one) also. > But my usually working account freezes, after i login. > If i login via terminal Ctrl-Alt-F3 it works. > So i think that something is crashed during the load after graphical > login. > How could i See, what is going on after graphical login? The different > steps and programs i mean. Any logfiles? > > I know that one of the first thing is loading gdm? Or am i wrong? > > Btw: i use wayland and GNOME. An update via dnf brings nothing. > > Hope someone does have an idea. > Thanks > Jens > ___ > 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/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Jens Reimer ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 37 hangs after graphical login
hurray, i find out the source of pain. it is the autofs.service. after disabling it, its working. but i do not know, why this service freeze my laptop. i use autofs since fedora 35 and do not edit anything. does anybody knows something about configuration of autofs, especially changes the last month? ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
6.0.16-200.fc36.x86_64 crash
I boot from the latest kernel (subject) then mount a shared directory on a RHEL 7.9 host. As soon as I access any file or directory on the shared directory the my machine instantly & completely freezes. Even the clock on the top bar stops, cursor stops blinking, and other pc's cannot ping this one. If I reboot to 6.0.15-200.fc36.x86_64, no problem. Also noted that another shared directory on another pc (not sure what OS) works fine. Just wondering what I should try next? ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
picture stitcher for Fedora?
Hi All, FC37 Is there a picture stitcher that works with Fedora and that does not require a rocked scientist to use? Many thanks, -T ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: picture stitcher for Fedora?
On 1/6/23 15:08, ToddAndMargo via users wrote: Is there a picture stitcher that works with Fedora and that does not require a rocked scientist to use? I use hugin. If you stay with the high-level workflow (the numbered buttons) it's simple to use. The rocket scientist options are also there though, if you need them. -- David King dave at daveking dot com ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 37 hangs after graphical login
On Fri, 06 Jan 2023 19:47:40 +0100 karlderletzte wrote: > hurray, > i find out the source of pain. > it is the autofs.service. > after disabling it, its working. > but i do not know, why this service freeze my laptop. > i use autofs since fedora 35 and do not edit anything. > > does anybody knows something about configuration of autofs, especially > changes the last month? I don't have any autofs mounted filesystems, but it seems that it is trying to mount a filesystem that isn't available. When it happens, try the command journalctl -r to see what was logged to the journal in reverse order. So, most recent will be first. I think this must be something particular to your system. I looked at the redhat bugzilla page, and didn't find anything that seemed to be related to your problem. Here is the page of open bugs. https://bugzilla.redhat.com/buglist.cgi?quicksearch=autofs ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: 6.0.16-200.fc36.x86_64 crash
On Fri, 6 Jan 2023 14:57:53 -0500 Roger Wells wrote: > I boot from the latest kernel (subject) then mount a shared directory > on a RHEL 7.9 host. > As soon as I access any file or directory on the shared directory the > my machine instantly & completely freezes. > Even the clock on the top bar stops, cursor stops blinking, and other > pc's cannot ping this one. > If I reboot to 6.0.15-200.fc36.x86_64, no problem. > Also noted that another shared directory on another pc (not sure what > OS) works fine. > Just wondering what I should try next? Is there anything in the logs on the local system after reboot, or on the shared directory system? This sounds like a null pointer is being accessed. Because it doesn't happen on 6.0.15, it might be a bug in the kernel. But I couldn't find any bugs open on the redhat bugzilla, so it seems unlikely. Has the protocol changed? Maybe it is trying to interpret the data it receives incorrectly. ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: picture stitcher for Fedora?
On 1/6/23 13:50, David King wrote: On 1/6/23 15:08, ToddAndMargo via users wrote: Is there a picture stitcher that works with Fedora and that does not require a rocked scientist to use? I use hugin. If you stay with the high-level workflow (the numbered buttons) it's simple to use. The rocket scientist options are also there though, if you need them. Thank you! ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: picture stitcher for Fedora?
Things I love about this list. You get to find out about interesting software you were not even looking for! On Fri, Jan 6, 2023 at 5:05 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote: > On 1/6/23 13:50, David King wrote: > > On 1/6/23 15:08, ToddAndMargo via users wrote: > >> Is there a picture stitcher that works with > >> Fedora and that does not require a rocked > >> scientist to use? > > > > I use hugin. If you stay with the high-level workflow (the numbered > > buttons) it's simple to use. The rocket scientist options are also > > there though, if you need them. > > > > Thank you! > ___ > 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/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- -- /\_/\ |O O| pepeb...@gmail.com Javier Perez While the night runs toward the day... m m Pepebuho watches from his high perch. ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: 6.0.16-200.fc36.x86_64 crash
On 06.01.23 23:03, stan via users wrote: On Fri, 6 Jan 2023 14:57:53 -0500 Roger Wells wrote: I boot from the latest kernel (subject) then mount a shared directory on a RHEL 7.9 host. As soon as I access any file or directory on the shared directory the my machine instantly & completely freezes. Even the clock on the top bar stops, cursor stops blinking, and other pc's cannot ping this one. If I reboot to 6.0.15-200.fc36.x86_64, no problem. Also noted that another shared directory on another pc (not sure what OS) works fine. Just wondering what I should try next? Is there anything in the logs on the local system after reboot, or on the shared directory system? This sounds like a null pointer is being accessed. Because it doesn't happen on 6.0.15, it might be a bug in the kernel. But I couldn't find any bugs open on the redhat bugzilla, so it seems unlikely. I have the same behavior with a cifs mount to a fritz box (AVM router). Also introduced with 6.0.16. mount options is my case are mount -o nounix,noserverino,uid=1501,gid=15010,file_mode=0640,dir_mode=0750,credentials=/home/ulf/.smb.fritz,vers=3 //fritz.box/FRITZ.NAS /mnt and there is nothing in the journal. Best regards Ulf ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: kernel bug? listening on same port with IPv4 and IPv6
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 bind and listen. Do you have sample code that demonstrates this process? I'm confused by your description, because setting IPV6_V6ONLY to 0 with setsockopt should result in a socket that's bound to a port that accepts both IPv4 and IPv6 connections. You shouldn't have ever been able to bind to that port in IPv4 in the past. ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 6/1/23 22:22, John Pilkington wrote: Heads up. After today's updates I get black unresponsive screens. OK in 6.0.15 I'm using the nvidia 525.60.11 driver from rpmfusion-nonfree-nvidia-driver and there is no issue with kernel 6.0.16. regards, Steve ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Grubby? Doesn't Load Initrd
Hi, I've just done an update which installed kernel 6.0.16 and I forgot to run grub2-mkconfig, and when I booted from the grub menu's defined in /boot/grub2/grub.cfg presumably updated by grubby, it did not run initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. Is this a defect with grubby? regards, Steve ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 37 hangs after graphical login
On Fri, 2023-01-06 at 19:47 +0100, karlderletzte wrote: > it is the autofs.service. > after disabling it, its working. > but i do not know, why this service freeze my laptop. > i use autofs since fedora 35 and do not edit anything. As far as I was aware, autofs didn't do anything unless you did edit something. If I want it to automount something I had to customise something. I believe things like USB drives and optical discs were usually handled by something else. And my past experience with mounting things via some kind of rule or /etc/fstab entry, was that the system would foul up at boot and shutdown if the thing listed wasn't present for the system to act on. I just use autofs for accessing NFS exports on another PC. e.g. I set the /net directory to be an automount point, then if I try to access something like /net/rocky/home/tim autofs will mount my home directory on the "rocky" server (that being its hostname). That automount will gracefully disappear after some time, rather than wedge my system (as it would if I had made an entry in my /etc/fstab and tried to boot or shutdown the client when the server wasn't available). -- uname -rsvp Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
On Sat, 2023-01-07 at 14:36 +1100, Stephen Morris wrote: > I've just done an update which installed kernel 6.0.16 and I forgot > to run grub2-mkconfig, and when I booted from the grub menu's defined in > /boot/grub2/grub.cfg presumably updated by grubby, it did not run > initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. I have to ask, since I see a lot of grubby posts (pun intended): I've *NEVER* run grub2-mkconfig. I've always just yum/dnf update (do all current updates), or just dnf update kernel (if I wanted to specifically just do that), and it's always installed the new kernel properly all by itself. No further action was required by me. What are people doing to their systems that they paint themselves into a corner that they have to manually manage this, then have to pick up the pieces when it doesn't work? -- uname -rsvp Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ 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/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
