openSUSE AMD64 February 2005

amd64@lists.opensuse.org

111 participants
114 discussions

by larry_prikockis＠natureserve.org

Has anyone managed to get any DVD playing software running properly under SuSE 9 for the AMD64? I've got an ASUS K8V Deluxe MB and an NVIDIA GF5200FX video card, for what that's worth. I've been trying, with little success, to compile a working version of the 'Ogle' DVD player, but am running into all sorts of dependency issues with RPMs, and missing library issues compiling from source. If someone else has gotten this working, I'd be interested in hearing exactly what RPMs/source files you used and what steps you followed. Thanks in advance ----------------------------------------- Real programmers confuse Christmas and Halloween because DEC 25 = OCT 31

17 years, 4 months

Giant honking great big .x.err file in /root

by jerry bookter

Hi folks-- I've been noticing my system acting funny lately. Last night apps started closing themselves, requiring a reboot. Sometimes cntrl-al-del won't work; after closing down X the same debug information flashes past on the screen endlessly, as if the machine can't quite manage shutting down all processes. Reach for the reset button..... However the system comes back up and functions fine for a while. Tonight VMware started complaining it was out of disk space, though I have about 70Gb allocated to / and should be nowhere near out of room on the drive. So I poked around and lo & behold I found a file named .x.err that was 33.6Gb(!) Obviously I've got something seriously wrong with X... I just freed up about 13Gb in / by moving some stuff over to one of my FAT32 partitions, but I'm afraid to even try to open this huge file. Is it safe to delete it, then wait a day or so to open it when it recreates itself? Then I can post what it says and work on getting X fixed. I'm tempted to just reinstall from the ground up, but I hate to have to go through all the tweaking and configuring of my setup again. So, is it safe to delete this file? TIA.....!

17 years, 4 months

Empty Files appearing all over file system

by Joel Wiramu Pauling

I first noticed this a day or so after install of suse 9.2 amd64, and now 2 months down the track I have noticed the same thing happening all over my filesystem. It only occurs on my 64bit workstation, my 32bit laptop is fine. What it is is an empty file with the name simply '2' appearing this appears in home directorys, / /vol and a seemingly random assortment of places... Deleting the offending file removes it but it comes back after a while... I've tried looking through logs etc and stat on the files they always have one of the systems users creation uid and group. But are created at seeminly random times. Anyone know what service/program thing that may be causing this behaviour?

17 years, 4 months

Re: [suse-amd64] AMD 64 and MPlayer

by Arne

Maybe using configure with --enable-libsuffix=64 might work /Arne On 21.2 2005 00:11, David Gillis wrote: > >I am trying to compile MPlayer using the --enable-gui on an HP Pavillion >with an AMD 64 processor. When I do ./configure --enable-gui the >configure fails with > >Checking for GUI ... yes > >Error: X11 support required for GUI compilation. > >I do have the devel rpms installed I think. Below is the part of my log >file that shows the no. What am I missing. MPlayer compiles and works >fine without the gui. > >David > >########################################## > >============ Checking for X11 headers presence ============ >Result is: yes (using /usr/X11/include) >########################################## > >============ Checking for X11 libs presence ============ >Result is: yes (using /usr/X11R6/lib) >########################################## > >============ Checking for X11 ============ > >#include <X11/Xlib.h> >#include <X11/Xutil.h> >int main(void) { (void) XCreateWindow(0,0,0,0,0,0,0,0,0,0,0,0); return 0; } > >cc /tmp/mplayer-conf-25663-32290.c -o /tmp/mplayer-conf-4934-32290.o >-I/usr/X11/include -L/usr/X11R6/lib -lXext -lX11 -lnsl >/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.4/../../../../x86_64-suse-linux/bin/ld: > >skipping incompatible /usr/X11R6/lib/libXext.so when searching for -lXext >/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.4/../../../../x86_64-suse-linux/bin/ld: > >skipping incompatible /usr/X11R6/lib/libXext.a when searching for -lXext >/usr/lib64/gcc-lib/x86_64-suse-linux/3.3.4/../../../../x86_64-suse-linux/bin/ld: > >cannot find -lXext >collect2: ld returned 1 exit status > >ldd /tmp/mplayer-conf-4934-32290.o >ldd: /tmp/mplayer-conf-4934-32290.o: No such file or directory > >Result is: no >########################################## > >-- >Check the List-Unsubscribe header to unsubscribe >For additional commands, email: suse-amd64-help(a)suse.com > > ------------------------------------------------------------------ Gratis svenskpråkig e-post och förmånliga textmeddelanden http://webmail.surfnet.fi ------------------------------------------------------------------

17 years, 4 months

hotplug SATA drives

by Rene Salmon

Hi list, Can some one point me to a how to or have any experience doing this? I added a new hotplugable drive to our SATA disk array. The disk array assigned the disk a new LUN. The LUN assigned to new drive is LUN 1. So as far as hardware is concerned everything is working fine with the hot-plug. Now on the Linux server I need Linux to rescan the SCSI bus and pick up this new device so here is what I did, /root# echo "scsi-qlascan" > /proc/scsi/qla2xxx/1 This got the qla2xxx device driver to scan the SCSI bus for new LUN/drives. Here is the syslog message for this. Feb 22 14:02:41 kernel: qla2300 0000:03:03.0: Scheduling rescan for new luns.. Also if I cat the /proc/scsi/qla2xxx/1 i see that the qla2xxx driver did detect the new LUN LUN 1. /root# cat /proc/scsi/qla2xxx/1 SCSI LUN Information: (Id:Lun) * - indicates lun is not registered with the OS. ( 0: 0): Total reqs 4015, Pending reqs 0, flags 0x0, 0:0:00 00 ( 0: 1): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:00 00 Now I do not know what the next step is. How to I get Linux to assign a /dev/sdXXX to this new LUN? Any ideas? Thank you for any help on this. Rene

17 years, 4 months

Re: [announce] 9.2 AMD64 Install CD with New Kernel

by Laboratory for Micro Enterprise

Andreas I'm trying to install 9.2 AMD64 on a new Asus A8N SLI Deluxe system with SATA HD and PCI-E NVidia GeForce 6600 graphics card. Using your 'Install CD with New Kernel', the boot process gets as far as 'unpacked extension disk', beeps, the screen goes blank and the system locks up - virtual consoles don't respond. I then tried a 9.2 32-bit install from the distribution CDs. This worked ok up to first boot of the newly installed system, when again the screen went blank and the system locked up. I repeated the install, this time configuring run level 3 as the default instead of 5. That gave me console access to the system. Suspecting a graphic card driver problem, I edited /etc/X11/xorg.conf to make 'vga' the default device instead of 'nv'. Then init 5 gave me X and a gleaming new desktop. This confirmed the 'nv' driver problem I've seen reported. The question now is how to proceed with the 64-bit install? It appears that 64-bit YaST doesn't use the 'vga' driver when it starts up (as 32-bit YaST evidently does), but instead uses the defective 'nv' driver. Is there a way of changing this unfortunate behaviour? NVidia provides a driver which is supposed to work ok, but I can't get to a point where I can install it. MfG John Storrs

17 years, 4 months

front panel usb ports

by Joe Georger

Here's a strange one.... I have a couple of usb thumbdrives by Memorex. Thunder K8W, dual Opteron 246's, Suse 9.2, Lian Li case Thumbdrive(s) initially worked on front panel usb. Now I plug them in and nothing happens. No cpu activity and certainly do not get mounted. Nothing in dmesg or /proc/bus/usb/devices. I cannot manually mount them (...not a valid block device). But they do work if I use a rear port. Is it me or am I missing something?

17 years, 4 months

User Mode Linux installation + amd64

by Joel Wiramu Pauling

Hi everyone. Suse 9.2 amd64 in yast 2 there is a UML install option. I sucessfully went through the wizard, and was waiting for somthing to happen, I got an xterm poping up, but it just complained about not finding port-helper (which is in /usr/lib64/uml/). At this point I did a ps ax, and found no less than 3 instances of ./linux (presuming the uml kernel). I couldn't kill them all, so I rebooted. On reboot I tried to start the uml environment through /etc/init.d/uml start... but kept on getting "skipped" messages. Is there somthing im doing wrong or is the UML toolset included with 9.2 broken? Kind regards Joel W

17 years, 4 months

Re: [suse-amd64] vodafone 3g card

by jm macip

Matt: I've allready tryied to add memory addresses reported by windows to the config.opts but no luck. One strange thing is happening, all my PCMCIA 16 bit cards are working: Compaq wl110, compact flash adapter and Thoshiba 2GB HD card but none of the 32 bit like a serial ata, USB 2.0, firewire and a conceptronic c54c, or vodafone 3g card are detected by the pcmcia subsystem. Ok, I will give a look to pcimcia Forums. >>> "Matt T." <Matt(a)boons.net> 21/02/2005 17:57:13 >>> On Monday 21 February 2005 03:11, jm macip wrote: > ** High Priority ** > > The only significant messages I get form dmesg are: > Feb 20 21:05:04 JMA64 kernel: psargs-0352: *** Error: Looking up > [Z005] in namespace, AE_NOT_FOUND > Feb 20 21:05:04 JMA64 kernel: search_node 0000010037e05c30 start_node > 0000010037e05c30 return_node 0000000000000000 sorry, doesn't ring a bell here. I haven't worked with PCMCIA to USB bridges yet, so I do not exactly know what to expect. I'm just guessing now, but what you could do is to make the memory and port ranges smaller. For a start, reduce it to the values you took from winXP only. Nothing else. Or you could load the module used by pcmcia for the usb bridge manually. I don't know how it's called now, I'm not at the notebook now. Look up the name of the module in the /etc/pcmcia/config file. (This is the way I get the Axen / Sagem GPRS card to work.) Then the next step would be to have a look at the PCMCIA mailing list and see if you find something there. May be the developers can guide you through debugging. This is not just said like that, I did find there the info which enabled me to get the Sierra Wireless aircard working on my amd64 notebook. Nice challenge. Good luck! Matt > > >>>Matt T. <Matt(a)boons.net> 02/20/05 8:52 pm >>> > > On Monday 21 February 2005 01:07, jm macip wrote: > >Yes, I have corrected config.opts and also added the memory areas > >reported by Windows. I also added the PCI bridge memory area. > >In windows the card is reported as a OPTi 82c861 PCI to USB open Host > >Controller using memory D04FE000-D04FEFFF, should I add this mem area > > to > > >config.opts? > > Why not, give it a try. > > After what Pascal reported about his card using memory and ports > different > from what lspci reported it would not surprise me. > > However please be aware that we could help you much better if you would > answer > more clearly about what you find in /var/log/messages or as dmesg > output. > Did you see my questions? > > If there would be indeed No messages, as you said earlier, then PCMCIA > would > not even start to try to talk to the card, and then adjusting the memory > and > port range would not help, the PCMCIA code would not get started. > > I have a modem card, when I insert it, then kde freezes. Until I take it > out > again. After that kde works fine again. When I close down the memory / > port > ranges then it does not get recognized, but PCMCIA starts and gives some > output. May be I just have not found the winning port / memory range for > it. > > This just to demonstrate you that PCMCIA can work for some cards, and > for > others not (yet). In order to understand if you have such a not working > card, > your clear report of /var/log/messages or as dmesg output might be > helpful. > > Also, have you seen my post that I need to kill and restart cardmanager > before > any card gets recognized. (I did not test yet if that is true for older > kernels, or only for the latest ones which I have installed currently. > As far > as I remember it was not like that for the kernels current 2 or 3 months > ago. > > HTH, > Matt > > >Thanks in advanve. > >Josep Maria Macip > > > >>>>Matt T. <Matt(a)Boons.net> 20/02/2005 16:46 >>> > > > >On Sunday 20 February 2005 03:09, jm macip wrote: > >>I'm sure PCMCIA is working > > > >PCMCIA on AMD64 might be working for some cards, but may be not for > >all. > > > >I understand that you already corrected your config.opts file using the > >output > >of lspci, correct? > > > >However if one card works that does not mean that all can work. Every > >card > >uses a different memory range / port range to talk to your system. I > >assume > >that some cannot use the memory / port range offered by amd64 64bit > >systems. > > > >Also different cards / different functions use different parts of the > >PCMCIA > >code. network cards and modem cards use different modules of the PCMCIA > > > >package. Some parts might work better than the others. > > > >>>>>Andreas Jaeger <aj(a)suse.de> 19/02/2005 20:49 >>> > >> > >>jm macip <jmmacip(a)gsei.net> writes: > >>>No messages! card is not recognized! > > > >Nothing in /var/log/messages? Nothing at all? Nothing about anonymous > > > >memory? Nothing about unable to access memory? > > > >Ususally there is something showing that PCMCIA understood there is > >something > >to do for it, it wakes up, checks, and if it does not recognize what is > >going > >on there usually is a message. And as far as I've seen, if a card does > >not > >get identified, the PCMCIA code seems to try the memory_cs module, > >which does > >the output listed above. > > > >Also, type dmesg in a konsole window, after you inserted the card. > >Look at > >the last lines of the output. There should be something. Is it? > > > >>Really nothing at all? Search the archives of this list, could be > > > >the > > > >>PCMCIA issue we discussed several times, > > > >yes, not all cards could get to work, and some need dirty workarounds > >(as > >postet here this and last month) > > > >>Andreas > > [snip] > > >>>>>>Andreas Jaeger <aj(a)suse.de> 19/02/2005 15:15 >>> > >>> > >>>jm macip <jmmacip(a)gsei.net> writes: > >>>>Hi all: > >>>>I recently bought a Vodafone 3g pcmcia card but i'm unable to > > > >make > > > >>>it > >>> > >>>>work. > >>>>I have followed the steps stated in this how-to > >>>>http://www.pharscape.org/index.php?option=content&task=view&id=28 > >>>> > >>>>but I get stuck beacause cardctl doesn't identify the card. (it > > > >is > > > >>>>currently working with my Wl-110 wireless card) > >>> > >>>What is the output of /var/log/messages? > >>> > >>>Andreas > > > >HTH, > >Matt > > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: suse-amd64-help(a)suse.com -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help(a)suse.com

17 years, 4 months

Re: [suse-amd64] cannot load kernel mod snd-emu10k1]

by melissad

New install and update to the new kernel. Have a SoundBlaster external Audigy NX connected via USB. Have turned of the ASUS SK8N sound codec in BIOS. The Audigy is on and works in Windows. In YaST, have deleted the SK8N native sound board and tried to add the Audigy. Error msg = "The kernel module snd-emu10k1 for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRG parameters." I had a SB external working under SuSE 9 32. Does anyone have any ideas that might help? melissa

17 years, 4 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

openSUSE AMD64 February 2005