From: Henry N. <Henry.Ne@Arcor.de> - 2007-12-03 23:39:23
|
Hello, http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071203-Snapshot/ A very fresh snapshot supports PCI devices, for example an output of lspci: 00:00.0 Display controller: Unknown device 1a55:0001 00:01.0 IDE interface: Unknown device 1a55:0002 00:02.0 SCSI storage controller: Unknown device 1a55:0003 00:03.0 Multimedia audio controller: Unknown device 1a55:0004 00:04.0 Ethernet controller: Unknown device 1a55:0005 00:05.0 Ethernet controller: Unknown device 1a55:0005 Some other commands should also work: lshw, lsdev, cat /proc/pci... The second news is the SCSI support. SCSI supports partitions in image files. Quemu image files should usable now. To use scsi, specify in config file: scsi0=disk,test.img scsi1=cdrom,test.iso Drivers and comments are written by Steve Shoecraft. Many thanks to him. He sayed "Consider this ALPHA code :P". I have tested, and it was never crashing. :-) -- Henry N. |
From: <Use...@zo...> - 2007-12-05 18:39:12
|
>http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071203-Snaps >hot/ With that snapshot my network card ist not working any more. Using the previous version, NET is OK. colinux:~# uname -a Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 i686 GNU/Li nux colinux:~# /etc/init.d/networking restart Reconfiguring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. SIOCSIFADDR: No such device eth0:0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device eth0:0: ERROR while getting interface flags: No such device eth0:0: ERROR while getting interface flags: No such device Failed to bring up eth0:0. done. colinux:~# lsmod Module Size Used by ipv6 260708 18 smbfs 65016 0 previous version: colinux:~# uname -a Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Wed Sep 12 11:35:56 CEST 2007 i686 GNU/ Linux colinux:~# /etc/init.d/networking restart Reconfiguring network interfaces...Freeing alive inet6 address c70967c0 eth0: duplicate address detected! done. ######################## config.in : kernel=vmlinux initrd=initrd.gz mem=128 cobd0=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi root=/dev/cobd0 hda=:cobd0 eth0=pcap-bridge,"LAN-ADM851X",, C:\coLinux>.\colinux-daemon.exe @config.in Cooperative Linux Daemon, 0.8.0 Compiled on Dec 3 2007 23:38:28 PID: 3508 colinux: booting Linux version 2.6.22-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE Linux)) #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 128MB LOWMEM available. initrd enabled: start: 0xc7f9a000 size: 0x00065881 Entering add_active_range(0, 0, 32768) 0 entries of 256 used Zone PFN ranges: DMA 0 -> 0 Normal 0 -> 32768 early_node_map[1] active PFN ranges 0: 0 -> 32768 On node 0 totalpages: 32768 DMA zone: 0 pages used for memmap Normal zone: 256 pages used for memmap Normal zone: 32512 pages, LIFO batch:7 Built 1 zonelists. Total pages: 32512 Kernel command line: root=/dev/cobd0 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 Setting proxy interrupt vectors PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour CoCON 80x25 Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 125440k/131072k available (1740k kernel code, 0k reserved, 670k data, 132k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffc000 - 0xfffff000 ( 12 kB) vmalloc : 0xc8800000 - 0xffffa000 ( 887 MB) lowmem : 0xc0000000 - 0xc8000000 ( 128 MB) .init : 0xc035e000 - 0xc037f000 ( 132 kB) .data : 0xc02b33e8 - 0xc035afe4 ( 670 kB) .text : 0xc0100000 - 0xc02b33e8 (1740 kB) Calibrating delay loop... 2883.58 BogoMIPS (lpj=14417920) Mount-cache hash table entries: 512 CPU: After generic identify, caps: afe9fbff 00100000 00000000 00000000 00000180 00000000 00000000 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K CPU: After all inits, caps: afe9f3ff 00100000 00000000 00002040 00000180 00000000 00000000 Compat vDSO mapped to ffffe000. CPU: Intel(R) Pentium(R) M processor 1.60GHz stepping 08 Checking 'hlt' instruction... OK. NET: Registered protocol family 16 SCSI subsystem initialized PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) NET: Registered protocol family 2 conet-bridged-daemon: Looking for interface "LAN-ADM851X" conet-bridged-daemon: checking connection: LAN-TAP V9 conet-bridged-daemon: checking connection: LAN-TAP V8(colinux) conet-bridged-daemon: checking connection: LAN-ADM851X conet-bridged-daemon: listening on: ADMtek 851X Series AdapterNDIS 5.0 Miniport Driver... conet-bridged-daemon: listening for: (ether dst 00:ff:31:55:88:00) or (ether broadcast or multicast) or (ip broadcast or multicast) IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 406k freed cofuse init 0.1 (API version 2.2) io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize cobd: loaded (max 32 devices) alias for cobd0 is hda cobd alias cobd0 -> hda created loop: module loaded conet0: irq 10, HWAddr 00:ff:31:55:88:00 coscsi_pci_init: registering... coscsi_pci_probe: adding host... scsi0 : Cooperative Linux SCSI Adapter serio: cokbd at irq 1 mice: PS/2 mouse device common for all mice input: Cooperative Mouse as /class/input/input0 TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI Shortcut mode input: AT Translated Set 2 keyboard as /class/input/input1 RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem). ReiserFS: cobd0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on cobd0 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on cobd0, internal journal EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem). Trying to move old root to /initrd ... okay Freeing unused kernel memory: 132k freed EXT3 FS on cobd0, internal journal NET: Registered protocol family 10 lo: Disabled Privacy Extensions System halted. colinux: Linux VM terminated Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------ |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-12-05 21:25:26
|
Rainer Zocholl wrote: >> http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071203-Snaps >> hot/ > > With that snapshot my network card ist not working any more. > Using the previous version, NET is OK. > > > colinux:~# uname -a > Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 i686 GNU/Li > nux > > > colinux:~# /etc/init.d/networking restart > Reconfiguring network interfaces...SIOCSIFADDR: No such device > eth0: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > eth0: ERROR while getting interface flags: No such device > Failed to bring up eth0. > SIOCSIFADDR: No such device > eth0:0: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > SIOCSIFBRDADDR: No such device > eth0:0: ERROR while getting interface flags: No such device > eth0:0: ERROR while getting interface flags: No such device > Failed to bring up eth0:0. > done. > > colinux:~# lsmod > Module Size Used by > ipv6 260708 18 > smbfs 65016 0 You used modules. Have you upgraded they? initrd.gz should it do, but not know was it? Please try the new build with temporaly disabled module loading. You can simple rename the directory /lib/modules/2.6.22-co-0.8.0 into 2.6.22-co-0.8.0-old Than start coLinux 0.8.0 without "initrd=initrd.gz". > ######################## > > config.in : > > kernel=vmlinux > initrd=initrd.gz > mem=128 > cobd0=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi > root=/dev/cobd0 > hda=:cobd0 > eth0=pcap-bridge,"LAN-ADM851X",, > C:\coLinux>.\colinux-daemon.exe @config.in > Cooperative Linux Daemon, 0.8.0 > Compiled on Dec 3 2007 23:38:28 > > PID: 3508 > colinux: booting > Linux version 2.6.22-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE Linux)) #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 > 128MB LOWMEM available. > [...] > conet-bridged-daemon: Looking for interface "LAN-ADM851X" > conet-bridged-daemon: checking connection: LAN-TAP V9 > conet-bridged-daemon: checking connection: LAN-TAP V8(colinux) > conet-bridged-daemon: checking connection: LAN-ADM851X > conet-bridged-daemon: listening on: ADMtek 851X Series AdapterNDIS 5.0 Miniport Driver... ... the daemon is ok. > [...] > conet0: irq 10, HWAddr 00:ff:31:55:88:00 ... Kernel should have the eth0 now. Give 'ifconfig' an output for eth0 ? Does does 'ifconfig eth0' print some about the interface without error? If yes: Reconfigure it by hands, for example 'ifconfig eth0 192.168.0.1' yust sets an ipaddress. Is eth0 in the list from 'cat /proc/net/dev' ? And last, shows 'lspci' the network interface? That is normal output for eth0: 00:03.0 Ethernet controller: Unknown device 1a55:0005 -- Henry N. |
From: <Use...@zo...> - 2007-12-06 23:15:50
|
Henry.Ne@Arcor.de(Henry Nestler) 05.12.07 22:26 >Rainer Zocholl wrote: >>> http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071203-Sn >>> aps hot/ >> >> With that snapshot my network card ist not working any more. >> Using the previous version, NET is OK. >> >> >> colinux:~# uname -a >> Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 >> i686 GNU/Li nux >> >> >> colinux:~# /etc/init.d/networking restart >> Reconfiguring network interfaces...SIOCSIFADDR: No such device >> eth0: ERROR while getting interface flags: No such device >> SIOCSIFNETMASK: No such device >> eth0: ERROR while getting interface flags: No such device >> Failed to bring up eth0. >> SIOCSIFADDR: No such device >> eth0:0: ERROR while getting interface flags: No such device >> SIOCSIFNETMASK: No such device >> SIOCSIFBRDADDR: No such device >> eth0:0: ERROR while getting interface flags: No such device >> eth0:0: ERROR while getting interface flags: No such device >> Failed to bring up eth0:0. >> done. >> >> colinux:~# lsmod >> Module Size Used by >> ipv6 260708 18 >> smbfs 65016 0 >You used modules. >Have you upgraded they? IIRC: yes ;-) >initrd.gz should it do, but not know was it? >Please try the new build with temporaly disabled module loading. Why is ipv6 a matter for eth0? >You can simple rename the directory /lib/modules/2.6.22-co-0.8.0 into 2.6.22-co-0.8.0-old >Than start coLinux 0.8.0 without "initrd=initrd.gz". >> ######################## >> >> config.in : >> >> kernel=vmlinux >> initrd=initrd.gzi removing that line does not help. >> mem=128 >> cobd0=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi >> root=/dev/cobd0 >> hda=:cobd0 >> eth0=pcap-bridge,"LAN-ADM851X",, >> conet-bridged-daemon: Looking for interface "LAN-ADM851X" >> conet-bridged-daemon: checking connection: LAN-TAP V9 >> conet-bridged-daemon: checking connection: LAN-TAP V8(colinux) >> conet-bridged-daemon: checking connection: LAN-ADM851X >> conet-bridged-daemon: listening on: ADMtek 851X Series AdapterNDIS >> 5.0 Miniport Driver... >... the daemon is ok. >> [...] >> conet0: irq 10, HWAddr 00:ff:31:55:88:00 >.. Kernel should have the eth0 now. >Give 'ifconfig' an output for eth0 ? No, only localinterface is listed. That's why i did the network restart which gav th results above >Does does 'ifconfig eth0' print some about the interface without >error? colinux:~# 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: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) colinux:~# ifconfig eth0 eth0: error fetching interface information: Device not found colinux:~# ls pci ls: pci: No such file or directory >If yes: Reconfigure it by hands, for example 'ifconfig eth0 >192.168.0.1' yust sets an ipaddress. colinux:~# ifconfig eth0 192.168.0.1 SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device colinux:~# >Is eth0 in the list from 'cat /proc/net/dev' ? colinux:~# cat /proc/net/dev Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packe ts errs drop fifo colls carrier compressed lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 eth21: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 colinux:~# ifconfig eth21 192.168.0.1 You have new mail in /var/mail/root colinux:~# eth21: duplicate address detected! colinux:~# ifconfig eth21 Link encap:Ethernet HWaddr 00:FF:34:C3:E0:00 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::2ff:34ff:fec3:e000/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:258 (258.0 b) TX bytes:258 (258.0 b) 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: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) >And last, shows 'lspci' the network interface? As long as i do not have eth0 i can't aptitude lspci because i don't have any network. No arms no cookies ;-( After patchin /etc/network/interfaces to use eth21 i could install pcitools: colinux:/etc/network# lspci 00:00.0 Display controller: Unknown device 1a55:0001 00:01.0 SCSI storage controller: Unknown device 1a55:0003 00:02.0 Multimedia audio controller: Unknown device 1a55:0004 00:03.0 Ethernet controller: Unknown device 1a55:0005 >That is normal output for eth0: > 00:03.0 Ethernet controller: Unknown device 1a55:0005 So the lastquestion: Why is it eth21 and not eth0? Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------ |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-12-06 23:55:04
|
Rainer Zocholl wrote: > Henry.Ne@Arcor.de(Henry Nestler) 05.12.07 22:26 > >> Rainer Zocholl wrote: >>>> http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071203-Sn >>>> aps hot/ >>> With that snapshot my network card ist not working any more. >>> Using the previous version, NET is OK. >>> >>> >>> colinux:~# uname -a >>> Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 >>> i686 GNU/Li nux >>> >>> >>> colinux:~# /etc/init.d/networking restart >>> Reconfiguring network interfaces...SIOCSIFADDR: No such device >>> eth0: ERROR while getting interface flags: No such device >>> SIOCSIFNETMASK: No such device >>> eth0: ERROR while getting interface flags: No such device >>> Failed to bring up eth0. >>> SIOCSIFADDR: No such device >>> eth0:0: ERROR while getting interface flags: No such device >>> SIOCSIFNETMASK: No such device >>> SIOCSIFBRDADDR: No such device >>> eth0:0: ERROR while getting interface flags: No such device >>> eth0:0: ERROR while getting interface flags: No such device >>> Failed to bring up eth0:0. >>> done. >>> >>> colinux:~# lsmod >>> Module Size Used by >>> ipv6 260708 18 >>> smbfs 65016 0 > >> You used modules. >> Have you upgraded they? > > IIRC: yes ;-) > >> initrd.gz should it do, but not know was it? > >> Please try the new build with temporaly disabled module loading. > > Why is ipv6 a matter for eth0? Was an idea for unmatching kernel and module, because we have currently no module version checks beween different builds. And on this build the kernel config was changed. > >> You can simple rename the directory /lib/modules/2.6.22-co-0.8.0 into 2.6.22-co-0.8.0-old > >> Than start coLinux 0.8.0 without "initrd=initrd.gz". > >>> ######################## >>> >>> config.in : >>> >>> kernel=vmlinux >>> initrd=initrd.gzi > > removing that line does not help. Have you also removed or renamed the module dirrectory? No module should load, to see problems from module or kernel. >> Is eth0 in the list from 'cat /proc/net/dev' ? > > colinux:~# cat /proc/net/dev > Inter-| Receive | Transmit > face |bytes packets errs drop fifo frame compressed multicast|bytes packe > ts errs drop fifo colls carrier compressed > lo: 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 > eth21: 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 That's bad. > [...] > So the lastquestion: > Why is it eth21 and not eth0? Yes. That's very interesting. Please send me your file 'config.in' as it is. I think, you found the error, I long time know and looking for an example! Than add a space and "#### some text" in end of same line with "eth0=...". Or add a new line at end of file. You have an space before eth0? Remove it. -- Henry N. |
From: <Use...@zo...> - 2007-12-07 02:26:43
|
Henry.Ne@Arcor.de(Henry Nestler) 07.12.07 00:55 >>> Is eth0 in the list from 'cat /proc/net/dev' ? >> >> colinux:~# cat /proc/net/dev >> Inter-| Receive | >> Transmit face |bytes packets errs drop fifo frame compressed >> multicast|bytes packe >> ts errs drop fifo colls carrier compressed >> lo: 0 0 0 0 0 0 0 0 >> 0 >> 0 0 0 0 0 0 0 >> eth21: 0 0 0 0 0 0 0 0 >> 0 0 0 0 0 0 0 0 >That's bad. >> [...] >> So the lastquestion: >> Why is it eth21 and not eth0? >Yes. That's very interesting. >Please send me your file 'config.in' as it is. I think, you found the >error, I long time know and looking for an example! >Than add a space and "#### some text" in end of same line with >"eth0=...". Or add a new line at end of file. >You have an space before eth0? Remove it. I had. iremoved: ethxx is still counting up. Starting with parameters on command line does not help too. (I made that config.in to easy testing this bug) ........... kernel=vmlinux initrd=initrd.gz mem=128 cobd0=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi root=/dev/cobd0 hda=:cobd0 eth0=pcap-bridge,"LAN-ADM851X",, I removed trailing " " to: No change. If i omit the eth0 lien, i don't get an eth. BTW: I did not install the pcap driver coming with colinus setup because my current is newer. kernel=vmlinux initrd=initrd.gz mem=128 cobd0=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi root=/dev/cobd0 hda=:cobd0 ###### eth0=pcap-bridge,"LAN-ADM851X",, eth0=slirp C:\coLinux>colinux-daemon.exe -k NT @config.in Cooperative Linux Daemon, 0.8.0 Compiled on Dec 3 2007 23:38:28 unsupported network transport type: slir supported types are: tuntap, pcap-bridge, slirp daemon: error parsing configuration parameters and boot params daemon: error parsing parameters NOTE: Run without arguments to receive help about command line syntax. Reason: The last line was not terminated with CR+LF- Using slirp: Still counting up! I assume the is a "static" symbol which is not initialzed and hapens to be placed always on the location. Rainer |
From: <ric...@gm...> - 2007-12-07 05:42:16
|
> Using slirp: > Still counting up! > Is slirp counting up with each boot, or did it pick an unused number greater than any used by pcap-bridge, but no longer climbing? > I assume the is a "static" symbol which is not initialzed and hapens > to be placed always on the location. Values of static variables aren't preserved across a reboot. It's something stored in your linux filesystem. > > > > Rainer > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-12-07 20:25:10
|
Rainer, ric...@gm... wrote: >> I assume the is a "static" symbol which is not initialzed and hapens >> to be placed always on the location. > > Values of static variables aren't preserved across a reboot. It's > something stored in your linux filesystem. True, you can check who counts it up. The coLinux driver, or your filesystem? Run colinux from initrd only: colinux-daemon kernel=vmlinux initrd=initrd.gz eth0=slirp root=/dev/ram0 Inside this, check the device number with "cat /proc/net/dev" Reboot or shutdown and start it again and check it again. (shutdown in this initrd goes with command 'halt' on linux prompt.) Count's it there also? >From Martins mail. That's true: Every boot got an other MAC, if no mac is configured. Please try this line for your LAN: eth0=pcap-bridge,"LAN-ADM851X",00:11:22:33:44:55 The random mac is not new in this version. But, the pcoc/pci interface is new. Perhaps your ditribution now can get it and "thinks" you have plugged in a new network card every boot. -- Henry N. |
From: <Use...@zo...> - 2007-12-08 14:50:11
|
Henry.Ne@Arcor.de(Henry Nestler) 07.12.07 21:25 >Rainer, >ric...@gm... wrote: >>> I assume the is a "static" symbol which is not initialzed and >>> hapens to be placed always on the location. >> >> Values of static variables aren't preserved across a reboot. It's >> something stored in your linux filesystem. >True, you can check who counts it up. The coLinux driver, or your >filesystem? >Run colinux from initrd only: >colinux-daemon kernel=vmlinux initrd=initrd.gz eth0=slirp >root=/dev/ram0 Inside this, check the device number with "cat >/proc/net/dev" Reboot or shutdown and start it again and check it >again. (shutdown in this initrd goes with command 'halt' on linux >prompt.) Count's it there also? >>From Martins mail. That's true: Every boot got an other MAC, if no >>mac >is configured. Please try this line for your LAN: > eth0=pcap-bridge,"LAN-ADM851X",00:11:22:33:44:55 >The random mac is not new in this version. Yes. >But, the proc/pci interface is new. >Perhaps your ditribution now can get it and "thinks" you have >plugged in a new network card every boot. Yes. this way it is not counting up anymore. I use debian etch. So maybe colinux should not use a random mac on every start but a fixed? Say calculated from host name XOR guest name or so? Don't worry if 2 VMs on the same box would have the same ethernet MAC: With (TCP)IP this is not a severe problem, as long as both VM have different IPs. Only the network performance would be slightly decreased as one box would see IP-Packets in it's IP stac with are not intented to be received here. There will be a nice kernel message if that happens. That are all problems i would expect with a "static" MAC. (no) Or should reset the ethernet dev counter? As a user would be really surpised if he said: "use eth0" and colinux generates a "eth1" only becaus the host name changes. (no) Or store a eth-MAC table somewhere (hidden?) in image and reuse the values? Independent if "slirp" "bridged" etc. eth0 should have always the same MAC. That would too reduce problems with old MACs stored in PC arp tables or switch tables. (maybe?) Rainer |
From: <Use...@zo...> - 2007-12-08 17:12:14
|
colinux:~# uname -a Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 i686 GNU/Linux shows an, em, effect on debian 4.0: Effect: After the second start of colinux the network is not working anymore. An attempt to start the network from console manually complaints like this: colinux:~# /etc/init.d/networking restart Reconfiguring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. SIOCSIFADDR: No such device ... #cat /proc/net/dev shows an eth device number greater eth0, incremented with each boot. The effect is (currently) only seen on debian 4.0 (etch). Workarround: 1st step: Assign a fixed MAC address in the colinux config: For example: eth0=pcap-bridge,,0A:C0:71:65:08:00, (implicit ethernet device is not recommanded) eth0=pcap-bridge,"WindowsNameOfYourEthernet",0A:C0:71:65:08:00, eth0=tuntap,LAN-TAP V8(colinux),0A:C0:71:65:08:00, Attention: The "second" nibble (from left) should have only the values 2,6,A or E. The remainder does not matter as long as it is unique in your LAN. 2nd step: remove all entries in "/etc/udev/rules.d/z25_persistent-net.rules" like these: SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:06:be:41:00", NAME="eth0" # PCI device 0x1a55:0x0005 (conet) SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:25:e6:00:00",NAME="eth1" (Typically the file is empty except the comment header) Rainer |
From: Juergen H. <jue...@gm...> - 2007-12-08 17:27:27
|
Rainer Zocholl wrote: > colinux:~# uname -a > Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 i686 GNU/Linux > > > > Workarround: > > 1st step: > Assign a fixed MAC address in the colinux config: > > Always a good idea! > > 2nd step: > remove all entries in > > "/etc/udev/rules.d/z25_persistent-net.rules" > > like these: > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:06:be:41:00", NAME="eth0" > > # PCI device 0x1a55:0x0005 (conet) > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:25:e6:00:00",NAME="eth1" > > I was just going to suggest this, but it looks, you found it on your own ;-) > (Typically the file is empty except the comment header) > > No it is typically not empty. It should contain a line for all statically defined (not via dhcp) devices. If you have multiple ethernet devices and you have a fixed setup for a specific ethernet card you normally want, that this network setup always applies to the same network card. If you insert a new one in your computer, this doesn't necessarily apply any more, because udev may allocate this number in a different order. To prevent this you can/and should bind a device name to a certain hardware (if a static network setup is used). Juergen |
From: <ric...@gm...> - 2007-12-08 21:05:12
|
On Dec 8, 2007 5:27 PM, Juergen Hennerich <jue...@gm...> wrote: > Rainer Zocholl wrote: > > colinux:~# uname -a > > Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Dec 3 23:34:07 CET 2007 i686 GNU/Linux > > > > > > > > Workarround: > > > > 1st step: > > Assign a fixed MAC address in the colinux config: > > > > > Always a good idea! I don't know why anyone ever thought this was optional. Ethernet interfaces MUST have a unique consistent MAC address. Maybe colinux should start rejecting (or warning) config files where the MAC isn't specified. |
From: <Use...@zo...> - 2007-12-08 21:29:48
|
ric...@gm...(ric...@gm...) 08.12.07 21:05 Once upon a time "ric...@gm... " shaped the electrons to say... >On Dec 8, 2007 5:27 PM, Juergen Hennerich <jue...@gm...> >> wrote: Rainer Zocholl wrote: >>> colinux:~# uname -a >>> Linux colinux 2.6.22-co-0.8.0 #1 PREEMPT Mon Dec 3 23:34:07 CET >>> 2007 i686 GNU/Linux >>> >>> >>> >>> Workarround: >>> >>> 1st step: >>> Assign a fixed MAC address in the colinux config: >>> >>> >> Always a good idea! >I don't know why anyone ever thought this was optional. Ethernet >interfaces MUST have a unique consistent MAC address. to remember: Suns sparc stations were/are delivered with the same MAC address. As long as there is only one box in the LAN all is well. Aber the second will work mostly too. http://docs.sun.com/app/docs/doc/816-4554/6maoq0288?a=view#mac11 They use /etc/hostname.<interface> contains the MAC address for <interface> to define other mac addresss. >Maybe colinux should start rejecting (or warning) config files >where the MAC isn't specified. ..and should suggest a better config line to use including with a good "local admistered" MAC address compatible with IEEE 802.3 standard. Rainer |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-12-08 21:49:24
|
ric...@gm... wrote: > I don't know why anyone ever thought this was optional. Ethernet > interfaces MUST have a unique consistent MAC address. Maybe colinux > should start rejecting (or warning) config files where the MAC isn't > specified. Should make a random MAC only ones per host and store it in registry? -- Henry N. |
From: <Use...@zo...> - 2007-12-09 00:24:02
|
Henry.Ne@Arcor.de(Henry Nestler) 08.12.07 22:50 Once upon a time "Henry Nestler " shaped the electrons to say... >ric...@gm... wrote: >> I don't know why anyone ever thought this was optional. Ethernet >> interfaces MUST have a unique consistent MAC address. Maybe colinux >> should start rejecting (or warning) config files where the MAC isn't >> specified. >Should make a random MAC only ones per host and store it in registry? Store it in an .ini file, not that crap "registry". Or suggest one the user has to place in conf file or on the command line. Or generate a conf file the user should use at the next start. Problem: slirp, pcap etc. should have the same MAC! maybe a new config entry eth0mac= eth1mac= etc. ? This way the MAC address of eth0 will not change when switching between slirp an tap or what ever. An otherway: To get one guarantied unique MAC address in this LAN - take the MAC address of a physically existing interface (from registry) - Set the bit 1 of the highest byte to invalidate the OUI by indicating LAA - done. Your turn to generarate a second uniq MAC address ;-) Or simply generate one fixed MAC LAA. If the user needs two interfaces he must generate uniq MAC LA addreses. A warning would be fair. Rainer |
From: Martin A. <mar...@af...> - 2007-12-07 02:01:13
|
Hi, > So the lastquestion: > Why is it eth21 and not eth0? This could be a problem with your combination of Linux distribution and coLinux configuration. If you didn't specify a certain MAC address for your ethernet device coLinux will randomly chose one at start, if I remember correctly, and this will give a different MAC address each time. On the other hand, newer Linux distributions use udev for managing device files and network interfaces and udev tries to provide persistent names. It usually expects a MAC address to be constant but if it changes each time (like in your situation) then it will simply take the next (never used before) interface name. It's not always like this depending on your udev configuration (which is distribution dependent). Hope that helps, Martin |
From: <ric...@gm...> - 2007-12-07 05:40:17
|
On Dec 6, 2007 7:05 PM, Martin Afanasjew <mar...@af...> wrote: > Hi, > > > So the lastquestion: > > Why is it eth21 and not eth0? > This could be a problem with your combination of Linux distribution and > coLinux configuration. If you didn't specify a certain MAC address for > your ethernet device coLinux will randomly chose one at start, if I > remember correctly, and this will give a different MAC address each > time. On the other hand, newer Linux distributions use udev for managing > device files and network interfaces and udev tries to provide persistent > names. It usually expects a MAC address to be constant but if it changes > each time (like in your situation) then it will simply take the next > (never used before) interface name. It's not always like this depending > on your udev configuration (which is distribution dependent). > > Hope that helps, > Martin > It's worth reading the section "Locally administered addresses" at http://en.wikipedia.org/wiki/MAC_address and picking a permanent MAC address for the tap or winpcap device. > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: <Use...@zo...> - 2007-12-08 15:20:02
|
ric...@gm...(ric...@gm...) 06.12.07 23:40 >It's worth reading the section "Locally administered addresses" at >http://en.wikipedia.org/wiki/MAC_address and picking a permanent MAC >address for the tap or winpcap device. Interresting reading to "refurbish" ethernet knowledge ;-) So: the generated MAC adresses of colinux should, emm "must" start at 02:xx:xx:xx:xx to have it indicated as "locally administered address". IOW: (only)the high nipples x2: x6: xA: xE: would be OK! Question: Why do i want to set the non-OUI bit? Answer: As that bit is never set in a Organizationally Unique Identifier (OUI) you can be absoletely sure never ever to interfere with any official assigned MAC addresess, even been assigned in future. Or? |
From: <Use...@zo...> - 2007-12-08 15:34:19
|
>>http://en.wikipedia.org/wiki/MAC_address and picking a permanent MAC >>address for the tap or winpcap device. >So: >the generated MAC adresses of colinux should, emm "must" start at >02:xx:xx:xx:xx >to have it indicated as "locally administered address". >IOW: >(only)the high nipples >x2: >x6: >xA: >xE: >would be OK Suggestion for a MAC Start value: 0A:C0:11:__:__:__ 0A:C0:71:__:__:__ AC071 = "A COLI"nux in "hex modified l33t"(tm) Or: Ask IEEE for an free(?) OUI? Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------ |
From: <ric...@gm...> - 2007-12-08 21:01:13
|
On 08 Dec 2007 16:19:00 +0100, Rainer Zocholl <Use...@zo...> wrote: > ric...@gm...(ric...@gm...) 06.12.07 23:40 > > > >It's worth reading the section "Locally administered addresses" at > >http://en.wikipedia.org/wiki/MAC_address and picking a permanent MAC > >address for the tap or winpcap device. > > > Interresting reading to "refurbish" ethernet knowledge ;-) > > So: > the generated MAC adresses of colinux should, emm "must" start at > 02:xx:xx:xx:xx > to have it indicated as "locally administered address". > > IOW: > (only)the high nipples > x2: > x6: > xA: > xE: > would be OK! looks right to me, any of those nibbles will be LAA and therefore you don't need to worry about conflicts with existing cards (of course, if someone else on your LAN segment is also making up MAC address...) > > > > Question: > Why do i want to set the non-OUI bit? > Answer: > As that bit is never set in a Organizationally Unique Identifier (OUI) > you can be absoletely sure never ever to interfere with any official assigned > MAC addresess, even been assigned in future. > > Or? > > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: <Use...@zo...> - 2007-12-08 14:28:15
|
mar...@af...(Martin Afanasjew) 07.12.07 02:05 Once upon a time "Martin Afanasjew " shaped the electrons to say... >Hi, >> So the lastquestion: >> Why is it eth21 and not eth0? >This could be a problem with your combination of Linux distribution >and coLinux configuration. If you didn't specify a certain MAC address >for your ethernet device coLinux will randomly chose one at start, if >I remember correctly, and this will give a different MAC address each >time. On the other hand, newer Linux distributions use udev for >managing device files and network interfaces and udev tries to provide >persistent names. It usually expects a MAC address to be constant but >if it changes each time (like in your situation) then it will simply >take the next (never used before) interface name. It's not always like >this depending on your udev configuration (which is distribution >dependent). kernel=vmlinux initrd=initrd.gz mem=128 cobd0=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi root=/dev/cobd0 hda=:cobd0 ###### eth0=pcap-bridge,"LAN-ADM851X",, #####eth0=slirp eth0=pcap-bridge,"LAN-ADM851X",00:FF:05:65:08:00, ##### colinux:~# cat /proc/net/dev Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packe ts errs drop fifo colls carrier compressed lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 eth33: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 colinux:~# ifconfig eth33 eth33 Link encap:Ethernet HWaddr 00:FF:05:65:08: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) This way it stays at eth33! Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------ |
From: <Use...@zo...> - 2007-12-08 14:28:39
|
mar...@af...(Martin Afanasjew) 07.12.07 02:05 Once upon a time "Martin Afanasjew " shaped the electrons to say... >Hi, >> So the lastquestion: >> Why is it eth21 and not eth0? >This could be a problem with your combination of Linux distribution >and coLinux configuration. If you didn't specify a certain MAC address >for your ethernet device coLinux will randomly chose one at start, if >I remember correctly, and this will give a different MAC address each >time. On the other hand, newer Linux distributions use udev for >managing device files and network interfaces and udev tries to provide >persistent names. It usually expects a MAC address to be constant but >if it changes each time (like in your situation) then it will simply >take the next (never used before) interface name. It's not always like >this depending on your udev configuration (which is distribution >dependent). I run debian 4 etch. colinux:~# cat /etc/issue Debian GNU/Linux 4.0 \n \l >Hope that helps, It sounds a vey good explanation of the effect! But: It does not explain, why the effects depends on the colinux version! I use the same images for both colinux version. Proofed: colinux:~# cat /proc/net/dev Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packe ts errs drop fifo colls carrier compressed lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 eth29: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 colinux:~# ifconfig eth29 eth29 Link encap:Ethernet HWaddr 00:FF:52:E0:FE:C0 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) colinux:~# cat /proc/net/dev Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packe ts errs drop fifo colls carrier compressed lo: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 eth30: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 colinux:~# ifconfig eth30 eth30 Link encap:Ethernet HWaddr 00:FF:7D:5B:97: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) C:\coLinux>type config.in kernel=vmlinux initrd=initrd.gz mem=128 cobd0=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi root=/dev/cobd0 hda=:cobd0 ###### eth0=pcap-bridge,"LAN-ADM851X",, eth0=slirp --------------------------------------------------------------- Colinux parser has a problem if the last line is not terminated with a CR-LF. Io.W.: if the last line ends at the end of file the colinux parser comes out of sync. Butthat is not the reason of the problem. |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-12-08 21:46:24
|
Rainer Zocholl schrieb: > mar...@af...(Martin Afanasjew) 07.12.07 02:05 > > Once upon a time "Martin Afanasjew " shaped the electrons to say... > >> Hi, > >>> So the lastquestion: >>> Why is it eth21 and not eth0? >> This could be a problem with your combination of Linux distribution >> and coLinux configuration. If you didn't specify a certain MAC address >> for your ethernet device coLinux will randomly chose one at start, if >> I remember correctly, and this will give a different MAC address each >> time. On the other hand, newer Linux distributions use udev for >> managing device files and network interfaces and udev tries to provide >> persistent names. It usually expects a MAC address to be constant but >> if it changes each time (like in your situation) then it will simply >> take the next (never used before) interface name. It's not always like >> this depending on your udev configuration (which is distribution >> dependent). > > I run debian 4 etch. > colinux:~# cat /etc/issue > Debian GNU/Linux 4.0 \n \l > > >> Hope that helps, > > It sounds a vey good explanation of the effect! > But: > It does not explain, why the effects depends on the colinux version! > I use the same images for both colinux version. The pci interface is new in this version. The distribution can get the list of hardware now. > C:\coLinux>type config.in > kernel=vmlinux > initrd=initrd.gz > mem=128 > cobd0=\colinux.disks\Debian-3.0r2.ext3-mit-backports.imi > root=/dev/cobd0 > hda=:cobd0 > ###### eth0=pcap-bridge,"LAN-ADM851X",, > eth0=slirp > > --------------------------------------------------------------- > > Colinux parser has a problem if the last line is not terminated > with a CR-LF. Io.W.: if the last line ends at the end of file > the colinux parser comes out of sync. Butthat is not the reason > of the problem. Ah, I see, would be fix in next version. Thanks for explain. -- Henry N. |
From: Henry N. <Henry.Ne@Arcor.de> - 2007-12-10 21:26:12
|
Henry Nestler wrote: > Rainer Zocholl wrote: >> Colinux parser has a problem if the last line is not terminated >> with a CR-LF. Io.W.: if the last line ends at the end of file >> the colinux parser comes out of sync. Butthat is not the reason >> of the problem. > > Ah, I see, would be fix in next version. Thanks for explain. Is fixed in SVN r790 and r791: http://colinux.svn.sourceforge.net/viewvc/colinux?view=rev&revision=791 -- Henry N. |
From: <Use...@zo...> - 2007-12-06 23:36:38
|
Henry.Ne@Arcor.de(Henry Nestler) 05.12.07 22:26 >Is eth0 in the list from 'cat /proc/net/dev' ? With every start the eth-number is increased. meanwhile it is eth22. Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------ |