[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
** Changed in: opencompute Status: New => Triaged ** Changed in: opencompute Status: Triaged => Confirmed ** Changed in: opencompute Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Also, it seems you have to set the power management option to ipmi_2.0 in the MAAS UI because the power command will work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: New Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
So basically I was able to get this to work in maas.
Basically you need to change the following line in :
/etc/maas/templates/commissioning-user-data/snippets/maas_ipmi_autodetect.py
def commit_ipmi_user_settings(user, password):
ipmi_user_number = get_ipmi_user_number(user)
if ipmi_user_number is None:
(status, output) = commands.getstatusoutput('bmc-config --commit
--key-pair="User10:Username=%s"' % user)
ipmi_user_number = get_ipmi_user_number(user)
You have to change User10 to User4, as this bmc config maxes out at 4
User sections.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1210393
Title:
MAAS ipmi fails on OCPv3 Roadrunner
Status in MAAS:
New
Status in Open Compute Project:
New
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Saucy:
Confirmed
Bug description:
The OCPv3 Roadrunner machine has been fully enabled and passes
certification testing. When testing ipmitool locally I'm able to
setup the BMC and users, etc.
When using MAAS, MAAS is able to setup the BMC network information (I
see that it changes that), but it appears to fail to set a username
and password. If I try to use the username and password as defined in
the MAAS GUI, it fails. Therefore commissioning and juju
bootstrapping the node has to be done manually (by physically pushing
the power button).
If I use the username/password I've set on the BMC I can see that MAAS
fails to set the username 'maas' and the password as defined in the
MAAS gui.
Since the commissioning/enlisting process is temporary and I'm not
sure how to login to this phase to gather data, troubleshooting tips
are welcome.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Just to clarify, I'm able to successfully update the username+password in the ephemeral saucy image by hand using ipmitool -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: New Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
User list after cloud-init/ipmitool has tried to set maas username/password: ID Name Callin Link Auth IPMI Msg Channel Priv Limit 1truefalse true USER 2 admintruefalse true ADMINISTRATOR 3 Operator truefalse true OPERATOR 4 admintruefalse true ADMINISTRATOR ** Changed in: maas Status: Triaged => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: New Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
ipmi-chassis --get-capabilities command success: Intrusion sensor: not provided Front Panel Lockout : provided Diagnostic Interrupt: provided Power interlock : not provided FRU Info Device Address : 20h SDR Device Address : 20h SEL Device Address : 20h Sys Mgmt Device Address : 0h Bridge Device Address : 20h IPMI modules are loaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: New Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Confirmed that the ipmi-locate command fails during the MAAS enlistment process on OCV3 bmc. ipmi-locate failure: Probing KCS device using DMIDECODE... done IPMI Version: 2.0 IPMI locate driver: DMIDECODE IPMI interface: KCS BMC driver device: BMC memory base address: 0x0 Register spacing: 1 Probing SMIC device using DMIDECODE... FAILED Probing BT device using DMIDECODE... FAILED Probing SSIF device using DMIDECODE... FAILED Probing KCS device using SMBIOS... done IPMI Version: 2.0 IPMI locate driver: SMBIOS IPMI interface: KCS BMC driver device: BMC memory base address: 0x0 Register spacing: 1 Probing SMIC device using SMBIOS... FAILED Probing BT device using SMBIOS... FAILED Probing SSIF device using SMBIOS... FAILED Probing KCS device using ACPI... FAILED Probing SMIC device using ACPI... FAILED Probing BT device using ACPI... FAILED Probing SSIF device using ACPI... FAILED Probing KCS device using PCI... FAILED Probing SMIC device using PCI... FAILED Probing BT device using PCI... FAILED Probing SSIF device using PCI... FAILED -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: New Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1126600] Re: [Lenovo L420]: System hangs at random spots during 12.04.2 install
This is still an issue with 12.04.3 unfortunately :/ ** Summary changed: - [Lenovo L420]: System hangs at random spots during 12.04.2 install + [Lenovo L420]: System hangs at random spots during 12.04.2 and 12.04.3 install -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1126600 Title: [Lenovo L420]: System hangs at random spots during 12.04.2 and 12.04.3 install Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Precise: Confirmed Bug description: [Lenovo L420]: System hangs at random spots during 12.04.2 install Problem: This machine was previously blocked for certification due to bug #990110. I downloaded the requested BIOS update from lenovo's site version: 1.20 and attempting an install via a live iso. While attempting the install the system would intermittently lose touchpad functionality and lock up. It will eventually stop responding to all keyboard and mouse activity and the progress indicator will halt implying the system has stopped. At this point you cannot switch to an alternate tty. Reproducible: yes Image used: b436b6d4c7de064652f30d783bda5b4e ubuntu-12.04.2-desktop-amd64.iso checksum from releases.ubuntu.com: b436b6d4c7de064652f30d783bda5b4e *ubuntu-12.04.2-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1126600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248327] Re: [Lenovo b475e]: Precise 12.04.3 install fails
I'm unable to gather logs from this machine at this time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248327 Title: [Lenovo b475e]: Precise 12.04.3 install fails Status in “linux” package in Ubuntu: New Bug description: When trying to boot from 12.04.3 CD or USB key the system shows only the purple boot splash. I cannot switch tty when this occurs. While attempting to PXE boot: Freeing SMP alternatives: 24k freed ACPI: Core revision 20121018 BIOS version: HPET09WW (0.09) CPU Type (AMD E2-1800 APU with Radeon (tm) HD Graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1248327] [NEW] [Lenovo b475e]: Precise 12.04.3 install fails
Public bug reported: When trying to boot from 12.04.3 CD or USB key the system shows only the purple boot splash. I cannot switch tty when this occurs. While attempting to PXE boot: Freeing SMP alternatives: 24k freed ACPI: Core revision 20121018 BIOS version: HPET09WW (0.09) CPU Type (AMD E2-1800 APU with Radeon (tm) HD Graphics) ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Canonical Hardware Enablement Team (canonical-hwe-team) Status: New ** Tags: 201204-10862 blocks-hwcert blocks-hwcert-enablement bot-stop-nagging lexington-lab precise ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Hardware Enablement Team (canonical-hwe-team) ** Tags added: 201204-10862 blocks-hwcert blocks-hwcert-enablement bot- stop-nagging lexington-lab precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248327 Title: [Lenovo b475e]: Precise 12.04.3 install fails Status in “linux” package in Ubuntu: New Bug description: When trying to boot from 12.04.3 CD or USB key the system shows only the purple boot splash. I cannot switch tty when this occurs. While attempting to PXE boot: Freeing SMP alternatives: 24k freed ACPI: Core revision 20121018 BIOS version: HPET09WW (0.09) CPU Type (AMD E2-1800 APU with Radeon (tm) HD Graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Saucy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Confirmed Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
I don't understand. Why was this set to incomplete? What specific information do you need? ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu Saucy) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Status in “linux” source package in Saucy: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
BMC is detected on the network, just cannot establish connection via link: ipmiping 10.193.37.122 ipmiping 10.193.37.122 (10.193.37.122) response received from 10.193.37.122: rq_seq=32 response received from 10.193.37.122: rq_seq=33 response received from 10.193.37.122: rq_seq=34 response received from 10.193.37.122: rq_seq=35 response received from 10.193.37.122: rq_seq=36 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
Troubleshooting steps: modprobe ipmi_msghandler modprobe ipmi_devintf modprobe ipmi_si Will enable the bmc device parameters to be changed locally and eliminate the write back errors, something I feel the Saucy ephemeral images are not doing. Secondly, trying to enable link authentication fails to set: ipmitool lan set 1 auth ADMIN MD5,PASSWORD Channel link access still states: User ID : 4 User Name : admin Fixed Name : No Access Available : call-in / callback Link Authentication : disabled IPMI Messaging : enabled Also, setting link access for channel 1 fails: sudo ipmitool lan set 1 access on Set Channel Access for channel 1 failed: Unknown (0x83) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900224/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900225/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900221/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900223/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900222/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900214/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900216/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900220/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2918 F pulseaudio CasperVersion: 1.336 DistroRelease: Ubuntu 13.10 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130916) MachineType: empty empty MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-7-generic N/A linux-backports-modules-3.11.0-7-generic N/A linux-firmware1.114 RfKill: Tags: saucy Uname: Linux 3.11.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: S8237 dmi.board.vendor: TYAN dmi.board.version: empty dmi.chassis.asset.tag: empty dmi.chassis.type: 28 dmi.chassis.vendor: empty dmi.chassis.version: empty dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/04/2013:svnempty:pnempty:pvrempty:rvnTYAN:rnS8237:rvrempty:cvnempty:ct28:cvrempty: dmi.product.name: empty dmi.product.version: empty dmi.sys.vendor: empty ** Tags added: apport-collected saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900215/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900218/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900217/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1210393/+attachment/3900219/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: New Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210393] Re: MAAS ipmi fails on OCPv3 Roadrunner
** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => ubuntu ** Package changed: ubuntu => linux (Ubuntu) ** No longer affects: freeipmi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210393 Title: MAAS ipmi fails on OCPv3 Roadrunner Status in MAAS: Triaged Status in Open Compute Project: New Status in “linux” package in Ubuntu: Incomplete Bug description: The OCPv3 Roadrunner machine has been fully enabled and passes certification testing. When testing ipmitool locally I'm able to setup the BMC and users, etc. When using MAAS, MAAS is able to setup the BMC network information (I see that it changes that), but it appears to fail to set a username and password. If I try to use the username and password as defined in the MAAS GUI, it fails. Therefore commissioning and juju bootstrapping the node has to be done manually (by physically pushing the power button). If I use the username/password I've set on the BMC I can see that MAAS fails to set the username 'maas' and the password as defined in the MAAS gui. Since the commissioning/enlisting process is temporary and I'm not sure how to login to this phase to gather data, troubleshooting tips are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1210393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1118657] Re: Lenovo m490/k4350/b580/L530/k29 - ACPI Warnings for \_SB_.PCI0.LPCB.H_EC.LED_
** Tags added: 201204-10884
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1118657
Title:
Lenovo m490/k4350/b580/L530/k29 - ACPI Warnings for
\_SB_.PCI0.LPCB.H_EC.LED_
Status in HWE Next Project:
Incomplete
Status in “linux” package in Ubuntu:
Incomplete
Status in “linux” source package in Precise:
Confirmed
Status in “linux” source package in Quantal:
Confirmed
Bug description:
Suspend and hibernate stress test got failed with following errors in logs:
s3: HIGH Kernel message: [10512.177806] ACPI Warning: For
\_SB_.PCI0.LPCB.H_EC.LED_: Excess arguments - needs 1, found 2
(20110623/nspredef-326)
s4: HIGH Kernel message: [11728.328110] ACPI Warning: For
\_SB_.PCI0.LPCB.H_EC.LED_: Excess arguments - needs 1, found 2
(20110623/nspredef-326)
Steps:
1. Log into desktop
2. Run s3/s4 stress test for 30 times
Expected results:
Suspend and hibernate stress got passed without any error
Actual results:
s3/s4 got failures in log file
Diagnosis:
This warning is generated by the ACPI LED method expects 1 argument, but the
kernel driver thinkpad_acpi.c function led_set_status will evaluate the ACPI
LED method with two arguments (let and led_status):
Method (LED, 1, NotSerialized)
{
If (H8DR)
{
Store (Arg0, MLED)
}
Else
{
And (RBEC (0x0B), 0xFD, Local0)
Or (Local0, Arg0, Local0)
WBEC (0x0B, Local0)
}
}
and I also checked with lenovo thiinkpad x220, x200, seems it accepts two
arguments in ACPI LED method:
Method (LED, 2, NotSerialized)
{
Or (Arg0, Arg1, Local0)
If (\H8DR)
{
Store (Local0, HLCL)
}
Else
{
\WBEC (0x0C, Local0)
}
}
It seems the spec change, if yes, we might need the spec.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1118657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 967399] Re: [11.10] Elantech trackpoint does not work Lenovo
** Tags added: 201205-10579 blocks-hwcert -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/967399 Title: [11.10] Elantech trackpoint does not work Lenovo Status in “linux” package in Ubuntu: In Progress Bug description: Title: trackpoint does not function Summary: trackpoint does not function Steps: 1. log into desktop 2. use trackpoint and trackpoint buttons Expected results: laptop responds to trackpoint and trackpoint buttons being pressed Actual results: nothing happens Manufacturer: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/967399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156888] Re: [Lenovo E330, b580, b90, b490, F230]: Accelerometer is not working
** Summary changed:
- [Lenovo E330, b580, b90, b490]: Accelerometer is not working
+ [Lenovo E330, b580, b90, b490, F230]: Accelerometer is not working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1156888
Title:
[Lenovo E330, b580, b90, b490, F230]: Accelerometer is not working
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Precise:
Won't Fix
Status in “linux” source package in Quantal:
Won't Fix
Status in “linux” source package in Raring:
Won't Fix
Bug description:
Problem:
Kernel detects presence of accelerometer hardware yet the accelerometer is
not functional.
Device:
I: Bus=0019 Vendor= Product= Version=
N: Name="Acer BMA150 accelerometer"
P: Phys=wmi/input1
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=event3 js0
B: PROP=0
B: EV=9
B: ABS=7
Looking in /devices/virtual/input/input3 there should be a position file that
relays axis data via x, y, z tilt counters.
For lenovo, it seems the hdaps driver is not longer available, nor is
there an opensource equivelant available.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1827 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9c61 irq 47'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,17aa5006,00100202
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Mon Mar 18 18:25:24 2013
HibernationDevice: RESUME=UUID=8ebe04d3-41f2-4b51-b2b5-e753af5a45ea
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: LENOVO 335421U
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 inteldrmfb
1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic
root=UUID=2060a7a9-51be-4440-bd16-468ee9100723 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-23-generic N/A
linux-backports-modules-3.5.0-23-generic N/A
linux-firmware1.79.1
SourcePackage: linux
StagingDrivers: rts_pstor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: H3ET31WW(1.14)
dmi.board.asset.tag: Not Available
dmi.board.name: 335421U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrH3ET31WW(1.14):bd07/13/2012:svnLENOVO:pn335421U:pvrThinkpadEdgeE330:rvnLENOVO:rn335421U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 335421U
dmi.product.version: Thinkpad Edge E330
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156888/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1118657] Re: Lenovo m490/k4350/b580/L530/k29 - ACPI Warnings for \_SB_.PCI0.LPCB.H_EC.LED_
** Tags added: 201202-10576
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1118657
Title:
Lenovo m490/k4350/b580/L530/k29 - ACPI Warnings for
\_SB_.PCI0.LPCB.H_EC.LED_
Status in HWE Next Project:
Confirmed
Status in “linux” package in Ubuntu:
Incomplete
Status in “linux” source package in Precise:
Confirmed
Status in “linux” source package in Quantal:
Confirmed
Bug description:
Suspend and hibernate stress test got failed with following errors in logs:
s3: HIGH Kernel message: [10512.177806] ACPI Warning: For
\_SB_.PCI0.LPCB.H_EC.LED_: Excess arguments - needs 1, found 2
(20110623/nspredef-326)
s4: HIGH Kernel message: [11728.328110] ACPI Warning: For
\_SB_.PCI0.LPCB.H_EC.LED_: Excess arguments - needs 1, found 2
(20110623/nspredef-326)
Steps:
1. Log into desktop
2. Run s3/s4 stress test for 30 times
Expected results:
Suspend and hibernate stress got passed without any error
Actual results:
s3/s4 got failures in log file
Diagnosis:
This warning is generated by the ACPI LED method expects 1 argument, but the
kernel driver thinkpad_acpi.c function led_set_status will evaluate the ACPI
LED method with two arguments (let and led_status):
Method (LED, 1, NotSerialized)
{
If (H8DR)
{
Store (Arg0, MLED)
}
Else
{
And (RBEC (0x0B), 0xFD, Local0)
Or (Local0, Arg0, Local0)
WBEC (0x0B, Local0)
}
}
and I also checked with lenovo thiinkpad x220, x200, seems it accepts two
arguments in ACPI LED method:
Method (LED, 2, NotSerialized)
{
Or (Arg0, Arg1, Local0)
If (\H8DR)
{
Store (Local0, HLCL)
}
Else
{
\WBEC (0x0C, Local0)
}
}
It seems the spec change, if yes, we might need the spec.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1118657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1157440] Re: [Lenovo E435, M490s]: Brightness controls do not work
It is a blocker though, neither the keys or the settings control allow
you to change the brightness settings appropriately.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1157440
Title:
[Lenovo E435, M490s]: Brightness controls do not work
Status in amd:
New
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Precise:
Confirmed
Bug description:
Problem:
Brightness keys or brightness settings controls do not change the
brightness or display as intended.
However, If I run the following command it works perfectly:
xrandr --output LVDS --brightness 0.5
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 2137 F pulseaudio
/dev/snd/controlC0: ubuntu 2137 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xf0544000 irq 46'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 6
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf054 irq 16'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aa5108,0013'
Controls : 20
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Mar 19 17:49:29 2013
HibernationDevice: RESUME=UUID=ee9d3e8f-05df-494c-afc6-36438c39723b
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: LENOVO 3469C01
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic
root=UUID=5396c06a-e550-4e31-b4f5-d953a397915f ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-23-generic N/A
linux-backports-modules-3.5.0-23-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: HNET14WW (1.01 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3469C01
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrHNET14WW(1.01):bd05/30/2012:svnLENOVO:pn3469C01:pvrThinkPadEdgeE435:rvnLENOVO:rn3469C01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3469C01
dmi.product.version: ThinkPad Edge E435
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1157440/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1157440] Re: [Lenovo E435]: Brightness controls do not work
Still an issue in 12.04.3
** Tags added: 201211-12079
** Summary changed:
- [Lenovo E435]: Brightness controls do not work
+ [Lenovo E435, M490s]: Brightness controls do not work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1157440
Title:
[Lenovo E435, M490s]: Brightness controls do not work
Status in amd:
New
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Precise:
Confirmed
Bug description:
Problem:
Brightness keys or brightness settings controls do not change the
brightness or display as intended.
However, If I run the following command it works perfectly:
xrandr --output LVDS --brightness 0.5
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 2137 F pulseaudio
/dev/snd/controlC0: ubuntu 2137 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xf0544000 irq 46'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 6
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf054 irq 16'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aa5108,0013'
Controls : 20
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Mar 19 17:49:29 2013
HibernationDevice: RESUME=UUID=ee9d3e8f-05df-494c-afc6-36438c39723b
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: LENOVO 3469C01
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic
root=UUID=5396c06a-e550-4e31-b4f5-d953a397915f ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-23-generic N/A
linux-backports-modules-3.5.0-23-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: HNET14WW (1.01 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3469C01
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrHNET14WW(1.01):bd05/30/2012:svnLENOVO:pn3469C01:pvrThinkPadEdgeE435:rvnLENOVO:rn3469C01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3469C01
dmi.product.version: ThinkPad Edge E435
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1157440/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156888] Re: [Lenovo E330, b580, b90, b490]: Accelerometer is not working
** Summary changed:
- [Lenovo E330, b580, b90]: Accelerometer is not working
+ [Lenovo E330, b580, b90, b490]: Accelerometer is not working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1156888
Title:
[Lenovo E330, b580, b90, b490]: Accelerometer is not working
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Precise:
Won't Fix
Status in “linux” source package in Quantal:
Won't Fix
Status in “linux” source package in Raring:
Won't Fix
Bug description:
Problem:
Kernel detects presence of accelerometer hardware yet the accelerometer is
not functional.
Device:
I: Bus=0019 Vendor= Product= Version=
N: Name="Acer BMA150 accelerometer"
P: Phys=wmi/input1
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=event3 js0
B: PROP=0
B: EV=9
B: ABS=7
Looking in /devices/virtual/input/input3 there should be a position file that
relays axis data via x, y, z tilt counters.
For lenovo, it seems the hdaps driver is not longer available, nor is
there an opensource equivelant available.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1827 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9c61 irq 47'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,17aa5006,00100202
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Mon Mar 18 18:25:24 2013
HibernationDevice: RESUME=UUID=8ebe04d3-41f2-4b51-b2b5-e753af5a45ea
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: LENOVO 335421U
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
0 inteldrmfb
1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic
root=UUID=2060a7a9-51be-4440-bd16-468ee9100723 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-23-generic N/A
linux-backports-modules-3.5.0-23-generic N/A
linux-firmware1.79.1
SourcePackage: linux
StagingDrivers: rts_pstor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: H3ET31WW(1.14)
dmi.board.asset.tag: Not Available
dmi.board.name: 335421U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrH3ET31WW(1.14):bd07/13/2012:svnLENOVO:pn335421U:pvrThinkpadEdgeE330:rvnLENOVO:rn335421U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 335421U
dmi.product.version: Thinkpad Edge E330
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1156888/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1152324] Re: [Lenovo b485]: Can't install precise 12.04.2 or 12.04.3 from live image or via PXE
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1152324 Title: [Lenovo b485]: Can't install precise 12.04.2 or 12.04.3 from live image or via PXE Status in “linux” package in Ubuntu: Confirmed Bug description: Problem, I'm currently unable to install 12.04.2 via PXE or live cd image. When trying to install via PXE the machine will hang with the following kernel messages showing: [0.004205] [Firmware Info]: CPU: Re-enabling disabled Toplogy Extensions Support [0.004254] CPU: Physical Processor ID: - [0.004293] CPU: Processor Core ID: 0 [0.004322] mce: CPU supports 7 MCE banks p0.006443] ACPI: Core revision 20120320 Whey trying to install via Live CD or Live USB I receive the following message: "If you're seeing this the installation has failed", from this point I can select to boot into single user mode, or an automated install. Selecting either causes the machine to hang with a cursor in the top left corner. Reproducable?: Yes I've reset all BIOS settings to the default values. In 12.04.1 the system will attempt to boot from the key/CD after selecting "Install Ubuntu" and proceed (trackpad is disabled and Ubuntu Desktop never loads" When trying to boot raring live image, the machine simply reboots never displaying a Grub Menu option. I have confirmed that the live images I was using are working with other machines without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1152324] Re: [Lenovo b485]: Can't install precise 12.04.2 from live image or via PXE
for the 7324 L520 sku I don't see an option in the BIOS menu to boot legacy only. This also still fails with 12.04.3 ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - [Lenovo b485]: Can't install precise 12.04.2 from live image or via PXE + [Lenovo b485]: Can't install precise 12.04.2 or 12.04.3 from live image or via PXE -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1152324 Title: [Lenovo b485]: Can't install precise 12.04.2 or 12.04.3 from live image or via PXE Status in “linux” package in Ubuntu: New Bug description: Problem, I'm currently unable to install 12.04.2 via PXE or live cd image. When trying to install via PXE the machine will hang with the following kernel messages showing: [0.004205] [Firmware Info]: CPU: Re-enabling disabled Toplogy Extensions Support [0.004254] CPU: Physical Processor ID: - [0.004293] CPU: Processor Core ID: 0 [0.004322] mce: CPU supports 7 MCE banks p0.006443] ACPI: Core revision 20120320 Whey trying to install via Live CD or Live USB I receive the following message: "If you're seeing this the installation has failed", from this point I can select to boot into single user mode, or an automated install. Selecting either causes the machine to hang with a cursor in the top left corner. Reproducable?: Yes I've reset all BIOS settings to the default values. In 12.04.1 the system will attempt to boot from the key/CD after selecting "Install Ubuntu" and proceed (trackpad is disabled and Ubuntu Desktop never loads" When trying to boot raring live image, the machine simply reboots never displaying a Grub Menu option. I have confirmed that the live images I was using are working with other machines without issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1222998] [NEW] bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build
*** This bug is a duplicate of bug 1222031 *** https://bugs.launchpad.net/bugs/1222031 Public bug reported: [Problem] Ubuntu:12.04.3 Jockey fails to install the detected available broadcom driver for a number of machine configurations. Installing bcmwl-kernel-source results in a non-zero exit code. Jockey log is attached. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 DKMSKernelVersion: 3.8.0-29-generic Date: Mon Sep 9 15:30:30 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True PackageVersion: 6.20.155.1+bdcom-0ubuntu0.0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise running-unity -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1222998 Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build Status in “bcmwl” package in Ubuntu: New Bug description: [Problem] Ubuntu:12.04.3 Jockey fails to install the detected available broadcom driver for a number of machine configurations. Installing bcmwl-kernel-source results in a non-zero exit code. Jockey log is attached. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 DKMSKernelVersion: 3.8.0-29-generic Date: Mon Sep 9 15:30:30 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True PackageVersion: 6.20.155.1+bdcom-0ubuntu0.0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1222998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1222263] Re: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build
** Tags added: 201304-13462 201305-13495 blocks-hwcert lexington-lab -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/163 Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build Status in “bcmwl” package in Ubuntu: Confirmed Bug description: My wireless adapter is not working. I'm sorry i'm not an expert ProblemType: Package DistroRelease: Ubuntu 12.04 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 DKMSKernelVersion: 3.8.0-30-generic Date: Sat Sep 7 11:04:16 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True PackageVersion: 6.20.155.1+bdcom-0ubuntu0.0.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 964231] Re: System Stutter When HDMI/Displayport Monitor Is Connected
k, that one failed ^^ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/964231 Title: System Stutter When HDMI/Displayport Monitor Is Connected Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Precise: Confirmed Status in “linux” source package in Quantal: Confirmed Bug description: With a fresh install of Ubuntu 11.10 x64, the system has many "microfreezes" when I connect an external monitor via HDMI. These last maybe 10ms and occur about once per second. As I move my cursor around the screen, it stops motion during these microfreezes, causing a very irritating stutter effect. This only happens when using HDMI- when connected via VGA to an external monitor, the system behaves smoothly as expected. I started a thread about this a long time ago, but I never did find an answer: http://ubuntuforums.org/showthread.php?t=1817910 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7.1 Uname: Linux 3.3.0-030300rc7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,move,vpswitch,place,mousepoll,resize,wall,regex,session,snap,gnomecompat,imgpng,animation,expo,workarounds,unitymtgrabhandles,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sat Mar 24 18:30:09 2012 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:2080] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: PEGATRON CORPORATION A15 ProcEnviron: PATH=(cususername, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-030300rc7-generic root=UUID=a19e39dd-b510-4f9d-93f5-de6d40df10f1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: A15 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr211:bd06/17/2011:svnPEGATRONCORPORATION:pnA15:pvr1.0:rvnPEGATRONCORPORATION:rnA15:rvr1.0:cvnPEGATRONComputerInc.:ct9:cvr1.0: dmi.product.name: A15 dmi.product.version: 1.0 dmi.sys.vendor: PEGATRON CORPORATION version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/964231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 759213] Re: [HP Compaq 6005 Pro] Suspend does not resume
** Changed in: linux (Ubuntu Precise)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Quantal)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/759213
Title:
[HP Compaq 6005 Pro] Suspend does not resume
Status in “linux” package in Ubuntu:
Triaged
Status in “linux” source package in Lucid:
Confirmed
Status in “linux” source package in Natty:
Invalid
Status in “linux” source package in Oneiric:
Invalid
Status in “linux” source package in Precise:
Confirmed
Status in “linux” source package in Quantal:
Confirmed
Bug description:
Resuming this system from suspend only shows a blank screen, rather
then returning to the desktop.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1432 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xf030 irq 11'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,103c3047,00100101'
Controls : 19
Simple ctrls : 11
Date: Tue Apr 12 17:27:43 2011
HibernationDevice: RESUME=UUID=938ca224-d6b8-44c0-82ed-0c15d5af6e3c
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110329)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic
root=UUID=069df1e8-a920-4d04-84bd-911cfaad7eee ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-8-generic N/A
linux-backports-modules-2.6.38-8-generic N/A
linux-firmware1.50
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G6 v01.11
dmi.board.asset.tag: WML3020081
dmi.board.name: 3047h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: WML3020081
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759213/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 874634] Re: [Eee PC 1001PXD] hcitool shows a bluetooth device, bluetoothd is running, but bluetooth is unusable
** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/874634 Title: [Eee PC 1001PXD] hcitool shows a bluetooth device, bluetoothd is running, but bluetooth is unusable Status in “bluez” package in Ubuntu: Invalid Status in “bluez” source package in Oneiric: Won't Fix Status in “bluez” source package in Precise: Fix Released Bug description: On this EeePC 1001PXD, title says it all... :/ Doing cert testing of Oneiric on the system. Bluetoothd is running, hcitool shows a device, but I can't actually do anything with it. If I click on the bluetooth applet icon, I get an abbreviated menu and the only options are Turn Bluetooth Off and Preferences. It says Bluetooth is on... If I look at the preferences, it says "Bluetooth is disabled" and when I try moving the slider from off to on, it just flips back to off. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-utils 1.0.24.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 CheckboxCommand: arecord -d 5 -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE CheckboxTest: bluetooth/audio Date: Fri Oct 14 17:24:12 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 1.23-0ubuntu3 Architecture: i386 DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) InterestingModules: bnep rfcomm btusb bluetooth MachineType: ASUSTeK Computer INC. 1001PXD Package: bluez 4.96-0ubuntu3 PackageArchitecture: i386 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=caecd489-e41f-4683-9b3e-346c353de4ba ro quiet splash initcall_debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Tags: oneiric running-unity Uname: Linux 3.0.0-12-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 08/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0105 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PXD dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0105:bd08/12/2010:svnASUSTeKComputerINC.:pn1001PXD:pvrx.x:rvnASUSTeKComputerINC.:rn1001PXD:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PXD dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 1C:4B:D6:17:FA:FF ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:467 acl:0 sco:0 events:19 errors:0 TX bytes:88 acl:0 sco:0 commands:19 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/874634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] Re: [OCPv2 Windmill]: Can't install Saucy.
*** This bug is a duplicate of bug 1154749 *** https://bugs.launchpad.net/bugs/1154749 ** This bug has been marked a duplicate of bug 1154749 reboot does a shutdown instead of rebooting (OCP v2) ** This bug is no longer a duplicate of bug 1154749 reboot does a shutdown instead of rebooting (OCP v2) ** Changed in: opencompute Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** This bug has been marked a duplicate of bug 1154749 reboot does a shutdown instead of rebooting (OCP v2) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Saucy. Status in Open Compute Project: Invalid Status in “linux” package in Ubuntu: Invalid Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] Re: [OCPv2 Windmill]: Can't install Saucy.
Update: So I was able to get Raring to boot successfully after a power reset and second attempt at booting. Retrying Saucy while attempting to blacklist mei. However I'm fairly certain we still have an issue with network connections with Saucy and this Windmill's Intel NICS. ** Summary changed: - [OCPv2 Windmill]: Can't install Raring or Saucy. + [OCPv2 Windmill]: Can't install Saucy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755213/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755216/+files/WifiSyslog.txt ** Description changed: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang - and stop responding to any keyboard actions. Can't switch tty etc. + (during first boot after install) and stop responding to any keyboard + actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. - With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. - --- - AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. - AplayDevices: - Home directory /home/ubuntu not ours. - List of PLAYBACK Hardware Devices - card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] -Subdevices: 1/1 -Subdevice #0: subdevice #0 - ApportVersion: 2.0.1-0ubuntu17.1 - Architecture: amd64 - ArecordDevices: - Home directory /home/ubuntu not ours. - List of CAPTURE Hardware Devices - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ubuntu 2760 F pulseaudio - CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. - Card0.Amixer.info: - Card hw:0 'Generic'/'HD-Audio Generic at 0xdfe4 irq 113' -Mixer name : 'ATI R6xx HDMI' -Components : 'HDA:1002aa01,00aa0100,00100200' -Controls : 6 -Simple ctrls : 1 - Card0.Amixer.values: - Simple mixer control 'IEC958',0 -Capabilities: pswitch pswitch-joined penum -Playback channels: Mono -Mono: Playback [on] - CurrentDmesg: - [ 43.890183] type=1400 audit(1375221797.042:30): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5" name="/usr/share/gvfs/remote-volume-monitors/" pid=2933 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 - [ 330.675164] type=1400 audit(1375222084.134:31): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1361 comm="cupsd" pid=1361 comm="cupsd" capability=36 capname="block_suspend" - [ 2016.826676] type=1400 audit(1375223771.934:32): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1361 comm="cupsd" pid=1361 comm="cupsd" capability=36 capname="block_suspend" - DistroRelease: Ubuntu 12.04 - HibernationDevice: RESUME=UUID=6d84a3d1-038d-4cf6-ba62-4c8937bf4a0c - InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) - IwConfig: - eth0 no wireless extensions. - - eth1 no wireless extensions. - - lono wireless extensions. - Lsusb: - Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 003: ID 0624:0296 Avocent Corp. - MachineType: Quanta Freedom - MarkForUpload: True - Package: linux (not installed) - ProcEnviron: - TERM=screen - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash - ProcFB: 0 radeondrmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=00a0e7af-77b9-4829-8f99-0fda2492da82 ro quiet splash initcall_debug vt.handoff=7 - ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 - PulseList: - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. - No PulseAudio daemon running, or not running as session daemon. - RelatedPackageVersions: - linux-restricted-modules-3.5.0-23-generic N/A - linux-backports-modules-3.5.0-23-generic N/A - linux-firmware1.79.1 - RfKill: - - Tags: precise - Uname: Linux 3.5.0-23-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: - - dmi.bios.date: 03/02/2012 - dmi.bios.vendor: AMI - dmi.bios.version: F03_3A07 - dmi.board.asset.tag: To be filled by O.E.M. - dmi.board.name: Windmill-EP - dmi.board.vendor: Quanta - dmi.board.version: To be filled by O.E.M. - dmi.chassis.asset.tag: To Be Filled By O.E.M. - dmi.chassis.type: 23 - dmi.chassis.vendor: Quanta - dmi.chassis.version: To Be Filled By O.E.M. - dmi.modalias: dmi:bvnAMI:bvrF03_3A07:bd03/02/2012:svnQuanta:pnFreedom:pvrC1:rvnQuanta:rnWindmill-EP:rvrTobefilledbyO.E.M.:cvnQuanta:ct23:cvrToBeFilledByO.E.M.: - dmi.product.name: Freedom - dmi.product.version: C1 - dmi.sys.vendor: Quanta + With precise and stock 3.5.0-23 kernel the installation and boot is + successful, but installing any kernel above 3.8 in precise fails to boot +
[Kernel-packages] [Bug 1206710] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755214/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755215/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755211/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755206/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755208/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755212/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755210/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] [NEW] [OCPv2 Windmill]: Can't install Raring or Saucy.
Public bug reported: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. ** Affects: opencompute Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected precise ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected precise ** Description changed: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. - With precise and stock 3.5.0-23 kernel the installation and boot is - successful, but installing any kernel above 3.8 in precise fails to boot - successfully. + With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. + AplayDevices: + Home directory /home/ubuntu not ours. + List of PLAYBACK Hardware Devices + card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] +Subdevices: 1/1 +Subdevice #0: subdevice #0 + ApportVersion: 2.0.1-0ubuntu17.1 + Architecture: amd64 + ArecordDevices: + Home directory /home/ubuntu not ours. + List of CAPTURE Hardware Devices + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2760 F pulseaudio + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + Card0.Amixer.info: + Card hw:0 'Generic'/'HD-Audio Generic at 0xdfe4 irq 113' +Mixer name : 'ATI R6xx HDMI' +Components : 'HDA:1002aa01,00aa0100,00100200' +Controls : 6 +Simple ctrls : 1 + Card0.Amixer.values: + Simple mixer control 'IEC958',0 +Capabilities: pswitch pswitch-joined penum +Playback channels: Mono +Mono: Playback [on] + CurrentDmesg: + [ 43.890183] type=1400 audit(1375221797.042:30): apparmor="DENIED" operation="open" parent=1 profile="/usr/lib/telepathy/mission-control-5" name="/usr/share/gvfs/remote-volume-monitors/" pid=2933 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 + [ 330.675164] type=1400 audit(1375222084.134:31): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1361 comm="cupsd" pid=1361 comm="cupsd" capability=36 capname="block_suspend" + [ 2016.826676] type=1400 audit(1375223771.934:32): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1361 comm="cupsd" pid=1361 comm="cupsd" capability=36 capname="block_suspend" + DistroRelease: Ubuntu 12.04 + HibernationDevice: RESUME=UUID=6d84a3d1-038d-4cf6-ba62-4c8937bf4a0c + InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) + IwConfig: + eth0 no wireless extensions. + + eth1 no wireless extensions. + + lono wireless extensions. + Lsusb: + Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 0624:0296 Avocent Corp. + MachineType: Quanta Freedom + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=screen + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=00a0e7af-77b9-4829-8f99-0fda2492da82 ro quiet splash initcall_debug vt.handoff=7 + ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.5.0-23-generic N/A + linux-backports-mod
[Kernel-packages] [Bug 1206710] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755207/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] AcpiTables.txt
apport information ** Attachment added: "AcpiTables.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755205/+files/AcpiTables.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1206710] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1206710/+attachment/3755209/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1206710 Title: [OCPv2 Windmill]: Can't install Raring or Saucy. Status in Open Compute Project: New Status in “linux” package in Ubuntu: Confirmed Bug description: [OCPv2 Windmill]: Can't install Raring or Saucy. I tried the latest daily saucy image with 3.10.0-6.17 and after installation the machine first fails to establish a network connection. NIC is plugged in and used to perform PXE boot. Then it proceeds to hang (during first boot after install) and stop responding to any keyboard actions. Can't switch tty etc. When loading the desktop, there is no indication that network -manager found any suitable physical network devices. I was unable to check whether the NIC interface was present in the /sys due to system halt and unresponsive keyboard. With precise and stock 3.5.0-23 kernel the installation and boot is successful, but installing any kernel above 3.8 in precise fails to boot successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/opencompute/+bug/1206710/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750284/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750281/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750283/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750269/+files/AplayDevices.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750280/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750268/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750282/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750277/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] Card0.Codecs.codec.3.txt
apport information ** Attachment added: "Card0.Codecs.codec.3.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750274/+files/Card0.Codecs.codec.3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] Re: Need driver support for IPMI device on OCPv2 Windmill
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1625 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xc262 irq 52' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0888,10ec0888,00100202 HDA:80862805,80860101,0010' Controls : 67 Simple ctrls : 25 DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=3c978014-bfb9-43e5-b497-193f13fd53e1 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: INSYDE StrawberryMountain MarkForUpload: True Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=32cb7b84-bce6-432a-8f2d-2adc2dff3c81 ro quiet splash initcall_debug vt.handoff=7 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 RfKill: Tags: precise Uname: Linux 3.5.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/18/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: SBM. 03.72.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrSBM.03.72.24:bd06/18/2012:svnINSYDE:pnStrawberryMountain:pvrSBM.03.72.24:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: StrawberryMountain dmi.product.version: SBM. 03.72.24 dmi.sys.vendor: INSYDE ** Tags added: apport-collected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750272/+files/Card0.Amixer.values.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750276/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750279/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750275/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750273/+files/Card0.Codecs.codec.2.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750278/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750271/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] ArecordDevices.txt
apport information ** Attachment added: "ArecordDevices.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750270/+files/ArecordDevices.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] AcpiTables.txt
apport information ** Attachment added: "AcpiTables.txt" https://bugs.launchpad.net/bugs/1156667/+attachment/3750267/+files/AcpiTables.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Confirmed Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1156667] Re: Need driver support for IPMI device on OCPv2 Windmill
I agree this is a kernel issue, and that we probably should be filling and tracking against linux. ** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1156667 Title: Need driver support for IPMI device on OCPv2 Windmill Status in MAAS: Invalid Status in Open Compute Project: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: The IPMI device is a custom module that adds support for the modified Intel management engine ipmi stack included by intel for this platform. $ ipmitool channel info Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.2.0-38-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04** # modprobe ipmi_si FATAL: Error inserting ipmi_si (/lib/modules/3.5.0-25-generic/kernel/drivers/char/ipmi/ipmi_si.ko): No such device **12.04.2** To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1156667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 964231] Re: System Stutter When HDMI/Displayport Monitor Is Connected
Sorry for the delay on this. That kernel worked perfectly! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/964231 Title: System Stutter When HDMI/Displayport Monitor Is Connected Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Precise: Confirmed Status in “linux” source package in Quantal: Confirmed Bug description: With a fresh install of Ubuntu 11.10 x64, the system has many "microfreezes" when I connect an external monitor via HDMI. These last maybe 10ms and occur about once per second. As I move my cursor around the screen, it stops motion during these microfreezes, causing a very irritating stutter effect. This only happens when using HDMI- when connected via VGA to an external monitor, the system behaves smoothly as expected. I started a thread about this a long time ago, but I never did find an answer: http://ubuntuforums.org/showthread.php?t=1817910 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7.1 Uname: Linux 3.3.0-030300rc7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,move,vpswitch,place,mousepoll,resize,wall,regex,session,snap,gnomecompat,imgpng,animation,expo,workarounds,unitymtgrabhandles,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sat Mar 24 18:30:09 2012 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:2080] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: PEGATRON CORPORATION A15 ProcEnviron: PATH=(cususername, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-030300rc7-generic root=UUID=a19e39dd-b510-4f9d-93f5-de6d40df10f1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 211 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: A15 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr211:bd06/17/2011:svnPEGATRONCORPORATION:pnA15:pvr1.0:rvnPEGATRONCORPORATION:rnA15:rvr1.0:cvnPEGATRONComputerInc.:ct9:cvr1.0: dmi.product.name: A15 dmi.product.version: 1.0 dmi.sys.vendor: PEGATRON CORPORATION version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/964231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1079933] Re: [Lenovo T530, W530]: External display does not work through Display port or VGA
Please see comment #3
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1079933
Title:
[Lenovo T530, W530]: External display does not work through Display
port or VGA
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” source package in Precise:
Confirmed
Bug description:
Problem:
Connecting a display through the display port does nothing. I can try to
press the key combo fn + f7 or trigger the monitor to refresh and the display
is still blank on the external monitor.
udev does not seem to notice the display port connection either.
Expected result: External display should be mirrored when inserting a
display port or VGA connection.
Video info
[0.729694] pci :00:02.0: Boot video device
[ 13.071619] Linux video capture interface: v2.00
[ 13.099290] uvcvideo: Found UVC 1.00 device Integrated Camera (5986:02d2)
[ 13.101511] usbcore: registered new interface driver uvcvideo
[ 13.101512] USB Video Class driver (1.1.1)
[ 13.182383] input: Video Bus as
/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input7
[ 13.183068] ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
ubuntu@201205-11132:~$ dmesg | grep -i graphics
[ 12.371300] [drm] MTRR allocation failed. Graphics performance may suffer.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-29-generic 3.2.0-29.46
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1539 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf253 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,17aa21f6,00100203
HDA:80862806,80860101,0010'
Controls : 36
Simple ctrls : 13
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Fri Nov 16 18:44:51 2012
HibernationDevice: RESUME=UUID=33af243d-8694-4458-a1eb-5c94d7303d8e
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
MachineType: LENOVO 235923U
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic
root=UUID=212db818-8dcd-4bbd-94a9-0a9ca8d086a3 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-29-generic N/A
linux-backports-modules-3.2.0-29-generic N/A
linux-firmware1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G4ET37WW (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 235923U
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG4ET37WW(1.12):bd05/29/2012:svnLENOVO:pn235923U:pvrThinkPadT530:rvnLENOVO:rn235923U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 235923U
dmi.product.version: ThinkPad T530
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1079933/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
