On Tue, 25 Jul 2006 03:52:38 -0700, Steven J. Hathaway wrote:
> "Steven J. Hathaway" wrote:
>
>> I wish to rebuild the bootdisk "bare.i" and the rootdisk "install.1"
>>
>> The symptom: CDROM boots, but cannot be mounted once the kernel
>> is resident and activeated. The ramdisk filesystem is OK, but
>> the CDROM cannot be mounted to obtain the sources
>
>> Since I have a working
>> patch for the kernel, I would like to use "bare.i" with replaced
>> kernel, and "install.1" for replaced rootdisk, compatible with
>> "install.1" for the package installation tools.
>>
>> Sincerely,
>> Steven J. Hathaway
>
> I am thinking that maybe the version of glibc is wrong.. I compile the
> kernel under Slackware 10.1, and it works under Slackware 10.1 and
> reads the CDROM. Using rdev to set the root device, prompt flag,
> and load ramdisk flag, and replacing the kernel in the SYSLINUX
> boot floppy, complains when the kernel attempts to load the install1
> diskette that includes kernel modules distributed with Slackware 10.2.
>
> As for burning a new .iso image for Slackware Install CD(1), my
> CDROM is a read-only device, not a writable device. I must go
> to my other office that has MS-Windows to burn .iso images to CD.
>
> I also looked at the install1 contents and find that the *.o kernel
> modules have been compressed with gzip. The patched kernel
> does not no how to load these compressed kernel modules.
> I have not looked closely enough at the modules.dep file to
> see if the *.gz files are explicitly referenced.
>
> As for more of my technical background:
> When building LFS (Linux From Scratch) I also modify the init.c
> to first look for /linuxrc as an init executable, and use it as a shell
> script with busybox(sh). I then configure another root system
> and do a pivot_root without the /linuxrc and it finds the true
> init program.
>
> I'll try the 'nodma' hint, trying to force the unpatched kernel
> to be compatible with the CDROM. I hope it does not interfere
> with using my hard disk drives. Before Linux Kernel 2.4.28 came
> out, I requested a patch to blacklist the SAMSUNG CD-140 disk.
> As of Linux Kernel 2.4.32, the drive is still not in the ide-dma
> blacklist.
>
> Sincerely,
> Steven J. Hathaway
>
If you compile your own kernel, then you need to use the modules for that
kernel, and label your new kernel appropriately. If you don't, then the
confusion you are seeing now is the result. You label your kernel by
using "extra version" for 2.4.x or "local version" for 2.6.x. For example,
if you label your kernel 2.4.32-sjh-01, then there will be no confusion
with Slackware's modules, 2.4.32. Another option is to remove that
version of Slackware's kernel and modules (and alsa-driver).
You must really like that Samsung drive to go to all this work to keep it
If it were mine, it would have tossed it long ago. Seriously, if you're
just trying to learn Slackware, you don't need this aggravation.
--
Douglas Mayne
--
Douglas Mayne