[SOLVED] k3b does not detect optical drive

Hello,
I am running Arch Linux x86_64 with recent updates. I have k3b 2.0.3 and when I launch it I get message that it does not detect my optical drive, and I need hal daemon. I checked, udev is running, node in dev /dev/sr0 has root.optical, my user is in optical group. How do I fix this? I want to burn BluRay disk, maybe k3b even does not support it? And is there a better tool for optical discs than k3b? I use KDE 4 so Qt tool would be nice
Last edited by adomas (2015-01-09 17:34:05)

[EDIT] I think problem is solved. Not sure how, but after reboot it works now
Thank you for you reply, Lone_Wolf
Permissions seems to be ok:
[adomas@voidbox ~]$ ls -l /dev/sr0
brw-rw---- 1 root optical 11, 0 Jan 9 21:18 /dev/sr0
[adomas@voidbox ~]$
And about dependencies I think I have what I need:
[root@voidbox adomas]# pacman -Qi k3b
Name : k3b
Version : 1:2.0.3a-1
Description : Feature-rich and easy to handle CD burning application
Architecture : x86_64
URL : http://sourceforge.net/projects/k3b/
Licenses : GPL
Groups : None
Provides : None
Depends On : kdebase-runtime libkcddb libsamplerate libmad ffmpeg taglib libmpcdec libdvdread cdrkit
libxft
Optional Deps : dvd+rw-tools: for dvd burning support [installed]
vcdimager: for vcd burning support
transcode: for advanced mpeg conversion support
emovix: for bootable multimedia cd/dvd support
cdrdao: for disk-at-once (DAO) mode support [installed]
cdparanoia: for cd ripping support
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 33.81 MiB
Packager : Eric Belanger <[email protected]>
Build Date : Thu 06 Nov 2014 05:21:31 AM EET
Install Date : Wed 07 Jan 2015 07:28:57 PM EET
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
[root@voidbox adomas]#
What else can be a problem? By the way may optical drive is external, connected via USB, if it makes any difference.
Last edited by adomas (2015-01-09 17:33:50)

Similar Messages

  • Logic Board Does Not Detect Hard Drive???

    Problem on startup shows "Folder with (?) Mark on it". Tried to use Disk Utility but it does not detect. Replaced drive and still nothing. Use the drive as external and it boots normal. It looks like it's something else. I have order a new cable connection that goes from the logic board to the hard drive, as it's cheaper to obtain than a logic board, but lets just say that it wasnt that and there is a problem with the logic board, can I buy a "9.5 mm SATA Optical Bay SATA Hard Drive Enclosure" to place the hard drive and boot from it? When I went into Disk Utility it did detected the DVD drive, so I know that portion of the logic board works fine. I don't use or need the DVD drive, and wondering if I can do this, it cost less than buying a logic board.
    Please let me know if this is possible, Thanks in advance.

    Well logic board seems faulty from the connecting point of the hard drive but not from the optical drive. Optical drive is detected by the Disk Utility, but not the hard drive, and thats why I was thinking of using the optical bay to run the machine.

  • WVC210 Device manger does not detect camera driver

    Hi, Iam doing a java application project which captures a vedio from linksys wvc210 network camera, the problem is the device manager does not detect the camera as one of the imaging devices or as any, and so the jmf registry editor does not also detect the camera in which i am stuck on how to make java detect it and work on it which is impossible without being detected with the jmf registry so i need windows first to detect it at the device manager which will lead jmf registry editor to also detect it.
    note that: the camera installation worked properly and i can access it normally. by the way iam using windows vista.
    any help please...

    First of all, thanks for ur reply, i will state the problem again: iam doing a java api application using the java media framework (JMF), the application goal is to capture a vedio from the ip camera, the application is done and works with my web cam which is detected by the java capture device manager, on the other hand the capture device manager does not detect the ip camera as one of the captured device in which i can't run my application on it. So the easiet way is to make windows detect it as one of the devices at the device manager so java capture device manager can detect it and my application will work immediatly. any suggestions ? 

  • IMac does not recognize optical drive

    I have an iMac that I purchased. I thought that the optical drive was bad, so I replaced it. But the new drive is having the same problems as the old. It will open when you press the eject button on the keyboard, so it is obviously communicating with the computer. But it will not mount the disk. I am trying to reinstall OS X, and when I try to boot from a CD or hold down option and try to select a startup drive, the optical drive does not read the disk. It just spits the disk out and starts up like normal. Any ideas of what I can do to fix this? Thanks!

    I have this same problem when I start k3b.
    I have installed cdrdao, cdrtools and dvd+rw-tools as dependencies for k3b, I have created burning group and set that settings on k3b "modify permissions", but something is not working as it's supposed, because any device is found:
    ll /dev | grep sr0
    or
    ll /dev | grep cdrom
    and no results, so my assumption its that some daemon that should be listening for changes on devices is not working... I assume that could be something with HAL daemon ( that I already have tried and no success) or other...
    Screenshots:
    https://dl.dropboxusercontent.com/u/141 … dialog.png
    https://dl.dropboxusercontent.com/u/141 … ttings.png
    I have read that the problem could be related to KDE (that's my desktop environment) - https://bugs.archlinux.org/task/24643
    PS: my optical DVD drive is external
    EDIT: I saw that this post is one year old, I'm trying to delete this post, but I can't!
    Last edited by poliveira (2014-01-19 20:13:04)

  • [SOLVED]mpd does not detect the music directory

    I recently installed mpd with the gmpc gui, set my "music_directory" in /etc/mpd.conf to the location of all of my music (which contains lots of other folders and subfolders), but there's no listing of the audio files in the database in gmpc.
    Here's the /etc/mpd.conf if that helps:
    # An example configuration file for MPD
    # See the mpd.conf man page for a more detailed description of each parameter.
    # Files and directories #######################################################
    # This setting controls the top directory which MPD will search to discover the
    # available audio files and add them to the daemon's online database. This
    # setting defaults to the XDG directory, otherwise the music directory will be
    # be disabled and audio files will only be accepted over ipc socket (using
    # file:// protocol) or streaming files over an accepted protocol.
    music_directory "/var/lib/mpd/music"
    # This setting sets the MPD internal playlist directory. The purpose of this
    # directory is storage for playlists created by MPD. The server will use
    # playlist files not created by the server but only if they are in the MPD
    # format. This setting defaults to playlist saving being disabled.
    playlist_directory "/var/lib/mpd/playlists"
    # This setting sets the location of the MPD database. This file is used to
    # load the database at server start up and store the database while the
    # server is not up. This setting defaults to disabled which will allow
    # MPD to accept files over ipc socket (using file:// protocol) or streaming
    # files over an accepted protocol.
    db_file "/var/lib/mpd/mpd.db"
    # These settings are the locations for the daemon log files for the daemon.
    # These logs are great for troubleshooting, depending on your log_level
    # settings.
    # The special value "syslog" makes MPD use the local syslog daemon. This
    # setting defaults to logging to syslog, otherwise logging is disabled.
    log_file "/var/log/mpd/mpd.log"
    # This setting sets the location of the file which stores the process ID
    # for use of mpd --kill and some init scripts. This setting is disabled by
    # default and the pid file will not be stored.
    pid_file "/var/run/mpd/mpd.pid"
    # This setting sets the location of the file which contains information about
    # most variables to get MPD back into the same general shape it was in before
    # it was brought down. This setting is disabled by default and the server
    # state will be reset on server start up.
    state_file "/var/lib/mpd/mpdstate"
    # The location of the sticker database. This is a database which
    # manages dynamic information attached to songs.
    #sticker_file "~/.mpd/sticker.sql"
    # General music daemon options ################################################
    # This setting specifies the user that MPD will run as. MPD should never run as
    # root and you may use this setting to make MPD change its user ID after
    # initialization. This setting is disabled by default and MPD is run as the
    # current user.
    user "mpd"
    # This setting specifies the group that MPD will run as. If not specified
    # primary group of user specified with "user" setting will be used (if set).
    # This is useful if MPD needs to be a member of group such as "audio" to
    # have permission to use sound card.
    #group "nogroup"
    # This setting sets the address for the daemon to listen on. Careful attention
    # should be paid if this is assigned to anything other then the default, any.
    # This setting can deny access to control of the daemon.
    # For network
    #bind_to_address "any"
    # And for Unix Socket
    #bind_to_address "~/.mpd/socket"
    # This setting is the TCP port that is desired for the daemon to get assigned
    # to.
    #port "6600"
    # This setting controls the type of information which is logged. Available
    # setting arguments are "default", "secure" or "verbose". The "verbose" setting
    # argument is recommended for troubleshooting, though can quickly stretch
    # available resources on limited hardware storage.
    #log_level "default"
    # If you have a problem with your MP3s ending abruptly it is recommended that
    # you set this argument to "no" to attempt to fix the problem. If this solves
    # the problem, it is highly recommended to fix the MP3 files with vbrfix
    # (available from <http://www.willwap.co.uk/Programs/vbrfix.php>), at which
    # point gapless MP3 playback can be enabled.
    #gapless_mp3_playback "yes"
    # This setting enables MPD to create playlists in a format usable by other
    # music players.
    #save_absolute_paths_in_playlists "no"
    # This setting defines a list of tag types that will be extracted during the
    # audio file discovery process. Optionally, 'comment' can be added to this
    # list.
    #metadata_to_use "artist,album,title,track,name,genre,date,composer,performer,disc"
    # This setting enables automatic update of MPD's database when files in
    # music_directory are changed.
    #auto_update "yes"
    # Limit the depth of the directories being watched, 0 means only watch
    # the music directory itself. There is no limit by default.
    #auto_update_depth "3"
    # Symbolic link behavior ######################################################
    # If this setting is set to "yes", MPD will discover audio files by following
    # symbolic links outside of the configured music_directory.
    #follow_outside_symlinks "yes"
    # If this setting is set to "yes", MPD will discover audio files by following
    # symbolic links inside of the configured music_directory.
    #follow_inside_symlinks "yes"
    # Zeroconf / Avahi Service Discovery ##########################################
    # If this setting is set to "yes", service information will be published with
    # Zeroconf / Avahi.
    #zeroconf_enabled "yes"
    # The argument to this setting will be the Zeroconf / Avahi unique name for
    # this MPD server on the network.
    #zeroconf_name "Music Player"
    # Permissions #################################################################
    # If this setting is set, MPD will require password authorization. The password
    # can setting can be specified multiple times for different password profiles.
    #password "password@read,add,control,admin"
    # This setting specifies the permissions a user has who has not yet logged in.
    #default_permissions "read,add,control,admin"
    # Input #######################################################################
    input {
    plugin "curl"
    # proxy "proxy.isp.com:8080"
    # proxy_user "user"
    # proxy_password "password"
    # Audio Output ################################################################
    # MPD supports various audio output types, as well as playing through multiple
    # audio outputs at the same time, through multiple audio_output settings
    # blocks. Setting this block is optional, though the server will only attempt
    # autodetection for one sound card.
    # See <http://mpd.wikia.com/wiki/Configuration#Audio_Outputs> for examples of
    # other audio outputs.
    # An example of an ALSA output:
    #audio_output {
    # type "alsa"
    # name "My ALSA Device"
    ## device "hw:0,0" # optional
    ## format "44100:16:2" # optional
    ## mixer_type "hardware" # optional
    ## mixer_device "default" # optional
    ## mixer_control "PCM" # optional
    ## mixer_index "0" # optional
    # An example of an OSS output:
    #audio_output {
    # type "oss"
    # name "My OSS Device"
    ## device "/dev/dsp" # optional
    ## format "44100:16:2" # optional
    ## mixer_type "hardware" # optional
    ## mixer_device "/dev/mixer" # optional
    ## mixer_control "PCM" # optional
    # An example of a shout output (for streaming to Icecast):
    #audio_output {
    # type "shout"
    # encoding "ogg" # optional
    # name "My Shout Stream"
    # host "localhost"
    # port "8000"
    # mount "/mpd.ogg"
    # password "hackme"
    # quality "5.0"
    # bitrate "128"
    # format "44100:16:1"
    ## protocol "icecast2" # optional
    ## user "source" # optional
    ## description "My Stream Description" # optional
    ## genre "jazz" # optional
    ## public "no" # optional
    ## timeout "2" # optional
    ## mixer_type "software" # optional
    # An example of a recorder output:
    #audio_output {
    # type "recorder"
    # name "My recorder"
    # encoder "vorbis" # optional, vorbis or lame
    # path "/var/lib/mpd/recorder/mpd.ogg"
    ## quality "5.0" # do not define if bitrate is defined
    # bitrate "128" # do not define if quality is defined
    # format "44100:16:1"
    # An example of a httpd output (built-in HTTP streaming server):
    #audio_output {
    # type "httpd"
    # name "My HTTP Stream"
    # encoder "vorbis" # optional, vorbis or lame
    # port "8000"
    # bind_to_address "0.0.0.0" # optional, IPv4 or IPv6
    ## quality "5.0" # do not define if bitrate is defined
    # bitrate "128" # do not define if quality is defined
    # format "44100:16:1"
    # max_clients "0" # optional 0=no limit
    # An example of a pulseaudio output (streaming to a remote pulseaudio server)
    audio_output {
    type "pulse"
    name "My Pulse Output"
    server "remote_server" # optional
    sink "remote_server_sink" # optional
    ## Example "pipe" output:
    #audio_output {
    # type "pipe"
    # name "my pipe"
    # command "aplay -f cd 2>/dev/null"
    ## Or if you're want to use AudioCompress
    # command "AudioCompress -m | aplay -f cd 2>/dev/null"
    ## Or to send raw PCM stream through PCM:
    # command "nc example.org 8765"
    # format "44100:16:2"
    ## An example of a null output (for no audio output):
    #audio_output {
    # type "null"
    # name "My Null Output"
    # mixer_type "none" # optional
    # This setting will change all decoded audio to be converted to the specified
    # format before being passed to the audio outputs. By default, this setting is
    # disabled.
    #audio_output_format "44100:16:2"
    # If MPD has been compiled with libsamplerate support, this setting specifies
    # the sample rate converter to use. Possible values can be found in the
    # mpd.conf man page or the libsamplerate documentation. By default, this is
    # setting is disabled.
    #samplerate_converter "Fastest Sinc Interpolator"
    # Normalization automatic volume adjustments ##################################
    # This setting specifies the type of ReplayGain to use. This setting can have
    # the argument "off", "album" or "track". See <http://www.replaygain.org>
    # for more details. This setting is off by default.
    #replaygain "album"
    # This setting sets the pre-amp used for files that have ReplayGain tags. By
    # default this setting is disabled.
    #replaygain_preamp "0"
    # This setting enables on-the-fly normalization volume adjustment. This will
    # result in the volume of all playing audio to be adjusted so the output has
    # equal "loudness". This setting is disabled by default.
    #volume_normalization "no"
    # MPD Internal Buffering ######################################################
    # This setting adjusts the size of internal decoded audio buffering. Changing
    # this may have undesired effects. Don't change this if you don't know what you
    # are doing.
    #audio_buffer_size "2048"
    # This setting controls the percentage of the buffer which is filled before
    # beginning to play. Increasing this reduces the chance of audio file skipping,
    # at the cost of increased time prior to audio playback.
    #buffer_before_play "10%"
    # Resource Limitations ########################################################
    # These settings are various limitations to prevent MPD from using too many
    # resources. Generally, these settings should be minimized to prevent security
    # risks, depending on the operating resources.
    #connection_timeout "60"
    #max_connections "10"
    #max_playlist_length "16384"
    #max_command_list_size "2048"
    #max_output_buffer_size "8192"
    # Character Encoding ##########################################################
    # If file or directory names do not display correctly for your locale then you
    # may need to modify this setting.
    #filesystem_charset "UTF-8"
    # This setting controls the encoding that ID3v1 tags should be converted from.
    #id3v1_encoding "ISO-8859-1"
    # SIDPlay decoder #############################################################
    # songlength_database:
    # Location of your songlengths file, as distributed with the HVSC.
    # The sidplay plugin checks this for matching MD5 fingerprints.
    # See http://www.c64.org/HVSC/DOCUMENTS/Songlengths.faq
    # default_songlength:
    # This is the default playing time in seconds for songs not in the
    # songlength database, or in case you're not using a database.
    # A value of 0 means play indefinitely.
    # filter:
    # Turns the SID filter emulation on or off.
    #decoder {
    # plugin "sidplay"
    # songlength_database "/media/C64Music/DOCUMENTS/Songlengths.txt"
    # default_songlength "120"
    # filter "true"
    Last edited by vlad951 (2011-05-07 09:36:11)

    vlad951 wrote:
    Thanks, I successfully launched mpd as a user and it detected all of my music. However, if I launch mpd with the mpd.conf that I created in my home directory, it launches, but outputs the following:
    [vladislav@vladislav .mpd]$ mpd ~/.mpd/mpd.conf
    listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
    Is this normal?
    *sigh* i answer this for the 3rd time in a row... this is no error it just says that binding to your ipv6 interface happened before the binding to ipv4.
    If you want to use your ipv4 interface hardcode it in mpd.conf
    bind_to_address "127.0.0.1"
    you can also have several binds:
    bind_to_address "127.0.0.1"
    bind_to_address "192.168.1.13"
    to make it listen on localhost and the external IP of your network card.
    If your music is on the same machine as your mpd i recommend to use a unix socket in addition.
    bind_to_address "/path/to/some/file/that/does/not/exist/yet"
    and make your client connect to that file instead of the IP. Speeds things up a log e.g. in ncmpcpp
    and btw: you can save your mpd.conf file as ~/.mpdconf and mpd will automatically use it.
    Last edited by Rasi (2011-05-07 08:41:30)

  • PowerBook G4 does not see optical drive in System Profiler

    I have a very strange situation in a powerbook G4 (1.67ghz, hi-res 15" screen).
    I bought the laptop non-working, installed a new power board (plug on old one was fried!) Installed a 250gb HD which I had installed OSX on in another G4 laptop, and it booted up fine, or so I thought.
    When I put in my Leopard install DVD to install over the existing 10.4 Tiger, the disc spun up, but would not mount - would not eject - and when I checked the System Profiler the superdrive was not recognized by the powerbook as being present on the ATA bus. The hard drive, of course, was seen on the ATA bus.
    I thought the superdrive was bum, so I installed a known-working combo drive I had around from a previously parted laptop (Apple branded) and experienced EXACTLY the same situation.
    Other things I have tried included using jumpers to manually set the hard drive to slave and cable select (from the factory, with no jumpers, it is set to master), thinking that perhaps the optical drive was somehow seen as master or cable select. All possible jumper settings I tried made no difference.
    Booting from external firewire hard drive shows exactly the same situation on the ATA bus, EXCEPT (and this is where it gets just weird enough to pique my curiosity and keep me trying to fix it) - When I boot from the external drive WITHOUT AN INTERNAL DRIVE installed, the SUPERDRIVE SHOWS UP ON THE ATA BUS of the System Profiler! I have not yet seen both at the same time, but I can get one or the other to show, depending on, apparently, the presence of the internal hard drive.
    Am I missing something here, or am I to assume a fault in the IDE controller of the logic board?
    I have never seen this laptop working properly, but the seller I acquired it from stated that the optical drive worked fine until he fried the DC in-board, presumably with a faulty power supply. He had removed his hard drive to save the data on it.
    Thanks for any help or clues that anyone might provide.
    See another post with similar situation (archived, or I would have jumped on that thread):
    http://discussions.apple.com/thread.jspa?threadID=1862129&tstart=0
    Ray

    Well, I am happy to report that the situation is resolved with my powerbook not seeing the superdrive, but I still do not really understand exactly why it was unavailable in the system profiler as I originally posted.
    My particular solution was to wipe out (erase) the hard drive, zapped PMU, zapped PRAM, did the reset-nvram in open firmware, rechecked to make CERTAIN the proper cables were installed properly, and Now I just completed a fresh install of Leopard from the previously recalcitrant superdrive, to the now-clean hard drive.
    My BEST GUESS as to what was wrong with the situation from the outset may have had something to do with where the hard drive came from and how that operating system was installed. (the OS was on the HD when I installed it) In hindsight, perhaps doing all the resets, as well as repairing permissions MIGHT have done it, but I got caught up in thinking it might be cables or something.
    So, I would advise others with a similar problem to:
    repair the hard drive
    repair permissions on the hard drive
    reset PMU
    reset PRAM
    boot to open firmware (hold command-option-o-f at boot) and type "reset-nvram" (without quotes) enter, the type "set-default" enter, then type "reset-all" enter
    cross your fingers, knock on wood, and boot! See what happens....
    if no glory, THEN look at cables (make certain they are the CORRECT cables and that they are seated properly) I bought a hard drive cable and an optical cable from ebay sellers with assurance that they were the proper cables, and NEITHER had the same part number as the original cable which I suspected faulty, and that in the end are actually GOOD! GO BY PART NUMBERS! do not accept someone elses assurance that their cable is the proper one!
    then suspect faulty optical drive - if possible swap another drive in and check.
    if a second optical fails, then SUSPECT logicboard, but before you invest in a new logic board ($$$$$) try putting a freshly erased HD in and just see if that helps.
    good luck to you all with your mac troubleshooting!
    and thanks to all who read and pondered....
    I will mark this case "answered" though it is more closed than truly answered.
    I am very relieved that the fault did not lie in any of the major components (or even the minor ones for that matter)
    It turned out to be only software/installation/settings, even though the symptoms certainly seemed to point to a hardware issue. It pays to try the resets and repairs!
    Ray

  • Does not see optical drive

    My IMac does not see the optical drive, however, it is visibable in windows 7.  I'm running Parallels

    Exactly. It can only be connected to one at a time. You have to eject it from Parallels for it to be used by the Mac.
    I initially thought you were using Boot Camp.

  • [Solved] Xrandr does not detect external monitor

    I recently just installed Arch linux on my laptop and decided to install the catalyst driver as well. I followed all the instructions on how to install catalyst and when I try to use the xrandr command it does not show my second monitor. I am using i3wm on the latest kernel and catalyst driver. I can also see a x cursor when I move my mouse to my other screen but it does show the i3bar or I cant drag a window to the other screen
    Here is my xorg.conf
    Section "ServerLayout"
    Identifier "aticonfig Layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    Screen "aticonfig-Screen[0]-1" Above "aticonfig-Screen[0]-0"
    EndSection
    Section "Module"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-1"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:0:1:0"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-1"
    Driver "fglrx"
    BusID "PCI:0:1:0"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    Monitor "aticonfig-Monitor[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-1"
    Device "aticonfig-Device[0]-1"
    Monitor "aticonfig-Monitor[0]-1"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    what xrandr -q shows
    Screen 0: minimum 320 x 200, current 1366 x 768, maximum 1920 x 1920
    LVDS connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
    1366x768 60.00*+
    1360x768 60.00
    1280x768 60.00
    1280x720 60.00
    1024x768 60.00
    1024x600 60.00
    800x600 60.00
    800x480 60.00
    640x480 60.00
    DFP1 disconnected (normal left inverted right x axis y axis)
    CRT1 disconnected (normal left inverted right x axis y axis)
    Last edited by Green (2014-09-16 01:00:22)

    Never mind I just needed to delete my xorg.conf and regenerate it by
    # aticonfig --initial

  • M30x bios does not detect hard drive, wont boot from HD

    Can someone help me in this issue.
    My Sat m30x wont boot from Hard Drive, instead tries to boot from network.
    Tried to load setup defaults and Hd wont show on the settings
    tried to reistal origin CD software by toshiba and the message no target drive displays
    Can this be a hardware problem, some damaged fisical conection, or is it a bios problem
    thanks in advance for some ligth on this problem

    My M30x has the same problem. I just have used it for 2 months.
    I sent it to the repair center as I was told to do, because it has warranty.
    I'm still waiting for a response from them. I don't know what caused it.

  • [solved] ArchLinux does not detect my usbstick

    Hi,
    I just installed ArchLinux a few days ago. Today I wanted to plugin my usbstick. I expected an icon to show up on the Gnome desktop. But nothing happened. Gnome-device-manager doesn't show anything. And dmesg also doens't mention anything about a usbstick plugged in. It's like the system doen's detect it.
    Any idea why this is?
    Last edited by mariourk (2007-10-21 18:04:27)

    I have both HAL and DBUS in rc.conf.
    DAEMONS=(syslog-ng network netfs crond portmap fam dbus hal gdm sshd)
    Gnome-volume-manager is installed.
    The usb-modules are also loaded
    [mario@dagobah ~]$ lsmod | grep usb
    usbhid 38048 0
    hid 26240 1 usbhid
    ff_memless 5256 1 usbhid
    usbcore 112520 3 usbhid,ohci_hcd
    I'm working with an usb-mouse without any trouble.

  • HP x720w 64GB Pen Driver Does not detect on Windows 7 Laptop

    HP x720w 64GB Pen Driver Does not detect on Windows 7 Laptop. While it detects on my PC. Same OS. Pls advise.

    I will have to wait until a Moderator inspects your image and makes it viewable.
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • [SOLVED] BIOS not detecting USB Drives after i installed Arch

    SOLVED: In BIOS under 'Advanced' disable 'Fast BIOS Mode'.
    Original post:
    Hi there!
    I'm fairly new to the arch (and linux) scene and just setup my Samsung 530U3B with a brand new installation of arch. Everything went fine and the system is running flawlessly. Almost.
    I just happend to notice that BIOS is not checking for USB drives anymore, it just somehow skips that part. If enter the boot selection, the bootable USB drive won't show up. Neither does it show up in BIOS setup. I tried to boot with the same USB drive that i used to install arch just yesterday, the live media does not boot - the drive doesn't even blink. The boot priority is set to usb drive first, the boot selection screen (hammering f10 during boot) doesn't give me any other option than to boot from the normal SSD. Also, prior to the arch installation (came with w7 installed) the BIOS screen would stay for about 2seconds and then proceed to boot - this doesn't happen anymore. When i press the power button greeted by the grub bootloader in about 1s.
    I tried 2 different usb drives, both with the arch iso (same that i used to install the currently running OS, downloaded yesterday). The drives also show up once my arch is booted (starting to blink just after i hit enter in grub). Also, both drives boot without a problem on my desktop computer.
    Anyone got any ideas?
    I don't really now what kinda of information would be helpful so i'm just dumping stuff i know:
    BIOS: Phoenix SecureCore Tiano Version 04XK
    Machine: Samsung 530U3B
    SSD: Samsung MZ7PC128HAFU-000
    ISO used to install (checksum ok): archlinux-2012.07.15-netinstall-dual.iso
    Last edited by araex (2012-07-26 16:57:47)

    DSpider wrote:
    The boot priority is set to usb drive first
    Welcome to the forum.
    If you just set the USB stick to be first in the boot order, the next option (from the list) takes its place the moment you unplug it. You need to set the BIOS to boot from your equivalent of "Removable Devices" first, "Internal Drives" second and "Optical Drives" third.
    The USB stick doesn't show up at all. I set the priority as follows:
    1. USB HDD
    2. USB FDD
    3. USB CD
    4. SATA CD
    5. SATA HDD
    6. NETWORK
    I used that same configuration to install arch. USB doesn't seem to initialize at all. Also, if i enter "usb" in the grub commandline, no devices are listed.
    Thanks!
    UPDATE:
    I just figured it out. In my BIOS under 'Advanced' the 'Fast BIOS Mode' was enabled, once i disabled it, everything went fine. I don't remember changing that option. Silly me.
    Sorry for your time
    Last edited by araex (2012-07-26 16:56:30)

  • [SOLVED] New install does not see SSD drive

    Ok, I have a DFI motherboard which at first did not recognize my new Intel SSD drive I have installed. After updating the BIOS, it now correctly recognizes it. However when I run the 2009.2 cd and try to prepare the drives, it does not show any drives listed?
    /sbin/fdisk -l
    does not show any drives either so it looks like arch cant see any installed HD's which makes since, but the motherboard does show the new Intel SSD as a Sata drive right under my DVD player?
    Any help?
    Edit: I hooked up my old Seagate drive and it shows up fine. Any idea on why this SSD is not playing nice?
    Solved: I have come to the conclusion this has nothing to do with the Arch install, but is simply a hardware issue with my motherboard. I installed the SSD drive in my wifes pc, it seen the ssd as a sata drive while booting, it seen it when arch was initializing, it seen it when I did a fdisk, and when i finally tried to install, it was there too!!
    So there must be some issue with my old DFI MB. I will work on that or upgrade..Thanks to everyone who helped out...
    Last edited by banshee28 (2009-02-28 16:48:07)

    lilsirecho wrote:
    I had trouble with my throttle device not making contact with the data lines when connected to USB.
    I assume the SSD has the same connector as the motherboard and the cable can be reversed end to end to test for performance.
    I use a multimeter to verify the presence of power to the device.
    Sata cables are known to be flaky.
    Throttle devices use 5vdc power from USB connector and are connected to esata cables at the same time since sata ports do not supply power.  The connections for throttle are on opposite ends of the device.
    I am not familiar with the SSD power setup but assume it is 5vdc as well.
    No other suggestions here..................
    Yes, the cable should be able to be reversed as the ssd drives are identical compared to normal sata drives in respect to the cable connections: one sata data connection and one power. I will try some different cables and see if that helps. I did try a new port on the mb which did not work, and when i used the current cables on my older seagate drive it worked fine
    Last edited by banshee28 (2009-02-26 13:15:52)

  • [SOLVED] Kernel over 3.14.4-1 does not detect my hardware proper

    Hello everyone,
    i've a little problem with any kernel higher then 3.14.4-1.. After a long time, i bootet up my PC and updatet Arch. There where nearly 350 package updates. Everything went fine, except for the kernel update.
    Updating to kernel 3.16.3-1 broke nearly everything on my system. Arch boots but does not detect any hardware like the graphics card or the network adapter. I've read journalctl but can't find any usefull hints or a point do begin my error searching.
    Maybe someone of you can give me a useful hint…
    Here is a link to the logfile: http://p.tkolb.de/SpGKcAQjxk1A.txt
    Thank you very much in advance for your help,
    Sqozz
    Last edited by Sqozz (2014-09-29 17:45:46)

    I've reverted to the last working kernel with "pacman -U".
    Could now find the Problem: /boot was not mountet during the kernel build.. Such a stupid mistake.
    Thank you anyway for your fast replies!

  • Tecra Z50-A-11V: New SSD but Win 8.1 does not detect it

    We bought a Crucial M550 256GB disk and want to replace in a Toshiba Tecra Z50-Av1
    We do not want to make any transfer of data or cloned.
    We want to do a clean install with Windows 8.1
    The BIOS recognizes the SSD
    But when you install Windows 8.1 does not detect any disk connected to the unit and requested additional drivers. Windows not detect drive
    https://www.dropbox.com/s/mlvk6v3lxzi1rrh/2014-05-04%2009.47.18.jpg
    https://www.dropbox.com/s/fr2eo5l9xonaoln/2014-05-04%2009.48.59.jpg
    https://www.dropbox.com/s/8usxog8wm06funr/2014-05-04%2010.06.09.jpg
    i too test with lasted version of this driver (old F6 in boot to locate hdd driver)
    https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23496&lang=eng&wapk w=f6flpy-x64.zip
    and with toshiba package
    http://support.toshiba.com/support/viewContentDetail?contentId=4004211
    you can see than i have 3.20 version of BIOS. interestingly I see that the last one is the Toshiba has released version 3.1
    But always the drive CRUCIAL is not reconized by the boot instalation of windows
    The problem is similar with ubunto, kubuntu, .... the drive is detected with the BIOS but not for the OS.
    any help?
    Thanks

    Hi
    Did you solve this issue?
    Could you install the Windows 8.1 system on this SSD drive?
    I think the additional driver installation while setup procedure isnt necessary since Win 8.1 should already contain the essential drivers.
    From my point of few there could be an compatibility issue (maybe SSD firmware update would solve this).
    How about the usage of other SSD drives? Do you have the same problem using other SSD drives from other manufactures?
    Feedback would be appreciated.

Maybe you are looking for