Jump to content











Photo
- - - - -

[Solved] Latest Sardu: lastest Avira fails to load


  • Please log in to reply
6 replies to this topic

#1 dasanco

dasanco
  • Members
  • 2 posts
  •  
    United States

Posted 13 December 2010 - 09:40 AM

SARDU_2.0.1 beta 2
Avira Rescue Disk v.20101212191958

Self check failed! The File failed the check. Press OK to shutdown the system.
< OK >

Anyone else getting this?

#2 davidecosta

davidecosta

    Silver Member

  • Developer
  • 678 posts
  • Location:Sardinia
  •  
    Italy

Posted 13 December 2010 - 10:28 AM

SARDU_2.0.1 beta 2
Avira Rescue Disk v.20101212191958

Self check failed! The File failed the check. Press OK to shutdown the system.
< OK >

Anyone else getting this?



The thread of beta version is this. WHy open other threads? :cheers:
Now i make a checkup of avira. Is with usb or iso?


Edit,
Founf this error with USB, now ....works to solve it

Edit two

Solved in next beta

#3 dasanco

dasanco
  • Members
  • 2 posts
  •  
    United States

Posted 13 December 2010 - 06:13 PM

The thread of beta version is this. WHy open other threads? :cheers:
Now i make a checkup of avira. Is with usb or iso?


Edit,
Founf this error with USB, now ....works to solve it

Edit two

Solved in next beta


Thank you for your hard work and kind words!

It is a great tool-set

#4 davidecosta

davidecosta

    Silver Member

  • Developer
  • 678 posts
  • Location:Sardinia
  •  
    Italy

Posted 13 December 2010 - 10:36 PM

Thank you for your hard work and kind words!

It is a great tool-set



The problem was a folder who sardu don't extracted in the new iso

#5 Darkwing4296

Darkwing4296
  • Members
  • 2 posts

Posted 13 January 2011 - 10:39 AM

First I would like to join in in saying that Sardu is a great tool. :hi:

Regarding the Avira issue, I encountered another problem and figured out a solution, which I would like to share with you.

I'm working with rather old PC assemblies, that have a 640x480 touch screen attached and only 512MB of RAM.

Older Avira Rescue System revisions worked ok, except for the fact that the update button was outside the visible screen area, so I usually switched to the console and updated the virus definition files there. Often I also started the virus scan from the command line as well.

Using the new Avira Rescue System from early this week, I briefly see the Avira GUI (after quite a long initialization phase), then the screen turns black.

I have seen this sometimes with earlier versions as well, but then I could press CTRL-ALT-BACKSPACE to get to the console and perform the update and scan operations on the command line. Doing this with the latest Avira, it seems to restart the X server almost immediately, causing the same black screen in addition to an "insufficient memory" message.

The original Avira ISO supports a "No GUI" boot option, that is not shown on the boot screen, I think, and that is not listed when running Avira from Sardu.

So I did add the respective boot section to my /extra/extra.cfg:

#
label Anti^Vir Rescue System (No GUI)
kernel /antivir/vmlinuz
append nofb initrd=/antivir/initrd.gz ramdisk_size=108178 root=/dev/ram0 rw console=/dev/vc/4 av-nogui


Unfortunately, not all initialization steps are performed automatically when using the No GUI option, so I added a short script, based on the one provided with the Avira Rescue system and added the update and scan commands as well, so I only need to run one command after booting.

I placed the script in /extra and named it "RunAvira". (I'm not sure about what some of the lines do exactly, since I'm not very familiar with Linux, but it seems to work alright).

So, after booting Avira (No GUI ), I use

sh /media/Disks/E\:__\(3.7G)/extra/RunAvira

with "E\:__\(3.7G)" being my thumb drive (replace with the drive letter of your Sardu drive)

It's content is this:

#!/bin/ash
DEBUG=false

export DBGTTY=/var/log/bootup.log

if echo "$@" | grep -q -e '--debug' ; then
DEBUG=true
fi

/bin/network &
/bin/get_vdf
if [ "0" != "$?" ] ; then
exit 1;
fi

/usr/bin/avupdate

/AntiVir/scancl --allboot --allfiles --scaninarchive --nolinks --colors /media/Devices/hda*

exit 0;
;;

esac


I hope this is of use to other people as well.

Maybe the Sardu/Avira menu could be modified to list the No GUI option natively?

#6 davidecosta

davidecosta

    Silver Member

  • Developer
  • 678 posts
  • Location:Sardinia
  •  
    Italy

Posted 13 January 2011 - 12:39 PM

First I would like to join in in saying that Sardu is a great tool. :hi:

Regarding the Avira issue, I encountered another problem and figured out a solution, which I would like to share with you.

I'm working with rather old PC assemblies, that have a 640x480 touch screen attached and only 512MB of RAM.

Older Avira Rescue System revisions worked ok, except for the fact that the update button was outside the visible screen area, so I usually switched to the console and updated the virus definition files there. Often I also started the virus scan from the command line as well.

Using the new Avira Rescue System from early this week, I briefly see the Avira GUI (after quite a long initialization phase), then the screen turns black.

I have seen this sometimes with earlier versions as well, but then I could press CTRL-ALT-BACKSPACE to get to the console and perform the update and scan operations on the command line. Doing this with the latest Avira, it seems to restart the X server almost immediately, causing the same black screen in addition to an "insufficient memory" message.

The original Avira ISO supports a "No GUI" boot option, that is not shown on the boot screen, I think, and that is not listed when running Avira from Sardu.

So I did add the respective boot section to my /extra/extra.cfg:

#
label Anti^Vir Rescue System (No GUI)
kernel /antivir/vmlinuz
append nofb initrd=/antivir/initrd.gz ramdisk_size=108178 root=/dev/ram0 rw console=/dev/vc/4 av-nogui


Unfortunately, not all initialization steps are performed automatically when using the No GUI option, so I added a short script, based on the one provided with the Avira Rescue system and added the update and scan commands as well, so I only need to run one command after booting.

I placed the script in /extra and named it "RunAvira". (I'm not sure about what some of the lines do exactly, since I'm not very familiar with Linux, but it seems to work alright).

So, after booting Avira (No GUI ), I use

sh /media/Disks/E\:__\(3.7G)/extra/RunAvira

with "E\:__\(3.7G)" being my thumb drive (replace with the drive letter of your Sardu drive)

It's content is this:

#!/bin/ash
DEBUG=false

export DBGTTY=/var/log/bootup.log

if echo "$@" | grep -q -e '--debug' ; then
DEBUG=true
fi

/bin/network &
/bin/get_vdf
if [ "0" != "$?" ] ; then
exit 1;
fi

/usr/bin/avupdate

/AntiVir/scancl --allboot --allfiles --scaninarchive --nolinks --colors /media/Devices/hda*

exit 0;
;;

esac


I hope this is of use to other people as well.

Maybe the Sardu/Avira menu could be modified to list the No GUI option natively?


Thanks for sharing.
My problems is who i cannot know the unit who the user use (Your hda. This is classic div solution. I can add this solution in the forum, to the FAQ section.

#7 Darkwing4296

Darkwing4296
  • Members
  • 2 posts

Posted 13 January 2011 - 02:04 PM

Thanks for sharing.
My problems is who i cannot know the unit who the user use (Your hda. This is classic div solution. I can add this solution in the forum, to the FAQ section.


The portion regarding the actual scan parameters is closely related to the individual system, of course. I intended this to be FAQ-like, that's true.

However, the option to boot Avira to the command line (No GUI), so the user may use system-specific command line operations, is something that could be handled by Sardu, I think.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users