**** BEGIN LOGGING AT Tue Sep 22 02:59:57 2009
Sep 22 03:07:02 <morfic> i think i'm gonna pass on lvm for the sheeva tonight, i am more interested in moving data back on a changed md0 starting before i go to bed tonight
Sep 22 03:07:41 <arachnist> md0? you have a "freebsd ramdisk device" on your linux? :>
Sep 22 03:08:02 <morfic> /dev/md0, my raid1
Sep 22 03:08:08 <arachnist> oh
Sep 22 03:09:23 <arachnist> well...
Sep 22 03:09:24 <arachnist> stalker ~ # uname -a; cat /etc/*release
Sep 22 03:09:24 <arachnist> Linux stalker 2.6.31-openrd #2 PREEMPT Tue Sep 22 03:58:47 CEST 2009 armv5tel Feroceon 88FR131 rev 1 (v5l) Marvell Ope
Sep 22 03:09:28 <arachnist> nRD Client Board GNU/Linux
Sep 22 03:09:30 <arachnist> Gentoo Base System release 2.0.1
Sep 22 03:21:14 <morfic> gentoo makes it easy to strip your system
Sep 22 03:21:28 <morfic> and keep stuff off your system with USE=-X and the like
Sep 22 03:21:44 <morfic> but i love not having to compile
Sep 22 03:27:37 <arachnist> morfic: well, i just set up distcc with my desktop
Sep 22 03:28:55 <morfic> it's nice once it's all set up, but not to get going
Sep 22 03:30:21 <arachnist> crossdev --target armv5tel-softfloat-linux-gnueabi, install distcc, create some symlinks in /usr/lib/distcc/bin and remove the default g++, gcc, cc and c++ symlinks
Sep 22 03:30:35 <arachnist> and set up distcc as you would usually do
Sep 22 03:33:37 <morfic> you did notice i run no gentoo system, not even a sourcemage system, so things now would not be as simple, i am fine, just need to get some more space for /usr/share stuff and the like to make system more usable
Sep 22 03:43:38 <morfic> chunksize on raid1 for my two usb drives is something that makes everyone queasy it seems :) while writing might not be affected, i wonder what impact chunk size of raid1 and block size of xfs will have on read performance
Sep 22 03:56:58 <arachnist> "Compliant with the Cortex A8, Sheeva also supports both the ARMv6 and ARMv7 instruction sets" - if that's true, why does `uname -m' show armv5tel?
Sep 22 03:59:11 <ShadowJK> where does it say that..
Sep 22 04:15:50 <arachnist> http://www.marvell.com/technologies/cpu_history/cpu_history.jsp
Sep 22 04:22:39 <tinker-f595> arachnist: ask rabeeh if that is correct with regard to the kirkwood
Sep 22 04:23:13 <morfic> what would those instruction sets do for the binaries on the sheeva if they are indeed supported?
Sep 22 04:23:46 <tinker-f595> arachnist: uname -m' shows armv5tel because that is how it is compiled.
Sep 22 04:25:18 <tinker-f595> morfic: I think that might be marketing hyperbole.  The functional specs for the kirkwood mentions ARMv5TE
Sep 22 04:25:47 <morfic> cpuinfo only shows that
Sep 22 04:25:49 <tinker-f595> but ask rabeeh...he should be able to clarify
Sep 22 04:26:25 <morfic> Processor       : Feroceon 88FR131 rev 1 (v5l) CPU architecture: 5TE
Sep 22 04:27:14 <tinker-f595> and it does not say that it is compliant with cortex 8.
Sep 22 04:27:35 <arachnist> hm
Sep 22 04:27:38 <tinker-f595> soory misread it does
Sep 22 04:28:02 <arachnist> well
Sep 22 04:28:03 <arachnist> http://dpaste.com/96592/
Sep 22 04:28:05 <tinker-f595> sorry the advertising stuff does say it is cortex A8 compliant
Sep 22 04:28:26 <arachnist> compiling it with "-march=armv6 -falign-functions=1 -falign-jumps=1 -falign-labels=1" and running gives illegal instruction
Sep 22 04:28:47 <arachnist> so, i guess it's not armv6
Sep 22 04:29:59 <morfic> marketing always finds ways to hype stuff, if it was up to marketing, my myTouch3G has 192MB RAM, no need to mention that 64MB is for fb and 32mb for radio, and only 96MB are actually there for linux kernel/OS
Sep 22 04:30:09 <tinker-f595> haha
Sep 22 04:30:23 <tinker-f595> take a look at the functional spec http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf
Sep 22 04:30:25 <morfic> they are not lying, they are just not truthful
Sep 22 04:30:31 <tinker-f595> http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf
Sep 22 04:31:02 <tinker-f595> http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf
Sep 22 04:31:40 <tinker-f595> hmm pasted the link as invisible
Sep 22 04:31:54 <tinker-f595> http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf
Sep 22 04:31:56 <morfic> we saw it, 3 times
Sep 22 04:32:01 <morfic> 4 times
Sep 22 04:32:01 <arachnist> well
Sep 22 04:32:11 <arachnist> i guess openrd is not armv6
Sep 22 04:32:14 <tinker-f595> oh not seeing on my end dumb bug in my client
Sep 22 04:32:26 <morfic> nice, not just me having fun bugs ;P
Sep 22 04:32:27 <arachnist> anyone with sheevaplug could check http://dpaste.com/96592/?
Sep 22 04:33:51 <morfic> Illegal instruction
Sep 22 04:34:34 <morfic> ok, moving on
Sep 22 04:34:37 <tinker-f595> apologies for the mutltiple link posts
Sep 22 04:34:49 <morfic> tinker-f595: we survive, barely, but we will
Sep 22 04:35:05 <tinker-f595> haha
Sep 22 04:35:08 <tinker-f595> tired...
Sep 22 04:35:10 <tinker-f595> time for sleep
Sep 22 04:35:33 * morfic thinks he could build and test a few raid options before moving files back if moving them the first time finishes not too long after midnight
Sep 22 04:35:58 <tinker-f595> and what time zone are is morfic in?
Sep 22 04:38:28 <morfic> tinker-f595: central time us, germany-7
Sep 22 04:38:47 <tinker-f595> oh you are just waking up ;)
Sep 22 04:38:55 <tinker-f595> early riser
Sep 22 04:38:58 <morfic> what?
Sep 22 04:39:02 <morfic> 23:38 here
Sep 22 04:39:13 <morfic> late sleeper is more like it
Sep 22 04:39:29 <morfic> waiting for rsync -av /home /mnt to finish
Sep 22 04:39:32 <tinker-f595> thought you said germany
Sep 22 04:39:32 <tinker-f595> misread
Sep 22 04:39:35 <tinker-f595> From the "88F6281 Integrated Controller Hardware Specifications"- Compliant with v5TE architecture, as published in the ARM Architect Reference Manual, Second Edition
Sep 22 04:40:06 <morfic> so i can umount /home and mdadm --stop /dev/md0 and the --create it again with changed chunk size
Sep 22 04:40:19 <tinker-f595> 21:40 here...going to have an early night
Sep 22 04:40:29 <morfic> tinker-f595: i meant GermanyTime minus seven hours
Sep 22 04:40:37 <tinker-f595> why germany time?
Sep 22 04:40:41 <morfic> west coast
Sep 22 04:40:46 <morfic> easier to remember?
Sep 22 04:40:58 <tinker-f595> yes west coast.
Sep 22 04:41:02 <morfic> i call family a lot, so i think in +7 hours for them
Sep 22 04:41:05 <tinker-f595> pacific time
Sep 22 04:41:11 <morfic> not gmt or utc
Sep 22 04:41:32 <tinker-f595> phases of the moon works better ;)
Sep 22 04:44:55 <tinker-f595> morfic night
Sep 22 04:45:45 <morfic> 'nigt tinker-f595
Sep 22 05:38:13 <arachnist> morfic: i'd suggest you try out raid-Z ;)
Sep 22 05:40:11 <morfic> would be nice, sounds a little iffy? rebuilding it i mean?
Sep 22 12:00:06 <Reedy> | os = [[Debian]] 9.04 (since rev. 1.2), [[Ubuntu (operating system)|Ubuntu]] 9.04 (before)
Sep 22 12:00:12 <Reedy> wtf is debian 9.04
Sep 22 12:01:13 <Reedy> does it come with debian as stock now?
Sep 22 12:01:40 <suihkulokki> ECONTEXT
Sep 22 12:01:51 <Reedy> ?
Sep 22 12:02:04 <suihkulokki> where is that info from?
Sep 22 12:02:23 <Reedy> wikipedia
Sep 22 12:03:24 <Reedy> i thought the only debian was Martyns one?
Sep 22 12:04:18 <Reedy> Cause it contradicts itself, saying martin has a debian port
Sep 22 12:06:06 <Reedy> I've commented that out
Sep 22 12:07:24 <suihkulokki> Reedy: probably whoever has been editing wikipedia has just been confused.
Sep 22 12:07:30 <Reedy> mhmm
Sep 22 12:07:38 <Reedy> I've commented it out for the moment
Sep 22 12:07:44 <Reedy> Will remove it later
Sep 22 12:13:02 <ron_> isn't there out-of-the-box kernels for it in debian proper now?
Sep 22 12:13:15 <ron_> you don't need anything special, just current debian armel
Sep 22 12:18:51 <arachnist> anyone with openrd-client? my second gigabit ethernet port doesn't seem to work properly with a custom kernel
Sep 22 12:19:38 <arachnist> in dmesg i get:
Sep 22 12:19:39 <arachnist> eth1: link up, 10 Mb/s, half duplex, flow control disabled
Sep 22 12:19:56 <lennert> arachnist: probably wrong phy address
Sep 22 12:20:04 <lennert> arachnist: or something like that
Sep 22 12:20:08 <arachnist> as in, mac?
Sep 22 12:20:12 <lennert> phy address
Sep 22 12:20:31 <lennert> what phy addresses are specified in the openrd bsp file?
Sep 22 12:20:39 <arachnist> what bsd file?
Sep 22 12:20:43 <arachnist> bsp*
Sep 22 12:21:25 <arachnist> where can i find it?
Sep 22 12:21:37 <lennert> which kernel patches did you use to build your kernel?
Sep 22 12:22:55 <arachnist> 0001-ARM-Kirkwood-Marvell-OpenRD-Base-board-support-added.patch, 0001-ARM-Kirkwood-Marvell-OpenRD-Client-board-support-add.patch, 0001-Kirkwood-Initialise-SATA-for-OpenRD-Base.patch and replaced mach-types
Sep 22 12:23:01 <lennert> where do i find those patches?
Sep 22 12:23:28 <arachnist> i found them on the http://groups.google.com/group/openrd/topics
Sep 22 12:28:38 <arachnist> http://groups.google.com/group/openrd/msg/3ecaba96b58f2187?&q=Kirkwood+Initialise+SATA+for+OpenRD+Base <| here's the exact post with the patches
Sep 22 12:30:31 <lennert> arachnist: that patch doesn't create a eth1
Sep 22 12:30:40 <lennert> arachnist: so how did you get the eth1?
Sep 22 12:30:50 <arachnist> it's just there
Sep 22 12:31:24 <arachnist> dmesg said:
Sep 22 12:31:25 <arachnist> net eth0: port 0 with MAC address 00:50:43:01:de:52
Sep 22 12:31:25 <arachnist> net eth1: port 0 with MAC address 00:50:43:01:de:53
Sep 22 12:31:47 <lennert> ah, looking at the wrong ile
Sep 22 12:31:52 <lennert> +       .phy_addr       = MV643XX_ETH_PHY_ADDR(8),
Sep 22 12:31:54 <lennert> +       .phy_addr       = MV643XX_ETH_PHY_ADDR(18),
Sep 22 12:31:58 <lennert> that latter one seems unlikely
Sep 22 12:32:01 <lennert> can you email me your dmesg?
Sep 22 12:32:17 <arachnist> will a dpaste.com paste be sufficent?
Sep 22 12:32:27 <lennert> sure
Sep 22 12:33:23 <arachnist>  http://dpaste.com/96692/
Sep 22 12:36:41 <arachnist> think i'll try with "MV643XX_ETH_PHY_ADDR(16)" in the mean time
Sep 22 12:37:10 <lennert> arachnist: right, or try 9
Sep 22 12:37:27 <lennert> arachnist: can you see what PHY chip is on the board?
Sep 22 12:37:36 <arachnist> how can i check it?
Sep 22 12:37:42 <lennert> or if you have phylib enabled, can you check what phylib driver bound to it?
Sep 22 12:37:52 <lennert> arachnist: well, if you have the bare pcb, try to find the ethernet phy chip
Sep 22 12:38:04 <lennert> it should have a part number 88E1??? if it's a marvell phy
Sep 22 12:38:13 <lennert> or there could be two of them
Sep 22 12:38:19 <lennert> but i would guess that there is a single dual-port chip
Sep 22 12:38:56 <ron_> 1116_NNC if the diagrams are to be believed
Sep 22 12:39:48 <lennert> 1116 is single-port
Sep 22 12:39:51 <lennert> ron_: are there two of them?
Sep 22 12:40:11 <arachnist> removing the enclosure will be rather hard with all the cables attached ;>
Sep 22 12:40:21 <lennert> arachnist: then leave it :)
Sep 22 12:40:23 <ron_> on the -client I think so, as there is only a single eth on the -base
Sep 22 12:40:34 <lennert> ron_: so the client has the same 1116, but twice?
Sep 22 12:41:15 <ron_> that's what the circuit diagram in front of me (and empty pads on the -base board) would have be believe
Sep 22 12:42:02 <lennert> ok
Sep 22 12:44:10 <lennert> ron_: where are the schematics?
Sep 22 12:44:54 <ron_> the copy I have came off the CD that came with it ...
Sep 22 12:45:10 <ron_> I thought most of that stuff was (freely) online somewhere though
Sep 22 12:45:11 <lennert> ron_: ok, then can you tell me what lines the CONFIG0-3 pins are hooked up to on each of the 88E1116R chips?
Sep 22 12:45:47 <lennert> i mean, to VSS, VDD, LED0 or LED1
Sep 22 12:48:09 <ron_> good question...  depends on what resistor pads are bridged by default ...
Sep 22 12:48:46 <lennert> hm :)
Sep 22 12:49:34 <arachnist> lennert: well, setting it to 16 didn't help
Sep 22 12:49:39 <arachnist> will try with "9" now
Sep 22 12:53:55 <ron_> looks like on eth1 C0 -> GND, C1 -> LED1, C2 -> VCC, C3 -> one of (any of) them
Sep 22 12:55:10 <ron_> for eth0 C0 -> GND, C1 -> LED1, C2 -> LED1, C3 -> any
Sep 22 12:56:03 <lennert> so eth0 phy addr is 01000, which is 8
Sep 22 12:56:24 <lennert> for eth1, phy addr is 11000, which is 24
Sep 22 12:56:44 <lennert> arachnist: try 24
Sep 22 12:57:05 <ron_> oh yep, they give exactly those addresses too
Sep 22 12:57:40 <arachnist> ok
Sep 22 13:02:28 <arachnist> (there should be some kind of distcc for "ld"...)
Sep 22 13:06:33 <arachnist> lennert: 24 worked. thanks :)
Sep 22 13:07:03 <lennert> arachnist: cool
Sep 22 13:07:11 <lennert> arachnist: please report that to that guy
Sep 22 13:07:27 <ron_> there's one bit of documentation that's correct then \o/
Sep 22 13:08:37 <lennert> ron_: thanks for checking the schematics
Sep 22 13:09:29 <ron_> np.  I had them right in front of me, so it seemed easy to scroll about and get good answers without guessing too much
Sep 22 13:44:45 <arachnist> hm
Sep 22 13:45:43 <arachnist> if it wasn't for capacitors C175 and C475 on the openrd-client, it looks like it's be possible to put a 3.5" drive inside the enclosure
Sep 22 13:46:08 <arachnist> though heat might be an issue
Sep 22 13:46:55 <arachnist> oh
Sep 22 13:47:04 <arachnist> and the enclosue's too low
Sep 22 13:47:30 * armin76 suggests glueing an external disk
Sep 22 13:47:49 <armin76> or SSD, no?
Sep 22 13:47:52 <arachnist> well
Sep 22 13:48:02 <arachnist> i have a sata<->esata cable
Sep 22 13:48:14 <arachnist> and a external power supply for the 3.5" drive
Sep 22 13:48:22 <arachnist> i was just curious
Sep 22 13:49:42 <arachnist> (and the enclosure looks just way too cool to dispose of it, imo :> )
Sep 22 13:53:55 <ron_> you could move those caps to the other side of the board easily enough
Sep 22 13:54:03 <ron_> they're through hole jobbies
Sep 22 13:54:34 <arachnist> provided i had any soldiering skills and... what was the "soldiering device" called in english?
Sep 22 13:55:39 <ron_> a soldiering device is probably a rifle, or cannon :)
Sep 22 13:56:12 <arachnist> "soldering gun"
Sep 22 13:56:26 <ron_> "iron" is the common word :)
Sep 22 13:57:00 <arachnist> iron is the thing that melts and connects, isn't it?
Sep 22 13:57:20 <arachnist> (well, at least the common name. not chemically iron)
Sep 22 13:57:54 <ron_> yeah, that's all you'd need to move those though
Sep 22 13:59:05 <ron_> (chemically they are usually mostly copper :)
Sep 22 14:27:30 <lennert> arachnist: openrd support should really go upstream
Sep 22 14:28:04 <arachnist> lennert: as in, kernel and u-boot patches?
Sep 22 14:28:25 <lennert> yep
Sep 22 14:28:58 <lennert> so there's one tested version of the code in one pąlace
Sep 22 14:29:02 <arachnist> lennert: well, it looked (from the discussion on the google group) that the guy who wrote the patches one of which i needed to modify has submitted them to the kernel devs
Sep 22 14:29:20 <lennert> alright
Sep 22 14:29:33 <lennert> so with that eth1 bug then
Sep 22 14:29:59 <ron_> if it's the ones I'm thinking of, they should be in mainline lk now (and nicolas' orion tree)
Sep 22 14:30:41 <ron_> sending a patch to those guys and/or linux-arm list would be appreciated
Sep 22 14:36:56 <tinker-f595> lennert: dhavel @ einfochips said he was going to upstream the OpenRD Client patches on Sept 17th but nothing has happened
Sep 22 14:42:56 <tinker-f595> arachnist why would you want to use a 3.5 inch drive?  They consume more power than a 2.5 inch drive.  Also there is 2.5 inch SATA drive header on the board.  One of the docs list the spacers needed to mount one.
Sep 22 14:45:34 <lennert> tinker-f595: ok
Sep 22 14:45:49 <ron_> dhaval's been responsive to taking patches, if not to pushing them back out again quickly :)
Sep 22 14:46:07 <ron_> the ones I sent him got pushed through quickly enough though
Sep 22 14:46:30 <tinker-f595> lennert: I was a bit disappointed when that date passed and the code had not be submittted upstream
Sep 22 14:47:39 <tinker-f595> ron_: also be nice to get openrd stuff upstream in uboot
Sep 22 14:47:59 <lennert> yea
Sep 22 14:51:04 <ron_> sure, that's been happening too, prafulla took and pushed some patches from me for that as well
Sep 22 14:51:49 <ron_> there's only so many hours in a day, if you want it to happen faster, the answer should be obvious :)
Sep 22 14:52:11 <tinker-f595> ron_: I have not seen them upstream in the uboot repository.  I spent a hour or two reading through it last night
Sep 22 14:52:34 <tinker-f595> ron_: sheevaplug stuff is upstream in the uboot repositiry
Sep 22 14:54:07 <tinker-f595> and dhaval has not put his OpenRD Client patch in his own repository http://repo.or.cz/w/linux-2.6/linux-2.6-openrd.git
Sep 22 14:55:19 <ron_> I've booted prafulla's branch off denx uboot, and sent some patches for it, and got an email from him last week that said he was going to push the next batch to them
Sep 22 14:55:49 <ron_> -client I have no idea about, I just have a somewhat modified -base
Sep 22 14:56:06 <arachnist> tinker-f595: one of the reasons being that i already have a 1TB 3.5" sata drive :>
Sep 22 14:57:59 <tinker-f595> arachnist: I have problems attemtping to use eSata.  The einfochips uboot has problems with it.
Sep 22 14:58:45 <arachnist> tinker-f595: well, i'm booting the system from the internal flash
Sep 22 14:59:01 <arachnist> tinker-f595: only /usr will be on the drive, as it didn't fit
Sep 22 14:59:13 <zumbi> how much power consumption has openrd with sata disks? someone knows?
Sep 22 15:07:51 <tinker-f595> zumbi depends on the particular disk you are using.
Sep 22 15:08:12 <zumbi> tinker-f595: which are your measurements? aprox
Sep 22 15:08:49 <tinker-f595> well depends if the disk is starting, reading, writing or idle
Sep 22 15:23:15 <zumbi> tinker-f595: max(power_consumption);
Sep 22 15:23:41 <zumbi> tinker-f595: are we talking 5W or 30W or 60W ?
Sep 22 15:23:43 <tinker-f595> as I said it depends on what drive you have
Sep 22 15:24:39 <zumbi> tinker-f595: could you tell an aproximated range?
Sep 22 15:24:45 <rektide> zumbi: the openrd will take <6W.  a SATA disk could peak at up to 15W, if its a beast.
Sep 22 15:25:16 <zumbi> rektide: thanks, so 20W aprox, that's too much for a small solar panel
Sep 22 15:26:30 <tinker-f595> look at 2.5 inch disks...they use much less power than 3.5
Sep 22 15:27:48 <rektide> depending on your storage requirements & what you're trying to do, a usb flash stick consumes less than a 2.5
Sep 22 15:28:23 <rektide> a 2.5" will take up to, i dunno, 8w at worst, for a power hungry drive.  a usb flash stick will take no more than 1w, i'd think.
Sep 22 15:28:36 <zumbi> rektide: i have a 2.5" only USB powered HD, that could do nice low power with sheeva
Sep 22 15:29:04 * zumbi was just wondering on how much would be moving to sata
Sep 22 15:33:42 <tinker-f595> rektide never seen a 2,5 inch sata hdd use more than 5 watts at startup
Sep 22 15:33:59 <tinker-f595> idle is less than a watt
Sep 22 15:34:33 <tinker-f595> remember 2,5 inch drives are designed for laptops etc
Sep 22 15:51:35 <rektide> even 7200 rpm drives?
Sep 22 15:52:18 <rektide> i'vee erred on the side of safeness here, but i still wouldnt be surprised by 8w peaks
Sep 22 15:57:39 <arachnist> hm
Sep 22 15:58:15 <arachnist> too bad the openrd-client doesn't fit in a 5.25" drive bay (like the cdrom drives etc.)
Sep 22 15:59:32 <arachnist> (yes, another computer inside a normal computer would be a nice idea imo. provided they had independent power supplies)
Sep 22 16:00:56 <rektide> theres really no reason the openrd has to be so frakking big
Sep 22 16:07:09 <tinker-f595> rektide especially 7200 rpm drives as they use the latest tech
Sep 22 16:08:01 <rektide> how bout 10k rpm drives? ;)
Sep 22 16:08:05 <tinker-f595> rektide: I wish the open rd came with the drive mounting spacers
Sep 22 16:08:28 <tinker-f595> rektide: have you found one that does not vibrate?
Sep 22 16:08:54 <rektide> heh no; i'm not looking, i'm happy with my ms4um 3.5" enclosure
Sep 22 16:09:06 <tinker-f595> rektide: 10k rpm dries are too expensive
Sep 22 16:09:17 <rektide> theyre all enterprise targetted
Sep 22 16:09:20 <rektide> not surprising
Sep 22 16:09:32 <tinker-f595> rektide: you like power hogs   ;)
Sep 22 16:09:34 <rektide> it is a bit surprising that they all seem to have such limited capacity
Sep 22 16:10:02 <rektide> well, i'm a bit hellbent on optimizing power consumption
Sep 22 16:10:04 <rektide> just in weird ways
Sep 22 16:10:26 <tinker-f595> well you could go expensive and use an ssd
Sep 22 16:10:47 <tinker-f595> "reliable" ssd are expensive
Sep 22 16:10:54 <rektide> ssds dont make sense yet
Sep 22 16:11:19 <tinker-f595> rektide: notice the quotes around "reliable"
Sep 22 16:11:43 <rektide> the latest ocz's and intels are reliable and moderately priced (comparatively)
Sep 22 16:12:07 <rektide> but in two years, any ssd you buy now will look laughably over expensive, horribly under performant, and woefully under capacity
Sep 22 16:13:47 <tinker-f595> and terribly unreliable
Sep 22 16:13:51 <armin76> rabeeh: around?
Sep 22 16:14:22 <tinker-f595> rektide: can you ping dhavel about the openrd git tree?
Sep 22 16:14:38 <rektide> yeah i'll drop by the newsgroup
Sep 22 16:14:42 <rektide> i'm going to try and push for upstream
Sep 22 16:14:56 <morfic> hey tinker-f595
Sep 22 16:15:07 <tinker-f595> rektide: thanks I don't want to ping him about it too many times in a row
Sep 22 16:15:36 <tinker-f595> morfic: I am heading off to work in a minute
Sep 22 16:15:38 <rektide> yup, i understand 100%
Sep 22 16:15:54 <morfic> raid1 resyncing plus moving data from 3rd drive to raid makes for a nice 6.something load :)
Sep 22 16:16:02 <tinker-f595> rektide: remind him about the openrd client code as well and uboot please
Sep 22 16:16:12 <rektide> good plans
Sep 22 16:16:17 <tinker-f595> morifc ???
Sep 22 16:16:43 <tinker-f595> ciao for now
Sep 22 16:16:46 <morfic> tinker-f595: why the ??? do you expect less with a saturated usb bus?
Sep 22 16:17:26 <tinker-f595> morfic wasn't sure of the context of the 6.
Sep 22 16:17:34 <tinker-f595> no units
Sep 22 16:18:02 <morfic> tinker-f595: don't be late for work :)
Sep 22 16:18:27 <morfic> "sory boss, this guy in #openplug was so confusing"... not a good excuse ;)
Sep 22 16:21:43 <rektide> i have yet to run Mono on my openrd
Sep 22 16:21:46 <rektide> i should really do that
Sep 22 16:21:59 <rektide> soon, considering how much code i'm developing specifically for that platform
Sep 22 16:22:19 <tinker-f595> morfic:  haha
Sep 22 16:22:51 <tinker-f595> rektide: mono hmmm
Sep 22 16:23:09 <rektide> i've been porting ioctl's and input.h to mono
Sep 22 16:23:44 <rektide> "fun"
Sep 22 16:32:44 <arachnist> hm
Sep 22 16:33:15 <arachnist> seems like the esata controller on the openrd is a little slower than the sata one in my pc
Sep 22 16:33:18 <arachnist> 4194304000 bytes (4.2 GB) copied, 48.4195 s, 86.6 MB/s
Sep 22 16:33:42 <arachnist> with my pc i get around 100MB/s for reads and writes
Sep 22 16:35:46 <viric> hello all
Sep 22 16:36:08 <viric> I built 2.6.31 for the sheevaplug, and hell, the default config didn't have initrd enabled :)
Sep 22 16:36:26 <viric> About u-boot... I built it with the default sheevaplug config, and I find many feataures missing
Sep 22 16:36:31 <armin76> viric: :D
Sep 22 16:36:32 <viric> for example, the tab-completion
Sep 22 16:36:45 * viric rebuilds 2.6.31
Sep 22 16:36:54 <arachnist> viric: what do you need initrd for, really? :>
Sep 22 16:37:12 <viric> I'm porting an OS that cares on an initrd
Sep 22 16:37:28 <viric> And I don't want to throw their work away on that part :)
Sep 22 16:37:38 <arachnist> which one?
Sep 22 16:37:41 <viric> NixOS
Sep 22 16:38:07 <viric> I don't have any heavier reason than that.
Sep 22 16:38:10 <armin76> arachnist: sata 1.5 or 3?
Sep 22 16:39:17 <arachnist> well, it got detected as a 1.5
Sep 22 16:39:19 <arachnist> 2009-09-22T16:24:53.704016+02:00 stalker kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
Sep 22 16:40:56 <arachnist> but 1.5gbps =~ 150MB/s
Sep 22 16:45:16 <arachnist> cool, switched a jumper on the drive, and now it's 3.0
Sep 22 16:45:17 <arachnist> 2009-09-22T18:44:38.964414+02:00 stalker kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
Sep 22 16:46:01 <arachnist> but it didn't change the results at all. anyway, i can live with 80MB/s
Sep 22 16:46:32 <viric> how do you test that speed?
Sep 22 16:46:39 <morfic> sheeva got no "speaker" to beep with?
Sep 22 16:46:59 <arachnist> viric: dd if=/dev/sde1 of=/dev/null bs=10M count=40
Sep 22 16:47:00 <morfic> looks like he used dd
Sep 22 16:47:30 <viric> ok
Sep 22 16:47:42 <morfic> try with bs=8k and appropriate count, or better yet try tiobench and bonnie++
Sep 22 16:48:06 <morfic> you can also test from /dev/zero to /dev/sde1
Sep 22 16:48:10 <arachnist> it's still about as fast as the ssd in my laptop and a little bit faster than the ata drive i left in my desktop
Sep 22 16:48:37 <arachnist> morfic: from /dev/zero to /dev/sde1 would cause a disaster ;)
Sep 22 16:49:04 <morfic> arachnist: well, i would mount it and write to a file
Sep 22 16:49:20 <morfic> more interesting that the <arachnist> viric: dd if=/dev/sde1 of=/dev/null bs=10M count=40 proposed
Sep 22 16:50:39 <arachnist> well
Sep 22 16:50:40 <arachnist> dd if=/dev/sde1 of=/dev/null bs=8k count=51200
Sep 22 16:50:45 <arachnist> 419430400 bytes (419 MB) copied, 5.19316 s, 80.8 MB/s
Sep 22 16:51:22 <morfic> how fast are writes on that?
Sep 22 16:51:54 <arachnist> dd if=/dev/zero of=/mnt/test.img bs=8k count=51200
Sep 22 16:51:58 <arachnist> 419430400 bytes (419 MB) copied, 4.84035 s, 86.7 MB/s
Sep 22 16:52:25 <arachnist> reasonable speeds, i'd say
Sep 22 16:54:29 <arachnist> /mnt is a 30GB ext3 partition, offset about 10GB from the disk start
Sep 22 16:56:59 <morfic> eewww, lost drives during rsync/resync
Sep 22 16:57:05 <morfic> going back to 2.6.30.6
Sep 22 16:57:21 <morfic> arachnist: nice speeds, yeah
Sep 22 16:57:42 <morfic> at least i hope it's a kernel issue
Sep 22 16:58:14 <viric> morfic: back ?where you were?
Sep 22 16:59:43 <morfic> i was on .30.6 but figured when i reboot it anyway might as well boot 2.6.31, but dmesg on that turned me off, so i went to 2.6.30.7 but with that i had lost drives twice now, first i thought it was a powerblip since got some good weather here, but now, i see drives just went bye
Sep 22 16:59:58 <viric> ?
Sep 22 17:00:04 <morfic> end_request: I/O error, dev sda, sector 963359
Sep 22 17:00:05 <morfic> <morfic> Kernel panic - not syncing: Attempted to kill init!
Sep 22 17:00:05 <viric> now in 2.6.30.6?
Sep 22 17:03:42 <viric> I'll try 2.6.31
Sep 22 17:03:44 <morfic> in a little bit
Sep 22 17:03:58 <morfic> booting from nand?
Sep 22 17:04:56 <viric> no
Sep 22 17:05:02 <viric> SD by now
Sep 22 17:06:52 <morfic> let me know what your dmesg looks like :)
Sep 22 17:07:09 <morfic> .6 has the only clean dmesg
Sep 22 17:07:28 <morfic> .7 still muttered something about mtdsomething being bad, lesson learned
Sep 22 17:15:11 <morfic> oh nice it oopsed even on .6 now
Sep 22 17:19:33 <viric> I booted a bit...
Sep 22 17:19:36 <viric> not perfectly.
Sep 22 17:19:43 <viric> about mtd? let me see
Sep 22 17:19:58 <viric> mtd: partition size too small (0)
Sep 22 17:19:58 <viric> Creating 3 MTD partitions on "orion_nand":
Sep 22 17:19:58 <viric> 0x000000000000-0x000000100000 : "u-boot"
Sep 22 17:19:58 <viric> 0x000000100000-0x000000500000 : "uImage"
Sep 22 17:19:58 <viric> 0x000000500000-0x000020000000 : "root"
Sep 22 17:20:31 <viric> NAND device: Manufacturer ID: 0xad, Chip ID: 0xdc (Hynix NAND 512MiB 3,3V 8-bit)
Sep 22 17:20:34 <viric> Scanning device for bad blocks
Sep 22 17:20:37 <viric> there are some 'bad eraseblocks'
Sep 22 17:27:10 <viric> 2.6.31 works fine here.
Sep 22 17:59:01 <arachnist> http://wstaw.org/images/free/2009/09/22/1588fec65934ed53c7515b0f7c27d8.jpeg
Sep 22 17:59:23 <lennert> arachnist: my seagate 500g drives look exactly like that
Sep 22 18:02:36 <arachnist> i think i'll need to get some stands for that drive, and possibly a cooling fan :/
Sep 22 18:03:08 <arachnist> (because of the heat)
Sep 22 18:03:23 <lennert> my old samsung 500g drives (4 platters?) get hot too
Sep 22 18:03:34 <lennert> i suspect new 500g drives wouldn't get so hot
Sep 22 18:06:57 <arachnist> well
Sep 22 18:07:18 <arachnist> that's a 4-platter 1TB drive (not sure if it's 4-platter)
Sep 22 20:36:50 <morficmobile> can I test the sheeva's memory? I want to know what the segfault was all about mounting md0 earlier.
Sep 22 20:38:28 <morficmobile> never built the memtest bit in kernel.
Sep 22 20:49:15 <viric_> morficmobile: uboot has a memtest
Sep 22 20:49:25 <viric_> iirc
Sep 22 21:58:22 <viric_> Great, sheevaplug works great finally
Sep 22 21:58:39 <viric_> I'm quite happy! :))
Sep 22 23:23:23 <Reedy> http://en.wikipedia.org/wiki/File:SheevaPlug_with_external_drive_enclosure.jpg
Sep 22 23:23:30 <Reedy> Have they moved the usb port on the newer revs?
Sep 22 23:25:37 <morfic> Reedy: why, where is yours?
Sep 22 23:25:51 <Reedy> much closer to the network port
Sep 22 23:25:58 <Reedy> ie right next to it
Sep 22 23:26:22 <Reedy> on that, the usb port and network are further apart
Sep 22 23:26:33 <Reedy> usb is probably same place, but network moved
Sep 22 23:27:55 <morfic> mine has a gap like that picture
Sep 22 23:28:41 <Reedy> hmm
Sep 22 23:30:37 <Reedy> i'd upload a picture if i wasnt about to go to beed
Sep 22 23:30:46 <Reedy> http://plugcomputer.org/plugforum/index.php?topic=771.0
Sep 22 23:30:53 <Reedy> posted it in the forums
**** ENDING LOGGING AT Wed Sep 23 02:59:58 2009