so.
the people at amazon say it will be friday before my new power supply arrives, and i'm still on the X200 that won't connect its wireless. (new developments: neither network-manager nor wicd will recognize the wireless chip, but if i uninstall network-manager the little wifi LED goes out, so it seems to be getting closer. but in that my desktop machine isn't working, i can use the space its keyboard occupied to place the X200 and plug it in via a nice, normal cat5 cable, which is how i can send this note.) you would think that after being hammered by the supreme court last week amazon would be trying extra hard for my business rather than taking a frigging week to get me my power supply. perhaps soon there will be a computer store on every block, like there was 30 years ago. but i digress.)
the gemini project continues apace; the people at planet computing were in my estimation lying when they said it was an android/linux device. it is a medocre googledroid phone with a keyboard that through extensive hacking may me made to prove that linux isn't all that useful on such a device. when it was offered, i and others thought that this meant they had worked out the bugs. they hadn't, they haven't now, and they never will have -- the people working on it are all volunteers, working hard and well for free. i hope that the essential features come to work aceptably well before everybody says the hell with it, but i have little confidence in that outcome.
which brings us to the subject of this note. in the other room, attached to its charger, is a bright new GPD Pocket. it is gorgeous. it looks as if i didn't read the tag and put my macbook into the dryer and it shrank. it is twice the size of the gemini but a hundred times the computer in many respects. it does not have an eight-core SoC like the gemini does (though i think that at least half those cores are to report back to mediatek, google, and Gok who else). but it does have a nice intel x86 chip, and in a bit i shall be backing up the win10 that came on it and installing instead ubuntu 17.10 with the unity desktop. this is because a version of that tuned to the Pocket is available for download, and most everything works right out of the tin.
when i fired it up the thing booted to windows 10 and that screeching harridan "cortana" began issuing demands. (leave it to microsoft -- they can't even spell cortina correctly; a terrible car, but it was also my first car, a 1965 four-speed that i got in 1969, not knowing that cortinas had only about four and one-half years of use in them, and i loved it anyway.) i disabled cortina, misspelled, at the first opportunity.
it's now on the charger, because things are about to get pretty delicate. i have to reflash the bios. the initial one was crippled. (though, come to think of it, i might check first to see if maybe they're shipping the updated version, which would be nice and might be possible: we're not talking planet computers here.)
anyway, it is my (probably vastly inflated) expectation to have linux working on the Pocket by evening's end, after which the next and most important task will be getting the trinity desktop up and running on it. so now, finally, a couple of questions:
actually, one: will it work? the Pocket has a touchscreen but it also has a nice, thinkpad-style trackpoint, so if the touchscreen doesn't work at all it will be at the very most a minor inconvenience -- i'm typing away here on the thinkpad and never does it cross my mind to poke at the screen with my fingers. i've installed TDE on other atom-powered devics uneventfully. anyone know of things to watch out for?
(if i get it all working, next project will be to acquire and attach a cheap 4G dongle, whereupon i will have achieved what i was hoping for with the gemini, only on a robustly-built device big enough to use.)
think it will all work?
dep
Sent withProtonMailSecure Email. Because privacy matters.
On Monday 25 June 2018 13:52:18 dep wrote:
so.
the people at amazon say it will be friday before my new power supply arrives, and i'm still on the X200 that won't connect its wireless. (new developments: neither network-manager nor wicd will recognize the wireless chip, but if i uninstall network-manager the little wifi LED goes out, so it seems to be getting closer. but in that my desktop machine isn't working, i can use the space its keyboard occupied to place the X200 and plug it in via a nice, normal cat5 cable, which is how i can send this note.) you would think that after being hammered by the supreme court last week amazon would be trying extra hard for my business rather than taking a frigging week to get me my power supply. perhaps soon there will be a computer store on every block, like there was 30 years ago. but i digress.)
the gemini project continues apace; the people at planet computing were in my estimation lying when they said it was an android/linux device. it is a medocre googledroid phone with a keyboard that through extensive hacking may me made to prove that linux isn't all that useful on such a device. when it was offered, i and others thought that this meant they had worked out the bugs. they hadn't, they haven't now, and they never will have -- the people working on it are all volunteers, working hard and well for free. i hope that the essential features come to work aceptably well before everybody says the hell with it, but i have little confidence in that outcome.
which brings us to the subject of this note. in the other room, attached to its charger, is a bright new GPD Pocket. it is gorgeous. it looks as if i didn't read the tag and put my macbook into the dryer and it shrank. it is twice the size of the gemini but a hundred times the computer in many respects. it does not have an eight-core SoC like the gemini does (though i think that at least half those cores are to report back to mediatek, google, and Gok who else). but it does have a nice intel x86 chip, and in a bit i shall be backing up the win10 that came on it and installing instead ubuntu 17.10 with the unity desktop. this is because a version of that tuned to the Pocket is available for download, and most everything works right out of the tin.
when i fired it up the thing booted to windows 10 and that screeching harridan "cortana" began issuing demands. (leave it to microsoft -- they can't even spell cortina correctly; a terrible car, but it was also my first car, a 1965 four-speed that i got in 1969, not knowing that cortinas had only about four and one-half years of use in them, and i loved it anyway.) i disabled cortina, misspelled, at the first opportunity.
it's now on the charger, because things are about to get pretty delicate. i have to reflash the bios. the initial one was crippled. (though, come to think of it, i might check first to see if maybe they're shipping the updated version, which would be nice and might be possible: we're not talking planet computers here.)
anyway, it is my (probably vastly inflated) expectation to have linux working on the Pocket by evening's end, after which the next and most important task will be getting the trinity desktop up and running on it. so now, finally, a couple of questions:
actually, one: will it work? the Pocket has a touchscreen but it also has a nice, thinkpad-style trackpoint, so if the touchscreen doesn't work at all it will be at the very most a minor inconvenience -- i'm typing away here on the thinkpad and never does it cross my mind to poke at the screen with my fingers. i've installed TDE on other atom-powered devics uneventfully. anyone know of things to watch out for?
Beware of UEFI/EFI ... don't know if your devices have such new "features", as it was hard for me to keep track of the different devices, the various issues, and their place in your own scheme of things. But if you try to install a Linux system on a newer machine that has UEFI, it will "protect" you from the dangers of Linux and hackers. There are ways to disable UEFI, though.
(if i get it all working, next project will be to acquire and attach a cheap 4G dongle, whereupon i will have achieved what i was hoping for with the gemini, only on a robustly-built device big enough to use.)
think it will all work?
dep
On Tue, Jun 26, 2018 at 12:22 AM, William Morder doctor_contendo@zoho.com wrote:
| Beware of UEFI/EFI ... don't know if your devices have such new "features", as it was hard for me to keep track of the different devices, the | various issues, and their place in your own scheme of things. But if you try to install a Linux system on a newer machine that has UEFI, it | will "protect" you from the dangers of Linux and hackers. There are ways to disable UEFI, though.
not a problem. there is a linux version of the computer and that's not an issue. the bios is unlocked.
dep
Sent with [ProtonMail](https://protonmail.com/) Secure Email. Because privacy matters.
William Morder composed on 2018-06-25 21:22 (UTC-0700):
Beware of UEFI/EFI ... don't know if your devices have such new "features", as it was hard for me to keep track of the different devices, the various issues, and their place in your own scheme of things. But if you try to install a Linux system on a newer machine that has UEFI, it will "protect" you from the dangers of Linux and hackers. There are ways to disable UEFI, though.
Like anything, to use it safely some (re-)education is involved, getting the hang of new paradigms. I have two UEFI PCs. When I started composing this I was doing my 7th (multiboot, adding OS #3 to an M.2 device) installation in UEFI mode, *buntu 18.04, to become Tubuntu, to follow-up on a year-old, still open TDE bug, but it's already finished and rebooted.
On Monday 25 June 2018 21:54:13 Felix Miata wrote:
William Morder composed on 2018-06-25 21:22 (UTC-0700):
Beware of UEFI/EFI ... don't know if your devices have such new "features", as it was hard for me to keep track of the different devices, the various issues, and their place in your own scheme of things. But if you try to install a Linux system on a newer machine that has UEFI, it will "protect" you from the dangers of Linux and hackers. There are ways to disable UEFI, though.
Like anything, to use it safely some (re-)education is involved, getting the hang of new paradigms. I have two UEFI PCs. When I started composing this I was doing my 7th (multiboot, adding OS #3 to an M.2 device) installation in UEFI mode, *buntu 18.04, to become Tubuntu, to follow-up on a year-old, still open TDE bug, but it's already finished and rebooted.
I had a friend who tried to install Trisquel Ubuntu on a new Toshiba laptop, but wasn't familiar with the newer UEFI, and thus turned her machine into a brick. Still no luck unlocking or resuscitating it, last I heard.
Bill
UEFI doesn't block the installation that is secure boot which requires the OS to be signed in order to boot. The reason why not every Linux can install is that the keys cost money and a one man shop that is giving things away for free won't be able to afford it. Most newer version of Linux have a versions that can install on either sometimes as separate downloads and sometimes as a combined image. If you are trying to install a non signed OS you must shut off the secure boot feature. The caveat is if you are looking to do a dual boot is an install done under secure boot will not boot once shut off and will need to be reinstalled. There are a few workarounds but they are a lot of effort vs just reinstalling after making backups.
On Tue, Jun 26, 2018 at 1:20 AM, William Morder doctor_contendo@zoho.com wrote:
On Monday 25 June 2018 21:54:13 Felix Miata wrote:
William Morder composed on 2018-06-25 21:22 (UTC-0700):
Beware of UEFI/EFI ... don't know if your devices have such new "features", as it was hard for me to keep track of the different
devices,
the various issues, and their place in your own scheme of things. But
if
you try to install a Linux system on a newer machine that has UEFI, it will "protect" you from the dangers of Linux and hackers. There are
ways
to disable UEFI, though.
Like anything, to use it safely some (re-)education is involved, getting the hang of new paradigms. I have two UEFI PCs. When I started composing this I was doing my 7th (multiboot, adding OS #3 to an M.2 device) installation in UEFI mode, *buntu 18.04, to become Tubuntu, to follow-up
on
a year-old, still open TDE bug, but it's already finished and rebooted.
I had a friend who tried to install Trisquel Ubuntu on a new Toshiba laptop, but wasn't familiar with the newer UEFI, and thus turned her machine into a brick. Still no luck unlocking or resuscitating it, last I heard.
Bill
To unsubscribe, e-mail: trinity-users-unsubscribe@ lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists. pearsoncomputing.net Read list messages on the web archive: http://trinity-users. pearsoncomputing.net/ Please remember not to top-post: http://trinity. pearsoncomputing.net/mailing_lists/#top-posting
On Tuesday 26 June 2018 01:20:09 William Morder wrote:
On Monday 25 June 2018 21:54:13 Felix Miata wrote:
William Morder composed on 2018-06-25 21:22 (UTC-0700):
Beware of UEFI/EFI ... don't know if your devices have such new "features", as it was hard for me to keep track of the different devices, the various issues, and their place in your own scheme of things. But if you try to install a Linux system on a newer machine that has UEFI, it will "protect" you from the dangers of Linux and hackers. There are ways to disable UEFI, though.
Like anything, to use it safely some (re-)education is involved, getting the hang of new paradigms. I have two UEFI PCs. When I started composing this I was doing my 7th (multiboot, adding OS #3 to an M.2 device) installation in UEFI mode, *buntu 18.04, to become Tubuntu, to follow-up on a year-old, still open TDE bug, but it's already finished and rebooted.
I had a friend who tried to install Trisquel Ubuntu on a new Toshiba laptop, but wasn't familiar with the newer UEFI, and thus turned her machine into a brick. Still no luck unlocking or resuscitating it, last I heard.
Bill
I've done that to one very highly rated raspi killer. No place in the propaganda did it mention it had a UEFI bios. I made one last try by going into the bios and found an option to disable the trusted computing chip. Its a brick I'll have to buy a jtag programmer and cable to fix, at 2x the nominally $100 cost of the board itself. Someday I'll come across it again and it fill make one last high trajectory flight into the trash can. Its one of the higher priced ODROID'S. The rock64 has no such bios, is a u-boot architecture, and with its different architecture can do i/o 500x faster than the pi can thru its usb-2 data pinhole.
But support ranges from media only to non-existent. Changing the installed kernel questions are for a beginner at u-boot like me, either ignored on the forum, or answered by pointing at 6 year old build tools. The rock64 is almost a year from its announcement right now. We need tools to go with todays hardware, and they are not forthconing from the pine people.
That, and I need someone to remove all the "am I running on a real pi3b" tests in the LinuxCNC rpspi.ko driver, then make it work with the gpio headers that come with the rock64.
But this is off-topic. To get back on-topic, changing the mouse focus behavior as directed by several here, was exactly what the doctor needed, speeding up my workflow overall on the milling machine by at least 50%. Thank you to all that responded.
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
On Tuesday 26 June 2018 01:20:09 William Morder wrote:
On Monday 25 June 2018 21:54:13 Felix Miata wrote:
William Morder composed on 2018-06-25 21:22 (UTC-0700):
Beware of UEFI/EFI ... don't know if your devices have such new "features", as it was hard for me to keep track of the different devices, the various issues, and their place in your own scheme of things. But if you try to install a Linux system on a newer machine that has UEFI, it will "protect" you from the dangers of Linux and hackers. There are ways to disable UEFI, though.
Like anything, to use it safely some (re-)education is involved, getting the hang of new paradigms. I have two UEFI PCs. When I started composing this I was doing my 7th (multiboot, adding OS #3 to an M.2 device) installation in UEFI mode, *buntu 18.04, to become Tubuntu, to follow-up on a year-old, still open TDE bug, but it's already finished and rebooted.
I had a friend who tried to install Trisquel Ubuntu on a new Toshiba laptop, but wasn't familiar with the newer UEFI, and thus turned her machine into a brick. Still no luck unlocking or resuscitating it, last I heard.
Bill
I've done that to one very highly rated raspi killer. No place in the propaganda did it mention it had a UEFI bios. I made one last try by going into the bios and found an option to disable the trusted computing chip. Its a brick I'll have to buy a jtag programmer and cable to fix, at 2x the nominally $100 cost of the board itself. Someday I'll come across it again and it fill make one last high trajectory flight into the trash can. Its one of the higher priced ODROID'S. The rock64 has no such bios, is a u-boot architecture, and with its different architecture can do i/o 500x faster than the pi can thru its usb-2 data pinhole.
But support ranges from media only to non-existent. Changing the installed kernel questions are for a beginner at u-boot like me, either ignored on the forum, or answered by pointing at 6 year old build tools. The rock64 is almost a year from its announcement right now. We need tools to go with todays hardware, and they are not forthconing from the pine people.
That, and I need someone to remove all the "am I running on a real pi3b" tests in the LinuxCNC rpspi.ko driver, then make it work with the gpio headers that come with the rock64.
But this is off-topic. To get back on-topic, changing the mouse focus behavior as directed by several here, was exactly what the doctor needed, speeding up my workflow overall on the milling machine by at least 50%. Thank you to all that responded.
When we are at LinuxCNC, could you try out the new syntax highlighting for gcode? It's included in the latest psb builds.
Nik
On Tuesday 26 June 2018 08:51:15 Dr. Nikolaus Klepp wrote:
When we are at LinuxCNC, could you try out the new syntax highlighting for gcode? It's included in the latest psb builds.
Nik
For what editor? Where should I see it IOW. Certainly not gedit as it has an incurable tendency to move arbitrary blocks of code around in the file so its been nuked from all of my systems. gedit is a very capable editor, capable of wrecking 2 years work. I've sorted that pan of scrambled eggs, 1000 LOC, several times too many, even resorting to getting last nights backup out to recover.
I now use nano or geany if a gui is available, which so far has Just Worked(TM). It does do some C style code checking, matching brackets etc type stuff, but I've found highlighting words only usefull by the spell checkers.
As for LCNC, I wish the highliteing of the line being processed in it lower code display wasn't greyed out as it is now, but displayed in bold text. Trying to read the greyed out text is getting difficult with my cataracts thrown in.
perhaps you could do something about that?
And we are off-topic, again.
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
On Tuesday 26 June 2018 08:51:15 Dr. Nikolaus Klepp wrote:
When we are at LinuxCNC, could you try out the new syntax highlighting for gcode? It's included in the latest psb builds.
Nik
For what editor? Where should I see it IOW. Certainly not gedit as it has an incurable tendency to move arbitrary blocks of code around in the file so its been nuked from all of my systems. gedit is a very capable editor, capable of wrecking 2 years work. I've sorted that pan of scrambled eggs, 1000 LOC, several times too many, even resorting to getting last nights backup out to recover.
It's for "kate" and "kwrite" :-)
I now use nano or geany if a gui is available, which so far has Just Worked(TM). It does do some C style code checking, matching brackets etc type stuff, but I've found highlighting words only usefull by the spell checkers.
geany was what I used ill I found FernVs gcode.xml for kate. I think the highlighting for kate works way better than in geany. The only bug I found is indirect o-calls are marked as syntax error (e.g.: o[#1] is displayed red underlined).
As for LCNC, I wish the highliteing of the line being processed in it lower code display wasn't greyed out as it is now, but displayed in bold text. Trying to read the greyed out text is getting difficult with my cataracts thrown in.
perhaps you could do something about that?
I think that would be possible, but axis is written python and my python knowledge is still in a book on the shelf ..
And we are off-topic, again.
:-)
Nik
well. have ubuntu 17.10 running nicely on the gpd pocket. everything seems to work. after i complete some photo assignments this afternoon and take a nap, i'll do phase 2, installation of trinity on the thing. it is currently running the unity desktop.
this could actually become a useful device. and unlike the thinkpad, its wifi works!
meanwhile, for sailfish fans, the planet computers people announced sailfish for the gemini:
https://www.indiegogo.com/projects/gemini-pda-android-linux-keyboard-mobile-...
(i know that there are some sailfish fans here.)
dep
Sent withProtonMailSecure Email. Because privacy matters.
On Tuesday 26 June 2018 09:47:09 Dr. Nikolaus Klepp wrote:
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
On Tuesday 26 June 2018 08:51:15 Dr. Nikolaus Klepp wrote:
When we are at LinuxCNC, could you try out the new syntax highlighting for gcode? It's included in the latest psb builds.
Nik
For what editor? Where should I see it IOW. Certainly not gedit as it has an incurable tendency to move arbitrary blocks of code around in the file so its been nuked from all of my systems. gedit is a very capable editor, capable of wrecking 2 years work. I've sorted that pan of scrambled eggs, 1000 LOC, several times too many, even resorting to getting last nights backup out to recover.
It's for "kate" and "kwrite" :-)
oh
I now use nano or geany if a gui is available, which so far has Just Worked(TM). It does do some C style code checking, matching brackets etc type stuff, but I've found highlighting words only usefull by the spell checkers.
geany was what I used ill I found FernVs gcode.xml for kate. I think the highlighting for kate works way better than in geany. The only bug I found is indirect o-calls are marked as syntax error (e.g.: o[#1] is displayed red underlined).
I'll have to see if thats available. kate and kwrite were not installed on that machine, but 47 files are being updated as I type, and a reboot will be needed before I can test this. And after installing them both, I can't find it (g-code.xml).
As for LCNC, I wish the highliteing of the line being processed in it lower code display wasn't greyed out as it is now, but displayed in bold text. Trying to read the greyed out text is getting difficult with my cataracts thrown in.
perhaps you could do something about that?
I think that would be possible, but axis is written python and my python knowledge is still in a book on the shelf ..
99% of mine is too, but I've not bought the book yet. :(
And we are off-topic, again.
:-)
Nik
On Tuesday 26 June 2018 07:26:30 Gene Heskett wrote:
On Tuesday 26 June 2018 09:47:09 Dr. Nikolaus Klepp wrote:
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
On Tuesday 26 June 2018 08:51:15 Dr. Nikolaus Klepp wrote:
When we are at LinuxCNC, could you try out the new syntax highlighting for gcode? It's included in the latest psb builds.
Nik
For what editor? Where should I see it IOW. Certainly not gedit as it has an incurable tendency to move arbitrary blocks of code around in the file so its been nuked from all of my systems. gedit is a very capable editor, capable of wrecking 2 years work. I've sorted that pan of scrambled eggs, 1000 LOC, several times too many, even resorting to getting last nights backup out to recover.
It's for "kate" and "kwrite" :-)
oh
I now use nano or geany if a gui is available, which so far has Just Worked(TM). It does do some C style code checking, matching brackets etc type stuff, but I've found highlighting words only usefull by the spell checkers.
geany was what I used ill I found FernVs gcode.xml for kate. I think the highlighting for kate works way better than in geany. The only bug I found is indirect o-calls are marked as syntax error (e.g.: o[#1] is displayed red underlined).
I'll have to see if thats available. kate and kwrite were not installed on that machine, but 47 files are being updated as I type, and a reboot will be needed before I can test this. And after installing them both, I can't find it (g-code.xml).
As for LCNC, I wish the highliteing of the line being processed in it lower code display wasn't greyed out as it is now, but displayed in bold text. Trying to read the greyed out text is getting difficult with my cataracts thrown in.
perhaps you could do something about that?
I think that would be possible, but axis is written python and my python knowledge is still in a book on the shelf ..
99% of mine is too, but I've not bought the book yet. :(
Don't bother spending your money. Just download it from somewhere or other.
And we are off-topic, again.
Bad cat! Bad cat!
:-)
Nik
Bill
(@)
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
[...] I'll have to see if thats available. kate and kwrite were not installed on that machine, but 47 files are being updated as I type, and a reboot will be needed before I can test this. And after installing them both, I can't find it (g-code.xml).
It's here(4:14.0.5~pre): tdelibs-data-trinity: /opt/trinity/share/apps/katepart/syntax/gcode.xml
As for LCNC, I wish the highliteing of the line being processed in it lower code display wasn't greyed out as it is now, but displayed in bold text. Trying to read the greyed out text is getting difficult with my cataracts thrown in.
perhaps you could do something about that?
I think that would be possible, but axis is written python and my python knowledge is still in a book on the shelf ..
99% of mine is too, but I've not bought the book yet. :(
And we are off-topic, again.
:-)
Nik
On Tuesday 26 June 2018 14:31:17 Dr. Nikolaus Klepp wrote:
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
[...] I'll have to see if thats available. kate and kwrite were not installed on that machine, but 47 files are being updated as I type, and a reboot will be needed before I can test this. And after installing them both, I can't find it (g-code.xml).
It's here(4:14.0.5~pre): tdelibs-data-trinity: /opt/trinity/share/apps/katepart/syntax/gcode.xml.
So it is, but neither kate nor kwrite can find it in its menu's. Is there another magic twanger to make it work? I can't find froggy either. :)
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
On Tuesday 26 June 2018 14:31:17 Dr. Nikolaus Klepp wrote:
Am Dienstag, 26. Juni 2018 schrieb Gene Heskett:
[...] I'll have to see if thats available. kate and kwrite were not installed on that machine, but 47 files are being updated as I type, and a reboot will be needed before I can test this. And after installing them both, I can't find it (g-code.xml).
It's here(4:14.0.5~pre): tdelibs-data-trinity: /opt/trinity/share/apps/katepart/syntax/gcode.xml.
So it is, but neither kate nor kwrite can find it in its menu's. Is there another magic twanger to make it work? I can't find froggy either. :)
Hm ... open a gcode-file (*.ngc) using kate, then menu/extra/highlighting/other/g-code - maybe the screenshot helps where to look.
Nik