Release 3.2 kernel issue tracking thread

Linux-SWAT

Hardcore Member
Joined
Feb 13, 2010
Messages
8,240
New USB wifi dongle, firmware missing. I'm on 1.54 + some updates.

dmesg


[ 80.074493] usb 2-2: new high-speed USB device number 2 using ehci-omap
[ 80.249786] usb 2-2: New USB device found, idVendor=148f, idProduct=5370
[ 80.249816] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 80.249816] usb 2-2: Product: 802.11 n WLAN
[ 80.249816] usb 2-2: Manufacturer: Ralink
[ 80.249847] usb 2-2: SerialNumber: 1.0
[ 80.427703] cfg80211: Calling CRDA to update world regulatory domain
[ 80.652313] usb 2-2: reset high-speed USB device number 2 using ehci-omap
[ 80.851104] ieee80211 phy0: Selected rate control algorithm 'pid'
[ 80.852294] Registered led device: rt2800usb-phy0::radio
[ 80.852508] Registered led device: rt2800usb-phy0::assoc
[ 80.852661] Registered led device: rt2800usb-phy0::quality
[ 80.853546] usbcore: registered new interface driver rt2800usb
[ 81.108123] udev: renamed network interface wlan0 to wlan1
[ 142.129516] phy0 -> rt2x00lib_request_firmware: Error - Failed to request Firmware.


lsmod


rt2800usb 12447 0
rt2800lib 41437 1 rt2800usb
rt2x00usb 8322 1 rt2800usb
rt2x00lib 31930 3 rt2800usb,rt2800lib,rt2x00usb
mac80211 223525 3 rt2800lib,rt2x00usb,rt2x00lib
cfg80211 154825 2 rt2x00lib,mac80211

lsusb

Code:
Bus 002 Device 002: ID 148f:5370 Ralink Technology, Corp.
 

Crionic

Member
Joined
Mar 13, 2013
Messages
179
Location
Germany
Hm, you normally don't switch kernels just because there are newer ones available. You would do, if there are some major bug fixes or new features the hardware could benefit from.

As I don't follow kernel development, is there something important new?
 

Linux-SWAT

Hardcore Member
Joined
Feb 13, 2010
Messages
8,240
I follow new kernels features, and here and then i told myself some features would be cool on the OP.

Can't pinpoint anything from memory, but as you can imagine, there's a huge gap between 3.2 and 3.10.
 

notaz

Certified Guru
Joined
Aug 23, 2005
Messages
4,913
Location
Lithuania
Website
notaz.gp2x.de
I'm not, for now at least.

In longer term pandora needs device tree conversion to work on newer kernels, and that's significant amount of work which includes converting various drivers.
 
Last edited by a moderator:

fantomid

Very Active Member
Joined
Oct 10, 2011
Messages
287
Age
42
Location
Near Toulouse, France
I was aware of the DTS. It could be a good starting point working on Linux kernel.

Are the various OP drivers really separated from the mainstream kernel.

It may be a hard task to update all the OP drivers. Doesn't it ?
 

fantomid

Very Active Member
Joined
Oct 10, 2011
Messages
287
Age
42
Location
Near Toulouse, France
Thanks for the information.

Patches have to be created for the mainline kernel and apply during the patch step of bitbake (OE).

I will try.

Do you think it will be better to create incremental patches: from current OP kernel to 3.3 mainline kernel + OE patch or go straight to 3.10 mainline kernel + OE patch.

I don't remember when the device tree was introduced.
 

notaz

Certified Guru
Joined
Aug 23, 2005
Messages
4,913
Location
Lithuania
Website
notaz.gp2x.de
I'm not sure it's wort doing incremental steps, OMAP and other ARM SoCs were (and still are) going through heavy changes to support multiplatform kernels for distributions (before you had to build different kernel for each SoC and sometimes even board, now it's possible to use one kernel on many SoCs), so each step might be a lot o work and targeting single kernel version might be easier.

Also we are no longer OE patches, everything needed is applied directly to our tree at http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-kernel.git and built from there without any extra patching.
 

fantomid

Very Active Member
Joined
Oct 10, 2011
Messages
287
Age
42
Location
Near Toulouse, France
One more interrogation,

In a first step, will it be more easier to work on the 3.10 mainline kernel and apply patches building from the master git openpandora kernel ?

After stabilization, the modifications could be pushed back to the openpandora 3.10 branch kernel.
 

Linux-SWAT

Hardcore Member
Joined
Feb 13, 2010
Messages
8,240
Always the same kernel compilation problem.

Latest git on latest Slack, gcc 4.8.2.

This time, both uImage and zImage are produced.

Black screen, no SD activity.

Any idea ?
 
Last edited by a moderator:

Linux-SWAT

Hardcore Member
Joined
Feb 13, 2010
Messages
8,240
Always the same kernel compilation problem.

Latest git on latest Slack, gcc 4.8.2.

Compilation succeeds.

Black screen, no SD activity.

Any idea ?

Posted the kernel if it can be useful, just remove the .txt.
 

Attachments

Last edited by a moderator:

Linux-SWAT

Hardcore Member
Joined
Feb 13, 2010
Messages
8,240
Something went really weird !

I booted fine after a 3h compilation, then recompiled another kernel, just changing the -append.

Now 14h37 are elapsed, and i'm at the modules part, CC [M] drivers/md/md.o

The system is responsive, but i didn't try any pnd to bench or anything yet.
 
Last edited by a moderator:
Top