openSuSE 11.3 .. Feb - Jul 2010| Time: |
|
Next Event: 11.3 PR Jul 15, 2010 |
These Web Pages change monthly, weekly, daily, hourly, minutely ... in seconds. All depends on what I have discovered... and how fast I have discovered it... and when I see my mistakes.
System Environment
I think it only fair to inform all readers of the System Environment this Operating System is being placed on / worked with / worked on. Different strokes for different folks. You may not experience the same successes, or failures, as I do because of different hardware.
| Harware Description | ||||
|---|---|---|---|---|
| Item Specifics - HP Pavilion Media Center TV m7480n Desktop PC | ||||
| Brand: | Hewlett Packard | Memory(RAM): | 4 GB | |
| Model: | Pavilion m7480n | Hard Drive Capacity: | (2) 300GB Drives | |
| Processor Type: | Intel PentiumD 940 (P) | Operating System(s): | Windows XP Media Center / SuSE 11.2 | |
| Processor Speed: | 3.2 GHz | Optical Drive: | Lightscribe DVD + DVD ROM | |
| Video Card: | GeForce 7300LE | Sound/Audio: | Realtek ALC 882 chipset | |
| Wireless Keyboard & Mouse with USB receiver/transmitter, Modem, Memory card reader, Network Integrated 10/100 Base-T, Wireless LAN 802.11 b/g, TV tuner card with FM tuner, Remote Control - USB infrared remote and receiver | ||||
| Even though it is not included in the name, the processor is Dual-Core. An "older" technology but still a Multi-Core. Does make it faster. (...yes I am proud of it.) | ||||
| Printer: | HP cp1700 | Router: | NetGear RT311 | |
| Printer Server: | NetGear PS110 | Switch: | NetGear FS108 | |
The Usual -or not- Intro
Another one of my fabulous write-ups on installing SuSE, now known as openSuSE. In these notes, I change between 'openSuSE' and 'SuSE'. Two reasons: SuSE is less typing and I like the sound of it. (Like Chuck instead of Charles.) I started these writeups primarily for myself and I see that others have at least looked at them. The main reason for them was so that I would have references of things done -and- have something to put on my Web Pages. In the beginnings there were lots of troubles installing VMware. Now it, as this version of Linux, has matured and they are relatively easy to install.
Of couse the ease of installation can be, and many times is, subjective. Depends on number one, the equipment you have. Number two, what you want to do. (Those two sometimes fight for first.) Annndd number three, your experience.
The DVD version of this OS contains a lot of Software. In addition, you can download and install software from various Web Sites. Now then, IF all you want to do is run this OS and possibly search the Web, then the default install will probably suit you. However, IF you want to develope some software and/or install some drivers and/or install VMware ... then you will need to install ... at a minimum, the 'C' and 'C++' compilers, the tool 'make', and the kernel source code. This act is mentioned in the verbiage that follows. I try to add/change each version somewhat to make things easier. -But- since I haven't gotten any feedback, I just have to wing it. Hopefully something in this mess will help at least one other person. If it does then my mission has been accomplished.
Welcome:
 Click-on for larger view |
July 15, 2010 Once again, on time. (I have moved this one to the top cause...
after all, it is what we are interested in. The rest are just notations for reading.) I brought down the code shortly
after it was available. However, I am delaying on installing it. Need to check out IF there is anything that needs back-up
before I ruin my current SuSE. It takes time to re-do a set-up and it seems that just about the time I get everything the way
I want it ... they come up with a newer, greater version!! Think this time I am gona stay put. |
Oh well. Mute point now. My cable connection is busted. Yes, I know I can install without the cable connection -but- at the tail-end of the install there is a requirement for an Internet connection. Yes... it is minor ... but I'll wait.
Think I am gona do the Update. IF there are problems ... then I will do a Full Install. The Update needs testing anyway.
Create New User: Click-on for larger view |
I want to put this up front so, hopefully, all will see it before they start...and it will cause some thought... and possibly some criticism. There are some defaults to the install that I personally do not agree with and will cause heartaches and problems later. One of them is Automatic Configuration and the other is Auto Login. I strongly suggest that you set the Auto Login to NO... On the Create New User frame, uncheck the box that says Automatic Login. IF we get to free with our systems then we are going the way of Windows and will loose the great security that we (the Linux Community) are famous for. |
| Auto Login: Now then, my reason for this... you get choices at the Login Prompt. IF
you want to change a parameter or sign on as root, or a different user, you have that option/choice. Auto login
takes you to .. you. To really play with Linux you need the OS selections and the User selections with all their
optional parameters available.
(Just my humble opion...)
And this is possibly needed when you are setting up your graphics card... see below. Auto Configuration: Uncheck this. More cause of past problems than anything else. I just prefer to set up the system myself and have not had as many problems IF I do it that way. Besides, then I get to see what it can find, and has found. |
|
Well, here it is, Feb 10th, 2010 and I still haven't
gotten the latest version of openSuSE downloaded.
I see that it was released, or announced on the 1st but I was to busy working on other's computers. So we will go over to
the SuSE page and read up on the new one whilst downloading it.
...now up to Apr 19th, 2010 ... and I am trying to get back to it.
I would really like to get back to the stage where my Linux was better than Windows. Right now that is not the case.
They have made many changes which I don't understand and some I think are rather silly. -But- that is mainly cause I
have been ... out of the loop ... for a while.
Other things became more important ... God, Family, Holidays and of course ... work. Had a rash of service calls
and some of them were pretty interesting ... and frustrating. You know, some of those Windows Viruses can get really
hairy!! -But- ... that is another story. Back to this.
- This mess will cover all the Milestone Releases.
- Going to use sda8, sda9 and sda10 for SuSE 11.3 (Partitioning note...mainly to myself)
- They started getting late on the releases at Milestone 4 and now at M6 it is going to be a week late.
- My greatest disappointment so far is my inability to get VMware installed. Not sure who is at fault, openSuSE, VMware or just my stupidity. June 29, 2010
The download, M4, took a long, long time. Hope it is worth it.
Apr 30, 2010: Well, it was released yesterday but I didn't get it until today. The front page still says Milestone 5 but the download page says Milestone 6. Then from the forum it looks like some are not happy with the Network connections. Primarily the wireless ones. I don't use those so maybe this one will be better. I couldn't get a stable enough one to try my VMware in M5. Hopefully, M6 will be ok.
The other thing is the sound. IF I have Netscape in the Host going and I use a Flash routine that has sound, it disconnects the sound in VMware. I have only mentioned it in the Forums. IF it is still a problem here in M6 I will report it as a bug. This has happened before and Petr Vandrovec had some fixes.
Nope!! M6 was so bad that I didn't even get a chance to install VMware on it. Could not get a stable operation.
May 22nd, 2010 ... Brought down and installed M7. At first grins it is much better than M6!!
June 17th, 2010 On time with this one. Both them and me. openSuSE 11.3 RC1
I brought it down and I just burned it to a DVD. Now to re-boot into it and do a Full, Fresh Install in my third
boot Partition.
Hurrah!! It installed ok and looks good. I like the new graphics. Now for the acid test ... after some yard work.
Well maybe not ... it is over 100 degrees. (I live in Arizona)
Initially RC1 looks good. Once again my display is centered and looking good with the initial default settings. Not gona worry about the nVidia drivers unless I really need them. I really like the looks of my display with this nouveau driver. (nVidia 7300LE)
Bug 615446 Submitted It, RC1, did not recognize my Optical Drives. So, I could not install VMware.
Possible Fix: In theForums.
hal - Daemon for Collecting Hardware Information
HAL is a hardware abstraction layer and aims to provide a live list of devices present in the system at any point in time. HAL tries to understand both, physical devices (such as PCI and USB) and the device classes (such as input, net, and block) physical devices have. Besides it allows merging of information from device info files specific to a device. HAL provides a API through D-BUS for querying devices and notifying when things change. Finally, HAL provides some monitoring (in an unintrusive way) of devices. For further information, please refer to the HAL specification.
gimp-module-hal - The GNU Image Manipulation Program - module to detect input devices with HAL
The GIMP (GNU Image Manipulation Program) is a powerful image composition and editing program, which can be extremely useful for creating logos and other graphics for Web pages. The GIMP offers many of the tools and filters you would expect to find in similar commercial offerings and contains some interesting extras as well. The GIMP provides alarge image manipulation toolbox, including channel operations and layers, effects, subpixel imaging and antialiasing, and conversions- all including multilevel undo. The GIMP offers a scripting facility, but many of the included scripts rely on fonts that we cannot distribute. This package provides a module to detect input devices with HAL.
July 01, 2010 On time again!! RC2. Got it down on my machine and now we need to
install it. I am doing a FULL install and not an update.(this is out
on my third partion ... not my main one)
HoooRah!! HooRay!!! VMware will install and work!!!
First Boot
Well, at first boot I was disappointed in both this "new" release and myself.
It looked like I was booting up the old 11.2 version. No bells, no whistles... nada. Just a boot up to the same
old boring default desktop. Then I forgot to add/change the system specifics that I like. Don't know where my
head was, but it certainly was on vacation when I did this first, initial install. Needless to say, I am gona
do it again... with head attached!!
Ok. The M6 was a disaster, -but- M7 started out looking good. Better display and font. But, alas, there are problems.
The USB icon is missing and it is difficult to use the CD/DVD drives. Must go into root to get it mounted.
One of the messages I got at this initial boot was ... (this was in M1??):
... and I don't even know what it is! I've seen it talked about before, but I never really investigated anything about it. Guess that I need to goto that Web Site and find out what it is. Might even be something that I could find useful!!
Ok. In M7 I didn't get it. Got another message box when I signed on as my user:
KResource Migration Tool
Trying to migrate'DefaultAddress Book'...
Migration of 'DefaultAddress Book' succeeded.
and got the Akonadi when I signed on as root.
Don't know why I get this Migration everytime I boot into this new 11.3 ??? Should only be a one time thing ... shouldn't it??
Once again the items missing for Quanta. No File manager on task bar. The NTFS worked right from the start. Could see my Windows parts with no trouble. Other things missing on task bar.
ARRGGG!! Can't leave it unattended. Goes into Hyper Drive!!! What is that?? you ask? I've mentioned this elsewhere but I'll mention it here again. When my processor gets to working hard... used more than, I believe 92%... the fan really kicks in. Part of the design. You can really hear it. Glad it doesn't run that loud all the time.
Boot Up and Install -or- Update??
We have both -but- almost everyone seems to prefer a "clean" installation, myself included, or at least for the most part in the past. Now then, because of the "extras" in my current installation of SuSE 11.2, I really don't want to wipe my system and perform a Clean Install. I really should be able to just do an Update -and- if not ... then it shouldn't be offered.
These pics are from an Update of SuSE 11.2 in VMware -and- a new Installation of SuSE 11.3 in VMware.
The Begining Click-on for larger view |
This is the same for both - Update -or- Install. Just a Welcome to openSuSE. |
Installer Click-on for larger view |
Now is where you chose to Install
(-or- Boot from the Hard Disc cause you forgot to remove the DVD.)
Anyway, for both Install -and- Update choose Install.
|
Loading Click-on for larger view |
Same for both ... Need some directing software to do all this. Linux is loaded to Install or Update itself. |
Initializing Click-on for larger view |
Initializing Click-on for larger view |
This can take some time. Be patient. |
| License Click-on for larger view |
Same for both ... the license is presented. I don't see a problem with this at all. Just read it ... or not ... and then move on by clicking Next. |
Analyzing Click-on for larger view |
Probing Click-on for larger view |
Here we analyze the system and probe the hardware. |
Mode... Click-on for larger view |
...Install Click-on for larger view |
The first one shows the default setup. Now I have UN-checked the Automatic Configuration. Like to do it myself...thank you. After you finish with this screen it does some more Initializing. |
...Update Click-on for larger view |
This is very similar to the Install. Here I also UN-check the Auto-Configuration. |
Install Mode Click-on for larger view |
In Install mode it does some initializing. |
Update Mode Click-on for larger view |
Update Mode Click-on for larger view |
Update Mode Click-on for larger view |
In Update checks Online. Then you get a selection of the system to update. In this case it is only one, but can be more. After your selection it checks out the Repositories. Since this is an Update, they will change. |
Update Mode Click-on for larger view |
Because we are Updating the system, the old Repos are removed. New ones will be installed. |
Clock Set Click-on for larger view |
Clock Set Click-on for larger view |
Here you set you clock time and time zone. Not needed for Update. |
Desktop Select Click-on for larger view |
Desktop Software Selections. KDE is the default. Not needed for Update. |
Suggested Partitioning Click-on for larger view |
Partition Editing Click-on for larger view |
Here we have the suggested Partitioning. These may, or may not, fit your needs. Usually, for the Install, I must
change them cause of my multiple System Layout.
The example here is from my Virtual Machine install. My main machine is a lot different. Notice that there
are two buttons, one for creating and one for editing the Partions. Use Caution here. Normally, changes are not needed for Update. |
Install Mode.. Click-on for larger view |
..Create New User Click-on for larger view |
Maintaining my differences ... I UN-check the 'Use same Paasword for root' and the 'Automatic Login'.
I mean we want security ... not open the doors wide. This will only be in the Install. It won't change when you Update. So you will not be required to create a new User. Not needed for Update. |
root Password Click-on for larger view |
Now then, you will only get this screen if you canceled using your User Password as the root Password
in the previous Create User screen. This will only be in the Install. It won't change when you Update. |
Install Mode Click-on for larger view |
Initial Software screens for Install. |
Install Mode Click-on for larger view |
Install Mode Click-on for larger view |
Here in the Installation Settings you can make all kinds of changes... in Install. |
| Update Mode Click-on for larger view |
... and fewer in Update |
Booting Click-on for larger view |
 Click-on for larger view |
Click on Booting in Installation Settings to change some boot parameters. First screen shows the Boot Loader settings with openSuSE selected by default. Click on Edit and you will get the next screen where you can add some parameters. I have added 'nomodeset' with a lot of spaces so it stands out and you can more easily see it. Don't add all those spaces when/if you add this parameter. |
Software Click-on for larger view |
 Click-on for larger view |
 Click-on for larger view |
 Click-on for larger view |
| These are Software selections made using the Detailed operations. | |||
Software Accept Click-on for larger view |
Changes made Click-on for larger view |
Upon clicking on Accept after making all your selections you will probably gt a bunch of extras. Just Accept them also. You will then see the changes being made. |
Start it.. Click-on for larger view |
Click on Install ... twice. Once in the Main Screen and second in the Dialog that asks if you are sure. |
Both Click-on for larger view |
Cute screen ... just had to include it. Get it for both. |
Entertain Click-on for larger view |
Details Click-on for larger view |
Installation starts, and you get entertained unless you click the 'Details' Tab. Also some differences between Install and Update. In the details section you may see some deletions during the Update. |
Install Click-on for larger view |
System Re-Boots Click-on for larger view |
Finish installation and do the initial re-boot... |
Update Click-on for larger view |
System Re-Boots Click-on for larger view |
Finish installation and do the initial re-boot... |
Install Click-on for larger view |
 Click-on for larger view |
The system re-booting process ... |
Install Click-on for larger view |
 Click-on for larger view |
 Click-on for larger view |
 Click-on for larger view |
|
More Network ops from the Install...first we must set the Host Name and Domain Name (for our Local Area Network) This is only for Install. Update should keep the same values. |
|||
Install Click-on for larger view |
 Click-on for larger view |
 Click-on for larger view |
Here we test the Internet Connection and get the latest Release Notes. Wait for the Success. |
Install Click-on for larger view |
 Click-on for larger view |
I missed the first screen which said it was getting the Repositories. Then it asks if you want to Update? Which may sound strange in a New Install -but- we are getting some items that couldn't be included in the first place. Things like Flash and Microsoft Fonts. |
Install Click-on for larger view |
 Click-on for larger view |
 Click-on for larger view |
 Click-on for larger view |
| These are the acceptance screens ... for the Updates that you just said yes to. | |||
Receiving... Click-on for larger view |
Receiving... Click-on for larger view |
..Finish Patches Click-on for larger view |
| Here we are getting the Updates and Patches to apply to our new system. | ||
Install Click-on for larger view |
 Click-on for larger view |
Write out the System Configuration and then display the Release Notes. |
Install Click-on for larger view |
 Click-on for larger view |
 Click-on for larger view |
Here we take care of the Hardware ... which will probably be different on most machines ... only the same
on identical ones. Not needed for Update. |
Finished Click-on for larger view |
We are fini... all done ... finished. Now we can re-start and sign on to our account. |
Re-booting... Click-on for larger view |
...Sign On ... Click-on for larger view |
...Loading Click-on for larger view |
Re-Boot ... Sign On ... Load Up ... |
Welcome Click-on for larger view |
Desktop Click-on for larger view |
Get an Informative Welcome and then the Plasma Desktop. |
My plans were to have some screen shots of the Update -but- I couldn't get them ... yet.
However, as the previous sentence implies ... I Updated to 11.3 ... on my main system. Matter of fact I am signed on
to Win2K inside VMware inside the New openSuSE 11.3. I didn't have to install anything ... yet.
However, because I have an nVidia card and already had the nVidia driver installed, uhmm, for
openSuSE 11.2, I decided to NOT set the nomodeset and just see what an update would do. It goes to the nouveau driver.
No surprise really. Matter of fact it all looks ok and the system works ... except ... no 3D. And how do I know that??
Cause when I fired up VMware and booted up the system that was waiting... it complained. Evidently Vista was the last
system I had used in VMware -and- because I wasn't paying attention it was the default. It came up ok, just had a
VMware message that there was no 3d.
Speaking of which ... I noticed, while the update was going on that I got radeon and intel drivers loaded. Why??? I have an nVidia Card!! (have to investigate this further)
Well, these are the two drivers that got installed...plus the nVidia driver. Wonder how
much else got installed that didn't catch my eye??
- xorg-x11-driver-video-intel-legacy - Legacy Version of the Intel X.Org Driver
This package contains the legacy version of the Intel X.Org driver which does not require KMS.
- xorg-x11-driver-video-radeonhd - Driver for AMD GPG (ATI) r5xx/r6xx Chipsets
radeonhd is the X.org X11 driver for AMD GPG (ATI) r5xx/r6xx chipsets. Main development is driven by Novell, in close relationship to AMD which provides free documentation for the chipsets.
- xorg-x11-driver-video-nouveau - Accelerated Open Source driver for nVidia cards
The nouveau project aims to build high-quality, open source drivers for nVidia cards. (Nouveau [nuvo] is the French word for new.)
Quanta
Guess somebody can't get this right. I have all the required items loaded and still
get these warnings!!
Some applications required for full functionality are missing:
- KFileReplace [http://kfilereplace.kdewebdev.org] - search and replace in files will not be available;
- KXSLDbg [http://xsldbg.sourceforge.net/] - XSLT debugging will not be available;
- KImageMapEditor [http://www.nongnu.org/kimagemap/] - editing HTML image maps will not be available;
- KLinkStatus [http://kde-apps.org/content/show.php?content=12318] - link validity checking will not be available;
- Cervisia [http://www.kde.org/apps/cervisia] - CVS management plugin will not be available.
You may download the applications from the specified locations.
However, it is interesting to note that my settings from SuSE 11.2 are still in effect with the Quanta loaded here in SuSE 11.3.
Firefox Update(s)
23 Jul 2010 Well... I had 3.6.4 in SuSE 11.2, which got upped to 3.6.6 in the SuSE 11.3 Update and now on first use, after the Update, it says I should get the latest which is 3.6.8! My, my ... the changes are rapid.
Bug 625340 Submitted KDE Screen Locker (kscreenlocker), signal: Segmentation fault
I am putting this here cause I had Firefox going along with VMware and ... well ... just because.
Update: Appears to be a problem when using the nouveau driver. I have since installed the nVidia Driver and NOT
had the crash again.
nVidia - Graphics and Display
Alllllrighty! In the M7 version my display came up properly and I did not have to install the nVidia driver. ... yet. Same for RC1 and RC2.Preliminary Info
July 15,2010 Ok, we got the Public Release and want to install it. Comments in the Forums over the past weeks seem to indicate that you must include nomodeset (see explanation further down) in the boot parameters IF you want to install the nVidia native driver. Someone else mentioned that you needed to blacklist the nouveau driver. Weellll, let me say this about that. I did not have any trouble with the nouveau driver. In fact it appeared to work great. I am only loading/installing the nVidia driver ... well, because. (hmmmm...ok I later had trouble with 3D in VMware)To Blacklist the nouveau module...
Insert "blacklist nouveau" without the quotes at the end of "/etc/modprobe.d/50-blacklist.conf".
This Mode Set has to do with changes in the kernel to help with the graphics cards... but it is not finished and can cause problems on its own. KMS (Kernel Mode Setting)
Hopefully, this isn't to mumble jumbled and you can get something out of it. Tried to cover the during and after intall procedures.
A list of actions that could be used to install the nVidia drivers as openSUSE 11.3 is installed:
- Before installing openSUSE, download the latest nVidia Video driver to your system.
(you can still do it after, if necessary) - Installation Settings:
Click-on for larger viewDuring the install, when you have the option to change your booting setup, add nomodeset to the kernel load command for the normal load/start of openSUSE. This kernel startup option is already present for the Failsafe selection for openSUSE.
- Boot Loader Settings:
Click-on for larger view
Click-on for larger viewClick on Booting in the Installation Settings (in the previous step),
then Click on the check-marked line to hi-lite it IF not already,
Click on Edit at the bottom,
Add nomodeset to the Optional Kernel Command Line Parameters. - Software Selections:
Click-on each for larger viewDuring the Install you can pick additional Software to Install and/or Remove. Now then, since the nVidia driver will require a compile -AND- the source headers, we must install the 'C' compiler and the Linux Kernel source code. This is accomplished by clicking on Software in the Installation Settings and then selecting the 'C' compiler and the Kernel Source code. You may want to click on Details for more info.
-
restart/reboot.
- Boot Page:
Click-on for larger viewIn the grub OS selection add "3" (without the quotes) to the Boot Options At the bottom of the page. This will cause you to just go to the run level three terminal prompt. Command line entries.
The above and below is assuming that you DO NOT have the AutoLogin enabled. - Command Line:
Click-on for larger viewLogin in as root and change to the /home/user/Downloads folder... or the one where you have saved the nVidia driver. - nVidia Install:
Click-on for larger viewRun/Install the NVIDIA video driver using:
"sh ./NVIDIA-Linux-x86_64-256.35.run -q"
and answer all questions as appropriate for your system.Ok now. We had a problem. /usr/lib/xorg/modules/extentions/libglx.so is not a symbolic link. The nVidia Install aborted and unistalled itself. However, upon looking in the dirs that were specified, I found that a link had been created. Possibly the timing was not correct. Since it is now there, we will try the nVidia Install again.
Ok. Running it again did not get the above error -but- it is not running either. Must be some more to do. In KDE in Kickoff (kmenu) in Search, nvidia was typed and Enter key hit. Got the following:
You do not appear to be using the NVIDIA X driver.
Please edit your X configuration file (just run `nvidia-xconfig` as root),
and restart the X server.
Reference: Lots of info - (http://www.sabi.co.uk/Notes/linuxNVIDIA.html) Unfortunately, it is XFree86.
Ooooopss... I missed one by one of our own:
(http://forums.opensuse.org/english/information-new-users/unreviewed-how-faq/441889-nvidia-newbies-part-1-a.html)
- Generate a default xorg.conf with nvidia-xconfig
Ok. nvidia-xconfig executed as root:
dusty-tr2:/home/ctaylor # nvidia-xconfig
Using X configuration file: "/etc/X11/xorg.conf".
Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup'
New X configuration file written to '/etc/X11/xorg.conf'
- Open /etc/sysconfig, select System, select kernel
and set NO_KMS_IN_INITRD to yes.
Now select Bootloader, select DEFAULT_APPEND, and enter nomodeset in the parameters on the line. See above if you missed or forgot to "Blacklist nouveau" in 50-blacklist.conf. - IF you made the above changes inside Yast2, then it ran SuSEconfig for you. If you made them outside of Yast2 then you will have to Run SuSEconfig.
- Type in reboot at terminal prompt to restart the system with the new video driver.
After OS Installed
The following little blurb is not finished...yet. It involves installing the driver
AFTER the OS is installed.
Well, it is finished.
- ctl-alt-F1 (get in terminal mode)
Weellll... this didn't work. On the Ctl-Alt-F1 I got an unreadable, scrambled, mushed screen. Ctl-Atl-F7 got me back to a readable GUI where I am now using Quanta to make this note. Guess we will reboot and go into command line mode from the Boot Page as described above.
-But- first I think that I need to set 'nomodeset' and 'NO_KMS_IN_INITRD' to 'yes'. - ReBoot the System.
- At the Boot Page enter 3 on the 'Boot Options' command line nad hit Enter. This will start you at the commandline in run level 3.
- sign on to root
- cd to the dir that you have the nVidia driver in.
- sh NV*.rub -q (execute the nVidia script)
- Now then, you can try running nvidia-xconfig now -but- I suspect you may have to re-start the system first and then stop at the Boot Page again and enter root at run level 3.
- Enter 'nvidia-xconfig' to create an xorg.conf file.
- Reboot the system.
- In KDE in Kickoff (kmenu) in Search, type nvidia and hit the Enter key. You should get the nvidia server settings dialog. Here you can set your resolution, and view a bunch of other info.
The following, as of 23 May 2010, are for the versions prior. Left here for reference. I have included some comments from the OpenSuSE Forums concerning these drivers. They don't really have an nVidia driver for this kernel version -but- they have made BIG ... Gigantic ... improvements in the default. Before I was always getting a display that was shifted about 1/4 inch to the right in Graphics mode and then text mode was to far to the left. Right now in this version they both look OK.
A Warning that can be received:Now the following was borrowed/stolen from the OpenSuSE Forums... and the comments are from user oldcpu. They were similar to my findings so I have included them here. Plus he has some good info that I don't want to loose.
================ WARNING WARNING WARNING WARNING ================
This server has a video driver ABI version of 7.0 that this
driver does not officially support. Please check
http://www.nvidia.com/ for driver updates or downgrade to an X
server with a supported driver ABI.
A possible fix:
Was able to work around this problem by adding the following section to /etc/X11/xorg.conf:
Code:
Section "ServerFlags"
Option "IgnoreABI" "True"
EndSection
Summary
Thus far, for my newer PCs, 11.3 M7 is positive. For my older PCs, it has problems due to
- nouveau driver does NOT like my older nVidia hardware
- kernel still does NOT like my older Intel i855GM graphics
11.3 Predictions
Based on this (and with my still having one PC left to test) I predict that for 11.3 GM in July (unless there are major changes between now and then) we will see:
- ATI/radeon users with legacy hardware noting this 11.3 release is superior to 11.2 and overall a better release (albeit not perfect).
- nVidia users with old hardware may be very upset, as the nouveau driver does not work well for them, and these users will be forced to boot in safe settings/fail safe, until they can configure the "nv" or "vesa" drivers better, and until they can install the proprietary nVidia driver (where I note there is NOT yet a proprietary legacy nVidia driver yet for the 2.6.34 kernel).
- nVidia users with relatively moderate-to-new graphic hardware will be ok with the nouveau graphic driver.
- Intel drivers will be a mixed lot. Those with the newer Intel hardware (that comes with i3 and i5) will be happier, as that hardware does NOT work well on 11.2. But users of older Intel graphics (such as in my Intel i855 GM) will continue to be dissatisfied.
More from oldcpu:
Further to this, on this sandbox PC of mine (an old 32-bit AMD Athlon-1100 w/1GB (MSI KT3 Ultra motherboard) w/AGP
nVidia GeForce FX5200 graphics) I took a look in more detail at Software.openSUSE.org to see if I could get sax2
and I did not like what I saw. So I decided to stop wasting my time on the "nv" driver, and I went ahead and
installed the proprietary nVidia legacy 173.14.25 graphic driver "the hardway" (which is not hard). In doing this
I booted to run level 3 without the "nomodeset" boot code. After running the proprietary driver ".run" file, I
built the custom xorg.conf with the proprietary "nvidia-xconfig" tool. Restarted to run level-3, and then booted
with "startx -- -ignoreABI". Since the 173.14.25 graphic driver is not yet ready for the 2.6.34 kernel ( ? ) ,
experience with earlier 11.3 milestone releases taught me this was necessary.
For some reason, this proprietary graphic driver install messes permissions on audio, and hence I had to add
regular users to group audio to get sound functioning for regular users. (after which a complete log out of Linux
was necessary for settings to be applied)
But once that was complete, I had 1920x1200 graphics, with sound, functioning. I changed the /boot/grub/menu.lst
file, replacing "nomodeset" with "3".
And this from user confused:
For example, to generate a new xorg.conf:
Login to a console as ordinary user and su to root. If not already, get to runlevel 3 by entering init 3 and then pressing enter again. Enter the command
Code:
Xorg -configure
It will place the file xorg.conf.new into the directory /root. It can be edited, then moved to become the file /etc/X11/xorg.conf. Then try to achieve runlevel 5 by entering init 5.
What is NoModeSet: The newest kernels have moved the video mode setting into the kernel.
I borrowed/swiped this explanation from:Sugar Labs
It comes down to different computers having different graphics cards (or the equivalent built onto the
motherboard or into a laptop). They all can draw pretty pictures. However, except for really basic
(read as slow) drawing, how the software needs to talk to the card is different for every card. In the
Windows world, this means you need different graphics drivers for different cards. The issue here is that
some new software/drivers for Linux which do something called "kernel mode setting" for graphics cards
haven't been sufficiently tested/developed for the particular cards with which you are having problems.
Specifying 'nomodeset' when the system boots basically tells the system to use an older set of software/drivers
which does work (but may be slower or have some other issues that people would like to eliminate).
Networking - Mainly Local
Some changes are needed for this local operation. The httpd.conf file and the
mod_userdir.conf file.
In the httpd.conf ... add the Include for mod_userdir.conf and the other changes.
I am allowing FollowSymLinks cause ... I have a SymLink to my local WebPages over on a Windows drive
so I can Edit and View in both Systems. (Dual Boot)
# added 13 Jul 09
Include /etc/apache2/mod_userdir.conf
# forbid access to the entire filesystem by default
<Directory />
Options Indexes FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Allow from dusty-tr2.TRComputing
</Directory>
... and the mod_userdir.conf ... un-comment the UserDir:
# the UserDir directive is actually used inside the virtual hosts, to # have more control UserDir public_html
In order to run a local Network, you need apache2(HTTP daemon) and
DNS(Domain Name Server) installed -AND- running. They weren't...running.
In this version, SuSE 11.3, apache2 and dnsmasq are started in System Services in YAST.
After this initial start -and- configuration of the edit levels, they start at each boot-up.
You should also have a hosts file and do not allow dhcp to change it ... IF ... you have special names that
you want to keep using. IF you are interconnecting with some Windows machines you also need Samba which
involves smb(Samba SMB/CIFS file and print server) and nmb
(Samba NetBIOS naming service over IP).
(These are not installed by default. You must
specifically install them.)
Hot Digity Dog!! The VMware Network Operations are back to being fast again. Previous versions of openSuSE 11.x were slow. Here in the Final Release of version 11.3 they are smokin' again.
TopM7 Boot Up
Ok. At first grins it looks and acts much more stabilly. Quanta is again claiming the missing components that I did install ... at the initial installation. Also missing is the little USB icon that tells me my CD/DVD's and Mem Sticks are loaded. Other than that it looks pretty good. Haven't tried VMware yet, but that is next on my list.
June 08, 2010 I brought down a fresh copy of M7. The version I had downloaded before was from the download page that 'said' it was M6 but when you clicked on the download it was openSUSE-DVD-Build0625-i586.iso, which is 11.3 M7. The download page now has all the proper markings for M7 and I have gotten a copy from it. Hopefully this will get a matching kernel and source headers.
Well, after this new installation my sound works. However, still do not have the USB
notification in the Task Bar. And I placed the VMware disc in one of my optical drives. Opened 'MyComputer'
and saw it listed. Clicked on it and got the following message:
There is no application installed that can open the type block device (inode/blockdevice).
Do you want to try to install one?
Had three choices: Checkbox 'Do not ask again' or 'Install' or 'No'. I chose Install... It then looked for the
software to install and could not find it. I was then instructed to See http://help.opensuse.org/ksuseinstall
for details and asked if I wanted to configure my repositories. Hmmmmm... this is normally done on the initial
install. Ok let's say yes.
Allllrighty. It makes me sign on as root, then opens Yast2 to the configured Repos.
Ok, I cheated and used zypper to get the same list I was shown in Yast2 so I could list them here. They are:
# | Alias | Name | Enabled | Refresh --+-------------------------------------+-------------------------------------+---------+-------- 1 | Updates for openSUSE 11.3 11.3-1.59 | Updates for openSUSE 11.3 11.3-1.59 | Yes | Yes 2 | openSUSE-11.3 11.3-1.59 | openSUSE-11.3 11.3-1.59 | Yes | No 3 | repo-debug | openSUSE-11.3-Debug | No | Yes 4 | repo-non-oss | openSUSE-11.3-Non-Oss | Yes | Yes 5 | repo-oss | openSUSE-11.3-Oss | Yes | Yes 6 | repo-source | openSUSE-11.3-Source | No | YesNow according to what I know and have learned, the code needed should be in one of the above repos. Ok, let's get out of my area and into root to see if we can then read the disc ... like it was on the previous load.
Ok. Over in root and the first thing that we do is change the background. I like to know definately that I am in root when I am there. So I use a Red KDE Gear background. (I copy it from release to release.)
In root Alllrighty! Another good point. File manager is back on the task bar. And in using it I find 'nothing' in media or mnt point. Once again we click on 'My Computer' and find that there is something in the DVD drive. It is: VMware-Workstation-Full-7.0.0-20. Hovering over it shows: /dev/sr0 block device Clicking on it and once again it asks if I want to install the block device.
TopVMware
July 16, 2010 Yipee and Hooray!! Got the Public Release
-AND- VMware Installs and works under the latest and greatest openSuSE 11.3.
(Oh Darn! After all my ranting and raving on how
great VMware is in the latest release I find there are troubles. Seems that RC2 is the only one that VMware can find
the kernel header files on. If you 'Update' from RC2 to the new Release it will also work. -But- IF you do a FULL
clean install ... VMware can not find the headers and therefore can not get compiled. Installed but no worky. This
is as of 30 July 2010.)
Side Note: VMware DVD Guest Update boot. I wanted to get some screen pics of the Update Process and was having a hard time getting VMware to boot from the Update DVD. Found that I must get into the Virtual Machine BIOS and change the settings. This can prove to be tricky. First you have to obtain focus of/for the Virtual Machine -and then- hit the F2 key before it passes by. It is doable and probably wouldn't be so bad if I canceled that dialog that tells me about my USB connections... but I like it and with patience, it can be done.
May 26, 2010: Well, it installed ... sorta. I was able to install VMware -but- I could not get it setup cause ... ta, ta, da, dahhh ... the 'C' header files did NOT match the running kernel. So, I will probably have to wait till the released version is out and everything is supposed to match. I went through all this with 11.2 and had continuous compile failures... until the released version.
June 16, 2010 Here it is the day before the release of RC1 and I just was able to get VMware loaded again. Still not clear on the DVD portion. I had to go into MyComputer, Right Click on the CD/DVD drive, select mount, then open a Terminal Window and finally execute the script. It claims to have installed. Now to see if I can run it.
Nope!! Said the headers did not match. Ok. Let's build one here:
Most, if not all of this was taken from:
Configure, Build and Install a Custom Linux Kernel By: sgt-d
cd /usr/src
cp -a linux-2.6.34-9 linux-my
cd /usr/src/linux-my make clean make mrproper
make cloneconfig
Note: The 'make cloneconfig' command copies your currently running kernel configuration to:
/usr/src/linux/.config
make xconfig
This will open the configuration screen so we can begin making changes. Please note, the current options that you see checked are what you kernel is currently using... this information was supplied when we used 'make cloneconfig' (above).
I had to install some more of QT3 in order to use this. I say more cause QT3 was installed but when I tried to run this it complained about it not being installed.?. Anyway, I didn't write down what I had to install -but- what I did was make some logical guesses and then when I clicked on accept a whole boat load of items got added. Must have been correct cause now it works.
Make sure to change the "Local Version Release String"!
Changing the release string is extremely important. If you don't change it, your new kernel and modules will overwrite the '-default' kernel and modules. We do NOT want that to happen. I used '-cmt' for my release string, so when I was done building and installing, my kernel and modules had a '-cmt' suffix, not '-default'.
This is found under 'General setup'. If you've never used this before it can be tricky. Changing the data item is accomplished by first clicking on 'General setup' then double clicking on 'Local version - append to kernel release: -9-desktop'. This will present the Data item at the bottom of the 'Option' section. Change 'desktop' to your own name, in my case it is cmt, and then hit Enter. Now, make more changes and/or save the configuration.
Example:
vmlinuz-2.6.34-9-cmt
In xconfig or menuconfig:
Change all settings needed.
General setup Local version - append to kernel release - Double click on this to change it - Do NOT skip this step! - Enter a 'dash' (-) and a string value, eg: -cmt or -test
Make sure that you save the config. Before exiting xconfig.
Make a backup of your kernel configuration:
cp .config .config.bak
The only thing the next commands do is verify that a unique release string is being used. Now then, it is said that they ARE NOT NEEDED and will cause problems if used. Others say things are fine. Execute at your own risk or skip to the Build.
This first time, I am going to skip them. If it doesn't work then I repeat and include them. Well, changed my mind. I looked in the Makefile and found the kernelrelease is created by make prepare. Since we just changed it ... we then need to run the following two commands..??..
make prepare make kernelrelease
Ok. I am at the point just before the 'Build' of the kernel. Everything should be ok. Since all the configs and sources should be correct AND the ones the current kernel is using, I therefore should be able to get the VMware modules to compile. (I didn't change the -9-desktop to -9-cmt)
dusty-tr2:/usr/src/linux-my # make kernelrelease 2.6.34-9-desktop dusty-tr2:/usr/src/linux-my # dusty-tr2:/usr/src/linux-my # uname -a Linux dusty-tr2 2.6.34-9-desktop #1 SMP PREEMPT 2010-06-03 18:33:51 +0200 i686 i686 i386 GNU/Linux dusty-tr2:/usr/src/linux-my #
- Build -
I included the 'time' command to see just how long it takes.
time make
This will build the kernel and all modules and it will take some time to complete. The build process can take anywhere from 60+ to 120+ minutes.
- Install -
Everything was built in the previous step, now we have to install it.
We are down to two final commands...
Install the modules:
make modules_install
Note: 'make modules_install' will install modules to:
/lib/modules/2.6.34-9-your_release_string
Example:
/lib/modules/2.6.34-9-cmt
Install the kernel:
make install
- Confirm and Boot -
Verify that the new /boot/grub/menu.lst looks correct, example:
Note: Do NOT use this info in your menu.lst, this is just an example...
title openSUSE 11.3 [cmt] - 2.6.34-9 root (hd0,1) kernel /boot/vmlinuz-2.6.34-9-cmt root=/dev/hda1 vga=0x31a resume=/dev/sda1 splash=verbose showopts initrd /boot/initrd-2.6.34-9-cmt
Take a quick look at your /boot directory/partition and make sure you see your new '-release' kernel, system map and initrd there, example:
/boot/initrd-2.6.34-9-cmt /boot/System.map-2.6.34-9-cmt /boot/vmlinuz-2.6.34-9-cmt
If your menu.lst file looks good, and you see your new '-release' files (shown directly above) in /boot, restart your computer and boot to your new custom kernel!
I just hate being made a fool of... especially by a computer. Don't know whether I am holding my tongue on the wrong side of my mouth, or what, but I can not get VMware to see/find the proper header files. Even though I just built a kernel with them!!!
External Boot-up
From the forums, a reply by jdmcdaniel3 to suse_tpx60s:
Setting up SuSE externally so you don't mess up your main machine.
You could always consider loading openSUSE 11.3 on an external USB hard drive,
that�s what I have done and it leaves the internal system untouched. Of course, first you need to
have such a hard drive which has 40 GB of free space to use for the install. You need to understand
that by default, openSUSE is wanting to install the grub menu into the MBR of that original boot drive.
So, to install openSUSE on an external USB hard drive, you need to do the following:
- Tell your computer BIOS to boot from your external USB (or eSATA) hard drive. (I think this might depend on your PCs capabilities...depending on its age.)
- Install openSUSE & its SWAP on primary partitions on the external hard drive.
- Install Grub onto the openSUSE partition and not the MBR.
- Install Generic MBR on external hard drive.
- Inform Grub that the external hard drive is the first boot drive (it can not guess this since you did not boot from it in the first place).
- Designate the openSUSE partition as the Active or booting partition.
- Make sure that nothing is installing on the internal hard drive.
That is it. Do this a couple of times and loading openSUSE on an external USB hard drive will be as natural as riding a bicycle. I use this method so I can test openSUSE on any computer that I want, including computers I have no intention on using openSUSE after the testing is done.
Thank You,
Borrowed/stolen from: Suite101
System BIOS Limitations And The Need For Master Boot Record Information
Many System BIOS Setups (older versions) in PCs do not have support for using a USB storage device
as a secondary booting option. But some/most of the latest BIOS do have this option.
When a system boots, it is the system BIOS program that runs first. After doing the preliminary checks,
it gets ready to load the Operating System; for that, it looks for Master Boot Record (MBR) information
inside the computer. This is (normally) available in the C partition of the Internal Hard drive. Just in
case the internal Hard disk has failed to run, BIOS programs will look for the next device (like a floppy
drive or a CD drive or another internal hard disk drive � depending on how the BIOS has been set up) for the MBR.
If the BIOS program can not accept a USB Storage Device (like the external had disk) or if the external
drive can not/ does not store the MBR, it can not function as the booting device. That is the simple reality.
However, booting of Linux Ubuntu (and openSuSE) operating system from external USB drives seems quite possible and the
procedure involved (described above) for this purpose is also, reportedly, easy and straightforward.
Is There an "Unofficial" Way Out?
Curious IT experts will always look for unofficial channels to circumvent such limitations to find ways of overcoming such challenges. But from the various discussion forums and websites available in the Internet, it looks there is no sure fire way existing currently to make the external hard disks bootable for Windows.Windows Operating Systems Do Not Support Booting From External Hard Disk
Microsoft Win XP or Vista does not, at present, support booting from an external hard disk.This means that the user cannot install the OS Software onto the External hard disk in a straight forward manner. For booting, a Master Boot Record (MBR) is needed. This must be available on the disk drive, and this includes external disk drives.
This facility is not offered by Microsoft, for the simple reason that it has the potential to encourage piracy.
Top
Super Grub
Thanks to a fabulous program called SuperGrub, you can still be able to boot back into your Linux System... after a screw up -or whatever- IF you haven't wiped the Disc. I am assuming that you have "accidentally" changed the MBR and this will help you get it back in order. This doesn't fix everything. You will still have to edit your "Main Grub" menu.lst to get all the ducks in line. But, like the author(s) said, this will teach you something about the booting process. I still have a lot to learn but, by guess and by golly, I got it to dual/triple boot again... without re-loading my Linux stuff.
I have used this a number of times in my Triple boot machine and it works wonderfully... at least as of today, 30 June 2010. The way things change I can't say after this date. Just try it.
TopStuff
Copyright © 2004-2010
All rights reserved.
