Bug 145395 - Network card not properly configured in Dell D610
Summary: Network card not properly configured in Dell D610
Status: VERIFIED WORKSFORME
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 1
Hardware: x86 SUSE Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Martin Vidner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-25 05:17 UTC by dante bly
Modified: 2006-04-20 20:47 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dante bly 2006-01-25 05:17:59 UTC
Can't access the Internet since the network card is not properly detected. YAST says the name of the card is Dell Latitude D610. 

I think the laptop uses the following network card:

NetXtreme BCM5751 Gigabit Ethernet PCI Express

The Internet worked fine with Suse 10.0.
Comment 1 Martin Vidner 2006-01-25 14:41:05 UTC
Please attach the logs: http://www.opensuse.org/Bug_Reporting_FAQ#YaST
Comment 2 dante bly 2006-01-26 03:10:10 UTC
I've created y2logs.tgz but there is no way to get it off the computer. The internet doesn't work as I've already mentioned. When I plug in a USB drive, I get the following error:

mount: according to mtab, /dev/sdb1 is already mounted on /media/usbdisk

When I try to access the cdrom, I get the following error:

mount: according to mtab, /dev/sr0 is already mounted on /media/cdrom
mount failed

I've already submitted a bug report for this. 

I'll wait to see if beta2 resolves these issues.
Comment 3 Gerald Pfeifer 2006-04-20 20:29:50 UTC
Sorry, but we've now been waiting for this information for close to
three months.  Without this input, we cannot do anything about it.

If you have an update for us, either way (works / still does not work),
we'll certainly appreciate that.
Comment 4 dante bly 2006-04-20 20:47:27 UTC
I forgot about this bug. Sorry about that. This problem occurred in Beta 1 but was resolved in later Betas.