Release 3.2 kernel issue tracking thread


Here's the lsmod of both with the device plugged in:

2.6


Module                  Size  Used by
mcs7830                 6848  0
bufferclass_ti          6036  0
omaplfb                 9408  0
pvrsrvkm              128296  2 bufferclass_ti,omaplfb
snd_seq                50656  0
snd_seq_device          7500  1 snd_seq
ipv6                  239592  10
fuse                   49244  2
ads7846                 9792  0
hwmon                   2516  1 ads7846
3.2


Module                  Size  Used by
hid_logitech_dj         8727  0
mcs7830                 5329  0
usbnet                 13207  1 mcs7830
ehci_hcd               32343  0
bluetooth             136791  0
omaplfb                 6739  0
pvrsrvkm              140050  1 omaplfb
zram                    9177  1
snd_seq                42877  0
snd_seq_device          4695  1 snd_seq
snd_pcm_oss            34139  0
snd_mixer_oss          12884  1 snd_pcm_oss
ipv6                  225065  10
fuse                   58870  2
ads7846                 8852  0
hwmon                   1003  1 ads7846
I'm not seeing any driver listed for 2.6 that I recognize for the keyboard, so I've also attached dmesg output for 2.6 when the device is attached.

Code:
[  410.917510] usb 1-2.4: configuration #1 chosen from 1 choice
[  410.937591] input: Logitech USB Receiver as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2.4:1.0/input/input8
[  411.000091] input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-ehci-omap.0-2.4
[  411.059020] input: Logitech USB Receiver as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2.4:1.1/input/input9
[  411.132843] input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-ehci-omap.0-2.4
[  411.196014] HID device claimed by neither input, hiddev nor hidraw
[  411.196899] usb 1-2.4: New USB device found, idVendor=046d, idProduct=c52b
[  411.196899] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  411.196929] usb 1-2.4: Product: USB Receiver
[  411.196929] usb 1-2.4: Manufacturer: Logitech
 
So 2.6 also complains with "HID device claimed by neither input, hiddev nor hidraw" but works?

Can you run "cat /proc/bus/input/devices" on 2.6?
 
Here's the logitech device outputs:

Code:
I: Bus=0003 Vendor=046d Product=c52b Version=0111
N: Name="Logitech USB Receiver"
P: Phys=usb-ehci-omap.0-2.4/input0
S: Sysfs=/devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2.4:1.0/input/input8
U: Uniq=
H: Handlers=kbd event6
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=c52b Version=0111
N: Name="Logitech USB Receiver"
P: Phys=usb-ehci-omap.0-2.4/input1
S: Sysfs=/devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2.4:1.1/input/input9
U: Uniq=
H: Handlers=kbd mouse3 event7
B: EV=1f
B: KEY=837fff 2c3027 bf004444 0 0 ffff0001 f84 8a27c000 667bfa d941dfed 9e0000 0 0 0
B: REL=1c3
B: ABS=1 0
B: MSC=10
 
Apologies if old news/irrelevant:

SZ1.52 / 3.2 Kernel

Just noticed that in a game I was trying to run, one of it's appdata folders contains a folder named 'DATA' - all in caps.

The game wouldn't work, booted with the old kernel to test if that was the issue and found that under the older kernel the same 'DATA' folder appears all lower case ('data') instead. Even if renamed, phenomenon persists after reboot.

I notice something similar with FUSE emulator file menu - all my spectrum games are organised in folders by genre, the folders are all named in Caps, but only appear correctly so under the 3.2 kernel, whereas they appear roughly half all upper and half all lower case under the old kernel, so alphabetical order is messed up too.

Just wondered if this had some bearing on 'missing rom' syndrome I and one or two others have experienced with Mame (some working roms vanish from file selector under new kernel).
 
What is the -cma kernel i've seens in the git repo ? Contiguous Memory Allocator ?

Will it be the next one ?
 
It's a test kernel for Cloudef to test omapdrm (more info at IRC #openpandora @ freenode).
 
Last edited by a moderator:
Hey Notaz, may I ask for DisplayLink support (again ;) ).

It would make the Pandiora so much more useful for office work.

Now as we have Libre Office I think it's also time to get HD output.

Your argument last time was that not much people would benefit from DisplayLink sou you'd better put you effort into stuff that's useful for more people.

I think that's not the case.

At FOSDEM I talked to some people about TV and HD output.

Most of them didn't know DisplayLink but as I explained what it is they liked it pretty much.

So if we would have some DisplayLink support on Zaxxon it's not enough.

But if we would have Full HD output also on the Pandora homepage and a thread here on the boards I think quite a lot people might use it.

Especially those who want to use the Pandora for business work.

For me it would be fantastic to make my presentations with my Pandora and need nothing more than DL and Pandora in classroom then.

Please think about it :) .

Maybe some voice of the community would be nice, too.

Do you think it's worth the effort to get DisplayLink which gives full HD (digital) and VGA (analog) output?

Not for games or movies, that's too slow, but for office work.

I already used it with Slackware and it was great. Firefox worked wonderful.
 
Last edited by a moderator:
Notaz, some more work for you:

1:

I don't need the hold button as it locks the keyboard.

For me it's not useful.

Maybe some settings menu which would allow you to switch the function would be nice.

I think of turning off the screen.

When listening to music with the Pandora speakers I can only turn brightness to "0" but not shut down the screen as it's when I close the lid.

It would save more battery if that''d be possible.

This might be useful for those who want to listen to music with their Pandora without headphones.

2:

Don't know if you know already.

Launcher is broken.

I've made some launcher on the Panel (Sysinfo, USB-Host, PND-Manager....)

It's one of those launchers which opens up a menu when you first click on it.

So the items work when I click on them with the mouse but don't when I select them with the D-Pad and press Enter.

If it doesn't take too long it'd be helpful to get those two things working.
 
Your post is badly offtopic, none of the issues you listed here are kernel related but I'll answer anyway.

1. For hold, you can edit /etc/pandora/conf/eventmap , if that doesn't work complain to skeezix, it was him who added it. Try changing it to call /usr/pandora/scripts/op_lid.sh .

2. I already told you I can't fix window manager and xfce bugs, it would take far too much time to read, understand and debug all that code. If you can find the same bugs in xfce bugtrackers, then fixes can be backported (probably).
 
Ah, ok.

Sorry.

Thanks for making it clear and your answers of course.
 
Last edited by a moderator:
Well I'll include the kernel driver in the next update, there is not much else I can do.

Hi Notaz,

in addition to including the kernel driver, there is an X driver needed.

We can probably compile that by ourselves and make a package for easy installation.

But maybe it would be good to include that in the next firmware version directly. Would you be the one to do that? I don't know.

The steps Linux-SWAT and I did for SL4P were those:



Code:
 
cd

git clone http://git.plugable.com/webdav/xf-video-udlfb/

cd xf-video-udlfb

export CFLAGS="-DPANDORA -O2 -pipe -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp"

export CXXFLAGS="-DPANDORA -O2 -pipe -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp"

./autogen.sh

./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc

make

mkdir /tmp/build

make install DESTDIR=/tmp/build/

cd /tmp/build/

makepkg -c y /tmp/xf-video-udlfb-201211-arm-1.tgz

installpkg /tmp/xf-video-udlfb-*-arm-1.tgz



 

Do you have an idea, when DisplayLink support will be available to the normal user via firmware flash/update?

 

Thanks!
 
Hi notaz,

   I've got a request for the next kernel please:

   CONFIG_BLK_DEV_DM=m

&

   CONFIG_DM_CRYPT=m

Cheers.
 
HMAC MD4 MD5 SHA1 SHA256 SHA512

CBC

AES

at least.
 
Last edited by a moderator:
Back
Top