vicidial.org

Immediately following the reboot after os-install I got a "file system type is ext2fs partition type is 0x83 .... Error 13 invalid or unsupported executable format" error message. Hard reboot and never saw that again so this error may or may not be related but it's worth mentioning. After rebooting I got to the yast autoconfiguration where I could tell it did not have Internet access and failed to download repodata/repomd.xml.asc etc.... Long story short and a few tries later it wasn't until I switched my interface to dhcp and back after installing before my network would work even though everything about my lan config looked good. I could ping myself but not anything on my lan.
So 4 questions:
what did my install miss if it couldn't run the yast
Is there a command I should run?
Do you have to leave 3.0.9 as dhcp during install? (I double and triple checked my settings but didn't try that)
Am I ok to proceed?

Vicibox 3.0.9 64bit from iso | Single Server | Sangoma PRI card | No Extra Software After Installation

You should follow the instructions in this thread:

http://www.vicidial.org/VICIDIALforum/v ... hp?t=14672

Since your system boots, you only need to do the last two lines.

What kind of motherboard/etc is it?

Not sure on the motherboard. I can research it though.
The system boots so I would just be using steps 15 and 16 from that post but I get the following. Looks like it wants to switch from 64 bit to 32 bit. Is that right? Is that what needs to be done?

Code: Select all

vicibox:~ # zypper in kernel-pae
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: kernel-pae-2.6.34.7-0.5.1.i586 conflicts with libc.so.6()(64bit) provid                                                            ed by glibc-2.11.2-3.1.1.x86_64
 Solution 1: Following actions will be done:
  install glibc-2.11.2-3.3.1.i686 despite the inferior architecture
  architecture change of glibc-2.11.2-3.3.1.x86_64 to glibc-2.11.2-3.3.1.i686
  architecture change of php5-eaccelerator-0.9.6-1.2.x86_64 to php5-eaccelerator                                                            -0.9.6-1.2.i586
  install php5-eaccelerator-0.9.6-1.2.i586 despite the inferior architecture
  architecture change of mpg123-1.12.5-1.pm.1.1.x86_64 to mpg123-1.12.5-1.pm.1.1                                                            .i586
  install mpg123-1.12.5-1.pm.1.1.i586 despite the inferior architecture
  architecture change of libmpg123-0-1.12.5-1.pm.1.1.x86_64 to libmpg123-0-1.12.                                                            5-1.pm.1.1.i586
  install libmpg123-0-1.12.5-1.pm.1.1.i586 despite the inferior architecture
  architecture change of libopencore-amrnb0-0.1.2-1.pm.3.1.x86_64 to libopencore                                                            -amrnb0-0.1.2-1.pm.3.1.i586
...
...
  install ConsoleKit-0.4.1-6.1.i586 despite the inferior architecture
 Solution 2: do not install kernel-pae-2.6.34.7-0.5.1.i586

Choose from above solutions by number or cancel [1/2/c] (c):


if you had issues during repository download, you may want to just do it over and use those instructions before the repo download to be sure it all happens correctly.

i've had a couple issues where the repo was unavailable and i've had to use a different repo. the times we tried it without the repo caused weirdness. reloading with a different repo got rid of all the weirdness.

between a successful repo and kumba's directions, you may get a cleaner system if you reinstall again.

Ok I will try again leaving it as dhcp. A little off topic but can you point me at another thread that talks about how to setup the sangoma card after the install?

does "the Sangoma Card" have a model number? remember you are setting this up in asterisk ... lots of sites available via google

Keeping it using DHCP during the install did the trick meaning there were no errors during os-install. Zypper in kernal-pae still looks like above though. Is that really what I should be doing? The motherboard is a Super Micro X7SBE

if you had no errors during install ... why are you zyppering again?

Because I am a noob. No wait! Because I thought I wanted a PAE kernel not default? Yea that sounds good....

How much memory do you have? (In case you're a noob)

And ... did you install the 64 bit or the 32 bit?

Try typing 'zypper refresh' before 'zypper in kernel-pae', they may have started moving repo's around.

In a related note, I almost have 3.0.10 ready to go from where susestudio lost some stuff.

Thanks for your help.
8gb of ram and I used ViciBox_Redux.x86_64-3.0.9.iso to install.
and "zypper refresh" beforehand does not change the output of "zypper in kernel-pae"

if you already have 64-bit, is there a problem with running the non-pae kernel? in 64 bit you can already address all the memory, and the system seems stable without the pae ...?

There is no PAE for 64-bit. That is solely a 32-bit feature. I missed that entire part of his post. Those instructions are only for the 32-bit ViciBox Redux. I've since gone back and clarified that on the post.

You can safely ignore them.

As far as the network not coming up, I have seen that sometimes after the initial install. Usually the fix is to reboot the machine again and everything is happy. Not sure why this happens, and it's intermittent so hard to diagnose. I just know I have seen it at times.

Usually when I do an install, I leave it as DHCP and mangle the network after the OS Install is done.

Usually when I do an install, I leave it as DHCP and mangle the network after the OS Install is done.

we've begun doing this too. Now that we're used to yast and opensuse, it is MUCH easier after you realize those screens can be used to modify internet settings at will, they aren't something kumba made up for the installation process.

Thanks for your help on this one. As far as my procedures for Installing ViciBox goes, I have added "test internet connection before running os-install" and "leave network settings as DHCP during os-install". Thanks again.

I did get the file system type error again but it only shows up once and doesn't seam to be a problem after a reboot.