Linux Kernel 6.9.6 Kirkwood package and Debian rootfs

@Bohdi,

First, thanks for the help.

I had the standard topkick 2.6.xx kernel that the tonidoplug2 ships with. When I installed, I did get two errors about missing symbolic links; others have mentioned them and said it still booted, so i paid it little mind.

thanks again

postman Wrote:
-------------------------------------------------------
> @Bohdi,
>
> First, thanks for the help.
>
> I had the standard topkick 2.6.xx kernel that the
> tonidoplug2 ships with. When I installed, I did
> get two errors about missing symbolic links;
> others have mentioned them and said it still
> booted, so i paid it little mind.
>
> thanks again

It is strange that you did not get any error regarding the inird.img. However, it will not work without the Topkick patch anyway! When I have some free time, I will take a look at the Arch Linux ARM patch to see if we can exract and build it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I was also not able to make theinitrd.img...

Okay really really noob question here. I have a goflex et device the one woth a single sata. Have setitup with arch basic install. Downloaded your debian image with kernel and extracted it to a newly formated ext3 pen drive. Now if I try to boot with usb the usb pen drive it wont how up wuth an ip anymore. Please guide... I want to boot debian on usb with a hdd on sata with all media.thanks for the great work you have putting in

Since you've installed Arch, your uBoot envs will probably need to be adjusted in order to boot Debian. Please login into Arch, and print your uBoot envs with
fw_printenv
and post the output here.

Usually it is just a couple of simple changes.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

[root@alarm ~]# fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=             ${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
[root@alarm ~]#

Sorry for taking this long.

dheerajjotwani Wrote:
-------------------------------------------------------
> [root@alarm ~]# fw_printenv
> Warning: Bad CRC, using default environment
> bootcmd=bootp; setenv bootargs root=/dev/nfs
> nfsroot=${serverip}:${rootpath}
> ip=            
> ${ipaddr}:${serverip}:${gatewayip}:${netmask}:${ho
> stname}::off; bootm
> bootdelay=5
> baudrate=115200
> [root@alarm ~]#
>
> Sorry for taking this long.

Looks like you have a problem with reading uBoot envs in Arch. You should fix that first, and then get a listing of uBoot envs. No way to tell why it's not booting Debian without seeing the envs.

Please create a new thread for this problem. I think we'll probably will be able to help, probably your /etc/fw_env.conf is not set correctly (but if not then you can get help at Arch site).

Hi Bodhi,

thank you for your work!!

when testing your kernel 3.8.11-kirkwood-tld3 I had trouble to bring up the phy interface of gigabit ethernet
on a NSA320 with stock uboot,

the attached patch was my quick solution, (however now autonegotiation is not working any longer),
the interface is set to full gigabit speed and full duplex, I can live with that,
this problem has also been discussed on the ARCH ALARM forum, it is a problem with powering up
the PHY, perhaps somebody has the same problem, so I would like to share the info here,..

best wishes, pbg4

p.s. there are also some trivial start value changes for the leds in the patch,..

p.p.s. a quick look in the config of the 3.8.11-kirkwood-tld-3 kernel revealed that
marvell phy is not!! included in the kernel,..

@bodhi: was this intention to use the generic mii_phy and not the mii_marvell_phy??,...
I'll have to test that and recompile the marvell_phy as a module and see if things with
the stock uboot get improved with mv643xx_eth on the nsa320,..

#
# MII PHY device drivers
#
CONFIG_AT803X_PHY=m
# CONFIG_AMD_PHY is not set
# CONFIG_MARVELL_PHY is not set



Edited 2 time(s). Last edit at 07/15/2013 02:21PM by pbg4.

@pbg4,

> p.p.s. a quick look in the config of the
> 3.8.11-kirkwood-tld-3 kernel revealed that
> marvell phy is not!! included in the kernel,..
>
> @bodhi: was this intention to use the generic
> mii_phy and not the mii_marvell_phy??,...
> I'll have to test that and recompile the
> marvell_phy as a module and see if things with
> the stock uboot get improved with mv643xx_eth on
> the nsa320,..

No, it was not intentional. It's been working with the generic mmi_phy for all other plugs, so we're not aware of that. I took a look back to 3.1.x kernel and we never use CONFIG_MARVELL_PHY. Did you look at Davy's rootfs config file to see if it was used?
UPDATED: looks like Davy did not have this set either.

BTW, could you post the link to Arch site thread about this problem?
Thanks,

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 07/16/2013 02:23AM by bodhi.

@bodhi,

pleases have a look at http://archlinuxarm.org/forum/viewtopic.php?f=27&t=3708&start=30
and http://archlinuxarm.org/forum/viewtopic.php?f=27&t=3851

where the power_resume.sh is discussed, the thread is rather messy so I simply quote
the statements from WarheadsSE:

"on the nsa320 we have also learned how to set the return from power loss behavior,
Apparently, the PHY eth stays happy if you turn resume ON. So, use that script to set it on (./power_resume.sh 1)"

and:

"Those GPIO pins are attached to a NV gate that controls the behavior of the PWM on-board the NSA320,
one is a "open for signalling" and the other is the "signal".

its also mentioned here (in french): http://cadcadet.blogspot.de/2013/03/installer-arch-linux-sur-le-zyxel-nsa320.html

in that respect the nsa320 is different from the other plugs, there is a mechanism in hardware which
affects powering up the whole unit from power loss plus activates the phy of egiga0, may be this also influences wol capabilities, I'll keep on testing and will report back,

best wishes pbg4



Edited 1 time(s). Last edit at 07/16/2013 08:20AM by pbg4.

bodhi Wrote:
> Dvb drivers probably were not included in kernel
> config (I don't have any video device attached so
> never noticed that). If anybody wanted to request
> some video drivers to be included, then please
> post the specific module info, I will recompile
> another version for it. Device name (as known to
> Linux) and the ko file name(s) are needed.

tks for the offer, I would like to request kernel support DVB-T USB tuners, namely for the AverMedia AVerTV Volar Black HD (A850) - af9013.
Other than that, works perfectly on NSA320.

I'm adding topkick plug, and most of multi-media supports to the kernel. Will upload new version in a couple days.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Bohdi,

Thanks much; this will be a great help, I'm sure.



Edited 1 time(s). Last edit at 07/25/2013 08:32AM by postman.

Kernel 3.9.11 version 1 was uploaded. Please see 1st post for download link.

Is there a new uboot that goes with or required for the new "Linux Kernel 3.9.11 Kirkwood package and rootfs" tarball?

I would also want to request the new kernel with DVB (c) support. Thank you very mich in advance.

Thanks for the update. I'm going to try it asap with my dvb-t tuner.
For who doesn't know how to install the 3.9.11 kernel:

tar -xjf linux-3.9.11-kirkwood-tld-1-bodhi.tar.bz2
dpkg -i linux-image-3.9.11-kirkwood-tld_1_1.0_armel.deb
dpkg -i linux-headers-3.9.11-kirkwood-tld_1_1.0_armel.deb
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.9.11-kirkwood-tld-1 -d /boot/vmlinuz-3.9.11-kirkwood-tld-1 /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.9.11-kirkwood-tld-1  -d /boot/initrd.img-3.9.11-kirkwood-tld-1 /boot/uInitrd

Edited 1 time(s). Last edit at 07/25/2013 07:09PM by David.

maihoamv & David,

The description and installation instruction is at the end of the 1st post :) burried under other updates! I guess I'll organize it again to make it easier to find. uBoot does not need to be replaced.

Quote

I have uploaded a Debian kernel package for 3.6.11-kirkwood which I've built with a collection of patches for GoFlex Home/Net, Pogoplug E02/Mobile/V4, iConnect, Dockstar, Sheevaplug and a few other Kirkwood plugs are already in the mainline. Since we don't have all Kirkwood FDT board files available yet (mainline has GoFlex Net and iConnect), I thought it would be useful for users who are looking to run kernel 3.6.x on Kirkwood boxes and can't wait for their board files to be submitted. This patched kernel basically de-selected FDT option in kernel config, and also has changed some FDT-only initialization code to remove compile problem. With this kernel we can run the Kirkwood boxes with arcNumber (i.e. mach-types implementation) like we've been doing.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

magnificent job, works as a charm on NSA320:

usb 1-1.3: dvb_usb_v2: 'AverMedia AVerTV Volar Black HD (A850)' successfully initialized and connected

tks a lot!

Rootfs 3.9.11 was uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I hadn't saw the instructions, maybe I did it too quick ;).
Instead, I had saw the kernel instructions for an older kernel , so it differ a bit in the file names. I thought that a lot of people doesn't even know how to correct it, so I modified it for the new kernel, good for dummies :P
I've finished the setup ,it works PERFECT with my setup (IT9135 DVB-T tuner and tvheadend) even its able to stream HD channels! :-D
Again, great work Bodhi, thanks for supporting and updating the kernel!



Edited 3 time(s). Last edit at 07/26/2013 02:33PM by David.

BigRon Wrote:
-------------------------------------------------------
> I would also want to request the new kernel with
> DVB (c) support. Thank you very mich in advance.

BigRon,

You did not see your device? there are DVB-C in the configuration items.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for your wonderful work.

I have two questions. There is a way where I can upgrade the roots because I have a lot of configurations and tools installed so I don't want to do all this work again. Any kind of magic? Second I can just install the kernel and not the rootfs?

I have a NSA320 with my own uBoot configuration.

Thanks in advance.

Ernesto

enavarrocu,

Yes, you can install the kernel only. Nothing will change but the kernel and related bootup configuration files.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

On vacation now. Can not wait to test the Terratec Cinergy HTC XS HD (DVB-C) with the kernel!

Thank you very much! :)

Thanks for building this. After far too much work I got it running on my nsa320 tonight.

My problem was that it was that the initramfs was trying to use a nonexistant /dev/root for the root filesystem, rather than honoring the kernel option I was passing in via uBoot.

Removing the flash-kernel package, updating the initramfs and turning it into a new uInitrd image finally solved the problem. I havent updated my kernel sinceI was running squeeze, so I think it must be some new behavior that came with Wheezy, either that, or I foolishly added the flash-kernel package without knowing why I needed it.

Anyway, thanks again, and I hope sharing my mistakes will save other people some time.

@eas,

Yes. I thought about putting a warning in the first post, but forgot to do it. Sometimes, dpkg -i command executes flash-kernel and does not deal with the error successfully, so it messes up initrd.img, but not always. Normally, people don't install flash-kernel so never have this problem. I recall that it did not cause problem for me in before 3.1.x kernel, perhaps something has changed after 3.1.x. Sorry you had to learn about it the hard way! and thanks for sharing this.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/02/2013 01:05AM by bodhi.

I've updated the first post to include the warning about flash-kernel. Thanks eas.
Sorry I also forgot the md5 for the 3.9.11 rootfs :) it's included now.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> @eas,
>
> Yes. I thought about putting a warning in the
> first post, but forgot to do it. Sometimes, dpkg
> -i command executes flash-kernel and does not deal
> with the error successfully, so it messes up
> initrd.img, but not always. Normally, people don't
> install flash-kernel so never have this problem. I
> recall that it did not cause problem for me in
> before 3.1.x kernel, perhaps something has changed
> after 3.1.x. Sorry you had to learn about it the
> hard way! and thanks for sharing this.

Thanks. To be clear, I didn't have any sort of error while generated the initrd.img. Its just that it couldn't mount the root file system due to flash-kernel forcing it to look for "/dev/root" rather than the bootparam I'd configured in uboot.

On the upside, I've learned about how the boot scripts work. Information I'm sure to forget before it comes up again.

I should probably file a bug with Debian because I don't think the behavior when flash-kernel is installed makes sense.

Hi bodhi,
thanks for the great service of providing an up-to-date kernel for the kirkwood platform.

I've installed it into a Debian7 USB-stick image and it works like a charm.

But I'm missing the table-nat module for netfilter. Could you be so kind, to bold a full set of netfilter modules?

Thanks,
Goetz.