vectorlinux-devel

[Vectorlinux-devel] soho-1.30

[Masta M. <mas...@gm...>]

1.30 r-815
This time I was able to get past the "no OS found" issue. Good job on fixing
that, and thanks.
  A new issue arrives with both LILO and GRUB.
LILO:
 Seems during installation it is installed successfully. Reboot the machine
and you do get a LILO screen to select OS. Choose the default and it will
boot showing the verbose screen (graphical with scrolling text) instead of
the silent mode (progress bar). Then it gets booting so far and ends up
with,
"The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2 filesystem
(and not swap or ufs or something else), then the superblock is corrupt, and
you might try running e2fsck with an alternate superblock:  ..."
   and so on. We're also presented with option to enter root password to run
fsck and make fixes, or use ctrl-d to proceed with normal startup. Ctrl-d
just reboots and we simply cycle back to the error. I've tried manual fix,
no luck there.

GRUB:
          Splash boots in proper silent mode and progressbar shows. That is
until we get to the same superblock / root-filesystem  error.

Boot Splash:
I can see the issue of the text on the left side not fitting into the image
window properly. I'll work this  :) .

Re: [Vectorlinux-devel] soho-1.30

[Uel A. <ue...@gm...>]

This is the udev error we talked about in IRC
The only way to fix in 1.30 is to manually delete rc.udev and  
reinstall the udev package

Fortunately there is a delta to 1.31 up already



On Sep 18, 2009, at 3:16 AM, Masta MCF <mas...@gm...> wrote:

> 1.30 r-815
> This time I was able to get past the "no OS found" issue. Good job  
> on fixing that, and thanks.
>   A new issue arrives with both LILO and GRUB.
> LILO:
>  Seems during installation it is installed successfully. Reboot the  
> machine and you do get a LILO screen to select OS. Choose the  
> default and it will boot showing the verbose screen (graphical with  
> scrolling text) instead of the silent mode (progress bar). Then it  
> gets booting so far and ends up with,
> "The superblock could not be read or does not describe a correct  
> ext2 filesystem. If the device is valid and it really contains an  
> ext2 filesystem (and not swap or ufs or something else), then the  
> superblock is corrupt, and you might try running e2fsck with an  
> alternate superblock:  ..."
>    and so on. We're also presented with option to enter root  
> password to run fsck and make fixes, or use ctrl-d to proceed with  
> normal startup. Ctrl-d just reboots and we simply cycle back to the  
> error. I've tried manual fix, no luck there.
>
> GRUB:
>           Splash boots in proper silent mode and progressbar shows.  
> That is until we get to the same superblock / root-filesystem  error.
>
> Boot Splash:
> I can see the issue of the text on the left side not fitting into  
> the image window properly. I'll work this  :) .
>
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9&#45;12, 2009. Register  
> now&#33;
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel