| 00:33:48 | sammy | morning ... |
| 04:07:39 | sammy | feel a little confuse ... |
| 04:09:35 | sammy | before I flash the kernel and ramdisk to flash , what things I must setup ? |
| 04:10:24 | sammy | then the blob can know where my kernel and ramdisk are ... |
| 04:12:20 | sammy | Russ ? BZFlag ? |
| 04:13:07 | sammy | what's the point hint ? |
| 05:08:44 | sammy | ... |
| 05:13:38 | BZFlag | sammy: there are some platform defines in blob for those locations and the mtd setting in the kernel too. |
| 05:14:23 | BZFlag | the mtd layer will only be used to rewrite the kernel/rootfs/bootloader, so that might not be importatnt. |
| 05:15:14 | BZFlag | the kernel gets loaded into ram by the bootloader and so does an initrd (if any). The location of an initrd in ram needs to be passed to the kernel. |
| 05:15:54 | BZFlag | on the tux (and many others) mtd is setup the same as blob for simplicity. |
| 05:16:55 | BZFlag | if you do root on an mtd device ie: jffs2, then you need to setup blob and mtd for that partition and be sure to pass the root device number to the kernel. |
| 05:17:13 | BZFlag | this is generally the preferred procedure. |
| 05:17:32 | sammy | but the case in LART , there is a choos when blob type help , what's flash use to do ? |
| 05:22:11 | BZFlag | "download" copies over the serial line. "boot" boots whats in RAM. "flash" saves what is is ram to flash so it can get reloaded from flash to ram after a reboot. |
| 05:22:24 | BZFlag | the contents of ram are lost on reboot. |
| 05:26:14 | sammy | Alright . is suppose that I compiler the new kernel image , I want update my kernel in LART ... |
| 05:26:57 | sammy | first I must boot from minicom , then ? |
| 05:27:33 | sammy | what's next ? |
| 05:28:20 | sammy | stop in blob ? |
| 05:30:24 | BZFlag | right. then "download kernel" and send the kernel with uuencode in another window (do not exit minicom, start uuencode at a different shell prompt on the same machine) |
| 05:30:47 | BZFlag | then "flash kernel" to put it in flash (if you want) and "boot" to test it. |
| 05:31:13 | BZFlag | you might want to test it a few times before flashing, but I normally just flash it every time. |
| 05:32:23 | BZFlag | then the same procedure for a "ramdisk". If it is a jffs2 image, then you must flash it. if it's a compressed minix or ext2 image then you can run it from ram without flashing. |
| 05:33:48 | sammy | not clear in "send the kernel with uuencode in another window"... |
| 05:36:36 | BZFlag | read http://TuxScreen.net/wiki/view//InstallingLinux |
| 05:36:53 | BZFlag | you are running minicom in an Xterm or similar? |
| 05:37:08 | sammy | yes. |
| 05:37:14 | sammy | Xterm |
| 05:37:41 | BZFlag | then leave that open, and open another xterm. in the new xterm us where you run uuencode after switching baud rates in minicom. |
| 05:38:00 | BZFlag | s/us/is/ |
| 05:38:45 | sammy | when I type download kernel it show.. |
| 05:38:52 | sammy | blob> download kernel |
| 05:38:53 | sammy | Switching to 115200 baud |
| 05:38:54 | sammy | You have 60 seconds to switch your terminal emulator to the same speed and |
| 05:38:55 | sammy | start downloading. After that blob will switch back to 9600 baud. |
| 05:38:56 | sammy | .......ëK...ò |
| 05:39:39 | sammy | so now my speed is 9600 , need to change to 115200, now |
| 05:40:08 | sammy | right ? |
| 05:40:33 | sammy | and leave it alone , and turn another xterm(next) |
| 05:41:53 | BZFlag | yes, change speed first. in minicom that's ctrl-a, p, i. |
| 05:42:39 | BZFlag | but you only have 60 seconds to do that and start the upload. else you have to switch back to 9600 and type the download command again. |
| 05:43:00 | BZFlag | bbiab |
| 06:08:38 | sammy | Tim , I want to order the Tuxscreen... |
| 06:40:22 | BZFlag | cool. |
| 06:40:35 | BZFlag | http://TuxScreen.net/wiki/view//TimRiker |
| 06:44:47 | sammy | if I download the kernel , I must also download the ramdisk too ? |
| 06:57:04 | BZFlag | or have a working ramdisk in flash. |
| 06:58:41 | sammy | if don't do that , then kernel will not find the ramdisk , and can't run it right ? |
| 06:59:49 | sammy | because , I only download the kernel so when I reboot , it only run to .. |
| 06:59:52 | sammy | INIT: Id "2" respawning too fast: disabled for 5 minutes |
| 06:59:53 | sammy | INIT: no more processes left in this runlevel |
| 07:02:55 | BZFlag | if you go INIT then it did find a root filesystem. |
| 07:03:10 | BZFlag | if you got INIT messages then it did find a root filesystem. |
| 07:03:51 | BZFlag | in this case it looks like your kernel worked, and your root filesystem is a bit messed up. |
| 07:04:20 | BZFlag | grep ^2 /etc/inittab to find the line that is failing. |
| 07:06:16 | sammy | kmod: failed to exec /sbin/modprobe -s -k char-major-4, errno = 2 |
| 07:07:06 | sammy | I download the radmdisk , it show the massage more 30 time's ... |
| 07:08:21 | BZFlag | got /sbin/modprobe on your ramdisk? |
| 07:08:56 | sammy | then make another ramdisk and download it agail right ? |
| 07:09:14 | BZFlag | hmm... char-major-4 is the tty. |
| 07:09:29 | BZFlag | got serial console and virtual terminal compiled in? |
| 07:10:28 | BZFlag | might want to turn off kernel modules support and compile everything static until you at least boot. |
| 07:11:29 | sammy | sorry, but it's still can boot ... |
| 07:12:32 | sammy | just no idea and less knowledge about why this massage show... |
| 07:15:19 | BZFlag | try adding "init=/bin/sh" to the kernel command line. |
| 07:21:04 | sammy | is try to find out where to add this command ? |
| 07:23:38 | BZFlag | do a "boot init=/bin/sh" and that should work. if you have other command line options compiled in, you might want to add those as well. |
| 08:00:19 | seletz | Good morning |
| 08:03:20 | erikm | morning |
| 08:03:32 | erikm | gets coffee |
| 08:05:04 | sammy | morning erikm |
| 08:06:16 | sammy | BZFlag : I type it , but it show can't fine the bash boot . |
| 08:08:34 | BZFlag | sammy you did init=/bin/sh ? |
| 08:08:51 | BZFlag | that should be ash or something, not bash. |
| 08:08:57 | seletz | caffeine refill |
| 08:08:59 | BZFlag | well, probably anyway. |
| 08:09:22 | BZFlag | ack.. if you guys are waking up, I should really get to bed. |
| 08:15:15 | erikm | calculates |
| 08:15:26 | erikm | yes, BZFlag, it's 2:20 in the morning |
| 08:15:37 | erikm | same time a I finally got to sleep :) |
| 08:17:32 | sammy | yap, you should need some sleep ...(suggest, if you tired) |
| 08:18:01 | ed__ | it's only 5:17 here |
| 08:18:14 | erikm | slaps ed__ into bed |
| 08:18:35 | ed__ | ach! das macht spass! |
| 08:19:01 | sammy | ed__ morning or evering ? |
| 08:19:10 | ed__ | am |
| 08:19:29 | sammy | because here also 5:17... |
| 08:19:38 | ed__ | hooray |
| 08:19:42 | sammy | but is PM.. |
| 08:19:48 | ed__ | where are you? |
| 08:19:59 | sammy | Taiwan |
| 08:20:06 | sammy | and you ? |
| 08:20:07 | ed__ | ahhh |
| 08:20:16 | ed__ | US, georgia, atlanta |
| 08:29:02 | seletz | erikm: Hello, got your mail about volatile, barrier() and my goto DONE :^) |
| 08:29:49 | seletz | erikm: my gotos are not for the compile, they are for me. IMHO its easyser to |
| 08:29:54 | sammy | is flash his ramdisk again ... |
| 08:30:18 | seletz | erikm: read when a func has _only_ one exit point. |
| 08:30:23 | erikm | seletz: I disagree |
| 08:30:35 | erikm | seletz: goto is considered dangerous |
| 08:30:55 | ed__ | sometimes its ok :P |
| 08:31:00 | seletz | erikm: ahhhh. dijkstra (how do you spell this name) |
| 08:31:01 | erikm | seletz: it's usually bad coding style, and in your cases it definitvely was |
| 08:31:45 | seletz | erikm: _this_ case of goto is _not_ meant in his doc. |
| 08:31:55 | erikm | seletz: the only way goto is considered good is if you want an ordered way to clean up things |
| 08:32:16 | erikm | seletz: like in module initialisation functions in a linux kernel module |
| 08:32:22 | seletz | erikm: mein reden. aerm. yes. thats exactlay what i try to do. |
| 08:33:00 | seletz | erikm: keep only one exit point. after DONE: one can clean up everything neatly. |
| 08:33:13 | seletz | erikm: code complexity goes way down. |
| 08:33:15 | erikm | seletz: Peek() and Poke() didn't clean up anything |
| 08:33:26 | seletz | erikm: yes. agreed. |
| 08:33:38 | erikm | seletz: ret = 2; goto DONE; is evil. you just want return 2 |
| 08:33:42 | seletz | erikm: thats because i use macros in vim :^) |
| 08:34:19 | seletz | erikm: no flame wars meant, but _why_ is it evil? |
| 08:35:06 | erikm | seletz: oops, sorry, SIGMANAGEMENT, I have an urgent meeting |
| 08:35:31 | seletz | erikm_meeting: tzhere you go :^D |
| 08:40:15 | seletz | can someone here explain me the workings of the barrier() macro? |
| 09:26:19 | seletz | coding |
| 09:41:15 | sammy | erikm: you are back... |
| 09:41:23 | erikm | seletz: the barrier macro is an empty inline assembly statement which fools gcc to think that it makes memory references |
| 09:42:14 | erikm | seletz: but we don't specify what memory reference, so the only thing the compiler can do is to commit all outstanding memory references |
| 09:42:51 | sammy | I use your kernel and ramdisk , but when the LART boot , it's run this about more then 30 time's then stop and show login : what's the program in this error massage ? |
| 09:42:53 | sammy | kmod: failed to exec /sbin/modprobe -s -k char-major-4, errno = 2 |
| 09:42:54 | sammy | kmod: failed to exec /sbin/modprobe -s -k char-major-4, errno = 2 |
| 09:42:55 | sammy | Itsy Linux (experimental) |
| 09:42:56 | sammy | Kernel 2.0.30 on sa1100/brutus |
| 09:42:57 | sammy | login: |
| 09:43:26 | erikm | ignore the kmod errors |
| 09:44:00 | sammy | what's that ? |
| 09:44:41 | erikm | it tries to open /dev/tty0 which is not there |
| 09:46:25 | sammy | this is serial important ...as you say before , if I don't need to know how the kernel work , if I get the error massage how can I know what's problem with that ? |
| 09:47:26 | sammy | if the kernel is stop at place like this ... |
| 09:47:28 | sammy | INIT: Id "1" respawning too fast: disabled for 5 minutes |
| 09:47:29 | sammy | kmod: failed to exec /sbin/modprobe -s -k char-major-204, errno = 2 |
| 09:47:30 | sammy | kmod: failed to exec /sbin/modprobe -s -k char-major-204, errno = 2 |
| 09:47:31 | sammy | INIT: Id "2" respawning too fast: disabled for 5 minutes |
| 09:47:32 | sammy | INIT: no more processes left in this runlevel |
| 09:48:13 | erikm | you are using an incompatible ramdisk-kernel compbination |
| 09:48:24 | erikm | char-204 is /dev/ttySA0 |
| 09:49:26 | erikm | my ramdisk-new-tty with linux-2.4.9-ac9-rmk1-np1 is a known good combination |
| 09:57:21 | sammy | what is a secret of success to make my own ramdisk to match the kernel ? |
| 09:57:44 | erikm | easy: use the correct serial ports |
| 09:58:19 | sammy | blurred ...@_@ |
| 10:06:00 | sammy | reload again ... |
| 10:14:32 | sammy | now flash it again... |
| 10:16:38 | sammy | error.... |
| 10:16:49 | sammy | EXT2-fs error (device ramdisk(1,0)): ext2_write_inode: unable to read inode block - inode=1161, block=8202 |
| 10:16:50 | sammy | attempt to access beyond end of device |
| 10:16:51 | sammy | 01:00: rw=0, want=8204, limit=8192 |
| 10:16:52 | sammy | EXT2-fs error (device ramdisk(1,0)): ext2_write_inode: unable to read inode block - inode=1172, block=8203 |
| 10:16:59 | sammy | Stop ....Why ? |
| 10:19:42 | erikm | because of ext2 errors |
| 10:19:56 | erikm | so your ramdisk image got somehow corrupted |
| 10:52:52 | sammy | you know . that I only change your source and nothing add , but just rebuild again ...so strange |
| 11:02:11 | seletz | hi all |
| 11:02:32 | seletz | coding |
| 12:31:28 | prpplague | morning all |
| 12:32:19 | seletz | hi |
| 12:32:45 | seletz | coding |
| 13:19:27 | sammy_ | night all... |
| 13:19:38 | seletz | goodnight |
| 13:49:57 | seletz | well, i'm off too. memory test from Charles Cazabon now runs, we'll see if i |
| 13:50:13 | seletz | have a mem fault on monday :) |
| 13:50:27 | erikm | ok, bye |
| 13:50:36 | prpplague | have a good weekend |
| 13:50:54 | prpplague | oops, alittle slow this morning |
| 13:50:59 | erikm | hehe |
| 13:51:20 | erikm | just filled the bug and feature request page on the blob sourceforge page |
| 13:52:15 | prpplague | erikm: should create a seperate patch for blob as secondary bootloader, or should i be work on integrating the code into the standard base? |
| 13:52:24 | prpplague | s/should/should i |
| 13:52:49 | erikm | I think it should be nice to have in the standard code base |
| 13:53:09 | erikm | though I think it is only a differend first stage loader, right? |
| 13:53:33 | erikm | s/differend/different/ |
| 13:54:10 | prpplague | erikm: ya that and a couple changes in the default DEFINES |
| 13:54:45 | erikm | would be nice enough to have |
| 13:55:17 | prpplague | erikm: ok then, thats where i'll head |
| 14:45:22 | erikm | hmm, a lart without blob-2.0.4, and it was even lying on my desk.... shame |
| 14:47:35 | erikm | reflashes |
| 14:55:12 | erikm | ah, much better |
| 14:58:54 | erikm | hi Russ |
| 14:59:16 | prpplague | welcome back Russ |
| 15:18:21 | prpplague | well my tuxscreen just arrived... |
| 15:18:46 | prpplague | it makes my cisco phone look antique |
| 15:18:59 | erikm | hehe |
| 16:06:52 | prpplague | is away: lunch |
| 17:29:35 | prpplague | is back (gone 01:22:42) |
| 17:58:48 | erikm | Russ: you there? |
| 18:03:34 | erikm | Russ: anyway, I added a couple of bugs and patches I know about on the sourceforge project pages |
| 18:04:03 | erikm | Russ: is it OK if I assign the parameter block support to you? |
| 18:04:14 | erikm | Russ|werk: or to Russ|werk? :) |
| 18:10:35 | Russ|werk | yah |
| 18:10:54 | Russ|werk | have you tried 2.4.9-ac10-rmk2-(np1) |
| 18:11:21 | erikm | not yet |
| 18:11:30 | erikm | -ENOTIME last week |
| 18:11:46 | Russ|werk | mount gets stuck on the 'D' state for me in checkroot.sh |
| 18:12:02 | Russ|werk | don't know if its teh kernel, or something I did to it |
| 18:12:14 | Russ|werk | haven't seen anything in linux-arm-kernel |
| 18:13:30 | erikm | no, me neither |
| 18:19:07 | erikm | Russ|werk: could you sysrq-t the system and decode the address to see where it is stuck? |
| 18:20:09 | erikm | Russ|werk: and post results to linux-arm-kernel? |
| 18:20:27 | erikm | Russ|werk: or directly to rmk |
| 18:22:44 | erikm | hi tim |
| 18:23:21 | Russ|werk | erikm: which address would I look at? |
| 18:24:28 | erikm | the stuck mount |
| 18:25:08 | erikm | Russ|werk: it should be hanging somewhere in kernel, and it's nice to know where exactly |
| 18:25:36 | Russ|werk | then I can look that up in my symbols? |
| 18:25:56 | erikm | yes |
| 18:37:04 | erikm | goes home |
| 18:37:08 | erikm | bye |
| 18:37:14 | prpplague | later |
| 19:27:48 | prpplague | howdy everyone |
| 19:28:08 | prpplague | BZFlag: got my tuxscreen today! |
| 19:44:14 | BZFlag | prpplague: sweet. the hacking begins. ;-) |
| 23:53:16 | prpplague | later all |