plocate?
New install of Fedora 40. It is unclear what program should be run to create plocate.db. -- ___ 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: plocate?
> On 15 May 2024, at 13:18, Geoffrey Leach wrote: > > New install of Fedora 40. It is unclear what program should be run to > create plocate.db. There is a service that does it: $ systemctl --all |grep plocate plocate-updatedb.service loaded inactive dead Update the plocate database plocate-updatedb.timer loaded active waiting Update the plocate database daily Barry > -- > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: plocate?
On Wed, 15 May 2024 05:18:11 -0700 Geoffrey Leach wrote: > New install of Fedora 40. It is unclear what program should be run to > create plocate.db. If you run rpm -q --list plocate among the files it lists is /usr/lib/systemd/system/plocate-updatedb.service If you look in there you'll find ExecStart=/usr/sbin/updatedb -- ___ 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: plocate?
On Wed, 15 May 2024 13:25:04 +0100 Barry Scott wrote: > > On 15 May 2024, at 13:18, Geoffrey Leach > > wrote: > > > > New install of Fedora 40. It is unclear what program should be run > > to create plocate.db. > > There is a service that does it: > > $ systemctl --all |grep plocate > plocate-updatedb.service > > loaded >inactive dead Update the plocate database > plocate-updatedb.timer > > loaded >active waiting Update the plocate database daily > > Barry > Ah! Thanks. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 39/40 hangs on boot after system update
Hi folks, I have an ASUS N550JK laptop running Fedora XFCE. I didn't use it for some months. It was running Fedora 39 XFCE. Today I did an update. After the update it hangs on boot. Because I removed "rhgb quiet" from GRUB_CMDLINE_LINUX I can see messages while the system boots. It seems that it hangs after a message like ... nouveau ... Enabling HDA controller As "nouveau" seems to be a driver for the graphic card and I can also see that the update probably installed a newer kernel 6.8.9-200.fc39.x86_64 I did a reboot with choosing an older kernel 6.6.9-200.fc39.x86_64 from boot menu. With this older kernel the system is able to boot without problems. Then I did an upgrade to Fedora 40 XFCE because I hoped that this could fix the problem. But with Fedora 40 I have the same problem. On starting with the now very new kernel 6.8.9-300.fc40.x86_64 it hangs on boot with the same message ... nouveau ... Enabling HDA controller If I start Fedora 40 with the older kernel 6.6.9-200.fc39.x86_64 from boot menu then the system boots without problems. For providing you some information about the hardware, I did run sudo dmidecode but this gives very very much information. Here is only a short snippet with some basic information: System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: N550JK Version: 1.0 SKU Number: ASUS-NotebookSKU Family: N To find something about the graphic card I did run dmesg | grep nouveau and in the very first line I can see that it seems to be a NVIDIA GM107 (117110a2): [2.426287] nouveau :01:00.0: NVIDIA GM107 (117110a2) [2.442106] nouveau :01:00.0: bios: version 82.07.2a.00.02 [2.526832] nouveau :01:00.0: fb: 2048 MiB DDR3 [2.526889] nouveau :01:00.0: bus: MMIO read of FAULT at 022554 [ PRIVRING ] [3.197385] nouveau :01:00.0: DRM: VRAM: 2048 MiB [3.197387] nouveau :01:00.0: DRM: GART: 1048576 MiB [3.197389] nouveau :01:00.0: DRM: Pointer to TMDS table not found [3.197390] nouveau :01:00.0: DRM: DCB version 4.0 [3.198239] nouveau :01:00.0: DRM: MM: using COPY for buffer copies [3.198466] [drm] Initialized nouveau 1.4.0 20120801 for :01:00.0 on minor 1 [3.198535] nouveau :01:00.0: [drm] No compatible format found [3.198537] nouveau :01:00.0: [drm] Cannot find any crtc or sizes [ 52.988052] nouveau :01:00.0: Enabling HDA controller [ 59.107580] nouveau :01:00.0: Enabling HDA controller [ 59.227433] nouveau :01:00.0: bus: MMIO read of FAULT at 619444 [ PRIVRING ] [ 97.171565] nouveau :01:00.0: Enabling HDA controller [ 97.288155] nouveau :01:00.0: bus: MMIO read of FAULT at 619444 [ PRIVRING ] I do not want to manually choose the kernel each time when I boot the computer. What can I do? Regards, Meikel -- ___ 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 39/40 hangs on boot after system update
On Wed, 15 May 2024 19:05:45 +0200 Meikel wrote: > I do not want to manually choose the kernel each time when I boot the > computer. What can I do? You can check out the nvidia drivers from rpmfusion.org and see if they work better. See https://rpmfusion.org/Howto/NVIDIA -- ___ 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 39/40 hangs on boot after system update
On Wed, May 15, 2024 at 2:06 PM Meikel wrote: > Hi folks, > > I have an ASUS N550JK laptop running Fedora XFCE. I didn't use it for > some months. It was running Fedora 39 XFCE. Today I did an update. After > the update it hangs on boot. Because I removed "rhgb quiet" from > GRUB_CMDLINE_LINUX I can see messages while the system boots. It seems > that it hangs after a message like > > ... nouveau ... Enabling HDA controller > > As "nouveau" seems to be a driver for the graphic card and I can also > see that the update probably installed a newer kernel > 6.8.9-200.fc39.x86_64 I did a reboot with choosing an older kernel > 6.6.9-200.fc39.x86_64 from boot menu. With this older kernel the system > is able to boot without problems. > > Then I did an upgrade to Fedora 40 XFCE because I hoped that this could > fix the problem. But with Fedora 40 I have the same problem. On starting > with the now very new kernel 6.8.9-300.fc40.x86_64 it hangs on boot with > the same message > > ... nouveau ... Enabling HDA controller > > If I start Fedora 40 with the older kernel 6.6.9-200.fc39.x86_64 from > boot menu then the system boots without problems. > > For providing you some information about the hardware, I did run > > sudo dmidecode > > but this gives very very much information. Here is only a short snippet > with some basic information: > > System Information > Manufacturer: ASUSTeK COMPUTER INC. > Product Name: N550JK > Version: 1.0 > SKU Number: ASUS-NotebookSKU > Family: N > > To find something about the graphic card I did run > > dmesg | grep nouveau > > and in the very first line I can see that it seems to be a NVIDIA GM107 > (117110a2): > > [2.426287] nouveau :01:00.0: NVIDIA GM107 (117110a2) > [2.442106] nouveau :01:00.0: bios: version 82.07.2a.00.02 > [2.526832] nouveau :01:00.0: fb: 2048 MiB DDR3 > [2.526889] nouveau :01:00.0: bus: MMIO read of > FAULT at 022554 [ PRIVRING ] > [3.197385] nouveau :01:00.0: DRM: VRAM: 2048 MiB > [3.197387] nouveau :01:00.0: DRM: GART: 1048576 MiB > [3.197389] nouveau :01:00.0: DRM: Pointer to TMDS table not > found > [3.197390] nouveau :01:00.0: DRM: DCB version 4.0 > [3.198239] nouveau :01:00.0: DRM: MM: using COPY for buffer > copies > [3.198466] [drm] Initialized nouveau 1.4.0 20120801 for > :01:00.0 on minor 1 > [3.198535] nouveau :01:00.0: [drm] No compatible format found > [3.198537] nouveau :01:00.0: [drm] Cannot find any crtc or > sizes > [ 52.988052] nouveau :01:00.0: Enabling HDA controller > [ 59.107580] nouveau :01:00.0: Enabling HDA controller > [ 59.227433] nouveau :01:00.0: bus: MMIO read of > FAULT at 619444 [ PRIVRING ] > [ 97.171565] nouveau :01:00.0: Enabling HDA controller > [ 97.288155] nouveau :01:00.0: bus: MMIO read of > FAULT at 619444 [ PRIVRING ] > > I do not want to manually choose the kernel each time when I boot the > computer. What can I do? > Are you using sddm? There are reports that nouveau doesn't work with sddm. -- George N. White III -- ___ 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
boot fails to mount after fc39 upgrade
Hi, I just upgraded my fc38 desktop to fc39 using the regular "dnf upgrade" method, as I've done forever. However, this time boot fails with messages related to failed dependencies and it being unable to mount any partitions other than boot and root. I managed to get networking working so I can copy off some of the config. Here's what's mounted when it fails: Filesystem Size Used Avail Use% Mounted on devtmpfs4.0M 0 4.0M 0% /dev tmpfs32G 0 32G 0% /dev/shm tmpfs13G 2.1M 13G 1% /run efivarfs192K 155K 33K 83% /sys/firmware/efi/efivars /dev/sdc4 1.8T 40G 1.7T 3% / /dev/loop1 6.9M 6.9M 0 100% /var/lib/snapd/snap/dalfox/227 /dev/loop0 104M 104M 0 100% /var/lib/snapd/snap/core/16928 tmpfs32G 0 32G 0% /tmp /dev/sdc2 974M 352M 555M 39% /boot /dev/sdc1 599M 7.5M 592M 2% /boot/efi I can mount my home directory manually, so it's not a problem with the disk. I also tried replacing the UUID in /etc/fstab with the actual device name and rebooting, but that didn't help either. I've also tried booting into the previous fc38 kernel that I know booted properly. I'm used to seeing the ext4 kernel module installed with lsmod, but it seems that's not needed anymore? There's also a message about selinux relabeling - I've also disabled selinux on boot using security=0 so I don't think that's the problem. Here are a few of the "fail" messages from "journalctl -xb 0" May 15 15:31:23 fedora systemd[1]: Mounting home-alex.mount - /home/alex... May 15 15:31:23 fedora mount[928]: mount: /home/alex: mount failed: Invalid argument. May 15 15:31:23 fedora systemd[1]: home-alex.mount: Mount process exited, code=exited, status=1/FAILURE May 15 15:31:23 fedora systemd[1]: Dependency failed for local-fs.target - Local File Systems. May 15 15:31:23 fedora systemd[1]: Dependency failed for selinux-autorelabel-mark.service - Mark the need to relabel after reboot. May 15 15:31:23 fedora systemd[1]: selinux-autorelabel-mark.service: Job selinux-autorelabel-mark.service/start failed with result 'dependency'. May 15 15:31:23 fedora systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. May 15 15:31:23 fedora systemd[1]: local-fs.target: Triggering OnFailure= dependencies. Here's my /etc/fstab. I've commented out all the secondary mount points other than my home directory after they all failed too. # cat /etc/fstab|grep -Ev '^$|#' UUID=39b42604-3f56-4537-b738-b79656379920 / ext3 defaults1 1 UUID=ca677379-15de-4b51-8728-e1c5591874fb /boot ext4 defaults1 2 UUID=E6F8-57A9 /boot/efi vfat umask=0077,shortname=winnt 0 2 UUID=e8add1bc-a807-4547-8177-52768f24bd25 noneswap defaults0 0 UUID=e9be12f8-7d21-4992-9018-d5032124264d /home/alex ext4 defaults,group,user,exec 0 0 -- ___ 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 fails to mount after fc39 upgrade
On 5/15/24 1:24 PM, Alex wrote: Hi, I just upgraded my fc38 desktop to fc39 using the regular "dnf upgrade" method, as I've done forever. However, this time boot fails with messages related to failed dependencies and it being unable to mount any partitions other than boot and root. not "system-upgrade"? There's also a message about selinux relabeling - I've also disabled selinux on boot using security=0 so I don't think that's the problem. Why would you do that? Now you're going to have even more problems. UUID=e9be12f8-7d21-4992-9018-d5032124264d /home/alex ext4 defaults,group,user,exec 0 0 Why do you have a partition for your specific user instead of just /home? -- ___ 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 fails to mount after fc39 upgrade
Hi, > > > I just upgraded my fc38 desktop to fc39 using the regular "dnf upgrade" > > method, as I've done forever. However, this time boot fails with > > messages related to failed dependencies and it being unable to mount any > > partitions other than boot and root. > > not "system-upgrade"? > Sorry, from memory. dnf -y upgrade --refresh && dnf system-upgrade releasever=39 -y dnf system-upgrade reboot > > There's also a message about selinux relabeling - I've also disabled > > selinux on boot using security=0 so I don't think that's the problem. > > Why would you do that? Now you're going to have even more problems. > relabeling is easier than dealing with selinux problems. Most times it's off anyway because of the other apps I use and non-standard paths that always create problems. > UUID=e9be12f8-7d21-4992-9018-d5032124264d /home/alex ext4 > > defaults,group,user,exec 0 0 > > Why do you have a partition for your specific user instead of just /home? > Because it's only my desktop. There are no other users. But I did figure out the problem. I just don't know how to solve it. Apparently fc39 doesn't support "group" and "user" mount options. After removing them from fstab, it boots normally. I don't mount those partitions as a regular user anymore anyway, but ideas on the new usage for these options would be appreciated. Thanks, Alex -- ___ 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
