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
linux-imag
Rodolfo Medina 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 flags: No such dev
On Sb, 23 oct 10, 14:46:18, Rodolfo Medina wrote:
> Andrei Popescu 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 u
Andrei Popescu 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 dmesg?
Here it is
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 upgr
Andrei Popescu 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
>> modprobe s
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 di
Andrei Popescu 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 be sure, I po
On Mi, 20 oct 10, 13:11:38, Rodolfo Medina wrote:
> Andrei Popescu 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
Andrei Popescu 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:
http://paste.debian.ne
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 any
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 s
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 'dmesg'. If you are
>>> worried about the si
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:
http:
Camaleón 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)
>>
>
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 writes:
>
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
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
>
On Lu, 18 oct 10, 14:06:08, Rodolfo Medina wrote:
> Camaleón writes:
>
> > On Sun, 17 Oct 2010 15:56:08 +0200, Rodolfo Medina wrote:
> >
> >> Camaleón writes:
> >
> >>> Please, type "lspci" and put here the output, just to be sure.
> >>
> >>
> >> I had already posted it:
> >>
> >> # lspci | gr
Greg Madden 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 one person,
Camaleón writes:
> On Sun, 17 Oct 2010 15:56:08 +0200, Rodolfo Medina wrote:
>
>> Camaleón writes:
>
>>> Please, type "lspci" and put here the output, just to be sure.
>>
>>
>> I had already posted it:
>>
>> # lspci | grep -i ethernet
>> eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-hos
Camaleón 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.
Ha
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
http://buf
On Sunday 17 October 2010 01:40:44 Rodolfo Medina wrote:
> Greg Madden 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
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
On Sun, 17 Oct 2010 15:56:08 +0200, Rodolfo Medina wrote:
> Camaleón writes:
>> Please, type "lspci" and put here the output, just to be sure.
>
>
> I had already posted it:
>
> # lspci | grep -i ethernet
> eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
Yep, but do not "grep" it,
Camaleón 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 the
Camaleón writes:
> On Sun, 17 Oct 2010 13:47:22 +0200, Rodolfo Medina wrote:
>
>> , so eth0 has always been a firewire device. But the device I'm using
>> as an ethernet port is eth1, which now is not detected by the command
>> ifconfig, nor dmesg, nor lspci.
>
> Please, type "lspci" and put her
On Sun, 17 Oct 2010 13:47:22 +0200, Rodolfo Medina wrote:
> , so eth0 has always been a firewire device. But the device I'm using
> as an ethernet port is eth1, which now is not detected by the command
> ifconfig, nor dmesg, nor lspci.
Please, type "lspci" and put here the output, just to be sur
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 o
Camaleón writes:
>>> But... what kind of device is that? Are you using an adapter (firewire
>>> to ethernet)? :-?
> It's like Rodolfo's ethernet device got messed in some way and the system
> now detects his ethernet connection as Firewire.
Well, the file /etc/udev/rules.d/z25_persistent-net.
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 0x1
On Sat, 16 Oct 2010 12:25:40 -0600, Morgan Gangwere wrote:
> On Sat, 16 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote:
>
>> But... what kind of device is that? Are you using an adapter (firewire
>> to ethernet)? :-?
>
> the 1394 standard says that a computer which supports 1394 must also
> sup
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:
>
> #
Greg Madden 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:
[...]
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
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 + (UTC) Camaleón <> 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 + (UTC) Camaleón <> wrote:
>
>> But... what kind of device is that? Are you using an adapter
>> (fire
Rodolfo Medina 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 flags: No such de
On Sat, 16 Oct 2010 16:15:12 + (UTC) Camaleón <> wrote:
> But... what kind of device is that? Are you using an adapter
> (firewire to ethernet)? :-?
the 1394 standard says that a computer which supports 1394 must also
support "1394 networking". Short end of it, if you need to move some
data b
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 error
On Sat, 16 Oct 2010 16:41:05 +0200, Rodolfo Medina wrote:
(...)
> Umarzuki Mochlis 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 themat
Rodolfo Medina 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 flags: No such dev
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
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
> 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
>
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 flags: No such device
SIOCSIFNETMASK: No such device
e
46 matches
Mail list logo
