Compiling drivers as lkm's

1999-11-29 Thread Donn Miller
Is there any kernel config option that can be used to link a driver to the kernel dynamically (LKM) instead of statically? Also, I'd like to know how to write a driver as an lkm. Of course, if anyone has any links or info on how to write a driver period, I'd like to know. It seems like the

[PATCH] Four patches for review and test

1999-11-29 Thread Kazutaka YOKOTA
Four patches for review and test. They are for 4.0-CURRENT. (moused patch should also work with -STABLE too.) http://www.freebsd.org/~yokota/moused-991129.diff http://www.freebsd.org/~yokota/kbdcontrol-991129.diff http://www.freebsd.org/~yokota/panickey-991129.diff

Soulness.com - Open your mind and free your soul

1999-11-29 Thread azani . sanchez
Hello, my name is Azani Sanchez, Senior Editor of Soulness.com.6 months ago I started Soulness.com as a senior in my dorm at Howard University in Washington, DC. I would like to invite you to visit www.soulness.com and join our online community, and take a look for yourself and see what we

Re: pcm - I can only get noice from it

1999-11-29 Thread Jesper Skriver
My collegue just made my day :-) device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 did it. /Jesper On Mon, Nov 29, 1999 at 03:22:45PM +0100, Jesper Skriver wrote: Hi, Just managed to get hold of a old Soundblaster

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Greg Lehey
On Saturday, 27 November 1999 at 10:26:15 -0500, Viren R.Shah wrote: I'm running a -current system from Nov 26th (approx 4am EST). I can currently reliably crash the system by doing: ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html The crash only works when I

ACPI project progress report - Nov.

1999-11-29 Thread Mitsuru IWASAKI
of cooperation/volunteers and others are very appreciated. Thanks! begin 644 acpi-sys-19991129.diff.gz M'XL(")N40C@``V%CDMWES+3$Y.3DQ,3(Y+F1I9F8`M#Q]?]HXTG^33Z'+ M7GO0`('T9;M-DRT!)_$M`0Z;IGUZ_?F,48(O8/ML0Y+;]C[[,Z,76P:;DPW MVTUE:32:8U,R.I$_?JBM3"18_4Z_M1Z-211A2+]Z/[J-]]^7;-_NV$[CL M5]TA94[

HEADS UP, bind update shortly...

1999-11-29 Thread Peter Wemm
I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the broken parts of the tree as I go. I will disable the named (and associated tools) build for the duration. If you want to do some make worlds or releases in the next 8 hours or so, do a cvsup pronto! Cheers, -Peter To

BOOTP appears to be broken again

1999-11-29 Thread Matthew Dillon
Hmm. BOOTP appears to be broken again in current My diskless systems are insisting on mounting root from fd0c with the latest current (verses one about a month ago). -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: Route table leaks

1999-11-29 Thread John Polstra
In article [EMAIL PROTECTED], Matthew Dillon [EMAIL PROTECTED] wrote: :1. Do I really need the splnet calls around RTFREE? Yes. Because the route table may be flushed from an interrupt in a low memory situation. I guess I didn't state the question very well. I realize that

Re: HEADS UP, bind update shortly...

1999-11-29 Thread Peter Wemm
Peter Wemm wrote: I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the broken parts of the tree as I go. I will disable the named (and associated tools) build for the duration. If you want to do some make worlds or releases in the next 8 hours or so, do a cvsup pronto!

Re: loader.conf, ordering of loading of modules

1999-11-29 Thread Daniel C. Sobral
Nick Hibma wrote: Is it possible to change the order in which modules are loaded in loader.conf? I need usb before uhci before ums. usb_load="YES" uhci_load="YES" ums_load="YES" doesn't do it. Funny, I thought they were loaded in the order they were declared.

Re: HEADS UP, bind update shortly...

1999-11-29 Thread Nate Williams
I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the broken parts of the tree as I go. I will disable the named (and associated tools) build for the duration. If you want to do some make worlds or releases in the next 8 hours or so, do a cvsup pronto! Thanks Peter! Nate

More newpcm breakage

1999-11-29 Thread Dag-Erling Smorgrav
My SB32 PnP, which had so far worked nicely with newpcm except for the "fast forward" bug, stopped working after the newmidi import. This means that none of my sound cards (except for the GUS PnP, which I haven't tested) work any more, and I am seriously losing faith in the authors' ability to

MAKEDEV newpcm driver

1999-11-29 Thread Donn Miller
So, is the right command to make the audio device entries ./MAKEDEV snd0, or does newpcm have a different method to create the audio device entries? Also, I have an ESS 1868, and I'm getting the "fast forward" effect with the newpcm driver. It's a SB compatible card. I'll attach the output

Re: State of Alpha support and Oracle.

1999-11-29 Thread Tim
http://www.relex.ru/linter/ This looks pretty neat. Has anybody actually used this under FreeBSD? Any comments? One of the tricky things about selecting FreeBSD software is how commited the vendor is towards the OS. I'd hate to commit to something like this and then have the vendor stop

New vfs_conf.c panic

1999-11-29 Thread Manfred Antar
Mike I get a panic on current smp-kernel with the new version of vfs_conf.c . The system is current as of this morning If I back out to version 1.44 it boots fine. It seems to panic at the swapon part of the boot process. I get : Fatal trap 12: page fault while in kernel mode mp_lock = 0102;

Re: New vfs_conf.c panic

1999-11-29 Thread Matthew Dillon
:c014a794 T devsw :c014a7b0 T cdevsw_add c014a79a --- sounds like the same or a similar bug to the one I fixed, where devsw() was being called with rootdev == NODEV (-1) and doing a NULL (well -1) pointer dereference. In my case it was related to an assumption at line 203 of

Re: New vfs_conf.c panic

1999-11-29 Thread Poul-Henning Kamp
Do you have /dev/sd* in your /etc/fstab ? It should be changed to /dev/da* In message [EMAIL PROTECTED], Manfred Antar writes: At 09:29 PM 11/29/99 +0100, Poul-Henning Kamp wrote: Manfred, Could you send the 10 lines surrounding the address 0xc014a79a from the output of "nm -n /this_kernel"

Re: IP Filter 3.3.3 in FreeBSD -CURRENT [LONG]

1999-11-29 Thread Nathan Kinsman
No solutions for you, but I have had the same exact problems with Current and Ip Filter 3.3.3. Giving up. Current Ip Filter works fine on 3.3-STABLE. Can't hardly wait for 4.0 to be stable and released, I'm not happy with my current mangling of different compilers in STABLE. _ Nathan Kinsman

Re: New vfs_conf.c panic

1999-11-29 Thread Matthew Dillon
:Mike :I get a panic on current smp-kernel with the new version :of vfs_conf.c . :The system is current as of this morning :If I back out to version 1.44 it boots fine. :It seems to panic at the swapon part of the boot process. :I get : :Fatal trap 12: page fault while in kernel mode :mp_lock =

Re: New vfs_conf.c panic

1999-11-29 Thread Manfred Antar
At 09:29 PM 11/29/99 +0100, Poul-Henning Kamp wrote: Manfred, Could you send the 10 lines surrounding the address 0xc014a79a from the output of "nm -n /this_kernel" ? OK This kernel was striped -g do you need a debug compiled kernel ? Here is what i get c014a1c8 T set_timecounter c014a234 t

HEADS-UP -- 4.0 alpha klds will need recompiling!

1999-11-29 Thread Andrew Gallatin
My recent change to the ipl functions in -CURRENT means that alpha kld modules will need to be recompiled before rebooting with a kernel built from version 1.14 or greater of sys/alpha/alpha/ipl_funcs.c. Klds will need to be recompiled because now that the spl functions are inlines, their

IP Filter 3.3.3 in FreeBSD -CURRENT [LONG]

1999-11-29 Thread Davec
Ok, I just tried downloading the IP Filter sources for 3.3.3 and followed the instructions at http://www.freebsddiary.org/freebsd/ipfilter333.htm. Unfortunately I have ended up with the same errors: open device: Device not configured ioctl(SIOCIPFFL): Bad file descriptor To reiterate for

Re: New vfs_conf.c panic

1999-11-29 Thread Manfred Antar
At 09:55 PM 11/29/99 +0100, Poul-Henning Kamp wrote: Do you have /dev/sd* in your /etc/fstab ? It should be changed to /dev/da* This is what I have # DeviceMountpoint FStype Options DumpPass# /dev/rda0s1bnoneswapsw 0 0

Re: New vfs_conf.c panic

1999-11-29 Thread Manfred Antar
At 10:23 PM 11/29/99 +0100, Poul-Henning Kamp wrote: Ahh, Ok. Bruce (a little hasty in my mind) removed a compat shim we had, please change the 'rda' to 'da' again and all should be fine. Poul-Henning Done Thanks Manfred = ||[EMAIL PROTECTED] || ||Ph. (415)

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Viren R.Shah
"Greg" == Greg Lehey [EMAIL PROTECTED] writes: Greg On Saturday, 27 November 1999 at 10:26:15 -0500, Viren R.Shah wrote: I'm running a -current system from Nov 26th (approx 4am EST). I can currently reliably crash the system by doing: ln -s

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Matthew Dillon
: : Eivind I *think* I know what this is due to - please upgrade : Eivind src/sys/nfs/nfs_vnops.c to revision 1.146 (which I just : Eivind committed) and try again. : :Tried it. Doesn't work. :-( It still crashes when creating a symbolic :link on a NFS mounted filesystem. [This is unfortunate in

Re: IP Filter 3.3.3 in FreeBSD -CURRENT [LONG]

1999-11-29 Thread O'Shaughnessy Evans
Davec [EMAIL PROTECTED] wrote: [...] But when I try to load any rules, I get the error messages above. Same result with ipnat. I checked to make sure I was using the right version of ipf: [...] So could it be that some of your rules are breaking things? I think I've seen the same error

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Julian Elischer
makeoptions DEBUG="-g" Easier option.. config -g To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Matthew Dillon
: : : makeoptions DEBUG="-g" : :Easier option.. :config -g Actually no. How many people remember to type options after 'config' ? Especially if you are juggling more then one kernel config, trying to remember which ones you intend to compile -g and which ones you don't

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Viren R.Shah
"Matt" == Matthew Dillon [EMAIL PROTECTED] writes: Matt The problem is a NULL pointer dereference somewhere... please Matt nm your kernel binary and extract out all elements with c0163 Matt in them. e.g. nm /kernel | fgrep c0163 | sort. OK, here's a -current system from today

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Eivind Eklund
On Mon, Nov 29, 1999 at 01:52:29PM -0800, Matthew Dillon wrote: : : Eivind I *think* I know what this is due to - please upgrade : Eivind src/sys/nfs/nfs_vnops.c to revision 1.146 (which I just : Eivind committed) and try again. : :Tried it. Doesn't work. :-( It still crashes when creating

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Eivind Eklund
On Mon, Nov 29, 1999 at 11:56:31PM +0100, Eivind Eklund wrote: I've been peering over the code, and I am unable to find anything wrong :-( I've also gotten panic information and symbol information from Viren, but this hasn't made me any wiser - the failure was in setlock (which seems to be an

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Matthew Dillon
:OK, here's a -current system from today (11/29) morning [4am EST] with :kernel compiled with DDB and -g. : :Tried doing a simple symlink over a NFS mounted filesystem: : :fatal trap 12: page fault while in kernel mode :fault virtual address = 0x4 :fault code= supervisor read, page

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Matthew Dillon
: Eivind, I'm not sure that change you made is legal. People use : symlink creation the same way they use O_EXCL file creation - as a : locking mechanism. In fact, in NFSv2 O_EXCL file creation is not : atomic (I'm pretty sure) and symlink was the *only* method available. : :The

-CURRENT crash under high exec() loads.. (vm_map_insert?)

1999-11-29 Thread Thomas Stromberg
While doing some testing (and actually, in the middle of me trying to post some results) for the FreeBSD Auditing project, my 4.0-CURRENT box crashed. These tests involved a barrage of automated exec() calls which I suspect is what tore it down. I had a similar crash two weeks ago, but did not

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Matthew Dillon
:I think I (well, Alfred Perlstein) have found what the problem is - in :nfs_symlink, newvp isn't initialized for NFSv2. Unfortunately, I have :zero clue about how to fix that - Alfred believes the checks for NFSv3 :may not be necessary - myself, I find the NFS code almost totally

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Viren R.Shah
"Matt" == Matthew Dillon [EMAIL PROTECTED] writes: Matt I've added a little cleanup to this patch. Viren, please try this Matt patch. Matt -Matt Matt Matthew Dillon Matt [EMAIL

Re: State of Alpha support and Oracle.

1999-11-29 Thread Mike Smith
http://www.relex.ru/linter/ This looks pretty neat. Has anybody actually used this under FreeBSD? Any comments? One of the tricky things about selecting FreeBSD software is how commited the vendor is towards the OS. I'd hate to commit to something like this and then have the vendor

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Viren R.Shah
Matt I've added a little cleanup to this patch. Viren, please try this Matt patch. I compiled a kernel with it, and no panic!! Here's what I get instead: [vshah@jabberwock] ~ rm index.html rm: index.html: No such file or directory 2220 [6:41pm]

Re: repeatable crash in -current (softupdates, NFS)

1999-11-29 Thread Matthew Dillon
:I compiled a kernel with it, and no panic!! Here's what I get instead: : :[vshah@jabberwock] ~ rm index.html :rm: index.html: No such file or directory :2220 [6:41pm] :[vshah@jabberwock] ~ ln -s public_html/index.html

Re: New vfs_conf.c panic

1999-11-29 Thread Mike Smith
Ahh, Ok. Bruce (a little hasty in my mind) removed a compat shim we had, please change the 'rda' to 'da' again and all should be fine. Actually, I did the dirty work because I agreed with Bruce. What I don't understand is why the system explodes when it can't find /, rather than giving

Re: New vfs_conf.c panic

1999-11-29 Thread Matthew Dillon
: Bruce (a little hasty in my mind) removed a compat shim we had, : please change the 'rda' to 'da' again and all should be fine. : :Actually, I did the dirty work because I agreed with Bruce. What I don't :understand is why the system explodes when it can't find /, rather than :giving up

Re: More newpcm breakage

1999-11-29 Thread tanimura
On 29 Nov 1999 19:19:24 +0100, Dag-Erling Smorgrav [EMAIL PROTECTED] said: Dag-Erling My SB32 PnP, which had so far worked nicely with newpcm except for the Dag-Erling "fast forward" bug, stopped working after the newmidi import. This Dag-Erling means that none of my sound cards (except for

Re: -CURRENT crash under high exec() loads.. (vm_map_insert?)

1999-11-29 Thread Matthew Dillon
:the timeout to kill it off because of the interactive mode. Otherwise :there was ~960,000 accumulated exec()'s altogether in a 5 hour period. : :As you can see, cron is the process that crashed it. Two weeks ago it :was an eggdrop. I've not had any crashes in -CURRENT while this program :was not

Re: IP Filter 3.3.3 in FreeBSD -CURRENT [LONG]

1999-11-29 Thread O'Shaughnessy Evans
"Mikhail A. Sokolov" [EMAIL PROTECTED] wrote: On Mon, Nov 29, 1999 at 02:15:16PM -0800, O'Shaughnessy Evans wrote: # Davec [EMAIL PROTECTED] wrote: # [...] # But when I try to load any rules, I get the error messages above. # Same result with ipnat. I checked to make sure I was using the

Re: sbc and pcm

1999-11-29 Thread tanimura
The following patch makes sbc_probe() to look at the vendor ID only for AWE64. Also, any device that has a logical ID matching 0x??0080ce should get probed. Index: sbc.c === RCS file: /home/ncvs/src/sys/dev/sound/isa/sbc.c,v

Re: IP Filter 3.3.3 in FreeBSD -CURRENT [LONG]

1999-11-29 Thread Davec
On Mon, 29 Nov 1999, O'Shaughnessy Evans wrote: "Mikhail A. Sokolov" [EMAIL PROTECTED] wrote: No, it can't. He was refering to ipf -V; I managed to reproduce the behaviour several days ago, but since I remade the devices it's ok in my case, but in his. Again, no other rules/whatever is

Re: IP Filter 3.3.3 in FreeBSD -CURRENT [LONG]

1999-11-29 Thread Davec
On Mon, 29 Nov 1999, O'Shaughnessy Evans wrote: So could it be that some of your rules are breaking things? I think I've seen the same error message when trying to write a rule for a non-existant interface name or a group that wasn't created with "... head N". -- O'Shaughnessy Evans I

Re: ep driver troubles

1999-11-29 Thread Matthew N. Dodd
On Mon, 29 Nov 1999, Eric Ogren wrote: Already there (I can attach my entire config file / dmesg output to anyone who wants to see it, but I didn't want to dump the whole thing to the list). How about the output of 'pnpinfo'? Apply this patch:

Re: MAKEDEV newpcm driver

1999-11-29 Thread Chris Costello
On Mon, Nov 29, 1999, Donn Miller wrote: So, is the right command to make the audio device entries ./MAKEDEV snd0, or does newpcm have a different method to create the audio device entries? Also, I have an ESS 1868, and I'm getting the "fast forward" effect with the newpcm driver. It's

Re: FreeBSD security auditing project.

1999-11-29 Thread Robert Watson
(Damn, go away for Thanksgiving and fall behind on -CURRENT, and miss out on large interesting and fast-paced discussions! I am now subscribed to the new -audit, and probably missed some messages. I've Bcc'd this to -current, but CC'd to -audit under the assumption that that is where it

Re: New vfs_conf.c panic

1999-11-29 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Mike Smith writes: Ahh, Ok. Bruce (a little hasty in my mind) removed a compat shim we had, please change the 'rda' to 'da' again and all should be fine. Actually, I did the dirty work because I agreed with Bruce. What I don't understand is why the system

Fast forward bug and newpcm (again)

1999-11-29 Thread Donn Miller
Yes, I DO have the bridge drivers in my kernel config files, and I still get the "fast forward" effect with my ESS 1868. My guess is that it's just a bug with the ESS 1868 driver, I don't know. Maybe my ordering is wrong? I've had the sbc driver for the ESS ever since the bridge drivers came

Re: Fast forward bug and newpcm (again)

1999-11-29 Thread Seigo Tanimura
On Tue, 30 Nov 1999 01:41:20 -0500, Donn Miller [EMAIL PROTECTED] said: Donn Now, the question is, do I use the Sound Blaster bridge driver Donn for the ESS 1868? And, is my ordering wrong? sbc driver does not probe ESS1868 at this moment. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL

Re: More newpcm breakage

1999-11-29 Thread Jeroen Ruigrok/Asmodai
-On [19991129 19:49], Dag-Erling Smorgrav ([EMAIL PROTECTED]) wrote: My SB32 PnP, which had so far worked nicely with newpcm except for the "fast forward" bug, stopped working after the newmidi import. This means that none of my sound cards (except for the GUS PnP, which I haven't te

Re: Fast forward bug and newpcm (again)

1999-11-29 Thread Donn Miller
On Tue, 30 Nov 1999, Seigo Tanimura wrote: On Tue, 30 Nov 1999 01:41:20 -0500, Donn Miller [EMAIL PROTECTED] said: Donn Now, the question is, do I use the Sound Blaster bridge driver Donn for the ESS 1868? And, is my ordering wrong? sbc driver does not probe ESS1868 at this moment.

Re: AHC0 fireworks ?

1999-11-29 Thread Warner Losh
In message [EMAIL PROTECTED] "Justin T. Gibbs" writes: : Parity errors indicate that data integrity is compromised on your SCSI : cable. Perhaps you bumped a connector, or a connector had been loose : for a long time and has just shifted to the point of causing a failure. : Open your case,