Re: Boot hangs on recent kernels
Klaus-Peter Schrage via users composed on 2024-06-09 13:47 (UTC+0200): > What I don't understand: What produced the entry "resume=UUID=8e895..." > in the file /etc/default/grub which was created on the install date, May > 3rd Does your fstab or installation media or any other media used during or prior to F40 installation include that UUID fragment? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Boot hangs on recent kernels
Klaus-Peter Schrage composed on 2024-06-08 18:20 (UTC+0200): > Since kernel 6.8.10-300.fc40.x86_64, boot hangs on KDE Plasma (kernel > 6.8.9-300.fc40.x86_64 was the last good one). > I found that there is a job running infinitely: > 'Job dev-disk-by\x2duuid-8e895running ...' > The above mentioned UUID (8e895 ...) corresponds to the kernel > 'resume=uuid=...' command line parameter. Does any device within your system actually include 8e895whatever within it? > When I comment it out in GRUB2, as suggested in > https://discussion.fedoraproject.org/t/solved-boot-hang-job-dev-disk-by-x2uuid-no-limit/ > then the system boots as expected. > This is a rather fresh install of fedora 40 (running on ext4): > da 8:0 0 232,9G 0 disk > ├─sda1 8:1 0 1,1G 0 part /boot > ├─sda2 8:2 0 49,1G 0 part / > ├─sda3 8:3 0 31,7G 0 part /home > └─sda4 8:4 0 151G 0 part /mnt/Daten3 > I have no swap partition, resume after hibernation works without errors. Did you previously have a swap partition whose UUID included 8e895? > Although there is an obvious workaround (permanently removing the resume > parameter from the kernel command line), I still wonder what has happened? # lsinitrd /boot/initramfs-6.8.11-300.fc40.x86_64.img | grep resume # If you run the above on 6.8.9, do you get the response I do? If yes, then it was creating a process destined to timeout and delay complete boot success. If no, then the resume= parameter in Grub was merely an override of that existing within your initramfs. Do you get the same result running the command on 6.8.10? When you removed it from Grub, you stopped creating what had not been specified in your initrd. IOW what I think happened is that whether resume= existed within your initrd was changed from 6.8.9 to 6.8.10. Since I always have noresume instead of resume=, I don't think I ever have had resume=in any of my initrds. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: number of lines on console
Samuel Sieb composed on 2024-06-06 20:53 (UTC-0700): > Felix Miata wrote: >> <https://forums.opensuse.org/t/how-to-have-a-custom-uefi-grub-menu-for-a-multiboot-system/133541> >> could help you get that started. /etc/grub.d/40_custom and 41_custom are >> designed >> for custom stanza creations. If you wish their result to head the selections >> in >> you Grub menu, you must rename whichever you choose to use so that it sorts >> before >> 10_linux. I use both avenues, so copy 40_custom to 06_custom, and 41_custom >> to >> 07_custom. Updates will at some point restore the original 40_custom and >> 41_custom, unless you keep and either empty them or make them nothing but >> comments. > This was just for a live image. There's no need to get that crazy > complicated. That's only for a multi-boot system. Adding items to a > single boot system is very simple. Adding a stanza to 40_custom is not complicated. That URL is mainly example of configuring grub, getting to know how it does what it does, good for people who learn better from reading and/or working with examples than reading man pages. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: number of lines on console
Greg Woods composed on 2024-06-06T20:55 (UTC-0600): > Samuel Sieb wrote: >> You could add an extra entry to the boot menu. > That's a thought. Of course one of the reasons I wanted to learn more about > the boot process is that it has changed so much since I was working as a > sysadmin, now that I'm retired I haven't kept up with everything as well as > I used to. So I have to admit that now, I don't even know how to do that. > Something else I need to learn. <https://forums.opensuse.org/t/how-to-have-a-custom-uefi-grub-menu-for-a-multiboot-system/133541> could help you get that started. /etc/grub.d/40_custom and 41_custom are designed for custom stanza creations. If you wish their result to head the selections in you Grub menu, you must rename whichever you choose to use so that it sorts before 10_linux. I use both avenues, so copy 40_custom to 06_custom, and 41_custom to 07_custom. Updates will at some point restore the original 40_custom and 41_custom, unless you keep and either empty them or make them nothing but comments. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: number of lines on console
Greg Woods composed on 2024-06-06 18:00 (UTC-0600): > So I have verified that if I boot the Fedora USB stick on my desktop using > the same monitor, the problem does not occur, and if I boot the stick on > the laptop without the dock and with the lid open, aside from the fact that > the text is too small to read on the 4K screen, the problem does not occur. > When I boot this laptop from its own native OS rather than from the stick, > I have kernel command line parameters > (vconsole.font=latarcyrheb-sun32.psfu.gz SYSFONT=latarcyrheb-sun32.psfu.gz) > that make the booting text larger so I can read it, and the problem also If you have this size 32 vconsole.conf configuration on your USB stick, I suggest changing it to something smaller, maybe 24, halfway between 16 & 32. > does not occur. It also makes the font larger that appears on the text > consoles. This is not so great for booting from the stick though; I have a > hard time entering these parameters correctly when editing a GRUB entry > when I cannot check what I am typing. I also tried playing games with > video= values, and it works while boot messages are printing, but once the > login prompt comes up, the font is tiny again. Reverting to mousetype is a forseeable result if vga= is used, suitable video= is not used, and KMS is not engaging before gettys startup. Configuring early KMS in initramfs should help if this is the situation. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: number of lines on console
Greg Woods composed on 2024-06-06 11:26 (UTC-0600): > Michal Schorm wrote: > If the Full HD resolution isn't working well in your setup, you may >> try to force a lower resolution by trying out 'video=1024x768' or >> 'vga=0x318' kernel parameters. > I have tried a couple of different vga values but it has no apparent > effect; I probably just haven't hit on the right one yet. I was kind of > hoping someone here would have already seen this problem and have some > specific values to try. Once the current system-upgrade that is in progress > finishes, I'll try the ones you list here. Any valid vga= applied lasts only until a module providing working KMS loads. Once KMS engages, the kernel decides the mode, unless a differing supported video= mode has been applied. If KMS engages early enough, the effect of vga= may never be seen. Using video= with a suitable value does normally change the mode if KMS is working, and with an appropriate mode, output fitting the available screen space should result. On a 1920x1080, try actually specifying 1920x1080. If that doesn't help, others to try include: 1600x900, 1280x768, 1152x854 & 1024x768. @60 or an alternate refresh rate may be appended to the video= mode, and may make a difference. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: grub2-mkconfig
Patrick Dupre composed on 2024-06-04 23:57 (UTC+0200): > Disklabel type: gpt > Disk identifier: 5975BF99-78B4-4807-9CE4-C2BB0B8FE075 > > Device Start End Sectors Size Type > /dev/sda1 2048 6143 4096 2M BIOS boot > /dev/sda2 6144 33560575 3355443216G Linux swap > /dev/sda3 33560576 34584575 1024000 500M EFI System This sda3 is the only ESP among your 3 disks. In general, having only one ESP is perfectly fine on a GNU/Linux computer, if: 1-all installations were done in legacy/BIOS mode, and none use the ESP, or 2-all installations were done in UEFI mode, and all use it, unless more than one installation is of the same distro, in which case /etc/default/grub needs its GRUB_DISTRIBUTOR= made unique on /at least/ all-1 of the matching distros. This could become Patrick Dupre, and probably should. 3-kernels are not installed on ESP. This is OK in principle, but only if ESP is large enough to fit the expected number of kernels. In traditional UEFI installations, the ESP is not used for keeping kernels or initrds. 500M is more than adequate if no kernels are kept there, but not if multiple kernels for each Fedora release are kept there. If on Patrick's system more than one installation was done in UEFI mode, then the UEFI installations' bootloaders will be a case of last one probably wins, usurping each other at every upgrade. The result is similar to reinstalling Windows, where Window bootloader replaces GRUB code in MBR with its own to break Linux booting. The most recently installed Fedora bootloader will be the one whose ESP entry in /boot/efi/EFI/fedora/ is in control of UEFI booting. Please boot in UEFI mode, then gather and provide here output from: A-efibootmgr -v", and B-tree /boot/efi" Also report for each of the 3 installations: a-value of GRUB_DISTRIBUTOR= in /etc/default/grub b-content of /etc/fstab c-input/output of lsblk -f -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: How to remove settings from a systemd unit file
Sam Varshavchik composed on 2024-06-04 19:24 (UTC-0400): > So I was tearing my hair out trying to figure out why attempts to push via > DAV to a git repo were failing. > Eventually I succeeded in stracing the httpd process sto capture the > request. It was getting an EROFS when it tried to write to the git repo. > Amusing. > To make a long story short, the culprit was: > ProtectHome=read-only > in /lib/systemd/system/httpd.service,(the git repo was in a directory inside > a mounted /home partition). > I tried using > systemctl edit httpd > And putting this in there: > [Service] > ProtectHome= > However this apparently did not work. Please show us the override file in /etc/systemd* that resulted from your edits. Using systemctl edit for for over a year had me baffled. > I threw in the towel and just edited > /lib/systemd/system/httpd.service and commented this setting out, entirely, > to finally fix this issue, and happy git pushing resumed. > But how do I fix this so that the next apache update doesn't clobber this? Get the override to work. I have several working. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: grub2-mkconfig
Samuel Sieb composed on 2024-06-04 15:03 (UTC-0700): > You don't have an EFI partition on this disk. It's not even a GPT > partition table. So both installations will be fighting over the EFI > partition on sda. And there's no easy way to add a boot entry for this > installation. A multiboot GNU/Linux PC needs only one bootloader. Maybe OP's configuration can be improved through some additional information: <https://forums.opensuse.org/t/how-to-have-a-custom-uefi-grub-menu-for-a-multiboot-system/133541> -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: grub2-mkconfig
Samuel Sieb composed on 2024-06-04 15:03 (UTC-0700): > You don't have an EFI partition on this disk. It's not even a GPT > > partition table. So both installations will be fighting over the EFI > > partition on sda. And there's no easy way to add a boot entry for this > > installation. A multiboot GNU/Linux PC needs only one bootloader. Maybe OP's configuration can be improved through some additional information: <https://forums.opensuse.org/t/how-to-have-a-custom-uefi-grub-menu-for-a-multiboot-system/133541> -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: grub2-mkconfig
Samuel Sieb composed on 2024-06-04 13:49 (UTC-0700): > Patrick Dupre via users wrote: >> I am maintaining this machine for numerous years, it always passed the >> updates, >> but from 38 to 40, the same approach fails! > You haven't given a full explanation of your disk layout, If you provide complete output from fdisk -l and/or parted -l, you might arouse interest in more potential or better help. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: grub2-mkconfig
Patrick Dupre via users composed on 2024-06-04 22:15 (UTC+0200): > I do not understand, because every thing seems OK > The file is at the right place as well as > System.map-6.8.11-300.fc40.x86_64 > initramfs-6.8.11-300.fc40.x86_64.img > config-6.8.11-300.fc40.x86_64 > symvers-6.8.11-300.fc40.x86_64.xz -> > /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz If everything was really OK, there would also be a vmlinu* there as well. https://bugzilla.redhat.com/show_bug.cgi?id=2119907 -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Please stop hijacking /etc/resolv.conf
Sam Varshavchik composed on 2024-05-31 12:13 (UTC-0400): > Masking is just solving the X of an XY problem. Either the dependencies > being masked are not needed, or if they are needed masking would break > something. I like KISS: # inxi -Sz System: Kernel: 6.8.11-300.fc40.x86_64 arch: x86_64 bits: 64 Console: pty pts/0 Distro: Fedora Linux 40 (Forty) # rpm -qa | egrep 'solv|netw|nage|wicd' | sort libsemanage-3.6-3.fc40.x86_64 libsolv-0.7.29-1.fc40.x86_64 systemd-networkd-255.7-1.fc40.x86_64 # systemctl list-unit-files | egrep 'net|solv|nage' display-manager.service alias - systemd-network-generator.servicedisabledenabled systemd-networkd-wait-online.service disableddisabled systemd-networkd-wait-online@.servicedisableddisabled systemd-networkd.service disableddisabled systemd-networkd.socket enabled disabled network-online.targetstatic - network-pre.target static - network.target static - # [ -f /etc/resolv.conf ] && lsattr /etc/resolv.conf i-e--- /etc/resolv.conf # ip a show eth0 | grep inet inet 192.168./24 brd 192.168. scope global eth0 # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: 2 installations on the same PC - Add partition in Ftab
soles.g composed on 2024-05-23 12:13 (UTC-0300): > I need help with two topics: > a) install two Fedora40. > Therefore I have two EFI > and that creates 'problems' > Is there anything I can do so the PC doesn't get 'confused'...? On a multiboot PC with only Linux, only one ESP is required, and only one bootloader is required. After the first Linux installation on a PC here, bootloaders are excluded from most if not all. I have 14 PCs with multiple Fedora installations on a single HDD or SSD. On none of them do I have a Fedora bootloader installed. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Who moved my journald.conf?
Tom Horsley composed on 2024-05-09 09:15 (UTC-0400): > On Tue, 7 May 2024 14:19:46 -0400 Felix Miata wrote: >>> Where are journal settings configured these days? >> /etc/systemd/journald.conf.d/ for overrides & customizations. > So if I put a .conf file in that directory, does it also need > to have the [Journal] line at the beginning? Like so: > [Journal] > option=setting > option=setting... I think this is what you want: man systemd.syntax -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Who moved my journald.conf?
Tom Horsley composed on 2024-05-07 14:34 (UTC-0400): > On Tue, 7 May 2024 14:19:46 -0400 Felix Miata wrote: >> /etc/systemd/journald.conf.d/ for overrides & customizations. > A directory which also doesn't exist :-). Like other /etc/**.conf.d/ directories in a systemd environment, it's optional, a place to override things one isn't happy with in the /usr/ tree. # cat /etc/systemd/journal.conf.d/local.conf [Journal] Storage=persistent SystemMaxFiles=10 RuntimeMaxFiles=12 ForwardToConsole=yes TTYPath=/dev/tty10 Audit=no # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Who moved my journald.conf?
Tom Horsley composed on 2024-05-07 14:09 (UTC-0400): > I have a bunch of journal setting I normally change in > /etc/systemd/journald.conf. > In fedora40 there doesn't appear to be such a file. > Where are journal settings configured these days? /etc/systemd/journald.conf.d/ for overrides & customizations. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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 40 and nouveau
SPA plugin is missing or broken. Some camera types may not be supported. # aplay /usr/local/share/sound/alsa/test.wav Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ OK HDMI output :) # aplay -D default /usr/local/share/sound/alsa/test.wav && sleep 5 Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ OK HDMI output :) # aplay -D hdmi:0,3 /usr/local/share/sound/alsa/test.wav Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ OK HDMI output :) # aplay -D hw:0,9 /usr/local/share/sound/alsa/test.wav Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ OK HDMI output :) # aplay -D hdmi /usr/local/share/sound/alsa/test.wav Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ but no output :( # aplay -D hdmi:0,0 /usr/local/share/sound/alsa/test.wav Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ but no output :( # aplay -D hdmi:0,1 /usr/local/share/sound/alsa/test.wav Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ but no output :( # aplay -D hw:0,3 /usr/local/share/sound/alsa/test.wav Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ but no output :( # aplay -D hw:0,7 /usr/local/share/sound/alsa/test.wav Playing WAVE '/usr/local/share/sound/alsa/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo ## ^ but no output :( # Good luck with your audio. Getting Linux audio to me is inexplicable hocus pocus. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: System upgrades. Where is the / filesystem?
Charles Dennett composed on 2024-05-02 13:08 (UTC-0400): > ...To find > the biggest offenders, cd to one of those directories (/var/cache for > example) and then use the command "sudo du -sh *" to get a listing of > each file/directory in the current directory and their sizes. You'd > have to investigate further to see what can be safely removed. Or simply ncdu -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: System upgrades. Where is the / filesystem?
John Pilkington composed on 2024-05-01 09:31 (UTC+0100): > I'm not aware of any snapshots, and suspect that Felix has a quicker way > of finding the relevant 'freespace' than waiting for dnf's version to > appear. Perhaps it's shown during the 'rpm --force' installs? I have > around 3400 packages. Math is required. Unless your packages cache is elsewhere than on an extX / filesystem, do: df / Did it yet increase by as much as the amount of additional freespace required that dnf system-upgrade first reported? If no, upgrade and remove another large rpm from the filesystem, and check again. Repeat until the number has become large enough. This only works as intended with a real remove, not with some file manager that moves to trash instead of actually removing. I use only mc or fcl or various cmdline utils for file management, never Dolphin or Thunar or any other GUI file manager. Also, if you added kernel* to dnf.conf skip list, you can remove it from the cache. DNF pretends everything in the skip list does not exist. The 5 raw 6.8.7 or 6.8.5 rpms are well upwards of 100MB. When time comes that upgrade has otherwise completed, kernel* must be removed from the skip list to allow dnf to upgrade to the current kernel. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: System upgrades. Where is the / filesystem?
John Pilkington composed on 2024-04-30 18:58 (UTC+0100): > Hi all: I have two old systems (with old nVidia graphics), recently > upgraded from f38 to f39 and both at present using nouveau. One was > OK-ish, the other had screen-recognition and HDMI-audio issues, and I > thought it might be worth trying the more-mainstream f40. > Now the main problem is with the previously OK (single-boot) box, which > reports after the download and dnf-testing that > "At least 446 MB more space (is) needed on the / filesystem". > Google (fedoraforum) has a suggestion of trimming the journalctl log, > but neither that nor any other space-clearing actions that I have tried > has made any difference. KDiskFree shows multi-GB space on all except > current /boot and a hopefully inactive remnant of another, much > older/boot with a different mount point. Both of those have sizes > around 450 MB and free space around 150 MB. TTBOMK only the current > 6.8.7 f39 kernel and its rescue version are installed. > Suggestions? Thanks. This is easy enough to fix. I've needed to do this many times. First, if more than one kernel remains installed, remove all but the latest working one. If freespace hasn't risen sufficiently following kernel removals, add the kernel to /etc/dnf/dnf.conf locks group so that a new kernel won't be part of the initial upgrade. Then try the system upgrade again. If that didn't make freespace adequate, navigate to the system-upgrade packages cache. Find the largest few rpms contained there. Determine that they are related to X and/or DE or other non-crucial subsystem rather than any crucial basesystem components. Fonts, themes, wallpapers and icons are such candidates. Force install one with rpm, then delete the rpm. Check freespace. If not yet adequate, force install another. When freespace becomes adequate, resume the system upgrade process. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Unable to do F40 Live Workstation install on machine with very old graphics
John Pilkington composed on 2024-04-27 12:54 (UTC+0100): > Felix Miata wrote: ... >> System: >>Host: mcp61 Kernel: 6.6.23-1-longterm arch: x86_64 bits: 64 compiler: gcc >> v: 13.2.1 clocksource: tsc avail: acpi_pm parameters: >> root=LABEL= >> ipv6.disable=1 net.ifnames=0 noresume consoleblank=0 preempt=full >> mitigations=off ... Notice absence of X graphics parameters (rhgb,quiet,nouveau,nvidia,drm,video,etc) on the kernel cmdline. >> Graphics: >>Device-1: NVIDIA C61 [GeForce 6150SE nForce 430] vendor: Micro-Star MSI >> driver: nouveau v: kernel non-free: series: 304.xx >> status: legacy (EOL~2017-09-xx) last: release: 304.137 kernel: 4.13 >> xorg: 1.19 arch: Curie process: 90-130nm built: 2003-2013 ports: >> active: VGA-1 empty: none bus-ID: 00:0d.0 chip-ID: 10de:03d0 >> class-ID: 0300 >>Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 >> compositor: kwin_x11 driver: X: loaded: modesetting dri: nouveau >> gpu: nouveau display-ID: :0 screens: 1 Loaded X driver: modesetting, the upstream default for all AMD, Intel and NVidia GPUs. >>Screen-1: 0 s-res: 1680x1050 s-dpi: 108 s-size: 395x246mm (15.55x9.69") >> s-diag: 465mm (18.32") >>Monitor-1: VGA-1 model: Dell P2213 serial: built: 2012 >> res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") >> diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 ... > The dual-boot box doesn't boot straight into graphics mode, pausing > while waiting to exit the plymouth screen and hanging after failing to > start abrtd.service. > ctrl-alt-F2 allows login, and plasmastart-wayland gives a 800x600 > plasma screen and starts wifi. I haven't yet found a bootline that does > better than this. Mostly the system just freezes. > I had installed the updated rpmfusion 340xx packages, without useful > results, before trying the updated 470xx. There are still references to > a 340xx config in the Xorg log. > #inxi -GSaz --zl --hostname > System: >Host: FedWin4c1 Kernel: 6.8.7-200.fc39.x86_64 arch: x86_64 bits: 64 > compiler: gcc v: 2.40-14.fc39 clocksource: tsc avail: hpet,acpi_pm > parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.7-200.fc39.x86_64 > root=/dev/mapper/fedora_localhost--live-root ro > rd.driver.blacklist=nouveau modprobe.blacklist=nouveau ... Absent complete, competent installation of proprietary NVidia drivers, blacklisting of nouveau kernel module completely blocks X competence. > Graphics: >Device-1: NVIDIA GK208B [GeForce GT 710] vendor: ASUSTeK GT710-SL-1GD5 > driver: nvidia v: 470.239.06 alternate: nouveau,nvidia_drm non-free: > series: 470.xx+ status: legacy-active (EOL~2024-09-xx) arch: Fermi 2 > code: GF119/GK208 process: TSMC 28nm built: 2010-2016 pcie: gen: 2 > speed: 5 GT/s lanes: 8 bus-ID: 01:00.0 chip-ID: 10de:128b class-ID: > 0300 >Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6 > compositor: kwin_wayland driver: X: loaded: N/A No X driver loaded (neither nvidia nor nouveau), no competence from X. alternate: nvidia > gpu: nvidia display-ID: 0 >Monitor-1: Unknown-1 res: 800x600 FOSS graphics setup can't be mixed with proprietary NVidia. One or the other to the exclusion of the other is the only way that can work competently. All of NVidia driver installation's changes must be 100% purged in order to enable FOSS to do its job. That's never been a problem here, as I've only ever installed FOSS drivers on my own hardware, including more than 5 NVidias running F39 and/or F40. # inxi -GSaz --zl --hostname System: Host: p5bse Kernel: 6.7.11-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 2.40-14.fc39 clocksource: tsc avail: hpet,acpi_pm parameters: ro root=LABEL= ipv6.disable=1 net.ifnames=0 selinux=0 plymouth.enable=0 consoleblank=0 mitigations=off Desktop: TDE (Trinity) v: R14.1.1 tk: Qt v: 3.5.0 wm: Twin v: 3.0 with: kicker vt: 7 dm: 1: TDM 2: XDM Distro: Fedora Linux 40 (Forty) Graphics: Device-1: NVIDIA GF119 [NVS 310] vendor: Hewlett-Packard driver: nouveau v: kernel non-free: series: 390.xx+ status: legacy (EOL~2022-11-22) last: release: 390.157 kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx process: 40/28nm built: 2010-2016 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports: active: DP-1,DP-2 empty: none bus-ID: 01:00.0 chip-ID: 10de:107d class-ID: 0300 temp: 50.0 C Display: x11 server: X.Org v: 1.20.14 compositor: Twin v: 3.0 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 2560x2490 s-dpi: 120 s-size: 541x527mm (21.30x20.75") s-diag: 755mm (2
Re: Unable to do F40 Live Workstation install on machine with very old graphics
Andre Robatino composed on 2024-04-27 03:56 (UTC): > I have 2 desktops, each running Fedora, the one in question is a backup that > I normally just log into with ssh and do updates, and would only use normally > if the main machine dies. I'll probably be buying a new machine in a year or > two and this one will go into storage, all of its hardware is old and I doubt > it's worth upgrading major parts of the hardware at this point. My suggestion was for a trivial investment of $0-$25US for an old used GPU that may be collecting cobwebs in a dead PC or on a shelf but works much better than a 6150SE. If another GeForce, it would be completely plug 'N play. Even if an AMD it could nevertheless be pure PNP. OTOH, why install afresh rather than upgrade from F39 to F40 in the first place? I love how well upgrades go, and have no love for all the changes required of a fresh install to accommodate my preferences. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Unable to do F40 Live Workstation install on machine with very old graphics
Andre Robatino composed on 2024-04-27 02:49 (UTC): > I have an old machine from 2008 with very old integrated graphics (GeForce > 6150SE nForce 430). Up to and including F39, I was able to do a Live > Workstation install simply by using the nomodeset boot option. With F40 that > no longer works - it fails to come up in graphical. I ended up doing a > netinstall, but it came up in text mode instead of graphical, and suggested > VNC, which I was able to use to do a graphical install (necessary since I > wanted to preserve /home, requiring custom partitioning). After installation, > it turns out that by replacing gdm with another display manager (I used > lxdm), I could even use GNOME, though screen locking, which requires gdm, > doesn't work - not a big deal. # inxi -GSaz --zl --hostname System: Host: mcp61 Kernel: 6.6.23-1-longterm arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc avail: acpi_pm parameters: root=LABEL= ipv6.disable=1 net.ifnames=0 noresume consoleblank=0 preempt=full mitigations=off Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 info: frameworks v: 5.115.0 wm: kwin_x11 dm: 1: KDM 2: XDM Distro: openSUSE Tumbleweed 20240403 Graphics: Device-1: NVIDIA C61 [GeForce 6150SE nForce 430] vendor: Micro-Star MSI driver: nouveau v: kernel non-free: series: 304.xx status: legacy (EOL~2017-09-xx) last: release: 304.137 kernel: 4.13 xorg: 1.19 arch: Curie process: 90-130nm built: 2003-2013 ports: active: VGA-1 empty: none bus-ID: 00:0d.0 chip-ID: 10de:03d0 class-ID: 0300 Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 compositor: kwin_x11 driver: X: loaded: modesetting dri: nouveau gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 1680x1050 s-dpi: 108 s-size: 395x246mm (15.55x9.69") s-diag: 465mm (18.32") Monitor-1: VGA-1 model: Dell P2213 serial: built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 egl: 1.4 drv: nouveau device: 1 drv: swrast gbm: egl: 1.4 drv: nouveau surfaceless: egl: 1.4 drv: nouveau x11: egl: 1.4 drv: nouveau inactive: wayland API: OpenGL v: 4.5 compat-v: 2.1 vendor: mesa v: 24.0.3 glx-v: 1.4 direct-render: yes renderer: NV4C device-ID: 10de:03d0 memory: 115.2 MiB unified: no # I've never tried Fedora on my old beast. It's functional in Debian 12 as well as openSUSE TW and Leap, but if you diligently search the web, you're likely to find confirmation that the 6150SE was likely the most troublesome and/or lowest value GeForce NVidia ever put to market. If you wish to keep that PC useful, I suggest finding a better GPU to install, even if that means it must be PCI rather than PCIe. I have a similar aged P4D with a passively cooled GeForce 8400 PCI that does a respectable job for something so old and inexpensive, and better than my 6150SE. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Stuck at grub prompt after reordering partitions
Klaus-Peter Schrage composed on 2024-04-21 18:15 (UTC+0200):
...
It really doesn't take much to load a kernel and initrd. All my EFI PCs have
only one Grub installation, even though there are upwards of 12 distros
installed on each PC, no VMs. One of the latest updated hosts this:
menuentry "Fedora 40 defkernel 3 on P14" {
load_video
set gfxpayload=keep
search --no-floppy --set=root --hint-baremetal=ahci0,gpt14 --label
tg1p14f40 3
linux /boot/vmlinuz root=LABEL=tg1p14f40 noresume audit=0
initrd /boot/initrd
}
That stanza lives in nvme0n1p7's /boot/grub2/custom.cfg, which is 100% under my
own
control, and is automatically offered by the installed Grub's
/boot/grub2/grub.cfg.
That file is pointed to by /EFI//grubx64.efi on the ESP, as directed
by
NVRAM, which ATM has only 2 entries:
# efibootmgr
BootCurrent:
Timeout: 1 seconds
BootOrder: ,0001
Boot*
HD(1,GPT,<...>1b27,0x800,0xa)/File(\EFI\\grubx64.efi)
Boot0001* UEFI OS
HD(1,GPT,<...>1b27,0x800,0xa)/File(\EFI\BOOT\BOOTX64.EFI)424f
#
Where you see above is the actual value in /etc/default/grub's
GRUB_DISTRIBUTOR= on EXT4-formatted nvme0n1p7.
If you can correctly equate your installed values for those in my Grub stanza
above, you should be able to boot by typing in each of the necessary lines from
your grub> prompt to get booted.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
--
___
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: Stuck at grub prompt after reordering partitions
Klaus-Peter Schrage via users composed on 2024-04-17 16:48 (UTC+0200): > After many years of maintaing dual boot setups (Fedora/Windows) my > harddisk layout got a bit confusing: Linux and Windows partition were > scattered on mainly two harddisks (all gpt). I was able to free a third > harddisk (ssd) and copied the linux partitions boot, root and home over > to the new disk, where they now reside as /dev/sda1, /dev/sda2 > and /dev/sda3. > I left the efi-partition on the disk /dev/sdc together with Windows 11. > As in /etc/fstab all partitions are identified by their UUID, I didn't > feel a need to adjust that file. > Trying to boot brought me to the grub command line prompt. After some > trial and error, the appropriate sequence of grub commands (set > root=..., linux ..., initrd ...) made the system boot into a fully > working Fedora 39 installation. > From there I tried to repair GRUB2, following the guidelines at > https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configuration_on_UEFI_systems > namely those three steps: > # rm /boot/efi/EFI/fedora/grub.cfg > # rm /boot/grub2/grub.cfg > # dnf reinstall shim-* grub2-efi-* grub2-common > But rebooting still gets me to the dreaded grub>. > So what am I missing? > BTW, I did NOT use the grub2-install command which shoud not be used on > UEFI systems. It seems like you're using UEFI, yet remain unaware of the efibootmgr command. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: crippling nvidia display issue.
home user composed on 2024-04-11 19:49 (UTC-0600): > What does the -100 vs. -200 signify? From observation, not reading any doc: A fresh Fedora release gets -300, moving the prior release to -200, and the prior to prior release to -100. After the prior-prior's support ends, there is only current, prior, and rawhide. At some later point, next release gets branched from Rawhide. I think it's at or before branching that prior gets switched from -200 to -100, and current gets switched from -300 to -200. So, latest/current, with next imminent, is F39 is -200 and F38 is -100, with F40 about to be released with -300. Does it actually have any more meaning? I haven't been able to spot anything more than at upgrade time, allowing the same version of kernel to be installed twice, first within the old release, then again from upgrading to the new release. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: imminent /boot problem. [SOLVED (for a while!)]
home user composed on 2024-02-25 21:17 (UTC-0700): > On 2/24/24 11:49 PM, Tim via users wrote: >>>> I'm curious how you installed it in the first place, then? >> home user: >>> That was about 11 years ago, so my memory of that is foggy and >>> incomplete. >>> I installed windows-7 first, probably from a CD purchased from a >>> local (near Washington, D.C) store. >>> Then using either a CD burned by a co-worker who was a sys. admin. >>> (most likely), or a CD that came with a thick paperback introductory >>> sys. admin. book, or a CD that I burned from windows, I installed >>> Fedora. It took a few tries. Then one day the installation process >>> just worked (seemingly like magic). That's all that I recall. >> You can run live versions from a disc. Does the computer only have a >> CD drive, or does it have a DVD? CD-only would make it hard. > I have one cd/dvd drive. It's slow and, h, "touchy". I still use it for > some back-ups. Based on what others have said in this thread, I prefer to > not try any re-partitioning or installing. It's too risky for me. CD/DVD drives in desktop PCs made in this century are cheaply made commodities. I've paid as little as $17 for a brand new DVD writer in the past decade. They are typically held in place by 4 or fewer phillips screws, and connected to a data cable and a power cable. Changing one can take as little as about 3 minutes. If the PC is old enough (not terribly likely in a PC that isn't older than 11 years) it could have a PATA rather than an SATA interface. PATA drives have jumpers than need to be appropriately set in order for them to behave as expected, according to the cable type used and the position on a 2" wide 3-connector cable (most cables have 3, none have more, some only have 2). Touchiness and lack of predictability and reliability could be because you have an inappropriately set jumper that takes minimal effort to move. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: imminent /boot problem.
Samuel Sieb composed on 2024-02-23 16:48 (UTC-0500): > home user wrote: >> -bash.4[~]: fdisk -l >> Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors >> Disk model: ST2000DM006-2DM1 >> Units: sectors of 1 * 512 = 512 bytes >> Sector size (logical/physical): 512 bytes / 4096 bytes >> I/O size (minimum/optimal): 4096 bytes / 4096 bytes >> Disklabel type: dos >> Disk identifier: 0xfde8da65 >> Device Boot Start End Sectors Size Id Type >> /dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT >> /dev/sda2 206848 1859026943 1858820096 886.4G 7 HPFS/NTFS/exFAT >> /dev/sda3 1859026944 1860050943 1024000 500M 83 Linux >> /dev/sda4 1860050944 3907029167 2046978224 976.1G 5 Extended >> /dev/sda5 1860052992 1876436991 16384000 7.8G 82 Linux swap / >> Solaris >> /dev/sda6 1876439040 1981296639 104857600 50G 83 Linux >> /dev/sda7 1981298688 3907028991 1925730304 918.3G 83 Linux > You could take 1GB off your swap partition and move the /boot partition > to there. That, or any other size that pleases, though if the swap is routinely used for hibernating and requires it all, complications grow among the possibilities. > If you had live boot capability, I would suggest moving the space up to > where /boot is now, but I don't think you can do that while running it. With swap off and /boot unmounted, swap could be deleted, boot enlarged to whatever size desired, then swap recreated in whatever remains unused. If live boot is truly impossible, this process should be easy enough to do by temporarily moving the disk to some other computer. Another option would be to shrink either sda7 or sda2. With the latter option, move sda3 then enlarge. With the former it's more complicate because of the MBR partitioning, create a new partition. The new boot at the end of disk would have to be created after deleting sda3 if you wish the new to remain a primary, because you can't have more primaries than you already have. If you're OK to have the new boot be a logical, then it's not an issue. Personally that wouldn't happen, as my boot partitions are always ever primary, because that's where I put Grub, not on the MBR, where Windows compatible code always stays. To be clear, sda4 here is a special case. It defines a location within which logical partitions live, but it doesn't need to be manually or consciously taken into account for these processes. Better partitioning tools automatically recreate it as and if required to fit any legal group of logicals. Therefore, adjusting it shouldn't require it be given any thought beyond the fact that it consumes a primary partition table entry. It can be pretended to not exist notwithstanding existence of its partition table entry. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: imminent /boot problem.
home user composed on 2024-02-22 21:06 (UTC-0700): > Felix Miata wrote: ... >> Does your overall configuration necessitate having boot on its own >> partition? If >> not, and you have plenty of freespace on /, you could remount your /boot/ >> filesystem elsewhere, remove that filesystem from fstab, copy old filesystem >> content to the now empty /boot/ directory on /, and finish by reinstalling >> bootloader. > I don't know. The original install was done 10+ years ago. Not knowing any > better, I very probably just accepted the defaults. Much of what you suggest > here is over my head. >> Another possibility: if there is space that can be made available for a >> completely >> new larger boot elsewhere, make it, and migrate in similar manner to moving >> old >> /boot/'s content to /. /boot/ filesystem need not be on the same disk as /. > There is only one hard drive. > Removing the oldest kernel (dnf remove kernel-core...) looks to have solved > the problem, at least for a while. But thank-you for trying to help. For now you should be fine with that config reduction to 2 kernels, but in the long run, it may be best to gain some understanding of what you have, so better to avoid more unexpected trouble as the system further evolves. Output from: cat /etc/fstab parted -l and/or fdisk -l lsblk -f would enable us to understand your configuration and enable recommendations to be made if indicated, before you get caught in an inextricable bind. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: imminent /boot problem.
home user composed on 2024-02-22 16:30 (UTC-0700): > Is my only real choice to cut back from 2 old kernels to 1 old kernel? Maybe not. Most people don't need to run more than one kernel at a time, or retain more than one as emergency fallback. Does your overall configuration necessitate having boot on its own partition? If not, and you have plenty of freespace on /, you could remount your /boot/ filesystem elsewhere, remove that filesystem from fstab, copy old filesystem content to the now empty /boot/ directory on /, and finish by reinstalling bootloader. Another possibility: if there is space that can be made available for a completely new larger boot elsewhere, make it, and migrate in similar manner to moving old /boot/'s content to /. /boot/ filesystem need not be on the same disk as /. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: kernels > 6.5.12-300.fc39.x86_64 do not boot
Samuel Sieb composed on 2024-02-16 16:34 (UTC-0800): > On 2/16/24 09:23, olivares33561 via users wrote: ... >> Feb 16 11:09:28 fedora kernel: ? >> __intel_display_power_get_domain.part.0+0x52/0x70 [i915] >> Feb 16 11:09:28 fedora kernel: ? ktime_get+0x3c/0xa0 >> Feb 16 11:09:28 fedora kernel: ? exc_page_fault+0x7f/0x180 >> Feb 16 11:09:28 fedora kernel: ? asm_exc_page_fault+0x26/0x30 >> Feb 16 11:09:28 fedora kernel: ? icl_aux_pw_to_phy.isra.0+0x35/0x40 [i915] >> Feb 16 11:09:28 fedora kernel: icl_aux_power_well_disable+0x39/0x1d0 [i915] >> Feb 16 11:09:28 fedora kernel: intel_power_domains_sanitize_state+0x91/0xb0 >> [i915] >> Feb 16 11:09:28 fedora kernel: intel_display_driver_probe_nogem+0x163/0x210 >> [i915] >> Feb 16 11:09:28 fedora kernel: i915_driver_probe+0x707/0xbe0 [i915] > An oops with a page fault in the i915 display driver relating to power > management. Somehow triggered by udev. > No idea what would cause that, but it explains why nomodeset works. So perhaps intel_pstate= kernel cmdline appendages are worth trying?: https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt 31% down from top of file. I'd go first for hwp_only, next no_hwp, then ??? https://www.kernel.org/doc/html/v4.19/admin-guide/pm/intel_pstate.html Has a BIOS upgrade already been checked for? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: kernels > 6.5.12-300.fc39.x86_64 do not boot
olivares33561 users composed on 2024-02-15 16:24 (UTC): ... I have another suggestion. Instead of appending 3 in place of " rhgb" and " quiet" or " nomodeset", append " noresume", either with or without " 3". Another to try: " enforcing=0" Do any of these bring a shell prompt or login screen? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: kernels > 6.5.12-300.fc39.x86_64 do not boot
olivares33561 composed on 2024-02-15 01:25 (UTC): >>> Edit the boot command line to remove "rhgb" and "quiet". Then you can >>> see where it's getting stuck. > I have done that plenty of times, taken pictures but to no avail, it did not > make a difference. I had to revert to old kernel to get successful boot. > Thanks to Felix's suggestion I was able to boot the kernel, but the one > difference in my machine secure boot is enabled. When booting the > screen/menu is hidden and I cannot press e to edit the command line to boot. > So I appeneded nomodeset to the kernel line removing rhgb and quiet from it. > Using gnome with wayland enabled. Can send/appened output of neofetch later > if needed/desired. Let's see how far along your boot gets before the hang. Instead of using nomodeset in place of "rhgb" and "quiet", remove them and add simply a 3. If you land a shell prompt, then the problem is in the GUI somewhere (GDM or Wayland or ???). If you are able to login, try: startx /usr/bin/icewm If you get a command not found error, do: sudo dnf install icewm and try again. Also you should be able to access the journal from a prior unadulterated boot attempt either the same way, or having used nomodeset, which may have needed clues. IOW, try to boot normally into a lockup, then on the immediately following boot, use nomodeset (or if it works, 3) and login. Then: sudo journalctl -b -1 > somefile.txt Then attach somefile.txt to your bug report. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: kernels > 6.5.12-300.fc39.x86_64 do not boot
Samuel Sieb composed on 2024-02-14 13:28 (UTC-0800): > olivares33561 wrote: >> I have installed and tried to boot the 6.6.X kernels in fedora and now the >> latest one 6.7.3 one and >> have not seen a successful boot of such a kernel. I have had to delete the >> kernels every time I try them. > Edit the boot command line to remove "rhgb" and "quiet". Then you can > see where it's getting stuck. > Since you said "nomodeset" lets it boot, what is your graphics chipset? I already indicated in thread, his, as indicated in OP, is identical to mine: Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21 I can't as yet reproduce, but thread hasn't shown much about his software configuration, which more than likely differs, with me using TDE/TDM and F39's ancient Xorg 1.20.14, on NVME/EXT4, and with no Fedora bootloader installed. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: PCI-E to PS2
ToddAndMargo via users composed on 2024-02-13 17:35 (UTC-0800): > Felix Miata wrote: >> ToddAndMargo via users composed on 2024-02-13 17:07 (UTC-0800): >>> Fedora 39 >>> I am trying to find a PCI-E 1x to 2xPS2 adapter >>> that actually works. >>> The only one I could find was >>> https://www.amazon.com/gp/product/B07VB9TD6D >>> and it was dead on arrival: no power to the >>> keyboard. >>> You guys know of one that is Fedora friendly >>> that actually works? >> I too would much rather have a working PCIe card, though I have found >> USB-to-PS/2 >> dongles generally more reliable. I haven't bought one in over a decade, so >> can't >> recommend against any in particular that don't work. This card is >> functionally >> worthless too: >> <https://www.walmart.com/ip/PCI-E-Dual-Port-PS2-Expansion-Adapter-Card-External-PS2-Device-for-PC/1007125601> >> It only works a keyboard after an OS driver loads, so can't be used to get >> into >> BIOS, BBS menu or Grub menu. > It need to work in bios too. My USB dongle will flash > my keyboard very couple of minutes and trash what I am > writing. One of the three dongles I have that work has a Belkin part number: F5U119-E -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: PCI-E to PS2
ToddAndMargo via users composed on 2024-02-13 17:07 (UTC-0800): > Fedora 39 > I am trying to find a PCI-E 1x to 2xPS2 adapter > that actually works. > The only one I could find was > https://www.amazon.com/gp/product/B07VB9TD6D > and it was dead on arrival: no power to the > keyboard. > You guys know of one that is Fedora friendly > that actually works? I too would much rather have a working PCIe card, though I have found USB-to-PS/2 dongles generally more reliable. I haven't bought one in over a decade, so can't recommend against any in particular that don't work. This card is functionally worthless too: <https://www.walmart.com/ip/PCI-E-Dual-Port-PS2-Expansion-Adapter-Card-External-PS2-Device-for-PC/1007125601> It only works a keyboard after an OS driver loads, so can't be used to get into BIOS, BBS menu or Grub menu. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: kernels > 6.5.12-300.fc39.x86_64 do not boot
olivares33561 composed on 2024-02-13 18:18 (UTC): > Felix Miata wrote: >> olivares33561 composed on 2024-02-13 12:21 (UTC-0500): >> > Finally I have successfully booted a kernel > 6.5.12-300.fc39.x86_64 on >> > Fedora. Thanks to all who have helped and provided things to try. I added >> > nomodeset to line, I guess I will have to add it to grub and make it >> > permanent so I do not have problems. >> > olivares@fedora:~$ uname -a >> > Linux fedora 6.7.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5 >> > 22:21:14 UTC 2024 x86_64 GNU/Linux >> > olivares@fedora:~$ >> Nomodeset is never a proper solution. It's designed as a troubleshooting >> parameter and workaround to allow graphical mode system administration and >> log >> access. It kills performance. It disables displays other than the first. It >> usually reduces the screen resolution to something less than the display's >> ideal >> native mode. >> >> https://web.archive.org/web/20230203110609/https://en.opensuse.org/SDB:Nomodeset:_Work_Around_Graphic_Upgrade_&_Installation_Obstacles > If I remove nomodeset from the grub cmdline, the boot hangs and does not > proceed. If I keep it, there is no sound. I have encountered problems > before on other machine(s) where sound does not work on one kernel, but an > update makes it work again(using hdmi). But here I am inexperienced with > nomodeset parameter. I am happy that I can boot the new kernel, but the > sound is not there, maybe a newer kernel can make it work, but I am unsure of > what to expect. It is strange that these things happened, because before for > two or three years it worked flawlessly. I suggest you report a bug that 6.6 and 6.7 kernels are not bootable without using nomodeset, while 6.5 kernels work as expected without nomodeset. https://docs.fedoraproject.org/en-US/quick-docs/bugzilla-file-a-bug/ You may try again to install inxi. If it fails again you may install directly from upstream: https://smxi.org/docs/inxi-installation.htm#inxi-manual-install Inxi is merely a perl script that collects and formats data that facilitates troubleshooting and solving bugs. Once your kernel problem is solved, your sound problem may solve itself, as your issue is apparently graphics-related, to which HDMI sound is coupled. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: kernels > 6.5.12-300.fc39.x86_64 do not boot
olivares33561 via users composed on 2024-02-13 12:21 (UTC-0500): > Finally I have successfully booted a kernel > 6.5.12-300.fc39.x86_64 on > Fedora. Thanks to all who have helped and provided things to try. I added > nomodeset to line, I guess I will have to add it to grub and make it > permanent so I do not have problems. > olivares@fedora:~$ uname -a > Linux fedora 6.7.4-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 5 22:21:14 > UTC 2024 x86_64 GNU/Linux > olivares@fedora:~$ Nomodeset is never a proper *solution*. It's designed as a troubleshooting parameter and workaround to allow graphical mode system administration and log access. It kills performance. It disables displays other than the first. It usually reduces the screen resolution to something less than the display's ideal native mode. <https://web.archive.org/web/20230203110609/https://en.opensuse.org/SDB:Nomodeset:_Work_Around_Graphic_Upgrade_&_Installation_Obstacles> -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: kernels > 6.5.12-300.fc39.x86_64 do not boot
uot;) ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-3: HDMI-A-2 mapped: HDMI-2 pos: top-right model: Dell P2213 serial: built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris inactive: gbm,wayland API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.3.3 glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RKL GT1) device-ID: 8086:4c8b memory: 29.48 GiB unified: yes # What does your kernel cmdline contain? What exactly does "do not boot" mean? GUI login greeter is not reached? No login prompt available on any of the vttys? Does appending nomodeset to the linu line after striking the E key at the boot menu enable "boot" to complete? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: NVMe sector size ?
John Mellor composed on 2024-01-10 12:31 (UTC-0500): > Almost all NVMe drives use 4k sectors. Its actually hard on the drive > to use 512 byte sectors, as when you write a block and sync it, it has > to read and then rewrite the rest of the 4k block. That's unnecessary > writes, shortening your drive life. Most Linux platforms will read the > natural sector size from the drive when you format it, so using 512 byte > sectors is pretty rare these days, unless you forced it of course. # fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: ZTC-PCIEG3-128G Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xdf5ee151 Device Boot Start End Sectors Size Id Type /dev/nvme0n1p12048516095514048 251M 6 FAT16 ... # fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: TEAM TM8FP6256G Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 5B330B05-5C88-4DF5-8359-67FF3E52CDC4 Device Start End Sectors Size Type /dev/nvme0n1p1 2048657407 655360 320M EFI System ... # fdisk -l Disk /dev/nvme1n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: Patriot M.2 P300 512GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 5B330B05-5C88-4DF5-8359-67FF3E52CDC4 Device Start End Sectors Size Type /dev/nvme1n1p1 2048657407 655360 320M EFI System ... Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors Disk model: PNY CS1030 500GB SSD Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 6369E8D7-0B94-4DF5-818C-2CD1A3A780CF Device Start End Sectors Size Type /dev/nvme0n1p1 2048657407 655360 320M EFI System ... All 4 report optimal 512. Is fdisk wrong? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: NVMe sector size ?
lejeczek via users composed on 2024-01-10 10:58 (UTC+0100): > I wonder if anybody played with both sector sizes 512 & 4086 > and if yes so - also had some test results / thoughts to share? > There are bits about it - bit confusing & a mixed-bag - > over the net but I failed to find anything Fedora-specific. I've never encountered information that any SSD uses anything but 512. I certainly wouldn't expect anything on the subject to be Fedora specific. All mine are 512. I don't think the role of bit density is the same on solid state media as on rotating rust. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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.6.x kernels do not boot successfully
olivares33561 via users composed on 2023-12-08 15:52 (UTC):
> olivares@fedora:~/Downloads/kerTeX/Documents/Documents/mptmp$ neofetch
> .',;;,'.olivares@fedora
> .';::;,.---
> .;cc;. OS: Fedora Linux 39 (Workstation
> Editi
> .:cc:. Host: XPS 8940
> .;c;.:dddl:.;ccc;. Kernel: 6.5.12-300.fc39.x86_64
> .:c;OWMKOOXMWd;ccc:.Uptime: 1 hour, 39 mins
> .:c;KMMc;cc;xMMc:ccc:. Packages: 2675 (rpm)
> ,cc;MMM.;cc;;WW::, Shell: bash 5.2.21
> :cc;MMM.;: Resolution: 1600x900
> :ccc;oxOOOo;MMM0OOk.;: DE: GNOME 45.2
> cc:0MMKxdd:;MMMkddc.;; WM: Mutter
> c:XM0';;MMM.;' WM Theme: Adwaita
> c;MMo;c;MMW.;ccc;Theme: Adwaita [GTK2/3]
> c;0MNc.ccc.xMMd:ccc; Icons: Adwaita [GTK2/3]
> cc;dNMWXXXWM0::cc:, Terminal: gnome-terminal
> ;.:odl:.;cc:,. CPU: 11th Gen Intel i5-11400 (12) @
> 4.
> ::'. GPU: Intel RocketLake-S GT1 [UHD
> Graph
> .:cc:;,..Memory: 2157MiB / 7500MiB
> '::cc::;,.
Unless your i5-11400 is defective, or incompatible with your motherboard in some
way, it should not be any problem for running 6.6.x. Here it's fine:
# inxi -CMz --vs --zl --hostname
inxi 3.3.31-00 (2023-11-02)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
Mobo: ASUSTeK model: PRIME B560M-A v: Rev 1.xx serial:
UEFI: American Megatrends v: 1601 date: 05/07/2022
CPU:
Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP
cache: L2: 3 MiB
Speed (MHz): avg: 800 min/max: 800/4400 cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
# inxi -GSaz
System:
Kernel: 6.6.4-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-13.fc39 clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL= noresume
audit=0 ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full
mitigations=off
Desktop: Trinity v: R14.1.1 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Fedora release 39 (Thirty Nine)
Graphics:
Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-12.1 process: Intel 10nm built: 2020-21
ports: active: DP-1,HDMI-A-1,HDMI-A-2 empty: HDMI-A-3 bus-ID: 00:02.0
chip-ID: 8086:4c8b class-ID: 0300
Display: x11 server: X.Org v: 1.20.14 driver: X: loaded: modesetting
dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
s-diag: 944mm (37.18")
Monitor-1: DP-1 pos: primary,bottom-l model: Acer K272HUL serial:
built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: top-left model: NEC EA243WM
serial: built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
Monitor-3: HDMI-A-2 mapped: HDMI-2 pos: top-right model: Dell P2213
serial: built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.2.1 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Graphics (RKL GT1)
device-ID: 8086:4c8b memory: 29.48 GiB unified: yes
#
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
--
___
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: Modern Dual-Boot Setup Prcoedure (Dell XPS)
George N. White III composed on 2023-12-07 19:38 (UTC-0400): > Samuel Sieb wrote: >> Usually there's a key you can press to get a boot selection menu so you >> can one-time boot from the USB without having to change the boot order. > F12 on my Dell systems. On my desktop the monitor is slow to start (using a > cheap USBC to HDMI adapter) so I often miss the window when F12 is active. I have at least one Dell with same issue. Dell is not my only source of such trouble. I just don't bother waiting before hitting F12 (or F2). I repeat hitting it each second or so until I see ack that menu or setup have been triggered. If I miss, C-A-D usually beats init starting to trigger a reset. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: Modern Dual-Boot Setup Prcoedure (Dell XPS)
Samuel Sieb composed on 2023-12-02 13:04 (UTC-0800): Tim Evans wrote: >> Brand New Dell XPS 15 coming tomorrow, to replace my venerable Lenovo >> T530. (Looking forward to something a little lighter to lug around.) >> It's been 10 years since I set the T530 up to dual-boot Fedora and Windows. >> I'm sure I can figure out how to reduce the size of the Windows >> partition to make space for Fedora, but am unsure of the process for >> current PC BIOS and grub setup for dual boot. Or is the Fedora installer >> smart enough to handle it for me? > I suggest using the windows disk tool to shrink the windows partition. > From there the Fedora installer can handle the rest. What I would do first is make sure Windows boots and works as expected. #2: Remove the disk and put it in a safe place for reinstallation if a warranty issue appears. #3: Put in a different disk and install Fedora. #4: install Windows in a VM. > If you can't get into the BIOS setup or boot selection, you might have > to go through windows to get there and enable it. Disabling fast boot > might be necessary as well. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: turn off service that installs sytem updates(kernel) off when one shuts down
olivares33561 via users composed on 2023-12-01 13:49 (UTC): > The newest kernel was installed via a service that runs automatically. I use > command line to install updates. There is a service that installs system > updates and installed the kernel which did not boot on this machine. When > starting the machine it froze and did not boot. The service installed the > latest kernel. How can I prevent it from doing that? How I do it: # grep kernel /etc/dnf/dnf.conf exclude= kernel* plymouth* # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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 screen after login to F39
Michael Eager composed on 2023-11-30 09:36 (UTC-0800): > I upgraded from Fedora 38 to Fedora 39 on an AMD Ryzen 5 5600 > with Nvidia Geforce RTX 3050 graphics card. I'm running KDE > Plasma-X11, not Wayland. > I tried to install the GPU drivers several ways using repos/RPMs, > but was not successful. I am using the Nvidia proprietary > drivers. They support dual monitors with no problems; I've had > problems with the nouveau driver and dual monitors in the past. > I start the system in multi-user (CLI) mode and then run "startx" > to start X11 and Plasma. (I started doing this in F38 because of > sddm hanging, which I was not able to resolve.) > When I log in with my user account and run startx, I get a black > screen (extending across both monitors) with an X cursor. The > cursor moves in response to the mouse, but neither left or right > mouse button do anything. I can get to an alternate console > using alt-F3 and kill the login. > I have discovered a bit of a rain dance to get a working system. I > can log in as root, run startx, and get a working KDE Plasma-X11 > screen. Then I log out to the sddm screen and log in again with > my user account. After this, everything (or almost everything) > works correctly. > I've checked the system logs and the Xorg log for any error > or warning messages, but nothing looks incorrect or at all > informative. > Does anyone have any suggestions or insights into this problem? All good in Plasma/X11 using Intel Graphics, but I'm not using SDDM. I'm still happy with KDM: # inxi -GSaz --vs --zl --hostname inxi 3.3.31-00 (2023-11-02) System: Host: big41 Kernel: 6.6.3-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 2.40-13.fc39 clocksource: tsc available: hpet,acpi_pm parameters: ro root=LABEL= ipv6.disable=1 net.ifnames=0 audit=0 selinux=0 consoleblank=0 Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 7 dm: 1: KDM 2: XDM Distro: Fedora release 39 (Thirty Nine) Graphics: Device-1: Intel 4 Series Integrated Graphics vendor: Biostar Microtech Intl Corp driver: i915 v: kernel arch: Gen-5 process: Intel 45nm built: 2008 ports: active: HDMI-A-1,VGA-1 empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:2e32 class-ID: 0300 Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.2.2 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00") s-diag: 803mm (31.62") Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: NEC EA243WM serial: built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-2: VGA-1 pos: right model: Dell P2213 serial: built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11: drv: crocus inactive: wayland API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 23.2.1 glx-v: 1.4 direct-render: yes renderer: Mesa Intel G41 (ELK) device-ID: 8086:2e32 memory: 1.46 GiB unified: yes # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata -- ___ 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: emacs is hopeless
Ranjan Maitra via users composed on 2023-11-14 13:26 (UTC-0600): > What really irritates me about vi and its friends is that it throws you > out of editing (insert) mode in order to save the file, and needs > another key to come back in. I suppose mcedit, from within or without mc, or filecommander's editor, are not your cup of tea either, perhaps too much like nano? I primarly use both, more often fc's in X, (not available without), rarely vi, and nano only when my primaries are unavailable (as in a limited environment), and emacs as yet, never. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Is AnyDesk any good?
Neal Becker composed on 2023-11-09 17:57 (UTC-0500): > My wife's mother is developing dementia. We got > her a chromebook. We would like to be able to remotely manage it for her, > but we need a solution that does not require her to take any action. Mom had one of these: https://www.grandpad.net/ Remote management is part of the deal, which my brother did, not me. I managed mom, and suggested which buttons to push. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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
NVidia Tesla trouble in both F38 & F39
3 different Tesla cards involved so far: GT210 (not mine) plus G98 and GT218 mine. Without the workaround, screen locks in black except for a few random portions of 80x25 mode characters in upper left. Bad kernels include 6.4.16, 6.5.9 & 6.5.10. OK without workaround: 6.3.12. Which kernels work OK without workaround seem to vary with which NVidia/PC combination. These are slow booting oldsters with no more than 2 CPU threads (here at least). Worse, the G98 is a PCI card, not PCIe. :( <https://www.linuxquestions.org/questions/linux-desktop-74/kernel-6-5-9-gt210-not-supported-by-noveau-blank-screen-fedora-38-a-4175730665/> has the original details. Known workaround so far here is to include vga=791 on kernel cmdline. Not yet tried on Fermis, and not yet tried forced inclusion of nouveau.ko in initrd. From one of 3 PCs involved: # inxi -GSaz --vs --zl --hostname inxi 3.3.31-00 (2023-11-02) System: Host: g5eas Kernel: 6.5.10-300.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 2.40-13.fc39 clocksource: tsc available: hpet,acpi_pm parameters: ro root=LABEL= noresume selinux=0 audit=0 ipv6.disable=1 net.ifnames=0 plymouth.enable=0 consoleblank=0 mitigations=off vga=791 Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 7 dm: 1: KDM 2: XDM Distro: Fedora release 39 (Thirty Nine) Graphics: Device-1: NVIDIA G98 [GeForce 8400 GS Rev. 2] vendor: PNY driver: nouveau v: kernel non-free: series: 340.xx status: legacy (EOL~2019-12-xx) last: release: 340.108 kernel: 5.4 xorg: 1.20 arch: Tesla process: 40-80nm built: 2006-2013 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 link-max: lanes: 16 ports: active: DVI-I-1,VGA-1 empty: none bus-ID: 0b:00.0 chip-ID: 10de:06e4 class-ID: 0300 Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.2.2 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00") s-diag: 803mm (31.62") Monitor-1: DVI-I-1 pos: primary,left model: NEC EA243WM serial: built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-2: VGA-1 pos: right model: Dell P2213 serial: built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 egl: 1.4 drv: nouveau device: 1 drv: swrast surfaceless: egl: 1.4 drv: nouveau x11: egl: 1.4 drv: nouveau inactive: gbm,wayland API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 23.2.1 glx-v: 1.4 direct-render: yes renderer: NV98 device-ID: 10de:06e4 memory: 483.4 MiB unified: no # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Upgrade to F39: Disk Requirements: At least 5633 MB more space needed on the / filesystem.
Paul Smith composed on 2023-11-07 16:46 (UTC): > While running > > dnf system-upgrade download --releasever=39 > > to upgrade Fedora, I get the following error: > > Error Summary - > Disk Requirements: At least 5633 MB more space needed on the / filesystem. > > Could you please help me? > > Thanks in advance, Do you have enabled to keep downloaded packages on disk? If yes, you're likely consuming a lot of space there. Do you have snapshotting enabled on BTRFS? If yes, you may need to delete old snapshots. Do you have more than two installed kernels? If yes, delete the old ones. Do you have firmware installed for hardware you do not have? (keepcache=1 in /etc/dnf/dnf.conf) If yes, try removing it. If you have persistent journal enabled, it may be past time to cull the oldest. I avoid your current problem by enabling a separate filesystem on /var/lib/dnf/system-upgrade just for caching system-upgrade packages. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: restoring fedora boot manager
Bill Cunningham composed on 2023-09-21 20:23 (UTC-0400): > Felix Miata wrote: ... >> Since UEFI, most USB sticks for installation and/or rescue are configured to >> boot >> in either legacy or EFI mode. When the UEFI BIOS has CSM (legacy) booting >> enabled, >> such USB sticks will show two entries per USB stick, one for each mode, >> which is >> why you see above both 0005 and 0006 entries. >> Also with UEFI, it's preferred to have the HDD/SSD's preferred OS as top >> priority, >> and to use the BBS hotkey whenever an alternative boot device is desired >> instead. > Does that mean you use a F key to boot from a USB stick? My UEFI is > always putting the OS before the USB stick. I have to change it to boot > from a USB stick. How do you use this "BBS Hotkey? Exactly the same as you use a BIOS setup key (typically DEL or F2) specific to the various brands and their BIOS: BBS Boot Keys [*]ASRock F11 [*]Asus F8 [*]Biostar F9 [*]Dell F12 [*]eCS F12 or F10 [*]eMachinesF10 [*]EVGA F7 [*]Gigabyte F12 [*]HP F9 or ESC or ESC,F9 [*]IntelF10 [*]Lenovo F12 or F8 or F10 [*]MSI F11 [*]Toshiba F12 What does BBS mean in BIOS? Short for BIOS boot specification, BBS is a BIOS (basic input/output system) feature that creates, maintains, and prioritizes all the IPL (initial program load) devices. While the computer is booting, each IPL device is checked to see if it's bootable. <https://www.computerhope.com/jargon/b/bbs.htm> -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: restoring fedora boot manager
Bill Cunningham composed on 2023-09-21 19:52 (UTC-0400):
> Felix Miata wrote:
>> # efibootmgr -o 0,4,1,2,3
>> BootCurrent: 0005
>> Timeout: 1 seconds
>> BootOrder: ,0004,0001,0002,0003,0005
>> Boot* fedora HD(...
>> Boot0001* UEFI OS HD(...
>> Boot0002* Hard DriveBBS(HD...
>> Boot0003* CD/DVD Drive BBS(CD...
>> Boot0004* Windows...
>> Boot0005* UEFI: USB DISK...
>> Boot0006* USBBBS(HD...
>> # systemctl reboot
>> One command to ID the state.
>> One command to change the state.
>> Another to reboot normally.
>> (Assuming your UEFI BIOS works as it should. Mine all do.)
> I see. I would have ordered it usb stick, dvd,fedora,windows myself :)
Since UEFI, most USB sticks for installation and/or rescue are configured to
boot
in either legacy or EFI mode. When the UEFI BIOS has CSM (legacy) booting
enabled,
such USB sticks will show two entries per USB stick, one for each mode, which is
why you see above both 0005 and 0006 entries.
Also with UEFI, it's preferred to have the HDD/SSD's preferred OS as top
priority,
and to use the BBS hotkey whenever an alternative boot device is desired
instead.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
___
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: restoring fedora boot manager
Bill Cunningham composed on 2023-09-21 18:43 (UTC-0400): > its bootloader will be default. I will need to boot into the fedora > rescue mode. This is where grub will need to be put. With mbr boot, I > used this- > grub2-install /dev/sda > grub2-mkconfig; > Then set the default. All is fine. Now, things are a little more > complicated. For me anyway. They shouldn't be. Once booted to rescue media, all you *should* need is to reorder the UEFI boot priority: # efibootmgr BootCurrent: 0005 Timeout: 1 seconds BootOrder: 0004,,0001,0002,0003,0005 Boot* fedoraHD(... Boot0001* UEFI OS HD(... Boot0002* Hard DriveBBS(HD... Boot0003* CD/DVD Drive BBS(CD... Boot0004* Windows ... Boot0005* UEFI: USB DISK... Boot0006* USB BBS(HD... # efibootmgr -o 0,4,1,2,3 BootCurrent: 0005 Timeout: 1 seconds BootOrder: ,0004,0001,0002,0003,0005 Boot* fedoraHD(... Boot0001* UEFI OS HD(... Boot0002* Hard DriveBBS(HD... Boot0003* CD/DVD Drive BBS(CD... Boot0004* Windows ... Boot0005* UEFI: USB DISK... Boot0006* USB BBS(HD... # systemctl reboot One command to ID the state. One command to change the state. Another to reboot normally. (Assuming your UEFI BIOS works as it should. Mine all do.) -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: GPT Partition
Bill Cunningham composed on 2023-09-15 11:23 (UTC-0400): >> WHat is the reason Peter behind xfs being used on the server edition and >> btrfs on the workstation? I pretty much stick with ext3. I don't even use >> ext4 really. I use EXT3 and EXT4. EXT4 is much faster. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: GPT Partition
Peter Boy composed on 2023-09-15 08:56 (UTC+0200): >> Felix Miata composed: >> BTRFS devs seem to >> think only one is somehow better due to its inclusion of LVM technology. > There is no „inclusion of LVM technology“ in BTRFS. LVM provides you with > several separate filesystems, completely independent from each other. A file > system failure in one LVM volume does not affect any of the other volumes. > All data in other volumes are safe. In BTRFS, everything is a single huge > file system, (sub)volumes are just logical groupings within a single, in the > worst case faulty, file system. You just described "LVM technology": keeping everything (except boot) in one or more partitions or disks logically combined as if only one, with subsections able to be allocated more or less size, and partitions and/or disks added or removed, all while actively in use. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: GPT Partition
Joe Zeff composed on 2023-09-14 20:49 (UTC-0600): > Felix Miata wrote: >> I always have my/home/ on a separate >> filesystem. My guess is it is an administrative thing. They probably get or think they get more and/or wilder complaints about mal-sizing separate filesystems than they do not making them separate. There's a BTRFS component to it too. BTRFS devs seem to think only one is somehow better due to its inclusion of LVM technology. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: GPT Partition
Bill Cunningham composed on 2023-09-14 21:15 (UTC-0400): > I am just starting to get into the UEFI with my newer computer. I > notice that f38's auto partitioning creates a partition and formats it > with xfs. I suppose manually ext4 could be used. This drive I don't > believe is too big for ext4. But it would take a little time to format. > My question is, using manual or "custom" partitioning would I want > a 250-500 MB partition with the ID 0xef00 and then an ext4 partition, > for use with linux? I know M$ adds all kinds of additions to the UEFI > spec. What is needed for linux in making a custom partition set up? UEFI booting requires an ESP (Efi System Partition) whether you want one or not. :) As little as 1 file on it can get Linux booted. UEFI Windows/Linux multibooters get by fine with the original 100M ESP Windows creates by default, typically having far more freespace on the ESP than used. Some people like mixing the OS with user data (only one EXT4 or BTRFS), or keeping it separate (at least 2 EXT4 or BTRFS). I always have my /home/ on a separate filesystem. The OS doesn't really need backing up once you get intimate with the installation process. It's easy enough to install afresh if the OS filesystem gets too messed up. I don't give the OS partition even 20G. Most I don't even give 10G, though all my installations are at least initially minimalist. Right now I'm running on 18G, 3 kernels are installed, and 75% is freespace. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: no network access
Samuel Sieb composed on 2023-08-07 16:13 (UTC-0700): > Wolfgang Pfeiffer wrote: >> From what I know: the passwords might also be in >> /etc/sysconfig/network-scripts/keys-* > ifcfg files are deprecated now. Any recently made connections are > stored in the nmconnection format. And the keys-* files are part of the > ifcfg system. Can you say if that format equates to, or is it similar to, the format systemd-networkd uses? # inxi -S System: Host: big41 Kernel: 6.3.12-200.fc38.x86_64 arch: x86_64 bits: 64 Console: pty pts/0 Distro: Fedora release 38 (Thirty Eight) # rpm -qa | grep -iE 'kmana|d-netw|solv' | sort kf5-networkmanager-qt-5.108.0-1.fc38.x86_64 libsolv-0.7.22-4.fc38.x86_64 systemd-networkd-253.7-1.fc38.x86_64 # cat /etc/systemd/network/eth0.network [Match] PermanentMACAddress=00:00:00:00:00:00 [Network] Address=192.xxx.xxx.xxx/24 DNS=192.xxx.xxx.yyy 1.1.1.1 1.0.0.1 Gateway=192.xxx.xxx.yyy IPv6AcceptRA=no LinkLocalAddressing=no # ls -gG /etc/resolv.conf -rw-r--r-- 1 233 Nov 30 2020 /etc/resolv.conf # ls -Gg /etc/sysconfig/network-scripts/*eth* -rw-r--r-- 1 267 Sep 9 2013 /etc/sysconfig/network-scripts/ifcfg-eth0 -rwxr-xr-x 1 6560 May 4 20:00 /etc/sysconfig/network-scripts/ifdown-eth -rwxr-xr-x 1 14192 May 4 20:00 /etc/sysconfig/network-scripts/ifup-eth # ip a ... 2: eth0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff inet 192.xxx.xxx.zzz/24 brd 192.xxx.xxx.255 scope global eth0 valid_lft forever preferred_lft forever # systemctl list-unit-files | grep net | sort netconsole.service disableddisabled network-online.target static - network-pre.target static - network.service generated - network.target static - systemd-network-generator.service disabledenabled systemd-networkd-wait-online.servicedisableddisabled systemd-networkd-wait-online@.service disableddisabled systemd-networkd.servicedisableddisabled systemd-networkd.socket enabled disabled # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Help needed: disabling system wide the Caps lock key in GNOME/Xwayland
Joachim Backes composed on 2023-08-01 21:30 (UTC+0200): > Hi gys, I'm running F38 with *Gnome/X-Wayland*, and in my environment I > do not need (hate it) the *Caps Lock* key.Question: How to realize the > disabling system wide, and how to get it working again? Whether that's possible or not I have no idea. I had the same problem with scroll lock, but with a keycap puller I pulled the cap and found something soft to stuff under it that makes it hard to push all the way down. Now I can use it if I need to, but it doesn't happen by accident any more. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: console logging during shutdown.
home user composed on 2023-07-25 19:43 (UTC-0600): > I'm very nervous about removing plymouth. Is there a way of controlling > shutdown (and boot-up) logging via configuration files? I would think that > would be much easier and safer. IMO, the primary purpose of Plymouth is to make Linux emulate Windows' boot and shutdown processes, which is to say, hide all that goes on during those processes behind a GUI screen on which little or nothing happens between BIOS/UEFI screen and login screen. I've heard it enables other things, but those things are apparently nothing I have any use for. The only installations I have with Plymouth installed are all Mageia, which creates a basesystem dependency on it and cannot be removed, only neutered. Systemd's journal takes care of boot/shutdown logging, as well as most other logging. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: [8086:2e32] black screen instead of Xorg/KDM unless preempt=none mitigations=off
Felix Miata composed on 2023-07-19 22:49 (UTC-0400): > # inxi -GxxS > System: > Host: big41 Kernel: 6.3.12-200.fc38.x86_64 arch: x86_64 bits: 64 > compiler: gcc v: 2.39-9.fc38 Console: pty pts/0 DM: 1: KDM 2: XDM > Distro: Fedora release 38 (Thirty Eight) > Graphics: > Device-1: Intel 4 Series Integrated Graphics vendor: Biostar Microtech Intl > Corp driver: i915 v: kernel arch: Gen-5 ports: active: HDMI-A-1,VGA-1 > empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:2e32 > Display: server: X.org v: 1.20.14 with: Xwayland v: 22.1.9 driver: X: > loaded: modesetting,vesa unloaded: fbdev gpu: i915 > display-ID: 00srv.ij.net:0 > Monitor-1: HDMI-A-1 model: NEC EA243WM res: 1920x1200 dpi: 94 > diag: 612mm (24.1") > Monitor-2: VGA-1 model: Dell P2213 res: 1680x1050 dpi: 90 > diag: 558mm (22") > API: OpenGL Message: GL data unavailable for root. > # dmesg | head -3 > [0.00] microcode: updated early: 0xa07 -> 0xa0b, date = 2010-09-28 > [0.00] Linux version 6.3.12-200.fc38.x86_64 > (mockbuild@ad82227541134b7bb9538baac1587d1c) (gcc (GCC) 13.1.1 20230614 (Red > Hat 13.1.1-4), GNU ld version 2.39-9.fc38) #1 SMP PREEMPT_DYNAMIC Thu Jul 6 > 04:05:18 UTC 2023 > [0.00] Command line: ro root=LABEL=f38p29-cgn ipv6.disable=1 > net.ifnames=0 audit=0 selinux=0 consoleblank=0 preempt=none mitigations=auto > # dmesg | tail -19 > [8.569886] pci :00:00.0: Intel G41 Chipset > [8.569904] resource: avoiding allocation from e820 entry [mem > 0xbddf-0xbfff] > [8.569906] resource: remaining [mem > 0xc000-0xcfff] available > [8.569916] pci :00:00.0: detected gtt size: 2097152K total, 262144K > mappable > [8.570204] pci :00:00.0: detected 32768K stolen memory > [8.570335] i915 :00:02.0: vgaarb: deactivate vga console > [8.570574] Console: switching to colour dummy device 80x25 > [8.634427] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on > minor 0 > [8.716724] r8169 :01:00.0 eth0: Link is Up - 1Gbps/Full - flow > control rx/tx > [8.816457] fbcon: i915drmfb (fb0) is primary device > [8.816627] Console: switching to colour frame buffer device 210x65 > [8.816637] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device > [ 20.122370] i915 :00:02.0: [drm] *ERROR* [CRTC:45:pipe A] flip_done > timed out > [ 30.362390] i915 :00:02.0: [drm] *ERROR* [CRTC:60:pipe B] flip_done > timed out > [ 30.362411] i915 :00:02.0: [drm] *ERROR* pipe A underrun > [ 41.114370] i915 :00:02.0: [drm] *ERROR* flip_done timed out > [ 41.114377] i915 :00:02.0: [drm] *ERROR* [CRTC:45:pipe A] commit wait > timed out > [ 51.354371] i915 :00:02.0: [drm] *ERROR* flip_done timed out > [ 51.354378] i915 :00:02.0: [drm] *ERROR* [CRTC:60:pipe B] commit wait > timed out > # > Same PC, same kernel version, F37 is all as expected. https://bugzilla.redhat.com/show_bug.cgi?id=2224592 reported complete I/O lockup on boot on Eaglelake 8086:2e32 with various cmdline combinations of consoleblank=/mitigations=/preempt= -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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
[8086:2e32] black screen instead of Xorg/KDM unless preempt=none mitigations=off
# inxi -GxxS System: Host: big41 Kernel: 6.3.12-200.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 2.39-9.fc38 Console: pty pts/0 DM: 1: KDM 2: XDM Distro: Fedora release 38 (Thirty Eight) Graphics: Device-1: Intel 4 Series Integrated Graphics vendor: Biostar Microtech Intl Corp driver: i915 v: kernel arch: Gen-5 ports: active: HDMI-A-1,VGA-1 empty: DP-1 bus-ID: 00:02.0 chip-ID: 8086:2e32 Display: server: X.org v: 1.20.14 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting,vesa unloaded: fbdev gpu: i915 display-ID: 00srv.ij.net:0 Monitor-1: HDMI-A-1 model: NEC EA243WM res: 1920x1200 dpi: 94 diag: 612mm (24.1") Monitor-2: VGA-1 model: Dell P2213 res: 1680x1050 dpi: 90 diag: 558mm (22") API: OpenGL Message: GL data unavailable for root. # dmesg | head -3 [0.00] microcode: updated early: 0xa07 -> 0xa0b, date = 2010-09-28 [0.00] Linux version 6.3.12-200.fc38.x86_64 (mockbuild@ad82227541134b7bb9538baac1587d1c) (gcc (GCC) 13.1.1 20230614 (Red Hat 13.1.1-4), GNU ld version 2.39-9.fc38) #1 SMP PREEMPT_DYNAMIC Thu Jul 6 04:05:18 UTC 2023 [0.00] Command line: ro root=LABEL=f38p29-cgn ipv6.disable=1 net.ifnames=0 audit=0 selinux=0 consoleblank=0 preempt=none mitigations=auto # dmesg | tail -19 [8.569886] pci :00:00.0: Intel G41 Chipset [8.569904] resource: avoiding allocation from e820 entry [mem 0xbddf-0xbfff] [8.569906] resource: remaining [mem 0xc000-0xcfff] available [8.569916] pci :00:00.0: detected gtt size: 2097152K total, 262144K mappable [8.570204] pci :00:00.0: detected 32768K stolen memory [8.570335] i915 :00:02.0: vgaarb: deactivate vga console [8.570574] Console: switching to colour dummy device 80x25 [8.634427] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 [8.716724] r8169 :01:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx [8.816457] fbcon: i915drmfb (fb0) is primary device [8.816627] Console: switching to colour frame buffer device 210x65 [8.816637] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device [ 20.122370] i915 :00:02.0: [drm] *ERROR* [CRTC:45:pipe A] flip_done timed out [ 30.362390] i915 :00:02.0: [drm] *ERROR* [CRTC:60:pipe B] flip_done timed out [ 30.362411] i915 :00:02.0: [drm] *ERROR* pipe A underrun [ 41.114370] i915 :00:02.0: [drm] *ERROR* flip_done timed out [ 41.114377] i915 :00:02.0: [drm] *ERROR* [CRTC:45:pipe A] commit wait timed out [ 51.354371] i915 :00:02.0: [drm] *ERROR* flip_done timed out [ 51.354378] i915 :00:02.0: [drm] *ERROR* [CRTC:60:pipe B] commit wait timed out # Same PC, same kernel version, F37 is all as expected. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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 38: Video ATI Radeon HD 6400M/7400M low resolution after update from Fedora 35
Dario Lesca composed on 2023-07-09 16:15 (UTC+0200): > On my notebook[1] I have update from Fedora 35 to Fedora 37, then to > Fedora 38. > > Now If I start with last Fedora 38 kernel (6.3.11-200.fc38.x86_64) the > system start without fully graphical boot and monitor is set to low > resolution 1024x768 (4:3) instead of the usual 1366x768 (16:9). > If I start with old kerner 5.17.5-200.fc35.x86_64 all work fine. > I have check the initrd of two kernel and I have noticed that into > kernel 6.X the radeon (and also amdgpu) firmware is missing > How to I can resolve my problem? It seems developers no longer use AMD/ATI GPUs as old as yours, so have been missing regressions they cause, and only get fixed by accident or when users report them. Try removing xorg-x11-drv-ati, then restarting X. That should switch Xorg from using the radeon DDX display driver to using the upstream default modesetting DIX display driver. It may solve your problem. > Why the firmware is missing? Package amd-gpu-firmware includes firmware for ati/radeon. If it is not installed, try installing it and restarting X before changing the display driver as above. > [1] > [root@fedora initrd-5]# DISPLAY= inxi -SGaz > System: > Kernel: 5.17.5-200.fc35.x86_64 arch: x86_64 bits: 64 compiler: gcc v: > 2.37-10.fc35 > parameters: > BOOT_IMAGE=(hd0,msdos1)/f9c6018290c14d36a6c3ccae0374bbba/5.17.5-200.fc35.x86_64/linux > root=/dev/mapper/fedora_danila--fedora-root ro > rd.lvm.lv=fedora_danila-fedora/root > rd.lvm.lv=fedora_danila-fedora/swap rhgb quiet LANG=it_IT.UTF-8 > Console: pty pts/2 DM: GDM v: 44.1 Distro: Fedora release 38 (Thirty Eight) > Graphics: > Device-1: AMD Seymour [Radeon HD 6400M/7400M Series] vendor: ASUSTeK > driver: radeon v: kernel > alternate: amdgpu arch: TeraScale-2 code: Evergreen process: TSMC 32-40nm > built: 2009-15 pcie: > gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 2 speed: 5 GT/s ports: > active: LVDS-1 > empty: HDMI-A-1,VGA-1 bus-ID: 01:00.0 chip-ID: 1002:6760 class-ID: 0300 > temp: 54.5 C > Device-2: Alcor Micro Asus Integrated Webcam driver: uvcvideo type: USB > rev: 2.0 > speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.2:4 chip-ID: 058f:a014 > class-ID: 0e02 > Display: server: X.org v: 1.20.14 with: Xwayland v: 22.1.9 compositor: > gnome-shell driver: X: > loaded: radeon unloaded: fbdev,modesetting,vesa dri: r600 gpu: radeon > display-ID: tty: 190x45 > Monitor-1: LVDS-1 size-res: N/A in console modes: max: 1366x768 min: 640x480 > API: OpenGL Message: GL data unavailable in console for root. Recent versions of inxi do not output lines of more than 80-90 characters, suggesting your inxi may be an old version from f35. In f38 inxi is nearly current. You may also try updating thus: sudo inxi -U Recent versions do a much better job with -GSaz. For best results, run it in an X terminal. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Video Display Freezes - Radeon GPU Lockup
Jon Ingason via users composed on 2023-07-08 23:09 (UTC+0200): > skrev Felix Miata: >> David Dembrow composed on 2023-07-08 12:12 (UTC-0400): >>> Recently my video display freezes after a few minutes. The video card >>> is an ATI Radeon dual head. Is there some configuration settings >>> available that may work around whatever my failure may be? >>> The only hint I have about the failure is from the dmesg command I can >>> reach through one of the virtual consoles because of course the >>> graphical video is frozen. I am including the last failure messages below. >> Which Radeon model do you have? Your problem may be related to this problem: >> https://bugzilla.redhat.com/show_bug.cgi > What is the "bug id"? BRO is all kinds of weird compared to BZ source defaults. I didn't notice the bug number isn't showing in the browser urbar, even after reloading: https://bugzilla.redhat.com/show_bug.cgi?id=2220717 -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Not enough swap space to hibernate
Patrick O'Callaghan composed on 2023-07-08 18:09 (UTC+0100): > On Sat, 2023-07-08 at 07:38 -0700, Doug Herr wrote: >> I think the partition will also need to be listed in the Grub boot >> line also. > Yes, I think you're right. In fact I think I even asked about this in > the distant past. It's normal to include the resume location in the initrd, thus including it on the kernel cmdline is either redundant, or an override, depending on the location there specified. > There's an old joke: > "I think I'm getting a combination of memory loss with déjà vu, because > I may have forgotten about this before." :D -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Video Display Freezes - Radeon GPU Lockup
David Dembrow composed on 2023-07-08 12:12 (UTC-0400): > Recently my video display freezes after a few minutes. The video card > is an ATI Radeon dual head. Is there some configuration settings > available that may work around whatever my failure may be? > The only hint I have about the failure is from the dmesg command I can > reach through one of the virtual consoles because of course the > graphical video is frozen. I am including the last failure messages below. Which Radeon model do you have? Your problem may be related to this problem: https://bugzilla.redhat.com/show_bug.cgi -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Gui for fstab?
ToddAndMargo composed on 2023-07-06 20:39 (UTC-0700): > Is there a GUI for settin up a new > drive in fstab? Or do we still need to > use to old one (vi)? Any plain text editor with superuser permission can edit /etc/fstab, including adding new entries. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Long time after login on Fedora 38 KDE
ogio.spam composed on 2023-06-14 15:38 (UTC+0200): > I experience a long time after password to obtain the desktop ready. > Just to be clear, the problem is only with a user. Another user is not > showing this behaviour. > The good user is a new fresh user, the not working is a user with the > home directory copied from an old Fedora with KDE. > I worked on startup, removing all of them, but the problem is still > there. > There is a way to check what is appening after enter password? First thing to try any time Plasma gets weird, is while logged out of it, delete the entire content of ~/.cache/. First login following will take a bit longer while its content gets automatically recreated, but subsequents may be much better. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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 growth (was: /boot problem.)
12-1-default # 11174K vmlinuz; removal freed 233.4 MiB 162928 ./5.16.15-1-default # 11340K vmlinuz 191304 ./5.17.9-1-default # 11475K vmlinuz 205624 ./5.18.15-1-default # 12148K vmlinuz 142544 ./5.19.13-1-default # 10753K vmlinuz 198788 ./6.0.12-1-default # 12407K vmlinuz 198896 ./6.1.12-1-default # 12409K vmlinuz 183924 ./6.2.10-1-default # 13718K vmlinuz The apparent drop in sizes after 5.18.15 is from applying more effective compression. This barely does justice for the total magnitude since 10 years ago, but it does show there have been steadily increasing overall kernel sizes. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: /boot problem.
home user composed on 2023-05-18 16:21 (UTC-0600): > (f37 stand-alone dual-boot workstation) > During this afternoon's patching (via dnf), a warning GUI popped up saying > /boot is full. ... > I'm comfortable using rm in regular hard drive areas like /home. But I'm > neither a trained nor a professional sys.admin. I'm seriously uneasy about > simply rm-ing files in /boot. What should I clear out of /boot, and what's > the best-practice way? > Please tell me what specific information you need to help me so I can provide > it. How many kernels are installed, more than two? If yes, uninstall the oldest. Listing output from tree /boot might suggest something is there that doesn't belong. What size is the filesystem on which /boot/ lives? Separate partition? BTRFS? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: blkid fully broken too chroot has losen sense in addition fstab has received an update not smart and luckily locate works with type the button star
Dorian ROSSE composed on 2023-05-18 12:21 (UTC): > blkid fully broken too chroot has losen sense in addition fstab has received > an update not smart so it has losen a lot of part and luckily locate works > without type the button star finally thanks you in advance to repair whole, Please have English speaking friend translate your Fedora problem. Your English is incomprehensible. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: failing to translate (was: Messages held for moderation)
Dorian ROSSE composed on 2023-05-08 15:15 (UTC): > Few of answer making Please have English speaking friend translate your Fedora problem. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Broken browser? Or broken website...
Todd Zullinger composed on 2023-05-01 12:37 (UTC-0400): > Andre Robatino wrote: >> It's hard to describe, but >> https://discussion.fedoraproject.org is way too long >> vertically and looks like it hasn't loaded fully. There's >> a reference above to turning off "use style" but I don't >> know what that means or if that has anything to do with >> the problem. I wouldn't expect to have to change defaults >> in order to view a Fedora-related site. > Are you using Firefox with the noscript plugin? Or a > different browser, like Seamonkey? > If the former, I found that setting the site to "Trusted" > was not enough. The "Custom" option had to be selected and > the "unrestricted CSS" box had to be checked. Without that, > the site did just as you describe, looking like this: > https://fedorapeople.org/~tmz/discourse.png > I've seen some other comment that things don't work with > Seamonkey very well either. > I think it's an annoyance that sites require such heavy > javascript to function. No luck here finding anything to do with Custom or CSS in NoScript in SeaMonkey. :( -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: More space needed on the / filesystem to upgrade from F37 to F38
Tim via users composed on 2023-05-01 03:38 (UTC+0930): > I gave up doing upgrades, many years ago, there was so many problems > with it: It took absolutely ages (it assesses the current system, > finds out everything that needs to be installed, downloads it, installs > it piece by piece). Conflicts needed resolving, some not very > straight-forward to handle. Backups ought to be made. And you still > had to assess and fix things up afterwards. It was like some kind of > torture. It's been over 42 months since I last booted a Fedora installer (to a 5.3 kernel). Upgrading Fedora has worked in excess of 100 times here (15 multiboot PCs with it). On faster machines, allocating as much as an hour for the process is a gross excess. On less weighty installations it probably can take under 10 minutes if you don't include POSTing time that on some machines takes longer than booting an OS. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Broken browser? Or broken website...
Dave Close composed on 2023-04-30 13:58 (UTC-0700):
> Accessing a page on <https://discussion.fedoraproject.org/>, I am
> presented with a banner reading, "Unfortunately, your browser is
> unsupported. Please switch to a supported browser to view rich content,
> log in and reply." I am unable to scroll beyond the portion of the
> page immediately visible.
> But, of course, I didn't ask for any support. I recognize that my
> browsers of choice may not properly render some web sites that choose
> to use some newer facilities. ("rich content", indeed! I'd be very happy
> without "rich" content.) If I'm stuck, I can use a different browser;
> I know how to do that.
> I wouldn't object to a banner warning me that some parts of the site
> might not render properly on my browser. But fedoraproject.org takes
> things further by refusing to allow the entire page to load. I resent
> their patronizing and holier-than-thou attitude.
> Unfortunately, fedoraproject.org is not the only place I've encountered
> this abomination. What gives the administrators of these places their
> special rights to control the rest of us?
Broken web site! Fallback to "poor" content should always result when "rich"
content is somehow blocked. I think it stinks for any non-financial web site to
demand what software you use to access its site.
SeaMonkey users are among those subjected to this rudeness by
discussion.fedoraproject.org, but they need only toggle off "use style" to enjoy
the full page text unencumbered by text that isn't a perfect match to one's
browser default size and family. Other browsers most likely have a similar
toggle
available.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
___
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: More space needed on the / filesystem to upgrade from F37 to F38
Paul Smith composed on 2023-04-30 15:23 (UTC+0100): > I am trying to use > dnf system-upgrade download --releasever=38 > to upgrade from F37 to F38. However, I am getting this error: > -- > - > Error Summary > - > Disk Requirements: >At least 4020MB more space needed on the / filesystem. > --- > Any ideas? This happens to me often, though not to such degree. Until dnf makes the report, I don't know how much it needs. First thing to do is get rid of trash. If you move things to "trash" rather than deleting, and /home isn't on its own filesystem, it's the logical place to start. Next, clear /var/tmp/ and /var/log and anyplace else you might have unneeded oldies. /var/log/journal/*/ may have a lot of ancient logs that serve no purpose. You can configure excess for autoremoval via /etc/systemd/journald.conf. Whatever is in /var/cache/dnf/ you should no longer need and can remove with dnf clean. Next, I use an upgrade initialization mini-script to get package management upgrades in place before continuing with the rest. It contains: dnf upgrade --releasever=38 dnf* rpm* libsol* glib* systemd* fedor* dracu* hawk* Lastly, locate the largest downloaded rpms and install selected biggies manually using rpm -Uvh --nodeps. Among them are typically graphics firmware, wallpapers, themes & icons, but there are generally some obese others that are perfectly safe to upgrade whilst operating in multi-user mode, anything to do with X, *office, web browsing, etc. After each such upgrade, delete the rpm from the cache. To facilitate the process, navigate to the cache directory using MC. Pretty much anything whose size MC shows with a K or M is candidate to start with. Once you've created however much space dnf reported you need has been freed, finish with dnf. Another option I often use for system-upgrade is attaching an extra filesystem to /var/lib/dnf/system-upgrade before beginning, a pretty good guarantee against lack of freespace. If you've already downloaded most and they're on /, find a place to move them that isn't, and mount that to /var/lib/dnf/system-upgrade before proceeding with another dnf system-upgrade download attempt. Don't forget to add the location to /etc/fstab before running dnf system-upgrade reboot. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: NetworkManager vs systemd-networkd
Mike Wright composed on 2023-04-25 18:43 (UTC-0700): > I've never been a fanboi when it came to NetworkManager so when I > installed f38 I used systemd-networkd. I found it straight forward and > was able to set up my networking very easily. > Does anybody know which way forward Fedora is going? That is, > NetworkManager with nmcli or systemd-networkd with networkctl? Or are > they going to co-exist? I've been using only systemd-networkd over two years no matter what Linux I boot. Given where it came from, I'd be shocked if it went away. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Recently sound does not play as root
Tim via users composed on 2023-03-20 20:28 (UTC+1030): > Felix Miata: >> If the superuser can't do something, how can a mere mortal user be expected >> to do >> same? When the superuser determines *everything* works as expected is time >> enough >> to create the first regular user. ... > Set up an ordinary account for yourself, and always use that. Set up > ordinary accounts for other uers. Do everything, and test things, as > an ordinary user That account would be root. I've been using Linux for well over 3 decades. I've had a subscription to at least one Fedora mailing list for as long as Fedora has existed. I have several dozen PCs, each of which, except for one laptop gifted me that I haven't altered, is multi- multiboot. Only a small handful include Windows. Average installations on each is well over a dozen, with over 50 on at least one. I am their only user. Only one filesystem exists on each for mounting to /home, and all installations mount it. Most installations are used for: 1-testing upgrade processes 2-testing alpha/beta installers 3-bug report QA 4-support for users in various forums where particular hardware is typically relevant to identifying problem solutions that typically involve procedures requiring superuser write access Everyone who reports use of root user doesn't need yet another lecture instead of an answer to a question asked. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Recently sound does not play as root
Samuel Sieb composed on 2023-03-20 00:31 (UTC-0700): > You shouldn't. Why are you trying to do that? If the superuser can't do something, how can a mere mortal user be expected to do same? When the superuser determines *everything* works as expected is time enough to create the first regular user. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: systemd-oomd insanely aggressive with non-DE logins
Andre Robatino composed on 2023-03-12 15:58 (UTC): > BTW, I did notice that the problem was gone during the time that systemd-oomd > wasn't running, so that's definitely the cause. Unfortunately, the mask > command alone isn't enough to prevent it from running, I'd have to either > remove systemd-oomd-defaults or edit some config files. And this really > should be fixed, it's just wrong that anything running in a DE is protected > from being killed, while a non-DE login, or any command run from within that, > isn't. Just a thought: I've never found anything to be automatically running after which I ran multiple systemctl commands in order: stop > disable > mask -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: F37 systemd pulseaudio paradox
Wolfgang Pfeiffer composed on 2023-03-06 18:38 (UTC+0100): > On Mar 06, 2023 at 03:34:38 -0500, Felix Miata wrote: >>I'm not against change, but this is a result of several years of >>system-upgrades, >>and I've never seen anything explaining how to make a switch: ... > In your messages wireplumber does not appear. It seems this software > is managing sound since F34. On this page > https://fedoraproject.org/wiki/Common_F35_bugs#No_sound_after_upgrade_(wireplumber_not_running) > you find > "Wireplumber ... "needs to be running for sound to work"." > The page above provides excellent documentation to find what went > wrong, and how to fix it. It doesn't seem to cover this: # dnf search systemd | grep -iE 'wire|puls|audio|sound' Last metadata expiration check: 0:20:21 ago on Mon 06 Mar 2023 06:11:55 PM EST. # dnf list installed | grep -iE 'wire|alsa|puls' alsa-firmware.noarch 1.2.4-7.fc37 @fedora alsa-lib.x86_641.2.8-2.fc37 @updates alsa-tools-firmware.x86_64 1.2.5-5.fc37 @fedora alsa-ucm.noarch1.2.8-2.fc37 @updates alsa-utils.x86_64 1.2.8-1.fc37 @updates pipewire-libs.x86_64 0.3.66-1.fc37 @updates pipewire-pulseaudio.x86_64 0.3.66-1.fc37 @updates pulseaudio-libs.x86_64 16.1-4.fc37 @updates pulseaudio-utils.x86_6416.1-4.fc37 @updates python3-alsa.x86_641.2.7-3.fc37 @fedora wireplumber.x86_64 0.4.13-1.fc37 @updates wireplumber-libs.x86_640.4.13-1.fc37 @updates zita-alsa-pcmi.x86_64 0.6.1-1.fc37 @updates # $ systemctl --user status wireplumber.service Unit wireplumber.service could not be found. $ This is after rebooting following running dnf swap --allowerasing pulseaudio pipewire-pulseaudio dnf install wireplumber-libs dnf remove pulseaudio-libs-glib2 # removed phonon* too Afterward: dnf install wireplumber $ systemctl --user status wireplumber.service # wireplumber.service - Multimedia Service Session Manager Loaded: loaded (/usr/lib/systemd/user/wireplumber.service: enabled; preset: enabled) Active: inactive (dead) $ aplay /usr/share/sounds/alsa/Noise.wav Playing WAVE '/usr/share/sounds/alsa/Noise.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono But, nothing coming from speakers. $ wireplumber & M 23:58:14.096348 mod.rt ../src/modules/module-rt.c:274:pw_rtkit_check_xdg_portal: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running? M 23:58:14.096462 mod.rt ../src/modules/module-rt.c:1035:pipewire__module_init: found session bus but no portal Failed to connect to PipeWire $ systemctl --user status pipewire-pulse ● pipewire-pulse.service - PipeWire PulseAudio Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: disabled) Active: active (running) since Tue 2023-03-07 00:29:15 EST; 43s ago TriggeredBy: ● pipewire-pulse.socket Main PID: 3398 (pipewire-pulse) Tasks: 2 (limit: 2320) Memory: 1.3M CPU: 44ms CGroup: /user.slice/user-2000.slice/user@2000.service/session.slice/pipewire-pulse.service └─3398 /usr/bin/pipewire-pulse Mar 07 00:29:15 gx62b systemd[2718]: Started pipewire-pulse.service - PipeWire PulseAudio. Mar 07 00:29:15 gx62b pipewire-pulse[3398]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal ru> Mar 07 00:29:15 gx62b pipewire-pulse[3398]: mod.rt: found session bus but no portal Mar 07 00:29:15 gx62b pipewire-pulse[3398]: mod.fallback-sink: can't connect: Host is down Mar 07 00:29:15 gx62b pipewire-pulse[3398]: default: can't run command load-module module-always-sink: Host is down $ # systemctl list-unit-files | grep xdg # Google hits for '"Is xdg-desktop-portal running?" site:fedoraproject.org' that are labeled as to being on ask.fedoraproject.org redirect to discussion.fedoraproject.org URIs totally unrelated to the indicated hit. Apparently https://ask.fedoraproject.org/ also redirects to discussion DDG doesn't return any hits for the same search terms. $ alsa-info.sh output: http://alsa-project.org/db/?f=9b4dd6548b64719700fe9f8dadcdfc47edf600d5 (older) https://paste.centos.org/view/3dbcc4b3 (current; 23hr expire) Is there anything helpful there? What else can I try? Are there additional packages that need to be installed? Where does xdg-desktop-portal come from? -- Evolution as taught in public
Re: 37 systemd pulseaudio paradox
francis.montag...@inria.fr composed on 2023-03-06 08:01 (UTC+0100): > On Mon, 06 Mar 2023 01:47:44 -0500 Felix Miata wrote: >> Can anyone reconcile the following? >> # journalctl -b --no-hostname | grep pulse >> Mar 06 01:38:45 systemd[577]: pulseaudio.socket - Sound System was skipped >> because of a failed condition check (ConditionUser=!root). >> Mar 06 01:38:45 systemd[577]: pulseaudio.service - Sound Service was skipped >> because of a failed condition check (ConditionUser=!root). > A systemd user for root has been attempted (pid 577, not 1). > The ConditionUser forbid to start it. >> # systemctl cat pulseaudio.service >> No files found for pulseaudio.service. >> # systemctl cat pulseaudio.socket >> No files found for pulseaudio.socket. >> # > This is a user unit. Use thus: systemctl --user cat pulseaudio.service Interesting. How would a global configuration change be implemented, since any edit made for a user who runs it goes into a user settings directory? > You seem to have pulseaudio installed, but as far as I now, pipewire should > replace it nowadays. I'm not against change, but this is a result of several years of system-upgrades, and I've never seen anything explaining how to make a switch: # rpm -qa | grep -iE 'pulse|wire' pulseaudio-libs-16.1-4.fc37.x86_64 pulseaudio-16.1-4.fc37.x86_64 pulseaudio-libs-glib2-16.1-4.fc37.x86_64 # dnf search pipewire | wc -l Last metadata expiration check: 2:43:14 ago on Mon 06 Mar 2023 12:29:01 AM EST. 54 # With close to 54 possibilities, it's unlikely I'd choose correctly what to install, or whether or which pulse packages to remove. Is there a conversion script available? Googling site:fedoraproject.org switch from pulseaudio to pipewire Produced https://ask.fedoraproject.org/t/how-do-i-switch-from-pulseaudio-to-pipewire-and-back/27441 that seemed appropriate, but clicking on it loaded https://discussion.fedoraproject.org/t/article-proposal-playing-with-modular-synth/27441 instead. 2nd hit was https://ask.fedoraproject.org/t/how-to-switch-from-pipewire-to-pulseaudio-on-fedora-37/29356 but clicking it produced 404. The few remaining I skipped. Searching elsewhere was also unhelpful. :( -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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
37 systemd pulseaudio paradox
Can anyone reconcile the following? # journalctl -b --no-hostname | grep pulse Mar 06 01:38:45 systemd[577]: pulseaudio.socket - Sound System was skipped because of a failed condition check (ConditionUser=!root). Mar 06 01:38:45 systemd[577]: pulseaudio.service - Sound Service was skipped because of a failed condition check (ConditionUser=!root). # systemctl cat pulseaudio.service No files found for pulseaudio.service. # systemctl cat pulseaudio.socket No files found for pulseaudio.socket. # How can a condition be checked and fail if there are no such files connected to a service or socket checked? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: tar
Patrick Dupre composed on 2023-02-01 20:24 (UTC+0100): > To create a tar file, I used to create a list and to make > tar -cvzf arch.tgz $list > However, if there are file names with a space, this space is > interpreted as file name separator. > How can I fix this, > either when I tar, or when I create the list? Rename the files to exclude spaces. Filenames with spaces are administrative headaches. mothersRecipesForPancakes01.txt is understandable enough that spaces aren't necessary. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Weird multiple display issue
Thomas Cameron via users composed on 2023-01-25 14:19 (UTC-0600): > I have a multi monitor machine. The displays are set up like this: > + + + > + > So I have three large monitors and a smaller tablet below the far right > monitor. > The weird thing is, it seems like the desktop THINKS my screen looks > like this: > + + + > + + + I can't tell you if it differs for Wayland users, but for Xorg users, that's exactly what you have, vast expanses of the defined desktop space that is not available for display, other than via a screenshot. Desktop spaces are always rectangles defined by the extremities. e.g. > https://imgur.com/a/gUBsgML That is not available here, because scripts must be enabled for the site to display anything useful. If you wish it fixed, move the tablet up alongside screen #3 with bottoms flush. Then your untouchable space will be limited to space above the top of the tablet. Alternatively, relocate the leftmost screen over or under screen #2. Hopefully, the screenshots I uploaded can help with understanding, if help is needed. Their individual life expectancies are a week each. Included in each is an arandr window that depicts the logical screen placements. All were made on F37 freshly upgraded except for using a 6.0.18 kernel: 1-4 different size displays tightly clustered, with one app open cornered at farthest distance from center of overall desktop per display: https://paste.opensuse.org/pastes/06e36edeccd6 2-same as #1, except each of the 4 cornered windows has been maximized: https://paste.opensuse.org/pastes/9e45b16325ec 3-twin smaller displays with 2 different larger displays, with windows as in #1: https://paste.opensuse.org/pastes/b356918e6712 4-same as #3, except each of the 4 cornered windows has been maximized: https://paste.opensuse.org/pastes/0c7e690a57fa 3 & 4 have a roughly similar effect on the overall desktop boundaries as in OP: on the right side there's a drop below the bottom of the left screen, causing anything left of the portion of that display that is below the left display to be unreachable with any pointing device, but visible in a screenshot, because Xorg desktops are rectangles. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Why do I see Xwayland when the desktop is on X11?
Tim via users composed on 2023-01-20 17:17 (UTC+1030): > On Thu, 2023-01-19 at 19:55 -0500, Felix Miata wrote: >> He doesn't attempt to keep the man page fully up to the capability of >> the binary. > How are you supposed to use things properly when the instructions are > wrong? His time is limited. His focus is on getting the binary to do as much right as possible. He gets less cooperation in the data accumulation than he needs to make that possible. If he wasn't wasting so much time working around lack of data, he would have more for documentation. He says that WRT Wayland that available docs are too limited for the moving target that it is. My power is limited to providing data, and making suggestions. If you can find something better, use it. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Why do I see Xwayland when the desktop is on X11?
Patrick O'Callaghan composed on 2023-01-19 17:15 (UTC-0500): > , and, if applicable: unloaded:, f ... > which doesn't match what I'm getting. So either a bug in inxi or a bug > in its man page. Man page version you see is incomplete. I mentioned in irc://irc.oftc.net/#smxi <https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/RC645ORG63PKKJHTGBLPKRDRHF7EXGED/> to the author, and his response was the next release will slightly change -G, and the man page will note the conditions that result in Xwayland appearing in output for -G run within an Xorg session. He doesn't attempt to keep the man page fully up to the capability of the binary. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Why do I see Xwayland when the desktop is on X11?
Patrick O'Callaghan composed on 2023-01-19 12:43 (UTC): > I run my desktop (KDE) by selecting Plasma(X11) at the login screen. > However I see this from inxi: > $ inxi -G > ... > Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.7 driver: X: > Why is this? I understood Xwayland to be a shim between Wayland and X11 > clients, and a look at pgrep shows no instance of Wayland running. I complained about this upstream when it first appeared. The answer didn't really gel, but it's basically a result of Wayland existing on the installed system, ostensibly able to be run if desired. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Manually get memtest 6.01 to work on both Legacy and UEFI boot with Fedora.
Michael D. Setzer II via users composed on 2023-01-16 03:11 (UTC+1000): > Where exactly did you get the mt83x64.efi file? did a > quick search, and didn't find a link. Took it off the free .iso download. > Another issue is latest 6.01 is dated 12/30/2022, while > you file is dated 11/22/2019? Don't know how the tests > between the to options are. I have no RAM newer than the file, so no incentive to find newer. > Will have to do some more searching. Also, your file is > much larger than the combined two memtest programs > and they are both legacy and uefi. memtest86 has more functionality than merely displaying RAM testing on screen. :) -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Manually get memtest 6.01 to work on both Legacy and UEFI boot with Fedora.
Michael D. Setzer II via users composed on 2023-01-16 01:50 (UTC+1000):
> Backed up the /etc/grub.d/20_memtest86+ and replaced it with this...
> # !/bin/sh
> exec tail -n +3 $0
> # This file provides an easy way to add custom menu entries. Simply type the
> # menu entries you want to add after this comment. Be careful not to change
> # the 'exec tail' line above.
> menuentry 'Memtest Legacy' {
> echo 'Loading memtest 6.01 for BIOS BOOT SYSTEM'
> linux /memtest.leg
> }
> menuentry 'Memtest UEFI' {
> echo 'Loading memtest 6.01 for UEFI BOOT SYSTEM'
> linux /memtest.uefi
> }
> Put the memtest files copied from the memtest.org's grub's iso file. leg for
> /boot
> an uefi from /EFI/BOOT.
> both have name memtest, so renamed them to match.
> put them in /boot directory and used grub2-mkconfig to create grub.cfg. Seems
> to work, but one needs to select the correct one. Sure a more complex setup
> could be done. Only have one UEFI machine, so don't know if it would work
> with
> all setups.
> To update my machines created a file.
> 57636 Jan 16 00:24 memtest6.01.xz
> that contains
> 416 Jan 16 00:24 20_memtest86+
> 1071 Jan 16 00:13 Memtest6.01-Readme
> 144344 Dec 30 17:00 memtest.leg
> 144384 Dec 30 17:00 memtest.uefi
> 294 Jan 16 00:23 setupmemtest6.01.sh
I've been using memtest86, not memtest86+, on UEFI using chainload instead of
linux, via the following stanza:
menuentry "memtest86 8.3 EFI" {
search --no-floppy --label --set=root ZM2P01ESP
chainloader /mt83x64.efi
}
# ls -n /boot/efi/*efi
-rwxr-xr-x 1 0 0 1243032 Nov 22 2019 /boot/efi/mt83x64.efi
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
___
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: F37/Xfce no Firefox window
Roger Heflin composed on 2023-01-09 14:34 (UTC-0600): > If you happen to have another firefox running elsewhere on the same machine > under the same username/firefoxprofile it will do that. > It will also do that if there is a firefox running on another screen of > your desktop. Try adding --no-remote to Firefox's startup options, or exporting MOZ_NO_REMOTE=1. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: housekeeping
stan via users composed on 2022-12-30 09:15 (UTC-0700): > On Fri, 30 Dec 2022 11:28:16 +0100 GianPiero Puccioni wrote: >> Yes, I do this so often that I have an alias in my .bashrc >> dus="du --max-depth=1 -h |sort -h" >> it shows the all the subdir sorted and in an easy to read way. > Now it's an alias on my system too. :-) I find ncdu more convenient. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Tip: how to make your own resolv.conf
Tom Horsley composed on 2022-12-18 16:27 (UTC-0500): > On Sun, 18 Dec 2022 21:19:02 + Barry wrote: >> That like my router config. Except I use systemd-networkd not networkmanager. >> Its been stable over lots of fedora releases. > Right up till the release when they decide to eradicate it > because everyone must use NetworkManager :-). Eradicate an easy-to-use component of systemd from systemd's flagship distro? Heresy!!! -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: configuring systemd-networkd (was: Tip: how to make your own resolv.conf)
ToddAndMargo via users composed on 2022-12-17 17:40 (UTC-0800): > Felix Miata wrote: >> All my current Fedora >> installations have been migrated to using systemd-network. They don't need >> "managing". > Details please! Largely copied from: <https://lists.opensuse.org/archives/list/supp...@lists.opensuse.org/message/FVOXJGVY6JKFPHGDFHFTWBAL4F6XDJMM/> Static IPs don't need managing. Disable or uninstall networkmangler and install systemd-network if not aready installed, then enable systemd-networkd: # inxi -S System: Host: big41 Kernel: 6.0.13-300.fc37.x86_64 arch: x86_64 bits: 64 Console: pty pts/0 Distro: Fedora release 37 (Thirty Seven) # systemctl list-unit-files | grep -Ei 'net|solv' dbus-org.freedesktop.network1.service alias - netconsole.service disableddisabled network.service generated - systemd-network-generator.service enabled enabled systemd-networkd-wait-online.servicemasked disabled systemd-networkd-wait-online@.service disableddisabled systemd-networkd.serviceenabled disabled systemd-resolved.servicemasked enabled systemd-networkd.socket enabled disabled network-online.target static - network-pre.target static - network.target static - Configuration is in /etc/systemd/network/.network: # cat /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] Address=192.168.nnn.qqq/24 DNS=192.168.nnn.mmm 1.1.1.1 1.0.0.1 Gateway=192.168.nnn.mmm IPv6AcceptRA=no LinkLocalAddressing=no # inxi -naz Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Biostar Microtech Intl Corp driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d800 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: Make /etc/resolv.conf a regular file and disable whatever is doing your resolv "management". -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: Tip: how to make your own resolv.conf
Tom Horsley composed on 2022-12-17 19:54 (UTC-0500): > On Sat, 17 Dec 2022 16:38:43 -0800 ToddAndMargo wrote: >> 3) create your own resolv.conf file > Not good enough. In the /etc/NetworkManager/NetworkManager.conf > file under the "[main]" section add a line like so: > [main] > dns=none > Otherwise a DHCP lease renewal will replace resolv.conf yet again. Not when you don't have networkmangler installed. All my current Fedora installations have been migrated to using systemd-network. They don't need "managing". -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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 locking (was: need perm. fix for)
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 or
>> removing. When you are ready to allow a kernel to be installed, remove the
>> kernel
>> from the exclude= line. I do that using a one character change in dnf.conf:
>> exclude=" 0kernel* "
>> Even when dnf.conf excludes kernels, kernels may still be added or removed
>> using
>> rpm directly.
> Seems like neat tricks. Thank-you. But I hope you understand when I
> say that I hope I never need to use them!
That one byte difference is like a lock on the kids' toychest that either allows
or prohibits the kids getting toys in or out, preserving status quo, or allowing
changes to occur. I use this one always. I choose a safe time for kernel
installation and removal. The kernel rarely requires changing coincident with
other periodic updates, and it's my computer.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
___
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: need perm. fix for monitor/display problem.
home user composed on 2022-12-15 14:17 (UTC-0700): > No one has yet answered my question: > Is what is currently in RPM Fusion non-free 36 updates everything I need > to really fix the problem for f36? > That should need only a yes or no answer. It may well be that no reader here who might have an authoritative answer and seeing your thread title has read the thread. The thread title does not suggest you have a package management issue, mush less and NVidia drivers issue. It may well be that no reader here who might has an authoritative answer, or is willing to speculate publicly. The facts that others have responded that they are using those drivers satisfactorily, and that others are not reporting trouble with rpmfusion's NVidia drivers currently suggests the answer would be yes if anyone were to post a direct answer. Note that the vast majority of users ATI and AMD GPUs do not require non-FOSS drivers, and for Intel GPU users, no non-FOSS drivers exist, regardless of distro. Only NVidia among major GPU providers has a policy of withholding hardware specifications that FOSS driver writers require for optimal results[1] that indirectly imposes recurring kernel/driver mismatch problems for users of its products. If and when an opportunity to replace your GPU occurs you may wish to consider a different brand. Or, like some people do (e.g. me), use the FOSS drivers without concern that their GPU is capable of performing better. [1] NVidia has recently modified its policy, but it only affects its recent products. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: need perm. fix for monitor/display problem.
home user composed on 2022-12-15 14:03 (UTC-0700): > -bash.10[~]: cat /etc/dnf/dnf.conf > # see `man dnf.conf` for defaults and possible options > > [main] > gpgcheck=True > installonly_limit=3 > clean_requirements_on_remove=True > best=False > skip_if_unavailable=True > -bash.11[~]: > -- > Is your suggestion to edit the "installonly_limit" value? If yes, is my > current setting (3) of that value sufficient? installonly_limit= determines how many kernels dnf will keep installed when it is performing its excess installed kernels removal process. The idea is too allow a larger safety margin for your working 5.19 kernel before its removal would be attempted. 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 or removing. When you are ready to allow a kernel to be installed, remove the kernel from the exclude= line. I do that using a one character change in dnf.conf: exclude=" 0kernel* " Even when dnf.conf excludes kernels, kernels may still be added or removed using rpm directly. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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: where is X? (was: Better way to refresh the Display?)
Patrick O'Callaghan composed on 2022-12-12 16:41 (UTC): > On Mon, 2022-12-12 at 09:33 -0700, stan via users wrote: >> On Mon, 12 Dec 2022 16:08:55 + Patrick O'Callaghan wrote: >>> On Mon, 2022-12-12 at 08:57 -0700, stan via users wrote: >>>> The graphical environment runs on virtual console 1, which is why >>>> you need to use another virtual console to switch away from it, >>>> and 1 to switch back. >>> My DE (KDE/Plasma) runs on Console 2 for some reason. >> So much for my story. :-) Always something new to learn. I think >> they do it just for the kicks of messing with people's heads. :-) > I know it used to be on 1, but changed some time ago. I never really > knew why, or if it was something I did. And the default text console > was on 7 I think, but I may be misremembering that. Where X runs depends on: 1-distro selection 2-DM selection 3-packager selection 4-Xorg vs Wayland? Traditionally, most distros ran the DM on 7, notably including RedHat, Fedora, SUSE & Mandrake/Mandriva/Mageia. Additional X session went to 8, and if another, to 9. The arrangement kept all of 1-6 available for shell logins. Some distros defined a larger or smaller number of available shell logins, so DM and X session 1 would there land on 5 or 6 or 8. Somebody at Gnome and/or systemd decided better to put GDM on 1, thereby reducing expectations, and the utility of many years of mailing list and forum archives. So, AFAIK that's where GDM wants to run, which includes Fedora as their flagship. I haven't had GDM installed anywhere since RedHat 5.2 last century. With some combinations of the three or four deps above, the DM goes on 1, but the first X session goes on 2. KDM's Xorg sessions remain on 7 in Fedora, and that's where TDM remains too. All of my Fedoras with Plasma, except one, remain on KDM. That means I have no Fedoras on LightDM and don't know where it or its Xorg run, but on openSUSE 15.4 and Mint 20, it and Xorg run on 7. The SDDM exception has greeter and Xorg Plasma both running on 2, while 1 hosts the last startup messages and does not accept keyboard input, leaving shell prompts on 3-6. Mageia 9 runs SDDM and Plasma Xorg on Xorg on 1. This schizophrenia makes providing help in various forums more complicated. It used to be normal to ask if Ctrl-Alt-F1 gets a login prompt when X produced a black screen, and Alt-F7 to return to X. That can't be counted on any more. My default away suggestion has migrated to Ctrl-Alt-F3, while instructing a n00bie how to return to X from a shell prompt is not simple. I have yet to find a reason to try opening a Wayland session of anything it supports, so don't know if it makes any difference to the DMs where to run it. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata ___ 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
