Hello, I am running Kubuntu 7.04 on a mac mini (specs attached via
info.html). For learning purposes I am trying to custom build a
2.6.22.3 kernel from source and boot from it. My plan was to use the
distributions .config file (and I specified the settings for options
that were added since the last kernel included with Kubuntu which is
(and is what I have now reverted to) Linux hexstar-desktop
2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux).
I have attached the .config file used in the building of the 2.6.22.3
kernel. Below is the error:
Starting up...
Uncompressing Linux... Ok, booting the kernel.
[ 32.227452] i8042.c: No controller found
[ 32.228426] Kernel panic - not syncing: VFS: Unable to mount root fs
on unknown-block(0,0)
That is the correct block however and it is of ext3 format. I have
made sure that the ext3 module is built into the kernel and have tried
it as a module and both times I get the same error. I am not sure why
it can't find the controller? Does my controller not have support in
the latest kernel?
Please CC me replies to this post, thanks! :)
On Tuesday 21 August 2007 22:19:13 you wrote:
> Hello, I am running Kubuntu 7.04 on a mac mini (specs attached via
> info.html). For learning purposes I am trying to custom build a
> 2.6.22.3 kernel from source and boot from it. My plan was to use the
> distributions .config file (and I specified the settings for options
> that were added since the last kernel included with Kubuntu which is
> (and is what I have now reverted to) Linux hexstar-desktop
> 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux).
> I have attached the .config file used in the building of the 2.6.22.3
> kernel. Below is the error:
>
> Starting up...
> Uncompressing Linux... Ok, booting the kernel.
> [ 32.227452] i8042.c: No controller found
> [ 32.228426] Kernel panic - not syncing: VFS: Unable to mount root fs
> on unknown-block(0,0)
>
> That is the correct block however and it is of ext3 format. I have
> made sure that the ext3 module is built into the kernel and have tried
> it as a module and both times I get the same error. I am not sure why
> it can't find the controller? Does my controller not have support in
> the latest kernel?
>
> Please CC me replies to this post, thanks! :)
Make sure your IDE/SATA driver is compiled in unless you are using an
initramfs image.
Regards,
ismail
--
Perfect is the enemy of good
On 8/21/07, Hex Star <[email protected]> wrote:
> Ah so the IDE/SATA driver should not be a module (if it is a module
> it'll cause this issue)?
>
One more thing, are there any other critical kernel components that
won't work as a module and thus prevent boot?
Thanks! :)
On 8/21/07, Ismail D?nmez <[email protected]> wrote:
>
> Make sure your IDE/SATA driver is compiled in unless you are using an
> initramfs image.
>
> Regards,
> ismail
>
> --
> Perfect is the enemy of good
>
Ah so the IDE/SATA driver should not be a module (if it is a module
it'll cause this issue)?
On Aug 21 2007 12:29, Hex Star wrote:
>
>Btw, I am not using a initramfs image..
success = (using_initramfs && ide == 'M') || ide == 'Y';
HTH.
Jan
--
On 8/21/07, Jan Engelhardt <[email protected]> wrote:
>
> success = (using_initramfs && ide == 'M') || ide == 'Y';
Thanks for the replies guys, I am building the ata_piix and
ata_generic drivers into the kernel now...hope this works :)
On Aug 21 2007 12:42, Hex Star wrote:
>On 8/21/07, Jan Engelhardt <[email protected]> wrote:
>>
>> success = (using_initramfs && ide == 'M') || ide == 'Y';
>
>Thanks for the replies guys, I am building the ata_piix and
>ata_generic drivers into the kernel now...hope this works :)
You do not need ata_generic if ata_piix can do it.
Jan
--
On Tuesday 21 August 2007 22:27:25 you wrote:
> On 8/21/07, Hex Star <[email protected]> wrote:
> > Ah so the IDE/SATA driver should not be a module (if it is a module
> > it'll cause this issue)?
>
> One more thing, are there any other critical kernel components that
> won't work as a module and thus prevent boot?
Well also the filesystem module for the root fs ( / ) should not be a module
as you won't be able mount root at startup hence causing a panic.
Regards,
ismail
--
Perfect is the enemy of good
On Aug 21 2007 22:56, Ismail Dönmez wrote:
>On Tuesday 21 August 2007 22:27:25 you wrote:
>> On 8/21/07, Hex Star <[email protected]> wrote:
>> > Ah so the IDE/SATA driver should not be a module (if it is a module
>> > it'll cause this issue)?
>>
>> One more thing, are there any other critical kernel components that
>> won't work as a module and thus prevent boot?
>
>Well also the filesystem module for the root fs ( / ) should not be a module
>as you won't be able mount root at startup hence causing a panic.
- which is why people use initramfs. It's all perfect.
>Perfect is the enemy of good
Jan
--
On 8/21/07, Ismail D?nmez <[email protected]> wrote:
> Well also the filesystem module for the root fs ( / ) should not be a module
> as you won't be able mount root at startup hence causing a panic.
Thanks, I have made sure that it is built in along with ata_piix
...however now I get this error:
[ 24.891879] ata_piix 0000:00:1f.2:invalid map value 0
But why do I get this error, if I run this script (which shows the
modules my system currently relies on):
#!/bin/bash
#
# find_all_modules.sh
#
for i in `find /sys/ -name modalias -exec cat {} \;`; do
/sbin/modprobe --config /dev/null --show-depends $i ;
done | rev | cut -f 1 -d '/' | rev | sort -u
It outputs:
FATAL: Module pci:v00008086d00002448sv00000000sd00000000bc06sc04i01 not found.
FATAL: Module pci:v00008086d000027A3sv00000000sd00000000bc11sc01i00 not found.
FATAL: Module eisa not found.
FATAL: Module serial8250 not found.
agpgart.ko
appleir.ko
ata_generic.ko
ata_piix.ko
ath_hal.ko
ath_pci.ko
bluetooth.ko
ehci-hcd.ko
evbug.ko
evdev.ko
generic.ko
hci_usb.ko
hid.ko
i2c-algo-bit.ko
i2c-core.ko
i2c-i801.ko
ieee1394.ko
intel-agp.ko
intelfb.ko
intel-rng.ko
iTCO_vendor_support.ko
iTCO_wdt.ko
libata.ko
ohci1394.ko
pci_hotplug.ko
pcspkr.ko
scsi_mod.ko
shpchp.ko
sky2.ko
snd-hda-codec.ko
snd-hda-intel.ko
snd.ko
snd-page-alloc.ko
snd-pcm.ko
snd-timer.ko
soundcore.ko
tsdev.ko
uhci-hcd.ko
usbcore.ko
usbhid.ko
usbkbd.ko
usbmouse.ko
vesafb.ko
wlan.ko
xpad.ko
which shows that ata_piix is the controller for the hd correct? Is
this a bug or is there some special parameter I have to configure to
make this work? Thanks! :)
On 8/21/07, Jan Engelhardt <[email protected]> wrote:
> - which is why people use initramfs. It's all perfect.
>
> >Perfect is the enemy of good
>
>
> Jan
> --
How would I go about setting up a initramfs for the kernel? The book
I'm referring to to help me learn kernel compilation and installation,
"Linux Kernel In A Nutshell" by Greg Kroah-Hartman doesn't mention how
to create a initramfs... Thanks! :)
I resolved the issue like so:
1) Download kernel source (K) from kernel.org
2) move the archive to a place where source is, /home/user/linux for
example (will have to do mkdir /home/user/linux first of course!) via
mv /home/user/Desktop/archive /dest/archive
3) Extract the archive: if .tar.bz2: tar -jxvf archive.tar.bz2 else
tar -zxvf archive.tar.gz
4) cd into resulting directory
5) do a sudo make defconfig, then sudo make xconfig (or if in terminal
menuconfig) and customize options for system, filesystem and
controller support must be built in!
6) do a sudo make
7) then sudo make modules_install
8) then sudo make install
9) then do a sudo update-initramfs -k kernelversion -c -v
10) then grub-update
11) reboot and enjoy!