Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Wlan und emerge ich dreh gleich durch.
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German)
View previous topic :: View next topic  
Author Message
falcon_munich
n00b
n00b


Joined: 10 Mar 2004
Posts: 17

PostPosted: Tue Jan 11, 2005 7:28 pm    Post subject: Wlan und emerge ich dreh gleich durch. Reply with quote

Hallo,

ich bin mit meinem latein am ende, ich habe eine WG511 die ich nicht zum laufen bekomme und ein lustiges emerge problem, hat da vieleicht irgend jemand eine idee ?
Gericom Laptop P3 Coppermine
2.4.26-gentoo-r9

hier erstmal die emerge fehler meldung:

>>> Auto-cleaning packages ...

sys-apps/diffutils
selected: 2.8.4-r4
protected: 2.8.7-r1
omitted: none

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging sys-apps/diffutils-2.8.4-r4...
No package files given... Grabbing a set.
Traceback (most recent call last):
File "/usr/bin/emerge", line 2997, in ?
unmerge("clean", ["world"])
File "/usr/bin/emerge", line 2167, in unmerge
retval=portage.unmerge(mysplit[0],mysplit[1],portage.root,mysettings,unmerge_action not in ["clean","prune"])
File "/usr/lib/portage/pym/portage.py", line 2700, in unmerge
mylink.unmerge(trimworld=mytrimworld,cleanup=1)
File "/usr/lib/portage/pym/portage.py", line 5936, in unmerge
a=doebuild(myebuildpath,"prerm",self.myroot,self.settings,cleanup=cleanup,use_cache=0,tree="vartree")
File "/usr/lib/portage/pym/portage.py", line 2465, in doebuild
return spawn(EBUILD_SH_BINARY+" "+mydo,mysettings,debug=debug,free=1,logfile=logfile)
File "/usr/lib/portage/pym/portage.py", line 1507, in spawn
return portage_exec.spawn_bash(mystring,env=env,**keywords)
File "/usr/lib/portage/pym/portage_exec.py", line 44, in spawn_bash
return spawn(args,env=env,opt_name=opt_name,**keywords)
File "/usr/lib/portage/pym/portage_exec.py", line 167, in spawn
raise str(e)+":\n "+myc+" "+string.join(myargs)
execve() arg 3 contains a non-string value:
/bin/bash [diffutils-2.8.4-r4] bash -c /usr/lib/portage/bin/ebuild.sh prerm
!!! FAILED prerm: 1

wenn ich die wlankarte in den pcmcia slot einführe, dann läd er mir den Treiber (von prism54.org) und inzwischen auch die Firmware. aber nach einem ifconfig eth1 up
sagt der ifconfig :
SIOCSIFFLAGS: Input/output error

und dmesg ist auch mitteilungs bedürftig:

Jan 11 20:13:06 [kernel] eth1: hot unplug detected
Jan 11 20:13:06 [kernel] cs: cb_free(bus 2)
Jan 11 20:13:21 [kernel] cs: cb_alloc(bus 2): vendor 0x1260, device 0x3890
Jan 11 20:13:21 [kernel] PCI: Found IRQ 10 for device 00:01.6
Jan 11 20:13:21 [kernel] ALSA ../alsa-kernel/pci/intel8x0m.c:400: codec_semaphore: semaphore is not ready [0x1][0x300]
- Last output repeated 49 times -
Jan 11 20:13:22 [kernel] ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1904: AC'97 1 does not respond - RESET
Jan 11 20:13:32 [kernel] eth1: resetting device...
Jan 11 20:13:32 [kernel] remove_proc_entry: 02:00.0/loading busy, count=1
Jan 11 20:13:32 [kernel] de_put: deferred delete of loading
Jan 11 20:13:32 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:32 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:33 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:33 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:34 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:34 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:35 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:35 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:36 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:36 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:37 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:37 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:38 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:38 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:39 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:39 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:40 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:40 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:41 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:41 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:42 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:42 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:43 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:43 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:44 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:44 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:45 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:45 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:46 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:46 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:47 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:47 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:48 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:48 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:49 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:49 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 10, triggering device
Jan 11 20:13:50 [kernel] eth1: no PIMFOR header found
Jan 11 20:13:50 [kernel] eth1: timeout waiting for mgmt response 100, triggering device
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 90, triggering device
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 80, triggering device
Jan 11 20:13:51 [kernel] eth1: no PIMFOR header found
- Last output repeated 2 times -
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 70, triggering device
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 60, triggering device
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 50, triggering device
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 40, triggering device
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 30, triggering device
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 20, triggering device
Jan 11 20:13:51 [kernel] eth1: timeout waiting for mgmt response 10, triggering device


so und hier noch die konfig von der kiste eth1 ist die wlan karte
eth0 Link encap:Ethernet HWaddr 00:90:F5:0A:E1:EB
inet addr:192.168.10.50 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34749 errors:0 dropped:0 overruns:0 frame:0
TX packets:22213 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:50700877 (48.3 Mb) TX bytes:2571274 (2.4 Mb)
Interrupt:10 Base address:0x3200

eth1 Link encap:Ethernet HWaddr 00:30:B4:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1335 (1.3 Kb) TX bytes:1335 (1.3 Kb)



Module Size Used by Not tainted
prism54 47916 0
firmware_class 4044 0 [prism54]
ohci1394 25584 0 (unused)
ieee1394 47908 0 [ohci1394]
snd-seq-oss 30368 0 (unused)
snd-seq-midi-event 3776 0 [snd-seq-oss]
snd-seq 39408 2 [snd-seq-oss snd-seq-midi-event]
snd-seq-device 4320 0 [snd-seq-oss snd-seq]
snd-pcm-oss 39400 0 (unused)
snd-pcm 64520 0 [snd-pcm-oss]
snd-timer 16100 0 [snd-seq snd-pcm]
snd-mixer-oss 14104 0 [snd-pcm-oss]
snd 36676 0 [snd-seq-oss snd-seq-midi-event snd-seq snd-seq-device snd-pcm-oss snd-pcm snd-timer snd-mixer-oss]
snd-page-alloc 5388 0 [snd-seq-oss snd-seq snd-seq-device snd-pcm snd-timer snd-mixer-oss snd]
trident 31024 0 (unused)



0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 630 Host (rev 31)
0000:00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
0000:00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge)
0000:00:01.1 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 82)
0000:00:01.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
0000:00:01.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
0000:00:01.4 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS PCI Audio Accelerator (rev 02)
0000:00:01.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0)
0000:00:02.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
0000:00:0a.0 CardBus bridge: Texas Instruments PCI4410 PC card Cardbus Controller (rev 02)
0000:00:0a.1 FireWire (IEEE 1394): Texas Instruments PCI4410 FireWire Controller (rev 02)
0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 630/730 PCI/AGP VGA Display Adapter (rev 31)
0000:02:00.0 Network controller: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duette] (rev 01)


es wäre echt supi wenn mir da irgendjemand tipps geben kann.
Achja, die karte ist ok unter knoppix läuft sie mit dem selben treiber.
MfG Falcon
_________________
Wer später bremst, fährt länger schnell.
Back to top
View user's profile Send private message
strubbldesign
Guru
Guru


Joined: 16 Jan 2005
Posts: 354
Location: still somewhere in the matrix but once i was able to look out of it

PostPosted: Tue Feb 08, 2005 5:30 pm    Post subject: Reply with quote

Habidere!

Ich würde gerne wissen an welchem Punkt der Installation du angekommen bist.

falls du noch am Stage1 dran bist
ferwende doch einfach
Code:
net-setup eth0


dann kommst du durch ein feines installations guide (auch für wireless)

falls du schon mit Stage 3 fertig bist und du schon rebooted hast, schau mal ob mit
Code:
ifconfig

alles stimmt. Ansonsten musste da die richtigen adressen eintippen.
Dann rebooten. dann ausprobieren
Code:
ping -c 3 www.mydvag.at

good luck
:wink:
ng Andi
_________________
Always look on the bright side of live. badu badubadubado
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum