January 26, 2015, 04:09:23 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: 1 ... 4 5 [6] 7 8 ... 10
 on: December 29, 2014, 03:57:24 am 
Started by uelsk8s - Last post by nightflier
Also, since installing SW14.1 and 7.1-RC3.1, I get a message that my battery is low and have to press F1 to continue!  This is a tower - no battery.  Booting to cd does not give that message.  Nor did previous installations.

That is referencing the bios battery on your motherboard. It is usually the size of a coin and snaps in/out of a spring loaded holder. It is there to maintain your bios settings when grid power is not available.

 on: December 28, 2014, 09:56:41 pm 
Started by User9 - Last post by User9
If I install the 7.1 RC, how difficult will it be to upgrade/update anything to the final release version if I have a release candidate installed?  Not sure if this is the right area of the forum.  Thanks in advance. 

 on: December 28, 2014, 04:42:01 pm 
Started by uelsk8s - Last post by roarde
See if reformatting swap (again as swap) helps. This will have the unwanted side effect of changing its UUID. Allow for that. I'd reference it by /dev/ for right now.

 on: December 28, 2014, 04:29:01 pm 
Started by uelsk8s - Last post by StrayBit
Using 7.0-LIVE, I copied the 7.1-rc3.1.iso and mdsum....txt from Win7 to my iso partition where I could check it  - it matched.
Ran the memtest from the LIVE cd - 1014M passed with no errors.
What can I do to get it to accept my passwords?  I haven't reinstalled yet but I could to allow the animation.

Also, since installing SW14.1 and 7.1-RC3.1, I get a message that my battery is low and have to press F1 to continue!  This is a tower - no battery.  Booting to cd does not give that message.  Nor did previous installations.

Presently, I have to use the cd to boot into 7.0.  I hate those USID labels!  And live desktop does NOT tell me what the various partitions are just their size!  (That's when I didn't catch it to mount them at startup.)

 on: December 28, 2014, 12:20:55 pm 
Started by uelsk8s - Last post by roarde
Sorry if I didn't catch you before a reinstall. I suggest using the bootsplash as you apparently had been doing, I'm pretty sure any difference between using splash and not has been repaired. But if it hasn't, the difference would favor bootsplash and the initrd it uses.

 on: December 28, 2014, 11:47:45 am 
Started by uelsk8s - Last post by StrayBit
Thanks for the link, nightflier.  Sorry for my abbreviation - I was installing rc3.1.

 on: December 28, 2014, 11:23:16 am 
Started by uelsk8s - Last post by sledgehammer
Don't know much about this complicated discussion.  But I loaded VL64-7.1-STD-RC3.1 on my samsung rf511, via unetbootin, and had no problems. The onboard wifi card worked out of the box.  Great distro!  I didn't reformat home and all my files are there.  There was a file missing when I loaded libreoffice and lyx doesn't work yet.  I will look into that as time permits.


 on: December 28, 2014, 10:38:16 am 
Started by uelsk8s - Last post by roarde
Thank you for your thoughts, pekka. I know it helps a lot to have a fresh take on install from someone who can express it so well.

UEFI and easier access to GPT were discussed, but the time that would have been spent on them had to be skipped to get this already late release out the door. GPT is available in the shell at install time: parted. I'm used to trying fdisk first, then cfdisk. Being used to those, I look at parted differently as I think you do. But I tried to put new eyes on and took another look. Since the word "help" is indeed a working command, I begin to think parted might be the best choice for those who haven't partitioned from the command line before; and not at all hard for previous users of other tools to pick up. But yes, a tip to its availability at the right point would be nice. UEFI and easier access to GPT will surely be handled in later releases.

Which brings me to one of my own questions: Does the gui installer already handle GPT if the table is already present? I have no way to check.

I have no doubt that VL releases will come to handle GPT and UEFI as automatically as is possible, just not this time.

RAID brings up another question from me: Wasn't VL set up to install to RAID at one time?
(not that i'd have anything to do with its absence)

Can't click "Post" without saying thank you once again, pekka.

 on: December 28, 2014, 07:45:02 am 
Started by uelsk8s - Last post by pekka
I was sent here by the guys at #vectorlinux channel in  freenode.
I've tested VL64-7.1-STD-RC3.1, and have some feedback about the text-installer.
The installation utilized an USB-flash pen, a desktop pc with a BIOS, and a new server with UEFI.

1) UEFI:
When trying to install VL on a system with new UEFI the installer get dropped to a root shell, see attached picture.
Ctrl-Alt-F1/F2/F3 gave 3 root shells, but no installer.  I dont know if it is the intention to have 3 virtual consoles in the installer. Never the less, I did like the idea. The availability of virtual consoles is a good thing. They are power tools for experienced users who do not need an X-session. But what is the command to start the installer from a root shell?
In the end I did overcome the UEFI install issue by installing VL on my desktop pc which have a BIOS, and then put the disk back in the server. VL did then boot without problems on the server.

2) BIOS:
With the BIOS, the installer start the installation process without any problem. The installer apparently run on the first virtual console. When testing the other 2 consoles, Ctrl-Alt-F2 and Ctrl-Alt-F3, I get 2 additional text-install processes. However the root shells are available by using the "back" button in the first page of the text-installer. I think there should be some information about the availability of 2 additional consoles in the text in the first page. Root consoles are a very useful feature for power users.

3) SSD:
The desktop pc is using a SSD as a system disk,  and the disk is set up for multibooting. That imply VectorLinux will share the SSD with other operating systems. However, I use GUID Partition Table (GPT), which is a better choice for for a SSD. The text-installer come with standard cfdisk (linux fdisk) as partition tool. Unfortunately cfdisk lack support for GPT. I think VectorLinux should add support for GPT, at least in the 64-bit version which I assume will also be used on newer hardware. A good tool, which operate in the same way as linux fdisk is GPT fdisk,
It would be nice if GPT fdisk was availale as an option in the "Disk Partition" page.

4) Installing on RAID? - Some additional thoughts:
I did the test on quite new hardware, but sometimes I do install VL on old hardware. In my eyes, given the fact that VectorLinux run well on old hardware, and has a slower release cycle than compareable distros, make Vectorlinux a very good choice for a server OS. Old desktop pc's can get a second life as servers, and I avoid reinstall too often. However, running a server on old HW is a risk. Sooner or later the HW will fail. If I reuse old HW this way, I always use raid arrays. Mirrored raid give an extra layer of security when old mechanical disks fail. And they do fail.
The linux kernel do autodetect raid arrays, and raid arrays were available as an install option in the text-installer. However, when I did install VL on a mirrored raid array (md126), VL did fail to boot. LILO boot loader did show an option to boot md126, but booting md126 gave a kernel panic. Both LILO and GRUB2 can be configured to boot an OS installed on a raid array, and some distros offer this option "out of the box" in the installer. However, with slackware you need to chroot, do a mkinitrd and make sure the necessary kernel modules are loaded, configure and reinstall bootloader from the chroot environment, etc. This kind of hacking take time.

I think a working "out of the box" option to "install VL on raid" in the text-installer would be a great feature. This feature will save users a lot of time and kernel-woodoo. And if I don't remember wrong, with this feature VectroLinux will be the only Slack-based distro, and maybe one of the few non-systemd distros, which have this feature working "out of the box" in the installer. Maybe a feature worth considering for VectorLinux.


 on: December 26, 2014, 08:54:03 am 
Started by uelsk8s - Last post by nightflier
RC3 is outdated. RC3.1 download and md5sum links are here:

Pages: 1 ... 4 5 [6] 7 8 ... 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!