Using 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009
x86_64 GNU/Linux
Jaunty upgrade worked fine on my other computer, using an Intel Core 2
Duo E8500 CPU. The computer i'm having problems with has an AMD X2 6000+
CPU, running at 3.0GHz but can downscale to 1.0GHz.
It appears power
Addition: after installing powernowd package, which implied removing the
cpufreqd package, CPU frequency scaling works again on my Athlon X2
6000+. So the problem seems to be related to cpufreqd.
--
cpu frequency scaling not supported after upgrading to 9.04
https://bugs.launchpad.net/bugs/365798
I can confirm this issue. I have Athlon X2 6000+ CPU and after upgrading
to 9.04, the applet controling the frequency doesn't allow me to change
the frequency and it stays in the maximum frequency setting of 3.0GHz.
Because i also have cpu temperature applet, i can verify that the power
management
For those who say this is working for them, did you actually upgrade
from 8.10 or did you do a clean install? This may be a bug for people
upgrading only, though that's just speculation. Also, Intel uses a
different driver (EIST) than AMD (cool'n'quiet).
--
cpu frequency scaling not supported in
BUGabundo: it gives me a popup asking for my password, like any process
that needs super-user privileges i guess. After that, it would allow me
to change the frequency manually. Regardless of that, when my pc is idle
it should throttle down to 1.0GHz which is did just this morning before
i upgraded
The message "CPU Frequency scaling not supported" appears when you hover
over the CPU Frequency Scaling Monitor (i have version 2.26.0) which is
an applet you can add to the Panel. However, in my case it doesn't state
that frequency is insupported, and the suggestion frozenskunk gave me
(adding "ac
I may have a different solution, that addresses the needs of most points
addressed here.
In the Gnome menu, for example Applications > Accessories, each
application should have both a title name and a description beneath it,
preferably with a small font size and silver-grey coloured text.
For exa
It's enabled by default, the way to shut it off has changed and the old
method no longer works. So if anyone needs to disable this 'feature' -
it likely requires hours of their time googling to fix it. Very smart
move!
To fix this issue:
sudo nano /etc/hal/fdi/policy/disable-emulate3buttons.fdi
Hello Colin,
I hope i'm not getting on your nerves. But the window for fixing
iSCSI-on-root bugs in time for 10.04 is closing rapidly.
I hope you can at least address this bug in time:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/546964
Another user called jkao has also confirmed thi
Great news!
Thanks Colin!
Will try out a nightly as soon as possible.
Kind regards,
Jason Edwards
On Wed, Apr 21, 2010 at 12:51 PM, Colin Watson wrote:
> Whoops! Thanks for the analysis - I'll get this fixed for final.
>
> ** Package changed: open-iscsi (Ubuntu) => initramfs-tools (Ubuntu)
>
Colin, my apologies for my late response. I found some time to play with
iSCSI again and used a fresh setup with final Ubuntu 9.10 server,
without much issues.
The problems i had appear to originate from the date Ubuntu 9.10 was
still in RC-phase; even after upgrading them as the final came out. I
I tried this with 9.10 server amd64 final ISO, but the problems stay:
=
PROBLEM #1: no suitable initrd.img file is provided that allows for
iSCSI-on-root booting, though it is possible to create one after
installing 9.10 to a VM for example and create a custom initrd.img file,
like i did.
Public bug reported:
Reading the release notes of karmic alpha's it clearly marks
improvements to iSCSI support during install. But when i try this with
karmic alpha6 amd64 in a Virtualbox VM, when it gets to the partition
phase it simply lists no partitions at all and no option to activate
iSCSI
I just tested again with a server nightly, but the same problem is still
present as of April 5th, 2010 lucid nightly.
This time i tested within Virtualbox, which uses pcnet ethernet driver;
i hope the screenshot may provide a clue of what's going wrong here.
** Attachment added: "Screenshot showi
Confirmed fixed. I just downloaded the new RC that was released today.
It still had the same bug, however by setting ip=:eth0:dhcp i
managed to boot. After i updated using apt-get update && apt-get dist-
upgrade, the initramfs package was updated and wrote a new initrd.img.
That one also boots
Public bug reported:
I downloaded Ubuntu 10.04 beta1 server amd64 ISO and booted it. I then
tried to setup iSCSI with no local disks present, which worked on 9.10.
But on 10.04 beta1, a few installer quirks make any user errors
punishing, as you would have to reboot the CD everytime. Here's the
pr
Public bug reported:
Binary package hint: open-iscsi
This is a follow-up of bug 546944; which focuses on issues with the
installer. This bug focuses on boot problems after having used the
installer cd to install to the iSCSI volume. After that, the vmlinuz and
initrd.img on the iSCSI install are
I tried the 20091006 daily build, in a Virtualbox with no local disks.
It still doesn't appear to give any possibility to use iSCSI. There's
notification about no disks being detected, or any of that.
For your convenience i attached a screenshot, located at:
http://img40.yfrog.com/img40/4483/scree
Ive tried the alternate cd image too, located here:
http://cdimage.ubuntu.com/daily-live/20091006/
Still no option to use iscsi, i did get a screen about no disk being
detected, with a list of drivers. Not any one contained "iscsi" or
something like that. If i choose the first option "Continue wit
The server daily build ISO indeed worked, it did prompt me for iSCSI and
install was a breeze, though setting up the network boot and mount root
part is not. Some more documentation on this would be nice, especially
now that Ubuntu has more or less "out of the box" support for iSCSI. For
example, p
Public bug reported:
Binary package hint: partman-iscsi
Now that the server daily karmic builds support installing to iSCSI
targets with no local disks present, this makes diskless ubuntu systems
possible. While the installation itself was very easy, setting up the
network boot correctly afterwar
Hm this bug still appears to be prevalent for those using a KVM switch.
After i switch to another pc and back again, it appears the
Emulate3Buttons feature is turned on again, even with the .fdi file
present. Apparantly the fdi file is a one-time configuration and
whenever a device disconnects and
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/33798313/AlsaDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/33798314/ArecordDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/33798315/BootDmesg.txt
**
Public bug reported:
>From the ubuntu-server karmic daily snapshot ISO from 15 october 2009.
Its an iSCSI-on-root install that does some heavy network I/O. Its
running inside Virtualbox.
I saw multiple bug reports already, but they seemed to differ. So i post
anyway if its the same issue as the o
Sorry for bumping this bug, but i files a similar bug here:
https://bugs.launchpad.net/ubuntu/+bug/435290
Reading the last statement that there has to be a local disk present for
the iSCSI package to become loaded; is this intentional or is this a
bug? It surely isn't consistent with the goals of
Thanks for your update. If i understand correctly, your fix will be
included in the next Ubuntu 9.10 (beta) release?
You said i should have gotten a 'choice menu' when no local disks were
found. However all i got was a blank list in the manual partitioner. In
previous installs i first got a colour
Alright thanks for your information. I'll retry with a newer release (RC
probably) and will report back in this bug thread.
--
Karmic installer does not prompt for iSCSI install
https://bugs.launchpad.net/bugs/435290
You received this bug notification because you are a member of Ubuntu
Bugs, whic
27 matches
Mail list logo
