chrishelms, > What I don't understand is that netconsole was > working fine. Then I did two changes unrelated to > netconsole, typed saveenv and upon restart I had > no connection to netconsole anymore. I wonder if > it is still working, maybe on another ip address? This is why I always recommend changing u-boot envs in Debian with fw_setenv only. Sometime saveenv inby bodhi - Debian
Looking at these envs, your netconsole should be working: ipaddr=192.168.10.233 serverip=192.168.10.244 preboot=run preboot_nc preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi ethaddr=b6:d0:5e:0f:a1:17 if_netconsole=ping $serveripby bodhi - Debian
chrishelms, > > first of all a big praise: i have a goflex home at > work where i installed debian. it's rock solid and > has been running as our companies main server for > 6 months now. Cool! this is the first time I'm actualy aware that my u-boot and Debian rootfs builds are used in workplace. > > so i decided to buy one for myself but i must havby bodhi - Debian
I've uploaded the Zyxel NSA310S/320S u-boot-2014.07-tld-4 image. Please see 1st post for download link.by bodhi - uBoot
edinger, > What do I have to change now to run a usb stick > with 2 partitions (boot and rootfs) - possibly > rootfs with ext4? See this thread: http://forum.doozan.com/read.php?3,19093 In summary, if you intend to plug in more than one USB or SATA drives, or having multiple partitions on a drive, you need do both sections A and B. With the new u-boot, you can use Ext4 forby bodhi - Debian
tilator, > I had some free time and took my Silverstone DC01 > (an OX820 device too) and compiled 4.1.6 kernel > for it. > > And - once again run in trouble with rtc because > this kernel does not power off this device > properly. Can you describe the rtc problem you have? does the DC01 have RTC? The Pogo V3 (so are many other plugs such as Dockstar, GoFlex Neby bodhi - Debian
@z3bram3n, There is something peculiar about your rootfs. I've installed and been running this test kernel on my NSA310S. Try it with a new test USB rootfs to see if you encounter the same problem. Do you have more than one user on your system, or just root?by bodhi - Debian
Davide, > CPU goes at 100%, mostly kernel times. > Is it a real problem ? It is not a real problem. If the dd command is the only thing running, we do want it to take most of the CPU :) OTOH, if something else is running actively, then dd should not take that much CPU. The disk read/write speed is that I meant above, that I want to take a look when I have time.by bodhi - Debian
edinger, > Maybe it's related to the fact that I just > unpacked the 3.18.5 package to the usb stick as I > have no running system on NSA325 to create the > correct kernel with your descriptions Right on! the rootfs can not be used to boot with your current default envs. It nees the DTB appended, as described in the installation instruction. Quote4. Create uImage withby bodhi - Debian
ziggy, There is nothing wrong with your u-boot envs. machid should be undefined. Try download the uImage again. I've just re-uploaded it. Perhaps I've used the wrong file the last time!by bodhi - Debian
I've uploaded a new test kernel for Zyxel NSA 310 and 320: http://forum.doozan.com/read.php?2,23555by bodhi - Debian
@edinger, According to the boot log, you have installed uboot.2014.07-tld-4 for NSA325, but did not flash the default u-boot envs in section B. But instead, your current envs are a mixed of stock u-boot envs and the new u-boot default envs (when you did the saveenv, it saves everything in the u-boot envs memory space). QuoteB. Flashing default u-boot envs image This is the tarball in sectby bodhi - Debian
I've uploaded linux-4.1.0-kirkwood-tld-3-test for the NSA310 and NSA320 boxes. This test kernel incorporated pbg4's patch for the nsa3xx-hwmon as described here. For users who has the NSA310 and NSA320, please try install this kernel and make use of the hwmon to see if your sensor monitor module is working correctly. Note that only some variant of the NSA310 has the correct sensor tby bodhi - Debian
andsol Wrote: ------------------------------------------------------- > @bodhi, did you had a chance to check file copy > perfomance issue? Not yet! I will when I have a chance to install another HDD on it.by bodhi - Debian
@ziggy, Here is Dropbox link for the uImage file. uImage.3.18.5-kirkwood-tld-1.tar md5 dca3dc0027b848c6f7255c6963c8e0a8 Assuming /media/sdxx is where the USB drive mounted on your Intel box. Extract the 3.18.5 rootfs to it. And then cd /media/sdxx/boot mv uImage uImage.orig tar -xf uImage.3.18.5-kirkwood-tld-1.tarby bodhi - Debian
@andsol, What you should do is creating a new uImage on a 3.18.5 rootfs (you could do this on your 4.1 rootfs too, with the right command). If you don't have this rootfs, let me create this file for ziggy. @ziggy, There is no need to do anything extra, just use your newly created 3.18.5 rootfs. Dowload the new uImage, replace the existing /boot/uImage file with this new one.by bodhi - Debian
I've moved ziggy's booting problem to a new thread below: http://forum.doozan.com/read.php?2,23536by bodhi - Debian
Thanks andsol. I think for the 3.18.5 rootfs, ziggy only needs the uImage file that has the NSA325 DTB appended to it. It looks like the rest are OK.by bodhi - Debian
@edinger, > @bodhi: how can I restore old mtd0 when I cannot > boot into any system (stock or linux). I tried to > create one single ext3 usb stick with 8GB, but it > didn't boot either. Let's recap the problem and see if there is a simple fix that get you boot into Debian: - Create the 3.18.5 rootfs on a single Ext3 partition on USB drive. I think you've doby bodhi - Debian
> stucks on 100% (mostly kernel time in htop). > Seems related to DMA not activated - makes me > wonder if it's available on this platform? Interesting. I'll hook up a second HDD and see if I can find out why.by bodhi - Debian
rynax, > It could be I mixed up some > FDT/DTB/embbeded/seperated files which is not > compatible with the current uboot env settings. Yes, that was the problem. Your u-boot envs are set up for booting separated DTB. So the uImage should not have DTB appended.by bodhi - uBoot
@ziggy, Your execution of the steps are all correct, I did not see any thing wrong. So that points to the mkimage command, which might be not working correctly in that Debian 3.16.0-4-586 system. To make matter simpler, instead of using the 3.18.5 rootfs, use the Debian-3.16.0-kirkwood-tld-2 rootfs, as I recommended in this post: http://forum.doozan.com/read.php?4,23425,23427#msg-23427by bodhi - Debian
ziggy Wrote: ------------------------------------------------------- > When I want to follow step 4 in the instructions: > QuoteUpdated 24 Feb 2015: > This rootfs is the first Debian jessie rootfs in > my Kirkwood kernel/rootfs release series, and to > keep in sync with kernel > Linux-3.18.5-kirkwood-tld-1. > > I get an error when creating the uImage > >by bodhi - Debian
In Debian, fw_setenv ethaddr xx:xx:xx:xx:xxby bodhi - Rescue System
rynax Wrote: ------------------------------------------------------- > the current uenv_read_disk settings seems to only > read /boot/uEnv.txt while the booting device is > mmc? > No, it scans all kind of drives for uEnv.txt. > I have this setting in the /boot/uEnv.txt > > usb_root=LABLE=ROOTFS > > boot usb driver's partition lable is ROOTFS, &gby bodhi - uBoot
doomgiant Wrote: ------------------------------------------------------- > hi, bodhi > > I found one strange thing , after flash > Debian-3.16.0-kirkwood-tld-2 rootfs: > http://forum.doozan.com/read.php?2,12096 > > on each boot to debian, mac address of the > ethernet is different , is it a known behavior? > > Thanks. No, it is not a normal behaviorby bodhi - Rescue System
bastel, > Leds don't work as promised :) LED settings might be missing in the rootfs when you run with NSA320 :) Look for them in /sys/class/leds and set them in /etc/rc/local and /etc/init.d/halt (similar to other boxes).by bodhi - Debian
doomgiant Wrote: ------------------------------------------------------- > bodhi, > > Many thanks for your detail explanation, it has > been a great progress to make it work with > Debian. > > Thanks again! > > And does it mean this boot issue can be fixed on > 2014.07 U-Boot? We wont know for sure until after you have installed the new u-boot.by bodhi - Rescue System
pengu Wrote: ------------------------------------------------------- > you can tell us about that perhaps we can confirm > this till next weekend ;-) I meant ideas related the code to initialize the 8169. It is technical: Kirkwood GBE code is deeply woven into its whole design structure, and we can't easily take out this part and add RT8169. So my thought is we might try to noby bodhi - uBoot
pengu, > Net: No ethernet found. > Error occured, error code = 64 > No such device: egiga0 OK, it means that the RT8169 initialization was never called. > no, ethernet doesn't work in stick U-Boot, it > tries to initiate the PHY but this timed out, > because > stock U-Boot only supports the marvell not the > realtek lan chip Yes, I thought so, jusby bodhi - uBoot