public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: xorg-server-1.5 update/old kernel+old fglrx
Date: Wed, 24 Jun 2009 19:33:25 -0700	[thread overview]
Message-ID: <5bdc1c8b0906241933n251d3d27vf1b314a8b5b488a8@mail.gmail.com> (raw)
In-Reply-To: <h1ul7h$8hg$1@ger.gmane.org>

On Wed, Jun 24, 2009 at 6:51 PM, Nikos Chantziaras<realnc@arcor.de> wrote:
> On 06/25/2009 04:27 AM, Mark Knecht wrote:
>>>
>>> I thought emerge xf86-video-ati, then swapping Driver "flgrx" to Driver
>>> "radeon" in xorg.conf was all that is required??
>>
>> No, I need a new kernel also. The kernel on this machine is 2 years
>> old. Also, I have about a dozen packages masked so I've unmasked those
>> and will need to get the whole machine up to date.
>>
>> None the less I'm happy to do it if there's any chance it will work.
>
> If it works, better make sure you keep the system up to date.  Gentoo will
> bark and bite you at some point if you don't; I'm sure you figured that out
> by now :P
>

Except for being forced into all these old kernel and video packages
the machine has been kept up to date. Now it will be completely up to
date. :-)

The new kernel booted the first time and except for me forgetting to
enable the correct NIC things looked good. I added the 3c590 and now
can get to it over ssh. emerge -DuN @world will take a few hours as
there are a number of packages to update.

Tomorrow I will delve into the newer Open Source ATI driver and see
how things go. Wish me luck.

cheers,
Mark



  reply	other threads:[~2009-06-25  2:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 23:20 [gentoo-user] xorg-server-1.5 update/old kernel+old fglrx Mark Knecht
2009-06-23 23:27 ` [gentoo-user] " Nikos Chantziaras
2009-06-23 23:40   ` Mark Knecht
2009-06-23 23:53     ` Mark Knecht
2009-06-24  0:06       ` Mark Knecht
2009-06-24  0:16         ` Nikos Chantziaras
2009-06-24  0:27           ` Mark Knecht
2009-06-24  0:33             ` Nikos Chantziaras
2009-06-24  0:42               ` Mark Knecht
2009-06-24  1:32                 ` Neil Bothwick
2009-06-24  3:13                   ` Mark Knecht
2009-06-24  5:55                     ` Dale
2009-06-24  0:29         ` Nikos Chantziaras
2009-06-24  0:37           ` Mark Knecht
2009-06-24  1:46             ` Dale
2009-06-24  1:14         ` Keith Dart
2009-06-24  1:28         ` Neil Bothwick
2009-06-24  1:42           ` Mark Knecht
2009-06-24  7:46             ` Neil Bothwick
2009-06-24 20:17               ` Mark Knecht
2009-06-24 20:29                 ` Neil Bothwick
2009-06-24 20:32                 ` Alan McKinnon
2009-06-25  0:08                 ` Adam Carter
2009-06-25  0:46                   ` Mark Knecht
2009-06-25  0:59                     ` Nikos Chantziaras
2009-06-25  1:25                       ` Mark Knecht
2009-06-25  1:04                     ` Adam Carter
2009-06-25  1:07                       ` Nikos Chantziaras
2009-06-25  1:15                         ` Adam Carter
2009-06-25  1:27                       ` Mark Knecht
2009-06-25  1:51                         ` Nikos Chantziaras
2009-06-25  2:33                           ` Mark Knecht [this message]
2009-06-25  8:47                         ` bn
2009-06-25 17:42                           ` Mark Knecht
2009-06-24  9:21           ` Peter Humphrey
2009-06-24 14:25         ` Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bdc1c8b0906241933n251d3d27vf1b314a8b5b488a8@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox