search for: uboot

...r to make xen boot (potentially non-smp without some later changes). But since I am not familiar enough with Arm I think I am stuck doing something wrong. I compiled the hypervisor with debug and early printk for midway and use the xen.bin file (I could get no output at all when trying to create a uboot image with mkimage from the uncompressed xen.gz). My uboot sequence looks like this: mw.l 800000 0 10000 scsi scan ext2load scsi 0 0x800000 xen.bin ext2load scsi 0 0x1000000 vmlinuz setenv kernsize $filesize ext2load scsi 0 0x2000000 initrd.img setenv initsize $filesize # Tried dtuart=/soc/serial@...

Hello, I would like to know which ARM processors does CentOS support? Does it support Freescale/NXP? Thanks and regards Jay

On 3/3/2017 5:34 AM, Robert Moskowitz wrote: > Well, I only wanted to copy the used part of the drive which I try to > keep small so I can still copy the image to an mSD card if I wish. So > I have to supply the amount of the drive to copy. The bs=512 went > fast enough, but then I was only copying 3.2GB. > > thanks for the help. personally, I would use 'dump' for

I am searching for the cheapeat *nix SOC device with ethernet and wifi that can run Python 2.7. Ethernet should be 100mbit and hopefully supporting PXE. OT because im doubting you can squeeze our bloaty friend onto such a device.... :)

...andard BIOS > > or EFI interfaces. > > > > Now, if you are using EFI, you might just want to consider just running > the kernel itself as an EFI executable. > > If with "bootloader in memory" you mean the whole firmware package, > look at EDK2, Coreboot, or uboot. > > -hpa > Hi Thanks a lot for the answers given. I think I should change this conversion topic to "storing the bootloader inside the BIOS chip" or something similar. I now understand a little bit more about the boot process and see that it is more complicated than just Emb...

On 01/13/16 00:13, Tal Lubko via Syslinux wrote: > > OK. I'll try that. > Any thoughts regarding the requirement to store the bootloader inside the BIOS chip? > That is fundamentally up to your BIOS. The best is to expose the bootloader in the BIOS as a (readonly) disk drive using standard BIOS or EFI interfaces. -hpa

Hello, I got CentOS for PPC64 from this link <http://mirror.centos.org/altarch/7/isos/ppc64/> but it uses grub. I want to use CentOS on a PowerPC Freescale T2080 board with U-Boot as the boot loader. Is it available? Thanks and regards Jaytirth S. Khairatkar | Assistant Manager -------------------------------------------------------------------------- --------------------------

.../rootfs.img, but it seems this is not a complete fs as yum is missing components, for example. So my question is: Is there any way to still use CentOS releases on new ARM64 development environments (without EFI boot support)? (2) In terms of UEFI firmware support in the ARM64 world (e.g. EDKII vs Uboot), is there any officially supported solution for CentOS, or do you simply support whatever supports the UEFI interface? Regards, Fred

...entOS 7 userland for armhfp is still built from the CentOS 7 distribution, with some modified, added (or removed) packages. Here are some highlights for the 7.5.1804 release : - Kernel (for both rpi2/3 and generic boards) was bumped to 4.14.x (LTS version) to also follow the i386 AltArch kernel. - uboot images were updated to version 2018.03 to support more boards - we have now variants other than "minimal" (so GNOME and KDE) - selinux is working in enforcing mode and not in permissive mode by default so there is no need anymore to relabel filesystem and reboot) We have also changed the...

...FI interfaces. >> > >> >> Now, if you are using EFI, you might just want to consider just running >> the kernel itself as an EFI executable. >> >> If with "bootloader in memory" you mean the whole firmware package, >> look at EDK2, Coreboot, or uboot. >> >> -hpa >> > > Hi > > Thanks a lot for the answers given. > I think I should change this conversion topic to "storing the bootloader > inside the BIOS chip" or something similar. > I now understand a little bit more about the boot process and se...

...ing to make a .iso to p2v some old windows servers, and I installed a brand new FC22 server to build my images I run virt-p2v-make-kickstart fedora livecd-creator p2v.ks and I get the following error: Installing: grubby ##################### [435/436] Installing: uboot-tools ##################### [436/436] Installing: b43-fwcutter ##################### [437/436] 947 blocks No '/dev/log' or 'logger' included for syslog logging dracut module 'dmsquash-live' depends on 'img-lib', which can't be...

...gt; >> > >> Now, if you are using EFI, you might just want to consider just > >> running the kernel itself as an EFI executable. > >> > >> If with "bootloader in memory" you mean the whole firmware package, > >> look at EDK2, Coreboot, or uboot. > >> > >> -hpa > >> > > > > Hi > > > > Thanks a lot for the answers given. > > I think I should change this conversion topic to "storing the > > bootloader inside the BIOS chip" or something similar. > > I now understa...

...a lot. I will try this thank you. > > > > So my question is: Is there any way to still use CentOS releases on new > > ARM64 development environments (without EFI boot support)? > > > > (2) In terms of UEFI firmware support in the ARM64 world (e.g. EDKII vs > > Uboot), is there any officially supported solution for CentOS, or do you > > simply support whatever supports the UEFI interface? > > > > I would not call any of this 'supported' .. but the UEFI image is what > we provide and really try to ensure is working .. for large data...

> On Oct 19, 2015, at 9:27 AM, Joerg Sonnenberger via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Mon, Oct 19, 2015 at 08:25:16AM -0700, Chris Lattner via llvm-dev wrote: >> 1) We could introduce a novel legal solution. > > Please, no. > >> 2) We could require new contributors to sign the Apache CLA. > > To me, this is the most acceptable

...IOS as a (readonly) disk drive using standard BIOS or > EFI interfaces. > Now, if you are using EFI, you might just want to consider just running the kernel itself as an EFI executable. If with "bootloader in memory" you mean the whole firmware package, look at EDK2, Coreboot, or uboot. -hpa

...; installed a brand new FC22 server to build my images > > I run > > virt-p2v-make-kickstart fedora > > livecd-creator p2v.ks > > and I get the following error: > > > Installing: grubby ##################### [435/436] > Installing: uboot-tools ##################### [436/436] > Installing: b43-fwcutter ##################### [437/436] > 947 blocks > No '/dev/log' or 'logger' included for syslog logging > dracut module 'dmsquash-live' depends on 'img-lib',...

....... :) I would have answered "CentOS 7 on armhfp board" but your last requirement is the one I'm not sure about : PXE boot But it seems possible : http://linux-sunxi.org/How_to_boot_the_A10_or_A20_over_the_network Never tried that, but it seems that you still need to at least have uboot on a microSD, as embedded firmware on such low cost armhfp boards have zero features for this Now if someone has interest in this , why not test it and report that on the dedicated "CentOS armhfp" wiki page ? https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32 :-) -- Fabian Arr...

...ing ppc. Are those board ppc64 compatible ? What is loaded by default on those ? Nothing would work "by default" from a CentOS side, but something could probably be done if you build a RootFS composed with the ppc64/ppc64le tree (depending on what's compatible with your board) and use uboot to chainload ? Can you give more details about the available and running distros for that board ? -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc T...

...if not let's figure out what we need to do to get what you want. > So my question is: Is there any way to still use CentOS releases on new > ARM64 development environments (without EFI boot support)? > > (2) In terms of UEFI firmware support in the ARM64 world (e.g. EDKII vs > Uboot), is there any officially supported solution for CentOS, or do you > simply support whatever supports the UEFI interface? > I would not call any of this 'supported' .. but the UEFI image is what we provide and really try to ensure is working .. for large data center deployment, etc....

...nk to, not MACADDR, what MAC address you want for your interface. So I have read the nmcli pages and googled a bit.? I cannot find a way to set MACADDR.? I suppose I can set HWADDR then use sed to change it to MACADDR, but this seems a real hack. ARM boards do not have assigned MAC addresses.? Uboot uses various information to generate a local MAC address.? I want finer control of my MAC address for my servers.? In the past, I just edited ifcfg-eth0.? I am trying now to do it all with nmcli.? I thought I had it, but I misread the manual. Any pointers? thanks BTW, I remember setting MAC...