Re: Some buttons not working properly on N800

2009-09-08 Thread Mark
On Tue, Sep 8, 2009 at 4:26 PM, João Marcelo wrote:
>> https://bugs.maemo.org/show_bug.cgi?id=978
>>
>> I haven't tried the solution yet myself - the details are pretty sketchy.
>>
>> Mark
>
> the system does performs slightly better after the crawler patch. but
> the problem persists, cannot unlock the keys. the other buttons are
> more responsive while using another applications.
>
> but not i configured the ssh-server and i'm checking the dmesg while i
> click the button. i get a lot of these:
>
> EAC mode: play disabled, rec disabled
>
> is it somehow related or a completely different beast?
>
> --
> __
> João Marcelo Uchôa de Alencar
> Computer Science BSc.
> jmarcelo.alencar(at)gmail.com
> http://simetriade.blogspot.com
> Linux User 398939
> __

So I tried the CRAWLPATH variable patch and it didn't make any
difference at all for me. After some digging I finally figured out
that to keep the crawler from starting all you need to do is add "exit
0" to the beginning of the file. That finally fixed the crawler
problem for me. I sure wish somebody who understands all the
implications would write a better and more explicit set of
instructions.

Back to your problem, though: I can't say that I really know what's
going on, but it sure sounds to me like you've got a recorder app
running in the background that's hijacking the button input and has
some other problem that is preventing proper operation - maybe it
isn't even fully loading properly. I would try looking through your
process list and/or system logs for any obvious suspects.

And with that I'll shut up. I'm trying to be helpful but I have to
admit I'm in over my head.

Mark
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Internal memory card is read-only

2009-09-08 Thread Keywan Najafi Tonekaboni
Hi,

thanks for your hints. I have a corrupted file called "map" which isn't
readable.fsck thrown some errors and I let repair it. It seems ok again.
How can I format it? Is there something tablet specific?

Btw. Shouldn't Maemo report such problems and help the user to fix it?

Regards,

Keywan

Am Mittwoch, den 09.09.2009, 00:45 +0200 schrieb Attila Csipa:
> On Tuesday 08 September 2009 23:20:16 Keywan Najafi Tonekaboni wrote:
> > my internal memory card is read only, but in the "Memory"-Settings (from
> > Control panel) the checkbox isn't activated. I tried to restart the
> > device, but after reboot it's still read-only. I can remount it to
> > read-write, but after one action it's read-only again. Any idea?
> 
> Try checking the filesystem, spontaneous switches to read-only mode can be 
> signs of FS corruption.
> ___
> maemo-users mailing list
> maemo-users@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-users
-- 
Keywan Najafi Tonekaboni
http://www.prometoys.net

peo...@world:/# apt-get --purge remove capitalism
After unpacking world will be freed.
You are about to do something potentially beneficial
To continue type in the phrase 'Yes, do as We say!'

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Internal memory card is read-only

2009-09-08 Thread Brad Midgley
Keywan

> my internal memory card is read only, but in the "Memory"-Settings (from
> Control panel) the checkbox isn't activated. I tried to restart the
> device, but after reboot it's still read-only. I can remount it to
> read-write, but after one action it's read-only again. Any idea?

the filesystem is corrupt. Some time ago I struggled with this and
found the easiest solution was to back up and reformat the card rather
than try to repair the fs.

-- 
Brad Midgley
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Internal memory card is read-only

2009-09-08 Thread Attila Csipa
On Tuesday 08 September 2009 23:20:16 Keywan Najafi Tonekaboni wrote:
> my internal memory card is read only, but in the "Memory"-Settings (from
> Control panel) the checkbox isn't activated. I tried to restart the
> device, but after reboot it's still read-only. I can remount it to
> read-write, but after one action it's read-only again. Any idea?

Try checking the filesystem, spontaneous switches to read-only mode can be 
signs of FS corruption.
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Some buttons not working properly on N800

2009-09-08 Thread João Marcelo
the system does performs slightly better after the crawler patch. but
the problem persists, cannot unlock the keys. the other buttons are
more responsive while using another applications.

but not i configured the ssh-server and i'm checking the dmesg while i
click the button. i get a lot of these:

EAC mode: play disabled, rec disabled

is it somehow related or a completely different beast?

On Tue, Sep 8, 2009 at 6:57 PM, Mark wrote:
> On Tue, Sep 8, 2009 at 3:30 PM, João Marcelo 
> wrote:
>> On Tue, Sep 8, 2009 at 6:10 PM, Mark wrote:
>>> On Sun, Sep 6, 2009 at 6:39 PM, João Marcelo 
>>> wrote:
 Helo Community,

 I've just bought a brand new nokia n800 tablet. It comes loaded with a
 old version of Maemo so I followed the instructions on
 http://wiki.maemo.org/Updating_the_tablet_firmware . I updated to the
 latest version, RX-34_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin using
 flasher-3.0.

 Everything worked just fine, the device rebooted. The problem happens
 when I single click the power button, the device mode menu appears and
 choose 'Lock touch screen and keys'. The screen is locked and I just
 can't unlock. When I click the power button again, a message asking me
 to press the central button appears. I click it, but the device
 doesn't unlock. The button seems to work with other applications, but
 it isn't something reliable, sometimes it doesn't work. The same can
 be said about all the other buttons, including the directional
 buttons, the return, menu and home buttons.

 Is it a hardware problem or by any chance is it related with software?

>>> I suspect that there is a software issue. I don't usually have any
>>> trouble unlocking the touch screen and keys, but I have a devil of a
>>> time unlocking the device with the numeric code if I shut it down
>>> while locked. I think that may be related to the piece of crap
>>> metalayer-crawler hogging 100% of the system resources for several
>>> minutes on bootup. Whose brilliant idea was it to design that process
>>> to run on startup with top priority, anyway? It should only run with a
>>> very low priority and allow other processes to run first.
>>>
>>
>> suppose this is the reason. is there a way to edit the init scripts
>> and change this process priority? this is a good explanation and also
>> explains other strange behaviors. i'm starting to consider the idea
>> that i'll have to learn with this.
>>
> https://bugs.maemo.org/show_bug.cgi?id=978
>
> I haven't tried the solution yet myself - the details are pretty sketchy.
>
> Mark
> ___
> maemo-users mailing list
> maemo-users@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-users
>



-- 
__
João Marcelo Uchôa de Alencar
Computer Science BSc.
jmarcelo.alencar(at)gmail.com
http://simetriade.blogspot.com
Linux User 398939
__
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Some buttons not working properly on N800

2009-09-08 Thread Mark
On Tue, Sep 8, 2009 at 3:30 PM, João Marcelo wrote:
> On Tue, Sep 8, 2009 at 6:10 PM, Mark wrote:
>> On Sun, Sep 6, 2009 at 6:39 PM, João Marcelo 
>> wrote:
>>> Helo Community,
>>>
>>> I've just bought a brand new nokia n800 tablet. It comes loaded with a
>>> old version of Maemo so I followed the instructions on
>>> http://wiki.maemo.org/Updating_the_tablet_firmware . I updated to the
>>> latest version, RX-34_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin using
>>> flasher-3.0.
>>>
>>> Everything worked just fine, the device rebooted. The problem happens
>>> when I single click the power button, the device mode menu appears and
>>> choose 'Lock touch screen and keys'. The screen is locked and I just
>>> can't unlock. When I click the power button again, a message asking me
>>> to press the central button appears. I click it, but the device
>>> doesn't unlock. The button seems to work with other applications, but
>>> it isn't something reliable, sometimes it doesn't work. The same can
>>> be said about all the other buttons, including the directional
>>> buttons, the return, menu and home buttons.
>>>
>>> Is it a hardware problem or by any chance is it related with software?
>>>
>> I suspect that there is a software issue. I don't usually have any
>> trouble unlocking the touch screen and keys, but I have a devil of a
>> time unlocking the device with the numeric code if I shut it down
>> while locked. I think that may be related to the piece of crap
>> metalayer-crawler hogging 100% of the system resources for several
>> minutes on bootup. Whose brilliant idea was it to design that process
>> to run on startup with top priority, anyway? It should only run with a
>> very low priority and allow other processes to run first.
>>
>
> suppose this is the reason. is there a way to edit the init scripts
> and change this process priority? this is a good explanation and also
> explains other strange behaviors. i'm starting to consider the idea
> that i'll have to learn with this.
>
https://bugs.maemo.org/show_bug.cgi?id=978

I haven't tried the solution yet myself - the details are pretty sketchy.

Mark
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Some buttons not working properly on N800

2009-09-08 Thread João Marcelo
Ok,

On Tue, Sep 8, 2009 at 6:10 PM, Mark wrote:
> On Sun, Sep 6, 2009 at 6:39 PM, João Marcelo 
> wrote:
>> Helo Community,
>>
>> I've just bought a brand new nokia n800 tablet. It comes loaded with a
>> old version of Maemo so I followed the instructions on
>> http://wiki.maemo.org/Updating_the_tablet_firmware . I updated to the
>> latest version, RX-34_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin using
>> flasher-3.0.
>>
>> Everything worked just fine, the device rebooted. The problem happens
>> when I single click the power button, the device mode menu appears and
>> choose 'Lock touch screen and keys'. The screen is locked and I just
>> can't unlock. When I click the power button again, a message asking me
>> to press the central button appears. I click it, but the device
>> doesn't unlock. The button seems to work with other applications, but
>> it isn't something reliable, sometimes it doesn't work. The same can
>> be said about all the other buttons, including the directional
>> buttons, the return, menu and home buttons.
>>
>> Is it a hardware problem or by any chance is it related with software?
>>
> I suspect that there is a software issue. I don't usually have any
> trouble unlocking the touch screen and keys, but I have a devil of a
> time unlocking the device with the numeric code if I shut it down
> while locked. I think that may be related to the piece of crap
> metalayer-crawler hogging 100% of the system resources for several
> minutes on bootup. Whose brilliant idea was it to design that process
> to run on startup with top priority, anyway? It should only run with a
> very low priority and allow other processes to run first.
>

suppose this is the reason. is there a way to edit the init scripts
and change this process priority? this is a good explanation and also
explains other strange behaviors. i'm starting to consider the idea
that i'll have to learn with this.

> Mark
> ___
> maemo-users mailing list
> maemo-users@maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-users
>



-- 
__
João Marcelo Uchôa de Alencar
Computer Science BSc.
jmarcelo.alencar(at)gmail.com
http://simetriade.blogspot.com
Linux User 398939
__
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Internal memory card is read-only

2009-09-08 Thread Keywan Najafi Tonekaboni
Hi,

my internal memory card is read only, but in the "Memory"-Settings (from
Control panel) the checkbox isn't activated. I tried to restart the
device, but after reboot it's still read-only. I can remount it to
read-write, but after one action it's read-only again. Any idea?

Thanks,

Keywan

-- 
Keywan Najafi Tonekaboni
http://www.prometoys.net

peo...@world:/# apt-get --purge remove capitalism
After unpacking world will be freed.
You are about to do something potentially beneficial
To continue type in the phrase 'Yes, do as We say!'

___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users


Re: Some buttons not working properly on N800

2009-09-08 Thread Mark
On Sun, Sep 6, 2009 at 6:39 PM, João Marcelo wrote:
> Helo Community,
>
> I've just bought a brand new nokia n800 tablet. It comes loaded with a
> old version of Maemo so I followed the instructions on
> http://wiki.maemo.org/Updating_the_tablet_firmware . I updated to the
> latest version, RX-34_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin using
> flasher-3.0.
>
> Everything worked just fine, the device rebooted. The problem happens
> when I single click the power button, the device mode menu appears and
> choose 'Lock touch screen and keys'. The screen is locked and I just
> can't unlock. When I click the power button again, a message asking me
> to press the central button appears. I click it, but the device
> doesn't unlock. The button seems to work with other applications, but
> it isn't something reliable, sometimes it doesn't work. The same can
> be said about all the other buttons, including the directional
> buttons, the return, menu and home buttons.
>
> Is it a hardware problem or by any chance is it related with software?
>
I suspect that there is a software issue. I don't usually have any
trouble unlocking the touch screen and keys, but I have a devil of a
time unlocking the device with the numeric code if I shut it down
while locked. I think that may be related to the piece of crap
metalayer-crawler hogging 100% of the system resources for several
minutes on bootup. Whose brilliant idea was it to design that process
to run on startup with top priority, anyway? It should only run with a
very low priority and allow other processes to run first.

Mark
___
maemo-users mailing list
maemo-users@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-users