SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
>
> liloconfig doesn't show ncurses menu? Did you really run it from chroot?
Theorically yes.
>
>
> You can install Grub instead of LILO, I replaced LILO with Grub using the same Slint ISO. And I created here exactly the same partitions layout: sda1 is swap and sda2 is root (/).
OK, I try it.
> Try this when booted into Slint live system:
> Code:
>
> mount /dev/sda2 /mnt
> mount -t proc none /mnt/proc
> mount -o bind /dev /mnt/dev
> mount -o bind /sys /mnt/sys
> chroot /mnt /bin/bash
> grub-install /dev/sda
> grub-mkconfig -o /boot/grub/grub.cfg
I get this error:
Code:
/ [To install, type setup] # grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-huge-3.10.17
Found linux image: /boot/vmlinuz-generic-3.10.17
No volume groups found
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
done
/ [To install, type setup] #
My partition layout :
Code:
Disk /dev/sda: 15.8 GB, 15795748864 bytes
64 heads, 32 sectors/track, 15064 cylinders, total 30851072 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5090f80a
Device Boot Start End Blocks Id System
/dev/sda1 2048 4196351 2097152 82 Linux swap
/dev/sda2 4196352 30851071 13327360 83 Linux
Disk /dev/sdb: 4026 MB, 4026531840 bytes
255 heads, 63 sectors/track, 489 cylinders, total 7864320 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0f2c53a1
Device Boot Start End Blocks Id System
/dev/sdb1 * 0 4712399 2356200 0 Empty
/dev/sdb2 2688 5567 1440 ef EFI (FAT-12/16/32)
Disk /dev/sdb1: 2412 MB, 2412748800 bytes
255 heads, 63 sectors/track, 293 cylinders, total 4712400 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0f2c53a1
Device Boot Start End Blocks Id System
/dev/sdb1p1 * 0 4712399 2356200 0 Empty
/dev/sdb1p2 2688 5567 1440 ef EFI (FAT-12/16/32)
Any idea ?
Thanks, see you.
---------- Post added 01-12-15 at 09:35 PM ----------
> Today, 06:38 PM #29
> Didier Spaier
Hi Didier ,
>
> Well xavi_slacky, as you used a Slint installer, I assume that I ought you some support or after sales service
>
> First, please confirm that :
>
> you downloaded the 32-bit image
Not, 64-bit.
> you checked the integrity of the ISO using the md5sum before writing it on a DVD or USB stick
>
Not.
> Then please boot again the installer and once logged in provide the output of following command:
> Code:
>
> lsblk -o name,type,model,size,fstype,mountpoint,label,uuid
>
Code:
/ [To install, type setup] # lsblk -o name,type,model,size,fstype
NAME TYPE MODEL SIZE FSTYPE
sda disk Transcend 16GB 14.7G
|-sda1 part 2G swap
`-sda2 part 12.7G ext4
sdb disk Transcend 4GB 3.8G iso9660
|-sdb1 part 2.3G iso9660
`-sdb2 part 1.4M vfat
sdc disk Transcend 2GB 1.9G
`-sdc1 part 1.9G vfat
/ [To install, type setup] # lsblk -o mountpoint,label,uuid
MOUNTPOINT LABEL UUID
8a3286fb-3f57-4d6c-8a8f-1e6edac3ab89
13ce6ae3-0bae-4627-a13f-9cc332093c21
Slint_installation_media
Slint_installation_media
Slint_installation_media 98B7-1A28
3882-18E3
/ [To install, type setup] #
> Then, please indicate how you intend to use each of the partitions listed. Hopefully this will help us to help you.
>
I understand you with "indicate how you intend to use each of the partitions listed".
/ [To install, type setup] # grub-mkconfig -o /boot/grub/grub.cfg
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-huge-3.10.17
Found linux image: /boot/vmlinuz-generic-3.10.17
No volume groups found
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
done
/ [To install, type setup] #
It isn't an error!!!
You installed Grub and added two kernel images to Grub menu.
When Grub tried to add the third image (that resides your usb stick) it fails, because Grub can't handle that image. It is normal.
Did you try to reboot immediately without trying to restore LILO instead installed Grub?
Added:
Look at this: http://i.imgur.com/Hf9t6Wp.jpg
it is the same output as you had, you just need to reboot after that error.
If you tried to install LILO after Grub installation, you ruined Grub image at MBR.
Run once again Grub installation (all the steps I wrote above) via chroot and reboot immediately after grub-mkconfig. Despite any "errors" and "warnings"
Do not forget to unplug stick when trying to boot with Grub.
>
> Quote:
> Originally Posted by xavi_slacky View Post
> >
> I get this error:
>
> Code:
>
> / [To install, type setup] # grub-mkconfig -o /boot/grub/grub.cfg
> Generating grub.cfg ...
> Found linux image: /boot/vmlinuz-huge-3.10.17
> Found linux image: /boot/vmlinuz-generic-3.10.17
> No volume groups found
> grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
> done
> / [To install, type setup] #
>
> It isn't an error!!!
> You installed Grub and added two kernel images to Grub menu.
> When Grub tried to add the third image (that resides your usb stick) it fails, because Grub can't handle that image. It is normal.
> Did you try to reboot immediately without trying to restore LILO instead installed Grub?
>
> Added:
> Look at this:
> http://i.imgur.com/Hf9t6Wp.jpg
> it is the same output as you had, you just need to reboot after that error.
OK, I following yours steps and after I reboot the box, I get a black screen, any more ...
From the output of lsblk, you are trying to install on an SDHC flash memory card...
You could have told that earlier. That's very important
As Slackware alone needs ~ 8GB there is only 8GB left for you data. But you know that already.
What's more important is that you install on a removable device whose name (/dev/sda /dev/sdb, etc.) can change every time you boot. Thus you should name your root partition (and also the swap) by UUID, as indicated in the output of lsblk, in grub.cf or lilo.conf as well as in /etc/fstab as the UUID never change. Otherwise the name of the root partition at boot time won't probably be the same as in these files thus you get a kernel panic. Come back if you need help to do that.
Installation to USB drive requires some kernel options to be enabled: you need to enable ehci_hcd and generic usb support options. They both must be built-in, not as separate modules. And it may require initramfs.
Just checked kernel-huge config, ehci_hcd set to be built as separate module.
It explains why do you have kernel panic - there is no kernel module to work with USB drive. It will not work.
You need to re-configure and re-build kernel
As well it may require to add kernel command line options to Grub/LILO menu: "rootwait" and/or "rootdelay"
It should be said at the very beginning that you trying to install to USB drive.
>
> Installation to USB drive requires some kernel options to be enabled: you need to enable ehci_hcd and generic usb support options. They both must be built-in, not as separate modules. And it may require initramfs.
> Just checked kernel-huge config, ehci_hcd set to be built as separate module.
> It explains why do you have kernel panic - there is no kernel module to work with USB drive. It will not work.
> You need to re-configure and re-build kernel
>
> As well it may require to add kernel command line options to Grub/LILO menu: "rootwait" and/or "rootdelay"
>
> It should be said at the very beginning that you trying to install to USB drive.
Installation to USB drive requires some kernel options to be enabled: you need to enable ehci_hcd and generic usb support options. They both must be built-in, not as separate modules. And it may require initramfs.
Just checked kernel-huge config, ehci_hcd set to be built as separate module.
It explains why do you have kernel panic - there is no kernel module to work with USB drive. It will not work.
You need to re-configure and re-build kernel
As well it may require to add kernel command line options to Grub/LILO menu: "rootwait" and/or "rootdelay"
It should be said at the very beginning that you trying to install to USB drive.
At first, what is your goal? Why do you trying to install system to USB?
Is your computer just lacks of harddrive or you are trying to make a bootable stick with system that you could use at different computers?
If you do not planning to use this stick on different machines, it will be easier to install system to stick.
If you planning to use it with different machines, it will require some additional tweaks.
How do you planning to use it?
it will be a bit easier since it going to be used at one computer only.
Boot into your live system and chroot into installed system
Code:
mount /dev/sda2 /mnt
mount -t proc none /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
chroot /mnt /bin/bash
now you have to tweak kernel config and rebuild kernel and modules
Code:
cd /usr/src/linux
cp .config .config-old
make menuconfig
when configuration tool will start, navigate to "Device Drivers -> USB support -> EHCI HCD (USB 2.0) support". Right now you have this option set to "M". You need to set it to "*", just press space key to change it to "*"
As well you can set "xHCI HCD (USB 3.0) support" option to "*"
Return to top level menu by selecting "Exit" (it requiers to select "Exit" + Enter two times)
Navigate to "General setup" section, select "Local version -append to kernel release" item and press Enter. Type "-usb" in text field and press Enter.
Select "Save" at bottom, and confirm suggested file name ".config" by pressing Enter.
Select "Exit" twice and exit menuconfig tool.
Now run:
Code:
make && make modules_install
it will take a lot of time (approximately 1 hour or so), so be patient.
Now you have to copy your new kernel to /boot directory.
Depending on your architecture, type this for 64bit:
correct your /etc/lilo.conf: you need to change "image = /boot/vmlinuz" to "/boot/vmlinuz-huge-3.10.17-usb"
as well you have to change this string:
append = " vt.<your code page>"
to
append = " vt.<your code page> rootwait rootdelay=20"
rootdelay parameter instructs kernel to wait for 20 secs, it may be needed to be sure usb stick is ready to mount.
it will be a bit easier since it going to be used at one computer only.
Boot into your live system and chroot into installed system
Code:
mount /dev/sda2 /mnt
mount -t proc none /mnt/proc
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
chroot /mnt /bin/bash
now you have to tweak kernel config and rebuild kernel and modules
Code:
cd /usr/src/linux
cp .config .config-old
make menuconfig
when configuration tool will start, navigate to "Device Drivers -> USB support -> EHCI HCD (USB 2.0) support". Right now you have this option set to "M". You need to set it to "*", just press space key to change it to "*"
As well you can set "xHCI HCD (USB 3.0) support" option to "*"
Return to top level menu by selecting "Exit" (it requiers to select "Exit" + Enter two times)
Navigate to "General setup" section, select "Local version -append to kernel release" item and press Enter. Type "-usb" in text field and press Enter.
Select "Save" at bottom, and confirm suggested file name ".config" by pressing Enter.las hay que vienen del otro lado del planeta ...
Select "Exit" twice and exit menuconfig tool.
Now run:
Code:
make && make modules_install
it will take a lot of time (approximately 1 hour or so), so be patient.
Now you have to copy your new kernel to /boot directory.
Depending on your architecture, type this for 64bit:
correct your /etc/lilo.conf: you need to change "image = /boot/vmlinuz" to "/boot/vmlinuz-huge-3.10.17-usb"
as well you have to change this string:
append = " vt.<your code page>"
to
append = " vt.<your code page> rootwait rootdelay=20"
rootdelay parameter instructs kernel to wait for 20 secs, it may be needed to be sure usb stick is ready to mount.
Save changes in lilo.conf and run
Code:
lilo
exit
reboot
Hi Teufel ,
I following yours steps and I get an error, after reboot, I don't get LILO typical screen, and it show many 99 numbers and halted.
What an error did you get? What a command failed with error?
Please be more detailed.
Regarding LILO "99" message, it is an error code.
Quote:
Errors 99 and 9A usually mean the map file (-m or map=) is not readable, likely because LILO was not re-run after some system change, or there is a geometry mis-match between what LILO used (lilo -v3 to display) and what is actually being used by the BIOS (one of the lilo diagnostic disks, available in the source distribution, may be needed to diagnose this problem).
There are few reasons why LILO indicates 99 error code
1. Disks boot order was changed in BIOS and now current order doesn't match to disks order when LILO was installed.
2. Kernel location was changed, but "lilo" was not re-run to reflect changes in lilo.conf
3. Root partition was not marked as active ("Boot" flag must be set to sda2)
4. BIOS must be set to access harddrive by LBA, not as "Auto".
5. You forgot to detach installation stick (live USB)
6. You are trying to install LILO to SD card, and LILO not aware of it. Especially if you using laptop's cardrider. Most of them unbootable. Isn't it your case?
Well.
Boot into live USB, chroot into system. Edit /etc/lilo.conf, add these lines at the top:
Code:
disk=/dev/sda
bios=0x80
disk=/dev/sdb
bios=0x81
it will instruct lilo which drive is first and which is second. Save changes and exit editor.
Why did you not pay attention to Didier's post here? He created SLINT and is a very experienced SLACKWARE user who has written articles about installing slackware to various media.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
