Re: onboard ethernet on Tyan Thunder K8WE (s2895)
On Sat, Apr 01, 2006 at 12:30:20PM -0800, David Liontooth wrote: Another way to solve this -- sort of oldfashioned but very elegant -- is to use labels. Say you want to label drives tv0 to tv2: * ext2 and ext3: e2label or tune2fs -L tv0 /dev/sde1 * XFS: xfs_admin -L tv1 /dev/sda1 (max 12 characters, unmounted drive) * JFS: jfs_tune -L tv2 /dev/sdb1 (max 16 characters) In /etc/fstab, LABEL=tv0 /tv0ext2auto,defaults,user,exec 0 0 LABEL=tv1 /tv1jfs auto,defaults,user,exec 0 0 LABEL=tv2 /tv2xfs auto,defaults,user,exec 0 0 No matter how you attach the drives -- SATA channel, USB -- they will be mounted where they should. This has been around for so long that it's rumored the guy who came up with it also invented the wheel! I tried that, but my initrd said something about not finding /dev/disk/label/ROOT when I passed root=LABEL=ROOT, and I had labeled the root filesystem with e2label. So either something doesn't work with labels in 2.6.15, or initramfs-tools doesn't generate an initrd that supports it. If someone knows how to solve that part of it, then I will be using labels to fix this. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: onboard ethernet on Tyan Thunder K8WE (s2895)
Lennart Sorensen wrote: On Sat, Apr 01, 2006 at 12:30:20PM -0800, David Liontooth wrote: Another way to solve this -- sort of oldfashioned but very elegant -- is to use labels. Say you want to label drives tv0 to tv2: * ext2 and ext3: e2label or tune2fs -L tv0 /dev/sde1 * XFS: xfs_admin -L tv1 /dev/sda1 (max 12 characters, unmounted drive) * JFS: jfs_tune -L tv2 /dev/sdb1 (max 16 characters) In /etc/fstab, LABEL=tv0 /tv0ext2auto,defaults,user,exec 0 0 LABEL=tv1 /tv1jfs auto,defaults,user,exec 0 0 LABEL=tv2 /tv2xfs auto,defaults,user,exec 0 0 No matter how you attach the drives -- SATA channel, USB -- they will be mounted where they should. This has been around for so long that it's rumored the guy who came up with it also invented the wheel! I tried that, but my initrd said something about not finding /dev/disk/label/ROOT when I passed root=LABEL=ROOT, and I had labeled the root filesystem with e2label. So either something doesn't work with labels in 2.6.15, or initramfs-tools doesn't generate an initrd that supports it. If someone knows how to solve that part of it, then I will be using labels to fix this. Ah, I haven't used initrd with this -- keep us posted. Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: onboard ethernet on Tyan Thunder K8WE (s2895)
On Fri, Mar 31, 2006 at 08:09:33PM -0800, Sebastian Haase wrote: Does that mean that the port assignment COULD potentially change after each reboot !? And I need a special script to adjust /etc/network/interfaces !? Hard to believe... [[ OK - I just started reading the mentioned wiki web page and here is a quote just for documentation purposes: One of the problems of Linux is that the order of the network interfaces is unpredictable. Between reboots it does stay the same, but it is very well possible that after an upgrade to a new kernel or the addition or replacement of a network card (NIC) that the other of all network interface changes. For example, what used to be eth0 now becomes eth1 or eth2 or visa versa. Well with udev this now applies to every @[EMAIL PROTECTED] boot. :) You can create a rule file for udev telling it which MAC address should be named what eth name. I tried this and it worked very well. Now if someone has an idea how to control the order of sata drives in initramfs-tools initrd on 2.6.15 I would be happy. Half the time my promise card goes first, and half the time the via onboard goes first. Since disk labels seem unsupported at this time, having the disk order change (sda - sdc, sdb - sdd), being able to at least have something make sure the initrd can actually find the root partition would be very handy. At this point I am getting close to thinking whoever invented udev shouldn't have. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: onboard ethernet on Tyan Thunder K8WE (s2895)
Lennart Sorensen wrote: On Fri, Mar 31, 2006 at 08:09:33PM -0800, Sebastian Haase wrote: Does that mean that the port assignment COULD potentially change after each reboot !? And I need a special script to adjust /etc/network/interfaces !? Hard to believe... [[ OK - I just started reading the mentioned wiki web page and here is a quote just for documentation purposes: One of the problems of Linux is that the order of the network interfaces is unpredictable. Between reboots it does stay the same, but it is very well possible that after an upgrade to a new kernel or the addition or replacement of a network card (NIC) that the other of all network interface changes. For example, what used to be eth0 now becomes eth1 or eth2 or visa versa. Well with udev this now applies to every @[EMAIL PROTECTED] boot. :) You can create a rule file for udev telling it which MAC address should be named what eth name. I tried this and it worked very well. Now if someone has an idea how to control the order of sata drives in initramfs-tools initrd on 2.6.15 I would be happy. Half the time my promise card goes first, and half the time the via onboard goes first. Since disk labels seem unsupported at this time, having the disk order change (sda - sdc, sdb - sdd), being able to at least have something make sure the initrd can actually find the root partition would be very handy. At this point I am getting close to thinking whoever invented udev shouldn't have. Hi Len, Another way to solve this -- sort of oldfashioned but very elegant -- is to use labels. Say you want to label drives tv0 to tv2: * ext2 and ext3: e2label or tune2fs -L tv0 /dev/sde1 * XFS: xfs_admin -L tv1 /dev/sda1 (max 12 characters, unmounted drive) * JFS: jfs_tune -L tv2 /dev/sdb1 (max 16 characters) In /etc/fstab, LABEL=tv0 /tv0ext2auto,defaults,user,exec 0 0 LABEL=tv1 /tv1jfs auto,defaults,user,exec 0 0 LABEL=tv2 /tv2xfs auto,defaults,user,exec 0 0 No matter how you attach the drives -- SATA channel, USB -- they will be mounted where they should. This has been around for so long that it's rumored the guy who came up with it also invented the wheel! David Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
onboard ethernet on Tyan Thunder K8WE (s2895)
Hi, I just got this new dual Opteron PC at my desk... I tried the official netinst CD and http://tinyplanet.ca/~lsorense/amd64/sarge-amd64-2.6.12-netinst.iso neither recognises the NIC. All I know is, it's a nVidia MAC nForce Prof 2200 and (2nd port) Prof 2050. I read some about forcedeth but don't know what that is ... Any hints !? Thanks, Sebastian Haase -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: onboard ethernet on Tyan Thunder K8WE (s2895)
Greetings Brett: I have that same board. I could not get it to boot off of the Sarge netinst CD at all. It successfully boots and installs from the Etch testing netinst CD, though. -Scott -- Original message -- From: Brett Ellis [EMAIL PROTECTED] Trying doing a lspci in one of the text base windows and see if it sees the nics. You may need to boot with pci=nommconf to see past the nvidia bridge. Brett Sebastian Haase wrote: Hi, I just got this new dual Opteron PC at my desk... I tried the official netinst CD and http://tinyplanet.ca/~lsorense/amd64/sarge-amd64-2.6.12-netinst.iso neither recognises the NIC. All I know is, it's a nVidia MAC nForce Prof 2200 and (2nd port) Prof 2050. I read some about forcedeth but don't know what that is ... Any hints !? Thanks, Sebastian Haase -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: onboard ethernet on Tyan Thunder K8WE (s2895)
Thanks for the replies. sarge-amd64-2.6.12-netinst.iso did not auto-detect the NICs but after manually choosing forcedeth it actually worked. ONLY: that I did get some timeout kernel error messages (sorry, forgot the exact text) and it only really worked after I switched the network cable between the two ports back and forth many times !! How can I know which port is eth0 and which eth1 ? And - if not - can I at least rely on the order staying the same between reboots ?? (I want to connect one port to the internet the other to a local (unroutable) private sub-net... Is forcedeth the only possible driver ? Just curious ... Thanks, Sebastian Haase David Liontooth wrote: Sebastian Haase wrote: Hi, I just got this new dual Opteron PC at my desk... I tried the official netinst CD and http://tinyplanet.ca/~lsorense/amd64/sarge-amd64-2.6.12-netinst.iso neither recognises the NIC. All I know is, it's a nVidia MAC nForce Prof 2200 and (2nd port) Prof 2050. I read some about forcedeth but don't know what that is ... Any hints !? Thanks, Sebastian Haase According to http://www.tyan.com/products/html/thunderk8we_spec.html it does have two nvidia NICs -- I found on a rather different Gigabyte K8NS with a similar NIC (identified on the board as ICS1883, regrettably disabled on recent versions of this mobo) that the card had some difficulties getting going during installation, but in fact is well supported as a gb NIC by the forcedeth driver. You may need a more recent version than the one on the install CD. I get this in dmesg: eth0: forcedeth.c: subsystem: 01458:e000 bound to :00:05.0 forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.31. This just to give thumbs up that this is the driver and it should work fine. Someone with the same board would know if there are issues. Dave *Integrated Secure Network Processor* • Two IEEE 802.3 Nvidia MAC 1000/100/10 Ethernet (1st from nForce™ Prof. 2200, 2nd from nForce Prof. 2050) • Supports WOL and PXE • Supports Ethernet Jumbo Frames (9018 Bytes) • Full Duplex Gigabit Ethernet support -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: onboard ethernet on Tyan Thunder K8WE (s2895)
Sebastian Haase wrote: Thanks for the replies. sarge-amd64-2.6.12-netinst.iso did not auto-detect the NICs but after manually choosing forcedeth it actually worked. ONLY: that I did get some timeout kernel error messages (sorry, forgot the exact text) and it only really worked after I switched the network cable between the two ports back and forth many times !! Good to hear you got it going, but do upgrade your kernel -- the driver should work without problems. How can I know which port is eth0 and which eth1 ? And - if not - can I at least rely on the order staying the same between reboots ?? (I want to connect one port to the internet the other to a local (unroutable) private sub-net... Yes, you can -- as usual in Linux, there are several ways. Check out http://www.science.uva.nl/research/air/wiki/LogicalInterfaceNames -- the script /share/usr/share/doc/ifupdown/examples/get-mac-address.sh comes with the ifupdown package. Is forcedeth the only possible driver ? Just curious ... Yes -- and it works great! David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
