Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: Boot problem on nec bootable usb 3 port

  1. #1
    Join Date
    Oct 2010
    Location
    Geneva/Switzerland
    Posts
    57

    Default Boot problem on nec bootable usb 3 port

    Hello,

    I did an installation suse 11.4 on a key usb3, connected to a controller nec usb 3 natively bootable on the motherboard of my machine.

    The installation went fine but on reboot, I have the following message:

    "Waiting for device / dev/disk/by-id/usb-innostor_xxx-0 :0-part2? (Y / N)"

    when I said yes and he seeks answers:

    "not found - exiting to / bin / sh"

    "sh: can not set terminal process group (-1): Inappropriate ioctl for device"

    "sh: no job control in this shell"

    If I plug this install on a USB 2 port intel it works but is too slow!

    Thank you for your help.

  2. #2
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Smile Re: Boot problem on nec bootable usb 3 port

    Hello,

    I did an installation suse 11.4 on a key usb3, connected to a controller nec usb 3 natively bootable on the motherboard of my machine.

    The installation went fine but on reboot, I have the following message:

    "Waiting for device / dev/disk/by-id/usb-innostor_xxx-0 :0-part2? (Y / N)"

    when I said yes and he seeks answers:

    "not found - exiting to / bin / sh"

    "sh: can not set terminal process group (-1): Inappropriate ioctl for device"

    "sh: no job control in this shell"

    If I plug this install on a USB 2 port intel it works but is too slow!

    Thank you for your help.
    So far I have not run into an Intel or AMD chipset that natively supports USB 3.0 and thus USB 3.0 drives can not be selected as a boot drive in BIOS setup. In the event you could select a USB 3.0 external hard drive to boot from and Grub does boot, but then the USB 3.0 drive fails to be found by the kernel, then I think you need to rebuild the kernel initrd image and add the USB 3.0 module. I thought it was called xhcd, but I can't remember the name this morning. Also, errors can occur with the grub boot loader in the /boot/grub/device.map file not properly reflect the external drive, perhaps sdb, as being hd0 in the device.map file and in the menu.lst file. So, more than one problem might exist.

    Thank You,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  3. #3
    Join Date
    Oct 2010
    Location
    Geneva/Switzerland
    Posts
    57

    Default Re: Boot problem on nec bootable usb 3 port

    I have a sony vaio new machine that can boot natively on an embedded controller USB3 NEC.

    I am newbie linux I'm not able to recompile the kernel, the other driver usb 3 is supposed to be already present in 11.4.

    Thank you for your help

  4. #4
    Join Date
    Oct 2010
    Location
    Geneva/Switzerland
    Posts
    57

    Default Re: Boot problem on nec bootable usb 3 port

    I just tried to install suse 11.4 with a "swap" and a directory "/" only, this does not work either.

    Error messages are the same as previously.

  5. #5
    Join Date
    Oct 2010
    Location
    Geneva/Switzerland
    Posts
    57

    Default Re: Boot problem on nec bootable usb 3 port

    The error occurs shortly after grub has launched the system.

  6. #6
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Smile Re: Boot problem on nec bootable usb 3 port

    So, I have looked up just what the USB 3 module is called and it is called xhci-hcd, but I can't say that this module is not automatically loaded. Way back when, at around version 10.0 of openSUSE, no USB drivers were loaded automatically and all had to be added to Initrd module if you intended on booting from a USB hard drive, but that is no longer true with the present openSUSE version, but again, I am not sure about USB 3.0 support. The basic issues were/are:

    1. Can you really boot from a USB 3.0 device by BIOS setup?
    2. Does the openSUSE Initrd Image really contain the xhci-hcd module, able to use/boot from UISB 3.0 drives?
    3. Is it possible your Grub Menu.lst file is just not setup properly to boot from an external hard drive?
    4. Is it possible you just don't have the correct partition setup to work with openSUSE?

    To over come an Intrd image file that might be missing the xhci-hcd module, you must download a LiveCD boot disk you can boot from to fix your openSUSE installation AFTER it has been installed. So, to make sure you understand how to install openSUSE onto an External Hard drive, here is basic partition setup information you need to know:

    Each hard drive can have up to four PRIMARY partitions, any of which could be marked active and bootable. No matter what you might hear, only one of the first four primary partitions can be booted from. That means you can boot from Primary partitions 1, 2, 3 or 4 and that is all. In order to boot openSUSE, you must load openSUSE and the grub boot loader into one of the first four partitions. Or, your second choice is to load the grub boot loader into the MBR (Master Boot Record) at the start of the disk. The MBR can be blank, like a new disk, it can contain a Windows partition booting code or generic booting code to boot the active partition 1, 2, 3, or 4. Or, as stated before, it can contain the grub boot loader. Why load grub into the MBR then? You do this so that you can "boot" openSUSE from a logical partition, numbered 5 or higher, which is not normally possible. In order to have more than four partitions, one of them (and only one can be assigned as extended) must be a extended partition. It is called an Extended Primary Partition, a container partition, it can be any one of the first four and it can contain one or more logical partitions within. Anytime you see partition numbers 5, 6 or higher for instance, they can only occur inside of the one and only Extended Primary partition you could have.

    What does openSUSE want as far as partitions? It needs at minimum a SWAP partition and a "/" partition where all of your software is loaded. Further, it is recommended you create a separate /home partition, which makes it easier to upgrade or reload openSUSE without losing all of your settings. So, that is three more partitions you must add to what you have now. What must you do to load and boot openSUSE from an external hard drive? Number one, you must be able to select your external hard drive as the boot drive in your BIOS setup. Number two, you need to make sure that the external hard drive, perhaps /dev/sdb, is listed as the first hard drive in your grub device.map file and listed as drive hd0. I always suggest that you do not load grub into the MBR, but rather into the openSUSE "/" root primary partition which means a primary number of 1, 2, 3 or 4. If number one is used, then that will be out. You will mark the openSUSE partition as active for booting and finally you must load generic booting code into the MBR so that it will boot the openSUSE partition. I suggest a partition like this:

    0. /dev/sdb, Load MBR with generic booting code
    1. /dev/sdb1, Primary NTFS Partition for Windows
    2. /dev/sdb2, Primary SWAP (4 GB)
    3. /dev/sdb3, Primary EXT4 "/" openSUSE Partition Marked Active for booting (80-120 GB)
    4. /dev/sdb4, Primary EXT4 "/home" Your main home directory (Rest of the disk)

    Now, if you feel you have install oipenSUSE properly to work with an External Hard drive, here is what you might do to add the xhci-hcd module to openSUSE, should it be missing:

    1. Boot from a LiveCD AFTER you have installed openSUSE properly, but where it does not boot into openSUSE properly.
    2. Open Up a terminal session and execute the following commands:

    mkdir /mnt/sysimage
    mount /dev/sdXY /mnt/sysimage
    chroot /mnt/sysimage

    NOTE: X=disk name as in a, b, c or d AND Y=1, 2, 3 or 4 as to partition number. Ex:sdb1 where you have installed the main or root openSUSE partition called /

    3. Use VI or other text editor (Look up the VI editor command first) and edit the file /etc/sysconfig/kernel
    5. In the text file called kernel look for the line that starts with INITRD_MODULES=" and add the name xhci-hcd to the line and save the file. For instances, here is what my line says with this option added:

    INITRD_MODULES="xhci-hcd pata_jmicron ata_generic thermal processor fan"

    Your line will likely be different than mine.

    6. Issue the following terminal commands after you have edited the above text file called kernel located in the folder /etc/sysconfig/

    mount -tproc none /proc
    mkinitrd

    This should create a new image in the /boot folder that might be named: initrd-2.6.37.1-1.2-desktop and is being loaded in your /boot/grub/menu.lst file.

    Thank You,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  7. #7
    Join Date
    Oct 2010
    Location
    Geneva/Switzerland
    Posts
    57

    Default Re: Boot problem on nec bootable usb 3 port

    Thank you for your advice! It works! It was enough to effect change in the file / etc / sysconfig / kernel and then do a mkinitrd I am happy thank you again.

    To answer the questions:

    1 yes I boot on usb 3, natively, on a Sony Vaio with nec usb3 chip integrated on the motherboard (VPCSB series)
    2 the 11.4 runs natively usb3

    I use a USB key 3 Sharkoon Flexi-Drive Extreme USB 3.0 Duo - 16 GB to 130 Mb w / r it's wonderful !

  8. #8
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Smile Re: Boot problem on nec bootable usb 3 port

    Thank you for your advice! It works! It was enough to effect change in the file / etc / sysconfig / kernel and then do a mkinitrd I am happy thank you again.

    To answer the questions:

    1 yes I boot on usb 3, natively, on a Sony Vaio with nec usb3 chip integrated on the motherboard (VPCSB series)
    2 the 11.4 runs natively usb3

    I use a USB key 3 Sharkoon Flexi-Drive Extreme USB 3.0 Duo - 16 GB to 130 Mb w / r it's wonderful !
    Yeah! I am happy to hear that this information helped. It does answer several questions about using USB3 to boot openSUSE. So, what more can you tell me about your computer? Can you tell me the model number so I can look up the chipset, cpu and BIOS information on this computer?

    Second, when and if more PC's come up with boot support for USB 3 external hard drives, more people will have the same issue as you did and required the manual modification of the initrd image to get it to work. That means that you actually helped me out with some very important information to know about USB 3 support in openSUSE, so thank you very much!

    Thank You,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  9. #9
    Join Date
    Oct 2010
    Location
    Geneva/Switzerland
    Posts
    57

    Default Re: Boot problem on nec bootable usb 3 port

    Hello,

    My machine is a Sony Vaio "VPCSB1Z9E / B" bios "R1030H4", Intel Core 2.3 GHz i5, chipset Standy Bridge, HM65, NEC USB3.

    Two other recent models of Vaio machines out on the market and equipped with USB3 NEC, I tested also the ability to boot on usb3.

    It is I who thank you very much, without you, progress would not exist in the same way ...

    I would love to buy you a beer to thank you, unfortunately it does not yet exist for download

    Thank you again and good continuations.

  10. #10
    Join Date
    Oct 2010
    Location
    Geneva/Switzerland
    Posts
    57

    Default Re: Boot problem on nec bootable usb 3 port

    Hello

    I have a new question to ask. I added a usb 3 hub "Icy Box"on my computer. If I boot on my usb 3 key (Linux) connected to this hub, I am limited to transfer rates of 30 Mb, I'm at full speed without this hub on linux, and at full speed in this hub on windows ?! Have you an idea of the reason for this limitation?

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •