Michael Schmitz dixit:
>The kernel ate the rest?
[…]
>14 MB ST-RAM and 512 MB TT-RAM doesn't make 514 MB total either.
I think that’s normal anyway, both free/top and /proc/meminfo
never show the full amount of system memory in any system I know.
bye,
//mirabilos
--
„nein: BerliOS und Sourcef
Am 23.01.2013 um 23:54 schrieb "Christian T. Steigies" :
> kullervo is doing fine so far with the new kernel and current debian.
> I am setting up a new chroot, then I will have a look at sbuild and buildd.
> A few things seem to have changed. I hope I do not need to use LVM for the
> chroots?
Yo
Hi Christian,
> A few things seem to have changed. I hope I do not need to use LVM for the
> chroots? Also, why do I see only 107MB RAM, I thought it has 128MB?
>
> cts@kullervo:~>free -m
> total used free sharedbuffers cached
> Mem: 107105
Hi Thorsten,
> >Has anyone tried the builtin EtherNEC driver on the TT? My attempts to
>
> I think the problem is that it doesn’t *boot* on the TT when
> that driver is compiled in. Those kernels do boot on the Falcon.
So where does it stop (debug=ser2 on a TT IIRC)?
> Hm. Strictly speaking,
On Sun, Jan 20, 2013 at 07:51:49PM +, Thorsten Glaser wrote:
> >When the fschk is through I will have a look at the chroots,
> >maybe I can already fire up a buildd?
>
> Not with the old kernel, really not. And you probably should
> re-do the chroots (quicker than upgrading them).
cts@kullerv
Dixi quod…
>Michael Schmitz dixit:
>
>>Has anyone tried the builtin EtherNEC driver on the TT? My attempts to
>
>I think the problem is that it doesn’t *boot* on the TT when
>that driver is compiled in. Those kernels do boot on the Falcon.
>
>Hm. Strictly speaking, to verify, we probably need to b
Michael Schmitz dixit:
>Has anyone tried the builtin EtherNEC driver on the TT? My attempts to
I think the problem is that it doesn’t *boot* on the TT when
that driver is compiled in. Those kernels do boot on the Falcon.
Hm. Strictly speaking, to verify, we probably need to build a
kernel with*o
Hi Thorsten,
> >Agreed - but you're using kernels without support from Debian already. Plus
>
> Only temporarily. And putting together an initrd is a PITA.
Can't speak to the initrd issue - never tried to build cross-initrds.
On 'temporarily' - there'a at least one commit in my network related
Hi,
I’ve just noticed a problem:
Wed, 23 Jan 2013 20:31:38 +
http://debian.advalem.net/debian-ports/dists/unstable/
Index of /debian-ports/dists/unstable
NameLast modified Size Description
Parent Directory-
Contents-all.gz 23-Ja
Michael Schmitz dixit:
>> But initrds without support from the distros suck, too…
>
>Agreed - but you're using kernels without support from Debian already. Plus
Only temporarily. And putting together an initrd is a PITA.
bye,
//mirabilos
--
„nein: BerliOS und Sourceforge sind Plattformen für Pr
10 matches
Mail list logo