May 2004 - openSUSE AMD64 - openSUSE Mailing Lists

Update from 9.0 to 9.1
by Örn Hansen 20 May '04

20 May '04

I just wanted to tell my non-woes story about updating. I have MSI K8T Neo, and the update from 9.0 went like a charm. There were minor issues, with the installation program not regocnizing my Logitech cordless mouse but since the keyboard is also navigatable, I just went onward. Then there was another minor issue, with the /dev/hde vs. /dev/hda with the boot loader. Specifically, it said it didn't recognize /dev/hda as a disk. What I did, was simply remove /dev/hdb,/dev/hda from the list, and specify /dev/hde,/dev/hdf instead. This resulted in grub specifying (NULL) as the hard disk device, which could easily be edited after the boot into (hd0,1) in my case. The only thing the update program missed, was the "powersave" group which it did not add. I had to add it by hand, probably without the correct system ID, but that can wait. After having found the advice to turn off ACPI daemon, the powersave daemon started and everything is working like a charm, so far, including the sound card. Great job guys.

1 0

Suse9.1 Failed Install on SK8N
by Michael White 20 May '04

20 May '04

I just received Suse 9.1, and am having problems with the install. System: ASUS SK8N with AMD64FX-51 80 MB SATA Drive Anyway, the install seems to go OK, but fails when attempting to install the bootloader onto floppy. Specifically, it cannot seem to find /dev/fd0. There is nothing wrong with /dev/fd0, because I can access it flawlessly under Mandrake 9.2 for AMD64 (just checked it right now). What is the problem here? Also, who thought it was a good idea to reboot the system? Now I have to go through the entire install again, don't I? Second, I cannot find this "registration code" described in the "Support at SUSE" brochure. Do I get support with purchase of 9.1 Professional? If so, where is the "registration code"? Finally, the reason I'm installing the bootloader onto floppy rather than /boot is I don't want it to overwrite my current bootloader configuration set up by Mandrake. Is there a way to simply update the bootloader, even though I have to go with a "new install" because there's no existing Suse install on the partion that I'm going to install Suse on? Thanks in advance. -- Michael White "To protect people from the effects of folly is to fill the world with fools." -Herbert Spencer, 1891 P.S. If the floppy disk issue is not resolved, is there any reason I -shouldn't- return this package and stick with Mandrake 9.2?

2 1

sax2 crashes
by Claus Christian Larsen 20 May '04

20 May '04

Hello. If i run sax2 it crashes and i will have to make a "hard reboot". I have a option in my XFree86.conf: Section device ----"---- option "NvAgp" "1" ---"--- without it x will not run. I have just updates my bios. My morherboard is a soltek SL-K8AV2-R nvidia grafikcart The real problem is my logictech usb mouse. I have to set it up after every start of the computer. Can i edid the xfree86.conf manuel .- ehm, and what shall i write then? Regards Claus

2 1

Update kernel, destroy installation (lvm-related)
by Neal D. Becker 20 May '04

20 May '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After installing suse-9.1, I had a major problem. 1. Installed suse-9.1/x86_64 using LVM on MSI SATA stripe 2 disks. Everything seems OK. Used grub. 2. Built/installed apt 3. Use apt to update stuff, including "kernel-of-the-day" 4. Reboot. Does not detect any lvm. Does not appear to have loaded dm-mod. 5. Try to use suse-9.1/x86_64 dvd as rescue disk. Does not detect any linux installation. Sorry, I don't have a log of the exact messages. This seems to be a repeat of the same kinds of problems I've suffered when playing with Fedora test releases. It looks like lvm2 arrays are not detected properly after upgrading kernel sometimes. Other times I've updated the kernel OK. Not really sure what's going on. Any advice? - -- Please AVOID sending me WORD, EXCEL or POWERPOINT attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFArJhaMDqogpR5tkMRAnEcAJ4km6RyoUi9roOgH1k371A04Y3+xQCfSi6M L2GHpuOZU5Nm7dhSUhuNqs4= =zGAy -----END PGP SIGNATURE-----

2 2

Mozilla 64bit memory Leak
by Joel Wiramu Pauling 20 May '04

20 May '04

I was noticing high memory ussage after a couple of hours (I have 2gb so this was obviously a leak somewhere). Don't know if suse is aware of the problem but the mozilla 64bit binary (suse 9.1) is the cause.

1 0

mkinitrd patch - for recreating initrd after booting w/ rescue disc
by Jan 19 May '04

19 May '04

Hi, having gotten in a situation where yast2 had broken my initrd (related with a SATA driver & module symbol dependency problem), I have made some 'corrections' (imho) to the mkinitrd script to allow for recreation of the initrd image when a different root / is mounted - e.g. after booting in rescue mode from the suse install cd. The changes should only be corrections to what the authors had intended anyways (but maybe not tested in detail). Still I'm having a problem with regenerating my initrd, since the sata_via module dependencies are somehow not processed correctly even though ldd lists them ok from modules.dep. But that could also be a problem with modules.dep or my (out of the box but possibly damaged) linker set-up. Hope the patch is useful input. best regards, Jan ----- result of calling mkinitrd (with normal root) --- # mkinitrd Root device: /dev/hda2 (mounted on / as reiserfs) Module list: stata_via libata scsi_mod sd_mod sbp2 sg sr_mod r8169 nvram reiserfs Kernel image: /boot/vmlinuz-2.6.4-54.5-default Initrd image: /boot/initrd-2.6.4-54.5-default Shared libs: lib64/ld-2.3.3.so lib64/libc.so.6 Cannot determine dependencies of module stata_via. Is modules.dep up to date? Cannot determine dependencies of module nvram. Is modules.dep up to date? Modules: kernel/drivers/scsi/scsi_mod.ko kernel/drivers/scsi/libata.ko kernel/drivers/scsi/sd_mod.ko kernel/drivers/ieee1394/ieee1394.ko kernel/drivers/ieee1394/sbp2.ko kernel/drivers/scsi/sg.ko kernel/drivers/scsi/sr_mod.ko kernel/drivers/net/r8169.ko kernel/fs/reiserfs/reiserfs.ko Bootsplash: SuSE (1024x768) ===== patch against suse v9.1 with online update of 12.05.2004 mkinitrd rpm v1.0 release 199.17 ==== --- mkinitrd.orig 2004-05-20 08:50:20.661210008 +0200 +++ mkinitrd 2004-05-17 04:29:09.000000000 +0200 @@ -427,9 +427,9 @@ CHROOT=/usr/bin/chroot if [ ! -x $CHROOT ]; then error 2 "I need $CHROOT." else - $CHROOT "$@" + $CHROOT ${root_dir} "$@" fi else "$@" fi @@ -515,9 +515,9 @@ else modprobe=$root_dir/sbin/modprobe fi tmp_conf="$(mktemp $root_dir/tmp/mkinitrd.XXXXXX)" - { echo "depfile=/lib/modules/$kernel_version/modules.dep" + { echo "depfile=$root_dir/lib/modules/$kernel_version/modules.dep" [ -f $root_dir/etc/modules.conf ] \ && sed -e '/^[ \t]*depfile=/d' $root_dir/etc/modules.conf } > "$tmp_conf" module_list=$( do_chroot \

1 0

Problems with libtool an amd64
by Neal D. Becker 19 May '04

19 May '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is this a known problem? I'm trying to build apt-0.5.15cnc6 from srpm on suse9.1 amd64. make[1]: Entering directory `/home/nbecker/RPM/BUILD/apt-0.5.15cnc6/lua' libtool --mode=link gcc -O2 -g -o lua/lua lua/lua_lua-lua.o liblua.la -lz - -lbz2 gcc -O2 -g -o lua/lua lua/lua_lua-lua.o ./.libs/liblua.al -lm -ldl - -lz /usr/lib/libbz2.so ^[[0m/usr/lib/libbz2.so: could not read symbols: Invalid operation As you see, libtool... -lbz2 decided to usr /usr/lib/libbz2.so instead of /usr/lib64. There are both /usr/lib/libbz2.la and /usr/lib64/libbz2.la. I have traced the problem as far as /usr/bin/libtool reading /usr/lib/libbz2.la instead of /usr/lib64 version. Questions: 1) Is this a bug in libtool amd64? 2) Should I report it? 3) Does anyone have a patch? 4) I can't possibly be the first one to notice this, right? - -- Please AVOID sending me WORD, EXCEL or POWERPOINT attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD4DBQFAqz+dMDqogpR5tkMRAjzZAJwOuOpynljHlciOtltCWM74iP1eJgCXfSNl 7uc+mlBjpK8nsmXw0JiXgg== =WQPs -----END PGP SIGNATURE-----

5 7

Re: [suse-amd64] OpenGL games randomly crash computer
by Steve Wagoner 19 May '04

19 May '04

I ran the mprime Torture Test for 20 hours, 38 minutes with 0 errors and 0 warnings. I don't know that it would be a hardware issue, because as soon as either of these games is running they are rock solid and I can play for hours on end. The only time the crashed occur is when the games are first starting. I have an NVIDIA 5900TX with an MSI K8T Neo mother board... Any further thoughts would be greatly appreciated. ~Steve > Go download mprimes and stress test your hardware.... > > http://www.mersenne.org/prime.htm > > On Tue, 2004-05-18 at 19:10, Franz Mach wrote: >> --- Steve Wagoner <mars(a)marsonist.com> schrieb: > >> Whenever I try to run Unreal Tournament 2004 I have >> > a 1/3 chance of having >> > my computer instantly reboot after the splash >> > screen. Trying to run >> > Neverwinter Nights gives me a 1:8 crash ration. I >> > don't know what logs I >> > might look at, or what I might be able to do to >> > solve this problem. >> > >> > Any thoughts? >> > >> > ~Steve >> >> Hi, >> >> i'm using also this two games with my SuSE 9.1 , >> now without any crashes. >> but primerly i this reboot as you described in UT2004 >> always ! >> after installing the kintersect patch i had it >> sometimes, maybe with 1/3 chance or something >> like that ... >> but i had also a lot of freezes and hangups (no >> reboots) while using normal KDE or X applications >> (no OpenGL). >> after updating my BIOS i had no crash at all. >> the NWN never crashed because i installed it >> after my BIOS update. >> Maybe this information could help you ... >> but without some information about the >> hardware you're using i think it's nearly impossible >> to say anything more exactly. >> >> greetings, >> Franz >> >> >> >> >> >> >> Mit schÃ¶nen GrÃ¼Ãen von Yahoo! Mail - http://mail.yahoo.de > > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: suse-amd64-help(a)suse.com

1 0

usbmouse-trouble
by Claus Christian Larsen 19 May '04

19 May '04

Hello.- I have a amd64 suse 9.0 with a logicteck usbmouse. The mouse works just well. But every time i start the computer i vill have to set the mouse up again in yast: yast-> choose mousemodel-> usb. Solution? Regards Claus

2 1

Re: [suse-amd64] MSI K8T Neo {Via VT8237, Promise 20378} SATA + Suse9.1 - stable?
by Joel Wiramu Pauling 19 May '04

19 May '04

The raid on the MSI Master2far is just the Via vt8237, If you using a different manufacturer it's possible they are using the promise controller for hardware raid and the vt8237 just as the sata controller... I'm not sure I would have to look at the manufacturers specs. The Kernel crash appears to be just the same as yours with a slightly different message. This is the output from /var/log/messages during a crash the xconsole shows the same message as yours... May 16 06:45:27 rincewind kernel: Unable to handle kernel NULL pointer dereference at 000000000000002a RIP: May 16 06:45:27 rincewind kernel: <ffffffff8027ac72>{ide_multwrite+194}PML4 1102a067 PGD 2b62f067 PMD 0 May 16 06:45:27 rincewind kernel: Oops: 0000 [1] May 16 06:45:27 rincewind kernel: CPU 0 May 16 06:45:27 rincewind kernel: Pid: 7717, comm: y2base Tainted: P 2.6.4-54.5-default May 16 06:45:27 rincewind kernel: RIP: 0010:[ide_multwrite+194/320] <ffffffff8027ac72>{ide_multwrite+194} May 16 06:45:27 rincewind kernel: RIP: 0010:[<ffffffff8027ac72>] <ffffffff8027ac72>{ide_multwrite+194} May 16 06:45:27 rincewind kernel: RSP: 0018:000001004feb79c8 EFLAGS: 00010246 May 16 06:45:27 rincewind kernel: RAX: 0000000000000008 RBX: 000001007fae2a78 RCX: 0000000000000000 May 16 06:45:27 rincewind kernel: RDX: ffffffff8043e300 RSI: 0000000000000000 RDI: 0000000000000000 May 16 06:45:27 rincewind kernel: RBP: 0000000000000008 R08: 0000000000000008 R09: 0000000000000000 May 16 06:45:27 rincewind kernel: R10: 0000000000000000 R11: 0000000000000175 R12: ffffffff80495ad8 May 16 06:45:27 rincewind kernel: R13: 000001007fae0008 R14: 000001001c593680 R15: 0000010073481b00 May 16 06:45:27 rincewind kernel: FS: 0000002a98315c00(0000) GS:ffffffff804bd300(0000) knlGS:0000000055999080 May 16 06:45:27 rincewind kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b May 16 06:45:27 rincewind kernel: CR2: 000000000000002a CR3: 0000000000101000 CR4: 00000000000006e0 May 16 06:45:27 rincewind kernel: Process y2base (pid: 7717, stackpage=1001bb65240) May 16 06:45:27 rincewind kernel: Stack: 0000000000000000 ffffffff80495ad8 ffffffff80495990 ffffffff8027b694 May 16 06:45:27 rincewind kernel: 0000000000000000 ffffffff8026fbe1 ffffffff80134320 000001004feb7a00 May 16 06:45:27 rincewind kernel: 000001004feb7a00 ffffffff80495ad8 May 16 06:45:27 rincewind kernel: Call Trace:<ffffffff8027b694>{__ide_do_rw_disk+1396} <ffffffff8026fbe1>{ide_wait_stat+257} May 16 06:45:27 rincewind kernel: <ffffffff80134320>{autoremove_wake_function+0} <ffffffff8026e53f>{start_request+543} May 16 06:45:27 rincewind kernel: <ffffffff8026e8a2>{ide_do_request+818} <ffffffff8025058e>{generic_unplug_device+46} May 16 06:45:27 rincewind kernel: <ffffffff80250651>{blk_execute_rq+177} <ffffffff80253389>{scsi_cmd_ioctl+2169} May 16 06:45:27 rincewind kernel: <ffffffff80134320>{autoremove_wake_function+0} <ffffffff80134320>{autoremove_wake_function+0} May 16 06:45:27 rincewind kernel: <ffffffffa005c064>{:reiserfs:do_journal_end+3444} <ffffffffa004a835>{:reiserfs:reiserfs_dirty_inode+101} May 16 06:45:27 rincewind kernel: <ffffffff8026d121>{generic_ide_ioctl+1585} <ffffffff801ec44a>{avc_has_perm+90} May 16 06:45:27 rincewind kernel: <ffffffff801ed952>{inode_has_perm+98} <ffffffff80251bd4>{blkdev_ioctl+1716} May 16 06:45:27 rincewind kernel: <ffffffff801ee886>{selinux_file_ioctl+742} <ffffffff8017760f>{blkdev_open+47} May 16 06:45:27 rincewind kernel: <ffffffff8016dc9a>{dentry_open+234} <ffffffff801811f1>{sys_ioctl+897} May 16 06:45:27 rincewind kernel: <ffffffff8016de41>{sys_open+113} <ffffffff801103a4>{system_call+124} May 16 06:45:27 rincewind kernel: May 16 06:45:27 rincewind kernel: May 16 06:45:27 rincewind kernel: Code: 0f b7 47 2a 0f b7 57 28 48 89 f9 ff c0 66 39 d0 66 89 47 2a May 16 06:45:27 rincewind kernel: RIP <ffffffff8027ac72>{ide_multwrite+194} RSP <000001004feb79c8> May 16 06:45:27 rincewind kernel: CR2: 000000000000002a --- Kernel panic sorry this was the wrong terminology, should have been oops =-). >From this it looks like the yast2base package is bad... but even when I reinstall yast I get this error...(there is no yast2-base package so I reinstalled by hand the yast rpms) This is how I reproduce. Go into yast2 (X or Console dosn't matter) Go to install and remove software Change some package selections... Wait... 10 secs... message in xconsole/logs appears... Then I have 10 secs or so before system reboots. Just for the record, how did you obtain the release... The version I'm using I torrented off the net, because suse/novell havn't shipped to NZ yet. I've noticed some inconsitencys in some of the packages... and have built up the system by hand from base install to make sure yast isn't install corrupt packages. Also what ram are you using i'm using OCZ ecc reged dual ddr dimms (ddr400) with my 248, and my system fails mprime stress test... and I can't turn on the ecc chipkill function on my board and still get it boot anything (will post, but won't run memtest even when ECC Chipkill is turned on) I have emailed msi about this. But i'm thinking my ram could be the problem. (Even tho it's specifically built for this type of platform, and it's gross price... ($1500 NZ) Dunno about your board but try 2cpu's forums, I learnt alot about my board from there. http://forums.2cpu.com/showthread.php?s=a0b9da91be0e34f9b417970121ac65ea&th… As an Aside... has anyone managed to get the flash plugin working??? If so how I've tried and it keeps on saying cannot find shared librarys.... And is there a 64bit compiled version of openoffice binarys somewhere?... I'm using the 2.0 codebase, and compiling looks like a bit of mission. Kind regards Joel On Tue, 2004-05-18 at 04:23, Jan Meyer wrote: > Hi Joel, > > Joel Wiramu Pauling wrote: > > I can confirm the same errors... I.e Yast2 kernel panic with scr0000002 > > whenever I confirm additional package updates. > > Mmmh, interesting, I don't get a kernel panic but only a message in > xterm: "Import 'SCR' failed." and then the yast2 module does not start. > [None of the modules works] > > What do you mean by "confirm"? Start an online update? > > > Also I have various weird crashes with the machine. Am Using a vt based > > sata solution in a msi master2-far dual proc board with an opteron... > > Appears to be a known bug as reported by ak(a)suse.de in another mail to > suse-amd64. > > > Have you managed to get to raid to work at all.. I eventually disabled > > raid on the chip and set up softraid in linux... > > I only intend to have one hdd - hence no RAID. > > Do you also have a Promise controller? On my mainboard it appears to be > the choice for SATA hw RAID. I don't fully understand why there are two > different SATA/PATA controllers on my board in the first place. > > - Jan > > > > > Kind regards > > > > Joel > > > > On Mon, 2004-05-17 at 22:09, Jan Meyer wrote: > > > >>Hi, > >> > >>recently I tried to install Suse v9.1-AMD64 on my Athlon64 machine with > >>an MSI K8T Neo-FIS2R (MS-6702) board. [Kernel was updated to 2.6.4-54.5] > >> > >>To make the story short: During various stages (after finishing the > >>installation and trying to fix issues like an incorrectly formatted swap > >>partition), I had my only SATA drive connected to either of the two SATA > >>controllers (and always the other one disabled). Still I encountered > >>many complete system freezes and recently mainly kernel oopses, which - > >>as far as I can tell - were related to either access to the SATA HDD or > >>a PATA device on the VT8237 controller. > >> > >>Even though I can finally boot the system, strangely yast2 is broken in > >>a way that I get "import 'SCR' failed" errors. [I was only fiddling with > >>modules.dep and initrd.] > >> > >>Unless you have a better idea, I have now made up my mind that I should > >>take the windows approach and format-and-reinstall Suse9.1. But before I > >>start with that and run into the same problems: > >> > >>Can you recommend to me which of the IDE controllers I should use? Which > >>one has the most stable amd64 kernel modules? > >> > >>Or should I consider patching the kernel (for a recent sata_via patch > >>see also: http://lwn.net/Articles/76129/ ) - or possibly using a kraxel > >>kernel? > >> > >>Would system stability increase if I switched to a 32-bit kernel? Maybe > >>the SATA controllers are not the problem? > >> > >>Any hints would be greatly appreciated. > >> > >>best regards, > >> > >> Jan > >> > >>P.S.: On the Via VT8237 my SATA hdd is now recognized as /dev/hda. > >>Should it not be /dev/sda as on the Promise? > >> > >>PPS: When I got the system to run after switching the SATA drive from > >>Promise to VT8237, the hardware autorecognition feature offered me to > >>add the sata_via module to initrd. I said 'yes' and my initrd got > >>screwed in a way that I could not boot anymore. It took me quite a while > >>to recreate a workable initrd - and still I got error messages that > >>mkinitrd could not check the dependencies in modules.dep for sata_via. > >>Maybe something is wrong with the mkinitrd script? > >> > >>PPPPS. I also have a recent NVidia based graphic card, which takes an > >>AGP aperture of 128MB. Running the suse install CD in rescue mode, I > >>noticed that a module called nvram was loaded - what is that for? > >> > >>-- > >>"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen! > >>Jetzt aktivieren unter http://www.gmx.net/info > >> > > > > > >

3 5