Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 14 hrs, 45 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 3 hrs ago - more...
|
2010-12-11
, 01:34
|
|
Posts: 701 |
Thanked: 585 times |
Joined on Sep 2010
@ London, England
|
#542
|
You'll need the devel repos, the latest in testing is v42. The main difference between v45 and v46 is that v45 has uboot, and v46 doesn't. Unless you want uboot, just enable the devel repo and install the latest version.
Also, "apt-cache showpkg <packagename> will give you information about all the versions of packages available in the repos you have selected and which repos they are in.
Also, "apt-cache showpkg <packagename> will give you information about all the versions of packages available in the repos you have selected and which repos they are in.
 |
|
2010-12-11
, 07:06
|
|
Posts: 28 |
Thanked: 24 times |
Joined on Feb 2010
|
#543
|
i thought today about connecting a web cam to myN900, i still haven't started experimenting with it, so i was just asking if anyone have already tried that ?
the camera works out of the box under ubuntu, it should be supported by v4l2.
so if the webcam works what software would be used with it on the n900 and can it record video from the webcam ?
My usb connector came out completely, and as the phone got no warranty i fixed it myself, but because it was very hard to connect all the pins back on the board i didn't connect the ID pin,
i know that this pin is used by USB OTG, so how will this affect my device ?
while i was fixing the usb connector i noticed the +5v pin of the usb connector was connected directly to a very small fuse, did anyone else notice that ? , its shown too on the phone schematic
what happens if you would short out the +5V and GND of the n900 USB connector. did anyone blow that fuse or its rated above the 200mA the port can deliver and no one should worry about it ?!
the camera works out of the box under ubuntu, it should be supported by v4l2.
so if the webcam works what software would be used with it on the n900 and can it record video from the webcam ?
My usb connector came out completely, and as the phone got no warranty i fixed it myself, but because it was very hard to connect all the pins back on the board i didn't connect the ID pin,
i know that this pin is used by USB OTG, so how will this affect my device ?
while i was fixing the usb connector i noticed the +5v pin of the usb connector was connected directly to a very small fuse, did anyone else notice that ? , its shown too on the phone schematic
what happens if you would short out the +5V and GND of the n900 USB connector. did anyone blow that fuse or its rated above the 200mA the port can deliver and no one should worry about it ?!
 |
|
2010-12-11
, 14:39
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#544
|
Originally Posted by Helmy
Search this and the more appropriate "problems"-thread .
i thought today about connecting a web cam to myN900, i still haven't started experimenting with it, so i was just asking if anyone have already tried that ?
the camera works out of the box under ubuntu, it should be supported by v4l2.
so if the webcam works what software would be used with it on the n900 and can it record video from the webcam ?
Please see post #9 of this thread, about topic of the thread.
Originally Posted by Helmy
The ID pin isn't needed for h-e-n hostmode.
My usb connector came out completely, and as the phone got no warranty i fixed it myself, but because it was very hard to connect all the pins back on the board i didn't connect the ID pin,
i know that this pin is used by USB OTG, so how will this affect my device ?
Originally Posted by Helmy
The fuse is a 2A, and most likely a self-resetting fuse that doesn't blow in the usual sense. I.E. nobody should worry.
while i was fixing the usb connector i noticed the +5v pin of the usb connector was connected directly to a very small fuse, did anyone else notice that ? , its shown too on the phone schematic
what happens if you would short out the +5V and GND of the n900 USB connector. did anyone blow that fuse or its rated above the 200mA the port can deliver and no one should worry about it ?!
/j
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
| The Following User Says Thank You to joerg_rw For This Useful Post: | ||
 |
|
2010-12-11
, 18:50
|
|
Posts: 330 |
Thanked: 483 times |
Joined on Dec 2010
@ Norwich, UK
|
#545
|
Originally Posted by retsaw
Is there any way to multiboot between the stable (non host mode) kernel and the devel one? Or is there no serious problems that I may cause by installing the devel?
You'll need the devel repos, the latest in testing is v42. The main difference between v45 and v46 is that v45 has uboot, and v46 doesn't. Unless you want uboot, just enable the devel repo and install the latest version.
EDIT:
Just installed v46 and h.e.n and I have to say this community is amazing. I honestly had no idea how easy it is to use this fantastic piece of software. Tested on high performance flash drive with 2 partitions and both were mounted with no problems.
I was also pleasantly surprised that OCing worked as before. Thanks to everyone involved
Last edited by FRuMMaGe; 2010-12-11 at 20:47.
| The Following User Says Thank You to FRuMMaGe For This Useful Post: | ||
|
|
2010-12-11
, 22:33
|
|
Posts: 543 |
Thanked: 151 times |
Joined on Feb 2010
@ Germany
|
#546
|
For me everything is working just fine 
I tested several USB sticks / drives and even 500GB HDDs are instantly detected and can be really fast accessed. I'm simply impressed!
I use this Adapter which I bought from a German Ebay shop: http://cgi.ebay.de/ws/eBayISAPI.dll?...=STRK:MEWNX:IT (1,00€)
This one to get additional power for HDDs and stuff: http://cgi.ebay.de/ws/eBayISAPI.dll?...=STRK:MEWNX:IT (3,89€)
I tested afterwards other devices like several Logitech USB mouses and they all worked fine with extmou (Also wireless ones!). I only noticed that I can't click anything inside the default browser and that some applications like Firefox don't show the mouse cursor.
USB keyboards with extkbd didn't worked for me at all, the 3 LEDs blink once and nothing happens. Sometimes extkbd stucks at 100% CPU when I try to configure the keyboard, so far no success.
Keep up the good work
I tested several USB sticks / drives and even 500GB HDDs are instantly detected and can be really fast accessed. I'm simply impressed!
I use this Adapter which I bought from a German Ebay shop: http://cgi.ebay.de/ws/eBayISAPI.dll?...=STRK:MEWNX:IT (1,00€)
This one to get additional power for HDDs and stuff: http://cgi.ebay.de/ws/eBayISAPI.dll?...=STRK:MEWNX:IT (3,89€)
I tested afterwards other devices like several Logitech USB mouses and they all worked fine with extmou (Also wireless ones!). I only noticed that I can't click anything inside the default browser and that some applications like Firefox don't show the mouse cursor.
USB keyboards with extkbd didn't worked for me at all, the 3 LEDs blink once and nothing happens. Sometimes extkbd stucks at 100% CPU when I try to configure the keyboard, so far no success.
Keep up the good work
|
|
2010-12-11
, 23:46
|
|
Posts: 28 |
Thanked: 24 times |
Joined on Feb 2010
|
#547
|
Originally Posted by joerg_rw
The fuse is a normal fuse consisting of a thin wire across a ceramic core , the wire thickness as i saw under a microscope is very thin it can never be 2A fuse, i saw its says 2.0A in the schematic but still it may be a mistake , maybe !
Search this and the more appropriate "problems"-thread .
Please see post #9 of this thread, about topic of the thread.
The ID pin isn't needed for h-e-n hostmode.
The fuse is a 2A, and most likely a self-resetting fuse that doesn't blow in the usual sense. I.E. nobody should worry.
/j
so what I'm asking here is did anyone short out the 5V with GND while a USB device was connected and the phone was supplying power to it ?
Last edited by Helmy; 2010-12-11 at 23:55.
|
|
2010-12-12
, 00:58
|
|
Posts: 701 |
Thanked: 585 times |
Joined on Sep 2010
@ London, England
|
#548
|
Have you forgotten that it also charges through the USB port, the included wall charger outputs 1.2A, so I'd expect the fuse to take at least 1.5A to give a safety margin (you don't want the fuse to be blown in the course of normal charging). The fuse is likely to be protection against dodgy chargers or a faulty charge circuit.
I doubt the fuse has anything to do with hostmode, in theory if shorted in hostmode it should detect this and cut the power (it does on my netbook), but I certainly won't volunteer my N900 to see what happens.
I doubt the fuse has anything to do with hostmode, in theory if shorted in hostmode it should detect this and cut the power (it does on my netbook), but I certainly won't volunteer my N900 to see what happens.
| The Following 2 Users Say Thank You to retsaw For This Useful Post: | ||
|
|
2010-12-12
, 06:07
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#549
|
test of today's release of "uboot for powerkernel v46" - in maemo-devel, and most recent h-e-n hostmode GUI as of today, on a pr1.1.1 system (yes!) with a custom kernel:
installation of uboot-pk-v46 went fine and pulled in pk as a dependency as supposed.
Not showing any of the usual warning dialogs though that usually come with pk.
uboot bootmenu showing fine, boot to system OK.
(installed backup-menu after that, and it also worked as expected)
installation of h-e-n GUI listed pk-v46 as a dependency that gets installed, obviously the dependencies of h-e-n aren't satisfied by uboot-pk-v46.
I refused to accept the warning dialog that showed up for pk this time ("click outside gray area...") -> HAM rises error notifier "installation wasn't possible"
Nevertheless h-e-n got installed
Clicking Icon doesn't work, running `update-sudoers` from a rootshell fixed this (why is the file so awkwardly named? ->"/etc/sudoers.d/hostmode.sudoers.dpkg-new")
after that h-e-n works like expected, until mounting.
error:"sh: /opt/h-e-n/mount.sh: Permission denied"
in a rootsh `chmod u+x /opt/h-e-n/mount.sh` fixed this, for the first time I tested. For some weird reason h-e-n wasn't able to call ` /opt/h-e-n/mount.sh --mount` after this initial success, on all my tests. I guess there's some bug in h-e-n regarding the mount button.
A manual call, in a rootshell, of ` /opt/h-e-n/mount.sh --mount` worked just fine
Maybe of interest: the unmount button works like expected. (checked by inserting "set -vx" at top of /opt/h-e-n/mount.sh)
[edit] unchecking the settings->"open fm after mount" seems fixed the mount button[/edit]
settings->default-filemanager: is locked, i.e it's empty and I can't change it. Not even after ticking above checkmark and closing/restarting h-e-n
The help text is using USB1.1 as descriptive term for both fullspeed and lowspeed. I suggest to check if that's not LS=USB1.0, and maybe even change the button labels to the more clear USBx.y terms rather than the HS/FS/LS. Also a sort order left=low, right=high would be more intuitive, I.E.: [USB1.0] [USB1.1] [USB2.0] for the three buttons.
[VBUS boost] should become a checkmark widget above those three buttons, and hitting any of the 3 would do both select speed and - according to VBUS checkmark - enable vboost same moment. The three speed buttons then change to a single [STOP] button.
Sidenote: it seems you need to be patient when hitting the buttons. My pendrive needs some 8s after vboost enable, and then again several seconds after ENUM, until kernel finally created device sda{1}. Prior to that 'mount' won't work I guess
bottom line: some weirdness might have come in by HAM aborting the installation as a result of me refusing to accept installation of pk. This probably resulted in postinstall script never being executed, which might explain the missing permissions and update-sudoers run.
The mount-button breakage I guess is related to inconsistencies between my 1.1.1 filesystem and pathes, and what h-e-n GUI expects to find for HFM. However this shouldn't cause the mount button to become dysfunctional
for the rest of it: nice work Mohammad. Thanks a lot
cheers
jOERG
Last edited by joerg_rw; 2010-12-12 at 06:54.
installation of uboot-pk-v46 went fine and pulled in pk as a dependency as supposed.
Not showing any of the usual warning dialogs though that usually come with pk.
uboot bootmenu showing fine, boot to system OK.
(installed backup-menu after that, and it also worked as expected)
installation of h-e-n GUI listed pk-v46 as a dependency that gets installed, obviously the dependencies of h-e-n aren't satisfied by uboot-pk-v46.
I refused to accept the warning dialog that showed up for pk this time ("click outside gray area...") -> HAM rises error notifier "installation wasn't possible"
Nevertheless h-e-n got installed
Clicking Icon doesn't work, running `update-sudoers` from a rootshell fixed this (why is the file so awkwardly named? ->"/etc/sudoers.d/hostmode.sudoers.dpkg-new")
after that h-e-n works like expected, until mounting.
error:"sh: /opt/h-e-n/mount.sh: Permission denied"
in a rootsh `chmod u+x /opt/h-e-n/mount.sh` fixed this, for the first time I tested. For some weird reason h-e-n wasn't able to call ` /opt/h-e-n/mount.sh --mount` after this initial success, on all my tests. I guess there's some bug in h-e-n regarding the mount button.
A manual call, in a rootshell, of ` /opt/h-e-n/mount.sh --mount` worked just fine
Maybe of interest: the unmount button works like expected. (checked by inserting "set -vx" at top of /opt/h-e-n/mount.sh)
[edit] unchecking the settings->"open fm after mount" seems fixed the mount button[/edit]
settings->default-filemanager: is locked, i.e it's empty and I can't change it. Not even after ticking above checkmark and closing/restarting h-e-n
The help text is using USB1.1 as descriptive term for both fullspeed and lowspeed. I suggest to check if that's not LS=USB1.0, and maybe even change the button labels to the more clear USBx.y terms rather than the HS/FS/LS. Also a sort order left=low, right=high would be more intuitive, I.E.: [USB1.0] [USB1.1] [USB2.0] for the three buttons.
[VBUS boost] should become a checkmark widget above those three buttons, and hitting any of the 3 would do both select speed and - according to VBUS checkmark - enable vboost same moment. The three speed buttons then change to a single [STOP] button.
Sidenote: it seems you need to be patient when hitting the buttons. My pendrive needs some 8s after vboost enable, and then again several seconds after ENUM, until kernel finally created device sda{1}. Prior to that 'mount' won't work I guess
bottom line: some weirdness might have come in by HAM aborting the installation as a result of me refusing to accept installation of pk. This probably resulted in postinstall script never being executed, which might explain the missing permissions and update-sudoers run.
The mount-button breakage I guess is related to inconsistencies between my 1.1.1 filesystem and pathes, and what h-e-n GUI expects to find for HFM. However this shouldn't cause the mount button to become dysfunctional
for the rest of it: nice work Mohammad. Thanks a lot
cheers
jOERG
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Last edited by joerg_rw; 2010-12-12 at 06:54.
| The Following 7 Users Say Thank You to joerg_rw For This Useful Post: | ||
|
|
2010-12-12
, 07:43
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#550
|
t900:~# udevadm monitor
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent
UEVENT[1292139844.895416] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292139844.898223] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292139844.915222] add /class/scsi_host/host6 (scsi_host)
UDEV [1292139844.920135] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292139844.985168] add /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UEVENT[1292139844.986419] add /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UEVENT[1292139844.987426] add /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292139844.988403] add /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292139845.130371] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292139845.139709] add /class/scsi_host/host6 (scsi_host)
UDEV [1292139845.147888] add /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UDEV [1292139845.156921] add /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292139845.165771] add /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UDEV [1292139845.171905] add /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292139849.999999] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292139850.003967] add /class/scsi_disk/6:0:0:0 (scsi_disk)
UEVENT[1292139850.009216] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292139850.221099] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292139850.222442] add /block/sda/sda1 (block)
UEVENT[1292139850.223907] add /class/bdi/8:0 (bdi)
UEVENT[1292139850.227752] add /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292139850.261840] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292139850.263275] add /class/scsi_disk/6:0:0:0 (scsi_disk)
UDEV [1292139850.272369] add /class/bdi/8:0 (bdi)
UDEV [1292139850.279541] add /block/sda (block)
UDEV [1292139850.283782] add /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292139850.335357] add /block/sda/sda1 (block)
#vboost off, on; enumerate
UEVENT[1292140015.841522] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140015.847076] remove /block/sda/sda1 (block)
UDEV [1292140015.983337] remove /block/sda/sda1 (block)
UDEV [1292140015.992675] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140017.473510] remove /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UEVENT[1292140017.477569] remove /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UEVENT[1292140017.481292] remove /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292140017.485259] remove /class/scsi_device/6:0:0:0 (scsi_device)
UEVENT[1292140017.488861] remove /class/scsi_disk/6:0:0:0 (scsi_disk)
UEVENT[1292140017.492736] remove /class/bdi/8:0 (bdi)
UEVENT[1292140017.496276] remove /block/sda (block)
UEVENT[1292140017.499755] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140017.503326] remove /class/scsi_host/host6 (scsi_host)
UEVENT[1292140017.508026] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292140017.510101] remove /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UEVENT[1292140017.513793] remove /devices/platform/musb_hdrc/usb1/1-1 (usb)
UDEV [1292140017.527557] remove /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292140017.533477] remove /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UDEV [1292140017.538482] remove /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UDEV [1292140017.543518] remove /class/bdi/8:0 (bdi)
UDEV [1292140017.548980] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292140017.550231] remove /class/scsi_disk/6:0:0:0 (scsi_disk)
UDEV [1292140017.554626] remove /class/scsi_host/host6 (scsi_host)
UDEV [1292140017.563079] remove /block/sda (block)
UDEV [1292140017.598205] remove /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292140017.604553] remove /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UDEV [1292140017.690521] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292140017.729675] remove /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140017.949890] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140017.952667] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292140017.969390] add /class/scsi_host/host7 (scsi_host)
UDEV [1292140017.973358] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140018.033996] add /class/usb_endpoint/usbdev1.17_ep01 (usb_endpoint)
UEVENT[1292140018.034545] add /class/usb_endpoint/usbdev1.17_ep82 (usb_endpoint)
UEVENT[1292140018.034820] add /class/usb_endpoint/usbdev1.17_ep83 (usb_endpoint)
UEVENT[1292140018.035095] add /class/usb_endpoint/usbdev1.17_ep00 (usb_endpoint)
UDEV [1292140018.171661] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292140018.193603] add /class/usb_endpoint/usbdev1.17_ep01 (usb_endpoint)
UDEV [1292140018.195465] add /class/usb_endpoint/usbdev1.17_ep82 (usb_endpoint)
UDEV [1292140018.198455] add /class/scsi_host/host7 (scsi_host)
UDEV [1292140018.205047] add /class/usb_endpoint/usbdev1.17_ep83 (usb_endpoint)
UDEV [1292140018.210876] add /class/usb_endpoint/usbdev1.17_ep00 (usb_endpoint)
UEVENT[1292140023.038940] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UEVENT[1292140023.042968] add /class/scsi_disk/7:0:0:0 (scsi_disk)
UEVENT[1292140023.048278] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.238189] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.239624] add /class/bdi/8:0 (bdi)
UEVENT[1292140023.240722] add /class/bdi/8:0 (bdi)
UEVENT[1292140023.242645] add /class/scsi_device/7:0:0:0 (scsi_device)
UDEV [1292140023.258483] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.270721] add /class/scsi_disk/7:0:0:0 (scsi_disk)
UDEV [1292140023.288391] add /block/sda (block)
UDEV [1292140023.291992] add /class/scsi_device/7:0:0:0 (scsi_device)
UDEV [1292140023.327728] add /block/sda/sda1 (block)
HFM (and also hulda?) doesn't like when you hit vboost-stop in h-e-n (well, I also applied external VBUS, and started bme):
Dec 12 08:55:55 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 08:55:55 t900 last message repeated 42 times
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - Failed to create monitor for path file:///media/sda1
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - error accessing 'file:///media/sda1': File not found
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - Failed to create monitor for path file:///media/sda1
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - error accessing 'file:///media/sda1': File not found
...
Dec 12 08:56:36 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 08:57:07 t900 last message repeated 122991 times
Dec 12 08:58:08 t900 last message repeated 252652 times
Dec 12 08:59:09 t900 last message repeated 253458 times
Dec 12 09:00:10 t900 last message repeated 252588 times
Dec 12 09:01:05 t900 last message repeated 231701 times
Dec 12 09:01:05 t900 iphbd: client with socket 9 disappeared
Dec 12 09:01:05 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 11190 times
Dec 12 09:01:09 t900 [2363]: GLIB CRITICAL ** default - free_async_operations_list: assertion `gAttachmentsOperList && g_list_length (gAttachmentsOperList) > 0' failed
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Goodbye! modest-nokiamessaging-plugin is being unloaded
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 30 times
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Unloaded!
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 1188 times
Dec 12 09:01:09 t900 maemo-launcher[966]: child (pid=2363) terminated due to exit()=0
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:40 t900 last message repeated 125470 times
Dec 12 09:02:02 t900 last message repeated 92220 times
Dec 12 09:02:02 t900 kernel: [ 7761.922119] kb_lock (GPIO 113) is now closed
Dec 12 09:02:02 t900 systemui-tklock[974]: Method call received from: :1.12, iface: com.nokia.system_ui.request, method: tklock_close
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 582 times
Dec 12 09:02:02 t900 browser[1786]: GLIB CRITICAL ** default - download_mgr_update_current: assertion `self->cur_item' failed
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 28 times
Dec 12 09:02:02 t900 kernel: [ 7762.258117] kb_lock (GPIO 113) is now open
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:33 t900 last message repeated 116783 times
Dec 12 09:01:05 t900 last message repeated 231701 times
Dec 12 09:01:05 t900 iphbd: client with socket 9 disappeared
Dec 12 09:01:05 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 11190 times
Dec 12 09:01:09 t900 [2363]: GLIB CRITICAL ** default - free_async_operations_list: assertion `gAttachmentsOperList && g_list_length (gAttachmentsOperList) > 0' failed
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Goodbye! modest-nokiamessaging-plugin is being unloaded
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 30 times
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Unloaded!
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 1188 times
Dec 12 09:01:09 t900 maemo-launcher[966]: child (pid=2363) terminated due to exit()=0
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:40 t900 last message repeated 125470 times
Dec 12 09:02:02 t900 last message repeated 92220 times
Dec 12 09:02:02 t900 kernel: [ 7761.922119] kb_lock (GPIO 113) is now closed
Dec 12 09:02:02 t900 systemui-tklock[974]: Method call received from: :1.12, iface: com.nokia.system_ui.request, method: tklock_close
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 582 times
Dec 12 09:02:02 t900 browser[1786]: GLIB CRITICAL ** default - download_mgr_update_current: assertion `self->cur_item' failed
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 28 times
Dec 12 09:02:02 t900 kernel: [ 7762.258117] kb_lock (GPIO 113) is now open
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:33 t900 last message repeated 116783 times
Found no other way to stop that madness, other than reboot
:-o
Last edited by joerg_rw; 2010-12-12 at 08:09.
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent
UEVENT[1292139844.895416] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292139844.898223] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292139844.915222] add /class/scsi_host/host6 (scsi_host)
UDEV [1292139844.920135] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292139844.985168] add /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UEVENT[1292139844.986419] add /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UEVENT[1292139844.987426] add /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292139844.988403] add /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292139845.130371] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292139845.139709] add /class/scsi_host/host6 (scsi_host)
UDEV [1292139845.147888] add /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UDEV [1292139845.156921] add /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292139845.165771] add /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UDEV [1292139845.171905] add /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292139849.999999] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292139850.003967] add /class/scsi_disk/6:0:0:0 (scsi_disk)
UEVENT[1292139850.009216] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292139850.221099] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292139850.222442] add /block/sda/sda1 (block)
UEVENT[1292139850.223907] add /class/bdi/8:0 (bdi)
UEVENT[1292139850.227752] add /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292139850.261840] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292139850.263275] add /class/scsi_disk/6:0:0:0 (scsi_disk)
UDEV [1292139850.272369] add /class/bdi/8:0 (bdi)
UDEV [1292139850.279541] add /block/sda (block)
UDEV [1292139850.283782] add /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292139850.335357] add /block/sda/sda1 (block)
#vboost off, on; enumerate
UEVENT[1292140015.841522] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140015.847076] remove /block/sda/sda1 (block)
UDEV [1292140015.983337] remove /block/sda/sda1 (block)
UDEV [1292140015.992675] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140017.473510] remove /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UEVENT[1292140017.477569] remove /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UEVENT[1292140017.481292] remove /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UEVENT[1292140017.485259] remove /class/scsi_device/6:0:0:0 (scsi_device)
UEVENT[1292140017.488861] remove /class/scsi_disk/6:0:0:0 (scsi_disk)
UEVENT[1292140017.492736] remove /class/bdi/8:0 (bdi)
UEVENT[1292140017.496276] remove /block/sda (block)
UEVENT[1292140017.499755] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UEVENT[1292140017.503326] remove /class/scsi_host/host6 (scsi_host)
UEVENT[1292140017.508026] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292140017.510101] remove /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UEVENT[1292140017.513793] remove /devices/platform/musb_hdrc/usb1/1-1 (usb)
UDEV [1292140017.527557] remove /class/scsi_device/6:0:0:0 (scsi_device)
UDEV [1292140017.533477] remove /class/usb_endpoint/usbdev1.16_ep83 (usb_endpoint)
UDEV [1292140017.538482] remove /class/usb_endpoint/usbdev1.16_ep82 (usb_endpoint)
UDEV [1292140017.543518] remove /class/bdi/8:0 (bdi)
UDEV [1292140017.548980] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0 (scsi)
UDEV [1292140017.550231] remove /class/scsi_disk/6:0:0:0 (scsi_disk)
UDEV [1292140017.554626] remove /class/scsi_host/host6 (scsi_host)
UDEV [1292140017.563079] remove /block/sda (block)
UDEV [1292140017.598205] remove /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1292140017.604553] remove /class/usb_endpoint/usbdev1.16_ep01 (usb_endpoint)
UDEV [1292140017.690521] remove /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292140017.729675] remove /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140017.949890] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140017.952667] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UEVENT[1292140017.969390] add /class/scsi_host/host7 (scsi_host)
UDEV [1292140017.973358] add /devices/platform/musb_hdrc/usb1/1-1 (usb)
UEVENT[1292140018.033996] add /class/usb_endpoint/usbdev1.17_ep01 (usb_endpoint)
UEVENT[1292140018.034545] add /class/usb_endpoint/usbdev1.17_ep82 (usb_endpoint)
UEVENT[1292140018.034820] add /class/usb_endpoint/usbdev1.17_ep83 (usb_endpoint)
UEVENT[1292140018.035095] add /class/usb_endpoint/usbdev1.17_ep00 (usb_endpoint)
UDEV [1292140018.171661] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0 (usb)
UDEV [1292140018.193603] add /class/usb_endpoint/usbdev1.17_ep01 (usb_endpoint)
UDEV [1292140018.195465] add /class/usb_endpoint/usbdev1.17_ep82 (usb_endpoint)
UDEV [1292140018.198455] add /class/scsi_host/host7 (scsi_host)
UDEV [1292140018.205047] add /class/usb_endpoint/usbdev1.17_ep83 (usb_endpoint)
UDEV [1292140018.210876] add /class/usb_endpoint/usbdev1.17_ep00 (usb_endpoint)
UEVENT[1292140023.038940] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UEVENT[1292140023.042968] add /class/scsi_disk/7:0:0:0 (scsi_disk)
UEVENT[1292140023.048278] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.238189] add /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.239624] add /class/bdi/8:0 (bdi)
UEVENT[1292140023.240722] add /class/bdi/8:0 (bdi)
UEVENT[1292140023.242645] add /class/scsi_device/7:0:0:0 (scsi_device)
UDEV [1292140023.258483] change /devices/platform/musb_hdrc/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0 (scsi)
UDEV [1292140023.270721] add /class/scsi_disk/7:0:0:0 (scsi_disk)
UDEV [1292140023.288391] add /block/sda (block)
UDEV [1292140023.291992] add /class/scsi_device/7:0:0:0 (scsi_device)
UDEV [1292140023.327728] add /block/sda/sda1 (block)
HFM (and also hulda?) doesn't like when you hit vboost-stop in h-e-n (well, I also applied external VBUS, and started bme):
Dec 12 08:55:55 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 08:55:55 t900 last message repeated 42 times
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - Failed to create monitor for path file:///media/sda1
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - error accessing 'file:///media/sda1': File not found
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - Failed to create monitor for path file:///media/sda1
Dec 12 08:55:55 t900 ossofilemanager[3363]: GLIB WARNING ** hildon-fm - error accessing 'file:///media/sda1': File not found
...
Dec 12 08:56:36 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 08:57:07 t900 last message repeated 122991 times
Dec 12 08:58:08 t900 last message repeated 252652 times
Dec 12 08:59:09 t900 last message repeated 253458 times
Dec 12 09:00:10 t900 last message repeated 252588 times
Dec 12 09:01:05 t900 last message repeated 231701 times
Dec 12 09:01:05 t900 iphbd: client with socket 9 disappeared
Dec 12 09:01:05 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 11190 times
Dec 12 09:01:09 t900 [2363]: GLIB CRITICAL ** default - free_async_operations_list: assertion `gAttachmentsOperList && g_list_length (gAttachmentsOperList) > 0' failed
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Goodbye! modest-nokiamessaging-plugin is being unloaded
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 30 times
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Unloaded!
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 1188 times
Dec 12 09:01:09 t900 maemo-launcher[966]: child (pid=2363) terminated due to exit()=0
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:40 t900 last message repeated 125470 times
Dec 12 09:02:02 t900 last message repeated 92220 times
Dec 12 09:02:02 t900 kernel: [ 7761.922119] kb_lock (GPIO 113) is now closed
Dec 12 09:02:02 t900 systemui-tklock[974]: Method call received from: :1.12, iface: com.nokia.system_ui.request, method: tklock_close
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 582 times
Dec 12 09:02:02 t900 browser[1786]: GLIB CRITICAL ** default - download_mgr_update_current: assertion `self->cur_item' failed
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 28 times
Dec 12 09:02:02 t900 kernel: [ 7762.258117] kb_lock (GPIO 113) is now open
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:33 t900 last message repeated 116783 times
Dec 12 09:01:05 t900 last message repeated 231701 times
Dec 12 09:01:05 t900 iphbd: client with socket 9 disappeared
Dec 12 09:01:05 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 11190 times
Dec 12 09:01:09 t900 [2363]: GLIB CRITICAL ** default - free_async_operations_list: assertion `gAttachmentsOperList && g_list_length (gAttachmentsOperList) > 0' failed
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Goodbye! modest-nokiamessaging-plugin is being unloaded
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 30 times
Dec 12 09:01:09 t900 [2363]: GLIB MESSAGE default - Unloaded!
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:09 t900 last message repeated 1188 times
Dec 12 09:01:09 t900 maemo-launcher[966]: child (pid=2363) terminated due to exit()=0
Dec 12 09:01:09 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:01:40 t900 last message repeated 125470 times
Dec 12 09:02:02 t900 last message repeated 92220 times
Dec 12 09:02:02 t900 kernel: [ 7761.922119] kb_lock (GPIO 113) is now closed
Dec 12 09:02:02 t900 systemui-tklock[974]: Method call received from: :1.12, iface: com.nokia.system_ui.request, method: tklock_close
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 582 times
Dec 12 09:02:02 t900 browser[1786]: GLIB CRITICAL ** default - download_mgr_update_current: assertion `self->cur_item' failed
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:02 t900 last message repeated 28 times
Dec 12 09:02:02 t900 kernel: [ 7762.258117] kb_lock (GPIO 113) is now open
Dec 12 09:02:02 t900 hulda[1238]: kdbus_sock_cb:204: unknown GIOCondition 9 for FD 7
Dec 12 09:02:33 t900 last message repeated 116783 times
PID PPID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
1238 667 root 20 0 5884 1420 1308 R 66.0 0.6 15:48.36 /usr/sbin/hulda
681 1 root 20 0 1620 568 516 S 26.0 0.2 6:31.50 /sbin/syslogd -n
:-o
__________________
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Maemo Community Council member [2012-10, 2013-05, 2013-11, 2014-06 terms]
Hildon Foundation Council inaugural member.
MCe.V. foundation member
EX Hildon Foundation approved Maemo Administration Coordinator (stepped down due to bullying 2014-04-05)
aka "techstaff" - the guys who keep your infra running - Devotion to Duty http://xkcd.com/705/
IRC(freenode): DocScrutinizer*
First USB hostmode fanatic, father of H-E-N
Last edited by joerg_rw; 2010-12-12 at 08:09.
| The Following 3 Users Say Thank You to joerg_rw For This Useful Post: | ||
Sorry for the ignorance, I looked at the description in package manager but can't find anything about a version number