Fedora :: FC13 'yum Update' Aborts Wth Bogus Compaint About Size Of / Boot
Jul 4, 2010
An a stable FC13 system, after resolving deps and downloading rpms, 'yum update' aborts with this single error message:Transaction Check Error:installing package kernel-PAE-2.6.33.5-124.fc13.i686 needs 801KB on the /boot filesystem.Silly thing is, I have at least 52MB available on /boot.An important datapoint is that I resized the boot partition since the initial install from 64MB to 128MB, which makes me think perhaps yum or anaconda recorded the original partition size, and is not looking at the current (correct) size of /boot.
I 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.
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.
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?
Just installed fresh FC14. I built/installed a project with some new man-pages. I'd like to update the apropos/man database. makewhatis was still present in FC13.
Googled this and found the same problem mentioned in the yum site: [root@plouton ~]# yum update kernel Loaded plugins: refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:2.6.33.6-147.fc13 set to be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:2.6.33.4-95.fc13 set to be erased --> Finished Dependency Resolution Dependencies Resolved
I'm a bit of a Linux novice but have taken the plunge and got a old Dell machine set up with Fedora 13, it works fine for the most part. If I can get it to boot. Whenever I start it up the tri-color boot bars go across the screen but seem to freeze at various times. Sometimes right as its getting started, other times it will go all the way across but never actually do anything. I can sometimes get it to work if I get into GRUB and try a different kernel version. Is there anyway to pull up a more informative boot screen or some other way of figuring out whats causing the freeze instead of just watching the progress bar?
Performed the daily update, don't recall which packages were available, and the boot process freezes near the end upon trying to start my VNC server. Using rescue disk removed tiger-vnc server. Oddly upon reboot, selinux reset the files even though initial setting was 'permissive'. have not tried re-installed vnc yet.
Ever since I have upgraded form fc 11 to 14, I cannot login using the KDE desktop, I am forced to use gnome. The problem with that is that KDE apps are not running well, slow and often crashing, when I try to use them under gnome.
Symptoms.
1. Attempting to log in as any user with either KDE or KDE failsafe selected brings up the KDE splash screen, the hard drive icon, and occasionally the wrench icon.. a long pause and then back to the login screen.
2. I have these problem described in other Linux forums and have attempted to implement their recommendations
2.1 Deleted the .kde and other directories associated with KDE, reinstalled KDE. 2.2 Checked the permissions on all the requisite files and directories to ensure that they were good. 2.4 Looked through endless log files for ANY clues.. none
3. KDE applications, like ocular, take about a minute to start up, respond very slowly and eventually stop responding. Gnome applications work normally.
Now, all of a sudden, after I restarted after a system update, My dell desktop inspiron hangs on boot. The kernel is: 2.6.34.8-68.fc13.i686. Not only that, but the system won't boot for any of the remaining previous kernels.
I'm running Ubuntu Lucid formatted ext3. It boots with Grub (old Grub) in sdb6 (hd1,5) It mounts at /, and its partition, sdb6. is flagged boot.
I created a new partition for Fedora 13, 64bit. I installed Fedora in sdb8 (hd1,7), formatted ext4, and created a separate /home in sdb7, formatted ext3, so I might share it with Ubuntu, in sdb6.
Fedora installed with Grub2. It booted fine, and after adjusting references in fstab Ubuntu booted OK too, but rather roughly.
That is when I shifted the boot flag to the Ubuntu partition. So now the original Ubuntu Grub is handling boot once again. Ubuntu boots as before, but I can't get Ubuntu's Grub to boot Fedora. An earlier post suggested this code, which generated error 13, Invalid or inappropriate executable:
Code:
I tried the following code, pasted from the Fedora Grub, but it doesn't work either:
Code:
I've got alternative lines invoking the kernel, because someone had suggested omitting the direct reference to root= ....
Either way I get error 2 - Bad File or directory.
I suspect the problem may be that I'm booting Grub in an ext3 partition and trying to invoke Fedora in an ext4 partition. Does anyone know if that is the likely cause of my problem? If so I can reinstall Fedora formatted ext3.
Alternatively, can I create a Fedora /boot partition, and move/reinstall Grub there? Either way -- should I use old Grub, so both Grubs are the same?
Should I have assigned mount points to sdb8 (Fedora) and sdb7 (home)? Currently I'm not using sdb7 at all.
I'll attach a screenshot from GParted of my partitions.
Having just installed fc13 and downloaded the KDE package I attempted to log out as user and back in as root, but I keep getting a message about the wrong password. This is odd as the same password works in terminal if I try to become a SuperUser. I have tried turning off SELinux to no avail. I cannot log in from cold as root,only as user.
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
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
having a weird problem with my wireless connection on a Dell Latitude E6400 laptop.This machine has a Dell 1510 half-card. It uses a Broadcom chipset.I've gotten to the point where fedora sees the card, and I can create wireless connections. But every time I try to connect to a network, it scans, connects, and disconnects several times, until it gets a completely bogus IP address, that has nothing to do with any of the networks onnect to. It is always "10.42.43.1", yet I have no static configuration for that address.
I want to update my fedora (Yum update), but not all of the packages in repositories! Only packages that have size<1MB ! How can I do it? Does have YUM this ability?
Last 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.
How come on x11vnc, with Fedora 12 PPC/x86/x64, my screen sizes can't be greater than 800 x 600, and they don't update when I change them in Displays. On my Ubuntu installations the x11vnc screen sizes update and can be basically any size selectable in Monitors.
I've got a Dell Latitude E6510. I've got FC13 and Windows 7 dual booting on the machine. Both were living in harmony with one another, no problem. Only issue I was having, was that when I plugged my external 19" dell monitor, my linux would do 1 of 2 things..
1) if plugged up prior to boot, it would black screen after the fedora boot screen that shows the blue heart
2) if plugged up post boot, it would freeze the computer
The last thing I did to troubleshoot the issues was install system-display-config, maximized the screen resolution in the settings of that app, and set the resolution to 1650 x 900 (i think it was 900, not sure). After reboot, I now get the screen below after the fc blue heart screen loads.
When I installed fedora I told the installation routine to use the free hard disk space. I had 98gb of free space. After the installation I look under the MyComputer icon checked the free space which is 45gb. Well I have a hard time believing that I have used half of 98gb already. There must be something going on here.Also.. With regards to the boot manager. It made Fedora the default OS. While I don't really have a problem with that is there a way to change it so that my other OS is the default? I use two operating systems and sometimes one week I'm using one primarily and then things will change.
I am trying to setup 2-factor authentication for SSH with PAM. Its working well, but if the password is incorrect, it does not ask for validation code, but rather asks for the password again. Any way not to warn about an incorrect password?
I am new to this and just got a SUN Netra 440MHz T1 105 with 512MB RAM, 2 19G SCSI drives and a IDE CDROM.I am having trouble loading Ubuntu 9.05 server iso via the CDROM. The CDROM driver does not get found and the installation aborts. The CDROM is a 24x toshiba XM-7002B.I can load the old Ubuntu server 7.10 but cannot update it. (would need some help to do that, too).
I've used NoMachine's NX software for some time, but on one of my machines it simply will not work. At first it did, but now when I log in it authenticates, starts downloading a session, but then drops dead. There is no hint of what the problem may be except in /var/log/messages on the server machine:
User 'bill' from '192.168.1.1' logged out. 'NXLogin::reset'
Notice that it's a login reset, after authentication went fine. Researching this I find the problem is often caused by a missing fixed font, which is remedied with an: # apt-get install xfonts-base --reinstall but that doesn't help. I have completely deinstalled and purged the three Nomachine packages on the server, deleting all associated directories, and reinstalled them, but no help. From my client machine I can log into a NX session just fine, so I'm sure it's not the client machine. The Linux version of this software has a limit of 2 sessions, and I suspect the server may have some bogus sessions open, but where? I've done a purge and deleted /usr/NX and /home/bill/.nx so where else could this be?
I am using using Red Hat Enterprise Linux ES release 3 (Taroon) dhcp server ver: dhcp-3.0pl2-6.14
I am trying to bind macid 00-21-6B-A1-C9-4C & 00-15-00-1D-AD-57; but it give, when I start dhcp service, I get the following error messages. I am sure macid are absolutely correct. Following the error message I get.
Starting dhcpd: Internet Software Consortium DHCP Server V3.0pl2 Copyright 1995-2003 Internet Software Consortium. All rights reserved. For info, please visit [URL] /etc/dhcpd.conf line 2196: Bogus number: 00-21-6B-A1-C9-4C. hardware ethernet 00-21-6B-A1-C9-4C; Configuration file errors encountered -- exiting
is lvresize with --resizefs options re-size the Logical Volume and then re-size the file system? i mean we don't need to use resize2fs?I looked at man pages but it doesn't explain this option.
i m using Centos 5.4 Dovecot and Sendmail serve my secondary server have some problems and shwoing me BOGUS files in var/mail
m using Centos 5.4 wiht dovecot and Sendmail my all users receiving a message 20times every time when they press their send/receive button three messages are repeating on every system i deleted all mail from my accounts but some of my accounts facing this problem
i have another problem when i insert my Cd or DVd in DVDwrite on my server and mount him mount /dev/scd0 ---- it dispaly that dev/scd0 does not exist in et/fstab i tried it clicking on DVDWriter Mount but seems error no media,..
I've been banging my head against the screen on this strange problem. Somehow my server sends out spam mails to a lot of aol mail addressess. The mail.log file looks like:
