Re: 2.6.12 and 2.6.13 won't access cdrom -UPDATE
On 11 Oct 2005, Basajaun wrote: Anthony Campbell wrote: On 11 Oct 2005, Basajaun wrote: Anthony Campbell wrote: [snip] I've just fetched the vanilla 2.6.13.3. It compiles correctly and recognizes my CD drives. So it looks as if the problem has been recognized and fixed in the most recent versions. Anthony [snip] Where did you find the 2.6.13.3 package? I have Etch and Sid sources in /etc/apt/sources.list, and 2.6.12 is the latest aptitude finds. Also, search in the Debian site gives 2.6.12 as the official kernel for Etch and Sid... could you post the sources.list line that does the trick, please? Basajaun I got it from ftp.kernel.org, i.e. the vanilla kernel source. Subsequently I also got the relevant linux-image from http://ftp.debian.org/debian/pool/main/l/linux-2.6/ and this seems to work as well. Anthony Thanks a lot. I actually had already compiled a 2.6.13 kernel from kernel.org, as I mention, and also dpkg-ed one from the experimental release. Both work fine, but the non-detection problem is identical with both of them and 2.6.12, because the source of the error is somewhere else. I backtracked the problem to the SATA disk my comp has. The 2.6 kernels recognize it as SCSI at boot, so they load the ata_piix module, which subsequently blocks loading of ide-core, ide-generic etc. Actually, these modules are loaded at some point, but they complain that ide0 and ide1 are already taken (ata_piix seems to have hijacked them). I intend to upload my epic odyssey to my Linux trick page, and I might post a link, if I don't find it too lame :^) My solution, in short, has been to insert these lines in /etc/mkinitrd/modules: ide-core cdrom ide-cd ide-disk ide-generic (the order is important, because of inter-dependencies that are not held properly at the boot time where these options kick in, since modprobe is not available to the kernel or whatever). Then I made a new initrd image for my kernel, reading the file above: mkinitrd -o /boot/initrd.img-2.6.12-1-686-smp.custom 2.6.12-1-686-smp and the final touch would be to insert the corresponding line in /boot/grub/menu.lst. HTH any other person with a similar problem. BTW, searching the web for literal boot-time error messages like I/O Resource 0x1F0-0x1F7 not free did it, so bless Google, and bless the thousands of users that, no matter how obscure an error might be, have already suffered it and posted about it in public forums (in this case, even as far back as in late 2004). Basajaun Interesting. My problem only became apparent with a newly built motherboard which does have SATA stuff in its BIOS. I don't understand much about this and am reusing my old disks so I turned it off. However, in my case there did seem to be a difference when moving from 2.6.12 to 2.6.13. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom -UPDATE
Basajaun wrote: [snip] I intend to upload my epic odyssey to my Linux trick page, and I might post a link, if I don't find it too lame :^) [snip] Here you are: http://makeashorterlink.com/?O532317FB That page, and those following the [Linux stuff] link at the bottom, could be helpfull in general. If anyone finds one of the many errors there sure are, I'd be grateful to know about it/them. (As a side note, my Bluebottle e-mail account asks for a confirmation when receiving e-mails, as a way to prevent automated spammers to get through. Sorry for the inconvenience if anyone writes.) Basajaun -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
On Mon, Oct 10, 2005 at 05:32:48PM -0700, James Vahn wrote: Gcc-4.0 won't work. Just install and link /usr/bin/gcc-3.4 to /usr/bin/gcc. Tried make deb-pkg yet? :-) Uh, why would he break his installation of gcc versus using the normal methods of specifying which compiler should be used? Leave the symlink alone. -- Marc Wilson | Oh, wow! Look at the moon! [EMAIL PROTECTED] | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
On 11 Oct 2005, Marc Wilson wrote: On Mon, Oct 10, 2005 at 05:32:48PM -0700, James Vahn wrote: Gcc-4.0 won't work. Just install and link /usr/bin/gcc-3.4 to /usr/bin/gcc. Tried make deb-pkg yet? :-) Uh, why would he break his installation of gcc versus using the normal methods of specifying which compiler should be used? Leave the symlink alone. Where do you do this, please? Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom -UPDATE
On 10 Oct 2005, Anthony Campbell wrote: On 10 Oct 2005, Basajaun wrote: I have a similar problem here, and sysfs won't help. My /proc/sys/dev/cdrom/info file is empty (contains the drive name:... entries, but w/o a value). Also my /sys/bus/ide/devices/ dir is empty. I am running Debian Etch with kernel 2.6.12-1-686-smp (on a P4 with HT), udev 0.070-2. Glad I'm not the only one - thought I was going mad! I've now found a version of the kernel tree (2.6.13.2) on my laptop and compiled it for my desktop, and I find it *does* compile and *does* recognize my cd drive. This is welcome, of course, but I wish I understood what is happening. Anthony I've just fetched the vanilla 2.6.13.3. It compiles correctly and recognizes my CD drives. So it looks as if the problem has been recognized and fixed in the most recent versions. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom -UPDATE
Anthony Campbell wrote: On 10 Oct 2005, Anthony Campbell wrote: On 10 Oct 2005, Basajaun wrote: I have a similar problem here, and sysfs won't help. My /proc/sys/dev/cdrom/info file is empty (contains the drive name:... entries, but w/o a value). Also my /sys/bus/ide/devices/ dir is empty. I am running Debian Etch with kernel 2.6.12-1-686-smp (on a P4 with HT), udev 0.070-2. Glad I'm not the only one - thought I was going mad! I've now found a version of the kernel tree (2.6.13.2) on my laptop and compiled it for my desktop, and I find it *does* compile and *does* recognize my cd drive. This is welcome, of course, but I wish I understood what is happening. Anthony I've just fetched the vanilla 2.6.13.3. It compiles correctly and recognizes my CD drives. So it looks as if the problem has been recognized and fixed in the most recent versions. Anthony I have compiled a 2.6.13.4 source from kernel.org, and the problem stays (no wonder, being the first kernel I compile. What bewilders me is that my comp didn't catch fire or something when I booted it on my compiled 2.6.13.4 :^). Where did you find the 2.6.13.3 package? I have Etch and Sid sources in /etc/apt/sources.list, and 2.6.12 is the latest aptitude finds. Also, search in the Debian site gives 2.6.12 as the official kernel for Etch and Sid... could you post the sources.list line that does the trick, please? Basajaun -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom -UPDATE
On Tue, 11 Oct 2005, Basajaun wrote: Where did you find the 2.6.13.3 package? I have Etch and Sid sources in Sid has 2.6.13.3. Debian does not add the stable patch level, so it is named linux-tree-2.6.13 (plus dependencies). -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom -UPDATE
On 11 Oct 2005, Basajaun wrote: Anthony Campbell wrote: On 10 Oct 2005, Anthony Campbell wrote: On 10 Oct 2005, Basajaun wrote: I have a similar problem here, and sysfs won't help. My /proc/sys/dev/cdrom/info file is empty (contains the drive name:... entries, but w/o a value). Also my /sys/bus/ide/devices/ dir is empty. I am running Debian Etch with kernel 2.6.12-1-686-smp (on a P4 with HT), udev 0.070-2. Glad I'm not the only one - thought I was going mad! I've now found a version of the kernel tree (2.6.13.2) on my laptop and compiled it for my desktop, and I find it *does* compile and *does* recognize my cd drive. This is welcome, of course, but I wish I understood what is happening. Anthony I've just fetched the vanilla 2.6.13.3. It compiles correctly and recognizes my CD drives. So it looks as if the problem has been recognized and fixed in the most recent versions. Anthony I have compiled a 2.6.13.4 source from kernel.org, and the problem stays (no wonder, being the first kernel I compile. What bewilders me is that my comp didn't catch fire or something when I booted it on my compiled 2.6.13.4 :^). Where did you find the 2.6.13.3 package? I have Etch and Sid sources in /etc/apt/sources.list, and 2.6.12 is the latest aptitude finds. Also, search in the Debian site gives 2.6.12 as the official kernel for Etch and Sid... could you post the sources.list line that does the trick, please? Basajaun I got it from ftp.kernel.org, i.e. the vanilla kernel source. Subsequently I also got the relevant linux-image from http://ftp.debian.org/debian/pool/main/l/linux-2.6/ and this seems to work as well. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom -UPDATE
Anthony Campbell wrote: On 11 Oct 2005, Basajaun wrote: Anthony Campbell wrote: [snip] I've just fetched the vanilla 2.6.13.3. It compiles correctly and recognizes my CD drives. So it looks as if the problem has been recognized and fixed in the most recent versions. Anthony [snip] Where did you find the 2.6.13.3 package? I have Etch and Sid sources in /etc/apt/sources.list, and 2.6.12 is the latest aptitude finds. Also, search in the Debian site gives 2.6.12 as the official kernel for Etch and Sid... could you post the sources.list line that does the trick, please? Basajaun I got it from ftp.kernel.org, i.e. the vanilla kernel source. Subsequently I also got the relevant linux-image from http://ftp.debian.org/debian/pool/main/l/linux-2.6/ and this seems to work as well. Anthony Thanks a lot. I actually had already compiled a 2.6.13 kernel from kernel.org, as I mention, and also dpkg-ed one from the experimental release. Both work fine, but the non-detection problem is identical with both of them and 2.6.12, because the source of the error is somewhere else. I backtracked the problem to the SATA disk my comp has. The 2.6 kernels recognize it as SCSI at boot, so they load the ata_piix module, which subsequently blocks loading of ide-core, ide-generic etc. Actually, these modules are loaded at some point, but they complain that ide0 and ide1 are already taken (ata_piix seems to have hijacked them). I intend to upload my epic odyssey to my Linux trick page, and I might post a link, if I don't find it too lame :^) My solution, in short, has been to insert these lines in /etc/mkinitrd/modules: ide-core cdrom ide-cd ide-disk ide-generic (the order is important, because of inter-dependencies that are not held properly at the boot time where these options kick in, since modprobe is not available to the kernel or whatever). Then I made a new initrd image for my kernel, reading the file above: mkinitrd -o /boot/initrd.img-2.6.12-1-686-smp.custom 2.6.12-1-686-smp and the final touch would be to insert the corresponding line in /boot/grub/menu.lst. HTH any other person with a similar problem. BTW, searching the web for literal boot-time error messages like I/O Resource 0x1F0-0x1F7 not free did it, so bless Google, and bless the thousands of users that, no matter how obscure an error might be, have already suffered it and posted about it in public forums (in this case, even as far back as in late 2004). Basajaun -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
Anthony Campbell wrote: Kernel versions 2.6.12 and 2.6.13 are causimg serious problems here. 2.6.13 won't access /cdrom and 2.6.12 segfaults when I try this. It is then impossible to log out normally and I have to pull the plug on the computer! I have an older (non-Debian) version of 2.6.12 which does work, for some reason. I'd like to revert to 2.6.11 or 2.6.10 but image files for this don't appear to be available for Debian now. I tried to compile a vanilla kernel but the compile fails (something to do with gcc ???). What to do now? Is there somewhere I can get earlier kernel images to try? Anthony apt-cache search kernel-image |more apt-get install kernel-image (choose one...) is this sarge? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
On Mon, Oct 10, 2005 at 02:35:09PM +0100, Anthony Campbell wrote: 2.6.13 won't access /cdrom and 2.6.12 segfaults when I try this. It is then impossible to log out normally and I have to pull the plug on the computer! Well, that sounds a touch drastic. First of all, do you mean /cdrom? There should be no such file. Do you mean /dev/cdrom? That used to exist, but I believe it's been deleted: it used to be a symlink to something like /dev/hdc (or whatever your CD-ROM drive device was), but lots of people have multiple CD/DVD drives; how is Linux supposed to know which one to symlink to? The proper approach now, I believe, is to use sysfs. See below for the info on my system. It says that my CD drive is /dev/hdc, which I can then -- if I want -- make a symlink to. I don't know how to make that symlink permanent, such that /dev/cdrom is there when I reboot. (09:39) [EMAIL PROTECTED]:~/private$ cat /proc/sys/dev/cdrom/info CD-ROM information, Id: cdrom.c 3.20 2003/12/17 drive name: hdc drive speed:24 drive # of slots: 1 Can close tray: 1 Can open tray: 1 Can lock tray: 1 Can change speed: 1 Can select disk:0 Can read multisession: 1 Can read MCN: 1 Reports media changed: 1 Can play audio: 1 Can write CD-R: 1 Can write CD-RW:1 Can read DVD: 1 Can write DVD-R:0 Can write DVD-RAM: 0 Can read MRW: 1 Can write MRW: 1 Can write RAM: 1 -- Stephen R. Laniel [EMAIL PROTECTED] +(617) 308-5571 http://laniels.org/ PGP key: http://laniels.org/slaniel.key signature.asc Description: Digital signature
Re: 2.6.12 and 2.6.13 won't access cdrom
On 10 Oct 2005, Bruno Buys wrote: Anthony Campbell wrote: Kernel versions 2.6.12 and 2.6.13 are causimg serious problems here. 2.6.13 won't access /cdrom and 2.6.12 segfaults when I try this. It is then impossible to log out normally and I have to pull the plug on the computer! I have an older (non-Debian) version of 2.6.12 which does work, for some reason. I'd like to revert to 2.6.11 or 2.6.10 but image files for this don't appear to be available for Debian now. I tried to compile a vanilla kernel but the compile fails (something to do with gcc ???). What to do now? Is there somewhere I can get earlier kernel images to try? Anthony apt-cache search kernel-image |more apt-get install kernel-image (choose one...) is this sarge? No, Sid. I already tried this; nothing older than 1.6.12 turns up. -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
On 10 Oct 2005, Stephen R Laniel wrote: On Mon, Oct 10, 2005 at 02:35:09PM +0100, Anthony Campbell wrote: 2.6.13 won't access /cdrom and 2.6.12 segfaults when I try this. It is then impossible to log out normally and I have to pull the plug on the computer! Well, that sounds a touch drastic. First of all, do you mean /cdrom? There should be no such file. Do you mean /dev/cdrom? That used to exist, but I believe it's been deleted: it used to be a symlink to something like /dev/hdc (or whatever your CD-ROM drive device was), but lots of people have multiple CD/DVD drives; how is Linux supposed to know which one to symlink to? The proper approach now, I believe, is to use sysfs. See below for the info on my system. It says that my CD drive is /dev/hdc, which I can then -- if I want -- make a symlink to. I don't know how to make that symlink permanent, such that /dev/cdrom is there when I reboot. (09:39) [EMAIL PROTECTED]:~/private$ cat /proc/sys/dev/cdrom/info CD-ROM information, Id: cdrom.c 3.20 2003/12/17 drive name: hdc drive speed:24 drive # of slots: 1 Can close tray: 1 Can open tray: 1 Can lock tray: 1 Can change speed: 1 Can select disk:0 Can read multisession: 1 Can read MCN: 1 Reports media changed: 1 Can play audio: 1 Can write CD-R: 1 Can write CD-RW:1 Can read DVD: 1 Can write DVD-R:0 Can write DVD-RAM: 0 Can read MRW: 1 Can write MRW: 1 Can write RAM: 1 -- Stephen R. Laniel [EMAIL PROTECTED] +(617) 308-5571 http://laniels.org/ PGP key: http://laniels.org/slaniel.key We seem to be at cross-purposes here. I have a directory called /cdrom. My /dev/cdrom is a symlink to /dev/hdc. With this, mounting /cdrom has always worked in the past (for years). I don't know anything about sysfs. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
On 10 Oct 2005, Antony Gelberg wrote: Anthony Campbell wrote: Kernel versions 2.6.12 and 2.6.13 are causimg serious problems here. 2.6.13 won't access /cdrom and 2.6.12 segfaults when I try this. It is then impossible to log out normally and I have to pull the plug on the computer! I have an older (non-Debian) version of 2.6.12 which does work, for some reason. I'd like to revert to 2.6.11 or 2.6.10 but image files for this don't appear to be available for Debian now. I tried to compile a vanilla kernel but the compile fails (something to do with gcc ???). What to do now? Is there somewhere I can get earlier kernel images to try? What version of Debian are you running? Where do the 2.6.12 and 2.6.13 come from? Who built them? I'm running Sid. The kernels I have are both linux-image, i.e. the standard Linux images as obtained from the Debian mirror. I've tried compiling vanilla kernels but for some reason they fail to do so, both on my desktop and my laptop. This a new development; they always used to compile in the past without problems. There was a large update on Sid a couple of days ago; perhaps this broke things? Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
Stephen R Laniel wrote:
On Mon, Oct 10, 2005 at 02:35:09PM +0100, Anthony Campbell wrote:
2.6.13 won't access /cdrom and 2.6.12 segfaults when I try this. It is
then impossible to log out normally and I have to pull the plug on the
computer!
Well, that sounds a touch drastic. First of all, do you mean
/cdrom? There should be no such file. Do you mean
/dev/cdrom? That used to exist, but I believe it's been
deleted: it used to be a symlink to something like /dev/hdc
(or whatever your CD-ROM drive device was), but lots of
people have multiple CD/DVD drives; how is Linux supposed to
know which one to symlink to?
The proper approach now, I believe, is to use sysfs. See
below for the info on my system. It says that my CD drive is
/dev/hdc, which I can then -- if I want -- make a symlink
to. I don't know how to make that symlink permanent, such
that /dev/cdrom is there when I reboot.
(09:39) [EMAIL PROTECTED]:~/private$ cat /proc/sys/dev/cdrom/info
CD-ROM information, Id: cdrom.c 3.20 2003/12/17
drive name: hdc
[snip]
I have a similar problem here, and sysfs won't help. My
/proc/sys/dev/cdrom/info file is empty (contains the drive name:...
entries, but w/o a value). Also my /sys/bus/ide/devices/ dir is empty.
I am running Debian Etch with kernel 2.6.12-1-686-smp (on a P4 with
HT), udev 0.070-2.
If I boot under 2.4.27-2-686-smp (w/o udev, of course), the /dev/hdc
device is created, and I can mount a CD just fine. With 2.6.12, not
even dmesg acknowlegdes the presence of the CD drive, no /dev entry is
created, and no info appears in /sys (I mean, regarding the CD drive).
Maybe, just maybe, it has something to do with module ide-detect?
Kernel 2.4 has it, but not 2.6. Somewhere I read to add ide-generic
to /etc/modules, in place of ide-detect (which would only make the
system complain everytime I booted into 2.6, anyway), and it didn't
help.
Another idea is: does it have anything to do with the fact that 2.4
sees my SATA drive as IDE, and 2.6 sees it as SCSI? Maybe 2.6 doesn't
find IDE drives, and doesn't load some modules which are later needed
for the CD? I seem to be seeing them loaded, however:
#lsmod | grep ide
ide_cd 43748 0
cdrom 41088 1 ide_cd
ide_disk 19104 0
ide_generic 1376 0 [permanent]
ide_core 132352 4 ide_cd,ide_disk,ide_generic,usb_storage
I have to add that I disabled hotplug on boot (after doing a lsmod |
awk '{print $1}' /etc/modules), because it made the computer take
forever (over 15m!!) to boot. Now, w/o hotplug, it is much faster, but
still very slow. And before anyone jumps on me, the problem was there
when I was running hotplug...
Can someone help?
Basajaun
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
On 10 Oct 2005, Basajaun wrote: I have a similar problem here, and sysfs won't help. My /proc/sys/dev/cdrom/info file is empty (contains the drive name:... entries, but w/o a value). Also my /sys/bus/ide/devices/ dir is empty. I am running Debian Etch with kernel 2.6.12-1-686-smp (on a P4 with HT), udev 0.070-2. Glad I'm not the only one - thought I was going mad! I've now found a version of the kernel tree (2.6.13.2) on my laptop and compiled it for my desktop, and I find it *does* compile and *does* recognize my cd drive. This is welcome, of course, but I wish I understood what is happening. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
Stephen R Laniel [EMAIL PROTECTED] writes: The proper approach now, I believe, is to use sysfs. See below for the info on my system. It says that my CD drive is /dev/hdc, which I can then -- if I want -- make a symlink to. I don't know how to make that symlink permanent, such that /dev/cdrom is there when I reboot. Install udev. There should already be rules for creating the cdrom symlink -- John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.12 and 2.6.13 won't access cdrom
Anthony Campbell wrote: Kernel versions 2.6.12 and 2.6.13 are causimg serious problems here. 2.6.13 won't access /cdrom and 2.6.12 segfaults when I try this. It is then impossible to log out normally and I have to pull the plug on the computer! Similar trouble here. Kernel.org-2.6.13 won't mount them yet I can burn images just fine. kernel.org-2.6.12.6 is okay other than umounting won't allow the use of the eject button - but the command eject as root works. I'm using ide-cd, and ide-scsi is even worse. I tried to compile a vanilla kernel but the compile fails (something to do with gcc ???). Gcc-4.0 won't work. Just install and link /usr/bin/gcc-3.4 to /usr/bin/gcc. Tried make deb-pkg yet? :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
