Editing User:Joerg rw/PC syslog of USB enum
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
- | this is a typical log on a linux PC, of a N900 plugged into USB in power-off state, clearly showing the three stages of boot: 1) | + | this is a typical log on a linux PC, of a N900 plugged into USB in power-off state, clearly showing the three stages of boot: 1) ROM-bootloader (idProduct=0106), 2) NOLO in "update mode" (idProduct=0105), and finally maemo fremantle system in act-dead modus for charging, nevertheless obviously exporting mass "Storage Mode" (idProduct=01c7) |
Note that particularly stage1 can't be broken unless either your device already is powered up when plugging it in to PC, or your PC does block USB access ( = you forgot to blacklist *-phonet kernel modules), or USB is broken (jack came off PCB, or cable defect, or you using a hub maybe). Stage1 USB ROM bootloader is also what does coldflashing to restore a broken NOLO (stage2 not showing up in your syslog, after stage1 did), thus establishing "unbrickability" of N900. | Note that particularly stage1 can't be broken unless either your device already is powered up when plugging it in to PC, or your PC does block USB access ( = you forgot to blacklist *-phonet kernel modules), or USB is broken (jack came off PCB, or cable defect, or you using a hub maybe). Stage1 USB ROM bootloader is also what does coldflashing to restore a broken NOLO (stage2 not showing up in your syslog, after stage1 did), thus establishing "unbrickability" of N900. |
Learn more about Contributing to the wiki.