[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: [rtl] Embedding real time linux
Thanks for the reply Ken. It turns out that when I compressed the root
fs with dd, it grabs the entire partition (10Mb) not just the part
of the partition that has stuff on it. So it makes sense now. So
I redid the script to make a 4Mb filesystem on that partition and
viola! Real time linux booted off the single floppy.
Now I've just got to tweek the startup scripts so that all the inet
stuff starts up correctly.
Jim.
At 09:34 AM 5/4/98 -0500, Ken Teh wrote:
>
>
>On Sun, 3 May 1998, James Cassidy wrote:
>
>>
>>
>> I'm trying to create a boot disk with RTLinux to embed in an instrument.
>> But I'm having a problem that I'm hoping someone can help with.
>>
>> I've created a bash script that creates a minimum root file system
>> and compresses it. I then build a boot disk with the kernel and this
>> compressed root. I set the appropriate bits with rdev.
>>
>> The kernel boots, the ramdisk detects the compressed ram disk image and
>> starts loading it. Part way through, error messages start popping up:
>>
>> end_request: I/O error, dev 01:00, sector XXXXXXX
>>
>> After lots of these messages, starting somewhere around sector 9XXX and
>> continuing to sector 21310 (odd numbers only), everything stops.
>>
>> I'm assuming that 01:00 are the major, minor numbers. If so they match
>> the ram device. But haven't a clue why this error is occuring.
>>
>> Would anyone have any wisdom for me on this problem?
>>
>> Thanks,
>> Jim.
>>
>> --- [rtl] ---
>> For more information on Real-Time Linux see:
>> http://rtlinux.cs.nmt.edu/
>>
>
>
>Jim,
>
>If you put the kernel and root filesystem together on the same medium,
>then you have to provide an offset for the rootfilesystem. This info is
>patched into the kernel with rdev -r.
>
>Suppose your Linux kernel is under 400kB. You could then conveniently place
>your rootfilesystem at offset 400kB. You patch this information into the
>kernel image with
>
>rdev -r zImage 29072
>
>
>before compressing it onto the medium. Btw, 29072 is 0x7190. The '7'
>indicates a ramdisk, while '190' indicates an offset of 400kB.
>
>
>I presume you've done the above steps correctly. Then, the first thing that
>pops to mind is the size of your ramdisk. They are typically set at 4096kB
>which is a constant defined in your kernel. I suspect your root image is
>larger than that, judging from your error message. Sector 9xxx is about
>4MB.
>
>Good luck!
>
>
--- [rtl] ---
For more information on Real-Time Linux see:
http://rtlinux.cs.nmt.edu/