This is my 3rd mail here about this problem without answer. Meanwhile I'm trying to solve the problem myself but at this time I still can't. I think the problem is in the boot.ini network script. In fact if I run "/etc/init.d/ network restart", I get: ==== Shutting down network interfaces: eth-pcmcia-0 done eth0 done Setting up network interfaces: lo done eth0 (DHCP) failed eth-pcmcia-0 (DHCP) failed ==== But if I do "ifconfi eth0 up" and than "dhcpcd", my internet connection works! I've paid about 80 euro for SuSE, their support doesn't cover this type of problem because in their opinion it is NOT a SuSE problem! I don't think so. With Debian all works fine. They told me to ask here. I hope I didn't trash my money purchasing this distro. Stefano
On Saturday 21 of February 2004 13:06, Stefano Ceci wrote:
This is my 3rd mail here about this problem without answer. Meanwhile I'm trying to solve the problem myself but at this time I still can't. I think the problem is in the boot.ini network script. In fact if I run "/etc/init.d/ network restart", I get: ==== Shutting down network interfaces: eth-pcmcia-0 done eth0 done Setting up network interfaces: lo done eth0 (DHCP) failed eth-pcmcia-0 (DHCP) failed ==== But if I do "ifconfi eth0 up" and than "dhcpcd", my internet connection works! I've paid about 80 euro for SuSE, their support doesn't cover this type of problem because in their opinion it is NOT a SuSE problem! I don't think so. With Debian all works fine. They told me to ask here. I hope I didn't trash my money purchasing this distro.
Stefano, Be more systematic, it is hard to help with almost no valuable information provided. What do you get in your logs? I think this might be something with routing (be more precisely with modify_resolve - dhcp gets resolve settings for eth0, backup current settings and set the new one, BUT later dhcp tries to force resolve to do modification one again for eth-pcmcia-0). Try to remove eth0 or pcmcia (or change from dhcp to static)? Does it work with only one dhcp? If yes, try to modify your dhcp client settings. Regards, -- Marek Chlopek
Alle 13:19, sabato 21 febbraio 2004, Marek Chlopek ha scritto:
Stefano, Be more systematic, it is hard to help with almost no valuable information provided. What do you get in your logs?
I think this might be something with routing (be more precisely with modify_resolve - dhcp gets resolve settings for eth0, backup current settings and set the new one, BUT later dhcp tries to force resolve to do modification one again for eth-pcmcia-0).
Try to remove eth0 or pcmcia (or change from dhcp to static)? Does it work with only one dhcp?
If yes, try to modify your dhcp client settings.
Thanks for answer. I've removed eth0 interface. Then with YAST2 I've configured eth-pcmcia-0 (recognized automatically by SuSE) as static with ip assigned by router. Then I've done "/etc/init.d/network restart" and finally I've read the message "done" on the screen for "setting up network interfaces" at eth-pcmcia-0 entry. Ok, but internet doesn't work. So I've manually launched "dhcpcd" and only after that, internet works!. Ok, I've rebooted the system and network does NOT work. During boot process, after F2, I've read "configuration lo...done" and "configuration eth-pcmcia-0....hotplug". If I do "ifconfig", only lo interface is present. I've tryed to extract pcmcia and reinsert and at dmesg i see: ==== cs: cb_free(bus 2) cs: cb_alloc(bus 2): vendor 0x10ec, device 0x8139 PCI: Enabling device 02:00.0 (0000 -> 0003) ==== but network still not works and only lo interface is present. Then I've done: ==== luna:/home/ste # /etc/init.d/network restart Shutting down network interfaces: eth-pcmcia-0 skipped Setting up network interfaces: lo done eth-pcmcia-0 hotplug ==== So... ==== luna:/home/ste # ifconfig eth-pcmcia-0 up eth-pcmcia-0: unknown interface: No such device ==== I'm going crazy!! With Debian I've compiled the pcmcia support static in the kernel and all works. I've switched to SuSE because I was looking for a distro more stable and modern. So I'd like take all SuSE structure with kernel preconfigured. Is it possible? How can I manage network card without hotplug? With YaST I've then configured a new interface NOT pcmcia with realtek module. Interface name is eth0 than: ==== luna:/home/ste # /etc/init.d/network restart Shutting down network interfaces: eth-pcmcia-0 done eth0 done Setting up network interfaces: lo done eth0 (DHCP) failed eth-pcmcia-0 (DHCP) failed ==== But after I've done luna:/home/ste # ifconfig luna:/home/ste # dhcpcd ==== Now the situation is: ==== luna:/home/ste # ifconfig eth0 Link encap:Ethernet HWaddr 00:40:F4:6A:2C:2D inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::240:f4ff:fe6a:2c2d/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:4 carrier:0 collisions:0 txqueuelen:100 RX bytes:1368 (1.3 Kb) TX bytes:3176 (3.1 Kb) Interrupt:9 Base address:0xb000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:50 errors:0 dropped:0 overruns:0 frame:0 TX packets:50 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3260 (3.1 Kb) TX bytes:3260 (3.1 Kb) ===== And now Internet works. Help!!! Regards Stefano
On Saturday 21 of February 2004 14:48, Stefano Ceci wrote:
Alle 13:19, sabato 21 febbraio 2004, Marek Chlopek ha scritto:
Stefano, Be more systematic, it is hard to help with almost no valuable information provided. What do you get in your logs?
I think this might be something with routing (be more precisely with modify_resolve - dhcp gets resolve settings for eth0, backup current settings and set the new one, BUT later dhcp tries to force resolve to do modification one again for eth-pcmcia-0).
Try to remove eth0 or pcmcia (or change from dhcp to static)? Does it work with only one dhcp?
If yes, try to modify your dhcp client settings.
Thanks for answer. I've removed eth0 interface. Then with YAST2 I've configured eth-pcmcia-0 (recognized automatically by SuSE) as static with ip assigned by router. Then I've done "/etc/init.d/network restart" and
Sorry, this is probably my "polish accent" in english. I was trying to say you should remove eth0 and leave pcmcia as dhcp OR keep eth0 but static and pcmcia as dhcp. In other words there should be one dhcp request only. Try just one interface only!!! and see it works. -- Marek Chlopek
Alle 14:52, sabato 21 febbraio 2004, Marek Chlopek ha scritto:
Sorry, this is probably my "polish accent" in english. I was trying to say you should remove eth0 and leave pcmcia as dhcp OR keep eth0 but static and pcmcia as dhcp. In other words there should be one dhcp request only.
Try just one interface only!!! and see it works.
Marek, misunderstanding perhaps depends by my "italian accent" too...:-)) With only one interface dhcp I've already tryed. In the last mail with my poor english I've written that I've tried with only one pcmcia interface static too, but without lucky. The only way to get it working is with a NO PCMCIA interface, static or dhcp. In other words, the interface have to be independent from hotplug. The problem is that I must configure it manually. Thanks again Stefano
On Saturday 21 of February 2004 15:13, Stefano Ceci wrote:
With only one interface dhcp I've already tryed. In the last mail with my poor english I've written that I've tried with only one pcmcia interface static too, but without lucky. The only way to get it working is with a NO PCMCIA interface, static or dhcp. In other words, the interface have to be independent from hotplug. The problem is that I must configure it manually.
ok. I understand eth0 via dhcp with no pcmcia works fine. I also understand you have tried start pcmcia as static and this was not working. Please try also pcmcia via dhcp (not hotplug) but eth0 should not exists in this configuration. Works fine? -- Marek Chlopek
Alle 15:33, sabato 21 febbraio 2004, Marek Chlopek ha scritto:
ok. I understand eth0 via dhcp with no pcmcia works fine. I also understand you have tried start pcmcia as static and this was not working.
Please try also pcmcia via dhcp (not hotplug) but eth0 should not exists in this configuration. Works fine?
How can I configure pcmcia without hotplug? If I configure eth with pcmcia, SuSE automatically manage it with hotplug. But hotplag seems not recognize that at boot. How about putting ifconfig eth0 up command in rc.local? Stefano
Ooops, sorry, I mean boot.local and not rc.local. Stefano
On 02/21/2004 10:13 PM, Stefano Ceci wrote:
The only way to get it working is with a NO PCMCIA interface, static or dhcp. In other words, the interface have to be independent from hotplug. The problem is that I must configure it manually.
I think your problem is the boot order. Using a PCMCIA network card, which requires hotplug, which probably starts after your network start script. Check /etc/init.d/hotplug and /etc/init.d/network. Make sure (by the header) that hotplug starts before network, then as root insserv hotplug to straighten out the startup script order. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Alle 16:21, sabato 21 febbraio 2004, Joe Morris (NTM) ha scritto:
I think your problem is the boot order. Using a PCMCIA network card, which requires hotplug, which probably starts after your network start script. Check /etc/init.d/hotplug and /etc/init.d/network. Make sure (by the header) that hotplug starts before network, then as root insserv hotplug to straighten out the startup script order. HTH.
Hi Joe, 1st thanks for answer. As you, I think the problem is in the boot order too. Bot how change it? I cannot understand how I can check the correct order between those two services. In the headers of the two files the situation is: HOTPLUG # Default-Start: 1 2 3 5 # Default-Stop: 0 4 6 NETWORK # Default-Start: 2 3 5 # Default-Stop: How change it (if worng)? Stefano
Alle 16:21, sabato 21 febbraio 2004, Joe Morris (NTM) ha scritto:
I think your problem is the boot order. Using a PCMCIA network card, which requires hotplug, which probably starts after your network start script. Check /etc/init.d/hotplug and /etc/init.d/network. Make sure (by the header) that hotplug starts before network, then as root insserv hotplug to straighten out the startup script order. HTH.
I played with YaST runlevel editor and I found that the problem isn't between hotplug and network services, but between PCMCIA and network services. PCMCIA should start before network an I forced it setting "B" for PCMCIA but in this way during boot the system stops and resume the booting process only with a CTRL-C command. After boot, all works fine. The question is: how can I set PCMCIA before Network in the runlevel without take errors? Thanks Stefano
I'm still investigating on my network problem. In my last mail I wrote that the problem seems to be in boot sequence between "network" and "pcmcia". Well, now I've discovered that after boot, if I do: ==== luna:/home/ste # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb) ==== then, if I do: ==== luna:/home/ste # modprobe 8139too ==== after few seconds, doing: ==== luna:/home/ste # ifconfig eth0 Link encap:Ethernet HWaddr 00:40:F4:6A:2C:2D inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::240:f4ff:fe6a:2c2d/64 Scope:Link UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:10 errors:0 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:100 RX bytes:623 (623.0 b) TX bytes:1226 (1.1 Kb) Interrupt:9 Base address:0x9000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2608 (2.5 Kb) TX bytes:2608 (2.5 Kb) ==== And all works fine! Please, I feel really near to solution. The last step is to configure the system to automatically load the 8139too driver. I've tryed to put it in the kernel modules to load at boot. It doesn't work because the pcmcia card is "hotplugged" after that the kern-modules are loaded. Why hotplug doesn't load automatically the correct module? Where is my error? Stefano
Marek, misunderstanding perhaps depends by my "italian accent" too...:-)) With only one interface dhcp I've already tryed. In the last mail with my poor english I've written that I've tried with only one pcmcia interface static too, but without lucky. The only way to get it working is with a NO PCMCIA interface, static or dhcp. In other words, the interface have to be independent from hotplug. The problem is that I must configure it manually. Thanks again Stefano
Check that /etc/init.d/network is starting -after- /etc/init.d/hotplug. <snip> # /etc/init.d/network # ### BEGIN INIT INFO # Provides: network # Required-Start: $local_fs # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: # Description: Configure the network interfaces and set up routing ### END INIT INFO </snip> Add hotplug at the end of the # Required-Start: $local_fs line. This all sounds like the network is trying to start before the card is recognized and modules loaded for it. Ken
Alle 21:57, sabato 21 febbraio 2004, Ken Schneider ha scritto:
Check that /etc/init.d/network is starting -after- /etc/init.d/hotplug.
<snip>
# /etc/init.d/network # ### BEGIN INIT INFO # Provides: network # Required-Start: $local_fs # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: # Description: Configure the network interfaces and set up routing ### END INIT INFO
</snip>
Add hotplug at the end of the # Required-Start: $local_fs line.
This all sounds like the network is trying to start before the card is recognized and modules loaded for it.
Ken, please, can you tell me exactly how can I check that /etc/init.d/network is starting -after- /etc/init.d/hotplug? I'm newbie here and so please give instruction for dummy. Tanks Stefano
<snip>
# /etc/init.d/network # ### BEGIN INIT INFO # Provides: network # Required-Start: $local_fs # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: # Description: Configure the network interfaces and set up routing ### END INIT INFO
</snip>
Add hotplug at the end of the # Required-Start: $local_fs line.
This all sounds like the network is trying to start before the card
is
recognized and modules loaded for it.
Ken, please, can you tell me exactly how can I check that /etc/init.d/network is starting -after- /etc/init.d/hotplug? I'm newbie here and so please give instruction for dummy. Tanks Stefano
You will also need to run SuSEconfig and I am not sure of insserv -d. Reboot in verbose mode and watch the messages as they cross the screen. If they go by to fast have a look at /var/log/boot.msg and/or run the dmesg|less to see boot messages (right after a boot). Ken
Alle 22:15, sabato 21 febbraio 2004, Ken Schneider ha scritto:
You will also need to run SuSEconfig and I am not sure of insserv -d. Reboot in verbose mode and watch the messages as they cross the screen. If they go by to fast have a look at /var/log/boot.msg and/or run the dmesg|less to see boot messages (right after a boot).
Ken, I've run SuSEconfig and insserv but doesn't help.
Here is my dmesg:
ste@luna:~> dmesg
Linux version 2.4.21-192-default (root@i386.suse.de) (gcc version 3.3.1 (SuSE
Li
nux)) #1 Wed Feb 18 19:26:28 UTC 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ec000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000b7f0000 (usable)
BIOS-e820: 000000000b7f0000 - 000000000b7ffc00 (ACPI data)
BIOS-e820: 000000000b7ffc00 - 000000000b800000 (ACPI NVS)
BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
829MB vmalloc/ioremap area available.
0MB HIGHMEM available.
183MB LOWMEM available.
ACPI: have wakeup address 0xc0001000
On node 0 totalpages: 47088
zone(0): 4096 pages.
zone(1): 42992 pages.
zone(2): 0 pages.
Compaq 12XL125 machine detected. Enabling interrupts during APM calls.
ACPI: RSDP (v000 PTLTD ) @ 0x000f7850
ACPI: RSDT (v001 PTLTD RSDT 01540.00000) @ 0x0b7fd0f7
ACPI: FADT (v001 COMPAQ ERA 01540.00000) @ 0x0b7ffb8c
ACPI: DSDT (v001 Compaq ERA 01540.00000) @ 0x00000000
ACPI: Skipping APIC setup
Building zonelist for node : 0
Kernel command line: root=/dev/hda2 vga=0x314 desktop acpi=force splash=silent
bootsplash: silent mode.
Initializing CPU#0
Detected 473.288 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 925.69 BogoMIPS
Memory: 182536k/188352k available (1580k kernel code, 5428k reserved, 605k
data,
160k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line)
CPU: After generic, caps: 008021bf 808029bf 00000000 00000002
CPU: Common caps: 008021bf 808029bf 00000000 00000002
CPU: AMD-K6(tm) 3D processor stepping 0c
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: AMD K6
ACPI: Subsystem revision 20030619
PCI: PCI BIOS revision 2.10 entry at 0xfd83e, last bus=1
PCI: Using configuration type 1
Looking for DSDT in initrd ... not found!
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: System [ACPI] (supports S0 S1 S4 S5)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 7 *9 10 11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 9)
ACPI: PCI Interrupt Link [LNKC] (IRQs 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKD] (IRQs 7 9 10 *11 12)
ACPI: Embedded Controller [EC] (gpe 6)
PCI: Probing PCI hardware
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 9
00:00:01[A] -> IRQ 9 Mode 1 Trigger 1
PIC: IRQ (9) already programmed
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 9
PIC: IRQ (9) already programmed
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
00:00:07[C] -> IRQ 11 Mode 1 Trigger 1
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
PIC: IRQ (11) already programmed
PIC: IRQ (9) already programmed
PIC: IRQ (9) already programmed
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even
'acpi=off
'
PCI: Disabling Via external APIC routing
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
apm: overridden by ACPI.
Starting kswapd
bigpage subsystem: allocated 0 bigpages (=0MB).
kinoded started
VFS: Disk quotas vdquot_6.5.1
aio_setup: num_physpages = 11772
aio_setup: sizeof(struct page) = 48
vesafb: framebuffer at 0xf5000000, mapped to 0xcc016000, size 8192k
vesafb: mode is 800x600x16, linelength=1600, pages=7
vesafb: protected mode interface info at c000:6352
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
mtrr: no more MTRRs available
bootsplash 3.0.9-2003/09/08: looking for picture.... silenjpeg size 16664
bytes,
found (800x600, 8118 bytes, v3).
bootsplash: silent jpeg found.
bootsplash: silent jpeg found.
Console: switching to colour frame buffer device 92x29
fb0: VESA VGA frame buffer device
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT
SHARE_I
RQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
Real Time Clock Driver v1.10e
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize
loop: loaded (max 16 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:07.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 vt82c686a (rev 19) IDE UDMA66 controller on pci00:07.1
ide0: BM-DMA at 0x1820-0x1827, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x1828-0x182f, BIOS settings: hdc:DMA, hdd:pio
hda: HITACHI_DK23AA-51, ATA DISK drive
blk: queue c03bc8e0, I/O limit 4095Mb (mask 0xffffffff)
hdc: TOSHIBA CD-ROM XM-7002Bc, 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: 10009440 sectors (5125 MB) w/512KiB Cache, CHS=10592/15/63, UDMA(33)
ide-floppy driver 0.99.newide
Partition check:
hda: [PTBL] [662/240/63] hda1 hda2 hda3
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
cryptoapi: loaded
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 268k freed
VFS: Mounted root (ext2 filesystem).
reiserfs: found format "3.6" with standard journal
reiserfs: enabling write barrier flush mode
reiserfs: using ordered data mode
reiserfs: checking transaction log (device ide0(3,2)) ...
for (ide0(3,2))
Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Trying to move old root to /initrd ... failed
Unmounting old root
Trying to free ramdisk memory ... okay
Freeing unused kernel memory: 160k freed
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
reiserfs: enabling write barrier flush mode
lvm-mp: allocating 42 lowmem entries at c1e93000
LVM version 1.0.5+(mp-v6c)(22/07/2002) module loaded
reiserfs: enabling write barrier flush mode
Adding Swap: 317512k swap-space (priority 42)
reiserfs: enabling write barrier flush mode
reiserfs: enabling write barrier flush mode
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
Yenta IRQ list 0008, PCI irq9
Socket status: 30000020
8139too Fast Ethernet driver 0.9.26
IPsec Security Association Database (SADB): initialized.
IPsec Security Policy Database (SPD): initialized.
IPsec PF_KEY V2: initialized
IPv6 v0.8 (usagi-cvs/IPsec6 based StS) for NET4.0
IPv6 over IPv4 tunneling driver
ip6_tables: (C) 2000-2002 Netfilter core team
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (1471 buckets, 11768 max) - 304 bytes per conntrack
8139too Fast Ethernet driver 0.9.26
raw1394: /dev/raw1394 device initialized
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 19:50:37 Feb 18 2004
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0x1800, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:07.2-1, assigned address 2
hub.c: USB hub found
hub.c: 4 ports detected
uhci.c: USB Universal Host Controller Interface driver v1.1
hub.c: new USB device 00:07.2-1.3, assigned address 3
usb.c: USB device 3 (vend/prod 0x46d/0xc501) is not claimed by any active
driver
.
hub.c: new USB device 00:07.2-1.4, assigned address 4
usb.c: USB device 4 (vend/prod 0x50f/0x180) is not claimed by any active
driver.
mice: PS/2 mouse device common for all mice
usb.c: registered new driver hiddev
usb.c: registered new driver hid
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb1:3.0
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik
After I did "luna:/home/ste # modprobe 8139too" at the dmesg output I read this lines: " 8139too Fast Ethernet driver 0.9.26 PCI: Setting latency timer of device 02:00.0 to 64 eth0: RealTek RTL8139 Fast Ethernet at 0xcc909000, 00:40:f4:6a:2c:2d, IRQ 9 eth0: Identified 8139 chip type 'RTL-8139C' eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1. eth0: no IPv6 routers present " Stefano
-----Original Message-----
From: Stefano Ceci
Add hotplug at the end of the # Required-Start: $local_fs line.
Ken, please, I still haven't understood how can I add hotplug at the end of # Required .... ecc. What I must add exactly and in ehat files? Thanks Stefano
Use your favorite editor. Mine is vi. vi /etc/init.d/network cursor the the end of the line hit the letter "a" to append after the cursor and add one space then hotplug hit escape to exit write mode :wq! to write and quit vi. Ken
Alle 22:15, sabato 21 febbraio 2004, Ken Schneider ha scritto:
<snip>
# /etc/init.d/network # ### BEGIN INIT INFO # Provides: network # Required-Start: $local_fs # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: # Description: Configure the network interfaces and set up routing ### END INIT INFO
Ken, I've added hotplug at the end of "# Required-Start: $local_fs" and what's new? When I do "luna:/home/ste # insserv -d", now I get: " insserv: There is a loop between service syslog and network " and if I do "luna:/home/ste # insserv hotplug", I get: " insserv: Warning, current runlevel(s) of script `hotplug' overwrites defaults. insserv: Warning, current runlevel(s) of script `hotplug' overwrites defaults. insserv: Warning, current runlevel(s) of script `hotplug' overwrites defaults. insserv: There is a loop between service network and hotplug insserv: There is a loop between service network and hotplug insserv: There is a loop between service syslog and network " What happens? Stefano
-----Original Message-----
From: Stefano Ceci
Ken, I've added hotplug at the end of "# Required-Start: $local_fs" and what's new? When I do "luna:/home/ste # insserv -d", now I get: " insserv: There is a loop between service syslog and network " and if I do "luna:/home/ste # insserv hotplug", I get: " insserv: Warning, current runlevel(s) of script `hotplug' overwrites defaults. insserv: Warning, current runlevel(s) of script `hotplug' overwrites defaults. insserv: Warning, current runlevel(s) of script `hotplug' overwrites defaults. insserv: There is a loop between service network and hotplug insserv: There is a loop between service network and hotplug insserv: There is a loop between service syslog and network " What happens? Stefano
Make sure you keep a log of the changes so that you can go back if you need to. Try removing # X-UnitedLinux-Should-Start: network from /etc/init.d/hotplug I think this line is trying to force the network up before hotplug has started. Ken
Ken, I have solved the problem launching a script into rc5 level. Perhaps it isn't so elgant but now all works fine. Thanks, Stefano
-----Original Message-----
From: Stefano Ceci
Ken, I have solved the problem launching a script into rc5 level. Perhaps it isn't so elgant but now all works fine. Thanks, Stefano
It actually turned out to be a better way since it will not be overwritten during a system upgrade. Should you do a clean install you will need notes to remember what you did. Now is the best time to make the notes, when they are fresh in your mine. Ken
Alle 12:32, domenica 22 febbraio 2004, Ken Schneider ha scritto:
It actually turned out to be a better way since it will not be overwritten during a system upgrade. Should you do a clean install you will need notes to remember what you did. Now is the best time to make the notes, when they are fresh in your mine.
Ken, perhaps it's my poor english, but I don't understand your message :-( Do you mean that the solution isn't so bad? Stefano
On Tue, 2004-02-24 at 13:16, Stefano wrote:
Alle 12:32, domenica 22 febbraio 2004, Ken Schneider ha scritto:
It actually turned out to be a better way since it will not be overwritten during a system upgrade. Should you do a clean install you will need notes to remember what you did. Now is the best time to make the notes, when they are fresh in your mine.
Ken, perhaps it's my poor english, but I don't understand your message :-( Do you mean that the solution isn't so bad? Stefano
If you modify existing start scripts in /etc/init.d they will be over written with the next update/upgrade and you will loose your modifications. By putting your own script there it will not be touched. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Alle 20:37, martedì 24 febbraio 2004, Kenneth Schneider ha scritto:
If you modify existing start scripts in /etc/init.d they will be over written with the next update/upgrade and you will loose your modifications. By putting your own script there it will not be touched.
Ken, sorry for my hard head. Ok now it's clear. I'll make notes to remember my steps. Bye Stefano
Stefano Ceci wrote:
Ken, I have solved the problem launching a script into rc5 level. Perhaps it isn't so elgant but now all works fine. Thanks, Stefano
Stefano, I would be interested to know what you did to get your pcmcia working. I was having the same problems--my pcmcia card was recognized and running, but no internet or dhcp. I felt it had to do with the network starting before hotplug. Seems you are on to something.
On Sunday 22 of February 2004 21:50, Chip Cooper wrote:
Stefano Ceci wrote:
Ken, I have solved the problem launching a script into rc5 level. Perhaps it isn't so elgant but now all works fine. Thanks, Stefano
Stefano,
I would be interested to know what you did to get your pcmcia working. I was having the same problems--my pcmcia card was recognized and running, but no internet or dhcp. I felt it had to do with the network starting before hotplug. Seems you are on to something.
Chip, Read the whole thread - there is a solution. Stefano has added an addition, his own, script to /etc/rc.d/... Regards, -- Marek Chlopek
Alle 21:50, domenica 22 febbraio 2004, Chip Cooper ha scritto:
Stefano,
I would be interested to know what you did to get your pcmcia working. I was having the same problems--my pcmcia card was recognized and running, but no internet or dhcp. I felt it had to do with the network starting before hotplug. Seems you are on to something.
Simply made a script with this 3 commands: modprobe 8139too ifconfig eth0 up dhcpcd. I've then put that file in /etc/init.d/ directory, opened the YaST runlevel editor and selected level 5 for my script. That's all Stefano
participants (7)
-
Chip Cooper -
Joe Morris (NTM) -
Ken Schneider -
Kenneth Schneider
-
Marek Chlopek -
Stefano -
Stefano Ceci