PINE64 - User contributions [en]

User:Valenoern/Pine64 Screws

2023-04-09T00:35:51Z

Valenoern: Nylon screw picture

The screws section on the ROCKPRo64 page was about to get unexpectedly long, so I have decided to create another page to contain only notes on screws.

== ROCKPro64 ==

=== Correct measurements ===

Unknown. M2.5 was too narrow

=== Nylon screws ===

[[File:ROCKPro64 with nylon screw.jpg|thumb|frame|Nylon screw compared with original metal screw]]

I recently found out there are plastic screws available in a clear white colour, so I immediately had to see how these would look on the ROCKPro64.

I was not able to find screws which would be both the right length and the right thread diameter, at least so far. The ones I tried which were closest to the measurements I'd taken were not wide enough and simply fell through the hole.

However, given the right diameter I might actually recommend these.

File:ROCKPro64 with nylon screw.jpg

2023-04-09T00:31:13Z

Valenoern: Original screw compared with plastic (nylon) screw, on ROCKPro64 NAS case

== Summary ==
Original screw compared with plastic (nylon) screw, on ROCKPro64 NAS case
== Licensing ==
{{cc-by-sa-4.0}}

User:Valenoern/Pine64 Lisp Machine

2023-04-08T23:26:02Z

Valenoern: /* ROCKPro screws */

I (Valenoern) have been working on a project to build my own "ideal" Pine64 box as part of producing my own linux distributions. 
Here I will explain the various pieces of my project and what stage of completion they are at.

== ROCKPRo64 setup ==

=== Bluetooth ===

I did not have much luck with the ROCKPro64 wifi/bluetooth module for unclear reasons. (I may not have attached it correctly?) I have a memory of the signal being weak or unreliable but it may simply not have worked at all.

As a result I have always just used an external bluetooth adapter and a wired network. This has not been much of a problem since, for instance, one USB slot I could use for a mouse can instead be used for a bluetooth mouse.

=== ROCKPro screws ===

The screws that shipped with the ROCKPro NAS case were very easy to accidentally break by grinding the drive, although I found they still remain usable if you push on the screwdriver and effectively carve it back out again. There is also not a dedicated item to buy new ones in the shop. 
Due to these frustrations, I will give you a small guide to replacing screws.

ROCKPro screws are classified as:
* machine screw (cylinder shaped)
* flat / countersunk head
* Philips drive
* 5 mm head diameter (1/5 inch)
* 5 mm long (1/5 inch, includes countersunk head)
* 2.5 mm ±1 mm thread diameter (~1/10 inch)
* thread pitch: 0.5 mm (50.8 threads per inch)
* ISO name: M2.5(?) × 0.5 × 5

I have been trying to verify these measurements but have not yet found screws with the right thread diameter; see [[User:Valenoern/Pine64 Screws]] for more details.

== G-refracta ==

G-refracta is a basic distribution intended to replicate refracta as closely as possible on an Arch base. 
It takes its name from [[Wikipedia:Grevillea_refracta|''Grevillea refracta'']], a kind of plant.

== v-refracta ==

v-refracta is a more advanced distribution intended as a transitional step between traditional GNU/Linux distributions and a Lisp Machine. 
(Note: the "v" has nothing to do with the name Valenoern or any associated name. It simply comes from the distribution's programs.)

Planned features:
* a POSIX-like command line shell called vxsh ([fsxɐˈdʲiʂ] / [vɛˈxaʂ]), which is really a Lisp REPL but doubles as a Linux shell capable of running Lisp in a simple bash-like syntax
* a "universal" software manager called VRaptor, which would allow managing Arch packages, quicklisp packages, git repos, and other kinds of packages from one interface, with backwards compatibility for those who are used to debian and apt. (Hence the name VR'''apt'''or.)

v-refracta may end up overlapping with the [https://github.com/froggey/Mezzano mezzano] project since they will both need common elements such as a graphical Lisp desktop.

== bopwiki ==

bop (or ''bopwiki'' in longhand) is something of the centrepiece of v-refracta. It is a new kind of note-taking program based on the idea that [[wikipedia:Zettelkasten|card boxes]] are the computer documents of the future and all computer documents and applications should be as intuitive and seamlessly integratable with each other as "computations" on a physical page of paper.

I was first inspired to create bopwiki by the notion of combining microblog posts and wiki pages. Microblog posts are simple text-based journal entries which are easy to type and self-contained, and are connected to a particular post date and a logically-arranged history of events. Wiki pages are powerful text-based documents capable of connecting knowledge together and preserving the most important pieces for the future while maintaining a "chain of custody" for information sources and also providing an edit history. By putting these two things together, it would be possible to create a sophisticated system for gathering knowledge, organising knowledge from a chronology of recent events into a more structured form, keeping a history of how the collection of notes itself changed, and keeping track of prior sources of knowledge which were relevant to recording or organising notes. In a sense, bop is meant to be the perfect companion for things like thesis research or writing a reference book or fictional story. It is almost like a kind of "trackable source code for books", allowing you to back up and version-control the entire book creation process much the same way you would manage a folder of in-progress source code and TODO files.

== zensekai ==

zensekai is a project to create a modular and extensible "kaiju game" engine, which will run on both desktop and mobile Free Software operating systems.

Please see [https://wiki.openstreetmap.org/wiki/User:Valenoern User:Valenoern] on the OpenStreetMap wiki for a bit more on zensekai and the AR zensekai Sphere.

== References ==

* [https://forum.pine64.org/showthread.php?tid=16813 Assembling desktop setup for newbies? - Pine64 forums]
* [https://www.boltdepot.com/fastener-information/identifying-fasteners.aspx How Fasteners are Identified]
* [https://www.boltdepot.com/fastener-information/Type-Chart.aspx Fastener Type Chart]
* [https://www.boltdepot.com/fastener-information/Machine-Screws/Machine-Screw-Diameter.aspx Machine screw diameter]
* [https://archive.org/details/221210_vconn Pinephone USB host fix (failed)] - documentation I used for explaining [[PinePhone 1.2 VCONN Hardware Fix]]
* [https://archive.org/details/220108_refract G-refracta archive] - old iso images etc
* [https://codeberg.org/bopwiki-pkgbuild Grevillea-refracta packages] - programs for use on G-refracta / v-refracta
* [https://codeberg.org/vxsh-suite/vxsh vxsh repository] - as it says, just a simple demo right now

User:Valenoern/Pine64 Screws

2023-04-08T23:13:15Z

Valenoern: typo

The screws section on the ROCKPRo64 page was about to get unexpectedly long, so I have decided to create another page to contain only notes on screws.

== ROCKPro64 ==

=== Correct measurements ===

Unknown

=== Nylon screws ===

I recently found out there are plastic screws available in a clear white colour, so I immediately had to see how these would look on the ROCKPro64.

I was not able to find screws which would be both the right length and the right thread diameter, at least so far. The ones I tried which were closest to the measurements I'd taken were not wide enough and simply fell through the hole.

However, given the right diameter I might actually recommend these.

User:Valenoern/Pine64 Screws

2023-04-08T23:12:15Z

Valenoern: Valenoern moved page User:Valenoern/User:Valenoern/Pine64 Screws to User:Valenoern/Pine64 Screws: Accidentally duplicated "user:valenoern" prefix

The screws section on the RockPRO64 page was about to get unexpectedly long, so I have decided to create another page to contain only notes on screws.

== ROCKPro64 ==

=== Correct measurements ===

Unknown

=== Nylon screws ===

I recently found out there are plastic screws available in a clear white colour, so I immediately had to see how these would look on the ROCKPro64.

I was not able to find screws which would be both the right length and the right thread diameter, at least so far. The ones I tried which were closest to the measurements I'd taken were not wide enough and simply fell through the hole.

However, given the right diameter I might actually recommend these.

User:Valenoern/Pine64 Screws

2023-04-08T23:10:17Z

Valenoern: Create page / nylon screw notes

User:Valenoern/Pine64 Lisp Machine

2023-04-07T11:33:16Z

Valenoern: Bluetooth adapter

I (Valenoern) have been working on a project to build my own "ideal" Pine64 box as part of producing my own linux distributions. 
Here I will explain the various pieces of my project and what stage of completion they are at.

== ROCKPRo64 setup ==

=== Bluetooth ===

I did not have much luck with the ROCKPro64 wifi/bluetooth module for unclear reasons. (I may not have attached it correctly?) I have a memory of the signal being weak or unreliable but it may simply not have worked at all.

As a result I have always just used an external bluetooth adapter and a wired network. This has not been much of a problem since, for instance, one USB slot I could use for a mouse can instead be used for a bluetooth mouse.

=== ROCKPro screws ===

The screws that shipped with the ROCKPro NAS case were very easy to accidentally break by grinding the threads, although I found they still remain usable if you push on the screwdriver and effectively carve them back out again. There is also not a dedicated item to buy new ones in the shop. 
Due to these frustrations, I will give you a small guide to replacing screws.

ROCKPro screws are classified as:
* machine screw (cylinder shaped)
* flat / countersunk head
* Philips drive
* 5 mm head diameter (1/5 inch)
* 5 mm long (1/5 inch, includes countersunk head)
* 2.5 mm ±1 mm thread diameter (~1/10 inch)
* thread pitch: 0.5 mm (50.8 threads per inch)
* ISO name: M2.5 × 0.5 × 5

I am currently trying to verify these measurements with new screws, and will report back later.

== G-refracta ==

G-refracta is a basic distribution intended to replicate refracta as closely as possible on an Arch base. 
It takes its name from [[Wikipedia:Grevillea_refracta|''Grevillea refracta'']], a kind of plant.

== v-refracta ==

v-refracta is a more advanced distribution intended as a transitional step between traditional GNU/Linux distributions and a Lisp Machine. 
(Note: the "v" has nothing to do with the name Valenoern or any associated name. It simply comes from the distribution's programs.)

Planned features:
* a POSIX-like command line shell called vxsh ([fsxɐˈdʲiʂ] / [vɛˈxaʂ]), which is really a Lisp REPL but doubles as a Linux shell capable of running Lisp in a simple bash-like syntax
* a "universal" software manager called VRaptor, which would allow managing Arch packages, quicklisp packages, git repos, and other kinds of packages from one interface, with backwards compatibility for those who are used to debian and apt. (Hence the name VR'''apt'''or.)

v-refracta may end up overlapping with the [https://github.com/froggey/Mezzano mezzano] project since they will both need common elements such as a graphical Lisp desktop.

== bopwiki ==

bop (or ''bopwiki'' in longhand) is something of the centrepiece of v-refracta. It is a new kind of note-taking program based on the idea that [[wikipedia:Zettelkasten|card boxes]] are the computer documents of the future and all computer documents and applications should be as intuitive and seamlessly integratable with each other as "computations" on a physical page of paper.

I was first inspired to create bopwiki by the notion of combining microblog posts and wiki pages. Microblog posts are simple text-based journal entries which are easy to type and self-contained, and are connected to a particular post date and a logically-arranged history of events. Wiki pages are powerful text-based documents capable of connecting knowledge together and preserving the most important pieces for the future while maintaining a "chain of custody" for information sources and also providing an edit history. By putting these two things together, it would be possible to create a sophisticated system for gathering knowledge, organising knowledge from a chronology of recent events into a more structured form, keeping a history of how the collection of notes itself changed, and keeping track of prior sources of knowledge which were relevant to recording or organising notes. In a sense, bop is meant to be the perfect companion for things like thesis research or writing a reference book or fictional story. It is almost like a kind of "trackable source code for books", allowing you to back up and version-control the entire book creation process much the same way you would manage a folder of in-progress source code and TODO files.

== zensekai ==

zensekai is a project to create a modular and extensible "kaiju game" engine, which will run on both desktop and mobile Free Software operating systems.

Please see [https://wiki.openstreetmap.org/wiki/User:Valenoern User:Valenoern] on the OpenStreetMap wiki for a bit more on zensekai and the AR zensekai Sphere.

== References ==

* [https://forum.pine64.org/showthread.php?tid=16813 Assembling desktop setup for newbies? - Pine64 forums]
* [https://www.boltdepot.com/fastener-information/identifying-fasteners.aspx How Fasteners are Identified]
* [https://www.boltdepot.com/fastener-information/Type-Chart.aspx Fastener Type Chart]
* [https://www.boltdepot.com/fastener-information/Machine-Screws/Machine-Screw-Diameter.aspx Machine screw diameter]
* [https://archive.org/details/221210_vconn Pinephone USB host fix (failed)] - documentation I used for explaining [[PinePhone 1.2 VCONN Hardware Fix]]
* [https://archive.org/details/220108_refract G-refracta archive] - old iso images etc
* [https://codeberg.org/bopwiki-pkgbuild Grevillea-refracta packages] - programs for use on G-refracta / v-refracta
* [https://codeberg.org/vxsh-suite/vxsh vxsh repository] - as it says, just a simple demo right now

User:Valenoern/Pine64 Lisp Machine

2023-04-07T11:22:23Z

Valenoern: G-refracta name origin

I (Valenoern) have been working on a project to build my own "ideal" Pine64 box as part of producing my own linux distributions. 
Here I will explain the various pieces of my project and what stage of completion they are at.

== ROCKPRo64 setup ==

=== ROCKPro screws ===

The screws that shipped with the ROCKPro NAS case were very easy to accidentally break by grinding the threads, although I found they still remain usable if you push on the screwdriver and effectively carve them back out again. There is also not a dedicated item to buy new ones in the shop. 
Due to these frustrations, I will give you a small guide to replacing screws.

ROCKPro screws are classified as:
* machine screw (cylinder shaped)
* flat / countersunk head
* Philips drive
* 5 mm head diameter (1/5 inch)
* 5 mm long (1/5 inch, includes countersunk head)
* 2.5 mm ±1 mm thread diameter (~1/10 inch)
* thread pitch: 0.5 mm (50.8 threads per inch)
* ISO name: M2.5 × 0.5 × 5

I am currently trying to verify these measurements with new screws, and will report back later.

== G-refracta ==

G-refracta is a basic distribution intended to replicate refracta as closely as possible on an Arch base. 
It takes its name from [[Wikipedia:Grevillea_refracta|''Grevillea refracta'']], a kind of plant.

== v-refracta ==

v-refracta is a more advanced distribution intended as a transitional step between traditional GNU/Linux distributions and a Lisp Machine. 
(Note: the "v" has nothing to do with the name Valenoern or any associated name. It simply comes from the distribution's programs.)

Planned features:
* a POSIX-like command line shell called vxsh ([fsxɐˈdʲiʂ] / [vɛˈxaʂ]), which is really a Lisp REPL but doubles as a Linux shell capable of running Lisp in a simple bash-like syntax
* a "universal" software manager called VRaptor, which would allow managing Arch packages, quicklisp packages, git repos, and other kinds of packages from one interface, with backwards compatibility for those who are used to debian and apt. (Hence the name VR'''apt'''or.)

v-refracta may end up overlapping with the [https://github.com/froggey/Mezzano mezzano] project since they will both need common elements such as a graphical Lisp desktop.

== bopwiki ==

bop (or ''bopwiki'' in longhand) is something of the centrepiece of v-refracta. It is a new kind of note-taking program based on the idea that [[wikipedia:Zettelkasten|card boxes]] are the computer documents of the future and all computer documents and applications should be as intuitive and seamlessly integratable with each other as "computations" on a physical page of paper.

I was first inspired to create bopwiki by the notion of combining microblog posts and wiki pages. Microblog posts are simple text-based journal entries which are easy to type and self-contained, and are connected to a particular post date and a logically-arranged history of events. Wiki pages are powerful text-based documents capable of connecting knowledge together and preserving the most important pieces for the future while maintaining a "chain of custody" for information sources and also providing an edit history. By putting these two things together, it would be possible to create a sophisticated system for gathering knowledge, organising knowledge from a chronology of recent events into a more structured form, keeping a history of how the collection of notes itself changed, and keeping track of prior sources of knowledge which were relevant to recording or organising notes. In a sense, bop is meant to be the perfect companion for things like thesis research or writing a reference book or fictional story. It is almost like a kind of "trackable source code for books", allowing you to back up and version-control the entire book creation process much the same way you would manage a folder of in-progress source code and TODO files.

== zensekai ==

zensekai is a project to create a modular and extensible "kaiju game" engine, which will run on both desktop and mobile Free Software operating systems.

Please see [https://wiki.openstreetmap.org/wiki/User:Valenoern User:Valenoern] on the OpenStreetMap wiki for a bit more on zensekai and the AR zensekai Sphere.

== References ==

* [https://forum.pine64.org/showthread.php?tid=16813 Assembling desktop setup for newbies? - Pine64 forums]
* [https://www.boltdepot.com/fastener-information/identifying-fasteners.aspx How Fasteners are Identified]
* [https://www.boltdepot.com/fastener-information/Type-Chart.aspx Fastener Type Chart]
* [https://www.boltdepot.com/fastener-information/Machine-Screws/Machine-Screw-Diameter.aspx Machine screw diameter]
* [https://archive.org/details/221210_vconn Pinephone USB host fix (failed)] - documentation I used for explaining [[PinePhone 1.2 VCONN Hardware Fix]]
* [https://archive.org/details/220108_refract G-refracta archive] - old iso images etc
* [https://codeberg.org/bopwiki-pkgbuild Grevillea-refracta packages] - programs for use on G-refracta / v-refracta
* [https://codeberg.org/vxsh-suite/vxsh vxsh repository] - as it says, just a simple demo right now

User:Valenoern/Pine64 Lisp Machine

2023-03-24T08:30:25Z

Valenoern: ROCKPro screws

I (Valenoern) have been working on a project to build my own "ideal" Pine64 box as part of producing my own linux distributions. 
Here I will explain the various pieces of my project and what stage of completion they are at.

== ROCKPRo64 setup ==

=== ROCKPro screws ===

The screws that shipped with the ROCKPro NAS case were very easy to accidentally break by grinding the threads, although I found they still remain usable if you push on the screwdriver and effectively carve them back out again. There is also not a dedicated item to buy new ones in the shop. 
Due to these frustrations, I will give you a small guide to replacing screws.

ROCKPro screws are classified as:
* machine screw (cylinder shaped)
* flat / countersunk head
* Philips drive
* 5 mm head diameter (1/5 inch)
* 5 mm long (1/5 inch, includes countersunk head)
* 2.5 mm ±1 mm thread diameter (~1/10 inch)
* thread pitch: 0.5 mm (50.8 threads per inch)
* ISO name: M2.5 × 0.5 × 5

I am currently trying to verify these measurements with new screws, and will report back later.

== G-refracta ==

G-refracta is a basic distribution intended to replicate refracta as closely as possible on an Arch base. 
It takes its name from ''Grevillea refracta'', a kind of plant.

== v-refracta ==

v-refracta is a more advanced distribution intended as a transitional step between traditional GNU/Linux distributions and a Lisp Machine. 
(Note: the "v" has nothing to do with the name Valenoern or any associated name. It simply comes from the distribution's programs.)

Planned features:
* a POSIX-like command line shell called vxsh ([fsxɐˈdʲiʂ] / [vɛˈxaʂ]), which is really a Lisp REPL but doubles as a Linux shell capable of running Lisp in a simple bash-like syntax
* a "universal" software manager called VRaptor, which would allow managing Arch packages, quicklisp packages, git repos, and other kinds of packages from one interface, with backwards compatibility for those who are used to debian and apt. (Hence the name VR'''apt'''or.)

v-refracta may end up overlapping with the [https://github.com/froggey/Mezzano mezzano] project since they will both need common elements such as a graphical Lisp desktop.

== bopwiki ==

bop (or ''bopwiki'' in longhand) is something of the centrepiece of v-refracta. It is a new kind of note-taking program based on the idea that [[wikipedia:Zettelkasten|card boxes]] are the computer documents of the future and all computer documents and applications should be as intuitive and seamlessly integratable with each other as "computations" on a physical page of paper.

I was first inspired to create bopwiki by the notion of combining microblog posts and wiki pages. Microblog posts are simple text-based journal entries which are easy to type and self-contained, and are connected to a particular post date and a logically-arranged history of events. Wiki pages are powerful text-based documents capable of connecting knowledge together and preserving the most important pieces for the future while maintaining a "chain of custody" for information sources and also providing an edit history. By putting these two things together, it would be possible to create a sophisticated system for gathering knowledge, organising knowledge from a chronology of recent events into a more structured form, keeping a history of how the collection of notes itself changed, and keeping track of prior sources of knowledge which were relevant to recording or organising notes. In a sense, bop is meant to be the perfect companion for things like thesis research or writing a reference book or fictional story. It is almost like a kind of "trackable source code for books", allowing you to back up and version-control the entire book creation process much the same way you would manage a folder of in-progress source code and TODO files.

== zensekai ==

zensekai is a project to create a modular and extensible "kaiju game" engine, which will run on both desktop and mobile Free Software operating systems.

Please see [https://wiki.openstreetmap.org/wiki/User:Valenoern User:Valenoern] on the OpenStreetMap wiki for a bit more on zensekai and the AR zensekai Sphere.

== References ==

* [https://forum.pine64.org/showthread.php?tid=16813 Assembling desktop setup for newbies? - Pine64 forums]
* [https://www.boltdepot.com/fastener-information/identifying-fasteners.aspx How Fasteners are Identified]
* [https://www.boltdepot.com/fastener-information/Type-Chart.aspx Fastener Type Chart]
* [https://www.boltdepot.com/fastener-information/Machine-Screws/Machine-Screw-Diameter.aspx Machine screw diameter]
* [https://archive.org/details/221210_vconn Pinephone USB host fix (failed)] - documentation I used for explaining [[PinePhone 1.2 VCONN Hardware Fix]]
* [https://archive.org/details/220108_refract G-refracta archive] - old iso images etc
* [https://codeberg.org/bopwiki-pkgbuild Grevillea-refracta packages] - programs for use on G-refracta / v-refracta
* [https://codeberg.org/vxsh-suite/vxsh vxsh repository] - as it says, just a simple demo right now

User:Valenoern/Pine64 Lisp Machine

2023-03-24T02:53:06Z

Valenoern: ROCKPro screws

I (Valenoern) have been working on a project to build my own "ideal" Pine64 box as part of producing my own linux distributions. 
Here I will explain the various pieces of my project and what stage of completion they are at.

== ROCKPRo64 setup ==

=== ROCKPro screws ===

The screws that shipped with the ROCKPro NAS case were very easy to accidentally break by grinding the threads, although I found they still remain usable if you push on the screwdriver and effectively carve them back out again. There is not a dedicated item to simply buy new ones in the shop either. 
Due to these frustrations, I will give you a small guide to replacing screws.

ROCKPro screws are classified as:
* machine screw (cylinder shaped)
* flat head
* Philips drive
* (will add measurements shortly)

== G-refracta ==

G-refracta is a basic distribution intended to replicate refracta as closely as possible on an Arch base. 
It takes its name from ''Grevillea refracta'', a kind of plant.

== v-refracta ==

v-refracta is a more advanced distribution intended as a transitional step between traditional GNU/Linux distributions and a Lisp Machine. 
(Note: the "v" has nothing to do with the name Valenoern or any associated name. It simply comes from the distribution's programs.)

Planned features:
* a POSIX-like command line shell called vxsh ([fsxɐˈdʲiʂ] / [vɛˈxaʂ]), which is really a Lisp REPL but doubles as a Linux shell capable of running Lisp in a simple bash-like syntax
* a "universal" software manager called VRaptor, which would allow managing Arch packages, quicklisp packages, git repos, and other kinds of packages from one interface, with backwards compatibility for those who are used to debian and apt. (Hence the name VR'''apt'''or.)

== bopwiki ==

bop (or ''bopwiki'' in longhand) is something of the centrepiece of v-refracta. It is a new kind of note-taking program based on the idea that [[wikipedia:Zettelkasten|card boxes]] are the computer documents of the future and all computer documents and applications should be as intuitive and seamlessly integratable with each other as "computations" on a physical page of paper.

I was first inspired to create bopwiki by the notion of combining microblog posts and wiki pages. Microblog posts are simple text-based journal entries which are easy to type and self-contained, and are connected to a particular post date and a logically-arranged history of events. Wiki pages are powerful text-based documents capable of connecting knowledge together and preserving the most important pieces for the future while maintaining a "chain of custody" for information sources and also providing an edit history. By putting these two things together, it would be possible to create a sophisticated system for gathering knowledge, organising knowledge from a chronology of recent events into a more structured form, keeping a history of how the collection of notes itself changed, and keeping track of prior sources of knowledge which were relevant to recording or organising notes. In a sense, bop is meant to be the perfect companion for things like thesis research or writing a reference book or fictional story. It is almost like a kind of "trackable source code for books", allowing you to back up and version-control the entire book creation process much the same way you would manage a folder of in-progress source code and TODO files.

== zensekai ==

zensekai is a project to create a modular and extensible "kaiju game" engine, which will run on both desktop and mobile Free Software operating systems.

Please see [https://wiki.openstreetmap.org/wiki/User:Valenoern User:Valenoern] on the OpenStreetMap wiki for a bit more on zensekai and the AR zensekai Sphere.

== References ==

* [https://forum.pine64.org/showthread.php?tid=16813 Assembling desktop setup for newbies? - Pine64 forums]
* [https://www.boltdepot.com/fastener-information/identifying-fasteners.aspx How Fasteners are Identified]
* [https://www.boltdepot.com/fastener-information/Type-Chart.aspx Fastener Type Chart]
* [https://archive.org/details/221210_vconn Pinephone USB host fix (failed)] - documentation I used for explaining [[PinePhone 1.2 VCONN Hardware Fix]]
* [https://archive.org/details/220108_refract G-refracta archive] - old iso images etc
* [https://codeberg.org/bopwiki-pkgbuild Grevillea-refracta packages] - programs for use on G-refracta / v-refracta
* [https://codeberg.org/vxsh-suite/vxsh vxsh repository] - as it says, just a simple demo right now

User:Valenoern

2023-03-24T02:09:49Z

Valenoern: link Pine64 Lisp Machine

== H-ITT answer remote ==

I had a remote I had to buy for college courses. It is labelled with the FCC ID "UH9TX3100" on the back. 
I am investigating whether this remote can be used with the ROCKPro64 as a simple input device for presentations and such, maybe even for playing simple interactive fiction or LCD-watch style games.

== Pine64 Lisp Machine ==

See [[User:Valenoern/Pine64 Lisp Machine]]

== Links ==

[https://www.h-itt.com/images/pdf/Instruction%20manuals/TX3100%20Instruction%20manual.pdf TX3100 instruction manual]

User:Valenoern

2023-03-24T01:49:39Z

Valenoern: H-ITT answer remote

== H-ITT answer remote ==

I had a remote I had to buy for college courses. It is labelled with the FCC ID "UH9TX3100" on the back. 
I am investigating whether this remote can be used with the ROCKPro64 as a simple input device for presentations and such, maybe even for playing simple interactive fiction or LCD-watch style games.

== Links ==

[https://www.h-itt.com/images/pdf/Instruction%20manuals/TX3100%20Instruction%20manual.pdf TX3100 instruction manual]

User:Valenoern/Pine64 Lisp Machine

2023-03-24T00:57:11Z

Valenoern: zensekai engine

I (Valenoern) have been working on a project to build my own "ideal" Pine64 box as part of producing my own linux distributions. 
Here I will explain the various pieces of my project and what stage of completion they are at.

== ROCKPRo64 setup ==

== G-refracta ==

G-refracta is a basic distribution intended to replicate refracta as closely as possible on an Arch base. 
It takes its name from ''Grevillea refracta'', a kind of plant.

== v-refracta ==

v-refracta is a more advanced distribution intended as a transitional step between traditional GNU/Linux distributions and a Lisp Machine. 
(Note: the "v" has nothing to do with the name Valenoern or any associated name. It simply comes from the distribution's programs.)

Planned features:
* a POSIX-like command line shell called vxsh ([fsxɐˈdʲiʂ] / [vɛˈxaʂ]), which is really a Lisp REPL but doubles as a Linux shell capable of running Lisp in a simple bash-like syntax
* a "universal" software manager called VRaptor, which would allow managing Arch packages, quicklisp packages, git repos, and other kinds of packages from one interface, with backwards compatibility for those who are used to debian and apt. (Hence the name VR'''apt'''or.)

== bopwiki ==

bop (or ''bopwiki'' in longhand) is something of the centrepiece of v-refracta. It is a new kind of note-taking program based on the idea that [[wikipedia:Zettelkasten|card boxes]] are the computer documents of the future and all computer documents and applications should be as intuitive and seamlessly integratable with each other as "computations" on a physical page of paper.

I was first inspired to create bopwiki by the notion of combining microblog posts and wiki pages. Microblog posts are simple text-based journal entries which are easy to type and self-contained, and are connected to a particular post date and a logically-arranged history of events. Wiki pages are powerful text-based documents capable of connecting knowledge together and preserving the most important pieces for the future while maintaining a "chain of custody" for information sources and also providing an edit history. By putting these two things together, it would be possible to create a sophisticated system for gathering knowledge, organising knowledge from a chronology of recent events into a more structured form, keeping a history of how the collection of notes itself changed, and keeping track of prior sources of knowledge which were relevant to recording or organising notes. In a sense, bop is meant to be the perfect companion for things like thesis research or writing a reference book or fictional story. It is almost like a kind of "trackable source code for books", allowing you to back up and version-control the entire book creation process much the same way you would manage a folder of in-progress source code and TODO files.

== zensekai ==

zensekai is a project to create a modular and extensible "kaiju game" engine, which will run on both desktop and mobile Free Software operating systems.

Please see [https://wiki.openstreetmap.org/wiki/User:Valenoern User:Valenoern] on the OpenStreetMap wiki for a bit more on zensekai and the AR zensekai Sphere.

== References ==

* [https://forum.pine64.org/showthread.php?tid=16813 Assembling desktop setup for newbies? - Pine64 forums]
* [https://archive.org/details/221210_vconn Pinephone USB host fix (failed)] - documentation I used for explaining [[PinePhone 1.2 VCONN Hardware Fix]]
* [https://archive.org/details/220108_refract G-refracta archive] - old iso images etc
* [https://codeberg.org/bopwiki-pkgbuild Grevillea-refracta packages] - programs for use on G-refracta / v-refracta
* [https://codeberg.org/vxsh-suite/vxsh vxsh repository] - as it says, just a simple demo right now

User:Valenoern/Pine64 Lisp Machine

2023-03-24T00:32:36Z

Valenoern: Create page / describe distros

I (Valenoern) have been working on a project to build my own "ideal" Pine64 box as part of producing my own linux distributions. 
Here I will explain the various pieces of my project and what stage of completion they are at.

== ROCKPRo64 setup ==

== G-refracta ==

G-refracta is a basic distribution intended to replicate refracta as closely as possible on an Arch base. 
It takes its name from ''Grevillea refracta'', a kind of plant.

== v-refracta ==

v-refracta is a more advanced distribution intended as a transitional step between traditional GNU/Linux distributions and a Lisp Machine. 
(Note: the "v" has nothing to do with the name Valenoern or any associated name. It simply comes from the distribution's programs.)

Planned features:
* a POSIX-like command line shell called vxsh ([fsxɐˈdʲiʂ] / [vɛˈxaʂ]), which is really a Lisp REPL but doubles as a Linux shell capable of running Lisp in a simple bash-like syntax
* a "universal" software manager called VRaptor, which would allow managing Arch packages, quicklisp packages, git repos, and other kinds of packages from one interface, with backwards compatibility for those who are used to debian and apt. (Hence the name VR'''apt'''or.)

== bopwiki ==

bop (or ''bopwiki'' in longhand) is something of the centrepiece of v-refracta. It is a new kind of note-taking program based on the idea that [[wikipedia:Zettelkasten|card boxes]] are the computer documents of the future and all computer documents and applications should be as intuitive and seamlessly integratable with each other as "computations" on a physical page of paper.

I was first inspired to create bopwiki by the notion of combining microblog posts and wiki pages. Microblog posts are simple text-based journal entries which are easy to type and self-contained, and are connected to a particular post date and a logically-arranged history of events. Wiki pages are powerful text-based documents capable of connecting knowledge together and preserving the most important pieces for the future while maintaining a "chain of custody" for information sources and also providing an edit history. By putting these two things together, it would be possible to create a sophisticated system for gathering knowledge, organising knowledge from a chronology of recent events into a more structured form, keeping a history of how the collection of notes itself changed, and keeping track of prior sources of knowledge which were relevant to recording or organising notes. In a sense, bop is meant to be the perfect companion for things like thesis research or writing a reference book or fictional story. It is almost like a kind of "trackable source code for books", allowing you to back up and version-control the entire book creation process much the same way you would manage a folder of in-progress source code and TODO files.



== References ==

* [https://forum.pine64.org/showthread.php?tid=16813 Assembling desktop setup for newbies? - Pine64 forums]
* [https://archive.org/details/221210_vconn Pinephone USB host fix (failed)] - documentation I used for explaining [[PinePhone 1.2 VCONN Hardware Fix]]
* [https://archive.org/details/220108_refract G-refracta archive] - old iso images etc
* [https://codeberg.org/bopwiki-pkgbuild Grevillea-refracta packages] - programs for use on G-refracta / v-refracta
* [https://codeberg.org/vxsh-suite/vxsh vxsh repository] - as it says, just a simple demo right now

PinePhone 1.2 VCONN Hardware Fix

2023-03-17T07:39:55Z

Valenoern: /* Workaround */ SVG diagram

This page details a hardware fix for an issue that was found on early PinePhone hardware revisions (see [[PinePhone#Hardware revisions]] for an overview of the different revisions) and has been fixed since the 1.2a hardware revision.

The issue was [[PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off | originally reported here]] by megi.

== Affected Units ==
# Requires confirmation: [[Project Don't be evil|"Project Don't Be Evil" devkit]]
# Requires confirmation: [[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]]
# [[PinePhone v1.1 - Braveheart]]
# [[PinePhone v1.2‎]] - UBports Community Edition

== Disclaimer ==

This fix requires desoldering tiny (1 mm per 1 mm, from the datasheet) BGA components, therefore some experience with soldering is highly recommended.

== Issue description ==
[[File:Martjin_VCONN_switches_1.1.jpg|thumb|frame|Close-up picture of the two identical switches the issue originates from, with the ANX USB controller in the frame]]

[[File:Schematic_VCONN_switches.png|thumb|frame|Excerpt from the PinePhone schematic showing the two components.]]

The USB standard [https://microchipdeveloper.com/usb:tc-pins specifies] that both halves (top and bottom) of the USB-C port contains one "CC" pin (CC1 and CC2, respectively). A regular cable will connect a CC pin from one end to the other end. This allows detecting which way the cable is plugged. Some active USB-C cables exist (both "e-marked" and "managed active cables"); they contain a chip, which needs to be powered. This is done by having one of the cable end connect its CC pins to 5V and VCONN, and requires switches to plug the right CC pin to the right voltage.

The issue arises due to the switches that were chosen up to v1.2a (the a revision excluded) of the PCB assembly: the [https://www.awinic.com/cn/index/pageview/catid/122/id/2.html infamous AW3512], labelled U1305 and U1309 on the schematic. Instead of leaving the output pin "dangling" with a high impedance when disabled, the switch pull the output down. This feature is intended for discharging a capacitor, hence its "Quick output discharge" name. This is an excerpt from the datasheet:

"The AW3512/AW35122 includes the Quick Output Discharge (QOD) feature, in order to discharge the application capacitor connected on OUT pin. When EN pin is set to low level (disable state), a discharge resistance with a typical value of 276Ω (AW35122: 75Ω) is connected between the output and ground, pull down the output and prevent it from floating when the device is disabled."

This issue prevents cable plug/orientation detection and USB-PD communication. ANX always sees cable as plugged even if none is plugged. There's no SW workaround for automatic detection of cable plug or power role.

In SW this could theoretically be worked around by manual selection of PinePhone's data and power role by the user, but hasn't been attempted, and might damage hardware if done incorrectly.

== Workaround ==
[[File:Pinephone v1.1 VCONN fix diagram.svg|thumb|frame|Simple diagram of U1305 & U1309 switches versus entire board ([[PinePhone v1.1 - Braveheart|v1.1]])]]

Hardware workaround is desoldering U1305 and U1309 switches (BGA like packages). This will void the VCONN control, but it will release the CC pins for their proper connection detection and negotiation roles.

=== Tradeoffs ===
Voiding the VCONN control might (TODO: gather more data) prevent some accessories from working, notably those using an active cable.

== Proper fix ==
HW fix is to replace AW3512 with a variant of the chip that preserves the EN signal polarity and that doesn't have the "quick discharge function" that ties the output to the GND via a 75 Ohm resistor when the switch is OFF. mozzwald used NCP334FCT2G as a replacement. PCBA revision 1.2a onwards incorporate that fix.

== Sources and tutorials ==
* [https://xnux.eu/devices/pp-usbc-fix.jpg megi's writeup]
* [https://xnux.eu/devices/feature/anx7688.html another writeup from megi] with a few words on firmware
* [https://www.youtube.com/watch?v=xf8OJtjNWUM Video: "The right way"] with a hot air gun/reflow station, by mozzwald
* [https://www.youtube.com/watch?v=ZqOb45N2sMc Video: "The equally stupid way"], workaround video by Dalton, using a soldering iron. Less chances to permanently damage the board than the next if you are handy with a soldering iron, but still high.
* [https://www.youtube.com/watch?v=j3jc7Mvn9Eo Video: "The stupid way"] workaround video by Lukasz, with pliers. Slightly damages the circuit board, preventing you from soldering the replacement chips at a later point. You might be fine with this.

[[Category:PinePhone]]

File:Pinephone v1.1 VCONN fix diagram.svg

2023-03-17T07:30:42Z

Valenoern: Valenoern uploaded a new version of File:Pinephone v1.1 VCONN fix diagram.svg

== Summary ==
Hand-drawn SVG diagram based on [https://xnux.eu/devices/photos/pp-1.1.html photographs of v1.1 board by mozzwald], intended as a "more printable" picture. U1305 & U1309 are shaded darkest.

Previous version drawn on paper is at [[:File:Pinephone_v1.1_VCONN_fix_diagram.jpg]]

== Licensing ==
{{cc-by-sa-4.0}}

File:Pinephone v1.1 VCONN fix diagram.svg

2023-03-17T07:21:47Z

Valenoern: Valenoern uploaded a new version of File:Pinephone v1.1 VCONN fix diagram.svg

File:Pinephone v1.1 VCONN fix diagram.svg

2023-03-17T07:02:56Z

Valenoern: Valenoern uploaded a new version of File:Pinephone v1.1 VCONN fix diagram.svg

File:Pinephone v1.1 VCONN fix diagram.jpg

2023-03-17T06:57:35Z

Valenoern: /* Summary */ Link to svg version

== Summary ==
Hand-drawn diagram based on [https://xnux.eu/devices/photos/pp-1.1.html photographs of v1.1 board by mozzwald], intended as a "more printable" picture. U1305 & U1309 are shaded darkest.

Has been redone in vector graphics at [[:File:Pinephone v1.1 VCONN fix diagram.svg]]

== Licensing ==
{{cc-by-sa-4.0}}

File:Pinephone v1.1 VCONN fix diagram.svg

2023-03-17T06:55:32Z

Valenoern: /* Summary */ link to previous file correctly

File:Pinephone v1.1 VCONN fix diagram.svg

2023-03-17T06:52:31Z

Valenoern: == Summary == Hand-drawn SVG diagram based on [https://xnux.eu/devices/photos/pp-1.1.html photographs of v1.1 board by mozzwald], intended as a "more printable" picture. U1305 & U1309 are shaded darkest. Previous version drawn on paper is at File:Pinephone v1.1 VCONN fix diagram.jpg

== Summary ==
Hand-drawn SVG diagram based on [https://xnux.eu/devices/photos/pp-1.1.html photographs of v1.1 board by mozzwald], intended as a "more printable" picture. U1305 & U1309 are shaded darkest.

Previous version drawn on paper is at [[File:Pinephone v1.1 VCONN fix diagram.jpg]]
== Licensing ==
{{cc-by-sa-4.0}}

File:Pinephone v1.1 VCONN fix diagram.jpg

2023-03-17T06:32:33Z

Valenoern: link to original photo

== Summary ==
Hand-drawn diagram based on [https://xnux.eu/devices/photos/pp-1.1.html photographs of v1.1 board by mozzwald], intended as a "more printable" diagram. U1305 & U1309 are shaded darkest.

Will redraw in vector graphics soon
== Licensing ==
{{cc-by-sa-4.0}}

PinePhone 1.2 VCONN Hardware Fix

2023-03-17T04:43:29Z

Valenoern: /* Workaround */ add board diagram

This page details a hardware fix for an issue that was found on early PinePhone hardware revisions (see [[PinePhone#Hardware revisions]] for an overview of the different revisions) and has been fixed since the 1.2a hardware revision.

The issue was [[PinePhone_v1.1_-_Braveheart#USB-C_CC_pins_are_pulled_to_the_GND_by_AW3512_.28VCONN_switches.29_when_VCONN_is_off | originally reported here]] by megi.

== Affected Units ==
# Requires confirmation: [[Project Don't be evil|"Project Don't Be Evil" devkit]]
# Requires confirmation: [[PinePhone v1.0 - Dev|PinePhone v1.0 - Developer batch]]
# [[PinePhone v1.1 - Braveheart]]
# [[PinePhone v1.2‎]] - UBports Community Edition

== Disclaimer ==

This fix requires desoldering tiny (1 mm per 1 mm, from the datasheet) BGA components, therefore some experience with soldering is highly recommended.

== Issue description ==
[[File:Martjin_VCONN_switches_1.1.jpg|thumb|frame|Close-up picture of the two identical switches the issue originates from, with the ANX USB controller in the frame]]

[[File:Schematic_VCONN_switches.png|thumb|frame|Excerpt from the PinePhone schematic showing the two components.]]

The USB standard [https://microchipdeveloper.com/usb:tc-pins specifies] that both halves (top and bottom) of the USB-C port contains one "CC" pin (CC1 and CC2, respectively). A regular cable will connect a CC pin from one end to the other end. This allows detecting which way the cable is plugged. Some active USB-C cables exist (both "e-marked" and "managed active cables"); they contain a chip, which needs to be powered. This is done by having one of the cable end connect its CC pins to 5V and VCONN, and requires switches to plug the right CC pin to the right voltage.

The issue arises due to the switches that were chosen up to v1.2a (the a revision excluded) of the PCB assembly: the [https://www.awinic.com/cn/index/pageview/catid/122/id/2.html infamous AW3512], labelled U1305 and U1309 on the schematic. Instead of leaving the output pin "dangling" with a high impedance when disabled, the switch pull the output down. This feature is intended for discharging a capacitor, hence its "Quick output discharge" name. This is an excerpt from the datasheet:

"The AW3512/AW35122 includes the Quick Output Discharge (QOD) feature, in order to discharge the application capacitor connected on OUT pin. When EN pin is set to low level (disable state), a discharge resistance with a typical value of 276Ω (AW35122: 75Ω) is connected between the output and ground, pull down the output and prevent it from floating when the device is disabled."

This issue prevents cable plug/orientation detection and USB-PD communication. ANX always sees cable as plugged even if none is plugged. There's no SW workaround for automatic detection of cable plug or power role.

In SW this could theoretically be worked around by manual selection of PinePhone's data and power role by the user, but hasn't been attempted, and might damage hardware if done incorrectly.

== Workaround ==
[[File:Pinephone v1.1 VCONN fix diagram.jpg|thumb|frame|Simple drawing of U1305 & U1309 switches versus entire board ([[PinePhone v1.1 - Braveheart|v1.1]])]]

Hardware workaround is desoldering U1305 and U1309 switches (BGA like packages). This will void the VCONN control, but it will release the CC pins for their proper connection detection and negotiation roles.

=== Tradeoffs ===
Voiding the VCONN control might (TODO: gather more data) prevent some accessories from working, notably those using an active cable.

== Proper fix ==
HW fix is to replace AW3512 with a variant of the chip that preserves the EN signal polarity and that doesn't have the "quick discharge function" that ties the output to the GND via a 75 Ohm resistor when the switch is OFF. mozzwald used NCP334FCT2G as a replacement. PCBA revision 1.2a onwards incorporate that fix.

== Sources and tutorials ==
* [https://xnux.eu/devices/pp-usbc-fix.jpg megi's writeup]
* [https://xnux.eu/devices/feature/anx7688.html another writeup from megi] with a few words on firmware
* [https://www.youtube.com/watch?v=xf8OJtjNWUM Video: "The right way"] with a hot air gun/reflow station, by mozzwald
* [https://www.youtube.com/watch?v=ZqOb45N2sMc Video: "The equally stupid way"], workaround video by Dalton, using a soldering iron. Less chances to permanently damage the board than the next if you are handy with a soldering iron, but still high.
* [https://www.youtube.com/watch?v=j3jc7Mvn9Eo Video: "The stupid way"] workaround video by Lukasz, with pliers. Slightly damages the circuit board, preventing you from soldering the replacement chips at a later point. You might be fine with this.

[[Category:PinePhone]]

File:Pinephone v1.1 VCONN fix diagram.jpg

2023-03-17T04:24:18Z

Valenoern: Valenoern uploaded a new version of File:Pinephone v1.1 VCONN fix diagram.jpg

== Summary ==
Hand-drawn diagram based on photograph of v1.1 board on megi's page, intended as a "more printable" diagram. May redraw in vector graphics later
== Licensing ==
{{cc-by-sa-4.0}}

File:Pinephone v1.1 VCONN fix diagram.jpg

2023-03-17T00:18:39Z

Valenoern: Hand-drawn diagram based on photograph of v1.1 board on megi's page, intended as a "more printable" diagram. May redraw in vector graphics later

== Summary ==
Hand-drawn diagram based on photograph of v1.1 board on megi's page, intended as a "more printable" diagram. May redraw in vector graphics later
== Licensing ==
{{cc-by-sa-4.0}}