Re: SG_BIG_BUFF, glibc 2.1 weirdness ...

Andreas Beck (becka@rz.uni-duesseldorf.de)
Sun, 15 Aug 1999 21:05:56 +0200

Hi !

> > Hi folks. I just went almost mad tracking a very strange problem with sane
> > 1.0.0, kernel 2.2.5 and glibc 2.1. I do not know, if it is fixed in 1.0.1.
> > If so, please disregard this mail.
> I run linux-2.2.5/x86 and sane-1.0.1 (SuSE-6.1)
> after I changed the SG_BIG_BUFF to 128K in both sg.h files and recompiled the
> kernel and sane everything works fine!

Yes. The both is the trick. I missed the second one, as I'm accustomed to
glibc. We should at least deal gracefully with the condition, as it as well
applies to binary distributions, that have been compiled on a machine with
SG_BIG_BUFF unmodified and that run on one with a modified BIG_BUFF.

> In the manpage sane-scsi there is written:
> XX Unless a system is seriously
> XX short on memory, it is recommended to increase this value
> XX to the maximum legal value of 128*1024-512=130560 bytes.

Interesting. Full 128k work for me as well and the sg-docs say that's what
it should be.

> > Glibc installs its _own_ scsi.h and sg.h, which are different from the
> > kernel. Thus is you only edit sg.h from the Linux subdirectory you get very
> > very weird behaviour:

> This is something that should be changed in ther kernel surces/glic.

I'll take care for a graceful handling of the condition as well as support
for the new sg driver in 2.2.6 and up.

CU, Andy

-- 
= Andreas Beck                    |  Email :  <andreas.beck@ggi-project.org> =

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com