Jump to content

Not able to load Mandriva after installing Kubuntu


ffi
 Share

Recommended Posts

Today I wanted to expiriment a little more with Kubuntu and reformated and labeled (to Ubuntu) a partition. I installed Kubuntu (6.04) but now when I boot into Mandriva I get the following error : fsck.ext3 could not resolve 'Label=Ubuntu' (or something similar). I then get asked wether I want to fix the error ( choosing either Y or N doesn't make any difference). I can then type my root password or ctrl-d for a reboot.

 

If it type my root password and then startx, x continues to load but encounters the following fatal error;

 

 (II) NVIDIA(0): Setting mode "1280x1024_60"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Keyboard1: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard1: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard1: XkbRules: "xorg"
(**) Keyboard1: XkbModel: "logicdp"
(**) Option "XkbLayout" "us_intl"
(**) Keyboard1: XkbLayout: "us_intl"
(**) Option "XkbOptions" "compose:rwin"
(**) Keyboard1: XkbOptions: "compose:rwin"
(**) Option "CustomKeycodes" "off"
(**) Keyboard1: CustomKeycodes disabled
(**) Option "Protocol" "ExplorerPS/2"
(**) Mouse1: Device: "/dev/mouse"
(**) Mouse1: Protocol: "ExplorerPS/2"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/mouse"
(==) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "6 7"
(**) Mouse1: ZAxisMapping: buttons 6 and 7
(**) Mouse1: Buttons: 11
(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(II) Mouse1: ps2EnableDataReporting: succeeded
Could not init font path element unix/:-1, removing from list!

Fatal server error:
could not open default font 'fixed'

Please consult the The X.Org Foundation support 
 at http://wiki.X.Org
for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

 

[moved from Software by spinynorman]

Link to comment
Share on other sites

Yes, I know the errors you described, I'm trying to determine what might be causing these errors by asking questions ;)

 

Did the hda2 partition exist during the mandriva install? or did you create it afterwards? that is, when you installed mandriva, were there two partitions in existance that were before the partition the mandriva installed on, or did you resize a partition and create a new one?

Link to comment
Share on other sites

when you login, take a look at your /etc/fstab file:

nano -w /etc/fstab

look for a line that references /dev/hda2:

/dev/hda2 /mnt/something etc.

and put a # in front of it for the time being (that is, comment it out):

#/dev/hda2 /mnt/something etc.

then reboot and see if the boot up error is fixed.

 

as far as the other error, it's a problem with fonts. you can try fixing it by:

fc-cache -v

before you do that startx, but I have a feeling the first error is what's causing the second one - boot up is stopping early and not starting some necessary services.

Link to comment
Share on other sites

Okay I saw a line:

 

´label=Ubuntu´ /mnt/win_c ext3 umask=0,iocharset=utf8 1 2

 

and changed it to

 

/dev/hda2 /mnt/win_c ext3 umask=0,iocharset=utf8 1 2

 

and now Mandriva works again. Strange thing though I was looking at the fstab file on hda3 (my mandriva partition) with my installation from Kubuntu (on hda2) but I needed admin privileges in Kubuntu to change the Mandriva fstab file. Do you suppose Kubuntu is using the same fstab file?

Link to comment
Share on other sites

it shouldn't be, though they may look similar. ubuntu usually detects other linux distributions, and may have changed the fstab for some reason. plus, when you mount a linux partition inside another linux system it retains the permissions, so a file that is only writable to root will still be so when mounted under another linux system.

Link to comment
Share on other sites

Okay, thanks for your answer and the help :) . BTW Kubuntu did not detect the Mandriva install (after all the troubles I had with boatloaders I had decided not to let Kubuntu install one but had manually added the entries in Mandriva before the install)

Edited by ffi
Link to comment
Share on other sites

strange o_O ubuntu is usually pretty good about that. last i installed it, it detected gentoo and windows and added both to grub. then again, i've seen it detect nothing on other systems. wonder what the issue is.

Link to comment
Share on other sites

When installing multiple Linux distros on the same machine, its wise to have a common /boot partition (normally formatted as ext2, and no larger than 64MB), where you install Grub just once and manage the various kernels of the various Linuxes by hand (sounds complicated, but it's actually very easy, or in anyway much easier than having multiple /boot partitions and bootloaders).

Link to comment
Share on other sites

o_O

 

Most people install grub on the MBR (and so only have one bootloader), having one /boot really doesn't have many advantages, and some distros may have conflicts with naming conventions of the kernels when they place them in /boot - they could start overwriting each other if they use the same naming conventions. I don't think having one /boot partition is a smart move for more novice users.

 

But we don't really need to get into it. ffi's problem has been solved :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...