LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-22-2004, 07:16 PM   #1
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,726

Rep: Reputation: 187Reputation: 187
SCSI bootdisk image to large for floppy


Hi,

first of all, sorry, if this has been asked before. I looked through this forum, but couldn't fine quite what I need.

My problem is this:
Slackware 10.0 has been running perfectly well with the bare.i kernel on one of my machines. Now I added a SCSI controller in order to connect a SCSI tape streamer and a SCSI scanner to it. To this end I have to replace the bare.i kernel with scsi2.s (which I hope to be the right choice for a Tekram DC395U SCSI adapter...).

What is the best way to switch the kernel?

There seem to be no Slackware packages with SCSI kernel binaries. So I thought I'd create a new bootdisk and install the new kernel from that using pkgtool. However, the bootdisk image created by makedisk is too large --- it doesn't fit on a standard HD floppy disk formatted for standard capacity (1.44MB). So this plan didn't work.

What options do I have, now, and which one is the best?

Thanks again!

gargamel
 
Old 07-23-2004, 05:03 AM   #2
keefaz
LQ Guru
 
Registered: Mar 2004
Distribution: Slackware
Posts: 6,230

Rep: Reputation: 724Reputation: 724Reputation: 724Reputation: 724Reputation: 724Reputation: 724Reputation: 724
Are you sure that bare.i kernel does not support your SCSI controler ?
 
Old 07-23-2004, 10:02 AM   #3
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,897

Rep: Reputation: 578Reputation: 578Reputation: 578Reputation: 578Reputation: 578Reputation: 578
You mean makebootdisk. makebootdisk should format the floppy first to 1680k. You can open the script in a text editor and change the line for 1440k though. But this floppy will still not boot like a slackware installation floppy(it will not mount a floppy root file system).
Isn't there a scsi2 BOOTDISK? And do you really need an install bootdisk?
To change the kernel just copy the bzImage, config and system.map into /boot. The best thing is to name them with the same, unique suffix: kernel: vmlinuz-customname; system.map: system.map-customname; config: config-customname
The system is smart and can locate the correct fiel to match the kernel and several kernels can all reside in the same dir.
then add the entry to lilo.conf and run lilo -v -t and if no errors then lilo
If you really want to make a custom installation bootdisk that works just like a slack bootdisk then you need to go into the /bootdisks dir and look at the script makedisk. You can't just run it as it is meant to run inside of make_all_bootdisks. But it has the commands there that you need to carry out to get a custom install floppy. You can use message.txt and syslinux.cfg from a standard Slack bootdisk and you can build it with any kernel from /kernels dir or self-compiled as long as it isn't over... er can't remember the figure, 1204k maybe. Anyway the rdev commands are what will make your kernel do what you want.
 
Old 07-23-2004, 04:23 PM   #4
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,726

Original Poster
Rep: Reputation: 187Reputation: 187
Quote:
Originally posted by keefaz
Are you sure that bare.i kernel does not support your SCSI controler ?
None of my SCSI devices is seen, it seems --- no sign of them in /var/log/messages or dmesg. There are also no generic SCSI support modules and no supporting devices.

modprobe sg
and lsmod

tell me that the desired module could not be found. Interestingly that's only true for kernel 2.4.26. I checked it also with 2.6.7, and there I see an sg module. However, no SCSI device, either:

cat /proc/scsi/scsi

returns nothing.

From that I conclude that bare.i doesn't support SCSI, apart from ide-scsi.
But I may be wrong. Do I miss something obvious?

gargamel
 
Old 07-23-2004, 04:36 PM   #5
keefaz
LQ Guru
 
Registered: Mar 2004
Distribution: Slackware
Posts: 6,230

Rep: Reputation: 724Reputation: 724Reputation: 724Reputation: 724Reputation: 724Reputation: 724Reputation: 724
Yes I would think so (kernel does not support SCSI). But to make boot disk from other kernels, aren't there instructions to how to do it in /kernels subdirectories in the install CDs ?

[edit]
This link may help : http://www.slackware.com/faq/do_faq....installation#4

Last edited by keefaz; 07-23-2004 at 04:39 PM.
 
Old 07-23-2004, 04:47 PM   #6
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,726

Original Poster
Rep: Reputation: 187Reputation: 187
First of all, thanks for your reply.

Quote:
Originally posted by gnashley
You mean makebootdisk. makebootdisk should format the floppy first to 1680k. You can open the script in a text editor and change the line for 1440k though. But this floppy will still not boot like a slackware installation floppy(it will not mount a floppy root file system).
Hmmm. Right now I'm not on Slack, so I can't verify it, but I thought the instructions (README file or something) were talking of makedisk... But it's quite possible that I misunderstood something.

Quote:
Originally posted by gnashley
Isn't there a scsi2 BOOTDISK?
OUCH. You are, of course, right, there is, in fact, such a boot disk... I should avoid working so long....

Quote:
Originally posted by gnashley
And do you really need an install bootdisk?
Unsure, here. pkgtool has a function "install kernel from boot disk", which I thought I could use. In order to be able to so I thought I'd create the boot disk, first. Of course, I had other ideas, first, but see below...

Quote:
Originally posted by gnashley

To change the kernel just copy the bzImage, config and system.map into /boot. The best thing is to name them with the same, unique suffix: kernel: vmlinuz-customname; system.map: system.map-customname; config: config-customname
The system is smart and can locate the correct fiel to match the kernel and several kernels can all reside in the same dir.
then add the entry to lilo.conf and run lilo -v -t and if no errors then lilo
I had this idea, in fact, but this way I would bypass the package management database of my system, which I would like to avoid, if possible. But if I don't find a way that helps to do it in more "official" manner, this method would certainly be an option.

Quote:
Originally posted by gnashley

If you really want to make a custom installation bootdisk that works just like a slack bootdisk then you need to go into the /bootdisks dir and look at the script makedisk. You can't just run it as it is meant to run inside of make_all_bootdisks. But it has the commands there that you need to carry out to get a custom install floppy. You can use message.txt and syslinux.cfg from a standard Slack bootdisk and you can build it with any kernel from /kernels dir or self-compiled as long as it isn't over... er can't remember the figure, 1204k maybe. Anyway the rdev commands are what will make your kernel do what you want.
The script worked, in prinicipal, but it terminated with an error message, that the data would not fit on the boot disk --- I had no System.map on the boot disk created.

Any additional comments or ideas are much appreciated!

gargamel
 
Old 07-23-2004, 05:32 PM   #7
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,726

Original Poster
Rep: Reputation: 187Reputation: 187
Quote:
Originally posted by keefaz
Yes I would think so (kernel does not support SCSI). But to make boot disk from other kernels, aren't there instructions to how to do it in /kernels subdirectories in the install CDs ?

[edit]
This link may help : http://www.slackware.com/faq/do_faq....installation#4
There are instructions telling to use ./makedisk. Which I did, giving me the mentioned result: Image created too big to fit on a floppy.

gargamel
 
Old 07-23-2004, 07:52 PM   #8
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,726

Original Poster
Rep: Reputation: 187Reputation: 187
Ok, I have the bootdisk. I copied vmlinuz from it to /boot (renamed it to vmlinuz-scsi-2426), added a section in /etc/lilo.conf for it, issued lilo and rebooted. Unfortunately... no effect. Still no SCSI devices detected.

I guess, the right driver is missing. Tekram DC395 is not listed in the description of any boot disk. That probably means that I have to compile my own kernel --- which I wanted to avoid as means that I'll have to to it over and over again, whenever a security patch is to be applied...

Thanks for your suggestions and comments, so far. Further thoughts and ideas welcome!

gargamel
 
Old 07-23-2004, 09:27 PM   #9
WMD
Member
 
Registered: Jul 2004
Location: Florida
Distribution: Slackware, Debian
Posts: 484

Rep: Reputation: 30
Lightbulb

Wait...there's 3 SCSI kernels I think. Try the other two.
 
Old 07-24-2004, 12:09 PM   #10
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,726

Original Poster
Rep: Reputation: 187Reputation: 187
Quote:
Originally posted by WMD
Wait...there's 3 SCSI kernels I think. Try the other two.
Yes, thanks. It seems that none of them has support for my SCSI adapter (Tekram DC395U). To my surprise this popular controller is not supported in the standard Linux kernel.

However, I found a driver for Slackware 9.0 and a kernel source tree patch, but right now I don't have the time to check them out. BTW, the driver maintenance is sponsored by SuSE, my other favourite distro --- which explains why I have never had no problems on SuSE with that controller. So this is the one situation when vendor patches aren't a bad thing...

Thanks!

gargamel
 
Old 07-24-2004, 01:11 PM   #11
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,726

Original Poster
Rep: Reputation: 187Reputation: 187
SOLVED: Kernel 2.6.7 supports my SCSI controller by default. 8-)
All I have to do is activate the driver module (modprobe) and the SCSI generic module (sg).

(1) Uncomment the line
#/sbin/modprobe sg

(2) Add
/sbin/modprobe dc395x

Thanks for your patience!

gargamel
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
questions regarding scsi and bootdisk celticX Slackware - Installation 2 09-04-2004 06:47 PM
Best image viewer for very large image files? andvaranaut Linux - Software 1 02-21-2004 11:01 AM
Floppy Bootdisk barc0de Linux - Newbie 1 01-30-2004 05:16 AM
Creating a floppy bootdisk from Slack 8.1 CD Kremlin Slackware 2 02-20-2003 10:27 AM
Floppy BootDisk Thomas_Delrue Linux - Newbie 1 07-08-2001 11:48 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:14 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration