what's the passwd? or what is an easy way to reset it On Thursday, June 8, 2017 at 3:56:27 AM UTC-4, Schooner wrote: > > This is a link to a BBB image on which the XHC pendant works, courtesy of > Simon Mali > > > https://www.dropbox.com/s/0z7k0eylr5ppcu6/image_SEM600_HB04_13_May_2017.xz?dl=0 > > A few people have used it sucessfully, including Mike Cinquino, on the > thread you joined. > > > I don't know why the BBB image has such difficulties with the XHC, it > works perfectly on x86 > > tcl is an 80's scripting abomination deserving the garbage bin. > On my own system I have replaced the tcl with Qt5 binaries, but a solution > like that will not be generally > available until Qt5 is the default Debian library version > > I doubt tcl is directly responsible, the xhc-hb04 binary references > libgcc_s.so.1 and I suspect libusb uses it. > > regards > > On 07/06/17 23:13, Konsgn wrote: > > Whelp, > > I've been running into the same problem. (libgcc_s.so.1 must be installed > for pthread_cancel to work) but it exists in the system. I've tried > symlinking it one directory up with no luck. > > I do believe that it is directly related to the pendant, as when I comment > out the xhc or monitor_xhc hal's from the .ini it stops throwing up. > > Interestingly, if I leave in either calls to the .tcl files, the same > error appears. > > Is there a way to debug the .tcl files? > > > On Saturday, May 20, 2017 at 5:13:52 AM UTC-4, Schooner wrote: >> >> >> On 20/05/17 03:10, Mike Cinquino wrote: >> >> Installed libgcc1_4.9.2-10_armhf.deb >> I had to installed gdebi to get it done as the command line methods I >> could not get to work. It said it installed and I had no errors. >> >> Confirmed libgcc_s.so.1 is in both 4.9 and 4.9.2 directory. >> >> Those are just symlinks >> >> >> Confirmed it is also in /lib/arm-linux-gnueabihf >> >> That is the real file, installed at last! >> >> >> $ sudo ldconfig -p | grep libgcc_s.so.1 >> returned : libgcc_s.so.1 (libc6,hard-float) => >> /lib/arm-linux-grueahihf/libgcc_s.so.1 >> >> sudo ldconfig -p >> saw the loads of stuff as you said. >> >> Attempted to launch with same error. Attempted sudo ldconfig multiple >> times. Same error. >> >> >> If you search this error it seems to occur in lots of different >> applications, for no good reason, when the library is installed. >> There has been a problem with python calls closing a file descriptor used >> by dlopen and leaving the library unreachable >> and loads of other similar but unresolved stuff. >> >> Now that you actually have it installed, I come to the end of what I can >> test. >> I don't use a BBB and just downloaded the image and burnt it to a SD card >> so I could see what was in it. >> The pendant and library loading works just fine on a x86_64 platform >> >> The possible fixes that suggest themselves would be tortuously difficult >> to try to explain given your level of >> linux-fu and I cannot test them first. >> >> My best suggestion is get hold of Simon Mali, who has a working XHC-HB04 >> config on a BBB as per this thread >> >> https://groups.google.com/forum/#!topicsearchin/machinekit/xhc-hb04;context-place=forum/machinekit/machinekit/8mMHqZ_Zb80 >> and ask him to clone his SD card image and post it somewhere so you can >> use it. >> >> >> >> >> >> >> >> On Fri, May 19, 2017 at 9:36 AM, schoo...@btinternet.com < >> schoo...@btinternet.com> wrote: >> >>> >>> On 19/05/17 13:56, Mike Cinquino wrote: >>> >>> I agree. And I truly appreciate your patience with me. >>> >>> This is what I have done to this point. Red is what I have pulled from >>> the above string that you have asked me to do. >>> >>> >>> 1- Confirmed- *You need to physically look in >>> /usr/lib/gcc/arm-linux-**gnueabihf/4.9 >>> for **libgcc_s.so.1 *(4.9 has the libgcc_s.so.1 file in it) >>> >>> >>> Does it, or is it a symlink which does not lead anywhere? >>> >>> The file in /usr/lib/gcc/arm-linux-gnueabihf/4.9 is just a symlink >>> >>> The actual file is a /lib/arm-linux-gnueabihf >>> >>> If you are using some dumb file manager which can't tell the difference, >>> that is part of your problem >>> >>> The symlink is installed as part of another gcc package, but its >>> presence does not mean that what it points to is present. >>> >>> >>> 2- Not sure here - *Now that you have installed libgcc1 package and can >>> find the file libgcc_s.so.1, does this file appear in ldconfig cache?* >>> >>> *$ sudo ldconfig -p | grep libgcc_s.so.1* >>> >>> Is the above command supposed to tell me if the file is in ldconfig >>> cache? Because when I run it I get nothing. Just returns to command prompt >>> no errors. >>> I test Machinekit and fail with error as described. >>> >>> >>> If it returns nothing, that is because there is no entry in its cache >>> relating to libgcc_s.so.1 >>> Run *sudo ldconfig -p* >>> and it will return loads of stuff, piping to grep is just a way to sort >>> out what you are looking for >>> >>> So you haven't installed it. >>> >>> You must install libgcc1 and you will have the file >>> https://packages.debian.org/jessie/armhf/libgcc1/filelist >>> >>> It is in libgcc1_4.9.2-10_armhf.deb >>> >>> Until you install the package it will not work. >>> >>> >>> >>> >>> 3- Not sure here either - This command should put the file in the >>> ldconfig cache - If not run $sudo ldconfig *and try again * (I run >>> this command and get nothing in return, no error, just new command prompt?) >>> >>> I test Machinekit and fail with error as described. >>> >>> So after running sudo ldconfig I go back to item 2 and run $ sudo >>> ldconfig -p | grep libgcc_s.so.1 again with same result. >>> >>> I test Machinekit and fail with error as described. >>> >>> ******************************************************************* >>> >>> Now in the directory /usr/lib/gcc/arm-linux-gnueabihf there appear to >>> be multiple versions. 4.9.2, 4.8.4, 4.8 and 4.9. These are all folders >>> in folders are in /usr/lib/gcc/arm-linux-gnueabihf directory. 4.9 and >>> 4.9.2 have libgcc_s.so.1 in them with multiple other files. The other 2 >>> are empty. >>> >>> How do I know what directory (or version) is being looked at or used? >>> You identify 4.9 as being the one to look in. But how do we know it's not >>> one of the others? >>> >>> >>> On Fri, May 19, 2017 at 3:00 AM, schoo...@btinternet.com < >>> schoo...@btinternet.com> wrote: >>> >>>> You have exactly the same error as before >>>> >>>> libgcc_s.so.1 must be installed for pthread_cancel to work >>>> >>>> /usr/bin/linuxcnc: line 753: 5138 Aborted haltcl -i >>>> "$INIFILE" $CFGFILE >>>> >>>> 5069 >>>> >>>> >>>> Until you get to grips with actually installing the lib and testing >>>> that it is present, you will just go around in circles. >>>> >>>> I have detailed what to do, but even when you say you have done it , >>>> you don't elaborate or give any output to show what resulted, so it is >>>> hard >>>> to help you. >>>> >>>> >>>> On 19/05/17 00:59, Mike Cinquino wrote: >>>> >>>> Here is the error list after the last changes. >>>> >>>> On Thu, May 18, 2017 at 4:35 PM, Mike Cinquino <mcin...@gmail.com> >>>> wrote: >>>> >>>>> Is there an older image that is known to work with BBB and the hb04? I >>>>> might be better off going that way if there is? >>>>> >>>>> I have not been in front of the machine much the last couple days. Now >>>>> that I know the difference between L and i ... I got through those >>>>> commands. >>>>> >>>>> Still get an error. I believe it is slightly different. It does not >>>>> say the file is missing it says it needs to be installed. I will send the >>>>> error log once I get back to the machine. >>>>> >>>>> On Wed, May 17, 2017 at 9:23 AM, Mike Cinquino <mcin...@gmail.com> >>>>> wrote: >>>>> >>>>>> Oops ...I think I am using a "i" rather than an "L" Capital I looks >>>>>> like I .... lower case L looks like l...same same. >>>>>> >>>>>> On Wed, May 17, 2017 at 9:17 AM, Mike Cinquino <mcin...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> I think I was looking at before and after I ran the commands. Looks >>>>>>> the same now. >>>>>>> >>>>>>> It tells me Idconfig: command not found >>>>>>> >>>>>>> On Wed, May 17, 2017 at 9:09 AM, schoo...@btinternet.com < >>>>>>> schoo...@btinternet.com> wrote: >>>>>>> >>>>>>>> >>>>>>>> On 17/05/17 13:19, Mike Cinquino wrote: >>>>>>>> >>>>>>>> I ran the commands above. Then...... >>>>>>>> >>>>>>>> I found something that I had not noticed. >>>>>>>> >>>>>>>> I was browsing to the file location usr/lib/gcc... But I was doing >>>>>>>> it under rootfs. >>>>>>>> >>>>>>>>
-- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
