Solved

Creating device /dev/sonycd with MAKEDEV

Posted on 1997-02-26
1
218 Views
Last Modified: 2013-12-15
Hi,

I found out that the Redhat 4.0 Linux installation had a problem recognizing my CD. So I installed it from my hard drive. After that I tried to get my CD (Sony, type CDU33A) to work, but when I tried to mount my cd, I always get the
error: "....does not recognize cdu31a as a valid block device". Trying to fill in /etc/conf.modules with kernelcfg works (and my kernel is comiled modular), but I still had the same error. Then I checked the /dev/ directory for my device: size of sonycd (and cdu31a) defvices are 0. For the
moment I can access my CD via a line in rc.local:
  /sbin/modprobe cdu31a.o cdu31a_port=0x340 cdu31a_irq=0
and then mounting it (my mount point does exist).
But I want to try the clean way and remaking my device, so I want to use "MAKEDEV sonycd". But this comes bak with the error:
 'device: unknown major number for device cdu31a'
Is this an old version of MAKEDEV? Because I think MAKEDEV makes all devices when installing Linux, and some of those devices are of size 0, which is not very normal.
0
Comment
Question by:liedekef
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 3

Accepted Solution

by:
pc012197 earned 50 total points
ID: 1626954
Devices don't have a size at all. What you get when you do "ls -l <device_name>" is the major and minor numbers of the device. Look at /usr/src/linux/Documentation/devices.txt to see which numbers belong to a certain device:

15 char        Joystick
[...]
   block       Sony CDU-31A/CDU-33A CD-ROM
                  0 = /dev/sonycd       Sony CDU-31a CD-ROM

For every major number there is a character device and a block device, with several minor numbers for each.
So, if an 'ls -l /dev/cdu31a' for you looks like this:

brw-------   1 root root 15,   0 Aug 26  1996 /dev/cdu31a

you're fine. You don't need to rerun MAKEDEV. I suppose this is the case, because if you insert the module with modprobe and mount it, it works all right.

Therefore the problem must lie somewhere in the kerneld and conf.modules setup. What does your conf.modules say about your cdrom device? Do you start kerneld before trying to mount the cdrom or after?


0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

SSH (Secure Shell) - Tips and Tricks As you all know SSH(Secure Shell) is a network protocol, which we use to access/transfer files securely between two networked devices. SSH was actually designed as a replacement for insecure protocols that sen…
Google Drive is extremely cheap offsite storage, and it's even possible to get extra storage for free for two years.  You can use the free account 15GB, and if you have an Android device..when you install Google Drive for the first time it will give…
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question