From: cummij@rpi.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] THNX linux kernel
Date: Wed, 19 Sep 2007 11:38:36 -0400 [thread overview]
Message-ID: <7e7c42d4dac527cf66a872848b63715d@mail.rpi.edu> (raw)
In-Reply-To: <13426df10709042258g3d46c6a3nb74757e95e125002@mail.gmail.com>
hi ron-
> is now on sources, ...
>
> ls -l /n/sources/contrib/rminnich/lguest/2.6.23-rc5.tbz2
> --rw-rw-r-- M 204583 rminnich sys 236518451 Sep 4 23:52
> /n/sources/contrib/rminnich/lguest/2.6.23-rc5.tbz2
>
> It's a git tree, the branch is plan9c.
>
> ron
ok, i'm in a bit over my head here, so bear with me...
i've been playing with the lguest stuff you put on sources, and had some
success. the "canned" system works on my thinkpad t40. i've been trying
to add some modules to the linux kernel (such as ath_pci for wireless),
and my ignorance is manifesting itself.
i rebuilt the kernel from 2.6.23-rc5.tbz2, and installed it into /boot
on the usb stick. then i had to learn all about initrd (and initramfs)
and managed to get an initramfs file into /boot also. this all seems
to work and i boot into the new kernel, run "runme" and start syslog;
all without apparent error. the problem comes when i try to start lguest
with RUNLGUEST - i get the following:
lguest: Mmapping vmlinux seg 0 gave 0xffffffff not 0x100000: invalid argument
lguest: Mmapping vmlinux seg 1 gave 0xffffffff not 0x16e000: invalid argument
lguest: syscall 64 is not resolved!
lguest used greatest stack depth: 1580 bytes left
any idea what i should try next? do i need to recompile a new "lguest?"
thanks a alot,
john cummings
next prev parent reply other threads:[~2007-09-19 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 5:58 ron minnich
2007-09-19 15:38 ` cummij [this message]
2007-09-19 19:42 ` ron minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e7c42d4dac527cf66a872848b63715d@mail.rpi.edu \
--to=cummij@rpi.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).