https://bugzilla.novell.com/show_bug.cgi?id=281243 snwint@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |gs@novell.com ------- Comment #1 from snwint@novell.com 2007-06-14 03:36 MST ------- Hm, looks to me identical to bug 278679, but more concise. If it hangs at the language screen, it is unlikely a memory issue. You'd need to provide some logs (http://en.opensuse.org/Bugs/YaST) to see what's happening. Moving bug to Gabi for the ncurses interface issues. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=281243 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|alpha096@tpg.com.au | ------- Comment #3 from alpha096@tpg.com.au 2007-06-14 16:46 MST ------- Sorry Unable to provide Logs as PC has been formatted for non GUI install. However I have ordered more RAM up to 512 lieu 384. I was so frustrated with non GUI install that took 6 days when it failed I pug AGP 128 MB Video card in and then tried 10.2 install which failed to more past language screen. I then tried 10.0 which did install 5 Days, however would not run when login. I am inclined NOT to trust the old PC which appears to have other issues old BIOS revision etc and is a Dell (non standard architecture always and components). Will attempt 10.2 GUI install when RAM arrives. Apologies for not saving logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=281243#c5 Scott Couston <scocoo@tpg.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bnc-team-screening@forge.provo.novell.com Severity|Major |Enhancement Status|RESOLVED |REOPENED Resolution|REMIND | Summary|GUI Installation is Not |GUI Installation is Not Possible with ( Paper |Possible with (Manual ) |Manual and Boxe ) Minimum System Criteria + |Publish Minimum System |possible solution |Criteria | --- Comment #5 from Scott Couston <scocoo@tpg.com.au> 2007-06-22 01:20:49 MST --- The text installation I did not pursue, mainly because as soon as I added the 128MB Video Card - it ran in GUI and I am sorry I cannot debug an install program that took over 10 days!!!!!!!!!!!!! Therefore along with the Physical RAM and CPU requirements we need to add minimum Graphics card VRAM. As in this case with the addition of a Video Card from 64MB upwards and not using an in build motherboard graphics - which must use perhaps between 4 -8 MB of shared System RAM, GUI interface WAS possible, however unusable. If any change is warranted in system requirements feel it should be inclusive of a Video Card with X and above RAM. I added more physical RAM so I have a PC now at P3 1500GHz 128 MB AGP Video RAM and 512 MB of Physical RAM and increased the HDD to 37GB and new CD R-W 40 x (x) x (x) x (x) I started to load 10.2 which it did, after the 128MB Video Card, Yast2 started in Graphics and before Language selection a Text window opened indicating shortage of RAM and requested Swap Space location. At this time the New install had no Linux formatting or SWP space so I could not activate the swap space required. As much as you can write the code as small as possible, every enhancement to the current install script will probably provide more functionality and most likely require more RAM. Enhancement request I think rather than start the install script we might just add a menu item (1) OR (2) in response to the Text based request for SWP Partition we evoke the GUI Partitioner for experts. In that way the user is able under directions from an admin or call for help to format the disk and create a SWP space. After the SWP space has been created (may not be necessary to provide full expert partitioning tool, however less code) the Install can be run again, this time when the text question requests SWP space it is already defined and should self fulfil the Virtual RAM that the whole install script requires now and in any future release of Suse. By adding the proposal to the Install Menu of "Active Partitioner Only" will require very little change in code and add support for hopefully a very long time of future releases. The partitioner only requires a very small amount of code and I know is basically a stand alone application now - All we need to do is add it to the menu as the current install already requests selection of SWP space, however on a new disk it will not be there. This should ???? be a very very addition to the Install program as it is probable only dependant on the 'udev' and a few other; if we go for option 1 above and add it to the Install Menu. Option 2 above IS more elegant - however Physical RAM and providing virtual RAM is what this request about and it could well be that being more elegant always means more RAM - Jast ask a Vista Pro user (who needs a new PC to run it) Option 1 could be easily added to version 10.3 I would believe as there should? be very very little coding envolved and no application interface needs to be built. Please let me know what you think - Sorry to mix thease two but its a little unavoidable and I hope you will forgive me just this once - just to maintain continuity Scott o-) Pleased on needinfor for reply to author Unquote Please let me know -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=281243#c7 Scott Couston <alpha096@tpg.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|alpha096@tpg.com.au | --- Comment #7 from Scott Couston <alpha096@tpg.com.au> 2007-07-04 00:07:23 MST --- I am sorry - it is quite apparent and not evident with the professional approach by Novell.de that your are serious about making the install program work with (currently) hardware that meets printed minimum requirements. This was easy to do as following software selection, providing more than adequate virtual RAM in the first stages - requires a re-boot and activation of the HDD virtual RAM availability. We dispensed with the ability to utilise what virtual RAM had been created in stage one, right until al software was reloaded and a the first re-boot which activated the availability of virtual RAM defined 6 disks ago and yet is not made use of until the the final boot. 10.0 did not work this way, all user input was registered, the system would reboot having access to the virtual RAM defined on the first disk. This part of the installation phase MUST be set early as further demands, by a more complex install programs will require more resources. 1. virtual RAM which is established very early one disk one IS not made use of in 10.2 as the first boot occurs at the end, which you may never get there, running out of physical RAM and in the current environment the virtual RAM is defined but not loaded As the install application WILL grow in resources, it may prove folly that inaccessible virtual RAM, defined, but not available; may bring further install script to a halt. I would request that the install profram follow the lines of 10.0 in that it can provide available virtual RAM after the configuration of same is done on disk one. The system should then first boot and have access to the now loaded virtual RAM. Currently this now does not occur as the swap volute is not mounted until the very very last of install procedure. RE: #6 "should go fine even without swap space activated." - we deal in realities. The expensed and demands of bow and further install script will depend on FACT. Fundamentally the current install program is flawed in low resourced devises - particularly when install script get far larges. Please consider this request to have Virtual RAM Available after it is defined and first boot occurred and all facilities. That way you overt to increases in install demands with ease. I no longer have the files you need, however in your test environment its will be faithfully reproduciable If you find not value in the bug, by all means close it wontfix. regards Scott -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=281243#c9 --- Comment #9 from Gabriele Mohr <gs@novell.com> 2007-08-09 04:12:50 MST --- Created an attachment (id=156428) --> (https://bugzilla.novell.com/attachment.cgi?id=156428) Hwinfo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.