public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Derek Tracy <tracyde@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is Gentoo still on the right path?
Date: Wed, 16 Nov 2005 17:37:22 -0500	[thread overview]
Message-ID: <9999810b0511161437l2b168ce4m8ffce3b7ccf2f202@mail.gmail.com> (raw)
In-Reply-To: <7573e9640511161422g122aebb0gf74c2dd5ff9500c3@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3148 bytes --]

On 11/16/05, Richard Fish <bigfish@asmallpond.org> wrote:
>
> On 11/16/05, Derek Tracy <tracyde@gmail.com> wrote:
> > When a branch is marked stable all of the packages in that branch should
> > work,
>
> I'm not sure this is always possible. Much of your complaint comes
> from the ipw2200 driver, which is new in 2.6.14. But the in-kernel
> version is several versions older than the external driver. So should
> 2.6.14 remain marked as unstable because of this one driver that works
> for some people, but not for others? Or because a specific externally
> maintained driver or package doesn't build against it?
>
> On my system, either the in-kernel or external drivers work fine. The
> only caveat is that I need firmware version 2.2 with the in-kernel
> drivers, and a different version for the external. If I am using the
> external version, the portage dependancy tree makes sure I have the
> right version of the firmware. But the kernel sources do not (and
> should not) depend upon the ipw2200-firmware package, so this is a
> case where I need to know the driver requirements. (Also, the kernel
> help specifies that the driver requires external firmware, although it
> doesn't specify what version.)


What I am complaining about is that neither of the drivers will work.

Regarding the X.org <http://X.org> issue, without an Xorg.0.log file, it is
> really
> impossible to say what the problem there is. It could be something as
> simple as your kernel configuration; for example leaving out I2C or
> AGP support could cause this.
>
> But in my view, you cannot take an existing xorg.conf file and expect
> it to work without any issues _without_ duplicating the same system
> configuration (kernel version, kernel config, and nvidia driver
> version). The fastest method of configuring X on a new system is to
> run "X -configure", test the resulting configuration, and use that
> xorg.conf file. Yes, this would use the opensource x.org <http://x.org> Nv
> driver,
> but it should definitely work for getting X up and running. If this
> doesn't work, then you have reason to complain.


I have tried both ways. My reasoning for taking my old config was originally
for the Modeline info. The only reason that I arbitrarily threw it into the
newly built system was because the X -configure did not work (even after I
switched the dev/mouse to /dev/input/mice) I get the same error with both of
the configs.

If the proprietary nvidia driver doesn't work with a particular kernel
> version, you can only complain to nvidia.


I have had that happen in the past and would not ever think about blaming
the Gentoo Developers for NVidias work.

I'm quite sure a binary-based distribution would have worked better
> for you in this case, only because nothing would have been upgraded or
> changed. Everything that worked before would have continued to work,
> just like everything that was broken before would have continued to be
> broken. It is the price of progress, IMO.
>
> -Richard
>
> --
> gentoo-user@gentoo.org mailing list
>
>


--
---------------------------------
Derek Tracy
tracyde@gmail.com
---------------------------------

[-- Attachment #2: Type: text/html, Size: 4345 bytes --]

  reply	other threads:[~2005-11-16 22:50 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 16:20 [gentoo-user] Is Gentoo still on the right path? Derek Tracy
2005-11-16 18:23 ` Mark Knecht
2005-11-19 15:07   ` A. Khattri
2005-11-16 19:53 ` Daniel da Veiga
2005-11-16 20:50   ` Derek Tracy
2005-11-16 21:50     ` Jeff Smelser
2005-11-16 22:32       ` Derek Tracy
2005-11-17  0:26         ` Richard Fish
2005-11-16 22:46     ` Neil Bothwick
2005-11-17 11:24       ` Derek Tracy
2005-11-17 11:59         ` Nagatoro
2005-11-17  7:44   ` jarmstrong
2005-11-16 22:51     ` Neil Bothwick
2005-11-17  3:03       ` Mark Knecht
2005-11-17  9:23         ` Neil Bothwick
2005-11-17 13:52           ` Allan Gottlieb
2005-11-17 14:35             ` Neil Bothwick
2005-11-17 17:44               ` Allan Gottlieb
2005-11-17 15:21           ` Mark Knecht
2005-11-17  0:17     ` Ciaran McCreesh
2005-11-17  0:34       ` Richard Fish
2005-11-16 20:12 ` Nick Rout
2005-11-16 20:30   ` kashani
2005-11-16 21:04     ` Nick Rout
2005-11-16 20:30   ` Benjamin Martin
2005-11-16 20:47     ` Mark Knecht
2005-11-16 20:55       ` Benjamin Martin
2005-11-16 20:59         ` Derek Tracy
2005-11-16 21:10         ` Mark Knecht
2005-11-16 21:20           ` Derek Tracy
2005-11-16 22:31             ` Richard Fish
2005-11-16 23:24             ` kashani
2005-11-16 21:33           ` Manuel McLure
2005-11-16 21:53         ` Jeff Smelser
2005-11-16 20:54   ` Zac Medico
2005-11-16 22:22 ` Richard Fish
2005-11-16 22:37   ` Derek Tracy [this message]
2005-11-17  0:21     ` Richard Fish
2005-11-17 14:03 ` Bill Roberts
  -- strict thread matches above, loose matches on Subject: below --
2005-11-16 20:27 Budd, Tracy

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=9999810b0511161437l2b168ce4m8ffce3b7ccf2f202@mail.gmail.com \
    --to=tracyde@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