Hi, I just installed 11.0 on a machine that I assumed to be a i386. The Hardware app in YaST seemed to confirm that it’s i386.
But I’m now looking at my computer’s specs online, which seem to indicate that my system is in fact 64-bit. So how can I know for sure?
Should I trust my 32-bit YaST, or is there a more conclusive way to determine this?
grep -w lm /proc/cpuinfo
Output means 64-bit, none means 32-bit.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you put in 32-bit media then you installed a 32-bit OS regardless of
your processor’s capabilities. Burn a 64-bit DVD and try the install.
If you get into the installation at all (or even to the very starting
parts of it) you have a 64-bit-capable box.
Good luck.
Slipstream00 wrote:
> Hi, I just installed 11.0 on a machine that I assumed to be a i386. The
> Hardware app in YaST seemed to confirm that it’s i386.
>
> But I’m now looking at my computer’s specs online, which seem to
> indicate that my system is in fact 64-bit. So how can I know for sure?
>
> Should I trust my 32-bit YaST, or is there a more conclusive way to
> determine this?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIs3Gl3s42bA80+9kRAkpQAJ9r4cXg1VURSmE4kCp5B3Ba2sbwPgCdE4pU
XeX4E1oF3uFYy9ZGckgLJ3c=
=ffkp
-----END PGP SIGNATURE-----
Thank you ken_yap! Here’s the output…
linux:~ # grep -w lm /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up pebs bts pni monitor ds_cpl tm2 cid cx16 xtpr
So it’s a 64? I’m going to try another 64-bit iso. I tried it once, but no luck. Not sure if it’s due to my CD-RW being defective though, since it’s been re-written many times.
I just went to my neighbors’ and got a new CD. This one works! My system is 64-bit!
I haven’t experimented with 64-bit in a long time. Can someone tell me if it’s still necessary to use win32 codec and to switch all browsers and plugins down to 32-bit?
On Tue, 26 Aug 2008 05:26:01 GMT
Slipstream00 <Slipstream00@no-mx.forums.opensuse.org> wrote:
>
> I just went to my neighbors’ and got a new CD. This one works! My
> system is 64-bit!
>
> I haven’t experimented with 64-bit in a long time. Can someone tell me
> if it’s still necessary to use win32 codec and to switch all browsers
> and plugins down to 32-bit?
>
>
I run 64bit suse on my machines, but will warn of many potential ‘gotchas’
when using a 64bit system in a 32bit world. Compiling programs can be
adventurous, as some ‘quirks’ are introduced into 32bit software which
expect 32bit registers and 32bit longs.
The OpenSUSE 11.0 install for firefox, java and flashplayer went very well,
only issue was the java, I used the newly released java7 (OSS) and it runs
well with the 64bit firefox, although dropping to a 32bit FF3 would probably
make things easier I suppose.
Depends on your skill level and patience. I’ve had the occasional issue
building some software I tinker with, odd programming quirks involving 32bit
limits usually. Some software won’t run until you remember to install the
32bit libraries if they’re provided, often they aren’t. Beware!
I had entire library ‘groups’ reinstalled to satisfy 32bit dependencies where
I had 64bit installed originally…
put it this way: It will work. You may have strange issues and problems.
And again, it depends on your skill level with things.
I’ve read that there is no “need” to run 64bit unless you’re running huge
databases or things like that… no idea. I know that the 64bit programs
take up a slightly bit more on the disk, you also need to have the 32bit
libraries installed too, which nearly double the space needed for the
libraries.
I’d really recommend 32bit install initially, and as your experience grows,
you might try installing 64bit later, after you know how things work.
Loni
–
L R Nix
lornix@lornix.com
Thanks loni, I’ve been using 32-bit for about 2-years or so. I had lots of headaches in the past with 64. Now I’ve once again gotten brave and installed the 64. I hope I don’t regret it too much!
So do I need to switch down to 32-bit browser, plugins and win32 codec to view videos and such?
And what about sound? I ran alsaconf, but my sound doesn’t work at all when I test it from YaST. Do the sound packages also need to be 32-bit to work with 32-bit browser plug-ins?
Must remember that line for cute neighbours. “Hi there, I’m your neighbour and I wondered if I could borrow a CD blank.” 
Sound is likely a separate issue.
Your sound driver comes from the “alsa” series of packaged rpms. There are different rpms for 64-bit and 32-bit. The proper 64-bit alsa packages should have been installed by default, although sometimes one needs alsa-firmware, and it is not installed by default. There are also some quirks (and bugs) introduced in openSUSE-11.0 wrt sound, and its possible you ran afoul of one of those.
There is an openSUSE audio troubleshooting guide in the following URL:
SDB:AudioTroubleshooting - openSUSE
If attempts to follow that don’t work, then in order to provide you concrete guidance as to how you can fix your sound, it would be useful to have detailed information on your PC’s hardware and software sound configuration.
To provide us more information, then with your PC connected to the internet, please copy and paste the following into a gnome-terminal / konsole:
wget http://home.cfl.rr.com/infofiles/tsalsa && su -c 'bash ./tsalsa'
when prompted for a password please enter your root password. Please try to accurately answer the question on the number of plugs/jacks on your PC (for example my PC has 3 i/o plugs/jacks: microphone, line-in, line-out ). When the script completes, it will pass you a URL. Please post that URL here.
Also, please copy and paste the following, one line at a time, into a gnome-terminal/konsole and post the output here.
rpm -qa | grep alsa
rpm -qa | grep pulse
rpm -q libasound2
uname -a
cat /etc/modprobe.d/sound
Thanks, and good luck.
On Tue, 2008-08-26 at 05:26 +0000, Slipstream00 wrote:
> I just went to my neighbors’ and got a new CD. This one works! My
> system is 64-bit!
>
> I haven’t experimented with 64-bit in a long time. Can someone tell me
> if it’s still necessary to use win32 codec and to switch all browsers
> and plugins down to 32-bit?
yes and no. You should be able to get flash and mplayerplug-in and
friends to work just fine (all 64bit).
The problem area is with Java applets (IMHO). And occasionally I
get problems with flash under 64bit. But Java is the killer for
some of my needs… so I go 32bit for the browser and plugins.
Then everything works. I don’t think my browser needs to
be 64bit (can’t think of a case right now where that’s needed).
Ok, after a series of long distractions, I finally got back to this task…
oldcpu, the trouble shooting guide worked. Just needed to adjust the mixer. Thanks!
cjcox, so far 64-bit Java seems to work for me. I selected the 64-bit openjdk plugin, java-1_6_0-openjdk-plugin. I’ll post back if I find something wrong with it.
The only sticking point seems to be Flash. For YouTube, it runs fine in the wrapper. But for news videos on yahoo.com (is that considered streaming video?) it plays the first one but then the plugin disappears afterwards.
I’m hesitant to downgrade to 32-bit Firefox. The 64-bit version seems to run more stable, maybe due to the extra address space that is usable in RAM: 32^2 versus 64^2. I keep lots of browser windows open at once, and 64-bit seems to avoid crashing and freezing-- unlike the 32-bit Firefox that was installed previously.
I really hate Flash, and don’t understand why the industry has settled for such a crappy standard. According to what I’ve read on the web, it sucks in Windows too. Oh well. BTW, swfdec looks to show some promise since it has nice control features. It doesn’t load reliably on my system though–many times I just get a blank rectangle. And it doesn’t appear to play streaming video yet (yahoo.com news, as mentioned above).
just a question i got the out put
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm ida
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm ida
from grep -w lm /proc/cpuinfo
am i 64-bit?
The easiest way to find out is to type uname - a in a console if you see x86_64 then you have 64 bit
/Geoff
Hi
As stated in the previous post, if you get output from the command your
processor is 64bit
Now are you running a 64bit OS, use the command uname -m to find out,
if it says x86_64 then it’s 64bit.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.1 x86 Kernel 2.6.27.7-9-default
up 1:53, 2 users, load average: 0.34, 0.18, 0.12
GPU GeForce 6600 TE/6200 TE - Driver Version: 180.22