James PEARSON <[EMAIL PROTECTED]> writes:

> Hello all
>
> I installed openSUSE 10.2 b2 on an old PentiumIII at work which
> uses an i810 chipset. The "yast" install ran in "ncurses" mode but it
> ran ok. That is very notable because alot of live cds wouldn't even
> start an xserver on the i810 chipset. Great work!
>
> Since that worked out OK I decided to install openSUSE 10.2  b2 on my
> T60 Thinkpad (Model 1952 W5R). It has a Intel Centrino Duo 1.83
> cpu with 2 Go of RAM and a Mobile Intel 945GM Express video chipset).
> Note as far as I know only openSUSE 10.1, gentoo, and the
> latest [k|u]buntu work OK on the Intel 945GM video chipset. Hands off to
> openSUSE for being one of the three.

Thanks!

> # My report
> I selected a kde install as per normal. The 10.2 b2 install went fairly
> quickly until it hit the "Download and Installation" page.  Creating /
> downloading the source(s) took some 20 minutes. First remark.  Why does
> creating / downloading the source(s) take so long ? (here's is what I
> hope will be taken as constructive criticism - as I can download 1000
> kb/sec+ on my side, I would appreciate more speed on the suse side. I
> personally would be willing to pay for higher download speeds -
> please note I have had problems in the past with slow updates when
> installing suse using the orginal 10.1 CD's and ended up leaving the
> computer on all night - maybe you could consider a subscription
> service something "a la Mandriva" for higher d/l speeds).
>
> On the "creating / downloading the source(s)" page, yast2 had a problem
> creating one of the sources (it definitely appeared to be looping for
> awhile). After some 20 minutes yast2 offered be the choice to hit the
> skip button and finished the install.

Please create a bug report for these two and attach /var/log/YaST (as
tar file) and /var/log/zmd*log

> When the install finished, yast rebooted automatically into kde but I
> had no kde menu panel. I managed to open a konsole window and I noticed
> that I had no IP either. Please note that I had selected "Network
> manager" during the install instead of the traditional setup method as I
> normally do. It would appear that "Network manager" had a problem when
> it had to choose between the normal network cable (which definitely
> works - I just deleted a working 10.1 install in order to test 10.2) and
> the Intel PRO/Wireless 3945 ABG chipset (which still had to be fully
> configured).

There are already bugs in this area, I think you hit a duplicate.
"rcnetwork restart" should fix it - if not, please open a bugreport.

>
> I rebooted again. On the second reboot I had a "SUSEPlugger - The KDE
> Crash Hander" window telling me that "The application SUSEPluger
> (suseplugger) crashed and casued the signal 6 (SIGABRT) 

Known bug - mentioned in the most annoying ones.

>
> I would really like to work with you on this in order to get openSUSE
> working on my T60. Please let me know what logs I need to send to help
> improve things.

Thanks for your testing!

Andreas
-- 
 Andreas Jaeger, [EMAIL PROTECTED], http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126

Attachment: pgpPfi2aQzrs6.pgp
Description: PGP signature

Reply via email to