From: Newtor <gen...@gm...> - 2009-07-28 19:15:28
|
Hello, Been out of town for a couple weeks, but am back now. Here's my latest run with 1.9.21. It's looking very nice as usual. The installer is coming along very nicely - keep up the good work M0E. The kde theme looks very nice as well - better than the default kde4 look. I'm still able to reproduce the fatal errors during package selection, and there were a few other (mostly) minor issues. The summary is below: >>> Preamble: vmware virtual install; reused virtual machine; new partitions; >>> custom/manual package selection but defaulted to full install; all services >>> selected: updated installer before beginning using following steps (for static network): >>> kill 3864 (dhcpcd pid) >>> ifconfig eth0 down >>> create /etc/resolv.conf >>> add 'nameserver 192.168.100.1' and save >>> ifconfig eth0 192.168.100.252 netmask 255.255.255.0 up >>> route add default gw 192.168.100.1 >>> cd speedy >>> svn up >>> received 'updated to revision 691' >>> gbr2 /root/speedy/vinstall-ng.gambas >>> >>> Initial installer lag time was significantly reduced in my virtual >>> environment. Previously (1.17 and before) it was somewhere around 60-70 >>> seconds. It was only about 20 seconds this time. I'm sure on real hardware it would be a bit quicker still. >>> >>> Fatal Error: I can still receive fatal errors by clicking 'next'/'back' and >>> selectall/unselectall a few times through the package selection screens and >>> when finally getting to the Installation Summary the fatal error happens. The >>> fatal error is: [-1] Key already used: 'X11'. Step8.?.0 >>> >>> More fatal errors below. Starting from first package selection screen, this is the sequence: >>> next, next, next - works fine >>> next, next, next, back, back, back, next, next, next - fatal error ([-1] Key already used: 'X11'. Step8.?.0) >>> next, next, next, back, next - fatal error ([-1] Key already used: 'FUN'. Step8.?.0) >>> >>> Seems like a variable/key is set during the first pass through and then when >>> the user backs up and moves forward the variable/key attempts to be added >>> again causing a conflict (duplicity). Something like that. >>> >>> I moved ahead with the 'Full Installation' at this point. >>> >>> I gotta ask, does the scrolling developer marquee slow down the installation >>> process at all? If it does then perhaps a static text box would be better to >>> decrease installation time, but if not then the scrolling would be preferred. >>> >>> Also, I'm flattered by the addition of my name to the scrolling marquee but >>> don't feel like I'm any kind of a developer. Stretchedthin on the other hand >>> has done a tremendous service with his/her video tutorials amonst other things >>> - an amazing job and (I bet) quite time consuming. >>> >>> I was asked twice to insert my 2nd cd. The second time it worked - perhaps >>> just an artifact of the virtual environment or I clicked 'Okay' too quick. >>> >>> System Bootloader Config: The video resolution dropdown is cut off about half way. >>> The target dropdown is slightly cut off at the end. >>> The default name is 'slackware'. >>> >>> After clicking on 'Grub' bootloader, I lose the ability to use my keyboard to >>> type a new label. I think it's related to a maximum characters in the 'Label' field being exceeded. >>> >>> Ifplugd still has 'vmware modules' as it's description. >>> >>> First boot: >>> even though the grub boot loader has a very long label starting with >>> 'slackware.....' the labels that actually showed up were 'vector linuc ()' and >>> 'vector linux (fail safe)' (the labels may not be exact) >>> >>> During post-installation configuration it ask about my keyboard settings, and >>> they are different than what I selected during the gui installer. Is there a >>> way to carry over the setting from the gui installer? >>> >>> Services failed during boot: >>> vmware, wicd or wifi-radar >>> >>> KDM: my user login failed. The user was shown as an option but my password >>> was not accepted - did I mistype it? Root account did work, on the other hand. >>> >>> akondadi control and server processes fail on first boot. >>> >>> After resetting my user account password I was able to login. I guess I'll >>> have to try another install and see if I just mistyped my password. >>> >>> The theme look much nicer than the default KDE4 theme. Cheers, newt |