Went for my second install of 6.4 on a new machine. This time, things did not go so smoothly. So far there have been three distinct problems: First, after you install initial packages off disk 1, Yast2 asks you to remove install media and it 'reboots, sortof. I had a Microsoft intella wheel mouse, and the yast2 screen locked up. No VT's could be accessed, and there was no response to the keyboard. I had to press reset, and all my e2fs partitions were thrashed. The happened THREE times in a row, until I replaced the MS wheel mouse with a Logic Tec three button PS/2 mouse. No more lockup. There was no indication of the mouse problem, it was Two, after going through the 15,000 packages to install (that's what we all like about SuSE), you have an option to save your selections to a floppy. Now, at a later date, I wanted to reinstall everything from scratch. However, there is no option to re-read your selections from the floppy, saving you hours of package selection. What good is the save to floppy then? Third, this system had two ethernet cards and works as a firewall. I didn't re-compile the kernel, with hope SuSE would install modules as necessary. After modifying /etc/rc.config with the info on eth0 and eth1, then rebooted. Suse could not find eth0 but it did find eth1. Later on a shutdown, during 'shutting down eth0' the system completely hung. I waited optimistically, but gave up after a half hour or no activity. I pressed reset, and watched fsck do it's thing. After finally coming back to li I have decided to format the root partition and install everything again, using what I have learned about this system. It's too bad condition number two exists. That portion of the install is a serious pain. These are a few examples why Linux is not ready for prime time. -- Ryan Allen Software Engineer, Systems Integration Group. Cray Inc. 411 First Avenue South Suite 600 Seattle, WA 98104-2860 -- Ryan Allen ryan@aa.net Web Mail services provided by http://www.aa.net -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Wed, 31 Dec 1969, Ryan Allen wrote:
Went for my second install of 6.4 on a new machine. This time, things did not go so smoothly. So far there have been three distinct problems:
So far, I've installed twice on two machines. First, on a Thinkpad 600X, initial install went fine except when Sax decided that it would put up a 1028 x 768 screen, but only show 640 x 480, making it impossible to see what you were tabbing to, (and of course you couldn't click offscreen). That one was easy for me (intermediate newbie), but not your real newbie. Second install went fine. The second machine, basic Dual PPro 200 Scsi system, I had the same Yast2 lockup problems on the first install, but not the second. No further install problems (that I didn't create myself). I have, however, had intermittent mouse lockups in X windows that I have had to kill the XServer to get out. Different windowmanagers, basic old Microsoft two button mouse, TNT videocard.
-- Ryan Allen Software Engineer, Systems Integration Group. Cray Inc. 411 First Avenue South Suite 600 Seattle, WA 98104-2860
-- Ryan Allen ryan@aa.net
Web Mail services provided by http://www.aa.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Ryan Allen wrote:
Went for my second install of 6.4 on a new machine. This time, things did not go so smoothly. So far there have been three distinct problems:
First, after you install initial packages off disk 1, Yast2 asks you to remove install media and it 'reboots, sortof. I had a Microsoft intella wheel mouse, and the yast2 screen locked up. No VT's could be accessed, and there was no response to the keyboard. I had to press reset, and all my e2fs partitions were thrashed. The happened THREE times in a row, until I replaced the MS wheel mouse with a Logic Tec three button PS/2 mouse. No more lockup. There was no indication of the mouse problem, it was
This is a YAST2 problem with the mouse. I went back to Yast1 and this didn't happen. But even Yast 1 reboots after getting all it can from CD-1. This is new to the installation process. I'm not sure why but I'm sure there is a reason. The intell- mouse issue has always been there. Until you get XF86 up and running you don't want to tell it your mouse is an IMPS/2. Just leave it as a PS/2 untill your all done then do it manually by editing XF86Config.
Two, after going through the 15,000 packages to install (that's what we all like about SuSE), you have an option to save your selections to a floppy. Now, at a later date, I wanted to reinstall everything from scratch. However, there is no option to re-read your selections from the floppy, saving you hours of package selection. What good is the save to floppy then?
Again this COULD just be a Yast2 problem. Yast1 does this correctly.
Third, this system had two ethernet cards and works as a firewall. I didn't re-compile the kernel, with hope SuSE would install modules as necessary. After modifying /etc/rc.config with the info on eth0 and eth1, then rebooted. Suse could not find eth0 but it did find eth1. Later on a shutdown, during 'shutting down eth0' the system completely hung. I waited optimistically, but gave up after a half hour or no activity. I pressed reset, and watched fsck do it's thing. After finally coming back to li
I've not yet done an install with more than one NIC.
I have decided to format the root partition and install everything again, using what I have learned about this system. It's too bad condition number two exists. That portion of the install is a serious pain.
These are a few examples why Linux is not ready for prime time.
These are just YAST2 maturing. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Ryan Allen wrote:
Went for my second install of 6.4 on a new machine. This time, things did not go so smoothly. So far there have been three distinct problems:
First, after you install initial packages off disk 1, Yast2 asks you to remove install media and it 'reboots, sortof. I had a Microsoft intella wheel mouse, and the yast2 screen locked up. No VT's could be accessed, and there was no response to the keyboard. I had to press reset, and all my e2fs partitions were thrashed. The happened THREE times in a row, until I replaced the MS wheel mouse with a Logic Tec three button PS/2 mouse. No more lockup. There was no indication of the mouse problem, it was
Two, after going through the 15,000 packages to install (that's what we all like about SuSE), you have an option to save your selections to a floppy. Now, at a later date, I wanted to reinstall everything from scratch. However, there is no option to re-read your selections from the floppy, saving you hours of package selection. What good is the save to floppy then?
YaST 2 is still very limited when it comes to package selection, as it's still a work in progress (isn't everything? ;-) ). If you want to select your own packages (or use your config floppy) then you'll have to use good old YaST 1, which you can get to by booting CD2 instead of CD1.
Third, this system had two ethernet cards and works as a firewall. I didn't re-compile the kernel, with hope SuSE would install modules as necessary. After modifying /etc/rc.config with the info on eth0 and eth1, then rebooted. Suse could not find eth0 but it did find eth1. Later on a shutdown, during 'shutting down eth0' the system completely hung. I waited optimistically, but gave up after a half hour or no activity. I pressed reset, and watched fsck do it's thing. After finally coming back to li
I have decided to format the root partition and install everything again, using what I have learned about this system. It's too bad condition number two exists. That portion of the install is a serious pain.
Hope you get everything fixed, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I believe that yast1 allows you to save and load custom configurations. If you have one saved already, then try using yast1. Victor On Mon, 24 Apr 2000, Ryan Allen wrote:
Went for my second install of 6.4 on a new machine. This time, things did not go so smoothly. So far there have been three distinct problems:
First, after you install initial packages off disk 1, Yast2 asks you to remove install media and it 'reboots, sortof. I had a Microsoft intella wheel mouse, and the yast2 screen locked up. No VT's could be accessed, and there was no response to the keyboard. I had to press reset, and all my e2fs partitions were thrashed. The happened THREE times in a row, until I replaced the MS wheel mouse with a Logic Tec three button PS/2 mouse. No more lockup. There was no indication of the mouse problem, it was
Two, after going through the 15,000 packages to install (that's what we all like about SuSE), you have an option to save your selections to a floppy. Now, at a later date, I wanted to reinstall everything from scratch. However, there is no option to re-read your selections from the floppy, saving you hours of package selection. What good is the save to floppy then?
Third, this system had two ethernet cards and works as a firewall. I didn't re-compile the kernel, with hope SuSE would install modules as necessary. After modifying /etc/rc.config with the info on eth0 and eth1, then rebooted. Suse could not find eth0 but it did find eth1. Later on a shutdown, during 'shutting down eth0' the system completely hung. I waited optimistically, but gave up after a half hour or no activity. I pressed reset, and watched fsck do it's thing. After finally coming back to li
I have decided to format the root partition and install everything again, using what I have learned about this system. It's too bad condition number two exists. That portion of the install is a serious pain.
These are a few examples why Linux is not ready for prime time.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (5)
-
chris.reeves＠iname.com -
dmarkh＠cfl.rr.com -
philtz＠mediaone.net -
ryan＠aa.net -
vcardona＠home.com