On 29/08/06, Eddy Petrişor <[EMAIL PROTECTED]> wrote:
Abel, from now on, please respond to the new bug report when related
to pppoe issues. Thanks.
The cloned bug will be assigned to ppp-udeb.
I looked over the log and I think the failure appears when the
concentrator is looked over the eth1 interface:
Aug 28 23:08:42 DEBUG:ppp-udeb: eth1 was not configured. ppp-udeb will
bring it up
Aug 28 23:08:42 kernel: ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 16
(level, low) -> IRQ 193
Aug 28 23:08:42 kernel: eth1: setting full-duplex.
Aug 28 23:08:42 debconf: --> PROGRESS START 0 45 ppp/detect_progress
Aug 28 23:08:42 debconf: <-- 0 OK
Aug 28 23:08:42 pppoe-discovery: ioctl(SIOCGIFHWADDR): No such device
Aug 28 23:08:42 debconf: --> PROGRESS STOP
Aug 28 23:08:42 debconf: <-- 0 OK
Aug 28 23:08:42 DEBUG:ppp-udeb: no concentrator found on eth1; will
bring the interface back down
Aug 28 23:08:42 debconf: --> INPUT critical ppp/no_concentrators
Aug 28 23:08:42 debconf: <-- 0 question will be asked
Aug 28 23:08:42 debconf: --> GO
Aug 28 23:08:42 pppoe-discovery: receivePacket: recv: Network is down
Aug 28 23:09:13 debconf: <-- 0 ok
Aug 28 23:09:13 main-menu[2234]: (process:11313): 0
Aug 28 23:09:13 main-menu[2234]: (process:11313): 0
Aug 28 23:09:13 main-menu[2234]: (process:11313): [:
Aug 28 23:09:13 main-menu[2234]: (process:11313): 11532: unknown operand
Aug 28 23:09:13 main-menu[2234]: (process:11313):
Aug 28 23:09:13 main-menu[2234]: WARNING **: Configuring 'ppp-udeb'
failed with error code 1
It seems that there is something strange happening with that
interface. Moreover, I don't see it discovered when hw-detect attempts
to find it.
Could you run by hand these commands (from the d-i environment, after
you make sure the eth1 interface is brought up) and send the out* and
err* files?
pppoe-discovery -A -I eth1 >out1 2>err1
pppoe-discovery -A -I eth1 >out2 2>err2
--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
