Yeah, it's the stock 2.6.18.3 kernel. I did it b/c I was trying to
learn some fundamental skills I thought would transfer to other distros.
I was just on the phone with David, and he suggested that I look at that
char/frame stuff.
For my distro of Slackware, this seems the path to least resistance:
1. install latest Slack-friendly 2.6 kernel
2. untar that kernel
3. run makeoldconfig in that untar dir
4. answer all the questions for my hardware
5. make a new bzImage based off that
6. boot to that kernel
Joel Brauer wrote:
Out of curiosity, are you guys trying to use a vanilla kernel? I would
really suggest getting a patchset from a trusted maintainer. The issue is
that there is really no longer a dev build of the kernel, so the 2.6 kernel
releases are also dev releases leaving the compatibility and stability
up to
the maintainers. Also check under the Character devices (IIRC) section and
make sure you compiled in the frame buffer support and such.
If it's a laptop, bring it with you tonight... we'll get it working.
-joel
On 12/2/06, Roger Rustad <[email protected]> wrote:
Alright, I finally recompiled it and got it "working". Not sure what
exactly I did, but it's back to the 2.4 kernel.
I am now looking through my history and trying to make sense of the
madness (David, I shared all of this with you via a Google docs
collaboration invite)
This is my history after we played around with the fortune cookie DB.
For whatever reason, I don't see your other kernel compiling commands.
I wonder if that's b/c they were part of another tty session?
426 fortune startrek
427 fortune linuxcookie
428 cd
429 X :1
430 ls
431 ls
432 ls
433 pwd
434 cd /usr/
435 ls
436 cd src/
437 ls
438 cd linux-2.6.18.3/
439 ls
440 cd arch
441 ls
442 cd i386/
443 ls
444 cd boot
445 ls
446 make menuconfig
447 cd ../../..
448 ls
449 cd ..
450 make menuconfig
451 menuconfig
452 ls
453 make menuconfig
454 chroot /usr/src
455 cd /bin/sh
456 ls
457 cd ../..
458 ls
459 cd bin
460 ls
461 chroot
462 cd /usr/src
463 chroot --help
464 ls
465 make menuconfig
466 chroot /bin/sh
467 chroot /bin
468 chroot /bin/sh
469 ls
470 pwd
471 make menuconfig
472 ls
473 cd linux
474 ls
475 make menuconfig
476 ls
477 cd ..
478 ls
479 cd linux-2.6.18.3/
480 ls
481 make menuconfig
482 time make clean && make && make_modules
483 mount /boot
484 ls
485 cd /boot
486 ls
487 ls -al mvlinuz
488 ls -al vmlinuz
489 time
490 date
491 cd -
492 make install
493 module-rebuild rebuild
494 cd /usr/src
495 ls
496 ln -sf linux-2.6.18.3/ linux
497 mount /boot
498 reboot
499 reboot
500 exit
501 cd ~./
502 ls
503 cd ~/
504 ls
505 cd scripts/
506 ls
507 cd ..
508 ls
509 history
510 history > /tmp/history.txt
This is odd, now that I look at it. A lot of what I and/or David did
isn't here. Some of my chrooted stuff isn't here, and neither is
David's kernel compilation commands.
Roger
_______________________________________________
909linux mailing list
[email protected]
http://909linux.org/cgi-bin/mailman/listinfo/909linux
