I did that but it doesn't get much farther. Here is as far back as I can see at the top of the screen:
Starting kerneloops:/sbin/start-stop-daemon: stat /usr/sbin/kerneloops: No such file or directory /etc/rc2.d/S23kerneloops: line 38: /var/run/kerneloops.pid: Read-only file system /etc/rc2.d/S26bootlogs:line 20: /var/run/motd: Read-only file sys I have narrowed the problem down to 1 kernel config paramater(CONFIG_LBDAF). If I build my kernel with CONFIG_LBDAF=y, the kernel will work. If I don't, it won't boot. I have submitted a bug report for linux-source-2.6.32 for this. My computer is a Lenovo thinkpad w500 with only a 150G hard drive so there is no need for CONFIG_LBDAF. I got a response from a Debian person saying to submit the kernel bug upstream and to give the kerneloops information. I don't know how to get any kerneloops information given what I see above. Brent On Fri, 2010-01-29 at 15:02 -0700, Matthew Wilcox wrote: > On Fri, Jan 29, 2010 at 01:23:13PM -0500, Brent S. Elmer Ph.D. wrote: > > I have built a new 2.6.32 kernel that is failing to boot. I don't know > > what the failure is. The previous kernel I > > built that works is 2.6.30. I used the config from the 2.6.30 and make > > oldconfig to configure for the 2.6.32 build. > > The failure is early on and has scrolled off the screen. What I do see on > > the screen is: > > /etc/rc2.d/S23kerneloops: line 29: basename: command not found > > OK, change line 29 of /etc/init.d/kerneloops from: > > prog=$(basename $exec) > > to: > > prog=kerneloops > > Sorry about that, I'll fix it in the next upload. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
