Fedora 14 boot problem

[nitishsp]

Hello guys,
I am new to Linux. I have Fedora 14 along with vista.

when I boot fedora, it gives following error at the beginning:

Starting udev:udevd-work[505]:error opening ATTR{/sys/devices/pci0000......./usb3/......../power/level3} for writing. No such file or directory

and halts right after-
Starting atd : [ OK ]

However I can use fedora in command mode.

I had installed some softwares & had removed Evolution before this problem started.


any solution?

[Mudgen]

What do you mean by "I can use fedora in command mode"? Does it just fail the gnome startup and drop you to a command prompt?

[jayd512]

I had installed some softwares & had removed Evolution before this problem started.

What software did you remove?
If you removed some things, then the issues started happening, I'd say that your system needs them back.
It sounds like you might be missing some dependencies somewhere.

[dmurphy787]

Hi,
I had exactly the same problem after a recent Fedora update, I believe that in my case it was a file related to Java but I never did track it down. It was the first major issue I have had with Fedora and in the end I have learnt that sometimes it pays to just restart the OS with a fresh copy, which is what I did as I had spent all day trying to track it down. I did get closer but my patience ran out, My posts and the replies at linuxquestions "org" may help. I can't paste the url as the forums here don't allow it until I have done 15 or more posts, sorry. Go the the address above at type "f14 hangs on reboot after update' to see my posts in that forum and I hope that may help you.
Fedora is a great OS so keep asking in the forums as many are willing to input into this fantastic Fedora community.

[PairOfBlanks2]

Having resolved an update issue before, I recommend the following as root (in bash ("command mode")):

- rpm -qa --last | less
This will show you all installed packages in the order of most recent to least recent. Now you must determine which of these packages broke your system. Try to remember a date/time on which your system ran well, and simply delete all packages installed after then. I'm tempted to tell you to re-install Evolution here, but I can't see how that can cause a problem.
- yum erase PackageNameAfterWorkingDate PackageNameAfterWorkingDate2 PackageNameAfterWorkingDate3... etc.
This will erase the packages.
- yum install evolution
Probably not necessary here.

My guess is that you are using a proprietary video driver from a third party source. Try erasing that driver (if you know it's name) and then getting either proprietary or free drivers from RPMFusion "org" by enabling their repositories like this:

- yum localinstall --nogpgcheck ehchteeteepee_download1_rpmfusion_org/free/fedora/rpmfusion-free-release-stable_noarch_dot_rpm ehchteeteepee_download1_rpmfusion_org/nonfree/fedora/rpmfusion-nonfree-release-stable_noarch_rpm
Replace _ with . and ehchteeteepee with you know what.
Consider not using proprietary software at all. Major problems like yours will be less frequent, and you can report bugs to help us all, and the world works better, and blah blah blah. Skip the last word of the above command if you wish to avoid RPMFusion's proprietary repository.
Please let us know how you solved this problem in this thread.

[nitishsp]

Thank You everyone for your replies.

What do you mean by "I can use fedora in command mode"? Does it just fail the gnome startup and drop you to a command prompt?

I meant to say, Fedora hangs displaying the "f" before the login & if I press Alt + Ctrl + f5 it goes to command mode.


@dmurphy787:
I went through your thread but I guess my system hangs
at different service (which is after atd)


@PairOfBlanks2:

I did: rpm -qa --last | less & removed all suspected packages.

I installed evolution too.

when I tried:

yum localinstall --nogpgcheck....

it returned:

/var/tmp/yum-root............
Nothing to do.

I have RPMFusion repositories enabled as per instructions on their site. I don't think that I have installed any proprietary video driver because only softwares I had installed on f14 were Google Chrome, Open Office & plugins for playing mp3 & avi files.

then as mentioned in dmurphy787's thread, I did:
"yum history undo <ID>" to undo 1 update

but that didn't help either.

[PairOfBlanks2]

Starting udev:udevd-work[505]:error opening ATTR{/sys/devices/pci0000......./usb3/......../power/level3} for writing. No such file or directory

This leads me to suspect that you're using an external hard drive and are trying to boot from it.
If write-protection is in use on this external drive, then this is likely the cause. Confirm that write-protection is off before continuing.
If you plug this external drive into USB, then try all other USB ports to see if they work (hardware problem, maybe).
Please confirm that your Vista partition is not experiencing concurrent problems.

[PairOfBlanks2]

Try googling your error message. I did, and I landed here

ehchteeteepee_bugzilla_redhat_com/show_bug.cgi?id=505438

Perhaps some other unsupported hardware is in use... tell us.

[nplusplus]

Look in /etc/rc5.d to see which process starts right after atd (I believe Fedora 14 is still using SVR4-style boot). atd should have a symlink like S##atd, where ## is some number. The next symlink in the directory, either adjacent or next higher number, is likely the one that starts next. You might then look at the startup script for it to figure out what it does or do man -k nameofstartupservice (like atd). If it does not look critical, then you might try running "chkconfig nameofstartupservice off." That will stop it from starting at boot. For instance, "chkconfig atd off" will stop atd from starting at boot. However, if the service is critical to the system's startup routine, you could find you are unable to boot again until you use a system rescue disk to set things straight, so be careful with this.

[ProfTheory]

I believe PairOfBlanks2 is on the right track. It looks like what is happening is the X server is not starting and when that happens the system will behave as you described.

To test it out when you boot and get to the GRUB menu highlight Fedora then hit the 'A' key and then type " 3" without the quotes. That will start you in runlevel 3. Then after logging in start X manually with startx and see what happens. Or you could also check /var/log/Xorg.log or Xorg.0.log and see where it is hanging up.

I had that happen to me after trying the Nvidia driver.