[gentoo-user] kernel panic not syncing
I have a "kernel panic not syncing" when sometimes trying to boot the PC, it small intel "atom" processor Here is the image: https://imgur.com/a/dDXUx3t Many times when I press the power button it keeps flashing three times, but wont boot. -- Thelma
Re: [gentoo-user] kernel panic - lilo can't find boot
On Sun, Jul 24, 2022 at 05:15:48PM +0200, k...@aspodata.se wrote > WD800BEVS-08 is a 5400rpm 2.5inch sata disk. > Go into the bios and set up sata to be AHCI. Thanks for the additional details. At Neil Bothwick's suggestion I've already toggled the BIOS from SATA to AHCI, and the system now boots up fine. I'm currently running an update world on it. -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] kernel panic - lilo can't find boot
On Sun, Jul 24, 2022 at 02:31:47PM +0100, Neil Bothwick wrote > It looks like your boot partition is not found, which points to a disk > driver issue. Check the BIOS of the computer to make sure it is using > SATA for the controller, or whatever your kernel is set up to use. To quote Elvis... "Thank you, thank you, thank you very very much". I went into the BIOS, toggled from "SATA" to "AHCI", and it booted up just fine. I'm now running update world on the laptop. -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] kernel panic - lilo can't find boot
Walter Dnes: > VFS: Cannot open device "801" or unknown-block (8,1): error -6 > Please append a correct "root=" boot option: here are the available > partitions: > Kernel panic - not syncing: VFS: Unable to mount root on unknown-block (8,1) ... > I've pulled in a working configuration from an old backup, so it > should work. ... > Disk model: WDC WD800BEVS-08 ... > image = /boot/kernel.production > root = /dev/sda1 > label = Production > read-only # read-only for checking > append = "noexec=on net.ifnames=0 intel_pstate=disable ipv6.disable=1" ... The kernel is missing the driver for your disk device. 801 is /dev/sda1: # ls -l /dev/sda1 brw-rw 1 root disk 8, 1 Aug 4 2013 /dev/sda1 WD800BEVS-08 is a 5400rpm 2.5inch sata disk. Go into the bios and set up sata to be AHCI. You have no initrd/initramfs so: "SCSI disk support" "Serial ATA and Parallel ATA drivers (libata)" "AHCI SATA support" and possilbe also "Platform AHCI SATA support" driver must be compiled in in the kernel. You can check that by doing something like: # grep BLK_DEV_SD= /boot/config.production CONFIG_BLK_DEV_SD=y # grep CONFIG_SATA_AHCI /boot/config.production CONFIG_SATA_AHCI=y CONFIG_SATA_AHCI_PLATFORM=y You must also compile in the filesystem used for / (perhaps it is ext4). # grep CONFIG_EXT4_FS= /boot/config.production CONFIG_EXT4_FS=y Every time you change the kernel you have to rerun lilo. Regards, /Karl Hammar
Re: [gentoo-user] kernel panic - lilo can't find boot
On Sun, 24 Jul 2022 07:01:21 -0400, Walter Dnes wrote: > I'm trying to revive an older Lenovo. It has worked in the past. > Here is the kernel panic error (3 lines)... > > VFS: Cannot open device "801" or unknown-block (8,1): error -6 > Please append a correct "root=" boot option: here are the available > partitions: Kernel panic - not syncing: VFS: Unable to mount root on > unknown-block (8,1) It looks like your boot partition is not found, which points to a disk driver issue. Check the BIOS of the computer to make sure it is using SATA for the controller, or whatever your kernel is set up to use. -- Neil Bothwick The thrill of victory, the agony of delete. pgplmWSOX7k6Y.pgp Description: OpenPGP digital signature
Re: [gentoo-user] kernel panic - lilo can't find boot
On 24/07/2022 12:01, Walter Dnes wrote: I'm trying to revive an older Lenovo. It has worked in the past. Here is the kernel panic error (3 lines)... VFS: Cannot open device "801" or unknown-block (8,1): error -6 Please append a correct "root=" boot option: here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root on unknown-block (8,1) I've pulled in a working configuration from an old backup, so it should work. I'm also listing "fdisk -l", "ll /boot", and /etc/lilo.conf (the machine is too old for UEFI). Any ideas? Dunno about modern lilo, and I get the impression from what you're saying that the kernel may have loaded but be crashing looking for root? But my memories of lilo was it was very important you had to re-run it every time you changed kernel, because it didn't know where the kernel was by path, it coded the actual lba reference into the boot code. So that might mean, if the kernel has been upgraded, an old boot config might not work. I know older SUSE install media had "boot system on disk" as one of their options - might that work if you can boot from CD-Rom or USB? Cheers, Wol
[gentoo-user] kernel panic - lilo can't find boot
I'm trying to revive an older Lenovo. It has worked in the past.
Here is the kernel panic error (3 lines)...
VFS: Cannot open device "801" or unknown-block (8,1): error -6
Please append a correct "root=" boot option: here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root on unknown-block (8,1)
I've pulled in a working configuration from an old backup, so it
should work. I'm also listing "fdisk -l", "ll /boot", and
/etc/lilo.conf (the machine is too old for UEFI). Any ideas?
===
Disk /dev/sda: 74.53 GiB, 80026361856 bytes, 156301488 sectors
Disk model: WDC WD800BEVS-08
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x16cab3f2
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 134219775 134217728 64G 83 Linux
/dev/sda2 134219776 156301487 22081712 10.5G 82 Linux swap / Solaris
===
drwxr-xr-x 2 root root4096 Jul 24 06:34 .
drwxr-xr-x 21 root root4096 Apr 25 03:16 ..
-rw-r--r-- 1 root root 0 Apr 12 18:57 .keep
-rw--- 1 root root 165376 Jul 24 06:34 .map
-rw-r--r-- 1 root root 3806788 Jul 24 06:30 System.map.experimental
-rw-r--r-- 1 root root 3806788 Jul 24 06:31 System.map.production
-rw-r--r-- 1 root root 512 Jul 24 05:38 boot.0800
-rw-r--r-- 1 root root 106972 Jul 24 06:30 config.experimental
-rw-r--r-- 1 root root 106972 Jul 24 06:31 config.production
-rw-r--r-- 1 root root 7596800 Jul 24 06:30 kernel.experimental
-rw-r--r-- 1 root root 7596800 Jul 24 06:31 kernel.production
===
# Faster, but won't work on all systems:
#compact
# Should work for most systems, and do not have the sector limit:
lba32
# If lba32 do not work, use linear:
#linear
# MBR to install LILO to:
boot = /dev/sda
map = /boot/.map
install = /boot/boot-menu.b # Note that for lilo-22.5.5 or later you
# do not need boot-{text,menu,bmp}.b in
# /boot, as they are linked into the lilo
# binary.
menu-scheme=Wb
prompt
# If you always want to see the prompt with a 15 second timeout:
timeout=150
delay = 50
#
# End LILO global section
#
#
# Linux bootable partition config begins
#
image = /boot/kernel.production
root = /dev/sda1
label = Production
read-only # read-only for checking
append = "noexec=on net.ifnames=0 intel_pstate=disable ipv6.disable=1"
image = /boot/kernel.experimental
root = /dev/sda1
label = Experimental
read-only # read-only for checking
append = "noexec=on net.ifnames=0 intel_pstate=disable ipv6.disable=1"
#
# Linux bootable partition config ends
#
===
--
Walter Dnes
I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
On Wed, Nov 25, 2020 at 12:15 PM wrote: > > On 11/25/2020 02:50 AM, Michael wrote: > > On Wednesday, 25 November 2020 06:30:05 GMT the...@sys-concept.com wrote: > > > >> On 11/24/2020 10:08 PM, the...@sys-concept.com wrote: > >>> I'm getting a kernel panic when booting a new system. > >>> > >>> kernel panic - not syncing: VFS: unable to mount root fs on unknown-block > >>> (0,0) > >>> > >>> fstab: > >>> LABEL=boot /boot vfat > > noauto,noatime1 2 > >>> root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b / > > ext4noatime 0 1 > >>> LABEL=swap noneswap > > sw0 0 > >>> > >>> I even use: emerge --ask sys-kernel/genkernel > >>> genkernel all > >>> > >>> So all the driver are compile-in (nothing should be missing) > >>> > >>> ls -al /boot/vmlinu* /boot/initramfs* > >>> -rwxr-xr-x 1 root root 11221820 Nov 24 21:30 > >>> /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672 > >>> Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920 > >>> Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64 > >> This problem is solved, it seems to me I was booting old kernel. > >> Removing old kernel and re-running: > >> grub-mkconfig -o /boot/grub/grub.cfg > >> > >> Solved the problem. > > > > Glad you got your new disk booting. > > > > Worth mentioning your fstab syntax is not entirely correct. According to > > 'man > > fstab' you can specify a device with LABEL=, as long as you have set > > up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is > > correct. > > > > UUID on the other hand is meant to be specified like so: > > > > UUID= > > > > In your case it would be: > > > > UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b > > > > instead of it being preceded by "root=". > > The "genkernel all" is working but I need to find out which option is it > that allow booting the drive. The genkernel.conf is different from > standard kernel .config > > Removing options from genkernel is not easy. With most initramfs you just pass root=UUID=foo on the kernel command line. In the past genkernel has been quirky - I use dracut and you'd definitely just use root=UUID=foo there. -- Rich
Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
On 11/25/2020 02:50 AM, Michael wrote: > On Wednesday, 25 November 2020 06:30:05 GMT the...@sys-concept.com wrote: > >> On 11/24/2020 10:08 PM, the...@sys-concept.com wrote: >>> I'm getting a kernel panic when booting a new system. >>> >>> kernel panic - not syncing: VFS: unable to mount root fs on unknown-block >>> (0,0) >>> >>> fstab: >>> LABEL=boot /boot vfat > noauto,noatime1 2 >>> root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b / > ext4noatime 0 1 >>> LABEL=swap noneswap > sw0 0 >>> >>> I even use: emerge --ask sys-kernel/genkernel >>> genkernel all >>> >>> So all the driver are compile-in (nothing should be missing) >>> >>> ls -al /boot/vmlinu* /boot/initramfs* >>> -rwxr-xr-x 1 root root 11221820 Nov 24 21:30 >>> /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672 >>> Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920 >>> Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64 >> This problem is solved, it seems to me I was booting old kernel. >> Removing old kernel and re-running: >> grub-mkconfig -o /boot/grub/grub.cfg >> >> Solved the problem. > > Glad you got your new disk booting. > > Worth mentioning your fstab syntax is not entirely correct. According to > 'man > fstab' you can specify a device with LABEL=, as long as you have set > up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is > correct. > > UUID on the other hand is meant to be specified like so: > > UUID= > > In your case it would be: > > UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b > > instead of it being preceded by "root=". The "genkernel all" is working but I need to find out which option is it that allow booting the drive. The genkernel.conf is different from standard kernel .config Removing options from genkernel is not easy.
Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
On 11/25/2020 02:50 AM, Michael wrote: > On Wednesday, 25 November 2020 06:30:05 GMT the...@sys-concept.com wrote: [snip] >>> root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b / [snip] >> >> Solved the problem. > > Glad you got your new disk booting. > > Worth mentioning your fstab syntax is not entirely correct. According to > 'man > fstab' you can specify a device with LABEL=, as long as you have set > up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is > correct. > > UUID on the other hand is meant to be specified like so: > > UUID= > > In your case it would be: > > UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b > > instead of it being preceded by "root=". I've notice it too during booting and corrected it, thanks.
Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0, 0)
On Wednesday, 25 November 2020 06:30:05 GMT the...@sys-concept.com wrote: > On 11/24/2020 10:08 PM, the...@sys-concept.com wrote: > > I'm getting a kernel panic when booting a new system. > > > > kernel panic - not syncing: VFS: unable to mount root fs on unknown-block > > (0,0) > > > > fstab: > > LABEL=boot /boot vfat noauto,noatime 1 2 > > root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b / ext4noatime 0 1 > > LABEL=swap noneswap sw 0 0 > > > > I even use: emerge --ask sys-kernel/genkernel > > genkernel all > > > > So all the driver are compile-in (nothing should be missing) > > > > ls -al /boot/vmlinu* /boot/initramfs* > > -rwxr-xr-x 1 root root 11221820 Nov 24 21:30 > > /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672 > > Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920 > > Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64 > This problem is solved, it seems to me I was booting old kernel. > Removing old kernel and re-running: > grub-mkconfig -o /boot/grub/grub.cfg > > Solved the problem. Glad you got your new disk booting. Worth mentioning your fstab syntax is not entirely correct. According to 'man fstab' you can specify a device with LABEL=, as long as you have set up a filesystem label with e.g. mkfs, or tune2fs. So, your "LABEL=boot" is correct. UUID on the other hand is meant to be specified like so: UUID= In your case it would be: UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b instead of it being preceded by "root=". signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)
Thelma On 11/24/2020 10:08 PM, the...@sys-concept.com wrote: > I'm getting a kernel panic when booting a new system. > > kernel panic - not syncing: VFS: unable to mount root fs on unknown-block > (0,0) > > fstab: > LABEL=boot/boot vfatnoauto,noatime 1 2 > root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b/ > ext4noatime 0 1 > LABEL=swapnoneswapsw 0 0 > > I even use: emerge --ask sys-kernel/genkernel > genkernel all > > So all the driver are compile-in (nothing should be missing) > > ls -al /boot/vmlinu* /boot/initramfs* > -rwxr-xr-x 1 root root 11221820 Nov 24 21:30 > /boot/initramfs-5.4.72-gentoo-x86_64.img > -rwxr-xr-x 1 root root 9036672 Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo > -rwxr-xr-x 1 root root 8513920 Nov 24 21:18 > /boot/vmlinuz-5.4.72-gentoo-x86_64 This problem is solved, it seems to me I was booting old kernel. Removing old kernel and re-running: grub-mkconfig -o /boot/grub/grub.cfg Solved the problem.
[gentoo-user] kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)
I'm getting a kernel panic when booting a new system. kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0) fstab: LABEL=boot /boot vfatnoauto,noatime 1 2 root=UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b / ext4noatime 0 1 LABEL=swap noneswapsw 0 0 I even use: emerge --ask sys-kernel/genkernel genkernel all So all the driver are compile-in (nothing should be missing) ls -al /boot/vmlinu* /boot/initramfs* -rwxr-xr-x 1 root root 11221820 Nov 24 21:30 /boot/initramfs-5.4.72-gentoo-x86_64.img -rwxr-xr-x 1 root root 9036672 Nov 24 10:56 /boot/vmlinuz-5.4.72-gentoo -rwxr-xr-x 1 root root 8513920 Nov 24 21:18 /boot/vmlinuz-5.4.72-gentoo-x86_64 But at the end of the compilation I get: * Kernel compiled successfully! * * --no-bootloader set; Skipping bootloader update ... * * Required kernel parameter: * * root=/dev/$ROOT * * Where $ROOT is the device node for your root partition as the * one specified in /etc/fstab * If you require Genkernel's hardware detection features, you MUST * tell your bootloader to use the provided initramfs file '/boot/initramfs-5.4.72-gentoo-x86_64.img'. * WARNING... WARNING... WARNING... * Additional kernel parameters that *may* be required to boot properly: * Do NOT report kernel bugs as genkernel bugs unless your bug * is about the default genkernel configuration... * * Make sure you have the latest ~arch genkernel before reporting bugs. -- Thelma
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
> > On my boxes with swap files, kernel 5.7.0 barfs; > > # file /swapfile > /swapfile: Linux/i386 swap file (new style), version 1 (4K pages), size > 2097151 pages, no label > # swapon -a > swapon: /swapfile: swapon failed: Invalid argument > > I havent looked into it yet as they're rarely used at all. What kernel are > you using? > FYI this issue is due to fallocate creating files with holes (found via dmesg | grep -i swap). Once I recreated the files with dd if=/dev/zero they were good.
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On Thu, Jun 4, 2020 at 2:24 AM wrote: > When I try to boot I'm getting an error: > > "Kernel panic - not syncing: No working init found. Try passing init= > option to kernel." > > I am running very low on disk space, I think. > I've tried to boot strap the system and remove some files but boot strap > is not working. When I boot from minimal-install gentoo CD I try: > > swapon /dev/sda3 > swapon: /dev/sda3: read swap header failed: Input/output error > > On my boxes with swap files, kernel 5.7.0 barfs; # file /swapfile /swapfile: Linux/i386 swap file (new style), version 1 (4K pages), size 2097151 pages, no label # swapon -a swapon: /swapfile: swapon failed: Invalid argument I havent looked into it yet as they're rarely used at all. What kernel are you using?
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On 3 June 2020 20:38:49 CEST, the...@sys-concept.com wrote: >On 06/03/2020 12:06 PM, J. Roeleveld wrote: >> On 3 June 2020 18:24:47 CEST, the...@sys-concept.com wrote: >>> When I try to boot I'm getting an error: >>> >>> "Kernel panic - not syncing: No working init found. Try passing >init= >>> option to kernel." >>> >>> I am running very low on disk space, I think. >>> I've tried to boot strap the system and remove some files but boot >>> strap >>> is not working. When I boot from minimal-install gentoo CD I try: >>> >>> swapon /dev/sda3 >>> swapon: /dev/sda3: read swap header failed: Input/output error >>> >>> Any solution? >> >> Is this on a new system? Or on an existing system that started >showing this issue after working correctly for a while? >> >> -- >> Joost >> > >The system is old and was working for some time, it has a SSD drive, it >just recently this error showed up. > >-- >Thelma How old are the SSDs? Were they used for swap? How are they connected? The dmesg you sent in the other email makes me think the SSDs are connected to old ATA ports as they mention UDMA instead of Sata speeds. I would definitely suspect: - the drives (incl. SSDs) - other hardware (incl. the disk controller(s)) - memory - PSU As the issue is recent and intermittent, either a recent addition is causing issues, or there is a timing issue occuring during boot. And these can also occur during kernel initialisation. An initramfs with failover to a simple shell could help here as then you can get a dmesg of when the init fails. There is a kernel commandline option that forces the kernel to wait an X amount of time before trying to access the root-partition and starting "init". This is usually needed for USB-boot, but might also be necessary when disks take a bit longer to initialize. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On 06/03/2020 12:06 PM, J. Roeleveld wrote: > On 3 June 2020 18:24:47 CEST, the...@sys-concept.com wrote: >> When I try to boot I'm getting an error: >> >> "Kernel panic - not syncing: No working init found. Try passing init= >> option to kernel." >> >> I am running very low on disk space, I think. >> I've tried to boot strap the system and remove some files but boot >> strap >> is not working. When I boot from minimal-install gentoo CD I try: >> >> swapon /dev/sda3 >> swapon: /dev/sda3: read swap header failed: Input/output error >> >> Any solution? > > Is this on a new system? Or on an existing system that started showing this > issue after working correctly for a while? > > -- > Joost > The system is old and was working for some time, it has a SSD drive, it just recently this error showed up. -- Thelma
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On 06/03/2020 11:28 AM, Dale wrote: > tedheadster wrote: >> Yes, you do need to capture the kernel output. >> >> The usual way is to hook up a serial cable to another computer and >> pipe the output to it. You interrupt the boot (usually by hitting >> or in GRUB), and then edit the kernel command line thus: >> >> console=tty1 console=ttyS0,115200n8 >> >> If you can do that you can give us some debug output. >> >> - Matthew >> >> > > > Could she boot from some other media, mount the partitions to get to > dmesg and get it from that? Or since it may not be mounting any > partitons, would that lead down the wrong path if it is outdated? > > Dale > > :-) :-) When the screen boots I see an output: "Decompressing Linux - Parsing ELF done. Booting the kernel ... next section scrolls very fast. Here is a link to a video (if you can slow it down) https://vimeo.com/user117037821/review/425595417/79e330424c The good news is that I had a luck to boot it; here output of "df -h df -h Filesystem Size Used Avail Use% Mounted on /dev/sda4 458G 372G 63G 86% / tmpfs 396M 1.2M 395M 1% /run dev 10M 0 10M 0% /dev shm 2.0G 4.0K 2.0G 1% /dev/shm cgroup_root 10M 0 10M 0% /sys/fs/cgroup none2.0G 0 2.0G 0% /run/user/1000 and "dmesg" dmesg [0.00] Linux version 4.9.72-gentoo (root@syscon4) (gcc version 6.4.0 (Gentoo 6.4.0-r1 p1.3) ) #3 SMP Wed Jun 3 09:12:45 MDT 2020 [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.9.72-gentoo root=/dev/sda4 ro [0.00] x86/fpu: Legacy x87 FPU detected. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e4000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xcff7] usable [0.00] BIOS-e820: [mem 0xcff8-0xcff8dfff] ACPI data [0.00] BIOS-e820: [mem 0xcff8e000-0xcffd] ACPI NVS [0.00] BIOS-e820: [mem 0xcffe-0xcfff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xffe0-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00012fff] usable [0.00] NX (Execute Disable) protection: active [0.00] SMBIOS 2.4 present. [0.00] DMI: System manufacturer P5E3 Deluxe/P5E3 Deluxe, BIOS 140107/17/2008 [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x13 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-D write-protect [0.00] E-E write-through [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0D000 mask FF000 uncachable [0.00] 1 base 0E000 mask FE000 uncachable [0.00] 2 base 0 mask F write-back [0.00] 3 base 1 mask FE000 write-back [0.00] 4 base 12000 mask FF000 write-back [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: update [mem 0xd000-0x] usable ==> reserved [0.00] e820: last_pfn = 0xcff80 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [880ff780] [0.00] Scanning 1 areas for low memory corruption [0.00] Base memory trampoline at [88099000] 99000 size 24576 [0.00] BRK [0x0212, 0x02120fff] PGTABLE [0.00] BRK [0x02121000, 0x02121fff] PGTABLE [0.00] BRK [0x02122000, 0x02122fff] PGTABLE [0.00] BRK [0x02123000, 0x02123fff] PGTABLE [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000FBB80 14 (v00 ACPIAM) [0.00] ACPI: RSDT 0xCFF8 3C (v01 A_M_I_ OEMRSDT 07000817 MSFT 0097) [0.00] ACPI: FACP 0xCFF80200 84 (v02 A_M_I_ OEMFACP 07000817 MSFT 0097) [0.00] ACPI: DSDT 0xCFF80440 009CA9 (v01 A0834 A0834088 0088 INTL 20060113) [0.00] ACPI: FACS 0xCFF8E000 40 [0.00] ACPI: APIC 0xCFF80390 6C (v01 A_M_I_ OEMAPIC 07000817 MSFT 0097) [0.00] ACPI: MCFG 0xCFF80400 3C (v01 A_M_I_ OEMMCFG 07000817 MSFT 0097) [0.00] ACPI: OEMB 0xCFF8E040 81
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On 3 June 2020 18:52:59 CEST, the...@sys-concept.com wrote: >On 06/03/2020 10:31 AM, Dale wrote: >> the...@sys-concept.com wrote: >>> When I try to boot I'm getting an error: >>> >>> "Kernel panic - not syncing: No working init found. Try passing >init= >>> option to kernel." >>> >>> I am running very low on disk space, I think. >>> I've tried to boot strap the system and remove some files but boot >strap >>> is not working. When I boot from minimal-install gentoo CD I try: >>> >>> swapon /dev/sda3 >>> swapon: /dev/sda3: read swap header failed: Input/output error >>> >>> Any solution? >>> >> >> >> Are you sure you are pointing to the right partition for /, root? >> That's one common reason for that error. >> >> Dale >> >> :-) :-) > >I'm sure, here is my backup fstab from this system: > >/dev/sda2 /boot ext2noauto,noatime 1 2 >/dev/sda3none swapsw >0 0 >/dev/sda4 / ext4noatime 0 1 >/dev/cdrom /mnt/cdrom autonoauto,user >0 0 > >Sometimes the system boot but most of the time it doesn't. So I was >trying to "bootstrap" it to clean up some files. > >-- >Thelma What exactly do you mean with "bootstrap"? -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On 3 June 2020 18:24:47 CEST, the...@sys-concept.com wrote: >When I try to boot I'm getting an error: > >"Kernel panic - not syncing: No working init found. Try passing init= >option to kernel." > >I am running very low on disk space, I think. >I've tried to boot strap the system and remove some files but boot >strap >is not working. When I boot from minimal-install gentoo CD I try: > >swapon /dev/sda3 >swapon: /dev/sda3: read swap header failed: Input/output error > >Any solution? Is this on a new system? Or on an existing system that started showing this issue after working correctly for a while? -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On Wednesday, 3 June 2020 18:28:33 BST Dale wrote: > tedheadster wrote: > > Yes, you do need to capture the kernel output. > > > > The usual way is to hook up a serial cable to another computer and > > pipe the output to it. You interrupt the boot (usually by hitting > > or in GRUB), and then edit the kernel command line thus: > > > > console=tty1 console=ttyS0,115200n8 > > > > If you can do that you can give us some debug output. > > > > - Matthew > > Could she boot from some other media, mount the partitions to get to > dmesg and get it from that? Or since it may not be mounting any > partitons, would that lead down the wrong path if it is outdated? > > Dale > > :-) :-) If the /dev/sda3 partition is the correct swap partition as fdisk reports with a LiveCD, the OP can create a new swap on it and see if it can be activated: mkswap -L SWAP /dev/sda3 swapon /dev/sda3 If there are still I/O errors try reseating the SATA cable, there may be corrosion on the contacts. dmesg with the LiveCD will also reveal any other hardware issues. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
tedheadster wrote: > Yes, you do need to capture the kernel output. > > The usual way is to hook up a serial cable to another computer and > pipe the output to it. You interrupt the boot (usually by hitting > or in GRUB), and then edit the kernel command line thus: > > console=tty1 console=ttyS0,115200n8 > > If you can do that you can give us some debug output. > > - Matthew > > Could she boot from some other media, mount the partitions to get to dmesg and get it from that? Or since it may not be mounting any partitons, would that lead down the wrong path if it is outdated? Dale :-) :-)
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
Yes, you do need to capture the kernel output. The usual way is to hook up a serial cable to another computer and pipe the output to it. You interrupt the boot (usually by hitting or in GRUB), and then edit the kernel command line thus: console=tty1 console=ttyS0,115200n8 If you can do that you can give us some debug output. - Matthew
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On 06/03/2020 10:57 AM, tedheadster wrote: > Can you provide the "Command line:" information from when the kernel > first boots? It is around line 5 or so. > > - Matthew To do it I think I need to record the screen as it boots. -- Thelma
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
Can you provide the "Command line:" information from when the kernel first boots? It is around line 5 or so. - Matthew
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
On 06/03/2020 10:31 AM, Dale wrote: > the...@sys-concept.com wrote: >> When I try to boot I'm getting an error: >> >> "Kernel panic - not syncing: No working init found. Try passing init= >> option to kernel." >> >> I am running very low on disk space, I think. >> I've tried to boot strap the system and remove some files but boot strap >> is not working. When I boot from minimal-install gentoo CD I try: >> >> swapon /dev/sda3 >> swapon: /dev/sda3: read swap header failed: Input/output error >> >> Any solution? >> > > > Are you sure you are pointing to the right partition for /, root? > That's one common reason for that error. > > Dale > > :-) :-) I'm sure, here is my backup fstab from this system: /dev/sda2 /boot ext2noauto,noatime 1 2 /dev/sda3none swapsw 0 0 /dev/sda4 / ext4noatime 0 1 /dev/cdrom /mnt/cdrom autonoauto,user 0 0 Sometimes the system boot but most of the time it doesn't. So I was trying to "bootstrap" it to clean up some files. -- Thelma
Re: [gentoo-user] Kernel panic - not syncing: No working init found.
the...@sys-concept.com wrote: > When I try to boot I'm getting an error: > > "Kernel panic - not syncing: No working init found. Try passing init= > option to kernel." > > I am running very low on disk space, I think. > I've tried to boot strap the system and remove some files but boot strap > is not working. When I boot from minimal-install gentoo CD I try: > > swapon /dev/sda3 > swapon: /dev/sda3: read swap header failed: Input/output error > > Any solution? > Are you sure you are pointing to the right partition for /, root? That's one common reason for that error. Dale :-) :-)
[gentoo-user] Kernel panic - not syncing: No working init found.
When I try to boot I'm getting an error: "Kernel panic - not syncing: No working init found. Try passing init= option to kernel." I am running very low on disk space, I think. I've tried to boot strap the system and remove some files but boot strap is not working. When I boot from minimal-install gentoo CD I try: swapon /dev/sda3 swapon: /dev/sda3: read swap header failed: Input/output error Any solution? -- Thelma
Re: [gentoo-user] Kernel panic on 5.4.2 - not sure of cause yet
On 15/12/2019 01:54, Andrew Udvare wrote: > On 12/12/2019 10:18, Daniel Frey wrote: >> >> I have just installed fresh new gentoo installs with 5.4.2 and both >> machines use nvidia-drivers - I have not seen this at all. >> >> I have been doing a fair bit of compiling on one of the machines and >> haven't had any hiccups whatsoever. >> >> Dan >> > > Thanks for the reply. > > I think I have found the issue in another 3rd party blob-ish driver from > Magewell, which is for my capture card. I removed the capture card > (since this would stop the module from loading) and my system has not > had a panic since. I have not tried to upgrade back to 5.4.2 yet but as > I said before I was getting the error on 5.4.0 too. > > Andrew > For anyone interested, here are some pictures of the panics: https://i.imgsafe.org/5e/5e20756985.jpeg (unknown) https://i.imgsafe.org/5e/5e20754111.jpeg (find_css_set) The driver in question is the one named ProCapture. I am fairly certain this is the cause of the recent panics. I have had some issues with overclocking my system (both CPU and memory) but I do not think this is related. Just for good measure I reseated all my RAM modules. I am currently running 3.7 GHz (from 3.5) with memory overclocked to 2667 MHz. Does not seem to have an issue. Andrew signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Kernel panic on 5.4.2 - not sure of cause yet
On 12/12/2019 10:18, Daniel Frey wrote: > > I have just installed fresh new gentoo installs with 5.4.2 and both > machines use nvidia-drivers - I have not seen this at all. > > I have been doing a fair bit of compiling on one of the machines and > haven't had any hiccups whatsoever. > > Dan > Thanks for the reply. I think I have found the issue in another 3rd party blob-ish driver from Magewell, which is for my capture card. I removed the capture card (since this would stop the module from loading) and my system has not had a panic since. I have not tried to upgrade back to 5.4.2 yet but as I said before I was getting the error on 5.4.0 too. Andrew signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Kernel panic on 5.4.2 - not sure of cause yet
On 2019-12-10 21:31, Andrew Udvare wrote: I have been getting relatively consistent kernel panics on some call to find_css_set and sometimes a stack trace that mentions cgroups. On 5.4.0 I don't get this same crash and I added blocking of auto-loading nvidia under the ramdisk just in case that's the issue, as I was sometimes getting a similar crash on 5.4.0. /etc/default/grub: GRUB_PRELOAD_MODULES=lvm GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd systemd.legacy_systemd_cgroup_controller=yes rd.driver.blacklist=nvidia rd.driver.blacklist=nvidia_modeset rd.driver.blacklist=nvidia_drm" GRUB_GFXPAYLOAD_LINUX="keep" The reason the legacy argument is there is because Docker won't work under the new cgroups, for now. I have a couple of modules, but the one that sticks out most is nvidia. This is the one I see in the stack trace. I have not seen a bug report on Gentoo or Nvidia's end. For now I've masked >5.4.0 gentoo-sources. Anyone else getting a similar issue? Thanks Andrew I have just installed fresh new gentoo installs with 5.4.2 and both machines use nvidia-drivers - I have not seen this at all. I have been doing a fair bit of compiling on one of the machines and haven't had any hiccups whatsoever. Dan
Re: [gentoo-user] Kernel panic on 5.4.2 - not sure of cause yet
On Wednesday, 11 December 2019 06:31:04 CET Andrew Udvare wrote: > I have been getting relatively consistent kernel panics on some call to > find_css_set and sometimes a stack trace that mentions cgroups. Can you provide the full kernel panic (a picture taken with phone or camera attached to an email is fine as well) and tell us at which point this happens? > On 5.4.0 I don't get this same crash and I added blocking of > auto-loading nvidia under the ramdisk just in case that's the issue, as > I was sometimes getting a similar crash on 5.4.0. I am "still" on 5.3.14, but not encountering any kernel panics myself. > /etc/default/grub: > > GRUB_PRELOAD_MODULES=lvm > GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd Not using systemd myself. > systemd.legacy_systemd_cgroup_controller=yes rd.driver.blacklist=nvidia > rd.driver.blacklist=nvidia_modeset rd.driver.blacklist=nvidia_drm" > GRUB_GFXPAYLOAD_LINUX="keep" > > The reason the legacy argument is there is because Docker won't work > under the new cgroups, for now. > > I have a couple of modules, but the one that sticks out most is nvidia. > This is the one I see in the stack trace. I have not seen a bug report > on Gentoo or Nvidia's end. Nvidia (and some other modules) "taint" the kernel. Any module that "taints" the kernel WILL be listed when a kernel-panic occurs. I never found that info really helpful as I never had those modules to be the cause. > For now I've masked >5.4.0 gentoo-sources. > > Anyone else getting a similar issue? No, but an upgrade to 5.4.x is on my todo-list. -- Joost
[gentoo-user] Kernel panic on 5.4.2 - not sure of cause yet
I have been getting relatively consistent kernel panics on some call to find_css_set and sometimes a stack trace that mentions cgroups. On 5.4.0 I don't get this same crash and I added blocking of auto-loading nvidia under the ramdisk just in case that's the issue, as I was sometimes getting a similar crash on 5.4.0. /etc/default/grub: GRUB_PRELOAD_MODULES=lvm GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd systemd.legacy_systemd_cgroup_controller=yes rd.driver.blacklist=nvidia rd.driver.blacklist=nvidia_modeset rd.driver.blacklist=nvidia_drm" GRUB_GFXPAYLOAD_LINUX="keep" The reason the legacy argument is there is because Docker won't work under the new cgroups, for now. I have a couple of modules, but the one that sticks out most is nvidia. This is the one I see in the stack trace. I have not seen a bug report on Gentoo or Nvidia's end. For now I've masked >5.4.0 gentoo-sources. Anyone else getting a similar issue? Thanks Andrew signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Kernel panic - not syncing - Attempted to kill init (Kernel 3.10.7)
On April 5, 2019 7:49:57 AM UTC, Erwan RIGOLLOT wrote: >Hi all, > >I have a VPS with Gentoo at Tilaa. (tilaa.com) > >Lasts days, I have try to make a new kernel (for update all my system) >and after that I can't boot anymore ! > >I have this message : Kernel panic - not syncing - Attempted to kill >init. > >So, I have restore my old kernel (and after I restore /lib64/modules) >and I have the same message > >The only kernel work now is the first given by Tilaa at the first setup >: vmlinuz-3.8.13-gentoo > >I would like to update all without reinstall but I don't know where I >can look for this problem. > >Have a good day ! Are you using the working config as a start? And compiled in all the virtualisation stuff, just to be certain? Are you using an initramfs? Are any necessary drivers compiled as module? Or is everything compiled-in? Which VM technology does Tilaa use? And can you provide the full error text? The actual cause is likely before this message. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
[gentoo-user] Kernel panic - not syncing - Attempted to kill init (Kernel 3.10.7)
Hi all, I have a VPS with Gentoo at Tilaa. (tilaa.com) Lasts days, I have try to make a new kernel (for update all my system) and after that I can't boot anymore ! I have this message : Kernel panic - not syncing - Attempted to kill init. So, I have restore my old kernel (and after I restore /lib64/modules) and I have the same message The only kernel work now is the first given by Tilaa at the first setup : vmlinuz-3.8.13-gentoo I would like to update all without reinstall but I don't know where I can look for this problem. Have a good day !
Re: [gentoo-user] Kernel Panic fglrx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/24/2011 08:27 PM, Michael Schreckenbauer wrote: Am Montag, 24. Oktober 2011, 18:11:45 schrieb 4k3nd0: On 10/24/11 17:31, Michael Schreckenbauer wrote: Hi, Am Montag, 24. Oktober 2011, 16:36:00 schrieb 4k3nd0: hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N [fglrx] ASIC hang happened is a message indicating a deadlock in a compute-kernel (shader, GPGPU), which in almost all cases is a userspace bug or the timeout in fglrx is too low for the kernel in question. I'm no expert in tweaking fglrx, but afaict there's nothing you can do except wait for an update of the driver. You could also try the opensource-drivers (I think r600 in your case), cause those do their own heuristics to determine hanging or deadlocked compute- kernels. Best, Michael Thank you. Do you think using a newer version of xserver would help? Always worth a try imo. But I wouldn't expect too much from doing this. The driver thinks, that a compute-kernel hangs or is deadlocked. If this assumption is correct, the userspace app needs a fix otherwise the driver is faulty. Is this problem related to running a special app or DE? Or does it happen always? Best, Michael I tried also updating to a newer Version of xorg-xserver als well using the 3.0.0.-generic-12 . Neither did it. The problem seems to be gone with a Linux Kernel 3.1.0 (no-gentoo-patch). I using now the lastet ATI-Driver from the Webpage, but can't tell how stable it is. I'll see it in around a week. But thanks for the help! Greeting's from Germany 4k3nd0 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOp8/IAAoJEARqOhiQNM7ZlvgIALswN1Rh7HxuBvIIM9+VmSI7 bGZ7ezAvX0Su0NfnH1npwrGwFdxfa6q8UVdCdyy7PzEZ54oYfaOUJOnn9FtIGMjs HGtS4Kek4zvxa3yRYH2yoarjTUiyLhTzk5TdbwcfgKQ2RzSPhNB+W2CeEakNPJRv uyIKLJysslwbdgx30hsbldBEV5MbU1tqII8WEk4pzFjE5Se9OgXgo2TQQjOYVx/V PB9w2oTUZ3TIvEV3J+IzbiTPhH2FbeJmRCbiM11JrSGcYPPZC4EzDgunUvnrwtdx 0c8fHZG04INnk4PdfHxCm12HJ+nRPZzTEUe8fe+GQZ1+H3apyIqLWabwTKzAQI0= =cdC0 -END PGP SIGNATURE-
Re: [gentoo-user] Kernel Panic fglrx
Am Mittwoch 26 Oktober 2011, 11:15:52 schrieb 4k3nd0: On 10/24/2011 08:27 PM, Michael Schreckenbauer wrote: Am Montag, 24. Oktober 2011, 18:11:45 schrieb 4k3nd0: On 10/24/11 17:31, Michael Schreckenbauer wrote: Hi, Am Montag, 24. Oktober 2011, 16:36:00 schrieb 4k3nd0: hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N [fglrx] ASIC hang happened is a message indicating a deadlock in a compute-kernel (shader, GPGPU), which in almost all cases is a userspace bug or the timeout in fglrx is too low for the kernel in question. I'm no expert in tweaking fglrx, but afaict there's nothing you can do except wait for an update of the driver. You could also try the opensource-drivers (I think r600 in your case), cause those do their own heuristics to determine hanging or deadlocked compute- kernels. Best, Michael Thank you. Do you think using a newer version of xserver would help? Always worth a try imo. But I wouldn't expect too much from doing this. The driver thinks, that a compute-kernel hangs or is deadlocked. If this assumption is correct, the userspace app needs a fix otherwise the driver is faulty. Is this problem related to running a special app or DE? Or does it happen always? Best, Michael I tried also updating to a newer Version of xorg-xserver als well using the 3.0.0.-generic-12 . which is not a vanilla kernel. vanilla-sources 3.0.7 is -- #163933
[gentoo-user] Kernel Panic fglrx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N I'm using the 11.9 ati-drivers, i got a ATI Readon HD6990 M uname -a Linux Slaxy 3.0.7-gentoo #1 SMP Sat Oct 22 20:44:41 CEST 2011 x86_64 Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz GenuineIntel GNU/Linux Using xorg-server 1.10.4-r1 Greeting's from Germany 4k3nd0 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOpXfQAAoJEARqOhiQNM7Zm9cH/0cs8Pkb8YIGKloBVMQhdFxq +bzFWxbv6aLTqph5uxUkcTZoWYiAZw55TVImaB3RIVbd248RHGrCJMwWywOnNHCY iJ2IVmUrXMFPfwTBSi1L9+2eMEZJqr8jcHCKEUUkJvKpgMcg4koTcFLWu/1RjMdw JecoMUwYZAb+0NC8kN+CQpytn6KlXdoMKYhprQ8QOj2HfCe3ZF5R3Shz62Nj99NB cAx87cX8YLYynPbhrmj2Fg44Q5ItsO4gAw4Z+zAC2Ikih+3jnSzFhwCPk1TRhmcn KffLGxun9eAKaJqKhcWXYWH9k3qYqN16x0/3cESAHFqY5FETOD3PRTu1shS3S0k= =ChkA -END PGP SIGNATURE-
Re: [gentoo-user] Kernel Panic fglrx
Hi, Am Montag, 24. Oktober 2011, 16:36:00 schrieb 4k3nd0: hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N [fglrx] ASIC hang happened is a message indicating a deadlock in a compute-kernel (shader, GPGPU), which in almost all cases is a userspace bug or the timeout in fglrx is too low for the kernel in question. I'm no expert in tweaking fglrx, but afaict there's nothing you can do except wait for an update of the driver. You could also try the opensource-drivers (I think r600 in your case), cause those do their own heuristics to determine hanging or deadlocked compute- kernels. Best, Michael
Re: [gentoo-user] Kernel Panic fglrx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/24/11 17:31, Michael Schreckenbauer wrote: Hi, Am Montag, 24. Oktober 2011, 16:36:00 schrieb 4k3nd0: hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N [fglrx] ASIC hang happened is a message indicating a deadlock in a compute-kernel (shader, GPGPU), which in almost all cases is a userspace bug or the timeout in fglrx is too low for the kernel in question. I'm no expert in tweaking fglrx, but afaict there's nothing you can do except wait for an update of the driver. You could also try the opensource-drivers (I think r600 in your case), cause those do their own heuristics to determine hanging or deadlocked compute- kernels. Best, Michael Thank you. Do you think using a newer version of xserver would help? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOpY5BAAoJEARqOhiQNM7ZwysH/RDWXwBdqLHgKL2R5tSgcOal tL3gYduHOB0vJdITrbm3hvAdq6axvOVW3UXlI9dskLvD/OlA2uH9U70Lbh5GjdZH +bqp8+B8gKBmm0yNIT9/PWPAI+yxSpf1JPXLwV08R5B9F1pRL4sXMhLzcjNbywZM V9V9tBaE/vVaAwvipN8kn9sK7vCorLkA9LcOF0IzNBJDSJIqxUZR9x99O2FA51re 57MyoQPyXxX0zlqe8mHHggLKCZnKYNmI5XNngX++2GL6vUVeerxKqJcPQJZ2vX+V xScQY1jFOqt1QPsVjqmhlTSbND7tcTl5yY6inrdS7ar1FhzpJjHZ8l4hJVS4ayU= =P9Xf -END PGP SIGNATURE-
Re: [gentoo-user] Kernel Panic fglrx
Am Montag 24 Oktober 2011, 16:36:00 schrieb 4k3nd0: hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N I'm using the 11.9 ati-drivers, i got a ATI Readon HD6990 M uname -a Linux Slaxy 3.0.7-gentoo #1 SMP Sat Oct 22 20:44:41 CEST 2011 x86_64 Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz GenuineIntel GNU/Linux Using xorg-server 1.10.4-r1 Greeting's from Germany 4k3nd0 well, the first thing is always: don't use patched kernels. gentoo kernels are patched. Use vanilla. See if the problems persist. fglrx has been solid for me for the last half of a year. With uptimes of two weeks and more, reboots always caused by kernel updates. -- #163933
Re: [gentoo-user] Kernel Panic fglrx
Am Montag, 24. Oktober 2011, 18:11:45 schrieb 4k3nd0: On 10/24/11 17:31, Michael Schreckenbauer wrote: Hi, Am Montag, 24. Oktober 2011, 16:36:00 schrieb 4k3nd0: hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N [fglrx] ASIC hang happened is a message indicating a deadlock in a compute-kernel (shader, GPGPU), which in almost all cases is a userspace bug or the timeout in fglrx is too low for the kernel in question. I'm no expert in tweaking fglrx, but afaict there's nothing you can do except wait for an update of the driver. You could also try the opensource-drivers (I think r600 in your case), cause those do their own heuristics to determine hanging or deadlocked compute- kernels. Best, Michael Thank you. Do you think using a newer version of xserver would help? Always worth a try imo. But I wouldn't expect too much from doing this. The driver thinks, that a compute-kernel hangs or is deadlocked. If this assumption is correct, the userspace app needs a fix otherwise the driver is faulty. Is this problem related to running a special app or DE? Or does it happen always? Best, Michael
Re: [gentoo-user] Kernel Panic fglrx
Am Montag, 24. Oktober 2011, 18:49:36 schrieb Volker Armin Hemmann: Am Montag 24 Oktober 2011, 16:36:00 schrieb 4k3nd0: hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N I'm using the 11.9 ati-drivers, i got a ATI Readon HD6990 M uname -a Linux Slaxy 3.0.7-gentoo #1 SMP Sat Oct 22 20:44:41 CEST 2011 x86_64 Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz GenuineIntel GNU/Linux Using xorg-server 1.10.4-r1 Greeting's from Germany 4k3nd0 well, the first thing is always: don't use patched kernels. gentoo kernels are patched. Use vanilla. See if the problems persist. Good advice in general. But afaik the deadlock detection happens completely in the driver, so I am not convinced other parts of the kernel could cause this. I might be wrong about this though. fglrx has been solid for me for the last half of a year. With uptimes of two weeks and more, reboots always caused by kernel updates. Best, Michael
Re: [gentoo-user] Kernel Panic fglrx
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/24/11 20:27, Michael Schreckenbauer wrote: Am Montag, 24. Oktober 2011, 18:11:45 schrieb 4k3nd0: On 10/24/11 17:31, Michael Schreckenbauer wrote: Hi, Am Montag, 24. Oktober 2011, 16:36:00 schrieb 4k3nd0: hi guys, somehow my fglrx is unstable. Got sometime a crashing fglrx that pulling down the hole system. Someone maybe a idea to fix this? http://pastebin.com/izFnWD7N [fglrx] ASIC hang happened is a message indicating a deadlock in a compute-kernel (shader, GPGPU), which in almost all cases is a userspace bug or the timeout in fglrx is too low for the kernel in question. I'm no expert in tweaking fglrx, but afaict there's nothing you can do except wait for an update of the driver. You could also try the opensource-drivers (I think r600 in your case), cause those do their own heuristics to determine hanging or deadlocked compute- kernels. Best, Michael Thank you. Do you think using a newer version of xserver would help? Always worth a try imo. But I wouldn't expect too much from doing this. The driver thinks, that a compute-kernel hangs or is deadlocked. If this assumption is correct, the userspace app needs a fix otherwise the driver is faulty. Is this problem related to running a special app or DE? Or does it happen always? Best, Michael First i suspect flash player, but it's randomly. There is no special reason i can detect. I will try using the other Kernel, maybe it will help. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOpbjxAAoJEARqOhiQNM7ZnvoH/0tj+06hg/8Si0A0usMDZAYn 3L6vyGjmYmOMW8eTzw7MTE3QFbw8rFrF9KeONzasZU83Z12saA/f+uRZkExcmrM1 kjYCDyzqlOqPz/u76X3HYP8DKIdFxI/mOws/xKf/kdOioI1TOpas5Lm18VkzfWiF JYQvJ7KjUIo/MfqMoTtWjUMn6lDfdQ9fs9DvQCQQuJtPZXp/N4cZb3WFHhXAl8mw LnoWi3vBh7EZv3W4pisaxKVti2cGmUFjzBjarQL89EB67coya6Iy7ZIDWoPHIFC0 WroGKaIFPwbMqWiSZxqSgwWAycpgs6Z9OuiQaz/BysYBQ7cwm6MosBG5stAbU3c= =W9dW -END PGP SIGNATURE-
Re: [gentoo-user] kernel panic on manually built kernel
Volker Armin Hemmann wrote: On Thursday 04 November 2010, dhk wrote: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk grub must point to sda3 not hda3 Yes, I had a similar problem. The device names are different on my machine between genkernel and my own kernel. Make sure to change that in your /etc/fstab as well. Dont know if this is always the case though. Regards, Coert Waagmeester
Re: [gentoo-user] kernel panic on manually built kernel
On 11/08/2010 05:28 AM, Coert Waagmeester wrote: Volker Armin Hemmann wrote: On Thursday 04 November 2010, dhk wrote: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk grub must point to sda3 not hda3 Yes, I had a similar problem. The device names are different on my machine between genkernel and my own kernel. Make sure to change that in your /etc/fstab as well. Dont know if this is always the case though. Regards, Coert Waagmeester I'm booting to an IDE hard disk. Are you say the device name should change from /dev/hda3 to /dev/sda3? If I change it in /etc/fstab and it doesn't work, I'll have problems, I'll probably have to boot to the livecd. Thanks, --dhk
Re: [gentoo-user] kernel panic on manually built kernel
dhk wrote:
On 11/08/2010 05:28 AM, Coert Waagmeester wrote:
Volker Armin Hemmann wrote:
On Thursday 04 November 2010, dhk wrote:
I've always used the genkernel, but now am trying to make a manual one.
I think the kernel is alright since all the default setting seemed
reasonable and the build was easy enough. However, when I boot to it I
get a kernel panic and it complains about the root device /dev/hda3. So
I think the problem has to do with my parameters or syntax in grub.conf.
Below are three grub menu options. The first two have the problem and
the third is the genkernel that works fine. Is there something wrong
with the way the first two are? Thanks.
# This is a Manually built kernel with default settings. kernel panic
title Gentoo Linux x86 2.6.34-r12
root (hd0,0)
kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3
# This is a Manually built kernel with default settings. kernel panic
title Gentoo Linux x86 2.6.34-r12
root (hd0,0)
kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791
splash=verbose video=vesafb:mtrr,ywrap udev
# From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85
# This a genkernel and works
title Gentoo Linux x86 2.6.34-r6
root (hd0,0)
kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc
ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose
video=vesafb:mtrr,ywrap udev
initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6
--dhk
grub must point to sda3 not hda3
Yes, I had a similar problem.
The device names are different on my machine between genkernel and my
own kernel.
Make sure to change that in your /etc/fstab as well.
Dont know if this is always the case though.
Regards,
Coert Waagmeester
I'm booting to an IDE hard disk. Are you say the device name should
change from /dev/hda3 to /dev/sda3? If I change it in /etc/fstab and it
doesn't work, I'll have problems, I'll probably have to boot to the livecd.
Thanks,
--dhk
It has indeed happened to me with an IDE PATA disk.
Try first only to change only your grub config.
Then if you see that the kernel boots fine, you can change /etc/fstab.
If you want you can even use LABELs in fstab.
give your ext{2,3} partitions labels with e2label
and change the device node eg /dev/hda1 in fstab to LABEL=yournewlabel
Regards,
Coert Waagmeester
Re: [gentoo-user] kernel panic on manually built kernel
On Monday 08 November 2010, dhk wrote: On 11/08/2010 05:28 AM, Coert Waagmeester wrote: Volker Armin Hemmann wrote: On Thursday 04 November 2010, dhk wrote: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk grub must point to sda3 not hda3 Yes, I had a similar problem. The device names are different on my machine between genkernel and my own kernel. Make sure to change that in your /etc/fstab as well. Dont know if this is always the case though. Regards, Coert Waagmeester I'm booting to an IDE hard disk. Are you say the device name should change from /dev/hda3 to /dev/sda3? If I change it in /etc/fstab and it doesn't work, I'll have problems, I'll probably have to boot to the livecd. Thanks, --dhk if you are using libata, you have sdX device names.
Re: [gentoo-user] kernel panic on manually built kernel
Coert Waagmeester wrote:
It has indeed happened to me with an IDE PATA disk.
Try first only to change only your grub config.
Then if you see that the kernel boots fine, you can change /etc/fstab.
If you want you can even use LABELs in fstab.
give your ext{2,3} partitions labels with e2label
and change the device node eg /dev/hda1 in fstab to LABEL=yournewlabel
Regards,
Coert Waagmeester
I agree with this 100%. I switched mine to the new PATA drivers and I
couldn't figure out what the drive order was. I used LABELS and it has
worked ever since. The funny thing is, I have a card to hook a SATA
drive up to and it puts it first instead of the drives that are hooked
directly to the mobo. I wasn't expecting that and that was why I could
not get mine to boot with the PATA drives. Bad thing is, the CD/DVD's I
have still use the old IDE drivers so I couldn't even test it by booting
that.
I have not been able to get grub to see the LABELS yet but I'm going to
post fstab so that you have a example that is known to work and not from
a guide:
/dev/disk/by-label/boot/bootext2noatime1 2
/dev/disk/by-label/root/reiserfsdefaults0 1
/dev/disk/by-label/swapnoneswapsw0 0
/dev/disk/by-label/portage/usr/portageext3defaults0 1
/dev/disk/by-label/home/homereiserfsdefaults1 1
/dev/disk/by-label/data/datareiserfsdefaults0 1
Now someone post their grub.conf for us both. I just can't get mine to
work with grub at all. I can't even use tab to find the drives in the
boot menu.
Hope that helps.
Dale
:-) :-)
Re: [gentoo-user] kernel panic on manually built kernel
On 8/11/2010, at 5:56pm, Dale wrote: ... I have not been able to get grub to see the LABELS yet but I'm going to post fstab so that you have a example that is known to work and not from a guide: /dev/disk/by-label/boot/bootext2noatime1 2 /dev/disk/by-label/root/reiserfsdefaults0 1 /dev/disk/by-label/swapnoneswapsw0 0 /dev/disk/by-label/portage/usr/portageext3defaults0 1 /dev/disk/by-label/home/homereiserfsdefaults1 1 /dev/disk/by-label/data/datareiserfsdefaults0 1 I'm not paying enough attention to know whether your above fastab works or not, but /dev/disk/by-label/* seems a relatively ugly way of doing things. I'm pretty sure it's not intended that you use that format, and I have no idea whether it's supposed to work that way. All the guides say to use the word LABEL. That's not a variable or anything - it's the literal word you're supposed to use. I have no idea why a guide should be considered unreliable, but the below is not fabricated - it is from an actual working system: $ grep -ve ^# /etc/fstab LABEL=boot /boot ext2noauto,noatime 1 2 LABEL=/ / ext4noatime 0 1 LABEL=swap noneswapsw 0 0 /dev/cdrom /mnt/cdrom autonoauto,ro,users 0 0 LABEL=space /mnt/space ext4noatime 0 3 shm /dev/shmtmpfs nodev,nosuid,noexec 0 0 $ To me this seems cleaner than your format, and it's certainly fewer characters! Stroller.
Re: [gentoo-user] kernel panic on manually built kernel
Stroller wrote: On 8/11/2010, at 5:56pm, Dale wrote: ... I have not been able to get grub to see the LABELS yet but I'm going to post fstab so that you have a example that is known to work and not from a guide: /dev/disk/by-label/boot/bootext2noatime1 2 /dev/disk/by-label/root/reiserfsdefaults0 1 /dev/disk/by-label/swapnoneswapsw0 0 /dev/disk/by-label/portage/usr/portageext3defaults0 1 /dev/disk/by-label/home/homereiserfsdefaults1 1 /dev/disk/by-label/data/datareiserfsdefaults0 1 I'm not paying enough attention to know whether your above fastab works or not, but /dev/disk/by-label/* seems a relatively ugly way of doing things. I'm pretty sure it's not intended that you use that format, and I have no idea whether it's supposed to work that way. All the guides say to use the word LABEL. That's not a variable or anything - it's the literal word you're supposed to use. I have no idea why a guide should be considered unreliable, but the below is not fabricated - it is from an actual working system: $ grep -ve ^# /etc/fstab LABEL=boot /boot ext2noauto,noatime 1 2 LABEL=/ / ext4noatime 0 1 LABEL=swap noneswapsw 0 0 /dev/cdrom /mnt/cdrom autonoauto,ro,users 0 0 LABEL=space /mnt/space ext4noatime 0 3 shm /dev/shmtmpfs nodev,nosuid,noexec 0 0 $ To me this seems cleaner than your format, and it's certainly fewer characters! Stroller. Well, it does work since it booted as recent as last night when I updated my kernel. I found that somewhere and just copied that to mine. It may be the long way but it does work. I may edit it and try it your way but since mine works and I don't move things to much, not sure it really matters. I sometimes like to get things from a working system, such as what you posted that you use, because sometimes what is in a guide somewhere may not apply to what I am using or even my OS. May be some subtle difference that causes me grief. Since you use Gentoo, yours is a good example to go by. Should have had that a few months ago when I was changing mine over. ;-) It would have saved me some typing as you pointed out. lol Wouldn't happen to have LABELS in your grub.conf file would you? Dale :-) :-)
Re: [gentoo-user] kernel panic on manually built kernel
On 8/11/2010, at 9:34pm, Dale wrote: ... Wouldn't happen to have LABELS in your grub.conf file would you? Nope. I believe this requires an initramfs - see the February 2009 thread, `Using root=LABEL= in grub.conf` for more details of that. I seem to rather have an aversion to initramfses. Stroller.
Re: [gentoo-user] kernel panic on manually built kernel
Stroller wrote: On 8/11/2010, at 9:34pm, Dale wrote: ... Wouldn't happen to have LABELS in your grub.conf file would you? Nope. I believe this requires an initramfs - see the February 2009 thread, `Using root=LABEL= in grub.conf` for more details of that. I seem to rather have an aversion to initramfses. Stroller. Yea, I don't like those either. I think grub2 supports it but I'm not sure. I think that is what I read but it may be just on a todo list or something. Maybe one day. Dale :-) :-)
Re: [gentoo-user] kernel panic on manually built kernel
On Mon, 08 Nov 2010 15:34:08 -0600, Dale wrote: Well, it does work since it booted as recent as last night when I updated my kernel. I found that somewhere and just copied that to mine. It may be the long way but it does work. I may edit it and try it your way but since mine works and I don't move things to much, not sure it really matters. Labels are stored in the filesystem, so LABEL= should always work. /dev/disk/by-label/ is created by udev rules, so it won't work if anything goes wrong with your udev rules or if you have to boot with init=/bin/sh. -- Neil Bothwick Tagline stealing is the sincerest form of flattery. signature.asc Description: PGP signature
Re: [gentoo-user] kernel panic on manually built kernel
Neil Bothwick wrote: On Mon, 08 Nov 2010 15:34:08 -0600, Dale wrote: Well, it does work since it booted as recent as last night when I updated my kernel. I found that somewhere and just copied that to mine. It may be the long way but it does work. I may edit it and try it your way but since mine works and I don't move things to much, not sure it really matters. Labels are stored in the filesystem, so LABEL= should always work. /dev/disk/by-label/ is created by udev rules, so it won't work if anything goes wrong with your udev rules or if you have to boot with init=/bin/sh. Guess I better change that soon then. While udev has been working pretty good here lately, we never know what may happen tomorrow. Thanks for the heads up. Dale :-) :-)
Re: [gentoo-user] kernel panic on manually built kernel
On 8/11/2010, at 10:39pm, Neil Bothwick wrote: On Mon, 08 Nov 2010 15:34:08 -0600, Dale wrote: Well, it does work since it booted as recent as last night when I updated my kernel. I found that somewhere and just copied that to mine. It may be the long way but it does work. I may edit it and try it your way but since mine works and I don't move things to much, not sure it really matters. Labels are stored in the filesystem, so LABEL= should always work. /dev/disk/by-label/ is created by udev rules, so it won't work if anything goes wrong with your udev rules or if you have to boot with init=/bin/sh. Thanks! I approximately figured this when I made my original posting, but don't really feel confident enough about /dev and udev rules to express it properly. That's why I just said I'm not sure the configuration is even supposed to work. Stroller.
Re: [gentoo-user] kernel panic on manually built kernel
On 11/04/2010 03:25 PM, Alan McKinnon wrote: Apparently, though unproven, at 19:36 on Thursday 04 November 2010, dhk did opine thusly: On 11/04/2010 01:08 PM, Neil Bothwick wrote: On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote: The reason I didn't include the exact error is that I can't capture it. I'd have to write it on paper and then reboot to the working kernel. Which is a lot less work than trying to fix the problem by guesswork. I have /boot as ext2 and the rest ext3 with lvm2. $ df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda3 8262068712028 7130344 10% / udev 10240 336 9904 4% /dev /dev/mapper/vg-usr15481840 12867912 1827496 88% /usr /dev/mapper/vg-home 51606140 42781428 6203272 88% /home /dev/mapper/vg-opt 5160576 2635064 2263368 54% /opt /dev/mapper/vg-var15481840 2387500 12307908 17% /var /dev/mapper/vg-tmp 2064208 68708 1890644 4% /tmp shm 512572 0512572 0% /dev/shm The ext2 wasn't compiled in, so I compiled it in and rebooted. I got the same error. kernel panic - not syncing : VFS: unable to mount root FS on unknown-block (2,0) This is what I had. Second extended fs support │ │ │ │* Ext3 journalling file system support │ │ │ │[ ] Default to 'data=ordered' in ext3 │ │ │ │[*] Ext3 extended attributes │ │ │ │[*] Ext3 POSIX Access Control Lists │ │ │ │[*] Ext3 Security Labels This is what I added. * Second extended fs support │ │ │ │[ ] Ext2 extended attributes (NEW) │ │ │ │[ ] Ext2 execute in place support (NEW) │ │ │ │* Ext3 journalling file system support │ │ │ │[ ] Default to 'data=ordered' in ext3 │ │ │ │[*] Ext3 extended attributes │ │ │ │[*] Ext3 POSIX Access Control Lists │ │ │ │[*] Ext3 Security Labels │ │ Thanks, --dhk Is your / partition in or out of the lvm? The / is out of lvm2 and is ext3, /boot is ext2.
Re: [gentoo-user] kernel panic on manually built kernel
Apparently, though unproven, at 11:29 on Friday 05 November 2010, dhk did opine thusly: Is your / partition in or out of the lvm? The / is out of lvm2 and is ext3, /boot is ext2. Ok, that's the easiest way. Seeing inside lvm at boot-time is no fun. But I think Niel spotted your real problem already, you do not have chipset support built into the kernel. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kernel panic on manually built kernel
On 11/04/2010 03:51 PM, Neil Bothwick wrote: On Thu, 04 Nov 2010 13:36:25 -0400, dhk wrote: The ext2 wasn't compiled in, so I compiled it in and rebooted. I got the same error. kernel panic - not syncing : VFS: unable to mount root FS on unknown-block (2,0) It's saying unknown block, not unknown fs. I suspect you haven't compiled in the drivers for your hard disk controller. All my hard disks are sata except the main one with the os on it that is ide. Is a fairly new disk, may be a year old, but should the following driver be compiled in? [ ] Very old hard disk (MFM/RLL/IDE) driver I went back to ide a few years ago because I had problems with sata. First, the system would never boot with more than one sata drive connected. There's something call Staggered Spin-up Detection which load balances the power going to the disks. The bios would error saying that there weren't any hard disks, when really they weren't powered up by time the bios finished checking them. Second, I broke a couple of motherboard sata connectors. Apparently the wire connection to the connector is tighter than the connector's connection to the motherboard, they pulled right off the board.
Re: [gentoo-user] kernel panic on manually built kernel
Apparently, though unproven, at 11:47 on Friday 05 November 2010, dhk did opine thusly: On 11/04/2010 03:51 PM, Neil Bothwick wrote: On Thu, 04 Nov 2010 13:36:25 -0400, dhk wrote: The ext2 wasn't compiled in, so I compiled it in and rebooted. I got the same error. kernel panic - not syncing : VFS: unable to mount root FS on unknown-block (2,0) It's saying unknown block, not unknown fs. I suspect you haven't compiled in the drivers for your hard disk controller. All my hard disks are sata except the main one with the os on it that is ide. Is a fairly new disk, may be a year old, but should the following driver be compiled in? [ ] Very old hard disk (MFM/RLL/IDE) driver No. Those are the ancient drives that shipped with original PCs way way way back in the 80s. Remember those monsters that were never bigger than 32M, were about 4 inches tall and had gigantic cables that were sensitive to be sneezed around? Those were MFM drives. These days libata does IDE as well. Think of it as a sort of universal wrapper around all drives you can buy today and gives a consistent interface. You do still need the driver for the IDE chipset which slots in one level lower. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kernel panic on manually built kernel
On Fri, 05 Nov 2010 05:47:42 -0400, dhk wrote: It's saying unknown block, not unknown fs. I suspect you haven't compiled in the drivers for your hard disk controller. All my hard disks are sata except the main one with the os on it that is ide. Is a fairly new disk, may be a year old, but should the following driver be compiled in? [ ] Very old hard disk (MFM/RLL/IDE) driver It's unlikely, more likely is that you don't have support for your controller chipset built in. Boot fro the genkernel kernel and run lspci -k to see which module it uses for the controller, then compile that into your kernel. Second, I broke a couple of motherboard sata connectors. Apparently the wire connection to the connector is tighter than the connector's connection to the motherboard, they pulled right off the board. That's happened to me a few times too. Fortunately, they push back on almost as easily as they pull off. -- Neil Bothwick WYTYSYDG - What you thought you saw, you didn't get. signature.asc Description: PGP signature
Re: [gentoo-user] kernel panic on manually built kernel
On 11/05/2010 06:33 AM, Neil Bothwick wrote: On Fri, 05 Nov 2010 05:47:42 -0400, dhk wrote: It's saying unknown block, not unknown fs. I suspect you haven't compiled in the drivers for your hard disk controller. All my hard disks are sata except the main one with the os on it that is ide. Is a fairly new disk, may be a year old, but should the following driver be compiled in? [ ] Very old hard disk (MFM/RLL/IDE) driver It's unlikely, more likely is that you don't have support for your controller chipset built in. Boot fro the genkernel kernel and run lspci -k to see which module it uses for the controller, then compile that into your kernel. Second, I broke a couple of motherboard sata connectors. Apparently the wire connection to the connector is tighter than the connector's connection to the motherboard, they pulled right off the board. That's happened to me a few times too. Fortunately, they push back on almost as easily as they pull off. This is what I have. $ lspci -k 00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1) Subsystem: ASUSTeK Computer Inc. K8N-E Kernel driver in use: agpgart-amd64 00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2) Subsystem: ASUSTeK Computer Inc. K8N-E 00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1) Subsystem: ASUSTeK Computer Inc. K8N-E 00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) Subsystem: ASUSTeK Computer Inc. K8N-E Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1) Subsystem: ASUSTeK Computer Inc. K8N-E Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2) Subsystem: ASUSTeK Computer Inc. K8N-E Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2) Subsystem: ASUSTeK Computer Inc. K8N-E Kernel driver in use: forcedeth Kernel modules: forcedeth 00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1) Subsystem: ASUSTeK Computer Inc. K8N-E Kernel driver in use: Intel ICH Kernel modules: snd-intel8x0 I think this may be the missing one(s). I can't find it in the list, but the AMD64/PATA is selected to be compiled in. vv 00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2) Subsystem: ASUSTeK Computer Inc. K8N-E Kernel driver in use: AMD_IDE Kernel modules: pata_acpi, ata_generic, pata_amd 00:0a.0 IDE interface: nVidia Corporation nForce3 Serial ATA Controller (rev a2) Subsystem: ASUSTeK Computer Inc. K8N-E Kernel driver in use: sata_nv Kernel modules: sata_nv, pata_acpi, ata_generic ^^^ 00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2) 00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation NV36 [GeForce FX 5700LE] (rev a1) Kernel driver in use: nvidia Kernel modules: nvidia 02:07.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) Subsystem: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 02:07.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 61) Subsystem: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 02:07.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) Subsystem: VIA Technologies, Inc. USB 2.0 Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 02:07.3 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev 46) Subsystem: VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller Kernel driver in use: ohci1394 Kernel modules: ohci1394 --dhk
Re: [gentoo-user] kernel panic on manually built kernel
On Thursday 04 November 2010, dhk wrote: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk grub must point to sda3 not hda3
[gentoo-user] kernel panic on manually built kernel
I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk
Re: [gentoo-user] kernel panic on manually built kernel
dhk wrote: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk When I get a kernel panic, it's usually because I'm pointing to the wrong partition or I forgot to include the file system that the root partition uses. Since the one you made and the genkernel match up, I would check to make sure you included the correct file system and it is BUILT IN not a module. Hope that helps or someone else comes up with another idea. Dale :-) :-)
Re: [gentoo-user] kernel panic on manually built kernel
Apparently, though unproven, at 18:34 on Thursday 04 November 2010, dhk did opine thusly: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. Why did you think it a good idea to NOT post the *actual* error? Your grub entries are correct. I'll bet money that you built one or more of your chipset drivers, libata, or root filesystem driver as a module. These must not be modules, they must be built-in (otherwise you need an initrd) # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kernel panic on manually built kernel
On 11/04/2010 12:52 PM, Alan McKinnon wrote: Apparently, though unproven, at 18:34 on Thursday 04 November 2010, dhk did opine thusly: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. Why did you think it a good idea to NOT post the *actual* error? Your grub entries are correct. I'll bet money that you built one or more of your chipset drivers, libata, or root filesystem driver as a module. These must not be modules, they must be built-in (otherwise you need an initrd) # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk Thanks all, I check those suggestions and get back to you. The reason I didn't include the exact error is that I can't capture it. I'd have to write it on paper and then reboot to the working kernel. By then it doesn't seem to be in any of the logs. I'll see what I can do about that. Thanks again. --dhk
Re: [gentoo-user] kernel panic on manually built kernel
On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote: The reason I didn't include the exact error is that I can't capture it. I'd have to write it on paper and then reboot to the working kernel. Which is a lot less work than trying to fix the problem by guesswork. -- Neil Bothwick Velilind's Laws of Experimentation: 1. If reproducibility may be a problem, conduct the test only once. 2. If a straight line fit is required, obtain only two data points. signature.asc Description: PGP signature
Re: [gentoo-user] kernel panic on manually built kernel
On 11/04/2010 01:08 PM, Neil Bothwick wrote: On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote: The reason I didn't include the exact error is that I can't capture it. I'd have to write it on paper and then reboot to the working kernel. Which is a lot less work than trying to fix the problem by guesswork. I have /boot as ext2 and the rest ext3 with lvm2. $ df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda3 8262068712028 7130344 10% / udev 10240 336 9904 4% /dev /dev/mapper/vg-usr15481840 12867912 1827496 88% /usr /dev/mapper/vg-home 51606140 42781428 6203272 88% /home /dev/mapper/vg-opt 5160576 2635064 2263368 54% /opt /dev/mapper/vg-var15481840 2387500 12307908 17% /var /dev/mapper/vg-tmp 2064208 68708 1890644 4% /tmp shm 512572 0512572 0% /dev/shm The ext2 wasn't compiled in, so I compiled it in and rebooted. I got the same error. kernel panic - not syncing : VFS: unable to mount root FS on unknown-block (2,0) This is what I had. Second extended fs support │ │ │ │* Ext3 journalling file system support │ │ │ │[ ] Default to 'data=ordered' in ext3 │ │ │ │[*] Ext3 extended attributes │ │ │ │[*] Ext3 POSIX Access Control Lists │ │ │ │[*] Ext3 Security Labels This is what I added. * Second extended fs support │ │ │ │[ ] Ext2 extended attributes (NEW) │ │ │ │[ ] Ext2 execute in place support (NEW) │ │ │ │* Ext3 journalling file system support │ │ │ │[ ] Default to 'data=ordered' in ext3 │ │ │ │[*] Ext3 extended attributes │ │ │ │[*] Ext3 POSIX Access Control Lists │ │ │ │[*] Ext3 Security Labels │ │ Thanks, --dhk
Re: [gentoo-user] kernel panic on manually built kernel
Dale rdalek1...@gmail.com wrote: dhk wrote: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk When I get a kernel panic, it's usually because I'm pointing to the wrong partition or I forgot to include the file system that the root partition uses. Since the one you made and the genkernel match up, I would check to make sure you included the correct file system and it is BUILT IN not a module. Hope that helps or someone else comes up with another idea. He does not have the ramdisk or initrd in his manual ones. That would do it right there. Be sure to generate the ramdisk as well. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] kernel panic on manually built kernel
On 11/04/2010 02:12 PM, cov...@ccs.covici.com wrote: Dale rdalek1...@gmail.com wrote: dhk wrote: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk When I get a kernel panic, it's usually because I'm pointing to the wrong partition or I forgot to include the file system that the root partition uses. Since the one you made and the genkernel match up, I would check to make sure you included the correct file system and it is BUILT IN not a module. Hope that helps or someone else comes up with another idea. He does not have the ramdisk or initrd in his manual ones. That would do it right there. Be sure to generate the ramdisk as well. The documentation doesn't say to use ramdisk or initrd for a manual kernel, only the genkernel.
Re: [gentoo-user] kernel panic on manually built kernel
dhk dhk...@optonline.net wrote: On 11/04/2010 02:12 PM, cov...@ccs.covici.com wrote: Dale rdalek1...@gmail.com wrote: dhk wrote: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk When I get a kernel panic, it's usually because I'm pointing to the wrong partition or I forgot to include the file system that the root partition uses. Since the one you made and the genkernel match up, I would check to make sure you included the correct file system and it is BUILT IN not a module. Hope that helps or someone else comes up with another idea. He does not have the ramdisk or initrd in his manual ones. That would do it right there. Be sure to generate the ramdisk as well. The documentation doesn't say to use ramdisk or initrd for a manual kernel, only the genkernel. But if the configs are the same, you need to do the same things, so generate your ramdisk and see what happens. I do this all the time, just use genkernel to generate the ramdisk and do all other things manually. I just make oldconfig when I upgrade and do make Bzimage and make modules and make modules_install and copy the kernel to the right place and update my lilo.conf. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] kernel panic on manually built kernel
On Thursday 04 November 2010 11:49:07 pm dhk wrote: stupid queston but did you select the appropriate sata drivers ? i ran into a similar problem just about an hr back becuase i forgot to include those . -- - Yohan Pereira.
Re: [gentoo-user] kernel panic on manually built kernel
Apparently, though unproven, at 19:00 on Thursday 04 November 2010, dhk did opine thusly: On 11/04/2010 12:52 PM, Alan McKinnon wrote: Apparently, though unproven, at 18:34 on Thursday 04 November 2010, dhk did opine thusly: I've always used the genkernel, but now am trying to make a manual one. I think the kernel is alright since all the default setting seemed reasonable and the build was easy enough. However, when I boot to it I get a kernel panic and it complains about the root device /dev/hda3. So I think the problem has to do with my parameters or syntax in grub.conf. Below are three grub menu options. The first two have the problem and the third is the genkernel that works fine. Is there something wrong with the way the first two are? Thanks. Why did you think it a good idea to NOT post the *actual* error? Your grub entries are correct. I'll bet money that you built one or more of your chipset drivers, libata, or root filesystem driver as a module. These must not be modules, they must be built-in (otherwise you need an initrd) # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 # This is a Manually built kernel with default settings. kernel panic title Gentoo Linux x86 2.6.34-r12 root (hd0,0) kernel /boot/kernel-2.6.34-gentoo-r12 root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev # From Documentation: video=uvesafb:mtrr:3,ywrap,1024x768...@85 # This a genkernel and works title Gentoo Linux x86 2.6.34-r6 root (hd0,0) kernel /boot/kernel-genkernel-x86_64-2.6.34-gentoo-r6 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 vga=791 splash=verbose video=vesafb:mtrr,ywrap udev initrd /boot/initramfs-genkernel-x86_64-2.6.34-gentoo-r6 --dhk Thanks all, I check those suggestions and get back to you. The reason I didn't include the exact error is that I can't capture it. I'd have to write it on paper and then reboot to the working kernel. By then it doesn't seem to be in any of the logs. I'll see what I can do about that. The usual error is something like panic: can't find root filesystem (dev/hda3) or similar. It's so common when building your own kernel the first time, that if you post the gist of the error (doesn't have to be 100% exact), you'll get 10 replies in an error from folk who've all made the same mistake themselves. Some of us more than once... It's always missing drivers or (more usually) drivers built as modules. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kernel panic on manually built kernel
Apparently, though unproven, at 19:36 on Thursday 04 November 2010, dhk did opine thusly: On 11/04/2010 01:08 PM, Neil Bothwick wrote: On Thu, 04 Nov 2010 13:00:21 -0400, dhk wrote: The reason I didn't include the exact error is that I can't capture it. I'd have to write it on paper and then reboot to the working kernel. Which is a lot less work than trying to fix the problem by guesswork. I have /boot as ext2 and the rest ext3 with lvm2. $ df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda3 8262068712028 7130344 10% / udev 10240 336 9904 4% /dev /dev/mapper/vg-usr15481840 12867912 1827496 88% /usr /dev/mapper/vg-home 51606140 42781428 6203272 88% /home /dev/mapper/vg-opt 5160576 2635064 2263368 54% /opt /dev/mapper/vg-var15481840 2387500 12307908 17% /var /dev/mapper/vg-tmp 2064208 68708 1890644 4% /tmp shm 512572 0512572 0% /dev/shm The ext2 wasn't compiled in, so I compiled it in and rebooted. I got the same error. kernel panic - not syncing : VFS: unable to mount root FS on unknown-block (2,0) This is what I had. Second extended fs support │ │ │ │* Ext3 journalling file system support │ │ │ │[ ] Default to 'data=ordered' in ext3 │ │ │ │[*] Ext3 extended attributes │ │ │ │[*] Ext3 POSIX Access Control Lists │ │ │ │[*] Ext3 Security Labels This is what I added. * Second extended fs support │ │ │ │[ ] Ext2 extended attributes (NEW) │ │ │ │[ ] Ext2 execute in place support (NEW) │ │ │ │* Ext3 journalling file system support │ │ │ │[ ] Default to 'data=ordered' in ext3 │ │ │ │[*] Ext3 extended attributes │ │ │ │[*] Ext3 POSIX Access Control Lists │ │ │ │[*] Ext3 Security Labels │ │ Thanks, --dhk Is your / partition in or out of the lvm? -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kernel panic on manually built kernel
On Thu, 04 Nov 2010 13:36:25 -0400, dhk wrote: The ext2 wasn't compiled in, so I compiled it in and rebooted. I got the same error. kernel panic - not syncing : VFS: unable to mount root FS on unknown-block (2,0) It's saying unknown block, not unknown fs. I suspect you haven't compiled in the drivers for your hard disk controller. -- Neil Bothwick Philosophical error: Demonstrate the existence of a key to continue signature.asc Description: PGP signature
Re: [gentoo-user] kernel panic on manually built kernel
On 4/11/2010, at 5:36pm, dhk wrote: ... This is what I had. Second extended fs support │ │ │ │* Ext3 journalling file system support │ │ │ │[ ] Default to 'data=ordered' in ext3 │ │ │ │[*] Ext3 extended attributes │ │ │ │[*] Ext3 POSIX Access Control Lists │ │ │ │[*] Ext3 Security Labels This is what I added. * Second extended fs support │ │ │ │[ ] Ext2 extended attributes (NEW) │ │ │ │[ ] Ext2 execute in place support (NEW) │ │ │ │* Ext3 journalling file system support │ │ │ │[ ] Default to 'data=ordered' in ext3 │ │ │ │[*] Ext3 extended attributes │ │ │ │[*] Ext3 POSIX Access Control Lists │ │ │ │[*] Ext3 Security Labels │ │ The kernel configuration is not terribly readable when posted in this format. Might I suggest posting the whole .config file as an attachment, perhaps gzipped? You can transfer it from the non-booting machine to the PC on which you have internet access by using scp from the LiveCD. Stroller.
[gentoo-user] kernel panic -- finding proper config diff
Hi group, Did linux#make menuconfig followed by linux# make make modules_install on the .2.6.30-gentoo-r7 sources. And copied over the new kernel and rebooted. The kernel panicked. The relevant messages are: ... VFS: Mounted root (ext2 filesystem) readonly on device 8:1, Freeing unused kernel memory: 276k freed Warning: unable to open an initial console Kernel panic - not syncing. No init found. Try passing init=option to kernel. Pid: 1. comm: swapper Not tainted 2.6.30-gentoo-r7 #2 Call Trace: [c0479986] ? printk+0xf/0x11 [c04798dc] panic+0x39/0xd4 [c020135z] init_post+0x13c/0x13e [c05b62dc] kernel_init+0x148/0x152 [c05b6194] ? kernel_init+0x0/0x152 [c02033cf] kernel_thread_helper+0x7/0x10 So far I've tried adding 'init=/bin/bash' and 'init=/sbin/init' to the command line. No help. Someone in a forum suggested chrooting and emerging sysvinit. But that's already installed. There's a million hits on google for this error message with about as many solutions. Assuming it has something to do with my kernel config, I tried running $diff -y on the two configs but at approx. 2600 lines per file I'm going to need some advice on what to zero in on. I tried to keep the new config as same as the old. But there's a lot of new features, weird stuff like CONFIG_X86_32_LAZY_GS=y and the new decompression protocol. Maxim
[gentoo-user] Kernel Panic Troubleshooting when machine is not avaiable directly
Hi,
I've been having kernel panics on a not-so-regular basis (server was
running fine for 30 days, then had a panic, again fine for 2 months or
so then panic'ed again). Problem is, the machine is far away and I
don't have access to the screen. So far I've changed syslog-ng to
record emergencies not to /dev/tty8 and console(root) but to files
snip
destination emergency { file(/var/log/emergencylog); };
destination else_all { file(/var/log/evrelse); };
(...)
filter f_emergency { level(emerg); };
(...)
log { source(src); filter(f_emergency); destination(emergency); };
log { source(src); destination(else_all); };
#line above ends all the log statements so it's basically a catch-all
/snip
Is this enough to record the msg dumps when it would panic again?
Also, I have no idea as to what's causing it, since it's so irregular.
I'm running Linux undine 2.6.23-hardened-r7-undine
(Just had to recompile kernel and tried to fix around stuffs + remove
the things I didn't need hoping it'd be the panic cause)
grsec is enabled and logs most things, with most security enabled
(minus the parts for TCP connections)
PaX is also enabled
-
Hieu Luu Danh
-
Freelance Web Designer
E: [EMAIL PROTECTED]
N: United Kingdom, SW15 East London
--
gentoo-user@lists.gentoo.org mailing list
RE: [gentoo-user] kernel panic from hell!
Hi group, I've been working and reading and tweaking and editing all day and gentoo will not boot. Typical kernel panic: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub kernel /vmlinuz root=/dev/hda3 ro [Linux-bzImage, setup=0x1200, size=0x13d208] grubboot ,,,VFS: Cannot open root device hda3 or unknown-block(0,0) Please append a correct root= boot option Kernel panic-not syncing...unknown-block(0,0) Panics for hda1 and hda3. Whether I use the device names or grub (hd0,x) terminology. Whether or not I declare a root dev after /vmlinuz Yes, ext2fs support was compiled *into* the kernel. There are 4 primary partitions: hda1(boot-ext2), 2(swap), 3(root-ext2) and 4(home-ext2). Very simple. No dual boot. No extended partitions. e2fsck checks out for hda1 and hda3. No errors are noted for the drive in dmesg or fdisk. Is there something I haven't tried? Maxim Check to make sure you have all the disk drivers compiled in -- for your controller etc -- some ide / ata drives require odd ones here and there -- I have tons of these errors :) Tim Holmes IT Manager / Webmaster / Teacher Medina Christian Academy A Higher Standard... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel panic from hell!-FIXED
Did a bit of googling for ya. You did compile in support for your IDE Bingo! Thanks everybody! Maxim TV dinner still cooling? Check out Tonight's Picks on Yahoo! TV. http://tv.yahoo.com/ -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel panic from hell!-FIXED
maxim wexler wrote: Did a bit of googling for ya. You did compile in support for your IDE Bingo! Thanks everybody! Maxim TV dinner still cooling? Check out Tonight's Picks on Yahoo! TV. http://tv.yahoo.com/ I guess sometimes I am worth something. :-p I must confess though, that error looked familiar. I googled to make sure it was what I thought it was. I did that the other day on my second box. I just used the wrong driver then though. I think the generic IDE should be enabled by default myself. It may not have DMA but at least it will boot up. Glad you got it working. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967
Re: [gentoo-user] kernel panic from hell!-FIXED
that error looked familiar. I googled to make sure I googled lots but didn't find that particular nugget. Unless my eyes were glazing over. What search terms did you use? Maxim Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel panic from hell!-FIXED
maxim wexler wrote: that error looked familiar. I googled to make sure I googled lots but didn't find that particular nugget. Unless my eyes were glazing over. What search terms did you use? Maxim Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com I used Please append a correct root= boot option and it was in there somewhere. I think it was the second one. After that, I remembered running into it myself. I like that quote thing. It helps a lot sometimes. Dale :-) :-) :-) -- www.myspace.com/dalek1967
[gentoo-user] kernel panic from hell!
Hi group, I've been working and reading and tweaking and editing all day and gentoo will not boot. Typical kernel panic: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub kernel /vmlinuz root=/dev/hda3 ro [Linux-bzImage, setup=0x1200, size=0x13d208] grubboot ,,,VFS: Cannot open root device hda3 or unknown-block(0,0) Please append a correct root= boot option Kernel panic-not syncing...unknown-block(0,0) Panics for hda1 and hda3. Whether I use the device names or grub (hd0,x) terminology. Whether or not I declare a root dev after /vmlinuz Yes, ext2fs support was compiled *into* the kernel. There are 4 primary partitions: hda1(boot-ext2), 2(swap), 3(root-ext2) and 4(home-ext2). Very simple. No dual boot. No extended partitions. e2fsck checks out for hda1 and hda3. No errors are noted for the drive in dmesg or fdisk. Is there something I haven't tried? Maxim Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel panic from hell!
maxim wexler wrote: Hi group, I've been working and reading and tweaking and editing all day and gentoo will not boot. Typical kernel panic: grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub kernel /vmlinuz root=/dev/hda3 ro [Linux-bzImage, setup=0x1200, size=0x13d208] grubboot ,,,VFS: Cannot open root device hda3 or unknown-block(0,0) Please append a correct root= boot option Kernel panic-not syncing...unknown-block(0,0) Panics for hda1 and hda3. Whether I use the device names or grub (hd0,x) terminology. Whether or not I declare a root dev after /vmlinuz Yes, ext2fs support was compiled *into* the kernel. There are 4 primary partitions: hda1(boot-ext2), 2(swap), 3(root-ext2) and 4(home-ext2). Very simple. No dual boot. No extended partitions. e2fsck checks out for hda1 and hda3. No errors are noted for the drive in dmesg or fdisk. Is there something I haven't tried? Maxim Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. http://answers.yahoo.com/dir/?link=listsid=396545367 Did a bit of googling for ya. You did compile in support for your IDE controller right? If not, it can't see your drives. Just a thought. Hope that helps. Dale :-) :-) :-) -- www.myspace.com/dalek1967 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel panic from hell!
On Mon, 29 Jan 2007 20:07:22 -0800 (PST) maxim wexler [EMAIL PROTECTED] wrote: Hi group, I've been working and reading and tweaking and editing all day and gentoo will not boot. Typical kernel panic: ... Very simple. No dual boot. No extended partitions. e2fsck checks out for hda1 and hda3. No errors are noted for the drive in dmesg or fdisk. Is there something I haven't tried? Maxim Have you tried ensuring that you have the driver for IDE support in your kernel? You should see something about an ide device or two up above the kernel panic... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] kernel panic from hell!
On Monday 29 January 2007 23:07, maxim wexler wrote: Is there something I haven't tried? Have you enabled support for your disk controller? -- Randy Barlow http://www.electronsweatshop.com Oh me of little faith... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
Rafael, Did you compile in support for your IDE controller? Well, I think so... is not a SCSI drive or similar. It is just an IDE hard drive, no special support is required. Anyway it doesn't matter I've re-formatted with: /dev/hda1 ext3 (here will go /) /dev/hda1 swap As I have my others computers. Thank you, Rafael Fernández López. -- A la vista de suficientes ojos todos los errores resultan evidentes - Linus Torvalds -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
Rafael Fernández López wrote: Hi, I've googled and I haven't got any successfull results. I've my hard disk as follows: /dev/hda1 - ext2 (here will go /boot) /dev/hda2 - swap /dev/hda3 - ext3 (here will go /) I've compiled gentoo-sources with NO genkernel, but manually. I've no filesystem as modules, everything is included in kernel (as asterisk (*)). I am getting the next error when booting: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0) And my bootloader is grub, here is grub.conf: default 0 hiddenmenu timeout 5 title=Gentoo GNU/Linux root (hd0,0) kernel /vmlinuz-2.6.17-gentoo-r5 root=/dev/hda3 I can't figure out what's going wrong... because I think that I don't need initram because I've nothing compiled as a module. Thank you very much, Rafael Fernández López. What ever file system you use for /boot and for / must be included IN the kernel, not as modules. It has to be able to read it for it to load the modules. That should help. Dale :-) :-) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
Andrew Frink wrote: On 8/18/06, *Dale* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Rafael Fernández López wrote: Hi, I've googled and I haven't got any successfull results. I've my hard disk as follows: /dev/hda1 - ext2 (here will go /boot) /dev/hda2 - swap /dev/hda3 - ext3 (here will go /) I've compiled gentoo-sources with NO genkernel, but manually. I've no filesystem as modules, everything is included in kernel (as asterisk (*)). I am getting the next error when booting: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0) And my bootloader is grub, here is grub.conf: default 0 hiddenmenu timeout 5 title=Gentoo GNU/Linux root (hd0,0) kernel /vmlinuz-2.6.17-gentoo-r5 root=/dev/hda3 I can't figure out what's going wrong... because I think that I don't need initram because I've nothing compiled as a module. Thank you very much, Rafael Fernández López. What ever file system you use for /boot and for / must be included IN the kernel, not as modules. It has to be able to read it for it to load the modules. That should help. Dale :-) :-) -- gentoo-user@gentoo.org mailto:gentoo-user@gentoo.org mailing list Dale The error seems to be that it doesn't know how to find the drive not that it doesn't know what FS it is, aslo the OP said that he had no FS's compiled as modules Andrew I guess I misread it then. It is common for someone to not put the file system root uses in the kernel though. Me, I don't use modules at all. The only module I have is nvidia. Dale :-) :-) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Kernel Panic
Hello everybody out there! Here I am again, ready to fight!! First of all, I'll start doing things in the right way, I'm burning the 2005.1-r1 live cd to perform a proper installation process from it. I think Ubuntu is making my system a little crazy (I've noticed some strange things wich won't explain here). If after all the problem continues you'll be the first to know about it!
[gentoo-user] Kernel Panic
Hi, Well, I've already posted this problem at Gentoo forums, but as I get no answers I decided to ask for your help too. I'm quite desperated! Here's the issue: http://forums.gentoo.org/viewtopic-t-435070.html Help me please!!
Re: [gentoo-user] Kernel Panic
On Saturday 18 February 2006 08:58, Izar Ilun [EMAIL PROTECTED] wrote about '[gentoo-user] Kernel Panic': Hi, Well, I've already posted this problem at Gentoo forums, but as I get no answers I decided to ask for your help too. I'm quite desperated! Here's the issue: http://forums.gentoo.org/viewtopic-t-435070.html Thanks for burying us in useless information. Very little of what you posted has any relation to your problem. For example, make.conf doesn't have anything to do with what the kernel does before starting init. If you don't know what to provide, not provide anything 'cept an offer for more information -- wading through useless information is not enjoyable when you are trying to fix someone else's problem. Tip: No one wants to see an entire kernel .config file. I'm betting (but don't hold me to this) that your root filesystem doesn't have the device node corresponding to your root= option. While devfs might work during early boot, I don't see it in your kernel (and anyway, udev is the way to go). Udev is all in userland so it won't get invoked (to create device nodes) until after init is found. You covered the big problems -- your root filesystem is compiled into the kernel, as is support for IDE drives and your chipset, in particular. You also don't appear to be running and initrd / initramfs. After booting into ubuntu and mounting your gentoo root filesystem, could you please ls /mnt/gentoo/dev/[hms]* -ld and provide the output? Also, you aren't trying to put bin, sbin, or lib on a separate filesystem are you? It could also be conceivably possible that even though both grub and ubuntu show that disk as (hd0)/hda [the first IDE drive], gentoo is detecting is as /dev/hdb, so you might try changing your root= option. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Kernel Panic
On Saturday 18 February 2006 08:58, Izar Ilun wrote: Here's the issue: http://forums.gentoo.org/viewtopic-t-435070.html From your post: title Ubuntu, kernel 2.6.12-9-386 root(hd1,1) kernel /boot/vmlinuz-2.6.12-9-386 root=/dev/hdb2 ro quiet splash initrd /boot/initrd.img-2.6.12-9-386 savedefault boot Try removing the initrd first. Just comment that line out and remove quiet and splash from the entry. This will test and make sure that /dev/hdb2 has a working installation. Once you can boot into the system proper then you can look for how to get the initrd image working. -- Zac Slade -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Kernel Panic
Ibai and me are the same, so I apologize again for amuising you! :-)On 2/18/06, Ibai [EMAIL PROTECTED] wrote: Fisrt of all, thanx for answering, I apologize for the excesive amount of info I brought! Well, I'll try to answer your posts in order Just a guess. Do you have /dev/console device existing? No, I don't. At less now that I'm chrooting Gentoo via Ubuntu... ls /mnt/gentoo/dev/[hms]* -ld ubuntu / # ls /dev/[hms]* -ld brw-rw 1 root disk 3, 0 oct 19 16:12 /dev/hda brw-rw 1 root disk 3, 1 oct 19 16:12 /dev/hda1 brw-rw 1 root disk 3, 10 oct 19 16:12 /dev/hda10 brw-rw 1 root disk 3, 11 oct 19 16:12 /dev/hda11 brw-rw 1 root disk 3, 12 oct 19 16:12 /dev/hda12 brw-rw 1 root disk 3, 13 oct 19 16:12 /dev/hda13 brw-rw 1 root disk 3, 14 oct 19 16:12 /dev/hda14 brw-rw 1 root disk 3, 15 oct 19 16:12 /dev/hda15 brw-rw 1 root disk 3, 16 oct 19 16:12 /dev/hda16 brw-rw 1 root disk 3, 17 oct 19 16:12 /dev/hda17 brw-rw 1 root disk 3, 18 oct 19 16:12 /dev/hda18 brw-rw 1 root disk 3, 19 oct 19 16:12 /dev/hda19 brw-rw 1 root disk 3, 2 oct 19 16:12 /dev/hda2 brw-rw 1 root disk 3, 20 oct 19 16:12 /dev/hda20 brw-rw 1 root disk 3, 3 oct 19 16:12 /dev/hda3 brw-rw 1 root disk 3, 4 oct 19 16:12 /dev/hda4 brw-rw 1 root disk 3, 5 oct 19 16:12 /dev/hda5 brw-rw 1 root disk 3, 6 oct 19 16:12 /dev/hda6 brw-rw 1 root disk 3, 7 oct 19 16:12 /dev/hda7 brw-rw 1 root disk 3, 8 oct 19 16:12 /dev/hda8 brw-rw 1 root disk 3, 9 oct 19 16:12 /dev/hda9 brw-rw 1 root disk 3, 64 oct 19 16:12 /dev/hdb brw-rw 1 root disk 3, 65 oct 19 16:12 /dev/hdb1 brw-rw 1 root disk 3, 74 oct 19 16:12 /dev/hdb10 brw-rw 1 root disk 3, 75 oct 19 16:12 /dev/hdb11 brw-rw 1 root disk 3, 76 oct 19 16:12 /dev/hdb12 brw-rw 1 root disk 3, 77 oct 19 16:12 /dev/hdb13 brw-rw 1 root disk 3, 78 oct 19 16:12 /dev/hdb14 brw-rw 1 root disk 3, 79 oct 19 16:12 /dev/hdb15 brw-rw 1 root disk 3, 80 oct 19 16:12 /dev/hdb16 brw-rw 1 root disk 3, 81 oct 19 16:12 /dev/hdb17 brw-rw 1 root disk 3, 82 oct 19 16:12 /dev/hdb18 brw-rw 1 root disk 3, 83 oct 19 16:12 /dev/hdb19 brw-rw 1 root disk 3, 66 oct 19 16:12 /dev/hdb2 brw-rw 1 root disk 3, 84 oct 19 16:12 /dev/hdb20 brw-rw 1 root disk 3, 67 oct 19 16:12 /dev/hdb3 brw-rw 1 root disk 3, 68 oct 19 16:12 /dev/hdb4 brw-rw 1 root disk 3, 69 oct 19 16:12 /dev/hdb5 brw-rw 1 root disk 3, 70 oct 19 16:12 /dev/hdb6 brw-rw 1 root disk 3, 71 oct 19 16:12 /dev/hdb7 brw-rw 1 root disk 3, 72 oct 19 16:12 /dev/hdb8 brw-rw 1 root disk 3, 73 oct 19 16:12 /dev/hdb9 brw-rw 1 root disk 22, 0 oct 19 16:12 /dev/hdc brw-rw 1 root disk 22, 1 oct 19 16:12 /dev/hdc1 brw-rw 1 root disk 22, 10 oct 19 16:12 /dev/hdc10 brw-rw 1 root disk 22, 11 oct 19 16:12 /dev/hdc11 brw-rw 1 root disk 22, 12 oct 19 16:12 /dev/hdc12 brw-rw 1 root disk 22, 13 oct 19 16:12 /dev/hdc13 brw-rw 1 root disk 22, 14 oct 19 16:12 /dev/hdc14 brw-rw 1 root disk 22, 15 oct 19 16:12 /dev/hdc15 brw-rw 1 root disk 22, 16 oct 19 16:12 /dev/hdc16 brw-rw 1 root disk 22, 17 oct 19 16:12 /dev/hdc17 brw-rw 1 root disk 22, 18 oct 19 16:12 /dev/hdc18 brw-rw 1 root disk 22, 19 oct 19 16:12 /dev/hdc19 brw-rw 1 root disk 22, 2 oct 19 16:12 /dev/hdc2 brw-rw 1 root disk 22, 20 oct 19 16:12 /dev/hdc20 brw-rw 1 root disk 22, 3 oct 19 16:12 /dev/hdc3 brw-rw 1 root disk 22, 4 oct 19 16:12 /dev/hdc4 brw-rw 1 root disk 22, 5 oct 19 16:12 /dev/hdc5 brw-rw 1 root disk 22, 6 oct 19 16:12 /dev/hdc6 brw-rw 1 root disk 22, 7 oct 19 16:12 /dev/hdc7 brw-rw 1 root disk 22, 8 oct 19 16:12 /dev/hdc8 brw-rw 1 root disk 22, 9 oct 19 16:12 /dev/hdc9 brw-rw 1 root disk 22, 64 oct 19 16:12 /dev/hdd brw-rw 1 root disk 22, 65 oct 19 16:12 /dev/hdd1 brw-rw 1 root disk 22, 74 oct 19 16:12 /dev/hdd10 brw-rw 1 root disk 22, 75 oct 19 16:12 /dev/hdd11 brw-rw 1 root disk 22, 76 oct 19 16:12 /dev/hdd12 brw-rw 1 root disk 22, 77 oct 19 16:12 /dev/hdd13 brw-rw 1 root disk 22, 78 oct 19 16:12 /dev/hdd14 brw-rw 1 root disk 22, 79 oct 19 16:12 /dev/hdd15 brw-rw 1 root disk 22, 80 oct 19 16:12 /dev/hdd16 brw-rw 1 root disk 22, 81 oct 19 16:12 /dev/hdd17 brw-rw 1 root disk 22, 82 oct 19 16:12 /dev/hdd18 brw-rw 1 root disk 22, 83 oct 19 16:12 /dev/hdd19 brw-rw 1 root disk 22, 66 oct 19 16:12 /dev/hdd2 brw-rw 1 root disk 22, 84 oct 19 16:12 /dev/hdd20 brw-rw 1 root disk 22, 67 oct 19 16:12 /dev/hdd3 brw-rw 1 root disk 22, 68 oct 19 16:12 /dev/hdd4 brw-rw 1 root disk 22, 69 oct 19 16:12 /dev/hdd5 brw-rw 1 root disk 22, 70 oct 19 16:12 /dev/hdd6 brw-rw 1 root disk 22, 71 oct 19 16:12 /dev/hdd7 brw-rw 1 root disk 22, 72 oct 19 16:12 /dev/hdd8 brw-rw 1 root disk 22, 73 oct 19 16:12 /dev/hdd9 brw-rw 1 root disk 33, 0 oct 19 16:13 /dev/hde brw-rw 1 root disk 33, 1 oct 19 16:13 /dev/hde1 brw-rw 1 root disk 33, 10
Re: [gentoo-user] Kernel Panic
On 2006-02-18 18:52:49 +0100 (Sat, Feb), Izar Ilun wrote: Do you have /dev/console device existing? No, I don't. At less now that I'm chrooting Gentoo via Ubuntu... So check once more (ls -l /dev/console), try to create it, and see what happens: mknod -m 0600 /dev/console c 5 1 ...assuming that you are in chrooted environment, and /dev/ is your Gentoo's directory - not Ubuntu's one. Console device should look like this: crw--- 1 root tty 5, 1 lut 18 17:30 /dev/console I suppose that you may be missing /dev/null device too. mknod -m 660 /dev/null c 1 3 And you may want to read Gentoo udev guide, too: http://www.gentoo.org/doc/en/udev-guide.xml -- No virus found in this outgoing message. Checked by grep -i virus $MESSAGE Trust me. pgpC6EiUjPxpY.pgp Description: PGP signature
Re: [gentoo-user] Kernel Panic
On Saturday 18 February 2006 11:52, Izar Ilun [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] Kernel Panic': Just a guess. Do you have /dev/console device existing? No, I don't. At less now that I'm chrooting Gentoo via Ubuntu... ls /mnt/gentoo/dev/[hms]* -ld ubuntu / # ls /dev/[hms]* -ld Are you inside the chroot here? If not, this listing is meaningless. Did you bind mount (or otherwise) mount something to /dev in the chroot before going in? If so, this listing is, again, meaningless. (We need do know the device nodes on the filesystem on partition hda3, not the device nodes created by devfs or udev or the device nodes on your ubuntu root partition.) Otherwise, you seem to have the right nodes for your drive -- can you tell if the kernel successfully detects your drive? Do you get any messages about a new block device: hda? If not, or if you just can't tell, you might try building mroe of the IDE controller drivers into [*] or * the kernel (not as modules M). Also, if you append init=/bin/bash to your kernel command-line, can you get a prompt? -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Kernel Panic
I'll tell you later on, now I'm tired alkoholic! ;-)On 2/18/06, Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:On Saturday 18 February 2006 11:52, Izar Ilun [EMAIL PROTECTED] wroteabout 'Re: [gentoo-user] Kernel Panic': Just a guess. Do you have /dev/console device existing? No, I don't. At less now that I'm chrooting Gentoo via Ubuntu... ls /mnt/gentoo/dev/[hms]* -ld ubuntu / # ls /dev/[hms]* -ldAre you inside the chroot here? If not, this listing is meaningless.Did you bind mount (or otherwise) mount something to /dev in the chroot before going in?If so, this listing is, again, meaningless.(We need do know the device nodes on the filesystem on partition hda3, notthe device nodes created by devfs or udev or the device nodes on your ubuntu root partition.)Otherwise, you seem to have the right nodes for your drive -- can you tellif the kernel successfully detects your drive?Do you get any messagesabout a new block device: hda?If not, or if you just can't tell, you might try building mroe of the IDE controller drivers into [*] or * thekernel (not as modules M).Also, if you append init=/bin/bash to your kernel command-line, can you geta prompt? --Boyd Stephen Smith Jr.[EMAIL PROTECTED]ICQ: 514984 YM/AIM: DaTwinkDaddy--gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(2,0)
--- Felipe Ribeiro [EMAIL PROTECTED] wrote: The /boot is on my root file Whatev. The kernel has to be able to read it without having to wait for a module. On 12/11/05, maxim wexler [EMAIL PROTECTED] wrote: --- Felipe Ribeiro [EMAIL PROTECTED] wrote: Hi all, I've just installed Gentoo 2005.1-r1 on my amd64 box and i've got this problem while rebooting: Root-NFS: No NFS server available giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Insert root floppy and press ENTER end-request: I/O error, dev fd0, sector 0 VFS: Cannot open root device hda2 or unknown-block(2,0) Please append a correct root= boot option. Kerenel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) What should i do? is it a grub configuration problem? or kernel compilation? kernel -- make sure / fs support is _not_ modular, for starters __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list -- gentoo-user@gentoo.org mailing list __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
