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 kno

daily CVS update output

2015-02-19 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/xcomp/mi P src/doc/TODO P src/external/mit/lua/dist/src/lapi.c P src/external/mit/lua/dist/src/ldebug.c P src/external/mit/lua/dist/src/llex.c P src/external/mit/lua/dist/src/llimits.h P src/external/mit/lua/dist/src/lstrlib.c P src/external/mit/lua/dist

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 da

Re: latest i386 radeondrmkms trials

2015-02-19 Thread Chavdar Ivanov
I am probably repeating others, but if you add Option "NoAccel" "True" to your Device section in xorg.conf it might work. I am in a similar point under -current. With NoAccel set to True it works fine. Without it I can run Xorg, which gives me black screen with a functional mouse, a small white r

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 wrote: > Tom Ivar Helbekkmo writes: > > > Chavdar Ivanov writes: > > > >> I've been getting the following: > >> [...] > >> #create sshramdisk/sshramdisk.fs >

Re: RPI build failure

2015-02-19 Thread Tom Ivar Helbekkmo
Tom Ivar Helbekkmo writes: > Chavdar Ivanov 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 >

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,

Re: RPI build failure

2015-02-19 Thread Tom Ivar Helbekkmo
Chavdar Ivanov 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 eff

RPI build failure

2015-02-19 Thread Chavdar Ivanov
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 -

Kernel debugging with qemu

2015-02-19 Thread Andreas Gustafsson
Hi all, I have recently updated and simplified the wiki instructions for setting up a qemu-based test environment for symbolic debugging of the NetBSD kernel: http://wiki.netbsd.org/kernel_debugging_with_qemu/ If there's a nagging kernel bug that you have long wanted to track down but have bee