Re: resurrecting old laptops
On Mon, May 23, 2022 at 12:07 PM Andras Simon wrote: > 2022-05-23 16:59 UTC+02:00, jim.cro...@gmail.com : > > [...] > > I have used fedora-live-usb to rescue machines > > in the past, but Im running out of options. > > I would welcome other distro suggestions for tired old hardware > > https://www.lxle.net works for me on a netbook from around 2008. > nice screenshots. I like the "prudent" selection of apps. I might have to try it on the next box. > > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: resurrecting old laptops
On Mon, May 23, 2022, 10:53 AM José María Terry Jiménez wrote: > El 23/5/22 a las 16:59, jim.cro...@gmail.com escribió: > > > > so Ive got some old i686 computers, > > electronics recycle day approaches, but before I do that, > > I thought Id try to get them working > > > > 1st one (toshiba satellite core2 laptop) threw a hard-drive, > > clunking noises, then finally falls back to pxe-boot. > > > > I put fedora-30-live on a usb (last one with i686 support) > > but booting it, I get a 2-line error: > > > > This kernel requires x86-64, but only detected i686 > > unable to boot - ... > > > > I know f30 supports i686 - I have 1 old desktop still running it. > > > > next is hp pavilion g7 > > pressing power gives brief spin-up of fans, nothing else. > > f2, f10, esc during boot dont help, > > screen brightness or vga monitor dont help either > > I pulled hard drive and memory to force BIOS / POST > > to do something different, NO CHANGE. > > Any suggestions? > > > > but at least I have a new/old hard-drive for the toshiba. > > > > I also have a dell pentium2-233, > > running knoppix with a 2.6.19 kernel, > > its reluctant to do anything (aptitude is trying forever) > > I think its too old to have a bios that can usb boot > > > > I have used fedora-live-usb to rescue machines > > in the past, but Im running out of options. > > I would welcome other distro suggestions for tired old hardware > > > > thanks > > > Hello > > Last release for i686 (i386) is Fedora 25. I've checked the repo. Here > are the downloads. Note that 26 and following only is available in x86_64 > > Yes I'll accept that I have an old 686 desktop thats still running F30, when they finally abandoned the updates. Its running a 5.16-rc4 kernel now :-) video resolution on distro kernel dropped to VGA quality at some point, I had to do something ;-) I ended up putting Bodhi Linux on the toshiba laptop cuz it targets low-mem, low-disk, slow-cpu machines, like these old machines I have lying around. > ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
resurrecting old laptops
so Ive got some old i686 computers, electronics recycle day approaches, but before I do that, I thought Id try to get them working 1st one (toshiba satellite core2 laptop) threw a hard-drive, clunking noises, then finally falls back to pxe-boot. I put fedora-30-live on a usb (last one with i686 support) but booting it, I get a 2-line error: This kernel requires x86-64, but only detected i686 unable to boot - ... I know f30 supports i686 - I have 1 old desktop still running it. next is hp pavilion g7 pressing power gives brief spin-up of fans, nothing else. f2, f10, esc during boot dont help, screen brightness or vga monitor dont help either I pulled hard drive and memory to force BIOS / POST to do something different, NO CHANGE. Any suggestions? but at least I have a new/old hard-drive for the toshiba. I also have a dell pentium2-233, running knoppix with a 2.6.19 kernel, its reluctant to do anything (aptitude is trying forever) I think its too old to have a bios that can usb boot I have used fedora-live-usb to rescue machines in the past, but Im running out of options. I would welcome other distro suggestions for tired old hardware thanks ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DRPM performance ?
On Wed, Feb 2, 2022 at 8:52 AM wrote: > > so a couple of weeks ago, > I did a dnf update, and got ~ 19% reduction due to DRPM > > that was by far the highest return on the effort Id seen. > previous experience for me was 1-4%. > I should have grabbed a "screenshot" and sent it here. > > Whats the "average" experience here ? > are there statistics ? > do *noarch 's do better ? > > how often do you see some version of "find/download failed" ? > (it sometimes appears to be a cached-version problem, > particularly if the update is older than a few days) One more data-point: I got 36% saved this morning. 7/10 packages were drpm'd that seems worth having, esp for the servers. Last metadata expiration check: 0:09:04 ago on Mon 11 Apr 2022 08:27:41 AM MDT. Dependencies resolved. Package ArchVersionRepositorySize Upgrading: selinux-policy noarch 35.16-1.fc35 updates 68 k selinux-policy-targeted noarch 35.16-1.fc35 updates 6.3 M systemd x86_64 249.11-1.fc35 updates 4.1 M systemd-containerx86_64 249.11-1.fc35 updates 523 k systemd-libs x86_64 249.11-1.fc35 updates 603 k systemd-networkd x86_64 249.11-1.fc35 updates 523 k systemd-oomd-defaultsnoarch 249.11-1.fc35 updates 24 k systemd-pam x86_64 249.11-1.fc35 updates 323 k systemd-resolved x86_64 249.11-1.fc35 updates 266 k systemd-udev x86_64 249.11-1.fc35 updates 1.8 M Transaction Summary Upgrade 10 Packages Total download size: 14 M Is this ok [y/N]: y Downloading Packages: (1/10): systemd-libs-249.9-1.fc35_249.11-1.fc35 93 kB/s | 104 kB 00:01 (2/10): systemd-container-249.9-1.fc35_249.11-1 194 kB/s | 262 kB 00:01 (3/10): systemd-pam-249.9-1.fc35_249.11-1.fc35. 272 kB/s | 83 kB 00:00 [DRPM 1/7] systemd-libs-249.9-1.fc35_249.11-1.fc35.x86_64.drpm: done [DRPM 2/7] systemd-container-249.9-1.fc35_249.11-1.fc35.x86_64.drpm: done (4/10): systemd-networkd-249.9-1.fc35_249.11-1. 246 kB/s | 151 kB 00:00 (5/10): systemd-resolved-249.9-1.fc35_249.11-1. 351 kB/s | 87 kB 00:00 [DRPM 3/7] systemd-pam-249.9-1.fc35_249.11-1.fc35.x86_64.drpm: done (6/10): selinux-policy-35.16-1.fc35.noarch.rpm 357 kB/s | 68 kB 00:00 (7/10): systemd-udev-249.9-1.fc35_249.11-1.fc35 375 kB/s | 477 kB 00:01 [DRPM 4/7] systemd-networkd-249.9-1.fc35_249.11-1.fc35.x86_64.drpm: done [DRPM 5/7] systemd-resolved-249.9-1.fc35_249.11-1.fc35.x86_64.drpm: done (8/10): systemd-oomd-defaults-249.11-1.fc35.noa 351 kB/s | 24 kB 00:00 (9/10): systemd-249.9-1.fc35_249.11-1.fc35.x86_ 379 kB/s | 1.7 MB 00:04 (10/10): selinux-policy-targeted-35.16-1.fc35.n 996 kB/s | 6.3 MB 00:06 [DRPM 6/7] systemd-udev-249.9-1.fc35_249.11-1.fc35.x86_64.drpm: done [DRPM 7/7] systemd-249.9-1.fc35_249.11-1.fc35.x86_64.drpm: done Total 1.0 MB/s | 9.2 MB 00:09 Delta RPMs reduced 14.4 MB of updates to 9.2 MB (36.0% saved) ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: DRPM performance ?
On Wed, Feb 2, 2022 at 8:52 AM wrote: > > so a couple of weeks ago, > I did a dnf update, and got ~ 19% reduction due to DRPM > just the other day, I saved 18%, so it does happen semi-regularly FWIW, I wouldnt mind seeing %saved over the DPRM subset, not just %saved vs the whole download. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
DRPM performance ?
so a couple of weeks ago, I did a dnf update, and got ~ 19% reduction due to DRPM that was by far the highest return on the effort Id seen. previous experience for me was 1-4%. I should have grabbed a "screenshot" and sent it here. Whats the "average" experience here ? are there statistics ? do *noarch 's do better ? how often do you see some version of "find/download failed" ? (it sometimes appears to be a cached-version problem, particularly if the update is older than a few days) ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
ssh key question - does jimc@fedora need to be updated to follow new hostname ?
so I generated my local .ssh/id_rsa before I chose a hostname. Now that Ive updated hostname, the id ends with jimc@fedora, which is somehow misleading. but does it matter otherwise? as a test, I have added the key w.o alteration to github, and it works, implying that the hostname is not part of the key itself, or at least not verified as consistent with the key. does that sound more or less right? ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F34 cannot load kernel modules
On Wed, Apr 28, 2021 at 10:01 AM Paul Smith wrote: > > On Wed, Apr 28, 2021 at 7:58 AM Samuel Sieb wrote: > > > > > I have just upgraded from F33 to F34, and everything seems to be > > > working fine except when booting: a message appears saying: > > > > > > Failed to load kernel modules. > > > > This is a common issue. I've seen it on some computers for a long time > > and I haven't looked into it yet. As long as everything's working, > > don't worry about it. > > Thanks, Samuel! I have just found out that the culprit was > > v4l2loopback > > which I removed and installed again, and the reported error disappeared. > > Paul > ___ thanks for the followup. I too have been too lazy to look into this before, I'll check on next boot or maybe in log ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
just saw 89.1% saved by dprms
[DRPM 230/230] texlive-tex-gyre-svn48058-11.fc31_svn48058-13.fc31.noarch.drpm: done - Total 404 kB/s | 27 MB 01:07 Delta RPMs reduced 263.7 MB of updates to 26.5 MB (89.1% saved) Until somebody beats that, I'll claim the record ! ;-) and no I didnt search 1st. the internet is so full of false claims ... ___ 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
missing /sys/class/drm/* on official Fedora kernels
starting with 4.19.5, all my fedora kernels fail to get edid info during boot and are consequently missing /sys/class/drm/* so graphical resolution is degraded to vga Dec 02 02:29:36 popeye kernel: Linux version 4.19.5-300.fc29.i686 (mockbu...@bkernel04.phx2.fedoraproject.org) (gcc version 8.2.1 20181105 (Red Hat 8.2.1-5) (GCC)) #1 SMP Tue Nov 2 7 19:30:11 UTC 2018 Dec 02 09:31:48 popeye gsd-color[1561]: failed to get edid: unable to get EDID for output Dec 02 09:31:48 popeye gsd-color[1561]: unable to get EDID for xrandr-default: unable to get EDID for output Ive not really concerned myself too much with it, cuz Ive been building my own kernels from kernel.org, and they pick up EDID fwiw, I start with fedora.config, and do localmodconfig. iiuc, this reduces module builds to those usable on the hardware? and its an old box, or someone else would have noticed vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz stepping : 10 microcode : 0xa0b cpu MHz : 2792.715 but in the ensuing months, grub2-mkconfig is failing to update grub.cfg properly, so its slightly more tedious, and I should start investigating proper fixes. ___ 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
Re: F29 fails on new ThinkPad P72
On Sat, Nov 24, 2018 at 12:55 AM dsavage--- via users wrote: > > Michael, > > Not sure I can do that with a spin live DVD image. When I try to edit the > boot initiation code by typing "e" I see: > > getparams 'Start Fedora-MATE-Compiz-Live 29' > > linuxfi /images/pxeboot root=live:CDLABEL=Fedora-MATE-Live-29-1-2 > read.live.img > initdefi /images/pxeboot/initrd.img > > I don't see where grub-style editing is supported on a live DVD image. > > --Doc > It looks like youre set to edit the boot-code. do cursor keys not let you select the linuxefi line ?? if they do, add a 2 at end of linuxefi line, it puts you to non-graphical boot once you do, can you report the absence of /sys/class/drm/* ? so far, none of my boots of the f29 kernels fill this dir, (on my 32bit core 2 duo vintage box) this caused window managers to fail hard. gdm just locked up. lightdm was a bit better, but got screen resolution wrong - minimal res, huge pointer, fonts what worked for me was a locally built kernel, localmodconfig, after copying /boot/config-mumble-f29 to .config this gets screen res correct > > > Try the troubleshooting and do the basic video install. Have seen some > > video > > configurations that fail with the default install, since something with > > the video > > isn't fully supported on the install image. Usually, the basic install > > will work, > > and then running the update will bring in the stuff to support the video. > > > > > > On 23 Nov 2018 at 21:38, dsavage--- via users wrote: > > > > Date sent:Fri, 23 Nov 2018 21:38:35 -0600 > > Subject: F29 fails on new ThinkPad P72 > > To: "Community support for Fedora users" > > > > Send reply to:Community support for Fedora users > > > > From: dsavage--- via users > > > > Copies to:dsav...@peaknet.net > > > >> I just bought a ThinkPad P72 "mobile workstation". To see if Fedora 29 > >> would work, I made a bootable thumb drive with the 64-bit F29-MATE > >> spin. > >> It passed the self-test, but the boot stops before going into graphical > >> mode. > >> > >> This is a new and just-released system, so it couldn't be tested before > >> F29 was released. Some tech details: > >> > >> CPUsTwo E-2186M Xeon 6-core 2.9-4.6GHz w/12MB cache > >> RAM 64GB DDR4 2400MHz ECC > >> SSD Two 2TB PCIe-NVMe OPAL2.0 M.2 in RAID1 (Intel on-board > >> controller) > >> Video nVidia Quaddro P5200 > >> Display 17.3" 4K (3840x2160) > >> > >> Are any of these known to cause problems with F29? > >> > >> Robert G. (Doc) Savage > >> Fairview Heights, IL > >> > >> "Perfection is the enemy of good enough." > >> -- Admiral of the Fleet Sergei G. Gorshkov > >> ___ > >> 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 > > > > > > ++ > > Michael D. Setzer II - Computer Science Instructor (Retired) > > mailto:mi...@guam.net > > mailto:msetze...@gmail.com > > Guam - Where America's Day Begins > > G4L Disk Imaging Project maintainer > > http://sourceforge.net/projects/g4l/ > > ++ > > > > http://setiathome.berkeley.edu (Original) > > Number of Seti Units Returned: 19,471 > > Processing time: 32 years, 290 days, 12 hours, 58 minutes > > (Total Hours: 287,489) > > > > BOINC@HOME CREDITS > > > > ROSETTA 66144274.031401 | ABC 16613838.513356 > > SETI109699319.488428 | EINSTEIN141698081.499240 > > ___ > > 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 > > > > > Robert G. (Doc) Savage > Fairview Heights, IL > > "Perfection is the enemy of good enough." > -- Admiral of the Fleet Sergei G. Gorshkov > ___ > 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 ___ users mailing list -- users@lists.fedoraproject.org To
where is /sys/class/drm/* ?
so I just upgraded an old Dell Optiplex 760 - Core 2 Duo - 686 class box Fedora 28 -> 29 and all manner of things went wrong. I had to fall back to runlevel 2 boot, and fiddled. switching display manager to lightdm helped, allowing a graphical boot again. Resolution is very low, mouse arrow is huge. it turns out that /sys/class/drm doesnt exist. dmesg | grep drm is empty. ISTM this is the problem - if the kernel doesnt know about the monitor then resolution is not available to display manager either. I was able to figure a horrid workaround, by plugging in a better monitor and cold-booting afterwards, I swapped vga connector back to original monitor, it kept the same better resolution I have built my own kernel, v4.20-rc3+ which works properly, and has /sys/class/drm/* as expected I built it like 1- cp /boot/config-f29-mumble .config; 2- make localmodconfig 3- make xconfig - flip 64bit build off on this 32bit box 4- make; make install Aside: I think step 3 should be unnecessary - build box == install box which should correct/override any defaults taken from 1, or by other operations of 2 I have since dnf updated, rebooted to 19.2, it exhibits same problem and rebooting to rc3+ fixes resolution problem wo doing the nasty monitor swap does anyone else seeing anything odd (I presume) related to old 32bit hardware and video card ? ___ 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: lost graphical boot after f29 upgrade
On Sat, Nov 17, 2018 at 11:58 AM wrote: > > boot process hangs/stalls on graphical screen with 3 blocks illuminated. > > startx works at least partly which means X, not wayland, I guess. FWIW, this is a vga monitor. there are some odd resolution switches during boot and Dell logo gets 4 interleaved ghosts on screen during part of these switches. maybe corroborating failure to read any monitor resolution > I have some recollection of seeing discussion of switching display managers, > Im gonna look at that next, hints welcome. I managed to switch to lightdm. boots to graphical screen, at LOW resolution (same big mouse/pointer) but usable, at least a little bit. Im gonna try a different monitor soon. but I think im stuck with vga on box ___ 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
lost graphical boot after f29 upgrade
boot process hangs/stalls on graphical screen with 3 blocks illuminated. booting as normal, but hitting escape early, will revert screen to a console, which displays the old-school kernel and systemd startup lines, until it hits "Starting GNOME Display Manager" then it hangs. If I edit boot command line by adding a 2 (runlevel 2) it will eventually (I came back later) leave that 3-block screen and go to console, the screen is full of accented Gs. Ive edited boot command line, dropping the "rhgb quiet" and adding "2" it boots faster to same 'G' filled console screen. console clears 'G's where it offers login prompt, typing clears lines after CR/NL once logged in, console is usable. startx works at least partly it clears screen, paints a big mouse and waits. eventually it rendered the default background - meshy blue screen, and the mouse started working the background looks same as on my hires laptop, despite the large pointer and font. Devices->Display shows blank resolution, lspci -v says its an Intel 4 series chipset integrated graphics controller this is on an old dell desktop with core 2 duo, uname -a has i686 (4.18-300 iirc) I have some recollection of seeing discussion of switching display managers, Im gonna look at that next, hints welcome. ___ 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: what release am I running ?
thank you all for your answers, I'll try to be complete here, but brief
1st, Im not having any troubles - normal ops are fine, sudo dnf update
works, etc.
only oddity is with dual boot - 1st few attempts to boot win10 failed after
installing 24-beta (not an upgrade from f23). But recent attempts now seem
to work, theyre just a little thrashy (iirc, the bios seems to boot 2x - 2
toshiba splash screens) but it gets there. This is my 1st EFI bios
machine, so I
dont have anything to compare it to.
[jimc@buffy ~]$ more /etc/fedora-release
Fedora release 24 (Twenty Four)
[jimc@buffy ~]$ more /etc/system-release*:
:
/etc/system-release
::
Fedora release 24 (Twenty Four)
::
/etc/system-release-cpe
::
cpe:/o:fedoraproject:fedora:24
So thos are good, but I dont know whether any of these said "beta" anywhere
before final release
[jimc@buffy ~]$ rpm -qil fedora-release
Name: fedora-release
Version : 24
Release : 2
Architecture: noarch
Install Date: Mon 27 Jun 2016 02:10:28 PM MDT
my /etc/os-release matches Darios
but again I dont know if it said beta earlier.
[jimc@buffy etc]$ dnf repoquery --duplicated
Last metadata expiration check: 0:36:45 ago on Tue Jun 28 10:02:03 2016.
so that looks clean
$ cat /var/lib/dnf/system-upgrade.json
{"upgrade_status": null, "download_status": null}
which seems kind-of empty,
and counter to what Rick Stevens expected in it,
but again I dont know how it looked before..
to satisfy curiosity, I ran:
[jimc@buffy dnf]$ pwd
/var/lib/dnf
[jimc@buffy dnf]$ sudo strings history/history-2016-05-04.sqlite | less
saw lots of 'fc24', but no 'beta's other than (mostly) taglib packages.
at this point, things are fine, so Im not gonna sweat the off-chance
that I might still be at "Beta" - all the packages upgraded to final.
In a few weeks I'll be back to those fc23 boxes,
will do those upgrades, and if that suggests anything pertinent here
(longshot)
I'll follow up here.
thanks again y'all
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
what release am I running ?
I installed Fc24 beta a month ago on a new laptop Ive tried upgrading to 24-final, unsure Ive succeeded. https://fedoraproject.org/wiki/DNF_system_upgrade heres what I get now: $ sudo dnf system-upgrade download --refresh --releasever 24 --allowerasing --best Error: Need a --releasever greater than the current system version. that error suggests upgrade completed. BUT $ sudo dnf system-upgrade reboot Error: system is not ready for upgrade that could be either because it isnt ready (for an unobvious reason) or because its already complete, and not ready for F25 yet Im pretty sure I ran this or similar shortly after final, but I also ran it on several other boxes, without keeping notes, so not sure of current state (on any of them :-( -d 7 seems to say Ive succeeded ]$ sudo dnf system-upgrade download --refresh --releasever 24 --allowerasing --best -d 7 timer: config: 3 ms cachedir: /var/cache/dnf Loaded plugins: generate_completion_cache, download, copr, reposync, protected_packages, system-upgrade, noroot, config-manager, playground, Query, needs-restarting, debuginfo-install, builddep, langpacks langpacks: No languages are enabled Error reading file : /var/lib/dnf/plugins/langpacks/installed_langpacks as it does not exist initialized Langpacks plugin DNF version: 1.1.9 Command: dnf system-upgrade download --refresh --releasever 24 --allowerasing --best -d 7 Installroot: / Releasever: 24 Base command: system-upgrade Extra commands: ['download'] Cleaning up. Error: Need a --releasever greater than the current system version. If youve succeeded in your install, what happens if you do this ?? dnf system-upgrade reboot -d 7 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
F-16 broken for runlevel 5
I just upgraded my 64bit box to F-16 using preupgrade, and the graphical login is busted. It displays the nice bathyscath (deep sea) screen for a second, then goes black with a sad computer face |:-(| saying non-specifically somethings gone wrong, . contact administator Box boots ok to runlevel 3, running startx gets same screen, ctrl-alt-delete gets logout dialog, doing it, I get same screen repeatedly. heres the log when I run startx: X.Org X Server 1.11.2 Release Date: 2011-11-04 X Protocol Version 11, Revision 0 Build Operating System: x86-12 2.6.32-131.17.1.el6.x86_64 Current Operating System: Linux groucho.jimc.earth 3.1.1-1.fc16.x86_64 #1 SMP Fri Nov 11 21:47:56 UTC 2011 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.1.1-1.fc16.x86_64 root=/dev/mapper/vg_groucho-lv_root ro rd.md=0 rd.dm=0 KEYTABLE=us quiet rd.lvm.lv=vg_groucho/lv_swap SYSFONT=latarcyrheb-sun16 rhgb rd.lvm.lv=vg_groucho/lv_root rd.luks=0 LANG=en_US.UTF-8 3 Build Date: 10 November 2011 07:40:04PM Build ID: xorg-x11-server 1.11.2-3.fc16 Current version of pixman: 0.22.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Mon Nov 14 16:25:59 2011 (==) Using config file: /etc/X11/xorg.conf (==) Using config directory: /etc/X11/xorg.conf.d (==) Using system config directory /usr/share/X11/xorg.conf.d resize called 3840 1200 GNOME_KEYRING_CONTROL=/tmp/keyring-Vk2x47 GNOME_KEYRING_PID=2647 GNOME_KEYRING_CONTROL=/tmp/keyring-Vk2x47 SSH_AUTH_SOCK=/tmp/keyring-Vk2x47/ssh GNOME_KEYRING_CONTROL=/tmp/keyring-Vk2x47 SSH_AUTH_SOCK=/tmp/keyring-Vk2x47/ssh GNOME_KEYRING_CONTROL=/tmp/keyring-Vk2x47 SSH_AUTH_SOCK=/tmp/keyring-Vk2x47/ssh GPG_AGENT_INFO=/tmp/keyring-Vk2x47/gpg:0:1 W: main.c: This program is not intended to be run as root (unless --system is specified). Gtk-Message: Failed to load module pk-gtk-module Gtk-Message: Failed to load module pk-gtk-module Initializing tracker-miner-fs... Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-miner-fs.cfg' Starting log: File:'/root/.local/share/tracker/tracker-miner-fs.log' Initializing tracker-store... Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-store.cfg' Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-store.cfg' Starting log: File:'/root/.local/share/tracker/tracker-store.log' You must NOT run gDesklets as super user (root). Please do not run uptrack-manager as root! (pass in --as-root if you really want to do this) Gtk-Message: Failed to load module pk-gtk-module JS ERROR: !!! Exception was: Error: Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found JS ERROR: !!! lineNumber = '0' JS ERROR: !!! fileName = 'gjs_throw' JS ERROR: !!! stack = '(Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found)@gjs_throw:0 @/usr/share/gnome-shell/js/ui/keyboard.js:3 ' JS ERROR: !!! message = 'Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found' JS ERROR: !!! Exception was: Error: Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found JS ERROR: !!! lineNumber = '0' JS ERROR: !!! fileName = 'gjs_throw' JS ERROR: !!! stack = '(Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found)@gjs_throw:0 @/usr/share/gnome-shell/js/ui/keyboard.js:3 ' JS ERROR: !!! message = 'Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found' JS ERROR: !!! Exception was: Error: Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found JS ERROR: !!! lineNumber = '0' JS ERROR: !!! fileName = 'gjs_throw' JS ERROR: !!! stack = '(Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found)@gjs_throw:0 @/usr/share/gnome-shell/js/ui/keyboard.js:3 ' JS ERROR: !!! message = 'Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found' Window manager warning: Log level 32: Execution of main.js threw exception: Error: Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found Gtk-Message: Failed to load module pk-gtk-module Gtk-Message: Failed to load module pk-gtk-module Gtk-Message: Failed to load module pk-gtk-module Gtk-Message: Failed to load module pk-gtk-module Gtk-Message: Failed to load module pk-gtk-module ** (gnome-user-share:2699): WARNING **: gnome-user-share cannot be started as root for security
Re: F-16 broken for runlevel 5
On Tue, Nov 15, 2011 at 7:46 PM, Joe Zeff j...@zeff.us wrote: On 11/15/2011 06:30 PM, Jim Cromie wrote: somethings gone wrong, . contact administator There's only one way to deal with programmers who think that's an appropriate error message: give their GPS coordinates to OADS (http://www.impsec.org/~jhardin/OADS/anvil_chorus.html). I dont think Id like complainers ringing my doorbell. Grovelling through your logs, however, reveals a large number of warnings about programs that shouldn't be run as root. Were you trying to log into the GUI as root? It's not exactly the best of ideas, and Fedora usually disables root logins by default. If so, have you tried logging in as a non-root user? -- No, gui login as regular user. reboot was needed to get to text prompt. at that point, logs in /var/log/messages were cluttered with the following runlevel 3 boot. Rather than find the pertinent parts, I just ran startx from the text session. I probably added sudo by habit for system-ish stuff. Heres a rerun of startx log 21 xauth: file /home/jimc/.serverauth.1967 does not exist X.Org X Server 1.11.2 Release Date: 2011-11-04 X Protocol Version 11, Revision 0 Build Operating System: x86-12 2.6.32-131.17.1.el6.x86_64 Current Operating System: Linux groucho.jimc.earth 3.1.1-1.fc16.x86_64 #1 SMP Fri Nov 11 21:47:56 UTC 2011 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.1.1-1.fc16.x86_64 root=/dev/mapper/vg_groucho-lv_root ro rd.md=0 rd.dm=0 KEYTABLE=us quiet rd.lvm.lv=vg_groucho/lv_swap SYSFONT=latarcyrheb-sun16 rhgb rd.lvm.lv=vg_groucho/lv_root rd.luks=0 LANG=en_US.UTF-8 3 Build Date: 10 November 2011 07:40:04PM Build ID: xorg-x11-server 1.11.2-3.fc16 Current version of pixman: 0.22.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 15 20:30:18 2011 (==) Using config file: /etc/X11/xorg.conf (==) Using config directory: /etc/X11/xorg.conf.d (==) Using system config directory /usr/share/X11/xorg.conf.d resize called 3840 1200 gnome-session-is-accelerated: No hardware 3D support. gnome-session-check-accelerated: Helper exited with code 256 gnome-session[2052]: WARNING: Session 'gnome' runnable check failed: Exited with code 1 GNOME_KEYRING_CONTROL=/tmp/keyring-ZXBHJB GNOME_KEYRING_PID=2079 GNOME_KEYRING_CONTROL=/tmp/keyring-ZXBHJB GNOME_KEYRING_CONTROL=/tmp/keyring-ZXBHJB GPG_AGENT_INFO=/tmp/keyring-ZXBHJB/gpg:0:1 GNOME_KEYRING_CONTROL=/tmp/keyring-ZXBHJB GPG_AGENT_INFO=/tmp/keyring-ZXBHJB/gpg:0:1 SSH_AUTH_SOCK=/tmp/keyring-ZXBHJB/ssh resize called 3840 1461 Gtk-Message: Failed to load module pk-gtk-module [1321414234,000,xklavier.c:xkl_engine_start_listen/]The backend does not require manual layout management - but it is provided by the application g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. (gnome-settings-daemon:2072): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (gnome-settings-daemon:2072): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (gnome-settings-daemon:2072): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (gnome-settings-daemon:2072): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed (gnome-settings-daemon:2072): color-plugin-WARNING **: Failed to CreateProfile: The connection is closed (gnome-settings-daemon:2072): color-plugin-WARNING **: Failed to CreateProfile: The connection is closed Gtk-Message: Failed to load module pk-gtk-module resize called 3840 1461 Gtk-Message: Failed to load module pk-gtk-module Gtk-Message: Failed to load module pk-gtk-module Gtk-Message: Failed to load module pk-gtk-module Gtk-Message: Failed to load module pk-gtk-module (bluetooth-applet:2214): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation Gtk-Message: Failed to load module pk-gtk-module ** (gnome-fallback-mount-helper:2221): DEBUG: Starting automounting manager ** (gnome-fallback-mount-helper:2221): DEBUG: Found ConsoleKit session at path /org/freedesktop/ConsoleKit/Session2 ** (gnome-fallback-mount-helper:2221): DEBUG: ScreenSaver name vanished ** (gnome-fallback-mount-helper:2221): DEBUG: ConsoleKit session is active 1 Gtk-Message: Failed to load module pk-gtk-module Initializing tracker-store... Tracker-Message: Setting up monitor for changes to config file:'/home/jimc/.config/tracker/tracker-store.cfg' ** Message: applet now removed from the notification area Gtk-Message: Failed to load module pk-gtk-module Initializing tracker-miner-fs... Tracker-Message: Setting
system-admin-add/remove-sw error msg clarification.
Im trying to build openwrt for x86 on x86-64 F-14 box, I get this error. [jimc@groucho backfire-svn]$ make ++ mkdir -p /home/jimc/projects/openwrt/backfire-svn/staging_dir/toolchain-i386_gcc-4.1.2_uClibc-0.9.30.1 ++ cd /home/jimc/projects/openwrt/backfire-svn/staging_dir/toolchain-i386_gcc-4.1.2_uClibc-0.9.30.1 ++ mkdir -p stamp lib usr/include usr/lib make[4]: Entering directory `/home/jimc/projects/openwrt/backfire-svn/target/linux' make[5]: Entering directory `/home/jimc/projects/openwrt/backfire-svn/target/linux/x86' make[6]: Entering directory `/home/jimc/projects/openwrt/backfire-svn/target/linux/x86/image' make[6]: Leaving directory `/home/jimc/projects/openwrt/backfire-svn/target/linux/x86/image' make[5]: Leaving directory `/home/jimc/projects/openwrt/backfire-svn/target/linux/x86' make[4]: Leaving directory `/home/jimc/projects/openwrt/backfire-svn/target/linux' Checking 'working-gcc-m32'... failed. grub: Please install 32 bits development files. (gcc-multilib on Debian/Ubuntu, gcc.i686 and libgcc.i686 on CentOS/Fedora/RHEL) I went to system-admin-add/remove-sw, searched for gcc, couldnt find an rpm. So I clicked menubar-System-Software-Sources, then tried to enable F-14 (F-14 -x86_64 already set) after authenticating, I get: Insert media labeled 'Fedora 14 Volume #1' or disable media repos. I dont have the DVD What/which are the media repos ? is a checkbox I need to disable in software sources, or something else ? help-content, gnome-packagekit search media repos showed nothing. -- 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
unable to build qgit v2.3 from source on fedora 13
I just grabbed qgit4 v2.3 from sourceforge, but I cannot build it. [jimc@groucho qgit]$ date Wed Apr 6 14:35:08 MDT 2011 [jimc@groucho qgit]$ qmake [jimc@groucho qgit]$ ll total 52 -rw-r--r--. 1 jimc jimc 12394 Dec 21 2007 exception_manager.txt -rw-rw-r--. 1 jimc jimc 1540 Apr 6 14:35 Makefile -rw-rw-r--. 1 jimc jimc 3584 May 5 2009 qgit_inno_setup.iss -rw-r--r--. 1 jimc jimc57 Mar 5 2009 qgit.pro -rw-rw-r--. 1 jimc jimc 15895 Mar 12 2009 README -rw-r--r--. 1 jimc jimc 1035 Aug 21 2008 README_WIN.txt drwxrwxr-x. 3 jimc jimc 4096 Apr 6 14:20 src [jimc@groucho qgit]$ make cd src qmake src.pro -o Makefile src.pro:12: Unknown test function: greaterThan Project ERROR: Sorry I need Qt 4.3.0 or later, you seem to have Qt instead make: *** [src/Makefile] Error 2 I have the apparent prereqs: $ rpm -qa |grep qt qt-4.6.3-10.fc13.i686 qt-4.6.3-10.fc13.x86_64 qt-devel-4.6.3-10.fc13.x86_64 qmake is part of qt3 - is this why it breaks with qt4 ??? It has been built for fedora-12, but not since, apparently. [jimc@groucho src]$ rpm -qi qgit Name: qgit Relocations: (not relocatable) Version : 2.3 Vendor: Fedora Project Release : 2.fc12Build Date: Tue 28 Jul 2009 03:14:17 AM MDT Install Date: Wed 26 May 2010 08:42:04 AM MDT Build Host: xenbuilder2.fedora.redhat.com Group : Development/Tools Source RPM: qgit-2.3-2.fc12.src.rpm Size: 1001518 License: GPLv2 Signature : RSA/SHA256, Mon 22 Feb 2010 02:03:16 AM MST, Key ID 7edc6ad6e8e40fde Packager: Fedora Project URL : http://digilander.libero.it/mcostalba/ Summary : GUI browser for git repositories Description : With qgit you are able to browse revisions history, view patch content and changed files, graphically following different development branches. -- 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: unable to build qgit v2.3 from source on fedora 13 - solved
On Wed, Apr 6, 2011 at 3:52 PM, Michael Cronenworth m...@cchtml.com wrote: Jim Cromie wrote: qmake is part of qt3 - is this why it breaks with qt4 ??? I'm not a Qt expert, but you may need to use qmake-qt4 instead. doh yes. -ETOORUSHED I tried qmake4, didnt think to check for other spellings thanks -- 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 -- 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
cant upgrade F13 to F14
Anaconda is telling me I have a dirty partition, and to reboot cleanly, which Ive done several times. The broken aspect here is that anaconda is complaining about /dev/sda1, which is the Dell Utility partition, which should *not* be involved. heres the partition table of the drive holding currrent F13 install Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf000 Device Boot Start End Blocks Id System /dev/sda1 1 6 48163+ de Dell Utility /dev/sda2 * 71271101560327 HPFS/NTFS /dev/sda31271 62450 4914237447 HPFS/NTFS /dev/sda4 62450 121602 4751329285 Extended /dev/sda5 62451 62514 512000 83 Linux /dev/sda6 62514 121602 474618880 8e Linux LVM Is this prob due to boot flag on sda2 ? Grub has no problem booting sda2 or sda5 title Fedora (2.6.34.7-63.fc13.x86_64) root (hd0,4) kernel /vmlinuz-2.6.34.7-63.fc13.x86_64 ro root=/dev/mapper/vg_groucho-l v_root rd_LVM_LV=vg_groucho/lv_root rd_LVM_LV=vg_groucho/lv_swap rd_NO_LUKS rd_N O_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABL E=us rhgb quiet initrd /initramfs-2.6.34.7-63.fc13.x86_64.img title Windows 7 rootnoverify (hd0,1) chainloader +1 Given that the problem is supposedly with the Dell Utility partition, I regard this as a reportable bug in anaconda. Concur ? Any workarounds ? -- 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
network interfaces aliases question/issue
using sysconfig-network, Ive added an alias to my eth0 to add a fixed IP [j...@groucho network-scripts]$ egrep -E 'DEV|BOOT|IPADD' ifcfg-eth0* ifcfg-eth0:DEVICE=eth0 ifcfg-eth0:BOOTPROTO=dhcp ifcfg-eth0:ONBOOT=yes ifcfg-eth0:1:DEVICE=eth0:1 ifcfg-eth0:1:BOOTPROTO=none ifcfg-eth0:1:IPADDR=192.168.20.2 but it seems I can only have one of them working: (Ive since renamed eth0:1 to eth0_static, thinking there was a problem with ':' in filename) [j...@groucho network-scripts]$ sudo ifup eth0 Active connection state: activating Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/5 state: activated Connection activated [j...@groucho network-scripts]$ ip addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:24:e8:2a:22:19 brd ff:ff:ff:ff:ff:ff inet 192.168.10.101/24 brd 192.168.10.255 scope global eth0 inet6 fe80::224:e8ff:fe2a:2219/64 scope link valid_lft forever preferred_lft forever [j...@groucho network-scripts]$ sudo ifup eth0_static Active connection state: activated Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/6 [j...@groucho network-scripts]$ ip addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:24:e8:2a:22:19 brd ff:ff:ff:ff:ff:ff inet 192.168.20.2/24 brd 192.168.20.255 scope global eth0 inet6 fe80::224:e8ff:fe2a:2219/64 scope link valid_lft forever preferred_lft forever I expected 2 inet lines above. And its not just NetoworkManager messing up. Ive taken both interfaces (main, alias) from NM's control, and I get the same *last-upped-interface-wins* behavior [j...@groucho network-scripts]$ ip addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:24:e8:2a:22:19 brd ff:ff:ff:ff:ff:ff inet 192.168.10.101/24 brd 192.168.10.255 scope global eth0 inet6 fe80::224:e8ff:fe2a:2219/64 scope link valid_lft forever preferred_lft forever [j...@groucho network-scripts]$ ifup eth0_static Active connection state: activated Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/9 [j...@groucho network-scripts]$ ip addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:24:e8:2a:22:19 brd ff:ff:ff:ff:ff:ff inet 192.168.20.2/24 brd 192.168.20.255 scope global eth0 inet6 fe80::224:e8ff:fe2a:2219/64 scope link valid_lft forever preferred_lft forever [j...@groucho network-scripts]$ ifup eth0 Active connection state: activating Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/10 state: activated Connection activated [j...@groucho network-scripts]$ ip addr show dev eth0 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:24:e8:2a:22:19 brd ff:ff:ff:ff:ff:ff inet 192.168.10.101/24 brd 192.168.10.255 scope global eth0 inet6 fe80::224:e8ff:fe2a:2219/64 scope link valid_lft forever preferred_lft forever btw, is one addressee better than the other ? -- 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: Yum update crashes
On Fri, Jan 29, 2010 at 11:27 AM, Jim mickey...@sbcglobal.net wrote: FC12-X86_64/KDE Yum update is crashing. I did a yum clean all, but that doesn't help. ]# yum update what happens if you update 1 package ? (pick a simple one, w/o lots of deps) -- 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/Communicate/MailingListGuidelines
