Re: Armel: Debian installer freeezes (GuruPlug Server plus)
I try tomorrow record Debian "Stretch" U-boot/uImage/uInitrd -terminal output with instructions "https://www.cyrius.com/debian/kirkwood/sheevaplug/install/; Sorry delay, I have to load new binaries to GuruPlug and I'm not very familiar with unix command line scripting, readable minicom -output needs little tee/sed processing. Kari Tanninen not very handy to make commad line scripting, terminal output Martin Michlmayr kirjoitti 1.3.2018 15:11: (Adding Ian Campbell.) Ok, I didn't notice the version of u-boot from the log you posted and went on what you wrote. However, looking at the log file again, I notice you're loading the DTB file separately. You say you follow my installation instructions but clearly you're not. In Debian installer, for the various plug devices, we append to the DTB at the end of the kernel rather than loading it separately. Can you please follow the instructions at https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ and post the output of that? * Kari Tanninen[2018-03-01 15:01]: I'm using Debian stretch U-boot version (U-boot version number is visible on the log-file). I have tried Debian "buster" U-boot version too, but it freezes at "Setting egiga0" point. There is warning on "Debian Armel installation guide", that U-boot does update kernel variables only on fresh installation, if first U-boot version is older than 2014, there will be problems becouse of "bootm_size" variable is missing and default value cannot be set. Flattened device tree -mechanism is not using those "ATAG" global kernel/U-boot -variables, but problem is missing U-boot "boot_args" -variable, too. Fdt-file includes that "Chosen" -field for command line parameters and U-boot has a commands to resize fdt -file and append command line parameters to it before actual boot. U-boot sets and can read correctly that fdt-file "chosen" part. U-boot kprint line for that "chosen" value is visible on log-file. Martin Michlmayr kirjoitti 1.3.2018 14:02: > * Kari Tanninen [2018-03-01 11:26]: > > HW: Guruplug Server plus with JTAG-box (ARMv5-family) > > original U-boot pre-2014 > ... > > Is there any fix-up/work-aroud trick available or is new kernel > > compiling > > only option? > > I've never had a GuruPlug so I cannot really comment but why are you > using the pre-2014 u-boot version? I cannot remember all the > differences of the u-boot versions of the installation page says you > should upgrade your u-boot before installing Debian. Maybe you can > give this a try. > > Based on the logs you posted, it seems to me that the kernel and > ramdisk are loaded but the kernel doesn't see the ramdisk, leading to > the "no root" issue.
Bug#891857: busybox: Special case for /32 subnets not working as expected
Package: busybox Severity: normal Dear Maintainer, Many of our customers would like to use the debian installer in order to set up their own VMs. Our DHCP servers currently offer addresses with /32 subnets, and we've come to realize that the debian installer does not properly configure the default route. A fix for /32 has already been implemented in an earlier version of busybox, but it doesn't seem to work as expected, because the interface isn't defined while adding the relevant route. Here's a suggested fix, which would probably also clear up what I mean: ## --- tree/debian/tree/busybox-udeb/etc/udhcpc/default.script 2018-03-01 15:45:33.0 +0100 +++ tree/debian/tree/busybox-udeb/etc/udhcpc/default.script_proposed 2018-03-01 15:47:37.259206527 +0100 @@ -68,7 +68,7 @@ # special case for /32 subnets, use onlink when adding routes [ ".$subnet" = .255.255.255.255 ] \ -&& onlink=onlink || onlink= +&& onlink="dev $interface onlink" || onlink= for r in "$router"; do ip -4 route add default via "$r" $onlink done ## We would appreciate it if you could patch all current/relevant versions to use this fix. Thank you! Yuval Freund, ProfitBricks GmbH
Re: Armel: Debian installer freeezes (GuruPlug Server plus)
Sorry, english is not my native language (I'm finnish), so I have been unclear on my previous posts. I have followed instructions literally, but installer freezes and text "Uncompressing Linux..." appears on terminal window. On "https://www.cyrius.com/debian/kirkwood/sheevaplug/install; separate ftd -blob file is indeed not loaded, but when I load fdt kernel finally boots but cannot find rootfile system. There is some information on "Debian armel installation" guide for uInitrd relocation problems and advice to se "bootm_size" to default value. Unfortunatelly that does not work if original U-boot version is pre-2014, becouse of bootm_size value is not set at all. I tried to se "bootm_size" value manually by U-boot without success, only way to get kernel to boot is load fdt separately. Martin Michlmayr kirjoitti 1.3.2018 15:11: (Adding Ian Campbell.) Ok, I didn't notice the version of u-boot from the log you posted and went on what you wrote. However, looking at the log file again, I notice you're loading the DTB file separately. You say you follow my installation instructions but clearly you're not. In Debian installer, for the various plug devices, we append to the DTB at the end of the kernel rather than loading it separately. Can you please follow the instructions at https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ and post the output of that? * Kari Tanninen[2018-03-01 15:01]: I'm using Debian stretch U-boot version (U-boot version number is visible on the log-file). I have tried Debian "buster" U-boot version too, but it freezes at "Setting egiga0" point. There is warning on "Debian Armel installation guide", that U-boot does update kernel variables only on fresh installation, if first U-boot version is older than 2014, there will be problems becouse of "bootm_size" variable is missing and default value cannot be set. Flattened device tree -mechanism is not using those "ATAG" global kernel/U-boot -variables, but problem is missing U-boot "boot_args" -variable, too. Fdt-file includes that "Chosen" -field for command line parameters and U-boot has a commands to resize fdt -file and append command line parameters to it before actual boot. U-boot sets and can read correctly that fdt-file "chosen" part. U-boot kprint line for that "chosen" value is visible on log-file. Martin Michlmayr kirjoitti 1.3.2018 14:02: > * Kari Tanninen [2018-03-01 11:26]: > > HW: Guruplug Server plus with JTAG-box (ARMv5-family) > > original U-boot pre-2014 > ... > > Is there any fix-up/work-aroud trick available or is new kernel > > compiling > > only option? > > I've never had a GuruPlug so I cannot really comment but why are you > using the pre-2014 u-boot version? I cannot remember all the > differences of the u-boot versions of the installation page says you > should upgrade your u-boot before installing Debian. Maybe you can > give this a try. > > Based on the logs you posted, it seems to me that the kernel and > ramdisk are loaded but the kernel doesn't see the ramdisk, leading to > the "no root" issue.
Re: Armel: Debian installer freeezes (GuruPlug Server plus)
(Adding Ian Campbell.) Ok, I didn't notice the version of u-boot from the log you posted and went on what you wrote. However, looking at the log file again, I notice you're loading the DTB file separately. You say you follow my installation instructions but clearly you're not. In Debian installer, for the various plug devices, we append to the DTB at the end of the kernel rather than loading it separately. Can you please follow the instructions at https://www.cyrius.com/debian/kirkwood/sheevaplug/install/ and post the output of that? * Kari Tanninen[2018-03-01 15:01]: > I'm using Debian stretch U-boot version (U-boot version number is visible on > the log-file). I have tried Debian "buster" U-boot version too, but it > freezes at "Setting egiga0" point. There is warning on "Debian Armel > installation guide", that U-boot does update kernel variables only on fresh > installation, if first U-boot version is older than 2014, there will be > problems becouse of "bootm_size" variable is missing and default value > cannot be set. > > Flattened device tree -mechanism is not using those "ATAG" global > kernel/U-boot -variables, but problem is missing U-boot "boot_args" > -variable, too. > > Fdt-file includes that "Chosen" -field for command line parameters and > U-boot has a commands to resize fdt -file and append command line parameters > to it before actual boot. > > U-boot sets and can read correctly that fdt-file "chosen" part. U-boot > kprint line for that "chosen" value is visible on log-file. > > Martin Michlmayr kirjoitti 1.3.2018 14:02: > > * Kari Tanninen [2018-03-01 11:26]: > > > HW: Guruplug Server plus with JTAG-box (ARMv5-family) > > > original U-boot pre-2014 > > ... > > > Is there any fix-up/work-aroud trick available or is new kernel > > > compiling > > > only option? > > > > I've never had a GuruPlug so I cannot really comment but why are you > > using the pre-2014 u-boot version? I cannot remember all the > > differences of the u-boot versions of the installation page says you > > should upgrade your u-boot before installing Debian. Maybe you can > > give this a try. > > > > Based on the logs you posted, it seems to me that the kernel and > > ramdisk are loaded but the kernel doesn't see the ramdisk, leading to > > the "no root" issue. -- Martin Michlmayr http://www.cyrius.com/
Re: Armel: Debian installer freeezes (GuruPlug Server plus)
I'm using Debian stretch U-boot version (U-boot version number is visible on the log-file). I have tried Debian "buster" U-boot version too, but it freezes at "Setting egiga0" point. There is warning on "Debian Armel installation guide", that U-boot does update kernel variables only on fresh installation, if first U-boot version is older than 2014, there will be problems becouse of "bootm_size" variable is missing and default value cannot be set. Flattened device tree -mechanism is not using those "ATAG" global kernel/U-boot -variables, but problem is missing U-boot "boot_args" -variable, too. Fdt-file includes that "Chosen" -field for command line parameters and U-boot has a commands to resize fdt -file and append command line parameters to it before actual boot. U-boot sets and can read correctly that fdt-file "chosen" part. U-boot kprint line for that "chosen" value is visible on log-file. Martin Michlmayr kirjoitti 1.3.2018 14:02: * Kari Tanninen[2018-03-01 11:26]: HW: Guruplug Server plus with JTAG-box (ARMv5-family) original U-boot pre-2014 ... Is there any fix-up/work-aroud trick available or is new kernel compiling only option? I've never had a GuruPlug so I cannot really comment but why are you using the pre-2014 u-boot version? I cannot remember all the differences of the u-boot versions of the installation page says you should upgrade your u-boot before installing Debian. Maybe you can give this a try. Based on the logs you posted, it seems to me that the kernel and ramdisk are loaded but the kernel doesn't see the ramdisk, leading to the "no root" issue.
Re: Armel: Debian installer freeezes (GuruPlug Server plus)
* Kari Tanninen[2018-03-01 11:26]: > HW: Guruplug Server plus with JTAG-box (ARMv5-family) > original U-boot pre-2014 ... > Is there any fix-up/work-aroud trick available or is new kernel compiling > only option? I've never had a GuruPlug so I cannot really comment but why are you using the pre-2014 u-boot version? I cannot remember all the differences of the u-boot versions of the installation page says you should upgrade your u-boot before installing Debian. Maybe you can give this a try. Based on the logs you posted, it seems to me that the kernel and ramdisk are loaded but the kernel doesn't see the ramdisk, leading to the "no root" issue. -- Martin Michlmayr http://www.cyrius.com/
Re: Armel: Debian installer freeezes (GuruPlug Server plus)
Log: Initializing Modem Welcome to minicom 2.3 Port /dev/ttyUSB0 Press CTRL-A Z for help on special keys U-Boot 2016.11+dfsg1-4 (Mar 27 2017 - 18:39:51 +) Marvell-GuruPlug SoC: Kirkwood 88F6281_A0 DRAM: 512 MiB WARNING: Caches not enabled NAND: 512 MiB In:serial Out: serial Err: serial Net: egiga0, egiga1 88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 IDE: ide_preinit failed Hit any key to stop autoboot: 6 5 4 3 2 1 starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... Device NOT ready Request Sense returned 02 3A 00 3 Storage Device(s) found 2055218 bytes read in 242 ms (8.1 MiB/s) 12015242 bytes read in 972 ms (11.8 MiB/s) 10522 bytes read in 76 ms (134.8 KiB/s) chosen { bootargs = "console=ttyS0, 115200 root=/dev/sdb2 rootdelay=10 base- installer/initramfs-tools/driver-policy=most"; stdout-path = "/ocp@f100/serial@12000"; } ## Booting kernel from Legacy Image at 0080 ... Image Name: Debian kernel Created: 2017-12-04 7:25:55 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size:2055154 Bytes = 2 MiB Load Address: 8000 Entry Point: 8000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 0110 ... Image Name: debian-installer ramdisk Created: 2017-12-04 7:25:55 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size:12015178 Bytes = 11.5 MiB Load Address: Entry Point: Verifying Checksum ... OK ## Flattened Device Tree blob at 0c00 Booting using the fdt blob at 0xc00 Loading Kernel Image ... OK reserving fdt memory region: addr=c00 size=3000 Using Device Tree in place at 0c00, end 0c005fff Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Booting Linux on physical CPU 0x0 [0.00] random: get_random_bytes called from start_kernel+0x28/0x3ec with crng_init=0 [0.00] Linux version 4.13.0-1-marvell (debian-ker...@lists.debian.org) (gcc version 6.4.0 20171112 (Debian 6.4.0-10)) #1 Debian 4.13.13-1 (2017-11-16) [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] OF: fdt: Machine model: Globalscale Technologies Guruplug Server Plus [0.00] bootconsole [earlycon0] enabled [0.00] Memory policy: Data cache writeback [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [0.00] Kernel command line: console=ttyS0,115200n8 earlyprintk [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Memory: 513692K/524288K available (3796K kernel code, 325K rwdata, 1164K rodata, 308K init, 229K bss, 10596K reserved, 0K cma-reserved, 0K highmem) [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xffc0 - 0xfff0 (3072 kB) [0.00] vmalloc : 0xe080 - 0xff80 ( 496 MB) [0.00] lowmem : 0xc000 - 0xe000 ( 512 MB) [0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB) [0.00] modules : 0xbf00 - 0xbfe0 ( 14 MB) [0.00] .text : 0xc0008000 - 0xc03bd468 (3798 kB) [0.00] .init : 0xc0503000 - 0xc055 ( 308 kB) [0.00] .data : 0xc055 - 0xc05a1490 ( 326 kB) [0.00].bss : 0xc05a4b14 - 0xc05de214 ( 230 kB) [0.00] ftrace: allocating 17887 entries in 35 pages [0.00] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [0.00] clocksource: orion_clocksource: mask: 0x max_cycles: 0x, max_idle_ns: 9556302233 ns [0.08] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [0.007979] Switching to timer-based delay loop, resolution 5ns [0.014481] Console: colour dummy device 80x30 [17;1H[0.019076] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=80) [0.029677] pid_max: default: 32768 minimum: 301 [0.034594] Security Framework initialized [0.038832] Yama: disabled by default; enable with sysctl kernel.yama.* [0.045674] AppArmor: AppArmor initialized [0.050046] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.056819] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.064903] CPU: Testing write buffer coherency: ok [0.070812] Setting up static identity map for 0x8200 - 0x823c [0.077051] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2 [0.084587] devtmpfs: initialized [0.091148] VFP support v0.3: not present [
Armel: Debian installer freeezes (GuruPlug Server plus)
HW: Guruplug Server plus with JTAG-box (ARMv5-family) Debian U-boot version: Armel stretch (buster u-boot version freezes when setting ethact IP-addresses), original U-boot pre-2014 Debain Installer version: stretch Problem: When trying to launch d-i (stretch, with instructions from Martin Michlmayr webpages) from USB-stick or memory (tftp-load), installer freezes with text "Uncompressing Linux". Original U-boot version pre-2014 has a documented bug with old u-boot versions variables (bootm_size value). Setting initrd_high/fdt_high 0x to fix doesn't help. When FDT-blob loaded to fix problem(addres 0x0c00)kernel founds fdt and uInird and starts obviously normally but won't read command line parametres from fdt-memory area as should (using original default fdt instead), and cannot find root file system (on default fdt-file root filesystem is not defined). Seems that U-boot sets and finds command line parametres to/from fdt normally, but kernel doesn't use it. (maybe d-i kernel configured for statical fdt?) Reference: Globalscale Fedora 11 (+ OpenDC) development package works and installs (unfortunatelly very old) system without major problems (minor changes with MAC-address space defaults to perl script needed) -> HW probably OK Is there any fix-up/work-aroud trick available or is new kernel compiling only option? Kari Tanninen