[Dec 07] DietPi(v6.18) - Pinebook / Manjaro KDE (preview3) / Manjaro LXQT (preview3) - Pinebook |[Dec 06] Armbian Debian Stretch (5.67) / Armbian Ubuntu 18.04 Bionic Desktop (5.67) - RockPro64 |[Dec 05] DietPi(v6.18) - 1080P Pinebook | [Nov 28] Slackware Aarch64 Miniroot (20181126) / Slackware Aarch64 XFCE (20181126) - RockPro64 / Manjaro KDE (preview3) / Manjaro LXQT (preview3) /Q4OS (2.6-r6) - 1080P Pinebook

Project Inspiration | Get Started | IRC Logs | Forum Rules/Policy


[28/03/2017] openSUSE Tumbleweed Images for Pine64
#1
[Image: rwMBVAb.png]
Changelog

27/4/16

- Initial release
- Kernel based on 3.10.65-7-pine64-longsleep-28

8/5/16

- Kernel updated to 3.10.101-0-pine64-longsleep-39
- Changed ownership of /home/pine64 to the pine64 user so that you can download/create/edit your stuff in it
- Changed hostname to pine64

3/10/16

- Kernel updated to 3.10.102-3-pine64-longsleep-98
- Image has been rebuilt from the ground up.
- All software has been updated.
- Includes the pine64-config tool

7/12/16

- Kernel updated to 3.10.104-1-pine64-longsleep-103
- All software has been updated.
- Image with LCD support (but with no touchscreen capability) is now available

28/03/17

- Kernel updated to 3.10.105-0-pine64-longsleep-3
- All software has been updated.
- SoPine images are now available

Downloads

Direct download from the project page

Login details

Username: pine64
Password: pine64linux

Root password: pine64root

Known bugs and Workarounds

Currently, there is no known bugs in the latest image.

If you can come out with a fix for any problems whether or not they are listed here or if you found new bugs, post them on this thread so that I will be able to patch the image and the entire community will benefit.
Donate BTC: 3Eav9uqXi8Nx1axb7QjK6xV4km4K9YGv9a
Reply
#2
Amazing ! will give this a go straight away :Smile does it come with a desktop environment ?
  If you manage to click this link you'll join in the IRC channel
Reply
#3
(04-27-2016, 06:09 PM)Luke Wrote: Amazing ! will give this a go straight away :Smile does it come with a desktop environment ?

No. Not yet. I am planning to include it in later builds.
Donate BTC: 3Eav9uqXi8Nx1axb7QjK6xV4km4K9YGv9a
Reply
#4
Created new openSUSE forum section and now move the thread over.
Reply
#5
(04-28-2016, 12:04 PM)tllim Wrote: Created new openSUSE forum section and now move the thread over.

Plain wrong. Think about removing all these crap OS images from the wiki and feature max 1 or 2 OS images (maybe 3 by dropping Android support and solely rely on RemixOS). It would help.
Reply
#6
(04-28-2016, 03:32 PM)tkaiser Wrote:
(04-28-2016, 12:04 PM)tllim Wrote: Created new openSUSE forum section and now move the thread over.

Plain wrong. Think about removing all these crap OS images from the wiki and feature max 1 or 2 OS images (maybe 3 by dropping Android support and solely rely on RemixOS). It would help.

I don't think that will help. Also, not all of the images are crap. We have all these different OS images to cater to the preferences of different groups of users. We can't force the users to choose only between 1 or 2 distributions. The more distributions we can get to run on the Pine64, the better because it will allow users to use the Pine64 with minimal need to relearn on how to use the system.
Donate BTC: 3Eav9uqXi8Nx1axb7QjK6xV4km4K9YGv9a
Reply
#7
(04-28-2016, 03:32 PM)tkaiser Wrote:
(04-28-2016, 12:04 PM)tllim Wrote: Created new openSUSE forum section and now move the thread over.

Plain wrong. Think about removing all these crap OS images from the wiki and feature max 1 or 2 OS images (maybe 3 by dropping Android support and solely rely on RemixOS). It would help.

I don't agree.
The more, the merrier, in this case.
Everyone has their own preference, and Linux all about choice.
Reply
#8
(04-30-2016, 07:29 AM)nomadewolfThe more, the merrier, in this case. Wrote: The more, the merrier, in this case.
Everyone has their own preference, and Linux all about choice.

Where's the point to hack together another crappy OS image if there are development tasks that need real attention? Less is more in this case and instead of producing 'just another Linux thing' real devs should start to do real work.

As an example for such an aforementioned crappy OS image let's have a look at this featured Ubuntu OS image: http://wiki.pine64.org/index.php/Pine_A6....2C_Pine64

I've no idea who created this image and why since it just sucks completely. It's already outdated (both kernel and u-boot need updates but since there's no documentation no user of these images does even know that there are necessary updates available!). Since the history is not cleared we can have a look what's different between this 1.8 GB image and longsleep's 160 MB original:

Code:
[email protected]:~$ history
   1  bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh)
   2  sudo bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh)
   3  su
   4  sudo curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh
   5  ls
   6  sudo  curl https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh
   7  ls
   8  sudo curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh > uboot.sh
   9  ls
  10  ls -a
  11  sudo chmod 755 uboot.sh
  12  uboot.sh
  13  ./uboot.sh
  14  sudo ./uboot.sh
  15  sudo curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh > uboot.sh           go
  16  sudo curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_kernel.sh > kernel.sh
  17  sudo chmod 755 kernel.sh
  18  sudo ./kernel.sh
  19  sudo reboot
  20  sudo apt-get update
  21  sudo resize_rootfs.sh
  22  df -h
  23  sudo apt-get upgrade
  24  sudo apt-get install xbuntu
  25  sudo apt-get install xubuntu
  26  ls
  27  cd /etc
  28  ls
  29  cd apt
  30  ls
  31  vi ./sources.list
  32  ls
  33  cd
  34  sudo apt-get install ubuntu
  35  sudo apt-get update
  36  sudo apt-get install xubuntu-desktop
  37  sudo reboot
  38  ls
  39  mv uboot.sh update-uboot.sh
  40  mv kernel.sh update-kernek.sh
  41  sudo apt-get update
  42  sudo apt-get upgrade

Obviously only the xubuntu-desktop package has been installed and the image has been resized from 3.8 to 8 GB for whatever reasons. And 2 of longsleep's update scripts have been put (renamed wrongly) in ubuntu's home:
Code:
-rwxr-xr-x  1 ubuntu ubuntu 1877 Apr 21 04:09 update-kernek.sh
-rwxr-xr-x  1 ubuntu ubuntu 2261 Apr 21 04:08 update-uboot.sh

So why is there a 'need' to create an outdated 1.8GB ubuntu image? Ah, Desktop environment, of course. X-Windows, this sort of stuff. With a kernel that's only able to drive displays with 1080p60 Wink 

We do have 2D acceleration already available for this Ubuntu image (provided also by longsleep as an launchpad PPA that already added to this image). So why the heck are the two necessary packages NOT installed already?! It takes an additional 
Code:
sudo apt-get install libump xserver-xorg-video-fbturbo
to get the available 2D acceleration. How many users know this?! This is developer's work thrown in the bin!

Next issue: HW accelerated video decoding: We have this available/useable since the Mid of March. The kernel features are ready so why isn't a movie player included that makes use of libvdpau-sunxi to get true HW acceleration? Why is 'export VDPAU_DRIVER=sunxi' missing in an approriate start script? What's the purpose of a desktop image that doesn't make use of developer's hard work to get HW acceleration running?

Next issue: Networking troubles when using more than one Pine64:
Code:
[email protected]:~# cat /boot/uEnv.txt
console=tty0 console=ttyS0,115200n8 no_console_suspend
kernel_filename=pine64/Image
initrd_filename=initrd.img
ethaddr=8e:21:0d:2e:ad:67

The  'ethaddr' line must not exist in uEnv.txt when providing an OS image! The value here has to be calculated randomly on first boot and then used to provide unique MAC addresses on all Pine64 in the network. With this image you get already in ARP/network troubles when used with more than one device.

At this point I already got so sick of this image and stopped testing. The other Ubuntu OS image featured in the wiki is known to contain even more mistakes. Why should this change when people start to combine just another boring arm64 Linux rootfs with longsleep's real work?

There are so many unresolved issues and any further fragmentation (both 'community wise' and regarding available OS image variants) will prevent resolving them. And my main argument against any more OS image is that their announcements/documentation always suppress necessary information.

All these OS images are based on the linux-sunxi community's and longsleep's work. For all of the OS images the limitations he clearly wrote apply (eg. http://forum.pine64.org/showthread.php?tid=376). Not also providing the list of limitations with another OS image is simply fooling users (have a look through the forums how many people think their Pine64 is DOA simply because the kernel each and everyone uses at the moment does not negotiate a display when it's not 1080p60)

If you want to do something useful look at enabling Bluetooth, build mpv/mplayer packages that make use of HW accelerated decoding (less OS images --> less packages!), look into the HDMI issues, package the necessary fixes to GPIO libraries and so on. There's so much real work to do!
Reply
#9
(05-01-2016, 10:15 AM)tkaiser Wrote:
(04-30-2016, 07:29 AM)nomadewolfThe more, the merrier, in this case. Wrote: The more, the merrier, in this case.
Everyone has their own preference, and Linux all about choice.



If you want to do something useful look at enabling Bluetooth, build mpv/mplayer packages that make use of HW accelerated decoding (less OS images --> less packages!), look into the HDMI issues, package the necessary fixes to GPIO libraries and so on. There's so much real work to do!

Couldn't have said it better myself. There is a lot to be said for the diversity of linux, in a pure environment. Where all is OSS. We dont have that, we have a tainted environment with binary blobs we are forced to live with at this time. You can wrap every flavor of linux you want around these blobs, but what we need is a unified force trying to get a functional OS. Right now we have everyone wanting to do things their own way. Everyone wants to support pine at a different site, everyone wants a different OS. Right now linux is a MESS on this device in part due to the lack of focus. Think of it like a cup of coffee, longsleep has built a good core, functional tools etc. but we have a lot of half hearted attempts at wrapping various linux flavors around it that then seem to get dropped. 

Lets try to pick a distro and focus until we get the basic functionality nailed. In the meanwhile if someone wants to create a build of their own fav linux, please make sure you are going to be at least as committed as longsleep is to helping and providing ongoing support and arent creating another also-ran orphan build.
Reply
#10
Hey guys, the openSUSE image has been updated.

Full changelog:

- Kernel updated to 3.10.101-0-pine64-longsleep-39
- Changed ownership of /home/pine64 to the pine64 user so that you can download/create/edit your stuff in it
- Changed hostname to pine64

Links are in the first post.

In the next release, I am planning to integrate longsleep's tools into the image. To do so, I will be needing a hosting provider for me to host the rpms that I will be generating out so that the installation of the tools will be easy (any suggestions?).
Donate BTC: 3Eav9uqXi8Nx1axb7QjK6xV4km4K9YGv9a
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  GUI on openSuSE joaoreino 10 2,073 01-23-2018, 09:00 PM
Last Post: tmechanic

Forum Jump:


Users browsing this thread: 1 Guest(s)