Pre-built images available

Hey, i have pi 3b+ but a can't find the img support it, can u show me

Unfortunately OSE still doesn't support 3B+.

See https://github.com/webosose/meta-webosose/commit/ec8766905c35071143578337a483d563ebb8503a

You should be able to boot it on 3B+ if you revert this commit, but you'll get issues with cursor in surface-manager, so GUI won't be usable at all. Patches fixing surface-manager to work correctly with newer kernel are welcome.

@jaeyoonjung FYI

thank for answering!

Hello, does somebody have a prebuilt image of webos OSE developer version?

Build #90 from [https://github.com/webosose/build-webos/commit/285c1ae45ca04b145e9a2ef454d9cbf765d01f62) finished building, new images available again on http://build.webos-ports.org/webosose/

I'll trigger build of webos-image-devel as well:

1 Like

webos-image-devel images from build #90 are available now as well.

2 Likes

FWIW, the files under the following directory are the pre-built VM images for VirtualBox emulator.
http://build.webos-ports.org/webosose/qemux86/

See https://www.webosose.org/docs/tools/sdk/emulator/emulator-user-guide/ for details.

Build #130 from [https://github.com/webosose/build-webos/commit/4a372dc5b8e4225c0e4d8a6c8bfec152d114314e] finished building, new webos-image and webos-image-devel are available again on:
http://build.webos-ports.org/webosose/

This time there are also images for raspberrypi4:
http://build.webos-ports.org/webosose/raspberrypi4

and for raspberrypi 3B+ owners I've added another image which includes 4.19.66 kernel which supports it (from https://github.com/webosose/meta-webosose/pull/16):
http://build.webos-ports.org/webosose/raspberrypi3/webos-image-raspberrypi3-master-20191023104959-4.19.66-3B%2B.wic.zip

2 Likes

Build #138 from [https://github.com/webosose/build-webos/commit/915b8611cbbf76c89c388b81e6b01d521293f4b1] finished building, new webos-image and webos-image-devel are available again on:
http://build.webos-ports.org/webosose/

for raspberrypi 3B+ owners I've added another image which includes 4.19.80 kernel which supports it (from https://github.com/webosose/meta-webosose/pull/16):
http://build.webos-ports.org/webosose/raspberrypi3/webos-image-devel-raspberrypi3-master-20191120182952-4.19.80-3B%2B.wic.zip
http://build.webos-ports.org/webosose/raspberrypi3/webos-image-raspberrypi3-master-20191120182952-4.19.80-3B%2B.wic.zip

2 Likes

The Raspberrypi 3B+ image should also work for Raspberrypi 3A+? Just tried it and stucked after the rainbow and raspberries screen.

I don't have 3A+ available. Please try to attach UART cable and let us know the output. One of the issues with 3B+ is the ethernet driver which 3A+ doesn't have, so maybe both images will work reasonably well (but wifi is more likely to work with 4B+ image than regular 4B image).

@gyeorye.lee FYI

Build #143 from https://github.com/webosose/build-webos/commit/aec2e3ff82330bae9042b6e2a9375e52f47a7544 finished building, new webos-image and webos-image-devel are available again on:
http://build.webos-ports.org/webosose/

1 Like

Build #154 from https://github.com/webosose/build-webos/commit/01a1b618c7aa17a54cb18c664a6707344b7634b6 finished building, new images are available again on http://build.webos-ports.org/webosose/

I cannot post another consecutive reply, so will be updating my last comment here..

Build #174 (v2.4.0) from https://github.com/webosose/build-webos/commit/199e974a41cea43516572320d32eac3d6df4df79 finished building, new images are available again on http://build.webos-ports.org/webosose/

2 Likes

Hi Martin Jansa,

I have tried these steps for the purpose of running webos image with qemu using OpenGL ..

  1. in step.5 instead of applying the patch, i directly changed the control-in file with the following changes.
    --enable-gtk
    --with-gtkabi=3.0
    --enable-opengl
    --enable-sdl --with-sdlabi=2.0
    --enable-virglrenderer`

and when running step.7 "debuild -us -uc -i -I" i'm facing some issues like:

#install and enable qemu-kvm.service as well as /etc/default/qemu-kvm

dh_systemd_enable -pqemu-system-common --name=qemu-kvm
dh_installinit -pqemu-system-common --no-restart-on-upgrade --error-handler=true --name=qemu-kvm
dh_installinit: --no-restart-on-upgrade has been renamed to --no-stop-on-upgrade
dh_installinit: This feature will be removed in compat 12.
dh_systemd_start -pqemu-system-common --no-restart-on-upgrade --name=qemu-kvm
dh_installinit -pqemu-guest-agent
dh_link
dh_strip
dh_compress
dh_fixperms
dh_shlibdeps
dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libvirglrenderer.so.0 (used by debian/qemu-system-x86/usr/bin/qemu-system-x86_64)
Hint: check if the library actually comes from a package.

dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libvirglrenderer.so.0 (used by debian/qemu-system-mips/usr/bin/qemu-system-mips64el)
Hint: check if the library actually comes from a package.

dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libvirglrenderer.so.0 (used by debian/qemu-system-s390x/usr/bin/qemu-system-s390x)
Hint: check if the library actually comes from a package.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/qemu-system-s390x.substvars debian/qemu-system-s390x/usr/bin/qemu-system-s390x returned exit code 25
dh_shlibdeps: dpkg-shlibdeps -Tdebian/qemu-system-x86.substvars debian/qemu-system-x86/usr/bin/qemu-system-x86_64 debian/qemu-system-x86/usr/bin/qemu-system-i386 returned exit code 25
dh_shlibdeps: dpkg-shlibdeps -Tdebian/qemu-system-mips.substvars debian/qemu-system-mips/usr/bin/qemu-system-mips64 debian/qemu-system-mips/usr/bin/qemu-system-mips64el debian/qemu-system-mips/usr/bin/qemu-system-mips debian/qemu-system-mips/usr/bin/qemu-system-mipsel returned exit code 25
dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libvirglrenderer.so.0 (used by debian/qemu-system-misc/usr/bin/qemu-system-sh4eb)
Hint: check if the library actually comes from a package.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/qemu-system-misc.substvars debian/qemu-system-misc/usr/bin/qemu-system-nios2 debian/qemu-system-misc/usr/bin/qemu-system-sh4 debian/qemu-system-misc/usr/bin/qemu-system-tricore debian/qemu-system-misc/usr/bin/qemu-system-xtensa debian/qemu-system-misc/usr/bin/qemu-system-cris debian/qemu-system-misc/usr/bin/qemu-system-xtensaeb debian/qemu-system-misc/usr/bin/qemu-system-m68k debian/qemu-system-misc/usr/bin/qemu-system-or1k debian/qemu-system-misc/usr/bin/qemu-system-unicore32 debian/qemu-system-misc/usr/bin/qemu-system-alpha debian/qemu-system-misc/usr/bin/qemu-system-microblaze debian/qemu-system-misc/usr/bin/qemu-system-moxie debian/qemu-system-misc/usr/bin/qemu-system-lm32 debian/qemu-system-misc/usr/bin/qemu-system-sh4eb debian/qemu-system-misc/usr/bin/qemu-system-microblazeel returned exit code 25
dh_shlibdeps: Aborting due to earlier error
debian/rules:179: recipe for target 'install' failed
make: *** [install] Error 255
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2
debuild: fatal error at line 1152:
dpkg-buildpackage -rfakeroot -us -uc -ui -i -I failed

I have tried editing debian/rules file using below text but also couldn't resolve it.

override_dh_shlibdeps:
    dh_shlibdeps --dpkg-shlibdeps-params=--ignore-missing-info

webOS OSE switched back to using VirtualBox, you no longer need to rebuild qemu, read https://www.webosose.org/docs/tools/sdk/emulator/virtualbox-emulator/emulator-user-guide/

Build #197 (v2.5.0) from https://github.com/webosose/build-webos/commit/83f0ce6ecd37657d8f7b03d657bbc9bedbc98215 finished building, new images are available again on http://build.webos-ports.org/webosose/

3 Likes

Hi,

Hope you are well.

Are you able to share the latest prebuilt image? Seems like the site "http://build.webos-ports.org/webosose/" is not reachable.

Would be greatly appreciated as I am keen on trying it on my Raspberry Pi 4 8GB.

Regards,

Tomas

It was back up when I looked just now.

Thank you, managed to download it. What is strange is that when I try to boot the WebOs OSE on my Pi 4 I get this error.

Boot was created using BalenaEtcher.

Any ideas/guidance?

Side Note: I have downloaded the latest Raspberry Pi OS to check that I have the latest firmware.

1 Like