i'm trying to fix my boot problem and so far booting from the install cd with test26.s works but i'd like to install the test26.s image to /boot so i can eliminate the cd for now while i figure out what's wrong. how do i do this? thank you in advance.

Mount the cd, ex: go to the cdrom, goto 'linux-2.6.13' dir, run and install from current directory, and install everything in the directory (kernel headers, source, alsa, etc.) That ought to get you going.
Then make sure lilo is installed. If not, run 'liloconfig'

Be aware that the 2.6.13 kernel in CD#2/testing/linux-2.6.13 is _not_ the same as the test26.s kernel you can install at install time. If you're using reiserfs, for example, you'll need to create an initrd or the kernel will be unable to mount your disk(s). See /boot/README.initrd for more information.

In one word: BULL.
I use reiserfs, and have had NO problems with it. I do not, and will not, use initrd. It's a kludge.Where do you get that from?
Just install it as I told you (As long as you selected the test26.s kernel at the end of the install, you will have no problems)

Allow me to offer, as evidence:

System 1, installed w/ 2.4 kernel, upgraded to 2.6.13 from CD#2:

bash-3.00$ ls -l /boot/vmlinuz-generic-2.6.13
-rw-r--r-- 1 root root 1492552 2005-09-04 00:15 /boot/vmlinuz-generic-2.6.13

System 2, installed using the test 2.6 kernel (ie the one on CD1):

bash-3.00$ ls -l /boot/vmlinuz
-r-------- 1 root root 3233958 2006-02-09 11:58 /boot/vmlinuz

On System 1, with the config from /proc/config on System2

bash-3.00$ diff /boot/config ./test26.s_config
4c4
< # Sat Sep 3 20:38:27 2005
---
> # Tue Sep 6 17:53:25 2005
707c707
< CONFIG_FW_LOADER=m
---
> CONFIG_FW_LOADER=y
776,777c776,777
< CONFIG_BLK_CPQ_DA=m
< CONFIG_BLK_CPQ_CISS_DA=m
---
> CONFIG_BLK_CPQ_DA=y
> CONFIG_BLK_CPQ_CISS_DA=y
779c779
< CONFIG_BLK_DEV_DAC960=m
---
> CONFIG_BLK_DEV_DAC960=y
785c785
< CONFIG_BLK_DEV_SX8=m
---
> CONFIG_BLK_DEV_SX8=y
855c855
< # CONFIG_BLK_DEV_SC1200 is not set
---
> CONFIG_BLK_DEV_SC1200=y
913,914c913,914
< CONFIG_SCSI_SPI_ATTRS=m
< CONFIG_SCSI_FC_ATTRS=m
---
> CONFIG_SCSI_SPI_ATTRS=y
> CONFIG_SCSI_FC_ATTRS=y
920,927c920,927
< CONFIG_BLK_DEV_3W_XXXX_RAID=m
< CONFIG_SCSI_3W_9XXX=m
< CONFIG_SCSI_7000FASST=m
< CONFIG_SCSI_ACARD=m
< CONFIG_SCSI_AHA152X=m
< CONFIG_SCSI_AHA1542=m
< CONFIG_SCSI_AACRAID=m
< CONFIG_SCSI_AIC7XXX=m
---
> CONFIG_BLK_DEV_3W_XXXX_RAID=y
> CONFIG_SCSI_3W_9XXX=y
> CONFIG_SCSI_7000FASST=y
> CONFIG_SCSI_ACARD=y
> CONFIG_SCSI_AHA152X=y
> CONFIG_SCSI_AHA1542=y
> CONFIG_SCSI_AACRAID=y
> CONFIG_SCSI_AIC7XXX=y
934c934
< CONFIG_SCSI_AIC79XX=m
---
> CONFIG_SCSI_AIC79XX=y
941,942c941,942
< CONFIG_SCSI_DPT_I2O=m
< CONFIG_SCSI_IN2000=m
---
> CONFIG_SCSI_DPT_I2O=y
> CONFIG_SCSI_IN2000=y
944,945c944,945
< CONFIG_MEGARAID_MM=m
< CONFIG_MEGARAID_MAILBOX=m
---
> CONFIG_MEGARAID_MM=y
> CONFIG_MEGARAID_MAILBOX=y
947,959c947,959
< CONFIG_SCSI_SATA_AHCI=m
< CONFIG_SCSI_SATA_SVW=m
< CONFIG_SCSI_ATA_PIIX=m
< CONFIG_SCSI_SATA_NV=m
< CONFIG_SCSI_SATA_PROMISE=m
< CONFIG_SCSI_SATA_QSTOR=m
< CONFIG_SCSI_SATA_SX4=m
< CONFIG_SCSI_SATA_SIL=m
< CONFIG_SCSI_SATA_SIS=m
< CONFIG_SCSI_SATA_ULI=m
< CONFIG_SCSI_SATA_VIA=m
< CONFIG_SCSI_SATA_VITESSE=m
< CONFIG_SCSI_BUSLOGIC=m
---
> CONFIG_SCSI_SATA_AHCI=y
> CONFIG_SCSI_SATA_SVW=y
> CONFIG_SCSI_ATA_PIIX=y
> CONFIG_SCSI_SATA_NV=y
> CONFIG_SCSI_SATA_PROMISE=y
> CONFIG_SCSI_SATA_QSTOR=y
> CONFIG_SCSI_SATA_SX4=y
> CONFIG_SCSI_SATA_SIL=y
> CONFIG_SCSI_SATA_SIS=y
> CONFIG_SCSI_SATA_ULI=y
> CONFIG_SCSI_SATA_VIA=y
> CONFIG_SCSI_SATA_VITESSE=y
> CONFIG_SCSI_BUSLOGIC=y
961,963c961,963
< CONFIG_SCSI_DMX3191D=m
< CONFIG_SCSI_DTC3280=m
< CONFIG_SCSI_EATA=m
---
> CONFIG_SCSI_DMX3191D=y
> CONFIG_SCSI_DTC3280=y
> CONFIG_SCSI_EATA=y
967,968c967,968
< CONFIG_SCSI_FUTURE_DOMAIN=m
< CONFIG_SCSI_GDTH=m
---
> CONFIG_SCSI_FUTURE_DOMAIN=y
> CONFIG_SCSI_GDTH=y
970c970
< CONFIG_SCSI_GENERIC_NCR5380_MMIO=m
---
> CONFIG_SCSI_GENERIC_NCR5380_MMIO=y
972,974c972,974
< CONFIG_SCSI_IPS=m
< CONFIG_SCSI_INITIO=m
< CONFIG_SCSI_INIA100=m
---
> CONFIG_SCSI_IPS=y
> CONFIG_SCSI_INITIO=y
> CONFIG_SCSI_INIA100=y
980c980
< CONFIG_SCSI_SYM53C8XX_2=m
---
> CONFIG_SCSI_SYM53C8XX_2=y
985c985
< CONFIG_SCSI_IPR=m
---
> CONFIG_SCSI_IPR=y
989,991c989,991
< CONFIG_SCSI_PSI240I=m
< CONFIG_SCSI_QLOGIC_FAS=m
< CONFIG_SCSI_QLOGIC_FC=m
---
> CONFIG_SCSI_PSI240I=y
> CONFIG_SCSI_QLOGIC_FAS=y
> CONFIG_SCSI_QLOGIC_FC=y
993,994c993,994
< CONFIG_SCSI_QLOGIC_1280=m
< # CONFIG_SCSI_QLOGIC_1280_1040 is not set
---
> CONFIG_SCSI_QLOGIC_1280=y
> CONFIG_SCSI_QLOGIC_1280_1040=y
996,1006c996,1006
< CONFIG_SCSI_QLA21XX=m
< CONFIG_SCSI_QLA22XX=m
< CONFIG_SCSI_QLA2300=m
< CONFIG_SCSI_QLA2322=m
< CONFIG_SCSI_QLA6312=m
< CONFIG_SCSI_QLA24XX=m
< CONFIG_SCSI_LPFC=m
< CONFIG_SCSI_SYM53C416=m
< CONFIG_SCSI_DC395x=m
< CONFIG_SCSI_DC390T=m
< CONFIG_SCSI_T128=m
---
> CONFIG_SCSI_QLA21XX=y
> CONFIG_SCSI_QLA22XX=y
> CONFIG_SCSI_QLA2300=y
> CONFIG_SCSI_QLA2322=y
> CONFIG_SCSI_QLA6312=y
> CONFIG_SCSI_QLA24XX=y
> CONFIG_SCSI_LPFC=y
> CONFIG_SCSI_SYM53C416=y
> CONFIG_SCSI_DC395x=y
> CONFIG_SCSI_DC390T=y
> CONFIG_SCSI_T128=y
1012c1012
< CONFIG_SCSI_NSP32=m
---
> CONFIG_SCSI_NSP32=y
1064,1065c1064,1065
< CONFIG_FUSION_SPI=m
< CONFIG_FUSION_FC=m
---
> CONFIG_FUSION_SPI=y
> CONFIG_FUSION_FC=y
1105c1105
< CONFIG_I2O=m
---
> CONFIG_I2O=y
1107c1107
< CONFIG_I2O_CONFIG=m
---
> CONFIG_I2O_CONFIG=y
1109,1112c1109,1112
< CONFIG_I2O_BUS=m
< CONFIG_I2O_BLOCK=m
< CONFIG_I2O_SCSI=m
< CONFIG_I2O_PROC=m
---
> CONFIG_I2O_BUS=y
> CONFIG_I2O_BLOCK=y
> CONFIG_I2O_SCSI=y
> CONFIG_I2O_PROC=y
2496c2496
< CONFIG_EXT3_FS=m
---
> CONFIG_EXT3_FS=y
2500c2500
< CONFIG_JBD=m
---
> CONFIG_JBD=y
2503c2503
< CONFIG_REISERFS_FS=m
---
> CONFIG_REISERFS_FS=y
2507c2507
< CONFIG_JFS_FS=m
---
> CONFIG_JFS_FS=y
2517c2517
< CONFIG_XFS_FS=m
---
> CONFIG_XFS_FS=y
2537c2537
< CONFIG_ISO9660_FS=m
---
> CONFIG_ISO9660_FS=y
2540,2541c2540,2541
< CONFIG_ZISOFS_FS=m
< CONFIG_UDF_FS=m
---
> CONFIG_ZISOFS_FS=y
> CONFIG_UDF_FS=y
2547,2549c2547,2549
< CONFIG_FAT_FS=m
< CONFIG_MSDOS_FS=m
< CONFIG_VFAT_FS=m
---
> CONFIG_FAT_FS=y
> CONFIG_MSDOS_FS=y
> CONFIG_VFAT_FS=y
2552c2552
< CONFIG_NTFS_FS=m
---
> CONFIG_NTFS_FS=y
2604c2604
< CONFIG_EXPORTFS=m
---
> CONFIG_EXPORTFS=y
2755c2755
< CONFIG_ZLIB_INFLATE=m
---
> CONFIG_ZLIB_INFLATE=y
2760a2761,2763
>
> --=_43f11534.OBW2rVI8BKOWEY6a+G0XoGQlSyWJEN92NYpcVdPdKUAFAneJ--
>
bash-3.00$

I'm writing this from a system that I just installed 2.6.13 from CD2 w/test26.s and reiserfs, installed as I said. No problems. Boots fine. Runs fine. No change from default config in /boot, but, as I said, you have to install the 26test.s kernel at the end of install, or, as happened to you, it does not boot reiserfs. You obviously messed up at the end.

No, I installed with the 2.4 and then upgraded at a later date using the packages on CD#2. At the time I didn't know you could install a 2.6 kernel during the main system install and then just install the modules from cd2 on first boot. Does that count as messing up?

As you can see from the diff above, though, the 2 are different. Specifically, the 2.6 kernel on CD1 includes ResierFS, the 2.6 kernel on cd2 has it as a module, necessitating the initrd.

Anyway, this really isn;t the place for a flamewar. I'll shut up now.

So if I started with the 2.4 default kernel and then upgrade to 2.6 with CD#2, I would need to do some tweaking. However, installing test2.6 at the end of installation and then getting the modules from CD#2, should require no tweaking. Ok, my system is currently running the default kernel. I'm going to follow the tip on installing 2.6 from CD#2 and see what happens.

Dachy, what's your progress so far?

cwwilson721 -

How exactly is initrd a kludge?

The README states that if you're using ext3, reiserfs before installing 2.6.13 that you will require an initrd. However, I'm using ext3 as my filesystem and didn't have to create an initrd. I think YMMV can applied to this dilemma.

Your Mileage May Vary.

By the way, with the 2.6.13 my laptop boots much faster. I love it.

see, the thing is, i installed using test26.s then i later installed the modules from the disc. later on i modified my rc.modules and then i had a problem at boot (a kernel panic that wouldn't let me boot) so now i need to go back and install just the test26.s image in /boot, that is the only thing i am trying to do. i do not need to install the modules again... or is that the only way this is possible?

i will do this
1.copy image and System.map it is tehre in the first cd of 10.2 /mnt/cdrom/kernels/test26.s/
(rename both files like bzimage to test26.s )
2. put these in /boot make a symlink for sytem.map
3. edit lilo and run lilo
4. installpkg /mnt/cdrom/linux-2.6.13/kernel-modules-2.6.13-i486-1.tgz (2nd cd rom)
hope will run

also all filesystem are built in in test26.s kernel so no worry, best of luck

I have upgraded the kernel several times, broke it a few, and redid it a few more.



just copy the kernal and map from disk 1, remove the modules for the 2.4, install the modules from 2.6 (from disk 2), and run lilo.



If you screw it up totally, you can boot to the cd and chroot to your install to fix it. no need to reinstall the entire system.



you may find the section on kernel on the slackware website to be of use, i generally use it as a refereance if its been awhile and i start forgetting commands.

...additional question.

It seems that some of you succeeded installing the test26.s kernel. I tried that, too, but failed.

At the end of the install procedure I chose to install the kernel from the installation CD. After that, the installer advised me to reboot. The reboot startet, I saw the lilo screen and was able to choose Linux or Windows. I selected Linux, and for a moment everything looked ok, with the familiar dots starting to fill a line and a couple of text messages scrolling into the screen.

However, at that stage the screen turned black. No progress, no error message. Weird!

BTW, I installed LILO to the MBR because the Win XP bootloader was already there on that machine, so it was easier to install LILO there, too than anywhere else.

So, does anyone have a clue what might have been wrong?

gargamel

that means ur kernel is uncomprezing (/ -mentioned in lilo is ok)
but the problem may be with file system support or disk support,
what is the ur root file system?
what disk it is sata or scsi ...?i hope all these are enaled in kernel as built in.
type #uname -r (or uname -a)and c what kernel u r using

file system...may be problem u choosed reiserfs and the support may not b there in kernel.. let us c
suse is working fine right?