Re: Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-09 Thread Patrick
On Tue, Mar 8, 2016 at 11:03 AM, 张云 wrote: > > You can circumvent the grub-install bug by substituting a USB memory for > the disk image. > > 发自 网易邮箱大师 > ​Ok, thanks! -Patrick​ ___ Kernelnewbies mailing

回复:Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-08 Thread 张云
You can circumvent the grub-install bug by substituting a USB memory for the disk image. 发自 网易邮箱大师 在2016年03月09日 00:56,Patrick 写道: The problem is caused by the command below mkfs -t vfat /dev/loop0 /dev/loop0 is the whole disk, and /dev/loop0p1 is the partition. The command make a file

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-08 Thread Patrick
> > The problem is caused by the command below > > mkfs -t vfat /dev/loop0 > > > /dev/loop0 is the whole disk, and /dev/loop0p1 is the partition. > > The command make a file system on the disk, thus overrides the disk’s > partition table. > > I guess that it is the partition on which you want to

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-07 Thread 张云
> On Mar 8, 2016, at 7:29 AM, Patrick wrote: > > On Fri, Mar 4, 2016 at 9:09 PM, 张云 > > wrote: > First your must know exactly how linux boot (not at source code level). > > Most recent linux distributions boot as > > grub

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-07 Thread Patrick
On Fri, Mar 4, 2016 at 9:09 PM, 张云 wrote: > First your must know exactly how linux boot (not at source code level). > > Most recent linux distributions boot as > > grub —> kernel —> initramfs’ /init executable > > All the userspace affair is started by initramfs’ /init.

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-05 Thread Patrick
> > What filesystem is on the /dev/sda image that qemu is using? You'll need > to > ​​ > ​ > either build your kernel with the support for that built into the kernel, > or an initrd that modprobes the filesystem module, and then mounts the > filesystem (then there's a few fun and games involved

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-04 Thread 张云
First your must know exactly how linux boot (not at source code level). Most recent linux distributions boot as grub —> kernel —> initramfs’ /init executable All the userspace affair is started by initramfs’ /init. Kernel no longer join the boot process. From you description, I think

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-04 Thread Patrick
On Fri, Mar 4, 2016 at 3:56 PM, Kristof Provost wrote: > > On 04 Mar 2016, at 23:50, Patrick wrote: > ​Thanks for the response.​ I had seen that StackOverflow post and done > that a couple of days ago. I was hoping there was another answer, since I >

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-04 Thread Kristof Provost
> On 04 Mar 2016, at 23:50, Patrick wrote: > ​Thanks for the response.​ I had seen that StackOverflow post and done that a > couple of days ago. I was hoping there was another answer, since I wouldn't > be able to do that if I weren't using QEMU. > If you weren’t using

Re: Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-04 Thread Kristof Provost
On 2016-03-04 11:38:33 (-0700), Patrick wrote: > I was able to install SYSLINUX on a disk image and get the kernel I built > to start booting Linux with QEMU pointing to a loopback device associated > with the disk image. However, at some point far into the boot process, I >

Booting with SYSLINUX on Loopback Device: Kernel Panic - Where to Start?

2016-03-04 Thread Patrick
Hello, I was able to install SYSLINUX on a disk image and get the kernel I built to start booting Linux with QEMU pointing to a loopback device associated with the disk image. However, at some point far into the boot process, I get a kernel panic. I can't read the beginning of the error messages