May 2007 - WLUG - wlug.mailman3.com

Re: [Wlug] last sparc64 gentoo question - I promise
by Jamie Guinan 24 May '07

24 May '07

On Thu, 24 May 2007, ken jones wrote: > I succeeded in doing: > #emerge --sync > #emerge portage > Then I tried > #emerge xorg-x11 > overnight. I woke up to find this had failed on step 101 out of 133. That's actually rather good progress. :) > ------------------- > The first two emerge's completed, emerge xorg-x11 did not. Below is > stdout. Looking at the log it appears that stddef.h is missing... > -----------snip--------- > makedepend: warning: clientattrib.c (reading /usr/include/gconv.h, line > 31): cannot find include file "stddef.h" > ---------snip---------- > Right at the end stdout said, "!!! If you need support, post the > topmost build error, and the call stack if relevant." > I have no idea what this means. Do you? > Any suggestions what I do now? My guess is to just try again. I found this, http://www.nabble.com/emerge-xorg-xll--fails-out-at-media-libs-mesa-6.5-r3-… See the post from Donnie Berkholz near the bottom, where he suggests # eselect opengl set xorg-x11 Then try, # emerge -ptv xorg-x11 [ this will show you what's going to be merged ] # emerge xorg-x11 [ ok, try again...] -Jamie > Ken Jones > ========================================== > -------------------snip of emerge failure step 101 out of > 133---------------- > >>> Emerging (101 of 133) media-libs/mesa-6.5.1-r1 to / > >>> Downloading > 'http://distfiles.gentoo.org/distfiles/MesaLib-6.5.1.tar.bz2' > --00:50:32-- http://distfiles.gentoo.org/distfiles/MesaLib-6.5.1.tar.bz2 > => `/usr/portage/distfiles/MesaLib-6.5.1.tar.bz2' > Resolving distfiles.gentoo.org... 156.56.247.195, 216.165.129.135, > 64.50.236.52, ... > Connecting to distfiles.gentoo.org|156.56.247.195|:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 3,138,257 (3.0M) [application/x-tar] > > 100%[===============================================================================>] > 3,138,257 523.02K/s ETA 00:00 > > 00:50:38 (503.34 KB/s) - `/usr/portage/distfiles/MesaLib-6.5.1.tar.bz2' > saved [3138257/3138257] > > * checking ebuild checksums ;-) > ... > [ ok ] > * checking auxfile checksums ;-) > ... > [ ok ] > * checking miscfile checksums ;-) > ... > [ ok ] > * checking MesaLib-6.5.1.tar.bz2 ;-) > ... > [ ok ] > * QA Notice: USE Flag 'amd64-fbsd' not in IUSE for media-libs/mesa-6.5.1-r1 > * QA Notice: USE Flag 'kernel_FreeBSD' not in IUSE for > media-libs/mesa-6.5.1-r1 > >>> Unpacking source... > >>> Unpacking MesaLib-6.5.1.tar.bz2 to > /var/tmp/portage/media-libs/mesa-6.5.1-r1/work > * Applying 6.5.1-freebsd-dri.patch > ... > [ ok ] > * Removing DO_DEBUG defs in dri drivers... > * Sparc assembly code is not working; deactivating > >>> Source unpacked. > >>> Compiling source in > /var/tmp/portage/media-libs/mesa-6.5.1-r1/work/Mesa-6.5.1 ... > (cd configs && rm -f current && ln -s linux-dri current) > . > . <<=============many steps in here=========>> > . > clientattrib.c: In function `__glFreeAttributeState': > clientattrib.c:131: error: dereferencing pointer to incomplete type > clientattrib.c:132: error: dereferencing pointer to incomplete type > make[3]: *** [clientattrib.o] Error 1 > make[3]: Leaving directory > `/var/tmp/portage/media-libs/mesa-6.5.1-r1/work/Mesa-6.5.1/src/glx/x11' > make[2]: *** [subdirs] Error 1 > make[2]: Leaving directory > `/var/tmp/portage/media-libs/mesa-6.5.1-r1/work/Mesa-6.5.1/src' > make[1]: *** [default] Error 1 > make[1]: Leaving directory > `/var/tmp/portage/media-libs/mesa-6.5.1-r1/work/Mesa-6.5.1' > make: *** [linux-dri] Error 2 > > !!! ERROR: media-libs/mesa-6.5.1-r1 failed. > Call stack: > ebuild.sh, line 1615: Called dyn_compile > ebuild.sh, line 972: Called qa_call 'src_compile' > ebuild.sh, line 44: Called src_compile > mesa-6.5.1-r1.ebuild, line 215: Called die > > !!! Build failed > !!! If you need support, post the topmost build error, and the call > stack if relevant. > !!! A complete build log is located at > '/var/tmp/portage/media-libs/mesa-6.5.1-r1/temp/build.log'. > > kjones-sun2 bin # > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

1 0

last sparc64 gentoo question - I promise
by ken jones 24 May '07

24 May '07

I succeeded in doing: #emerge --sync #emerge portage Then I tried #emerge xorg-x11 overnight. I woke up to find this had failed on step 101 out of 133. ------------------- The first two emerge's completed, emerge xorg-x11 did not. Below is stdout. Looking at the log it appears that stddef.h is missing... -----------snip--------- makedepend: warning: clientattrib.c (reading /usr/include/gconv.h, line 31): cannot find include file "stddef.h" ---------snip---------- Right at the end stdout said, "!!! If you need support, post the topmost build error, and the call stack if relevant." I have no idea what this means. Do you? Any suggestions what I do now? My guess is to just try again. Ken Jones ========================================== -------------------snip of emerge failure step 101 out of 133---------------- >>> Emerging (101 of 133) media-libs/mesa-6.5.1-r1 to / >>> Downloading 'http://distfiles.gentoo.org/distfiles/MesaLib-6.5.1.tar.bz2' --00:50:32-- http://distfiles.gentoo.org/distfiles/MesaLib-6.5.1.tar.bz2 => `/usr/portage/distfiles/MesaLib-6.5.1.tar.bz2' Resolving distfiles.gentoo.org... 156.56.247.195, 216.165.129.135, 64.50.236.52, ... Connecting to distfiles.gentoo.org|156.56.247.195|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3,138,257 (3.0M) [application/x-tar] 100%[===============================================================================>] 3,138,257 523.02K/s ETA 00:00 00:50:38 (503.34 KB/s) - `/usr/portage/distfiles/MesaLib-6.5.1.tar.bz2' saved [3138257/3138257] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking MesaLib-6.5.1.tar.bz2 ;-) ... [ ok ] * QA Notice: USE Flag 'amd64-fbsd' not in IUSE for media-libs/mesa-6.5.1-r1 * QA Notice: USE Flag 'kernel_FreeBSD' not in IUSE for media-libs/mesa-6.5.1-r1 >>> Unpacking source... >>> Unpacking MesaLib-6.5.1.tar.bz2 to /var/tmp/portage/media-libs/mesa-6.5.1-r1/work * Applying 6.5.1-freebsd-dri.patch ... [ ok ] * Removing DO_DEBUG defs in dri drivers... * Sparc assembly code is not working; deactivating >>> Source unpacked. >>> Compiling source in /var/tmp/portage/media-libs/mesa-6.5.1-r1/work/Mesa-6.5.1 ... (cd configs && rm -f current && ln -s linux-dri current) . . <<=============many steps in here=========>> . clientattrib.c: In function `__glFreeAttributeState': clientattrib.c:131: error: dereferencing pointer to incomplete type clientattrib.c:132: error: dereferencing pointer to incomplete type make[3]: *** [clientattrib.o] Error 1 make[3]: Leaving directory `/var/tmp/portage/media-libs/mesa-6.5.1-r1/work/Mesa-6.5.1/src/glx/x11' make[2]: *** [subdirs] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-libs/mesa-6.5.1-r1/work/Mesa-6.5.1/src' make[1]: *** [default] Error 1 make[1]: Leaving directory `/var/tmp/portage/media-libs/mesa-6.5.1-r1/work/Mesa-6.5.1' make: *** [linux-dri] Error 2 !!! ERROR: media-libs/mesa-6.5.1-r1 failed. Call stack: ebuild.sh, line 1615: Called dyn_compile ebuild.sh, line 972: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile mesa-6.5.1-r1.ebuild, line 215: Called die !!! Build failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/media-libs/mesa-6.5.1-r1/temp/build.log'. kjones-sun2 bin #

2 1

Re: [Wlug] It boots. Now what?
by Jamie Guinan 23 May '07

23 May '07

On Wed, 23 May 2007, ken jones wrote: > I got HAPPYMEAL to work. My sparc64 is on the WEB! > Here is result of ls -lad /etc/make.profile > ----------snip---------- > kjones-sun2 ~ # ls -lad /etc/make.profile > lrwxrwxrwx 1 root root 58 May 17 12:45 /etc/make.profile -> > ../usr/portage/profiles/default-linux/sparc/sparc64/2006.1 > -----------end snip--------- > Here is result of emerge xorg-x11: How do I install from the tar.bz > file? What is gentoo's equivalent of Red Hat's rpm? That's what gentoo's portage system (via the "emerge" command) does for you - downloads the tarballs, builds, installs, and keeps a record of what's installed under /var/db/pkg/<category>/<package>/ . Well, when it works. :) Look at /usr/portage/media-libs/libpng/*.ebuild, its fairly easy to get the gist of it if you know shell syntax. Did you do "emerge --sync" like some others suggested? I see a few libpng versions available, up to 1.2.16, $ ls /usr/portage/media-libs/libpng/*.ebuild /usr/portage/media-libs/libpng/libpng-1.2.14-r1.ebuild /usr/portage/media-libs/libpng/libpng-1.2.14.ebuild /usr/portage/media-libs/libpng/libpng-1.2.15.ebuild /usr/portage/media-libs/libpng/libpng-1.2.16.ebuild > --------------snip------------- > Lastly, how do you know that HAPPYMEAL is in the sun-hme module? Where > is the information indicating the functionality contained in each module? In the "make menuconfig" [Help] items. Also in menuconfig, you can search all the help text by typing "/" and entering some text. Generally, once you have your system configured to your satisfaction, you keep a copy of the kernel .config, and use that the next time you upgrade the kernel by copying it to the new kernel tree and doing "make oldconfig". -Jamie

1 0

It boots. Now what?
by ken jones 23 May '07

23 May '07

I would like to get X11 services. I did an "emerge xterm". Here's what happened. ------------start snip------------- (chroot) livecd proc # emerge xterm Calculating dependencies | !!! All ebuilds that could satisfy ">=x11-proto/xproto-7.0.6" have been masked. !!! One of the following masked packages is required to complete your request: - x11-proto/xproto-7.0.7 (masked by: ~sparc keyword) - x11-proto/xproto-7.0.10 (masked by: ~sparc keyword) - x11-proto/xproto-7.0.9 (masked by: ~sparc keyword) For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by "x11-libs/libX11-1.1.1-r1" [ebuild]) --------------end snip---------- What do I make of this? Another problem. My livecd prompt and my chroot prompt both see my ethernet card, eth0. However my new boot does not see the card. Ideas? Ken Jones

3 3

I got my sparc64 gentoo on the network
by ken jones 23 May '07

23 May '07

Thank you for suggesting that I compare two dmesg boot message outputs. "grep eth0" on the dmesg outputthat worked referenced HAPPYMEAL. The same 'grep' on the boot log that did not work had no HAPPYMEAL string. I had a 'CONFIG_HAPPYMEAL=m' line in .config. I changed it to 'CONFIG_HAPPYMEAL=y' and recompiled using genkernel. NOW MY NEWLY BOOTED sparc64 IS NETWORKED. The sky's the limit. :-) What I do not understand is how do I know which Module contains which functionality. If I had stuck with the '=m' config I should be able to add a module at boot time. How do I know which module to add? Ken Jones

3 2

gentoo on sparc64 portage question..
by ken jones 23 May '07

23 May '07

Please someone explain to me what is happening here. ---------------snip--------------------- (chroot) livecd dhcpcd # emerge dhcpcd Calculating dependencies... done! >>> Emerging (1 of 1) net-misc/dhcpcd-3.0.16-r1 to / >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking dhcpcd-3.0.16.tar.bz2 !!! Missing digest for 'dhcpcd-3.0.16.tar.bz2' (chroot) livecd dhcpcd # ---------------end snip---------------- Is this a successful emerge? If not, what do I do about the missing digest? Is there an emerge parameter that eliminates the sum check? I looked in 'man emerge' to no avail. emerge is supposed to install things. Instead of installations I get whatever this is. I can not "find" dhcpcd (a binary or a script) anywhere inside my machine. Is another step needed? Ken Jones

3 2

Re: [Wlug] PXE 101 (summer school)
by Adam Keck 22 May '07

22 May '07

<oops... replied off list, reposting> http://www.kernel.org/pub/linux/utils/boot/syslinux/ has the PXE server source that most distros use and http://syslinux.zytor.com/pxe.php talks about how to setup PXE, tftpd, and dhcpd (ISC). -Adam On 5/22/07, Doug Mildram <doug.mildram(a)mindspeed.com> wrote: > > doug> I too use PXE at work, with some success. > I could stand to learn more, and I sure as hell am still > looking for the "pxe daemon source code"...buried by intel?who? > while still running a redhat binary pxe daemon here. > > If every box had a bootable CD, it'd be easier to > just do that ...whether the CD is the stock CD, or one that > you customize a bit, which I've done; which is separate from > customizing the kickstart config file... > but realize as an opening comment, I may recommend that you > ignore PXE until you need it; ignore the boot-from-NIC potential. > > You're VERY welcome to torture me with questions, or visit Westboro > (work/days..it's quiet enough here) for some hands on confusion. > > It may be easier to LEARN PXE after learning "kickstart" without PXE. > e.g. booting from CD with > "linux ks=nfs:nfsserverip:/path/to/yourconfigfile.cfg" > and the .cfg file has MORE info like > ....some intro omitted..... > network ... (static,dhcp...it can install static > while USING a temp-dhcp installaddr) > part .... (disk layout) > authconfig ... ( --enablenis is my option) > nfs --server servername-or-ip --dir /path/releasedir > skipx (no X, dumb terminal consoles best for servers, right?) > %packages... > ...... > % post > exec > /KICKSTART.log 2>&1 > echo "hello..." > mkdir /customdir > mount nfsserver:/exporteddir /customdir > ( grab things, even edit files in / ....) > chkconfig --level 345 ntpd on > chkconfig --level 345 nfs on > ..............and so on. Tends to be a few hundred lines long. > > PXE does all this, but without the CD...and with more flaky results > depending on NIC cards, mostly, i think...I find it > just complicated enough to confuse me, > and just odd enough to NOT work in some cases. > > Challenges: 1) can't find the source to the pxe daemon, > which seems to have fallen OFF of the distros. > I feel "stuck" running a redhat9 binary (which works usually-for-me > on a redhat3-or-4 based system, just copying /usr/sbin/pxe > and firing it up manually (it often crashes after getting its job done) > > 2) complex dependencies. It needs > 2a) DHCP server, can be your existing one > 2b) TFTP server (this part is NOT complex, after you > learn some of the bootfile/dir layout) > as well as the (nfs,ftp,youdecide) server to grab packages from. > > What's confusing is how the PXE daemon and DHCP daemon play together. > When my boot fails, the error whines about DHCP even when PXE is the > problem. > >

1 0

Re: [Wlug] It boots. Now what?
by sageman＠WPI.EDU 22 May '07

22 May '07

> Message: 1 > Date: Tue, 22 May 2007 09:16:18 -0400 > From: ken jones <kjones(a)ziplink.net> > Subject: [Wlug] It boots. Now what? > To: WLUG <wlug(a)mail.wlug.org> > Message-ID: <4652ED22.5090802(a)ziplink.net> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I would like to get X11 services. I did an "emerge xterm". Here's what > happened. > ------------start snip------------- > (chroot) livecd proc # emerge xterm > Calculating dependencies | > !!! All ebuilds that could satisfy ">=x11-proto/xproto-7.0.6" have been > masked. > !!! One of the following masked packages is required to complete your > request: > - x11-proto/xproto-7.0.7 (masked by: ~sparc keyword) > - x11-proto/xproto-7.0.10 (masked by: ~sparc keyword) > - x11-proto/xproto-7.0.9 (masked by: ~sparc keyword) > > For more information, see MASKED PACKAGES section in the emerge man page > or > refer to the Gentoo Handbook. > (dependency required by "x11-libs/libX11-1.1.1-r1" [ebuild]) > --------------end snip---------- > > What do I make of this? > > Another problem. My livecd prompt and my chroot prompt both see my > ethernet card, eth0. However my new boot does not see the card. Ideas? > > Ken Jones Ken, Pulling in xterm, it needs libX11, which, in turn, is pulling in xproto. For the sparc, a masked version of xproto seems to be required. This masking with the "~" is just saying it's in the "testing" set of packages, but it's not hardmasked (it would mention it if it was), meaning it *should* be stable. Regardless, you need the "unstable" version in order to get xterm. There's a number of ways to deal with this, but the suggested way is to add the necessary files, one by one, to /etc/portage/package.unmask. You can do this by adding a line with "x11-proto/xproto ~sparc", or, even better, using the flagedit utility (which you must first "emerge flagedit" to get), and just do: "flagedit x11-proto/xproto +~sparc". [http://damz.net/flagedit/] More info on masking: http://gentoo-wiki.com/Masked

1 0

Re: [Wlug] [Fwd: Re: Multiple RS232 Com Ports...]
by Stephen Daukas 22 May '07

22 May '07

Hi all! Lots of good info... I hadn't stopped to think about a terminal server! OK, lets see about answering some of the questions... - - - - - - Yes, cabling will be fun. The sondes are used for sampling water... The sondes we use are cylinders approximately 2.5 feet in length and about 3 inches in diameter (one, called "big Bertha", is about six inches in diameter) . One end has a data connection that uses a round, screw-on, water tight serial connector, and the business end has several sensors sticking out (optical, chemical, conductivity, a little propeller for mixing water to be sampled, etc., etc.), all within a screw-on cage that protects the sensors from stuff like rocks passing by in the current (fast currents equate to rather large rocks). The idea is to have a tank of water (fish tank, cooler, whatever) fitted with Plexiglas that has multiple holes through which the several sondes are positioned upright, data end pointing up, with a bunch of cables hanging in-place above each sonde - think of the device that sets the bowling pins in place at the end of the alley... Anyway, you place a bunch of sondes into the tank (that has circulating water being maintained at a precise temp, % dissolved Oxygen, and so on), plug each sonde into the cable available directly above it, and then go to the *insert Linux solution here* and initiate communication, data upload, and calibration routines. (By the way, the tank is just about done - its is being debugged as we speak.) After upload and calibration (using the water in the tank), configure each sonde for the next deployment (how often to sample, etc.), turn them off, unscrew the cables and screw on a waterproof cover, remove them from the tank, and place the entire sonde into another protective chamber (6" PVC pipe with holes drilled in a specific pattern and capped on both ends) for another few weeks in some river/lake/coastal location. - - - - - - Yes, I may be confusing myself regarding "I/O device driver" versus "driver" for the sonde... However, I'm pretty sure that all I need is a vanilla "RS232 device driver" that will "just work" for any number of "com" ports by allowing some vanilla terminal emulation package (preferably one that has scripting capabilities) to talk to multiple RS232 ports. I could be wrong about this, in which case I may need to write some code, or perhaps the manufacturer might be thinking of supporting Linux. I don't do the day-to-day instrumentation work, but I am supposed to worry about it none the less. In terms of the "sondes going to sleep", this is based on concerns expressed by the lab along the lines of "if you hook-up the sonde and let it sit too long, you have to start over because it will turn itself off." Also, I use the term "vanilla" a lot because the staff aren't computer types - this has to "just work" like any other tool in the lab. Dear lord - we are talking about biology types after all! ;-) (Unlike engineering/geoscience types!!) - - - - - - So, the other question was about the necessity of having certain signals present. Again, I'm told that the sonde needs all the signals present in a DB-9. I'm guessing this may have more to do with not really knowing for sure and erring on the side of caution, but since there is hardware available that will do this and I can't spend all of my time chasing this down, I'll assume the information I'm getting on this topic is correct. (Biologists not withstanding.) I think this is where the multiport boards or a terminal server would come in... One of the replies mentioned writing a script, and that is what I was thinking about... Specifically, I was wondering if it could be as simple as a script sending the proper bit patterns to get the sonde to do the right things, pipe the serial data through the script and append the data to a file, and s on... (Was that you, John?) - - - - - - - Anyway, I'll have to take a look at the product references mentioned and contemplate what I might need to do in the world of scripting... I haven't heard back from the manufacturer yet, but I'm hoping this will turn out to be a simple project when all is said and done!! Also, I haven't used a terminal server before, so that should be interesting as well. Thanks! If you have any more thoughts, please let me know!! Steve On 5/21/07, Stephen C. Daukas <scd(a)daukas.com> wrote: > > > > -------- Original Message -------- Subject: Re: [Wlug] Multiple RS232 > Com Ports... Date: Mon, 21 May 2007 15:44:09 -0400 From: John Stoffel > <john(a)stoffel.org> <john(a)stoffel.org> Reply-To: Worcester Linux Users > Group <wlug(a)mail.wlug.org> <wlug(a)mail.wlug.org> To: Worcester Linux Users > Group <wlug(a)mail.wlug.org> <wlug(a)mail.wlug.org> References: > <4650752A.1020203(a)daukas.com> <4650752A.1020203(a)daukas.com> > <18001.54171.525952.976484(a)stoffel.org><18001.54171.525952.976484(a)stoffel.org> > <20070521181244.GH4900(a)angus.ind.WPI.EDU><20070521181244.GH4900(a)angus.ind.WPI.EDU> > > Chuck> On Mon, May 21, 2007 at 01:15:07PM -0400, John Stoffel wrote: > >> darn good things about the Cyclades stuff as well. Stay away from the > >> Legacy Avocent (who bought Cyclades...) serial port stuff, it's crap. > > Chuck> Hmm I have to disagree here. We have the Avocent/Cyclades ACS line > Chuck> and are very happy with them. They run Linux inside and support many > Chuck> connection protocols, like Telnet, SSH, Reverse Telnet, Bidirectional, > Chuck> etc. Full RTS/CTS control lines including DTR are available. They > Chuck> support console logging to RAM, PCMCIA flash card, or remote syslog. > > Chuck> Perhaps you are referring to their older Cyclades TS line. > > I'm talking about the old Avocent designed CPS line of crap. You're > talking about the Cyclades designed stuff, including the TS and the > ACS. > > I've got an ancient Cyclom-Y ISA 8-port serial card in my main home > computer and it's been working great for for years. Wish I could > afford the newer stuff. > > John > > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > >

2 1

Re: [Wlug] Setting up PXE/TFTBoot
by Mike Leo 22 May '07

22 May '07

no, but i bet these guys have some doc's for you http://www.ltsp.org/ ----- Original Message ---- From: Tal Cohen <wlug(a)cohen123.com> To: wlug(a)mail.wlug.org Sent: Tuesday, May 22, 2007 9:34:32 AM Subject: [Wlug] Setting up PXE/TFTBoot  I know that this is not new technology….but I am having quite a time figuring this out. I was hoping that you guys could give me a hand. In my office, I want to setup a system that will provide a boot image over the network so that I can remotely setup and configure new servers. I am running Crux2.3. Does anyone have experience setting up remote booting systems? Thanks, Tal _______________________________________________ Wlug mailing list Wlug(a)mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

1 0