search for: nomce

...n "syslinux -fs /dev/sda3" Is it possible to to boot like tihs? Am I missing something? The contents of syslinux.cfg follows ------------------------------------------------------ DEFAULT linux APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt.gz nomce loglevel=0 quiet BOOT_IMAGE=knoppix TIMEOUT 300 PROMPT 1 DISPLAY boot.msg F1 boot.msg F2 f2 F3 f3 LABEL knoppix KERNEL linux APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt.gz nomce loglevel=0 quiet BOOT_IMAGE=knoppix LABEL expert KERNEL linux APPEND ramdisk_s...

...s up wrong. I saw that there is a debug version of isolinux but could not find something similar for syslinux. Does such a thing exist? I have attached my syslinux.conf. * * * * * * * * * * DEFAULT linux24 APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt24.gz nomce quiet BOOT_IMAGE=knoppix TIMEOUT 300 PROMPT 1 DISPLAY boot.msg F1 boot.msg F2 f2 F3 f3 LABEL knoppix KERNEL linux24 APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt24.gz nomce quiet BOOT_IMAGE=knoppix LABEL memtest KERNEL memtest APPEND initrd= LABEL knoppix-tx...

Hi > Maybe I'm missing something, but this has been working flawlessly for > us in Tails so far. What exactly fails? Are you using EFI Handover Protocol? It might explain the difference Thomas

...-stick. Which parameters in syslinux.cfg I must change to start Ubuntu-Linux? There are the following files in Ubuntu-casper: initrd.gz vmlinuz The syslinux.cfg at bootfloppy begins with: DEFAULT linux24 APPEND ramdisk_size=100000 init=/etc/init lang=de apm=power-off vga=791 initrd=minirt24.gz nomce noapic quiet BOOT_IMAGE=knoppix frugal TIMEOUT 300 PROMPT 1 DISPLAY boot.msg F1 boot.msg F2 f2 F3 f3 LABEL dsl KERNEL linux24 APPEND ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt24.gz nomce noapic quiet BOOT_IMAGE=knoppix frugal Regards, Svgt -- Computer Bild Ta...

...efailsafe > menu label Live (failsafe) > kernel /live/vmlinuz2 > append initrd=/live/initrd2.img boot=live config live-media=removable apparmor=1 security=apparmor nopersistent noprompt timezone=Etc/UTC block.events_dfl_poll_msecs=1000 splash noautologin module=Tails noapic noapm nodma nomce nolapic nomodeset nosmp vga=normal > > Cheers, > -- > intrigeri > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >

...one_complete ... acpi_early_init start_kernel Kernel panic .... At a guess, I tried starting the installer with the options: linux text acpi=off noprobe I am not really clear on what part of the boot process is failing so I tried a number of random boot options including apm=off, noapic, apic, nomce. Nothing I tried change the error. (I also tried installing RHEL 4 but I got the same failure with less informative error reporting: Kernel panic - not syncing: Attempted to kill the idle task!) I also tried changing my BIOS options - changing the interupt mode from APIC to PIC which, if I underst...

I have a Lilo.conf file, which I have tried for many hours to convert to Syslinux. I looked around on the web for references on translating some of the components. I want to convert it to Syslinux/Isolinux. Any suggestions would be greatly appreciated. When I tried to convert it I made sure that the kernel and initrd had proper DOS names and such. -Michael =:LILO.CONF:= prompt timeout=10

Hi, Apologies in advance if this is rather long winded ... I have a Windows 2000 DHCP/FTP/TFTP server, serving up a linux-based diags package using PXELinux. Everything is working fine, just like I'd expect. I also have some WinImage images of DOS floppy disks that I'd also like to serve via PXE. So I made up some simple menus using menu.c32 to serve both the floppy image and the

...g Press ENTER to boot or TAB to edit a menu entry label live menu label Live kernel /live/vmlinuz append initrd=/live/initrd.img boot=live config quiet label livefailsafe menu label Live (failsafe) kernel /live/vmlinuz append initrd=/live/initrd.img boot=live config noapic noapm nodma nomce nolapic nomodeset nosmp vga=normal label live-686 menu label Live 686 kernel /live/vmlinuz2 append initrd=/live/initrd2.img boot=live config persistent noprompt debug=1 label live-686failsafe menu label Live 686 (failsafe) kernel /live/vmlinuz2 append initrd=/live/initrd2.img boot=live...

Hi there!! I has been modified the syslinux.cfg file according to the rules to add some boot parameters but since this modification, every time I that I highlight the modified entry in the boot menu and hit the TAB button on my keyboard, the entry's boot parameters is displayed twice and when I try to "backspace" them out, the line again get displayed twice and so on. So my

...is: label livefailsafe menu label Live (failsafe) kernel /live/vmlinuz2 append initrd=/live/initrd2.img boot=live config live-media=removable apparmor=1 security=apparmor nopersistent noprompt timezone=Etc/UTC block.events_dfl_poll_msecs=1000 splash noautologin module=Tails noapic noapm nodma nomce nolapic nomodeset nosmp vga=normal Cheers, -- intrigeri

...ox-20070620+IPAFont.iso,hdc,r'' ] vif = [ ''mac=00:16:3e:00:00:20'' ] ramdisk = "/export/xen-images/xenoppix/miniroot-xen.gz" kernel = "/export/xen-images/xenoppix/vmlinuz-2.6.18-xen" extra = " ramdisk_size=100000 init=/etc/init lang=de apm=power-off nomce xserver=Xvnc_xen nosound noapic noacpi pnpbios=off acpi=off nofstab noscsi nodma noapm nousb nopcmcia nofirewire noagp noswap nohwsetup" So the question is : Is the config file format used to install a Solaris DomU only possible for Solaris DomUs? regards Bernd This message posted fr...

....config files for i586. Building the i586 kernel and kernel-devel packages with Mock Building the i386 kernel-headers packages Setting up a minimal system on another (>=i686) computer, installing the kernel, adding any command line options to grub (for me, the system would not boot without "nomce"), installing openssl.i386 and glibc.i386, etc. It looks like the CentOS for the Pentium (and other archs) project might grow, so the content will probably change very fast, and soon might be outdated if a bootable i586 image is pushed out the door. In the meantime, though, I'd like the i...

...ux.cfg 553 CFG-bestand 17/12/2003 15:07:20 something like this should work for isolinux.cfg LABEL knoppix kernel VMLINUZ append ramdisk_size=100000 init=/etc/init lang=us apm=power-off hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi vga=791 initrd=MINIROOT.GZ nomce quiet BOOT_IMAGE=KNOPPIX the knoppix floppy file contains: ldlinux.sys syslinux syslinux.cfg vmlinuz 600KB or so initrd.gz 300KB or so. this means you should have plenty of space. I don't know if anyone has succeeded in a Linux 2.6 bootdisk with a somehow compressed kernel (bzImag...

hi, i am wondering about how submission of append parameters can be done. i have the following isolinux.cfg: --------------------------------------------------------------------- DEFAULT linux PROMPT 1 TIMEOUT 100 LABEL linux KERNEL vmlinuz APPEND initrd=initrd.gz nomce quiet ---------------------------------------------------------------------- what i want to do is to tell at start which keyboard layout to use by giving the propriate parameter e.g.: linux keyboard=foo i`am reading the given parameter in linuxrc with the following command: CMDLINE="$(cat...

> Nicolas Boulay wrote: >> kernel vmlinuz >> append livecd=livecd initrd=initrd.gz root=/dev/rd/3 devfs=nomount \ >> acpi=ht nomce vga=normal keyb=fr console=ttyS0,19200n8 > > You're not actually using \-continuation lines, are you? None of the syslinux programs support them at this time. no i wrote it just for this mail. The only message from the booting board is : Extlinux .... as said in my previous mail. But...

Is there a method by which one could boot an ISO image from a flash drive with syslinux? -- Dimeneira aka Dime

Hi Andi, Here's a little batch of cleanups: - re-enable VDSO when PARAVIRT is enabled - make the parainstructions symbols match the other altinstructions naming convention - add kernel command-line options to disable altinstructions for smp and pv_ops Oh, and I'm mailing your noreplacement patch back at you, for no particularly good reason. J --

Hi Andi, Here's a little batch of cleanups: - re-enable VDSO when PARAVIRT is enabled - make the parainstructions symbols match the other altinstructions naming convention - add kernel command-line options to disable altinstructions for smp and pv_ops Oh, and I'm mailing your noreplacement patch back at you, for no particularly good reason. J --

Has anyone yet tried PXE booting the vmlinuz/initrd.img set from Centos 4.0beta2? I have a pxelinux setup that is booting 3.4 PXE images fine, but the equivalent setup for 4.0beta loads the kernel and then splashes the monitor full of multicolor random characters. Not a good start to an install... Anyone had luck? Any changes for PXE boots known for 4.0? Thanks in advance. -Alan