Re: SoundBlaster PCI-128 performance

[Kenneth Wayne Culver]

maybe you did. I'm not sure what the problem is then.

Ken

On 30 Nov 2001, Seth Kingsley wrote:

> On Fri, Nov 30, 2001 at 09:12:52AM -0500, Kenneth Culver wrote:
> > On Friday 30 November 2001 02:44 am, you wrote:
> > Have you tried different speakers? Also have you tried moving the soundcard 
> > to a different slot? maybe some other card is causing interferance. I have a 
> > card that uses the same driver and havn't had a problem.
> 
> Oops, did I neglect to mention that it works perfectly under Windows 98
> SE?
> 
> -- 
> || Seth Kingsley || Meow Meow Fluff Fluff || [EMAIL PROTECTED] ||
> || rndcontrol -s 0 ||
> 


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

Re: linuxulator unimplemented syscalls

[Kenneth Wayne Culver]

> Your problem is probably somewhere other than ioctl 0x7201; try
> trussing/stracing the app and see what it's trying to access.
> 
Alright, I'll try that, I think I have another clue though, I got it to
find the file (it was looking in /usr/compat/linux/mnt/cdrom instead of
the regular /mnt/cdrom I guess b/c it was running from linux) but now it's
back to having problems with mmap2. I'll find the manpage on truss, and
put some output here when I get some.

Ken


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

Re: linuxulator unimplemented syscalls

[Kenneth Wayne Culver]

On Thu, 29 Nov 2001, Dan Nelson wrote:

> In the last episode (Nov 28), Kenneth Culver said:
> > I was just wondering if the following syscalls had any chance of being 
> > implemented anytime soon?
> > 
> > linux: syscall ftruncate64 is obsoleted or not implemented (pid=5695)
> > linux: syscall mmap2 is obsoleted or not implemented (pid=5691)
> > linux: 'ioctl' fd=6, cmd=0x7201 ('r',1) not implemented
> > 
> > I'm wondering because I wanted to use the new transgaming winex to
> > run windows games (which would allow me to remove windows completely
> > from my computer) but it won't run because these syscalls aren't
> > supported.
> > 
> > I'm running -CURRENT from a few days ago, with the linux_base-7.1 linux 
> > libraries. Thanks.
> 
> >From Linux headers:
> 
> #define TUNIOCGETINFO  0x7201  /* get version of driver & capabilities of tuner */
> 
> Doubtful that its failure will affect you.  I assume ftruncate64()
> should map almost directly onto our ftruncate().  Not sure what mmap2()
> is.
> 
Well, I switched to the linux_base-6.1 libs and all but the 0x7201 error
stopped occuring, but still the same problem, winex says it can't open the
the file that I'm trying to execute.

Ken


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

Re: FreeBSD current is very slow

[Kenneth Wayne Culver]

Well, FreeBSD-CURRENT will have bugs... That's why it's -CURRENT and not
-STABLE

Ken

On Mon, 10 Sep 2001, Liu Siwei wrote:

> Hi,all:
> Do you run freebsd-current? what current? I make a
> clean SNAP of freebsd-current through make release.
> And make a CD. I install freebsd-current from my own
> CD. All things are fine. But its multimedia is not
> soundable. I compile gnome-1.4 on this current-SNAP
> smoothly from source through ports. But when I first
> run gnome desktop environment, it takes long time to
> appear desktop environment. But when I disable the
> gnome's sound event and restart it again, it is very
> quickly start up. This is one reason I say that.
> Secondly, I make mpg123 from ports by
> source(current ports). I start it in background like
> this: "mpg123 my.mp3 &", I use top command to see my
> system's load, I was surpised: mpg123 only takes no
> more than 5% system resources, but the interrupt TAKES
> more than 90% system resources. So my system is very
> slow to run other software. Why? and I want to know
> what's the interrupt and it relates what?
> Now, I have installed FreeBSD 4.4RC1. I compile
> mpg123 again, and play it background, I find the
> interrupt takes no more than 5% system resource!
> Is it FreeBSD-current's BUGs???
> 
> Best Regard.
> 
> 
> __
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.yahoo.com
> 
> 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: Headsup! KSE believers should show up!

[Kenneth Wayne Culver]

Well, I for one can test it on an alpha (I'm borrowing from
[EMAIL PROTECTED]) as soon as my DSL gets installed ;-)

Ken

On Mon, 27 Aug 2001, Garance A Drosihn wrote:

> At 5:09 PM -0700 8/27/01, Darryl Okahata wrote:
> >  Is there some reason why KSE couldn't be integrated
> >ASAP *AFTER* 5.0 is released?
> >
> >[ Personally, I'd like to see it in 5.0, but, with all the qualms that
> >   people seem to have, I'm curious as to why it can't be integrated
> >   immediately after 5.0 is cut?  This way, Julian's MFCs are reduced,
> >   and it gives people more time to pound on KSE.  ]
> 
> In the interests of progress, let us assume for the moment that most
> of the qualms about KSE could be addressed by more testing of it,
> and a little more work for non-Intel platforms.
> 
> Based on that assumption, anyone who is eager for KSE should realize
> that NOW is the time to step forward and help out with it.  If we
> can get a reasonable amount of testing done in the next two or three
> weeks, then maybe we could get KSE committed for "5.0", and also
> get "5.0" released when we expected to release it.
> 
> I think this would be the ideal outcome.  If you have any energy to
> spare right now, let's put that energy towards the ideal outcome.
> But NOW is the time to help out, not in late October or November.
> 
> I have changed the subject for this message, because I am hoping
> that a more positive subject might get a more positive result.
> Anyone who does think KSE is worth having for 5.0, should step up
> and provide Julian with the help needed to address the legitimate
> concerns which have been mentioned.  Julian does not need people
> descending into a flame-war, he needs people to show up and help out.
> 
> -- 
> Garance Alistair Drosehn=   [EMAIL PROTECTED]
> Senior Systems Programmer   or  [EMAIL PROTECTED]
> Rensselaer Polytechnic Instituteor  [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: Headsup! KSE Nay-sayers speak up!

[Kenneth Wayne Culver]

> > >   I have one system that I've been maintaining/updating since the
> > > 2.X days and I feel it's time to nuke it and start over. +1 for a 
> > > non-smp system and SMP system.
> > > 
> > >   That said, I think the value of having both KSE and SMPng in 5.0
> > > is HUGE and I think there is probably a large number of people that
> > > would be willing to endure kernel panics, dumps, etc. because the value
> > > (in terms of technological accomplishment and saleability in the
> > > corporate space) would be absolutely worth the bumpy road.  -CURRENT
> > > isn't worth tracking unless the dumps, bugs, etc are all going toward
> > > both SMPng and KSE.
> > 
> > 
> > Hey, anyone running -current without a tape drive attached with a daily dump 
>schedule is either insane, a masochist, or both.
> > 
> > Read my post from this morning about the mysterious filesystem corruption I had 
>this morning...  Kudos to Justin Gibbs for fixing 
> > EOM detection [let's get his scsi_sa.c patches committed ASAP]!!!
> 
>   Thanks for the heads up!  Fortunately I have a few -STABLE
> systems that I can dump to and that host all of my email/development.  
> ;)  I'll probably go and pick up another 40+GB HD just for the extra
> head-room.
> 
> > >   If there are grave concerns about having KSE and SMPng in 5.X,
> > > then why not push back the release date?  The value far outweighs the
> > > extra months needed to get it finished and out the door, but what do I
> > > know, I'm just a quiet kernel by standard making an observation. -sc
> > 
> > 
> > Good idea.
> 
>   Seriously, is there any reason to hold to a time line at the
> expense of some very important and very fundamental enhancements to
> FreeBSD?  I suppose that's something for -core to talk about/discuss,
> but I bet that if a poll was put on the homepage of FreeBSD.org (hint
> hint) asking about this, you'd get an overwhelming response to see
> KSE/SMPng in 5.X.  With a poll you might even pick up some more testers
> given the exposure (hint hint).  -sc
> 
If it's testers you want, submit a story on slashdot heh heh, I know a lot
of BSDers that are converts from linux that want to test stuff, but only
read slashdot for their computer news.

Ken


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

Re: Headsup! KSE Nay-sayers speak up!

[Kenneth Wayne Culver]

> > FreeBSD is going to be left in the dust unless both the SMPng *AND*
> > KSE projects are integrated into 5.0.
> 
> I care about having a system that works well and does what I ask of
> it.  What the Linux horde is doing is of little concern to me, and I
> suspect the same goes for a number of other long-time FreeBSDers.
> 
Well, I've only been using FreeBSD for 4 or 5 years, and I don't really
care what the "linux horde" is doing, but I would like to see FreeBSD
surpass the other x86 OS's in terms of performance as well as "uptime"

Ken


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

RE: Headsup! KSE Nay-sayers speak up!

[Kenneth Wayne Culver]

On Mon, 27 Aug 2001, Garrett Wollman wrote:

> < said:
> 
> > Just to get this out in the public: I for one think 5.x has enough changes in
> > it and would like for KSE to be postponed to 6.0-current and
> > 6.0-release.
> 
> I agree.  I'd like to see this stuff happen, but I think it's too
> disruptive a change while we still haven't yet gotten over many of the
> SMPng issues yet.

Sorry to butt in on this conversation here, but wasn't one of the main
points of 5.0 and SMPng to bring KSE's into FreeBSD?

Ken


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

Re: QT23 not building

[Kenneth Wayne Culver]

You are building from the ports tree right? Did you check to make sure you
have The include path and library path for OpenGL libraries in the QT
Makefile?

On Tue, 21 Aug 2001, Salvo Bartolotta wrote:

> Dear FreeBSD'ers,
> 
> I am running -CURRENT as of August 18, 2001 -- yet another entry in the 
> -current userbase, BTW.
> 
> I am using XFree4 and my /etc/make.conf contains the required XFree86 version 
> string.
> 
> Qt23 will NOT build. It dies here:
> 
> 
> gmake[2]: Leaving directory `/usr/ports/x11-toolkits/qt23/work/qt-2.3.1/tools'
> gmake[1]: Leaving directory `/usr/ports/x11-toolkits/qt23/work/qt-2.3.1/tools'
> 
> The Qt library is now built in ./lib
> The Qt examples are built in the directories in ./examples
> The Qt tutorials are built in the directories in ./tutorial
> 
> Note: be sure to set $QTDIR to point to here or to wherever
>   you move these directories.
> 
> Enjoy!   - the Trolltech team
> 
> (cd /usr/ports/x11-toolkits/qt23/work/qt-2.3.1/src && /usr/bin/env 
> QTDIR=/usr/ports/x11-toolkits/qt23/work/qt-2.3.1 
> LD_LIBRARY_PATH=/usr/ports/x11-toolkits/qt23/work/qt-2.3.1/lib 
> PORTOBJFORMAT=elf PREFIX=/usr/X11R6 LOCALBASE=/usr/local X11BASE=/usr/X11R6 
> MOTIFLIB="-L/usr/X11R6/lib -lXm -lXp" LIBDIR="/usr/lib" CFLAGS="-O -pipe 
> -march=pentiumpro" CXXFLAGS=" -O -pipe -march=pentiumpro" 
> BSD_INSTALL_PROGRAM="install -c -s -o root -g wheel -m 555"  
> BSD_INSTALL_SCRIPT="install -c -o root -g wheel -m 555"  
> BSD_INSTALL_DATA="install -c -o root -g wheel -m 444"  
> BSD_INSTALL_MAN="install -c -o root -g wheel -m 444" gmake -f Makefile  
> opengl/qgl.o opengl/qgl_x11.o opengl/moc_qgl.o)
> c++  -c -I/usr/X11R6/include 
> -I/usr/ports/x11-toolkits/qt23/work/qt-2.3.1/include -pthread -D_THREAD_SAFE 
> -I/usr/X11R6/include -DQT_PREFIX=\"/usr/X11R6\" -pipe -O -fno-exceptions  -O 
> -pipe -march=pentiumpro -I/usr/include -D_PTH_H_ -D_PTH_PTHREAD_H_ 
> -frerun-cse-after-loop -fPIC -DQT_BUILTIN_GIF_READER=1 -DQT_XFT 
> -fno-exceptions  -I/usr/local/include  -o opengl/qgl.o opengl/qgl.cpp
> In file included from opengl/qgl.cpp:38:
> opengl/qgl.h:63: GL/gl.h: No such file or directory
> opengl/qgl.h:64: GL/glu.h: No such file or directory
> opengl/qgl.cpp: In method `void QGLWidget::glDraw()':
> opengl/qgl.cpp:1604: `GL_FRONT_LEFT' undeclared (first use this function)
> opengl/qgl.cpp:1604: (Each undeclared identifier is reported only once
> opengl/qgl.cpp:1604: for each function it appears in.)
> opengl/qgl.cpp:1604: implicit declaration of function `int glDrawBuffer(...)'
> opengl/qgl.cpp:1616: implicit declaration of function `int glFlush(...)'
> opengl/qgl.cpp: In method `void QGLWidget::qglColor(const QColor &) const':
> opengl/qgl.cpp:1634: implicit declaration of function `int glColor3ub(...)'
> opengl/qgl.cpp:1636: implicit declaration of function `int glIndexi(...)'
> opengl/qgl.cpp: In method `void QGLWidget::qglClearColor(const QColor &) 
> const':
> opengl/qgl.cpp:1654: `GLfloat' undeclared (first use this function)
> opengl/qgl.cpp:1654: syntax error before `.'
> opengl/qgl.cpp:1659: confused by earlier errors, bailing out
> gmake: *** [opengl/qgl.o] Error 1
> *** Error code 2
> 
> Stop in /usr/ports/x11-toolkits/qt23.
> *** Error code 1
> 
> Stop in /usr/ports/x11-toolkits/qt23.
> *** Error code 1
> 
> Stop in /usr/ports/x11-toolkits/qt23.
> *** Error code 1
> 
> Stop in /usr/ports/x11-toolkits/qt23.
> 
> 
> 
> The archives (-questions, -current, -ports) seem to contain other complaints. 
> 
> Is qt supposed to build with XFree86-4 under -CURRENT? What am I missing ?
> 
> -- Salvo (If I've missed something rivial, many apologies for the noise)
> 
> 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: driver writing newbie

[Kenneth Wayne Culver]

I havn't checked, but I'll probably do that soon.

Ken

On Wed, 25 Jul 2001 [EMAIL PROTECTED] wrote:

> 
> 
> On Wed, 25 Jul 2001, Kenneth Wayne Culver wrote:
> 
> > Well, I could do that, but I'd rather write a complete driver with all the
> > regular interfaces... (open, close, ioctl, and a specific major/minor in
> > the kernel, I'm going to add other chips to this driver eventually) The
> > way you are suggesting just opens /dev/io and uses inb and outb to do some
> > hacking around I believe.
> 
> You are absolutely correct. I was not suggesting this as the proper
> approach, but as a throw-away checkpoint only (the mapping registers
> seemed inconsistent between OS/motherboard combinations). I suppose
> 0x70 is for HWMon and 0x90 is for the SMBus function, in Via 686B.
> 
> Have you checked NetBSD, the seem to have a framework for temperature
> alarms etc.
> 
> 
> Juha
> 
> 


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

Re: driver writing newbie

[Kenneth Wayne Culver]

Well, I could do that, but I'd rather write a complete driver with all the
regular interfaces... (open, close, ioctl, and a specific major/minor in
the kernel, I'm going to add other chips to this driver eventually) The
way you are suggesting just opens /dev/io and uses inb and outb to do some
hacking around I believe.

Ken
On Wed, 25 Jul 2001 [EMAIL PROTECTED] wrote:

> 
> 
> Hello Kenneth,
> 
> shouldn't you use 0x70 for the mapping register of HWMon function ?
> 
> With ABit KT7A (686B)
> 
> # pciconf -l
> hostb1@pci0:7:4:
> class=0x06 card=0x chip=0x30571106 rev=0x40 hdr=0x00
> 
> # pciconf -r pci0:7:4 0x70
> 0x6001 
> 
> and 0x6000 can be used as an i/o-base by a dirty hack to directly inb()
> the monitor data. I stripped it from the NetBSD driver (I think).
> 
> 
> Juha
> 
> 


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

Re: driver writing newbie

[Kenneth Wayne Culver]

On Wed, 25 Jul 2001, Kenneth Wayne Culver wrote:

> Sorry to post to this forum, but I'm not getting any replies from -hackers
> or -questions, and I've looked at the webpages on writing device drivers,
> as well as several other drivers. Here's my problem/question/whatever...
> 
> I am writing a driver right now for the Hardware monitoring features of
> the via686a and via686b south bridge chips. I have documentation and have
> looked at the linux driver to see how things are done. My problem is that
> I've got the chip probing, and I have the pci_read_config telling me that
> my device needs a memory port (what's wierd is that I had to use the base
> register value of the chip instead of PCIR_COMMAND in pci_read_config to
> get it to tell me that it wanted me to set up a port instead of mem which
> is 0x70) So I set up the regid as 0x10 (PCIR_MAPS) as outlined in the

I meant above that the base register is 0x70 for my chip...

> webpage, and SYS_RES_IOPORT as I found in the pci driver for the es137x
> sound chip. I've also tried several combinations. So far the only thing I
> havn't tried is setting the regid to 0x10 (PCIR_MAPS) and using
> SYS_RES_MEMORY instead of SYS_RES_IOPORT (all these combinations are for
> use in bus_alloc_resource). The thing is everything I've tried fails to
> work, so I can't attach my driver because it won't map the resources.
> 
> Can anyone suggest other things I could try to make this work right?
> 
> Ken
> 
> 
> 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

driver writing newbie

[Kenneth Wayne Culver]

Sorry to post to this forum, but I'm not getting any replies from -hackers
or -questions, and I've looked at the webpages on writing device drivers,
as well as several other drivers. Here's my problem/question/whatever...

I am writing a driver right now for the Hardware monitoring features of
the via686a and via686b south bridge chips. I have documentation and have
looked at the linux driver to see how things are done. My problem is that
I've got the chip probing, and I have the pci_read_config telling me that
my device needs a memory port (what's wierd is that I had to use the base
register value of the chip instead of PCIR_COMMAND in pci_read_config to
get it to tell me that it wanted me to set up a port instead of mem which
is 0x70) So I set up the regid as 0x10 (PCIR_MAPS) as outlined in the
webpage, and SYS_RES_IOPORT as I found in the pci driver for the es137x
sound chip. I've also tried several combinations. So far the only thing I
havn't tried is setting the regid to 0x10 (PCIR_MAPS) and using
SYS_RES_MEMORY instead of SYS_RES_IOPORT (all these combinations are for
use in bus_alloc_resource). The thing is everything I've tried fails to
work, so I can't attach my driver because it won't map the resources.

Can anyone suggest other things I could try to make this work right?

Ken


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

Re: dual athlons

[Kenneth Wayne Culver]

I guess it won't be a waste of money then. :-)

On Thu, 7 Jun 2001, Jordan Hubbard wrote:

> From: Kenneth Wayne Culver <[EMAIL PROTECTED]>
> Subject: dual athlons
> Date: Thu, 7 Jun 2001 16:18:13 -0400 (EDT)
> 
> > Just curious, but are there plans to support the EV6 bus that the dual
> > athlon motherboards use? I'm not going to buy that kind of system unless
> > FreeBSD 5 will support it.
> 
> Both FreeBSD 4 and 5 already support it.
> 
> - Jordan
> 


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

Re: dual athlons

[Kenneth Wayne Culver]

Do they still perform better than the regular apic from INTEL though? I
mean it IS an EV6 bus.

On Thu, 7 Jun 2001, Mike Smith wrote:

> > Just curious, but are there plans to support the EV6 bus that the dual
> > athlon motherboards use? I'm not going to buy that kind of system unless
> > FreeBSD 5 will support it.
> 
> FreeBSD works just fine on the dual K7 evaluation systems that AMD have 
> been shipping around.  It seems that they wimped out and licensed Intel's 
> APIC design/interface, presumably because Microsoft wouldn't add OpenAPIC 
> support to NT, so the boards look just like "ordinary" SMP x86 systems.
> 
> -- 
> ... every activity meets with opposition, everyone who acts has his
> rivals and unfortunately opponents also.  But not because people want
> to be opponents, rather because the tasks and relationships force
> people to take different points of view.  [Dr. Fritz Todt]
>V I C T O R Y   N O T   V E N G E A N C E
> 
> 
> 


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

dual athlons

[Kenneth Wayne Culver]

Just curious, but are there plans to support the EV6 bus that the dual
athlon motherboards use? I'm not going to buy that kind of system unless
FreeBSD 5 will support it.

Ken


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

-stable build of kernel fails

[Kenneth Wayne Culver]

With the recent commits to -STABLE (I'm assuming these are MFC that's why
I sent to both freebsd-current and freebsd-stable) having to do with the
ipfw code, I have had a problem compiling the kernel. These are the
errors.

cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -ansi  -nostdinc -I- -I. -I../.. -I../../../include   
-D_KERNEL -include opt_global.h -elf  -mpreferred-stack-boundary=2  vers.c
linking kernel
ip_fw.o: In function `ip_fw_chk':
ip_fw.o(.text+0xff7): undefined reference to `INADDR_TO_IFP'
ip_fw.o(.text+0x1017): undefined reference to `INADDR_TO_IFP'
*** Error code 1

Before anyone asks, I did a make depend first, and I used config -r
instead of config when config'ing my kernel. 

Did I miss a message or something saying that I need something new in my
kernel for firewalls?

Ken


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

Re: HEADSUP! change to atapi-cd driver and burncd

[Kenneth Wayne Culver]

> This is because some sloppy firmware coders hasn't implemented the
> "test unit ready" command proberly, it return ready no matter what
> state the drive is in :( I've gotten ahold of one burner that has this
> problem and I'm trying to come up with a fix for it...

Is this the same problem I was having with my NEC burner?

Ken



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

Re: HEADS UP: I386_CPU

[Kenneth Wayne Culver]

OH ok, just curious how that was going to work.


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

On Tue, 16 Jan 2001, Will Andrews wrote:

> On Tue, Jan 16, 2001 at 09:16:14AM -0500, Kenneth Wayne Culver wrote:
> > Wont this make installing using sysinstall a bit hard? I know the generic
> > kernel includes all the CPU lines, so that all cpu's are recognized... so
> > are you going to just take this line out of the generic kernel, and have a
> > special kern.flp disk with a generic kernel that only has the i386 support
> > in it?
> 
> I don't think it's worth the effort.  By the time 5.0-RELEASE goes out,
> the 386 will have been around for over 10 years (actually I think it has
> already reached that point and gone beyond).  There are not likely to be
> many more installs of FreeBSD on 386's, let alone 5.x installs.
> 
> People who *really* want to install 5.x on a 386 can generate their own
> kernel and such.
> 
> -- 
> wca
> 



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

Re: HEADS UP: I386_CPU

[Kenneth Wayne Culver]

Wont this make installing using sysinstall a bit hard? I know the generic
kernel includes all the CPU lines, so that all cpu's are recognized... so
are you going to just take this line out of the generic kernel, and have a
special kern.flp disk with a generic kernel that only has the i386 support
in it?


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

On Tue, 16 Jan 2001, Peter Wemm wrote:

> I've requested a change for UPDATING:
> 
>   The kerrnel option I386_CPU is now mutually exclusive with the
>   other cpu types. If you have an i386 system, be sure that it
>   only had this line.  Remove it for all other configurations.
> 
> Note that this does not remove i386 support.  The actual commit message
> follows:
> 
>   Modified files:
> sys/i386/confNOTES 
> sys/i386/i386identcpu.c machdep.c pmap.c support.s 
> sys/pc98/confGENERIC 
> sys/pc98/i386machdep.c 
>   Log:
>   Stop doing runtime checking on i386 cpus for cpu class.  The cpu is
>   slow enough as it is, without having to constantly check that it really
>   is an i386 still.  It was possible to compile out the conditionals for
>   faster cpus by leaving out 'I386_CPU', but it was not possible to
>   unconditionally compile for the i386.  You got the runtime checking whether
>   you wanted it or not.  This change makes I386_CPU mutually exclusive with
>   the other cpu types, and tidies things up a little in the process.
>   
>   Reviewed by:  alfred, markm, phk, benno, jlemon, jhb, jake, grog, msmith,
> jasone, dcs, des (and a bunch more people who encouraged it)
>   
> Cheers,
> -Peter
> 
> 
> 
> 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: pmtimer

[Kenneth Wayne Culver]

Yeah, that's what I thought. A while back someone sent me some patches
that fix the broken statclock and make it work on laptops, I can't
remember his name right now. However those patches are against FreeBSD
4.1-RELEASE, and I'm not sure if they'd work for -CURRENT. I suppose I
could do without the statclock for now, but it'd be nice to have :-)




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

On Wed, 10 Jan 2001, Mitsuru IWASAKI wrote:

> Hi,
> 
> > I'm not sure what pmtimer is supposed to do. Isn't it supposed to give
> > support for the broken statclock on laptops? I saw my friend running 4.1
> > with some patches that allowed him to use the statclock (and the rtc
> > device showed up in systat -vm 2) On my laptop, pmtimer doesn't appear to
> > do anything; and I couldn't find a manpage on it
> 
> Please refer to src/UPDATING for -current.
> The new pmtimer device is necessary for laptops.  Failure to
> include the device will cause suspended laptops losing time
> when they resume.
> 
> Currently pmtimer won't solve the broken statclock problem...
> The timer related code at suspend/resume time have been moved from APM
> to pmtimer so that ACPI (includes new power management system) use
> pmtimer at sleep/wakeup time as well.
> 
> Thanks
> 



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

pmtimer

[Kenneth Wayne Culver]

I'm not sure what pmtimer is supposed to do. Isn't it supposed to give
support for the broken statclock on laptops? I saw my friend running 4.1
with some patches that allowed him to use the statclock (and the rtc
device showed up in systat -vm 2) On my laptop, pmtimer doesn't appear to
do anything; and I couldn't find a manpage on it



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



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

Re: YES! laptop installing

[Kenneth Wayne Culver]

I'm using a 3ccfe575ct-d, it works great, I just installed using it by
making my own GENERIC kernel with the cardbus stuff on it, and putting it
on an install boot floppy instead of the one that normally comes on
it. I'm not sure the pmtimer is working though, and I keep getting
dmesg: malloc failed


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

On Wed, 10 Jan 2001, Mark Murray wrote:

> > This is to let everyone know that right now as I type I am setting up
> > FreeBSD to start downloading over my cardbus ethernet card. It seems to
> > work great except it doesn't beep when the card enables, but that's fine
> > with me. :-)
> 
> What card?
> 
> My Netgear FA510 (dc0) probes (sorta) but comes up with a crazy
> MAC address, and then doesn't work. It doesn't even go UP.
> 
> MAC=00:00:80:00:00:80, FWIW.
> 
> M
> -- 
> Mark Murray
> Warning: this .sig is umop ap!sdn
> 



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

YES! laptop installing

[Kenneth Wayne Culver]

This is to let everyone know that right now as I type I am setting up
FreeBSD to start downloading over my cardbus ethernet card. It seems to
work great except it doesn't beep when the card enables, but that's fine
with me. :-)


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



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

Re: cardbus installs on -current

[Kenneth Wayne Culver]

oh ok, sounds good then... I'll definitly try it out soon then.


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

On Sun, 7 Jan 2001, Warner Losh wrote:

> In message <[EMAIL PROTECTED]> Kenneth Wayne 
>Culver writes:
> : on another note, did you ever get a chance to look at that code that
> : supposedly fixes a broken statclock? It is a patch against 4.1-RELEASE I
> : believe. I could still find it for you if you want.
> 
> I believe that those issues have been fixed with the pmtimer device.
> 
> Warner
> 



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

Re: cardbus installs on -current

[Kenneth Wayne Culver]

on another note, did you ever get a chance to look at that code that
supposedly fixes a broken statclock? It is a patch against 4.1-RELEASE I
believe. I could still find it for you if you want.


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

On Sun, 7 Jan 2001, Warner Losh wrote:

> In message <[EMAIL PROTECTED]> Kenneth Wayne 
>Culver writes:
> : Is the cardbus stuff in the GENERIC kernel, or will I have to change it
> : and build my own release or custom sysinstall?
> 
> You'll have to build a NEWCARD kernel, and put it on the install disk.
> 
> Warner
> 



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

Re: cardbus installs on -current

[Kenneth Wayne Culver]

Alright, will do.


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

On Sun, 7 Jan 2001, Warner Losh wrote:

> In message <[EMAIL PROTECTED]> Kenneth Wayne 
>Culver writes:
> : Is the cardbus stuff in the GENERIC kernel, or will I have to change it
> : and build my own release or custom sysinstall?
> 
> You'll have to build a NEWCARD kernel, and put it on the install disk.
> 
> Warner
> 



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

Re: cardbus installs on -current

[Kenneth Wayne Culver]

> : is installing FreeBSD-CURRENT with sysinstall using a cardbus supported
> : card (such as a 3com cardbus 3cfe575 or something) working yet? Just
> : wondering because I want to get windows off my laptop, and this will bring
> : me one step closer... (with support for my ess maestro3 chip being the
> : last step)
> 
> I don't think anybody has ever gone down this path.  If you do, please
> drop a note to -current and/or -mobile telling about your woes and
> wonders.  I'd suspect that it would just work *IF* the card probes
> before sysinstall's device harvesting mechanism kicks in.
> 
> Of course, pccardd will not start, but don't worry too much about that.
> 
Is the cardbus stuff in the GENERIC kernel, or will I have to change it
and build my own release or custom sysinstall?

Ken



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

cardbus installs on -current

[Kenneth Wayne Culver]

is installing FreeBSD-CURRENT with sysinstall using a cardbus supported
card (such as a 3com cardbus 3cfe575 or something) working yet? Just
wondering because I want to get windows off my laptop, and this will bring
me one step closer... (with support for my ess maestro3 chip being the
last step)

Ken



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

kernel panics in 4.2

[Kenneth Wayne Culver]

I sent this message to -questions earlier, but nobody seems to know about
my problem:

I just recently tried putting an adaptec 2940w SCSI controller into my
FreeBSD machine (running -STABLE cvsupped and recompiled every night at
1:30AM) and since including the driver in my kernel I've noticed some
random panics. Most of the time they occur during heavy disk activity, and
usually only when I'm running X (hence the reason I couldn't tell you the
panic message). Even wierder still, I don't even have any SCSI devices
connected yet; I'm using only IDE disks connected via the motherboard's
builtin ATA66. I have also searched the various FreeBSD mailinglist
archives and found some people with the same problems I was having, but no
solutions. Crashes do not occur in Windows with this configuration (at
least not any more than usual :-) ) and when I take the ahc driver out of
the kernel, the panics stop. I've included my dmesg -v output and my
kernel config file, please let me know if anything else is needed.

Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.2-STABLE #0: Fri Dec  1 11:55:01 EST 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/MYKERNEL
Calibrating clock(s) ... TSC clock: 800028138 Hz, i8254 clock: 1193181 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254"  frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x642  Stepping = 2
  
Features=0x183f9ff
  AMD Features=0xc044<,AMIE,DSP,3DNow!>
Data TLB: 24 entries, fully associative
Instruction TLB: 16 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative
real memory  = 134152192 (131008K bytes)
Physical memory chunk(s):
0x1000 - 0x0009, 651264 bytes (159 pages)
0x0035d000 - 0x07fe7fff, 130592768 bytes (31883 pages)
avail memory = 127324160 (124340K bytes)
bios32: Found BIOS32 Service Directory header at 0xc00faf90
bios32: Entry = 0xfb400 (c00fb400)  Rev = 0  Len = 1
pcibios: PCI BIOS entry at 0xb430
pnpbios: Found PnP BIOS data at 0xc00fbf00
pnpbios: Entry = f:bf30  Rev = 1.0
Other BIOS signatures found:
ACPI: 000f7ad0
Preloaded elf kernel "kernel" at 0xc0337000.
Preloaded elf module "if_xl.ko" at 0xc03370a8.
Preloaded elf module "miibus.ko" at 0xc0337148.
Preloaded elf module "usb.ko" at 0xc03371e8.
Preloaded elf module "ums.ko" at 0xc0337284.
Preloaded elf module "bktr_mem.ko" at 0xc0337320.
Preloaded elf module "bktr.ko" at 0xc03373c0.
Preloaded elf module "agp.ko" at 0xc033745c.
bktr_mem: memory holder loaded
Pentium Pro MTRR support enabled
pci_open(1):mode 1 addr port (0x0cf8) is 0x80003840
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=03051106)
pcib-: pcib0 exists, using next available unit number
apm0:  on motherboard
apm: found APM BIOS v1.2, connected at v1.2
npx0:  on motherboard
npx0: INT 16 interface
pci_open(1):mode 1 addr port (0x0cf8) is 0x
pci_open(1a):   mode1res=0x8000 (0x8000)
pci_cfgcheck:   device 0 [class=06] [hdr=00] is there (id=03051106)
pcib0:  on motherboard
found-> vendor=0x1106, dev=0x0305, revid=0x02
class=06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
map[10]: type 1, range 32, base d800, size 26
found-> vendor=0x1106, dev=0x8305, revid=0x00
class=06-04-00, hdrtype=0x01, mfdev=0
subordinatebus=1secondarybus=1
found-> vendor=0x1106, dev=0x0686, revid=0x22
class=06-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
found-> vendor=0x1106, dev=0x0571, revid=0x10
class=01-01-8a, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
map[20]: type 1, range 32, base d000, size  4
found-> vendor=0x1106, dev=0x3038, revid=0x10
class=0c-03-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=d, irq=10
map[20]: type 1, range 32, base d400, size  5
found-> vendor=0x1106, dev=0x3038, revid=0x10
class=0c-03-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=d, irq=10
map[20]: type 1, range 32, base d800, size  5
found-> vendor=0x1106, dev=0x3057, revid=0x30
class=06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
found-> vendor=0x109e, dev=0x036e, revid=0x02
class=04-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
intpin=a, irq=10
map[10]: type 1, range 32, base df002000, size 12
foun

2 patches for via kt133 agp stuff.

[Kenneth Wayne Culver]

I have included two very small patches that identify the via kt133 agp
stuff on the athlon motherboards. I think the messages are ok, but if not,
somebody change them. :-)

--- pci/agp_via.c   Wed Jul 19 05:48:04 2000
+++ pci/agp_via.c.new   Fri Nov  3 14:50:58 2000
@@ -70,6 +70,8 @@
return ("VIA 82C598 (Apollo MVP3) host to PCI bridge");
case 0x06911106:
return ("VIA 82C691 (Apollo Pro) host to PCI bridge");
+   case 0x03051106:
+   return ("VIA VT8363 (KT133) host to PCI bridge");
};
 
if (pci_get_vendor(dev) == 0x1106)

--- pci/pcisupport.cWed Nov  1 14:19:36 2000
+++ pci/pcisupport.c.newFri Nov  3 14:51:06 2000
@@ -698,6 +698,8 @@
/* VIA Technologies -- vendor 0x1106 */
case 0x85981106:
return ("VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge");
+   case 0x83051106:
+   return ("VIA VT8363 (KT133) PCI-PCI (AGP) bridge");
 
/* AcerLabs -- vendor 0x10b9 */
/* Funny : The datasheet told me vendor id is "10b8",sub-vendor */





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

ata problems, nevermind

[Kenneth Wayne Culver]

Wierd, I turned the computer off and turned it back on again and the
problem is solved... sorry bout that.

Ken



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

wierd ata driver problem

[Kenneth Wayne Culver]

with a -STABLE as of last night at 1:30 AM EST the ata driver refuses to
configure my DVD drive. Here is the output of a dmesg:

ad0: 8063MB  [16383/16/63] at ata0-master UDMA33
ad1: 13029MB  [26473/16/63] at ata1-master UDMA66
ad2: 14655MB  [29777/16/63] at ata1-slave UDMA66
ata0-slave: <\M-vO\M-wH\M^?B\M-w
\M-vV\M-v-\M-vO\M^? \M-wD\M^?M\M-w2\M-w2\M-v \M
-v \M-v \M-v \M-v \M-v \M-v \M-v/\M-wR\M-v2\M-v \M-v> Unknown device - NO
DRIVER
!

This is quite wierd because it was working before this.. 
here are some other relavent lines from my dmesg

atapci0:  port 0xd000-0xd00f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0

Thanks

Ken



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

Re: docs for via kt133 south bridge

[Kenneth Wayne Culver]

cool, thanks.


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

On Tue, 31 Oct 2000, Soren Schmidt wrote:

> It seems Kenneth Wayne Culver wrote:
> > > I think one of our Japanese friends has been trying to get these docs
> > > from VIA. With little luck it seems.
> > 
> > Hrmm, well I'll send a messege or something over to VIA... I'm going to
> > make this driver in such a way that it would be easy to add more drivers
> > for other hwmon stuff in the future...
> 
> Hmm, I have the docs for the '686 chip, I'll see if it includes the
> monitoring stuff...
> 
> -Søren
> 



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

Re: docs for via kt133 south bridge

[Kenneth Wayne Culver]

> I think one of our Japanese friends has been trying to get these docs
> from VIA. With little luck it seems.

Hrmm, well I'll send a messege or something over to VIA... I'm going to
make this driver in such a way that it would be easy to add more drivers
for other hwmon stuff in the future...
Ken



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

docs for via kt133 south bridge

[Kenneth Wayne Culver]

I was wondering if any of the developers here had any docs for the via
kt133 south bridge. I need the docs so that I can write a driver for the
hardware monitoring features of this chip... I looked on via's website,
but the docs there are incomplete...

Ken



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

RE: -current grinds exceeding slow

[Kenneth Wayne Culver]

I use 0.85, I had some wierd problems with it in -CURRENT. I've moved down
to 4.1.1-STABLE till some of this stuff in -CURRENT cools down.


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

On Fri, 13 Oct 2000, Daniel O'Connor wrote:

> 
> On 12-Oct-00 Bob Bishop wrote:
> > >It's not.  My current box that is having problems has an fxp0 card.
> > >BTW, what speed is your processor?  I'm curious because the PPro 200
> > >I have here is having problems, but the PIII-700 isn't very affected.
> >  Try removing SMP_DEBUG from your config (see
> >  Message-ID: <[EMAIL PROTECTED]>
> >  from Jason Evans on this thread).
> 
> That worked for me...
> 
> Does anyone here run the really new version of Licq?
> 
> I know it sounds dumb, but it seems that if I run it and do some reasonably
> heavy disk, processes start getting stuck in things like vnlock, inode and
> ffsvgt...
> 
> ---
> Daniel O'Connor software and network engineer
> for Genesis Software - http://www.gsoft.com.au
> "The nice thing about standards is that there
> are so many of them to choose from."
>   -- Andrew Tanenbaum
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



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

Re: TI1225 CardBus controller

[Kenneth Wayne Culver]

It doesn't work for cardbus.


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

On Thu, 5 Oct 2000, Julian Elischer wrote:

> Blaz Zupan wrote:
> 
> > 
> > Could somebody who has a laptop with a TI1225 PC card controller chip please
> > contact me? My idea currently is to print out the values of important chip
> > registers on a laptop and on a desktop and check what the differences
> > are. This way I may be able to find out what the driver is missing out in the
> > initialization.
> > 
> 
> The Dell Inspiron 7500 has one..
> works just fine..
> 
> pcic-pci0:  at device 4.0 on pci0
> pcic-pci0: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr
> save][FUNC p
> ci int + CSC serial isa irq]
> pcic-pci1:  at device 4.1 on pci0
> pcic-pci1: TI12XX PCI Config Reg: [ring enable][speaker enable][pwr
> save][FUNC p
> ci int + CSC serial isa irq]
> ...
> pccard: card inserted, slot 0
> sio4 at port 0x2e8-0x2ef irq 9 slot 0 on pccard0
> sio4: type 16550A
> 
> -- 
>   __--_|\  Julian Elischer
>  /   \ [EMAIL PROTECTED]
> (   OZ) World tour 2000
> ---> X_.---._/  presently in:  Perth
> v
> 
> 
> 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: ESS1879 hwptr went backward?

[Kenneth Wayne Culver]

-CURRENT as of the smpng commits is really unstable... it's even somewhat
unstable before that (I was having crashes on heavy disk activity even at
the smpng commit, which could've been just my lack of knowledge of cvs and
screwing up my source tree, but that's what was happening.)


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

On Wed, 27 Sep 2000, Karl M. Joch wrote:

> Notebook: KAPOK 8700 (sold under different brands) 233Mhz MMX, 128 MB, 4GB, ESS 1879 
>sound:
> 
> the ESS 1879 is correctly detected when booting. also cat /dev/sndstat shows up ESS 
>1878 irq5 io 240
> 1:3 (1p:1r). also tried it with using only one DMA.
> 
> but when trying to play ( cat somesound.au > /dev/audio) i get the message:
> 
> hwptr went backwards 0->4092
> 
> and the system crashes hard. only power off possible. i havnt used sound for a 
>longer time, but i am
> sure in 3.4 it has played with pcm.
> 
> running Current of 26th Sep.
> 
> --
> 
> my open problems:
> 
> reboot & shutdown -r hangs the box. (shutdown works, after pressing a key i see 
>rebooting, then
> screen is black and box hangs)
> 
> staroffice 52 works fine under KDE2 except when having a network connection (mail, 
>www) the
> statusline says making connection to somehost (netstat shows a connection) and it 
>waits forever.
> 
> vmware and serial: when i run the nokia pc suite for the communicator on NT/vmware 
>and connect to
> the mobile i can see the data. small transfers works fine. when trying to do a 
>backup it looks like
> there is a communication problem when sending more data. parts of the data are 
>transfered but the it
> displays an error. as usual without any hints under windows. already slowed down to 
>9600. no
> success. browsing the gsm fones data works.
> 
> there is one message when booting: isa0: too many dependant configs (8).   ??
> --
> 
> thanks for any tips.
> 
> Karl
> 
> 
> 
> 
> _
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> 
> 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: -CURRENT crashes under heavy disk activity

[Kenneth Wayne Culver]

Well, I downgraded to PRE_SMPNG and it still crashes on heavy disk
activity.


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

On Mon, 25 Sep 2000, Stanislav Grozev wrote:

> On Fri, Sep 22, 2000 at 03:37:32PM -0400, Kenneth Wayne Culver wrote:
> > I will try to build a debug kernel, and get a backtrace of what's
> > happening to send to the list, but basically what happened is that I was
> > running a cvsup of the cvs source repository and the ports repository and
> > it just crashed and rebooted (I'm doing this remotely, so I can't really
> > catch any messeges that get sent to the screen right now, not until I go
> > home from work). The second time it happened was doing the cvs update of
> > my source tree and ports tree, and it just crashed and rebooted.. I will
> > make a debug kernel and do a backtrace and send it as soon as I possibly
> > can.
> 
> i've experienced the same things: -CURRENT crashes on heavy disk activity,
> such as rm -rf /usr/ports or cvsup/anoncvs. it crashesh hard - no panic,
> just freezes... downgrading to PRE_SMPNG fixes it.
> 
> -tacho
> 
> --
>[i don't follow] | [http://daemonz.org/ || [EMAIL PROTECTED]]
>[everything should be made as simple as possible, but no simpler]
>0x44FC3339 || [02B5 798B 4BD1 97FB F8DB 72E4 DCA4 BE03 44FC 3339]
> 



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

Re: -CURRENT crashes under heavy disk activity

[Kenneth Wayne Culver]

I see.. just cvs update src/sys/dev/ata or something like that I
guess.. :-) I'll probably do that then.


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

On Fri, 22 Sep 2000, Soren Schmidt wrote:

> It seems Kenneth Wayne Culver wrote:
> > Alright, I think I may just do that too... I was going to try to tough it
> > out... but it looks like that just won't work I wish there was some
> > way to get the other changes without getting the SMP stuff though.
>  
> You update the ata driver to the lastest no probs that I know :)
> 
> -Søren
> 



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

Re: -CURRENT crashes under heavy disk activity

[Kenneth Wayne Culver]

Alright, I think I may just do that too... I was going to try to tough it
out... but it looks like that just won't work I wish there was some
way to get the other changes without getting the SMP stuff though.


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

On Fri, 22 Sep 2000, Michael Reifenberger wrote:

> On Fri, 22 Sep 2000, Kenneth Wayne Culver wrote:
> ...
> > To: [EMAIL PROTECTED]
> > Subject: -CURRENT crashes under heavy disk activity
> This is a well known issue.
> See the -current archive for more information.
> Search for "vmstat" and "FFS".
> 
> Bye!
> 
> Michael Reifenberger
> ^.*Plaut.*$, IT, R/3 Basis, GPS
> 
> 



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

-CURRENT crashes under heavy disk activity

[Kenneth Wayne Culver]

I will try to build a debug kernel, and get a backtrace of what's
happening to send to the list, but basically what happened is that I was
running a cvsup of the cvs source repository and the ports repository and
it just crashed and rebooted (I'm doing this remotely, so I can't really
catch any messeges that get sent to the screen right now, not until I go
home from work). The second time it happened was doing the cvs update of
my source tree and ports tree, and it just crashed and rebooted.. I will
make a debug kernel and do a backtrace and send it as soon as I possibly
can.

Ken



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

fdc problem

[Kenneth Wayne Culver]

as of a few days ago, for some reason my floppy drive controller does not
probe right with -CURRENT... I've attached a dmesg, a kernel config, and
my hints file as kernstuff.tar 

Please let me know if I've made some dumb mistake or something in my
configs... 

Kenneth Culver

 kernstuff.tar

Re: new idle_proc() makes my laptop very hot

[Kenneth Wayne Culver]

My system fans always stay on... but again this is not in a laptop .. it
is on my regular pc... 


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

On Thu, 21 Sep 2000, Mike Smith wrote:

> > My laptop does seem to run *MUCH* warmer than before as well.  It runs
> > hot to begin with, but with the latest kernels it runs really hot.  It
> > used to get this hot only when I compiled -j 4.  I don't have ACPI
> > enabled and am using UP kernel.  There really needs to be a HLT in the
> > idle loop to keep idle machines cools.
> 
> If I remember from a discussion with John Baldwin, the reason we don't do 
> this (yet) is that HLT only wakes up when you take an interrupt, and 
> there are cases where we can't guarantee that we'll take an interrupt in 
> order to get us out of the HLT.
> 
> > The thermal management code, iirc, works in conjunction with this by
> > lower the clock rate when things aren't too loaded, but that is a
> > fairly complex thign to wait for.  It also seems to help mostly on
> > lightly loaded machines.  HLT helps more than you'd otherwise
> > think...c
> 
> HLT helps a lot, yes, but the thermal management code is responsible for 
> running the system fan(s) in ACPI mode as well as throttling the CPU.  In 
> some cases, that's a real issue (eg. I'm building the world now and 
> extremely worried about how hot this system is because I forgot to turn 
> ACPI off first. 8)
> 
> -- 
> ... every activity meets with opposition, everyone who acts has his
> rivals and unfortunately opponents also.  But not because people want
> to be opponents, rather because the tasks and relationships force
> people to take different points of view.  [Dr. Fritz Todt]
> 
> 
> 
> 
> 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 idle_proc() makes my laptop very hot

[Kenneth Wayne Culver]

I don't have it enabled... I am not even on my laptop with
-CURRENT... this is on my regular PC... and I'm taking my thermal readings
by banging around on some memory addys through /dev/io with a little hack
of a program I wrote as a windowmaker dockapp for this purpose... 


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

On Thu, 21 Sep 2000, Mike Smith wrote:

> > I can second this... on my PC the cpu used to run around about 84 degrees
> > F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F
> > while the case runs at 80 degrees F.
> 
> While you're tinkering with SMPng, be VERY SURE that you do not have acpi 
> enabled (ie. make sure it's not in your kernel config).  We're not yet 
> handling thermal management, and this *will* hurt you.
> 
> -- 
> ... every activity meets with opposition, everyone who acts has his
> rivals and unfortunately opponents also.  But not because people want
> to be opponents, rather because the tasks and relationships force
> people to take different points of view.  [Dr. Fritz Todt]
> 
> 
> 



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

Re: new idle_proc() makes my laptop very hot

[Kenneth Wayne Culver]

I can second this... on my PC the cpu used to run around about 84 degrees
F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F
while the case runs at 80 degrees F.


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

On Fri, 22 Sep 2000, Takaya Ogawa wrote:

> Hi.
> 
> After new idle_proc() committed to the tree, my laptop
> become very hot as if under heavy cpu load even when
> cpu is actually 95%~ idle.
> 
> If I understand collectly, idle_proc() doesn't contain
> any HLT instruction in i386 UP case which former
> idle() had. 
> 
> Attached patch adds back the HLT in i386 UP case and
> seems to fix my problem, although I'm totally
> unfamiliar with SMP nor alpha.
> 
> Other than that, current runs quite fine in normal
> operation here.
> 
> Thanks.
> 
> --
> Takaya Ogawa
> [EMAIL PROTECTED]
> 
> 



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

Re: SMPng feedback

[Kenneth Wayne Culver]

> OK - its not my random driver, then :-).
> 
Well, unless your random driver is not attached to the ums device... It
does something when I use the mouse attached to the psm device... and the
mouse is still jumpy.

Ken



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

Re: SMPng feedback

[Kenneth Wayne Culver]

Personally, the whole system seems a bit sluggish with the SMPng stuff
there... I'm assuming this will be fixed later.


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

On Tue, 19 Sep 2000, Alexander Leidinger wrote:

> On 18 Sep, Kenneth Wayne Culver wrote:
> 
> > 1) When I'm playing music (mp3), and I move the mouse or move a window in
> > X, the sound stutters and I get a pcm0: hwptr went backwards x -> y (where
> > x and y are different numbers).
> 
> I see this too.
> 
> If I use xmms instead of mpg123 I didn't need to move the mouse. Perhaps
> something interrupt related. I see alot (more than usual) of interrupts
> in top (if the displayed information is correct). But perhaps this is
> just an "I want to see something different" experience, I have no
> similiar system to compare with.
> 
> Bye,
> Alexander.
> 
> -- 
>   The best things in life are free, but the
> expensive ones are still worth a look.
> 
> http://www.Leidinger.net   Alexander @ Leidinger.net
>   GPG fingerprint = 7423 F3E6 3A7E B334 A9CC  B10A 1F5F 130A A638 6E7E
> 
> 



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

Re: SMPng feedback

[Kenneth Wayne Culver]

IT's new as of last night. There is a random there, but it's not doing
anything when I move the mouse.


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

On Tue, 19 Sep 2000, Mark Murray wrote:

> > 1) When I'm playing music (mp3), and I move the mouse or move a window in
> > X, the sound stutters and I get a pcm0: hwptr went backwards x -> y (where
> > x and y are different numbers).
> > 
> > 2) the mouse is quite jumpy in X, especially while there is high cpu
> > usage. I have tried to use both the usb mouse and the psm mouse (I have a
> > usb to psm adapter) and the behaviour is the same with all mice I've
> > tried. ( a logitec optical mouse, and a ms intellimouse with the ball,
> > not optical) 
> 
> How old is your build? Do you have the kthreaded /dev/random driver?
> (do a top -S and look for a process called "random" when you wiggle
> your mouse).
> 
> M
> --
> Mark Murray
> Join the anti-SPAM movement: http://www.cauce.org
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



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

SMPng feedback

[Kenneth Wayne Culver]

Alright, I've been using -CURRENT with the SMPng changes for a few days
and wanted to give some feedback. 

Overall everything works, although I have been experienceing a few
problems which may or may not be related. 

1) When I'm playing music (mp3), and I move the mouse or move a window in
X, the sound stutters and I get a pcm0: hwptr went backwards x -> y (where
x and y are different numbers).

2) the mouse is quite jumpy in X, especially while there is high cpu
usage. I have tried to use both the usb mouse and the psm mouse (I have a
usb to psm adapter) and the behaviour is the same with all mice I've
tried. ( a logitec optical mouse, and a ms intellimouse with the ball,
not optical) 

These have been the only noticable changes to my system since the
update... I have built the world with the changes in the kernel without
problems so they seem stable enough, just kinda slow.

Ken



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

the SMPng stuff on UP

[Kenneth Wayne Culver]

Alright, I just wanted to let everyone know that I have gotten the SMPng
stuff up and working on my -CURRENT machine, and everything seems to work
fine except the occasional "pcm0: hwptr went backwards x --> y" when I
play sound and then do anything in X that involves moving a window. Oh,
and also, my load avg runs at a constant 1.00 instead of 0.00 when I'm not
using the machine, even though top reports 95-99% cpu idle. 

Ken



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

Re: microuptime() went backwards

[Kenneth Wayne Culver]

Could all this be in any way related to the statclock not working on
certain systems (like my Dell Inspiron)?? Also, could the "rtc" device as
listed in systat -vm not being there (I'm assuming this is the
statclock) be causing scheduling anomalies? I ask because I am trying to
get gaim (multi-threaded, and using gtk which is threaded as well) to work
on my laptop. It works on my desktop (-CURRENT), and on my friend's
desktop (-STABLE) but not on my laptop (-STABLE). Just
wondering... Thanks.


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

On Fri, 8 Sep 2000, Poul-Henning Kamp wrote:

> In message <[EMAIL PROTECTED]>, Mike Smith writes:
> >> > Sep  7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 
>10412, -694583121)y
> >> >
> >> > this is bad.. right ? :-)
> >> 
> >> Well, at any rate it looks very funny.  If this is a laptop, try
> >> building a kernel without apm and see if that helps.
> >
> >It only helps "hide" the problem.  There's either *extremely* bogus data 
> >coming in, or an arithmetic or sequencing error that's allowing a corrupt 
> >timecounter to be seen.
> >
> >It might help to see the negative number as hex...
> 
> I have collected all the emails I've received and I have identified
> at least two different causes:
> 
> There is a bogus i8254 implementation on certain Athlon Mobos, this
> is a non-brainer since they should not use the i8254 but the TSC.
> 
> There are negative numbers coming in from both the i8254 and in a
> few cases from the TSC.  NTIMECOUNTER may be too low for certain
> systems, I'm still waiting for some feedback on that.
> 
> Either way, I have a patch which I need to burn in in my lab, but
> right now I have a hard time getting my SMP box to even print out
> "Copyright..." when it boots :-(
> 
> --
> Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
> [EMAIL PROTECTED] | TCP/IP since RFC 956
> FreeBSD coreteam member | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
> 



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

Re: microuptime() went backwards

[Kenneth Wayne Culver]

If I build the kernel without apm, then there is no clock because the
statclock is broken on this computer.


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

On Fri, 8 Sep 2000, Greg Lehey wrote:

> On Friday,  8 September 2000 at  0:18:07 -0400, Kenneth Wayne Culver wrote:
> > On Fri, 8 Sep 2000, Greg Lehey wrote:
> >
> >> On Thursday,  7 September 2000 at 22:49:30 -0400, Kenneth Wayne Culver wrote:
> >>>> The point I'm making is that we've had these problems before SMPng,
> >>>> and that you can't automatically assume that it's SMPng just because
> >>>> you get the messages.  On the other hand, the 7 digits seem to be a
> >>>> pretty reliable signature.
> >>>
> >>> I'm getting this error while starting XFree86 4.0.1 on my laptop computer,
> >>> and I'm using FreeBSD 4.1-STABLE, so I'm sure it's not the SMP stuff
> >>> that's causing it.
> >>
> >> Right, but you're not getting the 7 digit microsecond count, right?
> >> You should contact phk.
> >
> > Well, here is one of the messeges:
> >
> > Sep  7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -> 
>10412, -694583121)
> >
> > this is bad.. right ? :-)
> 
> Well, at any rate it looks very funny.  If this is a laptop, try
> building a kernel without apm and see if that helps.
> 
> Greg
> --
> Finger [EMAIL PROTECTED] for PGP public key
> See complete headers for address and phone numbers
> 



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

Re: microuptime() went backwards

[Kenneth Wayne Culver]

Well, here is one of the messeges:

Sep  7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980
-> 10412, -694583121)

this is bad.. right ? :-)


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

On Fri, 8 Sep 2000, Greg Lehey wrote:

> On Thursday,  7 September 2000 at 22:49:30 -0400, Kenneth Wayne Culver wrote:
> >> The point I'm making is that we've had these problems before SMPng,
> >> and that you can't automatically assume that it's SMPng just because
> >> you get the messages.  On the other hand, the 7 digits seem to be a
> >> pretty reliable signature.
> >
> > I'm getting this error while starting XFree86 4.0.1 on my laptop computer,
> > and I'm using FreeBSD 4.1-STABLE, so I'm sure it's not the SMP stuff
> > that's causing it.
> 
> Right, but you're not getting the 7 digit microsecond count, right?
> You should contact phk.
> 
> Greg
> --
> Finger [EMAIL PROTECTED] for PGP public key
> See complete headers for address and phone numbers
> 



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

Re: microuptime() went backwards

[Kenneth Wayne Culver]

> The point I'm making is that we've had these problems before SMPng,
> and that you can't automatically assume that it's SMPng just because
> you get the messages.  On the other hand, the 7 digits seem to be a
> pretty reliable signature.
> 
I'm getting this error while starting XFree86 4.0.1 on my laptop computer,
and I'm using FreeBSD 4.1-STABLE, so I'm sure it's not the SMP stuff
that's causing it.

Ken (it's a 600 MHz coppermine based celeron BTW with a mobile BX chipset)

Ken



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

Re: xl driver

[Kenneth Wayne Culver]

the same thing is happening to me, only my pci bus is getting probed 3
times.


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

On Sun, 3 Sep 2000, Warner Losh wrote:

> In message <[EMAIL PROTECTED]> R Joseph Wright writes:
> : Sep  3 13:24:26 manatee /kernel: xl0: <3Com 3c900-COMBO Etherlink XL> port 
>0x6c00-0x6c3f irq 11 at device 9.0 on pci0
> : Sep  3 13:24:26 manatee /kernel: xl1: <3Com 3c900-COMBO Etherlink XL> port 
>0x6c00-0x6c3f irq 11 at device 9.0 on pci2
> 
> Looks like your pci bus is getting probed twice!
> 
> Warner
> 
> 
> 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: mixer no longer works

[Kenneth Wayne Culver]

Nope, I'm not using devfs.


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

On Sat, 2 Sep 2000, Cameron Grant wrote:

> 
> > In -CURRENT cvsupped as of today, the mixer no longer works. anything that
> > tries to access the mixer just says "Operation not permitted"
> 
> using devfs?
> 
> -cg
> 
> 
> 



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

forgot info on soundcard

[Kenneth Wayne Culver]

Alright, I forgot to mention what soundcard I have before, so here goes:

I have an es1371 card. To repeat the problem, with a day-old -current the
mixer doesn't work. I have the sound drivers loaded as a module.

Ken



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

mixer no longer works

[Kenneth Wayne Culver]

In -CURRENT cvsupped as of today, the mixer no longer works. anything that
tries to access the mixer just says "Operation not permitted"




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



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

Re: Possible bug in current?

[Kenneth Wayne Culver]

Yeah, it's supposedly fixed now.


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

On Tue, 1 Aug 2000, Damon Hammis wrote:

> Has anyone else stumbled across this bug in 5.0-CURRENT?  Whenever I try
> to do a tail -f on a text file the system locks up and requires a hard
> reboot.
> 
> Anyone else see anything similar?
> 
> --Damon
> 
>_ _
> |__/|  .~~.
> /o=o'`./  .'
>{o__,   \{
>  / .  . )\  
>  `-` '-' \} 
> .(   _(   )_.' 
>'---.~_ _ _| 
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
> 



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

Re: VM flakiness since Thursday

[Kenneth Wayne Culver]

I'm in the process of tracing it out (in my small amount of spare time) to
see where the problem is, and seeing if I can fix it, although I think
this is over my head :-) I just wanna see if I can do it.


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

On Tue, 1 Aug 2000, Steve Hocking wrote:

> I've been noticing some crashes (the previously reported by others lock stuff) 
> and some random sig 11s - any one else seeing this?
> 
> 
>   Stephen
> -- 
>   The views expressed above are not those of PGS Tensor.
> 
> "We've heard that a million monkeys at a million keyboards could produce
>  the Complete Works of Shakespeare; now, thanks to the Internet, we know
>  this is not true."Robert Wilensky, University of California
> 
> 
> 
> 
> 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: VM flakiness since Thursday

[Kenneth Wayne Culver]

Just the lock stuff here, nothing else. 


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

On Tue, 1 Aug 2000, Steve Hocking wrote:

> I've been noticing some crashes (the previously reported by others lock stuff) 
> and some random sig 11s - any one else seeing this?
> 
> 
>   Stephen
> -- 
>   The views expressed above are not those of PGS Tensor.
> 
> "We've heard that a million monkeys at a million keyboards could produce
>  the Complete Works of Shakespeare; now, thanks to the Internet, we know
>  this is not true."Robert Wilensky, University of California
> 
> 
> 
> 
> 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: keyboard problems with X

[Kenneth Wayne Culver]

My problems are with a previous build of late last week. And my problem
isn't with X. My problem only happens when you start "tail" on some file,
then try to exit. It locks the console solid... neither the mouse nor the
keyboard work.


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

On Sun, 30 Jul 2000, Chuck Robey wrote:

> On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote:
> 
> > The problem I am seeing is that the keyboard isnt even seen.
> > Its useable up until about midway through the boot process,
> > then it goes dead/locks up.  The boot continues fine and the machine
> > is up.  The mouse is usable in X but not the keyboard.  Cant even switch
> > virtual consoles. 
> 
> Is it useable or not, outside of X?  Can you single-user boot and get the
> keyboard working?  I am not clear if it's an X problem or a system
> problem.
> 
> You said you updated your source tree yesterday.  If that was from a
> recent build, then I don't know, but I'm very curious, just how old was
> your previous build?  The config changed really radically maybe 2 months
> ago, so maybe your config file is hosed?
> 
> > 
> > steve
> > 
> > > I have, like when I'm running tail on something, and then I try to ctrl-c
> > > out of it, the whole console locks solid, and I have to reboot. (although
> > > if I was connected to an ethernet, I think I could probably ssh in and
> > > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the
> > > lockmgr problems that were reported earlier.
> > > 
> > > 
> > > =
> > > | Kenneth Culver  | FreeBSD: The best NT upgrade|
> > > | Unix Systems Administrator  | ICQ #: 24767726 |
> > > | and student at The  | AIM: muythaibxr |
> > > | The University of Maryland, | Website: (Under Construction)   |
> > > | College Park. | http://www.wam.umd.edu/~culverk/|
> > > =
> > > 
> > > On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote:
> > > 
> > > > Hi,
> > > > 
> > > > I updated my source tree yesterday (and kernel) and am having some problems
> > > > with my keyboard under X.  Has anyone else noticed anything
> > > > strange.
> > > > 
> > > > steve
> > > > 
> > > > -- 
> > > > Steve Heistand
> > > > [EMAIL PROTECTED]
> > > > 
> > > > 
> > > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > > with "unsubscribe freebsd-current" in the body of the message
> > > > 
> > > 
> > > 
> > 
> > 
> > 
> 
> 
> Chuck Robey| Interests include C & Java programming, FreeBSD,
> [EMAIL PROTECTED]  | electronics, communications, and signal processing.
> 
> New Year's Resolution:  I will not sphroxify gullible people into looking up
> fictitious words in the dictionary.
> 
> 
> 
> 



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

Re: keyboard problems with X

[Kenneth Wayne Culver]

Hrmm, that's even worse than my problem.


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

On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote:

> The problem I am seeing is that the keyboard isnt even seen.
> Its useable up until about midway through the boot process,
> then it goes dead/locks up.  The boot continues fine and the machine
> is up.  The mouse is usable in X but not the keyboard.  Cant even switch
> virtual consoles. 
> 
> steve
> 
> > I have, like when I'm running tail on something, and then I try to ctrl-c
> > out of it, the whole console locks solid, and I have to reboot. (although
> > if I was connected to an ethernet, I think I could probably ssh in and
> > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the
> > lockmgr problems that were reported earlier.
> > 
> > 
> > =
> > | Kenneth Culver  | FreeBSD: The best NT upgrade|
> > | Unix Systems Administrator  | ICQ #: 24767726 |
> > | and student at The  | AIM: muythaibxr |
> > | The University of Maryland, | Website: (Under Construction)   |
> > | College Park.   | http://www.wam.umd.edu/~culverk/|
> > =
> > 
> > On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote:
> > 
> > > Hi,
> > > 
> > > I updated my source tree yesterday (and kernel) and am having some problems
> > > with my keyboard under X.  Has anyone else noticed anything
> > > strange.
> > > 
> > > steve
> > > 
> > > -- 
> > > Steve Heistand
> > > [EMAIL PROTECTED]
> > > 
> > > 
> > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > with "unsubscribe freebsd-current" in the body of the message
> > > 
> > 
> > 
> 
> 
> -- 
> Steve Heistand
> [EMAIL PROTECTED]
> 



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

Re: keyboard problems with X

[Kenneth Wayne Culver]

I have, like when I'm running tail on something, and then I try to ctrl-c
out of it, the whole console locks solid, and I have to reboot. (although
if I was connected to an ethernet, I think I could probably ssh in and
reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the
lockmgr problems that were reported earlier.


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

On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote:

> Hi,
> 
> I updated my source tree yesterday (and kernel) and am having some problems
> with my keyboard under X.  Has anyone else noticed anything
> strange.
> 
> steve
> 
> -- 
> Steve Heistand
> [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

patch for ds1 soundcard

[Kenneth Wayne Culver]

I found on my computer that a ds1 builtin soundcard of type 10 (found in
the file) will not init correctly unless the same 400ms wait is applied to
it that is applied to type 8 cards. I have included a patch to make this
happen. The patch was created against a -STABLE from today, but should not
be too hard to get into -CURRENT as it only modifies one line of code.

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


Index: sys/dev/sound/pci/ds1.c
===
RCS file: /home/ncvs/src/sys/dev/sound/pci/ds1.c,v
retrieving revision 1.8.2.1
diff -r1.8.2.1 ds1.c
295c295
<   if (sc->type == 8)
---
>   if (sc->type == 8 || sc->type == 10)

could someone with committer access commit this?

[Kenneth Wayne Culver]

This is the patch to make my soundcard, a Creative Ensoniq AudioPCI (an
es1371 chip, device id 0x58801274 rev 0x02). Can someone commit it please?


Thanks.



--- es137x.c.oldSun May 28 11:15:14 2000
+++ es137x.cSat Jul  1 23:22:00 2000
@@ -68,6 +68,7 @@
 #define ES1370_PCI_ID 0x50001274
 #define ES1371_PCI_ID 0x13711274
 #define ES1371_PCI_ID2 0x13713274
+#define ES1371_PCI_ID3 0x58801274
 
 #define ES_BUFFSIZE 4096
 
@@ -493,7 +494,7 @@
es->ctrl = 0;
es->sctrl = 0;
/* initialize the chips */
-   if (rev == 7 || rev >= 9) {
+   if (rev == 7 || rev >= 9 || rev == 2) {
 #define ES1371_BINTSUMM_OFF 0x07
bus_space_write_4(es->st, es->sh, ES1371_BINTSUMM_OFF, 0x20);
if (debug > 0) printf("es_init rev == 7 || rev >= 9\n");
@@ -724,7 +725,8 @@
device_set_desc(dev, "AudioPCI ES1370");
return 0;
} else if (pci_get_devid(dev) == ES1371_PCI_ID ||
-  pci_get_devid(dev) == ES1371_PCI_ID2) {
+  pci_get_devid(dev) == ES1371_PCI_ID2 ||
+  pci_get_devid(dev) == ES1371_PCI_ID3) {
device_set_desc(dev, "AudioPCI ES1371");
return 0;
}
@@ -789,7 +791,8 @@
}
 
if (pci_get_devid(dev) == ES1371_PCI_ID ||
-   pci_get_devid(dev) == ES1371_PCI_ID2) {
+   pci_get_devid(dev) == ES1371_PCI_ID2 || 
+   pci_get_devid(dev) == ES1371_PCI_ID3) {
if(-1 == es1371_init(es, pci_get_revid(dev))) {
device_printf(dev, "unable to initialize the card\n");
goto bad;



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

patch to be committed please?

[Kenneth Wayne Culver]

Here is a patch with the changes I made to get my soundcard to work. It
was pretty simple, it was just a matter of one more id that needed to be
added so that the ac97 stuff could be turned on. It was trying to do a
pre-ac97 2.1 init instead of what I should have been doing. Anyway, it
works now. :-)

Here it is:

--- es137x.c.oldSun May 28 11:15:14 2000
+++ es137x.cSat Jul  1 23:22:00 2000
@@ -68,6 +68,7 @@
 #define ES1370_PCI_ID 0x50001274
 #define ES1371_PCI_ID 0x13711274
 #define ES1371_PCI_ID2 0x13713274
+#define ES1371_PCI_ID3 0x58801274
 
 #define ES_BUFFSIZE 4096
 
@@ -493,7 +494,7 @@
es->ctrl = 0;
es->sctrl = 0;
/* initialize the chips */
-   if (rev == 7 || rev >= 9) {
+   if (rev == 7 || rev >= 9 || rev == 2) {
 #define ES1371_BINTSUMM_OFF 0x07
bus_space_write_4(es->st, es->sh, ES1371_BINTSUMM_OFF, 0x20);
if (debug > 0) printf("es_init rev == 7 || rev >= 9\n");
@@ -724,7 +725,8 @@
device_set_desc(dev, "AudioPCI ES1370");
return 0;
} else if (pci_get_devid(dev) == ES1371_PCI_ID ||
-  pci_get_devid(dev) == ES1371_PCI_ID2) {
+  pci_get_devid(dev) == ES1371_PCI_ID2 ||
+  pci_get_devid(dev) == ES1371_PCI_ID3) {
device_set_desc(dev, "AudioPCI ES1371");
return 0;
}
@@ -789,7 +791,8 @@
}
 
if (pci_get_devid(dev) == ES1371_PCI_ID ||
-   pci_get_devid(dev) == ES1371_PCI_ID2) {
+   pci_get_devid(dev) == ES1371_PCI_ID2 || 
+   pci_get_devid(dev) == ES1371_PCI_ID3) {
if(-1 == es1371_init(es, pci_get_revid(dev))) {
device_printf(dev, "unable to initialize the card\n");
goto bad;



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

patches for my new soundcard

[Kenneth Wayne Culver]

I just got the soundcard to work, patches to
/usr/src/sys/dev/sound/pci/ess137x.c are coming in a minute.

Ken



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

more info on sound card

[Kenneth Wayne Culver]

I managed to find a little more info on this chip in my new soundcard. It
is slightly different from a regular es1371... and in linux it even get's
some of its own #defines:

CT5880REV_CT5880_C is it's revision. (or 0x02) and the chip says CT5880 on
it. I'm assuming it's not much different, but so far in the linux driver,
there are a couple of little differences between this chip and the regular
1371. If I get this working, I'll submit whatever I did to the driver to
make it work, but I may need a little help here.

Ken



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

new sound card

[Kenneth Wayne Culver]

Alright, this just bit me in the ass... I just bought a card today
that says "Creative Ensoniq AudioPCI" on the box. Well, as far as I can
tell this card uses the es1371 chip. Well, I did a little digging because
apparently the card's pci device id wasn't in the es137x.c file. So what I
did was I put it in the file, and tried to make it configure as a 1371
chip. However I got an error when I did this:

pcm0:  port 0xe400-0xe43f irq 11 at device 9.0 on pci0
pcm0: ac97 codec invalid or not present (id == 0)

The mixer would not configure with this, and the driver wouldn't attach,
so I went to ac97.c and found the error message, and commented out the
"return ENODEV" statement so that I could make it attach the driver and
see what would happen. Well, when I did that, I got another error in
addition to the 2 above:

pcm0: ac97 codec reports dac not ready

however, the driver attaached, and I can use the mixer devices, and I can
play CD's, but pcm audio still won't play, and there are no errors on the
console when I try to play mp3's or any other kind of sounds. So I guess
my question is:

is anyone working on getting the device with id 0x58801274 (the closest
card originally listed in the file was: 0x50001274) to work? Or does
anyone already have this card working?

Ken



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

Re: What's going on with crypto all of a sudden ?

[Kenneth Wayne Culver]

:-) Well, I didn't know that... That could explain it.


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

On Thu, 29 Jun 2000, Sheldon Hearn wrote:

> 
> 
> On Thu, 29 Jun 2000 10:25:05 -0400, Kenneth Wayne Culver wrote:
> 
> > Hrmm, I think I just read somewhere (/usr/src/UPDATING?) that crypto is
> > required to get a make world to work, and I guess certain other things
> > won't work as well until you rebuild (?) :-) (:-P) 
> 
> You're grasping at straws, since the ssl(8) manual page isn't installed.
> The base system's openssl maintainer still isn't sure what to do about
> the docs. :-)
> 
> Ciao,
> Sheldon.
> 



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

Re: What's going on with crypto all of a sudden ?

[Kenneth Wayne Culver]

Hrmm, I think I just read somewhere (/usr/src/UPDATING?) that crypto is
required to get a make world to work, and I guess certain other things
won't work as well until you rebuild (?) :-) (:-P) 


> > if you're using -CURRENT, it's because you havn't followed the advice
> > about the new randomdev.
> 
> This doesn't explain why it suggests that the user reads a 
> non-existent man page (ssl(8)) :-P
> 
> > =
> > | Kenneth Culver  | FreeBSD: The best NT upgrade|
> > | Unix Systems Administrator  | ICQ #: 24767726 |
> > | and student at The  | AIM: muythaibxr |
> > | The University of Maryland, | Website: (Under Construction)   |
> > | College Park.   | http://www.wam.umd.edu/~culverk/|
> > =
> > 
> > On Wed, 28 Jun 2000, Pascal Hofstee wrote:
> > 
> > > Just now after a new buildworld/installworld i am suddenly getting errors
> > > like the following when trying to use OpenSSH's version 1 protocoll:
> > > 
> > > ssh: no RSA support in libssl and libcrypto.  See ssl(8).
> > > Disabling protocol version 1
> > > Protocol major versions differ: 2 vs. 1
> > > 
> > > 
> > > man 8 sslresults into the following:
> > > No entry for ssl in section 8 of the manual
> > > 
> > > This has been working just fine for months before.
> > > I get the idea it has something to do with the /dev/(random|zero) update.
> > > 
> > > Anyone care to explain this ?
> > > 
> > > -- 
> > >   Pascal Hofstee  < daeron @ shadowmere . student . utwente . nl >
> > >   Managers know it must be good because the programmers hate it so much.
> 
> -- 
> Brian <[EMAIL PROTECTED]>
>      
> Don't _EVER_ lose your sense of humour !
> 
> 
> 



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

Re: What's going on with crypto all of a sudden ?

[Kenneth Wayne Culver]

Nothing to be sorry about... just read a little more carefully :-)


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

On Wed, 28 Jun 2000, Pascal Hofstee wrote:

> On Wed, Jun 28, 2000 at 04:28:24PM -0400, Kenneth Wayne Culver wrote:
> > if you're using -CURRENT, it's because you havn't followed the advice
> > about the new randomdev.
> 
> Stumbled over it right after i sent the email  sorry 
> 
> -- 
>   Pascal Hofstee  < daeron @ shadowmere . student . utwente . nl >
>   Managers know it must be good because the programmers hate it so much.
> 



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

Re: What's going on with crypto all of a sudden ?

[Kenneth Wayne Culver]

if you're using -CURRENT, it's because you havn't followed the advice
about the new randomdev.


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

On Wed, 28 Jun 2000, Pascal Hofstee wrote:

> Just now after a new buildworld/installworld i am suddenly getting errors
> like the following when trying to use OpenSSH's version 1 protocoll:
> 
> ssh: no RSA support in libssl and libcrypto.  See ssl(8).
> Disabling protocol version 1
> Protocol major versions differ: 2 vs. 1
> 
> 
> man 8 sslresults into the following:
> No entry for ssl in section 8 of the manual
> 
> This has been working just fine for months before.
> I get the idea it has something to do with the /dev/(random|zero) update.
> 
> Anyone care to explain this ?
> 
> -- 
>   Pascal Hofstee  < daeron @ shadowmere . student . utwente . nl >
>   Managers know it must be good because the programmers hate it so much.
> 
> 
> 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: Config problems

[Kenneth Wayne Culver]

duh... that was too simple... :-)


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

On Mon, 26 Jun 2000, Peter Wemm wrote:

> Chuck Robey wrote:
> 
> > device  da0 at scbus 0 target 0
> > device  da1 at scbus 0 target 2
> > device  da2 at scbus 1 target 1
> > 
> > device  cd0 at scbus?
> > device  cd1 at scbus?
> 
> Change 'scbus 0' to 'scbus0' and 'scbus 1' to 'scbus1' and the gethints.pl
> script will understand it.
> 
> Cheers,
> -Peter
> --
> Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> "All of this is for nothing if we don't go to the stars" - JMS/B5
> 
> 



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

Re: Config problems

[Kenneth Wayne Culver]

Well, I think maybe you have to put a number in if you want stuff wired
down.. but basically I'm not sure if all the kinks have been worked out
yet...


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

On Sun, 25 Jun 2000, Chuck Robey wrote:

> On Sun, 25 Jun 2000, Kenneth Wayne Culver wrote:
> 
> > Hey chuck, except for the SMP stuff, your config looks mostly like mine (I
> > only have a cpu line for i686) Let me know if there's anything I can do to
> > help though.
> 
> I'm about ready to post again, so this is good timing.
> 
> I got the totally vague warning from gethints.pl to quiet by making my
> disk section look much like the NOTES file.  I then ran it by a brand new
> config, and out spewed more than 25 errors.  The entire section on wiring
> down disks fails, and also all the stuff on npx, even tho that part was
> copied verbatim from NOTES.
> 
> I have an Adaptec dual channel controller on my motherboard, and I have 3
> disks and 2 cdroms, which I want to wire down.  There's lines in the NOTES
> examples whose meanings just make no sense to me.  Let me do a bit of
> quoting:
> 
> [from NOTES]
> hint.scbus.0.at="ahc0"
> hint.scbus.1.at="ahc1"
> hint.scbus.1.bus="0"
> hint.scbus.3.at="ahc2"
> hint.scbus.3.bus="0"
> hint.scbus.2.at="ahc2"
> hint.scbus.2.bus="1"
> hint.da.0.at="scbus0"
> hint.da.0.target="0"
> hint.da.0.unit="0"
> hint.da.1.at="scbus3"
> hint.da.1.target="1"
> hint.da.2.at="scbus2"
> hint.da.2.target="3"
> hint.sa.1.at="scbus1"
> hint.sa.1.target="6"
> 
> 
> What does ``hint.scbus.1.bus="0"'' mean?  Do I have to stick a number
> after the "device ahc" and "device scbus" lines (the NOTES file
> doesn't).  Are there any other oddities I ought to know of?
> 
> 
> Chuck Robey| Interests include C & Java programming, FreeBSD,
> [EMAIL PROTECTED]  | electronics, communications, and signal processing.
> 
> New Year's Resolution:  I will not sphroxify gullible people into looking up
> fictitious words in the dictionary.
> 
> 
> 



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

Re: Config problems

[Kenneth Wayne Culver]

Hey chuck, except for the SMP stuff, your config looks mostly like mine (I
only have a cpu line for i686) Let me know if there's anything I can do to
help though.


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

On Sun, 25 Jun 2000, Chuck Robey wrote:

> I am getting a config error with the new gethints.pl stuff:
> 
> unrecognized config token 1
> 
> This is with a newly cvsupped system, and I checked the version of
> gethints.pl:
> 
> ROOT:/usr/src/sys/i386/conf:472 >cvs status gethints.pl
> ===
> File: gethints.pl   Status: Up-to-date
> 
>Working revision:1.4 Sun Jun 18 01:43:22 2000
>Repository revision: 1.4 /home/ncvs/src/sys/i386/conf/gethints.pl,v
>Sticky Tag:  (none)
>Sticky Date: (none)
>Sticky Options:  (none)
> 
> So I think that's right.  My config file before had worked just fine, but
> as a test, I went thru it and really tried to make it squeaky clean, but
> it didn't seem to get rid of that error.  I don't know if this message
> indicates a fatal problem or just is a leftover printf, there's damned
> little in the way of info in it.
> 
> I don't know, maybe that error message is referring to line 1 of my config
> file?  Here's the start of the config file:
> 
> machine i386
> 
> cpu I586_CPU
> cpu I686_CPU
> ident   CH
> maxusers64
> 
> # Create a SMP capable kernel (mandatory options):
> options SMP # Symmetric MultiProcessor Kernel
> options APIC_IO # Symmetric (APIC) I/O
> 
> If that doesn't do it, I'm attaching the entire config file to this mail.
> 
> Sure would appreciate a hint; I'm not a perl hacker, but if I gotta become
> one to puzzle this out, it's going to take me an long extra while trying
> to get me a new kernel.
> 
> 
> Chuck Robey| Interests include C & Java programming, FreeBSD,
> [EMAIL PROTECTED]  | electronics, communications, and signal processing.
> 
> New Year's Resolution:  I will not sphroxify gullible people into looking up
> fictitious words in the dictionary.
> 
> 
> 
> 
> 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: GENERIC from today does not detect system console on my box

[Kenneth Wayne Culver]

I had a wierder problem yesterday... I followed the new changes to the
kernel config file, and included everything that belonged there, and yet
for some reason, my kernel paniced while probing vga0 with an error number
6. I had to use a fixit floppy to get back into the system and compile a
generic kernel, and from there make a new config file. The wierd part is I
the panicing config and the non-panicing config both looked the
same... (diff showed only differences in whitespace and comments as far as
I could tell. Wierd...


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

On Fri, 16 Jun 2000, Jordan K. Hubbard wrote:

> I tried booting a kernel this morning, just to see Peter's new
> "lean-n-mean" kernel config format in action, and I turned my
> workstation into a headless server in the process. :-)
> 
> Most notably, these former entries were now missing from my dmesg
> output when I logged in remotely and poked around:
> 
> atkbdc0:  at port 0x60,0x64 on isa0
> atkbd0:  irq 1 on atkbdc0
> psm0:  irq 12 on atkbdc0
> psm0: model Generic PS/2 mouse, device ID 0
> vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> sc0:  on isa0
> 
> JFYI...
> 
> - Jordan
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



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

Re: fatal trap 12 after lastest kernel build

[Kenneth Wayne Culver]

Oh ok. well then I have no idea... :-) I thought that could be the
problem...


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

On Thu, 15 Jun 2000, Donn Miller wrote:

> Kenneth Wayne Culver wrote:
> > 
> > did you follow Peter Wemm's instructions on the new config changes?
> 
> Actually, I did.  In fact, I built 2 or 3 kernels after the changes
> went into effect with no problems.  It's just the sources that I
> cvsup'd as of an hour ago that's causing the problems.
> 
> 
> > On Thu, 15 Jun 2000, Donn Miller wrote:
> > 
> > > I just built my kernel from kernel sources as of Thu Jun 15 13:49:59 EDT
> > > 2000, and immediately after the kernel is loaded, I get a "fatal trap
> > > 12: page fault while in supervisor mode".  The uptime was 0s, so
> > > apparently, the boot loader must not like the kernel.  But, I can boot a
> > > kernel from Jun 14 10:25 with the same boot loader.  I did a make depend
> > > all install in /usr/src/sys/boot with the new sources, but still the same
> > > problem.
> > >
> > > Anyone else see this?
> > >
> > > - Donn
> > >
> > >
> > >
> > > 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
> 
> -- 
> - Donn
> 



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

Re: fatal trap 12 after lastest kernel build

[Kenneth Wayne Culver]

did you follow Peter Wemm's instructions on the new config changes?


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

On Thu, 15 Jun 2000, Donn Miller wrote:

> I just built my kernel from kernel sources as of Thu Jun 15 13:49:59 EDT
> 2000, and immediately after the kernel is loaded, I get a "fatal trap
> 12: page fault while in supervisor mode".  The uptime was 0s, so
> apparently, the boot loader must not like the kernel.  But, I can boot a
> kernel from Jun 14 10:25 with the same boot loader.  I did a make depend
> all install in /usr/src/sys/boot with the new sources, but still the same
> problem.
> 
> Anyone else see this?
> 
> - Donn
> 
> 
> 
> 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: Anyone else seeing jumpy mice?

[Kenneth Wayne Culver]

I saw it once or twice in the last couple of weeks, when I'm kicking the
hell out of the CPU (ie compiling something)


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

On Sun, 21 May 2000, Jordan K. Hubbard wrote:

> No, I don't mean rodents who've nibbled on chocolate-covered expresso
> beans, I mean PS/2 mice which fall victim to this new problem:
> 
> May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
> 
> I've seen it for the last few weeks and can only think that something
> must be stomping on the psm driver now (or the driver is missing
> interrupts for reasons of its own).  Anyone else seeing this?
> 
> - Jordan
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



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

pcm static

[Kenneth Wayne Culver]

I was just wondering what the status on the static in the pcm driver on
the SoundBlaster ViBRA16X is... Just in case anyone forgot what I'm
talking about, almost half the time when I start playing an mp3 or an mpg
movie I get static out of the soundcard instead of music. If I keep
restarting the song or movie, eventually I get music instead of static,
but then every time I switch songs I get static about half the time again
when the new song starts. Also, short wav files aren't playing all the way
through again.


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



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

Re: proposed pkg_delete change

[Kenneth Wayne Culver]

Yeah, but some ports and projects don't have the same beginning to their
names which prompted me to make my suggestion.


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

On Tue, 9 May 2000, Doug Rabson wrote:

> On Mon, 8 May 2000, Mike Pritchard wrote:
> 
> > On Mon, May 08, 2000 at 02:10:28AM -0400, Kenneth Wayne Culver wrote:
> > > I have a suggestion for pkg_delete: Very often when I'm deleting a package
> > > (such as kde, after testing the port) I want to delete that package, and
> > > all it's dependancies; instead of going around looking for the
> > > dependancies, I think it would be a nice idea to add an option to
> > > pkg_delete to automatically delete all dependancies that aren't currently
> > > used by anything else. If nobody is interested in doing this, I can do it
> > > when I have some spare time (finals here at school). And then submit
> > > patches.
> > 
> > That would have saved me a *lot* of time about a month ago when I
> > went and weeded out all of my packages when my /usr filled up.
> > I basically did what you are proposing by hand and it took forever.
> > e.g. pkg_delete some_package - oops, it depends on pkg_xxx, delete that,
> > oops, it depends on pkg_xxx2, and so on, when in reality that only
> > reason any of those additional packages were installed were for the
> > original package.
> 
> I just go to /var/db/pkg and type 'pkg_delete kde*' a few times. After a
> while they all get deleted.
> 
> -- 
> Doug Rabson   Mail:  [EMAIL PROTECTED]
> Nonlinear Systems Ltd.Phone: +44 20 8442 9037
> 
> 
> 



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

Re: rc.d startup scripts

[Kenneth Wayne Culver]

> 
> > Yeah, I was just joking, I kinda like some things about SVR4, but I still
> > think it would be nice to keep the option of using some of the regular rc
> > scripts that we have now. Imagine the confusion of the people that have
> > ONLY used FreeBSD when they go in and see rc.d and all it's
> > scripts. Personally I kinda like the rc.d stuff better myself, but I'm
> > just thinking about the average user.
> 
>   What does the average user do with the rc scripts? (BTW, I'm not being
> combative here, just using your letter as an opportunity...) In my
> outline we would still have /etc/rc.conf[.local], which is what the
> average user interacts with now. It's what happens behind the scenes
> that I want to change. The way that the various services get started.
> Instead of the arcane, confusing system of rc* files we have now (most
> of which grew out of necessity, don't get me wrong) we would have a
> system that could be used at startup, and then also used while the
> system is running to upgrade and downgrade individual bits, or groups of
> bits. 
> 
Well, I guess I am not an average user then. I have customized most of my
rc scripts. You are right though, it seems much better to "change what
goes on behind the scenes" because it took me quite a while to learn what
everything we have now did, and it took me only a day or two to figure out
how to use the system you describe (well the back end anyway)

Ken



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

Re: rc.d startup scripts

[Kenneth Wayne Culver]

> > 
> > Just curious, but wouldn't this be FreeSVR4??? :-)
> 
>   I'm going to assume that the smiley means you're joking, but I hope
> that we can stick to discussing this plan on its merits, rather than
> rejecting it out of hand because it's like something that someone else
> is doing.
> 
Yeah, I was just joking, I kinda like some things about SVR4, but I still
think it would be nice to keep the option of using some of the regular rc
scripts that we have now. Imagine the confusion of the people that have
ONLY used FreeBSD when they go in and see rc.d and all it's
scripts. Personally I kinda like the rc.d stuff better myself, but I'm
just thinking about the average user.

Ken



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

Re: rc.d startup scripts

[Kenneth Wayne Culver]

Just curious, but wouldn't this be FreeSVR4??? :-)


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

On Tue, 9 May 2000, Tony Finch wrote:

> Kris Kennaway <[EMAIL PROTECTED]> wrote:
> >On Sun, 7 May 2000, Doug Barton wrote:
> >
> >>I'm going to reply to the system part of this too, replies to this
> >> thread should split off to -current. I have a design in mind for a new
> >> rc system that uses scripts with "start, stop, status" operators to both
> >> upgrade and downgrade services, where "services" are defined as groups
> >> of daemons/programs that work together. For example, "nfs" would be an
> >> example of a service, which would be subdivided into client and server,
> >> etc. 
> >
> >Eivind Eklund made a prototype some time back which addressed this issue -
> >you'd do well to take a look at that one first before reinventing the
> >wheel :)
> 
> Or you could use the system that NetBSD already has working.
> 
> Tony.
> -- 
> f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECTED]
> 381 plastic fruit for a starving nation
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



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

Re: a better idea for package dependencies

[Kenneth Wayne Culver]

Alright, I'll try to do it after I get something working.


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

On Mon, 8 May 2000, Kris Kennaway wrote:

> On Mon, 8 May 2000, Kenneth Wayne Culver wrote:
> 
> > pkg_delete -d package-version (or some other unused switch for dependancy)
> 
> This might be a good option, but there should also be an automatic mode,
> whether or not it's the default.
> 
> > remove pkg_version_dependant [Y] ? y
> > removed!
> > remove pkg_version_dependant2 [Y] ? y
> > 
> > error: some_other_package depends on pkg_version_dependant2!
> 
> pkg_version_dependant2 is required by the following packages:
> foo-1.0
> bar-2.0a
> blee-0.0001
> remove pkg_version_dependant2 [Y] ? y
> 
> 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-current" in the body of the message

Re: a better idea for package dependencies

[Kenneth Wayne Culver]

Actually, it has to do with the pkg_ commands, which I believe are built
when you make world... and aren't part of the ports, so I assumed that
since these are part of -current, and changes would be made to -current,
it's better to send to -current. Sorry for any inconvenience.


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

On Mon, 8 May 2000, David O'Brien wrote:

> On Mon, May 08, 2000 at 02:26:42PM -0400, Kenneth Wayne Culver wrote:
> > Instead of automatically deleteing the dependencies, I think maybe it
> 
> This belongs on [EMAIL PROTECTED], not [EMAIL PROTECTED] has it has
> *nothing* to do with -CURRENT.
> 



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

a better idea for package dependencies

[Kenneth Wayne Culver]

Instead of automatically deleteing the dependencies, I think maybe it
would be better to (with the use of a commandline switch) ask the user
deleting the packages if he/she wants to delete a certain dependency,
without letting the user delete the dependency if some other package also
uses it. (Does this make sense?) For example:

pkg_delete -d package-version (or some other unused switch for dependancy)

remove pkg_version_dependant [Y] ? y
removed!
remove pkg_version_dependant2 [Y] ? y

error: some_other_package depends on pkg_version_dependant2!


prompt>

Is this a good behavior, or should it be more automatic? I like this
because it allows the user to choose if he/she wants to delete certain
dependancies, and won't let them delete those dependancies if something
else also uses them...


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






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

Re: proposed pkg_delete change

[Kenneth Wayne Culver]

Sounds good to me, again, I won't be doing anything for the next 2 weeks
except studying for finals, but as soon as I'm finished, I'll work on the
changes to the pkg_ commands to get the working this way.


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

On 8 May 2000, Satoshi - Ports Wraith - Asami wrote:

>  * From: Kenneth Wayne Culver <[EMAIL PROTECTED]>
> 
>  * dependancies, I think it would be a nice idea to add an option to
>  * pkg_delete to automatically delete all dependancies that aren't currently
>  * used by anything else. If nobody is interested in doing this, I can do it
> 
> Be careful about that "aren't currently used by anything else" part.
> If you already had a port A installed, and then later installed B
> (which just happens to depend on A), you could get A erased when you
> erase B.
> 
> You probably need to change pkg_add too, so that it will note
> somewhere on A's dependency list that it was installed by which port,
> and let pkg_delete check it.
> 
> It usually goes like this:
> 
>  @ install B, pkg_add installs A too, and mark A that it was
>"installed by B"
>  @ deinstall B, pkg_delete checks A, finds the mark and deletes it too
> 
> While, if you had installed A beforehand, it will be like:
> 
>  @ install A
>(...few months pass...)
>  @ install B, nothing special happens re the flag
>  @ deinstall B, pkg_delete checks A and doesn't find the flag, so
>doesn't delete it
> 
> You can also add a flag to pkg_delete to override said check in case
> you know you installed A just for the purpose of installing B.
> 
> If you come up with the file format and patches to pkg_*, I'll modify
> bsd.port.mk so it will DTRT on dependencies installed by "make
> install".
> 
> Satoshi
> 



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

Re: proposed pkg_delete change

[Kenneth Wayne Culver]

> > I have a suggestion for pkg_delete: Very often when I'm deleting a
> package > (such as kde, after testing the port) I want to delete that
> package, and > all it's dependancies; instead of going around looking
> for the > dependancies, I think it would be a nice idea to add an
> option to > pkg_delete to automatically delete all dependancies that
> aren't currently > used by anything else.
> 
> That would be cool, yes.  If you've got the time to do it, I think
> it would be well-worth the effort.

Alright, I'll get on it probably in 2 weeks when finals are over.

Ken



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

proposed pkg_delete change

[Kenneth Wayne Culver]

I have a suggestion for pkg_delete: Very often when I'm deleting a package
(such as kde, after testing the port) I want to delete that package, and
all it's dependancies; instead of going around looking for the
dependancies, I think it would be a nice idea to add an option to
pkg_delete to automatically delete all dependancies that aren't currently
used by anything else. If nobody is interested in doing this, I can do it
when I have some spare time (finals here at school). And then submit
patches.


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



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

Re: high CPU usage by xmms

[Kenneth Wayne Culver]

It was working perfectly about 10 days ago. It stopped working right after
one or two major commits. And also, it's in 5.0-CURRENT, not 4.0


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

On Mon, 1 May 2000, Ted Sikora wrote:

> Kenneth Wayne Culver wrote:
> > 
> > Hmm, I don't know then, I'm using that ViBRA 16X which seems to cause
> > problems a lot.
> > 
> > > 
> > On Sun, 30 Apr 2000, Ted Sikora wrote:
> > 
> > > Kenneth Wayne Culver wrote:
> > > >
> > > > I guess it depends on your soundcard, I'm getting the behavior I'm getting
> > > > with a ViBRA 16X and a kernel as of this morning. This didn't start
> > > > happening until about 4 days ago with a -CURRENT kernel. Maybe you have an
> > > > older -CURRENT.
> > > >
> > > >
> > > I did a make build/installworld and kernel this afternoon after I
> > > cvsup'd(current). I have an original non-pnp SB16.
> > > (Best sounding sound card on the market IMOP)
> > >
> 
> The VibraX used to be the card everyone recommended to stay away from.
> It's not full-duplex. Early on it was hard writing for it (mostly due to
> lack of specs and noise problems). It seems most problems have been
> solved now. Like someone mentioned already
> I think it's a 4.0 problem. Xmms worked perfectly under 3.4 for 
> me too. The eq problem appeared after the upgrades.
> 
> --
> Ted Sikora
> Jtl Development Group 
> [EMAIL PROTECTED]
> 



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

Re: high CPU usage by xmms

[Kenneth Wayne Culver]

Hmm, I don't know then, I'm using that ViBRA 16X which seems to cause
problems a lot.


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

On Sun, 30 Apr 2000, Ted Sikora wrote:

> Kenneth Wayne Culver wrote:
> > 
> > I guess it depends on your soundcard, I'm getting the behavior I'm getting
> > with a ViBRA 16X and a kernel as of this morning. This didn't start
> > happening until about 4 days ago with a -CURRENT kernel. Maybe you have an
> > older -CURRENT.
> > 
> > 
> I did a make build/installworld and kernel this afternoon after I
> cvsup'd(current). I have an original non-pnp SB16.
> (Best sounding sound card on the market IMOP) Aureal and any ESS equiped
> cards are excellent too.   
> 
> --
> Ted Sikora
> Jtl Development Group 
> [EMAIL PROTECTED]
> 



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

Re: high CPU usage by xmms

[Kenneth Wayne Culver]

I guess it depends on your soundcard, I'm getting the behavior I'm getting
with a ViBRA 16X and a kernel as of this morning. This didn't start
happening until about 4 days ago with a -CURRENT kernel. Maybe you have an
older -CURRENT.


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

On Sun, 30 Apr 2000, Ted Sikora wrote:

> Ted Sikora wrote:
> > 
> > VINSON WAYNE HOWARD wrote:
> > >
> > > Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6%
> > > while playing.  What's up w/ top?
> > >
> > 
> > Xmms on my SMP current machine: top shows 40 to 43% system
> > vmstat shows 10 to 11%
> > 
> 
> vmstat -w 1 matches top exactly about 41-43% system on my box.
> 
> --
> Ted Sikora
> Jtl Development Group 
> [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: high CPU usage by xmms

[Kenneth Wayne Culver]

I'm also getting this behavior now. It's not the xmms binary that's taking
all the cpu though... top reports it as "system" CPU usage.


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

On Sat, 29 Apr 2000, VINSON WAYNE HOWARD wrote:

> I did reboot for that reason, but I retried it and got about 50. Mabey I
> didn't run the player long enough...
> 
> 
> > > Ok, I checked, and vmstat shows cpu usage to be quite normal, about 6%
> > > while playing.  What's up w/ top?
> > 
> > Not on my computer:
> > 
> > pantzer@skalman ~ >vmstat -w 1
> >  procs  memory pagedisks faults  cpu
> >  r b w avm   fre  flt  re  pi  po  fr  sr ad0 da0   in   sy  cs us sy id
> >  4 1 0  339480  5552  131   0   0   1 147 233   0   0  288 1722 1971  6  5 89
> >  1 1 0  339480  55328   0   0   0   0   0   3   1  312 34105 34350 16 84  0
> >  1 1 0  339456  55565   0   0   0   6   0   0   0  321 34349 34608 10 90  0
> >  1 1 0  339456  55525   0   0   0   0   0   0   1  321 34211 34484 12 88  0
> > 
> > 
> > If you only run vmstat you get the average since the computer started.
> > 
> 
> 
> 
> 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

sound

[Kenneth Wayne Culver]

Just to let someone know (I know this is -current) but some of the recent
changes to the pcm driver have had some wierd effects. First, no wav file
will completely play (at least not the short ones); second, xmms now takes
100% cpu, and in top, it says that 76% of this is being used by the
"system"

Again, just to let someone know.

Ken



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

Re: linux ldconfig core dump

[Kenneth Wayne Culver]

oops, I forgot all about that, thanks. :-)


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

On Tue, 25 Apr 2000, Brooks Davis wrote:

> On Tue, Apr 25, 2000 at 09:14:57PM -0400, Kenneth Wayne Culver wrote:
> > As of about Thursday, Apr 20 I get this message when I try to run linux
> > ldconfig:
> > 
> > Segmentation fault(core dumped)
> > 
> > I recompiled the module and the kernel on this day so I think that's what
> > cause the problem, but I was wondering if there was anyone else having
> > this problem. This started last thursday, and it continues to be a problem
> > even now (with a kernel that's 10 minutes old, cvsupped today)
> 
> The method of branding has changed, and David O'Brien said you need to
> rebrand the linux ldconfig program.
> 
> -- Brooks
> 
> -- 
> Any statement of the form "X is the one, true Y" is FALSE.
> 



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