Re: Upgraded from 35 to 36, and noticed that VirtualBox wasn't working with 6.0.15, but would with 6.0.14?
On 26 Dec 2022 at 8:37, John Mellor wrote: From: John Mellor Date sent: Mon, 26 Dec 2022 08:37:42 -0500 Subject:Re: Upgraded from 35 to 36, and noticed that VirtualBox wasn't working with 6.0.15, but would with 6.0.14? To: users@lists.fedoraproject.org Send reply to: Community support for Fedora users > > > On 2022-12-26 07:29, Michael D. Setzer II via users wrote: > Appears there is kmod-VirtualBox-6.0.14-200.fc36.x86_64-7.0.4-1.fc36.x86_64 > but not a version for 6.0.15 yet? > Gave message the vboxdrv wasn't loaded, but ran the > commands it said, but guess without the package, it > couldn't build the module. > But was able to boot with 6.0.14, and do the testing I > needed. Took a while to figure out the issue, so have to > check for updates. > Just thought I'd mention it. Had no issues with Fedora 35, > so at first thought it might be a Fedora 36 issue. > Virtualbox is a 3rd-party package (in this case, Oracle), so > you would need to wait for an update released by them for > the newer kernel. This being a kmod, there is probably > nothing that the rpm packager (in this case its rpmfusion) > can do until Oracle releases a kernel-matching version. > Just out of curiosity, why are you using virtualbox instead of > a kvm solution frontended by boxes or virtmanager? Have been the maintainer of the G4L project going back to 2004, and have been using Virtualbox to check the iso images after creating new versions for both regular and efi setups. So, it is something that works just fine. Perhaps will take a look at those options. Thanks for reply. > -- > John Mellor ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mi...@guam.net mailto:msetze...@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ ___ 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: monitor/display problem. [SOLVED]
On 11/3/22 3:51 PM, home user wrote: This problem was solved by the "dnf upgrade" that I did on Dec. 14. Details can be viewed in the follow-up thread "need perm. fix for monitor/display problem.", launched on Dec. 14. My thanks to everyone who tried to help. (f36) Good afternoon, A short while ago, I did my weekly patches (dnf upgrade), and then re-booted. Just before that, the workstation display (dual monitor) was fine. After the reboot, only one display works. If I switch the monitor cables, I still get a one-monitor display, but on the other monitor. This leads me to think that the problem is not with the monitors. The display in the one monitor looks a little fuzzy and stretched out horizontally. I also notice at the end of the boot log the following lines: - M [K[ [0;31m*[0;1;31m*[0m] (2 of 3) Job plymouth-quit-wait.ser…tart running (1min 17s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m*[0m] (2 of 3) Job plymouth-quit-wait.ser…tart running (1min 17s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start running (1min 18s / no limit) M [K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 3) Job akmods.service/start running (1min 18s / no limit) M [K[[0;32m OK [0m] Finished [0;1;39makmods.service[0…all new kmods from akmod packages. [K Starting [0;1;39mnvidia-fallback.s… nouveau as nvidia did not load... [[0;32m OK [0m] Finished [0;1;39mnvidia-fallback.s…to nouveau as nvidia did not load. Starting [0;1;39mgdm.service[0m - GNOME Display Manager... [[0;32m OK [0m] Started [0;1;39mgdm.service[0m - GNOME Display Manager. - (first and last lines are for context only) I can't memorize fast enough, but I did notice during the last boot lines very much like (or identical to?) the lines above that mentioned "nvidia". What is the problem? More important, how do I fix it? thanks, Bill. ___ 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.
On 12/17/22 9:46 AM, home user wrote: On 12/17/22 12:54 AM, Samuel Sieb wrote: On 12/16/22 10:33, home user wrote: I shut down nightly. So I do notice the long time. I hear at least 3 long surges of the cooling fans during shutdown. But I don't know of a way of knowing what's really going on (the screens are blank). Since this is the first I've seen or heard anything of this in this list, I assume this is not really a concern. You could try pressing ESC. If the console is still functioning, it will show you what's going on. I'll give that a try, and open a new thread if I think there's a problem. Thank-you, Samuel. To more fully close this, the "dnf update" done on Dec. 14 apparently also solved the long shutdown problem. Shutdowns since then have been taking well under a minute. I'll keep that ESC trick in mind. ___ 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: USB 4 - usb4net - do we have it yet?
On Sun, 25 Dec 2022 08:04:22 +0100 lejeczek via users wrote: > Specs, rfcs & howtos are what we all can sroogle relatively > easily - as I had - still, thank you. > What I was hoping was for someone who had more of hands-on > experience(with the hardware) - if I was not clear > absolutely with my "do we have that" - to tell if this is an > out-of-box, more or less, experience with our Fedora OSes, > as of today. Why not just try the command given above? # modprobe thunderbolt-net or lsmod and look for a usb4 or thunderbolt entry. If you go to /boot and do a grep on the most recent config file like this, grep -i usb4 config[version] does it show CONFIG_USB4 set? If it does, then your kernel has usb4 available. ___ 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: Upgraded from 35 to 36, and noticed that VirtualBox wasn't working with 6.0.15, but would with 6.0.14?
On Mon, Dec 26, 2022 at 7:30 AM Michael D. Setzer II via users wrote: > > Appears there is kmod-VirtualBox-6.0.14-200.fc36.x86_64-7.0.4-1.fc36.x86_64 > but not a version for 6.0.15 yet? > Gave message the vboxdrv wasn't loaded, but ran the commands it said, but > guess without the package, it couldn't build the module. > But was able to boot with 6.0.14, and do the testing I needed. Took a while > to figure out the issue, so have to check for updates. > Just thought I'd mention it. Had no issues with Fedora 35, so at first > thought it might be a Fedora 36 issue. Also see "VirtualBox and Fedora 37" on the mailing list, https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/WB76I7KNYGLDBIB4JJZF5E6EJ7MCHONY/ Jeff ___ 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: Upgraded from 35 to 36, and noticed that VirtualBox wasn't working with 6.0.15, but would with 6.0.14?
On 2022-12-26 07:29, Michael D. Setzer II via users wrote: Appears there is kmod-VirtualBox-6.0.14-200.fc36.x86_64-7.0.4-1.fc36.x86_64 but not a version for 6.0.15 yet? Gave message the vboxdrv wasn't loaded, but ran the commands it said, but guess without the package, it couldn't build the module. But was able to boot with 6.0.14, and do the testing I needed. Took a while to figure out the issue, so have to check for updates. Just thought I'd mention it. Had no issues with Fedora 35, so at first thought it might be a Fedora 36 issue. Virtualbox is a 3rd-party package (in this case, Oracle), so you would need to wait for an update released by them for the newer kernel. This being a kmod, there is probably nothing that the rpm packager (in this case its rpmfusion) can do until Oracle releases a kernel-matching version. Just out of curiosity, why are you using virtualbox instead of a kvm solution frontended by boxes or virtmanager? -- John Mellor ___ 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
Upgraded from 35 to 36, and noticed that VirtualBox wasn't working with 6.0.15, but would with 6.0.14?
Appears there is kmod-VirtualBox-6.0.14-200.fc36.x86_64-7.0.4-1.fc36.x86_64 but not a version for 6.0.15 yet? Gave message the vboxdrv wasn't loaded, but ran the commands it said, but guess without the package, it couldn't build the module. But was able to boot with 6.0.14, and do the testing I needed. Took a while to figure out the issue, so have to check for updates. Just thought I'd mention it. Had no issues with Fedora 35, so at first thought it might be a Fedora 36 issue. ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mi...@guam.net mailto:msetze...@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ ___ 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
