Thanks for your help, even though I was finally resolved in such a strange way.
Posts by RDan
-
-
So I've done crazy:
I made flashdrive Syslinux and crossed the kernel. Once I quickly ran syslinux said flsah memory for a second that was made over LibreELEC creator and it works. Heureka: D -
Yes, I connected the hard drive to another PC and created for him the same thing I have done according to your instructions before the flash disk.
I do not know if it translates properly but I have already mentioned it several times:
Rufus flashdrive created using the Ubuntu ISO works. When creating, I'm asking that the ISO image can vytviřit as DD but recommended ISO.-> Ubuntu LIVE boos USB -> Works on my laptop.
-
I did it all on your hard disk -> IMG using Rufus hdd, copy files, create a Syslinux hdd, copy files -> the same result "Error in mount_flash ..."
PS: Connected to the internal SATA
PPS: LibreELEC creator ... Does the HDD, I had to use Rufus. -
Does not work: sdb1, sda1, sda2 ...
-
[font][font]Jen aby se ujistil, jste nastavit heslo správce? [/font][font]protože oni říkají, že [/font][/font][font][font]Secure Boot Configuration[/font][/font][font][font] karta nebude viditelný bez ní. [/font][/font]
[font][font]Spojení jsem vyslán byl pro svůj model notebooku LIFEBOOK AH531 () přímo z něj výrobcem. [/font][/font]
[font][font]Udělejte, co @ [/font][/font][font][font]Escalade[/font][/font][font][font] vám říkal, jestli se nám podaří najít tu správnou linii dát do "syslinux.cfg" to bude fungovat.[/font][/font]I have set the Supervisor Password.
-
Again, no one does not work:
aTLRDMDBFmZUNN4a6
kLT1SyJzS39nUQAa8
2wS94zHV75BGqLz7A
hiXRZCXzxuS2sHd87 -
-
After conversion to the MBR through the program partition is not bootable.
-
Well, I've already tried at some of the manual hand- OpenELEC.
At the end they wanted to copy the "kernel" in the System section but could not.
Since linux so I did not know what to do. -
Yes, no entries on setting secure boot.
That last Alpha version behaves the same way and if odtraním bootx64.efi so it behaves the same way.
Directly to disk, it can also enroll but I think it will be the same. For GPT's not boot.
And if it is somehow additionally Convert to MBR have no idea.
-
In my bios are items such as video.
LL79pohp7ru1uo8A8I see this in the boot menu.
I stress once again:
That same flashdrive working on it when I create a boot image from an ISO file.
C6wNAfJFoXvyWVk88 -
I think that the true essence of the problem is that these paintings are done DD file system. Flashdrive is created by GPT and as we know from GPT table can boot only UEFI.
If they were ISOs, so if everything worked as it should.
-
When you try to boot it returns to the boot menu.
But the same flashdrive works with Ubuntu.
I downloaded and extracted tar.gz I IMG, the one I'm using 2.11 Rufus recorded on a flash drive. Since this is not an iso image but DD so there do not set any parameters or name. -
I uploaded the latest bios. Newer anymore. In the BIOS settings are absolutely no choice about UEFI.
As I wrote earlier, if you create a bootable flashdrive with Ubuntu ISO file and boot up normally.
-
Notebook: "LIFEBOOK AH531"
Rufus version: 2.11.995
Windows version: Windows 10 64-bit (Build 14393)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.02~beta3
System locale ID: 0x0405
Will use default UI locale 0x0405
Found USB 2.0 device 'Verbatim STORE N GO USB Device' (18A5:0302)
Using autorun.inf label for drive J: 'KODIbuntu'
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 941, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x49B1802D
Drive has a Syslinux Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 7.2 GB (7745830912 bytes)
Start Sector: 2048, Boot: Yes
Scanning image...
ISO analysis:
'E:\Downloads\LibreELEC-Generic.x86_64-7.0.3.img.gz' doesn't look like an ISO image
Disk image analysis:
Image is a compressed bootable disk image
Using image: LibreELEC-Generic.x86_64-7.0.3.img.gzFormat operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE3 for write access
Will use 'J:' as volume mountpoint
I/O boundary checks disabled
Analyzing existing boot records...
Drive has a Syslinux Master Boot Record
Volume has an unknown Partition Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Writing Compressed Image...
Remounted \\?\Volume{eace6ea2-cc57-11e6-9480-50e549b2312e}\ on J:\Found USB 2.0 device 'Verbatim STORE N GO USB Device' (18A5:0302)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 941, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: GPT, NB Partitions: 2
Disk GUID: {CFF990E3-48D0-4BAE-BE7B-A7ABD96C22EB}
Max parts: 128, Start Offset: 17408, Usable = 7746845184 bytes
Partition 1:
Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
Name: 'primary'
ID: {2AB96FCF-B099-4CB3-98E1-27828DAB4CAC}
Size: 512 MB (536871424 bytes)
Start Sector: 2048, Attributes: 0x0000000000000004
Partition 2:
Type: {0FC63DAF-8483-4772-8E79-3D69D8477DE4}
Name: 'primary'
ID: {4CA0891C-F214-49D8-A0C8-3DECED273A81}
Size: 32 MB (33554944 bytes)
Start Sector: 1052672, Attributes: 0x0000000000000000
Found USB 2.0 device 'Verbatim STORE N GO USB Device' (18A5:0302)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 941, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: GPT, NB Partitions: 2
Disk GUID: {CFF990E3-48D0-4BAE-BE7B-A7ABD96C22EB}
Max parts: 128, Start Offset: 17408, Usable = 7746845184 bytes
Partition 1:
Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
Name: 'primary'
ID: {2AB96FCF-B099-4CB3-98E1-27828DAB4CAC}
Size: 512 MB (536871424 bytes)
Start Sector: 2048, Attributes: 0x0000000000000004
Partition 2:
Type: {0FC63DAF-8483-4772-8E79-3D69D8477DE4}
Name: 'primary'
ID: {4CA0891C-F214-49D8-A0C8-3DECED273A81}
Size: 32 MB (33554944 bytes)
Start Sector: 1052672, Attributes: 0x0000000000000000
Checking for Rufus updates...
Checking release channel...
No new release version found.Result on flashce:
post a picture -
I have a laptop without UEFI. Internal hard drive 320 gigabytes
If I create a "LibreELEC USB-SD" Boot Flask and not boot.
To know that it works, I tried to create a bootable flashdrive from the Ubuntu ISO. Thus, I have verified that the other operating system it works.My goal is to use flashdrive LibreELEC install an internal hard disk.
Yes I used "LibreELEC-Generic.x86_64".
I also tried a manual installation. I ended in that I did not go to copy a file named. And since I do not know linux so I did not know what to do.
-
I am trying to simply boot from the created flashdrive. Flashdrive is created USB-SD Creator. Even so, it does not boot. But if you create a bootable Flask with Ubuntu ISO file to the same flashdrive how it works.
I suppose that after boot installation option appears on the internal hard disk.