Reto Wrote: ------------------------------------------------------- > I am trying to get apache2 webserver running on > the 4.4 kernel. However without success so far. > Are there any known issues regarding this? For some reason the user www-data was corrupt. Even deleting www-data and creating it again did not help. I am now using a user called www and it works...by Reto - Debian
Bodhi, I am trying to get apache2 webserver running on the 4.4 kernel. However without success so far. Are there any known issues regarding this? I get a Error connecting: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) error message when installing. Thanks, Retoby Reto - Debian
Ok. Thank you again bodhi for all your help to bring my ix4 back to life. I would like to run it a raid 5. Do I have to create a partition on one of the disks first to copy the rootfs and only use the rest of the disk for the raid? Or should I first build the raid and then create a partition for rootfs on it?by Reto - uBoot
Yes I have. So I have to live with an USB memory key sticking out of the box for now?by Reto - uBoot
Ok, so which guide should I follow to flash the kernel?by Reto - uBoot
Same error. File is dated Aug 12 2012by Reto - uBoot
:-( root@debian:/tools# ./blparam MEMGETBADBLOCK: Invalid argumentby Reto - uBoot
bodhi, so what should we do next? Did you already contact damacc or should I do this? Best Regards, Retoby Reto - uBoot
saveenv worked, fw_printenv is giving me too few good blocks within range... root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x00000 0x10000 0x4000 root@debian:~# fw_printenv Too few good blocks within rangeby Reto - uBoot
It is working!!! u-boot is back to life!!! :-) However I had to change the flash_erase command, it was not working with 0 0... Also I now figured out that the second LAN port is working. But my MAC address setenv commands seem not to have any effect... root@debian:/tools# ./flash_erase /dev/mtd0 0 40 Erase Total 40 Units Performing Flash Erase of length 16384 at offset 0x9c000 doneby Reto - uBoot
By the way, I now have a recovery with the following files in it, if this can help us... Unfortunately the recovery seems not to work wihtout an u-boot... and perhaps even more than that... I tried holding the reset button and then booting via kwboot but it did not work... apps 620'602'368 apps.md5 33 config 8'388'608 config.md5 33 content.txt 0 copyjobs.lua 3by Reto - uBoot
root@debian:/tools# ./mtdinfo -a Count of MTD devices: 5 Present MTD devices: mtd0, mtd1, mtd2, mtd3, mtd4 Sysfs interface supported: yes mtd0 Name: uboot Type: nand Eraseblock size: 16384 bytes, 16.0 KiB Amount of eraseblocks: 40 (655360 bytes, 640.0 KiB) Minimum input/output unit sby Reto - uBoot
The network connection does not work although I have set the MAC address... Is it normal that u-boot is saying egiga0 and Debian eth0 root@debian:/tools# cat /proc/mtd dev: size erasesize name mtd0: 000a0000 00004000 "uboot" mtd1: 00010000 00004000 "env" mtd2: 00228000 00004000 "zImage" mtd3: 00300000 00004000 "initrd" mtd4: 02000000 000040by Reto - uBoot
So far so good... Marvell>> setenv usb_make_boot_args 'setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:$(uboot_size)@$(uboot_start)(uboot),$(env_size)@$(env_start)(env),$(kernel_size)@$(kernel_start)(zImage),$(initrd_size)@$(initrd_start)(initrd),32m@0x0(flash) root=LABEL=rootfs rootdelay=10' Marvell>> setenv load_initrd 'ext2load usb 0:1 0x1100000 /boot/by Reto - uBoot
somehow flinfo does not return anything, no error, nothing... Marvell>> help ? - alias for 'help' SatR - sample at reset sub-system, relevent for DB only base - print or set address offset boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootext2 dev:boot_part1,boot_part2 addr boot_image linux_dev_naby Reto - uBoot
Looks promising! Although it says IX4-110 LE so I am not sure if this is the correct u-boot. But most of it seems to work, disk recognized, LCD screen on the box is back to life... __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|by Reto - uBoot
bodhi, gedurin at the NAS forum sent me a mtd0.bin http://forum.nas-central.org/viewtopic.php?f=251&t=18299&p=101383#p101383 Is this what we are looking for? Retoby Reto - uBoot
I am having no luck :-( root@debian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x4000 root@debian:/tools# ./flash_erase /dev/mtd0 0 32 Erase Total 32 Units Performing Flash Erase of length 16384 at offset 0x7c000 done root@debian:/tools# ./nandwrite /dev/mtd0 uboot.2015.10-tld-1.sheevaplug.mtd0.kwby Reto - uBoot
So should I first modify the fw_env.config to reflect the above values?by Reto - uBoot
Before I flash, does this look ok so far? root@debian:/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.2.0-kirkwood-tld-1 -d vmlinuz-4.2.0-kirkwood-tld-1 uImage Image Name: Linux-4.2.0-kirkwood-tld-1 Created: Fri Jan 29 05:56:49 2016 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3147136 Bytes = 3073.38 kB = 3.00 MB Load Aby Reto - uBoot
I checked the environment and it showed the correct MAC addr, so I don't know why it did not apply it... I googled Manufacturer ID: 0xec, Chip ID: 0x75 and found Samsung K9F5608D0C http://www.alldatasheet.com/datasheet-pdf/pdf/83845/SAMSUNG/K9F5608D0C.html? Does this help or confirm?by Reto - uBoot
I tried this before because I thought the MAC address could be the problem. But also with the MAC address set I get: RTNETLINK answers: Cannot assign requested address Listening on LPF/eth0/00:00:00:00:00:00 Sending on LPF/eth0/00:00:00:00:00:00 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 send_packet: Network is down But I found pre-compilby Reto - uBoot
Next problem, I am not able to get a working internet connexion on the box. :-( Does this tell us something or are these fake values? [ 1.775911] nand: device found, Manufacturer ID: 0xec, Chip ID: 0x75 [ 1.782293] nand: Samsung NAND 32MiB 3,3V 8-bit [ 1.786882] nand: 32 MiB, SLC, erase size: 16 KiB, page size: 512, OOB size: 16by Reto - uBoot
Here is the log. What should I ask for? The dmesg output and the mtdparts output in u-boot? Sheevaplug> setenv usb_root 'LABEL=rootfs' Sheevaplug> setenv usb_rootfstype ext3 Sheevaplug> setenv usb_init 'run usb_scan; setenv usb_root LABEL=rootfs' Sheevaplug> setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),4M(uImage),-(rootfs)' Sheevaplug> bootby Reto - uBoot
Finally! I am on 4.2.0... Should we now get more info on the NAND flash? If yes, how?by Reto - uBoot
Still not... Sheevaplug> printenv arcNumber=2097 baudrate=115200 bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset bootdelay=3 console=ttyS0,115200 ethact=egiga0 force_rescue=0 force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /by Reto - uBoot
No luck :-( My USB device is labeled rootfs and formated with ext3... Sheevaplug> setenv usb_root 'LABEL=rootfs' Sheevaplug> setenv rootfstype ext3 Sheevaplug> printenv arcNumber=2097 baudrate=115200 bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset bootdelay=3 console=ttyS0,115200by Reto - uBoot