Linux Kernel 6.7.5 Kirkwood package and Debian rootfs

kernel 4.6 is out ...
it's running on my NSA325 and iconnect ... let's see ..
The Hauppauge WinTV MiniStick 2 which I'm using for several months with several kernel versions isn't working anymore ..
The firmware cannot be loaded .. (testet two different versions, no luck)
Unfortunately, I cannot find any of my other sticks, so I cannot change.

[ 1058.488465] usb 1-1.3: new high-speed USB device number 5 using orion-ehci
[ 1058.613242] usb 1-1.3: New USB device found, idVendor=2040, idProduct=f900
[ 1058.624403] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1058.644422] usb 1-1.3: Product: WinTV-Ministick 2
[ 1058.652416] usb 1-1.3: Manufacturer: Hauppauge
[ 1058.664407] usb 1-1.3: SerialNumber: 000DFE8C7D80
[ 1058.681675] usb 1-1.3: dvb_usb_af9035: prechip_version=83 chip_version=02 chip_type=9135
[ 1058.701376] usb 1-1.3: dvb_usb_v2: found a 'Hauppauge WinTV-MiniStick 2' in cold state
[ 1058.716178] usb 1-1.3: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9135-02.fw'
[ 1058.790534] dvb_usb_af9035: probe of 1-1.3:1.0 failed with error -5

let's see later .. ;-)


Edit

with kernel 4.5.4 and after two restarts it's working again

[   12.603699] usb 1-1.2: dvb_usb_af9035: prechip_version=83 chip_version=02 chip_type=9135
[   12.662092] usb 1-1.2: dvb_usb_v2: found a 'Hauppauge WinTV-MiniStick 2' in cold state
[   12.773961] usb 1-1.2: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9135-02.fw'
[   12.948436] usb 1-1.2: dvb_usb_af9035: firmware version=3.40.1.0
[   12.976153] usb 1-1.2: dvb_usb_v2: found a 'Hauppauge WinTV-MiniStick 2' in warm state
[   12.994935] usb 1-1.2: dvb_usb_af9035: [0] overriding tuner from 00 to 60
[   13.031671] usb 1-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[   13.076727] DVB: registering new adapter (Hauppauge WinTV-MiniStick 2)
[   13.145692] af9033 1-0038: firmware version: LINK 3.40.1.0 - OFDM 3.40.1.0
[   13.167965] af9033 1-0038: Afatech AF9033 successfully attached
[   13.182569] usb 1-1.2: DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))...
[   13.257792] it913x 1-001c: ITE IT913X BX successfully attached
[   13.303056] Registered IR keymap rc-empty
[   13.316012] input: Hauppauge WinTV-MiniStick 2 as /devices/platform/ocp@f1000000/f1050000.ehci/usb1/1-1/1-1.2/rc/rc0/input1
[   13.339333] rc rc0: Hauppauge WinTV-MiniStick 2 as /devices/platform/ocp@f1000000/f1050000.ehci/usb1/1-1/1-1.2/rc/rc0
[   13.358682] usb 1-1.2: dvb_usb_v2: schedule remote query interval to 500 msecs
[   13.366107] usb 1-1.2: dvb_usb_v2: 'Hauppauge WinTV-MiniStick 2' successfully initialized and connected
[   13.378399] usbcore: registered new interface driver dvb_usb_af9035

my kirkwood kernel builds
my oxnas kernel builds
Tvheadend Kirkwood Debian packages

my kirkwood devices:
- 1x hp t5325 (1,2 GHz, 88F6281 / 512 MB / 4x USB)

my oxnas devices
- 2x pogoplug

my dove devices
- 2x Chip PC LXD8541 (800 MHz, 88F510 / 1024 MB / 6x USB)
- 1x Wyse T50 (1,0 GHz, 88F510 / 1024 MB / 4x USB)

my amlogic devices
- several s905x / s912 devices

my x86 devices
Dell Optiplex 3020 (3,4 GHz, 2C/4T / Haswell / 4096 MB 2x Intel I210 / PicoPSU)
PC 1: (ASRock Z390 itx/ac / i3-8100, 3,6 GHZ, 2C / 4T / 32 GB RAM / Nanum SE-P180Q
PC 2: (ASRock Fatal1ty X470 Gaming-ITX/ac / Ryzen 5 2600, 3,4 GHz, 6C 12T / 32 GB RAM / Radeon RX550 2 GB / Be Quiet! BN229



Edited 2 time(s). Last edit at 05/16/2016 06:11PM by pengu.

bodhi Wrote:
-------------------------------------------------------
> Last post was moved to its own topic.
>
> If you have problem booting and need help, please
> make a new topic. This is the kernel release
> thread !

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

news news ..

"hwmon" is now working on NSA320 with kernel 4.6

[    0.000000] Linux version 4.6.0-kirkwood-rm-1 (root@debianNSA325v2) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon May 16 16:26:59 CEST 2016
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Zyxel NSA320
...
...
[    2.391951] nsa3xx-hwmon nsa3xx-hwmon: initialized

...


sensors
nsa3xx-isa-0000
Adapter: ISA adapter
Chassis Fan:        2100 RPM
System Temperature:  +38.3°C  

Kernel linux-4.6.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.

NOTE:

I would like to see reports from Zyxel NSA320 users in particular, whether it was successful or there is any problem.

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



Edited 1 time(s). Last edit at 05/20/2016 04:53PM by bodhi.

Hallo Bodhi,

tried to install your kernel 4.6 to my pogoplug e02 running on kernel 4.5

I think there are 2 errors in your documentation to unstall it:

I think in line:

mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.6.0-kirkwood-tld-1 -d vmlinuz-6.1.0-kirkwood-tld-1 uImage

vmlinuz-6.1.0-kirkwood-tld-1 should be vmlinuz-4.6.0-kirkwood-tld-1

and after the line:

mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.6.0-kirkwood-tld-1 -d initrd.img-4.6.0-kirkwood-tld-1 uInitrd

my pogo don´t want to go further, because it hasn´t found initrd.img-4.6.0-kirkwood-tld-1

So badly for me no success.

Rainer

Thanks for reporting the typo Rainer.

The file initrd.img-4.6.0-kirkwood-tld-1should be there after you run dpkg. Look in your /boot directory

ls -l *4.6.0-kirkwood-tld*

Do you see it? should look like this:

-rw-r--r-- 1 root root  144044 May 18 03:01 config-4.6.0-kirkwood-tld-1
-rw-r--r-- 1 root root 7542748 May 19 21:48 initrd.img-4.6.0-kirkwood-tld-1
-rw------- 1 root root 2315651 May 18 06:34 System.map-4.6.0-kirkwood-tld-1
-rw------- 1 root root 3257040 May 18 06:34 vmlinuz-4.6.0-kirkwood-tld-1

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



Edited 1 time(s). Last edit at 05/22/2016 04:42PM by bodhi.

Hi bodhi,

Adam Bakers patch for nsa320-hwmon after long reviews got finally upstream just in time for 4.6,..

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/diff/drivers/hwmon/nsa320-hwmon.c?id=v4.6&id2=v4.5

what puzzles me is that pengu reports nsa3xx-hwmon is working, this is the naming of my intermediate
patch which is now obsolete,.. did you incorporate this intermediate patch in 4.6 ?

will have a look the next days and let you know,..

best wishes pbg4

Hi pbg4,

I think I did. It was carried over from 4.5. Please take look at the patch and let me know if I should remove it from the kernel and use the mainline.

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

Hey bodhi, installed your new 4.6 kernel (big thanks btw!), and dmesg gives me the following warning:

[    2.776931] [Firmware Warn]: /ocp@f1000000/mdio-bus@72004/ethernet-phy@1: Whitelisted compatible string. Please remove

At the moment everything works fine, nothing to complain. Wanted to know if i can ignore this warning.

Thanks in advance!

LE: Unit is NSA310s



Edited 1 time(s). Last edit at 06/01/2016 04:08PM by JohnnyUSA.

JohnnyUSA Wrote:
-------------------------------------------------------
> Hey bodhi, installed your new 4.6 kernel (big
> thanks btw!), and dmesg gives me the following
> warning:
>

> [    2.776931] [Firmware Warn]:
> /ocp@f1000000/mdio-bus@72004/ethernet-phy@1:
> Whitelisted compatible string. Please remove
>

>
> At the moment everything works fine, nothing to
> complain. Wanted to know if i can ignore this
> warning.
>
> Thanks in advance!
>
> LE: Unit is NSA310s

That's OK. But I'll take a look why it shows in new kernel.

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

> >

> > [    2.776931] [Firmware Warn]:
> > /ocp@f1000000/mdio-bus@72004/ethernet-phy@1:
> > Whitelisted compatible string. Please remove
> >

> >
> > At the moment everything works fine, nothing to
> > complain. Wanted to know if i can ignore this
> > warning.


I've seen that too (when using old DTB, and the network device appears .. with new (4.5 and 4.6 it doesn't sorry that I doesn't mention this earler

Hi,
various procedures are applicable when is there the original firmware?
I've Iomega ix4-200d with the originale firmware version 2.1.48.30125.

If not, please help me with the complete procedure for apply your kernel..

Regards
Francesco

Francesco,

> various procedures are applicable when is there
> the original firmware?

Yes.

> I've Iomega ix4-200d

Pay attention to the DTB for your box in the instruction in the first post.

Quote

/boot/dts/kirkwood-iomega_ix4_200d.dtb

Use the latest rootfs, and remember to append the DTB (4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier)) since you are booting with stock u-boot.

Quote

Latest rootfs: Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (20 Feb 2016)

If you have problem while installing new rootfs, please start a new thread in this forum.

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



Edited 1 time(s). Last edit at 06/12/2016 06:27PM by bodhi.

Hi!

I have a ZyXEL NSA320S and I am interested to boot up a Debian system eith a fresh kernel on it. Because the old (2.6.31.8) kernel has a lot of disabled thing (for example the wifi support) and if I create a custom kernel it works, but a bit buggy...

So I decided to move to a Debian system and I found this nice article. :)

I have a TTL-USB cable and I have a basic knowledge in kernel flash, but I don't know what is the fdt and I think the default (stock) u-boot doesn't supports the tld... So if my theory is true I have to change the BL (u-boot). But I don't know how to do this and I am a bit worried, I don't want a brick. Or it isn't needed?

If I didn't misunderstood sg the ethernet won't work if I install this? But temporarily Can I use my usb wifi dongle (rt8192cu module)?

And Can I install the whole system to a pendrive and it doesn't overwrite my stock uimage and the others?

And is my HDD will be formatted?

It uses glibc or uClibc?

Thanks for Your work and sorry for my question flood (and my bad English too)...

Ps: If You need any information please tell me what is needed for You! ;)

Mr Dini Wrote:
-------------------------------------------------------
> Hi!
>
> I have a ZyXEL NSA320S and I am interested to boot
> up a Debian system eith a fresh kernel on it.
> Because the old (2.6.31.8) kernel has a lot of
> disabled thing (for example the wifi support) and
> if I create a custom kernel it works, but a bit
> buggy...
>
> So I decided to move to a Debian system and I
> found this nice article. :)
>
> I have a TTL-USB cable and I have a basic
> knowledge in kernel flash, but I don't know what
> is the fdt and I think the default (stock) u-boot
> doesn't supports the tld... So if my theory is
> true I have to change the BL (u-boot).

Not necessary.

But I don't
> know how to do this and I am a bit worried, I
> don't want a brick. Or it isn't needed?
>
> If I didn't misunderstood sg the ethernet won't
> work if I install this? But temporarily Can I use
> my usb wifi dongle (rt8192cu module)?
>

Ethernet does work in rootfs 4.4. And in kernel 4.6.

> And Can I install the whole system to a pendrive
> and it doesn't overwrite my stock uimage and the
> others?

Yes.

>
> And is my HDD will be formatted?

No.

>
> It uses glibc or uClibc?
>
> Thanks for Your work and sorry for my question
> flood (and my bad English too)...
>
> Ps: If You need any information please tell me
> what is needed for You! ;)

See this thread : http://forum.doozan.com/read.php?2,19720,28059#msg-28059
For how people install latest Debian rootfs (link in my signature) to run with stock u-boot.

When you're ready to install, post what you are going to do in that nsa320s thread, and I will check it for you.

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

I'm struggling here at the mkimage stage for initrd.

I've downloaded the kernel files from dropbox, have extracted everything I can but cannot find anywhere the initrd.img file needed by mkimage.

Can anyone point me in the right direction?

Ah - I see what I was doing wrong. I was trying to extract the files from the .deb file using ar, but we need to use dpkg because it does a whole load of post-processing on those files and generates the init image.

Was a bit chicken-and-egg for a while as my pogo fs has put itself into protective-read-only mode due to SD errors, but I've cloned it onto a spare card and am able to run dpkg on that.

Richard Wrote:
-------------------------------------------------------
> Ah - I see what I was doing wrong. I was trying to
> extract the files from the .deb file using ar, but
> we need to use dpkg because it does a whole load
> of post-processing on those files and generates
> the init image.
>
> Was a bit chicken-and-egg for a while as my pogo
> fs has put itself into protective-read-only mode
> due to SD errors, but I've cloned it onto a spare
> card and am able to run dpkg on that.

Cool!

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

Last post moved to its own topic.

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

Hi, is the Lenovo Iomega ix4-300d supported?

I only see a file named kirkwood-iomega_ix4_200d.dtb, not any kirkwood-iomega_ix4_300d.dtb.

CableCat Wrote:
-------------------------------------------------------
> Hi, is the Lenovo Iomega ix4-300d supported?
>
> I only see a file named
> kirkwood-iomega_ix4_200d.dtb, not any
> kirkwood-iomega_ix4_300d.dtb.

No. I don't have the Iomega ix4-300d and it has not been supported in the mainline, either.

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

Thank you for your reply :)

Which 4 drive model would you recommend?
I was thinking about a used ix4-200d. But I would like at least 1GB of RAM.

CableCat,

I don't have any recommendation for a 4-bay NAS.

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

Thanks for the credit, bodhi :)
Will continue to test

megal0maniac Wrote:
-------------------------------------------------------
> Thanks for the credit, bodhi :)
> Will continue to test

You're welcome! You guys did most of the testing. Too bad the uboot ethernet switch driver was not quite ready. I am still waiting for it to become mainlined. Hopefully when that happens more people will be interested.

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

bodhi Wrote:
-------------------------------------------------------
> No. I don't have the Iomega ix4-300d and it has
> not been supported in the mainline, either.

The ix4-300d uses a MV78230 SoC. In the Linux kernel it goes under the name mv78xx0.

CableCat Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > No. I don't have the Iomega ix4-300d and it has
> > not been supported in the mainline, either.
>
> The ix4-300d uses a MV78230 SoC. In the Linux
> kernel it goes under the name mv78xx0.

So it is Armada SoC, not Kirkwood.

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

bodhi Wrote:
-------------------------------------------------------
> CableCat Wrote:
> --------------------------------------------------
> -----
> > bodhi Wrote:
> >
> --------------------------------------------------
>
> > -----
> > > No. I don't have the Iomega ix4-300d and it
> has
> > > not been supported in the mainline, either.
> >
> > The ix4-300d uses a MV78230 SoC. In the Linux
> > kernel it goes under the name mv78xx0.
>
> So it is Armada SoC, not Kirkwood.


it is, see:

https://github.com/benoitm974/ix4-300d/wiki

Last post moved to its own thread.

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

In case anybody wondering, I've built kernel 4.7 without incidence. However it does not not have any thing interesting added, so decided not to release it and wait for 4.8.

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