[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer

2009-01-18 Thread Michael Nagel
closing this bug, i hope that's ok. feel free to reopen and report other issues! ** Changed in: linux (Ubuntu) Status: New => Invalid -- Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer https://bugs.launchpad.net/bugs/159577 You received this bug notifi

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer

2008-11-02 Thread Michael Nagel
** Changed in: linux (Ubuntu) Status: Incomplete => New -- Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer https://bugs.launchpad.net/bugs/159577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer

2008-09-24 Thread Michael Nagel
i am forwarding this to the kernel guys so they can decide how to proceed. ** Changed in: linux (Ubuntu) Sourcepackagename: None => linux -- Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer https://bugs.launchpad.net/bugs/159577 You received this bug notificat

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer

2008-09-24 Thread Russel Winder
I changed the title to show that the issue turned out to be about coping with a faulty DVD writer. I guess the question is whether this problem can be reproduced by someone. If it can then it will be possible to see if the problem is fixed in later kernels, Intrepid, Jaunty, . . . If no-one can

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer

2008-09-24 Thread Russel Winder
** Summary changed: - Neither Gutsy nor Feisty Live CD boot on P4P800 based system + Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer -- Neither Gutsy nor Feisty Live CD boot on P4P800 based system with faulty DVD writer https://bugs.launchpad.net/bugs/159577

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system

2008-09-24 Thread Michael Nagel
then please either change the desription of this bug in order to reflect that it is about coping with faulty hardware or close it as being no longer relevant. best regards, michael -- Neither Gutsy nor Feisty Live CD boot on P4P800 based system https://bugs.launchpad.net/bugs/159577 You received

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system

2008-09-24 Thread Russel Winder
In that we know what the problem was and that removing the faulty device allowed things to work normally then yes the report can be closed. In that the kernel was incapable of dealing sensibly with faulty hardware then no the bug report stands. In that I no longer have equipment that allows me to

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system

2008-09-24 Thread Michael Nagel
can i close this bug report then, as it was probably due to corrupt hardware? ** Changed in: ubuntu Status: New => Incomplete -- Neither Gutsy nor Feisty Live CD boot on P4P800 based system https://bugs.launchpad.net/bugs/159577 You received this bug notification because you are a member

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system

2007-11-06 Thread Russel Winder
The Gutsy Live CD does indeed now boot on this machine now that the part faulty CDROM rewriter has been taken out. So although the CDROM rewriter was functioning correctly as a reader, it failed to communicate in some way with the ata driver, and the ata driver did not do the right thing which is

[Bug 159577] Re: Neither Gutsy nor Feisty Live CD boot on P4P800 based system

2007-11-06 Thread Russel Winder
I had reason to tinker further with this and have ascertained that the problem was associated with a faulty CDROM rewriter. Kernels prior to 2.6.20 and 2.6.20-16.28 we able to boot even though there were issues with the ata driver. All other post 2.6.20 kernels fail to deal with the delay in som