From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 Description of problem: Automated kickstart installs of RHEL WS3 U4 on new Dell Precision 470 systems with IDE DVD burners generate incorrect symlink /dev/cdrom --> /dev/hdc during the install process. Manually running /usr/sbin/kudzu after firstboot fixes the symlink to /dev/cdrom --> /dev/scd0 Version-Release number of selected component (if applicable): 1.1.22.9 How reproducible: Always Steps to Reproduce: 1. perform a kickstarted install of RHEL WS3 U4, allowing automatic reboot 2. Wait for system to come up 3. Type `ls -l /dev/cdrom` Actual Results: lrwxrwxrwx 1 root root 9 Jan 22 01:35 /dev/cdrom -> /dev/hdc In this case the CDROM will work fine for burning only if ide-scsi module is removed, cannot be mounted for reading at all. Expected Results: lrwxrwxrwx 1 root root 9 Jan 22 01:35 /dev/cdrom -> /dev/scd0 And when this link is there and ide-scsi loaded, all works fine (reading and writing). Additional info: The systems have 2 SATA drives that show up as sda and sdb. The IDE DVD drive is secondary master. Here's what kudzu's changing when I run it manually. Output of (diff /etc/sysconfig/hwconf hwconf.orig) 306c306 < device: scd0 --- > device: hdc 308,313c308 < desc: "Philips DVD+-RW DVD8631" < host: 2 < id: 0 < channel: 0 < lun: 0 < generic: sg2 --- > desc: "PHILIPS DVD+/-RW DVD8631" 317a313 > device: fb0
Is ide-scsi appended to the kernel commandline in grub.conf?
Yes, ide-scsi is on the grub.conf kernel commandline: title Realm Linux (2.4.21-27.0.1.ELsmp) root (hd1,0) kernel /vmlinuz-2.4.21-27.0.1.ELsmp ro root=LABEL=/ hdc=ide- scsi initrd /initrd-2.4.21-27.0.1.ELsmp.img
This problem is resolved in the next release of Red Hat Enterprise Linux (RHEL 4). Red Hat does not currently plan to provide a resolution for this in a Red Hat Enterprise Linux update for currently deployed systems. With the goal of minimizing risk of change for deployed systems, and in response to customer and partner requirements, Red Hat takes a conservative approach when evaluating changes for inclusion in maintenance updates for currently deployed products. The primary objectives of update releases are to enable new hardware platform support and to resolve critical defects.