From EnricoToniolo at calearo.com Wed Feb 9 10:04:52 2005 From: EnricoToniolo at calearo.com (Enrico Toniolo) Date: Wed, 9 Feb 2005 11:04:52 +0100 Subject: problem with XFree and video card detecting installing RH WS Enterprise Ed. 3: what steps to follow for a working installation Message-ID: Hello to All, first of all I advise I'm all but expert of linux o.s., and I apologise if my question may be trivial for someone, now my problem: I had an IBM Intellistation A-Pro (AMD64bit Opteron) with "Linux Red Hat WS Enterprise Edition version 3" preinstalled. I have had to reinstall all the O.S. with a different scheme of partitions but, it didn't install properly as I am going to describe in the following: 1. The CD 1, of 10 of the "Linux Red Hat WS Enterprise Edition" included with the Workstation, was given to the Workstation when it started up. 2. I chose the graphical mode but the installer did not detect any video card (what mounted in the machine is Nvidia Quadro FX 1100), so the textual mode started. 3. Then I chose to install everything, and the installation finished well, but 4. Linux startup in textual mode and doesn't exist any /etc/X11/XF86Config configuration file or any xf86config, XF86Setup or Xconfigurator or xf86cfg executable to configure it. What I think is that after the Linux-installer didn't detect/recognize any video card it doesn't install XFree properly or completely, because even installing the video card driver from: ftp://ftp.software.ibm.com/pc/pccbbs/intellistation/nvidia-linux-x86_64-1.0-6629-pkg2.run it wasn't possible to configure any XFree for the same reason of the point 4 above. Probably after installing the video card driver, XFree must be reinstalled, but I don't know how, and I'm not completely sure of that. When the IBM Opteron arrived, the Linux there preinstalled worked properly. So it means there is a way to install it properly from the 10 Installation CDs included and the Nvidia driver not included. This way is not described in the Installation Guide Book there included. So I ask what steps to follow for a correct and complete (with XFree and KDE) installation of Linux 3 WS Ent. Edition. hoping for instructions, thanks in advance for the help and kind regards, Enrico Toniolo From jwelsh at digitalspy.co.uk Fri Feb 11 20:16:17 2005 From: jwelsh at digitalspy.co.uk (James Welsh) Date: Fri, 11 Feb 2005 15:16:17 -0500 Subject: Tyan/Broadcom issues? Message-ID: <20050211201616.EB73E5488D@buxton.digitalspy.co.uk> Hi everyone, We're considering moving to FC3 from FreeBSD 5.3, for two of our Opteron-based servers. The reason we're moving, incidentally, is because of an apparent incompatibility between FreeBSD 5.3 and our motherboard (Tyan S2882 Thunder K86) and its Broadcom integrated NICs with >4GB RAM. I've been reading this list and have noticed the Tyan name being brought up quite often and so I was wondering whether anyone can definitively say whether FC3 x86_64 is stable with a system of specs similar to these: Motherboard: Tyan S2882 Thunder K86 with U320 SCSI CPUs: AMD Opteron 248 2.2 GHz, 1MB cache x2 Memory: 8GB SCSI: Adaptec AIC-7902W dual channel RAID: LSI MegaRAID SCSI 320-1 64-bit Network Adapters: 2x Broadcom BCM5704C 1000Mbit integrated, 1x Intel PRO/100 integrated Any help/advice very gratefully received. Basically I want to ensure that we're not going to get a nasty surprise with the motherboard/NICs like we had with freebsd. Many thanks, James Welsh From mark at harddata.com Fri Feb 11 20:58:39 2005 From: mark at harddata.com (Mark Lane) Date: Fri, 11 Feb 2005 13:58:39 -0700 Subject: Tyan/Broadcom issues? In-Reply-To: <20050211201616.EB73E5488D@buxton.digitalspy.co.uk> References: <20050211201616.EB73E5488D@buxton.digitalspy.co.uk> Message-ID: <200502111358.39513.mark@harddata.com> On February 11, 2005 01:16 pm, "James Welsh" wrote: > Hi everyone, > > We're considering moving to FC3 from FreeBSD 5.3, for two of our > Opteron-based servers. The reason we're moving, incidentally, is because > of an apparent incompatibility between FreeBSD 5.3 and our motherboard > (Tyan S2882 Thunder K86) and its Broadcom integrated NICs with >4GB RAM. > I've been reading this list and have noticed the Tyan name being brought up > quite often and so I was wondering whether anyone can definitively say > whether FC3 x86_64 is stable with a system of specs similar to these: > > Motherboard: Tyan S2882 Thunder K86 with U320 SCSI > CPUs: AMD Opteron 248 2.2 GHz, 1MB cache x2 > Memory: 8GB > SCSI: Adaptec AIC-7902W dual channel > RAID: LSI MegaRAID SCSI 320-1 64-bit > Network Adapters: 2x Broadcom BCM5704C 1000Mbit integrated, 1x Intel > PRO/100 integrated Yes it is definitely stable. We have customers running FC2 and FC3 on the Tyan S2882 in production environments. FC3 currently provides very good support for x86_64. -- Mark Lane, CET -- mailto:mark at harddata.com Sales Manager -- Hard Data Ltd -- http://www.harddata.com T: 01-780-456-9771 -- F: 01-780-456-9772 11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3 --> Ask me about our New Dual and 4 Way Blade Servers <-- From jlabadie at acm.org Sun Feb 13 07:12:15 2005 From: jlabadie at acm.org (Jon LaBadie) Date: Sun, 13 Feb 2005 02:12:15 -0500 Subject: install of 32bit libs conflict with 64bit versions Message-ID: On RHEL 3, x86_64 I've been trying to install some needed 32bit libs. Most have installed without trouble, but a few report conflicts with pathnames in the already installed 64bit versions. As an example, the glib-1.2 rpm installs /usr/bin/glib-config and a header file, each with the same pathname, but different contents between the two packages. How should one handle this type of situation? I'm not looking for specifics about this particular library, though that would be appreciated, but general guidelines. From arjanv at redhat.com Sun Feb 13 13:18:30 2005 From: arjanv at redhat.com (Arjan van de Ven) Date: Sun, 13 Feb 2005 08:18:30 -0500 Subject: install of 32bit libs conflict with 64bit versions In-Reply-To: References: Message-ID: <1108300710.4050.101.camel@localhost.localdomain> On Sun, 2005-02-13 at 02:12 -0500, Jon LaBadie wrote: > On RHEL 3, x86_64 I've been trying to install some needed 32bit libs. > Most have installed without trouble, but a few report conflicts with > pathnames in the already installed 64bit versions. As an example, > the glib-1.2 rpm installs /usr/bin/glib-config and a header file, > each with the same pathname, but different contents between the > two packages. > > How should one handle this type of situation? > > I'm not looking for specifics about this particular library, > though that would be appreciated, but general guidelines. if you have a recent enough RHEL3 you're supposed to get a whole slew of 32 bit packages that just work... afaik glib is part of that. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From cartman_step1 at spymac.com Sun Feb 13 14:38:40 2005 From: cartman_step1 at spymac.com (cartman_step1 at spymac.com) Date: Sun, 13 Feb 2005 07:38:40 -0700 Subject: k3b don't burn data dvd Message-ID: <20050213143846.B12F05C0050@webmail3.spymac.net> Just a problem with k3b on my FC2-x86_64 My hardware is TSST CD/DVD ts-h552b Trying to burning data dvd I have this error : System ----------------------- K3b Version:0.11.14 KDE Version: 3.2.2-12.FC2 Red Hat QT Version: 3.3.3 growisofs ----------------------- Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Error trying to open /dev/hdc exclusively ... retrying in 1 second. Trying to open without locking. WARNING: /dev/hdc already carries isofs! About to execute 'builtin_dd if=/tmp/kde-andrea/K3b data project.iso of=/dev/hdc obs=32k seek=0' :-( Failed to change write speed: 2770->3324 Any idea? From jch at scalix.com Sun Feb 13 20:17:43 2005 From: jch at scalix.com (John Haxby) Date: Sun, 13 Feb 2005 20:17:43 +0000 Subject: k3b don't burn data dvd In-Reply-To: <20050213143846.B12F05C0050@webmail3.spymac.net> References: <20050213143846.B12F05C0050@webmail3.spymac.net> Message-ID: <420FB5E7.1000100@scalix.com> cartman_step1 at spymac.com wrote: >Just a problem with k3b on my FC2-x86_64 > >[snip] growisofs >----------------------- >Error trying to open /dev/hdc exclusively ... retrying in 1 second. >[snip] > >Error trying to open /dev/hdc exclusively ... retrying in 1 second. >Trying to open without locking. >WARNING: /dev/hdc already carries isofs! >About to execute 'builtin_dd if=/tmp/kde-andrea/K3b data project.iso of=/dev/hdc >obs=32k seek=0' >:-( Failed to change write speed: 2770->3324 > > The DVD is almost certainly mounted. Try "umount /mnt/cdrom" (or whatever it's mounted as -- run "mount" with no options to check if you're unsure) before you try to burn the DVD. Been caught by this myself. jch From cartman_step1 at spymac.com Sun Feb 13 22:43:44 2005 From: cartman_step1 at spymac.com (cartman_step1 at spymac.com) Date: Sun, 13 Feb 2005 15:43:44 -0700 Subject: Fwd: Re: k3b don't burn data dvd Message-ID: <20050213224348.2C1B05C0054@webmail3.spymac.net> ----- Original Message ----- From: John Haxby To: amd64-list at redhat.com Sent: Sun Feb 13 13:17 Subject: Fwd: Re: k3b don't burn data dvd cartman_step1 at spymac.com wrote: >Just a problem with k3b on my FC2-x86_64 > >[snip] growisofs >----------------------- >Error trying to open /dev/hdc exclusively ... retrying in 1 second. >[snip] > >Error trying to open /dev/hdc exclusively ... retrying in 1 second. >Trying to open without locking. >WARNING: /dev/hdc already carries isofs! >About to execute 'builtin_dd if=/tmp/kde-andrea/K3b data project.iso of=/dev/hdc >obs=32k seek=0' >:-( Failed to change write speed: 2770->3324 > > The DVD is almost certainly mounted. Try "umount /mnt/cdrom" (or whatever it's mounted as -- run "mount" with no options to check if you're unsure) before you try to burn the DVD. Been caught by this myself. jch -- amd64-list mailing list amd64-list at redhat.com https://www.redhat.com/mailman/listinfo/amd64-list Sorry for inconvenience ;-) Well thanks for your help . Now there is half problem about that . Solved the nautilus auto mounter here's the second . I show the k3b debug message : System ----------------------- K3b Version:0.11.14 KDE Version: 3.2.2-12.FC2 Red Hat QT Version: 3.3.3 growisofs ----------------------- WARNING: /dev/hdc already carries isofs! About to execute 'builtin_dd if=/tmp/kde-andrea/K3b data project.iso of=/dev/hdc obs=32k seek=0' :-( Failed to change write speed: 2770->3324 growisofs comand: ----------------------- /usr/bin/growisofs -Z /dev/hdc=/tmp/kde-andrea/K3b data project.iso -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=dao -dvd-compat -speed=2 Any other idea? From jlabadie at acm.org Sun Feb 13 23:53:48 2005 From: jlabadie at acm.org (Jon LaBadie) Date: Sun, 13 Feb 2005 18:53:48 -0500 Subject: install of 32bit libs conflict with 64bit versions -- summary and further question In-Reply-To: References: Message-ID: Jon LaBadie wrote: > On RHEL 3, x86_64 I've been trying to install some needed 32bit libs. > Most have installed without trouble, but a few report conflicts with > pathnames in the already installed 64bit versions. As an example, > the glib-1.2 rpm installs /usr/bin/glib-config and a header file, > each with the same pathname, but different contents between the > two packages. > > How should one handle this type of situation? > > I'm not looking for specifics about this particular library, > though that would be appreciated, but general guidelines. > Someone pointed out to me in private email that /usr/bin/glib-config is part of the glib-devel rpm, not the glib rpm. That showed me the error of my ways ;) When I looked at the installed packages I noted the x86_64 version of the glib-devel package was installed but overlooked the glib package which was also installed. It was actually the 32 bit version of glib I wanted but was trying to install glib-devel. Download the right package and it installs fine. That raises a hypothetical question though, suppose I did want to do both 64 and 32 bit development on the same system, would I not need both glib-devel rpms? And as I found out, there are conflicts between the x86_64 and i386 glib-devel rpm's. How is this handled? From kevins at solium.com Mon Feb 14 18:44:48 2005 From: kevins at solium.com (Kevin Stussman) Date: Mon, 14 Feb 2005 11:44:48 -0700 Subject: Got IBM eServer 326 w/ DS400? Message-ID: <1108406688.21574.1.camel@localhost.localdomain> We're getting a load of new equipment here in the next few weeks which Ido not have any direct experience loading/running with RHEL. I was hoping that there might be a few kind souls out there who might want to share their joys/pain on getting RHEL 3/4(beta) onto this server and setting up the HBA/SAN. Specifically: - Useful apps for the HBA/SAN configuration. - SNMP agents for monitoring the HW - Gotchas or general experiences. Slam dunk versus hours of driver hunting? System freezes, known problems, etc.. - Useful mailing lists / resources. I've been to the IBM/QLogic web site and found the usual suspects (i.e. source for the drivers, firmware updates, etc) but thought others might have some experience tips they could share. Regards, Kevin. eServer326 Dual Opteron DS400 Storage IBM Fiber Channel Card (24P0960 - QLogic I believe) From ben at muppethouse.com Mon Feb 14 19:29:48 2005 From: ben at muppethouse.com (Ben Russo) Date: Mon, 14 Feb 2005 14:29:48 -0500 Subject: Big filesystems... Message-ID: Have a big ass disk array with 3 1.6TB LUN's on it. I want to bind them together using LVM and then have one filesystem that is about 4.8TB in size. With a 2.6 kernel compiled for AMD64 is this possible? -Ben. From mark at harddata.com Mon Feb 14 19:51:11 2005 From: mark at harddata.com (Mark Lane) Date: Mon, 14 Feb 2005 12:51:11 -0700 Subject: Big filesystems... In-Reply-To: References: Message-ID: <200502141251.11214.mark@harddata.com> On February 14, 2005 12:29 pm, Ben Russo wrote: > Have a big ass disk array with 3 1.6TB LUN's on it. > I want to bind them together using LVM and then have one > filesystem that is about 4.8TB in size. > > With a 2.6 kernel compiled for AMD64 is this possible? > Yes -- Mark Lane, CET -- mailto:mark at harddata.com Sales Manager -- Hard Data Ltd -- http://www.harddata.com T: 01-780-456-9771 -- F: 01-780-456-9772 11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3 --> Ask me about our New Dual and 4 Way Blade Servers <-- From cartman_step1 at spymac.com Tue Feb 15 13:15:04 2005 From: cartman_step1 at spymac.com (cartman_step1 at spymac.com) Date: Tue, 15 Feb 2005 06:15:04 -0700 Subject: k3b don't burn data dvd Message-ID: <20050215131547.AEEFB4C04B@webmail2.spymac.net> On Mon Feb 14 2:26 , John Haxby sent: > >growisofs doesn't need to be told what speed to burn at: it will choose >the best for the media and drive. I don't use k3b so I don't know how >to tell it to let growisofs choose it's own speed -- is there a setting >for "auto" speed somewhere? Or somewhere that extra parameters are >specified on the command line? > >I think that letting growisofs choose the speed itself is the right >solution: I have some DVD+RW media that likes to be written at x2.4, I >unwittingly let a Windows application write at x2 and now I have a >DVD+RW coaster: I can't read, write or erase it. > >jch > >cartman_step1 at spymac.com wrote: > >>On Sun Feb 13 13:17 , John Haxby jch at scalix.com> sent: >> >> >> >>>cartman_step1 at spymac.com wrote: >>> >>> >>> >>>>Just a problem with k3b on my FC2-x86_64 >>>> >>>>[snip] growisofs >>>>----------------------- >>>>Error trying to open /dev/hdc exclusively ... retrying in 1 second. >>>>[snip] >>>> >>>>Error trying to open /dev/hdc exclusively ... retrying in 1 second. >>>>Trying to open without locking. >>>>WARNING: /dev/hdc already carries isofs! >>>>About to execute 'builtin_dd if=/tmp/kde-andrea/K3b data project.iso of=/dev/hdc >>>>obs=32k seek=0' >>>>:-( Failed to change write speed: 2770->3324 >>>> >>>> >>>> >>>> >>>The DVD is almost certainly mounted. Try "umount /mnt/cdrom" (or >>>whatever it's mounted as -- run "mount" with no options to check if >>>you're unsure) before you try to burn the DVD. >>> >>>Been caught by this myself. >>> >>>jch >>> >>>-- >>>amd64-list mailing list >>>amd64-list at redhat.com >>>https://www.redhat.com/mailman/listinfo/amd64-list >>> >>> >> >> >>Thanks for your reply , half problem is solved . You have the reason about the >>mount problems . Nutilus automatically mount the device when i insert a cd or dvd >>. Now the second half of the problem , that i think mean an hardware problem? >> >>Here's the output : >> >>System >>----------------------- >>K3b Version:0.11.14 >>KDE Version: 3.2.2-12.FC2 Red Hat >>QT Version: 3.3.3 >> >>growisofs >>----------------------- >>WARNING: /dev/hdc already carries isofs! >>About to execute 'builtin_dd if=/tmp/kde-andrea/K3b data project.iso of=/dev/hdc >>obs=32k seek=0' >>:-( Failed to change write speed: 2770->3324 >> >>growisofs comand: >>----------------------- >>/usr/bin/growisofs -Z /dev/hdc=/tmp/kde-andrea/K3b data project.iso >>-use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=dao >>-dvd-compat -speed=2 >> >>Any other idea >> >> >> > Ok problem solved!Thanks for your help . I put a sing on "ignore speed" on k3b and now it work very well . The same by command line , withouth setting the speed . Thanks again! ;-) From awol at home.nl Wed Feb 16 21:35:33 2005 From: awol at home.nl (Alexander Volovics) Date: Wed, 16 Feb 2005 22:35:33 +0100 Subject: ethernet failure after update to kernel-2.6.10-1.766 Message-ID: <20050216213532.GA5526@home.nl> This afternoon I updated to kernel-2.6.10-1.766 on an AMD64 machine. MSI K8N Neo2 Platinum mobo using the Realtek RTL-8169 Gigabit Ethernet adapter. On rebooting networking did not come up and I got the kernel message kernel: r8169: eth1: PHY reset until linkup Did any of the other users with this mobo and ethernet adapter using 64bit FC3 get this same problem. Is there a fix or will I have to revert to using the previous kernel. Alexander From rchiodin at bellsouth.net Thu Feb 17 11:10:48 2005 From: rchiodin at bellsouth.net (Bob Chiodini) Date: Thu, 17 Feb 2005 06:10:48 -0500 Subject: ethernet failure after update to kernel-2.6.10-1.766 In-Reply-To: <20050216213532.GA5526@home.nl> References: <20050216213532.GA5526@home.nl> Message-ID: <1108638648.11516.10.camel@tweedy.ksc.nasa.gov> On Wed, 2005-02-16 at 22:35 +0100, Alexander Volovics wrote: > This afternoon I updated to kernel-2.6.10-1.766 on an AMD64 machine. > MSI K8N Neo2 Platinum mobo using the Realtek RTL-8169 Gigabit Ethernet > adapter. > > On rebooting networking did not come up and I got the kernel message > kernel: r8169: eth1: PHY reset until linkup > > Did any of the other users with this mobo and ethernet adapter > using 64bit FC3 get this same problem. > > Is there a fix or will I have to revert to using the previous kernel. > > Alexander > Alexander, I have the same MB, but usually use the forcedeth driver on eth0, but switched interfaces after seeing you post. I also got the same message as you, but I was able to manually bring up the interface. Same kernel. Bob... From awol at home.nl Thu Feb 17 12:37:09 2005 From: awol at home.nl (Alexander Volovics) Date: Thu, 17 Feb 2005 13:37:09 +0100 Subject: ethernet failure after update to kernel-2.6.10-1.766 In-Reply-To: <1108638648.11516.10.camel@tweedy.ksc.nasa.gov> References: <20050216213532.GA5526@home.nl> <1108638648.11516.10.camel@tweedy.ksc.nasa.gov> Message-ID: <20050217123709.GA6247@home.nl> On Thu, Feb 17, 2005 at 06:10:48AM -0500, Bob Chiodini wrote: > On Wed, 2005-02-16 at 22:35 +0100, Alexander Volovics wrote: > > This afternoon I updated to kernel-2.6.10-1.766 on an AMD64 machine. > > MSI K8N Neo2 Platinum mobo using the Realtek RTL-8169 Gigabit Ethernet > > adapter. > > On rebooting networking did not come up and I got the kernel message > > kernel: r8169: eth1: PHY reset until linkup > > Did any of the other users with this mobo and ethernet adapter > > using 64bit FC3 get this same problem. > > Is there a fix or will I have to revert to using the previous kernel. > I have the same MB, but usually use the forcedeth driver on eth0, but > switched interfaces after seeing you post. I also got the same message > as you, but I was able to manually bring up the interface. Same kernel. Well, I had a very messy 24 hours. At first I could also manually bring up the interface but not use it, no data was transmitted. Then after a restart X wouldn't startup. So I tried the previous kernel and got the same problem. I gave up then. This morning I booted with trepidation but lo and behold the problem appeared to have been 'cleared up' automagically. I would really like to know what happened. From googling I gather that this 'PHY reset' has been troubling previous kernels with Gigabit ethernet adapters. I don't even know what it (PHY) is. Thanks for the reply. Alexander From rchiodin at bellsouth.net Thu Feb 17 14:27:31 2005 From: rchiodin at bellsouth.net (Bob Chiodini) Date: Thu, 17 Feb 2005 09:27:31 -0500 Subject: ethernet failure after update to kernel-2.6.10-1.766 In-Reply-To: <20050217123709.GA6247@home.nl> References: <20050216213532.GA5526@home.nl> <1108638648.11516.10.camel@tweedy.ksc.nasa.gov> <20050217123709.GA6247@home.nl> Message-ID: <1108650451.11516.30.camel@tweedy.ksc.nasa.gov> On Thu, 2005-02-17 at 13:37 +0100, Alexander Volovics wrote: > On Thu, Feb 17, 2005 at 06:10:48AM -0500, Bob Chiodini wrote: > > > On Wed, 2005-02-16 at 22:35 +0100, Alexander Volovics wrote: > > > This afternoon I updated to kernel-2.6.10-1.766 on an AMD64 machine. > > > MSI K8N Neo2 Platinum mobo using the Realtek RTL-8169 Gigabit Ethernet > > > adapter. > > > On rebooting networking did not come up and I got the kernel message > > > kernel: r8169: eth1: PHY reset until linkup > > > Did any of the other users with this mobo and ethernet adapter > > > using 64bit FC3 get this same problem. > > > Is there a fix or will I have to revert to using the previous kernel. > > > I have the same MB, but usually use the forcedeth driver on eth0, but > > switched interfaces after seeing you post. I also got the same message > > as you, but I was able to manually bring up the interface. Same kernel. > > Well, I had a very messy 24 hours. At first I could also manually bring > up the interface but not use it, no data was transmitted. Then after a > restart X wouldn't startup. > So I tried the previous kernel and got the same problem. I gave up then. > > This morning I booted with trepidation but lo and behold the problem > appeared to have been 'cleared up' automagically. > > I would really like to know what happened. From googling I gather > that this 'PHY reset' has been troubling previous kernels with Gigabit > ethernet adapters. I don't even know what it (PHY) is. > > Thanks for the reply. > > Alexander > Automagic, a great thing. The PHY usually means the physical components that connect to the wire or fiber or radio. I don't know whether the "PHY reset until linkup" message is an error or just info indicating that the physical interface will remain in a reset mode until a link is established. Bob... From cochranb at speakeasy.net Fri Feb 18 00:56:33 2005 From: cochranb at speakeasy.net (Robert L Cochran) Date: Thu, 17 Feb 2005 19:56:33 -0500 Subject: ethernet failure after update to kernel-2.6.10-1.766 In-Reply-To: <20050216213532.GA5526@home.nl> References: <20050216213532.GA5526@home.nl> Message-ID: <42153D41.1040704@speakeasy.net> Alexander Volovics wrote: >This afternoon I updated to kernel-2.6.10-1.766 on an AMD64 machine. >MSI K8N Neo2 Platinum mobo using the Realtek RTL-8169 Gigabit Ethernet >adapter. > >On rebooting networking did not come up and I got the kernel message > kernel: r8169: eth1: PHY reset until linkup > >Did any of the other users with this mobo and ethernet adapter >using 64bit FC3 get this same problem. > >Is there a fix or will I have to revert to using the previous kernel. > >Alexander > > > I'm surprised you have this problem. You must have made changes to your networking configuration -- even a seemingly tiny change can have big effects. I have the same motherboard -- I've forgotten the version number, I think it's a version 1 board. These are the messages that the 766 kernel gives me: Feb 17 18:03:13 bobcp4 ifup: Determining IP information for eth1... Feb 17 18:03:14 bobcp4 dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Feb 17 18:03:21 bobcp4 kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.30. Feb 17 18:03:21 bobcp4 kernel: eth0: forcedeth.c: subsystem: 01462:0250 bound to 0000:00:05.0 Feb 17 18:03:21 bobcp4 kernel: eth1: RTL8169 at 0xffffff000001e000, 00:11:09:61:11:6b, IRQ 201 Feb 17 18:03:22 bobcp4 kernel: r8169: eth1: link up Feb 17 18:03:20 bobcp4 ntpd[4662]: Listening on interface eth1, 192.168.1.14#123 When Fedora Core 3 first came out, I had no success getting the forcedeth driver to actually work on eth0 -- I simply gave up on it, which was easy since eth1 (the RTL8169) works just fine. I have not tried to get eth0 to work in recent times. Maybe the kernel has a revision to the forcedeth driver that gets it to work? Other than that -- I have no problems with the onboard LAN. Bob Cochran From awol at home.nl Fri Feb 18 22:38:57 2005 From: awol at home.nl (Alexander Volovics) Date: Fri, 18 Feb 2005 23:38:57 +0100 Subject: phy reset again Message-ID: <20050218223857.GA5647@home.nl> If From rchiodin at bellsouth.net Sat Feb 19 19:16:48 2005 From: rchiodin at bellsouth.net (Bob Chiodini) Date: Sat, 19 Feb 2005 14:16:48 -0500 Subject: VMWARE on AMD 64 Message-ID: <1108840608.7430.8.camel@littlenail.homelinux.net> yum info kernel: Name : kernel Arch : x86_64 Version: 2.6.10 Release: 1.766_FC3 Size : 52 M Repo : installed Summary: The Linux kernel (the core of the Linux operating system). After installing x86_64 version of kernel-2.6.10-1.766_FC3, I can no longer start vmware. I've rebuilt the modules and they load correctly, but no luck running the app. I've had no problems with the i686 version of the 766 kernel and also have no problem with x86_64 version of kernel-2.6.10-1.760_FC3. Any ideas? Bob... From angelus at sangreal.demon.nl Sat Feb 19 21:04:01 2005 From: angelus at sangreal.demon.nl (Angelo Machils) Date: Sat, 19 Feb 2005 22:04:01 +0100 Subject: FC3 x86-64 freezes on SATA?!?! Message-ID: <4217A9C1.1020009@sangreal.demon.nl> Hello there! Sometimes my box just 'freezes' on me, especially when I try some disk-intensive task (like rebuilding the database for slocate). It's probably a kernel panic (afterwards there are no entries in any log) and this also happens sometimes even at startup (most times at the 'checking for hardware' point). I get a message then about a kernel panic, not being able to sync and there is a mention about two SCSI modules who lock up (sorry, don't have the exact message, and here also there is nothing in the log, since it's a kernel panic). From searches on the internet I gather there must be some bad blocks on the disk, and smartctl could help, but since my SATA uses libata (the disk shows up as being a SCSI disk -- a /dev/sda) and this has no support in smartctl. What other util or solution could I try, because my box is even more unstable now then a win box at the moment. The entries in the websites show a little different error message, but the result is very similar. Very strange is that the only mention I find about such problems are always in a RAID environment, and I don't use RAID..... Hope this is enough information: [angelo at solaris]# lspci|grep IDE 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01) 00:05.0 IDE interface: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] (rev 01) [angelo at solaris]# smartctl -i /dev/sda smartctl version 5.33 [x86_64-redhat-linux-gnu] Copyright (C) 2002-4 Bruce AllenHome page is http://smartmontools.sourceforge.net/ Device: ATA Maxtor 6Y160M0 Version: YAR5 SATA disks accessed via libata are not currently supported by smartmontools. When libata is given an ATA pass-thru ioctl() then an additional '-d libata' device type will be added to smartmontools. Besides that, there is also a 'real' SCSI card in the system, 00:0c.0 SCSI storage controller: Adaptec AHA-7850 (rev 01) which uses the aic7xxx module. Could this be a problem, since most other 64 bits Linux's wouldn't even boot with this card in the system. This card has however, been in several other (AMD 32 bits) systems without problem (I put it in a AMD Athlon XP 2600+ system, with FC3, and no problems what-so-ever). My /var/log/messages says: Feb 8 13:26:48 localhost kernel: scsi: unknown opcode 0xbd Feb 8 18:32:37 localhost kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 Feb 8 18:32:37 localhost kernel: (scsi0:A:3): 10.000MB/s transfers (10.000MHz, offset 15) Feb 8 18:32:37 localhost kernel: (scsi0:A:4): 10.000MB/s transfers (10.000MHz, offset 15) Feb 8 18:32:37 localhost kernel: scsi1 : sata_sis Feb 8 18:32:37 localhost kernel: scsi2 : sata_sis Feb 8 18:32:37 localhost kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0 Feb 8 18:32:38 localhost kernel: Attached scsi tape st0 at scsi0, channel 0, id 3, lun 0 Feb 8 18:32:38 localhost kernel: Attached scsi tape st1 at scsi0, channel 0, id 4, lun 0 Feb 8 18:32:30 localhost kernel: Bootdata ok (command line is ro root=LABEL=/) Feb 8 18:32:30 localhost kernel: BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data) Feb 8 18:32:31 localhost kernel: Memory: 1024740k/1048512k available (2362k kernel code, 23008k reserved, 1268k data, 176k init) Feb 8 18:32:32 localhost smartd[5375]: Device /dev/sda, SATA disks accessed via libata are not currently supported by smartmontools. When libata is given an ATA pass-thru ioctl() then an additional '-d libata' device type will be added to smartmontools. Feb 8 18:32:33 localhost kernel: ksign: Installing public key data Feb 8 18:32:37 localhost kernel: ata1: SATA max UDMA/133 cmd 0xE200 ctl 0xE302 bmdma 0xE600 irq 177 Feb 8 18:32:37 localhost kernel: ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE502 bmdma 0xE608 irq 177 Feb 8 18:32:37 localhost kernel: ata1: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48 Feb 8 18:32:37 localhost kernel: ata1: dev 0 configured for UDMA/133 Feb 8 18:32:37 localhost kernel: scsi1 : sata_sis Feb 8 18:32:37 localhost kernel: ata2: no device found (phy stat 00000000) Feb 8 18:32:37 localhost kernel: scsi2 : sata_sis Feb 8 18:32:38 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode. Feb 8 18:32:38 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode. Feb 8 18:32:38 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode. There is a DVD player on the IDE bus Thanks for any help/assistance/help, because it is getting to be a real pain..... Angelo From maurice at harddata.com Sat Feb 19 21:13:28 2005 From: maurice at harddata.com (Maurice Hilarius) Date: Sat, 19 Feb 2005 14:13:28 -0700 Subject: FC3 x86-64 freezes on SATA?!?! In-Reply-To: <4217A9C1.1020009@sangreal.demon.nl> References: <4217A9C1.1020009@sangreal.demon.nl> Message-ID: <4217ABF8.7090909@harddata.com> Angelo Machils wrote: > Hello there! > > Sometimes my box just 'freezes' on me, especially when I try some > disk-intensive task (like rebuilding the database for slocate). It's > probably a kernel panic (afterwards there are no entries in any log) > and this also happens sometimes even at startup (most times at the > 'checking for hardware' point). First check for memory problems. Memtest86 is a good tool for that. Google for it. With our best regards, Maurice W. Hilarius Telephone: 01-780-456-9771 Hard Data Ltd. FAX: 01-780-456-9772 11060 - 166 Avenue email:maurice at harddata.com Edmonton, AB, Canada http://www.harddata.com/ T5X 1Y3 This email, message, and content, should be considered confidential, and is the copyrighted property of Hard Data Ltd., unless stated otherwise. From rchiodin at bellsouth.net Sat Feb 19 22:52:01 2005 From: rchiodin at bellsouth.net (Bob Chiodini) Date: Sat, 19 Feb 2005 17:52:01 -0500 Subject: VMWARE on AMD 64 In-Reply-To: <1108848202.7430.10.camel@littlenail.homelinux.net> References: <20050219204414.DE23073440@hormel.redhat.com> <4217A856.3020800@sangreal.demon.nl> <1108848202.7430.10.camel@littlenail.homelinux.net> Message-ID: <4217C311.5030402@bellsouth.net> Bob Chiodini wrote: >On Sat, 2005-02-19 at 21:57 +0100, Angelo Machils wrote: > > >>>yum info kernel: >>> >>>Name : kernel >>>Arch : x86_64 >>>Version: 2.6.10 >>>Release: 1.766_FC3 >>>Size : 52 M >>>Repo : installed >>>Summary: The Linux kernel (the core of the Linux operating system). >>> >>> >>>After installing x86_64 version of kernel-2.6.10-1.766_FC3, I can no >>>longer start vmware. I've rebuilt the modules and they load correctly, >>>but no luck running the app. I've had no problems with the i686 version >>>of the 766 kernel and also have no problem with x86_64 version of >>>kernel-2.6.10-1.760_FC3. >>> >>>Any ideas? >>> >>>Bob... >>> >>> >>> >>Hi there! >> >>What version of VMWare are you running? I have been running VMWare 5 >>beta, RC1 and RC2 since they came out on my AMD-64 (different kernel >>versions, also the 2.6.10-1.766_FC3 x86-64) without any major problems. >>I assume you did the vmware-config.pl as root?? >> >>Angelo >> >> >> > >Angelo, > >I am running version 4.5 build 8848. Yes I reran vmware-config.pl as >root, no errors. > >Am searching for their beta now. > >Bob... > > > Version 5 beta works with both the 760 and 766 kernel. Thanks for the tip. Bob... From angelus at sangreal.demon.nl Sun Feb 20 09:01:22 2005 From: angelus at sangreal.demon.nl (Angelo Machils) Date: Sun, 20 Feb 2005 10:01:22 +0100 Subject: FC3 x86-64 freezes on SATA?!?! In-Reply-To: <4217ABF8.7090909@harddata.com> References: <4217A9C1.1020009@sangreal.demon.nl> <4217ABF8.7090909@harddata.com> Message-ID: <421851E2.7000306@sangreal.demon.nl> Maurice Hilarius wrote: > Angelo Machils wrote: > >> Hello there! >> >> Sometimes my box just 'freezes' on me, especially when I try some >> disk-intensive task (like rebuilding the database for slocate). It's >> probably a kernel panic (afterwards there are no entries in any log) >> and this also happens sometimes even at startup (most times at the >> 'checking for hardware' point). > > > First check for memory problems. > Memtest86 is a good tool for that. > Google for it. Thank you for the tip, but there is nothing wrong with the memory, I let Memtest86+ v1.20 run for about 10 hours and there were no errors. Only strange thing is that the programs thinks there is single channel DDR400 memory in the box, while there should be dual channel. I have took out the SCSI card, which had no effect. When the machine freezes and I do a hard reset of the system I get an message of course that the system has shutdown uncleanly and if fsck should check the filesystems. If I choose yes, there will be a kernel panic during that check (about not syncing, it seems there are two scsi modules trying to get access while it's locked, sorry don't know the exact errormessage and since it's a kernel panic there is no logging), I reset again, do the test again, sometimes there is a 2nd kernel panic or it goes through the check without errors. The third time is always okay. After this the system runs for a little while without problems. It seems that it gets 'thrashed' somehow after a while. I had the drive also checked with the shop where I bought it, and they couldn't find anything wrong. I even had win xp 64 RC1 running on the system for a short while without problems (but perhaps that time was too short). Perhaps FC doesn't like the combination of SATA controler and drive?? Thanks, Angelo From mk at crc.dk Sun Feb 20 11:04:53 2005 From: mk at crc.dk (Mogens Kjaer) Date: Sun, 20 Feb 2005 12:04:53 +0100 Subject: FC3 x86-64 freezes on SATA?!?! In-Reply-To: <42186DD4.3070304@crc.dk> References: <4217A9C1.1020009@sangreal.demon.nl> <4217ABF8.7090909@harddata.com> <421851E2.7000306@sangreal.demon.nl> <42186DD4.3070304@crc.dk> Message-ID: <42186ED5.6060407@crc.dk> Mogens Kjaer wrote: > Angelo Machils wrote: > ... > >> >> Thank you for the tip, but there is nothing wrong with the memory, I >> let Memtest86+ v1.20 run for about 10 hours and there were no errors. > > > In some cases, 10 hours is not enough to show a memory error. Sorry, that should have gone to the list. Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk at crc.dk Homepage: http://www.crc.dk From maurice at harddata.com Sun Feb 20 17:23:43 2005 From: maurice at harddata.com (Maurice Hilarius) Date: Sun, 20 Feb 2005 10:23:43 -0700 Subject: FC3 x86-64 freezes on SATA?!?! In-Reply-To: <421851E2.7000306@sangreal.demon.nl> References: <4217A9C1.1020009@sangreal.demon.nl> <4217ABF8.7090909@harddata.com> <421851E2.7000306@sangreal.demon.nl> Message-ID: <4218C79F.2070003@harddata.com> Angelo Machils wrote: > Thank you for the tip, but there is nothing wrong with the memory, I > let Memtest86+ v1.20 run for about 10 hours and there were no errors. > Only strange thing is that the programs thinks there is single channel > DDR400 memory in the box, while there should be dual channel. > I have took out the SCSI card, which had no effect. > ... > Perhaps FC doesn't like the combination of SATA controler and drive?? OK, some more detail, what power supply, board and CPU do you have? As another posted memtest might take longer to find an error, but chances are that is not it. My next thoughts on likelihood are motherboard or power.. We have installed a lot of machines with FC3, SATA, etc.. With our best regards, Maurice W. Hilarius Telephone: 01-780-456-9771 Hard Data Ltd. FAX: 01-780-456-9772 11060 - 166 Avenue email:maurice at harddata.com Edmonton, AB, Canada http://www.harddata.com/ T5X 1Y3 From dstewart at atl.lmco.com Fri Feb 25 17:12:24 2005 From: dstewart at atl.lmco.com (Doug Stewart) Date: Fri, 25 Feb 2005 12:12:24 -0500 Subject: Update BIOS on Gigabyte K8NS Ultra-939? Message-ID: <421F5C78.2000201@atl.lmco.com> Howdy all: Has anyone been able to successfully update the BIOS on a GB K8NS Ultra-939? It seems to require either 1) an install of Win32 or 2) a regular floppy drive, neither of which I am "blessed" with. I've tried creating a boot cd using old Dos 6.22 images from bootdisk.com, but this doesn't work - the .exe whines about it not being a Win32 environment. While the mobo seems to support USB floppy drives as valid boot devices, the in-BIOS flash utility can't seem to see them. Any ideas? Gigabyte's website is of absolutely no help. -- ---------- Doug Stewart Systems Administrator/Web Applications Developer Lockheed Martin Advanced Technology Labs dstewart at atl.lmco.com From dstewart at atl.lmco.com Fri Feb 25 19:28:54 2005 From: dstewart at atl.lmco.com (Doug Stewart) Date: Fri, 25 Feb 2005 14:28:54 -0500 Subject: Update BIOS on Gigabyte K8NS Ultra-939? In-Reply-To: <421F79F2.2000900@dragondeveloper.com> References: <421F5C78.2000201@atl.lmco.com> <421F79F2.2000900@dragondeveloper.com> Message-ID: <421F7C76.5070107@atl.lmco.com> Dennis Shaw wrote: > You can buy a regular floppy drive for like $4. That would be the least > aggravating road to travel. That would be folding up, giving up and giving in to The Man! *chuckle* Blasted vendors and their Windows biases... -- ---------- Doug Stewart Systems Administrator/Web Applications Developer Lockheed Martin Advanced Technology Labs dstewart at atl.lmco.com From b.j.smith at ieee.org Fri Feb 25 19:33:41 2005 From: b.j.smith at ieee.org (Bryan J. Smith) Date: Fri, 25 Feb 2005 11:33:41 -0800 Subject: Update BIOS on Gigabyte K8NS Ultra-939? Message-ID: <2.1-17526347-397-A-OEWW@smtpauth.earthlink.net> Doug Stewart wrote: > That would be folding up, giving up and giving in to The Man! > *chuckle* > Blasted vendors and their Windows biases... Actually, the floppy option is nice. If they ever offer a load via El'Torito, that will take care of CDs too. Most (real-hardware) RAID storage vendors now offer a Linux-based firmware load. I suspect the BIOS vendors won't be far behind. -- Bryan J. Smith mailto:b.j.smith at ieee.org Currently Mobile From b.j.smith at ieee.org Fri Feb 25 23:13:52 2005 From: b.j.smith at ieee.org (Bryan J. Smith) Date: Fri, 25 Feb 2005 15:13:52 -0800 Subject: Update BIOS on Gigabyte K8NS Ultra-939? Message-ID: <2.1-17678974-393-A-OEWW@smtpauth.earthlink.net> Mark Reis wrote: > A 3rd option is just to make a bootable CD image out of the BIOS flash > floppy. This works quiet well every time I've used it on systems w/o a > floppy drive. And the BIOS knows to go to the CD? Or are you thinking of a bootable floppy? That's 100 percent *different*. We're talking about BIOSes that load the update directly from the floppy, the floppy itself does not boot. > > -Mark > > Bryan J. Smith wrote: > >> Actually, the floppy option is nice. >> If they ever offer a load via El'Torito, that will take care of CDs too. >> >> Most (real-hardware) RAID storage vendors now offer a Linux-based >> firmware load. >> I suspect the BIOS vendors won't be far behind. > -- Bryan J. Smith mailto:b.j.smith at ieee.org Currently Mobile From cochranb at speakeasy.net Sat Feb 26 00:09:29 2005 From: cochranb at speakeasy.net (Robert L Cochran) Date: Fri, 25 Feb 2005 19:09:29 -0500 Subject: Update BIOS on Gigabyte K8NS Ultra-939? In-Reply-To: <421F5C78.2000201@atl.lmco.com> References: <421F5C78.2000201@atl.lmco.com> Message-ID: <421FBE39.8000906@speakeasy.net> I always do install a floppy drive specifically to flash BIOS updates. They are cheap these days. Buy one used. Bob Cochran Greenbelt, MD Doug Stewart wrote: > Howdy all: > Has anyone been able to successfully update the BIOS on a GB K8NS > Ultra-939? It seems to require either 1) an install of Win32 or 2) a > regular floppy drive, neither of which I am "blessed" with. > > I've tried creating a boot cd using old Dos 6.22 images from > bootdisk.com, but this doesn't work - the .exe whines about it not > being a Win32 environment. While the mobo seems to support USB floppy > drives as valid boot devices, the in-BIOS flash utility can't seem to > see them. > > Any ideas? Gigabyte's website is of absolutely no help. From dstewart at atl.lmco.com Sat Feb 26 17:48:30 2005 From: dstewart at atl.lmco.com (Doug Stewart) Date: Sat, 26 Feb 2005 12:48:30 -0500 Subject: Update BIOS on Gigabyte K8NS Ultra-939? In-Reply-To: <421FBE39.8000906@speakeasy.net> References: <421F5C78.2000201@atl.lmco.com> <421FBE39.8000906@speakeasy.net> Message-ID: <4220B66E.2010900@atl.lmco.com> Many thanks to all who contributed advice. Here's the solution I worked out: I examined and extraced the actual BIOS ROM from Gigabyte's installer on another machine, pieced together a stripped-down Dos 6.22 boot disk with the flash program and ROM on it and managed to snag a USB floppy drive (the K8 NS-Ultra has the option of booting from a USB floppy, fortunately - lifesaver there). I've upgraded and all seems well. Thanks again for all the tips and advice. -- ---------- Doug Stewart Systems Administrator/Web Applications Developer Lockheed Martin Advanced Technology Labs dstewart at atl.lmco.com From ericm at sfour.no-ip.com Mon Feb 28 01:14:45 2005 From: ericm at sfour.no-ip.com (Eric Mittelstaedt) Date: Sun, 27 Feb 2005 20:14:45 -0500 Subject: Update BIOS on Gigabyte K8NS Ultra-939? In-Reply-To: <4220B66E.2010900@atl.lmco.com> References: <421F5C78.2000201@atl.lmco.com> <421FBE39.8000906@speakeasy.net> <4220B66E.2010900@atl.lmco.com> Message-ID: <42227085.5040600@sfour.no-ip.com> I realize you've already found a solution, but I thought I'd pass this on to ya (and the other folks on the list) - I've been using the "Ultimate bootdisk" (http://www.ultimatebootcd.com/) that contains quite a few utilities plus different types of DOS boots. Perfect CD to have around on floppy-less systems for diagnostics and BIOS flashing. Eric Doug Stewart wrote: > Many thanks to all who contributed advice. Here's the solution I > worked out: > > I examined and extraced the actual BIOS ROM from Gigabyte's installer > on another machine, pieced together a stripped-down Dos 6.22 boot disk > with the flash program and ROM on it and managed to snag a USB floppy > drive (the K8 NS-Ultra has the option of booting from a USB floppy, > fortunately - lifesaver there). I've upgraded and all seems well. > > Thanks again for all the tips and advice. > >