Wouldn't that mean that you can simply use rtc1 instead of rtc0?by Mijzelf - Debian
Was the original firmware able to wakeup the NAS on RTC?by Mijzelf - Debian
It's common practice to use the names uImage and uInitrd (which could be symlinks to uImage-<version> etc) for u-boot images. vmlinux normally is a 'raw' kernel.by Mijzelf - uBoot
I suggest you to consider to create 3 6TB volumes instead. Apart from having one big volume raid0 has no advantages here. It won't be faster, as the NIC is the bottleneck, and not the raw throughput of a single disk. But it has disadvantages. A single disk failing will kill all your data, and all disks will have to spin up to access the volume.by Mijzelf - Debian
Linux can handle GPT. That is unrelated to how the bootloader managed to start it. So yes, if your u-boot doesn't support GPT and you use a single MBR disk to load Linux, Linux will be able to use GPT on the other disks. Probably it can even use GPT on the MBR disk, if you create a hybrid partition table. QuoteIf the box cannot handle GPT, can I use 4+ TB MBR drives, but with the sector siby Mijzelf - Debian
Quote ## Loading Ramdisk Image at 02000000 ... Bad Magic Number� OpenWrt doesn't use a ramdisk. It's flash space will/is being used by the overlay. So you'll have to change the u-boot environment. https://github.com/openwrt/openwrt/commit/4e46ae1f69b5ff1cf09b2e2eee69a7c38a00202dby Mijzelf - uBoot
There are at least 2 different versions of the Networkspace 2. https://web.archive.org/web/20180720230834/http://lacie.nas-central.org/wiki/Category:Network_Space_2 I suppose that means that there should be 2 different u-boot's either.by Mijzelf - uBoot
The support for the original i386 was dropped in Linux 3.8, more than 10 years ago. AFAIK the main problem with the i386 was a missing CMPXCHG opcode, which made it hard to maintain.by Mijzelf - Debian
I'm afraid my 2Big2 died a few years ago. Bad capacitor, I thought, but exchanging it didn't solve the problem. So either my diagnostic or my soldering capacities are bad. However, according to strings the u-boot of the D2 Network2 supports the usb subsystem. And while I was searching for a u-boot dump for the 2Big2 or 5Big2 I found this: https://plugout.net/viewtopic.php?f=26&t=by Mijzelf - Debian
I think it's a bit more complicated than that. My old 2Big2 didn't have a writable u-boot config, and the stock environment reads a uImage from the raw partition sda6, and then boots it with the kernel commandline root=/dev/sda7. A default Debian boot with initramfs is not possible without exchanging u-boot, AFAIK. However, you can simply write your rootfs to /dev/sda7 and write the uby Mijzelf - Debian
The Mindspeed Comcerto alas doen't have upstream support in the Linux kernel. Only the kernel provided in the vendor provided SDK is available (3.2.54). In your case using the stock kernel is also problematic, as the SoC supports both 4k and 64k memory pages, and the stock kernel uses 64k, which is not compatible with the 'normal' Debian arm7hf rootfs. But you can have a look herby Mijzelf - uBoot
It should be something like eth0.ipaddr=192.168.1.191 eth0.serverip=192.168.1.139 https://community.zyxel.com/en/discussion/comment/35771/#Comment_35771by Mijzelf - uBoot
Quote HD44780: open(/dev/lcd) failed: Operation not permitted What does 'ls -l /dev/lcd*' say? Quote What indicates that the LCD display on the RN104 is a USB device and not a parallel port device? It's not a patallel port device. What was the last time you saw a parallel port? It could be usb, or i2c, or gpio connected, or... . The driver should take care for that.by Mijzelf - Displays
I can't imagine you'd need /dev/parport0. I suppose that is used when you have connected an LCD display to the parallel port, and lcd4linux does the bitbanging in user mode. But you have a driver which should do that work. According to the documentation there should be a /dev/lcd. This wiki suggests that lcd4linux can also handle that.by Mijzelf - Displays
When the position and sizes of the u-boot and u-boot env partitions didn't change, I *think* you only need the stock u-boot environment. The firmware itself is capable of filling the other partitions. Put back the original u-boot environment, download the right RescueStick here, unzip it to a FAT formatted USB thumb drive. Extract the uImage from the file ras.bin (binwalk can tell you whereby Mijzelf - uBoot
As long as the bootloader isn't damaged, you can recover it. But you'll need serial connection.by Mijzelf - uBoot
@martini: That is a neat trick. Do you have any idea why it works? I'd say that for ddr training it doesn't matter if the binary is read from uart or from nand. So which subtle effect is causing this?by Mijzelf - uBoot
In that case mkimage will be dependent on other files which cannot be found due to the different path. You can try to chroot it: chroot /volumeUSB1/usbshare/ /bin/sh That creates a new root in /volumeUSB1/usbshare/, and executes /bin/sh from there. So /volumeUSB1/usbshare/ becomes / in that shell. Then you can cd /boot /usr/bin/mkimage ... By executing 'exit' you leave theby Mijzelf - Debian
Use the full path: /volumeUSB1/usbshare/usr/bin/mkimageby Mijzelf - Debian
# gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.6 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT Your answer: 1 Disk /dev/sda: 7814037168 sectors, 3.6 TiB Model: TOSHIBA HDWD240 Sector size (logical/physical): 512/4096 bytes Disk identifiby Mijzelf - uBoot
Is it possible that you have a variable 'machtype' or something like that with value 1152 in your environment? Try to delete it, or set it to -1.by Mijzelf - Debian
Unfortunately that doesn't work. U-boot recognizes the hybid partition table, reads the GPT and errors out. You could create a hybrid table, and then delete the 'ee' entry in MBR, but I suppose gdisk doesn't support that.by Mijzelf - uBoot
The trick is simple. Use parted or fdisk to create a GPT partition table with a small boot partition (to contain the kernel and initamfs. 100MB or something like that) and further a rootfs partition and maybe a data partition, ... . The partition editor will automatically create a protective MBR table. Then use 'fdisk -t mbr <device>' to let fdisk ignore the GPT table, remove theby Mijzelf - uBoot
Quote WARNING - California Proposition 65 Warning: This product can expose you to chemicals, such as lead, known to the State of California to cause cancer, birth defects, or other reproductive harm. Does that mean anything? Is it just a disclaimer, or is the notebook actually more toxic than other ones?by Mijzelf - Off-Topic
habibie Wrote: ------------------------------------------------------- > Regardless, it > says it supports hot swap. However, I still have > to manually sync and dismount the HDD before pull > it out from the hard drive dock. AFAIK supporting hotswap for a harddisk dock only means that the earth pin will connect first, so that a difference in potential is not absorbed by the dby Mijzelf - Off-Topic
*Is* initrd.img-5.17.4-kirkwood-tld-1 gzip compressed?by Mijzelf - Debian
> Exactly as you point out, the chef build adds modules to rootfs instead of integrating them into kernel so it's no good. That is a consequence of OpenWrt. It's designed to run on devices which are sparse in memory and storage. So everything which is not needed to bring up a minimal functionality is added as a module. To add usb storage and ext4 support to the kernel, it would havby Mijzelf - Rescue System
pm4888 Wrote: ------------------------------------------------------- > Ok Openwrt for E02 has different MTD structure, > but it is not a big deal when usb boot is used, > right? As long as you don't actually flash it, it doesn't matter. > What's the difference say between uboot for kirkwood and uboot for rockchip? Huge. uboot doesn't only load the kernelby Mijzelf - Rescue System
An initramfs kernel doesn't need to support usb or ext4 in order to be booted from usb. It's the bootloader who reads it from usb, and starts it. However, if you need to access the usb filesystem from your running OpenWrt, you can create a custom image here: https://chef.libremesh.org/ You have to add at least kmod-fs-ext4 and kmod-usb-storage. More info can be found here. But beby Mijzelf - Rescue System