Francois Romieu wrote:
> [...]
>> [Bugme-new] [Bug 5137] New: r8169 - network dies.
>> http://bugzilla.kernel.org/show_bug.cgi?id=5137
>
> It's cooking.
This one looks _so_ familiar to me personally - exactly the same problems I
had:
Francois Romieu wrote:
[...]
[Bugme-new] [Bug 5137] New: r8169 - network dies.
http://bugzilla.kernel.org/show_bug.cgi?id=5137
It's cooking.
This one looks _so_ familiar to me personally - exactly the same problems I
had:
http://marc.theaimsgroup.com/?l=linux-kernelm=112458400611745w=2
On Monday 29 August 2005 19:48, Jonathan Corbet wrote:
> > I built and installed 2.6.13 today, and oldconfig revealed the new option
> > for timer frequency.
> >
> > I searched the LKML on this, but all I found is the technical stuff - not
> > really any layman solutions.
>
> I wrote a bit about
Hi all,
I built and installed 2.6.13 today, and oldconfig revealed the new option for
timer frequency.
I searched the LKML on this, but all I found is the technical stuff - not
really any layman solutions.
Two n00b questions here:
What does this do/what is it for?
I selected default, 250Hz.
Hi all,
I built and installed 2.6.13 today, and oldconfig revealed the new option for
timer frequency.
I searched the LKML on this, but all I found is the technical stuff - not
really any layman solutions.
Two n00b questions here:
What does this do/what is it for?
I selected default, 250Hz.
On Monday 29 August 2005 19:48, Jonathan Corbet wrote:
I built and installed 2.6.13 today, and oldconfig revealed the new option
for timer frequency.
I searched the LKML on this, but all I found is the technical stuff - not
really any layman solutions.
I wrote a bit about the timer
On Saturday 20 August 2005 21:53, you wrote:
> I have a problem with it:
> It's about patching, reverting, patching, reverting,...
> I got lost. That's why I asked for a... "straighter" one :-)
>> But I looked at what he said and found the real problem on my system (after
>> all that):
>>
Rakotomandimby Mihamina wrote:
> Hi,
>
> I now use a notebook that uses RTL8139, and I encounter exactly the same
> problems as this:
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0402.3/1289.html
>
> I know use Fedora Core 4 on this box.
> With a Linux FC4 kernel (not customized yet).
>
Rakotomandimby Mihamina wrote:
Hi,
I now use a notebook that uses RTL8139, and I encounter exactly the same
problems as this:
http://www.ussg.iu.edu/hypermail/linux/kernel/0402.3/1289.html
I know use Fedora Core 4 on this box.
With a Linux FC4 kernel (not customized yet).
As well
On Saturday 20 August 2005 21:53, you wrote:
I have a problem with it:
It's about patching, reverting, patching, reverting,...
I got lost. That's why I asked for a... straighter one :-)
But I looked at what he said and found the real problem on my system (after
all that):
Voluspa wrote:
> On 2005-08-14 20:10:49 Nick Warne wrote:
>
>>Note the last sentence:
>>
>>' This variation is designed for use with "libraries" of drive
>>identification information, and can also be used on ATAPI drives which may
>>give media e
Voluspa wrote:
On 2005-08-14 20:10:49 Nick Warne wrote:
Note the last sentence:
' This variation is designed for use with libraries of drive
identification information, and can also be used on ATAPI drives which may
give media errors with the standard mechanism.
My jaw just clonked
I just remember a path I took when resolving the issue further to my post
below.
Here is what man hdparm says on -i and -I:
-i Display the identification info that was obtained from the
drive at boot time,
if available. This is a feature of modern IDE drives, and
Voluspa wrote:
>
> The "hdparm -I /dev/hdc"
>
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> de: failed opcode was: 0xec
>
> Is present on all kernels that I have locally (oldest 2.6.11.11)
> so it is not related to the
Voluspa wrote:
The hdparm -I /dev/hdc
hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
hdc: drive_cmd: error=0x04 { AbortedCommand }
de: failed opcode was: 0xec
Is present on all kernels that I have locally (oldest 2.6.11.11)
so it is not related to the threadstarters
I just remember a path I took when resolving the issue further to my post
below.
Here is what man hdparm says on -i and -I:
-i Display the identification info that was obtained from the
drive at boot time,
if available. This is a feature of modern IDE drives, and
On Friday 12 August 2005 20:15, Jan Engelhardt wrote:
> >>Didn't 'Linux' originate from a mis-spelling of Linus' name when his
> >> first account on some box in Helsinki Uni was created /home/linux/?
> >
> >It was because the ftp admin did not like the original name "freex" so he
> > just renamed
On Friday 12 August 2005 20:15, Jan Engelhardt wrote:
Didn't 'Linux' originate from a mis-spelling of Linus' name when his
first account on some box in Helsinki Uni was created /home/linux/?
It was because the ftp admin did not like the original name freex so he
just renamed it to
>> This is a surprising result, as the VT8233 datasheet didn't mention the
>> I2C block mode. I'll add this model to the list. This also suggests that
>> the VT8233A may support it as well - if someone could test that.
>>
>> I have to admit I don't know exactly in which order the different south
This is a surprising result, as the VT8233 datasheet didn't mention the
I2C block mode. I'll add this model to the list. This also suggests that
the VT8233A may support it as well - if someone could test that.
I have to admit I don't know exactly in which order the different south
bridges
> http://eng.cowon.com/product/iAUDIOU2/feature.html
>
> Mac and Lynux OS
> Use Mac or Lynux? No problem!!
> iAUDIO U2 is available to be used on Mac or Lynux OS.
Didn't 'Linux' originate from a mis-spelling of Linus' name when his first
account on some box in Helsinki Uni was created
http://eng.cowon.com/product/iAUDIOU2/feature.html
Mac and Lynux OS
Use Mac or Lynux? No problem!!
iAUDIO U2 is available to be used on Mac or Lynux OS.
Didn't 'Linux' originate from a mis-spelling of Linus' name when his first
account on some box in Helsinki Uni was created /home/linux/?
> But not all cases could be accounted in that way. If you
> report back that memtest86 ran cleanly...
Hugh,
Nothing to do with the 'problem' in this thread, but an aside that is perhaps
relevant.
On my main gateway, I couldn't get any kernel greater than 2.6.4 to run
without an 'oops' after
But not all cases could be accounted in that way. If you
report back that memtest86 ran cleanly...
Hugh,
Nothing to do with the 'problem' in this thread, but an aside that is perhaps
relevant.
On my main gateway, I couldn't get any kernel greater than 2.6.4 to run
without an 'oops' after x
On Monday 14 February 2005 12:45, Roman Zippel wrote:
> On Mon, 14 Feb 2005, Nick Warne wrote:
> > So I can ignore the debug prints?
>
> Yes.
OK, thanks for your replies. I am since trying 2.6.10 again (with new GCC
version and system memory this time), and the messages do not
On Monday 14 February 2005 12:12, you wrote:
> Hi,
>
> On Mon, 14 Feb 2005, Nick Warne wrote:
> > Are the optimize && ? lines normal?
>
> They are only debug prints, but I'm quite sure they are fixed in recent
> versions.
>
> > This is from a cur
Hi all,
I only just noticed this, but been building kernel source for a long time. On
my 233 over ssh, it is a bit slow, and I just noticed this output when doing
a 'make menuconfig':
make[1]: `scripts/fixdep' is up to date.
scripts/kconfig/mconf arch/i386/Kconfig
optimize && ?
optimize &&
Hi all,
I only just noticed this, but been building kernel source for a long time. On
my 233 over ssh, it is a bit slow, and I just noticed this output when doing
a 'make menuconfig':
make[1]: `scripts/fixdep' is up to date.
scripts/kconfig/mconf arch/i386/Kconfig
optimize?
optimize?
On Monday 14 February 2005 12:12, you wrote:
Hi,
On Mon, 14 Feb 2005, Nick Warne wrote:
Are the optimize? lines normal?
They are only debug prints, but I'm quite sure they are fixed in recent
versions.
This is from a current tree that has an uptime of 50 days
Could you specify
On Monday 14 February 2005 12:45, Roman Zippel wrote:
On Mon, 14 Feb 2005, Nick Warne wrote:
So I can ignore the debug prints?
Yes.
OK, thanks for your replies. I am since trying 2.6.10 again (with new GCC
version and system memory this time), and the messages do not appear in later
On Friday 11 February 2005 22:19, Terence Ripperda wrote:
> > > I just read through the nVidia readme file, and there is a
> > > comprehensive section on what module to use for what chipset (and
> > > card). It recommends using the nVagp for my setup,
>
> is that the "CONFIGURING AGP"
On Friday 11 February 2005 22:19, Terence Ripperda wrote:
I just read through the nVidia readme file, and there is a
comprehensive section on what module to use for what chipset (and
card). It recommends using the nVagp for my setup,
is that the CONFIGURING AGP appendix? I didn't
On Saturday 05 February 2005 02:01, Gary Smith wrote:
> Quoting Nick Warne <[EMAIL PROTECTED]>:
> > Here is the link that explains it... what to do with many processes
> > segfaulting, I don't know. RHEL support is _very_ good - give them a
> > ring.
> >
>
On Saturday 05 February 2005 02:01, Gary Smith wrote:
Quoting Nick Warne [EMAIL PROTECTED]:
Here is the link that explains it... what to do with many processes
segfaulting, I don't know. RHEL support is _very_ good - give them a
ring.
http://people.redhat.com/drepper/assumekernel.html
>> Is there something more that I need to compile besides the kernel for
>> compatability or is this a sign of some type of bug. I do realize that
RHEL3
>> itself has some proprietary items added to their kernel but replacing it
>> shouldn't make other applications fails.
>>
>> Any
Is there something more that I need to compile besides the kernel for
compatability or is this a sign of some type of bug. I do realize that
RHEL3
itself has some proprietary items added to their kernel but replacing it
shouldn't make other applications fails.
Any assistance would be
101 - 136 of 136 matches
Mail list logo
