On Sun, Apr 07, 2002 at 09:01:47AM -0400, Thomas R. Shemanske wrote:
> Sorry to be so long in getting back to the list, but I had been working
> at home on a laptop with USB options compiled into the kernel, and
> wanted to make sure that using them as modules was not the problem. I
> am at wor
Sorry to be so long in getting back to the list, but I had been working
at home on a laptop with USB options compiled into the kernel, and
wanted to make sure that using them as modules was not the problem. I
am at work now where I am running a 2.4.18 kernel built from the debian
source packag
On Sat, Apr 06, 2002 at 03:26:07PM -0500, Jens Gecius wrote:
> Craig Dickson <[EMAIL PROTECTED]> writes:
>
> >> Its odd because the Mandrake 2.4.18 works with this reader. My next
> >> step is to compile pristine kernel.org 2.4.18 source to see I can
> >> make that work. I'm curious to find where
Craig Dickson <[EMAIL PROTECTED]> writes:
>> Its odd because the Mandrake 2.4.18 works with this reader. My next
>> step is to compile pristine kernel.org 2.4.18 source to see I can
>> make that work. I'm curious to find where the fault is.
>
> I should have specified that I use kernel.org tarball
begin john quotation:
> Its odd because the Mandrake 2.4.18 works with this reader. My next
> step is to compile pristine kernel.org 2.4.18 source to see I can
> make that work. I'm curious to find where the fault is.
I should have specified that I use kernel.org tarballs, not Debian's
kernel-s
>> I use this sandisk reader on 2.4.18 without a problem, but it is not a=20
>> stock kernel.
>
> I build my own kernels too, but I couldn't get the SDDR-31 to work on
> 2.4.18 at all, although with essentially the same kernel configuration,
> it works beautifully on either 2.4.17 or the 2.4.19-pr
begin Thomas Shemanske quotation:
> I use this sandisk reader on 2.4.18 without a problem, but it is not a
> stock kernel.
I build my own kernels too, but I couldn't get the SDDR-31 to work on
2.4.18 at all, although with essentially the same kernel configuration,
it works beautifully on eithe
You should probably also have scsi-generic loaded as a module
modprobe sg
You could install the package scsiadd, then run
scsiadd -s
to scan the scsi devices.
On occasion (no idea why), I suddenly needed to mount sdb1 instead of sda1.
I use this sandisk reader on 2.4.18 without a problem, but
>
># lsmod grep 'usb\|scsi'
> usb-storage _ _ _ _ _ _48000 _ 0 _(unused)
> scsi_mod _ _ _ _ _ _ _ 84984 _ 2 _[sd_mod usb-storage]
> usbcore _ _ _ _ _ _ _ _48192 _ 0 _[uhci usb-storage]
>
> ... usb-storage is unused though, as if the kernel can't find the
> device - which I guess is what the origi
Hi
I recently installed kernel image 2.4.18-686 under Woody but found I was
unable to mount my Sandisk CF reader (SDDR-31), whereas under 2.4.17-686
this works flawlessly.
So I get the source - debian kernel-source-2.4.18-4, configure it, compile.
Still no go, but I get a handy error message (I
10 matches
Mail list logo
