From: Edward Macfarlane Smith <snowfire@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Cc: Hlaing Oo <hlaing_1999@yahoo.com>
Subject: Re: missing cdrom in new kernel 2.4.26
Date: Wed, 14 Jul 2004 16:42:13 +0100 [thread overview]
Message-ID: <200407141642.14047.snowfire@blueyonder.co.uk> (raw)
In-Reply-To: <20040714121731.52870.qmail@web90005.mail.scd.yahoo.com>
On Wednesday 14 July 2004 13:17, Hlaing Oo wrote:
> >>>>> my new kernel dmesg is below
>
> #cat /var/log/dmesg
> Linux version 2.4.26 (root@localhost.localdomain) (gcc
> version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #3 SMP
> BIOS strings suggest APM reports battery life in
> minutes and wrong byte order.
> Kernel command line: ro root=/dev/hda2 hdc=ide-scsi
> ide_setup: hdc=ide-scsi
---cut---
old
> EXT3-fs: mounted filesystem with ordered data mode.
> SCSI subsystem driver Revision: 1.00
> scsi0 : SCSI host adapter emulation for IDE ATAPI
> devices
> Vendor: MATSHITA Model: UJDA310 Rev: 1.34
> Type: CD-ROM ANSI SCSI
> revision: 02
In both old and new you are passing in hdc=ide-scsi on the boot line, telling
the kernel to use ide-scsi for hdc. (I'd guess that /dev/cdrom points
to /dev/sr0). The bit below shows that it has correctly inserted the ide-scsi
module in your old kernel and detected the cdrom. That is missing from the
new one. Are you sure you built the ide-scsi module in your new kernel? Have
you checked /var/log/messages or /var/log/warn to see if there were any
errors about problems with the ide-scsi module?
Fairly certain I remember getting the same error one time when I forgot to
build ide-scsi.
Regards,
Edward
next prev parent reply other threads:[~2004-07-14 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 12:17 missing cdrom in new kernel 2.4.26 Hlaing Oo
2004-07-14 12:35 ` Martin Zwickel
2004-07-14 15:42 ` Edward Macfarlane Smith [this message]
2004-07-14 16:38 ` Hlaing Oo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200407141642.14047.snowfire@blueyonder.co.uk \
--to=snowfire@blueyonder.co.uk \
--cc=hlaing_1999@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox