Re: Unable to buildworld (new record, 18)
Original Message On 9/7/02, 11:20:48 PM, Riccardo Torrini [EMAIL PROTECTED] wrote regarding Re: Unable to buildworld (new record, 18): On 07-Sep-2002 (21:00:28/GMT) Riccardo Torrini wrote: Have you read through UPDATING? Yes, more and more ... I added -DNO_WERROR without luck I also found two PR speaking about wchar_t (31864 and 40084). I'm about to remove contrib/gcc tree and cvsuping again... No, same error :( Any other ideas? [...] wild guess Have you tried making new includes? /wild guess Ciao, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: unknown PNP hardware
I'm running -current as of an hour ago. I've gotten this since I've been running 4.2-stable, any ideas on how I can find out what it belongs to? unknown: PNP0303 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0401 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0f13 can't assign resources This harmless message has been known for a good number of months. There is nothing to worry about. Now before someone flames both of us -- me for responding and you for not first searching the archives, where discussions about this topic took place countless times -- could you please go there and retrieve this information? :-)) By the way, you can also find freebsd posts on http://www.google.com and http://www.geocrawler.com. HTH, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
(Apparently) SOLVED: Re: QT23 not building
++ 21/08/01 02:21 +0200 - Salvo Bartolotta: || I am using XFree4 and my /etc/make.conf contains the required XFree86 || version string. || || opengl/qgl.h:63: GL/gl.h: No such file or directory || opengl/qgl.h:64: GL/glu.h: No such file or directory | These are included in || the Mesa port, and the qt23 port has a depend for | Mesa (USE_MESA= yes), but this is broken for XFree86 4. See my PR at At least, under -CURRENT. On (yet) another slice of mine -- featuring FreeBSD 4-S --, I can see the problematic files in place. | http://www.freebsd.org/cgi/query-pr.cgi?pr=29546, I'm still waiting for | someone on portmgr@ to commit it. BTW, I tried your suggestion, but it did NOT work: the same error occurred at the same place. getting lazy... OTOH, since qt had complained about missing files... I built Mesa3 and put those missing files, ie gl.h, glext.h, glu.h, and glx.h in /usr/X11R6/include/GL. Needless to say, qt-2.3.1 built without further complaints. So, rather than delve into the makefiles, I cheated square and fair :-) -- Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
QT23 not building
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
No Subject
OK, I;ve looked and looked and can't seem to figure out how to set hw.ata.wc to enabled. I've put and a few other things in /etc/sysctl.conf, the others get set, hw.ata.wc doesn't. You can't change it by hand either as sysctl tells you it's readonly. Grepping in /sys/i386/conf has turned up nothing and neither has grepping /boot. Have you tried specifying it in /boot/loader.conf ? hw.ata.wc=1 HTH (and have as much fun as possible :-), Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Experiences with new dir allocation on FFS?
[ resending, with a subject ] OK, I;ve looked and looked and can't seem to figure out how to set hw.ata.wc to enabled. I've put and a few other things in /etc/sysctl.conf, the others get set, hw.ata.wc doesn't. You can't change it by hand either as sysctl tells you it's readonly. Grepping in /sys/i386/conf has turned up nothing and neither has grepping /boot. Have you tried specifying it in /boot/loader.conf ? hw.ata.wc=1 HTH (and have as much fun as possible :-), Salvo P.S. Apologies for the previous subjectless message. Because of my current ISP's ahem policy, I am using another ISP's webmail services for sending mail. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
buildworld dies
Dear FreeBSD'ers with sources as of today, ~ 15:40 GMT (from the dutch mirror), my buildworld dies thus: === sbin/adjkerntz^M cc -O -pipe -march=pentiumpro -Wall -I/usr/obj/usr/src/i386/usr/include -c /usr/src/sbin/adj kerntz/adjkerntz.c^M cc -O -pipe -march=pentiumpro -Wall -I/usr/obj/usr/src/i386/usr/include -static -o adjkernt z adjkerntz.o ^M make: don't know how to make adjkerntz.1. Stop^M *** Error code 2^M ^M Stop in /usr/src/sbin.^M *** Error code 1^M ^M Stop in /usr/src.^M *** Error code 1^M ^M Stop in /usr/src.^M *** Error code 1^M ^M Stop in /usr/src.^M HTH Best regards/mes salutations les meilleures/mit freundlichen Gruessen, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvsup'ing repo cvs-checkout'ing sources makes cvs complain...
/* apologies if this is not the most appropriate list; [additional] * apologies for the long post; suggestions and pointers gladly * accepted. */ Dear FreeBSD'ers, Over the past few days, I have been cvsup'ing FreeBSD's repository and cvs-checkout'ing out my -CURRENT sources; for the record, I had been cvsup'ing my sources and making the buildkernel etc. dance flawlessly on this very test system. It seems a logical approach to switch from cvsup'ing each system separately to cvsup'ing the repo cvs-checkout'ing the desired modules (src, ports, doc, www) for each of my systems. However, I have had a few (probably minor) problems on my -CURRENT test system, where I am playing the new "cvsup repo"/"cvs-checkout modules" dance. My (stripped) cvs-supfile: blockquote # $FreeBSD: src/share/examples/cvsup/cvs-supfile,v 1.26.2.3 2000/09/22 06:31:21 asami Exp $ # *default host=cvsup.nl.FreeBSD.org *default base=/myjunk *default prefix=/myjunk/home/ncvs *default release=cvs *default delete use-rel-suffix *default compress src-all ports-all doc-all www /blockquote The background (also posted to -questions) -- Following Warner's directions in internat.txt, I removed the crypto-related stuff, and issued the following explicit command: 201 1:54am /usr # cvs -d /myjunk/home/ncvs checkout -r HEAD src # Script started on Wed Jan 17 01:54:54 2001 You have mail. 201 1:54am /usr # cvs -d /myjunk/home/ncvs checkout -r HEAD src cvs checkout: Updating src RCS file: /myjunk/home/ncvs/src/Makefile,v retrieving revision 1.234 retrieving revision 1.242 Merging differences between 1.234 and 1.242 into Makefile src/Makefile already contains the differences between 1.234 and 1.242 RCS file: /myjunk/home/ncvs/src/Makefile.inc1,v retrieving revision 1.141.2.2 retrieving revision 1.180 Merging differences between 1.141.2.2 and 1.180 into Makefile.inc1 src/Makefile.inc1 already contains the differences between 1.141.2.2 and 1.180 RCS file: /myjunk/home/ncvs/src/README,v retrieving revision 1.15 retrieving revision 1.19 Merging differences between 1.15 and 1.19 into README src/README already contains the differences between 1.15 and 1.19 RCS file: /myjunk/home/ncvs/src/UPDATING,v retrieving revision 1.73.2.3 retrieving revision 1.134 Merging differences between 1.73.2.3 and 1.134 into UPDATING src/UPDATING already contains the differences between 1.73.2.3 and 1.134 /* How come...? */ ? src/contrib ? src/gnu ? src/etc ? src/games ? src/include ? src/lib ? src/libexec ? src/release ? src/bin ? src/sbin ? src/share ? src/sys ? src/usr.bin ? src/usr.sbin ? src/tools ? src/kerberosIV ? src/kerberos5 ? src/makeworld_logfiles /* ? cvs doesn't like all directories, except the removed (crypto) ones, which are correctly updated. */ cvs checkout: Updating src/crypto U src/crypto/README cvs checkout: Updating src/crypto/heimdal U src/crypto/heimdal/ChangeLog snip /* cvs correctly updates the files in the src/crypto directories: heimdal, kerberos, openssh, etc. */ cvs checkout: Updating src/secure U src/secure/Makefile snip /* cvs correctly updates the files in the src/crypto directories: heimdal, kerberos, openssh, etc.; nothing else is updated */ 202 1:59am /usr # exit exit Script done on Wed Jan 17 02:00:13 2001 Needless to say, I rm -rf'ed the directories marked by "?", and repeated the whole checkout operation. Apart from a few ? in front of some files of mine in the source tree, everything was fine. I am now happily running a -CURRENT built from those very sources. What am I missing in the above cvs steps ? Why were my source directories marked as "?" and not updated ? Is it really necessary to rm -rf those subtrees? Mutatis mutandis, the same occurred in my ports tree (in the same -CURRENT system): Script started on Thu Jan 18 00:28:26 2001 You have mail. 201 12:28am /usr # cvs -d /myjunk/home/ncvs checkout ports cvs checkout: Updating ports U ports/.cvsignore cvs checkout: move away ports/INDEX; it is in the way C ports/INDEX cvs checkout: move away ports/LEGAL; it is in the way C ports/LEGAL U ports/Makefile U ports/README ? ports/README.html ? ports/Mk ? ports/Templates ? ports/Tools ? ports/archivers ? ports/astro ? ports/audio ? ports/benchmarks ? ports/biology ? ports/cad ? ports/chinese ? ports/comms ? ports/converters ? ports/databases ? ports/deskutils ? ports/devel ? ports/editors ? ports/emulators ? ports/ftp ? ports/games other directories snipped Again, removing the "?" directories (except distfiles) and cvs checkout'ing once more gave me a working ports tree. I haven't tried other modules (yet). I would first like to understand what happened. -- brand-new problems - As I said above, I removed the "?" directories, cvs-checkout'ed my sources, and successfully updated my -CURRENT (test) system. But on the next src checkout, the following warnings were given: Script started on Fri Jan 19
Re: cvsup'ing repo cvs-checkout'ing sources makes cvs complain...
Original Message On 1/21/01, 11:28:46 PM, Szilveszter Adam [EMAIL PROTECTED] wrote regarding Re: cvsup'ing repo cvs-checkout'ing sources makes cvs complain...: Dear Salvo, So if you want to place a directory under CVS control, you must first rm -rf it and then check it out again. Thanks a lot again. And still more apologies for the newbieish questions. Evidently, I was not correct in implicitly assuming that cvs would recognize/adopt a previously cvsup'ed tree. As for your second question: CVS does not normally delete files that you no longer need but only displays warnings about them. You can remove those files now. Cvsup in contrast also removes the files if you tell it so. Ok, since I logged those warnings, I'll just write a two-liner awk/perl script for that :-) Best regards, Salvo (I'll get out and grep someone... :-)) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SOLVED: SCSI CD recorder no longer attached; minor issues
Original Message On 1/8/01, 7:17:46 AM, "Justin T. Gibbs" [EMAIL PROTECTED] wrote regarding Re: SCSI CD recorder no longer attached; minor issues : Can you see if this patch corrects the problem? /* The patch in question, if not yet committed, can be retrieved in the previous message */ On my FreeBSD 5-0 CURRENT (sources as of... the day before yesterday ~ 18:15 GMT): perl -pi -e "s:^V^M::g" Gibbsdiffs # How come... :-) patch -d /usr/src/sys/dev/aic7xxx/ Gibbsdiffs --- new kernel compiled and installed; /* testing my YAHAMA CD-recorder and player */ --- boot messages are all right; --- 637-MB ISO image created via mkisofs and burnt to CD via cdrecord; --- diff -r /cdrom /path/to/my/test/files Summing up: SCSI seems to work like a charm. Thank you very much, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SCSI CD recorder no longer attached; minor issues
Dear FreeBSD'ers, I am running -CURRENT as of today (sources as of ~ 18:15 GMT). I can see the following (a # sign precedes my comments): Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad2s1a # YAMAHA CRW4416S: it is correctly recognized by -STABLE. # OTOH, the archives seem to report just *minor* SCSI issues. (cd0:ahc0:0:3:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ahc0:0:3:0): error code 0 (cd0:ahc0:0:3:0): fatal error, failed to attach to device (cd0:ahc0:0:3:0): lost device (cd0:ahc0:0:3:0): removing device entry # My cd player works cd1 at ahc0 bus 0 target 6 lun 0 cd1: PLEXTOR CD-ROM PX-40TS 1.00 Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present # It is unusual on this system pcm0: hwptr went backwards 20 - 12 pcm0: hwptr went backwards 2072 - 2048 pcm0: hwptr went backwards 2184 - 2048 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 2068 - 2048 pcm0: hwptr went backwards 2240 - 2048 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 2204 - 2048 pcm0: hwptr went backwards 20 - 0 pcm0: hwptr went backwards 2068 - 2048 pcm0: hwptr went backwards 2068 - 204 I forgot to reboot via 'shutdown -r now' *sigh* On a couple of subsequent occasions, however, shutdown -r now was timed out, and no entropy file was created; 'dd if=/dev/random of=/entropy bs=4096 count=1' (within the shutdown sequence) did NOT create anything. In s.u.m., I issued it as an ordinary explicit command, but it stalled. So... workaround: 'dd if=/dev/urandom of=/entropy bs=4096 count=1'. Then /dev/random, asked again to do its duty, helped dd (to) create an entropy file. I was wondering whether such a sanity check would be worth adding (in rc.shutdown ?) in order to prevent the above entropy (minor) issue. Does this make sense at all? Is this just a little temporary problem ? Thanks for your patience and best regards,. Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrading -stable - -current, boot failure?
Original Message On 10/11/00, 9:53:07 AM, Mike Meyer [EMAIL PROTECTED] wrote regarding Upgrading -stable - -current, boot failure?: I've got a system with 4.1-STABLE installed. I mount -current sources on it, do make buildworld/buildkernel/installkernel/installworld and reboot. The boot loader runs, gives me the "booting default in..." countdown, prints "|", and then stops. After thrashing the disks (with *no* boot messages), I get a prompt from init. Since the same sources build and boot properly elsewhere, I assume I've missed a step. I normally run mergemaster after installworld and rebooting singleuser. Could someone provide the clue I've not got? thanx, mike Mike, not quite sure that this is relevant, but since nobody has replied ... Surely you configured the hints stuff ? /not quite sure that this is relevant, but since nobody has replied ... Best regards, Salvo (running PRE_SMPNG without any problems -- so far) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: downgrade?
Dear Alfred Perlstein, caution type="I haven't (as yet) tried this" From the posts I have been reading, I seem to understand that the following may apply (depending on the divergence/relationship between -CURRENT and -STABLE): -- It may be necessary to downgrade the toolchain (e.g. binutils; gcc); -- It may be necessary to downgrade "script"utils (ie perl). /caution Yes you're correct there will be problems with perl, that's why you need a 4.x machine to do the building on and that's also why you may need several 'make -k installworld' runs to finally get a 'make installworld' to work. Oooops, I had another problem in mind. I thought of the theoretical general problem of downgrading a -CURRENT machine in a "self-consistent" fashion (ie on the same machine). I haven't done that (so far), so I am not aware of any [other] unwanted side-effects. AFAIR, a few weeks ago, someone performed such an operation (in the first week of August or so); I read several posts about the matter. If somebody has successfully tried such an operation recently (on a PRE_SMPNG machine), s/he will be able to help Phillip. Anyway, your suggestion sounds safer. Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Make World
Original Message On 9/28/00, 10:53:21 PM, [EMAIL PROTECTED] wrote regarding Make World: I recently cvsup'ped my source to the Current 5.0 version of FreeBSD. I recompiled the kernel and did all of that jazz and ultimately decided I wanted to go back to 4.1. So, I used CVSup to download the 4.1 release. I deleted the usr/obj directory and reissued the "make buildworld" command. It went for a long time, but after a while it errored out with this message: Writing Makefile for DynaLoader mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/auto/DynaLoader perl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib - I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib - I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib - I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib DynaLoader_pm.PL DynaLoader.pm Perl lib version (5.00503) doesn't match executable version (5.006) at /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/Config.pm line 7. Compilation failed in require at DynaLoader_pm.PL line 2. BEGIN failed--compilation aborted at DynaLoader_pm.PL line 2. *** Error code 255 Stop in /usr/obj/usr/src/gnu/usr.bin/perl/perl/ext/DynaLoader. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I thought perhaps that I had some old sources laying around, so I blew away my entire src directory and re-downloaded it from CVS. I deleted the usr/obj directory, and did a make buildworld and came up with the EXACT SAME ERROR! I cannot figure this out. Does anyone have any advice? Thanks, Justin Justin, CURRENT utilizes a different (more recent) version of perl (5.6.0). AFAIR, this problem has already been reported to the list; AFAIR, Kris Kennaway suggested wiping out all traces of perl before making the 4.x buildworld. N.B. I am NOT sure this will grant you success. AFAIR, a few weeks ago, you had to downgrade such pieces as e.g. binutils and gcc. You will have to check those items yourself. At any rate, if something does go wrong, you have a clue ... HTH, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86
Original Message On 9/7/00, 10:51:14 AM, Piotr Woniak [EMAIL PROTECTED] wrote regarding XFree86: Hi, I have installed XFree86 and there is no XF86Setup. Have you any idea - why? I want to increase depth of color and modifing /etc/XF86Config has no result. How can I do it? Piotr Wozniak Dear Piotr Wozniak, When I installed XFree86 3.3.6 (via the ports mechanism), I had the opportunity of installing the VGA server(s). More precisely: installation.log [...] Which servers do you wish to build, you can save a lot of disk space by only compiling the server you will be using. It will also save you considerable compile time. *** If you want to use XF86Setup to set the INITIAL configuration, *** then you must build the VGA server Do you want to build the VGA16 server? [YES] Y Do you want to build the VGA16Dual server? [YES] Y [...] /installation.log As to modeline "hacking", you may wish to have a look at http://www.linux.org/docs/ldp/howto/XFree86-Video-Timings-HOWTO.html, and/or at Greg's excellent book (The Complete FreeBSD). HTH, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86
Original Message On 9/7/00, 12:18:07 PM, Mark Murray [EMAIL PROTECTED] wrote regarding Re: XFree86 : Hi, I have installed XFree86 and there is no XF86Setup. Have you any idea - why? I want to increase depth of color and modifing /etc/XF86Config has no result. Tcl/Tk. Build X, clean it out. Build Tcl/Tk 8.2. Build X again. You'll have XF86Setup. BTW - there is no XF86Setup in XFree86-4 yet. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org Dear Mark Murray, from my installation.log, just to add another datapoint: installation.log === Configuring for XFree86-3.3.6 Using tk-8.3 Which servers do you wish to build, you can save a lot of disk space by only compiling the server you will be using. It will also save you considerable compile time. *** If you want to use XF86Setup to set the INITIAL configuration, *** then you must build the VGA server Do you want to build the VGA16 server? [YES] Y Do you want to build the VGA16Dual server? [YES] Y /installation.log IMHE, the configuration is possible via [a] few different versions; mine is, er, are currently tcl-8.3.1 and tcl-8.2.3; I recall installing XFree86-3.3.6 immediately after I had installed tk-8.3 (ie which, in turn, installed tcl-8.3.1). Also, as a quick look at the PLIST confirms, different versions of Tcl -- Tool Command Language -- can (should) happily coexist :-) Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mixer no longer works
Original Message On 9/2/00, 6:29:32 AM, Kenneth Wayne Culver [EMAIL PROTECTED] wrote regarding mixer no longer works : In -CURRENT cvsupped as of today, the mixer no longer works. anything that tries to access the mixer just says "Operation not permitted" ME TOO type="*sigh*" -CURRENT, sources as of September, 1, ~ midnight GMT. Maybe I have cvusp'ed a few (?) minutes later than you. /ME TOO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: forgot info on soundcard (was: mixer no longer works)
Original Message On 9/2/00, 5:14:39 PM, Kenneth Wayne Culver [EMAIL PROTECTED] wrote regarding forgot info on soundcard: 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 Dear Kenneth Wayne Culver, I am afraid the problem may not bear any relation to soundcards. FWIW, mine is a soundblaster AWE 64 (ISA), and it IS detected at boot time; by the way, I have been using device pcm, seq, sbc, and joy in my kernel config; also, I have remade the snd0 device. Best regards, Salvo -- listening to his favo(u)rite composers under 4-STABLE :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make installkernel broken ? (was Re: World broken)
Original Message On 7/23/00, 7:19:03 AM, Warner Losh [EMAIL PROTECTED] wrote regarding World broken: cc -O -pipe -DMD5 -DSHA1 -DRMD160 -I/usr/obj/home/imp/FreeBSD/src/i386/usr/include -o mtree compare.o crc.o create.o excludes.o misc.o mtree.o spec.o verify.o -lmd misc.o: In function `flags_to_string': misc.o(.text+0x89): undefined reference to `fflagstostr' spec.o: In function `set': spec.o(.text+0x5f5): undefined reference to `strtofflags' *** Error code 1 I'm kludging mtree so that make buildworld isn't broken. Don't remove the kludge until such time as the underlying problems have been corrected. Dear FreeBSd'ers, The good news: I have just made buildworld (sources cvsup'ed today), and made buildkernel with no problems. The (moderately) bad news: make installkernel fails: /usr/src # make installkernel cd /usr/obj/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386 /usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/ lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/us r/obj/usr/src/i386/usr/games:/tmp/install.12899 MACHINE=i386 KERNEL=GENERIC make KERNEL=GENERIC install make: not found *** Error code 127 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It is a few weeks since I last made a -CURRENT world, so I have been cautious enough, and I have chosen the buildkernel and installkernel targets -- as if I were updating from -STABLE. Since I am already well "flamed" (~ 35/40 °C down here), please be so kind as not to flame me :-) Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Yet another breakage this week ...
Dear FreeBSD'ers, yet another item of bad news during this long endless week *sigh* I succesfully built and installed the world -- sources as of 24 May at (about) 21 GMT. However, I couldn't compile a kernel. It broke at the ipfilter module as I recall. Well, I downloaded the sources again "today" (at 11 GMT on May, 25) to compile ONLY the kernel -- without remaking the world. The good news is that the ipfilter module compiles; the bad news that there's a problem (read ``Error code 1'') in .../modules/twe/twe.c at line 1488, 1495, 1496: structure has no member named tqh_something. HTH, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel compile error
Original Message On 5/24/00, 6:26:46 PM, Maxim Sobolev [EMAIL PROTECTED] wrote regarding Re: kernel compile error: Scott Flatman wrote: I've done that twice. Buildworld failed both times. My last sucessful buildworld was last sunday, 5/21. I know that because I can't build it during past 3 days too. Please be patient, someone will definitely fix somwhere in future ;-). -Maxim Dear Maxim Sobolev, JOKING MODEI seem to understand that, statistically speaking, Sunday is the best day for cvsupping/making the world ... /JOKING MODE Actually, whenever I cvsup'ed sources on Sunday, I've NEVER scr***d a make world ... well, ehem, at least so far. Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ldconfig -m not configuring ?
Dear FreeBSD'ers I cvsup'ed -CURRENT on 25 April at about 9 GMT. I succesfully made the world apart from a couple of minor issues. In the next few days, I installed some ports and, in, particular, the linux_base-6.1 port; then I installed StarOffice5.1a (via ports). Everything seemed to work properly. I installed Acrobat Reader 4.05 (via ports) and then other ports (e.g. Apsfilter (ie teTeX), lyx, textproc/docproj, ...) and I configured JADETEX C. But when I issued "acroread4", the terminal spat out "ELF interpreter /lib/ld-linux.so.2 not found." The interpreter does exist in /usr/compat/linux/lib/ld-linux.so.2 -- ld-2.1.2.so and this is what "file ld-2.1.2.so" says: ld-2.1.2.so: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped. I issued a "ldconfig -r | grep ld-linux" and, actually, I found nothing. Then I issued a "ldconfig -m /usr/compat/linux/lib" and even a "ldconfig -aout -m /usr/compat/linux/lib" (paranoia.) Now ldconfig -r shows a bunch of /usr/compat/linux/lib libraries EXCEPT the one I would have liked it to save among the hints. For some obscure (to me) reason, it refuses to take ld-linux.so.2 (ie ld-2.1.2.so) into consideration. By the way, acroread is correctly brandelfed, since it was installed after remaking the -CURRENT world. Just to be paranoidly safe, I rebrandelfed it, and a diff with the .orig version (previously copied) of course showed no difference. What prevents ldconfig -m /usr/compat/linux/lib from doing its duty ? What am I missing ? Many thanks in advance and happy weekend, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ldconfig not configuring NOT solved: followup (RTFM .RTFM RTFM ... )
Dear FreeBSD'ers, I apologize for the previous very superficial question. I had missed the Linux mode stuff blushing like a primary school pupil not having done his/her homework I RTFMed it. However, the problem is still there *re-sigh* I ran the Linux ldconfig, ie /usr/compat/linux/sbin/ldconfig -p | grep ld: it said that ld-linux-so.2 WAS in the hints. Then I ran /usr/compat/linux/ldconfig (no options). And yet I got the same error when I launched "acroread4": ELF interpreter /lib/ld-linux.so.2 not found. I made a copy of ld-2.1.2.so (the actual file referred to by ld-linux.so.2) with suffix .orig, and I brandelfed -t Linux ld.2.1.2.so. Alas, it did NOT work either. I had a look at another slice (4-STABLE) of mine, where Acrobat Reader 4.05 works. BTW, the ld.so.cache was equal. I have not yet discovered any illuminating difference in the /usr/compat/linux subtree. **If** I fully understand the situation and if I am not missing other pieces of the puzzle, the "syntax" is all right. Therefore the problem should be "semantical". In other words, under 5-CURRENT (sources as of 25 April 9 GMT) the Linux mode does NOT work properly. Please note: StarOffice 5.1a works whereas Acrobat Reader (which requires the ld-linux.so.2 interpreter) does NOT. This problem should not be related to the brandelf issue: I installed the linux_base-6.1 and a couple of Linux-emulated ports (StarOffice, Acrobat) *after* making the 5-CURRENT world. As I said in the previous message, StarOffice works. And brandelfing acroread produces a file *equal* to the non-brandelfed acroread. What am I missing now ? Is the Linux mode just broken ? Thanks in advance again for any help and best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
A positive data point ... and one question.
Dear FreeBSD'ers, Although I had been reading negative news, I went ahead ruthlessly and I upgraded one of my 4.0-S slices to 5-CURRENT. My attempt was successful. For the record, I had cvsup'ed -CURRENT on 25 April at about 9 GMT. However,I found a couple of curious things: 1) Albeit I had remade all the devices (including all the slices in use, sound devices etc.), this warning appeared: "WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices"; 2) while booting, I saw a bunch of "unknowns": bartequi /kernel: unknown: PNP0400 can't assign resources bartequi /kernel: unknown: PNP0501 can't assign resources bartequi /kernel: unknown: PNP0501 can't assign resources bartequi /kernel: unknown: PNP0700 can't assign resources bartequi /kernel: unknown0: PNP0c01 at iomem 0-0x9,0x10-0x17ff,0xe8000-0xe,0xf-0xf3fff,0xf4000 -0 xf7fff,0xf8000-0xfbfff,0xfc000-0xf,0xfffe-0x on isa0 bartequi /kernel: unknown: PNP can't assign resources bartequi /kernel: unknown1: PNP0100 at port 0x40-0x43 irq 0 on isa0 bartequi /kernel: unknown2: PNP0b00 at port 0x70-0x71 irq 8 on isa0 bartequi /kernel: unknown: PNP0303 can't assign resources bartequi /kernel: unknown3: PNP0c04 at port 0xf0 irq 13 on isa0 bartequi /kernel: unknown4: PNP0200 at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 bartequi /kernel: unknown5: PNP0800 at port 0x61 on isa0 bartequi /kernel: unknown6: PNP0a03 at port 0xcf8-0xcff on isa0 bartequi /kernel: unknown7: PNP0c02 at port 0x290-0x297,0xe400-0xe43f,0xe800-0xe83f on isa0 bartequi /kernel: sbc0: Creative SB AWE64 at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 bartequi /kernel: sbc0: setting card to irq 5, drq 1, 5 bartequi /kernel: pcm0: SB DSP 4.16 on sbc0 bartequi /kernel: joy0: Generic PnP Joystick at port 0x200-0x207 on isa0 bartequi /kernel: unknown8: WaveTable at port 0x620-0x623 on isa0 well, I had seen unknown8 before, but it was the ONLY unknown. Finally, I deinstalled the tcsh port and changed my shell to /bin/csh (ie /bin/tcsh). Apart from the above minor items, the upgrade seems to have been quite successful. Question. I had created the 4.0-S system that I would subsequently upgrade to -CURRENT via "make release". I ran "disklabel -B ad2" just to be safe (the OS, now -CURRENT, lives on ad2s1.) When I issued a "disklabel -r ad2", I got "disk: ad2s1". On the other hand, I issued a "disklabel -B ad1" for another 4.0-S system of mine, a 4.0-S system which lives on ad1s2 (/, /var swap) and ad2s2 (/usr). I had successfully upgraded this (former) 3.4-S to 4.0-CURRENT via cvsup and the procedure described in UPDATING; then I had upgraded it to 4.0-S. For this system, disklabel -r spits out "disk:wd1s2" (instead of "ad1s2"). What am I (yawn) missing ? Thanks in advance and best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: 3.x - 4.0-STABLE upgrade instructions
Original Message On 3/16/00, 2:52:36 AM, Brandon Fosdick [EMAIL PROTECTED] wrote regarding Re: HEADS UP: 3.x - 4.0-STABLE upgrade instructions: Warner Losh wrote: In message [EMAIL PROTECTED] Doug Barton writes: : You can find instructions at : http://freebsd.simplenet.com/make-upgrade.html. I am planning to update : that file for 3.4 - 4.0 asap BTW. Let me know if the following doesn't work: To update from 3.x to 4.0 stable cd /usr/src make buildworld cd sbin/mknod make install follow directions to build/install a kernel follow rebuild disk /dev entries above[*] reboot in single user cd /usr/src make -DNOINFO installworld make installworld [*] You may need to switch from wd to ad ala 19991210 To build a kernel - Update config, genassym and go: cd src/usr.bin/genassym make depend all install cd ../../usr.sbin/config make depend all install cd ../../sys/i386/conf config YOUR_KERNEL_HERE cd ../../compile/YOUR_KERNEL_HERE make depend make make install To rebuild disk /dev entries MAKEDEV should be copied from src/etc/MAKEDEV to /dev before starting the following: For N in the list of disks MAKEDEV N # eg ad0 for M in the list of slices MAKEDEV NsMa# eg ad0s1a How to go about switching over from wd to ad needs to be explained a little better. After doing the MAKEDEV routine I went and changed all the wd's in my fstab to ad's. Boy was that a mistake. Now I have to find somthing I can boot with that will let me mount the root partition read/write so that I can change fstab back. On top of that my cdrom suddenly decided to non-bootable. Maybe I'm just having a bad day... -Brandon Dear Brandon Fosdick, the (almost complete) updating procedure lies before you [was: Nature ;-)]. I am afraid the difficulties do NOT consist in making the devices nodes and the related slice entries. The following questions arise spontaneously. Q0) Have you been reading the -CURRENT mailing list archives for a while? In particular, have you read the letters posted in the last few weeks ? Q1) Did you exactly do as described in the procedure ? That is, if your disk is ,say, wd0, did you make an ad0 device node ? Did you make the *slice* entries, in our example ad0s1a (which makes ados1a through ad0s1h), as indicated there ? Did you update your /etc/fstab accordingly ? Did you substitute ad* for wd* in all your configuration files ? Q2) Have you read the very recent letters on the updating procedure (as of yesterday and today) ? Q3) Have you appropriately used the -k (ie force) option when making installworld ? Mind you, I missed the "cleaning" issue (you should not use the clean target in genassym etc. when making your first 4.0 kernel.) However, I succeeded in upgrading (though not all components were actually built). I did not care. Rather, I made the world again and checked my install logs (and they looked ok): now my 4.0-CURRENT (or should I say 4-STABLE ;-) seems to work like charm. At least, so far ... Good luck Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
upgraded to -CURRENT et al -- solved; X and PAM work for me
Dear FreeBSDers, after a couple of days spent RTFMing like crazy, I am back at my console at last ! (yawn ...) I have read some of the recent messages about X not working on -CURRENT as well as other issues. Although my -CURRENT sources are the same (last cvsup on 06-Mar-2000 11pm GMT), I seem to have solved most of my difficulties. Remark I Since I am a bit paranoid, I remade the world once more (exactly by the book, except for m.m. of course), and, wait for it, I met NO errors in making installworld. NO errors. Even sysinstall, after making (it) clean, was made smoothly. I am running a full-blown -CURRENT :-)) [wild screams of joy censored] In the past few weeks, under a -STABLE installation of mine (which was to become my present -CURRENT), I had compiled XFree86-3.3.6 with PAM support, among other things. As I wrote a couple of days ago, I met authentication errors with my freshly-(re)made -CURRENT. However, my pam.conf and ttys files were perfectly correct. Thus I recompiled X (with PAM support yet again!) and this time ... it worked seamlessly. Am I the sole person running X (compiled with PAM support) without problems under -CURRENT ? :-) HTH, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
Original Message
On 3/10/00, 9:51:06 AM, R Joseph Wright [EMAIL PROTECTED] wrote
regarding single user mode problem:
This has been going on for awhile, and I've looked everywhere for a
solution. When I boot single user, the / filesystem gets mounted on
wd0s4a even though /dev does not even have such an entry nor does
/etc/fstab, since these have all been updated.
This is not really such a problem until I try to exit from single user
mode. Then, it tries to remount / on ad0s4a and can't find it.
Dear Joseph,
as I have recently written, I met an analogous problem while upgrading
to CURRENT: the "wdNsMa syndrome" appeared when I rebooted in s.u.m.
with the shining gleaming roaring freshly-made 4.0-CURRENT kernel in
order to (somehow) make installworld. Well, I did NOT care about it
and I went ahead ruthlessly ...
By the way, I made another kernel at the end of the process ("by the
book"). I suppose (?) this cleared the problem. In fact, I was able to
boot with no weird messages: all my filesystems were correctly
identified as adNsM (e.g. ad1s2a, ad1s2e ...)
HTH,
Salvo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
upgraded to -CURRENT (?) et al.
Dear users, I (last) cvupped -CURRENT on 6 March at about 11:00 pm GMT, and, with few (necessary) variations, I tried to follow the instructions in UPDATING on the next day. I *seem* to have upgraded to -CURRENT. FWIW, here is what I did: 1) /usr/src/make -j48 buildworld 2) /usr/src/sbin/mknod/make install 3) followed the directions to build/install a kernel. Remark: config -r core dumps (bad system call); config (no option) does not. 4) rebuilt disk /dev entries; updated the relevant files (/etc/fstab). In order not to forget anything, I issued various grep -r commands. 5) reboot in s.u.m. Remark I : the root partition is seen as wd1s2a; the others are seen correctly. Remark II: if one happens to reboot, one meets a FATAL TRAP; after rebooting, one is denied access to / . Workaround: I booted from another installation of mine (-STABLE) on another slice, and ran fsck from there. 6) /usr/src/make installworld I got this error: lib/libcom_errdoc [omissis] unrecognized option `--defsection=Programming development tools.' Error code 1 (six times) 7) /usr/src/usr.bin/xinstall/make clean all install NOSHARED=YES 8) /usr/src/make installworld It failed with the same errors as sub 6). 9) /usr/src/make -DNOINFO installworld I got another error: install: genassym: no such file or directory. Error code 71. Error code 1 (five times.) It was time to use ... the Force. 10) /usr/src/make -DNOINFO -k installworld 11) /usr/src/make -k installworld Alas, I did not log the sessions sub 10) and sub 11) because ... I did NOT believe I would succeed in making installworld #@[]*^§ [severely censored] 12) mergemaster, devices, sysinstall and (yet another) kernel by the book. Remark I: making sysintall failed: undefined reference in pccard Initialize. Error code 1. Remark II: this time config -r worked. If I had used -k properly, I would have finished earlier. I suppose I am somehow running -CURRENT (?) N.B. I am Italian and I chose MD5, discarding everything DES-related. I suppose this has automagically eliminated a few problems. Under -STABLE, I used to compile my kernels with a0ffa0ff flags for my IDE disks 0 and 1, and b0ff for my third IDE disk. Under -CURRENT, I specified the ata driver as per the suggestions in LINT, and I did NOT specified ata0 and ata1; which are indicated for older systems. The log messages show that all three disks are accessed in UDMA 33 mode and are seen as having **16** heads. However, I must miss something obvious here (yawn) how can I specify the LBA mode for my third disk ? Is it automagically set ??? I fear I can corrupt part of my filesytems: my /usr lives on my third IDE disk (formerly accessed in LBA mode.) Another problem. I get "isa0: unexpected tag 14" while booting. What am I missing ? There are other questions: e.g. X authentication fails. Pam.conf and ttys are all right, though. Before attacking all of them (grepping -r the d***ed wd disks and recompiling the related ports ...), I would like to be in a position to recompile things in /usr without running any risks to destroy that filesystem. In this way, I will also be able te remake the world once more ... I thank you very much in advance for any help. Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
upgraded to -CURRENT (?) et al. III
Dear users, I forgot to specify another point in my first letter: "N.B. I am Italian and I chose MD5, discarding everything DES-related. I suppose this has automagically eliminated a few problems." I chose MD5 when installing FreeBSD-3.3-Release, whence I upgraded to -STABLE and finally to -CURRENT. Sorry for these omissions :-( I should really go to bed *sigh* Best regards, Salvo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
