Page 1 of 1

No Network Adaptor found -- even though I'm net booting!

Posted: Mon Nov 07, 2011 1:10 am
by thekorn
Howdy!

I already have a fully functioning PXE boot system up and running for months (maybe years at this point) serving a few existing minimyth clients. I decided to add one a Shuttle XS35GT to the stable. Plugged it into the network, it gets an address, finds the tftp server, pulls ram-minimyth-0.24.1-77 across, throws up the blue screen & progress bar like it should...

...except at that point, I get the message, "no network adapter found", then 'directory /minimyth failed to mount' (makes sense, if you can't find the network adapter), then a message to check /var/log/messages for details.

I think I'd get some insight if I could get into /var/log/messages , except there seems to be no way to check that file! Obviously I can't telnet in over the network. I have a USB keyboard hooked up, but can't find any way to switch off of the blue screen and back to a console... tried alt+0-9, alt + f1-f12, all do nothing. (Caps lock doesn't do anything either. This same keyboard works to get into the bios, so it's not the keyboard.)

What am I missing here? Thanks!

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Wed Nov 09, 2011 7:43 pm
by thekorn
Threw in a liveCD (which is a trick since it doesn't have an optical drive! :D ), and was able to get this info via a lspci -vv:

Code: Select all

02:00.5 Ethernet controller: JMicron Technology Corp. JMC260 PCI Express Fast Ethernet Controller (rev 02)
        Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device 2005
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 45
        Region 0: Memory at feaf8000 (32-bit, non-prefetchable) [size=16K]
        Region 2: I/O ports at dc00 [size=128]
        Region 3: I/O ports at d800 [size=256]
        Capabilities: [68] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Express (v1) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <64ns, L1 <1us
                        ClockPM- Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [40] MSI-X: Enable- Count=8 Masked-
                Vector table: BAR=0 offset=00002000
                PBA: BAR=0 offset=00003000
        Capabilities: [70] MSI: Enable+ Count=1/8 Maskable+ 64bit+
                Address: 00000000fee0100c  Data: 4189
                Masking: 000000fe  Pending: 00000000
        Kernel driver in use: jme
        Kernel modules: jme

03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8191SEvA Wireless LAN Controller (rev 10)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8191SEvA Wireless LAN Controller
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 19
        Region 0: I/O ports at e800 [size=256]
        Region 1: Memory at febfc000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [70] Express (v1) Legacy Endpoint, MSI 00
                DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
                        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
                LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
                        ClockPM+ Surprise- LLActRep- BwNot-
                LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
                        ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
        Capabilities: [100 v1] Advanced Error Reporting
                UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                CESta:  RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
                AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
        Capabilities: [140 v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
                        Status: NegoPending- InProgress-
        Capabilities: [160 v1] Device Serial Number [[redacted]]
        Kernel driver in use: rtl8192se
        Kernel modules: rtl8192se
There is more, obviously, but those are the only relevant portions. And I'm not trying to do this wirelessly, by the way; doing it wired but figured I'd list the wireless controller just in case there was a conflict.

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Wed Nov 09, 2011 8:08 pm
by JoeHenley
What does your dhcp.conf file look like?
Did you check the dhcp parameters in the minimyth.conf file for the new fe?
Do you see anything in the /var/log/messages file on the server?
If not, do you have minimyth.conf set up to send error messages to the server's messages file?
Maybe add "/sbin/syslogd -m 0 -R 192.168.1.100" <or whatever your server's address is> to the /etc/rc.d/rc.sysinit file (use it to replace "/sbin/syslogd") for the fe.

I looked at the lspci -vv results on my PC and they are essentially the same as yours, and my PXE boot works.

Good luck, and keep us posted.

Joe Henley

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Thu Nov 10, 2011 12:14 am
by thekorn
JoeHenley wrote:What does your dhcp.conf file look like?
Don't have one, as such. I'm using my dd-wrt router as my DHCP server. It's not doing anything special; ipv4, subnet, default gateway, etc. Only real option I have it sending is...

Code: Select all

dhcp-boot=pxelinux.0,,(172.18.myth server IP address)
...but I really don't think the problem could be located here anyway, or my other minimyth clients would be having a problem.
Did you check the dhcp parameters in the minimyth.conf file for the new fe?
The new FE is running my default minimyth config (shared with two other non-special clients), which has the following dhcp parameters defined in it:

Code: Select all

MM_DHCP_LOG_SERVERS='172.18.log_server.address'
MM_DHCP_HOST_NAME='myth-floater'
MM_DHCP_TCODE='America/Chicago'
MM_DHCP_NTP_SERVERS='172.18.myth_server.address'
Do you see anything in the /var/log/messages file on the server?
If not, do you have minimyth.conf set up to send error messages to the server's messages file?
I have a log server set, but no messages are being sent by this frontend. (I think it's failing WAY too early in the process.)

Maybe add "/sbin/syslogd -m 0 -R 192.168.1.100" <or whatever your server's address is> to the /etc/rc.d/rc.sysinit file (use it to replace "/sbin/syslogd") for the fe.
I don't quite follow what you're asking me to do here. Are you asking me to replace a file within the minimyth distribution?

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Thu Nov 10, 2011 4:43 pm
by JoeHenley
Do you see anything in the /var/log/messages file on the server?
If not, do you have minimyth.conf set up to send error messages to the server's messages file?

I have a log server set, but no messages are being sent by this frontend. (I think it's failing WAY too early in the process.)
At the start of the dhcp activity I see stuff like:
Nov 7 08:55:40 Eddie dhcpd: DHCPDISCOVER from <client A> via eth0
Nov 7 08:55:40 Eddie dhcpd: DHCPOFFER on <server> to <client A> via eth0
Nov 7 08:55:42 Eddie dhcpd: DHCPREQUEST for <server> (xxx.xxx.xxx.xxx) from <client A> via eth0
Nov 7 08:55:42 Eddie dhcpd: DHCPACK on <server> to <client A> via eth0
Nov 7 08:55:42 Eddie xinetd[5795]: START: tftp pid=8855 from=192.168.1.203

This gives me some info that it is starting out OK.
Maybe add "/sbin/syslogd -m 0 -R 192.168.1.100" <or whatever your server's address is> to the /etc/rc.d/rc.sysinit file (use it to replace "/sbin/syslogd") for the fe.

I don't quite follow what you're asking me to do here. Are you asking me to replace a file within the minimyth distribution?
Sorry for the poor description. In the /etc/rc.d/rc.sysinit file there is a line "/sbin/syslogd". Replace that line with "/sbin/syslogd -m 0 -R 192.168.1.100" <or whatever your server's address is>. That will send the log info to the server's /var/log/messages file, for your review.

Good luck. Let us know how you do.

Joe Henley

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Thu Nov 10, 2011 5:29 pm
by thekorn
JoeHenley wrote:At the start of the dhcp activity I see stuff like:
Nov 7 08:55:40 Eddie dhcpd: DHCPDISCOVER from <client A> via eth0
Nov 7 08:55:40 Eddie dhcpd: DHCPOFFER on <server> to <client A> via eth0
Nov 7 08:55:42 Eddie dhcpd: DHCPREQUEST for <server> (xxx.xxx.xxx.xxx) from <client A> via eth0
Nov 7 08:55:42 Eddie dhcpd: DHCPACK on <server> to <client A> via eth0
Nov 7 08:55:42 Eddie xinetd[5795]: START: tftp pid=8855 from=192.168.1.203

This gives me some info that it is starting out OK.
How are you even doing that?? This makes no sense to me; remote syslog is a UDP based service, but because you're sending out DHCP you shouldn't have an IP address yet!

(Unless you're logging to the same machine, in which case it makes sense but is a moot point.)

On a working client, the first lines I see on my syslog server are...

Code: Select all

2011-11-10 10:17:46	User.Debug	172.18.0.147	Nov 10 10:17:35 kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
2011-11-10 10:17:46	User.Info	172.18.0.147	Nov 10 10:17:35 kernel: input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input2
2011-11-10 10:17:46	User.Info	172.18.0.147	Nov 10 10:17:35 kernel: ENS1371 0000:02:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
2011-11-10 10:17:46	Local0.Info	172.18.0.147	Nov 10 10:17:35 minimyth: starting CPU frequency scaling ...
2011-11-10 10:17:46	Local0.Info	172.18.0.147	Nov 10 10:17:35 minimyth: starting virtual console ...
2011-11-10 10:17:46	Local0.Info	172.18.0.147	Nov 10 10:17:35 minimyth: starting telnet server ...
2011-11-10 10:17:46	Local0.Info	172.18.0.147	Nov 10 10:17:35 minimyth: configuring ssh server ...
2011-11-10 10:17:46	Local0.Info	172.18.0.147	Nov 10 10:17:35 minimyth: enabling udev hotplug scripts ...
2011-11-10 10:17:46	Local0.Info	172.18.0.147	Nov 10 10:17:35 minimyth: starting cron ...
2011-11-10 10:17:46	Local0.Info	172.18.0.147	Nov 10 10:17:35 minimyth: configuring MythTV master backend communication ...
2011-11-10 10:17:51	Local0.Info	172.18.0.147	Nov 10 10:17:40 minimyth: installing binary codecs ...
...and from then on who cares as it's clearly booting. But this is all happening far after DHCP has re-fetched the IP address.
Sorry for the poor description. In the /etc/rc.d/rc.sysinit file there is a line "/sbin/syslogd". Replace that line with "/sbin/syslogd -m 0 -R 192.168.1.100" <or whatever your server's address is>. That will send the log info to the server's /var/log/messages file, for your review.
OK, I'm following you, but I don't know how to affect that change. I can telnet into a running minimyth client and change it, but it doesn't survive a reboot since it just pulls the stock FS from the tftp server.

More to the point, I think this may be a red herring. Since minimyth is not finding the network card at all (or at least, that's what it says on the blue progress screen), it can't possibly re-do DHCP over it, and as a result can't possibly send syslog messages over the network.

That they keyboard interface is dead when minimyth boots up is really killing the debug process; any suggestions on that end? It works otherwise (with a live CD, in the bios, etc.) so it's only minimyth that's doing a hard faceplant.

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Thu Nov 10, 2011 8:17 pm
by JoeHenley
At the start of the dhcp activity I see stuff like:
Nov 7 08:55:40 Eddie dhcpd: DHCPDISCOVER from <client A> via eth0
Nov 7 08:55:40 Eddie dhcpd: DHCPOFFER on <server> to <client A> via eth0
Nov 7 08:55:42 Eddie dhcpd: DHCPREQUEST for <server> (xxx.xxx.xxx.xxx) from <client A> via eth0
Nov 7 08:55:42 Eddie dhcpd: DHCPACK on <server> to <client A> via eth0
Nov 7 08:55:42 Eddie xinetd[5795]: START: tftp pid=8855 from=192.168.1.203

This gives me some info that it is starting out OK.

How are you even doing that?? This makes no sense to me; remote syslog is a UDP based service, but because you're sending out DHCP you shouldn't have an IP address yet!

(Unless you're logging to the same machine, in which case it makes sense but is a moot point.)
My Myth server is also my dhcp, boot, and tftp server. This clip is from the messages file of that server. So in retrospect, my suggestion on this one may not be too useful. Does your dd-wrt router give you any log info? If you get REALLY desperate, I suppose you could briefly hook up your myth server as your dhcp server, but .... ugh!
Sorry for the poor description. In the /etc/rc.d/rc.sysinit file there is a line "/sbin/syslogd". Replace that line with "/sbin/syslogd -m 0 -R 192.168.1.100" <or whatever your server's address is>. That will send the log info to the server's /var/log/messages file, for your review.

OK, I'm following you, but I don't know how to affect that change. I can telnet into a running minimyth client and change it, but it doesn't survive a reboot since it just pulls the stock FS from the tftp server.
On the server, dig thru to the /tftpboot/minimyth-<ver>/rootfs-ro/etc/rc.d/rc.sysinit.sh file. Look in there to make the change.
More to the point, I think this may be a red herring. Since minimyth is not finding the network card at all (or at least, that's what it says on the blue progress screen), it can't possibly re-do DHCP over it, and as a result can't possibly send syslog messages over the network.
Well, since it's getting to the point to start MiniMyth, you know the nic is working. The issue looks to be "only" getting MM to recognize it. Have you tried changes in the MM configuration and dhcp sections in minimyth.conf. Have you checked the bios on the Shuttle for any screwball settings? I'm sure you have, but I'm just throwing out ideas here.
That they keyboard interface is dead when minimyth boots up is really killing the debug process; any suggestions on that end?
If it were I, and if the Shuttle has a "standard kb" connector, I'd try a "standard kb." I've had plenty of problems with a "fussy" boot and a USB kb. Those two things seem to feed off each other. Sometimes there are bios settings which will help that problem (legacy keyboard/mouse things).

While on the subject of "just throwing out ideas....." My current desktop, while booting up, gives me a message about an option to modify how it does a pxe boot. IIRC, I can even turn it (pxe boot) off from that option. Have you checked that on the Shuttle?

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Fri Nov 18, 2011 10:46 pm
by thekorn
JoeHenley wrote:My Myth server is also my dhcp, boot, and tftp server. This clip is from the messages file of that server. So in retrospect, my suggestion on this one may not be too useful. Does your dd-wrt router give you any log info? If you get REALLY desperate, I suppose you could briefly hook up your myth server as your dhcp server, but .... ugh!
I can set my dd-wrt to syslog to a remote server, but ... I really don't think DHCP is the problem. Worst case I could sniff the traffic if you really think DHCP is the culprit, but since minimyth is complaining that it can't find the network adapter at all, I don't have much hope.
On the server, dig thru to the /tftpboot/minimyth-<ver>/rootfs-ro/etc/rc.d/rc.sysinit.sh file. Look in there to make the change.
Interesting! That area isn't changeable for me...

Code: Select all

Mythtery:/tftpboot$ cd ram-minimyth-0.24.1-77
Mythtery:/tftpboot/ram-minimyth-0.24.1-77$ ls -l
total 116540
drwxr-xr-x 8 root root      4096 2011-06-06 23:14 html
-rw-r--r-- 1 root root   2538976 2011-06-06 23:14 kernel
-rw-r--r-- 1 root root      3694 2011-06-06 23:30 minimyth.md5
-rw-r--r-- 1 root root 116654080 2011-06-06 23:30 rootfs
drwxr-xr-x 2 root root      4096 2011-06-06 23:14 scripts
drwxr-xr-x 2 root root      4096 2011-06-06 23:29 themes
-rw-r--r-- 1 root root        10 2011-06-06 23:14 version
rootfs is just a regular old... file.
Well, since it's getting to the point to start MiniMyth, you know the nic is working. The issue looks to be "only" getting MM to recognize it. Have you tried changes in the MM configuration and dhcp sections in minimyth.conf. Have you checked the bios on the Shuttle for any screwball settings? I'm sure you have, but I'm just throwing out ideas here.
Yup, nothing in the BIOS except for one option regarding the wireless card. (Well, and the option on whether or not I WANT to net boot it, but I'm pretty sure I have that set correctly! :mrgreen: )
If it were I, and if the Shuttle has a "standard kb" connector, I'd try a "standard kb." I've had plenty of problems with a "fussy" boot and a USB kb. Those two things seem to feed off each other. Sometimes there are bios settings which will help that problem (legacy keyboard/mouse things).
Yeah, unfortunately no dice there, it's USB or GTFO. I did try a different USB keyboard to no different effect.
While on the subject of "just throwing out ideas....." My current desktop, while booting up, gives me a message about an option to modify how it does a pxe boot. IIRC, I can even turn it (pxe boot) off from that option. Have you checked that on the Shuttle?
There are a couple of minimal options, mainly just selecting what to boot from... SD card, PXE boot, internal hard drive... just your fairly standard boring stuff, really. It's an Intel BIOS, so the BIOS is pretty straight ahead.



Just stumbled across the supported hardware doc, don't know why I didn't look at this before. Guess I'm SOL running minimyth on this thing, as the ethernet controller uses the jme driver for linux. Damn.

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Mon Nov 21, 2011 7:09 pm
by Pablo
I have added the JME driver. It will be in the next build.

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Mon Nov 21, 2011 10:57 pm
by thekorn
Pablo wrote:I have added the JME driver. It will be in the next build.
Hey, that's great news; thanks!

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Tue Nov 29, 2011 10:57 pm
by thekorn
As a follow-up, upgraded to 0.24.1-78, fixed the whole thing right up. Thanks again, Pablo!

Re: No Network Adaptor found -- even though I'm net booting!

Posted: Wed Nov 30, 2011 7:12 am
by Pablo
I am glad it worked.