Show all posts by user
Mele A1000/A2000/MK802/A10 tablet discussions
Re: Problems booting Debian on 88f6283 - 22 days ago
QuoteCan confirm LED works correctly! Cool! that GPIOs 38 (red) and 39 (green). These 2 were easy to see in the patch. I did not think GPIO 45 is the right one. u-boot uses GPIO 48 and 47. u-boot + MPP45_GPIO, /* USB_IND */ + MPP46_GPIO, /* USB_RS_IND */ + MPP47_GPIO, /* RST_GE */ + MPP48_GPIO, /* RST_USB */ So let's try 46 next. If that does not work, we'll go baby bodhi - Debian
Re: Problems booting Debian on 88f6283 - 22 days ago
gt, This DTB has: - Use GPIO 45 for USB power. It seems odd that GPIO 48 did not work (u-boot use that to reset USB). But it's worth a try to see if 45 does anything. - Status LEDs should work now with green LED and red LED. When Linux finishes booting it should become solid green.by bodhi - Debian
Re: Problems booting Debian on 88f6283 - 23 days ago
gt, > Well, I transferred rootfs to ubfs on mtd, it > boots and works OK. Cool! > Bodhi, is it ok to ask to tinker with dtb a little > more? Usb devices are not powering up in linux, > and led flashes red uncontrollably. Sure. Let me modify and upload new DTB version.by bodhi - Debian
Re: Problems booting Debian on 88f6283 - 24 days ago
> Surprisingly, it works correct with > kirkwood-silverstore-hncn2.dtb. It is a coinincidence :) without looking at those, I think they are the same GPIO numbers.by bodhi - Debian
Re: Problems booting Debian on 88f6283 - 24 days ago
This DTB has: - Added USB power regulator - Removed the DIP switches Please try booting without USB hub.by bodhi - Debian
Re: Problems booting Debian on 88f6283 - 24 days ago
MPP 47 48 + MPP47_GPIO, /* RST_GE */ + MPP48_GPIO, /* RST_USB */ So my guess is 48 for USB power. 47 is for Ethernet. Will upload another DTB.by bodhi - Debian
Re: Problems booting Debian on 88f6283 - 24 days ago
Cool! USB is a bit harder. I could not guess the names they used in the patch. My guess is MPP45_GPIO but why the weird name! u-boot patch + MPP45_GPIO, /* USB_IND */ + MPP46_GPIO, /* USB_RS_IND */ + MPP47_GPIO, /* RST_GE */ + MPP48_GPIO, /* RST_USB */ Power up, interrupt serial console and md.l 0xF1010000 8 And then md.l 0xF1010100 1 md.l 0xF1010140 1 usb startby bodhi - Debian
Re: Problems booting Debian on 88f6283 - 24 days ago
Quoteeth0 worked inside debian, usb worked with hub ("[ 17.311402][ T1] Waiting for root device /dev/sda1..." when plugged directly) Cool! It has Ethernet implementation only. I want to make sure that we got that out of the way. Please try Ethernet port 1, both scenarios: 1. Unplug port 0 and plug the cable to 2nd port while Debian is running. 2. Reboot, and verify ethernetby bodhi - Debian
Re: Problems booting Debian on 88f6283 - 24 days ago
gt, Try this attached DTB. Power up, interrupt serial consolse and printenv bdinfo ping <your router IP> # for example, 192.168.0.1 And then boot the same way you did in the successful boot. And please post the entire serial console log.by bodhi - Debian
Re: Problems booting Debian on 88f6283 - 24 days ago
QuoteBTW, what is the exact name and model of this box? is it IP-Plug, by PromWad or they made this for a client? I see in the patch + * Promwad WTPlug Reference Board Setupby bodhi - Debian
Re: Problems booting Debian on 88f6283 - 24 days ago
gt, Even though the network was detected, the network link was never active. And the USB power hub is needed to boot then there was no power to the USB port. Both of these problems most likely due to the DTS that's good for Openblock A7 but something is missing or wrong for your box. Let me take a look at the patch. BTW, what is the exact name and model of this box? is it IP-Plug,by bodhi - Debian
Re: Problems booting Debian on 88f6283 - 25 days ago
gt, > Also I found a USB-hub with external power > supply. > Using it, I successfully booted to Debian USB! > Yay! Congrat! > But Ethernet ports are not working :( . They do > register link, but fail to receive anything, just > like OpenWRT images. Which DTB you are using? > Is there a way to create dtb from a patch that > makes workable kernel 3.1.by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 25 days ago
> As expected, flashing the latest stock firmware > didn’t fix or enable the uart :) PM the users on that working thread for mtd0 dump. They might not read new posts.by bodhi - Debian
Re: Problems booting Debian on 88f6283 - 25 days ago
The problem is related to the USB drives/ports. [ 12.405096][ T102] usb 1-1: New USB device found, idVendor=0000, idProduct=0000, bcdDevice= 0.00 [ 12.414052][ T102] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 12.422828][ T102] hub 1-1:1.0: USB hub found [ 12.427458][ T102] hub 1-1:1.0: 4 ports detected [ 12.744635][ T102] usb 1-1.3: new high-speedby bodhi - Debian
Re: revive Medion oxnas stg-212 - 25 days ago
alexinc, Try booting Debian. On another Linux box, use the kernel zImage in this tarball linux-5.4.210-oxnas-tld-1.bodhi.tar.bz2 and append the DTB. cp -a zImage-5.4.210-oxnas-tld-1 zImage.fdt cat dts/ox820-stg212.dtb >> zImage.fdt mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-5.4.210-oxnas-tld-1 -d zImage.fdt uImage And boot the same wayby bodhi - Rescue System
Re: Problems booting Debian on 88f6283 - 26 days ago
gt, Try these 2 tests: 1. Use different USB port if this box has more than one USB port. If that does not work, 2. Use Silverstore DTBby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 26 days ago
> I was thinking it was > because of the firmware and the chance it had not > enable by default Yes, it does not hurt to do that. But the chance is quite slim that was the reason. When the BootROM starts, u-boot is not running yet. The first few lines on console are from BootROM. QuoteBootROM - 1.73 Booting from NAND flashby bodhi - Debian
Re: Debian on Action Tech SG200 and MI424WR-rev-I - 26 days ago
8086k, My ActionTec MI424WR-rev-I has been put away in a closet. One of these days when nothing else going on, I'll boot it up again.by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 26 days ago
i5Js, > Perhaps I need to go to the orignal WD firmware? No, because the envs will not work. > > I will try to contact CyperPK or vzhilov and > let’s see if they can dump their u-boot. > Yes. Come back and I'll help you flashing it. It is best to have the dump for the entire mtd0 (5MB). > Thanks again for all your time and advices with my > issue.by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 26 days ago
> And then if you decide to flash that u-boot > without serial console, you must get vzhilov or > CyperPK or others to dump the envs image. And then > flash both u-boot image and the envs image in the > same session. Or if they can dump their mtd0 (which include the envs), then you can also flash the whole mtd0 file at once.by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 26 days ago
i5Js, Quotenew uImage, old RamDisk in USB1 + USB2 attached -> Doesn't boot new uImage, new RamDisk in USB1 + USB2 attached -> Doesn't boot new uImage, new RamDisk, renamed as uInitrd in USB1 + USB2 attached ->It boots but in WD recovery, no ssh access just web to upload a firmware new uImage, old RamDisk in USB1+hardrive with rootfs -> Doesn't boot new uImaby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 27 days ago
> Should I rename the uInitrd to uRamDrive ? No, the Ramdisk for booting is stock initrd on the FAT USB. The new rootfs initrd is quite larger than stock, so pretty good chance is that it wont boot. But if the new kernel+old RamDisk combo does not boot, then try the uInitrd anyway (in this case, yes, copy it to uRamdisk).by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 27 days ago
You can also do it in stock OS. which tar which mkimageby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 27 days ago
i5Js, > Question: can I do it from a Linux VM using > crosscompile? No need to cross compile anything. The rootfs creation steps are universal.by bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 27 days ago
i5Js , Follow the instruction and create the released rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 on a different USB drive. You need to do Step 3 and use armada-385-wd-ex2-ultra.dtb Quote3. Create uImage with DTB appended. I am using the Zyxel NAS326 as an example here. Please replace armada-380-zyxel-nas326.dtb below with the appropriate DTB name for your box. cd /media/sdby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 27 days ago
> So, just to understand, no matter I can compile > the kernel, an uImage and a uRamDisk, it won't > work, right? Right, it is quite risky to flash the kernel files to NAND without serial console. You would need to have some way to boot it from RAM or USB first. However, you mentioned that > New chapter, I have had lucky and the box has > booted up from a USB keyby bodhi - Debian
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 27 days ago
QuoteLinux version 3.10.70 (root@build64) (gcc version 4.9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #5 SMP Tue Dec 27 22:04:20 +05 2016 .... Kernel command line: console=ttyS0,115200 earlyprintk root=/dev/ram console=ttyS0,115200 You are booting with stock kernel and rootfs on NAND. And the envs cannot be listed without serial console. So we cannot adjust the envs to boot USB rootby bodhi - Debian
Re: revive Medion oxnas stg-212 - 27 days ago
alexinc, Boot with tftp. Download: https://downloads.openwrt.org/releases/22.03.0-rc6/targets/oxnas/ox820/openwrt-22.03.0-rc6-oxnas-ox820-mitrastar_stg-212-initramfs-uImage And place it in the /tftproot Power up, interrupt serial console and setenv mtdparts 'mtdparts=41000000.nand:14m(boot),-(ubi)' setenv bootargs 'console=ttyS0,115200 $mtdparts' tftpbootby bodhi - Rescue System
Re: WD My Cloud Ex2: Kernel v5.10 with Debian Bullseye and OMV - 27 days ago
> New chapter, I have had lucky and the box has > booted up from a USB key. Do you have a serial bootlog? if serial console still not working then dmesg mount cat /proc/mtd > > So I guess I would be able to flash an modified > uImage and uRamdisk to work with the uBoot from > the command line, right? But which one could I > use? > Why not using theby bodhi - Debian
Re: Debian on Dell Wyse T10 / T50 - 28 days ago
wildhem, > Nov 2 15:29:53 debian user.warn kernel: [ > 3.239507][ T1] dove-pinctrl f10d0200.pin-ctrl: > falling back to hardcoded PMU resource > Nov 2 15:29:53 debian user.warn kernel: [ > 3.239847][ T1] dove-pinctrl f10d0200.pin-ctrl: > : Missing pinctrl regs in DTB. > Please update your firmware. > Nov 2 15:29:53 debian user.info kernel: [ &gby bodhi - Debian