June 2004 - openSUSE AMD64 - openSUSE Mailing Lists

SuSE 9.0 Kernel 2.6.6
by einar 20 Jun '04

20 Jun '04

Hello, I fail to bring up my kernel. Using the common 2.6.6 source, I always get stuck at VFS: cannot open root device "sda3" or fd0 I can see how the VIA SATA controller is detected, the initrd is found and the drivers for scsi, sd_mod, libata and finally sata_via are loaded. Then it tries to mount root via NFS and I am asked to insert a root floppy. After pressing any key, I get the final message I already wrote. So, I thought maybe 2.6.6 does not see SATA as a SCSI anymore and so the name of the disks might have changed. I tried with different names in my grub bootloader (root=/dev/hda3 instead of root=/dev/sda3) but with no success. I am using reiserfs and I already compiled this into the kernel to avoid any possible problem with the initrd. Needless to say that the box works fine with the 2.4.21-215 from SuSE. Any ideas? tia, einar

3 5

Linux Newbie
by Tony 20 Jun '04

20 Jun '04

I just built a new rig with 2 10,000rpm SATA hard drives. I have them setup in RAID 0 in WinXP Pro. I am totally new to any linux, but I thought I would give SuSE a try since I like playing with new things and its 64bit compatible. Anyways, I have yet to install SuSE 9.1 cause when I start the installation one of the first messages goes something like this: This system has at least one hard disk w/ a RAID configuration sold by the BIOS as RAID that is in fact a software RAID. (then the last part of the message states) If you do an installation on these Disks your RAID configuration and any Data on the RAID will be lost! Now I was just wondering if this means it will erase WinXP and my other files off my drives? Should I just continue through the normal installation? I am completely new but would like to experience the whole linux world. I have AMD64 3200++ and SuSE Linux Pro 9.1. Please help me out. Thanks, tony. __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail

2 1

gFTP
by rkimber＠ntlworld.com 20 Jun '04

20 Jun '04

Does anyone have gFTP working? Mine segfaults when you try to do anything other than enter preferences. I have 9.1 dual opteron with gftp-2.0.16-33 and 2.6.4-54.5-smp, and the network connection seem to be fine for email and browsing. -- Richard Kimber http://www.psr.keele.ac.uk/

3 2

libiconv missing from suse.
by Joel Wiramu Pauling 20 Jun '04

20 Jun '04

What has happened to libiconv and the respective php modules from suse 9.1 amd64? I've just realised that it's not installed, nor available from any packages.... and need it for a web app i'm developing... Can someone enlighten me as to this? Kind regards Joel

1 1

Default sudo behaviour in suse
by Joel Wiramu Pauling 20 Jun '04

20 Jun '04

I noted this issue with all the previous version of suse,and this is not amd64 specific, yet I am hoping someone will address this. By default suse, seems to setup the sudo command to allow access using only the root password (i.e even if a user is listed in /etc/sudoers, when running sudo <command> they will be prompted NOT for there own password (sensible default behaviour of sudo) but for the ROOT password). This is a major concern, as all suse distro's I have used have this as the default behaviour. This is a really really stupid thing to do from a security and convenience standpoint. Can someone please fix this. Or at least give me some explanation as to why sudo is setup like this in suse, as it is a very ... pointless and stupid behaviour for a command that;s existence is to relegate the dissemination of the superuser password to the scrap heap. Kind regards Joel

1 0

Sun JDK 1.3.1_12 with SuSE 9.1 AMD64
by Thomas Peuss 19 Jun '04

19 Jun '04

Hello! Has someone got Sun JDK 1.3.1_12 running with SuSE Linux 9.1 AMD64? I am getting following error during compilation: error: compiler message file broken: key=compiler.err.sun.io.MalformedInputException arguments=null, null, null, null, null, null, null I had to patch $JAVA_HOME/bin/java to make java think that x86_64 is a i386 platform... BTW: Sun JDK 1.4.2_03 is running fine. CU Thomas

3 3

Re: [suse-amd64] SuSE 9.1 on MSI K8T Master-FAR SATA disk i/o problem
by Brock Witherspoon 19 Jun '04

19 Jun '04

Hi all, Well, I just thought I'd follow up. It did turn out that some of our memory was outright bad, while the rest of it was just causing minor instability. (Some of it did pass the whole battery of memtest86, though.) We will be returning all of the RAM for some less aggressively timed stuff. But there was also a SuSE problem as well when it came to the hard disk controllers. I now have Mandrake 10.0 Official for amd64 installed on all 4 machines, and everything went much more smoothly. I didn't have to disable ACPI in order for the installer boot sequence to freeze. I didn't get random freezes during the installation process. The drives were recognized as sd#, not hd#. The Linux software RAID arrays were partitioned and formatted without any problem (with the SuSE install, I always had to do it at least twice because of unspecified errors in formatting md3 or whatever). Most of all, I now have to work extremely hard in order to crash the systems, whereas with SuSE they sometimes wouldn't even make it through the boot process. Hopefully with the new RAM they won't crash at all. To answer a question in this thread -- on both SuSE and Mandrake, I was able to install completely to two RAIDed disks. The RAID partitions looked like this: md0 - / (swap, not raided) md1 - /tmp md2 - /usr md3 - /home md4 - /boot md5 - /var I didn't have any trouble whatsoever booting from the Linux software RAID. Just make sure to split off /boot. Yes /boot is part of a RAID array as well, but I guess things work as long as it's separate from /. However, the bootloader is installed on the MBR of only one disk, so if that disk fails then I'll have to boot from a CD or floppy and reinstall the bootloader. Well, so ends my foray into SuSE. I've used Mandrake for other machines in the past, and I'm really just more used to it. (The reason I tried SuSE was that Mandrake didn't have the 10.0 Official amd64 ISOs available for download from the Mandrakeclub despite their promises weeks before to do so. Well, finally they are available. I had tried RC1 and had several problems.) I like the urpmi package manager. It might not always work all the time, but at least when it doesn't work then I already know how to fix it, unlike with normal rpm where I was clueless. Of course I'd really prefer FreeBSD for these machines, but unfortunately SMP amd64 isn't quite good to go yet, as far as I'm concerned.... Well, I hope that this post doesn't start a series of flames. I'm just trying to be helpful by following up in case other people have the same problems in the future. SuSE just didn't end up working for me in my particular situation, and Mandrake did. Best to all, -Brock Witherspoon

1 0

RE: [ok] [suse-amd64] VMWare and kernel mis-match
by Creamer, Mark 18 Jun '04

18 Jun '04

Hmmm. You mean 4.5.2 Workstation version maybe? That one was just released on Friday. Maybe I'll try that...don't really need the extras that GSX would offer anyway. Boss will like cheaper price for sure... <mc> -----Original Message----- From: Curt Purdy [mailto:purdy@tecman.com] Sent: Friday, June 18, 2004 2:24 PM To: Creamer, Mark; suse-amd64(a)suse.com Subject: RE: [ok] [suse-amd64] VMWare and kernel mis-match Creamer, Mark wrote : <snip> > I run the script to configure VMWare, and see this: > > " Trying to find a suitable vmmon module for your running kernel. Also forgot to mention in my first post that you can forget about vmware on x86_64 for now. I've heard roomers that 4.5.2 will address it. Curt Purdy CISSP, GSEC, MCSE+I, CNE, CCDA Information Security Engineer DP Solutions ---------------------------------------- If you spend more on coffee than on IT security, you will be hacked. What's more, you deserve to be hacked. -- White House cybersecurity adviser Richard Clarke

1 0

RE: [suse-amd64] IOMMU
by richard.brunner＠amd.com 18 Jun '04

18 Jun '04

If I recall correctly, enabling IOMMU in the BIOS just makes the kernel's job easier in finding a hunk of MMIO space to place the Aperture. Providing you didn't disable IOMMU on the grub line, I believe Andi's code will still attempt to setup the Aperture and use it for IOMMU even if it is not getting hints from the BIOS. -Rich Brunner, AMD >-----Original Message----- >From: John Craig [mailto:johncraig01@netscape.net] >Sent: Friday, June 18, 2004 9:11 AM >To: suse-amd64(a)suse.com >Subject: [suse-amd64] IOMMU > >This may seem like a dumb question, but should I enable IOMMU in the >bios? This is a dual Opteron file server with a MSI K8D Master Mobo. I >just noticed that it was disabled by default, and that it is used by >Linux to translate 32-bit addresses to 64-bit addresses. > >Thanks, >John Craig > > > > >-- >Check the List-Unsubscribe header to unsubscribe >For additional commands, email: suse-amd64-help(a)suse.com > > >

2 1

RE: [ok] [suse-amd64] VMWare and kernel mis-match
by Creamer, Mark 18 Jun '04

18 Jun '04

Thanks Curt - that's pretty much what the other postings on this issue are saying, and I agree with you that it sure seems like that would be the answer. However, I haven't done any online updates, and both the running kernel and the kernel-source package were installed from the same shrinkwrap dvd. In Yast, both say 2.6.4. Any other ideas why it would think they aren't the same? <mc> -----Original Message----- From: Curt Purdy [mailto:purdy@tecman.com] Sent: Friday, June 18, 2004 10:37 AM To: Creamer, Mark; suse-amd64(a)suse.com Subject: RE: [ok] [suse-amd64] VMWare and kernel mis-match Creamer, Mark wrote : <snip> > I run the script to configure VMWare, and see this: > > " Trying to find a suitable vmmon module for your running kernel. It sounds like you have updated your kernel through Yaz and need to obtain the new source that matches your current kernel. It is available on SuSE FTP site. Curt

2 1