Linux Kernel 6.11.6 Kirkwood package and Debian rootfs

Atesz Wrote:
-------------------------------------------------------
> Hi.
>
> Can I try this debian linux without install? So
> only run from USB pendrive? I will not touch
> original firmware and data in HDD. Can you help
> for me?

May be. Which plug do you have? are you running stock FW and OS?

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

@Atesz
in my expirience, it all depends on amout of time you are willing to put into it.
The way you can do it for sure is to pop open your device, find serial console pins, and connect serial TTL cable to it (few dollars on ebay). In that way, when device is starting, you can see all what is happening, and stop it before it loads its own system from ROM, and make it load yours from usb. Depending on the device itself, it may be that someone has some better hack-solution to avoid all that, and to just plug in USB drive and restart device, but...

However, Linux is not Windows or Mac, not user-friendly, and mostly - huge drain of your energy.
To ilustrate this: i just wanted to connect usb to serial converter cable. The thing that in Windows world its just a "install driver" thing, but here, with only vague anwsers available online, I ended up learning to compile kernel, and burning two weeks of life :)

But, eventually, device is not just a thing any more. It's now yours in a grater way than before.

So, google a bit to find all about your device and to be able to ask the right question.

I have a NSA320 with Original FW + FFP... Can you send a tutorial how to install to USB pendrive? Thanks!

Atesz,

See first post of this thread for how to download the latest rootfs (3.12.0-kirkwood-tld-3, updated 14 Dec 2013), and installation to a USB pen drive.

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



Edited 1 time(s). Last edit at 02/02/2014 11:15AM by bodhi.

@milhouse31,

I've ran the same dd test on the GoFlex Net USB thumb drive

root@HomeMBP:/localdisk# dd if=/dev/zero of=./test count=50000
50000+0 records in
50000+0 records out
25600000 bytes (26 MB) copied, 1.51012 s, 17.0 MB/s

No disk write slow down problem in 3.12.x or 3.13.1.

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

Kernel 3.13.1-kirkwood-tld-1 package was uploaded. Please see first post for download link.

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

odhi

Excellent instructions.
I upgraded from 2.6 to 3.13.1 .. no issues Pogo EO2 -- didn't make any changes to uboot or any other env.
then I went back and updated to wheezy and am doing fine.

Great Work-- accept my thanks!

S Sharma,

Cool! Glad it works well upgrading from squeeze…. Are you running old uBoot? if not sure, run this command

grep -a --null-data U-Boot /dev/mtd0ro

Note: don't be alarmed if seeing NAND error messages in dmesg when running this command! (the error was because mtd0 is not a normal partition).

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



Edited 1 time(s). Last edit at 02/04/2014 05:37AM by bodhi.

Heads up!!!

Kernel 3.13 seems to have problem with booting NFS root. As I can tell from serial console, it seems that initrd probed modules mvmdio and mv643xx_eth in wrong order.


kernel 3.12.0-kirkwood-tld-5

[    2.556718] udevd[62]: starting version 175
[    2.650231] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    2.736122] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    2.776651] libphy: orion_mdio_bus: probed
[

kernel 3.13.1-kirkwood-tld-1

[    6.479613] udevd[52]: starting version 175
[    6.557927] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    6.630018] libphy: PHY orion-mdio-mii:00 not found
[    6.634947] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[    6.659006] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    6.680708] SCSI subsystem initialized
[    6.742837] libphy: orion_mdio_bus: probed
……

Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done.
ipconfig: no devices to configure
ipconfig: no devices to configure

My conclusion is this was the problem because the eth0 device is not up early enough for the kernel to do ipconfig (even with static IP, somehow ipconfig was still executed when the kernel processes the command line arguments).

If you're not booting the kernel with NFS root, then no need to do anything. Booting with USB or SATA (i.e. local storage) is fine, no problem.

I think the solution to make it foolproof is: we need to change the kernel config to include mvmdio and mv643xx_eth in the kernel directly, not relying on initrd loading as modules. If anybody has different idea, please post.

I'll build another version to test this solution. Stay tuned!

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

Bodhi --

output of grep is :

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02U-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot BUG at %s:%d!


S Sharma

Problem with 3.13.1 NFS rootfs above solved!

I've rebuilt with mvmdio and mv643xx_eth modules included in the kernel directly (previously loaded by initrd), and no longer see the error, the kernel is now booting with NFS rootfs. Will upload newer version shortly.

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

Kernel 3.13.1-kirkwood-tld-2 package was uploaded. Please see 1st post for download link.

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

Rootfs Debian-3.13.1-kirkwood-tld-2 was uploaded. Please see 1st post for download link.

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

Hi there. I wanted to know if there i2s support is activated in the kernel! I want to use a I2S DAC with the goflex net.

Thanks in advance

bodhi - can you pls verify if hiddev is enabled in your kernel when it was compiled? i see its enabled in the config file (CONFIG_USB_HIDDEV = y) but when I plug in my UPS and run apcupsd, it cannot seem to find the UPS as hiddev seems to be missing. Thanks.

BigRon,

Unfortunately, I2S support is not turned on in the current kernel! But I could include that in the next released version.

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

Dave Wrote:
-------------------------------------------------------
> bodhi - can you pls verify if hiddev is enabled in
> your kernel when it was compiled? i see its
> enabled in the config file (CONFIG_USB_HIDDEV = y)
> but when I plug in my UPS and run apcupsd, it
> cannot seem to find the UPS as hiddev seems to be
> missing. Thanks.

Hi Dave,

Yes it is included. Did you see any thing in dmesg when you plug in the UPS?

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

Thank you bodhi for considering activating/implementing I2S Support into the next kernel Build!. Could you also implement I2C and SPDIF Support? ... If you can not implement the other features besides I²S its not that important.

Thank you really much for your help and work... Need to get into Kernel Kompiling so I dont have to ask anyone! ^^
Is there a good Tutorial on how to compile the Kernel for those ARM Devices!?

Thank you really much bodhi!

Greetings from Germany!
Ron

Bodhi - Thanks for the prompt response. Output from dmesg :

[52247.653548] usb 1-1.3: new low-speed USB device number 4 using orion-ehci
[52247.808800] usb 1-1.3: New USB device found, idVendor=051d, idProduct=0002
[52247.816143] usb 1-1.3: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[52247.823768] usb 1-1.3: Product: Back-UPS ES 550 FW:843.K2 .D USB FW:K2
[52247.830479] usb 1-1.3: Manufacturer: APC
[52247.834839] usb 1-1.3: SerialNumber: 4B0944P19754
[52247.938188] hidraw: raw HID events driver (C) Jiri Kosina
[52248.078356] usbcore: registered new interface driver usbhid
[52248.084361] usbhid: USB HID core driver

In an older kernel I'm using, I see hiddev in the dmesg
[228798.603432] usb 1-1.1: Manufacturer: American Power Conversion
[228798.609389] usb 1-1.1: SerialNumber: 8B0749R24292
[228798.617141] usb 1-1.1: configuration #1 chosen from 1 choice
[228799.790604] generic-usb 0003:051D:0002.0008: hiddev0,hidraw0: USB HID v1.10 Device [American Power Conversion Back-UPS XS 1300 LCD FW:836.H7 .D USB FW:H7 ] on usb-orion-ehci.0-1.1/input0

Also, when I do "ls -l /sys/bus/usb/drivers/" , I dont see hiddev listed
drwxr-xr-x 2 root root 0 Feb 9 10:07 hub
drwxr-xr-x 2 root root 0 Feb 9 10:07 usb
drwxr-xr-x 2 root root 0 Feb 9 10:07 usb-storage
drwxr-xr-x 2 root root 0 Feb 9 10:07 usbfs
drwxr-xr-x 2 root root 0 Feb 9 10:03 usbhid

Thanks.

@Dave & Ron,
I'll include the requested config options in the next release. You can test it, then!

@Dave,
I saw some unchecked config switches under HID. Perhaps include them will cover your UPS. But out of curiousity, if you still have the older kernel files, could you get the output of this grep and post it here? (where config-3.xx.x-kirkwood-xx is that kernel config file):

cat config-3.xx.x-kirkwood-xx | grep -i hid

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

bodhi Wrote:
> @Dave,
> I saw some unchecked config switches under HID.
> Perhaps include them will cover your UPS. But out
> of curiousity, if you still have the older kernel
> files, could you get the output of this grep and
> post it here? (where config-3.xx.x-kirkwood-xx is
> that kernel config file):
>

> cat config-3.xx.x-kirkwood-xx | grep -i hid
>

This was a pretty old kernel : config-2.6.32-5-kirkwood
CONFIG_BT_HIDP=m
CONFIG_HID_SUPPORT=y
CONFIG_HID=m
CONFIG_HIDRAW=y
CONFIG_USB_HID=m
CONFIG_HID_PID=y
CONFIG_USB_HIDDEV=y
# Special HID drivers
CONFIG_HID_A4TECH=m
CONFIG_HID_APPLE=m
CONFIG_HID_BELKIN=m
CONFIG_HID_CHERRY=m
CONFIG_HID_CHICONY=m
CONFIG_HID_CYPRESS=m
CONFIG_HID_DRAGONRISE=m
CONFIG_HID_EZKEY=m
CONFIG_HID_KYE=m
CONFIG_HID_GYRATION=m
CONFIG_HID_TWINHAN=m
CONFIG_HID_KENSINGTON=m
CONFIG_HID_LOGITECH=m
CONFIG_HID_MICROSOFT=m
CONFIG_HID_MONTEREY=m
CONFIG_HID_NTRIG=m
CONFIG_HID_PANTHERLORD=m
CONFIG_HID_PETALYNX=m
CONFIG_HID_SAMSUNG=m
CONFIG_HID_SONY=m
CONFIG_HID_SUNPLUS=m
CONFIG_HID_GREENASIA=m
CONFIG_HID_SMARTJOYPLUS=m
CONFIG_HID_TOPSEED=m
CONFIG_HID_THRUSTMASTER=m
CONFIG_HID_WACOM=m
CONFIG_HID_ZEROPLUS=m

Thanks.... Dave.

How do we setup the uboot for nfs booting? want to give it a shot to see how it goes.

Is it as simple as this in uboot setting the root device to something like this:

root=NFS=192.168.1.20:/(rootshare)



Edited 1 time(s). Last edit at 02/13/2014 07:49AM by Buttzy10169.

Buttzy,

It's much more complicate than that. See this thread by tsunulukai for a really good description of the procedure:
http://forum.doozan.com/read.php?3,12261,12261#msg-12261

One thing I did different from tsunulukai was I did not use tftp. Since the new u-Boot has nfs supports, the nfs rootfs coud be mounted directly. My u-Boot envs:

nfs_boot=run nfs_load_uimage; run nfs_load_uinitrd; run nfs_boot_debian
nfs_boot_debian=run nfs_bootm
nfs_bootcmd=run nfs_set_bootargs; run nfs_boot
nfs_bootm=bootm 0x800000 0xe00000
nfs_ipconfig=192.168.0.229:192.168.0.224:192.168.0.1:255.255.0.0:tldDebian2::off
nfs_load_uimage=nfs 0x800000 $nfs_server:$nfs_path/boot/uImage
nfs_load_uinitrd=nfs 0xe00000 $nfs_server:$nfs_path/boot/uInitrd
nfs_path=/srv/nfs/hosts/tldDebian2
nfs_server=192.168.0.224
nfs_set_bootargs=setenv bootargs console=$console root=/dev/nfs nfsroot=$nfs_server:$nfs_path,v3  rootfstype=nfs rootwait  ip=$nfs_ipconfig $mtdparts

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

Bodhi,

I'm interested in trying to get some kind of union filesystem working, and would prefer to build on your kernels rather than from scratch!

Would I be right in thinking that you are taking the upstream (kernel.org) kernel, applying the patches (that you include in the distribution), building according to the config file (also included)?

This is all a bit new to me, although I think I (now) have the environment to do it (given that I've successfully created a U-Boot with preboot, netconsole and IDE/USB support from the 1.1.4 sources), so any pointers would be appreciated!

Thanks,

Malc.

Malc,

> Would I be right in thinking that you are taking
> the upstream (kernel.org) kernel, applying the
> patches (that you include in the distribution),
> building according to the config file (also
> included)?

Yes indeed! the released tarball has everything you need to build the same kernel.

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

Hi bodhi,

thanks again for your last effort, finally last weekend I had some time to test your 3.13.1-kirkwood-tld-2 kernel
on NSA320 and iConnect,..

everything is working smoothly, as my iConnect still has a debian squeeze rootfs I had some
problems with the installation of the header files, because with this version 3.13.1 ncurses-5.9
is mandatory in the depends,.. (actually depends need libtinfo5 which is only available if ncurses-5.9 is installed)

so I had to backport ncurses-5.9 to squeeze from wheezy, if it's worth the effort is questionable because I would
always recommend full kernel sources for recompiling additional modules,..

(if one want's to recompile from headers the prevalant old arm mach/timex.h bug which has not been
corrected since 3.2 kernel versions is still occuring),..

best wishes pbg4



Edited 1 time(s). Last edit at 02/18/2014 03:32PM by pbg4.

pbg4,

Thanks for reporting your tests! is there a reason why you're using squeeze for iConnect?

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

Hi bodhi,

the only reason is that the iConnect is serving all the squeezebox stuff in my house, because it
has the smallest energy budget for running in 24/7 mode around the year,... so ist is long overdue that all the
masses of services running there should have been dist-upgraded to wheezy,.. that is the only reason,.. and the time for doing that,..

best wishes pbg4

I see. The squeezebox is stuck in squeeze :)

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

Hi bodhi,

..., definitely, but after the dist-upgrade I have to get a couple of wheezeboxes to sound right,.. :)

best wishes pbg4

p.s. when I send you the patch for the s2-liplianin dvb-usb-dw2102 per pm, would it be possible to include that
in further updates?? of course with maintenance on my side, perhaps it would make some users out there happy,..



Edited 1 time(s). Last edit at 02/21/2014 03:39PM by pbg4.