I can confirm, in generic or Huge, dvd is sr0. But in my custom kernel 2.6.34-rc1 as well as 2.6.33-rc8, dvd is hdc.
Running Huge correctly creates /dev/dvd link to the dvd drive.
But generic does not.
When running generic the first line in the normal boot is a message about a memory collision or something like that. It does not show up using Huge. I'll try to write it down next time I see it.
Looking at my syslog, I see the following two lines are the first seen up on booting. They start on March 4 and happen every reboot.
udevd[1106]: bind failed: address already in use
udevd[1106]: error binding control socket, seems udevd is already running.
But I also see these when booting Huge when most things seem to work.
Looking at kernel configs
Huge:
Code:
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
My custom
Code:
CONFIG_HAVE_IDE=y
CONFIG_IDE=y
#
# Please see Documentation/ide/ide.txt for help/info on IDE drives
#
CONFIG_IDE_XFER_MODE=y
CONFIG_IDE_ATAPI=y
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_IDE_GD=y
CONFIG_IDE_GD_ATA=y
# CONFIG_IDE_GD_ATAPI is not set
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEACPI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y
#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_PLATFORM is not set
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEDMA_SFF=y
#
# PCI IDE chipsets support
#
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
CONFIG_BLK_DEV_ATIIXP=y
# CONFIG_BLK_DEV_... not set
...
CONFIG_BLK_DEV_IDEDMA=y
#
# SCSI device support
I can try doing custom kernel with ide settings from Huge. That should make my dvd link to sr0. Still have to play with why /dev/dvd on generic does not link correctly and see if that situation exists for custom kernel.