IN2000 driver/config

IN2000 driver/config

Post by Peter » Sun, 01 Jan 1995 11:17:02



Hi, there

        I just upgraded to the SLS distribution, which uses Linux 1.1.51.
I added the IN2000 ALPHA driver and everything seemed fine.  I was able
to fdisk my /dev/sda and set up partitions.

        First I built 2 512MB partitions under DOS and they can be seen
from Linux for both read and write.  Then I fdisk'ed a third partition
and tried to do a mke2fs.  At the end of the fdisk run, the program
hangs, indicating that a write (10) failed with something like "00 00 24
5e 26 00 00 00 aa 00" as an error.  A message also suggests that a SCSI
bus hang occurred.  The only thing I could do to get out is hard reset.
(Note that I need to flip my dip switches going between DOS and Linux.)
What did I do wrong?

        Also, the program indicated that I had only 1314 cylinders (64
hds, 32 sectors) with the ST43400 2.9GB disk I had.  This comes out to
some 1.3 GB only.  When I use the DOS fdisk, it can see 2.0 GBs, as
documented by the IN2000 installation guide (limit of 1024 cylinders ->
1024 * 64 * 63 * 512).  Why does the Linux fdisk underestimate?  I
presume that I can fudge this by going into the expert mode in fdisk and
force it to say that there are at least 2016 cylinders (2.0 GB).  I don't
know if I can go to 2765 (2.9 GB).  Any comments?

        Thanks for any help in advance.

                                                Peter Lu

 
 
 

IN2000 driver/config

Post by Daryl Richar » Wed, 04 Jan 1995 03:45:33


:       I just upgraded to the SLS distribution, which uses Linux 1.1.51.
: I added the IN2000 ALPHA driver and everything seemed fine.  I was able
: to fdisk my /dev/sda and set up partitions.

 As I have said many times before, there is a problem with the IN2000 driver,
and kernels >1.1.0... This is what causes the random lock-up you have in
the next paragraph..

:       First I built 2 512MB partitions under DOS and they can be seen
: from Linux for both read and write.  Then I fdisk'ed a third partition
: and tried to do a mke2fs.  At the end of the fdisk run, the program
: hangs, indicating that a write (10) failed with something like "00 00 24
: 5e 26 00 00 00 aa 00" as an error.  A message also suggests that a SCSI
: bus hang occurred.  The only thing I could do to get out is hard reset.
: (Note that I need to flip my dip switches going between DOS and Linux.)
: What did I do wrong?

:       Also, the program indicated that I had only 1314 cylinders (64
: hds, 32 sectors) with the ST43400 2.9GB disk I had.  This comes out to
: some 1.3 GB only.  When I use the DOS fdisk, it can see 2.0 GBs, as
: documented by the IN2000 installation guide (limit of 1024 cylinders ->
: 1024 * 64 * 63 * 512).  Why does the Linux fdisk underestimate?  I
: presume that I can fudge this by going into the expert mode in fdisk and
: force it to say that there are at least 2016 cylinders (2.0 GB).  I don't
: know if I can go to 2765 (2.9 GB).  Any comments?

 SCSI doesn't really use cylinders to access the drive, but it there is some
translation done to match DOS's partition table.. You should be able to fudge
the code in in2000.c, right at the end, to return whatever size you want.
This may cause hassles in fdisk, but if you follow some of the guidelines for
IDE drivers with >1024 cylinders, you shouldn't have any problems..

 
 
 

1. Make sure drivers/input/Config.in goes before drivers/char/Config.in

This makes drivers/input/Config.in always comes before drivers/char/Config.in.

Currently, alpha, mips and mips64 source drivers/input/Config.in after
drivers/char/Config.in.  But as noted in most of the other arches
config.in, drivers/input/Config.in must come before
drivers/char/Config.in for all depenancies to be worked out.  This adds
that comments to these arches as well as fixing the dependancy.

On the off chance that this is intentional, linux-mips and linux-alpha
are CC'ed as well.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

===== arch/alpha/config.in 1.15 vs edited =====
--- 1.15/arch/alpha/config.in   Sat May 25 19:37:06 2002

 fi
 endmenu

+#
+# input before char - char/joystick depends on it. As does USB.
+#
+source drivers/input/Config.in
 source drivers/char/Config.in


 endmenu

 source drivers/usb/Config.in
-source drivers/input/Config.in

 source net/bluetooth/Config.in

===== arch/mips/config.in 1.6 vs edited =====
--- 1.6/arch/mips/config.in     Thu Feb 28 06:57:19 2002

 fi
 endmenu

+#
+# input before char - char/joystick depends on it. As does USB.
+#
+source drivers/input/Config.in
 source drivers/char/Config.in


 fi

 source drivers/usb/Config.in
-source drivers/input/Config.in

 mainmenu_option next_comment
 comment 'Kernel hacking'
===== arch/mips64/config.in 1.6 vs edited =====
--- 1.6/arch/mips64/config.in   Thu Feb 28 06:57:19 2002

 fi
 endmenu

+#
+# input before char - char/joystick depends on it. As does USB.
+#
+source drivers/input/Config.in
 source drivers/char/Config.in


 fi

 source drivers/usb/Config.in
-source drivers/input/Config.in

 mainmenu_option next_comment
 comment 'Kernel hacking'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. strange root filesystem full problem

3. in2000, what kernel, config used?

4. CD ROM in Setup! Still dosen't Work!!

5. new Always-IN2000 scsi driver available

6. VxVM / VxFS 3.5 vxlicrep

7. IN2000 driver?

8. 2.5.46-mm1

9. Help requested compiling kernel with in2000 scsi driver

10. improved IN2000 scsi driver available

11. 2.4.20 compile fix for drivers/scsi/in2000.c

12. IN2000 Driver...HELP

13. IN2000 Driver Modificatoion Question