Re: [linux-sunxi] Fedora 19 update causes bootloader to fail?
Hi, On 02/22/2014 09:57 PM, Oliver Schinagl wrote: False alarm I should have cheked it out first; After mounting my SD card in the desktop, I noticed the boot partition had a new kernel and everything was overwritten. ./select-board.sh fixed it, so no biggie. Is it an idea to remove /dev/mmcblk0p1 from fstab? Nah, just edit /etc/yum.conf and add an exclude kernel* line actually there already is an exclude line there, as we had the same problem with F-18, but the kernel package name changed in F-19, and I forgot to fix the exclude. Regards, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [linux-sunxi] Fedora 19 update causes bootloader to fail?
On 02/23/14 09:07, Hans de Goede wrote: Hi, On 02/22/2014 09:57 PM, Oliver Schinagl wrote: False alarm I should have cheked it out first; After mounting my SD card in the desktop, I noticed the boot partition had a new kernel and everything was overwritten. ./select-board.sh fixed it, so no biggie. Is it an idea to remove /dev/mmcblk0p1 from fstab? Nah, just edit /etc/yum.conf and add an exclude kernel* line actually there already is an exclude line there, as we had the same problem with F-18, but the kernel package name changed in F-19, and I forgot to fix the exclude. That will also exclude the boot.cmd updates? Good to know it's that easy. Oliver Regards, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [linux-sunxi] Fedora 19 update causes bootloader to fail?
Hi, On 02/23/2014 10:54 PM, Olliver Schinagl wrote: On 02/23/14 09:07, Hans de Goede wrote: Hi, On 02/22/2014 09:57 PM, Oliver Schinagl wrote: False alarm I should have cheked it out first; After mounting my SD card in the desktop, I noticed the boot partition had a new kernel and everything was overwritten. ./select-board.sh fixed it, so no biggie. Is it an idea to remove /dev/mmcblk0p1 from fstab? Nah, just edit /etc/yum.conf and add an exclude kernel* line actually there already is an exclude line there, as we had the same problem with F-18, but the kernel package name changed in F-19, and I forgot to fix the exclude. That will also exclude the boot.cmd updates? Yes AFAIK those are done by kernel upgrade post-install scripts. Regards, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [linux-sunxi] Fedora 19 update causes bootloader to fail?
On 02/23/14 23:05, Hans de Goede wrote: Hi, On 02/23/2014 10:54 PM, Olliver Schinagl wrote: On 02/23/14 09:07, Hans de Goede wrote: Hi, On 02/22/2014 09:57 PM, Oliver Schinagl wrote: False alarm I should have cheked it out first; After mounting my SD card in the desktop, I noticed the boot partition had a new kernel and everything was overwritten. ./select-board.sh fixed it, so no biggie. Is it an idea to remove /dev/mmcblk0p1 from fstab? Nah, just edit /etc/yum.conf and add an exclude kernel* line actually there already is an exclude line there, as we had the same problem with F-18, but the kernel package name changed in F-19, and I forgot to fix the exclude. That will also exclude the boot.cmd updates? Yes AFAIK those are done by kernel upgrade post-install scripts. Thanks Hans, I made a warning about this in my book. I manually 'fixed' it, but I guess it's safe to just do a select-board.sh again? It only re-writes bootloader, config scripts and kernel, no matter what is in the root at that moment, right? Oliver Regards, Hans -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [linux-sunxi] Fedora 19 update causes bootloader to fail?
False alarm I should have cheked it out first; After mounting my SD card in the desktop, I noticed the boot partition had a new kernel and everything was overwritten. ./select-board.sh fixed it, so no biggie. Is it an idea to remove /dev/mmcblk0p1 from fstab? oliver On 02/22/14 20:58, Oliver Schinagl wrote: Hey all, concider this potentially more a dump of my log. I've spent the last 6!! hours doing a yum update; and after rebooting, I got spewed this. Appearantly the yum update has overwritten. I haven't even looked at the log yet; But it looks like something got updated that wasn't supposed to be ;) Is there anything to prevent this for a common user to have it happen? Olliver [23004.163205] Restarting system. [23005.242007] [hotplug]: try to kill cpu:1 failed! U-Boot SPL 2013.10-rc2-00118-gbf62731 (Oct 13 2013 - 11:53:07) Board: Cubietruck DRAM: 2048 MiB CPU: 96000Hz, AXI/AHB/APB: 3/2/2 spl: not an uImage at 1600 U-Boot 2013.10-rc2-00118-gbf62731 (Oct 13 2013 - 11:53:07) Allwinner Technology CPU: Allwinner A20 (SUN7I) Board: Cubietruck I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0 In:serial Out: serial Err: serial Net: emac Hit any key to stop autoboot: 0 256 bytes read in 9 ms (27.3 KiB/s) Loaded environment from uEnv.txt 19282 bytes read in 9 ms (2 MiB/s) Jumping to boot.scr ## Executing script at 4400 Welcome to a-b-c 0.56. Using defaults for sun4i-a10-cubieboard.dtb, but will not load dtb during startup. Will scan for kernels on mmc, using ext2 filesystems with bootm Starting menu init Using kernel k2 (3.12.9-201.fc19.armv7hl). Auto-booting 3.12.9-201.fc19.armv7hl in 3 seconds. Type ^C to abort then run menu for help. 3 2 1... 5064952 bytes read in 273 ms (17.7 MiB/s) 11865694 bytes read in 603 ms (18.8 MiB/s) bootargs are ro rootwait rhgb quiet root=UUID=33de6a91-2289-4ec7-9703-2b03a9d51725 console=ttyS0,115200 ## Booting kernel from Legacy Image at 4030 ... Image Name: 3.12.9-201.fc19.armv7hl Created: 2014-02-22 18:53:35 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:5064888 Bytes = 4.8 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 4160 ... Image Name: initramfs Created: 2014-02-22 18:53:38 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size:11865630 Bytes = 11.3 MiB Load Address: Entry Point: Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree bootargs are ro rootwait rhgb quiet root=UUID=33de6a91-2289-4ec7-9703-2b03a9d51725 console=ttyS0,115200 ## Booting kernel from Legacy Image at 4030 ... Image Name: 3.12.9-201.fc19.armv7hl Created: 2014-02-22 18:53:35 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:5064888 Bytes = 4.8 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 4160 ... Image Name: initramfs Created: 2014-02-22 18:53:38 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size:11865630 Bytes = 11.3 MiB Load Address: Entry Point: Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree bootargs are ro rootwait rhgb quiet root=UUID=33de6a91-2289-4ec7-9703-2b03a9d51725 console=ttyS0,115200 ## Booting kernel from Legacy Image at 4030 ... Image Name: 3.12.9-201.fc19.armv7hl Created: 2014-02-22 18:53:35 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:5064888 Bytes = 4.8 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 4160 ... Image Name: initramfs Created: 2014-02-22 18:53:38 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size:11865630 Bytes = 11.3 MiB Load Address: Entry Point: Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree bootargs are ro rootwait rhgb quiet root=UUID=33de6a91-2289-4ec7-9703-2b03a9d51725 console=ttyS0,115200 ## Booting kernel from Legacy Image at 4030 ... Image Name: 3.12.9-201.fc19.armv7hl Created: 2014-02-22 18:53:35 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:5064888 Bytes = 4.8 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 4160 ... Image Name: initramfs Created: 2014-02-22 18:53:38 UTC Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size:11865630 Bytes = 11.3 MiB Load Address:
