So there's really nothing to worry anymore :)
Thanks.
stefano
On Friday 28 November 2003 16:47, you wrote:
> On Fri, 28 Nov 2003, Stefano Barbato wrote:
> > > That's not an error. 36 bytes is the normal length of an INQUIRY
> > > response. I'm not quite sure why the driver asks for 255 bytes;
On Fri, 28 Nov 2003, Stefano Barbato wrote:
> > That's not an error. 36 bytes is the normal length of an INQUIRY
> > response. I'm not quite sure why the driver asks for 255 bytes; under 2.6
> > it only asks for 36. The FIX_INQUIRY flag isn't needed.
>
> INQUIRY len seems to be (errouneously?)
> That's not an error. 36 bytes is the normal length of an INQUIRY
> response. I'm not quite sure why the driver asks for 255 bytes; under 2.6
> it only asks for 36. The FIX_INQUIRY flag isn't needed.
INQUIRY len seems to be (errouneously?) hardcoded into scsi layer:
2.4.22 [scsi_scan.c:589]
-
On Thu, 27 Nov 2003, Stefano Barbato wrote:
> Alan,
>
> I got some more cards to try and all worked correctly.
>
> It seems that the card I was using for testing (it's an old 8Mb compact flash)
> confuses this reader (oh, btw, it's called Atech PRO-9 [search engines this
> is for you]) that s
Alan,
I got some more cards to try and all worked correctly.
It seems that the card I was using for testing (it's an old 8Mb compact flash)
confuses this reader (oh, btw, it's called Atech PRO-9 [search engines this
is for you]) that stop working after receiving the first command when such
ca
On Wed, 26 Nov 2003, Stefano Barbato wrote:
> Hi Alan,
>
> sorry if I take so long to reply, I couldn't reply until now.
>
> I attached a complete log from the power up to the read failure.
>
> After the prompt I run:
>
> # modprobe ehci-hcd
> # modprobe
On Sun, 23 Nov 2003, Stefano Barbato wrote:
> I forgot to write that I'm running a vanilla kernel 2.4.22 on a VIA chipset
> (VIA Epia board but I've also tried an ASUS [also with VIA chipset] with same
> results).
>
> I managed to let it work once using the uhci driver (before was usb-uhci). Th
On Sun, 23 Nov 2003, Stefano Barbato wrote:
> Thanks for your reply.
>
> I rebooted, (usbcore and usb-uhci were automatically loaded), modprobe
> usb-storage, modprobe sd_mod.
> I saved the log in "not_connected.log".
>
> Then I connected the reader without any memory cards inserted and I got
I forgot to write that I'm running a vanilla kernel 2.4.22 on a VIA chipset
(VIA Epia board but I've also tried an ASUS [also with VIA chipset] with same
results).
I managed to let it work once using the uhci driver (before was usb-uhci). The
first time I run dd it took about 10 seconds to retu
Thanks for your reply.
I rebooted, (usbcore and usb-uhci were automatically loaded), modprobe
usb-storage, modprobe sd_mod.
I saved the log in "not_connected.log".
Then I connected the reader without any memory cards inserted and I got
"connected_no_card.log".
Then I put a compact flash and ru
On Sun, 23 Nov 2003, Stefano Barbato wrote:
> I bought an Atech PRO-9 (actually two :( ) multi memory cards reader because I
> read somewhere that it works on linux but I'm experiencing strange problems
> that make it unusable.
>
> I use polling (dd if=/dev/sdX of=/dev/null bs=1 count=1) to det
I bought an Atech PRO-9 (actually two :( ) multi memory cards reader because I
read somewhere that it works on linux but I'm experiencing strange problems
that make it unusable.
I use polling (dd if=/dev/sdX of=/dev/null bs=1 count=1) to detect when a card
is inserted but after a few cycles it
12 matches
Mail list logo
