Przerywane połączenie.....

Te, które nie mieszczą się w powyższych kategoriach, a mają coś wspólnego ze Slackware.

Moderatorzy: Moderatorzy, Administratorzy

nothing
Użytkownik
Posty: 11
Rejestracja: 2006-08-18, 11:47

Przerywane połączenie.....

Post autor: nothing »

czesc!

po wlaczeniu slackware 10.2 moge korzystac z przegladania internetu przez 60 sekund, potem nie moge zrobic nic - strony sie nie laduja

udalo mi sie cos na to poradzic:
spod zwyklego usera otwieram plik inet.conf lub resolv.conf i w jakimkolwiek miejscu daje spacje, nastepnie probuje zapisac zmiany (co jest oczywiscie niewykonalne spod usera, ale to 'odswieza' plik), wtedy dalej moge korzystac z ff lub konquerora ale tylko przez kolejne 60 sekund.
znaczy to, ze po 'odswiezeniu' ktoregos z w/w plików mam chwilowy dostep do sieci

co zrobic by ten dostep byl dostepny caly czas? gdzie znalesc plik odpowiedzialny za moj problem?
Awatar użytkownika
difrost
Moderator
Posty: 2802
Rejestracja: 2006-03-11, 12:31
Lokalizacja: Wrocław
Kontakt:

Re: Przerywane połączenie.....

Post autor: difrost »

Spinguj onet po IP w momencie gdy nie masz dzialajacego neta:

Kod: Zaznacz cały

ping 213.180.130.200
Sprawdz czy jest ruch!
Ostatnio zmieniony 2006-08-29, 13:00 przez difrost, łącznie zmieniany 1 raz.
[url=http://bdtk.sourceforge.net][img]http://pin.if.uz.zgora.pl/~beton/bdt-ready.png[/img][/url] #337142
--------------------------------------------
"I had a letter in the post today. It said 'Gas Bill'. It sounds a tempting offer." -- Alan Cox
"Users have been trained that when a computer bluescreens and losing all of their data, it's either (a) just the way things are, or (b) it's microsoft's fault." -- Theodore Tso
nothing
Użytkownik
Posty: 11
Rejestracja: 2006-08-18, 11:47

Re: Przerywane połączenie.....

Post autor: nothing »

nie pinguje
tak samo nie pinguje mojego gateway'a
pobieranie danych z sieci zostaje rozwniez przerwane po 60 sekundach

po prostu calkowicie zrywa polaczenie z netem
Awatar użytkownika
difrost
Moderator
Posty: 2802
Rejestracja: 2006-03-11, 12:31
Lokalizacja: Wrocław
Kontakt:

Re: Przerywane połączenie.....

Post autor: difrost »

Hmm...jak masz ,,dostarczana'' siec (LAN,wifi,etc) - chodzi mi o dokladne info na temat polaczenia?
[url=http://bdtk.sourceforge.net][img]http://pin.if.uz.zgora.pl/~beton/bdt-ready.png[/img][/url] #337142
--------------------------------------------
"I had a letter in the post today. It said 'Gas Bill'. It sounds a tempting offer." -- Alan Cox
"Users have been trained that when a computer bluescreens and losing all of their data, it's either (a) just the way things are, or (b) it's microsoft's fault." -- Theodore Tso
nothing
Użytkownik
Posty: 11
Rejestracja: 2006-08-18, 11:47

Re: Przerywane połączenie.....

Post autor: nothing »

net mam udostepniony poprzez tzw. radiowke
nie mam zew. ip

ip - 10.0.0.154
maska podsieci - 255.255.255.0
gateway - 10.0.0.1
dns1 - 194.204.159.1
dns2 - 194.204.152.34

jezeli mam podac pliki resolv.conf, inet1.conf ew. jakis inny to prosze dac znac, w tej chwili jestem na windowsie, w razie potrzeby przeloguje sie


EDIT:
moze wystarczy bym wstawil jakis skrypt, ktory ladowalby sie wraz ze startem slacka i odswiezal dns-y co 50 sekund?

tylko problem w tym ze nie potrafie czegos takiego napisac, jezeli ktos umie to prosze o pomoc w razie gdyby inne wyjscia zawidly,

zmienianie co minute okien i naciskanie ctrl+s jest dosyc uciazliwe
Ostatnio zmieniony 2006-08-30, 16:18 przez nothing, łącznie zmieniany 1 raz.
Awatar użytkownika
nOrNIc
Użytkownik
Posty: 478
Rejestracja: 2005-02-10, 00:41
Lokalizacja: Edinburgh

Re: Przerywane połączenie.....

Post autor: nOrNIc »

Ma się również rozumieć, że pod Windowsem działa wszystko normalnie, tak? Zadnego rozlaczana?
[url=http://pin.if.uz.zgora.pl/beton/][img]http://pin.if.uz.zgora.pl/~beton/bdt-ready.png[/img][/url] [url=http://www.slackware.com][img]http://pin.if.uz.zgora.pl/~nornic/images/slackware.png[/img][/url] [url=http://www.firefox.pl][img]http://firefox.pl/promo/firefox_apxl.png[/img][/url] [url=http://www.google.pl][img]http://pin.if.uz.zgora.pl/~nornic/images/google.png[/img][/url] #416576
nothing
Użytkownik
Posty: 11
Rejestracja: 2006-08-18, 11:47

Re: Przerywane połączenie.....

Post autor: nothing »

pod windowsem wszystko gra
w aurox'ie tez bylo ok
Awatar użytkownika
difrost
Moderator
Posty: 2802
Rejestracja: 2006-03-11, 12:31
Lokalizacja: Wrocław
Kontakt:

Re: Przerywane połączenie.....

Post autor: difrost »

Jaka masz karte? Czym ja odpaliles? Zagladales do logow systemowych, czy nie ma tam moze przydatnych komunikatow?
[url=http://bdtk.sourceforge.net][img]http://pin.if.uz.zgora.pl/~beton/bdt-ready.png[/img][/url] #337142
--------------------------------------------
"I had a letter in the post today. It said 'Gas Bill'. It sounds a tempting offer." -- Alan Cox
"Users have been trained that when a computer bluescreens and losing all of their data, it's either (a) just the way things are, or (b) it's microsoft's fault." -- Theodore Tso
nothing
Użytkownik
Posty: 11
Rejestracja: 2006-08-18, 11:47

Re: Przerywane połączenie.....

Post autor: nothing »

ufff....chcialem napisac wczesniej ale ciezko sie dostac na forum o pewnych porach

tak wiec karte sieciowa mam zintegrowana z plyta glowna ASUS A7V333-X, karta ta nosi nazwe BroadCom 10/100 Mbps

a co do logow...... jestem liniksowym noobem, wiem trylko ze logi znajduja sie w /var/log ale nie wiem w ktorym podfolderze/pliku znajduja sie przydatne informacje

polaczenie skonfigurowalem przy pomocy netconfig'a, oraz poprzez reczne dopisanie drugiego adresu dns w resolv.conf - nie wiem czy to dobra odpowiedz na pytanie: "Jak ją odpaliłeś?"
Awatar użytkownika
brx
Użytkownik
Posty: 723
Rejestracja: 2004-06-24, 14:37
Lokalizacja: Poznań/Lublin

Re: Przerywane połączenie.....

Post autor: brx »

Pokaż wyniki ifconfig, route.

Co do logów:
tail -n 50 /var/log/messeges
dmesg

Sprawdz czy nie ma tam nic niepokojącego odnośnie interfejsów sieciowych.
Slackware Current - Kernel 2.6.18 - Xfce - - Aterm - Kadu
_______________________________________
Registered Linux User 363857 :D
nothing
Użytkownik
Posty: 11
Rejestracja: 2006-08-18, 11:47

Re: Przerywane połączenie.....

Post autor: nothing »

ifconfig

Kod: Zaznacz cały

eth0      Link encap:Ethernet  HWaddr 00:E0:18:B5:B7:5B
          inet addr:10.0.0.154  Bcast:10.0.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:118 errors:0 dropped:0 overruns:0 frame:0
          TX packets:119 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:72556 (70.8 Kb)  TX bytes:17931 (17.5 Kb)
          Interrupt:9

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
route

Kod: Zaznacz cały

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
localnet        *               255.255.255.0   U     0      0        0 eth0
loopback        *               255.0.0.0       U     0      0        0 lo
tail -n 50 /var/log/messeges

Kod: Zaznacz cały

Sep  2 16:11:14 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:14 localhost logger: /etc/rc.d/rc.inet1:  /sbin/ifconfig eth0 10.0.0.154 broadcast 10.0.0.255 netmask 255.255.255.0
Sep  2 16:11:14 localhost logger: /etc/rc.d/rc.inet1:  /sbin/route add default gw 10.0.0.1 metric 1
Sep  2 16:11:14 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:14 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:14 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:14 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:15 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:15 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:15 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:15 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:15 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:15 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:15 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:15 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:15 localhost kernel: b44: eth0: Link is down.
Sep  2 16:11:15 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:15 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:15 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:15 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:16 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:16 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:16 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:16 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:16 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:16 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:16 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:16 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:16 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:16 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:16 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:16 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:17 localhost kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
Sep  2 16:11:17 localhost kernel: b44: eth0: Flow control is off for TX and off for RX.
Sep  2 16:11:18 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:18 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:19 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:19 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:19 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:19 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:19 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:19 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:19 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:19 localhost kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  2 16:11:19 localhost kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  2 16:11:19 localhost kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.5
Sep  2 16:11:33 localhost logger: /etc/rc.d/rc.hotplug start (exiting script)
Sep  2 16:11:33 localhost sshd[2219]: Server listening on 0.0.0.0 port 22.
Sep  2 16:11:39 localhost apmd[2235]: Version 3.0.2 (APM BIOS 1.2, Linux driver 1.16)
Sep  2 16:11:39 localhost apmd[2235]: Charge: * * * (-1% unknown)
dmesg

Kod: Zaznacz cały

Linux version 2.4.31 (root@tree) (gcc version 3.3.5) #6 Sun Jun 5 19:04:47 PDT 2005
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000002fffc000 (usable)
 BIOS-e820: 000000002fffc000 - 000000002ffff000 (ACPI data)
 BIOS-e820: 000000002ffff000 - 0000000030000000 (ACPI NVS)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
767MB LOWMEM available.
On node 0 totalpages: 196604
zone(0): 4096 pages.
zone(1): 192508 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=slackware ro root=303
Initializing CPU#0
Detected 1666.767 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 3329.22 BogoMIPS
Memory: 774700k/786416k available (1832k kernel code, 11328k reserved, 607k data, 120k init, 0k highmem)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU:     After generic, caps: 0383fbff c1c3fbff 00000000 00000000
CPU:             Common caps: 0383fbff c1c3fbff 00000000 00000000
CPU: AMD Athlon(TM) XP 2000+ stepping 02
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xf1640, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Via IRQ fixup
PCI: Using IRQ router VIA [1106/3177] at 00:11.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
Journalled Block Device driver loaded
vesafb: framebuffer at 0xf0000000, mapped to 0xf080d000, size 1536k
vesafb: mode is 1024x768x8, linelength=1024, pages=4
vesafb: protected mode interface info at c000:c200
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
pty: 512 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10f
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1
    ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:DMA
hda: SAMSUNG SP2514N, ATA DISK drive
blk: queue c03af460, I/O limit 4095Mb (mask 0xffffffff)
hdc: LG CD-RW CED-8080B, ATAPI CD/DVD-ROM drive
hdd: BENQ DVD DD DW1650, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
hdc: attached ide-cdrom driver.
hdc: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
Uniform CD-ROM driver Revision: 3.12
hdd: attached ide-cdrom driver.
hdd: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Partition check:
 hda: hda1 hda2 < hda5 hda6 hda7 hda8 > hda3 hda4
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
   8regs     :  2389.600 MB/sec
   32regs    :  1600.800 MB/sec
   pIII_sse  :  2557.200 MB/sec
   pII_mmx   :  3901.600 MB/sec
   p5_mmx    :  4984.800 MB/sec
raid5: using function: pIII_sse (2557.200 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.8(17/11/2003)
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 120k freed
Adding Swap: 755044k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,3), internal journal
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 690M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: AGP aperture is 64M @ 0xf8000000
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,8), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NTFS driver v1.1.22 [Flags: R/O MODULE]
NTFS: unkown option 'rwx'
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus] [pm]
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
ds: no socket drivers loaded!
PCI: Enabling device 00:11.5 (0000 -> 0001)
PCI: Assigned IRQ 9 for device 00:11.5
PCI: Setting latency timer of device 00:11.5 to 64
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Enabling device 00:10.3 (0014 -> 0016)
PCI: Assigned IRQ 10 for device 00:10.3
IRQ routing conflict for 00:10.0, have irq 5, want irq 10
IRQ routing conflict for 00:10.1, have irq 5, want irq 10
PCI: Sharing IRQ 10 with 00:10.2
ehci_hcd 00:10.3: VIA Technologies, Inc. USB 2.0
ehci_hcd 00:10.3: irq 10, pci mem f0b02000
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 6 ports detected
uhci.c: USB Universal Host Controller Interface driver v1.1
PCI: Assigned IRQ 5 for device 00:10.0
PCI: Sharing IRQ 5 with 00:10.1
IRQ routing conflict for 00:10.2, have irq 10, want irq 5
IRQ routing conflict for 00:10.3, have irq 10, want irq 5
uhci.c: USB UHCI at I/O 0xd800, IRQ 5
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Assigned IRQ 5 for device 00:10.1
PCI: Sharing IRQ 5 with 00:10.0
IRQ routing conflict for 00:10.2, have irq 10, want irq 5
IRQ routing conflict for 00:10.3, have irq 10, want irq 5
uhci.c: USB UHCI at I/O 0xd400, IRQ 5
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Enabling device 00:10.2 (0014 -> 0015)
PCI: Assigned IRQ 10 for device 00:10.2
IRQ routing conflict for 00:10.0, have irq 5, want irq 10
IRQ routing conflict for 00:10.1, have irq 5, want irq 10
PCI: Sharing IRQ 10 with 00:10.3
uhci.c: USB UHCI at I/O 0xd000, IRQ 10
usb.c: new USB bus registered, assigned bus number 4
hub.c: USB hub found
hub.c: 2 ports detected
b44.c:v0.93 (Mar, 2004)
PCI: Enabling device 00:09.0 (0004 -> 0006)
PCI: Assigned IRQ 9 for device 00:09.0
eth0: Broadcom 4400 10/100BaseT Ethernet 00:e0:18:b5:b7:5b
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
b44: eth0: Link is down.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is off for TX and off for RX.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: shpc_init : shpc_cap_offset == 0
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp: PCI Express Hot Plug Controller Driver version: 0.5
mam nadzieje ze tu uda sie odnalesc problem
oczywiscie sam probowalem odnalesc cos w tych logach lecz nic nie widze - noob to noob


EDIT:
dlaczego po wydaniu polecenia route zamiast bramy 10.0.0.1 jest '?

w inet1.conf w linijce gateway jest ten numer
Ostatnio zmieniony 2006-09-02, 15:26 przez nothing, łącznie zmieniany 2 razy.
Bysz
Użytkownik
Posty: 84
Rejestracja: 2006-08-21, 18:26
Lokalizacja: Zduńska Wola

Re: Przerywane połączenie.....

Post autor: Bysz »

Kod: Zaznacz cały

lspci -v 

Wklej fragment zawierajacy info o karcie, nie wrzucaj wszystkiego.
nothing
Użytkownik
Posty: 11
Rejestracja: 2006-08-18, 11:47

Re: Przerywane połączenie.....

Post autor: nothing »

lspci -v

Kod: Zaznacz cały

(...)

00:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
        Subsystem: ASUSTeK Computer Inc. A7V8X motherboard
        Flags: bus master, fast devsel, latency 32, IRQ 9
        Memory at ed800000 (32-bit, non-prefetchable) [size=8K]
        Expansion ROM at efef0000 [disabled] [size=16K]
        Capabilities: [40] Power Management version 2

(...)
Bysz
Użytkownik
Posty: 84
Rejestracja: 2006-08-21, 18:26
Lokalizacja: Zduńska Wola

Re: Przerywane połączenie.....

Post autor: Bysz »

Zobacz to >tutaj<
i to w sekcji LAN na tej >stronie<
nothing
Użytkownik
Posty: 11
Rejestracja: 2006-08-18, 11:47

Re: Przerywane połączenie.....

Post autor: nothing »

w tym drugim linku autor proponowal zainstalowac dane sterowniki w przypadku problemow z kernelem 2.6.15. moj kernel to 2.4.31
jednak chyba nie ma rozroznienia sterownikow dla poszczegolnych kerneli - nie widze tego przynajmniej na stronie broadcom.com

w kazdym badz razie sciagnolem paczke, rozpakowalem, przeczytalem readme, zgodnie z nim uzylem polecenia make i chyba tu jest problem, prosze spojrzec na to co mi wyskoczylo:

Kod: Zaznacz cały

gcc -DMODULE -D__KERNEL__ -Wall -Wstrict-prototypes -I/lib/modules/2.4.31/build/include  -DOLD_DMA -DO                            LD_MALLOC -DNO_DMA_MAPPING_ERROR -O2   -c -o b44.o b44.c
In file included from /lib/modules/2.4.31/build/include/linux/spinlock.h:6,
                 from /lib/modules/2.4.31/build/include/linux/module.h:12,
                 from b44.c:19:
/lib/modules/2.4.31/build/include/asm/system.h: In function `__set_64bit_var':
/lib/modules/2.4.31/build/include/asm/system.h:190: warning: dereferencing type-punned pointer will br                            eak strict-aliasing rules
/lib/modules/2.4.31/build/include/asm/system.h:190: warning: dereferencing type-punned pointer will br                            eak strict-aliasing rules
mimo ze nie wiedzialem czy jest dobrze uzylem polecenia make install i pojawilo sie niewiele informacji:

Kod: Zaznacz cały

gzip -c b44.4 > b44.4.gz
mkdir -p /lib/modules/2.4.31/kernel/drivers/net;
install -m 444 b44.o /lib/modules/`uname -r`/kernel/drivers/net;
install -m 444 b44.4.gz /usr/share/man/man4;\
nadal co 60s przerwa w polaczeniu
nastepnie reboot - niestety dalej co 60 s przerwa
kolejno netconfig - skutek jak wyzej

i to tyle, nie wiem co zrobic, jezeli nikt nie doszuka sie przyczyny problemu w w/w informacjach to przeinstaluje slacka ale z kernelem 2.6.15
Ostatnio zmieniony 2006-09-04, 11:49 przez nothing, łącznie zmieniany 2 razy.
ODPOWIEDZ