denexo Wrote: ------------------------------------------------------- > @bodhi, > > if it is not a trouble for you, could you please > make a testing 3.17 kernel with the above > mentioned uvcvideo patches? I could try its > working status ;) Sure, I will when I have time to do it!by bodhi - Debian
@Robert, Activate netconsole fw_setenv preboot 'run preboot_nc' Set bootargs fw_setenv set_bootargs_usb 'setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params'by bodhi - Debian
bobafetthotmail, Yes, with the new pre-release u-boot. It is quite stable now, no long experimental. And with kernel 3.16 tdl-3 only.by bodhi - Debian
Thanks shv, it will come in handy someday!by bodhi - uBoot
@WarheadsSE, Thanks for confirming. Not a watchcat, but this watchdog has nine lives :)by bodhi - Debian
@Robert, Step 4 in the installation: Quote 4. Create uImage and uInitrd and setup for booting. I'm using the GoFlex Net booting with USB drive as an example here. Please replace its name (kirkwood-goflexnet.dtb) with the box you are installing on (for example, kirkwood-pogo_e02.dtb). Look inside /boot/dts/ for the correct DTB file name for your box. ………… 4a. Boot witby bodhi - Debian
@robert, Please refrain from changing the subject of this thread. It's a kernel release thread. The reason your SATA boot failed was because you have not adapted the DTB booting syntax (the instruction is for USB) in to your SATA boot commands. I will respond in detail in your new thread when I have time to post again (if you have not solved it by then).by bodhi - Debian
@bobafetthotmail, > In case you were wondering, I nuked "softdog" > process you pointed out above for addy75. > Blacklisted its kernel module and disabled the > daemon from its config (see here > https://tools.bitfolk.com/wiki/Softdog ). > > No difference. Reboot at around 30-35 sec from > start. Thanks for the info. Good to know this for a fact!by bodhi - Debian
@bobafetthotmail, > I have a nsa325v2 with stock U-boot and set it up > with the 3.16 debian rootfs with the watchdog > fixed. Make sure you run 3.16.0-kirkwood-tld-2 with stock U-Boot. The fix in 3.16.0-kirkwood-tld-3 works with new U-Boot. > > Installed OMV + some plugins that have nothing to > do with watchdogs. > > Now the dumb watchdog kicks in at aroby bodhi - Debian
Update your wget package. http://permalink.gmane.org/gmane.linux.debian.user.security.announce/3224by bodhi - Debian
Rootfs Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 was uploaded. Please see 1st post for download link.by bodhi - Debian
@highsinberg, Do what Almaz has suggested: recreate your rootfs, and reinstall packages. After you've rebuilt your package database like I posted above, all the inconsistency about dpkg/apt database should have been fixed. If the problem comes back like you've experienced above, it indicates that your rootfs is no good. Don't fight it :) you're going to waste your time agaiby bodhi - Debian
Almaz Wrote: ------------------------------------------------------- > sounds to me like you never put properly rootfs on > USB stick. I think Almaz is right, the rootfs seems to be corrupted. What I've suggested above was to fix the package database corruption. And it seems to have fixed the problem, for now. But I think it is safer to recreate the rootfs from scratch. Just repeby bodhi - Debian
slyphoxj, 1. Make sure GND is well connected. This problem might be GND. Usually it shows a different behavior when the RXD and TXD are not connected correctly. But according to the eBay info, Green is TXD, so it should be connected to RXD on the plug header. But you'll never know, with cheap serial converter on eBay, you should be prepared to just trying to swap the TXD and RXD wire tillby bodhi - uBoot
slyphoxj, It might be a problem with your serial connections. Have you get it working before, or is this the first try on the Pogo E02? You should recheck your serial connections (GND-GND, crossing TXD-RXD, baud-rate, parity…. etc). If after you've verified the connections are OK, and it still gives this problem, then let it boot, don't interrupt it. Then capture the entire booby bodhi - uBoot
highsinberg, You can try this first to see if it helps: apt-get clean dpkg --clear-avail rm /var/lib/apt/lists/* --force dpkg --configure -a apt-get update apt-get install samba apt-get install minidlna And always sync before shutdown, and turn off power. sync shutdown -h nowby bodhi - Debian
QuoteI think the original environment is located at a different memory address, e.g. 0xa0000. Moreover it has a different format and/or checksum because I can't print it with fw_printenv if I change Device offset to 0xa0000 in /etc/fw_env.config Correct, they are at different location, and use different checksum. So running original u-boot, you'll need 0xa0000 and blparam. That'sby bodhi - uBoot
shv, a backup of Goflex Net Stock uboot envs Very encouraging. Have you tried these? mainlineLinux=no is relevant: mainlineLinux=no console=console=ttyS0,115200 bootargs_root=root=/dev/mtdblock2 ro bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000 If this does not boot, the next thing you can do is to create a script to setby bodhi - uBoot
Rootfs Debian-3.17.0-kirkwood-tld-1 was uploaded. Please see 1st post for download link.by bodhi - Debian
shv, In the first 2 tries, the bootargs might have something to do with it not being able to go further. There are 3 possibilities: 1. bootargs variable was set explicitly in the envs in stock. 2. bootargs variable was set by stock u-boot internally (bootargs env might be undefined). 3. bootargs are hardcoded in stock kernel, so it does not matter what the bootargs content is (bootargs eby bodhi - uBoot
shv, Something similar to this: rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi Consider this about the rescue system: similar to the original kernel uImage. Sorry I can't be more specific. I'm just not interested in booting Popo OS so never thought about this much,by bodhi - uBoot
denexo, > The issue seems to have been solved > http://git.linuxtv.org/cgit.cgi/pinchartl/media.gi > t/commit/?h=uvcvideo/fixes&id=a7f053c67c357c4b68c1 > be21976a1d464f97916b but hasn't been kernel > upstreamed yet. Did people try this and report that it works? I could incorporate the patch into the kernel and recompile to get the module (the modification is inteby bodhi - Debian
@Juan C Ah! I'm not familiar with OpenWRT so did not know that it boots only with uImage. This should boot with Debian, OpenWRT, and Arch: Add load_initrd, and modify bootcmd_usb: setenv usb_load_initrd 'ext2load usb $device 0x1100000 /boot/uInitrd' setenv bootcmd_usb 'run usb_init; run set_bootargs_usb; run usb_load_uimage; if run usb_load_initrd; then bootm 0x80by bodhi - uBoot
blackdevil, The patch is large and looks pretty bad :) I don't think we should even attempt to retrofit it. If you can find the Linux SATA driver for this SoC that can be used in modern kernel, then I would say attempting to create a DTS for FDT kernel is feasible. If you can't find SATA driver then I would throw in the towel :)by bodhi - Debian
@Juan, This is a typical rootfs mounting problem. - Ensure your rootfs (/ partition) is formatted as Ext3, because your rootfstype env is: rootfstype=ext3 - Label your rootfs (sdxx is the partition letter for you rootfs /) \. In Linux: tune2fs -L rootfs /dev/sdxx - Set your rootfs label in bootargs in serial console setenv usb_root 'LABEL=rootfs' If you have 2 partitiby bodhi - uBoot
shv, Take alook at how the rescue system and the ubifs system is booted in the envs set by Jeff's script: bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset force_rescue=0 force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0xby bodhi - uBoot
ingmar_k Wrote: ------------------------------------------------------- > Thank you very much for the hint! > > I just ran into a kernel oops with a Goflex-Net > and Kernel 3.16.3 and samba over eth0. > Seems this fixed it. At least I hope that it did. I've also pached the kernel to set it to default off (see the patch in the kernel release thread).by bodhi - Debian
Kernel linux-3.17.0-oxnas-tld-1 package was uploaded. Please see 1st post for download link.by bodhi - Debian
anto, > at last after 2 > years gathering dust I can finally use my pogo pro > to play music! Cool! glad to hear a success story :)by bodhi - Debian
Gravelrash, This is a nice writeup: http://forum.doozan.com/read.php?3,12261 I've been runing a cluster of Pogos with nfsroot on a GoFlex Net SATA for about a year now. All connected with Gbit Ethernet. It's best to run NFS V3 with these Pogos, easier to make it work.by bodhi - Debian