Re: [QtMoko GTA02] udevd errors on screen after update
Pay attention with updated upgrades because in these days they're moving squeeze to oldstable and wheezy to stable... they're actually working on servers... uro On Fri, 03 May 2013 15:23:45 +0200, Radek Polak pson...@seznam.cz wrote: On Friday, May 03, 2013 01:31:24 PM asteroid wrote: I disable udev and I haven't got udevd running after reboot. So, can we remove udev package completly ? I am not sure if it is removable because of dependencies. And udev is quite nice when you use usbhost, so i think disabling it is better then removing. Regards Radek -- 不要催我!你曾經問過梵谷畫很快嗎? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko GTA02] udevd errors on screen after update
On Thursday, May 02, 2013 06:51:35 PM francesco.dev...@mailoo.org wrote: Hi today I did a dist-upgrade on QtMoko v55 on GTA02, after an update of qtmoko-neo (55-1 ?) and the linux image (uname -r gives 2.6.34-qtmoko-v55) I have this error repeated again and again: udevd[667]: unable to receive ctrl connection: Function not implemented QtMoko eventually starts but it takes too much time, I can use ssh but the error is continuosly repeated on the screen. Hmm QtMoko on Freerunner does not need udev - we are using kernel devtmpfs which is enough. Can you try disabling udev? Something like: update-rc.d -f udev-mtab remove update-rc.d -f udev remove and reboot. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko GTA02] udevd errors on screen after update
On Thursday, May 02, 2013 06:51:35 PM francesco.dev...@mailoo.org wrote: Hi today I did a dist-upgrade on QtMoko v55 on GTA02, after an update of qtmoko-neo (55-1 ?) and the linux image (uname -r gives 2.6.34-qtmoko-v55) I have this error repeated again and again: udevd[667]: unable to receive ctrl connection: Function not implemented QtMoko eventually starts but it takes too much time, I can use ssh but the error is continuosly repeated on the screen. Hmm QtMoko on Freerunner does not need udev - we are using kernel devtmpfs which is enough. Can you try disabling udev? Something like: update-rc.d -f udev-mtab remove update-rc.d -f udev remove and reboot. Regards Radek I disable udev and I haven't got udevd running after reboot. So, can we remove udev package completly ? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko GTA02] udevd errors on screen after update
On Friday, May 03, 2013 01:31:24 PM asteroid wrote: I disable udev and I haven't got udevd running after reboot. So, can we remove udev package completly ? I am not sure if it is removable because of dependencies. And udev is quite nice when you use usbhost, so i think disabling it is better then removing. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko GTA02] udevd errors on screen after update
francesco.dev...@mailoo.org writes: today I did a dist-upgrade on QtMoko v55 on GTA02, after an update of qtmoko-neo (55-1 ?) and the linux image (uname -r gives 2.6.34-qtmoko-v55) I have this error repeated again and again: I don't run qtmoko but I don't think this bug is qtmoko specific. Could you also mention udev version number? Both old and new? grep udev /var/log/dpkg.log should show this. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko GTA02] udevd errors on screen after update
I've got the same, and a lot of udevd process shown by 'ps fax' or 'top', and use a lot of battery. Hi today I did a dist-upgrade on QtMoko v55 on GTA02, after an update of qtmoko-neo (55-1 ?) and the linux image (uname -r gives 2.6.34-qtmoko-v55) I have this error repeated again and again: udevd[667]: unable to receive ctrl connection: Function not implemented QtMoko eventually starts but it takes too much time, I can use ssh but the error is continuosly repeated on the screen. Help :( Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko GTA02] udevd errors on screen after update
Il 02/05/2013 19:28, Timo Juhani Lindfors ha scritto: I don't run qtmoko but I don't think this bug is qtmoko specific. Could you also mention udev version number? Both old and new? grep udev /var/log/dpkg.log here it is root@neo:~# grep udev /var/log/dpkg.log 2013-03-28 07:00:30 install libudev0:armel none 175-7.1 2013-03-28 07:00:30 status half-installed libudev0:armel 175-7.1 2013-03-28 07:00:30 status unpacked libudev0:armel 175-7.1 2013-03-28 07:00:31 status unpacked libudev0:armel 175-7.1 2013-03-28 07:00:32 install udev:armel none 175-7.1 2013-03-28 07:00:32 status half-installed udev:armel 175-7.1 2013-03-28 07:00:36 status unpacked udev:armel 175-7.1 2013-03-28 07:00:36 status unpacked udev:armel 175-7.1 2013-03-28 07:03:05 install libgudev-1.0-0:armel none 175-7.1 2013-03-28 07:03:05 status half-installed libgudev-1.0-0:armel 175-7.1 2013-03-28 07:03:05 status unpacked libgudev-1.0-0:armel 175-7.1 2013-03-28 07:03:05 status unpacked libgudev-1.0-0:armel 175-7.1 2013-03-28 07:05:54 configure libudev0:armel 175-7.1 none 2013-03-28 07:05:54 status unpacked libudev0:armel 175-7.1 2013-03-28 07:05:54 status half-configured libudev0:armel 175-7.1 2013-03-28 07:05:54 status installed libudev0:armel 175-7.1 2013-03-28 07:05:55 configure udev:armel 175-7.1 none 2013-03-28 07:05:55 status unpacked udev:armel 175-7.1 2013-03-28 07:05:55 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status unpacked udev:armel 175-7.1 2013-03-28 07:05:56 status half-configured udev:armel 175-7.1 2013-03-28 07:05:57 status installed udev:armel 175-7.1 2013-03-28 07:06:48 configure libgudev-1.0-0:armel 175-7.1 none 2013-03-28 07:06:48 status unpacked libgudev-1.0-0:armel 175-7.1 2013-03-28 07:06:48 status half-configured libgudev-1.0-0:armel 175-7.1 2013-03-28 07:06:48 status installed libgudev-1.0-0:armel 175-7.1 2013-05-02 18:22:13 upgrade udev:armel 175-7.1 175-7.2 2013-05-02 18:22:13 status half-configured udev:armel 175-7.1 2013-05-02 18:22:14 status unpacked udev:armel 175-7.1 2013-05-02 18:22:14 status half-installed udev:armel 175-7.1 2013-05-02 18:22:33 status half-installed udev:armel 175-7.1 2013-05-02 18:22:35 status half-installed udev:armel 175-7.1 2013-05-02 18:22:35 status unpacked udev:armel 175-7.2 2013-05-02 18:22:36 status unpacked udev:armel 175-7.2 2013-05-02 18:22:36 upgrade libudev0:armel 175-7.1 175-7.2 2013-05-02 18:22:36 status half-configured libudev0:armel 175-7.1 2013-05-02 18:22:36 status unpacked libudev0:armel 175-7.1 2013-05-02 18:22:36 status half-installed libudev0:armel 175-7.1 2013-05-02 18:22:37 status half-installed libudev0:armel 175-7.1 2013-05-02 18:22:38 status unpacked libudev0:armel 175-7.2 2013-05-02 18:22:38 status unpacked libudev0:armel 175-7.2 2013-05-02 18:24:08 upgrade libgudev-1.0-0:armel 175-7.1 175-7.2 2013-05-02 18:24:08 status half-configured libgudev-1.0-0:armel 175-7.1 2013-05-02 18:24:08 status unpacked libgudev-1.0-0:armel 175-7.1 2013-05-02 18:24:08 status half-installed libgudev-1.0-0:armel 175-7.1 2013-05-02 18:24:10 status half-installed libgudev-1.0-0:armel 175-7.1 2013-05-02 18:24:11 status unpacked libgudev-1.0-0:armel 175-7.2 2013-05-02 18:24:11 status unpacked libgudev-1.0-0:armel 175-7.2 2013-05-02 18:27:39 configure libudev0:armel 175-7.2 none 2013-05-02 18:27:39 status unpacked libudev0:armel 175-7.2 2013-05-02 18:27:39 status half-configured libudev0:armel 175-7.2 2013-05-02 18:27:39 status installed libudev0:armel 175-7.2 2013-05-02 18:27:40 configure udev:armel 175-7.2 none 2013-05-02 18:27:40 status unpacked udev:armel 175-7.2 2013-05-02 18:27:40 status unpacked udev:armel 175-7.2 2013-05-02 18:27:40 status unpacked udev:armel 175-7.2 2013-05-02 18:27:40 status unpacked udev:armel 175-7.2 2013-05-02 18:27:40 status unpacked udev:armel 175-7.2 2013-05-02 18:27:40 status unpacked udev:armel 175-7.2 2013-05-02 18:27:40 status unpacked udev:armel 175-7.2 2013-05-02 18:27:41 status unpacked udev:armel 175-7.2 2013-05-02 18:27:41 status unpacked udev:armel 175-7.2 2013-05-02 18:27:41 status unpacked udev:armel 175-7.2 2013-05-02 18:27:41 status unpacked udev:armel 175-7.2 2013-05-02 18:27:41 status half-configured udev:armel 175-7.2 2013-05-02 18:27:49 status installed udev:armel 175-7.2 2013-05-02 18:28:05 configure libgudev-1.0-0:armel 175-7.2 none 2013-05-02 18:28:05 status unpacked libgudev-1.0-0:armel 175-7.2 2013-05-02 18:28:05 status half-configured libgudev-1.0-0:armel 175-7.2 2013-05-02 18:28:06 status installed libgudev-1.0-0:armel 175-7.2 so, it could be the new version of udev the cause of these
