azambuja
08-10-2003, 01:18 PM
Hey guys! What's up??
I'm so very happy that I decided to post my deed here. This topic is just for bragging (I sinceriy apologize to the people who don't like that), and I'm sorry if I'm posting it in the wrong forum - I thought about putting it in the "How I did it!" but there is a place for howtos/guides/etc.
Today, after 3 days of testing, googling, looking around, etc, etc, etc, I finally got my NIC (Realtek 8139B) to work!
Here's the thing: I had this ethernet card wich I believe it's generic, with a RTL8139B chipset lying around. I'm not sure how it got here, I suspect I bought it some time ago. Anyways, I decided to install it just for fun. And that's when the problems started. As I have done before, I turned off the computer, inserted the NIC, rebooted. Got into the console, typed # insmod 8139too, and got some errors. My journey begun, I googled a lot, finally got to the conclusion that nobody else had ever had that problem, but it seemed to be something with my IO addres or IRQ. I thought that if I would specify the ioaddr and irq for the module the problem should solve itself, but apparently the module doesn't accept any of those options (weird eh? maybe I did something wrong).
More Googling, and I downloaded a diagnoses program called "rtl8139-diag", wich also didn't recognize my card, unless I specified the ioaddr. So, nowhere else to turn, I decided to look into the code of the 8139too.c (the module). As I'm not a programmer and I only knew a bit of basics (printf, scanf, just that) cause I've looked at a few codes before, I understood almost nothing. I decided too look into the the "rtl8139-diag.c" source-code, and finally, today, I solved the problem!!!
Conclusions: something was sort of wrong with my card (somehow my chipset it's not correctly recognized by the system, I have no clue how that happened, but all I know is that the line in the /proc/pci is not how it's supposed to be and the "pci device id" is wrong too, it's 8039, should be 8139).
So, I wanted to brag a little and thank this forum, because even known I never got to post anything and I'm new to the forum, I passed to admire the forum and it's users and decided not to post anything before I do my homework. :) If it had been any other forum, I would have posted my problem, nobody would have known anything, problem not even answered, and I'd have just given up. Thanks to this forum I had the desire to look for a solution myself, and because I solved the problem I'm very happy I did that.
Thanks for your time,
Fernando Azambuja
PS: maybe there's still something wrong with the card (I think there is), probably I'll get a lot of problems from it (like today: I finally did "insmod 8139too" with no message errors, the second I went to brag in the #justlinux, I typed a phrase and pressed enter, m y *****X closed with a "Illegal instruction" problem and now refuses to even open), but hey, I'm still happy
I'm so very happy that I decided to post my deed here. This topic is just for bragging (I sinceriy apologize to the people who don't like that), and I'm sorry if I'm posting it in the wrong forum - I thought about putting it in the "How I did it!" but there is a place for howtos/guides/etc.
Today, after 3 days of testing, googling, looking around, etc, etc, etc, I finally got my NIC (Realtek 8139B) to work!
Here's the thing: I had this ethernet card wich I believe it's generic, with a RTL8139B chipset lying around. I'm not sure how it got here, I suspect I bought it some time ago. Anyways, I decided to install it just for fun. And that's when the problems started. As I have done before, I turned off the computer, inserted the NIC, rebooted. Got into the console, typed # insmod 8139too, and got some errors. My journey begun, I googled a lot, finally got to the conclusion that nobody else had ever had that problem, but it seemed to be something with my IO addres or IRQ. I thought that if I would specify the ioaddr and irq for the module the problem should solve itself, but apparently the module doesn't accept any of those options (weird eh? maybe I did something wrong).
More Googling, and I downloaded a diagnoses program called "rtl8139-diag", wich also didn't recognize my card, unless I specified the ioaddr. So, nowhere else to turn, I decided to look into the code of the 8139too.c (the module). As I'm not a programmer and I only knew a bit of basics (printf, scanf, just that) cause I've looked at a few codes before, I understood almost nothing. I decided too look into the the "rtl8139-diag.c" source-code, and finally, today, I solved the problem!!!
Conclusions: something was sort of wrong with my card (somehow my chipset it's not correctly recognized by the system, I have no clue how that happened, but all I know is that the line in the /proc/pci is not how it's supposed to be and the "pci device id" is wrong too, it's 8039, should be 8139).
So, I wanted to brag a little and thank this forum, because even known I never got to post anything and I'm new to the forum, I passed to admire the forum and it's users and decided not to post anything before I do my homework. :) If it had been any other forum, I would have posted my problem, nobody would have known anything, problem not even answered, and I'd have just given up. Thanks to this forum I had the desire to look for a solution myself, and because I solved the problem I'm very happy I did that.
Thanks for your time,
Fernando Azambuja
PS: maybe there's still something wrong with the card (I think there is), probably I'll get a lot of problems from it (like today: I finally did "insmod 8139too" with no message errors, the second I went to brag in the #justlinux, I typed a phrase and pressed enter, m y *****X closed with a "Illegal instruction" problem and now refuses to even open), but hey, I'm still happy