Show all posts by user
Mele A1000/A2000/MK802/A10 tablet discussions
Re: HowTo: OpenWrt on Kirkwood boxes - 14 days ago
Everything looks OK for Debian, but perhaps OpenWrt still relies on archNumber. Interupt serial/net console at count down, and setenv arcNumber 3960 setenv machid f78 And continue installation. If it works, I'll need to revise the u-boot installation instruction to remind users of this.by bodhi - Rescue System
Re: Stuck in initramfs Pogoplug V2 - 14 days ago
camstar, This env is wrong: mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) From the look of your serial boot log, you have netconsle enabled. So you need to run netconsole on another terminal. And then when you see it is pinging on serial console Using egiga0 device host 192.168.1.212 is alive Go to the netconsole terminal, you will see the count down, and can interruby bodhi - Debian
Re: HowTo: OpenWrt on Kirkwood boxes - 14 days ago
happydiy, > Got the following error, somehow, messed up with > Pogoplug E02 env setup > > Sun Jun 12 17:49:29 UTC 2022 upgrade: Device > cloudengines,pogoe02 not supported by this image > Sun Jun 12 17:49:29 UTC 2022 upgrade: Supported > devices: cloudengines,pogoplugv4 > Image check failed. > Power up, interrupt serial console and ver printenvby bodhi - Rescue System
Re: HowTo unbrick? / Pogoplug E02 /Brick after install Squeeze / - 15 days ago
> I guess he/she wants an usb-ttl adapter to get > serial console? Ah :) in that case, any CP2102 adapter would work. Like this one, https://www.amazon.com/HiLetgo-CP2102-Converter-Adapter-Downloader/dp/B00LODGRV8 But really, you'd need to try them. It's low cost (~6 USD and fast shipping). Waiting for one coming from China costs 2-3 USD would take 2-3 weeks.by bodhi - Debian
Re: HowTo: OpenWrt on Kirkwood boxes - 15 days ago
For Pogo V4 the following change should be done for the instruction in the 1st post. Quote1. Modify uBoot variables First, we need to boot the box to debian, log in and then do the following: fw_setenv mtdparts 'mtdparts=orion_nand:0x200000@0x0(u-boot),-@0x100000(ubi)' This is needed for future u-boot upgrade. Since my released u-boot defines the mtd0 as 2MB (same as stocby bodhi - Rescue System
Re: HowTo unbrick? / Pogoplug E02 /Brick after install Squeeze / - 15 days ago
happydiy, > Can you recommend any USB adapter from Amazon to > unbrick Pogoplug E02? For Pogo E02, you don't need any adapter, just use a Sandisk brand, USB 2.0 thumb drive. If you meant a USB hub, then it's depending on which USB drive you will plug in the hub. If you have a USB 3.0 thumb drive and to want use it with the Pogo E02, it's best to use a USB 3.0 hub (iby bodhi - Debian
Re: HowTo: OpenWrt on Kirkwood boxes - 15 days ago
happydiy, > To confirm, for E02, the following has to be the > exact same > > fw_setenv mtdparts > 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)' > fw_setenv partition 'nand0,0' > fw_setenv set_bootargs_lede 'setenv bootargs > console=ttyS0,115200 $mtdparts' > fw_setenv bootcmd_lede 'run set_bootargs_lede; ubiby bodhi - Rescue System
Re: HowTo: OpenWrt on Kirkwood boxes - 15 days ago
happydiy, > Comparing the new envs > fw_setenv mtdparts > 'mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)' > fw_setenv partition 'nand0,0' > fw_setenv set_bootargs_lede 'setenv bootargs > console=ttyS0,115200 $mtdparts' > fw_setenv bootcmd_lede 'run set_bootargs_lede; ubi > part ubi; ubi read 0x800000 kernel; bootm &gby bodhi - Rescue System
Re: No mtd block devices under Linux Kernel 5.17.4 Kirkwood - 15 days ago
Hi Schnee, [ T159] mtdblock: MTD device 'u-boot' is NAND, please consider using UBI block devices instead. That's OK. Only a warning to recommend people to move on to UBIFS, instead of JFFS2 (the old default).by bodhi - Debian
Re: No mtd block devices under Linux Kernel 5.17.4 Kirkwood - 15 days ago
Hi Schnee, The MTD block was reconfigured to loadable module. It has been giving misleading scary messages for some boxes, so I decided to change it to loadable module. QuoteKernel linux-5.16.5-kirkwood-tld-1 package has been uploaded. The following features were added/updated: - General kernel upgrade - Add supports for CTera C200 V1 box. - Move MTD block devices to loadable moduleby bodhi - Debian
Re: Debian Security Advisory - 16 days ago
Quote- ------------------------------------------------------------------------- Debian Security Advisory DSA-5160-1 security@debian.org https://www.debian.org/security/ Salvatore Bonaccorso June 10, 2022 https://www.debian.org/security/faq - ------------------------------------------------------------------------- Packageby bodhi - Debian
Re: Any notable rugged USB flash drives? Even wear leveling if relevant. - 16 days ago
Joey, QuoteSo far it's looking like a Sandisk USB 3.1 stick @ 128 GB, getting closer. So this way those occasional dongle requests aren't tying up faster buses in the event I use an adapter to plug 3.1 into a USB 2.0 port. That would keep that situation down to the 480kbps even on a faster machine. A reminder. Use a USB 3 hub in this situation. Most controller in USB 3 hub (poweredby bodhi - Off-Topic
Re: Certificate Problems on 5.16.5 - 20 days ago
This rootfs is running with Sysvinit. I mentioned it in the rootfs release instruction. QuoteTo boot with systemd, add parameter init=/bin/systemd to your u-boot env bootargs (beware that in later Debian distribution, the location of systemd binary might have changed). - For example, fw_setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdpaby bodhi - Debian
Re: Certificate Problems on 5.16.5 - 20 days ago
Hey Marcus, That 10.12 is a bit old. It is oldstable distribution, Debian stable is 11.x now. I don't know for sure if your particular problem will be resolved by upgrading, but it's worth doing. You dont' want to run old distribution because there are security problem that have been fixed in new Debian stable. I would upgrade the distribution. But make sure you do a back upby bodhi - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 21 days ago
The include chain: kirkwood-dockstar.dts --> kirkwood-6281.dts --> kirkwood.dtsi Try commenting out these UART pins defintion /* * Default UART pinctrl setting without RTS/CTS, * overwrite marvell,pins on board level if required. */ pmx_uart0: pmx-uart0 {by bodhi - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 21 days ago
So your serial console would have problem if you use GPIO 10 and 11 for other purpose.by bodhi - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 21 days ago
renojim, I did not pay attention before about what you did. I read the previous posts now. > TxD/RxD are the easiest > GPIO pins to access on the Dockstar, so that's why > I used them. Everything in /sys/class acts as if > it's working, so I'm wondering if some other GPIOs > are getting mapped to 10 and 11. The pins were defined: kirkwood.dtsiby bodhi - Debian
Re: Can't control GPIO pins after update to kernel 5.17.4 - 21 days ago
QuoteI figured out why this only affects the first bank of GPIOs. The second bank (MPP32-49) is already configured to have every pin set as a GPIO. The pin ranges list for that bank is also empty, so this procedure accomplishes nothing for that bank either. I love how this routine doesn't return any error. Welcome to the club :) you'll run into code like that very often when you playby bodhi - Debian
Re: Certificate Problems on 5.16.5 - 21 days ago
Hi Marcus, What version you are running exactly? uname -a cat /etc/debian_version Have you updated Debian lately? apt-get update apt-get upgrade Problem like that is usually related to Debian distribution, not likely a kernel version issue.by bodhi - Debian
Re: Debian on Dell Kace M300 - 23 days ago
> I'm not the > first to do this sort of screw-up given my friend > had the same issue, and I definitely won't be the > last. better I have the week-long headache about > this now and save someone else from throwing their > M300 across the room later :D Not that drastic :) since this box can be kwboot. I would use that to boot the system, and use uEnv.txt to moby bodhi - Debian
Re: Debian on Dell Kace M300 - 23 days ago
> Hardware protection mode means the flash as a > whole, all 100% of it was locked down and will not > accept writes no matter what and would not take > unlocking commands from the uboot command line no > matter how hard you tried... Flashing stock uboot > would have been impossible as it was software > write protected and then hardware write protected > over it. Wiby bodhi - Debian
Re: Debian on Dell Kace M300 - 23 days ago
sudos, I'm glad you guys solved your problem! After seeing all that impressive works and technical know-hows, I feel bad to post this observation :) you could have just flashed stock u-boot back, start fresh, and solve this problem in an easier way. I think I've mentioned this before in my previous post. Most of the time, the KISS principle is the best method.by bodhi - Debian
Re: Debian on Dell Kace M300 - 24 days ago
Here is the info on my 2nd M300 box. [ 0.000000][ T0] Linux version 5.17.1-kirkwood-tld-1 (root@tldDebianVM) (arm-linux-gnueabi-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1.0 PREEMPT Fri Apr 1 16:17:12 PDT 2022 root@m300:~# cat /proc/cmdline console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:0x7f000@0(uboot),0x1000@0x7f000(uby bodhi - Debian
Re: Debian on Dell Kace M300 - 24 days ago
> except on both of my kace boxes Quite strange. renojim and I can set the envs with fw_setenv without problem. Let me gather and list all the necessary settings so you can compare with. > doing some more reading I did come across a > stackoverflow post of someone saying they could > manipulate the serial NOR flash (what we have here > with the macronix part in the M300) bby bodhi - Debian
Re: Debian on Dell Kace M300 - 24 days ago
> sudos, I just checked on my M300 with U-Boot > 2022.04-tld-1 (Mar 20 2022 - 18:15:15 -0700), > Kernel 5.16.5, and Bullseye (11.2) and I can set > environment variables and they stick after a power > cycle. Thanks! that answered sudos question. Here is what I think happened for the problem with changing envs in Debian, even with new u-boot installed. This box SPI flasby bodhi - Debian
Re: Debian on Dell Kace M300 - 25 days ago
Yes. I know what's going on there. It's all because the SPI flash was protected initially (Dell engineers are too clever by half). Will get back to this thread and explain in more details. In a nutshell, to start fresh we can always flash stock u-boot back and from there everything should be like we expect it to be.by bodhi - Debian
Re: Debian on Dell Kace M300 - 25 days ago
bodhi Wrote: ------------------------------------------------------- > daviddyer Wrote: > ------------------------------------------------------- > > I guess we can skip this ....I don't think > anyone > > will use that box with the original 16GB "sd". > So > > he / she will need to remove the old drive and > he > > / she needs to opby bodhi - Debian
Re: Debian on Dell Kace M300 - 25 days ago
> yeah I get that, the problem is that he has the > new uboot, but old envs. To recover from this problem, use uEnv.txt capability. The file uboot.2022.04-tld-1.m300.environment is the envs listing that I used in creating the uboot.2022.04-tld-1.m300.environment.4K.img. This can be used as uEnv.txt. Moun your USB rootfs on another Linux box. Copy the uboot.2022.04-tld-1.m300.envby bodhi - Debian
Re: Debian on Dell Kace M300 - 25 days ago
> not a single soul knows, it was hard coded onto a > USB key that is lost to the ages. When you can log innto stock OS, you are on the rootfs in the internal SSD. > as defined in the old guide. but yet the pogo E02 > config I have lists /dev/mtd0 as the defined MTD > device. That's really apple and orange. Pogo E02 is a completely different beast (each Kirkwood plby bodhi - Debian
Re: Debian on Dell Kace M300 - 25 days ago
daviddyer Wrote: ------------------------------------------------------- > I guess we can skip this ....I don't think anyone > will use that box with the original 16GB "sd". So > he / she will need to remove the old drive and he > / she needs to open the case anyway.. When he / > she opens the case, then booting with uart or > changing shadowed password caby bodhi - Debian