Re: [Fedora] Problems installing Fedora core 6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/29/06, David Vanfleet <vanfleet@xxxxxxxxxxxxx> wrote:
>David Vanfleet writes:
>> Hi,
>> I'm trying to get Fedora core 6 installed on my system and I'm having
>> some
>> problems. I got through the initial installation, got to the part where
>> it
>> tells me to remove the media and reboot the system to continue. When the
>> system reboots it locks up at the time that X windows starts (or shortly
>> after). I see the "X" curser for only a moment then it goes away and I
>> get
>> a blank screen and nothing else. I then booted up the system in "rescue"
>> mode and manually started X Windows without any problems (running
>> startx).
>> I'm upgrading this system from Fedora Core 4, which has been running
>> without problems for some time.
>>
>> Any ideas what could be happening here? Any help here would be
>> appreciated.


> Could be many things.  The first thing to try is to boot into run level 4,
> log in as root, and run "system-config-display --reconfig".  This will
> give
> you a fresh X configuration.  You can boot into run level 4 by pressing
> 'E'
> at the grub prompt, instead of pressing <Enter> or waiting for grub's
> default timeout to expire, pressing 'E' again to edit the kernel boot
> arguments, and appending <space>4 to the end, then <Enter>, then 'B' to
> boot
> the kernel.
>
> If that doesn't fix it, boot into run level 4, and look in
> /var/log/Xorg.0.log for clues (don't use the rescue disk again, starting X
> in rescue mode will wipe out Xorg.0.log).
>
> If you're using non-free binary blobs from Nvidia or ATI, remove them, and
> reinstall all X rpms, to fix any breakage.

--------------------------------------------------

Sam, thanks for your quick responce. I tried what you suggested above but I
got the same result when I tried to boot into run level 4. Right before the
system tries to start X the following is displayed in the console, I'm not
sure what comes after udev but I wonder if that's the problem:

Setting Clock        OK
Starting udev        OK

The only way I could get logged in to look at the Xorg.0.log file was to
boot into rescue mode again. When I did that I found the following warnings
and errors:

  (WW) No monitor specified for screen "Screen0".
    Using a default monitor configuration.

  (WW) The core pointer device wasn't specified explicitly in the layout.
    Using the default mouse configuration.

  (WW) No FontPath specified.  Using compiled-in default.
  (==) FontPath set to:
    unix/:7100,
    built-ins

  (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)

  (EE) AIGLX: Screen 0 is not DRI capable
  (II) Loading local sub module "GLcore"
  (II) LoadModule: "GLcore"
  (II) Loading /usr/lib/xorg/modules/extensions/libGLcore.so
  (II) Module GLcore: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.0.0
    ABI class: X.Org Server Extension, version 0.3

  (WW) <default pointer>: No Device specified, looking for one...
  (II) <default pointer>: Setting Device option to "/dev/input/mice"
  (--) <default pointer>: Device: "/dev/input/mice"
  (==) <default pointer>: Protocol: "Auto"

Then the very last line of this file says:

  Could not init font path element unix/:7100, removing from list!

Any other suggestions?

Thanks,
David

Try runlevel 3 instead (text only, multiuser, networking enabled). Or
you can boot into runlevel 2 which is single user.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux