I have an issue with the serial console and I'm not getting any readings from the device. When pludgged in, the adabper's LED starts blinking, as it is connecting and transfering data, but the terminal stays silent?! I have double and triple checked tha soldering on the ix4, and test the adapter on another device (the NETGER NAS, this topic was initiated for). Soldering looks fine, andby metodi - Debian
Mijzelf Wrote: ------------------------------------------------------- > 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. @Mijzelf, @bodhi, Thanks, guys! I found that my unit has no seriaby metodi - Debian
To clarify: Is this Kirkwood box unable to recognize/handle a GPT drive at all, or it just can't boot from one? I mean what if I use a small MBR drive on SATA0 (disk1) to install Debian on it, and for the SATA1-3 (disk 2-4) I use larger GPT drives? Will Debian then be able to handle the GPT or is this a function of u-boot itself and cannot be worked around? And one more question: If thby metodi - Debian
bodhi, Thanks! I managed to install (and reinstall a couple of times already) Debian on this NAS. In the post, you linked, I found something interesting: "Linux Kernel 6.8.x Kirkwood package and rootfs for... Iomega ix4-200d... and all other Kirkwood plugs that are already in the mainline." I do have one of those - Iomega ix4-200d (not Cloud Edition) devices and I am stuck wby metodi - Debian
Hello all, I'm trying to install Debian Bullseye on my old NETGEAR ReadyNAS Duo v2. I am getting to the point where I should configure Network hardware, but the installer says "No network device found"?! The NAS is working fine with the stock OS, so it is not about a hardware malfunctioning. I've created the uImage using this commands: wget http://ftp.fr.debian.org/dby metodi - Debian
Thank you bodhi, I checked the serial port pins. No odd colors, no sign of burning, no unstable pins. The only odd thing I saw were multiple "wet spots" (I don't know how are these called in English?!) on the back/downside of the whole board. It is like at some moment there were salty water drops that had dried out, but left like tiny white spots?! Now that I have observed thby metodi - uBoot
I'm still trying to get some meaningful data out of the box, using both converters, but still wigh no luck. I have a couple of questions: 1 - is it possible the communication settings to be different, like different baud rate, or data bits, or stop bits, etc.? I searched more information on the internet and I found a couple of articles, stating that those 00s I am getting are a sign forby metodi - uBoot
bodhi, The first row in my previous post is a copy/paste of the picocom log file. This morning I ran the command again, but this time I am attaching the file(s) itself. p.s. I am about to get an FT232RL converter and try if the issues came from the CP2102 converter itself. UPDATE: Today I get another TTL converter, RS323RL and run all the commands mention above with the same result. Iby metodi - uBoot