I got more information: I was unable to load the sound modules so I
followed Chris Wedgwood's <chris@cybernet.co.nz> advice about backing
up the patch to mm/vmalloc.c.
After I did this the machine was able to boot 2.1.110 and all SCSI
devices hooked-up to the NCR53c810 were detected and are working fine
now:
ncr53c8xx: at PCI bus 0, device 1, function 0
ncr53c8xx: 53c810 detected
ncr53c810-0: rev=0x01, base=0x21000000, io_port=0xd200, irq=11
ncr53c810-0: ID 7, Fast-10, Parity Checking
ncr53c810-0: restart (scsi reset).
scsi0 : ncr53c8xx - revision 3.0g
scsi : 1 host.
Vendor: CONNER Model: CFP1080S Rev: 4649
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: SyQuest Model: SyJet-S Rev: 0112
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi removable disk sdb at scsi0, channel 0, id 3, lun 0
Vendor: TOSHIBA Model: CD-ROM XM-4101TA Rev: 0064
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0
ncr53c810-0-<0,0>: tagged command queue depth set to 8
ncr53c810-0-<3,0>: tagged command queue depth set to 8
scsi : detected 1 SCSI cdrom 2 SCSI disks total.
ncr53c810-0-<4,*>: FAST-5 SCSI 4.0 MB/s (250 ns, offset 8)
Uniform CD-ROM driver Revision: 2.12
ncr53c810-0-<0,*>: FAST-5 SCSI 5.0 MB/s (200 ns, offset 8)
SCSI device sda: hdwr sector= 512 bytes. Sectors= 2110812 [1030 MB] [1.0 GB]
ncr53c810-0-<3,*>: FAST-5 SCSI 5.0 MB/s (200 ns, offset 8)
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2929800 [1430 MB] [1.4 GB]
I guess the changes to mm/vmalloc.c prevent the NCR driver to allocate
memory (error message is "can't map memory mapped IO region"). I bet
everything would have been fine if I have used normal I/O instead of
memory mapped I/O. So, my conclussion is that there is nothing wrong
with the NCR driver (it's a memory manager problem).
Regards,
Eloy.-
Richard Gooch <rgooch@workaholix.atnf.CSIRO.AU> wrote:
> Hi, all. I just tried 2.1.110 on a machine with the NCR 53c810 SCSI
> card, and I get the following messages:
>
> ncr53c8xx: at PCI bus 0, device 16, function 0
> ncr53c8xx: 53c810 detected
> ncr53c810-0: rev=0x02, base=0xe4000000, io_port=0x6500, irq=9
> ncr53c810-0: can't map memory mapped IO region
> ncr53c810-0: detaching
>
> and since the root FS is accessed through this controller, the machine
> is rooted :-( :-(
>
> On the other hand, with 2.1.104, I get the following:
>
> ncr53c8xx: at PCI bus 0, device 16, function 0
> ncr53c8xx: 53c810 detected
> ncr53c810-0: rev=0x02, base=0xe4000000, io_port=0x6500, irq=9
> ncr53c810-0: ID 7, Fast-10, Parity Checking
> ncr53c810-0: restart (scsi reset).
> scsi0 : ncr53c8xx - revision 2.5f
> scsi : 1 host.
>
> which is definately preferred! Note that 2.1.110 has revision 3.0g of
> the NCR driver.
>
> Regards,
>
> Richard....
>
--Eloy A. Paris Information Technology Department Rockwell Automation Venezuela Telephone: +58-2-9432311 Fax: +58-2-9431645
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html