* problems with putting an rtlinux kernel on a 686 on a PC104 board
@ 2002-12-03 23:38 Sonal Bhushan
2002-12-04 18:20 ` Feher Tamas
0 siblings, 1 reply; 3+ messages in thread
From: Sonal Bhushan @ 2002-12-03 23:38 UTC (permalink / raw)
To: linux-8086
hi,
I'm trying to install a linux kernel on a 686 on a PC 104 board (it is
intended to fly on a UAV). it has a 33MB Flash Disk (which is the only
hard disk on the computer). i compile the kernel on a host machine (which
has red hat 7.3 , with rt linux on top of it), and then make a bzdisk. so
far so good. when i try to boot the pc104 machine with the floppy though,
it comes up with the following error:
hda3: bad access: block=2, count=2
end_request: I/O error, dev 03:03 (hda), sector 2
EXT3-fs: unable to read superblock
hda3: bad access: block=2, count=2
end_request: I/O error, dev 03:03 (hda), sector 2
EXT3-fs: unable to read superblock
hda3: bad access: block=64, count=2
end_request: I/O error, dev 03:03 (hda), sector 64
EXT3-fs: unable to read superblock
isofs_read_super: bread failed, dev=03:03, iso_blknum=16, block=32
Kernel panic: VFS: Unable to mount root fs on 03:03
I tried looking up this error on mailing list archives, and it seems a
possible solution is to try passing "ide=reverse" as a kernel option. i'm
not sure when to do that though, because the pc104 is booting directly
from the bzdisk, and does not give me a chance to enter any command line
options.
i'm a newbie when it comes to compiling kernels, so any help would be
appreciated!
thanks,
sonal
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: problems with putting an rtlinux kernel on a 686 on a PC104 board
2002-12-03 23:38 problems with putting an rtlinux kernel on a 686 on a PC104 board Sonal Bhushan
@ 2002-12-04 18:20 ` Feher Tamas
2002-12-04 19:50 ` Dan Olson
0 siblings, 1 reply; 3+ messages in thread
From: Feher Tamas @ 2002-12-04 18:20 UTC (permalink / raw)
To: linux-8086; +Cc: Sonal Bhushan
Regards,
>I'm trying to install a linux kernel on a 686 on a PC 104 board (it is
>intended to fly on a UAV).
You should not post here:
-This list is for ELKS, the Linux for 8086/286 and other 16-bit cpu.
-We do not want to be suicide bombed by the guys, whom your sponsors want
to spy on by that UAV!
BTW, does the use of Linux for military purposes make the open source
development community legitimate targets? I indeed do think so. Commercial
sw licences specifically prohibite critical applications (nuclear
powerplants, life support and the like) which conveniently covers military
use, so they are not agreeing to that. Linus should better look out for
the bearded man with thin face...
Sincerely: Tamas Feher.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: problems with putting an rtlinux kernel on a 686 on a PC104 board
2002-12-04 18:20 ` Feher Tamas
@ 2002-12-04 19:50 ` Dan Olson
0 siblings, 0 replies; 3+ messages in thread
From: Dan Olson @ 2002-12-04 19:50 UTC (permalink / raw)
To: linux-8086
> BTW, does the use of Linux for military purposes make the open source
> development community legitimate targets? I indeed do think so. Commercial
> sw licences specifically prohibite critical applications (nuclear
> powerplants, life support and the like) which conveniently covers military
> use, so they are not agreeing to that. Linus should better look out for
> the bearded man with thin face...
You really think so? I would think the community would be a little too
far removed, like the auto maker who made the car that the suicide bomber
drove or something. It's an interesting point though.
Dan
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-12-04 19:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-03 23:38 problems with putting an rtlinux kernel on a 686 on a PC104 board Sonal Bhushan
2002-12-04 18:20 ` Feher Tamas
2002-12-04 19:50 ` Dan Olson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox