Dhcpcd errors [ioctl]
 

hi all,

i just recompiled my 2.4.22 kernel, and now i am getting some weird messages when i boot up, mainly pertaining to my NIC.

here is it...

Dhcpcd [162]: DhcpStart: iotcl SIOCSIFFLAGS: invalid argument

Dhcpcd [170]: DhcpStart: iotcl SIOCSIFFLAGS: invalid argument


thats the output from dmesg. i compiled my NIC (both on borad and PCI) as modules, and it appears that they are being loaded, but it says that they are unused, and when i run both

dhcpcd eth0
dhcpcd eth1

to start the dhcp client, they do not do anything at all, it acts exactly like whenyou just press return, it goes to the next line and waits for a command. ANy help on this subject is very much appreciated. If any other info is needed, please let me know and I will post it up here...thanks again.

something to try
 

Greetings,
There are a couple things to try:
in /etc/dhcpc try dumping everything but the *.exe file and rerunning /etc/rc.d/rc.inet1

Type in dhcpcd and see if you get any errors.

Lastly check your /etc/rc.d/rc.inet1.conf file and ensure that the ethX entries are set to dhcp

lsmod to see whether ur compiled module is installed, see /etc/rc.d/rc.modules for how u can have it loaded automatically during boot time. Maybe can try insmod nicmodule.o first.

/sbin/dhcpcd -t 10 -d eth0
/sbin/dhcpcd -t 10 -d eth1
ifconfig -a

Btw, it is better to have nicmodules built into kernel rather than as module, y u want the opposide ?

Re: Dhcpcd errors [ioctl]
 

What type of NIC is this?

thanks to everyone who responded....i am not at my house right now I had to come home from college for a family thing, so i wont be able to see if any of these suggestions worked, but i will keep you informed. But i will answer your questions, cause maybe they will help you help me out if these suggestions dont wind up ixing my problem....

i have a SOYO KT400 MB with the VIA-RHINE onboard NIC, as well as a NetGear PCI NIC. I am not sure of the exact one that it is, however it uses the tulip driver, and the VIA uses the via-rhine driver. I have had both working previous to my recompile of the 2.4.22 kernel. During the boot process, I can see that the kernel has detected the cards, and loads the modules for both, i confirmed this with lsmod. By the way, i keep them comiled as kernels, so that if i am not using one then i can unload the support, and vica versa. I have never had a problem with anything like this so far, and hopefully when i fix it I wont again. As I said before, as soon as i get home tomorrow afternoon I will try out subekk0's suggestion and see what it yields.

I too seem to be having a similar problem. I am on a soyo sy-k7v dragon+ with a via rhine card at eth0. I can see the via-rhine module, and I see two other modules that say they "depend on via-rhine" they are: mii, and crc32. I am running slackware 9.1 (with "everything installed", and the bareacpi kernel from the CD)

The oddest thing is that I can ping my router/surf the net--periodically. I am able to ping my router and surf for about 30 seconds when I do the following:
ifconfig eth0 down
rmmod via-rhine
insmod via-rhine
ifconfig eth0 up

If I do this consecutively, it works about %20 of the time--the other %80 it does absolutely nothing?!?!


I loaded Slack 9.1 on another of my computers with the exact same setup paramaters, and it uses dhcpcd with no problems (I am writing this from my second box).

I have loaded RH9 on the soyo dragon+, and the NIC works flawlessly (I just HATE redhat, so I wanna fix this).

any help is appreciated!

sadwart, i would say to try the things that were suggested above, remove all the files except the *.exe from /etc/dhcpc and see if that helps. It's worked for me, and also i compiiled my NIC's into the kernel, i didn't use modules, which might make a small difference. good luck, i hope that i helped you out in some way...

The more I mess around, the less this seems to be a similar situation--I am using a fresh install, and don't have anything inside my /etc/dhpc folder other than a .exe file. It seems to me that any NIC I try on this particular board fails to be able to "ping out" for any extended period of time.

I just disabled my internal NIC, and put a D-Link w/ a realtek chip into an empty pci slot--and I seem to have the exact same problem. My dmesg output concerning the D-Link was as follows:
8139too Fast Ethernet driver 0.9.26
eth0: D-Link DFE-538TX (RealTek RTL8139) at 0xd88c8000, 00:05:5d:44:0e:c5, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139C'

I am still a very new newbie--and tried compiling a kernel last night--I did OK, and got the system to boot, but I failed to get the Via-Rhine supported (I compiled it into the kernel, not as a module--and had NOT swapped my D-Link in yet :), but still no go. I also failed to get X to work--I was missing some kind of core device.

Does anyone have any advice, or any logs or messages that I might check to troubleshoot this problem?

Thanks :)

check the XServer Output, its located in /var/adm/XFree86.0.log and also /var/adm/syslog

So I seem to have found a way around the problem (and have only wasted shipping fees acquiring a different brand of WiFi NIC).

First I found the following thread here and here that detail the fact that the Wireless NIC that I bought has some kinda unpredictable results (btw, the card it a Trendware TEW-223PI). I immediately sent this card back to newegg for a refund.

After re-installing Slack 9.1, I had similar problems w/ my intigrated NIC. Oddly enough, I had no problems with the Trendware or the built in when I ran RH9, but I hate Red Hat--and liked everything about slack other than the fact that I couldn't get my NICs to work. The board is a Soyo sy-k7v dragon plus and it's integrated NIC is a via-rhine chip.

So I put in a D-Link NIC and disabled the onboard--still couldn't get a ping out. However, after reinstalling Slackware with the onboard disabled, and the D-Link installed I finally met sucess.

I ordered a Netgear MA311 Wireless NIC, and put it in this evening. It was as smooth an install as I have ever done--I had the card booting with my essid and WEP key in less than an hour (and I have never successfully configured a wireless card w/ slackware until tonight).

The moral of the story is--find a card that doesn't rely on semi-open source drivers, and I personally won't probably buy from Soyo anymore.

Thanks for everyone's help!

Its Problem with the ACPI of bios
just recompile the kernel and disable ACPI
i got the same problem on my dragon kt 333
since you cant disable ACPI from the bios, the only way is to recompiling the kernel without the ACPI.
it will work fine :)

I Think this is a great shit of SOYO
i got similar problem in Binblows too
its a pain in the ass.

you know the really obnoxious thing--my FDD doesn't work--and it never has with this mobo. If I toss it into my tyan system, I can boot from it no prob, but on the soyo--it just WON'T boot.

Funny thing is, when I emailed Soyo to tell them that I couldn't get the FDD to boot on THEIR Mobo, they told me to flash the BIOS (how do I do this w/out a FDD???? I guess I could burn a CD, but still)

Anyone have any similar probs now that this thread has become a Soyo bash?