search for: epsm

Displaying 18 results from an estimated 18 matches for "epsm".

Did you mean: eps
2014 Mar 17
1
Regarding: unable to make USB-ZIP using rufus_v1.4.5
Test, test one two, test > > > > Thanks in advance, > > > > Prof S W Damle > > I don't know whether Pete Batard (RUFUS' developer) have read your > messages. And this message is to see if the "reply to list mungling" is gone. (Check the E-mail headers ( this message was/is a "reply to list" )) Groeten Geert Stappers
2010 May 16
0
[PATCH v2 2/3] fbmem, drm/nouveau: kick firmware framebuffers as soon as possible
...;s a short window between start of initialisation and framebuffer registration when two drivers touch the hardware. Unfortunately sometimes it breaks nouveau initialisation. Fix it by kicking firmware driver(s) before we start touching the hardware. Reported-by: Didier Spaier <didier.spaier at epsm.fr> Tested-by: Didier Spaier <didier.spaier at epsm.fr> Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc: Andrew Morton <akpm at li...
2010 Apr 12
1
[PATCHv2 1/2] fbdev: allow passing more than one aperture for handoff
It simplifies nouveau code by removal of detection which region to pass to kick vesafb/efifb. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Eric Anholt <eric at anholt.net> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Thomas Hellstrom <thellstrom at vmware.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc:
2010 Apr 05
3
Blank screen at startup (conflict with VESA VGA)
Hi all, new to this list ;) I have a Lenovo Thinkpad T61. lspci|grep VGA says: 01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 140M (rev a1) I have Slacware64-13.0 and Slackware64-current installed. Nouveau is modularized in all my kernels for -current. A problem arise even if I don't want to use nouveau under X: unless nouveau be blacklisted in
2013 Mar 26
5
Allowed code pages and encodings to write f0.txt through f1.txt?
Hi there. Slackware's installer, that I am internationalizing, makes use of ISOLINUX. I want to give instructions to users in other languages than US English, e.g. which code to type to see installation messages in their native language. So my question are: (1) Which character encodings can be used in message.txt and f1.txt through f1O.txt? (2) Is UTF-8 allowed? (3) I'm guessing that
2010 Apr 10
3
[PATCH 1/3] fbmem: fix aperture overlapping check
fb_do_apertures_overlap is returning wrong value when one aperture is completely whithin the other. Add generic ranges_overlap macro (probably kernel.h candidate) and use it here. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> Cc: Dave Airlie <airlied at redhat.com> Cc: Peter Jones <pjones at redhat.com> Cc: Andrew Morton <akpm at linux-foundation.org> ---
2013 Nov 01
0
isohybrid fails with: seek error - 3
On 01/11/2013 18:40, Didier Spaier wrote: > On 01/11/2013 05:36, Ady wrote: >> >>> That is with syslinux 4.05 on Slackware-14.0: >>> >>> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >>> catalogue offset: 561 >>> ve[0]: 1, cs: 1 >>> ve[1]: 0, cs: 1 >>> ve[2]: 0, cs: 1 >>> ve[3]: 0, cs: 1 >>>
2014 Apr 16
2
syslinux fails to make a bootable USB stick in Slackware64-14.1 installer
On 16/04/2014 23:46, H. Peter Anvin wrote: > On 04/16/2014 02:15 PM, Didier Spaier wrote: >> Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 >> (to make a bootable USB stick) fails like this: >> >> Error converting to codepage 850 Invalid argument >> Cannot initialize 'S:' >> Bad target s:/ldlinux.sys >>
2013 Oct 31
2
isohybrid fails with: seek error - 3
That is with syslinux 4.05 on Slackware-14.0: bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso catalogue offset: 561 ve[0]: 1, cs: 1 ve[1]: 0, cs: 1 ve[2]: 0, cs: 1 ve[3]: 0, cs: 1 ve[4]: 0, cs: 1 ve[5]: 0, cs: 1 ve[6]: 0, cs: 1 ve[7]: 0, cs: 1 ve[8]: 0, cs: 1 ve[9]: 0, cs: 1 ve[10]: 0, cs: 1 ve[11]: 0, cs: 1 ve[12]: 0, cs: 1 ve[13]: 0, cs: 1 ve[14]: 21930, cs: 21931 ve[15]: 43605, cs:
2014 Jul 29
0
isohybrid: slint64-14.1.iso: unable to find mac efi image
HI, On 29/07/2014 22:23, Ady wrote: > Even without such "Mac" hardware at hand, it might still be helpful > to test mkisofs 3.01a24 and then check the resulting ISO image. > Perhaps Didier can update his current version of mkisofs and retry > with his current scripts/receipts. I will upgrade the cdrtools package from 3.01a17 to 3.01a24 in the coming days and see what I
2013 Nov 01
2
isohybrid fails with: seek error - 3
On 01/11/2013 05:36, Ady wrote: > >> That is with syslinux 4.05 on Slackware-14.0: >> >> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >> catalogue offset: 561 >> ve[0]: 1, cs: 1 >> ve[1]: 0, cs: 1 >> ve[2]: 0, cs: 1 >> ve[3]: 0, cs: 1 >> ve[4]: 0, cs: 1 >> ve[5]: 0, cs: 1 >> ve[6]: 0, cs: 1 >> ve[7]: 0, cs: 1
2014 Apr 16
2
syslinux fails to make a bootable USB stick in Slackware64-14.1 installer
Running "syslinux -s /dev/dsb" during installation of Slackware64-14.1 (to make a bootable USB stick) fails like this: Error converting to codepage 850 Invalid argument Cannot initialize 'S:' Bad target s:/ldlinux.sys syslinux: failed to create ldlinux.sys But running the same command in the installed system succeeds. In both cases we are using syslinux-4.0.6 (same syslinux
2014 Jun 23
1
isohybrid has 2 variants
Hi, On 23/06/2014 12:07, Thomas Schmitt wrote:> Hi, > > i have written an introduction to isohybrid and put it on > the discussion page of the ISOLINUX wiki. > > http://www.syslinux.org/wiki/index.php/Talk:ISOLINUX#Proposal_for_description_of_isohybrid > > Review and proposals are appreciated. Caveat emptor: this is a review by an end user (not a developer), who
2014 Jul 29
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
HI, In http://slint.fr/misc/MacBoot/ you'll find all context information. All files referenced here are stored there. Long story short: once dd-ed on an USB stick the ISO image can boot on a BIOS or EFI machine, but I want it to be able to boot on most x86_64 Macs with an EFI firmware. Unfortunately I get the error message: isohybrid: slint64-14.1.iso: unable to find mac efi image The
2014 Nov 10
2
Boot fails in a VMware player VM - syslinux 6.03
On 10/11/2014 04:02, Ady wrote: > >> Hi there, >> >> I failed to boot an installer in a VMware player (Version6.0.3 >> build-1895310) >> using syslinux 6.03, be it off an hybrid ISO image and an USB stick. >> >> Booting succeeds if the VM is set to use a BIOS firmware with both media, >> but fails using an efi firmware. >>
2014 Nov 10
1
Boot fails in a VMware player VM - syslinux 6.03
On 10/11/2014 10:46, Thomas Schmitt wrote: > Hi, > > i downloaded > http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso > > Inspection by xorriso-1.3.8: > > xorriso -indev slint64-14.1_syslinux.6.03.iso \ > -report_el_torito plain \ > -report_system_area plain > > yields > > El Torito catalog : 46 1 >
2014 Jul 29
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso
2014 Jul 30
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
Hi, On 29/07/2014 23:19, Thomas Schmitt wrote: > A good opportunity to brag with xorriso's boot inspection > features (since xorriso-1.3.8): Yes! I've upgraded libburn, libisofs and libisoburn so now I can play with it too ;) > I forgot to advise (or misadvise) -isohybrid-apm-hfsplus with > the image /isolinux/efiboot.img . So we only got one APM > partition here. A