(1st Jul, 2013 11:37 PM)ilgrank Wrote: [ -> ]@IriDium: Sorry if I sounded unpolite, that was not my intention.
What I wanted to say is that I've encountered the error in the un-hotfixed B1 and just wanted to know if someone else, besides me, was aware of the issue.
@mk01: I've already stated that I'm at office right now and can't do it from here... I'll comply as soon as I can of course
Thanks everyone!
@
ilgrank: What Iridium is trying to say is that this thread is not about the un-hotfixed B1, for that you need the thread he linked, and if you have issues that are new, please report them there (that's also the thread where you can find out if a certain issue with the un-hotfixed B1 is already flagged). I hope that clarifies things somewhat.
I'll give the hotfix a whirl tonight, will report back.
(1st Jul, 2013 06:18 PM)Koenkk Wrote: [ -> ] (1st Jul, 2013 05:54 AM)DexterBelgium Wrote: [ -> ]Tried it just now, got
Code:
W: Failed to fetch http://dikonist.asuscomm.com:82/XBian/APT/dists/wheezy/Release.gpg Could not connect to dikonist.asuscomm.com:82 (88.159.202.11). - connect (111: Connection refused)
can ping the dikonist.asuscomm.com domain from the Pi just fine, so I'm thinking it might be the port?
Fixed
Well, for me it is still:
Terminal
Err http://dikonist.asuscomm.com wheezy Release.gpg
Could not connect to dikonist.asuscomm.com:82 (88.159.202.11). - connect (111: Connection refused)
Repo is up again, this is (or is atleast quite close) to the final beta 1.1 (aka beta 1 hotfix)
Just tried the instructions in the opening post (so using the "dikonist" repo on a fresh b1 image):
Code:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
xbian-update : PreDepends: xbian-update (= 1.0-1) but 1.0-1.2 is to be installed
PreDepends: xbian-package-splash (>= 1.0-0.6) but 1.0-0.4 is to be installed
E: Unable to correct problems, you have held broken packages.
Gonna try doing an apt-get upgrade and then maybe do the xbian-update thing? I dunno...
EDIT: that went nowhere. (got stuck on somethning about "intramfs triggers").
Could it be that I have beta1.OLD already downloaded on my system and that the installer is therefore not giving me the same "clean" beta1 that you guys are starting from? I'll take the june 23 image from the repo linked above and try again from that.
EDIT2: or maybe I won't, that takes over an hour to download, and I need to get to work...
Downloading beta1 image from the site now, gonna flash with win32diskimager, see whether that allows me to finally follow the simple instructions from the OP (which then might also flag a problem: i.e., any hotfix would need to take into account people with an "old" image in their windows installer temp directories).
Tried it from an image downloaded off the site, same thing (although that did mention 9 packages rather than 7 available?).
I just now hit apt-get upgrade again, see if that does something.
EDIT: that seems to hang on "processing triggers for xbian-package-intramfs-tools" again. I'll leave it to stew on that and get to work.
And i'm thinking it won't help anyway, as the unmet dependency for xbian-update is the xbian-package-splash package at >=1.0-0.6 and it just updated it to 1.0-0.5.
and as i'm writing this i'm seeing a write error on swap device pop up on my tv screen (not on my putty console).
Weird, maybe I should try mk01's repo next, but I ran out of time (I REALLY need to get to work)... oh what the hell, I can't let go of these things when they oppose me. I'll try that and THEN leave for work.
EDIT2: weird, mk01s repo has 10 packages as output from apt-get update (had 7 when I install with the installer, 9 from koenkk's repo, and now 10)
EDIT3: can now confirm that KoenKKs repo does not work for me (dependency error mentioned above), while mk01s does start the process. Too bad it's slower than thick ... through a funnel
FINAL EDIT: got through the procedure for the most part, although at one point the connection via putty dropped out. I don't know whether the update completed successfully. Still have the "corrupted" visuals on the ssh version of xbian-config, so I'm not hopeful...
I have only 512kbps upload, so... but I was writing it somewhere, don't try what was officialy presented as hot fix. the bug is within initramfs (or was still there). the only issue was that there was command using compression on the final initramfs image with no limit on memory, what was hitting 250mb at the end.
I with 512mb model never realized such problem, but definitely some people will hit to it as serious error causing update to fail.
corrupted visuals (if you mean improper corners and lines) are due wrong locale and font setting rather on windows side. unfortunately microsoft never had full multi language support implemented and it depends on the fonts used etc...
(2nd Jul, 2013 05:32 PM)mk01 Wrote: [ -> ]I have only 512kbps upload, so... but I was writing it somewhere, don't try what was officialy presented as hot fix. the bug is within initramfs (or was still there). the only issue was that there was command using compression on the final initramfs image with no limit on memory, what was hitting 250mb at the end.
I with 512mb model never realized such problem, but definitely some people will hit to it as serious error causing update to fail.
corrupted visuals (if you mean improper corners and lines) are due wrong locale and font setting rather on windows side. unfortunately microsoft never had full multi language support implemented and it depends on the fonts used etc...
Cool, I had thought as much with the "corrupt visuals" (indeed, the lines and corners). Although it used to work on alpha 5 with the same putty setup, so something probably changed there, although it is not "broken" as such.
I'm on a 256mb Pi as well (very EARLY model B), so that indeed makes sense.
From my very limited testing this morning, the update seems to have worked ok (apt-getting xbian-update from your repo): I have youtube installed no probs, it worked perfect. I'll test more when I get home.
So, the Hotfix is no longer available?
[edit]Think it worked anyway, was kinda surprised the website was xxxx-ed out, so thought the Hotfix was down[/edit]
on my repo instant development
(3rd Jul, 2013 12:24 PM)mk01 Wrote: [ -> ]on my repo instant development
could you please post instructions for the less-tech-savvy users of Beta 1?
Just like in the opening post.
Thanks