Menu
▾
▴
vectorlinux-devel
|
From: uel a. <ue...@gm...> - 2009-08-25 05:00:06
|
New ISO's new kde pkgs new installer ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17.iso ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17-CD2.iso > > vectorlinux:$ md5sum VL6.0-SOHO-A1.17.iso 470aaed434786ef543f79fe0c5ebb965 VL6.0-SOHO-A1.17.iso vectorlinux:$ md5sum VL6.0-SOHO-A1.17-CD2.iso 991d0d49974b88ee0b20f973bcab0853 VL6.0-SOHO-A1.17-CD2.iso |
|
From: Newt <gen...@gm...> - 2009-08-25 18:43:30
|
Hello All, Here are my notes on 1.17, install r733 (I think): >> Bootloader Installation: >> -The bootsector option is still only offering the bootsector of my /home (sda2) >> directory, rather than my / directory (sda1). Aside from that, the bootsector >> option fails to install. >> -I like the added message about clicking back to try again on a failed bootloader >> installation, however this message is only presented when Grub fails to install. >> If you could implement the same message when lilo fails then that should be >> sufficient. >> -When installing grub, even though it only shows one entry that will be added to >> the boot options it adds the 'recovery mode' boot option by default. Lilo does >> not do this and it would be nice if it did to give the user a way back into a TUI >> interface in case they borked their xorg/gui. >> -When clicking back after a failed installation the bootloader configuration >> screen is still frozen. The 'Saving Configuration...Please Wait' message is >> still display, and nothing below that message can be edited. However, the user >> CAN chose a different location to install the bootloader and switch between >> loaders so, effectively, the bootloader installation can still take place. It >> would be nice to have this screen reset to default when going back to it. >> >> System Administrator Account: >> -There's still some kind of wierdness going on with the 'Next' button. There >> are still instances where it will enable (or stay enabled) allowing the user to >> bypass root password creation. However, it's slightly different that before. >> Let's see if I can describe what I'm seeing: >> -User clicks 'next' from regional settings and gets to system administrator >> account page. The 'next' button initially disables for about 1/2 second, but >> then it enables and will stay enabled until the mouse is moved into the System >> Administrator Account region. You can however move you mouse along the >> horizontal lower button plane, up the process overview area, and across the >> vectorlinux banner and the 'next' button will stay enabled. I hope that all >> makes sense. >> >> First boot: >> -wifi-rader service fails to start (perhaps a conflict with another service? e.g. wicd) >> -VasmCC start, however when I simply click on 'UTILITIES' I get a fatal error: >> [-1]Unable to load image. Mfiles.?.0 >> -VasmCC - Filesystem/Bootloader only offers lilo - needs updated to include grub >> -VasmCC - ALSASound doesn't seem to do anything - or does it just take a really long time? >> -VasmCC - Hardware Config message cannot be read (the lower 3/4 is cut off) >> -VasmCC - SAMBA Networking - Should we start Samba SWAT? Yes. Failed, cannot start SWAT. >> -VasmCC - CUPS Printing - Same deal as Samba SWAT. Tries to start it but cannot - failed. >> -Ooo - Extension Manager problem persists Hope this helps. Again, mostly minor things. No show stoppers by any means, just some normal bugs - most are minor but a couple are bigger than that. Still a great release and speedy too (pun intended). Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Monday, August 24, 2009, 10:59:48 PM, you wrote: ua> New ISO's ua> new kde pkgs ua> new installer ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17.iso ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17-CD2.iso >> >> vectorlinux:$ md5sum VL6.0-SOHO-A1.17.iso ua> 470aaed434786ef543f79fe0c5ebb965 VL6.0-SOHO-A1.17.iso ua> vectorlinux:$ md5sum VL6.0-SOHO-A1.17-CD2.iso ua> 991d0d49974b88ee0b20f973bcab0853 VL6.0-SOHO-A1.17-CD2.iso |
|
From: M0E L. <m0...@gm...> - 2009-08-25 19:31:08
|
Newt, our of curiosity, are you using xfs as a filesystem for your target / ? bootsector is not an option when you use xfs. On the other issues you're having, could you fill out bug reports at http://vlcore.vectorlinux.com/trac/vinstall please? These get lost in my quite populated inbox so I keep forgetting about them. If you do not have an account yet @ the installer devel page, you should sign up. |
|
From: Newt <gen...@gm...> - 2009-08-27 16:32:38
|
Hello, Any relevant installer issues will be filed in vlcore bugs: >> -language, keyboard layout, mouse type screen is gone. I think it was a nice addition. If it >> can be added back that would be nice;. >> >> Bootloader: >> The 'Saving Configuration...Please Wait' message only appears once the bootloader has been >> installed rather than the moment the button is clicked. The same is true for the lower half >> of the screen - it only disables once the bootloader is successfully installed. This should >> be adjusted because it's a nice informational message and indicates something is happening. >> >> Bootloader: >> Lilo Bootsplash Medium fails to install because it leaves the 'vga =' line empty like that. >> Maybe it should be 'vga = 788' (800x600 64k) >> >> Bootloader/Bootsector: >> -bootloader lists correct bootsector (hda1), but fails to install lilo or grub. >> -The lilo failed message reads: "Unable to successfully install LILO on" (seems either >> incomplete or has the extra word 'on') >> >> LILO bootsector help: >> I chrooted to /mnt/target and looked at lilo.conf after the failed bootsector installation. >> I contains an empty string where the boot device is specified (i.e. 'boot ='). I tried >> installing lilo with this and it gave an error at or above line 7. I then removed that line >> from lilo.conf and tried installing lilo again and it worked. I don't know if this is the >> proper fix but it works for installing to /dev/sda1. >> >> GRUB bootsector help: >> I chrooted to /mnt/target. I attempted a 'grub-install /dev/sda' and it completed with no error >> reported. I then tried 'grub-install /dev/sda1' and it gave this message: >> grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a >> BAD idea. >> grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by >> using blocklists. However, blocklists are UNRELIABLE and its use is >> discouraged. >> grub-setup: error: If you really want blocklists, use --force. >> I then tried a 'grub-install --force /dev/sda1' and it gave the same 'warn' message but completed >> successfully. >> >> -I ended up going with GRUB installed to bootsector and LILO installed to MBR. I will attempt to >> chainload them to test the GRUB installation. I've never tried chainloading like this using lilo so >> we'll see. >> >> Root password: >> -Everything seems to be working correctly. I cannot bypass this. AWESOME!! >> >> >> First boot: >> -No bootsplash - I see the scrolling text (tui) boot with black background. >> -wifi-radar service fails Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Monday, August 24, 2009, 10:59:48 PM, you wrote: ua> New ISO's ua> new kde pkgs ua> new installer ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17.iso ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17-CD2.iso >> >> vectorlinux:$ md5sum VL6.0-SOHO-A1.17.iso ua> 470aaed434786ef543f79fe0c5ebb965 VL6.0-SOHO-A1.17.iso ua> vectorlinux:$ md5sum VL6.0-SOHO-A1.17-CD2.iso ua> 991d0d49974b88ee0b20f973bcab0853 VL6.0-SOHO-A1.17-CD2.iso |
|
From: uel a. <ue...@gm...> - 2009-08-27 16:43:45
|
newt, does this installer work with your nvidia/kvm box? On 8/27/09, Newt <gen...@gm...> wrote: > > Hello, > > Any relevant installer issues will be filed in vlcore bugs: > > >> -language, keyboard layout, mouse type screen is gone. I think it was a > nice addition. If it > >> can be added back that would be nice;. > >> > >> Bootloader: > >> The 'Saving Configuration...Please Wait' message only appears once > the bootloader has been > >> installed rather than the moment the button is clicked. The same is > true for the lower half > >> of the screen - it only disables once the bootloader is successfully > installed. This should > >> be adjusted because it's a nice informational message and indicates > something is happening. > >> > >> Bootloader: > >> Lilo Bootsplash Medium fails to install because it leaves the 'vga > =' line empty like that. > >> Maybe it should be 'vga = 788' (800x600 64k) > >> > >> Bootloader/Bootsector: > >> -bootloader lists correct bootsector (hda1), but fails to install > lilo or grub. > >> -The lilo failed message reads: "Unable to successfully install LILO > on" (seems either > >> incomplete or has the extra word 'on') > >> > >> LILO bootsector help: > >> I chrooted to /mnt/target and looked at lilo.conf after the failed > bootsector installation. > >> I contains an empty string where the boot device is specified (i.e. > 'boot ='). I tried > >> installing lilo with this and it gave an error at or above line > 7. I then removed that line > >> from lilo.conf and tried installing lilo again and it worked. I > don't know if this is the > >> proper fix but it works for installing to /dev/sda1. > >> > >> GRUB bootsector help: > >> I chrooted to /mnt/target. I attempted a 'grub-install /dev/sda' and > it completed with no error > >> reported. I then tried 'grub-install /dev/sda1' and it gave this > message: > >> grub-setup: warn: Attempting to install GRUB to a partition > instead of the MBR. This is a > >> BAD idea. > >> grub-setup: warn: Embedding is not possible. GRUB can only be > installed in this setup by > >> using blocklists. However, blocklists are > UNRELIABLE and its use is > >> discouraged. > >> grub-setup: error: If you really want blocklists, use --force. > >> I then tried a 'grub-install --force /dev/sda1' and it gave the same > 'warn' message but completed > >> successfully. > >> > >> -I ended up going with GRUB installed to bootsector and LILO installed > to MBR. I will attempt to > >> chainload them to test the GRUB installation. I've never tried > chainloading like this using lilo so > >> we'll see. > >> > >> Root password: > >> -Everything seems to be working correctly. I cannot bypass this. > AWESOME!! > >> > >> > >> First boot: > >> -No bootsplash - I see the scrolling text (tui) boot with black > background. > >> -wifi-radar service fails > > Cheers, newt > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > Monday, August 24, 2009, 10:59:48 PM, you wrote: > > ua> New ISO's > ua> new kde pkgs > ua> new installer > ua> > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17.iso > ua> > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.17-CD2.iso > > >> > >> vectorlinux:$ md5sum VL6.0-SOHO-A1.17.iso > ua> 470aaed434786ef543f79fe0c5ebb965 VL6.0-SOHO-A1.17.iso > > ua> vectorlinux:$ md5sum VL6.0-SOHO-A1.17-CD2.iso > ua> 991d0d49974b88ee0b20f973bcab0853 VL6.0-SOHO-A1.17-CD2.iso > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Newt <gen...@gm...> - 2009-08-27 17:46:32
|
Hello Uel, No 1.17 does not work with my nvidia/kvm box. I think the issue is more related to the X video driver (i.e. vesa) than anything else. I will try this system again tonight directly connected (i.e. no kvm) to see if there's any change. I also notice 1.18 is ready so I'll try that one tonight. Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Thursday, August 27, 2009, 10:43:34 AM, you wrote: ua> newt, ua> does this installer work with your nvidia/kvm box? |
|
From: Sergey P. <fa...@gm...> - 2009-08-27 21:22:01
|
Hi, installing 117 now. Couldn't install LILO properly. The "Reboot" button on selecting services screen has transferred me to "details of your vectorlinux install". I pressed "Back" and pressed "Reboot" again and it succesfully rebooted. |
|
From: M0E L. <m0...@gm...> - 2009-08-27 21:32:31
|
1.18 is up there... and new installer also. try the new ISO and update the installer in it by refreshing the svn branch in it. Thanks |
×
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