| Age | Commit message (Collapse) | Author |
|---|
|
Newer modprobe will only look at .conf files.
(closes: #541864)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
fb should be loaded after initramfs by init to have a beautiful
userland. allows faster boot not to try parsing crazy things
with only posix sh at our hands.
this will need a README.DEBIAN section as noone is now currently
loading fbcon.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
thrive for a smaller initramfs,
were loading of the modules is so fast that acpi should be loaeded
by udev after init(8) call.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
The i915 DRM module doubles as a framebuffer of sorts, at least in kernel
mode-setting setups; like its cousins intelfb and i810fb, it effectively
requires intel-agp despite not actually using any of its symbols. As
such, could you please arrange for scripts/init-top/framebuffer to give
it the same treatment, per the following patch?:
(closes: #533258)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
make it more concise:
* use POSIX ${parameter:+word}
* replace *[/]*) by just */*)
* test exit code of command -v rather then running test -x on it
while we are at it fix another command -v usage in scripts/functions.
Reviewed-by: Colin Watson <cjwatson@ubuntu.com>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
the regex was overly severe not allowing dots althoug they are
useful as word ending.
based on a patch in launchpad, that didn't get all occurences right,
but was a good start.
(LP: #305837)
|
|
fix wrong merge of e184c8c2a9ad4520cf0cf4536301c6ae6206e911
scripts/init-top/framebuffer: 84: Syntax error: ")" unexpected (expecting ";;")
|
|
After further experimentation, I discovered additional problems that my
first patch did not address, namely that
1) Some FB drivers need the AGP subsystem up and running before they
are loaded and
2) intelfb needs intel-agp.ko, but does not have a dependency on it.
intelfb does not actually *work* on my testsystem after this (it
crashes), but unlike with plain initramfs-tools, it loads (and prints
something useful if loaded with the probeonly option). I'll try to find
out why it fails to work tomorrow; it's probably an unrelated issue.
[ make the patch applyable, probably whitespace damaged, fix comments,
no need to pass -q to modprobe that is set globaly -maks ]
(closes: #416063, #455876)
Signed-off-by: maximilian attems <maks@debian.org>
|
|
DO NOT USE -Qb for framebuffer.
Blank ttys when using vesafb (vga=xxx) LP: #129910
[ s/-Q/-q/ for modprobe options -maks ]
|
|
while at it cleanup the variable name that came due to legacy
naming nfsopts in a very early initramfs-tools release.
"The local-top/iscsi initramfs integration script uses the
configure_networking function, which depends on the IPOPTS environmental
variable set by the init script. However, this variable is not
available, because it's not exported from init, and local-top/iscsi is
not sourced but executed. Thus static IP configuration on the kernel
command line is not communicated to the script."
(closes: #516746)
Reported-by: Ferenc Wagner <wferi@niif.hu>
|
|
do the same dance here, same code, just slightly renamed variables.
|
|
The attached patch is needed for booting with root=mtd0.
Basically, the init scripts assume the root device should have a special
device file somewhere, and if not will wait for it to appear. This patch
changes it so that it only waits for a device file to appear if $ROOT starts
with "/dev". In the case of things like ROOT=LABEL=foo, the init scripts
will translate that to a device. With ROOT=mtd0, the init scripts will not
check for a device, and will successfully mount the root filesystem.
Signed-off-by: Andres Salomon <dilinger@debian.org>
|
|
(closes: #514997)
Reported-by: Michael Prokop <mika@grml.org>
|
|
since Lenny lvm2 ships it's own hooks scripts, no need to dup.
|
|
in 0.92m, the timeout for ipconfig in scripts/functions was set to 60
seconds. This broke our iscsi-rootfs setups.
It took me a while to debug this, but it seems that 60 seconds is not
enough for switches which have spanning-tree enabled, they need some
more time before they take up a port, in our case between 62 and 65
seconds.
(closes: #511085)
|
|
d-i uses to pass it with the value 1
Reported-by: Frans Pop <fjp@debian.org>
|
|
Fix buglet in parse_numeric where *:* would match mtd:root. We only
want to match numbers. This fixes redboot partition support.
Signed-off-by: Andres Salomon <dilinger@debian.org>
|
|
|
|
udev isn't started at this point and therefore can't create framebuffer
devices. This causes usplash not to run on PS3.
set sane permissions will making the char files.
This reverts commit 0aec8b0c22b7622841c4ab7a3b492b4d2657456f.
|
|
Uvesafb framebuffer driver needs v86d userspace program
but when fb driver is modprobed at init-top stage of initrd,
/dev/zero and /dev/mem are missing because udev have not
been run yet.
|
|
thanks martin f krafft <madduck@debian.org>
closes: #502058
|
|
|
|
rather than waiting forever (LP: #182940).
|
|
On OLPC machines, root is a nand device that is mounted as mtd0 (it is
neither a block device nor a char device). The arguments passed to the
kernel are "ro root=mtd0 rootfstype=jffs2".
Unfortunately, attempting to use an initrd based upon initramfs-tools
on such a machine results in a kernel panic and a syntax error.
Begin: Mounting root file system ... /init: line 172: syntax error:
0xmtd0
The probably appears to be in parse_numeric(); the init scripts
assume that normal devices are always prefixed with /, and root=
strings that aren't are raw device numbers (prefixing them with
0x). I'm not sure if there are other devices similar to mtd that
don't begin with a /.
How about something like the following patch? It's not foolproof,
but it at least ignores things that can't possibly be hex strings.
fixes partially #497133
|
|
after lenny the symlink of udev is meant to be gone,
support partial upgrades from lenny.
|
|
Please make log_begin_msg not emit a trailing newline - this makes the non-
"quiet" output cleaner and results in half as many lines being emitted. For
example:
Begin: Finding root filesytem ...
Done.
Becomes:
Begin: Finding root filesytem ... done.
Patch attached - it also adds a space and alters the case of "done" for
symmetry. This would be especially useful in Debian Live where we show a
large number of these messages by default.
(closes: #494257)
|
|
|
|
ubuntu sync
|
|
thanks to Frans Pop <elendil@planet.nl> for report,
idea stolen from Ubuntu, adapted their boot script
same boot param.
closes: #485786
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Debian users were pasting that without getting the real trouble,
thanks for the better rephrasing.
|
|
add small comment on top, what for we need it.
Signed-off-by: maximilian attems <maks@debian.org>
|
|
udev may be busy creating links for the root device by the time
mountroot is called. udevsettle makes sure these are processed. I thus
call udevsettle with a timeout of 10 seconds after the $BOOT-top
scripts have run and before the ROOTDELAY hack kicks in.
I thought about doing this with a local-top script instead, but there is
no way to ensure that it'll run last; cryptsetup uses a hack to make
sure it runs last, if we also use the same hack, there'll be
a dependency loop.
Signed-off-by: martin f. krafft <madduck@debian.org>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
log_begin_msg already puts ... at the end of the stuff it prints, so no
need to have it in there explicitly.
Signed-off-by: martin f. krafft <madduck@debian.org>
Signed-off-by: maximilian attems <maks@debian.org>
|
|
Parse cmdline for resume_offset, export it and pass it to
the klibc resume binary.
Based on a patch by Alan Jenkins <alan-jenkins@tuffmail.co.uk>.
Bonus small codingstyle clean up of local-premount/resume.
|
|
found on testing that configure_networking() shouldn't make
assumption that ${DEVICE} is really already set.
this still allows to bail out if device is passed and set.
|
|
udev takes care to load the relevant modules.
also PS3PF never had landed in debian thus pretty useless
to take care of it just nuke it and be happy that
udev loading is fixed since 2.6.23-rc1.
|
|
based on a patch by Luke Yelavich <luke.yelavich@canonical.com>.
|
|
IPOPTS can be assumed to get passed :::::: and thus configure
any possible interface. we have thus also to source the relevant
ipconfig output :)
based on a patch by Michal Sojka <sojkam1@fel.cvut.cz>:
"If I want several computers to boot from the same ramdisk (with NFS
root) and some computers have multiple network interfaces, the DEVICE
variable can't be set to a specific value (e.g. eth0). Ipconfig from
klibc supports a mode, where DHCP request is sent to all interfaces
and the one receiving the first DHCP offer is used. This perfectly
suits my needs, but it can't be used with initramfs scripts because
the interface name in not known in advance and the DEVICE variable is
set to something like ::::::."
|
|
No need to call chmod later on, now that klibc mknod can set permissions.
|
|
udev creates tty devices too, in the case of not using udev,
we need to ship more anyway, so no need to worry about that right now.
|
|
nuke fb device mknod creation as udev creates the fb device nodes.
suggested by waldi. positive test on qemu with usplash.
let's see if we get a bad interaction with usplash and vga=XXX boots.
|
|
This patch is part of three patches (initramfs-tools, cryptsetup,
dropbear) which enable mkinitramfs to create initramfs that provide the
ability to log in and unlock a cryptroot during the boot process from
remote via ssh.
Calling configure_networking from /scripts/functions might appear more
than once, so just try if it hasn't been done/wasn't successful yet.
Check that by testing for existence of /tmp/net-$DEVICE.conf which is
created by ipconfig.
|
|
|
|
s/fbnum/fbno/
|
|
ltsp in ubuntu started using NBD+unionfs+squashfs instead of NFS, and
debian-live uses has a network boot methods using cifs in addition to a
different way of using NFS (i think it also uses unionfs and maybe
squashfs, not just a plain NFS/cifs mount)...
so splitting out the networking related code into a separate function
would move towards not having forked code for all of these different
network boot methods. at least, that's my hope.
|
|
you can only have up to 32 fb devices going from fb0 to fb31.
|
|
|
|
|
|
sleep can take arg 0
|
|
* add the error messages
* fix double call to set_initlist
* skip empty dirs at start
|
