In message <37316232.c92a5...@altavista.net> Maxim Sobolev writes:
: Instead of
: #include
: should be
: #include
: and pnp.h also
i386/isa/isa_device.h is the legecy interface to the isa drivers. Its
use should be strongly discouraged...
Warner
To Unsubscribe: send mail to majord...@freebsd
>I solved it by installing new miniperl before building perl itself,
>but it doesn't seem to be a good idea to use installled (maybe old
>version of) miniperl at this point.
`make world' is supposed to use the new miniperl that it has just
installed in ${TOOLROOT}/usr/bin which is at the front of
Hi,
In the article <199905031757.kaa40...@mrynet.com>,
free...@mrynet.com (FreeBSD mailing list) wrote:
> Perl is failing due to some kind of conflict in library versions:
>
> miniperl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib -e 'use AutoSplit;
> autosplit_lib_modules(@ARGV)' lib/*.pm lib
I get DMA / interrupt timeouts on programs such as mpg123 or NAS. Those
programs that mmap the DMA buffer and set it cycling through (quake & friends)
work fine.
Stephen
--
The views expressed above are not those of PGS Tensor.
"We've heard that a million monkeys at a million k
On Thu, 6 May 1999, Thomas T. Veldhouse wrote:
> I had this problem on a Linux box a little while back. It also used
> egcs-1.1.2. I suspect there is a problem with the compiler or the configure
> script of the kde tarball.
>
> Tom Veldhouse
> ve...@visi.com
>
> -Original Message-
> Fr
On Thu, May 06, 1999 at 10:04:19PM -0400, Brian Feldman wrote:
> 2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my
>new Seagate, which does UDMA2 fine with ATA
>
Can you boot -v and give the output of the ATA_INQUIRY line? That should say
which modes are available on
I'm having two problems with IDE nowadays.
1. ATA doesn't work with LS-120. That's not new. But ATA does seem to crash on
me, and there's no dump() so I can't figure out why.
2. wd supports UDMA on my chipset, but won't enable any kind of DMA on my
new Seagate, which does UDMA2 fine with ATA
On Wed, 05 May 1999 23:25:46 -0600,
Warner Losh said:
imp> : Daniel O'Connor has posted a problem similar to my one, followed by the
fix
imp> : patch by Luoqi Chen. I will try that patch tonight at home...
imp> I strongly suspect that the Luoqi Chen fix will solve your problem.
imp> It certai
I'm condisering such an animal for PicoBSD.
I'm willing to do it for current and other branches,
if and only if I can get three solid alpha testers.
"Daniel C. Sobral" wrote:
> Nick Hibma wrote:
> >
> > Jordan, you said nowadays one can simply compile a kernel < 1.44Mb and
> > stick it on the d
All,
After cvsuping the latest source, I cd'ed to the /usr/src directory
and tried to ``make world''. It failed with the following message:
===> cpp
cc -O -pipe -I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc
-I/usr/src/gnu/usr.bin/cc/cpp/../../../../contrib/egcs/gcc/config
-DFREEBS
> % gdb foobar foobar.core
> Register %s not found in core file.
^^
Should read:
"Register eax not found in core file."
Silly me... :-)
-scooter
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Current's gdb cannot read core files today (cvsup'd on Monday
and installed Monday). It reports:
% gdb foobar foobar.core
Register %s not found in core file.
%
The error emanates in gdb/gdb/core-aout.c. I was going to try
to diagnose the problem this weekend but unfortunately I have
USNR duty.
A
Hi,
When I attempt to install the 0506 snap, things work correctly
until I get the following on the debug screen:
DEBUG: MakeDev: Unknown major/minor for devtype 0s1b
DEBUG: MakeDev: Unknown major/minor for devtype 0s1e
DEBUG: MakeDev: Unknown major/minor for devtype 0s1a
DEBUG: MakeDev: Unkno
I have just committed a number of CAM changes that will require
recompilation of any userland programs you have that access the CAM
passthrough driver. So things like cdrecord, xmcd, etc., should be
recompiled.
The best way to update your system is via make world.
NOTE: I would really like to
If you want some information on USB:
FreeBSD USB homepage:
http://www.etla.net/~n_hibma/usb/usb.pl
USB homepage:
http://www.usb.org
Mailing list:
usb-...@egroups.com
subscribe: http://www.egroups.com
Specs on chips:
http://www.intel.com/
At 10:34 AM 5/6/99 -0700, Matthew Dillon wrote:
>:I'll gladly test them. I'm in the process of upgrading the lab I run to 3.1
>:and it depends heavily on NFS. Since the lab is closed during finals I won't
>:be losing massive amounts of data if they go wrong. Send 'em on. :) NFS is
a
>:big deal
: Ok, that's good news. I'd like to stick with -stable if I can. No
:pressure, but do you have an ETA on the VM backport? I'm assuming that
:something like that is "down the road," probably after 3.2?
There's no ETA at the moment. I'm hoping that modifications to -current's
VM sys
Matthew Dillon wrote:
> The only major bugfixes that have not been backported from -current to
> -stable in regards to NFS are the NFS/TCP fix, which is being backported
> now, and a number of fixes to the VM system when dealing with mmap(),
> which cannot be backported until we ba
On Wed, 5 May 1999, Mike Holling wrote:
> Apple's QuickTime 4 uses these protocols for streaming QuickTime, and I've
> got users asking me if the FreeBSD NAT box can be made to handle it.
> Looks like these protocols are new internet standards, has anyone
> integrated them into libalias yet? If n
:I'll gladly test them. I'm in the process of upgrading the lab I run to 3.1
:and it depends heavily on NFS. Since the lab is closed during finals I won't
:be losing massive amounts of data if they go wrong. Send 'em on. :) NFS is a
:big deal to a lot of us, and we'd like to see the changes MFC
Oops, those symbols are in /kernel, of course.
Sorry for bothering you with my noisy message.
In article <87hfpqfb98@ba2.so-net.ne.jp>
Takanori Saneto said:
>% nm /modules/procfs.ko | egrep ' U procfs_'
> U procfs_read_fpregs
> U procfs_read_regs
> U procfs_
Besides procfs_rlimit(), there are several undefined symbols in
procfs.ko:
% nm /modules/procfs.ko | egrep ' U procfs_'
U procfs_read_fpregs
U procfs_read_regs
U procfs_sstep
U procfs_write_fpregs
U procfs_write_regs
Is this OK?
--
さねを mailto:san...@b
Greg Lehey wrote:
> > I know it goes through periods of instability, but assuming that I'm
> > following the lists and know when not to build, could I put a 4.x
> > box up and not be embarrassed?
>
> Yes, but that's a big assumption: "assuming everything went OK". How
> do you known in advance w
On Thu, 6 May 1999, David O'Brien wrote:
> > the build of egcs. My understanding was that to bootstrap over the change
> > I should first (before the make world) do:
>
> VERY wrong. All you want to do is a normal ``make world'' (or ``make
> buildworld'')
Hup, you're right, sorry about the false
On 06-May-99 Jordan K. Hubbard wrote:
>> 2. Our architecture is *highly* dependent on NFS. I know that the good
>> work on NFS is happening in -current, which is why I'm considering it.
>> How well does -current NFS mix with an almost all-Sun network? Any
>> plans on MFC'ing the NFS fixes to -sta
On Thu, May 06, 1999 at 09:35:51AM -0500, Thomas T. Veldhouse wrote:
> >checking for kde libraries installed... configure: error: your system fails
> at linking a small KDE application!
> >Check, if your compiler is installed correctly and if you have used the
> >same compiler to compile qt and kde
I had this problem on a Linux box a little while back. It also used
egcs-1.1.2. I suspect there is a problem with the compiler or the configure
script of the kde tarball.
Tom Veldhouse
ve...@visi.com
-Original Message-
From: Tomer Weller
To: FreeBSD Current ; FreeBSD Ports
Date: Thurs
whenever i try to compile KDE software (ports also) i get this error, though
packages install fine.
i installed KDE from packages, i suspect that's the problem.
this is from the kmp3 port, but happens with every piece of kde software :
checking for KDE... libraries /usr/local/lib, headers /u
"Jordan K. Hubbard" wrote:
>
> > 3. How good and how stable is SMP currently, and does -current offer any
> > big advantages over -stable in SMP?
>
> I think SMP is pretty good in either branch, though Luoqi and Alan
> have been working to improve it in -current lately.
5% gain on worldstone for
>I don't know if anyone else has seen this yet. I'm current as of
> 5 1/2 hours ago... (2am EST, 11pm PST).
I had a non-standard Makefile, my bad. Fixed an hour or so ago.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the mes
Hi,
I don't know if anyone else has seen this yet. I'm current as of
5 1/2 hours ago... (2am EST, 11pm PST).
Thanks!
John
file2c 'u_char boot0[] = {' '};' < /boot/boot0 >> makedevs.tmp
mv makedevs.tmp makedevs.c
rm -f .depend
mkdep -f .depend -a-I/usr/src/release/sysinstall/../../gnu/lib
"Jordan K. Hubbard" wrote:
> > As of today -CURRENT (cvsup'ed several minutes ago) sysinstall still
> > broken:
>
> Current as of 10 minutes ago:
>
> cc -O -pipe -mpentium -Wall
> -I/usr/src/release/sysinstall/../../gnu/lib/libdialog
> -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/
> As of today -CURRENT (cvsup'ed several minutes ago) sysinstall still
> broken:
Current as of 10 minutes ago:
cc -O -pipe -mpentium -Wall
-I/usr/src/release/sysinstall/../../gnu/lib/libdialog
-I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/../../sys
-I/usr/src/release/sysinstall/.
> 1. In general how stable is -current? I know it goes through periods of
> instability, but assuming that I'm following the lists and know when not
> to build, could I put a 4.x box up and not be embarrassed?
I run my own machine off -current, have been doing so for months now,
and it's hardly a
> Apple's QuickTime 4 uses these protocols for streaming QuickTime, and I've
> got users asking me if the FreeBSD NAT box can be made to handle it.
> Looks like these protocols are new internet standards, has anyone
> integrated them into libalias yet? If not I might give it a shot, but I'm
> prob
> the build of egcs. My understanding was that to bootstrap over the change
> I should first (before the make world) do:
VERY wrong. All you want to do is a normal ``make world'' (or ``make
buildworld'')
> # cd /usr/src/gnu/usr.bin/cc; make clean; make obj
> # make
...
> ===> cc
...
> /usr/obj/
As of today -CURRENT (cvsup'ed several minutes ago) sysinstall still
broken:
sh-2.03# cd /usr/src/release/sysinstall/
sh-2.03# make depend
cc -o rtermcap /usr/src/release/sysinstall/rtermcap.c -ltermcap
rm -f keymap.tmp
for map in be.iso br275.iso danish.iso finnish.iso fr.iso? german.iso
hr.iso h
On Wednesday, 5 May 1999 at 23:59:21 -0700, Doug Barton wrote:
> First off, let's assume that I'm aware of all the traditional caveats
> re -current being bleeding edge, read the lists, etc. and am willing to
> deal with that. Now let's assume that I am trying to convince the powers
> that b
Studded wrote:
> Now, the main question I have is, at what points do I want to upgrade
> /etc? I ask both for my own edification, and for the purpose of testing
> the new version of mergemaster. I generally upgrade /etc/ before I make
> world (after backing up of course) so I'm guessing I wan
39 matches
Mail list logo