LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Error after running yum update - black screen (https://www.linuxquestions.org/questions/linux-newbie-8/error-after-running-yum-update-black-screen-4175535732/)

bluforce 03-04-2015 08:51 AM
Error after running yum update - black screen
 
Can you guys advise on how to resolve this? We have a machine (RHEL 6 32bit 2.6.32-504.8.1.el6.i686) that boots to a black screen. I can SSH into it from my machine, but when you're physically at the machine it just displays a black screen.

I have tried booting from the previous 2 kernels, but still get the black screen.

I am assuming something got hosed with the video stuff? Its an ATI Radeon 4000series card. Should I install the ATI driver from their website and try? We have never had to do that with these machines though.


Also, when running a yum update, we receive this error. I'm not sure how to resolve this and if resolving this will fix the video issues.

Code:
# yum update
Loaded plugins: downloadonly, product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package libudev.i686 0:147-2.46.el6 will be updated
--> Processing Dependency: libudev = 147-2.46.el6 for package: libgudev1-147-2.46.el6.i686
---> Package libudev.i686 0:147-2.57.el6 will be an update
---> Package libudev-devel.i686 0:147-2.46.el6 will be updated
---> Package libudev-devel.i686 0:147-2.57.el6 will be an update
---> Package udev.i686 0:147-2.46.el6 will be updated
---> Package udev.i686 0:147-2.57.el6 will be an update
--> Finished Dependency Resolution
Error: Package: libgudev1-147-2.46.el6.i686 (@rhel-i386-workstation-6)
          Requires: libudev = 147-2.46.el6
          Removing: libudev-147-2.46.el6.i686 (@rhel-i386-workstation-6)
              libudev = 147-2.46.el6
          Updated By: libudev-147-2.57.el6.i686 (rhel-i386-workstation-6)
              libudev = 147-2.57.el6
          Available: libudev-147-2.29.el6.i686 (rhel-i386-workstation-6)
              libudev = 147-2.29.el6
          Available: libudev-147-2.35.el6.i686 (rhel-i386-workstation-6)
              libudev = 147-2.35.el6
          Available: libudev-147-2.40.el6.i686 (rhel-i386-workstation-6)
              libudev = 147-2.40.el6
          Available: libudev-147-2.41.el6.i686 (rhel-i386-workstation-6)
              libudev = 147-2.41.el6
          Available: libudev-147-2.42.el6.i686 (rhel-i386-workstation-6)
              libudev = 147-2.42.el6
          Available: libudev-147-2.46.el6_4.2.i686 (rhel-i386-workstation-6)
              libudev = 147-2.46.el6_4.2
          Available: libudev-147-2.51.el6.i686 (rhel-i386-workstation-6)
              libudev = 147-2.51.el6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Heres after running yum update --skip-broken:

Code:
# yum update --skip-broken
Loaded plugins: downloadonly, product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package libudev.i686 0:147-2.46.el6 will be updated
--> Processing Dependency: libudev = 147-2.46.el6 for package: libgudev1-147-2.46.el6.i686
---> Package libudev.i686 0:147-2.57.el6 will be an update
---> Package libudev-devel.i686 0:147-2.46.el6 will be updated
---> Package libudev-devel.i686 0:147-2.57.el6 will be an update
---> Package udev.i686 0:147-2.46.el6 will be updated
---> Package udev.i686 0:147-2.57.el6 will be an update
--> Running transaction check
---> Package libudev.i686 0:147-2.46.el6 will be updated
---> Package libudev.i686 0:147-2.57.el6 will be an update
--> Processing Dependency: libudev = 147-2.57.el6 for package: libudev-devel-147-2.57.el6.i686
--> Running transaction check
---> Package udev.i686 0:147-2.46.el6 will be updated
--> Processing Dependency: udev = 147-2.46.el6 for package: libudev-devel-147-2.46.el6.i686
---> Package udev.i686 0:147-2.57.el6 will be an update

Packages skipped because of dependency problems:
    libudev-147-2.57.el6.i686 from rhel-i386-workstation-6
    libudev-devel-147-2.57.el6.i686 from rhel-i386-workstation-6
    udev-147-2.57.el6.i686 from rhel-i386-workstation-6
Thanks in advance.

business_kid 03-05-2015 06:55 AM
get busy with rpm and the man page. You can use levers and hammers to get yourself out of something like that. I think you will have to download everything skipped, and find their requirements. Then install the requirements. Major PITA.

RockDoctor 03-05-2015 08:01 AM
I'd start by running yum update on just libgudev1; it appears that the remaining dependencies would be satisfied if you can get beyond that one

bluforce 03-05-2015 11:46 AM
Quote:
Originally Posted by RockDoctor (Post 5327291)
I'd start by running yum update on just libgudev1; it appears that the remaining dependencies would be satisfied if you can get beyond that one
Thanks guys.
I tried to update just this one package and it says:

Code:
sudo yum update libgudev1-147-2.46.el6.i686
Loaded plugins: downloadonly, refresh-packagekit, rhnplugin, security
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Update Process
No Packages marked for Update

EDDY1 03-05-2015 12:07 PM
You think this bug report might help?
https://bugzilla.redhat.com/show_bug.cgi?id=888085
Sorry not sure if that was relevant because of the difference in name.

EDDY1 03-05-2015 12:15 PM
After looking at your errors that link may be quite relevant.

bluforce 03-05-2015 12:57 PM
Thanks but I'm not sure what I should do after reading thru those comments :confused:

RockDoctor 03-06-2015 07:27 AM
Back to the black screen problem - have you tried booting using the nomodeset kernel parameter?

business_kid 03-06-2015 12:56 PM
@RockDoctor: Good suggestion, but I recently had no kernel modesetting on one oldish laptop running a recent kernel and X wouldn't boot that way. I had been doing a 'git bisect' and somehow lost my own video driver in the remakes.

EDDY1 03-06-2015 02:05 PM
You probably need to create a link here
Quote:
After creating a symlink between libudev.so.1 and libudev.so.0 it worked fine.
Also if you have a redhat subscription, you've paid for support I would give them a call.


All times are GMT -5. The time now is 03:46 PM.