black screen after glibc update [Solved]

[phd7]

Hi,
After updating glibc a while back, I receive a message saying ti is extremely important to update 7 configuration files before rebooting.
Following advice from another thread, I ran

equo conf update
and was told there were no problems.

Now when I reboot, I get a black screen with flashing cursor.
Doing CTL-ALT F1 and logging in and trying startx, I just get 3 graphical terminal windows.
Any ideas?

[phd7]

Update...

I have now tried this update 4 times since my last backup
I had updated the 7 config files I was aske to update.
Following advice on another post I also reinstalled grub2.
When I tired to update grub, I got the zfs module messages mentioned elsewhere.
After reboot..same result.. black screen with blinking cursor.

So I went into mint and reinstalled and updated grub from there.
After reboot I chose Sabyon from grub and this time, got the Sabayon X graphical screen, and I could see at the bottom that the boot was stalled at "initialising Kernel" (i.e. nothing at all happened)

[sabayonino]

I had updated the 7 config files

what are these seven files?

what altered these files?

If in doubt discard the changes

What D.E. you are using ?

...more info ...

[phd7]

Im using KDE on Sabayon 9.
Atfer updating glibc via rigo, this mesage popped up , so I followed the advice by accepting the config file updates, again via rigo.:

http://screencloud.net/img/screenshots/bdb831032dddbc48ee97c87f5fb4d987.png

[phd7]

5th attempt. I got partway to solving this.
This time after the glibc update, I didnt update config files, and was able to reboot into image 3.4.
Then I installed image 3.5
Edited results below:

Code: Select all

>>    ## Installing package: sys-kernel/linux-sabayon-3.5-r7
>>    ## [Official Sabayon Linux Standard kernel image]
>>    ## Updating database: sys-kernel/linux-sabayon-3.5-r7
>>    ## Cleaning previously installed application data.
>>    ## SPM: post-install phase
 * Removing extents option for ext4 drives from /etc/fstab
 * Updating boot splash for /boot/initramfs-genkernel-x86_64-3.5.0-sabayon
 * Updating boot splash for /boot/initramfs-genkernel-x86_64-3.4.0-sabayon
/var/tmp/entropy/packages/amd64/5/sys-kernel_linux-sabayon-3.5-r7_0.tbz2/portage/sys-kernel/linux-sabayon-3.5-r7/temp/environment: line 3826: /sbin/grub-mkdevicemap: No such file or directory
----------------------
loads of these:
Failed to load ZFS module stack.
Load the module manually by running 'insmod <location>/zfs.ko' as root.
..............
Generating grub.cfg ...
/etc/grub.d/00_header: line 28: /lib64/grub/grub-mkconfig_lib: No such file or directory
Setting bzImage to kernel-genkernel-x86_64-3.5.0-sabayon
Setting Initrd to initramfs-genkernel-x86_64-3.5.0-sabayon
...................
again it showed the config files to be updated, which I ignored
...............

sabayon # eselect kernel list
Available kernel symlink targets:
  [1]   linux-3.4.0-sabayon
  [2]   linux-3.5.0-sabayon *
--------------

As grub.cfg wouldnt update, I manually changed it. copying the 3.4 entries and changing all instances of 3.4 to 3.5

On reboot sabayon kernel 3.5 was listed (with nothing else) so I booted into that.
Again trying to update grub.cfg , i got the zfs errors, so I updated the config files at this stage.

Then I was able to update grub.cfg without the zfs module stack errors.

Upon reboot into 3.5, I am once again presented with the black screen and flashing cursor as mentioned above.
Booting into the recovery versionand CTL-D, gives me the previous Sabayon X graphical screen with the "initalising kernel" message, but the loginin dialogus doesnt show up.

[phd7]

I had a look a a previous post of mine about the steps necessary to change to the open vid driver from flgrx, and checked the relevant files.
Some changes seemto have been undone since the last update,so Ihad to redo them...

Remove the file /etc/gpu-detector.conf

Edit /etc/conf.d/modules add “radeon” to modules line

Edit /etc/default/grub in the line GRUB_CMDLINE_LINUX_DEFAULT add “radeon.modeset=1”

I assume now that the problem was that among the config files to be updated were /etc/conf.d/modules and etc/default/grub. If I hadnt updated them I may have been okay. You live and learn.