w output strange message
Hi all... I am running a very recent -CURRENT. Within X, running w produce weird message: $ w w: /dev/:0: No such file or directory 2:52PM up 40 mins, 2 users, load averages: 1.52, 1.73, 1.42 USER TTY FROM LOGIN@ IDLE WHAT john p2 :0.0 2:50PM - vim john p4 :0.0 2:52PM - w /john I go, I fight, and I win! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: malloc() and the stock Perl in -CURRENT (and -STABLE)
On Thu, Mar 14, 2002 at 07:40:04AM +0100, Poul-Henning Kamp wrote: But if somebody wants to try to code this optimization, I'll be more than happy to review the result. I just don't expect it to do much in real-life as opposed to silly benchmark situations. Sorry to start this thread at the first place. Well, the reason that I did was because I had this in my head: What? This little snippet of code runs bloddy slower than in Linux? Boy... I use Perl happily in FreeBSD, and I can't lie to myself that in some situations, I felt like my FreeBSD perl scripts run slower than in Linux. Well... If I write to [EMAIL PROTECTED], those genius developers might catch this and maybe discuss on how to overcome the problem. I don't know whether anything's useful, but at least if I post, more people will notice and PROBABLY can improve a thing or two. I hate to run my scripts under Linux and will do everything I can to make my scripts run in FreeBSD at least as fast as in Linux! This is not just talking about benchmarks. This situation will probably make people conclude things that are not beneficial at all for FreeBSD. People in my definition are non-C-coders and those-who-just-like-to-generalize-things. Exclude me from that list, but there are many of others who fit to that group. I am not complaining and bugging FreeBSD developers to do anything at all. Well, I can't help myself, but at least I have done my part to post this. Thanks... /john I go, I fight, and I win! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
malloc() and the stock Perl in -CURRENT (and -STABLE)
Dear all...
This morning I found a very interesting mail. All of you can see it from:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1669241+0+current/freebsd-questions
As stated in the mail, a simple Perl script like this:
-- Begin --
#!/usr/bin/perl
$temp = ;
$begin = time;
for ($i = 0; $i 100; $i++) {
$result .= $i\n;
}
print Exec time: , time - $begin, secs\n;
-- End --
can show that there PROBABLY is something wrong with malloc() in -CURRENT
and -STABLE.
I am just bringing this to a wider audience so maybe this could be a
valueable information for FreeBSD developer and Perl maintainer in FreeBSD.
I heard that Perl in -CURRENT would be updated to Perl 5.6.1, maybe the
maintainer can put the default build for this new version of Perl to use its
own malloc (provided from Perl 5.6.1) IF it turns out that there is nothing
wrong with malloc() in -CURRENT and -STABLE (I don't know cause I am not a C
programmer)...
Thanks...
/john
I go, I fight, and I win!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: malloc() and the stock Perl in -CURRENT (and -STABLE)
On Wed, Mar 13, 2002 at 09:28:10PM -0800, Alfred Perlstein wrote: FreeBSD 5.0 has (being a developer release) has special diagnostics turned on in malloc that causes it to take more time to do allocations. But... it DOESN'T only happen in -CURRENT. Even Raistlin Majere [EMAIL PROTECTED] is using a -STABLE or a -RELEASE maybe (he doesn't state his uname output in the message). And to confirm, I have just run the script with FreeBSD 4.4-STABLE of Nov 24th 2001: 44 secs! Awfully slow! (Perl 5.005_03 built from buildworld) And... let me tell you more. I run the script in -CURRENT who has: $ ll /etc/malloc.conf lrwxr-xr-x 1 root wheel 2 Feb 8 14:08 /etc/malloc.conf - aj This is a fresh -CURRENT (Mar 13th 2002) with Perl 5.6.0 built from buildworld. And to clarify things... I don't know what's wrong with malloc() in -CURRENT and -STABLE (and I don't even know whether it's even wrong). All I want is to let the Perl maintainer in -CURRENT and -STABLE to compile the stock Perl with its own malloc library, thus Perl in FreeBSD doesn't suffer from this kind of slowness. Thanks... -Alfred /john I go, I fight, and I win! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: malloc() and the stock Perl in -CURRENT (and -STABLE)
On Thu, Mar 14, 2002 at 07:04:06AM +0100, Poul-Henning Kamp wrote: At the cost of considerable complexity (a mremap(2) implementation amongst other things), realloc in phkmalloc(3) can be optimised but it is not on my plate right now. Glad to know that there is no problem with malloc() in -CURRENT. But I still think that this must be addressed in Perl. So maybe, the stock Perl should be built against its own malloc library? Thank you for the clarification. /john I go, I fight, and I win! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Undefined symbol __stderrp
Hi... I have just finished building and installing a very recent -CURRENT. Now, my Yahoo! Messenger can't start with the following error message: /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol __stderrp Please don't flame me. I LOVE -CURRENT, it's just that I don't know C, and I am trying to get help on how to resolve this problem. Any tips on how to solve this problem? tq /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Anyone had luck with 3Com HomeConnect ADSL Modem Dual Link???
On Thu, Sep 27, 2001 at 12:57:26AM -0700, Julian Elischer wrote: I'd try asking for a service name of ISP THANK YOU!!! :)) /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Anyone had luck with 3Com HomeConnect ADSL Modem Dual Link???
On Tue, Sep 25, 2001 at 12:42:47PM +0100, Brian Somers wrote: You could try running ``tcpdump -i xl0 -e -l not ip'' to see if any of your traffic is being replied to (and to ensure it goes out with the dodgy header numbers). I have run tcpdump and attached is the output in libpcap format. If you care to take a look, I'd really appreciate it. tq... /john Live Free OR Die sniff
Anyone had luck with 3Com HomeConnect ADSL Modem Dual Link???
Hi... Has anyone on this list had any luck dealing with 3Com HomeConnect ADSL Modem Dual Link? I am stuck with this peace of hardware and please don't flame me ;) I connect the modem to an xl card sitting on the PC. I am running a fairly recent -CURRENT system. Here is my /etc/ppp/ppp.conf: default: set device PPPoE:xl0 set speed sync set mru 1492 set mtu 1492 set ctsrts off enable lqr set log Phase tun command add default HISADDR enable dns cbn: set authname [EMAIL PROTECTED] set authkey When I start ppp as root, and issue the dial command, here's what /var/log/ppp.log witness: Sep 25 15:34:27 adsl ppp[735]: Phase: Using interface: tun0 Sep 25 15:34:27 adsl ppp[735]: Phase: deflink: Created in closed state Sep 25 15:34:27 adsl ppp[735]: tun0: Command: default: add default HISADDR Sep 25 15:34:27 adsl ppp[735]: tun0: Command: default: enable dns Sep 25 15:34:27 adsl ppp[735]: tun0: Phase: PPP Started (interactive mode). Sep 25 15:34:34 adsl ppp[735]: tun0: Command: /dev/ttyp0: set log +debug Sep 25 15:34:35 adsl ppp[735]: tun0: Command: /dev/ttyp0: dial Sep 25 15:34:35 adsl ppp[735]: tun0: Phase: bundle: Establish Sep 25 15:34:35 adsl ppp[735]: tun0: Phase: deflink: closed - opening Sep 25 15:34:35 adsl ppp[735]: tun0: Debug: List of netgraph node ``xl0:'' (id 2) hooks: Sep 25 15:34:35 adsl ppp[735]: tun0: Debug: Found orphans - ethernet Sep 25 15:34:35 adsl ppp[735]: tun0: Debug: Connecting netgraph socket .:tun0 - [4]::tun0 Sep 25 15:34:35 adsl ppp[735]: tun0: Debug: Sending PPPOE_CONNECT to .:tun0 Sep 25 15:34:35 adsl ppp[735]: tun0: Phase: deflink: Connected! Sep 25 15:34:35 adsl ppp[735]: tun0: Phase: deflink: opening - dial Sep 25 15:34:35 adsl ppp[735]: tun0: Phase: deflink: dial - carrier Sep 25 15:34:35 adsl ppp[735]: tun0: Debug: Waiting for carrier Sep 25 15:34:36 adsl ppp[735]: tun0: Phase: Received NGM_PPPOE_SUCCESS (hook tun0) Sep 25 15:34:36 adsl ppp[735]: tun0: Phase: deflink: carrier - login Sep 25 15:34:36 adsl ppp[735]: tun0: Phase: deflink: login - lcp Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: fsm_Output Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: 01 01 00 16 01 04 05 d4 05 06 6b 60 c8 47 04 08 ..k`.G.. Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: c0 25 00 00 0b b8 .% Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: proto_LayerPush: Using 0xc021 Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: link_PushPacket: Transmit proto 0xc021 Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: m_enqueue: len = 1 Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: m_dequeue: queue len = 1 Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: link_Dequeue: Dequeued from queue 1, containing 0 more packets Sep 25 15:34:37 adsl ppp[735]: tun0: Debug: deflink: DescriptorWrite: wrote 24(24) to 3 Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: fsm_Output Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: 01 01 00 16 01 04 05 d4 05 06 6b 60 c8 47 04 08 ..k`.G.. Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: c0 25 00 00 0b b8 .% Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: proto_LayerPush: Using 0xc021 Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: link_PushPacket: Transmit proto 0xc021 Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: m_enqueue: len = 1 Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: m_dequeue: queue len = 1 Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: link_Dequeue: Dequeued from queue 1, containing 0 more packets Sep 25 15:34:40 adsl ppp[735]: tun0: Debug: deflink: DescriptorWrite: wrote 24(24) to 3 Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: fsm_Output Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: 01 01 00 16 01 04 05 d4 05 06 6b 60 c8 47 04 08 ..k`.G.. Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: c0 25 00 00 0b b8 .% Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: proto_LayerPush: Using 0xc021 Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: link_PushPacket: Transmit proto 0xc021 Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: m_enqueue: len = 1 Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: m_dequeue: queue len = 1 Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: link_Dequeue: Dequeued from queue 1, containing 0 more packets Sep 25 15:34:43 adsl ppp[735]: tun0: Debug: deflink: DescriptorWrite: wrote 24(24) to 3 Sep 25 15:34:46 adsl ppp[735]: tun0: Debug: fsm_Output Sep 25 15:34:46 adsl ppp[735]: tun0: Debug: 01 01 00 16 01 04 05 d4 05 06 6b 60 c8 47 04 08 ..k`.G.. Sep 25 15:34:46 adsl ppp[735]: tun0: Debug: c0 25 00 00 0b b8 .% Sep 25 15:34:46 adsl ppp[735]: tun0: Debug: proto_LayerPush: Using 0xc021 Sep 25 15:34:46 adsl ppp[735]: tun0: Debug: link_PushPacket: Transmit proto 0xc021 Sep 25 15:34:46 adsl ppp[735]: tun0: Debug: m_enqueue: len = 1 Sep 25 15:34:46 adsl ppp[735]: tun0: Debug: m_dequeue: queue len = 1 Sep 25 15:34:46 adsl ppp[735]: tun0: Debug: link_Dequeue: Dequeued from
Re: 3Com HomeConnect ADSL Modem Dual Link
On Tue, Sep 18, 2001 at 09:50:19PM -0700, Julian Elischer wrote: Can -CURRENT work with 3Com HomeConnect ADSL Modem Dual Link? depends how it connects to the system. I wanna connect it to an NIC, then use it as a media to connect to the Internet. I see in the handbook that there is a sysctl to force FreeBSD (-STABLE I assume) to cope with that particular standard non-compliant ADSL modem, but I can't find that sysctl in -CURRENT. Thus, the question first showed up because, I wanna know whether -CURRENT can work with the modem... tq... /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
3Com HomeConnect ADSL Modem Dual Link
Hi... One simple question. Can -CURRENT work with 3Com HomeConnect ADSL Modem Dual Link? tq /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
net-snmp port on -CURRENT?
Hi... I am trying to build net-snmp port on -CURRENT but don't have enough luck with it. Here's the error message on my system: -- cc -DINET6 -O -pipe -march=pentiumpro -Dfreebsd5 -I. -I../.. -I. -I./../.. -I./../../snmplib -I./.. -I.. -c host/hr_storage.c -fPIC -DPIC -o host/.libs/hr_storage.lo host/hr_storage.c: In function `var_hrstore': host/hr_storage.c:526: structure has no member named `m_mbufs' host/hr_storage.c:565: structure has no member named `m_clusters' host/hr_storage.c:565: structure has no member named `m_clfree' *** Error code 1 Stop in /usr/ports/net/net-snmp/work/ucd-snmp-4.2.1/agent/mibgroup. *** Error code 1 Stop in /usr/ports/net/net-snmp/work/ucd-snmp-4.2.1/agent. *** Error code 1 Stop in /usr/ports/net/net-snmp/work/ucd-snmp-4.2.1. *** Error code 1 Stop in /usr/ports/net/net-snmp. *** Error code 1 Stop in /usr/ports/net/net-snmp. *** Error code 1 Stop in /usr/ports/net/net-snmp. *** Error code 1 Stop in /usr/ports/net/net-snmp. -- /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
My mouse is gone...
Hi all... I have just finished installing my fairly recent -CURRENT. And now I lost my PS/2 mouse. My motherboard is an ASUS CUSL-2. I have been reading a thread about the psm disappearance too, but unfortunately I lost the mails :( Can someone please guide me to solve the problem? Thanks a lot /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
No more snapshots of -CURRENT?
Hi all... I have been visiting current.freebsd.org for the past weeks, and see no newer i386 snapshots then 20010618. Does it mean -CURRENT is in no stable condition right now? tq /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: No more snapshots of -CURRENT?
On Thu, Jul 12, 2001 at 02:08:34AM -0500, Alfred Perlstein wrote: newer i386 snapshots then 20010618. Does it mean -CURRENT is in no stable condition right now? current is never stable, if you want stable stil with -stable. :) I KNOW. That's why I put double quotes around the stable word from the first place ;) The first intention was just to ask why aren't there newer snapshots then 20010618. I am thinking of installing newest snapshots on my PC. Thanks anyway... /john Live Free OR Die To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
My network is dead because of this program :(
Dear all... First of all, really sorry for cross-posting... I am running a -CURRENT system (Apr 30th 2001). There is a user in my machine running this small program to DoS my xl0 interface. I doubt that this program is specifically designed for xl cards though. Once the program is started, it starts forking childs I assume. Then after sometime, this messages start popping to my screen: xl0: no memory for rx lists -- packet dropped After going to single user mode, cause I can't kill the offending program once it is running in multiuser mode (even kill -9 won't work on my system), then coming back to multiuser mode, I tried to run it and trace what it does with truss. But, truss didn't seem to output anything at all. Then, I saw the program state in top and it said the program is in mbuf state. I have searched all mailing lists archieves in http://www.freebsd.org/search/search.html#mailinglists but wierdly, there are no articles shown when I enter this as a query: no memory for rx list Can anyone help me trace what the program does? And how can I prevent the program to DoS my network interface? Even when the program is started by unprivileged user, it works, it DoS my network interface. Is this a bug? I have attached the offending program with this mail. Please don't run it on production system! You have been warned! Thank you very much... /john Live Free OR Die x
How is -CURRENT?
Hi folks... Now I am running 20010210-CURRENT. I was wondering, how is the state of -CURRENT? I've checked current.freebsd.org, but there are no newer snapshots than 20010210. Is it safe to make world right now? Do KDE2 apps work flawlessly on newest -CURRENT? If there are people that can say yes to that answer, than I am ready to blow away all my /usr/X11R6 and /usr/local and build everything from scratch, thank you... /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT is bad for me...
On Mon, Feb 12, 2001 at 07:59:03AM -0500, Daniel Eischen wrote: Did you miss the HEADS UP posted to -current? You better read these. Somehow, I just didn't notice that there is a HEADS UP. I have bang my head to the wall because of this sillyness I've done :( I have just reformat my box, and now running: 5.0-20010210-CURRENT I think this is currently the last known good snapshot in current.freebsd.org To get around the installworld problem, do: Too late. I have just, for the first time since running -CURRENT feel the sorrow of running -CURRENT. He3x... But I'm not complaining. I take this as a challenge and as a reminder to not miss any more HEADS UPs ;) Thanks anyway for the help... Dan Eischen /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Failed to build kdesupport2 port
Hi folks...
I am on a FreeBSD 5.0-20010210-CURRENT box. This is a clean system, I
installed it from current.freebsd.org
I tried to build kdesupport2 port, but it failed. Somehow, when checking
for Qt, kdesupport2 configure script died. However, I installed qt 2.2.4
from port cleanly, no errors whatsoever.
My version of /usr/src/contrib/gcc.295/config/freebsd.h is
v 1.32 2001/02/08 05:27:17
BTW the only different file from my system is that I applied this
patch from Maxim Sobolev to /usr/port/Mk/bsd.port.mk:
--- bsd.port.mk 2001/02/08 19:09:54 1.2
+++ bsd.port.mk 2001/02/08 19:15:50
@@ -948,6 +948,14 @@
MAKEFILE?= Makefile
MAKE_ENV+= PREFIX=${PREFIX} LOCALBASE=${LOCALBASE} X11BASE=${X11BAS
E} MOTIFLIB="${MOTIFLIB}" LIBDIR="${LIBDIR}" CFLAGS="${CFLAGS}" CXXFLAGS="${CXXF
LAGS}"
+.if ${OSVERSION} 50
+PTHREAD_CFLAGS=-D_THREAD_SAFE
+PTHREAD_LIBS= "-pthread"
+.else
+PTHREAD_CFLAGS=""
+PTHREAD_LIBS= "-lc_r"
+.endif
+
.if exists(/usr/bin/fetch)
# avoid -A for 2.2 -- it's not ported to that branch
.if ${OSVERSION} 30
Attached is the failure log of my kdesupport2 build.
Am I the only one having this problem?
Thanks...
/john
Script started on Thu Feb 15 11:01:48 2001
[root@dante kdesupport2]# make install
=== Extracting for kdesupport-2.0.1
Checksum OK for kdesupport-2.0.1.tar.bz2.
=== kdesupport-2.0.1 depends on executable: bzip2 - found
=== kdesupport-2.0.1 depends on executable: gmake - found
=== kdesupport-2.0.1 depends on shared library: png.4 - found
=== kdesupport-2.0.1 depends on shared library: jpeg.9 - found
=== kdesupport-2.0.1 depends on shared library: qt2.4 - found
=== Patching for kdesupport-2.0.1
=== Applying FreeBSD patches for kdesupport-2.0.1
=== Configuring for kdesupport-2.0.1
/usr/bin/perl -pi -e "s@TOPSUBDIRS libaps@TOPSUBDIRS@g ; s@odbc libaps@odbc@g"
/usr/ports/converters/kdesupport2/work/kdesupport-2.0.1/configure
/usr/bin/perl -pi -e "s@-version-info 1:1@-version-info 3:0@g"
/usr/ports/converters/kdesupport2/work/kdesupport-2.0.1/mimelib/Makefile.in
creating cache ./config.cache
checking host system type... i386--freebsd5.0
checking target system type... i386--freebsd5.0
checking build system type... i386--freebsd5.0
checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel
checking whether build environment is sane... yes
checking whether gmake sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for a C-Compiler... cc
checking whether the C compiler (cc -O -pipe -mcpu=i686 -march=i686 ) works... yes
checking whether the C compiler (cc -O -pipe -mcpu=i686 -march=i686 ) is a
cross-compiler... no
checking whether we are using GNU C... yes
checking how to run the C preprocessor... cc -E
checking for a C++-Compiler... c++
checking whether the C++ compiler (c++ -O -pipe -mcpu=i686 -march=i686 ) works... yes
checking whether the C++ compiler (c++ -O -pipe -mcpu=i686 -march=i686 ) is a
cross-compiler... no
checking whether we are using GNU C++... yes
checking whether c++ supports -fno-exceptions... yes
checking whether c++ supports -fno-check-new... yes
checking whether c++ supports -Wno-long-long... yes
checking whether c++ supports -fno-builtin... yes
checking whether c++ supports -fexceptions... yes
checking whether c++ supports -frtti... yes
checking how to run the C++ preprocessor... c++ -E
checking whether c++ supports -frepo... yes
checking for ld used by GCC... /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
checking for /usr/libexec/elf/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking for ranlib... ranlib
checking for strip... strip
checking for Cygwin environment... no
checking for mingw32 environment... no
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking whether -lc should be explicitly linked in... yes
checking for objdir... .libs
checking for cc option to produce PIC... -fPIC -DPIC
checking if cc PIC flag -fPIC -DPIC works... yes
checking if cc static flag -static works... yes
checking if cc supports -c -o file.o... yes
checking if cc supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd5.0 ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for dlopen in -ldl... no
Re: -lc_r against shared library (Re: Failed to build kdesupport2 port)
On Thu, Feb 15, 2001 at 02:51:51PM +0200, Maxim Sobolev wrote:
CONFIGURE_ARGS= "LIBS=-pthread"
to kdesupport2/Makefile would help.
There are some way to ``fix'' this problem:
c) Use -lc_r instead of -pthread.
As -pthread will be depreciated, we should use -lc_r for FreeBSD
5.0 and later, shouldn't we?
Yes, it looks like a most appropriate solution to me. If you read -ports,
recently I proposed to add a small patch for the bsd.port.mk to help with
transition process, but have not heard anything back from PW yet.
Either I do it the wrong way, or you are not paying attention to my
first message thoroughly. I HAVE applied your patch to my
/usr/ports/Mk/bsd.port.mk! But still, I failed to build kdesupport2
So, here's the summary of what I have done:
1. Reformat hard drive (cause I have a broken -CURRENT caused by FILE struct
changes)
2. Install from current.freebsd.org a -CURRENT snapshot of 2210
3. cvsup the latest ports tree
4. Applied Maxim Sobolev patch against my /usr/ports/Mk/bsd.port.mk
The patch is:
--- bsd.port.mk 2001/02/08 19:09:54 1.2
+++ bsd.port.mk 2001/02/08 19:15:50
@@ -948,6 +948,14 @@
MAKEFILE?= Makefile
MAKE_ENV+= PREFIX=${PREFIX} LOCALBASE=${LOCALBASE} X11BASE=${X11BASE}
MOTIFLIB="${MOTIFLIB}" LIBDIR="${LIBDIR}" CFLAGS="${CFLAGS}" CXXFLAGS="${CXXFLAGS}"
+.if ${OSVERSION} 50
+PTHREAD_CFLAGS=-D_THREAD_SAFE
+PTHREAD_LIBS= "-pthread"
+.else
+PTHREAD_CFLAGS=""
+PTHREAD_LIBS= "-lc_r"
+.endif
+
.if exists(/usr/bin/fetch)
# avoid -A for 2.2 -- it's not ported to that branch
.if ${OSVERSION} 30
Correct isn't it?
5. Start building my ports
6. Everything from XFree86-4.0.2_6 to qt-2.2.4 build and installed just fine
7. kdesupport2 started bombing error messages
So, if after all of this I SHOULD have not undergone any errors, then the
mistakes is on me, please forgive me for wasting your time and bandwith.
I am only seeking for some enlightenment.
-Maxim
/john
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
-CURRENT is bad for me...
Just finished buildworld on recent -CURRENT. installworld target died with this: === gnu/usr.bin/perl/suidperl install -c -s -o root -g wheel -m 511 suidperl /usr/bin /usr/bin/sperl5 - /usr/bin/suidperl /usr/bin/sperl5.6.0 - /usr/bin/suidperl === gnu/usr.bin/perl/library sed: stdout: Bad file descriptor *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/library. *** 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. *** Error code 1 Stop in /usr/src. Sigh... Now I have an impaired world and kernel that's way out of sync :( I guess I am still lucky enough if this mail can reach the mailing list. This mail only serves as a warning to other typical -CURRENT user like me to be aware that -CURRENT has troubles for the moment... /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
My world is totally broken. Request help...
Please help me to overcome this. My world is totally broken. ps and top don't work. fetchmail, and other program seems to lost STDOUT. After failed installworld, I reboot my machine, blew away /usr/obj and make clean in /usr/src. Now when I want to rebuild the world, make just don't want to do its jobs anymore :( Now, what should I do. This is -CURRENT as of today... /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Is -CURRENT in bad shape?
Now I'm in the middle of make -j10 buildworld. Is -CURRENT in bad shape? I'm planning to blow away all /usr/local and /usr/X11R6 to build "a whole new world", again... ;) Should I wait for a couple of hours/days? Thanks... /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Is -CURRENT in bad shape?
On Sun, Feb 11, 2001 at 10:39:56PM -0800, Alfred Perlstein wrote: Current from Sat Feb 10 17:00:18 looks ok, there were just some patches to the scheduler but no one has complained yet. Let us know. :) Thanks for the fast reply. I really need it. OK... buildworld seems to be running ok right now. I'll let you know if something goes wrong, of course... ;) BTW, today I saw post from John Baldwin to remove device random from the kernel config. Then, other post replied that this is a good thing, mpg123 playing went a lot better for him, well at least, that's what he said. If this is so, then why is there a device random line in GENERIC kernel? Do we really need device random? Thanks... -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failed. again...
Latest -CURRENT buildworld target failed again with this message: === share/monetdef grep -v '^#' /usr/src/share/monetdef/en_US.ISO_8859-1.src en_US.ISO_8859-1.out grep -v '^#' /usr/src/share/monetdef/nl_NL.ISO_8859-1.src nl_NL.ISO_8859-1.out grep -v '^#' /usr/src/share/monetdef/ru_RU.KOI8-R.src ru_RU.KOI8-R.out === share/msgdef grep -v '^#' /usr/src/share/msgdef/en_US.ISO_8859-1.src en_US.ISO_8859-1.out grep -v '^#' /usr/src/share/msgdef/nl_NL.ISO_8859-1.src nl_NL.ISO_8859-1.out grep -v '^#' /usr/src/share/msgdef/ru_RU.KOI8-R.src ru_RU.KOI8-R.out === share/numericdef make: don't know how to make nl_NL.ISO_8859-1.out. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error I thought that this problem has been fixed. Am I the only one experiencing this? /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failed
Dunno whether this happens only to me, but in my machine, latest -CURRENT buildworld target failed with this message: === share/monetdef grep -v '^#' /usr/src/share/monetdef/en_US.ISO_8859-1.src en_US.ISO_8859-1.out grep -v '^#' /usr/src/share/monetdef/nl_NL.ISO_8859-1.src nl_NL.ISO_8859-1.out grep -v '^#' /usr/src/share/monetdef/ru_RU.KOI8-R.src ru_RU.KOI8-R.out === share/msgdef grep -v '^#' /usr/src/share/msgdef/en_US.ISO_8859-1.src en_US.ISO_8859-1.out grep -v '^#' /usr/src/share/msgdef/nl_NL.ISO_8859-1.src nl_NL.ISO_8859-1.out grep -v '^#' /usr/src/share/msgdef/ru_RU.KOI8-R.src ru_RU.KOI8-R.out === share/numericdef make: don't know how to make nl_NL.ISO_8859-1.out. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildkernel target died...
On Mon, Feb 05, 2001 at 01:30:26AM -0800, Doug Barton wrote: In order to follow -current you have to follow freebsd-current mailing list and the commit logs. Cameron recently committed some new stuff, then committed the makefile for it a little while after. This was all described on the lists. If you're using cvsup, try it again. If you're using cvs, make sure you include the -d flag to update. Sorry... I am subscribed to freebsd-current and commit logs mailing list. But sometimes I just skip reading those commit logs :) Will try tommorrow... /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildkernel target died...
Latest -CURRENT buidkernel died with this error messages: === sound/driver === sound/driver/ad1816 rm -f setdef0.c setdef1.c setdefs.h setdef0.o setdef1.o snd_ad1816.ko snd_ad1816.kld ad1816.o @ machine symb.tmp tmp.o bus_if.h device_if.h isa_if.h pci_if.h ac97_if.h channel_if.h feeder_if.h mixer_if.h === sound/driver/cmi cd: can't cd to /usr/src/sys/modules/sound/driver/cmi *** Error code 2 Stop in /usr/src/sys/modules/sound/driver. *** Error code 1 Stop in /usr/src/sys/modules/sound. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/DANTE. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-CURRENT and -STABLE against XFree86 4.0.2 problem
Hi... Forgive me if I'm being such a nuisance. I wish I can help but I don't have the strength to :( I have seen many responses that prove that there is something WRONG with agp support both in -CURRENT and -STABLE if used against XFree86 4.0.2. Here is another one: - Forwarded message from Andrea Campi [EMAIL PROTECTED] - From: Andrea Campi [EMAIL PROTECTED] To: Stijn Hoop [EMAIL PROTECTED] Cc: John Indra [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: -CURRENT and XFree86 4.0.2 problem Date: Tue, 30 Jan 2001 03:04:30 +0100 I suspect (from the error log) that this has something to do with Intel 810 chipset and -CURRENT agp module. FWIW, I have the same problem with a -STABLE from jan. 20th. So the bug is probably also in the -STABLE agp module, or else it is XFree86-4.0.2_5 (I also blew away /usr/local and /usr/X11R6 before installing it). I have been just bitten by the same problem, on -STABLE. Having rebuilt the world I can not swear it's not a problem in the kernel, but: /usr/src/sys/pci/agp.c so, either changes to other parts of the system broke agp, or the port is indeed broken. Quite a few changes to AGP GART configuration went in from 4.0.1 to 4.0.2, and it's not very clear if they DTRT. Anybody has any hint, or at least the knowledge to investigate? If so, I will send logfiles etc. Otherwise I will have to try and get everything back to the time when we had 4.0.1... Bye, Andrea -- Failure is not an option. It comes bundled with your Microsoft product. - End forwarded message - I have open up a PR, and I think that this problem is critical and must be addressed ASAP. Attached is a log file which I hope can be a help even maybe a little one. FYI Hardware is Intel 815 with latest -CURRENT as I'm writing this mail. Thanks... /john XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Tue Jan 30 13:08:04 2001 (==) Using config file: "/etc/X11/XF86Config" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout "Simple Layout" (**) |--Screen "Screen 1" (0) (**) | |--Monitor "My Monitor" (**) | |--Device "My VGA Card" (**) |--Input Device "Mouse0" (**) |--Input Device "Keyboard1" (**) Option "AutoRepeat" "500 30" (WW) Option "XkbCompat" requires an string value (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (**) FontPath set to "unix/:7100" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (II) xf86ReadBIOS(f8000, e80, Buf, 2)- b4 09 2c fb... (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8000f948, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1130 card 1043,8027 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,1132 card 1043,8027 rev 02 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 1043,8027 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 1043,8027 rev 01 class 0c,05,00 hdr 00 (II) PCI: 01:0a:0: chip 10b7,9200 card 10b7,1000 rev 6c class 02,00,00 hdr 00 (I
DEVFS newbie...
I noticed that DEVFS has been the default in GENERIC kernel. I have been -CURRENT tracker for the past couple of months and things like DEVFS is still new to me. Thus, a couple of questions arise and I am very glad if someone want to explain it to me, or maybe point to docs that I should read. 1. Say I want to use DEVFS, what should I change? /etc/fstab? Should I nuke the current /dev? 2. If something change to the source tree's MAKEDEV, what should I do? Thanks... /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failed
Latest -CURRENT died with this error messages: -- /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of `__sys_aio_suspend' discards qualifiers from pointer target type /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for argument 3 of `__sys_aio_suspend' *** Error code 1 cc -fpic -DPIC -O -pipe -mcpu=i686 -march=i686 -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc_r/uthread/uthread_attr_getdetachstate.c -o uthread_attr_getdetachstate.So /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c: In function `_aio_suspend': /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: warning: passing arg 1 of `__sys_aio_suspend' discards qualifiers from pointer target type /usr/src/lib/libc_r/uthread/uthread_aio_suspend.c:45: incompatible type for argument 3 of `__sys_aio_suspend' *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-CURRENT and XFree86 4.0.2 problem
Dear all... First of all, sorry for cross-posting cause I don't know which mailing list is the most appropriate for this kind of question and I think this affects all mailing list I send this mail to. Running -CURRENT with world and kernel of: Thu Jan 18 13:04:05 JAVT 2001 Blew away all /usr/X11R6 and /usr/local to have fresh ports on my system. Then, I install XFree86-4.0.2_5. Now, whenever I enter X (using startx) and try to go to console (Ctrl+Alt+Fx) and then try to get back to X (Alt+F9), X died :( I suspect (from the error log) that this has something to do with Intel 810 chipset and -CURRENT agp module. Attached is /var/log/XFree86.0.log Thanks... /john XFree86 Version 4.0.2 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 18 December 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Module Loader present (==) Log file: "/var/log/XFree86.0.log", Time: Tue Jan 23 09:27:23 2001 (==) Using config file: "/etc/X11/XF86Config" Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout "Simple Layout" (**) |--Screen "Screen 1" (0) (**) | |--Monitor "My Monitor" (**) | |--Device "My VGA Card" (**) |--Input Device "Mouse0" (**) |--Input Device "Keyboard1" (**) Option "AutoRepeat" "500 30" (WW) Option "XkbCompat" requires an string value (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (**) FontPath set to "unix/:7100" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (II) xf86ReadBIOS(f8000, e80, Buf, 2)- b4 09 2c fb... (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.0.2, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1130 card 1043,8027 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,1132 card 1043,8027 rev 02 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 1043,8027 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 1043,8027 rev 01 class 0c,05,00 hdr 00 (II) PCI: 01:0a:0: chip 10b7,9200 card 10b7,1000 rev 6c class 02,00,00 hdr 00 (II) PCI: 01:0b:0: chip 1274,5880 card 1274,2000 rev 02 class 04,01,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: "scanpci" (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor="The XFree86 Project" compiled for 4.0.2, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0xd000 - 0xd0ff (0x100) IX[B] [1] -1 0xd400 - 0xd4ff (0x100) IX[B] [2] -1 0xd800 - 0xd8ff (0x100) IX[B] [3] -1 0xdc00 - 0xdcff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0xf680 - 0xf6ff (0x80) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xf7f0 - 0xf7ff (0x10) MX[B] (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x00 (VGA_EN is cleared)
Still... hwptr went backwards...
Dear all... Just a few days ago, I thought I saw a few posts that state the latest -CURRENT emits less hwptr went backwards messages. Apparently this doesn't happen on my system :( Currently running KDE 2.0.0 with XFree86 4.0.1 and when I play MP3, and want to lock my screen, MP3 playing choked heavily. If disk is heavily access, MP3 playing choke more worse. $ cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 10 2001 18:06:06 Installed devices: pcm0: AudioPCI ES1371 at io 0xd400 irq 9 (1p/1r channels duplex) $ dmesg Copyright (c) 1992-2001 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 5.0-CURRENT #0: Wed Jan 10 18:07:41 JAVT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DANTE Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 737023115 Hz CPU: Pentium III/Pentium III Xeon/Celeron (737.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 133083136 (129964K bytes) avail memory = 125952000 (123000K bytes) Preloaded elf kernel "kernel" at 0xc0312000. Pentium Pro MTRR support enabled Using $PIR table, 10 entries at 0xc00f0ed0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82815 (i815 GMCH) Host To Hub bridge at pcibus 0 on motherboard pci0: PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) SVGA controller mem 0xf700-0xf707,0xf800-0xfbff irq 11 at device 2.0 on pci0 pcib1: PCI-PCI bridge at device 30.0 on pci0 pci1: PCI bus on pcib1 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xd800-0xd87f mem 0xf680-0xf680007f irq 9 at device 10.0 on pci1 xl0: Ethernet address: 00:50:da:95:85:dc miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: AudioPCI ES1371 port 0xd400-0xd43f irq 9 at device 11.0 on pci1 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 ATA100 controller port 0xb800-0xb80f at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: serial bus, SMBus at 31.3 (no driver attached) atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5" drive on fdc0 drive 0 ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0401 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources unknown: PNP0700 can't assign resources unknown: PNP0f13 can't assign resources unknown: PNP0303 can't assign resources unknown: PNP0c02 can't assign resources ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 14324MB QUANTUM FIREBALLlct15 15 [29104/16/63] at ata0-master UDMA33 acd0: CDROM SONY CDU4811 at ata0-slave using PIO4 Mounting root from ufs:/dev/ad0s2a pcm0: hwptr went backwards 64 - 32 pcm0: hwptr went backwards 192 - 4032 pcm0: hwptr went backwards 384 - 192 pcm0: hwptr went backwards 2752 - 2720 pcm0: hwptr went backwards 192 - 32 pcm0: hwptr went backwards 2304 - 2048 pcm0: hwptr went backwards 2176 - 2080 pcm0: hwptr went backwards 2112 - 2048 pcm0: hwptr went backwards 2112 - 1856 pcm0: hwptr went backwards 64 - 4064 Sound card is Creative SoundBlaster Vibra 128. Motherboard ASUS CUSL2. /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld Problems at NTP
On Fri, Jan 05, 2001 at 12:37:43AM -0800, Crist J. Clark wrote: I'd really like to get this working so I can play with some kernel mods I made last week. Any ideas? I've just finished building world and kernel with recent -CURRENT. Didn't encounter any problem though. % uname -a FreeBSD dante.naver.co.id 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Jan 5 13:19:17 JAVT 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DANTE i386 /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make buildkernel failed
On Thu, Jan 04, 2001 at 10:07:37AM +, Pierre Y. Dampure wrote: Hmmm. It looks like there were other bits missing... the MELCO LUATX entry was replaced in the last commit to usbdevs by two new entries, LUATX1 and LUATX5, but if_aue.c was not modified to reflect this. You need to do this manually. If the goal is to make modifications in one place only (and that certainly seems to be the case, hence usbdev2h.awk), maybe what's required is a new field in the usbdevs table, so that the tables used by the various *.c get generated automagically too? I really really wish I could understand this :) I'm not a C programmer, and I'm just a FreeBSD user tracking -CURRENT. But I am learning, so that one they I can help commit a helpful patches :) /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make buildkernel failed
Dear all... Recent -CURRENT make buildkernel target died with this message: === uscanner cc -O -pipe -g -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c/usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: `USB_PRODUCT_EPSON_1640' undeclared here (not in a function) /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: initializer element is not constant /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: (near initialization for `scanner_ids[45].product') *** Error code 1 Stop in /usr/src/sys/modules/uscanner. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/DANTE. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. /john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -CURRENT kernel build problem...
On Tue, Dec 19, 2000 at 10:16:01AM +0200, Ruslan Ermilov wrote: If I remeber correctly, someone else reported this was caused by phk's change staticizing something... Sorry, I do not recall this in details, and I don't have a fresh -CURRENT. OK then... Any workaround or fix coming shortly to overcome this guys? BTW... I am very interested to become one of you guys, the FreeBSD committers. I mean it. I am ready to devote my life to FreeBSD (if this phrase is not too much :) ). Now I am still trying to finish my Bachelor degree. In the mean time I am working as a Network Administrator for a company in Indonesia. Soon after I finish my school, I will have plenty of time to study C and maybe try to understand piece by piece FreeBSD codes, maybe not in all section, and if I am qualified enough, I'd like to contribute something to FreeBSD. What I need now is a guidance. I think I'm not a very novice programmer. For my bachelor degree, I'm trying to make a Natural Language enabled (at semantic level) search engine. Planning to use Perl to build the beast :) Where can I start to dig more information about OS, efficient programming with C, etc. to help me get what I want? Sorry, I think this is becoming out of topic, but I'm very glad to have said my wish :) Thanks a lot... Regards, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent -CURRENT kernel build problem...
On Tue, Dec 19, 2000 at 09:22:57AM +0100, [EMAIL PROTECTED] wrote: Can you try the appended patch and tell us how it goes? Yeah... finally, my world is in sync with the kernel, what a joy :) Until know... the system is pretty stable. Will this be committed to the tree soon? Thank you very much... Regards, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Recent -CURRENT kernel build problem...
Dear all... Has anyone noticed this problem? Or is it just happening to me? On make buildkernel (with -CURRENT just cvsuped a few minutes ago) and the generic config KERNEL; make depend; make; cycle, the kernel build failed with this message: -- cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../dev -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel agp_amd.o: In function `agp_amd_alloc_gatt': agp_amd.o(.text+0x67): undefined reference to `M_AGP' agp_amd.o(.text+0x89): undefined reference to `M_AGP' agp_amd.o(.text+0xd5): undefined reference to `M_AGP' agp_amd.o(.text+0x105): undefined reference to `M_AGP' agp_amd.o(.text+0x112): undefined reference to `M_AGP' agp_amd.o(.text+0x234): more undefined references to `M_AGP' follow *** Error code 1 Stop in /usr/src/sys/compile/DANTE. -- Please help, my kernel and userland is badly not in sync ;) Attached is my kernel config file. Thank you... Regards, John ident DANTE machine i386 cpu I686_CPU maxusers256 options INET options FFS options FFS_ROOT options SOFTUPDATES options COMPAT_43 options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG options KTRACE options SYSVSHM options SYSVMSG options SYSVSEM options SHMMAX=33554432 options SHMALL=16384 options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV options ATA_STATIC_ID options ATA_ENABLE_ATAPI_DMA options USER_LDT options IPFILTER options IPFILTER_LOG options TCP_DROP_SYNFIN options TCP_RESTRICT_RST options VESA options NMBCLUSTERS=16384 options SC_DISABLE_REBOOT options NOBLOCKRANDOM device isa device pci device fdc device ata device atadisk device atapicd device atkbdc 1 device atkbd device psm device vga device splash device sc 1 device npx device apm device sio device ppc device ppbus device lpt device plip device ppi device miibus device xl device random device loop device ether device tun device pty device md device bpf device vn device snp device pcm device agp
Re: My cdrom disappeared with the new ata-all.c :-(
On Fri, Nov 10, 2000 at 08:56:22AM +0200, Reinier Bezuidenhout wrote: |I've upgraded my 5.0-current to the sources of about 2 days ago ... before |then my CD-ROM was working just fine (detected etc), since the upgrade |my kernel too fails to detect the cdrom. One out of the 5 times I rebooted, |it found the cdrom. What seems strange is that if it fails to detect the |cdrom, my hardrive LED stays on the whole time. # uname -sr FreeBSD 5.0-20001108-CURRENT I confirm the same situation happened to me. - HD LED stays on all the time. - dmesg doesn't even show any living sign of my CD-ROM which worked fine under 4.1.1-STABLE. I'm using the GENERIC kernel which contain support for atapicd - After a few hours my system went very slow. I'm typing this message in a Pentium III 733 MHz but it felt like I'm on Intel 80386 :) |This is not on a laptop but on an Intel BX440 chipset motherboard, PII. I'm using ASUS PC133 CUSL2 motherboard Regards, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sound support in -CURRENT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi FreeBSD fans and developers... This is my first question in -CURRENT. Yesterday was the first time I tried to follow the -STABLE line. And I must admit that once again FreeBSD amazed me ;) Running -STABLE rite now (I used to run only -RELEASE before cause I'm haunted by the feeling that the upgrading process will be very complicated, but that's my mistake... The upgrading process was really simple and easy... ;) ) Now to the real question... I have a Compaq Deskpro EP system with onboard Intel 810e AGP VGA Card and onboard sound support (which maybe is AC97 or something similar). After running -STABLE I can use my VGA Card. How about the sound card? Does - -CURRENT support the sound card? Cause if -CURRENT can make my sound card sings, I'd love to give it a try. After all, this isn't a production machine. Regards, John Indra -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.2 (FreeBSD) Comment: Be the best! iD8DBQE5oNNhxcp0HIxafmQRAnm/AJsH99EctqjU2YukF3o0PfOIxNAx4ACgvmx0 YhugvQc/j2TtVcbHRvi6zrk= =wwoJ -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
