latest kernel update fixed mine
dell inspiron 1150
2.6.27-13-generic
On Tue, Mar 3, 2009 at 3:30 AM, Martin Pitt
wrote:
> Dimitrios Symeonidis [2009-03-01 21:00 -]:
> > The reason 2.6.27-13 isn't automatically installed is that, for some
> > strange reason, linux-image-generic wasn't updated
Dimitrios Symeonidis [2009-03-01 21:00 -]:
> The reason 2.6.27-13 isn't automatically installed is that, for some
> strange reason, linux-image-generic wasn't updated, and still points to
> -12...
It is updated now.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu D
It won't auto update you to it yet, it's waiting for external drivers to
build perhaps?
I manually installed it, cause my laptop doesn't require any.
If you do a search for 2.6.27-13 it should come up and you could give it a
try (but it might break prop. drivers until they get built). Alternative
2.6.27-12-generic (latest proposed update)
still broken on dell inspiron 1150
On Fri, Feb 20, 2009 at 11:15 AM, Stefan Bader
wrote:
> The patch "Input: atkbd - broaden the Dell DMI signatures" has been
> applied to Intrepid by the update to 2.6.27.15 (see LP bug #328652)
>
> ** Changed in: linux
On Thu, Feb 05, 2009 at 05:18:43PM -, nanotube wrote:
> will this latest kernel be released for intrepid? or is it jaunty-only?
This is a Jaunty kernel only. Intrepid is carrying the 2.6.27 series of
kernels.
--
X never sees brightness key release events on Dell laptops
https://bugs.launchp
On Sun, Feb 01, 2009 at 02:41:13PM -, nanotube wrote:
> Problem still persists with the latest intrepid kernel update
> (2.6.27-11-generic) here on Dell Inspiron 5150.
>
> dmidecode says manufacturer is "Dell Computer Corporation"
The fix as committed will be in the next Jaunty kernel, it is
most recent ubuntu 8.10 proposed update (last night)
2.6.27-11-generic
still broken
On Sat, Jan 31, 2009 at 2:37 PM, Tim Gardner
wrote:
> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
> jaunty.git;a=commit;h=bf9b51b29cab40295dfc5d79289bd389f24b7b06
>
> ** Changed in: linux (Ubuntu Jaunty)
> Im
On Mon, Jan 19, 2009 at 05:32:01PM -, klerfayt wrote:
> However the fix used to get around "most Fn keys on Dell laptops do not
> generate release event" would be similar if not exactly same for other brands
> of laptops:
> "generate release events ourselves"
Generally quirk based fixes such
The fix is in the *kernel* package. You need the kernel package from
-proposed until it gets released to -updates.
Ben Trusty wrote:
>
> I concur, the slider now actually updates, but I still have to ctrl +
> alt +
> f2 to fix keyboard problem (cant click on menus, cant type, etc)
>
> dell inspir
On Sun, Dec 28, 2008 at 10:09:13AM -, Stan Couix wrote:
> Hi everybody,
>
> Recent update fix the issue of the brightness indicator (it moves now!)
> but the indicator is still here, I can't click on menus, etc.
> (fortunately switching VT workaround still works)
>
> I have a Dell inspiron 51
I concur, the slider now actually updates, but I still have to ctrl + alt +
f2 to fix keyboard problem (cant click on menus, cant type, etc)
dell inspiron 1150, 852/855gm
On Sun, Dec 28, 2008 at 5:09 AM, Stan Couix wrote:
> Hi everybody,
>
> Recent update fix the issue of the brightness indicat
Hi Essence:
Can you open another bug on that issue against the gnome-power-manager
package, and subscribe dell-team to it? I'm aware of the issue myself,
but it would be good to track it while the gnome power manager
maintainers triage it.
-Original Message-
From: [EMAIL PROTECTED] on b
i still have the problem with this
Linux rook 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686
GNU/Linux
so i am using the purposed via synaptic
it is nice that i know i can just hit ctrl+alt+f2 to fix it (rather than
having to reboot, like i used to. but it seems that this is a major pr
On Fri, Nov 28, 2008 at 04:47:03PM -, Cory wrote:
> I previously thought the upgrade to 2.6.27-8 solved the problem, but I
> just had my keyboard disabled again when trying to change brightness.
> I've attached my lspci -nn output.
Could you try the 2.6.27-10.20 release currently in -proposed.
I think that you need to look a little closer at what's actually
happening for these "Release" events possibly. Try starting a Failsafe
Terminal at your login screen. If you run xev over there, you'll see
that a KeyRelease event is somehow generated, however it is *followed*
by the KeyPress event
Stephen Gibson wrote:
> I'm assuming that most people commenting to this bug have checked which
> image they are running, however, it's something that can be overlooked
> when freaking out about a finger-memory keystroke that render X useless.
It is worth checking. :)
Just to confirm, I still see
16 matches
Mail list logo
