VectorLinux

Please login or register.

Login with username, password and session length
Advanced search  

News:

Visit our home page for VL info. For support and documentation, visit the Vector Linux Knowledge Center or search the Knowledge Center and this Forum using the search box above.

Pages: 1 ... 6 7 [8] 9 10
 71 
 on: January 23, 2017, 04:30:47 pm 
Started by roarde - Last post by retired1af
nano

 72 
 on: January 23, 2017, 04:24:05 pm 
Started by Hairyloon - Last post by Hairyloon
A new image made no difference to "install32".  Odd: I'm sure it worked first time around.
Trying again to install.  Is it worth trying to do anything through the command prompt after the install stops?
Perhaps try to finish the job, install the bootloader, or check the system in some way.

 73 
 on: January 23, 2017, 01:05:15 pm 
Started by Hairyloon - Last post by Hairyloon
First issue, booting from the CD (?) and continuing from HDD requires you to know where you installed to. The default install is to "/dev/sda1", but it could be different. If you're sure you got that entry right, then the installation is corrupt.
Reasonably sure, but to be clear, it does do a lot of stuff before the error message...

Quote
It would not be unusual for an old optical drive to not work reliably all the time. A fingerprint on the disc can be enough to confuse it.

It's a USB stick: this one doesn't have an optical drive. I think I'll try redoing the image next.

Quote
I'm not familiar with the technical term "petunia", but I assume you installed using the text installer, by typing "install" on the first screen?
Petunia in this instance means bizarre and colourful, but the term has wider usage. 
I tried "install32" on the assumption that that was for a 32 bit machine, but that's now giving the error message.
If I type "install", then it runs an installer with the results as discussed...
Quote
The installer needs at least 256M of RAM and 4G of hard drive space, are those specs met?
That much and more! :D

 74 
 on: January 23, 2017, 09:42:47 am 
Started by Hairyloon - Last post by nightflier
I agree with you on not wanting to throw away working hardware. :)

First issue, booting from the CD (?) and continuing from HDD requires you to know where you installed to. The default install is to "/dev/sda1", but it could be different. If you're sure you got that entry right, then the installation is corrupt.

It would not be unusual for an old optical drive to not work reliably all the time. A fingerprint on the disc can be enough to confuse it.

I'm not familiar with the technical term "petunia", but I assume you installed using the text installer, by typing "install" on the first screen?

The installer needs at least 256M of RAM and 4G of hard drive space, are those specs met?

 75 
 on: January 23, 2017, 09:05:34 am 
Started by Hairyloon - Last post by Hairyloon
The first message tells us that either the installation is corrupt, or not on the specified device.
How can I find which?

Quote
Second message indicates a bad install medium, it can not read the needed files on the disc (or USB device).
It worked before. :?
I do notice that the error refers to isolinux where the directory on the disk is ISOLINUX. Could that be a part of the problem?
Quote
Which version of VL is it you are using?
7.1 Light.
Quote
Would you give us the specs for the computer you are installing to?
It's a Dell X200 series laptop with an 800MHz PIII(?) processor... Probably not worth the trouble, but I don't like to throw things away if they work.  :-[

 76 
 on: January 23, 2017, 08:50:47 am 
Started by Hairyloon - Last post by nightflier
Quote
end Kernel panic - not syncing: VFS: Unable to mount rootfs on unknown-block(8,1)
random: nonblocking pool is initialised

And it sits there flashing lights...

I'll try installing again while I wait for a reply, in case I did something silly last time...

Or maybe I won't: it says
Quote
Could not find kernel image: /isolinux/kernel/sata32

The first message tells us that either the installation is corrupt, or not on the specified device.

Second message indicates a bad install medium, it can not read the needed files on the disc (or USB device).

Which version of VL is it you are using?
Would you give us the specs for the computer you are installing to?

 77 
 on: January 23, 2017, 06:12:24 am 
Started by Hairyloon - Last post by Hairyloon
Quote
end Kernel panic - not syncing: VFS: Unable to mount rootfs on unknown-block(8,1)
random: nonblocking pool is initialised

And it sits there flashing lights...

I'll try installing again while I wait for a reply, in case I did something silly last time...

Or maybe I won't: it says
Quote
Could not find kernel image: /isolinux/kernel/sata32

 78 
 on: January 23, 2017, 05:35:00 am 
Started by roarde - Last post by M0E-lnx
My top 3 in order of preference.

micro
vi/vim
nano

 79 
 on: January 22, 2017, 01:33:12 pm 
Started by StrayBit - Last post by StrayBit
using smbpasswd, guestpc without a password does not work!  bruce with a password works but I can only access my home account!  Until I removed the Force User in Samba.config.
Thanks, Nightflier.

Oh! And changing a parameter in the repeater allowed my to access internet.

 80 
 on: January 22, 2017, 06:39:49 am 
Started by roarde - Last post by bigpaws
Vi/Vim

Pages: 1 ... 6 7 [8] 9 10