[support-gang] using usb2vga with 11.2.0 and 10.1.3

Kevin Gordon kgordon420 at gmail.com
Wed Jun 22 07:39:58 EDT 2011


Update:

rather than power off, I decided to do another ctl-alt-f2 at the snag of the
'stall point' below, and got a bash prompt,

entering  stop prefdm there then returns "unknown instance" and a bash
prompt

tried the insmod tests from there, loaded successfully with the following
output:

usb 1-2: USB2VGA dongle found at address 3
usb 1-2: Allocated 8 output buffers
usb 1-2: 8Mb 1 ch/1 r SDR SDRAM, bus width 32
usbcore: registered new interface driver sisusb

tried the rmmod, got the following output:

usbcore: deregistering interface driver sisusb

did it about 10 times with various 1-10 second waits before and after each
step,  always results as above.

KG








On Wed, Jun 22, 2011 at 7:23 AM, Kevin Gordon <kgordon420 at gmail.com> wrote:

> DSD:
>
> Hit a snag on your method below:
>
> Moved the .ko
>
> rebooted
>
> rebooted with USBVGA2 plugged in, booted successfully with no VGA display,
> as you predicted
>
> ctl-alt-f2
>
> hit enter to login, gives me the bash # prompt
>
> entering stop prefdm at the prompt does not then return a # prompt, just
> shoots a bunch of text console lines, ending with
>
> Starting crond:
> [21.486698] input: olpc-kbdshim virtual input as
> /devices/virtual/input/input6
> [97.220326] dcon_freeze_store: 0
>
> any subsequent input echoes but does nothing, have to power off by the
> power button
>
> Any suggestions?
>
>
>
>
> More specific instructions for this:
>
>>
>> Boot without USBVGA connector attached. Go to a root terminal and move
>> sisusbvga.ko to /root:
>> # mv /lib/modules/*/kernel/drivers/usb/misc/sisusbvga/sisusbvga.ko /root
>>
>> Power off the system, connect USBVGA, boot. It should boot
>> successfully, but without any VGA output. Press ctrl+alt+f2 to get to
>> a root terminal, and stop X/sugar with:
>> # stop prefdm
>>
>> Now load the sisusbvga driver manually and see if it hangs:
>> # insmod /root/sisusbvga.ko
>>
>> Wait a few seconds, see if the system is hung or if you can still type
>> on the console.
>>
>> If you can still type, unload the module:
>> # rmmod sisusbvga
>>
>> and now try loading/unloading a few more times with a few seconds
>> pause between each step.
>> # insmod /root/sisusbvga.ko
>> ...
>> # rmmod sisusbvga
>> ...
>> # insmod /root/sisusbvga.ko
>> ...
>> # rmmod sisusbvga
>> ...
>> etc
>>
>> The idea is to find out whether the system hang is caused by the
>> loading of sisusbvga. It might not hang first time, may require a few
>> attempts, hence the repeated loading.
>>
>> Thanks,
>> Daniel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/devel/attachments/20110622/1a326000/attachment.htm 


More information about the Devel mailing list