Show all posts by user

Re: LG N2B1 - 1 year ago

I took a stab at a first dts specific to this device, it's based on the NS2 dts but with some changes: removed anything that showed as failing in your initial boot removed anything specific to lacie or the NS2 removed the dependency on kirkwood-ns2-common.dtsi adjusted the ram to the correct size enabled pcie which will hopefully allow sata to be detected I confirmed it will build w

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

actually I think you'll need to grab the needed include files out of the kernel source too: kirkwood-6281.dtsi kirkwood-ns2-common.dtsi kirkwood.dtsi I think moving forward you'll want to try to eliminate kirkwood-ns2-common.dtsi as a dependency but I'd suggest verifying you can successfully build a DTB before moving forward with actually editing one.

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

Here is the basic process for getting started modifying the device tree (example shows just building the one you've already tested). #install the needed tools and source (for the dts file) apt-get install device-tree-compiler linux-source-4.9 u-boot-tools #grab the installer initrd (it's already packaged and ready for use) wget "http://ftp.nl.debian.org/debian/dists/stretch

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

typically when I start modifying/testing a device tree I setup a full kernel crosscompile environment with some scripts to make executing the build and packaging the resulting dtb file with the kernel easier. I can help you set something like that up for your testing but I suspect there is an easier way. I'm curious to compare notes with @bohdi who seems to do this more than I do.

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

nice, that's a good starting point. getting it to boot is half the battle and you've already managed that. it looks like it didn't find your hard drive(s) but we were expecting that. you can confirm this by trying to run through the installer, i'm guessing it will say it can't find any disks. hopefully you can find it on the network, you should be able to connect o

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

Looks good. Now add the initrd and you should be in business

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

My bad, I think I directed you at something that doesn't exist for that one. looking at the dts files in the mainline kernel I see the following options: kirkwood-blackarmor-nas220.dts kirkwood-laplug.dts kirkwood-ns2lite.dts kirkwood-ns2mini.dts kirkwood-pogoplug-series-4.dts kirkwood-rd88f6192.dts you could try the lacie ns2 files as a start: https://d-i.debian.org/daily-ima

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

i'd recommend doing it from a hard drive to start, we know it will boot from that. @bohdi might have some advice for getting it to work if you want to pursue that route. also it looks like this has a different SoC than the N4B1 did, rather than trying the kurobox image you'd want to try the ls-xl installer image instead to start.

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

it's been a while since I worked on this one, sadly I didn't keep the greatest notes. You shouldn't have to replace uboot to get this working. as I recall the serial console feels pretty laggy which is fine. I'd recommend starting by trying to boot into that debian installer I linked to earlier. The main advantage being that if sata doesn't work right away you'll

by 1000001101000 - Debian

Re: LG N2B1 - 1 year ago

I had an N4B1 that I did a lot of work with ~ 2010 - 2014 and know quite a bit about that device, I suspect the N2B1 is basically the same. if that's the case it should have a pretty easily accessible serial header on the board. I was able to boot the device using the device-tree for the "kurobox pro" which got network and some other things working. I believe if you enable pcie

by 1000001101000 - Debian

Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 1 year ago

Yeah, usually by the time I can narrow down the issue to the specific patch/commit that caused the problem I find that some has reported it. By then you usually understand the problem well enough to search for it effectively.

by 1000001101000 - Debian

Re: Zyxel 310. No ethernet since the 4.20 kernel on Arch - is it working in Debian? - 1 year ago

QuoteSo you have the same problem as mine - it looks, that the newer kernel isn't perfect. Nobody noticed that besides us yet? I couldn't find noone with this problem in the whole google. Weird... 4.20.x is right at the bleeding edge, it hasn't worked its way into much yet. Even debian testing only moved to 4.19 about a month ago though I beleive there is a 4.20 experimental pack

by 1000001101000 - Debian

Re: Debian on Synology RS816 (Armada 385) - 1 year ago

sounds like a good start. sometimes if you have hardware defined in the dtb that doesn't actually exist it will reserve the pins that you need which will keep you from changing them. I just had that with a device where the drive power pin was one of the i2c pins, the device I copied the original dts from was using i2c for the rtc but the device I was working with didn't use i2c at a

by 1000001101000 - Debian

Re: Debian on Synology RS816 (Armada 385) - 1 year ago

Typically what I do at this point is pull up the gpio binding documentation for the SoC and determine what range of GPIO pins are likely to be the power pins for the drives (ie not reserved for the ethernet controller/uart/etc) and loop through them with a script enabling each while watching dmesg for the drive being detected. Once I've identified all the pins I create the appropriate device

by 1000001101000 - Debian

Re: Debian on Synology RS816 (Armada 385) - 1 year ago

looks like progress, the drive is still accessible with SoC sata disabled. is this a typo? pcie@3,0 { /* Port 2, Lane 0 */ status = "okay"; }; pcie@3,0 { /* Port 3, Lane 0 */ status = "okay"; };

by 1000001101000 - Debian

Re: Debian on Synology RS816 (Armada 385) - 1 year ago

Quoteso this means one drive accessible through pcie and another accessible via soc sata I guess ? look like it. That matches what I've seen before, the soc sata taking priority over the pcie when both are enabled (only the one drive since the device-tree only enables one sata via soc). You should be able to remove the soc sata entry from the dtb so that pcie takes over for that one too:

by 1000001101000 - Debian

Re: Troubleshooting Freeze Issue on Debian 9 - SSH, Ping, Logs - 1 year ago

I might not be the best person to ask when it comes to these devices. These logs might be disabled to reduce disk activity or something like that (I'm guessing if you can run apt-get install it's not a read only filesystem). If you have any logs in /var/log they may be a good place to start. there are a bunch of options you can pursue but someone with more experience troubleshooting

by 1000001101000 - Debian

Re: Troubleshooting Freeze Issue on Debian 9 - SSH, Ping, Logs - 1 year ago

If you've got access to the device when it happens running dmesg for the kernel output is a good first step. /var/log/messages and /var/log/syslog are also good places to start.

by 1000001101000 - Debian

Re: Debian on Synology RS816 (Armada 385) - 1 year ago

While you're working though this, keep an eye on /dev/disk/by-path. That'll let you see whether it's accessing the drive via the soc or the pcie controller. I think your/bohdi's next steps will be to try disabling the soc sata and confirm you're accessing those disks via sata then work on enabling the other disks, though you can do it the other way around. sorry to

by 1000001101000 - Debian

Re: Debian on Synology RS816 (Armada 385) - 1 year ago

That's also probably why using the stock dtb is failing, the new kernel doesn't like that older style binding for pcie (and possibly others). looking again at @bohdi 's dts it looks like that's already covered, the pcie errors are probably from the extra entry he has in there, maybe. I'd guess the drives aren't showing up because they aren't being powered

by 1000001101000 - Debian

Re: Debian on Synology RS816 (Armada 385) - 1 year ago

more or less. most of that is covered in armada-385.dtsi which you are including at the top of your dts file, most likely all you need to do is override the status from "disabled" to "okay". It's probably something like: &pciec { pcie@2,0 { status = "okay"; }; };

by 1000001101000 - Debian

Re: Debian on Synology RS816 (Armada 385) - 1 year ago

I had a virtually identical experience with the Linkstation 441de, Though it's a different SoC the same situation seems to apply. If I'm reading the right specs the armada-385 has 2x sata ports built in just like the armada-370, for the 4+ bay model buffalo uses a seperate sata chip connected via pcie, I'm guessing it's the same for this synology device. If so enabling pcie in

by 1000001101000 - Debian

Re: Debian Stretch on Armada-370 Buffalo Devices (LS2XX, LS4XX, TS1XXX) - 1 year ago

The model I’m working with (TS3400D) helpfully has a serial port on the front which outputs the console, but they disconnect or otherwise inhibit the RX pin. Most other models don’t have any easily accessible UART header (or if they do it’s disconnected). One of these days I’ll put more effort into working around those issues but so far I’ve just lived without being able to directly acc

by 1000001101000 - Debian

Re: Debian Stretch on Armada-370 Buffalo Devices (LS2XX, LS4XX, TS1XXX) - 1 year ago

I forgot you're out of town, I can probably try builing against your source. I've got your patch and config, which version of the source are you currently using? The device I'm using doesn't permit input on the console ( I beleive I need to remove/bypass a diode to re-enable it). It'll be a while before I get a chance to try out that operation. I suppose I could make t

by 1000001101000 - Debian

Re: Debian Stretch on Armada-370 Buffalo Devices (LS2XX, LS4XX, TS1XXX) - 1 year ago

fortunately these devices don't have that issue, in my previous testing I confirmed they can handle kernels up to 11mb (I only tested up to 6mb) and initrd > 75mb. I hooked up the serial console and tried again, unfortunately I didnt get anything past "Starting Kernel ...". most of the times I've had that problem have been an issue with the dtb I was testing, conside

by 1000001101000 - Debian

Re: Debian Stretch on Armada-370 Buffalo Devices (LS2XX, LS4XX, TS1XXX) - 1 year ago

Fortunately Debian has now moved to kernel 4.19 which includes all the fixes required to boot armada-370 devices again and even fixes the temperature sensor issue. I've created new device trees for the 4.19 kernel which can be found at https://github.com/1000001101000/Debian_on_Buffalo/tree/master/Buster/device_trees I attempted to install your linux-4.19.1-mvebu-tld-1 kernel on a device

by 1000001101000 - Debian

Re: Why do we need custom kernel? - 1 year ago

Someone who's actually worked with that device can probably give you better info, but I did a quick search and found a few things. The device is running an SoC that works with that kernel and the kernel package includes a dtb for the device but I didn't find anyone claiming to have actually tried to use that kernel with this device anywhere I've been successful getting that

by 1000001101000 - Debian

Re: armada 370 (88f6710) mainline uboot support - 1 year ago

Looks like the issue with the temperature sensor was due to a bug that was introduced when they made the binding changes rather than the changes themselves. a patch was recently accepted into the mainline kernel to fix it: https://github.com/torvalds/linux/commit/70bb27b79adf63ea39e37371d09c823c7a8f93ce

by 1000001101000 - uBoot

Re: NSA310 - fail installing debian - initramfs - 1 year ago

I should have probably mentioned that the /etc/fstab would be found inside the rootfs once you manage to mount it. bodhi or someone familiar with these specific images might chime in with a best practice for this situation (I haven't gotten around to trying them out yet). But I've been at this point before and think I know what you need. I'm thinking you should be able to g

by 1000001101000 - Debian

Re: NSA310 - fail installing debian - initramfs - 1 year ago

admittedly I'm making a few assumptions. If you post the output of "ls /sys/block", "cat /etc/fstab" from that recovery shell and the output of "printenv" from uboot I can probably be more specific.

by 1000001101000 - Debian