Re: kullervo

[Ingo Jürgensmann <ij@2013.bluespice.org>]

Am 24.01.2013 um 10:09 schrieb "Christian T. Steigies" <cts@debian.org>:

>> You should preferrably use either LVM or BTRFS snapshotsto speed up deinstallation of build-dep packages. I've chosen LVM because I'm unfamiliar with BTRFS, which is the most recommended option for handling chroots. 
> I am a bit familar with LVM. Can I use this on one partition only instead of
> the whole disk?

Sure. Just choose a partition for LVM and do a pvcreate /dev/sdXY, pvcreate & lvcreate. 

> So far I always used chroot in standard directories, but
> debootstrap failed in the end with this:
> W: Failure trying to run: chroot /data/chroot/buildd/sid mount -t proc proc /proc
> W: See /data/chroot/buildd/sid/debootstrap/debootstrap.log for details
> chroot: failed to run command 'mount': No such file or directory
> I dimly remember that I have to mount the proc directory on the host system,
> but this error message is not very helpful.

Yes, I had the same error, but I don't remember how I worked around it. :-/

>>> t is the standard kernel from debian-ports, but I think Thorsten has the
> same version on is webpage. I tried to build my own with the crosscompiler
> packages from Thorsten, but the build failed...
> [    0.000000] Linux version 3.2.0-4-amiga (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14+m68k.2) ) #1 Debian 3.2.35-2
> [    0.000000] Enabling workaround for errata I14 
> [    0.000000] Amiga hardware found: [A3000] VIDEO BLITTER AMBER_FF AUDIO FLOPPY A3000_SCSI KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA DENISE_HR AGNUS_HR_PAL MAGIC_REKICK ZORRO3 
> [    0.000000] Ignoring memory chunk at 0x7000000:0x1000000 before the first chunk
> [    0.000000] Fix your bootloader or use a memfile to make use of this area!
> [    0.000000] On node 0 totalpages: 28672
> [    0.000000] free_area_init_node: node 0, pgdat 00377d3c, node_mem_map 003ff000
> [    0.000000]   DMA zone: 252 pages used for memmap
> [    0.000000]   DMA zone: 0 pages reserved
> [    0.000000]   DMA zone: 28420 pages, LIFO batch:7
> [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
> [    0.000000] pcpu-alloc: [0] 0 
> [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 28420
> [    0.000000] Kernel command line: root=/dev/sda5 fb=false video=amifb:ntsc-lace BOOT_IMAGE=Work:linux/vmlinux-3.2.0-4-amiga
> How do I use a memfile to use this area, or where do I get a fixed
> bootloader?


Hmm, I guess kullervo has some additional onboard Fast-RAM (ZIP Chips). That can be up to 16 MB RAM. When you substract this amount from 128M - kernel space it would make up to 20 MB, resulting in roughly 107 MB usuable RAM. But why should amiboot or the kernel substract the onboard Fastmem from the accelerator card memory? 

There seems to be some information about amiboot on ftp://ftp.uni-erlangen.de/pub/Linux/680x0/v2.0/boot/amiboot-4.0.README including information about memfile. I guess Geert can better comment on amiboot questions.

-- 
Ciao...            //      Fon: 0381-2744150
      Ingo       \X/       http://blog.windfluechter.net


gpg pubkey:  http://www.juergensmann.de/ij_public_key.asc