Danny Milosavljevic skribis:
> On Tue, 27 Feb 2018 20:32:49 +0100
> Danny Milosavljevic wrote:
>
>> > > P.S. How come glibc is in the initrd? Shouldn't guile have statically
>> > > linked it?
>> > > glibc is like 5 kiB. In that case saving 800 kiB is not really
>> > > worth it...
>>
On Tue, 27 Feb 2018 20:32:49 +0100
Danny Milosavljevic wrote:
> > > P.S. How come glibc is in the initrd? Shouldn't guile have statically
> > > linked it?
> > > glibc is like 5 kiB. In that case saving 800 kiB is not really worth
> > > it...
> >
> > One of the packages that ends up i
> > P.S. How come glibc is in the initrd? Shouldn't guile have statically
> > linked it?
> > glibc is like 5 kiB. In that case saving 800 kiB is not really worth
> > it...
>
> One of the packages that ends up in the initrd must be dynamically
> linked. You need to find out which one it
Hello,
ng0 skribis:
> Ludovic Courtès transcribed 0.8K bytes:
>> Hello,
>>
>> Mark H Weaver skribis:
>>
>> > To make this easier, I think the right approach is to include many
>> > modules like these to our installation image initrd, and then to
>> > automatically detect which modules are nee
Danny Milosavljevic skribis:
> So what we would need next is something like modprobe written in guile.
>
> I think that ./gnu/build/linux-modules.scm load-linux-module* already does
> that.
>
> The only part missing is to replace %modprobe-wrapper by a guile script
> which imports ./gnu/build/li
Hi Ludo,
On Mon, 26 Feb 2018 16:20:08 +0100
l...@gnu.org (Ludovic Courtès) wrote:
> I suppose the bits I’ve promised to detect necessary modules based on
> modules.alias and /sys should be useful here?
Definitely!
I've posted a working patch series (v3, "Load Linux module only when supported
ha
Hello,
Danny Milosavljevic skribis:
> I've got it to work now. I've got a very minimal static kmod into the initrd
> and
> that's now only loading modules for which supported hardware is present.
>
> On the other hand, the initrd got 800 kiB larger - I'm not sure why modprobe
> is so big... hm
Hi Andreas,
On Sat, 24 Feb 2018 00:02:39 +0100
Andreas Enge wrote:
> On Fri, Feb 23, 2018 at 03:28:55PM +0100, Danny Milosavljevic wrote:
> > No, wait, according to
> > https://unix.stackexchange.com/questions/43699/debian-does-not-detect-serial-pci-card-after-reboot/43723#43723
> > ,
> > the
Ludovic Courtès transcribed 0.8K bytes:
> Hello,
>
> Mark H Weaver skribis:
>
> > To make this easier, I think the right approach is to include many
> > modules like these to our installation image initrd, and then to
> > automatically detect which modules are needed for booting. A future
> > e
Hello,
On Fri, Feb 23, 2018 at 03:28:55PM +0100, Danny Milosavljevic wrote:
> No, wait, according to
> https://unix.stackexchange.com/questions/43699/debian-does-not-detect-serial-pci-card-after-reboot/43723#43723
> ,
> the kernel should be doing that even without udev. Are we sure we need to
Hello,
Mark H Weaver skribis:
> To make this easier, I think the right approach is to include many
> modules like these to our installation image initrd, and then to
> automatically detect which modules are needed for booting. A future
> easy installer could automatically add those modules to t
No, wait, according to
https://unix.stackexchange.com/questions/43699/debian-does-not-detect-serial-pci-card-after-reboot/43723#43723
,
the kernel should be doing that even without udev. Are we sure we need to
manually modprobe the stuff in gnu/build/linux-boot.scm in
the first place? I think
Hi Mark,
On Thu, 22 Feb 2018 17:01:11 -0500
Mark H Weaver wrote:
> Every extra loaded kernel module means more RAM usage in the kernel, a
> larger initrd image that must be loaded by possibly slow bootloaders,
> and code complexity in the running kernel, leading to a greater attack
> surface for
Hi Andreas,
Andreas Enge writes:
> recently I had an unpleasant experience in installing GuixSD: After booting
> with the USB key and following the installation instructions, then rebooting
> into the installed system, the "/" file system was not found: neither using
> file system labels, nor de
Hello Danny,
On Thu, Feb 22, 2018 at 10:34:03PM +0100, Danny Milosavljevic wrote:
> When you booted from the USB key the system DIDN'T need mptsas to find
> ITS root filesystem. So it booted fine and in the end of it all you had
> a working GNU Linux, with udev.
>
> Then udev saw the hard disk a
Hi,
On Thu, 22 Feb 2018 22:29:25 +0100
Jan Nieuwenhuizen wrote:
> (initrd (lambda (file-systems . rest)
> (apply base-initrd file-systems
> #:extra-modules '("pata_via" "pata_acpi" "sata_via")
> rest)))
Hmm, see gnu/system/linux-initrd
Hi Andreas,
On Thu, 22 Feb 2018 22:17:07 +0100
Andreas Enge wrote:
> The problem turned out to be that the disk of the machine needed special
> kernel modules, and adding
> (initrd (lambda (file-systems . rest)
> (apply base-initrd file-systems
>#:extra-modules
Andreas Enge writes:
> The problem turned out to be that the disk of the machine needed special
> kernel modules, and adding
> (initrd (lambda (file-systems . rest)
> (apply base-initrd file-systems
>#:extra-modules '("mptbase" "mptsas" "mptscsih")
>
Hello,
recently I had an unpleasant experience in installing GuixSD: After booting
with the USB key and following the installation instructions, then rebooting
into the installed system, the "/" file system was not found: neither using
file system labels, nor device nodes.
The problem turned out
19 matches
Mail list logo
