Slackware 13.0 with KDE 3.5.10?
in [Slackware]
|
Prev: useradd, upgrading Feunster
Next: Qemu help
From: barnabyh on 2 Jan 2010 11:27 * Tuxedo <tuxedo(a)mailinator.com> wrote: > Grant wrote: > > [...] > > Currently I have a newly installed Slackware with kernel 2.6.27.7. > > The installation was done with a full DVD version of Slackware 12.2 There is an official patch to kernel 2.6.27.31 for Slack 12.2. Barnabyh -- The general public is a bunch of morons who destroy the fun and life in everything it collectively touches. Disney is what the public wants. NASCAR is what the public wants. Windows is what the public wants. (Comment on Slashdot, Monday March 28 2005, @11:02AM, Gnome Removed From Slackware.)
From: Tuxedo on 2 Jan 2010 13:40 Glyn Millington wrote: > Tuxedo <tuxedo(a)mailinator.com> writes: > > > Grant wrote: > > > > [...] > > > >> You're being wimpish about upgrading kernel ;) > > > > Yes, wimpishness, as well not having a clue how to upgrade a kernel :-( > > > > You should find a clue here > > > > http://www.slackbasics.org/html-singlepage/slackware-basics.html#kernel > > This outlines the basic process pretty well. > > atb > > Glyn Proceding with various recommended post-install configurations in order to set up a 'daily use' system I wonder if the following is about right procedures? .... after a standard 12.2 DVD installation: I inserted the DVD that was used for the installation and mounted it as follows (although I guess there's a more 'normal' way): mount /dev/cdrom0 /tmp/DVD cp /tmp/DVD/kernels/speakup.s/config /usr/src/linux/.config I did the initial installation with the speakup.s kernel so I also used this one when compiling the kernel from the DVD. These were my next steps: cd /usr/src/linux make menuconfig Press Exit. Do you wish to save your new kernel configuration <Yes> The configuration was written to .config make ..... about an hour later: Note: According to http://www.slackbasics.org/html-singlepage/slackware-basics.html#chap-kernel-compile "a compressed kernel image 'bzImage' exists in /usr/src/linux/arch/i386/boot". This however is a symlink to /usr/src/linux/arch/x86/boot/bzImage Install kernel modules: Note: According to slackbasics.org it is a good idea to remove old modules as in 'rm -rf /lib/modules/2.6.27.7' However, I did mv /lib/modules/2.6.27.7 /lib/modules/2.6.27.7_old I then did: make modules_install A new /lib/modules/2.6.27.7 directory was created. I thereafter copied the generated bzImage into the boot directory. I noticed there is a boot image there already named: /boot/vmlinuz-speakup.s-2.6.27.7 which is 4570992 (about 4.5MB) I named the new image /boot/vmlinuz-speakup.s-2.6.27.7-new: cp -i /usr/src/linux/arch/x86/boot/bzImage /boot/vmlinuz-speakup.s-2.6.27.7-new The new image is 4540208, so only a bit smaller than the speakup kernel that already exist in the boot directory. I thereafter added the 'Image = /boot/vmlinuz-speakup.s-2.6.27.7-new' line to /etc/lilo.conf and ran lilo (which made an old floppy diskette for now). There were some warnings, but probably nothing important. This was the complete output of running 'lilo': * LBA32 addressing assumed * boot recod relocation boyond BPB is necessary: /dev/fd0 * The boot sector and map file are on different disks Added Slack-12.2-new * Added Slack-12.2 Added XP ------------------------ Slackware now boots fine from either Slack-12.2-new or Slack-12-2. Start up time counting from the LILO menu until the log-in prompt takes about 50 seconds for either LILO options. This may be an obvious question but with the exception of the kernel image filesize being a slightly different what is the actual difference in running the system with either kernel booting options at this stage, if any? Anyhow, I guess I should do an the initial RAM disk creation. I continued as follows: mkinitrd -c -k 2.6.27.7 -m reiserfs Output was: 2982 blocks An initrd-tree directory and initrd.gz file now exists. I added the /boot/initrd.gz bit to the relevant section of /etc/lilo.conf and ran 'lilo' again. I then rebooted and Slackware start-up appears to run fine, until it gets stuck on some critical errors: initrd.gz: Loading kernel modules from initrd image: scsi2 : SBP-2 IEEE-1395 mount: mounting /dev/root on /mnt failed: No such file or directory ERROR: No /sbin/init found in rootdev (or not mounted). Trouble ahead. You can try and fix it. Type 'exit' when things are done. /bin/sh: can't access tty; job control turned off / $ ieee1394: sbp2: Logged into SBP-2 device ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - May payload [2048] scsi 2:0:0:0: CD-ROM TSSTcorp CD/DVDW TS-L632B TM32 PQ: 0 ANSI: 0 sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 --- I press 'exit' and the following errors occur: / $ edit initrd.gz: exiting switch_root: bad newroot /mnt Kernel panic - not syncing: Attempting to kill init! .... Thats where all stops, even the screen gets frozen, no further keyboard input is possible, only switching off the power button. Slackware still boots up and runs fine from the old LILO option that does not load the recompiled kernel and initrd.gz. Does anyone have any idea what part(s) of the set-up I did wrong? Thanks, Tuxedo
From: Tuxedo on 2 Jan 2010 14:05 barnabyh wrote: > * Tuxedo <tuxedo(a)mailinator.com> wrote: > > Grant wrote: > > > > [...] > > > > Currently I have a newly installed Slackware with kernel 2.6.27.7. > > > > The installation was done with a full DVD version of Slackware 12.2 > > There is an official patch to kernel 2.6.27.31 for Slack 12.2. > > Barnabyh Do you know where to find more information about this and if the patch may address the Intel graphic xorg driver problems? Thanks, Tuxedo
From: barnabyh on 2 Jan 2010 17:47 * Tuxedo <tuxedo(a)mailinator.com> wrote: > barnabyh wrote: > >> * Tuxedo <tuxedo(a)mailinator.com> wrote: >> > Grant wrote: >> > >> > [...] >> > >> > Currently I have a newly installed Slackware with kernel 2.6.27.7. >> > >> > The installation was done with a full DVD version of Slackware 12.2 >> >> There is an official patch to kernel 2.6.27.31 for Slack 12.2. >> >> Barnabyh > > Do you know where to find more information about this and if the patch may > address the Intel graphic xorg driver problems? > > Thanks, > Tuxedo > Hi Tuxedo, have a look at the security advisories for 2009 on slackware.com, 18th Aug 2009, kernel (SSA 2009-230-01). I don't think it addresses your specific problem but addresses a rather important security issue (kernel bug). Barnabyh -- The general public is a bunch of morons who destroy the fun and life in everything it collectively touches. Disney is what the public wants. NASCAR is what the public wants. Windows is what the public wants. (Comment on Slashdot, Monday March 28 2005, @11:02AM, Gnome Removed From Slackware.)
From: jkaidor on 25 Jan 2010 23:37
*** Not only can you get the latest kernel, but you can also menuconfig it to take out all the hardware that you don't have. So you wind up with a smaller and faster kernel. There's an awful lot of hardware in a full-boat kernel. Admittedly, mostly in modules. - Jerry Kaidor |