Re: RPI build failure

2015-02-19 Thread Tom Ivar Helbekkmo
Chavdar Ivanov ci4...@gmail.com writes:

 I've been getting the following:
 [...]
 #create  sshramdisk/sshramdisk.fs
 nbmakefs: `work' size of 14200832 is larger than the maxsize of 13631488.

The size was recently updated, but you have to clean out the RPI_INSTALL
kernel build directory for it to take effect.

-tih
-- 
Popularity is the hallmark of mediocrity.  --Niles Crane, Frasier


Re: RPI build failure

2015-02-19 Thread Nick Hudson

On 02/17/15 08:31, Chavdar Ivanov wrote:

Hi,

I've been getting the following:


Calculated size of `ramdisk.fs.tmp': 3145728 bytes, 621 inodes
Extent size set to 4096
ramdisk.fs.tmp: 3.0MB (6144 sectors) block size 4096, fragment size 512
 using 1 cylinder groups of 3.00MB, 768 blks, 704 inodes.
super-block backups (for fsck -b #) at:
  32,
Populating `ramdisk.fs.tmp'
Image `ramdisk.fs.tmp' complete
--- all-sshramdisk ---
[ work.built = work.built -a -f sshramdisk.fs -a ! sshramdisk.fs -ot
work.built ]  || {  echo '#  '  create  sshramdisk/sshramdisk.fs;  rm -f
sshramdisk.fs sshramdisk.fs.tmp;
  /home/sysbuild/Sysbuild/evbarm/tools/bin/nbmakefs -t ffs -B le -s 13m -F
work.spec  -N /home/sysbuild/src/etc -o bsize=4096,fsize=512  -o
optimization=space,minfree=0  -f 15 sshramdisk.fs.tmp work   mv -f
sshramdisk.fs.tmp sshramdisk.fs;  }
#create  sshramdisk/sshramdisk.fs
nbmakefs: `work' size of 14200832 is larger than the maxsize of 13631488.
*** [sshramdisk.fs] Error code 1
nbmake[5]: stopped in
/home/sysbuild/src/distrib/evbarm/instkernel/sshramdisk
1 error
nbmake[5]: stopped in
/home/sysbuild/src/distrib/evbarm/instkernel/sshramdisk
*** [all-sshramdisk] Error code 2
nbmake[4]: stopped in /home/sysbuild/src/distrib/evbarm/instkernel
1 error
nbmake[4]: stopped in /home/sysbuild/src/distrib/evbarm/instkernel
*** [all-instkernel] Error code 2
nbmake[3]: stopped in /home/sysbuild/src/distrib/evbarm
1 error
nbmake[3]: stopped in /home/sysbuild/src/distrib/evbarm
*** [all-evbarm] Error code 2


when trying to build a live-image for RPI on -current.


I think I fixed that already and

http://releng.netbsd.org/builds/HEAD/201502190220Z/

has a complete build


Chavdar Ivanov



Nick


Re: RPI build failure

2015-02-19 Thread Michael van Elst
ci4...@gmail.com (Chavdar Ivanov) writes:

I am getting a crash, though; this RPI is connected to a 27 Dell monitor's
USB hub, the k/b and mouse go there. After a message that they have been
detached (perhaps power saving on the monitor - it happens when left
overnight) I receive:

I don't know about the Dell monitor, but the LG monitor here only
has an _unpowered_ hub. Whatever power it and the connected mouse
and keyboard need, has to be provided by the RPI and its power supply.

Greetings,
Michael


-- 
-- 
Michael van Elst
Internet: mlel...@serpens.de
A potential Snark may lurk in every tree.


Re: RPI build failure

2015-02-19 Thread Chavdar Ivanov
I am getting a crash, though; this RPI is connected to a 27 Dell monitor's
USB hub, the k/b and mouse go there. After a message that they have been
detached (perhaps power saving on the monitor - it happens when left
overnight) I receive:

uvm.fault(0xc051b078,da3c8000,1) - e
Fatal kernel mode data abort: 'Translation Fault (S)'
trapframe: 0xcbb39e70
FSR=0005, FAR=da3c9dff, spsr=2013
 registers...
Stopped in pid 0.21 (system) at netbsd:usbd_transfer+0x600= ldr r3, [r3]

I'll leave it for a while without the USB hub to see if this is indeed the
reason (this is not the first time it has happened - prior to 7.99.5 it was
running aroung 6.99.49 vintage and was crashing in similar manner, but I
never took any notice).

Chavdar


On Thu Feb 19 2015 at 9:18:25 AM Chavdar Ivanov ci4...@gmail.com wrote:

 Thanks, I repeated the build yesterday and it completed fine.


 Chavdar Ivanov


 On Thu Feb 19 2015 at 9:16:46 AM Tom Ivar Helbekkmo t...@hamartun.priv.no
 wrote:

 Tom Ivar Helbekkmo t...@hamartun.priv.no writes:

  Chavdar Ivanov ci4...@gmail.com writes:
 
  I've been getting the following:
  [...]
  #create  sshramdisk/sshramdisk.fs
  nbmakefs: `work' size of 14200832 is larger than the maxsize of
 13631488.
 
  The size was recently updated, but you have to clean out the RPI_INSTALL
  kernel build directory for it to take effect.

 Ah, wait, you don't even have the update.  You need revision 1.7 of each
 of the files src/sys/arch/evbarm/conf/RPI_INSTALL and
 src/distrib/evbarm/instkernel/sshramdisk/Makefile, and *then* you need
 to clean out the RPI_INSTALL kernel build directory.

 -tih
 --
 Popularity is the hallmark of mediocrity.  --Niles Crane, Frasier




Re: RPI build failure

2015-02-19 Thread Chavdar Ivanov
Thanks, I repeated the build yesterday and it completed fine.

Chavdar Ivanov


On Thu Feb 19 2015 at 9:16:46 AM Tom Ivar Helbekkmo t...@hamartun.priv.no
wrote:

 Tom Ivar Helbekkmo t...@hamartun.priv.no writes:

  Chavdar Ivanov ci4...@gmail.com writes:
 
  I've been getting the following:
  [...]
  #create  sshramdisk/sshramdisk.fs
  nbmakefs: `work' size of 14200832 is larger than the maxsize of
 13631488.
 
  The size was recently updated, but you have to clean out the RPI_INSTALL
  kernel build directory for it to take effect.

 Ah, wait, you don't even have the update.  You need revision 1.7 of each
 of the files src/sys/arch/evbarm/conf/RPI_INSTALL and
 src/distrib/evbarm/instkernel/sshramdisk/Makefile, and *then* you need
 to clean out the RPI_INSTALL kernel build directory.

 -tih
 --
 Popularity is the hallmark of mediocrity.  --Niles Crane, Frasier