Michal Suchanek wrote:
How would I specify the nodma then?
If it is only read from options present in the ramdisk I cannot boot
on devices with broken DMA (intel BX/LX/VX chipsets with certain
CD-ROMs for one).
maximilian attems wrote:
as a boot arg for example, kernel parses it.
and
On Sat, 16 Aug 2008, Chris Lamb wrote:
maximilian attems wrote:
# Automatically generated email from bts, devscripts version 2.10.7
reassign 442333 live-initramfs
Hm, really? According to my tests, the ide modules are already loaded
before mountroot in live-initramfs is called.
yes
On 09/09/2008, maximilian attems [EMAIL PROTECTED] wrote:
On Sat, 16 Aug 2008, Chris Lamb wrote:
maximilian attems wrote:
# Automatically generated email from bts, devscripts version 2.10.7
reassign 442333 live-initramfs
Hm, really? According to my tests, the ide modules are
On Tue, Sep 09, 2008 at 01:35:53PM +0200, Michal Suchanek wrote:
How would I specify the nodma then?
If it is only read from options present in the ramdisk I cannot boot
on devices with broken DMA (intel BX/LX/VX chipsets with certain
CD-ROMs for one).
as a boot arg for example, kernel
maximilian attems wrote:
# Automatically generated email from bts, devscripts version 2.10.7
reassign 442333 live-initramfs
Hm, really? According to my tests, the ide modules are already loaded
before mountroot in live-initramfs is called.
Regards,
--
Chris Lamb, UK
Package: initramfs-tools
Version: 0.90a
Some kernel command line parameter, like ide=nodma, for example, are
ignored by the ramdisk's script.
When booting from Compact flas, for example, the ide=nodma on the kernel
command line is useless, since ide modules loaded from ramdisk scripts
ignores
6 matches
Mail list logo
