Cannot do zless. Hmmm.

dpkg -S /bin/zless
gzip: /bin/zless

If you have installed the gzip package then you will have zless. If you do not have zless, then you have not installed gzip, and you will not be able to gunzip!

So you need to

apt-get install gzip

and whilst you are at it, also do

apt-get install bzip2

since you are going to need that to unpack the kernel source.

And good news on the kernel source front, another Debian revised version (number 4) has just been released.

apt-get install kernel-source-2.4.21

Good thinking!

This is going to be interesting. I have had a struggle to get my Radeon 8500 working with DRI under SuSe. Your choice for frame buffer support is going to be limited to VESA, since the ATI frame buffer driver in the kernel does not yet support the 9000. Furthermore even if it did, the Radeonfb conflicts with the Radeon video driver (as might be expected). But VESA is good enough and you will get your boot logo.

Bad news, there is no Debian package that I can find for ATI. So you are going to have to manually install the ATI Radeon driver from the ATI site.

So

apt-get install kernel-patch-scripts
apt-get install kernel-patch-debianlogo

You indicated no problems for these.

The recommendation is ALSA. For sound, choose ALSA modules. You will need to download all the necessary ALSA packages.

Do you need anything special for that? Probably not.

[QUOTE]Asus CD-S520/A 52X[QUOTE]

Is that a SCSI CD-ROM? What does the S mean?

You know you need SCSI support for CD writers? And for DVD you need UDF support.

And if you do that, on the recommendation of what I have read, it makes sense to emulate all your CD-ROM devices as SCSI devices, and so you do not compile in IDE CDROM support.

Well you will know by now what USB stuff you need to compile in.

Just about, yes. But somethings you should or can only do as modules. PNP sound cards have to be done as modules because they are only in a recognised state after the kernel has finished booting.

So for sound support you build modules. And if you had a tv card you would also do that as a module. And if you want to do ppp that should also be built as a module. In fact compression over ppp is only available if you build as modules.

Oh and somethings we forgot, useful but not essential is cdfs support, which is available as a module.

apt-get install cdfs-src

And you should install lm-sensors

for which you need to get

apt-get install i2c-source
apt-get install lm-sensors-source

When you come to compile your kernel, in the config you need to say that you will be wanting to build modules for i2c, but do not select any of the modules to be built, since they will be provided by the external i2c module build. Same goes for ALSA.

For which you need to get lots of packages

alsa-base
alsa-headers
alsa-source
alsa-utils
alsaconf
alsamixergui
libasound2

If you ever want to compile yourself some ALSA programs (eg MPlayer which is always best self-compiled) then you will need

libasound2-dev

and you should also get

libasound2-doc

I think that is just about everything.

debian:/home/servant# dpkg -S /bin/zless
gzip: /bin/zless

debian:/home/servant# zless /usr/share/doc/kernel-package/README.gz
/bin/zless: line 4: exec: less: not found

debian:/home/servant# cd /usr/share/doc/kernel-package/

debian:/usr/share/doc/kernel-package# ls
Flavours.gz README.gz README.source copyright
Multi-Arch.gz README.headers README.tecra kernel_grub_conf.sh
Problems.gz README.image Rationale.gz sample.kernel-img.conf
README.doc README.modules changelog.gz

debian:/home/servant# apt-get install gzip
Reading Package Lists... Done
Building Dependency Tree... Done
Sorry, gzip is already the newest version.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
debian:/home/servant# apt-get install bzip2
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
libbz2-1.0
The following NEW packages will be installed:
bzip2 libbz2-1.0
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 264kB of archives. After unpacking 496kB will be used.
Do you want to continue? [Y/n] Y

debian:/home/servant# zless /usr/share/doc/kernel-package/README.gz
/bin/zless: line 4: exec: less: not found


Don't understand this problem. I gunzipped the rascal and printed it. Will read it after some sleep.

You have given me quite a bit to do. I hope the mod doesn't mind us using the forum like this - it's a bit more like email, I think. Perhaps someone else will follow this thread and get themselves a well-built shiny new Linux system.

It was my intention to build a very fast, streamlined Linux box - with only that software needed to do my work. However, at this point, my goal is simply to replace M$ as the OS which I use. From that point I'll live and learn and advance as time permits.

I don't know diddly about forums and less about Linux. All I know is that for the last decade+ M$ has controlled my computers, and I'm ready to assume the responsibility myself.

If God hadn't given me a brain, I would happily acquiesce to M$ and give up my rights to the freedom which should be mine with computers. However, I see M$ marching towards the total control of this industry, and until such time as they pry the 0's and 1's out of my hands, it is my full intention to learn Linux and such open source software as is available, and use them without disruption or interference from outside sources. Considering the fact that I have purchased the software from M$, it is criminal that they should still have such control over my software and my computer. In my present location, building and repairing computers is my joyful hobby. When I install M$ convoluted OS on a new hd, the first thing I do is remove their Alexa spy ware from the registry. It's only the beginning. But I digress.

I suppose that I should install these various things in the order in which you have entered them. If not, I'll start over later.

Thanks.

/bin/zless: line 4: exec: less: not found

Obviously you need to install the less package.

apt-get install less

Remember less is more.

From your speech there, it sound like you have just been released from the Micro$loth Matrix. ;+)

And once you get your Debian system setup, you will be able to install a Matrix screensaver ;+P

Do I apt-get those you mentioned in post #16 from debian:/usr/src# ?

It appears that the latest kernel source on the web is 2.4.21-3. That is from http://packages.debian.org/testing/allpackages.html as well doing apt-get install kernel-souce-2.4.21 from the mirror I'm currently using in Taiwan http://debian.linux.org.tw However, I find this kernel-tree-2.4.21_2.4.21-4_all.deb at http://debian.linux.org.tw/debian/po...source-2.4.21/

Perhaps you could enlghten me some more?


TIA

You just type

# apt-get install <package-name>

and provided you have put the right entries in your /etc/apt/source.list, it will retrieve them from your Debian mirror site and install them.

In the case of kernel source and module source packages, it will put a tarball in /usr/src.

Further details on proceeding will be sent by e-mail, I'm just checking a revised shell script.

Thank you so much. I know I can do it and try to fix it or reinstall, but I've done that so many times and wind up having to reinstall because somethings broke I can't fix. Is it just me, or is most of the Linux documentation written to the level of someone who has been using a Linux distro for a year or more - and is it all really as conflicting from one persons's How-To to another? I am beginning to feel like I have NO reading comprehension!

The Linux HOWTOs are written mainly by people who started using linux from the time it was first released and they have forgotten that other people have not got a clue what they are trying to explain.

Hello Chinaman, I hear your frustration, all the way here in Sweden! I'll throw in my two cents ( Though in fear of being contradicted by half of Texas! ) I read through some of your posts here, my advice would be to avoid installing a stable distro and updating it with the testing version, am I correct in assuming this is what you did? When I install a Linux server in a production environment I always have a test machine for mucking about with, testing kernels and new hardware any old PC will do. In order to fully understand how to customize your kernel you must first know your hardware inside out, next you must understand how your boot loader works and you must keep your standard kernel available for rescue mode! The problem you are having with the network cards could be down to system resources, devices need system resources in order to operate, there could be a conflict between your network card and something else. Post detailed information about the machine you are configuring and I'll see if I can help you. With regard to the documentation, some configuration techniques are difficult to learn from documentation, though I do think that all of the documentation on www.tldp.org is excellent, becoming a linux pro takes time and lots of reading there are no shortcuts, if you jump in too deep you'll get confused.

Hello again mrhyde! It's great to hear from you.

Corin has been most gracious to help and educate me. We've had quite a bit of email at this point. I've really been learning a lot, and there's a lot that we've done "behind the scenes," so to speak. It's just taken me a while to do what he's told me in this forum.

You're exactly right!

The network card issue is solved by editing /etc/network/interfaces (post #9).

My machine is in post #15.

As my new friend says, "the biggest stumbling block is always esoteric"; and, "The problem of the material on the web is that it assumes a prior knowledge of the topic."

My frustration with Linux is not nearly as severe as my frustration with Micro$loth. It's just that right now, because of years of experience, I have a finely tuned Windoze XP system with which I can work, and all my hardware is detected. I built this computer on Nov. 1, 2002, and I have not had one single BSOD, hang, or other problem - with one exception. The Wacom pen tablet which I bought here in China doesn't have English documentation, so I can't properly install it on XP. The last kernel I built for Debian detected it correctly, though, so I expect it to work better under Linux.

I am not giving up on Linux, and I do understand it will take time to become proficient. You helped me, MasterC has helped me, and Corin has taught me a lot in a little time. It is my goal to become a Linux professional. About getting there, it's as we say in China...
man man lai (little by little)


P.S. I almost forgot. The place Corin jumped in and began helping me was when I bumped this thread because I didn't get a response to post #1. Every time I boot, if I enter before the timeout, or enter linux single, it gives the following error:

boot:
Loading Linux.........................
Uncompressing Linux...

invalid compressed format (err=1)

-- System halted

Then I can only reset, and it boots okay. If, however, I don't enter anything at the boot time, it boots okay every time. We jumped right over that issue, because I threw something else into the thread. Corin explained the boot process to me, and I believe this is happening because I used the bf24 kernel when I originally installed, though I have no facts upon which to base my opinion. Anyway, I think this will disappear once I recompile the kernel. Which, by the way, I am about to do tonight - I think.

You never got round to printing the contents of your " /etc/lilo.conf " file, you went off on a tangent! Can you post this file and list the contents of you /boot directory. Corin has been pretty decent! You can't beat Europeans for hospitality especially Belgians!

mrhyde,

I'll boot back into Debian and do it straight away! Yes, Corin is a God-send! You guys have certainly helped me more than I could have hoped for, and your patience is unbelievable. I've had to be in Windoze to use Photoshop and PageMaker to prepare a newsletter.

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81

#disk=/dev/sda
# bios=0x80

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda3

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=10

# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
# prompt
# single-key
# delay=100
# timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal

# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1

#image=/vmlinuz.old
# label=LinuxOLD
# read-only
# optional
# restricted
# alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
other=/dev/hdb1
label= Windoze
table= /dev/hdb
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80

You probably didn't want all that, but editing for me takes longer than skimming for you When Debian installs lilo, it won't boot hdb1, but MasterC told me to change it as it is above, and that boots hdb1. The delay=10 doesn't work, either. It delays 15, and actually, I only need about 3 secs.

Here's the /boot info:

debian:/boot# ls -al
total 1830
drwxr-xr-x 3 root root 248 Aug 5 16:55 .
drwxr-xr-x 20 root root 480 Aug 5 13:51 ..
-rw-r--r-- 1 root root 559088 Aug 5 13:48 System.map-2.4.18-bf2.4
-rw-r--r-- 1 root root 512 Aug 5 13:53 boot.0300
lrwxrwxrwx 1 root root 11 Aug 5 13:52 boot.b -> boot-menu.b
-rw-r--r-- 1 root root 16984 Aug 5 13:48 config-2.4.18-bf2.4
-rw------- 1 root root 20480 Aug 5 08:38 map
-rw-r--r-- 1 root root 1263339 Aug 5 13:48 vmlinuz-2.4.18-bf2.4


It's the wife's birthday, so if I don't get back tonight, I'll bet back to it tomorrow.

TIA

P.S. Good to hear from you again.