shayan123, See this release thread: https://forum.doozan.com/read.php?2,12096 QuoteLatest released rootfs: Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (24 Jul 2017) Scroll down to section: QuoteUpdated 24 Jul 2017: Basic Debian stretch Kirkwood rootfs for most Kirwood plugs: - tarball size: 188M - install size: 488M - The init system used in this rootfs is sysvinitby bodhi - uBoot
shayan123 Wrote: ------------------------------------------------------- > The main reason I started tinkering with my GFH > was because I wanted CUPS on it. So I suppose > Debian is a better choice. True. > I'm not sure how to proceed (considering that my > envs are currently messed up). > If I decide to install Debian, do I need to fix > the envs first?by bodhi - uBoot
shayan123, > Yes, I can. But the real issue is, I can't get it > to boot successfully, This is what I always get: > *** Warning - bad CRC or NAND, using default > environment Your envs were corrupted for whatever reason. So you cannot boot to stock OS or any OS. That CRC error means the NAND space (usually 128K) that contains the envs were wiped out, or messed up. &by bodhi - uBoot
Ghosty, It's in the u-boot installation instruction. You've just missed it! Quote8. Flashing default u-boot envs image (if you are upgrading from 2016.05-tld-1 u-boot, you can skip this step 8). ..... f. Adjust the DTB name to boot with a rootfs that has FDT kernel 3.17+ (this is the normal case): Find your box DTB file in the rootfs /boot/dts directory and adjust theby bodhi - uBoot
Let’s see the serial boot log.by bodhi - Debian
Ron, > From 192.168.1.254 icmp_seq=3 Destination Host > Unreachable > Is it weird that the message is coming from it's > own address? > That's normal. It showed the box is 192.168.1.254. And it's trying to reach the router (Destination Host), but there is no connection. Ah! I've missed that error "Environment does not fit into available sectby bodhi - Debian
Ron, QuoteAnd error about fw_printenv was because the content of fw_env.config should look like: # MTD device name Device offset Env. size Flash sector size Number of sectors # Linksys EA4500 /dev/mtd1 00080000 0x20000 0x20000 Pls get the listing of envs in Debian: fw_printenv and also cat /etc/network/interfacesby bodhi - Debian
Ron Nelson Wrote: ------------------------------------------------------- > All the file contains is this: > > nameserver 192.168.1.1 > > Should it have more? I've never had to edit it to > get internet before. That looks good. Usually nameserver is your router. So try static IP to make sure ethernet works first.by bodhi - Debian
Ron, What is is in your resolv.conf? cat /etc/resolv.conf If this resolv.conf looks good, then you should try using a static IP to see if it is OK.by bodhi - Debian
Your Wifi is runing: wlp1s0: flags=4098<BROADCAST,MULTICAST> mtu 1500 ether 48:f8:b3:99:29:80 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp2s0: flags=4098<BROADCAST,MULTICAST> mtu 15by bodhi - Debian
Ron, That's not the entire serial log. Entire serial log means from u-boot banner to the last command output (copy/paste your terminal session here). There are a lot going on in the serial log that hopefully will tell the story. And error about fw_printenv was because the content of fw_env.config should look like: # MTD device name Device offset Env. size Flash sector size Numby bodhi - Debian
Ok, it's time for me to see your entire serial console log! Power up, interrupt serial console and set up your envs like you would. And then printenv boot Let it boot and log in. And cat /proc/mtd cat /etc/fw_env.config fw_printenv ifconfig -a Pls post the entire log here.by bodhi - Debian
Ron, > Ethernet isn't cooperating, and I am > guessing/hoping it's just because of that darn > WiFi extender that it is plugged into. Could be. > Maybe sometime I'll move all this stuff > upstairs and get a direct connection. During testing, I would do this and then later move it back to where it is intended. Direct connect to a swich or a router is bby bodhi - Debian
Joey, > Powerful warm spell here too so maybe bodhi's > timeline I hope to get to my projects proper inc > DreamPlug. Get going Joey :)by bodhi - Off-Topic
This is an interesting patch: QuoteLinux 4.17-rc4 Leon Romanovsky (4): RDMA/mlx5: Fix multiple NULL-ptr deref errors in rereg_mr flow RDMA/mlx5: Protect from shift operand overflow RDMA/mlx5: Properly check return value of mlx5_get_uars_page RDMA/mlx4: Add missed RSS hash inner header flagby bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > shayan123 Wrote: > ------------------------------------------------------- > > bodhi Wrote: > > > ------------------------------------------------------- > > > > > Of course, it is impossible to send command > to > > the > > > GF Home if you don't connect iby bodhi - uBoot
Ron, Cool that you have booted into Debian successfully! Yes, the envs were the problem. I've also specified "earlyprintk=serial" just in case I need to see the kernel booting progress, but I knew that the loading address was the problem. This is the correct behavior for the DSA switch. [ 8.687935] DSA: switch 0 0 parsed [ 8.691378] DSA: tree 0 parsed [ 9.588by bodhi - Debian
Nirmal_Kumar, > i cound't able to find a simple steps to on what > is the configuration i need to make in order to > boot from HDD.? Your u-boot is already set up to boot from HDD. All you need to do is the create the rootfs on HDD, either brannd new, or clone it from the MMC drive. See the Wiki thread for tutorial about cloning rootfs: QuoteBackup and Cloning roby bodhi - Debian
Ron, Do the same procedure, with these envs, setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' setenv load_usb 'usb start; ext2load usb 0:1 0x800000 /boot/uImage; ext2load usb 0:1 0x02100000 /boot/uInitrd' setenv bootcmd_usb 'setenv bootargs $(bootargs_usb); run load_usb; bootm 0x800000 0x02100000' And pls postby bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > ayosher, > > Your envs were correct in this this post: > https://forum.doozan.com/read.php?2,62669,62669#msg-62669 I took a closer look again! It was actually wrong here: bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)by bodhi - Debian
Ray, > So its likely that kirkwood support for > anything more than 512MB of memory has minimal if > any testing. True. I have not seen a > 1GB Kirkwood box until this M300. There were memmory tricks in the past that allow us to go over 768M, but they all phased out (those were workarounds so they were removed when the CONFIG_HIGHMEM was merged to mainline). I'll lookby bodhi - Debian
Gravelrash Wrote: ------------------------------------------------------- > well today it landed..... :) > > * progress will be slow as the UK is having > unseasonably good weather and im making the most > of it :))))))) Cool :) I'm going to be very busy in the next 6 weeks (works and trips). But I might be able to spend a few hours to open up the box and hook up serby bodhi - Off-Topic
shayan123 Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > > Of course, it is impossible to send command to > the > > GF Home if you don't connect its RXD pin. From > the > > pic you posted above, only GND and TX are > > connected. > > > &gby bodhi - uBoot
ayosher, Your envs were correct in this this post: https://forum.doozan.com/read.php?2,62669,62669#msg-62669 Power up, interrupt serial console, and do whatever you want to change to envs, and then printenv boot Post your entire serial boot log (from u-boot banner until the Debian login prompt).by bodhi - Debian
ayosher, > Just to let you know, kernel you providing > ignoring mtdparts that sent in command line. That's incorrect. You must have some syntax error in the command line bootargs, and the kernel took what's in the DTB.by bodhi - Debian
Here is what I got so far. Everything is working well. Except: Minor: - SPI flash is still protected. So we can see the u-boot envs in Debian, but can't change it yet. - LEDs: without GPL, looks like we need to ping each one. But this is a good-to-have, not important. Major: - 2GB Memory is a tough one. I've rebuilt the kernel to use highmem. But testing showed that it is quby bodhi - Debian
ayosher, I won't be able to get to my boxes today, and perhaps in a couple days. Anybody who has tried to compile module and can chime in?by bodhi - Debian
Cool! BTW, Dockstar runs quite hot. You might need the use 4 felt pads as feet to raise the box up a little.by bodhi - uBoot
Rolfep, The reason you could not modify ethaddr in Debian because your kernel is too old (3.3.2-kirkwood-dg). This is because mtd0 was locked to prevent ethaddr beign changed. You can use the local MAC address ethaddr=52:3b:20:9c:11:51for now. Once you have booted into the new rootfs Debian-4.12.1-kirkwood-tld-1 ethaddr will be modifiable. > Right now, only squeeze is booting for me.by bodhi - uBoot
ayosher Wrote: ------------------------------------------------------- > bodhi, > > The (1) I found myself: > > root@pogoplug:~# ls -la /lib/modules/$(uname > -r)/build > lrwxrwxrwx 1 root root 44 Jul 3 01:06 > /lib/modules/4.17.2-kirkwood-tld-1/build -> > /usr/src/linux-headers-4.17.2-kirkwood-tld-1 > root@pogoplug:~# > > > However (2)by bodhi - Debian