I upgraded from f13 to f14 and now i get this message after booting up. I am at a loss as to what to do to clear it.
Code:
cat: /proc/self/attr/current: Invalid argument
Welcome to Fedora
Starting udev: udevd[478]: SYSFS{}= will be removed in a future udev version,
[Code].....
I just upgraded to mediawiki-1.16.4-58.fc13.x86_64 on my fedora box and did:
Code:
Now I get 403 Forbidden message when I access.
I find several config files related to mediawiki, and modified them, but I still see 403.
After asking on both this forum and the Fedora forum, I felt it was safe enough to install a copy of Fedora on my working-well openSUSE drive. I have a 1 TB drive, partitioned as follows:
I did an install of Fedora 13, was VERY careful to set up the installer to put it's files in the partitions I wanted, although I did let it mark the partition as active, feeling it may have to boot during the installation process.
I had grub installed in the root of the partition rather than the MBR for both systems.
When Fedora finished installing, I rebooted the system only to find that it wouldn't. I got the dreaded "No Boot Device" message.
So, I started the 5 hour process of booting with the parted magic disk, booting with a Gentoo live disk (only one around), monkeying with the install parts of the openSUSE and Fedora disks, swapping drives to Windows to download openSUSE Live CDs (yes, both) and searching the forums and various other web sites for some poor bloke who did the same stupid whatever it was I did, and finally, as I was using fdisk on the Gnome Live CD, I noticed the warning message stating that fdisk would not work on a drive that was partitioned with the GPD format.
Notice that I have 5 partitions? That is not a typo on my part, I used the GPD format when I set it up so I could do what I did without using "imitation" partitions.
When I used parted (the command line editor on the Gnome Live CD) to change the active partition, everything started working again! Well, at least I can boot the openSUSE system, the most important thing.
It is my suspicion that the Fedora install uses fdisk to do it's work, and fdisk just mucks up a GPD formatted disk. Not the information, just the part of the drive that holds the partition table. Perhaps just the flags section. I don't know enough to say with any certainty.
I didn't change the drives parameters during the installation of Fedora, so I don't know of it even offers the GPD partitioning option. If not, I can understand how this sort of thing could happen.
Still....So now all I have to do is make the grub menu, the one installed with openSUSE, boot the Fedora installation on the next partition. Seems simple enough.
I'm trying to upgrade from 9.10 to 10.04 LTS I've followed [URL] Everything is updated. But, i don't receive the message "New Ubuntu release..." Will I have to download the entire DVD?
View 7 Replies View Relatedi'm heaving the following message at boot time: "Starting udev: udevd[114]: unknown key 'DEVTYPE' in /etc/udev/rules.d/70-cups-libusb.rules:6", i guess it's something about usb printing support but i am not sure, and i don't know how to fix it, does any of you guys know what this exactly means and how to fix it
View 6 Replies View RelatedEvery time I boot up FC13 I get a boot message which is showing a failed task. The line is as follows:
Enabling the nvidia driver: /etc/rc.d/init.d/functions: line 530: 1174 Segmentation fault "$@"[FAILED]
Everything appears to be running fine on my system. This message is more nuisance that a functionality message. But I could be wrong.
I upgrade my f13 to f14 with preupgrade but after that i give this boot message.how can i fix this error?
Code...
how can i fix this error?
I'm new to fedora and when I boot from a cd I get the message: could not find kernel image. I currently have windows xp and my motherboard is and ix38 quad gt if that helps.
View 2 Replies View RelatedI've been fiddling about with vortexbox (the one before 1.4 I think), for a while. This is a music ripping and server rpm setup using Fedora 11 as the base.
As it was on a test machine, decided to try changing the logical volume sizes of LogVol00 and LogVol02 to fit a few more cd's on 02 before getting a new pc (just to see how it works).
Logged on and opened up the graphic version of lvm (using gnome). Then selected the LogVol02 logical volume, select edit, changed name to LogVol02-Storage, saved and logged out. Rebooted vortexbox since then its been unable to start properly (is this a kernel panic?).
Read up a lot on lvm on the net, have access to Fedora 11 disk 1, so logged on. Eventually managed (I thought to) to change LogVol02-Storage to LogVol02 using lvrename.
However, still refuses to boot completely.
The message it gives is as follows (sort of): Welcome to Fedora Press '1' to enter interactive startup
Setting up Logical Volume Management: 3 logical volume(s) in volume group 'VolGroup00' now active
*** An error occurred during file system check.
*** Droping you to a shell; the system will reboot when you leave the shell.
Give root password for maintenance (or type Control-D to continue):
Loving vortexbox appart from this. Will it be easier just to reinstall everything? If so, is there a way of listing all the changes I've done so I can reproduce (I'm thinking of just looking at all the commands I ran on the CLI).
Otherwise, is there a way of listing all of the commands I ran in terminal and piping them into a file so I can see what I need to do to rebuild after reinstalling?
I have a fresh computer with specs as such:
Hard Drive: Western Digital Caviar Black 500Gb 6Gbs Sata
Asus Sata DVD/CD Burner
Core i3 3.3GHz Sandy Bridge chipset
MSI P67A-GD55 Motherboard
Zotac GTS 450
I have a problem where the live cd gives this error message:
Boot failure, sleeping forever.
I'm currently trying to get to the root of an problem on startup; unfortunatly when booting after the first couple of messages when booting without quiet and with nosplash in the grub menu I still end up with the nice blue background and the slowly filling bubble... I'd like to go back to the old, boring, messy, but much loved and now much missed (least by me) text boot screen where I can see wtf my system is doing and where its hanging during the boot process.
(I know the cause of the hang now but still want to go back to the old fashioned noisy boot environment - not a fan of the windows style silent boot... I like to know what's going on and that my PC hasn't decided to join the French and go on strike, though wouldn't blame my poor netbook if it has, hammering the bleeper doing random number analysis - not something an atom 270 is designed for)
I tried to dual boot Fedora on a vista system. Now fedora boots as primary and when i try to boot vista i get the message, bootmgr missing control, alt, delete to restart.
View 10 Replies View RelatedHi I am running a fedora 10 desktop. when i send an email using evolution the message was not sent but returns a error message:"Error while performing operation.DATA command failedError: 550 Viagra SPAM - Hi in Subject" and the message did not have an attachment just plain words. what might have gone wrong for i have been using this for sometime without a problem. or what security measures should be in place to remove this viagra spamAm I infected by virus on this fedora, all my updates are up to date.
View 1 Replies View RelatedThis is probably a pretty basic question - a little embarrassing because I am not totally new to Debian. I am installing Squeeze on my Acer netbook. I am using an iso image that is a few months old, so once the system was installed I ran aptitude update and upgrade which fetched a lot of upgrades. During the install a message pops up regarding initramfs-tools that states: To improve boot speed and avoid some complications, video drivers are no longer included in intramfs by default (MODULES=most). --maximillian attems <max@deian.org> Mon, 05 Apr 2010 /tmp/tmpvNAm1I (END)My really embarrassing question is: How do I get past this message and proceed with installation of the files? I know I've had to contend with this in past, but for some reason I am drawing a blank on how to exit this message
View 2 Replies View Relatedcan 't boot fedora 12 from usb HDD after upgrade from fedora12 to fedora13 failed
View 6 Replies View RelatedMy fedora 11 (2.6.30-102) spends a long time while initializing services on
"Starting system message bus:"
---------- Post added at 08:47 PM CST ---------- Previous post was at 06:33 PM CST ----------
Auth is LDAP.
There's a 3.5 years old bug in redhat bugs database, that's still not resolved,regarding dbus trying to use ldap auth, before ldap service is started.Workaround is to change ldap config to soft binding.
3.5 years for a bug that affect enterprise users - are you there redhat?
Since I upgrade our cluster from the FC14 to the FC15 I have a bad problem with the tftpd server. I have some thinstations booting over the network after the update the boot failed with the message "TFTP open timeout". I use an "ip alias" (cluster adress) for the tftp server (next-server in the dhcp), when I use the real ip I have no problem. I found some information about a "Service Guard environment" and an option to enable it:
"This option is required for some tftp clients. These clients reject the tftp reply received from a different IP address than the one requested when the server?s interface is configured with an alias IP address." I do not see an option like that in the tftpd server of the FC15.
I've just (finally!) gotten around to upgrading a couple of machines at a company I do some work for. One machine had a problem when I rebooted onto the new system. During the boot sequence, when it was checking and mounting the filesystems, it was unable to find the /boot partition. Now, this machine does run LVM on all but the /boot partition. The two SATA drives are mirrored, and they have the same partition layout:
Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[code]....
I got the system to boot by commenting out the /boot partition in /etc/fstab, but this is certainly only a temporary solution. The other system that I upgraded came up just fine, as have several of my own. Unfortunately, I am doing these two systems by remote control via ssh as I have only limited plysical access to them. (I did have to get to it to figure out why it didn't boot up..)
I just upgraded to F15 and it went well. But at the next and each subsequent cold boot the BIOS reports "Your system last boot fail or post interrupted Please enter setup to load default and reboot". The board is an asus P5N-D. I press F1 to blow past the error and all is well until the next cold boot. Restarts are fine, no errors at all.
View 12 Replies View RelatedJust now, I finished upgrading from Fedora10 to Fedora11. But Now the Fedora 11 cannot boot, the screen just stay blue with 'fedora'.
btw, my computer is Dell Inspiron 1525.
I upgraded from 12 using an x86_64 installation DVD on a Dell Poweredge 300. All seemed to go well until right at the end when it took over two hours not to 'finish' the upgrade. Cycling round into the shell prompt showed the machine was idle and there didn't seem to be anything waiting for anything to complete. In the end I was forced to re-boot.
I got a kernel panic saying it couldn't mount on unknown block (0,0).I re-ran the upgrade DVD and it said there was one rpm left to apply called upstart-[something I missed] and it successfully applied this and then claimed I had successfully completed the upgrade. Sadly, re-booting got the same.Using the older F12 kernel still works, so my server is operational, but believes it is still F12 (and these point to (0,0) as well so it isn't that). If I try to do a yum upgrade, it will only try to upgrade a few F12 packages that must have appeared in the last few days as it was fully patched a week ago.
I think the kernel panic may be due to missing disc drivers from what my googling reveals, or a missing initrd image. There is no initrd parameter in grub.conf, I've tried creating one manually but I get a load of errors saying the /lib/modules/2..../modules.dep file is missing. Another machine that I have upgraded has such an initrd parameter in grub.conf - so I may well need to put this in.
I installed F14 on my desktop yesterday. It booted fine right after DVD install. After that I did an upgrade and installed quite a lot of packages. But when I reboot the server, it stuck in a black screen. I did get the initial blueish screen with the F in the middle. But nothing after that, no error msgs, just stuck.
View 14 Replies View RelatedWhen I boot the fedora system,disable the plymouth,the language of booting message showed is english.Can it change to other language,chinese?
View 2 Replies View RelatedWas running Server 8.04 with graphical desktop - no problems. Wanted to upgrade to 10.04, so ran sudo do-release-upgrade --proposed
Upgrade was successful (although so much stuff scrolled by, it's hard to tell if something errored along the way).
Server rebooted and a dark maroon screen said 10.4 is booting, ntp service started etc. and a scrolling series of dots.
Then got a sky blue patterned login screen, so I logged in. Screen then went black, with a movable mouse pointer.
If I do Alt-Tab a panel pops up saying ** NO WINDOWS **
Using Ctrl-Alt-F1 (iirc) got me a command prompt, so I logged in there and ran: startx
This gives me the message:
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again
So checked runlevel (who -r) and that was set to 2. Changed /etc/init/rc-sysinit.conf so RUNLEVEL=5
Rebooted, logged in again, still got black screen + mouse, and **NO WINDOWS**. Logged into terminal and runlevel=5.
Also tried running dpkg-reconfigure xserver-xorg but that returns immediately without anything apparently happening(?).
how I can get my KDE graphical environment back up ?
When running Synaptic manager I get this message:
Code:
As I run the dpkg in the terminal I get this message:
Code:
You have 1 broken package on your sytem! Use the "Broken" filter to locate it
Returning back to the Synaptic manager And when I try to upgrade that package it will hang with the following text displayed
preconfiguring packages ...(reading database ... 199488 files and directories currently installed.) preparing to replace mysql-server-5.1 5.1.41-3ubuntu12.1 (using .../mysql-server-5.1_5.1.41 3ubuntu12.3_i386.deb) ...
It's become a tradition since I've installed FC6 on my machine: after each Fedora upgrade, the PC hangs at reboot because of a badly make initrd !
I found this post a while ago that helped me to solve the problem by rebuilding the initrd with the right librairies in it: [url]
So for each upgrade I've done the last 2 years I had to follow again these instructions to rebuild the initrd.
I've just finished the upgrade from F9 to F10 and I faced the following friendly message:
Code:
Allright, not a surprise in fact. While rebuilding the initrd I discovered there's no more /lib/i686/nosegneg/ directory in Fedora10's initrd. Therefore I reinstalled the libm-2.9.so library as follows:
Code:
Once the initrd rebuilt, I rebooted and faced a second friendly message:
Code:
I searched for posts reporting problems with segfault in ld-2.9.so but didn't find anything. So now I'm with a successfully upgraded fedora 10 system that refuses to boot.
By the way, I've done the upgrade using the netinstall CD, all the packages have been retreived online without errors and I think I've therefore the latest versions.
How to making this F10 box to start ?
I have just upgraded my F11 x86_64 system using the DVD ISO.
After rebooting as requested:
1) Cupsd fails to start - it can't find libaudit.so.1 (this doesn't worry me in itself).
2) Boot process proceeds until starting hald. This gets an OK response, but then the process hangs. No further output appears on the console. Pressing [ENTER] just causes a blank line to appear on the console. Pressing CTRL-ALT-DEL causes a reboot, and the same symptoms re-occur.
I'm tempted to boot with the rescue disk, save a few critical data directories, then start afresh with a clean install, but is there anything I can do to salvage the upgrade?
I've just updated my desktop to F13 using preupgrade but now grub won't boot it. The upgrade seemed to go OK, and none of the disk partitions should have changed as far as I'm aware, but now I get an error
VFS: Cannot open root device "UUID=xxx" or unknown block(0,0).
I'm not a complete newb, or a seasoned hacker. I can't figure out what's up with this, I keep getting this message when I try to apply updates. [('installing package kernel-2.6.35.12-88.fc14.i686 needs 17MB on the /boot filesystem', (9, '/boot', 16985088L))]
View 6 Replies View RelatedI recently upgraded through 'YUM' from Fedora 14 to Fedora 15. The upgrade appeared to be successful until it re booted, ever since then it hangs at
Code:
Started SYSV: Enable monthly update of smolt.
I have downloaded the ISO and burned it to DVD on another system which I used to try to rescue the installation, so far to no avail. My system specs are in my signature below (Laughlin is what I upgraded from).