Siduction Forum
Siduction Forum => Installation - Support => Topic started by: hepp on 2014/08/14, 18:28:56
-
Im trying to put siduction ISO on an USB stick for installing siduction on a lenovo laopto but keep failing. Following the instructions but only met by a grub command prompt when booting from the stick.
Tried both KDE and LXQT. Formatted as ext2 and vfat32 with two different sticks (4GB stick and 8GB). I've earlier installed aptosid and fedora on usb stick without problems.
Since I don't (as most modern hardware) have CD drive I do need the USB solution.
What I'm I doing wrong ? Any help is appreciated.
Thank's
-
I have had good luck with unetbootin in recent times.
-
@hepp
try dd to put the image on the pure metal - thats the method we prefer.
@dibl - really - cool, you've got the job as our new unetbootin-supporter...
... btw, never get it working with unetbootin, but that may have changed :P
-
@dibl - really - cool, you've got the job as our new unetbootin-supporter...
... btw, never get it working with unetbootin, but that may have changed :P
Well, let me make one right now and post back about my success.
-
Well ... I did make a bootable 64-bit paintitblack stick just now. Unfortunately, the only computer in my house that will boot it to the desktop has a broken ethernet chip and needs the Broadcom firmware to run wifi, so I can't post from that one (without doing more work). This release has a "EHCI-orion module not found" problem that dumps my 64-bit desktop systems to a busybox prompt.
Here is all you need to do ("x" is YOUR device ID and don't get it wrong!):
dd if=/dev/zero of=/dev/sdx bs=512 count=1
Then from the KDE desktop "kdesu gparted" and make an ext2 or fat32 partition, and mark it bootable.
Pull the stick and reinsert it, and use your dolphin or whatever file manager to mount it to /media.
Alt-F2 "kdesu unetbootin", choose your ISO file, choose your /dev/sdx stick, and it works. Even on a junky old plastic Verbatim stick with a proprietary hidden partition on it.
-
Thank you Dibi. Appreciated!
I followed the gparted, format to ext2 etc running unetbootin.
Now there was some hope of success. After complaint of files missing (menu.c32 and libutil.c32) I copied them from my laptop to the root of the usb. Now it stops at
Probing devices [sr0]
Failed to detect live media
...etc
ending with /bin/sh can't access tty; job control turned off
where it stops
.....
Any clue ?
-
Before the busybox prompt, do you see an error message approximately like: "ehci-orion module not found"?
If so, then that is a problem that cropped up in the last couple of releases -- I see that too on some systems. I think it must be specific to some kinds of hardware, and not on others. I can boot a Dell E6500 laptop with no problem, but get the busybox on 3 different Intel desktops. I don't think it has anything to do with how you make the USB stick.
EDIT: Here it is. (https://forums.kali.org/showthread.php?21575-Debian-Live-image-failed-to-boot)
-
Yes, it does come with the ehci-orion not found.
I'm primarily trying it on a lenovo x121e thinkpad. I have earlier installed aptosid on a similar laptop. But that was about two years ago.
-
Check the edit in my last post. The problem is not your USB stick, unfortunately.
-
@hepp -- "Another day, another way."
A little googling revealed that the ehci-orion module problem is related to some combinations of USB hardware + the squashfs filesystem (used by unetbootin). That is why the stick I made yesterday booted on the Dell laptop but not the Intel motherboards. Therefore, the way around that issue is to use the ISO filesystem directly. So, here is how I did it today, working from my backup directory where I keep old ISO files that I might want in the future:
root@imerabox:/mnt/DATA/BACKUPS/ISO# dd if=/dev/zero of=/dev/sdf bs=1024 count=1
1+0 records in
1+0 records out
1024 bytes (1.0 kB) copied, 5.5123e-05 s, 18.6 MB/s
root@imerabox:/mnt/DATA/BACKUPS/ISO# ls
18nov2012_familypix.iso
debian-live-7.0.0-amd64-kde-desktop.iso
debian-live-7.5.0-amd64-kde-desktop.iso
landofthebuckeye_jul2014.iso
pmagic_2014_01_04.iso
siduction-11.1-OneStepBeyond-kde-amd64-201112302141.iso
siduction-12.2.0-ridersonthestorm-kde-amd64-201212092131.iso
siduction-13.1.0-firestarter-kde-amd64-201305211844.iso
siduction-13.2.1-december-kde-amd64-201401272125.iso
siduction-13.2.1-december-lxde-i386-201401272144.iso
siduction-13.2.1-december-nox-amd64-201401272149.iso
siduction-14.1.0-paintitblack-lxqt-amd64-201405081704.iso
trusty_tahr.iso
VMware-tools-linux-116369.iso
root@imerabox:/mnt/DATA/BACKUPS/ISO# dd if=siduction-14.1.0-paintitblack-lxqt-amd64-201405081704.iso of=/dev/sdf
1624064+0 records in
1624064+0 records out
831520768 bytes (832 MB) copied, 356.13 s, 2.3 MB/s
This was the same old Verbatim USB stick that I used yesterday. Now it boots in all my 64-bit hardware.
@melmarker, I'll take a pass on that unetbootin support job! ;D
-
@dibl: only a hint - dd bs=4M if... might be a good idea :) 1k block size, hmm better than 1 Byte, but we live in the 21. century
-
Yes, I do see that would be faster -- thanks! Basically, I fear dd ;D . So I don't use it often and don't really know how to be efficient with it.
-
Basically, I fear dd ;D .
I fear unetbootin. Had several failures with it but I don't recall any with dd.
-
In 99% of all cases unetbootin does not work propper with isohybrid images.
That's why no one of us suggests unetbootin and dd makes the job fine.
-
Solved! I finally had it working by using dd=
mkfs.ext2 /dev/sdg
dd if=~/siduction-13.2.1-december-lxde-i386-201401272144.iso of=/dev/sdg bs=4M; sync
Thank you Dibl and all for helping me!
-
Solved! I finally had it working by using dd=
mkfs.ext2 /dev/sdg
dd if=~/siduction-13.2.1-december-lxde-i386-201401272144.iso of=/dev/sdg bs=4M; sync
The mkfs bit is redundant as dd will overwrite the filesystem anyway.