Suse 10.1 Final - anyone?

I'm running 10.1rc2 on my Dell M70. Apart from some bug fixes, there is no difference between it and the final.

Movie here: http://theendlessnow.com/ten/uP/Articles/xgl.mpg

as far as i am concerned suse is crap. i swear to you if you pull a linux cd out of a dogs ass it will still be better than suse. that said, i wont be trying 10.1 finals where as the betas have already disappointed me. that, and i am in the middle of setting up a great gentoo install.... which WORKS and is FAST ... something suse is, and never will be.

I am currently running Suse 9.3 (64 bit) on my emachines m6805 laptop. This is the ONLY distro (so far) to work with all of my hardware, and be stable. So I downloaded Suse 10.1 (also 64 bit) thinking it will be improved. I have installed it twice.

The first time it seemed to be working fine except that I set Yast2 power management acpi to shutdown when I closed the lid. I closed the lid and came back several hours later to a still running but locked up laptop! I could not get it to reboot or respond to the keyboard, so I did a hard reset. The file system was so totally wrecked that I reinstalled. (First thing I learned: don't use power management to control lid-closed shutdown.)

The second install (fresh from scratch, not a repair) went well, but runs unimpressively slow. Suse changed the way some things were controlled (I hate when they change where stuff is controlled from), so that took some figuring out. For instance Samba settings were slightly different. Ndiswrapper worked with the Suse rpm version. (In 9.3, I had to compile from source to get ndiswrapper working. The rpm on the Suse DVD did NOT work!) Printing to a Windows connected HP Dekjet 722C worked and did not lose it's settings. (In 9.3 every time I reboot, I have to reset Samba firewall settings. Suse Firewall is awful.) Acpi seems to have something wrong though.

So I went back to Suse 9.3. Suse 10.1 is less stable (on my laptop). It shows promise though of improving the firewall and Samba at least. But Please Suse, as you improve things, DON'T change how they are controlled.

EDIT: Forgot to mention that the 64 bit problem of screen not returning to previous brightness setting has NOT changed. I still have to re-brighten my screen each time I reboot my 64 bit Suse 10.1 AND Suse 9.3. (For that matter Fedora Core 5 too.)

Hi all, Im running a dual boot with XP 32 and Suse 10.1 x64 on a Sager 9750. All is working fine except the onboard webcam and the tv tuner. Suse 10.1 completley enables acpi and if ya google "Hacking Suse 10.1" you should find a great link to The Jem Reports setup for multi media, wireless etc.. (Atheros Mad Wifi is for the a/b/g gygabite wireles card i have so if ya have something other than an atheros wireless chipset youl have to look that up seperatley. Also i stopped short of the XGL configuration due to reports that the performance slow down is horrible. Other wise the only other issue i faced was getting the 3 acceleration (Go 7800gtx) working in 1920x1200. The trick to xorg initializing the LCD is as follows:

During the install of Suse 10.1 dont hesitate to pick 1920x1200, a screen size of 17 with a 16/10 ratio and 1920x1200 WUXGA at 24 bit (do this even if the refresh rate is not correct - you will change it in the steps below. Download and install the video drivers from Nvidia (http://www.nvidia.com/object/linux_d..._1.0-8762.html) following the instructions in Nvidias link to the Suse Read Me (http://www.suse.de/~sndirsch/nvidia-...-HOWTO.html#2). The section called 10.1 x64 beta is the commands you install with. when the install completes do not run sax2 as the instructions state.

Instead edit the /etc/X11/xorg.conf and make the following two sections look exactly like they do in this post.

Section "Monitor"
DisplaySize 366 229
HorizSync 29-76
Identifier "Monitor[0]"
ModelName "1920X1200@61HZ"
Option "DPMS"
VendorName "--> LCD"
VertRefresh 0-62
UseModes "Modes[0]"
EndSection

Section "Device"
BoardName "GeForce Go 7800 GTX"
BusID "PCI:2:0:0"
Option "UseEdidFreqs" "false"
Driver "nvidia"
Identifier "Device[0]"
VendorName "NVidia"
EndSection

Reboot the machine after saving the changes and 3d should enable and launch into X (you should see the NVIDIA logo just before login if 3d is enabled.

I could care less about the onboard web cam and as far as the TV tuner goes, Suse 10.1 detects the card properly however i have loaded the module with every tuner possible in the tuner list and one that works simply doesnt exist as far as im aware. Im sure tuner support for it will be available at some point -- hopefully soon. Enjoy (I will check back here to see if there are any questions.