I upgrade from FC12 to FC14 on Monday last. Yesterday, I noticed that CUPS wasn't running, so I looked at services and started it manually. The services appeared to be set to start CUPS automatically, but today again it wasn't running. Looking at messages, I now have the following 'errors' that appear to be disabling CUPS due to some form of load dependency.
Message log extract:
[code]....
I'm planing to upgrade from FC11 to FC14 using a preupgrade. I've read about some ways to overcome the problem of my /boot partition being only 200MB in size while the newer versions require 500MB. The option of "filling the free space on the boot partition to be less than 100MB to cause preupgrade to download the loader" appeals to me. But what I don't understand is: is the 500MB requirement of the new versions is transient during the install or a permanent requirement? If I do this trick of first filling up the free space on /boot then freeing it up before the reboot, what will be the permanent disk space requirement of FC14?
Are there any safe (and prefarably simple) ways to increase the size of the /boot partition after decreasing the size of other partition? Here is the output of "df" relevant to the /dev/sda disk:
Code:
i have just upgraded from f14 to f15 using preupgrade. i am now still waiting for the first boot to finish. the screen is stuck for more than an hour and the last line written was:
Started LSB: Start up the OpenSSH server daemon. and there is a blinking cursor.
I was recently messing around with the partitions on my tri-boot system and ultimately messed everything up. After a few hours of tinkering I was able to recover but learned something interesting in the process.Something has changed with FDISK, or some underlying component, from FC12 to FC14. I keep partition backups so when I mess things up, I restore using dd. Anyway I think I was restoring partitions at the wrong starting blocks as some partitions worked while others did not. I just happened to notice the start for sda1 on FC14 and said to myself, that's not right.
Anyway take a look as the 'fdisk -l /dev/sda' for FC12 and FC14. What gives? My backups were all made on an FC12 install and when I restored from an FC12 boot CD all is well. Anyone know what the deal is? Should I recreate all my backups again using FC14? Not sure how the boot sector is affected with this FC14 sda1 start at 64.
HTML Code:
*** FC12 x64
Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[code]....
I have with the Videocard of one of my laptops. This laptop has a Mobility Radeon X600 card (RV380 based). I always had 3D hardware acceleration with mesa (at least in Fedora 12 and 13), but now it doesn't work. Boot seems normal, but reviewing the logs, I see this in the Xorg.0.log (after loading the radeon modues):
[Code]....
I don't have hardware acceleration, so no compositing and no gnome-shell I tried with both 7.9.1 and 7.9.2 versions of mesa-dri-driver (and its libs). The xorg-x11-drv-ati version is 6.13.1-0.3.20100705git37b348059.fc14
From at leat FC12 to FC14, I notice that the form we have to fill in to write a filename (for example) don't give anymore the choice of the file which already exist in the current directory.I explain :Use gimp or geditCreate a simple file : example.txt or xample.jpgnd save this fileclose this filecreate now a new filetry to save it under the name: exand in FC9, the system added one line to propose you example.txt because example match with ex you just typedin FC14, this proposal doesn't exist anymore.How to setup it again ?I am working with gnome but the problem is the same with kde
View 2 Replies View RelatedI upgraded from FC12 to FC14 and now the system/case fan blows full speed constantly. I also moved from i386-PAE to am64.
The CPUs are cool, the machine is basically idle, and the fan noise is really annoying (and blowing cool air).
In FC12 the fan would auto-adjust with CPU load. This is not the case now.
I ran sensors-detect and it doesn't seem to find my fans:
[root@pangea modprobe.d]# sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +40.0C (crit = +75.0�C)
k8temp-pci-00c3
Adapter: PCI adapter
code....
I don't remember ever having to even run sensors-detect in FC12. I searched the board for a bit and didn't see any solutions. I'll attach the full output from sensors-detect.
I have a tricky problem which I could soIve with a c program. I wrote one and found I didnt have gcc so I tried to install it. I was told I needed to install packages. I acknowledged and an error was generated gcc-4.4.2-7.fc12.i686 requires libgomp = 4.4.2-7.fc12 I try to install libgomp and go round again.
View 2 Replies View Relatedafter upgrading to FC14, i'm getting this when I run emacs file.sh:
GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)
Fatal error (6)Aborted (core dumped) This only happen when i'm logged in as root, on the Terminal session. As a regular user, or launching emacs from task bar icon don't happen.
I'm having some issues upgrading my F9 to F12 using 'preupgrade' so I'm looking for anybody who has ever been able to complete a preupgrade from F9 x86_64 to F12. The error message I receive is TypeError: Parsing primary.xml error: attributes construct error. To my knowledge this has been reported as a bug in F10 which was resolved by a yum update to version 3.2.24.
For F9 the latest yum version is 3.2.21 which has this Parsing error bug that prevents the preupgarde to continue. Interesting enough that the preupgarde lets me select Fedora 12 and progresses with all the preupgrade steps properly until the parsing error occur. How to fix this Parsing error on a F9 x86_64 system.
when i want run "ltsp-build-client" command i get this error: ERROR: fc14 is unsupported i want know there is any plan for ltsp 5.2 support in fedora 14 and how i can solve this problem for use ltsp in fedora 14.
View 2 Replies View RelatedI have work through fedora project guides and got these messages beneath.
[code]...
Dell Studio 1555 (Wireless WLAN 1397 Half MiniCard (4312bg)) I'd tried
Code:
# akmods --force
5.100.82.38-1-for-2.6.38.6-27.fc15.i686.PAE.failed.log is attached. How to build akmods?
Having trouble with ffmpeg install using fc14. [solved]#yum install ffmpeg . . . gives the following error:
Finished Dependency Resolution Error: Package: libavcodec52-0.6.1-38_git20110115.fc14.i686 (atrpms) Requires: libva-0.31.1.1.so.1
it's the installation media or the ISO is broken because i have reburned / redownloaded the fedora14 multiple times with the same result. I even tried burning the disc on a different computer just to make sure the burner is still working. This is the error i am getting when the "Starting installation Process" dialog displayed.
"The file upstart-sysvint.0.65.9.fc14.i686.rpm cannot be opened. This is due to a missing file, a corrupt package or corrupt media. Please verify your installation source" I remember fedora 13 and below i have to use nousb command or something similar to get fedora installed properly but not for fedora 14. It just pops up with the message above.
i recently installed the banshee media player using yum extender. Everytime i run it i get this error " a crash in mono-core-2.4.2.3-2.fc12 has been detected" how can i fix this problem?
View 2 Replies View RelatedI have installed Fedora Core 12 and all seems fine. I have also set up the main repositories as was suggested on the following fedora set up guide website: [URL]. I have since tried to update my Fedora release with all the updates available, alas I get the following error message:
Error Type: <class 'yum.Errors.RepoError'>
Error Value: Error getting repository data for installed, repository not found
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in <module>
main()
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main
backend.dispatcher(sys.argv[1:])
File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 710, in dispatcher
self.dispatch_command(args[0], args[1:])
File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 657, in dispatch_command
self.update_packages(only_trusted, package_ids)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1948, in update_packages
signed = self._is_package_repo_signed(pkg)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1437, in _is_package_repo_signed
repo = self.yumbase.repos.getRepo(pkg.repoid)
File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo
'Error getting repository data for $s, repository not found' $ (repoid)
The relevant details of my setup are:
Samsung R522 laptop
Realtek RTL8192E wireless network controller (PCI)
Fedora 12, kernel 2.6.32.9-70.fc12.i686 (automatically updated using software update)
My problem is that my wireless card has never worked - basically there aren't any widely available linux drivers, and there are many threads on getting the RTL8192E to work on many different forums, e.g. here, but none specifically for Fedora, so I think that this thread could potentially guide many more users. FYI, my hardwired network connection works perfectly.
Fantastically however, by emailing Realtek support, they'll send you their Linux driver, which most people have claimed works perfectly (although why they haven't just put it on their website is beyond me). SO, I've got a Linux driver for my wireless card. When Realtek emailed me to send me the driver, they said to just 'cd' into the driver directory, then do
su
make clean
make
make install
reboot
./wlan0up or ./wlan1up
OK, so I tried to do this and get the following error:
make: *** /lib/modules/2.6.32.9-70.fc12.i686/build: No such file or directory. Stop.
make: *** [all] Error 2
I don't know enough about linux to understand this error. I really don't want to have to recompile my kernel, and I hope there is some way to install this driver with not too much hassle. How to overcome this error, and install my wireless driver so I can get wireless network access on my Fedora 12 operating system. I've found Fedora 12 really easy to use so far, but this is proving quite hard!
This is the output of 'ls -lh' in the folder which seems to be causing the error, namely /lib/modules/2.6.32.9-70.fc12.i686/
total 3.1M
lrwxrwxrwx 1 root root 46 2010-03-16 22:53 build -> ../../../usr/src/kernels/2.6.32.9-70.fc12.i686
drwxr-xr-x 2 root root 4.0K 2010-03-03 05:28 extra
drwxr-xr-x 11 root root 4.0K 2010-03-16 22:53 kernel
-rw-r--r-- 1 root root 498K 2010-03-16 22:53 modules.alias .....
Today's update failed with this line tagged to every package:
Error: Unresolvable requirement /sbin/ldconfig for pixman-0.16.2-1.fc12.x86_64 (installed)
Error: Unresolvable requirement /sbin/ldconfig for libXrandr-1.3.0-3.fc12.x86_64 (installed)
Error: Unresolvable requirement /sbin/ldconfig for libedit-2.11-4.20080712cvs.fc12.x86_64 (installed)
[code]....
i tried running (yum update, also yum install vlc) and i get these error
Code:
Error: Package: abrt-1.0.7-1.fc12.i686 (updates-testing)
Requires: librpm.so.0
Removing: rpm-libs-4.7.1-6.fc12.i686 (@anaconda-InstallationRepo-200911081854.i386)
[code]....
I`m having a problem with upgrading my Fedora 11 to either Fedora 12 or Fedora 13. When i start preupgrade, it lists all packages that need to be upgraded, but then it ends with the message that none of the mirrors can be found. I`m seeing the messages in the console, and indeed all the mirrors return "HTTP Error 404: Not Found". Any idea how to change this and eventually do an upgrade?. I also downloaded the Fedora 13 DVD, and tried to upgrade that way, but it never showed me the window which must give me the option to upgrade instead of doing a fresh install. The explanation in the official website clearly shows that this window exist, but after several tries with the DVD I did not get it.
View 1 Replies View Relatedwhen ever i try to install updates i get shown an error & the updates stop the error i get says "librpmio.so.0 is needed by package abrt-1.0.3-1.fc12.i686 (updates) librpm.so.0 is needed by package abrt-1.0.3-1.fc12.i686 (updates)"
View 12 Replies View RelatedRecently, after upgrading from FC11 to FC14 I checked my bluray burner (relevant lines from dmesg):
[code]...
got empty output, which means: all files are identical. I can set the post-write verification to "off" but I prefer it "on" when backing up important data. Does this error familiar? how to solve it or, at least, where to look for messages that might have a hint as to what's wrong
this is the error i got when i type yum update command
Code:
[root@VAIO yum.repos.d]# yum update
Loaded plugins: presto, refresh-packagekit
http://download.fedoraproject.org/pub/fedora/linux/updates/12/i386/repodata/repomd.xml: [Errno 14] HTTP Error 302 : http://download.fedoraproject.org
[Code]....
I am interesting in hearing from anyone who has used preupgrade to upgrade from f13 to f14.
View 14 Replies View RelatedI'm not an early adopter; i prefer to wait and see, and let others suffer the new distro's teething troubles. Finally, I decided to try preupgrade. I was a little astonished to find that it doesn't install itself to any menu, but that's OK. I ran it as root, and went on with what I was doing while it got ready. Eventually it prompted me to reboot and I did.
I'd like to say that everything went fine, and in about an hour, I had a working system with no glitches. Alas, that would be a lie. Not only did it change all my customized system sounds (with no apparent way of getting back what I want; the new sounds aren't selectable.) it replaced my carefully-tweaked fstab with one of its own. This mean that several partitions that I don't want mounted were. Not only that, in some cases right-click and unmount got a message that the partition wasn't mounted, even though I could browse it. I had to open a terminal and manually unmount them, followed by copying back my fstab to keep this from happening again.
While doing this, I learned that the arrow keys on my keyboard don't work right, with the up arrow mapped to screen shot, and the Enter key by the number pad disabled. I'm still working around that one.
Worst was that Firefox wouldn't open. Trying it from a terminal, I learned that it couldn't start XCOM. Weird.
I tried a system update, but the livna issue popped up. By good luck, I knew enough to locate the appropriate file and disable it. Yumex has been spending over four hours, downloading and installing more updates than preupgrade did, by almost 100%.
failure: repodata/3a2a6da78e69f9b2608b1c399561b99073baa86b5454618459 ceecb79d58da09-filelists.sqlite.bz2 from preupgrade-updates: [Errno 256] No more mirrors to try.
I receive this error when I run try to run preupgrade to go from F12 to F13.
It's definitely not an issue with my internet connection, I'm running this from a college campus with a 150mbps connection.
I've tried running it 3 times now, and get this every time. It also gives me the error about not enough space on the boot partition, so I press continue there to move on.
just upgraded fc12 -> fc13 with preupgrade. all seems well except for network manager icon missing from the systemtray and therefor unable to connect to wifi. uninstalled network manager and reinstaled but to no avail. wifi is a bcm4318 airforce one btw, broadcom kernel stuff is loaded but maybe in fc13 its supported in the kernel now?
View 4 Replies View Relatedif I can upgrade my fedora fedora 12 to 14, using preupgrade?
View 1 Replies View RelatedGoing from Fedora 12 to 13. Got to the point where I have to reboot to install, system reboots to 12. This is a triple boot system with Open Suse and Mint, and the grub2 bootloader from Mint is the bootloader for the whole shebang. In the "how to use preupgrade" instructions there's a line that says "dentify the drive and partition of your Fedora /boot folder." How? If that sounds odd, consider that in my set up "computer" shows 4 partitions (and with just three operating systems..?). I can mount them, but have a problem telling which sytem is Fedora, Suse or Mint. And getting the FEDORA bootloader to find the PREUPGRADE kernel ... Momma said there'd be days like this.
cat /etc/fstab just returned /dev/sda1 on /boot. I installed Fedora first, before Suse or Mint, so being on the first drive or partition sounds right, but the multiple drives throws me, and "just guessing" doesn't seem like the way to go.