SEO

I need to patch the Linux 2.4.31 kernel (ala Slackware 10.2)
in order to use my a broken driver for SAMSUNG ATAPI CDROM, by
blacklisting the SAMSUNG drive in the drivers/ide/dma.c. The patch
works with the 2.4.31 kernel compiled under the Slackware 10.1
distribution.

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. To install
Slackware 10.1, I had to copy the distribution to another disk
that could be mounted to the ramdisk. 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

On Sun, 23 Jul 2006 20:38:22 -0700, Steven J. Hathaway wrote:

> I need to patch the Linux 2.4.31 kernel (ala Slackware 10.2)
> in order to use my a broken driver for SAMSUNG ATAPI CDROM, by
> blacklisting the SAMSUNG drive in the drivers/ide/dma.c. The patch
> works with the 2.4.31 kernel compiled under the Slackware 10.1
> distribution.
>
> 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. To install
> Slackware 10.1, I had to copy the distribution to another disk
> that could be mounted to the ramdisk. 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 think you should be able to recompile the kernel with your patch
included. The resulting kernel can be named bare.i to start the boot
process for the setup program. You can also use whatever kernel you want
with Slackware once it is installed (remember to recompile alsa-driver,
too, to get the sound working.)

I think that's right. It's been a while since I setup Slack with floppies.

--
Douglas Mayne

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2006-07-24, Steven J. Hathaway <shathawa@e-z.net> wrote:
> I need to patch the Linux 2.4.31 kernel (ala Slackware 10.2)
> in order to use my a broken driver for SAMSUNG ATAPI CDROM, by
> blacklisting the SAMSUNG drive in the drivers/ide/dma.c. The patch
> works with the 2.4.31 kernel compiled under the Slackware 10.1
> distribution.
>
> I wish to rebuild the bootdisk "bare.i" and the rootdisk "install.1"

You shouldn't need to touch the install.1 image at all. This is
probably as simple as compiling your kernel and placing it on the
floppy. I'm unsure if there is any magic that needs to be done to the
floppy, as I've only done this with custom burned CD images.

Anyhow, to do this with a CD image, place the kernel in a directory
like custom.i under kernels/ and edit isolinux/isolinux.cfg IIRC.
Looking inside that file you'll see the setup is pretty
self-explainitory, then just load custom.i instead of bare.i.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFExSg3z8zcalmVmBkRAv8YAKCuE7y8rSwpI+8bsXlikL XDXOtBQQCfeOMi
MSOFynD6pudykhEAearu0i4=
=1vyW
-----END PGP SIGNATURE-----

Douglas Mayne wrote:
> I think you should be able to recompile the kernel with your patch
> included. The resulting kernel can be named bare.i to start the boot
> process for the setup program. You can also use whatever kernel you want
> with Slackware once it is installed (remember to recompile alsa-driver,
> too, to get the sound working.)

Yes, there is some magic that needs to be run on the kernel to get it to prompt for the root disk. It has been a long time so I do not remember the syntax, but I know that you need to run the "rdev" command against your custom kernel before you write it to your boot floppy. I want to say that the command is something like "rdev 1 <kernel>". Reference the man page for rdev for details.



Grant. . . .

Steven J. Hathaway wrote:

> I need to patch the Linux 2.4.31 kernel (ala Slackware 10.2)
> in order to use my a broken driver for SAMSUNG ATAPI CDROM, by
> blacklisting the SAMSUNG drive in the drivers/ide/dma.c. The patch
> works with the 2.4.31 kernel compiled under the Slackware 10.1
> distribution.

How about disabling dma in the BIOS?
Or disabling it with a kernel parameter? I think it's ide1=nodma or
hdc=nodma - but check the docs.


--
damjan

"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

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