September 21, 2019, 01:31:46 pm

News:

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


3.4.67+ kernel

Started by patwood, November 24, 2013, 06:39:57 pm

Previous topic - Next topic

patwood

I have uploaded a build of the 3.4.67 kernel pulled from the stage/sunxi-3.4 linux-sunxi git repository today (Nov 13th is the most recent commit) + an update for the Realtek 8188eu wifi adapter: http://dl.cubieforums.com/patwood/A10-kernel-3.4.67.tar.gz

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

fattahi

Hi
Thank you for new compile...

I tried to use this kernel in more than 3 images I downloaded previously. One of those imgs is Cubieez published in this forum.

I have same problem when changing kernel on bootable MicroSD.
Most times system booting then freezing when loading LXDE or after Login to desktop.
Check me if I made mistake:
1- I removed all files in /lib/firmware/* & /lib/modules/* in second partition of MicroSD
2- I copied your extracted files and folders to firmware and modules whit keeping ownership to root:root
3- Remove uImage file of first partition
4- Put you uImage.3.4.67-sun4i+ file on first partition and rename it to uImage
5- sync, unmount and remove SD and put it to device and turn on...

some times I booted the system successfully and get your kernel version with 'uname -a'
and please let me know should I use config.3.4.67-sun4i+ somewhere?

fattahi

I think I had permission problem with LXDE!
because I was able to ssh or login from tty1 (Ctrl+alt+F1)
I run this command:
gconftool-2 -\-type bool -\-set /apps/gksu/sudo-mode true

I found the command from http://www.cubieforums.com/index.php/topic,10.msg388.html#msg388
It seems to be fixed my problem with LXDE loading...

carryonrewardless

Thanks for posting this kernel particularly with the DVB devices enabled. I have a Realtek 2832 device and some but not all of the required modules are present for this. However the dvb_usb_rtl28xxu module still needed to be modprobed. Does not load by itself. I will have a go at building the modules again from the kernel sources at sunxi and report back.

patwood

Quote from: carryonrewardless on February 07, 2014, 06:57:26 pm
Thanks for posting this kernel particularly with the DVB devices enabled. I have a Realtek 2832 device and some but not all of the required modules are present for this. However the dvb_usb_rtl28xxu module still needed to be modprobed. Does not load by itself. I will have a go at building the modules again from the kernel sources at sunxi and report back.

Does it load if you put it in /etc/modules?

carryonrewardless

February 08, 2014, 05:29:46 pm #5 Last Edit: February 08, 2014, 08:08:20 pm by carryonrewardless
Quote from: patwood on February 07, 2014, 11:59:19 pm
Does it load if you put it in /etc/modules?

No lsmod still shows no dvb modules. The device id by the way is 0bda:2838.
I have attached the lsmod from my laptop but it is on kernel 3.11.0-15-generic so it is indicative only.
Had trouble with the github .zip file for the kernel sources so my attempt to re-compile the modules crashed. Gave a symlink error: File name too long. Haven't found a good work around for that.
Thanks

patwood

If you want to build the kernel, follow the instructions in the linux-sunxi wiki or in several of the forum topics here and use git to download the sources.  The github .zip file generation, as you've found, doesn't work for the linux kernel.  I know it sounds like more work, but it really is the best way to do this.

carryonrewardless

Quote from: patwood on February 08, 2014, 10:08:18 pm
If you want to build the kernel, follow the instructions in the linux-sunxi wiki or in several of the forum topics here and use git to download the sources.  The github .zip file generation, as you've found, doesn't work for the linux kernel.  I know it sounds like more work, but it really is the best way to do this.

I have built a new set of modules successfully by cross compiling on the laptop after checking that the config had the required selections. The modinfo looked good but the modules still don't load and when I modprobe the dvb_usb_rtl28xxu it does not load the ir_sony_decoder etc. modules. I am thinking that means the 2830 and 28xxu soucre files will need to be edited for the 0bda:2838 device id.
lsmod only shows this after the modprobe:
dvb_usb_rtl28xxu       11708  0
rtl2830                 6743  1 dvb_usb_rtl28xxu
dvb_usb                17560  1 dvb_usb_rtl28xxu
dvb_core               92992  1 dvb_usb
rc_core                21478  2 dvb_usb_rtl28xxu,dvb_usb
cpufreq_userspace       3305  0
cpufreq_conservative     5570  0
cpufreq_powersave       1221  0
cpufreq_stats           2808  0
8188eu                498084  0


carryonrewardless

Does it need a patch like : https://linuxtv.org/patch/10406/
Its way beyond my skill level.

patwood

Quote from: carryonrewardless on February 13, 2014, 06:28:56 am
Does it need a patch like : https://linuxtv.org/patch/10406/
Its way beyond my skill level.


That patch is for autoloading the module when a USB device is plugged in.  It won't affect manual loading with modprobe.

Do you get any error messages from modprobe or anything in dmesg (dmesg | tail).

carryonrewardless

Thanks for helping Pat.
lsmod when device is inserted just shows:
usb 2-1.3.3: new high-speed USB device number 5 using sw-ehci
and when I modprobe dvb_usb_rtl28xxu there are no further dmesg entries but lsmod now looks like :
Module                  Size  Used by
dvb_usb_rtl28xxu       11708  0
rtl2830                 6743  1 dvb_usb_rtl28xxu
dvb_usb                17560  1 dvb_usb_rtl28xxu
dvb_core               92992  1 dvb_usb
rc_core                21478  2 dvb_usb_rtl28xxu,dvb_usb
cpufreq_userspace       3305  0
cpufreq_conservative     5570  0
cpufreq_powersave       1221  0
cpufreq_stats           2808  0
8188eu                498084  0

I found this
enum rtl28xxu_usb_table_entry {
        RTL2831U_0BDA_2831,
        RTL2831U_14AA_0160,
        RTL2831U_14AA_0161,
};

static struct usb_device_id rtl28xxu_table[] = {
        /* RTL2831U */
        [RTL2831U_0BDA_2831] = {
                USB_DEVICE(USB_VID_REALTEK, USB_PID_REALTEK_RTL2831U)},
        [RTL2831U_14AA_0160] = {
                USB_DEVICE(USB_VID_WIDEVIEW, USB_PID_FREECOM_DVBT)},
        [RTL2831U_14AA_0161] = {
                USB_DEVICE(USB_VID_WIDEVIEW, USB_PID_FREECOM_DVBT_2)},

        /* RTL2832U */
        {} /* terminating entry */

in rtl28xxu.c which seems to have no entry for 0BDA_2838 required for my device. Maybe this is the cause of my woes.

Rob

patwood

Not having the matching usb_device_id entry will prevent the driver from being loaded, but shouldn't affect it once it *is* loaded.  You could poke around to see if the driver does anything special with those constants in the device table, especially the ones for USB_VID_REALTEK and USB_PID_REALTEK_RTL2831U, which looks to match your vendor ID.

In any case, device ID entries look like this:

    { USB_DEVICE(0x0a5c, 0x21e1) },

so you can add one of your own if you want.

You might also want to make sure you run depmod on the Cubie after you copy over the .ko file.

carryonrewardless

This device being a Realtek Semiconductor Corp. RTL2838 DVB-T needs to load rtl2832.ko and r820t.ko as well as rtl2830.ko and dvb_usb_rtl28xxu
This site
http://openpli.org/forums/topic/20899-rtl2832u-chipset-support-proposal/page-6?hl=rtl2838
has a patch for 3.6 kernels but it won't work for me without the header and source files for rtl2832.ko etc..
Is there another way to bring in these files bearing in mind that I am cross-compiling from your sunxi kernel sources?
Perhaps I have to wait for some-one to develop a 3.6 kernel for this ARM device.

patwood

I doubt you'll see a 3.6 or 3.8 kernel for the AW chips.  The current mainlining efforts are with the 3.14 kernel.

carryonrewardless

Quote from: patwood on February 16, 2014, 12:39:17 am
I doubt you'll see a 3.6 or 3.8 kernel for the AW chips.  The current mainlining efforts are with the 3.14 kernel.

So what would you see as my best means of getting this device working? I can currently boot the AW with 3.0.62, 3.4.29 and 3.4.67 kernels.