I would like to refer back to my last post( see foot of this post) and the question about re-configuring and re- compling and installing a new kernel. I have been reading Jem's Guide: How to complie and install a new Linux kernel.
Now the thing is the only item here is that looking in the kernal config file all I need to do is to disable CONFIG_BLK_DEV_LOOP. (I am not going to use the SAME version (2.4.22-1.2115.nptl) kernel that is presently installed) but re-configured and re-complied –seems a long proceess.
According to Jem's Guide: copying the old .config file file to the top level of my source.
Also the Guide says “if you want to re-confiure the kernel from scratch and re-compleit , you must use the the process below:
make mrproper (note that “make mrproper” deletes your .config file)
make oldconfig
make dep
make clean
make bzImage
make modules
make modules_install
I am wondering if all this is necessary and how would installing the recomplied
kernel have on the old kernal.?
Finally when installing and booting the new kernel the example in the guide is
cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.22
Now since this will be the same version should I use the command
cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.22a?
Also the file System.map must be copied to the same boot directory.
At the moment GRUB looks like this:
default=1
timeout=10
splashimage=(hd0,4)/boot/grub/splash.xpm.gz
title Fedora Core (2.4.22-1.2115.nptl)
root (hd0,4)
kernel /boot/vmlinuz-2.4.22-1.2115.nptl ro root=LABEL=/1 hdc=ide-scsi rhgb
initrd /boot/initrd-2.4.22-1.2115.nptl.img
title DOS
rootnoverify (hd0,0)
chainloader +1
I expect that when I edit this file it will be 2.4.22a-1.2115.nptl.
Finally ,, umm I do have space on a another partition, which might be
less demanding But I wonder since the .config file is alredy confiured
on the CD I am not sure if I can change it
Many thanks for your feedback
Andrew
--------------------------------------------------------------------
Man is rich in the fewness of his wants
-----------------------------------------------------------------------
This is what I am refering to
3. Instructions for building loop.o driver
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Before you attempt to build loop.o driver (loop.ko on 2.6 kernels), you
*must* configure, compile and install new kernel so that CONFIG_MODULES=y
and CONFIG_BLK_DEV_LOOP=n. Also, CONFIG_KMOD=y is recommended but not
required (kernel 2.0 doesn't have CONFIG_KMOD, set CONFIG_KERNELD=y
instead). Configuring your kernel so that loop driver is built-in
(CONFIG_BLK_DEV_LOOP=y) or module (CONFIG_BLK_DEV_LOOP=m) will *not* work.
After building and installing your new kernel, do not attempt to clean
kernel tree, or rename path to kernel sources.
(Re)configuring and (re)compiling your kernel are required for following
reasons: (1) to disable loop driver in your kernel, (2) to get your kernel
sources to match your running kernel, (3) to get your kernel .config to
match your running kernel, (4) to set up configure time generated links
properly, (5) to generate compile time created header files properly to
match your kernel configuration. Failure to fulfill *all* above requirements
may cause loop.o driver compilation to fail or generate incorrectly
operating code. If you are just upgrading existing loop-AES with newer
version, there is no need to recompile kernel or reboot. Just unmount all
file systems using old loop driver, and remove loop driver from kernel with
rmmod command before compiling new loop driver.
bwkaz
03-19-2005, 10:10 AM
I'm not positive that I know what you're asking, but personally I don't think recompiling a kernel takes all that long.
If you're going to go through and look at every single option, read the help on it, and think a while (which I highly recommend you do at some point), then yes, that will take a while. But to just disable the loopback block device support in an already existing configuration shouldn't take all that long.
Whenever I tweak my kernel's configuration, this is generally how I do it. Assume I start with kernel 2.6.11.5, and I need to disable loopback block device support, just like you. Since I compile my own kernels, I have them sitting in my home directory, but they can be anywhere (as long as the user that you're compiling as has write permission).
I cd into /home/me/linux-2.6.11.5, and open up the Makefile in an editor. I add some string to the EXTRAVERSION variable at the top, so that I don't lose my original set of kernel modules. Generally adding "custom" or "noblkdev" or something would work.
Then, if I know the CONFIG_ variable name, I edit the .config file, make the changes that are needed, and run "make oldconfig". If I don't know the CONFIG_ names, I look through the "make menuconfig" interface for the setting I need to change, and change it. Then I exit, telling it I do want to save the changes.
Then, I do a "make" then (as root) a "make modules_install". You can skip modules_install if you don't have modules enabled at all, but your post seems to say that modules are required, so don't skip it. ;)
Then, still as root, I cp arch/i386/boot/bzImage to /boot/<whatever-filename>. Personally, I'll use /boot/bzImage-<kernel version>, so I can keep several kernel versions straight, but that's a personal choice. You can use vmlinuz-<version>, or vmlinuz and vmlinuz.old (if you only ever need 2 kernels), or whatever else, the filename doesn't matter.
I then edit my bootloader's configuration, and add an entry for the new kernel. I do NOT touch the old kernel's entry, so that just in case I screwed something up with the new one, I can still go back. I copy the section that I was booting to, and just change the kernel filename.
This is where you need to know the new kernel's filename, obviously, but what it actually is doesn't matter. Heck, you could call it "fjkldsajflkdsajflkfdaf" if you wanted to. :D
Does that help at all?
XiaoKJ
03-19-2005, 12:32 PM
andrew, what is your distro? Fedora what?
and also, why do you want the same kernel? Its easy to cause problems that way. I think you should get a new kernel version and compile with that instead of this kernel.
Why? because if you compile with this kernel, all the symlinks will point to the same few files, and you will have havoc in your system if anything breaks. its best to have a correct kernel by itself in case anything happens.
If you get a new kernel version, best to be 2.4, you can just copy the file /boot/config-2.4.22-1.2115.nptl into the directory and rename that as .config, then you can make oldconfig and make menuconfig
the make menuconfig is for you to remove that offending option. after that, you can continue with the guide and make your own kernel.
andrew anand
03-20-2005, 01:17 PM
I am running fedora core 1
Thanks for the posts. I am hoping that XiaoKJ you may be incorrect in what you said because I only have the one kernel. Thats THE one I refered to in my last post
NOW TO Bwkaz
Yes thats correct I am config complile and install the same Kernel I have at present but only as you said I am to disable the loopback block device support .
Now I do not have the kernel sitting on my computer please tell me the
commands to open (not install)a RPM in the KDE file manager window.
You said ". I add some string to the EXTRAVERSION variable at the top, so that I don't lose my original set of kernel modules. Generally adding "custom" or "noblkdev" or something would work."
can you tell me the string to add. In Generally is ok but are you sure about
custom or noblkdev?
Editing the config would be simple but what do you mean when you say
not knowing the config names. what do you mean by this? Is it not just a matter of editing the loop back to disable why is it neccessary to look through the make menu config?
What I would like you to understand is that I have installed and I am cofig recomile and installing the same version kernel only this time with loopback disabled. Do you think I will have a problem with it being being the same kernel version? as our friend XiaoKJ in his post.?
Now on to this paragraph
<Then, still as root, I cp arch/i386/boot/bzImage to /boot/<whatever-filename>. Personally, I'll use /boot/bzImage-<kernel version>, so I can keep several kernel versions straight, but that's a personal choice. You can use vmlinuz-<version>, or vmlinuz and vmlinuz.old (if you only ever need 2 kernels), or whatever else, the filename doesn't matter..>>>
iF i use /boot/bzImage -<kernel version> as I said in my last post if it is the same version as the verion already running then should I somehow change the version from version 2.4.22 to /boot/vmlinuz-2.4.22a?
Also
you said>I then edit my bootloader's configuration, and add an entry for the new kernel>
How would this look in my case with GRUB you can see how it looks at the moment from my last post.
many thanks
Andrew
:) :)
bwkaz
03-20-2005, 03:00 PM
Originally posted by andrew anand
Now I do not have the kernel sitting on my computer please tell me the commands to open (not install) RPM in the KDE file manager window. Does your distro have a graphical package manager somewhere? Fire it up, find the kernel-source package, and install that. That would be the easiest.
can you tell me the string to add. It does not matter what you add -- I just add something to make the new kernel's version string different from the old kernel's version string. The actual string does not matter one bit.
not knowing the config names. what do you mean by this? Is it not just a matter of editing the loop back to disable why is it neccessary to look through the make menu config? It depends on what you're trying to disable. In your case, you know exactly which setting needs to be disabled, so you could just edit .config and run "make oldconfig".
In my case, I often don't know the name of the setting, but I do know where in menuconfig it's stored (because I've done the "read through the help on all the options" a few times now, so I'm fairly familiar with where each option is). For example, just the other day I changed the configuration of my kernel to include the network driver for FA311-chipset network cards. I don't know which setting that is in the .config file, but I do know that I have to set the "National Semiconductor DPwhatever PCI Ethernet" driver to be a module. So I fired up menuconfig, made that change, exited, then built the new module.
Do you think I will have a problem with it being being the same kernel version? If you edit the EXTRAVERSION variable in the top level Makefile, then it won't be the same version. That's why I include that step. ;)
The code will still be the same in the actual kernel, but the version string that the kernel "knows" itself by will be different, so it won't step on the other kernel.
iF i use /boot/bzImage-<kernel version> as I said in my last post if it is the same version as the verion already running then should I somehow change the version from version 2.4.22 to /boot/vmlinuz-2.4.22a? If you edited the top level Makefile and set EXTRAVERSION to the string "a" (without the quotes), then the kernel's version will be 2.4.22a. Of course, that doesn't mean you have to name it /boot/vmlinuz-2.4.22a, either (as before, the filename does not matter one bit).
How would this look in my case with GRUB you can see how it looks at the moment from my last post. Something like this:
title DOS
rootnoverify (hd0,0)
chainloader +1 Now that I reread your menu.lst file again, I see that your current kernel has an initrd set up. I've never used an initrd (for practical reasons: There's absolutely NO REASON to build your root filesystem driver or the driver for your main IDE chipset as modules, if you're going to load those modules in an initrd and never unload them!), so I'm not entirely sure what's involved in building a new one, but you'll probably have to build a new one after compiling your new kernel. I believe the "mkinitrd" command would be useful, but I don't know anything about it.
Otherwise, you could just change your kernel's configuration so that the driver for whatever filesystem you have on your root partition is built in (not a module), and also the driver for your IDE chipset is built in (not a module). Then you shouldn't need an initrd, and you can remove the "initrd" line (the one with the ***** above).
je_fro
03-21-2005, 10:21 AM
If he is successful and disables the loopback, won't that take away 127.0.0.1 and make the box useless for networking, and lots of other things? Why disable lo?
Choozo
03-21-2005, 10:40 AM
Originally posted by je_fro
If he is successful and disables the loopback, won't that take away 127.0.0.1 and make the box useless for networking, and lots of other things? Why disable lo? I'd like to know that too :p
XiaoKJ
03-21-2005, 10:58 AM
no. He will install a new one from another source, so he must remove it.
And isn't it the BLOCK loopback DEVICE support? why is it lo now?
bwkaz
03-21-2005, 07:38 PM
CONFIG_BLK_DEV_LOOP is not in any way related to the "lo" network interface (other than their names). ;)
The loopback block device is used for creating a block device out of a file that's already on a filesystem. (It's the way I test out CD images between mkisofs and cdrecord -- I have the .iso file on a filesystem somewhere, so I loopback-mount it and make sure it looks OK. If it doesn't, I modify either the directory that mkisofs used, or the mkisofs command line parameters. If it does look OK, then I unmount the .iso file and proceed to cdrecord it.)
Disabling kernel loopback block-device support will not disable 127.0.0.1.
je_fro
03-21-2005, 09:29 PM
Yeah, that's right....
mount -o loop something somewhere/
is the command to mount an iso. silly of me.
losetup also comes to mind...
andrew anand
03-22-2005, 10:12 AM
Thanks for all the posts helping me with my kerenel.
This has become a bit of a challenge .
OK bwkaz
Your last two paragraphs re initrd have got me thinking,
But I must press on .
You wrote:
: There's absolutely NO REASON to build your root filesystem driver or the driver for main your IDE chipset as modules:
what do you mean by “build” and would this effect the process of commands and things to do, mentioned previously in your last post before your last two paragraph ‘s
and in the post before that?
You wrote:
:if you're going to load those modules in an initrd and never unload them!:
what does this mean, what are the implications of loading modules in inird
and not loading modules in initrd? Just by way of a sideline I have read in
the loop-aes-3-0b that once you encrypt your filesysyem initrd can be used
as separate system. I have looked in Fedora in 24 hours (the book) and Linux
cookbook 2nd but not much about initrd
you wrote:
:so I'm not entirely sure what's involved in building a new one, but you'll probably have to build a new one after compiling your new kernel. I believe the "mkinitrd" command would be useful, but I don't know anything about.:
So I am thinking how to proceed? Mkinitrd has the following commands:
you wrote:
:Otherwise, you could just change your kernel's configuration so that the driver for whatever filesystem you have on your root partition is built in (not a module),
uum so how do I change the kernels configurarion?
For whatever filesystem?
Built in?
Driver located where?
You wrote:
and also the driver for your IDE chipset is built in (not a module). Then you shouldn't need an initrd, and you can remove the "initrd" line :
driver for for IDE chipset located where?
What about this suggestion.
Burn my two Fedora disks on to two new disks. Do not burn the
Kernel, rpm but copy it to my desktop or where ever amend the config file
so that CONFIG_BKL_DEV_LOOP is disabled save it. I might be able to do this
with the rpm command or with a graphical package manager if I can find one.
Burn the new kernel to the disk and run the whole show in a new partition.
Andrew:)
bwkaz
03-22-2005, 07:51 PM
Originally posted by andrew anand
what do you mean by "build" and would this effect the process of commands and things to do, mentioned previously in your last post before your last two paragraphs and in the post before that? I should have said "configure", not "build".
If you want to use an initrd (and keep your current setup), then ignore that whole section. But if you don't, then you'll have to "make menuconfig" (instead of oldconfig), find the drivers for your root filesystem type and your IDE chipset, and set them to Y instead of M. When you exit, be sure to save.
Then resume at the next step.
what does this mean, what are the implications of loading modules in inird and not loading modules in initrd? The main point of that statement wasn't the initrd part. ;) It was the fact that many people install a distro kernel, which autodetects a bunch of stuff at boot time (while the initrd is processing) and loads the appropriate modules then. But then they never unload those modules, so there's absolutely nothing gained over configuring them right into the kernel from the beginning.
They would be better off configuring those drivers into the kernel, because they would save a tiny bit of space for the module headers.
I have looked in Fedora in 24 hours (the book) and linux cookbook 2nd but not much about initrd And I've never used one either, so I probably can't answer most of your questions about them...
So I am thinking how to proceed? Mkinitrd has the following commands:
mkinitrd /boot/initrd-2.4.22a 2.4.22a But I don't know for sure if that'll work.
uum so how do I change the kernels configurarion? See above about menuconfig.
For whatever filesystem? The filesystem on your root partition. You should have told your distro installer what to use when you installed (it probably had a default too).
If you don't remember, then you can find out by looking through /etc/fstab for the line whose second field is "/" (fields are separated by whitespace). The filesystem will be the third field.
Built in? As opposed to "built as a module". Built-in means "included in the kernel at all times, so you don't have to manually load it".
Driver located where? In the kernel configuration (the menus that menuconfig provides).
driver for for IDE chipset located where? Same as above.
Burn my two Fedora disks on to two new disks. Do not burn the Kernel, rpm but copy it to my desktop or where ever amend the config file so that CONFIG_BKL_DEV_LOOP is disabled save it. I might be able to do this with the rpm command or with a graphical package manager if I can find one. Burn the new kernel to the disk and run the whole show in a new partition. No idea -- I'm not familiar enough with Fedora to know how to do that or what might be involved.
But I HIGHLY doubt you can reconfigure the kernel by editing RPM files, if that's what you meant. The RPM contains a kernel that has already been compiled, and you have to configure it before you compile it.
andrew anand
03-23-2005, 06:20 AM
Thanks for your post.
I understood things before we got to the initrd stage, now its beyond
my scope of knowledage and to be truthful I do not know how to proceed
it may be not as complicated as it looks but I feel I must now move on
and perhaps look at it again when I have a better understanding
many thanks
Andrew:)
andrew anand
03-23-2005, 12:01 PM
IGNORE LAST POST-------------------
I think it might be good to at least TRY rather than give up.
MY IDE CHIPSET what command would bring up the neccessary info about that please.
make menu config will have lots of info in it I hope I can decipher it.
many thanks
Andrew
:) :) :)
je_fro
03-23-2005, 02:12 PM
Look at the output from the commands:
lspci
and
dmesg | less
to see what hardware you have. That info will be invaluable when you do make menuconfig to configure your next kernel.
bwkaz
03-23-2005, 08:34 PM
Originally posted by andrew anand
So is my filesystem /dev/shm? It's ext3, actually. ;) The first line, in your case, is for the root filesystem.
In the lspci output, the line you're interested in for the IDE chipset will be the one that says "IDE interface" somewhere on it. But I agree with je_fro: It's a good idea to know what else you have, in case that ever causes a problem later (or you want to menuconfig from scratch, or you want to remove unused drivers).
andrew anand
03-24-2005, 11:21 AM
Thanks for the two posts received yesterday.
This is the output from lspci
Is this line what I am looking for?
00:1f.1 IDE interface: Intel Corp. 82801DB Ultra ATA Storage Controller (rev 02)
Yes I am aware of the less command, and this will NOT happen again,but working on the principle that "less is more "I am would welcome suggestions as to what is only essential to check in the .menuconfig
root@localhost xstation]# dmesg
Linux version 2.4.22-1.2115.nptl (bhcompile@daffy.perf.redhat.com) (gcc version 3.2.3 20030422 (Red Hat Linux 3.2.3-6)) #1 Wed Oct 29 15:42:51 EST 2003
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001ff40000 (usable)
BIOS-e820: 000000001ff40000 - 000000001ff50000 (ACPI data)
BIOS-e820: 000000001ff50000 - 0000000020000000 (ACPI NVS)
0MB HIGHMEM available.
511MB LOWMEM available.
ACPI: have wakeup address 0xc0001000
On node 0 totalpages: 130880
zone(0): 4096 pages.
zone(1): 126784 pages.
zone(2): 0 pages.
ACPI: RSDP (v000 ACPIAM ) @ 0x000f7370
ACPI: RSDT (v001 INTEL D845PESV 0x20030425 MSFT 0x00000097) @ 0x1ff40000
ACPI: FADT (v001 INTEL D845PESV 0x20030425 MSFT 0x00000097) @ 0x1ff40200
ACPI: MADT (v001 INTEL D845PESV 0x20030425 MSFT 0x00000097) @ 0x1ff40300
ACPI: ASF! (v016 AMIASF I845GASF 0x00000001 MSFT 0x0100000d) @ 0x1ff44360
ACPI: DSDT (v001 INTEL D845PESV 0x0000010a MSFT 0x0100000d) @ 0x00000000
Kernel command line: ro root=LABEL=/1 hdc=ide-scsi rhgb
ide_setup: hdc=ide-scsi
Initializing CPU#0
Detected 2666.604 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 5321.52 BogoMIPS
Memory: 513564k/523520k available (1503k kernel code, 9568k reserved, 1110k data, 136k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After generic, caps: bfebfbff 00000000 00000000 00000000
CPU: Common caps: bfebfbff 00000000 00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz stepping 07
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
ACPI: Subsystem revision 20031002
ACPI: Interpreter disabled.
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge
PCI: Using IRQ router PIIX/ICH [8086/24c0] at 00:1f.0
PCI: Found IRQ 9 for device 00:1f.1
PCI: Sharing IRQ 9 with 00:1d.2
PCI: Sharing IRQ 9 with 02:02.0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS0 at 0x03f8 (irq = 4) is a 16550A
Real Time Clock Driver v1.10e
NET4: Frame Diverter 0.46
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH4: IDE controller at PCI slot 00:1f.1
PCI: Enabling device 00:1f.1 (0005 -> 0007)
PCI: Found IRQ 9 for device 00:1f.1
PCI: Sharing IRQ 9 with 00:1d.2
PCI: Sharing IRQ 9 with 02:02.0
ICH4: chipset revision 2
ICH4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio
hda: ST3120022A, ATA DISK drive
blk: queue c040cfc0, I/O limit 4095Mb (mask 0xffffffff)
hdc: TEAC DV-W50E, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=14593/255/63, UDMA(100)
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
ide: late registration of driver.
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 162k freed
VFS: Mounted root (ext2 filesystem).
Journalled Block Device driver loaded
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 136k freed
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected an Intel(R) 845G, but could not find the secondary device. Assuming a non-integrated video card.
agpgart: Detected Intel(R) 845G chipset
agpgart: AGP aperture is 64M @ 0xf8000000
[drm] AGP 0.99 Aperture @ 0xf8000000 64MB
[drm] Initialized r128 2.2.0 20010917 on minor 0
mice: PS/2 mouse device common for all mice
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 15:50:32 Oct 29 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:1d.0
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0xe800, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 5 for device 00:1d.1
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0xe880, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 9 for device 00:1d.2
PCI: Sharing IRQ 9 with 00:1f.1
PCI: Sharing IRQ 9 with 02:02.0
PCI: Setting latency timer of device 00:1d.2 to 64
usb-uhci.c: USB UHCI at I/O 0xec00, IRQ 9
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Found IRQ 10 for device 00:1d.7
PCI: Setting latency timer of device 00:1d.7 to 64
ehci_hcd 00:1d.7: Intel Corp. 82801DB USB2
ehci_hcd 00:1d.7: irq 10, pci mem e2bacc00
usb.c: new USB bus registered, assigned bus number 4
ehci_hcd 00:1d.7: enabled 64bit PCI DMA
PCI: cache line size of 128 is not supported by device 00:1d.7
ehci_hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
hub.c: USB hub found
hub.c: 6 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
hub.c: connect-debounce failed, port 1 disabled
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,5), internal journal
Adding Swap: 1052248k swap-space (priority -1)
hub.c: new USB device 00:1d.0-1, assigned address 2
usb-uhci.c: interrupt, status 3, frame# 1860
input: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb1:2.0
SCSI subsystem driver Revision: 1.00
hdc: attached ide-scsi driver.
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: TEAC Model: DV-W50E Rev: 1.10
Type: CD-ROM ANSI SCSI revision: 02
IA-32 Microcode Update Driver: v1.11 <tigran@veritas.com>
microcode: CPU0 no microcode found! (sig=f27, pflags=4)
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
inserting floppy driver for 2.4.22-1.2115.nptl
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 9 for device 02:02.0
PCI: Sharing IRQ 9 with 00:1d.2
PCI: Sharing IRQ 9 with 00:1f.1
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 Fast Ethernet at 0xe2c99c00, 00:10:a7:08:e4:63, IRQ 9
eth0: Identified 8139 chip type 'RTL-8139C'
divert: freeing divert_blk for eth0
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (4090 buckets, 32720 max) - 292 bytes per conntrack
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 9 for device 02:02.0
PCI: Sharing IRQ 9 with 00:1d.2
PCI: Sharing IRQ 9 with 00:1f.1
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 Fast Ethernet at 0xe2cb9c00, 00:10:a7:08:e4:63, IRQ 9
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: link down
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
lp0: using parport0 (polling).
lp0: console ready
Intel 810 + AC97 Audio, version 0.24, 15:50:18 Oct 29 2003
PCI: Found IRQ 3 for device 00:1f.5
PCI: Sharing IRQ 3 with 00:1f.3
PCI: Sharing IRQ 3 with 02:04.0
PCI: Setting latency timer of device 00:1f.5 to 64
i810: Intel ICH4 found at IO 0xe080 and 0xe400, MEM 0xffaff800 and 0xffaff400, IRQ 3
i810: Intel ICH4 mmio at 0xe2ce6800 and 0xe2ce8400
i810_audio: Primary codec has ID 2
i810_audio: Audio Controller supports 6 channels.
i810_audio: Defaulting to base 2 channel mode.
i810_audio: Resetting connection 0
i810_audio: Connection 0 with codec id 2
ac97_codec: AC97 Audio codec, id: ADS116 (Unknown)
i810_audio: AC'97 codec 2 supports AMAP, total channels = 2
Andrew
:)
je_fro
03-24-2005, 02:44 PM
So why are we talking about your IDE chipset again?
Oh yeah, just make sure it's built in, with a <*> instead of a <M>.
In regards to make menuconfig, I would go through every single bit of it, disabling what you don't need, and building in (<*>) what you need all the time, and making as modules (<M>) stuff that you might use SOME of the time.
But that's just me.
bwkaz
03-24-2005, 07:59 PM
Originally posted by andrew anand
This is the output from lspci
Is this line what I am looking for?
00:1f.1 IDE interface: Intel Corp. 82801DB Ultra ATA Storage Controller (rev 02) Yep.
Set CONFIG_BLK_DEV_PIIX to "y", or go through menuconfig and turn on "Device Drivers" -> "ATA/ATAPI/MFM/RLL support" -> "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support" -> PCI IDE chipset support" -> "Generic PCI bus-master DMA support" -> "Intel PIIXn chipsets support".
Many of those are on the same screen, so you'll just have to make sure they're all set to <*> (to change them to that, use the up & down arrow keys until the setting is highlighted, and hit the "Y" key).
justlinux.com
Copyright Internet.com Inc. All Rights Reserved.