Show all posts by user
Discuss all things Debian on your device
Re: Promise Apollo Cloud - Armada 385 - 4 months ago
Just received this device and the first issue I see with the device tree provided above is that it defines 2 CPUs. This device has an 88F6810 as defined by your U-Boot log above and by inspection of the board. So you should remove the cpu@1 definition from your DTS file.by rayknight - Debian
Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104 - 4 months ago
Based on the DTS file I believe you need to include the following config options: CONFIG_AUXDISPLAY=y CONFIG_HD44780=y Rayby rayknight - Displays
Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104 - 4 months ago
First suggestion would be to ensure that the driver has actually loaded. Initialization of the charlcd driver has the following: charlcd_puts(lcd, "\x1b[Lc\x1b[Lb\x1b[L*Linux-" UTS_RELEASE "\n"); This should print the linux version on the display if the module loaded correctly. The (un)official LCD4Linux Wiki could be another source for answers to your question.by rayknight - Displays
Re: Debian on HP Thin Client T5335z - 5 months ago
bodhi Wrote: ------------------------------------------------------- > See the picture in this post (the picture > orientation is also inside-facing-out): > https://forum.doozan.com/read.php?2,66989,116939#msg-116939 > > Perhaps your board is from a different production > lot. The photo in that post appears to be for a HP t5325 not the t5335z which is very different iby rayknight - Debian
Re: Debian on HP Thin Client T5335z - 5 months ago
bodhi Wrote: ------------------------------------------------------- > Serial console pinouts. > > Left-to-Right, Inside facing out. > > MicroJST header > > 1. GND > 2. RxD > 3. TxD > 4. N/A: 3.3V This is confusing and caused me to have issues! The MicroJST on both of my examples is P4 and has pins 1 and 4 labeled. With front of unit with power fby rayknight - Debian
Re: Mainline Linux on GlobalScale D2Plug - 5 months ago
Still not able to affect environment with fw_setenv after the above changes. Since this device has USB serial console its easy enough to get access to u-boot, so no rush to resolve this issue. Rayby rayknight - Debian
Re: Mainline Linux on GlobalScale D2Plug - 5 months ago
bodhi Wrote: > 1. The env size is 64K, sector size 4K > > > # MTD device name Device offset Env. size > Flash sector size Number of sectors > > /dev/mtd1 0x0000 0x10000 > 0x1000 > > With this config fw_printenv now works, but fw_setenv does not appear to actually set anything. Rayby rayknight - Debian
Re: Mainline Linux on GlobalScale D2Plug - 5 months ago
Attached is the result of the above dd command. Rayby rayknight - Debian
Re: Mainline Linux on GlobalScale D2Plug - 5 months ago
root@D2Plug:~# root@D2Plug:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0000 0x20000 0x1000 root@D2Plug:~# fw_printenv Cannot read environment, using default Cannot read default environment from file Attempt to dump mtd1 root@D2Plug:~# nanddump --noecc --omitooby rayknight - Debian
Re: shipping board for a flash - 5 months ago
You might want to mention your general location as someone in the same country/region as you may make more sense than shipping it halfway around the world!by rayknight - Off-Topic
Re: Mainline Linux on GlobalScale D2Plug - 5 months ago
This improves things but I still have an issue. From dmesg I now see the flash partitions recognized: [ 5.461676] spi-nor spi0.0: mx25l3205d (4096 Kbytes) [ 5.467359] 3 cmdlinepart partitions found on MTD device spi0.0 [ 5.474884] Creating 3 MTD partitions on "spi0.0": [ 5.480376] 0x000000000000-0x0000000c0000 : "u-boot" [ 5.488428] 0x0000000c0000-0x00by rayknight - Debian
Re: Mainline Linux on GlobalScale D2Plug - 5 months ago
__ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__|by rayknight - Debian
Re: Mainline Linux on GlobalScale D2Plug - 5 months ago
Following up on this it appears that the correct mac address is already set by the mainline linux kernel and the set_persistent_mac_address script is not needed for this device. root@debian:~# dmesg | grep eth0 [ 5.570953] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address f0:ad:4e:XX:XX:XX [ 152.888169] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, fulby rayknight - Debian
Mainline Linux on GlobalScale D2Plug - 5 months ago
I am trying to get the MVEBU kernel and Debian root file to work with a GlobalScale D2Plug. I was successful in modifying the u-boot environment to boot the MVEBU and Debian root from USB. The first issue I am trying to resolve is getting the MAC address set properly using the set_persistent_mac_address script. The problem I have is creating a correct /etc/fw_env.config file. The stock enviroby rayknight - Debian
Re: Change openWRT to debian on STORA - 6 months ago
bodhi Wrote: -> I could not find this OpenWrt u-boot in their > source tree. So that is my educated guess. > The pull request has not yet been merged by someone with commit access. It likely will not be merged as activity seems to have stopped by the developer back in May and the code will need to be re-based at a minimum. Rayby rayknight - Debian
Re: Problems booting Debian on 88f6283 - 7 months ago
Which dtb file are you using? Have you tried each of the existing dtb files that support the 6283 SOC? kirkwood-openblocks_a6.dts kirkwood-openblocks_a7.dts kirkwood-silverstore-hncn2.dtb kirkwood-topkick.dtb Rayby rayknight - Debian
Re: Problems booting Debian on 88f6283 - 7 months ago
The Marvelll 88F6283 is the low power version of the ARMADA 300/310 available operating at either 800MHz or 1GHz. Its the same processor as the Freecom SilverStore as bodhi suggested, so that dts might be a good starting point. An even closer example would be the Plat'Home OpenBlocksA7 (DTB file is kirkwood-openblocks_a7.dtb) as it has very similar features (i.e. 1GB RAM, 2x Gigabit Etherneby rayknight - Debian
Re: Debian on Dell Wyse T10 / T50 - 7 months ago
karrelax Wrote: ------------------------------------------------------- > GREAT SUCCESS!!!! > > So, In sum: > > I have a Wyse 3020 with thinOs Lite. > The 3020 is a different device than the T10/T50 with a different SOC. The 3020 has an Armada PXA2128 and does appear to be supported by mainline Linux kernel as there is a DTS file (mmp3-dell-ariel.dts).by rayknight - Debian
Debian for older unsupported Chromebooks - 7 months ago
I recently came across my old Samsung Chromebook (the 1st ARM based Chromebook) that is no longer provided updates to Chrome by Google. Found the Velvet OS project on GitHub that provides Debian and Ubuntu images and a build mechanism for not only older Chromebooks but a variety of other ARM devices. I'm happily running Debian Bullseye with kernel 5.18.1 and will be building my on 6.0 versby rayknight - Off-Topic
Re: NSA325 fan control - 9 months ago
I haven't tried it as I did not have an NSA325 at the time (and NAS Central is no longer online), but I recall someone indicating that the gpio lines for the MCU on NSA325 and NSA320 were identical (verified by inspection of both dts files). They apparently were able to add the appropriate node to the NSA325 dts and get the nsa320-hwmon to work with the NSA325 as well. https://cateee.net/lkby rayknight - Debian
Re: NSA325 fan control - 9 months ago
The nsa320-hwmon kernel module is supposed to be able to handle the MCU on both the NSA320 and NSA325. Rayby rayknight - Debian
Re: Pogoplug Network Stack - 9 months ago
Amazon has a 10 pack of 0.5ft for $17.99. They are available in a couple of colors.by rayknight - Off-Topic
Re: HowTo: openWrt on OXNAS boxes - 10 months ago
bodhi Wrote: ------------------------------------------------------- > For now it's a caveat in the installation: that > you can only read from the envs inside Openwrt, > but can only update it in serial/net console. > Curious as to why you can't update envs in OpenWrt? The uboot-env partition is not set read-only. + partition@3c0000 { + label = "u-boby rayknight - Rescue System
Re: Debian/U-boot? on the USI Topkick-1281p2 (Tonidoplug2) - 11 months ago
I have both devices. A TonidoPlug 2 and one that came in a Marvell box with label UGNAS-P30855. The wikidevi entry for Topkick1281P2 was created for the device in the white Marvell box labeled UGNAS-P30855. The only apparent difference is the TonidoPlug 2 has a label identifying it as such. They both have 800 MHz Marvell 88F6283 which according to Marvell differs from the 88F6282 only as follby rayknight - Debian
Re: Debian/U-boot? on the USI Topkick-1281p2 (Tonidoplug2) - 11 months ago
New page for Topkick1281P2 on WikiDevi with board photos. Rayby rayknight - Debian
Re: Debian/U-boot? on the USI Topkick-1281p2 (Tonidoplug2) - 11 months ago
The TechInfoDepot data was taken from my entry on the original WikiDevi created from the device I have. I now contribute to WikiDevi. The processor is an 800 MHz 88F6283. Rayby rayknight - Debian
Re: Pogoplug Mobile BogoMIPS dropped in half from Jessie -> Bullseye? - 11 months ago
They really are just Pogoplug Mobile devices with the Zigbee module soldered to the serial pins. I believe the overclocking to 1 GHz was done by jumping some pins on the serial. I have a box full of these devices, if you'd like one just PM me. Rayby rayknight - Debian
Re: Debian on Synology RS816 (Armada 385) - 11 months ago
See Recovering a Failed Synology Diskstation with a Serial Console for details regarding pin out for most Marvell based Synology NAS. Rayby rayknight - Debian
Re: Pogoplug Mobile BogoMIPS dropped in half from Jessie -> Bullseye? - 11 months ago
The Smartenit Harmony P2 which was a re-labeled Pogoplug Mobile with a Jennic Zigbee card attached to the serial pins was overclocked to 1 GHz.by rayknight - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 1 year ago
Can you post the diff between versions that show the offending line of code? Perhaps that would shed some light on how to submit a pull request to the kernel to get the issue corrected. Rayby rayknight - Debian