build kernel
Since release 150, udev requires that support for the CONFIG_SYSFS_DEPRECATED feature is disabled in the running kernel. Please upgrade your kernel before or while upgrading udev. AT YOUR OWN RISK, you can force the installation of this version of udev WHICH DOES NOT WORK WITH YOUR RUNNING KERNEL AND WILL BREAK YOUR SYSTEM AT THE NEXT REBOOT by creating the /etc/udev/kernel-upgrade file. There is always a safer way to upgrade, do not try this unless you understand what you are doing! -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1nkjuk-00061j-00.electro-nic-mail...@f246.mail.ru
Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.
reassign 504016 linux-2.6 thanks On Saturday 01 November 2008, Hans-Joachim Zierke wrote: But I found it by completely disabling almost everything in the BIOS, getting a success, then systematically reenabling stuff. It's the Promise ATA-100 BIOS. If I reset that BIOS from Auto to Disabled, then I get the Ok, booting the kernel message. The A7V Board has an ATA-66 controller in the chipset, plus an additional ATA-100 Promise controller on the motherboard. The strange thing is that your initial report shows that the initrd and kernel do get loaded from the CD; it just fails to take the next step. As this really looks like a kernel issue, I'm reassigning your report to the kernel team. Maybe they can offer additional help. It could also possibly an isolinux problem. have you tried installing the Lenny kernel on your Etch system and booting that? I won't even know how to do that. ;-) I know how to compile a kernel for the running system with make-kpkg, but that's it. Just download the package from packages.debian.org and install it using 'dpkg -i package'. I'm not a Linux freak, but a user. When I looked for Lenny news on the website, I read that we should try the installer, so I did. Thanks a lot for testing it. We do appreciate that and the fact that you filed your installation report. Unfortunately when you do run into such a problem with Linux it's basically up to the user to find the correct person to look into the problem and to provide any needed info to track it down. Depending on the issue, that can require a significant amount of effort on the user's part. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.
Processing commands for [EMAIL PROTECTED]: reassign 504016 linux-2.6 Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gzready. Bug reassigned from package `installation-reports' to `linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.
On Thursday 30 October 2008, Hans-Joachim Zierke wrote: In expert mode, the result is exactly the same: Loading /install.386/vmlinuz . Loading /install.386/initrd.gz .. ..ready. OK. This is very clearly a kernel problem, not an installer problem. We can try one more thing, but I think you'll have to report this to the upstream kernel developers. Please try booting in expert mode using a current daily built image with the following added parameters: debug earlyprintk=vga,keep edd=off It could also possibly an isolinux problem. have you tried installing the Lenny kernel on your Etch system and booting that? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.
On 01.11.2008 16:08:13, Frans Pop wrote: OK. This is very clearly a kernel problem, not an installer problem. We can try one more thing, but I think you'll have to report this to the upstream kernel developers. Please try booting in expert mode using a current daily built image with the following added parameters: debug earlyprintk=vga,keep edd=off This did not give any other result. But I found it by completely disabling almost everything in the BIOS, getting a success, then systematically reenabling stuff. It's the Promise ATA-100 BIOS. If I reset that BIOS from Auto to Disabled, then I get the Ok, booting the kernel message. The A7V Board has an ATA-66 controller in the chipset, plus an additional ATA-100 Promise controller on the motherboard. The relevant lspci lines: 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/ C PIPC Bus Master IDE (rev 10) 00:0c.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 12) 00:11.0 Mass storage controller: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) (rev 02) It does /not/ help, to set boot priority to SCSI/ATA100 (as I had done), and it does /not/ help, if I don't allow booting from it. The Promise BIOS /must/ be /disabled/ for booting the kernel from SCSI CD. I guess, but don't know, that the Linux boot system ignores the boot priorities of the BIOS, gets confused, and tries to find a CD at the Promise controller. It could also possibly an isolinux problem. have you tried installing the Lenny kernel on your Etch system and booting that? I won't even know how to do that. ;-) I know how to compile a kernel for the running system with make-kpkg, but that's it. I'm not a Linux freak, but a user. When I looked for Lenny news on the website, I read that we should try the installer, so I did. Hans-Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.
Package: Installation-reports Boot method: Booted from CD The following is copied from Etch dmesg sym0: 810a rev 0x12 at pci :00:0c.0 irq 11 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: SCSI BUS has been reset. scsi0 : sym-2.2.3 Vendor: PLEXTOR Model: CD-ROM PX-40TSRev: 1.01 Type: CD-ROM ANSI SCSI revision: 02 target0:0:1: Beginning Domain Validation target0:0:1: asynchronous target0:0:1: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 8) BIOS is SDMS 4.12.0.0, and reports No Emulation mode on BIOS screen while booting. Image version: 157034496 2008-10-28 22:11 debian-LennyBeta2-i386-netinst.iso Second try with daily build debian-testing-i386-netinst.iso from http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/ But it is also reproducible with a Knoppix CD, and therefore probably a general Isolinux problem not limited to the Debian Installer. Date: Oct 29 Machine: Homebuilt 24/7 machine, motherboard ASUS A7V 1.04 with latest BIOS 1011 from 2002, running under Debian Etch normally. SCSI controller is an ASUS SC-200, SDMS BIOS 4.12.0.0 is delivered by the motherboard, as usual for these controllers. Processor: Duron 600 CPU: After generic identify, caps: 0183f9ff c1c7f9ff CPU: After vendor identify, caps: 0183f9ff c1c7f9ff CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 64K (64 bytes/line) CPU: After all inits, caps: 0183f9ff c1c7f9ff 0420 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: AMD Duron(tm) Processor stepping 00 Checking 'hlt' instruction... OK. Memory:SDRAM 100 383MB LOWMEM available. Partitions:FilesystemType 1K-blocks Used Available Use% Mounted on /dev/hda1 ext321342047 456 15813206 22% / tmpfstmpfs 193452 0193452 0% /lib/init/rw udev tmpfs 1024084 10156 1% /dev tmpfstmpfs 193452 8193444 1% /dev/shm /dev/hdc2 ext391658564 44736272 42266256 52% /home /dev/hde1 ext3 476750548 341159516 111373448 76% /home/hajo/Archiv /dev/hdf1 ext3 240362656 143533616 84619240 63% /home/hajo/Archiv/Bahn Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] [1106:0305] (rev 02) 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] [1106:8305] 00:04.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] [1106:0686] (rev 22) 00:04.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 10) 00:04.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 10) 00:04.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 10) 00:04.4 Bridge [0680]: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] [1106:3057] (rev 30) 00:09.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 02) 00:09.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 02) 00:0a.0 Multimedia controller [0480]: Philips Semiconductors TriMedia TM-1300 [1131:5402] (rev 83) 00:0b.0 PCI bridge [0604]: IBM IBM27-82351 [1014:0022] (rev 01) 00:0c.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c810 [1000:0001] (rev 12) 00:0d.0 Multimedia audio controller [0401]: C-Media Electronics Inc CM8738 [13f6:0111] (rev 10) 00:11.0 Mass storage controller [0180]: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) [105a:0d30] (rev 02) 01:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G400/G450 [102b:0525] (rev 04) 02:00.0 Network controller [0280]: Compaq Computer Corporation Netelligent Dual 10/100 TX PCI UTP [0e11:ae40] (rev 10) 02:01.0 Network controller [0280]: Compaq Computer Corporation Netelligent Dual 10/100 TX PCI UTP [0e11:ae40] (rev 10) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E]
Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.
On Thursday 30 October 2008, Hans-Joachim Zierke wrote: Comments/Problems: BIOS boot uneventful, Hostadapter BIOS reports No Emulation mode, Installation CD screen comes up fine with all the help options. After Enter, I get Loading /something-386/vmlinuz . Loading /something-386/initrd.gz ... .ready. After that, the machine stops activity, nothing even after 10 minutes, and does not react to Ctrl-Alt-Del. Hardware reset necessary. Please try booting in expert mode (see advanced menu) and give us the boot log information visible on the screen when it hangs. If it is clear where the problem is, you may only have to give the last few lines. If it is not clear, please provide as much context as possible (a screenshot with a camera is OK as long as it is clear [1]). Cheers, FJP [1] Note that large attachments may not reach the mailinglist, so please check that your message is visible in the mailing list archive: http://lists.debian.org/debian-boot/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504016: Lenny Beta II + daily build, kernel dies after initrd.gz....ready.
On 30.10.2008 17:27:54, Frans Pop wrote: Loading /something-386/vmlinuz . Loading /something-386/initrd.gz ... .ready. Please try booting in expert mode (see advanced menu) and give us the boot log information visible on the screen when it hangs. In expert mode, the result is exactly the same: Loading /install.386/vmlinuz . Loading /install.386/initrd.gz .. ..ready. And that's it. Ciao Hans-Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Unable to build kernel udeb
Hi I am trying to build Build images with a custom kernel $dpkg-buildpackage it gets following error debian/nic-extra-modules-2.6.8.18-386-di lib/modules/2.6.18.8-2-386/kernel/drivers/base/firmware_class.ko debian/irda-modules-2.6.8.18-386-di lib/modules/2.6.18.8-2-386/kernel/drivers/base/firmware_class.ko some modules are in more than one package command exited with status 255 make: *** [binary-arch] Error 2 please give any clue to over come such problem?? I am using source package linux-kernel-di-i386-2.6-1.02sarge4 and working on debian sarge (kernel 2.4.27-2-386) I have successfully build kernel deb, installed and reboot with it using make-kpkg and Murad - Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.
Re: Unable to build kernel udeb
hasan murad wrote: I am trying to build Build images with a custom kernel $dpkg-buildpackage it gets following error debian/nic-extra-modules-2.6.8.18-386-di lib/modules/2.6.18.8-2-386/kernel/drivers/base/firmware_class.ko debian/irda-modules-2.6.8.18-386-di lib/modules/2.6.18.8-2-386/kernel/drivers/base/firmware_class.ko some modules are in more than one package command exited with status 255 make: *** [binary-arch] Error 2 please give any clue to over come such problem?? touch ignore-dups # run in the top level of your package This isn't a clean fix, but it is designed to work around the problem easily. The clean fix is probably to make irda-modules and nic-extra-modules depend on firmware-modules, and put firmware_class in firmware_modules. -- see shy jo signature.asc Description: Digital signature
Re: build kernel problem
On Tue, Jul 15, 2003 at 03:15:22PM +1000, Jennifer wrote: Dear Debian people I am newly getting to start to learn Debian, and try to get Debian working on my PC. I used Debian 3.0 Woody CD set (7 of them) to install. And the kernel version is 2.2.20. For I need to install Oracle9i on this Debian, so I need to upgrade kernel to 2.4.xx I downloaded kernel-image-2.4.21-2-386_2.4.21-2_i386.deb from Debian site. And I copied this image file to /usr/src/ Then I cd to /usr/src I ran the command dpkg --install kernel-image-2.4.21-2-386_2.4.21-2_i386.deb. The console told me the following error message: You are attempting to install an initrd kernel image (version 2.4.21-2-386). but you do not seem to have a mkinitrd command in the path. This will break the installation. I am aborting now. Could not find mkinitrd in path at /var/lib/dpkg/tmp.ci/preinst line 165.dpkg: error processing /usr/src/kernel-image(--install) So I used command of find / -name mkinitrd. And there is no result. I also used man mkinitrd, and it says no man entry for mkinitrd. In this case, what should I do? Go to http://www.debian.org/distrib/packages search for kernel-image-2.4 in stable (woody is the current stable release) click a suitable package e.g. http://packages.debian.org/stable/base/kernel-image-2.4.18-386.html See there that the packages depends on the package initrd-tools which provides the program mkinitrd. I think that you overruled dependencies, dpkg --install package respects them. Your advice will be highly appreciated. Thank you very much. Please use next time '[EMAIL PROTECTED]' for a more installer related issue. Jennifer Z Geert Stappers pgp0.pgp Description: PGP signature
build kernel problem
Dear Debian people I am newly getting to start to learn Debian, and try to get Debian working on my PC. I used Debian 3.0 Woody CD set (7 of them) to install. And the kernel version is 2.2.20. For I need to install Oracle9i on this Debian, so I need to upgrade kernel to 2.4.xx I downloaded "kernel-image-2.4.21-2-386_2.4.21-2_i386.deb" from Debian site. And I copied this image fileto /usr/src/ Then I cd to /usr/src I ran the command " dpkg --install kernel-image-2.4.21-2-386_2.4.21-2_i386.deb". The console told me the following error message: You are attempting to install an initrd kernel image (version 2.4.21-2-386). but you do not seem to have a mkinitrd command in the path. This will break the installation. I am aborting now. Could not find mkinitrd in path at /var/lib/dpkg/tmp.ci/preinst line 165.dpkg: error processing /usr/src/kernel-image(--install) So I used command of "find / -name mkinitrd". And there is no result. I also used "man mkinitrd", and it says no man entry for mkinitrd. In this case, what should I do? Your advice will be highly appreciated. Thank you very much. Jennifer Z
