d1zzyg, thanks for testing and the feedback. Since we have received no
response from anyone else regarding the Hardy Heron 8.04 Alpha/Beta
release I'm going to close this for now against the Hardy kernel.
Please feel free to reopen (ie set the Status back to New) if you still
experience issues
Fixed - for us at least.
I am working in a corporate environment and the pre-boot config is out
of my hands (support contracts blah blah blah). I recently got hold of
an identical server and tried to install Gutsy -- it worked without a
hitch! It turns out that on the first machine there was a
I'm having the same problem with a couple of DL380 G4s.
The fix involving the removal of sym53c8xx drivers worked on an older G1
we have, but yields no results on the newer machines.
I just keep getting back to the partition editor which says things like
failed to read drive geometry and
Can someone confirm this issue for the latest 8.04 Hardy Alpha release?
Thanks.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: New = Won't Fix
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
Compaq Proliant DL360: raid controller should use cpqarray, not
** Tags added: qa-hardy-kernel
** Tags removed: qa-hardy-list
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Hi there,
This may benefit others who have also had problems installing Ubuntu Server
7.10.
I have just managed to install Ubuntu Server 7.10 on my Compaq DL360 G1 by
followed Alex Smith's recommendation above using the module blacklist technique.
- Boot from the Ubuntu Server 7.10 CD
- At the
I had exactly the same problem on my G1 as well. After searching the web all
morning and reading all your posts, I was not bothered in following all the
steps outlined in the fix ISO. I am using Gutsy 7.10 server insall and had the
same problem.
So, what I ended up doing was, used the
This is not even understood for Gutsy and Hardy so far, so nothing to
fix for Dapper.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Triaged = Won't Fix
Target: dapper-updates = None
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-source-2.6.22 = linux
Target:
On Jan 9, 2008 12:29 AM, tad1073 [EMAIL PROTECTED] wrote:
From the Ubuntu boot screen I selected Check CD for Defects and got
the errors listed below:
[364.283722] ata1.01: Exception Emask 0x0 Sact 0x0 Serr 0x0 action 0x2
Frozen
[364.283771] ata1.01 (BMDMA stat 0x44)
[364.283822] ata1.01:
I forgot to mention that the CD was ordered from Ubuntu, I ordered two
more which are the text based installers. I will check it on another
machine. If there are no errors can you help me installing it on the
machine mentioned.
I am not necessarily going to use that machine as a server, for now
I checked the CD and there are no defects on it or with it. i kind of
figured it was a compatibility issue, so now what do I do?
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are
I checked the CD and there are no defects on it or with it. i kind of
figured it was a compatibility issue, so now what do I do?
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are
tad: Not sure if your issue has anything to do with the
cpqarray/sym53c8xx module issue. Maybe you ought to file a separate bug
report? I don't mean to dismiss your problem, just trying to keep this
particular bug discussion on topic.
--
Compaq Proliant DL360: raid controller should use
Capt. Salty: I agree.
Tad: If the CD passes the check on a different system, then I would suspect
the CD-ROM drive on your system. The original problem this thread was about
was specifically the hard-drive controller being recognized correctly
*after* installation.
From what you've told us, I'd
i guess I will file a seperate bug report for the issue I am having. In
the mean time I will try to swap the cd-rom drive out and check it
again.
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification
Thanks for the help. Bug filed #181678
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Spec:
Compaq Proliant ML330
Pentium III 733mhz 256k cache
256mb ram
Compaq Smart Array 431 Controller set to RAID0 w/25.9gb=3/9.1gb hd's
System Embedded IDE Controller
SCSI Controller
I have been trying to get Ubuntu 7.10 on that machine for a week now. I
keep getting the same errors and I am
Not fixed in 7.10 Server. WTH??
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Ben says this is not practical to do for a stable dapper update, so
backing this out of Dapper.2.
** Changed in: linux-source-2.6.15 (Ubuntu)
Target: ubuntu-6.06.2 = dapper-updates
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
Could one of you paste the output of lspci -vvnn from a feisty boot?
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-rc-
fixes-2.6.git;a=commitdiff;h=b2b3c121076961333977f485f0d54c22121df920
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are a
I saw that fix when I was googling around, but that fix went into .18,
and it's fixed on most distros with .18 or newer, so I was mystified as
to why it was happening on Gutsy.
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You
As a workaround, you can add this to the kernel command line when
booting:
sym53c8xx.blacklist=true
That worked for me on my Compaq Proliant DL360 (G1), after some poking
around in busybox I found that d-i can have modules blacklisted by
adding module.blacklist=true to the command line.
--
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete = Triaged
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team
Status: New = Triaged
Target: None = ubuntu-7.10-beta
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: New = Incomplete
--
Compaq Proliant DL360: raid controller should use cpqarray, not sym53c8xx
https://bugs.launchpad.net/bugs/110585
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
26 matches
Mail list logo
