[Solved]USB Flash Installation Media fails on booting kernel

I've been trying to install Arch on my desktop however the live USB keeps failing to load. The process of loading modules freezes at random points. I've tried acpi=off and mem=2048M, as well as enabled various debugging flags. It doesn't freeze at the same spot on different tries. I tried loading from RAM and dd'ing the drive, I'm sure the drive works because my laptop can boot off of it. I've ran out of options, can anyone help?
http://i60.tinypic.com/2rca6bp.jpg
http://i62.tinypic.com/6z9fsl.jpg
EDIT: Nevermind nomodeset worked....
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by Pentlander (2014-03-28 01:52:25)

@DSpider: Please stop FUD about archisolabel and related message. I suggest to learn how boot things really works.
Reaching such message is because some of these things fails:
1) User does not setup a filesystem label when copy ISO contents to booteable media (usb drives). In that case, if users insist in not using label, there is a boot option archisodevice=...
2) Broken/incompatible/unsupported hardware/firmware on Linux and sometimes with udev built-ins (cdrom_id, ...). -> Needed modules not loaded or loaded but not working for boot medium.
Again, archboot work in a really different way than archiso. It just work on initramfs (rootfs), so there is no need to detect and mount boot media then switch_root.
So please finish with these false alarms. I already read several of your messages in different places on this forum, repeating the same thing over and over again.
PS1: Archiso will continue using the great label-system.
PS2: memdisk is the most discourage method to boot especially in x86_32.

Similar Messages

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

[SOLVED]USB flash drive no longer showing up in /dev

My USB flash drives are no longer showing up in /dev. I also don't see them in /dev/disks/... either. Dmesg outputs:
[731969.826862] usb 1-1: new high-speed USB device number 5 using ehci_hcd
Any ideas on where to start?
Last edited by nadman10 (2012-09-26 22:12:22)

ls -l outputs:
Bus 001 Device 005: ID 0781:5530 SanDisk Corp. Cruzer
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0781 SanDisk Corp.
idProduct 0x5530 Cruzer
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x045e Microsoft Corp.
idProduct 0x0040 Wheel Mouse Optical
bcdDevice 3.00
iManufacturer 1
iProduct 3
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 72
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 3.05
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0001 1.1 root hub
bcdDevice 3.05
iManufacturer 3
iProduct 2
iSerial 1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0002 1x 2 bytes
bInterval 255

SCCM Standalone USB to Installation Media ....HELP!

Hi there, I have a standalone media on USB from our SCCM server for our machines that are no attached to our domain. They are on a workgroup. I am using Serva to deploy Windows 7 to our clients on the workgroup, however this media will not deploy in the
structure it is in. Is there any way of being able to manipulate the SCCM Media which is made for bootable deployment to each machine to an installation media format?
Thanks for your time

Hi,
Connecting the printer to a router's USB port (aka. print server) will only allow you basic print functionality , it won't provide you any scan functionality, faxing from the computer, ink levels or any operation of the HP Solution Center program.
To get full functionality you must work with the provided functionality which means USB connection directly to a single PC or Ethernet connection to a router.. therefore using an Ethernet router will be the preferred solution for you.
In order to setup the printer as you described you should connect the printer to the USB port and go to Control Panel > System. click add a printer and add it through the network.. there might be a need to enter your wireless homepage to enable the printer through the USB, there might be additional setup information in there.. that veries between different print servers and you may contact Huawei support or your ISP for any assistant within the print server configuration.
Shlomi
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

[Solved]USB Flash Drive inaccessible.

Hi there.
I have installed Arch Linux on my Sony laptop and I have configured it so that most stuff works. The only problem I'm facing now, is that my USB Flash Drive won't show up when I plug it in. I have tried restarting ehci service, but it does not solve anything. I had this problem many years ago with another computer running Linux, but I can't remember how it got solved. Connecting a USB-mouse works perfectly but not a flash drive. The drive is a FAT32 formatted Kingston.
This is my dmesg log:
[ 109.300651] usb 2-1.3: new high-speed USB device number 4 using ehci_hcd
[ 109.613294] Initializing USB Mass Storage driver...
[ 109.613459] scsi7 : usb-storage 2-1.3:1.0
[ 109.613577] usbcore: registered new interface driver usb-storage
[ 109.613579] USB Mass Storage support registered.
[ 110.614456] scsi 7:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 2
[ 110.616674] sd 7:0:0:0: [sdc] 8237056 512-byte logical blocks: (4.21 GB/3.92 GiB)
[ 110.617821] sd 7:0:0:0: [sdc] Write Protect is off
[ 110.617835] sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 110.618550] sd 7:0:0:0: [sdc] No Caching mode page present
[ 110.618561] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 110.621899] sd 7:0:0:0: [sdc] No Caching mode page present
[ 110.621908] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 110.787723] sdc: sdc1
[ 110.880634] sd 7:0:0:0: [sdc] No Caching mode page present
[ 110.880647] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 110.880655] sd 7:0:0:0: [sdc] Attached SCSI removable disk
Running openbox with PCManFM. Any clues how to solve this?
Last edited by light (2013-03-17 21:26:26)

s1ln7m4s7r wrote:
For what i can see from the log there is no problem.
Have you tried to manually mount it? To see if it is a PCManFM issue. Also, have you checked this:
https://wiki.archlinux.org/index.php/PC … ge_devices
Hi.
I tried installing gvfs, apparently I uninstalled it for some reason before. But it did not help mounting the flash drive. So I tried mounting it manually and it worked (Yaay!). But it complained that my flash drive was not mentioned in fstab. So I looked in fstab and the only ones listed is my root partion "/" and "/home". So how do I add USB mounting to fstab? I'm a little bit confused.
And one off-topic question: Shouldn't my "/var" partion also be mentioned in fstab?
Thanks for helping me
Edit: This is how fstab looks right now
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2 LABEL=/
UUID=ed07bdb6-61c6-4cc7-b98d-122a869046f1 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4 LABEL=/home
UUID=7448100b-682b-430f-9e59-327ce6f9f22c /home ext4 rw,relatime,data=ordered 0 2
Last edited by light (2013-03-17 20:54:38)

Installation CD Fails To Boot

Hello everybody!
Well long story short, I had arch linux installed for a little over a year. I since then have migrated distros twice for shits and giggles, though, it seems I am not able to re-install with the installation image. It boots from the USB/CD just fine, but then I select the x86_64 option, and after it finishes what it's doing on the bottom of the screen (sorry, not extremely well versed in this and going off of memory) my computer shuts off and reboots back into the OS installed (which at the time was Ubuntu 14.04). I since wiped that computer's hard drive to see if that would fix any issues, though so far it hasn't.
I've had arch installed on that very computer multiple times, and to my knowledge I haven't changed anything about it. So I just wanted to ask what would be causing this, and if you kind gents could help me fix it.
Thank you in advance!

Hi,
TheAmazingGymShorts wrote:I since wiped that computer's hard drive to see if that would fix any issues
First the thing I don't get is why you wiped your hard drive instead of re-doing the bootable USB. Sometimes (already happend to me twice) dd s**** his pants and USB doesn't boot properly (a lot less than UnetBootin that just can't boot an Arch). However if you had already successfuly installed Arch on that very laptop of yours a couple time means you probably shouldn't have wiped the HDD and do the following(explained here).
Restore the USB drive:
dd count=1 bs=512 if=/dev/zero of=/dev/sdx && sync
Create a new partition table using cfdisk:
cfdisk /dev/sdx
Format the USB drive:
mkfs.vfat -F32 /dev/sdx1
or for ext4
mkfs.ext4 /dev/sdx1
and if you want to rename it (absolutely not necessary)
dosfslabel /dev/sdx1 <your_usb_name>
Then you can then redo the USB with
dd bs=4 if=/path/to/archlinux of=/dev/sdx && sync

[SOLVED] HP Envy 14 Installation Media Won't Boot Beyond Grub

I just got an HP Envy 14. I've heard of some minor Linux issues with it, but all well past the installation phase.
As for me, I can't get the installation CD/USB to load beyond GRUB. I select the first option - to run the OS live from the USB/CD - and I see the first few lines of the correct output (decompressing kernel, etc.). After that, it hits a blank (black) screen and hangs. Five or ten minutes later - nothing, still black screen.
Has anybody else had this issue - with the Envy or any other computer? I've installed Arch on a few other computers before and never run into this problem.
Last edited by chimeracoder (2011-08-28 18:03:49)

This may be set a record for the fastest/most mundane solution ever! It turns out that the screen turns off after GRUB loads Arch (this isn't just an Arch issue - I tried it with a Xubuntu live CD I had lying around as well). Anyway, if anybody else has this problem as well, just turn the brightness back on once you're past GRUB and you should be good to go.

[solved] Cannot complete install, grub fails to boot the new install

I'm using the 2009.08 USB image.
I've tried this 2 weeks ago, tried it again today, same result. (I'm on Win7 meanwhile).
I'm installing arch, everything goes fine.
I've tried 2 setups:
a)
100GB ext4 /
12GB swap
(no separate /boot, should work)
b)
100MB ext3 /boot
100GB ext4 /
12GB swap
Neither a) or b) will boot.
When the newly installed grub boots, I get a error saying:
filesystem type unknown, partition type 0x7
I get this for the ext3, ext4, and windows partitions.
I get it for both a) and b) setups.
I have doublechecked the menu.lst file. I've even created another entry setting root=/dev/sdb1 (as opposed to the default /dev/disks/by-uuid/..).
I should mention, I have two disks, the first (sda) is currently with a Win7 installation, the 2nd (sdb) is the one I'm trying to install Arch again (and failing).
After the reboot, I've tried booting into the livecd again and manually trying to mount /dev/sdb1 /mnt, it works.
Why isn't my grub boothing from ext{3,4}?
Last edited by Frantic (2009-11-05 18:35:15)

Rede wrote:
I was getting that error but after re-installing grub and making some changes to the menu.lst file it was fixed.
I was able to at one stage boot into arch but it gave problems with the root. Now it just seems to freeze while trying to load grub.
I am currently trying yet another install of grub. I have been noticing though that my menu.lst file has been rolling back or not updating when I chroot back into my install after changing it earlier.
Try mounting your /boot partition under /mnt/boot.

I can't install Adobe Flash -installation keeps failing

I run Windows Vista, and have been using Firefox as my browser (current version). In May some time Flash stopped working on Firefox. It works fine on IE8. I have uninstalled Flash and reinstalled it - successful on IE, and uninstalled Firefox and reinstalled it, then tried to install the Flash plugin, all to no avail. When I try to install it manually nothing happens. Is something changed on a security setting that is preventing this? My cookies/pop-ups allow adobe.com on Firefox.
Any help would really be appreciated.

Thanks for your reply. I am the admin account in Vista. I always log in as admin. Is there a setting within admin preventing me from loading the plugin? If so, I have been able to load other plugins without a problem.
I can't install the plugin with Firefox closed. It tries to load on the browser. For example, I get the message that a plugin needs to be installed from the top of my browser window, I click on it, it takes me to the Adobe license page, I accept, and it takes me to a window where the plugin is being loaded. Then a window comes up that says "Completing the Plug-in Finder Service" which says "No Plug-ins were installed, Adobe Flash Player 10.3.181, Failed" I get the Manual Install button, but when use that to go to the Adobe page, and try to install manually, nothing happens - no acceptance of license, nothing.
I have another computer - newer - with Windows 7 - and Flash loaded and runs fine on my Firefox browser on it.
Any other ideas?

Usb flash drive disables Airport on boot

Apple Gurus,
I have found that plugging a flash drive into my system at boot time disables the airport on the machine.
Have you ever heard of such a thing and is there a work around?
Many thanks.
-Chris

I applied the 10.4.10 patch, and it will now boot with Airport enabled.
Thanks,
Chris

Additional Instructions for Creating USB Installation Media

Greeting Everyone,
I have been trying to install archlinux on my Acer c720 chromebook. The instructions have been posted on one of the forums and I have been following them and ran into a bit of a problem. For some mysterious reason using Syslinux as the bootloader (I think I got that right) puts the C720 into reboot immediately. The forums indicate that I should use GRUB instead of Syslinux. Great! That is exactly what I want to do, and here is the problem:
The instructions for creating the USB Flash Installation Media give step by step instructions for getting archlinux.iso and Syslinux on to the USB memory stick - which I followed and succeeded- but no instructions on how to put GRUB on there instead of Syslinux.
Could someone give me instructions on how to do that.
I am following the "Manual Formatting" --- "In Windows" section of the wiki titled "USB Flash Installation Media."
Just so everyone knows this is my first venture into linux world and away from point and click windows world.....

Steef435 wrote:
Those instructions are about the installation(about what you choose to install on your harddisk). So they aren't important yet if you haven't managed to boot up the usb drive. What three images did you try? You should get the image from here:
https://www.archlinux.org/download/
Did you try booting the drive on other machines and how did that go? Did you go through all the instructions described in the wiki(enabling developer mode and enabling legacy boot) and did you get to the boot menu?
Were you able to select the usb drive in the boot menu?
On a side-note, I don't have a Chromebook so I'm not able to confirm the instructions on how to enable developer mode etc.
Yes I used the following images from archlinux.org:
archlinux-2013.10.01-dual.iso
archlinux-2014.01.05-dual.iso
and the third was from a random selection from the drop down menu in LiLi USB creator.
Yes I have followed the instructions from the installation wiki and was able to get the developer mode and to the boot menu on the c720 and able to select USB to boot from.
As I mentioned earlier I had success using the method for creating a USB Installation in the wiki (under "Using manual formatting", "In Windows" https://wiki.archlinux.org/index.php/US … tion_Media ) I was able to get the archlinux splash screen and it tries to install but resets. And I figured out that this happens because following the instructions I end up with archlinux and Syslinux on the USB and I need arclinux and GRUB.
Hence my request for additional instructions for getting archlinux and GRUB onto a USB for installation.
I will try the USB installation created using LiLi on a different computer - it is much older though and I am not sure it has enough memory for it.

Can't boot from windows 7 usb installation media

When trying to boot from windows 7 usb installation media no efi boot option availiable. Using "boot from efi file" option whith each and every .efi file on installation media results in a message saying "The selected boot device failed. Press <Enter> to Continue".
USB installation media created using original windows 7 iso image and couple diskpart commands(resulting in clean flash storage with a single active primary partition) plus simple copying of the iso image's contents on usb flash.
Enabling/Disabling SecureBoot doesn't have any impact whatsoever.
Installation boots from aforementioned media successfully when CSM enabled, though i would really prefer installing Windows 7 in uefi mode. Which microsoft claims Windows 7 supports.
Any help or suggestions would be much appreciated. Thanks in advance.
PS: my disappointment in this particular HP notebook is unspeakable. Aside from issue of the current topic, It keeps defaulting to windows boot manager when dual-booting windows & linux no matter what i do, and windows 8.1 Pro is constantly BSODing whenever i try to run fullscreen games on high-performance GPU whith every graphics driver i could possibly install (including both hp's own and amd's). Found silly workarounds for both of these issues, however still hate HP treating it's customers that way.

Booting from USB 2.0 port or DVD with SecureBoot disabled gets me to a screen saying "starting windows", just before the actual setup begins and then system simply hangs. Still unable to install. Thanks for your suggestion though.

NB100 - How can I reinstall OS from USB flash drive

My TOSHIBA NB 100 notebook does not have CD-DVD drive.
OS is Windows XP Home SP2.
OS is not booting.
Notebook won't start at all so I cannot run any sort of test when i turn it on.
The we apologize screen come on it says run safe mode, safe mode networking, safe mode comand prompt or start windows normally. But no matter which I chose it won't start it only goes to Windows and seems like its starting but then shows the blue Windows screen & stays there.
So I want to reload Windows from my USB flash drive.
The BIOS boot sequence is HDD - FDD - FD - CD - USB Memory.
What are the steps for loading Windows from USB flash drive?
If this does not work then I want to connect another laptop with Windows CD in its CD-DVD drive to the Notebook.
Will this work? Will the Notebook use the Windows CD in the laptop drive to load the OS?
How to do this connection?

Hi
Usually you would need an external USB CD/DVD drive in order to boot from the Windows XP disk or Toshiba recovery disk.
But there is a method which allows you to install the Win XP using 2GB USB flash drive.
This is possible because the BIOS of NB100 support the booting from USB memory stick.
Pease check this internet page:
+Installing Windows XP Using A USB Flash Drive+
http://www.pctipsbox.com/installing-windows-xp-using-a-usb-flash-drive/
Hope it could be helpful.

[SOLVED] USB Installation Media Boot Problems

Hi all,
I'm having trouble creating a live USB stick that my new (to me) HP Elitebook
2730p laptop can boot successfully. Here is what I've tried so far:
1. dd with the latest stable Arch installation media
In other words:
# dd if=/path/to/archlinux*.iso of=/dev/sdb
Result: I can boot with the USB stick on my old Dell laptop (which is running
Arch) without issue, but can't with the new HP. The BIOS will freeze if the USB
stick is inserted, and will only unfreeze after I remove it.
2. dd with a recent Arch installation media snapshot
The snapshot is ``archlinux-2012.06.05_04-00-01-core-x86_64.iso''. I
install the image to the USB stick with the same dd method above,
and I get the same behavior: works fine on the old Dell, but freezes the BIOS of
the new HP.
3. dd with an old lubuntu iso
This time, I used an old lubuntu iso
(lubuntu-11.10-desktop-amd64.iso) with dd. This method
worked without a problem -- both my old Dell and my new HP would boot it without
complaint.
3. unetbootin with the latest stable Arch installation media
Creating the USB stick with unetbootin allows me to boot the stick with the new
HP, but the boot fails to the ramfs prompt after ``Waiting 30 seconds for device
/dev/disk/by-label/ ...'' (notice how there's nothing after ``by-label/'').
Adding ``vmalloc=448M'' to the end of the unetbootin boot entry makes no
difference.
4. Image Writer for Windows
The ``USB Installation Media'' wiki page suggests using ``Image Writer for
Windows'' to create a bootable USB stick. I tried this method using Windows 7
Professional, and the result was the same as attempts 1 and 2: the USB stick
freezes the HP's BIOS.
Other notes
I've checked the md5sums of all the isos I've tried
I've updated the BIOS on the HP laptop
I've used the same USB stick for each of the above situations
The new HP laptop does not have an optical drive, and I don't own an
external one
In attempts 1, 2, and 4, I noticed that cfdisk shows that the partition
that contains the installation files has both the ``Bootable'' and ``NC'' flags
set. The cfdisk man page says that the latter flag stands for ``Not Compatible
with DOS or OS/2''. I can actually remove this flag by using the ``Maximize''
option in cfdisk, which actually makes the USB stick bootable by the HP
computer's BIOS, but the boot eventually fails to the ``ramfs prompt
thingy'' after saying ``ERROR: '/dev/disk/by-label/ARCH_201108' found, but the
filesystem type is unknown''
In attempt 3 (the lubuntu one), I noticed that cfdisk shows a bit of free
space in front of the partition that contains the lubuntu files. The ``NC'' flag
is not present when I run cdisk.
My current theory is this: I believe my new HP's BIOS is unhappy with the
``isohybrid-nature'' of the Arch installation media. Is there any way I can
confirm this, or obtain ``non-isohybrid'' Arch media?
As you might imagine, this has been pretty frustrating. Any help would be
greatly appreciated!
Daniel
Last edited by bebeababa (2012-06-10 15:04:43)

bebeababa wrote:
DSpider wrote:
Adding ``vmalloc=448M'' to the end of the unetbootin boot entry makes no difference.
Duh. That's for booting it from RAM (with MEMDISK) in case it doesn't map the entire file, which for some reason it didn't for the i686 iso on my computer. I probably should've specified it when I wrote the article. I'll add it tomorrow morning.
Speaking of which, have you tried it?
https://wiki.archlinux.org/index.php/US … O_from_RAM
Because you only seem to be using dd ("Image Writer" is the same) and Unetbootin (which had various problems since forever). The correct syntax for dd is:
$ sudo dd if=archlinux.iso of=/dev/sd[x]
Warning: Make sure to use /dev/sdx and NOT /dev/sdx1. This is a very common error!
https://wiki.archlinux.org/index.php/US … _USB_drive
Haven't tried the ``Boot the entire ISO from RAM'' method yet. I'll give that a shot next.
The ``Boot the entire ISO from RAM'' method worked like a charm! Thanks,
DSpider!
Marking thread [SOLVED].

Boot Installation media from USB flash/Pen Drive?

Hi there,
The hardrive on my X60 died. Died so badly that even Resue and Recovery wouldn't start yet alone Windows (even in safe mode).
I have a new hard drive and installation media en route from Lenovo (laptop was under warranty)
The problem is that the installation media is on CD/DVD and my laptop does not have an optical drive.
So my questions are:
1. Can the installation media be installed from a USB Pen/Flash drive? (the BIOS does support USB booting)
2. Does anyone have experience of this or instructions?
On a side note I find it slightly irritating that even under warranty Lenovo won't supply me software/hardware that will return my laptop to its original state without the user, me, potentially having to buy an external optical drive. The warranty support chap said "you'll just need to buy an external USB optical drive" - *sighs*
Cheers
Lawrence

Tnx 4 ur reply RX-8.
I bought the lappie used. It had BIOS ver. 103 when I bought it, so I upgraded to ver. 111 and it kept on booting from pen drives just fine.
A few days after I bought it, the internal HDD failed with S.M.A.R.T. ID 5, something about reallocated sectors count. I got an exact replacement for the dead HDD. When I installed it, I unplugged the lappie's battery, then plugged the battery back in before I buttoned it all up. I think THAT was the start of my USB flash pen drive boot problem.
The new HDD is fine. It passes the HGST Drive Fitness Test with long SMART test, which takes between 2 and 3 hours.
I tried the EC update. Inside the zip file was a TXT file with a link to an MSI page that has a PDF file on how to do the EC update. I had that PDF open on another machine when I did the EC update so I could follow the instructions exactly.
After an F9 on the UEFI screen to restore defaults and an F10 to save the UEFI config, I rebooted and everything seemed OK. I then used a pin to force a reset. For the second time, I unplugged the lappie and waited a few minutes for the EC memory to clear.
I still have the same problem. I can't boot from a USB flash pen drive.
I'm enclosing shots of my USB config with XHCI enabled and disabled. I tried to boot from a pen drive with both XHCI settings. No joy. Will I ever be able to boot from a USB flash pen drive again?
I should also mention that I have a portable HDD with a USB 3 interface that boots just fine on other machines but won't boot on the GS60 Ghost. The LED on the portable HDD comes on and the lappie screen just sits there with a blinking underscore cursor.

[Solved]USB Flash Installation Media fails on booting kernel

Similar Messages

Maybe you are looking for