|
Bugzilla – Full Text Bug Listing |
| Summary: | Kernel selection during installation defaulting to 2.6.x bigsmp instead of default kernel | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Darren Clarke <mailcentre2> |
| Component: | Installation | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aj, forgotten_--EoyBps8f, locilka, rodschaffter |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Beta 2 Yast install log for PIII 850 Compaq Armada M700 | ||
|
Description
Darren Clarke
2007-08-24 09:06:36 UTC
I too had the bigsmp kernel install on my old Pentuium III 850 Compaq Armada M700 laptop. It sure boots up quick, and seems to work. However, when update was run, it installed the Xen kernel too. I also tried uninstsalling it and installing the default kernel, and afterwards there are no boot options for the kernel in /boot/grub/menu.lst, which results in it coming up in text mode as Darren noted. Adding "splash=silent showopts" will fix it. On a fresh install plus update, installing the default kernel alongside the bigsmp and xen kernels does put the correct kernel options in for all kernels. Please, attach YaST logs. Anyway, I think this is intentional (but without logs...). Created attachment 159971 [details]
Beta 2 Yast install log for PIII 850 Compaq Armada M700
Is "pcnet32 missing" also intentional or is the first comment wrong on that aspect? Kernel switch: PAE ProbeKernel determined: ["kernel-bigsmp"] Selecting 'kernel-bigsmp' as kernel package Packages for base kernel-bigsmp: ["kernel-bigsmp"] So it is intentional. Reassigning to jsrain to reevaluate (because he has implemented that) but I guess it works as expected. Where would I find the installation logs? "I guess it works as expected" Really? Could someone post the .config file for both the default kernel and the bigsmp kernel, because I have observed that certain modules are missing. Look at bug #298944. Again, the bigsmp kernel is shown to have missing components. If this is "expected", what does that say... 298944 is fixed, the configurations are the same. Both kernel-default and kernel-smp have pcnet32 as modules: bigsmp:CONFIG_PCNET32=m bigsmp:CONFIG_PCNET32_NAPI=y default:CONFIG_PCNET32=m default:CONFIG_PCNET32_NAPI=y rpm -ql kernel-bigsmp |grep pcnet32 /lib/modules/2.6.22.5-2-bigsmp/kernel/drivers/net/pcnet32.ko Darren, with Beta2 there should be the same modules. Here's a diff between the configs: --- default 2007-08-25 12:54:53.000000000 +0200 +++ bigsmp 2007-08-25 12:54:53.000000000 +0200 @@ -31,7 +31,7 @@ # # General setup # -CONFIG_LOCALVERSION="-default" +CONFIG_LOCALVERSION="-bigsmp" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_SUSE_KERNEL=y CONFIG_SWAP=y @@ -172,12 +172,13 @@ CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y +CONFIG_X86_CMPXCHG64=y CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_MINIMUM_CPU_MODEL=4 CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y -CONFIG_NR_CPUS=32 +CONFIG_NR_CPUS=128 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y # CONFIG_PREEMPT_NONE is not set @@ -207,10 +208,12 @@ CONFIG_DCDBAS=m CONFIG_DMIID=y # CONFIG_NOHIGHMEM is not set -CONFIG_HIGHMEM4G=y -# CONFIG_HIGHMEM64G is not set +# CONFIG_HIGHMEM4G is not set +CONFIG_HIGHMEM64G=y CONFIG_PAGE_OFFSET=0xC0000000 CONFIG_HIGHMEM=y +CONFIG_X86_PAE=y +# CONFIG_NUMA is not set CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y @@ -220,7 +223,7 @@ CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_SPARSEMEM_STATIC is not set CONFIG_SPLIT_PTLOCK_CPUS=4 -# CONFIG_RESOURCES_64BIT is not set +CONFIG_RESOURCES_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_NR_QUICK=1 CONFIG_HIGHPTE=y @@ -1553,6 +1556,7 @@ CONFIG_I2O=m CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y CONFIG_I2O_EXT_ADAPTEC=y +CONFIG_I2O_EXT_ADAPTEC_DMA64=y CONFIG_I2O_CONFIG=m CONFIG_I2O_CONFIG_OLD_IOCTL=y CONFIG_I2O_BUS=m (In reply to comment #7 from Darren Clarke) > Where would I find the installation logs? /var/log/YaST/ directory > "I guess it works as expected" > > Really? > > Could someone post the .config file for both the default kernel and the bigsmp > kernel, because I have observed that certain modules are missing. You have to distinguish between two different issues: 1.) Kernel selection during installation - based on features supported by processor, size of RAM, etc. 2.) Bugs in Kernel packages - such as missing modules or real bugs in Kernel itself YaST / Installation can always solve only case "1", the other issue must be reported, solved separately... (Er, the directory is '/var/log/YaST2/' sorry) I have an IBM thinkpad T43p single processor machine that default installed the bigsmp kernel. It also only has 1GB of memory. It has been decided to use the bigsmp kernel regardless the amount of memory or the count of CPUs. The only rule which defines which kernel will be used by default is the presence of the PAE extensions. I think this can be marked as fixed. The missing module are solved and the rest is intentional - and documented now in the release notes. After 10.3, let's discuss renaming kernel-bigsmp... |