> > 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 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. (i'm talking without the hardware jumper). the machine I used to set the limit (target machine doesn't but without the hardware clip), seems to reset the software clip. Probably the BIOS who does that. It seems stable now, machine boots OK, and Linux sees 61GB. Let's hope it will stay that way. 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/
- 2.2.18 and Maxtor 96147H6 (61 GB) Igmar Palsenberg
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Sven Koch
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Andre Hedrick
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Igmar Palsenberg
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Sven Koch
- Re: 2.2.18 and Maxtor 96147H6 (61 ... Igmar Palsenberg
- Re: 2.2.18 and Maxtor 96147H6 ... Matthias Andree
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Matthias Andree
- Re: 2.2.18 and Maxtor 96147H6 (61 ... Igmar Palsenberg
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Igmar Palsenberg
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Igmar Palsenberg
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Eric Lammerts
- Re: 2.2.18 and Maxtor 96147H6 (61 ... Tommi Virtanen
- RE: 2.2.18 and Maxtor 96147H6 (61 GB) Torrey Hoffman
- RE: 2.2.18 and Maxtor 96147H6 (61 GB) Igmar Palsenberg
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Tim Wright
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Igmar Palsenberg
- Re: 2.2.18 and Maxtor 96147H6 (61 ... Brad Hartin
- Re: 2.2.18 and Maxtor 96147H6 (61 GB) Andries . Brouwer