new device drivers for RME soundcard and G400-TV

[Daniel Pouzzner]

I'm about to get cracking on a device driver for the RME Digi96/8 PAD.

The card's full set of I/O channels is: S/PDIF I/O (2 channels in, 2
out, 16-24 bits@32-96kHz), AES/EBU I/O (2ch in, 2 out, 16-24
bits@32-96kHz), analog I/O (2ch in, 2 out, 16-24 bits@32-96kHz), and
ADAT I/O (8 channels in, 8 out, 16-24 [EMAIL PROTECTED] or 48kHz).

The hardware supports on-board routing between these channels,
e.g. ADAT->S/PDIF or S/PDIF->ADAT.  I will be supporting these
features.  For those who are simply curious about features, see
http://www.rme-audio.com/english/digi96/digi96pa.htm


My starting point (what I have in hand) is (1) a complete and
functioning driver (supporting most key functionalities of the card)
for Linux and the ALSA ("Advanced Linux Sound Architecture")
subsystem, and (2) complete internal documentation on the card, from
the manufacturer.

Is FreeBSD's OSS-like audio subsystem powerful enough to provide
access to all the card's features (particularly, all its ports, word
sizes, and sample rates)?  ac97.c goes only to 20 bits/sample, for
example, but the card is 24 bits throughout.

I have to decide what strategy to pursue: do I write a new driver
based on an existing FreeBSD driver, using the Linux driver for hints,
or do I use a FreeBSD driver for hints, basing the new driver on the
Linux one (and thereby winding up with a GPL'd driver)?  Or indeed do
I write a driver truly from the ground up?  The only FreeBSD soundcard
driver I know of that includes analog and digital I/O support is the
SB Live! driver, which in my experience doesn't work particularly well
(in particular, capture didn't work at all when I tried it in April),
so my sense is that there exists no smoothly working FreeBSD driver
for a soundcard with anything remotely approaching the capabilities of
the RME products.

Finally, I have to decide whether I will port the ALSA library (in
whole or in part - appealing because it would facilitate support for
the dozens of other soundcards ALSA supports and FreeBSD doesn't),
write a glue layer so that a driver that supplies an ALSA-type
interface will work with the FreeBSD audio subsystem, simply create a
driver that supplies a FreeBSD-style audio interface, or finally,
create a driver that allows direct and specialized ioctl access to
unusual card features not accommodated by the FreeBSD audio subsystem,
but otherwise providing access via /dev/dsp et al.


This will be the first device driver I write.  Any advice, assistance,
caveats, etc., will certainly be much appreciated.  In particular, if
anyone has a guide to device driver implementation, draft or polished
form, complete or incomplete, it would surely be helpful to me.  I
understand some basic porting issues, e.g. bus_space_read_4 instead of
readl(), copyin() instead of copy_from_user(), etc.  The details will
come into focus with determination and repeated exposure.

I already have the card on the PCI bus, and am quite committed to BSD,
so I will see this project to its successful conclusion (unless
someone beats me to it (by all means, go ahead!:-)).


-Daniel Pouzzner


P.S. Also, if no one beats me to it, I will port G400-TV support for
the realtime MJPEG codec, the TV/radio tuner, and video I/O and audio
routing.  The Linux development effort
(http://marvel.sourceforge.net/) is just coming together and I won't
be embarking on the project until they've got things basically working
smoothly and I've got the RME card basically working smoothly.  I do
already have a G400-TV on my machine, currently not using the -TV part
of course.


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

Re: [net] bpf question

[Jan Koum]

i think the buffer is 32K (from BPF_MAXBUFSIZE in bpf.h) and you should be
able to bump it up a bit on your box if you wish. it might help. also,
maybe we should consider upping the default buffer size in our tree?

On Mon, May 22, 2000 at 04:16:56PM -0700, Christopher Nielsen <[EMAIL PROTECTED]> 
wrote:
> On Mon, 22 May 2000, Graham Wheeler wrote:
> 
> > If my memory serves me correctly, Marcus Ranum wrote a white paper on
> > IDS systems in the early days of NFR, in which he said that the existing
> > configuration of BPF was inadequate for capturing all packets on a fast
> > link, and suggested a patch to improve the situation. THe patch involved
> > bumping up a buffer from about 16kb to 256kb. Unfortunately I no longer
> > have the details handy, but if you did a search for BPF/IDS/NFR/Ranum
> > you might find something.
> 
> http://www.nfr.net/forum/publications/LISA-97.htm
> 
> -- 
> Christopher Nielsen
> (enkhyl|cnielsen)@pobox.com
> Enkhyl on IRC
> Space monekys ate my brain: No such file or directory
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-net" in the body of the message


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

Patch to get Cron to do UTC cron jobs

[Daniel O'Connor]

Hi,
Early January this year Bjorn Danielsson
<[EMAIL PROTECTED]> posted a patch for cron which allowed
it to have UTC cronjobs.

The message is at ->
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=28667+30785+/usr/local/www/db/text/2
000/freebsd-hackers/2116.freebsd-hackers

The patch is at ->
http://urquell.pilsnet.sunet.se:8000/cron-utc-patch.txt

Any chance of having this committed? IMHO it is very useful to have.

---
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-hackers" in the body of the message

Teaching sysinstall about the documentation packages

[Nik Clayton]

[ -doc, -hackers, and jkh.pl on the To: line.  Watch those replies :-) ]

For those that haven't been keeping up at the back, Doc. Project package
generation is now pretty stable.  What this means is that if you take 
yourself off to

ftp.FreeBSD.org:/pub/FreeBSD/doc/packages/

and take a look in there, you'll see one package for each document, format,
and language combination we currently support, all ripe for putting through
pkg_add(1).  Modulo some final testing, automatic generation of these is
pretty much sorted.

So, the time has come to think about ripping out the doc distro from 
"make release", and to teach sysinstall about these packages instead.
Much as I relish the chance to do this, I'm already up to >here< with 
other doc. proj. pointy-hair work and all the fun things that entails,
so I'm not going to get the chance to do this any time soon.

Any volunteers?

N
-- 
Internet connection, $19.95 a month.  Computer, $799.95.  Modem, $149.95.
Telephone line, $24.95 a month.  Software, free.  USENET transmission,
hundreds if not thousands of dollars.  Thinking before posting, priceless.
Somethings in life you can't buy.  For everything else, there's MasterCard.
  -- Graham Reed, in the Scary Devil Monastery


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

Re: [net] bpf question

[Christopher Nielsen]

On Mon, 22 May 2000, Graham Wheeler wrote:

> If my memory serves me correctly, Marcus Ranum wrote a white paper on
> IDS systems in the early days of NFR, in which he said that the existing
> configuration of BPF was inadequate for capturing all packets on a fast
> link, and suggested a patch to improve the situation. THe patch involved
> bumping up a buffer from about 16kb to 256kb. Unfortunately I no longer
> have the details handy, but if you did a search for BPF/IDS/NFR/Ranum
> you might find something.

http://www.nfr.net/forum/publications/LISA-97.htm

-- 
Christopher Nielsen
(enkhyl|cnielsen)@pobox.com
Enkhyl on IRC
Space monekys ate my brain: No such file or directory



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

Re: please hellllllllllllp me!

[Peter van Dijk]

On Mon, May 22, 2000 at 03:33:50PM -0700, Alfred Perlstein wrote:
> > 
> > dscheidt@shell-2 ~ 536$ ls -al | grep .snapshot
> > dscheidt@shell-2 ~ 537$ ls -al .snapshot
> > total 60
> > drwxrwxrwx   2 root  wheel   4096 May 22 15:01 .
> > drwxr-xr-x  15 dscheidt  dialin  8192 May 22 15:51 ..
> > drwxr-xr-x  15 dscheidt  dialin  8192 May 22 14:58 hourly.0
> > drwxr-xr-x  15 dscheidt  dialin  8192 May 22 13:52 hourly.1
> > drwxr-xr-x  15 dscheidt  dialin  8192 May 22 13:00 hourly.2
> > drwxr-xr-x  15 dscheidt  dialin  8192 May 22 10:52 hourly.3
> > drwxr-xr-x  15 dscheidt  dialin  8192 May 19 16:34 nightly.0
> > drwxr-xr-x  15 dscheidt  dialin  8192 May 19 16:34 nightly.1
> > dscheidt@shell-2 ~ 538$ 
> > 
> > doesn't count then?  This is a directory NFS-mounted from a NetApp.  The
> > .snapshot directory is a lifesaver, and support cost cutter.
> 
> If the netapp doesn't honor readdir requests properly then it's
> breaking unix semantics.
> 
> Netapp is broken, there's no reason to intentionally hide this
> directory from readdir.

bash$ ls -al /home/staff
total 53
drwxr-xr-x  13 root  vwstaff  4096 May 16 13:46 .
drwxr-xr-x   4 root  wheel 512 Mar 28 17:44 ..
drwxrwxrwx  10 root  wheel4096 May 23 00:00 .snapshot

Ours apparently isn't, and I have seen .snapshot dirs from shellboxes on
lots of other NetApps too.

I can't find the relevant config-option right now, if there is one.

Greetz, Peter.
-- 
[EMAIL PROTECTED] - Peter van Dijk [student:developer:madly in love]


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

Re: NFS server problems on 3.4-S, any interest?

[Doug Barton]

On Mon, 22 May 2000 [EMAIL PROTECTED] wrote:

> > Yeah, I miss the blinky lights. I went to the x-over cable because
> > the hub I bought originally was giving me non-stop collisions under
> > load.
> 
> It should be noted that a lot of collisions is *expected* under load.

Yes, I'm not quite _that_ much of a neophyte. :) When I first set
those machines up the hub was fine, since I wasn't pushing a lot of
traffic through it. As soon as I started to experiment with the nfs,
samba, etc. it was clear that the hub wasn't cutting it anymore, and free
(I made the x-over cable from parts I had at hand) was better than $100+
for a switch. I'm going to be adding another machine to that network
though, so it's switch time now either way. 

Thanks for the input (and to the others who've mailed me as well),

Doug
-- 
"Live free or die"
- State motto of my ancestral homeland, New Hampshire

Do YOU Yahoo!?




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

Re: please hellllllllllllp me!

[Alfred Perlstein]

* David Scheidt <[EMAIL PROTECTED]> [000522 14:30] wrote:
> On Mon, 22 May 2000, Alfred Perlstein wrote:
> 
> > * Shadi Fazelian <[EMAIL PROTECTED]> [000522 02:31] wrote:
> > > Hello.
> > > please guide me:
> > > 1- how I can see a hidden file (not dot file) and how
> > > I can hidden a file ?
> > >  my mean: I want make a file that ls -al can't see it.
> > 
> > impossible(*) afaik.
> 
> dscheidt@shell-2 ~ 536$ ls -al | grep .snapshot
> dscheidt@shell-2 ~ 537$ ls -al .snapshot
> total 60
> drwxrwxrwx   2 root  wheel   4096 May 22 15:01 .
> drwxr-xr-x  15 dscheidt  dialin  8192 May 22 15:51 ..
> drwxr-xr-x  15 dscheidt  dialin  8192 May 22 14:58 hourly.0
> drwxr-xr-x  15 dscheidt  dialin  8192 May 22 13:52 hourly.1
> drwxr-xr-x  15 dscheidt  dialin  8192 May 22 13:00 hourly.2
> drwxr-xr-x  15 dscheidt  dialin  8192 May 22 10:52 hourly.3
> drwxr-xr-x  15 dscheidt  dialin  8192 May 19 16:34 nightly.0
> drwxr-xr-x  15 dscheidt  dialin  8192 May 19 16:34 nightly.1
> dscheidt@shell-2 ~ 538$ 
> 
> doesn't count then?  This is a directory NFS-mounted from a NetApp.  The
> .snapshot directory is a lifesaver, and support cost cutter.

If the netapp doesn't honor readdir requests properly then it's
breaking unix semantics.

Netapp is broken, there's no reason to intentionally hide this
directory from readdir.

-Alfred


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

Re: NFS server problems on 3.4-S, any interest?

[Kent Stewart]

Doug Barton wrote:
> 
> On Mon, 22 May 2000, Matthew Dillon wrote:
> 
> > :>From the workstation:
> > :Name  Mtu   Network   Ipkts  IerrsOpktsOerrs Coll  Drop
> > :fxp0  150032102492 0  31653667   0   30900   0
> > :
> > :>From the fileserver:
> > :Name  Mtu   Network   Ipkts  IerrsOpktsOerrs Coll   Drop
> > :xl0   1500  3250417328967   32900227   00   0
> > :
> > : I did find it a little unusual that I was getting collisions on a
> > :crossover cable, but when I looked at the mail archives related to that
> > :problem I read that the intel cards are very aggressive packet pushers,
> > :and that this isn't all that unusual. The ratio of good packets to
> > :collisions seemed healthy enough to not warrant too much concern.
> >
> > 28967 input errors on xl0?  Problem!
> 
> heh... ok, I can take a hint.
> 
> > But the real problem is that you are attempting to do 10BaseT
> > full-duplex.  Full-duplex operation with 10BaseT is problematic
> > at best.  Full duplex has good interoperability at 100BaseTX speeds,
> > but not at 10BaseT speeds.
> 
> Ok, I learned something new. :) I've had "get another fxp0 and a
> real switch" for the home network on my list for a while now, I guess it's
> time to move that up a little.
> 
> > Crossover cables work fine, usually, but I personally *never* use them.
> > I always throw a switch in between the machines and let it negotiate
> > the duplex mode with each machine independantly, plus it gives me nice
> > shiny LEDs that tell me what the switch thinks the port is doing as
> > a sanity check.
> 
> Yeah, I miss the blinky lights. I went to the x-over cable because
> the hub I bought originally was giving me non-stop collisions under
> load. It worked really well for about 5 months, then the last couple
> months it's given me problems. I'm still learning the whole networking
> thing, so I appreciate the insight.

I had an fxp0 that the mounting bracket was a little long and the
pressure of screwing it down messed things up. I would get 10MB/s out
but only 10KB/s into that system. It was dropping 300-700 bytes in
some packets. I found out last night that I could remove the screw and
it worked just fine. An old 3C905-TX didn't have the problem either
but I only got 8-9MB/s. A spare fxp0 also didn't have the problem and
it was 11MB/s both directions.

Kent

> 
> Doug
> --
> "Live free or die"
> - State motto of my ancestral homeland, New Hampshire
> 
> Do YOU Yahoo!?
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Kent Stewart
Richland, WA

mailto:[EMAIL PROTECTED]
http://www.3-cities.com/~kstewart/index.html
FreeBSD News http://daily.daemonnews.org/

SETI(Search for Extraterrestrial Intelligence) @ HOME
http://setiathome.ssl.berkeley.edu/

Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR
http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html


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

Re: de-GNUfication of Digiboard driver ?

[Brian Somers]

More work needs to be done here...  The dgb and dgm drivers are 
almost the same, and the dgb driver doesn't probe my digiboard at the 
moment (I don't know if this is due to broken hardware or a broken 
driver).  The driver doesn't conform to style(9) and needs to be 
newbusified.

I've been intending to work on this driver for over a year now :-/

If you're not interested in the other issues, BSDifying it would be 
an excellent start though :-)  Send me the patches and I'll commit.

Cheers.

> Hi,
> 
> I've been reading recently some stories about the licensing
> issues and that brought me to an interesting conclusion:
> 
> apparently, we are able to change the license of the Digiboard
> driver from GPL to BSD ? It does not seem to be that much important
> any more as these cards are obsolete, but still.
> 
> I was the original author of that driver. To get the information
> about the Digi interface I've read the Linux driver. I supposed
> that it made me mentally contaminated with GPL. But all the FreeBSD
> driver was written from scratch, with none of the Linux code
> re-used (except for the array with the image of firmware but
> apparently that one was available as well from non-GPL-contaminated
> sources, such as Digi's drivers for other Unixes). 
> 
> But now looking at the BSD-USL case it seems like I was wrong about
> the mental contamination. Apparently none of the author of the later
> changes to this driver were enthusiastic about GPL as well.
> 
> So if I'm getting the things right, can we just go ahead now and
> change its license to BSD ? Or am I wrong ?
> 
> -SB

-- 
Brian <[EMAIL PROTECTED]>
     
Don't _EVER_ lose your sense of humour !




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

Re: NFS server problems on 3.4-S, any interest?

[sthaug]

>   Yeah, I miss the blinky lights. I went to the x-over cable because
> the hub I bought originally was giving me non-stop collisions under
> load.

It should be noted that a lot of collisions is *expected* under load.
If you saturate a half-duplex segment (using for instance ttcp), the
sender would expect to see about 50% collisions (every other full size
TCP packet from the sender will collide with an ACK from the receiver),
and the receiver would expect to see 100% collisions.

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]


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

Re: please hellllllllllllp me!

[David Scheidt]

On Mon, 22 May 2000, Alfred Perlstein wrote:

> * Shadi Fazelian <[EMAIL PROTECTED]> [000522 02:31] wrote:
> > Hello.
> > please guide me:
> > 1- how I can see a hidden file (not dot file) and how
> > I can hidden a file ?
> >  my mean: I want make a file that ls -al can't see it.
> 
> impossible(*) afaik.

dscheidt@shell-2 ~ 536$ ls -al | grep .snapshot
dscheidt@shell-2 ~ 537$ ls -al .snapshot
total 60
drwxrwxrwx   2 root  wheel   4096 May 22 15:01 .
drwxr-xr-x  15 dscheidt  dialin  8192 May 22 15:51 ..
drwxr-xr-x  15 dscheidt  dialin  8192 May 22 14:58 hourly.0
drwxr-xr-x  15 dscheidt  dialin  8192 May 22 13:52 hourly.1
drwxr-xr-x  15 dscheidt  dialin  8192 May 22 13:00 hourly.2
drwxr-xr-x  15 dscheidt  dialin  8192 May 22 10:52 hourly.3
drwxr-xr-x  15 dscheidt  dialin  8192 May 19 16:34 nightly.0
drwxr-xr-x  15 dscheidt  dialin  8192 May 19 16:34 nightly.1
dscheidt@shell-2 ~ 538$ 

doesn't count then?  This is a directory NFS-mounted from a NetApp.  The
.snapshot directory is a lifesaver, and support cost cutter.

David Scheidt



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

Re: NFS server problems on 3.4-S, any interest?

[Doug Barton]

On Mon, 22 May 2000, Matthew Dillon wrote:

> :>From the workstation:
> :Name  Mtu   Network   Ipkts  IerrsOpktsOerrs Coll  Drop
> :fxp0  150032102492 0  31653667   0   30900   0
> :
> :>From the fileserver:
> :Name  Mtu   Network   Ipkts  IerrsOpktsOerrs Coll   Drop
> :xl0   1500  3250417328967   32900227   00   0
> :
> : I did find it a little unusual that I was getting collisions on a
> :crossover cable, but when I looked at the mail archives related to that
> :problem I read that the intel cards are very aggressive packet pushers,
> :and that this isn't all that unusual. The ratio of good packets to
> :collisions seemed healthy enough to not warrant too much concern. 
> 
> 28967 input errors on xl0?  Problem!

heh... ok, I can take a hint. 
 
> But the real problem is that you are attempting to do 10BaseT 
> full-duplex.  Full-duplex operation with 10BaseT is problematic
> at best.  Full duplex has good interoperability at 100BaseTX speeds,
> but not at 10BaseT speeds.

Ok, I learned something new. :) I've had "get another fxp0 and a
real switch" for the home network on my list for a while now, I guess it's
time to move that up a little. 

> Crossover cables work fine, usually, but I personally *never* use them.
> I always throw a switch in between the machines and let it negotiate
> the duplex mode with each machine independantly, plus it gives me nice
> shiny LEDs that tell me what the switch thinks the port is doing as
> a sanity check.

Yeah, I miss the blinky lights. I went to the x-over cable because
the hub I bought originally was giving me non-stop collisions under
load. It worked really well for about 5 months, then the last couple
months it's given me problems. I'm still learning the whole networking
thing, so I appreciate the insight. 

Doug
-- 
"Live free or die"
- State motto of my ancestral homeland, New Hampshire

Do YOU Yahoo!?




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

Re: SMP kernel compilation??

[Warner Losh]

In message <[EMAIL PROTECTED]> Joy Ganguly writes:
: i tried to compile a SMP kernel . but when it tries to load the kernel
: it gives me " undefined symbol" messages. the messages are:-

Make depend?

Warner


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

Re: eBones really dead?

[Kris Kennaway]

On Mon, 22 May 2000, Doug Barton wrote:

>   I read this weekend that eBones is dead, but I still see it in my src
> tree on -Current, so I'm curious as to what the status really is. 

All of the files are in the attic in my repo. Are you sure this isn't just
a leftover from a machine which was updated from 2.2.(<6)?

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>



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

Re: NFS server problems on 3.4-S, any interest?

[Matthew Dillon]

:>From the workstation:
:Name  Mtu   Network   Ipkts  IerrsOpktsOerrs Coll  Drop
:fxp0  150032102492 0  31653667   0   30900   0
:
:>From the fileserver:
:Name  Mtu   Network   Ipkts  IerrsOpktsOerrs Coll   Drop
:xl0   1500  3250417328967   32900227   00   0
:
:   I did find it a little unusual that I was getting collisions on a
:crossover cable, but when I looked at the mail archives related to that
:problem I read that the intel cards are very aggressive packet pushers,
:and that this isn't all that unusual. The ratio of good packets to
:collisions seemed healthy enough to not warrant too much concern. 

28967 input errors on xl0?  Problem!

But the real problem is that you are attempting to do 10BaseT 
full-duplex.  Full-duplex operation with 10BaseT is problematic
at best.  Full duplex has good interoperability at 100BaseTX speeds,
but not at 10BaseT speeds.

Crossover cables work fine, usually, but I personally *never* use them.
I always throw a switch in between the machines and let it negotiate
the duplex mode with each machine independantly, plus it gives me nice
shiny LEDs that tell me what the switch thinks the port is doing as
a sanity check.

:always worked before. I ran 'ping -f' simultaneously on both hosts, and
:did experience a 4% packet loss on one host, and 1% on the other. Changing
:to an explicit:
:
:ifconfig fxp0 inet 10.0.0.2 netmask 255.255.255.0 media 10baseT/UTP
:mediaopt full-duplex
:
:gets me 0 packet loss on both sides. So you may be right Matt, it may be a
:network error after all. I'll give it another test run and see what I can
:see. 
:...
:Thanks,
:
:Doug

Given what you've described, I'm dead certain it is (or was :-)).

p.s. Throw away your 10BaseT switches and hubs and go get 100BaseTX 
switches, they're getting real cheap and modern machines can push the
bandwidth just fine (even the crappy cards).  Don't buy HUBs (10 or 100),
switches are a whole lot faster and a whole lot easier to troubleshoot.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>



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

Re: NFS server problems on 3.4-S, any interest?

[Doug Barton]

On Mon, 22 May 2000, Matthew Dillon wrote:

> : I have two machines at home, one running 3.4-Stable which is my
> :firewall/natd/file server machine. The other is running 5.0-Current
> :(around 5/8 right now) which mounts a whole bunch of stuff via amd from
> :the 3.4 machine. Up until say... 2 months ago, this worked really well.
> :I never had any nfs performance problems. One of the things I mount for
> :example is /usr/src, and my make world time didn't suffer much, if at
> :all. 
> :
> : However, at some point about 2 months ago (I wish I had a more definite
> :time period, but the problem has kind of snuck up on me) I have been
> :getting increasingly bad performance from the nfs mount. I get "nfs
> :...
> :Doug
> 
> First, make sure the 5.x machine is up to date.

I'm going to upgrade it today, I'm checking out a new source tree
local to the workstation machine. 

> Second, start looking for network problems, because if you are getting
> 'host not responding' errors it's probably due to packet loss somewhere.
> NFS is particularly sensitive to packet loss.  This doesn't sound like
> an NFS problem on the face of it.

The errors are of the sort:

workstation /kernel: nfs server fileserver:/usr/ncvs: not responding

It's possible that it's a network problem I suppose, although I'm
using a crossover cable from an fxp0 in the workstation to an xl0 in the
fileserver. Both are running at 10Mb, full duplex. Netstat -id shows:

>From the workstation:
Name  Mtu   Network   Ipkts  IerrsOpktsOerrs Coll  Drop
fxp0  150032102492 0  31653667   0   30900   0

>From the fileserver:
Name  Mtu   Network   Ipkts  IerrsOpktsOerrs Coll   Drop
xl0   1500  3250417328967   32900227   00   0

I did find it a little unusual that I was getting collisions on a
crossover cable, but when I looked at the mail archives related to that
problem I read that the intel cards are very aggressive packet pushers,
and that this isn't all that unusual. The ratio of good packets to
collisions seemed healthy enough to not warrant too much concern. 

Hrrrmm... I just took a look at the settings for each card. I did
not specify full duplex in the fxp0 ifconfig line, since autoselect has
always worked before. I ran 'ping -f' simultaneously on both hosts, and
did experience a 4% packet loss on one host, and 1% on the other. Changing
to an explicit:

ifconfig fxp0 inet 10.0.0.2 netmask 255.255.255.0 media 10baseT/UTP
mediaopt full-duplex

gets me 0 packet loss on both sides. So you may be right Matt, it may be a
network error after all. I'll give it another test run and see what I can
see. 

In case it's significant, the fileserver has been up for 11 days
(last make world) and the workstation has been up for two. 

Thanks,

Doug
-- 
"Live free or die"
- State motto of my ancestral homeland, New Hampshire

Do YOU Yahoo!?





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

Re: SMP and APIC???

[Joy Ganguly]

[EMAIL PROTECTED] wrote:

> > i have compiled freeBSD 3.4 SMP. but when i try to boot it the kernel
> > shows "Testing APIC 8254" and then it hangs. earlier i had run mptable
> > and it showed:I/O APICs:
> > --
> > {Lots of stuff}
> >
> >  APIC ID Version State   Address
> >  2   0x20usable  0xfec0
> >  3   0x20usable  0xfd8df000
>
> You seem to have two IO APICs. You need
>
> optionsNAPIC=2 # number of IO APICs
>
> in the kernel config, *and* the following patch to sys/i386/i386/pmap.c
> (this patch is in 3.4-STABLE, but not in 3.4-RELEASE).

thanx  it is working now. though frankly i am still clueless about how it is
working. are there any docs about SMP on freebsd??

joy




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

Re: Supermicro PIIIDM3 Problems...

[Mike Smith]

> On the PIIIDM3 that I was working with I had both ECC and PC100 SDRAM. I
> forget what I had and when. I did though at one point have ECC unbuffered
> memory, and had ECC enabled. I will have some more of these boards later
> these week and will retest them, making note of what I have in there. I'll
> try ecc and pc100 individual and play with the settings, to see if I can
> find exactly what configuration is giving the problem.

If you're using 133MHz FSB CPUs, start there; see my reply to Ken.
-- 
\\ 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-hackers" in the body of the message

Re: please hellllllllllllp me!

[Alfred Perlstein]

* Aleksandr A.Babaylov <[EMAIL PROTECTED]> [000522 08:30] wrote:
> Alfred Perlstein writes:
> > > 2- how I can write somthing in a file that nobody can
> > > see them
> > > my mean: in crontab adding some command that this is
> > > hidden.
> > impossible(*) afaik.
> possible if use similar to linux emulator method
> to redirect open(2) - but it is TOO expansive
> and kernel need to be changed IMHO for this

Why not just trojan cron or any other deamon to periodically execute
some program?

After a compromise it's best to just reinstall and audit the rest of
your machines.

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."


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

Re: SMP and APIC???

[sthaug]

> i have compiled freeBSD 3.4 SMP. but when i try to boot it the kernel
> shows "Testing APIC 8254" and then it hangs. earlier i had run mptable
> and it showed:I/O APICs:
> --
> {Lots of stuff}
> 
>  APIC ID Version State   Address
>  2   0x20usable  0xfec0
>  3   0x20usable  0xfd8df000

You seem to have two IO APICs. You need 

optionsNAPIC=2 # number of IO APICs

in the kernel config, *and* the following patch to sys/i386/i386/pmap.c
(this patch is in 3.4-STABLE, but not in 3.4-RELEASE).

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
--
*** pmap.c.orig Sat Apr  1 23:58:17 2000
--- pmap.c  Tue Apr 25 23:59:29 2000
***
*** 434,441 
for (j = 0; j < 16; j++) {
/* same page frame as a previous IO apic? */
if (((vm_offset_t)SMP_prvpt[j + 16] & PG_FRAME) ==
!   (io_apic_address[0] & PG_FRAME)) {
!   ioapic[i] = (ioapic_t *)&SMP_ioapic[j * PAGE_SIZE];
break;
}
/* use this slot if available */
--- 434,442 
for (j = 0; j < 16; j++) {
/* same page frame as a previous IO apic? */
if (((vm_offset_t)SMP_prvpt[j + 16] & PG_FRAME) ==
!   (io_apic_address[i] & PG_FRAME)) {
!   ioapic[i] = (ioapic_t *)&SMP_ioapic[j * PAGE_SIZE
! + (io_apic_address[i] & PAGE_MASK)];
break;
}
/* use this slot if available */


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

Re: SMP and APIC???

[Mike Smith]

This sounds like a known problem with 3.4 and the timer interrupt routing 
code.  You will need to update to 4.0 to work around it.

> i have compiled freeBSD 3.4 SMP. but when i try to boot it the kernel
> shows "Testing APIC 8254" and then it hangs. earlier i had run mptable
> and it showed:I/O APICs:
> --
> {Lots of stuff}
> 
>  APIC ID Version State   Address
>  2   0x20usable  0xfec0
>  3   0x20usable  0xfd8df000
> 
> 
> and then..
> 
> options SMP # Symmetric MultiProcessor
> Kernel
> options APIC_IO # Symmetric (APIC) I/O
> 
> # Optional (built-in defaults will work in most cases):
> #optionsNCPU=2  # number of CPUs
> #optionsNBUS=6  # number of busses
> #optionsNAPIC=2 # number of IO APICs
> #optionsNINTR=24# number of INTs
> 
> i am totally clueless. whats going on???
> 
> thanx in advance
> 
> joy
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
> 

-- 
\\ 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-hackers" in the body of the message

Re: Supermicro PIIIDM3 Problems...

[Essenz Consulting]

On the PIIIDM3 that I was working with I had both ECC and PC100 SDRAM. I
forget what I had and when. I did though at one point have ECC unbuffered
memory, and had ECC enabled. I will have some more of these boards later
these week and will retest them, making note of what I have in there. I'll
try ecc and pc100 individual and play with the settings, to see if I can
find exactly what configuration is giving the problem.

-john v. e.

On Mon, 22 May 2000, Kenneth D. Merry wrote:

> On Mon, May 22, 2000 at 11:33:52 -0700, Mike Smith wrote:
> > 
> > Can you be more specific about "panicing"?  As far as details go, you're 
> > not helping yourself.
> > 
> > > I was doing a FreeBSD 4.0 Install on a fairly new Supermicro PIIIDM3
> > > motherboard. I eventually got FreeBSD 4.0 installed, however, during the
> > > install, it kept hanging up and panicing. After trying to do a bin only
> > > install, it took about 7 trys until it didnt hang up and panic. When I did
> > > get it installed, everything worked, and it booted. But if I go into
> > > sysinstall and try to do a post install addition of, lets say src/sys,
> > > same thing happens. It freezes up and hangs part way throw, and eventually
> > > will throw up a panic error.
> > > 
> > > Any ideas about the stability of the aix78xx driver for this motherboard
> > > and it's aic-7892 chip?
> > 
> > I use one of these boards on a daily basis; it's been very stable under 
> > both -stable and -current, although I don't use the SCSI interface very 
> > often anymore.
> 
> Well, one question is whether or not you have ECC memory in the machine,
> and if so, if you have parity checking or ECC turned on.
> 
> Mike's board doesn't have ECC memory, and I've been trying to find someone
> with a SuperMicro 840 board with ECC turned on.  (To see whether their
> boards have the problem with the MRH-S chip.)
> 
> As far as the 7892 chip, the driver should be pretty stable, I don't think
> other folks have had trouble with it.
> 
> Ken
> -- 
> Kenneth Merry
> [EMAIL PROTECTED]
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
> 



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

Re: IP tunnel

[Mike Nowlin]

> Can anyone tell me the difference between nos-tun(8) and gif(4) (Other
> than IPv6)?  I want to create a tunnel between 2 networks (IPv4), 2
> FreeBSD boxes... will one of these work or is this a different type
> of tunnel.  I am familiar with Cisco tunnelling, I am assuming a similar
> concept.  Anyone doing this already, if so sample configs?  Is it
> possible?

I'm using nos-tun(8) between Cisco 2610/1720 routers and FBSD machines to
make various subnets show up where they shouldn't...  I have a /24 at one
office and a /25 at another one -- wanted to have a /29 from each of these
appear at my house.  

Works quite well...

mike




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

Re: Supermicro PIIIDM3 Problems...

[Mike Smith]

> Well, one question is whether or not you have ECC memory in the machine,
> and if so, if you have parity checking or ECC turned on.
> 
> Mike's board doesn't have ECC memory, and I've been trying to find someone
> with a SuperMicro 840 board with ECC turned on.  (To see whether their
> boards have the problem with the MRH-S chip.)

Sorry, I thought I followed up on this.

I was lent a couple of 133MHz FSB CPUs and some PC100 ECC memory by ASA 
Computers; the 133MHz CPUs don't like this board, but the ECC memory 
worked fine with the 100MHz FSB CPUs I've been using.

-- 
\\ 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-hackers" in the body of the message

Re: Supermicro PIIIDM3 Problems...

[Kenneth D. Merry]

On Mon, May 22, 2000 at 11:33:52 -0700, Mike Smith wrote:
> 
> Can you be more specific about "panicing"?  As far as details go, you're 
> not helping yourself.
> 
> > I was doing a FreeBSD 4.0 Install on a fairly new Supermicro PIIIDM3
> > motherboard. I eventually got FreeBSD 4.0 installed, however, during the
> > install, it kept hanging up and panicing. After trying to do a bin only
> > install, it took about 7 trys until it didnt hang up and panic. When I did
> > get it installed, everything worked, and it booted. But if I go into
> > sysinstall and try to do a post install addition of, lets say src/sys,
> > same thing happens. It freezes up and hangs part way throw, and eventually
> > will throw up a panic error.
> > 
> > Any ideas about the stability of the aix78xx driver for this motherboard
> > and it's aic-7892 chip?
> 
> I use one of these boards on a daily basis; it's been very stable under 
> both -stable and -current, although I don't use the SCSI interface very 
> often anymore.

Well, one question is whether or not you have ECC memory in the machine,
and if so, if you have parity checking or ECC turned on.

Mike's board doesn't have ECC memory, and I've been trying to find someone
with a SuperMicro 840 board with ECC turned on.  (To see whether their
boards have the problem with the MRH-S chip.)

As far as the 7892 chip, the driver should be pretty stable, I don't think
other folks have had trouble with it.

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]


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

SMP and APIC???

[Joy Ganguly]

hi

i have compiled freeBSD 3.4 SMP. but when i try to boot it the kernel
shows "Testing APIC 8254" and then it hangs. earlier i had run mptable
and it showed:I/O APICs:
--
{Lots of stuff}

 APIC ID Version State   Address
 2   0x20usable  0xfec0
 3   0x20usable  0xfd8df000


and then..

options SMP # Symmetric MultiProcessor
Kernel
options APIC_IO # Symmetric (APIC) I/O

# Optional (built-in defaults will work in most cases):
#optionsNCPU=2  # number of CPUs
#optionsNBUS=6  # number of busses
#optionsNAPIC=2 # number of IO APICs
#optionsNINTR=24# number of INTs

i am totally clueless. whats going on???

thanx in advance

joy



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

IP tunnel

[Nick Rogness]

Can anyone tell me the difference between nos-tun(8) and gif(4) (Other
than IPv6)?  I want to create a tunnel between 2 networks (IPv4), 2
FreeBSD boxes... will one of these work or is this a different type
of tunnel.  I am familiar with Cisco tunnelling, I am assuming a similar
concept.  Anyone doing this already, if so sample configs?  Is it
possible?

Thanks.

Nick Rogness
- Speak softly and carry a Gigabit switch.





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

hashing a symbol before looking into a hashed table

[gerald stoller]

I've been looking at the source code for  FreeBSD 3.3  and i noticed that a 
table-lookUp is called and given the name to look-up and also its  hashed  
value.  Why is the hashed value supplied, why should the caller even be 
aware of it (this is strictly internal to the table-lookUp)?  Even if there 
are differing hashing techniques for various tables, the caller shouldn't 
have to know which one to use.

Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com



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

Re: Supermicro PIIIDM3 Problems...

[Mike Smith]

Can you be more specific about "panicing"?  As far as details go, you're 
not helping yourself.

> I was doing a FreeBSD 4.0 Install on a fairly new Supermicro PIIIDM3
> motherboard. I eventually got FreeBSD 4.0 installed, however, during the
> install, it kept hanging up and panicing. After trying to do a bin only
> install, it took about 7 trys until it didnt hang up and panic. When I did
> get it installed, everything worked, and it booted. But if I go into
> sysinstall and try to do a post install addition of, lets say src/sys,
> same thing happens. It freezes up and hangs part way throw, and eventually
> will throw up a panic error.
> 
> Any ideas about the stability of the aix78xx driver for this motherboard
> and it's aic-7892 chip?

I use one of these boards on a daily basis; it's been very stable under 
both -stable and -current, although I don't use the SCSI interface very 
often anymore.

-- 
\\ 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-hackers" in the body of the message

Supermicro PIIIDM3 Problems...

[Essenz Consulting]

I was doing a FreeBSD 4.0 Install on a fairly new Supermicro PIIIDM3
motherboard. I eventually got FreeBSD 4.0 installed, however, during the
install, it kept hanging up and panicing. After trying to do a bin only
install, it took about 7 trys until it didnt hang up and panic. When I did
get it installed, everything worked, and it booted. But if I go into
sysinstall and try to do a post install addition of, lets say src/sys,
same thing happens. It freezes up and hangs part way throw, and eventually
will throw up a panic error.

Any ideas about the stability of the aix78xx driver for this motherboard
and it's aic-7892 chip?

-john v. e.



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

Re: NFS server problems on 3.4-S, any interest?

[Matthew Dillon]

:   I have two machines at home, one running 3.4-Stable which is my
:firewall/natd/file server machine. The other is running 5.0-Current
:(around 5/8 right now) which mounts a whole bunch of stuff via amd from
:the 3.4 machine. Up until say... 2 months ago, this worked really well.
:I never had any nfs performance problems. One of the things I mount for
:example is /usr/src, and my make world time didn't suffer much, if at
:all. 
:
:   However, at some point about 2 months ago (I wish I had a more definite
:time period, but the problem has kind of snuck up on me) I have been
:getting increasingly bad performance from the nfs mount. I get "nfs
:...
:Doug

First, make sure the 5.x machine is up to date.

Second, start looking for network problems, because if you are getting
'host not responding' errors it's probably due to packet loss somewhere.
NFS is particularly sensitive to packet loss.  This doesn't sound like
an NFS problem on the face of it.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


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

eBones really dead?

[Doug Barton]

I read this weekend that eBones is dead, but I still see it in my src
tree on -Current, so I'm curious as to what the status really is. 

Thanks,

Doug
-- 
"Live free or die"
- State motto of my ancestral homeland, New Hampshire

Do YOU Yahoo!?


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

NFS server problems on 3.4-S, any interest?

[Doug Barton]

I have two machines at home, one running 3.4-Stable which is my
firewall/natd/file server machine. The other is running 5.0-Current
(around 5/8 right now) which mounts a whole bunch of stuff via amd from
the 3.4 machine. Up until say... 2 months ago, this worked really well.
I never had any nfs performance problems. One of the things I mount for
example is /usr/src, and my make world time didn't suffer much, if at
all. 

However, at some point about 2 months ago (I wish I had a more definite
time period, but the problem has kind of snuck up on me) I have been
getting increasingly bad performance from the nfs mount. I get "nfs
server not responding" errors periodically, sometimes lasting for a
minute or more. Last night/this morning the nfs mount stopped
completely, and my world build failed. I also tried mounting the src
directory directly (no amd) and there was no improvement. I tried
killing nfsiod on the workstation and that got things going again
temporarily, but then it died again. 

So, I am intimately aware of the improvements in nfs in 4.0-Stable, so
if the answer is to just upgrade and get it over with, no problem. I
like to run one of my machines on the older branches to keep track of
possible problems that might crop up at work, but that's no great
sacrifice. However, if there is any interest in debugging this problem,
I'd be glad to help. I've tried ktrace'ing the nfsd on the 3.4 machine,
but I get no output (a 0 byte kdump file). I haven't been able to get a
tcpdump yet, since it usually doesn't wedge itself long enough. In any
case, if anyone is interested in this problem, let me know. If I don't
hear from anyone by friday I'll likely go ahead and do the 4.0 upgrade. 

Doug
-- 
"Live free or die"
- State motto of my ancestral homeland, New Hampshire

Do YOU Yahoo!?


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

SMP kernel compilation??

[Joy Ganguly]

hi all,

i tried to compile a SMP kernel . but when it tries to load the kernel
it gives me " undefined symbol" messages. the messages are:-

intr_machdep.o(.data+0xc0): undefined reference to `Xtsintr0'
intr_machdep.o(.data+0xc4): undefined reference to `Xtsintr1'
intr_machdep.o(.data+0xc8): undefined reference to `Xtsintr2'
intr_machdep.o(.data+0xcc): undefined reference to `Xtsintr3'
intr_machdep.o(.data+0xd0): undefined reference to `Xtsintr4'
intr_machdep.o(.data+0xd4): undefined reference to `Xtsintr5'
intr_machdep.o(.data+0xd8): undefined reference to `Xtsintr6'
intr_machdep.o(.data+0xdc): undefined reference to `Xtsintr7'
intr_machdep.o(.data+0xe0): undefined reference to `Xtsintr8'
intr_machdep.o(.data+0xe4): undefined reference to `Xtsintr9'
intr_machdep.o(.data+0xe8): undefined reference to `Xtsintr10'
intr_machdep.o(.data+0xec): undefined reference to `Xtsintr11'
intr_machdep.o(.data+0xf0): undefined reference to `Xtsintr12'
intr_machdep.o(.data+0xf4): undefined reference to `Xtsintr13'
intr_machdep.o(.data+0xf8): undefined reference to `Xtsintr14'
intr_machdep.o(.data+0xfc): undefined reference to `Xtsintr15'
*** Error code 1

i grepped the source but couldnt find any reference to the above
symbols. whats wrong???

thanx in advance

joy



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

Re: Device driver requirement...

[Andrew Reiter]

You are correct.. However, they were quite useless, imo.  This tutorial
will go into detail regarding each step of the skeleton for ading syscalls
and device drivers so that hopefully anyone can quickly learn how to write
them.

Andrew

On Tue, 23 May 2000, Daniel C. Sobral wrote:

|Andrew Reiter wrote:
|> 
|> Quick note... in my tutorial on writing KLD's, it will include a section
|> on an example character device skeleton.  3 of 5 sections are complete in
|> this tutorial... so I suspect that son I will release it publically.
|
|We had a a script, written by Julian, I think, in our tree that
|generated skeleton drivers for 2.2.x. I don't know if they ever got
|updated for 3.x, and I'm pretty confident they didn't get updated for
|4.x. :-) But, still... you might want to replace them in our tree?
|
|-- 
|Daniel C. Sobral   (8-DCS)
|[EMAIL PROTECTED]
|[EMAIL PROTECTED]
|[EMAIL PROTECTED]
|
|   "Sentience hurts."
|
|

-
Andrew Reiter<[EMAIL PROTECTED]> 
Computer Security Engineer 



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

Re: Device driver requirement...

[Daniel C. Sobral]

Andrew Reiter wrote:
> 
> Quick note... in my tutorial on writing KLD's, it will include a section
> on an example character device skeleton.  3 of 5 sections are complete in
> this tutorial... so I suspect that son I will release it publically.

We had a a script, written by Julian, I think, in our tree that
generated skeleton drivers for 2.2.x. I don't know if they ever got
updated for 3.x, and I'm pretty confident they didn't get updated for
4.x. :-) But, still... you might want to replace them in our tree?

-- 
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"Sentience hurts."



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

Re: boot/kernel debugging

[Nick Hibma]

> > You can single step at boot time, by setting the flags in the loader.
> 
> None of this will be source level, correct?  Will it at least have labels if
> i use a debug kernel?

With remote debugging it will be source level debugging, with DDB it
will not. In both cases it will have labels. Even in modules.

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



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

Re: please hellllllllllllp me!

[Aleksandr A.Babaylov]

Alfred Perlstein writes:
> > 2- how I can write somthing in a file that nobody can
> > see them
> > my mean: in crontab adding some command that this is
> > hidden.
> impossible(*) afaik.
possible if use similar to linux emulator method
to redirect open(2) - but it is TOO expansive
and kernel need to be changed IMHO for this

-- 
@BABOLO  http://links.ru/


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

Re: Device driver requirement...

[Andrew Reiter]

Quick note... in my tutorial on writing KLD's, it will include a section
on an example character device skeleton.  3 of 5 sections are complete in
this tutorial... so I suspect that son I will release it publically.


Andrew

On Mon, 22 May 2000, G.B.Naidu wrote:

|
|Hi,
|
|I would like to know about the device drivre development. I know the basic
|concepts behind a device driver. But haven't written a driver my self. But
|now time has come for me to do that.
|
|I need to develop a device driver for a ethernet switch/hub. So I would
|like to have some clarifications:
|
|1. How much effort it takes for a real device driver to be written?
|Please provide a realistic estimate. I guess somebody might have written
|some commercial device drivres.
|
|2. What all information do I need to design a device driver? I have the
|data sheets of the product available from the net. Anything else I need?
|
|3. How do I decide whether a driver has to be block device or character
|device?
|
|4. I went through the two documents posted on the list about newbus. Is it
|mandatory that one has to use newbus architecture from FreeBSD 4.0
|onwards? Frankly speaking I didnt understand much of the documents. 
|
|5. I would like to know where I can get the small driver written by Warner
|Losh?
|
|6. Any other info on device drivers for freeBSD other than these two
|documents posted on the list? I checked in the handbook but there seems
|nothing on device drivres.
|
|
|thanks in advance
|--gb
| 
|
|
|
|
|To Unsubscribe: send mail to [EMAIL PROTECTED]
|with "unsubscribe freebsd-hackers" in the body of the message
|

-
Andrew Reiter<[EMAIL PROTECTED]> 
Computer Security Engineer 



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

Re: boot/kernel debugging

[J McKitrick]

On Sun, May 21, 2000 at 12:02:53PM +0100, Nick Hibma wrote:

> You can single step at boot time, by setting the flags in the loader.

None of this will be source level, correct?  Will it at least have labels if
i use a debug kernel?

jm
-- 
---
Jonathon McKitrick -- [EMAIL PROTECTED]   
I am a bomb technician.  If you see me running, try to keep up.
---


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

Xircom MPCI Modem ?

[Holm Tiffe]

Hi all,

Does anyone know if it is possible to get an "Xircom MPCI Modem 56 WinGlobal"
working with - current ?

It is the internal Modem from my Notebook (Maxdata 650T).
Is this an infamous Win Modem ?


It gets detected as follows:

twity /kernel: found->  vendor=0x11c1, dev=0x0420, revid=0x01
twity /kernel: class=07-80-00, hdrtype=0x00, mfdev=0
twity /kernel: subordinatebus=0 secondarybus=0
twity /kernel: intpin=a, irq=11
twity /kernel: map[10]: type 1, range 32, base fc008400, size  8 , enabled
twity /kernel: map[14]: type 4, range 32, base 1808, size  3 , enabled
twity /kernel: map[18]: type 4, range 32, base 1400, size  8 , enabled

the next device I've found is this:

twity /kernel: found->  vendor=0x1073, dev=0x0010, revid=0x02
twity /kernel: class=04-01-00, hdrtype=0x00, mfdev=0
twity /kernel: subordinatebus=0 secondarybus=0
twity /kernel: intpin=a, irq=5
twity /kernel: map[10]: type 1, range 32, base fc00, size 15 , enabled
twity /kernel: map[14]: type 4, range 32, base 1080, size  6 , enabled
twity /kernel: map[18]: type 4, range 32, base 1800, size  2 , enabled

This appears to be an internal YAMAHA DS-XG Legacy Sound system and a
YAMAHA DS-XG PCI Audio Codec.

I'm totally unfamiliar with this sort of devices, since it is my first
notebook. Please put me in the right direction..

Where can I read how I can get those working?

I've fixed the problems with my internal lan card (lnc based) myself
and mailed a patch to the driver to Paul Richards to detect properly
the AM79C973 chips.



Holm
-- 
FreibergNet Systemhaus GbR  Holm Tiffe  * Administration, Development
Systemhaus für Daten- und Netzwerktechnik   phone +49 3731 781279
Unternehmensgruppe Liebscher & Partnerfax +49 3731 781377
D-09599 Freiberg * Am St. Niclas Schacht 13http://www.freibergnet.de/



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

Re: modules and newbus

[Nick Hibma]

> I got the impression that newbus would make it easier to make kernel
> modules out of things.  What in general does it take to make something
> into a kld?  I'm thinking of pcm for example.  

In general all it takes is a good look at de-allocation of the resources
it allocates. Another point with some hardware is that you need to
deinitialise it and make it shut up / no longer produce interrupts.

Also the encapsulation of the driver into a MODULE needs to be done,
which should be fairly trivial or already done.

Be reminded that you cannot detach from all the busses, like for example
ISA.

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



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

Re: boot/kernel debugging

[Nick Hibma]

In general it is well possible to single step anything in the
kernel. You might find occasions where things stop working, and odd
cases were things all of a sudden start working, but normally, apart
from hardware things, most things are not time critical, or create
problems through spin locks.

You can single step at boot time, by setting the flags in the loader.

set boot_ddb# jump to debugger
set boot_gdb# use remote gdb for debugging by default

Hope this helps.

Nick

> I've used softice for debugging under windows, and i was wondering if gdb
> offers similar capabilities.  It seems the best way to debug the ECP
> parallel port problem is to step through the code during the boot phase.
> Can this be done, or is there too much timing-critical stuff going on then?
> 
> jm
> -- 
> ---
> Jonathon McKitrick -- [EMAIL PROTECTED]   
> I am a bomb technician.  If you see me running, try to keep up.
> ---
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" 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-hackers" in the body of the message

Re: further question to bus_alloc_resource

[Nick Hibma]

> > It was just the first driver I got, so far only an example (bad one).
> > What about aha?
> 
> It would be nice to be able te detach most drivers. I think that when aha
> was converted originally, cam didn't support detach but I'm pretty sure it
> does now.

The cam_sim_free hasn't been exercised a lot. I've tried using it for
the USB Zip drives, but I failed at some stage and left it at
that. Basically, you can detach from a drive, but you can't detach from
a SIM IMHO.

However, the PCCARD ahc driver does detach properly from a SIM, so maybe
it does work, and there simply was a bug in my code. One of the things I
was not doing, I just noticed, was to send a AC_LOST_DEVICE for path for
the SIM.

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




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

Re: bpf question

[Graham Wheeler]

Dmitry Samersoff wrote:
> 

> I have stoped on perforamnce bpf itself.
> 
> Is there alternate driver or can changing of bpf queue in kernel help, and where
> I can read about it?

If my memory serves me correctly, Marcus Ranum wrote a white paper on
IDS systems in the early days of NFR, in which he said that the existing
configuration of BPF was inadequate for capturing all packets on a fast
link, and suggested a patch to improve the situation. THe patch involved
bumping up a buffer from about 16kb to 256kb. Unfortunately I no longer
have the details handy, but if you did a search for BPF/IDS/NFR/Ranum
you might find something.


-- 
Dr Graham WheelerE-mail: [EMAIL PROTECTED]
Director, Research and Development   WWW:http://www.cequrux.com
CEQURUX Technologies Phone:  +27(21)423-6065
Firewalls/VPN SpecialistsFax:+27(21)424-3656


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

Re: please hellllllllllllp me!

[Udo Schweigert]

On Mon, May 22, 2000 at 02:59:01 -0700, Alfred Perlstein wrote:
> * Shadi Fazelian <[EMAIL PROTECTED]> [000522 02:31] wrote:
> > Hello.
> > please guide me:
> > 1- how I can see a hidden file (not dot file) and how
> > I can hidden a file ?
> >  my mean: I want make a file that ls -al can't see it.
> 
> impossible(*) afaik.
> 
> > 
> > 2- how I can write somthing in a file that nobody can
> > see them
> > my mean: in crontab adding some command that this is
> > hidden.
> 
> impossible(*) afaik.
> 
> > 
> > 3- how I can run somthing in background that ps can't
> > see it.
> 
> impossible(*) afaik.
> 
> > 
> > please guide me. hackeres attack my servers and I
> > don't know how he/she can.
> 
> (*) see: http://www.rootkit.com/
> and: http://www.rootkit.com/whitepapers.shtml
> 

1- and 3- are possible, if the attacker can change the installed versions of
ls and ps to his own, compromised versions.

Regards

-- 
Udo Schweigert, Siemens AG   | Voice  : +49 89 636 42170
ZT IK 3, Siemens CERT| Fax: +49 89 636 41166
D-81730 Muenchen / Germany   | email  : [EMAIL PROTECTED]
PGP-2/5 fingerprint  | D8 A5 DF 34 EC 87 E8 C6  E2 26 C4 D0 EE 80 36 B2


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

Re: please hellllllllllllp me!

[Alfred Perlstein]

* Shadi Fazelian <[EMAIL PROTECTED]> [000522 02:31] wrote:
> Hello.
> please guide me:
> 1- how I can see a hidden file (not dot file) and how
> I can hidden a file ?
>  my mean: I want make a file that ls -al can't see it.

impossible(*) afaik.

> 
> 2- how I can write somthing in a file that nobody can
> see them
> my mean: in crontab adding some command that this is
> hidden.

impossible(*) afaik.

> 
> 3- how I can run somthing in background that ps can't
> see it.

impossible(*) afaik.

> 
> please guide me. hackeres attack my servers and I
> don't know how he/she can.

(*) see: http://www.rootkit.com/
and: http://www.rootkit.com/whitepapers.shtml

-Alfred


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

please hellllllllllllp me!

[Shadi Fazelian]

Hello.
please guide me:
1- how I can see a hidden file (not dot file) and how
I can hidden a file ?
 my mean: I want make a file that ls -al can't see it.

2- how I can write somthing in a file that nobody can
see them
my mean: in crontab adding some command that this is
hidden.

3- how I can run somthing in background that ps can't
see it.

please guide me. hackeres attack my servers and I
don't know how he/she can.

regurds shadi

__
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/


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

Device driver requirement...

[G.B.Naidu]

Hi,

I would like to know about the device drivre development. I know the basic
concepts behind a device driver. But haven't written a driver my self. But
now time has come for me to do that.

I need to develop a device driver for a ethernet switch/hub. So I would
like to have some clarifications:

1. How much effort it takes for a real device driver to be written?
Please provide a realistic estimate. I guess somebody might have written
some commercial device drivres.

2. What all information do I need to design a device driver? I have the
data sheets of the product available from the net. Anything else I need?

3. How do I decide whether a driver has to be block device or character
device?

4. I went through the two documents posted on the list about newbus. Is it
mandatory that one has to use newbus architecture from FreeBSD 4.0
onwards? Frankly speaking I didnt understand much of the documents. 

5. I would like to know where I can get the small driver written by Warner
Losh?

6. Any other info on device drivers for freeBSD other than these two
documents posted on the list? I checked in the handbook but there seems
nothing on device drivres.


thanks in advance
--gb
 




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