** Attachment added: "dmesg-customkernel-cpufreq.debug7.txt"
http://launchpadlibrarian.net/25796591/dmesg-customkernel-cpufreq.debug7.txt
--
CPU Frequency Scaling Not Supported for Intel Centrino Duo Processors
https://bugs.launchpad.net/bugs/156066
You received this bug notification because
Hm, I added cpufreq.debug=7 after that by editing the command on the
grub boot screen, I will try editing the menu.lst instead.
--
CPU Frequency Scaling Not Supported for Intel Centrino Duo Processors
https://bugs.launchpad.net/bugs/156066
You received this bug notification because you are a memb
[0.00] Kernel command line:
root=UUID=dbb5c117-c690-4c20-a4bc-bfb6e5c87877 ro quiet splash cpufreq.debug=7
[0.00] Unknown boot option `cpufreq.debug=7': ignoring
--
CPU Frequency Scaling Not Supported for Intel Centrino Duo Processors
https://bugs.launchpad.net/bugs/156066
You re
Yes, I had installed that kernel via the package manager than added
cpufreq.debug=7 to the command line by editing menu.lst - where there
any additional steps I needed to do?
--
CPU Frequency Scaling Not Supported for Intel Centrino Duo Processors
https://bugs.launchpad.net/bugs/156066
You receiv
CPU frequency scaling is working fine now, and I think I may know why -
whenever the updater has prompted me to update my menu.lst, i've always
told it to retain the old version because I have also specified Windows
in the menu.lst and don't want to keep adding it. As a result, new
kernels have bee
Ah, I hadn't specified the 2.6.28-11 kernel, it was still booting the
old one. (2.6.27-something). Booting 2.6.28-11 now.
--
CPU Frequency Scaling Not Supported for Intel Centrino Duo Processors
https://bugs.launchpad.net/bugs/156066
You received this bug notification because you are a member of
I can confirm that this is present in the latest Jaunty RC. Upgraded
from 8.10 to 9.04 RC tonight using update-manager -d and on startup I
get a message saying that frequency scaling isn't supported, despite it
working perfectly under 8.10. The frequency scaler applet also confirms
this, showing my
@Stefan, i'm unable to test with 8.10 since I no longer have that
installed - I upgraded from 8.10 to 9.04 RC hence overwriting my
existing install. Like the original submitter, the processor is a
Centrino duo, but i'm unsure how to obtain the exact model number under
Linux.
I've attached all the
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/25624770/dmesg.txt
--
CPU Frequency Scaling Not Supported for Intel Centrino Duo Processors
https://bugs.launchpad.net/bugs/156066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "dmidecode.txt"
http://launchpadlibrarian.net/25624780/dmidecode.txt
--
CPU Frequency Scaling Not Supported for Intel Centrino Duo Processors
https://bugs.launchpad.net/bugs/156066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Last attached file requested.
** Attachment added: "lsmod.txt"
http://launchpadlibrarian.net/25624812/lsmod.txt
--
CPU Frequency Scaling Not Supported for Intel Centrino Duo Processors
https://bugs.launchpad.net/bugs/156066
You received this bug notification because you are a member of Ubuntu
Sadly, I lost the disk a while back - i'll redownload it and give it a
go though.
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz
stepping: 6
cpu MHz : 23
I'm seeing this with a HP NC523SFP 10G NIC and MASS 2.4.0~beta2 on
Ubuntu 18.04. If I UEFI boot from the NIC, it eventually brings up a
grub shell. Taking a packet capture confirmed the same ARM storm
behaviour when attempting to boot - thousands of packets from the server
that is being commissione
Public bug reported:
I have an old machine that does not have any form of IPMI or remote
power control. I created a new machine in MAAS with the "Manual" power
type, expecting that I would still be able to use it with MAAS but that
I would need to manually power the machine on and off.
However, w
My apologies, I created this in completely the wrong project.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768657
Title:
Testing Fails due to Power Issue with Manual Power Type
To manage notifica
Output of dmesg on Bionic - note interface MTU being changed from 9000
to 1500.
** Attachment added: "Bionic dmesg output.txt"
https://bugs.launchpad.net/maas/+bug/1774666/+attachment/5147502/+files/Bionic%20dmesg%20output.txt
--
You received this bug notification because you are a member of
** Attachment added: "Xenial dmesg"
https://bugs.launchpad.net/maas/+bug/1774666/+attachment/5147508/+files/xenial%20dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774666
Title:
Bond i
** Attachment added: "MAAS Curtin Config"
https://bugs.launchpad.net/maas/+bug/1774666/+attachment/5147504/+files/maas%20curtin%20config.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774666
T
** Attachment added: "bionic ip link sh"
https://bugs.launchpad.net/maas/+bug/1774666/+attachment/5147503/+files/bionic%20ip%20link%20sh.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774666
T
** Attachment added: "Xenial /etc/network/interfaces.d/50-cloud-init.cfg"
https://bugs.launchpad.net/maas/+bug/1774666/+attachment/5147506/+files/xenial%20eni.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Attachment added: "MASS dpkg"
https://bugs.launchpad.net/maas/+bug/1774666/+attachment/5147507/+files/maas%20dpkg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774666
Title:
Bond interfa
** Attachment added: "Xenial dpkg | grep cloud-init"
https://bugs.launchpad.net/maas/+bug/1774666/+attachment/5147509/+files/xenial%20dpkg%20cloud-init.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
@cyphermox I'm deploying the machine back to Bionic to try this now. Can
you confirm where exactly in the netplan config I need to set this?
(e.g. in the bonds section, or add a new eth1 definition to the
ethernets section?)
--
You received this bug notification because you are a member of Ubuntu
I've added "mtu: 9000" to the bonds section, which now reads as follows;
bonds:
eth1:
mtu: 9000
interfaces:
- enp5s0f0
- enp5s0f1
- enp6s0f0
- enp6s0f1
parameters:
down-delay: 0
24 matches
Mail list logo
