ACPI and network on Toshiba note 349
Peter,
Pleae stop talking about ACPI! It is your NIC that is not doing what you want (probably not working), not ACPI. Yes, ACPI may be the cause of that, but...
I really apreciate your help, but first, let me tell you a few things: 1. Im not a lammer, I just dont have enought knowlege on ACPI 2. If I knew, it I wouldn't ask 3. I had tryied many things before posting here 4. If you're mad to me because I don't know how ACPI works, please stop answering, I really don't wan't to annoy you anymore. Maybe someone else who don't get annoyed by other's doubts can answer my question later.
Now, if you really want to continue helping me (I surelly do) let's be less aggressive. I help a lot of people on usenet on other subjects, and never was bold about my knowledge after all, you answer because you want, and just for that reason.
Subba Rao I think you have gone about this in a confabulated way, but you should be able to make a COPY (just in case) of your saved .mbx file you retrieved...
Peter T. Breuer
I'm not buttuming anything. I don't know if you got it but I'll explain again: I have two realities with my notebook:
1st: I boot it with 'acpi=off' and everything works well, network, dhcp, etc. I'm writting this post using my notebook, so I'm *very* sure that the dhcp is working well. Also, all config onetc-sysconfig are consistent, since I don't have to manualy setup my network.
2nd: I boot without 'acpi=off' and the dhcp fails to load. All interfaces were detected correctly (ifconfig shows all interfaces like: eth0, ath0, lo) but no IPs:
After rpm --rebuilddb i receive: error: rpmdbAdd: skipping h# 270 Header V3 DSA signature: BAD, key ID 700468 plus 16e error: rpmdbAdd: skipping h# 352 Header V3 DSA signature: BAD, key ID 700468 plus 16e...
$ ifconfig ath0 Link encap:Ethernet HWaddr 00:11:F5:A7:7D:5D inet6 addr: fe80::211:f5ff:fea7:7d5d-64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8376 errors:0 dropped:0 overruns:0 frame:0 TX packets:8971 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
eth0 Link encap:Ethernet HWaddr 00:C0:9F:F1:B5:AC inet6 addr: fe80::2c0:9fff:fef1:b5ac-64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 Interrupt:11 Base address:0xa000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1-128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:26 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
wifi0 Link encap:Ethernet HWaddr 00:11:F5:A7:7D:5D inet6 addr: fe80::211:f5ff:fea7:7d5d-64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:123877 errors:0 dropped:0 overruns:0 frame:137243 TX packets:9707 errors:10 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 Interrupt:11 Memory:df280000-df290000
That's the point, Peter, I had no idea of that. This is a really valuable information for me now, since I can continue with my debugging.
Jon Kennedy Indeed. Your hypothesis is entirely correct, and as one who setup sendmail so many times I wrote a program to do it for...
You're so bold that you don't even care understanding the problem... No matter how I call my interface, if it's still a network interface! I called it 'ath0' because it's my wireless Atheros device and that's the default name for Atheros devices.
I really tryied not to, but Linux seems to need it so hard... I grep'ed for IPV6 all overetc-sysconfig but couldn't find any place to turn it off... maybe you can explain me how to disable it.
Got me... no idea either...
First of all, I'm not using dhclient, I'm using dhcpd as a client. Second, ifup is the same as calling ifconfig, dhclient and setting routes, so no big deal using it.
Any way, for your confort, the call to ifconfig ath0 up is fine, it starts up the interface (as you should have guessed, since I told you that the devices are recognized and created nicely) but when I call the dhcp on it it just waits forever and times out.
Hello, Briefly, here is a bug that I may be confronted with and told to spend some time on. There are several embedded "time critical" programs on different machines (SGI, and Linux PC's and...
well, at the end, I could get a valuable information from all this, that the acpi messes a lot around how the hardware is interpreted by the kernel. I'll continue looking for it untill I have more real answers.
thank you! --rengolin
ACPI and network on Toshiba note 350
Linux groups from Newsgroups