|
Aradalf
|
 |
« on: February 08, 2011, 10:43:16 PM » |
|
As explained in this thread, I have successfully accessed the BIOS on my CR-48. Now when booting it up, this is what happens: So I proceed to boot up my PCLOS-LiveUSB, made with PCLinuxOS-LiveUSB. It has LXDE-mini, Phoenix-mini, and E17-light on it. The reason I put these light ones was because the CR-48 only has a 16GB SSD drive, and I wanted to keep it dual-boot. I booted up LXDE-mini, and upon switching to Verbose, found that it stopped booting at: Searching for the loop image: /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5 /dev/sda6 /dev/sda7 /dev/sda8 /dev/sda9 /dev/sda10 /dev/sda11 /dev/sda12 [DONE} ERROR: Unable to mount the livecd
Dropping you to a limited shell. Loading /initrd/bin/ash /initrd/bin/ash: can't access tty: job control turned off. $_
This happened with all three flavors of PCLOS that I had on the LiveUSB. Anybody have any advice on what I could try? BTW, it has an Intel Atom N455 @ 1.66GHz Single-Core, 2 GB RAM in the first slot, and the second slot empty, Sandisk SSD P4 16GB, and an Intel GMA integrated graphics card. I found this all out from the BIOS. Anyone have any ideas? 
|
|
|
|
|
Logged
|
|
|
|
|
T6
|
 |
« Reply #1 on: February 08, 2011, 10:50:33 PM » |
|
my netbook has the same hardware but less ram
i installed pclinux by using livecd on a external optical dvd burner
|
|
|
|
|
Logged
|
"It pays to keep an open mind, but not so open your brains fall out."
Carl Sagan
|
|
|
|
Aradalf
|
 |
« Reply #2 on: February 08, 2011, 10:55:35 PM » |
|
my netbook has the same hardware but less ram
i installed pclinux by using livecd on a external optical dvd burner
I don't have an external optical drive, but if you think it would work, I'll go get one. My desktop's optical drive has been broken for a few years now too, but I never really needed another, since who uses cds these days?  So you think that booting from an external optical drive will work?
|
|
|
|
|
Logged
|
|
|
|
|
T6
|
 |
« Reply #3 on: February 08, 2011, 10:59:49 PM » |
|
no, can't say that but i did it here and worked
if you could have one borrowed just for testing it would be better
also the boot codes to force detection and similar stuff, don't know where is that post
|
|
|
|
|
Logged
|
"It pays to keep an open mind, but not so open your brains fall out."
Carl Sagan
|
|
|
|
Aradalf
|
 |
« Reply #4 on: February 08, 2011, 11:10:52 PM » |
|
no, can't say that but i did it here and worked
if you could have one borrowed just for testing it would be better
also the boot codes to force detection and similar stuff, don't know where is that post
Well, I'll try with an external optical drive and report back.
|
|
|
|
|
Logged
|
|
|
|
|
Was_Just19
|
 |
« Reply #5 on: February 09, 2011, 05:02:06 AM » |
|
As explained in this thread, I have successfully accessed the BIOS on my CR-48. Now when booting it up, this is what happens: So I proceed to boot up my PCLOS-LiveUSB, made with PCLinuxOS-LiveUSB. It has LXDE-mini, Phoenix-mini, and E17-light on it. The reason I put these light ones was because the CR-48 only has a 16GB SSD drive, and I wanted to keep it dual-boot. I booted up LXDE-mini, and upon switching to Verbose, found that it stopped booting at: Searching for the loop image: /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5 /dev/sda6 /dev/sda7 /dev/sda8 /dev/sda9 /dev/sda10 /dev/sda11 /dev/sda12 [DONE} ERROR: Unable to mount the livecd
Dropping you to a limited shell. Loading /initrd/bin/ash /initrd/bin/ash: can't access tty: job control turned off. $_
This happened with all three flavors of PCLOS that I had on the LiveUSB. Anybody have any advice on what I could try? BTW, it has an Intel Atom N455 @ 1.66GHz Single-Core, 2 GB RAM in the first slot, and the second slot empty, Sandisk SSD P4 16GB, and an Intel GMA integrated graphics card. I found this all out from the BIOS. Anyone have any ideas?  I would suggest that you edit the heading to reflect that fact you are asking about a LiveUSB and not a LiveCD  *** From your output, it appears that the system cannot find the named .sqfs file on your system. To try to determine the cause a lot more info is needed. Please post back with the results of the following (including command used) ... fdisk -l [lower case L and run as root] Highlight the partition you are trying to use in the output posted above. The contents of the /boot/grub/menu.lst file that is in control of the booting. Also, do an MD5sum comparison of the .sqfs file on the USB device and the .sqfs from the downloaded ISO. Also of course confirm that the ISO itself produces the correct MD5sum when compared to the number provided with it. Please take the time to confirm the above and post back about each so that we are sure of those items before drawing any conclusions. regards.
|
|
|
|
|
Logged
|
|
|
|
|
Was_Just19
|
 |
« Reply #6 on: February 09, 2011, 05:21:23 AM » |
|
Some further thoughts after reading the linked-to thread ...... So I proceed to boot up my PCLOS-LiveUSB, made with PCLinuxOS-LiveUSB. It has LXDE-mini, Phoenix-mini, and E17-light on it. The reason I put these light ones was because the CR-48 only has a 16GB SSD drive, and I wanted to keep it dual-boot. This makes it all very confusing ...... if you have installed the Live PCLOS on a USB thumb drive, then why the reference to the internal SSD drive, which is not connected with booting from a thumb drive? Maybe a better explanation of what set up you have is needed to sort out this confusion. regards.
|
|
|
|
|
Logged
|
|
|
|
|
Aradalf
|
 |
« Reply #7 on: February 09, 2011, 03:59:28 PM » |
|
Some further thoughts after reading the linked-to thread ...... So I proceed to boot up my PCLOS-LiveUSB, made with PCLinuxOS-LiveUSB. It has LXDE-mini, Phoenix-mini, and E17-light on it. The reason I put these light ones was because the CR-48 only has a 16GB SSD drive, and I wanted to keep it dual-boot. This makes it all very confusing ...... if you have installed the Live PCLOS on a USB thumb drive, then why the reference to the internal SSD drive, which is not connected with booting from a thumb drive? Maybe a better explanation of what set up you have is needed to sort out this confusion. regards. I just simply stated that because once I install them, I need the disk space on the ssd drive for files and other stuff. The 8 GB flash drive is set up with one FAT32 primary partition, for files that can be accessed on windows, and one ext4 partition for the LiveUSB files. fdisk -l returns this(/dev/sdg is my flash drive): [root@CHON PCLOS-LiveUSB]# fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes 194 heads, 44 sectors/track, 73235 cylinders, total 625142448 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: 0x696e1c95
Device Boot Start End Blocks Id System /dev/sda1 2048 10631167 5314560 27 Unknown /dev/sda2 * 10631168 272766975 131067904 7 HPFS/NTFS /dev/sda3 272767880 625133959 176183040 f W95 Ext'd (LBA) /dev/sda5 272767924 304231575 15731826 83 Linux /dev/sda6 304231620 312622463 4195422 82 Linux swap / Solaris /dev/sda7 312622508 375541319 31459406 83 Linux /dev/sda8 375543808 625133567 124794880 83 Linux
Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 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: 0x44fdfe06
Device Boot Start End Blocks Id System /dev/sdb1 * 63 976768064 488384001 7 HPFS/NTFS
Disk /dev/sdg: 7998 MB, 7998537728 bytes 247 heads, 62 sectors/track, 1020 cylinders, total 15622144 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: 0x000709fa
Device Boot Start End Blocks Id System /dev/sdg1 2048 7813119 3905536 b W95 FAT32 /dev/sdg2 7813120 15622143 3904512 83 Linux
These are the contents of /boot/grub/menu.lst on /dev/sdg2: timeout 10 color black/cyan yellow/cyan gfxmenu (hd0,1)/boot/gfxmenu default 0 title LXDE-mini kernel (hd0,1)/LXDE-mini_1/vmlinuz livecd=LXDE-mini_1 fromusb root=UUID=3ab0e69b-e78f-4ba1-831d-42982180af2c acpi=on vga=791 splash=silent initrd (hd0,1)/LXDE-mini_1/initrd.gz title LXDE-mini with Persistence kernel (hd0,1)/LXDE-mini_1/vmlinuz livecd=LXDE-mini_1 fromusb root=UUID=3ab0e69b-e78f-4ba1-831d-42982180af2c acpi=on fstab=rw,noauto vga=791 changes_dev=UUID=3ab0e69b-e78f-4ba1-831d-42982180af2c splash=silent initrd (hd0,1)/LXDE-mini_1/initrd.gz
title Phoenix-mini kernel (hd0,1)/Phoenix-mini_1/vmlinuz livecd=Phoenix-mini_1 fromusb root=UUID=3ab0e69b-e78f-4ba1-831d-42982180af2c acpi=on vga=791 splash=silent initrd (hd0,1)/Phoenix-mini_1/initrd.gz
title E17-light kernel (hd0,1)/E17-light_1/vmlinuz livecd=E17-light_1 fromusb root=UUID=3ab0e69b-e78f-4ba1-831d-42982180af2c acpi=on vga=791 splash=silent initrd (hd0,1)/E17-light_1/initrd.gz
title Minime kernel (hd0,1)/Minime_1/vmlinuz livecd=Minime_1 fromusb root=UUID=3ab0e69b-e78f-4ba1-831d-42982180af2c acpi=on vga=791 splash=silent initrd (hd0,1)/Minime_1/initrd.gz
|
|
|
|
|
Logged
|
|
|
|
|
Was_Just19
|
 |
« Reply #8 on: February 09, 2011, 05:57:36 PM » |
|
and one ext4 partition for the LiveUSB files. Try ext3 or ext2
|
|
|
|
|
Logged
|
|
|
|
AS
Global Moderator
Hero Member
   
Offline
Posts: 4139
Have a nice ... night!
|
 |
« Reply #9 on: February 09, 2011, 06:46:51 PM » |
|
kernel (hd0,1)/LXDE-mini_1/vmlinuz livecd=LXDE-mini_1 are the images (*.sqfs) placed on the root directory of the partition ? I don't think the boot process can scan inside directories searching for UUID... just a thought, because of vmlinuz placed inside a directory. AS
|
|
|
|
|
Logged
|
|
|
|
|
Aradalf
|
 |
« Reply #10 on: February 09, 2011, 07:31:04 PM » |
|
kernel (hd0,1)/LXDE-mini_1/vmlinuz livecd=LXDE-mini_1 are the images (*.sqfs) placed on the root directory of the partition ? I don't think the boot process can scan inside directories searching for UUID... just a thought, because of vmlinuz placed inside a directory. AS Yes, all 4 images(*.sqfs) are placed in the root directory of the partition.
|
|
|
|
|
Logged
|
|
|
|
|
knome
|
 |
« Reply #11 on: February 09, 2011, 08:02:11 PM » |
|
What is shown in /boot/grub/device.map? If you're booting from sdg then I would expect the device.map entry to read (hd0) /dev/sdg
|
|
|
|
|
Logged
|
|
|
|
|
Aradalf
|
 |
« Reply #12 on: February 09, 2011, 08:13:32 PM » |
|
and one ext4 partition for the LiveUSB files. Try ext3 or ext2 I formatted the partition. as ext3, and then used PCLOS-LiveUSB on it again, and all is well. Shouldn't the PCLinuxOS-LiveUSB prevent me from installing on ext4? It does this for FAT, so it should do this for ext4, too. PCLOS-E17-light boots up without a hitch. 
|
|
|
|
|
Logged
|
|
|
|
|
T6
|
 |
« Reply #13 on: February 09, 2011, 08:32:47 PM » |
|
maybe i don't understand but ext4 is supported by linux to put file structure for the os, fat32 is form microsoft, not friendly with other os ands with file size limit at 4 gbs
|
|
|
|
|
Logged
|
"It pays to keep an open mind, but not so open your brains fall out."
Carl Sagan
|
|
|
|
Aradalf
|
 |
« Reply #14 on: February 09, 2011, 10:25:55 PM » |
|
maybe i don't understand but ext4 is supported by linux to put file structure for the os, fat32 is form microsoft, not friendly with other os ands with file size limit at 4 gbs
I'm talking about the PCLinuxOS-LiveUSB creator script. It works with ext2 and ext3, but not ext4. I was simply asking if a warning could be made that is shown when an ext4 partition is selected, similar to the warning that is shown if a fat32 partition is selected. I'm also surprised, since ext4 is what I have always used for my Linux partitions, yet it is not compatible with the PCLinuxOS-LiveUSB creator script.
|
|
|
|
|
Logged
|
|
|
|
|