recover from a bad F16 install
by Paul Allen Newell
To all:
I have an install DVD that I used to do a fresh install of F16 onto a
i386/686 machine. I then used it to do a fresh install of a second
machine. Midway through the formatting/partitioning, it "popped up a
bug". When I reported it, it pointed me to 743778 which was closed as
"notabug". At that point, the machine was at some unknown state in its
formatting.
I now have a machine that is "a brick". There is no operating system on
it as that got destroyed and any attempts to do a fresh install come
back with "No usable disks have been found" and I can't make any
progress. Nothing could be done in the troubleshoot options except get a
dmesg, which I have attached to this email.
Is this one of these times where I need to get something like
partedmagic and figure out how to format/partition from there? If so,
anyone done this before and can give pointers. If not, what other
options do I have.
The machine in question has two hard drives, if that matters.
For what it is worth, I used the same DVD and am now doing a fresh
install on a third machine. First and third machines are HP x4000 and
the second "brick" is HP xw8000. I'm hard-pressed to believe it is a
difference between x4000 and xw8000, but I thought it ought to mention.
Thanks in advance,
Paul
12 years, 2 months
Re: booting from DVD image on hard drive partition
by Jackson Byers
Michael,
Your responses have me more and more confused as to exactly
what you are trying to do:
>My machine can still boot from my FC13 installation disk.
>I copied FC13's vmlinuz to a hard drive and
>tried again with the grub command line.
>I have F14 installed, but F13 is the most recent DVD I can find.
why are you booting from F13 installation disk if you have F14 installed?
why do you need to find the F14 DVD?
Does this mean:
--you do not have F13 installed?
--your F14 install is somehow broken?
What version of installed-fedora are you operating from?
What version of fedora is the iso you are extracting from?
Is either F15,F16 involved?
the hdinstall, as per Horsley, and as per fedoraproject:
is meant to operate from an already existing fedora system,
which you don't seem to have.
>Chapter 12. Installing Without Media
>12.1. Retrieving Boot Files
>12.2. Editing the GRUB Configuration
>12.3. Booting to Installation
>Linux Required
>This procedure assumes you are already using Fedora or another relatively modern >Linux distribution, and the GRUB boot loader. It also assumes you are a somewhat >experienced Linux user.
>This section discusses how to install Fedora on your system without making any >additional physical media. Instead, you can use your existing GRUB boot loader to start >the installation program
Note:" without making any additional physical media", i.e, no DVD, just the iso
Note: "use your existing GRUB boot loader"
Jack
12 years, 2 months
nvidia-installer
by Lawrence E Graves
I believe there is something wrong with the nvidia-installer and I don't
know where to begin to troubleshoot this problem. Will someone advise.
There is a patch out there but I don't know how to install it or where
to install it. Please help.
--
Lawrence Graves All things are workable but don't all things work.
12 years, 2 months
systemctl completion failure?
by Ed Greshko
I think this is a failure....but not 100% certain that it isn't intended behavior....
Typing.... "systemctl is-enabled h" (followed by tab) give the output of....
halt-local.service home-egreshko-misty.mount
halt.service home.mount
Suggesting those are the only choices. But if "systemctl is-enabled httpd.service"
is typed the status of "disabled" is returned correctly.
It seems to me that the "is-enabled" parameter is using the output of "systemctl
list-units --all" as the array of choices to pattern match against. I'm thinking it
really should be using the output of "systemctl list-unit-files".
--
Do not condemn the judgment of another because it differs from your own. You may both
be wrong. -- Dandemis
12 years, 2 months
A nit on apper
by Patrick O'Callaghan
I recently attempted to update my system using apper. It gave me the
list of rpms, I said Apply, it started working, then it popped up a
message about some packages not being signed and did I want to proceed.
However it didn't say *which* packages.
How is the user supposed to make an intelligent decision in this
situation?
I just killed apper and used yum, which my usual procedure.
Interestingly, yum had no complaints about unsigned packages and
everything worked.
So to summarize: apper's behaviour in this case recalls the aprocryphal
IBM mainframe message "Wrong Error".
Or to summarize the summary: WTF?
poc
12 years, 2 months
Issue with updates on 64 bit systems
by Michael D. Setzer II
Getting errors on running updates on x64 systems.
The 32 bit machines upgraded with no problems, but the 64 bit
systems are getting dependency errors.
Seens seems some of the 64 bit files are not in updates, but do
appear to be in testing, but when trying to add them on a test
machine, the get a clang requires 4.6.2 of gcc-c++, but it is about
to upgrade to 4.6.3-2?
Originally in doing the update there were a number of other
programs to be updated that did get updated even with
skip-broken, but manually update the ones I could.
The stdout of yum update
Loaded plugins: fastestmirror, langpacks, presto,
refresh-packagekit
Loading mirror speeds from cached hostfile
* fedora: ucmirror.canterbury.ac.nz
* rpmfusion-free: mirror.hiwaay.net
* rpmfusion-free-updates: mirror.hiwaay.net
* rpmfusion-nonfree: mirror.hiwaay.net
* rpmfusion-nonfree-updates: mirror.hiwaay.net
* updates: ucmirror.canterbury.ac.nz
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package cpp.x86_64 0:4.6.2-1.fc16 will be updated
---> Package cpp.x86_64 0:4.6.3-2.fc16 will be an update
---> Package gcc.x86_64 0:4.6.2-1.fc16 will be updated
---> Package gcc.x86_64 0:4.6.3-2.fc16 will be an update
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc-c++ = 4.6.2 for package:
clang-2.9-6.fc16.x86_64
---> Package gcc-c++.x86_64 0:4.6.3-2.fc16 will be an update
---> Package gcc-gfortran.x86_64 0:4.6.2-1.fc16 will be updated
---> Package gcc-gfortran.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgcc.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgcc.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgcj.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgcj.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgfortran.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgfortran.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgomp.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgomp.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libquadmath.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libquadmath.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libquadmath-devel.x86_64 0:4.6.2-1.fc16 will be
updated
---> Package libquadmath-devel.x86_64 0:4.6.3-2.fc16 will be an
update
---> Package libstdc++.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libstdc++.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libstdc++-devel.x86_64 0:4.6.2-1.fc16 will be
updated
---> Package libstdc++-devel.x86_64 0:4.6.3-2.fc16 will be an
update
---> Package libtool.x86_64 0:2.4-8.fc16 will be updated
---> Package libtool.x86_64 0:2.4-9.fc16 will be an update
---> Package libtool-ltdl.x86_64 0:2.4-8.fc16 will be updated
---> Package libtool-ltdl.x86_64 0:2.4-9.fc16 will be an update
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc = 4.6.2-1.fc16 for package:
gcc-c++-4.6.2-1.fc16.x86_64
--> Processing Dependency: libstdc++ = 4.6.2-1.fc16 for package:
gcc-c++-4.6.2-1.fc16.x86_64
--> Processing Dependency: libstdc++-devel = 4.6.2-1.fc16 for
package: gcc-c++-4.6.2-1.fc16.x86_64
---> Package gcc-c++.x86_64 0:4.6.3-2.fc16 will be an update
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc = 4.6.2-1.fc16 for package:
gcc-c++-4.6.2-1.fc16.x86_64
---> Package libstdc++.i686 0:4.6.2-1.fc16 will be installed
--> Processing Dependency: libgcc_s.so.1(GCC_3.3.1) for
package: libstdc++-4.6.2-1.fc16.i686
--> Processing Dependency: libgcc_s.so.1(GLIBC_2.0) for
package: libstdc++-4.6.2-1.fc16.i686
--> Processing Dependency: libgcc_s.so.1 for package:
libstdc++-4.6.2-1.fc16.i686
--> Processing Dependency: libgcc_s.so.1(GCC_3.0) for package:
libstdc++-4.6.2-1.fc16.i686
--> Processing Dependency: libgcc_s.so.1(GCC_4.2.0) for
package: libstdc++-4.6.2-1.fc16.i686
--> Processing Dependency: libgcc_s.so.1(GCC_3.3) for package:
libstdc++-4.6.2-1.fc16.i686
---> Package libstdc++.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libstdc++.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libstdc++-devel.i686 0:4.6.2-1.fc16 will be installed
---> Package libstdc++-devel.x86_64 0:4.6.2-1.fc16 will be
updated
---> Package libstdc++-devel.x86_64 0:4.6.2-1.fc16 will be
updated
--> Running transaction check
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: gcc = 4.6.2-1.fc16 for package:
gcc-c++-4.6.2-1.fc16.x86_64
---> Package libgcc.i686 0:4.6.3-2.fc16 will be installed
--> Running transaction check
---> Package gcc.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: cpp = 4.6.2-1.fc16 for package:
gcc-4.6.2-1.fc16.x86_64
--> Processing Dependency: libgomp = 4.6.2-1.fc16 for package:
gcc-4.6.2-1.fc16.x86_64
---> Package gcc.x86_64 0:4.6.3-2.fc16 will be an update
--> Processing Dependency: gcc = 4.6.3-2.fc16 for package:
libquadmath-devel-4.6.3-2.fc16.x86_64
--> Processing Dependency: gcc = 4.6.3 for package:
libtool-2.4-9.fc16.x86_64
--> Processing Dependency: gcc = 4.6.3-2.fc16 for package:
gcc-gfortran-4.6.3-2.fc16.x86_64
---> Package gcc-c++.x86_64 0:4.6.2-1.fc16 will be updated
--> Running transaction check
---> Package gcc.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: cpp = 4.6.2-1.fc16 for package:
gcc-4.6.2-1.fc16.x86_64
---> Package gcc.x86_64 0:4.6.3-2.fc16 will be an update
--> Processing Dependency: gcc = 4.6.3-2.fc16 for package:
libquadmath-devel-4.6.3-2.fc16.x86_64
--> Processing Dependency: gcc = 4.6.3 for package:
libtool-2.4-9.fc16.x86_64
--> Processing Dependency: gcc = 4.6.3-2.fc16 for package:
gcc-gfortran-4.6.3-2.fc16.x86_64
---> Package libgomp.i686 0:4.6.2-1.fc16 will be installed
---> Package libgomp.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgomp.x86_64 0:4.6.2-1.fc16 will be updated
--> Running transaction check
---> Package cpp.x86_64 0:4.6.2-1.fc16 will be updated
---> Package cpp.x86_64 0:4.6.3-2.fc16 will be an update
---> Package gcc.x86_64 0:4.6.2-1.fc16 will be updated
---> Package gcc.x86_64 0:4.6.3-2.fc16 will be an update
---> Package gcc-gfortran.x86_64 0:4.6.2-1.fc16 will be updated
--> Processing Dependency: libgfortran = 4.6.2-1.fc16 for
package: gcc-gfortran-4.6.2-1.fc16.x86_64
--> Processing Dependency: libquadmath = 4.6.2-1.fc16 for
package: gcc-gfortran-4.6.2-1.fc16.x86_64
---> Package gcc-gfortran.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libquadmath-devel.x86_64 0:4.6.2-1.fc16 will be
updated
---> Package libquadmath-devel.x86_64 0:4.6.3-2.fc16 will be an
update
---> Package libtool.x86_64 0:2.4-8.fc16 will be updated
---> Package libtool.x86_64 0:2.4-9.fc16 will be an update
--> Running transaction check
---> Package libgfortran.i686 0:4.6.2-1.fc16 will be installed
---> Package libgfortran.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgfortran.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libquadmath.i686 0:4.6.2-1.fc16 will be installed
---> Package libquadmath.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libquadmath.x86_64 0:4.6.2-1.fc16 will be updated
--> Running transaction check
---> Package libgcc.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgcc.i686 0:4.6.3-2.fc16 will be installed
---> Package libgcc.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgcj.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgcj.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgfortran.i686 0:4.6.2-1.fc16 will be installed
---> Package libgfortran.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgfortran.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libgomp.i686 0:4.6.2-1.fc16 will be installed
---> Package libgomp.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libgomp.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libquadmath.i686 0:4.6.2-1.fc16 will be installed
---> Package libquadmath.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libquadmath.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libstdc++.i686 0:4.6.2-1.fc16 will be installed
---> Package libstdc++.x86_64 0:4.6.2-1.fc16 will be updated
---> Package libstdc++.x86_64 0:4.6.3-2.fc16 will be an update
---> Package libstdc++-devel.i686 0:4.6.2-1.fc16 will be installed
---> Package libstdc++-devel.x86_64 0:4.6.2-1.fc16 will be
updated
---> Package libstdc++-devel.x86_64 0:4.6.3-2.fc16 will be an
update
---> Package libtool-ltdl.x86_64 0:2.4-8.fc16 will be updated
---> Package libtool-ltdl.x86_64 0:2.4-9.fc16 will be an update
--> Finished Dependency Resolution
Packages skipped because of dependency problems:
cpp-4.6.3-2.fc16.x86_64 from updates
gcc-4.6.3-2.fc16.x86_64 from updates
gcc-c++-4.6.3-2.fc16.x86_64 from updates
gcc-gfortran-4.6.3-2.fc16.x86_64 from updates
libquadmath-devel-4.6.3-2.fc16.x86_64 from updates
libtool-2.4-9.fc16.x86_64 from updates
The stderr output
Error: Protected multilib versions: libgfortran-4.6.3-2.fc16.x86_64
!= libgfortran-4.6.2-1.fc16.i686
Error: Protected multilib versions:
libstdc++-devel-4.6.2-1.fc16.i686 !=
libstdc++-devel-4.6.3-2.fc16.x86_64
Error: Protected multilib versions: libgomp-4.6.2-1.fc16.i686 !=
libgomp-4.6.3-2.fc16.x86_64
Error: Protected multilib versions: libstdc++-4.6.2-1.fc16.i686 !=
libstdc++-4.6.3-2.fc16.x86_64
Error: Protected multilib versions: libquadmath-4.6.2-1.fc16.i686
!= libquadmath-4.6.3-2.fc16.x86_64
+----------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
Guam Community College Computer Center
mailto:mikes@kuentos.guam.net
mailto:msetzerii@gmail.com
http://www.guam.net/home/mikes
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
SETI 11969293.719299 | EINSTEIN 7540627.629852
ROSETTA 4338248.975416 | ABC 11847529.608889
12 years, 2 months
akmod seemed to fail on newest kernel-3.3.0-4.fc16
by Donald Reader
I am running a fully updated f16 system on a dual core amd box.
Am wondering if this is a bug or something gone wrong with my box.
And if there might be a work around. This issue is way over my head
and any help would be much appreciated.
I have attached the failed log
12 years, 2 months
XFCE and Libre Office window title bar
by SternData
When I open multiple Libre Office documents, the first one appears
cleanly on screen. The second one opens with the title bar just below
the top menu bar for XFCE. It then jumps up to the top of the physical
screen, pushing the title bar behind XFCE's menu bar. To close that
window, I have to use ALT+F4 because I can't get to the "X".
Is anyone else seeing this? I'd like to see if it's just me before
posting to BZ.
--
-- Steve
12 years, 2 months
F17 Alpha: how to add a keyboard layout switcher widget?
by Fernando Cassia
I´ve been using Fedora 17 Alpha on a Dual-core Opteron server with ATI
X1600 gfx card and dual head display (two 19" LED LCD screens).
So far so good, but two notes, one on performance the other on usability:
1. Dragging windows across one screen to the other shows a noticiable
slowdown vs Fedora 16 XFCE (ie at some points I can see the window being
redrawn, wheres on XFE is moves smoothly with no visual artifacts).
I know the Gnome "weight" so to speak is much higher than XFCE but I also
wonder if perhaps this in an issue with X.org or the kernel. How to know?.
2. For the life of me I can´t find any way to add a widget to the top bar
to switch between keyboard layouts.
Any help?.
FC
--
During times of Universal Deceit, telling the truth becomes a revolutionary
act
- George Orwell
12 years, 2 months
