he netwoork mananger no the the conex'ao bridge in the network card SIS 190, problem in the script

Bug #174875 reported by kamaraopoa
2
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-panel

The netwoork mananger not think the connection bridge on the network card onboard SIS 190, problem in the script

ProblemType: Bug
Architecture: i386
Date: Sat Dec 8 11:36:24 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.20.0.1-0ubuntu6
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-config-prefix /gnome-panel-YMkAdF/ --sm-client-id 117f000101000119508334600000054160000 --screen 0
ProcCwd: /home/edson
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
Uname: Linux edson-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
kamaraopoa (kamaraopoa) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your comments. This does not appear to be a bug report as such. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. http://launchpad.net/support

Changed in gnome-panel:
status: New → Invalid
Revision history for this message
kamaraopoa (kamaraopoa) wrote : Re: [Bug 174875] Re: he netwoork mananger no the the conex'ao bridge in the network card SIS 190, problem in the script
Download full text (7.1 KiB)

First, I will show how we can get a full report of the problem, so that
in other forums of life can help us. Then, the more adventurous, I
decided to show my problem and did the network of such PC work in
Ubuntu. Who knows you can not solve your problem as well?
Most of the following commands to be executed as root. In Ubuntu you can
run as root adding the command "sudo" before the command, or using the
command "sudo su" to login as root. In other distribution, use the
command "su -" to gain root access.

Step 1: collecting information on the problem

The first thing to do is to discover how the system sees the hardware
problem. There is no advance in the forum say that your network card of
the SIS is not working. It must describe the model, and this information
can you get with `` lspci. It will list your network card, your video
card, modem and other devices, something fine. Here we go:

# Lspci - nn

00:04.0 Ethernet controller [0200]: Silicon Integrated Systems (SIS) 190
Gigabit Ethernet Adapter [1039:0190] (rev 01)

Seen? Placed only the line of the network card not to pollute the text,
but you should learn more about ten lines. Look problem and the hardware
store and two paragraphs in particular: the first block of numbers that
appears - in the case there from above, the "00:04.0" - and the ID of
the device-in finalzinho, in brackets: 1039:0190.
The module of the hardware problem
Is the module of the device was loaded? Furthermore ... What is the
module him? To discover this we use the ID of the device (in my case, as
we saw above, is 1039:0190).
The ID of the device has two parts: the first four numbers (1039)
indicate the manufacturer (in our case the SIS). The last four (0190)
the model. To learn what is the driver of the device in question between
with this command, obviously replacing the numbers of their ID by:

# Modprobe-c | egrep'1039 .* 0190 '

Alias pci: v00001039d00000190sv * * sd bc * sc * i * sis190

The module is that there at the end of the line, the sis190. Does he is
charged? Enter the command "lsmod | grep sis190." If the command does
not return anything, try to manually load the module using the modprobe
sis190 "(always as root, do not forget). The module loaded, but the
network still does not work? Then continue reading.
Ask kernel: why the hardware does not work?
Now let's see what's happening with the hardware problem during boot
Linux. Therefore, we use the command `dmesg", which shows us the log
with all the "events" of the kernel during boot. But we peneirar the
result, for which only the lines relating to our hardware esquisitão
appear. Therefore, I will filter the output of dmesg by grep, asking him
to show us only the lines containing "00:04.0" - getting that number go
up with the command lspci - nn, remember? Be sure to replace the
"00:04.0" by the block of numbers on your hardware.

# Dmesg | grep'00: 04.0 '
0000:00:04.0: Read MAC address from APIC
0000:00:04.0: Can not find ISA bridge

A-ago, the network card does not find the ISA bridge! What this means? I
know there, the important thing is that the error is this. If you want
to do a search on google or ask for help in th...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.