Public bug reported:
Using jaunty on OQO 01. LCD is 800X480 (common for Palmtops and some Netops).
Driver goes to 800X600 and screen is black.
xorg.conf Modeline to manually provide proper panel size is ignored by
the driver.
** Affects: xserver-xorg-video-siliconmotion (Ubuntu)
Importance
** Attachment added: "Xorg.log"
http://launchpadlibrarian.net/24372174/Xorg.log
--
siliconmotion driver fails to recognize 800x480 panel size
https://bugs.launchpad.net/bugs/348147
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Conducted a bunch of experiments, still unable to get the driver to
work.
- Tried Option 'PanelSize" "800x480". Driver seems to create the right
Modeline, but I still get a garbled screen for a few second (horizontal lines)
then black.
- May mean that I am hitting a different bug.
Attached lspc
** Summary changed:
- siliconmotion driver fails to recognize 800x480 panel size
+ siliconmotion driver fails to start on 800x480 panel
--
siliconmotion driver fails to start on 800x480 panel
https://bugs.launchpad.net/bugs/348147
You received this bug notification because you are a member of Ub
Problem was a bug that prevented the LCD from being turned on. Solved on
3.19.09 in freedesktop.org git head.
http://cgit.freedesktop.org/xorg/driver/xf86-video-
siliconmotion/commit/?id=6691678b5f04d52a1e08f9eaa6d511df9b7eeb4d
Compiled and successfully tested on my system.
--
siliconmotion dri
Experiencing same problem on Lenovo X200 with embedded Ericsson F3507g
card. Using 2.6.28-13-generic.
Used to work great, now does not show up in lsusb and
/sys/devices/platform/thinkpad_acpi/wwan_enable does not exist.
I have not been able to make the card work by hibernating/resuming.
Makes th
Correcting my previous post.
In fact I am running: 2.6.28-11-generic #43~undervolt1-Ubuntu SMP Fri
Apr 17 18:32:02 UTC 2009 i686 GNU/Linux. Because I use the phc patches
to undervolt my CPU.
Since my kernel has NOT been upgraded, it suggests that something else
has gone wrong in the last few week
Thank you for your guidance. Below my observations:
1. Set to hidden, radio blocked or something like that in the BIOS setup
screens (usually cannot be reenabled by software until reconfigured in
BIOS);
>Disabled/re-enabled wireless in BIOS. No effect.
2. Disabled in software, and not re-enabled
The following might help debug the problem:
dmesg shows that in fact the card IS detected during boot, the proper
modules -cdc_acm and cdc_wdm- load and create the appropriate comm
ports, but after a while the usb port is disconnected and ehci_hcd
appears unhappy.
I have noted that in kernel 2.27
