Hi all, i want to report a problem with the Development Build: next/b3acd7b8-dirty of Core 69. I have tried the boot.ipfire.org section but the following error appears.
IPXE initialising devices... OK IPFire boot server (boot.ipfire.org) IPXE 1.0.0+ --open source Network Boot firmware - http://ipxe.org
Waiting for link -up on net to... failed Permission denied (http://ipxe.org/o227603x) Could not configure net0: permission denied (http://ipxe.org/o227603x)
Reboot and Select proper boot device.....
Greetings
Erik
On 2013-06-03 11:42, embp wrote:
Hi all, i want to report a problem with the Development Build: next/b3acd7b8-dirty of Core 69. I have tried the boot.ipfire.org [1] section but the following error appears.
IPXE initialising devices... OK IPFire boot server (boot.ipfire.org [1]) IPXE 1.0.0+ --open source Network Boot firmware - http://ipxe.org [2]
Waiting for link -up on net to... failed Permission denied (http://ipxe.org/o227603x [3]) Could not configure net0: permission denied (http://ipxe.org/o227603x [3])
looks like an unsupported nic. can you give some hardware details.
Reboot and Select proper boot device.....
Greetings
Erik
Links:
[1] http://boot.ipfire.org [2] http://ipxe.org [3] http://ipxe.org/o227603x
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi Arne, http://fireinfo.ipfire.org/profile/0ff6b8f6c99b0d7ab521300a9bf1d968d595e2c2 . The same Machine works as IPFire (test Fire) since a couple of months now
Greetings
Erik
Am 04.06.2013 um 08:44 schrieb Arne Fitzenreiter:
On 2013-06-03 11:42, embp wrote:
Hi all, i want to report a problem with the Development Build: next/b3acd7b8-dirty of Core 69. I have tried the boot.ipfire.org [1] section but the following error appears. IPXE initialising devices... OK IPFire boot server (boot.ipfire.org [1]) IPXE 1.0.0+ --open source Network Boot firmware - http://ipxe.org [2] Waiting for link -up on net to... failed Permission denied (http://ipxe.org/o227603x [3]) Could not configure net0: permission denied (http://ipxe.org/o227603x [3])
looks like an unsupported nic. can you give some hardware details.
Reboot and Select proper boot device..... Greetings Erik Links:
[1] http://boot.ipfire.org [2] http://ipxe.org [3] http://ipxe.org/o227603x _______________________________________________ Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
On 2013-06-04 08:50, Erik K. wrote:
Hi Arne, http://fireinfo.ipfire.org/profile/0ff6b8f6c99b0d7ab521300a9bf1d968d595e2c2 [5] . The same Machine works as IPFire (test Fire) since a couple of months now
Greetings
Erik
Am 04.06.2013 um 08:44 schrieb Arne Fitzenreiter:
On 2013-06-03 11:42, embp wrote:
Hi all,
i want to report a problem with the Development Build:
n
re 69. I have tried the boot.ipfire.org [1] [1]
ection but the following
kquote>IPXE initiali
.. OK IPFire boot server (Developme
Links:
Muss ich nochmal Testen. Ich hoffe ich finde einen RTL8168 irgendwo. Oder kommt das iPXE mit zwei gleichen Nic's nicht klar?
[1] http://boot.ipfire.org [2] http://ipxe.org [3] http://mail.ipfire.org/h<div>
> [3]">http://ipxe.org/o227603x%C2%A0%5B3]) > > loo
</div>supportednic.canyougivesomehardwaredetails.
<b<div>
> ">Reboot and Select proper boot device.....
</div>ngs </blockquote><block<div>
> r> > >> Links: > >> ------
</div>1]<ahref= [4] http://ipxe.o<div>
> br>[3]
</div>//ipxe.org/o227603x [5] http://fireinfo.ipfire.org/profile/0ff6b8f6c99b0d7ab521300a9bf1d968d595e2c2
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
I have to test this again with a rtl 8168. (my rtl 8139 has worked) Have someone already tested if iPXE works with more than one identical nics?
Arne
On 2013-06-04 08:50, Erik K. wrote:
Hi Arne, http://fireinfo.ipfire.org/profile/0ff6b8f6c99b0d7ab521300a9bf1d968d595e2c2 [5] . The same Machine works as IPFire (test Fire) since a couple of months now
Greetings
Erik
Am 04.06.2013 um 08:44 schrieb Arne Fitzenreiter:
On 2013-06-03 11:42, embp wrote:
Hi all,
i want to report a problem with the Development Build:
n
re 69. I have tried the boot.ipfire.org [1] [1]
ection but the following
kquote>IPXE initiali
.. OK IPFire boot server (Developme
Links:
[1] http://boot.ipfire.org [2] http://ipxe.org [3] http://mail.ipfire.org/h<div>
> [3]">http://ipxe.org/o227603x%C2%A0%5B3]) > > loo
</div>supportednic.canyougivesomehardwaredetails.
<b<div>
> ">Reboot and Select proper boot device.....
</div>ngs </blockquote><block<div>
> r> > >> Links: > >> ------
</div>1]<ahref= [4] http://ipxe.o<div>
> br>[3]
</div>//ipxe.org/o227603x [5] http://fireinfo.ipfire.org/profile/0ff6b8f6c99b0d7ab521300a9bf1d968d595e2c2
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Hi Arne
I've tested the pxe boot from cd with an Intel onboard gigabit nic and it works fine here.
- Daniel
Hello,
i have a proble with calls via ISDN. I can't hear the caller. But the caller hear me. Everything work fine with internal calls and calls via sipgate.
Software: Asterisk 1.8.19.0, LCR Version 1.12 and Misdn
Misdn Info: Port 0 'hfc-pci.1': TE/NT-mode BRI S/T (for phone lines & phones) 2 B-channels: 1-2 B-protocols: RAW HDLC X75slp L2:DSP L2:DSPHDLC
I've looks in some log-files. This was the only thing it looks like a problem:
LCR-LOG: DEBUG (in new_state() line 261): PORT(misdnextern-0-in) new state PORT_STATE_RELEASE --> PORT_STATE_RELEASE DEBUG (in stack2manager() line 2903): cmd(0x11001) pid(0x10001) TRACE : 08.06.13 17:13:16.296 CH(2): MT_RELEASE_L3ID INDICATION port 0 callref 0x10001 DEBUG (in stack2manager() line 2903): cmd(0x12002) pid(0x40) DEBUG (in stack2manager() line 3006): Got L2 idle DEBUG (in drop_bchannel() line 1076): PmISDN(misdnextern-0-in) dropping bchannel TRACE : 08.06.13 17:13:16.296 CH(2): BCHANNEL deactivate port 0 channel 1 DEBUG (in ~PmISDN() line 224): destroyed mISDNPort(misdnextern-0-in). Currently 0 objects DEBUG (in ~Port() line 209): removing port (2) of type 0x1111, name 'misdnextern-0-in' DEBUG (in b_sock_callback() line 2004): DL_RELEASE confirm: bchannel is now de-activated (socket 12).
Thank you for your help.
Michael
-
Arne Fitzenreiter -
Daniel Weismüller -
embp -
Erik K. -
Michael Liekmeier