** Changed in: debian-installer (Ubuntu)
Status: Incomplete = Confirmed
--
alternate installer broken
https://bugs.launchpad.net/bugs/294365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
As part of supporting multi-CD installs, Debian added some code to
unmount and remount /cdrom at various points during installation. These
happen when installing packages into /target, and the exact behaviour
there is conditional on a lot of things, including things like encrypted
partition setup.
The insert cdrom... message will only occur if I try to create a
filesystem directly on a cryptopartition! If i put LVM between the
crypto and the FS the installer works fine.
However, I don't understand what the cdrom has to do with my crypto
setup?
--
alternate installer broken
and here's lspci
** Attachment added: lspci.txt
http://launchpadlibrarian.net/19562671/lspci.txt
--
alternate installer broken
https://bugs.launchpad.net/bugs/294365
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The Desktop CD doesn't work, probably since my Radeon HD4870 isn't supported
yet. Once it switches to graphics mode, the Screen goes to standby. Should I
open another bug for this problem?
Once fglrx is installed and a appropriate X.org configfile generated with
atitool it does work fine. (I
the message appears after Updating list of available packages...
here's a screenshot of console 4
** Attachment added: DSCN9393.JPG
http://launchpadlibrarian.net/19562647/DSCN9393.JPG
--
alternate installer broken
https://bugs.launchpad.net/bugs/294365
You received this bug notification
I get the same error when installing the AMD64 version, even without any
cryptostuff and only a single ext3 root partition. The last status
before the message was Gathering information for installation
report...
--
alternate installer broken
https://bugs.launchpad.net/bugs/294365
You received
Teej, the processor is irrelevant to this bug. If this were a 32/64-bit
mismatch then it clearly wouldn't have got anywhere near as far as
asking for a different CD; it would have just completely failed to boot.
Also, 64-bit systems can run 32-bit installations perfectly happily and
it is often
Hi znuh,
Thank you for reporting the above problem and helping to improve Ubuntu.
Where exactly is it getting to and then asking for the CD?
What was the result of the 32 bit version, did it work?
Can I ask you to do an md5 checksum on the CD's and to burn them slower,
possible 4-8x, in case of
with tried the 32bit version I meant that the above describes problem
occured with the 32bit version. I haven't tried 64bit.
Will check the md5s soon. Exact point of the installer where it happens
is hard to find since the message won't go away. Thus I can't see the
progress any longer.
--
btw. I also transferred the .iso via netcat to the installing machine and
mounted it via -o loop.
The installer still didn't like it. This probably rules out any bruning errors
in my opinion.
--
alternate installer broken
https://bugs.launchpad.net/bugs/294365
You received this bug
Hi znuh,
Can you provide information about the hardware itself please, Make/Model
processor etc. Do you have a 64 bit processor, otherwise 64 bit linux
will not work anyway. If you are 64 bit, then you really *should* be
using the 64 bit installer anyway. Also do the same problems arise with
the
tried the x86 32bit version
--
alternate installer broken
https://bugs.launchpad.net/bugs/294365
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
13 matches
Mail list logo
