Re: PC104 board boot off compact flash, load initrd, and execute out of ramdisk
From: Joseph Chiu (nospam.joseph_at_candlelighttechnology.com)
Date: 06/03/05
- Previous message: Sudhakar Velusamy: "Serial Port Internal Loopback in 2.6 Kernel"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 3 Jun 2005 02:57:15 -0700
/dev/hdc as a kernel argument is for pointing the kernel to the correct
driver; your filesystem image itself must contain the necessary block
special file to point to the correct driver...
"Mark" <fj40rockcrawler@gmail.com> wrote in message
news:1116448149.165747.187980@f14g2000cwb.googlegroups.com...
>I think it can boot off a USB device although we are not using any USB
> stuff and therefore did not purchase the little pigtails that would go
> onto this board.
>
> The board is made by Kontron, it was in the neighborhood of $300 with
> 256meg of SO-DIMM (std laptop memory) installed in the one memory slot,
> I didn't decide on this model, but this is what was purchased.
>
> Here is the URL to the board:
> http://www.kontron.com/products/pdproductdetail.cfm?keyProduct=31751&kps=1040&kpc=135
>
> It's a cute little board, and pretty powerful, basically a full desktop
> system, minus the drives in a 3.5"x3.5" computer, also no fan is needed
> for the CPU and the whole board runs off 5v.
>
> With the help of some major linux gurus I have almost gotten this thing
> to reliably boot, it is very odd how it works and extremely
> frustrating, a big problem has been with bootloaders. They seem
> inheriently flawed to me, when I'm in a running system (off the HD) the
> CF card shows up as /dev/hdc, however with a newer kernel a buddy gave
> me it *should* showup as /dev/discs/disc0/disc, but it doesn't, well it
> kinda does, to get it to boot you HAVE to pass "root=/dev/hdc1 rw" to
> the kernel, even on the newer kernel that when fully booted does not
> have /dev/hdc in it's /dev directory, then it apparently sees the
> partiion as /dev/discs/disc0/part1 which is should...it is very odd and
> there is something fishy going on between the bios and the bootloader
> and kernel...it's been a total mess to be honest with you and I would
> never do this again without some more help. Every writeup I have found
> that gave nice clear instructions on how to do this would not work,
> simple as that, enter this command, the root drive should be here,
> etc...didn't happen that way. Cute board but not a fun project...
>
- Previous message: Sudhakar Velusamy: "Serial Port Internal Loopback in 2.6 Kernel"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
