Hi all, Just wondering if it is me, or if there is a reason why the 10.1 beta install time is greater then 12 hours from the CD's? I credit this to the faulty font config packages mentioned elsewhere, as I noticed during the install it seemed to freeze during font installations. My concern after this is even after replacing the font config packages once the system is up and running, the boot on the system is extremely slow and the OS is sluggish enough to be unusable at all. My system is no slug, and Suse 10.0 runs fine on it as do other distros. Any ideas why this might be? My system is an AMD Athlon 2400, 1 GB RAM, swap configured for 1GB as well. Thanks. Regards, Eric Burke
Eric Burke wrote:
Just wondering if it is me, or if there is a reason why the 10.1 beta install time is greater then 12 hours from the CD's? I credit this to the faulty font config packages mentioned elsewhere, as I noticed during the install it seemed to freeze during font installations. My concern after this is even after replacing the font config packages once the system is up and running, the boot on the system is extremely slow and the OS is sluggish enough to be unusable at all. My system is no slug, and Suse 10.0 runs fine on it as do other distros. Any ideas why this might be? My system is an AMD Athlon 2400, 1 GB RAM, swap configured for 1GB as well.
My experiences are also serious trouble to get the 10.1 beta2 properly installed. My hardware is an older K7, 512 MB RAM and a 5,8 GB disk slice for / and 1 GB for swap. It has worked and works well since long time with Suse 9.1-9.3 Pro, SLES9 (Java Desktop), OpenSuse 10.0 and Ubuntu 5.10; the last three now in a multiboot configuration with Win2k as well. Already on the 10.1 beta2 intial Partitioning the changes from long time YaST2 installations arised. 10.0 installs streamlined using the 5.8GB single slice mounted as root. (10.1 tries to split this partition in two parititions for / and /home). 10.0 mounts two FAT and two NTFS partitions as /windows/C - F (10.1 doesn't). At last I've had to drop the 10.1 beta2 and go back and reinstall 10.0 from scratch again. I've tried both Internet and CD installations, upgrades and new installations several times. Most of the times 10.1 looks to freeze somewhere during the installation or during boot up. Suse "font config" is mentioned, but also similar on "Save drivers info" (or similar) The libidl package would not install. Once I managed or forced the installation through and was able to logon, the system was sluggish and useless when trying to start any application. I've noticed boot (error) messages like "Kernel panic - not syncing: Fatal exception in interupt" "Fatal error inserting Thermal (........)" "Fatal error inserting lib modules 2.6 ...." "Trans replayed: ....a lot of error message lines follows" Rgds, Terje J. hanssen
Hi, Terje J. Hanssen schrieb:
I've noticed boot (error) messages like
"Kernel panic - not syncing: Fatal exception in interupt"
That problem is very serious. Can you please open a bug in bugzilla with more details? If it's too much work to transcribe the full kernel panic message, you can also take a photo with a digital camera. Regards, Carl-Daniel -- http://www.hailfinger.org/
"Terje J. Hanssen"
My experiences are also serious trouble to get the 10.1 beta2 properly installed. My hardware is an older K7, 512 MB RAM and a 5,8 GB disk slice for / and 1 GB for swap. It has worked and works well since long time with Suse 9.1-9.3 Pro, SLES9 (Java Desktop), OpenSuse 10.0 and Ubuntu 5.10; the last three now in a multiboot configuration with Win2k as well.
Already on the 10.1 beta2 intial Partitioning the changes from long time YaST2 installations arised. 10.0 installs streamlined using the 5.8GB single slice mounted as root. (10.1 tries to split this partition in two parititions for / and /home). 10.0 mounts two FAT and two NTFS partitions as /windows/C - F (10.1 doesn't).
The later is worth a bug report, please follow bugs.opensuse.org. The extra home partition was a request made here that we incorporated. If the heuristic needs fine tuning, please open a bugreport with details.
At last I've had to drop the 10.1 beta2 and go back and reinstall 10.0 from scratch again. I've tried both Internet and CD installations, upgrades and new installations several times. Most of the times 10.1 looks to freeze somewhere during the installation or during boot up. Suse "font config" is mentioned, but also similar on "Save drivers info" (or similar) The libidl package would not install.
Once I managed or forced the installation through and was able to logon, the system was sluggish and useless when trying to start any application.
I've noticed boot (error) messages like
"Kernel panic - not syncing: Fatal exception in interupt"
That's a serious issue - we need that in bugzilla so that it gets fixed.
"Fatal error inserting Thermal (........)" "Fatal error inserting lib modules 2.6 ...." "Trans replayed: ....a lot of error message lines follows"
Andreas -- Andreas Jaeger, aj@suse.de, 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
Carl-Daniel Hailfinger wrote:
Terje J. Hanssen schrieb: /> I've noticed boot (error) messages like / /> / /> "Kernel panic - not syncing: Fatal exception in interupt" /
That problem is very serious. Can you please open a bug in bugzilla with more details? If it's too much work to transcribe the full kernel panic message, you can also take a photo with a digital camera.
Andreas Jaeger wrote:
That's a serious issue - we need that in bugzilla so that it gets fixed.
As Bugzilla is new to me, can someone guide me how to attach screen photos to a bug report in Bugzilla? Rgds, Terje J. Hanssen
On Sun, Feb 12, 2006 at 04:05:23PM +0100, Terje J. Hanssen wrote:
As Bugzilla is new to me, can someone guide me how to attach screen photos to a bug report in Bugzilla?
On the bug page there's a link called "Create attachment" (a bit hidden between all the other things). Click that, select file for upload. add a description, upload, done. Sonja -- Sonja Krause-Harder (skh@suse.de) Research & Development SUSE Linux Products GmbH
Sonja Krause-Harder wrote:
On Sun, Feb 12, 2006 at 04:05:23PM +0100, Terje J. Hanssen wrote:
As Bugzilla is new to me, can someone guide me how to attach screen photos to a bug report in Bugzilla?
On the bug page there's a link called "Create attachment" (a bit hidden between all the other things). Click that, select file for upload. add a description, upload, done.
Sorry, I can't still see it. I'm using the link https://bugzilla.novell.com/enter_bug.cgi?product=SUSE+Linux+10.1 and after login get the initial page headed "Enter Bug: SUSE Linux 10.1 This page lets you enter a new bug into Bugzilla." In the middle section of this page, there is a Bug Details Summary field and a Desription field. Below these there is a <Submit Report> button. The section below is "Other information". Could you possibly reference the "Create attachment" link on this page, possibly on another page? Will it be one attachment for each photo (jpg file) or? Thanks, Terje J. Hanssen
On Sun, Feb 12, 2006 at 04:55:56PM +0100, Terje J. Hanssen wrote:
Sorry, I can't still see it. I'm using the link https://bugzilla.novell.com/enter_bug.cgi?product=SUSE+Linux+10.1 and after login get the initial page headed "Enter Bug: SUSE Linux 10.1 This page lets you enter a new bug into Bugzilla."
Sorry. You have to enter a bug first. Then you can add attachments to it.
Will it be one attachment for each photo (jpg file) or?
Yes. Sonja -- Sonja Krause-Harder (skh@suse.de) Research & Development SUSE Linux Products GmbH
Sonja Krause-Harder wrote:
On Sun, Feb 12, 2006 at 04:55:56PM +0100, Terje J. Hanssen wrote:
Sorry, I can't still see it. I'm using the link https://bugzilla.novell.com/enter_bug.cgi?product=SUSE+Linux+10.1 and after login get the initial page headed "Enter Bug: SUSE Linux 10.1 This page lets you enter a new bug into Bugzilla."
Sorry. You have to enter a bug first. Then you can add attachments to it.
Will it be one attachment for each photo (jpg file) or?
Philipp Thomas wrote:
You can't attach anything to a bugreport you're just creating. So first enter your bug report, submit the report and when you revisit that report, you will get the option to create an attachment.
OK, thanks. Collected the jpg's in one pdf. Rgds, Terje J. Hanssen
Terje J. Hanssen schrieb:
Sonja Krause-Harder wrote:
On Sun, Feb 12, 2006 at 04:55:56PM +0100, Terje J. Hanssen wrote:
Sorry, I can't still see it. I'm using the link https://bugzilla.novell.com/enter_bug.cgi?product=SUSE+Linux+10.1 and after login get the initial page headed "Enter Bug: SUSE Linux 10.1 This page lets you enter a new bug into Bugzilla."
Sorry. You have to enter a bug first. Then you can add attachments to it.
Will it be one attachment for each photo (jpg file) or?
Philipp Thomas wrote:
You can't attach anything to a bugreport you're just creating. So first enter your bug report, submit the report and when you revisit that report, you will get the option to create an attachment.
OK, thanks. Collected the jpg's in one pdf.
Um, I think there was a misunderstanding. Once you have created a bugreport, you can attach as many files as you like, but only one at a time. After you have created the first attachment, you will get a page asking you whether you want to attach another one. So if possible, please attach the individual jpeg images and not the pdf. PDF files have a tendency to make images big and unreadable and they can't be displayed in a browser without plugins installed. Regards, Carl-Daniel -- http://www.hailfinger.org/
On Sun, 12 Feb 2006 16:55:56 +0100, Terje J. Hanssen wrote:
Sorry, I can't still see it. I'm using the link https://bugzilla.novell.com/enter_bug.cgi?product=SUSE+Linux+10.1 and after login get the initial page headed "Enter Bug: SUSE Linux 10.1
You can't attach anything to a bugreport you're just creating. So first enter your bug report, submit the report and when you revisit that report, you will get the option to create an attachment. Philipp
Eric Burke
Hi all,
Just wondering if it is me, or if there is a reason why the 10.1 beta install time is greater then 12 hours from the CD's? I credit this to the faulty font config packages mentioned elsewhere, as I noticed during the install it seemed to freeze during font installations. My concern after
Yes, that's definitely a culprit on a lot of installations - strangely it always worked for me :-(
this is even after replacing the font config packages once the system is up and running, the boot on the system is extremely slow and the OS is
The bootup time is longer and we do have SLAB debugging enabled in the kernel - but it shouldn't be as bad as you describe.
sluggish enough to be unusable at all. My system is no slug, and Suse 10.0 runs fine on it as do other distros. Any ideas why this might be? My system is an AMD Athlon 2400, 1 GB RAM, swap configured for 1GB as well. Thanks.
I would appreciate if you could do some investigation and figure out what goes on. Btw. please discuss the Betas on the opensuse-factory list, Andreas -- Andreas Jaeger, aj@suse.de, 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
participants (6)
-
Andreas Jaeger -
Carl-Daniel Hailfinger -
Eric Burke -
Philipp Thomas -
Sonja Krause-Harder -
Terje J. Hanssen