This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Karmic is no longer supported. Please test to see whether or not this
problem still exists in natty. Thanks!
** Changed in: linux (Ubuntu Karmic)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Karmic)
Milestone: karmic-updates => None
** Changed in: linux (Ubuntu)
Jaunty is no longer supported.
** Changed in: linux (Ubuntu Jaunty)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Jaunty)
Milestone: jaunty-updates => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Changed in: linux (Ubuntu)
Assignee: Andy Whitcroft (apw) => (unassigned)
** Changed in: linux (Ubuntu Karmic)
Assignee: Andy Whitcroft (apw) => (unassigned)
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification becau
Different Chipset. Different bug.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
This problem went away for me in the more recent Karmic kernels, but
after upgrading to Lucid, it has resurfaced. I am once again
intermittently getting dumped to a busybox prompt instead of booting.
3ware 8006-2LP RAID controller
Intel P35 chipset
--
Fails to find boot device in Intel D945Gnt
** Tags added: cherry-pick kernel-uncat
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Closing this oldish release notes task; I understand that the scope of
the problem is smaller now, since the systems actually boot albeit
slowly; so I'm closing the task, but please reopen if it necessary.
** Changed in: ubuntu-release-notes
Status: Confirmed => Invalid
--
Fails to find b
I've just realized I made a mistake, Intrepid Ibex 8.10 "will reach" EOL
on 30 "APRIL" 2010.
Sorry for this.
Anyway, I think that one month doesn't make any difference now.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification be
Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on
30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please feel free to report any other bugs you may find.
Thank you.
** Changed in: linux (Ubuntu Intrep
Since it worked in Hardy, isn't it still regression potential? I have one
box on Hardy due to this buh.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: intrepid jaunty karmic
** Tags removed: regression-potential
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
>I am also experiencing a similar problem on my Asrock P4i65GV (intel
ICH5) chipset.
The problem described in this comment is a different bug. Please file a
new bug for this.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification
I am also experiencing a similar problem on my Asrock P4i65GV (intel ICH5)
chipset.
I know that in in intrepid and jaunty was necessary to blacklist intel_agp
module to make that mobo working.
With karmik the only solution to make live CD bootable (and installable) is to
expand inittramfs and sq
** Tags added: iso-testing
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
i've got similar issue since Ubuntu Karmic (tried Daily build/beta), I
am using a VIA VT8237R/VT8237R Plus Chipset wich Supports dual channel
native SATA controller up to 1.5Gb/s with RAID 0 or RAID 1. I am running
"fake"raid 1 at the moment.
waiting longer or setting longer boot delay doesn't wo
In Karmic my problem went (almost) away. My dvd-rom works flawlessly
(but I have to do more tests). System boots with every hard disk
configuration. The only remaining problem: while booting there is a lot
of text about "searching" for sda1, sda2 etc.under the white Ubuntu logo
for a few seconds. B
I upgraded the system that caused me to file this bug to Karmic today and
it appears similar to Jaunty. It takes forever to boot, but gets there
eventually without the root delay work around.
[1.088696] sda: sda1 sda2 < sda5 >
[1.131086] sd 2:0:0:0: [sda] Attached SCSI disk
[5.944009
I upgraded the affected box today and it seems similar to Jaunty. It
does boot without the rootdelay workaround that I had to use in
Intrepid, but is still very slow
[1.088696] sda: sda1 sda2 < sda5 >
[1.131086] sd 2:0:0:0: [sda] Attached SCSI disk
[5.944009] ata4: link is slow to re
@Scott K. can you please test per comment #163 and let us know if that
patch fixed the issue.
Thanks
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
There is a commit related to link init failures in the final karmic
kernel which may be relevant. So it may be worth testing with
2.6.31-14.46:
commit e827d71dd6d39b3e28a519cb0bace9634d42aa7d
Author: Tejun Heo
Date: Tue Oct 6 17:08:40 2009 +0900
libata: fix incorrect link online che
I upgraded to Karmic last night (about 16 hours ago) and it wouldn't boot.
Haven't tried the delay, and can't access the machine now (because it wouldn't
boot, of course).
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification bec
@Morgan Jones -- the dmesg buffer size was upped by default in the
latest karmic kernels, you can also dynamically change it using the
log_buf_len=nnn (this needs to be a power of 2) kernel parameter. Would
you also be able to test with the 2.6.31 based kernels in Karmic and let
us know how this b
** Changed in: linux (Ubuntu Karmic)
Milestone: jaunty-updates => None
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Full dmesg output for kernel 2.6.31-rc4
Still get the SRST failed message... but it only probes interfaces for
~60 seconds which is better.
** Attachment added: "2.6.31-rc4 dmesg output"
http://launchpadlibrarian.net/29780662/dmesg
--
Fails to find boot device in Intel D945Gnt
https://bugs.
@Andy - Do you know of a boot param that increases dmesg buffersize? I
can't get the full log from 2.6.31-rc4 as it is truncated.
Thanks! Morgan
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubu
Ok, I will do so when I get around to it. I am out of town until
Saturday and will not be at the computer involved until Monday. I am
running 2.6.30.3 mainline right now and this issue has not been fixed.
But I will try.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bug
This could be fixed in 2.6.31-rc4.
>From the changelog:
libata: fix follow-up SRST failure path
ata_eh_reset() was missing error return handling after follow-up SRST allowing
EH to continue the normal probing path after reset failure. This was discovered
while testing new WD 2TB drives whi
@Morgan -- would you be able to test the latest 2.6.31-rc4 mainline
kernel (or later if its appeared) and post me a dmesg from that kernel.
Thanks!
https://wiki.ubuntu.com/KernelTeam/MainlineBuilds
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You recei
@Andy- The tests I did were mainly with the mainline kernel. I got the same
issues I had with the (-generic) kernels.
Two more updates here:
2.6.29.4 - SRST failed
2.6.30 - SRST failed
Still not fixed in 2.6.30, obviously. I think (in 2.6.29.4) my kernel sees my
drive as an sda/sdb device. It doe
@Morgan -- did you manage to figure out which configuration you were
using for your various kernels. It might be worth do the same test
with the kernels from the Mainline Kernel archive as we build those with
the same options as we build the Ubuntu kernels.
@Jake -- thats rather wierd I would no
i still had the same issue after upgrade to karmic kernel of 2.6.30-10-generic.
So i think the bug exist in karmic.
it does boot find when i exit the initramfs , and rootdelay=30 didnt work for
me. will try to add another 30 to the rootdelay number.
** Attachment added: "lspci.txt"
http://
I don't know if this helps or not, but I'll throw it in anyway. I had
the same issue with 2.6.28-12-generic on the same Intel MB. When I
tried to reinstall the kernel from the CLI, APT gave me a message about
DPKG needing to be reconfigured. I followed the command it gave me
(sudo dpkg --configu
I'm using 2.6.28-11-generic on Jaunty, and the bug is still present.
(It first appeared for me with one of the Intrepid kernels; never
happened with earlier releases.)
Of note, I do not have any drives on the motherboard's SATA bus. My
boot device is a 3ware hardware RAID card whose driver is par
you will find you have /dev/sd* or /dev/hd* for these kernels. and the
same strings should be reported in the dmesg.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
2.6.29.3 still gives those SRST failed messages.
In summary, here's what each kernel version does for me.
2.6.24-21-generic: Boots right up
2.6.27.10: SRST failed
2.6.28-rc6: SRST failed
2.6.28: SRST failed
2.6.28-11-generic: SRST failed, but boots up after 60 seconds
2.6.28.4: SRST failed
2.6.28
Hmm, I don't think I configured those kernels differently. Let me check
to see if the new 2.6.29.3 works.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Scott -- actually could you also attach a current dmesg output from
your working but very slow boot for me.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
@Scott -- possibly yes. I was basing that on both your feedback and
that of @Morgan who seems to note things improving over time. However
looking at his feedback I am not sure his kernel is configured
correctly. @Richard just throws more confusing in as he is now working.
@Morgan -- I notice th
Fixed for me in version 2.6.28-12 of the kernel. Relative to the old
kernels in 8.04 the boot time is now much faster as well.
Thanks for fixing this!
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member
I think fixed is too strong a term as it still takes a very long time for
the device to turn up. I think the consequences of this bug are reduced
(slow boot instead of failed boot), but the underlying defect is still
present.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpa
I still have this issue in Jaunty (2.6.28-11) x86_64 when I place my
sata dvd drive on the same channels as my sata (not sata2) hard drives..
So I dont know why this is being marked as fixed..
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this b
Based on Scott's feedback here on Jaunty I am going to close the Jaunty
task fixed, as the device is found there without need for modification
of the boot configuration. I suspect Karmic is also fixed but is as yet
untested.
** Changed in: linux (Ubuntu Jaunty)
Status: Confirmed => Fix Rel
Just to add to the list of hardware experiencing this problem:
3ware 8006-2LP RAID controller
Intel P35 chipset
I haven't tried the newest kernel; I'm still using the standard Intrepid
repositories.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You receive
** Also affects: busybox (Ubuntu Karmic)
Importance: High
Status: Invalid
** Also affects: initramfs-tools (Ubuntu Karmic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Karmic)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: Confir
It's apparent that something was fixed between 2.6.27 and 2.6.28 and
fixed even more between 2.6.28 and 2.6.29.1.
** Attachment added: "Dmesg output from 2.6.29.1 (my current working kernel)"
http://launchpadlibrarian.net/25911392/dmesg_2.6.29.1.txt
--
Fails to find boot device in Intel D945G
** Attachment added: "Dmesg output from 2.6.28"
http://launchpadlibrarian.net/25911367/dmesg_2.6.28.txt
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Oddly enough, I had this problem constantly when I was running the
2.6.27 kernel and above (getting the SRST failed. I decided to switch
from Ubuntu's kernel to the mainline Linux kernel for now (and am
running 2.6.29.1 at the time) and it seems to have partially fixed the
problem. The only weird t
I just upgraded the machine that cause me to file this bug to Jaunty and
it now boots without rootdelay. I still get serveral of the ata4: SRST
failed (errorno=-16) errors in the boot process. They come at ~ 22, 32,
67, and I think 72 and 74. So it looks like the root cause is still
there, but 2
I think this was meant to go to confirmed.
** Changed in: linux (Ubuntu Jaunty)
Status: Incomplete => Confirmed
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I have found that adding rootdelay=90 resolves an issue with dropping to a
intramfs busybox shell when booting with
a usb-stick made by usb-creator in jaunty 9.04 , that bug is
https://bugs.launchpad.net/bugs/276822
Linux wirechief-laptop 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC
2
Ok, my symptoms resolved: FWIW I found out that 'lvchange -a y' was
taking ages on my volume group that contained a snaphot of 18Gb that was
50% full. Ages measuring in minutes, it would prevent successfull boot.
I found out by doing repeated
/sbin/lvm vgchange -a n
/sbin/lvm vgchange -a y
/sbin/
What is incomplete about this bug?
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Thanks for the hint. I found bug #332270... it might be more akin to
what I'm describing. Still might be fruitful to cross examine that one:
udev's change to inotify is known to cause problems/slowness in booting
by constant firings of change events. This might happen without lvm? I
don't know abou
since this bug happened on Intrepid and non-lvm systems, I suspect you are
having a different problem and should file a new bug.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which
As you can see the boot time is pretty pathetic now. Up from 40s (before
upgrade) to 2"14s (resuming as quickly as possible)
** Attachment added: "jaunty-after-quickmanualresume"
http://launchpadlibrarian.net/25224512/intrepid-jaunty-20090410-2.png
--
Fails to find boot device in Intel D945Gn
** Attachment added: "jaunty-after-slowmanualresume"
http://launchpadlibrarian.net/25224417/intrepid-jaunty-20090410-1.png
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Has a cause been identified? I can certainly help with that part! Here's
some more I dugg up (attached)
Bootcharts from my intrepid install directly before upgrading
And from the jaunty directly after upgrading (luckily, bootchart was alwyas
installed on my system)
Lvm seems to be taking an awf
This is currently a priority item for both the kernel team and the release
team. Since no solution has been found yet, the odds of this getting fixed
before release are low. More attention won't help.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You rece
Added findings:
(1) i was overly optimistic when I said that exiting the initramfs shell
immediately helped. It often requires a wait of 30-60 seconds to succeed.
(2) an added observation that could shed some light: the hard-disk activity led
lights up continously since 'booting' the grub select
No. This issue is in Intrepid too and no lvm involved.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
PS. My exact method of distupgrading was actually 'update-manager -d' in
case anyone was wondering about the reboot-method thingie I mentioned
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Have this problem since my Jaunty upgrade. Upgraded from existing
intrepid install. Config identical to hostname config. In fact I can
still boot into a snapshot of the pre-upgrade intrepid (have backups, at
all times). Immediately exiting the busybox shell works all the time.
Did anyone investiga
As we don't appear to have a handle on this bug's origin, I'm
milestoning it for jaunty-updates. It remains a candidate for
intrepid/jaunty SRU if a fix becomes available.
** Changed in: linux (Ubuntu Jaunty)
Milestone: None => jaunty-updates
--
Fails to find boot device in Intel D945Gnt
ht
I tried the kernel provided by Andy and the problem remains. I used the
amd64 version of the kernel.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Ok, I have built some test kernels with the patch suggested by TJ.
Perhaps those of you affected by this issue could try the kernels and
report back here. Kernels are at the URL below:
http://people.ubuntu.com/~apw/lp290153-jaunty/
--
Fails to find boot device in Intel D945Gnt
https://bugs.
** Also affects: busybox (Ubuntu Jaunty)
Importance: High
Status: Invalid
** Also affects: initramfs-tools (Ubuntu Jaunty)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Jaunty)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: Incomp
@FernanAguero -- it seems that this fix no longer works for the reporter
either so I would ignore it for now.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
> @Richard -- it would be good to confirm the nearest previous version you
> tried where it does not work. To limit the search for the trigger.
>
> @All -- if those of you who are affected could try the Jaunty 2.6.28-11
> kernel and report back if that also fixes the issue for you.
Andy,
can y
Andy, is this closely coupled to libata issues or could it be yet
another by-product of the RCU idle issue I proposed a patch for last
week (Friday, 14:52 - "rcu: Teach RCU that idle task is not quiscent
state at boot") ?
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bu
OK I retried this with the 2.6.28-11-generic and unfortunately it is not
working so the fix I reported
does not work. It is weird that it should boot OK one time and not the next.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notifica
@Richard -- it would be good to confirm the nearest previous version you
tried where it does not work. To limit the search for the trigger.
@All -- if those of you who are affected could try the Jaunty 2.6.28-11
kernel and report back if that also fixes the issue for you.
** Changed in: linux (U
Some good news at last!
With the latest Jaunty kernel (2.6.28-11-generic) this problem has
disappeared. I have tried a large number of different kernels and this
is the only one since intrepid's first kernel that does not have the
problem. Let me know if you need any more information from my syste
We are also affected by this bug. We have had to use rootdelay workaround with
a 420 delay. We use use a Dell PV-124-T LTO-2 autochanger which takes ages to
load and because devices appears after the autochanger init we have to wait for
long time.
I'm a bit confused with proposed kernel fix, cau
I tested this on the following kernels
2.6.28-9
2.6.29-rc7
The problem remains the same for both.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Now that we have mainline kernel builds could those who are affected by
this try the latest mainline kernel and see if that works correctly.
This may help us figure out what is different in the jaunty kernels. I
would like to get a comparison with both the latest mainline kernel:
v2.6.29-rc7
After last kernel update on Intrepid the bug is back. :|
I have to wait about a minute and then write exit and hit enter.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Tags added: regression-potential
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
** Tags added: regression-release
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
i'm not sure what bug you're workinbg around, but I'm pretty sure it isn't
this one.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Some what of a workaround.
For those of you who are able to boot using a USB flash drive, you can
use UNetbootin which will make a bootable flash drive for you. So, when
you restart your computer, boot using the flash drive and install from
there. I had no issues with this method and it was a lot
OK, have calmed down a bit since yesterday, when I had multiple X crashes with
the vesa driver.
The connection with nvidia drivers was that the only way I can boot this
machine atm. is using a way old kernel image I only still have out of pure
coincidence and because I've been upgrading this mac
This bug has nothing to do with Nvidia drivers.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
Back on topic - I just got Ubuntu 8.10 to boot on the liveCD - I had to
add the option all_generic_ide to the kernel line . This of course
allowed me to boot the liveCD but I don't see this as being an option
for a regular install since its going to really degrade performance..
But perhaps this ca
Nvidia Drivers? Are you talking about a display issue? This bug report
is for issues with Intrepid and also Jaunty not being able to boot to or
with a sata dvd-rom drive connected.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notifica
"I'm really excited about some of the things in Jaunty..."
I for my part am really excited of not being able to run nvidia drivers
on this box for four months. I'm quite loth to use nvidia packaged
drivers. Anybody affected here, knows whether machines affected by this
work with any other Debian-b
Update to my previous post - I have tested Alpha4 Jaunty with 32 and
64bit liveCD's - and no luck with either one. I'm really excited about
some of the things in Jaunty (ext4, etc) - so hopefully this can be
resolved before its out of beta. I'm looking forward to even faster
boot up times - so I'
I reported that the problem was gone for me but I discovered recently
that it's not entirely gone. I don't have busybox anymore as long as I
don't attach additional SATA drive. When I attach the SATA drive (third
HDD in my system) then it's busybox again and sometimes writing exit and
hitting enter
I can also confirm this - had report this issue here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/291791
But looks like this is also where I belong. I have tested Intrepid
64bit w/ Kernel 2.6.27-11 and the liveCD I made with that would not
boot, the same is with any standard intrepid Liv
I can confirm that the latest kernel just in intrepid-updates does not fix
this problem.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I had this issue a few months ago on 8.04, but was about to upgrade to
8.10 anyway, so did that. Haven't had a problem since until today.
Interestingly, when I removed 'splash quiet' from the kernel line, the
boot was normal. I'm thinking maybe s short rootdelay will do the trick
for me, will try
Since the links to the jaunty kernels above are dead, I dl'ed the kernel
2.6.28-5 from packages.ubuntu.com. I installed the following packages:
linux-backports-modules-2.6.28-5-generic_2.6.28-5.2_i386.deb
linux-headers-2.6.28-5_2.6.28-5.15_all.deb
linux-headers-2.6.28-5-generic_2.6.28-5.15_i386.de
Additional information regarding my report of 2008-12-21 - same system,
except install to an AT drive continues to have the problem; however,
the SCSI controller was still enabled. With the SCSI controller
disabled in the BIOS, clean boot off the AT drive. With reference to
the original report, t
On Thu, 15 Jan 2009 17:21:44 - Andy Whitcroft wrote:
>There do not seem to be any further updates to the NV driver
>specificially in mainline at this time.
I'm a bit confused how this relates to the bug. The original report (mine)
is on an all Intel box.
--
Fails to find boot device in I
There do not seem to be any further updates to the NV driver
specificially in mainline at this time. So our next step is to confirm
whether the problem is seen in the Jaunty kernels. If those who see
this problem could either test the Jaunty Alpha-3 live cd or the Jaunty
2.6.28-4-10 kernels from
** Tags added: qa-jaunty-kernel
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
I'm exhausted. I wanted to try out Ubuntu after going back to Windows a
few months ago. I DL and burned Ubuntu Ultimate 2.0. I am aware of
problems with bad burns (been there), so I burned the disk at 2X.
Popped the DVD in yesterday and came up with this error also. I have
spent the last 24 hours,
Forget my previous comment: described behavior is not repeatable.
Sometimes system boots, some others doesn't, with or without rootdelay.
Sorry for the noise.
--
Fails to find boot device in Intel D945Gnt
https://bugs.launchpad.net/bugs/290153
You received this bug notification because you are a
Hello.
I experienced the same problem with an ASUS A6Rp, but I can add some (hoping)
useful infos: the system is unable to boot only after the sequence: suspend ->
failed resume -> forced poweroff (I did not tried with hibernate).
I faced with the problem while testing suspend/resume for finding
rootdelay=90 has remedied my "Gave up waiting for root device" error.
This is on a different motherboard than D45gnt and with a SCSI interface
- not SATA.
The 8.10 server install is on a Rackable Systems Phantom4 4.0 system
that uses an Intel SE7501WV2 motherboard with dual Zeons and 4 SCSI
drives
1 - 100 of 195 matches
Mail list logo
