Re: Upgrade instructions are incorrect

2002-05-22 Thread Martin Kacerovsky
On Wed, May 22, 2002 at 01:05:48PM -0400, John Baldwin wrote: > Wrong. If you are following the proper upgrade path, then your old > binaries will always work with your new kernel. Can I ask you what the proper upgrade path is? In /usr/src/UPDATING : To rebuild everything and install it on th

Re: buildworld broken

2002-05-22 Thread Martin Kacerovsky
On Wed, May 22, 2002 at 10:23:31AM -0500, David W. Chapman Jr. wrote: > On Wed, May 22, 2002 at 05:21:59PM +0200, Martin Kacerovsky wrote: > > Hi, > > I've got this error during buildworld: > > Have you read UPDATING and put what it told you to in make.conf? Yes, I

buildworld broken

2002-05-22 Thread Martin Kacerovsky
Hi, I've got this error during buildworld: building shared library libusbhid.so.0 ===> lib/libvgl cc -O -pipe -Wall -I/mnt/store/usr/src/lib/libvgl -c /mnt/store/usr/src/lib/libvgl/main.c -o main.o In file included from /mnt/store/usr/src/lib/libvgl/vgl.h:37, from /mnt/store/u

Re: cannot make vidcontrol

2002-05-22 Thread Martin Kacerovsky
On Wed, May 22, 2002 at 04:29:33PM +0300, Giorgos Keramidas wrote: > It's very likely that other things will have problems with the new > kernel too. You just haven't discovered yet. You should really > always try to run a userland and kernel that have been compiled from > the same set of sourc

Re: cannot make vidcontrol

2002-05-22 Thread Martin Kacerovsky
On Wed, May 22, 2002 at 11:22:43AM +0300, Maxim Sobolev wrote: > sys/consio.h header installed on your system is too old. You need to > do a fresh `make world' and rebuild/reinstall your kernel - it's the > only way to do vidcontrol upgrade properly. I don't understand, I have CVSUPed the whole t

cannot make vidcontrol

2002-05-22 Thread Martin Kacerovsky
I got this problem: [ /usr/src/usr.sbin ]#make vidcontrol Warning: Object directory not changed from original /usr/src/usr.sbin/vidcontrol cc -O -pipe -c vidcontrol.c vidcontrol.c: In function `load_font': vidcontrol.c:221: structure has no member named `font_size' *** Error code 1 Stop in

Re: linux-q3ademo --> X crash

2002-05-21 Thread Martin Kacerovsky
On Tue, May 21, 2002 at 06:02:17PM +, Glenn G. wrote: > In general 'X11' is really not that stable in -current (and has been > for a while) Not only in current, the same crashes happened to me also in -stable (q3ademo), and there I haven't loaded DRI, here I have (although the log, I've se

Re: linux-q3ademo --> X crash

2002-05-21 Thread Martin Kacerovsky
On Tue, May 21, 2002 at 01:55:20PM -0400, Kenneth Culver wrote: > It looks like DRI isn't set up right. > > Ken > Yes, but if the DRI is correctly enabled it crashes too, sorry for desinformation, this log wasn't the best I could choose. Martin To Unsubscribe: send mai

linux-q3ademo --> X crash

2002-05-21 Thread Martin Kacerovsky
Hi. I've installed linux-q3ademo to do some "benchmarking", but X server crashes during startup... X server gets signal 11, XFree86.1.log is included as attachement I haven't found solutions of this problem on the internet, only the same questions. Martin XFree86 Versi

src/sys/crypto/missing

2002-05-20 Thread Martin Kacerovsky
Hi, I've just CVSUPed sources of kernel (I had a snapshot) and there's no crypto directory in src/sys and make writes error : make: don't know how to make /usr/src/sys/crypto/rijndael/rijndael-alg-fst.c. Stop what should I do? copy the old crypto directory into new source tree ? or is the mis

kernel panic in 5.0-20020302-PREVIEW with drm-kmod

2002-05-17 Thread Martin Kacerovsky
Hi, I have a problem with DRM, I have ATI Xpert2000 AGP card, in 4.5-RELEASE I used r128.ko , and all was fine, in current my kernel hangs up saying: malloc type lacks magic number. I have compiled the kernel with 'device agp' so what can be wrong? To Unsubscribe: send mail to [EMAIL PROTECTED]

Argument list too long in BUILDWORLD

2002-05-13 Thread Martin Kacerovsky
Hi, I've got error : /bin/sh:Argument list too long, while making buildworld, I haven't found any solution in archives, can you help me? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message