[Bug 1037] wrote:
https://qa.mandrakesoft.com/show_bug.cgi?id=1037Sorry, the part during install is Not losing track of drive, in fact there is a file that got stuck in ISO for CD1 that is just plain wrong. That is why reregistering it after install with the urpmi.update for source cdrom1 works (with that CD in drive, urpmi reads the CD itself to see what is on it and updates its database accordingly, THEN it can find what is on it correctly). There are two files on CD ISOs from Mandrake that do this, hdlist and synthesis. on an ISO set, there can be two of these on CD1, one set for the whole CD set (which the installer reads at the beginning), and another for just the CD1. With betas and last minute changes, ISO contents can change and get moved from CD to CD. That is the how it can happen that a CD1 cannot be found and the drive drivers can be fine. Another way is to acidentally burn so that the wrong volume label gets burned, but in my case I know for a fact that the CD-ROM drive worked and the burning was correct to what was in the ISO and the ISOs came from main mirrors and md5summed right before burning in addition to all the above. And I had the same basic thing happen to me.
------- Additional Comments From [EMAIL PROTECTED] 2003-01-25 02:36 -------
This workaround works - but begs the question, how is it that linux loses track
of its cdrom? I've seen that problem before under 8.1
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
description: I've tried to install 9.1b2 twice tonight on my ibm x21 laptop. Everything goes
fine, except that xwindows won't start after install completes. After the
install, it boots only to console (even when I tell it to default to gnome).
When I say startx, it complains that things are not properly setup. Setup never
queries me about the display.
When I su and try to run drakconf to configure the display, it asks for cd1
again, but when I put it in, it doesn't recognize it.
When I try running xf86config to set things up, it goes through everything ok,
but when I run startx, it gives an execsv error about x.
in my case, after install I did this to get into the KDE GUI:
tried the approach you did, same result;
then did this oddball set of things:
invoked 'gdm' and got an error telling me X was running , after about 30 seconds at 3500+ bogomips (1793 actual MHz P4 box), and did I want to try that using a different display-- I told it yes. And X came up with KDE loading. After playing a bit, I updated cooker to two days ago, and now system comes up sweet as a fresh cucumber from the midwest-- or in Dolphin, as I multiboot cooker and Dolphin. Each is on a separate HD. The only way each can see part of the other is if I manually mount a partition. KDE 3.1 is sweetly implemented for a test release, and this is an early one which is even more exciting.
John.
John.
