Show all posts by user
Mele A1000/A2000/MK802/A10 tablet discussions
Re: Linux Kernel 5.4.101 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 5 weeks ago
Kernel linux-5.4.210-oxnas-tld-1 package was uploaded. See 1st post for download link. NOTE: If you had some problem setting envs in Debian with previous kernel version, see Step 6b in this kernel installtion for possible explanation. And please create a new thread for questions or problem in installation.by bodhi - Debian
Re: Zyxel NAS326 Installation Instruction - 5 weeks ago
robdejonge, Yes, currently in bullseye for all MVEBU boxes (Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2) See the main kernel and rootfs release thread: https://forum.doozan.com/read.php?2,32146 The instruction in this thread 1st post was last updated with the buster rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2. Replace that with Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.by bodhi - Debian
Re: Linux Kernel cleanup question - 5 weeks ago
> Ah, I see what you meant now! I misunderstood-- I > initially thought that the kernel updates directly > reflected or corresponded to respective Debian > kernels (Debian 10, 11, etc.). So, the rootfs is > the base that ultimately determines the kernel > version and supersedes any of the updates. Yes, it's difference from running a mainline Debian distribution, whby bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
bluzfanmr1, Let's wait for the next kernel release. And then we go from there.by bodhi - Debian
Re: Linux Kernel cleanup question - 5 weeks ago
Here is the Debian buster rootfs in the release thread. The link is OK. https://forum.doozan.com/read.php?2,12096 Quote ======================================================================= Updated 25 Aug 2019: Basic Debian buster Kirkwood rootfs for most Kirwood plugs: - tarball size: 209M - install size: 536M - The init system used in this rootfs is sysvinit . To boot wiby bodhi - Debian
Re: Linux Kernel cleanup question - 5 weeks ago
dumdedumda, > Little confused here. Just checked my Pogo V4 with > a freshly installed copy of the latest rootfs (26 > Sept 2021 > Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2) > and it is showing Debian 11 (Bullseye), and not 10 > (Buster). Also, the release page shows "Updated 26 > Sept 2021:Basic Debian bullseye Kirkwood rootfs > for most Kirwood pluby bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
So perhaps boot back to 4.14.x and remove netconsole from /etc/initram-tools/modules, too. And then reinstall 5.4.179.by bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
> I have an Asus Merlin router and use it as the > netconsole server box. I can switch that to > another box if that might help? I think netconsole server should be another box. The OXNAS network driver is picky that it could wait for carrier a long long time.by bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
Please see my recent post above.by bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
[ 11.254469][ T134] netpoll: netconsole: local IPv4 address 10.1.1.196 [ 11.261071][ T134] netpoll: netconsole: interface 'eth0' [ 11.266449][ T134] netpoll: netconsole: remote port 6666 [ 11.271869][ T134] netpoll: netconsole: remote IPv4 address 10.1.1.1 That does not look right. ipaddr=10.1.1.196 serverip=10.1.1.1 The serverip looks like your router IP, nby bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
OK I've updated the post above: https://forum.doozan.com/read.php?2,132799,132846#msg-132846 Please try.by bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
I've booted up my Pogo Pro and not seeing the problem (it booted OK into Debian) but I am seeing in the boot log something I don't like. So stay tune.by bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
bluzfanmr1, Since you have recreated the uImage, boot again with serial console. Interrupt u-boot countdown, and turn off netconsole. setenv preboot setenv mtdparts 'mtdparts=41000000.nand-controller:14m(boot),-(data)' saveenv and then reset Let it boot automatically. Please the entire serial console log here. ======= BTW, I'm about to release another staby bodhi - Debian
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
Here is the new version. Please kwboot it and scsi reset scsi info scsi part Update: Re-uploaded the u-boot image.by bodhi - uBoot
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
Do you have all 4 HDDS in the slots? These 2 are internal SATA ports. So I would exepect the "sata init" would find them. If these 2 ports have HDD attached then the u-boot failed to power them up. Marvell Serial ATA Adapter Integrated Sata device found [0 0 0]: Enable DMA mode (6) Device 0 @ 0 0: Model: ST6000NM021A-2R7101 Firm: SN03 Ser#:by bodhi - uBoot
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
Correct! there are 2 different controllers. I would exepct to see PCI bus handling 2 ports, and internal SATA handling 2 ports. Ah! SCSI: AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl IDE mode So I recall that you did "scsi reset" in stock u-boot to see the HDDs?by bodhi - uBoot
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
What about these output? sata init sata info sata part And please post the entire serial log (during uboot booting).by bodhi - uBoot
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
QuoteIm pretty sure I see the same in stock u-boot too for ata3 and 4 but they are detected and working there Let see if the version I just uploaded above is better!by bodhi - uBoot
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
Here is the new test version. This has substantial change, so cross your finger :) uboot.2022.10-rc3-tld-0.2.ix4_200d.mtd0.kwb. Try kwboot and sata init sata info sata partby bodhi - uBoot
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
CodeJACK, Very cool! Looks like everything is working as it should. You have only 2 HDDs in the box, right? I'll upload another u-boot version for testing shortly.by bodhi - uBoot
Re: Linux Kernel cleanup question - 5 weeks ago
dumdedumda , > Additionally, what's the latest version of Debian > Buster for Kirkwood devices? > Would that be > linux-5.13.6-kirkwood-tld-1 (04 Aug 2021)? No, the latest rootfs is Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (Buster). And it has kernel linux-5.13.6-kirkwood-tld-1 already installed on it. This rootfs can be used for any Kirkwood box. And thenby bodhi - Debian
Re: Pogoplug Pro Issues - Any Linux Kernel 5 and Up - 5 weeks ago
bluzfanmr1, > [ 15.359731][ T134] netpoll: netconsole: > timeout waiting for carrier That sounds familiar. And your boot log also show: - a random MAC address (36:5d:d7:18:18:93) - The DTB is probably appended to the uImage 1. Boot again and in serial console, printenv ethaddr See if it is the correct MAC address (no need to print it out) of this box (check the case stiby bodhi - Debian
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
CodeJACK, QuoteFailed to load '/boot/uImage.orig' So when you installed 5.18.6-kirkwood-tld-1, you did not save the uImage.orig as instructed. https://forum.doozan.com/read.php?2,12096 Quote4b. Boot with DTB file embedded in the kernel image.Again, this step 4b is for stock U-Boot only. mv uImage uImage.orig Boot with stock u-boot into Debian and cd /boot ls -lartby bodhi - uBoot
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
> sata init, part and info do not return anything. > > They are currently GPT, with a single ext4 primary > partition on each. OK, more to configure, then. In the mean time, since you have booted stock u-boot to the new USB Debian rootfs, you can use that same USB rootfs with this new u-boot. But the envs will be a bit different. setenv set_bootargs 'setenv booby bodhi - uBoot
Re: Zyxel NSA325 no IP - 5 weeks ago
> Wait.... is used dd to make an image of the usb > stick and mounted that. It worked,,, I can browse > the files now from the image! > > Just copying it over now to a new usb stick. Will > try booting the nas tomorrow. Cool! When I have time I will beef up that post about USB rootfs. There are more things you can do to avoid wearing out flash drives, but the log isby bodhi - Debian
Re: OOM Killer in action against squeezelite on Seagate Dockstar - 5 weeks ago
Paolo, Look like we were posting at the same time, please see above!by bodhi - Debian
Re: Iomega ix4-200d U-boot needed - 5 weeks ago
> There is disks now installed to all slots but no > partitions on them. OK, we need a real partition to check. But also do this to see if the HDD is spun up. sata init sata info > > I'll reboot shortly and get the pinmux command but > I dont see it in the list of available commands > via 'help' OK. Look like I need to reconfigure it.by bodhi - uBoot
Re: OOM Killer in action against squeezelite on Seagate Dockstar - 5 weeks ago
Hi Paolo, Unfortunately I have not used or looked at squeezelite for many years, so don't have better suggestion other than some observation. The current Debian kernel 5.18.6-kirkwood-tld-1 is configured with CONFIG_IOSCHED_BFQ=y CONFIG_BFQ_GROUP_IOSCHED=y BFQ is a remedy for the OOM killer stepping in when there are large swap space. So if squeezelite is not triggering OOM byby bodhi - Debian
Re: Zyxel NSA325 no IP - 5 weeks ago
Bobby, Sounds like this drive is going bad. Try using a different flash drive. Can you mount it? it will be read-only but you will be able to read from it. If you have installed a lot of packages, then copy the rootfs over. If not, then create a fresh Debian rootfs. How to copy using tar (you can also use cp): https://forum.doozan.com/read.php?2,12096,24034#msg-24034 You must be roby bodhi - Debian
Re: OOM Killer in action against squeezelite on Seagate Dockstar - 5 weeks ago
Paolo, Have you tried running with sysvinit? ie. temporarily remove init=systemd parameter from the bootargs.by bodhi - Debian