07:23:29 | mmatten | morning |
09:28:26 | seletz | morning |
14:41:38 | KuEdE | hi guys |
14:42:41 | KuEdE | Perhaps anyone knows about the source of the "Mounting Rootfs panic"..... could it be a bad toolchain ? |
14:55:45 | KuEdE | Perhaps anyone knows about the source of the "Mounting Rootfs panic"..... could it be a bad toolchain ? |
14:59:06 | prpplague | KuEdE: what is the root device your are trying to use? |
15:01:17 | KuEdE | its a ramdisk root=/dev/ram |
15:01:53 | KuEdE | re :-)) |
15:02:00 | KuEdE | <KuEdE> its a ramdisk root=/dev/ram |
15:02:13 | KuEdE | 01:00 |
15:02:19 | prpplague | did you make sure to do a rdev on your kernel image? |
15:02:48 | KuEdE | :-D .. oups .. whats rdev ? |
15:05:19 | prpplague | KuEdE: when you build a kernel, the root device on the system you build is used as the root device, if you intended on using another device you need to use the rdev command on the image to change the root dev |
15:05:39 | prpplague | you should be able to do a man on rdev and get some additional information |
15:05:45 | KuEdE | thx.... found out @ same moment :-)) |
15:05:55 | KuEdE | ill do .. |
15:06:03 | prpplague | KuEdE: i'm not saying this is the problem, but its one thing to check |
15:07:09 | KuEdE | yeah.. its another point i can look after before i get another toolchain... |
15:07:37 | KuEdE | ... ill do that..have a smoke and tell ya if it works |
15:07:47 | KuEdE | but anyways... thx !! |
16:00:59 | KuEdE | rdev'ing is like (in my case) setting CONFIG_CMDLINE="/dev/ram"..... i tried it but without success... perhaps ill get the lart toolchain instead using the suse ones |
16:01:44 | KuEdE | i mean CONFIG_CMDLINE="root=/dev/ram" |
16:03:01 | KuEdE | 4(0prpplague4) 0 i hope im right.... or are there another things which i got to manipulate with rdev ? |
16:20:02 | Russ | KuEdE: don't use colors excessively |
16:23:53 | seletz | hi |
16:35:12 | prpplague | hey seletz |
16:35:19 | prpplague | doh |
16:36:26 | prpplague | i wonder is seletz will return |
16:51:55 | prpplague | seletz: you made hotel reservations for ottawa yet? |
16:53:39 | seletz | prpplague: yes, i got the confirmation today |
16:53:47 | prpplague | seletz: which hotel? |
16:54:01 | KuEdE | prpplague: got another idea ? Is there a possibility that my toolchain is bad (i use the SuSE one ) ....... |
16:54:07 | seletz | prpplague: well, the one recomended on the ols site |
16:54:13 | prpplague | seletz: ohh |
16:54:25 | seletz | prpplague: hmm? |
16:54:34 | prpplague | seletz: that one seem a little expensive |
16:55:10 | prpplague | KuEdE: sorry, no suggestions off the top of my head |
16:55:23 | seletz | prpplague: well, these are suites, and they mean "+kitchen +sofa (read: 2nd bed!!) etc" |
16:55:39 | seletz | prpplague: so the price is for 2 persons. |
16:55:39 | prpplague | KuEdE: my next guess would be check whether the device is compiled into the kernel |
16:55:52 | prpplague | seletz: ya, its only me |
16:56:27 | prpplague | seletz: btw, did you know there is a beer festival on the 21-23? |
16:56:38 | seletz | prpplague: i checked out some other nearby hotels, but they're comparable expensive. |
16:56:47 | seletz | prpplague: in ottawa? |
16:56:51 | prpplague | seletz: ya |
16:57:18 | seletz | prpplague: doh, booked my flight already. 25 of june arrival. |
16:57:51 | prpplague | seletz: ya i've already booked too, but i'm going to change mine, its actually cheaper too |
16:58:05 | prpplague | seletz: gotta run, bbl |
16:58:13 | seletz | prpplague: see ya |
16:58:13 | prpplague | KuEdE: good luck |
16:58:24 | seletz | KuEdE: what problem do you have? |
16:58:33 | seletz | just curious |
16:58:43 | KuEdE | there compiled in..... im sure.... ill try tomorrow ... BTW: i use the "lart-ramdisk-1.2-lmbench.gz"..... |
16:59:14 | KuEdE | seletz: my kernel doesnt like the ramdisk.... |
16:59:19 | seletz | scratching behind his ear |
16:59:22 | seletz | well, |
16:59:32 | seletz | see ya guys... |
16:59:38 | KuEdE | Unable to mount root fs 01:00..... |
16:59:44 | seletz | ah |
16:59:58 | seletz | use root=/dev/ram0 |
17:00:08 | seletz | be sure to compile in initrd support |
17:00:13 | KuEdE | all done |
17:00:18 | seletz | hmm |
17:00:34 | seletz | how big is your rd? |
17:00:40 | seletz | decompressed i mean |
17:00:50 | KuEdE | its a new sa1110 hw port im doing... so i never can say that HW is 100% ok |
17:01:05 | seletz | hmm, the kernel starts up? |
17:01:11 | KuEdE | but it worx well on WinshitCE |
17:01:19 | seletz | hmm |
17:01:27 | KuEdE | i mean... WinCE woks well ON this hardware ;-) |
17:01:57 | seletz | maybe you want to take a look at my initial ramdisk, its quite minimal |
17:02:01 | KuEdE | my .config is very similar to lart's one |
17:02:08 | KuEdE | yeah... |
17:02:11 | seletz | http://www.eletztrick.de |
17:02:18 | KuEdE | :-) |
17:02:23 | seletz | search for cramfs howto |
17:02:42 | seletz | there should some links in the download section too |
17:03:20 | KuEdE | thx.... perhaps i forgot something whats clear to a "senior" arm developer |
17:03:20 | seletz | you have to be wary about the _decompressed_ ramdisk size. |
17:03:35 | seletz | KuEdE: is this a new port (i.e. new board/machine) |
17:03:35 | KuEdE | 32megs ram i got |
17:04:17 | KuEdE | its a sa1110 based thing... |
17:04:32 | seletz | KuEdE: well, doesnt depend on how much ram you got. initial ramdisks are _fixed_ _size_ /COMPILE TIME) |
17:05:22 | seletz | KuEdE: well, the question is: Is it a new kernel port (i.e. a new machine number and so on) or are you "just" using an existing kernel |
17:05:34 | KuEdE | new number |
17:05:45 | KuEdE | made a port of blob too... |
17:05:59 | KuEdE | its still not registered at arm.uk |
17:06:08 | seletz | KuEdE: which hw? Name? |
17:06:10 | KuEdE | i took a high fantsy number |
17:06:46 | KuEdE | yeah.. i know... but first i want to bring it working before sending diffs |
17:06:50 | seletz | KuEdE: anyway: make sure that in your fixup function your ramdisk size is set up correctly |
17:07:48 | seletz | KuEdE: IIRC you must parse ATAG tags by hand and setup the ramdisk. Check out arch/arm/assabet.c, search for .... |
17:07:51 | seletz | looking |
17:08:27 | KuEdE | in lart.c theres no fixup ... so why do I need a fixup for mine ? |
17:08:44 | seletz | KuEdE: setup_initrd() |
17:08:54 | KuEdE | sorry for bothering with dumbass questions... |
17:08:55 | seletz | KuEdE: lart is _minimal_ |
17:09:18 | seletz | KuEdE: my custom board is minimal too, but i do need a fixup routine because: |
17:09:28 | seletz | KuEdE: - i need some specific interupts |
17:09:39 | seletz | KuEdE: - i have HW registers to set up correctly |
17:09:48 | seletz | KuEdE: - configure the initial RD |
17:09:53 | KuEdE | i future ill need too... setup external DAC for Contrast.. Backlite |
17:09:53 | seletz | :) |
17:10:07 | seletz | KuEdE: look at system3.c |
17:10:12 | KuEdE | ok |
17:10:39 | seletz | KuEdE: thats my board, so expecht some bugs :) |
17:10:45 | seletz | s/expecht/expect/ |
17:10:56 | KuEdE | :-O |
17:11:04 | seletz | KuEdE: i have some contr/bright/ setting via PWM in there |
17:11:35 | seletz | KuEdE: i use a CSTN display, works quite well (what can you expect from CSTN, tho) |
17:12:45 | seletz | KuEdE: my apporach was: look at assabet. Copy it. Cut ugly stuff out. goto 1. Look at neponset code. merge them. |
17:12:54 | seletz | KuEdE: got a SA1111 too? |
17:12:57 | KuEdE | nope |
17:13:05 | seletz | KuEdE: lucky ... |
17:13:12 | KuEdE | but i got a usb host (isp1161) |
17:13:21 | seletz | KuEdE: SA1111 is crap IMHO |
17:13:31 | KuEdE | i heard in the mailinglists... |
17:13:38 | seletz | KuEdE: supported by linux already? |
17:13:48 | KuEdE | u mean 1161 ? |
17:13:53 | seletz | yup |
17:14:14 | KuEdE | theres a V0.8 of this driver.. (not merged in the official kernel tree) ... |
17:14:30 | seletz | well, ok |
17:14:34 | KuEdE | i read ..it wuz developed on a PC ISA card |
17:15:18 | KuEdE | but i heard from WinCE guys that the ISP1161 is very hard to bring to work |
17:15:24 | KuEdE | so... |
17:15:37 | KuEdE | sorry my friends... i gotta.. go.. |
17:15:43 | seletz | KuEdE: one last thing: be sure to send diffs as soon as possible, Russell King is _very_ good in finding bugs and ugly (read: wrong, not linux-like, Not The Way To Do It) code. |
17:15:54 | KuEdE | k... |
17:16:01 | seletz | KuEdE: It helped me a _lot_ |
17:16:25 | seletz | KuEdE: dont worry if the kernel boots not correctly |
17:16:33 | KuEdE | ill check in tomorrow..... ill try these thing u told me.. |
17:16:37 | KuEdE | But 1 question: |
17:16:41 | KuEdE | last one |
17:16:55 | seletz | KuEdE: just read the docs at armlinux website at last thrice :) |
17:17:02 | seletz | KuEdE: specially the patches section |
17:17:03 | KuEdE | u say lart is minimal.. but how to run linux when initrd fails.. ? |
17:17:27 | KuEdE | im a little bit confused.. |
17:19:02 | seletz | KuEdE: I dont know exactly wether or not you have to call the setup_initrd() directly or wether or not its setup inirectly by having correct kernel parameters (and BLOB set up your ATAG tags). |
17:19:25 | KuEdE | ahh.. |
17:19:26 | seletz | KuEdE: i have 3 lines in my fixup function and all is set :) |
17:19:57 | seletz | KuEdE: one thing: Are you sure that your kernel expects the ramdisk at the right physical ram address? |
17:20:15 | KuEdE | hmm.. another good question... |
17:20:17 | seletz | look at this: |
17:20:31 | | | static void __init fixup_system3(struct machine_desc *desc, |
17:20:31 | | | struct param_struct *params, char **cmdline, struct meminfo *mi) |
17:20:31 | | | { |
17:20:31 | | | DPRINTK( "%s\n", "START" ); |
17:20:32 | | | ROOT_DEV = MKDEV(RAMDISK_MAJOR,0); |
17:20:32 | | | setup_ramdisk( 1, 0, 0, 8192 ); |
17:20:36 | | | setup_initrd( 0xc0800000, 8*1024*1024 ); |
17:20:41 | seletz | } |
17:21:28 | seletz | the setup_initrd() call has the phys. ram addr of the initrd as a parameter |
17:21:45 | KuEdE | yep... ive seen this in your system3.c and in simpad.c |
17:21:53 | seletz | KuEdE: the fixup function runs when no VM is running IIRC |
17:22:07 | KuEdE | but now... :-((( sorry... i gotta go... my bud's waiting |
17:22:18 | KuEdE | k |
17:22:22 | KuEdE | ill save this s |
17:22:22 | seletz | KuEdE: the assabet.c does parse the ATAG |
17:22:33 | seletz | ok, i'll leave too |
17:22:35 | seletz | see ya |
17:22:47 | seletz | (join #kernelnewbies!!) |
17:26:52 | KuEdE | ill save this chat log......seems very informative ;-))) |
17:27:03 | KuEdE | cu guys and thx again |
19:26:02 | Russ | seletz_home: /dev/ram is the wrong root for a ramdisk iirc |
19:26:06 | Russ | that would be a ramfs |
19:26:49 | Russ | nm |
19:26:53 | Russ | Notes: You may have "/dev/ram" or "/dev/ramdisk" or both. |
22:47:11 | prpplague | howdy all |
22:49:43 | prpplague | BZFlag: seen my order for tux+jtag yet? |
22:51:50 | Russ|werk | prpplague: my board house screwed up on substitutions and forgot a part |
22:51:52 | Russ|werk | grrrr |
22:52:40 | prpplague | argh |
22:52:50 | prpplague | i hate it when that happenes |
22:54:26 | prpplague | Russ|werk: on my tcsx-1 board, i had laid out a set of jumpers to run the processor at 50, 66 and 75mhz, but the board house couldn't figure out what two resistors were for, so they droped them, so now it will only run at 75mhz |
22:55:15 | prpplague | Russ|werk: what kind of board is it? |
23:17:34 | Russ|werk | sa1100 |
23:17:55 | Russ|werk | I caught them before they placed all the zero ohms |
23:18:10 | Russ|werk | even though it clearly explained them in the bom |
23:39:29 | prpplague | good that you caught them |
23:48:17 | Russ|werk | they also could not find the transpower jacks I asked for, but said they found some sutible replacements |
23:48:45 | Russ|werk | I repeatadly checked with them that they are exact matches, including the turn ratio on the built in filters |
23:49:12 | Russ|werk | and on the board I now have straight through ethernet jacks with no filters |