public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	opensuse factory list <opensuse-factory@opensuse.org>
Subject: Re: 2.6.37-rc3-git installed modules zero bytes long
Date: Wed, 01 Dec 2010 14:48:46 +0000	[thread overview]
Message-ID: <4CF6604E.8080109@blueyonder.co.uk> (raw)
In-Reply-To: <20101201060704.GD5210@cr0.nay.redhat.com>

On 01/12/10 06:07, Américo Wang wrote:
>
> (Please don't drop lkml, and I am not a subscriber of the opensuse list.)
>
OK. I built 2.6.37-rc3-git7-smp on the second box, checked the modules 
were OK. Rebooted and modules were still OK, built the NVidia module, 
rebooted and it's OK.
I didn't build VirtualBox-3.2-3.2.10_66523 modules this time to 
eliminate that as the problem previously appeared after I had rebuilt 
VBox as the last action before rebooting straight into X.

I'm now building 2.6.37-rc4-git1 and I shall repeat that sequence again.
Regards
Sid.

> On Tue, Nov 30, 2010 at 05:24:52PM +0000, Sid Boyce wrote:
>> On 30/11/10 15:48, Américo Wang wrote:
>>> On Tue, Nov 30, 2010 at 02:59:55PM +0000, Sid Boyce wrote:
>>>> openSUSE 11.3 on one box and openSUSE 11.4 Milestone 4 on the other.
>>>> I have a message that says the built modules not found. When I check e.g
>>>> /lib/modules/2.7.37-rc3-git7-smp, most modules are zero bytes long.
>>>> I have to "make modules_install" and use modprobe on each.
>>>> To get the network up on the 11.3 box "modprobe r6189" then "rcnetwork
>>>> restart", "modprobe rtl8187", "/etc/init.d/network-remotefs start",
>>>> etc., etc.
>>>
>>> Confused, shouldn't we always run 'make modules_install'?
>>> What did you do before that?
>>>
>>
>> As usual a script that does the following and never had problems
>> before. It says it's installed the modules, but a check shows they
>> are all zero bytes long.
>> -------------------------------------------------------------------
>> #!/bin/sh
>> make -j 4 clean&&  make headers_install&&  make -j 4&&  make -j 4
>> modules_install
>> -------------------------------------------------------------------
>
> Hmm, nothing is wrong with this script.
>
> Sounds like a regression, but I don't recall we have any 'module_install'
> changes recently.
>
> What does 'make V=2 modules_install' output?
>
> Thanks.
>


-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks


  reply	other threads:[~2010-12-01 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 14:59 2.6.37-rc3-git installed modules zero bytes long Sid Boyce
2010-11-30 15:48 ` Américo Wang
     [not found]   ` <4CF53364.1090807@blueyonder.co.uk>
2010-12-01  6:07     ` Américo Wang
2010-12-01 14:48       ` Sid Boyce [this message]
2011-02-26  1:41 ` Sid Boyce
2011-02-26  3:16   ` Sid Boyce
2011-03-01 17:54     ` 2.6.37-rc3-git installed modules zero bytes long - only on root xfs Sid Boyce

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=4CF6604E.8080109@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensuse-factory@opensuse.org \
    --cc=xiyou.wangcong@gmail.com \
    /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