TheDoo, In addition to the good advices from graymanforhire above, > I figured it might be the Uboot parameters, > unfortunately I can't ssh into just the pogoplug > to update them. Or I'm missing something. You need to use the rootfs label for the usb rootfs, and setup u-boot envs to mount rootfs with label, while booting multiple disks. I've just posted thisby bodhi - uBoot
mikeh49 Wrote: ------------------------------------------------------- > I'm preparing to update a Pogo P21 with the new > u-boot to use the new kernel and Debian file > system. The bad blocks check returns the > following: > > > /$ dmesg | grep -i 'bad' > [ 1.710000] Scanning device for bad blocks > [ 1.780000] Bad eraseblock 981 at &by bodhi - uBoot
suo_jian, It's a strange behavior from serial console (repeating prompt). If you'd like to confirm your booting process, please power up, interrupt serial console and then list the envs, I will take a look. printenvby bodhi - uBoot
habibie, To do what you plan to setup NFS booting: 1. Setup NFS v3 share on the GoFlex Net first, and make sure you can mount it on the other boxes. This is a little bit time consuming. 2. Once you can mount NFS v3 shares and use it on the other boxes, then install u-boot on the other boxes, make sure you can run normally with USB drive, as before. 3. Download the latest rootfs (3.14, 3.by bodhi - uBoot
gunjae, > But, I believe it is out of 1M area for uboot. > Right? Right, it is way out, higher than 1M. Besides, your u-boot in NAND has booted until after the kernel was loaded successfully, and solid green LED means kernel was loaded and starting. So it is not u-boot. The remaining possible problems are bootargs and rootfs mounting. And your bootargs look OK. So for whatever reasby bodhi - uBoot
gunjaekoo, Does the LED lit solid green? do you use static IP address? netconsole only shows that much, nothing more, unless you set it up further. All I can suggest is: - Take the USB to another box and do fsck to make sure there is no file system error. - If there was no error, perhaps try rootfs label approach: 1. Take the USB to another Linux box, mount it and label the rootfs (iby bodhi - uBoot
@nohud, > Enabling the following in the next kernel compile > should fix the issues with wireless: > > Old > # CONFIG_CFG80211_WEXT is not set > > New > CONFIG_CFG80211_WEXT=y > > > See > https://github.com/raspberrypi/linux/issues/171 Which wireless issue? with the stock wifi ?by bodhi - Debian
Neptune Wrote: ------------------------------------------------------- > Ok, I downloaded and installed the Archlinux and > here is the output. > I am unable to get the env output. > > # cat /etc/fw_env.config > cat: /etc/fw_env.config: No such file or > directory > # > Create this file and copy the content above to it. > > And here is the compby bodhi - Rescue System
habibie, > Is this > uboot.2014.07-tld-1. > dockstar.bodhi.tar your latest uboot for > dockstar? If so, does it support EXT4? Yes it does. > > OTOH, I read the above link and somewhere there is > a reference to a non-FDT and/or FDT kernel. What > does it mean by FDT? Flattened Device Tree (FDT) info My released kernel : Linux Kernel 3.17 (FDT) and 3.1by bodhi - uBoot
Guidobelix Wrote: ------------------------------------------------------- > Hi Bodhi, > > just wanted to say thank you because this new > uboot has brought a new life to my PP4s. > Now I can reboot consistently (no matter which > devices I have plugged in), I have NTP enabled > (and services are not starting in 1970 anymore) > and I have netconsole working (well,by bodhi - uBoot
@grayman4hire, I was just making a blanket stament about using ext3 to avoid power outage problem. Nothing specific!by bodhi - uBoot
suo_jian Wrote: ------------------------------------------------------- > Hi Bodhi, > I connected a serial-usb adaptor between e02 and > ubuntu 14.04 > > The wire's map is : GND - GND, RXD - TXD, TXD - > RXD according to > http://blog.qnology.com/2013/10/pogoplug-e02-v2-se > rial-connection.html > > and run > #> screen /dev/tty1 > >by bodhi - uBoot
Your u-boot even though it is old, it's fine. Don't try to mess with it for now. You can just download the latest Arch rootfs and create a new USB thumb drive, format it as Ext3 with it (on a different Linux box), and boot with it. If you're desperate to get anything working, temporarily use my rootfs (Updated 31 Oct 2014 Rootfs Debian-3.17.0-kirkwood-tld-1) and boot with it. Iby bodhi - Rescue System
@TheDoo, You are running the latest u-boot. Do this to recover: - Download the latest rootfs from this thread (Updated 31 Oct 2014 Rootfs Debian-3.17.0-kirkwood-tld-1). - Format a new USB thumb drive with Ext3 (or just use one you have and format it as new, wiping out all data, though) - Follow instruction to untar that rootfs to the drive - Take it to the Pogo and cold start. Fromby bodhi - uBoot
What a f' mess :)) where did you get this roofts? In your serial console please print the u-boot version: > version It you are running u-boot installed by Jeff's script or my u-boot build then the fw_config should look like mine showed above.by bodhi - Rescue System
Good idea, but while you are waiting for serial, - on server start pinging the pogo ping 192.168.1.76 - power up the pogo - if the pogo netconsole is running then you should see it responds to a few pings. If no response then either the network problem, or neconsole is not running at all.by bodhi - uBoot
purespin Wrote: ------------------------------------------------------- > I just upgraded to this kernel and rootfs with the > help from bodhi! Everything looks good except one > thing: > > > oxnas:~# mount -t iso9660 -o ro,loop keiso.iso > /mnt/temp > mount: Could not find any loop device. Maybe this > kernel does not know > about the loop deviceby bodhi - Debian
suo_jian Wrote: ------------------------------------------------------- > Hi bodhi, > Checked with new command, still no message shown, > is it possible the nc message is not sent to > 192.168.1.78, but somewhere else? Ah! it was reversed in u-boot envs :) serverip=192.168.1.78 ipaddr=192.168.1.76 if_netconsole=ping 192.168.1.78 start_netconsole=setenv ncip 192.168.1.7by bodhi - uBoot
purespin, Quote > fw_setenv ethaddr '00:25:31:00:ef:ed' > Can't overwrite "ethaddr" > > But I can change ipaddr and serverip env using the > same fw_setenv command! It should allow you to change ethaddr in Debian. You can also set it in u-boot console with setenv. What's your output of fw_printenv mtdparts uname -a Quote > - Do I stiby bodhi - uBoot
Neptune Wrote: ------------------------------------------------------- > Ok, I again reformatted the drive and installed > Archlinux again and this time its getting > IP(although I have set it as statis IP, it is > getting random IP, but this we can solve later). > I have 2 issues now, when I boot into Archlinux > and issue command > > What I did: > I interrby bodhi - Rescue System
Your roofts still has error. Have you tried to use a different Usb drive? Perhaps this drive is bad.by bodhi - Rescue System
suo_jian Wrote: ------------------------------------------------------- > Hi bodhi , > I run netcat-traditional, and listening at > 192.168.1.78, but there is no output. > > any other suggestion? Check your nc command. The correct command is: nc -lup 6666 192.168.1.78 6666by bodhi - uBoot
Purespin, Mount the new rootfs on the other Linux box and regenerate uImage: mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-3.17.0-oxnas-tld-1 -d /boot/vmlinuz-3.17.0-oxnas-tld-1 /boot/uImage sync Take it to the Pogo and power up.by bodhi - uBoot
purespin, > ls -l /media/sdc1/boot > total 5488 > -rw------- 1 root root 2805560 Jun 6 2013 > uImage-3.1.10 > -rw------- 1 root root 2805496 Jun 6 2013 > zImage-3.1.10 > > Are you running Arch or Debian? there is no uInitrd in /boot. Is this a special build by Ingmar? I recall Ingmar_k does not use Initrd. > I haven't upgrade the kernel yet. Bby bodhi - uBoot
suo_jian, > This is nc from the netcat-openbsd package. An > alternative nc is available > in the netcat-traditional package. > Yes, you need to run netcat-traditional. > Btw, all rootfs/format are done in the ubuntu vm since mac can't write to ext3 easily.... This is fine, I do exactly this very often on a MacBook Pro. I'm sure your problem is easy toby bodhi - uBoot
purespin, > Thank you for the quick reply. Are you talking > about step 9 & 10 in 1st post? Yes step 9 and 10 > I didn't do these as I thought this is only for > FDT kernel. The new kernel is FDT. Stock kernel is not FDT (also some people are still running older non-FDT kernels). So if you plan to run new kernel then the new envs are needed if the DTB is not emby bodhi - uBoot
suo_jian, > I also create Linux Kernel 3.17 (FDT) on a usb > flash Did you upgrade the kernel on an existing rootfs, or create a brand new rootfs? > and plug to the usb, after reboot, I do not > see any message output from netconsole server. serverip=192.168.1.78 ipaddr=192.168.1.76 if_netconsole=ping 192.168.1.78 start_netconsole=setenv ncip 192.168.1.78; setenvby bodhi - uBoot
Your current env: usb_rootfstype=ext2 In serial console, change to ext3: setenv usb_rootfstype ext3 then let it boot boot After verifying everything is working OK, set it permanently in Linux: fw_setenv usb_rootfstype ext3by bodhi - Rescue System
purespin Wrote: ------------------------------------------------------- > Hi, > > I tried to upgrade from an old U-Boot (1.1.2 Jul > 29 2010) by following the first post. Everything > seems fine but I got the following error when > rebooting (using serial cable): > > > U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27) > Boot device: NAND > Attempting toby bodhi - uBoot
@Neptune, To really fix and prevent your rootfs corruption, you need to change u-boot env rootfs type to be consistent with what you have on the USB drive. If you're not sure how, please post your u-boot envs. In serial console, printenv Your dmesg showed that you're still having problem.by bodhi - Rescue System