ssh problem with kernel 2.6.32.10-90
Hi all, This morning I updated my Fedora 12 64bit laptop to kernel 2.6.32.10-90. Immediately after I couldn't forward X apps over ssh anymore. Usually, I run X apps on my 3 laptops from my F12 64bit server. The server has been updated to kernel 2.6.32.10-90 at the same time. The 2 other laptops are running fine since they are running Fedora 13 alpha. It is not a major problem since I went back on 2.6.32.9-70 on the F12 laptop and everything is OK. I just thought that posting this might be useful for someone who has a similar problem. If you have any idea on the cause of the problem, feel free to comment. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
fc15 automatically re-boots after fc14 to fc15 upgrade
Gentlemen, I did 'yum update' 'yum install preupgrade' 'preupgrade' And then re-booted system, running KDE on a Dell 1501 Laptop;1gb ram, 120GB HD partitioned Win and Fedora; When I do a normal leave and shutdown all goes normally, then it seems at random time the system will be running again and waiting to select the user. I shut down last knight 10 pmish and my wife awoke me at 335am with the system waiting for the selection of user. The only other thing that seems strange is that the time is incorrect, it says 3:38Pm on the 7th and it is 10:40 pm on the 7th and the time and date were set this morning and were correct before system was shutdown. I don't remember seeing any strange messages on the update. Thank you in advance for your time John A. Ward j...@mbstemps.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: fc15 automatically re-boots after fc14 to fc15 upgrade
Tim, That was my thought but the bios doesn't seem to have any 'wake on alarm' or 'wake on lan' settings. From the messages log there seems to be wifi activity at the top of the log. Is it possible that fc15 is putting the system into a sleep mode, NOT turning the system off? Only pet I have is a 97lb. dog, but he wasn't upstairs when this happened and he doesn't show any interest inkeyboards when he is upstairs. John -Original Message- From: Tim [mailto:ignored_mail...@yahoo.com.au] Sent: Sunday, August 7, 2011 11:41 PM To: 'Community support for Fedora users' Subject: Re: fc15 automatically re-boots after fc14 to fc15 upgrade On Mon, 2011-08-08 at 05:41 +, j...@mbstemps.com wrote:> And then re-booted system, running KDE on a Dell 1501 Laptop;1gb ram,> 120GB HD partitioned Win and Fedora; When I do a normal leave and> shutdown all goes normally, then it seems at random time the system> will be running again and waiting to select the user. I shut down last> knight 10 pmish and my wife awoke me at 335am with the system waiting> for the selection of user. The only other thing that seems strange is> that the time is incorrect, it says 3:38Pm on the 7th and it is 10:40> pm on the 7th and the time and date were set this morning and were> correct before system was shutdown. I don't remember seeing any> strange messages on the update.Does your computer have a BIOS with a wake-up alarm (triggered by theclock, or activity on the ports)? Does the BIOS have an option to fireup the computer after a mains power failure? Do you have a pet cat thatmight walk on the keyboard?-- [tim@localhost ~]$ uname -r2.6.27.25-78.2.56.fc9.i686Don't send private replies to my address, the mailbox is ignored. Iread messages from the public lists. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
System starts by itself
I had posted a prblem with FC15 about an updated system that started by itself for no apparent reason. The solution was, do a new install from scratch, NOT an update. That problem was solved but the system still had a number of small problems, my solution was to do a yum update , things have gotten much better at this point, I still have a problem Rhythembox recongnizing cd contents, when other apps do just fine and printing that crashes, but things are working out. Recommendation to anybody, # 1 don't do an upgrade, put your stuff in a configured /home directory and do a cold install, and do a yum update, immediately! Now I just wish I could get the stupid looking bird in a tree screen gone from the startup user selection screen, does anyone know what procedure is called to start the system? Thank you in advance and this group has generally very interesting comments, I use KDE for Fedora and our RHEL systems and really don't like KDE 4.x, but I am still looking into 'tunning KDE' does anyone know of using KDE 3.x instead. I wish they would have simply made KDE3.x faster, more reliable and possibly made the program functionallity a little better, rather than the big change that was made. John -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
A question about Virtuality
I have just acquired an i3 box with 2*500 GB disks, 4 GB ram and Windows10, essentially 'because it was there' and because my grandson's homework typically assumes an M$ environment. Fact. In the past I would have installed Fedora as a double-boot, but this list has much of talk of virtual boxes. I'd like a few pointers on their practicality on this box and where to start. TIA, John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: A question about Virtuality
On 21/02/18 16:54, Patrick O'Callaghan wrote: On Wed, 2018-02-21 at 15:04 +0000, John Pilkington wrote: I have just acquired an i3 box with 2*500 GB disks, 4 GB ram and Windows10, essentially 'because it was there' and because my grandson's homework typically assumes an M$ environment. Fact. In the past I would have installed Fedora as a double-boot, but this list has much of talk of virtual boxes. I'd like a few pointers on their practicality on this box and where to start. I assume you mean a Windows guest under a Fedora host, rather than the other way round. Probably the easiest way to try it is with VirtualBox as it has a fairly clear GUI install process. Set up a basic Win10 system with 20GB of disk and 2GB of RAM and test it. You'll need a Windows installer image of course (DVD or ISO file). However with 4GB of host memory it's going to be less than ideal. Adding another 4GB stick (and reconfiguring the VM to use 4GB, with whatever additional disk space you need) would probably make a noticeable difference. poc Thank you both for your replies. Yes, I had expected that I would use mainly the Fedora option but would have Win10 available so that I could see it in action; news of WSL came as something of a surprise. I'm not in any great hurry although I guess I ought to fire it up to see that it actually works. I had suspected that more ram would be a good idea, and there are slots unpopulated. John ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: basic issue/question -- renaming in mass a bunch of files
On 02/24/2018 08:38 AM, Patrick O'Callaghan wrote: On Sat, 2018-02-24 at 09:03 -0500, bruce wrote: Hi. Have a bunch of files with the basic naming of: ztcloud_nfs_parseztaa_1__WGS_7500_001__parse.dat ztcloud_nfs_parseztaa_1__WGS_7500_002__parse.dat etc.. I'd like to simply remove the 1st part ztcloud_nfs_parsezt from the files, renaming the files to the rest of the filename.. Thought it should be simple using rename rename 's/ztcloud_nfs_parseztaa/aa/' zt*.dat Read the man page again. The pattern is just a text string, not a regex or sed-type command. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org There appears to be 2 different "rename" programs out in the world. The Fedora rename uses a text string for the pattern, but on my Mint box the pattern is a sed-like substitution. Confusing ? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Yumex Getting Bus Connection/Network Issues
On 25/02/18 20:37, Stephen Morris wrote:
Hi,
Has anybody seen these messages before and know what is causing
them, and hence why yumex is getting them? These are potentially new
since the last system update.
(, DBusException('Rejected send
message, 2 matched rules; type="method_call", sender=":1.107" (uid=1000
pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), 0x7fea6ad483b0>)
(yumex:3908): IBUS-WARNING **: Unable to connect to ibus: Could not
connect: Connection refused
(, DBusException('Rejected send
message, 2 matched rules; type="method_call", sender=":1.107" (uid=1000
pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), 0x7fea6ad4ad88>)
07:31:35 : INFO - Can't detect the network connection state
(, DBusException('Rejected send
message, 2 matched rules; type="method_call", sender=":1.107" (uid=1000
pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), 0x7fea6ad4cfc8>)
regards,
Steve
I use yumex - on my el7 (SL7) box; but I thought you were on f27, where
yumex itself is surely not recommended. My f26 box has a bewildering
set of package managers that seem to conflict in their demands for
access, but aren't dnf-dragora or yumex-dnf more appropriate?
I always see the initial 'can't detect network connection state' on SL7,
but it works. Atop shows high cpu loads for metadata operations after
package download.
John P
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Yumex Getting Bus Connection/Network Issues
On 25/02/18 21:25, Stephen Morris wrote:
On 26/2/18 7:55 am, John Pilkington wrote:
On 25/02/18 20:37, Stephen Morris wrote:
Hi,
Has anybody seen these messages before and know what is causing
them, and hence why yumex is getting them? These are potentially new
since the last system update.
(, DBusException('Rejected
send message, 2 matched rules; type="method_call", sender=":1.107"
(uid=1000 pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), at 0x7fea6ad483b0>)
(yumex:3908): IBUS-WARNING **: Unable to connect to ibus: Could not
connect: Connection refused
(, DBusException('Rejected
send message, 2 matched rules; type="method_call", sender=":1.107"
(uid=1000 pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), at 0x7fea6ad4ad88>)
07:31:35 : INFO - Can't detect the network connection state
(, DBusException('Rejected
send message, 2 matched rules; type="method_call", sender=":1.107"
(uid=1000 pid=3908 comm="/usr/bin/python -tt /usr/bin/yumex "
label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
interface="(unset)" member="GetDevices" error name="(unset)"
requested_reply="0" destination=":1.9" (uid=0 pid=1456
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")',), at 0x7fea6ad4cfc8>)
regards,
Steve
I use yumex - on my el7 (SL7) box; but I thought you were on f27,
where yumex itself is surely not recommended. My f26 box has a
bewildering set of package managers that seem to conflict in their
demands for access, but aren't dnf-dragora or yumex-dnf more appropriate?
I am on F27. I have dnfdragora installed but I don't like its gui
interface, yumex as a gui interface is ten times better than dnfdragora.
Yumex-dnf doesn't exist as a command on my system and a dnf whatprovides
yumex-dnf seems to be indicating it is provided by dnfdragora, but I
can't find it in the filelist in the dnfdragora packages.
In my view the dnf command line interface is hopeless at being able to
find what packages are provided by the various repositories, what they
are and what files they contain, compared to yumex which makes it
simple, so until a gui interface to the package system that is of the
same quality as yumex, that talks directly to dnf rather than through a
translation interface, is produced I've continued to use yumex.
The messages above I have never noticed before, which doesn't
necessarily mean they weren't produced, its just that now the warning
text is being displayed in yellow it now stands out and is hence more
noticeable.
regards,
Steve
I have always found the yumex gui a helpful source of package info too -
but at present on f26 yumex-dnf tells me that 'dnf is locked by another
process. Yum-extender will exit.'
I suspect that process is 'Discover', but Apper, dnf-dragora and
dragora-updater are lurking somewhere too. I don't necessarily want to
disable them completely but I would prefer them to do their routine
updates and then go to sleep.
John
I always see the initial 'can't detect network connection state' on
SL7, but it works. Atop shows high cpu loads for metadata operations
after package download.
John P
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Yumex Getting Bus Connection/Network Issues
On 25/02/18 22:44, Ed Greshko wrote: On 02/26/18 06:17, John Pilkington wrote: I have always found the yumex gui a helpful source of package info too - but at present on f26 yumex-dnf tells me that 'dnf is locked by another process. Yum-extender will exit.' I suspect that process is 'Discover', but Apper, dnf-dragora and dragora-updater are lurking somewhere too. I don't necessarily want to disable them completely but I would prefer them to do their routine updates and then go to sleep. FYI, https://docs.fedoraproject.org/f27/release-notes/desktop/Desktop.html Yes Ed, and thanks. I reported on the KDE list in late Nov that dnf-dragora didn't allow repo selection, which is one of the main reasons for using a gui. Other tools did, and the BZ list for dragora looked overloaded and inactive. I gave up. John ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: The Fedora Wiki page, "Mailing list guidelines" needs to update!
On 02/03/18 00:40, Joe Zeff wrote: On 03/01/2018 04:16 PM, Ed Greshko wrote: Well, that then seems to be inconsistently applied. Maybe not. If any of it's sent through the expected server, you'll see it. I have the original post, listing HyperKitty as user agent. The rpmfusion list has a thread (and a BZ) showing that replies to posts on its HyperKitty are not viewable on that web page, but do arrive by email. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: dnf crash
On 05/03/18 05:31, Eyal Lebedinsky wrote: On 05/03/18 15:27, Ed Greshko wrote: On 03/05/18 12:23, Samuel Sieb wrote: On 03/04/2018 05:55 PM, Eyal Lebedinsky wrote: While it mostly works, this specific command fails: $ dnf provides '*/Droid Sans*' This is consistent, and also happens on a second machine. Both run f27 fully updated. The following does work: $ dnf provides '*/Droid*' But this one crashes: $ dnf provides '*/x y*' I suspect a python problem. Anyone else sees these crashes? I've never tried a query like that before, but I do get a crash as well. The stack trace isn't always the same, but it's usually in a malloc call. It looks like it's possibly a glibc problem. But for some reason abrt isn't detecting the crash which makes it harder to report. I will file a bug. OK, but isn't this searching for a file that has a "space" in it? Can't recall ever seeing one like that as part of the O/S. True. I was trying to understand why mythtv-setup complains: 2018-03-05 16:28:02.602160 E MythFontProperties: Failed to load 'Droid Sans', got 'Droid Sans [MONO]' instead Location: /usr/share/mythtv/themes/MythCenter-wide/base.xml @ 6 Name: 'basesmall' Type: 'fontdef' and just copied/pasted the font name into the search. Still, should not crash, and anyway on linux one *can* have spaces (and other funny chars) in file names, especially when one is asking for trouble :-( I know this thread is about dnf, but I've seen exactly this font problem. mythtv will be looking for /usr/share/mythtv/fonts/DroidSans-Bold.ttf which may be a real file derived from the mythtv distro or may be a link to the system fonts location like /usr/share/fonts/google-droid/DroidSansMono.ttf, which on this, el7, box is from the epel package google-droid-sans-mono-fonts John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: dnf crash
On 05/03/18 08:50, John Pilkington wrote: I know this thread is about dnf, but I've seen exactly this font problem. mythtv will be looking for /usr/share/mythtv/fonts/DroidSans-Bold.ttf which may be a real file derived from the mythtv distro or may be a link to the system fonts location like /usr/share/fonts/google-droid/DroidSansMono.ttf, which on this, el7, box is from the epel package google-droid-sans-mono-fonts John P ... and it's in the mythtv-frontend package. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: video card questions
Hi François Please see the following links that might be useful: https://doc.fedora-fr.org/wiki/Prime https://doc.fedora-fr.org/wiki/Carte_graphique_ATI_-_AMD_Radeon_:_installation_des_pilotes_libres In relation to a proprietary driver that would depend on the card you have. Can you tell me what card you have? If you have an older card then the opensource driver is your only option as I believe these older cards are only supported by the opensource driver. If you have a new card then please see the following: https://support.amd.com/en-us/kb-articles/Pages/AMD-Radeon-GPU-PRO-Linux-Beta-Driver%E2%80%93Release-Notes.aspx Regards John ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Issues trying to lock-down display resolution and overscan
On 04/04/18 17:47, Go Canes wrote: A while back my Intel NUC failed, and I replaced it with a newer one. Since then I have been having a few issues with my display. The first is overscan - the NUC is used as a media PC, and is hooked up via an A/V receiver to a HDTV using HDMI. Unfortunately there doesn't seem to be a way to tell the TV to turn off the overscan. With the older NUC, I used intel_panel_fitter (I think) to adjust the display, and all was well. But that program doesn't work on the new NUC. I can however, use xrandr's transform settings, and this seems to be OK. If anyone has better ideas for accommodating overscan (other than buying a new TV), I would love to hear it! For some time I thought I had set my Panasonic TV to disable overscan (it's in an Advanced Settings screen) but overscanning persisted. Then I realised that it is disabled *only* when 16:9 aspect is also specifically enabled - not just auto selected. That may not apply to your TV, but a bit more hunting might be worthwhile. The second issue is that when I switch the TV away from the NUC, and then eventually back to the NUC, the display is zoomed slightly - just enough so that the KDE bar at the bottom is now off-screen. I can use xrandr to reset the transforms to their default, and then re-apply my desired transforms and it is back to where it should be. But I would like to eliminate this annoying "zoom" altogether if possible. I thought maybe treating it similar to a KVM switch, and forcing the modeline within the xorg config would help, but it doesn't seem to change the behavior at all. The third issue is that sometimes I lose the display more-or-less completely. I switch the receiver to the NUC, and I get a black screen. If I reboot (via a ssh session), I get nothing. To get the display back, I have to poweroff and cold boot. The login screen is fine, but after logging-in, KDE seems to be set for a lower resolution (800x600?) than the TV is using (1080i), and I have go into "System Settings" to correct it - which is difficult when you can't really read the display very well! Any suggestions on these issues would be appreciated! My google searches haven't come up with much help. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: gthumb crash (after enabling vdpau?)
On 10/04/18 06:04, Eyal Lebedinsky wrote: If anyone is interested, this is now on redhat bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1564794 HTH On 03/04/18 11:21, Eyal Lebedinsky wrote: I recently replaced my graphics card (with NVIDIA GT 710). A newer nvidia module was installed kmod-nvidia-340xx-4.15.7-200 -> kmod-nvidia-390.42-1 I also enabled VDPAU which was incorrectly installed until now. I have no idea if this is relevant, but my nvidia GT710 card works well with the latest driver from rpmfusion nvidia-kmod-390.48-1.fc26... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Weird repo problem
On 21/04/18 17:51, Danny Horne via users wrote: Hi all, I have a PC and laptop both running Fedora 27 Workstation and both fully updated, they both have an identical set of repos installed and enabled. The only difference is the PC has Wine installed. For reasons I won't go into I have to reinstall Wine occasionally but I can't find it in either the 'Software' app or via dnf, dnf doesn't show any of the core Wine packages. Trying 'dnf search wine' on the laptop shows Wine and all it's ancillary packages, but nothing is showing on the PC so I can't uninstall or do anything with it. I've tried 'dnf clean all' but that doesn't help. Anyone any clues what's going on? Thanks for looking I'm still on f26; I suppose you know where it is? https://fedora.pkgs.org/27/fedora-x86_64/wine-2.17-1.fc27.x86_64.rpm.html ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: F28 update fails
Read this Antonio: https://fedoramagazine.org/upgrading-fedora-27-fedora-28/ "If you have issues when upgrading because of packages without updates, broken dependencies, or retired packages, add the *‐‐allowerasing* flag when typing the above command. This will allow DNF to remove packages that may be blocking your system upgrade." This flag fixed that error for me. - *Regards,* *John Quirke* On 1 May 2018 at 19:26, Antonio M wrote: > this is the full output > > dnf system-upgrade download --refresh --releasever=28 > Before you continue ensure that your system is fully upgraded by running > "dnf --refresh upgrade". Do you want to continue [y/N]: y > Ultima verifica della scadenza dei metadati: 0:00:00 fa il mar 01 mag 2018 > 20:24:38 CEST. > Errore: > Problema: nss-pem-1.0.3-6.fc27.i686 has inferior architecture > - nss-pem-1.0.3-6.fc27.x86_64 does not belong to a distupgrade repository > - problem with installed package nss-pem-1.0.3-6.fc27.i686 > > > Antonio Montagnani > > Linux Fedora 27(Workstation) > da/from Gmail > > 2018-05-01 19:52 GMT+02:00 Antonio M : > >> When updating by dnf to F28, process fails saying that nss-pem has an >> inferior architecture (I have both i686 and 64 packages). Any idea?? >> > > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Reports of gcc8 vector-validation problems in F28
The MythTV lists have had several reports of problems apparently arising from new (and improved) vector-validation in gcc8. Is there a temporary workaround? It may be a coincidence, but the MythTV bug-tracker is currently reporting a temporary and apparently Fedora-related error: Something has triggered an error on your website. This is the default error page for nginx that is distributed with Fedora. It is located /usr/share/nginx/html/50x.html ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Reports of gcc8 vector-validation problems in F28
On 07/05/18 10:13, Jakub Jelinek wrote: On Mon, May 07, 2018 at 09:51:52AM +0100, John Pilkington wrote: The MythTV lists have had several reports of problems apparently arising from new (and improved) vector-validation in gcc8. Is there a temporary workaround? If you don't provide details (links to the reports, etc.), then it is impossible to tell anything. Jakub As I said, the bug-tracker is currently out of action. Here's the original report: http://lists.mythtv.org/pipermail/mythtv-commits/2018-May/117389.html ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Reports of gcc8 vector-validation problems in F28
On 07/05/18 12:14, Jakub Jelinek wrote: On Mon, May 07, 2018 at 10:40:39AM +0100, John Pilkington wrote: On 07/05/18 10:13, Jakub Jelinek wrote: On Mon, May 07, 2018 at 09:51:52AM +0100, John Pilkington wrote: The MythTV lists have had several reports of problems apparently arising from new (and improved) vector-validation in gcc8. Is there a temporary workaround? If you don't provide details (links to the reports, etc.), then it is impossible to tell anything. Jakub As I said, the bug-tracker is currently out of action. Here's the original report: http://lists.mythtv.org/pipermail/mythtv-commits/2018-May/117389.html If mythtv invoked UB, then you really just want to fix the UB, not look for workarounds. Jakub Agreed. But it seems unlikely that MythTV will be the only programme affected, and people who rely on packaged builds won't immediately have that option. I'm still on F26...and SL7 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Strange behavior with MATE desktop
On Thu, 2018-05-17 at 12:51 -0700, Paolo Galtieri wrote: > I also found an curious issue. The system > this problem is occuring on is a laptop, and I have an external monitor > attached. When I loggen into Gnome Classic the external monitor was an > extension of the laptop display, i.e. I move the mouse off the right > side of the laptop display and it shows up on the external monitor. I > changed the configuration so that the external monitor showed the same > as the laptop display. I also added an icon for gnome-terminal on the > desktop. So far so good. When I logged out of Gnome Classic and logged > back in to MATE the display configuration had changed from what it was > before, now under MATE the external monitor was no longer a clone of the > laptop display as it was previously, and there was now an icon for the > terminal app on the MATE desktop which there was not previously. Dunno about the other problems but those two behaviors are normal. ~/Desktop is a standardized location so both desktop environments will see a .desktop file dropped there. The monitor config is different though. mate-display-properties and Gnome's tool will store information in their own place and in their own way. You will have to configure it in both. And good luck getting one of them to actually save the default the login box will use because then you get into a combinational explosion where each possible display manager might use parts of any desktop environment to get that information from, but being Fedora will probably want to be configured by Gnome 3 unless you have swapped out the default login. signature.asc Description: This is a digitally signed message part ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/B5BECNKULBGZ2ENR7WATXRTRO6HQPXTP/
dmesg spam after f26 -> f27 upgrade
I just upgraded my kde/f26 system to f27 using dnf. It seems to be working well but dmesg has rc rc1: error -5 repeated around 10 times per second. ISTR that when I first saw it it was rc0: Searching hasn't been much help. I use MythTV but not the lirc infra-red remote-control features, and thought it might be lirc-related, so installed lirc-disable-kernel-rc. But the messages continue. They make it impossible to query dmesg for anything else. /etc/rc.d includes various Kxxx files, and rc-local.service is 'static' Suggestions please... John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/ACKJ4PLMOHWG64EQFEHLXQKSTTQ3FAPZ/
Re: dmesg spam after f26 -> f27 upgrade
On 26/05/18 21:04, stan wrote: On Sat, 26 May 2018 13:38:29 +0100 John Pilkington wrote: I just upgraded my kde/f26 system to f27 using dnf. It seems to be working well but dmesg has rc rc1: error -5 repeated around 10 times per second. ISTR that when I first saw it it was rc0: Searching hasn't been much help. I use MythTV but not the lirc infra-red remote-control features, and thought it might be lirc-related, so installed lirc-disable-kernel-rc. But the messages continue. They make it impossible to query dmesg for anything else. /etc/rc.d includes various Kxxx files, and rc-local.service is 'static' Suggestions please... No specific idea, but anything writing that often should be visible in top. Once you know what program it is, you can use rpm -qf to find which package it is. You could also try disabling dmesg logging, and see what complains. Does anything show up in journalctl -r? Thanks to both Samuel and stan for your responses. Yes, there are 2 tuners cards, one PCI and one usb. The spam continued when I unplugged the usb device; I don't want to disable them unless all else has failed. I had looked at atop, and can compare what I see with another very similar 'production' box running the same MythTV version under SL7.5. The spam continues in f27 with MythTV inactive. systemd-journal and rsyslogd are active; rcu_sched shows up intermittently. There's also more akonadi activity which I don't knowingly use. journalctl -r looks as if it ought to be useful but I haven't used it before on either box. Before the 26>27 upgrade it looks as if it was almost exclusively pulseaudio stuff, switching between intel and nvidia for reasons that were never clear; now it looks much denser and almost all kde related. I'll try a reboot and leaving MythTV inactive. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/FSRXPVIA7XPF3N7APCSWZPUF2XWZ7LRB/
Re: dmesg spam after f26 -> f27 upgrade
On 26/05/18 23:53, Roger Heflin wrote: you might try a find /sys -name "rc1*" and see if some piece of hw has that name. It may be some driver trying to manage the ir remote hardware. When I do it on my machine I get this: find /sys -name "rc1*" -ls 33248 0 drwxr-xr-x 5 root root0 May 8 15:50 /sys/devices/pci:00/:00:14.4/:04:06.2/rc/rc1 33252 0 lrwxrwxrwx 1 root root0 May 8 15:50 /sys/class/rc/rc1 -> ../../devices/pci:00/:00:14.4/:04:06.2/rc/rc1 lspci | grep -i 04:06 04:06.0 Multimedia video controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 04:06.1 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05) 04:06.2 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 04:06.4 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05) modinfo cx88 shows it has a parameter disable_ir Thanks for this. It led me to 'lspci | grep -i 07:04' and the Philips Multimedia controller SAA7131/SAA7133/SAA7135 Browsing /sys/class/rc/rc1 showed a uevent with NAME = rc-hauppauge, DRV_NAME = ir_kbd_i2c, DEV_NAME = HVR 1110 (now well into its second decade) and 'sudo modprobe -r ir_kbd_i2c' has stopped the spam. The only parameter listed for ir_kbd_i2c is 'enable hdpvr:bool' I suppose, to survive reboots, I should try creating an /etc/modprobe.d/ir_kbd_i2c.conf - or can I simply add another line to /etc/modprobe.d/dvb.conf, which now specifies the adapter numbers? Or blacklist ir_kbd_i2c? John Yours may be a cx88 I think they are pretty common or some similar card. To find it I did lsmod | grep dvb and then lsmod | grep cx88 and modinfo the various pieces and mine does have a disable for ir. On Sat, May 26, 2018 at 4:48 PM, John Pilkington wrote: On 26/05/18 21:04, stan wrote: On Sat, 26 May 2018 13:38:29 +0100 John Pilkington wrote: I just upgraded my kde/f26 system to f27 using dnf. It seems to be working well but dmesg has rc rc1: error -5 repeated around 10 times per second. ISTR that when I first saw it it was rc0: Searching hasn't been much help. I use MythTV but not the lirc infra-red remote-control features, and thought it might be lirc-related, so installed lirc-disable-kernel-rc. But the messages continue. They make it impossible to query dmesg for anything else. /etc/rc.d includes various Kxxx files, and rc-local.service is 'static' Suggestions please... No specific idea, but anything writing that often should be visible in top. Once you know what program it is, you can use rpm -qf to find which package it is. You could also try disabling dmesg logging, and see what complains. Does anything show up in journalctl -r? Thanks to both Samuel and stan for your responses. Yes, there are 2 tuners cards, one PCI and one usb. The spam continued when I unplugged the usb device; I don't want to disable them unless all else has failed. I had looked at atop, and can compare what I see with another very similar 'production' box running the same MythTV version under SL7.5. The spam continues in f27 with MythTV inactive. systemd-journal and rsyslogd are active; rcu_sched shows up intermittently. There's also more akonadi activity which I don't knowingly use. journalctl -r looks as if it ought to be useful but I haven't used it before on either box. Before the 26>27 upgrade it looks as if it was almost exclusively pulseaudio stuff, switching between intel and nvidia for reasons that were never clear; now it looks much denser and almost all kde related. I'll try a reboot and leaving MythTV inactive. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/V4JDY4RIISFQVDAM3LYMEKHZLP5CRHNT/
Re: [OT] HP EX920
On Fri, 2018-05-25 at 15:40 -0700, Mike Wright wrote: > newegg has a good price on the 512G HP EX920 M.2 ($180US) NVMe SSD > drives this weekend. > > I can find no references to this part and Linux. Everything refers to > Windows (and the problems they're having with it). > > This is supposed to be the latest, greatest, fastest, blabla, etc. > > Anybody familiar with this re: Linux? Assuming it doesn't have any glitches unique to it, Fedora has no problem with an NVMe drive. So long as your BIOS / UEFI firmware supports booting from it you should be good. If you use multiple distros you may find support isn't universal yet. I know PCLinuxOS has problems, they warned about it but I got it to install onto one with some manual fussing. Don't really do a lot of Windows but yea, keep hearing about it being a challenge there unless it is a vendor preload. The PCLinuxOS was on a laptop with a preload of Win10 and it still dual booted ok after the mucking around with UEFI. NVMe is a big break from the old IDE drive world, really expected more breakage. signature.asc Description: This is a digitally signed message part ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/KBAFJSJQFFODPKXSRKPQ7HKT232OBFVC/
Re: F28 - Today's updates messed up writing to USB
On Fri, 2018-06-01 at 11:30 -0700, Samuel Sieb wrote: > You did online updates? This is the reason why offline updates is the > default now, because doing updates without a reboot can cause weird > situations like this. Ok, you maniacs finally did it, you made a Linux suck as hard as Windows. I'm out. signature.asc Description: This is a digitally signed message part ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/EOWXROI5ND7IGXL6LDMTUUE53VDJI6H4/
Re: better subject
On 22/06/18 16:28, Patrick O'Callaghan wrote: On Fri, 2018-06-22 at 08:28 -0500, Rex Dieter wrote: François Patte wrote: Bonjour, such inflammatory subject lines are not welcome, please do better next time. I know you were joking, but that was a greeting rather than a Subject line. poc I was bemused at first, but I think you'll find Rex was not thinking of the French-style greeting but of the original Subject line, which expressed some irritation. John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/T464NVCQXACPZ2WQKZTBAWL6GHZ3EO4E/
Re: Redshift has an issue with geoclue2
On 22/06/18 22:24, ToddAndMargo wrote: Hi All, Fedora 28, x64 redshift-gtk-1.11-8.fc28.x86_64 redshift-1.11-8.fc28.x86_64 geoclue2-libs-2.4.10-2.fc28.x86_64 geoclue2-2.4.10-2.fc28.x86_64 When starting Redshift, I get the following error $ redshift Trying location provider `geoclue2'... Using provider `geoclue2'. Unable to start GeoClue client: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying. Unable to connect to GeoClue. Unable to get location from provider. the pop up says: GDBus.Error" org.freedesktop.DBus.Error.AccessDenied Any word of wisdom? It worked under Fedora 27. -T Not tried, but the FAQ has There is currently no way for Redshift to adjust the color temperature in Wayland. (quotes f25) ? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/GOLNW6HH2PVMX4KGP7SWRPUUESTRKIVI/
Re: off-topic : Adobe reader doesn't show file window
On 30/06/18 06:48, Ed Greshko wrote: On 06/30/18 13:35, Todd Chester wrote: On 06/29/2018 04:54 PM, Ed Greshko wrote: On 06/30/18 06:10, ToddAndMargo wrote: You actually got Adobe reader to work at all. Wow! Even though I use okular, I just installed AdbeRdr9.5.5-1_i486linux_enu.rpm for testing only on an F28 system running fully updated KDE. It installed and ran just fine from the KDE menu as well as from the command line. FWIW, okular does what I need it to do and I really don't like (personal preference) the 80+ i686 packages it needs to install to run. I run WineStaging .686, so I got a ton of i686 packages to support it. I wonder how many more Adobe reader would add? It adds the following to a totally x86_64 system So, bit more than 80. :-) I just looked at okular dependencies on my SL7 system. The only i686 ones I see are kde-runtime and glibc ?? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/RPTRI3KTGIOEFWARQDK35HYBJLASZ5N3/
Re: off-topic : Adobe reader doesn't show file window
On 30/06/18 08:38, Ed Greshko wrote: On 06/30/18 15:21, John Pilkington wrote: On 30/06/18 06:48, Ed Greshko wrote: On 06/30/18 13:35, Todd Chester wrote: On 06/29/2018 04:54 PM, Ed Greshko wrote: On 06/30/18 06:10, ToddAndMargo wrote: You actually got Adobe reader to work at all. Wow! Even though I use okular, I just installed AdbeRdr9.5.5-1_i486linux_enu.rpm for testing only on an F28 system running fully updated KDE. It installed and ran just fine from the KDE menu as well as from the command line. FWIW, okular does what I need it to do and I really don't like (personal preference) the 80+ i686 packages it needs to install to run. I run WineStaging .686, so I got a ton of i686 packages to support it. I wonder how many more Adobe reader would add? It adds the following to a totally x86_64 system So, bit more than 80. :-) I just looked at okular dependencies on my SL7 system. The only i686 ones I see are kde-runtime and glibc ?? What are you questioning? My dis-jointed English? :-) Maybe :-) I had read the long list as being required by okular and wondered if those wide-range packages were somehow responsible. Adobe-reader doesn't appear to be on offer.. Those i686 packages are being added as the result of installing Adobe Reader. Previously, the KDE system had zero i686 packages installed. [egreshko@f28k-b1 ~]$ rpm -qa | grep 686 [egreshko@f28k-b1 ~]$ [egreshko@f28k-b1 ~]$ rpm -qa | grep x86_ | wc 1556 1556 52757 [egreshko@f28k-b1 ~]$ rpm -qa | grep noar | wc 344 344 13560 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/S42EEHFWX5R3QWGXUQXVQALE2XUFOA6Y/ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/U5JXYCZPOTR6DMLW5ALAXOQKDLNNJMA4/
Re: How to read pdf's with animations
On 10/07/18 10:22, Ranjan Maitra wrote: On Tue, 10 Jul 2018 13:40:56 +0800 Ed Greshko wrote: On 07/10/18 12:27, Ranjan Maitra wrote: I have a pdf with animations. However, when I try to read it in evince or okular, in the first case, nothing happens with the animation. In the case of okular, I get a blank gray square where the animation is. How do I read this usign OSS? (I did not want to go get acroread: are there any other options?) Many thanks for any advice! I don't know if the circumstances match exactly. But doing a bit of googling found a suggestion that installing phonon-qt5-vlc (available in rpmfusion) may get things working. They did for at least one person but they didn't specify what type of animation was in the PDF. Sorry, but is this available in F28? I get No match. dnf is fussy. Tried google? Also, don't know if this is good enough, but you may want to consider pdfdetach to extract the embedded files from the pdf. Thanks! I will try that, but I was hoping for a solution inside the pdf reader. Ranjan ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/HUNDZSCDS3L7DEPRTEDJBVXQ22DFCU36/ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/PKFF37GWXWUT7IFCKBFQ5KOJHW5DAJDV/
Re: How to read pdf's with animations
On 10/07/18 17:38, Rick Stevens wrote: On 07/10/2018 02:22 AM, Ranjan Maitra wrote: On Tue, 10 Jul 2018 13:40:56 +0800 Ed Greshko wrote: On 07/10/18 12:27, Ranjan Maitra wrote: I have a pdf with animations. However, when I try to read it in evince or okular, in the first case, nothing happens with the animation. In the case of okular, I get a blank gray square where the animation is. How do I read this usign OSS? (I did not want to go get acroread: are there any other options?) Many thanks for any advice! I don't know if the circumstances match exactly. But doing a bit of googling found a suggestion that installing phonon-qt5-vlc (available in rpmfusion) may get things working. They did for at least one person but they didn't specify what type of animation was in the PDF. Sorry, but is this available in F28? I get No match. It's there: # dnf list "*phonon*" ... Available Packages phonon-backend-vlc.x86_64 0.9.1-4.fc28 rpmfusion-free So it's in the rpmfusion-free repo. I had suggested asking google. I tried 'phonon-qt5-vlc rpm fc28' and the first 5 hits were for phonon-qt5-backend-vlc-0.9.1-4.fc28.x86_64.rpm from rpmfusion. Quick and easy. This is specifically for qt5. The question now is 'does it do the job?' John P Also, don't know if this is good enough, but you may want to consider pdfdetach to extract the embedded files from the pdf. Thanks! I will try that, but I was hoping for a solution inside the pdf reader. Ranjan ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/HUNDZSCDS3L7DEPRTEDJBVXQ22DFCU36/ ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/UGHO2TOMSJ4LPTPEXXZ5JSFZUEWMCZYX/
Re: Update problem: soundtouch (F27)
On 19/07/18 10:15, Frank Elsner wrote: Hello, on my fully updated F27 system todays "dnf update --refresh" gave the error # dnf update --refresh --exclude="kernel*" Last metadata expiration check: 0:00:00 ago on Thu 19 Jul 2018 11:12:27 AM CEST. Dependencies resolved. Problem: package gstreamer1-plugins-bad-free-1.12.4-1.fc27.i686 requires libSoundTouch.so.1, but none of the providers can be installed - cannot install both soundtouch-2.0.0-3.fc27.i686 and soundtouch-1.9.2-6.fc27.i686 - cannot install both soundtouch-1.9.2-6.fc27.i686 and soundtouch-2.0.0-3.fc27.i686 - cannot install the best update candidate for package soundtouch-1.9.2-6.fc27.i686 - cannot install the best update candidate for package gstreamer1-plugins-bad-free-1.12.4-1.fc27.i686 == PackageArch Version Repository Size == Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): soundtouch i686 2.0.0-3.fc27 updates 75 k Transaction Summary == Skip 1 Package How to overcome this problem? Cheers, Frank I see the same with fc27 x86_64. Forcing the upgrade would remove 38 packages. John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/K2YTWNQ5XECNE5P3ZD4EZ3A7LO4HQLBC/
Re: Update problem: soundtouch (F27)
On 19/07/18 11:00, Ed Greshko wrote: On 07/19/18 17:58, John Pilkington wrote: On 19/07/18 10:15, Frank Elsner wrote: Hello, on my fully updated F27 system todays "dnf update --refresh" gave the error # dnf update --refresh --exclude="kernel*" Last metadata expiration check: 0:00:00 ago on Thu 19 Jul 2018 11:12:27 AM CEST. Dependencies resolved. Problem: package gstreamer1-plugins-bad-free-1.12.4-1.fc27.i686 requires libSoundTouch.so.1, but none of the providers can be installed - cannot install both soundtouch-2.0.0-3.fc27.i686 and soundtouch-1.9.2-6.fc27.i686 - cannot install both soundtouch-1.9.2-6.fc27.i686 and soundtouch-2.0.0-3.fc27.i686 - cannot install the best update candidate for package soundtouch-1.9.2-6.fc27.i686 - cannot install the best update candidate for package gstreamer1-plugins-bad-free-1.12.4-1.fc27.i686 == Package Arch Version Repository Size == Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): soundtouch i686 2.0.0-3.fc27 updates 75 k Transaction Summary == Skip 1 Package How to overcome this problem? Cheers, Frank I see the same with fc27 x86_64. Forcing the upgrade would remove 38 packages. That has been fixed... https://bugzilla.redhat.com/show_bug.cgi?id=1601724 Thanks Ed. I had seen the original thread but didn't connect. I think I shall go into wait mode. Maybe some locally built packages would need rebuilds too. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/TYRTNT52RQGI6WEKRQF4VEBODCVEO6FA/
Re: Select packages missing from repo
On 22/07/18 20:56, Samuel Sieb wrote: On 07/22/2018 06:36 AM, Alex wrote: One of the previous writers on this thread cut that part out of my initial post: # dnf search perl-Encode This was not in your initial post. Check your dnf.conf file and see if you have an exclude line in there. In f27 I have recently replaced yumex-dnf by dnfdragora. I'm not yet familiar with its current idiosyncracies, but I notice that perl-Encode is not marked as installed, while other packages are. I tried dnf install perl-Encode, and was told that it was already installed. rpm -qa sees it too. Perhaps suggests all is not quite right. There are several other perl-Encode* packages. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/RJUUIARLBEWL4O43ZIVPWPBPT2OPMTOI/
Re: astropy.io.ascii
On 14/09/18 12:13, Patrick Dupre wrote: Hello, How can I install astropy.io.ascii in fedora? Thank. === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France === As usual, no background info. How about https://dl.fedoraproject.org/pub/fedora/linux/releases/28/Everything/x86_64/os/Packages/p/python3-astropy-3.0.1-1.fc28.x86_64.rpm http://docs.astropy.org/en/stable/install.html John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: astropy.io.ascii
On 14/09/18 16:13, Patrick Dupre wrote: Thank, I am running fedora28. But, by default it run python2 Also under geany, it run pyhton2 even if I put #!/usr/bin/python3 in my file if I run python3 mypy.py Then it run pyhton3 However, I get an error: import matplotlib.pyplot as plt ModuleNotFoundError: No module named 'matplotlib' Do I need to install another matplotlib for python3? I don't know: I haven't used any astropy packages, and suggested the python3 version only because it seemed to tie in better with the installation write-up. There;s a python2 set of packages as well, in an apparently earlier version, which may be easier to set up. I'm stll using f27... https://dl.fedoraproject.org/pub/fedora/linux/releases/28/Everything/x86_64/os/Packages/p/python2-astropy-2.0.5-2.fc28.x86_64.rpm === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France === Sent: Friday, September 14, 2018 at 4:42 PM From: stan To: users@lists.fedoraproject.org Subject: Re: astropy.io.ascii On Fri, 14 Sep 2018 15:21:48 +0200 "Patrick Dupre" wrote: I did dnf install python3-astropy (no problem) and then import astropy but I get import astropy ImportError: No module named astropy The default python up to f28 is python2. If you want to start python3, you have to specifically say python3. When I start the python3 interpreter, and type import astropy, it loads without issue. Do I also need to run pip install astropy --no-deps ? No, the fedora package is all you need to install. In fact, it is not a good practice to mix pip and rpms for the same python package. If you use pip to install python modules, you should investigate the --user option so they won't conflict with rpm. as mentioned in http://docs.astropy.org/en/stable/install.html ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: astropy.io.ascii
On 15/09/18 20:46, Patrick Dupre wrote:
I am sorry. It seems that there is some confusion.
The following lines, can be commented or not. It does not change anything
from mpl_toolkits.mplot3d import Axes3D
import mpl_toolkits.mplot3d.axes3d as axes3d)
I do not use pip. However pip list provides a list of 207 pacakges.
The error is the same in python2 and python3
ax.yaxis.set_scale('log')
AttributeError: 'YAxis' object has no attribute 'set_scale'
I think you should perhaps ask about this in matplotlib circles. This
'closed' bug has similarities:
https://github.com/matplotlib/matplotlib/issues/8027
John P
On Sat, 15 Sep 2018 10:47:43 +0200
"Patrick Dupre" wrote:
However, I am sure that it is linked to fedora, but I get one
error with
ax.zaxis.set_scale('log')
ax.zaxis.set_scale('log')
AttributeError: 'ZAxis' object has no attribute 'set_scale'
(from mpl_toolkits.mplot3d import Axes3D
import mpl_toolkits.mplot3d.axes3d as axes3d)
If this is part of the error it is indicating that axes3d is being
imported twice, as different names. If both exist, it seems they have
a conflict. Because python is case sensitive in names,
Axes3D != axes3d.
I found the following:
https://stackoverflow.com/questions/24442309/attributeerror-zaxis-object-has-no-attribute-set-scale-error-indicates-mat
Some ideas?
The link seems to be indicating that there are two versions of the
library installed, and they are incompatible. Which is what the above
error also seems to be indicating. I'm not familiar with these
routines, so have no idea what is actually going on. I think this is
too complicated to solve second hand. To find the error, the code
that is failing has to be debugged to find how and why it is failing.
And then fixed. Not a trivial exercise.
Another alternative:
Did you by chance install matplotlib using pip, without --user? If you
did, you have conflicting installs from pip and rpm in the system
libraries. The pip install has to be removed. Even if you installed
a duplicate library with pip using --user, depending on your python
path it can conflict with the system libraries if it is before them,
introducing an inconsistency.
If a library exists in fedora and pip, always use the fedora library
so the system libraries remain self consistent. Only use pip for
libraries that aren't packaged in fedora, and always use --user to
install them, so they don't get installed into the system space.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: fc29 beta
On 29/09/18 08:55, Patrick O'Callaghan wrote: On Fri, 2018-09-28 at 15:46 -0700, ToddAndMargo wrote: On 9/28/18 3:13 PM, Patrick O'Callaghan wrote: On Fri, 2018-09-28 at 11:48 -0700, ToddAndMargo wrote: Hi All, I just upgraded one of my machines to FC29 Beta. Looks pretty. Haven't had a chance to play with it yet. -T Here are my upgrade notes; FC 28 -->> FC 29: # rpm --rebuilddb # rpm -Va --nofiles --nodigest if anything is too new, do a # dnf downgrade offender(s) # dnf --enablerepo=* update --refresh # dnf install python3-dnf-plugin-system-upgrade # dnf system-upgrade download --refresh --releasever=29 --allowerasing --best # dnf clean packages <-- optional # dnf system-upgrade reboot Wrong list. The Fedora Test list is the appropriate place. poc Are you sure? I was just giving general information to the community as a whole. I haven't tested anything yet F29 is not released. The guidelines for the User list state that it's for discussion of the released version of Fedora (currently 28 and 27). If you have comments on the future version the Test list is the place to post them. Many people on the Test list do not read the User list and won't see your comments, and cross-posting to multiple lists is frowned on. poc I think this is too restrictive, The procedures quoted are for users of FC28. John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: fc29 beta
On 01/10/18 11:07, Patrick O'Callaghan wrote: On Sun, 2018-09-30 at 17:06 -0700, ToddAndMargo wrote: On 9/29/18 12:55 AM, Patrick O'Callaghan wrote: F29 is not released. The guidelines for the User list state that it's for discussion of the released version of Fedora (currently 28 and 27). If you have comments on the future version the Test list is the place to post them. Many people on the Test list do not read the User list and won't see your comments, and cross-posting to multiple lists is frowned on. Hi Patrick, Now this is a catch 22. All of the commands I showed were Fedora 28 commands, so it was within scope of a released product. The result was an available product in testing but not on the released list. So, I would have been in scope if I had not had mentioned the result. And, if I had posted on the testing group, I would have been told that code for a released version was not in scope. I strongly doubt that. Helping those interested in upgrading to the next version is one of the things the Test list is used for, and anyone doing the upgrade should be on that list as a matter of course. Catch 22 When tips like I posted that are offered in friendship to help other that are constantly helping me cuts across two mail lists, would you please consider a tiny tweak to your guidelines? First of all, they aren't *my* guidelines. I didn't write them. I'm not a moderator or admin for this list (or for the Test list). Your contention that all the commands you recommend are for F28 seems to me irrelevant. The entire purpose of your post is to give instructions on upgrading to F29, which is so far unreleased. There's no Catch-22. All of this is, needless to say, merely my opinion. Cheers poc I've just consulted google, as a new user might; obvious hits told me how to post and how to frame useful questions, but nothing about list guidelines in the sense being used here. The closest approach to what I wanted came up here: - I'm seeing a hyperkitty page. https://lists.fedoraproject.org/archives/ where the descriptions are very brief - and don't rule out this post ;-) John ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Which scanner/copier do you use with Fedora?
OS: Fedora 39 MFP: HP M477 - Got Simple-scan working over network Web Interface is clunky, Printer console interface is too. Software is mostly the typical Windows-Centric, though the HPLIP package seems pretty tidy: https://developers.hp.com/hp-linux-imaging-and-printing/gethplip Firmware updates -may- interfere with third party inks. Time setting at one point required a full system reset - needed for Fax Date time -due to lack of Time service. Paper transport for Automatic Doc Feeder has been very solid. Ink has been reliable after long offlne periods. John Westerdale -- ___ 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: After having updated nvidia drivers, cannot start obs
On 30/03/2024 16:55, Joe Zeff wrote: On 03/30/2024 10:43 AM, francis.montag...@inria.fr wrote: Have you wait for akmods to compile the nvidia kernel modules before rebooting ? Unless things have changed considerably since I used those drivers, the akmod module runs at boot, and checks to see if it needs to do anything. If it does, it rebuilds the kmod; if not, it simply exits. Running it after an update and before reboot is just making sure it gets done and can be skipped if you don't mind the extra few seconds during boot. I never bothered and never had any problems letting them do their jobs as they were designed to do. The rpmfusion nvidia howto says it may take 5 minutes to build. That's a long time to wait with no obvious progress during a reboot. It's much more comfortable to wait until the builds (maybe for several kernels) are complete before triggering the reboot. And ISTR that graphically selecting a restart early can give problems too. systemctl show-jobs can show progress, and then systemctl reboot. John P -- ___ 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.
On 12/04/2024 00:52, home user wrote: On 4/11/24 5:39 PM, Samuel Sieb wrote: On 4/11/24 16:36, home user wrote: On 4/11/24 5:31 PM, Samuel Sieb wrote: On 4/11/24 16:05, home user wrote: /tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40: error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean 'VM_LOCKED'? There has been a kernel change of some sort. The driver needs to be updated to match the kernel. You will not get this driver to build on any newer kernels. -- So realistically, my only practical choice is what Todd suggested, "to just switch to the stuff Nvidia provides directly"? Unless there's a hope of the rpmfusion package getting updated, it looks like it. I'm not really familiar with akmods, but maybe you could just update the source somehow. I'm not a systems administrator. I need someone to step me through the full switch in detail. Reminders: This is a dual boot (Fedora-38 and windows-7) stand-alone work station; it's 11 years old. I have only one old kernel, and no rescue kernel. The graphics card is an nvidia GeForce GTX 660. (anything else?) I have two systems affected by this, and have posted about it on the rpmfusion and fedora-kde lists. I'm having trouble accessing the rpmfusion archive, so maybe a comment here is in order. Both systems have GeForce GT 710 cards. This is low-spec, not for gamers, and I've been using the rpmfusion 470xx drivers for years. I upgraded from F38 to F39 around 2 weeks ago. AIUI we are moving from X11 graphics towards Wayland, which the nvidia driver will not support; but nouveau might. So I've been trying it. On one box it's working acceptably, with VGA nad HDMI screens. Single-boot F39. The other box is dual-boot with Windows 10. I can boot into Fedora only with 'nomodeset', when I get a single screen HDMI 800x600 which seems fine but limited. I can run MythTV frontend with --geometry 720x504+40+20, and mythleanfront on an Android tv. The biggest worry is getting past a frozen boot, so I don't want to make any recommendations. I have removed all the *nvidia* rpms except nvidia-gpu-firmware, and installed nouveau-firmware from the rpmfusion-nonfree-tainted repo. Maybe the rpmfusion team will make the old system work soon, or maybe the even-older but just-updated 340xx driver would work. I'll try living with what I have for now. HTH John P -- ___ 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.
On 12/04/2024 12:58, John Pilkington wrote: On 12/04/2024 00:52, home user wrote: On 4/11/24 5:39 PM, Samuel Sieb wrote: On 4/11/24 16:36, home user wrote: On 4/11/24 5:31 PM, Samuel Sieb wrote: On 4/11/24 16:05, home user wrote: /tmp/akmodsbuild.2VNb1GB1/BUILD/nvidia-470xx-kmod-470.223.02/_kmod_build_6.8.4-100.fc38.x86_64/nvidia-drm/nvidia-drm-drv.c:748:40: error: 'DRM_UNLOCKED' undeclared here (not in a function); did you mean 'VM_LOCKED'? There has been a kernel change of some sort. The driver needs to be updated to match the kernel. You will not get this driver to build on any newer kernels. -- So realistically, my only practical choice is what Todd suggested, "to just switch to the stuff Nvidia provides directly"? Unless there's a hope of the rpmfusion package getting updated, it looks like it. I'm not really familiar with akmods, but maybe you could just update the source somehow. I'm not a systems administrator. I need someone to step me through the full switch in detail. Reminders: This is a dual boot (Fedora-38 and windows-7) stand-alone work station; it's 11 years old. I have only one old kernel, and no rescue kernel. The graphics card is an nvidia GeForce GTX 660. (anything else?) I have two systems affected by this, and have posted about it on the rpmfusion and fedora-kde lists. I'm having trouble accessing the rpmfusion archive, so maybe a comment here is in order. Both systems have GeForce GT 710 cards. This is low-spec, not for gamers, and I've been using the rpmfusion 470xx drivers for years. I upgraded from F38 to F39 around 2 weeks ago. AIUI we are moving from X11 graphics towards Wayland, which the nvidia driver will not support; but nouveau might. So I've been trying it. On one box it's working acceptably, with VGA nad HDMI screens. Single-boot F39. The other box is dual-boot with Windows 10. I can boot into Fedora only with 'nomodeset', when I get a single screen HDMI 800x600 which seems fine but limited. I can run MythTV frontend with --geometry 720x504+40+20 The biggest worry is getting past a frozen boot, so I don't want to make any recommendations. I have removed all the *nvidia* rpms except nvidia-gpu-firmware, and installed nouveau-firmware from the rpmfusion-nonfree-tainted repo. Maybe the rpmfusion team will make the old system work soon, or maybe the even-older but just-updated 340xx driver would work. I'll try living with what I have for now. After kernel and firmware updates today the behaviour of both systems, using nouveau, seems essentially unchanged from the report above. kernel now is 6.8.5-201.fc39.x86-64 If the 'nomodeset' is edited out in grub, a reboot of the dual-boot box still hangs almost immediately. I've removed the claim that mythleanfront works with mythbackend on the dual-boot box. I think that was mistaken, and a local permissions issue. HTH John P -- ___ 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.
On 14/04/2024 16:22, Michael D. Setzer II via users wrote: On 15 Apr 2024 at 0:29, Michael D. Setzer II via user wrote: Just as an additional note. I have an older Acer notebook that has an NVIDIA GT 650M that had been working fine with the rpmfusion driver. Have BOINC using its GPU for a project. After recent kernel upgrade, I noticed it was no longer working. Tried reinstalling the rpm and it fails to build, so goes to fallback of noveum? driver. Went to NVIDIA site, and downloaded what I believe was the correct driver for the GT 650M, but it also fails to build? Currently 17 timezones away from machine. In GMT -0700, while machine is in GMT +1000, so accessing remotely via TurboVNC. So, not sure if this is a kernel issue, or the driver issue, but seems neither rpmfusiong or nvidia's driver will work any longer? I've got other machines that have new nvidia cards, and they are working with a different rpmfusing nvidia rpm. Perhaps I'm missing something. Thanks. Otherwise machines fully updated with no issues. Was looking around, and found this info in /var/cache/akmods/nvidia-470xx Appears that it was working with 6.7.11 kernel but is now failing with 6.8.x 26183873 Apr 2 12:52 kmod-nvidia-470xx-6.7.11-200.fc39.x86_64-470.223.02-2.fc39.x86_ 64.rpm 14360178 Apr 2 12:52 470.223.02-2-for-6.7.11-200.fc39.x86_64.log 614649 Apr 10 15:32 470.223.02-2-for-6.8.4-200.fc39.x86_64.failed.log 616385 Apr 15 01:02 470.223.02-2-for-6.8.5-201.fc39.x86_64.failed.log Thanks. I've dropped the initial posts in this thread.. When I posted on the rpmfusion list, on 9 April, Sergio's response was: a fix for nvidia 340x was posted today , for Fedora 40 we don't have these kmod nvidias because it fail to build with gcc14 . Please someone which have these graphics try fix it ASAP Thank you So one difficulty is probably a lack of rpmfusion devs with the affected hardware... John P -- ___ 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.
On 15/04/2024 20:02, home user wrote: On 4/11/24 11:19 AM, home user wrote: After a few days of being seriously side-tracked, I can try to get back to this. Those who explained the kernel numbering: thank-you. (f-38; stand-alone work station; nvidia graphics card; dual monitor; kmod 4xx driver) I just finished doing a "dnf upgrade" as a prerequisite step to upgrading from f-38 to f-39. There were no hints of any problems. The kernel and the graphics driver were replaced during this "dnf upgrade". The akmods did finish before I rebooted. The shutdown took 5 minutes because it ran akmods (a second time?!). During the boot-up, there was a message that it was failing back to nouveau. The display is not working properly; only one monitor is being used and everything is oversized in the display. I am not comfortable proceeding with the f-38 to f-39 upgrade with the work station in this condition. Important: I have only one old kernel. I have no rescue kernel. How do I get this workstation working properly? A. nvidia's proprietary drivers. There's 1. (Thomas) I finally just nuked all the RPMFusion packages and downloaded the drivers directly from https://www.nvidia.com/download/index.aspx and ran the installer from there. It works fine again. (Todd) I can tell you that building the 2 or 3 nvidia 470xx packages works well for the later 6.7 and current 6.8 kernels. and there's 2. (John) AIUI we are moving from X11 graphics towards Wayland, which the nvidia driver will not support... (Michael) So, not sure if this is a kernel issue, or the driver issue, but seems neither rpmfusiong or nvidia's driver will work any longer? These seem to me to be inconsistent with each other. What am I missing? B. nvidia and Fedora. From posts in this thread, I gather that 1. nvidia users can no longer use Fedora, and 2. Fedora users can no longer use nvidia. Is this correct? I don't think your summaries are correct. But although technical fixes may exist for the immediate problems the situation at rpmfusion looks more difficult. See this Bugzilla and in particular Comment 5. https://bugzilla.rpmfusion.org/show_bug.cgi?id=6904 John P -- ___ 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: The best way to still use Fedora + Xorg + Gnome ... even after version 40
With X being a completely unmaintainable mess, all new and bugfix development stopped about 2 years ago. Most disturbing is that for the last 2 years there have been essentially no security fixes as a result. A couple of distros have done some critical bugfixes to try to keep the dead horse alive, but its been on life support for a long time now. Every distro announced a long time ago that X support would end, and to move on and redesign for Wayland. Some of the original X developers started Wayland as X reimagined 45 year later for the 21st century needs. However, given that absolutely everyone today has compute power on their desk and everyone has a gpu for things like compositing instead of what was available back when X was designed, they made some major architectural decisions that will affect some people, like dropping remote app windows in favour of remote desktops. As far as I'm aware there are no distros with plans to try to keep on building X. Its dead. Today, Wayland can do most of the things that it was envisioned to do, with Fedora probably being the one with the most up-to-date implementation. Good luck in your search for an up-to-date distro knowingly shipping big security holes today. Maybe you can keep using an old distro release and airgap your entire inboard network and use X without interacting with the rest of the net as a way out of your dilemma. On 2024-04-17 11:37 a.m., Patrick O'Callaghan wrote: On Wed, 2024-04-17 at 14:00 +0200, Dario Lesca wrote: Ok my notebook I work with Fedora from Core 1 with Gnome on Xorg-x11 I would like to continue to work with Gnome on Xorg-x11 ... even after version 40 What is the best way to do that without change distro? As I understand it, X11 will still be installable, though I don't know how long that will last. poc -- ___ 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
Fedora 40 - KeePass fails to run
Hi, Just an FYI that KeePass is failing to run on my recently upgraded Fedora 40 machine. I'm not sure of the correct place to report the issue. [image: image.png] John -- ___ 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
ick driver: dvb_usb_dvbsky type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-2:2 chip-ID: 0572:c688 class-ID: Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.2.6 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 3048x1050 s-dpi: 96 s-size: 804x277mm (31.65x10.91") s-diag: 850mm (33.48") Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: right model: Sony TV built: 2020 res: 1368x768 hz: 60 dpi: 49 gamma: 1.2 size: 708x398mm (27.87x15.67") diag: 1836mm (72.3") ratio: 16:9 modes: max: 1360x768 min: 640x480 Monitor-2: VGA-1 pos: primary,left model: Dell 2009W serial: built: 2009 res: 1680x1050 hz: 60 dpi: 99 gamma: 1.2 size: 433x271mm (17.05x10.67") diag: 511mm (20.1") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11: drv: nouveau inactive: wayland API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 23.3.6 glx-v: 1.4 direct-render: yes renderer: NV106 device-ID: 10de:128b memory: 986.3 MiB unified: no API: Vulkan v: 1.3.275 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM 17.0.6 128 bits) driver: N/A device-ID: 10005: surfaces: xcb,xlib 2024041140 BST Dual-boot with Windows 10 #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 resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet nomodeset Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.12 info: frameworks v: 5.115.0 wm: kwin_wayland with: krunner vt: 2 dm: SDDM Distro: Fedora Linux 39 (Thirty Nine) 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 alternate: nvidia gpu: nvidia display-ID: 0 Monitor-1: Unknown-1 res: 800x600 size: N/A modes: N/A API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm: drv: kms_swrast surfaceless: drv: swrast wayland: drv: swrast x11: drv: swrast inactive: device-1 API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 23.3.6 glx-v: 1.4 direct-render: yes renderer: llvmpipe (LLVM 17.0.6 256 bits) device-ID: : memory: 15.21 GiB unified: yes display-ID: :0.0 API: Vulkan v: 1.3.275 layers: 2 device: 0 type: discrete-gpu name: NVIDIA GeForce GT 710 driver: N/A device-ID: 10de:128b surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM 17.0.6 256 bits) driver: N/A device-ID: 10005: surfaces: xcb,xlib,wayland }}} John P -- ___ 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 - KeePass fails to run
Thanks. I just looked at the other versions to see how they differ. They are forks off the original. I prefer to stay with the main one. I did open a bug and they traced it to "Confirmed this is caused by zlib-ng migration.". I am not sure when it will get fixed. It is an inconvenience to me as all of my passwords are in the application. But my machine is dual boot. So I was able to copy my vault over to windows and retrieve my passwords there. John On Sun, Apr 28, 2024 at 9:26 PM Lester Petrie wrote: > > > On 4/28/2024 5:52 PM, Go Canes wrote: > > On Thu, Apr 25, 2024 at 10:12 AM John List > <mailto:jlists...@gmail.com>> wrote: > > > Just an FYI that KeePass is failing to run on my recently upgraded > > Fedora 40 machine. I'm not sure of the correct place to report the > issue. > > > > There are several keepass* alternatives: > > keepassx.x86_64 > > keepassxc.x86_64 > > keepass.x86_64 > > keepassx0.x86_64 > > > > Perhaps one of them will work better? FWIW I use keepassxc, but I am on > > f38 (and now upgrading to f39). > > > > I have upgraded to F40, and keepassxc.x86_64 is working fine for me. > > -- > Lester Petrie > -- > ___ > 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
System upgrades. Where is the / filesystem?
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. John P -- ___ 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?
On 01/05/2024 00:54, Gordon Messmer wrote: On 2024-04-30 10:58 AM, John Pilkington wrote: (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. Have you made snapshots of your system volume, or installed any applications that might create snapshots (something like timeshift or snapper)? If your filesystem has snapshots, deleting files will not free up space until you also remove the snapshots that contain those files. Thank you for this, and to Felix for his instructions too. 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. I decided to try fixing the issues on the already upgraded f40 box first... Thanks again, John -- ___ 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?
On 01/05/2024 15:51, Felix Miata wrote: 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. Thank you for this, and for earlier posts that I found elsewhere. The system is now updated to f40 and seems to be running well. I didn't have to use rpm installs from the cache in /var/lib/dnf/system-update. I think the effective change was to add "exclude kernel* linux-firmware* java* libreoffice* " to /etc/dnf/dnf.conf, before repeating everything from the preliminary "sudo dnf upgrade--refresh" and applying "--allowerasing --skip-broken" in the download. I suppose a "sudo dnf clean all" had helped too: 88 files removed. After the download KDiskFree reported 3.9 GB free in /, and dnf said that was the total package size. "df / " said 4093160 blocks. After the reboot I removed the excludes, ran dnf upgrade again, and installed locally built MythTV rpms. That's an account of what I did. I'm afraid it comes with no guarantees. John P -- ___ 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 increase size of /boot partition
On 03/05/2024 18:52, richard emberson wrote: Just today I upgraded from 39 to 40 but there was an issue: dnf told me I needed some 800k more space in my /boot partition to proceed. I had two kernels in /boot so I dnf removed those associated with the older of the two kernels. I then successfully upgraded. I fear the next time I do a dnf update which includes a new kernel I will be told, again, that there is not enough space in my /boot partition. So, how can I increase the size of the /boot partition? Many partitions, like /tmp, are bigger than they need to be. Here is what how the /sda disk is organized. $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 223.6G 0 disk ├─sda1 8:1 0 250M 0 part /boot ├─sda2 8:2 0 105.5G 0 part │ └─luks-a2ebb2b0-527d-47f3-83ef-e5908805f31d │ 253:3 0 105.5G 0 crypt /ssd ├─sda3 8:3 0 97.7G 0 part │ └─luks-35719a97-5898-4420-9a56-1576ffdc6db3 │ 253:1 0 97.7G 0 crypt / ├─sda4 8:4 0 1K 0 part ├─sda5 8:5 0 9.8G 0 part │ └─luks-5ee2ed8e-4bdf-43e1-adb0-34a70610a77f │ 253:2 0 9.8G 0 crypt /tmp └─sda6 8:6 0 9.8G 0 part └─luks-03c06df8-f9b9-4f0d-847e-79a7ed527888 253:0 0 9.8G 0 crypt [SWAP] $ df -h Filesystem Size Used Avail Use% Mounted on /dev/dm-1 96G 22G 70G 25% / devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 16G 0 16G 0% /dev/shm tmpfs 6.3G 1.8M 6.3G 1% /run /dev/sda1 237M 179M 42M 82% /boot /dev/dm-2 9.5G 260K 9.0G 1% /tmp /dev/dm-3 104G 193M 99G 1% /ssd /dev/dm-4 1.9T 1.2T 630G 66% /home /dev/dm-5 1.7T 903G 736G 56% /data1 /dev/dm-6 20G 12G 6.9G 63% /var tmpfs 3.2G 152K 3.2G 1% /run/user/1000 Thanks for any help give. I realize one way is to backup /home and then reinstall Fedora but 1) that seems like a lot of work and 2) it would mean that the machine in question would then have to use Wayland rather than Xorg. Richard This isn't a direct reply to your question: IIUC you need to run a 'live' image to do that. But I installed f40 a few days ago, and today "dnf upgrade" installed kernel-6.8.8 but *not* vmlinuz-6.8.8, so booting failed. My /boot partition is 450 GB, and I now have two bootable f40 kernels and a recent rescue kernel. There's no room for another. You probably don't have a "recovery" option. I now have "installonly_limit=2" in /etc/dnf/dnf.conf, but a new "dnf upgrade" after that said there was "nothing to do". What did work was ( while running 6.8.7): sudo dnf remove kernel-core-6.8.8 sudo dnf upgrade and then when "systemctl list-jobs" was clear, "sudo systemctl reboot" I, too, would prefer to have a bigger /boot, but this info might help. John P -- ___ 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 40 and nouveau
Both my old HP boxes have F40 up-to-date. Both are connected to an HDMI
tv and vga monitor, but the one dual-booted with Windows has a fixed
800x600 screen size that appears only on the HDMI screen but lacks HDMI
audio. I reinstalled the (Fedora provided) nouveau driver on both boxes
before these reboots. The boot lines shown give rrunning systems. Most
variants that I have tried freeze sooner or later.
I still have no idea of how to pre-specify the devices that I want to use.
John P
{{{
The same packages are on both boxes:
[john@HPFed ~]$
[john@HPFed ~]$ rpm -qa | grep -i nouveau
nouveau-firmware-340.32-12.fc40.noarch
xorg-x11-drv-nouveau-1.0.17-7.fc40.x86_64
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$ rpm -qa | grep -i nvidia
nvidia-gpu-firmware-20240410-1.fc40.noarch
[john@HPFed ~]$
===
This box works acceptably for me, but may not provide hardware
acceleration or deinterlace.
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$ sudo dmesg | grep -i nouveau
[sudo] password for john:
[0.00] Command line:
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora-root ro rd.driver.blacklist=nvidia
modprobe.blacklist=nvidia nouveau-drm.modeset=1 rd.lvm.lv=fedora/swap
rd.lvm.lv=fedora/root rhgb quiet
[0.080150] Kernel command line:
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora-root ro rd.driver.blacklist=nvidia
modprobe.blacklist=nvidia nouveau-drm.modeset=1 rd.lvm.lv=fedora/swap
rd.lvm.lv=fedora/root rhgb quiet
[6.251690] nouveau :01:00.0: vgaarb: deactivate vga console
[6.259071] nouveau :01:00.0: NVIDIA GK208B (b060b0b1)
[6.471713] nouveau :01:00.0: bios: version 80.28.a6.00.35
[6.478430] nouveau :01:00.0: fb: 1024 MiB DDR3
[7.506681] nouveau :01:00.0: DRM: VRAM: 1024 MiB
[7.506687] nouveau :01:00.0: DRM: GART: 1048576 MiB
[7.506691] nouveau :01:00.0: DRM: TMDS table version 2.0
[7.509397] nouveau :01:00.0: DRM: MM: using COPY for buffer copies
[7.519874] [drm] Initialized nouveau 1.4.0 20120801 for :01:00.0
on minor 0
[7.717489] fbcon: nouveaudrmfb (fb0) is primary device
[7.864230] nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame
buffer device
[ 26.289099] snd_hda_intel :01:00.1: bound :01:00.0 (ops
nv50_audio_component_bind_ops [nouveau])
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$
[john@HPFed ~]$ sudo dmesg | grep -i nvidia
[0.00] Command line:
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora-root ro rd.driver.blacklist=nvidia
modprobe.blacklist=nvidia nouveau-drm.modeset=1 rd.lvm.lv=fedora/swap
rd.lvm.lv=fedora/root rhgb quiet
[0.080150] Kernel command line:
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora-root ro rd.driver.blacklist=nvidia
modprobe.blacklist=nvidia nouveau-drm.modeset=1 rd.lvm.lv=fedora/swap
rd.lvm.lv=fedora/root rhgb quiet
[6.259071] nouveau :01:00.0: NVIDIA GK208B (b060b0b1)
[ 26.293617] input: HDA NVidia HDMI/DP,pcm=3 as
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11
[ 26.293770] input: HDA NVidia HDMI/DP,pcm=7 as
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input12
[ 26.293969] input: HDA NVidia HDMI/DP,pcm=8 as
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input13
[ 26.294042] input: HDA NVidia HDMI/DP,pcm=9 as
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14
[john@HPFed ~]$
===
Dual-boot giving HDMI 800x600 window only and no HDMI audio.
john@FedWin4c1:~$
john@FedWin4c1:~$
john@FedWin4c1:~$ sudo dmesg | grep -i nouveau
john@FedWin4c1:~$
john@FedWin4c1:~$
john@FedWin4c1:~$
john@FedWin4c1:~$ sudo dmesg | grep -i nvidia
[0.00] Command line:
BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
[0.00] Kernel command line:
BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
[ 20.370975] input: HDA NVidia HDMI/DP,pcm=3 as
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input9
[ 20.371114] input: HDA NVidia HDMI/DP,pcm=7 as
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10
[ 20.371229] input: HDA NVidia HDMI/DP,pcm=8 as
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input11
[ 20.371315] input: HDA
Re: Fedora 40 and nouveau
On 07/05/2024 05:12, Felix Miata wrote: John Pilkington composed on 2024-05-06 12:32 (UTC+0100): Both my old HP boxes have F40 up-to-date. Both are connected to an HDMI tv and vga monitor, but the one dual-booted with Windows has a fixed 800x600 screen size that appears only on the HDMI screen but lacks HDMI audio. I reinstalled the (Fedora provided) nouveau driver on both boxes before these reboots. The boot lines shown give running systems. Most variants that I have tried freeze sooner or later. I still have no idea of how to pre-specify the devices that I want to use. It's not clear to me whether you're trying to solve a video problem, an audio problem, or both, or whether the answers apply to both hosts, or just one. Good luck with your audio. Getting Linux audio to me is inexplicable hocus pocus. Thank you for the various diagnostic quotes from your system. My main reason for posting was to provide info about settings that worked for me, because I find testing of systems that fail to boot frustrating. I have removed xorg-x11-drv-nouveau from the dual-boot box, and applied today's upgrades. It still seems to need "nomodeset" to boot to a working system, still 800x600 and only on the HDMI screen, with line-out audio. Specifying "modesetting" starts well, with both screens active in text mode; but then it jumps to graphical memory images, and shortly after the cursor appears it, and then the whole system, freezes. Continuing John -- ___ 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
On 07/05/2024 14:07, Andre Robatino wrote: I have a very old computer with GeForce 6150SE nForce 430 integrated video. I had video trouble as well, had been using just "nomodeset" to work around it, but got 1024x768 pincushioned video on my old CRT with 1280x1024 as the maximum resolution. (This is just a backup machine now, that I normally just ssh into to do updates, so I could tolerate it.) The machine is dual boot with Windows 10 where I get normal 1280x1024 video. Probably Windows has a much bigger hardware database and is better able to work around quirky hardware. Anyway, with F40 it wouldn't boot to graphical at all, but I eventually found that adding "nomodeset vga=795" fixes the video and lets it come up in 1280x1024, without pincushioning, like in Windows. (I'm not able to change the video resolution as an ordinary user, in Settings, but I don't care since the resolution is optimal.) Both options are necessary. The video mode numbers are at https://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers . So try "nomodeset vga=XXX" where XXX is the desired mode. Thank you for that - and ISTR that you had posted something similar earlier. I have tried it, and variations on it, but any boot-to-completion still gives me 800x600. I just tried playback of 1920x1080, and it was fine, but ffmpeg used 4 cores all at 90%. Letting the TV do the heavy lifting is better. John -- ___ 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: What is Castor ? Att.Jonathan Billings.
On 08/05/2024 10:18, Tim via users wrote: On Tue, 2024-05-07 at 17:36 -0400, Jonathan Billings wrote: Some home router/gateways will remember the hostname a system used as part of their network, and when handing out the same IP to a new host, re-uses the saved hostname. I've yet to come across a home gateway that handles name resolution, they just dole out numerical IPs from their DHCP server, it also seems to be a bit of a rarity for a client to accept a hostname that a DHCP server does supply (if it does). DHCP clients can also request the DHCP server lets them use their own hostname, and that's often ignored, too. More often than not, a client would to a reverse DNS look-up on its assigned IP to see what domain/hostname is associated with that IP (which could be a DNS query, but first it looks in the hosts file). Not everyone has a DNS server, or a configurable one, nor adjusts their hosts file (often fighting with Network Mangler over it). So: Set your preferred hostname either in GNOME Settings (or whatever DE’s settings) or with hostnamectl. Which stores a setting somewhere naming itself consistently, whatever IP address you get given. This can get messy if you get assigned different numerical IPs from time to time. It occurs to me that my new 'dual-boot' problems with F40 KDE might be related to this, but I'm not clear how I could test it. I've posted both here and on the kde list. I have two screen-devices, HDMI tv and vga monitor. By default booting is to Windows, but 'escape' early on goes to an HP-provided boot-selection sequence and grub. Choosing "modesetting" starts booting with both screens active, but freezes shortly after a cursor appears. "nomodeset" gives a usable system, but with the vga screen never active and final HDMI resolution fixed at 800x600. Could this perhaps be a conflict of hostnames set at power-on and by Fedora? John P -- ___ 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: What is Castor ? Att.Jonathan Billings.
On 08/05/2024 17:54, Roger Heflin wrote:
On Wed, May 8, 2024 at 5:09 AM John Pilkington wrote:
On 08/05/2024 10:18, Tim via users wrote:
On Tue, 2024-05-07 at 17:36 -0400, Jonathan Billings wrote:
Some home router/gateways will remember the hostname a system used as
part of their network, and when handing out the same IP to a new
host, re-uses the saved hostname.
I've yet to come across a home gateway that handles name resolution,
they just dole out numerical IPs from their DHCP server, it also seems
to be a bit of a rarity for a client to accept a hostname that a DHCP
server does supply (if it does). DHCP clients can also request the
DHCP server lets them use their own hostname, and that's often ignored,
too.
More often than not, a client would to a reverse DNS look-up on its
assigned IP to see what domain/hostname is associated with that IP
(which could be a DNS query, but first it looks in the hosts file).
Not everyone has a DNS server, or a configurable one, nor adjusts their
hosts file (often fighting with Network Mangler over it). So:
Set your preferred hostname either in GNOME Settings (or whatever
DE’s settings) or with hostnamectl.
Which stores a setting somewhere naming itself consistently, whatever
IP address you get given.
This can get messy if you get assigned different numerical IPs from
time to time.
It occurs to me that my new 'dual-boot' problems with F40 KDE might be
related to this, but I'm not clear how I could test it. I've posted
both here and on the kde list.
I have two screen-devices, HDMI tv and vga monitor. By default booting
is to Windows, but 'escape' early on goes to an HP-provided
boot-selection sequence and grub.
Choosing "modesetting" starts booting with both screens active, but
freezes shortly after a cursor appears.
"nomodeset" gives a usable system, but with the vga screen never active
and final HDMI resolution fixed at 800x600.
Could this perhaps be a conflict of hostnames set at power-on and by Fedora?
John P
No.
Whatever the hostname is it really does not matter for booting or not.
The fact that nomodeset works tells me that the graphics driver in the
kernel is unable to handle your card and/or monitors in some critical
way.
What kind of vga/video card do you have?
Thanks, Tim and Roger, for both these replies.
The harware was working well, before my recent upgrades from f38,
briefly to f39 and now to f40. Then I was using the rpmfusion 470xx
builds of the nvidia legacy drivers. Now the dual-boot box has no
nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of
config might remain; inxi still finds nvidia traces:
{{{
ohn@FedWin4c1:~$ inxi -G
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] driver: N/A
Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu: N/A resolution: 800x600
API: EGL v: 1.5 drivers: kms_swrast,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.5 vendor: mesa v: 24.0.6 renderer: llvmpipe (LLVM 18.1.1
256 bits)
API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland
$ sudo dmesg | less
[0.00] Command line:
BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
Mose variations of this give a frozen system.
}}}
John
--
___
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: What is Castor ? Att.Jonathan Billings.
On 08/05/2024 20:13, Samuel Sieb wrote: On 5/8/24 10:50 AM, John Pilkington wrote: The harware was working well, before my recent upgrades from f38, briefly to f39 and now to f40. Then I was using the rpmfusion 470xx builds of the nvidia legacy drivers. Now the dual-boot box has no nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of config might remain; inxi still finds nvidia traces: Nouveau is included with the kernel, it doesn't have its own package. xorg-x11-drv-nouveau is supplied by fedora, but I was told that the kernel driver was more up to date, so I removed the fformer. ohn@FedWin4c1:~$ inxi -G Graphics: Device-1: NVIDIA GK208B [GeForce GT 710] driver: N/A Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6 compositor: kwin_wayland driver: X: loaded: nvidia This is the xorg nvidia drive, but I assume it's not working if the kernel driver isn't loaded. unloaded: fbdev,modesetting,nouveau,vesa gpu: N/A resolution: 800x600 API: EGL v: 1.5 drivers: kms_swrast,swrast platforms: gbm,wayland,x11,surfaceless,device API: OpenGL v: 4.5 vendor: mesa v: 24.0.6 renderer: llvmpipe (LLVM 18.1.1 256 bits) llvmpipe means it's using software 3D rendering because it doesn't have a 3d hardware driver. I don't think I want 3D API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland $ sudo dmesg | less [ 0.00] Command line: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64 root=/dev/mapper/fedora_localhost--live-root ro rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset There are a lot of duplicates in that list. If you include "nomodeset", then you'll be using the lowest common factor display options. Is there a reason you don't want to use the rpmfusion drivers? It appears that nouveau isn't working for your system, or else something is mixed up. You could check the logs for a previous boot that didn't work. I have happily used the rpmfusion builds of 470xx until a few weeks ago; but it was said that wayland support was missing, and for some time akmods failed to build anyway. I hoped to be able to use the reverse-engineered FOSS drivers. And a few days ago, after reverting to 470xx, kwin_wayland appeared to be running 4 cpu cores at 90% and the mouse was unusable. On the linux-only box I have nvidia-gpu-firmware installed. It may not be loading (MythTV says vdpau isn't available) but that system currently does the jobs that I want. My apologies, by the way, for what looks like a hijack. John -- ___ 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
F40 dual-boot problem, was Re: What is Castor ? Att.Jonathan Billings.
On 08/05/2024 21:57, Samuel Sieb wrote:
On 5/8/24 1:13 PM, John Pilkington wrote:
On 08/05/2024 20:13, Samuel Sieb wrote:
On 5/8/24 10:50 AM, John Pilkington wrote:
The harware was working well, before my recent upgrades from f38,
briefly to f39 and now to f40. Then I was using the rpmfusion 470xx
builds of the nvidia legacy drivers. Now the dual-boot box has no
nvidia or nouveau rpms installed (rpm -qa) although I suppose bits
of config might remain; inxi still finds nvidia traces:
Nouveau is included with the kernel, it doesn't have its own package.
xorg-x11-drv-nouveau is supplied by fedora, but I was told that the
kernel driver was more up to date, so I removed the fformer.
xorg-x11-drv-nouveau is the xorg driver that uses (and requires) the
kernel driver. You need both.
llvmpipe means it's using software 3D rendering because it doesn't
have a 3d hardware driver.
I don't think I want 3D
KDE/wayland uses 3D rendering.
API: Vulkan v: 1.3.280 drivers: N/A surfaces: xcb,xlib,wayland
$ sudo dmesg | less
[ 0.00] Command line:
BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.8.8-300.fc40.x86_64
root=/dev/mapper/fedora_localhost--live-root ro
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/root
rd.lvm.lv=fedora_localhost-live/swap rhgb quiet
rd.driver.blacklist=nvidia modprobe.blacklist=nvidia nomodeset
There are a lot of duplicates in that list. If you include
"nomodeset", then you'll be using the lowest common factor display
options. Is there a reason you don't want to use the rpmfusion
drivers? It appears that nouveau isn't working for your system, or
else something is mixed up. You could check the logs for a previous
boot that didn't work.
I have happily used the rpmfusion builds of 470xx until a few weeks
ago; but it was said that wayland support was missing, and for some
time akmods failed to build anyway. I hoped to be able to use the
reverse-engineered FOSS drivers. And a few days ago, after reverting
to 470xx, kwin_wayland appeared to be running 4 cpu cores at 90% and
the mouse was unusable.
As far as I know, the NVidia drivers have had Wayland support for a long
time. That CPU usage is likely if you're using software 3D rendering.
You need to sort out what you have installed.
On the linux-only box I have nvidia-gpu-firmware installed. It may
not be loading (MythTV says vdpau isn't available) but that system
currently does the jobs that I want.
My apologies, by the way, for what looks like a hijack.
Yes, you definitely should have started a new thread.
but it seems better to continue here.
On the dual-boot box I have done
"sudo dnf remove *nouveau*", which removed nouveau-firmware and
xorg-x11-drv-nouveau
"sudo dnf install *470xx*", which pulled in the rpmfusion builds of the
legacy nvidia driver and updated the kernel command line. Wayland
support has been said to start at series 490, which is why I had been
looking at nouveau.
"sudo dnf upgrade" because things are moving quickly at present.
Now booting goes as expected, giving two screens at their expected
resolution *BUT* the cursor movement is jerky, keyboard response is very
slow, and "atop" shows 4 3GHz cores at 99%, for kwin_wayland.
Ctrl/Alt/F3 is the only way to make progress.
Throughout this saga there have been fleeting complaints about the abrtd
service. It's the only one that "systemctl" lists in red.
Ctrl/Alt/F1 says the abrtd.service failed to start and lists Dependency
issues for four abrtd services. I haven't investigated more.
In some ways this is progress, but the system is less usable than the
800x600 nouveau-only form.
{{{
$ inxi -GA
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] driver: nvidia v: 470.239.06
Device-2: Chicony HP 720p HD Monitor Webcam driver:
snd-usb-audio,uvcvideo type: USB
Display: server: X.org v: 1.20.14 with: Xwayland v: 23.2.6 driver: X:
loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu:
nvidia,nvidia-nvswitch tty: 100x37 resolution:
1: 1360x768 2: 1920x1080
API: EGL v: 1.5 drivers: kms_swrast,nvidia,swrast platforms:
gbm,wayland,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 24.0.6 note:
console (EGL sourced)
renderer: llvmpipe (LLVM 18.1.1 256 bits), NVIDIA GeForce GT
710/PCIe/SSE2
API: Vulkan v: 1.3.280 drivers: N/A surfaces: wayland
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
Device-2: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
Device-3: Chicony HP 720p HD Monitor Webcam driver:
snd-usb-audio,uvcvideo type: USB
Device-4: C-Media USB PnP Sound Device driver:
hid-generic,snd-usb-audio,usbhid type: USB
API: ALSA v: k6.8.8-300.fc40.x86_64 status: kernel-api
Re: What is Castor ? Att.Jonathan Billings.
On 10/05/2024 15:00, George N. White III wrote: On Wed, May 8, 2024 at 5:13 PM John Pilkington <mailto:johnpilk...@gmail.com>> wrote: On 08/05/2024 20:13, Samuel Sieb wrote: > On 5/8/24 10:50 AM, John Pilkington wrote: >> The harware was working well, before my recent upgrades from f38, >> briefly to f39 and now to f40. Then I was using the rpmfusion 470xx >> builds of the nvidia legacy drivers. Now the dual-boot box has no >> nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of >> config might remain; inxi still finds nvidia traces: > > Nouveau is included with the kernel, it doesn't have its own package. xorg-x11-drv-nouveau is supplied by fedora, but I was told that the kernel driver was more up to date, so I removed the fformer. I have a late 2012 iMac with Nvidia that was using 470xx. I mostly use nouveau with wayland, but do have xorg-x11-drv-nouveau. There were issues with 470xx failing to build in F40 with the akmods install from rpmfusion, but now there is a testing version that does install. Some users have success with the Nvidia installer. I have the rpmfusion-testing package installed but haven't had time to test it. I don't think it supports Wayland. Thanks for your comment. I posted later, in this thread but with a subject-line change. It does show in HyperKitty and I've put a link to it on the rpmfusion list. I have removed all nouveau packages and installed all *470xx" packages, which installed the new versions. That gave HDMI and vga screens with their expected resolutions but essentially no user interactivity because active kwin_wayland runs all cpus at full throttle. Perhaps that's 'not supported'. Ctrl/Alt/F3 still works, and I have 6.8.9 now. That complained that there was "no space on /boot/efi/EFI/Linux/Fedora " (200 MB) but seems to run (with the same cpu runaway) after I deleted several f39 files. The single-boot box is still running nouveau. Cheers, John -- ___ 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: What is Castor ? Att.Jonathan Billings.
On 10/05/2024 15:51, John Pilkington wrote: On 10/05/2024 15:00, George N. White III wrote: On Wed, May 8, 2024 at 5:13 PM John Pilkington <mailto:johnpilk...@gmail.com>> wrote: On 08/05/2024 20:13, Samuel Sieb wrote: > On 5/8/24 10:50 AM, John Pilkington wrote: >> The harware was working well, before my recent upgrades from f38, >> briefly to f39 and now to f40. Then I was using the rpmfusion 470xx >> builds of the nvidia legacy drivers. Now the dual-boot box has no >> nvidia or nouveau rpms installed (rpm -qa) although I suppose bits of >> config might remain; inxi still finds nvidia traces: > > Nouveau is included with the kernel, it doesn't have its own package. xorg-x11-drv-nouveau is supplied by fedora, but I was told that the kernel driver was more up to date, so I removed the fformer. I have a late 2012 iMac with Nvidia that was using 470xx. I mostly use nouveau with wayland, but do have xorg-x11-drv-nouveau. There were issues with 470xx failing to build in F40 with the akmods install from rpmfusion, but now there is a testing version that does install. Some users have success with the Nvidia installer. I have the rpmfusion-testing package installed but haven't had time to test it. I don't think it supports Wayland. Thanks for your comment. I posted later, in this thread but with a subject-line change. It does show in HyperKitty and I've put a link to it on the rpmfusion list. I have just updated that, re the dual-boot box. See below: I have removed all nouveau packages and installed all *470xx" packages, which installed the new versions. That gave HDMI and vga screens with their expected resolutions but essentially no user interactivity because active kwin_wayland runs all cpus at full throttle. Perhaps that's 'not supported'. Ctrl/Alt/F3 still works, and I have 6.8.9 now. That complained that there was "no space on /boot/efi/EFI/Linux/Fedora " (200 MB) but seems to run (with the same cpu runaway) after I deleted several f39 files. I hope this doesn't offend any 'religious' beliefs. Installing plasma-workspace-x11 (in the updates repo but NOT supported by the Fedora KDE SIG) and selecting "Desktop Session: Plasma (X11)" in the login screen, has apparently restored this system to a usable state. At present password entry still has a sluggish keyboard. The single-boot box is still running nouveau. Cheers, John -- ___ 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 too small
On 14/05/2024 08:54, Michal Schorm wrote: Hi, for an immediate workaround, remove the oldest kernel. Here are the steps together with an example output: 1) List installed kernel-core packages: # rpm -qa | grep kernel-core | sort kernel-core-6.8.4-200.fc39.x86_64 kernel-core-6.8.6-200.fc39.x86_64 kernel-core-6.8.7-200.fc39.x86_64 2) Remove the oldest one # dnf remove Dependencies resolved. PackageArch Version Repository Size Removing: kernel-corex86_64 6.8.4-200.fc39@updates66 M Removing dependent packages: kernel x86_64 6.8.4-200.fc39@updates 0 kernel-modules x86_64 6.8.4-200.fc39@updates58 M kernel-modules-corex86_64 6.8.4-200.fc39@updates32 M kernel-modules-extra x86_64 6.8.4-200.fc39@updates 2.4 M Transaction Summary Remove 5 Packages Freed space: 159 M 3) profit you have extra ~160 MB now. System update should have enough space to install the new kernel now. 4) Once finished, I'd recommend you to try to enlarge your /boot/ partition a bit (e.g. 100 - 500 MB ?) to avoid this problem permanently. Michal Schorm Software Engineer Core Services - Databases Team Red Hat I had the same problem a few days ago and did the same. I posted this reply but HyperKitty doesn't find it. So.. But I installed f40 a few days ago, and today "dnf upgrade" installed kernel-6.8.8 but *not* vmlinuz-6.8.8, so booting failed. My /boot partition is 450 GB, and I now have two bootable f40 kernels and a recent rescue kernel. There's no room for another. You probably don't have a "recovery" option. I now have "installonly_limit=2" in /etc/dnf/dnf.conf, but a new "dnf upgrade" after that said there was "nothing to do". What did work was ( while running 6.8.7): sudo dnf remove kernel-core-6.8.8 sudo dnf upgrade and then when "systemctl list-jobs" was clear, "sudo systemctl reboot" I, too, would prefer to have a bigger /boot, but this info might help. John P -- On Tue, May 14, 2024 at 9:44 AM Patrick Dupre via users wrote: Hello, During an update, I get Error Summary - Disk Requirements: At least 7MB more space needed on the /boot filesystem. How can I fix it without currently resizing /boot? Thank drwx--. 5 root root 4096 May 14 08:36 grub2 lrwxrwxrwx. 1 root root45 Mar 7 13:24 symvers-6.7.7-100.fc38.x86_64.xz -> /lib /modules/6.7.7-100.fc38.x86_64/symvers.xz -rw---. 1 root root 81850041 Mar 7 13:24 initramfs-6.7.7-100.fc38.x86_64.img -rw-r--r--. 1 root root269378 Mar 1 01:00 config-6.7.7-100.fc38.x86_64 -rw-r--r--. 1 root root 8851783 Mar 1 01:00 System.map-6.7.7-100.fc38.x86_64 -rwxr-xr-x. 1 root root 14794568 Mar 1 01:00 vmlinuz-6.7.7-100.fc38.x86_64 lrwxrwxrwx. 1 root root45 Feb 13 17:38 symvers-6.7.4-100.fc38.x86_64.xz -> /lib /modules/6.7.4-100.fc38.x86_64/symvers.xz -rw---. 1 root root 81905180 Feb 13 17:37 initramfs-6.7.4-100.fc38.x86_64.img -rw-r--r--. 1 root root269327 Feb 5 01:00 config-6.7.4-100.fc38.x86_64 -rw-r--r--. 1 root root 8850577 Feb 5 01:00 System.map-6.7.4-100.fc38.x86_64 -rwxr-xr-x. 1 root root 14806856 Feb 5 01:00 vmlinuz-6.7.4-100.fc38.x86_64 lrwxrwxrwx. 1 root root46 Jan 25 13:39 symvers-6.6.13-100.fc38.x86_64.xz -> /li b/modules/6.6.13-100.fc38.x86_64/symvers.xz -rw---. 1 root root 42503616 Jan 25 13:39 initramfs-6.6.13-100.fc38.x86_64.img -rw-r--r--. 1 root root266375 Jan 20 01:00 config-6.6.13-100.fc38.x86_64 -rw---. 1 root root 8786049 Jan 20 01:00 System.map-6.6.13-100.fc38.x86_64 -rwxr-xr-x. 1 root root 14676712 Jan 20 01:00 vmlinuz-6.6.13-100.fc38.x86_64 -rw-r--r--. 1 root root147744 Jan 7 01:00 memtest86+x64.bin drwx--. 4 root root 4096 Jun 20 2023 efi drwxr-xr-x. 2 root root 4096 Jun 20 2023 extlinux -rw---. 1 root root 103940590 Jul 21 2022 initramfs-0-rescue-c60d54440c4d444a9eb5a084a65edf40.img -rwxr-xr-x. 1 root root 11802352 Jul 21 2022 vmlinuz-0-rescue-c60d54440c4d444a9eb5a084a65edf40 drwxr-xr-x. 3 root root 4096 Jul 21 2022 loader drwx--. 2 root root 16384 Jul 21 2022 lost+found === Patrick DUPRÉ | | email: pdu...@gmx.com === -- -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-con
Re: My Fedora 40 experiences
er hardware work on current kernels. Rpmfusion is having difficulties finding volunteers to package software. Fewer volunteers have access to older hardware and those that do are getting old themselves and may be dealing with the problems facing older people in our society, so rpmfusion falls down in their priority list. -- George N. White III I have two F40 systems using nvidia GT_710 cards, both 'dnf upgraded' a few minutes ago. It's beginning to look good, but it has been a painful experience. I'm using the 470.239.06 driver from rpmfusion and the plasma-workspace-x11 package from fedora-upgrades, with the "Desktop Session: Plasma (X11)" selected on login. With the same driver and the Wayland desktop I have found all cpus maxed out, with keyboard and mouse almost unusable. On one system this still makes login awkward. I believe that this support of x11 has been championed by two individuals, and the Fedora KDE SIG disowns that effort. Clearly things are going to be fragile for some time. Before today's upgrade one system frequently reported graphics resets. That seems to have been fixed. HTH John P -- ___ 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: My Fedora 40 experiences
On 17/05/2024 13:08, francis.montag...@inria.fr wrote: Hi. On Thu, 16 May 2024 23:04:21 +1000 Stephen Morris wrote: On 16/5/24 21:33, George N. White III wrote: Many users have had problems with the akmod-nvida install. For 470xx the module failed to compile. For newer cards, users sometimes end up with unsigned drivers. This usually means they rebooted too quickly (during the window after the module was compiled but before it was signed.). Or before the depmod done by the postintall of the kmod-nvidia-KERNEL RPM finishes. I have had the reboot happen too too quickly before but in this case I had no control over the reboot process, it happened automatically when the installs were completed. Right: more precisely as soon as dnf system-upgrade finishes. As said earlier on this list: I made a proposal to prevent that: kmod failed to load after upgrade Fedora using dnf system-upgrade https://bugzilla.redhat.com/show_bug.cgi?id=2011120 still waiting for approval. This morning 'dnf upgrade' on one of my boxes installed the 470.239.06-2 versions of akmod and kmod, while the other box, having the -1 nersions, said there was 'nothing to do'; then packagekit found them and did a preliminary reboot before install. Both boxes now have the -2 versions installed and running. The process does take several minutes - and I did an "akmods --rebuild --force" just to make sure. F40 with plasma-workspace-x11 does seem to be working well now for me, and can use vdpau. John P -- ___ 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: My Fedora 40 experiences
On 18/05/2024 03:17, Stephen Morris wrote: On 17/5/24 22:43, John Pilkington wrote: On 17/05/2024 13:08, francis.montag...@inria.fr wrote: Hi. On Thu, 16 May 2024 23:04:21 +1000 Stephen Morris wrote: On 16/5/24 21:33, George N. White III wrote: Many users have had problems with the akmod-nvida install. For 470xx the module failed to compile. For newer cards, users sometimes end up with unsigned drivers. This usually means they rebooted too quickly (during the window after the module was compiled but before it was signed.). Or before the depmod done by the postintall of the kmod-nvidia-KERNEL RPM finishes. I have had the reboot happen too too quickly before but in this case I had no control over the reboot process, it happened automatically when the installs were completed. Right: more precisely as soon as dnf system-upgrade finishes. As said earlier on this list: I made a proposal to prevent that: kmod failed to load after upgrade Fedora using dnf system-upgrade https://bugzilla.redhat.com/show_bug.cgi?id=2011120 still waiting for approval. This morning 'dnf upgrade' on one of my boxes installed the 470.239.06-2 versions of akmod and kmod, while the other box, having the -1 nersions, said there was 'nothing to do'; then packagekit found them and did a preliminary reboot before install. Both boxes now have the -2 versions installed and running. The process does take several minutes - and I did an "akmods --rebuild --force" just to make sure. F40 with plasma-workspace-x11 does seem to be working well now for me, and can use vdpau. How did you get Xorg working with Plasma as I can't see any group in dnf to install that? The path to where I am now has been complicated, mainly because my nvidia hardware is 'legacy' and its 470xx driver has not claimed to support Wayland. Under Wayland all cpus max out, and keyboard/mouse are almost unusable. YMMV. dnf info plasma-workspace-x11 It's in the Fedora 'updates' repo. The other thing I didn't like with the F40 upgrade was in F39 I had dnf configured to retain 5 kernels, but the F40 upgrade reset that back to 3. My system has 450 MB /boot, space for only 2 kernels + rescue. regards, Steve John P -- ___ 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: Updated 3 machines from 39 to 40, but on 4th machine get this error at end??
On 19/05/2024 09:48, Michael D. Setzer II via users wrote: Error: Transaction test error: file /usr/share/gir-1.0/GLib-2.0.gir conflicts between attempted installs of glib2-devel-2.80.2-1.fc40.i686 and glib2-devel-2.80.2-1.fc40.x86_64 # rpm -qa | grep glib2-devel glib2-devel-2.78.6-1.fc39.x86_64 glib2-devel-2.78.6-1.fc39.i686 Don't know if other 3 machines had these installed or not? Thanks for any recommendations?? Do you need the i686 package? I tried your rpm -qa line on one box, and worryingly got a db error: error: rpmdbNextIterator: skipping h# which looks as if it has been fixed by rpm --rebuilddb. The package found was: glib2-devel-2.80.2-1.fc40.x86_64 John P -- ___ 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: Updated 3 machines from 39 to 40, but on 4th machine get this error at end??
On 19/05/2024 18:08, Michael D. Setzer II wrote: On 19 May 2024 at 14:50, John Pilkington wrote: Date sent: Sun, 19 May 2024 14:50:55 +0100 Subject:Re: Updated 3 machines from 39 to 40, but on 4th machine get this error at end?? To: users@lists.fedoraproject.org From: John Pilkington Send reply to: Community support for Fedora users On 19/05/2024 09:48, Michael D. Setzer II via users wrote: Error: Transaction test error: file /usr/share/gir-1.0/GLib-2.0.gir conflicts between attempted installs of glib2-devel-2.80.2-1.fc40.i686 and glib2-devel-2.80.2-1.fc40.x86_64 # rpm -qa | grep glib2-devel glib2-devel-2.78.6-1.fc39.x86_64 glib2-devel-2.78.6-1.fc39.i686 Don't know if other 3 machines had these installed or not? Thanks for any recommendations?? Do you need the i686 package? Turns out the i686 file wasn't being used by anything else, so uninstalled it, and reran the upgrade, and it went thru fine. Don't recall why it has both x86_64 and i686 version installed, or why they earlier had no conflict together on 39, but now failed on 40? Did find it stranger in rerunning the upgrade, it didn't have to download any of files, but rpmkeys took just as long to run. But wasn't sure uninstalling it would fix problem, so just thought I'd check if might require something more. I suppose you were using this: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/ and it's likely that downloading with --allowerasing and/or --skip-broken would have gone ahead (Section 3). But the document suggests a number of post-upgrade jobs, most of which ideally require careful thought before 'yes' :-) Thanks for quick reply. I tried your rpm -qa line on one box, and worryingly got a db error: error: rpmdbNextIterator: skipping h# which looks as if it has been fixed by rpm --rebuilddb. The package found was: glib2-devel-2.80.2-1.fc40.x86_64 John P -- ___ 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mi...@guam.net mailto:msetze...@gmail.com mailto:msetze...@gmx.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: VirtualBox does not run on Wayland
On 06/07/2024 09:50, Frédéric wrote: Hi, It took me a while to understand that Wayland was the source of my problem so I share my experience so that others can be quicker to solve this issue. I moved to F40 and Plasma came only with Wayland. Then, everything seemed OK apart that my Windows VM running in VirtualBox did not capture the mouse (quite annoying!). I run VirtualBox 7.0.18-1.fc40 from rpmfusion-free-updates. I tried all options for the mouse (PS/2 mouse, USB tablet, multi-touch USB tablet and USB MT TouchScreen and TouchPad) but nothing worked. The VirtualBox menu above the VM was also not accessible. After one week of research, I found this post: https://askubuntu.com/questions/1512787/ubuntu-22-04-2-virtualbox-7-0-18-captured-mouse-is-not-contained-when-integrat and installed plasma-workspace-x11. I now run X11 Plasma and VirtualBox works fine. Thanks, F plasma-workspace-x11 in F40 may be auto-erased by later kde updates. Playground dispute. https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.org/thread/M45QTYTM52LQNMJCW5UX3VQYQHDWUV42/ John P -- ___ 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: Remastering ISO filenames (was: make a bootable dvd)
Thought that entries in a vfat file system are case sensitive? John Westerdale Sr Container Consultant Red Hat <https://www.redhat.com/> NYC - He / Him / His - john.westerd...@redhat.comM: 201-376-9993 IM: jwesterd <https://www.redhat.com/> I respect your Life-Work balance. No need to respond immediately if you receive this outside your normal working hours. On Mon, Jul 8, 2024 at 9:42 PM Jeffrey Walton wrote: > On Mon, Jul 8, 2024 at 9:16 PM Tim via users > wrote: > > > > On Mon, 2024-07-08 at 17:01 +0200, François Patte wrote: > > > I downloaded the f40 iso for a worksation, but I did not see on the > > > fedora website how to burn a bootable DVD with this iso file > > > > This page has some doing it from the command line instructions: > > > > > https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/ > > > > Bear in mind that if it doesn't work, in the end, it *may* not be that > > you've done something wrong. I couldn't make a bootable disc (of any > > kind) out of the spins. I had to use the server edition. > > > > NB: This is some kind of compatibility issue with *SOME* hardware and > > some Fedora ISO files, not all hardware. > > ++. The firmware on my old Asus Q500a laptop wanted the efi filename > in all lowercase -- EFI/BOOT/bootx64.efi instead of > EFI/BOOT/BOOTx64.efi. The laptop would not boot to the DVD otherwise. > The UEFI on the laptop was by a company called Aptio. > > Attached is the script I wrote to perform the rename. The ISO image > could then be burned to CD. > > 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 > -- ___ 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: nvidia drivers installation
On 15/07/2024 17:14, Patrick O'Callaghan wrote: On Mon, 2024-07-15 at 10:10 -0400, Jeffrey Walton wrote: On Mon, Jul 15, 2024 at 6:48 AM George N. White III wrote: On Sun, Jul 14, 2024 at 5:50 AM François Patte wrote: [...] I have secure boot enabled. Is there some how-to explaining with details how to proceed. I'm not very good with efi boot system nor secure boot. You should know that secure boot as implemented in most linux distros is "security theater". Another complaint about Trusted Execution Environments and Secure Boot is, they only make a statement/attestation about the system in the past. A system with resident malware exploited after boot will still report Ok. Extra work is needed when initread and kernel are separate, and /boot should be encrypted: <https://ruderich.org/simon/notes/secure-boot-with-grub-and-signed- linux-and-initrd> The existing Fedora secure boot configuration may offer some protection for those who also boot Windows. I'm not sure what any of this has to do with installing Nvidia drivers, but then I've never enabled Secure Boot. poc I'm not sure what the current status of your system is, but the usual 'howto' is https://rpmfusion.org/Howto/NVIDIA?action=show&redirect=Howto%2FnVidia That, of course, assumes that you already have a working system that can 'dnf install' the packages appropriate to your card. If that's the case it is best to wait, after dnf completes, for the actual modules to be built and installed. On my systems that takes several minutes, particularly if there are multiple kernels. I usually run 'atop', after dnf has quit, to watch the sequence of akmods-related events. When it all calms down 'sudo systemctl reboot' might work. HTH, John P -- ___ 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 and System Rescue CD disagree on the state of my btrfs filesystem
On 2024-07-26 8:25 a.m., Richard Shaw wrote: On Thu, Jul 25, 2024 at 6:29 PM Jeffrey Walton wrote: On Thu, Jul 25, 2024 at 2:15 PM Richard Shaw wrote: > > I recently had the Fedora install on my laptop go sideways (Ryzen 5 4500U w/ nvme disk). > > The filesystem was going readonly so I installed System Rescue CD to a thumb drive to investigate. Sure enough I had 4 unrecoverable errors. > > I don't keep anything critical on it so I decided to just reinstall with Fedora 40. Installation went fine but I did notice weird dnf output on my first updated buy everything SEEMED fine... > > I rebooted after the update and tried to log in when after a minute or two the system froze. Rebooted and sure enough a `dmesg | grep BTRFS` showed an error. > > Back to booting with System Rescue CD neither a `btrfs check --check-data-csum` or after mounting, a `btrfs scrub` show any errors. > > So who's right? And if there is an error, what's causing it? I've checked the drive with smartctl and even let the factory HP firmware diag tools run in a loop overnight checking everything without error. The (1) irrecoverable disk errors from the original install, and (2) the errors from the current install, and (3) the errors from dnf indicate (to me) you have a failed NVMe drive. I used to see the symptoms all the time when using SDcards in ARM dev boards. I would put a swap file on the dev board (due to lack of resources), and the drives would fail within about 6 months with the symptoms you describe. Now the interesting part (to me) is, (4) lack of errors reported by some tools. That indicates to me a Chinese drive that misreports drive size and statistics. They usually show up on thumb drives, but I experienced one on a SSD drive years ago. Also see <https://www.google.com/search?q=counterfeit+drive+misreport+size>. All in all, I would replace the NVMe drive with a new one from a trusted source. Not Amazon or eBay. It's the drive that came with the laptop so unlikely to be a cheap/phony drive but the mystery does get deeper... 1. I was able to see the same results even if I booted to a F40 Live USB. I'm thinking that the system caught the problem quick enough the error didn't actually get written to the disk. 2. I consistently see the problem at about 30 seconds (from dmesg) if I boot the 6.9.9 or 6.9.10 kernels that have been installed via updates. If I boot 6.8.5, the kernel that shipped with F40 I can't reproduce the problem. Of course that's strange because if this was a widespread issue there would be tons of people complaining. Odds are that you have bad ram or are running the processor clock higher than what it can handle. I also had this kind of issue when I had a bad video card, but the system generally froze or crashed and left the drive in an unrecoverable state. The tools for fixing a btrfs partition are generally lacking in Fedora, and the tools that come with btrfs are also useless when the failing partition is your active root partition. I don't know if Suse has better tools, but its a huge problem with Fedora recoverability. So, question for the Fedora filesystem team: When are we going to see fixed btrfs tools? -- John mellorjohn.mel...@gmail.com 519-721-6671 -- ___ 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: DNF upgrade not upgrading my kernel
On 11/08/2024 18:30, Dave Close wrote: I can't make sense of this output, can you? # rpm -q kernel-core kernel-core-6.9.9-100.fc39.x86_64 kernel-core-6.9.12-200.fc40.x86_64 kernel-core-6.10.3-200.fc40.x86_64 That kernel runs for me, but I have romm for only two. How big is /boot ? -- ___ 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 stops before startx....
On 19/08/2024 09:51, François Patte wrote: Le 2024-08-18 16:05, francis.montag...@inria.fr a écrit : Hi. On Sun, 18 Aug 2024 14:59:09 +0200 François Patte wrote: Le 2024-08-17 06:07, Robert McBroom via users a écrit: The 6.10.x kernels are not yet supported for nvidia. I checked past friday with the 6.10.4-200.fc40 kernel and the 4 drivers provided by rpmfusion. akmods succeded to compile: kmod-nvidia-3:555.58.02-1.fc40.x86_64 This was the installed akmod-nvidia (for GeForce GTX 1050 Ti} and, for me, it failed to compile when upgrading the kernel to 6.10.4-200.fc40.x86_64 How can we be sure that a new kernel has the suitable stuff to compile kernel modules? (before launching dnf upgrade, of course) Regards I can't answer that, and I don't know how much our systems have in common. But I have had no serious problems with almost daily 'dnf upgrade's since this post on 14 July, which named the packages being used. That's on an old HP box, 470xx, KDE plasma-workspace-x11 and not using EFI. https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.org/thread/EIKE6QFJDDSGLRMGIYABA4R6QQLLYPC5/ John P -- ___ 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 stops before startx....
On 22/08/2024 19:52, home user via users wrote: On 8/22/24 3:53 AM, Barry Scott wrote: On 22 Aug 2024, at 02:58, home user via users wrote: I'll just say I can only keep one old kernel and not go into the details. FYI: dnf update will never remove the kernel that you are currently running. Barry (not replying specifically to Barry) I currently have two kernels on this f39 workstation: * 6.9.12, and * 6.10.4. I do not have space for another. If I understand things correctly, the rpmfusion nvidia package that I need for 6.10.xx is now available. My lesser question: Am I correct? If the answer to the lesser question is "yes", then here's my greater question: Should I: A. boot into 6.9.12, and then do the "dnf upgrade"; B. boot into 6.10.4, and then do the "dnf upgrade"; or C. something else (what?)? thanks, Bill. My f40 box is at present off, but runs 6.10.5 with 470xx. That is from the rpmfusion-nonfree-updates testing repo. So you need to enable that repo for f39. If you can then boot and run dnf in an x11 desktop, either of your suggestions ought to work, leaving you with the running kernel and the installed update. After that, ensure that the akmods build process has completed before rebooting. L John P -- ___ 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: RAM shows less
Just a question here... are you running a 32-bit version of Fedora or a 64- bit version? 32-bit versions will only show about 3 gigs of memory, no matter how much if you have 20 Gigs, you'll only see 3. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: RAM shows less
On Tue May 11 2010, Mike Guilmot wrote: > > > Just a question here... are you running a 32-bit version of Fedora > > > or a > > > > 64- > > > > > bit version? 32-bit versions will only show about 3 gigs of memory, > > > no matter how much if you have 20 Gigs, you'll only see 3. > > > > What? > > > > [egres...@meimei RSS-Estimates_Docs]$ cat /proc/meminfo > > MemTotal:8255264 kB > > > > [egres...@meimei RSS-Estimates_Docs]$ uname -r > > 2.6.30.10-105.2.23.fc11.i686.PAE > > The PAE kernels do not have the 3 GB limitation. No idea about the > non-PAE kernels though. > I can see my full 4 Gb in 32b PAE kernel too. > > MemTotal:4113744 kB > 2.6.32.11-99.fc12.i686.PAE I sit corrected. IT has been my understanding that 32-bit kernels could not see or maybe could not *access* more than 3 Gigs of memory? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: esata drive question
On 05/12/2010 09:39 AM, Gerhard Magnus wrote: > I recently acquired a Toshiba external hard drive that has both usb and > eSATA ports and would like to use the eSATA connection to take advantage > of the speed. I'm running FC11 with the gnome desktop. Is it as simple > as getting an eSATA PCI card and cable or does Fedora have other > requirements? Thanks for any advice! --Jerry > > I got a bracket with 2 eSATA connectors, on the inside are just 2 sata cables that connect to the motherboard sata ports. Works fine with F11 and 2 Western Digital external hard drives. No PCI card required, unless you need some additional sata ports. Regards, John -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: esata drive question
On 05/12/2010 08:36 PM, Tim wrote: > On Wed, 2010-05-12 at 19:47 -0700, john wendel wrote: >> I got a bracket with 2 eSATA connectors, on the inside are just 2 sata >> cables that connect to the motherboard sata ports. Works fine with F11 >> and 2 Western Digital external hard drives. No PCI card required, >> unless you need some additional sata ports. > > That may not work for all circumstances. External SATA is supposed to > handle hotplugging, but that's not expected with internal SATA drives. > If an internal host supports hotplugging, consider that to be an > surprise bonus. > Just for reference, the motherboard is an Intel and the sata controller > SATA controller: Intel Corporation 82801GR/GH (ICH7 Family) SATA AHCI > Controller (rev 01) it's pretty old, but hotplugging works fine in this configuration. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: k3b users, I need help.
On 05/19/2010 07:21 PM, r...@dwf.com wrote: > I have used k3b before to burn iso's, but never to build a CD/DVD of my own > files. (I used to use xcdroast for this...) > > In any case, Im trying to build a CD with about 130k of data files. > They were initially under 3 directory heads, but to simplify things Ive moved > the directories under one directory head. > > When I bring up k3b, and drag that directory from the top to the bottom > window, > it tells me that there is 5.7Mb there, which is wrong. If I burn the CD, I see > a whole lot of empty directories. > > So how do I tell k3b that I want all the data below each directory head? > That would seem to be the obvious default, but its not happening, and I > dont see any option to turn it on/off. > > Probably something stupid, but whatever, I need help. > I just tried it with 4 nested levels of directories, each with about 40 data files. I just had it make the .iso file which I then loop mounted and verified that it was OK. No options to set, it just worked. Which version of Fedora / K3B are you running? Do you have 130,000 data files or 130KB of data? Regards, John -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Linking two files together
On 05/26/2010 10:16 AM, Rector, David wrote: > Hello, > > I have studied various filesystems, and am fairly familiar with how they are > structured. However, I am currently stuck on trying to do what seems like a > simple thing. > > I would like to join two files together without having to physically copy > bytes (i.e. I have vary large files, so I don't want to use 'cat'). It seems > to me that it should be possible to simply modify the file entry in the > filesystem such that the last inode of the first file points to the first > inode of the second file. I guess this is similar to a "hard link", but used > to join files rather than simply have another pointer to one file. > > I have seen 'mmv' and 'lxsplit' and they all seem to do the same thing, > namely they want to physically copy the bytes in order to join two files > together. > > Is there any such utility in linux to perform such a hard link to join or > connect two files together without having to copy bytes? > > Thanks for your help. > > Dave Rector > *:^) You could create a shared library that replaces the libc versions of "open", "read", "write", "seek", "lseek", "close", ... (whatever your app needs). It would open multiple files, but return a single file handle to the caller. It would need to track the "virtual" file pointer by examining each read, write, seek call and switch "real" files as required. Not trivial, but also not rocket science. Just handling sequential reads is pretty simple. Full file handling semantics would be a pain. Regards, John -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Relabeling all audio files on a server
On 05/31/2010 10:27 AM, Bill Davidsen wrote:
> Leonard Adjei wrote:
>> I have a server which houses thousands of audio tracks and materials.
>> Recently I started using a web application which seems to have a ew
>> problems with the naming convention used by default.
>> For example it has a problem with apostrophe signs ('), I want to be
>> able to create a script which goes to through the folder and all
>> files and folders under it and renames all the tracks by deleting
>> every entry of the apostrophe where it encounters them.
>> E.g. This ain't no game => This aint no game
>> Mr Brown's Last supper => Mr Browns Last supper
>> and like that. I want the apostrophe sign to be deleted but everything
>> else stays the same.
>> Any suggestions on doing this would really be appreciated. Thanks.
>
> Suggestions:
> 1 - any mass rename opens you to disaster
> 2 - may not handle blanks well either
> 3 - possible solution below
>
> find . -name "*'*.wav" |
> while read item; do
> dir=${item%/*}
> oldname=${item##*/}
> newname=${oldname//\'/}
> mv "$dir/$oldname" "$dir/$newname"
> done
>
> Beware typos, I just typed that in...
>
I use a little app called "detox" for this kind of change. Works great!
I didn't find an rpm, but it's on Sourceforge.
Regards,
John
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
F13: Evolution icons - configurable?
Hello, I recently upgraded to Fedora 13, and am finding the evolution mail client icons a bit awkward. I use KDE for the desktop. I found this image on the 'net of basically what it use to look like: http://www.backuphowto.info/files/images/howto/2007/linux-screw-10-total-4-unread-evolution.png Personally I preferred the old icons, is there any way re-install them? If not, then: 1) I used to have both icons and text on the taskbar (as in the picture). Now I only have the icons. Anyway I can get both back again? 2) The icons are a bit small. Anyway to increase their size? 3) The icons are quite close together, and over to the left of the application window. As seen in the picture, the icons used to be spread along the top. Anyway to spread out the icons a bit? Thanks, John. -- John Horne, University of Plymouth, UK Tel: +44 (0)1752 587287Fax: +44 (0)1752 587001 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F13: Evolution icons - configurable?
On Tue, 2010-06-01 at 16:41 +0100, John Horne wrote: > Hello, > > I recently upgraded to Fedora 13, and am finding the evolution mail > client icons a bit awkward. I use KDE for the desktop. I found this > image on the 'net of basically what it use to look like: > http://www.backuphowto.info/files/images/howto/2007/linux-screw-10-total-4-unread-evolution.png > > Personally I preferred the old icons, is there any way re-install them? > > If not, then: > > 1) I used to have both icons and text on the taskbar (as in the > picture). Now I only have the icons. Anyway I can get both back again? > > 2) The icons are a bit small. Anyway to increase their size? > > 3) The icons are quite close together, and over to the left of the > application window. As seen in the picture, the icons used to be spread > along the top. Anyway to spread out the icons a bit? > Okay, it seems all 3 above are related. My work PC is still running F11 (until Friday), and I had a look at its Evolution settings today. Using 'gconf-editor' these 2 were set: /desktop/gnome/interface/toolbar_icons_size "large-toolbar" /desktop/gnome/interface/toolbar_style "both" Now, just by stopping/starting Evolution I could change these settings, and see the effect. If I changed the toolbar style to 'icons' and used a 'small-toolbar', then I get pretty much exactly what I have under F13. (In fact the only difference seems to be the icon for 'delete message'.) If I changed it back to a style of 'both' - that is, icons and text, and a large toolbar, then the icons are more spread out, presumably because they have to cater for the text underneath as well now. It all appears as I want it. So, at home with F13, I set both of these using gconf-editor - to use a large toolbar with both icons and text. I restarted Evolution, and nothing changed. I logged out and in; no change. I rebooted the machine; no change. Gconf-editor (and gconftool-2) shows that these values have been set. I can also seem them in my ~/.gconf/... xml file. But for some reason Evolution (and others?) is ignoring them. I'll play a bit more with this, but this seems like a bug to me. John. -- John Horne, University of Plymouth, UK Tel: +44 (0)1752 587287Fax: +44 (0)1752 587001 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F13: Evolution icons - configurable?
On Tue, 2010-06-01 at 12:28 -0430, Patrick O'Callaghan wrote: > On Tue, 2010-06-01 at 16:41 +0100, John Horne wrote: > > Hello, > > > > I recently upgraded to Fedora 13, and am finding the evolution mail > > client icons a bit awkward. I use KDE for the desktop. I found this > > image on the 'net of basically what it use to look like: > > http://www.backuphowto.info/files/images/howto/2007/linux-screw-10-total-4-unread-evolution.png > > > > Personally I preferred the old icons, is there any way re-install them? > > My specific nit is that the icons for Delete and Junk look almost identical, > causing a lot of > visual confusion. > I would agree. The F11 'delete' icon is a large red cross, completely different from the 'junk' icon, whereas all the other icons are the same as I see under F13. However, with text underneath the icons, they do get spread out a bit more. (Although getting F13 to use icons with text is proving difficult!) John. -- John Horne, University of Plymouth, UK Tel: +44 (0)1752 587287Fax: +44 (0)1752 587001 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Evolution oddities in F13
On Sat, 2010-06-05 at 22:03 -0500, Mike Chambers wrote: > On Sat, 2010-06-05 at 19:33 -0400, Matthew Saltzman wrote: > > > * The first message selected in a window doesn't change status > > from unread to read until I change it by hand. > > > > Above isn't a bug. It actually was suppose to do this same thing in F12 > but there was a bug that prevented it. But this is the way it's suppose > to work. It will change if you select on another one then come back to > it. And if there are other emails in the folder, i think it will change > status but can't remember. > But if there are no other messages in the folder, it remains as unread. That is the problem. I now have folders each with one message in them, and they are all (still!) marked as unread despite having read them all (and having set the 'mark as read after ...' option). To me that is a bug. John. -- John Horne Tel: +44 (0)1752 587287 University of Plymouth, UK Fax: +44 (0)1752 587001 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F13: screensaver problem after upgrade from F12
Kevin T. Likes wrote: > > I recently upgraded from F12 to F13 using preupgrade. Everything > seemed to go well, except for one problem I think I've traced to the > screensaver. > > When I lock the screen now at the console, I get logged out of my > session after a short period of time (a few minutes) . My first > thought was that maybe one of the screensavers was bad, so I went to > change that one I was using, but as soon as I selected another one > (not even having to hit preview), I get logged out, although it does > seem the selection is changed. I tried unlocking immediately, and it > works. If I unlock the screen after a couple of minutes, but before > the unwanted logout, the screen just goes black, and I can't get in. > The system is still running, though, since I can get in via SSH. > > I do see in /var/log/messages that is looks like Xorg is coredumping, > but I don't see anything to indicate why. > > Has anyone else had this trouble? > Yes, maybe. It has happened twice now for me. The first time I assumed I did something like tell the PC to logout rather than 'lock'. However, it happened again a few minutes ago. I had a task running, and left my PC to talk to someone else. I noticed when the screensaver kicked in, but didn't look at my PC after that. A few mins later I came back and it had logged out. I was left at the login screen. I have been able to lock and unlock the screensaver without a problem. No blank screen. I do not see anything in any of the log files. I am using the KDE 4D Hypertorus screensaver. John. -- John Horne Tel: +44 (0)1752 587287 University of Plymouth, UK Fax: +44 (0)1752 587001 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F13: screensaver problem after upgrade from F12
On Mon, 2010-06-07 at 16:27 +0100, John Horne wrote: > Kevin T. Likes wrote: > > > > I recently upgraded from F12 to F13 using preupgrade. Everything > > seemed to go well, except for one problem I think I've traced to the > > screensaver. > > > > When I lock the screen now at the console, I get logged out of my > > session after a short period of time (a few minutes) . My first > > thought was that maybe one of the screensavers was bad, so I went to > > change that one I was using, but as soon as I selected another one > > (not even having to hit preview), I get logged out, although it does > > seem the selection is changed. I tried unlocking immediately, and it > > works. If I unlock the screen after a couple of minutes, but before > > the unwanted logout, the screen just goes black, and I can't get in. > > The system is still running, though, since I can get in via SSH. > > > > I do see in /var/log/messages that is looks like Xorg is coredumping, > > but I don't see anything to indicate why. > > > > Has anyone else had this trouble? > > > Yes, maybe. It has happened twice now for me. The first time I assumed I > did something like tell the PC to logout rather than 'lock'. However, it > happened again a few minutes ago. I had a task running, and left my PC > to talk to someone else. I noticed when the screensaver kicked in, but > didn't look at my PC after that. A few mins later I came back and it had > logged out. I was left at the login screen. > > I have been able to lock and unlock the screensaver without a problem. > No blank screen. I do not see anything in any of the log files. > Wow! Spoke too soon :-) It happened again as I was talking to someone. Screensaver was running, I moved the mouse and got the 'unlock' box. Entered my password, and it just crashed, and I ended up with the login screen. In my daemon log (I filter saemon stuff to a seperate log file) I can see: Jun 7 16:46:59 jhorne abrt[11255]: saved core dump of pid 6605 (/usr/bin/Xorg) to /var/cache/abrt/ccpp-1275925617-6605.new/coredump (59949056 bytes) Jun 7 16:46:59 jhorne abrtd: Directory 'ccpp-1275925617-6605' creation detected Jun 7 16:46:59 jhorne abrtd: Crash is in database already (dup of /var/cache/abrt/ccpp-1275667541-2204) Jun 7 16:46:59 jhorne abrtd: Deleting crash ccpp-1275925617-6605 (dup of ccpp-1275667541-2204), sending dbus signal Jun 7 16:46:59 jhorne kdm[2118]: X server for display :0 terminated unexpectedly So it does look like Xorg is crashing. John. -- John Horne Tel: +44 (0)1752 587287 University of Plymouth, UK Fax: +44 (0)1752 587001 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F13: screensaver problem after upgrade from F12
On Mon, 2010-06-07 at 16:55 +0100, John Horne wrote: > On Mon, 2010-06-07 at 16:27 +0100, John Horne wrote: > > Kevin T. Likes wrote: > > > > > > I recently upgraded from F12 to F13 using preupgrade. Everything > > > seemed to go well, except for one problem I think I've traced to the > > > screensaver. > > > It seems this has been bugzilled: https://bugzilla.redhat.com/show_bug.cgi?id=601110 John. -- John Horne Tel: +44 (0)1752 587287 University of Plymouth, UK Fax: +44 (0)1752 587001 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Evolution oddities in F13
On Mon, 2010-06-07 at 15:29 -0500, Mike Chambers wrote: > On Mon, 2010-06-07 at 14:44 +0100, John Horne wrote: > > O > > But if there are no other messages in the folder, it remains as unread. > > That is the problem. I now have folders each with one message in them, > > and they are all (still!) marked as unread despite having read them all > > (and having set the 'mark as read after ...' option). To me that is a > > bug. > > In that case, right click and "mark as read". Yes it sucks that it shows > taht when only one message in the folder. If your deleting them, it > doesn't make a difference, but if your saving them, then guess it does. > Yup. I dug out your bugzilla entry and saw the response. So It seems this is in fact a feature working correctly. I guess because I had no problem with the previous action, but others did, so it seems odd to me. John. -- John Horne, University of Plymouth, UK Tel: +44 (0)1752 587287Fax: +44 (0)1752 587001 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: [F13, Nvidia] Nvidia drivers for Nvidia GF FX5200
On 06/07/2010 01:51 PM, Michael Cronenworth wrote: > A 5200FX is not remotely fast to begin with. I used to run one in a work > machine. I've since banned the lowest tier cards from my future > purchases. They aren't saving you any money when you can't be productive! True, the card isn't fast, but with the Nvidia driver mine playes 720p video perfectly, whereas with the Nouveau driver I get a stuttering, jerky mess. A well written driver can make old hardware useful, and as we all have seen with ATI, a poorly written driver can ruin great hardware. Regards, John -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
F13 doesn't let me customize install
I'm trying to upgrade an existing install and the F13 DVD didn't ask me to confirm my partitions nor did it offer to let me customize my install. What's up with that? Hopefully it's not going to wipe my system and do a fresh install! I think someone needs to fix this in the next release so that it *always* offers to customize your install! If this ruins my existing install by creating a LVM or something, I'm going to be seriously upset! The last time I had an LVM, it caused my system to crash! I don't need an LVM on my home pc! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F13 doesn't let me customize install
Quoting g : > this has been discussed already on this tsl and is a problem. > > i do not recall if there was a work around solution. > > you do have alternative of pre-upgrade and online upgrade. even this is > with problems, but does appear to have gotten better. > > so, unless your internet speed is to slow to make an online upgrade > impractical, you may well be better off using upgrade. > Well, it's kinda difficult to do when the install you *want* to upgrade won't boot. :-) I had a "failed" F12 install that I was upgrading. Since the upgrade completed, and it's not finishing the boot (freezes at the splash screen) I'm looking more and more at re-doing the F12 install. :-( > > with other problems of fedora 13 at this time, you may also, be better > off by waiting for a re-spin, or fedora 14 to be released. > Yeah. I think I might step back one version and see. > > if you really rather be on 'bleeding edge' of new technology, be ready > to bleed a little. > Well, this is the first time it's really bitten me. As I posted in response to the developers closing my bugzilla report, they need to at least warn us before installing if they aren't going to let us customize an upgrade. > > even with all the great work that is done with rawhides, first release > is and will be filled with problems. > > there just are not enough testers to test rawhide on enough different > system hardware to get all of problems worked out. > > from what i have seen of fedora from early core days, this is how it > has been, i there really is no practical way to make things different. > > Yeah... I think I'm going to step back to F12 and see if that works any better. F13 just isn't "ready for primtime" in my opinion. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F13 - goodnews and bad news
Quoting Tim : > > Very dangerous, much better to deselect all discs, and make the user > figure out which is the right disc to use. Else they stand a very good > chance of wiping out something they needed to keep. > > Providing the disc info does make it possible for you to look in the box > and identify which is the drive you've just inserted, and pick the same > one from the configuration screen. Especially so when someone puts in > two or more almost identical drives. > Hell, I'm in the same boat as the OP. I have three physical disks in the system and two of them are PATA disks. If the system at least had told me that it was seeing two PATA disks and one SATA, that would have helped, but no, all it told me was that it had three ATA disks in the system. I agree, the system should tell you more when installing! -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
missing deps on F13
Trying to keep my newly installed (update from F12) system updated and I keep running up against an unresolved dependency in compat-db.x86_64 0:4.7.25-2.fc13. Anyone know when this will be resolved? The specific error I'm getting is as follows: Error: Package: compat-db-4.7.25-2.fc13.x86_64 (fedora) Requires: compat-db45 = 4.5.20-2.fc13 Installed: compat-db45-4.5.20-5.fc10.x86_64 (@fedora/12) Available: compat-db45-4.5.20-2.fc13.x86_64 (fedora) Error: Package: compat-db-4.7.25-2.fc13.x86_64 (fedora) Requires: compat-db46 = 4.6.21-2.fc13 Installed: compat-db46-4.6.21-5.fc10.x86_64 (@fedora/12) Available: compat-db46-4.6.21-2.fc13.x86_64 (fedora) >From the looks of things, it appears that the F12 RPM is *newer* than the F13. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Upgrade to Fedora13 from Fedora 8
On Thu June 10 2010, Marvin Kosmal wrote: > HI > > I have FC12 and am thinking of going to FC13. > > Will I have the same options? > > I was thinking FC13 would overlay FC12 making it FC13... Is that not > going to happen.?? With the same partitions.. > > FC 12 is ONLY thing on drive.. > No, you can upgrade F12 to F13, no problem. The OP was trying to go from FC8 to F13. BIG difference. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: missing deps on F13
On Thu June 10 2010, Germán "A. Racca" wrote: > > What happens if you first uninstall the fc10 versions > > compat-db45-4.5.20-5.fc10.x86_64 > compat-db46-4.6.21-5.fc10.x86_64 > > and then install compat-db-4.7.25-2.fc13.x86_64 again? Maybe yum will > push the correct dependencies. > Thanks. Looks like that did it. :-) I also had another install (different hard drive) that was FC10. I'm not using F(C)10 any longer, so I had no problem removing the FC10 RPMs. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Status of SSDs under Fedora ?
On Thu, 2010-06-10 at 17:10 -0500, Michael Cronenworth wrote: > Linuxguy123 wrote: > > I'm using ext4 for that drive right now. Is there a better filesystem > > for SSDs ? > > There's a few "SSD specific" file systems, but you won't gain much in > everyday computing from switching. ext4 will be just fine. > > > > > Is there anything that I should be aware of as far as switching ? > > Nope! Fedora 13 has support for TRIM, so you don't need to worry about > anything. No tweaking, no special maintenance. Enjoy! > Yes it "has TRIM support" but is it enabled and does anything use it ? I have checked two sets of kernel documentation /linux-2.6.33.5/Documentation/filesystems/ext4.txt /linux-2.6.34/Documentation/filesystems/ext4.txt In options it says When mounting an ext4 filesystem, the following option are accepted: (*) == default ... discard Controls whether ext4 should issue discard/TRIM nodiscard(*)commands to the underlying block device when blocks are freed. This is useful for SSD devices and sparse/thinly-provisioned LUNs, but it is off by default until sufficient testing has been done. When I mount an ext4 SSD (No RAID) in F13 I see no "discard" option set, maybe the default has been changed but I doubt it. Hot-plugging my 128GB Crucial SSD shows /dev/sdb3 on /media/ssd3 type ext3 (rw,nosuid,nodev) /dev/sdb2 on /media/ssd2_ type ext4 (rw,nosuid,nodev) /dev/sdb1 on /media/ssd1 type ext3 (rw,nosuid,nodev) Partition sdb2 is "/" of a full F13 ext4 install The fstab on that ext4 F13 partition shows UUID=ededfd60-3173-40b7-b144-026143e3cbf7 / ext4 defaults 1 1 So the installer does not set "discard" A manual mount -t auto -o discard /dev/sdb2 /mnt/zip gives /dev/sdb2 on /mnt/zip type ext4 (rw,discard) I assume that setting "discard" in /etc/fstab would work - It would be highly desirable to have definitive answers to 1. Is "discard" set by default in F13? 2. How can you find what/where the default mount options are set 3. Does setting the "discard" option do everything that is required to enable TRIM to do its job with no further action? 4. Is it safe to use the "discard" option yet? 5. How do you automatically set the "discard" option when hot-plugging an SSD disk? (What controls the mount? hal, udev, XFCE, Gnome, kde, ...) I am using kdm, XFCE and probably bits of gnome John -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
