Could not find package - using ports
Hi everyone, I'm upgrading all the ports I have installed and the command I used is portupgrade -aP, exluding ruby and portupgrade itself. Sad news is that for every single package it tries to fetch it doesn't find anything, so it uses the ports, and it needs lots of time to compile everything. (gnome, X, firefox are not so fast to compile!) Am I doing something wrong or /Luca]$ ssh preso...@lxplus.cern.ch *** PINE 4.58 COMPOSE MESSAGE Folder: INBOX 4 Messages + To : freebsd-questions@freebsd.org Cc : Attchmnt: Subject : Could not find package - using ports - Message Text - Hi everyone, I'm upgrading all the ports I have installed and the command I used is portupgrade -aP, exluding ruby and portupgrade itself. Sad news is that for every single package it tries to fetch it doesn't find anything, so it uses the ports, and it needs lots of time to compile everything. (gnome, X, firefox are not so fast to compile!) Am I doing something wrong or are the packages really missing? I'm using freeBSD 7.0-release on a i386 architectyre and I'm trying to update the ports after having done portsnap fetch update, so it should be trying to install the latest version of the ports. Thank you, Luca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
R: Could not find package - using ports
The reason that portupgrade -P was not using packages is that, by default it fetches packages built against the tree that's on the install disks, so there wont be any for updated ports. You can set portupgrade to fetch packages for the 7-stable development branch (you can google for how to do this). For the most part this will work, but occasionally there will be library problems. Thank you, now it's clear. I will try this as soon as I can. Luca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Various X errors (difficult to see)
Hi, I have a freebsd 7.0 release with xorg 7.3 installed on a i386 with a NVIDIA GeForce Go 7300 Official nvidia drivers installed and apparently no problems. In the xorg.0.log file there aren't any errors, glx is correctly loaded etc.. My system starts without X and then I use startx to start X server and KDE3.5 (if I'm not wrong about the version). Some errors are written on the console and I'm not able to see them! To see them I have to stop X (with ctrl+ bkspc) and use scroll lock to see what's there. I found the console full of X error: bad window parameter (and some numbers and parameters which I can't remember) Then I find a lots of warnings about kde problems (about loading arts daemons). Except for these errors that I wouldn't be seeing if logging in directly in a graphical environment everything seems to work fine. So I have some questions: is this way of reporting errors correct? Can this be the related to the fact that when I try to use compiz-fusion it starts but it's way too slow and uses a lot of cpu? Should I worry about these errors? How can I solve them?? (They seem really too generic) Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Various X errors (difficult to see)
You should run startx and redirect the output to a file and check the errors and then try to fix them. To do this try: startx /tmp/somexerrorlogfile 21 Done that! Here-s the first error(s): DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket Warning: kbuildsycoca is unable to register with DCOP. kbuildsycoca running... DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... DCOP Cleaning up dead connections. Reusing existing ksycoca Is it something wrong in /etc/hosts?? Then I get lots of line(130!) like : kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2' kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/zip' kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-7z' kbuildsycoca: WARNING: '/usr/local/share/applications/themus-theme-applier.desktop' specifies undefined mimetype/servicetype 'application/x-gnome-theme-installed' Then finally: DCOP Cleaning up dead connections. Launched ok, pid = 1283 ICE default IO error handler doing an exit(), pid = 1222, errno = 0 There are already artsd objects registered, looking if they are active... Error: Can't add object reference (probably artsd is already running). If you are sure it is not already running, remove the relevant files: /tmp/ksocket-Luca/Arts_SoundServerV2 /tmp/ksocket-Luca/Arts_SoundServer /tmp/ksocket-Luca/Arts_SimpleSoundServer /tmp/ksocket-Luca/Arts_PlayObjectFactory /tmp/ksocket-Luca/Arts_AudioManager Then, every time I launch a program that open a new window I get: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x66 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
R: Various X errors (difficult to see)
Is it something wrong in /etc/hosts?? It could be your /etc/hosts or /etc/hosts.allow or you may need to add: -listen_tcp to your startx commandline. I supposed the problem was there! I'll look at -listen_tcp and at hosts.allow. I have doubts about setting hosts. X used to give me errors about not being able to connect (but still worked!). Then I tried to set up hosts correctly and now here's the new problem. I've read man hosts, read the handbook and googled around but it's not very clear what I should write in this file. My hostname is lucy. It's a laptot that eventually connects to the nearest available network. So it isn't part of a domain or something like that. In the end I set up the concerned hosts lines to: ::1 localhost localhost.my.domain lucy 127.0.0.1 localhost localhost.my.domain lucy Is it correct? Why should I leave localhost.my.domain ? These messages are errors telling you the window manager cannot manage these mimetypes. Did you remove any ports for handling these types of archive files? No, I didn't remove anything! But I copied just 3 warnings. There were 130 of them related not only to archive files handling but almost to everything. This error refers to the artsd daemon already running, or the system thinks this daemon is running. You should open a terminal window and do: ps -ax|grep -i art and see if the artsd daemon is running or not. If it is not, you may need to force it to start. I'll try that later! When you say every time you launch a program how exactly are you trying to launch a program? Either with the kde launch program, either launching the file in a xterm, either when firefox opens a new popupAnd I think those are pretty much all the possible ways I explored! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Various X errors (difficult to see)
This error refers to the artsd daemon already running, or the system thinks this daemon is running. You should open a terminal window and do: ps -ax|grep -i art and see if the artsd daemon is running or not. If it is not, you may need to force it to start. I'll try that later! If I do ps -ax etc... I get: 1185 ?? S 0:00.03 kdeinit: kdeinit: klauncher --new-startup (kdeinit) 1187 ?? S 0:00.28 kdeinit: kdeinit: kded --new-startup (kdeinit) 1206 ?? S 0:00.49 /usr/local/bin/artsd -F 10 -S 4096 -s 60 -m artsmessage -c drkonqi -l 3 -f 1106 v0 I+ 0:00.00 /bin/sh /usr/local/bin/startx 1131 v0 I 0:00.01 /bin/sh /usr/local/bin/startkde 1328 p0 R+ 0:00.00 grep -i art I think that 1206 is the right daemon and is correctly running. Correct? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Tuning make.conf
Hi everyone! I was starting to think to recompile everything for my pc to speed up everything. I started googling and I found almost nothing about how to change make.conf on bsd. Almost everything was about Gentoo, somehow not unsurprisingly. The first thing I noticed is that for linux all the instructions are about doing CFLAGS= value while it seems from /etc/share/examples/make.conf that in bsd I don't need . Is it correct? Second question: If I set MAKEOPTS= -j 3 will that be used when portupgrading? (It's really to slow otherwise!) Third question...The most difficult..Which are the best flags for my machine? (freebsd 7.0-RELEASE with an intel centrino core2 duo) I have seen in the /examples/etc/make.conf that one of the possible CPUTYPE is core2 which looks to me as the right one but a geekier friend of mine that lives inside gentoo-linux told me that this option is unknown is gcc 4.2 and will be working from gcc4.3, so he told me to use prescott. And what do I have to set to make gcc aware of the type of CPU I have? CPUTYPE= cpu and then CFLAGS= --O2 -pipe (etc..) or should I not write the cputype and then do: CLFAGS= -march=mycpu --O2 etc Can someone give me some advice on how to configure this file? Or can you provide me some documentation? Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Tuning make.conf
You're *really* wasting your time. I supposed that! Your system is doing no cpu cycles at all for most of the time anyway. [cut]Also, makeopts and -pipe just make _compiling_ faster, not the applications themselves!!!. I agree with everything. In any case I think that a faster compiling will really be a good thing. I have been reading another time the man of make.conf and I still have some doubts. Neither in the example either in the man page there is any reference to MAKEOPTS. Changing from -j1 to -j3 would really be a huge difference! To be able to set this is very important. Then I don't want an ultra tweaked make.conf like gentooers do. Just a reasonable one. (And you have convinced me, I won't recompile everything. Just to have a good compiling when I will be upgrading) I have some doubts about the correct syntax, the man is ambiguous in this point. If I write CPUTYPE= core2 will it automatically sets all the best safe CFLAGS for my core or just set the -march=core2 Should my make.conf be like: MAKEOPTS==-j3 CPUTYPE=core2 CFLAGS= --O2 -pipe -fno-strict-aliasing or just: MAKEOPTS==-j3 CPUTYPE=core2 or maybe: MAKEOPTS==-j3 CPUTYPE=core2 CFLAGS+= --O2 -pipe -fno-strict-aliasing Please take a look at the following pages, they have a lot more information about this matter ;) http://funroll-loops.info/ http://bugs.gentoo.org/show_bug.cgi?id=74072 Actually that's really funny!! I think that's why there are so many pages about gentoo and almost none about other OSes. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Tuning make.conf
Isn't -j depend on how many cpu/core and a faster harddisk / raid? Yes, it is. But with j1 you have only one job running at a time. On a dual core you can really easily running at least two jobs at the same time. Then I've read a number of ideas about which is the relation between the number of cores and the optimal number of jobs. I have been suggested something between n+1 and 2n+1 Of course the optimal number of jobs depends on the disk speed and similar. But switching between 1 and 3 gives something like halving the time needed to compile everything. Maybe it's possible that when building the kernel it gives some problem, but I'm thinking about compiling ports. Or does portupgrade automatically chooses which -j to use? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
wpi driver patches
Hi, It's still me. I have read past posts about the patches available for the wpi intel3945abg driver found at: http://people.freebsd.org/~thompsa/wpi_releng7.diff I see that it's a diff between the newest version and a version dated:2 february 2008. The wpi drivers I have are from: www.clearchain.com/wiki/FreeBSD_Intel_3945abg_WPI_Wireless_Driver and are last updated in november. If I try to apply the patches with #patch wpi_releng7.diff I get lots of errors. Hunk #1 failed at 75. Hunk #2 failed at 158. Hunk #3 failed at 188. Hunk #4 failed at 198. Hunk #5 succeeded at 212 (offset 1 line). Hunk #6 succeeded at 220 with fuzz 1 (offset 1 line). Hunk #7 succeeded at 300 with fuzz 2 (offset -1 lines). Hunk #8 failed at 461. Hunk #9 failed at 507. and so on for lots of line... When coming to the last file(if_wpivar.h) It tells me: Reversed (or previously applied) patch detected! Assume -R? [y] Any answer I give will give some error. Of course after that if I try to compile it gives lots of error. All that to say that it looks to me like the wrong patch for the drivers I have. Where can I find more updated drivers to which I can apply these patches? Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: wpi driver patches
The patches are for the RELENG_7 sources. I could figure that from the name. Where can I find a list of which version are available and where? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Tuning make.conf
Thank you for your answers, you have been very clear! I'm still not into recompiling the kernel for the moment! I will have a look at the way to speed up the various ports building with the gmake. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
selected port (devel/root) is marked as broken
Hi, I often use have to use root a program that has been ported to freebsd. If I try portinstall or I go into the directory and do make /make install I get selected port is marked as broken: Does not compile Or maybe a slightly different error with the same meaning.(I'm not on that machine now so I cannot cut and paste) That's ok, but I want to have root on freebsd to be able to use that machine more often. I downloaded the sources from root.cern.ch then I tried to compile them. The suggested way is to use a provided script where you type the OS and the arch of your machine and it sets up everything for you. But this script supports only freebsd4/5/6, not 7.0 which I'm currently using. I tried telling him it's 6 but then when compiling I get some errors, as announced by the previous messages! What can I try to be able to compile it? Will that be hard to do? Do you know if somebody is already working at it and give me some link to them? Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: selected port (devel/root) is marked as broken
On Wed, 12 Mar 2008, Mel wrote: It fails on gcc3 specific classes. FreeBSD 7 uses gcc 4.x, so the problem lies with root developers. Or...you could install lang/gcc34, then: make -DTRYBROKEN CC=gcc34 CXX=g++34 I'm not sure it'll work though. Well, on other OSes they have been compiling new releases with gcc4.2 without any problems for months, so it's not a gcc problem. I have discovered that someone has already submitted a case to the root developing team in middle january. They think the problem lies within the gcc command line options, but from that moment on no new updates are available. I renewed the request to them. So that now they will know that there are 2 people using both root and fbsd! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
WLan randomly suffering from heavy package lost
Hi everyone. I'm currently running freebsd-7.0-release GENERIC on a dell Inspiron 6400 (i386). I have a problem when networking via wifi. I have an intel 3945abg integrated card and I'm using the wpi drivers. I can connect to my wlan but after one minute or so of perfect connection the network starts to be terribly slow. I have tried pinging and I discovered that I have a 60% package lost when pinging something like google or other sites, that goes up to 90% or more when I increase the package size. When pinging my router or other computers inside my network I get even worse performances. (Something like 97% package lost or 100% if increasing the package size to something like 1400) With other OSes in my pc everything is fine, other pcs connect without problem. If I connect via etherneth to the same hub where the wifi transmitter is connected everything is fine. I have tried adding to resolv.conf, automatically generated by dhclient, the addresses of the DNSs of my ISP and browsing the internet has become a liiitle better, but still very far from the normal speed. And connecting to other pcs inside my network is still a pain.. Any idea? Thank you, Luca resolve .conf: nameserver 192.168.1.1 (my router) nameserver ...(my ISP DNS) #ifconfig wpi0 wpi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:1b:77:23:a3:9e inet6 fe80::21b:77ff:fe23:a39e%wpi0 prefixlen 64 scopeid 0x1 inet 192.168.1.250 netmask 0xff00 broadcast 255.255.255.255 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/24Mbps) status: associated ssid Maldives channel 6 (2437 Mhz 11g) bssid 00:11:95:18:83:45 authmode OPEN privacy OFF txpower 50 bmiss 7 scanvalid 60 protmode CTS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
