chascon
July 7th, 2005, 04:56 PM
I thought I'd post about this problem I'm having. I've already posted at bugzilla, but in the interest of transparency here it is.
Ubuntu boots fine from the CD and the install appears normal until it reports
that it has been unable to install the multiseat package. No further details
are given and it looks as if it would be poosible to continue installing other
packages.
Target machine is a twin CPU 200MHz Pentium Pro NCR box with 256 meg of memory,
installing to a 4 gig SCSI boot disk (single partition).
Is there somewhere I can check for more details of the error ?
I've reverted the machine to Windows 2000 which boots, loads and seems to run
OK. Machine is currently grinding out seti@home on one CPU and
www.ud.com/cancer on the other without any indication of underlying hardware issues.
Any thoughts on where to start looking for the problem appreciated !
Cheers, J/.
------- Additional Comment #1 From Matt Zimmerman 2005-06-28 01:00 UTC -------
When you are asked to choose your language, select "Go back" and run a CD
integrity check from the menu
------- Additional Comment #2 From mcepeda 2005-07-07 20:53 UTC -------
I'm having the same problem on a 400 mhz iMac DV and hoary ubuntu and kubuntu install CDs, regardless of
server install or default, I tried three cds that burned propperly with xcdroast (I know how to do), and
their md5s checked out.
Since it's third CD and all the md5s check out, I highly doubt it is an issue with data corruption on the
CDs.
by the way, these settings:
linux multiseat-udeb/disable_multiseat=true
at the first prompt didn't work either. It gives: cd:2,linux: Unkown or corrupt filesytem
Update:
I tried a fourth atttempt using the burner called firestarter, something I've burned warty with
succesfully, and I get the same failure.
Checking CD-ROM integrety says,
"Integrety test successful. The CD-ROM integrety test was successful. The CD-ROM is valid".
Setting, 'linux multiseat-udeb/disable_multiseat=true' does not reap different results as before with
earlier CDs.
PS-The burned CDs have been both CD-W and CDRWs. So this seems to not be a physical problem but a software
one.
Ubuntu boots fine from the CD and the install appears normal until it reports
that it has been unable to install the multiseat package. No further details
are given and it looks as if it would be poosible to continue installing other
packages.
Target machine is a twin CPU 200MHz Pentium Pro NCR box with 256 meg of memory,
installing to a 4 gig SCSI boot disk (single partition).
Is there somewhere I can check for more details of the error ?
I've reverted the machine to Windows 2000 which boots, loads and seems to run
OK. Machine is currently grinding out seti@home on one CPU and
www.ud.com/cancer on the other without any indication of underlying hardware issues.
Any thoughts on where to start looking for the problem appreciated !
Cheers, J/.
------- Additional Comment #1 From Matt Zimmerman 2005-06-28 01:00 UTC -------
When you are asked to choose your language, select "Go back" and run a CD
integrity check from the menu
------- Additional Comment #2 From mcepeda 2005-07-07 20:53 UTC -------
I'm having the same problem on a 400 mhz iMac DV and hoary ubuntu and kubuntu install CDs, regardless of
server install or default, I tried three cds that burned propperly with xcdroast (I know how to do), and
their md5s checked out.
Since it's third CD and all the md5s check out, I highly doubt it is an issue with data corruption on the
CDs.
by the way, these settings:
linux multiseat-udeb/disable_multiseat=true
at the first prompt didn't work either. It gives: cd:2,linux: Unkown or corrupt filesytem
Update:
I tried a fourth atttempt using the burner called firestarter, something I've burned warty with
succesfully, and I get the same failure.
Checking CD-ROM integrety says,
"Integrety test successful. The CD-ROM integrety test was successful. The CD-ROM is valid".
Setting, 'linux multiseat-udeb/disable_multiseat=true' does not reap different results as before with
earlier CDs.
PS-The burned CDs have been both CD-W and CDRWs. So this seems to not be a physical problem but a software
one.