SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
nice to meet a man with my problem...I thougt the problem was only with italians...
if you red the topic you will know that it is for long time I used the patience of the senior members of this forum. Now, I will try to cancel the packet DHCPCD (perhaps a conflict with DHCP...), the packet DHCP (I will run netconfig with IP static), and eventually I cancel 10.2 and try to install Slack 10. I will post the result.
perhaps it's an issue with the kernel/module and not with dhcpcd itself??
maybe a BIOS issue??
all of you with the problem are using a realtek 8139 card, right?? what revision??
what kernel versions are you guys using?? pre-compiled or self-compiled??
BTW, i am using an RTL-8139 (rev 10) card also (and a sis900), with a DHCP configured connection on the 8139, using dhcpcd... it works fine here... i am using kernel 2.4.33-pre1, but i never had dhcpcd problems with either 2.4.32/31/30/29 etc...
Location: Bulgaria, the small and peaceful town of Razlog
gusgoose_it.. it happens to bulgarians too man
but now i've fixed it... finally. i had 2 NICs and the first one (build-in) was broken and i forgot to disable it from the BIOS. when i ran netconfig it configured my broken NIC so i could get a respond from the dhcp. so i disabled it and i made a full re-intall of slackware. in netconfig i choose DHCP without entrying dhcp host and here i am writtin this post so it was a hardware problem afterall.......
my /etc/rc.d/rc.netdevice looks like:
i guest that's how your looks like
do you have other NICs installed? or maybe the problem commes from the NIC you're using. good luck my friend. i'll try to help with all i can
wow!!! now it works!!! I installed Slack 10, I doesnt run netconfig, I edited manually rc.inet1.conf by put "yes" on "USE_DHCP" and it works (I dont know why)
againstall: P.S. what is NIC ?
win32sux: I use only precompiled kernel, I doesnt change BIOS (one week ago Klaxs worked with the same BIOS) I hope you will know what happens, I post some useful things. Now I will try to install (sixth time...)Slack 10.2
notice how the module wasn't getting used on 10.2, yet on 10.0 it is...
so if you wanna get it to work on 10.2 you need to focus on the kernel IMHO... i'd say compile yourself a 2.4.32 (the lastest 2.4 stable release at the time of this post) or a 2.4.33-pre1 (the latest 2.4 prepatch at the time of this post) and see if it helps... if it doesn't, well, it's time to research/google about this to see if it's a known-issue or what the deal is...
hey i just saw in this thread a suggestion for appending the "noapic" kernel boot option to deal with an 8139too issue...
i'm not sure if it's what's happening to you in 10.2, but if you want to get your 10.2 working then i'd say it's worth a shot... i guess you could also try disabling ACPI in the BIOS to see if it helps... in fact, if you aren't using ACPI then you should probably have it disabled anyways...
for the "noapic" just edit your lilo.conf and add noapic to the "append" part (between the quotes)... then execute lilo with a "lilo -v"...
is your 8139 card an integrated one?? or is it in a pci slot?? i ask cuz most of the reports i've googled similar to yours are with integrated 8139s...
something you might wanna check is that the "PNP OS" option in your BIOS is set to "No"...
oh, and another boot option you could try is the "acpi=off" one...
halleluiah, slack 10.2 works!!!
On BIOS I disabled the option PnP OS, I installed Slack 10.2 (the 14th time...) without netconfig, then I edited the file inet1.conf putting "yes" on USE_DHCP", I decommented on rc.modules sbin/modprobe 8139too and it works!!!
that's incredible, but the only thing I made compared to the past 13 attempts is disable the PnP OS on BIOs!
win32sux: thanks for your patience, I confess that without you I passed out slackware
A cup of coffee to you!!!
to all: I was a pleasure to meet you into this international forum