VectorLinux

The nuts and bolts => Installation & Updates => Topic started by: joel2007 on May 25, 2010, 11:09:19 pm

Title: [Solved] Could not find ramdisk image: /isolinux/init.gz
Post by: joel2007 on May 25, 2010, 11:09:19 pm
I followed the instructions here: http://vectorlinux.osuosl.org/docs/vl60/manuals/vl6_installation_guide_en.html
I cannot get to The Graphical (GUI Based) Installation Process. I always get the message:
Could not find ramdisk image: /isolinux/init.gz
I have check MD5 checksum. Match.
My computer: Dell GX260 2.4Ghz 512mb ram. Windows XP pro.
Please help?
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: sledgehammer on May 26, 2010, 05:37:27 pm
Thanks, Joe12007,
I have installed VL6.0 quite a few times and did not know of the instruction sheet.

Rather, I burn the LV 6.0 iso to a cdrom off the Vector site.

Then I put it in the cdrom drive and follow the onscreen prompts.  I generally type "linux" at the first prompt, as I prefer the old non-graphical installer.

As I have never dual booted, I can't help you there.

JOhn
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: nightflier on May 26, 2010, 06:23:04 pm
Please describe the procedure you followed (ISO install, bootable CD..).
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: joel2007 on May 26, 2010, 07:20:23 pm
Please describe the procedure you followed (ISO install, bootable CD..).
VL 6.0 Light Edition
http://vectorlinux.com/downloads
Burn to CD.
Restart computer. Boot from CD.
Then I got this:
Could not find ramdisk image: /isolinux/init.gz
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: retired1af on May 26, 2010, 07:50:27 pm
Sounds like a faulty burn. I'd recheck the MD5 sums, ensure they match, then burn at a slower speed.
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: sledgehammer on May 26, 2010, 08:54:51 pm
I use VL light with Pentium 2 machines, with much less than 512 in memory.  Unless there is something that drags the system on dual boot (perhaps more memory is needed on dual boot), I suggest you try the regular VL 6.0.  It is a wonderful distribution that should run fine on your machine. Certainly, unless the dual boot causes problems, it would run find on your machine.  I see no reason you are having problems unless, as retired1af says, there is something wrong with your download. 

Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: joel2007 on May 26, 2010, 11:20:37 pm
Sounds like a faulty burn. I'd recheck the MD5 sums, ensure they match, then burn at a slower speed.
MD5 sums matched. I use ImgBurn. I burn it at 1x speed. I have tried it on 2 cds Verbatim brand. Same thing happens.
Note: I have also tried to boot it on usb stick. Same thing happens.
I did search around. I found this thread:
http://forum.vectorlinux.com/index.php?topic=11594.0
Can you confirm and give a solution?
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: nightflier on May 27, 2010, 05:37:01 am
VL6 Light is pretty old-fashioned and geeky. It does not have a GUI installer.

I agree with sledgehammer that you should try another version. Your machine is plenty fast to run VL Standard. You may also give KDE-Classic-Live a try.
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: joel2007 on May 27, 2010, 11:36:38 am
The VL Standard is XFCE or GNOME?
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: retired1af on May 27, 2010, 11:38:47 am
Gnome? Perish the thought!  ;D  Standard is Xfce.
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: joel2007 on May 27, 2010, 02:57:56 pm
The VL 6 Standard works.
Thanks.
Title: Re: Could not find ramdisk image: /isolinux/init.gz
Post by: sledgehammer on May 27, 2010, 08:20:00 pm
If you haven't already done so, when time permits, its a good idea to get on gslapt, then update, then mark all records, then execute.  This will update your system.  Later on, you may or may not want to keep updating generically, as above.  Many, after the first update, only update specific programs.