9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Mathieu Lonjaret" <lejatorn@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] kernel panic with fresh sources
Date: Fri, 14 Mar 2008 01:38:29 +0100	[thread overview]
Message-ID: <16ff6b980803131738s657c6138nc75601b8c69b65cf@mail.gmail.com> (raw)
In-Reply-To: <ed127e709f1bf4f80593bc3a55c53ca5@quanstro.net>

On Wed, Mar 12, 2008 at 6:54 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> > Just for kicks, I have tried rebuilding another kernel with the fresh
>  > sources and this modified sdiahci.c but it fails with the errors
>  > attached in build.txt.
>
>  the build warnings are harmless.  it has to do with the fact that
>  u32int is considerd a uint by the print format checking while
>  ulong is considerd a ulong.
>
>  i'll take a look at the other stuff this p.m.
>
>  assuming that you have venti or kenfs on your machine, you
>  can do this
>         cp `{yesterday ahci.h sdiahci.c} . ;  mk clean ; mk 'CONF=pcf'

I have neither, but I had a backup of the sources. So yeah if I put those
 two back in the fresh sources and I build the kernel it goes fine. And then
that kernel boots fine as well. So could it be possible to have the changes
you made in that driver integrated to the distribution driver? Surely it'd be
cleaner this way rather than me keeping that copy. Besides, I guess it
could happen that one day it doesn't even build anymore after a pull
because it's not compatible anymore with the distribution, right?

Now another problem is the ethernet driver, I'm still getting a mac address
of 0000000000 with the distribution driver, which seems to be a problem
to reach the outside world depending on which LAN I'm connected to.
I guess I could also rebuild a kernel with my previous working driver (which
has the  hw address hardcoded in), but it also seems like something you
had fixed I think, and which could as well be added to the sources if
it works...

Mathieu.

--
GPG key on subkeys.pgp.net:

KeyID: | Fingerprint:
683DE5F3 | 4324 5818 39AA 9545 95C6 09AF B0A4 DFEA 683D E5F3


  reply	other threads:[~2008-03-14  0:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 17:48 Mathieu Lonjaret
2008-03-12 17:54 ` erik quanstrom
2008-03-14  0:38   ` Mathieu Lonjaret [this message]
2008-03-14  2:02     ` erik quanstrom
2008-03-14  2:35       ` erik quanstrom

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=16ff6b980803131738s657c6138nc75601b8c69b65cf@mail.gmail.com \
    --to=lejatorn@gmail.com \
    --cc=9fans@9fans.net \
    /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).