by Mohammed Elabdellao » Tue, 26 Dec 1995 04:00:00
I've just installed Slackware 2.3 on my Win95 machine. After instalation and
boot using Lilo everything is OK i.e it could detect ny CD-ROM. Then I ran
Win95
then went back to Linux and CD-ROM is still detected (or maybe not and I did
not pay attention). Anyway running Linux from my /dev/hda2 will not see my
CD-ROM anymore but running Linux using my Boot and Root flopies sees it. What's
the deal here? Any pointers will be very much appreciated.
Moh
by Raymond Scott Felle » Tue, 26 Dec 1995 04:00:00
: I've just installed Slackware 2.3 on my Win95 machine. After instalation and
: boot using Lilo everything is OK i.e it could detect ny CD-ROM. Then I ran
: Win95
: then went back to Linux and CD-ROM is still detected (or maybe not and I did
: not pay attention). Anyway running Linux from my /dev/hda2 will not see my
: CD-ROM anymore but running Linux using my Boot and Root flopies sees it. What's
: the deal here? Any pointers will be very much appreciated.
: Moh
This sounds like the usual case where the kernel on the installation boot
floppy has a kernel that supports a wide range of hardware (inorder to
maximize the chance that your Linux installation program can see the CD)
where as the kernel that is placed on your Linux partition often has many
of the hardware drivers stripped off inorder to make the kernel more
compact and efficient. Ideally, the installed kernel will still have the
drivers you need but in your case I think not.
The usual procedure once you get Linux running is to recompile your
kernel with only the options you need (like support for you cdrom). The
procedure to do this is easy but it will take a little reading. I know
you can find the info in one of the howto's as well as in "Running Linux"
and the "Linux Bible".
Good luck,
Ray
--
***************************************************************************
Raymond Fellers | | | |\ | | | \ /
The Saykally Research Group | |__ | | \| |__| / \
Laser Spectroscopy/VdW Clusters |
***************************************************************************
by Todd Graham Lewi » Fri, 29 Dec 1995 04:00:00
If ti works, the config file, 99% probably /etc/fstab, have been
changed. If not, then your floppies might have a different symbolic link
from /dev/cdrom than your HD.
That you can do it from floppy bodes well; it means that it's sopmething
fixeable.
________________________________________________________________________
Copyright 1995, Todd Lewis.This message may not be used or distributed by
the Microsoft Corporation except upon payment of royalties in the sum of
$500 to the copyright owner.Usage constitutes an agreement to these terms.
Quote:> Hello there Linux Gurus,
> I've just installed Slackware 2.3 on my Win95 machine. After instalation and
> boot using Lilo everything is OK i.e it could detect ny CD-ROM. Then I ran
> Win95
> then went back to Linux and CD-ROM is still detected (or maybe not and I did
> not pay attention). Anyway running Linux from my /dev/hda2 will not see my
> CD-ROM anymore but running Linux using my Boot and Root flopies sees it. What's
> the deal here? Any pointers will be very much appreciated.
> Moh
1. Strange CD-ROM Issue (aka CD-ROM Problem)
Ok...this is a fairly strange problem that I don't even know how to
begin fixing. I have Linux Mandrake 8.0 installed on my Thinkpad
i1400 laptop. I initially had problem installing off of a CD that a
friend burned for me, but I attributed this to a bad downloaded iso
image and I downloaded the install straight to my hard drive and
installed from the hard drive. Now, I think that the cd is really not
corrupted and is related to a problem with my cd-rom operating in
Linux.
Now, after working out most of the kinks in my system, I have really
started to use it. My first problem relating to the CD drive has to
do with a CD that I had filled with my favorite mp3 songs. In
windows, this cd always played fine in Winamp and the songs worked
great. However, I noticed that, in Linux, the majority of the songs
get cut off anywhere from 30% to 90% of the way through. XMMS just
stops playing. KDE Media player also stops in the same spot. I
thought that the songs must have been corrupted when they were burned
onto the cd, but, like I said, they work fine in windows off of the
cd. To try to see if it was a corruption problem, I did a diff on one
of the songs that I had on the cd with an identical song on my hard
drive. The diff encountered an I/O error when it tried to do the
compare. I then tried copying the song to the hard drive from the cd,
but the copy stalled at about the same % as the song would stop
playing in XMMS and I got a copy error. If I copy the song in windows
to the hard drive, then go back into linux and do a diff, the two
songs are identical. What could be causing this problem??? I'm
absolutely clueless as to how to proceed. Any help is much
appreciated.
Note: I have heard that this may be related to supermount. I have
heard a lot of people complain about it. The only thing that makes me
believe it's not supermount related is that most people who say
supermount sucks also can't get their cd-rom drives to work. However,
mine is detected and works. The songs and some files just get cut off
or encounter read errors. Could this be a supermount problem or is it
something else?
2. Kerneld / binfmt_aout & modules...
3. bizarre cd-rom behavior on install
5. CD-ROM mount needs source <--> source needs CD-ROM mount
6. ATI MAch64 svgalib or driver??
7. CD-ROM driver for Turtle Beach/Funai 6X CD-ROM?
9. Intsall from CD-ROM without a CD-ROM
10. PAS 16 CD-ROM and Slakware96, mounting CD-ROM crashes system
12. Mount CD-ROM over network and report as CD-ROM
13. Universal CD-ROM resells LINUX CD-ROM