Mandrake 10.1 won't recognize SATA CD drive

k27lawlr · 03-13-2005, 06:01 PM

I have an Asus A8V Deluxe mobo connected to an SATA harddrive and SATA CD-RW/DVD-ROM...it boots from the harddrive fine, and the VIA controller recognizes both the harddrive and the cd drive.

I can't mount the cd drive, however, because mandrake doesn't seem to know it's there. I looked in /proc/scsi/scsi and all it listed was the harddrive. I confess to being pretty ignorant when it comes to things of this nature so I don't want to change anything lest I screw something up.

Anyone know what is wrong?

tlowk · 03-19-2005, 04:43 PM

Take a look in
dmseg | less

maybe you find some explanation how the kernel call's your cd, another place to look is
/sys/block and look for the sr scd letters

cat /sys/block/sda/device/model
shows you what each device is, So when you have the brand name you can use this brute force approach

grep -i CDROM /sys/block/*/device/model

just try something relevant instead of CDROM as a model/type name

Tlowl

k27lawlr · 03-27-2005, 03:40 PM

The only thing in /sys/block is sda (harddrive), fd0 (floppy) and hdc (cd-rom i stole from another computer). The kernel doesn't seem to know there is something connected to the second SATA bus. How does the kernel communicate with the VIA controller...could this be the problem?

dmesg brings up everything...my wireless interface, extra cd-rom, floppy, it just skips over the sata drive.

tlowk · 03-28-2005, 02:12 AM

Just a thought

For some devices you can specify as kernel parameter 'hdd=ide-cd' as append= in the
lilo.conf and probably very similar for GRUB

If you have your kernel sources, you van find more inspiration in the file

/usr/src/linux-2.6.10/Documentation/kernel-parameters.txt
(or a places that looks similar in case you have your kernel source at another
place.

I expect that a sata cdrom is not recognized by default, another option can be that
you need to load a specific kernel module for it, altough I don't see wich one, maybe
the scsi cdrom, since sata appear very scsi-like

Tlowk

atom · 03-28-2005, 03:14 AM

I have the same problem (This topic)

There's lsmod output as well as everything else I discovered there.

k27lawlr · 04-06-2005, 01:38 PM

I think I've found the drive in /dev...it's called sr0. I added it to /etc/fstab with

none /mnt/cdrom supermount ro,dev=/dev/sr0,fs=udf:iso9660,--,iocharset=iso8859-1 0 0

However, when I try mount /mnt/cdrom as root, i get a mount: permission denied error.

And on a side note, if anyone could explain to me why it's in /dev as sr0 I would be fascinated. I'm a newbie (in case you couldn't already tell)

atom · 04-06-2005, 01:43 PM

I've seen this before, even on this forum, but no sr0 at my place.

about the meaning: the "s" definitely stands for "sata", and the "r" probably (and I stress: PROBABLY) stands for (cd)rom.
Um, could you send me your .config of your kernel so I can compare it to mine and see where I have gone wrong? Then I can help you mount the drive.

k27lawlr · 04-06-2005, 01:52 PM

I would be happy to if you tell me how to find it

I've actually mounted it now (other drive was mounted to /mnt/cdrom already, stupid me), and mount tells me that it's mounting /dev/sr0, but it seems to think that there isn't a CD in the drive, or that the CD is empty (console doesn't list any files, and I know there are some on the disc I put in).

k27lawlr · 04-06-2005, 02:00 PM

hope this is what you need:

Code:

# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECS=m
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
CONFIG_IDE_TASK_IOCTL=y
# CONFIG_IDE_TASKFILE_IO is not set

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=m
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_OFFBOARD=y
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=m
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_AEC62XX=m
CONFIG_BLK_DEV_ALI15X3=y
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_ATIIXP is not set
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=m
# CONFIG_BLK_DEV_CY82C693 is not set
CONFIG_BLK_DEV_CS5520=m
CONFIG_BLK_DEV_CS5530=m
CONFIG_BLK_DEV_HPT34X=y
CONFIG_HPT34X_AUTODMA=y
CONFIG_BLK_DEV_HPT366=y
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_IT8212=m
# CONFIG_BLK_DEV_NS87415 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
CONFIG_PDC202XX_FORCE=y
CONFIG_BLK_DEV_SVWKS=y
CONFIG_BLK_DEV_SIIMAGE=y
CONFIG_BLK_DEV_SIS5513=y
CONFIG_BLK_DEV_SLC90E66=m
CONFIG_BLK_DEV_TRM290=m
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_ST=m
CONFIG_CHR_DEV_OSST=m
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y

#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=m
CONFIG_SCSI_FC_ATTRS=m

#
# SCSI low-level drivers
#
CONFIG_BLK_DEV_3W_XXXX_RAID=m
CONFIG_SCSI_3W_9XXX=m
CONFIG_SCSI_ACARD=m
CONFIG_SCSI_AACRAID=m
CONFIG_SCSI_AIC7XXX=m
CONFIG_AIC7XXX_CMDS_PER_DEVICE=253
CONFIG_AIC7XXX_RESET_DELAY_MS=15000
# CONFIG_AIC7XXX_BUILD_FIRMWARE is not set
# CONFIG_AIC7XXX_DEBUG_ENABLE is not set
CONFIG_AIC7XXX_DEBUG_MASK=0
CONFIG_AIC7XXX_REG_PRETTY_PRINT=y
CONFIG_SCSI_AIC7XXX_OLD=m
CONFIG_SCSI_AIC79XX=m
CONFIG_AIC79XX_CMDS_PER_DEVICE=32
CONFIG_AIC79XX_RESET_DELAY_MS=15000
# CONFIG_AIC79XX_BUILD_FIRMWARE is not set
# CONFIG_AIC79XX_ENABLE_RD_STRM is not set
# CONFIG_AIC79XX_DEBUG_ENABLE is not set
CONFIG_AIC79XX_DEBUG_MASK=0
CONFIG_AIC79XX_REG_PRETTY_PRINT=y
CONFIG_SCSI_MEGARAID=m
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_SVW=m
CONFIG_SCSI_ATA_PIIX=m
CONFIG_SCSI_SATA_NV=m
CONFIG_SCSI_SATA_PROMISE=m
CONFIG_SCSI_SATA_SX4=m
CONFIG_SCSI_SATA_SIL=m
CONFIG_SCSI_SATA_SIS=m
CONFIG_SCSI_SATA_VIA=m
CONFIG_SCSI_SATA_VITESSE=m
CONFIG_SCSI_BUSLOGIC=m
# CONFIG_SCSI_OMIT_FLASHPOINT is not set
CONFIG_SCSI_DMX3191D=m
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
# CONFIG_SCSI_EATA_LINKED_COMMANDS is not set
CONFIG_SCSI_EATA_MAX_TAGS=16
CONFIG_SCSI_EATA_PIO=m
CONFIG_SCSI_FUTURE_DOMAIN=m
CONFIG_SCSI_GDTH=m
CONFIG_SCSI_IPS=m
CONFIG_SCSI_INITIO=m
CONFIG_SCSI_INIA100=m
CONFIG_SCSI_PPA=m
CONFIG_SCSI_IMM=m
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
# CONFIG_PPSCSI is not set
CONFIG_SCSI_SYM53C8XX_2=m
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
CONFIG_SCSI_IPR=m
# CONFIG_SCSI_IPR_TRACE is not set
# CONFIG_SCSI_IPR_DUMP is not set
CONFIG_SCSI_QLOGIC_ISP=m
CONFIG_SCSI_QLOGIC_FC=m
# CONFIG_SCSI_QLOGIC_FC_FIRMWARE is not set
CONFIG_SCSI_QLOGIC_1280=m
CONFIG_SCSI_QLA2XXX=m
CONFIG_SCSI_QLA21XX=m
CONFIG_SCSI_QLA22XX=m
CONFIG_SCSI_QLA2300=m
CONFIG_SCSI_QLA2322=m
CONFIG_SCSI_QLA6312=m
CONFIG_SCSI_QLA6322=m
CONFIG_SCSI_DC395x=m
CONFIG_SCSI_DC390T=m
CONFIG_SCSI_DEBUG=m

atom · 04-06-2005, 02:00 PM

well, the most obvious way to find it is

Code:

$ locate .config #reads as locate [dot]config

if locate doesn't find anything, try looking in /usr/src/ and go into the folder "linux" if there is one. Then write

Code:

$ ls -la | grep .config

and if anything shows up, you've found it.

If you haven't found anything, then tell me exactly which version of the precompiled kernel you are using (for instance, fedora core 2.6.11-something ) and where you got it from (or what the name of the rpm package is) and i'll get it from the net.

Waiting for your answer...

Gasper

tlowk · 04-06-2005, 02:08 PM

about this /dev/sr0

it is a scsi cdrom, which can be normal since sata use scsi emulation, I think it will require the drivers for a scsi cdrom.

modprobe sr_mod
can load the driver in case the driver is available.

Tlowk

k27lawlr · 04-06-2005, 02:13 PM

Doesn't find anything...anywhere else to get the driver?

atom · 04-06-2005, 02:15 PM

dude this is all compiled as modules

. I see you are fammiliar with the approach. I, however, hate initrd so i'm compiling all sata support into the kernel (have no IDE stuff whatsoever). I'm gonna see if i have the same config as stated here.... Will post followup.

atom · 04-06-2005, 02:27 PM

Ok... I got nuts today and just compiled in all scsi controller drivers

. If it doesn't work now, it's never going to.
will post followup when I reboot (probably tomorow).

tlowk · 04-06-2005, 02:30 PM

from the config file above, I see that it is configured are a module so it should exist
if not you could try

make modules
make modules_install

in your kernel tree
(/usr/src/linux-2.6.x)

try also to see if the module is load after a modprobe
with lsmod

Tlowk
(fyi I don't have regular internet access for the moment)