Re: Can't get if_txp(4) to attach to a 3CR990B-TXM NIC
On Fri, Jun 08, 2007 at 09:13:37AM -0700, Freddie Cash wrote:
> Good morning,
>
> I'm having a bit of an issue getting a 3CR990B-TXM NIC detected and
> usable. Just wondering if anyone knows of any issues with this NIC
> chipset and/or with the motherboard chipset.
>
> The motherboard is a Biostar GeForce 6100 AM2 using an nVidia nForce 410
> chipset and nVidia GeForce 6100 vide chipset.
>
> I've tried FreeBSD 6.1, 6.2, 6-STABLE (from Wed), and 7-CURRENT (from Thu)
> on this system. Everything installs nicely, everything on the board is
> detected correctly and usable. It's just the PCI NIC that doesn't work.
>
> If I compile a custom kernel without any network drivers in it, and then
> kldload if_txp, the following appears (same message on all 4 versions):
>
> txp0: <3Com 3cR990B-TXM Etherlink with 3XP Processor> port 0xbc00-0xbc7f
> mem 0xfdcff000-0xfdcff07f irq 16 at device 8.0 on pci3
> txp0: not waiting for boot
> device_attach: txp0 attach returned -1
>
Would you try attached path?
It wouldn't fix your issue but it will handle failure of contigmalloc
as expected.
> If I reboot and load if_nve (on 6.2 and 6-stable), then I get:
> nve0: port 0xdc00-0xdc07 mem
> 0xfe02d000-0xfe02dfff irq 22 at device 20.0 on pci0
> nve0: Ethernet address 00:19:21:37:d5:60
>
> Followed by the above messages for txp0 (it seems to detect and load
> if_txp automativally when loading if_nve).
>
> I've updated the BIOS on the motherboard. I've tried different PCI slots
> on the motherboard. Nothing changes. The "not waiting for boot" message
> keeps appearing.
>
> Attached are dmesg output from:
> 6.1-RELEASE GENERIC kerneldmesg_6.1.txt
> 6.2-RELEASE GENERIC kerneldmesg_6.2.txt
> 6.2-RELEASE GENERIC kernel verbose boot dmesg_6.2_verbose.txt
> 6-STABLE GENERIC kerneldmesg_6_generic.txt
> 6-STABLE TEST kernel (no NIC drivers) dmesg_6_custom.txt
> 7-CURRENTGENERIC kerneldmesg_7_generic.txt
> 7-CURRENTTEST kernel (no NIC drivers) dmesg_7_custom.txt
>
> I've looked through the cvsweb entries for txp and didn't see anything
> related to this issue. Reading the man page for if_txp(4) doesn't show
> anything about this error. I tried reading the source, but C is pretty
> much Greek to me.
>
> Everything I've read online says this NIC should work, and other are using
> it successfully. My gut feeling is that it's something to do with the
> motherboard chipset and the way it detects the NIC. But I could be way
> off.
>
> (As a test, I popped in a Kanotix LiveCD and the 3Com NIC is detected and
> usable, so it's [hopefully] not a defective NIC.)
>
> Anyone have any suggestions? Comments? Methods to destroy the NIC as an
> act of defiance? :)
>
--
Regards,
Pyun YongHyeon
Index: if_txp.c
===
RCS file: /home/ncvs/src/sys/dev/txp/if_txp.c,v
retrieving revision 1.44
diff -u -r1.44 if_txp.c
--- if_txp.c4 Mar 2007 03:38:08 - 1.44
+++ if_txp.c9 Jun 2007 04:56:59 -
@@ -264,6 +264,11 @@
sc->sc_fwbuf = contigmalloc(32768, M_DEVBUF,
M_NOWAIT, 0, 0x, PAGE_SIZE, 0);
+ if (sc->sc_fwbuf == NULL) {
+ device_printf(dev, "no memory for firmware\n");
+ error = ENXIO;
+ goto fail;
+ }
error = txp_download_fw(sc);
contigfree(sc->sc_fwbuf, 32768, M_DEVBUF);
sc->sc_fwbuf = NULL;
@@ -273,6 +278,11 @@
sc->sc_ldata = contigmalloc(sizeof(struct txp_ldata), M_DEVBUF,
M_NOWAIT, 0, 0x, PAGE_SIZE, 0);
+ if (sc->sc_ldata == NULL) {
+ device_printf(dev, "no memory for descriptor ring\n");
+ error = ENXIO;
+ goto fail;
+ }
bzero(sc->sc_ldata, sizeof(struct txp_ldata));
if (txp_alloc_rings(sc)) {
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
First of all, your question is about ports, so it should have been directed to the freebsd-ports@ list, FYI. Stephen Clark wrote: > There is a deadly embrace. I think you are overthinking this, and it didn't help that the only advice you got was to re-read the instructions. You want to first upgrade your existing ports, then you should install /usr/ports/x11/xorg to make sure you have all the components. If you don't want to use portupgrade to do the update, there are other alternatives, including using portmaster. Take a look at http://www.freebsd.org/cgi/getmsg.cgi?fetch=2209+0+/usr/local/www/db/text/2007/freebsd-ports/20070603.freebsd-ports hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
On Fri, Jun 08, 2007 at 04:20:29PM -0400, Stephen Clark wrote: > So I should wait a about week after I do a cvsup of ports - then > hopefully most of the packages will be there - right? Yes, but you'll have to check. Some ports (not the X11 ones) can't be packaged due to licensing restrictions. You can get a good idea of the state of the current build errors for packages from pointyhat on http://pointyhat.freebsd.org/errorlogs/i386-6-latest/; to find out the package state of any port, use portsmon at (e.g.) http://portsmon.freebsd.org/portoverview.py?category=x11&portname=xorg . Both the pointyhat index pages and the portsmon summaries contain a great deal of information, but you have to do a little bit of research. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
Mark Linimon wrote: On Fri, Jun 08, 2007 at 03:26:21PM -0400, Stephen Clark wrote: Thats another question - why aren't packages released simultaneously with the ports update? There's a circular dependency here. The ports tree is updated by checkins, which is then pushed to the package building system, which then does complete package builds -- which can take a week or more, depending. We don't have any way to tell the package system "here is what the ports tree will be a week from now"; it's simply driven by cvs checkout, and after that it's simply a matter a machine horsepower to crank them out. We have a fair amount of i386 and amd64 horsepower (the latter is a recent development); we have a grossly insufficient amount of sparc64 horsepower, and so the packages are ~3 weeks behind. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" So I should wait a about week after I do a cvsup of ports - then hopefully most of the packages will be there - right? Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
On Fri, Jun 08, 2007 at 03:26:21PM -0400, Stephen Clark wrote: > Thats another question - why aren't packages released simultaneously > with the ports update? There's a circular dependency here. The ports tree is updated by checkins, which is then pushed to the package building system, which then does complete package builds -- which can take a week or more, depending. We don't have any way to tell the package system "here is what the ports tree will be a week from now"; it's simply driven by cvs checkout, and after that it's simply a matter a machine horsepower to crank them out. We have a fair amount of i386 and amd64 horsepower (the latter is a recent development); we have a grossly insufficient amount of sparc64 horsepower, and so the packages are ~3 weeks behind. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
Nikolay Pavlov wrote: On Friday, 8 June 2007 at 14:34:14 -0400, Stephen Clark wrote: Kevin Oberman wrote: Date: Fri, 08 Jun 2007 12:45:34 -0400 From: Stephen Clark <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] Tom Evans wrote: On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote: Hello List, A few weeks ago I installed 6.2. I did a cvsup of the ports and now anytime I try to make anything that uses X I get something like the following: ===> Patching for tk-8.5.a.6_1 ===> Applying FreeBSD patches for tk-8.5.a.6_1 ===> tk-8.5.a.6_1 depends on file: /usr/local/libdata/xorg/libraries - not found ===>Verifying install for /usr/local/libdata/xorg/libraries in /usr/ports/x11/xorg-libraries Read /usr/ports/UPDATING for the procedure to upgrade or install xorg 7.2. *** Error code 1 I have xorg-6.9 installed from the release iso - I selected x-kernel-developer Does this install all the things that would be installed from the xorg meta port? Because if I do a pkg_info I don't see anything that says xorg meta port. This is my work - workstation and I don't want to fubar it. If this is your working workstation i recomend to wait for packages. You will lost the day or two or even more. Thats another question - why aren't packages released simultaneously with the ports update? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
On Friday, 8 June 2007 at 14:34:14 -0400, Stephen Clark wrote: > Kevin Oberman wrote: > > >>Date: Fri, 08 Jun 2007 12:45:34 -0400 > >>From: Stephen Clark <[EMAIL PROTECTED]> > >>Sender: [EMAIL PROTECTED] > >> > >>Tom Evans wrote: > >> > >> > >>>On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote: > >>> > >>> > Hello List, > > A few weeks ago I installed 6.2. I did a cvsup of the ports and now > anytime I try to make > anything that uses X I get something like the following: > > ===> Patching for tk-8.5.a.6_1 > ===> Applying FreeBSD patches for tk-8.5.a.6_1 > ===> tk-8.5.a.6_1 depends on file: /usr/local/libdata/xorg/libraries - > not found > ===>Verifying install for /usr/local/libdata/xorg/libraries in > /usr/ports/x11/xorg-libraries > Read /usr/ports/UPDATING for the procedure to upgrade or install xorg 7.2. > *** Error code 1 > > > I have been following the thread on xorg 7.2. > > The /usr/src/UPDATING says under caveats > "Make sure you have the x11/xorg meta-port installed" > > When I run make in the x11/xorg dir I get the following which > says use portupgrade if you want to upgrade X.Org. > > > /usr/ports/x11/xorg]# make > This is a meta-port, meaning that it just depends on its subparts of the > port. > It won't build and install all the parts until you have typed make install > This port does not ensure things are upgraded; use portupgrade if you > want to > upgrade X.Org. If you simply type 'make install' it may use over 2GB to > build > all of the subports. You can install the ports singly if you are low on > space. > > So now which is it? > > Use the meta port or portupgrade? > > Thanks, > Steve > > > > >>>I'd read /usr/ports/UPDATING again, if you follow the exact instructions > >>> > >>> > >> I have it printed out sitting right in > >> front of me. > >> > >> > >>>in that file, you won't have many problems. > >>> > >>> > >>But what about this paragraph under caveats from /usr/ports/UPDATING: > >> > >>"Make sure you have the x11/xorg meta-port installed. If you do not have > >> this meta-port installed with X.Org 6.9, you will miss out on a lot of > >> the new X.Org 7.2 sub-ports." > >> > > > >Do you have xorg-6.9 installed before starting? If not, you might well > >want to install it after the upgrade. If it is already installed, it > >will be automatically upgraded, so don't worry about it. > > > >That said, my experience in updating about a dozen systems is to roll > >the ports tree back to before 7.2 was committed and install xorg > >(portinstall xorg) before starting the upgrade. It's not essential that > >you do so, but it does eliminate some rough edges in the upgrade as the > >main test case was almost certainly with xorg-6.9 installed on systems > >prior to the upgrade. > > > I have xorg-6.9 installed from the release iso - I selected x-kernel-developer > > Does this install all the things that would be installed from the xorg meta > port? Because > if I do a pkg_info I don't see anything that says xorg meta port. > > This is my work - workstation and I don't want to fubar it. If this is your working workstation i recomend to wait for packages. You will lost the day or two or even more. > > Thanks to all who have responded. > > Steve > > -- > > "They that give up essential liberty to obtain temporary safety, deserve > neither liberty nor safety." (Ben Franklin) > > "The course of history shows that as a government grows, liberty decreases." > (Thomas Jefferson) > > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- == - Best regards, Nikolay Pavlov. <<<--- == ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
> Date: Fri, 08 Jun 2007 12:45:34 -0400 > From: Stephen Clark <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > Tom Evans wrote: > > >On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote: > > > > > >>Hello List, > >> > >>A few weeks ago I installed 6.2. I did a cvsup of the ports and now > >>anytime I try to make > >>anything that uses X I get something like the following: > >> > >>===> Patching for tk-8.5.a.6_1 > >>===> Applying FreeBSD patches for tk-8.5.a.6_1 > >>===> tk-8.5.a.6_1 depends on file: /usr/local/libdata/xorg/libraries - > >>not found > >>===>Verifying install for /usr/local/libdata/xorg/libraries in > >>/usr/ports/x11/xorg-libraries > >>Read /usr/ports/UPDATING for the procedure to upgrade or install xorg 7.2. > >>*** Error code 1 > >> > >> > >>I have been following the thread on xorg 7.2. > >> > >>The /usr/src/UPDATING says under caveats > >>"Make sure you have the x11/xorg meta-port installed" > >> > >>When I run make in the x11/xorg dir I get the following which > >>says use portupgrade if you want to upgrade X.Org. > >> > >> > >>/usr/ports/x11/xorg]# make > >>This is a meta-port, meaning that it just depends on its subparts of the > >>port. > >>It won't build and install all the parts until you have typed make install > >>This port does not ensure things are upgraded; use portupgrade if you > >>want to > >>upgrade X.Org. If you simply type 'make install' it may use over 2GB to > >>build > >>all of the subports. You can install the ports singly if you are low on > >>space. > >> > >>So now which is it? > >> > >>Use the meta port or portupgrade? > >> > >>Thanks, > >>Steve > >> > >> > >> > > > >I'd read /usr/ports/UPDATING again, if you follow the exact instructions > > > > > I have it printed out sitting right > in front of me. > > >in that file, you won't have many problems. > > > > > But what about this paragraph under caveats from /usr/ports/UPDATING: > > "Make sure you have the x11/xorg meta-port installed. If you do not have > this meta-port installed with X.Org 6.9, you will miss out on a lot of > the new X.Org 7.2 sub-ports." Do you have xorg-6.9 installed before starting? If not, you might well want to install it after the upgrade. If it is already installed, it will be automatically upgraded, so don't worry about it. That said, my experience in updating about a dozen systems is to roll the ports tree back to before 7.2 was committed and install xorg (portinstall xorg) before starting the upgrade. It's not essential that you do so, but it does eliminate some rough edges in the upgrade as the main test case was almost certainly with xorg-6.9 installed on systems prior to the upgrade. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgplGQQfwiIJ4.pgp Description: PGP signature
Re: upgrade 6.2 to xorg 7.2
Kevin Oberman wrote:
Date: Fri, 08 Jun 2007 12:45:34 -0400
From: Stephen Clark <[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
Tom Evans wrote:
On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote:
Hello List,
A few weeks ago I installed 6.2. I did a cvsup of the ports and now
anytime I try to make
anything that uses X I get something like the following:
===> Patching for tk-8.5.a.6_1
===> Applying FreeBSD patches for tk-8.5.a.6_1
===> tk-8.5.a.6_1 depends on file: /usr/local/libdata/xorg/libraries -
not found
===>Verifying install for /usr/local/libdata/xorg/libraries in
/usr/ports/x11/xorg-libraries
Read /usr/ports/UPDATING for the procedure to upgrade or install xorg 7.2.
*** Error code 1
I have been following the thread on xorg 7.2.
The /usr/src/UPDATING says under caveats
"Make sure you have the x11/xorg meta-port installed"
When I run make in the x11/xorg dir I get the following which
says use portupgrade if you want to upgrade X.Org.
/usr/ports/x11/xorg]# make
This is a meta-port, meaning that it just depends on its subparts of the
port.
It won't build and install all the parts until you have typed make install
This port does not ensure things are upgraded; use portupgrade if you
want to
upgrade X.Org. If you simply type 'make install' it may use over 2GB to
build
all of the subports. You can install the ports singly if you are low on
space.
So now which is it?
Use the meta port or portupgrade?
Thanks,
Steve
I'd read /usr/ports/UPDATING again, if you follow the exact instructions
I have it printed out sitting right
in front of me.
in that file, you won't have many problems.
But what about this paragraph under caveats from /usr/ports/UPDATING:
"Make sure you have the x11/xorg meta-port installed. If you do not have
this meta-port installed with X.Org 6.9, you will miss out on a lot of
the new X.Org 7.2 sub-ports."
Do you have xorg-6.9 installed before starting? If not, you might well
want to install it after the upgrade. If it is already installed, it
will be automatically upgraded, so don't worry about it.
That said, my experience in updating about a dozen systems is to roll
the ports tree back to before 7.2 was committed and install xorg
(portinstall xorg) before starting the upgrade. It's not essential that
you do so, but it does eliminate some rough edges in the upgrade as the
main test case was almost certainly with xorg-6.9 installed on systems
prior to the upgrade.
I have xorg-6.9 installed from the release iso - I selected
x-kernel-developer
Does this install all the things that would be installed from the xorg
meta port? Because
if I do a pkg_info I don't see anything that says xorg meta port.
This is my work - workstation and I don't want to fubar it.
Thanks to all who have responded.
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
Stephen Clark wrote: > There is a deadly embrace. > > The /usr/src/UPDATING says I am going to miss out if I > don't have the meta port installed (which I currently don't), but when I > try to install > the meta port it tells me I should use portupgrade to upgrade Xorg, but > the /usr/src/UPDATING > which talks about using portupgrade says I am going to miss out if I > don't have the meta > port installed (which I currently don't), but when I try to install the > meta port it tells me I > should use portupgrade to upgrade Xorg, but ad infinitum! > > Steve > It would appear you are skipping over the relevant portion of UPDATING. The message you are seeing appears when your environment does not have XORG_UPGRADE=yes set in its environment. This is necessary even after you have completed the instructions, and for future updates. The exact reasoning and such was discussed on the ports list and can be found in the archives. I believe someone (Kris?) said that this will be necessary for the time being, but not at some yet-to-be-determined point in the future. Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
On Jun 8, 2007, at 10:41 AM, Stephen Clark wrote: There is a deadly embrace. The /usr/src/UPDATING says I am going to miss out if I don't have the meta port installed (which I currently don't), but when I try to install the meta port it tells me I should use portupgrade to upgrade Xorg, but the /usr/src/UPDATING which talks about using portupgrade says I am going to miss out if I don't have the meta port installed (which I currently don't), but when I try to install the meta port it tells me I should use portupgrade to upgrade Xorg, but ad infinitum! Read the 20070519 entry carefully, and follow the instructions, in the order presented, carefully. If they don't work, you should use script or nohup to save the error messages to a logfile which you quote in followup emails so we can take a look. In order words, you should start with: portupgrade -f -o ports-mgmt/portupgrade-devel portupgrade -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
Oliver Fromme wrote: Stephen Clark wrote: > Tom Evans wrote: > > Stephen Clark wrote: > > I'd read /usr/ports/UPDATING again, if you follow the exact instructions > > > I have it printed out sitting right > in front of me. Then there shouldn't be any problem. > But what about this paragraph under caveats from /usr/ports/UPDATING: > > "Make sure you have the x11/xorg meta-port installed. If you do not have > this meta-port installed with X.Org 6.9, you will miss out on a lot of > the new X.Org 7.2 sub-ports." Exactly what that paragraph says. I've read your first email message again and I'm still unable to find out what your actual problem is. What exactly is unclear to you, or what part of the update failed for you? (Please paste the error message if you got one.) Best regards Oliver There is a deadly embrace. The /usr/src/UPDATING says I am going to miss out if I don't have the meta port installed (which I currently don't), but when I try to install the meta port it tells me I should use portupgrade to upgrade Xorg, but the /usr/src/UPDATING which talks about using portupgrade says I am going to miss out if I don't have the meta port installed (which I currently don't), but when I try to install the meta port it tells me I should use portupgrade to upgrade Xorg, but ad infinitum! Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
Stephen Clark wrote: > Tom Evans wrote: > > Stephen Clark wrote: > > I'd read /usr/ports/UPDATING again, if you follow the exact instructions > > > I have it printed out sitting right > in front of me. Then there shouldn't be any problem. > But what about this paragraph under caveats from /usr/ports/UPDATING: > > "Make sure you have the x11/xorg meta-port installed. If you do not have > this meta-port installed with X.Org 6.9, you will miss out on a lot of > the new X.Org 7.2 sub-ports." Exactly what that paragraph says. I've read your first email message again and I'm still unable to find out what your actual problem is. What exactly is unclear to you, or what part of the update failed for you? (Please paste the error message if you got one.) 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 Perl is worse than Python because people wanted it worse. -- Larry Wall ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
Tom Evans wrote:
On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote:
Hello List,
A few weeks ago I installed 6.2. I did a cvsup of the ports and now
anytime I try to make
anything that uses X I get something like the following:
===> Patching for tk-8.5.a.6_1
===> Applying FreeBSD patches for tk-8.5.a.6_1
===> tk-8.5.a.6_1 depends on file: /usr/local/libdata/xorg/libraries -
not found
===>Verifying install for /usr/local/libdata/xorg/libraries in
/usr/ports/x11/xorg-libraries
Read /usr/ports/UPDATING for the procedure to upgrade or install xorg 7.2.
*** Error code 1
I have been following the thread on xorg 7.2.
The /usr/src/UPDATING says under caveats
"Make sure you have the x11/xorg meta-port installed"
When I run make in the x11/xorg dir I get the following which
says use portupgrade if you want to upgrade X.Org.
/usr/ports/x11/xorg]# make
This is a meta-port, meaning that it just depends on its subparts of the
port.
It won't build and install all the parts until you have typed make install
This port does not ensure things are upgraded; use portupgrade if you
want to
upgrade X.Org. If you simply type 'make install' it may use over 2GB to
build
all of the subports. You can install the ports singly if you are low on
space.
So now which is it?
Use the meta port or portupgrade?
Thanks,
Steve
I'd read /usr/ports/UPDATING again, if you follow the exact instructions
I have it printed out sitting right
in front of me.
in that file, you won't have many problems.
But what about this paragraph under caveats from /usr/ports/UPDATING:
"Make sure you have the x11/xorg meta-port installed. If you do not have
this meta-port installed with X.Org 6.9, you will miss out on a lot of
the new X.Org 7.2 sub-ports."
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrade 6.2 to xorg 7.2
On Fri, 2007-06-08 at 09:22 -0400, Stephen Clark wrote: > Hello List, > > A few weeks ago I installed 6.2. I did a cvsup of the ports and now > anytime I try to make > anything that uses X I get something like the following: > > ===> Patching for tk-8.5.a.6_1 > ===> Applying FreeBSD patches for tk-8.5.a.6_1 > ===> tk-8.5.a.6_1 depends on file: /usr/local/libdata/xorg/libraries - > not found > ===>Verifying install for /usr/local/libdata/xorg/libraries in > /usr/ports/x11/xorg-libraries > Read /usr/ports/UPDATING for the procedure to upgrade or install xorg 7.2. > *** Error code 1 > > > I have been following the thread on xorg 7.2. > > The /usr/src/UPDATING says under caveats > "Make sure you have the x11/xorg meta-port installed" > > When I run make in the x11/xorg dir I get the following which > says use portupgrade if you want to upgrade X.Org. > > > /usr/ports/x11/xorg]# make > This is a meta-port, meaning that it just depends on its subparts of the > port. > It won't build and install all the parts until you have typed make install > This port does not ensure things are upgraded; use portupgrade if you > want to > upgrade X.Org. If you simply type 'make install' it may use over 2GB to > build > all of the subports. You can install the ports singly if you are low on > space. > > So now which is it? > > Use the meta port or portupgrade? > > Thanks, > Steve > I'd read /usr/ports/UPDATING again, if you follow the exact instructions in that file, you won't have many problems. signature.asc Description: This is a digitally signed message part
autofs
Hi, list. I'm find in source tree : /usr/src/lib/libautofs /usr/src/sbin/mount_autofs /usr/src/share/examples/autofs /usr/src/share/man/man5/autofs.5 Sorry, for stupid question. Could somebody explain me, how I can build it and why it doesn't build by default? WBR. Dmitriy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
upgrade 6.2 to xorg 7.2
Hello List, A few weeks ago I installed 6.2. I did a cvsup of the ports and now anytime I try to make anything that uses X I get something like the following: ===> Patching for tk-8.5.a.6_1 ===> Applying FreeBSD patches for tk-8.5.a.6_1 ===> tk-8.5.a.6_1 depends on file: /usr/local/libdata/xorg/libraries - not found ===>Verifying install for /usr/local/libdata/xorg/libraries in /usr/ports/x11/xorg-libraries Read /usr/ports/UPDATING for the procedure to upgrade or install xorg 7.2. *** Error code 1 I have been following the thread on xorg 7.2. The /usr/src/UPDATING says under caveats "Make sure you have the x11/xorg meta-port installed" When I run make in the x11/xorg dir I get the following which says use portupgrade if you want to upgrade X.Org. /usr/ports/x11/xorg]# make This is a meta-port, meaning that it just depends on its subparts of the port. It won't build and install all the parts until you have typed make install This port does not ensure things are upgraded; use portupgrade if you want to upgrade X.Org. If you simply type 'make install' it may use over 2GB to build all of the subports. You can install the ports singly if you are low on space. So now which is it? Use the meta port or portupgrade? Thanks, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru: runtime went backwards, RELENG_6, SMP
On Wed, 6 Jun 2007, Matthew Dillon wrote: MD> :IV> > Upd: on GENERIC/amd64 kernel I got the same errors. MD> :IV> MD> :IV> Do you perhaps run with TSC timecounter? (that's the only cause I've notice MD> :IV> that can generate this message). MD> : MD> :Nope: MD> : MD> :[EMAIL PROTECTED]:~> sysctl kern.timecounter MD> :kern.timecounter.tick: 1 MD> :kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-100) MD> :kern.timecounter.hardware: ACPI-fast MD> :... MD> MD> kgdb your live kernel and 'print cpu_ticks'. See what the cpu ticker MD> is actually pointing at, because it might not be the time counter. MD> It could still be TSC. Hmm, i'm not sure I understand you right: what do you mean by 'kgdb live kernel'? I send break over serial console, and in ddb got db> print cpu_ticks Symbol not found Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iSCSI initiator tester wanted
> A couple comments just from reading through this, see below.
>
> > #!/bin/sh
> >
> > # PROVIDE: iscsi
> > # REQUIRE: NETWORKING
> > # BEFORE: DAEMON
> > # KEYWORD: nojail shutdown
> >
> > #
> > # Add the following lines to /etc/rc.conf to enable iscsi:
> > #
> > # iscsi_enable="YES"
> > # iscsi_fstab="/etc/fstab.iscsi"
>
> The iscsi_exports knob should also be documented here.
agreed
>
> > . /etc/rc.subr
> >
> > name=iscsi
> > rcvar=`set_rcvar`
> >
> > command=/usr/local/sbin/iscontrol
>
> Assuming this gets commited this will want to be /sbin/iscontrol.
>
absolutely
> > iscsi_enable=${iscsi_enable:-"NO"}
> > iscsi_fstab=${iscsi_fstab:-"/etc/fstab.iscsi"}
> > iscsi_exports=${iscsi_exports:-"/etc/exports.iscsi"}
> >
> > start_cmd="iscsi_start"
> > faststop_cmp="iscsi_stop"
> > stop_cmd="iscsi_stop"
> >
> > iscsi_wait()
> > {
> >dev=$1
> >trap "echo 'wait loop cancelled'; exit 1" 2
> >count=0
> >while true; do
> > if [ -c $dev ]; then
> > break;
> > fi
> > if [ $count -eq 0 ]; then
> > echo -n Waiting for ${dev}': '
> > fi
> > count=$((${count} + 1))
> > if [ $count -eq 6 ]; then
> > echo ' Failed'
> > return 0
> > break
> > fi
> > echo -n '.'
> > sleep 5;
> >done
> >echo '.'
> >return 1
> > }
> >
> > iscsi_start()
> > {
> >#
> ># load needed modules
> >for m in iscsi_initiator geom_label; do
> > kldstat -qm $m || kldload $m
> >done
>
> Good thinking making geom_label a pseudo-requirement. Examples and
> documentation for fstab.iscsi should strongly recommend its use, since
> device names will vary.
>
> >sysctl debug.iscsi=2
>
> Maybe make this another rc variable that could be set in /etc/rc.conf.
> You'll probably also want to change the module's default verbosity
> level once it becomes more official.
it will be zero by default, and no reason to clobber rc.conf.
>
> >#
> ># start iscontrol for each target
> >if [ -n "${iscsi_targets}" ]; then
> > for target in ${iscsi_targets}; do
> > ${command} ${rc_flags} -n ${target}
> > done
> >fi
> >
> >if [ -f "${iscsi_fstab}" ]; then
> > while read spec file type opt t1 t2
> > do
> > case ${spec} in
> > \#*|'')
> > ;;
> > *)
> > if iscsi_wait ${spec}; then
> > break;
> > fi
> > echo type=$type spec=$spec file=$file
> > fsck -p ${spec} && mount ${spec} ${file}
> > ;;
> > esac
> > done < ${iscsi_fstab}
> >fi
> >
> >if [ -f "${iscsi_exports}" ]; then
> > cat ${iscsi_exports} >> /etc/exports
> > #/etc/rc.d/mountd reload does not work, why?
> > kill -1 `cat /var/run/mountd.pid`
> >fi
> > }
>
> Look at how Pawel handled this with ZFS (mostly in the zfs and mountd
> rc.d scripts), and use the fact that mountd can take multiple exports
> files on its command line to your advantage. i.e. appending to the
> normal exports file is not really what you want to do.
I like the idea of keeping things from spreading around, and maybe
/etc/rc.d/mountd
can be taught to use all exportfs.something files might be an idea, specially
since sometimes one has to '/etc/rc.d/mountd reload' - i miss 'exportfs -a' :-)
>
> > iscsi_stop()
> > {
> >echo 'iscsi stopping'
> >while read spec file type opt t1 t2
> > do
> > case ${spec} in
> > \#*|'')
> > ;;
> > *)
> > echo iscsi: umount $spec
> > umount -fv $spec
> > # and remove from the exports ...
>
> See above; this could be a no-op.
>
> > ;;
> > esac
> > done < ${iscsi_fstab}
> > }
> >
> > load_rc_config $name
> > run_rc_command "$1"
> > --
> > problems with the above script:
> > - no background fsck
>
> It would be nice not to re-invent the wheel here, and there are other
> reasons it would be nice to just use /etc/fstab instead of adding a new
> file -- a number of utilities use /etc/fstab to map between mountpoints
> and device names even if the device isn't mounted. Did you try this
> approach, and if so what obstacles did you encounter? I will play
> around with this if I have time. The "late" fstab/mount option will
> probably be useful here.
it all boils down to my not-liking-to-spread-out syndrome, rc.conf should
have all that is needed to configure a host, but alas, that is a too
minimalistic approach, since there are also config files.
well, some of the solutions take into concideration my local environment,
most of the servers and workstations are 'dataless', they share many files, and
via DHCP/rc.conf and some other magic, it all works. Except for 'small' changes
in cofiguration files, ie:
most of the hosts have serial console enabled, but a few problematic ones
don't.
[easy solution: a script that changes off/on accroding to some rc.conf
tunable).
most have a common fstab (cdr
Re: Server setup as a Diskless Server on reboot sends DHCP Discover packets out
Kim Attree wrote: > I've setup a machine as a diskless server, using PXEBoot with ihc-dhcpd > to offer dhcp and dhcp configuration information. I did a test reboot on > the server, and found to my dismay that the server NIC's are sending out > dhcp discover packets and trying to get an address. > > The NIC's IP info is captured correctly in /etc/rc.conf: > [...] > and the /etc/dhclient.conf file is empty. I thought maybe it was the > /conf directory used in the diskless Root structure creation, so I > renamed it out of the way, but that made no difference. > > I can't seem to find where the definition is that makes the NIC's ask > for DHCP info. > > Shortened output of /var/run/dmesg.boot pertaining to the DHCP Discover > packets: > > > Sending DHCP Discover packet from interface bge0 (00:0b:db:e6:a9:33) > Sending DHCP Discover packet from interface bge1 (00:0b:db:e6:a9:35) That's the kernel itself trying to perform BOOTP/DHCP. It does that before mounting the root file system (which might be mounted via NFS anyway, requiring an IP address to be obtained via BOOTP or DHCP). If you don't want that, then remove "options BOOTP" from your kernel config file and rebuild your kernel. 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 "To this day, many C programmers believe that 'strong typing' just means pounding extra hard on the keyboard." -- Peter van der Linden ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard Hang, nothing in logs / no panics
On Fri, Jun 08, 2007 at 11:35:33AM +0400, Alexey Karagodov wrote: > just another some words: > > i have had similar trouble but my server reboots > > problem was in ECC correctable errors but FreeBSD kernel just reboot machine > when this occures > linux kernel wrote me what is the problem > i don't know how to figure out that in FreeBSD and other hardware issues ... Not at all the same, then. Check your BIOS for the event log of ECC errors. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard Hang, nothing in logs / no panics
just another some words: i have had similar trouble but my server reboots problem was in ECC correctable errors but FreeBSD kernel just reboot machine when this occures linux kernel wrote me what is the problem i don't know how to figure out that in FreeBSD and other hardware issues ... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iSCSI initiator tester wanted
... > > The message on the machine running scsi-target is: "Unsupported INQUIRY > > VPD page 80" > yes, I have tested it against ports/net/iscsi-target, I use it to try out > errror recovery :-), and as far as I could tell it's harmelss. > Anothere thing I can report is that running both (target/initiator) does not ^ on the same host > work, and it seems that the target gets stuck. cheers, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
