Show all posts by user
Bootloader tips and tricks
Re: Use front USB connector as Ethernet service port with DHCP - Yesterday
For remote serial access I have heard that one of these makes a great solution. I've ordered a few to try and will post results when I've been able to test.by rayknight - Debian
Re: Checkpoint L-50 - 2 days ago
Gravelrash Wrote: ------------------------------------------------------- > @rayknight > Are you aware of any pinout/connector on the board > that will allow direct access to the uboot output > on the standard firmware setup? Serial access is available from RJ-45 Console port at 115200, 8N1. I just used a Cisco rollover to USB cable that I've used with many other devices wby rayknight - Debian
Re: Checkpoint L-50 - 2 days ago
DTS was submitted to mainline kernel. You can also find high res photos of it I submitted at WikiDevi.by rayknight - Debian
Re: Checkpoint L-50 - 6 days ago
All versions are supported the L-50 has no wireless and no ADSL annex, the L-50W has 802.11bgn WiFi via an Atheros AR9287 PCIe based card and the L-50WD adds an ADSL annex board to that. There may be an L-50D, but I haven't seen one. The ADSL annex board is currently unsupported. I never did get around to testing the ExpressCard/34 slot to see what it would support. Rayby rayknight - Debian
Re: New Computer Parts - 11 days ago
I frequently get items from MicroCenter, but they have a location near me. Not sure what their shipping policy is, but you may want to see if it works for you. I've been using them for more than 25 years.by rayknight - Off-Topic
Re: Cubox 510 1st gen kirkwood + debian 11 - 28 days ago
CUBOX_K Wrote: ------------------------------------------------------- > Greetings. I didn’t manage to get it to work > last time, today I returned to this issue again. > Debian 11, kernel 6.0.0. What exactly do I have to > do to get the sound to work? I would be grateful > for help I just discovered that most of the dove devices with dts in mainline kernel are missing enaby rayknight - Debian
Re: Cubox 510 1st gen kirkwood + debian 11 - 30 days ago
I have the Cubox and two other 88AP510 based devices (GlobalScale D2Plug and GlobalScale D3) and audio doesn't appear to work on any of them. I suspect that there is something missing or mis-configured in the DTS or the kernel config is missing 1 or more relevant defines. I haven't had the time lately to dig into it and likely won't until late March!by rayknight - Debian
Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104 - 6 weeks ago
From my earlier linked article QuoteNow that the hard part — configuring the kernel and the device tree — is done, we can very easily print stuff on the screen by just writing to the /dev/lcd file. Rayby rayknight - Displays
Re: Build-in 2 by 16 character front display on Netgear ReadyNAS RN104 - 6 weeks ago
You might want to take a look at HD44780 LCD I²C screen using Linux mainline charlcd driver. That appears to have enough information to be able to determine if lcd4linux already support the device and to add support to lcd4llinux if it does not. Rayby rayknight - Displays
U-Boot now supports booting Linux from HTTP - 7 weeks ago
Recent article CNX Software announces that Linaro has added support for booting Linux from HTTP to U-Boot and apparently HTTPS support is also in the works. Booting would be as simple as: setenv autoload 0;dhcp wget $loadaddr 192.168.0.1:~/vmlinuz Rayby rayknight - uBoot
Re: Debian on Dell Wyse T10 / T50 - 7 weeks ago
I mentioned this before in this thread, but I've seen further posting that has me convinced that some people are confused about which Dell device they have. The Dell Wyse 3010 (sometimes listed as TX0, T10 or T50) has a single DVI-I video output and contains the Marvell Dove 88AP510 SOC, the Dell Wyse 3020 (sometimes listed as TX0D, T10D or T20D) has dual DVI-I and DVI-D video output and coby rayknight - Debian
Re: Install debian on Netgear stora - 2 months ago
demonside Wrote: ------------------------------------------------------- > Failed to reload daemon: Refusing to reload, not > enough space available on /run/systemd. Currently, > 10.4M are free, but a safety buffer of 16.0M is > enforced. > Failed to reload daemon: Refusing to reload, not > enough space available on /run/systemd. Currently, > 10.4M are free, but a safby rayknight - Debian
Re: GTI Mirabox and Netgear RN120 (Armada 370) Installation & Kernel Upgrade (Linux-5.19.2) - 2 months ago
bodhi, Not a problem for me a I usually build my own kernels using your patches. Just thought it would be helpful to have the config options there for any current or future users of your kernel packages who might be using with that device. Rayby rayknight - Debian
Re: GTI Mirabox and Netgear RN120 (Armada 370) Installation & Kernel Upgrade (Linux-5.19.2) - 2 months ago
bodhi, Those options would also apply to the Kirkwood kernel for NETGEAR ReadyNAS NV+ v2 as well. Rayby rayknight - Debian
Re: Promise Apollo Cloud - Armada 385 - 2 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 - 2 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 - 2 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 - 2 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 - 2 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 - 3 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 - 3 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 - 3 months ago
Attached is the result of the above dd command. Rayby rayknight - Debian
Re: Mainline Linux on GlobalScale D2Plug - 3 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 - 3 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 - 3 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 - 3 months ago
__ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__|by rayknight - Debian
Re: Mainline Linux on GlobalScale D2Plug - 3 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 - 3 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 - 4 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 - 4 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