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 i
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
> > > > recog
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.
> > >
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:"...
> > > > e
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
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
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 ru
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
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?
L
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 wo
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
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
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. Firs
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
> > com
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 to
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!
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
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 wh
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
rea
19 matches
Mail list logo
