Hi everybody, Like million users around the world, I'm using the best media player ever :) But lately, this World News Live plugin (my favorite) has been mostly non-functioning: Forum: XBMC/Kodi World News Live Repo: WNL repository - k3oni WNL repository - moneymaker If anybody who is good with Python, and interested in internet media streaming, please help. I'd really apby bodhi - Off-Topic
pocket, BTW, I think we've covered the kernel/rootfs installation topic at this point. Any other problem/questions, you should start a new Debian thread!by bodhi - Debian
pocket Wrote: ------------------------------------------------------- > bodhi > > i have made new dist-upgrade he found 189 packages > do upgrade after this is recomend to install again > the sysvinit?? > Yes, do this after the first dist-upgrade to jessie. When in doubt, you can do it again, no problem. > i have remove the older kernell and seems to be ok &gby bodhi - Debian
As I've mentioned, the 3.14 and 3.16 rootfs might not work because of missing envs. If you can't get it boot then try 3.18 rootfs. If neither works then serial console will solve it.by bodhi - uBoot
Jean, > But what I really want to do is > to install Debian on my new USB stick, so that I > can have many more space for all the stuffs I > need. What are the steps I need to follow in order > to achieve a working installation of the latest > Debian release on my Dockstar ? The only thing you need to do is to create the USB rootfs following instruction for the versioby bodhi - Debian
pengu, > but there is another problem, wich rises now: > > Is there something wrong with the USB 3.0 port? > > when connecting different usb sticks when running > debian, the rootfs will go away after a while, > only reboot helps ;-( Did you look at the sys log for clues when this happened? I'd not be too surpirsed to see certain USB 3.0 drive cause some kby bodhi - Debian
pocket , Correct. Purge all others but keep the current kernel. > i have update the sources list with the jeesie > sources and have run the command They look OK. But the sysvinit reinstall should be after the dist-upgrade, not before Remember to always check your uImage and uInitrd after massive upgrade like this.by bodhi - Debian
After you're all done, you might want to remove all old kernels so that they won't interfer with future upgrade. dpkg -l | grep linux-image and then use dpkg --purge to purge each one.by bodhi - Debian
Also need to regenerate uImage for 4.1.0, too. Update: no I was mistaken. Look like it is your appended DTB uImage, so it is OK.by bodhi - Debian
You need to regenerate uInitrd for 4.1.0 -rw-r--r-- 1 root root 5409997 Aug 4 23:16 uInitrd -rw-r--r-- 1 root root 5743803 Aug 6 09:44 initrd.img-4.1.0-kirkwood-tld-1by bodhi - Debian
Did you check your initramfs whether it was regenerated? cd /boot ls -lart See if you uInitrd is newer than initramfs. If it is then do a few syncs and reboot. Also doublecheck uImage, it should be newer then vmlinuz.by bodhi - Debian
pocket, > root@debian:/boot# apt-get install sysvinit-core > sysvinit sysvinit-utils You only need to do this after upgrading to jessie.by bodhi - Debian
bobafetthotmail, I've released a new u-boot for NSA325. It solved all little problems that have been nagging us.by bodhi - Debian
pocket, Is the source in /etc/apt/sources.list pointing to jessie now? After apt-get update apt-get dist-upgrade Try apt-get update apt-get install sysvinit-core sysvinit sysvinit-utilsby bodhi - Debian
Good work osa :) I was able to bring the link up fine in the new kernel after a shutdown. I'm going to add either kernel config options (or device tree node parsing) to execute this PHY fixup only in Zyxel boxes with this Ethernet 88E1318/S chip, and then release new kernel version tld-2. Would you like to look into moving it to the PHY subsystem? pls let me know either way!by bodhi - Debian
newhope, You don't need to select anything regarding system type. It's already done in the released config file in the tarball. You can build using the exact same config that I have. And then later, add in whaterver you need using make menuconfig.by bodhi - Debian
osa, > and general patch should detect model ( or maybe > this init is general for all zyxel's boxes)? > Also port_init part can be common for zyxel's > Do other supported boxes use the same network > chip? This patch can affect them Yes, it will affect them, so we have to do the "#ifdef CONFIG_NSA3xx" to wrap the code.by bodhi - Debian
Thanks osa! The patch looks like it will work. I'll rebuild with it and let you know. BTW, this should be a temporary patch. I think eventually we should find a good place for this code in the PHY subsystem (linux-4.1/drivers/net/phy), if it's possible to do that.by bodhi - Debian
pocket, It looks reasonable. Since the current Debian stable is jessie, wheezy is already old, that's why there are kept back packages. You could choose to run with wheezy for a while, or choose to upgrade to jessie right away. However, upgrading to jessie will move your rootfs to systemd, and that is sometime troublesome. I would recommend that if you upgrade to jessie, then put it bby bodhi - Debian
Your kernel was very old. So the apt source list is probably squeeze. cat /etc/apt/sources.list Change source to wheezy and try again. But before you do that: 1. Make sure you have a backup (clone the USB drive to another drive). 2. And because you can't set the env for booting with DTB. You must append the DTB to uImage using step 4b. And use kirkwood-goflexhome.dtb to do that.by bodhi - Debian
Hi pbg4, > thermal@10078 { > compatible = > "marvell,kirkwood-thermal"; > reg = <0x10078 0x4>; > status = "okay"; > }; I've briefly gave it a shot and it does not seem to work. I've recompiled a new kernel with modified config and DTS using this latest DTS patch: http://lists.infradead.oby bodhi - Debian
I've uploaded the Zyxel NSA320 u-boot-2014.07-tld-4 image. Please see 1st post for download link.by bodhi - uBoot
Thanks for jumping in to help, gray! There is small possibility that 3.14 or 3.16 will not work in this case (some envs are missing). So I played it safe and recommended 3.18 rootfs :) But it's true, I always recommend 3.16 rootfs because it is simpler. Edit: typoby bodhi - uBoot
Please reread the installation instruction. This is not a command to execute: /dev/sde1 / ext2 noatime,errors=remount-ro 0 1 Actually, you can skip step 3. It is not necessary to do it now.by bodhi - uBoot
pocket, Once you're able to log into Debian like this, it is all OK. root@debian:~# So you've done the installation! Now the next step is to update your system: apt-get update apt-get upgradeby bodhi - Debian
pratikworld, When you plug the USB stick into Ubuntu (or any Linux system), it will be assigned a mount letter. It could be: sda1, sdb1, sdc1, sdd1, ..... So that is the drive you need to use in the instruction. So if you format the drive like this successfully, then it must have been assigned as sdc1: root@ubuntu:/home/ubuntu# # e2fsck -f /dev/sdc1 root@ubuntu:/home/ubuntu# # mke2fs -n /dby bodhi - uBoot
Hi Jean, Both the squeeze and wheezy scripts by Jeff were out of date (with respect to the Debian repo), so they are not working properly anymore. That's why I've released the rootfs mentioned above. This rootfs is a minimal Debian system, much like what you get after you ran one of these scripts. So currently this is the best way to get latest Debian kernel installed for the Dockstaby bodhi - Debian
Hi pbg4, So the behavior is consistent with the NSA310S PHY manual pokes. Everything works, but a minor glitch is some how the Ethernet port LED does not refect the true speed. I'll move this image status up to release thread. We'll look at the LED issue later. Thanks!by bodhi - uBoot
Hi pbg4, > since I am testing at the moment for a new > devicetree description to > let the nsa3xx-hwmon kernel module recognize the > nsa320 mcu I have here two > nsa320 boxes, Any luck in testing this NSA320 DTS change?by bodhi - Debian
I've uploaded a test u-boot for the NSA320. Please see: http://forum.doozan.com/read.php?3,23039by bodhi - uBoot