got my upgraded fedora 14 partition to boot, but I find out that I had to reinstall my nvidia driver, no big deal. seemed to go ok, but now when I go applications->system tools -> terminal I get the "starting terminal" thing on the bar, and then nothing. Can't figure out whats up.
View 4 RepliesLast nights upgrade of java-1.6.0-openjdk-1.6.0.0-43.1.8.2.fc13.i686 and java-1.6.0-openjdk-plugin-1.6.0.0-43.1.8.2.fc13.i686 prevent the loading of Ameritrades Command Center.Downgrading to version 1.6.0.0-37 fixes the problem. I'll post the bugzilla number as soon as I get the chance to file it.
View 3 Replies View RelatedI just installed FC13 on my laptop. I cannot upgrade from FF 3.6.7 to 3.6.8.
View 3 Replies View RelatedI upgraded from FC11 to FC13 last night. The desktop has not been stable since. It will run for anything from 5 to 30 minutes before it locks up. Interesting, if I am already ssh'd in, I can perform commands, but a new SSH will hang, and if I try to SU to root in an already logged in ssh, it hangs.
However, I did finally manage to get the messages that were logged to /var/log/messages at the time of the desktop freeze.
Here are the messages. The first 3 about high speed usb may or may not be relevant. The freeze appeared to happen around the 4th message in the log below.
Code:
Sep 2 13:16:57 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6
Sep 2 13:26:38 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6
Sep 2 13:31:20 starbug kernel: usb 2-4.2: reset high speed USB device using ehci_hcd and address 6
Sep 2 13:38:03 starbug kernel: INFO: task jbd2/dm-0-8:558 blocked for more than 120 seconds.
[Code].....
Took an FC12 system to FC13 via 'preupgrade'There was a REALLY old version of gimp-print-cups in RPM, and the installer announced "a fatal error occurred". However, everything else seemed to download properly and I allowed the upgrader to reboot the system.
a) grub boots the kernel, then the kernel can't find root and panics. It does this because it can't root file system with root=UUID= kernel option. If I manually tweek the grub line to use root=/dev/sdx, kernel finds its root and boots up to the next problem.
b) GUI environment not launched. Init scripts die on "error loading modules.dep". Sure enough - one is not there. Ran "depmod" to generate it ,and rebooted. System reboots into GUI, where I login to find the next problem.
c) Evolution won't start. Reason turns out the evolution-data-server from FC12 is still present. Did a check on just how many other FC12 RPM's are present: 1100. Yeah - over 1000. About 850 of the FC12 RPM's also had FC13 replacements installed. Did an "rpm -e" on these. Also had to do some remove action on mkinitrd, nash, plymouth-scripts-0.8.0, and parted-1.9.0 as there are replacements for these utilities under different package names. That cleaned up the system some, to present me with the next problem.
d) yum package repository still linked into FC12. Removed fedora-release-12-2.noarch and then I could "yum install" evolution and a few other packages properly.
I've done one other FC12->FC13 upgrade today, and that went flawlessly. So, I think in general the upgrade works fine. It just looks like if preupgrade finds anything amiss, it doesn't take care of a lot of things and generally leaves you with an unbootable mess to clean up.
I was having a job in /etc/event.d. It was working fine upto FC12. With upgrade to Fedora 13, it stopped working . Searching the internet, It looks like /etc/event.d is obsolete and I need to use /etc/init. Also the filename has to have a '.conf' extension. So I have renamed my job as /etc/init/svscan.conf.However, it fails to start automatically on reboot . It works if I manually issue the command % sudo /sbin/initctl emit qmailstartBut fails to start automatically on reboot. Is there anything wrong in my script below ? Let me know if I have missed out anything?
% cat /etc/init/svscan.conf
# svscan - runlevel compatibility
# WARNING: This file was auto-generated. Do not edit!
[code]....
I have a problem with LVM. My installation of Fedora 13 is on 2 SATA hard disks, which are set as /dev/sda and /dev/sdb. On sda there are two partitions (boot and a physical part of the volume group) and on sdb is only one partition (other physical part of the volume group). Both physical parts of the volume group are used for one volume group and the VG is splittet into multiple logical groups. The system works and all seems to be ok. But I saw a strange thing on last reboot:
The device /dev/sda was not recognized during the boot sequence, instead the system has build a device /dev/md126p1 with the same geometry and partitions and it has the same disk id as sda.
The volume group is also ok, the system boots into the desktop environment, but the system-config-lvm says that /dev/sda is not initialized and the volume group consists of sdb and md126p1. fdisk -l knows three devices (sda, sdb and md126p1). I think, that is the reason for my problems with preupgrade, which stops after the reboot with a LVM problem (root not found). Can I correct that without data loss?
I am unable to login to kde after upgrade to fc14 from fc13 as user , the splash screen works for seconds and returns back to login screen, but I am able to do as root
I also managed to login to KDE (failsafe session)
and also I am able to login as normal user to gnome desktop
I managed to successfully upgrade FC11 to FC13. While doing the post upgrade steps, I made a HUGE mistake. After identifying the unsupported packages, I used "yum remove package1 package2" command to remove the obsoleted ones without realizing the yum was also removing many FC13 packages! Here are the cmd sequence used:
# package-cleanup --orphans
...
# yum remove compat-db45-4.5.20-5.fc10.i386 flash-plugin-10.0.32.18-release.i386 gnome-spell-1.0.8-5.fc9.i386 ifd-egate-0.05-21.i586
[code]....
I simply typed Yes and left unattended for a few minutes after yum prompted there were # of packages to be removed as I blindly believed it would do the job. After returning to the computer, I found many installed icons were disappearing, the wireless suddenly turned off etc. I killed the yum process right away but it was too late.
-Is there anything I could do to undo the yum remove process?
-How to safely remove supported packages?
I have just upgraded my FC12 installation to FC13. The initial boot failed (just blank screen). Second time I received 'selinux targeted policy relabel is required'. I let that run, but still the boot did not suceed.
I then went in to verbose boot and saw that the boot would hang at libvirtd. So I disabled libvirtd for anything above run level 1. Next boot failed at atd, disabled atd. Next boot failed at 'monthly Smolt checkin'.
At that point and booted in to single user mode and dissabled SELinux, thinking that was the cause of all the problems. That did not help.
The update process has also removed my previous kernels, so I can't test a different kernel
Code:
$ su -c 'yum install wine'
this forum won't let me put all the text in Transaction Check Error: package openldap-2.4.21-6.fc13.x86_64 (which is newer than openldap-2.4.21-4.fc13.i686) is already installed package nss-softokn-freebl-3.12.4-19.fc13.x86_64 (which is newer than nss-softokn-freebl-3.12.4-17.fc13.i686) is already installed
Fedora (2.6.34.6-47.fc13.x86_64) I installed that update, during the installation process it said that it had to remove three packages, one of them was kmod nvidia for the old kernel (Fedora (2.6.33.8-149.fc13.x86_64))After the update finished installing the new kernel, I restarted the system and Nvidia did not load. (I assume because Update manager removed the old nvidia? But I also assumed that a new version would be installed automatically?)I received the following Boot messages:
Code:
Entering non-interactive startup
Starting monitoring for VG vg_user1: 3 logical volume(s) in volume group "vg_user1" monitored
[code]....
I'm confused, if Update Manager removed kmod nvidia, then why does yum say it is installed? And why doesn't the new kernel update work with that version? Or should I install a driver version for that particular kernel? I've read while searching that I need to install a kmod-nvidia for that particual kernel version and that I should login to my previous kernel until that happens, is that the problem I'm having?
Why don't rpmfusion and fedoraproject release the kmod-nvidia and kernel updates at the same time to avoid problems such as this? Does anyone know how long does it usually take for rpmfusion to release the new kmod-nvidia driver for the latest kernel?
I just installed FC13.It wiped out everything from the previous (FC11) installation. I cannot connect to the existing windows network that was working before. I don't see SAMBA so I downloaded and installed the RPM. I still don't see it on any of the menus. I am trying to connect to the existing Windows network
View 6 Replies View RelatedCan I migrate from fc12 to fc13 or do I have to do a full re-install? If I can migrate, can you point me to the instructions/working paper/etc.?
View 6 Replies View RelatedI have been running FC13 for some time now without any problems on my HP dc5800 Microtower. Recently I ran a software update, and when I rebooted the machine I got a blank screen with only a blinking underscore in the upper-left corner. Rebooted several times to no avail. I thought perhaps I had made a mistake, so I just reinstalled. I have tried reinstalling several times now with both 32-bit and 64-bit FC13, each time with the same result: everything works fine up until I install software updates; then after the next reboot I get a blank screen with the blinking underscore. I see the POST screen, and then it just goes blank. It doesn't seem to respond to any keyboard/mouse input; I eventually have to hold down the power button to make it power off.
View 5 Replies View RelatedI am trying to setup VNC server on FC13 box. i am not able to do proper configuration. Can anone point to me a good link which is working. I did many configurations. but no success yet. I have an issue especially with xstartup script. I am running VNC server on Linux and RealVNC viewer on Win Vista OS.When i try to connect to VNC server from RealVNC viewer from Win Vista. It gives error like "unable to connect to host: Connection timed out (10060)"
View 4 Replies View RelatedFollowing this from the wiki: It states Testing shows that upgrading within X will cause X to hang when installing bitmap-fonts-compat, but it can be done anyway by making sure that bitmap-fonts-compat is the last package to update. How do you ensure that its the last package to update?
First install the new fedora 13 gpg key. You may wish to verify this package against [URL] and the fedora ssl certificate.
rpm --import [URL]
Upgrade all packages with
yum update yum
yum clean all
yum --releasever=13 distro-sync
- Testing shows that upgrading within X will cause X to hang when installing bitmap-fonts-compat, but it can be done anyway by making sure that bitmap-fonts-compat is the last package to update ... YMMV.
- Intel video no longer works without Kernel Mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.
- nVidia video no longer works without kernel mode Setting (KMS). You must remove 'nomodeset' from your /etc/grub.conf kernel command line, if present.
- It may be necessary to run "db_recover -h /var/lib/ldap/ ; chown ldap:ldap /var/lib/ldap/*" once in order for slapd to start.
I have FC 13 with both KDE and Gnome loaded. Over the last couple of years of using linux. I've found Gnome better suitable for my needs than KDE and now I'm stuck!
View 6 Replies View RelatedI did a fresh FC13 install on a computer and after trying to install the nvidia drivers the machine hangs on starting atd when it boots.Initially, I tried to install the nvidia drivers with yum but it didn't work. The nvidia module was not loading and although I blakclisted the nouveua driver the machine was still picking it up. Anyway after spending a lot of time trying to find a solution online, I decided to download the drivers from nvidia and install it myself.So I did that, run sh <nvidia-package>.run and the installation was completed without any complaints. Since then the machine hangs when I booted it up. Also I don't see any errors in var/log/messages or in /Xorg.0.logHere is my grub.conf:
Code: default=0
timeout=0
splashimage=(hd0,0)/grub/splash.xpm.gz
[code]....
I have just updated to FC 13 (64 bit), and there seems to be a problem with Jabber in Kopete. I use this to connect to the google talk servers. In FC 12 this was not a problem. However, now I recieve a message "Cannot load the Jabber protocol plugin." when trying to add a Jabber account in kopete. This happens on two separate recently upgraded machines.
I suspect the kdenetwork package shipped with FC 13 is broken in this respect.
EDIT: Updating to the kde packages from the kde-testing repository fixes this, so it looks like the package is indeed broken.
I have a fresh install of FC13, nVidia 9800 GTX+ video card but no 3D.
View 4 Replies View RelatedI have a mivvy l310 netbook. Before I had FC12 on it and I couldn't upgrade (not enough space on /boot, tried all commands and it didn't worked) to FC13. So I said I would do a fresh install for FC13. I used live CD FC 13 iso to make the usb drive (16gb) bootable.It boots, all goes ok, untill the installation is in progress of copying files to my HDD (at this point my HDD is empty, since it was formated). At about half of the progress bar of copying the installation files to HDD it stops with: ""There was an error installing the live image to your hard drive. This could be due to bad media. Please verify your installation media."" I can't go further and install it. I tried making the usb drive on FC13 (finished successfully, on another laptop with liveusb creator) and also on SUSE and it behaves the same.
I also tried second method (described in a thread around here, it worked for me in the past for FC11), by just making the usb drive bootable, using commands in the terminal (here my FC13 kernel, on another laptop crashes, for some commands) and when I try to install I get only: "missing operating system, sleeping forever". For this method, it does not boot at all, so I guess the usb drive is not properly setup. I don't know what else to try. I tried normal dvd iso, live cd, tried making the usb using commands, using live cd, with commands on suse, on FC13 etc...
LE: I found in messages log that I have: zlib_inflate error fc13
LE LE: what's more weird is that I downloaded the same live image of FC13 and burned it on a CD and managed to install it on my other laptop and it worked.
Later update: I tried now with the DVD iso for FC13 and now I get: operating system not found
I have a GeForce 7100 GS Nvidia card (that is, a 2 year old card: not old, not new), that I always used with the kmod-nvidia kernel modules without a problem.But FC13 installs nouveau, drivers for nvidia cards. I tried those, and glx is too slow. Foobilliard and gl-117 games are VERY slow, glxgears shows 400 fps. Is there a xorg.conf trick?
View 3 Replies View RelatedI installed pidgin 2.6.6 on fedora 13 and setup as following:
protocol: yahoo
pager server : scsa.msg.yahoo.com
port: 5050
file transfer server: filetransfer.msg.yahoo.com
file transfer port: 80
[Code].....
Post upgrade from 12-13 my Banshee installation is refusing to play CDs. In fact it doesn't even recognise there is one in the drive.
The icon appears on the desktop ok when I put on in and I get asked what I want to use to open it so it seems the system itself recognises a CD but for some reason Banshee doesn't.
I got an error about Banshee needing CD Audio Plugin, which I told Banshee to try and find but it failed. No idea where to go from here.
Worked it back to gstreamer-plugins-bad / ugly packages were wanted. So removed with yum then allowed banshee to try finding them.
It got as far as asking for root auth which I gave it, it them fell over in a heap.
Now it seems banhsee is no longer on my system and has some dependency issues....
[root@bigfoot log]# yum install banshee
Loaded plugins: presto, refresh-packagekit
Setting up Install Process
Resolving Dependencies
--> Running transaction check
[Code]....
I am using FC13 (2.6.33.6-147.2.4.fc13.x86_64) with a ASUS MB/Athlon II X4 CPU for the hardware.Recently my workstation keeps freezing, the power is still on, but the screen goes black,I cannot ping it from other computers on the network, the only thing to do is to press the power switch.
Questions:
* I cannot find any messages in the log, no kernel panic message on the screen, I even installed kdump but no kernel dump is created,does it means it can only be a hardware problem ? I have a vendor kernel module for my NIC and my video card could they cause that kind of problem ?
* I am logging the CPU temp every minutes and I notice that on a few occasion the CPU is close to 70C when the workstation freeze,is 70C too hot for the CPU, is that what CPU do when they reach a temp to high for them to operates ?
Recently I upgraded my kernel to 2.6.34.6-47.fc13.x86_64 and then also did an update to 2.6.34.6-47.fc13.x86_64. Both of these kernels I do not get a login dialogue box. I still have the one kernel that works and it is 2.6.33.8-149.fc13.x86_64. The system I am on has a Radeon graphics card, but I don't think the graphics card is the issue since I get the login screen's background, but not the login screen itself. <Later> After messing around with this for a while I came to the conclusion that livna-config-display was messing with the xorg.conf file. Removed it and things seem to be working fine now.
View 1 Replies View Related2.6.34.6-54.fc13.i686mplayer is install. Most of what I find on the web is playable but if someone sends me a wmv file, I save it and run > mplayer abc.wmv. mplayer pops up, looks like everything is ..... and just sits there - black screen - click on the play> button - blink - nothing.
View 5 Replies View RelatedBefore buying an HP DL380 G5 (Intel Xeon 2 or 4 core) I need to be sure. Does anybody have installed succesfully FC12 or FC13 on this hardware? I could not find an HCL for FC12 or FC13.
View 3 Replies View RelatedWe have several FC machines (from 6 to 12) that use an OpenLDAP server running on Centos 5.4 for authentication. I have now tried setting up a FC13 workstation. I notice that the authentication GUI has changed and wants me to use Kerberos or a TLS enabled server. Is there a way to get FC13 to behave like FC12 in this respect. Or (less desirable) what changes do I have to make to the server to accommodate FC13?
The workstation knows who the users are, but will not authenticate if they try and log in.
[URL]
but it didn't work for me