Does this mean that they're not propogating Diablo updates through the repository anymore? Are they avoiding the repository now, thanks to people like us? Need we investigate alternatives for getting updates?
No... he means that he has the newer image that was just compiled... and not finished any internal testing yet.
Aisu, you got your N810 working on Diablo, right? Did you use the same procedure that I outlined a few posts back (page 50) ? Or did you have to do anything special to get it working on N810?
I did a clean reflash. (I forgot to disable the lifeguard the first try )
Then, I changed every instance of Chinook in hildon's list to Diablo, even the extras to be safe... And, that's about it. Oh, and I flashed the kernel afterwards. Mine got caught in a loop, but only needed a good kernel. (I used the one out with rotation support.)
Then, I change every instance of Chinook in hildon's list to Diablo, even the extras to be safe... And, that's about it. Oh, and I flashed the kernel afterwards. Mine got caught in a loop, but only needed a good kernel. (I used the one out with rotation support.)
You only need to change the tableteer update repo to Diablo. The rest of them can be left as is, though you may or may not benefit from adding a Diablo Extras alongside Chinook Extras (though there's nothing in Diablo Extras worth mentioning at the moment).
I did a clean reflash. (I forgot to disable the lifeguard the first try )
Then, I changed every instance of Chinook in hildon's list to Diablo, even the extras to be safe... And, that's about it. Oh, and I flashed the kernel afterwards. Mine got caught in a loop, but only needed a good kernel. (I used the one out with rotation support.)
Hope it helps!!!
My APT sources list doesn't even list the extras repository. There are only three lines.
Okay, I ran through my procedure again. Every time I try it, it seems to go differently, which goes against every ounce of common sense in my engineering brain. This time, during the install, I got some strange "cannot remove /usr/share directory - not empty" errors, followed by some "out of space" errors (even though I had plenty of space in my root partition. This stopped the install, and an "apt-get -f install" instructed me to run "dpkg --configure -a", at which point it then resumed.
When it finished, I skipped the flash-and-reboot step, and now it boots fine. I have no idea how "clean" my file system is, and the obsessive-compulsive part of me wants very badly to retry the process from the beginning, but I'm afraid I'll never be able to get it to boot again. So I'll stick with what I have now unless/until I run into issues.
)