Pbxinaflash 1.1

[jrglass]

I installed the new iso this AM. It seems to be working except for two things.
1 Every time I do a shutdown -r now I getCode bad EIP value, Kernel panic.

2 I installed a inbound route that works but does not show up in Incoming Routes. When I try to add it it said it is already there.

Thanks,

Jeff

 

[wardmundy]

Have you run linux mediacheck on the install CD??

 

[darmock]

Generally bad EIP value has always turned out to be a bad hardware card for me. Usually X100p cards removed them and it went away. Course you may have something completely different

what hardware/processor/cards do you have?

Tom

 

[jrglass]

Have you run linux mediacheck on the install CD??

I will run it tomorrow!

Thanks,

Jeff

 

[jrglass]

Generally bad EIP value has always turned out to be a bad hardware card for me. Usually X100p cards removed them and it went away. Course you may have something completely different

what hardware/processor/cards do you have?

Tom

I will remove the clone x100p cards tomorrow. AMD processor. The MB I will need to check tomorrow.

Thanks,

Jeff

 

[jrglass]

Have you run linux mediacheck on the install CD??

I tried to run linux mediacheck from the boot prompt but rather then checking the media it started the install program.

Jeff

 

[jrglass]

Generally bad EIP value has always turned out to be a bad hardware card for me. Usually X100p cards removed them and it went away. Course you may have something completely different

what hardware/processor/cards do you have?

Tom

A ECS K7S5A MB
[SIZE=-1]Processors[/SIZE][SIZE=-1]1[/SIZE][SIZE=-1]Model[/SIZE][SIZE=-1]AMD Athlon(tm) Processor[/SIZE][SIZE=-1]CPU Speed[/SIZE][SIZE=-1]945.99 Mhz[/SIZE][SIZE=-1]Cache Size[/SIZE][SIZE=-1]256.00 KB[/SIZE][SIZE=-1]System Bogomips[/SIZE][SIZE=-1]1892.57[/SIZE][SIZE=-1]PCI Devices[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1](2x) Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]Host bridge: Silicon Integrated Systems [SiS] 735 Host[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE][/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]Multimedia audio controller: Cirrus Logic CS 4614/22/24/30 [CrystalClear SoundFusion Audio Accelerator][/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1](2x) USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]VGA compatible controller: nVidia Corporation NV11DDR [GeForce2 MX 100 DDR/200 DDR][/SIZE][SIZE=-1]IDE Devices[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]hdc: CDU5211[/SIZE][SIZE=-1]-[/SIZE][SIZE=-1]hda: IBM-DPTA-371360 (Capacity: 12.74 GB)[/SIZE][SIZE=-1]SCSI Devices[/SIZE][SIZE=-1]none[/SIZE] [SIZE=-1]USB Devices[/SIZE][SIZE=-1]none[/SIZE]

Jeff

 

[darmock]

Not to bash Centos/redhat/et al (as this is their problem) but AMD support for onboard devices is at times problematic I am afraid. Centos out of the box sometimes just does not have the drivers required to make AMD stuff work reliably. THIS IS NOT A FLAME WAR PLEASE!!!!

I use AMD stuff all of the time with great results under linux. I personally don't use them for my production PBX servers due to the patches that need to be implemented to get a reliable PBX platform.

Intel stuff seems to be better supported (again my personal opinion no flames) under Centos. This translates to fewer problems especially in commercial production machines. I recommend the Intel based supermicro stuff now although I have a wack of clients using an intel based gigabyte board on their production servers... (Board is no longer available)

I also am going to order a dell 440 special which is intel based to see if it holds up. I have been wary of big box names just because they sometimes put odd hardware in and it has NO linux support.

I assume you have turned everything off in the BIOS especially the sound card. Pull out your Tiger jet modem card and see if you get the bad EIP value.

Also running an older hard drive can cause "odd" issues.... (again personal observation)

Tom

 

[jvantslot]

hmmm... a "whack of clients"

Is that like a "murder of crows" or a "gaggle of geese"?

I would have thought a "bother of clients" but you must have a better class of clientel than me. ;-)

Sorry for the off topic, but couldn't resist.

 

[darmock]

hmmm... a "whack of clients"

Is that like a "murder of crows" or a "gaggle of geese"?

I would have thought a "bother of clients" but you must have a better class of clientel than me. ;-)

Sorry for the off topic, but couldn't resist.

Too much sopranos

Tom

 

[jrglass]

Generally bad EIP value has always turned out to be a bad hardware card for me. Usually X100p cards removed them and it went away. Course you may have something completely different

what hardware/processor/cards do you have?

Tom

I took out the x100p and sound card, The program will run a shutdown -r now with out crashing. Linux mediacheck failed so I am D/L the whole ISO rather than torrent. The problem of the inbound route still exist.

Jeff

 

[mp3geek]

kernel panic

I recently had to dust off an old X100p card and put it back in service on my home box ( a customer needed a TDM400 installed pronto, so I robbed my card). I too had the kernel panic issue with the X100p. I found that if you stop Asterisk first, then reboot, the kernel panic went away. I wrote this simple script and use it to do a restart:

#!/bin/sh

service asterisk stop
shutdown -r now

You should also be able to use amportal stop instead of service asterisk stop if you like.

Cheers,
Mike

 

[TomS]

I have a Dell P4 with 1G RAM and as soon as I inserted the two X100P clone cards and set them up, the kernel panics when rebooting (not when the PC is powering up when being turned on).
This same fix has worked on my Micro PCs also.

The same old fix works like a charm - I have been using it for a couple of years:
cd /etc/rc2.d
vi K02haldaemon that's K zero 2 ...

Add the line "killproc asterisk" just before the other killproc command in the
stop() section of the script.

It should now look something like this:

stop() {
echo -n $"Stopping HAL daemon: "

# Added to stop the X100P cards causing a KERNEL PANIC
killproc asterisk

killproc $servicename -TERM

... and the remaining code ...

Then save the file.
My Dell now reboots with no problem. Hope this helps you!
Best of luck!
TomS