Mailinglist Archive: opensuse (4208 mails)

< Previous Next >
RE: [SLE] Boot time excessive for clean SuSE 9.0 install
  • From: "Larry Johnson KISE" <ljohnson@xxxxxxxxxxxx>
  • Date: Mon, 26 Jul 2004 15:18:10 -0700
  • Message-id: <NFBBKDGMKLPBLAOOBFHBOEECECAA.ljohnson@xxxxxxxxxxxx>
Well after looking at the syslog with full debugging turned on, it's clear
that hotplugging is the culprit.

So I disable the four USB 1.1 ports from the motherboard BIOS, and now I get
a 4 minute boot, down from 9 minutes.

So the I disable USB hotplugging with SuSE configuration to avoid my USB 2.0
ports, and now I get a 1 minute boot.

I review the HOTPLUG docs in SuSE 9.0 - practically zilch.

I go to hotplugging at sourceforge,
and about the time the SuSE scripts were written signed off, there are
threads about all kinds of problems with USB and delays - some from SuSE.
There is a bug reported 25 July 2004 about this same issue. (997624)

This explains the NOHOTPLUG and NOCOLDPLUG options in SuSE 9.1.

So I say that SuSE sold a distribution with a buggy boot scheme, didn't
provide a workable alternative, that they were aware of it, and are
unwilling to acknowledge it. I would love to be wrong about this.

Apparently (unverified) the use of multiple & mixed versions of USB hubs
triggers the problem - standard features of my Gigabyte GA-7VRXP Rev 2.0

There are some indications that the problem also exists in SuSE 9.1 as well
as other distributions that use hotplugging.

I have spent quite a bit of time discovering this unpleasant fact, and I am
very unhappy about it.

Pressure from users (as well as the Linux community) has moved MS to improve
their products and practices, perhaps it could work for SuSE/Novell too.

Larry Johnson, KeepItSimpleEngineering,Inc.

> -----Original Message-----
> From: doc [mailto:kd4e@xxxxxxxxxxx]
> Sent: Sunday, July 25, 2004 18:29
> To: suse-linux-e@xxxxxxxx
> Subject: Re: [SLE] Boot time excessive for clean SuSE 9.0 install
> Larry Johnson KISE wrote:
> > So I tried NOHOTPLUG=YES as a boot parameter, and then NOHOTPLUG=YES and
> > NOCOLDPLUG=YES, but boot is still hanging in the same places -
> it seems that
> > these boot parameters don't work in 9.0.
> >
> > -----
> >
> > I'm about ready to conclude that the SuSE desktop is not ready for prime
> > time, and that SuSE doesn't care. I know that's harsh - but skimpy and
> > apparently inaccurate documentation along with too much stuff
> that does not
> > work like HP printers/Scanners (only works under root)/PC Webcams and
> > meaningless error messages/unstable applications/too much
> system maintenance
> > have tolerance limits in users, especially me. Too much time,
> not enough
> > results.
> >
> > I short, I'm bummed about it.
> > Larry Johnson, KeepItSimpleEngineering,Inc.
> Why are you judging Suse on an *old* version, that seems to make very
> little good technological sense.
> You need to run 9.1 with all of the updates before making any valid
> judgments about whether or not "SuSE" is "ready for prime time".
> I have to say that the powers-that-be continue to insist upon
> Microsoft products where I work and we suffer *daily* troubles
> with lost files, crashing windows, incompatibilities, unnecessary
> virus vulnerabilities, constant needs for "critical security updates",
> etc.
> In the real world there is no perfect desktop but I have chosen
> Suse 9.1 and run it on my notebook at home and at work -- interfaced
> with the lesser Microsoft machines -- because I trust it for security
> and stability that no version of MS Windows has ever offered.
> IMHO, YMMV ... ;-)
> --
> Thanks! & 73, doc kd4e
> West Central Florida 100% Linux. Suse 9.1
> Drake, Hallicrafters, Heathkit, TenTec, Yaesu
> Radio Life:
> Linux-Incompatible hardware is defective!
> USA Pres. Election 2004:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> --
> Check the headers for your unsubscription address
> For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
> Also check the archives at
> Please read the FAQs: suse-linux-e-faq@xxxxxxxx

< Previous Next >