[ previous ] [ next ] [ threads ]
 
 From:  Mike Reiprich <reiprim at gmail dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Issues with 1.33b1 / Realtelk devices / Watchguard x series
 Date:  Sun, 16 Jan 2011 20:27:28 -0700
I can confirm this bug, I captured a good boot with 1.32 and the bad 
boot with 1.33b1



1.32 boot:
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
     The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.4-RELEASE-p5 #0: Sun Apr 11 18:55:29 CEST 2010
     root at mb64 dot neon1 dot net:/usr/src/sys/i386/compile/M0N0WALL_GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(TM) CPU                1200MHz (1202.73-MHz 
686-class CPU)
   Origin = "GenuineIntel"  Id = 0x6b4  Stepping = 4
   
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory  = 268435456 (256 MB)
avail memory = 236515328 (225 MB)
wlan: mac acl policy registered
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
cpu0 on motherboard
pcib0: <Intel 82815 (i815 GMCH) Host To Hub bridge> pcibus 0 on motherboard
pir0: <PCI Interrupt Routing Table: 11 Entries> on motherboard
$PIR: Using invalid BIOS IRQ 9 from 2.13.INTA for link 0x63
pci0: <PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pcib2: <PCIBIOS PCI-PCI bridge> at device 30.0 on pci0
pci2: <PCI bus> on pcib2
pci2: <unknown> at device 6.0 (no driver attached)
re0: <RealTek 8139C+ 10/100BaseTX> port 0xd500-0xd5ff mem 
0xefefa000-0xefefa1ff irq 10 at device 9.0 on pci2
miibus0: <MII bus> on re0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re0: Ethernet address: 00:90:7f:2f:39:b9
re0: [FAST]
re1: <RealTek 8139C+ 10/100BaseTX> port 0xd600-0xd6ff mem 
0xefefb000-0xefefb1ff irq 5 at device 10.0 on pci2
miibus1: <MII bus> on re1
rlphy1: <RealTek internal media interface> on miibus1
rlphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re1: Ethernet address: 00:90:7f:2f:39:ba
re1: [FAST]
re2: <RealTek 8139C+ 10/100BaseTX> port 0xd900-0xd9ff mem 
0xefefc000-0xefefc1ff irq 11 at device 11.0 on pci2
miibus2: <MII bus> on re2
rlphy2: <RealTek internal media interface> on miibus2
rlphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re2: Ethernet address: 00:90:7f:2f:39:bb
re2: [FAST]
re3: <RealTek 8139C+ 10/100BaseTX> port 0xda00-0xdaff mem 
0xefefd000-0xefefd1ff irq 12 at device 12.0 on pci2
miibus3: <MII bus> on re3
rlphy3: <RealTek internal media interface> on miibus3
rlphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re3: Ethernet address: 00:90:7f:2f:39:bc
re3: [FAST]
re4: <RealTek 8139C+ 10/100BaseTX> port 0xdd00-0xddff mem 
0xefefe000-0xefefe1ff irq 9 at device 13.0 on pci2
miibus4: <MII bus> on re4
rlphy4: <RealTek internal media interface> on miibus4
rlphy4:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re4: Ethernet address: 00:90:7f:2f:39:bd
re4: [FAST]
re5: <RealTek 8139C+ 10/100BaseTX> port 0xde00-0xdeff mem 
0xefeff000-0xefeff1ff irq 6 at device 14.0 on pci2
miibus5: <MII bus> on re5
rlphy5: <RealTek internal media interface> on miibus5
rlphy5:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re5: Ethernet address: 00:90:7f:2f:39:be
re5: [FAST]
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH2 UDMA100 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xe0000-0xe0fff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
unknown: <PNP0c01> can't assign resources (memory)
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
RTC BIOS diagnostic error 20<config_unit>
Timecounter "TSC" frequency 1202733448 Hz quality 800
Timecounters tick every 1.000 msec
Fast IPsec: Initialized Security Association Processing.
IP Filter: v4.1.28 initialized.  Default = block all, Logging = enabled
md0: Preloaded image </mfsroot> 16777216 bytes at 0xc0abc3e8
ad0: 62MB <SAMSUNG CF/ATA S1.18.4> at ata0-master PIO2
Trying to mount root from ufs:/dev/md0
kern.coredump: 1 -> 0
Found configuration on ad0.
Initializing timezone... done
Configuring firewall... done
Configuring LAN rinterface... e1: link state changed to DOWN
done
Configuring WAN interface... re0: link state changed to DOWN
done
Starting syslog service... done
Starting webGUI... done
Starting DNS forwarder... done
Starting DHCP service... done
Starting NTP client... done


*** This is m0n0wall, version 1.32
     built on Sat Apr 17 21:02:05 CEST 2010 for generic-pc
     Copyright (C) 2002-2010 by Manuel Kasper. All rights reserved.
     Visit http://m0n0.ch/wall for updates.


     LAN IP address: 192.168.3.1

     Port configuration:

     LAN   -> re1
     WAN   -> re0


m0n0wall console setup
**********************
1) Interfaces: assign network ports
2) Set up LAN IP address
3) Reset webGUI password
4) Reset to factory defaults
5) Reboot system
6) Ping host

Enter a number: 1

Valid interfaces are:

re0     00:90:7f:2f:39:b9   (up)   RealTek 8139C+ 10/100BaseTX
re1     00:90:7f:2f:39:ba   (up)   RealTek 8139C+ 10/100BaseTX
re2     00:90:7f:2f:39:bb          RealTek 8139C+ 10/100BaseTX
re3     00:90:7f:2f:39:bc          RealTek 8139C+ 10/100BaseTX
re4     00:90:7f:2f:39:bd          RealTek 8139C+ 10/100BaseTX
re5     00:90:7f:2f:39:be          RealTek 8139C+ 10/100BaseTX

Do you want to set up VLANs first?
If you're not going to use VLANs, or only for optional interfaces, you
should say no here and use the webGUI to configure VLANs later, if required.



1.33b1 boot:
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
     The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.4-RELEASE-p5 #0: Wed Oct 13 14:46:28 CEST 2010
     root at mb64 dot neon1 dot net:/usr/src/sys/i386/compile/M0N0WALL_GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Celeron(TM) CPU                1200MHz (1202.73-MHz 
686-class CPU)
   Origin = "GenuineIntel"  Id = 0x6b4  Stepping = 4
   
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory  = 268435456 (256 MB)
avail memory = 236515328 (225 MB)
wlan: mac acl policy registered
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
cpu0 on motherboard
pcib0: <Intel 82815 (i815 GMCH) Host To Hub bridge> pcibus 0 on motherboard
pir0: <PCI Interrupt Routing Table: 11 Entries> on motherboard
$PIR: Using invalid BIOS IRQ 9 from 2.13.INTA for link 0x63
pci0: <PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pcib2: <PCIBIOS PCI-PCI bridge> at device 30.0 on pci0
pci2: <PCI bus> on pcib2
pci2: <unknown> at device 6.0 (no driver attached)
pci2: <network, ethernet> at device 9.0 (no driver attached)
pci2: <network, ethernet> at device 10.0 (no driver attached)
pci2: <network, ethernet> at device 11.0 (no driver attached)
pci2: <network, ethernet> at device 12.0 (no driver attached)
pci2: <network, ethernet> at device 13.0 (no driver attached)
pci2: <network, ethernet> at device 14.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH2 UDMA100 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pmtimer0 on isa0
orm0: <ISA Option ROM> at iomem 0xe0000-0xe0fff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
unknown: <PNP0c01> can't assign resources (memory)
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
RTC BIOS diagnostic error 20<config_unit>
Timecounter "TSC" frequency 1202733869 Hz quality 800
Timecounters tick every 1.000 msec
Fast IPsec: Initialized Security Association Processing.
IP Filter: v4.1.33 initialized.  Default = block all, Logging = enabled
md0: Preloaded image </mfsroot> 16777216 bytes at 0xc0ad03b4
ad0: 62MB <SAMSUNG CF/ATA S1.18.4> at ata0-master PIO2
Trying to mount root from ufs:/dev/md0
kern.coredump: 1 -> 0
Found configuration on ad0.
Initializing timezone... done
Configuring firewall... done
Configuring LAN interface... done
Configuring WAN interface... done
Starting syslog service... done
Starting webGUI... done
Starting DNS forwarder... done
Starting DHCP service... done
Starting NTP client... done


*** This is m0n0wall, version 1.33b1
     built on Wed Dec 29 17:05:36 CET 2010 for generic-pc
     Copyright (C) 2002-2010 by Manuel Kasper. All rights reserved.
     Visit http://m0n0.ch/wall for updates.


     LAN IP address: 192.168.3.1

     Port configuration:

     LAN   -> re1
     WAN   -> re0


m0n0wall console setup
**********************
1) Interfaces: assign network ports
2) Set up LAN IP address
3) Reset webGUI password
4) Reset to factory defaults
5) Reboot system
6) Ping host

Enter a number: 1

Valid interfaces are:


Do you want to set up VLANs first?
If you're not going to use VLANs, or only for optional interfaces, you
should say no here and use the webGUI to configure VLANs later, if required.

Do you want to set up VLANs now? (y/n) n

If you don't know the names of your interfaces, you may choose to use
auto-detection. In that case, disconnect all interfaces before you begin,
and reconnect each one when prompted to do so.



On 12/30/2010 11:02 AM, Manuel Kasper wrote:
> On 30.12.2010, at 10:36, Simon Baker wrote:
>
>> Just tried to upgrade one of my watchguards which I'd moved to m0n0wall a while back ; the new
beta version doesn't seem to support my network cards anymore.  They're definitely realtek cards, I
can't recall the model number at the moment,as I've just wiped out my fw ;-)
>>
>> Anyways, here's the rather limited info I can provide currently:
>>
>> After an initial reboot, everything was down and not responding.  Hook up console (which was also
unfun!), the version has updated and also it's kept the config:
> Can you post the dmesg output (i.e. all the stuff that the kernel prints out while booting before
the m0n0wall console menu appears)? That might help narrow down the issue.
>
> - Manuel
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>