Re: Insufficient Space to upgrade

Mark <wolfmane <at> gmail.com> writes:

> emelFM2 is a very handy file manager that should meet your
> requirements. DiskUsage is a utility that might actually be very
> helpful in your scenario as well.

I used DisUsage and manually removed some documentation pdf files. And
I uninstalled big packages like gnumeric.

The first time I tried to upgrade I hade 35M free or something like
that and the upgrade proceeded but the installation failed and when I
rebooted I got into a reboot loop and I hade to reflash the device.

The second time I tried I had 70M free and it worked...

--

-- 
/Tommy Persson

Re: Insufficient Space to upgrade

<div><div dir="ltr">
<div>I had the same experience - I deleted documentation files and it seemed to provide enough space but when I rebooted I got in an endless reboot loop and had to reflash. Fortunately that fixed some other problems I was having like the RSS feeder not working, still a pain setting up my claws mail accounts again.</div>

<div>&nbsp;</div>
<div>Mike<br><br>
</div>
<div class="gmail_quote">On Tue, Sep 30, 2008 at 6:27 PM, Tommy Persson <span dir="ltr">&lt;<a href="mailto:tpe <at> ida.liu.se">tpe <at> ida.liu.se</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div class="Ih2E3d">Mark &lt;<a href="mailto:wolfmane <at> gmail.com">wolfmane <at> gmail.com</a>&gt; writes:<br><br>&gt; emelFM2 is a very handy file manager that should meet your<br>&gt; requirements. DiskUsage is a utility that might actually be very<br>
&gt; helpful in your scenario as well.<br><br>
</div>I used DisUsage and manually removed some documentation pdf files. And<br>I uninstalled big packages like gnumeric.<br><br>The first time I tried to upgrade I hade 35M free or something like<br>
that and the upgrade proceeded but the installation failed and when I<br>rebooted I got into a reboot loop and I hade to reflash the device.<br><br>The second time I tried I had 70M free and it worked...<br><br>--<br>/Tommy Persson<br>
<div>
<div></div>
<div class="Wj3C7c">_______________________________________________<br>maemo-users mailing list<br><a href="mailto:maemo-users <at> maemo.org">maemo-users <at> maemo.org</a><br><a href="https://lists.maemo.org/mailman/listinfo/maemo-users" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div></div>

Updating n810w (rx-48) to latest firmware

Hi,

I have n810 wimax (rx-48) where I need to upgrade from maemo 0.2008.14-9
to the latest version (4.2008.36-5). However, I can't seem to get my
hands on a frimware binary. I've tried both
http://tablets-dev.nokia.com/nokia_N810.php and the Windows software
update tool from Nokia
(Nokia_Internet_Tablet_Software_Update_Wizard.exe) without any luck.

Has anyone had the same problem?

Thanks,
Pete

Re: WiFi borked after update

Andre Klapper wrote:
> This might be related to the problem:
> https://bugs.maemo.org/show_bug.cgi?id=3749
>   
thanks. that was the exact problem. Poking around with autoconnection on 
my N800 made it to connect to nearest known AP, from there I was able to 
continue in terminal. ugh. glad I didn't have to reflash.
> See comment 5 for a potential workaround. No idea about potential
> negative side effects, though. :-/
>
> andre
>   

Re: WiFi borked after update

	Hi,

On Tue, 2008-09-30 at 19:37 +0300, ext Marius Vollmer wrote:

>    # dpkg --configure -a

On my device everything else configured itself except:

dpkg: dependency problems prevent configuration of
osso-software-version-rx44:
 osso-software-version-rx44 depends on pre-installed-documentation-rx44
(= 5.4); however:
  Version of pre-installed-documentation-rx44 on system is 5.3.
dpkg: error processing osso-software-version-rx44 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 osso-software-version-rx44

> Rebooting might also help, in case you didn't do that already.

I wouldn't reboot until running dpkg --configure -a, but maybe that's
just me. It is also advisable to do a backup before upgrading.

I have more logs for you Marius when you're at the office.

Regards,
	Patrik

--

-- 
Patrik Flykt <Patrik.Flykt <at> nokia.com>

Re: Flash player conflict stopping the feature update

Ryan Abel wrote:
> On Sep 30, 2008, at 12:01 PM, Matt Emson wrote:
>
> That "someone" being timeless. :)

"Someone" being a simple way not to have to go search for the 
culprit/genius/kind individual that created the package, obviously 

>
>> Unfortunately, it seems this package is stopping installation of the
>> latest feature upgrade available via system update......
>
> Just uninstall the package from Application manager and all will be well.

As indicated, I was going to try that, but I wanted to do it at home as 
work WIFI is spotty at best. I can confirm "promlems fixed" with removal.

M

Re: Updating n810w (rx-48) to latest firmware

Hi,

Am Dienstag, den 30.09.2008, 22:00 -0700 schrieb Pete Black:
> I have n810 wimax (rx-48) where I need to upgrade from maemo 0.2008.14-9
> to the latest version (4.2008.36-5). However, I can't seem to get my
> hands on a frimware binary. I've tried both
> http://tablets-dev.nokia.com/nokia_N810.php and the Windows software
> update tool from Nokia
> (Nokia_Internet_Tablet_Software_Update_Wizard.exe) without any luck.
> 
> Has anyone had the same problem?

0.2008.14-9? Where did you get that version (and the device) from?
Your description is vague - What *exactly* was the issue with flashing
it? Any error messages?

andre
--

-- 
Andre Klapper (maemo.org bugmaster)

Re: Offline mode from the command-line?

Thanks to all who replied.

Faheem's 
/usr/bin/dbus-send --system --type=signal /com/nokia/mce/signal
com.nokia.mce.signal.sig_device_mode_ind string:"[normal|flight]"
works a treat.

Had to live with a bit of a hack to get it to wake up again in the morning until I can find some documentation for
alarmtool (though it seems the alarm's not that reliable anyway) but my battery was a lot fuller this
morning 

In case it's of help to anybody, this is the script that I'm now running. I start it via SSH from my server at the
end of the backup. The downside is that the SSH session stays up until it restarts, but it's less of an
overhead than staying connected (I've backgrounding the script, but SSH seems determined to stay.)

# Switch to offline mode
/usr/bin/dbus-send --system --type=signal /com/nokia/mce/signal
com.nokia.mce.signal.sig_device_mode_ind string:"flight"

# wait 8 1/2 hours so the device will reconnect in time for when I'll need it online again
sleep 30600

# Switch back to online mode and reconnect to the default access point
/usr/bin/dbus-send --system --type=signal /com/nokia/mce/signal
com.nokia.mce.signal.sig_device_mode_ind string:"normal"

-- 
Tony Green
Ipswich, Suffolk, England
http://www.beermad.org.uk/
http://www.suffolkcamra.co.uk/pubs/

** This message is digitally signed. If your email client is unable to read digital signatures, you may see
an attachment that you cannot open. See http://www.gnupg.org/documentation/faqs.en.html for more information.
You can validate my PGP key from my website: http://www.beermad.org.uk/
* No Micro$oft products were used in the generation of this communication

Thanks to all who replied.

Faheem's 
/usr/bin/dbus-send --system --type=signal /com/nokia/mce/signal
com.nokia.mce.signal.sig_device_mode_ind string:"[normal|flight]"
works a treat.

Had to live with a bit of a hack to get it to wake up again in the morning until I can find some documentation for
alarmtool (though it seems the alarm's not that reliable anyway) but my battery was a lot fuller this
morning 

In case it's of help to anybody, this is the script that I'm now running. I start it via SSH from my server at the
end of the backup. The downside is that the SSH session stays up until it restarts, but it's less of an
overhead than staying connected (I've backgrounding the script, but SSH seems determined to stay.)

# Switch to offline mode
/usr/bin/dbus-send --system --type=signal /com/nokia/mce/signal
com.nokia.mce.signal.sig_device_mode_ind string:"flight"

# wait 8 1/2 hours so the device will reconnect in time for when I'll need it online again
sleep 30600

# Switch back to online mode and reconnect to the default access point
/usr/bin/dbus-send --system --type=signal /com/nokia/mce/signal
com.nokia.mce.signal.sig_device_mode_ind string:"normal"

--

-- 
Tony Green
Ipswich, Suffolk, England
http://www.beermad.org.uk/
http://www.suffolkcamra.co.uk/pubs/

** This message is digitally signed. If your email client is unable to read digital signatures, you may see
an attachment that you cannot open. See http://www.gnupg.org/documentation/faqs.en.html for more information.
You can validate my PGP key from my website: http://www.beermad.org.uk/
* No Micro$oft products were used in the generation of this communication

Re: Updating n810w (rx-48) to latest firmware

On Oct 1, 2008, at 7:21 AM, Andre Klapper wrote:

> Hi,
>
> Am Dienstag, den 30.09.2008, 22:00 -0700 schrieb Pete Black:
>> I have n810 wimax (rx-48) where I need to upgrade from maemo  
>> 0.2008.14-9
>> to the latest version (4.2008.36-5). However, I can't seem to get my
>> hands on a frimware binary. I've tried both
>> http://tablets-dev.nokia.com/nokia_N810.php and the Windows software
>> update tool from Nokia
>> (Nokia_Internet_Tablet_Software_Update_Wizard.exe) without any luck.
>>
>> Has anyone had the same problem?
>
> 0.2008.14-9? Where did you get that version (and the device) from?

Internal release for the RX-48. Clearly this is an internal pre- 
release device.

> Your description is vague - What *exactly* was the issue with flashing
> it? Any error messages?

Well, the issue is that there's no public images available for RX-48.  
The RX-34 and RX-44 images don't have the stuff needed for the RX-48,  
so getting them running on the RX-48 isn't going to be an option like  
it was for the RX-34 back in November with the RX-48 image.

--
Ryan Abel
Maemo Community Council chair

Re: WiFi borked after update

On Tue, 2008-09-30 at 23:37 -0600, Dmitry S. Makovey wrote:
> Andre Klapper wrote:
> > This might be related to the problem:
> > https://bugs.maemo.org/show_bug.cgi?id=3749
> >   
> thanks. that was the exact problem. Poking around with autoconnection on 
> my N800 made it to connect to nearest known AP, from there I was able to 
> continue in terminal. ugh. glad I didn't have to reflash.

Yes same for me (I didn't put it in the report but I removed all non
diablo repo from my source list before apt-get). After the manual
command line cleanup everything seems back to normal (and reboot works
fine). Only thing is that osso-software-version-rx44 is no longer
installed for some reason.

Laurent