Show all posts by user
Mele A1000/A2000/MK802/A10 tablet discussions
Re: Debian on Dell Kace M300 - 26 days ago
I've started to write a new installation procedure for this box. The simplest way is to install from inside stock OS. But now I realized that I never log into stock OS when the box is in a pristine condition. I skipped that and boot straight into my rootfs on USB. And later I just mounted the stock rootfs and changed the root password in its shadow file. So I don't know the stockby bodhi - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 29 days ago
> I ran into the wrong binaries in the headers > package issue when cross compiling. It's not > really a big deal, but did you find a solution or > did you just create the headers package on a > Kirkwood box? No, I have not looked into this issue. I rebuilt the Kirkwood kernel on an Armada 385 (armv7) box.by bodhi - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 29 days ago
I think JT is already aware of what Ray said. But this is the Kirkwood kernel, i.e. works all Kirkwood boxes that I supports here. I don't have a small target such as specific target for the Dockstar. You could take out things like sounds, dvb video. But even that does not make it significantly built faster. For me, I don't have a need for speed. When the build goes, it will beby bodhi - Debian
Re: Debian on Dell Kace M300 - 4 weeks ago
sudos, > Would you be willing to update the guide post so > it's up to date for mentioning the current rootfs > and current 2022-04 u-boot build further up this > page? Sure, I'll consolidate the instruction. I am getting a bit busy with day jobs, it will be a few days or a week from now.by bodhi - Debian
Re: Debian Security Advisory - 4 weeks ago
Update your dpkg. https://www.debian.org/security/2022/dsa-5147by bodhi - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 4 weeks ago
QuoteI removed all references to the LEDs from the dtb and I am able to control them via gpioset and /sys/class in both kernels, but not TxD/RxD. Maybe it has something to do with GPIO10/11 being used by the UART, but I even tried removing all references to the UART from the DTB and that didn't seem to help. OK. Remove the GPIO for LEDs allowed you to control them through /sys/class. So weby bodhi - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 4 weeks ago
Perhaps you can play with the new userspace tool. https://packages.debian.org/bullseye/gpiod QuotePackage: gpiod (1.6.2-1) Tools for interacting with Linux GPIO character device - binary libgpiod encapsulates the ioctl calls and data structures behind a straightforward API. This new character device interface guarantees all allocated resources are freed after closing the device file dby bodhi - Debian
Re: Help unbricking Synology DS411Slim - 4 weeks ago
Not sure about this behavior. But the 3.3V should not be connected. You could fry the serial port with the power connected to it. The power should come from the USB converter only. But there are garbage chars output to the log, so it was likely not damage. How about: restore the eeprom, connect serial console without the 3.3.V, just 3 wires and try: - swapping TXD and RXD - If you haveby bodhi - uBoot
Re: Can't control GPIO pins after update to kernel 5.17.4 - 4 weeks ago
renojim, > I hope I'm missing something simple. I've been > working for the last week to update my Dockstar > from kernel 4.8.3 to 5.17.4 and once I got past > not being able to build LKMs I now find that I > can't control GPIO10 (TxD) with the LKM or via > /sys/class/gpio/gpio10. Did it work in kernel 4.8.3? GPIO10 and 11 are undefined in the DTS, soby bodhi - Debian
Re: Help unbricking Synology DS411Slim - 4 weeks ago
> The box was in my parent's house before it was > bricked. Since my father bring it to me, I never > seen nothing on the serial output. That's what I was thinking. If this is the first time you connect the serial console to this box, then perhaps the connection is not good. Try checking the wires, swapping TX and RX. It is always better to have a connected serial consoby bodhi - uBoot
Re: Help unbricking Synology DS411Slim - 4 weeks ago
> After several tries, Several kwboot tries? > the behavior of the card has > changed: now the green LED is blinking very fast > and I can hear a tick-tick-tick... There is alway some hope of reviving the box if the LED is still blinking. If it is off and the board is silent then it is really dead. And did the serial console work (you've connected and see output) bby bodhi - uBoot
Re: Help unbricking Synology DS411Slim - 5 weeks ago
rclsilver, blinking blue light without any data on the console serial port (J1). Sounds like u-boot was corrupted. The kernel files rd.bin and zImage on flash might still be OK (but we'll know one way or the other, when you get to that point where you can see u-boot running). You can try to boot with UART using kwboot. See this post: https://forum.doozan.com/read.php?3,51739,519by bodhi - uBoot
Re: Executables in linux-headers deb pkg are x86-64 - 5 weeks ago
Give this a try. Purge it and reinstall with the new headers deb. dpkg --purge linux-headers-5.17.4-kirkwood-tld-1 dpkg -i linux-headers-5.17.4-kirkwood-tld-1_1.0_armel.deb https://forum.doozan.com/read.php?2,12096,12096#msg-12096 QuoteUpdated: apparently the kernel headers has some problem. So I've rebuilt it and uploaded to Dropbox. Please use this headers package instead if yoby bodhi - Debian
Re: Executables in linux-headers deb pkg are x86-64 - 5 weeks ago
I've rebuild the kernel headers. Will upload it shortly.by bodhi - Debian
Re: Executables in linux-headers deb pkg are x86-64 - 5 weeks ago
renojim, > > If this is intentional and I just need to > rebuild > > everything I'll continue down that path, I've verified what you saw. But I'm a bit short on time right now to dig deeper, please rebuild the binaries you need. Is that a few or a lot?by bodhi - Debian
Re: Executables in linux-headers deb pkg are x86-64 - 5 weeks ago
renojim, > If this is intentional and I just need to rebuild > everything I'll continue down that path, but if > not, the ARM executables would be nice to have in > the package. Not intentional! thanks for reporting this. Not sure why that could happen, though. It was built at the same time as linux-image-5.17.4-kirkwood-tld-1 in Linaro cross-compile environment.by bodhi - Debian
Re: [NSA325] I'm having trouble building the uInitrd - 5 weeks ago
> Now the above I've wrote between your edits, so > now I assume my questions answered ^_^J Cool :) glad you got the answer you need! There is better way to ensure the load addresses are OK. But that will be for another day in the future when I will release new u-boot version.by bodhi - Debian
Re: [NSA325] I'm having trouble building the uInitrd - 5 weeks ago
Dźwiedziu , Use 5.17.4-kirkwood-tld-1, interrupt serial console at count down > Hit any key to stop autoboot: And then set the load address of load_dtb_addr to 0x2c00000 and boot. setenv load_dtb_addr 0x2c00000 boot ========= I've just recall I already wrote this on the u-boot installation thread: QuoteB. Load addresses for large systems This u-boot was releby bodhi - Debian
Re: [NSA325] Is it dead or just sleeping? - 6 weeks ago
> [ 8.598956][ T1] VFS: Cannot open root > device "(null)" or unknown-block(0,0): error -6 > [ 8.680507][ T1] (driver?) > [ 8.688519][ T1] Kernel panic - not syncing: > VFS: Unable to mount root fs on > unknown-block(0,0) This error is just either the root device in the bootargs is wrong, or the USB rootfs partition does not have label rby bodhi - Debian
Re: Debian on Dell Kace M300 - 6 weeks ago
> I know in the E02 the kirkwood is bare, as > it is in the Pogo v4 as well. in the E02 just add > a heatsink that fits, and in the v4, you need to > get crafty to figure a way to take up the air gap > between the SoC and the steel weight on the bottom > of the casing. That provides ample thermal mass to > keep the 800MHz part cool enough to not > fall over on itselby bodhi - Debian
Re: Kernel update to Kernel linux-5.17.4-kirkwood-tld-1. - 6 weeks ago
> Why not. the point here is that at every kernel > update the mess inceases :) Yup :) But the kernel files must be in /boot for certain things to work, such as Debian version upgrade. So keep 2 versions and uninstall the rest. Example to uninstall a kernel version (any version except the one running). List them root@tldDebian:/boot# dpkg -l | grep linux-image ii linux-imagby bodhi - Debian
Re: [Solved] Ox820: gpio-keys-polled does not provide /dev/input/eventx - 6 weeks ago
miazza, Each box has a different LEDs skeme so if the questions are about NSA325, it should not be asked here (will be consfusing to go back and forth). Should be in this thread https://forum.doozan.com/read.php?2,32460,32467#msg-32467 You will see the examples about using esekeyd to control button. And how to set up the script to shoutdown.by bodhi - Debian
Re: Kernel update to Kernel linux-5.17.4-kirkwood-tld-1. - 6 weeks ago
You could also create a folder and move them there cd /boot mkdir -p kernel mv -i linux-image-*.deb *.tar *.bz2 ./kernelby bodhi - Debian
Re: Kernel update to Kernel linux-5.17.4-kirkwood-tld-1. - 6 weeks ago
miazza, > Thank you. I supposed it was like that but I > wanted to be sure. Yes, instruction to remove is there as a precaution when people install the kernel from a mainline rootfs. delete: > linux-dtb-5.17.4-kirkwood-tld-1.tar > linux-5.17.4-kirkwood-tld-1-bodhi.tar.bz2 But keep everything else, those are kernel files, in case you have to recreate the uImage and uInby bodhi - Debian
Re: [NSA325] Is it dead or just sleeping? - 6 weeks ago
Dźwiedziu, > Only > unset all the env variables and semi-manually set > them to the defaults, taken from > https://forum.doozan.com/read.php?3,12381 -> > uboot.2016.05-tld-1.environment.bodhi.tar. That's not a recommended approach. When you think the envs are all messed up, you can use the uEnv.txt to reload all default envs. See here: https://forum.doozan.cby bodhi - Debian
Re: Netgear Stora MS2000 and indicators - 7 weeks ago
macsneil, > I've tried the fix for the blue LED indicator > activity trigger and it works but I can't seem to > make it persistent across reboots. > /sys/class/leds/status:blue:activity_led/trigger > defaults back to heartbeat from none after > reboot. Did you add this to your /etc/rc.local (place it at the end before "exit 0"): echo none >by bodhi - Debian
Re: Debian on Dell Kace M300 - 7 weeks ago
sudos, Very nice mod! > Hopefully this little infopost finds someone else > well as the Armada chips are pretty much the only > SoCs in the kirkwood family I can find to have a > working thermal sensor that can be probed. The > others might have it but I've never seen a device > yet aside from this example where it has been made > visible and working. Theby bodhi - Debian
Re: Mail server pogoplug pro v3 - 7 weeks ago
> card from another pc to bring it back to live, it > used to be my main gamer but I built it in 2014 so > it is pretty much obsolete and I figured since I > refuse to part with it I may as well use it for > something useful. I see. Hard to part with something like that. I would keep it too. I have a box of floppy disks somewhere in the closet, in among them my first 8086 deby bodhi - Debian
Re: Mail server pogoplug pro v3 - 7 weeks ago
echowarrior108, > Operating System: Debian GNU/Linux 11 > KDE Plasma Version: 5.20.5 > KDE Frameworks Version: 5.78.0 > Qt Version: 5.15.2 > Kernel Version: 5.10.0-13-amd64 > OS Type: 64-bit > Processors: 6 × AMD Phenom(tm) II X6 1100T > Processor > Memory: 15.6 GiB of RAM > Graphics Processor: NVC1 All that horsepower for a mail server? wow! Sell itby bodhi - Debian