October 18, 2019, 07:36:52 pm

News:

Have you visited the Allwinner Chipset wiki? - http://linux-sunxi.org/


3.4.61+ kernel

Started by patwood, October 14, 2013, 11:57:19 pm

Previous topic - Next topic

patwood

October 14, 2013, 11:57:19 pm Last Edit: October 15, 2013, 12:01:44 am by patwood
I have uploaded a build of the 3.4.61 kernel pulled from the stage/sunxi-3.4 linux-sunxi git repository today (Oct 9th is the most recent commit): http://dl.cubieforums.com/patwood/A10-kernel-3.4.61.tar.gz

It has a few new drivers that people have requested (HIDRAW, HID_LOGITECH, and other Logitech drivers, Reiser FS, XFS).

The stage/sunxi-3.4 and cedar branches on my github repo at https://github.com/patrickhwood/linux-sunxi have been updated.

The 3.4.43 kernel is now deprecated.

Hannes Worst

Hi Patwood and others,

Some time ago I purchased a Cubieboard A10. I am using it with the Cubieez-image and recently I upgraded my kernel to 3.4.61+. Sadly now my soundcard (I am using the analog output) is no longer recognized as sunxi-CODEC but as sunxi-sndi2s. There are no controls in the alsamixer and there is no more sound. The guidelines about sound for the Cubieboard on the sunxi website do not give any clarification for this problem. Do you have any suggestions?

Thanks in advance and compliments for the great achievements on the Cubieboard-project.

patwood

Quote from: Hannes Worst on October 27, 2013, 04:11:43 pm
Hi Patwood and others,

Some time ago I purchased a Cubieboard A10. I am using it with the Cubieez-image and recently I upgraded my kernel to 3.4.61+. Sadly now my soundcard (I am using the analog output) is no longer recognized as sunxi-CODEC but as sunxi-sndi2s. There are no controls in the alsamixer and there is no more sound. The guidelines about sound for the Cubieboard on the sunxi website do not give any clarification for this problem. Do you have any suggestions?

Thanks in advance and compliments for the great achievements on the Cubieboard-project.


Looks like a bug in the latest sunxi-codec driver on A10. It fails to initialize and returns an error code (works fine on A20, though).  I've reported it on the linux-sunxi mailing list.

Lu6ith

November 05, 2013, 08:22:04 am #3 Last Edit: November 06, 2013, 03:47:14 am by Lu6ith
Hello Patwood,
Please let me know, what has happened with sw_ahci_platform module?
I suppose, it was replaced with libata driver, right ?
But my SATA drive stoped working  :(
Must I compile old (sw_ahci_platform) driver and load it ?

from dmesg:

[    1.412536] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 56
[    6.825021] ata1: link is slow to respond, please be patient (ready=0)
[   11.453181] ata1: COMRESET failed (errno=-16)
[   11.804436] ata1: SATA link down (SStatus 0 SControl 300)



please help

regards

patwood

Quote from: Lu6ith on November 05, 2013, 08:22:04 am
Hello Patwood,
Please let me know, what has happened with sw_ahci_platform module?
I suppose, it was replaced with libata driver, right ?
But my SATA drive stoped working  :(
Must I compile old (sw_ahci_platform) driver and load it ?

from dmesg:

[    1.412536] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 56
[    6.825021] ata1: link is slow to respond, please be patient (ready=0)
[   11.453181] ata1: COMRESET failed (errno=-16)
[   11.804436] ata1: SATA link down (SStatus 0 SControl 300)



please help

regards


This module is built into the kernel.  See the config file:

CONFIG_SW_SATA_AHCI_PLATFORM=y

Also, if you look in the /lib/modules/3.4.61-sun7i+/modules.builtin file, you'll see:

kernel/drivers/ata/libata.ko
kernel/drivers/ata/sw_ahci_platform.ko
kernel/drivers/ata/libahci.ko


I would say the messages you're seeing in dmesg indicate that the drive isn't being recognized because the driver is timing out after waiting 10 seconds for it to respond to some SATA command.

zefto

Hello,

I have the same problem, everything is configured right, power is sufficient (2,5A) but HD does not start. At boot up, I hear a 1 second buzz, like if electricity was accumulating, then the HD clicks and stay off.

[    3.730000] sw_ahci sw_ahci.0: controller can't do PMP, turning off CAP_PMP
[    3.740000] sw_ahci sw_ahci.0: forcing PORTS_IMPL to 0x1
[    3.750000] sw_ahci sw_ahci.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode
[    3.770000] sw_ahci sw_ahci.0: flags: ncq sntf pm led clo only pio slum part ccc
[    3.780000] scsi0 : sw_ahci_platform
[    3.790000] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 56
...

[    9.210000] ata1: link is slow to respond, please be patient (ready=0)
[   13.840000] ata1: COMRESET failed (errno=-16)
[   14.190000] ata1: SATA link down (SStatus 0 SControl 300)



Quote from: patwood on November 07, 2013, 07:39:02 pm
I would say the messages you're seeing in dmesg indicate that the drive isn't being recognized because the driver is timing out after waiting 10 seconds for it to respond to some SATA command.



Would you know how to fix this problem ?

patwood

Quote from: zefto on November 30, 2013, 12:44:31 pm
Hello,

I have the same problem, everything is configured right, power is sufficient (2,5A) but HD does not start. At boot up, I hear a 1 second buzz, like if electricity was accumulating, then the HD clicks and stay off.

Quote from: patwood on November 07, 2013, 07:39:02 pm
I would say the messages you're seeing in dmesg indicate that the drive isn't being recognized because the driver is timing out after waiting 10 seconds for it to respond to some SATA command.



Would you know how to fix this problem ?


This is probably caused by insufficient power to the SATA drive.  This has been discussed many times on this forum (just search for sata power).

Get an external power supply for it and don't power it through the cubieboard until you're sure it's working properly.

patwood

Quote from: Hannes Worst on October 27, 2013, 04:11:43 pm
Hi Patwood and others,

Some time ago I purchased a Cubieboard A10. I am using it with the Cubieez-image and recently I upgraded my kernel to 3.4.61+. Sadly now my soundcard (I am using the analog output) is no longer recognized as sunxi-CODEC but as sunxi-sndi2s. There are no controls in the alsamixer and there is no more sound. The guidelines about sound for the Cubieboard on the sunxi website do not give any clarification for this problem. Do you have any suggestions?

Thanks in advance and compliments for the great achievements on the Cubieboard-project.


This problem was fixed recently, and is included in the latest kernel I uploaded: http://www.cubieforums.com/index.php/topic,1076.0.html.

Hannes Worst

Hi Patwood,

thanks! I installed the 3.4.67+ kernel, and everything works perfectly now!