headers
James Burton | 1 Mar 2004 10:59

Re: sip0: transmit FIFO underrun on 1.6.2RC4

> You may want to take a look at PR-13770 (too).  I experienced the same
> "transmit FIFO underrun" with the sip0 driver on a freshly installed NetBSD
> 1.6.1 system, and found that the fix described in PR-13770 worked.

Spot on.
Thanks for that Dion.

I now get 

Mar  1 20:43:41 artworks /netbsd: sip0: frame alignment error
Mar  1 20:43:43 artworks /netbsd: sip0: frame alignment error

but only a few so far and at least the error rate is well down

Name  Mtu   Network       Address              Ipkts Ierrs    Opkts Oerrs Colls
sip0  1500  <Link>        00:09:5b:60:7e:3e    92303     2    73643     2 64702
sip0  1500  1.2.3.4/      1.2.3.6      
                          224.0.0.1            92303     2    73643     2 64702
sip0  1500  1.2.3.4/      1.2.3.9              92303     2    73643     2 64702
sip0  1500  1.2.3.4/      1.2.3.10             92303     2    73643     2 64702

I submitted a new PR.

Thanks,
James
---
James Burton (james <at> jmsh.net)           Call the men of science, let them
                                        hear this song. Tell them Albert
                                        Einstein & Copernicus were wrong.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Apprich | 2 Mar 2004 02:29
Picon

Compaqs and 16MB limits


    I'm having trouble getting the GENERIC kernel to see more than 16MB
on a Compaq Prosignia VS and Proliant rack mount units. Is there some
kind of quirk in the memory management that causes this?

This is the dmesg.out from the ProLiant

NetBSD 1.5.2 (GENERIC) #3: Sat Aug 18 23:37:05 CEST 2001
    he <at> hamster.urc.uninett.no:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium (P54C) (586-class), 100.21 MHz
total memory = 16000 KB
avail memory = 9596 KB
using 225 buffers containing 900 KB of memory
BIOS32 rev. 0 found at 0xf0000
mainbus0 (root)
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled
Compaq Triflex Host-PCI Bridge (miscellaneous prehistoric, revision
0x01) at pci0 dev 0 function 0 not configured
siop0 at pci0 dev 10 function 0: Symbios Logic 53c825 (fast wide scsi)
siop0: interrupting at irq 10
scsibus0 at siop0: 16 targets, 8 luns per target
ex0 at pci0 dev 14 function 0: 3Com 3c905B-TX 10/100 Ethernet (rev.
0x24)
ex0: interrupting at irq 5
ex0: MAC address 00:50:04:23:d2:9e
exphy0 at ex0 phy 24: 3Com internal media interface
exphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pceb0 at pci0 dev 15 function 0
pceb0: Intel 82375EB/SB PCI-EISA Bridge (PCEB) (rev. 0x05)
(Continue reading)

Permalink | Reply | 2 comments |
headers
Christian Biere | 2 Mar 2004 04:19
Picon
Picon
Gravatar

Re: Compaqs and 16MB limits

Paul Apprich wrote:
>     I'm having trouble getting the GENERIC kernel to see more than 16MB
> on a Compaq Prosignia VS and Proliant rack mount units. Is there some
> kind of quirk in the memory management that causes this?

See options(4) for REALEXTMEM. Be sure to substract the first MB.

--

-- 
Christian
Permalink | Reply | 0 comments |
headers
Alicia da Conceicao | 2 Mar 2004 19:59
Picon
Favicon

GetTempFileNameA likely cause of link.exe error under NetBSD+Peace

Hi again:

I have managed to also get both the Win32 "cl.exe" and WinCE/PocketPC
"clarm.exe" compilers to work under NetBSD+Peace, and these produce
the proper object files that I can transfer to a windows system and
successfully link into working Win32(98/ME/2000/XP) and working
WinCE/PocketPC binaries.

Of course, I still need to get "link.exe" to work in NetBSD+Peace so
that I can link the windows binaries from the object files without
having to transfer them to another computer.

I have examined the "link.exe" further, and it would appear that either
GetTempFileNameA fails (can't generate a proper temp filename), or the
filename it provides has an invalid path.  As I mentioned previously, I
am still the "TMP" & "TEMP" environment variables to a proper temporary
directory ("C:\tmp") which under Peace is translated to "/sec/tmp" on
my NetBSD filesystem.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/gettempfilename.asp

Does anyone know anyway that we find out what if any temp filename
that the "link.exe" binary is trying to use?  "ktrace link.exe" does
not help.

BTW, this "link.exe" I am trying to use came with VC++ (from Visual
Studio 6.0).  When I attempt to use the newer "link" that comes with
eVC++ (Embedded Visual Studio: WCE400-420), it would SEG-FAULT:
==============================================
         PF_FLOATING_POINT_PRECISION_ERRATA
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Laight | 3 Mar 2004 01:03
Picon

Re: Compaqs and 16MB limits

On Mon, Mar 01, 2004 at 08:29:42PM -0500, Paul Apprich wrote:
> 
>     I'm having trouble getting the GENERIC kernel to see more than 16MB
> on a Compaq Prosignia VS and Proliant rack mount units. Is there some
> kind of quirk in the memory management that causes this?
> 
> This is the dmesg.out from the ProLiant
> 
> NetBSD 1.5.2 (GENERIC) #3: Sat Aug 18 23:37:05 CEST 2001

Try something that escaped from the ark...

	David

--

-- 
David Laight: david <at> l8s.co.uk
Permalink | Reply | 0 comments |
headers
Dr R.S. Brooks | 3 Mar 2004 12:24
Picon
Favicon

Updated binary package ISOs?

Following the release of 1.6.2, will there be an updated set of
binary package ISOs for i386?  And if so, when are they likely
to appear?

Roger
Permalink | Reply | 4 comments |
headers
Steven M. Bellovin | 3 Mar 2004 12:45
Picon

Re: Updated binary package ISOs?

In message <Pine.GSO.4.58.0403031120530.16324 <at> fs3.liv.ac.uk>, "Dr R.S. Brooks" 
writes:
>Following the release of 1.6.2, will there be an updated set of
>binary package ISOs for i386?  And if so, when are they likely
>to appear?
>

They are there:

ftp> ls i386*
229 Entering Extended Passive Mode (|||57500|)
150 Opening ASCII mode data connection for '/bin/ls'.
-rw-r--r--  1 1237  netbsd   147816448 Mar  1 19:28 i386cd.iso
-rw-r--r--  1 1127  hubertf  690257920 Mar  1 05:53 i386pkg.iso
226 Transfer complete.
ftp> pwd
257 "/pub/NetBSD/iso/1.6.2" is the current directory.

This is on ftp.netbsd.org

		--Steve Bellovin, http://www.research.att.com/~smb
Permalink | Reply | 3 comments |
headers
Dr R.S. Brooks | 3 Mar 2004 12:54
Picon
Favicon

Re: Updated binary package ISOs?

On Wed, 3 Mar 2004, Steven M. Bellovin wrote:

>In message <Pine.GSO.4.58.0403031120530.16324 <at> fs3.liv.ac.uk>, "Dr R.S. Brooks"
>writes:
>>Following the release of 1.6.2, will there be an updated set of
>>binary package ISOs for i386?  And if so, when are they likely
>>to appear?
>>
>
>They are there:
>
>ftp> ls i386*
>229 Entering Extended Passive Mode (|||57500|)
>150 Opening ASCII mode data connection for '/bin/ls'.
>-rw-r--r--  1 1237  netbsd   147816448 Mar  1 19:28 i386cd.iso
>-rw-r--r--  1 1127  hubertf  690257920 Mar  1 05:53 i386pkg.iso
>226 Transfer complete.
>ftp> pwd
>257 "/pub/NetBSD/iso/1.6.2" is the current directory.
>
>This is on ftp.netbsd.org

Yes, but I was referring to the multi-cd set of binary packages:

ftp> pwd
257 "/pub/NetBSD/iso/1.6.1" is the current directory.
ftp> dir i386*
200 PORT command successful.
150 Opening ASCII mode data connection for '/bin/ls'.
-rw-rw-r--  1 1237  netbsd   128155648 Apr 21  2003 i386cd.iso
(Continue reading)

Permalink | Reply | 1 comment |
headers
Simas Mockevicius | 3 Mar 2004 12:54
Picon

Re: Updated binary package ISOs?

On Wed, 3 Mar 2004 11:24:19 +0000 (GMT), Dr R.S. Brooks 
<R.S.Brooks <at> liverpool.ac.uk> wrote:

> Following the release of 1.6.2, will there be an updated set of
> binary package ISOs for i386?  And if so, when are they likely
> to appear?
>
> Roger
Hi, Roger,

first of all: ftp://ftp.netbsd.org/pub/NetBSD/iso/1.6.2/README.i386pkg
then:

ftp://ftp.netbsd.org/pub/NetBSD/iso/1.6.2/i386pkg.iso

--

-- 
Sincerely,
Simas Mockevicius
Permalink | Reply | 0 comments |
headers
Maggio | 4 Mar 2004 19:10
Picon

LiteON 52x24x52x DMA old problems

Hi

This is an OLD problem of NetBSD with the LiteON CDRW drives , I've
reported this yet on the "port-i386" mailing list sometime ago , and
with me some other people have replied to that accusing this very very
very annoing problem .

I hoped that this would be fixed in the meantime (from 1.6 or 1.6.1 , I
don't remember , but some months ago , anyway) , but this hasn't been
fixed .

The problem is this :
My model  is LiteON LTR-52246S , I use the lastest FirmWare

The drive seems to be recognized correctly , and I can put a CD inside
it and use it for while the CD is still running in the device , but if
the CD stops running in the device , because the CDRW drive has not been
accessed by a few time when I try to access to it again I get this error :

pciide0:1:0: lost interrupt
             type: atapi tc_bcount: 0 tc_skip: 0
pciide0:1:0: lost interrupt
             type: atapi tc_bcount: 0 tc_skip: 0
pciide0:1:0: dmamode timed out

These messages continue to appear on the screen , until I reload the
device .

I don't know why NetBSD has this LOST INTERRUPT on this device , Linux
and FreeBSD stable have ever worked well .
(Continue reading)

Permalink | Reply | 0 comments |

Gmane