I am new here;
I have found that if I call an ELF32 Executable program from a php page
loaded by a 64 bit PHP module then I obtain a shared library error,
even if the program does not require the library.
------ cc -o pro -m32 pro.c
then call it from a php page:
$s = "/tmp/pro 2>/tmp/er 1>&2";
echo "$s : ";
echo `cat /tmp/er`;
// just to test that it works...
$s = "ls -al /tmp 2>/tmp/er 1>&2";
echo "$s : ";
echo `cat /tmp/er`;
issuee? Error?Bug? my fault???
Hints? I cannot recompile at 64 all my programs ...
I'm fixing to put together a system for suse linux to run on from the 64
amd cpu. I'm looking at asus, abit,
gigabyte, an msi motherboards.
asus K8V-SE Deluxe K8T800 or K8N-E DELUXE
abit KV8PRO K8T800 Pro
msi MSI K8N NEO Platinum
I will put in 1 gig of ram on any of these systems. I have used asus boards
in the past but am willing to try another one this time around.
These are the models that one of our parts sources has in stock at the
moment. If there is another one out there that you would recommend I would
look at it also.
If you using one of these does all the on board components work, sound lan
ect with suse. I will be putting suse 9.3 on the machine.
I just received 9.3 today and installed it on my workstation. I had to
add 'mem=2000m' to the kernel boot options get it to boot up after the
install. Is this a known problem?
Here are some hardware details:
tyan S2885 motherboard
2 opteron 248 cpus
nvidia 6800 video card
lsilogic megaraid pci-x card
I'm also getting the following during bootup. The megaraid_mm and
megaraid_mbox modules are loaded and the raid array seems to be
operating ok. Although it seems quite a bit slower.
kobject_register failed for megaraid (-17)
XMMS was installed from SuSE's dvd and all patches from YOU were
applied. Whenever a cd is played, XMMS exits with a segmentation
fault. I am now giving up with SuSE XMMS implementation and would like
to compile it from source.
At the moment, compiling XMMS gives libmikmid, libvorbis and libGL
errors. It appears that the scripts cannot link with the right
libraries and include files or cannot find them. Can anyone offer any
assistance with compiling XMMS on a AMD64 computer?
On Wednesday 27 April 2005 13:04, you wrote:
> Valur Olafsson wrote:
> >Hello all,
> >Before going into the problem at hand let me say that my desktop computer
> > was working as it should running SUSE 9.2, which was installed on the
> > machine before I upgraded to SUSE 9.3.
> >Now to the problem. As the title indicates I have been experiencing
> > lockups after upgrading my AMD64 desktop machine to 64-bit SUSE 9.3.
> > This all started when I wanted to configure my USB Linksys wireless card
> > (WUSB11 v2.8) on my desktop. I needed to configure it to access the
> > internet. So, like I did when I installed SUSE 9.2 in the past, I
> > installed the wireless-tools and atmel-firmware rpms, and plugged the
> > WUSB11 into a USB port on my desktop. Using 'dmesg' I saw that the atmel
> > firmware got uploaded to the WUSB11. So the system recognized the WUSB11
> > as it had done when I was running 9.2. Then I went into the network
> > module in Yast2 and setup the wireless connection. After that I needed to
> > unplug and plug the WUSB11 to get it to start to connect to my router,
> > but as it was about the get an IP from my router the computer froze.
> >At first I did not know what the problem was, so I tried to install
> > different versions of the atmel-firmware rpm, both the one that came with
> > 9.2 (and had worked previously) and the most recent one from the homepage
> > of the atmel-firmware project. Still the computer froze when the WUSB11
> > was about to get an IP from my router. Next I thought that maybe the
> > dhcp client on SUSE 9.3 was to blame so I hardwired a particular IP to
> > WUSB11 when setting up the connection in the network module in Yast2 to
> > bypass it. This did the trick, I was finally able to get online, without
> > the machine locking up. This is currently the only way I know how to get
> > the computer online using the WUSB11.
> >This however was to be a short victory, since about a half an hour after
> >getting online for the first time, while surfing the net, the computer
> > locked up again. This time, I was not doing anything specific, just
> > browsing the web through the wireless connection. I thought that maybe
> > this was a one off thing, but this has happened multiple times after that
> > incident.
> >As I said in the first paragraph, everything was working well when running
> >SUSE 9.2 on the same hardware and using the same WUSB11 device to access
> > the internet. Also, the machine is a dual boot machine, and everything
> > is working fine in windows.
> >So what would be my next steps in debugging this problem. Currently, I
> > have no idea what is causing the lockups, or why even the dhcp should be
> > causing lockups when I'm not bypassing that by hardwiring the IP. Any
> > suggestions to logs or something of that sort that I should be looking at
> > are welcome, 'cause I sure as hell don't know what should be my next
> > steps.
> >Valur Olafsson
> I had even worse problems with a Belkin F5D6050 usb adapter. The
> adapter was recognised as "wlan0" device. However, whenever I tried to
> connect to the wirless network my entire system would freeze, forcing me
> to hard boot the PC. My solution was to delete the wireless drivers
> provided by SuSE located in the /lib/modules directory and to compile
> the drivers from source.
> My suggestion would be that you try this approach, if you can find the
> source code for the the drivers.
Are you talking about the source that comes when you install the km_wlan rpm
that comes with suse 9.3. If so, then that is just what I did, that is, I
deleted the wireless drivers in /lib/modules and compiled the drivers from
source that came from the km_wlan rpm. Did you maybe find some other source
for the drivers that worked for you? I ask, because I believe that our USB
adapters have the same atmel chipset. My adapter uses the at76c503
(at76c505_rfmd2958 to be more specific) kernel module. Anyway, after the
recompile, I still need to hardwire the IP number for the adapter when I am
setting it up in the network module in Yast2. But, so far, I've had no
lockups and thus no hard reboots needed to fix that.
Thanks for all the help,
Thanks for giving this link.
I had a look : there is only an update for SuSE 9.0 i586.
As my k3b does not work properly, I use now cdbakeoven
but this is only for CD, not for DVD. For DVD, I have to
boot with SuSE 9.1
You could visit http://packman.links2linux.org under Multimedia.
He builds a lot of different packages for various suse releases. I know
he has a k3b that matches you suse distro, not sure about the kde part
From: patheve2 [mailto:firstname.lastname@example.org]
Sent: Thursday, April 28, 2005 6:58 PM
Subject: [suse-amd64] k3b and suse 9.0 AMD64
k3b freezes when I try to burn an ISO image.
This k3b 0.10 with KDE 3.1.4 of SuSE 9.0 AMD64.
Where can I find a update of k3b for this SuSE ?
Check the List-Unsubscribe header to unsubscribe For additional
commands, email: suse-amd64-help(a)suse.com
We are having major problems with our Athlon 64 system that is being used as a
We are running a Brother printer that is not listed in the drivers list, but
has been printed to using the gimp-print driver. (known to work the largest
number of printers)
Now Brother doesn't "support" linux, but they do provide linux drivers for
some of their other printers. Also the printer is similar to our HP laserjet,
and it runs flawlessly.
It seems most of the issues are coming from printing from OpenOffice, which
seems weird. But it gets even weirder. Now looking at the print queue it
looks like this:
krusty:~ # lpq
mfc7820n is ready and printing
Rank Owner Job File(s) Total Size
active brian 4 (stdin) 6144 bytes
1st brian 5 Untitled1 26624 bytes
2nd brian 6 Job Report - KJobViewer 56320 bytes
3rd brian 7 file:/// 232448 bytes
4th brian 8 file:/// 232448 bytes
5th brian 9 file:/// 232448 bytes
But nope, it isn't printing. Any suggestions?? We have removed the printer,
and re-added it. Hooked it up directly through USB, and also had it networked
as well. While the printer was networked, we could only get one page to be
sent to the printer and then the CUPS server said the printer "wasn't ready"
President and CEO
WebbGroup Network Systems L.L.C.