Quotehttps://github.com/benoitm974/ix4-300d/wiki UART on connector CN9 (four pins, outer side of board) provides Vcc at pin 1 (marked). Connect Pin 2 to the RX pin of your serial adapter, Pin 3 is GND and Pin 4 is TX. Connection parameters are 115200/8N1. Vcc can be controlled by the adjacent JP1 (pin 1 marked); bridging 1/2 provides 3V3, bridging 2/3 provides 5V - but beware that this does NOT cby 1000001101000 - Debian
How you should proceed depends on what you are trying to accomplish and what your constraints are along several axis. odds are anything you need can be found via http://archive.debian.org or https://snapshot.debian.org/. To start: Installing a new libc version into an ancient Debian install risks messing a lot of things up. Hopefully you've got a backup image of this system you can goby 1000001101000 - Debian
I think you're probably right, I've not looked that closely at the protective MBR in such cases. Any chance you could post the output of gdisk -l /dev/sdx for one of your disks?by 1000001101000 - uBoot
It's probably worth mentioning that gdisk supports Hybrid GPT-MBR partitions and will do the hard bits for you. It will also tell you useful things like the state of the secondary GPT table. In my experience a lot confusing uboot issues come from disks with invalid secondary GPT tables either because they aren't in the proper place after cloning a disk or just left over from being reby 1000001101000 - uBoot
Here is some sample code to read those values and print them on the LCD. I don't know quite where the temp sensor is, I assume it's Celsius. I printed the two fan values I'm aware of. The first is the speed setting (0-3) the second might be the PWM value but I don't really know. #!/usr/bin/python3 import libmicon import socket import time test = libmicon.micon_apiby 1000001101000 - Debian
Good to hear from you! What version of Debian/kernel are you running? (It's not important to my answer, I'm just curious). Sadly, I've only really implemented the minimum required to successfully use the device (disable the onboard watchdog timer, set a welcome message, fan daemon so rackmount devices aren't so loud). Beyond that I've only provided examples of how cby 1000001101000 - Debian
Go you have a link to the GPL source in question?by 1000001101000 - uBoot
Nice!by 1000001101000 - Debian
I spent some time working with an ix4-200d a couple years ago. I found that benoitm974's kernel module for the LCD worked if adjusted the GPIOs but also found that approach to be a pain to work with. I ended up writing some Python to set the display, it should work with the ix4-300d if you change the GPIOs to the proper ones for that device. https://github.com/1000001101000/ix4-200d-rby 1000001101000 - Debian
Turns out the PCI issue for non-DTB devices was less complicated than I thought…. Or at least working around it is fairly simple. The PCI setup attaches a map_irq function to a function pointer so that the proper irq can be assigned when a device is detected. If the driver making the call is in a kernel module that call crosses a namespace boundary and results in a kernel panic. This issue canby 1000001101000 - Debian
I have a similar quick and dirty solution I use in my installer: https://github.com/1000001101000/Debian_on_Buffalo/blob/master/Tools/ifup-mac.sh I know someone created an out-of-tree kernel patch that mimicked the method buffalo/marvell use to pass the MAC though that repo appears to have disappeared. I never used it personally since I have this weird fixation with compatibility with Debian&by 1000001101000 - Debian
Sorry, I've been away and didn't see this. I've got a device tree for that device here: https://github.com/1000001101000/Debian_on_Buffalo/tree/master/Buster/device_trees make sure to use the wxl device tree (I believe there is mainline one too), your comment about 64 vs 128mb has me worried you may have the wrong one in mind.by 1000001101000 - uBoot
Neat! On a brighter note, I was able to Upgrade my LS-GL to Bullseye (with Debian's 5.10 kernel) without issue. Looks like some Orion5x devices should work just fine.by 1000001101000 - Debian
Quotebodhi Ah, I see that the 2MB kernel size is artificial (limited by the stock MTD partition). That sounds worth a shot, though it might not be the only limitation. I know from experience on some of those Orion5x devices uboot crashes if you try to load a kernel file larger than 2mb. It's also pretty common for NAS devices that boot from mtd devices to not have drivers for their onboarby 1000001101000 - Debian
I believe the specific issue is that the uboot on these older devices can't handle kernel images larger than 2MB and it's become virtually impossible to compile a kernel that small these days. I have some ideas to work around that limit but haven't spent much time looking at it yet. I'm guessing the TS-409 would have separate issues since it is an Orion5x devices that usesby 1000001101000 - Debian
@bhodi Thanks or starting this thread. I'm working on Bullseye support for a bunch of similar Buffalo devices and am curious to hear about any experiences with these older QNAP devices. I'm particularly curious if anyone has TS-409 and what was the latest kernel it worked with.by 1000001101000 - Debian
Quotebodhi Thanks, I defer to your experience about this :) I recall some binding for LCD in some Armada boxes. But I don't really know if this LCD needs some driver that is not in mainline yet. I believe the binding is for the shift-register that is used to multiplex the LEDs (I had fun writing a script to find those pins). As far as I could tell when I was looking into it there was noby 1000001101000 - Debian
I don't think there is a driver/binding for this type of display (please correct me if I'm wrong about that). Last year I wrote a python script which displays a bitmap on the screen (it can also be used to read the screen). Checkout lcd_test.py here: https://github.com/1000001101000/ix4-200d-research I was originally planning to do a bunch of other things for this device but ranby 1000001101000 - Debian
I'm assuming you're not using systemd, if you were you can set your script to run after the network is up via a "wants=" field. you should be able to set your script to run have dhcp-client to ensure the network will be up. it's been a while....but don't you put it in rc.6 with a suitable filename (since they get executed alphabetically)?by 1000001101000 - Debian
lol, maybe Buffalo forgot a resistor on their board design.by 1000001101000 - Debian
Exactly! Quote Aurora cache disabled: 42 MB/s Aurora cache enabled: 82 MB/s Aurora cache enabled and CPU coherency enabled: 99 MB/s If the 82MB/s->99MB/s checks out I could see going through the trouble of moving to a custom kernel based around this patch and a few others I'm aware of (phy voltage fix, patch to read MAC from atag etc). I suppose I'd need at leastby 1000001101000 - Debian
Hmmm, i’ll have to try and reproduce that. It might give me a reason to move to a custom kernel for the armhf devices. I tried to avoid that for years but the CI/CD process I put together for the MV78100 kernel is way less painful than I expected.by 1000001101000 - Debian
I suppose technically it's available form debian in the kernel-image or kernel-config package. Here's the one I just grabbed from the device.by 1000001101000 - Debian
depends on whether the kernel will just change it again after you do or not. as far as I can tell danitool and I are using the same hardware and uboot image (I flashed the one they posted) and are getting different results. I think the main difference is I'm using Debian's kernel and my DTB and they are using a custom openwrt kernel and DTB. Seems to me a strong indication this isby 1000001101000 - Debian
One of these days I should take a closer look at the openwrt work on this device. danitool has posted some really interesting stuff about the hardware and even figured out why a subset of these devices have network issues. I wonder if there's something about the openwrt kernel or their DTB that is causing this problem and is subsequently fixed by that DTB entry on the post.by 1000001101000 - Debian
I tested it against Debian's current kernels: 4.9.0-14-armmp (Stretch) 4.19.0-12-armmp (Buster) 5.8.0-0.bpo.2-armmp (Buster-backports) For all three the cache appears to be enabled already (the devmem values look correct and dmesg says it is) [ 0.000000] Aurora cache controller enabled, 4 ways, 256 kB [ 0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a086302 root@ls4by 1000001101000 - Debian
I'll test this out on the LS421DE (same device he's using on openwrt) under Debian and see if I can reproduce.by 1000001101000 - Debian
is it marked read-only in your device tree?by 1000001101000 - Debian
you can search for packages using: apt-cache search sqlite3 Debian's package page is also a great resource: https://www.debian.org/distrib/packagesby 1000001101000 - Debian
Keep us updated though. I've been trying to build a u-boot image for a different armada-370 device (Linkstation LS441DE). I've had some success setting up a crossbuild setup but haven't been able to generate anything useful yet.by 1000001101000 - Debian