Rodolfo Medina rodolfo.med...@gmail.com writes:
The ethernet port of my Hyundai laptop, that used to work fine, seems to be
dead. At boot, I get the following message:
Setting up networking
Configuring network interfaces...SIOCSIFADDR: No such device
eth1: ERROR while getting interface
Dne, 03. 11. 2010 19:13:02 je Rodolfo Medina napisal(a):
A few weeks ago I started the present thread. The messages from this
list
seemed to conclude that it was a hardware problem and no remedy to
make it
work. Then I bought a new usb ethernet port and upgraded the kernel
to
On Vi, 22 oct 10, 14:58:12, Rodolfo Medina wrote:
I'm attaching the file ethernet-enquiry.tar.gz, that you can unpack with `tar
xzvf ethernet-enquiry.tar.gz'. It's only 12Kb. There are all those outputs:
dmesg
ifconfig -a
uname -a
modprobe sis990
lspci -nnk
for the two different
Andrei Popescu andreimpope...@gmail.com writes:
On Vi, 22 oct 10, 14:58:12, Rodolfo Medina wrote:
I'm attaching the file ethernet-enquiry.tar.gz, that you can unpack with
`tar xzvf ethernet-enquiry.tar.gz'. It's only 12Kb. There are all those
outputs:
dmesg
ifconfig -a
uname -a
On Sb, 23 oct 10, 11:48:59, Rodolfo Medina wrote:
`modprobe sis900' gets no output at all; the output of `ifconfig -a' is the
one
I sent in the file `ethernet-enquiry.tar.gz'.
Hmm, no output usually means no error. Anything new showing in dmesg?
As a sidenote, you might want to upgrade
Andrei Popescu andreimpope...@gmail.com writes:
On Sb, 23 oct 10, 11:48:59, Rodolfo Medina wrote:
`modprobe sis900' gets no output at all; the output of `ifconfig -a' is the
one I sent in the file `ethernet-enquiry.tar.gz'.
Hmm, no output usually means no error. Anything new showing in
On Sb, 23 oct 10, 14:46:18, Rodolfo Medina wrote:
Andrei Popescu andreimpope...@gmail.com writes:
On Sb, 23 oct 10, 11:48:59, Rodolfo Medina wrote:
`modprobe sis900' gets no output at all; the output of `ifconfig -a' is the
one I sent in the file `ethernet-enquiry.tar.gz'.
Hmm, no
Andrei Popescu andreimpope...@gmail.com writes:
@Rodolfo, could you please post the output of 'lspci -nnk', preferably
only the part relevant to the SiS Ethernet controler.
On Mi, 20 oct 10, 13:11:38, Rodolfo Medina wrote:
For Etch, the `k' option is not valid: so I used Knoppix.
To
Andrei Popescu andreimpope...@gmail.com writes:
@Rodolfo, could you please post the output of 'lspci -nnk', preferably
only the part relevant to the SiS Ethernet controler.
For Etch, the `k' option is not valid: so I used Knoppix.
To be sure, I posted the whole output of 'lspci -nnk' to:
On Mi, 20 oct 10, 13:11:38, Rodolfo Medina wrote:
Andrei Popescu andreimpope...@gmail.com writes:
@Rodolfo, could you please post the output of 'lspci -nnk', preferably
only the part relevant to the SiS Ethernet controler.
For Etch, the `k' option is not valid: so I used Knoppix.
Andrei Popescu andreimpope...@gmail.com writes:
Here's your network card. Very interesting that it didn't show up in
the grep... are you aware of any differences (for example booting with
a different kernel)?
Could you please let us see the full output of 'dmesg'. If you are
worried about
On Tue, 19 Oct 2010 11:23:02 +0200, Rodolfo Medina wrote:
Andrei Popescu writes:
Here's your network card. Very interesting that it didn't show up in
the grep... are you aware of any differences (for example booting
with a different kernel)?
Could you please let us see the full output of
On Ma, 19 oct 10, 09:56:28, Camaleón wrote:
@Andrei, could it be related to this old bug?
ip1394 not needed and causing trouble
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=238979
I'd say not, that bug looks more like a naming issue, but blacklisting
that module is worth a try anyway.
Camaleón noela...@gmail.com writes:
On Sun, 17 Oct 2010 13:46:07 +0200, Rodolfo Medina wrote:
What is the brand and model of your motherboard?
I don't know... How can I work that out?
As root: dmidecode -t 2
Here it the output of dmidecode -t 2:
# dmidecode 2.8
SMBIOS 2.3 present.
Greg Madden p...@gci.net writes:
One thing to be absolutely sure about is that the device is on a hardware
compatibility list (hcl) or has positive Linux reviews.. I don't use such
devices but in my experience, a device needs to be shown to work reliably
with a kernel version, by more than
On Mon, 18 Oct 2010 14:05:20 +0200, Rodolfo Medina wrote:
Camaleón writes:
As root: dmidecode -t 2
Here it the output of dmidecode -t 2:
# dmidecode 2.8
SMBIOS 2.3 present.
Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Uniwill
Product Name:
On Lu, 18 oct 10, 14:06:08, Rodolfo Medina wrote:
Here it is the output of `lspci':
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 03)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL
On Mon, 18 Oct 2010 18:35:37 +0200, Rodolfo Medina wrote:
On Lu, 18 oct 10, 14:06:08, Rodolfo Medina wrote:
Here it is the output of `lspci':
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900
PCI Fast Ethernet
(rev 91)
Andrei Popescu andreimpope...@gmail.com
Camaleón noela...@gmail.com writes:
On Mon, 18 Oct 2010 18:35:37 +0200, Rodolfo Medina wrote:
On Lu, 18 oct 10, 14:06:08, Rodolfo Medina wrote:
Here it is the output of `lspci':
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900
PCI Fast Ethernet
(rev 91)
Andrei
On Lu, 18 oct 10, 21:29:55, Rodolfo Medina wrote:
It seems that I don't manage to use that page. Then I'm attaching dmesg.
The file is empty as well. Try:
dmesg dmesg.txt
and then attach the file dmesg.txt
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
Greg Madden gomadtr...@gci.net writes:
On Saturday 16 October 2010 10:57:30 Rodolfo Medina wrote:
Morgan Gangwere 0.fracta...@gmail.com writes:
dmesg | grep eth gives the folloing output:
eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
On Sat, 16 Oct 2010 16:15:12 +
On Sat, 16 Oct 2010 20:30:24 +0200, Rodolfo Medina wrote:
Camaleón writes:
But... what kind of device is that? Are you using an adapter (firewire
to ethernet)? :-?
I can't answer to this question. . The file
/etc/udev/rules.d/z25_persistent-net.rules is the following:
# Firewire
On Sat, 16 Oct 2010 20:30:24 +0200, Rodolfo Medina wrote:
The file /etc/udev/rules.d/z25_persistent-net.rules is the following:
# Firewire device 00030d53255c8616 (ohci1394) SUBSYSTEM==net,
DRIVERS==?*, ATTRS{address}==00:03:0d:53:25:5c:86:16, NAME=eth0
# PCI device 0x1039:0x0900 (sis900)
On Sun, 17 Oct 2010 13:46:07 +0200, Rodolfo Medina wrote:
What is the brand and model of your motherboard?
I don't know... How can I work that out?
As root: dmidecode -t 2
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
Camaleón noela...@gmail.com writes:
On Sun, 17 Oct 2010 13:46:07 +0200, Rodolfo Medina wrote:
What is the brand and model of your motherboard?
I don't know... How can I work that out?
As root: dmidecode -t 2
All right, I'll post it as soon as I get home.
Do you think there are hopes
On Sun, 17 Oct 2010 15:57:46 +0200, Rodolfo Medina wrote:
Camaleón writes:
As root: dmidecode -t 2
All right, I'll post it as soon as I get home.
Do you think there are hopes the ethernet device can be saved?
While the system cannot detect it, there is no chance :-(
If it's and
On Sunday 17 October 2010 01:40:44 Rodolfo Medina wrote:
Greg Madden gomadtr...@gci.net writes:
On Saturday 16 October 2010 10:57:30 Rodolfo Medina wrote:
Morgan Gangwere 0.fracta...@gmail.com writes:
dmesg | grep eth gives the folloing output:
eth1394: eth0: IEEE-1394 IPv4 over
Dne, 17. 10. 2010 19:39:05 je Greg Madden napisal(a):
Time spent on compatibility is far shorter than time trying to get
some device
with a unknown chipset working.
Or money spent on replacing it with a working one ...
+1
--
Regards,
Klistvud
Certifiable Loonix User #481801
you could try using any live cd (e.g. debian live cd) to see if it is the
software/hardware that are problematic
2010/10/16 Rodolfo Medina rodolfo.med...@gmail.com
The ethernet port of my Hyundai laptop, that used to work fine, seems to be
dead. At boot, I get the following message:
Setting
On Sat, 16 Oct 2010 12:15:06 +0200, Rodolfo Medina wrote:
(please, open a new thread if you change the thematic of the e-mail)
The ethernet port of my Hyundai laptop, that used to work fine, seems to
be dead. At boot, I get the following message:
Setting up networking
Configuring
Rodolfo Medina rodolfo.med...@gmail.com writes:
The ethernet port of my Hyundai laptop, that used to work fine, seems to be
dead. At boot, I get the following message:
Setting up networking
Configuring network interfaces...SIOCSIFADDR: No such device
eth1: ERROR while getting interface
On Sat, 16 Oct 2010 16:41:05 +0200, Rodolfo Medina wrote:
(...)
Umarzuki Mochlis umarz...@gmail.com writes:
you could try using any live cd (e.g. debian live cd) to see if it is
the software/hardware that are problematic
Camaleón writes:
(please, open a new thread if you change the
Dne, 16. 10. 2010 18:15:12 je Camaleón napisal(a):
With Knoppix 6.0, I ran `ifconfig -a' and got the following output:
loLink encap:Local Loopback
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX
packets:0 errors:0
Rodolfo Medina rodolfo.med...@gmail.com writes:
The ethernet port of my Hyundai laptop, that used to work fine, seems to be
dead. At boot, I get the following message:
Setting up networking
Configuring network interfaces...SIOCSIFADDR: No such device
eth1: ERROR while getting
On Sat, 16 Oct 2010 20:30:24 +0200 Rodolfo Medina wrote:
[...]
Had any electrical storms? Switches that have been acting up? New
carpeting? Power outages? Brownouts? Etc?
Sounds like the device is busted, frankly.
--
Morgan Gangwere
PGP Key at http://indrora.homelinux.org/gpg_key.asc
BOFH
35 matches
Mail list logo
