Micky Wicky, Try adding GPIO 20 or 22 or both in addition to the GPIO 33 in the mask.by bodhi - uBoot
syong, > pogo v4 senses the input pin of its serial port is high(3.3v) > No need of the resistor, > if the input pin of the serial port of the pogo v4 > is connected to 3.3v when booting as shown in the > attached picture. This is a cool deductive reasoning! And this mod will not fry the Pogo V4 serial port with the 3.3V because the 3.3V is connecting to the RX pin onby bodhi - Off-Topic
sunspot, Netconsole only outputs this much. After the kernel begins starting, there will be no more outptut, unless Debian was setup to output more during kernel booting. And this requires the initrd image to be regenerated while Debian is running. Try interrupting netconsole to print out the u-boot envs. Assuming the Pogo u-boot env ipaddr was set as 192.168.0.100, use this command: nby bodhi - uBoot
Joey, > > Wish I at least had the torrent file to give you, > because torrents should still be fine. Pretty sure > mine's long gone though. Thanks for the thought! I found it in my archive. Turned out I did download this ISO back in December, but forgot about it :)by bodhi - Off-Topic
Joey, > Have you all tried 17.3 No Mint 17.3, the site was hacked too. I guess I'll have to find the torrent somewhere.by bodhi - Off-Topic
Hi syong, > No need to solder, > > if the serial port of pogo v4 is connected to an > USB2TTL adaptor as shown in the attached picture. Wow. That's cool! And good to see you posting again :)by bodhi - Off-Topic
Gravelrash, > However the Arch guys figured out a > "workaround" > https://wiki.archlinux.org/index.php/Dell_Chromebook_11#Post_Installation_Configuration > Thanks, this might work.by bodhi - Off-Topic
Gravelrash, I'm trying to get the trackpad to work on Mint 17.1 or 17.2 with Dell Chromebook 11 (first year model). It does not work at all in either versions. I think perhaps the driver was not running, but dmesg did not show any sight of it was even trying to load. While the system on USB is running, xinput does not show the trackpad, only usb. Right now I'm have to use the mouby bodhi - Off-Topic
Beware of hacked ISOs if you downloaded Linux Mint on February 20th! http://blog.linuxmint.com/?p=2994 As Clem recommended, make sure you check the md5sum for this ISO.by bodhi - Off-Topic
I've uploaded the latest rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Please see 1st post for download link.by bodhi - Debian
tilator, I've just remember this. Which u-boot are you running? the version I've released has SNTP, but the RTC clock driver was commented out, since the Pogo V3 does not have it. You could take a look at the source code in my GitHub. And see if you can put it back, and use SNTP to query the datetime, and that hopefully will update RTC during boot. However, I am not sure if our cby bodhi - Debian
bobafetthotmail, > I know. My point still stands. Adding letters > after names is silly and should be avoided. I do agree. > Sorry but there isn't any clear indication on the > box nor on the board. no V1 or V2 or V3 or > nothing. > But obviously the above was probably the reason for the DTS author to have named them that way? We know what's in the kiby bodhi - Debian
notoneofmyseeds, For step 1. If you run Windows PC and have Acronis True Image, I would recommend using that and be done quickly. If you do it as instructed in a Linux box, then the drive letters need to be adjusted to whatever being mounted in your box. Sometime the drive is mounted using its parttion label, or using a special name (which is your situation). So in this thread: http://by bodhi - Debian
bobafetthotmail Wrote: ------------------------------------------------------- > >So please list the model and DTS file names > here. > > Can you explain a bit more in detail? What do you > want me to do? :) > I need to describe the difference between the 3rd version of the DTS and the exisiting 2 DTS. And how would users determine if they should use this 3rd versby bodhi - Debian
tilator, > Sounds like rootfs will be corrupted several times > more before file system drivers are OK. I think we are safer to stay with kernel 4.1 Oxnas and not try to test using real rootfs until we figure out the reason. The puzzle is why Kirkwood 4.4 rootfs is working fine with Ext4 but not the Oxnas 4.4 rootfs? something in the Oxnas-specific code must have triggered this bug.by bodhi - Debian
vaidyasr, You can try creating 2 USB rootfs (versions 3.16 and 3.18.5). See this kernel/rootfs thread: http://forum.doozan.com/read.php?2,12096 Look for these 2 tarballs in 2 sections: Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2 QuoteUpdated 02 Sept 2014 (rootfs): Rootfs Debian-3.16.0-kirkwood-tld-2 was uploaded. This rootfs is to keep in sync with kernel Linux-3.16.0-kirkwoby bodhi - Debian
I did some testing with what we already have. Using an Ext4 rootfs. The interesting behavior of Ext4 driver: Booting with kernel 4.1, there is no problem running it for a while. And then, booting with kernel 4.4 caused an error: [ 26.608547] EXT4-fs error (device sda1): ext4_get_branch:170: inode #409672: block 1684366702: comm mv: invalid block After booting back to kernel 4.1, thiby bodhi - Debian
> > It would just be "nice" to have the device still > alive and updated. It's not easy to find other > similar devices with internal sata, esata, > two usbs, passive cooling, small footprint > and so on. Yeah, I plan to revisit this so we can upgrade the kernel. Just need to find more time... or a good hint from mr google :) or perhaps from someone whoby bodhi - Debian
> Thats the same model as mine then: lm85 and red > USB LED. > Would be nice if bodhi can provide a third variant > of the dts file along with the next kernel > release. > So far I can live without the red USB LED but got > the fan tamed :) Sure I will :) But before doing that I would like you guys to post the definitive info about the variants. Currently NAS Centralby bodhi - Debian
tilator Wrote: ------------------------------------------------------- > Can you tell me one more thing. > > Compiling u-boot 2014.10 does make u-boot binary, > but not SPL. What might I do wrong? Nothing wrong. You can build u-boot separately, which is what I do normaly (there is no need to rebuild SPL, 2013 version works just fine). If you want to rebuild SPL, then use theby bodhi - Debian
sLOID, Here you go, use this u-boot image for LaCie ns2l to run kwboot with option -p: ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2015.10-tld-1.ns2l.mtd0.kwb -pby bodhi - Debian
Damien Wrote: ------------------------------------------------------- > Bodhi, > > I must say I'm starting to be a bit mystified by > these issues. I'm going to revert to 3.18-5 on > Jessie and see how it goes. So far, these are the > tests I've done with my cheapo-chinese-Wifi: > > 1- Debian 7 wheezy w/ kernel 3.18-5 with kernel > driver =by bodhi - Debian
Damien, The configuration for RTL8192CU did not change in 4.4, it is the same as in 3.14. Does the kernel driver in 4.4 cause the same problem? have you let it run for a while?by bodhi - Debian
fido95, > My pogoplug indicator doesn't blink green or red, > with nor without sd card. > Is connecting via serial converter to load uboot > the only solution to connect with my pogoplug ? Yes, connect serial is the only way. Yes those should work. But also read this thread before buying: http://forum.doozan.com/read.php?8,13263by bodhi - uBoot
sLOID, > i tried your workaround but without success. i'll > give your actual u-boot a try Don't flash :) they are not built for the LaCie! do only UART booting see if it works.by bodhi - Debian
sLOID, It is a classical problem with ntpd and ntpdate resource fighting. Sep 4 10:14:56 LaCie daemon.err ntpd[1502]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Our member restamp did a really good job with his explanation: http://forum.doozan.com/read.php?2,20817,20828#msg-20828 If you were running one of my new u-boot images, then SNTP prby bodhi - Debian
tilator Wrote: ------------------------------------------------------- > I have it all. Do you want it? It is a little old, > though ;) I could have used this long ago :) I don't see the need for this now. Except if we need to find out what it does with the RTC driver m41t00. I think you should try to resolve the shutdown problem first (perhaps it is related to the RTC problemby bodhi - Debian
sLOID, Which rootfs are you running? if you are running my 3.18.5 rootfs then your ntpd should be running. Could you post the whole dmesg output and logread output here or pastebin them. I don't think I can guess the problem without seeing the whole picture. > is > there a way to set the rtc over the > serial-connection after interrupting the boot > sequence ?? Not liby bodhi - Debian
Woow. I did not know we have GPL for this?! is that from Oxnas? do you have the whole GPL package or just a few files?by bodhi - Debian
tilator, > There must be some reset routine somewhere in the > old kernel Apparently so. I agreed, seems like it needs to be more than what being done in the 4.1 driver. Wonder what's in 4.4 or 4.5-rc?by bodhi - Debian