On Fri, 2008-12-26 at 11:23 -0800, Ben Vlug wrote:
> I put a mem=512M and now it boots and boots into X

Ben,

So I assume you problems are now resolved.

Just ensure:

a) that you actually have 512M of physical system memory.  The kernel's
going to take your word for it and you'll get the mystery crash sometime
later if it tries to use physical memory you don't have.

b) The ivtv driver loads in the last log you sent were also griping
about running out of vmalloc space.  Make sure you've got vmalloc set
high enough so that those units are working OK too.

Regards,
Andy


> 
> 
> ______________________________________________________________________
> From: Andy Walls <[email protected]>
> To: Ben Vlug <[email protected]>
> Cc: User discussion about IVTV <[email protected]>
> Sent: Friday, December 26, 2008 12:46:43 PM
> Subject: Re: [ivtv-users] NVidia and CX18
> 
> On Fri, 2008-12-26 at 06:52 -0800, Ben Vlug wrote:
> > Hey Andy,
> >  
> > I added the value vmalloc=256M and I added a 1600 into the system.
> > Almost immediately on boot I got the following errors. I had to do
> an
> > "a" to edit and remove the new addition for the system to boot. 
> >  
> > initrd extends beyond end of memory
> 
> Ugh.  I now recall I ran across this "initrd" error message on a
> machine
> with very low memory.
> 
> 
> Well, I know you need more vmalloc space than the 112 MB that you are
> at. (You will need more than 143 MB of vmalloc space as a lower bound
> based on what you submitted previously).  256 MB kills the boot
> process.
> You said 192M didn't work.  That leaves 224 MB as the next trial in a
> binary search.
> 
> But what did /var/log/messages show when things didn't work with 192
> MB?
> 
> What did /proc/meminfo and /proc/iomem show with 192MB set and the
> HVR-1600 in the system? 
> 
> What does /proc/interrupts show for the interrupt the HVR-1600 is
> using?
> 
> Regards,
> Andy
> 
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0)
> > 
> > Thanks,
> >  
> > Ben
> > 
> 
> 
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
> 
> 


_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to