[quote]The backlight works WITHOUT the poulsbo driver.
well works with a script to manage brightness as my function keys do
not always work, even with the kernel options acpi_backlight=vendor and
acpi_osi=Linux.[/quote]
How does this work exactly?
I have precise beta and kernel
I'm wondering if there's a reason this bug is linked to, as far as I can
tell, a bluetooth CVE?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500 psb_gfx
To manage notifications
Nevermind. I should scroll down and read the whole CVE report before
commenting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500 psb_gfx
To manage notifications about this bug
@Chris Van Hoof (vanhoof)
It would be nice to have a proper fix instead of a workaround.. this way the
livecd could work out of the box
also for those people that don't know about this issue and how to bypass it.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
yes the driver is working but screen stays black. I tried adding
console=tty1 but the screen stays black. But additionally switching
ttys shortly (with Ctrl+Alt+F1 and Ctrl+Alt+F7) gets me to the login
screen. I bet that can be fixed easily too - has anybody an idea?
--
You received this bug
Please try removing vt.handoff=7 from the kernel boot options, this
should sort things out for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500 psb_gfx
To manage
I took the daily build for a spin, the pab_gfx is working, although I
still need to either restart X or add console=tty1 to the boot options
(see the bug report filed by Lucazade (lucazade) -
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/914311 )
--
You received this bug notification
This bug was fixed in the package linux - 3.2.0-19.30
---
linux (3.2.0-19.30) precise; urgency=low
[ Andy Whitcroft ]
* [Config] Fix typeo in the Hyper-V module names
[ Colin Watson ]
* [Config] Move kernels to Section: kernel
- LP: #499557
[ John Johansen ]
*
Hi All,
I submitted the patch to the Ubuntu kernel team mailing list for review
[1]. It has since been applied to Precise and should be available in
the next upload. I'm marking the linux task as Fix Committed and
closing the task for module-init-tools. Thanks.
[1]
Thanks very much! Here is the requested info, also fo Dell Mini 12
(inspiron 1210).
** Attachment added: result_dell_mini12_inspiron1210.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+attachment/2866950/+files/result_dell_mini12_inspiron1210.txt
--
You received this bug
requested info for dell mini 12 (inspiron 1210) on which psb_gfx works.
** Attachment added: lspci-dell-insprion-1210
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+attachment/2859146/+files/lspci-dell-insprion-1210.txt
--
You received this bug notification because you are a
Looks like Stefan got there first, but here is 'sudo lspci -vnvn' from
my Dell Inspiron Mini 10, just in case they are different.
This output was collected running 12.04 Beta 1 live USB. Booting got as
far as static text, then the desktop was started by crtl-alt-f1; sudo
rmmod poulsbo; sudo
Thanks for continuing to work on this. I have attached the requested
information.
** Attachment added: lspci -vvv
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+attachment/2854410/+files/lspci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Attached output of `sudo lspci -vnvn` on a Dell Inspiron Mini 10.
psb_gfx is loaded on boot, but when lightdm first launces, X only covers
the top half of the screen, the lower half is still console messages
from the boot process. Also the mouse pointer can't escape from the top
half. This is
i can confirm that removing the poulsbo module, and loading the psb_gfx
module is needed to get a GUI on a dell mini 12 with gma500.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
Hi Everyone,
Could I get everyone who's confirmed that the psb_gfx driver is working
well from them to please attach the output of 'sudo lspci -vnvn'. I
want want to capture confirmed hw information. I'll then raise this on
the mailing list and hopefully have this resolved before Beta-2.
--
psb_gfx is working well on my eee pc 1101ha (only 2d though).
** Attachment added: lspci -vnvn
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+attachment/2840501/+files/psb_gfx.eepc_1101ha.lspci_-vnvn
--
You received this bug notification because you are a member of Ubuntu
** Tags added: rls-p-tracking
** Also affects: linux (Ubuntu Precise)
Importance: High
Assignee: Leann Ogasawara (leannogasawara)
Status: In Progress
** Also affects: module-init-tools (Ubuntu Precise)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu
rmmod poulsbo modprobe psb_gfx is working well on Dell Mini 10
** Attachment added: lspci-vnvn
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+attachment/2840975/+files/lspci-vnvn
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It might also be good to make ubiquity 2d the default login when using
psb_gfx..?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500 psb_gfx
To manage notifications about this bug
Output for Acer Aspire 0751h attached...(works well in 2D unaccelerated)
** Attachment added: lspci-vnvn.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/899244/+attachment/2842518/+files/lspci-vnvn.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
As far as I can determine the poulsbo stub driver serves no useful
purpose and can be removed totally.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500 psb_gfx
To manage
Leann -
This is still not working in 12.04 Beta 1 ., the poulsbo driver
continues to be loaded and conflicts with the psb_gfx, and has to then
be blacklisted.
Can you provide more information or a link to a bug report regarding
There were some concerns raised with the original solution of
Hi Bodhi,
Apologies for this still being an issue with Beta-1. As you've noticed,
no solution has been committed at the moment.
I'd actually committed the original idea of completely disabling the
poulsbo driver. At the time the team was physically together for a face
to face meeting and one
The name is very poor, but the poulsbo driver is not a video driver ,
it is a driver for the backlight
From the help:
Symbol: STUB_POULSBO [=n]
│
│ Type : tristate
The poulsbo driver is just a stub module that enables the acpi video support
for the panel brightness.
This feature is already present inside the psb_gfx driver.
The poulsbo module is loaded before the psb_gfx 'stealing' the pciid and not
allowing the psb_gfx module
to start up and open the
Wish I could edit my comments, the poulsbo driver is not a graphical
driver, it has nothing to do with X, it is a low level driver that
claims to be used by the backlight, but in practice it does not used by
the gma500. It seems to be a poorly named driver.
--
You received this bug notification
When the poulsbo kernel module is loaded at boot, as it is now with
12.04, X fails completely (no VESA, no graphical interface, just a
command prompt).
You can start X / lightdm with
rmmod poulsbo
depmod psb_gfx
/etc/init.d/lisghtdm restart
--
You received this bug notification because you are
Changing brightness seems to work for me (Dell mini 10) in Precise
without 'acpi_backlight=vendor', which hasn't happened since Karmic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
I too have this problem and would love to see a fix to this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500 psb_gfx
To manage notifications about this bug go to:
Hi All,
There were some concerns raised with the original solution of completely
disabling the poulsbo driver. As an alternative, it was suggested to
blacklist it instead. I've therefore built a test package for module-
init-tools which should blacklist the poulsbo driver and result in the
It would be excellent if this could be fixed in time for the Beta
release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500 psb_gfx
To manage notifications about this bug go to:
Seconded - a lot of effort has been expended in getting the GMA500 to be
useable within Ubuntu...for a little more Ubuntu could become the best
Linux distro to support this chipset. There seem to be a lot of users
out there who have laptops or notebooks that use this device and getting
the last
Any idea when we can see this fix in Ubuntu 12.04 ? It is such a trivial
change to the kernel configuration.
Fedora 17 alpha is working -
http://blog.bodhizazen.net/img/gma500/fedora2.png
Would like to say the same for Ubuntu.
--
You received this bug notification because you are a member of
Small update - the driver has moved out of staging in the mainline
(3.3-rc1) kernel
It is now under
Device Drivers -
Graphics support -
DRM (Direct Rendering Manager) -
Intel GMA5/600 KMS Framebuffer
The name has changes in the .config file, it is now called
DRM_GMA500
grep DRM_GMA500 .config
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: module-init-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
I have to correct my previous comment #5
There is no conflict between plymouth and psb_gfx but the problem is only
'vt.handoff=7' as kernel parameter..
This doesn't allow KMS to detect the correct resolution and employ the psb_gfx
framebuffer as VT7, resulting in a black screen instead of X.
I've created this bug report for the vt.handoff=7 issue..
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/914311
hope to have created it correctly, against grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500 psb_gfx
To manage notifications about this bug go to:
** Also affects: module-init-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Fix Committed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for looking into this Leann Ogasawara (leannogasawara)
The kernel you build works as expected on my GMA500, thank you.
NOTE: When booting you still need to add the boot paramater
console=tty1, but I do not think there is anything you can do about
that.
--
You received this bug
@bodhi
console=tty1 is needed because there is a conflict with plymouth.
another way to workaround it is to completely disable plymouth...
sudo sed -i 's/splash//g' /etc/default/grub
sudo sed -i 's/$linux_gfx_mode/text/g' /etc/grub.d/10_linux
sudo mv /etc/init/plymouth.conf
** Changed in: linux (Ubuntu)
Importance: Low = High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) = Leann Ogasawara
(leannogasawara)
** Tags added: kconfig
--
You received this bug notification because you are a member of Ubuntu
Hi bodhi.zazen,
I've built a Precise test kernel with CONFIG_STUB_POULSBO disabled. Can
you please test and confirm there is no longer a conflict between the
psb_gfx and poulsbo drivers and that the psb_gfx driver works as
expected. I've placed the test kernel at the url below. Please let us
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899244
Title:
GMA500
Thank you Joseph, I can submit apport-collect 899244 if it would help,
otherwise it is a small configuration change.
The stub driver affects only the GMA500. You would think the stub driver
would be compatible with the psg_gfx, but it is not.
--
You received this bug notification because you
47 matches
Mail list logo
