| 00:45.11 | RobNC | <PROTECTED> |
| 00:54.02 | RobNC | kowalcyk: is hard drive spinning up, is it self-powered or 2.5" bus-powered? |
| 01:22.29 | rwhitby | RobNC: mtn protocol is over a different port |
| 01:22.53 | rwhitby | Sinclair73de: reflash doesn't work when apex is used. |
| 01:23.45 | rwhitby | Sinclair73de: /proc/mtd from SlugOS 4.8/BE (LE should be identical): |
| 01:23.46 | rwhitby | dev: size erasesize name |
| 01:23.46 | rwhitby | mtd0: 00040000 00020000 "RedBoot" |
| 01:23.46 | rwhitby | mtd1: 00020000 00020000 "SysConf" |
| 01:23.46 | rwhitby | mtd2: 00020000 00020000 "Loader" |
| 01:23.48 | rwhitby | mtd3: 00120000 00020000 "Kernel" |
| 01:23.48 | rwhitby | mtd4: 00640000 00020000 "Flashdisk" |
| 01:23.51 | rwhitby | mtd5: 00020000 00020000 "FIS directory" |
| 01:24.23 | rwhitby | Sinclair73de: did you build slugosle for ixp4xxle or nslu2le ? You get a different kernel depending on that setting. |
| 01:25.06 | rwhitby | RobNC: did slugimage finally work for you? |
| 01:27.19 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |
| 01:47.12 | *** join/#nslu2-linux simond (n=simon@76.74.139.38) |
| 04:01.08 | *** join/#nslu2-linux DrZimmerman (n=theo@77-56-246-76.dclient.hispeed.ch) |
| 04:22.18 | *** join/#nslu2-linux edmondsc (n=edmondsc@c-24-22-21-198.hsd1.mn.comcast.net) |
| 04:24.47 | *** join/#nslu2-linux Sinclair73de_ (n=Sinclair@p57B4843A.dip0.t-ipconnect.de) |
| 04:29.41 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |
| 05:06.30 | *** join/#nslu2-linux mithro (n=tim@unaffiliated/mithro) |
| 05:11.43 | *** join/#nslu2-linux HopsNBarley (n=hops@nslu2-linux/HopsNBarley) |
| 05:54.12 | *** join/#nslu2-linux kowalczyk (n=kowalczy@128.80-202-137.nextgentel.com) |
| 06:00.12 | *** join/#nslu2-linux drath_ (i=vmaster@p5B07F995.dip.t-dialin.net) |
| 06:29.28 | *** join/#nslu2-linux forecastius (n=forecast@apoc.mythi.cx) |
| 07:01.58 | *** join/#nslu2-linux erikja (n=erikja@0x57314066.abnxx10.adsl-dhcp.tele.dk) |
| 07:30.35 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |
| 09:06.59 | *** join/#nslu2-linux pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 09:35.59 | *** join/#nslu2-linux kolla (n=kolla@haugum.uninett.no) |
| 10:03.03 | *** join/#nslu2-linux forecastius (n=forecast@apoc.mythi.cx) |
| 10:11.48 | *** join/#nslu2-linux kowalczyk (n=kowalczy@128.80-202-137.nextgentel.com) |
| 10:35.22 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |
| 11:09.28 | *** join/#nslu2-linux kowalczyk (n=kowalczy@128.80-202-137.nextgentel.com) |
| 11:35.46 | *** join/#nslu2-linux GPSFan (n=kenm@12.10.255.246) |
| 11:50.45 | *** join/#nslu2-linux RobNC (i=4157acf4@gateway/web/ajax/mibbit.com/x-d9e54d24cc4a3224) |
| 11:51.26 | *** join/#nslu2-linux RobNC_ (i=4157acf4@gateway/web/ajax/mibbit.com/x-7968e07ee9cc53a3) |
| 11:52.23 | *** join/#nslu2-linux RobNC (i=4157acf4@gateway/web/ajax/mibbit.com/x-eb9e3db6886d33b3) |
| 12:26.07 | *** join/#nslu2-linux eno__ (n=eno@adsl-70-137-143-151.dsl.snfc21.sbcglobal.net) |
| 12:35.17 | *** join/#nslu2-linux osmeest (n=olivier@d83-186-177-181.cust.tele2.be) |
| 12:35.37 | osmeest | hi |
| 12:35.53 | osmeest | I'm trying to run Debian on an Iomega NAS 100d |
| 12:36.27 | osmeest | problem: the apex in slugos/LE does not support the ram disk (needed by debian) |
| 12:36.53 | osmeest | and the apex in debian does not work with the NAS 100d (kind of FatSlug) |
| 12:37.16 | osmeest | anyone knows how/where I could get an APEX that works with debian ? |
| 12:37.38 | osmeest | (or how to recompile APEX for debian on the NAS) |
| 12:39.53 | Sinclair73de | Hi osmeest |
| 12:40.58 | Sinclair73de | I think the difference between with or without ramdisk is only the "startup" and "cmdline" settings in apex |
| 12:41.43 | Sinclair73de | do u have access to the apex-console? |
| 12:43.15 | osmeest | yes through serial line |
| 12:43.22 | osmeest | apparently, there is more than that |
| 12:43.33 | osmeest | there is an ATAG-INITRD2 which needs to be set |
| 12:44.16 | osmeest | when I use the apex from debian, the ATAG is set but the kernel does not like the ramdisk format |
| 12:44.29 | Sinclair73de | i see... |
| 12:44.36 | osmeest | when I use the apex from slugos, the ATAG is not set so the ramdisk is ignored by the kernel |
| 12:44.51 | Sinclair73de | i'm using a fatslug with 2 apex |
| 12:45.26 | Sinclair73de | my first apex (redboot replacement) has the ATAG_INITRD2 and the second not |
| 12:45.55 | osmeest | I did not dare to replace redboot, so I use it only as a secondary bootloader |
| 12:46.02 | osmeest | it works ok with slugos |
| 12:46.18 | osmeest | debian boots but the mounting of root (initrd) fails |
| 12:47.00 | Sinclair73de | i did the ram upgrade 2 years ago... at this time no second stage bootloader was available |
| 12:47.36 | Sinclair73de | and the cmdline is correct? |
| 12:47.38 | osmeest | lucky I am... I had only to solder the serial port on the NAS motherboard |
| 12:48.32 | osmeest | I guess (I use the default one from the Debian APEX) |
| 12:48.51 | osmeest | the one from slugos specifies the root and rootfstype (jffs2) |
| 12:49.27 | Sinclair73de | no init= ? |
| 12:49.36 | osmeest | no |
| 12:50.02 | osmeest | but the problem is earlier: it complains about no root being defined or accessible |
| 12:51.07 | Sinclair73de | console=ttyS0,115200n8 root=/dev/mtdblock4 rootfstype= |
| 12:51.07 | Sinclair73de | jffs2 rw init=/linuxrc noirqdebug |
| 12:51.25 | osmeest | that's for slugos and works ok |
| 12:51.33 | osmeest | but initrd is not jffs2 |
| 12:52.16 | Sinclair73de | but i dont know if this is working, because that loads only my second apex |
| 12:52.47 | osmeest | what's the cmdline for the apex that loads the debian kernel ? |
| 12:52.59 | osmeest | (the second apex boot command) |
| 12:56.26 | Sinclair73de | a i changed the cmdline of the first to that from the second |
| 12:56.34 | Sinclair73de | so now, both are the same |
| 12:56.51 | Sinclair73de | but the difference was in the startup command too |
| 12:57.12 | Sinclair73de | do u have 1 or 2 copy commands in the startup |
| 13:00.10 | osmeest | two for debian |
| 13:00.14 | osmeest | one for slugos |
| 13:01.08 | osmeest | something like copy $kernelsrc $bootaddr; copy $ramdisksrc $ramdiskaddr; wait... ; boot |
| 13:01.18 | Sinclair73de | i think two are correct for ramdisk |
| 13:01.49 | osmeest | it looked fine to me too... |
| 13:02.02 | osmeest | but the kernel does not recognize the ramdisk |
| 13:02.27 | osmeest | I've the impression the address of the ramdisk is wrong in the debian apex |
| 13:02.51 | osmeest | and the ramdisk is simply ignored when using the slugos apex |
| 13:07.14 | osmeest | one thing I'm not sure also is whether the ramdisk of debian has to be byteswapped to be recognized by the kernel |
| 13:07.34 | osmeest | I would hope not (because both slugosle and debian are little endian) |
| 13:08.35 | Sinclair73de | i dont know... |
| 13:12.08 | osmeest | OK thanks anyway for trying :) |
| 13:13.30 | Sinclair73de | is the nas proc the same like in the nslu2? |
| 13:18.33 | osmeest | I think so (Intel IXP420) |
| 13:18.59 | osmeest | the bootloader is a little different (no network support - hence the serial port I had to add) |
| 13:19.30 | osmeest | the memory is bigger and it comes with an internal HDD of 250MB |
| 13:20.00 | Sinclair73de | and >64MB RAM are running stable and fast? |
| 13:20.34 | osmeest | it has 64MB of RAM |
| 13:21.46 | osmeest | slug has 32 as I've read |
| 13:22.58 | osmeest | fast: it all depends to what you compare... compared to my PC, it's horribly slow |
| 13:23.13 | osmeest | file transfers with SSH are quite slow also |
| 13:23.24 | osmeest | but SMB or FTP is OK |
| 13:23.41 | Sinclair73de | ok, 64MB is ok |
| 13:24.00 | osmeest | I ran slug os for sometime which was fine but HPLIP is not available for it |
| 13:24.13 | osmeest | so I wanted to go to Debian so to be able to install it |
| 13:24.25 | Sinclair73de | my fatslug is running with 64MB "fast" and stable, but still not with 128MB |
| 13:25.00 | osmeest | it becomes what with 128MB ? slow ? unstable ? or both ? |
| 13:25.19 | Sinclair73de | both |
| 13:25.29 | osmeest | aouch! |
| 13:28.00 | osmeest | I would not dare to use a soldering iron in such a device... I'm too much of a software guy... |
| 13:28.27 | osmeest | (at least not for piggybacking memory chips) |
| 13:29.10 | Sinclair73de | i'm both, but everything only for 50% ;-) |
| 13:30.11 | *** join/#nslu2-linux x29a (n=x29a@unaffiliated/x29a) |
| 13:30.37 | osmeest | hehe |
| 13:30.46 | osmeest | OK, I've got to go... |
| 13:31.00 | osmeest | see you and thx again for trying to help :) |
| 13:31.18 | Sinclair73de | ok, sry... |
| 13:31.21 | Sinclair73de | bye! |
| 13:35.30 | *** join/#nslu2-linux HopsNBarley (n=hops@nslu2-linux/HopsNBarley) |
| 13:37.37 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |
| 13:53.48 | rwhitby | osmeest: apex for nas100d: http://ipkg.nslu2-linux.org/feeds/kernel/ |
| 13:58.26 | rwhitby | osmeest: but you don't actually need apex for debian on nas100d, since nas100d has working fis support in redboot, so you can size the kernel and ramdisk partitions however you want. |
| 13:58.59 | rwhitby | (I have two nas100d boxes, one of which runs Debian) |
| 14:07.44 | *** join/#nslu2-linux Ragnor (n=Ragnor@dslb-084-060-152-200.pools.arcor-ip.net) |
| 14:09.37 | osmeest | rwhitby: I thought it was needed for big kernels... |
| 14:10.41 | osmeest | if I put debian kernel in kernel and the debian initrd in filesystem (or was it ramdisk), what's the cmdline to boot it properly then ? |
| 14:10.49 | osmeest | do I need to byteswap the initrd ? |
| 14:29.46 | *** join/#nslu2-linux DrZimmerman (n=theo@77-56-246-76.dclient.hispeed.ch) [NETSPLIT VICTIM] |
| 15:04.01 | *** join/#nslu2-linux erikja (n=erikja@0x57314066.abnxx10.adsl-dhcp.tele.dk) |
| 15:29.34 | CIA-45 | 03bzhou * r8286 10optware/trunk/make/zile.mk: zile: 2.2.56 -> 2.2.58 |
| 15:33.32 | *** join/#nslu2-linux eno (n=eno@nslu2-linux/eno) |
| 16:03.26 | osmeest | rwhitby: when do you know you have to byteswap ? I tried the debian kernel straight... I just get one line starting with a $ sign (I guess I need to swap) |
| 16:03.59 | osmeest | rwhitby: but what about the initial ramdisk then ? to swap or not to swap... |
| 16:06.49 | *** join/#nslu2-linux eiffel (n=eiffel@dslb-084-061-038-050.pools.arcor-ip.net) |
| 16:40.33 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |
| 17:07.32 | *** join/#nslu2-linux kolla (i=kolla@firda.kolla.no) |
| 17:39.50 | kowalczyk | I had trouble getting debian working on my nslu2 yesterday. I tried upslug... Now I tried the webbrowser. when I press start upgrade I get disconnected from web browser |
| 17:41.52 | osmeest | on the NAS100d, upslug is not an option because it has a different version of redboot (no upgrade mode, no sercomm) |
| 17:50.32 | *** join/#nslu2-linux kowalczyk (n=kowalczy@128.80-202-137.nextgentel.com) |
| 18:26.00 | *** join/#nslu2-linux Reedy (n=Reedy@wikimedia/Reedy-Boy) |
| 18:30.16 | kowalczyk | I'm having problem installing debian on my nslu2. I have tried both upslug2 and webinterface. I install it. and its okay. but when It reboots nothing happens. I plug my harddrive to it. but the light dosen't light, and I cant ssh to it. It just a orange light:( |
| 18:32.23 | kowalczyk | im using the last debian unofficial |
| 18:32.36 | mwester | kowalczyk: Use only upslug2 (webinterface is not reliable on any firmware,really). |
| 18:32.51 | Reedy | and please dont duplicate this in both channels |
| 18:32.52 | mwester | kowalczyk: Start by flashing the original Linksys firmware, and making sure that boots. |
| 18:33.08 | kowalczyk | it does |
| 18:33.25 | kowalczyk | I have booth tried upslug2 and webinterface |
| 18:33.45 | mwester | Then change the network settings using the Linksys firmware to use a static network address NOT 192.168.1.77 -- and fill in all the network items (gateway, netmask, DNS servers). |
| 18:34.07 | mwester | Once you have set all those, reboot, make sure that the firmware boot up with the network settings. |
| 18:34.31 | mwester | Then shut down, use upslug2 to flash the debian binary, and it should appear on the assigned network address as expected. |
| 18:35.03 | kowalczyk | I have done that 2 |
| 18:35.17 | kowalczyk | it has ip 10.0.0.7 |
| 18:35.55 | kowalczyk | and it doesnt show up on the network |
| 18:36.12 | kowalczyk | its inactiv when I check my router |
| 18:36.50 | kowalczyk | can it be something wrong with the rc3 version of debian? |
| 18:37.57 | Reedy | how long have you given it after the post flash reboot? |
| 18:38.22 | kowalczyk | yesterday 1 - 1.5 hour |
| 18:38.50 | kowalczyk | and nothing happens |
| 18:38.53 | kowalczyk | just a orange light |
| 18:52.24 | kowalczyk | anyone have an idea what can be wrong_ |
| 18:52.28 | kowalczyk | ? |
| 18:56.41 | kowalczyk | can it be a good idea trying rc2 instead of rc3? |
| 19:19.18 | *** join/#nslu2-linux Reedy (n=Reedy@wikimedia/Reedy-Boy) |
| 19:43.45 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |
| 19:58.52 | rwhitby | osmeest: nas100d has no limit on kernel size - that's an nslu2 redboot limitation only |
| 19:59.35 | osmeest | rwhitby: really ? I tried to boot the kernel from redboot, it gave the infamous $junk line |
| 19:59.41 | rwhitby | osmeest: you need to swap or not depending on the endianness of your bootloader. nas100d bootloader is BE, so you need to swap. |
| 20:00.03 | osmeest | then I tried a byteswapped version, which showed some garbled text |
| 20:00.17 | *** join/#nslu2-linux awolf (n=admin@butler.math.umn.edu) |
| 20:00.57 | osmeest | this thing is really driving me nuts... slugos was really easy to install once I found out that there were precompiled packages for the NAS100d |
| 20:01.09 | rwhitby | osmeest: what garbled text? |
| 20:01.12 | osmeest | debootstrapping was not more complicated |
| 20:01.31 | osmeest | when the kernel booted, I saw some text but it was unreadable |
| 20:01.47 | osmeest | it was not like the $junk line |
| 20:02.00 | rwhitby | Was there any text that was readable (like "Uncompressing kernel") ? |
| 20:02.02 | osmeest | more like some text that would have been byteswapped |
| 20:02.17 | osmeest | no, that's what I hoped for but it was not there |
| 20:02.40 | rwhitby | oh, did you add the kernel prepend to switch the processor into le mode? |
| 20:03.04 | rwhitby | (which is one thing that apex does) |
| 20:03.05 | osmeest | heu... no... what's that ? |
| 20:03.27 | rwhitby | come to think of it, it's probably easier just to put apex on the nas100d as a second stage. |
| 20:03.34 | rwhitby | why don't you just do that? |
| 20:03.37 | osmeest | that's why using APEX, it booted then :) |
| 20:03.46 | osmeest | I did |
| 20:03.55 | rwhitby | ok, so what's the status now? |
| 20:03.56 | osmeest | but then it does not recognize the ramdisk |
| 20:04.21 | rwhitby | are you using the nas100d debian apex? |
| 20:05.09 | osmeest | I think its the debian apex but not the 100d specific |
| 20:05.34 | rwhitby | that won't work then |
| 20:05.37 | rwhitby | apex is board specific |
| 20:05.48 | rwhitby | you can't use an nslu2 apex on anything else |
| 20:06.10 | osmeest | ah :( I thought all those devices were closer than what they really are then |
| 20:06.35 | osmeest | so to summarize, I flash byteswapped kernel and ramdisk |
| 20:06.44 | rwhitby | well, for a start apex needs to set up the correct machine id for the board, since the vendor bootloader on these type of devices hardly ever does that correctly. |
| 20:06.56 | rwhitby | use the debian nas100d apex |
| 20:07.02 | osmeest | I flash the apex for debian on nas100d from the ipkg feed |
| 20:07.06 | rwhitby | you don't need to byteswap anything then |
| 20:07.45 | rwhitby | make sure apex is at 0xfa0000 in the flash, with an 0x20000 length. |
| 20:08.00 | rwhitby | (it's compiled so that the environment region appears near the end of that erase block) |
| 20:08.21 | osmeest | oh ho... mine is not at that address |
| 20:08.35 | osmeest | will have to play with redboot fis :) |
| 20:08.38 | rwhitby | yep |
| 20:08.44 | rwhitby | or recompile apex with a different config |
| 20:09.08 | osmeest | it's easier to play with fis... |
| 20:09.08 | rwhitby | put kernel, then rootfs, then sysconfig (if you want slugos sysconf to work), then apex |
| 20:09.48 | rwhitby | I have compiled these apex images to always assume that apex is the last block before the fis stuff at the end of the flash |
| 20:09.58 | osmeest | I did my best to keep sysconf at its original location (but shrunk it to make space for apex config) |
| 20:10.10 | rwhitby | (BTW, I'm expecting you to be writing a wiki page up with all this info in it - are you prepared to do that?) |
| 20:10.46 | osmeest | when I manage to put debian on my slug, I'm ready for doing it yes |
| 20:11.07 | osmeest | the procedure is much simpler than when I started my slug experiments last year |
| 20:11.53 | osmeest | honnestly, information about those byte swapping and what the bootloaders are doing about it should be made available in one page |
| 20:12.08 | osmeest | that's the thing I'm doing trial and error to proceed |
| 20:12.19 | osmeest | and even so, I can't find my way without bothering you :) |
| 20:12.32 | rwhitby | yep, and I'm expecting you to put a page on the wiki where you would have been expecting to find that info |
| 20:12.54 | *** join/#nslu2-linux DrZimmerman (n=theo@77-56-246-76.dclient.hispeed.ch) |
| 20:14.29 | rwhitby | debian-nas100d-arm_config has CONFIG_ENV_REGION="nor:0xfbc000+15k" |
| 20:14.29 | rwhitby | <PROTECTED> |
| 20:14.55 | osmeest | yep, saw that in slugos version as well |
| 20:14.56 | rwhitby | that mandates where you put the apex binary in flash. I usually use "apex" as the fis directory entry name. |
| 20:15.14 | osmeest | I had a fis partition for it but it ignores it apparently |
| 20:15.18 | rwhitby | yep, I put apex in the same location on both |
| 20:15.36 | rwhitby | you then need to change fconfig to "fis load apex ; go" |
| 20:15.49 | rwhitby | so that redboot palms off to apex |
| 20:15.53 | osmeest | that's what I have already |
| 20:16.15 | rwhitby | what's it ignoring then? |
| 20:16.33 | osmeest | apex does not use my apex config partition |
| 20:16.54 | osmeest | I thought it would check on the partition names |
| 20:17.43 | osmeest | I have "apex" and "apex config" |
| 20:17.50 | osmeest | but only apex is used |
| 20:19.04 | rwhitby | no, it uses a hard coded flash address |
| 20:19.34 | rwhitby | and there's no need for a separate config partition |
| 20:19.57 | osmeest | I know why I did that: in FisList page, there is a partition scheme for LudeBoot which has a separate config partition |
| 20:20.26 | rwhitby | yeah, but ludeboot is a redboot replacement, it's not apex. |
| 20:20.55 | rwhitby | actually, I'd like you to add an apex/debian fis scheme on that page. |
| 20:26.09 | osmeest | OK |
| 20:26.13 | osmeest | I'll do |
| 20:27.12 | osmeest | BTW, on the NAS, there was a usr partition which seemed unused by the original firmware |
| 20:28.07 | osmeest | at some point, I merged the filesystem and usr partitions to make room for the slugos rootfs |
| 20:33.58 | osmeest | what do you think about it ? keep it or merge them ? |
| 20:34.42 | rwhitby | for slugos, merge them, cause you can run from jffs2. |
| 20:34.58 | rwhitby | for debian, it doesn't matter, cause it doesn't use rootfs after installation |
| 20:42.41 | osmeest | can you use debian apex with slug os ? or is it linked to the OS as well ? |
| 20:44.50 | *** join/#nslu2-linux awolf (n=admin@butler.math.umn.edu) |
| 20:45.54 | rwhitby | it's linked to the OS too, however that link is just the default settings - you can change that at the apex command line after installation. |
| 20:46.20 | rwhitby | but it's easiest just to flash the correct one each time |
| 21:19.03 | *** join/#nslu2-linux awolf (n=admin@butler.math.umn.edu) |
| 21:29.16 | *** join/#nslu2-linux kowalczyk (n=kowalczy@128.80-202-137.nextgentel.com) |
| 21:38.33 | osmeest | rwhitby: I'll try with the right apex in the right flash location tomorrow and hopefully have good news :) |
| 21:38.39 | osmeest | see you tomorrow |
| 22:09.36 | *** join/#nslu2-linux awolf (n=admin@butler.math.umn.edu) |
| 22:46.45 | *** join/#nslu2-linux osas (n=nnnnnnnn@nslu2-linux/osas) |