no /dev/cdr* devices created in Slack 12.0
Luis P. Mendes
I have to use an older disk with Slack 12.0 in a new system and compiled
a new kernel: 2.6.31.6.
With default 12.0 kernel (2.6.21.5), the two ide cd/dvd-rom/rw were
created as /dev/hda and /dev/hdc.
Now:
# ll /dev/cd*
ls: cannot access /dev/cd*: No such file or directory
# ll /dev/hd*
ls: cannot access /dev/hd*: No such file or directory
I deleted /etc/udev/rules.d/75-optical-devices.rules file so that it
could be recreated by /lib/udev/cdrom-symlinks.sh, but it is not.
When I try to find one of the dvd drives on dmesg, I get nothing:
# grep -i 'asus' /var/log/dmesg
(nothing shown for this one or the other)
After greping .config of the new kernel for IDE options:
# grep -i 'ide' .config | grep -vi 'trident' | grep -vi 'video'
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_TIMINGS=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=y
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEACPI=y
CONFIG_IDE_TASK_IOCTL=y
CONFIG_IDE_PROC_FS=y
# IDE chipset support/bugfixes
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPNP=m
CONFIG_BLK_DEV_IDEDMA_SFF=y
# PCI IDE chipsets support
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# Other IDE chipsets support
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_SND_RIPTIDE is not set
CONFIG_LEDS_TRIGGER_IDE_DISK=y
CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
# lspci | grep -i 'ide'
00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port
SATA IDE Controller
00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port
SATA IDE Controller
03:00.0 IDE interface: JMicron Technology Corp. JMB368 IDE controller
So,I grep .config for JMicron
# grep -i jmicron .config
CONFIG_BLK_DEV_JMICRON=y
CONFIG_PATA_JMICRON=y
and do the same for intel:
# grep -i intel .config
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_CPU_SUP_INTEL=y
CONFIG_X86_MCE_INTEL=y
CONFIG_MICROCODE_INTEL=y
# CONFIG_MOXA_INTELLIO is not set
CONFIG_HW_RANDOM_INTEL=y
CONFIG_AGP_INTEL=y
CONFIG_SND_HDA_INTEL=y
CONFIG_SND_HDA_CODEC_INTELHDMI=y
# CONFIG_SND_INTEL8X0 is not set
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_INTEL_IOATDMA is not set
# CONFIG_INTEL_MENLOW is not set
# CONFIG_CRYPTO_CRC32C_INTEL is not set
CONFIG_KVM_INTEL=y
Please, can someone show me the light in this issue?
What's wrong? What should I do?
Luis
Grant
>Hi,
>
>I have to use an older disk with Slack 12.0 in a new system and compiled
>a new kernel: 2.6.31.6.
>
>With default 12.0 kernel (2.6.21.5), the two ide cd/dvd-rom/rw were
>created as /dev/hda and /dev/hdc.
/dev/sr0, /dev/sr1?
Grant.
--
http://bugsplatter.id.au
Luis P. Mendes
No /dev/sr{0,1}, Grant.
Thank you,
Luis
Henrik Carlqvist
> a new kernel: 2.6.31.6.
As upgrading the kernel might have some disadvantages and also means some
work I suppose you have a good reason to upgrade the kernel only instead
of keeping the old kernel or upgrade the entire distribution to get a
complete system with matching parts?
> With default 12.0 kernel (2.6.21.5), the two ide cd/dvd-rom/rw were
> created as /dev/hda and /dev/hdc.
So, the old kernel with its old config were able to identify and use your
hardware.
> When I try to find one of the dvd drives on dmesg, I get nothing
> After greping .config of the new kernel for IDE options:
> CONFIG_IDE=y
...
> Please, can someone show me the light in this issue? What's wrong? What
> should I do?
Instead of trying to configure a kernel from scratch it is usually easier
to start with a working configuration and only make small changes to that
configuration.
If I for some reason would have to upgrade a working kernel in Slackware I
would copy the configuration file from the old working kernel, it was
pointed to by the link /boot/config and should be copied to .config in
your new kernel source tree. Then in the kernel source tree do a "make
oldconfig" before configuring and compiling your new kernel.
Example:
cp /boot/config-huge-smp-2.6.21.5 /usr/src/linux-2.6.31.6/.config
cd /usr/src/linux-2.6.31.6
make oldconfig
make bzImage
make modules
make modules_install
Then copy .config, System.map and bzImage to /boot with some well chosen
names and fix your symbolic links and run lilo. It might be a good idea to
keep an entry for an old known working kernel in lilo also.
Finally, recompile and install any installed modules not part of the
kernel source tree. Those modules might be drivers for video or audio or
other custom modules like kqemu. In the case of Slackware 12.0 I think
that svgalib_helper-1.9.25_2.6.21.5-i486-1 package is the only standard
Slackware package that contains kernel modules except for the
kernel-modules-* packages.
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
root
>
> Instead of trying to configure a kernel from scratch it is usually easier
> to start with a working configuration and only make small changes to that
> configuration.
>
> If I for some reason would have to upgrade a working kernel in Slackware I
> would copy the configuration file from the old working kernel, it was
> pointed to by the link /boot/config and should be copied to .config in
> your new kernel source tree. Then in the kernel source tree do a "make
> oldconfig" before configuring and compiling your new kernel.
Whenever I make changes to the original .config I have to
change all the file system types from M to *, otherwise
my new kernel can't mount the (ext2) root file system.