Re: ATA atapi-all.c problems/fixes/cleanups

[Soren Schmidt]

It seems Brian Fundakowski Feldman wrote:
> How about this?  It's mostly the changes in your patch, but it also takes
> into account non-int{8,16}_t-sizing/alignment.  It also takes care of the
> truncation problem when you use outsl and insl, as part of that.  Please
> review it, as I think it should be the right thing to do.

Hmm, sortof. In the real world we should newer ever see partial
transfers, they should always be of N * DEV_BSIZE, so this is
a bitt overkill. However some of the internal ATAPI handling
use odd sizes for modes etc, but they are all at least 16 bit
aligned, so 8 bit alignment is not needed, I'll have to check
if we need 16 bit alignment, I can't remember ofhand...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Mounting CD-ROM with ATA driver hangs system

[Soren Schmidt]

It seems Peter Jeremy wrote:
> I just discovered that my ATAPI CD-ROM is no longer usable - when I
> try to mount it, my maching hangs (hard).
> 
> I'm running -current from cvs-cur 5961 (Monday about UTC).
> 
> The symptoms are:
> 
> Run "mount -r /dev/acd0c /cdrom"
> The CD-ROM activity light flashes briefly and the CD-ROM spins up.
> The activity light then goes hard on for something like 20 seconds.
> The kernel then prints:
>   acd0: atapi_timeout: cmd=READ_BIG - resetting
>   ata0: resetting devices .. _
> The cursor remains at the end of the line ("_" above).  The CD-ROM
> spins up and down.  The HDD light stays hard on.

> acd0:  CDROM drive at ata0 as slave 
> acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA
^^^
You have enabled ATAPI DMA in your kernel config, dont, your
drive apparently doesn't support it.
DMA on ATAPI devices is disabled as default because _lots_ and I mean
_lots_ of ATAPI devices claim to do DMA, but they actually dont :(

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Advance notice: Removing SHA1 passwords

[Kris Kennaway]

Tomorrow I plan to remove the support for SHA1 passwords from libcrypt:
this was (re-)added silently by Mark Murray a few months ago as part of a
cleanup/re-merging of the libcrypt code, and he's already okayed the
re-removal.

The reason I want to remove this is because I intend to reimplement
libcrypt in a more extensible way sometime over the next few months
(assuming I can get over/around/under a final hurdle), and I'd prefer not
to have any more compatability warts than necessary (if this were to make
it into a release we'd have to support it forever). There's no real
advantage to using SHA1 passwords anyway, since they're an algorithmically
identical format to the default MD5 system, and there's nothing inherently
insecure about that one.

If anyone has been using SHA1 passwords, now's the time to regenerate them
:-)

Kris



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current

[Mark Newton]

On Wed, Jan 05, 2000 at 09:15:07PM -0800, David O'Brien wrote:

 > Correct.  The change is due to philosophical changes by the GCC
 > development team.  GCC 2.95.2's cpp built from cccp.c is now a pure
 > preprocessor and knows much less about the world than it previously did.
 > In 2.95.2 there is now an additional cpp that is build using gcc.c and is
 > a driver for the cccp.c cpp.

I dare you to try saying that again with a mouth full of peanuts!

   - mark :-)

-- 
Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current

[David O'Brien]

On Wed, Jan 05, 2000 at 08:47:07PM -0800, David Dawes wrote:
> I've just been doing a build test of the pre-3.3.6 version of
> XFree86 on a recent FreeBSD 4.0-current, and I've noticed that
> /usr/libexec/cpp doesn't predefine the symbol __FreeBSD__.

Correct.  The change is due to philosophical changes by the GCC
development team.  GCC 2.95.2's cpp built from cccp.c is now a pure
preprocessor and knows much less about the world than it previously did.
In 2.95.2 there is now an additional cpp that is build using gcc.c and is
a driver for the cccp.c cpp.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current

[David Dawes]

On Wed, Jan 05, 2000 at 08:47:07PM -0800, David Dawes wrote:
>I've just been doing a build test of the pre-3.3.6 version of
>XFree86 on a recent FreeBSD 4.0-current, and I've noticed that
>/usr/libexec/cpp doesn't predefine the symbol __FreeBSD__.  imake
>uses /usr/libexec/cpp.  Is it intentional that /usr/libexec/cpp
>not predefine any symbols like this?  I've changed imake to use
>/usr/bin/cpp instead, and it seems to work on 3.4 and 4.0.  Should
>this be OK on all FreeBSD versions?

I posted too soon.  This is already dealt with in the pre-4.0 XFree86
code by using 'cc -E'.  I'll fold that change in for 3.3.6.

David


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Matthew Dillon]

:This is a cryptographically signed message in MIME format.
:
:--ms7B55930FA2AAFE9EE4D45CA1
:Content-Type: text/plain; charset=us-ascii
:Content-Transfer-Encoding: 7bit
:
:
:Stupid question: will the latest PAO stuff be integrated with 4.0?
:
:
:-dpg
:--ms7B55930FA2AAFE9EE4D45CA1
:Content-Type: application/x-pkcs7-signature; name="smime.p7s"
:Content-Transfer-Encoding: base64
:Content-Disposition: attachment; filename="smime.p7s"
:Content-Description: S/MIME Cryptographic Signature
:
:MIIKLgYJKoZIhvcNAQcCoIIKHzCCChsCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
:B7owggSEMIID7aADAgECAhAV4oOYVg1pE0gVFzzXJ4WbMA0GCSqGSIb3DQEBBAUAMIHMMRcw
:FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
:...
:... lots of junk removed
:...

What is all ^^^ this junk?  Can you post without adding
all of this?

-Matt


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current

[David Dawes]

I've just been doing a build test of the pre-3.3.6 version of
XFree86 on a recent FreeBSD 4.0-current, and I've noticed that
/usr/libexec/cpp doesn't predefine the symbol __FreeBSD__.  imake
uses /usr/libexec/cpp.  Is it intentional that /usr/libexec/cpp
not predefine any symbols like this?  I've changed imake to use
/usr/bin/cpp instead, and it seems to work on 3.4 and 4.0.  Should
this be OK on all FreeBSD versions?

--- imakemdep.h 1999/07/29 09:22:27 3.24.2.14
+++ xc/config/imake/imakemdep.h 2000/01/06 04:39:59
@@ -265,8 +265,11 @@
 #ifdef _CRAY
 #define DEFAULT_CPP "/lib/pcpp"
 #endif
-#if defined(__386BSD__) || defined(__NetBSD__) || defined(__OpenBSD__) || 
defined(__FreeBSD__)
+#if defined(__386BSD__) || defined(__NetBSD__) || defined(__OpenBSD__)
 #define DEFAULT_CPP "/usr/libexec/cpp"
+#endif
+#if defined(__FreeBSD__)
+#define DEFAULT_CPP "/usr/bin/cpp"
 #endif
 #if defined(__sgi) && defined(__ANSI_CPP__)
 #define USE_CC_E


David
-- 
David Dawes  Email: [EMAIL PROTECTED]
Co-founder/President, The XFree86 Project, Inc   Phone: +1 570 775 9502
http://www.xfree86.org/  Fax:   +61 2 9897 3755


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Mounting CD-ROM with ATA driver hangs system

[Peter Jeremy]

I just discovered that my ATAPI CD-ROM is no longer usable - when I
try to mount it, my maching hangs (hard).

I'm running -current from cvs-cur 5961 (Monday about UTC).

The symptoms are:

Run "mount -r /dev/acd0c /cdrom"
The CD-ROM activity light flashes briefly and the CD-ROM spins up.
The activity light then goes hard on for something like 20 seconds.
The kernel then prints:
acd0: atapi_timeout: cmd=READ_BIG - resetting
ata0: resetting devices .. _
The cursor remains at the end of the line ("_" above).  The CD-ROM
spins up and down.  The HDD light stays hard on.

At this point, the system will not respond to the keyboard.

I didn't have any problems with the WD driver, so I don't think it's
hardware.

Any ideas?

Dmesg output:
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #15: Thu Jan  6 08:02:56 EST 2000
[EMAIL PROTECTED]:/3.0/cvs/src/sys/compile/gsmx
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 267310659 Hz
CPU: Pentium II (267.31-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x633  Stepping = 3
  Features=0x80f9ff
real memory  = 67108864 (65536K bytes)
avail memory = 61980672 (60528K bytes)
Preloaded elf kernel "kernel" at 0xc0301000.
VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc02b1e22 (122)
VESA: Matrox Graphics Inc.
Pentium Pro MTRR support enabled
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
isab0:  at device 7.0 on pci0
isa0:  on isab0
ata-pci0:  at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11
chip1:  at device 7.3 on pci0
vga-pci0:  irq 10 at device 9.0 on pci0
tx0:  irq 9 at device 10.0 on pci0
tx0: address 00:e0:29:24:34:1f, type SMC9432TX, Auto-Neg 100Mbps 
ed0 at port 0x300-0x31f iomem 0xcc000-0xc irq 7 on isa0
ed0: address 00:00:c0:57:99:47, type WD8013EPC (16 bit) 
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
ata-isa0: already registered as ata0
ata-isa1: already registered as ata1
fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
fd1: not probed (disabled)
sio0 at port 0x3f8-0x3ff irq 4 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
pca0 at port 0x40 on isa0
pca0: PC speaker audio driver
isa_compat: didn't get irq for ppc
ppc0 at port 0x378-0x37f irq 7 on isa0
isa_compat: didn't get irq for ppc
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
plip0:  on ppbus 0
lpt0:  on ppbus 0
lpt0: Interrupt-driven port
ppi0:  on ppbus 0
pps0:  on ppbus 0
sbc0:  at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,3 on 
isa0
sbc0: setting card to irq 5, drq 1, 3
pcm0:  on sbc0
joy0:  at port 0x201 on isa0
ad0:  ATA-3 disk at ata0 as master
ad0: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, UDMA33
ad2:  ATA-0 disk at ata1 as master
ad2: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S
ad2: 16 secs/int, 1 depth queue, DMA
acd0:  CDROM drive at ata0 as slave 
acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA
acd0: Reads: CD-R, CD-RW, CD-DA stream
acd0: Audio: play, 16 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
Mounting root from ufs:/dev/ad0s2a

Peter
--
Peter Jeremy (VK2PJ)[EMAIL PROTECTED]
Alcatel Australia Limited
41 Mandible St  Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015   Fax:   +61 2 9690 5982


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: error messages while loading the kernel

[Greg Lehey]

On Wednesday,  5 January 2000 at 18:15:42 -0500, Robert C. Noland III wrote:
> Mark Newton writes:
>> On Wed, Jan 05, 2000 at 05:49:44PM -0500, Robert C. Noland III wrote:
>>
>>> I have seen that as well... It seems to be caused by svr4_enable="YES"
>>> in rc.conf.  or rather the specified module.
>>
>> FWIW, this was fixed in rev 1.10 of svr4_sysvec.c
>
> So it was, it now shows up in:
>
> vinum/vinum.ko
>  U zfree
>
> BTW, this seems to be the only module referencing this symbol at the
> moment.

It's all a consspiracy of the South Australian committers to break the
kernel build.  You'll notice that Peter Wemm (just West of South
Australia) didn't blow our cover :-)

Seriously, it's an inline function.  If you don't include vm/vm_zone.h
in the source file, it will become an undefined reference.  As I said
in an earlier message, it's fixed in Vinum now.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: error messages while loading the kernel

[Greg Lehey]

On Wednesday,  5 January 2000 at 23:35:03 +0100, Thierry Herbelot wrote:
> I've just remade the world and a new kernel with sources supped around
> 21h00 GMT today, and I've got error messages in the kernel loading phase
> (on an SMP machine : bi-celeron BP6)
>
> link_elf: symbol zfree undefined
> link_elf: symbol zfree undefined
>
> 
>
> FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0:
> Wed Jan  5 23:15:23 CET 2000
> [EMAIL PROTECTED]:/usr/src/sys/compile/multi  i386

One possibility is that you're including Vinum in the kernel, as not
recommended.  There was a problem between commits 1.48 and 1.49 of
vinumio.c, about 18 hours.  If you have Vinum in the kernel, just
re-CVSup.

Greg
--
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make.conf NO_SENDMAIL=true blown

[Randy Bush]

>> but current as of today is stomping on /usr/sbin/sendmail, /usr/bin/mailq,
>> etc. all about /usr/sbin/mailwrapper.
> Yeah, that bit me too but I forgot to post a message here.  I'm using
> postfix and I just changed /etc/mail/mailer.conf to this:
> 
> sendmail/usr/local/sbin/sendmail
> send-mail   /usr/local/sbin/sendmail
> mailq   /usr/local/sbin/sendmail
> newaliases  /usr/local/sbin/sendmail

similarly, but i am an exim bigot.

> It was still really annoying, though

thousands of people were denied the wisdom of my words for hours until i
noticed it.  :-)

> and at least UPDATING could have had an entry for it.

yup^2

randy


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: make.conf NO_SENDMAIL=true blown

[Chris Piazza]

On Wed, Jan 05, 2000 at 04:27:26PM -0800, Randy Bush wrote:
> my /etc/make.conf has NO_SENDMAIL=true
> 
> but current as of today is stomping on /usr/sbin/sendmail, /usr/bin/mailq,
> etc. all about /usr/sbin/mailwrapper.

Yeah, that bit me too but I forgot to post a message here.  I'm using
postfix and I just changed /etc/mail/mailer.conf to this:

sendmail/usr/local/sbin/sendmail
send-mail   /usr/local/sbin/sendmail
mailq   /usr/local/sbin/sendmail
newaliases  /usr/local/sbin/sendmail

It was still really annoying, though, and at least UPDATING could
have had an entry for it.

-Chris
-- 
[EMAIL PROTECTED]   [EMAIL PROTECTED]
Abbotsford, BC, Canada


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Warner Losh]

In message <[EMAIL PROTECTED]> Dennis Glatting writes:
: Stupid question: will the latest PAO stuff be integrated with 4.0?

Not as such no.  Like 3.x before, most of the PAO bits have been
merged, but much still remains in PAO that hasn't been integrated.
There will likely be a PAO4 while we trnasition to the new pccard
system.  At least that's my sense of things.  I'm not part of the PAO
team, so they may deside to do something different.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Yoshinobu Inoue]

> Will we try to include the remaining KAME IPv6 integration into 4.0 before
> the freeze?  It would be nice to have 4.0 with a functioning IPv6 stack and
> some applications.
> 
> louie

As an information from a person doing merging work,
  -Kernel part is almost done(tcp patch is under review and testing).
  -IPsec userland tools patch is also under review.
  -some more tcp and udp userland tools need to be added but I think
   it can be done including review time before 15th.
Then I think 4.0 will have some enough degree of IPv6 and
IPsec functionalities.

Some items won't make it until 15th,
  -IPv6 multicast routing
  -many IPv6 ports
But after 4.0 is released, KAME package for 4.0 release will
be also made, and I think it can provide those part and other
update for users who needs more intensive support for IPv6 and
IPsec.


Yoshinobu Inoue


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Dennis Glatting]

Stupid question: will the latest PAO stuff be integrated with 4.0?


-dpg
 S/MIME Cryptographic Signature

make.conf NO_SENDMAIL=true blown

[Randy Bush]

my /etc/make.conf has NO_SENDMAIL=true

but current as of today is stomping on /usr/sbin/sendmail, /usr/bin/mailq,
etc. all about /usr/sbin/mailwrapper.

randy


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Louis A. Mamakos]

> Louis A. Mamakos wrote:
> > 
> > Will we try to include the remaining KAME IPv6 integration into 4.0 before
> > the freeze?  It would be nice to have 4.0 with a functioning IPv6 stack and
> > some applications.
> 
> IPv6 is a very complex area and I believe that a -RELEASE should come with
> both a clean IPv6 stack and working userland tools.  When looking at
> Linux and Solaris, they also lack a usable IPv6 support when it comes
> to userland tools.
> 
> A lot of things need to be modified: ifconfig, route, ipfw, tcpd, ...
> and all the client/server tools you can find in /etc/inetd.conf
> 
> I doubt that IPv6 will make it into 4.0-RELEASE, but I'm sure it
> will be a major item for this year.

A large part of the integration has already been done.  The KAME IPv6 and
IPSEC code has been available for 3.2 and 3.3 for a while, and seems to be
pretty stable based on the testing I did a few weeks ago.  While there's been
a bunch of changes in the 4.0 kernel, I think adapted to the differences 
between
3.x and 4.x is the major challange rather than the IPSEC and IPv6 features
and functionality.

All the changes you mentioned (and more) already exist as patches to 3.3
from KAME.

Of course, I'm not doing the work, so my opinion on the difficulty doesn't
carry much authority..

louie

.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA atapi-all.c problems/fixes/cleanups

[Brian Fundakowski Feldman]

How about this?  It's mostly the changes in your patch, but it also takes
into account non-int{8,16}_t-sizing/alignment.  It also takes care of the
truncation problem when you use outsl and insl, as part of that.  Please
review it, as I think it should be the right thing to do.

-- 
 Brian Fundakowski Feldman   \  FreeBSD: The Power to Serve!  /
 [EMAIL PROTECTED]`--'


Index: atapi-all.c
===
RCS file: /usr2/ncvs/src/sys/dev/ata/atapi-all.c,v
retrieving revision 1.29
diff -u -r1.29 atapi-all.c
--- atapi-all.c 2000/01/03 10:26:56 1.29
+++ atapi-all.c 2000/01/05 23:37:27
@@ -552,23 +552,39 @@
*buffer = (int8_t *)&request->sense;
 
 if (request->bytecount < length) {
-   printf("%s: read data overrun %d/%d\n",
+   printf("%s: read data buffer too small (bs %d > buflen %d)\n",
   request->device->devname, length, request->bytecount);
 #ifdef ATA_16BIT_ONLY
insw(request->device->controller->ioaddr + ATA_DATA, 
-(void *)((uintptr_t)*buffer), length / sizeof(int16_t));
+(void *)*buffer, request->bytecount / sizeof(int16_t));
 #else
insl(request->device->controller->ioaddr + ATA_DATA, 
-(void *)((uintptr_t)*buffer), length / sizeof(int32_t));
+(void *)*buffer, request->bytecount / sizeof(int32_t));
+   if (request->bytecount & sizeof(int16_t)) {
+*(int16_t *)(*buffer + request->bytecount -
+   (sizeof(int16_t) + (request->bytecount & sizeof(int8_t =
+   inw(request->device->controller->ioaddr + ATA_DATA);
+length -= sizeof(int16_t);
+   }
 #endif
-   for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA);
+   if (request->bytecount & sizeof(int8_t)) {
+(*buffer)[request->bytecount - sizeof(int8_t)] =
+inb(request->device->controller->ioaddr + ATA_DATA);
+(void)inb(request->device->controller->ioaddr + ATA_DATA);
+length -= sizeof(int8_t);
+   }
+   resid = request->bytecount & ~(sizeof(int16_t) | sizeof(int8_t));
+   for (; resid < length; resid += sizeof(int16_t))
+(void)inw(request->device->controller->ioaddr + ATA_DATA);
+   *buffer += request->bytecount;
+   request->bytecount = 0;
 }  
-else
+else {
insw(request->device->controller->ioaddr + ATA_DATA,
-(void *)((uintptr_t)*buffer), length / sizeof(int16_t));
-request->bytecount -= length;
-*buffer += length;
+(void *)*buffer, length / sizeof(int16_t));
+   *buffer += length;
+   request->bytecount -= length;
+}
 }
 
 static void
@@ -581,23 +597,38 @@
*buffer = (int8_t *)&request->sense;
 
 if (request->bytecount < length) {
-   printf("%s: write data underrun %d/%d\n",
-  request->device->devname, length, request->bytecount);
+   printf("%s: write data underrun (buflen %d < bs %d), padding written\n",
+  request->device->devname, request->bytecount, length);
 #ifdef ATA_16BIT_ONLY
outsw(request->device->controller->ioaddr + ATA_DATA, 
- (void *)((uintptr_t)*buffer), length / sizeof(int16_t));
+ (void *)*buffer, request->bytecount / sizeof(int16_t));
 #else
outsl(request->device->controller->ioaddr + ATA_DATA, 
- (void *)((uintptr_t)*buffer), length / sizeof(int32_t));
+ (void *)*buffer, request->bytecount / sizeof(int32_t));
+   if (request->bytecount & sizeof(int16_t)) {
+   outw(request->device->controller->ioaddr + ATA_DATA,
+*(int16_t *)(*buffer + request->bytecount -
+(sizeof(int16_t) + (request->bytecount & sizeof(int8_t);
+   length -= sizeof(int16_t);
+   }
 #endif
-   for (resid=request->bytecount; residbytecount & sizeof(int8_t)) {
+   outb(request->device->controller->ioaddr + ATA_DATA,
+(*buffer)[request->bytecount]);
+   length -= sizeof(int8_t);
+   }
+   resid = request->bytecount & ~(sizeof(int16_t) | sizeof(int8_t));
+   for (; resid < length; resid += sizeof(int16_t))
 outw(request->device->controller->ioaddr + ATA_DATA, 0);
+   *buffer += request->bytecount;
+   request->bytecount = 0;
 }
-else
+else {
outsw(request->device->controller->ioaddr + ATA_DATA, 
- (void *)((uintptr_t)*buffer), length / sizeof(int16_t));
-request->bytecount -= length;
-*buffer += length;
+ (void *)*buffer, length / sizeof(int16_t));
+   *buffer += length;
+   request->bytecount -= length;
+}
 }
 
 static void 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

ATA driver problems

[Peter Jeremy]

Yesterday I updated from a pre-signal-change -current to something closer
to the present (cvs-cur 5961 - about last Monday, to be precise).

Every night, I run "dd if=/dev/rwdXc of=/dev/null bs=64k" on both of
my disks (I trim the output and merge it with a number of other
systems).  I forgot to update the wd to ad and last night it reported
errors.  I was expecting:

gsmx07:wd0:91746+1 records in
gsmx07:wd0:91746+1 records out
gsmx07:wd0:6012679680 bytes transferred
gsmx07:wd2:19561+1 records in
gsmx07:wd2:19561+1 records out
gsmx07:wd2:1281950208 bytes transferred

But instead I got:
gsmx07:wd0:dd: /dev/rwd0c: Invalid argument
gsmx07:wd0:91747+0 records in
gsmx07:wd0:91747+0 records out
gsmx07:wd0:6012731392 bytes transferred
gsmx07:wd2:dd: /dev/rwd2c: Input/output error
gsmx07:wd2:19561+0 records in
gsmx07:wd2:19561+0 records out
gsmx07:wd2:1281949696 bytes transferred

At about the same time, the following message appeared in /var/log/messages:
/kernel: ad2: HARD READ ERROR blk# 2503871
/kernel: ad2: HARD READ ERROR blk# 2503871 status=59 error=10
/kernel: ad2: DMA problem encountered, fallback to PIO mode

I just tried repeating it with ad0 instead of wd0 and got the same thing.
I don't want to repeat it with ad2 since there doesn't appear to be any
way to re-enable DMA short of rebooting [or maybe that patch hasn't
arrived here yet].

This suggests that there are two separate problems:
1) An I/O request for a block that entends beyond the end of the physical
   slice will abort with EINVAL, rather than returning a partial block.
2) There seems to be an off-by-1 error in the size reported by my
   Fireball (or maybe in the request handling), causing it to report
   an I/O error on the last sector.

The first problem would seem to be a bug in the ata driver, since the
behaviour on other Unices is to return a partial block.  (And this
might be related to the difficulties Brian Feldman is reporting).

I'm not sure about the second problem - all I can say if that the wd
driver saw the same number of sectors and the bytes read from the disk
matches the number of sectors in the slices.

Does anyone have any ideas?

The disk-related probe messages are:

ata-pci0:  at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
...
ata-isa0: already registered as ata0
ata-isa1: already registered as ata1
...
ad0:  ATA-3 disk at ata0 as master
ad0: 6187MB (12672450 sectors), 13410 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, UDMA33
ad2:  ATA-0 disk at ata1 as master
ad2: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S
ad2: 16 secs/int, 1 depth queue, DMA
acd0:  CDROM drive at ata0 as slave 
acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA
acd0: Reads: CD-R, CD-RW, CD-DA stream
acd0: Audio: play, 16 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked

ad0 has two active slices, the FreeBSD one is the second and is 11743515
sectors. ad2 is dedicated (not dangerously) to FreeBSD and the slice is
2503809 sectors.

Peter
--
Peter Jeremy (VK2PJ)[EMAIL PROTECTED]
Alcatel Australia Limited
41 Mandible St  Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015   Fax:   +61 2 9690 5982


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: unwanted Vinum partition fsck'ing when booting

[Thierry Herbelot]

Mark Newton wrote:
> 
> On Wed, Jan 05, 2000 at 11:44:44PM +0100, Thierry Herbelot wrote:
> 
>  > On my SMP box, I've set up a striped Vinum partition. Not wanting to
>  > mount it each time I boot, I've included a "placeholder" in fstab to get
>  > it known, but without it getting mounted at boot-up.
> 
> Uh huh -- But you've specified a non-zero fsck pass number in the fstab
> entry.  Change this:
> 
>  > /dev/vinum/initial  /files1 ufs rw,noauto   2  2
> 
> to this:
> 
> /dev/vinum/initial  /files1 ufs rw,noauto   2 0

done ! (and it now works "as advertised")

(but my /files3 line was identical and /ad4s2e was not fsck'ed)
/dev/ad4s2e /files3 ufs rw,noauto  2   2

Strange

TfH


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: error messages while loading the kernel

[Robert C. Noland III]

So it was, it now shows up in:

vinum/vinum.ko
 U zfree

BTW, this seems to be the only module referencing this symbol at the
moment.

robert.

Mark Newton writes:
>On Wed, Jan 05, 2000 at 05:49:44PM -0500, Robert C. Noland III wrote:
>
> > I have seen that as well... It seems to be caused by svr4_enable="YES" 
> > in rc.conf.  or rather the specified module.
>
>FWIW, this was fixed in rev 1.10 of svr4_sysvec.c
>
>- mark
>
>-- 
>Mark Newton   Email:  [EMAIL PROTECTED] (W)
>Network Engineer  Email:  [EMAIL PROTECTED]  (H)
>Internode Systems Pty Ltd Desk:   +61-8-82232999
>"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: unwanted Vinum partition fsck'ing when booting

[Mark Newton]

On Wed, Jan 05, 2000 at 11:44:44PM +0100, Thierry Herbelot wrote:

 > On my SMP box, I've set up a striped Vinum partition. Not wanting to
 > mount it each time I boot, I've included a "placeholder" in fstab to get
 > it known, but without it getting mounted at boot-up.
 
Uh huh -- But you've specified a non-zero fsck pass number in the fstab
entry.  Change this:

 > /dev/vinum/initial  /files1 ufs rw,noauto   2  2

to this:

/dev/vinum/initial  /files1 ufs rw,noauto   2 0

   - mark

-- 
Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: error messages while loading the kernel

[Mark Newton]

On Wed, Jan 05, 2000 at 05:49:44PM -0500, Robert C. Noland III wrote:

 > I have seen that as well... It seems to be caused by svr4_enable="YES" 
 > in rc.conf.  or rather the specified module.

FWIW, this was fixed in rev 1.10 of svr4_sysvec.c

- mark

-- 
Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: error messages while loading the kernel

[Thierry Herbelot]

"Robert C. Noland III" wrote:
> 
> I have seen that as well... It seems to be caused by svr4_enable="YES"
> in rc.conf.  or rather the specified module.
> 

I'd say any module :
multi% kldstat
Id Refs AddressSize Name
 12 0xc010 1c4b58   kernel
 41 0xc1155000 2000 blank_saver.ko
multi% 

I don't use the svr4 emulation 

TfH

> robert.
> 
> Thierry Herbelot writes:
> >I've just remade the world and a new kernel with sources supped around
> >21h00 GMT today, and I've got error messages in the kernel loading phase
> >(on an SMP machine : bi-celeron BP6)
> >
> >link_elf: symbol zfree undefined
> >link_elf: symbol zfree undefined
> >
> >
> >
> >FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0:
> >Wed Jan  5 23:15:23 CET 2000
> >[EMAIL PROTECTED]:/usr/src/sys/compile/multi  i386
> >
> >
> >To Unsubscribe: send mail to [EMAIL PROTECTED]
> >with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

error messages while loading the kernel

[Robert C. Noland III]

I have seen that as well... It seems to be caused by svr4_enable="YES" 
in rc.conf.  or rather the specified module.

robert.

Thierry Herbelot writes:
>I've just remade the world and a new kernel with sources supped around
>21h00 GMT today, and I've got error messages in the kernel loading phase
>(on an SMP machine : bi-celeron BP6)
>
>link_elf: symbol zfree undefined
>link_elf: symbol zfree undefined
>
>
>
>FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0: 
>Wed Jan  5 23:15:23 CET 2000 
>[EMAIL PROTECTED]:/usr/src/sys/compile/multi  i386
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS-UP newppbus for beta-testing

[Maxim Sobolev]

Nicolas Souchu wrote:

> On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote:
> >
> >Nicolas Souchu wrote:
> >
> >> Hi there!
> >>
> >> FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current
> >>
> >> A major ppbus(4) release is available for beta-testing.
> >
> >Good work! Now plip, which has been broken for ages, works perfectly - no more
> >lockups, spontaneous reboots, panics, etc! To test it I even managed to get X
> >and NFS working over plip line, things which was impossible with oldppbus.
>
> Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration)
> in you MACHINE config file would have done the job.

Unfortunately it is not a solution because net,tty and bio keywords went away from
config(8) long time ago... I've only received `syntax error' message.

-Maxim




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

unwanted Vinum partition fsck'ing when booting

[Thierry Herbelot]

Hello,

On my SMP box, I've set up a striped Vinum partition. Not wanting to
mount it each time I boot, I've included a "placeholder" in fstab to get
it known, but without it getting mounted at boot-up.

/dev/vinum/initial  /files1 ufs rw,noauto   2  
2
herbie2:/files2 /files2 nfs rw
/dev/ad4s2e /files3 ufs rw,noauto   2  
2
/dev/ad4s1b /usr/objmfs rw  0  
0

This evening, with freshly supped sources (got around 21h00 GMT,
followed by a "make world"), my new kernel insists it wants to fsck the
/files1 partition, even if it is not to be mounted.

I then have to comment out the /files1 line in /etc/fstab while in
single-user mode : no joy

the /files3 has absolutely no trouble, it stays un-mounted and
un-fsck'ed

TfH


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

error messages while loading the kernel

[Thierry Herbelot]

I've just remade the world and a new kernel with sources supped around
21h00 GMT today, and I've got error messages in the kernel loading phase
(on an SMP machine : bi-celeron BP6)

link_elf: symbol zfree undefined
link_elf: symbol zfree undefined



FreeBSD multi.herbelot.nom 4.0-CURRENT FreeBSD 4.0-CURRENT #0: 
Wed Jan  5 23:15:23 CET 2000 
[EMAIL PROTECTED]:/usr/src/sys/compile/multi  i386


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

unknown*:*

[Alexey Zelkin]

hi,

I just updated my -CURRENT, compiled kernel with PNPBIOS
and found a lot of unknown items in dmesg output. Should I
submit my PNP devices IDs ? And who is PNP related part maintainer ?

PS: Also I got strange error about `device slot allocation' for acd0. What the
trouble I got ? As I understand it's something related to DEVFS.

Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #3: Mon Jan  3 11:36:10 MSK 2000
[EMAIL PROTECTED]:/usr/src/HEAD/src/sys/compile/SPIDER
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Celeron (334.09-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x660  Stepping = 0
  
Features=0x183f9ff
real memory  = 67108864 (65536K bytes)
avail memory = 61665280 (60220K bytes)
Preloaded elf kernel "kernel" at 0xc0339000.
DEVFS: ready for devices
VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc00c0e38 (ce38)
VESA: S3 Incorporated Trio3D.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0:  on motherboard
npx0: INT 16 interface
apm0:  on motherboard
apm: found APM BIOS v1.2, connected at v1.2
pcib0:  on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
vga-pci0:  at device 0.0 on pci1
isab0:  at device 7.0 on pci0
isa0:  on isab0
ata-pci0:  at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 10
chip1:  at device 7.3 on pci0
ed0:  irq 12 at device 9.0 on pci0
ed0: supplying EUI64: 00:00:21:ff:fe:c7:5b:a7
ed0: address 00:00:21:c7:5b:a7, type NE2000 (16 bit) 
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
fdc0:  at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
unknown:  can't assign resources
unknown0:  at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 
on isa0
unknown1:  at port 0x40-0x43 irq 0 on isa0
unknown2:  at port 0x70-0x71 irq 8 on isa0
unknown:  can't assign resources
unknown:  can't assign resources
unknown3:  at port 0xf0-0xff irq 13 on isa0
unknown4:  at iomem 0-0x9,0xfffe-0x,0x10-0x3ff on isa0
unknown5:  at iomem 
0xf-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xf on isa0
unknown6:  at port 
0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f,0x4000-0x403f,0x5000-0x501f on isa0
unknown7:  at port 0x208-0x20f on isa0
unknown:  can't assign resources
unknown:  can't assign resources
unknown8:  at port 0x378-0x37f irq 7 on isa0
unknown:  can't assign resources
pcm0:  at port 
0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0
unknown9:  at port 0x201 on isa0
unknown10:  at port 0x100-0x107 on isa0
unknown11:  at port 0x1e0-0x1e7,0x3e6 irq 11 on isa0
DEVFS: ready to run
ad0:  ATA-4 disk at ata0 as master
ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, UDMA33
Device acd0a: name slot allocation failed (Errno=17)
  ^^
Device acd0c: name slot allocation failed (Errno=17)
  ^^
acd0: <24X CD-ROM/VER 1.0E> CDROM drive at ata0 as slave 
acd0: read 687KB/s (3093KB/s), 128KB buffer, UDMA33
acd0: Reads: CD-DA stream
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
Mounting root from ufs:/dev/wd0s1a
ed0: starting DAD for fe80:0001::0200:21ff:fec7:5ba7
ed0: DAD complete for fe80:0001::0200:21ff:fec7:5ba7 - no duplicates found

-- 
/* Alexey Zelkin   && [EMAIL PROTECTED]*/
/* Tavric National University  && [EMAIL PROTECTED]  */
/* http://www.ccssu.crimea.ua/~phantom && [EMAIL PROTECTED] */


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

upgrade 3.3REL -> 4.0

[Joao Pedras]

Hello all!

On the 2nd on January I made a fresh install of a 3.3-REL. On that same day I
updated its /usr/src to 4.0-CURRENT. I went through a process(almost trivial to
me, trivial for you guys) that took sometime. On the 3rd the machine was fully
running -CURRENT.
I made this rehearsal because I have a dozen must-be-online that in due time,
will be running 4.0.

I remember last years 'version-rush', scripts and whatever, to upgrade everyone
to 3.0. Some made it with success, some not.

Thanks to the great job FreeBSD's team has been doing, more and more people are
running FreeBSD on very serious environments/bussinesses and gladly, not
everyone needs to be a 15 year-old Unix hacker to command the troops.

What are your plans regarding the upgrading procedure this year ? Will it be
easy to upgrade to the 4.0-REL from 3.4(5) with scripts ? 

Joao


  ^\   /^
O O
o00-(_)-00o--

This sentence contradicts itself -- no actually it doesn't.
-- Hofstadter

-
PGP key available upon request or may be cut at 
http://pedras.webvolution.net/pgpkey.html



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: 4.0 code freeze scheduled for Jan 15th

[Waite, Michael]

What kind of an Alpha would you like?

Mike

Michael Waite
Global Partnering Solutions, Marlboro Center
Compaq Computer Corporation
TEL: (508)467-2289
EMAIL: [EMAIL PROTECTED]

> --
> From: Jordan K. Hubbard[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Wednesday, January 05, 2000 2:44 PM
> To:   [EMAIL PROTECTED]
> Cc:   [EMAIL PROTECTED]
> Subject:  4.0 code freeze scheduled for Jan 15th
> 
> And given that we've already slipped from December 15th, I think you
> can treat this as a pretty hard deadline, to be further slipped only
> grudgingly and in response to clear and dire need.
> 
> 10 days, folks!  Make 'em count.. :)
> 
> The code freeze will last for 15 days, during which time the 4.0
> snapshot server (current.freebsd.org) will be cranking out its daily
> snapshots (and, in the last half of the release cycle, ISO images as
> well).  There will be an additional 10 days following 4.0-RELEASE
> before the final CD images are made, it being our goal to get the bugs
> worked out of the net release before the CDs are made in the future.
> This will result in some additional lag to CD customers, but they'll
> also get a product with the sharp edges filed off in return for the
> delay and I think it's worth-while since CDs are a lot harder to
> update than FTP sites. :-)
> 
> If someone would care to volunteer an Alpha which has good network
> connectivity and enough "oomph" to create a full release every night,
> I'd also be happy to drag the Alpha architecture into this process of
> doing some actual release QA by porting my snapshot building scripts
> over and starting them up.
> 
> - Jordan
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Christian Kuhtz]

On Wed, Jan 05, 2000 at 09:39:30PM +0100, Kai Voigt wrote:
> > Will we try to include the remaining KAME IPv6 integration into 4.0 before
> > the freeze?  It would be nice to have 4.0 with a functioning IPv6 stack and
> > some applications.
> 
> IPv6 is a very complex area and I believe that a -RELEASE should come with
> both a clean IPv6 stack and working userland tools.  When looking at
> Linux and Solaris, they also lack a usable IPv6 support when it comes
> to userland tools.

Really.  IPv6 code is in the 2.2 release & 2.3 development kernels (albeit
flagged as experimental).  And works quite well, and is being used on the 
6bone and other IPv6 testbeds.  

So, what exactly do you mean with your statement?  Would you care to qualify
your remark?

I don't consider it fair to throw Solaris into the mix isn't fair because it's 
a different beast considering the availability and maintenance of the source.
You're comparing apples with oranges here.

Nobody expects IPv6 to be particularly pretty, but it needs to make it into the
regular tree.  Why not for the 4.0 release.  For example, Cisco's IPv6 IOS
train isn't pretty, but it works.  And has been brought up to their most 
current code train almost a year ago, if I recall correctly.

If it doesn't get in now, it will be a very long time before a major release
will come about.  And it's not going to get any prettier if nobody has exposure
to it.

> I doubt that IPv6 will make it into 4.0-RELEASE, but I'm sure it
> will be a major item for this year.

I think that's not good enough.  Nobody says it has to be turned on by default,
but it needs to make it into the train as a regular component to allow it to
get more exposure.

Cheers,
Chris

--
Christian Kuhtz Architecture, BellSouth.net
<[EMAIL PROTECTED]> -wk, <[EMAIL PROTECTED]> -hm   Atlanta, GA
"Speaking for myself only."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Kelly Yancey]

On Wed, 5 Jan 2000, Jordan K. Hubbard wrote:

> And given that we've already slipped from December 15th, I think you
> can treat this as a pretty hard deadline, to be further slipped only
> grudgingly and in response to clear and dire need.
> 
> 10 days, folks!  Make 'em count.. :)
> 

  I don't suppose there is any chance that kern/15251 might be closed
before then. It adds unsigned support to sysctl(8) so it doesn't report
bogus numbers. It's just a minor detail, but it wouldn't take but a moment
to fix. I'de commit it myself, but... ;)

  Kelly

--
Kelly Yancey  -  [EMAIL PROTECTED]  -  Richmond, VA
Analyst / E-business Development, Bell Industries  http://www.bellind.com/
Maintainer, BSD Driver Database   http://www.posi.net/freebsd/drivers/
Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: date(1) and -v-1m

[Alexander Langer]

Thus spake Brian Somers ([EMAIL PROTECTED]):

> > Do we want an additional option? (I want :-))
> I certainly wouldn't object to -V doing the same as -v but rounding 
> down this could also decide how to behave when a -v adjusts the 
> time onto a non-existent time (say 1:30 when the clocks go forward).

Ok. I start work :-)

Alex

-- 
I doubt, therefore I might be. 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Kai Voigt]

Louis A. Mamakos wrote:
> 
> Will we try to include the remaining KAME IPv6 integration into 4.0 before
> the freeze?  It would be nice to have 4.0 with a functioning IPv6 stack and
> some applications.

IPv6 is a very complex area and I believe that a -RELEASE should come with
both a clean IPv6 stack and working userland tools.  When looking at
Linux and Solaris, they also lack a usable IPv6 support when it comes
to userland tools.

A lot of things need to be modified: ifconfig, route, ipfw, tcpd, ...
and all the client/server tools you can find in /etc/inetd.conf

I doubt that IPv6 will make it into 4.0-RELEASE, but I'm sure it
will be a major item for this year.

Kai

-- 
kai voigt   hamburger chaussee 36
   24113 kiel
  04 31 - 22 19 98 69
http://k.123.org/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Christian Kuhtz]

On Wed, Jan 05, 2000 at 03:26:00PM -0500, Louis A. Mamakos wrote:
> 
> Will we try to include the remaining KAME IPv6 integration into 4.0 before
> the freeze?  It would be nice to have 4.0 with a functioning IPv6 stack and
> some applications.

I second that desire.

Cheers,
Chris

-- 
Christian Kuhtz Architecture, BellSouth.net
<[EMAIL PROTECTED]> -wk, <[EMAIL PROTECTED]> -hm   Atlanta, GA
"Speaking for myself only."


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Louis A. Mamakos]

Will we try to include the remaining KAME IPv6 integration into 4.0 before
the freeze?  It would be nice to have 4.0 with a functioning IPv6 stack and
some applications.

louie



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: 4.0 code freeze scheduled for Jan 15th

[Matthew Dillon]

Hallelujah!

Guys, lets try to make this the most stable .0 release ever!

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

4.0 code freeze scheduled for Jan 15th

[Jordan K. Hubbard]

And given that we've already slipped from December 15th, I think you
can treat this as a pretty hard deadline, to be further slipped only
grudgingly and in response to clear and dire need.

10 days, folks!  Make 'em count.. :)

The code freeze will last for 15 days, during which time the 4.0
snapshot server (current.freebsd.org) will be cranking out its daily
snapshots (and, in the last half of the release cycle, ISO images as
well).  There will be an additional 10 days following 4.0-RELEASE
before the final CD images are made, it being our goal to get the bugs
worked out of the net release before the CDs are made in the future.
This will result in some additional lag to CD customers, but they'll
also get a product with the sharp edges filed off in return for the
delay and I think it's worth-while since CDs are a lot harder to
update than FTP sites. :-)

If someone would care to volunteer an Alpha which has good network
connectivity and enough "oomph" to create a full release every night,
I'd also be happy to drag the Alpha architecture into this process of
doing some actual release QA by porting my snapshot building scripts
over and starting them up.

- Jordan


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: HEADS-UP newppbus for beta-testing

[Nicolas Souchu]

On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote:
>
>Nicolas Souchu wrote:
>
>> Hi there!
>>
>> FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current
>>
>> A major ppbus(4) release is available for beta-testing.
>
>Good work! Now plip, which has been broken for ages, works perfectly - no more
>lockups, spontaneous reboots, panics, etc! To test it I even managed to get X
>and NFS working over plip line, things which was impossible with oldppbus.

Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration)
in you MACHINE config file would have done the job.

>
>Count on my vote to commit it before branch split because IMHO it should be
>considered as a bugfix rather that a new feature.
>
>-Maxim
>

Nicholas

-- 
[EMAIL PROTECTED] / [EMAIL PROTECTED]
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Boot serial console all blanks

[Archie Cobbs]

Warner Losh writes:
> : The 2nd and 3rd stage boot loader output to the serial port is all
> : blanks.  That is, every character is output as a blank -- you can
> : see them printing, and see the 10 second autoboot messages, but
> : they're all space characters.
> 
> I have seen this when I've had the baud rate wrong.  On my development
> box that has a serial console, I seem to recall that I needed to build
> special bootblocks to run at 115200.
> 
> Try connecting a serial line analyser to the line if you have it.  Or
> a oscope will do in a pinch.  Or try the default baud rate of 9600.

I am doing 9600 baud..  also, this is a slightly abnormal setup,
using the old boot0/boot1 bootblocks (because it's an InterJet)
with /kernel hardlinked to 3.4-REL /boot/loader (so I can boot an ELF
kernel).

The old bootblocks print normally, then /boot/loader prints all spaces,
then when the kernel itself boots it prints normally again.  Everything
seems to be printing at the same baud rate (9600).

Maybe the old boot blocks are confusing the loader in the way they
are configuring the serial port.. ?

-Archie

___
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Boot serial console all blanks

[Warner Losh]

In message <[EMAIL PROTECTED]> Archie Cobbs writes:
: The 2nd and 3rd stage boot loader output to the serial port is all
: blanks.  That is, every character is output as a blank -- you can
: see them printing, and see the 10 second autoboot messages, but
: they're all space characters.

I have seen this when I've had the baud rate wrong.  On my development
box that has a serial console, I seem to recall that I needed to build
special bootblocks to run at 115200.

Try connecting a serial line analyser to the line if you have it.  Or
a oscope will do in a pinch.  Or try the default baud rate of 9600.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Boot serial console all blanks

[Jim Shankland]

Archie Cobbs <[EMAIL PROTECTED]> writes:

> The 2nd and 3rd stage boot loader output to the serial port
> is all blanks.  That is, every character is output as a
> blank -- you can see them printing, and see the 10 second
> autoboot messages, but they're all space characters.

Sorry, I'm drawing a blank.

(Carry on; moment of weakness.)

Jim Shankland
NLynx Systems, Inc.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Boot serial console all blanks

[Archie Cobbs]

Has anyone else seen this problem?

The 2nd and 3rd stage boot loader output to the serial port is all
blanks.  That is, every character is output as a blank -- you can
see them printing, and see the 10 second autoboot messages, but
they're all space characters.

Thanks for any insights.

-Archie

___
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[William Woods]

Here is the pccard.conf entry:

# 3Com Fast Etherlink 3C574TX
card "3Com" "Megahertz 574B"
config  0x1 "ep0" ? 0x1
insert  echo 3Com Fast Etherlink 3C574B inserted
insert  /etc/pccard_ether ep0
remove  echo 3Com Fast Etherlink 

This is on a 3.4 -stable system


On 05-Jan-00 Warner Losh wrote:
> In message <[EMAIL PROTECTED]> will andrews
> writes:
>: I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that
>: is
> 
> What does your pccard.conf entry look like for it?
> 
> Warner


--
E-Mail: William Woods <[EMAIL PROTECTED]>
Date: 05-Jan-00
Time: 10:23:02
FreeBSD 3.4 
--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[Warner Losh]

In message <[EMAIL PROTECTED]> will andrews writes:
: I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that is

What does your pccard.conf entry look like for it?

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: options COMPAT_LINUX makes kernel fail to compile

[Peter Wemm]

David Scheidt wrote:
> On Wed, 5 Jan 2000, Michael Lucas wrote:
> 
> > Hello,
> > 
> > Not that this is an actual fix to the problem, but:
> > 
> > The COMPAT_LINUX kernel option isn't needed any more, per Marcel.  (At
> > least, when I wrote an article on this, it wasn't.)  You can probably
> > remove COMPAT_LINUX entirely.
> 
> I use COMPAT_LINUX because I make kernels more frequently then I make world
> or modules.  I get fewer panics that way.
> 
> David Scheidt

You should definately use a static kernel without modules if you are
tracking -current and rebuilding regularly.  It is too easy to shoot
yourself in the foot by getting /modules and the kernel out of sync while
the internal interfaces are still changing.

Using kld's to develop drivers is different.

Cheers,
-Peter




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rlogin from 3.X to 4.0 problem...

[Udo Schweigert]

On Wed, Jan 05, 2000 at 18:33:40 +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Luigi Rizzo writes:
> >With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine:
> >
> > > rlogin bsd4
> > assword:hey this is great!
> >
> >why is the initial 'P' missing, and the password echoed ?
> 
> Bug in /etc/pam.conf
> 

Fixed with pam.conf version 1.4.

Regards
---
Udo Schweigert  || Voice  : +49 89 636 42170
Siemens AG, Siemens CERT|| Fax: +49 89 636 41166
ZT IK 3 || email  : [EMAIL PROTECTED]
D-81730 Muenchen / Germany  ||: [EMAIL PROTECTED]
PGP fingerprint || 2A 53 F6 A6 30 59 64 02  6B C4 E0 73 B2 C9 6C E7
---


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[Warner Losh]

In message <[EMAIL PROTECTED]> "Matthew N. Dodd" 
writes:
: Anyone know of a PCI Cardbus bridgeboard?  I'd rather not have to get a
: laptop just so I can play with cardbus.

I've seen two, both of which seem to be unavailable.  One is at a URL
that I've lost and the other was made by compaq and was available for
their desktop machines.  CDW used to carry this, but it is unavailable
now as well.  I'll have to dig up the URL that I've lost (it is in my
netscape history file, I'm sure) since they talked about availablities
after the first of the year which is why I blew them off before (it
was in October or so I was looking).  I'll send you something if I can
find it.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problem with rlogin and /etc/pam.conf

[Udo Schweigert]

On Tue, Jan 04, 2000 at 08:10:24 +0200, Mark Murray wrote:
> > My work around to this problem is to add the following line to /etc/pam.conf,
> > rshdauthsufficient  pam_deny.so
> 
> What timing! I just committed something that looks identical!
> 

Great. That fixed it for me.

Also I think this should be considered for MFC since the /etc/pam.conf from 
-current works for me under -stable and makes XFree86 with PAM support working.

Regards
---
Udo Schweigert  || Voice  : +49 89 636 42170
Siemens AG, Siemens CERT|| Fax: +49 89 636 41166
ZT IK 3 || email  : [EMAIL PROTECTED]
D-81730 Muenchen / Germany  ||: [EMAIL PROTECTED]
PGP fingerprint || 2A 53 F6 A6 30 59 64 02  6B C4 E0 73 B2 C9 6C E7
---


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: rlogin from 3.X to 4.0 problem...

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, Luigi Rizzo writes:
>With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine:
>
>   > rlogin bsd4
>   assword:hey this is great!
>
>why is the initial 'P' missing, and the password echoed ?

Bug in /etc/pam.conf

I belive markm is on the case.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

rlogin from 3.X to 4.0 problem...

[Luigi Rizzo]

With the 991229 shapshot, from a FreeBSD 3.3 or 3.4 machine:

> rlogin bsd4
assword:hey this is great!

why is the initial 'P' missing, and the password echoed ?

cheers
luigi
---+-
  Luigi RIZZO, [EMAIL PROTECTED]  . Dip. di Ing. dell'Informazione
  http://www.iet.unipi.it/~luigi/  . Universita` di Pisa
  TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
  Mobile   +39-347-0373137
---+-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[Warner Losh]

In message <[EMAIL PROTECTED]> Frank Mayhar writes:
: He's got both the card and the documentation, courtesy of Terry Murphy at
: 3Com and my efforts to that end.

Cool.

: > I have a 3CCFE575CT sitting here on my desk right now as a gentile
: > reminder to work on pccard/cardbus stuff :-).
: 
: Is that one that Matt sent you?  If so, that's the result of the same effort.
: Else Matt has one, too.

No.  FreeBSD Inc and/or Walnut creek bought mine.  I'll keep your name 
in mind if I need any docs for it.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Proposal: Removing doscmd from the source tree...

[Oliver Fromme]

Michael Lucas <[EMAIL PROTECTED]> wrote in list.freebsd-current:
 > Actually, several ports give you the option of building with or
 > without X support (i.e., SSH).  It would be nice to have a USE_X11
 > option in /etc/make.conf for doscmd as well as these ports, so you
 > don't have to specify it on the command line while building.
 > 
 > Of course, I'd like a pony too.  And a pink bike shed.

Me too!  :)

I'm currently trying to fix the POV-Ray port.  It could be
built with and without X11 support, too, and it would be very
useful to have a way to let the user choose.  A USE_X11 knob
in make.conf would be great.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[will andrews]

On 05-Jan-00 William Woods wrote:
> ok, now...to get it working...
> 
> ideas?

I am currently using a 3Com 3CCFE574BT with 4.0-CURRENT here. Mind you, that is
4.0-CURRENT as of September 29, right before Matt Dodd's if_ep.c commit that
moved towards newcard implementation.

You will not be able to use it on any later version of 4.0-CURRENT as far as I
know. And I know it does not work with 3.3-RELEASE. You may have better luck
with 3.4-RELEASE, but I wouldn't know.

/me waits for Matt to fix if_ep *patiently* ;-)

I know it's coming soon. *twiddle thumbs*

--
Will Andrews <[EMAIL PROTECTED]>
GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w---
?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ 
G++>+++ e-> h! r-->+++ y?


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: options COMPAT_LINUX makes kernel fail to compile

[David Scheidt]

On Wed, 5 Jan 2000, Michael Lucas wrote:

> Hello,
> 
> Not that this is an actual fix to the problem, but:
> 
> The COMPAT_LINUX kernel option isn't needed any more, per Marcel.  (At
> least, when I wrote an article on this, it wasn't.)  You can probably
> remove COMPAT_LINUX entirely.

I use COMPAT_LINUX because I make kernels more frequently then I make world
or modules.  I get fewer panics that way.

David Scheidt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: options COMPAT_LINUX makes kernel fail to compile

[Kenneth Wayne Culver]

Well, just make sure that you load the linux compatibility kernel module
though.


=
| Kenneth Culver  | FreeBSD: The best OS around.|
| Unix Systems Administrator  | ICQ #: 24767726 |
| and student at The  | AIM: AgRSkaterq |
| The University of Maryland, | Website: (Under Construction)   |
| College Park.   | http://www.wam.umd.edu/~culverk/|
=

On Wed, 5 Jan 2000, Michael Lucas wrote:

> Hello,
> 
> Not that this is an actual fix to the problem, but:
> 
> The COMPAT_LINUX kernel option isn't needed any more, per Marcel.  (At
> least, when I wrote an article on this, it wasn't.)  You can probably
> remove COMPAT_LINUX entirely.
> 
> (If only the rest of the problems were this easy.  :)
> 
> ==ml
> 
> > Hi!
> > 
> > With option COMPAT_LINUX (which present in LINT) make depend fails with:
> > cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
> > -fformat-extensions -ansi  -nostdinc -I- -I. -I../.. -I../../../include
> > -D_KERNEL -include opt_global.h -elf -fno-builtin
> > -mpreferred-stack-boundary=2  -UKERNEL -o linux_genassym.o -c
> > ../../i386/linux/linux_genassym.c
> > genassym -o linux_assym.h linux_genassym.o
> > genassym:No such file or directory
> > *** Error code 1 
> > 
> > Dmitry.
> > 
> > 
> > 
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> > 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA))

[Nick Hibma]

> > and I apologise for wrongfully accusing it.   The panic is in fact
> > caused by newpcm (Cameron CC'd).  DDB trace can be provided upon request
> > (is there a way to save it into a file instead of having to write it
> > down on a piece of paper?)
> 
> Sure. Hook up serial console or some terminal program to appropriate
> serial port using null-modem cable, then rebuild your kernel and boot
> with right flag. Look at sys/i386/LINT, man sio(4) and man boot(8).

Or, if the panic happens after rc.conf has been run / you can log in,
set the dump device to something sensible. From DDB type panic. When the
system boots up again, you type savecore /some/dir and possibly copy the
debugging kernel from /sys/compile/KERNELNAME to /some/dir/kernel.0 as
well.


Nick

--
[EMAIL PROTECTED]
[EMAIL PROTECTED]  USB project
http://www.etla.net/~n_hibma/



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[Matthew N. Dodd]

On Wed, 5 Jan 2000, Frank Mayhar wrote:
> > I have a 3CCFE575CT sitting here on my desk right now as a gentile
> > reminder to work on pccard/cardbus stuff :-).
> 
> Is that one that Matt sent you?  If so, that's the result of the same
> effort. Else Matt has one, too.

I offered him mine but he said he already had one.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ifq_maxlen in vx-driver

[Matthew N. Dodd]

On Wed, 5 Jan 2000, Oliver Schonefeld wrote:
> i am using the vx driver in for my two 3c397 boards.
> when booting i get the following message:
> 
> vx0 XXX: driver didn't set ifq_maxlen
> 
> obviosly the ifq_maxlen is not set in the eisa nor in the pci version
> in the driver. actually, to set this, would be one line in the driver,
> but unfrotunatly i am not that familiar with the hardware, and do not
> know, which value this parameter shoul have. maybe, someone knows ...

This is just a warning message; it doesn't hurt anything.

I'll deal with if_vx at some point; it will get fixed with if_ed and if_vx
get collided at high speed.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

HEADS UP: Crossbuilding world

[Marcel Moolenaar]

Hi,

After a couple of weeks (or is it months already) of reorganizing the
build process, I've come to the point where I can say that I'm ready --
well, sort of. I'm cross-building with two patches that are in the
pipeline of being committed. I've made the patches available for those
who can't or won't wait for the patches (or equivalent fixes) to be
committed:
http://www.freebsd.org/~marcel/crossbuild.diff

NOTE: gnu/usr.bin/cc/cc_tools/Makefile also needs to be fixed. It
creates the wrong dependencies which breaks a buildworld with -DNOCLEAN
at the moment. The workaround is to remove the '.depend' file in the
object directory before starting the buildworld.

Of course this doesn't mean that when that is fixed, I'm finished. At
least the following tasks still need to be done:

o  Finish cross-building kernels.
o  Fix installworld so that it doesn't execute any of the binaries
   previously installed. This solves the upgrade problem in which
   the kernel isn't capable (yet) of running the binaries.
o  Create a 'kernel' target to make kernels. This target is to be
   used by the upgrade process.
o  Redefine the current 'upgrade' target to make world and kernel,
   followed by an install for world and kernel. It ends with a
   reboot.

This roughly describes what I'm going to do next wrt to the build
process. If you think I should be doing things differently, this is the
time to speak up... preferably with diffs :-)

\begin{talking to myself}
I have to finish those linux ports and PRs as well. Not to forget mumble
mumble, especially mumble mumble mumble...
\end{mumble mumble}

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

making release

[Alexandr Listopad]

thanks...

marc.s>Have a look at :
marc.s>
marc.s>http://www.external.org/freebsd/current.html
marc.s>
marc.s>Worked fine for me.

...but it not what do I mean... I need to make RELEASE (ftp-like).
I know that I need a FULL CVS tree as handbook wrote:

---
  Second, you have to have the whole CVS repository at hand. To get this
^^^
  you can use CVSUP but in your supfile set the release name to cvs and
  remove any tag or date fields:
---

but it is so difficult for me (14.4Kbit/s - our I-net... ;/)

Did there anybody who can help me?

I have full src-es, cvsuped today. My configs is:

*default  host=cvsup2.ua.freebsd.org
*default  base=/usr
*default  prefix=/usr
*default  release=cvs
*default  tag=RELENG_3
*default  delete use-rel-suffix

doc-all
src-base
src-bin
src-contrib
src-etc
src-gnu
src-include
src-lib
src-libexec
src-release
src-sbin
src-share
src-sys
src-usrbin
src-usrsbin


As you can see I have not all sources... Did it wrong for making
release? Did I certainly need

src-all
src-secure
src-eBones 

for making release? Can I make my custom release?

Is there another way for making release? Because a "have to have the whole
CVS repository at hand" VERY difficult for me.

Please... help me!

Thanks.

Regards,
  Listopad Alexandr
  ([EMAIL PROTECTED]), LAA7-RIPE
  ZGIA, Zaporozhye, Ukraine. 
  http://www.zgia.zp.ua. 




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[Frank Mayhar]

Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Frank Mayhar writes:
> : Wups, I thought I read 575BT.  But no, the 574BT doesn't work either; there's
> : a bug somewhere in the driver.  I have one of _those_, too, having read the
> : same thing you did.
> 
> Last I heard, Matt Dodd had or was waiting for a 574BT and pccard
> enviornment to fix the driver.

He's got both the card and the documentation, courtesy of Terry Murphy at
3Com and my efforts to that end.

> I have a 3CCFE575CT sitting here on my desk right now as a gentile
> reminder to work on pccard/cardbus stuff :-).

Is that one that Matt sent you?  If so, that's the result of the same effort.
Else Matt has one, too.
-- 
Frank Mayhar [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: kvm-troubles

[Pascal Hofstee]

On Wed, Jan 05, 2000 at 11:38:56AM +0100, Pascal Hofstee wrote:
> with a buildworld of sources fetched about 6-8 hours ago ... I get a whole
> lot of trouble with anything that tries to use kvm.
> 
> Ending up with loads of the following error:
> link_elf_lookup_symbol: corrupt symbol table
> 
> bash-2.03$ vmstat -i
> vmstat: undefined symbols:
>  _cp_time _cnt _boottime _hz _stathz _nchstats _intrnames _eintrnames
> _intrcnt _eintrcnt _kmemstatistics _bucket _zlist
> 
> 
> bash-2.03$ top
> top: nlist failed
> 
> 
> I get the feeling it's still trying to use /var/db/kvm_kernel.db which
> hasn't been updated since (iirc) the kernel should directly acuire these
> symbols from the running kernel itself. (around Dec. 25th 1999)

Ok ... either this problem has been solved in the source-code already.
Or i just had to do a config -r on my kernel configuration first.
Either way ... it's working again.

-- 

  Pascal Hofstee - [EMAIL PROTECTED]

-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP--
t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+
--END GEEK CODE BLOCK--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: new man pages

[Marc Schneiders]

On Wed, 5 Jan 2000, Bruce Evans wrote:

> On Wed, 5 Jan 2000, Ollivier Robert wrote:
> 
> > According to Rodney W. Grimes:
> > > xntpd was recently renamed ntpd, but the documentation and manual
> > > pages was not. 
> >  
> > > You'll find the manual page for ntpd with a ``man xntpd''.
> 
> Those are the old man pages.  You're not running -current if you have
> them :-).
> 

As far as I can see only the command is removed, the xntpd man page is
left alone. I still have it. This is current of December 31.

[...]

--
Marc Schneiders

[EMAIL PROTECTED]
[EMAIL PROTECTED]

propro3:02pm  up   5 days,  16:51,  load average: 2.18 2.09 2.05



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: options COMPAT_LINUX makes kernel fail to compile

[Marcel Moolenaar]

Michael Lucas wrote:

> The COMPAT_LINUX kernel option isn't needed any more, per Marcel.  (At
> least, when I wrote an article on this, it wasn't.)  You can probably
> remove COMPAT_LINUX entirely.

Assuming that you want to use the module of course...

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

ifq_maxlen in vx-driver

[Oliver Schonefeld]

hello *!

i am using the vx driver in for my two 3c397 boards.
when booting i get the following message:

vx0 XXX: driver didn't set ifq_maxlen

obviosly the ifq_maxlen is not set in the eisa nor in the pci version in the
driver.
actually, to set this, would be one line in the driver, but unfrotunatly i
am not that familiar with the hardware, and do not know, which value this
parameter shoul have. maybe, someone knows ...

cheers,
oliver
-- 

And remember: "Life sucks and then you die!"

email: [EMAIL PROTECTED]
   [EMAIL PROTECTED]

Hi! I'm a .signature virus! Copy me in your ~/.signature
to help me spread! <- Save this lifeform ;-)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

making release

[Alexandr Listopad]

Hi.

I want to make a release of 4.0-CUR in 3.4-ST. Will it nice idea? Now I
cvsuping sources of 4.0. Is there any troubles?

And another one question: I don't cvsup "cvs-crypto". Will my release
maked?

Thanks. ..and sorry for my bad English. ;|

P.S. pls reply to me, i'm not currently subscribed.

Regards,
  Listopad Alexandr
  ([EMAIL PROTECTED]), LAA7-RIPE
  ZGIA, Zaporozhye, Ukraine. 
  http://www.zgia.zp.ua. 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Proposal: Removing doscmd from the source tree...

[Marcel Moolenaar]

Taavi Talvik wrote:
> 
> Maybe knob in /etc/make.conf instead to force compiling with X?
> 

Nah, we don't need to. doscmd doesn't have X support by default (now
that I've committed the fix). Recompiling doscmd to get X (given X is
installed on the machine of course) is broken but simple enough. If you
don't want X, don't recompile doscmd or don't install X. Any other
change only adds to the argument of making doscmd a port (or two), IMO.

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[Matthew N. Dodd]

On Wed, 5 Jan 2000, Warner Losh wrote:
> Last I heard, Matt Dodd had or was waiting for a 574BT and pccard
> enviornment to fix the driver.

I've got both a 574 and a 575.  I'm waiting on my PCIC ISA bridgeboard. :/

Anyone know of a PCI Cardbus bridgeboard?  I'd rather not have to get a
laptop just so I can play with cardbus.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Proposal: Removing doscmd from the source tree...

[Michael Lucas]

> > > A possibility could be: 1. build it for i386 only, 2. build it via
> > > buildworld without X11, regardless if X11 exists. If I want to use it
> > > with X11, it is interactive and I can make it for X11 by hand - it will
> > > not break on compile runs at some hour at night.
> > 
> > I'll commit a fix that will prevent including X when DESTDIR has been
> > set. In practice this means that doscmd will never include X, unless you
> > compile it by hand. This of course implies that you have to compile
> > doscmd by hand every time you do an installworld, given that you want X.
> 
> Maybe knob in /etc/make.conf instead to force compiling with X?
> 
> best regards,
> taavi

Actually, several ports give you the option of building with or
without X support (i.e., SSH).  It would be nice to have a USE_X11
option in /etc/make.conf for doscmd as well as these ports, so you
don't have to specify it on the command line while building.

Of course, I'd like a pony too.  And a pink bike shed.

==ml


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: compiling libF77/libI77

[David O'Brien]

On Tue, Jan 04, 2000 at 10:28:28PM +0100, Dave J. Boers wrote:
> It's funny how I tend to find things out only just _after_ I asked someone

If you still need the shared libf2c.so.2 for older binaries, install the
latest compat3x distribution.

-- 
-- David([EMAIL PROTECTED])


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA atapi-all.c problems/fixes/cleanups

[Brian Fundakowski Feldman]

On Wed, 5 Jan 2000, Soren Schmidt wrote:

> Try this patch instead, it should do the right thing..

Since they're functionally the same, sure, I wouldn't mind either
way :)

> 
> -Søren
> 

-- 
 Brian Fundakowski Feldman   \  FreeBSD: The Power to Serve!  /
 [EMAIL PROTECTED]`--'



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Opera Beta and FreeBSD

[Bill Fumerola]

On Wed, 5 Jan 2000, Lutz Albers wrote:

> Works fine, but you need the glibc-2.1 libraries (i.e. from RedHat 6.1), as 
> it is linked against these.
> 
> Keep in mind that this is no beta, but a 'technical preview', many 
> functions are still missing.

FWIW, the linux_base port in http://www.FreeBSD.org/~marcel/ works fine,
and probably should be committed. I'm running Nutscrape on that port
on several different machines and they're all just fine.

-- 
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED]  -






To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Proposal: Removing doscmd from the source tree...

[Taavi Talvik]

On Wed, 5 Jan 2000, Marcel Moolenaar wrote:

> Thomas Zenker wrote:
> > 
> > A possibility could be: 1. build it for i386 only, 2. build it via
> > buildworld without X11, regardless if X11 exists. If I want to use it
> > with X11, it is interactive and I can make it for X11 by hand - it will
> > not break on compile runs at some hour at night.
> 
> I'll commit a fix that will prevent including X when DESTDIR has been
> set. In practice this means that doscmd will never include X, unless you
> compile it by hand. This of course implies that you have to compile
> doscmd by hand every time you do an installworld, given that you want X.

Maybe knob in /etc/make.conf instead to force compiling with X?

best regards,
taavi
---
Taavi Talvik| Internet: [EMAIL PROTECTED] 
Unineti Andmeside AS| phone: +372 6405150
Ravala pst. 10  | fax: +372 6405151
Tallinn 10143, Estonia  |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Proposal: Removing doscmd from the source tree...

[Marcel Moolenaar]

Thomas Zenker wrote:
> 
> A possibility could be: 1. build it for i386 only, 2. build it via
> buildworld without X11, regardless if X11 exists. If I want to use it
> with X11, it is interactive and I can make it for X11 by hand - it will
> not break on compile runs at some hour at night.

I'll commit a fix that will prevent including X when DESTDIR has been
set. In practice this means that doscmd will never include X, unless you
compile it by hand. This of course implies that you have to compile
doscmd by hand every time you do an installworld, given that you want X.

I still think doscmd should and can be a port, but I think it helps my
argument if I have the port ready to be committed and downloadable for
testing. It helps undermine the general objection that doscmd is very
dependent on the kernel, which I doubt...

If not, it will at least show me that I'm wrong :-)

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Opera Beta and FreeBSD

[Lutz Albers]

If memory serves me right,  said on 2000-01-04 15:29 -0600:

> Has anyone gotten Opera beta working under linux emulation?

Works fine, but you need the glibc-2.1 libraries (i.e. from RedHat 6.1), as 
it is linked against these.

Keep in mind that this is no beta, but a 'technical preview', many 
functions are still missing.

--
Lutz Albers, [EMAIL PROTECTED], pgp key available from 
Do not take life too seriously, you will never get out of it alive.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: options COMPAT_LINUX makes kernel fail to compile

[Michael Lucas]

Hello,

Not that this is an actual fix to the problem, but:

The COMPAT_LINUX kernel option isn't needed any more, per Marcel.  (At
least, when I wrote an article on this, it wasn't.)  You can probably
remove COMPAT_LINUX entirely.

(If only the rest of the problems were this easy.  :)

==ml

> Hi!
> 
> With option COMPAT_LINUX (which present in LINT) make depend fails with:
> cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
> -fformat-extensions -ansi  -nostdinc -I- -I. -I../.. -I../../../include
> -D_KERNEL -include opt_global.h -elf -fno-builtin
> -mpreferred-stack-boundary=2  -UKERNEL -o linux_genassym.o -c
> ../../i386/linux/linux_genassym.c
> genassym -o linux_assym.h linux_genassym.o
> genassym:No such file or directory
> *** Error code 1 
> 
> Dmitry.
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: A couple questions regarding pcmcia cards....

[Brad Knowles]

At 11:59 PM -0700 2000/1/4, Warner Losh wrote:

>   I fear it will be Feb or Mar before I get to it at this rate
>  since I have little free time.  Consulting $$$ takes precidence over
>  freetime hacking...

I'm not one of the affected, but is there any chance a collection 
could be taken up to help fund this effort at a higher priority?  It 
seems to me that this is precisely the sort of thing that people 
might be willing pay some money for, and it wouldn't take too much 
money from too many people before this might start becoming 
potentially interesting.


On a related note, perhaps it might be interesting to start a 
list of FreeBSD projects that might affect relatively large numbers 
of people, but which are languishing due to lack of funds on the part 
of the people who are involved in the implementation process?

I don't have any money to just donate to causes like this [0], 
but I suspect that this is one of those things where we could allow 
people to contribute in a material fashion, other than either hacking 
on code or volunteering to be a guinea-pig and testing out code that 
had been hacked by someone else.  It would also allow people to get 
collections together for those things where a lot of people who would 
be materially impacted could get small-scale donations together and 
potentially have a large impact.

In fact, you could even get into corporate sponsors & paid 
support contracts, and potentially start generating some serious 
money that could be put to good uses.


Sorry if I'm re-opening any old wounds, or if this is something 
that's already being done.  However, if that's the case, I'd 
appreciate pointers to information on this.








[0]  It's not like I'm a multi-millionaire who got lots of money from 
a company I founded being bought out from underneath me or going IPO, 
and then spending all my free time working on FreeBSD kernel issues 
-- unlike certain other people I could mention. ;-)

-- 
   These are my opinions -- not to be taken as official Skynet policy
  
|o| Brad Knowles, <[EMAIL PROTECTED]>Belgacom Skynet NV/SA |o|
|o| Systems Architect, News & FTP Admin  Rue Col. Bourg, 124   |o|
|o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels   |o|
|o| http://www.skynet.be Belgium   |o|
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
  Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
   Unix is very user-friendly.  It's just picky who its friends are.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

kvm-troubles

[Pascal Hofstee]

with a buildworld of sources fetched about 6-8 hours ago ... I get a whole
lot of trouble with anything that tries to use kvm.

Ending up with loads of the following error:
link_elf_lookup_symbol: corrupt symbol table

bash-2.03$ vmstat -i
vmstat: undefined symbols:
 _cp_time _cnt _boottime _hz _stathz _nchstats _intrnames _eintrnames
_intrcnt _eintrcnt _kmemstatistics _bucket _zlist


bash-2.03$ top
top: nlist failed


I get the feeling it's still trying to use /var/db/kvm_kernel.db which
hasn't been updated since (iirc) the kernel should directly acuire these
symbols from the running kernel itself. (around Dec. 25th 1999)

-- 

  Pascal Hofstee - [EMAIL PROTECTED]

-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP--
t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+
--END GEEK CODE BLOCK--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Opera Beta and FreeBSD

[Vallo Kallaste]

On Wed, Jan 05, 2000 at 11:53:46AM +0200, Maxim Sobolev <[EMAIL PROTECTED]> wrote:

> > What WM you are running? Is it Blackbox with KDE or..?
> 
> Looks like it is KWM with KDE ;).

Ok, ok :) I did run Blackbox some time ago w.o. KDE and now I saw the
nice taskbar with gradient, so.. hehe I thought it has something to do
with Blackbox. Forgot themes completely.
Can Opera run NS plugins, example Shockwave plugin for Linux? Shockwave
enabled, err.. restricted site count seems to increase rapidly nowadays :-|
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Opera Beta and FreeBSD

[Maxim Sobolev]

Vallo Kallaste wrote:

> On Tue, Jan 04, 2000 at 02:12:08PM -0800, Chris Piazza <[EMAIL PROTECTED]> wrote:
>
> > Yes.  I must warn you it's still really buggy if you intend to use
> > it a lot.  Basically all I did was grab the opera tarball, extract
> > it and run the 'runnow' script.
> >
> > Screenshot here: http://www.freebsd.org/~cpiazza/sshot-opera.png
>
> What WM you are running? Is it Blackbox with KDE or..?

Looks like it is KWM with KDE ;).

-Maxim



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: A couple questions regarding pcmcia cards....

[Jason Young]

> You can pull rev. 1.87 of if_ep.c out of the Attic from cvsweb:
> 
>  http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/Attic/if_ep.c
> 
> And it will drop directly into your tree in /sys/i386/isa. 
> Make sure you
> have 1.23.2.1 or later of if_epreg.h.

Argh, I thought I was talking on the freebsd-stable list. You're going to
have to talk to Matt about this card in -current, since he's the maintainer
of the driver now. I might look into it later, but I stopped cvsupping my
laptop when the ep driver upheavals began for fear of losing connectivity
totally (never have gotten the modem to work).

The instructions I gave -will- get a 3.X box working, however
 
> The only major change of the patch is to hit the card with an 
> offset command
> if the no-offset commands don't work. I have no idea what its 
> significance
> is other than it's required to make my card work. I can't 
> remember where I
> got the basic idea from, it was from PAO I think.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: A couple questions regarding pcmcia cards....

[Jason Young]

The card is also available in a 16-bit version (it has a PC Card logo on the
back, I don't know if the Cardbus one does or not). It's important to note
that the 575 (not the 574) is CardBus. I used to have one, but
semi-thankfully, it got blown up by lightning and the replacement was 16-bit
and thus usuable with FreeBSD.

If you actually have the 16-bit pccard version, then you need to patch your
driver. I sent in patches that got committed to 4.0, but were basically
replaced a month later by Matt Jacob's massive rework of the entire ep
driver and not MFC'd.

You can pull rev. 1.87 of if_ep.c out of the Attic from cvsweb:

 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/isa/Attic/if_ep.c

And it will drop directly into your tree in /sys/i386/isa. Make sure you
have 1.23.2.1 or later of if_epreg.h.

The only major change of the patch is to hit the card with an offset command
if the no-offset commands don't work. I have no idea what its significance
is other than it's required to make my card work. I can't remember where I
got the basic idea from, it was from PAO I think.


> -Original Message-
> From: Frank Mayhar [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 05, 2000 12:18 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: A couple questions regarding pcmcia cards
> 
> 
> William Woods wrote:
> > I have two pcmcia cards here I am wondering if the work 
> under either -stable
> > or -current, they are:
> >  
> > 3COM Megahertz 10/100 LAN PC Card model #3CCFE574BT
> 
> This is a cardbus card (I have one, too) and won't work.  
> Many of us are
> eagerly awaiting Warner's new cardbus code.
> 
> > The other card is cardbus, so I doubt it but I will ask anyway
> > 
> > Adaptec SlimSCSI 1480A UltraSCSI
> 
> If it's cardbus, it won't work.
> -- 
> Frank Mayhar [EMAIL PROTECTED]
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA lost contact

[Soren Schmidt]

It seems Kris Kennaway wrote:
> On Wed, 5 Jan 2000, Soren Schmidt wrote:
> 
> > The disk probably has problems with DMA mode (lots of older WD disks
> > has that). You only get WDMA2 mode since you controller is an older
> > Intel PIIX that can't do UDMA...
> 
> Hmm..This disk was bought in about March 99..you're sure that's the
> reason?

No, but I've had my share of bad experiences with WD disks in that
regard, I'll have to look up the modelnumber to be sure...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

portmap problems

[Anthony Kimball]

Recently I've noticed that it takes a long time for portmap
to settle well enough so that mountd and nfsd can register.

Jan  5 02:16:56 avalon mountd[97]: can't register mount
Jan  5 02:16:56 avalon nfsd:[99]: can't register with udp portmap

Very strange.  Strange enough so that perhaps it might
catch someone else's interest.  Someone who might actually do
something about it, maybe even.

portmap was pid 92 this time.  Killing and restarting mountd and nfsd
works:

% rpcinfo -p
   program vers proto   port
102   tcp111  portmapper
102   udp111  portmapper
153   udp   1011  mountd
153   tcp   1020  mountd
151   udp   1011  mountd
151   tcp   1020  mountd
132   udp   2049  nfs
133   udp   2049  nfs

Which suggests to me -- perhaps portmap and mountd
should be allowed to take a -u argument as well, to reduce
port consumption?  If so, I imagine the patch would be something
like this:

diff -u sbin/mountd/mountd.c.orig sbin/mountd/mountd.c.new
--- sbin/mountd/mountd.c.orig   Wed Jan  5 02:36:27 2000
+++ sbin/mountd/mountd.c.newWed Jan  5 02:38:22 2000
@@ -229,6 +229,8 @@
 int debug = 0;
 #endif
 
+int udponly = 0;
+
 /*
  * Mountd server for NFS mount protocol as described in:
  * NFS: Network File System Protocol Specification, RFC1094, Appendix A
@@ -255,7 +257,7 @@
if (error)
errx(1, "NFS support is not available in the running kernel");
 
-   while ((c = getopt(argc, argv, "2dlnr")) != -1)
+   while ((c = getopt(argc, argv, "2dlnru")) != -1)
switch (c) {
case '2':
force_v2 = 1;
@@ -272,6 +274,9 @@
case 'l':
log = 1;
break;
+   case 'u':
+   udponly = 1;
+   break;
default:
usage();
};
@@ -317,7 +322,7 @@
}
}
if ((udptransp = svcudp_create(RPC_ANYSOCK)) == NULL ||
-   (tcptransp = svctcp_create(RPC_ANYSOCK, 0, 0)) == NULL) {
+   (!udponly && (tcptransp = svctcp_create(RPC_ANYSOCK, 0, 0)) == NULL)) {
syslog(LOG_ERR, "can't create socket");
exit(1);
}
@@ -325,12 +330,12 @@
pmap_unset(RPCPROG_MNT, 3);
if (!force_v2)
if (!svc_register(udptransp, RPCPROG_MNT, 3, mntsrv, IPPROTO_UDP) ||
-   !svc_register(tcptransp, RPCPROG_MNT, 3, mntsrv, IPPROTO_TCP)) {
+   (!udponly && !svc_register(tcptransp, RPCPROG_MNT, 3, mntsrv, 
+IPPROTO_TCP))) {
syslog(LOG_ERR, "can't register mount");
exit(1);
}
if (!svc_register(udptransp, RPCPROG_MNT, 1, mntsrv, IPPROTO_UDP) ||
-   !svc_register(tcptransp, RPCPROG_MNT, 1, mntsrv, IPPROTO_TCP)) {
+   (!udponly && !svc_register(tcptransp, RPCPROG_MNT, 1, mntsrv, 
+IPPROTO_TCP))) {
syslog(LOG_ERR, "can't register mount");
exit(1);
}
diff -u usr.sbin/portmap/portmap.c.orig usr.sbin/portmap/portmap.c.new
--- usr.sbin/portmap/portmap.c.orig Wed Jan  5 02:33:53 2000
+++ usr.sbin/portmap/portmap.c.new  Wed Jan  5 02:36:03 2000
@@ -109,6 +109,7 @@
 
 struct pmaplist *pmaplist;
 int debugging = 0;
+int udponly = 0;
 
 int
 main(argc, argv)
@@ -121,7 +122,7 @@
int len = sizeof(struct sockaddr_in);
register struct pmaplist *pml;
 
-   while ((c = getopt(argc, argv, "dv")) != -1) {
+   while ((c = getopt(argc, argv, "duv")) != -1) {
switch (c) {
 
case 'd':
@@ -132,6 +133,10 @@
verboselog = 1;
break;
 
+   case 'u':
+   udponly = 1;
+   break;
+
default:
usage();
}
@@ -169,29 +174,32 @@
pml->pml_map.pm_port = PMAPPORT;
pmaplist = pml;
 
-   if ((sock = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) {
+   if (!udponly) {
+
+   if ((sock = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP)) < 0) {
syslog(LOG_ERR, "cannot create tcp socket: %m");
exit(1);
-   }
-   if (bind(sock, (struct sockaddr *)&addr, len) != 0) {
+   }
+   if (bind(sock, (struct sockaddr *)&addr, len) != 0) {
syslog(LOG_ERR, "cannot bind tcp: %m");
exit(1);
-   }
-   if ((xprt = svctcp_create(sock, RPCSMALLMSGSIZE, RPCSMALLMSGSIZE))
-   == (SVCXPRT *)NULL) {
+   }
+   if ((xprt = svctcp_create(sock, RPCSMALLMSGSIZE, RPCSMALLMSGSIZE))
+   == (SVCXPRT *)NULL) {
syslog(LOG_ERR, "couldn't do tcp_create");
exit(1);
+   }
+   /* make an entry for ourself */
+   pml = (stru

newpcm problems

[Anthony Kimball]

With yesterday's current I get bounce buffer panics in isa_dmastart
doing cat foo.pcm >/dev/dsp.  The same thing happens with mss.c v1.42
modified to reduce MSS_BUFSIZE by 48k.

The card is ESS1869 in this case:

Jan  5 02:16:55 avalon /kernel: unknown0:  at 
port 0x800-0x807 on isa0
Jan  5 02:16:55 avalon /kernel: sbc0:  at port 
0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0
Jan  5 02:16:55 avalon /kernel: pcm0:  on sbc0
Jan  5 02:16:55 avalon /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00
Jan  5 02:16:55 avalon /kernel: bus_dmamap_load: Too many segs! buf_len = 0xdf00
Jan  5 02:16:55 avalon /kernel: joy1:  at port 0x200 on isa0


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA lost contact

[Kris Kennaway]

On Wed, 5 Jan 2000, Soren Schmidt wrote:

> The disk probably has problems with DMA mode (lots of older WD disks
> has that). You only get WDMA2 mode since you controller is an older
> Intel PIIX that can't do UDMA...

Hmm..This disk was bought in about March 99..you're sure that's the
reason?

Kris



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA lost contact

[Soren Schmidt]

It seems Kris Kennaway wrote:
> One of my Western Digital Caviars doesn't work under the new ATA driver:
> upon trying to access the disk (via swapon or mount during boot) it gives
> the famous "lost contact with disk" message and falls back to PIO mode.
> Interestingly, my two older WDCs work fine - although I notice that ad1
> and ad2 are only detected as WDMA2, when it seems (from the udma=2) that
> they can handle UDMA - is this a cabling issue or something (I'm not
> familiar with IDE cabling requirements)?

The disk probably has problems with DMA mode (lots of older WD disks
has that). You only get WDMA2 mode since you controller is an older
Intel PIIX that can't do UDMA...

> ata-pci0:  at device 7.1 on pci0
> ata-pci0: Busmastering DMA supported
> ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0
> ad0:  ATA-0 disk at ata0 as master
> ad0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S
> ad0: 16 secs/int, 1 depth queue, WDMA2
> ad1: piomode=4 dmamode=2 udmamode=2 cblid=0
> ad1:  ATA-3 disk at ata0 as slave 
> ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S
> ad1: 16 secs/int, 1 depth queue, WDMA2
> ad2: piomode=4 dmamode=2 udmamode=2 cblid=0
> ad2:  ATA-4 disk at ata1 as master
> ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
> ad2: 16 secs/int, 1 depth queue, WDMA2


-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: ATA atapi-all.c problems/fixes/cleanups

[Soren Schmidt]

It seems Brian Fundakowski Feldman wrote:
> 
> I used a multiple of the blocksize, and it works fine, except for on
> the very last bit of data.  The very last bit of data is what causes
> an underrun, and the code that's there for overrun/underrun is
> wrong right now.  For underrun, it ends up writing the underlying
> blocksize length from the user buffer of _less_than_that_size_, then
> it writes (blocksize - user buffer size) _more_ zeroed data!  This
> promptly locks up the IDE bus with my CD-R.  That's what the patch was
> about and you didn't say anything about; yes, I know that blocksizes
> should be matched perfectly and padded perfectly to prevent the ATA
> driver from having to handle the underrun/overrun cases, but the
> current handling is/was still broken.

Try this patch instead, it should do the right thing..

Index: atapi-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/atapi-all.c,v
retrieving revision 1.29
diff -u -r1.29 atapi-all.c
--- atapi-all.c 2000/01/03 10:26:56 1.29
+++ atapi-all.c 2000/01/05 08:36:49
@@ -563,12 +563,15 @@
 #endif
for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA);
+   *buffer += request->bytecount;
+   request->bytecount = 0;
 }  
-else
+else {
insw(request->device->controller->ioaddr + ATA_DATA,
 (void *)((uintptr_t)*buffer), length / sizeof(int16_t));
-request->bytecount -= length;
-*buffer += length;
+   *buffer += length;
+   request->bytecount -= length;
+}
 }
 
 static void
@@ -585,19 +588,22 @@
   request->device->devname, length, request->bytecount);
 #ifdef ATA_16BIT_ONLY
outsw(request->device->controller->ioaddr + ATA_DATA, 
- (void *)((uintptr_t)*buffer), length / sizeof(int16_t));
+ (void *)((uintptr_t)*buffer), request->bytecount/sizeof(int16_t));
 #else
outsl(request->device->controller->ioaddr + ATA_DATA, 
- (void *)((uintptr_t)*buffer), length / sizeof(int32_t));
+ (void *)((uintptr_t)*buffer), request->bytecount/sizeof(int32_t));
 #endif
for (resid=request->bytecount; residdevice->controller->ioaddr + ATA_DATA, 0);
+*buffer += request->bytecount;
+   request->bytecount = 0;
 }
-else
+else {
outsw(request->device->controller->ioaddr + ATA_DATA, 
  (void *)((uintptr_t)*buffer), length / sizeof(int16_t));
-request->bytecount -= length;
-*buffer += length;
+*buffer += length;
+   request->bytecount -= length;
+}
 }
 
 static void 

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message