Menu
▾
▴
vectorlinux-devel
|
From: Robert L. <vec...@ya...> - 2009-09-02 08:18:33
|
Hi All, Installed A1.21 a little while ago. I have to say we are ready for prime time now all but the grub bootloader went well no hickups even got a face for my user account. The bug I do have is that os-prober does not seem to be doing it's thing from installer I get the default for the partition im installing too and the recovery but no other partitions. After installation if I do grub-mkconfig -o /boot/grub/grub.cfg all works as expected all partitions are picked up with proper vector labels. So I expect all the goodies are in place just the os-prober part is not getting passed to the target partition during install. Other wise great job everyone !!! we are close ..........very close Cheers, Robert Robert Lange vec...@ya... http://www.vectorlinux.com __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ |
|
From: M0E L. <m0...@gm...> - 2009-09-02 12:46:31
|
I've tried so hard to sqash this bug, but it's jut not doing it. Maybe we should do it on first boot we can append the config file that runs on first boot if the user chooses grub for bootloader. |
|
From: Paul M. <pa...@wa...> - 2009-09-02 17:15:22
|
Just installed A1.21. I'm using my own Grub install, so I didn't see that problem, though I notice that my Windows partition is not showing up in the options for the boot loader. Install was pretty good. The problems with lag and strange screen updates that I was seeing are pretty well gone. However, I did hit a couple of other problems with the install. First (niggle rather than serious). I would prefer to see the old option of importing existing user records. Found it a bit confusing when it told me it had 'created' the user I used. Second, it would be nice to have a prompt to eject the first CD. On this machine at least, the installer simply sat until I ejected the first CD and inserted the second. It would be nice to either have it ejected when necessary, or prompt the user to eject and insert the second CD. Third, when the install completed, the Reboot button was greyed out. I had to push 'back', at which point the reboot button became active and I was able to select it. Forth, I made the mistake of minimising the installer while the install was in progress. When I brought it back up, it was essentially blank, except for the 'development team' scrolling list. A bit off-putting. It did come back when then next stage of the install started, but a means to refresh the display would be useful. After install, I had the same video problems I've been having with all the other alphas. After the login prompt, the screen goes white, then goes grey, and I'm left with a mouse cursor and nothing else. The only way to fix it is to use CTRL-ALT-BackSpace to kill X, then select the 'safe KDE' option. After that, the KDE desktop comes up ok. Well, sort of ok.... This install was to my T61 - Intel graphics, native resolution is 1280x800. Unfortunately, all the more recent alphas have come up in 1024x768 and not offered any higher resolution. I have to su, use init 3 and run Vasm to fix the problem. I still can't use any of the screen effects, even once the correct driver is loaded and working. I needed Vasm for another reason as well. During the first stage of the install, I selected a generic 104 key keyboard, UK layout. However, on first boot to the installed system, I have a US layout in both X and console. While I can fix most of these problems, I doubt that many in the target user base will have the necessary expertise to do so. I'm not a fan of Kmail, but the version with the new KDE seems to be badly broken. It failed to log in to my ISP to send mail (even though it is set up in exactly the same way as Seamonkey is set in 6.0 Standard). It then said the message I had entered would be left in outgoing. Only it wasn't. It seems to have eaten the outgoing message. I could not find any trace of it at all.... Its getting a lot better, but there is still a long way to go, I think.... paul |
|
From: M0E L. <m0...@gm...> - 2009-09-02 17:25:04
|
You should be geting a dialog box asking you to insert the second cd. I cannot automate the eject action because it's not supported on all devices, and it's a hit and miss even on those that do support it. The screen refreshing problem is a known bug for ages... for some reason, and I'm willing to bet it's due to an old GTK the screen does not refresh instantly... it takes a while to refresh... I can't find a way to fix that As far as the reboot button at the end goes. If the button is grayed out it means there is still some activity going on in the background and it is not safe to reboot yet. there are scripts runnin in the background to prepare the system for initial boot. The process is normally finished by the time you reach the end of the installer wizard, but if it is not, it should be telling you to wait for the process to finish, the button will be enabled when it is safe to reboot. |
|
From: Paul M. <pa...@wa...> - 2009-09-02 19:01:15
|
M0E Lnx wrote: > You should be geting a dialog box asking you to insert the second cd. > I cannot automate the eject action because it's not supported on all > devices, and it's a hit and miss even on those that do support it. Ok, didn't realise that. Maybe the message could be more explict? > The screen refreshing problem is a known bug for ages... for some > reason, and I'm willing to bet it's due to an old GTK the screen does > not refresh instantly... it takes a while to refresh... I can't find a > way to fix that Fair enough. > As far as the reboot button at the end goes. > > If the button is grayed out it means there is still some activity > going on in the background and it is not safe to reboot yet. there are > scripts runnin in the background to prepare the system for initial > boot. Hmm. Well, I left it for several minutes. All I had was an empty window headed "Your Vectorlinux installation", no sign of hard drive activity. I'll try again and see if waiting longer fixes it. > The process is normally finished by the time you reach the end of the > installer wizard, but if it is not, it should be telling you to wait > for the process to finish, the button will be enabled when it is safe > to reboot. Nothing about waiting. And it looked as though it was finished. At present, the keyboard selection stuff at the start of the install doesn't seem to do much (unless it affects the keyboard layout during the install?). At the end of the install, even though I had selected UK layout, I still had US layout. :) Its getting there, but still a way to go, I think.... paul. |
|
From: M0E L. <m0...@gm...> - 2009-09-02 19:11:47
|
Yeah... for some reason the idling message is not showing up on time... I will have to fix that |
|
From: Newt <gen...@gm...> - 2009-09-02 19:17:16
|
Hello All, Here are my notes on 1.21: -wifi-rader service fails -How can someone check that their options chosen in the installer are preserved to installed system? (Language/keyboard/mouse/etc). Based on Paul's comments, I suspect they are not carried over? KDM: -no users have images, but I did not specify any during install either. root does not have an image in 1.21. KDE: -Nepojuk Strigi is still somewhat verbose. -Played with Desktop vs Folder view and themes. I had not tried the KDE menu yet, but after playing with these settings I was not able to access the KDE menu (i.e. I click on it and the button would just blink - no menu popped up) -There are advantages and disadvantages to Desktop vs Folder views. I like both for different reasons. Folder view is more typical and what people are used to. Desktop is more eye candy and clean looking and new. The best option would be to allow users to choose between one or the other on first entering KDE with a graphical and verbal description of some of the features of each. Of course, if this feature is not already built by the KDE people then it's basically not an option. -The 'blend' theme, with it's bluish color scheme, blends well (no pun intended) with the VL blue color scheme. -Shortcut settings did not start for me (from upper-right menu); this was after playing with settings above -On 2nd boot, I discovered that the KDE menu "breaks" after changing themes. It works before changing themes and after it does not. Maybe it's just me? Cheers, newt |
|
From: M0E L. <m0...@gm...> - 2009-09-02 19:26:14
|
Check your user's .bashrc to make sure your keyboard model and map as well as LANG are preserved. keep in mind that your desktop will only follow the LANG variable if you chose to install the language package that matches your selection. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X