20210628 - Upgrade of php fixed the page rendering issue.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
howtos:hardware:arm:toshiba_ac100_dynabook_az [2015/06/18 05:19 (UTC)]
didierspaier [Backuin Up] Typo fixed.
howtos:hardware:arm:toshiba_ac100_dynabook_az [2016/03/30 12:51 (UTC)] (current)
louigi600 [Repackaging The Boot Images For Aboot]
Line 38: Line 38:
   13      EM2     1001984 256 (512 kB)   13      EM2     1001984 256 (512 kB)
   14      UDB     1002240 6837504 (13354.5 )      user data (/storage) mmcblk0p7   14      UDB     1002240 6837504 (13354.5 )      user data (/storage) mmcblk0p7
-All partitions hace sectors of 2048 bytes and id 18.+All partitions have sectors of 2048 bytes and id 18.
  
-The tegrapart format is a coma separated list od items like this :+The tegrapart format is a coma separated list of items like this :
   <partition name>:<hex start sector>:<hex partition size in sectors>:<hex sector size in bytes>,...   <partition name>:<hex start sector>:<hex partition size in sectors>:<hex sector size in bytes>,...
 +that needs to be read out from /proc/cmdline while the AC100 is running the stock OS or needs to be manually created based on the info from the output of tegrapart (the latter is tricky as it is undocumented). 
  
 ====== Booting Custom Images ====== ====== Booting Custom Images ======
Line 48: Line 49:
   * via the normal boot image   * via the normal boot image
  
-Even if you manage to reck both you can still rescue your device using nvflash but if you bake backups and only flash one at a time you can just keep the backups safe for any future use. +Even if you manage to wreck both you can still rescue your device using nvflash but if you make backups and only flash one partition at a time you can use the other to put things right. You should keep the backups safe for any future use and/or restoring back the original OS
-try flashing the rescue image first and then I use that to flash the rest ... but you can keep using nvflash for both boot images and even for the root filesystem if you like the idea.+tried flashing the rescue image first and then I use that to flash the rest ... but you can keep using nvflash for both boot images and even for the root filesystem if you like the idea. There is a new rescue image that can be run from ram without actually flashing anything into the rescue partition, but it is handy to have a rescue partition that can be used to assist fixing the OS you are going to install (as the stock one is useless on anything but the stock OS).
  
 ===== Requirements ===== ===== Requirements =====
Line 71: Line 72:
 Although it is technically possible to boot without using an initrd I've not had the time to experiment that. If all you need is simple boot then the initrd only really needs busybox and a very simple script that mounts root and then switches root. Although it is technically possible to boot without using an initrd I've not had the time to experiment that. If all you need is simple boot then the initrd only really needs busybox and a very simple script that mounts root and then switches root.
  
-I make a slight difference between the rescue init script and the boot init script, making the forme allways drop you into a shell prompt from the initrd system and the later allways attempt to switch root.+I make a slight difference between the rescue init script and the boot init script, making the former always drop you into a shell prompt from the initrd system and the latter always attempt to switch root.
  
 This is what my boot init script looks like: This is what my boot init script looks like:
Line 99: Line 100:
  
 If you wish to alter the init scripts you can extract them from the rescue and boot images: first use abootimg to extract the initrd.img then use zcat | cpio -idm to extract the content from the initrd image. If you wish to alter the init scripts you can extract them from the rescue and boot images: first use abootimg to extract the initrd.img then use zcat | cpio -idm to extract the content from the initrd image.
-Edit them to suit your desigred setup (in my case root is on the internal EMMC biggest partition), load any modules required for switching root and then repackage the images.+Edit them to suit your desired setup (in my case root is on the internal EMMC biggest partition), load any modules required for switching root and then repackage the images.
  
 ===== Repackaging The Boot Images For Aboot===== ===== Repackaging The Boot Images For Aboot=====
Line 115: Line 116:
   abootimg -create rescue_new.img -k zImage -f bootimg.cfg -r initrd.img   abootimg -create rescue_new.img -k zImage -f bootimg.cfg -r initrd.img
  
-You are now ready to try your rescue image without actually flashing it.+You are now theoretically ready to try your rescue image without actually flashing it
 + 
 +Restart your device into recovery mode (POWER + ESC + CTRL) an load the rescue image into ram. I've not yet got round to prepare a ram rescue image (requires 3.8+ kernel, u-boot and other details prepended to the kernel and initrd images) but over at ac100.grandou.net they have it sorted out, so for the mean time you can try their ram loading [[https://dl.dropboxusercontent.com/u/40761340/sos-uboot-r5-alpha.bin|sos-uboot-r5-alpha.bin]] image ... other wise skip this step and go to the one below. 
 +If you want to read more about sos-uboot-r5-alpha you can do so [[https://ac100.grandou.net/sosbootr5|here]].
  
-Then restart your device into recovery mode (POWER + ESC + CTRL) an load the rescue image into ram. I've not yet got round to prepare a rab rescue image (requires 3.8+ kernel, u-boot and other details prepended to the kernel and initrd images) but over at ac100.grandou.net they have it sorted out so for the mean time you can try their ram loading sos-uboot-r5-alpha.bin image ... other wise skip this step and go to the one below. 
   nvflash --bl sos-uboot-r5-alpha.bin --sync   nvflash --bl sos-uboot-r5-alpha.bin --sync
  
Line 237: Line 240:
 According to [[http://ac100.grandou.net/kerneldev#mainline_git_kernel|ac100.grangow.net]] form 3.15 on there is full support on mainstream kernel. According to [[http://ac100.grandou.net/kerneldev#mainline_git_kernel|ac100.grangow.net]] form 3.15 on there is full support on mainstream kernel.
  
-Native kernel build (in order to compile this native 512Mb arr not sufficient so you need to swap on something {SD,usb storage or internal emmc}: an extra 512Mb swap will suffice). +Native kernel build (in order to compile this native 512Mb are no longer sufficient so you need to swap on something {SD,usb storage or internal emmc}: an extra 512Mb swap will suffice). 
-It;s technically possible to work form marvin's kernel git but I've not been able to configure that kernel to boot correctly ... it hangs while attempting to read RTC, but it's probably just something wrong that I did in the configuration.+It's technically possible to work form marvin's kernel git but I've not been able to configure that kernel to boot correctly ... it hangs while attempting to read RTC, but it's probably just something wrong that I did in the configuration.
 #git clone --depth 1 -b chromeos-ac100-3.0 https://gitorious.org/~marvin24/ac100/marvin24s-kernel.git #git clone --depth 1 -b chromeos-ac100-3.0 https://gitorious.org/~marvin24/ac100/marvin24s-kernel.git
  

In Other Languages
QR Code
QR Code howtos:hardware:arm:toshiba_ac100_dynabook_az (generated for current page)