[solved] Re: hda=stroke for installer?

2004-12-06 Thread Richard Hector
On Sun, Dec 05, 2004 at 11:23:53PM +1300, Richard Hector wrote:
 Hi all,
 
 I'm trying to install sarge on an old (Celeron 366) machine with a new
 disk.

Thanks to all those who offered advice.

To summarise:

I jumpered my 80G disk to clip its capacity, so that my old Award bios
would boot.

For Linux to see this, with a recent (=2.6.7) kernel, the ide driver
needs the 'hda=stroke' option.

The debian installer uses modules for all that, so putting it on the
command line doesn't work - it has to go with loading the module.

The module in question is ide_core, which is normally loaded implicitly
when you load another module that depends on it. That doesn't allow for
adding options, so I had to shell out and run

modprobe ide_core options=hda=stroke

from the command line, before letting the installer start loading the
other ide modules (which it does when looking for the CDROM, so I had to
get in before that). Note also that the syntax is different: when using
a built-in driver, just add 'hda=stroke' to the kernel command line;
when using a module, it's 'options=hda=stroke'.

That lets the installer do it's thing, but it doesn't pass that on to
the installed system.

When I install debian, I usually create a root partition of around 2G,
from which I set up LVM and so on for the rest of it. That all fits in
the first 33.8G (naturally), so it let me carry on to build a kernel
with the ide drivers built in (and in fact no initrd at all), which I
then installed.

Lastly I tweaked /boot/grub/menu.lst to add 'hda=stroke' (no 'options'
stuff this time) to the command line, and I now see the full disk.

I'm sure it's possible to get the initrd stuff set up right too, but I'm
less familiar with that, so I didn't pursue that very far.

Hopefully that helps anyone in a similar situation :-)

What I really need, of course, is better hardware ... the PII 400
machine behind me is still clunking away building the kernel; I gave up
waiting for it after about half an hour, and sshed in to work and built
it on my P4 1.7 and copied it back in a fraction of the time (woohoo -
the other one's finished now too!).

Richard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



hda=stroke for installer?

2004-12-05 Thread Richard Hector
Hi all,

I'm trying to install sarge on an old (Celeron 366) machine with a new
disk.

From what I've read, I should be able to use the jumper on my seagate
st380011a to limit it to 33.8G, then use hda=stroke on the kernel
command line (for kernels later than 2.6.7), and linux should see the
whole lot.

I've downloaded a netinst iso that has 2.6.8, so that bit should be ok,
and I then boot with either

linux26 hda=stroke

or

expert26 hda=stroke

but when I get to the partitioner, it still shows up as 33.8G rather
than the 80G it should be. Good old fdisk shows the same thing.

dmesg shows (hand typed, so there may be errors):

hda: Host Protected Area detected.
current capacity is 66055248 sectors (33820 MB)
native  capacity is 156301488 sectors (80026 MB)
hda: 66055248 sectors (33820 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(33)

so the kernel knows about the issue at some level.

My resources so far include:
http://www.seagate.com/support/disc/specs/ata/st380011a.html
http://www.tldp.org/HOWTO/Large-Disk-HOWTO-11.html

Any suggestions?

Thanks,

Richard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: hda=stroke for installer?

2004-12-05 Thread Joao Clemente
Richard Hector wrote:
From what I've read, I should be able to use the jumper on my seagate
st380011a to limit it to 33.8G, then use hda=stroke on the kernel
command line (for kernels later than 2.6.7), and linux should see the
whole lot.
[snip]
Any suggestions?
Well, I've actually been able to use new 80GB disks in very old 
computers (Pentium 200 Classic) with no jumper limiter... Maybe you 
could try to boot without the jumper? Even if the bios can't see the 
whole disk, Linux will see it you just need to get booted.. (in last 
instance you can boot from a floppy )

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: hda=stroke for installer?

2004-12-05 Thread Joey Hess
Richard Hector wrote:
 I've downloaded a netinst iso that has 2.6.8, so that bit should be ok,
 and I then boot with either
 
 linux26 hda=stroke
 
 or
 
 expert26 hda=stroke

As far as I know passing parameters to the ide (or whatever) module like
this will only work if it's built into the kernel, not if it's a module.
If it's a module the parameter has to be passed when the module is
modprobed. When you boot in expert mode it should let you specifiy
module parameters before loading whichever module is the one that
processes this parameter and you can enter it there.

-- 
see shy jo


signature.asc
Description: Digital signature


Re: hda=stroke for installer?

2004-12-05 Thread Richard Hector
On Sun, Dec 05, 2004 at 10:13:59PM -0500, Joey Hess wrote:
 Richard Hector wrote:
  I've downloaded a netinst iso that has 2.6.8, so that bit should be ok,
  and I then boot with either
  
  linux26 hda=stroke
  
  or
  
  expert26 hda=stroke
 
 As far as I know passing parameters to the ide (or whatever) module like
 this will only work if it's built into the kernel, not if it's a module.
 If it's a module the parameter has to be passed when the module is
 modprobed. When you boot in expert mode it should let you specifiy
 module parameters before loading whichever module is the one that
 processes this parameter and you can enter it there.

Excellent, thanks - that certainly pointed me in the right direction.

Unfortunately, the module that needs the option is ide_core, and that
isn't loaded explicitly by the installer, so I had no chance to add the
option there. What I had to do was, once it said it was going to detect
the CDROM, I went to the 2nd VC and ran

modprobe ide_core options=hda=stroke

(and working out the options= bit took some time, too ...), then I
returned to the installer and didn't need to specify anything else.

The next problem is that, presumably because the installer knew nothing
about what I had done, it didn't add the option to the initrd image
either, so on reboot I'm back to a 33.8G disk. I'm now working through
how to recreate the initrd image ...

Many thanks,

Richard


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]