From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=DMARC_REJECT, MAILING_LIST_MULTI,NICE_REPLY_A autolearn=unavailable autolearn_force=no version=4.0.0 Received: from mx0.dataguard.no (mx0.dataguard.no [212.62.224.13]) by chiba.3jane.net (Postfix) with SMTP id C59DCAC694 for ; Thu, 13 Jun 2002 04:55:42 -0500 (CDT) Received: (qmail 51417 invoked from network); 13 Jun 2002 09:55:40 -0000 Received: from unknown (HELO nix.no-ip.org) (217.8.136.251) by mx0.dataguard.no with SMTP; 13 Jun 2002 09:55:40 -0000 Date: Thu, 13 Jun 2002 12:01:05 +0200 From: Kim Bratlie To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] Gentoo Linux 1.3a Final Overview Message-Id: <20020613120105.2f345361.eonic@goth.net> In-Reply-To: <200206131103.55883.verwilst@gentoo.org> References: <200206131103.55883.verwilst@gentoo.org> X-Mailer: Sylpheed version 0.7.7 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 82adbb51-17b1-4d72-a219-e8dab26ccdf4 X-Archives-Hash: 397326732cdc0d9125fa8f84b40a1b7e > Things already fixed in my current 1.3b trial version: > > - ncurses prob (new gcc revision (r6)) > - 2 bogus accounts on tarballs > - emerge rsync complaining about /etc/make.profile > - .. more, can't seem to remember them :) > > > Please, gimme more! :o) > Thanks in advance make.conf: CFLAGS="-march=i686 -mmmx -msse -mfpmath=sse -O3 -pipe" CXXFLAGS="-march=i686 -mmmx -msse -mfpmath=sse -O3 -pipe" Works through the bootstrap but fails at emerge system, can't remember on what exactly though. :-/ Small thing I guess.. Other than that I find 1.3a very nice, only problem was changing -march=pentium3 to -march=i686 when compiling lbreakout2 :) Again, a package problem I guess.. I have a general gentoo problem with my SCSI devices, especially if I try to use SCSI together with IDE, then the system hangs completely so I removed all my IDE devices and now after changing network card (my old network card would give me SCSI errors when doing anything internet related under the gentoo install) the only problem remaining is this: WARNING - Running *really* short on dma buffers WARNING - Running *really* short on dma buffers WARNING - Running *really* short on dma buffers WARNING - Running *really* short on dma buffers --- more of the same... SCSI cdrom error : host 0 channel 0 id 3 lun 0 return code = 10000 I/O error: dev 0b:00, sector xxxxx cp: read: input/output error SCSI cdrom error : host 0 channel 0 id 3 lun 0 return code = 10000 I/O error: dev 0b:00, sector xxxxx cp: read: input/output error --- more of the same... I get this when I try to copy stuff from my SCSI CD-RW, both with original discs and discs I've made myself and which work well on other computers. Also when I try to burn CD's I sometimes get input/output errors. I see several people have a similar problem with Adaptec SCSI adapters using the AIC7xxx driver, think there might be a problem with it? For instance, Erwann Corvellec said in a earlier mail: "I am trying to install gentoo-i686-1.2.iso and while executing mke2fs on a 12GB SCSI partition I get : Writing superblocks and filesystem accouting information: Warning - running *really* short on DMA buffers Warning - running *really* short on DMA buffers Warning - running *really* short on DMA buffers ... etc. The same command doesn't output any warning on gentoo-i686-1.1a.iso. The gentoo 1.2 kernel flavor is surely the cause. To be more precise, it is maybe the "Adaptec AIC7xxx" driver revision : 6.2.5 on 1.1a vs 6.2.6 on 1.2. -- Erwann CORVELLEC" Only difference is my problems relate to a CD-RW drive and not a harddrive.. it's been a long time since I tried 1.1a so I can't really tell you if I have no problems with that release, but perhaps it's time to look into this? :) However, I can tell you for sure that this problem did not exist on m$ winblows. - Kim