Path: csiph.com!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Unknown Newsgroups: comp.os.linux.misc Subject: Re: booting with usb Date: Sat, 11 Apr 2015 15:03:46 +0000 (UTC) Organization: A noiseless patient Spider Lines: 115 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 11 Apr 2015 15:03:46 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="14cecb64d7591c5f383c2239cb82f311"; logging-data="10415"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18R7V+6lrwK7/5mpmZ/zhxndlH5Fq+Ee9c=" User-Agent: Pan/0.133 (House of Butterflies) Cancel-Lock: sha1:kmEwHXWZR4pu1TwUMZDkZ3v9lOs= Xref: csiph.com comp.os.linux.misc:14470 On Wed, 08 Apr 2015 19:15:45 +0000, Charlie Gibbs wrote: > On 2015-04-08, William Unruh wrote: > >> On 2015-04-08, Bill Cunningham wrote: >> >>> Ok someone told me this needs to be done when booting from a usb. >>> I have >>> looked all over and can't find the steps. To boot from usb I was >>> advised to use a uuid in fstab. Ok fine. Do I need to do anything with >>> initramfs.conf ? initramfs has to be alter too somehow. Does any one >>> know anything about this? >> >> Information would be good. What computer? Does it use URFI or legacy >> boot? Is usb booting enabled in the bios? Whic distribution are you >> trying to boot? AFAIK BIOS must show the facility [in its menu]. probably USB-CDROM and my this old MOBO [does SATA & old-IDE] has a selection for "USB zip" [strange name?!] which boots the USBstik, which the Slak13 installation has setup; and which I've been editing, since the Slak install just wrote to the [obviously M$ formatted] new USBstik. IMO initramfs.conf can't be accessed until booting has suceeded? ===> here's part of the mess:--- ~:fdisk -l /dev/sdb Disk /dev/sdb: 8023 MB, 8023703552 bytes 247 heads, 62 sectors/track, 1023 cylinders Units = cylinders of 15314 * 512 = 7840768 bytes Disk identifier: 0xde8e7bb0 This doesn't look like a partition table Probably you selected the wrong device. Device Boot Start End Blocks Id System /dev/sdb1 ? 197240 197273 253319 e4 SpeedStor Partition 1 has different physical/logical beginnings (non-Linux?): phys=(190, 120, 0) logical=(197239, 8, 51) Partition 1 has different physical/logical endings: phys=(544, 125, 44) logical=(197272, 29, 24) Partition 1 does not end on cylinder boundary. /dev/sdb2 ? 65729 195542 993984023 98 Unknown Partition 2 has different physical/logical beginnings (non-Linux?): phys=(1010, 16, 43) logical=(65728, 56, 10) Partition 2 has different physical/logical endings: phys=(205, 205, 22) logical=(195541, 245, 55) Partition 2 does not end on cylinder boundary. /dev/sdb3 ? 110790 236159 959953209 7d Unknown Partition 3 has different physical/logical beginnings (non-Linux?): phys=(252, 139, 46) logical=(110789, 48, 54) Partition 3 has different physical/logical endings: phys=(367, 195, 2) logical=(236158, 138, 25) Partition 3 does not end on cylinder boundary. /dev/sdb4 ? 244 249 32768 0 Empty Partition 4 has different physical/logical beginnings (non-Linux?): phys=(0, 10, 0) logical=(243, 229, 53) Partition 4 has different physical/logical endings: phys=(0, 0, 0) logical=(248, 51, 54) Partition 4 does not end on cylinder boundary. Partition table entries are not in disk order -------------------Here's the USBstik [single partition's contents:- # ls -l total 12148 -rwxr-xr-x 1 root root 595 2014-02-25 12:50 HOW2boot2Win -rwxr-xr-x 1 root root 2267 2015-04-06 20:44 Log drwxr-xr-x 2 root root 4096 2014-09-25 19:04 Mandr9fd0Btr drwxr-xr-x 2 root root 4096 2014-02-25 12:50 etc -rwxr-xr-x 1 root root 653 2013-09-02 22:27 f1.txt ++ drwxr-xr-x 4 root root 4096 2014-10-22 15:35 fromwxp.dir -rwxr-xr-x 1 root root 2375866 2014-09-17 14:28 initrd.gz <- for kz drwxr-xr-x 2 root root 4096 2014-09-17 14:32 kogi4.dos -rwxr-xr-x 1 root root 4907792 2014-09-17 14:29 kz <-difrnt Knl -r-xr-xr-x 1 root root 10827 2013-09-02 22:27 ldlinux.sys ++ -rwxr-xr-x 1 root root 708 2013-11-28 19:13 message.txt ++ -rwxr-xr-x 1 root root 906 2014-12-17 15:17 sylinux.cfg ++ -rwxr-xr-x 1 root root 302 2014-09-17 15:27 sysBKcfg ++ -rwxr-xr-x 1 root root 396 2014-10-09 14:49 syslOct.cfg ++ -rwxr-xr-x 1 root root 609 2014-09-29 11:11 syslOct.cfgL ++ -rwxr-xr-x 1 root root 974 2015-04-06 20:46 syslinux.cfg ++ -rwxr-xr-x 1 root root 411 2014-10-09 19:10 syslinux.cfgC32 ++ -rwxr-xr-x 1 root root 309 2014-09-17 14:38 syslnxB2.cfg ++ drwxr-xr-x 2 root root 4096 2014-07-12 14:06 tts -rwxr-xr-x 1 root root 123172 2014-10-09 15:57 vesamenu.c32 ++ -rwxr-xr-x 1 root root 4940304 2013-09-02 22:27 vmlinuz ++ The ones marked "++" were from the Slak13 installation; PLUS ones that I've edited/experimented. vesamenu.c32 and ldlinux.sys are the original binaries. Since it's a 8GB stik, I've written other M$ stuff for if/when I boot winXP. hexdump of ldlinux.sys [apparently the loader] is:-- 00000000 0D 0A 53 59 53 4C 49 4E 55 58 20 33 2E 35 32 20 ..SYSLINUX 3.52 00000010 32 30 30 37 2D 30 39 2D 32 35 20 00 0D 0A 1A 00 2007-09-25 ..... 00000020 FE 02 B2 3E 44 07 41 78 92 0A 15 00 D1 8A 9D A5 ...>D.Ax........ ------ one text files does the config; which I've expanded/experimented; and one does the message/prompts. It works well for me. And an alternative boot-route to different instalattion/s & M$ is to unplug the stik and go via the 2nd-alternative: hard-disk:MBR.