Old Release
Dear List I'm new int this list and noob in Debian, but already success install my first Debian Woody 3.0r3. My question is : 1. Why in this release, package such as KDE, XFree86..etc even the kernel it self seem old version. 2. How to made my own linux disto from debian ? please give me reference. regards reza -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Old Release
Ok, you are asking two questions here, Before answering them, can I point you at http://catb.org/~esr/faqs/smart-questions.html which will make getting answers to your debian based questions easier. Thanks for the link, This is because you are running woody, also known as stable. The idea behind stable is that it is very stable, stable enough to run for years without crashing, stable enough that you could forget your root password to a woody server and it wouldn't be a problem, stable enough that the very earth could be rent asunder a woody box and it wouldn't fall over. Because most people don't have the need for such a platform, and would prefer a more up to date packages, debian has two other streams. They are called steams because your can't really install them. Instead you install stable and then jump on a stream. The two streams: Testing aka Sarge This is the next stable release and the debian devs upload new packages in a effort to fix all the bugs in it. It will be released to replace woody at some point. unstable aka sid This is where the newest packages are tested. Unstable is very cutting edge, with new versions as up to date as possible. to give an example of this, when kde 3.3 was released, it was in unstable before any other distro had it. More information about both streams is just a google away. to switch to one of the two streams open the file /etc/apt/sources.list and change all references to stable with testing or unstable. Then run apt-get update && apt-get dist-upgrade . Warning: this may well break your system. once again, more information is a google away my /etc/apt/source.list get file from /cdrom, i have 7 CD of woody, and all line references to unstable. here is some snip for detail; deb cdrom:[Debian GNU/Linux 3.0r3 _Woody_ - Official i386 Binary-6 (20041027)]/ unstable contrib main non-US/contrib non-US/main non-US/non-free non-free debian:/# apt-get update && apt-get dist-upgrade Reading Package Lists... Done Building Dependency Tree... Done Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. how do i upgrade my package, (ex:KDE), should i switch my source to debian package repository ? and if yes, what repository should i use ? please enlight this noob. regards reza -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
distro maker...
Dear All, I'm interested in make a linux distro based on debian, just like as ubuntu, knoppix or libranet does. Can someone give me reference..howto..URL link of how to do that ? any kind help will appriciated regards reza -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kernel 2.6.8 won't boot
Dear Lists, I'm stuck with compiling debian kernel-2.6.8 source at Sarge, this is what exactly i did... debian:/usr/src# ln -s kernel-source-2.6.8 linux debian:/boot# cd /usr/src/linux debian:/usr/src/linux# cp /root/config .config debian:/usr/src/linux#patch -p1 debian:/usr/src/linux#make menuconfig debian:/usr/src#make-kpkg --initrd --revision=custom.1.0 kernel_image sucess- debian:/usr/src/linux# cd ../ debian:/usr/src# ls kernel-image-2.6.8_custom.1.0_i386.deb kernel-patches kernel-source-2.6.8 kernel-source-2.6.8.tar.bz2 linux debian:/usr/src# dpkg -i kernel-image-2.6.8_custom.1.0_i386.deb ---sucess--- but new compile kernel wont boot with this error... RAMDISK: cramfs file system found at block 0 RAMDISK: loading 3620 block [1 disk] into ramdisk done.. Kernel Panic:VFS:unable to mount root fs on unknown_block(3.1) please help me...to solved this problem.. here is .config and menu.lst in attach regards reza # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y # CONFIG_STANDALONE is not set CONFIG_BROKEN_ON_SMP=y # # General setup # CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_LOG_BUF_SHIFT=17 CONFIG_HOTPLUG=y CONFIG_EVLOG=y # CONFIG_EVLOG_FWPRINTK is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set # # Class Based Kernel Resource Management # CONFIG_CKRM=y CONFIG_RCFS_FS=m CONFIG_CKRM_TYPE_TASKCLASS=y CONFIG_CKRM_RES_NUMTASKS=m CONFIG_CKRM_TYPE_SOCKETCLASS=y CONFIG_CKRM_RBCE=m CONFIG_CKRM_CRBCE=m CONFIG_DELAY_ACCT=y CONFIG_KALLSYMS=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set CONFIG_M586=y # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set CONFIG_X86_GENERIC=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_ALIGNMENT_16=y CONFIG_X86_INTEL_USERCOPY=y # CONFIG_HPET_TIMER is not set # CONFIG_HPET_EMULATE_RTC is not set # CONFIG_SMP is not set # CONFIG_PREEMPT is not set CONFIG_X86_UP_APIC=y CONFIG_X86_UP_IOAPIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set CONFIG_X86_MCE_P4THERMAL=y CONFIG_TOSHIBA=m CONFIG_I8K=m CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # CONFIG_EDD=m # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_HIGHMEM=y CONFIG_HIGHPTE=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_EFI=y CONFIG_BOOT_IOREMAP=y CONFIG_REGPARM=y # # Special options # CONFIG_PROC_MM=y # # Power management options (ACPI, APM) # CONFIG_PM=y CONFIG_SOFTWARE_SUSPEND=y # CONFIG_PM_DISK is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m CONFIG_ACPI_ASUS=m CONFIG_ACPI_TOSHIBA=m # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y CONFIG_ACPI_INITRD=y # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=y # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_APM_DO_ENABLE=y # CONFIG_APM_CPU_IDLE is not set CONFIG_APM_DISPLAY_BLANK=y # CONFIG_APM_RTC_IS_GMT is not set CONFIG_APM_ALLOW_INTS=y # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_PROC_INTF=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m # CONFIG_CP
Re: Kernel 2.6.8 won't boot
Eric Gaumer wrote: On Tue, 2005-01-04 at 00:44 +0700, Muhammad Reza wrote: Dear Lists, I'm stuck with compiling debian kernel-2.6.8 source at Sarge, this is what exactly i did... debian:/usr/src# ln -s kernel-source-2.6.8 linux debian:/boot# cd /usr/src/linux debian:/usr/src/linux# cp /root/config .config debian:/usr/src/linux#patch -p1 debian:/usr/src/linux#make menuconfig debian:/usr/src#make-kpkg --initrd --revision=custom.1.0 kernel_image sucess- debian:/usr/src/linux# cd ../ debian:/usr/src# ls kernel-image-2.6.8_custom.1.0_i386.deb kernel-patches kernel-source-2.6.8 kernel-source-2.6.8.tar.bz2 linux debian:/usr/src# dpkg -i kernel-image-2.6.8_custom.1.0_i386.deb ---sucess--- but new compile kernel wont boot with this error... RAMDISK: cramfs file system found at block 0 RAMDISK: loading 3620 block [1 disk] into ramdisk done.. Kernel Panic:VFS:unable to mount root fs on unknown_block(3.1) please help me...to solved this problem.. here is .config and menu.lst in attach Since you are using a ramdisk, it would be helpful if you could post the contents of the loadmodules file on the ramdisk itself. You are most likely missing some modules needed to mount the filesystem since (3,1) is hda1. ]$ mount -o loop /boot/initrd-xxx /mnt/tmp ]$ cat /mnt/tmp/loadmodules lspci may also help. What kernel are you currently running? Any special file system stuff like RAID or SATA? Thanks for good advice this differnet betwen 2.4.7 and 2.6.8 loadmodules.. ---2.4.7 debian:/mnt/tmp# cat loadmodules modprobe -k vesafb > /dev/null 2>&1 modprobe -k fbcon 2> /dev/null modprobe -k unix 2> /dev/null modprobe -k pdc202xx_new > /dev/null 2>&1 modprobe -k trm290 > /dev/null 2>&1 modprobe -k triflex > /dev/null 2>&1 modprobe -k siimage > /dev/null 2>&1 modprobe -k adma100 > /dev/null 2>&1 modprobe -k cs5530 > /dev/null 2>&1 modprobe -k rz1000 > /dev/null 2>&1 modprobe -k ns87415 > /dev/null 2>&1 modprobe -k pdc202xx_old > /dev/null 2>&1 modprobe -k alim15x3 > /dev/null 2>&1 modprobe -k sc1200 > /dev/null 2>&1 modprobe -k generic > /dev/null 2>&1 modprobe -k opti621 > /dev/null 2>&1 modprobe -k piix > /dev/null 2>&1 modprobe -k hpt366 > /dev/null 2>&1 modprobe -k hpt34x > /dev/null 2>&1 modprobe -k serverworks > /dev/null 2>&1 modprobe -k amd74xx > /dev/null 2>&1 modprobe -k aec62xx > /dev/null 2>&1 modprobe -k via82cxxx > /dev/null 2>&1 modprobe -k sis5513 > /dev/null 2>&1 modprobe -k slc90e66 > /dev/null 2>&1 modprobe -k cy82c693 > /dev/null 2>&1 modprobe -k atiixp > /dev/null 2>&1 modprobe -k cmd640 > /dev/null 2>&1 modprobe -k cmd64x > /dev/null 2>&1 modprobe -k ide-detect modprobe -k ide-disk --2.6.8--- modprobe -k unix 2> /dev/null modprobe -k ata_piix modprobe -k sd_mod modprobe -k cs5520 > /dev/null 2>&1 modprobe -k cs5530 > /dev/null 2>&1 I'm now confused, in my .config for 2.6.8 kernel (attach..) , all module that need it already enabled, fyi i get this .config from Suse-9.1 I dont have spesial file system like you said, i just this kernel to be portable... please help me.. regards reza -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6.8 won't boot
Roberto Sanchez wrote: Muhammad Reza wrote: Dear Lists, I'm stuck with compiling debian kernel-2.6.8 source at Sarge, this is what exactly i did... debian:/usr/src# ln -s kernel-source-2.6.8 linux debian:/boot# cd /usr/src/linux debian:/usr/src/linux# cp /root/config .config debian:/usr/src/linux#patch -p1 but new compile kernel wont boot with this error... RAMDISK: cramfs file system found at block 0 RAMDISK: loading 3620 block [1 disk] into ramdisk done.. Kernel Panic:VFS:unable to mount root fs on unknown_block(3.1) please help me...to solved this problem.. here is .config and menu.lst in attach Have you tried without an initrd? Also, do you have /boot on a seperate partition? -Roberto Sanchez I'm already tried without --initrd, the last result it same, kernel won`t boot cause unable to mount root file system. And fyi, with or without --initrd, ext2, ext3 and reiserfs is compiling static to my 2.6.8 kernel. this my mtab from previous good booting kernel... debian:~# uname -a Linux debian 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686 GNU/Linux debian:~# cat /etc/mtab /dev/hda1 / ext3 rw,errors=remount-ro 0 0 proc /proc proc rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs rw 0 0 /dev/hda9 /home ext3 rw 0 0 /dev/hda8 /tmp ext3 rw 0 0 /dev/hda5 /usr ext3 rw 0 0 /dev/hda6 /var ext3 rw 0 0 usbfs /proc/bus/usb usbfs rw 0 0 regards reza -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6.8 won't boot
Eric Gaumer wrote: On Tue, 2005-01-04 at 01:23 +0700, Muhammad Reza wrote: Eric Gaumer wrote: On Tue, 2005-01-04 at 00:44 +0700, Muhammad Reza wrote: Dear Lists, I'm stuck with compiling debian kernel-2.6.8 source at Sarge, this is what exactly i did... debian:/usr/src# ln -s kernel-source-2.6.8 linux debian:/boot# cd /usr/src/linux debian:/usr/src/linux# cp /root/config .config debian:/usr/src/linux#patch -p1 debian:/usr/src/linux#make menuconfig debian:/usr/src#make-kpkg --initrd --revision=custom.1.0 kernel_image sucess- debian:/usr/src/linux# cd ../ debian:/usr/src# ls kernel-image-2.6.8_custom.1.0_i386.deb kernel-patches kernel-source-2.6.8 kernel-source-2.6.8.tar.bz2 linux debian:/usr/src# dpkg -i kernel-image-2.6.8_custom.1.0_i386.deb ---sucess--- but new compile kernel wont boot with this error... RAMDISK: cramfs file system found at block 0 RAMDISK: loading 3620 block [1 disk] into ramdisk done.. Kernel Panic:VFS:unable to mount root fs on unknown_block(3.1) please help me...to solved this problem.. here is .config and menu.lst in attach Since you are using a ramdisk, it would be helpful if you could post the contents of the loadmodules file on the ramdisk itself. You are most likely missing some modules needed to mount the filesystem since (3,1) is hda1. ]$ mount -o loop /boot/initrd-xxx /mnt/tmp ]$ cat /mnt/tmp/loadmodules lspci may also help. What kernel are you currently running? Any special file system stuff like RAID or SATA? Thanks for good advice this differnet betwen 2.4.7 and 2.6.8 loadmodules.. ---2.4.7 debian:/mnt/tmp# cat loadmodules modprobe -k vesafb > /dev/null 2>&1 modprobe -k fbcon 2> /dev/null modprobe -k unix 2> /dev/null modprobe -k pdc202xx_new > /dev/null 2>&1 modprobe -k trm290 > /dev/null 2>&1 modprobe -k triflex > /dev/null 2>&1 modprobe -k siimage > /dev/null 2>&1 modprobe -k adma100 > /dev/null 2>&1 modprobe -k cs5530 > /dev/null 2>&1 modprobe -k rz1000 > /dev/null 2>&1 modprobe -k ns87415 > /dev/null 2>&1 modprobe -k pdc202xx_old > /dev/null 2>&1 modprobe -k alim15x3 > /dev/null 2>&1 modprobe -k sc1200 > /dev/null 2>&1 modprobe -k generic > /dev/null 2>&1 modprobe -k opti621 > /dev/null 2>&1 modprobe -k piix > /dev/null 2>&1 modprobe -k hpt366 > /dev/null 2>&1 modprobe -k hpt34x > /dev/null 2>&1 modprobe -k serverworks > /dev/null 2>&1 modprobe -k amd74xx > /dev/null 2>&1 modprobe -k aec62xx > /dev/null 2>&1 modprobe -k via82cxxx > /dev/null 2>&1 modprobe -k sis5513 > /dev/null 2>&1 modprobe -k slc90e66 > /dev/null 2>&1 modprobe -k cy82c693 > /dev/null 2>&1 modprobe -k atiixp > /dev/null 2>&1 modprobe -k cmd640 > /dev/null 2>&1 modprobe -k cmd64x > /dev/null 2>&1 modprobe -k ide-detect modprobe -k ide-disk --2.6.8--- modprobe -k unix 2> /dev/null modprobe -k ata_piix modprobe -k sd_mod modprobe -k cs5520 > /dev/null 2>&1 modprobe -k cs5530 > /dev/null 2>&1 I'm now confused, in my .config for 2.6.8 kernel (attach..) , all module that need it already enabled, fyi i get this .config from Suse-9.1 I dont have spesial file system like you said, i just this kernel to be portable... Okay ata_piix leads me to believe you are using SATA. Is this correct? The new API (libata) scans for drives on the SCSI bus. Try root=/dev/sda1 (edit the grub entry at boot) Sorry, is not correct, my drive is hda ... regards reza -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6.8 won't boot
Eric Gaumer wrote: On Tue, 2005-01-04 at 02:05 +0700, Muhammad Reza wrote: Eric Gaumer wrote: Dear Lists, I'm stuck with compiling debian kernel-2.6.8 source at Sarge, this is what exactly i did... debian:/usr/src# ln -s kernel-source-2.6.8 linux debian:/boot# cd /usr/src/linux debian:/usr/src/linux# cp /root/config .config debian:/usr/src/linux#patch -p1 debian:/usr/src/linux#make menuconfig debian:/usr/src#make-kpkg --initrd --revision=custom.1.0 kernel_image sucess- debian:/usr/src/linux# cd ../ debian:/usr/src# ls kernel-image-2.6.8_custom.1.0_i386.deb kernel-patches kernel-source-2.6.8 kernel-source-2.6.8.tar.bz2 linux debian:/usr/src# dpkg -i kernel-image-2.6.8_custom.1.0_i386.deb ---sucess--- but new compile kernel wont boot with this error... RAMDISK: cramfs file system found at block 0 RAMDISK: loading 3620 block [1 disk] into ramdisk done.. Kernel Panic:VFS:unable to mount root fs on unknown_block(3.1) please help me...to solved this problem.. here is .config and menu.lst in attach Since you are using a ramdisk, it would be helpful if you could post the contents of the loadmodules file on the ramdisk itself. You are most likely missing some modules needed to mount the filesystem since (3,1) is hda1. ]$ mount -o loop /boot/initrd-xxx /mnt/tmp ]$ cat /mnt/tmp/loadmodules lspci may also help. What kernel are you currently running? Any special file system stuff like RAID or SATA? Thanks for good advice this differnet betwen 2.4.7 and 2.6.8 loadmodules.. I'm now confused, in my .config for 2.6.8 kernel (attach..) , all module that need it already enabled, fyi i get this .config from Suse-9.1 I dont have spesial file system like you said, i just this kernel to be portable... Okay ata_piix leads me to believe you are using SATA. Is this correct? The new API (libata) scans for drives on the SCSI bus. Try root=/dev/sda1 (edit the grub entry at boot) Sorry, is not correct, my drive is hda ... Are using SATA? It looks like mkinitrd is saying yes. If you are then your drive is no longer hda. It PIII machine with Asus motherboard, this dmesg output and lspci for futher reference, debian:/usr/src/linux# dmesg | more Linux version 2.4.27-1-386 ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian 1:3.3.4-9)) #1 Fri Sep 3 06:24:46 UTC 2004 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 07ffc000 (usable) BIOS-e820: 07ffc000 - 07fff000 (ACPI data) BIOS-e820: 07fff000 - 0800 (ACPI NVS) BIOS-e820: - 0001 (reserved) 127MB LOWMEM available. On node 0 totalpages: 32764 zone(0): 4096 pages. zone(1): 28668 pages. zone(2): 0 pages. ACPI disabled because your bios is from 2000 and too old You can enable it with acpi=force Kernel command line: root=/dev/hda1 ro Local APIC disabled by BIOS -- reenabling. Found and enabled local APIC! Initializing CPU#0 Detected 503.533 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 1002.70 BogoMIPS Memory: 123556k/131056k available (1065k kernel code, 7112k reserved, 457k data, 96k init, 0k highmem) Dentry cache hash table entries: 16384 (order: 5, 131072 bytes) Inode cache hash table entries: 8192 (order: 4, 65536 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU: After generic, caps: 0383fbff CPU: Common caps: 0383fbff CPU: Intel Pentium III (Coppermine) stepping 06 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. Checking for popad bug... OK. POSIX conformance testing by UNIFIX enabled ExtINT on CPU#0 ESR value before enabling vector: ESR value after enabling vector: Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 503.5380 MHz. . host bus clock speed is 100.7073 MHz. cpu: 0, clocks: 1007073, slice: 503536 CPU0 ACPI: Subsystem revision 20040326 ACPI: Interpreter disabled. PCI: PCI BIOS revision 2.10 entry at 0xf0890, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: Using IRQ router VIA [1106/0596] at 00:04.0 Activating ISA DMA hang workarounds. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd VFS: Disk quotas vdquot_6.5.1 devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x0 pty: 256 Unix98 ptys configured Serial
Re: Kernel 2.6.8 won't boot
Eric Gaumer wrote: On Tue, 2005-01-04 at 02:16 +0700, Muhammad Reza wrote: debian:/usr/src/linux# lspci :00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) This is a serial ATA chipset. http://www.linuxmafia.com/faq/Hardware/sata.html Make sure you have sata_via module listed in /etc/mkinitrd/modules and then re-install the 2.6 kernel (this will create a new initrd image). Then at boot time, edit grub so that root=/dev/sda1 I know 2.4 shows the drive as hda but 2.6 will see it as sda because this is how libata works. Almost give up... I did exactly what this lists suggest...(recompile with sata modules, edit grub, and add entry in /etc/mkinitrd/modules) but it's still produce same error when booting the new kernel. Is there any clue...? regards reza reza -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6.8 won't boot
Eric Gaumer wrote: On Tue, 2005-01-04 at 05:19 +0700, Muhammad Reza wrote: Eric Gaumer wrote: On Tue, 2005-01-04 at 02:16 +0700, Muhammad Reza wrote: debian:/usr/src/linux# lspci :00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10) This is a serial ATA chipset. http://www.linuxmafia.com/faq/Hardware/sata.html Make sure you have sata_via module listed in /etc/mkinitrd/modules and then re-install the 2.6 kernel (this will create a new initrd image). Then at boot time, edit grub so that root=/dev/sda1 I know 2.4 shows the drive as hda but 2.6 will see it as sda because this is how libata works. Almost give up... I did exactly what this lists suggest...(recompile with sata modules, edit grub, and add entry in /etc/mkinitrd/modules) but it's still produce same error when booting the new kernel. Is there any clue...? The initrd-tools package is a bit problematic these days. How about just compiling the filesystem stuff directly into the kernel and not using a ramdisk. This will surely fix things providing you've got everything you need compiled into the kernel. If you have any doubts what should be compiled in just add everything from the loadmodules files on both 2.4 and 2.6. I would also make sure the SCSI stuff and SATA stuff is in there as well. You could always fine tune things once you get it booted and can actually see what your using. Before you try this "long" approach, you may want to list every module from the 2.4 loadmodules file in /etc/mkinitrd/modules and reproduce the initrd. Try booting that and see what happens. You are obviously missing a module somewhere and it's just a matter of finding out which one. Don't give up now. This whole experience will strengthen your knowledge. I'm suspicions in .config file that i copied from Suse-9.1 /proc/config.gz The fastest solution that i do now, is install kernel image from source list. regards reza -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
