Folks,

I posted this on the PHLAK forum as well... no replies as of yet. PHLAK runs flawlessly from the liveCD, but when running from the hard drive install, no networking, see below.

The liveCD PHLAK runs great, what an utterly smooth distribution! Nice when everything works, my immense gratitude extends to the team for about the smoothest operating system I've had pleasure to know. It's as if you melted off the bristly edges growing around Debian and distilled it into one heck of a solid and functional O/S.

I'm itching to solve this problem so I can run updates and have at it.

Now, when booting into the hard drive-installed system I lose networking. Here's a bit of what I see:

Firstly, I usually get from ifconfig ": error fetching interface information: Device not found"

...but oddly one time (only) I got:

eth0 Link encap:Ethernet HWaddr AA:00:04:00:0A:04
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:7737 errors:0 dropped:0 overruns:0 frame:0
TX packets:1991 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2489318 (2.3 MiB) TX bytes:99454 (97.1 KiB)

...which is not the MAC of the card. While running from the liveCD, ifconfig shows it (correctly) as 00:90:27:31:A1:99.

But dmesg (after booting from HD) shows the right MAC and that the e100 module is loading without error:

(cut)
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
Registering unionfs version $Id: main.c,v 1.85 2005/03/14 22:19:49 dquigley Exp $
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
PCI: Enabling device 0000:00:0e.0 (0104 -> 0106)
PCI: Found IRQ 10 for device 0000:00:0e.0
e100: Intel(R) PRO/100 Network Driver, 3.0.27-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
PCI: Found IRQ 9 for device 0000:00:06.0
PCI: Sharing IRQ 9 with 0000:00:07.2
e100: eth0: e100_probe: addr 0xf4108000, irq 9, MAC addr 00:90:27:31:A1:99
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
ieee1394: Initialized config rom entry `ip1394'
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
USB Universal Host Controller Interface driver v2.2
PCI: Found IRQ 9 for device 0000:00:07.2
PCI: Sharing IRQ 9 with 0000:00:06.0
uhci_hcd 0000:00:07.2: Intel Corp. 82371AB/EB/MB PIIX4 USB
uhci_hcd 0000:00:07.2: irq 9, io base 00001040
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
NET4: DECnet for Linux: V.2.5.68s (C) 1995-2003 Linux DECnet Project Team
DECnet: Routing cache hash table of 1024 buckets, 8Kbytes
NET: Registered protocol family 12
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
ttyS1: LSR safety check engaged!
ttyS1: LSR safety check engaged!
lp0: using parport0 (interrupt-driven).
lp0: console ready
Bluetooth: Core ver 2.6
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.4
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM ver 1.3
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
apm: BIOS not found
(etc)

...e100 is loaded, as agreed by lsmod:

Module Size Used by
rfcomm 31132 0
l2cap 18820 5 rfcomm
bluetooth 38276 4 rfcomm,l2cap
lp 9516 0
decnet 92176 0 [permanent]
ide_cd 36896 0
aic7xxx 160440 0
aha152x 36560 0
atp870u 21152 0
megaraid 37192 0
tmscsim 24128 0
a100u2w 10432 0
uhci_hcd 27920 0
ohci_hcd 18308 0
ohci1394 29700 0
ieee1394 303032 1 ohci1394
parport_pc 35648 1
parport 32456 2 lp,parport_pc
sg 28320 0
e100 30208 0
mii 3968 1 e100
snd_ymfpci 52676 2
snd_ac97_codec 63568 1 snd_ymfpci
snd_opl3_lib 8192 1 snd_ymfpci
snd_hwdep 6916 1 snd_opl3_lib
gameport 3712 1 snd_ymfpci
snd_mpu401_uart 5760 1 snd_ymfpci
snd_pcm_oss 46760 0
snd_pcm 77576 2 snd_ymfpci,snd_pcm_oss
snd_page_alloc 7432 2 snd_ymfpci,snd_pcm
snd_mixer_oss 16256 3 snd_pcm_oss
snd_seq_oss 28800 0
snd_seq_midi 6304 0
snd_rawmidi 18852 2 snd_mpu401_uart,snd_seq_midi
snd_seq_midi_event 6016 2 snd_seq_oss,snd_seq_midi
snd_seq 44688 5 snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 19460 4 snd_ymfpci,snd_opl3_lib,snd_pcm,snd_seq
snd_seq_device 6280 5 snd_opl3_lib,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 43748 13 snd_ymfpci,snd_ac97_codec,snd_opl3_lib,snd_hwdep,snd_mpu401_uart,snd_pcm_oss,snd_pcm,snd_mixer_oss,s nd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 6880 3 snd
usbhid 38336 0
usb_storage 61120 0
usbcore 96868 6 uhci_hcd,ohci_hcd,usbhid,usb_storage
ext3 104808 0
jbd 49176 1 ext3
unionfs 812052 0
yenta_socket 17920 0
ds 13700 0
pcmcia_core 57796 2 yenta_socket,ds
intel_agp 18720 1
agpgart 27432 1 intel_agp
pcspkr 3304 0
8250_pnp 8064 0
8250 33856 1 8250_pnp
serial_core 17408 1 8250
evdev 7168 0
tsdev 5824 0
af_packet 16008 2
ipv6 219648 12
md5 3840 1
rtc 9400 0

The above indicates (at least to me) that the kernel does not need recompiling.

All dhcpd and dhclient commands run on the interface result in "Can't get interface flags for : No such device exiting"

I spent the day checking "diff"s between the liveCD versus the hard drive 'versions' of various contents of /etc for clues. Lots of diffs... but nothing glaring jumps out to my most untrained eye. I am no where near the class of you developer-types regarding such things. (I'm an historian by vocation)

I add that this exact scenario occurred on an unrelated P-III 600 system as well.

I'll keep poking away at it. I suspect dhcpd is the culprit, perhaps a script... which is way beyond my league to find or fix all by my lonesome. But if anyone had any suggestions, I could sure handle the "just (friggin'!) do this..." style of advice. In fact I'd learn immensely from such advice. I've been using Linux exclusively now for around 7 years, ever since I taught a Windoze(tm)-oriented "A+ certification" course at a local college. After learning what I had about Microsquish(tm) in order to teach that course, I ran away from the Borg and never looked back... what a nightmare! (also the genesis of my interst in security, btw)

Again, great distro. I've learned a lot already, like what a good Linux distro really is. Thanks.

Cliff Jones
Horseheads, New York

I just reported to PHLAK that, although I have done nothing, the network suddenly works. All the commands still report no iterface device! I am at a total loss... don't like the mysteries.