23 May
2006
23 May
'06
7:25 p.m.
Firstly thanks to Asbjørn, Lee, Tim and others who have given me advice
so far.
I tried using Asbjørn's vanilla kernel but it didn't work as our laptops
are different, but your config settings were a good guide.
I downloaded the source package for 2.6.16
I did make oldconfig, to use the config already working on my machine
(just without the VXpocket support), I tried compiling the kernel as per
the instructions on the Demudi page
<http://demudi.agnula.org/wiki/Low-latencyKernelBuildingHowto>, and by
referencing Asbjørn's config settings
Lee had written that CONFIG_ISAPNP must be enabled, but this wasn't an
option that I could choose in menuconfig, there was just a hyphen beside
this option, also this wasn't enabled in Asbjørn's settings which
reportedly works.
but got this error message on reboot
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I assume this means I didn't have the exact settings configured for my laptop.
So then I put the result of lspci -v into http://kmuto.jp/debian/hcl/
0000:00:00.0 0600: 8086:3340 (rev 21)
0000:00:01.0 0604: 8086:3341 (rev 21)
0000:00:1d.0 0c03: 8086:24c2 (rev 03)
0000:00:1d.1 0c03: 8086:24c4 (rev 03)
0000:00:1d.2 0c03: 8086:24c7 (rev 03)
0000:00:1d.7 0c03: 8086:24cd (rev 03)
0000:00:1e.0 0604: 8086:2448 (rev 83)
0000:00:1f.0 0601: 8086:24cc (rev 03)
0000:00:1f.1 0101: 8086:24ca (rev 03)
0000:00:1f.5 0401: 8086:24c5 (rev 03)
0000:00:1f.6 0703: 8086:24c6 (rev 03)
0000:01:00.0 0300: 1002:4e50
0000:02:08.0 0200: 8086:1039 (rev 83)
0000:02:09.0 0280: 8086:4223 (rev 05)
0000:02:0a.0 0607: 1180:0475 (rev b8)
0000:02:0a.1 0c00: 1180:0551
and it requires the intel-agp driver, which reportedly works
80863340 Yes Intel Corporation 82855PM Processor to I/O Controller
intel-agp
in the Configuration Archive I couldn't find any kernel on any architecture where this
can be enabled.
Anyway then I tried to rebuild the package with initrd, as I got the impression from the
Demudi page that though building a fatter kernel,
at least my machine would reboot
unfortunately this couldn't be built because yaird, or intramfs-tools or
linux-intramafs-tool were not previously installed,
and I don't seem to be able to install them, either with apt-get or synaptic, as some
list is locked/unlocked
so a few questions - can I salvage things at this point or do I have to start over from a
fresh install?
what did I do wrong and how can avoid similar problems happening again?
am I going about this the right way, should i be using initrd?
I hadn't got around to installing the VXpocket firmware - though I don't think
this was the problem,
when booting into the new kernel Alsa couldn't find the soundcard, though I assume it
would be solved after the firmware was installed.
As much as I enjoy re-compiling and re-installing over and over again, I rather be making
some music - thanks in advance
peace
Hamish
Send instant messages to your online friends http://au.messenger.yahoo.com
24 May
24 May
9:45 a.m.
New subject: [linux-audio-user] Re-compiling Demudi kernel help please: Digigram VXpocket2
Your problem is that stock kernels usually use an initrd, but when you
compile by hand you aren't setting up the initrd. You can either grok
initrd, or compile a few more things into the kernel instead of as
modules. Needless to say the latter is by far easier.
You need the appropriate disk drivers (IDE/ATA, for example) and the
appropriate file system(s) compiled in (ext3 for example).
On Wed, 24 May 2006 at 11:25 +1200, Hamish Low wrote:
Firstly thanks to Asbjørn, Lee, Tim and others who
have given me advice
so far.
I tried using Asbjørn's vanilla kernel but it didn't work as our laptops
are different, but your config settings were a good guide.
I downloaded the source package for 2.6.16
I did make oldconfig, to use the config already working on my machine
(just without the VXpocket support), I tried compiling the kernel as per
the instructions on the Demudi page
<http://demudi.agnula.org/wiki/Low-latencyKernelBuildingHowto>, and by
referencing Asbjørn's config settings
Lee had written that CONFIG_ISAPNP must be enabled, but this wasn't an
option that I could choose in menuconfig, there was just a hyphen beside
this option, also this wasn't enabled in Asbjørn's settings which
reportedly works.
but got this error message on reboot
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
I assume this means I didn't have the exact settings configured for my
laptop.
So then I put the result of lspci -v into http://kmuto.jp/debian/hcl/
0000:00:00.0 0600: 8086:3340 (rev 21)
0000:00:01.0 0604: 8086:3341 (rev 21)
0000:00:1d.0 0c03: 8086:24c2 (rev 03)
0000:00:1d.1 0c03: 8086:24c4 (rev 03)
0000:00:1d.2 0c03: 8086:24c7 (rev 03)
0000:00:1d.7 0c03: 8086:24cd (rev 03)
0000:00:1e.0 0604: 8086:2448 (rev 83)
0000:00:1f.0 0601: 8086:24cc (rev 03)
0000:00:1f.1 0101: 8086:24ca (rev 03)
0000:00:1f.5 0401: 8086:24c5 (rev 03)
0000:00:1f.6 0703: 8086:24c6 (rev 03)
0000:01:00.0 0300: 1002:4e50
0000:02:08.0 0200: 8086:1039 (rev 83)
0000:02:09.0 0280: 8086:4223 (rev 05)
0000:02:0a.0 0607: 1180:0475 (rev b8)
0000:02:0a.1 0c00: 1180:0551
and it requires the intel-agp driver, which reportedly works
80863340 Yes Intel Corporation 82855PM Processor to I/O
Controller intel-agp
in the Configuration Archive I couldn't find any kernel on any architecture
where this can be enabled.
Anyway then I tried to rebuild the package with initrd, as I got the
impression from the Demudi page that though building a fatter kernel, at
least my machine would reboot
unfortunately this couldn't be built because yaird, or intramfs-tools or
linux-intramafs-tool were not previously installed, and I don't seem to be
able to install them, either with apt-get or synaptic, as some list is
locked/unlocked
so a few questions - can I salvage things at this point or do I have to
start over from a fresh install?
what did I do wrong and how can avoid similar problems happening again?
am I going about this the right way, should i be using initrd?
I hadn't got around to installing the VXpocket firmware - though I don't
think this was the problem, when booting into the new kernel Alsa couldn't
find the soundcard, though I assume it would be solved after the firmware
was installed.
As much as I enjoy re-compiling and re-installing over and over again, I
rather be making some music - thanks in advance
peace
Hamish
Send instant messages to your online friends http://au.messenger.yahoo.com
--
Hans Fugal ; http://hans.fugal.net
There's nothing remarkable about it. All one has to do is hit the
right keys at the right time and the instrument plays itself.
-- Johann Sebastian Bach
11:54 a.m.
New subject: [linux-audio-user] Re-compiling Demudi kernel help please: Digigram VXpocket2
On Wed, 24 May 2006 at 11:25 +1200, Hamish Low wrote:
> Firstly thanks to Asbjørn, Lee, Tim and others who have given me advice
> so far.
>
> I tried using Asbjørn's vanilla kernel but it didn't work as our laptops
> are different, but your config settings were a good guide.
>
> I downloaded the source package for 2.6.16
> I did make oldconfig, to use the config already working on my machine
> (just without the VXpocket support), I tried compiling the kernel as per
> the instructions on the Demudi page
> <http://demudi.agnula.org/wiki/Low-latencyKernelBuildingHowto>, and by
> referencing Asbjørn's config settings
> Lee had written that CONFIG_ISAPNP must be enabled, but this wasn't an
> option that I could choose in menuconfig, there was just a hyphen beside
> this option, also this wasn't enabled in Asbjørn's settings which
> reportedly works.
>
> but got this error message on reboot
>
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
>
> I assume this means I didn't have the exact settings configured for my
> laptop.
On Wed, May 24, 2006 at 07:44:59AM -0600, Hans Fugal wrote:
Your problem is that stock kernels usually use an
initrd, but when you
compile by hand you aren't setting up the initrd. You can either grok
initrd, or compile a few more things into the kernel instead of as
modules. Needless to say the latter is by far easier.
That is a judgement call.
For the former (under debian, not guaranteed, an example)
apt-get initrd-tools
mkinitrd -o /boot/initrd-img-2.6.16 2.6.16
Add an initrd line to GRUB or LILO
For the latter (ditto, guaranteed not to work)
You need the appropriate disk drivers (IDE/ATA, for
example) and the
appropriate file system(s) compiled in (ext3 for example).
Here is a start, all the items containing EXT2, EXT3, IDE
but not VIDEO.
Just change all the 'm' or 'not set' to 'y', append to
the end of .config, and compile. (Praying doesn't help,
but it might make you feel better. Pizza and beer are
also considered highly effective.)
$ grep EXT3 /src/linux-2.6.16/.config
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
$ grep EXT2 /src/linux-2.6.16/.config
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
$ grep IDE /src/linux-2.6.16/.config | grep -v VIDEO
# CONFIG_PARIDE is not set
CONFIG_IDE=m
CONFIG_BLK_DEV_IDE=m
# Please see Documentation/ide.txt for help/info on IDE drives
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=m
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
# IDE chipset support/bugfixes
CONFIG_IDE_GENERIC=m
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
CONFIG_JOYSTICK_SIDEWINDER=m
# CONFIG_FB_TRIDENT is not set
# CONFIG_SND_TRIDENT is not set
CONFIG_SOUND_TRIDENT=m
--
Joel Roth
30 May
30 May
2:56 a.m.
New subject: [linux-audio-user] Re-compiling Demudi kernel help please: Digigram VXpocket2
On Wednesday 24 May 2006 00:25, Hamish Low was like:
am I going about this the right way, should i be using
initrd?
You need to statically include the modules for your hardware (i.e. not build
them as separately loadable modules) if you're not using initrd, which is the
recommended method. Dave Phillips wrote a reasonably clear explanation of how
to create an initrd from a similar situation, you'll have to trawl the a-user
list archives to find this. I don't have it to hand.
--
cheers,
tim hall
http://glastonburymusic.org.uk/tim
We are the people We've been waiting for.
6904
days inactive
6911
days old
linux-audio-user@lists.linuxaudio.org
3 comments
4 participants
participants (4)
-
Hamish Low -
Hans Fugal -
Joel Roth -
tim hall