Re: Development repos accumulating prior daily builds [FIXED]
On Fri, 2021-03-05 at 12:16 -0800, Kevin Fenzi wrote: > On Fri, Mar 05, 2021 at 01:53:34PM -0600, Robert G. (Doc) Savage via > test wrote: > > > > Kevin, > > > > Thanks for submitting those PRs. Do you have a sense of when the > > scripts will actually be updated and the older files flushed? > > The scripts are updated now, but rawhide compose failed today > (due to xorg-x11-server-utils being retired and lorax still trying to > install it). > > https://github.com/weldr/lorax/issues/1117 > > as soon as that gets fixed and we get a compose the old duplicates > should go away. Kevin, My local rsync just finished up. It's a couple hundred gigs lighter. :- ) Thanks. --Doc Savage Fairview Heights, IL ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Development repos accumulating prior daily builds
On Fri, 2021-03-05 at 12:16 -0800, Kevin Fenzi wrote: > On Fri, Mar 05, 2021 at 01:53:34PM -0600, Robert G. (Doc) Savage via > test wrote: > > > > Kevin, > > > > Thanks for submitting those PRs. Do you have a sense of when the > > scripts will actually be updated and the older files flushed? > > The scripts are updated now, but rawhide compose failed today > (due to xorg-x11-server-utils being retired and lorax still trying to > install it). > > https://github.com/weldr/lorax/issues/1117 > > as soon as that gets fixed and we get a compose the old duplicates > should go away. Kevin, Thanks for the update. --Doc Savage Fairview Heights, IL ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Development repos accumulating prior daily builds
On Wed, 2021-03-03 at 19:50 -0800, Kevin Fenzi wrote: > On Wed, Mar 03, 2021 at 08:53:10PM -0600, Robert G. (Doc) Savage via > test wrote: > > Not sure if anyone here can address this minor problem, but here > > goes. > > For more than a week The top-level Fedora development repository at > > //dl.fedoraproject.org/fedora-linux-development/34 and /rawhide > > haven't > > been deleting the previous datetime versions of isos and other > > large > > files. Example: > > > > $ cd .../rawhide/Spins/x86_64/iso/ > > $ ls -al > ...snip... > > > > That's consuming a lot of unnecessary filespace. > > Good eye. :) > > It's a bug that was introduced in a recent change in the scripts that > sync rawhide and branched. ;( > > I just made some PR's to fix it: > > https://pagure.io/pungi-fedora/pull-request/1014 > https://pagure.io/pungi-fedora/pull-request/1015 > > as soon as those get reviewed this should get fixed. > > Thanks for noting it! Kevin, Thanks for submitting those PRs. Do you have a sense of when the scripts will actually be updated and the older files flushed? --Doc Savage Fairview Heights, IL ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Development repos accumulating prior daily builds
Not sure if anyone here can address this minor problem, but here goes. For more than a week The top-level Fedora development repository at //dl.fedoraproject.org/fedora-linux-development/34 and /rawhide haven't been deleting the previous datetime versions of isos and other large files. Example: $ cd .../rawhide/Spins/x86_64/iso/ $ ls -al total 67072371 -rw-r--r--. 1 nobody nobody 2164260864 Feb 23 18:31 Fedora-Cinnamon- Live-x86_64-Rawhide-20210223.n.1.iso -rw-r--r--. 1 nobody nobody 2164260864 Feb 25 02:47 Fedora-Cinnamon- Live-x86_64-Rawhide-20210225.n.0.iso -rw-r--r--. 1 nobody nobody 2164260864 Feb 26 02:32 Fedora-Cinnamon- Live-x86_64-Rawhide-20210226.n.0.iso -rw-r--r--. 1 nobody nobody 2162147328 Feb 27 02:35 Fedora-Cinnamon- Live-x86_64-Rawhide-20210227.n.0.iso -rw-r--r--. 1 nobody nobody 2164260864 Feb 28 02:26 Fedora-Cinnamon- Live-x86_64-Rawhide-20210228.n.0.iso -rw-r--r--. 1 nobody nobody 2118221824 Feb 22 02:01 Fedora-KDE-Live- x86_64-Rawhide-20210222.n.0.iso -rw-r--r--. 1 nobody nobody 2126544896 Feb 23 18:47 Fedora-KDE-Live- x86_64-Rawhide-20210223.n.1.iso -rw-r--r--. 1 nobody nobody 2126544896 Feb 25 02:47 Fedora-KDE-Live- x86_64-Rawhide-20210225.n.0.iso -rw-r--r--. 1 nobody nobody 2126544896 Feb 26 02:37 Fedora-KDE-Live- x86_64-Rawhide-20210226.n.0.iso -rw-r--r--. 1 nobody nobody 2126544896 Feb 27 02:35 Fedora-KDE-Live- x86_64-Rawhide-20210227.n.0.iso -rw-r--r--. 1 nobody nobody 2126544896 Feb 28 02:36 Fedora-KDE-Live- x86_64-Rawhide-20210228.n.0.iso -rw-r--r--. 1 nobody nobody 1366327296 Feb 22 01:59 Fedora-LXDE-Live- x86_64-Rawhide-20210222.n.0.iso -rw-r--r--. 1 nobody nobody 1377550336 Feb 23 18:33 Fedora-LXDE-Live- x86_64-Rawhide-20210223.n.1.iso -rw-r--r--. 1 nobody nobody 1377550336 Feb 25 02:30 Fedora-LXDE-Live- x86_64-Rawhide-20210225.n.0.iso -rw-r--r--. 1 nobody nobody 1376190464 Feb 26 02:36 Fedora-LXDE-Live- x86_64-Rawhide-20210226.n.0.iso -rw-r--r--. 1 nobody nobody 1375731712 Feb 27 02:34 Fedora-LXDE-Live- x86_64-Rawhide-20210227.n.0.iso -rw-r--r--. 1 nobody nobody 1377550336 Feb 28 02:22 Fedora-LXDE-Live- x86_64-Rawhide-20210228.n.0.iso -rw-r--r--. 1 nobody nobody 1455341568 Feb 23 18:42 Fedora-LXQt-Live- x86_64-Rawhide-20210223.n.1.iso -rw-r--r--. 1 nobody nobody 1455341568 Feb 25 02:33 Fedora-LXQt-Live- x86_64-Rawhide-20210225.n.0.iso -rw-r--r--. 1 nobody nobody 1453916160 Feb 26 02:34 Fedora-LXQt-Live- x86_64-Rawhide-20210226.n.0.iso -rw-r--r--. 1 nobody nobody 1453916160 Feb 27 02:33 Fedora-LXQt-Live- x86_64-Rawhide-20210227.n.0.iso -rw-r--r--. 1 nobody nobody 1453916160 Feb 28 02:32 Fedora-LXQt-Live- x86_64-Rawhide-20210228.n.0.iso -rw-r--r--. 1 nobody nobody 2172518400 Feb 23 18:47 Fedora-MATE_Compiz- Live-x86_64-Rawhide-20210223.n.1.iso -rw-r--r--. 1 nobody nobody 2172518400 Feb 25 02:39 Fedora-MATE_Compiz- Live-x86_64-Rawhide-20210225.n.0.iso -rw-r--r--. 1 nobody nobody 2172518400 Feb 26 02:32 Fedora-MATE_Compiz- Live-x86_64-Rawhide-20210226.n.0.iso -rw-r--r--. 1 nobody nobody 2172518400 Feb 27 02:41 Fedora-MATE_Compiz- Live-x86_64-Rawhide-20210227.n.0.iso -rw-r--r--. 1 nobody nobody 2172518400 Feb 28 02:26 Fedora-MATE_Compiz- Live-x86_64-Rawhide-20210228.n.0.iso -rw-r--r--. 1 nobody nobody 1093238784 Feb 22 01:57 Fedora-SoaS-Live- x86_64-Rawhide-20210222.n.0.iso -rw-r--r--. 1 nobody nobody 1099726848 Feb 23 18:29 Fedora-SoaS-Live- x86_64-Rawhide-20210223.n.1.iso -rw-r--r--. 1 nobody nobody 1099726848 Feb 25 02:28 Fedora-SoaS-Live- x86_64-Rawhide-20210225.n.0.iso -rw-r--r--. 1 nobody nobody 1098645504 Feb 26 02:29 Fedora-SoaS-Live- x86_64-Rawhide-20210226.n.0.iso -rw-r--r--. 1 nobody nobody 1098645504 Feb 27 02:22 Fedora-SoaS-Live- x86_64-Rawhide-20210227.n.0.iso -rw-r--r--. 1 nobody nobody 1098645504 Feb 28 02:27 Fedora-SoaS-Live- x86_64-Rawhide-20210228.n.0.iso -rw-r--r--. 1 nobody nobody 774 Feb 22 03:48 Fedora-Spins-Rawhide- x86_64-20210222.n.0-CHECKSUM -rw-r--r--. 1 nobody nobody 1378 Feb 23 23:17 Fedora-Spins-Rawhide- x86_64-20210223.n.1-CHECKSUM -rw-r--r--. 1 nobody nobody 1378 Feb 25 07:01 Fedora-Spins-Rawhide- x86_64-20210225.n.0-CHECKSUM -rw-r--r--. 1 nobody nobody 1378 Feb 26 07:11 Fedora-Spins-Rawhide- x86_64-20210226.n.0-CHECKSUM -rw-r--r--. 1 nobody nobody 1568 Feb 27 06:08 Fedora-Spins-Rawhide- x86_64-20210227.n.0-CHECKSUM -rw-r--r--. 1 nobody nobody 1568 Mar 2 11:10 Fedora-Spins-Rawhide- x86_64-20210228.n.0-CHECKSUM -rw-r--r--. 1 nobody nobody 1666252800 Feb 22 02:00 Fedora-Xfce-Live- x86_64-Rawhide-20210222.n.0.iso -rw-r--r--. 1 nobody nobody 1672806400 Feb 23 18:37 Fedora-Xfce-Live- x86_64-Rawhide-20210223.n.1.iso -rw-r--r--. 1 nobody nobody 1672806400 Feb 25 02:32 Fedora-Xfce-Live- x86_64-Rawhide-20210225.n.0.iso -rw-r--r--. 1 nobody nobody 1672806400 Feb 26 02:35 Fedora-Xfce-Live- x86_64-Rawhide-20210226.n.0.iso -rw-r--r--. 1 nobody nobody 1671168000 Feb 27 02:26 Fedora-Xfce-Live- x86_64-Rawhide-20210227.n.0.iso -rw-r--r--. 1 nobody nobody 1671168000 Feb 28 02:34 Fedora-Xfce-Live- x86_64-Rawhide-20210228.n.0.iso -rw-r--r--. 1 nobody nobody
Re: Unable to boot on Raspberry Pi 4B
Sam, Thanks for your response. Note, however, that this info is "as of" almost a year ago. Has any progress been made since then? The only remotely possible way I know of to install Fedora on a P4B is to follow the complex instructions at https://medium.com/ironhaul/installing-64-bit-fedora-on-the-raspberry-pi-4-d4a665ea65d3. Unfortunately it requires a very heavy prerequisite: learning Ansible. --Doc SavageFairview Heights, IL On Fri, 2020-10-09 at 00:00 -0700, Samuel Sieb wrote: > On 10/8/20 10:05 PM, Robert G. (Doc) Savage via test wrote: > > This is a fairly harsh response. If you really meant to say > > "Never", please elaborate. What is the issue? The P4B is an > > important product, potentially one that will establish ARM as a > > valid desktop and small server option. For Fedora to support P3B+ > > and then reject its successor without explanation is curious. > > https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_4 > ___test mailing list -- > test@lists.fedoraproject.org > To unsubscribe send an email to test-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/test@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Unable to boot on Raspberry Pi 4B
This is a fairly harsh response. If you really meant to say "Never", please elaborate. What is the issue? The P4B is an important product, potentially one that will establish ARM as a valid desktop and small server option. For Fedora to support P3B+ and then reject its successor without explanation is curious. --Doc SavageFairview Heights, IL On Wed, 2020-09-30 at 07:08 -0500, Klein Kravis wrote: > For the foreseeable future Fedora wi not run on Raspberry Pi 4. > Please try a 3B+ > > > On Sep 30, 2020, 7:07 AM -0500, Ashish Kumar > , wrote: > > > > > > > > > > > > > > > > > > > > > Hi, > > > > I am trying to boot Fedora IoT aarch64 images on my Raspberry Pi 4B > > but failing to do so as I see an error that EFI was unable to load > > the image. I have tried using the raw images of the current 32 IoT > > and 33 Pre-release IoT. Please tell me where I am going wrong. > > > > > > > > > > > > > > > > > > > > > > ___ > > > > test mailing list -- test@lists.fedoraproject.org > > > > To unsubscribe send an email to test-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/test@lists.fedoraproject.org > > > > > ___test mailing list -- > test@lists.fedoraproject.org > To unsubscribe send an email to test-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/test@lists.fedoraproject.org ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Re: Exciting news
On Sat, 2020-02-15 at 22:23 -0500, David wrote: > I am not the sharpest tool in the shed, but I resolved my Rawhide > update problem > all on my own. > > The trick was to first run "dnf install redhat-rpm-config" > > I think that is all there was too it. > > I installed a lot of packages manually, but I do not think that was > necessary. > > My Rawhide install now has about seventy fc33 packages. And > lots of the > anaconda packages seemed to clear out. > > Everything installed !! > > I am too scared to reboot.But probably will anyways. > > I am curious now whether my system will say I am on Fedora 33, if > it reboots successfully ?? > > David Locklear > Fedora Rawhide Novice Level 0.0.0.2 > Arcola, Texas USA > David, If you want a simple way to see exactly what kernel you're running, type: uname -a If you want to know the familiar name of the OS you are running, type: cat /etc/fedora-release If you REALLY want to get fancy, edit your /etc/bashrc file using vim or equivalent editor. Look for the following three lines about 52 lines into the file: # Turn on checkwinsizeshopt -s checkwinsize[ "$PS1" = "\\s- \\v\\\$ " ] && PS1="[\u@\h \W]\\$ " Replace the third line with this: [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="\n\\033[1;31m`cat /etc/redhat- release`\n\\033[1;34m`date +%A` - `date +%B` `date +%d`, `date +%Y` \\033[0;32m\t `date +%Z`\n\033[0;36m[\u@\h:\l] \\033[1;33m\w\\033[0;37m\n\\$ " (Make sure you use back ticks rather than single quotes.) This will give you a complex colorful multi-line xterm prompt that will dress up your terminal sessions. If you like running Rawhide simply because it has a cool name, you should probably have heeded your mother's warning not to run with scissors. I've been using Fedora since its initial release, and Red Hat Linux before that. I remember the wreckage in the early days when I (ignorantly) tried installing every (!) package in what was then Rawhide. Talk about your major train wreck. I eventually learned to install development versions of Fedora (starting with the Beta release) only in a VM so any serious oops wouldn't destroy my day-to-day working files in /home. It's up to you, of course. Just a bit of no-cost advise from a long- time user to a new guy. --Doc Savage Fairview Heights, IL ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
[Fwd: Two package dependency problems in F30 during updates.]
Ed Greshko suggested I forward this to the test group rather than users since F30 has not yet formally been released. I'm seeing two package collissions that dnf/yum updates can't resolve. Forwarded message: Not sure F30 is supported yet, but there's apparently a couple of dependency problems with glassfish-jax-rs-api and eclipse-linuxtools-dockeras currently released. I installed F30 from the MATE_Compiz spin. Things went fine for a couple of weeks until this happened a couple of days ago: # yum -y update --skip-broken RPM Fusion for Fedora 30 - Free tainted 66 kB/s | 71 kB 00:01 Failed to synchronize cache for repo 'rpmfusion-free-tainted' RPM Fusion for Fedora 30 - Nonfree tainted 76 kB/s | 71 kB 00:00 Failed to synchronize cache for repo 'rpmfusion-nonfree-tainted' Ignoring repositories: rpmfusion-free-tainted, rpmfusion-nonfree-tainted Last metadata expiration check: 0:14:23 ago on Wed 13 Mar 2019 08:15:31 PM CDT. Dependencies resolved. Problem 1: package eclipse-linuxtools-docker-7.1.0-3.fc30.noarch requires osgi(javax.ws.rs-api), but none of the providers can be installed - cannot install both glassfish-jax-rs-api-2.1.5-3.fc30.noarch and glassfish-jax-rs-api-2.0.1-8.fc30.noarch - cannot install both glassfish-jax-rs-api-2.0.1-8.fc30.noarch and glassfish-jax-rs-api-2.1.5-3.fc30.noarch - cannot install the best update candidate for package glassfish-jax-rs-api-2.0.1-8.fc30.noarch - cannot install the best update candidate for package eclipse-linuxtools-docker-7.1.0-3.fc30.noarch Problem 2: problem with installed package eclipse-linuxtools-docker-7.1.0-3.fc30.noarch - package eclipse-linuxtools-docker-7.1.0-3.fc30.noarch requires osgi(javax.ws.rs-api), but none of the providers can be installed - cannot install both glassfish-jax-rs-api-2.1.5-3.fc30.noarch and glassfish-jax-rs-api-2.0.1-8.fc30.noarch - cannot install both glassfish-jax-rs-api-2.0.1-8.fc30.noarch and glassfish-jax-rs-api-2.1.5-3.fc30.noarch - package jersey-2.28-1.fc30.noarch requires mvn(jakarta.ws.rs:jakarta.ws.rs-api), but none of the providers can be installed - cannot install the best update candidate for package jersey-2.23.2-6.fc30.noarch Package Arch Version Repository Size Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): glassfish-jax-rs-api noarch 2.1.5-3.fc30 updates-testing 143 k Skipping packages with broken dependencies: jersey noarch 2.28-1.fc30 updates-testing 2.5 M Transaction Summary Skip 2 Packages Nothing to do. Complete! By adding the two suggested command line arguments, I get a slightly different output: # yum -y update --skip-broken --best --allowerasing RPM Fusion for Fedora 30 - Free tainted 70 kB/s | 71 kB 00:01 Failed to synchronize cache for repo 'rpmfusion-free-tainted' RPM Fusion for Fedora 30 - Nonfree tainted 148 kB/s | 71 kB 00:00 Failed to synchronize cache for repo 'rpmfusion-nonfree-tainted' Ignoring repositories: rpmfusion-free-tainted, rpmfusion-nonfree-tainted Last metadata expiration check: 0:15:12 ago on Wed 13 Mar 2019 08:15:31 PM CDT. Error: Problem: cannot install the best update candidate for package eclipse-linuxtools-docker-7.1.0-3.fc30.noarch - problem with installed package eclipse-linuxtools-docker-7.1.0-3.fc30.noarch - package eclipse-linuxtools-docker-7.1.0-3.fc30.noarch requires osgi(javax.ws.rs-api), but none of the providers can be installed - cannot install the best update candidate for package glassfish-jax-rs-api-2.0.1-8.fc30.noarch - cannot install both glassfish-jax-rs-api-2.1.5-3.fc30.noarch and glassfish-jax-rs-api-2.0.1-8.fc30.noarch - cannot install both glassfish-jax-rs-api-2.0.1-8.fc30.noarch and glassfish-jax-rs-api-2.1.5-3.fc30.noarch Does this look untangleable to anyone? v/r Robert G. (Doc) Savage Fairview Heights IL --- Begin Message --- Not sure F30 is supported yet, but there's apparently a couple of dependency problems with glassfish-jax-rs-api and eclipse-linuxtools-dockeras currently released. I installed F30 from the MATE_Compiz spin. Things went fine for a couple of weeks until this happened a couple of days ago: # yum -y update --skip-broken RPM Fusion for Fedora 30 - Free tainted 66 kB/s | 71 kB 00:01 Failed to synchronize cache for repo 'rpmfusion-free-tainted' RPM Fusion for Fedora 30 - Nonfree tainted
Managing virtualization in F30_MATE-Compiz
i've installed the F30_MATE-Compiz live spin to my system. Pretty much the whole enchilada -- 4820 packages. I noticed that virtualization support does not appear under the Applications > System Tools menu. Indeed the System Tools lists only A packet generator to Midnight Commander. System apps beginning with N-Z don't appear on the list, which does not scroll by the way. I can Add an application to the top tool bar for Virtual Machine Manager, but that appears to be the only way to access it. It also seems to be having some stability problems of its own. Has anyone else noted this missing menu behavior. Is it "normal" or should I file a bug? V/R --Doc Savage Fairview Heights, IL ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-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/test@lists.fedoraproject.org
SPARC keys
Is there a reason why the F15 Alpha release contains keys for SPARC in the i386/os and x86_64/os directories, and on the DVD iso images? --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Serial Mouse in Fedora
On Sat, 2011-03-05 at 08:28 -0800, Adam Williamson wrote: On Sat, 2011-03-05 at 06:49 -0800, Chuck Forsberg WA7KGX N2469R wrote: The computers I am trying to get Fedora running on do not have accessible USB ports and only one ps/2 connector. Can't you get little breakout connectors that let you connect a mouse and keyboard to one PS/2 port? I'm sure I've seen those somewhere. Should work Chuck: http://www.amazon.com/PS2-adapter-keyboard-mou-PS2-ADAPTER/dp/B003Z31N8W --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: big f14 iso ?
On Fri, 2010-12-31 at 08:46 +0200, cornel panceac wrote: omg, i only looked at the size (and name). i apologize for the noise, thank you for assistance. Cornel, I think we're all chuckling a bit in your embarassment. Most of us have done something similar -- and recently. We're human. Happy New Year. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: big f14 iso ?
On Thu, 2010-12-30 at 22:44 +0200, cornel panceac wrote: anybody knows what is this 6.9 GB f14 (?) iso? http://torrent.cs.pub.ro/download/fedora14-iso-i386.torrent Cornel, Can you provide any additional context info about it? I'd rather not have to download that much only to find it's a modified copy of, say, the Fedora-14-Live-multi.iso. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: big f14 iso ?
On Thu, 2010-12-30 at 23:43 +0200, cornel panceac wrote: 2010/12/30 Robert G. (Doc) Savage dsav...@peaknet.net On Thu, 2010-12-30 at 22:44 +0200, cornel panceac wrote: anybody knows what is this 6.9 GB f14 (?) iso? http://torrent.cs.pub.ro/download/fedora14-iso-i386.torrent Cornel, Can you provide any additional context info about it? I'd rather not have to download that much only to find it's a modified copy of, say, the Fedora-14-Live-multi.iso. --Doc Savage Fairview Heights, IL i find it here: http://www.fedoraproject.ro/download i have no idea what it is or if it's an official fedora spin. as i see here, http://alt.fedoraproject.org/pub/alt/mega-dvd-test/Fedora-14-Live-multi/ this iso is 5.2 GB, so i'd say it's not it. Cornel, Since the official F14 i386 iso is only 3.4GB, I'll guess that the 6.9GB iso on the Romanian site may be a local build of some sort. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What is this mega-dvd-test?
On Sun, 2010-10-31 at 01:50 -0400, Scott Robbins wrote: On Sun, Oct 31, 2010 at 12:14:07AM -0500, Robert G. (Doc) Savage wrote: Like you, I'm running into trouble with livecd-iso-to-disk. I'm seeing a couple of different problems: Waiting for devices to settle... mkdosfs 3.0.9 (31 Jan 2010) mount: you must specify the filesystem type Cleaning up to exit... umount: /media/cdtmp.6Ci76u: not mounted This is on a fully-updated 32-bit F13 system, attempting to write the image to an 8GB USB drive formatted to FAT-32. Doesn't FAT32 have a 4 GB limit on file size? Scott, It may, but that's moot. l-i-t-d does that formatting, and it's not a user option. l-i-t-d should also specify a filesystem type for mount, but it's not doing that right either. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What is this mega-dvd-test?
On Sun, 2010-10-31 at 12:48 -0500, Bruno Wolff III wrote: On Sun, Oct 31, 2010 at 05:03:30 -0500, Robert G. (Doc) Savage dsav...@peaknet.net wrote: It may, but that's moot. l-i-t-d does that formatting, and it's not a user option. l-i-t-d should also specify a filesystem type for mount, but it's not doing that right either. Normally you don't need to specify a file system for a mount. Mount can detect what type it should be, and use the correct handler. When you get that message usually something is messed up with the filesystem. Bruno, I think I found at least part of the problem here. The Downloads directory in my home folder is bind mounted to an NFS filesystem on an RHEL5 server. For some reason the iso file is being severely truncated by that NFS filesystem: Here's the original file in a 1.1TB ext3 filesystem: Red Hat Enterprise Linux Server release 5.5 (Tikanga) Sunday - October 31, 2010 17:16:56 CDT [...@lion] /pub/fedora/linux/releases/14/Live $ ls -l total 5463812 -rw--- 1 doc doc950 Oct 21 09:17 Fedora-14-Live-multi-CHECKSUM -rw--- 1 doc doc 5589458944 Oct 21 10:06 Fedora-14-Live-multi.iso drwxrwxr-x 2 doc doc 4096 Oct 26 20:02 i386 drwxrwxr-x 2 doc doc 4096 Oct 26 20:02 x86_64 Here's the NFS-exported version as seen on the F13 system, the one running l-i-t-d: Fedora release 13 (Goddard) Sunday - October 31, 2010 16:55:17 CDT [...@tiger] /net/lion/pub/fedora/linux/releases/14/Live $ ls -l total 5463812 -rw--- 1 doc doc950 Oct 21 09:17 Fedora-14-Live-multi-CHECKSUM -rw--- 1 doc doc 1294491648 Oct 21 10:06 Fedora-14-Live-multi.iso drwxrwxr-x 2 doc doc 4096 Oct 26 20:02 i386 drwxrwxr-x 2 doc doc 4096 Oct 26 20:02 x86_64 Curiously, the difference in file sizes is precisely 4GB. Is this a bug, or normal behavior for NFS? --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: What is this mega-dvd-test?
On Thu, 2010-10-28 at 08:32 -0400, Richard Ryniker wrote: Fedora-14-Live-multi.iso is too large (5.2 gigabytes) for a normal DVD with capacity of 4.7 gigabytes or so. Aha! It must be intended for a USB flash drive with capacity of 8GB or greater... [r...@ryniker ryniker]# cmd/livecd-iso-to-disk --format --reset-mbr --overlay-size-mb 1024 --home-size-mb 1024 --unencrypted-home fedora/F14/Fedora-14-Live-multi.iso /dev/sdh1 Verifying image... /home/ryniker/fedora/F14/Fedora-14-Live-multi.iso: Could not get pvd data Unable to read the disc checksum from the primary volume descriptor. This probably means the disc was created without adding the checksum.Are you SURE you want to continue? Press Enter to continue or ctrl-c to abort WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdh!!! Press Enter to continue or ctrl-c to abort Waiting for devices to settle... mkdosfs 3.0.1 (23 Nov 2008) ERROR: /home/ryniker/fedora/F14/Fedora-14-Live-multi.iso does not appear to be a Live image or DVD installer. Cleaning up to exit... [r...@ryniker ryniker]# [snip] Richard, I burned this oversized iso image to an 8.5GB DVD+R(DL) disc, then used it to successfully boot a 64-bit laptop with a BluRay drive. It displays a grub menu with (I think) sixteen separate entries. Like you, I'm running into trouble with livecd-iso-to-disk. I'm seeing a couple of different problems: # livecd-iso-to-disk --format --reset-mbr /home/doc/Downloads/Fedora-14-Live-multi.iso /dev/sdc Verifying image... /home/doc/Downloads/Fedora-14-Live-multi.iso: Could not get pvd data Unable to read the disc checksum from the primary volume descriptor. This probably means the disc was created without adding the checksum.Are you SURE you want to continue? Press Enter to continue or ctrl-c to abort WARNING: THIS WILL DESTROY ANY DATA ON /dev/sdc!!! Press Enter to continue or ctrl-c to abort Warning: The resulting partition is not properly aligned for best performance. Waiting for devices to settle... mkdosfs 3.0.9 (31 Jan 2010) mount: you must specify the filesystem type Cleaning up to exit... umount: /media/cdtmp.6Ci76u: not mounted This is on a fully-updated 32-bit F13 system, attempting to write the image to an 8GB USB drive formatted to FAT-32. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Another Release Candidate?
Will there be an F14 Release Candidate 2 between now and Tuesday? --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: !! NVIDIA WORKS !!!
On Fri, 2010-10-15 at 13:17 -0400, Scott Robbins wrote: On Fri, Oct 15, 2010 at 11:09:21AM -0500, Jim Bennett wrote: How do you boot into text mode. I have used linux a long time but I don't know how do that. Change the runlevel to 3. I'm not sure if systemd will change this, but at present, edit /etc/inittab and find the line that says id:5:initdefault: Change that 5 to a 3. Or to boot into text mode just once: * Press ESC to interrupt grub boot-up * Arrow to the kernel of your choice (usually the top one) * Press E to edit that stanza * Arrow down to the kernel ... line * Press E to edit that line * Append 3 (that's space-3 without the dash or quotes) to the line * Press ENTER to quit edit mode * Press B to resume the boot. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Booting Rawhide to text mode
On Fri, 2010-10-15 at 11:14 -0700, Chuck Forsberg WA7KGX N2469R wrote: Edit the appropriate boot command line to change rhgb quiet to 2 when you get the grub boot display. 3 will give you text + networking. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
TC1.1 Live CD - ATI Rage Mobility chipset missing in R128 driver
I've just made and booted an i686 TC1.1 Live CD for my old 32-bit Thinkpad A22p w/ATI video and 1600x1200 screen. As I expected, the video display is torn into vertical stripes starting about 2/3 of the way across (old problem). This can only be corrected with a manually-created xorg.conf file (copy attached) on a fully-installed system. Curiously, an Alt-PrtSc snapshot copied to another system does not show the tears. The only new thing I see that isn't working correctly is the screen resolution. It boots up as an Unknown monitor at 1280x1024. There's no system-config-display utility to change it to 1600x1200. lspci correctly identifies my ATI video chipset: [r...@localhost ~] lspci | grep ATI 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x [rev 02] Somehow that particular version has never been included in the R128 driver's list of chipsets. The closest match in /var/log/Xorg.0.log is: ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP) A few lines later in Xorg.0.log the LCD panel is correctly detected: [ 318.256] (**) R128(0): Using flat planel for display [ 318.257] (II) R128(0): Primary Display == Type 2 [ 318.257] (II) R128(0): Panel size: 1600x1200 [ 318.257] (II) R128(0): Panel ID: LG.PHILIPS LP150U1-A2 [ 318.257] (II) R128(0): Panel Type: Color, Single, TFT [ 318.257] (II) R128(0): Panel Interface: LVDS Yet the desktop still comes up in 1280x1024, the highest resolution available with System - Preferences - Monitors. It's being prevented from using 1600x1200 by the default hsync: [ 318.280] (II) R128(0): default monitor: Using hsync range of 31.50-74.01 kHz ... [ 318.284] (II) R128(0): Not using default mode 1600x1200 (hsync out of range) ... [ 318.285] (II) R128(0): Not using default mode 1600x1200 (hsync out of range) ... [ 318.289] (**) R128(0): *Default mode 1280x1024: 162.0 MHz (scaled from 108.0 MHz), 60.0 kHz, 60.0 Hz [ 318.289] (II) R128(0): Modeline 1280x1024x60.0 1280 1344 1368 1840 1024 1026 1029 1074 +hsync +vsync (64.0 kHz) How does one go about getting the R128 driver updated to include the M3 AGP 2x [rev 02] chipset? --Doc Savage Fairview Heights, IL Section Device Identifier Videocard0 Driver r128 EndSection Section Monitor Identifier Monitor0 VendorName IBM ModelName Thinkpad A22p DisplaySize 305 229 # 1600x1200 @ 60.00 Hz (GTF) hsync: 74.52 kHz; pclk: 160.96 MHz Modeline 1600x1200 60.00 160.96 1600 1704 1880 2160 1200 1201 1204 1242 -HSync +Vsync EndSection Section Screen Identifier Screen0 Device Videocard0 Monitor Monitor0 Subsection Display Viewport0 0 Depth 24 Modes 1600x1200 EndSubSection EndSection -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: TC1.1 Live CD - ATI Rage Mobility chipset missing in R128 driver
On Thu, 2010-10-14 at 10:34 -0400, Adam Jackson wrote: Try this driver build: http://kojipkgs.fedoraproject.org/packages/xorg-x11-drv-r128/6.8.1/5.fc15/ Download that on the live system, install it, and then log out of X and back in so the server will restart and pick up the new driver. Adam, Thanks for the suggestion, but no joy. I booted the Live CD to runlevel 3, logged in as root, scp'd the new driver from a neighbor system, installed it using 'yum localinstall...', then ran init 5. The same tearing distorts the screen even with the new 6.8.1-5 driver. You said X drivers don't consider PCI revision, only vendor and device ID. At http://www.pcidatabase.com/vendor_details.php?id=240 I find two devices with Chip Number Mobility M3 AGP: 0x4C45 Chip Description: Rage Mobility M3 AGP 0x4C46 Chip Number:Mobility M3 AGP Chip Description: 0x4c46 Notes: DRIVER In /usr/share/hwdata/pci.ids I found: 4c45 Rage Mobility M3 AGP 4c46 Rage Mobility M3 AGP 2x 1002 0155 IBM Thinkpad A22p 1014 0155 IBM Thinkpad A22p 1028 00b1 Latitude C600 Do you suppose the aty128fb.ko kernel driver contains the correct parameter info for one of the device numbers but not the other (e.g. 1002 but not 1014)? The display tearing problem I'm seeing goes back a long time (prior to F7 for sure). Could we have been missing half a loaf all this time? James MacKenzie has experienced the same problem on his A22p. The only solution I've found is the xorg.conf file I attached to my first msg. Before I hacked that together I had to use the VESA driver, which is now abominably slow. A key number in my xorg.conf file is the hsync value found by the gtf utility: 74.52 kHz. That's 501 Hz higher than the default value listed in Xorg.0.log. The difference is blocking a 1600x1200 display. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fedora 14 under constant load
On Thu, 2010-10-14 at 16:29 -0700, John Poelstra wrote: Compared to Fedora 13 and Fedora 12, I'm noticing that on my Dell XPS M1330 laptop, the system is under a load average of 1.0+ at all times... even with no desktop applications open. Naturally this makes it run hotter and shortens the battery life. Are other people seeing this? How to diagnose further beyond 'top' or system monitor? John, I'll bet it's beagle. Useless POS kills my laptops. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: 64bit Flash Player! Must Read!!!
On Sat, 2010-10-02 at 10:33 +0200, Guido Grazioli wrote: On Fri, 2010-10-01 at 15:12 -0700, Rob Healey wrote: I had problems with this release as well until I found and renamed several nswrapper_XX_XX.libflashplayer.so files to so.save and restarted Firefox. I think you could just edit /etc/sysconfig/nspluginwrapper , adding :libflashplayer* to IGNORE_WRAP Ahhh. That's how it's done. Thanks, Guido. --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: bizarre yum
On Thu, 2010-08-12 at 11:51 -0600, Michal Jaegermann wrote: It appears that alchemist is gone in F14. It was installed by default previously and it depends on python 2.6 and seemingly noting obsoletes it or provides something to satisfy dependencies and/or force a replacement. Most likely more people doing updates of that sort will bump into the issue. Michal, That rings a bell. A fix to system-config-http in May might have removed the last requirement for alchemist. See https://bugzilla.redhat.com/show_bug.cgi?id=528638#c12 --Doc Savage Fairview Heights, IL -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
