[YLUG] Update fedora 10

Patrick Dupre pd520 at york.ac.uk
Sun Dec 21 12:04:35 UTC 2008


Hi Mike,

Unfortunately, It just does not work !
startx gives me the Fedora 10 background blue image, and the arrow, but
not the shape moving around the arrow. It just frozes there and I have to 
reset manually from the switch.

> Try adding "nomodeset" (without the quotes) to the kernel boot line.
>
> i.e. when you boot hit the down arrow button when grub starts. Then
> press "e" and edit the kernel line by adding the word above to the end
> of the line.
> Then press enter and then "c" to get a grub command line. Then type
> "boot" to continue the boot with the above command included.
>
> In F10 there is kernel modesetting that works with some Radeon cards,
> but this is very new and there are still some bugs in the code. It is
> not the xorg driver but in the kernel itself now. By using nomodeset
> this is bypassed. It is documents in the "common problems" page for
> f10 that is referenced in the links I sent you yesterday. I presume
> that you do not get the Plymouth graphic during the main boot but a
> text mode blue and white line that goes across the bottom of the
> screen during the initial boot phase?  X only starts once the main
> boot is complete.
Yes, I thing so.
>
> If the suggestion above works then you can edit the grub.conf file to
> use nomodeset at every reboot.  If not then ask again and work from
> that point.
>
> Mike
>
> On Sun, Dec 21, 2008 at 4:29 AM, Patrick Dupre <pd520 at york.ac.uk> wrote:
>> Hello,
>>
>> So, I restart from scratch with a new disk !!
>> I installed from the DVD, and I got a kernel 2.6.27.7-134. I looks like
>> that I has been automatically upgraded. But the big problem is that I still
>> cannot get the X session running. As before it frozes after I get the Fedora
>> image.
>> Before it was working while I supected problem with the X session:
>> slow response time with some applications, no ATL-CTL working.
>> My card is a Radeon RV100 QY.
>> Are the xorg drivers bugged ?
>> Can I choose another driver ? IF yes, how can I do it in text mode.
>>
>> Thank for your help.
>>
>>
>>
>>> On Sat, Dec 20, 2008 at 6:00 PM, Patrick Dupre <pd520 at york.ac.uk> wrote:
>>>>
>>>> On Sat, 20 Dec 2008, mike cloaked wrote:
>>>>
>>>>> Exactly how did you update from FC7?
>>>>>
>>>>> i.e. to be explicit - did you
>>>>
>>>> 2 weeks ago I did the update by running a yum upgrade
>>>>
>>>> 2 weeks ago IO updated from the DVD (anaconda): of course from the iso
>>>> image.
>>>>
>>>> yesterday from yumex.
>>>
>>> Well now I am confused...
>>> So you did yum upgrade initially to change your version from FC7 to
>>> F10 - I don't understand whether you mean you then did some kind of
>>> upgrade to that from the DVD? Or did you do a new fresh install from
>>> scratch. In addition I now don't know what you did with yumex. However
>>> F10 is very very different to FC7 (and note that it is F10 and not
>>> FC10 even though package names are tagged wit the .fc10 suffix for
>>> special reasons because Fedora packages are now part of a unified
>>> Fedora Collection, and not Fedora Core as it was at the time of FC7)
>>>
>>> If you still have old versions of your configs lying around and did a
>>> yum upgrade from version 7 to version 10 then you will almost
>>> certainly get problems....I would strongly recommend that you do not
>>> try to get that system working as the upgrade from 7 to 10 is too huge
>>> a change.
>>>
>>> I would strongly suggest that you start from scratch and do an install
>>> from the DVD and make sure that you ask anaconda to format the root
>>> partition during that install. If you have a wired connection during
>>> the install then it will automatically configure a wired interface for
>>> you and NetworkManager will use it.  You can install to the root ( / )
>>> partition and leave your other partitions untouched, provided you ask
>>> it to do a custom disk partition when you get to that section of the
>>> install.  Always make a backup of all files ahead of this in case it
>>> all goes wrong - this is standard advice.
>>>
>>> Make sure that you read the release notes, and also the install guide for
>>> F10
>>> http://docs.fedoraproject.org/release-notes/f10/
>>> http://docs.fedoraproject.org/install-guide/f10/en_US/
>>>
>>> The install guide will also give you information on other methods for
>>> the install, including hard drive and http, plus nfs installs.
>>>
>>> Once you have the install running, make sure you select your packages
>>> and it will pull the necessary files from the DVD, and during the
>>> firstboot you are asked to make a user area, and then log in to that
>>> user area in gnome, then before you start configuring anything else
>>> make sure you then do either:
>>> yum -y update
>>> or
>>> use PackageKit which is now the default background process that runs
>>> yum for you - and let that update your system.
>>>
>>> Note that by default you are unable to login as root so make sure you
>>> do create a non-root user during the install.
>>>
>>> Then re-boot after the yum update as you will have a new kernel and
>>> many other updated packages.
>>>
>>> Only then can you start either retrieving old user files and setting
>>> up the system as you wish. At this stage you should already have a
>>> working X and be logged in to a desktop.
>>>
>>> You can of course switch out of X to a VT if you wish to use a command
>>> line only. However it is easier to open a set of terminal windows in
>>> the desktop and work from there.
>>>
>>> Also note that by default you will have SElinux enabled and enforcing.
>>> You should read about SElinux so that you can work with it.
>>> http://docs.fedoraproject.org/selinux-user-guide/f10/en-US/
>>>
>>> If you feel that SElinux is too much for you then you can switch it to
>>> permissive.  Note that if you disable SElinux then getting it back can
>>> be quite a pain! However leaving it permissive will allow you to work
>>> but you will get SElinux warnings.
>>>
>>>> From what you have posted it is not clear what state your system is
>>>
>>> in, and in this case it is very difficult for other people to offer
>>> you advice. If you have a cleanly installed system and can quote
>>> exactly what you did when a problem occurs and can also provide the
>>> results of log files and a good description then others can try to
>>> triage the problem and suggest a solution.
>>>
>>> I hope this helps.
>>>
>>
>> --
>> ---
>> ==========================================================================
>>  Patrick DUPRÉ                      |   |
>>  Department of Chemistry            |   |    Phone: (44)-(0)-1904-434384
>>  The University of York             |   |    Fax:   (44)-(0)-1904-432516
>>  Heslington                         |   |
>>  York YO10 5DD  United Kingdom      |   |    email: pd520 at york.ac.uk
>> ==========================================================================
>> _______________________________________________
>> York mailing list
>> York at lists.lug.org.uk
>> https://mailman.lug.org.uk/mailman/listinfo/york
>>
>>
>
>
>
>

-- 
---
==========================================================================
  Patrick DUPRÉ                      |   |
  Department of Chemistry            |   |    Phone: (44)-(0)-1904-434384
  The University of York             |   |    Fax:   (44)-(0)-1904-432516
  Heslington                         |   |
  York YO10 5DD  United Kingdom      |   |    email: pd520 at york.ac.uk
==========================================================================


More information about the York mailing list