I'm not sure we are understanding each other correctly. I am not sure
what the change you made to multipath-tools has to do with this bug, but
the change you made to parted which is still sitting in the -proposed
pocket is incorrect and needs to be rejected. Instead of changing
parted, it is
Your output there clearly shows that the verification *failed*. This
change needs to be reverted as it does completely the wrong thing. The
correct name is p1, not -part1. It is multipath-tools that needs
changed, not parted. Please revert the parted change immediately.
** Changed in: parted
I'm guessing that this particular scsi controller supports hot plug and
so identifies the drives as removable since technically you can yank out
the raid bays and replace them while the system is on. The whole
concept of whether a drive is "removable" or not is a hand waving best
guess that
** Changed in: multipath-tools (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/737027
Title:
kpartx udev rule is broken
We have already spent a lot of effort over the years going with #2, so
turning around at this point isn't the right thing to do. The one place
I still see multipath-tools doing the wrong thing is in its kpartx.rules
file, which still contains this stanza:
ENV{DM_STATE}=="ACTIVE",
sudo /etc/init.d/udev stop
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1473903
Title:
parted will generate two devices when adding one partition on mpath
device
To
I'm not sure why the error from parted's mkpart command, but the fact
that there are two different devices is due to the multipath-tools guys
deciding to break traddition and configure their udev script to run
kpartx and ask it to create the partition with the form base-partX
rather than the baseX
** Package changed: lm-sensors (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1472549
Title:
As the error message indicates, your system does not have any supported
sensors.
** Changed in: lm-sensors (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
Please run grep fancontrol /etc/init.d/* and post the output.
** Changed in: lm-sensors (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
to, but that
may be considered a separate issue.
For now I will focus on at least getting rid of the bad behavior of
permanently chowning files.
** Changed in: libvirt (Ubuntu)
Status: Won't Fix = Triaged
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Phillip Susi (psusi)
--
You
Public bug reported:
When starting a vm in virt-manager and pointing it to an iso file in my
home directory, it changes the permissions so it can only be accessed by
the owner, and chowns the file to libvirt-qemu.kvm, so I no longer have
access to it. It should not be changing permissions.
**
Public bug reported:
/etc/init.d/libvirt-bin lists Should-Start: avahi. There is no such
service. Apparently it has been renamed to avahi-daemon.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
libvirt has not been updated since 2013 and upstream has had a number of
new releases. Please update.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Tags: needs-packaging
--
You received this bug notification because you are a member of
** Changed in: lm-sensors (Ubuntu)
Status: Fix Committed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1426787
Title:
the sensors don't show real CPUcore temp
You can add acpi_enforce_resources=lax to your kernel command line
arguments ( edit /etc/default/grub, and run sudo update-grub ) to force
the module to load, though there is a chance that doing so may cause
problems.
** Changed in: lm-sensors (Ubuntu)
Status: New = Invalid
--
You
Closing due to PEBKAC error ;)
** Changed in: lm-sensors (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/485899
Title:
pwmconfig
** Changed in: lm-sensors (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1406499
Title:
AMD Kaveri support needs lm-sensors 3.3.5
To
** Branch linked: lp:~psusi/ubuntu/vivid/lm-sensors/merge
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1406499
Title:
AMD Kaveri support needs lm-sensors 3.3.5
To manage
If you aren't using gpt then you aren't getting the error message and
thus aren't related to this bug. That message again was:
Assertion (last_usable = disk-dev-length) at
../../../libparted/labels/gpt.c:718 in function _parse_header() failed.
--
You received this bug notification because you
It seems the bug on the gdisk side was fixed sometime between 0.5.1 and
0.8.1: the latter version now correctly reports the size error.
** Changed in: gdisk (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team,
If sensors-detect doesn't detect it then yea, it's not supported.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1389647
Title:
lm-sensors don`t recognize fan in the laptop ASUS
That isn't a bug...
** Changed in: lm-sensors (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1389647
Title:
lm-sensors don`t recognize
This doesn't seem to have anything to do with ubiquity what makes
you think this isn't simply your keyboard's auto repeat feature and
you're holding down the key for too long?
** Package changed: ubiquity (Ubuntu) = qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Status: New = Incomplete
** Package changed: util-linux (Ubuntu) = openvpn (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1359296
Title:
Shutting down OpenVPN before umount network shares causes
Probably because redhat has an older version of gcc.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1348945
Title:
-lsensors doesn't link to libsensors
To manage notifications
What? There doesn't seem to be any such thing as module-init-
tools.conf. The modules in /etc/modules are loaded by /etc/init.d/kmod,
which runs in rcS.d, before anything in rc2.d.
** Changed in: lm-sensors (Ubuntu)
Status: New = Incomplete
--
You received this bug notification
Ahh, you must be still running 12.04. This was fixed after 12.04 by
switching from module-init-tools to kmod.
** Changed in: lm-sensors (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Then you should upgrade to 14.04.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1322625
Title:
sensord daemon does not detects chips
To manage notifications about this bug go
Sure, but only critical fixes get backported to older releases.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1322625
Title:
sensord daemon does not detects chips
To manage
Public bug reported:
I shutdown my server to single user mode and ran a dist-upgrade. The
postfix postint started the daemon, even though it is not supposed to be
running in single user mode.
** Affects: postfix (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Just created a fresh install of 13.10 in a vm, swapped
/etc/apt/sources.list to trusty, shutdown to single user mode, confirmed
with runlevel that the system was in single user mode, and ran apt-get
install postfix to upgrade it, and sure enough, it it started postfix.
** Changed in: postfix
It looks like the problem is in invoke-rc.d: manually running invoke-
rc.d postfix restart, while in single user mode, starts postfix.
** Package changed: postfix (Ubuntu) = sysvinit (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
What does Windows have to do with it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/42376
Title:
hibernate should hide grub menu
To manage notifications about this bug go to:
If the proprietary amd graphics driver is causing excessive heat, you
will need to take that up with amd, or stop using the proprietary
driver.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
You don't use ---pretend-input-tty in conjunction with --script. The
point is to pretend that you are a human, not a script.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1212492
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1093918
Title:
grub-probe auto-detection fails on raid
Public bug reported:
I booted the 13.10 live cd using -vga std ( since the default cirrus no
longer works correctly ) and it comes up using the full resolution of my
real screen, which is annoying since the window does not fit no the
screen. I went into the display control pannel to switch to a
The full command line was:
qemu-system-x86_64 --enable-kvm -m 1200 -drive
if=virtio,file=img,cache=unsafe -drive if=ide,file=Downloads/trusty-
desktop-amd64.iso,media=cdrom -vga std -boot d
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** No longer affects: multipath-tools (Ubuntu Quantal)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1093918
Title:
grub-probe auto-detection fails on raid
To manage
The backport to precise is still waiting for someone to test and verify
it, see comment #56.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1093918
Title:
grub-probe
** Changed in: multipath-tools (Ubuntu Precise)
Milestone: ubuntu-12.04.3 = ubuntu-12.04.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1093918
Title:
grub-probe
Looks like the arguments to parted are backwards.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1212444
Title:
cc_growpart failed in auto grow mode with Error: Could not stat
You have to not use --script and parse the output for the warning and
answer yes. I have been mulling over a --force-things system to allow a
script to specify that it expects a specific error and how it should be
handled but it isn't easy the way libparted is structured.
--
You received this
IIRC, parted assumes --script mode when stdin is not a tty. There was
an undocumented switch that the test suite uses to override this, or I
thought that expect allocates a pseudo tty (might need a switch) and
that should also do the trick.
--
You received this bug notification because you are
Currently the only way to have parted resize a busy partition is to use
interactive mode rather than script mode and say yes at the prompt.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Before running dmraid -ay, what does blkid show?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/941874
Title:
(fakeraid) root device not activated during boot
To manage
If /dev/mapper/pdc_ebdeeaiceb does not exist without you having to run
dmraid, then it is unrelated to this bug. Please file a new one.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Description changed:
kpartx was mapping the entire extended partition then stacking the
logical partitions on that device. This exposes a device that otherwise
appears to be an entire disk device containing the logical partitions,
and this confuses grub. The extended partition is
As sensors-detect said, there is no driver for this chip, so this is not
a bug.
** Changed in: lm-sensors (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
I guess I haven't had to modify my sieve scripts in a while since I
didn't notice this until I came across this bug report, but yea, since
upgrading my server to quantal, I can't modify my sieve scripts as
managesieved just crashes every time.
** Tags removed: dovecot managesieved segfault sieve
Looks like debian already fixed it and that version made it into raring.
** Changed in: dovecot (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
This package has been removed from Ubuntu. Closing all related bugs.
** Changed in: firestarter (Ubuntu)
Status: Fix Committed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
** Summary changed:
- upgrading to 8.10
+ postinst doesn't handle failure of dnshostname
** Changed in: kerberos-configs (Ubuntu)
Status: Confirmed = Triaged
** Changed in: kerberos-configs (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are
** Branch linked: lp:~psusi/ubuntu/precise/multipath-tools/fix-dmraid-
extended-partitions
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1093918
Title:
grub-probe
** Changed in: multipath-tools (Ubuntu Precise)
Status: New = In Progress
** Changed in: multipath-tools (Ubuntu Precise)
Assignee: (unassigned) = Phillip Susi (psusi)
** Changed in: multipath-tools (Ubuntu Precise)
Importance: Undecided = Critical
** Changed in: multipath-tools
I believe the modules are now auto loaded on demand. Is this still an
issue for you?
** Package changed: devmapper (Ubuntu) = lvm2 (Ubuntu)
** Changed in: lvm2 (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Without a way to reproduce the problem, and the fact that the conf file
in the package does not look like that, I don't think we have a bug
here. Combined with a lack of input for several years, I think it's
time this is put to rest.
** Changed in: postfix (Ubuntu)
Status: Confirmed =
Closing this bug due to lack of input for over a year.
** Changed in: backuppc (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to backuppc in Ubuntu.
https://bugs.launchpad.net/bugs/68729
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read How to report bugs effectively
Unless you have setup fancontrol ( which it seems you have not ) then
lm-sensors nor any other component in Ubuntu is in control of your fans.
The hardware controls them, and you said they do speed up so it sounds
like that hardware control is working properly. You may be able to run
the
You will need to seek support from your hardware vendor since
overheating is a hardware defect.
** Changed in: lm-sensors (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
The current raring version, which appears to be 1.4.0+dfsg-1expubuntu3.
Also I guess this should be under just the qemu package now rather
than -kvm.
The command line is qemu -drive file=whatever.iso,if=virtio,media=cdrom.
With or without the media argument seems to make no difference; either
way
Are you sure it actually speeds up when you set it too low? I have
noticed that the Intel stock CPU fans seem to have a minimum speed they
will refuse to go below, but when you try, it just refuses to go any
lower rather than speeding up.
--
You received this bug notification because you are a
Public bug reported:
Trying to install Ubuntu or Debian using virtio to emulate the cdrom
fails. This appears to be due to the drive appearing to be a hard disk,
rather than a cdrom, despite the media=cdrom argument to qemu.
I'm not sure if this is a bug in qemu, or the kernel virtio driver?
*** This bug is a duplicate of bug 1103111 ***
https://bugs.launchpad.net/bugs/1103111
** This bug has been marked a duplicate of bug 1103111
Upgrade failure
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unixodbc in Ubuntu.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did the other errors go away? Those were odd... looked like something
dmraid might say but AFAIK it isn't run by update-grub.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined -
kpartx is incorrectly mapping the entire extended partition, then
building the logical partitions on top of the extended. Bad kpartx.
** Also affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
I believe I have fixed the problem. Please add my PPA to your sources
and update:
sudo apt-add-repository ppa:psusi/ppa
sudo apt-get update
sudo apt-get upgrade
** Branch linked: lp:~psusi/ubuntu/raring/multipath-tools/fix-extended-
partitions
--
You received this bug notification because
Have you tried 12.10?
** Changed in: lm-sensors (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1093013
Title:
sensors-detect doesn't
Please stop changing the status.
** Changed in: lm-sensors (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1078922
Title:
Fan runs
Then I'm afraid I have to stand by what I said before: this isn't a bug.
You will need to look into your motherboard manual to see if there are
settings you can tune for the fan.
** Changed in: lm-sensors (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because
Can you boot 12.10 using the kernel from 12.04 and see the lower
temperature come back?
** Changed in: lm-sensors (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
Have you installed lm-sensors and configured fancontrol?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1078922
Title:
Fan runs unnecessary
To manage notifications about this
Are you saying that this has been fixed in 11.10?
** Changed in: lm-sensors (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/1062310
If you aren't using fancontrol, then there's no bug here. Without that,
the fans are controlled by the hardware in response to temperature rise.
You have nothing to worry about as far as damage goes as processors are
intended to handle 90-100 C, so even 52 is quite cool. Often times the
system
Unless you must dual boot this system with Windows, the best thing to do
is not to use fake raid. Switch to regular Linux software raid instead.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
This looks like a kernel regression. We will need to narrow down where
it was introduced. Could you try 11.04 and 11.10 next?
** Package changed: lm-sensors (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Adi, dmraid is for fake hardware raid support, not the software raid you
are using. Your issue seems to be unrelated to dmraid or this bug
report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
Can you please boot the 10.10 livecd and verify that you still get a
correct reading there, and also run the following command and attach the
resulting file ( DSDT.gz ):
sudo cat /sys/firmware/acpi/tables/DSDT | gzip -c - DSDT.gz
** Changed in: lm-sensors (Ubuntu)
Status: New =
The broken/nonfunctional udev rule has not yet been removed in kpartx,
but 12.04 uses kpartx to activate dmraid partitions and so supports GPT.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
** Changed in: dmraid (Ubuntu)
Importance: High = Critical
** Changed in: multipath-tools (Ubuntu)
Importance: High = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
I've fixed both packages to get this working and set up an isw dmraid
with my old disks and installed precise and the updated packages to
verify it works. Just waiting for a sponsor to merge the changes.
** Changed in: dmraid (Ubuntu)
Status: Fix Released = In Progress
** Changed in:
The -p is to disable dmraid's internal handling of partitions in favor
of letting kpartx take care of it. This was done because kpartx also
supports GPT, but dmraid does not.
Can you try updating your initramfs and see if that helps?
sudo update-initramfs -u
Also please make sure you are
What do you mean by added kpartx hooks?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/941874
Title:
(fakeraid) root device not activated during boot
To manage
Ok, kpartx has a hook rule that is supposed to do that already, but for
some reason, it is not being installed. It looks like a packaging error
of some sort.
** Changed in: multipath-tools (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a
) = Phillip Susi (psusi)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/941874
Title:
(fakeraid) root device not activated during boot
To manage notifications about this bug
Wait a second, the kpartx udev rule shouldn't have anything to do with
dmraid. The dmraid udev rule takes care of running kpartx.
** Changed in: multipath-tools (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Then it isn't a bug in lm-sensors, but in the hardware/firmware of the
motherboard.
** Changed in: lm-sensors (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
When this happens, what is the output from the following commands:
sudo dmsetup table
sudo kpartx -l /dev/sdb1
** Changed in: multipath-tools (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
It looks like you have not configured fancontrol so it isn't actually
working. Can you try removing the package and see if the behavior
remains the same?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
You must write a config file for it by hand or using pwmconfig.
** No longer affects: lm-sensors (Ubuntu Oneiric)
** No longer affects: lm-sensors (Ubuntu Precise)
** Changed in: lm-sensors (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a
This is really a question but since it was also filed as a question at
the time, and been answered, I'm just going to close the bug now.
** Changed in: lm-sensors (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This appears to be a hardware defect that needs a workaround in the
kernel k8temp driver. Such a workaround may already be in place. Is
this still an issue with Ubuntu 11.10?
** Package changed: lm-sensors (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed =
Config files don't contain messages, they configure fancontrol to work.
Is the man page not sufficient?
I suppose the package could have a debconf question that prompts you to
run pwmconfig when you install it...
** Summary changed:
- fancontrol cannot read its own configuration file
+
Yes, that's exactly the idea.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/884177
Title:
fancontrol should have debconf prompt to run pwmconfig
To manage notifications about
Unfortunately, lm-sensors has no way of knowing whether or not your
particular motherboard has the sensor properly wired. If you wish to
hide sensors that your motherboard does not correctly use, then you can
edit /etc/sensors3.conf. See man sensors.conf.
** Changed in: lm-sensors (Ubuntu)
It looks like you do not have any supported sensors. You mention that
this worked on a previous release. Can you boot that release and
provide the results of running sensors-detect there? Also you might
want to answer yes to the question to probe i2c devices.
** Changed in: lm-sensors
Please provide the output of the sensors command.
** Changed in: lm-sensors (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in Ubuntu.
https://bugs.launchpad.net/bugs/710040
Title:
This report has become an extended support discussion, and does not
describe an actual bug, therefore I am closing it.
** Changed in: lm-sensors (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
1 - 100 of 125 matches
Mail list logo
