X.org's radeon(4x) slowness
I apologize but I can't put this post in the thread. This should be a reply to the post from Jeremie Le Hen on Thu May 31 22:19:55. Actually we are both using the X.org's radeon driver with: Option AccelMethod EXA According to radeon(4x) manpage, EXA is supposed to be faster than the traditional mode XAA but it is also newer and possibly unstable. Removing this option or switching back to the VESA driver solves the slowness. This option is not selected in my configuration but is is slow since the upgrade to X.org 7.2 with firefox. I have alse rebuild firefox after all was rebuild. It is only with Firefox. I have the following modules loaded. Loaddbe # Double buffer extension Loadextmod Loadglx The card is a Radeon 9250 AGP. What can I try? -- regis ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestion: force removal and reinstallation of eaccelerator on php upgrade
Xin LI ha scritto: I usually use portupgrade -fr lang/php5, but I think it may worthy to just bump PORTREVISION across PHP upgrade. Every php extension (optimizer, pecl, accelerator and so on) needs to be recompiled after updating base PHP. I cannot bump all ports when php4 or php5 is updated, be serious :-) Recursively updating all the extensions is the right thing you have to do. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [net/samba3] Upgrade to Samba 3.0.25a
On Tue, Jun 05, 2007 at 03:54:25PM -0700, Doug Barton wrote: I think it's very reasonable, and well in keeping with FreeBSD tradition, to delay upgrading to a new release of ported software until the maintainer is convinced that it's safe to do so. I have Yes, but on the other hand it is the server admin's job to test new software and to decide if and when he starts to deploy it on his production machines. And what about those users/admins who want to test new samba versions to actively help the samba team with improving the software? They would have to modify the port on their own to get the newest version. To be able to install and test brand new software (without being forced to do so!) is one of the best features of FreeBSD's ports system. If people want to play it safe, they can still use Debian/RHEL/whatever. :) Uwe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestion: force removal and reinstallation of eaccelerator on php upgrade
On Wed, 06 Jun 2007 09:33:35 +0200 Alex Dupre [EMAIL PROTECTED] wrote: Xin LI ha scritto: I usually use portupgrade -fr lang/php5, but I think it may worthy to just bump PORTREVISION across PHP upgrade. Every php extension (optimizer, pecl, accelerator and so on) needs to be recompiled after updating base PHP. I cannot bump all ports when php4 or php5 is updated, be serious :-) Why ? We did this in the past for enough ports, we do it for claws-mail-*, etc. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect signature.asc Description: PGP signature
Ports Index
Hello, I have this error when building a port index. Updating the ports index ... Generating INDEX.tmp - please wait..astk-client-1.5.0.1_2: /usr/ports/shells/bash2 non-existent -- dependency list incomplete === cad/astk-client failed It looks as though bash2 has been removed from the ports collection. Is there a fix for this? Thanks David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suggestion: force removal and reinstallation of eaccelerator on php upgrade
Quoting Alex Dupre [EMAIL PROTECTED] (from Wed, 06 Jun 2007 14:30:38 +0200): Ion-Mihai Tetcu ha scritto: Why ? We did this in the past for enough ports, we do it for claws-mail-*, etc. Do we bump every p5-* port when we update perl? No, but you are supposed to update them. Here is even more complex: if I update php4, why should php5 users update their extensions? There is no reason. And only a minimal part of the extensions will effectively require an update, so it's simpler to deal with them only when a breakage occurs. As a data point: the claws-mail plugins are bumped because the plugins don't startup when they are not recompiled. They contain the claws mail version number and bail out if the compiled in one is not equal to the version number of the currently running claws-mail. So anyone using plugins has to update them on each claws-mail update. The portrevision is bumped to trigger this explicitly. This way we also get suitable packages (but I don't remember if this would be the case anyway). My advise would be to do the same with those ports, which show similar behavior. Regarding php and eaccelerator: I always recompile eaccelerator by hand when I update php, so I would not mind if the revision of eaccelerator would be incremented on each version bump of php (disclaimer, I didn't follow this discussion and stumbled upon this specific mail only by accident). Bye, Alexander. -- Cthulhu for President! (If you're tired of choosing the lesser of two evils.) http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Index
On Wed, 06 Jun 2007 13:12:46 +0200, Thomas Spreng wrote David wrote: Hello, I have this error when building a port index. Updating the ports index ... Generating INDEX.tmp - please wait..astk-client-1.5.0.1_2: /usr/ports/shells/bash2 non-existent -- dependency list incomplete === cad/astk-client failed It looks as though bash2 has been removed from the ports collection. Is there a fix for this? This has already been discussed yesterday, see the thread 'make index failed'. The problem is that some ports still depend on shells/bash2 which has been removed from the ports, hence the index creation fails. Just cvsup again to get the latest patches and you'll be able to build the index. Worked for me ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: squidGuard-1.2.0_1
I was wondering if the squidGuard port was going to be updated from squidGuard-1.2.0_1 to squidGuard-1.2.1? The new version includes LDAP support and would be very beneficial. Brian E. Conklin, MCP+I, MCSE Director of Information Services Mason General Hospital voice: 360.427.3423 fax: 360.427.3433 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [net/samba3] Upgrade to Samba 3.0.25a
Uwe Laverenz wrote: On Tue, Jun 05, 2007 at 03:54:25PM -0700, Doug Barton wrote: I think it's very reasonable, and well in keeping with FreeBSD tradition, to delay upgrading to a new release of ported software until the maintainer is convinced that it's safe to do so. I have Yes, but on the other hand it is the server admin's job to test new software and to decide if and when he starts to deploy it on his production machines. Yes of course that's true, but it's not related to the matter at hand. And what about those users/admins who want to test new samba versions to actively help the samba team with improving the software? They would have to modify the port on their own to get the newest version. Well boo hoo! If you're smart enough to be useful in testing new versions, you're smart enough to modify the port yourself, or build the software without the port. Sorry to be so flippant, but this whole line of reasoning is absurd. A port maintainer has to take the best interests of the majority of the userbase into account, not cater to edge cases, especially when the edge cases ought to be able to get their own hands dirty. I also think it's useful to keep in mind that we are giving you the bits for free, and there is nothing stopping you from doing whatever you want to do with them. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Index
David wrote: Hello, I have this error when building a port index. Out of curiosity, why are you building the index yourself instead of using 'make fetchindex'? It's also worth noting that the other response you got was right. The first thing you should always do if you encounter an error is update your sources to see if it's been fixed already. :) hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
compat6x
Is anyone working on a compat6x port? Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compat6x
On 6/6/07, Kris Kennaway [EMAIL PROTECTED] wrote: Is anyone working on a compat6x port? mnag is ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compat6x
Kris Kennaway wrote: Is anyone working on a compat6x port? I started this some months ago. Now i can finish this because libs are bumped. Old port can be found here: http://people.freebsd.org/~mnag/compat6x.shar I'll send finished port ASAP. Regards Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Marcus Alves Grando marcus(at)sbh.eng.br | Personal mnag(at)FreeBSD.org | FreeBSD.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Samba] Problem about samba3 on freebsd, with smbldap-tools [solved]
Hi I have figured out what went wrong. I have previously complied samba without ldap support. There are tdb files in /var/db/samba. I have just uninstall samba and remove all tdb files (this instruction was given when run make deinstall in the samba3 ports, but I didn't follow it before). I did a fresh recompile with ldap support and now the problem is gone. Thanks Patrick --- Patrick Dung [EMAIL PROTECTED] wrote: My domain name is WORKGROUP 1. smbldap-usershow WORKGROUP\$ or smbldap-usershow DOMAIN\$ shows user XXX doesn't exist in both FreeBSD/Linux 2. I have used smbldap-populate and I have verified the items is added into the ldap server: dn: dc=localdomain dn: ou=people,dc=localdomain dn: ou=group,dc=localdomain dn: ou=computers,dc=localdomain dn: ou=Idmap,dc=localdomain dn: uid=root,ou=people,dc=localdomain dn: uid=nobody,ou=people,dc=localdomain dn: cn=Domain Admins,ou=group,dc=localdomain dn: cn=Domain Users,ou=group,dc=localdomain dn: cn=Domain Guests,ou=group,dc=localdomain dn: cn=Domain Computers,ou=group,dc=localdomain dn: cn=Administrators,ou=group,dc=localdomain dn: cn=Account Operators,ou=group,dc=localdomain dn: cn=Print Operators,ou=group,dc=localdomain dn: cn=Backup Operators,ou=group,dc=localdomain dn: cn=Replicators,ou=group,dc=localdomain dn: sambaDomainName=WORKGROUP,dc=localdomain dn: uid=w2000srv$,ou=computers,dc=localdomain dn: uid=server$,ou=computers,dc=localdomain 3. I have used slapcat and found no special problem. BTW, I have found this in my samba log: [2007/06/05 18:00:40, 0] auth/auth_util.c:create_builtin_users(758) create_builtin_users: Failed to create Users 4. I am using the same setup (eg. ldap access list, smb.conf) for both FreeBSD and Linux. Only FreeBSD have the problem. Regards Patrick --- Cardon Denis [EMAIL PROTECTED] wrote: Patrick Dung a écrit : Hi I have tried to setup freebsd (with samba3 ports), backend is openldap with smbldap-tools. After a windows client joined the domain, I tried to right click a folder to set Security/permission. The windows client has a popup windows which display: The program cannot open the required dialog box because it cannot determine whether the computer named DOMAIN is joined to a domain I have also tried to do same setup with Debian/Linux with the same settings in samba/openldap but it did not have this problem. Have you check that the entry is correctly created into the ldap tree (type smbldap-usershow DOMAIN\$ if DOMAIN is really your computer name...). You should also check that the group id/SID of your computers does exist in your ldap. When the windows box is joined to a domain, you should get a log of the complete smbldap-useradd line used for adding the computer in your smb.log file. If it failed, you can replay it on the command line to see what is the error code. Perhaps there is a missing perl library. Hope this helps, Denis BTW seems HPUX with the CIFS also get this problem: http://docs.hp.com/en/B8725-90119/ar01s05.html Any ideas? Thanks Patrick Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting -- Denis Cardon Tranquil IT Systems 10 rue du Docteur Bouchard 49400 Saumur tel : +33 (0) 2.41.67.56.99 http://www.tranquil-it-systems.fr Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [net/samba3] Upgrade to Samba 3.0.25a
Uwe Laverenz wrote: I know. I'm sorry if you got the impression I wouldn't appreciate your work. I guess my English is just too clumsy to be precise enough sometimes. Fair enough. :) Your english is great, and I don't even speak german, never mind writing it, so I'm not in a position to criticize. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
compile error in sysutils/fusefs-kmod
Hello list, I have the error below, when I try to portmanager sysutils/fusefs-kmod. Thank you for any suggestion! === mount_fusefs (all) Warning: Object directory not changed from original /usr/ports/sysutils/fusefs-kmod/work/fuse4bsd-0.3.0/mount_fusefs cc -O2 -fno-strict-aliasing -pipe -I/usr/src/sbin/mount -I../include -c mount_fusefs.c mount_fusefs.c:47:21: mntopts.h: No such file or directory mount_fusefs.c:58: error: elements of array `mopts' have incomplete type mount_fusefs.c:59: warning: excess elements in struct initializer mount_fusefs.c:59: warning: (near initialization for `mopts[0]') mount_fusefs.c:59: warning: excess elements in struct initializer mount_fusefs.c:59: warning: (near initialization for `mopts[0]') mount_fusefs.c:59: warning: excess elements in struct initializer mount_fusefs.c:59: warning: (near initialization for `mopts[0]') mount_fusefs.c:59: warning: excess elements in struct initializer mount_fusefs.c:59: warning: (near initialization for `mopts[0]') mount_fusefs.c:60: warning: excess elements in struct initializer mount_fusefs.c:60: warning: (near initialization for `mopts[1]') mount_fusefs.c:60: warning: excess elements in struct initializer mount_fusefs.c:60: warning: (near initialization for `mopts[1]') mount_fusefs.c:60: warning: excess elements in struct initializer mount_fusefs.c:60: warning: (near initialization for `mopts[1]') mount_fusefs.c:60: warning: excess elements in struct initializer mount_fusefs.c:60: warning: (near initialization for `mopts[1]') mount_fusefs.c:61: warning: excess elements in struct initializer mount_fusefs.c:61: warning: (near initialization for `mopts[2]') mount_fusefs.c:61: warning: excess elements in struct initializer mount_fusefs.c:61: warning: (near initialization for `mopts[2]') mount_fusefs.c:61: warning: excess elements in struct initializer mount_fusefs.c:61: warning: (near initialization for `mopts[2]') mount_fusefs.c:61: warning: excess elements in struct initializer mount_fusefs.c:61: warning: (near initialization for `mopts[2]') mount_fusefs.c:62: warning: excess elements in struct initializer mount_fusefs.c:62: warning: (near initialization for `mopts[3]') mount_fusefs.c:62: warning: excess elements in struct initializer mount_fusefs.c:62: warning: (near initialization for `mopts[3]') mount_fusefs.c:62: warning: excess elements in struct initializer mount_fusefs.c:62: warning: (near initialization for `mopts[3]') mount_fusefs.c:62: warning: excess elements in struct initializer mount_fusefs.c:62: warning: (near initialization for `mopts[3]') mount_fusefs.c:63: warning: excess elements in struct initializer mount_fusefs.c:63: warning: (near initialization for `mopts[4]') mount_fusefs.c:63: warning: excess elements in struct initializer mount_fusefs.c:63: warning: (near initialization for `mopts[4]') mount_fusefs.c:63: warning: excess elements in struct initializer mount_fusefs.c:63: warning: (near initialization for `mopts[4]') mount_fusefs.c:63: warning: excess elements in struct initializer mount_fusefs.c:63: warning: (near initialization for `mopts[4]') mount_fusefs.c:65: warning: excess elements in struct initializer mount_fusefs.c:65: warning: (near initialization for `mopts[5]') mount_fusefs.c:65: warning: excess elements in struct initializer mount_fusefs.c:65: warning: (near initialization for `mopts[5]') mount_fusefs.c:65: warning: excess elements in struct initializer mount_fusefs.c:65: warning: (near initialization for `mopts[5]') mount_fusefs.c:65: warning: excess elements in struct initializer mount_fusefs.c:65: warning: (near initialization for `mopts[5]') mount_fusefs.c:66: warning: excess elements in struct initializer mount_fusefs.c:66: warning: (near initialization for `mopts[6]') mount_fusefs.c:66: warning: excess elements in struct initializer mount_fusefs.c:66: warning: (near initialization for `mopts[6]') mount_fusefs.c:66: warning: excess elements in struct initializer mount_fusefs.c:66: warning: (near initialization for `mopts[6]') mount_fusefs.c:66: warning: excess elements in struct initializer mount_fusefs.c:66: warning: (near initialization for `mopts[6]') mount_fusefs.c:67: warning: excess elements in struct initializer mount_fusefs.c:67: warning: (near initialization for `mopts[7]') mount_fusefs.c:67: warning: excess elements in struct initializer mount_fusefs.c:67: warning: (near initialization for `mopts[7]') mount_fusefs.c:67: warning: excess elements in struct initializer mount_fusefs.c:67: warning: (near initialization for `mopts[7]') mount_fusefs.c:67: warning: excess elements in struct initializer mount_fusefs.c:67: warning: (near initialization for `mopts[7]') mount_fusefs.c:68: warning: excess elements in struct initializer mount_fusefs.c:68: warning: (near initialization for `mopts[8]') mount_fusefs.c:68: warning: excess elements in struct initializer mount_fusefs.c:68: warning: (near initialization for `mopts[8]') mount_fusefs.c:68: warning: excess elements in struct
Re: compile error in sysutils/fusefs-kmod
On Wed, Jun 06, 2007 at 11:34:25PM +0200, Gaye Abdoulaye Walsimou wrote: Hello list, I have the error below, when I try to portmanager sysutils/fusefs-kmod. Thank you for any suggestion! === mount_fusefs (all) Warning: Object directory not changed from original /usr/ports/sysutils/fusefs-kmod/work/fuse4bsd-0.3.0/mount_fusefs cc -O2 -fno-strict-aliasing -pipe -I/usr/src/sbin/mount -I../include -c mount_fusefs.c mount_fusefs.c:47:21: mntopts.h: No such file or directory snip You need full source tree installed, not just kernel sources as port's Makefile requires. HTH, Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compile error in sysutils/fusefs-kmod
Yuri Pankov a écrit : On Wed, Jun 06, 2007 at 11:34:25PM +0200, Gaye Abdoulaye Walsimou wrote: Hello list, I have the error below, when I try to portmanager sysutils/fusefs-kmod. Thank you for any suggestion! === mount_fusefs (all) Warning: Object directory not changed from original /usr/ports/sysutils/fusefs-kmod/work/fuse4bsd-0.3.0/mount_fusefs cc -O2 -fno-strict-aliasing -pipe -I/usr/src/sbin/mount -I../include -c mount_fusefs.c mount_fusefs.c:47:21: mntopts.h: No such file or directory snip You need full source tree installed, not just kernel sources as port's Makefile requires. HTH, Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] Ok after: cvsup -g -L 2 /usr/share/examples/cvsup/stable-supfile All work fine Thank a lot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Index
On Wed, 06 Jun 2007 12:33:40 -0500, Doug Barton [EMAIL PROTECTED] wrote: David wrote: Hello, I have this error when building a port index. Out of curiosity, why are you building the index yourself instead of using 'make fetchindex'? There are a few of reasons to build port index by yourself. The 'make fetchindex' don't sync with ports tree by 100% at most if you are using CVS/CVSup. If you modify any choice of dependency, it will changing the INDEX. You will have to build index by yourself if you have different branch of ports tree such as recently with xorg git, MC ports (GNOME stuff) or personal branch. As for in my system: = # ls -l /usr/ports | grep INDEX -rw-r--r-- 1 root wheel 0 May 20 2006 INDEX.dummy # make -V PORTS_INDEX /usr/ports/INDEX.dummy # portmaster rules portmaster version 1.17 Usage: [] ;-) = Cheers, Mezz It's also worth noting that the other response you got was right. The first thing you should always do if you encounter an error is update your sources to see if it's been fixed already. :) hth, Doug -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
postfix port install
1-This flew by pretty quick, if it weren't followed by a series of questions I might not have seen it. Warning: you still need to edit myorigin/mydestination/mynetworks parameter settings in /usr/local/etc/postfix/main.cf. 2-The below /etc/periodic.conf file isnt correct, /etc/periodic.conf doesnt exist; should I be deleting the 4 files at the bottom or creating a file /etc/periodic.conf with the below contents? And you can disable some sendmail specific daily maintenance routines in your /etc/periodic.conf file: daily_clean_hoststat_enable=NO daily_status_mail_rejects_enable=NO daily_status_include_submit_mailq=NO daily_submit_queuerun=NO Is this actually /etc/periodic/daily/ 150.clean-hoststat 460.status-mail-rejects 440.status-mailq 500.queuerun ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
x11 error
Hi folks, I'm preparing a PR for a bug I'm experiencing but wanted to mail the list first and see if anyone else had encountered this: My system is: FreeBSD devil.deweymonster.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Apr 30 02:37:07 MDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEVIL i386 I am using an intel810 graphics chip. X Windows was working very well until the last major ports upgrade with X 7.2 coming in. Now, whenever I use startx, the OS gives me the following error message: X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD devil.deweymonster.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Apr 30 02:37:07 MDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEVIL i386 Build Date: 04 June 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Jun 6 20:41:06 2007 (==) Using config file: /etc/X11/xorg.conf (EE) I810(0): Given bpp (32) is not supported by i810 driver (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found X connection to :0.0 broken (explicit kill or server shutdown). If X is started with the flag: startx -- -depth 16 Then it will start. However, no window manager sitting on top of X (such as xfce or GNOME) can manage to start a session. I don't know if this'll help, but I thought the output of dmesg -a might help identify the appropriate chip: Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #0: Mon Apr 30 02:37:07 MDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEVIL Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (501.14-MHz 686-class CPU) Origin = GenuineIntel Id = 0x681 Stepping = 1 Features=0x387f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE real memory = 267321344 (254 MB) avail memory = 252071936 (240 MB) kbd1 at kbdmux0 acpi0: IntelR AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff,0x5000-0x500f,0x4000-0x40f7 on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82810 (i810 GMCH) SVGA controller mem 0xd000-0xd3ff,0xd410-0xd417 irq 11 at device 1.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib1 ed0: RealTek 8029 port 0xc000-0xc01f irq 11 at device 4.0 on pci1 ed0: Ethernet address: 00:02:44:08:cd:de ed0: type RTL8029 (16 bit) ral0: Ralink Technology RT2560 mem 0xd400-0xd4001fff irq 5 at device 5.0 on pci1 ral0: MAC/BBP RT2560 (rev 0x04), RF RT2525 ral0: Ethernet address: 00:12:17:90:a8:07 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH UDMA66 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 uhci0: Intel 82801AA (ICH) USB controller port 0xd000-0xd01f irq 9 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801AA (ICH) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcm0: Intel ICH (82801AA) port 0xd800-0xd8ff,0xdc00-0xdc3f irq 5 at device 31.5 on pci0 pcm0: Analog Devices AD1881A AC97 Codec acpi_tz0: Thermal Zone on acpi0 fdc0: floppy drive controller port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: ECP parallel printer port port 0x378-0x37f,0x778-0x77b,0xb78-0xb7b,0xf78-0xf7b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 orm0: ISA Option ROM at iomem 0xc-0xc7fff on isa0 sc0: System
Re: x11 error
On Wed, 6 Jun 2007 20:54:22 -0600 James [EMAIL PROTECTED] wrote: Hi folks, I'm preparing a PR for a bug I'm experiencing but wanted to mail the list first and see if anyone else had encountered this: Bug is a serious word. My system is: FreeBSD devil.deweymonster.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Apr 30 02:37:07 MDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEVIL i386 I am using an intel810 graphics chip. X Windows was working very well until the last major ports upgrade with X 7.2 coming in. Now, whenever I use startx, the OS gives me the following error message: X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD devil.deweymonster.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Apr 30 02:37:07 MDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEVIL i386 Build Date: 04 June 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Jun 6 20:41:06 2007 (==) Using config file: /etc/X11/xorg.conf Can you post your /etc/X11/xorg.conf? And what happens if you start Xorg without xorg.conf? (EE) I810(0): Given bpp (32) is not supported by i810 driver (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found X connection to :0.0 broken (explicit kill or server shutdown). This can simply mean that there is no usable combination of parametres in your xorg.conf. Nikola Lečić ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11 error
On Wed, Jun 06, 2007 at 08:54:22PM -0600, James wrote: Hi folks, I'm preparing a PR for a bug I'm experiencing but wanted to mail the list first and see if anyone else had encountered this: My system is: FreeBSD devil.deweymonster.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Apr 30 02:37:07 MDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEVIL i386 I am using an intel810 graphics chip. X Windows was working very well until the last major ports upgrade with X 7.2 coming in. Now, whenever I use startx, the OS gives me the following error message: X Window System Version 7.2.0 Release Date: 22 January 2007 X Protocol Version 11, Revision 0, Release 7.2 Build Operating System: FreeBSD 6.2-STABLE i386 Current Operating System: FreeBSD devil.deweymonster.com 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Apr 30 02:37:07 MDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEVIL i386 Build Date: 04 June 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Jun 6 20:41:06 2007 (==) Using config file: /etc/X11/xorg.conf (EE) I810(0): Given bpp (32) is not supported by i810 driver (EE) Screen(s) found, but none have a usable configuration. snip Try DefaultFbBpp 24 in Section Screen. HTH, Yuri ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
