Apparently, though unproven, at 01:47 on Wednesday 26 January 2011, Peter
Humphrey did opine thusly:
> > [1] old age this end = fuzzy memory = get names mixed up sometimes
>
> Eh? I thought you were just a young whipper-snapper. And no, you can't
> have any fuzzy memory - it's all taken.
You t
On Tuesday 25 January 2011 22:43:17 Alan McKinnon wrote:
> Apparently, though unproven, at 19:33 on Tuesday 25 January 2011,
> Peter Humphrey did opine thusly:
> > On Tuesday 25 January 2011 17:05:41 Bill Longman wrote:
> > > You can *always* compile any package against your choice of
> > > kernel.
Apparently, though unproven, at 19:33 on Tuesday 25 January 2011, Peter
Humphrey did opine thusly:
> On Tuesday 25 January 2011 17:05:41 Bill Longman wrote:
> > You can *always* compile any package against your choice of kernel.
> > Just use "KERNEL_DIR=/usr/src/mykerneldir emerge package". It
>
On Tuesday 25 January 2011 17:05:41 Bill Longman wrote:
> You can *always* compile any package against your choice of kernel.
> Just use "KERNEL_DIR=/usr/src/mykerneldir emerge package". It
> doesn't have to be the running kernel or the current kernel.
We've been through this once.
--
Rgds
Pete
On 01/16/2011 01:18 AM, Peter Humphrey wrote:
> On Sunday 16 January 2011 03:25:41 cov...@ccs.covici.com wrote:
>> Adam Carter wrote:
>>> Did you remember to repoint the /usr/src/linux link? IIRC the
>>> module is built to suit whatever kernel that is pointing to. If
>>> its not set correctly you'
On Sunday 16 January 2011 15:32:03 Alan McKinnon wrote:
> Logic tells me you likely have something dodgy local to your machine
> as you are the only one so this would be a good point to post the
> error output you get.
As I said to Dale, I'll check at the next upgrade. Thanks anyway.
--
Rgds
Pe
On Monday 17 January 2011 02:28:57 Dale wrote:
> Peter, you got something weird going on with your system?
Maybe I have, or did have at one time. I'll try it again at the next
update. Thanks for the info.
--
Rgds
Peter. Linux Counter 5290, 1994-04-23.
Dale wrote:
> cov...@ccs.covici.com wrote:
> > Dale wrote:
> >
> >
> >> Peter Humphrey wrote:
> >>
> >>> On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
> >>>
> >>>
> >>>
> The no kernel config error sounds more like you havent done make
> oldconfig/menuconfig w
cov...@ccs.covici.com wrote:
Dale wrote:
Peter Humphrey wrote:
On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
The no kernel config error sounds more like you havent done make
oldconfig/menuconfig whatever to create the .config file.
In fact that isn't i
Dale wrote:
> Peter Humphrey wrote:
> > On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
> >
> >
> >> The no kernel config error sounds more like you havent done make
> >> oldconfig/menuconfig whatever to create the .config file.
> >>
> > In fact that isn't it. I've copied the .con
Dale wrote:
Peter Humphrey wrote:
On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
The no kernel config error sounds more like you havent done make
oldconfig/menuconfig whatever to create the .config file.
In fact that isn't it. I've copied the .config from /boot, run make
oldconfig, com
Peter Humphrey wrote:
On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
The no kernel config error sounds more like you havent done make
oldconfig/menuconfig whatever to create the .config file.
In fact that isn't it. I've copied the .config from /boot, run make
oldconfig, compil
Apparently, though unproven, at 17:18 on Sunday 16 January 2011, Peter
Humphrey did opine thusly:
> On Sunday 16 January 2011 12:54:46 Alan McKinnon wrote:
> > That's nonsense.
>
> It is not.
It has not been a problem for me, not once, in 4 years at least, both on x86
and amd64. Other posters
On Sunday 16 January 2011 12:54:46 Alan McKinnon wrote:
> That's nonsense.
It is not.
--
Rgds
Peter. Linux Counter 5290, 1994-04-23.
On Sunday 16 January 2011 12:13:54 Adam Carter wrote:
> The no kernel config error sounds more like you havent done make
> oldconfig/menuconfig whatever to create the .config file.
In fact that isn't it. I've copied the .config from /boot, run make
oldconfig, compiled the kernel and copied it to
On Sun, 16 Jan 2011 11:06:30 +, Peter Humphrey wrote:
> > > You can't emerge nvidia-drivers if /usr/src/linux points to a
> > > kernel version other than the currently running one - it complains
> > > it can't find a valid kernel config. This means that, after
> > > emerging a new kernel versi
Apparently, though unproven, at 11:18 on Sunday 16 January 2011, Peter
Humphrey did opine thusly:
> On Sunday 16 January 2011 03:25:41 cov...@ccs.covici.com wrote:
> > Adam Carter wrote:
> > > Did you remember to repoint the /usr/src/linux link? IIRC the
> > > module is built to suit whatever ke
>
> I am using x86 rather than 64 and I did emerge it after rebooting to the
> new kernel, but I got invalid argument when issuing the modprobe
> command.
>
>
Can you cut/paste the command and output? and also the command "modinfo
nvidia" and its output?
Peter Humphrey wrote:
> On Sunday 16 January 2011 03:25:41 cov...@ccs.covici.com wrote:
> > Adam Carter wrote:
> > > Did you remember to repoint the /usr/src/linux link? IIRC the
> > > module is built to suit whatever kernel that is pointing to. If
> > > its not set correctly you'll need to re-e
>
>
>>
>>
>
> I have compiled a kernel for 2.6.37 but I have not booted it yet. I'll set
> the link to the new kernel, emerge nvidia and see what happens when I boot
> the new kernel.
>
> In the past, I was on x86 on my old rig. Maybe it is the arch that affects
> something. I'm not sure but wil
Peter Humphrey wrote:
On Sunday 16 January 2011 10:48:45 Dale wrote:
Peter Humphrey wrote:
You can't emerge nvidia-drivers if /usr/src/linux points to a
kernel version other than the currently running one - it complains
it can't find a valid kernel config. This means that, after
emerg
On Sunday 16 January 2011 10:48:45 Dale wrote:
> Peter Humphrey wrote:
> > You can't emerge nvidia-drivers if /usr/src/linux points to a
> > kernel version other than the currently running one - it complains
> > it can't find a valid kernel config. This means that, after
> > emerging a new kernel
Peter Humphrey wrote:
On Sunday 16 January 2011 03:25:41 cov...@ccs.covici.com wrote:
Adam Carter wrote:
Did you remember to repoint the /usr/src/linux link? IIRC the
module is built to suit whatever kernel that is pointing to. If
its not set correctly you'll need to re-emerge nvidia
On Sunday 16 January 2011 03:25:41 cov...@ccs.covici.com wrote:
> Adam Carter wrote:
> > Did you remember to repoint the /usr/src/linux link? IIRC the
> > module is built to suit whatever kernel that is pointing to. If
> > its not set correctly you'll need to re-emerge nvidia-drivers.
>
> linux i
On Sat, Jan 15, 2011 at 6:56 PM, wrote:
>
> Here is my nvidia drivers version:
> Installed versions: 260.19.29!s(09:14:27 PM 01/15/2011)(acpi gtk
> kernel_linux -custom-cflags -multilib)
>
> I am using gentoo-x86 and the card is 01:00.0 VGA compatible controller:
> nVidia Corporation G86 [GeFor
Adam Carter wrote:
> On Sun, Jan 16, 2011 at 1:34 PM, wrote:
>
> > Hi. I am trying to use my unstable gentoo on kernel 2.6.36-gentoo-r6
> > and when I emerge nvidia-drivers, I get invalid argument when I try to
> > modprobe the module.
> >
>
> Did you remember to repoint the /usr/src/linux li
On Sun, Jan 16, 2011 at 1:34 PM, wrote:
> Hi. I am trying to use my unstable gentoo on kernel 2.6.36-gentoo-r6
> and when I emerge nvidia-drivers, I get invalid argument when I try to
> modprobe the module.
>
Did you remember to repoint the /usr/src/linux link? IIRC the module is
built to suit
Mark Knecht wrote:
> On Sat, Jan 15, 2011 at 6:34 PM, wrote:
> > Hi. I am trying to use my unstable gentoo on kernel 2.6.36-gentoo-r6
> > and when I emerge nvidia-drivers, I get invalid argument when I try to
> > modprobe the module. I could not find a bug anywhere -- is this a too
> > recent
On Sat, Jan 15, 2011 at 6:34 PM, wrote:
> Hi. I am trying to use my unstable gentoo on kernel 2.6.36-gentoo-r6
> and when I emerge nvidia-drivers, I get invalid argument when I try to
> modprobe the module. I could not find a bug anywhere -- is this a too
> recent kernel for him?
>
> Any assist
Hi. I am trying to use my unstable gentoo on kernel 2.6.36-gentoo-r6
and when I emerge nvidia-drivers, I get invalid argument when I try to
modprobe the module. I could not find a bug anywhere -- is this a too
recent kernel for him?
Any assistance would be appreciated.
--
Your life is like a p
30 matches
Mail list logo
