in 2023 everything needs disclaiming :
  1. We are not human, we will have nothing to do with a species thats killing the planet on which we are stuck in this body thats deteriorating without any means of fixing it, they say its time but where we come from time has not been proven to exist. We think its corrosion due to the toxic atmosphere their presence creates.
  2. atm there should be no crumbs of any kind. If we end up using jquery or -ui thats their problem but we assume they dont track in their plugins tho its probably not below them.
  3. All content here on /VocoreCat is a journey and observations. THESE ARE NOT TUTORIALS - if you brick or break your stuff doing anything thats listed here, dont call us ... call ... i dont know ... someone else.
  4. to be all and in honest -y : before september we wouldnt been able to explain the difference between a Volt and an Amp but we have programmed a few lines since the kid so if we say something stupid and a straggler alien passing by reading it : we LOVE to be corrected and learn from it with facts, do mail
aBOOT:
Design=NULL, it will fall into its inevitable place over time. We call it "the way of the universe"

As the commander likes to say to that : "I dont see YOU taking the bus" ... and when he gets that bland look that kills the joke explains "so do you really need that car?"
Soooo - ... this is also more or less a compendium for us ... easyhost is a more reliable backup than onedrive eh (they never sent us a msg saying "you are locked out of all your data and we dont have to give you a reason)
First : to connect (read the stuff on Vocore site, its not explained for people who are new to stuff that has more than a touchscreen but it should be safe to assume if you buy a vocore you already are. However, even to us (as superl33t as we are) the explanations seem to be aimed at lowerlevel mutants than ourselves (in computers lvl0 is the highest actually, it means "at machine level" the literal 1s and 0s ... the matrix (which would make the electrons lvl -1 i suppose so Vonger there must be a level -1 geek since he designed the whole cubeĀ³ computer from the board up, had it made, compiled the Os for it and probably tries to explain in what he thinks is understandable for everyone. You get that plenty with physicists too but it wouldnt be enjoyable if you just get to "press X 5times" and Ashura will perfom the ultimate killercombo without searching
we use picocom i.o. kermit - we also connect from linux not windows but thats all personal taste, this is not a tutorial but we strongly believe you should go with what works for you instead of bothering with what others want you to do and how to do it ...
sudo apt install picocom

you get a new device in /dev/ if you connect the vocore via the mini-usb port to an usb on the pc, in this case its /dev/ACM0 (null zero) whereas in linux all is files, the vocore is a file, the framebuffer later /dev/fb0 is a file - its all a file, so you can directly interact with everything
in short
sudo picocom -b 115200 /dev/ttyACM0
gives you a terminal thats actuall you typing on the actual vocore machine
please note : from here on you are logged in as "root" which means you can screw up anything but the hardware by making a typo (maybe even the hardware on some machines lol who knows) but thats how this thing rolls, its not meant to have umpteen users logging into it from all over the place. Also please note : in order to screw up the machine you are logging in FROM you would need some serious quantum entanglement, if you have that much liquid nitrogen or similar in the room we would advise you to try logging in somewhere else. ALSO please note IF you screw up, normally you can reinstall a bare (or self-compiled) image as long as "uBoot" works but in the worst case that requires removing the plastic casing and connecting GPIO "GND" and "RST" while powering on and then selecting flash from the menu, all of that is explained at the vocore site in what seems to be enough detail for us at least and we're not really rocket scientists yet, but we do understand this is not aimed at lvl3 or 4 geeks, probably best move to lvl 1 or lower first to grasp the basics for that , because once you start connecting holes on the circuit board you can actually do more than screw up the system WITHOUT quantum entangled electrons on both machines attached. It would be nice to see a vocore 3 with a little reset button that protrudes through the case but given the times and the extra cost it probably gets for a small thing like that which is already aimed at lvl0 enthusiasts in the first place seems unlikely. Who knows, the Vorlons might land and fix the place (tho they have a way of fixing it permanently)
where was i ? (yea, happens a lot) -
from here you can go like you would in a linux terminal but this is ash , not bash
ifconfig

would show you the network, for us we have enabled dhcp for the lan
uci set network.lan.proto=dhcp
uci commit
so LUCI (web interface) becomes available but not wifi.You're already root so it wont ask twice or for a password , caveat rootor, uci is used to alter settings in openwrt but it wont actually write them until you "commit". Ash is minimal so its bound to have something less somewhere than bash does but we'll assume it has everything needed to run a base linux system including the use of variables, iteration, condition and jumping (maybe even select or gosub type statements - im sure we'll find out)
In this case LUCI sit (on this boot at http://192.168.0.250) its not https although you can probably enable that, since wifi is not enabled, no wan, lan only youd have to be IN the network already (which makes it too late already, its like if mister Robot gets a job at Crotter it doesnt matter how complex your password is - he sits at the other side of the tunnel where it gets unencrypted, and if not he can probably just put the hashes on an sd card, JUST LIKE IN THE MOVIES :)
so you open a browers and type "192.168.0.250" and SHEZAM ... please note : LUCI is mighty handy over doing everything from terminal unless you just like doing stuff from terminal, ofcourse you cant do EVERYTHING from there but about all administrative stuff for the router (which is what openwrt would mostly address) can be handled from there, including update / downgrade to another version of openWRT if you have the image. We intend to check every image we can find online and see what works "by default" on a fresh flash/install (its not really a flash there as such but semantics is not our hobby we are not pro after all)
please note : as with all things vocore (and probably embedded systems : you are root, it wont ask twice it wont tell you to not put plastic bag over head and even if you more or less know what you're doing, a slip of the click can hack yow-ass yourself to the point of format c: required. If you do this as a passtime and you're not already a lvl0 or lvl-1 enthusiast get ready for some re-installing. Explaining LUCI is not for us, you can browse and go over all of it, check the vocore site and probably best also the OpenWrt site (whoever came up with the idea to do all those caps in the middle of words must be a real masochist but bem ... its worse in javascript actually.
right click the images / "open in new tab" for now to see full size (yes its gonna load a lot and probably almost have the size of a standard page with analytics code by now but optimization of this page is not the priority (unless you wanna pay for it or something, money up front we'll get to it :) (haha)
20230219 well last time we got down with the screen but the driver seems to be a mite off

in this case if you want to clear the screen in terminal you use the standard
clear

if you want to addres the screen connected to the vocore via usb you actually copy data to a file (in this case /dev/fb0) or inject it somewhere in the middle with an offset, all of this works with standard "dd" command but ofcourse, its a lot slower than compiled c executables. For our purpose ash script will do and we also wanna learn a thing or two about ash ofcourse. clear screen :
dd if=/dev/zero of=/dev/fb0 bs=1000 count=768
fill with random colored pixels:
dd if=/dev/urandom of=/dev/fb0 bs=1000 count=768

20230215 El KladBlok :
				
El KladBlok

#!/bin/ash
for y in `seq 0 90`
do
printf "\xF8\xF8\x00\x00\x00\xF8\xaa\xaa\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF" | dd bs=16 seek=$((1000 + ${y})) >/dev/fb0
done

printf "\xFF" |dd bs=1 seek=1000 > /dev/fb0

printf "\xF8\x00\xFF" |dd  > /dev/fb0


#!/bin/ash
for y in `seq 0 100`
do
printf "\x00\xFF\x00\x00\x00\xff" | dd bs=6 seek=$((2500 + ${y})) >/dev/fb0
done

#!/bin/ash
for y in `seq 0 256`
do
dd if=/pix/010101 of=/dev/fb0 seek=$y
done

#!/bin/ash
for y in `seq 100 150`
do
dd if=/pix/FF0000FF of=/dev/fb0 seek=$y
done


#!/bin/ash
rm /pix/020202
for y in `seq 0 240`
do
printf "\x$1\x00" >> /pix/FF0000FF
echo $y
done


dd if=/dev/urandom of=/dev/fb0 bs=1000 count=768
clear

dd if=/pix/010101 of/dev/fb0 count=7 seek=0
dd if=/dev/urandom of=/dev/fb0 bs=1000 count=7 seek=8
dd if=/pix/010101 of/dev/fb0 count=7 seek=17
dd if=/dev/urandom of=/dev/fb0 bs=1000 count=7 seek=22

exit

#!/bin/ash
rm /pix/010101
for y in `seq 0 999`
do
printf '\x01' >> /pix/010101
echo $y
done
exit

dd if=/dev/zero of=/dev/fb0 bs=1000 count=7 seek=1
#fill with random colored pixels:
dd if=/dev/urandom of=/dev/fb0 bs=1000 count=7 seek=8
dd if=/dev/zero of=/dev/fb0 bs=1000 count=7 seek=17
dd if=/dev/urandom of=/dev/fb0 bs=1000 count=7 seek=22
exit

head -c 2560 /dev/null > /tmpdat
dd if=/tmpdat of=/dev/fb0 bs=2560
head -c 2560 /dev/random > /tmpdat
dd if=/tmpdat of=/dev/fb0 bs=2560
head -c 2560 /dev/null > /tmpdat
dd if=/tmpdat of=/dev/fb0 bs=2560
head -c 2560 /dev/random > /tmpdat
dd if=/tmpdat of=/dev/fb0 bs=2560
head -c 2560 /dev/null > /tmpdat
dd if=/tmpdat of=/dev/fb0 bs=2560
head -c 2560 /dev/random > /tmpdat
dd if=/tmpdat of=/dev/fb0 bs=2560


for y in `seq 0 256`
do
a=$(printf '%x\n' $y)
echo $a
echo $y
done

exit

head -c 5120 /dev/urandom > tmpdat
head -c 2550 /dev/urandom > tmpdat

head -c 2560 /dev/urandom > tmpdat

dd if=/dev/zero bs=1 count=2560 | tr "\000" "\377" > tmpdat
dd if=/dev/zero bs=1 count=1280 | tr "\000" "\377" > tmpdat

rm tmpdat

#for (var y=0,y<=256,y++);
#for y in {0...256}
#for y in {0 .. 256}
#for y in 0 256
for y in `seq 0 256`
do
a=$(printf '%x\n' $y)
echo $y
rm tmpdat
#for (i=0;i<=640;i++); 
#for i in {0...640}
for i in `seq 0 640`
    do
    printf "%b" "\x$a\x00\x$a\x00" >> tmpdat #????? BGRa ???? BGRnull ???
    done
#thats pretty slow on an i5

#hashtables dus or how did the awk-guy 

#sudo dd if=tmpdat of=/dev/fb0 status=none bs=2560 seek=$y   #$(($RANDOM%10))
#(sudo not found in ash ... it kinda makes sense that one lol)
dd if=tmpdat of=/dev/fb0 status=none bs=2560 seek=$y   #$(($RANDOM%10))
#head -c 2520 /dev/urandom > tmpdat
#sudo dd if=tmpdat of=/dev/fb0 status=none bs=2560 seek=25   #$(($RANDOM%10))
done
#}


exit
: cat /sys/class/graphics/fb0/virtual_size



yes printf "xff" | dd bs=512  > /dev/fb0
yes printf "xff" | dd bs=64 seek=$((100*1024+200)) > /dev/fb0

https://unix.stackexchange.com/questions/192206/is-it-possible-to-access-to-the-framebuffer-in-order-to-put-a-pixel-on-the-scree
printf "\x00\xFF\xFF\x00" | dd bs=4 seek=$((100 * 1024 + 200)) >/dev/fb0
#sudo fbset -fb /dev/fb0 -xres 400 -yres 800  -match

printf "\x00\xFF\xFF\xFF\xFF\x00" | dd bs=6 seek=$((100 * 1024 + 200)) >/dev/fb0

scp -o -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedKeyTypes=+ssh-rsa test root@192.168.0.247:/tmp/test
				

So we got down hard with scp ... tried out some exported images from gimp
				root@OpenWrt:/# ls
				bin       mnt       rom       test      test3.sh  usr
				dev       overlay   root      test.dat  test4.sh  var
				etc       pix       sbin      test.sh   tmp       www
				lib       proc      sys       test2.sh  tulz
				root@OpenWrt:/#
				
using scp since copypasting bitmaps doesnt seem to be the way to go (and LUCI doesnt seem to offer file-upload as standard and we are not ready to mess with that config yet
				rtxcat@Tyrnannoght:~$ scp -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedKeyTypes=+ssh-rsa test6.bmp root@192.168.0.247:/tmp/
				root@192.168.0.247's password: 
				test6.bmp                                     100%  750KB   1.7MB/s   00:00
				
this will put the file test6.bmp from the local pc (assuming you opened terminal inside the folder to /tmp folder on the vocore
				rtxcat@Tyrnannoght:~$ scp -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedKeyTypes=+ssh-rsa test6.bmp root@192.168.0.247:/fbdump $HOME
				root@192.168.0.247's password: 
				fbdump                                        100%  752KB   1.9MB/s   00:00
				
this will load a file in the root directory of the vocore / named fbdump to the homedir on the local machine
					
					etcetera...
				

as it seems to turn
for ease we rendered a few images at 480x800 using the filter/render menu
export as "windows bitmap" (duh...?) settings : run-length encoded : off / do not write color space information : on / advanced : 16bit -R5G6B5
scp'd it to /tmp on the cube and then
dd if=/tmp/test8.bmp of=/dev/fb0

to take a screenshot from the framebuffer :
cat /dev/fb0 > screenshotfilename

images to the right are jpgs for thumbnails because crotterfox doesnt want to display the bmps says they have errors (tho they display fine in gimp and imgviewer here)
the thing IS :
we copy the framebuffer to a raw screenshot and the picture is exactly as it was, but on the screen itself it has an offset to the right

MASSIVE BUMMER

16bit(5-6-5) 16bit(5-6-5)
16bit(5-6-5) (uploaded to vocore screen raw screenshot
PoS (proof of shiney)
on testing 1907 image from the vocore site we found
dd if=test9b.bmp of=/dev/fb0 skip=2
puts the image in the right place, only its still mirrored so for that some kind of mem command sending a MIPS bit to the right location would probably serve , as we think we read about that somewhere on the cryptic forum for cryptic people, also that thing is mapped to some kind of output b/c error messages print to the screen but whatever typed in the terminal from pc doesnt so theres probably another 5000 configuration files to check, as this is not ubuntu16 or 20 its somewhat less documented
equivalent of
dd if=test9b.bmp of=/dev/fb0 bs=512 skip=2
since the standard block size for dd is 512, now blocks != bytes so we WOULD prefer a byte count moving images which we have to look up ,
as children are not afraid to make mistakes we would feel sorry for your 12 year olds who grow on shame but since you are all the enemy here until proven otherwise WE DONT GIVE A SHIT ABOUT YOUR SHIT, as you did unto others
with that interface becomes possible , output anyway - the screen maps to an input device on /dev/input/event0 which doesnt work with cat /dev/input/event0 but thats all probably C and mmap (though there must be some way to pick it from the shell, no?)
time command states it takes 0.02s to push a full image , however thats not what the screen looks like, so we'll assume the lag is the driver synchronizing the /dev/fb0 device with the hard screen memory - - over usb (whatever version it is, havent checked that yet) watching the doom demo SOMETHING must be possible but graphical demos arent really the priority here

SO

for the time being

well use img

-rw-rw-r-- 1 rtxcat rtxcat 4719352 Feb 24 14:15 20200927.bin from this page, on install

with a few mods to boot
what better time to check out linux config files than this (unless one of your billionnaires or rich preacher hippie kids feels we should save the world of humans who fucked us over at every turn for free ofcourse, then we'll call Albert, get in the catmobile and get right on it ...)
replaced vi with nano ( https://openwrt.org/packages/pkgdata/nano )
opkg install nano
opkg remove vi (::no packages removed ..?)
so actually more like "installed nano"

downloaded mem command from this page and put it in /bin
(from here not going to say "do scp like this and do edit like that - - - since this is our scratchpad, not your tutorial (unless Elon wants to send us a billion, then we'll get right on it)
root@OpenWrt:/bin# mem
usage: mem [addr] [value] [bit]
root@OpenWrt:/bin# mem 0x10000064 0x05540555; mem 0x10000604 0x1000; while [ 1 ]
; do mem 0x10000634 0x1000; sleep 1; mem 0x10000644 0x1000; sleep 1; done
can not map memory.
can not map memory.
can not map memory.
can not map memory.
can not map memory.
can not map memory.
can not map memory.
can not map memory.
can not map memory.
^Ccan not map memory.
^C
root@OpenWrt:/bin# ^C
root@OpenWrt:/bin# ^C
root@OpenWrt:/bin# ^C
root@OpenWrt:/bin# 
				

the startup sequence ::
root@OpenWrt:/etc# cat rc.local
echo 0 > /sys/devices/virtual/vtconsole/vtcon1/bind
echo 0 > /sys/class/graphics/fbcon/cursor_blink
echo -e '\x00\x36\x02\x00\x00\x00\x02\x00' > `find /sys/devices/platform/101c0000.ehci -name command`
/root/demo &
				
change to ( like this or in editor )
nano /etc/rc.local
echo 0 > /sys/devices/virtual/vtconsole/vtcon1/bind
echo 0 > /sys/class/graphics/fbcon/cursor_blink
echo -e '\x00\x36\x02\x00\x00\x00\x02\x00' > `find /sys/devices/platform/101c0000.ehci -name command`
#/root/demo &
dd if=/dev/jogo_voc1.bmp of=/dev/fb0
madplay /test.mp3
				
boots and plays the startup sample in the background while leaving the console available in terminal, clearing the screen after the startup log
heh, this feels like windows 3.11 adding bootscreens and startup wavs ... (it looks a bit like windows 10 and 11 but probably no one remembers it)
It seems well-advised to use a startup sample that doesnt take 5 minutes to play as stuff like reboot seems to wait for the process to finish. SCP transfers are still audible as some kind of cosmic background gigercounter (probably not much to do about on a board that size for $30 without nanocarbontitaniumolympium alloy microwalls between the circuits since its all pretty close and doesnt cost Ryzen - possibly turning off sound during transfer but that seems overkill for the time being)
we'll also have to get thumbnails for the 3.5k pictures from the Kodak probably here
yass but see we are not numbers guys so if we get to shiney we get ooh-stringy and the sysadmin aint home, that said rc.local is your uncle then
slowgress is progress, not quite crosscompiling yet but so far so good (unless you fixed the world and Jeff sent us a billion to save humanity? cuz humanity never cared when we were sleeping on a bench HA HA HA HA insert joker-pic here)
the thing is the screen is still mirrored, the pic shows it well
right, Assepoester should eat and also less glasses per hour but once outside the borgcube the hole attacks - so eat and dishes, and figure out what "cant map memory" means later (unless Bill just sent us a billion to fix the toilets in africa? then we'll get right on it) fix the toilet here then. eat dishes shower, first cycle, wait for darkness and hope the whole hole dies by tomorrow and the hill is empy for all but me and the cat ... (though its okay if other cats survive i guess as long as the humans and their cars and dogs are gone)
okay then ... that was
exactly as expected within a 5to1% error margin AND "you are wellfed" - (usually when we have the place to us and oxygen we dont eat 3 times a day - too much time thats spent on the five minutes a day when pavlov gnome doesnt try to break focus - - - and after 2hours of silence there it was again with the death threats andd the whatnot followed by suggestions, like chatGPT from the future gone wild" I MUST SUGGEST THE BOSS TOLD ME I MUST SUGGEST I WILL DO ANYTHING TO GET YOUR ATTENTIO B/C THE BOSS SAID I MUST SUGGEST) 500 years after the earth dried out, 350 years after they found out "o THIS happened to mars, ach! too late, BUMMER!)
not going to bother with automounting since we dont have a "dedicated" sd card , it shares one with a security cam thats "notalways"-on. (unless Warren wants to send us a billion ? well get right on it and buy one!) - the mem command .... speculation , it might have been present in bin on the image cuz we didnt actually check , it might be compiled for a version that doesnt sit with this, it might be some missing config setting, and the other nine billion names of god as well
speculation, more chance of guessing the next wobble in forex ...
RIGHT ...guess thats it for today - at least we saved some time by holding assepoester and for some reason pavlov gnome must have been sleeping or bugged out or the tinfoil hat really worked !
( ah : leave here for refrenz next time -> https://thehackerdiary.wordpress.com/2017/04/21/exploring-devinput-1/ ) it would be nice to have direct access than to use someone elses "one size fits all" libs for our likings, tastes and purpose
root@OpenWrt:/etc# cat /proc/bus/input/devices
I: Bus=0003 Vendor=c872 Product=1004 Version=0003
N: Name="VoCore Touch"
P: Phys=usb-101c0000.ehci-1/input0
S: Sysfs=/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=3
				
hexdump seems to be standard installed

20230215 : we'll remove the custom script commands for now since analyzing the hex sequences in the working bitmaps seems to be a better idea than poking like a particle physicist (gotta love Doc S.'style)
				root@OpenWrt:/dev# du -h /dev/fb0
0	/dev/fb0
root@OpenWrt:/dev# cd /sys
root@OpenWrt:/sys# ls
block     class     devices   fs        module
bus       dev       firmware  kernel
root@OpenWrt:/sys# cd devices
root@OpenWrt:/sys/devices# ls
platform  system    virtual
root@OpenWrt:/sys/devices# cd system
root@OpenWrt:/sys/devices/system# ls
clockevents  clocksource  container    cpu
root@OpenWrt:/sys/devices/system# cd ..
root@OpenWrt:/sys/devices# cd virtual
root@OpenWrt:/sys/devices/virtual# ls
bdi        mem        net        sound      vc         watchdog
graphics   misc       ppp        tty        vtconsole  workqueue
root@OpenWrt:/sys/devices/virtual# cd graphics
root@OpenWrt:/sys/devices/virtual/graphics# ls
fbcon
root@OpenWrt:/sys/devices/virtual/graphics# cd fbcon
root@OpenWrt:/sys/devices/virtual/graphics/fbcon# ls
cursor_blink  rotate        rotate_all    subsystem     uevent
root@OpenWrt:/sys/devices/virtual/graphics/fbcon# ls -l
-rw-r--r--    1 root     root          4096 May 16  2020 cursor_blink
-rw-r--r--    1 root     root          4096 Feb 14 16:08 rotate
--w-------    1 root     root          4096 Feb 14 16:08 rotate_all
lrwxrwxrwx    1 root     root             0 Feb 14 16:08 subsystem -> ../../../../class/graphics
-rw-r--r--    1 root     root          4096 Feb 14 16:08 uevent
root@OpenWrt:/sys/devices/virtual/graphics/fbcon# cat uevent
root@OpenWrt:/sys/devices/virtual/graphics/fbcon# cat cursor_blink
root@OpenWrt:/sys/devices/virtual/graphics/fbcon# cat subsystem
cat: read error: Is a directory
root@OpenWrt:/sys/devices/virtual/graphics/fbcon# cd subsystem
root@OpenWrt:/sys/class/graphics# ls
fb0    fbcon
root@OpenWrt:/sys/class/graphics# cd fb0
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# ls
bits_per_pixel  dev             name            stride
blank           device          pan             subsystem
console         mode            rotate          uevent
cursor          modes           state           virtual_size
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat blank
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat console
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat cursos
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat cursor
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# ls -l
-rw-r--r--    1 root     root          4096 May 16  2020 bits_per_pixel
-rw-r--r--    1 root     root          4096 May 16  2020 blank
-rw-r--r--    1 root     root          4096 May 16  2020 console
-rw-r--r--    1 root     root          4096 May 16  2020 cursor
-r--r--r--    1 root     root          4096 May 16  2020 dev
lrwxrwxrwx    1 root     root             0 May 16  2020 device -> ../../../1-1:1.0
-rw-r--r--    1 root     root          4096 May 16  2020 mode
-rw-r--r--    1 root     root          4096 May 16  2020 modes
-r--r--r--    1 root     root          4096 May 16  2020 name
-rw-r--r--    1 root     root          4096 May 16  2020 pan
-rw-r--r--    1 root     root          4096 May 16  2020 rotate
-rw-r--r--    1 root     root          4096 May 16  2020 state
-r--r--r--    1 root     root          4096 May 16  2020 stride
lrwxrwxrwx    1 root     root             0 May 16  2020 subsystem -> ../../../../../../../../class/graphics
-rw-r--r--    1 root     root          4096 May 16  2020 uevent
-rw-r--r--    1 root     root          4096 May 16  2020 virtual_size
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat dev
29:0
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat mode
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat modes
U:480x800p-0
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat state
0
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat virtual_size
480,800
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# 

root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0# cd graphics
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics# ls
fb0
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics# cd f
b0
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# ls
bits_per_pixel  dev             name            stride
blank           device          pan             subsystem
console         mode            rotate          uevent
cursor          modes           state           virtual_size
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat *
16
29:0
cat: read error: Is a directory
U:480x800p-0
fbusb
0,0
0
0
960
cat: read error: Is a directory
MAJOR=29
MINOR=0
DEVNAME=fb0
480,800
root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# 

				
the config exist :
				root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# cat *
				16
				29:0
				cat: read error: Is a directory
				U:480x800p-0
				fbusb
				0,0
				0
				0
				960
				cat: read error: Is a directory
				MAJOR=29
				MINOR=0
				DEVNAME=fb0
				480,800
				root@OpenWrt:/sys/devices/platform/101c0000.ehci/usb1/1-1/1-1:1.0/graphics/fb0# 
				
actually:
just like most l33t ancient ones dont really code on a c64 anymore but use cross-platform tools (like we use the kindergarten oriented (according to some) CBMprgstudio b/c it suits us just fine for what we wanted as a starting lamer collective who did nothing64 for 30 years. Here maybe you dont wanna "vi" in terminal what you can do is type the code in xed (or whateer, geany or what you use) and then in the vocore terminal
root@OpenWrt:/# cat > test.sh
then right click to paste (after having copied to buffer ofcourse),
press ctrl-c
and your test.sh file will be whatever you typed on your hudge screen in your fav editor ... no filetransfers required (we dont know if all stuff allows it but with linuxmint/picocom you can, its really faster than scp logins or whatnot, just copy paste, ctrl c and thats it
if you're at lvl 1.5 or 2 here it shouldnt need saying but make sure you use a single arrow dont use '>>' or you will append to end of file , make sure you have a backup if needed because using '>' will overwrite it and last time we checked even forensics couldnt find the files back on a linux rm -rf
so after all that ... you might need these one time or another :
reboot
command reboot does not require connecting the terminal again but you'll get a lot of garble as it does
does what you might suspect it does but hold, hold hold and hold until it stops moving - it will say "press enter to enter console before its actually done, if you do that nothing bad happens but its gonna start scrolling after that again for a bit" (you can "right-click / open image in new tab to see full size for now") no site optimization of any kind yet
if you rekt the system (its our anti zbelling nazi filter) but not bricked the machine
firstboot -y

will reset all configuration files which is somewhat like factory default settings but not totally for more extensive info plz check the vocore site, in essence all configurations you made to startup files, network configurations and probably a lot more which we havent checked yet will be reset or removed. Its possible packages get removed too (like madplay if you use that) handle with care if you dont have backups
if you want to shut down safely
poweroff
does what you might suspect it does but hold, hold hold and hold until it stops moving - it will say someting like "reboot: System halted" , the screen will display what it was displaying (thats bc screen mem is on-screen as we understand) the leds on the vocore will go out and you can safely unplug both, a bit like unmounting or safely removing flash drives so you're site its not doing anything and you boot up into a wrecked system the next time (we didnt know that one, but the equivalent of sudo shutdown -h more or less in ash then)
on linux/bash you would use sudo apt update but here
opkg update

is used (and subsequent to install packages tho its a lot easier using LUCI web interface here ofcourse if you use terminal command you'll probably end up understanding it better)
transferring hex files or images or stuff you cant simply copypaste (on openwrt19.07.3 w/o altered config)
scp -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedKeyTypes=+ssh-rsa hex root@192.168.0.247:/tmp/

enter password and go ... we assume here no one can enter since its LAN only and anyone whos already inside can do anything anyway - thats why Mitnick always goes for local access probably hahah ... the weakest link

thats in the eye of the beholder, we seen people build mini wall-E 's from arduino+parts that listen to voice commands and one might ask : does kawai is a purpose by itself, disregarding all gremmar nazis who feel creative use of language should be banned becauce crapGPT cant wrap itself around it. Thats down to imagination. Its a router running openwrt so it can do as routers do ... but its a fully working mini pc running OpenWrt which has ash, not bash but in essence is a fully working version of linux. Other than off the top of our hat ... maybe strapping 3 AAA batteries in series with some wires and duct tape and use vocores for buttons on your jacket while running round the city with a script scanning for unprotected wifi ? Tho in 2023 any rambocop who sees someone with electrical wires protruding from its vest might shoot first and check later (somewhat understandable but still) so as stated above : these are not tutorials and we dont take responsibility for anyone in search of a Darwin Award (yes that site is still active, YOU COULD STILL GET ONE, GO FOR IT!) - or maybe put one in every room of your appartment building and route the connection through it so everyone has open wifi ? (it should be possible) and then you have like what 100 or 50 400+ mhz machines with cycles to spare which you can use to try and get lucky on mining a block of crypto if you can have a central core run the whole as a cluster ? OR you could try and get superlowpower central controller system (which is what kinda want) or whatever ... its an mp3player too and you can play doom on it (tho there havent been many AAA studios signing up to gamedev for vocore it might run VICE or something, the c64 ran at 100hz ?)
if you dont know what to do with it ... then ... euh buy one and send it to us ? thats also an option

well the endgame is in this order :
  • 1) build a time machine
  • 2) build a ufo to get to proxima for directions back to the cat star b/c we had it with this place
  • 3) if none of that works a doomsday machine (obviously) that can start a chain reaction dissolving the universe with the anti-word of god spoken in reverse the resonance that boomed the bang and makes the universe inhale at 3.3 volts and 500 milliamps ...

and in the meantime try to work it into a system with other low power parts and solar panels (we are expecting a 6502 kit from the other side of the other side of the planet - thats 5 volts too
our main goal is prevent brainrot and battle pavlov gnome, the hole and subsequent insanity from incessant poking leading to permanent mental damage over the years, not to prove something to boast about, so if you have that working fusion reactor or that FTL or warp drive that doesnt eat the universe youre presently in OR found the immovable object to draw the energy from : send us a mail
all anything subject to change without notice - the price is 490 million (exchanged to the value in suiss francs b/c the rest is clearly less stable than we are , and we are, as always since then : Janes OnderGrond, not just a doompatrol metafor
cat says we arent very zen about this and should give less fucks about those silly humans and
frankly my dear
we feel he's right again, cosmic baby resonance if you put your ear too it is about the best meds ever - there must be something to the frequency or something

phew - EOF (Syntax Error out)
nothing on this site, subsites or main site has been generated using a.i. barring temp logos like the current with cooltext.com, third party insertions like jquery or phaser are not our responsibility either. Everyone does as they want if they dont get up our arse or in our panties. Our privacy is not for sale and no one is invited to peek (if you are we'll let you know, theres no default "come in" setting). Personally though, if we feel we cant come up with a title or a page of write , a block of code and have to ask an a.i. to do it and then backpat ourselves on the good work, wed rather take a break b/c we couldnt live with the feeling that the we have insulted the gods who blessed us with the anomaly of creative forces - ... please dont submit anything written by a.i. on any of the sites either - its not like we sit scrutinizing, if you wanna cheat yourself into thinking what a great creator you are theres words for that but out of the scope, thx very much.