| Author |
How I make Debian etch recognize my Samsung SCR-830 cdrom drive
|
|
|
|
To get Debian etch to recognize my Samsung SCR-830 cdrom drive,
I add the parameter 'cdrom=scr-830' to the 'kernel' command line using
the Grub editor as follows (I am not sure if the parameter 'single' is
mandatory or not):
kernel /boot/vmlinuz-2.6.18-5-486 root=/dev/hde10 ro single \ cdrom=scr-830
Here are a few relevant bits from the resulting 'dmesg' output text:
Linux version 2.6.18-5-486 (Debian 2.6.18.dfsg.1-13etch4)
(dannf@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 Tue Oct 2 23:38:54 UTC 2007
[...]
Kernel command line: root=/dev/hde10 ro single cdrom=scr-830
[...]
Probing IDE interface ide0...
[...]
hda: SCR-830, ATAPI CD/DVD-ROM drive
[...]
Whereupon
nohostname[gonzo]:/gonzo/stage/issues/
..$ mount /media/cdrom0
mount: block device /dev/hda is write-protected, mounting read-only
nohostname[gonzo]:/gonzo/stage/issues/
..$ ls -F /media/cdrom0
README.diskdefines doc/ isolinux/ pics/ preseed/ ubuntu@
dists/ install/ md5sum.txt pool/ tools/
Voila!
--
| |
| Randolf Balasus 2007-10-29, 1:12 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
anon wrote:
>
> To get Debian etch to recognize my Samsung SCR-830 cdrom drive,
> I add the parameter 'cdrom=scr-830' to the 'kernel' command line using
> the Grub editor as follows (I am not sure if the parameter 'single' is
> mandatory or not):
>
>
> kernel /boot/vmlinuz-2.6.18-5-486 root=/dev/hde10 ro single \ cdrom=scr-830
> Hello anon, are you sure that is the right syntax for this?
what i sth eexact problem? normally the kernel detects the CD-Rom drive
without any parameters. In your output the kernel detects it as /dev/hda
and it is successfully mounted. but it seems that the parameter is not
required. can you access the drive?
Regards Randolf Balasus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHJhoFPtLQAXC/ xvYRAkcEAJ9fJ9DlWLSjwbu90xJ9rV0FBxsyJwCg
igvI
HUIJft6l/hXH1sv5HHLKamU=
=u0pu
-----END PGP SIGNATURE-----
| |
|
| Randolf Balasus wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> anon wrote:
>
> what is the exact problem? normally the kernel detects the CD-Rom drive
> without any parameters. In your output the kernel detects it as /dev/hda
> and it is successfully mounted. but it seems that the parameter is not
> required. can you access the drive?
>
Thank you.
All I know at this point is that if I omit 'cdrom=scr-830' and boot
single, I can mount and read from the drive, but when I then press
ctrl-D to resume booting, it goes into an endless loop printing out
error messages that say
Oct 29 14:53:21 nohostname kernel: hdb: status error: status=0x00 { }
Oct 29 14:53:21 nohostname kernel: ide: failed opcode was: unknown
Oct 29 14:53:21 nohostname kernel: hdb: status error: status=0x00 { }
Oct 29 14:53:21 nohostname kernel: ide: failed opcode was: unknown
Oct 29 14:53:21 nohostname kernel: hdb: status error: status=0x00 { }
Oct 29 14:53:21 nohostname kernel: ide: failed opcode was: unknown
Oct 29 14:53:21 nohostname kernel: hdb: status error: status=0x00 { }
Oct 29 14:53:21 nohostname kernel: ide: failed opcode was: unknown
and I have to hit reset to exit.
I should probably also mention that adding the 'cdrom=scr-830' argument
doesn't *always* work, but sometimes is a lot better than never (I am
running on Debian etch at this moment).
| |
| Randolf Balasus 2007-10-30, 7:14 am |
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello
>
> I should probably also mention that adding the 'cdrom=scr-830' argument
> doesn't *always* work, but sometimes is a lot better than never (I am
> running on Debian etch at this moment).
>
and now you want make this change permanent?
in /boot/grub/menu.lst can you write it. (or am I wrong)
But by the way your kernel seems very old. Maybe it is better to change
this kernel first to a more recent.
Randolf Balasus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHJuQQPtLQAXC/xvYRAh/WAKCXU4G9UZ0YUno/4XlfaJvA94YvZgCcDNu6
KBo/Xi47ZVjZlVY6cOno2OA=
=Y/1q
-----END PGP SIGNATURE-----
| |
|
| Randolf Balasus wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello
>
> But by the way your kernel seems very old. Maybe it is better to change
> this kernel first to a more recent.
Thank you.
What is the most recent kernel? I ran apt-get update and it seems to
think I already have the most recent one installed.
> Randolf Balasus
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHJuQQPtLQAXC/xvYRAh/WAKCXU4G9UZ0YUno/4XlfaJvA94YvZgCcDNu6
> KBo/Xi47ZVjZlVY6cOno2OA=
> =Y/1q
> -----END PGP SIGNATURE-----
| |
| sk8r-365 2007-10-30, 7:12 pm |
| Horton heard a Who named anon saying:
> Randolf Balasus wrote:
>
> Thank you.
>
> What is the most recent kernel? I ran apt-get update and it seems to
> think I already have the most recent one installed.
Your kernel is current ... it's for i486 rather than i686.
--
sk8r-365
The U.S. Congress enjoys damaging "big business"
but are themselves building big government!
| |
|
| sk8r-365 wrote:
> Horton heard a Who named anon saying:
>
> Your kernel is current ... it's for i486 rather than i686.
>
And my computer has an AMD k6-3 cpu, which is certainly not i686.
| |
| sk8r-365 2007-10-30, 7:12 pm |
| Horton heard a Who named anon saying:
> sk8r-365 wrote:
>
> And my computer has an AMD k6-3 cpu, which is certainly not i686.
Add the 686 kernel, keeping the 486 as well, and try it out.
--
sk8r-365
The U.S. Congress enjoys damaging "big business"
but are themselves building big government!
| |
|
| sk8r-365 wrote:
> Horton heard a Who named anon saying:
>
> Add the 686 kernel, keeping the 486 as well, and try it out.
>
That would be grabbing at straws.
Given (1) that I can boot a bootable CD from the drive, (2) that the
drive works fine on Win98se and Win2k, (3) that despite some error
messages during boot, the drive works ok on Slackware-11 (linux 2.4
kernel) but prevents Debian etch (linux 2.6 kernel) from booting -- and
even then not always -- I decided finally to swap in a generic Mitsumi
drive.
Problem solved.
<B
| |
| sk8r-365 2007-11-01, 7:12 pm |
| Horton heard a Who named anon saying:
> sk8r-365 wrote:
>
> That would be grabbing at straws.
Perhaps, but a drowning man will grab at anything and the water seemed
to be at your nostrils.
<snip>
> I decided finally to swap in a generic Mitsumi drive.
>
> Problem solved.
Pleased to hear it.
--
sk8r-365
The U.S. government is destroying our freedoms daily
but are themselves enjoying "liberties" at our expense!
|
|
|
|