You are not logged in.
When I start my system running Archlinux I never have problems. These only occur when I reboot my system. Something goes wrong and it system never goes beyond [network]
When I look at the log, there seems to be something wrong with my network card. You can see the messages below. Any suggestions that might help solve this problem? Now I have to wait 5-10 minutes before I can use my system again :-( I never had this problem running other distros.
My log when things go wrong (sorry for big post):
Feb 18 13:58:17 gommans1 Real Time Clock Driver v1.12
Feb 18 13:58:17 gommans1 sis900.c: v1.08.07 11/02/2003
Feb 18 13:58:17 gommans1 ACPI: PCI interrupt 0000:00:04.0[A] -> GSI 19 (level, low) -> IRQ 19
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 0.
Feb 18 13:58:17 gommans1 eth0: Realtek RTL8201 PHY transceiver found at address 1.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 2.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 4.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 6.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 7.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 8.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 10.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 11.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 12.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 13.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 15.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 16.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 17.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 21.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 22.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 23.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 25.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 26.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 27.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 28.
Feb 18 13:58:17 gommans1 eth0: Unknown PHY transceiver found at address 31.
Feb 18 13:58:17 gommans1 e09954f7http://www.mozilla.org/start/1.7/
Feb 18 13:58:17 gommans1 PREEMPT SMP
Feb 18 13:58:17 gommans1 Modules linked in: sis900 rtc nls_cp437 vfat fat ntfs
Feb 18 13:58:17 gommans1 CPU: 0
Feb 18 13:58:17 gommans1 EIP: 0060:[<e09954f7>] Not tainted VLI
Feb 18 13:58:17 gommans1 EFLAGS: 00010296 (2.6.10-ARCH)
Feb 18 13:58:17 gommans1 EIP is at sis900_check_mode+0x17/0xa0 [sis900]
Feb 18 13:58:17 gommans1 eax: 00000000 ebx: df58d400 ecx: 10501010 edx: 0000ec18
Feb 18 13:58:17 gommans1 esi: 00000000 edi: 0000ec00 ebp: df58d620 esp: dfac1e88
Feb 18 13:58:17 gommans1 ds: 007b es: 007b ss: 0068
Feb 18 13:58:17 gommans1 Process dhcpcd (pid: 1321, threadinfo=dfac0000 task=dfaff520)
Feb 18 13:58:17 gommans1 Stack: 00000000 00000000 00000000 0000000a df58d400 0000ec00 e0994d27 df58d400
Feb 18 13:58:17 gommans1 00000000 00000001 df58d400 df58d400 91f6c870 df58d400 00000000 00001002
Feb 18 13:58:17 gommans1 00000000 c042fb05 df58d400 c0433d04 df58d400 00001063 df58d400 c043135f
Feb 18 13:58:17 gommans1 Call Trace:
Feb 18 13:58:17 gommans1 [<e0994d27>] sis900_open+0x107/0x170 [sis900]
Feb 18 13:58:17 gommans1 [<c042fb05>] dev_open+0x85/0xa0
Feb 18 13:58:17 gommans1 [<c0433d04>] dev_mc_upload+0x24/0x40
Feb 18 13:58:17 gommans1 [<c043135f>] dev_change_flags+0x5f/0x150
Feb 18 13:58:17 gommans1 [<c042f9ed>] dev_load+0x2d/0x70
Feb 18 13:58:17 gommans1 [<c047487b>] devinet_ioctl+0x56b/0x620
Feb 18 13:58:17 gommans1 [<c0476c4a>] inet_ioctl+0xca/0xe0
Feb 18 13:58:17 gommans1 [<c0426405>] sock_ioctl+0x1a5/0x260
Feb 18 13:58:17 gommans1 [<c01736ae>] sys_ioctl+0x1ee/0x250
Feb 18 13:58:17 gommans1 [<c01031d9>] sysenter_past_esp+0x52/0x75
Feb 18 13:58:17 gommans1 Code: ff ff 89 34 24 e8 8a 41 aa df e9 4b ff ff ff 90 8d 74 26 00 83 ec 18 89 74 24 10 8b 74 24 20 89 5c 24 0c 8b 5c 24 1c 89 7c 24 14 <80> 7e 0e 02 8b 7b 68 8b 4b 18 74 3d 8d 51 04 ed 83 c8 10 ef 89
Feb 18 13:58:17 gommans1 <6>eth0: Using transceiver found at address 1 as default
Feb 18 13:58:17 gommans1 eth0: SiS 900 PCI Fast Ethernet at 0xec00, IRQ 19, 00:10:dc:7f:b7:0b.
Feb 18 13:58:17 gommans1 ACPI: PCI interrupt 0000:00:02.7[C] -> GSI 18 (level, low) -> IRQ 18
Feb 18 13:58:17 gommans1 intel8x0_measure_ac97_clock: measured 49645 usecs
Feb 18 13:58:17 gommans1 intel8x0: clocking to 48000
Feb 18 13:58:17 gommans1 usbcore: registered new driver usbfs
Feb 18 13:58:17 gommans1 usbcore: registered new driver hub
Feb 18 13:58:17 gommans1 usbcore: registered new driver usblp
Feb 18 13:58:17 gommans1 drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Feb 18 13:58:18 gommans1 ts: Compaq touchscreen protocol output
Feb 18 13:58:19 gommans1 i2c-sis96x version 1.0.0
Feb 18 13:58:19 gommans1 sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x10c0
Feb 18 13:58:20 gommans1 ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
Feb 18 13:58:20 gommans1 ACPI: PCI interrupt 0000:00:02.3[B] -> GSI 17 (level, low) -> IRQ 17
Feb 18 13:58:20 gommans1 ohci1394: fw-host0: Unexpected PCI resource length of 1000!
Feb 18 13:58:20 gommans1 ieee1394.agent[2355]: ... no drivers for IEEE1394 product 0x/0x/0x
Feb 18 13:58:20 gommans1 ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[17] MMIO=[ea428000-ea4287ff] Max Packet=[2048]
Offline
Yes, actually your network card may cause that problem.
I suggest you disable it and see what you get when you reboot.
If it does not work, then I think it's a problem with your kernel configuration or your BIOS needing an upgrade.
nano -w /etc/rc.confPut a '!' in front of the 'network' daemon and reboot.
If this does not solve the problem, dont forget to post the list of your material and eventually your kernel configuration(well only what may be interesting in it, not the whole stuff)
P.S. : If you tried all I said, then type
dhcpcd -k eth0and see what you get when you reboot.
Offline
Thanks for your reaction!
Indeed, the netword card is causing the problem. When I disabled it, my system rebooted just fine.
Funny thing is, that I can reboot into XP without issues and I never had these problems before with other distros. Perhaps you have a suggestion how to change the sequence of my modules and deamons that optimizes my system and might get my network card to stop giving me a headache.
MODULES=(snd-intel8x0 snd-pcm-oss usblp sis900 usbserial)
DAEMONS=(syslog-ng network hotplug !pcmcia netfs crond cups)
Any help is most welcome!
Offline
Put the network daemon just after pcmcia because it may be needed by netfs but it may need hotplug modules or pcmcia modules.
What's the vendor and name of the network card you use ? Perhaps you could google around to see if a more recent driver/module has been made for that product...
Offline
Put the network daemon just after pcmcia because it may be needed by netfs but it may need hotplug modules or pcmcia modules.
Thanks, I will try that!
What's the vendor and name of the network card you use ? Perhaps you could google around to see if a more recent driver/module has been made for that product...
It is an onboard network card, SIS900.
I have a MSI 6701 board, I believe made specific for Medion. Perhaps they did not deliver the perfect board. I had problems with the USB 2.0 ports on the mainboard, that did not work the way they should (bought a new card for that). But then again, I have only had problems with the network card running Archlinux. I will try the change in settings first. Perhaps that gives the network card just enough rest to perform correct.
I will keep you informed.
Thanks jerem!
Offline
Update: I recently updates to kernel 2.6.11-1 and the problem is gone!
Offline
rmbalfa,
I do not know if these problems are related.
I would suggest you give 2.6.11-1 a try.
:twisted:
Offline
Offline