NEC-260; Can't mount; Get 'not a block device error'

NEC-260; Can't mount; Get 'not a block device error'

Post by Keith Bobit » Sun, 19 Feb 1995 03:23:43



        I have read plenty of posts on NEC260's but I haven't seen
this error reported before.  My NEC-260R is in a Gateway P5-90.  The
machine has two 1G WDC drives on the EIDE interface and the cdrom
alone on the ISA IDE interface.  Linux is on the second WDC drive
with / in hdb2, swap in hdb3, and /usr in hdb4. I use version 1.1.92
of the kernel.  The kernel doesn't seem to recognize the cdrom or the
ISA IDE interface at boot time.  It finds the EIDE interface at
IRQ14 but not ISA interface at IRQ15.  When I try to mount the cdrom
on /dev/nec260 (major 26 minor 0) or /dev/hdc (major 22 minor 0),
I get the following error message:

        mount: /dev/hdc (or whatever) is not a block device

Both /dev/nec260 and /dev/hdc are block devices; their permissions
start with a 'b'.  I have deleted and remade the device files with
the mknod command and have run the "MAKEDEV..etc.." script in
/usr/src/linux/drivers/block that is referenced in the ide.c and
ide-cd.c source files.  I have also played with the #defines in
ide.c to no avail.  I have tried /dev/hdc[0-16] for a device file and
all fail in the same way.  

Thanks in advance.

-------------------------------------------------------------
Keith Bobitt                        Ph. 919-941-5740x4125    

Wandel & Goltermann Technologies    RTP, NC                  
-------------------------------------------------------------

 
 
 

NEC-260; Can't mount; Get 'not a block device error'

Post by John Duks » Fri, 24 Feb 1995 03:45:42


Keith:

in order to get your NEC260  cd rom drive to work, you'll need to edit
/usr/src/linux/drivers/block/nec260.c

in the defines in the beginning you'll need to set the IRQ to 15, set the
I/O address properly  (probably 0x170) and set the defines for whether or
not the drive is alone on the bus (which it seems it is) and whether it
is the master drive on the bus (which it would also be).

Once you make these changes and recompile the kernel, you should be able
to mount your nec260 without a hitch.

Good luck.

-John
--
John Duksta




 
 
 

1. NEC-260R; Can't mount; Get 'not a block device' error

        I have read plenty of posts on NEC260's but I haven't seen
this error reported before.  My NEC-260R is in a Gateway P5-90.  The
machine has two 1G WDC drives on the EIDE interface and the cdrom
alone on the ISA IDE interface.  Linux is on the second WDC drive
with / in hdb2, swap in hdb3, and /usr in hdb4. I use version 1.1.92
of the kernel.  The kernel doesn't seem to recognize the cdrom or the
ISA IDE interface at boot time.  It finds the EIDE interface at
IRQ14 but not ISA interface at IRQ15.  When I try to mount the cdrom
on /dev/nec260 (major 26 minor 0) or /dev/hdc (major 22 minor 0),
I get the following error message:

        mount: /dev/hdc (or whatever) is not a block device

Both /dev/nec260 and /dev/hdc are block devices; their permissions
start with a 'b'.  I have deleted and remade the device files with
the mknod command and have run the "MAKEDEV..etc.." script in
/usr/src/linux/drivers/block that is referenced in the ide.c and
ide-cd.c source files.  I have also played with the #defines in
ide.c to no avail.  I have tried /dev/hdc[0-16] for a device file and
all fail in the same way.  I boot from DOS with loadlinux.

Thanks in advance.

-------------------------------------------------------------
Keith Bobitt                        Ph. 919-941-5740x4125    

Wandel & Goltermann Technologies    RTP, NC                  
-------------------------------------------------------------

2. tape backup

3. NEC-260R; Can't mount - 'not a block device' error

4. corel linux

5. 2.4 -ac zip ppa -- 'mount: /dev/sda4 is not a valid block device'

6. Help - libwww(perl) installation

7. unable to mount 'remote' loopback block devices

8. LILO version 22.6.1 released

9. Linux won't recognize my CD-ROM (nec cdr-260)

10. NEC 260 / Music CD's Anybody?

11. the kernel does not recognize /dev/fd0 as a block device (maybe 'insmod driver'?)