K5 Debian on Paperwhite [video]

[twobob]

update: nope. It dies trying to do grayscale on the PC too:

me@dev ~/GIT/buildroot-k3-current/package $ Xephyr :1 -title "yayness" -screen 800x600 -cc 4 -grayscale -dpi 135 -nolisten tcp

Backtrace:
0: Xephyr (xorg_backtrace+0x37) [0x3fd1c7]
1: Xephyr (0x25e000+0x1a2f4a) [0x400f4a]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0x7e540c]
3: Xephyr (miInitVisuals+0x433) [0x30fcd3]
4: Xephyr (fbInitVisuals+0x5b) [0x2eb9ab]
5: Xephyr (fbFinishScreenInit+0xd8) [0x2edfe8]
6: Xephyr (0x25e000+0x84d51) [0x2e2d51]
7: Xephyr (AddScreen+0x16d) [0x2a91dd]
8: Xephyr (0x25e000+0x852cd) [0x2e32cd]
9: Xephyr (InitOutput+0x2b) [0x27ce1b]
10: Xephyr (0x25e000+0x1e740) [0x27c740]
11: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0xba84d3]
12: Xephyr (0x25e000+0x1ec39) [0x27cc39]
Segmentation fault at address (nil)

Caught signal 11 (Segmentation fault). Server aborting

will have to dig more... I feel that fixing this is probably partly key to implemented a slight variant as opposed to a full fledged replacement.

Thoughts on that?

[twobob]

okay... solution

[root@kindle root]# DISPLAY=:0 Xephyr :1 \
-title "L:A_N:application_ID:xephyr_O:R_PC:N" \
-screen 800x600 -grayscale -dpi 135 -nolisten tcp

that works...

cant use with a -cc flag (duh!) - thanks for the nice error

okay - onward... we have an example grayscale implementation.
We can mangle. we can cross compile.

take as example and neatly duplicate? cascade support as demonstrated by the grayscale implementation? Or just get hacking - find what works. backport it tidy later...

Starting point yeah? these are my thoughts

[twobob]

last thought.
-cc4
-grayscale
and "no definition"

color handling all have implications to be considered as some outputs don't work (visually) OOTB.

: ) as tested with blackbox.

[khseal]

Offtop
I tried to connect a USB flash drive to the internal usb.
But nothing happened.
Some errors:

Spoiler:

[root@kindle root]# lsusb
lsusb: /sys/bus/usb/devices: No such file or directory
[root@kindle root]# modprobe ehci-hcd
[root@kindle root]# lsusb
Bus 001 Device 001: ID 1d6b:0002

[root@kindle root]# dmesg | grep -i usb
regulator: VUSB2: 2400 <--> 2775 mV
regulator: VUSB: 0 mV
kernel: I perf:usb:usb_gadget_loaded=4.35 seconds:
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
usb usb1: USB disconnect, address 1
fsl-ehci fsl-ehci.1: USB bus 1 deregistered
usbcore: deregistering device driver usb
usbcore: deregistering interface driver usbfs
usbcore: deregistering interface driver hub
usb 1-1: device not accepting address 12, error -71
usb 1-1: new full speed USB device using fsl-ehci and address 13
usb 1-1: device not accepting address 13, error -71
hub 1-0:1.0: unable to enumerate USB device on port 1
USB Host suspended
USB Host resumed
usb 1-1: new full speed USB device using fsl-ehci and address 14
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: new full speed USB device using fsl-ehci and address 15
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: new full speed USB device using fsl-ehci and address 16
usb 1-1: device not accepting address 16, error -71
usb 1-1: new full speed USB device using fsl-ehci and address 17
usb 1-1: device not accepting address 17, error -71
hub 1-0:1.0: unable to enumerate USB device on port 1

[geekmaster]

Originally Posted by khseal

Offtop
I tried to connect a USB flash drive to the internal usb.
But nothing happened.
Some errors:

Spoiler:

[root@kindle root]# lsusb
lsusb: /sys/bus/usb/devices: No such file or directory
[root@kindle root]# modprobe ehci-hcd
[root@kindle root]# lsusb
Bus 001 Device 001: ID 1d6b:0002

[root@kindle root]# dmesg | grep -i usb
regulator: VUSB2: 2400 <--> 2775 mV
regulator: VUSB: 0 mV
kernel: I perf:usb:usb_gadget_loaded=4.35 seconds:
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
usb usb1: USB disconnect, address 1
fsl-ehci fsl-ehci.1: USB bus 1 deregistered
usbcore: deregistering device driver usb
usbcore: deregistering interface driver usbfs
usbcore: deregistering interface driver hub
usb 1-1: device not accepting address 12, error -71
usb 1-1: new full speed USB device using fsl-ehci and address 13
usb 1-1: device not accepting address 13, error -71
hub 1-0:1.0: unable to enumerate USB device on port 1
USB Host suspended
USB Host resumed
usb 1-1: new full speed USB device using fsl-ehci and address 14
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: new full speed USB device using fsl-ehci and address 15
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: new full speed USB device using fsl-ehci and address 16
usb 1-1: device not accepting address 16, error -71
usb 1-1: new full speed USB device using fsl-ehci and address 17
usb 1-1: device not accepting address 17, error -71
hub 1-0:1.0: unable to enumerate USB device on port 1

Did you supply +5v to the USB device? You could use a powered hub (perhaps), or a modified USB cable.

EDIT: 1d6b:0002 is a Linux Foundation USB 2.0 root hub.

[khseal]

Originally Posted by geekmaster

Did you supply +5v to the USB device? You could use a powered hub (perhaps), or a modified USB cable.

Yes, i'm supply +5v to the USB device. Have you tried to connect something?
I do not know what this error:
usb 1-1: device descriptor read/64, error -71

[geekmaster]

Originally Posted by khseal

Yes, i'm supply +5v to the USB device. Have you tried to connect something?
I do not know what this error:
usb 1-1: device descriptor read/64, error -71

According to this:
http://ubuntuforums.org/showthread.php?t=797789

Re: [SOLVED] device descriptor read/64, error -71 - USB problem
Did you try this:
http://www.mepis.org/node/5860 <== dead URL

In short as root:
echo Y > /sys/module/usbcore/parameters/old_scheme_first

More:
http://www.linuxforums.org/forum/har...rror-71-a.html

[khseal]

Quote:
Originally Posted by khseal
Yes, i'm supply +5v to the USB device. Have you tried to connect something?
I do not know what this error:
usb 1-1: device descriptor read/64, error -71

According to this:
http://ubuntuforums.org/showthread.php?t=797789
Quote:
Re: [SOLVED] device descriptor read/64, error -71 - USB problem
Did you try this:
http://www.mepis.org/node/5860 <== dead URL

In short as root:
echo Y > /sys/module/usbcore/parameters/old_scheme_first
More:
http://www.linuxforums.org/forum/har...rror-71-a.html

I'm reverse Rx and Tx or other flash.
[root@kindle root]# lsusb -v
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 0951:1603

But how now this USB flash mount?

[eureka]

Originally Posted by khseal

I'm reverse Rx and Tx or other flash.
[root@kindle root]# lsusb -v
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 0951:1603

But how now this USB flash mount?

USB mass storage support is disabled in stock KT kernel config. You should recompile kernel to add handling of USB disks.

[khseal]

Originally Posted by eureka

USB mass storage support is disabled in stock KT kernel config. You should recompile kernel to add handling of USB disks.

I've never compiled a kernel.

[knc1]

Originally Posted by khseal

I've never compiled a kernel.

A great learning opportunity.
There is over a decade of help available on the 'net for that subject.

[twobob]

Originally Posted by khseal

I've never compiled a kernel.

Here's one I did earlier. (For the 3) http://www.mobileread.com/forums/sho...d.php?t=188031
Chris's OTG USB 4 info http://www.christian-hoff.com/?p=44
The USB work is on the cards RSN.

Cheers.

and a couple of notes I found about similar errors with OTG http://www.raspberrypi.org/phpBB3/vi...p?f=53&t=14254
and this (worth translating http://labs.consol.de/lang/en/blog/r...piegel-sticks/ )

also did you try as root:
echo Y > /sys/module/usbcore/parameters/old_scheme_first
or similar pokes to that area...
echo -1 >/sys/module/usbcore/parameters/autosuspend

Anyways I am just attempting to nudge you in the right direction. hope you find some joy.

[khseal]

Need module driver for kernel usb-storage.ko =(

and a couple of notes I found about similar errors with OTG http://www.raspberrypi.org/phpBB3/vi...p?f=53&t=14254
and this (worth translating http://labs.consol.de/lang/en/blog/r...piegel-sticks/ )

also did you try as root:
echo Y > /sys/module/usbcore/parameters/old_scheme_first
or similar pokes to that area...
echo -1 >/sys/module/usbcore/parameters/autosuspend

Anyways I am just attempting to nudge you in the right direction. hope you find some joy.

I'm solved problem...

[twobob]

Just so I understand - when you say "Solved" do you mean "Fixed" - like it works now - or do you mean "Understood": as in - it still doesn't work but you know why...

usb-storage.ko
you want one? or you have one?

Fairly sure I could build one of them if you don't, will have a nose around

[khseal]

Originally Posted by twobob

Just so I understand - when you say "Solved" do you mean "Fixed" - like it works now - or do you mean "Understood": as in - it still doesn't work but you know why...

usb-storage.ko
you want one? or you have one?

Fairly sure I could build one of them if you don't, will have a nose around

My English is very bad. =)
I realized what was causing the problem and fix it.

I'm reverse Rx and Tx or other flash.
[root@kindle root]# lsusb -v
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 0951:1603

I need a module usb-storage.ko. I think it is enough only this module. I hope that in the firmware is a function depmod. If you can get it that would be good. I tried to compile the kernel but still did not succeed.