Quirky Xerus 8.1.4 for Raspberry Pi2 and 3
close to getting a Nexus 7 to boot maru OS
Preetam and Tyler Martin seem close to getting a Nexus 7 to boot maru OS
https://groups.google.com/forum/#!topic ... dT_qHydRXA
However only 2013 Google version of Nexus 7 has a Slimport which is needed to
see the linux screen. Tyler says that android works on his smartphone.
He still needs to boot up the linux kernel.
Also a Sony Xperia Z3 Compact model
https://groups.google.com/forum/#!topic ... jJvMHP-_OI
https://groups.google.com/forum/#!topic ... dT_qHydRXA
However only 2013 Google version of Nexus 7 has a Slimport which is needed to
see the linux screen. Tyler says that android works on his smartphone.
He still needs to boot up the linux kernel.
________________________________________________Tyler Martin
16 Sep (20 hours ago)
That's really weird. They are definitely in vendor/asus folder.
EDIT: Figured it out. device.mk was point to vendor/asus/flo/device-vendor.mk (which doesn't exist) instead of vendor/asus/flo/flo-vendor.mk. I'll have a new build to test tomorrow.
Also a Sony Xperia Z3 Compact model
https://groups.google.com/forum/#!topic ... jJvMHP-_OI
So it looks like the HDMI monitor was connected successfully over MHL, and Maru responded by trying to start the desktop...but it failed.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Ah yes, 01micko now supports xz compressed PET packages in Slacko. Quirky only supports gz compressed PETs.don570 wrote:After investigating the bug further...
The error definitely is not the pinstall.sh script.
I came across a similar problem a couple of months ago and reported to
uextract developer
http://murga-linux.com/puppy/viewtopic. ... ced152f2d1
He said the problem was due to an old version of bash 3.0 that BarryK uses,
whereas 01micko and others have moved on to a newer version.
A simple change of a sed command solved the problem.
Here is another pet package that causes the same error message...Code: Select all
petget pmusic-5.2.0.pet gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now
It was created in Slacko which is also used by Zigbert. That may be the the culprit
That's the reason for the failure.
It is on my to-do list, to support xz-compressed PETs, dunno when I'll get around to it though.
Note, Slacko supports both gz and xz PETs, so PET creators probably should stick with gz for support for older pups and derivatives.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
OK, this is one of those things I really do need to fix, so I have.BarryK wrote:Ah yes, 01micko now supports xz compressed PET packages in Slacko. Quirky only supports gz compressed PETs.don570 wrote:After investigating the bug further...
The error definitely is not the pinstall.sh script.
I came across a similar problem a couple of months ago and reported to
uextract developer
http://murga-linux.com/puppy/viewtopic. ... ced152f2d1
He said the problem was due to an old version of bash 3.0 that BarryK uses,
whereas 01micko and others have moved on to a newer version.
A simple change of a sed command solved the problem.
Here is another pet package that causes the same error message...Code: Select all
petget pmusic-5.2.0.pet gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now
It was created in Slacko which is also used by Zigbert. That may be the the culprit
That's the reason for the failure.
It is on my to-do list, to support xz-compressed PETs, dunno when I'll get around to it though.
Note, Slacko supports both gz and xz PETs, so PET creators probably should stick with gz for support for older pups and derivatives.
The next release should allow you to install xz-compressed PETs when you click on them.
[url]https://bkhome.org/news/[/url]
Several times Rox has launched a window with no top menu bar and
the window can't be closed or moved.
I have to relaunch X windows at the start menu to fix the problem.
I never saw this problem in fatdog arm, but the version of rox
in fatdog arm has other bugs.
_______________________________________
cd to / ---> there is a lot of folders beginning with the word 'Debian'
Very strange.
___________________________________________________
Using my raspberry pi2 board I can't make alsamixer or amixer work.
When I try to launch them I get the 'No such file or directory' error.
This makes me think that they were compiled on the wrong platform.
Is the sound chip on the raspberry pi3 board different than the pi2 board??
Retrovol only shows a blank window so it's not useful.
But oddly I can get sound to play by installing my omxplayer 3.7 pet package.
It plays both sound and video files nicely.
I included the free fonts package so that subtitles will show.
download available
http://www.mydrive.ch
User: porteus@don570
Password: porteus
___________________________________________________
the window can't be closed or moved.
I have to relaunch X windows at the start menu to fix the problem.
I never saw this problem in fatdog arm, but the version of rox
in fatdog arm has other bugs.
_______________________________________
cd to / ---> there is a lot of folders beginning with the word 'Debian'
Very strange.
___________________________________________________
Using my raspberry pi2 board I can't make alsamixer or amixer work.
When I try to launch them I get the 'No such file or directory' error.
This makes me think that they were compiled on the wrong platform.
Is the sound chip on the raspberry pi3 board different than the pi2 board??
Retrovol only shows a blank window so it's not useful.
But oddly I can get sound to play by installing my omxplayer 3.7 pet package.
It plays both sound and video files nicely.
I included the free fonts package so that subtitles will show.
download available
http://www.mydrive.ch
User: porteus@don570
Password: porteus
___________________________________________________
I use the HDMI input of my TV set for video. With the default config.txt
file that is supplied I get strange in and out pulses of the video.
So I switch the config.txt file to the same one i use in fatdog arm...
The resolution is small but the screen is stable.
I need the following line to get clean audio (no stuttering)
hdmi_ignore_edid_audio=1
______________________________________________________
file that is supplied I get strange in and out pulses of the video.
So I switch the config.txt file to the same one i use in fatdog arm...
The resolution is small but the screen is stable.
Code: Select all
disable_overscan=0
start_x=1
gpu_mem=128
hdmi_group=1
hdmi_mode=4
# Safest video mode
#hdmi_safe=1
# If audio stutters uncomment the next line to output sound to stereo jack...
#hdmi_ignore_edid_audio=1
# Berryboot settings, do not change
#initramfs berryboot.img
#[pi2]
#kernel=kernel_rpi2_aufs.img
initramfs initrd.rpi2
[pi2]
kernel=vmlinuz.rpi2
# Warning: CMA does not work properly in newer firmware versions
#
#cma_lwm=16
#cma_hwm=32
#cma_offline_start=16
hdmi_ignore_edid_audio=1
______________________________________________________
To my surprise I can use my wacom tablet with quirky alpha..
I use the boot manager app to make sure that the wacom driver is loaded
and then set the preferences of mtpaint to control the pressure
(set the pen and pad to 'Screen')
and the pressure of the pen is felt...
I assume that GIMP and Blender can work with my tablet as well.
____________________________________________
I use the boot manager app to make sure that the wacom driver is loaded
and then set the preferences of mtpaint to control the pressure
(set the pen and pad to 'Screen')
and the pressure of the pen is felt...
I assume that GIMP and Blender can work with my tablet as well.
____________________________________________
- Attachments
-
- screenshot-wacom.png
- screenshot of mtpaint program
- (1.54 KiB) Downloaded 1202 times
I was able to run the XMING X server program.
Here are my instructions:
FIRST check to see if you have a connection to a windows network.
There is an icon in the tray that helps make the connection.
You can use the ping command if you wish to be sure you have a connection
to a windows computer.
-install my dropbear pet package (compiled in fatdogarm!!)
- to start dropbear
go to /etc/init.d and run ...
Note that this will have to be done each time you boot your computer
however the boot manager automatically loads dropbear at startup.
A nice feature!
On windows computer set up Xming --- it has a special app to set up the configuration.
I suggest setting Xming so that it will launch one app only, not multiple apps.
Let it run in the tray
Run putty program .
Connection > SSH > X11
Enable X11 forwarding (see image)
Fill in raspberry pi address and port 22
Then click Open
user : root
password : woofwoof
You will get message in Putty terminal that /root/.Xauthority doesn't exist
Close putty and then run Putty a second time.
This time /root/.Xauthority will exist and X GUI apps will launch
from the Putty terminal. For example type mtpaint or rox in Putty terminal.
Here is the output...
Here are my instructions:
FIRST check to see if you have a connection to a windows network.
There is an icon in the tray that helps make the connection.
You can use the ping command if you wish to be sure you have a connection
to a windows computer.
-install my dropbear pet package (compiled in fatdogarm!!)
- to start dropbear
go to /etc/init.d and run ...
Code: Select all
./S50dropbear start
however the boot manager automatically loads dropbear at startup.
A nice feature!
On windows computer set up Xming --- it has a special app to set up the configuration.
I suggest setting Xming so that it will launch one app only, not multiple apps.
Let it run in the tray
Run putty program .
Connection > SSH > X11
Enable X11 forwarding (see image)
Fill in raspberry pi address and port 22
Then click Open
user : root
password : woofwoof
You will get message in Putty terminal that /root/.Xauthority doesn't exist
Close putty and then run Putty a second time.
This time /root/.Xauthority will exist and X GUI apps will launch
from the Putty terminal. For example type mtpaint or rox in Putty terminal.
Here is the output...
- Attachments
-
- dropbear-v7-2016.pet
- New version - compiled in quirky arm
- (191.43 KiB) Downloaded 435 times
Last edited by don570 on Tue 20 Sep 2016, 15:48, edited 1 time in total.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Version 8.0.18 has been uploaded, see also link to release notes:
http://barryk.org/news/?viewDetailed=00411
I cracked the wifi problem, happily posting from my Pi3 right now!
The big surprise for 8.0.18 is.... Libreoffice
The bluetooth problem might be cracked too, haven't tried yet.
http://barryk.org/news/?viewDetailed=00411
I cracked the wifi problem, happily posting from my Pi3 right now!
The big surprise for 8.0.18 is.... Libreoffice
The bluetooth problem might be cracked too, haven't tried yet.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Note that Bluetooth is still not working in 8.0.18.
I thought that I had fixed it, but not so. I have posted a report:
http://barryk.org/news/?viewDetailed=00413
So, hopefully in the next release.
I thought that I had fixed it, but not so. I have posted a report:
http://barryk.org/news/?viewDetailed=00413
So, hopefully in the next release.
[url]https://bkhome.org/news/[/url]
In my experience, the wifi configuration is not ‘sticky’ from session to session. After scanning and establishing a profile, it functions well. But when I turn off the computer and reboot, the connection information has been lost. Right-clicking the network icon brings up the connection dialogue window.
The prior established profile is listed, but ‘Connect Now’ does not re-establish the connection. I had to again click on ‘wlan0’ , rescan, choose my router and enter my password to get a connection.
Another problem I stumbled into was with the Quirky Package Manager. On clicking ‘Update now’, the manager seemed to do its thing, going to each repository and downloading the current package list, and then arranging the info into a usable format. However the process was faster than usual.
But when I looked for some common packages (e.g. Chromium, HPLIP) they could not be found. So I looked into the database folders at /root/.Packages/Packages-ubuntu-xenial-main (and xxx-multiverse and xxx-universe). Although, in ROX-Filer the directories were labled in boldface fonts as if they had fresh content, they were EMPTY. However the database folders for /root/.Packages/Packages-pet-armv6-official (and xxx-noarch-official and xxx-xerus-official) all had reasonable content. I verified that I was connected to the internet during this process.
For some reason, the package list for the Ubuntu repositories doesn’t seem to be updating.
The prior established profile is listed, but ‘Connect Now’ does not re-establish the connection. I had to again click on ‘wlan0’ , rescan, choose my router and enter my password to get a connection.
Another problem I stumbled into was with the Quirky Package Manager. On clicking ‘Update now’, the manager seemed to do its thing, going to each repository and downloading the current package list, and then arranging the info into a usable format. However the process was faster than usual.
But when I looked for some common packages (e.g. Chromium, HPLIP) they could not be found. So I looked into the database folders at /root/.Packages/Packages-ubuntu-xenial-main (and xxx-multiverse and xxx-universe). Although, in ROX-Filer the directories were labled in boldface fonts as if they had fresh content, they were EMPTY. However the database folders for /root/.Packages/Packages-pet-armv6-official (and xxx-noarch-official and xxx-xerus-official) all had reasonable content. I verified that I was connected to the internet during this process.
For some reason, the package list for the Ubuntu repositories doesn’t seem to be updating.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Yes, I also had that problem. I investigated and have fixed it for Simple Network Wizard. This is for my wireless network, phone as hotspot.eowens2 wrote:In my experience, the wifi configuration is not ‘sticky’ from session to session. After scanning and establishing a profile, it functions well. But when I turn off the computer and reboot, the connection information has been lost. Right-clicking the network icon brings up the connection dialogue window.
The prior established profile is listed, but ‘Connect Now’ does not re-establish the connection. I had to again click on ‘wlan0’ , rescan, choose my router and enter my password to get a connection.
Tested a few times, reboot, it reconnects.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Version 8.0.18 is massive, 388MB, big by Puppy standards.
There is lots of dead wood in there, have already brought it down to 348MB for the 8.0.19 build. Should be able to knock off quite a bit more.
Are any of you guys familiar with using Bluetooth mouse and keyboard?
I now have bluetooth pairing working after a reboot, for my mouse.
However, I have to power-on the mouse after Quirky has booted up. If I turn on the mouse before turning on the Pi3, the mouse is not detected.
Is this the expected behaviour?
There is lots of dead wood in there, have already brought it down to 348MB for the 8.0.19 build. Should be able to knock off quite a bit more.
Are any of you guys familiar with using Bluetooth mouse and keyboard?
I now have bluetooth pairing working after a reboot, for my mouse.
However, I have to power-on the mouse after Quirky has booted up. If I turn on the mouse before turning on the Pi3, the mouse is not detected.
Is this the expected behaviour?
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
don570 wrote:Several times Rox has launched a window with no top menu bar and
the window can't be closed or moved.
I have to relaunch X windows at the start menu to fix the problem.
I never saw this problem in fatdog arm, but the version of rox
in fatdog arm has other bugs.
_______________________________________
cd to / ---> there is a lot of folders beginning with the word 'Debian'
Very strange.
___________________________________________________
Using my raspberry pi2 board I can't make alsamixer or amixer work.
When I try to launch them I get the 'No such file or directory' error.
This makes me think that they were compiled on the wrong platform.
Is the sound chip on the raspberry pi3 board different than the pi2 board??
Retrovol only shows a blank window so it's not useful.
Perhaps you have installed something that has messed things up.
I have just booted up my 8.0.19 build on the Pi2, which is the same as 8.0.18 as far as sound is concerned, I think.
alsamixer and amixer both work.
Right-click retrovol and the mixer window shows two level controls.
I have never had the problem of windows launching without the title-bar etc. I am testing every day on both Pi2 and Pi3.
[url]https://bkhome.org/news/[/url]