Hi Andre,
On Fri, 11 Aug 2000, Andre Hedrick wrote:
> On Fri, 11 Aug 2000, Corin Hartland-Swann wrote:
> > When I try hdparm -m -c -d1 -a, I get the following output:
> >
> > /dev/hdc:
> > setting using_dma to 1 (on)
> > HDIO_SET_DMA failed: Operation not permitted
> > multcount= 16 (on)
Sheesh you have to at least turn on in the kernel at compile time to
attempt dma. Maybe using the chipset tuning code to get it programmed
correctly, would get you to the average 22MB/sec that piix and drive combo
will do.
On Fri, 11 Aug 2000, Corin Hartland-Swann wrote:
>
> Mark,
>
> I'm cr
> -Original Message-
> From: Nick Kay [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 11, 2000 9:27 AM
> To: Gregory Leblanc
> Cc: [EMAIL PROTECTED]
> Subject: RE: lilo issue
>
> >Can you show us your lilo.conf? Do you have a default label
> set? Does
> >lilo-21.5 include RH's boot f
On Fri, Aug 11, 2000 at 05:11:59PM +0100, Corin Hartland-Swann wrote:
> Partition check:
> hda: hda1 hda2 hda3
> hdb: hdb1
> hdc: [PTBL] [4982/255/63] hdc1
>
> Can anyone explain to me what the [PTBL] bit means? I've been wondering
> this for about 4 years now, and still don't know :)
For al
>
>Can you show us your lilo.conf? Do you have a default label set? Does
>lilo-21.5 include RH's boot from RAID1 patch, or another boot from RAID1
>patch?
No I don't have the default label set - I tend to like having the
option of alternate kernels as a rescue mechanism. I guess I
don't hav
Mark,
I'm cross-posting this to the kernel and RAID lists again, because there's
more information about the problem in here. I hope this is acceptable.
On Thu, 10 Aug 2000, Mark Hahn wrote:
> > Intel 810E Chipset Motherboard (CA810EAL), Pentium III-667, 32M RAM,
> > Maxtor DiamondMax Plus 40 40
> -Original Message-
> From: Nick Kay [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 11, 2000 6:51 AM
> To: [EMAIL PROTECTED]
> Subject: lilo issue
>
> Hi all,
> I have my raid-1 up and running over two 9gig scsi
> drives under slackware 7.1 with kernel 2.2.16+raid-2.2.6-AO
> fro
Yeah, it's in there. I was blowing past that before... My mistake.
Thanks for the help.
--
On Aug 11 at 14:32, Nick Kay (nick) wrote:
> Subject: Re: How do I tell the kernel I want RAID-5?
>
> At 09:12 11/08/00 -0400, you wrote:
> >This is going to sound pretty stupid, but here goes anywa
Hi all,
I have my raid-1 up and running over two 9gig scsi
drives under slackware 7.1 with kernel 2.2.16+raid-2.2.6-AO
from Ingo and lilo-21.5.
After disconnecting the second drive (ID 1) and rebooting
works fine, however pulling ID0 causes problems in that lilo comes
up without an
At 09:12 11/08/00 -0400, you wrote:
>This is going to sound pretty stupid, but here goes anyway...
>
>I got 2.2.16 and the latest patch from kernel.org, applied it and started to
>rebuild.
>
>The question is, where do I tell the kernel to use RAID-5?
>
>I can't see it in the 'make menuconfig' stuf
This is going to sound pretty stupid, but here goes anyway...
I got 2.2.16 and the latest patch from kernel.org, applied it and started to
rebuild.
The question is, where do I tell the kernel to use RAID-5?
I can't see it in the 'make menuconfig' stuff anywhere... Am I missing
something here?
Gregory Leblanc writes:
...
> > I know that the Linux kernel auto-detects the SCSI devices on boots
> > and assigns them
> >
> > /dev/sda to the first one
> > /dev/sdb to the second one ...
> >
> > and so on.
>
> Yep. Lots of planning done there. :-)
>
> > Doesn't this put a kink
Christoph Kukulies writes:
...
> > Would there be a patch against an oldstyle md-patched kernel somewhere?
> > Since your distribution (Wasn't it RedHat?) is delivering it like that
>
> Yes, RH 6.1
>
> > maybe they should do that?
> >
> > But your best strategy is probably to grab a cl
On 11-Aug-00 Christoph Kukulies wrote:
>> So you have a kernel which is already patched with raid-code and you try
>> to
>
> patched with old style raid code?
Yes -- thats the problem.
SuSE is just the same -- They distribute kernels which include a lot of
patches and you almost can't apply a
On Fri, Aug 11, 2000 at 10:53:11AM +0200, Karl-Heinz Herrmann wrote:
>
> On 11-Aug-00 Christoph Kukulies wrote:
> ># cat /proc/mdstat
> > Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
> > read_ahead not set
> > md0 : inactive
> > md1 : inactive
> > md2 : inactive
> > md3 : inactive
>
On 11-Aug-00 Christoph Kukulies wrote:
># cat /proc/mdstat
> Personalities : [1 linear] [2 raid0] [3 raid1] [4 raid5]
> read_ahead not set
> md0 : inactive
> md1 : inactive
> md2 : inactive
> md3 : inactive
Yes -- thats old style md-raid.
So you have a kernel which is already patched with raid
On Thu, Aug 10, 2000 at 05:07:42PM +0200, Karl-Heinz Herrmann wrote:
> Hi,
>
>
> On 10-Aug-00 Christoph Kukulies wrote:
> >> If the patch is not clean (i.e. rejects) you probably had a kernel
> >> patched
> >> with the old style md-raid. The patch is probably against a clean kernel
> >> source.
17 matches
Mail list logo