I was testing the boot.iso installation yesterday and was unable to make any headway. Their is a failure at the Floppy IO, during the YAST configuration where it is checking packages. Please fix this. I am currently installation Suse from a friends Personal Edition. At least this way I will be able to see what Suse looks like. However, it's a pretty grim start for what is proclaimed to be one of the better distributions out there. What surprises me most is that this boxen has been used to install everything as a test bed and it is here that it just can't get started. The CD installation is extremely unstable on the XWindow GUI. I'm not sure that I will even be able to finish, but time will tell. I have not tried RedHat on this boxen yet, but I have tried Slackware, Gentoo, Debian with success. -- Men have a much better time of it than women; for one thing they marry later; for another thing they die earlier. -- H.L. Mencken
On Mon, Jun 02, 2003 at 10:53:33PM -0400, Tom Allison wrote:
I was testing the boot.iso installation yesterday and was unable to make any headway. Their is a failure at the Floppy IO, during the YAST configuration where it is checking packages.
boot.iso is intended for ftp installation. Was your computer connected to the Internet?
Please fix this.
I'm afraid you're asking in the wrong place. If you want to address your request to SuSE, you better do it at http://www.suse.de/cgi-bin/feedback.cgi
I am currently installation Suse from a friends Personal Edition. At least this way I will be able to see what Suse looks like.
If you want to get an idea of what SuSE Linux looks like you probably better try LiveEval CD, that's a complete SuSE system running off a CD. It's available at ftp://ftp.suse.com/pub/suse/i386/live-eval-8.2/SuSE-8.2-LiveEval-i386-Int-RC2.iso
The CD installation is extremely unstable on the XWindow GUI. I'm not sure that I will even be able to finish, but time will tell.
What do you mean by "unstable"? Did it fail at some point?
I have not tried RedHat on this boxen yet, but I have tried Slackware, Gentoo, Debian with success.
Try SuSE LiveEval. It should work. Regards, -Kastus
Tom Allison wrote:
I was testing the boot.iso installation yesterday and was unable to make any headway. Their is a failure at the Floppy IO, during the YAST configuration where it is checking packages.
As far as I am concerned there is no way that Yast is trying to install Suse from Floppy, which gives me to think if you are really writing about your experience, or just marketing some other OS.
Please fix this.
This shows that you do not have that much experience with computers and software, otherwise you would not ask for this in a mailinglist and without giving anymore details.
I am currently installation Suse from a friends Personal Edition. At least this way I will be able to see what Suse looks like.
However, it's a pretty grim start for what is proclaimed to be one of the better distributions out there. What surprises me most is that this boxen has been used to install everything as a test bed and it is here that it just can't get started.
The CD installation is extremely unstable on the XWindow GUI. I'm not sure that I will even be able to finish, but time will tell.
I cannot confirm any of this, in fact I think that it is very unlikely that this is related to the installation GUI if it happened at all, as there are so many users who installed Suse 8.2 without any problems, leaving aside some that had problems due to hardware failure but certainly not with a floppy drive that is not needed when Yast2 is up, especially if you are using the boot.iso, which would hint to a ftp-installation, or hd-installation (unlikely) but certainly not a floppy-disk installation. Further an I/O error with the fd might lead to Yast2 not including it into the configuration. However, if you used it for the boot-images successfully it sounds unlikely that it suddenly fails after that. If you used the CD boot.iso you would have disabled it in the BIOS. Knowing about testbed etc. shows some knowledge of computers, which strucks me because of your fix comment and the inability to give more detail, apart from trying to install 8.2 without fd, i.e. disabling it.
I have not tried RedHat on this boxen yet, but I have tried Slackware, Gentoo, Debian with success.
In my opinion and I might be wrong this posting is meant to market some other OS, or just very ignorant of the computer knowledge shown in some parts of it. Whoever just installs Redhat, Slackware, Gentoo and Debian surely must have some knowledge in order not to fail at a floppy-problem without giving more information or trying disabling it. Sven
The 03.06.03 at 08:01, Sven Burmeister wrote:
This shows that you do not have that much experience with computers and software, otherwise you would not ask for this in a mailinglist and without giving anymore details.
As a matter of fact, he did, but got almost no responses. He was installing by FTP, but for some unknown reason, after language selection the process got stuck when it tried to check the floppy drive with an IO error - read his email of two days ago, and see if you can help him. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.06.03 at 08:01, Sven Burmeister wrote:
This shows that you do not have that much experience with computers and software, otherwise you would not ask for this in a mailinglist and without giving anymore details.
As a matter of fact, he did, but got almost no responses. He was installing by FTP, but for some unknown reason, after language selection the process got stuck when it tried to check the floppy drive with an IO error - read his email of two days ago, and see if you can help him.
Well not in this email and also he did not refer to the other. I gave him a hint, i.e. to disable his floppy-drive in the BIOS and/or unplug it. The fact that he did not get any answers might be linked to the fact that it is very unlikely that it has something to do with Suse 8.2. Further, if he already send an email with the same issue then why does he demand in this one a fix and does not refer back to his other email? I might be wrong but in my opinion these are just too many things that rather fit to my suspision than a real propblem of the Suse 8.2 installation. It might be hardware, but again, I told him what to try. I do not tell anyone what they got to think, I just pointed out my opinion as well as the reasons that I have. Certainly the style of the email, especially that fixing issue had a big impact on this, anyway. Sven
Thanks to all who replied... I was originally attempting to do an FTP installation using the boot.iso. I have the computer hooked up to a LAN network residing behind a choke firewall which in turn is behind a standard NAT firewall. No Proxies, local DHCP, DNS, etc. Sven Burmeister wrote:
Tom Allison wrote:
I was testing the boot.iso installation yesterday and was unable to make any headway. Their is a failure at the Floppy IO, during the YAST configuration where it is checking packages.
As far as I am concerned there is no way that Yast is trying to install Suse from Floppy, which gives me to think if you are really writing about your experience, or just marketing some other OS.
Yast isn't trying to install from the floppy. I never said that it was. What is happening is that YAST goes through the installation process and dies during package selection, after the hardware detection process has finished. I'm not sure exactly where, but shortly after it determines a disk partition. The screen states package selection. The error is centered around an IO error regarding the floppy device.
Please fix this.
This shows that you do not have that much experience with computers and software, otherwise you would not ask for this in a mailinglist and without giving anymore details.
I will resist the temptation to flame you here. Seven years on Linux and 25 years with computers might make me somewhat qualified to have at least a rudimentary level of experience with computers. Your opinion on this point is not appreciated, but summary statements on my part can lead to this type of conclusion.
I am currently installation Suse from a friends Personal Edition. At least this way I will be able to see what Suse looks like.
However, it's a pretty grim start for what is proclaimed to be one of the better distributions out there. What surprises me most is that this boxen has been used to install everything as a test bed and it is here that it just can't get started.
The CD installation is extremely unstable on the XWindow GUI. I'm not sure that I will even be able to finish, but time will tell.
I cannot confirm any of this, in fact I think that it is very unlikely that this is related to the installation GUI if it happened at all, as there are so many users who installed Suse 8.2 without any problems, leaving aside some that had problems due to hardware failure but certainly not with a floppy drive that is not needed when Yast2 is up, especially if you are using the boot.iso, which would hint to a ftp-installation, or hd-installation (unlikely) but certainly not a floppy-disk installation. Further an I/O error with the fd might lead to Yast2 not including it into the configuration. However, if you used it for the boot-images successfully it sounds unlikely that it suddenly fails after that. If you used the CD boot.iso you would have disabled it in the BIOS. Knowing about testbed etc. shows some knowledge of computers, which strucks me because of your fix comment and the inability to give more detail, apart from trying to install 8.2 without fd, i.e. disabling it.
The instability with X has to do with the screen. This is a seperate error from my original problem with IO. If I wiggle the mouse when the hourglass is up, the display will break up into bars of green gibberish. Selecting a different mouse driver doesn't help this problem at all. I've simply learned not to move the mouse after a click. I call that unstable. I have an i810 integrated video chip on this motherboard. This may very well be a problem with the mouse, unfortunately the selection made my Yast is the most stable, but the best selection for the given mouse does not appear on the installation menu. And the Knowledge Base states: Cause: The floppy in your BIOS is deactivated. The kernel fails when it tries to recognize the hard disk partitions as there's no floppy device available. Solution: Please activate the floppy in your BIOS settings, even if there's no existing physical device. I couldn't find anything else out there per your previous suggestions.
I have not tried RedHat on this boxen yet, but I have tried Slackware, Gentoo, Debian with success.
In my opinion and I might be wrong this posting is meant to market some other OS, or just very ignorant of the computer knowledge shown in some parts of it. Whoever just installs Redhat, Slackware, Gentoo and Debian surely must have some knowledge in order not to fail at a floppy-problem without giving more information or trying disabling it.
This is not an attempt to market another OS. In fact I'm trying another OS to see how Suse compares with Gentoo, Debian, and Slackware. I've been MSFT free for 6 years.
Tom Allison wrote:
Please fix this.
This shows that you do not have that much experience with computers and software, otherwise you would not ask for this in a mailinglist and without giving anymore details.
I will resist the temptation to flame you here. Seven years on Linux and 25 years with computers might make me somewhat qualified to have at least a rudimentary level of experience with computers.
Ah, yeah seven years of experience and then a comment to a non-devel mailinglist like "please fix this"? Either you are experienced, then one can expect that you do not blame Yast for your display problems, which you did by not stating that the instability of the GUI was due to your hardware and not Suse, and do not request a fix from this mailing-list, or you do not have experience, well then at least your post would be on the right level. Anyway, I am going off topic and that's not a good thing, so I am leaving this thread here. Sven
Tom Allison wrote:
Please fix this.
This shows that you do not have that much experience with computers and software, otherwise you would not ask for this in a mailinglist and without giving anymore details.
I will resist the temptation to flame you here. Seven years on Linux and 25 years with computers might make me somewhat qualified to have at least a rudimentary level of experience with computers.
Ah, yeah seven years of experience and then a comment to a non-devel mailinglist like "please fix this"? Either you are experienced, then one can expect that you do not blame Yast for your display problems, which you did by not stating that the instability of the GUI was due to your hardware and not Suse, and do not request a fix from this mailing-list, or you do not have experience, well then at least your post would be on the right level. Anyway, I am going off topic and that's not a good thing, so I am leaving this thread here. Sven
You're not getting off that easy!!! :) I will try the boot.iso on another machine today and will be looking for a repeat of this floppy IO problem. If it fails, then I will pull the floppy device and see what that does. I haven't had to do that in the past so it seems slightly unorthodox. Not wrong, just unorthodox. With regard to the GUI problem: I am essentially at the point where if I can get the installation to pass, and have a stable OS as the result, then who cares if I have to practice Trancendental Mediation or some other oddities for my stupid mouse? My remarks should go to the Feedback.cgi, and they will when I can get the details necessary. But past experiences has revealed that sometimes installation feedback on a mailing list has two effects: It helps someone else who is experiencing the same problem. Or it presents the developers with a potential bug. However, you implicate the Suse mailing list doesn't work that way. Unlike Debian and Gentoo, you imply that the user mailing list does not gaurantee the presence of the developers as well. True/False? You accused me of attempting to market another OS. Not true. But I am coming from a group of Linux distributions which seem to be different enough in their social and code structure as to present me as something akin to a clueless newbie. Imagine how someone from Linux From Scratch would look at Suse? It would certainly be different, though the inner workings are the same.
On Tuesday 03 June 2003 17.15, tallison@tacocat.net wrote:
However, you implicate the Suse mailing list doesn't work that way. Unlike Debian and Gentoo, you imply that the user mailing list does not gaurantee the presence of the developers as well. True/False?
There are virtually no developers on the gentoo user list. I can't say what the situation is at Debian. And no, the frequently repeated statement from the suse people who are here is that any message you may see here from a SuSE emplyee is purely coincidental. If you want to be sure they read it, you should send it to one of the official SuSE email addresses, or go through the feedback web site
On Tuesday 03 June 2003 17.15, tallison@tacocat.net wrote:
However, you implicate the Suse mailing list doesn't work that way. Unlike Debian and Gentoo, you imply that the user mailing list does not gaurantee the presence of the developers as well. True/False?
There are virtually no developers on the gentoo user list. I can't say what the situation is at Debian.
OK, thanks. FYI, Most of the Debian Developers are on the user-list.
The 03.06.03 at 11:15, tallison@tacocat.net wrote:
However, you implicate the Suse mailing list doesn't work that way. Unlike Debian and Gentoo, you imply that the user mailing list does not gaurantee the presence of the developers as well. True/False?
Correct. A few suse employees do write on the list (I don't know if more read it), but it seems to be exceptional, and unofficial. A complaint, bug, whatever, comented here is not guaranteed to get to the person responsible for correcting it. I don't like it, but that is how things are here :-) I fact, not even reporting something to "feedback" guarantees having it corrected, or at least not till next version. -- Cheers, Carlos Robinson
"Carlos E. R."
I fact, not even reporting something to "feedback" guarantees having it corrected, or at least not till next version.
Yes, we do decide what warrants an immediate update and what not. The policy is rather simple: only serious and/or security bugs will be fixed for released distributions. It's a simple question of resources. Philipp -- Philipp Thomas work: pthomas@suse.de Development, SuSE Linux AG private: philipp.thomas@t-link.de
tallison@tacocat.net [Tue, 3 Jun 2003 11:15:48 -0400 (EDT)]:
However, you implicate the Suse mailing list doesn't work that way. Unlike Debian and Gentoo, you imply that the user mailing list does not gaurantee the presence of the developers as well. True/False?
Yes, that's true. SuSE only runs the list, it's *not* an official support forum. You'll find next to no SuSE developer on this list and any SuSE employee you encounter here is doing it in their free time. Philipp -- Philipp Thomas work: pthomas@suse.de SuSE Linux AG private: philipp.thomas@t-link.de
On Tue June 3 2003 6:53 am, Tom Allison wrote: <snip> Please refer to prior postings for the history... Have you tried the acpi=off and apm=off options at boot? Sounds like some experiences others have had where hardware/BIOS settings/configurations aren't as perfect as we expect and SuSE install and ongoing operations are effected by incomplete or bad ACPI implementations in BIOSes. Stan
participants (8)
-
Anders Johansson -
Carlos E. R. -
Kastus -
Philipp Thomas -
Stan Glasoe -
Sven Burmeister -
tallison＠tacocat.net -
Tom Allison