Re: mergemaster broken -- take 2
Mike Lempriere wrote: Hi folks -- sorry to be a nag, but my main production system is barely limping along on an old kernel with mismatched libraries. I have no idea what else to do -- please help! --- I'm upgrading 5-stable (was at 5.5) to 6-stable, in preparation for 6-stable to 7-stable. No problems with cvsup, make buildworld, make installworld, make buildkernel, mergemaster -p. make installkernel, boot to single user. Then mergemaster -- blammo: What is your exact make sequences are? I usually do this way: # csup /usr/share/examples/cvsup/standard-supfile # cd /usr/src here I usually softlink my kernel config file in /root directory to appropriate architecture one and edit /etc/make.conf: --- SUP_UPDATE=yes SUPHOST=cvsup.no.FreeBSD.org SUPFILE=/usr/share/examples/cvsup/standard-supfile PORTSSUPFILE=/usr/share/examples/cvsup/ports-supfile DOCSUPFILE=/usr/share/examples/cvsup/doc-supfile KERNCONF=KERNEL --- /usr/src/sys/amd64/conf KERNEL - /root/kernel/KERNEL # make buildkernel # make installkernel # make buildworld # mergemaster -p # make installworld # mergemaster NOTE: I do not reboot my system until everything is updated. Why it is necessary to boot new kernel and then upgrade world is beyound me..YMMW ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mergemaster broken -- take 2
On Thu, Jan 08, 2009 at 10:10:25AM +0200, Andrei Kolu wrote: Mike Lempriere wrote: Hi folks -- sorry to be a nag, but my main production system is barely limping along on an old kernel with mismatched libraries. I have no idea what else to do -- please help! --- I'm upgrading 5-stable (was at 5.5) to 6-stable, in preparation for 6-stable to 7-stable. No problems with cvsup, make buildworld, make installworld, make buildkernel, mergemaster -p. make installkernel, boot to single user. Then mergemaster -- blammo: What is your exact make sequences are? I usually do this way: # csup /usr/share/examples/cvsup/standard-supfile # cd /usr/src here I usually softlink my kernel config file in /root directory to appropriate architecture one and edit /etc/make.conf: --- SUP_UPDATE=yes SUPHOST=cvsup.no.FreeBSD.org SUPFILE=/usr/share/examples/cvsup/standard-supfile PORTSSUPFILE=/usr/share/examples/cvsup/ports-supfile DOCSUPFILE=/usr/share/examples/cvsup/doc-supfile KERNCONF=KERNEL --- /usr/src/sys/amd64/conf KERNEL - /root/kernel/KERNEL # make buildkernel # make installkernel # make buildworld # mergemaster -p # make installworld # mergemaster It may be me that is mistaken, but this seems wrong to me, as does the sequence in the original message: # cvsup # make buildworld # make installworld # make buildkernel # mergemaster -p. # make installkernel # boot to single user # mergemaster If I am not very much mistaken, the canonical process is: # make buildworld # make buildkernel # make installkernel # reboot (*) # mergemaster -p # make installworld # mergemaster The reasons for the other methods being wrong are (as I understand them): - You should build your new world before building your new kernel, as it may be the case that some aspects of the new kernel build are dependent upon aspects of the new world build. If you build your new kernel before building your new world, you will be building your new kernel against the old world. - You should install your new kernel before installing your new world, as it can be the case that some aspects of the new world will not be understood by your old kernel. A new kernel should always be compatible with an old userland/world, but an old kernel may not always be compatible with a new userland/world. NOTE: I do not reboot my system until everything is updated. Why it is necessary to boot new kernel and then upgrade world is beyound me..YMMW - I suppose that it is not strictly necessary to reboot between installing kernel and world, but I always do so. The reason for this is that, if something has gone horribly wrong, it is quite easy to go back and boot kernel.old. If you don't realize that there is something wrong until after you have installed everything (kernel and userland), it can be much more difficult to recover. -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: NIC for VLAN
Edvaldo Silva wrote: Please, can someone point a NIC, PCI 2.2 specs, full VLAN capable under FreeBSD? I'm using bge(4) and bce(4) interfaces (Broadcom GBit) and fxp(4) ones (100 MBit) in enviroments with heavy use of VLANs. They work very well. There are no problems with the MTU. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd A language that doesn't have everything is actually easier to program in than some that do. -- Dennis M. Ritchie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Problems with network in jail
Hi all, Is it mandatory to add device mem to jails to enable network via the gateway? Left ezjail with FreeBSD-6.3 (and a hardware replacement of my server) and am now starting again with FreeBSD-7.1. Early this week, I upgraded from 7.0 to 7.1 (not having 'used' jails on 7.0). After creating the jail with `ezjail-admin update -i` I created a 'ports build' jail `ezjail-admin create build 127.0.0.3` and forgot to add the alias to lo0, so no networking off-course. So I added the 127.0.0.3 alias to lo0 `ifconfig lo0 inet 127.0.0.3 alias` and restarted the jail Then I could get to the host machine, but not outside via the gateway. `netstat -nr` was returning errors netstat: kvm not available: /dev/mem: No such file or directory Routing tables rt_tables: symbol not in namelist But I could use the dns on the host, but was restricted to the host. After adding mem to the devfs_rules for my jail, I can see the routing tables And with mem added to devfs, I can also connect via the gateway on the host (NAT) If it's required to add 'mem' to the devfs rules to enable networking in the jail, it may be worth adding to the FAQ and/or the man-pages for ezjail-admin and jail? (and perhaps add a devfsrules_netjail to the default/devfs.rules) Kind regards, Spil. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Error in make buildworld
Realy my box is obsolet(Atlhon 2.0 - 512 Ram) I try without -j for discard overheated. tks again. On Wed, Jan 7, 2009 at 10:47 PM, Claus Guttesen kome...@gmail.com wrote: Hi Claus, thanks for return. I'm tried this steps below before send the first email and not resolve my problem =/ I notice you run a pre-release of 7.1. Did you update to the latest 7.1-release? make cleandir make cleandir rm -rf /usr/obj/* make -j6 buildworld but...the segmentation fault persist. I have more logs of buidworld, if you want, I send :D any idea? and thanks again. Could you try a buildworld without the -j parameter? If it still fails but in different stages of the buildworld it could be bad/overheated ram as mentioned by pluknet. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare -- dieggo.rbo at gmail dot com FreeBSD-BR User: #1047 Linux User: #395884 www.linkedin.com/in/diegodias Limeira - SP - [o] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mergemaster broken -- take 2
Greg Byshenk wrote: Andrei Kolu wrote: Mike Lempriere wrote: Hi folks -- sorry to be a nag, but my main production system is barely limping along on an old kernel with mismatched libraries. I have no idea what else to do -- please help! --- I'm upgrading 5-stable (was at 5.5) to 6-stable, in preparation for 6-stable to 7-stable. No problems with cvsup, make buildworld, make installworld, make buildkernel, mergemaster -p. make installkernel, boot to single user. Then mergemaster -- blammo: As others have pointed out, the order is wrong, which caused the problem Mike is seeing. The correct order is listed in /usr/src/UPDATING. The reasons for the other methods being wrong are (as I understand them): - You should build your new world before building your new kernel, as it may be the case that some aspects of the new kernel build are dependent upon aspects of the new world build. If you build your new kernel before building your new world, you will be building your new kernel against the old world. In particular, building the kernel uses the new toolchain (i.e. compiler, linker, make(1) binary and so on) that was built in /usr/obj during buildworld. That's why you have to do buildworld first, then make kernel. - You should install your new kernel before installing your new world, as it can be the case that some aspects of the new world will not be understood by your old kernel. A new kernel should always be compatible with an old userland/world, but an old kernel may not always be compatible with a new userland/world. That's correct. Note that your kernel config should include the appropriate options COMPAT_* lines if you update across a major version boundary, e.g. options_COMPAT_FREEBSD6 when you update from 6.x to 7.x. The GENERIC kernel already has those. NOTE: I do not reboot my system until everything is updated. Why it is necessary to boot new kernel and then upgrade world is beyound me..YMMW - I suppose that it is not strictly necessary to reboot between installing kernel and world, but I always do so. It _is_ necessary. If you don't reboot, you're still running the old kernel which might not be able to support new binaries and libraries that installworld will install on your system. For example, there may be new syscalls that the new binaries will try to use, but the old kernel doesn't know about them. It doesn't happen often, so you can get away without rebooting most of the time. But it's risky, especially when updating across major versions. So the recommendation is to always reboot after installing the new kernel and before performing the installworld. It's also important that installworld is the last step (except for mergemaster), because this is the point of no return. As long as you still have the old userland (world), you can still boot the old kernel and everything is fine. You can start all over froms cratch, if necessary. But as soon as you have started installworld, your system will not be able to work with the old kernel anymore. And remember: Always make a backup before you start to update. And verify that the backup works. Better safe than sorry. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd ... there are two ways of constructing a software design: One way is to make it so simple that there are _obviously_ no deficiencies and the other way is to make it so complicated that there are no _obvious_ deficiencies.-- C.A.R. Hoare, ACM Turing Award Lecture, 1980 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Samsung SCX-4200 printer
On Mon, Jan 05, 2009 at 07:01:02PM -0500, Alex Goncharov wrote: On Mon, Jan 05, 2009 at 11:26:23PM +0100, Roland Smith wrote: On Mon, Jan 05, 2009 at 05:44:03PM +0100, Erwan David wrote: On Mon, Jan 05, 2009 at 05:36:35PM CET, Torfinn Ingolfsen torfinn.ingolf...@broadpark.no said: On Sun, 04 Jan 2009 23:14:22 +0100 Harald Weis ha...@free.fr wrote: Is there a way to install the SCX-4200 printer on a FreeBSD box ? The printer is delivered with the install software required for Linux. And CUPS does not seem to know it. It is not always sufficient. My Brother DCP-540 CN is said to work perfectly, but only with brother binary linux drivers, under linux. I did not find any way to make it work under freeBSD. This should be a FAQ: do yourself a favor and get a printer that supports postscript. It will work with little effort with most UNIX-based program (because they usually support postscript output) and with most spoolers. Try to install the cupsys, cupsys-bsd, cupsomatic-ppd and foomatic-db None of these exist in the FreeBSD port index (/usr/ports/INDEX-7) ports and take a look at this link: http://forums.linux-foundation.org/read.php?31,302,320,quote=1 Refers only to Linux :-( Harald -- FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problems with network in jail
Hi Peter, Thanks a lot! Will read up on that. (luckily I do speak german/swiss-german). From discussions on ##FreeBSD IRC I learned that it is not recommended to use lo0 for jails! On FreeBSD-6.3 I succesfully used lo0/127.0.0.2 for my mysql jail that needed to be addressed only locally, but ONLY LOCALLY, no other access. It may be possible to add a line similar to 00100 divert 8668 ip from any to any in via xl0 to my ipfw/NAT config, but being warned, I'm not going down that path. Since I moved my portbuild jail to bridge0/172.17.2.17 it works as expected, without device mem! And to boot I made errors when creating my aliases (ifconfig bridge0 inet 172.17.2.17 netmask *172.17.2.255* in stead of 255.255.255.0) I will protect the jails that only need to be connected to from local by adding rules to my ipfw setup Now Iet's hope that my failures/problems serve as reference for future users of (ez)jail! Kind regards, Spil. 2009/1/8 Oliver Peter li...@peter.de.com: On Thu, 8 Jan 2009 11:07:04 +0100 Spil Oss spil@googlemail.com wrote: Early this week, I upgraded from 7.0 to 7.1 (not having 'used' jails on 7.0). After creating the jail with `ezjail-admin update -i` I created a 'ports build' jail `ezjail-admin create build 127.0.0.3` and forgot to add the alias to lo0, so no networking off-course. So I added the 127.0.0.3 alias to lo0 `ifconfig lo0 inet 127.0.0.3 alias` and restarted the jail If you use the loopback device for your jails you have to add NAT rules to your host machine, this documentation is very useful: http://www.rootforum.de/wiki/freebsd/04_jail_infrastructure#packet_filter_einrichten (The article is in German, but the configuration stuff should be understandable anyway) -- Oliver PETER, email: oli...@peter.de.com, ICQ# 113969174 If it feels good, you're doing something wrong. -- Coach McTavish ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problems with network in jail
On Thu, 8 Jan 2009 11:07:04 +0100 Spil Oss spil@googlemail.com wrote: Early this week, I upgraded from 7.0 to 7.1 (not having 'used' jails on 7.0). After creating the jail with `ezjail-admin update -i` I created a 'ports build' jail `ezjail-admin create build 127.0.0.3` and forgot to add the alias to lo0, so no networking off-course. So I added the 127.0.0.3 alias to lo0 `ifconfig lo0 inet 127.0.0.3 alias` and restarted the jail If you use the loopback device for your jails you have to add NAT rules to your host machine, this documentation is very useful: http://www.rootforum.de/wiki/freebsd/04_jail_infrastructure#packet_filter_einrichten (The article is in German, but the configuration stuff should be understandable anyway) -- Oliver PETER, email: oli...@peter.de.com, ICQ# 113969174 If it feels good, you're doing something wrong. -- Coach McTavish ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Samsung SCX-4200 printer
On Thu, Jan 08, 2009 at 12:11:27PM +0100, Harald Weis wrote: On Mon, Jan 05, 2009 at 07:01:02PM -0500, Alex Goncharov wrote: On Mon, Jan 05, 2009 at 11:26:23PM +0100, Roland Smith wrote: On Mon, Jan 05, 2009 at 05:44:03PM +0100, Erwan David wrote: On Mon, Jan 05, 2009 at 05:36:35PM CET, Torfinn Ingolfsen torfinn.ingolf...@broadpark.no said: On Sun, 04 Jan 2009 23:14:22 +0100 Harald Weis ha...@free.fr wrote: Is there a way to install the SCX-4200 printer on a FreeBSD box ? The printer is delivered with the install software required for Linux. And CUPS does not seem to know it. It is not always sufficient. My Brother DCP-540 CN is said to work perfectly, but only with brother binary linux drivers, under linux. I did not find any way to make it work under freeBSD. This should be a FAQ: do yourself a favor and get a printer that supports postscript. It will work with little effort with most UNIX-based program (because they usually support postscript output) and with most spoolers. Try to install the cupsys, cupsys-bsd, cupsomatic-ppd and foomatic-db None of these exist in the FreeBSD port index (/usr/ports/INDEX-7) foomatic-db = /usr/ports/print/foomatic-db looking for cupsys on the internet will give results like cupsys renamed to cups (at least for debian). Best regards, Holger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Version Number Only Changes
I am sure there is a reason for it. Upon running mergemaster this time through it seemed like there were _a lot_ of files where the only change was the version number. I have run to mergemaster on four more hosts. Ugh! mergemaster -aiU still seems to require a ton of interaction. Is there a better way? Thanks, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Version Number Only Changes
Jason C. Wells wrote: I am sure there is a reason for it. Upon running mergemaster this time through it seemed like there were _a lot_ of files where the only change was the version number. I have run to mergemaster on four more hosts. Ugh! mergemaster -aiU still seems to require a ton of interaction. Is there a better way? I have the following in /etc/mergemaster.rc: DIFF_FLAG='-Bub' DIFF_OPTIONS='-I$FreeBSD:.*[$]' IGNORE_MOTD=yes Also, I'm not sure you really want to use the -a option. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd When your hammer is C++, everything begins to look like a thumb. -- Steve Haflich, in comp.lang.c++ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problems with network in jail
Spil Oss spil@googlemail.com wrote: Thanks a lot! Will read up on that. (luckily I do speak german/swiss-german). From discussions on ##FreeBSD IRC I learned that it is not recommended to use lo0 for jails! Why would that be not recommended? In fact I think it is a very good idea to use lo0 addresses for jails, for security reasons, because they're guaranteed to not leave your local system. Therefore you have full control of what the process within the jail can do. If you want to grant specific network access to a jail (incoming or outgoing, or both), you add appropriate fwd rules to IPFW. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd That's what I love about GUIs: They make simple tasks easier, and complex tasks impossible. -- John William Chambless ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Tue, Jan 06, 2009 at 12:36:20PM -0500, Robert Noland wrote: I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 I tested your patch on 2 different machines: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. 2) dual-Opteron 285/amd64 with a Radeon X1600 (RV530) Works, but no direct rendering yet. I guess this would eventually work with a newer xorg?! If it helps somehow I could test again with xorg-7.4. Thanks again for your work! Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 14:47 +0100, Uwe Laverenz wrote: On Tue, Jan 06, 2009 at 12:36:20PM -0500, Robert Noland wrote: I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 I tested your patch on 2 different machines: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. 2) dual-Opteron 285/amd64 with a Radeon X1600 (RV530) Works, but no direct rendering yet. I guess this would eventually work with a newer xorg?! If it helps somehow I could test again with xorg-7.4. new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch robert. Thanks again for your work! Uwe signature.asc Description: This is a digitally signed message part
igb on a Nehalem system, buildworld stats
Hi guys, I just got on my hands today a NEHALEM system: 2 x 5560 Nehalem CPU (2.8GHz, 8MB cache memory, 6.4GT/sec [QPI]) 12GB 1333Mhz DDR3 Memory 1 x 500GB SATA HDD FreeBSD 7.1-RELEASE/amd64 install fine, however I seemed to be having problems w/ its built-in Intel NICs: igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e2 inet6 fe80::230:48ff:fec5:dbe2%igb0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX full-duplex) status: active igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e3 inet6 fe80::230:48ff:fec5:dbe3%igb1 prefixlen 64 scopeid 0x2 inet 172.17.32.32 netmask 0x broadcast 172.17.255.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active The first NIC would always want 100baseTX no matter how I'd ifconfig down/up it, so I just had to use the 2nd NIC. Unfortunately, this too is having problems. Like being unable to 'see' some machines on the same network segment. Some other machines are accessible. And yes I've double-checked the network stuff (cables, switch, IP settings) and my conclusion is b0rky NICs. pciconf -lvc: i...@pci0:1:0:0:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint i...@pci0:1:0:1:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint So anyone else having igb problems? I'm downloading 200812-CURRENT now (is tehre gonna be a 200901-CURRENT ISO soon? :-p), I'd like to try that, but checking cvs seem only a handful of changes. Also I did some buildworlds: make -j8 buildworld 2846.900u 2266.188s 15:50.43 537.9% 6375+2082k 10084+7937io 1482pf+0w make -j16 buildworld 3518.254u 2175.593s 14:23.29 659.5% 6656+2147k 26165+8546io 4300pf+0w make -j32 buildworld 3582.897u 4437.710s 18:03.88 739.9% 6528+2125k 5725+7930io 1555pf+0w Verbose dmesg: http://pastebin.com/f5f799561 Thanks! -- cheers mars ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, Jan 08, 2009 at 09:03:50AM -0500, Robert Noland wrote: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. Yes, it's a PCIE card: ATI FireGL M24 GL 3154 (PCIE) new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch Ok, I'll test it. Uwe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, 8 Jan 2009 15:27:08 +0100 Uwe Laverenz u...@laverenz.de wrote: On Thu, Jan 08, 2009 at 09:03:50AM -0500, Robert Noland wrote: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. Yes, it's a PCIE card: ATI FireGL M24 GL 3154 (PCIE) new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch Ok, I'll test it. I have an RV6xx based system here - graphics in the chipset. Can you, Roland, say whether this patch will allow me to use DRM/DRI with it? Right now it's not recognized. --- Gary Jennejohn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
kernel dump with 7.1-RELEASE
Hi, I am having kernel dumps with FreeBSD 7.1 panic: semexit - semid not allocated cpuid = 1 Uptime : 8m22s Cannot dump. No dump device defined Sleeping thread (tid 100129, pid 1479) owns a non-sleepable lock I know it is not clear and there were no swap space configured on this server (which I will re-install with swap space) but can someone enlighten me about this since I think this bug was also in FreeBSD 6.2 and fixed in FreeBSD 6.3 Regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 17:22 +0100, Gary Jennejohn wrote: On Thu, 8 Jan 2009 15:27:08 +0100 Uwe Laverenz u...@laverenz.de wrote: On Thu, Jan 08, 2009 at 09:03:50AM -0500, Robert Noland wrote: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. Yes, it's a PCIE card: ATI FireGL M24 GL 3154 (PCIE) new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch Ok, I'll test it. I have an RV6xx based system here - graphics in the chipset. Can you, Roland, say whether this patch will allow me to use DRM/DRI with it? Right now it's not recognized. what is the pci id? Probably not, I think that is an r600 chipset, but AMD has released preliminary code, so it shouldn't be too much longer. robert. --- Gary Jennejohn signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 17:22 +0100, Gary Jennejohn wrote: On Thu, 8 Jan 2009 15:27:08 +0100 Uwe Laverenz u...@laverenz.de wrote: On Thu, Jan 08, 2009 at 09:03:50AM -0500, Robert Noland wrote: 1) the infamous ThinkPad T43p ;) running i386: Sorry, but RELENG_7_1 with your drm-update still shows a garbled screen. The same userland with a -CURRENT kernel works without problems. Is this a pci based radeon as well? If so, there is still a patch in -CURRENT that isn't in this set yet. Yes, it's a PCIE card: ATI FireGL M24 GL 3154 (PCIE) new xorg will hit ports soon, but a preliminary patch is available at http://people.freebsd.org/~rnoland/xorg-7.4-111608.patch Ok, I'll test it. I have an RV6xx based system here - graphics in the chipset. Can you, Roland, say whether this patch will allow me to use DRM/DRI with it? Right now it's not recognized. It should however support the latest Intel chipsets, and R500 and below AMD/ATI including the IGP chips (rs690 and rs485). If you have the garbled screen with pci based radeons, I have a patch for that also that isn't part of this MFC yet. The newer chips may also need the newer Xorg / Mesa bits, coming to a ports collection near you very soon. robert. --- Gary Jennejohn signature.asc Description: This is a digitally signed message part
Re: Pending MFC of drm updates
Robert Noland wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 robert. I've pulled this down and patched my install of FreeBSD 7.1-RELEASE. Whilst using a Radeon 9250 (R280?), I have no problems. There is also no apparent performance difference. The only issue I have seen occurs with my dual-monitor setup. Occasionally a window on the second monitor will decide to render its drop-down menus or other (overlay-based?) graphics on the primary monitor instead of where it should be. Restarting the application seems to clear this up. I have not seen this previously before applying your patch. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 11:57 -0500, Steve Polyack wrote: Robert Noland wrote: I am planning to merge most all of the drm from -CURRENT to releng_7 shortly. The merge that I have staged includes the following. Merged /head/sys:r182080,182467-182469,182883-182884,183573,183603-183605, 183828,183830-183834,184212-184213,184263,184373-184375 There are really too many updates/fixes to mention as the drm from 7 is more than 2 years old now. This has support for several newer Intel and AMD/ATI chips, (no r6/7xx yet, but soon(tm)). I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 robert. I've pulled this down and patched my install of FreeBSD 7.1-RELEASE. Whilst using a Radeon 9250 (R280?), I have no problems. There is also no apparent performance difference. The only issue I have seen occurs with my dual-monitor setup. Occasionally a window on the second monitor will decide to render its drop-down menus or other (overlay-based?) graphics on the primary monitor instead of where it should be. Restarting the application seems to clear this up. I have not seen this previously before applying your patch. Hrm, I'm not sure how that could be related... You might try rebuilding graphics/libdrm. That sounds like an framebuffer offset issue. robert. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org signature.asc Description: This is a digitally signed message part
Re: Problems with network in jail
Spil Oss wrote: Hi Peter, Thanks a lot! Will read up on that. (luckily I do speak german/swiss-german). From discussions on ##FreeBSD IRC I learned that it is not recommended to use lo0 for jails! On FreeBSD-6.3 I succesfully used lo0/127.0.0.2 for my mysql jail that needed to be addressed only locally, but ONLY LOCALLY, no other access. It may be possible to add a line similar to 00100 divert 8668 ip from any to any in via xl0 to my ipfw/NAT config, but being warned, I'm not going down that path. Since I moved my portbuild jail to bridge0/172.17.2.17 it works as expected, without device mem! And to boot I made errors when creating my aliases (ifconfig bridge0 inet 172.17.2.17 netmask *172.17.2.255* in stead of 255.255.255.0) You can create lo1 if you want: ifconfig create lo1 ifconfig lo1 inet 172.17.2.17 netmask 255.255.255.0 in rc.conf cloned_interfaces=lo1 ifconfig_lo1=inet 172.17.2.17 netmask 255.255.255.0 And then use NAT / RDR in your favorite firewall (I am using PF) Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: igb on a Nehalem system, buildworld stats
I have not seen a problem like this ever, what is the link partner of each NIC and if you switch the ports what happens? We have Nehalem's in the validation lab but I have not had an excuse to install on one so far, I guess now I do :) Jack On Thu, Jan 8, 2009 at 6:16 AM, Mars G Miro s...@anarchy.in.the.ph wrote: Hi guys, I just got on my hands today a NEHALEM system: 2 x 5560 Nehalem CPU (2.8GHz, 8MB cache memory, 6.4GT/sec [QPI]) 12GB 1333Mhz DDR3 Memory 1 x 500GB SATA HDD FreeBSD 7.1-RELEASE/amd64 install fine, however I seemed to be having problems w/ its built-in Intel NICs: igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e2 inet6 fe80::230:48ff:fec5:dbe2%igb0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX full-duplex) status: active igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e3 inet6 fe80::230:48ff:fec5:dbe3%igb1 prefixlen 64 scopeid 0x2 inet 172.17.32.32 netmask 0x broadcast 172.17.255.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active The first NIC would always want 100baseTX no matter how I'd ifconfig down/up it, so I just had to use the 2nd NIC. Unfortunately, this too is having problems. Like being unable to 'see' some machines on the same network segment. Some other machines are accessible. And yes I've double-checked the network stuff (cables, switch, IP settings) and my conclusion is b0rky NICs. pciconf -lvc: i...@pci0:1:0:0:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint i...@pci0:1:0:1:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint So anyone else having igb problems? I'm downloading 200812-CURRENT now (is tehre gonna be a 200901-CURRENT ISO soon? :-p), I'd like to try that, but checking cvs seem only a handful of changes. Also I did some buildworlds: make -j8 buildworld 2846.900u 2266.188s 15:50.43 537.9% 6375+2082k 10084+7937io 1482pf+0w make -j16 buildworld 3518.254u 2175.593s 14:23.29 659.5% 6656+2147k 26165+8546io 4300pf+0w make -j32 buildworld 3582.897u 4437.710s 18:03.88 739.9% 6528+2125k 5725+7930io 1555pf+0w Verbose dmesg: http://pastebin.com/f5f799561 Thanks! -- cheers mars ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Samsung SCX-4200 printer
,--- You/Harald (Thu, 8 Jan 2009 12:11:27 +0100) * | Try to install the cupsys, cupsys-bsd, cupsomatic-ppd and foomatic-db | ports and take a look at this link: | | None of these exist in the FreeBSD port index (/usr/ports/INDEX-7) So, you've now looked :-) I've had good experience with foomatic use for most various printers in the past and wanted to give you a pointer to that package, no promises, since you didn't seem to be familiar it. I didn't have the printing packages installed in the machine I sent the original mail from, so could not check the correct package names -- I can check what I have now: $ pkg_info -L foomatic-db-20070124_1| grep -ic samsung 62 $ pkg_info -L foomatic-db-20070124_1| grep -ic scx 0 So, that printer is not yet in BSD foomatic-db. | http://forums.linux-foundation.org/read.php?31,302,320,quote=1 | | Refers only to Linux :-( I know -- but I often used Linux-based advice as a clue for solving printing problems on FreeBSD. Sorry this didn't help you (and I am sure you saw this http://www.openprinting.org/show_printer.cgi?recnum=Samsung-SCX-4200). -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: igb on a Nehalem system, buildworld stats
On Fri, Jan 9, 2009 at 12:44 AM, Jack Vogel jfvo...@gmail.com wrote: I have not seen a problem like this ever, what is the link partner of each NIC and if you switch the ports what happens? Hi Jack, They're connected to a GigE switch. It was just one w/ the first NIC, but having seen that it only connects at 100baseTX, I wired the 2nd and saw that it can now do 1000baseTX. Unfortunately w/ problems as it can 'see' some machines but unable to see others (in the same physical network segment). I've changed cables, and plugged them in different ports in the switch but still the same behavior. IIRC, this is the first time I had igb problems and only on this box. I believe I encountered igb NICs in the newer HP DL380/385 but those work fine. btw, this is a Supermicro Intel Engineering sample box (major vendors don't have Nehalems in the market yet) so there prolly are hardware/driver bugs lurking? I dunno. Thanks. We have Nehalem's in the validation lab but I have not had an excuse to install on one so far, I guess now I do :) Jack On Thu, Jan 8, 2009 at 6:16 AM, Mars G Miro s...@anarchy.in.the.ph wrote: Hi guys, I just got on my hands today a NEHALEM system: 2 x 5560 Nehalem CPU (2.8GHz, 8MB cache memory, 6.4GT/sec [QPI]) 12GB 1333Mhz DDR3 Memory 1 x 500GB SATA HDD FreeBSD 7.1-RELEASE/amd64 install fine, however I seemed to be having problems w/ its built-in Intel NICs: igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e2 inet6 fe80::230:48ff:fec5:dbe2%igb0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX full-duplex) status: active igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e3 inet6 fe80::230:48ff:fec5:dbe3%igb1 prefixlen 64 scopeid 0x2 inet 172.17.32.32 netmask 0x broadcast 172.17.255.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active The first NIC would always want 100baseTX no matter how I'd ifconfig down/up it, so I just had to use the 2nd NIC. Unfortunately, this too is having problems. Like being unable to 'see' some machines on the same network segment. Some other machines are accessible. And yes I've double-checked the network stuff (cables, switch, IP settings) and my conclusion is b0rky NICs. pciconf -lvc: i...@pci0:1:0:0:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint i...@pci0:1:0:1:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint So anyone else having igb problems? I'm downloading 200812-CURRENT now (is tehre gonna be a 200901-CURRENT ISO soon? :-p), I'd like to try that, but checking cvs seem only a handful of changes. Also I did some buildworlds: make -j8 buildworld 2846.900u 2266.188s 15:50.43 537.9% 6375+2082k 10084+7937io 1482pf+0w make -j16 buildworld 3518.254u 2175.593s 14:23.29 659.5% 6656+2147k 26165+8546io 4300pf+0w make -j32 buildworld 3582.897u 4437.710s 18:03.88 739.9% 6528+2125k 5725+7930io 1555pf+0w Verbose dmesg: http://pastebin.com/f5f799561 Thanks! -- cheers mars ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- cheers mars ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Samsung SCX-4200 printer
On Thu, Jan 08, 2009 at 01:01:57PM -0500, Alex Goncharov wrote: ,--- You/Harald (Thu, 8 Jan 2009 12:11:27 +0100) * | Try to install the cupsys, cupsys-bsd, cupsomatic-ppd and foomatic-db | ports and take a look at this link: | | None of these exist in the FreeBSD port index (/usr/ports/INDEX-7) So, you've now looked :-) Oh, yes, sorry, foomatic-db does indeed exist. I've had good experience with foomatic use for most various printers in the past and wanted to give you a pointer to that package, no promises, since you didn't seem to be familiar it. I didn't have the printing packages installed in the machine I sent the original mail from, so could not check the correct package names -- I can check what I have now: $ pkg_info -L foomatic-db-20070124_1| grep -ic samsung 62 $ pkg_info -L foomatic-db-20070124_1| grep -ic scx 0 So, that printer is not yet in BSD foomatic-db. | | Refers only to Linux :-( I know -- but I often used Linux-based advice as a clue for solving printing problems on FreeBSD. Sorry this didn't help you (and I am sure you saw this http://www.openprinting.org/show_printer.cgi?recnum=Samsung-SCX-4200). Yes, I did. Harald -- FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Error in make buildworld
Wow, I catch the problem. My memory realy is broken the memtest warn me. =/ I take a new memory and try again. []'s On Thu, Jan 8, 2009 at 8:34 AM, Diego Ribeiro dieggo@gmail.com wrote: Realy my box is obsolet(Atlhon 2.0 - 512 Ram) I try without -j for discard overheated. tks again. On Wed, Jan 7, 2009 at 10:47 PM, Claus Guttesen kome...@gmail.com wrote: Hi Claus, thanks for return. I'm tried this steps below before send the first email and not resolve my problem =/ I notice you run a pre-release of 7.1. Did you update to the latest 7.1-release? make cleandir make cleandir rm -rf /usr/obj/* make -j6 buildworld but...the segmentation fault persist. I have more logs of buidworld, if you want, I send :D any idea? and thanks again. Could you try a buildworld without the -j parameter? If it still fails but in different stages of the buildworld it could be bad/overheated ram as mentioned by pluknet. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare -- dieggo.rbo at gmail dot com FreeBSD-BR User: #1047 Linux User: #395884 www.linkedin.com/in/diegodias Limeira - SP - [o] -- dieggo.rbo at gmail dot com FreeBSD-BR User: #1047 Linux User: #395884 www.linkedin.com/in/diegodias Limeira - SP - [o] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: igb on a Nehalem system, buildworld stats
On Fri, Jan 9, 2009 at 2:33 AM, Jack Vogel jfvo...@gmail.com wrote: Well, I am at Intel you know, and even we don't seem to have any systems with 82576 down in my group here. The way link works I can be about 99.9% sure in saying its not the driver. Its preproduction so there are lots of possibilities, and the biggest problem is its going to be difficult to help when I don't have any such hardware :( I've heard from the 1G product team that they have seen EEPROM mismatches on systems that will result in things not working in funny ways. Jahh, I've seen those but not w/ Intel NICs. I believe it was from Broadcom on some IBM x3455? (IIRC) and it was indeed quite amusing ;-) If you have a back to back connection to another NIC on Port 0, no switch, does it still autoneg to 100? I will have do that tomorrow as I am @home now ;-) btw, another data point, during sysinstall, we encountered: unknown network interface type on both the igbs. Thanks. Jack On Thu, Jan 8, 2009 at 10:19 AM, Mars G Miro s...@anarchy.in.the.ph wrote: On Fri, Jan 9, 2009 at 12:44 AM, Jack Vogel jfvo...@gmail.com wrote: I have not seen a problem like this ever, what is the link partner of each NIC and if you switch the ports what happens? Hi Jack, They're connected to a GigE switch. It was just one w/ the first NIC, but having seen that it only connects at 100baseTX, I wired the 2nd and saw that it can now do 1000baseTX. Unfortunately w/ problems as it can 'see' some machines but unable to see others (in the same physical network segment). I've changed cables, and plugged them in different ports in the switch but still the same behavior. IIRC, this is the first time I had igb problems and only on this box. I believe I encountered igb NICs in the newer HP DL380/385 but those work fine. btw, this is a Supermicro Intel Engineering sample box (major vendors don't have Nehalems in the market yet) so there prolly are hardware/driver bugs lurking? I dunno. Thanks. We have Nehalem's in the validation lab but I have not had an excuse to install on one so far, I guess now I do :) Jack On Thu, Jan 8, 2009 at 6:16 AM, Mars G Miro s...@anarchy.in.the.ph wrote: Hi guys, I just got on my hands today a NEHALEM system: 2 x 5560 Nehalem CPU (2.8GHz, 8MB cache memory, 6.4GT/sec [QPI]) 12GB 1333Mhz DDR3 Memory 1 x 500GB SATA HDD FreeBSD 7.1-RELEASE/amd64 install fine, however I seemed to be having problems w/ its built-in Intel NICs: igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e2 inet6 fe80::230:48ff:fec5:dbe2%igb0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX full-duplex) status: active igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e3 inet6 fe80::230:48ff:fec5:dbe3%igb1 prefixlen 64 scopeid 0x2 inet 172.17.32.32 netmask 0x broadcast 172.17.255.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active The first NIC would always want 100baseTX no matter how I'd ifconfig down/up it, so I just had to use the 2nd NIC. Unfortunately, this too is having problems. Like being unable to 'see' some machines on the same network segment. Some other machines are accessible. And yes I've double-checked the network stuff (cables, switch, IP settings) and my conclusion is b0rky NICs. pciconf -lvc: i...@pci0:1:0:0:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint i...@pci0:1:0:1:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint So anyone else having igb problems? I'm downloading 200812-CURRENT now (is tehre gonna be a 200901-CURRENT ISO soon? :-p), I'd like to try that, but checking cvs seem only a handful of changes. Also I did some buildworlds: make -j8 buildworld 2846.900u 2266.188s 15:50.43 537.9% 6375+2082k 10084+7937io 1482pf+0w make -j16 buildworld 3518.254u 2175.593s 14:23.29 659.5% 6656+2147k 26165+8546io 4300pf+0w make -j32 buildworld 3582.897u 4437.710s
Re: Samsung SCX-4200 printer
On Thu, Jan 08, 2009 at 03:06:42PM +0200, Alexander Shikoff wrote: On Sun, Jan 04, 2009 at 11:14:22PM +0100, Harald Weis wrote: Is there a way to install the SCX-4200 printer on a FreeBSD box ? The printer is delivered with the install software required for Linux. And CUPS does not seem to know it. Thank you in advance for any help. I've successfully setup printing on SCX-4521F connected to MS Windows box. I use Linux binary driver from Samsung website. On my FreeBSD box (7.1-PRERELEASE) I use cups and samba-client. Unfortunately I have detailed description of all steps in Russian only. But I'll try to give you a the short summary. I hope it will let you find right way: snip That's all. If you have any issues/question feel free to ask. Have a nice day! Thank you very much. I'll report as soon as possible. Harald -- FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: igb on a Nehalem system, buildworld stats
So it wasn't identified during install but was in the kernel you built afterward, is that what you're saying? Even if that's true I don't think its relevant to the failure. I have made a couple queries internally, there are a lot of variations on Nehalem systems, at least one other engineer in my group had an encounter with one like yours, I have two managers looking for me, hopefully I can find one. Jack On Thu, Jan 8, 2009 at 10:50 AM, Mars G Miro s...@anarchy.in.the.ph wrote: On Fri, Jan 9, 2009 at 2:33 AM, Jack Vogel jfvo...@gmail.com wrote: Well, I am at Intel you know, and even we don't seem to have any systems with 82576 down in my group here. The way link works I can be about 99.9% sure in saying its not the driver. Its preproduction so there are lots of possibilities, and the biggest problem is its going to be difficult to help when I don't have any such hardware :( I've heard from the 1G product team that they have seen EEPROM mismatches on systems that will result in things not working in funny ways. Jahh, I've seen those but not w/ Intel NICs. I believe it was from Broadcom on some IBM x3455? (IIRC) and it was indeed quite amusing ;-) If you have a back to back connection to another NIC on Port 0, no switch, does it still autoneg to 100? I will have do that tomorrow as I am @home now ;-) btw, another data point, during sysinstall, we encountered: unknown network interface type on both the igbs. Thanks. Jack On Thu, Jan 8, 2009 at 10:19 AM, Mars G Miro s...@anarchy.in.the.ph wrote: On Fri, Jan 9, 2009 at 12:44 AM, Jack Vogel jfvo...@gmail.com wrote: I have not seen a problem like this ever, what is the link partner of each NIC and if you switch the ports what happens? Hi Jack, They're connected to a GigE switch. It was just one w/ the first NIC, but having seen that it only connects at 100baseTX, I wired the 2nd and saw that it can now do 1000baseTX. Unfortunately w/ problems as it can 'see' some machines but unable to see others (in the same physical network segment). I've changed cables, and plugged them in different ports in the switch but still the same behavior. IIRC, this is the first time I had igb problems and only on this box. I believe I encountered igb NICs in the newer HP DL380/385 but those work fine. btw, this is a Supermicro Intel Engineering sample box (major vendors don't have Nehalems in the market yet) so there prolly are hardware/driver bugs lurking? I dunno. Thanks. We have Nehalem's in the validation lab but I have not had an excuse to install on one so far, I guess now I do :) Jack On Thu, Jan 8, 2009 at 6:16 AM, Mars G Miro s...@anarchy.in.the.ph wrote: Hi guys, I just got on my hands today a NEHALEM system: 2 x 5560 Nehalem CPU (2.8GHz, 8MB cache memory, 6.4GT/sec [QPI]) 12GB 1333Mhz DDR3 Memory 1 x 500GB SATA HDD FreeBSD 7.1-RELEASE/amd64 install fine, however I seemed to be having problems w/ its built-in Intel NICs: igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e2 inet6 fe80::230:48ff:fec5:dbe2%igb0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (100baseTX full-duplex) status: active igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:30:48:c5:db:e3 inet6 fe80::230:48ff:fec5:dbe3%igb1 prefixlen 64 scopeid 0x2 inet 172.17.32.32 netmask 0x broadcast 172.17.255.255 media: Ethernet autoselect (1000baseTX full-duplex) status: active The first NIC would always want 100baseTX no matter how I'd ifconfig down/up it, so I just had to use the 2nd NIC. Unfortunately, this too is having problems. Like being unable to 'see' some machines on the same network segment. Some other machines are accessible. And yes I've double-checked the network stuff (cables, switch, IP settings) and my conclusion is b0rky NICs. pciconf -lvc: i...@pci0:1:0:0:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled cap 10[a0] = PCI-Express 2 endpoint i...@pci0:1:0:1:class=0x02 card=0x10c915d9 chip=0x10c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit, vector masks
Re: igb on a Nehalem system, buildworld stats
On Fri, Jan 9, 2009 at 3:06 AM, Jack Vogel jfvo...@gmail.com wrote: So it wasn't identified during install but was in the kernel you built afterward, is that what you're saying? Even if that's true I don't think its relevant to the failure. Ahm no, sysinstall said something like: igb0: unknown network interface type igb1: unknown network interface type but we just went ahead and made the choice. I thought it might be a slight variation of igb NICs or something so I stated that info. I have made a couple queries internally, there are a lot of variations on Nehalem systems, at least one other engineer in my group had an encounter with one like yours, I have two managers looking for me, hopefully I can find one. Ok cool. Matsalams (means much thanks!) ;-) Jack [snip] -- cheers mars ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ACPI support?
On Tue, 06 Jan 2009 13:12:05 +0200 Krassimir Slavchev kra...@bulinfo.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello All, I have had a problem detecting the network card on my notebook when ACPI is enabled for a year. The problem still exists in 7.1-RELEASE. Which make and model notebook is this? You have my sympaties, my own laptop[1] (Acer Aspire 5672) have the same sort of problem - drivers for NICs (both wired and wireless) will not attach if acpi is enabled. And this laptop gets too hot when acpi is disabled - I fear it will overheat. Linux runs fine[2] on it. I had a lot of help in trying to fix the problem a wbile back (check the freebsd-mobile mailing list archives), but in the end, nothing helped. I can only offer general advice, not a solution. Try too look for a modfified DSDT for your notebook, perhpas you will find something that helps. References: 1) http://tingox.googlepages.com/aceraspireas5672andfreebsd 2) http://tingox.googlepages.com/as5672_xubuntu -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
possibility of a severe flaw in the logic of FreeBSD's kernel handling multiple host bridges ...
First: Congratulations upon 7.1 final RELEASE ! On Fri, 24 Oct 2008, I pointed out the possibility of a severe flaw in the logic of FreeBSD's kernel handling multiple host bridges and the corresponding assignment of (in principle, correctly detected) devices to their host bridges :: -- http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128331 :: -- http://forums.freebsd.org/showthread.php?t=236 but unfortunately, I did not get any response at all. Two mails to kensm...@cse.buffalo.edu asking for any contact e-mail address of a FreeBSD Kernel developer knowing his way around host-bridges and PCI-devices also gave no reaction. I am sorry for this noise (I would have preferred to handle this more quietly), but finally I take hope to the advice of Daniel Gerzo (Thanks @ danger): If you will not receive any feedback I would recommend you to send an email to current@ and stable@ mailing lists. PR's sometimes get lost in the traffic and not all developers are checking GNATS all the time. Looking forward to a contact Kind regards Manfred ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD Update should be back to normal
Hi all, There are now more freebsd-update mirrors and it looks like they're handling the load quite well. It's possible that the load balancing between mirrors will need to be tweaked a bit. If you have problems accessing a mirror (e.g., if freebsd-update exits with an error of downloading files... failed or complains that a file does not exist) please: 1. Try again using the -s option to make sure that you're accessing the same mirror (to make sure that this wasn't a temporary network glitch). 2. Assuming the first mirror still fails, use the -s option to pick a different mirror. 3. Assuming that the second mirror works, send me an email telling me which mirror failed and which one worked so that I can have the load balancing adjusted. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mergemaster broken -- take 2
On Thu, Jan 08, 2009 at 11:47:42AM +0100, Oliver Fromme wrote: Greg Byshenk wrote: Andrei Kolu wrote: NOTE: I do not reboot my system until everything is updated. Why it is necessary to boot new kernel and then upgrade world is beyound me..YMMW - I suppose that it is not strictly necessary to reboot between installing kernel and world, but I always do so. It _is_ necessary. If you don't reboot, you're still running the old kernel which might not be able to support new binaries and libraries that installworld will install on your system. Of course this is correct; my error. The chance of something going wrong in this case is probably quite small, but it something does go wrong it can go horribly wrong. -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
CFT: ath hal src switchover
I've brought the hal source code back to RELENG_7 but not connected it to the build and/or driver. I want folks to test this before I commit those changes. To do this you must have an up to date RELENG_7 code base and then apply this patch: http://people.freebsd.org/~sam/ath_hal-releng7.patch Then rebuild your kernel. There should be no changes to user apps. Beware however that custom kernel configurations will need to change; instead of: device ath device ath_hal device ath_rate_sample (or similar) you need: device ath device ath_hal options AH_SUPPORT_AR5416 device ath_rate_sample If you want to configure a subset of the chip support implied by ath_hal then you may not need the options line. If you are using modules note that ath_hal and ath_rate_* modules no longer exist; they are now rolled into the ath module. If you use a rate control algorithm other than sample then you'll need to modify the ath module build or override by specifying ATH_RATE; e.g. cd sys/modules/ath make ATH_RATE=onoe The updated hal code adds support for several parts but otherwise makes no effort to address driver bugs. You should see no regressions relative to operation w/ the older hal. If you are running the 7.1 release you will need to import the hal code that is now in sys/dev/ath/ath_hal before following the above instructions. I have no idea if this will work for an earlier version of FreeBSD; if you're not running at least 7.1 my advise is to upgrade. Please report any issues to this mailing list. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Pending MFC of drm updates
On Tue, Jan 06, 2009 at 12:36:20PM -0500, Robert Noland wrote: I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 Excellent! Thanks for your hard work on this, Robert! After updating my source to 7.1-RELEASE, I applied this patch and built and installed a new kernel and world. This went without problems. Starting X on a Sapphire Radeon X1650Pro works OK. XAA 2D accelleration works OK. The X logfile says that direct rendering is enabled, as is Xv. Mplayer works with Xv. But whenever I try to start a program that uses OpenGL (i.e. glxgears) I get the following message: unknown chip id 0x71c1, can't guess. libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering :-( The same number shows in Xorg.0.log: snip (--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x71c1) rev 158, Mem @ 0xe000/28, 0xfe9e/16, I/O @ 0xd000/8, BIOS @ 0xfe9c/17 snip (II) Loading extension XFree86-DGA snip (--) Chipset RV535 found snip (II) RADEONHD(0): Unknown card detected: 0x71C1:0x174B:0x0880. If - and only if - your card does not work or does not work optimally please contact radeo...@opensuse.org to help rectify this. Use the subject: 0x71C1:0x174B:0x0880: name of board and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RV535 on an unidentified card (==) RADEONHD(0): Write-combining range (0xfe9e,0x1) was already clear (II) RADEONHD(0): Mapped IO @ 0xfe9e to 0x8006a2000 (size 0x0001) (II) RADEONHD(0): PCIE Card Detected (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x174b SubsystemID: 0x0880 IOBaseAddress: 0xd000 Filename: 8C88GCSA.003 BIOS Bootup Message: A67120 RV535XT VO BIOS GDDR3 600E/700M snip (II) RADEONHD(0): Found libdri 5.4.0. drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: drmOpenMinor returns 8 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) RADEONHD(0): Found libdrm 1.3.0. (II) RADEONHD(0): Found radeon drm 1.29.0. snip (II) RADEONHD(0): Output DVI-I_2/digital using initial mode 1280x1024 (II) RADEONHD(0): RandR 1.2 support enabled (==) RADEONHD(0): RGB weight 888 (==) RADEONHD(0): Default visual is TrueColor (==) RADEONHD(0): Using gamma correction (1.0, 1.0, 1.0) (II) RADEONHD(0): Using 1280x1280 Framebuffer with 1280 pitch (II) RADEONHD(0): FB: Allocated ScanoutBuffer at offset 0x8000 (size = 0x0064) (**) RADEONHD(0): Display dimensions: (376, 301) mm (**) RADEONHD(0): DPI set to (86, 108) snip (II) RADEONHD(0): On Crtc 0 Setting 60.0 Hz Mode: Modeline 1280x1024 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync I wonder if the framebuffer size is OK? The screen is 1280x1024. That is probably why the DPI is wacky (should both be 86). Should I write the card in to opensuse.org? The card is a Sapphire Radeon X1650Pro. Additionally (but maybe unrelated), when I try to start tyr-glquake, it bombs with an X error: Callback: in_dgamouse ON X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 137 (XFree86-DGA) Minor opcode of failed request: 2 (XF86DGADirectVideo) Serial number of failed request: 117 Current serial number in output stream: 118 The library libXxf86dga-1.0.2 is installed. I see Xorg loading the extension. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpi4zSgaW1tj.pgp Description: PGP signature
Re: Pending MFC of drm updates
On Thu, 2009-01-08 at 22:26 +0100, Roland Smith wrote: On Tue, Jan 06, 2009 at 12:36:20PM -0500, Robert Noland wrote: I have a patch available for testing at http://people.freebsd.org/~rnoland/drm-update-7-010609.patch.bz2 Excellent! Thanks for your hard work on this, Robert! After updating my source to 7.1-RELEASE, I applied this patch and built and installed a new kernel and world. This went without problems. Starting X on a Sapphire Radeon X1650Pro works OK. XAA 2D accelleration works OK. The X logfile says that direct rendering is enabled, as is Xv. Mplayer works with Xv. But whenever I try to start a program that uses OpenGL (i.e. glxgears) I get the following message: unknown chip id 0x71c1, can't guess. libGL warning: 3D driver returned no fbconfigs. libGL error: InitDriver failed libGL error: reverting to (slow) indirect rendering Yep, you need the updated xorg and mesa. We are getting ready to update the ports collection. I may build up a new patch in a little while. robert. :-( The same number shows in Xorg.0.log: snip (--) PCI:*(1:0:0) ATI Technologies Inc unknown chipset (0x71c1) rev 158, Mem @ 0xe000/28, 0xfe9e/16, I/O @ 0xd000/8, BIOS @ 0xfe9c/17 snip (II) Loading extension XFree86-DGA snip (--) Chipset RV535 found snip (II) RADEONHD(0): Unknown card detected: 0x71C1:0x174B:0x0880. If - and only if - your card does not work or does not work optimally please contact radeo...@opensuse.org to help rectify this. Use the subject: 0x71C1:0x174B:0x0880: name of board and *please* describe the problems you are seeing in your message. (--) RADEONHD(0): Detected an RV535 on an unidentified card (==) RADEONHD(0): Write-combining range (0xfe9e,0x1) was already clear (II) RADEONHD(0): Mapped IO @ 0xfe9e to 0x8006a2000 (size 0x0001) (II) RADEONHD(0): PCIE Card Detected (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x174b SubsystemID: 0x0880 IOBaseAddress: 0xd000 Filename: 8C88GCSA.003 BIOS Bootup Message: A67120 RV535XT VO BIOS GDDR3 600E/700M snip (II) RADEONHD(0): Found libdri 5.4.0. drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 8, (OK) drmOpenByBusid: drmOpenMinor returns 8 drmOpenByBusid: drmGetBusid reports pci::01:00.0 (II) RADEONHD(0): Found libdrm 1.3.0. (II) RADEONHD(0): Found radeon drm 1.29.0. snip (II) RADEONHD(0): Output DVI-I_2/digital using initial mode 1280x1024 (II) RADEONHD(0): RandR 1.2 support enabled (==) RADEONHD(0): RGB weight 888 (==) RADEONHD(0): Default visual is TrueColor (==) RADEONHD(0): Using gamma correction (1.0, 1.0, 1.0) (II) RADEONHD(0): Using 1280x1280 Framebuffer with 1280 pitch (II) RADEONHD(0): FB: Allocated ScanoutBuffer at offset 0x8000 (size = 0x0064) (**) RADEONHD(0): Display dimensions: (376, 301) mm (**) RADEONHD(0): DPI set to (86, 108) snip (II) RADEONHD(0): On Crtc 0 Setting 60.0 Hz Mode: Modeline 1280x1024 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync I wonder if the framebuffer size is OK? The screen is 1280x1024. That is probably why the DPI is wacky (should both be 86). Should I write the card in to opensuse.org? The card is a Sapphire Radeon X1650Pro. Additionally (but maybe unrelated), when I try to start tyr-glquake, it bombs with an X error: Callback: in_dgamouse ON X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 137 (XFree86-DGA) Minor opcode of failed request: 2 (XF86DGADirectVideo) Serial number of failed request: 117 Current serial number in output stream: 118 The library libXxf86dga-1.0.2 is installed. I see Xorg loading the extension. Roland signature.asc Description: This is a digitally signed message part
Re: igb on a Nehalem system, buildworld stats
On Fri, Jan 09, 2009 at 02:50:45AM +0800, Mars G Miro wrote: On Fri, Jan 9, 2009 at 2:33 AM, Jack Vogel jfvo...@gmail.com wrote: Well, I am at Intel you know, and even we don't seem to have any systems with 82576 down in my group here. The way link works I can be about 99.9% sure in saying its not the driver. Its preproduction so there are lots of possibilities, and the biggest problem is its going to be difficult to help when I don't have any such hardware :( I've heard from the 1G product team that they have seen EEPROM mismatches on systems that will result in things not working in funny ways. Jahh, I've seen those but not w/ Intel NICs. I believe it was from Broadcom on some IBM x3455? (IIRC) and it was indeed quite amusing ;-) If you have a back to back connection to another NIC on Port 0, no switch, does it still autoneg to 100? I will have do that tomorrow as I am @home now ;-) btw, another data point, during sysinstall, we encountered: unknown network interface type on both the igbs. This is due to missing a missing device entry in the sysinstall code. Unfortunately there are entries missing for several new drivers, I will commit a patch to fix this soon. Anyway, it shouldn't be related to your problems. - Christian -- Christian Brueffer ch...@unixpages.org bruef...@freebsd.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgpxamjPY4bMJ.pgp Description: PGP signature
Re: possibility of a severe flaw in the logic of FreeBSD's kernel handling multiple host bridges ...
On Thu, 2009-01-08 at 20:20 +0100, Manfred_Knick wrote: First: Congratulations upon 7.1 final RELEASE ! On Fri, 24 Oct 2008, I pointed out the possibility of a severe flaw in the logic of FreeBSD's kernel handling multiple host bridges and the corresponding assignment of (in principle, correctly detected) devices to their host bridges :: -- http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/128331 :: -- http://forums.freebsd.org/showthread.php?t=236 but unfortunately, I did not get any response at all. Two mails to kensm...@cse.buffalo.edu asking for any contact e-mail address of a FreeBSD Kernel developer knowing his way around host-bridges and PCI-devices also gave no reaction. I am sorry for this noise (I would have preferred to handle this more quietly), but finally I take hope to the advice of Daniel Gerzo (Thanks @ danger): If you will not receive any feedback I would recommend you to send an email to current@ and stable@ mailing lists. PR's sometimes get lost in the traffic and not all developers are checking GNATS all the time. Looking forward to a contact I'm really not sure that I am the best person to try and tackle this, but it does fall somewhere near me... Can you send me a pciconf -lv. robert. Kind regards Manfred ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org signature.asc Description: This is a digitally signed message part
Big problems with 7.1 locking up :-(
I have a number of HP 1U servers, all of which were running 7.0 perfectly happily. I have been testing 7.1 in it's various incarnations for the last couple of months on our test server and it has performed perfectly. So the last two days I have been round upgrading all our servers, knowing that I had run the system stably on identical hardware for some time. Since then I have starte seeing machines lock up. This always happens under heavy disc load. When I bring the machine back up then sometimes it fails to fsck due to a partialy truncated inode. The locksup appear to be disc related - on my mysql msater machine it will come back up with files somewhat shorted than those which ahve aready been transmitted to the slave (i.e. some data was in memory, and claimed to have been written to the drive, but never made it onto the disc). The only time I have seen anything useful on the screen was during one lockup where I got a message about a spin lock being held too long and some comment in parentheses about it being a turnstile lock. Help! :-( I am now downgrading all the machine to 7.0 as fast as I can - though the machine I am trying to compile it on has locked up once during the compile so I havent got anywhere so far. The machines are HP Proliant DL360 G5s - they have an embedded P400i RAID controller with a pair of mirrored drives connected. Each one has both ethernets connected, bundled using lagg and LACP. Advice ? -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD Update should be back to normal
On 09/01/2009, at 7:19 AM, Colin Percival wrote: 2. Assuming the first mirror still fails, use the -s option to pick a different mirror. Where can we find a list of mirrors? Ari Maniatis -- ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD Update should be back to normal
Aristedes Maniatis wrote, on 1/8/2009 5:12 PM: On 09/01/2009, at 7:19 AM, Colin Percival wrote: 2. Assuming the first mirror still fails, use the -s option to pick a different mirror. Where can we find a list of mirrors? This technically answers your question, but may not be very interesting. ;-) ro...@heffalump$ host -t srv _http._tcp.update.FreeBSD.org _http._tcp.update.FreeBSD.org has SRV record 1 10 80 update1.FreeBSD.org. _http._tcp.update.FreeBSD.org has SRV record 1 10 80 update3.FreeBSD.org. _http._tcp.update.FreeBSD.org has SRV record 1 25 80 update2.FreeBSD.org. _http._tcp.update.FreeBSD.org has SRV record 1 30 80 update4.FreeBSD.org. Since it's unlikely that most people need to query the servers via some means other than freebsd-update, and since freebsd-update automatically pulls its list of mirrors from DNS, this is really only for the sake of curiosity. The list of mirrors can change at any time, which should be transparent to users of freebsd-update. It looks like a couple of them are through Voxel's content delivery network (CDN). I think that one of them has been hosted by ISC for some time. Since the Voxel ones are 3 and 4, I'm guessing that they are the newcomers. ro...@heffalump$ host update1.FreeBSD.org update1.FreeBSD.org has address 72.21.59.252 ro...@heffalump$ host 72.21.59.252 252.59.21.72.in-addr.arpa domain name pointer 252.59.21.72.static.reverse.ltdomains.com. ro...@heffalump$ host update2.FreeBSD.org update2.FreeBSD.org has address 149.20.64.41 ro...@heffalump$ host 149.20.64.41 41.64.20.149.in-addr.arpa domain name pointer update2.freebsd.org. ro...@heffalump$ whois 149.20.64.41 | grep OrgName OrgName:Internet Systems Consortium, Inc. ro...@heffalump$ host update3.FreeBSD.org update3.FreeBSD.org has address 72.26.203.74 ro...@heffalump$ host 72.26.203.74 74.203.26.72.in-addr.arpa domain name pointer update3.FreeBSD.org. ro...@heffalump$ whois 72.26.203.74 | grep OrgName OrgName:Voxel Dot Net, Inc. ro...@heffalump$ host update4.FreeBSD.org update4.FreeBSD.org is an alias for content.voxcdn.net. content.voxcdn.net is an alias for content.loc.voxcdn.net. content.loc.voxcdn.net is an alias for content.sjc1.site.voxcdn.net. content.sjc1.site.voxcdn.net has address 208.122.62.226 Royce -- Royce D. Williams - http://royce.ws/ Words are good servants but bad masters. - Aldous Huxley ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: CFT: ath hal src switchover
On Jan 8, 2009, at 15:12 , Sam Leffler wrote: I've brought the hal source code back to RELENG_7 but not connected it to the build and/or driver. I want folks to test this before I commit those changes. To do this you must have an up to date RELENG_7 code base and then apply this patch: http://people.freebsd.org/~sam/ath_hal-releng7.patch Then rebuild your kernel. There should be no changes to user apps. Beware however that custom kernel configurations will need to change; instead of: device ath device ath_hal device ath_rate_sample (or similar) you need: device ath device ath_hal options AH_SUPPORT_AR5416 device ath_rate_sample If you want to configure a subset of the chip support implied by ath_hal then you may not need the options line. If you are using modules note that ath_hal and ath_rate_* modules no longer exist; they are now rolled into the ath module. If you use a rate control algorithm other than sample then you'll need to modify the ath module build or override by specifying ATH_RATE; e.g. cd sys/modules/ath make ATH_RATE=onoe The updated hal code adds support for several parts but otherwise makes no effort to address driver bugs. You should see no regressions relative to operation w/ the older hal. If you are running the 7.1 release you will need to import the hal code that is now in sys/dev/ath/ath_hal before following the above instructions. I have no idea if this will work for an earlier version of FreeBSD; if you're not running at least 7.1 my advise is to upgrade. Please report any issues to this mailing list. With this code in my kernel I get: ath0: unable to reset hardware; hal status 0 ioctl[SIOCS80211, op 23, arg 0x0] : Invalid argument Failed to initiate AP scan. ath0: unable to reset hardware; hal status 14 ioctl[SIOCS80211, op 23, arg 0x0] : Invalid argument Failed to initiate AP scan. when I try to use wpa_supplicant with the code. My home network uses WPA. Best, George PGP.sig Description: This is a digitally signed message part
Re: CFT: ath hal src switchover
On Thu, 8 Jan 2009, Sam Leffler wrote: I've brought the hal source code back to RELENG_7 but not connected it to the build and/or driver. I want folks to test this before I commit those changes. To do this you must have an up to date RELENG_7 code base and then apply this patch: http://people.freebsd.org/~sam/ath_hal-releng7.patch *snip* Please report any issues to this mailing list. No problems for my Netgear WPN511. It works well at home. Now, if I just could figure out why the recent Aruba update at work is preventing me from authenticating with it, I would be happy. This is not related to the MFC of the code. iPhones and MacOSX 10.4 (but not 10.5) are also having problems. Windows works. Sean -- s...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD Update should be back to normal
Aristedes Maniatis wrote: On 09/01/2009, at 7:19 AM, Colin Percival wrote: 2. Assuming the first mirror still fails, use the -s option to pick a different mirror. Where can we find a list of mirrors? The list of is distributed via DNS SRV records: # host -t srv _http._tcp.update.freebsd.org prints a list of the mirrors (currently update1 through update4, but that is subject to change). -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
