Install trouble on a Toshiba laptop (330CDT)
The install finds my hardware, runs /sbin/loader, pops up a picture of chips, runs for a long time, and hangs. Is there any way I can make the graphic go away so that I can see what's going on? Thanks, Matt
Hi Matt On Saturday 11 February 2006 20:43, Matt Timmermans wrote:
The install finds my hardware, runs /sbin/loader, pops up a picture of chips, runs for a long time, and hangs.
Is there any way I can make the graphic go away so that I can see what's going on?
If you refer to Tux with the flyswat, pressing F2 will make the splash screen disappear and the boot up text will scroll by. Regards, Paul. -- From the Klingon book of C: Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
It was the earlier graphic. It turned out to be some assertion getting thrown in the bit that discovers the drive geometry before partitioning. I managed to muddle through the text mode install, telling it to ignore the assertions as they came up. The remainder of the install took 5 hours, and it didn't set up the operator user properly, but everything else was just fine. It was easy enough to fix. On top of that, my new "quickstep" driver module works beautifully, and can deliver 30000 steps/s to all axes simultaneously. It'll be in your mailbox shortly. All in all, I couldn't be happier with my new EMC-based setup! It's miles better than the *ahem* DOS based program that I was using before (it was the only thing that could run the steppers fast enough OOtB). I took your advice and used xfce, which works just fine, and it wasn't hard to figure out how to add the launcher for EMC in the task panel. Thanks, Matt
Hi Matt On Monday 13 February 2006 00:31, Matt Timmermans wrote:
It was the earlier graphic.
Ah.. During the installation from the CD - Missed that bit.
It turned out to be some assertion getting thrown in the bit that discovers the drive geometry before partitioning. I managed to muddle through the text mode install, telling it to ignore the assertions as they came up. The remainder of the install took 5 hours, and it didn't set up the operator user properly, but everything else was just fine. It was easy enough to fix.
There is no way the installation should be taking five hours - 45-60 minutes should be the norm. I need to take a long hard look at where anaconda is wasting time and try to improve on things. Could you provide some specs on the laptop (CPU speed, memory, etc). Regards, Paul. -- From the Klingon book of C: Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
Hi Paul, It's a P266 with 128MB RAM and 4 GB disk. Detailed specs are here: http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_outFrm.jsp?moid=1073769720&... I partitioned it with a 3GB ext3 partition for /, and 1GB swap partition. The installer told me that it was activating the swap immediately, because I had so little memory. I'm guessing that the install took so long, because it had to use swap for unpacking the archives. -- Matt ----- Original Message ----- From: "Paul" <[email protected]> To: "BDIHelp" <[email protected]> Sent: Sunday, February 12, 2006 7:55 PM Subject: Re: [Bdi4emc-help] Install trouble on a Toshiba laptop (330CDT) Hi Matt On Monday 13 February 2006 00:31, Matt Timmermans wrote:
It was the earlier graphic.
Ah.. During the installation from the CD - Missed that bit.
It turned out to be some assertion getting thrown in the bit that discovers the drive geometry before partitioning. I managed to muddle through the text mode install, telling it to ignore the assertions as they came up. The remainder of the install took 5 hours, and it didn't set up the operator user properly, but everything else was just fine. It was easy enough to fix.
There is no way the installation should be taking five hours - 45-60 minutes should be the norm. I need to take a long hard look at where anaconda is wasting time and try to improve on things. Could you provide some specs on the laptop (CPU speed, memory, etc). Regards, Paul. --
From the Klingon book of C: Klingon function calls do not have 'parameters' - they have 'arguments' - and they ALWAYS WIN THEM.
_______________________________________________ Bdi4emc-help mailing list [email protected] http://lists.ourproject.org/cgi-bin/mailman/listinfo/bdi4emc-help
participants (2)
-
Matt Timmermans -
Paul