Re: cdrom problem
One of the things that I use to confirm how a CD/DVD is set up, is to try eject /dev/hdb, and BTW, why are you looking for them as scd0, mine are all hdb, hdc, and hdd.Maybe you are mounting the wrong device, or one that does not exist. When I type eject /dev/hbd I get this:[EMAIL PROTECTED]:/dev$ eject /dev/hdbeject: unable to find or open device for: `/dev/hdb' I don't know if that is any helpful at all.-- - Joseph Smidt [EMAIL PROTECTED]
Re: cdrom problem
Joseph Smidt wrote:
When I try to mount something on my cdrom I get this error: mount: special
device /dev/scd0 does not exist
When I type dmesg | grep CD I get no results.
When I type lsscsi I get: [0:0:0:0]diskATA TOSHIBA MK1032GS
AS02 -
Does anybody know what I can do about these problems so I can mount things.
By the way, it says /dev/cdrom doesn't exist.
On my machine, /dev/cdrom is simply a link to /dev/hdc.
You can search for devices by using hdparm if you have it installed...
# hdparm /dev/hda
/dev/hda:
multcount= 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq= 0 (off)
using_dma= 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead= 256 (on)
geometry = 65535/16/63, sectors = 78165360, start = 0
# hdparm /dev/hdb
/dev/hdb: No such device or address
# hdparm /dev/hdc
/dev/hdc:
HDIO_GET_MULTCOUNT failed: Invalid argument
IO_support = 0 (default 16-bit)
unmaskirq= 0 (off)
using_dma= 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead= 256 (on)
HDIO_GETGEO failed: Invalid argument
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdrom problem
When I try to mount something on my cdrom I get this error: mount: special device /dev/scd0 does not existWhen I type dmesg | grep CD I get no results.When I type lsscsi I get: [0:0:0:0] disk ATA TOSHIBA MK1032GS AS02 - Does anybody know what I can do about these problems so I can mount things.By the way, it says /dev/cdrom doesn't exist. Thanks -- - Joseph Smidt [EMAIL PROTECTED]
Re: cdrom problem
On Sunday 16 April 2006 7:44 pm, Joseph Smidt so eloquently stated: When I try to mount something on my cdrom I get this error: mount: special device /dev/scd0 does not exist When I type dmesg | grep CD I get no results. When I type lsscsi I get: [0:0:0:0]diskATA TOSHIBA MK1032GS AS02 - Does anybody know what I can do about these problems so I can mount things. One of the things that I use to confirm how a CD/DVD is set up, is to try eject /dev/hdb, and BTW, why are you looking for them as scd0, mine are all hdb, hdc, and hdd. Maybe you are mounting the wrong device, or one that does not exist. Rob -- Mountlake Terrace, WA Onward, Through the fog! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
Andrea Vettorello wrote: On Tue, 04 Jan 2005 02:45:23 +0200, Necati DEMiR [EMAIL PROTECTED] wrote: Andrea Vettorello wrote: On Mon, 03 Jan 2005 21:38:34 +0200, Necati DEMiR [EMAIL PROTECTED] wrote: [...] it is a cd-writer. i think debian knows a cd-writer is connected and loads the module ide-scsi, but it doesn't create hdb,cdrom or sr* under /dev/ directory. it is not problem for me to use my cd-writer as a cd-rom. i wanna use it as a cdrom. After solving this problem, i will try to use it as a cd-writer, but my first aim is, to mount my cd-rom. OK? :) First of all don't use SCSI emulation for your CD-ROM, then check if in your /etc/udev/rules.d there's a symlink to ../cd-aliases.rules, if not present create it, then restart udev... i did the followings; # ls -al /etc/udev/rules.d/ total 8 drwxr-xr-x 2 root root 4096 Dec 26 18:37 . drwxr-xr-x 5 root root 4096 Jan 3 19:46 .. lrwxrwxrwx 1 root root 19 Dec 26 18:37 cd-aliases.rules - ../cd-aliases.rules lrwxrwxrwx 1 root root 13 Dec 26 18:37 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 12 Dec 26 18:27 z_hal-plugdev.rules - ../hal.rules # cd /etc/init.d # ./udev restart Recreating device nodes...done. # ls /dev/ MAKEDEV hda7 ram0shm tty19 tty35 tty51 ttyS1 [...] ttyS41 urandom as you see there is no hdb or cdrom still! Have you checked if you have at least ide-cd module loaded? Modprobe it if not. And put a line in your /etc/modules too if not present. The ide-cd depends on ide-core and cdrom, so modprobing it should load them too... Andrea thanks to everybody! i solved my problem. i forgot that everything needs module. these are the steps how i solved my problem; #modprobe ide_cd #echo ide_cd/etc/modules again and again thanx to everybody! -- Necati DEMiR [EMAIL PROTECTED] http://demir.web.tr My Public Key = http://demir.web.tr/ndemir.asc - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
Try giving the file system type in your mount command: mount -t iso9660 /dev/hdb /mnt/cdrom it didin't work. i am telling from stracth; i rebooted the machine; then # dmesg|grep hdb ide_setup: hdb=ide-scsi ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA hdb: HL-DT-ST GCE-8400B, ATAPI CD/DVD-ROM drive # ls /dev/ MAKEDEVinitctl ram14tty10 tty3 tty49 ttyS1 ttyS29 ttyS48 adsp inputram15tty11 tty30 tty5 ttyS10 ttyS3 ttyS49 agpgartkmem ram2 tty12 tty31 tty50 ttyS11 ttyS30 ttyS5 audio kmsg ram3 tty13 tty32 tty51 ttyS12 ttyS31 ttyS50 consoleloop ram4 tty14 tty33 tty52 ttyS13 ttyS32 ttyS51 core mem ram5 tty15 tty34 tty53 ttyS14 ttyS33 ttyS52 dspmixerram6 tty16 tty35 tty54 ttyS15 ttyS34 ttyS53 fb0net ram7 tty17 tty36 tty55 ttyS16 ttyS35 ttyS6 fd null ram8 tty18 tty37 tty56 ttyS17 ttyS36 ttyS7 fd0port ram9 tty19 tty38 tty57 ttyS18 ttyS37 ttyS8 full ppp random tty2 tty39 tty58 ttyS19 ttyS38 ttyS9 hdaprinter rtc tty20 tty4 tty59 ttyS2 ttyS39 urandom hda1 psauxshm tty21 tty40 tty6 ttyS20 ttyS4 vbi0 hda2 ptmx snd tty22 tty41 tty60 ttyS21 ttyS40 vcs hda3 pts sndstat tty23 tty42 tty61 ttyS22 ttyS41 vcs1 hda4 ram0 stderr tty24 tty43 tty62 ttyS23 ttyS42 vcs7 hda5 ram1 stdintty25 tty44 tty63 ttyS24 ttyS43 vcsa hda6 ram10stdout tty26 tty45 tty7 ttyS25 ttyS44 vcsa1 hda7 ram11tty tty27 tty46 tty8 ttyS26 ttyS45 vcsa7 hda8 ram12tty0 tty28 tty47 tty9 ttyS27 ttyS46 video0 hw_random ram13tty1 tty29 tty48 ttyS0 ttyS28 ttyS47 zero as you see there is no cdrom or hdb in /dev directory. what should i do after that? -- Necati DEMiR [EMAIL PROTECTED] http://demir.web.tr My Public Key = http://demir.web.tr/ndemir.asc - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
On Mon, 03 Jan 2005 12:17:10 +0200, Necati DEMiR [EMAIL PROTECTED] wrote: Try giving the file system type in your mount command: mount -t iso9660 /dev/hdb /mnt/cdrom it didin't work. i am telling from stracth; i rebooted the machine; then # dmesg|grep hdb ide_setup: hdb=ide-scsi ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA hdb: HL-DT-ST GCE-8400B, ATAPI CD/DVD-ROM drive # ls /dev/ MAKEDEVinitctl ram14tty10 tty3 tty49 ttyS1 ttyS29 ttyS48 adsp inputram15tty11 tty30 tty5 ttyS10 ttyS3 ttyS49 agpgartkmem ram2 tty12 tty31 tty50 ttyS11 ttyS30 ttyS5 audio kmsg ram3 tty13 tty32 tty51 ttyS12 ttyS31 ttyS50 consoleloop ram4 tty14 tty33 tty52 ttyS13 ttyS32 ttyS51 core mem ram5 tty15 tty34 tty53 ttyS14 ttyS33 ttyS52 dspmixerram6 tty16 tty35 tty54 ttyS15 ttyS34 ttyS53 fb0net ram7 tty17 tty36 tty55 ttyS16 ttyS35 ttyS6 fd null ram8 tty18 tty37 tty56 ttyS17 ttyS36 ttyS7 fd0port ram9 tty19 tty38 tty57 ttyS18 ttyS37 ttyS8 full ppp random tty2 tty39 tty58 ttyS19 ttyS38 ttyS9 hdaprinter rtc tty20 tty4 tty59 ttyS2 ttyS39 urandom hda1 psauxshm tty21 tty40 tty6 ttyS20 ttyS4 vbi0 hda2 ptmx snd tty22 tty41 tty60 ttyS21 ttyS40 vcs hda3 pts sndstat tty23 tty42 tty61 ttyS22 ttyS41 vcs1 hda4 ram0 stderr tty24 tty43 tty62 ttyS23 ttyS42 vcs7 hda5 ram1 stdintty25 tty44 tty63 ttyS24 ttyS43 vcsa hda6 ram10stdout tty26 tty45 tty7 ttyS25 ttyS44 vcsa1 hda7 ram11tty tty27 tty46 tty8 ttyS26 ttyS45 vcsa7 hda8 ram12tty0 tty28 tty47 tty9 ttyS27 ttyS46 video0 hw_random ram13tty1 tty29 tty48 ttyS0 ttyS28 ttyS47 zero as you see there is no cdrom or hdb in /dev directory. what should i do after that? This seems strangely empty. Are you using devfs or something similar? udev maybe? greets, Wim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
On Monday 03 January 2005 10:17, Necati DEMiR wrote: # dmesg|grep hdb ide_setup: hdb=ide-scsi ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA hdb: HL-DT-ST GCE-8400B, ATAPI CD/DVD-ROM drive It looks to me as though you are using udev (or devfs). When you use ide-scsi, the cdrom is no longer /dev/hdb, but something like /dev/sr0 (not sure). A bit late now, but when asked for dmesg, it would have been more helpful to give us it all, then we can get other clues. For instance - what version of the kernel are you using. 2.6 doesn't need (indeed shouldn't have) ide-scsi. You will need to load ide-cd though (put it in /etc/modules). -- Alan Chandler [EMAIL PROTECTED] First they ignore you, then they laugh at you, then they fight you, then you win. --Gandhi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
# dmesg|grep hdb ide_setup: hdb=ide-scsi ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA hdb: HL-DT-ST GCE-8400B, ATAPI CD/DVD-ROM drive # ls /dev/ MAKEDEVinitctl ram14tty10 tty3 tty49 ttyS1 ttyS29 ttyS48 adsp inputram15tty11 tty30 tty5 ttyS10 ttyS3 ttyS49 agpgartkmem ram2 tty12 tty31 tty50 ttyS11 ttyS30 ttyS5 audio kmsg ram3 tty13 tty32 tty51 ttyS12 ttyS31 ttyS50 consoleloop ram4 tty14 tty33 tty52 ttyS13 ttyS32 ttyS51 core mem ram5 tty15 tty34 tty53 ttyS14 ttyS33 ttyS52 dspmixerram6 tty16 tty35 tty54 ttyS15 ttyS34 ttyS53 fb0net ram7 tty17 tty36 tty55 ttyS16 ttyS35 ttyS6 fd null ram8 tty18 tty37 tty56 ttyS17 ttyS36 ttyS7 fd0port ram9 tty19 tty38 tty57 ttyS18 ttyS37 ttyS8 full ppp random tty2 tty39 tty58 ttyS19 ttyS38 ttyS9 hdaprinter rtc tty20 tty4 tty59 ttyS2 ttyS39 urandom hda1 psauxshm tty21 tty40 tty6 ttyS20 ttyS4 vbi0 hda2 ptmx snd tty22 tty41 tty60 ttyS21 ttyS40 vcs hda3 pts sndstat tty23 tty42 tty61 ttyS22 ttyS41 vcs1 hda4 ram0 stderr tty24 tty43 tty62 ttyS23 ttyS42 vcs7 hda5 ram1 stdintty25 tty44 tty63 ttyS24 ttyS43 vcsa hda6 ram10stdout tty26 tty45 tty7 ttyS25 ttyS44 vcsa1 hda7 ram11tty tty27 tty46 tty8 ttyS26 ttyS45 vcsa7 hda8 ram12tty0 tty28 tty47 tty9 ttyS27 ttyS46 video0 hw_random ram13tty1 tty29 tty48 ttyS0 ttyS28 ttyS47 zero as you see there is no cdrom or hdb in /dev directory. what should i do after that? for some reason the device is not created. Hm, do you have udev installed? yes i have udev installed. what can be the reason of not creating devices? Why do you set hdb=ide-scsi (see above). Is it scsi? it is a cd-writer. i think debian knows a cd-writer is connected and loads the module ide-scsi, but it doesn't create hdb,cdrom or sr* under /dev/ directory. it is not problem for me to use my cd-writer as a cd-rom. i wanna use it as a cdrom. After solving this problem, i will try to use it as a cd-writer, but my first aim is, to mount my cd-rom. OK? :) -- Necati DEMiR [EMAIL PROTECTED] http://demir.web.tr My Public Key = http://demir.web.tr/ndemir.asc - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
On Mon, 03 Jan 2005 21:38:34 +0200, Necati DEMiR [EMAIL PROTECTED] wrote: [...] it is a cd-writer. i think debian knows a cd-writer is connected and loads the module ide-scsi, but it doesn't create hdb,cdrom or sr* under /dev/ directory. it is not problem for me to use my cd-writer as a cd-rom. i wanna use it as a cdrom. After solving this problem, i will try to use it as a cd-writer, but my first aim is, to mount my cd-rom. OK? :) First of all don't use SCSI emulation for your CD-ROM, then check if in your /etc/udev/rules.d there's a symlink to ../cd-aliases.rules, if not present create it, then restart udev... Andrea -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
Andrea Vettorello wrote: On Mon, 03 Jan 2005 21:38:34 +0200, Necati DEMiR [EMAIL PROTECTED] wrote: [...] it is a cd-writer. i think debian knows a cd-writer is connected and loads the module ide-scsi, but it doesn't create hdb,cdrom or sr* under /dev/ directory. it is not problem for me to use my cd-writer as a cd-rom. i wanna use it as a cdrom. After solving this problem, i will try to use it as a cd-writer, but my first aim is, to mount my cd-rom. OK? :) First of all don't use SCSI emulation for your CD-ROM, then check if in your /etc/udev/rules.d there's a symlink to ../cd-aliases.rules, if not present create it, then restart udev... i did the followings; # ls -al /etc/udev/rules.d/ total 8 drwxr-xr-x 2 root root 4096 Dec 26 18:37 . drwxr-xr-x 5 root root 4096 Jan 3 19:46 .. lrwxrwxrwx 1 root root 19 Dec 26 18:37 cd-aliases.rules - ../cd-aliases.rules lrwxrwxrwx 1 root root 13 Dec 26 18:37 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 12 Dec 26 18:27 z_hal-plugdev.rules - ../hal.rules # cd /etc/init.d # ./udev restart Recreating device nodes...done. # ls /dev/ MAKEDEV hda7 ram0shm tty19 tty35 tty51 ttyS1 ttyS26 ttyS42 vbi0 adsp hda8 ram1snd tty2 tty36 tty52 ttyS10 ttyS27 ttyS43 vcs agpgart hw_random ram10 sndstat tty20 tty37 tty53 ttyS11 ttyS28 ttyS44 vcs1 audioinitctlram11 stderr tty21 tty38 tty54 ttyS12 ttyS29 ttyS45 vcs7 console input ram12 stdintty22 tty39 tty55 ttyS13 ttyS3 ttyS46 vcsa core kmem ram13 stdout tty23 tty4 tty56 ttyS14 ttyS30 ttyS47 vcsa1 dsp kmsg ram14 tty tty24 tty40 tty57 ttyS15 ttyS31 ttyS48 vcsa7 fb0 loop ram15 tty0 tty25 tty41 tty58 ttyS16 ttyS32 ttyS49 video0 fd memram2tty1 tty26 tty42 tty59 ttyS17 ttyS33 ttyS5zero fd0 mixer ram3tty10tty27 tty43 tty6 ttyS18 ttyS34 ttyS50 full netram4tty11tty28 tty44 tty60 ttyS19 ttyS35 ttyS51 hda null ram5tty12tty29 tty45 tty61 ttyS2 ttyS36 ttyS52 hda1 port ram6tty13tty3 tty46 tty62 ttyS20 ttyS37 ttyS53 hda2 pppram7tty14tty30 tty47 tty63 ttyS21 ttyS38 ttyS6 hda3 printerram8tty15tty31 tty48 tty7 ttyS22 ttyS39 ttyS7 hda4 psaux ram9tty16tty32 tty49 tty8 ttyS23 ttyS4 ttyS8 hda5 ptmx random tty17tty33 tty5 tty9 ttyS24 ttyS40 ttyS9 hda6 ptsrtc tty18tty34 tty50 ttyS0 ttyS25 ttyS41 urandom as you see there is no hdb or cdrom still! -- Necati DEMiR [EMAIL PROTECTED] http://demir.web.tr My Public Key = http://demir.web.tr/ndemir.asc - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
On Tue, 04 Jan 2005 02:45:23 +0200, Necati DEMiR [EMAIL PROTECTED] wrote: Andrea Vettorello wrote: On Mon, 03 Jan 2005 21:38:34 +0200, Necati DEMiR [EMAIL PROTECTED] wrote: [...] it is a cd-writer. i think debian knows a cd-writer is connected and loads the module ide-scsi, but it doesn't create hdb,cdrom or sr* under /dev/ directory. it is not problem for me to use my cd-writer as a cd-rom. i wanna use it as a cdrom. After solving this problem, i will try to use it as a cd-writer, but my first aim is, to mount my cd-rom. OK? :) First of all don't use SCSI emulation for your CD-ROM, then check if in your /etc/udev/rules.d there's a symlink to ../cd-aliases.rules, if not present create it, then restart udev... i did the followings; # ls -al /etc/udev/rules.d/ total 8 drwxr-xr-x 2 root root 4096 Dec 26 18:37 . drwxr-xr-x 5 root root 4096 Jan 3 19:46 .. lrwxrwxrwx 1 root root 19 Dec 26 18:37 cd-aliases.rules - ../cd-aliases.rules lrwxrwxrwx 1 root root 13 Dec 26 18:37 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 12 Dec 26 18:27 z_hal-plugdev.rules - ../hal.rules # cd /etc/init.d # ./udev restart Recreating device nodes...done. # ls /dev/ MAKEDEV hda7 ram0shm tty19 tty35 tty51 ttyS1 [...] ttyS41 urandom as you see there is no hdb or cdrom still! Have you checked if you have at least ide-cd module loaded? Modprobe it if not. And put a line in your /etc/modules too if not present. The ide-cd depends on ide-core and cdrom, so modprobing it should load them too... Andrea -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
mknod, /dev/hdb, /dev/cdrom problem
Hi, i wanted to mount my cdrom, but i saw that there is no hdb or cdrom in /dev directory, and i decided to create them by using mknod. and i did the followings; #mknod -m 0660 /dev/hdb b 3 64 #ln -s /dev/hdb /dev/cdrom every thing is ok up to now. then i tried; #mount /dev/cdrom /mnt/cdrom/ but it gave error like this; mount: /dev/cdrom is not a valid block device How can i solve this problem? Thanks! -- Necati DEMiR [EMAIL PROTECTED] http://demir.web.tr My Public Key = http://demir.web.tr/ndemir.asc - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
On Sun, Jan 02, 2005 at 11:29:25PM +0200, Necati DEMiR wrote: Can't read your message -- it's in html. Turn that off and send plain text so we can all read it. Ollie -- |---| | Ollie Acheson | | Morristown, NJ| |---| -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
Hi, i wanted to mount my cdrom, but i saw that there is no hdb or cdrom in /dev directory, and i decided to create them by using mknod. and i did the followings; #mknod -m 0660 /dev/hdb b 3 64 #ln -s /dev/hdb /dev/cdrom every thing is ok up to now. then i tried; #mount /dev/cdrom /mnt/cdrom/ but it gave error like this; mount: /dev/cdrom is not a valid block device How can i solve this problem? Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
On Sun, 2005-01-02 at 23:39 +0200, Necati DEMiR wrote: Hi, i wanted to mount my cdrom, but i saw that there is no hdb or cdrom in /dev directory, and i decided to create them by using mknod. and i did the followings; #mknod -m 0660 /dev/hdb b 3 64 #ln -s /dev/hdb /dev/cdrom every thing is ok up to now. then i tried; #mount /dev/cdrom /mnt/cdrom/ but it gave error like this; mount: /dev/cdrom is not a valid block device How can i solve this problem? Thanks! send us the output of dmesg. cheers, Hp. -- Hanspeter Kunz Artificial Intelligence Laboratory Ph.D. Student Department of Information Technology Email: [EMAIL PROTECTED] University of Zurich Tel: +41.(0)44.63-54306 Andreasstrasse 15, Office 2.12 http://ailab.ch/people/hkunzCH-8050 Zurich, Switzerland Spamtraps: [EMAIL PROTECTED] [EMAIL PROTECTED] --- If at first you don't succeed, destroy all evidence that you tried. signature.asc Description: This is a digitally signed message part
Re: mknod, /dev/hdb, /dev/cdrom problem
Ollie Acheson([EMAIL PROTECTED]) is reported to have said: On Sun, Jan 02, 2005 at 11:29:25PM +0200, Necati DEMiR wrote: Can't read your message -- it's in html. Turn that off and send plain text so we can all read it. Ollie Add this to your .mutt_mailcap and you will be able to read his mail. __ # This version would convert the text/html to text/plain text/html; lynx -force_html -dump %s; copiousoutput _ but I hope he, and others, learn to 'not use html on this list. WT -- Real computer scientists only write specs for languages that might run on future hardware. Nobody trusts them to write specs for anything homo sapiens will ever be able to fit on a single planet. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mknod, /dev/hdb, /dev/cdrom problem
On Sun, Jan 02, 2005 at 11:39:04PM +0200, Necati DEMiR wrote: Hi, i wanted to mount my cdrom, but i saw that there is no hdb or cdrom in /dev directory, and i decided to create them by using mknod. and i did the followings; #mknod -m 0660 /dev/hdb b 3 64 #ln -s /dev/hdb /dev/cdrom every thing is ok up to now. then i tried; #mount /dev/cdrom /mnt/cdrom/ but it gave error like this; mount: /dev/cdrom is not a valid block device How can i solve this problem? Thanks! Try giving the file system type in your mount command: mount -t iso9660 /dev/hdb /mnt/cdrom Also using a symbolic link is unnecessary in this since once you get it working you will surely make an entry in /etc/fstab. Symbolic links, in this, are for making it easier to maintain after a few months when you have forgotten what you did to get it working. HTH -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrom-Problem
* Michael Ott [EMAIL PROTECTED] wrote: Hallo Norbert! Du auch hier! Offenbar. Und warum meldet mein CD-ROM-Laufwerk read-error, wenn ich eine Audio-CD einlegen? Ohne _exakte_ Fehlermeldung und mehr Details kann man dir nicht helfen. Das solltest du inzwischen wissen. Ich weiß! Also mein Laptop besitzt ein DVD-CDRW-Laufwerk. Er spielt Daten-CDs ohne Probleme, nur meine Musik-CDs will er nicht! Und wie versuchst du die Musik CDs abzuspielen? -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
cdrom-Problem
Hallo Norbert! Du auch hier! Und warum meldet mein CD-ROM-Laufwerk read-error, wenn ich eine Audio-CD einlegen? Ohne _exakte_ Fehlermeldung und mehr Details kann man dir nicht helfen. Das solltest du inzwischen wissen. Ich weiß! Also mein Laptop besitzt ein DVD-CDRW-Laufwerk. Er spielt Daten-CDs ohne Probleme, nur meine Musik-CDs will er nicht! Laufwerk wird beim booten als ide-scsi geladen sudo less -f /dev/scd0 gibt read-error zurück und bei /dev/cdrom und /dev/sr0 auch. Eintrag in messages: kernel: I/O error: dev 0b:00, sector 0 -- CU Michael .--. |o_o | --||_/ | /-\// \ \ | Michael Ott, Glockenhofstr. 29a, 90478 Nuernberg | (| | ) | e-mail: [EMAIL PROTECTED], Tel. +49 9 11 41 88 576 | /'\_ _/`\ \-/ \___)=(___/ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: /dev/cdrom problem...
Thanks Daniel, I am using the standard (unmodified) 2.2.19-12 kernel from the Debian distribution. The devfsd package is not installed. I checked out the website, but I am not sure if this would solve my problem. I am not mounting this manually, or I would do it the way I want it. I will check /etc/init.d... I appreciate the info, Daniel. JP On Sunday 23 December 2001 12:42 am, Daniel Freedman wrote: Hi All, I have a problem with my device configuration. I have a CD player and a CD writer (/dev/hdc and /dev/hdd, r espectively), and whenever I boot up it links up the writer on /dev/cdrom1, and the reader on /dev/cdrom2 (/dev/cdrom is, correctly a link to /dev/cdrom1). I can change the links, but they go back to the other configuration after a reboot. Of course, this screws up cd players, rippers, writers, etc. Any info on how to configure this correctly? JP, You don't give much information, but maybe you're using a kernel with devfs mounted automatically (or you, or one of your /etc/init.d scripts, are mounting it manually). Since devfs is a virtual file system (I like to think of its analogy to the /proc fs), any changes made to it are not preserved across reboots (or actually across unmounting and remounting it). If my 'devfs' guess is correct, you can find more information about it at: http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html Hope this helps, Daniel Content-Type: /; name=Attachment: 1 Content-Transfer-Encoding: 7bit Content-Description:
Re: /dev/cdrom problem...
To reply to my own post - I think the problem is in /etc/init.d/iscover: # Link /dev/cdromX to all detected CD drives, and create mount points: CDNUM=1 for CDROM in `discover --device cdrom` do if [ ! -e $CDROM ] then echo -n discover reports that $CDROM is the CD-ROM device, but it echo does not exist. Not updating /dev/cdrom$CDNUM. elif [ ! -b $CDROM ] then echo -n discover reports that $CDROM is the CD-ROM device, but it echo is not a block device. Not updating /dev/cdrom$CDNUM. elif [ -e /dev/cdrom$CDNUM -a ! -L /dev/cdrom$CDNUM ] then echo -n /dev/cdrom$CDNUM exists and is not a symlink. Not updating echo /dev/cdrom$CDNUM. CDNUM=`expr $CDNUM + 1` else ln -fs $CDROM /dev/cdrom$CDNUM mkdir /cdrom$CDNUM CDNUM=`expr $CDNUM + 1` fi done # Link /dev/cdrom to the appropriate device: if [ -e /dev/cdrom1 ] then if [ -L /dev/cdrom -o ! -e /dev/cdrom ] then ln -fs /dev/cdrom1 /dev/cdrom else echo /dev/cdrom exists and is not a symlink. Not updating /dev/cdrom. fi else echo No CD-ROM drives found. fi this script is calling /sbin/discover, which returns a list of path names to devices specified on the command line (in this case --device cdrom), but the list is coming out in reverse order, i.e. hdd before hdc. Anyone else have this problem? Is this a bug? Cheers, JP On Sunday 23 December 2001 01:30 am, JP Glutting wrote: Rese nt-Message-ID: [EMAIL PROTECTED] Resent-From: debian-user@lists.debian.org X-Mailing-List: debian-user@lists.debian.org archive/latest/187577 X-Loop: debian-user@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] Thanks Daniel, I am using the standard (unmodified) 2.2.19-12 kernel from the Debian distribution. The devfsd package is not installed. I checked out the website, but I am not sure if this would solve my problem. I am not mounting this manually, or I would do it the way I want it. I will check /etc/init.d...
/dev/cdrom problem...
Hi All, I have a problem with my device configuration. I have a CD player and a CD writer (/dev/hdc and /dev/hdd, respectively), and whenever I boot up it links up the writer on /dev/cdrom1, and the reader on /dev/cdrom2 (/dev/cdrom is, correctly a link to /dev/cdrom1). I can change the links, but they go back to the other configuration after a reboot. Of course, this screws up cd players, rippers, writers, etc. Any info on how to configure this correctly? Thanks, JP
Re: /dev/cdrom problem...
On Sun, Dec 23, 2001, JP Glutting wrote: Hi All, I have a problem with my device configuration. I have a CD player and a CD writer (/dev/hdc and /dev/hdd, respectively), and whenever I boot up it links up the writer on /dev/cdrom1, and the reader on /dev/cdrom2 (/dev/cdrom is, correctly a link to /dev/cdrom1). I can change the links, but they go back to the other configuration after a reboot. Of course, this screws up cd players, rippers, writers, etc. Any info on how to configure this correctly? JP, You don't give much information, but maybe you're using a kernel with devfs mounted automatically (or you, or one of your /etc/init.d scripts, are mounting it manually). Since devfs is a virtual file system (I like to think of its analogy to the /proc fs), any changes made to it are not preserved across reboots (or actually across unmounting and remounting it). If my 'devfs' guess is correct, you can find more information about it at: http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html Hope this helps, Daniel Thanks, JP -- Daniel A. Freedman Laboratory for Atomic and Solid State Physics Department of Physics Cornell University
CDROM PROBLEM
I HAVE A CDROM ATAPI 50X WHICH ACCORDING THE THE CONTROL PANEL SYSTEM AND DEVICE MANAGER IS WORKING PROPERLY. HOWEVER, IT IS NOT ACCESSIBLE THANKS TO HAVING RECEIVED A CD FROM WINSTRUCT.COM CALLED "LEARNING WINDOWS: GETTING STARTED" WHICH STALLED IT AND HAD TO REBOOT THE COMPUTER. AFTER FINALLY CONTACTING SOMEONE WHO USED TO DEAL WITH THE COMPANY KESTAL COMMUNICATION WHO DISTRIBUTES THE CD I WAS ADVISED TO REMOVE THE CDROM AND REBOOT AND LET THE COMPUTER REFIND IT. THIS DID NOT WORK. DO YOU HAVE ANY IDEA WHO I CAN GET IT TO WORK AGAIN.
Re: CDROM PROBLEM
High, Please, stop shouting. We can hear you. On Thu, 9 Aug 2001 [EMAIL PROTECTED] wrote: I HAVE A CDROM ATAPI 50X WHICH ACCORDING THE THE CONTROL PANEL SYSTEM AND DEVICE MANAGER IS WORKING PROPERLY. HOWEVER, IT IS NOT ACCESSIBLE THANKS TO HAVING RECEIVED A CD FROM WINSTRUCT.COM CALLED LEARNING WINDOWS: GETTING STARTED WHICH STALLED IT AND HAD TO REBOOT THE COMPUTER. Why would you want to learn windoze? The user stuff is pretty trivial. The non-user stuff is very untrivial because M$ does not like us to take a look on their code. AFTER FINALLY CONTACTING SOMEONE WHO USED TO DEAL WITH THE COMPANY KESTAL COMMUNICATION WHO DISTRIBUTES THE CD I WAS ADVISED TO REMOVE THE CDROM AND REBOOT AND LET THE COMPUTER REFIND IT. THIS DID NOT WORK. DO YOU HAVE ANY IDEA WHO I CAN GET IT TO WORK AGAIN. Not the cdrom, the cdrom drive. Go to the control panel, select your Atapi drive and remove it. Then reboot your computer and wait forever, perhaps windoze will find the drive right away, else you have to run the hardware wizard. BTW: are you aware that this is a Linux list? Or did they give you the impression that windoze was the only OS available? For problems bith M$-stuff, you should contact [EMAIL PROTECTED] Then you will find out why there is Linux too. Greetz, Sebastiaan
Re: CDROM PROBLEM
#! On Thu, Aug 09, 2001, [EMAIL PROTECTED] wrote: I HAVE A CDROM ATAPI 50X WHICH ACCORDING THE THE CONTROL PANEL SYSTEM AND DEVICE MANAGER IS WORKING PROPERLY. HOWEVER, IT IS NOT ACCESSIBLE THANKS TO HAVING RECEIVED A CD FROM WINSTRUCT.COM CALLED LEARNING WINDOWS: GETTING STARTED WHICH STALLED This is a common problem. Your computer is afraid that you are about to make a dreadful mistake. Insert the Learning Linux: Getting Started CD and it should improve. Tip: to the left of your keyboard, you can see a larg-ish key marked CapsLock. If you press it, you can get rid of that ANNOYING ALL CAPS TEXT. I know you were probably thinking of purchasing a new keyboard to deal with this but there's no need. Just press that lil button and the problem goes away. Hope this helped! -- Patrick sig free and joyful Kirk GSM: +44 7876 560 646 ICQ: 42219699
Re: CDROM PROBLEM
Sebastiaan wrote: High, Please, stop shouting. We can hear you. On Thu, 9 Aug 2001 [EMAIL PROTECTED] wrote: I HAVE A CDROM ATAPI 50X WHICH ACCORDING THE THE CONTROL PANEL SYSTEM AND DEVICE MANAGER IS WORKING PROPERLY. HOWEVER, IT IS NOT ACCESSIBLE THANKS TO HAVING RECEIVED A CD FROM WINSTRUCT.COM CALLED LEARNING WINDOWS: GETTING STARTED WHICH STALLED IT AND HAD TO REBOOT THE COMPUTER. Why would you want to learn windoze? The user stuff is pretty trivial. The non-user stuff is very untrivial because M$ does not like us to take a look on their code. AFTER FINALLY CONTACTING SOMEONE WHO USED TO DEAL WITH THE COMPANY KESTAL COMMUNICATION WHO DISTRIBUTES THE CD I WAS ADVISED TO REMOVE THE CDROM AND REBOOT AND LET THE COMPUTER REFIND IT. THIS DID NOT WORK. DO YOU HAVE ANY IDEA WHO I CAN GET IT TO WORK AGAIN. Not the cdrom, the cdrom drive. Go to the control panel, select your Atapi drive and remove it. Then reboot your computer and wait forever, perhaps windoze will find the drive right away, else you have to run the hardware wizard. BTW: are you aware that this is a Linux list? Or did they give you the impression that windoze was the only OS available? For problems bith M$-stuff, you should contact [EMAIL PROTECTED] Then you will find out why there is Linux too. Greetz, Sebastiaan Ah now I understand what he is talkong about. He seems to have a problem with his caps lock key as well. Frank
Re: Newbie Slink install CDROM problem on old computer
If you are like me and your CDROM is hanging off a soundcard or add-in card, then hda-hdd isn't enough. If this is your case, you need to add a mount point. I had that problem with my /dev/hde. If this is your case and you need to add a mount point, log in as root: cd /dev ls -l hdh (to see if you already have one) if not ./MAKEDEV -n -v hdh (-v is verbose, -n is simulate) Umm, I'm not trying to be rude, but the above might be confusing. /dev/hd* is not a mount point but a device. The mount point can be any directory. For a cdrom, it's often /mnt/cdrom/ or /cdrom/. You mount a device on a mount point: mount -t iso9660 /dev/hdh /mnt/cdrom ^^^ ^^^^^^ fs-type device mount-point -- Pat Mahoney [EMAIL PROTECTED] Hobbes: Do you have an idea for your story yet? Calvin: No, I'm waiting for inspiration. You can't just turn on creativity like a faucet. You have to be in the right mood. Hobbes: What mood is that? Calvin: Last-minute panic. -- From Calvin and Hobbes by Bill Watterson
Re: Newbie Slink install CDROM problem on old computer
On Wed, May 10, 2000 at 08:07:26PM -0400, Andy L. Krietemeyer wrote: I have run dmesg and it reports my CDROM has been probed as hdh. Answering hdh or /dev/cdrom or dev/hdh does nothing to help. Hi, If the CDROM is plugged in the primary or secondary IDE controller on the motherboard then it would normally be hda-hdd. Since this is what most people do with modern gear, the default devices are only hda-hdd. If you are like me and your CDROM is hanging off a soundcard or add-in card, then hda-hdd isn't enough. If this is your case, you need to add a mount point. I had that problem with my /dev/hde. If this is your case and you need to add a mount point, log in as root: cd /dev ls -l hdh (to see if you already have one) if not ./MAKEDEV -n -v hdh (-v is verbose, -n is simulate) The above is a dry run; you haven't actually done anything. if the dry run looks good, then ./MAKEDEV -v hdh (for real this time, no -n) Even if this isn't your problem, I don't think it will break anything. I have mount points for /dev/hdc and hdd, and I don't have those devices, so I wouldn't think it would matter. Then you might need to make a link to cdrom: ln -s hde cdrom Good luck! -- Thank you, Joe Bouchard Powered by Debian GNU/Linux
Re: Newbie Slink install CDROM problem on old computer
Andy L. Krietemeyer wrote: Hello: I have successfully installed and configured the base system of slink (2.1r4) on a 486 machine with 24 meg. The install program recognized and installed debian from the (Creative Labs) ATAPI CDROM. When I get to dselect to install packages, whether from a profile, selected tasks, or individual packages, the program does recognize the CDROM. I have tried to mount the CDROM, but the mount command does not work and reports the device is not recognized. You certainly should get it mounted first. What happens when you try something like: mkdir /mnt/cdrom mount -t iso9660 /dev/hdh /mnt/cdrom You could try /dev/hdb, /dev/hdc, etc, as has been suggested...
Newbie Slink install CDROM problem on old computer
Hello: I have successfully installed and configured the base system of slink (2.1r4) on a 486 machine with 24 meg. The install program recognized and installed debian from the (Creative Labs) ATAPI CDROM. When I get to dselect to install packages, whether from a profile, selected tasks, or individual packages, the program does recognize the CDROM. I have tried to mount the CDROM, but the mount command does not work and reports the device is not recognized. This continues to occur even after I have manually added the CDROM to fstab (I don't know enough to know whether that should help or not). Dselect also asks for identification of the block device [ ]. Nothing I type for an answer does anything except cause the program to repeat the question and lock me in a loop I can't escape from. I have run dmesg and it reports my CDROM has been probed as hdh. Answering hdh or /dev/cdrom or dev/hdh does nothing to help. Does anyone have any ideas of what I'm doing wrong or any suggestions to help. Thanks and regards, Andy
Re: Newbie Slink install CDROM problem on old computer
On Wed, May 10, 2000 at 08:07:26PM -0400, Andy L. Krietemeyer wrote: Hello: I have successfully installed and configured the base system of slink (2.1r4) on a 486 machine with 24 meg. The install program recognized and installed debian from the (Creative Labs) ATAPI CDROM. When I get to dselect to install packages, whether from a profile, selected tasks, or individual packages, the program does recognize the CDROM. I have tried to mount the CDROM, but the mount command does not work and reports the device is not recognized. This continues to occur even after I have manually added the CDROM to fstab (I don't know enough to know whether that should help or not). Dselect also asks for identification of the block device [ ]. Nothing I type for an answer does anything except cause the program to repeat the question and lock me in a loop I can't escape from. I have run dmesg and it reports my CDROM has been probed as hdh. Answering hdh or /dev/cdrom or dev/hdh does nothing to help. Try /dev/hdb or /dev/hdc or /dev/hdd John Does anyone have any ideas of what I'm doing wrong or any suggestions to help. Thanks and regards, Andy -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Using Linux
Re: How's the CDROM problem, solved?
Hi, Yes, I read that post. You need to determine what the IRQ and IO address of your board is currently. Then tell linux about it. By looking at the current switch settings on your board, use the tables in the manual to determine what IRQ and IO address the board is set for. Don't trust anything that says default until you have verified it. The modprobe command error indicates something is wrong with the combination of HW/SW. The mount command will never work until you get this right. You can always view the system boot text by executing the dmesg command. You will want to look at the IRQs used by other devices and may have to set your board differently, so it does not use one of those. I would post the entire dmesg output to the list if you can't figure out what the error messages are from the normal messages. I am not sure where to specify these addresses to linux, so you may want to post that specific question to the list once you do determine what your current addresses are, and it doesn't look like any other devices are using the IRQ. John __ Get Your Private, Free Email at http://www.hotmail.com
Re: CDROM problem, solved? Yes, I think
Hi, The dselect program will mount the CDROM for you. I assume you wish to get the rest of the debian SW on your machine and that is why you wish to use the CDROM at the moment. You can brave dselect now, chose the Multi-CD option in ACCESS. When it asks you for the device, specify /dev/mcd for it. It will ask you a few questions about directories, but since you have the CD, you should be able to hit RETURN for everything. Then refer to my earlier post to brave dselect, but I REALLY recommend getting more info on deselect if you get too frustrated. If you wish to see if the CDROM works first, execute that mount command that was posted, or you may be able to get away with mount /dev/mcd /mnt(mounts the CD as /mnt) ls /mnt(lists the files in the top level directory) df (shows you what is mounted) umount /mnt(unmounts the /mnt which is your CDROM now) You may have to use mount -t iso9660 /dev/mcd /mnt ro or whatever was contained the other post. I'm sure you wrote it down or have it. John From: jh [EMAIL PROTECTED] To: John Miskinis [EMAIL PROTECTED] Subject: CDROM problem, solved? Yes, I think Date: Sun, 17 Oct 1999 00:36:05 -0600 I pulled the interface card and the first thing that I noticed is that nothing was set to default. I thought I would restore the jumper settings and the switches to default and try it. I went into modconf and installed the module to the kernel. It worked! It succedded. Now how do I mount it? I am very grateful for your coaching. The part about not trusting that something is set to default did it. Jeff __ Get Your Private, Free Email at http://www.hotmail.com
dmesg output for PCMCIA CDROM problem...
Hi, I have included the dmesg output, showing exactly what is happening when the CDROM times out during boot. Since this worked once, I am hoping that something stands out, and someonce can advise me on how to increase the timeout. Again this is a H45 QuickCD. When it did work once, it worked on IR3 as /dev/hdc as listed in the output deom the failed attempts. Any advice would be appreciated, John __ Get Your Private, Free Email at http://www.hotmail.com
dmesg output for PCMCIA CDROM problem...
Hi, I have included the dmesg output, showing exactly what is happening when the CDROM times out during boot. Since this worked once, I am hoping that something stands out, and someonce can advise me on how to increase the timeout. Again this is a H45 QuickCD. When it did work once, it worked on IR3 as /dev/hdc as listed in the output deom the failed attempts. Any advice would be appreciated, John -- begin dmesg output - Memory: sized by int13 088h Console: 16 point font, 400 scans Console: colour VGA+ 80x25, 1 virtual console (max 63) pcibios_init : BIOS32 Service Directory structure at 0x000fd870 pcibios_init : BIOS32 Service Directory entry at 0xfd880 pcibios_init : PCI BIOS revision 2.10 entry at 0xfd8c0 Probing PCI hardware. Calibrating delay loop.. ok - 53.04 BogoMIPS Memory: 22136k/24576k available (1136k kernel code, 384k reserved, 920k data) Swansea University Computer Society NET3.035 for Linux 2.0 NET3: Unix domain sockets 0.13 for Linux NET3.035. Swansea University Computer Society TCP/IP for NET3.034 IP Protocols: IGMP, ICMP, UDP, TCP VFS: Diskquotas version dquot_5.6.0 initialized Checking 386/387 coupling... Ok, fpu using exception 16 error reporting. Checking 'hlt' instruction... Ok. Intel Pentium with F0 0F bug - workaround enabled. alias mapping IDT readonly ... ... done Linux version 2.0.36 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Sun Feb 21 15:55:27 EST 1999 Starting kswapd v 1.4.2.2 Real Time Clock Driver v1.09 tpqic02: Runtime config, $Revision: 0.4.1.5 $, $Date: 1994/10/29 02:46:13 $ tpqic02: DMA buffers: 20 blocks, at address 0x282600 (0x28254c) Ramdisk driver initialized : 16 ramdisks of 4096K size loop: registered device at major 7 hda: IBM-DTNA-22110, 2016MB w/96kB Cache, CHS=1024/64/63 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 md driver 0.36.3 MAX_MD_DEV=4, MAX_REAL=8 Failed initialization of WD-7000 SCSI card! scsi : 0 hosts. scsi : detected total. Partition check: hda: hda1 hda2 hda5 hda6 VFS: Mounted root (ext2 filesystem) readonly. Adding Swap: 50364k swap-space (priority -1) PS/2 auxiliary pointing device detected -- driver installed. lp0 at 0x03bc, (polling) Serial driver version 4.13 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 16550A tty01 at 0x02f8 (irq = 3) is a 16550A Linux PCMCIA Card Services 3.0.5 kernel build: 2.0.36 unknown options: [pci] [cardbus] Intel PCIC probe: Cirrus PD6729 PCI at port 0x3e0 ofs 0x00, 2 sockets host opts [0]: [ring] [1/6/8] [1/20/8] host opts [1]: [ring] [1/6/8] [1/20/8] ISA irqs (default) = 3,4,5,7,9,10,11,12 status change on irq 11 cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x268-0x26f 0x330-0x337 0x388-0x38f 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: clean. cs: memory probe 0x0d-0x0d: clean. hdc: no response (status = 0x80), resetting drive ide_cs: ide_register() at 0x170 0x376, irq 3 failed __ Get Your Private, Free Email at http://www.hotmail.com
Re: sbpcd CDROM Problem! Need Help!
[This message has also been posted.] On 27 Aug 99 17:17:56 GMT Tam Ma [EMAIL PROTECTED] wrote: I think you guys should know these information; When I install the module, it gives me this message sbpcd-0 [11]:Drive 0(ID=0); CR-563 (0.81) at 0x340 (type 0) and then it tells me to do something with the sbpcd.h file... I used to use sbpcd. It's just telling you to recompile the kernel (or spbcd module) so that it knows to look at 0x340, instead of having to scan. The module should work fine up to then, but there will be time-wasting scanning every time you load it. When I look the /dev directory, I see cdrom as a link to sbpcd and I also see a bpcd(don't what this is ). I wonder if bpcd could be a Backpack CD. Backpack makes parallel-port CD-ROM units. In any case, use modprobe to find out if spbcd is loaded. If it is, don't fool around with configuration files, just type mount -t iso9660 /dev/cdrom /mnt -- Carl Fink [EMAIL PROTECTED] This fool wishes to reverse the entire science of astronomy. -Martin Luther on Copernicus' theory that the Earth orbits the sun
sbpcd CDROM Problem! Need Help!
Hi everyone, Ok, here is my problem. I just install slink yesterday using the floppies method because I can't boot from my Matsushita/Panasonic CR-563 CDROM. So I install the base system using the floppy set and everything went great. I got the base system installed, YES Anyway, the problem lies when I try to mount my CDROM and here is what I did: First, I added a line in my /etc/fstab file. The line is /dev/sbpcd /cdrom iso9660 noauto,ro,user and then I try to mount it like this mount /cdrom but it gives a this message special device /dev/sbpcd is not found (something like this) I don't know what's wrong, so I modify my /etc/fstab file again using this line this time /dev/sbpcd0 /cdrom iso9660 noauto,ro,user but it still gives me the same message. I couldn't figure out what's wrong so I uses modconf to remove the sbpcd driver that I've install and then reinstall it, and still it doesn't work. It gives me the same message when I try to mount it. I think you guys should know these information; When I install the module, it gives me this message sbpcd-0 [11]:Drive 0(ID=0); CR-563 (0.81) at 0x340 (type 0) and then it tells me to do something with the sbpcd.h file...It also tell me to look up linus/documentation/cdrom/sbpcd to information but I couldn't find that directory on my base system so can anyone tell my where i can read it on-line?? When I look the /dev directory, I see cdrom as a link to sbpcd and I also see a bpcd(don't what this is ). That's all folks. If anyone can help, please do. I appreciate it. Thanks everyone. Tam Ma [EMAIL PROTECTED]
CDROM Problem: Bad transfer size
Debian Users: While installing Debian 2.1 on my new Linux box, I ran into cdrom reading problems in the dselect phase. I selected the applications I wanted, and dselect started. I began to notice the following messages: hdb: cdrom_real_intr: Bad transfer size 65534 This drive is not supported by this version of the driver end_request: I/O error, dev 03:40, sector 888148 hdb: status error: status = 0x58 hdb: drive not ready for command hdb: ATAPI reset complete These messages would repeat, perhaps 100s of times. Finally, the loading would stop with a fatal device error. Twice (out of perhaps 10 tries) all selected applications were loaded, but always with many Bad transfer size messages. I should note that I loaded a Win98 partition on the same box without incident using the standard MS ATAPI driver. The CDROM is a Creative Labs 36X device, and the PC is running an Abit board, with 400 Celeron, 128 Mb, and 10GB Western Dig HD. Any help appreciated. Norm Hummon
Re: CDROM problem
On Thu, 11 Mar 1999 16:27:45 -0600, you wrote: I thought the standard name for all cdrom devices was /dev/hdc check your /dev drirectory to see if you have a hdc device and I bet my bottom dollar that is your cdrom device the standard device for many scsi cdroms is /dev/scd0 for the first and ...scd1 etc. /dev/hdc is the 3rd ide disk Juice --have fun --harm none
Re: CDROM problem
I have been fighting a simular problem. I've traced mine down to the scsi driver probing for devices during boot-up. If the cdrom is found during bootup, the adding of the module will add sr. Most of the time, this new resc1440.bin doesn't find my cdrom. Once booted Press alt+F2 if you need a new terminal to work in cd /proc cat devices 11 sr should be one of the entries or you're not getting any closer. The software device sr is needed to talk to cdroms. The command `dmesg` ( or `dmsg` I keep forgetting) will show you the scroll that happened during bootup. If your cdrom is not listed then you have the same problem I do. I have an adaptec 2940u scsi pci controller. There is a chance that you don't have the same problem I have had but I have seen 2 other complaints in the last week plus, but no real answers yet. What I am looking for now: 1. an option to give the scsi driver during configuration to extend the timeout of waiting for devices to respond 2. a way to tell the kernel there is a drive it missed and to add it to its lists. Feel free to contact me if there is a chance we can compare notes. Juice --have fun --harm none On Thu, 11 Mar 1999 12:29:03 +0100, you wrote: hello, when I install the latest version of linux (debian) from a CDROM eveything works good until it begins with dselect. It ask me for the source and I tell it CDROM, after it ask me for the block device type and it is imposible to go ahead. I try some things like this: /dev/hdb but it say that the kernel do not support the iso9660 norm. I do not understand because it make the all instalation from the CDROM. If I execute a shell I can't mount the CDROM and it tell me the same thing about the iso norm even if I mount it with the next command: mount /dev/hdb -t iso9660 /cdrom Last year with the same computer I could install an older version of debian. Now I can't install the same version. The only thing that difers from before is that I have install a CDROM writer. I have a pentium 166MMX. Notes: - I can install the latest version of RED HAT and after I can mount perfectly the CDROM but I prefer to install the Debian distribution. - Somebody told me that probably the iso9660 file system is configured as a module but I couldn't do anything wiyh the insmod command. May be I don't do it well. Thanks a lot.
CDROM problem
hello, when I install the latest version of linux (debian) from a CDROM eveything works good until it begins with dselect. It ask me for the source and I tell it CDROM, after it ask me for the block device type and it is imposible to go ahead. I try some things like this: /dev/hdb but it say that the kernel do not support the iso9660 norm. I do not understand because it make the all instalation from the CDROM. If I execute a shell I can't mount the CDROM and it tell me the same thing about the iso norm even if I mount it with the next command: mount /dev/hdb -t iso9660 /cdrom Last year with the same computer I could install an older version of debian. Now I can't install the same version. The only thing that difers from before is that I have install a CDROM writer. I have a pentium 166MMX. Notes: - I can install the latest version of RED HAT and after I can mount perfectly the CDROM but I prefer to install the Debian distribution. - Somebody told me that probably the iso9660 file system is configured as a module but I couldn't do anything wiyh the insmod command. May be I don't do it well. Thanks a lot. begin:vcard n:Carbonnier;Jean-Georges tel;fax:965919551 tel;work:96 5919331 x-mozilla-html:FALSE url:http:\\www.dsp.umh.es org:Departamento de Salud Publica;Universidad Miguel Hernandez adr:;;Campus de San Juan, ctra de Valencia (km 87);San Juan ;Alicante;03550 ;Spain version:2.1 email;internet:[EMAIL PROTECTED] end:vcard
Re: CDROM problem
I thought the standard name for all cdrom devices was /dev/hdc check your /dev drirectory to see if you have a hdc device and I bet my bottom dollar that is your cdrom device Jean-Georges Carbonnier wrote: hello, when I install the latest version of linux (debian) from a CDROM eveything works good until it begins with dselect. It ask me for the source and I tell it CDROM, after it ask me for the block device type and it is imposible to go ahead. I try some things like this: /dev/hdb but it say that the kernel do not support the iso9660 norm. I do not understand because it make the all instalation from the CDROM. If I execute a shell I can't mount the CDROM and it tell me the same thing about the iso norm even if I mount it with the next command: mount /dev/hdb -t iso9660 /cdrom Last year with the same computer I could install an older version of debian. Now I can't install the same version. The only thing that difers from before is that I have install a CDROM writer. I have a pentium 166MMX. Notes: - I can install the latest version of RED HAT and after I can mount perfectly the CDROM but I prefer to install the Debian distribution. - Somebody told me that probably the iso9660 file system is configured as a module but I couldn't do anything wiyh the insmod command. May be I don't do it well. Thanks a lot.
ATAPI CDROM problem (NEC-260)
Hi everyone, I'm really green, so pardon me if this is in a FAQ, but I did search the archives for this problem to no avail. I have an NEC IDE/ATAPI CD-ROM. It says CDR-250 on the case, and the BIOS reports NEC ATAPI CDROM: 260 (or something similar to that). I'm having trouble getting it to be recognized by Debian Linux (Hamm release, version 2.0.2 on CD from Linux Systems Labs). Using a DOS boot floppy with the NEC driver and MSCDEX, I am able to read the CD, which convinces me that it is not a drive or cable problem. It is jumpered as a slave on the primary IDE controller (on the motherboard). Examining the dmesg output I found the following, which would seem to be the problem: ide: i82371 PIIX (Triton) on PCI bus 0 function 57 ide0: BM-DMA at 0xf000-0xf007 ide1: BM-DMA at 0xf008-0xf00f hda: SAMSUNG VG38404A (8.40GB), 8056MB w/490kB Cache, CHS=1027/255/63 hdb: NEC CD-ROM DRIVE:260, ATAPI cdrom or floppy?, assuming FLOPPY drive ide-floppy: Packet size is not 12 bytes long ide-floppy: hdb: not supported by this version of ide-floppy ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 [complete dmesg output after message] Apparently the OS is making an incorrect assumption about the identity of the device and then failing because of it. (Ever heard of an IDE floppy? I've certainly never seen one). Anyway, after booting, there is no /dev/hdb device to mount. I don't know what I can do about this. Surely there's some way to nudge Debian in the right direction? (I have installed the basic part of the OS from floppy disks, so it is possible to tinker with the configuration files). - As an alternative, I have a Creative Labs Infra-1800 CD-ROM which is a 12X with a gimmicky infra-red remote. I figured it would be better to leave that on the Windows machine. It's also an ATAPI IDE CD-ROM. I would expect it to have the same problem, but I'll probably try it if all else fails. -- Many thanks! Terry Hancock ** Complete DMESG Listing Follows ** Console: 16 point font, 400 scans Console: colour VGA+ 80x25, 1 virtual console (max 63) pcibios_init : BIOS32 Service Directory structure at 0x000fabc0 pcibios_init : BIOS32 Service Directory entry at 0xfb040 pcibios_init : PCI BIOS revision 2.10 entry at 0xfb070 Probing PCI hardware. Calibrating delay loop.. ok - 80.08 BogoMIPS Memory: 6020k/8192k available (1124k kernel code, 384k reserved, 664k data) This processor honours the WP bit even when in supervisor mode. Good. Swansea University Computer Society NET3.035 for Linux 2.0 NET3: Unix domain sockets 0.13 for Linux NET3.035. Swansea University Computer Society TCP/IP for NET3.034 IP Protocols: IGMP, ICMP, UDP, TCP VFS: Diskquotas version dquot_5.6.0 initialized Checking 386/387 coupling... Ok, fpu using exception 16 error reporting. Checking 'hlt' instruction... Ok. Linux version 2.0.34 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Thu Jul 9 10:57:48 EST 1998 Starting kswapd v 1.4.2.2 Real Time Clock Driver v1.09 tpqic02: Runtime config, $Revision: 0.4.1.5 $, $Date: 1994/10/29 02:46:13 $ tpqic02: DMA buffers: 20 blocks, at address 0x277800 (0x2777d8) Ramdisk driver initialized : 16 ramdisks of 4096K size loop: registered device at major 7 ide: i82371 PIIX (Triton) on PCI bus 0 function 57 ide0: BM-DMA at 0xf000-0xf007 ide1: BM-DMA at 0xf008-0xf00f hda: SAMSUNG VG38404A (8.40GB), 8056MB w/490kB Cache, CHS=1027/255/63 hdb: NEC CD-ROM DRIVE:260, ATAPI cdrom or floppy?, assuming FLOPPY drive ide-floppy: Packet size is not 12 bytes long ide-floppy: hdb: not supported by this version of ide-floppy ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 md driver 0.35 MAX_MD_DEV=4, MAX_REAL=8 Failed initialization of WD-7000 SCSI card! ppa: Version 1.42 ppa: Probing port 03bc ppa: Probing port 0378 ppa: SPP port present ppa: PS/2 bidirectional port present ppa: Probing port 0278 scsi : 0 hosts. scsi : detected total. Partition check: hda: hda1 hda2 hda5 hda6 hda7 hda8 hda9 hda10 VFS: Mounted root (ext2 filesystem) readonly. Adding Swap: 130748k swap-space (priority -1) Module inserted $Id: cdrom.c,v 0.8 1996/08/10 10:52:11 david Exp $ Serial driver version 4.13 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 16550A tty01 at 0x02f8 (irq = 3) is a 16550A tty03 at 0x02e8 (irq = 3) is a 16550A lp1 at 0x0378, (polling) VFS: Disk change detected on device 02:00
ATAPI CDROM problem (NEC-260)
Try linux /dev/hdb = cdrom at the lilo prompt. == Amateur Radio, when all else fails! http://www.qsl.net/wa2mze Debian Gnu Linux, Live Free or . _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: ATAPI CDROM problem (NEC-260)
At 12:04 AM 1/19/1999 -0800, Terry Hancock wrote: Apparently the OS is making an incorrect assumption about the identity of the device and then failing because of it. (Ever heard of an IDE floppy? I've certainly never seen one). Anyway, after booting, there is no /dev/hdb device to mount. Kenneth Sharf hopefully provided the solution (as I have none), but I did want to say that I *think* (and don't quote me on this) that an internal zip drive is considered an IDE floppy.
RE: ATAPI CDROM problem (NEC-260)
Starting sometime around 2.0.33 kernel, I have had to put append=hdc=cdrom in lilo.conf. My home system has both an internal zip and a cdrom. I have to use the append line whether there is a zip drive present or not. It just seems to get the cdrom wrong. Just give it a hint in lilo.conf and things will be ok. My zip looks like a hard disk. I don't know if it is an ide floppy or not. I believe the imation(sp?) 120mb superdisk is an ide floppy. jim -- From: Kent West[SMTP:[EMAIL PROTECTED] Sent: Tuesday, January 19, 1999 10:40 AM To:[EMAIL PROTECTED]; debian-user@lists.debian.org Cc:The recipient's address is unknown. Subject: Re: ATAPI CDROM problem (NEC-260) At 12:04 AM 1/19/1999 -0800, Terry Hancock wrote: Apparently the OS is making an incorrect assumption about the identity of the device and then failing because of it. (Ever heard of an IDE floppy? I've certainly never seen one). Anyway, after booting, there is no /dev/hdb device to mount. Kenneth Sharf hopefully provided the solution (as I have none), but I did want to say that I *think* (and don't quote me on this) that an internal zip drive is considered an IDE floppy. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: /dev/cdrom problem
On Thu, Nov 12, 1998 at 11:39:26PM +, Vincent Murphy wrote: i can't use xplaycd or any other cd playing program as a normal user. the message i get from xplaycd is that permission is denied to use /dev/cdrom. i can make the program work using sudo though. any way i can fix this? See if adding yourself to group disk helps, as in adduser username disk HTH, James
RE: /dev/cdrom problem
Please include the program's output and the result of: ls -al on the /dev device that /dev/cdrom is linked to. On 12-Nov-98 Vincent Murphy wrote: i can't use xplaycd or any other cd playing program as a normal user. the message i get from xplaycd is that permission is denied to use /dev/cdrom. i can make the program work using sudo though. any way i can fix this? i will supply diagnostics if someone shows me how to get them.
/dev/cdrom problem
i can't use xplaycd or any other cd playing program as a normal user. the message i get from xplaycd is that permission is denied to use /dev/cdrom. i can make the program work using sudo though. any way i can fix this? i will supply diagnostics if someone shows me how to get them. regards, vinny -- Vincent Murphy | UCC CompSci Student | [EMAIL PROTECTED] | +353 (086) 8397405
Re: cdrom problem
[EMAIL PROTECTED] (Greg Norris) writes: [...] So when I need to switch my OS, I've been halting the system (shutdown -h now), then pressing reset after I saw a confirmation message for the halt. More because I only use Linux, I've changed my init setup so that this is what Ctrl-Alt-Del does. Edit /etc/inittab and change the line htat says ca:12345:ctrlaltdel:/sbin/shutdown -t1 -r now so that it has -h instead of -r, then type init q to reload it into init. Now I don't have to worry about switching off quickly just after my PC reboots, but only once I get System halted. -- Carey Evans http://home.clear.net.nz/pages/c.evans/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: cdrom problem
After running debian, if I reboot into DOS or win95, my cdrom is not detected by the driver. I have to power off and back on before by cdrom is accessible again. It is an IDE/ATAPI 24X cdrom. I'm not sure of the brand offhand. Just curious if anyone has encountered similar problems, or might have any suggestions. I have encountered the same behaviour with a TEAC CD-56E 6X IDE/ATAPI drive. In my case, I've found that I don't actually have to power down in order for the drive to be recognized by Windows (NT4 in my case), but rebooting via the reset switch is sufficient. So when I need to switch my OS, I've been halting the system (shutdown -h now), then pressing reset after I saw a confirmation message for the halt. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: cdrom problem
I have the same problem with a Mitsumi cdrom on a Mad16 card. I thought it was something to do with the fact that the Mad16 is a software configurable card. Linux seems to leave the hardware in a state DOS can't recognise. I just use halt instead of reboot, and then press the reset button. Tim. PS, sorry if this has already been replied to, usa.net is about six hours slow, I'm looking for another POP mail service. --- Debian/GNU Linux... the maintainable operating system http://www.debian.org -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
cdrom problem
After running debian, if I reboot into DOS or win95, my cdrom is not detected by the driver. I have to power off and back on before by cdrom is accessible again. It is an IDE/ATAPI 24X cdrom. I'm not sure of the brand offhand. Just curious if anyone has encountered similar problems, or might have any suggestions. Geoff Mitchell [EMAIL PROTECTED] --- I think your flesh is separated from the sins it commits and that explains why you smile when you balance on your stack of regrets. --Brainiac -- http://www.inlink.com/~pug -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
CDROM problem part II
What boot parameters should I set to prevent autoprobe and set everything manually? I'm trying to install from scratch if that makes a drifference. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
cdrom problem...
I have a base Debian system installed from floppies on my 586 133mhz. My hd is partitioned for Windoze95 and for Debian. I ran fips, am using a boot mgr, everything going fairly well until I get to the point of trying to get my cdrom running under linux. Please help, 'cause I'm rippin' my hair out here! I've got a quad speed creative labs cdrom with a soundblaster 16 sound card. It works fine with winblows... I bought my Debian CD from CheapBytes with all the goodies on it, and there it sits, patiently waiting... I've read the howto's that I think apply, I couldn't find anything in the dejanews archives, and I even bought my Linux in a Nutshell book. I've tried the ATAPI/IDE driver, nothing. I have no SCSI devices in my system. I bought this system in 1995..were creative labs cdroms still proprietary, or interfaced thru the sound card? I know this is probably just a really dumb user error, and there's probably a simple fix, but it eludes me :-( Any suggestions, please? TIA!
Re: cdrom problem...
On Mon, 31 Mar 1997, smorrill wrote: I have a base Debian system installed from floppies on my 586 133mhz. My hd is partitioned for Windoze95 and for Debian. I ran fips, am using a boot mgr, everything going fairly well until I get to the point of trying to get my cdrom running under linux. Please help, 'cause I'm rippin' my hair out here! I've got a quad speed creative labs cdrom with a soundblaster 16 sound card. It works fine with winblows... I bought my Debian CD from CheapBytes with all the goodies on it, and there it sits, patiently waiting... I've read the howto's that I think apply, I couldn't find anything in the dejanews archives, and I even bought my Linux in a Nutshell book. I've tried the ATAPI/IDE driver, nothing. I have no SCSI devices in my system. I bought this system in 1995..were creative labs cdroms still proprietary, or interfaced thru the sound card? If the cdrom does not have a proprietary interface, then it should be an IDE device. You may need to specify the line hdc=cdrom on the boot line to get it recognized, e.g. 'boot: linux hdc=cdrom'. If it is proprietary, the only driver that might work, AFAIK, is the spbcd driver which you can probably choose to load as a module when you configure the kernel modules from the drivers disk. Good Luck. Syrus. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Syrus Nemat-Nasser [EMAIL PROTECTED]UCSD Physics Dept.
Re: cdrom problem during installation
I did not have a CD at hand so they way I circumvented the problem was to kept opening the CD door until the installation program resumed somehow. On Tue, 24 Dec 1996, Bruce Perens wrote: Gee, these CD drivers are no fun at all. Did you try placing a CD in the drive? (or removing the CD?). Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 --- Alexander Lobkovsky Phone: (805) 893-3684 Institute for Theoretical Physics Fax: (805) 893-2431 University of CaliforniaEmail: [EMAIL PROTECTED] Santa Barbara, CA 93106-4030WWW: http://rainbow.uchicago.edu/~lobkovsk --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
cdrom problem during installation
I had a problem with the Sony CDU 311 CDROM during a floppy installation. The cdrom drive was recognized fine. During the menu driven installation phase, I kept getting messages hdc: media changed hdc: media changed hdc: tray open or drive not ready hdc: irq timeout : status = 0xd0 hdc: ATAPI RESET complete hdc: code: 0x70 key: 0x02 asc: 0x53 ascq: 0x00 etc, etc, etc the cdrom light would keep falshing. I tried turning the cdrom drive off in the BIOS but it didn't help What can I do, please help. --- Alexander Lobkovsky Phone: (805) 893-3684 Institute for Theoretical Physics Fax: (805) 893-2431 University of CaliforniaEmail: [EMAIL PROTECTED] Santa Barbara, CA 93106-4030WWW: http://rainbow.uchicago.edu/~lobkovsk --- -- This message was delayed because the list mail delivery agent was down.
Re: cdrom problem during installation
Gee, these CD drivers are no fun at all. Did you try placing a CD in the drive? (or removing the CD?). Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: cdrom problem during installation
On Tue, 24 Dec 1996, Bruce Perens wrote: Gee, these CD drivers are no fun at all. Did you try placing a CD in the drive? (or removing the CD?). I had the same problem at home with my ATAPI CDROM (Sony CDU77E), the installation program would eventually go on after a long time, but as this program probes the disks often it was quite unsusable. Putting a CD in the drive does solve the problem. My computer at work has got a Toshiba ATAPI CDROM player and does not show this problem. It think the installation instructions should talk about this problem and give the fix. It's better than releasing yet another boot disk with no CDROM support at all, uh? :) -- Farzad FARID Administrateur Reseau SGIP - Publicis -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
