I don't see this to be fixed in the 9.10 iso I downloaded and installed
this week. I have tried to install it from a CD and USB stick, but both
fail to boot after the initial restart at the completion of setup.
The hardware I'm installing on doesn't have an onboard CD so it's
impossible for the b
I don't think this will be fixed ..
The new LTS will most likely use the "search-for-disk-with-uuid-x and
set that as ROOT if found" mechanism from the new grub releases. Easiest
way for now is to first live edit the config at first regular boot after
install (set root(x,y) to whatever you need it
I believe that this situation still exists with 8.04 (which as LTS I'm
trying to install). I don't have a CD drive, so i'm installing from a
USB key. The BIOS on the Sun x2200 sees the usb key as a type of hard
disk. During install it is registered as /dev/sda, with the (single)
SATA disk as /de
Once you have an incorrectly-generated /boot/grub/menu.lst, 'update-
grub' will still take defaults from that.
Then, to get rid of this problem, simply remove (or just move)
/boot/grub/menu.lst and have 'update-grub' generate an entirely new one.
--
grub guessed BIOS disk order incorrectly
https
This is fixed for new Ubuntu 8.10 installs using the latest daily-live
CDs:
http://cdimage.ubuntu.com/daily-live
or for Kubuntu:
http://cdimage.ubuntu.com/kubuntu/daily-live
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification beca
I have a similar problem, in both 8.04 and 8.10b
My menu.lst always sets the root as hd(2,x) but it should be hd(0,x)
Please let me know if anyone needs any more info from me, I will be glad
to help.
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received t
I am experiencing randomizing. I am using U8.04 64bit and all updates
had been applied.
Yesterday, 2008-09-19, my devices were:
[EMAIL PROTECTED]:/boot/grub# fdisk -l|grep Disk
Disk /dev/sda: 120.0 GB, 120034123776 bytes <-IDE0 100% Windows
Disk identifier: 0xc8e067c5
Disk /dev/sdb: 500.
I am not sure whether this bug is supposed to have been fixed or not,
but it is still present in the main release of 8.04 and I can document
pretty much exactly what happens.
I have an Asus P4C800-E motherboard with 2 identical 160 GB Samsung
disks (D1 & D2) attached to the main SATA controller, a
Here's a workaround at least for my case without any severe modification of the
system.
1: Make sure the bootloader is installed on the boot HD whether it works right
or not. Manually install if you have to with find root and setup in grub off
the live cd (I'm not putting those instructions he
Thanks to some of your help I think I can fix the problem, but I have
used a couple of versions of Fedora and they simply give you an option
to change the drive order during installation.
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notifi
Running Gigabyte GA-81EXP with 2 channels of onboard IDE and channels
of Promise IDE has this same problem. Up until last night I was running
7.10 and the controllers booted up randomly. If they came up backwards I
could just reboot a couple of times until everything mounted correctly.
Upgraded to
Mike, the fix you mentioned is specific to Wubi, since Wubi uses a
slightly differerent bootloader/bootloader configuration (grub4dos).
That fix will soon be available, see:
https://bugs.launchpad.net/wubi/+bug/217348
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/849
Hello, is this really fixed? I came here from
https://wiki.ubuntu.com/WubiGuide and had this error today installing
Ubuntu 8.04 with Wubi. All went well until the second restart (the one
after installation from within Ubuntu), and I got Error 15 on all
entries including Windows, which was quite sca
Having spoke to Matt Domsch, EDD kernel support's author, it seems it's
the reading of the MBR that's typically causes booting problems when the
drive being read doesn't exist. So there's no point doing just the MBRs
and ignoring the advanced BIOS calls in the hope that it could be
enabled by defa
Having spoke to Matt Domsch, EDD kernel support's author, it seems it's
the reading of the MBR that's typically causes booting problems when the
drive being read doesn't exist. So there's no point doing just the MBRs
and ignoring the advanced BIOS calls in the hope that it could be
enabled by defa
Colin, one has to boot with edd=on for this to be activated, as you say,
and it's presumably defaults to off for good reason, "This option is
experimental and is known to fail to boot on some obscure
configurations." says drivers/firmware/Kconfig. However, I'd guess that
grub only makes use of the
Colin:
That's a pity. If you can only use it on a case by case basis (because some
BIOSes are still getting it wrong) any automatic activation will require the
building of a whitelist which sounds extremely painful...
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8
Sitsofe: unfortunately I don't think it's even as simple as a date-style
cutoff. My understanding is that it still depends on your manufacturer
to a large extent. Dell systems generally seem to get it right as they
created the specification in the first place, and some other systems
will support it
gfxboot-theme-ubuntu (0.5.14) hardy; urgency=low
* Update translations from Launchpad.
* Add edd=on option to the "Other Options" menu.
-- Colin Watson <[EMAIL PROTECTED]> Thu, 03 Apr 2008 10:23:24 +0100
** Also affects: gfxboot-theme-ubuntu (Ubuntu)
Importance: Undecided
Status:
This bug was fixed in the package grub - 0.97-29ubuntu20
---
grub (0.97-29ubuntu20) hardy; urgency=low
* debian/patches/edd-device-map.diff: Use EDD information if available to
help generate a more correct device.map; boot with edd=on to activate
this (LP: #8497).
* Fix a
** Tags added: qa-hardy-platform
** Changed in: grub (Ubuntu)
Importance: Medium => High
Status: In Progress => Fix Committed
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I now have a grub patch that I think shuffles the devices around
appropriately provided that you boot with edd=on, provided that EDD
works on your hardware, and provided that the MBR signatures exposed by
EDD are distinct - pretty much the same conditions as in SuSE. We can't
make this the default,
** Tags removed: qa-hardy-platform
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
** Tags added: wubi
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
Over in SUSE SLES/SLED land EDD is compiled in but not used by default -
http://www.novell.com/documentation/sled10/readme/release_notes_sp1.html#b554l8b
. My thinking is that if newer devices are getting EDD right perhaps
it's going to be time for another BIOS year cutoff and those devices
past th
** Tags added: qa-hardy-platform
** Tags removed: qa-hardy-list
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Changed in: grub
Status: New => Fix Released
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Changed in: grub
Status: Unknown => New
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
** Bug watch added: Debian Bug tracker #460177
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460177
** Also affects: grub via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460177
Importance: Unknown
Status: Unknown
--
grub guessed BIOS disk order incorrectly
https://bugs.la
I'm having the same problem:
Configuration: 2 disks (IDE and SATA). Bios sets the IDE disk as the
first disk (default option) and I've changed this to the SATA one. I
guess that's why grub sets the hd0 disk as the disk it will boot from.
This is quite frustrating and it involves a couple of trial
Sounds like this might be related to my problem at
http://ubuntuforums.org/showthread.php?t=668639. Not only did GRUB
install itself to hd2 (needs to be changed to hd0 to boot) but the
kernel typically enumerates the SATA drives in a completely different
order every time. If fstab wasn't using UUID
Hum, I think I have read too fast.
Seems like bug #15213 (that was 8899 in bugzilla time) was indeed fixed by
deactivating CONFIG_EDD.
So, seems the problem would still be that the CONFIG_EDD patch is still buggy,
causing a big delay at boot.
--
grub guessed BIOS disk order incorrectly
https://
I am recalling developers here that Michael Vogt has given a hint on how to fix
this in:
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/8497/comments/11 by using
kernel option CONFIG_EDD that was deactivated because of a bug that is now
fixed: http://bugzilla.ubuntu.com/show_bug.cgi?id=8899
A number of comments posted here are unrelated to this bug report. If
you get to a grub menu, then this bug report is not related to your
problem. Having the kernel not be able to find the root filesystem
because it changed name and you weren't using the UUID is a separate
issue. Devices changin
** Tags added: qa-hardy-list
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
Billnvd, your old kernel 2.6.12-10-386 was a Breezy kernel, so I guess
the upgrade to 6.06 was not properly done. File a new bug if you still
think there's a bug.
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a
Billnvd:
If the computer is getting to a shell then GRUB should be ok and it is the OS
that is having problems. From the sounds of it you could try using UUIDs
instead of relying on device nodes to mount drives. This has been the default
in Ubuntu for a while now (though I'm not sure if it was
My experience with this issue is a little different.
The system is a file server running 6.06 LTS
There are five HD's
Boot and OS disk is attached to the MB Pri Master.
This disk has always been HDA
Partitions are:
hda1 = boot
hda5 = root
hda6 = home
There are four MDRaid disks on a SIL controll
Hi Colin, I'm taking the imposition of assigning this to you because
many of the duplicates were and it seems to need someone to move it
forward. I thought you'd know who that should be. Also,
https://wiki.ubuntu.com/Bugs/Importance says an Importance of High is
for a bug that "Has a severe impac
This is STILL an issue in GUTSY and can create an UN-BOOTABLE SYSTEM
that's very difficult to debug.
Ubuntu (or grub) simply doesn't have the same idea of disk ordering as
the BIOS.
In particular this is what just happened to me with a new Gutsy install.
After installation and reboot the compute
Robert, the entries in menu.lst inside the
### BEGIN AUTOMAGIC KERNELS LIST
section that begin with a single comment # are actually used by the
updater as settings.
Genuine comments use two ## symbols, just to confuse you.
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/
TJ, given that it was commented out, will this stay persistent between
kernel updates?
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailin
Robert, the solution to your issue is to edit /boot/grub/menu.lst and
set groot correctly. This is what is used when the kernel is updated.
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,4)
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You recei
My work around for this which I have been doing for some time is to just
edit my Grub boot line, boot into Ubuntu then alter my menu.lst back to
how it should be. The culprit for me is always the following line for
each kernel listed:
root(hd0,1)
For whatever reason after a kernel upd
Sometimes it helps to engage brain before putting mouth into gear!
In my edd module-build instructions above I forgot two things:
1. libx86 is for user-space applications; no involvement in the kernel (was
thinking about vbetool at the time I typed that!)
2. The built module can't be modprobe-d
... or I could boot from a Fedora or SUSE live CD. ;-)
Will do that tomorrow. Cheers.
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs maili
If you're feeling particularly adventurous you could build the kernel
EDD module.
1. Install the kernel-source from GIT
(https://wiki.ubuntu.com/KernelGitGuide) or use
$ sudo apt-get install linux-source
$ sudo tar -xjf linux-source-2.6.22.tar.bz2
$ cd /usr/src/linux-source-2.6.22
2. Edit debian
A follow-up to my observations of the SCSI address allocation. It looks
as if this is determined in
drivers/ata/libata-core.c::ata_host_register()
where, in part, you find "/* print per-port info to dmesg */"
and in turn calls
drivers/ata/libata-scsi.c::ata_scsi_scan_host()
It appears that ea
These two comments suggest EDD is the right way to construct device.map:
http://kerneltrap.org/node/6408
"These days, you just cannot enumerate controllers in any meaningful
manner.
I don't think you ever really could, but at least with static hardware,
any random enumerat
Yeah, the Windows ones are supposed to be (channel, target, lun) or
(controller, target, lun).
I would have thought logically they would all have the same controller,
but maybe SATA is handled differently.
(0,0,0), (0,1,0), and (1,0,0) would map well to IDE primary master, IDE
primary slave, IDE
Mikel, thanks for those reports, they help clarify your circumstances
tremendously. This is just off the top of my head without any real
investigation, but the difference in the SCSI addresses between Windows
and Linux makes me wonder about how the SCSI addressing is being
determined.
For Windows,
Even more info than you wanted, but dmesg suggests it's using AHCI mode,
which is interesting.
[ 26.020215] ahci :00:12.0: version 2.2
[ 26.020433] ahci :00:12.0: controller can't do 64bit DMA, forcing 32bit
[ 26.072845] ide: Assuming 33MHz system bus speed for PIO modes; override
w
I think /proc/scsi/scsi is the simplest way to find out Linux has the
order different:
/proc/scsi$ cat scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: ATA Model: ST380817AS Rev: 3.42
Type: Direct-AccessANSI SCSI revision: 05
Host: scsi1
Corrections:
Windows:
SCSI 0,0,0 Seagate ST380817AS 80 GB HD
SCSI 0,1,0 Seagate ST380813AS 80 GB HD <---
SCSI 1,0,0 Seagate ST3250820AS 250 GB HD
And to make it clear, I'm not actually using any kind of RAID, just that
the mobo is capable of it.
The relevant part of lspci -vv shows this:
00:12
Ubuntu Linux 7.10 RC amd64
ASUS M2A-VM mainboard
Configured in PATA emulation mode so that Windows Vista works. (I'm not
sure what they called it on the BIOS settings, but it's the opposite of
AHCI mode. In Windows they show up under a generic ATA controller.)
Mainboard:
SATA4 (empty)
SATA2 Se
Will all those experiencing this bug with Gutsy give us detailed
information as to the physical configuration of the motherboard disk
interfaces and disk drives so we can understand the precise
circumstances that cause this?
Right now we have a combination of comments, some of which indicate an
is
https://wiki.ubuntu.com/Bugs/Importance says an Importance of High is
for a bug that "Has a severe impact on a small portion of Ubuntu users".
This bug stops systems booting for a small, but growing, number of
users. It also says "Makes a default Ubuntu installation generally
unusable for some use
This is a SHOWSTOPPER.
The priority HAS to be at the highest.
This thing has racked up 23 duplicates already, it is a major problem.
And the conditions for it aren't special, it's basically any new computer.
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You rece
I think that this is serious. It still happens with Gutsy on some
(desktop) installs with a raid system that hd1 is used instead of hd0
which makes system unbootable for newbies and it even happened between a
Kernel upgrade during Gutsy Alpha.
--
grub guessed BIOS disk order incorrectly
https://b
I too fear that this is going to bite more people as their hardware
moves over time away from PATA. Rendering a system unbootable is pretty
severe and something that many users can't recover from un-aided. And
how do they get that aid if the machine is their main Internet access?
Can this bug's i
I got bitten by this again in the Gutsy RC on my new PC.
I posted my experiences here
http://ubuntuforums.org/showthread.php?p=3518911#post3518911.
In brief:
My BIOS sees my drives as:
HDD1 - 80 GB - Windows
HDD2 - 80 GB - Linux
HDD3 - 250 GB - Media
Linux sees them as:
/dev/sda - 80 GB - Windo
I am wondering if my bug #107249 is also being caused by this. In my
case, kernel updates have sometimes failed and have resulted in the
system presently being unbootable.
My machine, an Asus A8V, reports 4 sata drives, two on each controller.
Three of these drives are being used by linux: a boot
Hi,
Just to add some more information if it was not available already. My
lone remaining PATA drive died a few weeks back, and I did a clean
install of Feisty (7.04) today as follows:
Cold boot, press F8 to select boot menu popup (since default boot order is hard
drive first).
Boot off the insta
The bug is affecting IBM R52 laptop as well. I have installed i386
Ubuntu 7.04 and grub on external USB drive using alternate CD. I must
mention that I chose not to follow installer suggestion to install grub
to my internal HDD and installed it on my USB HDD instead. I can boot
into grub, but get e
Thanks Val. I understand it can be corrected and worked around, but it
takes a lot of perserverance to get to the point where you find a bug
report like this one and discover the workaround. Every attempt at
installation finishes with the "all went well" message yet reboot fails.
I'm happy to del
In my case the drive that is seen by grub as (hd1) when the system is
running appears as (hd0) to grub during bootup.
As a workaround I opened /boot/grub/menu.lst and changed the 'groot'
line to rea:
# groot=(hd0,0)
Note that the line is supposed to stay commented out. The 'update-grub'
tool act
I'm another person bitten by this. A system with PATA and SATA drives
attempting to install on /dev/sda. The install goes fine and says it's
finished but the BIOS fails to find any boot loader installed and wants
a system disk inserted.
Given the number of individual "me toos" on this bug, and t
The same problem for me. I have an Ide hd and an ata hd. My ata is
/dev/sda and my ide /dev/hdb. Ubuntu create device.map:
(hd0) /dev/hdb
(hd1) /dev/sda
But really my bios hd order is:
(hd0) /dev/sda
(hd1) /dev/hdb
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/
The same problem for me. I have an Ide hd and an ata hd. My ata is
/dev/sda and my ide /dev/hdb. Ubuntu create device.map:
(hd0) /dev/hdb
(hd1) /dev/sda
But really my bios hd order is:
(hd0) /dev/sda
(hd1) /dev/hdb
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/
All partitions really should be referenced by UUID/label in /etc/fstab
(see https://help.ubuntu.com/community/UsingUUID for details) however
this doesn't help for deciding where to put the MBR when using grub-
install (which is what I assume this bug is about)...
--
grub guessed BIOS disk order i
Probably my problem falls under the same category (Ubuntu 7.04, fresh
installation):
I have a pci IDE controller (Sil 0680 ATA) with two hard disks (master/slave)
on it's 1st channel.
I also have four hard disks on the onboard IDE controller (both channels)
So, my "normal" setup is:
Onboard IDE
I would like to add my experience here:
upgraded a running ubuntu 6.x to 7.04. This caused an unbootable system, so I
reinstalled 7.04. I got an error 15 from grub. Problem was that the disk
order was different depending on if I booted with the install CD or without the
CD.
I have 3 disks:
1
I've found a solution to my problem...using entries in /etc/fstab and
/boot/grub/menu.lst that refer to the disk "by-id", such as :
# /dev/sda1
/dev/disk/by-id/scsi-1ATA_Maxtor_7V300F0_V601KP2G-part1 / reiserfs
nouser,defaults,noatime,auto,rw,dev,exec,suid 0 1
If people aflicted by this bug are
There is no way to detect how the bios sees the disks, and the bios may
not see some disks at all. I think the fix for this is to have the
installer notify the user that it is making its best guess as to how the
bios sees the disks, but it may be wrong and if so, they will need to
correct it. The
Can confirm this to , full report here ( I believe i've tested it on
dapper/edgy/feisty )
http://ubuntuforums.org/showthread.php?p=2523834#post2523834
Something similar yet quit different here, ( might be the same problem )
upon attaching my RAID5 array to feisty, all my sata drives (MD) superblo
I'm curious if this bug is the same as what I see on my Abit AN8-32X
system. I have 6 SATA drives (4 on an Nvidia chip, and 2 on Sil 3132
chip), 2 IDE drives (each a master on its own channel), and 2 USB
"drives", which are a SD and CF card reader.
In Dapper, Edgy, and Fiesty, I see the set of 2
** Changed in: grub (Ubuntu)
Assignee: Colin Watson => (unassigned)
--
grub guessed BIOS disk order incorrectly
https://bugs.launchpad.net/bugs/8497
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-
I've hit this problem too in the latest Feisty release (5).
I have three drives which are labelled by Linux and grub in the
following manner:
Drive type Linux grub
SATA-1 /dev/sda ??
SATA-2 /dev/sdb /dev/sda (this is my boot disk)
SATA-2 /dev/sdc ??
The BIOS
Urgh, forgot the bugzilla -> lanchpad renumbering. I meant bug 15213.
--
grub guessed BIOS disk order incorrectly
https://launchpad.net/bugs/8497
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Why not build with CONFIG_EDD=m, and set the default Linux command line
to 'edd=skipmbr'?
That way we don't have the takes-forever disk checks of bug 8899, but we will
still be able to get
the geometry information correctly for GRUB et. al.?
And if someone *really* needs the MBR checks, they can
I can confirm this is present in 6.10 release.
What do I change for Ubuntu to correctly auto-generate my new menu.lst
when I update my kernel?
--
grub guessed BIOS disk order incorrectly
https://launchpad.net/bugs/8497
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Bug #30967 have the same title.
--
grub guessed BIOS disk order incorrectly
https://launchpad.net/bugs/8497
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is still a problem on the Edgy Beta LiveCD/Installer. I entered bug
7 (now listed as duplicate of this one)
--
grub guessed BIOS disk order incorrectly
https://launchpad.net/bugs/8497
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
Werks fine now.
Still an important bug in the installer however.
I shood also note that I never chanjed the boot order in BIOS. It's
simply that GRUB detects them in the rong order.
--
grub guessed BIOS disk order incorrectly
https://launchpad.net/bugs/8497
--
ubuntu-bugs mailing list
ubuntu
I just got bitten bi a similar issue.
I hav:
SATA 1 - /dev/sda
SATA 2 - /dev/sdb
PATA 1 - /dev/hdb
In mi ASUS/nVidia BIOS, the boot configuration is:
CD-ROM
SATA
SCSI
HDD (meening PATA/IDE)
Installing Ubuntu 6.06 from the Live CD resulted in an unbootable
sistem. I just see "GRUB GRUB GRUB" hee
I have the same issue with Ubuntu Dapper 6.06 LTS. My equipment spec is
as below:
ASUS A8N-SLI Deluxe
2GB DDR RAM
4 x Hitachi DeskStar 400GB SATA drives running on nForce4 SATA chipset as
individual drives
AMD Athlon64 3600+ (2.2GHz, running stock speed)
Windows XP is running on the real first d
I had the same issue as the original poster of this bug with one
difference. Instead of my /dev/sda drive being a SATA drive, it is a USB
drive.
I installed Dapper to the USB drive using the Intel x86 alternate
install CD. The computer is a Compaq Presario R3000 [even though it is
an AMD 64, I use
87 matches
Mail list logo
