CDROM problems
I have two drives, a newer LG slaved on the 1st IDE and an older Smart-and-friendly: slaved on the 2nd IDE. Both have worked fine in the past. Now: Both will play music fine using Kscd (for analog mode) or xmms, etc., digital mode. The LG will not mount data disks at all--LED never stops blinking. This may not be a problem with linux at all--I have no idea why this as stopped working. This is, of course, the newer and faster drive. The S+F will not mount by mount /dev/hdd according to /etc/fstab. I can successfully mount it by the full command sudo mount -t iso9660 /dev/hdd . Clicking the KDE desktop icon for the drive will not mount it either. Any ideas? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: custom initrd on stock kernel installation (cdrom problems)
kristian kvilekval a écrit : Background: Having discovered that my cdrom disappeared a while ago, I tracked down that the loading order of modules determines whether I have a Cdrom device or not. Specifically I need to force ide-core cdrom ide-cd ide-disk ide-generic to load before any scsi drivers load specifically by placing them in the initial ramdisk used during the kernel load. I accomplished this by placing the above list in /etc/mkinitrd/modules Question: I would like to run debian stock kernels from unstable. However I would like a custom initrd instance to be installed while installing the standard kernel. Is this possible? Yes, and you don't have to do anything. The standard kernel doesn't come with an initrd, the initrd is build with options you set in /etc/mkinitrd when you install the new kernel package. cu. It appear that kernel-img.conf allows set a ramdisk command, but this fails even with mkinitrd (documentation says it must be compatible with mkinitrd?) Thanks for any suggestions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
custom initrd on stock kernel installation (cdrom problems)
Background: Having discovered that my cdrom disappeared a while ago, I tracked down that the loading order of modules determines whether I have a Cdrom device or not. Specifically I need to force ide-core cdrom ide-cd ide-disk ide-generic to load before any scsi drivers load specifically by placing them in the initial ramdisk used during the kernel load. I accomplished this by placing the above list in /etc/mkinitrd/modules Question: I would like to run debian stock kernels from unstable. However I would like a custom initrd instance to be installed while installing the standard kernel. Is this possible? It appear that kernel-img.conf allows set a ramdisk command, but this fails even with mkinitrd (documentation says it must be compatible with mkinitrd?) Thanks for any suggestions. -- Kristian Kvilekval [EMAIL PROTECTED] http://www.cs.ucsb.edu/~kris w:805-893-2526 h:504-9756 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Cdrom Problems
When I mount the cdrom in kde, half the time, I can't unmount it or can't eject it Can anyone offer me some information on this or let me know where I might find it? Thanks for your time, Bill H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cdrom Problems
tech wrote: When I mount the cdrom in kde, half the time, I can't unmount it or can't eject it Can anyone offer me some information on this or let me know where I might find it? Thanks for your time, Bill H. I believe it may have to do with famd; try killing that process and see if it releases the CD-ROM. I have no detailed knowledge of this problem, however. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Cdrom Problems
I beleve it was kio_audiocd preventing me from ejecting the cd. I removed the kdemultimedia-plugin package and it seems to fix the problem. I don't use music cd's on the system anyway. Thanks for your time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
autofs cdrom problems
Hi all, I've just set up autofs to handle my cdrom mounting, but I've hit a slight snag: antgel $ eject /cdrom umount: /dev/cdrom mount disagrees with the fstab eject: unmount of `/dev/cdrom' failed antgel $ Here's the line from my fstab: /dev/cdrom /cdrom iso9660 ro,user,sync,nodev,nosuid,noauto 0 0 And this is from /etc/auto.misc: cdrom -fstype=iso9660,ro,sync,nodev,nosuid,user,noauto :/dev/cdrom It then worked when I changed my fstab to read: /dev/cdrom /var/autofs/misc/cdrom iso9660 ro,user,sync,nodev,nosuid 0 0 even though /cdrom is a symlink to /var/autofs/misc/cdrom. I also had to type eject /var/autofs/misc/cdrom. In this case, eject /cdrom caused thetry to open and close immediately. Also, I can't figure out how to play audio cd's. This used to be as simple as selecting the /cdrom directory in xmms. Can anyone tell me what's wrong? A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CDROM problems with installer 2.2.23
Hi Have installed potato(carefully,multiple times) using boot floppy images 2.2.23 from CDROM. On reboot, apt-get tries to access packages and gets error: fs iso9660 not supported by kernel. Using mount has always given the same error. I tried using an older version installer (2.1) which explicitly refused to load the cdrom module. The CDROM is ATAPI, ASUS CD S400/A and should not need a special driver. The computer is AMD K5 -- Debian is hdc secondary master, CDROM is hdd secondary slave. CDROM works fine on Mandrake 8.0 which is on a different physical drive hda, dual boot using LILO. CDROM works on floppy or CDROM Debian boot media, just not from Debian on hdc. I tried to use ftp for access thinking to try to compile a different kernel but on the last two tries apt-get now cannot name resolve the Debian ftp site. I had gotten further with this Debian install and after some effort X-windows was working somewhat. I then tried to mess with kernel issues to get the CDROM working but I'm not winning. As I reread this, sounds like hdc maybe can't reach the CDROM. I'll check the hardware, but are there any other insights? For some reason the kernel does not seem to support iso9660 file format. Could be some module matter. Have you got an option to choose some other kernel for the installation? Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Shaul Karl [EMAIL PROTECTED]
Re: CDROM problems with installer 2.2.23
On Monday 17 September 2001 09:37 pm, Shaul Karl wrote: It sounds like you need to recompile and add iso9660 support. That is the standard error. One quick way to check is to take out the media when booting. A simple recompile however should fix it. Topp Dogg Hi Have installed potato(carefully,multiple times) using boot floppy images 2.2.23 from CDROM. On reboot, apt-get tries to access packages and gets error: fs iso9660 not supported by kernel. Using mount has always given the same error. I tried using an older version installer (2.1) which explicitly refused to load the cdrom module. The CDROM is ATAPI, ASUS CD S400/A and should not need a special driver. The computer is AMD K5 -- Debian is hdc secondary master, CDROM is hdd secondary slave. CDROM works fine on Mandrake 8.0 which is on a different physical drive hda, dual boot using LILO. CDROM works on floppy or CDROM Debian boot media, just not from Debian on hdc. I tried to use ftp for access thinking to try to compile a different kernel but on the last two tries apt-get now cannot name resolve the Debian ftp site. I had gotten further with this Debian install and after some effort X-windows was working somewhat. I then tried to mess with kernel issues to get the CDROM working but I'm not winning. As I reread this, sounds like hdc maybe can't reach the CDROM. I'll check the hardware, but are there any other insights? For some reason the kernel does not seem to support iso9660 file format. Could be some module matter. Have you got an option to choose some other kernel for the installation? Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: CDROM problems with installer 2.2.23
On Monday 17 September 2001 08:19 pm, richard wrote: Hi Have installed potato(carefully,multiple times) using boot floppy images 2.2.23 from CDROM. On reboot, apt-get tries to access packages and gets error: fs iso9660 not supported by kernel. Using mount has always given the same error. I tried using an older version installer (2.1) Sounds like you don't have support in your kernel for ISO 9660 file systems. Which floppy images did you use? I'd imagine they'd all at least have support for ISO 9660. If you're getting an fs error then it's likely your drive was detected but the kernel can't read the media. You could check your kernel logs (dmesg) to see if your CD-ROM is detected, but I suspect it has been. Usually your recourse is to recompile the kernel with support for ISO 9660 file system, but if you're using the stock kernel from the installation disks then the fact that it can't read the CD is strange indeed. which explicitly refused to load the cdrom module. The CDROM is ATAPI, ASUS CD S400/A and should not need a special driver. The computer is AMD K5 -- Debian is hdc secondary master, CDROM is hdd secondary slave. CDROM works fine on Mandrake 8.0 which is on a different physical drive hda, dual boot using LILO. CDROM works on floppy or CDROM Debian boot media, just not from Debian on hdc. I tried to use ftp for access thinking to try to compile a different kernel but on the last two tries apt-get now cannot name resolve the Debian ftp site. I had gotten further with this Debian install and after some effort X-windows was working somewhat. I then tried to mess with kernel issues to get the CDROM working but I'm not winning. As I reread this, sounds like hdc maybe can't reach the CDROM. I'll check the hardware, but are there any other insights? Richard
CDROM problems with installer 2.2.23
Hi Have installed potato(carefully,multiple times) using boot floppy images 2.2.23 from CDROM. On reboot, apt-get tries to access packages and gets error: fs iso9660 not supported by kernel. Using mount has always given the same error. I tried using an older version installer (2.1) which explicitly refused to load the cdrom module. The CDROM is ATAPI, ASUS CD S400/A and should not need a special driver. The computer is AMD K5 -- Debian is hdc secondary master, CDROM is hdd secondary slave. CDROM works fine on Mandrake 8.0 which is on a different physical drive hda, dual boot using LILO. CDROM works on floppy or CDROM Debian boot media, just not from Debian on hdc. I tried to use ftp for access thinking to try to compile a different kernel but on the last two tries apt-get now cannot name resolve the Debian ftp site. I had gotten further with this Debian install and after some effort X-windows was working somewhat. I then tried to mess with kernel issues to get the CDROM working but I'm not winning. As I reread this, sounds like hdc maybe can't reach the CDROM. I'll check the hardware, but are there any other insights? Richard
newbie: mounting Mitsumi cdrom problems
My goal is to get dselect to recognize my cdrom drive so that I can install applications. After booting the OS logging on as /, I enter dselect. I choose [0. Access] and select multicd. The cd is in the drive. System responds: I see that /dev/cdrom exists and is a block device. Insert the CD-ROM and enter the block device name [/dev/cdrom]: So I accept the default. System doesn't like that and responds: mount: the kernal does not recognize /dev/cdrom as a block device. (maybe 'insmod driver'?) unable to mount /dev/cdrom on /var/lib/dpkg/methods/mnt, type iso9660 Insert the CD-ROM and enter the block device name [/dev/cdrom]: And from there I'm stuck. I'm a linux newbie; yesterday was my first attempt to install a system. Since I couldn't get the cdrom working, I made installation floppies of Debian 2.1 (slink) from the debian.org site. Installation went smoothly. I even successfully installed the cdrom driver correctly after divining the port address, DMA, and IRQ settings from the interface card. When I boot the OS, the boot banner says: mcd=0x320,9: Mitsumi status, type and version: 10 D 2 Double Speed CD ROM and it also says: Failed initialization of WD-7000 SCSI card! scsi: o hosts scsi: detected total More hardware info: Micron 486DX 100, CD is Mitsumi FX001D. The interface card on the CD says CD-ROM Drive 16BIT I/F Card 74-1881A. I'm kind of confused about the SCSI failed initialization msg, b/c my HD is IDE and seems to work fine. The Mitsumi manual says nothing about the interface card being SCSI or IDE. Did I leave out any other relevant information? Oh yeah, I'm a Gemini. thanks in advance for any suggestions.
Re: newbie: mounting Mitsumi cdrom problems
mcd=0x320,9: Mitsumi status, type and version: 10 D 2 Double Speed CD ROM and it also says: Failed initialization of WD-7000 SCSI card! scsi: o hosts scsi: detected total More hardware info: Micron 486DX 100, CD is Mitsumi FX001D. The interface card on the CD says CD-ROM Drive 16BIT I/F Card 74-1881A. I'm kind of confused about the SCSI failed initialization msg, b/c my HD is IDE and seems to work fine. The Mitsumi manual says nothing about the interface card being SCSI or IDE. Did I leave out any other relevant information? Oh yeah, I'm a Gemini. Offhand, i'd say that you're trying to install a SCSI module at boot time, and it's failing because the card doesn't exist. cat /etc/modules to find out what modules are being loaded at boot. - flip - [EMAIL PROTECTED]/[EMAIL PROTECTED] -- Good. Bad. I'm the guy with the gun. -- Ash, Army of Darkness
Re: newbie: mounting Mitsumi cdrom problems
On Fri, Jun 11, 1999 at 01:25:27PM -0600, David Brode wrote: My goal is to get dselect to recognize my cdrom drive so that I can install applications. After booting the OS logging on as /, I enter dselect. I choose [0. Access] and select multicd. The cd is in the drive. System responds: I see that /dev/cdrom exists and is a block device. Insert the CD-ROM and enter the block device name [/dev/cdrom]: So I accept the default. System doesn't like that and responds: mount: the kernal does not recognize /dev/cdrom as a block device. (maybe 'insmod driver'?) unable to mount /dev/cdrom on /var/lib/dpkg/methods/mnt, type iso9660 Insert the CD-ROM and enter the block device name [/dev/cdrom]: And from there I'm stuck. I'm a linux newbie; yesterday was my first attempt to install a system. Since I couldn't get the cdrom working, I made installation floppies of Debian 2.1 (slink) from the debian.org site. Installation went smoothly. I even successfully installed the cdrom driver correctly after divining the port address, DMA, and IRQ settings from the interface card. When I boot the OS, the boot banner says: mcd=0x320,9: Mitsumi status, type and version: 10 D 2 Double Speed CD ROM You should probably use /dev/mcd (or link /dev/cdrom to /dev/mcd). and it also says: Failed initialization of WD-7000 SCSI card! scsi: o hosts scsi: detected total The default kernel has a module for scsi and the probe fails, since there are no scsi devices. Ignore it. My advice would be to compile your own kernel after you get things running and configure it only have the features (built-in or module) that your hardware requires. This will avoid these types of messages. More hardware info: Micron 486DX 100, CD is Mitsumi FX001D. The interface card on the CD says CD-ROM Drive 16BIT I/F Card 74-1881A. I'm kind of confused about the SCSI failed initialization msg, b/c my HD is IDE and seems to work fine. The Mitsumi manual says nothing about the interface card being SCSI or IDE. Did I leave out any other relevant information? Oh yeah, I'm a Gemini. Oh. In that case ignore my advice above. I'm a Capricorn. Bob -- Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
Cdrom Problems
Hello, I want to install Debian from my CD-Rom (the Base system I already installed from floppy's), but Debian does not want me to: it does not recognize my CD-Rom. I have an unknown brand - Megabitz, model 8000 AT - which says to be PIN-Compatible with the Sony CDU31a. So, I tried all sorts of settings with the cdu31a driver, but none of these worked. I also tried other drivers (cdrom, sbpcd etc.) but nothing was successful yet. Has anybody got an idea what else I can do?
Re: Cdrom Problems
I'm guessing when you set up support for the device you didn't pass parameters for it. Unfortunately for this device this is necessary since the driver can't/won't autoprobe for the device. Here's the snippet from the CDROM-Howto: 4.3.3. Cdu31a Driver Principal author: Corey Minyard ([EMAIL PROTECTED]) Multi-session support: yes Multiple drive support: no Loadable module support: yes Reading audio frames: yes Auto-probing: no Device file: /dev/cdu31a, major 15 Configuration file: cdu31a.h Kernel config option: Sony CDU31A/CDU33A CDROM support? README file: cdu31a This driver accepts a kernel command line of the form: cdu31a=io-address,interrupt,PAS The first number is the I/O base address of the card (e.g. 0x340). The second is the interrupt number to use (0 means to use polled i/o). The optional third parameter should be PAS if the drive is connected to a Pro-Audio Spectrum 16 sound card, otherwise left blank. If the driver is loaded as a module, it uses a slightly different format. When loading the driver using the modprobe or insmod command, the parameters take the form: cdu31a_port=io-address cdu31a_irq=interrupt The base io-address is required while the interrupt number is optional. The device file can be created using: # mknod /dev/cdu31a b 15 0 See the file cdu31a for more information on this driver. Also see the Web page put together by Jeffrey Oxenreider ([EMAIL PROTECTED]) that covers a lot of common problems with these drives. It can be found at http://www.infinet.com/~zureal/cdu31a.html. W.S. van Oijen wrote: Hello, I want to install Debian from my CD-Rom (the Base system I already installed from floppy's), but Debian does not want me to: it does not recognize my CD-Rom. I have an unknown brand - Megabitz, model 8000 AT - which says to be PIN-Compatible with the Sony CDU31a. So, I tried all sorts of settings with the cdu31a driver, but none of these worked. I also tried other drivers (cdrom, sbpcd etc.) but nothing was successful yet. Has anybody got an idea what else I can do? -- Jens B. Jorgensen [EMAIL PROTECTED]
cdrom problems
Hi! I'm getting these reports whenever I access my new cdrom (Samsung 32x max). I'm using kernel 2.0.37prelatest. Everything works fine, I just get these annoying messages and the access to the CD-ROM is slower. Can anybody help? Thanks! -- p.
Re: Linux CDROM problems
It could also be that time of the CD-ROM's life when it has to go and meet it's maker...It's a good possibility as you say it also occurs in NT. I think the likelyhood of the BIOS settings screwing it up are minimal (I've found linux to be very robust when it comes to using CD-ROM drives). Cheers Dave On Wed, Mar 03, 1999 at 22:19 -, Sarah Iain wrote: I am running Debian 2.0 and am expriencing problems with my CDROM. Previously all was going well and I could add packages via the 2.0 CD, however recently my CD player has been giving problems (when I power up the active light is flashing constantly and never stops). When I boot into debian the kernel finds that the device is not ready with error (I've appended the dmesg report below) hdb: no response (status = 0x90) Is there any way in which I can manually reset the CD drive from the prompt, because dselect tells me that hdb is not a valid block device. I have a Samsung CDROM which is normally on /dev/hdb - the active light flashes from the moment I power on - could this be a problem with the BIOS settings? I unfortunately lost (i.e. wasn't clever enough to write down) the BIOS settings I had when the CD was working. I believe this may be the case since I am now having similar problems under Windows NT. Many thanks, Dr Iain Scott, [EMAIL PROTECTED] -- Dave Swegen | Debian 2.0 on Linux i386 2.2.1 [EMAIL PROTECTED] | PGP key available on request [EMAIL PROTECTED] | Linux: The Choice of a GNU Generation --
Linux CDROM problems
I am running Debian 2.0 and am expriencing problems with my CDROM. Previously all was going well and I could add packages via the 2.0 CD, however recently my CD player has been giving problems (when I power up the active light is flashing constantly and never stops). When I boot into debian the kernel finds that the device is not ready with error (I've appended the dmesg report below) hdb: no response (status = 0x90)Is there any way in which I can manually reset the CD drive from the prompt, because dselect tells me that hdb is not a valid block device. I have a Samsung CDROM which is normally on /dev/hdb - the active light flashes from the moment I power on - could this be a problem with the BIOS settings? I unfortunately lost (i.e. wasn't clever enough to write down) the BIOS settings I had when the CD was working. I believe this may be the case since I am now having similar problems under Windows NT. Many thanks, Dr Iain Scott, [EMAIL PROTECTED] Mesg Description: Binary data
Re: cdrom problems
ITom - WebIroda [EMAIL PROTECTED] writes: The exact error message would help. Also, what do you get in `dmesg | more' starting from the ide: line? Here's the message: ISO9660 Extensions: RRIP_1991A Interleaved files not (yet) supported. Warning: defective cdrom (volume sequence number). Enabling cruft mount option. You shouldn't get this from the official Debian CD, or from a CD that didn't do this on another drive. Are there any errors at the end of the output of dmesg after this happens? I sometimes get CDU31A: Read error: 0x40 but my drive (not an IDE one) recovers. If it didn't recognise it properly (rare now) maybe adding hdd=cdrom will help. I read this in the cdrom HOWTO. Where should I add it? When LILO starts up, hold down SHIFT or another key like that if it doesn't wait for you to type something. Then at the LILO boot: prompt, type linux hdd=cdrom (or something similar). If it works, add it to /etc/lilo.conf as `append=hdd=cdrom' and rerun lilo. -- Carey Evans * http://home.clear.net.nz/pages/c.evans/ gc Neniu anticipas la hispanan Inkvizicion. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: cdrom problems
ISO9660 Extensions: RRIP_1991A Interleaved files not (yet) supported. Warning: defective cdrom (volume sequence number). Enabling cruft mount option. You shouldn't get this from the official Debian CD, or from a CD that didn't do this on another drive. The awful thing is that I got this message _only_ from the Official Debian 1.3 Binary CD (from cheapbytes), that worked before with another drive, and I can read this CD without errors under DOS or Win95. Are there any errors at the end of the output of dmesg after this happens? I sometimes get CDU31A: Read error: 0x40 but my drive (not an IDE one) recovers. Yes. There are some files on the CD, which cannot be read by the system, but I only have the errors when I try 'ls -l' the mounted CD. e.g. I cannot read a symbolic link stable - bo, so I even cannot install any package with dselect. When LILO starts up, hold down SHIFT or another key like that if it doesn't wait for you to type something. Then at the LILO boot: prompt, type linux hdd=cdrom (or something similar). If it works, add it to /etc/lilo.conf as `append=hdd=cdrom' and rerun lilo. OK I'll try it. Thanks! Tamas Imrei [EMAIL PROTECTED] 'ITom' - [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: cdrom problems
On Sun, 26 Oct 1997, ITom - WebIroda wrote: I thought this was normal. It means the kernel's noticed you've got a different CD-ROM in than last time it looked. OK Thanks. interleaved files not (yet) supported'. I didn't have any problems with the other drive with this Debian cd. The exact error message would help. Also, what do you get in `dmesg | more' starting from the ide: line? Here's the message: ISO9660 Extensions: RRIP_1991A Interleaved files not (yet) supported. Warning: defective cdrom (volume sequence number). Enabling cruft mount option. If it didn't recognise it properly (rare now) maybe adding hdd=cdrom will help. I read this in the cdrom HOWTO. Where should I add it? I should be the last one to tell you and I hope someone will give you a better answer - I think you should include it in /etc/lilo.conf See how I added the fact that mem=128M bytes in my system; I think you do the same thing with another append boot=/dev/hda1 root=/dev/hda1 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 image=/vmlinuz label=Linux append=mem=128M read-only As I said I am complete novice but I think I saw somewhere in the HowTos that you may add append=hdd=cdrom Good luck // Daniel J. Mashao -- [EMAIL PROTECTED] http://www.ee.uct.ac.za/~daniel // -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
cdrom problems
Hello! I've installed v1.3.1 from the Official Debian Binary cd, I've used a noname 24x cdrom drive for installation. Now I had to give back that drive, now I have a Creative/Matshita CR-581 quad-speed drive. Every time I mount a cd with the command line: itom# mount -t iso9660 -r /dev/hdd /cdrom I get a message which says: '/dev/hdd: media changed' which I didn't receive once with the other drive. Is this an error, or what? The second thing is that when I try to use dselect I get an error message, (I'm sorry, I don't remember exactly) which says that 'a bad or corrupted or sg. like that cd detected, using cruft (?), interleaved files not (yet) supported'. I didn't have any problems with the other drive with this Debian cd. Does anyone has any ideas about it? This Matshita drive is connected to the secondary ide controller for slave mode (like the other was). Pse excuse me a little offtopic: I had problems with this drive under win95, too, but changing the driver program from a usual cdatapi.sys to a cr_atapi.sys helped. Thanks in advance, ITom -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: cdrom problems
ITom - WebIroda [EMAIL PROTECTED] writes: [snip] I get a message which says: '/dev/hdd: media changed' which I didn't receive once with the other drive. Is this an error, or what? I thought this was normal. It means the kernel's noticed you've got a different CD-ROM in than last time it looked. The second thing is that when I try to use dselect I get an error message, (I'm sorry, I don't remember exactly) which says that 'a bad or corrupted or sg. like that cd detected, using cruft (?), interleaved files not (yet) supported'. I didn't have any problems with the other drive with this Debian cd. The exact error message would help. Also, what do you get in `dmesg | more' starting from the ide: line? If it didn't recognise it properly (rare now) maybe adding hdd=cdrom will help. -- Carey Evans * http://home.clear.net.nz/pages/c.evans/ gc Neniu anticipas la hispanan Inkvizicion. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: cdrom problems
I thought this was normal. It means the kernel's noticed you've got a different CD-ROM in than last time it looked. OK Thanks. interleaved files not (yet) supported'. I didn't have any problems with the other drive with this Debian cd. The exact error message would help. Also, what do you get in `dmesg | more' starting from the ide: line? Here's the message: ISO9660 Extensions: RRIP_1991A Interleaved files not (yet) supported. Warning: defective cdrom (volume sequence number). Enabling cruft mount option. If it didn't recognise it properly (rare now) maybe adding hdd=cdrom will help. I read this in the cdrom HOWTO. Where should I add it? Thanks again, ITom -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
