similar to: newbie

Hi, I 'am trying to launch linux kernel 2.6.7 with initramfs. My pxelinux.cfg/default file looks as follows: default a1 prompt 1 timeout 600 label a1 kernel vmlinuz-2.6.7-1 append initrd=initramfs_data.cpio.gz root=/dev/ram0 init=/linuxrc Kernel image vmlinuz-2.6.7-1 and initramfs_data.cpio.gz was loaded succesfully by pxelinux. Kernel says: checking if image is initramfs... it is but

Hello, I have a couple of questions, But first.... Thankyou for creating such an easy to use awesome piece of software. I am wanting to use ISO linux to select two different kernels/configurations and have set up the isolinux.cfg file as follows.... DISPLAY start.msg TIMEOUT 10000 DEFAULT linux LABEL linux KERNEL vmlinuz APPEND root=/dev/ram0 initrd=txtimage.gz LABEL linux-fb KERNEL

Hi,   I am trying to build dom0 iso. I have following in my isolinux.cfg file. I see error: "Invalid or corrupt image file".   --- default 1 prompt 1 timeout 300 display menu.txt label 1   kernel boot/vmlinuz.vm   append boot/xen.gz  ramdisk_size=131072 initrd=boot/ramdisk.gz root=/dev/ram0 ---   The image I check is valid. xen.gz is actually xen-3.4.2.gz: xen.gz: gzip compressed data,

Hello, I'm trying to launch NFS MW on Wine 1.0.1, but instead of playing game i get errors in console: Code: $ wine "/media/USBFLASH/nfs/speed.exe" fixme:mixer:ALSA_MixerInit No master control found on HDA ATI HDMI, disabling mixer fixme:imm:ImmDisableIME (0): stub err:wgl:get_render_type_from_fbconfig Unknown render_type: 0 err:wgl:get_render_type_from_fbconfig Unknown render_type:

Hi all, I''m trying to boot XEN. I get the following error though Panic on CPU 0: Early fatal page fault at e008:ff134570 (cr2=fffdf020, ec=0000) Reboot in five seconds... Unknown interrupt (cr2=fffdf020) My system has 2GB of RAM. Has anyone had the same problem and can give an hint? Thanks. In case anyone had done the same I''m doing, I''m actually downloading XEN

hi ya syslinuxerz - i've been slowly working on a making a custom bootable standalone usb-stick with X11 and kde - it's basically builds itself off of a slackware-10.1 server - create a custom initrd.gz ( /dev/ram0 ) http://linux-boot.net/Bootable/InitRD/ - create a custom rootfs.gz ( /dev/loop0 ) http://linux-boot.net/Bootable/RootFS/ - create X11 and kde loopfiles

Hi! I write this config line: kernel /boot/i386/vmlinuz ro ramdisk=32768 root=/dev/ram0 init=/linuxrc but when I try to boot I got this mesasge: Could not find kernel image: /boot/i.386/ Same symptomes are with slash and backslash too. I think, the parses don't understand the directory separator characters and count as the part of filename. ps Sorry for my english -- Gabor HALASZ

Hi, I have setup pxelinux like this, default linux label=linux kernel linux append initrd=rootfs.img ipappend 1 I have my dhcpd.conf like this, allow booting; allow bootp; group{ filename "pxelinux.cfg/pxelinux.0"; host deploy { next-server 192.168.1.254; hardware ethernet 00:0E:A6:22:28:21;

The following is a pxelinux problem, specifically to do with including config files with the menu include directive and the ifcpu64.c32 com module. I have a working ifcpu64.c32 setup that jumps to the label rescue64 in the case of a 64-bit CPU. The label "rescue64" defines a 64-bit kernel and a 64-bit initrd.img. The setup jumps to a label named "rescue32" in the case of a

Hi Dongyang, Yan, When testing BTRFS with RAID 0 metadata on linux-3.3, we see discard ranges exceeding the end of the block device [1], potentially causing dataloss; when this occurs, filesystem writeback becomes catatonic due to continual resubmission. The reproducer is quite simple [2]. Hope this proves useful... Thanks, Daniel --- [1] attempt to access beyond end of device ram0: rw=129,

I am trying to boot a ramdisk on a usb stick in read-only mode using extlinux. When the system boots all I am getting is a blinking cursor. The stick booted with lilo, but I had some issues with lilo so I am trying extlinux. 1) I partitioned the stick as a linux partition, formated it ext2, and mounted /dev/sda1 on /mnt/flash. 2) I am running extlinux 3.86. 3) excuted "extlinux -i

I am running isolinux 4.02 and ramdisk_size does not seem to have an effect on the ramdisk size. No matter what I set it to in the isolinux.cfg file it seems the limit is 32768. I get the error: ram0: rw=0, want=360456, limit=32768 EXT2-fs error (device ram0): My isolinux.cfg file: LABEL EB KERNEL vmlinuxE APPEND initrd=bos.img root=/dev/ram0 rw ramdisk_size=545000 I am running the 2.6.38.2

Hi, I am trying to track down a ISOLINUX boot problem on my workhorse computer. Booting slax-6.0.0-rc5.iso from www.slax.org (a live distro) from CD gives the following messages: Loading /boot/vmlinuz ........... Loading /boot/initrd.gz ............ Ready. _ Silence. The next message should be, but does not appear: Uncompressing Linux ........... This message appears with the same CD on an old

Hello all, I think I may have found a bug with the way lpxelinux.0 sends http requests. Specifically when I trace the requests I notice that the Host: header does not contain the port that was used to make the request. Here's my scenario. I have a python Flask app that dynamically generates the PXE menu for kickstarts. When I request a URL the server responds with a file containing more

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

  Sure. Thanks again for the prompt help - very appreciated. As I see I am trying to do what only few have done wrt Xen dom0 to package as bootable iso with ramdisk.   Now error below Xen dom 0 is trying to bring up Linux:   <..clipped..> md: ... autorun DONE. RAMDISK: ext2 filesystem found at block 0 RAMDISK: image too big! (524288KiB/4096KiB)   <...clipped: Details below...>

I'm integrating DBAN (http://dban.sourceforge.net/) into our PXE boot menu system (using vesamenu.c32) but it just hangs when I'm using vesamenu.c32 and confusingly when I revert our menu system to using vesa.c32 it works ok. I've stripped out any extraneous configuration but it still seems to have the same problem. When I use this in pxelinux.cfg it boots into DBAN ok: default

Looking at the FAQ for SysLinux there is an option for an initrd file (initrd=filename), this does not seem to work with pxelinux (or it is just that I am doing something wrong...). here is my config file: prompt 1 #serial 0 115200 label linux kernel vmlinuz-2.4.18-ssi #read-write #root=/dev/ram0 append init=/linuxrc console=tty0 console=ttyS0,115200 initrd initrd-2.4.18-ssi.img label local

I have an interesting situation where I am loading gpxelinux.0 v3.72 from pxelinux.0 ( older ). I have a stanza that I use after loading gpxelinux such as : --- label pxelinux.new kernel pxelinux.new.0 label recovery.http kernel http://kickstart/pxelinux.new/vmlinuz-ramdisk append initrd=http://kickstart/pxelinux.new/ramdisk.img.gz ramdisk_size=358400 ramdisk_blocksize=1024

Hello, When I upgrade syslinux from 2.13 to 3.02. my linux floppy doesn't boot anymore. steps: dd if=/dev/zero of=fdimg bs=18k count=160 mkdosfs fdimg syslinux fdimg mount -o loop fdimg /mnt cp files/* /mnt/ umount /mnt then use memdisk load fdimg the files includes: vmlinuz initrd syslinux.cfg message.txt f1.txt ... it only prompts 1 line: SYSLINUX 3.02