similar to: ubuntu 13.10 kernel 32bit

Displaying 20 results from an estimated 3000 matches similar to: "ubuntu 13.10 kernel 32bit"

2013 Jun 30
3
6.01-pre 4 no timeout when using serial
Could it be that syslinux is waiting for ever if you use serial mode? SERIAL 0 115200 DEFAULT ramdisk LABEL ramdisk kernel /casper/vmlinuz append boot=casper toram initrd=/casper/initrd.img nomodeset console=ttyS0 LABEL isotest kernel /casper/vmlinuz append boot=casper integrity-check initrd=/casper/initrd.img nomodeset console=ttyS0 LABEL memtest kernel /install/memtest append -
2013 Jun 27
0
ubuntu 13.10 kernel 32bit
On Thu, Jun 27, 2013 at 2:50 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: > Trying syslinux-6.00 and get the following error using ramdisk isotest > or memtest > Loading /casper/vmlinuz... ok > Loading /casper/initrd.img...ok > No linux boot function registered for firmware > Booting kernel failed: Bad file number Try the current -pre (6.01-pre4) -- -Gene
2013 Jun 28
2
com32 poweroff.c32
On Fri, Jun 28, 2013 at 2:31 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 27, 2013 at 6:03 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit >> >> LABEL halt >> com32 poweroff.c32 >> >> Does not power off my qemu, it stays open in halt mode. >> qemu -cdrom
2013 Jun 27
2
com32 poweroff.c32
Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit LABEL halt com32 poweroff.c32 Does not power off my qemu, it stays open in halt mode. qemu -cdrom ubuntu.iso -boot d -net nic,model=virtio -m 1024 -curses If I boot into ubuntu first and do sudo halt -p it powers off and closes qemu. Can poweroff.c32 do the same as sudo halt -p in ubuntu?
2013 Jun 30
2
com32 poweroff.c32
Gert Cuykens wrote: > On Fri, Jun 28, 2013 at 2:41 AM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >> On Fri, Jun 28, 2013 at 2:31 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Thu, Jun 27, 2013 at 6:03 PM, Gert Cuykens <gert.cuykens at gmail.com> wrote: >>>> Using syslinux 6.01-pre4 and ubuntu 13.10 kernel 32bit >>>>
2013 Apr 24
1
casper-rw and PXE
Hallo, syslinux, I'm working with an USB stick and an *.iso image. On an USB stick I can use "casper-rw" and "home-rw" for persistent directories/files. Under PXE I haven't yet found a similar option. Is that a syslinux-/pxelinux problem, or is that a "casper" problem? Example: USB stick, part of "isolinux.cfg": label desinfect menu label
2017 Dec 20
0
no display what can I try.
On Tue, Dec 19, 2017 at 3:47 PM, Jeff Sadowski via Syslinux <syslinux at zytor.com> wrote: > I have an odd issue. > I have one machine that does not display to the monitor when it goes > to a linux boot loader. > It has the issue with grub and pxelinux. > > I see the bios but between bios and graphics driver I see a blank screen. > > Any recommendations on how to fix
2013 Sep 05
3
5.10 regression (from 5.01) MENU INCLUDE broken.
On 09/05/2013 01:55 AM, Gene Cumm wrote: > On Wed, Sep 4, 2013 at 2:34 PM, Piotr Karbowski > <piotr.karbowski at gmail.com> wrote: > >> With syslinux (extlinux) it will jump to last INCLUDE'ed menu always, with >> 5.01 it will display list of elements, then allow me to choose which one I >> want to enter. >> >> Even if the include part contain a
2017 Dec 21
0
no display what can I try.
Have you tried a different monitor? Has that monitor ever shown you a boot loader menu? It might be that it just doesn't support the low-level resolutions Grub is trying to use. On Wed, Dec 20, 2017 at 7:09 PM, Jeff Sadowski via Syslinux < syslinux at zytor.com> wrote: > I want to see things, I'm not sure how quiet would work. > Maybe next time I get the box I can re-put
2017 Dec 19
3
no display what can I try.
I have an odd issue. I have one machine that does not display to the monitor when it goes to a linux boot loader. It has the issue with grub and pxelinux. I see the bios but between bios and graphics driver I see a blank screen. Any recommendations on how to fix it? More to it. It is a newer nvidia card, That I need to drive a 4K monitor at 60Hz . If I replace it with an old nvidia card I can
2023 Jan 13
2
failed: Could not start storage pool: cannot open directory: ... No such file or directory
Hi, # cat /etc/redhat-release CentOS Linux release 7.9.2009 (Core) #virt-install --version 1.5.0 # # ls -l /var/lib/libvirt/isos/ total 8302356 -rw-r--r--. 1 root root 4712300544 Aug 31 2021 CentOS-7-x86_64-DVD-2009.iso -rw-r--r--. 1 qemu qemu 990904320 Aug 11 2021 ubuntu-18.04.5-live-server-amd64.iso -rw-r--r--. 1 qemu qemu 1331691520 Feb 23 2022 ubuntu-20.04.4-live-server-amd64.iso
2017 Dec 21
2
no display what can I try.
I want to see things, I'm not sure how quiet would work. Maybe next time I get the box I can re-put in the older working card and try to do a firmware upgrade. This does not seem distro specific. All versions of grub and syslinux do not work in the default configs. I will try using menu.c32 vs vesamenu.c32 as well. To see if it won't display. On Wed, Dec 20, 2017 at 4:52 AM, Gene Cumm
2008 Mar 04
3
Failed to boot USB drive via syslinux if kernel is not in /
Hi, Sorry for asking this again if this have been asked. I searched this mailing list but I can not find the confirmed answer. We tried to use syslinux to boot USB flash drive. The problem is, if we put the kernel and initrd in /casper directory, syslinux failed to boot, it showed us: ------------------ Booting error message: SYSLINUX 3.11 Debian-2007-03-12 EBIOS boot: /casper/vmlinuz1 Could not
2023 Jan 13
1
failed: Could not start storage pool: cannot open directory: ... No such file or directory
On 13/01/2023 18:50, Kaushal Shriyan wrote: Hi Kaushal, > virt-install --name demoreactui --ram 8096 --disk > path=/linuxkvmguestosdisk/demoreactui.img,size=20 --vcpus 2 --os-variant > ubuntu20.04 --network bridge=br0 --graphics none --console > pty,target_type=serial --location > /var/lib/libvirt/isos/ubuntu-20.04.4-live-server-amd64.iso,kernel=casper/vmlinuz,initrd=casper/initrd
2023 Jan 14
1
failed: Could not start storage pool: cannot open directory: ... No such file or directory
El 13/1/23 a las 18:50, Kaushal Shriyan escribi?: > Hi, > > # cat /etc/redhat-release > CentOS Linux release 7.9.2009 (Core) > #virt-install --version > 1.5.0 > # > > # ls -l /var/lib/libvirt/isos/ > total 8302356 > -rw-r--r--. 1 root root 4712300544 Aug 31 2021 CentOS-7-x86_64-DVD-2009.iso > -rw-r--r--. 1 qemu qemu 990904320 Aug 11 2021 >
2017 Dec 21
1
no display what can I try.
On Wed, Dec 20, 2017 at 10:37 PM, Locane <locane at gmail.com> wrote: > Have you tried a different monitor? Has that monitor ever shown you a boot > loader menu? It might be that it just doesn't support the low-level > resolutions Grub is trying to use. I can't say I've ever seen a monitor that didn't interpolate the very low output sizes. With that, have you
2013 Jul 03
2
com32 poweroff.c32
Gert Cuykens wrote: > On Mon, Jul 1, 2013 at 10:50 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: >> Gert Cuykens wrote: >>> >>> On Sun, Jun 30, 2013 at 6:12 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: >>>> >>>> Which qemu version with which bios are you trying? >>> >>> >>> inside a vmware player 5.0.2
2013 Jul 03
2
Problems with gfxboot.c32
Am 03.07.2013 14:11, schrieb Matt Fleming: > On Wed, 03 Jul, at 12:22:52PM, Andreas Heinlein wrote: >> Hello, >> >> I am currently trying to get the gfxboot archive from Ubuntu 12.04 >> working with gfxboot.c32 under BIOS, using ISOLINUX 6. >> >> AFAIK, the Ubuntu patches have been added in 4.03, and in fact it >> works with the official 4.05 release,
2013 Jul 01
2
com32 poweroff.c32
Gert Cuykens wrote: > On Sun, Jun 30, 2013 at 6:12 PM, Sebastian Herbszt <herbszt at gmx.de> wrote: >> Which qemu version with which bios are you trying? > > inside a vmware player 5.0.2 build-1031769 running ubuntu 13.10 > SeaBIOS (version 1.7.2-20130528_111335-allspice) > QEMU emulator version 1.5.0 QEMU starting from v1.3.0-408-g9ee59f3 no longer supports the Bochs
2010 Apr 14
2
brtfs on Solaris? (Re: [osol-discuss] [indiana-discuss] So when are we gonna fork this sucker?)
brtfs could be supported on Opensolaris, too. IMO it could even complement ZFS and spawn some concurrent development between both. ZFS is too high end and works very poorly with less than 2GB while brtfs reportedly works well with 128MB on ARM. Olga On Wed, Apr 14, 2010 at 5:31 PM, <Casper.Dik at sun.com> wrote: > > >>Just a completely different question...is there any plans