Eero Tamminen wrote:
Are you building your own kernel which is newer than the one coming
with the latest release?I heard that with some of the newer versions
/etc/init.d/ttyusb0 could start getty and the script needs to be updated
for newer kernel.
Own kernel from bora 3.1 repository with
Hi,
ext Frantisek Dufka wrote:
> Another thing is getty running on /dev/ttyS0, I think I removed it from
> inittab and it appeared again. R&D mode is disabled. Does this cause
> higher power consumption or is harmless?
Are you building your own kernel which is newer than the one coming
with the l
2007/4/18, Eero Tamminen <[EMAIL PROTECTED]>:
Hi,
ext Frantisek Dufka wrote:
>>> Also there are other issues with the firmware. It looks like
>>> /var/run/wtmp growing problem is back (was in some n770 firmware but was
>>> solved if I remember correctly).
>
> Sorry, it is in /var/log
That I hav
On 4/18/07, Eero Tamminen <[EMAIL PROTECTED]> wrote:
> Sorry, it is in /var/log
That I have, but it's only 6kB after several days of device being
on/online.
mine was 62-megs (of course what i did immediately is ln -sf /dev/null
/var/log/wtmp)
(latest firmware)
--
Kemal
___
Hi,
ext Frantisek Dufka wrote:
>>> Also there are other issues with the firmware. It looks like
>>> /var/run/wtmp growing problem is back (was in some n770 firmware but was
>>> solved if I remember correctly).
>
> Sorry, it is in /var/log
That I have, but it's only 6kB after several days of devi
Eero Tamminen wrote:
Also there are other issues with the firmware. It looks like
/var/run/wtmp growing problem is back (was in some n770 firmware but was
solved if I remember correctly).
Sorry, it is in /var/log
___
maemo-developers mailing list
maem
Hi,
ext Frantisek Dufka wrote:
>> It was a (new) bug noticed too little time before the latest release
>> so there was not enough time to find the root cause & fix & re-build
>> everything needed. The effect is a couple of secs lost at bootup and
>> a couple of MB of RAM lost after device is up (
Eero Tamminen wrote:
It was a (new) bug noticed too little time before the latest release
so there was not enough time to find the root cause & fix & re-build
everything needed. The effect is a couple of secs lost at bootup and
a couple of MB of RAM lost after device is up (compared to system t
