Hi
I want to transfer my own windows ce 6.0 os design to a htc prophet ?
Is it possible?
I found a nk.bin file in os release dir. is it the same as nk.nbf or it needs something to be added to it like ipl/spl?
No.
Let me just verify that I understand you correctly:
You have Platform Builder for Windows CE (not Mobile) 6 and you compiled and OS.
Now you want to put it on your Prophet?
Here is why this can not work:
a) You do not have the hardware drivers. Even if by some miracle you got the Prophet BSP (board support package) from HTC, because CE 6 architecture is so different from CE 5 on which the BSP is based you would have to rewrite them.
b) The nk.bin Platform Builder produces is in plain binary format. The nk.nbf which the Prophet bootloader can recognize is in HTC's special encrypted format so the bootloader will not read the bin.
Yes. You get it right. I know if I want to use phone features completely I need BSP. But what if I want just use some standard features? just LCD and phone features.
Also I saw nbftool that decrypt and encrypt nbf files. Can I use it to encrypt files for prophet?
You need BSP for everything, not just "full features". Every little bit of hardware that connects to the CPU requires a driver unique for your device, that includes the screen, the digitizer (touch screen), hardware keys, USB port, SD card, etc.
This is why the Linux project for these devices hasn't moved beyond booting the kernel.
There are tons of work to be done (not to say it is impossible).
I am not sure about the nbftool but even if you manage to create an image that boots best case scenario is you will see something on the screen.
But you will have no way of controlling the device - no touch screen or keys, and no way to connect to it from windows since you do not have USB drivers.
Then what are the BSPs which exist in Wince by default. There is a ARMv4. How can I use it? Can you help me?
There is ARMv4 and there is Samsung, TI, Xscale, etc. Unlike x86 - all are different. Different memory map, different GPIO, different periferials.
Better waste your time on something else. Anyway CE 6 does not have phone features at all. Compile it for your PC and see that yourself.
mamaich said:
There is ARMv4 and there is Samsung, TI, Xscale, etc. Unlike x86 - all are different. Different memory map, different GPIO, different periferials.
Better waste your time on something else. Anyway CE 6 does not have phone features at all. Compile it for your PC and see that yourself.
Click to expand...
Click to collapse
I think ARMv4 BSP in Platform Builder already have enough driver for this type of CPUs. And HTC phones are ARMv4. So normaly I should be able to build and transfer my OS to there. CE 6 have buitin drivers for modem,LCD and so on. But there is no phone. Because phone is an app that runs on CE. So if I just want to use devices like modem It is enough. The problem is nbf files ae encrypted and os.bin file should encrypt to os.nb and then transfer to device.
shariat said:
I think ARMv4 BSP in Platform Builder already have enough driver for this type of CPUs. And HTC phones are ARMv4. So normaly I should be able to build and transfer my OS to there. CE 6 have buitin drivers for modem,LCD and so on. But there is no phone. Because phone is an app that runs on CE. So if I just want to use devices like modem It is enough. The problem is nbf files ae encrypted and os.bin file should encrypt to os.nb and then transfer to device.
Click to expand...
Click to collapse
you dont really understand the problem.
ARMv4 is not a cpu, it is the ARM version 4 instruction set ....
afaik your phone has some kind of OMAP.
i don't know if CE6 has a BSP for that, but even if it does, it will still not work without modifications.
a recent example. a friend of mine wanted to download a generix xscale 25x eboot (bootloader) to a device that had xscale 255. he almost killed the whole device because the RAM memory map of this generic eboot managed to overlap with the device's original bootloader memory space in ROM. (the virtual memory mapping differed in such an unlucky way.) and so the device's own bootloader thought it had to flash it in instead of loading it into RAM and it overwrote part of itself. luckily only the splashscreen got damaged...
(and of course the device would not boot this eboot.)
that's what happens when someone who has not ever dealt with hardware and memory mappings (i.e. you) tries to play with platform builder and flashing.
also, what is this about CE6 having built in drivers for the modem (you mean GPRS?) and LCD. it doesn't have the correct ones for your device.
and, the phone is more than just an app, it also needs drivers. the modem needs it too.
all in all...i strongly discourage you trying to flash that nk.bin.
it is not even in a format that your bootloader will understand, it is MS BIN format. the nk.nb0 in same release dir (or if there is none then cvrtbin will convert it) will be the raw format that needs to be encoded for nbf, but that is far from enough because it will never boot anyway. so forget this info.
cmonex said:
you dont really understand the problem.
ARMv4 is not a cpu, it is the ARM version 4 instruction set ....
afaik your phone has some kind of OMAP.
i don't know if CE6 has a BSP for that, but even if it does, it will still not work without modifications.
Click to expand...
Click to collapse
But at least the way of using loader is possible. Like how Linux is loaded
shariat said:
But at least the way of using loader is possible. Like how Linux is loaded
Click to expand...
Click to collapse
loader, for what purpose?
cmonex said:
loader, for what purpose?
Click to expand...
Click to collapse
For running WinCE , like Linux. Am i right? Linux devs uses Loader to load Linux on Mobile devices. I think I am confused. Help me on this. My purpose is to use my own OS design.
shariat said:
For running WinCE , like Linux. Am i right? Linux devs uses Loader to load Linux on Mobile devices. I think I am confused. Help me on this. My purpose is to use my own OS design.
Click to expand...
Click to collapse
well, for linux, the drivers have to be written too. (most of the time there are existing ones with source available that can be modified, though.)
so it is more complicated than that.
shariat: writing your own OS for this hardware is not impossible, but is not easy.
I suggest you go away for a while and get hold of platform builder and an arm reference guide and read everything you can about the device, the memory structure, your dedicated hardware structure, and then start writing.
Knowing how the hardware and CPU operate is fundamental to the OS you will write. Platform Builder will give you some source code access and help give you some ideas.
This is a nearly impossible task for a hobbyist coder. I'm sure people will help you, but you need to discuss what you have in mind.
Have a look here for some other easier ideas:
http://simpleos.iroot.ca/index.php
V
Link:
http://bbs.phoenixstudio.org/en/showthread.php?tid=5616
Update details
This version is 64bit with Kernel 4.9
Add Multiboxing feature（The feature allows you to create a duplicate of an app. The duplicate and origin one run separately with independent data and resources. All data in the duplicate will be erased after it's eliminated while data of the original one is still there.)
The screen problem cause by Nvidia Graphics card has been fixed.
Improve compatibility.
Update pre-installed apps
Support OTA
The keyboard mapping will automatically suspended while you're entering text.
1. Thanks. Every things work fine. Only missing GApps . Is there any way to install them?
2.I installed via exe file. I want to use my computer with tv via HDMi. My laptop is a few year old and it is BIOS, not UEFI. How I can Off nativ screen ( mylaptop screen)? I want to use only mt Tv as my main screen.
I have installed phoenix on hdd on tablet with intel atom x5 and intel hd graphic, UEFI Secured boot disabled, i choose phoenix from boot, after writing '' search phoenix os ... found on sdaetc.etc. '' The screen gets black and blocks everything, can you help me? sorry for my bad english
Lost sound with update
Hi Guys. After days of setting up my cheap X86_64 Chuwi Android box to run PhoenixOS and windows and to boot normally I lost sound after update. I had the hacked 2.0.1 version with gapps and root from a forum on the PhoenixOS website. Sorry I can't post links yet. So somehow someone got sound to work on this device but not sure how they did it. Windows says my soundcard is a Intel SST Audio Device (WDM). So now I have 2.0.2 but no sound. . Any Ideas?
Hey , where to download 2.0.2 32bit ? 64 bit is not working for me , same Problem like remix 64, blisspop 64 and all other Android x86_64 ... Just looping before bootlogo. I dont understand why becorse win 7 and 10 64 also working fine like of all Android x86 32. thanks
Version 2.0 is available for 32b
@wizmart
I know but 2.0.0 is not the same as 2.0.2 i will try it today , but i dont understand why 64 bit is looping while win 64 is working. I hope soon every New Version would be arriveable AS 32 bit , many people i know only can use 32 bit on older PCs.
stucks at a black screen..seems to be a bootloop on my laptop..(amd a4-6210)
tried dual booting with ubuntu and windows..same result
but boots fine on my computer with intel i3 and nvidia card!
can anyone tell me what is the problem and if there is a 32 bit version that will work? i need this for development processes!
I have new instructions here that are much better, but require some amount of software compiling (mainly with the kernel): https://forum.xda-developers.com/iconia-a500/linux-acer-iconia-tab-a500-2020-edition-t4136023
I'm a latecomer to the scene of seeing GNU/Linux userland distros run on this tablet, as I only acquired mine from a friend since last year, and couldn't use it until I replaced the ac adapter and battery. I was this lucky as Android devices capable of running GNU/Linux distros natively are hard to come by, and moreso for getting it for free. But first, the tablet needed to be fixed up by software:
I upgraded the stock Android OS from 3.?.? to 4.0.3 by downloading Acer-provided updates to a microSD card.
Now I could retrieve the tablet's serial number and generate the SBK from it in order to flash Skrillax_CZ's custom bootloader with nvflash.
I flashed CWM 6.0.4.5 custom recovery first (to AKB partition), then OmniROM based on Android 4.4.4 (to LNX partition). I flashed an Open GApps package at first, but I had to remove it as those apps try to utilize the NEON extensions that this tablet's CPU lacks, causing them to crash. (4.4 is the minimum version the Open GApps supports anyways) Instead, I used F-Droid for an app store replacement, which sufficed for most of my needs.
Then I got to flashing a kernel that enables booting native Linux distros (to SOS partition). While I tried both sp3dev's 2.6.38 kernel and rogro82's 3.1.10 kernel (a modded version that loads the distro from the 2nd partition of a microSD card), I stuck with the 3.1.10 kernel, as it included the ASIX AX8817X USB 2.0 Ethernet driver which allows me an alternate method of internet connection in case I couldn't use wi-fi (both boot images are attached for preservation and convenience, renamed).
Now I was ready to experience running Linux distros natively on a mobile device for the first time. :fingers-crossed: From this point on, I would be using rootfs images to reach this dream of mine. With the new instructions posted above, I may have finally realized this dream! While I have more stuff working smoothly (Wi-Fi and Bluetooth, 2D software acceleration), other minor things are still not, including the camera and 3D acceleration (due to such support not existing in mainline kernel).
Some notes I made for this time period:
I have found out that glibc versions 2.24 and later have removed support for Linux kernel versions < 3.2, which limits the choice of distros I can select from without additional work.
The minimum Linux kernel version that this version of the GNU C Library can be used with is 3.2, except on i[4567]86 and x86_64, where Linux kernel version 2.6.32 or later suffices (on architectures that already required kernel versions more recent than 3.2, those requirements remain unchanged). Linux 3.2 or later kernel headers are required on all architectures.
Click to expand...
Click to collapse
The workarounds to this are to use an alternate C library, or use older versions of glibc (Version 2.23 is used in Ubuntu 16.04, but it is compiled to only run with Linux 3.2 or later, so it must be recompiled by lowering the minimum kernel version to 2.6.32).
The file bcm4329-fullmac-4.bin can be found in packages of linux-firmware, but bcm4329-fullmac-4.txt needs to be obtained from the stock Android OSes, as the file "/system/etc/wifi/bcmdhd.cal" (original file attached for convenience, renamed).
Linux kernel version 3.1.10 is the latest one provided by NVIDIA, and new versions are unlikely to be ported to this tablet's CPU, according to https://developer.nvidia.com/linux-tegra-rel-16.
Other than the above three points, Linux distros will work almost flawlessly, but if the screen is turned back on, an external keyboard is needed to switch to one of six virtual terminals by using Ctrl+Alt+[1-6], and then switching back to Ctrl+Alt+7, where 7 may be replaced if the GUI is running in another virtual terminal location. This process is not needed if the NVIDIA proprietary drivers are being used, which can be found on this page: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-tegra/16.3-0ubuntu2/+build/4804631 (Beware that X11 ABI versions > 14 are not supported, so downgrade the xorg version somehow to the 1.14.x series to use this driver).
[Version 16.3] is the final release supporting Ventana. T20 support will not be included in future releases.
Click to expand...
Click to collapse
The internal storage is also detected by the kernel, but its contents cannot be normally accessed, as it has a special partitioning scheme that cannot be recognized. It is possible to format it, and partition it to hold accessible data, but I recommend not doing any partitioning for it, as it may require a longer restoration process that will not be explained here for now. However, using TestDisk to search for partitions using the GPT partitioning scheme allows four of them to be accessible. I recommend only copying data from those partitions; writing the detected partitioning scheme is risky for now.
Putting the tablet to sleep by use of pm-utils works, and the tablet will even power back up after the power button is pressed, but it may cause the BCM4329 SDIO card to stop working until the next reboot.
Any programs that utilize OpenGL during their operations are very likely to have poor performance, and will remain so, as this tablet model's GPU only supports OpenGL ES and EGL :crying: , unless those programs are altered by source code to include support one of these two APIs. Additionally, some colors may appear to be off during any OpenGL rendering (e.g. orange is rendered blue) However, the proprietary drivers may help with faster OpenGL ES and EGL rendering, but still, most programs are unable to utilize them.
I guess I can be blamed for sticking with too old hardware; people are moving onto newer hardware so quickly! However, there's still hope for having some sort of Linux tablet, but the road to getting there is not easy.
NEW: I have successfully cross-compiled this Linux 3.17.0-rc7 kernel, using the picasso config from rogro82's kernel source. When compiling this kernel, do not switch to any other branches, or prompts like this will appear upon invoking make:
Code:
Patch physical to virtual translations at runtime (ARM_PATCH_PHYS_VIRT) [N/y/?] n
Physical address of main memory (PHYS_OFFSET) [] (NEW)
I also created a boot image for it, but after flashing it, attempting to boot results in the bootloader being stuck at the loading screen, without hope for anymore activity unless powered off by force. Even inserting an initrd will not change anything but the size of the boot image (Max size for the SOS partition is ~5MB). :crying: This also seems to have happened a version of the 2.6.38 kernel from sp3dev that I have self-compiled, but that one was without an initrd. Either I'm not using the correct toolchain (I'm using the ones provided from the Ubuntu repositories), or non-manufacturer-provided kernels don't have the special code to support this tablet model. However, I really want to get this kernel to boot successfully, so that newer distro versions can be used (my results will appear in another post).
Supported Distros
Almost any distro will work out-of-the-box (OOTB), but some require software-level modifications that can only be done on a real armv7-based device or emulation, so here is a list of distros whose latest stable versions have an arm build, can successfully boot up, use glibc <= 2.23, and their image locations (all of them can at least boot to a terminal login screen, if a graphical desktop environment is not preinstalled, but this will require use of an external USB keyboard):
Devuan 1 Jessie (Mirrors for this distro are located in the directory "devuan_jessie/embedded/")
Slackware ARM 14.2 | http://ftp.arm.slackware.com/slackwarearm/slackwarearm-devtools/minirootfs/roots/
CentOS 7 | http://mirror.centos.org/altarch/7/isos/armhfp/
openSUSE Leap 42.3 | http://download.opensuse.org/ports/armv7hl/distribution/leap/42.3/appliances/
Unfortunately, for some reason, the BCM4329 wi-fi works OOTB only with older versions of some distros, including these:
Devuan 1 Jessie (already listed above)
Debian 8 Jessie and older (supported until May 2020)
Ubuntu 14.04 Trusty Tahr and older (supported until April 2019)
On newer versions of these distros, if I was able to boot them successfully, they will work, but when running
Code:
iwconfig wlan0 txpower auto
it results in input/output errors that are meaningless, and the kernel messages do not really help that much, even when using the supplied nvram file (do I need to get a different one, or support had been dropped entirely for this card?) For these cases, USB ethernet adapters are the only way to get an internet connection to this tablet model. I have never been able to get Bluetooth to work, unless I missed some other task that I have not yet heard of.
NOTE: To remove the root password, use this command on a Linux/BSD/other Unix OS:
Code:
sed -i 's/root:x:/root::/' /etc/passwd
"/etc/passwd" can be replaced with another location if needed. "/etc/fstab" may also need to edited to reflect the partition layout of the microSD card that a selected distro is installed to.
OOTB distro support for this tablet model is very limited at this time; support for it seems to be being dropped implicitly , unless I can compile and successfully get a newer kernel version to boot up. DistroWatch.com lists many more, but older versions of most distros will most likely have to be used. It's better to use the versions that are still supported, for that they will still receive software and security updates occasionally.
booted up slackware rootfs using thor2002ro installer successfully
Potential new kernel source
See the bottom of the first post for more information about this.
I'm working on trying to get us a newer kernel version than the NVIDIA-provided 3.1.10 one, located at https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git/. This one is at 3.17.0-rc7. It's better in that comes straight from kernel.org, the official source of Linux kernel releases. However, its last update was from 09/28/2014, so while it is considerably newer than manufacturer-provided sources, it's not as new as the 4.x series (I'm not sure if I'm even willing to try compiling this series due to the age of this tablet model's hardware), but at least this will allow the tablet to successfully boot up newer distro versions. The issues with the BCM4239 card are likely to carry over here, but I can compile more drivers, either built-in to the image, or as modules that need to be added to a rootfs. Doing this will open up more alternate methods of getting an internet connection, such as by USB wi-fi/cellular adapters, or by USB RNDIS tethering. For reference, here are the current two 3.x release series, both of which are receiving updates as long-term support series:
3.16.x, supported until April 2020.
3.2.x, supported until May 2018.
That means in about two more years, this tablet model will effectively reach its end-of-life.
Do not flash the boot image attached here; it does not work yet. All of the attachments are provided for analysis, as they need more work before becoming usable. I try to learn most things on my own, but some things are not obvious to me as to what I should, so I need all the help I can get so that we can load new distro versions and give life to the remaining of these tablets for a few more years. At most, CentOS 7 is supported until June 2024 (enterprise-oriented distros tend to be supported for unusually longer amounts of time), if older kernels versions must be used or I fail to get this new kernel working at all, so this will be our only supported option if we can't get a new solution by the 1st half of 2020.
i found a thread with step how to install wifi drivers on deb-based distros
https://forum.xda-developers.com/showthread.php?t=1782549
we need packages: broadcom-sta-common broadcom-sta-source firmware-b43-installer firmware-b43legacy-installer b43-fwcutter
(i never tried it, idk if it even works)
still pursuing this project?
not sure if you are still pursuing this but if you are i would like to help
Aaron
adconway said:
not sure if you are still pursuing this but if you are i would like to help
Aaron
Click to expand...
Click to collapse
Yes, I'm still looking for people to help me with this; it will happen for as long as I own this tablet model; I haven't made much progress as I haven't found enough people to help me. It's good that you would like to help me.
Hi!
Sorry for the noob question folks...
I really would like to try some linux distros on this tablet, I have the Skrillax_CZ's custom bootloader installed, also the latest OmniROM but how can I install / boot a linux distro?
Thank you!
Ladislav
The kernel that I used expects the root file system to be on
Code:
/dev/mmcblk1p2
. Images for the Raspberry Pi are usually formatted with two partitions: one containing the boot files; the other containing the actual filesystem. The latter is what the kernel expects to read.
I've been hoping for a thread like this since I wasn't getting anywhere with my own old A500. With Google support flaky as ever on my tablet, I've been itching to remove it entirely for a Linux distro. When I get time, I would love to tinker with the materials you've shared, Worldblender.
Do someone have headers for kernel 3.8.13.20-digetx-thor-01232-gfe12f92?
2019 Status
Finally, I've decided to try again to get something a little more recent onto here. Ubuntu 16.04 and one flavor, Ubuntu MATE 15.04, can currently be run. Ubuntu Mate is an Ubuntu flavor shipping with the MATE desktop environment, and the only flavor to produce images for the Raspberry Pi, hence their partition layout is compatible with the 3.1.10 kernel image.
Here's what I went through today (all versions require editing /etc/fstab to disable mounting of the first partition for them to complete booting. To get Wi-Fi working, use the text file from the very first post of this topic, and place it in the same location (/lib/firmware/brcm); no need to copy the BIN file as it will already be present on the images):
Ubuntu MATE:
15.04: Only version that successfully boots out-of-the-box. Unsupported version. Use this image for now, as all others listed here don't work out-of-the-box.
15.10: Crashes with a kernel panic. Unsupported version.
16.04: Crashes with a kernel panic. Requires replacing the libc6 package and everything that directly depends on it with the ones from 15.10. Supported until April 2021. Glibc version 2.23 is in 16.04, while 2.21 is in 15.04 and 15.10.
Ubuntu:
16.04: Preinstalled images for Raspberry Pi 2/3 available at http://cdimage.ubuntu.com/releases/16.04/release/. Username and password is "ubuntu", and will prompt to change password upon logging in. Requires replacing the libc6 package and everything that directly depends on it with the ones from 15.10. Glibc version 2.23 is in 16.04, while 2.21 is in 15.04 and 15.10.
For Ubuntu 16.04, the following packages must be replaced prior to first boot with a chroot running on either an ARM virtual machine (the instructions at https://wiki.debian.org/QemuUserEmulation will also work), or another ARM computer (Android smartphones and tablets can be used here, as long as they have a microSD slot or support USB-OTG, where a USB SD card reader has to be used instead):
libc-bin
libc6
locales
perl
perl-base
perl-modules
After that, I recommend pinning/locking the packages "libc6" and "perl-base" to prevent the OS from becoming unbootable after an upgrade.
For all unsupported versions of Ubuntu, change the package repository URLs to point to http://old-releases.ubuntu.com/ubuntu/ so that more packages can be installed.
To download any of the Ubuntu MATE image versions listed above, use the torrents attached below (should still work at the time of writing this post). The Internet Archive has saved copies of these torrents, as they can no longer be accessed from the current Ubuntu MATE download page. They can be found at https://web.archive.org/web/*/https://ubuntu-mate.org/raspberry-pi/*
This is the best that I can offer; either use Ubuntu 15.04 right away (and access some newer program versions, but have no access to the latest security updates), or tweak Ubuntu 16.04 post-install with the package names listed above (and access even newer program versions plus security updates until April 2021). It may be the last time we can get newer software on an aging tablet from 2011 [!], unless new ones are compiled from source.
digetx repository
TeTriNol said:
Do someone have headers for kernel 3.8.13.20-digetx-thor-01232-gfe12f92?
Click to expand...
Click to collapse
digetx has a repository on bitbucket, might be there
Upgrade from 14.04 lubuntu by digetx
Thanks for posting the upgrade info, trying for a while but never found out the fix, until now.
After installing and upgrading 14.04 install as originally described on tegraowners I locked all the packages you mentioned eg:
libc-bin
libc6
locales
perl
perl-base
perl-modules
Then did a distrbution upgrade and presto, v16.04. Now I can install the latest versions of some programs I use.
Many thanks for sharing and kudos for finding issue. One day I hope to get back into linux seriously, changed a lot since the 14 floppy disk distributions. :good:
18.04 upgrade works so far
After the v16.04 upgrade I thought "go for broke" and try another dist upgrade and after a few warnings it worked.
Havent tried everything yet but Chromium works to get this typed, and system profiler but I can't upload image here.
Kicad 5 installed but eeschema crashed in 16.04 but it runs on 18.04 albeit a little slower than an i5
https://drive.google.com/file/d/1X3yEyWYsCWyF6RXxgd4GpBkyIHBmIPlw/view?usp=sharing
beaka said:
After the v16.04 upgrade I thought "go for broke" and try another dist upgrade and after a few warnings it worked.
Havent tried everything yet but Chromium works to get this typed, and system profiler but I can't upload image here.
Kicad 5 installed but eeschema crashed in 16.04 but it runs on 18.04 albeit a little slower than an i5
Click to expand...
Click to collapse
Hi beaka, can you share rootfs and install files from tegraowners lubuntu 14.04 ? I'm looking for it but tegraowners is gone now.
rootfs and installer from tegraowners
pheex79 said:
Hi beaka, can you share rootfs and install files from tegraowners lubuntu 14.04 ? I'm looking for it but tegraowners is gone now.
Click to expand...
Click to collapse
Hi pheex,
Here are links to the files I used to install lubuntu 14.04 then do the distupgrades to 18.04
installer:
https://drive.google.com/file/d/13Gg7Xhyx_C1Ra7_rkD4G_3yoPbf-qvC5/view?usp=sharing
rootfs:
https://drive.google.com/file/d/14YZ-_o2c-3afqD0PbppWod12p3xB5fs2/view?usp=sharing
I have skrilax v8 loader and install to sd card.
Hope that helps. :good:
thanks a lot !
Now wifi work, i can't figure it out with ubuntu debootstrap root fs
beaka said:
Hi pheex,
Here are links to the files I used to install lubuntu 14.04 then do the distupgrades to 18.04
I have skrilax v8 loader and install to sd card.
Hope that helps. :good:
Click to expand...
Click to collapse
Dist upgrade don't work for me, something broke dependencies, maybe the packages i freeze (libc...)
Do you remember how do you proceed ?
pheex79 said:
Dist upgrade don't work for me, something broke dependencies, maybe the packages i freeze (libc...)
Do you remember how do you proceed ?
Click to expand...
Click to collapse
I did a new install to card.
apt update
apt upgrade
reboot
open synaptic package manager and lock the versions of:
libc-bin
libc6
locales
perl
perl-base
perl-modulesby selecting then Package/Lock version from menu
reboot and make sure it works
open software updater and update (use gui version as apt doesnt seem to lock version)
reboot and make sure it works
open software updater and do dist upgrade to 16.04 (go to bed as slow dl on 3g)
reboot to see if it worked
then I did a dd of the sd as the upgrade takes hours over 3g
software updater to upgrade 16.04 security
after that I again used software updater to go to 18.04
dd sd card so never have to do it again
using apt from 18.04 doesnt seem to break anything so far that I use.
brief summary but hope it helps. once you get it to 16.04 it seems a bit more stable and on 18.04 it works and is a bit more responsive but I havent tried every feature, just web(chromium and ff v55, had to find old pre-neon vers) , samba, kicad, freerdp (works well) and I can even print to epson wifi x420 (just found it on network, almost thought I was in windows )
good luck let us know how you go