don't start whith hd


Forum: HD Install
Topic: don't start whith hd
started by: ix1esm

Posted by ix1esm on Mar. 06 2005,14:39
I've a pc Unisys MPI 4663 whith scsi disk 16 Mb. ram

it start with live but don't recognize the hd sda?!

anyone help me please

Posted by cbagger01 on Mar. 07 2005,02:55
You need to find out some more information on your SCSI controller, including make and model and also the BIOS/hardware settings like IRQ or IO.

For a shot in the dark, try this:

sudo su
modprobe aha152x
exit
exit

and see what happens.

Posted by ix1esm on Mar. 08 2005,12:57
Quote (cbagger01 @ Mar. 06 2005,21:55)
You need to find out some more information on your SCSI controller, including make and model and also the BIOS/hardware settings like IRQ or IO.

For a shot in the dark, try this:

sudo su
modprobe aha152x
exit
exit

and see what happens.

I boot whith fd because the bios hasn't option whith follow string:

expert dsl 2

when i try aha152x=0x340,7,11,0,0,0,100,1

system call me the floppy whith modules?!?

can i generate it

TNX de IX1ESM

Posted by cbagger01 on Mar. 09 2005,03:16
It is possible to create a floppy disk with the module file on it, but you don't need to do this just yet.

Instead, boot live and then go to a command prompt and try to modprobe your driver.  Then try to access sda via a manual mount command like:

mkdir /mnt/sda1
mount -t vfat /dev/sda1 /mnt/sda1

for example if your first partition is an MSDOS/Win95/98/ME partition.

The driver file is included on the livecd.

You can use emelfm to copy it over to the floppy disk.

It is located in

/lib/modules/2.4.26/kernel/drivers/scsi/aha152x.o

Good Luck.

Posted by ix1esm on Mar. 14 2005,10:43
Quote (cbagger01 @ Mar. 06 2005,21:55)
You need to find out some more information on your SCSI controller, including make and model and also the BIOS/hardware settings like IRQ or IO.

For a shot in the dark, try this:

sudo su
modprobe aha152x
exit
exit

and see what happens.

then try modprobe aha152x

aha1521: IRQ 12 Possibly wrong Please verify

Yes i've IRQ 11

What's solution

IX1ESM

Posted by cbagger01 on Mar. 14 2005,17:09
modprobe aha152x irq=11
Posted by ix1esm on Mar. 18 2005,11:42
It work whith
modprobe aha152x io=0x340 irq=11

The installation whith "sudo dsl-hdinstall" has'nt error, but when i reboot the machine the tenminal print as follow

Kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
VFS: Cannot open root device "801" or 08:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:01

I formatted the disk sda1 15Mbyte sda2 500Mbyte
may be invert partition?
or LILO don't work propement correctly?

Many thank

Posted by cbagger01 on Mar. 18 2005,23:29
I know of 2 possible problems that could be here.

1)  Your BIOS / Bootloader (LILO) will not boot from this type of SCSI hard drive controller.

2)  Your Bootloader does the job correctly, but your miniroot filesystem and init scripts do not load up the correct SCSI driver.

You will need to uncompress minirt24.gz and mount it as a loop filesystem and then add your aha152x.o driver file into the mountpoint.

Then you will need to add this command to your init script:

insmod aha152x io=0x340 irq=11

This is not an easy job for the novice user.  I wish you luck.

Posted by ix1esm on Mar. 23 2005,08:33
My bootloader work correcly (LILO)
I've uncompress minirt24.gz but is incoprensive format
Where was an applicatition for do this
You can explain the correct process?

Posted by cbagger01 on Mar. 23 2005,18:33
Open an xterminal and type:

sudo su
gunzip minirt24.gz
mkdir image
mount -o loop -t ext2 minirt24 image

Then copy the /lib/modules/2.4.26/kernel/drivers/scsi/aha152x.o  (I think that the path is correct)  file into the appropriate subdirectory inside the image directory.

Then edit one of the init scripts, find out where the initial driver modules are loaded and add

insmod aha152x

at the end of this list and then save the script and exit the image directory back to your home directory.  Then type:

umount minirt24
gzip minirt24

and then copy your new minirt24.gz file so that it overwrites your old minirt24.gz file that is accessed by your boot loader.  It is a good idea to backup the original minirt24.gz file in case you have really hosed things somehow.

This is about as good of an explanation as I can give right now. Hope this helps.

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.