> Probably you confused the proper way to use ibmsetmax with
> the proper way to use setmax. For setmax, and a Maxtor disk,
> you do not use a different machine, put the jumper to clip,
> now the boot succeeds, and you let Linux unclip.
> Either with a patched kernel that knows about these
Probably you confused the proper way to use ibmsetmax with
the proper way to use setmax. For setmax, and a Maxtor disk,
you do not use a different machine, put the jumper to clip,
now the boot succeeds, and you let Linux unclip.
Either with a patched kernel that knows about these things
or
From: Igmar Palsenberg <[EMAIL PROTECTED]>
> > 2.2.18 sometimes sees 61 GB, sometimes 32 GB.
> > I don't call that hard to understand.
>
> The same kernel has varying behaviour?
> Maybe not hard to understand, but rather surprising.
> You are the first to report
> > 2.2.18 sometimes sees 61 GB, sometimes 32 GB.
> > I don't call that hard to understand.
>
> The same kernel has varying behaviour?
> Maybe not hard to understand, but rather surprising.
> You are the first to report nondeterministic behaviour.
You're not the only one that is suprised :
1)
2.2.18 sometimes sees 61 GB, sometimes 32 GB.
I don't call that hard to understand.
The same kernel has varying behaviour?
Maybe not hard to understand, but rather surprising.
You are the first to report nondeterministic behaviour.
You're not the only one that is suprised :
1) Put
From: Igmar Palsenberg [EMAIL PROTECTED]
2.2.18 sometimes sees 61 GB, sometimes 32 GB.
I don't call that hard to understand.
The same kernel has varying behaviour?
Maybe not hard to understand, but rather surprising.
You are the first to report
> 2.2.18 sometimes sees 61 GB, sometimes 32 GB.
> I don't call that hard to understand.
The same kernel has varying behaviour?
Maybe not hard to understand, but rather surprising.
You are the first to report nondeterministic behaviour.
-
To unsubscribe from this list: send the line "unsubscribe
On Sat, 6 Jan 2001 [EMAIL PROTECTED] wrote:
> > It's not that simple.. The maxtor comes clipped,. but Linux can't kill the
> > clip. So it sticks with 32 MB
>
> > ibmsetmax.c does a software clip, but that bugs a bit. Sometimes even
> > Linux doesn't see 61 GB, but only 32, sometimes the full
On Sat, 6 Jan 2001 [EMAIL PROTECTED] wrote:
It's not that simple.. The maxtor comes clipped,. but Linux can't kill the
clip. So it sticks with 32 MB
ibmsetmax.c does a software clip, but that bugs a bit. Sometimes even
Linux doesn't see 61 GB, but only 32, sometimes the full capacity.
2.2.18 sometimes sees 61 GB, sometimes 32 GB.
I don't call that hard to understand.
The same kernel has varying behaviour?
Maybe not hard to understand, but rather surprising.
You are the first to report nondeterministic behaviour.
-
To unsubscribe from this list: send the line "unsubscribe
On Fri, Jan 05, 2001 at 12:34:11AM +0200, Eric Lammerts wrote:
> I had the same problem with my 80Gb Maxtor. (Asus P2L97, works with
> 60Gb but hangs with 80Gb :-/) After clipping the drive with ibmsetmax
> (http://www.uwsg.indiana.edu/hypermail/linux/kernel/0012.1/0249.html)
> and removing the
On Fri, Jan 05, 2001 at 12:34:11AM +0200, Eric Lammerts wrote:
I had the same problem with my 80Gb Maxtor. (Asus P2L97, works with
60Gb but hangswith 80Gb :-/) After clipping the drive with ibmsetmax
(http://www.uwsg.indiana.edu/hypermail/linux/kernel/0012.1/0249.html)
and removing the
> It's not that simple.. The maxtor comes clipped,. but Linux can't kill the
> clip. So it sticks with 32 MB
> ibmsetmax.c does a software clip, but that bugs a bit. Sometimes even
> Linux doesn't see 61 GB, but only 32, sometimes the full capacity.
Please don't talk vague useless garbage.
> > Sven, how did you kill the clipping ??
> > Or in generic, how do I kill the clipping ?
>
> Go set the jumpers right. (anyhow, IBM drives are delivered unclipped,
> not sure why Maxtors seem to be)
It's not that simple.. The maxtor comes clipped,. but Linux can't kill the
clip. So it sticks
On Thu, 04 Jan 2001, Igmar Palsenberg wrote:
> Ah.. This is a i386 machine, UDMA33 capable, and the bloody thing won't
> boot with the clipping removed, and with clipping I can use only 32 GB :((
BIOS update or manual configuration in Standard BIOS configuration
required?
--
Matthias Andree
-
On Thu, 04 Jan 2001, Igmar Palsenberg wrote:
> Sven, how did you kill the clipping ??
> Or in generic, how do I kill the clipping ?
Go set the jumpers right. (anyhow, IBM drives are delivered unclipped,
not sure why Maxtors seem to be)
--
Matthias Andree
-
To unsubscribe from this list: send
On Thu, 04 Jan 2001, Igmar Palsenberg wrote:
Sven, how did you kill the clipping ??
Or in generic, how do I kill the clipping ?
Go set the jumpers right. (anyhow, IBM drives are delivered unclipped,
not sure why Maxtors seem to be)
--
Matthias Andree
-
To unsubscribe from this list: send
On Thu, 04 Jan 2001, Igmar Palsenberg wrote:
Ah.. This is a i386 machine, UDMA33 capable, and the bloody thing won't
boot with the clipping removed, and with clipping I can use only 32 GB :((
BIOS update or manual configuration in Standard BIOS configuration
required?
--
Matthias Andree
-
Sven, how did you kill the clipping ??
Or in generic, how do I kill the clipping ?
Go set the jumpers right. (anyhow, IBM drives are delivered unclipped,
not sure why Maxtors seem to be)
It's not that simple.. The maxtor comes clipped,. but Linux can't kill the
clip. So it sticks with
It's not that simple.. The maxtor comes clipped,. but Linux can't kill the
clip. So it sticks with 32 MB
ibmsetmax.c does a software clip, but that bugs a bit. Sometimes even
Linux doesn't see 61 GB, but only 32, sometimes the full capacity.
Please don't talk vague useless garbage.
There is
On Sat, 6 Jan 2001, Igmar Palsenberg wrote:
>
> > I had a similar situation except I was more interested in the performance
> > difference. Went from ~4MB/s with the 430HX controller to ~12.5MB/s with
> > the promise. This on an old Pentium system.
>
> The network is 10 mbit, so 4 MB/sec is no
> I had a similar situation except I was more interested in the performance
> difference. Went from ~4MB/s with the 430HX controller to ~12.5MB/s with
> the promise. This on an old Pentium system.
The network is 10 mbit, so 4 MB/sec is no good in this case.
I've got the thing running, with
On Fri, Jan 05, 2001 at 12:25:09AM +0100, Igmar Palsenberg wrote:
> On Thu, 4 Jan 2001, Torrey Hoffman wrote:
>
> > I had exactly this problem with the Maxtor 61 GB drive on my
> > Pentium based server. Theoretically a BIOS upgrade could fix it,
> > but ASUS quit making BIOS upgrades for my
> I need to look at fdisk, because it is doing things wrong.
I don't think so, unless you have a really old version.
> Linux sees the correct size, but fdisk still sees 32 GB.
> Probably a recompile / upgrade.
Yes, upgrade in case your version is older than 2.10i.
Andries
-
To unsubscribe
> No. 2.2.* handles large drives since 2.2.14.
> This looks more like you used the jumper to clip the drive to 32GB.
> Don't use it and get full capacity.
> If your BIOS hangs when it sees such a large drive so that you
> cannot avoid using the jumper, use setmax in your boot scripts,
> or use a
No. 2.2.* handles large drives since 2.2.14.
This looks more like you used the jumper to clip the drive to 32GB.
Don't use it and get full capacity.
If your BIOS hangs when it sees such a large drive so that you
cannot avoid using the jumper, use setmax in your boot scripts,
or use a
I need to look at fdisk, because it is doing things wrong.
I don't think so, unless you have a really old version.
Linux sees the correct size, but fdisk still sees 32 GB.
Probably a recompile / upgrade.
Yes, upgrade in case your version is older than 2.10i.
Andries
-
To unsubscribe from
On Fri, Jan 05, 2001 at 12:25:09AM +0100, Igmar Palsenberg wrote:
On Thu, 4 Jan 2001, Torrey Hoffman wrote:
I had exactly this problem with the Maxtor 61 GB drive on my
Pentium based server. Theoretically a BIOS upgrade could fix it,
but ASUS quit making BIOS upgrades for my
On Sat, 6 Jan 2001, Igmar Palsenberg wrote:
I had a similar situation except I was more interested in the performance
difference. Went from ~4MB/s with the 430HX controller to ~12.5MB/s with
the promise. This on an old Pentium system.
The network is 10 mbit, so 4 MB/sec is no good in
> On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
>
>> kernel 2.2.18 hates my Maxtor drive :
>> hda: Maxtor 96147H6, 32253MB w/2048kB Cache, CHS=65531/16/63, (U)DMA
>>
>> Actual (correct) parameters : CHS=119112/16/63
No. 2.2.* handles large drives since 2.2.14.
This looks more like you used the
On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
> Yeah.. I removed the clipping, and the machine won't boot. It halts after
> PnP init. Any way to use full capacity with the clipping enabled ?
I had the same problem with my 80Gb Maxtor. (Asus P2L97, works with
60Gb but hangs with 80Gb :-/) After
On Thu, 4 Jan 2001, Torrey Hoffman wrote:
> I had exactly this problem with the Maxtor 61 GB drive on my
> Pentium based server. Theoretically a BIOS upgrade could fix it,
> but ASUS quit making BIOS upgrades for my motherboard two years
> ago.
Ah well, join the club in my case :)
> I solved
I had exactly this problem with the Maxtor 61 GB drive on my
Pentium based server. Theoretically a BIOS upgrade could fix it,
but ASUS quit making BIOS upgrades for my motherboard two years
ago.
I solved the problem by getting a Promise Ultra 100 controller
and putting the drive on that. Works
> I did'nt know something like that even existed :)
>
> Just plugged the drive into the ide controller (single drive on a
> promise ata100 in a dec alpha) and it worked.
Ah.. This is a i386 machine, UDMA33 capable, and the bloody thing won't
boot with the clipping removed, and with clipping I
On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
> > You have a hard destroke clipping on the drive.
> > Go look at you logs.
>
> Yep, logs indicate that..
>
> Sven, how did you kill the clipping ??
> Or in generic, how do I kill the clipping ?
I did'nt know something like that even existed :)
Just
On Thu, 4 Jan 2001, Andre Hedrick wrote:
>
> You have a hard destroke clipping on the drive.
> Go look at you logs.
Yeah.. I removed the clipping, and the machine won't boot. It halts after
PnP init. Any way to use full capacity with the clipping enabled ?
Regards,
Hi,
Forget the question on killing the drive clipping. I forgot to RTFM :)
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
> You have a hard destroke clipping on the drive.
> Go look at you logs.
Yep, logs indicate that..
Sven, how did you kill the clipping ??
Or in generic, how do I kill the clipping ?
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe
You have a hard destroke clipping on the drive.
Go look at you logs.
On Thu, 4 Jan 2001, Sven Koch wrote:
> On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
>
> > kernel 2.2.18 hates my Maxtor drive :
> >
> > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > hda: Maxtor 96147H6, 32253MB w/2048kB Cache,
On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
> kernel 2.2.18 hates my Maxtor drive :
>
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: Maxtor 96147H6, 32253MB w/2048kB Cache, CHS=65531/16/63, (U)DMA
>
> Actual (correct) parameters : CHS=119112/16/63
>
> Looks like some short int (2 bytes)
Hi,
Just tried the ide patches for 2.2.18, and same result :((
Any patches / suggestions I can try ??
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read
Hi,
kernel 2.2.18 hates my Maxtor drive :
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: Maxtor 96147H6, 32253MB w/2048kB Cache, CHS=65531/16/63, (U)DMA
Actual (correct) parameters : CHS=119112/16/63
Looks like some short int (2 bytes) overflowing. I'll try the ide patches.
Regards,
Hi,
kernel 2.2.18 hates my Maxtor drive :
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: Maxtor 96147H6, 32253MB w/2048kB Cache, CHS=65531/16/63, (U)DMA
Actual (correct) parameters : CHS=119112/16/63
Looks like some short int (2 bytes) overflowing. I'll try the ide patches.
Regards,
Hi,
Just tried the ide patches for 2.2.18, and same result :((
Any patches / suggestions I can try ??
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read
On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
kernel 2.2.18 hates my Maxtor drive :
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: Maxtor 96147H6, 32253MB w/2048kB Cache, CHS=65531/16/63, (U)DMA
Actual (correct) parameters : CHS=119112/16/63
Looks like some short int (2 bytes) overflowing. I'll
You have a hard destroke clipping on the drive.
Go look at you logs.
On Thu, 4 Jan 2001, Sven Koch wrote:
On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
kernel 2.2.18 hates my Maxtor drive :
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: Maxtor 96147H6, 32253MB w/2048kB Cache,
You have a hard destroke clipping on the drive.
Go look at you logs.
Yep, logs indicate that..
Sven, how did you kill the clipping ??
Or in generic, how do I kill the clipping ?
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe
Hi,
Forget the question on killing the drive clipping. I forgot to RTFM :)
Regards,
Igmar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Thu, 4 Jan 2001, Andre Hedrick wrote:
You have a hard destroke clipping on the drive.
Go look at you logs.
Yeah.. I removed the clipping, and the machine won't boot. It halts after
PnP init. Any way to use full capacity with the clipping enabled ?
Regards,
On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
You have a hard destroke clipping on the drive.
Go look at you logs.
Yep, logs indicate that..
Sven, how did you kill the clipping ??
Or in generic, how do I kill the clipping ?
I did'nt know something like that even existed :)
Just plugged
On Thu, 4 Jan 2001, Torrey Hoffman wrote:
I had exactly this problem with the Maxtor 61 GB drive on my
Pentium based server. Theoretically a BIOS upgrade could fix it,
but ASUS quit making BIOS upgrades for my motherboard two years
ago.
Ah well, join the club in my case :)
I solved the
On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
Yeah.. I removed the clipping, and the machine won't boot. It halts after
PnP init. Any way to use full capacity with the clipping enabled ?
I had the same problem with my 80Gb Maxtor. (Asus P2L97, works with
60Gb but hangs with 80Gb :-/) After
On Thu, 4 Jan 2001, Igmar Palsenberg wrote:
kernel 2.2.18 hates my Maxtor drive :
hda: Maxtor 96147H6, 32253MB w/2048kB Cache, CHS=65531/16/63, (U)DMA
Actual (correct) parameters : CHS=119112/16/63
No. 2.2.* handles large drives since 2.2.14.
This looks more like you used the jumper to
53 matches
Mail list logo
