Loss of Functionality with newpnp

1999-09-26 Thread Donald J . Maddox

The new PnP code just plain does not work for my PnP AWE64.

If I configure like this:

controller  pnp0
controller  snd0
device  sb0
device  sbxvi0
device  sbmidi0
device  awe0
device  opl0
device  joy0

Which is the way it *should* work, in my understanding, it simply
fails like this:

unknown0: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown1: Game at port 0x200-0x207 on isa0
unknown2: WaveTable at port 0x620-0x623 on isa0

If I configure it the old way:

controller  pnp0
controller  snd0
device  sb0 at isa? port 0x220 irq 5 drq 1
device  sbxvi0  at isa? drq 5
device  sbmidi0 at isa? port 0x330
device  awe0at isa? port 0x620
device  opl0at isa? port 0x388
device  joy0at isa? port 0x200

I get the same failures as above from the PnP code, but the card still
works (mostly) because it has already been configured by the PnP BIOS.
The SB16-compatible portion of the card works OK even if I take PnP
support out of the kernel completely, and always has.

Unfortunately, the AWE device *needs* a little more initialization than
it gets from the BIOS to probe correctly.  With the old PnP code, I used
a userconfig-script, like this:

pnp 1 0 os enable port0 0x220 irq0 5 drq0 1 drq1 5 port1 0x330 port2 0x388
pnp 1 1 os enable port0 0x200
pnp 1 2 os enable port0 0x620 port1 0xa20 port2 0xe20

The first 2 lines have always been unnecessary, but harmless; however, the
3rd line is _absolutely necessary_ to get the AWE to probe.

As far as I can tell, there is no way to duplicate this functionality
with the new PnP code.

Is the new PnP code really so smart that it has no use for user intervention
ever?  My experience indicates that it is not.

It would be very nice if the architects of the new PnP code would add back
this lost functionality.


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



Re: Boot problems with new -current

1999-09-26 Thread Soren Schmidt

It seems Cejka Rudolf wrote:
 I think internal bad block remapping is long time here. But
 in the middle of 1996 I have bought a new Western Digital disk 
 with some bad sectors and it runs without any problems till today
 (and without any new bad sectors - I have tried new disk format
 some time ago). Does this mean that I should in such cases make
 a complaint in a store if I want to use new ATA driver?

Hmm, a modern ATA disk should have NO defects, if it has it is
to be replaced immediately under warranty, if they refuse,
dont buy anything from that vendor again :)

-Søren


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



Re: make world, attempt 5

1999-09-26 Thread John Hay

Are you sure everything is ok on your machine? I have done 4-5 make worlds
in the last 48 hours and except for the perl breakage, haven't had any
other problems. Even make release worked here.

John
-- 
John Hay -- [EMAIL PROTECTED]

 I've been trying for the last 24 hours solid to make a new world.  The
 latest problem is:
 
 === libwrap
 cc -nostdinc -O -pipe -DFACILITY=LOG_AUTH -DHOSTS_ACCESS -DNETGROUP 
-DDAEMON_UMASK=022  -DREAL_DAEMON_DIR=\"/usr/libexec\" -DPROCESS_OPTIONS  
-DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" 
-DHOSTS_ALLOW=\"/etc/hosts.allow\"  -DSYS_ERRLIST_DEFINED -DALWAYS_HOSTNAME 
-I/usr/obj/src/PANIC/src/tmp/usr/include -c 
/src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c -o hosts_access.o
 /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245: syntax 
error before `'
 /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:84: warning: 
`host_match' declared `static' but never defined
 /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:85: warning: 
`string_match' declared `static' but never defined
 
 Could we have a break for those people who would like make world to
 complete?
 
 Greg
 -- 
 See complete headers for address, home page and phone numbers
 finger [EMAIL PROTECTED] for PGP public key


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



-current panic w/linux netscape

1999-09-26 Thread Mike Pritchard

I finally saw my first -current panic in more than 5 months (not a bad
track record).

I have a panic that I can duplicate with a 24 hour old "make world"
and a 4 hour old -current kernel.  If I run the linux netscape (installed
from ports less than a week ago), the kernel panics in copystr().
Minimal gdb output follows.  I'll have to generate a kernel with
debug info for more information.

The linux netscape worked fine with my old kernel from 9/16.
I'm willing to try and track this down, but I hope someone
will pop up and have an idea what is wrong.

-Mike

Script started on Sun Sep 26 05:47:00 1999
mpp 2# gdb -k /usr/src/sys/compile/MPP/kernel /var/crash/vmcore.0
GNU gdb 4.18
(no debugging symbols found)...
IdlePTD 3264512
initial pcb at 29f1c0
panicstr: from debugger
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x7
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc0222d50
stack pointer   = 0x10:0xcb0bdc80
frame pointer   = 0x10:0xcb0bdce8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 385 (communicator-4.6)
interrupt mask  = none
panic: from debugger
panic: from debugger

dumping to dev #wd/0x50001, offset 131072
dump 191 ... 1
---
#0  0xc013a644 in boot ()
(kgdb) bt
#0  0xc013a644 in boot ()
#1  0xc013a9e9 in panic ()
#2  0xc011f435 in db_panic ()
#3  0xc011f3d5 in db_command ()
#4  0xc011f49a in db_command_loop ()
#5  0xc012151f in db_trap ()
#6  0xc0215210 in kdb_trap ()
#7  0xc02240ac in trap_fatal ()
#8  0xc0223d85 in trap_pfault ()
#9  0xc02239c7 in trap ()
#10 0xc0222d50 in copystr ()
#11 0xc0dc7209 in ?? ()
#12 0xc0dc5fbd in ?? ()
#13 0xc0224316 in syscall ()
#14 0xc0215b06 in Xint0x80_syscall ()
#15 0x28abf564 in ?? ()
-- 
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Ollivier Robert

According to Donald J . Maddox:
 I get the same failures as above from the PnP code, but the card still
 works (mostly) because it has already been configured by the PnP BIOS.
 The SB16-compatible portion of the card works OK even if I take PnP
 support out of the kernel completely, and always has.

Can you try to new newpcm ?

controller pnp0
device pcm0

 The first 2 lines have always been unnecessary, but harmless; however, the
 3rd line is _absolutely necessary_ to get the AWE to probe.

The above works for my AWE64.

pcm0: SB16 PnP at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown0: Game at port 0x200-0x207 on isa0
unknown1: WaveTable at port 0x620-0x623 on isa0

FreeBSD Audio Driver (newpcm) Sep  9 1999 00:19:32
Installed devices:
pcm0: SoundBlaster 16 4.16 at io 0x220 irq 5 drq 1:5 (1/1 channels duplex)

-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep  9 00:20:51 CEST 1999



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



Re: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread Brian Somers

  Basically, I think not allowing ISP's to allow the Dialup lines to
  forward email as a good thing, but for them to limit was businesses do
  with their IP traffic is simply too big brother'ish, no matter what
  their contract states.
 
 If _we_ don't start to do something about it, big brother _is_ going
 to do something about it.  Trust me on this one, being a member of the
 USPA I know that we are far better off implementing our own (as ISP's)
 set of safe gaurds that help eliminate certain undesirable behavior.
[.]

I think it's up to the ISP what default policies they have, and I 
also think that this sort of policy is a good default... but only as 
long as the ISP allows exceptions.  As a paying subscriber with a 
clean record I *must* be allowed to ask for a hole through your 
firewall.

This protects both sides.

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

-- 
Brian [EMAIL PROTECTED][EMAIL PROTECTED]
  http://www.Awfulhak.org   [EMAIL PROTECTED]
Don't _EVER_ lose your sense of humour !  [EMAIL PROTECTED]




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



Re: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread sthaug

  If _we_ don't start to do something about it, big brother _is_ going
  to do something about it.  Trust me on this one, being a member of the
  USPA I know that we are far better off implementing our own (as ISP's)
  set of safe gaurds that help eliminate certain undesirable behavior.
 [.]
 
 I think it's up to the ISP what default policies they have, and I 
 also think that this sort of policy is a good default... but only as 
 long as the ISP allows exceptions.  As a paying subscriber with a 
 clean record I *must* be allowed to ask for a hole through your 
 firewall.

Sure, as long as you can prove your email server is not an open relay.

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]


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



Signal 6

1999-09-26 Thread Stephan van Beerschoten

When making /usr/ports/x11/gnome, the compiler fails with the following:

obgtkObject.m: In function `obgtk_signal_relay':
obgtkObject.m:133: Could not find a spill register
(insn:HI 564 562 565 (set (mem:DF (reg:SI 0 %eax))
(subreg:DF (reg:SI 128) 0)) 77 {movdf_mem+1} (insn_list 562 (nil))
(expr_list:REG_DEAD (reg:SI 0 %eax)
(nil)))
gcc: Internal compiler error: program cc1obj got fatal signal 6
*** Error code 1

This is reproducable simply by changing to the directory and executing the
gcc line.
I'd like to know if this is -current related (gcc), or -ports related (gnome).

Has anyone else experienced this ?

-Steve


-- 
Stephan van BeerschotenEmail: [EMAIL PROTECTED] 
Network Engineer   Luna Internet Services www.luna.nl
   PO Box 28013 3003 KA  Rotterdam NL
PGPKey fingerprint = 45 57 97 61 B2 12 FB 4C  77 8D 35 29 C4 2A 2D 27
 "RETURN VALUES: The panic() function call does not return" :P


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



Re: Boot problems with new -current

1999-09-26 Thread Bruce Evans

On Sun, 26 Sep 1999, Cejka Rudolf wrote:

 Ok: Just run "disklabel -r -e ad0", clear word "badsect"
 in "Flags:" line and booting of new kernels is back...

I think phk set to switch back to the wd driver to run disklabel, but
that shouldn't be necessary -- a new label can certainly be written
using the ad driver, so something would have to be broken for an old
or broken label not to be modifiable.

 Soren Schmidt wrote (1999/09/25):
 
  The ATA driver has no bad144 support, thats probably why you get
  the above message. The reason is that modern ATA disks does internal
  bad block remapping (just as SCSI), and if you have used up all
  the spares you better swap that disk for another one, its going
  bad on you no matter what...
 
 But in earlier versions ATA driver worked for me. Does this mean that

That was because earlier versions of the ad driver were too broken to
handle the bad block table properly.  They silently ignored the error
of having one, and would probably have corrupted your data if the
table was non-null.  Your table seems to have been null, so there were
no problems.

 flag "badsect" was silently ignored and now it have an effect on
 a panic? Isn't a big warning message sufficient instead of a panic?

It's just an error.  IIRC, the panic was because your root file system
became inaccessible.

Bruce



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



ata driver question..

1999-09-26 Thread Viren R. Shah


I made world and build a new kernel on Friday the 24th, and later that
evening, I got these:

Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost disk contact - 
resetting
Sep 24 18:00:33 jabberwock /kernel: ata0: resetting devices .. done




Today morning, I found my machine "hung" (couldn't kill old processes,
couldn't start new ones). 

Any ideas?


Here's the kernel config:

#
#
# For more information read the handbook part System Administration - 
# Configuring the FreeBSD Kernel - The Configuration File. 
# The handbook is available in /usr/share/doc/handbook or online as
# latest version from the FreeBSD World Wide Web server 
# URL:http://www.FreeBSD.ORG/
#
# An exhaustive list of options and more detailed explanations of the 
# device lines is present in the ./LINT configuration file. If you are 
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
#   $Id: GENERIC,v 1.118 1998/09/18 00:46:40 mjacob Exp $

machine "i386"
cpu "I686_CPU"
ident   "J38"
maxusers128

options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!]
options UCONSOLE#Allow users to grab the console


# Allow the FFS to use Softupdates technology.
# To do this you need to copy the two files
# /sys/ufs/ffs/softdep.h and /sys/ufs/ffs/ffs_softdep.c
# from /usr/src/contrib/sys/softupdates
# and understand the licensing restrictions.
# You should also check on the FreeBSD website for newer versions.
optionsSOFTUPDATES

controller  isa0
controller  pci0

controller  fdc0at isa? port "IO_FD1"  irq 6 drq 2 
diskfd0 at fdc0 drive 0

controller  ata0
device  atadisk0# ATA disk drives
device  atapicd0# ATAPI CDROM drives
#device atapifd0# ATAPI floppy drives
#device atapist0# ATAPI tape drives


controller  ahc0


device  pass0
controller  scbus0

device  da0

# atkbdc0 controls both the keyboard and the PS/2 mouse
controller atkbdc0 at isa? port IO_KBD
device atkbd0  at atkbdc?  irq 1
device psm0at atkbdc?  irq 12

device  vga0at isa? port ? conflicts
device  sc0 at isa? 

device npx0at nexus? port IO_NPX irq 13


device  sio0at isa? port "IO_COM1" flags 0x10  irq 4 





pseudo-device   loop
pseudo-device   ether
pseudo-device   pty 48
pseudo-device   bpf 2   #Berkeley packet filter
#pseudo-device   splash

# KTRACE enables the system-call tracing facility ktrace(2).
# This adds 4 KB bloat to your kernel, and slightly increases
# the costs of each syscall.
options KTRACE  #kernel tracing

# This provides support for System V shared memory.
#
options SYSVSHM
options SYSVSEM
options SYSVMSG

# sound card stuff

controller pnp0

#device pcm0 at nexus ? port?  irq 5 drq 1 
device pcm0  

options USER_LDT#allow user-level control of i386 ldt

options P1003_1B
options _KPOSIX_PRIORITY_SCHEDULING
options _KPOSIX_VERSION=199309L




-- 
Viren Shah  | IF YOU CAN'T BE GOOD, BE LOUD.
[EMAIL PROTECTED]   |  -- Frank Hill
RST, Inc|


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



Re: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread Rodney W. Grimes

   If _we_ don't start to do something about it, big brother _is_ going
   to do something about it.  Trust me on this one, being a member of the
   USPA I know that we are far better off implementing our own (as ISP's)
   set of safe gaurds that help eliminate certain undesirable behavior.
  [.]
  
  I think it's up to the ISP what default policies they have, and I 
  also think that this sort of policy is a good default... but only as 
  long as the ISP allows exceptions.  As a paying subscriber with a 
  clean record I *must* be allowed to ask for a hole through your 
  firewall.
 
 Sure, as long as you can prove your email server is not an open relay.

We do not even require proof of that.  Or should I say the proof that
you will continue to have a ``clean record'' is that your services
will be terminated if you don't keep it clean, and the balance on
your current contract is still owed us.  It is written as an early
termination clause without relief from finacial burden, you can
find them in most ``leases'' of any reasonable duration.

One of the bigger problems we faced was new customers who wanted the
wavier right up front, we had no track history on them, so no ``clean
record'' existed.  We decided that reasonable finacial burden would
at least keep the honest folks honest and give us a legal axe to
swing at the bad boys with.  It's much easier to file a claim for
breach of contract due to non-payment than it is for violation of
an AUP or ``spamming'' :-)

It has been effective, we had a known spammer approach us for
connectivity, who we knew had already been terminated by another
ISP for spamming.  We explained our policy to him and
he said, nope, no thanks I don't want to buy anything from you.

This, IMHO, is going to be about the only way there is to put
these folks out of the business.  Our at least get them to
look at a more proper bulk email model.

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


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



Re: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread Gary Palmer

Brian Somers wrote in message ID
[EMAIL PROTECTED]:
  I have some experience (from anti-spam mailing lists) of ISP's who
  are quite prepared to open port 25 for customers who ask. This is
  very good; SMTP has no authentication at all, and it is this
  "free-for-all" feature that spammers abuse. However - with a view
 [.]
 
 I belive sendmail-8.10 will have smtp authentication built in.  
 There's an rfc too (2554) but I can't say that they're the same thing 
 for sure.

There are two `standards' from SMTP Auth out there ... one by Netscape
(which is that rfc), and one by M$.  To date, only Netscape 4.5 and
higher (I believe), and products from Software.com (i.e. InterMail)
support the netscape version (although I haven't looked in a few
months, so I could be wrong).  M$ Exchange and Outlook and so on
support the M$ version of SMTP Auth, although I've been told that the
two use different commands so (in theory) you can support both on the
same box, althgouh I don't know of anyone planning or doing that.


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Donald J . Maddox

The whole point is that I want to be able to use the wavetable
synthesis features of the card.  Newpcm (or oldpcm, for that matter)
provides NO support for the AWE device whatsoever, as you can see
from your dmesg below.

It makes little sense to me that PnP functionality should be tied
down to a particular audio driver.  Obviously, the newpnp code is
not as versatile as the oldpnp code was, because the oldpnp code
worked with my card regardless of whether I used snd or pcm.

I'm just suggesting here that it would be nice if the authors of
this code would make it _equally functional_ to what was removed.
It's not nice to remove functionality unconditionally and then
provide no replacement at all...


On Sun, Sep 26, 1999 at 12:58:58PM +0200, Ollivier Robert wrote:

 Can you try to new newpcm ?
 
 controller pnp0
 device pcm0
 
  The first 2 lines have always been unnecessary, but harmless; however, the
  3rd line is _absolutely necessary_ to get the AWE to probe.
 
 The above works for my AWE64.
 
 pcm0: SB16 PnP at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
 unknown0: Game at port 0x200-0x207 on isa0
 unknown1: WaveTable at port 0x620-0x623 on isa0
 
 FreeBSD Audio Driver (newpcm) Sep  9 1999 00:19:32
 Installed devices:
 pcm0: SoundBlaster 16 4.16 at io 0x220 irq 5 drq 1:5 (1/1 channels duplex)
 
 -- 
 Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
 FreeBSD keltia.freenix.fr 4.0-CURRENT #74: Thu Sep  9 00:20:51 CEST 1999
 
 
 
 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: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread Gary Palmer

Brian Somers wrote in message ID
[EMAIL PROTECTED]:
 I think it's up to the ISP what default policies they have, and I 
 also think that this sort of policy is a good default... but only as 
 long as the ISP allows exceptions.  As a paying subscriber with a 
 clean record I *must* be allowed to ask for a hole through your 
 firewall.

No, actually, there is absolutely nothing which says that you, as a
subscriber of good standing, *have* to be allowed to connect to
non-local port 25.  I think it is perfectly reasonable that the ISP
require that you buy a static IP (with N months initially prepaid) or
something to get port 25 privs.

If you want to go after the real source of the problem, then lobby
your local government to make spammers pay for the damage they do.
Otherwise the `freedom' of the old internet will be worn away because
ISPs will have to protect themselves more and more.

Anyhow, this is completely offtopic ... mail me in private if you want
to continue :)


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Gary Palmer

"Donald J . Maddox" wrote in message ID
[EMAIL PROTECTED]:
 I'm just suggesting here that it would be nice if the authors of
 this code would make it _equally functional_ to what was removed.
 It's not nice to remove functionality unconditionally and then
 provide no replacement at all...

If people lose functionality, then it motivates them to help the
author replace the functionality that is important to them, and for
devices that the author probably has no access to

We're a volunteer project Donald, and screaming blue murder 'cos your
foo card doesn't work as well as it used to gets us nowhere.  Have
you contacted the newpcm author and asked if you can help to get AWE64
support back?  Thats probably the best way to proceed.


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Donald J . Maddox

On Sun, Sep 26, 1999 at 01:11:55PM -0400, Gary Palmer wrote:
 "Donald J . Maddox" wrote in message ID
 [EMAIL PROTECTED]:
  I'm just suggesting here that it would be nice if the authors of
  this code would make it _equally functional_ to what was removed.
  It's not nice to remove functionality unconditionally and then
  provide no replacement at all...
 
 If people lose functionality, then it motivates them to help the
 author replace the functionality that is important to them, and for
 devices that the author probably has no access to
 
 We're a volunteer project Donald, and screaming blue murder 'cos your
 foo card doesn't work as well as it used to gets us nowhere.  Have
 you contacted the newpcm author and asked if you can help to get AWE64
 support back?  Thats probably the best way to proceed.

Ummm...  I'm not screaming anything, Gary.  The intent of my message is
just to let the authors of this code know that it is *not* equal in
functionality to what was removed.  As I said in my original message, it
would be nice to see that functionality restored.

It may very well be that the authors are aware of this, and just don't
give a damn.  I prefer to give them the benefit of the doubt.



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



Re: -current panic w/linux netscape

1999-09-26 Thread Marcel Moolenaar

Mike Pritchard wrote:

 I have a panic that I can duplicate with a 24 hour old "make world"
 and a 4 hour old -current kernel.

If you use the linux module, make sure it's in sync with the kernel. If
that doesn't help, either follow Matt's advice or use ktrace/truss.

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


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



Re: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread Matthew Dillon


:Brian Somers wrote in message ID
:[EMAIL PROTECTED]:
: I think it's up to the ISP what default policies they have, and I 
: also think that this sort of policy is a good default... but only as 
: long as the ISP allows exceptions.  As a paying subscriber with a 
: clean record I *must* be allowed to ask for a hole through your 
: firewall.
:
:No, actually, there is absolutely nothing which says that you, as a
:subscriber of good standing, *have* to be allowed to connect to
:non-local port 25.  I think it is perfectly reasonable that the ISP
:require that you buy a static IP (with N months initially prepaid) or
:something to get port 25 privs.

ISP's have begun to do this sort of blocking because dialup spammers 
abuse their privilages so much that a single spammer can cause an ISP
to get inundated with complaints, yet the ISP can do little about it
other then kick the spammer off (which solves nothing, really, considering
how cheap dialup accounts are). 

Frankly, I have to agree that no dynamic dialup user should be allowed
to connect through to port 25 on anything but the ISPs own mail server.

-Matt



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



Re: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread Gary Palmer

Alex Zepeda wrote in message ID
Pine.BSF.4.10.9909261017060.367-10@localhost:
 No, the real problem is the ISPs who can't fund decent servers and provide
 decent service.  If they could take care of spam and provide a 99%
 reliable service, I'd have very few problems with using their mailservers.

If they can't provide a reliable OGM server, find a different ISP, no
matter what else.  And I fail to see how they can `take care of spam'
if you won't let them close it at the source ... people doing direct
injection of spam to the recipients MX and relay raping others to hide
their tracks.  ISPs blocking outbound port 25 from dynamic dialups and
inbound port 25 to people who shouldn't be running servers (e.g. your
average cablemodem customer, a fair number of whom run open relays,
and most of whom have a TOS which doesn't allow them to run `servers'
in the first place) will cure a lot of problems, whether you like it
or not.

More than 75% of ISP customers would like less spam ... but they
*have* to be willing to accept that to stop the spammer they may have
to jump through a new hoop.

Heck, I believe a UK company (FreeServe?) uses a L4 switch (or some
similar technology) to redirect all outbound port 25 traffic to
their SMTP servers.  US ISPs probably don't have that choice if they
cover any territory at all (the cost of the switches becomes
prohibitive as you need one per POP), but a Cisco ACL would work just
as well at stopping the problem.

A growing number of companies block dynamic dialup blocks from
connecting to their inbound mail servers.  We do it by TCP wrapping
sendmail and doing wildcard matching of hostnames.  Other people use
the MAPS DUL or the (now, and probably temporarily, dead) IMRSS DSSL.
So even if your ISP does let port 25 out, its usefulness is *very*
shortlived.


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Gary Palmer

"Donald J . Maddox" wrote in message ID
[EMAIL PROTECTED]:
 Ummm...  I'm not screaming anything, Gary.  The intent of my message is
 just to let the authors of this code know that it is *not* equal in
 functionality to what was removed.  As I said in my original message, it
 would be nice to see that functionality restored.

And how much time/resources are you willing to dedicate to restoration
of functionality *YOU* need?

 It may very well be that the authors are aware of this, and just don't
 give a damn.  I prefer to give them the benefit of the doubt.

They probably give a damn, but it goes a long way if you HELP them
rather than go around demanding stuff be put back.


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Mike Smith

 Sigh.  Again, I didn't demand anything.
 
 I simply pointed out that functionality had been lost.  If I
 was the author of this code, I would *want* feedback on how
 it was working out for people out here in userland.  I assume
 that the authors in question _do_ want such feedback.

Actually, in your case, no.  The "functionality" you're claiming was 
lost was actually an unintentional side-effect of the code which will 
intentionally not be emulated. 

You are encouraged to participate in the ongoing development of our new 
sourd drivers in order to ensure they meet the functionality of the old 
ones, since that _is_ lost functionality that we care about.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Donald J . Maddox

On Sun, Sep 26, 1999 at 10:51:59AM -0700, Mike Smith wrote:
  Sigh.  Again, I didn't demand anything.
  
  I simply pointed out that functionality had been lost.  If I
  was the author of this code, I would *want* feedback on how
  it was working out for people out here in userland.  I assume
  that the authors in question _do_ want such feedback.
 
 Actually, in your case, no.  The "functionality" you're claiming was 
 lost was actually an unintentional side-effect of the code which will 
 intentionally not be emulated. 

I'm not sure I follow you here.  My card was recognized and configured
properly by the old PnP code.  It is not recognized and configured
properly by the new PnP code.  How can that be classified as simply
'an unintentional side-effect of the code'?

It seems to me that PnP functionality should not be dependant on any
particular driver...  I mean, the PnP code and the audio code (and the
network driver code, and any other possible PnP device driver code)
are seperate things, no?  Shouldn't it be the job of the PnP code to
recognize and configure the device so that it probes and attaches,
regardless of what driver finds it?  At least, it appears to me that
that is what the old PnP code did.  My card worked just fine with it,
regardless of whether I selected 'pcm' or 'snd' in my kernel config.

 
 You are encouraged to participate in the ongoing development of our new 
 sourd drivers in order to ensure they meet the functionality of the old 
 ones, since that _is_ lost functionality that we care about.


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



New PnP code does not work for me(?)

1999-09-26 Thread Donald J . Maddox

I couldn't get my PnP Creative AWE64G to work with the new PnP
code, so I tried compiling a kernel with pcm instead.  All I get is:

unknown0: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
unknown1: Game at port 0x200-0x207 on isa0
unknown2: WaveTable at port 0x620-0x623 on isa0

It is my understanding that, with the new PnP code, I should not have to
specify the ports, IRQs, DMA, etc., right?  Here is the config I used:

machine i386
ident   RHIANNON
maxusers128
options MAXDSIZ="(256*1024*1024)"
options DFLDSIZ="(256*1024*1024)"
options INCLUDE_CONFIG_FILE
cpu I586_CPU
options COMPAT_43
options USER_LDT
options SYSVSHM
options SYSVSEM
options SYSVMSG
options MD5
options DDB
options KTRACE
options PERFMON
options UCONSOLE
options USERCONFIG
options VISUAL_USERCONFIG
options INET
pseudo-device   loop
pseudo-device   bpf 4
pseudo-device   disc2
pseudo-device   tun 2
pseudo-device   ppp 2
pseudo-device   streams
options PPP_BSDCOMP
options PPP_DEFLATE
options PPP_FILTER
options MROUTING
options FFS
#optionsCD9660
options MFS
#optionsMSDOSFS
#optionsPROCFS
options SOFTUPDATES
options NSWAPDEV=20
controller  scbus0
device  da0
device  cd0
device  pass0
options SCSI_REPORT_GEOMETRY
pseudo-device   pty 32
pseudo-device   speaker
pseudo-device   gzip
#pseudo-device  vn
pseudo-device   snp 3
pseudo-device   splash
controller  isa0
options AUTO_EOI_1
options AUTO_EOI_2
controller  pnp0
controller  atkbdc0 at isa? port IO_KBD
device  atkbd0  at atkbdc? irq 1
device  sc0 at isa?
device  vga0at isa? port ? conflicts
options MAXCONS=32
#optionsSTD8X16FONT
options SC_HISTORY_SIZE=1000
options SC_PIXEL_MODE
device  npx0at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13
controller  wdc0at isa? port IO_WD1 irq 14 flags 0xb0ffb0ff
diskwd0 at wdc0 drive 0
diskwd1 at wdc0 drive 1
controller  fdc0at isa? port IO_FD1 irq 6 drq 2
diskfd0 at fdc0 drive 0
device  sio0at isa? port IO_COM1 flags 0x10 irq 4
device  sio1at isa? port IO_COM2 irq 3
device  sio2at isa? port IO_COM3 flags 0x2000 irq 12
#device sio2at isa? port IO_COM3 flags 0x2 irq 12
device  sio3at isa? port IO_COM4 irq 9
#controller snd0
#device sb0 at isa? port 0x220 irq 5 drq 1
#device sbxvi0  at isa? drq 5
#device sbmidi0 at isa? port 0x330
#device awe0at isa? port 0x620
#device opl0at isa? port 0x388
device  pcm0#at isa? port ? irq 5 drq 1 flags 0x15
#device pca0at isa? port IO_TIMER1
#device joy0at isa? port 0x200
options AHC_ALLOW_MEMIO
controller  pci0
controller  ahc0
#optionsEXT2FS
options SHOW_BUSYBUFS
options SHMALL=1025
options SHMMAX="(SHMMAXPGS*PAGE_SIZE+1)"
options SHMMAXPGS=1025
options SHMMIN=2
options SHMMNI=33
options SHMSEG=9
options MSGBUF_SIZE=40960
#optionsVESA
options P1003_1B
options _KPOSIX_PRIORITY_SCHEDULING
options _KPOSIX_VERSION=199309L

And here is the pnpinfo output:

Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID CTL009e (0x9e008c0e), Serial Number 0x09f665ec
PnP Version 1.0, Vendor Version 32
Device Description: Creative SB AWE64 Gold

Logical Device ID: CTL0044 0x44008c0e #0
Device Description: Audio
TAG Start DF
Good Configuration
IRQ: 5  - only one type (true/edge)
DMA: channel(s) 1 
8-bit, not a bus master, count by byte, , Compatibility mode
DMA: channel(s) 5 
16-bit, not a bus master, , count by word, Compatibility mode
I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10
[16-bit addr]
I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2
[16-bit addr]
I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4
[16-bit addr]
TAG Start DF
Acceptable Configuration
IRQ: 5 7 9 10  - only one type (true/edge)
DMA: channel(s) 0 1 3 
8-bit, not a bus master, count by byte, , Compatibility mode
DMA: channel(s) 5 6 7 
16-bit, not a bus master, , count by word, Compatibility mode
I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10
[16-bit addr]
I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2
[16-bit addr]
I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4
[16-bit addr]
TAG Start DF
Acceptable Configuration
IRQ: 5 7 9 10  - only one type (true/edge)
DMA: channel(s) 0 1 3 
8-bit, not a bus master, count by byte, , 

Re: Loss of Functionality with newpnp

1999-09-26 Thread Mike Smith

 On Sun, Sep 26, 1999 at 10:51:59AM -0700, Mike Smith wrote:
   Sigh.  Again, I didn't demand anything.
   
   I simply pointed out that functionality had been lost.  If I
   was the author of this code, I would *want* feedback on how
   it was working out for people out here in userland.  I assume
   that the authors in question _do_ want such feedback.
  
  Actually, in your case, no.  The "functionality" you're claiming was 
  lost was actually an unintentional side-effect of the code which will 
  intentionally not be emulated. 
 
 I'm not sure I follow you here.  My card was recognized and configured
 properly by the old PnP code.  It is not recognized and configured
 properly by the new PnP code.  How can that be classified as simply
 'an unintentional side-effect of the code'?

PnP is an infrastructure facility used by drivers to detect and 
configure hardware.  The side-effect you were relying on was that the 
old code would indiscriminately configure any and all PnP hardware 
regardless of whether a driver had requested it to.

 It seems to me that PnP functionality should not be dependant on any
 particular driver...  I mean, the PnP code and the audio code (and the
 network driver code, and any other possible PnP device driver code)
 are seperate things, no?

No.

  Shouldn't it be the job of the PnP code to
 recognize and configure the device so that it probes and attaches,
 regardless of what driver finds it?

No.

  At least, it appears to me that
 that is what the old PnP code did.  My card worked just fine with it,
 regardless of whether I selected 'pcm' or 'snd' in my kernel config.

I don't think an explanation of how PnP works or how it fits into our 
device architecture is feasible at this point, so I'm going to 
encourage you to do some research of your own. 

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



Demand-loaded network ifs and bpf

1999-09-26 Thread Donald J . Maddox

I see that support has been added for demand-loading network
if drivers.  I seem to recall that the last time I tried using
network drivers as klds, nothing that required bpf to work
was functional anymore, because bpf required that the device
existed at the time it was initialized.  Is this still the case?
Will bpf work for demand-loaded network klds?


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Donald J . Maddox

On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
 
 PnP is an infrastructure facility used by drivers to detect and 
 configure hardware.  The side-effect you were relying on was that the 
 old code would indiscriminately configure any and all PnP hardware 
 regardless of whether a driver had requested it to.
 

Why is this not desirable?


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



Re: make world, attempt 5

1999-09-26 Thread Sheldon Hearn



On Sun, 26 Sep 1999 09:00:50 +0930, Greg Lehey wrote:

 I've been trying for the last 24 hours solid to make a new world.  The
 latest problem is:

:-(

 /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245:
 syntax error before `'

Hi Greg,

I was the last person to touch that file, but I honestly can't see why
you're having a problem with it.

Are you sure that you have hosts_access.c rev 1.2 ?

Ciao,
Sheldon.


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Mike Smith

 On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
  
  PnP is an infrastructure facility used by drivers to detect and 
  configure hardware.  The side-effect you were relying on was that the 
  old code would indiscriminately configure any and all PnP hardware 
  regardless of whether a driver had requested it to.
 
 Why is this not desirable?

I've already asked you to do your own research, and I meant it.  The 
simple answer is "if we don't have a [working] driver for it, we don't 
want it".

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Donald J . Maddox

On Sun, Sep 26, 1999 at 11:59:33AM -0700, Mike Smith wrote:
  On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:
   
   PnP is an infrastructure facility used by drivers to detect and 
   configure hardware.  The side-effect you were relying on was that the 
   old code would indiscriminately configure any and all PnP hardware 
   regardless of whether a driver had requested it to.
  
  Why is this not desirable?
 
 I've already asked you to do your own research, and I meant it.  The 
 simple answer is "if we don't have a [working] driver for it, we don't 
 want it".

But we do have a working driver for the AWE64.  Or rather, it worked fine
before the new PnP code was comitted, now it doesn't.  It seems to me that
this indicates a deficiency in the new PnP code.  Isn't that correct?


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



Re: Experimental ACPI driver.

1999-09-26 Thread Mike Smith

 Hi, there.
 
  We wrote experimental ACPI driver for 4.0-CURRENT.
 
 This was just one week work so its functionallity is very very poor :-)
 but I think it is good idea to start with this for developping ACPI
 driver for FreeBSD because it is enough small to understand it.

I'm not sure this is the right way to go about it, although I haven't 
looked at your code yet.  APCI is a big animal, and I think it's going 
to take a proper design to get it right.

The key components would appear to be a full AML parser, an object 
manager to manage the ACPI namespace, and an AML interpreter to run the 
AML methods.

 If someone already started wriring ACPI devive driver, please let us
 know.  We'd like to merge them and would be happy in collaboration
 with you.

Both Doug Rabson and myself have been tinkering with this, and there's 
someone that's been looking at an AML parser/interpreter in the last 
couple of weeks.  At this point in time, the parser and object manager 
are the most vital components.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Kenneth Wayne Culver

This is only partially related, but I still can't even boot a kernel with
the pnp0 controller enabled. It just hangs after probing the soundcard.

On Sun, 26 Sep 1999, Mike Smith wrote:

  Sigh.  Again, I didn't demand anything.
  
  I simply pointed out that functionality had been lost.  If I
  was the author of this code, I would *want* feedback on how
  it was working out for people out here in userland.  I assume
  that the authors in question _do_ want such feedback.
 
 Actually, in your case, no.  The "functionality" you're claiming was 
 lost was actually an unintentional side-effect of the code which will 
 intentionally not be emulated. 
 
 You are encouraged to participate in the ongoing development of our new 
 sourd drivers in order to ensure they meet the functionality of the old 
 ones, since that _is_ lost functionality that we care about.
 
 -- 
 \\  The mind's the standard   \\  Mike Smith
 \\  of the man.   \\  [EMAIL PROTECTED]
 \\-- Joseph Merrick   \\  [EMAIL PROTECTED]
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Mike Smith

 On Sun, Sep 26, 1999 at 11:59:33AM -0700, Mike Smith wrote:
   On Sun, Sep 26, 1999 at 11:41:14AM -0700, Mike Smith wrote:

PnP is an infrastructure facility used by drivers to detect and 
configure hardware.  The side-effect you were relying on was that the 
old code would indiscriminately configure any and all PnP hardware 
regardless of whether a driver had requested it to.
   
   Why is this not desirable?
  
  I've already asked you to do your own research, and I meant it.  The 
  simple answer is "if we don't have a [working] driver for it, we don't 
  want it".
 
 But we do have a working driver for the AWE64.  Or rather, it worked fine
 before the new PnP code was comitted, now it doesn't.  It seems to me that
 this indicates a deficiency in the new PnP code.  Isn't that correct?

No.

I have already explained to you that the AWE64 driver that you were 
using (one actually of _three_ that we have) only worked with PnP cards 
as an accidental side-effect of the old PnP code.  Now that the PnP 
code has been fixed, the brokenness of the old driver is exposed.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Mike Smith

 This is only partially related, but I still can't even boot a kernel with
 the pnp0 controller enabled. It just hangs after probing the soundcard.

You seem to have accidentally deleted all of the details related to 
this bug report from your email before sending it.  Please try again.
-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



Re: make world, attempt 5

1999-09-26 Thread D. Rock

Greg Lehey schrieb:
 
 I've been trying for the last 24 hours solid to make a new world.  The
 latest problem is:
 
 === libwrap
 cc -nostdinc -O -pipe -DFACILITY=LOG_AUTH -DHOSTS_ACCESS -DNETGROUP 
-DDAEMON_UMASK=022  -DREAL_DAEMON_DIR=\"/usr/libexec\" -DPROCESS_OPTIONS  
-DSEVERITY=LOG_INFO -DRFC931_TIMEOUT=10  -DHOSTS_DENY=\"/etc/hosts.deny\" 
-DHOSTS_ALLOW=\"/etc/hosts.allow\"  -DSYS_ERRLIST_DEFINED -DALWAYS_HOSTNAME 
-I/usr/obj/src/PANIC/src/tmp/usr/include -c 
/src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c -o hosts_access.o
 /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245: syntax 
error before `'
 /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:84: warning: 
`host_match' declared `static' but never defined
 /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:85: warning: 
`string_match' declared `static' but never defined
I know these errors.

Mostly they are caused by local modifications of the source. If you then
"cvs update"
your tree, and there is a conflict, the offending lines are surrounded
by

Your Code
===
New Code


I also have overseen cvs conflicts dozens of time.

Daniel


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread D. Rock

"Donald J . Maddox" schrieb:
 Is the new PnP code really so smart that it has no use for user intervention
 ever?  My experience indicates that it is not.
 
 It would be very nice if the architects of the new PnP code would add back
 this lost functionality.
My (QD) solution for this problem:

Get rid of
controller  pnp0
in your config-file.

Write down the Port/IRQ/DMA of all your PnP cards, then configure them
the
hard way (they normally don't change between reboots).

This was my solution to get my PnP ISDN card working again (i4b isn't
yet
converted to newPnP). As a side effect I also had to manually configure
my NE2000 compatible PnP card manually.

Before
---
controller  pnp0
device  ed0
device  isic0
--
ed0: NE2000 Compatible at port 0x220-0x23f irq 3 on isa0
ed0: address 00:40:05:38:7b:a4, type NE2000 (16 bit)
unknown3: speed win SEDLBAUER AG at port 0x108-0x10f irq 11 on isa0

After
---
device  ed0 at isa? port 0x220 irq 3
device  isic0   at isa? port 0x108 irq 11 flags 9
--
ed0 at port 0x220-0x23f irq 3 on isa0
ed0: address 00:40:05:38:7b:a4, type NE2000 (16 bit)
isic0 at port 0x108 irq 11 flags 0x9 on isa0
isic0: Sedlbauer WinSpeed
isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2)
(Addr=0x10a)
isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x10b, AddrB=0x10d)

The ISDN card needed some additional tweaking, since it a PnP only card
and
isn't expected to run as a non-PnP card, but the sound driver should be
just
like the ed driver.


Daniel


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



Re: New PnP code does not work for me(?)

1999-09-26 Thread D. Rock

"Donald J . Maddox" schrieb:
 
 I couldn't get my PnP Creative AWE64G to work with the new PnP
 code, so I tried compiling a kernel with pcm instead.  All I get is:
 
 unknown0: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
 unknown1: Game at port 0x200-0x207 on isa0
 unknown2: WaveTable at port 0x620-0x623 on isa0
unknown indicates that no driver seems to be responsible for this card.
I had a similar problem with an Aztech sound card, which should be MSS
compatible.

 Logical Device ID: CTL0044 0x44008c0e #0
 Device Description: Audio
[...]

You should check your Device IDs with the ones in
/sys/dev/pcm/isa/sb.c

You should add your IDs at the right place there (it should be easy to
find).
Only use the "Audio" ID (CTL0044)

Daniel


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Donald J . Maddox

Thanks.  That is exactly what I have done.  The AWE device cannot
work this way, but everything else is functional if I remove the
PnP controller from my kernel...

On Sun, Sep 26, 1999 at 10:04:38PM +0200, D. Rock wrote:
 "Donald J . Maddox" schrieb:
  Is the new PnP code really so smart that it has no use for user intervention
  ever?  My experience indicates that it is not.
  
  It would be very nice if the architects of the new PnP code would add back
  this lost functionality.
 My (QD) solution for this problem:
 
 Get rid of
 controllerpnp0
 in your config-file.
 
 Write down the Port/IRQ/DMA of all your PnP cards, then configure them
 the
 hard way (they normally don't change between reboots).
 
 This was my solution to get my PnP ISDN card working again (i4b isn't
 yet
 converted to newPnP). As a side effect I also had to manually configure
 my NE2000 compatible PnP card manually.
 
 Before
 ---
 controllerpnp0
 deviceed0
 deviceisic0
 --
 ed0: NE2000 Compatible at port 0x220-0x23f irq 3 on isa0
 ed0: address 00:40:05:38:7b:a4, type NE2000 (16 bit)
 unknown3: speed win SEDLBAUER AG at port 0x108-0x10f irq 11 on isa0
 
 After
 ---
 deviceed0 at isa? port 0x220 irq 3
 deviceisic0   at isa? port 0x108 irq 11 flags 9
 --
 ed0 at port 0x220-0x23f irq 3 on isa0
 ed0: address 00:40:05:38:7b:a4, type NE2000 (16 bit)
 isic0 at port 0x108 irq 11 flags 0x9 on isa0
 isic0: Sedlbauer WinSpeed
 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2)
 (Addr=0x10a)
 isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x10b, AddrB=0x10d)
 
 The ISDN card needed some additional tweaking, since it a PnP only card
 and
 isn't expected to run as a non-PnP card, but the sound driver should be
 just
 like the ed driver.
 
 
 Daniel
 
 
 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: New PnP code does not work for me(?)

1999-09-26 Thread Donald J . Maddox

Thanks again, Daniel...  I'll take a look.  If the ID isn't in there,
I'll submit a PR to get it added.  (should only take about 10-12
months to actually get it comitted, if experience is a reliable guide :-/)

On Sun, Sep 26, 1999 at 10:09:58PM +0200, D. Rock wrote:
 "Donald J . Maddox" schrieb:
  
  I couldn't get my PnP Creative AWE64G to work with the new PnP
  code, so I tried compiling a kernel with pcm instead.  All I get is:
  
  unknown0: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
  unknown1: Game at port 0x200-0x207 on isa0
  unknown2: WaveTable at port 0x620-0x623 on isa0
 unknown indicates that no driver seems to be responsible for this card.
 I had a similar problem with an Aztech sound card, which should be MSS
 compatible.
 
  Logical Device ID: CTL0044 0x44008c0e #0
  Device Description: Audio
 [...]
 
 You should check your Device IDs with the ones in
 /sys/dev/pcm/isa/sb.c
 
 You should add your IDs at the right place there (it should be easy to
 find).
 Only use the "Audio" ID (CTL0044)
 
 Daniel
 
 
 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: New PnP code does not work for me(?)

1999-09-26 Thread Peter Wemm

"Donald J . Maddox" wrote:
 I couldn't get my PnP Creative AWE64G to work with the new PnP
 code, so I tried compiling a kernel with pcm instead.  All I get is:
 
 unknown0: Audio at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 o
n isa0
 unknown1: Game at port 0x200-0x207 on isa0
 unknown2: WaveTable at port 0x620-0x623 on isa0
[..]
 Card assigned CSN #1
 Vendor ID CTL009e (0x9e008c0e), Serial Number 0x09f665ec
 PnP Version 1.0, Vendor Version 32
 Device Description: Creative SB AWE64 Gold
 
 Logical Device ID: CTL0044 0x44008c0e #0
 ^^
[..]

Thank you! Finally, that was the information needed.  (The logical device
ID)

Please try the following patch:

Index: src/sys/dev/pcm/isa/sb.c
===
RCS file: /home/ncvs/src/sys/dev/pcm/isa/sb.c,v
retrieving revision 1.23
diff -u -r1.23 sb.c
--- sb.c1999/09/07 08:42:44 1.23
+++ sb.c1999/09/26 20:23:34
@@ -1258,6 +1309,7 @@
case 0x31008c0e: /* CTL0031 */
case 0x41008c0e: /* CTL0041 */
case 0x42008c0e: /* CTL0042 */
+   case 0x44008c0e: /* CTL0044 */
case 0x45008c0e: /* CTL0045 */
s = "SB16 PnP";
break;

Cheers,
-Peter



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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Hellmuth Michaelis

From the keyboard of Mike Smith:

 I don't think an explanation of how PnP works or how it fits into our 
 device architecture is feasible at this point, so I'm going to 
 encourage you to do some research of your own. 

An explanation of how PnP works is not necessary, some good books and
papers exist on this topic.

But an explanation of the new device architecture for non-architects
which is a bit more helpful than http://www.freebsd.org/~dfr/devices.html
and how the new-PnP code fits into that would be very helpful and i'm
quite shure that this would enable much more people to actually work
with the code and fix problems rather than just complaining here.

hellmuth
-- 
Hellmuth MichaelisTel   +49 40 559747-70
HCS Hanseatischer Computerservice GmbHFax   +49 40 559747-77
Oldesloer Strasse 97-99   Mail  hm [at] hcs.de
22457 Hamburg WWW   http://www.hcs.de


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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Hellmuth Michaelis

From the keyboard of Kenneth Wayne Culver:

 This is only partially related, but I still can't even boot a kernel with
 the pnp0 controller enabled. It just hangs after probing the soundcard.

Same here for a week or two in which dfr was very helpful to try to find 
out what happened.

With new userland and kernel made yesterday (25.) the problem silently 
disappeared without a trace and i'm able to boot again. Silly ..

hellmuth
-- 
Hellmuth MichaelisTel   +49 40 559747-70
HCS Hanseatischer Computerservice GmbHFax   +49 40 559747-77
Oldesloer Strasse 97-99   Mail  hm [at] hcs.de
22457 Hamburg WWW   http://www.hcs.de


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



Re: New PnP code does not work for me(?)

1999-09-26 Thread Peter Wemm

"Donald J . Maddox" wrote:
 Ok, will do.  Thanks.
 
 This may be a silly question, but...  The old PnP driver recognized
 a lot of devices, including my AWE64.  Isn't there a list of IDs it
 was aware of that should be merged into newPnP ASAP?

The old PnP code was matching on the card vendor ID.  The new pnp code
treats each logical device on it's own and matches by logical ID..
(It's actually far more useful that way as most cards have their own
manufacturer ID but quite often when they are compatable with something
they use that as their logical ID.)

For example, there are a zillion Soundblaster PnP compatables with their own
unique vendor ID but with a CTL ID on the logical device that implements
the sb parts of the card.

We're not doing this because we enjoy pain and suffering, it's because
it'll be better and more robust in the long run.  Unfortunately, there was
no canonical list of logical ID's on the cards we used to recognize.

So I repeat for the list.. If you've got a card that used to work or does
work under BIOS backwards compat preconfig with 'controller pnp0' disabled,
please send us a dmesg and pnpinfo -v so we can add the ID's.  'controller
pnp0' is quite likely to become non-optional soon so we can use the
motherboard resource lists.

Cheers,
-Peter




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



Re: New PnP code does not work for me(?)

1999-09-26 Thread Donald J . Maddox

On Mon, Sep 27, 1999 at 05:05:37AM +0800, Peter Wemm wrote:
 
 The old PnP code was matching on the card vendor ID.  The new pnp code
 treats each logical device on it's own and matches by logical ID..
 (It's actually far more useful that way as most cards have their own
 manufacturer ID but quite often when they are compatable with something
 they use that as their logical ID.)

Ah, OK...  That makes a lot of sense.  Thanks for the clear, concise
explanation.

 
 For example, there are a zillion Soundblaster PnP compatables with their own
 unique vendor ID but with a CTL ID on the logical device that implements
 the sb parts of the card.
 
 We're not doing this because we enjoy pain and suffering, it's because
 it'll be better and more robust in the long run.  Unfortunately, there was
 no canonical list of logical ID's on the cards we used to recognize.
 
 So I repeat for the list.. If you've got a card that used to work or does
 work under BIOS backwards compat preconfig with 'controller pnp0' disabled,
 please send us a dmesg and pnpinfo -v so we can add the ID's.  'controller
 pnp0' is quite likely to become non-optional soon so we can use the
 motherboard resource lists.

Again, thanks for the very helpful and informative answers.  I would still
appreciate it if someone could give me a little bit more of a clue as to
what is necessary to add newPnP-awareness to the AWE driver, though.
(Surly and unhelpful responses from Mike Smith specifically NOT solicited)



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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Mike Smith

 On Sun, Sep 26, 1999 at 12:29:46PM -0700, Mike Smith wrote:
   
   But we do have a working driver for the AWE64.  Or rather, it worked fine
   before the new PnP code was comitted, now it doesn't.  It seems to me that
   this indicates a deficiency in the new PnP code.  Isn't that correct?
  
  No.
  
  I have already explained to you that the AWE64 driver that you were 
  using (one actually of _three_ that we have) only worked with PnP cards 
  as an accidental side-effect of the old PnP code.  Now that the PnP 
  code has been fixed, the brokenness of the old driver is exposed.
 
 Can you give me a few hints on what would be necessary to get the old
 driver to work with the new PnP?

As has already been explained to you (you _do_ read these messages in 
their entirety, right?), the old driver has been obsoleted.  You need 
to take the functionality that you want from the old driver and 
implement it in the newpcm code.

 It's amazing that one of the most popular sound cards of all time, one
 that works fine on practically every OS from DOS3.3 to Linux and BeOS,
 is of no concern to FBSD developers :-/

Since the AWE64 is already reported to work just fine with the current 
generation sound code, this sounds just a little hysterical to me.  You 
seem to have a slightly more specialised requirement that's not yet 
being catered to that does require some more attention.


-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



[dmaddox@conterra.com: Re: New PnP code does not work for me(?)]

1999-09-26 Thread Donald J . Maddox




On Sun, Sep 26, 1999 at 02:29:43PM -0700, Mike Smith wrote:
  Again, thanks for the very helpful and informative answers.  I would still
  appreciate it if someone could give me a little bit more of a clue as to
  what is necessary to add newPnP-awareness to the AWE driver, though.
  (Surly and unhelpful responses from Mike Smith specifically NOT solicited)
 
 You get what you have coming to you.  In the time it's taken you to 
 discover that I'm not interesting in holding your hand through the 
 entire process you could have worked it out for yourself.
 
 Consider which would have been the better investment.

I didn't enter this conversation looking for hand-holding from anybody.

I simply reported what seemed like broken functionality to me.  Thanks to
Peter, I now at least understand why the brokenness is unavoidable in this
case.  Thanks to you...  Well, I don't actually have anything to thank you
for, do I?





Re: New PnP code does not work for me(?)

1999-09-26 Thread Doug

Peter Wemm wrote:
 
 "Donald J . Maddox" wrote:
  Ok, will do.  Thanks.
 
  This may be a silly question, but...  The old PnP driver recognized
  a lot of devices, including my AWE64.  Isn't there a list of IDs it
  was aware of that should be merged into newPnP ASAP?
 
 The old PnP code was matching on the card vendor ID.  The new pnp code
 treats each logical device on it's own and matches by logical ID.

The new architecture sounds like a good thing, but isn't there a way to
fall back to the old method if the logical device ID isn't found?
Perhaps with an error message asking the user to report the logical ID
to [EMAIL PROTECTED]? Of course I'm probably dreaming
here, but it seems to me that some kind of compromise should be
possible, since I tend to agree with Donald that "Working before + not
working now = broken," no matter how much "better" the broken version is
from the purity standpoint. 

Doug
-- 
"Stop it, I'm gettin' misty." 

- Mel Gibson as Porter, "Payback"


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



Re: New PnP code does not work for me(?)

1999-09-26 Thread Mike Smith

  The old PnP code was matching on the card vendor ID.  The new pnp code
  treats each logical device on it's own and matches by logical ID.
 
   The new architecture sounds like a good thing, but isn't there a way to
 fall back to the old method if the logical device ID isn't found?
 Perhaps with an error message asking the user to report the logical ID

No.  The goal is to fix drivers, not conceal their shortcomings while 
requiring admins to apply unnecessary bandaids.

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



Re: New PnP code does not work for me(?)

1999-09-26 Thread Peter Wemm

Vladimir Kushnir wrote:
 Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
 perfectly all right as css device  friends  under old Pnp  VoxWare, but
 now outputs very poor sound through /dev/dsp and no sound at all when
 playing audio CD, and of course no midi):
 
 dmesg:
 pcm0: Yamaha SA2 at port
 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370
 -0x371 irq 5 drq 0,1 on isa0
 unknown0: OPL3-SA2 Sound Board at port 0x201 on isa0
 unknown1: OPL3-SA2 Sound Board at port 0x100-0x107 on isa0
 unknown2: OPL3-SA2 Sound Board at port 0x1e0-0x1e7,0x3e6 irq 11 on isa0
 
 pnpinfo -v (BTW, why the kernel message 
 mss_intr: irq, but not from mss
 when running pnpinfo?):
 Checking for Plug-n-Play devices...
 
 Card assigned CSN #1
 Vendor ID YMH0020 (0x2000a865), Serial Number 0x
 PnP Version 1.0, Vendor Version 0
 Device Description: OPL3-SA2 Sound Board
 
 Logical Device ID: YMH0021 0x2100a865 #0

I have one of these cards BTW.  My recollection was that it ran
beautifully..  I did have a more than my fair share of trouble with the
sample converters earlier on though..  newpcm will generate 8-bit and 16 bit
samples on the fly to best fit the sound hardware.  For example, if you have
an 8-bit card and play 16 bit samples, it'll down convert.  (there was a
nasty bug there though for a while. :-) )

I didn't have a cable to connect it to a CD though.

Poor sound usually isn't a pnp issue though, it's more likely a pcm driver
problem.

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]



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



Re: New PnP code does not work for me(?)

1999-09-26 Thread Vladimir Kushnir

Thanks for replay, but what I am to do? At least, where to start looking?
Card is revognized, so this indeed shouldn't be PnP fault.
Card's 16 bit, but so far the only acceptable sound give esd or mpg123.

On Mon, 27 Sep 1999, Peter Wemm wrote:

 Vladimir Kushnir wrote:
  Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
  perfectly all right as css device  friends  under old Pnp  VoxWare, but
  now outputs very poor sound through /dev/dsp and no sound at all when
  playing audio CD, and of course no midi):
snip
 
 I have one of these cards BTW.  My recollection was that it ran
 beautifully..  I did have a more than my fair share of trouble with the
 sample converters earlier on though..  newpcm will generate 8-bit and 16 bit
 samples on the fly to best fit the sound hardware.  For example, if you have
 an 8-bit card and play 16 bit samples, it'll down convert.  (there was a
 nasty bug there though for a while. :-) )
 
 I didn't have a cable to connect it to a CD though.
 
 Poor sound usually isn't a pnp issue though, it's more likely a pcm driver
 problem.
 
 Cheers,
 -Peter
 --
 Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
 
Regards,
Vladimir

===|===
 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: New PnP code does not work for me(?)

1999-09-26 Thread Peter Wemm

Vladimir Kushnir wrote:
 Thanks for replay, but what I am to do? At least, where to start looking?
 Card is revognized, so this indeed shouldn't be PnP fault.
 Card's 16 bit, but so far the only acceptable sound give esd or mpg123.

The person to talk to is Cameron Grant [EMAIL PROTECTED] for actual driver
problems.  Beware though, he's in the middle of a house move right at this
second.

It sounds like there's a problem with 8-16 bit sound conversion of mpg123
works but .au files don't.  I know Cameron's got a few tweaks/fixes in the
pipeline there somewhere.

 On Mon, 27 Sep 1999, Peter Wemm wrote:
 
  Vladimir Kushnir wrote:
   Hello, here's an output for my Yamaha OPL-SA2 card (it used to work
   perfectly all right as css device  friends  under old Pnp  VoxWare, but
   now outputs very poor sound through /dev/dsp and no sound at all when
   playing audio CD, and of course no midi):
 snip
  
  I have one of these cards BTW.  My recollection was that it ran
  beautifully..  I did have a more than my fair share of trouble with the
  sample converters earlier on though..  newpcm will generate 8-bit and 16 bi
t
  samples on the fly to best fit the sound hardware.  For example, if you hav
e
  an 8-bit card and play 16 bit samples, it'll down convert.  (there was a
  nasty bug there though for a while. :-) )
  
  I didn't have a cable to connect it to a CD though.
  
  Poor sound usually isn't a pnp issue though, it's more likely a pcm driver
  problem.
  
  Cheers,
  -Peter
  --
  Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
  
 Regards,
 Vladimir
 
 ===|===
  Vladimir Kushnir|
  [EMAIL PROTECTED], |Powered by FreeBSD
  [EMAIL PROTECTED]  |
 
 
 

Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]



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



Re: make world, attempt 5

1999-09-26 Thread Greg Lehey

On Sunday, 26 September 1999 at 21:01:17 +0200, Sheldon Hearn wrote:


 On Sun, 26 Sep 1999 09:00:50 +0930, Greg Lehey wrote:

 I've been trying for the last 24 hours solid to make a new world.  The
 latest problem is:

 :-(

 /src/PANIC/src/lib/libwrap/../../contrib/tcp_wrappers/hosts_access.c:245:
 syntax error before `'

 Hi Greg,

 I was the last person to touch that file, but I honestly can't see why
 you're having a problem with it.

 Are you sure that you have hosts_access.c rev 1.2 ?

I have now.  That's what comes of not reading my cvs logs.  I had a
different version of this file that I had been playing around with,
and your commit (of effectively the same thing) spammed it.

Sorry for the confusion.

Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key


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



Re: On hub.freebsd.org refusing to talk to dialups

1999-09-26 Thread Jonathan M. Bresler


stopping chat on the tech lists is an open research project ;)

jmb


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



New ATA, HPT366 and UDMA66

1999-09-26 Thread ktsin

Hi

I'm unable to get the new ATA driver to configure the HPT366 controller
to use busmastering DMA and to make the IBM 22GXP drive run at UDMA66.

Linux HPT366 driver supports busmastering DMA and UDMA66.

Does anybody know how to fix this?

Below is a portion of the output from dmesg:

ata-pci1: HighPoint HPT366 IDE controller irq 18 at device 19.0 on pci0
ata-pci1: Busmastering DMA not supported
   ^
ata2 at 0xd800 irq 18 on ata-pci1
ata-pci2: HighPoint HPT366 IDE controller irq 18 at device 19.1 on pci0
ata-pci2: Busmastering DMA not supported
   ^
atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
unknown0: CTRL on isa0
pcm0: CS4235 at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 7 drq 1,0 on isa0
unknown1: GAME at port 0x200-0x207 on isa0
unknown2: MPU at port 0x330-0x331 irq 10 on isa0
ad0: Maxtor 86448D6/NAVXAF20 ATA-3 disk at ata0 as master
ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue, UDMA33
Creating DISK ad0
Creating DISK wd0
ad1: IBM-DJNA-371350/J76OA30K ATA-4 disk at ata2 as master
ad1: 12949MB (26520480 sectors), 26310 cyls, 16 heads, 63 S/T, 512 B/S
ad1: 16 secs/int, 31 depth queue, PIO
  ^^^
Creating DISK ad1
Creating DISK wd1


Thanks,
kt


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



Re: Experimental ACPI driver.

1999-09-26 Thread Takanori Watanabe

In message [EMAIL PROTECTED], Mike Smith wrote:
Both Doug Rabson and myself have been tinkering with this, and there's 
someone that's been looking at an AML parser/interpreter in the last 
couple of weeks.  At this point in time, the parser and object manager 
are the most vital components.

Yes.I think so too.

Takanori Watanabe
a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html"
Public Key/a
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 


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



Re: New ATA, HPT366 and UDMA66

1999-09-26 Thread Foxfair Hu


On Mon, 27 Sep 1999 08:49:59 +0800 (SGT)
[EMAIL PROTECTED] wrote:

 Hi
 I'm unable to get the new ATA driver to configure the HPT366 controller
 to use busmastering DMA and to make the IBM 22GXP drive run at UDMA66.
 Linux HPT366 driver supports busmastering DMA and UDMA66.
 Does anybody know how to fix this?
 Below is a portion of the output from dmesg:
[]

  Check the commit message from -cvs :
=
sos 1999/09/24 05:36:11 PDT

  Modified files:
sys/dev/ata  ata-all.c ata-disk.c ata-disk.h 
 atapi-all.c atapi-all.h atapi-cd.c 
 atapi-cd.h 
  Log:
  Fix timeout handeling and add retry counts.
  Add HPT366 probe message (but no real support yet),
  Add CDR support for several diffenrent blocktypes, also close
  disk as a multisession CD.
  
  Revision  ChangesPath
  1.22  +5 -5  src/sys/dev/ata/ata-all.c
  1.27  +17 -1 src/sys/dev/ata/ata-disk.c
  1.12  +2 -1  src/sys/dev/ata/ata-disk.h
  1.16  +17 -2 src/sys/dev/ata/atapi-all.c
  1.11  +2 -1  src/sys/dev/ata/atapi-all.h
  1.18  +32 -27src/sys/dev/ata/atapi-cd.c
  1.7   +7 -7  src/sys/dev/ata/atapi-cd.h
===

  There is no UDMA66 support for HPT366 controller now in FreeBSD. Good
  news is it just works fine/rocky in UDMA33 and you can use it in this
  mode.

  I think the supporting code is under the progress now.
  
 Thanks,
 kt
 

Cheers,
-Foxfair.


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



Re: New PnP code does not work for me(?)

1999-09-26 Thread Darryl Okahata

Peter Wemm [EMAIL PROTECTED] wrote:

 We're not doing this because we enjoy pain and suffering, it's because
 it'll be better and more robust in the long run.  Unfortunately, there was
 no canonical list of logical ID's on the cards we used to recognize.
 
 So I repeat for the list.. If you've got a card that used to work or does
 work under BIOS backwards compat preconfig with 'controller pnp0' disabled,
 please send us a dmesg and pnpinfo -v so we can add the ID's.  'controller
 pnp0' is quite likely to become non-optional soon so we can use the
 motherboard resource lists.

 I want to publicly thank Peter Wemm for posting a reply that is
courteous, informative, and useful.  Recently, there has been too much
noise in this and other FreeBSD lists/groups where other people have
been abrupt to the point of rudeness.

--
Darryl Okahata
[EMAIL PROTECTED]

DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.



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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Chuck Robey

On Sun, 26 Sep 1999, Mike Smith wrote:

  This is only partially related, but I still can't even boot a kernel with
  the pnp0 controller enabled. It just hangs after probing the soundcard.
 
 You seem to have accidentally deleted all of the details related to 
 this bug report from your email before sending it.  Please try again.

Mike, I'm checking into this on my own, so this isn't a question, but you
might want to know that I have a Turtle Beach PCI audio card, setup with
controller pnp0 and device pcm0, and getting about the same responses.
Things have stopped working (the mixer totally).

This is just data if you wanted it.  I can see the answer isn't laying at
your fingertips, so I will continue to read code.

 


Chuck Robey| Interests include C programming, Electronics,
213 Lakeside Dr. Apt. T-1  | communications, and signal processing.
Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and
(301) 220-2114 |   jaunt.mat.net : FreeBSD-current(Alpha)




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



Re: Experimental ACPI driver.

1999-09-26 Thread Mitsuru IWASAKI

Hi, Mike.
# I'm very happy because of your reply :)

   We wrote experimental ACPI driver for 4.0-CURRENT.
  
  This was just one week work so its functionallity is very very poor :-)
  but I think it is good idea to start with this for developping ACPI
  driver for FreeBSD because it is enough small to understand it.
 
 I'm not sure this is the right way to go about it, although I haven't 
 looked at your code yet.  APCI is a big animal, and I think it's going 
 to take a proper design to get it right.

Indeed.  Also I think that this project cannot be achieved easily by
only one/two person's efforts.  I believe having this kind of prototype
makes our discussion easier.  We are going to prepare the materials
for our further discussion.

 The key components would appear to be a full AML parser, an object 
 manager to manage the ACPI namespace, and an AML interpreter to run the 
 AML methods.

Yes, Yes.

  If someone already started wriring ACPI devive driver, please let us
  know.  We'd like to merge them and would be happy in collaboration
  with you.
 
 Both Doug Rabson and myself have been tinkering with this, and there's 
 someone that's been looking at an AML parser/interpreter in the last 
 couple of weeks.  At this point in time, the parser and object manager 
 are the most vital components.

Now we got new friends :) Mr. Watanabe is going FreeBSDCon
(unfortunately I cannot), you can discuss this matter with him.
I think the time has come to start!

Thank you very much.


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



Re: Wierd su problem still there

1999-09-26 Thread Benjamin Lewis


[EMAIL PROTECTED] said:
 adams@nightfall(18:06:51)$ su
 Password:load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
 load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
 load: 0.37  cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k
 
 each "load" line is an enter press.

[snip]

 As soon as I get this the app becomes totaly useless, I can't control-z or
 control-c it, I have to kill the term.
 
 VNC (on the password prompt) and other random apps do this too, but you
 get the idea, I just rebuild/installed world from an cvsup from about 30
 minutes ago, this has been going on for over a week (I cvsup every day).
 
 Any ideas?

I too have encountered the same symptoms.  I have no idea why this started 
happening, but I have found a couple ways around it.  First, two Control-Ds 
will act as a Return if you find the status lines appearing.  Second, the
stty command will fix it totally.  I use `stty status ^T' to remap the status 
command to Control-T rather than Control-J (the ^T is a carat, T):

  akira:/home/bhlewis [123]su
  Password:load: 0.03  cmd: su 24921 [ttyin] 0.00u 0.00s 0% 624k
  [2 ^D's here]
  akira:/home/bhlewis [101]#exit
  exit
  akira:/home/bhlewis [124]stty
  speed 38400 baud;
  lflags: echoe echok echoke echoctl pendin
  iflags: -ixany ignpar
  oflags: -oxtabs
  cflags: cs8 -parenb -hupcl
  status
  ^J  
  akira:/home/bhlewis [125]stty status ^T
  akira:/home/bhlewis [126]stty
  speed 38400 baud;
  lflags: echoe echok echoke echoctl pendin
  iflags: -ixany ignpar
  oflags: -oxtabs
  cflags: cs8 -parenb -hupcl
  akira:/home/bhlewis [127]su
  Password:
  akira:/home/bhlewis [101]#

I hope this helps,

-Ben
-- 
Benjamin Lewis
[EMAIL PROTECTED] -or-   [EMAIL PROTECTED]




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



Re: Wierd su problem still there

1999-09-26 Thread Adam Strohl

 I too have encountered the same symptoms.  I have no idea why this started 
 happening, but I have found a couple ways around it.  First, two Control-Ds 
 will act as a Return if you find the status lines appearing.  Second, the
 stty command will fix it totally.  I use `stty status ^T' to remap the status 
 command to Control-T rather than Control-J (the ^T is a carat, T):

Damn, that works like a charm, but I wonder what is causing this to begin
with.

 I hope this helps,

Yeah, good work around thanks :)

- ( Adam Strohl ) -
-  UNIX Operations/Systems   http://www.digitalspark.net  -
-  adams (at) digitalspark.netxxx.xxx. x  -
- ( DigitalSpark.NET )--- -




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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Alok K. Dhir


Well said.

On Sun, 26 Sep 1999, Donald J . Maddox wrote:

 On a more personal note - What *is* your problem, anyway?  If you
 don't have anything useful to contribute to the conversation, why
 reply at all? Peter answered all my questions, and provided lots of
 useful information in a single missive.  I have yet to get anything
 from you except surly and wholely unhelpful responses.  Please - If
 you don't have any useful info, try to restrain yourself from the
 compulsion to reply.  Thank you in advance





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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Mike Smith

 On Sun, 26 Sep 1999, Mike Smith wrote:
 
   This is only partially related, but I still can't even boot a kernel with
   the pnp0 controller enabled. It just hangs after probing the soundcard.
  
  You seem to have accidentally deleted all of the details related to 
  this bug report from your email before sending it.  Please try again.
 
 Mike, I'm checking into this on my own, so this isn't a question, but you
 might want to know that I have a Turtle Beach PCI audio card, setup with
 controller pnp0 and device pcm0, and getting about the same responses.
 Things have stopped working (the mixer totally).

It sounds like your situation is completely different from Mr Culver's 
- his system is locked with interrupts masked during startup.

JFYI, the pnp device is only relevant to ISA - a PCI card is a PCI 
card, and is handled by the PCI bus code.

 This is just data if you wanted it.  I can see the answer isn't laying at
 your fingertips, so I will continue to read code.

You'll want to collect as much as you can and wait for Cameron to get 
back online.  One he's settled again we'll be trying to get as many
high-quality reports handed to him as possible, and anything that you 
can track down for yourself will greatly help.  (Heck, you may even 
find the problem yourself!)

-- 
\\  The mind's the standard   \\  Mike Smith
\\  of the man.   \\  [EMAIL PROTECTED]
\\-- Joseph Merrick   \\  [EMAIL PROTECTED]




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



Re: Loss of Functionality with newpnp

1999-09-26 Thread Oliver Fromme

Mike Smith wrote in list.freebsd-current:
   Can you give me a few hints on what would be necessary to get the old
   driver to work with the new PnP?
  
  As has already been explained to you (you _do_ read these messages in 
  their entirety, right?), the old driver has been obsoleted.  You need 
  to take the functionality that you want from the old driver and 
  implement it in the newpcm code.

I don't think that would be the right approach.  The
functionality of the awe0 driver should be kept separate and
not be integrated in the pcm0 driver.  (After all, the awe0
driver has nothing to do with PCM.)

  Since the AWE64 is already reported to work just fine with the current 
  generation sound code,

Uhm, it is?  I don't think so.  My AWE64 doesn't work either
with "newpnp", and I haven't seen a report from someone for
whom it works.  Except for the SB16-compatible PCM part of
the AWE64, of course, which does work (at least I can play
mp3 files).  But the actual AWE part does not work.  It did
with the old code.

  this sounds just a little hysterical to me.  You 
  seem to have a slightly more specialised requirement that's not yet 
  being catered to that does require some more attention.

Seems like I'm in the same situation as Donald.  The "slightly
more specialized requirement" is to get the AWE part of an
AWE64 to work, which I think is the whole point of having an
AWE64.  (If I just wanted PCM playback, I'd buy a cheaper
card.)

I'm aware that -- instead of whining around -- I should start
adapting the old awe0 driver to newpnp.  Indeed I would give
this a try if there was some documentation of the newpnp frame-
work, but I haven't found any, and I don't have the time to
find out on my own (this might seem lazy, but I do not regard
C source code as "documentation").

Anyway.  Downgrading that particular machine went fast and
easy, and now everything works fine again.

Regards
   Oliver

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

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


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



Re: EGCS, or EGCS?

1999-09-26 Thread Peter Jeremy

Peter Wemm [EMAIL PROTECTED] wrote:
Peter Jeremy wrote:
 I appear to have two complete copies of gcc - one in src/contrib/gcc
 and another in src/contrib/egcs/gcc.

src/contrib/gcc is where gcc used to live.  Then along came egcs with a
cygnus-style tree that ended up in src/contrib/egcs (v1.1.1 and later
1.1.2).  Now, egcs has become gcc 2.95, so it's going back to src/contrib/
gcc again.

That's the way I remembered things.  What threw me is that I currently
have two _different_ gcc directories, both claiming to be EGCS 1.1.2,
and both being updated.

  David O'Brien is working on this now but I think he's 
suffering from gcc-induced insanity. :-)

I guess that's one explanation...

Peter


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



No Subject

1999-09-26 Thread Tim Longbottom

unsubscribe


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



No Subject

1999-09-26 Thread Tim Longbottom

unsubscribe freebsd-current


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



Re: New ATA, HPT366 and UDMA66

1999-09-26 Thread Soren Schmidt

It seems Jason Young wrote:
 
 I looked at this yesterday (we just got one in). The HighPoint controller
 has some specific initialization needs, just like the Promise controller.
 
 The Linux code doesn't seem terribly twisted, although I didn't have
 enough caffiene handy to try and interpret the logic and add it into the
 new ATA driver. 
 
 I wonder if Soren (sorry, I don't know how to persuade my machine to spell
 your name correctly) would be interested in one so that he could work on
 supporting it? I would be happy to send one.. email me privately. 

I have the docs, and have been promised that an Abit HotRot controller be 
sent to me, but I havn't received it yet. So if you can get one out the
door asap that would be just fine (I really dont trust that other controller
to appear anytime soon...), just wrap it in neutral brown paper and
it should pass customs just fine :)

My snail mail addresss is:

Soren Schmidt
Soparken 61,  Klokkerholm
DK9320 Hjallerup
Denmark

-Soren (and yes today I'm on a 7bit line too :) )




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