[01:03] Weeeee [01:03] Hi! [01:03] Ive got my hands on an old Skye SL [01:03] Now big question [01:03] How do i get ubuntu on it? [01:04] I presume you don't mean http://brickwell.com/product/10-trek-skye-sl-57861-1.htm : do you have a link to specs? [01:05] Somehow, I expect not [01:05] Yepp, its a rather rare device. I found some info and also tried out his Linux [01:05] it would be interesting to try to install ubuntu on gears on a device [01:05] Ubuntu, bike edition [01:05] http://scholbert.homelinux.org/SkeyePad.html [01:05] there you go [01:05] maybe its too classic [01:05] but it would be just so cool [01:06] that WinCE 3.0 is giving me shivers [01:06] "skeye" is quite different [01:06] checking [01:06] no, ARM on that one is too old. You might be able to get debian on it [01:06] Debian will run fine. [01:07] It's an SA1100 .. should run Debian fine [01:07] Jaunty might even install, but would run vey slowly. [01:07] Jaunty won't install .. its an arm v4 [01:07] Oh, right. [01:07] and the memory map and driver map for that device is cwazy [01:08] * persia is often confused by the various extensions in the SA1110 and needs to hardwire the brain to say "Cannot run Ubuntu" [01:08] http://scholbert.homelinux.org/SkeyePad_stuff.html [01:08] OOOOllld hardware [01:09] aye [01:09] but still a very robust build [01:09] Gestahlt: So, you should have good kernel support, but you likely have to make your own kernel. Getting it to boot directly (rather than chain-boot out of WinCE) may be a bit tricky. [01:09] i want to pimp it up [01:09] I hate to say it, but it won't be very "pimp" able [01:09] it has very little memory [01:09] And when I say very little .. I mean a TINY amount of RAM [01:10] Samsung SDRAM 2x32MB (K4S561632-TC75) @ 103MHz [01:10] Computers wont need ever more than 640kb of RAM [01:10] Isn't that 64MB? [01:10] Should be fine, for careful use. [01:10] Actually [01:10] Worse, it has even less -storage- [01:10] Intel NOR Flash 2x16MB (28F128J3A-150) [01:10] i need it for RDP / VNC Streaming and Tux Paint [01:10] 32MB of storage. That's it ... [01:10] and maybe seamonkey [01:10] Well [01:11] there is a CF card [01:11] getting a basic linux install squeezed in there, is going to be a bitch [01:11] Zaurus has 64MB, and later Zauri were known to run Jaunty. [01:11] That said, I wouldn't try to compile boost on it :) [01:11] Yes, Zaurus had more storage though [01:11] Depends on the model. SLC-1000 has no NOR. [01:11] Err, -3000. [01:12] 3000 *ONLY* had CF storage. Mind you, two CF, one pre-installed with a microdrive, but still. [01:12] That's because it had a -hard disk- [01:12] yeah [01:12] So? [01:12] Stick a microdrive or a bundle of flash in the CF slot, and who cares. [01:12] CF-ATA is all sorts of well supported. [01:12] true [01:12] could be interesting [01:13] Gestahlt: But, yeah, your first steps are figuring out how to build the right kernel, and getting it to boot that kernel. Once you can do that, putting a Debian 5.0 filesystem on the CF card shuold be trivial. [01:14] Zaurus は常に（今まで）非常にしっかり造られたハードウェアでした [01:14] * Martyn mangles japanese with the best of 'em [01:14] Persia, that scholbert guy already build an running kernel (2.4.x but still better than ce 3.0) with GPE [01:14] In the beginning, this was true. Not so much these days :) [01:14] Gestahlt: You really want a 2.6 kernel these days :) [01:15] Probably at least > 2.6.13, really. [01:15] I know... [01:27] persia: none of the zaurus had nor, all of them have nand [01:30] Ah, right. My mistake. [01:30] 3000 still didn't have either :) [01:30] persia: 3000 had 128M of NAND [01:30] persia: so your still wrong :-) [01:30] What? [01:30] all zaurus had NAND [01:31] I thought that was precisely the difference between the 3000 and the 3100, and specifically didn't get a 3000 because of this understanding. [01:31] It was reputed to boot slow because of this. [01:32] it only had 16M [01:32] OK. That I can believe. [01:32] 3100 had 128M [01:32] but the rom and bootloader was always in NAND [01:32] Ah, right. So 3000 had kernel in NAND, and full FS on CF-ATA, whereas 3100 had the base FS in NAND also. [01:32] * XorA|gone has spent too many years of life hacking on openzaurus [01:33] * persia was only ever a Zaurus user, and no longer (the 3100 died, and the Netwalker has left the 3200 to gather dust) [01:33] persia: yeah something like that, couldnt tell you the exact layout of a 3000 as I never owned one, but its flashing script is identicle to 3100 [01:33] Earlier models have just given up (no longer charge or boot) [01:34] Makes sense, and simplifies internals to have the 16M for booting. [01:34] (that said, I'm still happy to have never been a 3000 owner) [01:35] Ive had 5500, 5600, 6000, c860, 3200 [01:35] only got 5500 left [01:36] I've had J1M1,760,860,3100,3200, and only the 3200 still works. [01:36] J1M1 isn't directly comparable, of course, running an entirely different OS :) [01:36] anyway Im off to bed its well late here :-) [01:37] Sleep well :) === XorA|gone is now known as XorA|goner [01:55] * NCommander needs Marvell :-/ [03:10] ogra_cmpc: BTW, have you ever caught a stray cat before? [03:10] * NCommander has one that recently showed up in town, and I'd like to trap it, get it neutered, and release/put up for adaption [07:15] mmmmm, segfaultilicious [07:16] debootstrap'ing lucid in qemu now results in segfaults instead of hangs :p [07:28] segfaults.. C's way of reporting errors to the user :) [07:33] if it's actually segfaulting instead of hanging, I'm happy :p [07:33] if it's just segfaulting before it gets to the point at which it used to hang, I'm not so happy [07:33] segfaults: C's way of saying "I love you" [07:34] "spend more time with me" [07:34] "why don't you ever call anymore?" [07:38] :) [07:41] I was about to draw a bunch of parallels between c and one's psycho ex-girlfriend, but it might be hitting too close to home [07:49] dunno, my experience is on the C side only [07:50] and I think I'm fine with that [08:48] Hi, I don't understend, there is no way to compile the kernel with OHCI-1394 support? that is strange ... [08:49] is it true for all the beagleboard distro ? or can I find one with this modules on the kernel ? [09:07] hmm, how do you propose to get firewire on a beagle? [09:09] lost of soldering ? [09:09] *lots [09:09] wouldn't be all that much, no? [09:10] I'm sure dlp has a nice easy to use module [09:10] er, ftdi [09:10] well, i'd use some USB adapter [09:10] likely the easiest [09:10] and probably evan already supported by the ubuntu default kernel [09:11] if not, dkms is your friend ;) [09:22] USB to firewire? there's not such a thing. Or at least, not one that can do general-purpose firewire. [09:55] DanaG, http://www.usbfirewire.com/Parts/rr-527950.html [09:55] oh, he's gone [10:01] Hello all [10:18] he'll be back [10:32] ogra_cmpc, was that you I was talking to the other day about lucid not installing in qemu? [10:45] cwillu_at_work, if i talked about it then only in connection with rootstock, i guess it was rather lool, he does std. installs in qemu [10:46] though he focuses on aemu-maemo atm afaik [10:46] *qemu-maemo === XorA|goner is now known as XorA [12:54] Hi, what do i need for lan connection via the usb? [13:02] I'm trying to be able to login as root on my system, but after changing the root's password, I get "You are required to change your password immediately (root enforced)" [13:03] Then I (by mistake) changed the password for the ordinary user, and the same message appears for that user [13:07] samuel_Sayag: You need a USB LAN device. Your life will be easier if it is known to be supported in Ubuntu (but this is hard to discover: you probably want to make sure it's supported in the upstream kernel) [13:07] sveinse: You hit the clock bug. Set the system clock to something closer to real time. [13:08] It happens when the target system clock is out-of-sync with the real clock [13:08] persia: Yes, so I figured [13:09] persia, Thanks [13:09] I believe it only happens when the system clock is set to some time prior to the timestamp of the shadow file, but then again, my knowledge of that bug comes from listening to a couple people talk about it in a hotel room many months ago :) [13:10] That said, because of the some-systems-don't-have-battery-backed-clocks-and-can't-get-network-to-get-real-time-until-post-login issue, it's worth tracking down the bug, and investigating what other options are available to address the reason the check is present without cauing it to happen for everyone who has a failed/incorrect RTC. [13:11] persia: It is a good theory for my system. You see, I use NFS as rootfs, so the files will probably be timestamped with the host time. When the arm target is living in the 1970s you get these kind of errors [13:12] If possible, prefer boards with battery-backed RTCs :) [13:12] * persia believes this to be a hardware issue, but is amenable to software workarounds. [13:15] wee plymouth SEGV [13:18] wow adding text + nosplash actually turns on the output [13:20] persia: Turns out it's not the kernel turning graphics on! [13:21] lool: What does it then? [13:21] Does plymouth reprobe directly? Is that why it build-deps on libdrm? [13:21] I didn't find out yet, but init=/bin/sh doesn't turn it on [13:23] Cool. That makes it easier. [13:25] * NCommander waves [13:25] except I'm still fighting to get any sort of console [13:34] Gah, the cloud*.conf scripts were hanging === XorA is now known as XorA|gone [18:37] eero heinäluoma on käynyt kaivamassa isoisän urlimuseosta kommenttia joilla kosiskella nuivia äänestämään sdp:tä [18:38] "ne vie meidän työttämien työpaikat" [18:38] that's a lot of finnish [18:38] :P [18:39] oops, wrong channel :P [19:08] lol === jldugger is now known as pwnguin