[opensuse] wierd boot-up problem
I run SuSE 10.2 together with MS Windows. The boot menu had SUSE 10.2 as the default, then Windows and then SuSE failsafe. After installing some files from madwifi, including three kernel files, I now have the boot menu showing two more versions of SuSE, and has the last of them set as the default! How do I change the situation so that SuSE 10.2 as originally installed is the default? - Best regards, Dennis J. Tuchler University City, Missouri 63130 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I run SuSE 10.2 together with MS Windows. The boot menu had OpenSUSE 10.2 as the default, then Windows and then OpenSuSE failsafe. After installing some files from madwifi, including three kernel files, have two new entries on the boot menu: Kernel 2.6.18.2-34-bigsmp Kernel 2.6.18.2-34-xen The last of these became the default. I changed the default back to the initial entry, but I wonder why the default changed and what these two new kernel entries are all about. I found no difference when I booted up with Kernel 2.6.18.2-34-xen, but when I booted with the previous kernel Kernel ... -bigsmp, the system simply rebooted. I'd appreciate an explanation of all this. -- Best regards, Dennis J. Tuchler University City, Missouri 63130 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I run SuSE 10.2 together with MS Windows. The boot menu had OpenSUSE 10.2 as the default, then Windows and then OpenSuSE failsafe.
After installing some files from madwifi, including three kernel files, have two new entries on the boot menu:
First of all, I don't think madwifi requires to install those 2 new kernels. Who or what told you to install those kernels?
Kernel 2.6.18.2-34-bigsmp
Some people are confused by the differences between the SMP and BIGSMP kernels included in SUSE Linux, and which one to use for their system. A quick look at the build configuration for both kernels shows several differences, but the most significant involves the supported amount of RAM and number of CPUs. The SMP kernel contains the following parameters: CONFIG_HIGHMEM4G=y CONFIG_NR_CPUS=32 ==> Thus allowing a maximum of 4G RAM and 32 processors. The BIGSMP kernel, however, has these: CONFIG_HIGHMEM64G=y CONFIG_NR_CPUS=128 Enabling support for 64G memory and 128 processors. ==> If a system has either more than 4G RAM or more than 32 processors, the BIGSMP kernel must be used to fully utilize the system.
Kernel 2.6.18.2-34-xen
A Kernel-xen is only needed if one wants to use vitualization, thus xen. In your case, I don't think you want to use this kernel, unless you really want to deal with virtualization. So, both new kernels are not needed in case you only want to get your wlan run properly.
The last of these became the default. I changed the default back to the initial entry, but I wonder why the default changed and what these two new kernel entries are all about. I found no difference when I booted up with Kernel 2.6.18.2-34-xen, but when I booted with the previous kernel Kernel ... -bigsmp, the system simply rebooted.
It's the policy in openSUSE 10.2 to make the last installed kernel the default kernel (entry). Thus, if the xen kernel was installed at last, it gets the new default entry (in boot menu).
I'd appreciate an explanation of all this.
I hope this explanation was satisfying.
-- Best regards,
Dennis J. Tuchler University City, Missouri 63130
Greetings, -- Alexander Osthof R&D SI Architecture Maintenance SUSE Linux Products GmbH, Maxfeldstr.5 D-90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) Phone: +49-911-74053-0 GPG 1024D/06EF2575 3362 3E18 9A21 5080 50F2 000C 7F04 A5B0 06EF 2575
On Wednesday 14 February 2007, Alexander Osthof wrote:
Some people are confused by the differences between the SMP and BIGSMP kernels included in SUSE Linux,
Yes, including ATI among others. When building drivers for ati cards you have to guess at which options to select, because they have nothing that directly compares to the suse naming conventions. -- _____________________________________ John Andersen
Alexander Osthof wrote:
I run SuSE 10.2 together with MS Windows. The boot menu had OpenSUSE 10.2 as the default, then Windows and then OpenSuSE failsafe.
After installing some files from madwifi, including three kernel files, have two new entries on the boot menu:
First of all, I don't think madwifi requires to install those 2 new kernels. Who or what told you to install those kernels? They were in the relevant directory and I could find no instructions or advice as to what to load and what not to load. I knew that one of the kernel patches had to be installed, but had no idea as to what the availability of the other kernel variants contributed. Indeed, I wrote to a listserv (or was it a newsgroup?) asking just this question, and received no answer.
Kernel 2.6.18.2-34-bigsmp
Some people are confused by the differences between the SMP and BIGSMP kernels included in SUSE Linux, and which one to use for their system. A quick look at the build configuration for both kernels shows several differences, but the most significant involves the supported amount of RAM and number of CPUs.
The SMP kernel contains the following parameters:
CONFIG_HIGHMEM4G=y CONFIG_NR_CPUS=32
==> Thus allowing a maximum of 4G RAM and 32 processors.
The BIGSMP kernel, however, has these:
CONFIG_HIGHMEM64G=y CONFIG_NR_CPUS=128
Enabling support for 64G memory and 128 processors.
==> If a system has either more than 4G RAM or more than 32 processors, the BIGSMP kernel must be used to fully utilize the system.
The system would not boot on the bigsmp kernel, but selecting it only caused the computer to reboot back to the system-selection screen
Kernel 2.6.18.2-34-xen
A Kernel-xen is only needed if one wants to use vitualization, thus xen. In your case, I don't think you want to use this kernel, unless you really want to deal with virtualization.
So, both new kernels are not needed in case you only want to get your wlan run properly.
The last of these became the default. I changed the default back to the initial entry, but I wonder why the default changed and what these two new kernel entries are all about. I found no difference when I booted up with Kernel 2.6.18.2-34-xen, but when I booted with the previous kernel Kernel ... -bigsmp, the system simply rebooted.
It's the policy in openSUSE 10.2 to make the last installed kernel the default kernel (entry). Thus, if the xen kernel was installed at last, it gets the new default entry (in boot menu).
I'd appreciate an explanation of all this.
I hope this explanation was satisfying.
I truly appreciate your information. Thank you!
-- Best regards,
Dennis J. Tuchler University City, Missouri 63130
Greetings,
-- Best regards, Dennis J. Tuchler 7330 Kingsbury Boulevard University City, Missouri 63130 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Alexander Osthof wrote:
I run SuSE 10.2 together with MS Windows. The boot menu had OpenSUSE 10.2 as the default, then Windows and then OpenSuSE failsafe.
After installing some files from madwifi, including three kernel files, have two new entries on the boot menu:
First of all, I don't think madwifi requires to install those 2 new kernels. Who or what told you to install those kernels?
They were in the relevant directory and I could find no instructions or advice as to what to load and what not to load. I knew that one of the kernel patches had to be installed, but had no idea as to what the availability of the other kernel variants contributed. Indeed, I wrote to a listserv (or was it a newsgroup?) asking just this question, and received no answer.
Kernel 2.6.18.2-34-bigsmp
Some people are confused by the differences between the SMP and BIGSMP kernels included in SUSE Linux, and which one to use for their system. A quick look at the build configuration for both kernels shows several differences, but the most significant involves the supported amount of RAM and number of CPUs.
The SMP kernel contains the following parameters:
CONFIG_HIGHMEM4G=y CONFIG_NR_CPUS=32
==> Thus allowing a maximum of 4G RAM and 32 processors.
The BIGSMP kernel, however, has these:
CONFIG_HIGHMEM64G=y CONFIG_NR_CPUS=128
Enabling support for 64G memory and 128 processors.
==> If a system has either more than 4G RAM or more than 32 processors, the BIGSMP kernel must be used to fully utilize the system.
The system would not boot on the bigsmp kernel, but selecting it only caused the computer to reboot back to the system-selection screen
Jep, that's right. Since I assume you are running a 32bit system with less than 4GB of RAM you won't need and must not use a bigsmp kernel. Your (installed) kernel-default is the one you want to use. If there are patches you have to apply, then download or install the sources of the kernel-default and apply the required patches on those sources. Then build and install this (modified) kernel. In your case, just deinstall those 2 wrong kernels (bigsmp and xen) by typing "rpm -e kernel-bigsmp" and "rpm -e kernel-xen" if you have installed them with rpm or yast.
Kernel 2.6.18.2-34-xen
A Kernel-xen is only needed if one wants to use vitualization, thus xen. In your case, I don't think you want to use this kernel, unless you really want to deal with virtualization.
So, both new kernels are not needed in case you only want to get your wlan run properly.
The last of these became the default. I changed the default back to the initial entry, but I wonder why the default changed and what these two new kernel entries are all about. I found no difference when I booted up with Kernel 2.6.18.2-34-xen, but when I booted with the previous kernel Kernel ... -bigsmp, the system simply rebooted.
It's the policy in openSUSE 10.2 to make the last installed kernel the default kernel (entry). Thus, if the xen kernel was installed at last, it gets the new default entry (in boot menu).
I'd appreciate an explanation of all this.
I hope this explanation was satisfying.
I truly appreciate your information. Thank you!
You're welcome :)
-- Best regards,
Dennis J. Tuchler University City, Missouri 63130
Greetings,
-- Best regards,
Dennis J. Tuchler 7330 Kingsbury Boulevard University City, Missouri 63130
If there are any questions left, feel free to ask. Have a nice evening, -- Alexander Osthof R&D SI Architecture Maintenance SUSE Linux Products GmbH, Maxfeldstr.5 D-90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) Phone: +49-911-74053-0 GPG 1024D/06EF2575 3362 3E18 9A21 5080 50F2 000C 7F04 A5B0 06EF 2575
Alexander Osthof wrote:
Alexander Osthof wrote:
I run SuSE 10.2 together with MS Windows. The boot menu had OpenSUSE 10.2 as the default, then Windows and then OpenSuSE failsafe.
After installing some files from madwifi, including three kernel files, have two new entries on the boot menu: First of all, I don't think madwifi requires to install those 2 new kernels. Who or what told you to install those kernels? They were in the relevant directory and I could find no instructions or advice as to what to load and what not to load. I knew that one of the kernel patches had to be installed, but had no idea as to what the availability of the other kernel variants contributed. Indeed, I wrote to a listserv (or was it a newsgroup?) asking just this question, and received no answer.
Kernel 2.6.18.2-34-bigsmp Some people are confused by the differences between the SMP and BIGSMP kernels included in SUSE Linux, and which one to use for their system. A quick look at the build configuration for both kernels shows several differences, but the most significant involves the supported amount of RAM and number of CPUs.
The SMP kernel contains the following parameters:
CONFIG_HIGHMEM4G=y CONFIG_NR_CPUS=32
==> Thus allowing a maximum of 4G RAM and 32 processors.
The BIGSMP kernel, however, has these:
CONFIG_HIGHMEM64G=y CONFIG_NR_CPUS=128
Enabling support for 64G memory and 128 processors.
==> If a system has either more than 4G RAM or more than 32 processors, the BIGSMP kernel must be used to fully utilize the system. The system would not boot on the bigsmp kernel, but selecting it only caused the computer to reboot back to the system-selection screen
Jep, that's right. Since I assume you are running a 32bit system with less than 4GB of RAM you won't need and must not use a bigsmp kernel. Your (installed) kernel-default is the one you want to use.
If there are patches you have to apply, then download or install the sources of the kernel-default and apply the required patches on those sources. Then build and install this (modified) kernel.
In your case, just deinstall those 2 wrong kernels (bigsmp and xen) by typing
"rpm -e kernel-bigsmp" and "rpm -e kernel-xen"
if you have installed them with rpm or yast.
After installing madwifi using Yast, I got an update message from my in Zen icon at the lower right part of the screen (KDE). Delighted that it was finally doing something (I had found updates using Yast that weren't noted by Zen), I told Zen to go ahead and correct things. I may have complicated matters a mite. When I did as you suggested, I got error messages: # rpm -e kernel-xen error: Failed dependencies: kernel(vmlinux) = 44ebeb27f25f7b59 is needed by (installed) madwifi-kmp-xen-0.9.2.1_2.6.18.2_34-0.1.i586 kernel(vmlinux) = 93376bd16ab33bbc is needed by (installed) madwifi-kmp-xenpae-0.9.2.1_2.6.18.2_34-0.1.i586 kernel-xen is needed by (installed) madwifi-kmp-xen-0.9.2.1_2.6.18.2_34-0.1.i586 #rpm -e kernel-bigsmp error: Failed dependencies: kernel(vmlinux) = bb95ba9d667bafff is needed by (installed) madwifi-kmp-bigsmp-0.9.2.1_2.6.18.2_34-0.1.i586 kernel(vmlinux) = 93376bd16ab33bbc is needed by (installed) madwifi-kmp-xenpae-0.9.2.1_2.6.18.2_34-0.1.i586 kernel-bigsmp is needed by (installed) madwifi-kmp-bigsmp-0.9.2.1_2.6.18.2_34-0.1.i586 So, do I just leave the tangle as is?
If there are any questions left, feel free to ask.
I probably will when I get my new WiFi card and try to install it :| -- Best regards, Dennis J. Tuchler 7330 Kingsbury Boulevard University City, Missouri 63130 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Mittwoch, 14. Februar 2007 18:33 schrieb Dennis J. Tuchler:
Alexander Osthof wrote:
Alexander Osthof wrote:
I run SuSE 10.2 together with MS Windows. The boot menu had OpenSUSE 10.2 as the default, then Windows and then OpenSuSE failsafe.
After installing some files from madwifi, including three kernel files, have two new entries on the boot menu:
First of all, I don't think madwifi requires to install those 2 new kernels. Who or what told you to install those kernels?
They were in the relevant directory and I could find no instructions or advice as to what to load and what not to load. I knew that one of the kernel patches had to be installed, but had no idea as to what the availability of the other kernel variants contributed. Indeed, I wrote to a listserv (or was it a newsgroup?) asking just this question, and received no answer.
Kernel 2.6.18.2-34-bigsmp
Some people are confused by the differences between the SMP and BIGSMP kernels included in SUSE Linux, and which one to use for their system. A quick look at the build configuration for both kernels shows several differences, but the most significant involves the supported amount of RAM and number of CPUs.
The SMP kernel contains the following parameters:
CONFIG_HIGHMEM4G=y CONFIG_NR_CPUS=32
==> Thus allowing a maximum of 4G RAM and 32 processors.
The BIGSMP kernel, however, has these:
CONFIG_HIGHMEM64G=y CONFIG_NR_CPUS=128
Enabling support for 64G memory and 128 processors.
==> If a system has either more than 4G RAM or more than 32 processors, the BIGSMP kernel must be used to fully utilize the system.
The system would not boot on the bigsmp kernel, but selecting it only caused the computer to reboot back to the system-selection screen
Jep, that's right. Since I assume you are running a 32bit system with less than 4GB of RAM you won't need and must not use a bigsmp kernel. Your (installed) kernel-default is the one you want to use.
If there are patches you have to apply, then download or install the sources of the kernel-default and apply the required patches on those sources. Then build and install this (modified) kernel.
In your case, just deinstall those 2 wrong kernels (bigsmp and xen) by typing
"rpm -e kernel-bigsmp" and "rpm -e kernel-xen"
if you have installed them with rpm or yast.
After installing madwifi using Yast, I got an update message from my in Zen icon at the lower right part of the screen (KDE). Delighted that it was finally doing something (I had found updates using Yast that weren't noted by Zen), I told Zen to go ahead and correct things. I may have complicated matters a mite. When I did as you suggested, I got error messages:
# rpm -e kernel-xen error: Failed dependencies: kernel(vmlinux) = 44ebeb27f25f7b59 is needed by (installed) madwifi-kmp-xen-0.9.2.1_2.6.18.2_34-0.1.i586 kernel(vmlinux) = 93376bd16ab33bbc is needed by (installed) madwifi-kmp-xenpae-0.9.2.1_2.6.18.2_34-0.1.i586 kernel-xen is needed by (installed) madwifi-kmp-xen-0.9.2.1_2.6.18.2_34-0.1.i586
#rpm -e kernel-bigsmp error: Failed dependencies: kernel(vmlinux) = bb95ba9d667bafff is needed by (installed) madwifi-kmp-bigsmp-0.9.2.1_2.6.18.2_34-0.1.i586 kernel(vmlinux) = 93376bd16ab33bbc is needed by (installed) madwifi-kmp-xenpae-0.9.2.1_2.6.18.2_34-0.1.i586 kernel-bigsmp is needed by (installed) madwifi-kmp-bigsmp-0.9.2.1_2.6.18.2_34-0.1.i586
So, do I just leave the tangle as is?
Nope, now I see your problem: You fetched the wrong package of madwifi. Those you fetched are for xen and bigsmp kernels. Therefore those 2 kernel are in dependancy with the madwifi package. Thus, deinstall the madwifi packages first, then the 2 wrong kernels. What you need is a package for kernel-default (e.g. madwifi & madwifi-kmp-default). Take a look at the openSUSE 10.2 DVD - if available - or the online sources of opensuse (download.opensuse.org).
If there are any questions left, feel free to ask.
I probably will when I get my new WiFi card and try to install it :|
-- Best regards,
Dennis J. Tuchler 7330 Kingsbury Boulevard University City, Missouri 63130
cu :) -- Alexander Osthof R&D SI Architecture Maintenance SUSE Linux Products GmbH, Maxfeldstr.5 D-90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) Phone: +49-911-74053-0 GPG 1024D/06EF2575 3362 3E18 9A21 5080 50F2 000C 7F04 A5B0 06EF 2575 "Float like a Butterfly, sting like a bee. Your hands can't hit what your eyes can´t see. Now you see me, now you don't, George thinks he will, but I know he won’t." Cassius Marcellus Clay (aka Muhammad Ali)
Dennis J. Tuchler wrote:
I run SuSE 10.2 together with MS Windows. The boot menu had SUSE 10.2 as the default, then Windows and then SuSE failsafe. After installing some files from madwifi, including three kernel files, I now have the boot menu showing two more versions of SuSE, and has the last of them set as the default!
How do I change the situation so that SuSE 10.2 as originally installed is the default?
You can configue the GRUB boot loader in Yast > System > Boot Loader. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Alexander Osthof -
Dennis J. Tuchler -
James Knott -
John Andersen