From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7 Description of problem: I get error 8 when I try to connect to my ISP using new kernel (2.6.13-1.1526). Works fine with earlier kernels. Version-Release number of selected component (if applicable): system-config-network 1.3.26 How reproducible: Always Steps to Reproduce: 1. Boot with kernel-2.6.13-1.1526 2. Log in 3. Start Nework Device Control 4. Select "Activate" for ISP Actual Results: "Failure to activate . . . error 8" Expected Results: Activate connection with ISP Additional info:
Also won't work with kernel-2.6.13-1.1532
Error code: 8 The connect script failed (returned a non-zero exit status). I have no idea... Can you talk to your modem via e.g. "minicom" ?
I will chime in also with the same problem. Works in 2.6.12-1.1456_FC4 but not in 2.6.13-1.1526 or 1532. The problem seems to be with the network but I am sure the interfaces (DE500's) are working. The dhcp request just does not seem to be making it to the ISP (Shaw Cable in my case) but they are visible with tcpdump. The other DE500 set with static works fine. I have a system at work running 1532 with a couple of intel cards that works fine.
2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you.
(In reply to comment #4) > 2.6.14-1.1637_FC4 has been released as an update for FC4. > Please retest with this update, as a large amount of code has been changed in > this release, which may have fixed your problem. > > Thank you. > Still unable to connect
The same applies here. Is there anything else I can do to help get this resolved? It only seems to be a problem on my firewall system with a bare install "minimal with some other packages of necessity and some for convenience.) Still on 2.6.12-1.1456_FC4. This is the x86_64 release.
Are you using the stock iptables scripts that come with Fedora ? Or a third party firewall script ?
(In reply to comment #7) > Are you using the stock iptables scripts that come with Fedora ? Or a third > party firewall script ? > Not using third-party script.
Would you mind trying the fedora-netdev kernels? http://people.redhat.com/linville/kernels/fedora-netdev/ Please give those a try and post the results here...thanks!
Tried the 2.6.14-1.1637_FC4.netdev.2 but no success. I also tried a different ethernet card (3c595) and moving the de500 to a different slot. In the latter case I got a 'disabling irq 5' message after it tried to start eth0. Kernels since 2.6.13-1 have broken dhcp as a client and as a server. 2.6.12-1.1456_FC4 still works as expected. I do run custom iptables but still nothing happens when they are disabled. Something in UDP layer perhaps?
(In reply to comment #9) > Would you mind trying the fedora-netdev kernels? > > http://people.redhat.com/linville/kernels/fedora-netdev/ > > Please give those a try and post the results here...thanks! Tried the netdev kernels: No luck connecting.
Please attach the output of running "sysreport" on the box in question...thanks! Also, have you tried booting w/ "acpi=off" or "acpi=noirq" on the kernel command-line?
Ok. I have had success. I started with adding irqpoll to the boot and lo - I was able to get an address. I had done some bios mucking and one of the thing was to clear ESCD. Now the irqpoll, noacpi and acpi=noirq are not required, though the latter two did work on booting, but these were tried after the bios mucking.
Created attachment 121820 [details] sysreport output
(In reply to comment #12) > Please attach the output of running "sysreport" on the box in > question...thanks! > > Also, have you tried booting w/ "acpi=off" or "acpi=noirq" on the kernel > command-line? Output of "sysreport" sent. Now using kernel-smp-2.6.14-1.1644_FC4, neither "acpi=off" nor "acpi=noirq" allowed dialup connection: error 8 each time.
David, please look at comment 13. Have you tried using the "irqpoll" boot option? Have you tried clearing ESCD?
(In reply to comment #16) > David, please look at comment 13. Have you tried using the "irqpoll" boot > option? Have you tried clearing ESCD? "irqpoll" didn't allow dialup. I don't know anything about clearing ESCD, but should I be "mucking" with the BIOS if dialup works fine now with the earlier kernel?
This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you.
Closed due to lack of response...please reopen when the bug is verified against current kernels...thanks!