Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I made a bootable usb flashdrive by the root command:
#dd if=debian-live-6.0.7-i386-gnome-desktop.iso of=/dev/sdb bs=1M;sync
My dell-vostro-xxxx laptop recognized the usb and I could run the live OS. But when I tried it on my Zenith-AlwaysOn (Indian OEM) netbook
the machine simply hung and refused to recognize the usb.
With debian-wheezy-live-rc1-i386-gnome-desktop.iso both the machine
booted without any hiccup.
Can anybody please explain why this strange behaviour?
Last edited by prudra; 04-30-2013 at 08:50 AM.
Reason: Grammatical mistake.
I ran into this a couple of times when I was doing computer repair. Some motherboards just hate certain USB hardware--anything from hubs, to flash drives, to gamepads, etc. I have yet to determine WHY this happens, but when it does, the main symptom (or only symptom) is that if you try to boot with it in, it won't get past the initial POST screen, or the screen will simply remain black (depending on the computer).
For a flash drive, you might try the following from a Linux computer. Make sure that there's nothing on it you care about before starting.
1. Plug the flash drive in.
2. Type the following (as root):
# Identify the device name of your flash drive--probably /dev/sdXY. Note what "X" and "Y" are.
badblocks -svw /dev/sdX
# Note that "Y" isn't included. This will check your drive with a read/write test. It will erase all data! (Non-destructive tests can only test for certain kinds of defects.)
Wait for the test to finish. If numbers start appearing, then those are bad sectors: your drive is effectively "dead," and the solution is to simply use a different flash drive. (Depending on how it's being read on each piece of hardware, the bad sectors may or may not be noticed--hence, some computers will "like" it and not others.) If not, then the drive is almost certainly OK, and the problem is with the laptop's motherboard not "liking" it. Hopefully, someone knows how to get past the latter problem; I've never been able to reconcile it, short of not using that device with that motherboard.
I'll answer DaneM first. The funny thing is that this occurs only when live version of the Stable Debian is tried. (This also is the case with live linuxmint maya.) There is no problem with live versions of Wheezy, ubuntu,xubuntu, opensuse; nor with non-live version of squeeze; all tried with the same usb.
When tried all these on the other dell laptop eerything is ok. So the usb must be all right. The hardware of the netbook must be the culprit.
Jefro, I didn't understand what is cold booting.
However, since Wheezy will be out this weekend and the non-live version of the stable on this usb creates no problem (I am already working with Squeeze on this netbook), all this must be academic.
Well, here's something you can try: have you used the "isoinfo" tool to see what's different about the images? Specifically, the boot-up methods employed by the different images could be part of the problem. (I think that they SHOULD work on any PC if they work on one, but...) For example, this is what I get with I look at the Linux Mint 14 64-bit MATE ISO:
dane@orchestrator /mnt/PERSONAL/Dane/ISO/Linux/Linux Mint/14 Nadia $ isoinfo -d -i linuxmint-14-mate-dvd-64bit.iso
CD-ROM is in ISO 9660 format
System id: LINUX
Volume id: Linux Mint 14 MATE 64-bit
Volume set id:
Data preparer id:
Application id: GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE (C) 1997-2006 J.PEARSON/J.SCHILLING (C) 2006-2007 CDRKIT TEAM
Copyright File id:
Abstract File id:
Bibliographic File id:
Volume set size is: 1
Volume set sequence number is: 1
Logical block size is: 2048
Volume size is: 495477
El Torito VD version 1 found, boot catalog is in sector 69
Joliet with UCS level 3 found
Rock Ridge signatures version 1 found
Eltorito validation header:
Arch 0 (x86)
Key 55 AA
Eltorito defaultboot header:
Bootid 88 (bootable)
Boot media 0 (No Emulation Boot)
Load segment 0
Sys type 0
Bootoff 46 70
The "Eltorito," "Joliet," and "Rockridge" stuff are probably of specific importance in this, but you might also note anything that's different about the images, because "the clue" may lie therein. :-)
Good that you cleared that up for me on the iso. Thanks.
Now that I have learned what is cold booting I tell that I have all along been doing exactly that. In fact, I have learned in the hard way that restarting the computer with a live bootable usb does not work on my netbook.
So you did a full power down, pulled the plug and removed battery, pressed power button a few times, then attached usb flash, attached power and booted to bios? What did you see in bios in "hard drive" order??
Now that wheezy has become stable, I downloaded
and dd'ed it on the usb flashdrive and now the netbook is booting.
My previous attemt was for squeeze
Maybe, something was changed in the wheezy release and this is one case when
Murphy's law is not working.