Re: [PARPORT] Jaz 2GB freezes machine on modprobe ppa


Serge Pineault (Serge.Pineault@hia.nrc.ca)
Wed, 22 Dec 1999 12:22:32 -0800


Hi:

I have made progress on the Jaz/ppa/Mandrake-6.1 front. Firstly,
following a suggestion by Tim Waugh, I added the line
"alias block-major 8 sd_mod" in my conf.modules file
[NOTE: I since discovered that SCSI disk support is
actually built INTO the kernel and NOT as a module. Is this line
actually used? Incidentally, thanks for reminding me
of virtual consoles and making me aware of the existence of
Magic SysRq].

Secondly, since the Jaz
disk I was initially trying to mount contained backup data from
my old Amiga system, I thought the problem might be related
to the filesystem rather than something else. So I tried with a
vfat Jaz disk into the drive, and this time the system did not freeze
or crash [the extra line in the /var/log/messages showed
sda: sda4]. The Jaz disk can then be mounted normally and read.

The next step was to try to read my Amiga backup Jaz disk.
[Yes the Amiga Fast File System, affs, has been compiled as a module].
This did not work with the system rebooting right after the
"modprobe ppa" line and before I could even try to mount
the disk [relevant lines of the /var/log/messages
follow]. But I know I can read this disk on my RedHat 5.2 laptop
[equivalent lines from the /var/log/messages also follow].

In trying to find a solution, I have examined the differences
between the two situations and the following questions have come
to my mind.

1) Does ppa need to know what the filesystem type is on the disk that
is about to be mounted and, if so, how do I pass it that information?
[In the form of options in the conf.modules file?...]
The RedHat 5.2 ppa certainly did not seem to care about it since it
did recognize the two disk partitions [kernel: sda: RDSK sda1 sda2]
before I issued the "mount -t affs /dev/sda2 /mnt/jaz" command.

2) Is the only Jaz disk partition acceptable to ppa the fourth
one, sda4? My amiga partitions are sda1 and sda2.

3) There is an auto-mount utility on Mandrake that does not exist
on RedHat 5.2. For example, this line appears before the ppa lines:

   Dec 19 14:33:59 24 amd[436]: FS: autofs, isofs, nfs, vfat, ext2.

Is it possible that somehow ppa needs some filesystem info and gets
it from this "table". If so, is there a simple way to have the
affs filesystem added in the list?

4) The mount manpages refer to a file /etc/filesystems as well
as /proc/filesystems which are different filesystems which can
be "tried". There is no such /etc/filesystems on my system. Is
there any point in creating it and, if so, what is its format?!!!

Thanks in advance for any help,

Serge Pineault

  
   ************** Some lines from /var/log/messages files....*********

On Linux-Mandrake 6.1 system:
----------------------------
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Dec 19 14:36:45 24 kernel: parport0: PC-style at 0x378 [SPP,PS2]
Dec 19 14:36:45 24 kernel: parport0: no IEEE-1284 device present.
Dec 19 14:36:45 24 kernel: ppa: Version 2.03 (for Linux 2.2.x)
Dec 19 14:36:45 24 kernel: ppa: Found device at ID 3, Attempting to use EPP 32 b
it
Dec 19 14:36:45 24 kernel: ppa: Found device at ID 3, Attempting to use PS/2
Dec 19 14:36:45 24 kernel: ppa: Communication established with ID 3 using PS/2
Dec 19 14:36:45 24 kernel: scsi0 : Iomega VPI0 (ppa) interface
Dec 19 14:36:45 24 kernel: scsi : 1 host.
Dec 19 14:36:46 24 kernel: Vendor: iomega Model: jaz 2GB Rev: E.1
7
Dec 19 14:36:46 24 kernel: Type: Direct-Access ANSI SCS
I revision: 02
Dec 19 14:36:46 24 kernel: Detected scsi removable disk sda at scsi0, channel 0,
 id 3, lun 0
Dec 19 14:36:46 24 kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors= 391
5600 [1911 MB] [1.9 GB]
Dec 19 14:36:46 24 kernel: sda: Write Protect is off

%%%%%%%%%%%%% System reboots or freezes after this line %%%%%%%%%%%%%%%%%%%
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

On RedHat 5.2 system:
--------------------
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
Dec 19 19:13:14 phoenix kernel: ppa: Version 1.42
Dec 19 19:13:14 phoenix kernel: ppa: Probing port 03bc
Dec 19 19:13:14 phoenix kernel: ppa: Probing port 0378
Dec 19 19:13:14 phoenix kernel: ppa: SPP port present
Dec 19 19:13:14 phoenix kernel: ppa: PS/2 bidirectional port present
Dec 19 19:13:14 phoenix kernel: ppa: Found device at ID 3, Attempting to use EPP
 32 bit
Dec 19 19:13:14 phoenix kernel: ppa: Found device at ID 3, Attempting to use PS/
2
Dec 19 19:13:14 phoenix kernel: ppa: Communication established with ID 3 using P
S/2
Dec 19 19:13:14 phoenix kernel: ppa: Probing port 0278
Dec 19 19:13:14 phoenix kernel: scsi0 : Iomega parport ZIP drive
Dec 19 19:13:14 phoenix kernel: scsi : 1 host.
Dec 19 19:13:14 phoenix kernel: Vendor: iomega Model: jaz 2GB Rev
: E.17
Dec 19 19:13:14 phoenix kernel: Type: Direct-Access ANS
I SCSI revision: 02
Dec 19 19:13:14 phoenix kernel: Detected scsi removable disk sda at scsi0, chann
el 0, id 3, lun 0
Dec 19 19:13:21 phoenix kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors
= 3915600 [1911 MB] [1.9 GB]
Dec 19 19:13:21 phoenix kernel: sda: Write Protect is off
Dec 19 19:13:21 phoenix kernel: sda: RDSK sda1 sda2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --



This archive was generated by hypermail 2.0b3 on Wed 22 Dec 1999 - 15:28:32 EST