Hi Leann, just FYI, I sent a report of my problem (same as in comment
31) and after verifying which specific RTL8168 chipset I had, suggested
I try a 3.2 RC kernel. I did so, using the RC7 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc7-precise/, and
this problem has been fixed
Thanks Leann and hackurx.
I'm trying to use Ubuntu 11.10 on a fit-pc2i with Realtek hardware
(RTL8111/8168B according to lspci), with vlan tagging enabled via
virtual interfaces, and was seeing an easily reproducible kernel freeze.
The signature of the problem is: if I run tail -f
** Attachment added: uname.txt
http://launchpadlibrarian.net/26598264/uname.txt
--
lid switch on HP 6930p works only after running on battery
https://bugs.launchpad.net/bugs/372824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: lspci.txt
http://launchpadlibrarian.net/26598324/lspci.txt
--
lid switch on HP 6930p works only after running on battery
https://bugs.launchpad.net/bugs/372824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: dmidecode.txt
http://launchpadlibrarian.net/26598331/dmidecode.txt
--
lid switch on HP 6930p works only after running on battery
https://bugs.launchpad.net/bugs/372824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: kern.log
http://launchpadlibrarian.net/26598341/kern.log
--
lid switch on HP 6930p works only after running on battery
https://bugs.launchpad.net/bugs/372824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: acpi.tar.bz
http://launchpadlibrarian.net/26598345/acpi.tar.bz
--
lid switch on HP 6930p works only after running on battery
https://bugs.launchpad.net/bugs/372824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This may be related to bug 321153 or bug 277534, which seem to be about
lid switch events not arriving on other HP hardware. But since those
bug reports involve both different hardware and an earlier Ubuntu
release (Intrepid, which worked for me) I thought it's best to file a
new bug.
--
lid
Public bug reported:
I have an HP Elitebook 6930p laptop running Jaunty (and formerly
Intrepid, but this is a clean install of Jaunty, not an upgrade).
I find that the lid switch on this machine works on battery, and works
on AC after the machine has been running on battery, but doesn't work on
Actually, any power supply transition seems to kick it into the good
state.
Booting on battery, the lid switch is broken, if I plug in AC, then the
lid switch works, and I can then go back and forth between battery and
AC and the lid switch keeps working.
Booting on AC, the lid switch is broken,
On an HP 6930p using Jaunty GA, I had this problem (exactly as in
Intrepid, see bug 269027). Adding the options snd-hda-intel
model=laptop to /etc/modprobe.d/alsa-base.conf fixed it, again.
The OP (Andy) said adding snd-hda-intel model=laptop to that file
didn't help, but that line is missing
Public bug reported:
I installed Ubuntu 9.04 (Jaunty) final release on an HP Elitebook 6930p
laptop with Radeon HD 3450 display controller. As it was configured by
default, it always crashed (screen entirely black, not responding to
pings) on resume from suspend.
I used the Hardware Drivers
** Attachment added: apr29-1-host-no-resume-look-for-restart
http://launchpadlibrarian.net/26192300/apr29-1-host-no-resume-look-for-restart
--
default radeon driver prevents resume from suspend on hp elitebook 6930p
https://bugs.launchpad.net/bugs/370074
You received this bug notification
syslog from 2 separate attempts attached.
** Attachment added: apr29-2-host-no-resume-look-for-restart-2
http://launchpadlibrarian.net/26192333/apr29-2-host-no-resume-look-for-restart-2
--
default radeon driver prevents resume from suspend on hp elitebook 6930p
Ahem, this bug does reflect one real problem on one specific family of
devices.
The snd-hda-intel driver does not correctly detect/configure the jacks
on HP Elitebook 2530p/6930p (and probably 8530p, and apparently some
other similar HP models). With the stock settings, you will get sound
from
So for linux-image-debug-generic, the intentional supported path is to
manually download the .ddeb from ddebs.ubuntu.com and install it with
dpkg, and do this again next time the kernel is upgraded, and it can't
be managed with apt? Or is this an oversight or temporary situation
while other
I think this bug report itself has bit-rotted somewhat.
I'm not sure what release this was originally reported against, but I
believe Gutsy and Hardy had a linux-image-debug-generic metapackage that
served this need. Then in Intrepid, things have regressed somewhat, and
the necessary package
Duplicate of https://bugs.launchpad.net/ubuntu/intrepid/+source/linux-
meta/+bug/253904?
--
Intrepid: missing linux-image-debug for 2.6.27?
https://bugs.launchpad.net/bugs/289087
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yup. The systemtap package currently included with Intrepid isn't
compatible with the 2.6.27 kernel, due to the on_each_cpu change, and of
course Intrepid does use a 2.6.27 kernel! There's little point in
packaging a systemtap that's incompatible with the kernel you ship;
everyone who tries to
Under Intrepid, the on_each_cpu issue remains (see
https://bugs.launchpad.net/ubuntu/+source/systemtap/+bug/293235); I
didn't run into issues after patching around that and was able to get
some of the sample .stp scripst to work, so things seem to be on the
whole better.
--
systemtap fails
My variant of the 6930 has ATI graphcs (Radeon HD3400 series). My screen
brightness experience is somewhat better than you describe. The Fn-
controlled keys on the keyboard work for brighter/dimmer; the gnome
applet also works; the brightness state agrees between these two
methods. xbacklight
The bug about the headphone vs internal speakers is also filed as
https://bugs.launchpad.net/bugs/269027. Apparently the snd_hda_intel
driver doesn't properly detect the model configuration but knows what to
do if you load it with model=mobile.
On my 6930p, the hardware mute switch+LED does work,
Also, for the brightness keys: a friend who's better versed than I in
the ways of hal showed me how to copy some entries from
/usr/share/hal/fdi/information/10freedesktop/30-keymap-hp.fdi to
/usr/share/hal/fdi/information/20thirdparty/30-keymap-private.fdi. (It
probably would have sufficed to edit
I now have just options snd_hda_intel model=mobile in
/etc/modprobe.d/options, and that also suffices to let me play sound
through headphones when plugged in and internal speakers otherwise.
It also has the side effect of removing most of the tracks from the
volume control for device HDA Intel
I have a brand new HP 6930 notebook, and installed Ubuntu 8.10 current
beta with all packages up to date.
I see this same problem, and the same solution works. (I don't know if
both options lines are necessary or not; I just added both and
rebooted.)
Also, on the 6930 there's a hardware mute
25 matches
Mail list logo
