**** BEGIN LOGGING AT Fri Sep 24 10:52:15 2010 Sep 24 13:43:46 can I use debs for maemo in Maverick? Sep 24 13:45:05 thought I'd try x2goclient on my igepv2 and see if it's a viable thinclient in my environment, but the only ARM packages I can find is for maemo. Sep 24 13:47:59 persia: thanks for the review, will go over it later today Sep 24 13:54:29 oh, did he find aynthing ? Sep 24 13:54:38 * ogra didnt get any inof about it Sep 24 13:55:36 just can't get inof? :) Sep 24 13:57:00 ogra: sent just for me, will go over the list then and ask you a new review :-) Sep 24 13:57:07 if we're fine, we can try to push them Sep 24 14:00:35 rsalveti, awesome Sep 24 14:07:11 jo-erlend, if you can get a source package, rebuilding it is probably straightforward; otherwise, the deb may or may not work, depending on a bunch of stuff Sep 24 14:07:33 I've never created a package before. Sep 24 14:09:33 rsalveti, Mind you, it's *very* pedantic: don't worry if some things turn out to be annoying or hard. Sep 24 14:10:16 is there any way to bypass oem-install on first boot? Sep 24 14:11:09 isbric, There are a bunch of ways, but that would leave you without a user. What are you seeking to accomplish? Sep 24 14:11:58 http://elinux.org/BeagleBoardUbuntu#Lucid_10.04.1 Sep 24 14:12:20 i dont have a monitor, thats the main problem Sep 24 14:13:21 persia: sure, np :-) Sep 24 14:13:26 "Note: On first boot, you must use an DVI/LCD monitor, oem-config seems to force tty0.. 2nd boot you can switch to serial by default.." Sep 24 14:15:36 persia: trying to finish the install with ttyS0 Sep 24 14:20:20 isbric, Ah. I understand. I think there's no way to complete it with the current images. Sep 24 14:20:54 I think you'd need to build new images that used the debconf front-end for configuration, but I don't know that anyone defined an oem-config harness for that interface. Sep 24 14:32:06 jo-erlend, sorry, went afk Sep 24 14:32:11 jo-erlend, that's not what I asked :p Sep 24 14:32:35 cwillu_at_work, did you ask me anything? Sep 24 14:32:51 jo-erlend, if you can get a source package for the deb, then there's a good chance that dpkg-buildpackage will Just Work and give you a working binary deb that you can then Just Install. Sep 24 14:33:01 jo-erlend, I didn't use a question mark :p Sep 24 14:33:05 really? That'd be nice. Sep 24 14:33:10 I'll have to look into that. Sep 24 14:33:14 jo-erlend, you on ubuntu right now? Sep 24 14:33:18 yes. Sep 24 14:33:30 jo-erlend, open a terminal, make an empty directory, cd into that directory Sep 24 14:34:11 next, apt-get build-dep xsplash Sep 24 14:34:18 next, apt-get source xsplash Sep 24 14:34:19 seems they don't make source debs available. They publish tar.gz packages only. Sep 24 14:34:38 okay; that's not impossible to deal with either :p Sep 24 14:35:03 generally, unpacking the tar.gz, and then running ./configure, then make, will compile the package Sep 24 14:35:33 if one is lazy at that point, a make install will generally install it, or you can use checkinstall to make a deb of questionable quality Sep 24 14:35:50 in many cases, that's everything you need Sep 24 14:35:54 checkinstall is new to me. Sep 24 14:36:00 !checkinstall Sep 24 14:36:01 checkinstall is a wrapper to "make install", useful for installing programs you compiled. It will create a .deb package, which will be listed in the APT database and can be uninstalled like other packages. See https://help.ubuntu.com/community/CheckInstall - Read the warnings at the top and bottom of that web page, and DO NOT interrupt CheckInstall while it's running! Sep 24 14:36:55 thanks. I'll go read now. :) Sep 24 14:37:04 more fun to just dive in :) Sep 24 14:38:45 hehe, not when things go wrong and you have to spend a week fixing the problems you wouldn't have had if you spent the ten minutes reading the manual first. :) Sep 24 14:44:36 ok, I've give it a go. Thanks. :) Sep 24 15:34:27 * rsalveti lunch Sep 24 16:01:34 morning Sep 24 16:03:40 are there any know USB bugs on IGEPv2 or Beagle board? Sep 24 16:04:10 i searched in launchpad and found nothing, maybe I am doing someting wrong Sep 24 16:04:34 there are known HW bugs with beagle afaik Sep 24 16:04:56 with the pre-C4 boards Sep 24 16:05:13 ogra: the problem is that a device only works if pluged on start up Sep 24 16:05:30 and if i take it out, and try to put something there again, it will not enumerate Sep 24 16:05:45 what board specifically (nobody here has an IGEP2) Sep 24 16:05:55 I have :D Sep 24 16:06:18 well, let me rephrase ... what beagle ? :) Sep 24 16:06:24 http://pastebin.ubuntu.com/499799/ Sep 24 16:06:27 which revision Sep 24 16:06:32 ahh Sep 24 16:06:48 IGEPv2 revision 3 Sep 24 16:06:58 its one of the most recents one Sep 24 16:07:05 since the arm team doesnt have IGEP2 its very likely that we miss bugs there Sep 24 16:07:26 (and very unlikely that we get them fixed in time for maverick this late in the cycle, but you can try) Sep 24 16:07:50 i wouldnt expect more than one kernel upload for omap3 anymore before release though Sep 24 16:08:48 (i know there are already a bunch of IGEP2 fixes, if you can send patches along with the bug they might make it in) Sep 24 16:09:05 s/fixes/pending fixes/ Sep 24 16:09:12 problem is that i am not a programer Sep 24 16:09:29 just user, trying to put the board making sound properly Sep 24 16:09:54 rlameiro: That sounds like a bug; I think you should file it against the kernel you're running Sep 24 16:10:05 rlameiro, I have the same board and the same problem. Sep 24 16:10:11 I even bought a 30USD hub, bigger than my board to check if it was because i was using to much power on the usb rail... Sep 24 16:10:32 ogra, speaking of maverick ... is there anything that you need from me for that release ? (any more bugs, etc, etc) ? Sep 24 16:10:49 devilhorns, no, but i got you access to the upstream tree Sep 24 16:10:53 rlameiro, have you tried rsalvetis recent kernels? Sep 24 16:10:55 jo-erlend_igep: ok, so we can join forces :D Sep 24 16:10:58 devilhorns, mail coming with URL Sep 24 16:11:00 ogra, w00t ! :) thanks :) Sep 24 16:11:34 rlameiro, gladly. One big problem here, is that those who know what to do, don't have the hardware and we who have the hardware doesn't know what to do. :) Sep 24 16:11:35 lool, does linaro possibly have fixes ubuntu could pull in ? Sep 24 16:11:39 jo-erlend_igep: problem is that i Cant file bugs against other kernels that arent from ubunto or linaro Sep 24 16:11:40 * devilhorns now has to learn bzr for commits :) Sep 24 16:11:45 no one will look at them Sep 24 16:11:51 i want to fix ubuntu Sep 24 16:12:05 rlameiro, you should probably talk to the linaro guys, they might have patches for the issue we are just missing in the ubuntu kernel Sep 24 16:12:13 rlameiro, I've been acting as rsalvetis bot for a few days, and now screen and networking is working. Bluetooth and sound is not working and I cannot connect to wpa-protected wifis. Sep 24 16:12:14 ogra: I didn't hear of a fix for this specific issue Sep 24 16:12:21 lool, ok Sep 24 16:12:33 but you seem not to see it in linaro Sep 24 16:12:46 ogra: why doesnt canonical just order a board, or even ask one for free? its only 145€.... Sep 24 16:12:53 jo-erlend_igep: Oh WPA was working for me with libertas-firmware Sep 24 16:13:04 ogra: I didn't say that Sep 24 16:13:06 rlameiro, we'll likely do that for natty ... Sep 24 16:13:18 lool, no, was an assumption i shamelessly made :) Sep 24 16:13:32 rlameiro: You're asking weird things :-) Sep 24 16:13:48 free boards? Sep 24 16:13:49 rlameiro: In any case, Linaro is also trying to support IGEP in their own OMAP kernels, and we do have some IGEPs Sep 24 16:13:59 lool, really? I have installed libertas-firmware. Sep 24 16:14:00 rlameiro, for maverick our main focus is and was omap4, we also did omap3 but only focusing on beagle C4 and XM Sep 24 16:14:05 free board is awesome :P Sep 24 16:14:25 for natty we might add IGEP2 to our list of HW to work with Sep 24 16:14:31 rlameiro: You're asking Canonical to spend money and (more importantly) engineering time on IGEP; if you wonder why it's not being done, it's just because of the cost versus other things we could work on :-) Sep 24 16:14:35 ogra: I got that, only problem is that almost no one has omap4, but omap3 Sep 24 16:14:44 anyway, it is not my bussines anyway Sep 24 16:14:48 jo-erlend_igep: I didn't test in the last couple of weeks, but it was the only thing which worked for me, yes Sep 24 16:15:04 omap4 vs omap3 will change quickly as soon as the boards are on the market Sep 24 16:15:39 rlameiro: You're looking at the problem from the angle of "what would be the most profitable to the community", but another angle to the question is how to pay the engineers working on bugs Sep 24 16:15:40 I wonder how much faster omap4 will be IRL. Sep 24 16:15:40 ogra: true, but that means that the people that already have ompa3 boards need to go for ompa4..... Sep 24 16:16:04 lool: I will glady donate for specific things Sep 24 16:16:20 not for beagle Xm Sep 24 16:16:35 didn't we use to have "bounties"? Sep 24 16:16:35 rlameiro, well, our team is small we only have so much manpower to support three arches currently Sep 24 16:16:57 ogra: I know, and it is nothing against you, really Sep 24 16:16:57 rlameiro: This is a nice thing of you; thanks for offering that! I'm afraid Canonical itself is not setup to receive direct user donations (AFAIK), but perhaps you can offer a bounty to an interested developer/company to fix our pet bugs? Sep 24 16:17:11 people have always to much work, and to few people Sep 24 16:17:11 rlameiro, i didnt take it as something against me/us :) Sep 24 16:17:17 rlameiro: True Sep 24 16:17:53 What would be interesting is whether the bug is also present on other OMAP3 boards like beagles or beagle XMs Sep 24 16:17:53 lol, why would it be against you??? Sep 24 16:18:03 and also whether it's present in the upstream tree or not Sep 24 16:18:08 rlameiro, we like to fix bugs (and as you can see on rsalveti helping jo-erlend, we even do it actively as good as we can) Sep 24 16:18:11 It might just be a kernel config being mis-set Sep 24 16:18:21 rlameiro, the main problem is the time of release you approach us Sep 24 16:18:33 a month ago everything was easier Sep 24 16:18:50 ogra: I know. my only problem is with the "upper" people Sep 24 16:18:52 the later we get into the cycle the harder it gets to make changes Sep 24 16:19:03 which "upper" people ? Sep 24 16:19:32 they market ARM as the big bet , but then puts little engineers on it and then they need to make everything Sep 24 16:19:35 * jo-erlend_igep is really grateful for the help rsalveti has given him. Sep 24 16:19:37 we actually can work fine with community members to fix HW we dont have but that requires far more time Sep 24 16:20:09 which measn such things need to show up earlier in the cycle or they will suffer from our focus on HW we actualyl have Sep 24 16:20:17 ogra: and I really love to do that to :D Sep 24 16:20:33 I filed some bugs already and help debuging some stuff also Sep 24 16:20:39 yes, i saw that Sep 24 16:20:45 and you are doing great :) Sep 24 16:20:59 yea early on the cycle i couldnt even boot my board with ubuntu.... Sep 24 16:21:14 i also dont want to turn you down in what you do, i'm just trying to explain the situation Sep 24 16:21:37 ogra: you dont need to explain, you make a great job in here, believe me. Sep 24 16:21:40 rlameiro: Is there a LP bug # for the USB issue you mentioned earlier? Sep 24 16:21:59 if you file a bug it will definitely be taken care of ... its just not clear if it will make it into the release or has to wait for an update or worst case for next release Sep 24 16:22:05 lool: no, thats why i felt it was weird, because its a really common thing Sep 24 16:22:10 ogra: By whom? Sep 24 16:22:35 lool, for what ? Sep 24 16:22:37 rlameiro: Would be good if you could file it, explaining which devices you're testing, on which USB port etc. Sep 24 16:22:46 lool, the SRU or the next release ? Sep 24 16:22:49 ogra: You say it will be taken care of Sep 24 16:22:57 by the kernel team or us Sep 24 16:23:01 rlameiro, the USB issue, as I understand it, is that if you disconnect and reconnect a USB device, then it's not being recognized? Does this also affect keyboard and mouse? Sep 24 16:23:01 or linaro Sep 24 16:23:03 ogra: Are you folks committed to fixing OMAP3/IGEP bugs? Sep 24 16:23:08 or a combination of these Sep 24 16:23:12 no Sep 24 16:23:24 but there is interest on our side to have them fixed Sep 24 16:23:44 as there is interest to get all other omap3 HW working Sep 24 16:23:45 Oh ok, you were saying "it will definitely be taken care of", so I wondered Sep 24 16:23:49 jo-erlend_igep: yes, my mouse isnt reconigzed after I unplug something Sep 24 16:23:57 someone will do it, i'm sure Sep 24 16:23:59 rlameiro, have you tried the new kernel from rsalveti? Sep 24 16:24:29 lool, i know rsalveti cant sleep if bugs exiost in the world :) and i know mpoirier has interest in IGEP2 Sep 24 16:24:30 rlameiro, I no longer have that problem, but I remember having it in the beginning. Sep 24 16:24:43 no, jo-erlend_igep but as i said, i wanted to help debug stuff in ubuntu, but it seems i will need to use other kernels Sep 24 16:25:04 ogra: Ok; I don't want jo-erlend_igep and rlameiro to be disappointed if you say it will definitely be taken care of, but then it might not Sep 24 16:25:30 I'm certainly interested in having it in our list of Linaro IGEP bugs if it can be reproduced with Linaro kernels Sep 24 16:25:41 lool, well, given linaro uses that HW i would expect you guys to hit the same bug at some point for example ... Sep 24 16:25:52 so there might be a patch that suits both teams Sep 24 16:25:54 lool: I iam runing a linaro kerne Sep 24 16:25:58 *kernel Sep 24 16:26:07 rlameiro: And you have the same issue? Sep 24 16:26:12 lool: yes Sep 24 16:26:17 rlameiro, I'm using rsalvetis kernel. The only thing that doesn't work, is audio, bluetooth, and possible wlan. I haven't had time to really look into the wlan issues yet. Sep 24 16:26:25 lool: the most recent linaro kernel on the repos Sep 24 16:26:28 lool: you don't get cool hw anymore? :P Sep 24 16:26:37 armin76: ? Sep 24 16:26:49 armin76, IGEP2 isnt cool ? Sep 24 16:27:00 well, its not an omap4 Sep 24 16:27:13 I don't have OMAP4, no Sep 24 16:27:14 jo-erlend_igep: for the wlan, you need to put the libertas firmware in helper by hand, i am not sure if they are opensource Sep 24 16:27:15 its also not a tegra2 Sep 24 16:27:22 nor an xscale Sep 24 16:27:36 rlameiro: Nope; but the package in multiverse worked forme Sep 24 16:28:03 rlameiro, jo-erlend_igep: So would either of you please report the USB issue with the exact kernel version, USB port, and device you folks are using? Sep 24 16:28:10 IGEPv2 wat the first dev board to have LAN, wifi, bluetooth 512/512mb on the market Sep 24 16:28:24 GrueMaster, hey, i fixed the "all headers installed" issue :) Sep 24 16:28:29 lool, I no longer have that issue, so that'll be a bit difficult. Sep 24 16:28:38 cool Sep 24 16:28:38 tomorrows images will only ship the actually needed headers Sep 24 16:28:47 jo-erlend_igep: Oh you *don't* have the USB issue, so it got solved by a kernel update? Sep 24 16:28:53 Heh. Promises, promises. :P Sep 24 16:28:56 lool: where do i file it? lp? Sep 24 16:28:58 heh Sep 24 16:29:01 rlameiro: Yup Sep 24 16:29:22 rlameiro: Ideally, just "ubuntu-bug linux-linaro" or linux if you're running an Ubuntu kernel Sep 24 16:29:28 lool, I _think_ one of salvetis kernels fixed it. That is to say: I think I had the problem, but if I did, I don't anymore. :) Sep 24 16:29:40 jo-erlend_igep: hmm ok Sep 24 16:29:46 so there is a patch *somewhere* Sep 24 16:29:48 :) Sep 24 16:30:14 hidden in rsalveti's branch on the ubuntu git server i bet :) Sep 24 16:30:46 lool, not the best comment for a bug: «This was maybe fixed by something that somebody might have done.» Sep 24 16:31:34 jo-erlend_igep: Yeah Sep 24 16:31:43 I'm counting on rlameiro to file the bug though, as he is seeing it Sep 24 16:31:45 jo-erlend_igep, "that was fixed with a manual build i got from ... " Sep 24 16:31:55 ;) Sep 24 16:33:11 doing it now, plus debbuging Sep 24 16:42:57 berco: good morning Sep 24 16:43:16 Irg: good morning Sep 24 16:46:34 done lp#646985 Sep 24 16:46:43 done lp #646985 Sep 24 16:46:44 Launchpad bug 646985 in linux-linaro (Ubuntu) "[IGEPv2 board] The USB systems cease to work after an unplug event on linux linaro kernel (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/646985 Sep 24 16:48:00 lool: ping Sep 24 16:48:47 jo-erlend_igep: maybe you can comment on this bug saying what kernel you use and that you dont have the problem anymore Sep 24 16:49:33 rlameiro: Could you note which of the USB ports you're using? Sep 24 16:49:44 rlameiro: Hub/no hub and the like Sep 24 16:49:52 ok Sep 24 16:51:04 rlameiro, sure. Sep 24 16:51:35 lool: updated Sep 24 16:51:45 rlameiro: If you're tempted to compare with the Ubuntu omap kernel, that would be interesting Sep 24 16:52:08 lool: it didnt work also Sep 24 16:52:19 I'm personally kicking builds of linux and linux-omap with the Linaro OMAP; perhaps these might hint at what's wrong? Sep 24 16:52:27 rlameiro: Could you note which version you tried? Sep 24 16:52:45 wich version of the ubuntu kernel? Sep 24 16:52:45 rlameiro: If that's the latest, then I'll add a task on the Ubuntu omap kernel Sep 24 16:52:49 rlameiro: yup Sep 24 16:53:14 Grmpf, my vm went down again Sep 24 16:53:16 this is tiring Sep 24 16:53:37 * rsalveti back Sep 24 16:54:09 lool: it was this version linux-image-2.6.35-22-omap Sep 24 16:54:20 rlameiro: Do you have the version of the package as well? Sep 24 16:54:30 rlameiro: The "version" in the package name is just the ABI Sep 24 16:54:37 .33 Sep 24 16:55:12 rsalveti, I never installed the linux-firmware-image_2.6.35.4+43_armel.deb package. Should I? Sep 24 16:55:53 rlameiro: Ok, that's almost the latest kernel in Ubuntu, and the latest one doesn't seem to touch anything related Sep 24 16:56:01 jo-erlend_igep: you could, don't know if it'll make any difference for you Sep 24 16:56:08 the only ARM change is "Adding vdd_sdi regulator supply to OMAP3EVM Sep 24 16:56:09 " Sep 24 16:56:09 depends on what firmwares you actually need Sep 24 16:56:24 * rsalveti reading the backlog Sep 24 16:58:55 * rlameiro is going to eat something, bugs make him hungry Sep 24 17:01:03 * prpplague gives rlameiro some fried beattles and baked crikets Sep 24 17:04:58 jo-erlend_igep: are you sure you're using the same hardware rlameiro has? Sep 24 17:05:12 almost. Sep 24 17:05:24 rlameiro, you're using igepv2 rc? Sep 24 17:05:25 I am using a IGEPv2 rev 3 Sep 24 17:05:31 rc 3 Sep 24 17:05:56 oh. I'm using rc1. Sep 24 17:06:51 hm Sep 24 17:06:55 in the back i have RC and a 3 writen by hand Sep 24 17:07:10 jo-erlend_igep: can you check yours? Sep 24 17:07:20 in the back? Sep 24 17:07:22 rlameiro: without the usb-hub, does it also happens when you just use a mouse? Sep 24 17:08:03 rlameiro, I just did. It sais IGEP 0020 RC and then a hand written 1. Sep 24 17:08:06 I mean, using the mouse directly, without an usb-hub in the middle Sep 24 17:08:10 not sure, i will need to reboot and all the process again, but the mouse is usb 1.1 and the usb host oin the board is just/only 2.0, ence the need of a hub Sep 24 17:08:35 ok, more is more recent Sep 24 17:08:37 hm Sep 24 17:12:25 rsalveti: did you had acces to igep's kernel source? Sep 24 17:12:49 got the access to the website, but still didn't download it Sep 24 17:13:02 let me take a look on it Sep 24 17:13:14 do you want me put it on my dropbox for you? Sep 24 17:14:22 rlameiro: it'd be good to test with the stock kernel from igep, maybe they have the patch already but just didn't publish it Sep 24 17:14:30 rsalveti: with the mouse directly connected to the USB host on board, nothing Sep 24 17:15:08 rlameiro: nothing you mean it wasn't even recognized during boot? Sep 24 17:15:08 is there some tool that allows to visualize the diff of 2 kernel folders? Sep 24 17:15:20 rsalveti: yes Sep 24 17:15:38 diff would be enough, but I'm looking more to a git tree or something like that Sep 24 17:15:41 to see the patches Sep 24 17:15:45 but as I said, it is a 2.0 port, so it needs a hub to recognise a 1.1 usb Sep 24 17:16:04 they have a git repo Sep 24 17:16:11 rlameiro: do you have any other usb device that's 2.0? Sep 24 17:16:37 rsalveti: i am afraid not, everything is 1.1 compliant Sep 24 17:17:58 rlameiro, may I suggest that you try the rsalvetis kernel and see if that fixes it? At least that would confirm that something has changed in a good way. Sep 24 17:18:12 http://git.igep.es/ Sep 24 17:18:35 the weird thing is that I don't have any usb-related patch... Sep 24 17:21:12 jo-erlend_igep: yes, i think i will do that Sep 24 17:21:27 is it possible that I had that problem with the Poky installation that came with the board, come to think of it. I'm just not sure anymore. Sep 24 17:21:40 rlameiro, great, then we will know for sure. Sep 24 17:26:52 rebooting... Sep 24 17:29:17 rsalveti: happens the same Sep 24 17:29:28 with you v4 image Sep 24 17:29:34 rlameiro: so this is probably related with your board revision Sep 24 17:29:41 weird.. Sep 24 17:29:49 I'm digging the git tree to see if I see something Sep 24 17:30:09 rlameiro: do you have the board changelog between revisions? Sep 24 17:30:27 jo-erlend: can you unplug your hub and plug it again to se if it works? Sep 24 17:30:29 I'd bet we have a link for it, just didn't find it yet Sep 24 17:30:40 rsalveti: i am searching it Sep 24 17:31:50 usb: make disconnect and suspend interrupts work again Sep 24 17:31:52 from kernel changelog Sep 24 17:31:56 let me dig the commit Sep 24 17:31:58 rlameiro: ^ Sep 24 17:32:37 hummm Sep 24 17:32:51 http://git.igep.es/?p=pub/scm/linux-omap-2.6.git;a=commitdiff;h=8ea712c38bd5e948d8f2a14d0c5bf4551032fe5b;hp=6fe3e7e1222a3ade418ad8c3b0542686a9a41f30 Sep 24 17:34:18 but I believe we have this commit already... Sep 24 17:34:21 * ogra_ac guesses that will interfer with other omap boards Sep 24 17:34:50 we already have it Sep 24 17:34:53 ah Sep 24 17:35:43 rsalveti, I just did. Everything works. Sep 24 17:35:45 their tree is based on 2.6.33 =\ Sep 24 17:35:54 ugh Sep 24 17:36:58 so, it could be because this is a different tree? Sep 24 17:37:31 its three versions behind the current development tree Sep 24 17:38:37 *and* it is a separate tree (linux-omap vs linux) Sep 24 17:38:39 good thing is that it seems they are maintaining a tree by rebasing their changes to 2.6.36 Sep 24 17:38:48 ah cool Sep 24 17:39:08 yup, much easier to get the fixes :-) Sep 24 17:39:54 rsalveti: http://dl.dropbox.com/u/1333955/MAN-PR-IGEP.0020.HW_USER_MANUAL.pdf Sep 24 17:40:18 page 16 starts talking about revisions, mine is a revision C. Sep 24 17:42:14 jo-erlend: can you please confirm you revision, if it is C or not? if it is a B revision it should have writen on the board in white IGEP0020-RB1 Sep 24 17:43:35 Just fyi, I did a hot unplug, wait 10s, plug of my usb hub on my beagle. Everything (keyboard, mouse, network, and usb drive with test media) came back no problem. Sep 24 17:51:04 Interesting info in the beagle manual on the C3>C4 changes. *Might* be applicable. "Uboot: Turning on VAUX2 for the EHCI fix" and A more advanced fix for the EHCI noise issue on Rev C3 board. This involves a Sep 24 17:51:05 change in the power circuitry for the 1.8V rail supplied to the EHCI PHY interface. The power is now derived from the VAUX2 on the TPS65950 through a Sep 24 17:51:05 filter circuit. Sep 24 17:51:42 I wonder if any of that applies, since the IGEP is based on the beagleboard designs. Sep 24 17:51:44 rlameiro: http://git.igep.es/?p=pub/scm/linux-omap-2.6.git;a=commitdiff;h=4911716a8b50fa080e613d2005d7d9a81255c0ca;hp=77fd21409771b51a3969da1f1724854901071e3f Sep 24 17:52:06 at this patch there's the code to identify the revisions, and set the correct pins for wlan and bt Sep 24 17:52:40 not related with usb though, but should also be applied Sep 24 17:53:05 I'm fetching the tree but I'm getting 14KiB/s :-( Sep 24 17:53:20 rsalveti: they have slow servers Sep 24 17:53:33 rlameiro, as I understand it, mine is revision c rc 1. Sep 24 17:54:39 ok, so mine has a 3 writen by hand, so it shouldnt be an hardware change, else they would write it on the board, its just for tracking of lots maybe Sep 24 17:55:35 rsalveti: I think they have newer trees than .33 Sep 24 17:55:52 and at least for the kernel, they are sending some patches upstream Sep 24 17:55:57 lool: they have, these links I sent are all target for 2.6.36 Sep 24 17:56:40 rsalveti: http://git.igep.es/?p=pub/scm/linux-omap-2.6.git;a=shortlog;h=refs/heads/linux-2.6.35.y for instance seems to be their .35 tree Sep 24 17:57:04 lool: I'm trying to fetch the tree to see all the patches that could be important for us Sep 24 17:57:21 but will take a while, very slow server Sep 24 17:58:45 you're pulling from a linux base, right? Sep 24 17:58:49 I mean --reference Sep 24 18:00:24 lool: this branch is a merge branch from linaro, it seems Sep 24 18:00:38 not a rebase one, so need to check the differences comparing trees Sep 24 18:00:58 but doesn't seems to have any important fix related to usb Sep 24 18:02:41 rsalveti: From linaro really? Sep 24 18:02:46 I was expecting from linux-omap Sep 24 18:02:55 lool: well, there's a merge from linaro Sep 24 18:03:52 http://git.igep.es/?p=pub/scm/linux-omap-2.6.git;a=commitdiff;h=0a500156f2acfe06f270ba02ac004bae548e12d2;hp=27498d7ece6e964b9350aaad1fda1bd3d67e5c25 Sep 24 18:04:00 rlameiro: lool: maybe this patch could help Sep 24 18:04:09 setting gpio for external vbus Sep 24 18:05:29 maybe Sep 24 18:06:22 its possible that is related to some change on the voltage when its unplugged that shuts down the power to that bus Sep 24 18:06:44 rlameiro: once the fetch is completed I'll generate a new deb for you to test Sep 24 18:07:21 rlameiro: could be Sep 24 18:07:47 rsalveti: I find it really cool that they merge from Linaro Sep 24 18:08:26 rsalveti: i just dont get why does it work with jo-erlend_igep ... Sep 24 18:09:06 well, there is always the chance of hardware bug Sep 24 18:09:21 very unlikely, but possible Sep 24 18:09:27 rlameiro: yep, and could also be related with the peripherals he's using Sep 24 18:09:41 rlameiro: are you sure your usb hub is not pulling energy from the usb? Sep 24 18:10:01 it very common to find usb hubs that doesn't respect that and pulls a lot of energy from the usb Sep 24 18:10:02 this one, no, i bought it today on porpuse, beacuse of that Sep 24 18:10:10 even the powered ones Sep 24 18:10:17 it has is own power supply Sep 24 18:10:21 I've seen some USB hubs that, when powered, push power back into the upstream port. Sep 24 18:10:28 well, that i cant say.. Sep 24 18:10:32 rlameiro: What is the ps supplied amperage? Sep 24 18:10:34 urgh, that's ugly Sep 24 18:10:57 Rosewill has some USB hub power-adapters that give well over 5 volts when not heavily loaded. Sep 24 18:11:03 GrueMaster: the hub power supply its rated at max 2 Amp Sep 24 18:11:09 Ok. Sep 24 18:11:17 That should be fine then. Sep 24 18:11:39 and outputs 5v, so its not regulated inside the board Sep 24 18:11:59 well, at least AFAIK.... i didnt opened the hub yet Sep 24 18:12:12 you could measure it Sep 24 18:12:22 but the power supply is a switching power, so it should be regulated Sep 24 18:12:29 let's also wait to see if this patch could make any difference for you Sep 24 18:12:33 I have the same powersupply currently powering my hub on my beagleboard (and my beagleboard is drawing power from it using a USB<>PS connector). Sep 24 18:12:42 dont have in here my multimeter Sep 24 18:13:13 GrueMaster: I was thinking in doing that :D Sep 24 18:13:39 but for now, my igep board uses a palm power supply from my old m515 Sep 24 18:13:59 max output current is 1 Amp... Sep 24 18:14:03 Hmmm. I wonder if it is enough? Sep 24 18:14:49 well, i dont know, maybe Sep 24 18:14:59 let me check the hardware reference Sep 24 18:15:56 GrueMaster: 5Vcc / 1A Sep 24 18:16:05 it should be enough Sep 24 18:17:02 I see that. Still, could be wavering. If you can, try a beefier ps. The board will only draw what it needs. Just keep it at 5v. Sep 24 18:17:53 typical is 650 mA, Max is 750mA, so it is more than enough Sep 24 18:18:54 but i will try with another PS. maybe from an atx ps that i converted to bench PS Sep 24 18:19:13 problem is that my electronic materials are at my parents garage.... Sep 24 18:19:26 no space on the condo..... GRRRRR Sep 24 18:19:38 Just be very careful. We can't help if you fry your board. Sep 24 18:20:10 GrueMaster: dont worry :D I play with electronics for a while :D Sep 24 18:21:22 i wonder if this problems happens with the default poky on the nand... Sep 24 18:28:11 rlameiro: wait it a bit until I deliver you a new kernel, don't know how secure could be your usb hub Sep 24 18:28:58 at least the one I got I could easily fry the usb port Sep 24 18:29:03 ok, i wait Sep 24 18:29:13 lol Sep 24 18:29:15 no prob Sep 24 18:29:23 i send it back to ISEE :D Sep 24 18:29:28 then I had to remove a resistor from it to avoid pulling from the usb port Sep 24 18:29:42 haha :-) Sep 24 18:30:00 oh, you say the usb hub gets fried??? Sep 24 18:30:16 no, the usb port from my computer, or board Sep 24 18:30:21 lol, that is not a problem, i just go to the shop and say, hey this port doesnt work!!! Sep 24 18:30:23 :) Sep 24 20:14:42 rlameiro: http://people.canonical.com/~rsalveti/kernel/linux-image-2.6.35.4+_2.6.35.4+-5_armel.deb Sep 24 20:15:10 with the vbus patch Sep 24 20:15:21 rsalveti: thanks :D Sep 24 20:15:49 I will test it soon Sep 24 20:16:22 rlameiro: cool Sep 24 20:49:54 rsalveti: what is linux-firmware-image_2.6.35.4+-5_all.deb for? Sep 24 20:59:57 rsalveti: update-initramfs: Generating /boot/initrd.img-2.6.35.4+ Sep 24 20:59:58 /etc/kernel/postinst.d/update-notifier: 17: gettext: not found Sep 24 21:00:08 it output this error Sep 24 21:04:57 rlameiro: linux-firmware should be the default firmware pack from the kernel Sep 24 21:05:02 you probably don't need it Sep 24 21:05:25 rlameiro: hm, try installing gettext and try it again Sep 24 21:15:45 * rsalveti brb Sep 24 21:24:05 rsalveti: this one has your network driver patch? Sep 24 21:24:19 t took alot time to bring it up Sep 24 21:24:26 dmesg at 65 seconds from boot Sep 24 21:24:42 8.168334] libertas_sdio: probe of mmc1:0001:1 failed with error -2 Sep 24 21:24:43