Bug 434308 - TOSHIBA TX/3516: e100 won't link up on 2.6.24.2-10.fc8
TOSHIBA TX/3516: e100 won't link up on 2.6.24.2-10.fc8
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
8
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-22 10:57 EST by Mamoru TASAKA
Modified: 2008-03-01 08:50 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-01 08:50:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
dmesg on 2.6.24.2-10.fc8 (22.07 KB, text/plain)
2008-02-22 10:57 EST, Mamoru TASAKA
no flags Details
dmesg on 2.6.23.14-107.fc8 (19.94 KB, text/plain)
2008-02-22 10:58 EST, Mamoru TASAKA
no flags Details

  None (edit)
Description Mamoru TASAKA 2008-02-22 10:57:48 EST
Description of problem:
With my laptop (Toshiba TX/3516) my network eth0 (acutally e100)
won't link up on 2.6.24.2-10.fc8

With 2.6.23.14-107.fc8 network links up normally

Version-Release number of selected component (if applicable):
kernel-2.6.24.2-10.fc8.i686

How reproducible:
100%

Steps to Reproduce:
1. boot with 2.6.24.2-10.fc8
2.
3.
  
Actual results:
dmesg attached

Expected results:
link up as 2.6.23.14-107.fc8 (dmesg attached)

Additional info:
Comment 1 Mamoru TASAKA 2008-02-22 10:57:48 EST
Created attachment 295642 [details]
dmesg on 2.6.24.2-10.fc8
Comment 2 Mamoru TASAKA 2008-02-22 10:58:44 EST
Created attachment 295643 [details]
dmesg on 2.6.23.14-107.fc8
Comment 3 Mamoru TASAKA 2008-03-01 08:50:01 EST
It seems that it is okay after I set up network configuration
after booting with 2.6.24 kernel again.

Note You need to log in before you can comment on or make changes to this bug.