similar to: "Boot error" on USB drive on some systems

I may have asked about this before, but I can't find any records of so doing in my saved mail (which includes almost everything I ever read or write): All of a sudden, I am not getting flash drives automatically mounted in CentOS 5.3 with GNOME - they are recognized by the hardware, but there seems to be a (new?) problem with the maps. Here's the tail end of dmesg: usb 1-10: new high

This past Tuesday (2/22/07) my flash drive started acting really strange - it only worked intermittently and would disappear right after an access or two. Yesterday it stopped working altogether - I couldn't even access it through my WinXP-on-VMWare. I rebooted my machine, and it worked fine after that. Is there some time limit on how long a USB flash drive will work in CentOS or is this a

I do not see /dev/sd* for this USB Jun 27 17:53:54 host.example.net kernel: : usb 4-9: new high speed USB device number 3 using xhci_hcd Jun 27 17:53:54 host.example.net kernel: : usb 4-9: New USB device found, idVendor=0781, idProduct=5567 Jun 27 17:53:54 host.example.net kernel: : usb 4-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 27 17:53:54 host.example.net kernel: : usb

Hi all- I'm trying to use a SanDisk Cruzer Micro flash drive (usb, 512MB). It has CruzerLock version 2.0 Security software in it. When I plug it in, it is recognized OK. When I open the drive, I have a file to open: CruzerLock2.exe. It has the Wine icon. But when I click on it, I get: CLZ1020: cannot locate the application in it's required location:

Greets, Ummmmm never had one b4... picked up a new 4 Gig SanDisk Cruzer Micro USB 2.0 Flash Drive to play with. Dunno if I will keep it or not. I am mostly interested in using it with CentOS of course. Ummmmm it comes with like 120 meg of non linux apps and stuff on it. Can I dust that garbage and just reformat this unit to boot with CentOS or?? Been around for a long time, know google

In message <49973.1389992217 at server1.tristatelogic.com>, I wrote: > >In message <52D90648.4010900 at mattiasschlenker.de>, >Mattias Schlenker <ms at mattiasschlenker.de> wrote: > >>I would be personally interested in the following experiment: >> >> 1. Download this LessLinux test build: >>

I have a Pentium 4 machine that does not boot from my 32GB SanDisk Cruzer. Its first partition is 24GB and FAT32, to serve as cross-platform storage. There is a second partition of 7GB in EXT2 which is bootable and contains a Linux system armed with syslinux (extlinux). This works fine booting off of recent laptops and desktops alike. This particular desktop has in its BIOS everything related to

Semi-OT? I just got a new SanDisk 8GB flash drive, and, as usual, it came with the U3 software (for Windoze) on a "CD" partition and considerably less than 8GB on the disk partition. I put it into my WinXP portable and told U3 to delete itself, but I still can't get at the old U3 part of the drive. I've tried WinXP's format command, disk management and CentOS's fdisk,

Hi, I bought a 16GB Transcend JetFlash V10 yesterday and am trying to put the fc8 livecd on it (after filling it up with all sorts of other junk :) I've only plugged it into an fc8 machine (from unopened) - nothing else. I also have a Toshiba U3 2GB USB. The OS is fc8 fully updated except the kernel (2.6.23.15-137.fc8) the livecd-iso-to-disk uses the command "syslinux -d syslinux

Folks, When I run syslinux on my Sandisk Cruzer (512MB) USB flash RAM with the "syslinux /dev/sda" , it corrupts the partition table that I had already created on my USB device. It attempts to boot but eventually fails trying to load the kernel. If I try "syslinux /dev/sda1", the USB device fail to boot at all. I would think that /dev/sda would be the correct device to use if

On 03/18/2017 01:18 AM, Ady Ady via Syslinux wrote: > Some of the things you should / could (re)test / (re)try: > > _ Verify the md5sum of the ISO image. SHA256 verified for downloaded image and for contents of USB flash drive (see below). > _ Is this particular USB device _still_ capable of booting newer > computers? Yes. > What happens if you would try _again_ to boot a

I've got a bootable USB pendrive with Syslinux 3.72, and while it usually works, there are a few computers, where I get the syslinux prompt, but it neither loads the configuration file, nor I'm able to boot anything. The only message I get on screen (apart from boot:) is "Could not find kernel image: linux". The configuration (and kernels) are in syslinux directory, but even

Hi folks. I'm not very well versed in linux (although I understand the basics, having used unix quite a bit - albeit a long time ago). I've decided to make the break from windows, and I'm trying to learn something along the way. So, I have a Dell Vostro 200, Core 2 Duo, shipped with no OS. I decided to try the Live USB approach to get started. The first step, of course, is to

Ok guys & gals here is the scenario: 1.) Host RHEL 4 U3 2.6.9-34.0.2.EL 2.) OCFS2 latest version 3.) Successfully formatted & mounted OCFS2 filesystems on 2 nodes /dev/sdb1 /u02/oradata/usdev/voting /dev/sdc1 /u02/oradata/usdev/data01 /dev/sdd1 /u02/oradata/usdev/data02 /dev/sde1 /u02/oradata/usdev/data03 4.) Downloaded & installed ASMLib 2.0 on both nodes 5.) Ran

I can't seem to find the info I'm looking for in google, hopefully someone has dealt with these sorts of issues in the past. I have a machine where my messages file keeps getting lines like: Mar 13 18:34:43 nemesis kernel: usb 2-6: reset high speed USB device number 2 using ehci_hcd Mar 13 18:34:57 nemesis kernel: usb 2-6: reset high speed USB device number 2 using ehci_hcd Mar 13

I managed to install RHEL3 onto a 1GB USB key. I had to forgo using grub to get it to but, but am now using extlinux. It actually boots, but ends up panicking. Here's the console messages that should be of interest: usb.c: registered new driver hub Loading ehci-hcd.o module ehci-hcd 00:1d.7: Intel Corp. 82801EB USB2 ehci-hcd 00:1d.7: irq 23, pci mem f882b000 usb.c: new USB bus

Here's an interesting problem, and the first partial failure I've seen when booting USB keys. I've installed a bootable Knoppix "CD" image to my USB key, and posted a writeup of my installation method here: http://knoppix.net/forum/viewtopic.php?t=25402 Up until now, I've always had one of: 100% success (it fully boots) 100% failure (BIOS fails to recognize the USB

Hi, Ady wrote: > The whole "booting business" is bigger than one specific bootloader. Too many participants at too many interfaces. > IMHO, there is more-than-enough to do about The Syslinux Project > itself Nevertheless i believe that the SYSLINUX wiki could be more tangible about what is a "normal" MS-DOS formatted disk. At least for those who seek help for

Hi, I've created a rPath appliance which boots from a USB memory stick. Today I upgraded extlinux on my rPath appliance and the memory stick froze the system during POST. After a lot of trial and errors I found out this could be fixed by wiping the USB memory stick and reproduced it by writing extlinux (3.72) to the stick. I finally found out how to fix this issue, by entering the correct

I'm currently testing a process very similar to that found here: http://wiki.centos.org/HowTos/InstallFromUSBkey And would like to update that doc with my observations once confirmed. Preliminary notes (not all relevant to that specific WikiPage - suggestions for where to put the non-kickstart info? First boot partition on USB is FAT32 and uses GRUB to chainload to the second ext2