On Friday 08 June 2007 14:57:45 Paul Albrecht wrote:
>
> Seems like an obvious regression so I was wondering if I could get some
> help resolving the problem here?
>
I see a reply from Dimitry Torokhov which you haven't acknowledged. Did you
miss it?
Andrew Walrond
PS 'Nudge' m
On Friday 08 June 2007 14:57:45 Paul Albrecht wrote:
Seems like an obvious regression so I was wondering if I could get some
help resolving the problem here?
I see a reply from Dimitry Torokhov which you haven't acknowledged. Did you
miss it?
Andrew Walrond
PS 'Nudge' messages like
On Saturday 02 June 2007 12:00:28 Shahbaz Khan wrote:
> I need help with my homework
>
Both tools come with extensive documentation, but such questions are unwelcome
here.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Saturday 02 June 2007 12:00:28 Shahbaz Khan wrote:
I need help with my homework
Both tools come with extensive documentation, but such questions are unwelcome
here.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
On Saturday 24 February 2007 15:23, Jan Engelhardt wrote:
> On Feb 23 2007 15:47, Andrew Walrond wrote:
> >
> >I have tracked this down to a broken version of gnu cpio (latest release,
> > 2.7) which was used to create the initramfs archive. Bloody annoying
> > sinc
On Saturday 24 February 2007 15:23, Jan Engelhardt wrote:
On Feb 23 2007 15:47, Andrew Walrond wrote:
I have tracked this down to a broken version of gnu cpio (latest release,
2.7) which was used to create the initramfs archive. Bloody annoying
since this has bitten me before! Last time I
fore! Last time I even sent the maintainer a bug report, and
apparently a fix is in CVS waiting for the next release. Ho hum.
Sorry for the noise.
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
On Friday 23 February 2007 13:32, Tomasz Chmielewski wrote:
> Andrew Walrond schrieb:
> > On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the
> > same procedure successfully on x86_64 and itanium2 servers).
> >
> > The relevent silo section looks lik
<0>Press Stop-A (L1-A) to return to the boot prom
So it knows about the initramfs, but then tries to mount a root filesystem
instead...
I haven't tried this (initramfs) with earlier kernels, so I don't know
whether this is a regression. Any clues about how to solve this would be
gr
-A) to return to the boot prom
So it knows about the initramfs, but then tries to mount a root filesystem
instead...
I haven't tried this (initramfs) with earlier kernels, so I don't know
whether this is a regression. Any clues about how to solve this would be
greatly appreciated.
Andrew
On Friday 23 February 2007 13:32, Tomasz Chmielewski wrote:
Andrew Walrond schrieb:
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the
same procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
image=/boot/2.6.20.image
the maintainer a bug report, and
apparently a fix is in CVS waiting for the next release. Ho hum.
Sorry for the noise.
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
On Friday 09 February 2007 00:01, David Miller wrote:
> From: Andrew Walrond <[EMAIL PROTECTED]>
> Date: Thu, 8 Feb 2007 21:31:25 +
>
> > Sometime between 2.6.18.3 and 2.6.20, this change...
> >
> > --- /include/linux/atmarp.h 2007-01-10 16:32:05.
include
linux/types.h
I've cc'ed Adrian Bunk since he seemed interested last time I reported
something like this.
http://lkml.org/lkml/2007/1/19/39
Hope that is useful.
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
include
linux/types.h
I've cc'ed Adrian Bunk since he seemed interested last time I reported
something like this.
http://lkml.org/lkml/2007/1/19/39
Hope that is useful.
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Friday 09 February 2007 00:01, David Miller wrote:
From: Andrew Walrond [EMAIL PROTECTED]
Date: Thu, 8 Feb 2007 21:31:25 +
Sometime between 2.6.18.3 and 2.6.20, this change...
--- /include/linux/atmarp.h 2007-01-10 16:32:05.0 +
+++ pkg/linux/include/linux/atmarp.h
de/linux/byteorder/big_endian.h?
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
/big_endian.h?
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Olaf Hering wrote:
Why do you need /sbin/hotplug anyway, just for firmware loading for a
non-modular kernel?
I guess this is unusual, but FWIW...
I have a custom distro and I was just looking for the easiest way to
create a bootable rescue pen-drive. So I just took a working distro,
added
Olaf Hering wrote:
On Mon, Jan 15, Andrew Walrond wrote:
To solve this, I deleted /sbin/hotplug from the initramfs archive and
modified /init to reinstate it once it gets control. This works fine,
but seems inelegant. Is there a better solution? Should sbin/hotplug be
called at all before
to /init?
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
to /init?
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Olaf Hering wrote:
On Mon, Jan 15, Andrew Walrond wrote:
To solve this, I deleted /sbin/hotplug from the initramfs archive and
modified /init to reinstate it once it gets control. This works fine,
but seems inelegant. Is there a better solution? Should sbin/hotplug be
called at all before
Olaf Hering wrote:
Why do you need /sbin/hotplug anyway, just for firmware loading for a
non-modular kernel?
I guess this is unusual, but FWIW...
I have a custom distro and I was just looking for the easiest way to
create a bootable rescue pen-drive. So I just took a working distro,
added
I was running 2.6.18.3 before, which worked fine.
Only managed to get a screen grab from remote KVM, but hope its useful.
I'll try latest rc when I can get someone to reset the (remote) box.
Andrew Walrond
<>
I was running 2.6.18.3 before, which worked fine.
Only managed to get a screen grab from remote KVM, but hope its useful.
I'll try latest rc when I can get someone to reset the (remote) box.
Andrew Walrond
attachment: oops.JPG
if I can do anything to help chase this down.
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-A) to return to the boot prom
Let me know if I can do anything to help chase this down.
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
le. It's a complete rewrite of rubyx
(http://www.rubyx.org) but doesn't have its own website yet. Discussion is
happening on the rubyx ML. Cross compilation support would be a simple
extension to Heretix, if you fancy a project :)
Andrew Walrond
-
To unsubscribe from this list: send the
://www.rubyx.org) but doesn't have its own website yet. Discussion is
happening on the rubyx ML. Cross compilation support would be a simple
extension to Heretix, if you fancy a project :)
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
ne. They are
> already aware of my problems ;)
Care to share your monotone wishlist?
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-inf
projects, like darcs, would know what needs working
on.
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
needs working
on.
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
of my problems ;)
Care to share your monotone wishlist?
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
On Saturday 02 April 2005 20:10, Andrew Walrond wrote:
>
> In the meantime, I'm going to remove this driver from the .config
>
Boots fine without this driver compiled in (SCSI_FUTURE_DOMAIN=n)
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kerne
like the "Future Domain 16xx SCSI/AHA-2920A" scsi driver detect routine
is doing something naughty.
This is a Tyan 2885 dual x86_64 running a 64bit generic x86_64 kernel. It
doesn't have any scsi hardware.
In the meantime, I'm going to remove this driver from the .config
Andrew Walrond
like the Future Domain 16xx SCSI/AHA-2920A scsi driver detect routine
is doing something naughty.
This is a Tyan 2885 dual x86_64 running a 64bit generic x86_64 kernel. It
doesn't have any scsi hardware.
In the meantime, I'm going to remove this driver from the .config
Andrew Walrond
2.6.11.6
On Saturday 02 April 2005 20:10, Andrew Walrond wrote:
In the meantime, I'm going to remove this driver from the .config
Boots fine without this driver compiled in (SCSI_FUTURE_DOMAIN=n)
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On Friday 11 March 2005 09:28, Ingo Molnar wrote:
> i have released the -V0.7.40-00 Real-Time Preemption patch, which can be
> downloaded from the usual place:
>
I've lost the thread a little; Is this still x86 only?
Andrew Walrond
-
To unsubscribe from this list: send the line &qu
On Friday 11 March 2005 09:28, Ingo Molnar wrote:
i have released the -V0.7.40-00 Real-Time Preemption patch, which can be
downloaded from the usual place:
I've lost the thread a little; Is this still x86 only?
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux
fter writing TN_SETVAL to the config register sets the
* counter value, the second write sets the threshold.
*/
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.o
to the config register sets the
* counter value, the second write sets the threshold.
*/
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
t;
Just to confirm that this also fixes the problem for two types of MSI dual
opteron motherboards. (MSI K8D Master 2/3)
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Master 2/3)
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
after
FWIW The problem is not limited to the IBM e325. I cannot boot a HPET_TIMER
enabled x86 kernel on any of the various Tyan and MSI opteron boards I have
here without hpet=disable. x86_64 kernels work fine.
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubsc
The problem is not limited to the IBM e325. I cannot boot a HPET_TIMER
enabled x86 kernel on any of the various Tyan and MSI opteron boards I have
here without hpet=disable. x86_64 kernels work fine.
Andrew Walrond
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On Monday 17 January 2005 16:32, Mark Watts wrote:
>
> Thats your answer then. HyperThreading makes one cpu act as two (with a
> suitable performance increase for some workloads)
>
Me thinks you should reread the original message ;)
Andrew
-
To unsubscribe from this list: send the line
On Monday 17 January 2005 16:32, Mark Watts wrote:
Thats your answer then. HyperThreading makes one cpu act as two (with a
suitable performance increase for some workloads)
Me thinks you should reread the original message ;)
Andrew
-
To unsubscribe from this list: send the line unsubscribe
48 matches
Mail list logo
