date:20000222


On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote:
 Dear guys,
 
   I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
 KDE 1.1.2.  All from monday's ports tree.
   Well, I think I can't say I am running this system, for I am getting
 the following message whenever I try startx:
 
 Authentication failed - cannot start X server.
 Perhaps you do not have console ownership?
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 giving up.
 xinit:  No such file or directory (errno 2):  unable to connect to X server
 xinit:  No such process (errno 3):  Server error.
 
   Damn, I know this must be my mistake. However, I can't seem to get
 X up. However, /stand/sysinstall - Configure - XFree86 - XF86Setup
 works smooth. Before you mention it: yeah, yeah, I tried startx as root
 against my best judgement; and no, it did not work. :)
   UCONSOLE is enabled.
   My .xinitrc follows at the end of this file.
   What am I missing? A new authentication system? My guess. I went
 through the FAQ and most of the simple docs; I must be overlooking something.
   Any and all help appreciated. Please CC: to [EMAIL PROTECTED], for I
 am subscribed to neither freebsd-questions nor freebsd-current.
   I apologize in advance for the CC: accross mailing lists.
 
   Regards,
   Mario Ferreira
 
 ps: Please, don't flame me. /dev/null appreciates it. Thanks again.

1) Do you have "XSERVER" option in kernel? I'm not sure if it's
required, but it might be.

2) You should start KDE with "startkde" not "kde".

-- 
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: IP tunnel

2000-02-22 Thread Archie Cobbs


Cob writes:
 What about ${subj} in current?
 Or maybe someone know how to make 
 ip tunnel on current using patches, tools, etc.?

One way is exhibited in /usr/share/examples/netgraph/udp.tunnel.

-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: Interesting failure mode for static linking with shared libs.

2000-02-22 Thread Vladimir Kushnir


Actually, this is a (minor) bug in binutils (see patch below): ELF
interpreteu is defined as /usr/lib/libc.so.1 rather than
(here) /usr/libexec/ld-elf.so.1 

On Tue, 22 Feb 2000, Martin Cracauer wrote:

 In [EMAIL PROTECTED], Jordan K. Hubbard wrote: 
  root@zippy- cc -fPIC -c stub.c
  root@zippy- ld -shared -o stub.so stub.o
  root@zippy- cc -static test.c -o test stub.so
  root@zippy- ./test 
  ELF interpreter /usr/lib/libc.so.1 not found
  Abort trap
  root@zippy- cc -static test.c -o test stub.o
  root@zippy- ./test 
  Now in the client, calling doit()
  You have reached the stub.  Please leave a message.
 
 As a workaround for a static binary, you should be able to use
   -Xlinker -Bstatic
 instead of
   -static
 
 -static links the libs statically and also leaves out the dynamic
 loading code from the binary.
 
 The former leaves the dynamic loading code in the binary, but links
 the libs statically. You have a slightly bigger binary, but you don't
 need the libs at runtime and you are resistent against changed/faked
 libs, which might do the job you want static linking for.
 
 Martin
 

Regards,
Vladimir

--- /usr/src/contrib/binutils/bfd/elf32-i386.c.orig Tue Feb  9 21:57:33 1999
+++ /usr/src/contrib/binutils/bfd/elf32-i386.c  Tue Feb  9 21:55:53 1999
@@ -249,7 +249,7 @@
 /* The name of the dynamic interpreter.  This is put in the .interp
section.  */
 
-#define ELF_DYNAMIC_INTERPRETER "/usr/lib/libc.so.1"
+#define ELF_DYNAMIC_INTERPRETER "/usr/libexec/ld-elf.so.1"
 
 /* The size in bytes of an entry in the procedure linkage table.  */
 
--- /usr/src/contrib/binutils/bfd/elf64-alpha.c.origWed Feb 10 00:39:39 1999
+++ /usr/src/contrib/binutils/bfd/elf64-alpha.c Wed Feb 10 00:40:05 1999
@@ -1018,7 +1018,7 @@
 
 #define MAX_GOT_ENTRIES(64*1024 / 8)
 
-#define ELF_DYNAMIC_INTERPRETER "/usr/lib/ld.so"
+#define ELF_DYNAMIC_INTERPRETER "/usr/libexec/ld-elf.so.1"
 
 /* Handle an Alpha specific section when reading an object file.  This
is called when elfcode.h finds a section with an unknown type.
-- 

===|===
 Vladimir Kushnir  |
 [EMAIL PROTECTED]  |Powered by FreeBSD
 [EMAIL PROTECTED]  |



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

Re: Upgrade from 3.4 to 4.0...


Well, I guess what confused me is the order

I would assume that the last entry, being the newest, would have all the steps
listed that are currently needed. Maby its just me and, I am really not tyring
to cause a hassle, maby I am reading it wrong.

It seems to me that you need to piece together what you need be applying past
steps and seeing what has changed. I guess what I am looking for is a :

1) xx
2) xx
3) xx

type of thing.

Again, thats what confused me. Maby others can see it fine, but it lost me.

Thanks

On 23-Feb-00 Alfred Perlstein wrote:
 * William Woods [EMAIL PROTECTED] [000222 21:27] wrote:
 I did read that document, and honestly, it dident make a lot of sence and it
 seemed to have some conflicting instructions.which is why I am asking
 here.
 
 It looks pretty concise to me, perhaps you can explain the confusion
 so that we may fix it so as to help other users?
 
 -Alfred
 
 
 On 23-Feb-00 Alfred Perlstein wrote:
  * William Woods [EMAIL PROTECTED] [000222 21:19] wrote:
  Hey,
  
  I have been following the disscussions here for a while, just trying to
  get
  a
  feel of what the transition from 3.4-stable 4.0-release will be like. I
  am
  running -current on my alpha, but that was a fresh install. I am debating
  trying -current on my laptop, but before we go there, I would like to
  inquire
  as to what shape the transition is in. Are there steps posted somewhere
  that
  work?
  
  Also, what condition (I know, I am asking you to read the future) do you
  expect
  the transition to be like at the end of the month when 4.0 -release comes
  out.
  
  Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now,
  where
  would I find the nessary instructions?
  
  Please see src/UPDATING


--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 22-Feb-00
Time: 21:05:59l
FreeBSD 3.4
--


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

Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.

2000-02-22 Thread Thierry Herbelot


Mike Smith wrote:
 
I've yesterday sent a post on this list (from my work email) about the
impossibility of loading the if_xl and miibus modules with the loader
(it works well with kldload, afterwards)
  
   This is a known problem with modules that have dependancies; if you load
   the miibus module first it shouldn't happen (I haven't tested this).
 
  it does : I've tried
  loading miibus alone : works fine
  loading miibus, then if_xl : loops in loading miibus
 
 Ok.  We know that hurts, don't do that. 8)

fine, could there be a note in /boot/loader.conf, so that l^Husers don't
get burn trying to load things which won't work (no code change : just a
word of caution)

TfH


 
 --
 \\ Give a man a fish, and you feed him for a day. \\  Mike Smith
 \\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
 \\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]


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

Re: Interesting failure mode for static linking with shared libs.

2000-02-22 Thread Martin Cracauer


In [EMAIL PROTECTED], Jordan K. Hubbard wrote: 
 root@zippy- cc -fPIC -c stub.c
 root@zippy- ld -shared -o stub.so stub.o
 root@zippy- cc -static test.c -o test stub.so
 root@zippy- ./test 
 ELF interpreter /usr/lib/libc.so.1 not found
 Abort trap
 root@zippy- cc -static test.c -o test stub.o
 root@zippy- ./test 
 Now in the client, calling doit()
 You have reached the stub.  Please leave a message.

As a workaround for a static binary, you should be able to use
  -Xlinker -Bstatic
instead of
  -static

-static links the libs statically and also leaves out the dynamic
loading code from the binary.

The former leaves the dynamic loading code in the binary, but links
the libs statically. You have a slightly bigger binary, but you don't
need the libs at runtime and you are resistent against changed/faked
libs, which might do the job you want static linking for.

Martin
-- 
%
Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/
BSD User Group Hamburg, Germany http://www.bsdhh.org/


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

Re: After last ATAPI update system doesn't boot if modules loaded by /boot/loader.

2000-02-22 Thread Mike Smith


 I've yesterday sent a post on this list (from my work email) about the
 impossibility of loading the if_xl and miibus modules with the loader
 (it works well with kldload, afterwards)
   
This is a known problem with modules that have dependancies; if you load
the miibus module first it shouldn't happen (I haven't tested this).
  
   it does : I've tried
   loading miibus alone : works fine
   loading miibus, then if_xl : loops in loading miibus
  
  Ok.  We know that hurts, don't do that. 8)
 
 fine, could there be a note in /boot/loader.conf, so that l^Husers don't
 get burn trying to load things which won't work (no code change : just a
 word of caution)

Actually, I think that turning off dependancy handling in the loader is 
the right way to do it.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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

Re: Crashing netscape?

2000-02-22 Thread Martin Cracauer


In [EMAIL PROTECTED], Alex Le Heux wrote: 
 Hi,
 
 Am I the only one who's experiencing an amzing amount of crashes on
 Netscape?

This made a real difference in stability for me:
Before installing a new Netscape,
rm -rf /usr/local/lib/netscape
rm -rf /home/*/.netscape

Seriously, when I had old config stuff lying around, Netscape's crash
frequency was about 10 times as much as it is now that I clean up
before upgrading.

Turning off Javascript also helps, but may be contraproductive.

Also, consider Netscape 3.04 for stability.

BTW, does anyone know if its possible to write a plugin for the BSDI
version of Navigator 3.04 so that it display *.png files as it
displays *.gif files now?

As I understand, a plugin doesn't have fine enough access to the
display code to do this, right?

Martin
-- 
%
Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/
BSD User Group Hamburg, Germany http://www.bsdhh.org/


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

Re: Crashing netscape?

2000-02-22 Thread Donn Miller


Martin Cracauer wrote:

 BTW, does anyone know if its possible to write a plugin for the BSDI
 version of Navigator 3.04 so that it display *.png files as it
 displays *.gif files now?
 
 As I understand, a plugin doesn't have fine enough access to the
 display code to do this, right?

You could try Mozilla.  I usually check out the SeaMonkeyAll code via
cvs.  So far, it's built fairly well.  Mozilla is still a bit sluggish
now, though.  (I guess the optimization for speed will come later.)  I
can give you the .mozconfig file I used to successfully build Mozilla
on -current.

Also, xemacs has a `w3' package that does web pages, possibly png. 
(Some pages don't look very well, however.)

- Donn


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

Re: Panic (TCP)

2000-02-22 Thread Jeroen Ruigrok/Asmodai


-On [2221 12:01], Luigi Rizzo ([EMAIL PROTECTED]) wrote:
 this is fun...
 
 Just caught panic #3 on my Diablo newstransit box running 4.0 from the
 7th of February.
 
 This box pushes around 360-380 GB in a weekend on network IO.

this is the right kind of app for -current isn't it :)

Hey you guys claim everything was limited and fixed and more stable and
errr...  Wait a sec, I'm part of this development.

Mmm. =)

Well, it's definately a good torture box for CURRENT.

I was already able to get the amr driver to wedge once after which I
changed something in the driver after speaking with Mike.

Now to get the last few panics looked at.

OBTW, is it possible to gdb -k kernel.0 vmcore.0 the files on another
box, or not?

-- 
Jeroen Ruigrok vd Werven/Asmodaiasmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/B-rated Coder BSD: Technical excellence at its best  
The BSD Programmer's Documentation Project http://home.wxs.nl/~asmodai
Religion... Is the opium of the people...


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

Re: timeout problems HighPoint HPT366 ATA66 controller 40 GB Diamond Max Plus


It seems Andreas Klemm wrote:
 Hi !
 
 I have hangs and timeouts using the EIDE disk in my computer.
 The controller is a Abit Hot Rod 66 and Maxtor Diamond Max 54098U8.
 I use the 80 pin cable from the Abit EIDE controller special for UDMA.
 
 Messages are:
 ad4: READ command timeout - resetting
 ata2: resetting devices
 
 ad4: WRITE command timeout - resetting
 ata2: resetting devices .. done

You have a config problem
 atapci0: Intel PIIX3 ATA controller at device 7.1 on pci0
 atapci0: Busmastering DMA not enabled
 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x
 ata0: probe allocation failed
 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0001
 ata1: probe allocation failed
 atapci1: HighPoint HPT366 ATA66 controller port 
0xa400-0xa4ff,0xa000-0xa003,0x9c00-0x9c07 irq 15 at device 14.0 on pci0
 ata2: iobase=0x9c00 altiobase=0xa000 bmaddr=0xa400
 ata2: at 0x9c00 on atapci1
 atapci2: HighPoint HPT366 ATA66 controller port 
0xb000-0xb0ff,0xac00-0xac03,0xa800-0xa807 irq 15 at device 14.1 on pci0
 ata3: iobase=0xa800 altiobase=0xac00 bmaddr=0xb000
 ata3: probe allocation failed

Now where did this come form:
 ata4: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x
 ata4: mask=00 status0=ff status1=ff
 ata4: probe allocation failed

 ata2-master: success setting up UDMA4 mode on HPT366 chip
 ad4: Maxtor 54098U8/DA620CQ0 ATA-5 disk at ata2 as master
 ad4: 39082MB (80041248 sectors), 79406 cyls, 16 heads, 63 S/T, 512 B/S
 ad4: 16 secs/int, 1 depth queue, UDMA66
 ad4: piomode=4 dmamode=2 udmamode=4 cblid=1
 
 # ATA and ATAPI devices
 deviceata0at isa? port IO_WD1 irq 14
 #device   ata1at isa? port IO_WD2 irq 15
 deviceata
 deviceatadisk # ATA disk drives
 #device   atapicd # ATAPI CDROM drives
 #device   atapifd # ATAPI floppy drives
 #device   atapist # ATAPI tape drives
 options   ATA_STATIC_ID   #Static device numbering
 #options  ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices

make that:

deviceata
deviceatadisk
options   ATA_STATIC_ID

-Søren


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

extern variables in shared libraries broken (ld.so or mmap bug)

2000-02-22 Thread Martin Cracauer


I am trying to hunt the strptime(..., "%+", ...) bug down. It looks
like a showstopper dynamic linker bug in 4.0 now. I suspect that
extern variables located in shared variables are broken, either by a
ld.so or a mmap bug.

In a dynamically linked program, it looks like the address of the
symbol "extern char *tzname[];" changes at runtime. You can write to
it as much as you like, but if you read it, the address points to the
void and the program dumps core. gdb displays very odd stuff, probably
reflecting a change in the underlying memory mapping.

When you link the program statically, it runs fine.

Try this program:

#include stdio.h
#include time.h

int
main(void)
{
  fprintf(stderr, "Address of tzname: %p\n", tzname);

  tzname[0] = "ERA";
  fprintf(stderr, "Address of tzname: %p\n", tzname);
  tzname[1] = "ERA";
  fprintf(stderr, "Address of tzname: %p\n", tzname);

  tzset();

  fprintf(stderr, "Address of tzname: %p\n", tzname);

  fprintf(stderr, "Values: '%s', '%s'\n", tzname[0], tzname[1]);

  return 0;
}

Run it in gdb, using this .gdbinit:

file test2
b main
r
display tzname
n
n

Breakpoint 1, 0x80484ab in main () at test2.c:7
7 fprintf(stderr, "Address of tzname: %p\n", tzname);
Address of tzname: 0x8049638
9 tzname[0] = "ERA";
1: {data variable, no debug info} (void *) 0x8049638 = 671997369
10fprintf(stderr, "Address of tzname: %p\n", tzname);
1: {data variable, no debug info} (void *) 0x8049638 = 134514018


Now, look at the addresses printed by gdb: The hex addresses are the
same, but the decimal ones are not.

Also, the type of variable tzname is defined in scope, gdb should be
able to gather it.

Further down, when accessing tzname[0] or tzname[1] for reading, the
program dumps core, both when running in gdb and running standalone.

As I said, everything works fine when linking statically. In
3.4-stable, all is well for static and dynamic linking.

Martin
-- 
%
Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/
  Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536


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

Re: Big ATA problems

2000-02-22 Thread Nick Hibma



Maybe this is a silly suggestion, but could someone with a card like
that boot it in a Windows environment and tell us what that hardware
manager tells us about hardware requirements the card would have if it
is configured for the '0x160' address (whatever that configuration is
on the card I don't know)?

Nick

   A typical isic hardware has an ISAC and an HSCX chip onboard. The ISAC
   chip does the D-channel handling and uses offsets 0-0x2b and 0x30-0x3b,
   the HSCX (B-channels) uses offsets 0-0x3b and 0x40-0x73.
  
  But in the case of the teles16.3, it does _not_ use offsets 0x00-0x3b in
  the HSCX or ISAC: the ASIC on the card has 'folded' the address space so
  that the fifo appears at an address 3 bytes after the last register (0x3e
  with the current scheme - see tels0163_read_fifo()).
 
 Oh yes, you are right! I was (and am still a bit) confused.
 
 So it uses 0x20-0x3e for the ISAC and 0x20-0x3e and 0x60-0x7e for the HSCX
 and at least three bytes at its base address, right ?
 
 This makes sense. Now the real question left is are this the only locations
 where the card is driving the bus ?
 
 hellmuth
 -- 
 Hellmuth Michaelis[EMAIL PROTECTED]   Hamburg, Europe
  We all live in a yellow subroutine, yellow subroutine, yellow subroutine ...
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 

--
[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: ATA errors

2000-02-22 Thread Nick Hibma


 I cvsupped this morning and I just had a chance to build a new kernel, and
 now I get a "cannot mount root" and it drops into some kind of commandline
 where I can enter a root for it to mount. This is the error it gives me
 now:
 
 ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY
 ata0-slave: ata_command: timeout waiting for intr
 ata0-slave: identify failed
 
 I went through this this morning.  If you are loading modules from the
 boot loader, load them later, like from rc.conf.  I'm not sure what
 broke there, but it's a good workaround.


Well, the same seems to apply to some OHCI host controllers. They fail
to work as well if preloaded or postloaded, but do work if they are
compiled into the kernel. I haven't tried yet whether the compiled USB
support fails if a module is preloaded though. My gut feeling is that
this must be related. I think, and this is just a bad guess, that this
broke around 2 weeks ago. I'll see if I can run a few test kernels this
evening.

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: Crashing netscape?

2000-02-22 Thread Alex


I will try this and see if it helps.

Cheers,

Alex

On Mon, Feb 21, 2000 at 06:56:41PM -0500, Bryan Liesner wrote:
 On Mon, 21 Feb 2000, Alex Le Heux wrote:
 
 Hi,
 
 Am I the only one who's experiencing an amzing amount of crashes on
 Netscape?
 
 It's been going on for quite some time now (months), upgrading Netscape or
 switching from the Linux to the FreeBSD to the BSDI version doesn't help.
 The most stable version seems to be the Linux version, but that even
 crashes 5-10 times per day. It will *always* crash when a page uses java,
 but I've not been able to find a non-java page that will always crash it.
 
 Netscape would always crash on me when loading a java applet - I found
 that if you define both the scaled and unscaled fonts in XF86Config as
 below that all the java related crashes go away.
 
 It still crashes occasionally on complex pages that load up a million
 different frames, though.
 
 Section "Files"
   RgbPath"/usr/X11R6/lib/X11/rgb"
   FontPath   "/usr/X11R6/lib/X11/fonts/75dpi"
   FontPath   "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
   FontPath   "/usr/X11R6/lib/X11/fonts/misc"
   FontPath   "/usr/X11R6/lib/X11/fonts/misc:unscaled"
   ModulePath "/usr/X11R6/lib/modules"
 EndSection
 
 Hope this helps.
 
 -Bryan
 
 

-- 
---
I dabble in techno-house and sometimes,
I do that badass hip-hop thang...
But the F U N K gets me every time!


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

Re: Panic (TCP)


It looks fine to me.

Perhaps Garrett has something to say about it?

-- 
Jeroen Ruigrok van der Werven  Network- and systemadministrator
[EMAIL PROTECTED]  bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70  http://www.bart.nl


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

Re: 0208-CURRENT and CD-Changer


It seems Morten Seeberg wrote:
 I have a Teac 6 CD changer (acd0: CDROM with 6 CD changer CD-C68E at
 ata1-master using PIO4), which works just fine in 3.x except for the usual
 error message when the CD-ROM drive is empty and I start up
 /stand/sysinstall), but in subj. when starting /stand/sysinstall (this also
 happens when installing), it takes a LNG time to start, and these are
 some of the errors that appear:

I've just yesterday committed some updates to the changercode, that
might solve your problem...

-Søren


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

Re: Interesting failure mode for static linking with shared libs.

2000-02-22 Thread Jordan K. Hubbard


 As a workaround for a static binary, you should be able to use
   -Xlinker -Bstatic
 instead of
   -static

Actually, it appears that just -Xlinker is necessary; it works
fine in conjunction with -static.  Thanks for this most helpful
tip!  I can see a *lot* of scenarios where I'll be using
-Xlinker in the future.  I didn't even know about that flag. :)

- Jordan


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

ABIT BP6, UDMA-66 and wdc AC310200

2000-02-22 Thread Arun Sharma


I have the above hardware combination and here's the dmesg from 
4.0-current:
 
atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0
atapci1: HighPoint HPT366 ATA66 controller port 
0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0
ata2: at 0xac00 on atapci1
atapci2: HighPoint HPT366 ATA66 controller port 
0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0
ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33

How do I get my disk to work in UDMA66 mode ? Is it supported with for
my disk ?

http://www.westerndigital.com/service/FAQ/dtr.html lists my disk as
ATA-66. 

What am I doing wrong ?

-Arun


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

Re: Crypto progress! (And a Biiiig TODO list)

2000-02-22 Thread Mark Murray


 Paul Richards [EMAIL PROTECTED] writes:
 
  The daemon approach actually has benfits that I'm keen on that aren't
  related to security. A single point of access to the data means that the
  backend can be changed so that passwords can be in a different file or a
  database, without having to worry about rebuilding all the binaries. You
  could even split users across different back end systems.
 
 This sounds like PAM, doesn't it?

One of the prime uses for the tool will be PAM.

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


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

Re: ABIT BP6, UDMA-66 and wdc AC310200


It seems Arun Sharma wrote:
 I have the above hardware combination and here's the dmesg from 
 4.0-current:
  
 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0
 atapci1: HighPoint HPT366 ATA66 controller port 
0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0
 ata2: at 0xac00 on atapci1
 atapci2: HighPoint HPT366 ATA66 controller port 
0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0
 ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33
 
 How do I get my disk to work in UDMA66 mode ? Is it supported with for
 my disk ?


Do you have the prober 80pin cable ?? if so please provide a verbose boot...

-Søren


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

Re: ABIT BP6, UDMA-66 and wdc AC310200

2000-02-22 Thread nnd


In [EMAIL PROTECTED] Arun Sharma [EMAIL PROTECTED] wrote:

What kind of cable do yuo use ?
Is it 80-wire one ?
N.Dudorov


 I have the above hardware combination and here's the dmesg from 
 4.0-current:
  
 atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0
 atapci1: HighPoint HPT366 ATA66 controller port 
0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0
 ata2: at 0xac00 on atapci1
 atapci2: HighPoint HPT366 ATA66 controller port 
0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0
 ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33
 
 How do I get my disk to work in UDMA66 mode ? Is it supported with for
 my disk ?
 
 http://www.westerndigital.com/service/FAQ/dtr.html lists my disk as
 ATA-66. 
 
 What am I doing wrong ?
 
   -Arun
 
 


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

Re: timeout problems HighPoint HPT366 ATA66 controller 40 GB Diamond Max Plus


On Tue, Feb 22, 2000 at 09:32:43AM +0100, Soren Schmidt wrote:
 You have a config problem

Oh ...

 Now where did this come form:
  ata4: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x
  ata4: mask=00 status0=ff status1=ff
  ata4: probe allocation failed
 
  ata2-master: success setting up UDMA4 mode on HPT366 chip
  ad4: Maxtor 54098U8/DA620CQ0 ATA-5 disk at ata2 as master
  ad4: 39082MB (80041248 sectors), 79406 cyls, 16 heads, 63 S/T, 512 B/S
  ad4: 16 secs/int, 1 depth queue, UDMA66
  ad4: piomode=4 dmamode=2 udmamode=4 cblid=1

Hmmm...

  # ATA and ATAPI devices
  device  ata0at isa? port IO_WD1 irq 14

Thought, this would be necessary.

  #device ata1at isa? port IO_WD2 irq 15
  device  ata
  device  atadisk # ATA disk drives
  #device atapicd # ATAPI CDROM drives
  #device atapifd # ATAPI floppy drives
  #device atapist # ATAPI tape drives
  options ATA_STATIC_ID   #Static device numbering
  #optionsATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices
 
 make that:
 
 deviceata
 deviceatadisk
 options   ATA_STATIC_ID

Will try that. BTW, I tried this night (til 5am *sigh*)
to make the device run under the Boards IDE controller.

To make that happen I did the (probably mistake), to 
set a cylinder limitation jumper and install a special
BIOS on the disk using the MaxBlast software from Maxtors
ftp site. Since then the disk only had 4111cyl/255heads/64sectors
=66043215 sectors.
Now the drive ran fine under Windows and FreeBSD, but when I
removed the jumper on the disk and tried again the abit EIDE
controller, the disk wasn't recognized anymore.
O.k. at 5am I was f***ing tired... Did I do something wrong
to my disk using this maxtor utility ? Does somebody know,
if there is a magic trick, to remove the BIOS ?

I'll now try, what FreeBSD says to the drive, when I install
the new kernel and if I remove the jumpers...

Andreas ///

-- 
Andreas Klemm  http://www.FreeBSD.ORG/~andreas
 http://www.freebsd.org/~fsmp/SMP/SMP.html
   powered by Symmetric MultiProcessor FreeBSD
Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html



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

kdelibs port broken?


I am trying to build the kdelibs port on a -current that is 2 days old..
It fails like so...

gmake[2]: Entering directory
`/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore'
/usr/X11R6/bin/moc ./kconfig.h -o kconfig.moc
/usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol
"_vt$9exception"
gmake[2]: *** [kconfig.moc] Error 1
gmake[2]: Leaving directory
`/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore'

Now, I'd look this up in the mailing lists, but the search is still down :(

I do remember something about C++ stuff needing to be recompiled (which is
why I'm rebuilding kdelibs in the first place)..

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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

Re: status of 'device awe' ?


-On [2221 21:15], Lyndon Nerenberg ([EMAIL PROTECTED]) wrote:
LINT has an entry for an 'awe' device, however there doesn't appear
to be any corresponding source code in the tree. Is this device dead?
If so, the entry should be removed from LINT, or an appropriate
comment added.

device pcm
device sbc

Should be used instead.

I am so in favor of just declaring voxware dead...  But the armchair
generals wouldn't like that.

-- 
Jeroen Ruigrok van der Werven  Network- and systemadministrator
[EMAIL PROTECTED]  bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70  http://www.bart.nl


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

Re: timeout problems HighPoint HPT366 ATA66 controller 40 GB Diamond Max Plus


Hi Soren,


 make that:
 deviceata
 deviceatadisk
 options   ATA_STATIC_ID

did that: after kernel re-compilation
I created a new disklabel on the device
I used the whole disk
/dev/ad4c   /data   ufs rw  1   2
just for testing purposes.
Newfs'ing and mounting the filesystem went fine.
I enabled softupdates prior mounting.

But when I tried fire up bonnie -s 100
I soon get after nearly writing the 100 MB characterwise...

ad4: READ command timeout - resetting
ata2: resetting devices

And the whole system hangs - reset

Behind dmesg of a verbose boot my new kernel config as reference

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 #0: Tue Feb 22 12:11:23 CET 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/TITAN
Calibrating clock(s) ... TSC clock: 199426380 Hz, i8254 clock: 1193149 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
CPU: Pentium Pro (199.43-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x619  Stepping = 9
  Features=0xfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV
real memory  = 159383552 (155648K bytes)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x00345000 - 0x097f5fff, 155914240 bytes (38065 pages)
avail memory = 150921216 (147384K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
IOAPIC #0 intpin 16 - irq 15
IOAPIC #0 intpin 17 - irq 11
IOAPIC #0 intpin 18 - irq 10
IOAPIC #0 intpin 19 - irq 14
SMP: CPU0 apic_initialize():
 lint0: 0x0700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec0
bios32: Found BIOS32 Service Directory header at 0xc00fac30
bios32: Entry = 0xfb0b0 (c00fb0b0)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xb0e0
pnpbios: Found PnP BIOS data at 0xc00fbc30
pnpbios: Entry = f:bc58  Rev = 1.0
Other BIOS signatures found:
ACPI: 
Preloaded elf kernel "kernel" at 0xc0329000.
ccd0-3: Concatenated disk drivers
Pentium Pro MTRR support enabled
SMP: CPU0 bsp_apic_configure():
 lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff
pci_open(1):mode 1 addr port (0x0cf8) is 0x805c
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=12378086)
npx0: math processor on motherboard
npx0: INT 16 interface
pci_open(1):mode 1 addr port (0x0cf8) is 0x
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=12378086)
pcib0: Host to PCI bridge on motherboard
found- vendor=0x8086, dev=0x1237, revid=0x02
class=06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
found- vendor=0x8086, dev=0x7000, revid=0x01
class=06-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
found- vendor=0x8086, dev=0x7010, revid=0x00
class=01-01-80, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
found- vendor=0x102b, dev=0x0519, revid=0x01
class=03-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=15
map[10]: type 1, range 32, base e000, size 14
map[14]: type 1, range 32, base e100, size 23
found- vendor=0x10b7, dev=0x9001, revid=0x00
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=14
map[10]: type 1, range 32, base 9400, size  6
found- vendor=0x1102, dev=0x0002, revid=0x04
class=04-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
intpin=a, irq=10
map[10]: type 1, range 32, base 9800, size  5
found- vendor=0x1102, dev=0x7002, revid=0x01
class=09-80-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
map[10]: type 1, range 32, base 9c00, size  3
found- vendor=0x9004, dev=0x8178, revid=0x00
class=01-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=11
map[10]: type 1, range 32, base a000, size  8
map[14]: type 1, range 32, base e200, size 12
found- vendor=0x1103, dev=0x0004, revid=0x01
class=01-80-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
intpin=a, irq=15
map[10]: type 1, range 32, base a400, size  3
map[14]: type 1, range 32, base a800, size  2
map[20]: type 1, range 32, base ac00, size  8
found-

Re: timeout problems HighPoint HPT366 ATA66 controller 40 GB Diamond Max Plus


It seems Andreas Klemm wrote:
 Newfs'ing and mounting the filesystem went fine.
 I enabled softupdates prior mounting.
 
 But when I tried fire up bonnie -s 100
 I soon get after nearly writing the 100 MB characterwise...
 
   ad4: READ command timeout - resetting
   ata2: resetting devices
 
 And the whole system hangs - reset

Hmm, this looks very wierd, how is your BIOS setup wrt to onboard
ATA channels ??
Try to use a "normal" ie 40pin cable, that will limit the disk to
UDMA33 mode, if that works, well...


-Søren


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

Re: Interesting failure mode for static linking with shared libs.

2000-02-22 Thread Bruce Evans


On Tue, 22 Feb 2000, Jordan K. Hubbard wrote:

  As a workaround for a static binary, you should be able to use
-Xlinker -Bstatic
  instead of
-static
 
 Actually, it appears that just -Xlinker is necessary; it works
 fine in conjunction with -static.  Thanks for this most helpful
 tip!  I can see a *lot* of scenarios where I'll be using
 -Xlinker in the future.  I didn't even know about that flag. :)

This is because `-Xlinker -static' is equivalent to `-Xlinker -Bstatic'
in the elf case.  Passing -static to the linker used to be a common
error.  The aout linker doesn't understand -static; it has sloppy args
checking and misinterprets -static as -s (strip).

-Xlinker alone is bogus.  -Xlinker is not an option; it modifies the
next option by causing it to be passed to the linker instead of
interpreted by the compiler.

I didn't know about -Xlinker either :-).  It is normally spelled `-Wl,'.

Bruce



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

Re: timeout problems HighPoint HPT366 ATA66 controller 40 GB Diamond Max Plus


On Tue, Feb 22, 2000 at 01:39:46PM +0100, Soren Schmidt wrote:
 Hmm, this looks very wierd, 

Oh yes ;-)

BTW no problem with win98 or Win2000 installation.

 how is your BIOS setup wrt to onboard ATA channels ??

 Try to use a "normal" ie 40pin cable, that will limit the disk to
 UDMA33 mode, if that works, well...

Will have to buy that. When I ran with the on board IDE chip I
had a drive mode (something like) mdma2. That worked even with
FreeBSD.

I now tried BIOS setup values.
First entered BIOS default values, which are turning off most
features, then I enabled SETUP defaults and then changed no
performance boosting things.

RAM Timing I changed to automatic 70ns, although I have 60 ns
RAM.

On chip PCI IDE is completely disabled.

Then I changed as a last resort method the mode to
hw.atamodes: ---,---,---,---,pio,---,---,---,  

Even with PIO the drive has problems, but is then able to recover:

ata2-master: success setting up PIO4 mode on HPT366 chip
ad4: invalid primary partition table: no magic
this is. because I newfs'd ad4c on the whole ... quick and dirty
for testing...

now bonnie -s 100

ad4: WRITE command timeout - resetting
ata2: resetting devices .. ata2: mask=01 status0=50 status1=00
ata2-master: success setting up PIO4 mode on HPT366 chip
done
ad4: timeout waiting for DRQ

How can I force the driver with kernel modifications to use
mdma2 mode or something like this ???

BTW, I have a 5 Slot PCI machine ...
in the first slot there is the abit controller in the last
the Matrox Millenium card. They share the same IRQ 15...

Is this sane ?

Or might my problem be SMP related ???

Well, have to go to the supermarket now ...
I'll remove one card later, to free one IRQ and will try to use
a single cpu kernel...


-- 
Andreas Klemm  http://www.FreeBSD.ORG/~andreas
 http://www.freebsd.org/~fsmp/SMP/SMP.html
   powered by Symmetric MultiProcessor FreeBSD
Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html



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

Re: Panic (TCP)

2000-02-22 Thread Yoshinobu Inoue


  If persist timer is working, and if it happen to timeout between
  callout_reset(tp-tt_rexmt, tp-t_rxtcur,
tcp_timer_rexmt, tp);
  and
  callout_stop(tp-tt_persist);
  then the panic might happen at tcp_setpersist().
 
 This should never happen, since this code is supposed to be running at
 splnet(), which is supposed to block timeouts.  Rather than papering
 over the problem, I'd like to understand how it's possible.

I also later thought so, but again I suspect that the part is
also one of the cause of the problem. Because as the value of
tp-t_rexmt at panic, retransmit timer also seemed to be
running at the time, and I can't find any other place which
might cause this situation.
Also I think anyway the patch is better to be applied.

My assumption might be wrong but I am now trying if I can
create some patch that make the problem very likely to happen.

Thanks,
Yoshinobu Inoue

 -GAWollman
 
 --
 Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
 [EMAIL PROTECTED]  | O Siem / The fires of freedom 
 Opinions not those of| Dance in the burning flame
 MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick


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

Re: kdelibs port broken?

2000-02-22 Thread Maxim Sobolev


Daniel O'Connor wrote:

 I am trying to build the kdelibs port on a -current that is 2 days old..
 It fails like so...

 gmake[2]: Entering directory
 `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore'
 /usr/X11R6/bin/moc ./kconfig.h -o kconfig.moc
 /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol
 "_vt$9exception"
 gmake[2]: *** [kconfig.moc] Error 1
 gmake[2]: Leaving directory
 `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore'

 Now, I'd look this up in the mailing lists, but the search is still down :(

 I do remember something about C++ stuff needing to be recompiled (which is
 why I'm rebuilding kdelibs in the first place)..

You have to rebuild qt2 first to be able to run moc.

-Maxim



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

Re: kdelibs port broken?


ON that subject, has anyone tried compiling the KDE port with the new QT145
port?

On 22-Feb-00 Maxim Sobolev wrote:
 Daniel O'Connor wrote:
 
 I am trying to build the kdelibs port on a -current that is 2 days old..
 It fails like so...

 gmake[2]: Entering directory
 `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore'
 /usr/X11R6/bin/moc ./kconfig.h -o kconfig.moc
 /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol
 "_vt$9exception"
 gmake[2]: *** [kconfig.moc] Error 1
 gmake[2]: Leaving directory
 `/usr/tmp/work/usr/ports/x11/kdelibs11/work/kdelibs-1.1.2/kdecore'

 Now, I'd look this up in the mailing lists, but the search is still down :(

 I do remember something about C++ stuff needing to be recompiled (which is
 why I'm rebuilding kdelibs in the first place)..
 
 You have to rebuild qt2 first to be able to run moc.
 
 -Maxim
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message


--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 22-Feb-00
Time: 07:39:55l
FreeBSD 3.4
--


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

Re: kdelibs port broken?

2000-02-22 Thread Ilmar S. Habibulin


On Tue, 22 Feb 2000, Daniel O'Connor wrote:

 I am trying to build the kdelibs port on a -current that is 2 days old..
 It fails like so...
[...]
 Now, I'd look this up in the mailing lists, but the search is still down :(
 
 I do remember something about C++ stuff needing to be recompiled (which is
 why I'm rebuilding kdelibs in the first place)..
I tryed to recompile them and failed. Qt builds fine, and kdelibs libs
compiled fine. The error occured at the linkage stage. :( So i switched to
kde-2.0(current). There i have another problems. libkhtml has undefined
simbol. But it compiles and works.




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

Promise Ultra66 + Seagate ATA/66 = Ultra ATA/33 :(


  Hi,

  I'm running recent 4.0-CURRENT and my Seagate Barracuda ST320430A
20GB hard drive connected with Promise Ultra66 card isn't recognized
as an Ultra ATA/66 drive but only /33.

  I'm sure I'm using a correct cable for the /66 drive and I confirmed
it works successfully in /66 on WinNT 4.0.

  Am I missing something or doing wrong?  Any suggestions are welcome.

-- kernel config file --
machine i386
cpu I686_CPU
ident   ARCHON
maxusers32
options INET
options FFS
options FFS_ROOT
options SOFTUPDATES
options MFS
options NFS
options MSDOSFS
options NTFS
options EXT2FS
options CD9660
options PROCFS
options NULLFS
options UNION
options PORTAL
options COMPAT_43
options SCSI_DELAY=3000
options UCONSOLE
options USERCONFIG
options VISUAL_USERCONFIG
options KTRACE
options SYSVSHM
options SYSVMSG
options SYSVSEM
options P1003_1B
options _KPOSIX_PRIORITY_SCHEDULING
options _KPOSIX_VERSION=199309L
options ICMP_BANDLIM
options DDB
options SMP
options APIC_IO
device  isa
device  eisa
device  pci
device  fdc0at isa? port IO_FD1 irq 6 drq 2
device  fd0 at fdc0 drive 0
device  ata
device  atadisk
options ATA_STATIC_ID
device  ahc
device  scbus
device  da
device  sa
device  cd
device  pass
device  atkbdc0 at isa? port IO_KBD
device  atkbd0  at atkbdc? irq 1
device  psm0at atkbdc? irq 12
device  vga0at isa?
pseudo-device   splash
device  sc0 at isa?
device  npx0at nexus? port IO_NPX irq 13
device  apm0at nexus? disable flags 0x20
device  pcm0
device  sio0at isa? port IO_COM1 flags 0x10 irq 4
device  sio1at isa? port IO_COM2 irq 3
device  ppc0at isa? irq 7
device  ppbus
device  lpt
device  plip
device  ppi
device  fxp
pseudo-device   loop
pseudo-device   ether
pseudo-device   sl  1
pseudo-device   ppp 1
pseudo-device   tun
pseudo-device   pty 16
pseudo-device   md
pseudo-device   vn
pseudo-device   bpf 4
options SHMMAXPGS=2049
options COMPAT_LINUX

-- 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 #29: Sat Feb 19 02:21:47 JST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/ARCHON
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (451.02-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
  
Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
real memory  = 268435456 (262144K bytes)
avail memory = 256925696 (250904K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec0
Preloaded elf kernel "kernel" at 0xc0361000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
vga-pci0: Matrox MGA G200 AGP graphics accelerator mem 
0xe100-0xe17f,0xe000-0xe0003fff,0xe400-0xe4ff at device 0.0 on pci1
isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
ata-pci0: Intel PIIX4 ATA-33 controller at device 7.1 on pci0
ata-pci0: Busmastering DMA not enabled
pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 19
Timecounter "PIIX"  frequency 3579545 Hz
chip1: Intel 82371AB Power management controller port 0x5000-0x500f at device 7.3 on 
pci0
ahc0: Adaptec 2940 Ultra2 SCSI adapter port 0xa400-0xa4ff mem 0xe892-0xe8920fff 
irq 17 at device 8.0 on pci0
ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs
fxp0: Intel EtherExpress Pro 10/100B Ethernet port 0xa800-0xa81f mem 
0xe880-0xe88f,0xe8921000-0xe8921fff irq 19 at device 9.0 on pci0
fxp0: Ethernet address 00:90:27:14:cf:35
pcm0: AudioPCI ES1370 port 0xac00-0xac3f irq 18 at device 10.0 on pci0
ata-pci1: Promise ATA-66 controller port 
0xc000-0xc03f,0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 mem 
0xe890-0xe891 irq 16 at device 12.0 on pci0
ata2 at 0xb000 irq -1 on ata-pci1
fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0:

Re: Promise Ultra66 + Seagate ATA/66 = Ultra ATA/33 :(


It seems Akinori -Aki- MUSHA wrote:
   Hi,
 
   I'm running recent 4.0-CURRENT and my Seagate Barracuda ST320430A
 20GB hard drive connected with Promise Ultra66 card isn't recognized
 as an Ultra ATA/66 drive but only /33.

Could I have a verbote boot log please, that would give some hints...

 ata-pci1: Promise ATA-66 controller port 
0xc000-0xc03f,0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 mem 
0xe890-0xe891 irq 16 at device 12.0 on pci0
 ata2 at 0xb000 irq -1 on ata-pci1
 ad4: 19569MB ST320430A [39761/16/63] at ata2-master using UDMA33

This probe suggests that you are not up to date on -current, that would
maybe also help...

-Søren


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

Re: ABIT BP6, UDMA-66 and wdc AC310200

2000-02-22 Thread Arun Sharma


On Tue, Feb 22, 2000 at 11:54:40AM +0100, Soren Schmidt wrote:
 It seems Arun Sharma wrote:
  I have the above hardware combination and here's the dmesg from 
  4.0-current:
   
  atapci0: Intel PIIX4 ATA33 controller port 0xf000-0xf00f at device 7.1 on pci0
  atapci1: HighPoint HPT366 ATA66 controller port 
0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0
  ata2: at 0xac00 on atapci1
  atapci2: HighPoint HPT366 ATA66 controller port 
0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807 irq 11 at device 19.1 on pci0
  ad4: 9787MB WDC AC310200R [19885/16/63] at ata2-master using UDMA33
  
  How do I get my disk to work in UDMA66 mode ? Is it supported with for
  my disk ?
 
 
 Do you have the prober 80pin cable ?? if so please provide a verbose boot...

Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very
unscientific benchmark that I ran didn't seem to produce much of a difference
between UDMA33 and UDMA66. In both cases, I got roughly 13 MB/s.

# dd if=/dev/ad4s2 of=/dev/null bs=40960k count=10
10+0 records in
10+0 records out
419430400 bytes transferred in 30.797045 secs (13619177 bytes/sec)

Can anyone point me to some benchmarks and comment about the improvement ?

-Arun


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

Re: ABIT BP6, UDMA-66 and wdc AC310200


It seems Arun Sharma wrote:
  Do you have the prober 80pin cable ?? if so please provide a verbose boot...
 
 Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very
 unscientific benchmark that I ran didn't seem to produce much of a difference
 between UDMA33 and UDMA66. In both cases, I got roughly 13 MB/s.

There are almost no mesureable difference between UDMA33 and UDMA66, all
mesurements I've done (and have read about) sees little if no difference,
in fact some drives can be faster under UDMA33 even if they support the
higher rate too.

 # dd if=/dev/ad4s2 of=/dev/null bs=40960k count=10
 10+0 records in
 10+0 records out
 419430400 bytes transferred in 30.797045 secs (13619177 bytes/sec)

Thats probably close to what your drive can pull of the platters...
I get 22-23MB/sec off an IBM DPTA drive here with  1% cpu usage,
so the driver is not the problem..
I have a config with 7 disks online, giving me a raw throughput
of ~100MB/s sustained, that is about the limit of what can be done
over the PCI bus...

-Søren


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

Re: Crashing netscape?

2000-02-22 Thread Steve Hocking


There was some discussion of this over on the XFree mailing lists, and it 
transpired that netscape was using a pointer to some memory that had been 
freed some time back. This showed up in cases where you open up a stack of 
windows and then close them at random. There was a patch to work around this 
for libXt (I think).


Stephen



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

Re: ABIT BP6, UDMA-66 and wdc AC310200

2000-02-22 Thread Joseph Thomas


 
 It seems Arun Sharma wrote:
   Do you have the prober 80pin cable ?? if so please provide a verbose boot...
  
  Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very
  unscientific benchmark that I ran didn't seem to produce much of a difference
  between UDMA33 and UDMA66. In both cases, I got roughly 13 MB/s.
 
 There are almost no mesureable difference between UDMA33 and UDMA66, all
 mesurements I've done (and have read about) sees little if no difference,
 in fact some drives can be faster under UDMA33 even if they support the
 higher rate too.
 
  # dd if=/dev/ad4s2 of=/dev/null bs=40960k count=10
  10+0 records in
  10+0 records out
  419430400 bytes transferred in 30.797045 secs (13619177 bytes/sec)
 
 Thats probably close to what your drive can pull of the platters...
 I get 22-23MB/sec off an IBM DPTA drive here with  1% cpu usage,
 so the driver is not the problem..

Look at your drive specs. I have one drive (Maxtor) with specs that
say ~34MB to/from media and 66MB to/from interface (bus). Another piece of
the puzzle is the amount of drive cache buffer. Again, I've seen between
512KB and 2MB. Mileage will vary... [It's the old 'burst rate of X' where
the following 378 conditions must be met to reach the burst level...]



 I have a config with 7 disks online, giving me a raw throughput
 of ~100MB/s sustained, that is about the limit of what can be done
 over the PCI bus...
 
 -Søren
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 


-- 
Joseph Thomas   E/Mail:  [EMAIL PROTECTED]
Network Computing Services, Inc. [EMAIL PROTECTED]
1200 Washington Ave So. Tel: +1 612 337 3558
Minneapolis, MN 55415-1227  FAX: +1 612 337 3400

An elephant is a mouse with an operating system.


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

Hardware for 4.0

2000-02-22 Thread mwlucas


Hello,

I'm purchasing a server to run 4.0 on.  It won't be in production
immediately, but I need to get a quote ASAP.

What SCSI card would people recommend?  It doesn't need RAID.
Any particular SCSI tape drive?

I'll probably buy a midrange Asus motherboard and a nice Intel fxp
NIC to go on it.  Any other recommendations?

Thanks,
==ml


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

Re: Promise Ultra66 + Seagate ATA/66 = Ultra ATA/33 :(


At Tue, 22 Feb 2000 18:14:23 +0100 (CET),
Soren Schmidt [EMAIL PROTECTED] wrote:
 Could I have a verbote boot log please, that would give some hints...

Sorry but could you tell me how to increase verbosity?

  ata-pci1: Promise ATA-66 controller port 
0xc000-0xc03f,0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 mem 
0xe890-0xe891 irq 16 at device 12.0 on pci0
  ata2 at 0xb000 irq -1 on ata-pci1
  ad4: 19569MB ST320430A [39761/16/63] at ata2-master using UDMA33
 
 This probe suggests that you are not up to date on -current, that would
 maybe also help...

Okay, I'll update the kernel, but I built it last Saturday from the
then up-to-date source tree.  Not recent enough?

-- 
   /
  /__  __
 / )  )  ) )  /
Akinori -Aki- MUSHA aka / (_ /  ( (__(  [EMAIL PROTECTED]

"If you choose not to decide you still have made a choice."


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

Re: Promise Ultra66 + Seagate ATA/66 = Ultra ATA/33 :(


On Wed, Feb 23, 2000 at 02:55:27AM +0900, Akinori -Aki- MUSHA wrote:
 At Tue, 22 Feb 2000 18:14:23 +0100 (CET),
 Soren Schmidt [EMAIL PROTECTED] wrote:
  Could I have a verbote boot log please, that would give some hints...
 
 Sorry but could you tell me how to increase verbosity?

set boot_verbose=1

in the boot loader

-- 
Andreas Klemm  http://www.FreeBSD.ORG/~andreas
 http://www.freebsd.org/~fsmp/SMP/SMP.html
   powered by Symmetric MultiProcessor FreeBSD
Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html



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

Re: Hardware for 4.0

2000-02-22 Thread Dan Moschuk



| What SCSI card would people recommend?  It doesn't need RAID.
| Any particular SCSI tape drive?

I like the Adapdec 2940 cards for low-medium end servers.

| I'll probably buy a midrange Asus motherboard and a nice Intel fxp
| NIC to go on it.  Any other recommendations?

The fxp cards are good, but I usually use the 3Com 905[BC] cards.

-- 
Dan Moschuk ([EMAIL PROTECTED])
"Waste not fresh tears on old griefs."


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

Upgrade to 4.0 current

2000-02-22 Thread Christopher T. Griffiths


Hello,

I was trying to upgrade from 3.4 -stable to 4.0 Current to test it out for
the coming release of 4.0.


I cvsup'd as of this morning at 10:00am and did a make buildworld.  Then
followed by a shutdown now then make installworld.


I then got the following error:

=== lib/csu/i386-elf
install -c -o root -g wheel -m 444  crt1.o /usr/lib/crt1.o
install -c -o root -g wheel -m 444  crtbegin.o /usr/lib/crtbegin.o
install -c -o root -g wheel -m 444  crtend.o /usr/lib/crtend.o
install -c -o root -g wheel -m 444  crti.o /usr/lib/crti.o
install -c -o root -g wheel -m 444  crtn.o /usr/lib/crtn.o
install -c -o root -g wheel -m 444  gcrt1.o /usr/lib/gcrt1.o
install -c -o root -g wheel -m 444  crtbegin.So /usr/lib/crtbeginS.o
install -c -o root -g wheel -m 444  crtend.So /usr/lib/crtendS.o
=== lib/libcom_err
cd /usr/src/lib/libcom_err   install -C -o root -g wheel -m 444
/usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/include
cd /usr/src/lib/libcom_err   install -C -o root -g wheel -m 444
/usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include
install -c -o root -g wheel -m 444   libcom_err.a /usr/lib
install -c -o root -g wheel -m 444   libcom_err_p.a /usr/lib
install -c -s -o root -g wheel -m 444 libcom_err.so.2 /usr/lib
ln -sf libcom_err.so.2 /usr/lib/libcom_err.so
install -c -o root -g wheel -m 444 com_err.3.gz  /usr/share/man/man3
=== lib/libcom_err/doc
install-info --quiet  --defsection="Programming  development tools."
--defentry="* libcom_err: (com_err).A Common Error Description
Library for UNIX."  com_err.info /usr/share/info/dir
install-info: unrecognized option `--defsection=Programming  development
tools.'
Try `install-info --help' for a complete list of options.
*** Error code 1

Stop.
*** Error code 1

Stop.


If anyone can give me any pointers as to how to fix this that would be
great.

Thanks

Chris


---
Christopher T. Griffiths
Engineering Department
Quansoo Group Inc.
[EMAIL PROTECTED]




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

Re: Promise Ultra66 + Seagate ATA/66 = Ultra ATA/33 :(


  Alright, I booted the system with boot_verbose=1, and the dmesg
output was as follows.  I wish this would help your investigation.

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 #30: Wed Feb 23 03:50:42 JST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/ARCHON
Calibrating clock(s) ... TSC clock: 451010773 Hz, i8254 clock: 1193150 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
CPU: Pentium II/Pentium II Xeon/Celeron (451.02-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x665  Stepping = 5
  
Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
real memory  = 268435456 (262144K bytes)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0037e000 - 0x0fff7fff, 264740864 bytes (64634 pages)
fb: new array size 4
avail memory = 256921600 (250900K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
SMP: CPU0 apic_initialize():
 lint0: 0x0700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  0, version: 0x00040011, at 0xfee0
 cpu1 (AP):  apic id:  1, version: 0x00040011, at 0xfee0
 io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec0
bios32: Found BIOS32 Service Directory header at 0xc00faf10
bios32: Entry = 0xfb390 (c00fb390)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xb3c0
pnpbios: Found PnP BIOS data at 0xc00fbff0
pnpbios: Entry = f:c018  Rev = 1.0
Other BIOS signatures found:
ACPI: 
Preloaded elf kernel "kernel" at 0xc0362000.
Pentium Pro MTRR support enabled
md0: Malloc disk
Creating DISK md0
SMP: CPU0 bsp_apic_configure():
 lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff
pci_open(1):mode 1 addr port (0x0cf8) is 0x805c
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=71908086)
npx0: math processor on motherboard
npx0: INT 16 interface
pci_open(1):mode 1 addr port (0x0cf8) is 0x
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=71908086)
pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard
found- vendor=0x8086, dev=0x7190, revid=0x02
class=06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
map[10]: type 1, range 32, base e800, size 23
found- vendor=0x8086, dev=0x7191, revid=0x02
class=06-04-00, hdrtype=0x01, mfdev=0
subordinatebus=1secondarybus=1
found- vendor=0x8086, dev=0x7110, revid=0x02
class=06-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
found- vendor=0x8086, dev=0x7111, revid=0x01
class=01-01-80, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
Freeing (NOT implemented) redirected PCI irq 11.
found- vendor=0x8086, dev=0x7112, revid=0x01
class=0c-03-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=d, irq=19
map[20]: type 1, range 32, base a000, size  5
found- vendor=0x8086, dev=0x7113, revid=0x02
class=06-80-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
map[90]: type 1, range 32, base 5000, size  4
Freeing (NOT implemented) redirected PCI irq 9.
found- vendor=0x9005, dev=0x0010, revid=0x00
class=01-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=17
map[10]: type 1, range 32, base a400, size  8
map[14]: type 1, range 64, base e892, size 12
Freeing (NOT implemented) redirected PCI irq 11.
found- vendor=0x8086, dev=0x1229, revid=0x05
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=19
map[10]: type 1, range 32, base e8921000, size 12
map[14]: type 1, range 32, base a800, size  5
map[18]: type 1, range 32, base e880, size 20
Freeing (NOT implemented) redirected PCI irq 5.
found- vendor=0x1274, dev=0x5000, revid=0x01
class=04-01-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=18
map[10]: type 1, range 32, base ac00, size  6
Freeing (NOT implemented) redirected PCI irq 10.
found- vendor=0x105a, dev=0x4d38, revid=0x01
class=01-80-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=16
map[10]: type 1, range 32, base b000, size  3
map[14]: type 1, range 32, base b400, size  2
map[18]: type 1, range 32, base b800, size  3
map[1c]: type 1, range 32, base bc00, size  2
map[20]: type 1, range 32,

Re: Hardware for 4.0

2000-02-22 Thread Garrett Wollman


On Tue, 22 Feb 2000 11:06:07 -0800 (PST), "Rodney W. Grimes" 
[EMAIL PROTECTED] said:

 IBM Hard drives...

If you can actually get them  Last time I bought a drive we
weren't able to get IBM in any reasonable timeframe and ended up with
a Seagate instead.  (And that Cheetah 18LP's not a bad drive, either.)

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED]  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick


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

Re: Hardware for 4.0

2000-02-22 Thread Rodney W. Grimes


 On Tue, 22 Feb 2000 11:06:07 -0800 (PST), "Rodney W. Grimes" 
[EMAIL PROTECTED] said:
 
  IBM Hard drives...
 
 If you can actually get them  Last time I bought a drive we
 weren't able to get IBM in any reasonable timeframe and ended up with
 a Seagate instead.  (And that Cheetah 18LP's not a bad drive, either.)

Should you run into that problem again give me a call.  We deal directly
with one of the larger official distributors of IBM hard drives.  Last
inventory check showed about 4,000+ IBM 25L1900/25L1910's on the shelf.


-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)   [EMAIL PROTECTED]


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

Re: Promise Ultra66 + Seagate ATA/66 = Ultra ATA/33 :(


It seems Akinori -Aki- MUSHA wrote:
   Alright, I booted the system with boot_verbose=1, and the dmesg
 output was as follows.  I wish this would help your investigation.

It does:

 ata2-master: success setting up UDMA2 mode on Promise chip
 ad4: ST320430A/3.11 ATA-4 disk at ata2 as master
 ad4: 19569MB (40079088 sectors), 39761 cyls, 16 heads, 63 S/T, 512 B/S
 ad4: 16 secs/int, 1 depth queue, UDMA33
 ad4: piomode=4 dmamode=2 udmamode=2 cblid=1
   ^^

The disk reports it can do at max UDMA2 mode (ATA33), so thats why
the ata driver dont put it at UDMA4 (ATA66)...

-Søren


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

Panic (ffs) #2


And here we are again.

This time on another disk:

dev = #amrd/0x20004, block = 2048, fs = /news/spool
panic: ffs_blkfree: freeing free block
Debugger("panic")
Stopped at  Debugger+0x35:  movb$0,in_Debugger.372
db trace
Debugger(c01e7ee3) at Debugger+0x35
panic(c01f27e0,c01f27c0,c1ccc894,800,c1d0d0d4) at panic+0x70
ffs_blkfree(c1db6d00,800,2000,0,d98cfe44) at ffs_blkfree+0x1dd
ffs_indirtrunc(c1db6d00,fff4,10bab0,,0,d98cfd84) at
ffs_indirtrunc+0x219
ffs_truncate(d8c79da0,0,0,0,c1d4d700) at ffs_truncate+0x6fd
ufs_setattr(d98cfec8,d98cff3c,c0171857,d98cfec8,d98b52a0) at
ufs_setattr+0x1ce
ufs_vnoperate(d98cfec8,d98b52a0,c0206bac,d98cff80,d8c79da0) at
ufs_vnoperate+0x15
ftruncate(d98b52a0,d98cff80,8098900,bfbff608,bfbf741f) at
ftruncate+0x113
syscall(2f,280a002f,bfbf002f,bfbf741f,bfbff608) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26

Dumping the 512 MB to disk now.

See my previous Panic (ffs) mail on CURRENT for a almost exact problem.

No soft-updates.  Two different disks on two different controllers now.

Current from 21 Feb.

-- 
Jeroen Ruigrok van der Werven  Network- and systemadministrator
[EMAIL PROTECTED]  bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70  http://www.bart.nl


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

Re: Hardware for 4.0

2000-02-22 Thread Kenneth D. Merry


On Tue, Feb 22, 2000 at 14:25:45 -0500, Garrett Wollman wrote:
 On Tue, 22 Feb 2000 11:06:07 -0800 (PST), "Rodney W. Grimes" 
[EMAIL PROTECTED] said:
 
  IBM Hard drives...
 
 If you can actually get them  Last time I bought a drive we
 weren't able to get IBM in any reasonable timeframe and ended up with
 a Seagate instead.  (And that Cheetah 18LP's not a bad drive, either.)

Yeah, the Seagates are good too.  I wish they'd come up with temperature
sensors like IBM, though. :)

But I'm surprised you had trouble getting IBM drives.  NECX (www.necx.com)
at least, usually has most IBM SCSI disks in stock.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


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

Re: Panic (ffs) #2

2000-02-22 Thread Thomas David Rivers


 
 And here we are again.
 
 This time on another disk:
 
 dev = #amrd/0x20004, block = 2048, fs = /news/spool
 panic: ffs_blkfree: freeing free block
 Debugger("panic")
 Stopped at  Debugger+0x35:  movb$0,in_Debugger.372
 db trace
 Debugger(c01e7ee3) at Debugger+0x35
 panic(c01f27e0,c01f27c0,c1ccc894,800,c1d0d0d4) at panic+0x70
 ffs_blkfree(c1db6d00,800,2000,0,d98cfe44) at ffs_blkfree+0x1dd


 Aha!  The Dave Rivers' memorial panic rears its ugly head!

 This is exactly the panic's I reported years ago; but we've never
 been able to track down... [Even the same block number I believe]

 You may want to scan the archives to read more about my investigations;
 which never went anywhere... (sigh)  I describe a way to reproduce
 it on some versions of FreeBSD, you might want to see if you can
 get a reliable reproduction, etc...

- Dave Rivers - 





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

Re: timeout problems HighPoint HPT366 ATA66 controller 40 GB Diamond Max Plus


It seems Andreas Klemm wrote:
 On Tue, Feb 22, 2000 at 01:39:46PM +0100, Soren Schmidt wrote:
  Try to use a "normal" ie 40pin cable, that will limit the disk to
  UDMA33 mode, if that works, well...
 
 Hurray, using a normal cable works. I got 2 cables for $0
 from a friend in a computershop ;-) A freebsd user, which
 I gave a promotion CD last year ;-)
 
 dmesg | grep ata:
 
 atapci0: Intel PIIX3 ATA controller at device 7.1 on pci0
 atapci0: Busmastering DMA not enabled
 atapci1: HighPoint HPT366 ATA66 controller port 
0xac00-0xacff,0xa800-0xa803,0xa400-0xa407 irq 15 at device 14.0 on pci0
 ata2: at 0xa400 on atapci1
 atapci2: HighPoint HPT366 ATA66 controller port 
0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 irq 15 at device 14.1 on pci0
 ad4: 39082MB Maxtor 54098U8 [79406/16/63] at ata2-master using UDMA33
 
 Do you think there is a chance to get UDMA66 running, although
 for one disk UDMA/33 should be satisfactory ?

There are two posibilities, either the cable is bad or the disk is bad.
Since you could talk to it, and you didn't get ICRC errors, my bet is
that the particular Maxtor model is just as broken as most of its
other family memebers :(
However there is no mesurable difference between running ATA66
and ATA33 as long as you have only one disk pr channel, and if 
you have more than one, the difference is still not worth 
mentioning...

 BTW, what mode is MA DMA or something like this ? The abit supports
 two modes I never heard of before. PIO is known UDMA is known, but
 something like M DMA or MA DMA ???

That has to me MWDMA that the old 16MB/s mode, ata knows this mode
too, but only uses it if no UDMA mdoes are possible...

 Then an idea. What about something like atacontrol, to overwrite
 the speed settings, if you have to like in this case ? Would it
 be much work for you or worth the effort ?

Well, there are some pretty tricky things with that, some of the
controllers dont like you to step back in mode without serious
handholding and special code

 Would be fine to use the better cable with low speed...

As long as you dont get any ICRC errors due to bad cableing there
is no difference whatsoever...

-Søren


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

Re: openssl in -current

2000-02-22 Thread Joel Ray Holveck


 It would obviously not be hard to write a set of stubs for these
 things, getting those stubs called selectively in the "no real RSA"
 case also not being very difficult.  One way would be to put them in a
 lower version-numbered shared lib, like OpenBSD did it, so that the
 application would fall through to link against the stub version if
 librsaref.so.2 was not found.  Another, better way, would be to use
 weak symbols and a dlopen(), e.g.:
[snip]
 That way it's not an error to link against the openssl library without
 librsa, though if you do link with -lrsa and -lssl then you can also
 skip the stubs entirely and not encur the dlopen() overhead, something
 which makes the -static (or stand-alone) linkers happy.

I'm not familiar with OpenSSL's link lines, but here's a question.
Are linking with -lrsa and -lssl normally necessary, or is it normally
just -lssl?  If it't the latter, then programs that expect to link
against OpenSSL will succeed to build and link, but fail to run
properly.  I realize that every OS has its quirks for building
packages, but I find this sort of change vulgar.

Naturally, if OpenSSL-based programs *expect* to build against -lrsa
and -lssl, then I have no objections.

joelh

-- 
Joel Ray Holveck - [EMAIL PROTECTED]
   Fourth law of programming:
   Anything that can go wrong wi
sendmail: segmentation violation - core dumped


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

I have just read several documents from www.eff.org, www.rsa.com, and
www.openssl.org and have failed to find anything in there, that forbids us
from not using openssl's RSA version. RSA has a patent for the algorithm,
and they have provided a reference implementation to help the adoption of
the algorithm. In their license (RSAREF) it says you can't export the code
outside USA, but the US ITAR laws don't say anything about importing. So in
theory, if the CD was made outside the USA, then it could be imported
without a single problem.

I'm not a lawyer. Here's my take.

Let's consider that we are in Switzerland making the One Great CD that
I may legally use inside of the US. (We may assume that I also may
use it outside of the US, but that's irrelevant to this discussion.)
While I use this CD, I'm using the RSA algorithm. This is covered by
US patent 4,405,829, meaning that I have to have RSA Labs' permission
to use it.

I am now obligated to obtain their permission. I have their
permission to use it, so long as I'm using RSAREF, and I'm using it
for non-commercial purposes. So, we now have to use RSAREF.

However, since we're making this in Switzerland, and RSAREF originated
in the US, we (or somebody else) must have exported it from the US.

We could put a non-RSAREF algorithm on it, but then I do not have
RSA's permission to use it in the US.

This is entirely disregarding the expense of setting up a Walnut Creek
CD-ROM plant in Switzerland, or flying Jordan out of the country every
time he wants to build a new release.

The whole RSA scheme is bogus, because anyone in the world can get an
implementation of RSA, so its widely accesible, so why all this
RSAREF/non-RSAREF mumbo-jumbo?

The whole RSA scheme is not entirely bogus, at least not from a
commercial point of view. The RSAREF/non-RSAREF scheme is the
implementation of RSA's goals within our current legal framework.

Anybody who is inside the US and using RSA for commercial purposes
must pay RSA Labs. That is the purpose of RSA's patent. Encouraging
RD using RSA is the purpose of RSAREF.

Then, people outside of the US want a way to use RSA. Because of
ITAR, they can't get at RSAREF. So, that is the purpose of
non-RSAREF.

No doubt RSA Labs would love to be able to patent their algorithm
outside of the US and export their software, but ITAR forbds it.

Perhaps we should send e-mail to RSA to clarify this, and in light
of this, ask for permission to distribute RSA with the base OS. Gee,
we can get RSA anyway, so what's the point on making harder?

RSA is not likely to be helpful. They cannot allow non-US users to
use RSAREF, so the best they could do would be to allow a non-RSAREF
implementation to be used in the US. That may open them up to certain
legal problems, and doesn't gain them anything, so they are very
likely to say "go away".

Does anyone have ANY document saying that if you are in the US you are
obligued to use RSAREF?

Patent #4,405,829, issued 20Sep1983, availible online from the horse's
mouth at
http://164.195.100.11/netacgi/nph-Parser?Sect1=PTO1Sect2=HITOFFd=PALLp=1u=/netahtml/srchnum.htmr=1f=Gl=50s1='4,405,829'.WKU.OS=PN/4,405,829RS=PN/4,405,829

This means that if I'm in the US, I must have permission from RSA Labs
to use the RSA algorithm. Now, there are two main ways to get
permission. Either set up an agreement with RSA (and probably give
them money as part of the agreement), or use RSAREF.

Cheers,
joelh

--
Joel Ray Holveck - [EMAIL PROTECTED]
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped

--BAC18391.951126129/detlev.piqnet.org--

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

Re: Rc2 install

2000-02-22 Thread Joel Ray Holveck


 I've come to the conclusion that the -current stuff really doesn't install
 on an 8 Meg machine anymore. I have an old 486/66 machine I'm using
 to play with the current-RC's, and it consistantly dies loading the 'bin'
 stuff. 

Perhaps I'll make a MINIGENERIC kernel without some extraneous items
like NFS, etc.

I can attest that 3.3 can be made to install with 8MB, albeit with
some work.  I've got a machine with only 8MB that can't be upgraded or
replaced.  It took some work to get it 3.3 to install (I think I ended
up using a different installation method than I originally planned,
but I forgot to document it).  Anyway, I'll probably bring it to 4.0
after its release, and I'll try to document whatever I do to make it
happen.

Cheers,
joelh

-- 
Joel Ray Holveck - [EMAIL PROTECTED]
   Fourth law of programming:
   Anything that can go wrong wi
sendmail: segmentation violation - core dumped

--BAE18391.951126130/detlev.piqnet.org--




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

Re: Weird AMD panics caused by VMware?!

2000-02-22 Thread Nick Sayer



To followup to myself, I think I have this pinned down...

In line 403 of /sys/kern/vfs_cache.c, ncpp is somehow becoming 0. I believe
that
the trap is in ncp = LIST_FIRST(ncpp); -- LIST_FIRST(x) expands to
((x)-lh_first).
That ends up being a dereference of NULL, which causes the trap and panic.

As to how ncpp ends up being null, that's a good question, given it's the
variable in the
for loop at line 402. cache_zap() can't really have a side effect, since ncpp
is a stack
variable.

I am going to try rewriting the outer for() loop as

for(i=nchash ; i=0 ; i--) and the initialization of the inner loop as
ncp = LIST_FIRST((nchashtbl[i])) just in case cache_zap() causes the
value of nchashtbl to change (just how the hell THAT would happen is
way beyond me).

Nick Sayer wrote:

 (crossposting to -current in case it's not VMware related)

 I have a serial console running on the machine, so now I can tell the
 difference between
 a panic and a hang. :-)

 With that said, I now have a complete dump from one of these trap panics.
 Here is a
 stack trace:

 #0  0xc0152d28 in boot ()
 #1  0xc01530ac in poweroff_wait ()
 #2  0xc02571f9 in trap_fatal ()
 #3  0xc0256ed7 in trap_pfault ()
 #4  0xc0256a9a in trap ()
 #5  0xc0177da0 in cache_purgevfs ()
 #6  0xc017e6f1 in dounmount ()
 #7  0xc017e681 in unmount ()
 #8  0xc0257437 in syscall ()
 #9  0xc024b946 in Xint0x80_syscall ()
 #10 0x8057585 in ?? ()
 [etc]

 The machine is running amd, and my home directory is amd mounted. That is
 the only
 conceivable reason I can think why an 'unmount' would be in progress.

 Sure enough, ps aux on the core shows:

 USER PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED  TIME COMMAND
 root 841 97.7  0.0  11000  ??  R31Dec69   0:00.00  (amd)
 nsayer   699  8.5  0.0 594800 #C1  R31Dec69   4:46.96  (vmware)
 root   2  0.0  0.0 00  ??  RL   31Dec69   0:03.56
 (pagedaemon)
 root   3  0.0  0.0 00  ??  DL   31Dec69   0:00.42  (vmdaemon)
 root   4  0.0  0.0 00  ??  RL   31Dec69   0:00.00  (bufdaemon)

 root   5  0.0  0.0 00  ??  RL   31Dec69   0:02.17  (syncer)
 [...]

 Does anyone recognize this? What other information can I get that would be
 of use?

 "Vladimir N. Silyaev" wrote:

   My machine here at the office gets these a _lot_ whenever I'm running
   vmware:
  [skipped]
 
  This machine also seems to hang a lot, but it could be that the hangs
  are just these happening behind X so I can't see them.
  As you wrote below, you are have another box. So just try to use
  serial console (that will be provide a possibility to always
  see a panic message), also will be a right thing to compile kernel
  with DDB, that will provide some more information.
 
   They always happen with amd as the current process. They frequently
   happen when
  vmware is running. They never happen at other times.
  The FreeBSD vmmon has a 'historical' bug - it's clear 'GS' register.
  But I was never encounter problem with them. And more I was
  so impressed by the fact that I was never encountered any vmware(vmmon)
  related problem.
 
  --
  Vladimir Silyaev
 
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with "unsubscribe freebsd-emulation" in the body of the message

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-emulation" 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 (ffs) #2


-On [2222 21:55], Thomas David Rivers ([EMAIL PROTECTED]) wrote:
 
 And here we are again.
 
 This time on another disk:
 
 dev = #amrd/0x20004, block = 2048, fs = /news/spool
 panic: ffs_blkfree: freeing free block
 Debugger("panic")
 Stopped at  Debugger+0x35:  movb$0,in_Debugger.372
 db trace
 Debugger(c01e7ee3) at Debugger+0x35
 panic(c01f27e0,c01f27c0,c1ccc894,800,c1d0d0d4) at panic+0x70
 ffs_blkfree(c1db6d00,800,2000,0,d98cfe44) at ffs_blkfree+0x1dd

 Aha!  The Dave Rivers' memorial panic rears its ugly head!

 This is exactly the panic's I reported years ago; but we've never
 been able to track down... [Even the same block number I believe]

Well, at this rate I can drop debugs on the lists at a rate of one per
day.

 You may want to scan the archives to read more about my investigations;

If they were up.  Thank god I have some personal archives...  Hope I'll
get some info from them.

 which never went anywhere... (sigh)  I describe a way to reproduce
 it on some versions of FreeBSD, you might want to see if you can
 get a reliable reproduction, etc...

Hah, reliable reproduction, try to let the box stay up for a day or two,
bang.

So far in this existance of the box, I have had 4 ffs panics and 1
tcp...  If this were a debug box I'd say ok, well cool...  But this is
in fact a machine so close to the RC of 4.0 that I am not sure I want to
run production servers on it.

Add to that mix that I am a b-rated coder, just learning about gdb, and
on filesystem level and even dumber than (insert locally dumb idiot
here).

Then the logical step might be to say, well, then the hardware must be
faulty...  No way Jose...  I have tested this box in every way possible,
even detected incorrect CAS/RAS latency settings on the box in the BIOS
for the memory.

Anyways:

[root@tyr] (4) # gdb -k /kernel.debug vmcore.1 
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2625536
initial pcb at 21c9e0
panicstr: from debugger
panic messages:
---
panic: ffs_blkfree: freeing free block
panic: from debugger
Uptime: 39m4s
amrd0: still open, can't shutdown

dumping to dev #da/0x20001, offset 524312
dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 
491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 
470 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 
449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 
428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 
407 406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 
386 385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 
365 364 363 362 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 
344 343 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 
323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 
302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 282 
281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 !
 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245 
244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 
223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 
202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 
181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 
160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 
139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 
118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 
96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 
67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 
38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 
9 8 7 6 5 4 3 2 1 0 
---
(kgdb) bt
#0  boot (howto=260) at ../../kern/kern_shutdown.c:304
#1  0xc0143d61 in panic (fmt=0xc01e27f4 "from debugger")
at ../../kern/kern_shutdown.c:554
#2  0xc01244e1 in db_panic (addr=-1071886047, have_addr=0, count=-1, 
modif=0xd8b7fb88 "") at ../../ddb/db_command.c:433
#3  0xc0124481 in db_command (last_cmdp=0xc02042fc, cmd_table=0xc020415c, 
aux_cmd_tablep=0xc021905c) at ../../ddb/db_command.c:333
#4  0xc0124546 in db_command_loop () at ../../ddb/db_command.c:455
#5  0

Re: Promise Ultra66 + Seagate ATA/66 = Ultra ATA/33 :(


At Tue, 22 Feb 2000 21:29:30 +0100 (CET),
Soren Schmidt [EMAIL PROTECTED] wrote:
  ad4: piomode=4 dmamode=2 udmamode=2 cblid=1
^^
 
 The disk reports it can do at max UDMA2 mode (ATA33), so thats why
 the ata driver dont put it at UDMA4 (ATA66)...

  Ah!  I tried resetting the /66 activation flag by Seagate's utility,
and now it's successfully proved at /66 mode! :)

  I still wonder why it was ok on WinNT 4.0, but anyway I'm now happy
on FreeBSD with your ata driver.  Thanks!

-- 
   /
  /__  __
 / )  )  ) )  /
Akinori -Aki- MUSHA aka / (_ /  ( (__(  [EMAIL PROTECTED]

"If you choose not to decide you still have made a choice."


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

Re: status of 'device awe' ?



On 22-Feb-00 Jeroen Ruigrok van der Werven wrote:
 Should be used instead.
 I am so in favor of just declaring voxware dead...  But the armchair
 generals wouldn't like that.

The awe device controls the AWE's wavetable.. newpcm doesn't talk to this
(yet - no idea if there are any plans)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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

Re: status of 'device awe' ?


-On [2222 23:25], Daniel O'Connor ([EMAIL PROTECTED]) wrote:

On 22-Feb-00 Jeroen Ruigrok van der Werven wrote:
 Should be used instead.
 I am so in favor of just declaring voxware dead...  But the armchair
 generals wouldn't like that.

The awe device controls the AWE's wavetable.. newpcm doesn't talk to this
(yet - no idea if there are any plans)

newmidi is underway...

That's why I wanted to kill voxware in 4.0, would allow pcm to be used
from default...  Now we're stuck to the voxware crap for another release
cycle until 5.0 hits the public.

-- 
Jeroen Ruigrok van der Werven  Network- and systemadministrator
[EMAIL PROTECTED]  bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70  http://www.bart.nl


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

Re: status of 'device awe' ?



On 22-Feb-00 Jeroen Ruigrok van der Werven wrote:
 That's why I wanted to kill voxware in 4.0, would allow pcm to be used
 from default...  Now we're stuck to the voxware crap for another release
 cycle until 5.0 hits the public.

shrugs You don't _have_ to use it :)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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

Re: Panic (ffs) #2


*sigh*

ignore the gdb output of this one...

it was the old one.  =(

/var/crash was too full.

-- 
Jeroen Ruigrok van der Werven  Network- and systemadministrator
[EMAIL PROTECTED]  bART Internet Services /
BSD: Technical excellence at its best  VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70  http://www.bart.nl


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

Re: kdelibs port broken?



On 22-Feb-00 Maxim Sobolev wrote:
  Now, I'd look this up in the mailing lists, but the search is still down
  I do remember something about C++ stuff needing to be recompiled (which
  is
  why I'm rebuilding kdelibs in the first place)..
  You have to rebuild qt2 first to be able to run moc.

Ahh yes, that fixed it.. I rebuild qt142.. 

KDE libs works fine now, thanks :)

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum


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

Re: kdelibs port broken?


On Tue, Feb 22, 2000 at 05:36:19PM +0200, Maxim Sobolev wrote:
 You have to rebuild qt2 first to be able to run moc.

ITYM Qt 1.45, not Qt2.

-- 
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: kdelibs port broken?


On Tue, Feb 22, 2000 at 07:40:55AM -0800, William Woods wrote:
 ON that subject, has anyone tried compiling the KDE port with the new QT145
 port?

In my original tests, Qt 1.45 works fine with the KDE ports. Do you have
any problems with it?

-- 
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: status of 'device awe' ?

2000-02-22 Thread Andy Sparrow


On Tue, Feb 22, 2000 at 03:46:04PM -0700, Kenneth D. Merry wrote:
 On Tue, Feb 22, 2000 at 23:33:26 +0100, Jeroen Ruigrok van der Werven wrote:
  -On [2222 23:25], Daniel O'Connor ([EMAIL PROTECTED]) wrote:
  
  On 22-Feb-00 Jeroen Ruigrok van der Werven wrote:
   Should be used instead.
   I am so in favor of just declaring voxware dead...  But the armchair
   generals wouldn't like that.
  
  The awe device controls the AWE's wavetable.. newpcm doesn't talk to this
  (yet - no idea if there are any plans)
  
  newmidi is underway...
  
  That's why I wanted to kill voxware in 4.0, would allow pcm to be used
  from default...  Now we're stuck to the voxware crap for another release
  cycle until 5.0 hits the public.
 
 Voxware may be "crap", but newpcm doesn't work right for my GUS PnP.  (And
 yep, I sent mail to the multimedia list, which got some response, and I
 sent mail to Cameron, which got no response.)
 
 Voxware used to work fine, way back when.  Luigi's pcm code worked fine as
 well with my GUS PnP.  Maybe it's time for me to switch back to voxware
 from newpcm.  I'm tired of getting static every once in a while when
 playing sound files.
 
 I don't see any reason to get rid of voxware before newpcm is fully
 functional.


Unfortunately for those of us who used to use 'pnp' commands in
userconfig to probe/init the AWE registers, the AWE wavetable is
already useless in -current.

AFAIK, the AWE cannot work without this, and the cards PnPinfo
seems to not include the other two registers - and if you don't
probe them, then the 'awe' driver check doesn't see the EMU8000...

Is there even a single person out there able to use the AWE device
under Voxware in -current?


My understanding is that this is no longer possible, following the
removal of the 'pnp' interface in userconfig..

So, people with the AWE32, AWE daughter card or the AWE64 might as
well have an original SoundBlaster 16, for all the good the EMU8000
wavetable/synth chip does them. 


If that is really so, then I would suggest that either:

a)  the 'awe' driver is now just so much cruft and should be removed.

or

b)  FreeBSD has lost significant functionality (namely, AWE wavetable
support) with the removal of the older 'pnp' interface, and this
should be put back.


I guess that your perspective on this really depends on whether
you actually have the hardware and want to use it...

For me, with an integrated Vibra 16 on the mobo, Voxware is now
unusable for sound as the SoundBlaster portion is not recognised.
(Again, only in -current, it all works perfectly in -stable).

I /have/ to use pcm in -current, simply to play CDs (which,
incidentally, works well for me)...

Of course, for the time being, I have the option of using this
hardware under -stable, but eventually the changes will filter
through to there as well.

Of more importance (to me, right now), is that -stable is not
getting the benefit of the other improvements that are going on in
-current. (e.g. Linux threads, SMP, NFS etc.)


Cheers,

AS


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

Re: Kernel

2000-02-22 Thread Bosko Milekic



Try looking at the sysctl(3) interface. Issue `sysctl -A' and note
  one of the exported variable names. Then, search the code to see how it's
  setup. This is most probably what you're looking for.

On Mon, 21 Feb 2000, [iso-8859-1] José Luís Faria wrote:

Hello 

I'm creating a litle update to a freebsd 3.4 kernel.
My program is for account some data: number of
packets by class, number of packets dropped by class, etc.
Now I need to pass this values to another program wich in X-Window
display this values on-line. After, I want to save this values
in a file.

I need some docs about how I can do this.
Which are the primitives in the kernel to do this.
I use the printf to put this data in /var/log/messages.
This inappropriate, I dont want this. This is only for testing now.

Can you help me ?

Thank you very much.


P.S. I'm sorry my english.


-- 

  :) cumprimentos

  Jose Luis Faria
  Administrador de Sistemas
  Universidade do Minho - Departamento de Informática
  Campus de Gualtar
  4710-057 Braga
  Portugal
  tel.: +351 253604440 Fax:+351 253604471
  http://admin.di.uminho.pt/~jose



--
  Bosko Milekic * [EMAIL PROTECTED] * http://pages.infinit.net/bmilekic/
--




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

Re: kdelibs port broken?


Yea, after I compiled QT145, I couldent compile KDE. I am not sure of the exact
error, it was a few days ago and I went back to 142, but It wouldent comile.

On 22-Feb-00 Will Andrews wrote:
 On Tue, Feb 22, 2000 at 07:40:55AM -0800, William Woods wrote:
 ON that subject, has anyone tried compiling the KDE port with the new QT145
 port?
 
 In my original tests, Qt 1.45 works fine with the KDE ports. Do you have
 any problems with it?
 
 -- 
 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?


--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 22-Feb-00
Time: 16:27:23l
FreeBSD 3.4
--


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

Re: kdelibs port broken?

2000-02-22 Thread Chris D. Faulhaber


On Tue, 22 Feb 2000, William Woods wrote:

 On 22-Feb-00 Will Andrews wrote:
  On Tue, Feb 22, 2000 at 07:40:55AM -0800, William Woods wrote:
  ON that subject, has anyone tried compiling the KDE port with the new QT145
  port?
  
  In my original tests, Qt 1.45 works fine with the KDE ports. Do you have
  any problems with it?
 Yea, after I compiled QT145, I couldent compile KDE. I am not sure of the exact
 error, it was a few days ago and I went back to 142, but It wouldent comile.
 

Did you change the depends under USE_QT in bsd.port.mk to use qt.3
(provided by qt145) instead of qt.2 (provided by qt142)?  I'm using
qt145/kde under -CURRENT and -STABLE (under OLDGCC *and* NEWGCC) without
problems.

-
Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]

FreeBSD: The Power To Serve   -   http://www.FreeBSD.org



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

XFree 3.3.6 authentication failed?

2000-02-22 Thread lioux


Dear guys,

I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
KDE 1.1.2.  All from monday's ports tree.
Well, I think I can't say I am running this system, for I am getting
the following message whenever I try startx:

Authentication failed - cannot start X server.
Perhaps you do not have console ownership?
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
_X11TransSocketUNIXConnect: Can't connect: errno = 2
giving up.
xinit:  No such file or directory (errno 2):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

Damn, I know this must be my mistake. However, I can't seem to get
X up. However, /stand/sysinstall - Configure - XFree86 - XF86Setup
works smooth. Before you mention it: yeah, yeah, I tried startx as root
against my best judgement; and no, it did not work. :)
UCONSOLE is enabled.
My .xinitrc follows at the end of this file.
What am I missing? A new authentication system? My guess. I went
through the FAQ and most of the simple docs; I must be overlooking something.
Any and all help appreciated. Please CC: to [EMAIL PROTECTED], for I
am subscribed to neither freebsd-questions nor freebsd-current.
I apologize in advance for the CC: accross mailing lists.

Regards,
Mario Ferreira

ps: Please, don't flame me. /dev/null appreciates it. Thanks again.

--

#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi

# start some nice programs

kde


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

Re: XFree 3.3.6 authentication failed?

2000-02-22 Thread Crist J. Clark


On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote:
 Dear guys,
 
   I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
 KDE 1.1.2.  All from monday's ports tree.
   Well, I think I can't say I am running this system, for I am getting
 the following message whenever I try startx:
 
 Authentication failed - cannot start X server.
 Perhaps you do not have console ownership?
[snip]

You built X with PAM enabled.
-- 
Crist J. Clark   [EMAIL PROTECTED]


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

Upgrade from 3.4 to 4.0...


Hey,

I have been following the disscussions here for a while, just trying to get a
feel of what the transition from 3.4-stable 4.0-release will be like. I am
running -current on my alpha, but that was a fresh install. I am debating
trying -current on my laptop, but before we go there, I would like to inquire
as to what shape the transition is in. Are there steps posted somewhere that
work?

Also, what condition (I know, I am asking you to read the future) do you expect
the transition to be like at the end of the month when 4.0 -release comes out.

Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now, where
would I find the nessary instructions?

--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 22-Feb-00
Time: 20:40:26l
FreeBSD 3.4
--


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

Re: XFree 3.3.6 authentication failed?

2000-02-22 Thread Will Saxon


Actually I think this is a pam.conf issue. You probably built 3.3.6 with
PAM support? This happened to me as soon as 3.3.6 came out.

try copying pam.conf from whereveryoubuildworld/etc to /etc and see if
that fixes it.

I think mergemaster would take care of this too, I dunno last time I used
it it did more harm than good.

-Will

On Tue, 22 Feb 2000, Will Andrews wrote:

 On Wed, Feb 23, 2000 at 02:10:00AM -0300, [EMAIL PROTECTED] wrote:
  Dear guys,
  
  I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
  KDE 1.1.2.  All from monday's ports tree.
  Well, I think I can't say I am running this system, for I am getting
  the following message whenever I try startx:
  
  Authentication failed - cannot start X server.
  Perhaps you do not have console ownership?
  _X11TransSocketUNIXConnect: Can't connect: errno = 2
  _X11TransSocketUNIXConnect: Can't connect: errno = 2
  _X11TransSocketUNIXConnect: Can't connect: errno = 2
  _X11TransSocketUNIXConnect: Can't connect: errno = 2
  _X11TransSocketUNIXConnect: Can't connect: errno = 2
  _X11TransSocketUNIXConnect: Can't connect: errno = 2
  giving up.
  xinit:  No such file or directory (errno 2):  unable to connect to X server
  xinit:  No such process (errno 3):  Server error.
  
  Damn, I know this must be my mistake. However, I can't seem to get
  X up. However, /stand/sysinstall - Configure - XFree86 - XF86Setup
  works smooth. Before you mention it: yeah, yeah, I tried startx as root
  against my best judgement; and no, it did not work. :)
  UCONSOLE is enabled.
  My .xinitrc follows at the end of this file.
  What am I missing? A new authentication system? My guess. I went
  through the FAQ and most of the simple docs; I must be overlooking something.
  Any and all help appreciated. Please CC: to [EMAIL PROTECTED], for I
  am subscribed to neither freebsd-questions nor freebsd-current.
  I apologize in advance for the CC: accross mailing lists.
  
  Regards,
  Mario Ferreira
  
  ps: Please, don't flame me. /dev/null appreciates it. Thanks again.
 
 1) Do you have "XSERVER" option in kernel? I'm not sure if it's
 required, but it might be.
 
 2) You should start KDE with "startkde" not "kde".
 
 -- 
 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
 



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

Re: Upgrade from 3.4 to 4.0...

2000-02-22 Thread Alfred Perlstein


* William Woods [EMAIL PROTECTED] [000222 21:19] wrote:
 Hey,
 
 I have been following the disscussions here for a while, just trying to get a
 feel of what the transition from 3.4-stable 4.0-release will be like. I am
 running -current on my alpha, but that was a fresh install. I am debating
 trying -current on my laptop, but before we go there, I would like to inquire
 as to what shape the transition is in. Are there steps posted somewhere that
 work?
 
 Also, what condition (I know, I am asking you to read the future) do you expect
 the transition to be like at the end of the month when 4.0 -release comes out.
 
 Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now, where
 would I find the nessary instructions?

Please see src/UPDATING

thanks,
-Alfred


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

Re: Upgrade from 3.4 to 4.0...


I did read that document, and honestly, it dident make a lot of sence and it
seemed to have some conflicting instructions.which is why I am asking here.

On 23-Feb-00 Alfred Perlstein wrote:
 * William Woods [EMAIL PROTECTED] [000222 21:19] wrote:
 Hey,
 
 I have been following the disscussions here for a while, just trying to get
 a
 feel of what the transition from 3.4-stable 4.0-release will be like. I am
 running -current on my alpha, but that was a fresh install. I am debating
 trying -current on my laptop, but before we go there, I would like to
 inquire
 as to what shape the transition is in. Are there steps posted somewhere that
 work?
 
 Also, what condition (I know, I am asking you to read the future) do you
 expect
 the transition to be like at the end of the month when 4.0 -release comes
 out.
 
 Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now,
 where
 would I find the nessary instructions?
 
 Please see src/UPDATING
 
 thanks,
 -Alfred


--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 22-Feb-00
Time: 20:53:10l
FreeBSD 3.4
--


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

Re: Upgrade from 3.4 to 4.0...


On Tue, Feb 22, 2000 at 08:45:28PM -0800, William Woods wrote:
 I have been following the disscussions here for a while, just trying to get a
 feel of what the transition from 3.4-stable 4.0-release will be like. I am
 running -current on my alpha, but that was a fresh install. I am debating
 trying -current on my laptop, but before we go there, I would like to inquire
 as to what shape the transition is in. Are there steps posted somewhere that
 work?

See src/UPDATING.

I made the transition on my laptop from 3.3-RELEASE to 4.0-CURRENT about
six months ago, so my experience wouldn't help you much, unfortunately.

However, I would just like to say that I'm very happy with my
4.0-CURRENT running with a 3Com 3CCFE574BT PC-Card. :-)

 Also, what condition (I know, I am asking you to read the future) do you expect
 the transition to be like at the end of the month when 4.0 -release comes out.

Should be fairly easy, if you do it the cvsup/make world way.. there's a
lot of different thorns here and there so I'm not real sure what it
would be like once 4.0-RELEASE goes out.

-- 
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: Upgrade from 3.4 to 4.0...



On 23-Feb-00 Will Andrews wrote:
 
 See src/UPDATING.

I read that...I must say it is a bit confusing and in some places contradictory
 
 I made the transition on my laptop from 3.3-RELEASE to 4.0-CURRENT about
 six months ago, so my experience wouldn't help you much, unfortunately.
 
 However, I would just like to say that I'm very happy with my
 4.0-CURRENT running with a 3Com 3CCFE574BT PC-Card. :-)

I have that same card

--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 22-Feb-00
Time: 20:55:56l
FreeBSD 3.4
--


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

Re: Upgrade from 3.4 to 4.0...


On Tue, Feb 22, 2000 at 08:54:14PM -0800, William Woods wrote:
 I did read that document, and honestly, it dident make a lot of sence and it
 seemed to have some conflicting instructions.which is why I am asking here.

Specifics, specifics... and are you sure you're looking at an
_UP_TO_DATE_ copy of src/UPDATING ?

-- 
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: Upgrade from 3.4 to 4.0...


cvsupped a few hours ago..

On 23-Feb-00 Will Andrews wrote:
 On Tue, Feb 22, 2000 at 08:54:14PM -0800, William Woods wrote:
 I did read that document, and honestly, it dident make a lot of sence and it
 seemed to have some conflicting instructions.which is why I am asking
 here.
 
 Specifics, specifics... and are you sure you're looking at an
 _UP_TO_DATE_ copy of src/UPDATING ?
 
 -- 
 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?


--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 22-Feb-00
Time: 21:02:44l
FreeBSD 3.4
--


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

Re: Upgrade from 3.4 to 4.0...

2000-02-22 Thread Alfred Perlstein


* William Woods [EMAIL PROTECTED] [000222 21:27] wrote:
 I did read that document, and honestly, it dident make a lot of sence and it
 seemed to have some conflicting instructions.which is why I am asking here.

It looks pretty concise to me, perhaps you can explain the confusion
so that we may fix it so as to help other users?

-Alfred

 
 On 23-Feb-00 Alfred Perlstein wrote:
  * William Woods [EMAIL PROTECTED] [000222 21:19] wrote:
  Hey,
  
  I have been following the disscussions here for a while, just trying to get
  a
  feel of what the transition from 3.4-stable 4.0-release will be like. I am
  running -current on my alpha, but that was a fresh install. I am debating
  trying -current on my laptop, but before we go there, I would like to
  inquire
  as to what shape the transition is in. Are there steps posted somewhere that
  work?
  
  Also, what condition (I know, I am asking you to read the future) do you
  expect
  the transition to be like at the end of the month when 4.0 -release comes
  out.
  
  Lastly, if I were to be so brave as to go from 3.4 to 4.0 -current now,
  where
  would I find the nessary instructions?
  
  Please see src/UPDATING


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

Re: Upgrade from 3.4 to 4.0...


On Tue, Feb 22, 2000 at 08:57:35PM -0800, William Woods wrote:
  4.0-CURRENT running with a 3Com 3CCFE574BT PC-Card. :-)
 
 I have that same card

Works great on 4.0-CURRENT, which I'm sure you'll be glad to know. If
you have any trouble getting it to work, just drop me a line and I'll
help you debug it. :-)

I've been able to get 1.2MB/sec on half-duplex 100BaseTX.

-- 
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: Upgrade from 3.4 to 4.0...

2000-02-22 Thread Warner Losh


In message [EMAIL PROTECTED] William Woods writes:
: I read that...I must say it is a bit confusing and in some places contradictory

I'm not surprising that it is confusing.  It is hard to hit a moving
target like current.  And things have often are contradictory...

Warner


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

Re: Upgrade from 3.4 to 4.0...


On Tue, Feb 22, 2000 at 09:03:04PM -0800, William Woods wrote:
 cvsupped a few hours ago..

  Specifics, specifics... and are you sure you're looking at an

Specifics please.

-- 
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: XFree 3.3.6 authentication failed?

2000-02-22 Thread Max Khon


hi, there!

On Wed, 23 Feb 2000 [EMAIL PROTECTED] wrote:

   I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and
 KDE 1.1.2.  All from monday's ports tree.
   Well, I think I can't say I am running this system, for I am getting
 the following message whenever I try startx:
 
 Authentication failed - cannot start X server.
 Perhaps you do not have console ownership?
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 _X11TransSocketUNIXConnect: Can't connect: errno = 2
 giving up.
 xinit:  No such file or directory (errno 2):  unable to connect to X server
 xinit:  No such process (errno 3):  Server error.

seems that you have built XFree with PAM support.
Just rebuild without PAM -- it's broken.

/fjoe



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

Re: Upgrade from 3.4 to 4.0...

2000-02-22 Thread R Joseph Wright


On Tue, 22 Feb 2000, Alfred Perlstein wrote:

 * William Woods [EMAIL PROTECTED] [000222 21:27] wrote:
  I did read that document, and honestly, it dident make a lot of sence and it
  seemed to have some conflicting instructions.which is why I am asking here.
 
 It looks pretty concise to me, perhaps you can explain the confusion
 so that we may fix it so as to help other users?

It seems like it contains good information for those who have
been on the track for awhile, while being a bit cryptic for
people new to the process.  Since this is a development version, I
suppose that's to be expected.
I followed the instructions that someone else posted on -questions:

make buildworld
make buildkernel make installkernel
Then reboot in single user mode
make -DNOINFO installworld
make buildkernel make installkernel (again)
make installworld

This worked for me perfectly.



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

Re: Upgrade from 3.4 to 4.0...



On 23-Feb-00 R Joseph Wright wrote:
 
 make buildworld
 make buildkernel make installkernel
 Then reboot in single user mode
 make -DNOINFO installworld
 make buildkernel make installkernel (again)
 make installworld
 
 This worked for me perfectly.

Hmmm.the only question I have regarding this is does it handle the new
devices corectly?

--
E-Mail: William Woods [EMAIL PROTECTED]
Date: 22-Feb-00
Time: 22:18:06l
FreeBSD 3.4
--


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

Problem with IBM Netfinity 5000 Server

2000-02-22 Thread User URANIA




I've a Netfinity 5000 Server, internal 5 PCI slot onborad.
If i put one Intel 82558 NIC at 5th PCI Slot, everythings goes
fine. Every times i put the same Intel NIC to any other PCI
slots ( 1th ~ 4th ), after system login prompt , i also login 
as root, then system direct reboot  #


Here is boot -v message as I put The NIC at 4th PCI Slot:
Feb 23 14:02:59 www /kernel: Copyright (c) 1992-2000 The FreeBSD Project.
Feb 23 14:02:59 www /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993
Feb 23 14:02:59 www /kernel: The Regents of the University of California. All rights 
reserved.
Feb 23 14:02:59 www /kernel: FreeBSD 4.0-CURRENT #0: Wed Feb 23 13:56:44 CST 2000
Feb 23 14:02:59 www /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/www
Feb 23 14:02:59 www /kernel: Calibrating clock(s) ... TSC clock: 498595828 Hz, i8254 
clock: 1193010 Hz
Feb 23 14:02:59 www /kernel: CLK_USE_I8254_CALIBRATION not specified - using default 
frequency
Feb 23 14:02:59 www /kernel: Timecounter "i8254"  frequency 1193182 Hz
Feb 23 14:02:59 www /kernel: CLK_USE_TSC_CALIBRATION not specified - using old 
calibration method
Feb 23 14:02:59 www /kernel: Timecounter "TSC"  frequency 498670821 Hz
Feb 23 14:02:59 www /kernel: CPU: Pentium III/Pentium III Xeon (498.67-MHz 686-class 
CPU)
Feb 23 14:02:59 www /kernel: Origin = "GenuineIntel"  Id = 0x673  Stepping = 3
Feb 23 14:02:59 www /kernel: 
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM
Feb 23 14:02:59 www /kernel: real memory  = 536854528 (524272K bytes)
Feb 23 14:02:59 www /kernel: Physical memory chunk(s):
Feb 23 14:02:59 www /kernel: 0x1000 - 0x0009dfff, 643072 bytes (157 pages)
Feb 23 14:02:59 www /kernel: 0x0031c000 - 0x1fff3fff, 533561344 bytes (130264 pages)
Feb 23 14:02:59 www /kernel: avail memory = 517894144 (505756K bytes)
Feb 23 14:02:59 www /kernel: bios32: Found BIOS32 Service Directory header at 
0xc00fd5d0
Feb 23 14:02:59 www /kernel: bios32: Entry = 0xfd5e1 (c00fd5e1)  Rev = 0  Len = 1
Feb 23 14:02:59 www /kernel: pcibios: PCI BIOS entry at 0xd61c
Feb 23 14:02:59 www /kernel: pnpbios: Found PnP BIOS data at 0xc00fde90
Feb 23 14:02:59 www /kernel: pnpbios: Entry = f:497d  Rev = 1.0
Feb 23 14:02:59 www /kernel: Other BIOS signatures found:
Feb 23 14:02:59 www /kernel: ACPI: 000fdec0
Feb 23 14:02:59 www /kernel: Preloaded elf kernel "kernel" at 0xc0303000.
Feb 23 14:02:59 www /kernel: Pentium Pro MTRR support enabled
Feb 23 14:02:59 www /kernel: Math emulator present
Feb 23 14:02:59 www /kernel: pci_open(1):   mode 1 addr port (0x0cf8) is 0x0070
Feb 23 14:02:59 www /kernel: pci_open(1a):  mode1res=0x8000 (0x8000)
Feb 23 14:02:59 www /kernel: pci_cfgcheck:  device 0 [class=06] [hdr=80] is 
there (id=00071166)
Feb 23 14:02:59 www /kernel: npx0: math processor on motherboard
Feb 23 14:02:59 www /kernel: npx0: INT 16 interface
Feb 23 14:02:59 www /kernel: pci_open(1):   mode 1 addr port (0x0cf8) is 0x
Feb 23 14:02:59 www /kernel: pci_open(1a):  mode1res=0x8000 (0x8000)
Feb 23 14:02:59 www /kernel: pci_cfgcheck:  device 0 [class=06] [hdr=80] is 
there (id=00071166)
Feb 23 14:02:59 www /kernel: pcib0: Host to PCI bridge on motherboard
Feb 23 14:02:59 www /kernel: found-vendor=0x1166, dev=0x0007, revid=0x04
Feb 23 14:02:59 www /kernel: class=06-00-00, hdrtype=0x00, mfdev=1
Feb 23 14:02:59 www /kernel: subordinatebus=0   secondarybus=0
Feb 23 14:02:59 www /kernel: map[10]: type 1, range 32, base , size  0
Feb 23 14:02:59 www /kernel: found-vendor=0x1166, dev=0x0005, revid=0x02
Feb 23 14:02:59 www /kernel: class=06-00-00, hdrtype=0x00, mfdev=1
Feb 23 14:02:59 www /kernel: subordinatebus=0   secondarybus=0
Feb 23 14:02:59 www /kernel: found-vendor=0x9004, dev=0x7895, revid=0x04
Feb 23 14:02:59 www /kernel: class=01-00-00, hdrtype=0x00, mfdev=1
Feb 23 14:02:59 www /kernel: subordinatebus=0   secondarybus=0
Feb 23 14:02:59 www /kernel: intpin=a, irq=11
Feb 23 14:02:59 www /kernel: map[10]: type 1, range 32, base 2000, size  8
Feb 23 14:02:59 www /kernel: map[14]: type 1, range 32, base febff000, size 12
Feb 23 14:02:59 www /kernel: found-vendor=0x9004, dev=0x7895, revid=0x04
Feb 23 14:02:59 www /kernel: class=01-00-00, hdrtype=0x00, mfdev=1
Feb 23 14:02:59 www /kernel: subordinatebus=0   secondarybus=0
Feb 23 14:03:00 www /kernel: intpin=b, irq=15
Feb 23 14:03:00 www /kernel: map[10]: type 1, range 32, base 2200, size  8
Feb 23 14:03:00 www /kernel: map[14]: type 1, range 32, base febfe000, size 12
Feb 23 14:03:00 www /kernel: found-vendor=0x1022, dev=0x2000, revid=0x36
Feb 23 14:03:00 www /kernel: class=02-00-00, hdrtype=0x00, mfdev=0
Feb 23 14:03:00 www /kernel: subordinatebus=0   secondarybus=0
Feb 23 14:03:00 www /kernel: intpin=a, irq=10
Feb 23 14:03:00 www /kernel: map[10]: type 1, range 32, base 2180, size  5
Feb 23 14:03:00 www /kernel: map[14]: type 1, range 32, base febfdc00, size  5
Feb 23

Re: Upgrade from 3.4 to 4.0...

2000-02-22 Thread R Joseph Wright


On Tue, 22 Feb 2000, William Woods wrote:

 
 On 23-Feb-00 R Joseph Wright wrote:
  
  make buildworld
  make buildkernel make installkernel
  Then reboot in single user mode
  make -DNOINFO installworld
  make buildkernel make installkernel (again)
  make installworld
  
  This worked for me perfectly.
 
 Hmmm.the only question I have regarding this is does it handle the new
 devices corectly?

It did, although I did eventually remake them.

I did:
mv /dev /dev.old
mkdir /dev
cp /usr/src/etc/MAKE* /dev
sh MAKEDEV all

I also had to make the partition entries for my IDE drive:

sh MAKEDEV ad0s4a

Then I edited /etc/fstab to reflect the new devices --Very Important!

Of course I also ran mergemaster to update the /etc directory.
That's it.



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

Re: Upgrade from 3.4 to 4.0...