All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Gifford <maillist@jg555.com>
To: sparclinux@vger.kernel.org
Subject: Re: More on the Sun Disk Label Issue
Date: Tue, 11 Apr 2006 06:42:31 +0000	[thread overview]
Message-ID: <443B4FD7.1010904@jg555.com> (raw)
In-Reply-To: <443AE0BA.8070706@jg555.com>

David S. Miller wrote:
> From: Jim Gifford <maillist@jg555.com>
> Date: Mon, 10 Apr 2006 23:12:07 -0700
>
>   
>> The bottom line somehow the writing of the header is not being done 
>> correctly. If it's fdisk or something related to the kernel, that's what 
>> I'm trying to determine.
>>     
>
> So let's start from the very beginning.
>
> If you have an existing system that works, and you run a gcc-4.1
> compiled kernel on it, does that work?
>   
It works, but if the paritition is was created by a fdisk compiled with 
GCC 4.1, it will give the checksum error during bootup. It just hangs, 
the kernel works fine, but if you are using udev, this error prevents 
the kernel from creating devices in /dev.

With everything I've discovered, and not my team, tonight. The problem 
is actually a util-linux issue and not a kernel issue. The issue is that 
util-linux doesn't generate a proper sun disk label, when it's built 
with GCC 4.1.

  parent reply	other threads:[~2006-04-11  6:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 22:48 More on the Sun Disk Label Issue Jim Gifford
2006-04-10 23:03 ` David S. Miller
2006-04-11  3:24 ` Jim Gifford
2006-04-11  6:03 ` David S. Miller
2006-04-11  6:12 ` Jim Gifford
2006-04-11  6:36 ` David S. Miller
2006-04-11  6:42 ` Jim Gifford [this message]
2006-04-11  6:52 ` David S. Miller
2006-04-15  0:47 ` Jim Gifford
2006-04-15  2:44 ` David S. Miller
2006-04-15  2:48 ` Jim Gifford
2006-04-15  2:56 ` David S. Miller

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=443B4FD7.1010904@jg555.com \
    --to=maillist@jg555.com \
    --cc=sparclinux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.