Thanks.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Needs Info => Fix Released
--
edgy knot-1 desktop cd - harddrive is not accessable
https://launchpad.net/bugs/54727
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Okay it appears that knot 3 or I should say atleast kernel 2.6.17-7 seems to
fix the issues.
On 9/21/06, Charles Pirnat <[EMAIL PROTECTED]> wrote:
>
> I'll let you know when beta comes out if that solves it.
>
> On 9/21/06, Ben Collins <[EMAIL PROTECTED]> wrote:
> >
> > Please try knot-3. If that
I'll let you know when beta comes out if that solves it.
On 9/21/06, Ben Collins <[EMAIL PROTECTED]> wrote:
>
> Please try knot-3. If that still fails, try the Edgy Beta when it
> becomes available. Fixes for the controller have been implemented in
> recent kernels.
>
> ** Changed in: linux-source
Please try knot-3. If that still fails, try the Edgy Beta when it
becomes available. Fixes for the controller have been implemented in
recent kernels.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed => Needs Info
--
edgy knot-1 desktop cd - harddrive is not accessable
https:
I can reproduce this error with a Gateway Solo 5300 Notebook. Which has
the same chipset 82371AB. Also this problem persists with Knot 2 Re:
https://launchpad.net/distros/ubuntu/+bug/59038
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Unconfirmed => Confirmed
--
edgy knot-1 deskt
I'm experiencing the same sort of problems with knot2. Its seeing the
controller as scsi for some reason as described above /dev/sda etc...
The system is operable however the cdrom attached to /dev/hdc will not
function due to these issues and there is an ata2 timeout error on boot.
This is on a
The problem was not present in desktop 8/15-16 for [x|k]ubuntu (I tried
all 3). The delay retrieving the partition information is now less than
5 seconds.
I still could not install using the live cd but those were errors
happening later in the install process.
I would mark this bug as closed.
No
I'm at a loss. Is the installer perhaps loading some extra drivers
causing this to happen? I mean if the text installer works, then the
graphic installer has to be doing something different.
--
edgy knot-1 desktop cd - harddrive is not accessable
https://launchpad.net/bugs/54727
--
ubuntu-bugs
This feels like it must be due to the recent libata changes. Ben? If it
turns out to be an installer bug then of course I'll happily accept the
bug back.
** Tags removed: installer ubiquity
** Changed in: ubiquity (Ubuntu)
Sourcepackagename: ubiquity => linux-source-2.6.17
--
edgy knot-1 deskto
Apologies for mistyping the kernel number used in the daily 7/31 ubuntu
desktop cd in my previous comment. It is 2.6.17-5-686.
Both Knot-1 and daily 8/2 Ubuntu alternate installation cd complete
without problems.
I also zeroed the drive, then restored only the ntfs partion using
Acronis TrueImage
** Description changed:
- I'm unsure if this is a problem with kernel 2.6.17-4-386 or with the
- installation software.
+ edit: the problem is in the graphical installation software. kernel
+ works properly.
This is an IBM Thinkpad T22 24678EU. pata harddrive is attached to ide0.
dapper
** Changed in: Ubuntu
Sourcepackagename: None => ubiquity
--
edgy knot-1 desktop cd - harddrive is not accessable
https://launchpad.net/bugs/54727
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
additional information:
This problem seems to only occur with manual partitioning selected. (the
other methods produce an error of not being able to unmount the device
part way through the installation of files)
I tried again with the 7/31 daily build for ubuntu desktop 386. Kernel
is 2.6.25-5-68
13 matches
Mail list logo
