search for: nodeo

I'm developing my own Linux-kernel OS (https://github.com/NodeOS/NodeOS) and I have been able to build a live ISO using IsoHybrid. Point is, it doesn't work on my MacBook Pro (Quad-core, 2.66GHz, 8GB), only on BIOS-based PCs. rEFInd show a new "Legacy OS" entry for the pendrive, but after some seconds it shows the "Not found Operating System...

...label and no TIMEOUT option) and change the kernel arguments to redirect the console to a serial port instead of the screen. So far I've seen that the SERIAL statement give me a welcome message and the loading of the kernel and initramfs on the serial port (but curiously, not the "Loading NodeOS" message that I put, just directly the kernel string...), but the system start automatically. I've read in the docs that the boot prompt can be forced to be shown if the caps_lock or the scroll_lock keys are set, but QEmu doen't offer a way to have them enabled at boot time and by usi...

...dia > Boot Behavior". In general, the file paths can be set by a NVRAM > variable (FilePathList[0] ?) for particular devices. > > Do you have indications that syslinux.efi was really executed ? I get the rEFInd shell, and under it the lines "SYSLINUX 6.03", "Booting NodeOS..." (what I have in the SAY field in syslinux.cfg file), "Loading kernel.img... ok" and "Loading initram.gz... ok", so yes, syslinux.efi gets executed, the syslinux.cfg file is parsed and the linux kernel and the initramfs are loaded, but after that nothing happens, while...

Hi, i wrote: > > http://mjg59.dreamwidth.org/11285.html piranna at gmail.com wrote: > There it says about creating a third El Torito image only for Macs, > since old ones could fail and this could be the problem I'm having. The third boot image is HFS+, not FAT. I understand this is for pre-EFI Macs. Try a Debian amd64 ISO, e.g.:

I'm trying to install SysLinux on a disk image as part of NodeOS automated build process, but seems SysLinux requires administrative priviledges. I suposse this is needed because `syslinux` command try to mount the disk image / device to store the needed files, that otherwise would be have been written before and this step omitted. The other half would be to wr...

On Tue, Dec 20, 2016 at 7:14 AM, piranna--- via Syslinux <syslinux at zytor.com> wrote: > I'm trying to install SysLinux on a disk image as part of NodeOS > automated build process, but seems SysLinux requires administrative > priviledges. I suposse this is needed because `syslinux` command try > to mount the disk image / device to store the needed files, that > otherwise would be have been written before and this step omitted. The >...

...on) and change the kernel arguments to redirect the console to a > serial port instead of the screen. > > So far I've seen that the SERIAL statement give me a welcome message > and the loading of the kernel and initramfs on the serial port (but > curiously, not the "Loading NodeOS" message that I put, just directly > the kernel string...), but the system start automatically. I've read > in the docs that the boot prompt can be forced to be shown if the > caps_lock or the scroll_lock keys are set, but QEmu doen't offer a way > to have them enabled at...

For the sake of the discussion. Screenshots not included due size limit. ----- Forwarded message from syslinux-owner at zytor.com ----- Date: Sun, 05 Apr 2015 17:09:50 -0700 from: syslinux-owner at zytor.com To: syslinux-owner at zytor.com Subject: Syslinux post from piranna at gmail.com requires approval List: Syslinux at zytor.com From: piranna at gmail.com Subject: Re: