[06:42] Funnily enough, when it comes to the Nook Color... Touch works on Kubuntu, but not Ubuntu... [06:43] Xase: surely that's an issue of KDE vs. GNOME [06:43] or vs. unity or whatever [06:44] xw3m [06:44] ... How could it be??? I can't even log in yet? [06:45] So you're telling me that lightdm is so vastly different from kdm that'd prevent touch from working? [06:46] twb: I may not be some hardocre awesome programmer... but the logic there doesn't seem right... [06:46] Uh, the dm only does something when you log in [06:46] Once you've logged in, it's gone [06:46] Well on the DM screens... ubuntu doesn't work... kubuntu does. [06:47] But really I would expect it to be libgtk vs. libqt or libgnome vs. libkde [06:47] ... [06:47] Really? [06:47] causing touch not to work? [06:48] Sure [06:48] Well touch must work somewhat... b ecause I just saw somethign as I was drumming my fingers across the screen... [06:48] Shrug [06:48] This is new to me too [06:49] hmmm... [06:49] I somehow managed to get it to switch to the "other" login... [06:49] Touch seems to be registering... but not perfectly... but the nook has a notoriously finnicky screen that suffers from phantom touches... [06:53] Xase: use evtest and pastie its output [06:55] Wish I could boss... [06:55] I can't even get the device to login. [06:55] Waiting on my usb male to micro converter.... [06:56] Dunno even know if the kernel I'm using has usb host built into it yet. [06:56] Will try tomorrow if converter comes... [06:56] ah ok, so you don't have adb abilities or network then [06:56] Interesting; I ran "speaker-test" and it emits white noise [06:57] adb on linux? [06:57] Ah that's by design [06:57] lilstevie: wasnt aware that'd work... [06:57] speaker-test -t sine [06:57] Xase: yeah, adbd is statically linked [06:57] so it works [06:58] so hold on then... brb... gotta disconnect my phone and hook up my nook which means no internet for a moment. [06:58] ok [07:04] Hmmm, [07:04] after powering it down before your request... [07:04] Everything was fine... now the SD won't boot for some reason. [07:04] you do need to inject adbd and an init script for it, just FYI [07:05] I'll have to re-dd it tomorrow. [07:05] and then Adb from another computer will work? [07:05] yes [07:06] The things you learn.... I'll have to check it out tomorrow, as it's now past my bedtime :D [07:07] past my pubtime [07:19] That's odd, onboard crashes at startup despite its deps being met [07:19] http://paste.debian.net/149912/ [07:20] lilstevie: do you care about that? [07:36] Is dasher still "cool" or is it abandonware? [07:36] No change since maverick so I'm guessing gnome3 killed it [09:36] twb that would be more a report for someone who maintains onboard === doko_ is now known as doko [15:55] lilstevie: if adb is statically linked... wouldn't I still require an adb built for arm? [15:56] Xase: adbd is built for arm in android systems :) [15:56] So i can extract adbd from my inspire then? [15:57] I assume the script should read something like sudo sh /opt/asdk/adb start-server and place the script in /etc/init.d/ ? [16:00] Xase: http://htc-linux.org/wiki/index.php?title=Ubuntu/Leo#ADB [16:08] lilstevie: wish I had notcied you posted that sooner lol... i'm sitting in adb shell trying all sorts of scp commands... and then it strikes me that adb pull /sbin/adbd would work fine. [16:09] heh [16:09] What can I say... I'm a certified noob. [16:13] lilstevie: once I copy it to /etc/init.d how am I supposed to execute update-rc.d adb.d defaults? [16:14] chroot [16:14] o.o [16:14] Heheh [16:15] the only time I advocate the use of chroots is for preparing the native images [16:15] ... hrmmm aren't there special instructions for chrooting an arm image anyways? [16:15] copying a binary into place and chrooting it if on x86 [16:16] or just straight up chroot if on native hardware [16:16] Yeah I think I have the instructions somewhere in my history... [16:48] lalalala time to try it. [17:07] No go for some reason... [18:18] Meh... I can't tell if I wired this wrong or what..... [18:31] lilstevie is it a possiblity that for some reason the kerel is not set up to allow communication over the microusb port you think?