WD World Edition My Book as NAS

Source

The World Edition My Books function as Network-attached storage (NAS), by way of an Ethernet interface. They also feature an extra USB host port to allow an additional USB drive to be daisychained. Data on first generation (Blue Rings) My Book World is accessed as CIFS/SMB shared folders. The second generation (White Lights) expands the access choices to include NFS, FTP, an iTunes server, and a Twonky media server.

In addition, the World Edition uses WD Anywhere Access to gain remote access to the drive via the Internet.

It has the same basic case design as the Premium Edition drives, including the capacity gauge, except the color of the World Edition is white. It also has the same Morse codeventilation as the other editions.

[edit]

Network speed

Although MyBook Ethernet-capable disks come with a Gigabit Ethernet interface, the network speed is significantly slower. Especially for older "blue rings" models (200Mhz ARM CPU and 32 MByte RAM), where it varies between 3–6 MByte/s, with an average of 4.5 MByte/s.^[5]. The newer "white lights" MyBook World Edition 1TB and 2TB models, WDH1NC and WDH2NC (oxnas810^[6], 380 Mhz ARM CPU and 128 MByte RAM), compare to USB drive speed at about 10MB/s write and 25MB/s read.^[7].

Using a performance-optimized copying software, such as FastCopy^[8], enlarged TcpWindowSize on WindowsXP ("TCP tuning") and enlarged network MTU size ("Jumbo frame") enabled on both MyBook and Windows, a "white lights" WDH1NC achieves ~36 MByte/s reading and ~18 MByte/s writing speed for Samba/CIFS access over Gigabit Ethernet.

[edit]

Internals

Controller board for My Book World Edition

This drive runs BusyBox on Linux on an Oxford Semiconductor 0XE800 ARM chip which has the ARM926EJ-S core. In addition it uses aVIA Cicada Simpliphy vt6122 Gigabit Ethernet chipset, and a Hynix 32 Mbit DDR Synchronous DRAM chip. The webserver is the mini_httpd server, although thought to be Lighttpd. The drives of the World Edition are xfs formatted, which means that the drive can be mounted as a standard drive from within Linux if removed from the casing and installed in a normal PC.

The disk filesystems are also known to exist in a format created by linux multiple devices driver (Mdadm) which ultimately wraps an ext3 partition with some metadata that allows the inquiry of the position of the drive in a RAID set. Unfortunately, this makes mounting the drives outside of the enclosure a bit more complicated, it also requires a machine with a flavor of the Linux operating system. For example, the best way to mount the drives on a Linux flavored operating system after they have been removed from the enclosure is to use the following set of commands for mirrored RAID 1 disks.

$ sudo modprobe md
$ sudo mknod /dev/md4 b 9 4
$ sudo apt-get install mdadm
$ sudo mdadm --assemble /dev/md4 /dev/sdb4
$ sudo mkdir /media/xyz
edia/xyz
$ sudo chmod -R 777 /me
$ sudo mount /dev/md4 /
mdia/xyz

Note that the above set of commands assume that your drives appear as /dev/sdb to linux. You can use a utility like gparted to determine which paths are relevant for your setup.

And alternately you can use this command set for mounting a multidisk spanning RAID 0 set in linux:

$ sudo modprobe md
$ sudo mknod /dev/md4 b 9 4
$ sudo apt-get install mdadm
$ mdadm -Cv /dev/md4 -l0 -n2 -c64 /dev/sdb4 /dev/sdc4
$ sudo mkdir /media/xyz
edia/xyz
$ sudo chmod -R 777 /me
$ sudo mount /dev/md4 /
mdia/xyz

Note that the above set of commands assume that your drives appear as /dev/sda and /dev/sdb to linux. Again, you can use a utility like gparted to determine which paths are relevant for your setup.

Further details and support are available at the following My Worldbook wiki.

[edit]

Extending capabilities

The device can be 'unlocked' and accessed via SSH terminal (newer versions of WDH1NC10000 do not need to be "unlocked": MBWE SSH Access), meaning that the WD MioNetjava-based software can be disabled so the device can be run with an unrestricted Linux OS,^[9] at the cost of voiding the warranty.^[10] The unlocking makes it possible to install other software on MyBook (i.e. run a different webserver or an ftp server (such as vsftpd) on it, use NFS for mounting shared directories natively from Unix, or even install a bitTorrent client such as rTorrent,^[11] etc.) Further information on unlocking the device and downloads you are going to need can be found here.

Linux Software Raid 1 Setup

How To Resize RAID Partitions (Shrink & Grow) Software RAID
Source

1. Introduction

This article describes step by step setup of Linux software RAID 1 on Linux Platform. Although this software RAID 1 configuration has been accomplished on Debian ( Ubuntu ) it also can guide you if you are running some other Linux distributions such as RedHat, Fedora , Suse, PCLinux0S etc. For RAID-1 setup we need two or more disks. RAID1 mode creates a exact mirror of all data between two or more disks.

1.1. System Info

• OS: Debian Etch ( basic installation on /dev/sda)
• Kernel: Linux raid 2.6.18-5-686 #1 SMP Fri Jun 1 00:47:00 UTC 2007 i686 GNU/Linux
• Hard Drives: /dev/sda -> 4GB , /dev/sdb -> 5GB

2. The Plan

We start with running linux system Debian Etch and the following partition scheme and hard drives ( sda , sdb ):

3. Software Installation

There is only 1 package ( + prerequisites ) needed by software raid 1 on debian. This package is mdadm. Simply use apt-get tool to install mdadm package it into your system. You may be asked to answer couple question.

apt-get install mdadm 

4. Configure Kernel Modules

4.1. Load modules at boot time

No we need to make sure that raid kernel modules are loaded at the boot time. To accomplish this task we need to edit /etc/modules files and add couple lines. Open up your favorite text editor or just simply append lines with echo command.

echo raid1 >> /etc/modules echo md >> /etc/modules 

4.2. Load modules to the Kernel

At this stage if we want to use raid modules we have two options. First one is to reboot our system and the other option is to use modprobe or insmode  to load modules to the Kernel. I find second option easier:

modprobe raid1 

NOTE: if you do not have md module already loaded as shown on the figure above use modprobe to load it:

modprobe md 

There are two ways to confirm that our raid modules are loaded into kernel:

lsmod | grep raid1 

cat /proc/mdstat 

You should have similar output as shown on the figure below:

5. Prepare sdb for RAID

6. Setting Up RAID 1 Arrays

6.1. Create RAID 1 Arrays

6.2. Create a filesystem on RAID 1 Arrays

6.3. Edit mdadm.conf file

7. Edit /etc/fstab

8. Configure GRUB boot manager

9. Copy data from sda => sdb

10. Setup boot manager

11. Reboot

12. Add first hard drive ( sda ) to the RAID 1 array

12.1. Change Partition Id with sfdisk

12.2. Add partitions with mdadm to RAID 1 array

12.3. Edit /etc/mdadm/mdadm.conf

13. Finish

grub probs with SW RAID

software raid 10 : my experience
Ressources

Serial ATA (SATA) for Linux GRUB manual

Manage a Linux RAID 10 Storage Server

Linux RAID and Hardware I've seen a lot of confusion about Linux RAID, so let's clear that up. Linux software RAID has nothing to do with hardware RAID controllers. You don't need an add-on controller, and you don't need the onboard controllers that come on most motherboards. In fact, the lower-end PCI controllers and virtually all the onboard controllers are not true hardware controllers at all, but software-assisted, or fake RAID. There is no advantage to using these, and many disadvantages. If you have these, make sure they are disabled. Ordinary PC motherboards support up to six SATA drives, and PCI SATA controllers provide an easy way to add more. Don't forget to scale up your power and cooling as you add drives. If you're using PATA disks, only use one per IDE controller. If you have both a master/slave on a single IDE controller, performance will suffer and any failure risks bringing down both the controller and the second disk.

Debian: transfered Grub can’t find /dev/md0

It came out what is really the problem here: in /etc/mdadm/mdadm.conf there is the old set of hdds (through the UUIDs). Just replace:

ARRAY /dev/md0 UUID=x

with:

ARRAY /dev/md0 devices=/dev/sda1,/dev/sdb1

or whatever is your configuration, rebuild the initramfs with:

update-initramfs -k `uname -r` -c -t

do:

update-grub and grub-install "(md0)"

that’s it!

Solved in teamwork, cf: http://forum.ubuntuusers.de/topic/grub-bootet-nicht-vom-raid1/

http://forum.ubuntuusers.de/topic/raid-nachtraeglich-installieren/

Die Grub-Install von LiveCD läuft doch auch über chroot.

sehen: 

/etc/fstab /etc/mtab /boot/grub/menu.lst

/etc/mdadm/mdadm.conf 

sowie

sudo blkid
sudo fdisk -l
mount

Versuche mal die UUID von md0 zu ändern

Versuche mal root direkt so zu übergeben:

root=/dev/md0

=====

Prompt mit blinkendem Cursor bringt:

ALERT! /dev/md0 does not exist. Dropping to a shell!
(initramfs) _

und /dev/md0 existiert nicht in dieser Konsole...

Solution:Du musst nochmal mit nem LiveSystem in ne chroot-Umgebung und den Schritt aus deiner Anleitung wiederholen, wo mdadm installiert wird und wo das initramfs upgedatet wird.

Also, in der Anleitung mit der ich das RAID aufgebaut hab, hab ich nix gefunden über initramfs, aber ich hab bischen hier im Forum gestöbert und mit dem Befehl

update-initramfs -u -k all

hab ich jetzt wohl mdadm integriert und dann diese initrd-Datei in meine boot-Partition kopiert, da ich nicht als chroot drin war. Also scheint zu gehen, der Rechner bootet und mount zeigt dass /dev/md0 als / eingehängt ist, das sieht doch schon mal gut aus.

Das initramfs aktualisieren:

sudo mount /dev/md0 /mnt
sudo mount -o bind /dev /mnt/dev
sudo mount -t proc /proc /mnt/proc
sudo chroot /mnt /bin/bash
 all
sudo update-initramfs -u -
k

Ok, das hat schon mal nicht funktioniert, das wäre eine Sache, die man am Wiki erweitern müsste - bei der "normalen" Ubuntu-LiveCD ist madam nicht von Anfang an geladen (bei der alternate LiveCD wohl schon...?)

Lösung:

sudo apt-get install mdadm 

http://forum.ubuntuusers.de/topic/grub-bootet-nicht-vom-raid1/2/

=====

http://en.opensuse.org/How_to_instal..._software_RAID

The definitive guide to Software RAID on linux

The Ubuntu 'White Screen of Death'

Source
somewhat of a workaround:
Hold down left-shift on boot to enter GRUB
hit "e" to edit the kernel
remove "quiet splash" and replace with "nomodeset single"
control-x to boot
(http://bugs.launchpad.net/ubuntu/+so...2/+bugs/511130)
A system recovery screen appears, I selected "start ubuntu normally" (or whatever option is similar) which put me through to a shell login prompt. After logging in to the basic shell I typed:
Code:
$ sudo /etc/init.d/gdm start
Which, much to my surprise, launched the Lucid Lynx gui.
I'm using the standard drivers for my video card (I attempted, but failed to install ATI's catalyst control center.)
^^^^^^^^^^^^^^
Re: 10.04 LTS RC: Blank Screen at startup

For me, I seem to have found the workaround.
First, credit where credit is due:
http://ubuntuforums.org/showthread.php?p=9221567
So, to make this change (remember to ALWAYS preserve a backup of your files)
Code:
$ cd /etc/default
$ sudo gedit grub
The editor will come up
Locate this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Change it to:
GRUB_CMDLINE_LINUX_DEFAULT="radeon.modeset=0 quiet splash"
Save, reboot, and voila!
When Lucid is installed, it defaults to KMS - Kernel Mode Setting, which means the Kernel determines the graphics mode to launch in. It seems that ATI cards don't like this and cause the Blank Screen of Death(tm).
Further reading:
https://wiki.ubuntu.com/X/KernelModeSetting
Further note: I make no promises as to whether this change will work on "your" system.
Source
This may be of help: http://www.ubuntugeek.com/incompatibility-with-nvidia-upstream-driver-installer-in-ubuntu-10-04-lucid.html
Edit: Did you run
$ sudo nvidia-xconfig
 in the terminal and restart the X-server?
Lucid Lynx and NVIDIA video cards
Source
I’ve installed nvidia-current. Now
lsmod | grep nvidia
shows me that the nvidia module is loaded, everything is ok, except that i can’t turn on the composite and all those visual effects, that worked fine in karmic.The problem solved, now i’m using native NVIDIA 195.36.24 driver. Here is what i’ve done:

http://lushchick.blogspot.com/2010/05/lucid-lynx-and-nvidia-video-cards.html
.........
This really sucks. Unfortunately even the latest driver available in Lucid’s “Hardware Drivers” menu doesn’t support my NVidia GT 240.
Worse yet, the Nouveau driver doesn’t work very well with my card, either, leaving strange artifacts on screen during startup and locking up the X Server every now and then.

If the nvidia drivers don’t allow you to have special effects, just try this :

blacklist nouveau
blacklist lbm-nouveau
..in the following file :
/etc/modprobe.d/blacklist.conf
.. then :
#update-initramfs -u .. in a terminal.
Download and install normally the nvidia proprietary drivers. Restart the X server … and everything should be OK!
Source
help.ubuntu.com/.../BinaryDriverHowto/Nvidia
Source
On a terminal
(alt+ctrl+F1)login and type:
ps -ef
of
top
cat /etc/X11/xorg.conf
Try to ssh into it when it freezes, if you can. Many times I've had a hard X server lockup, but I can still login remotely and kill X.
To ssh into the machine, you need another machine on the same network (it can be any OS). Install openssh-server, and start it with

Code:

/etc/init.d/ssh start

On your remote machine, install openssh-client or PUTTY (Windows). Then on remote host do

Code:

ssh antonio@192.168.1.200

Of course you would use your username and the ip address of the machine you're trying to log into.
Try

Code:

sudo ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key

Also,

Code:

sudo /usr/sbin/sshd -t

It would be very good if we could ssh into the machine after the crash, it will be much easier to figure out what is wrong.
------------
ssh's port is 22,
Try a

Code:

sudo apt-get --purge remove openssh-server

and reinstall. I've never even had to generate the keys by hand, so I don't know why this isn't working.

You could also try installing a telnet server, that might be easier to do, and we can still log in and look at the machine (or if we can't, then we probably can't with ssh either).

Code:

sudo aptitude install telnetd

I just tried this, and it required nothing else. I could telnet to my machine immediately (it starts the daemon on demand).
You don't need telnetd on the remote machine, just "telnet" (the client). Telnet should also be available on a Windows machine, just start the command prompt and run "telnet".
Logging in:
Run telnet
Inside telnet: open 192.168.0.5 (or whatever your IP is)
You should get a login prompt, where you type your username and passwd.
------
An open port means that a) nothing is blocking the port and b) something is listening on that port. If you have no firewall, it should just work; mine started up telnetd automatically when I tried to log in (the "internet daemon" inetd listens on port 23 and starts telnetd). I have tried this from an XP machine.
Is anything else on your machine out of whack? Is all this trouble another manifestation (like the lock ups) of a deeper problem?


--------------------------------------

it sounds like you have enabled desktop effects (wobbly windows and the like) before you removed your video drivers. by doing that you have disabled hardware 3d acceleration which the desktop effects needs to run. instead the desktop effects are just showing a 'white screen'.
im not sure howto disable desktop effects from loading on login so id recommend that you run the command
sudo apt-get remove compiz beryl
after logging into recovery mode
(see: https://wiki.ubuntu.com/RecoveryMode to learn more about howto boot into recovery mode)
if you want the desktop effects back you will have to re-install you restricted video drivers and then install compiz or beryl from synaptic.
----------
got to a terminal and did a
sudo apt-get remove compiz beryl
but it reported a bunch of packages no longer needed that weren't removed automatically, mainly compiz libraries IIRC. Simply running the above command did not fix the system, but running
sudo apt-get autoremove
after removing compiz and beryl did fix it.
You can also try this:
http://ubuntuforums.org/showpost.php?p=4970051&postcount=2
...and this:
http://ubuntuforums.org/showpost.php?p=5082510&postcount=2

---

----------------------------------------
http://ubuntuforums.org/showthread.php?t=819043

Code:

sudo apt-get install build-essential

-------------------------------------------
sudo dpkg-reconfigure xserver-xorg
 and set the following options:
- Kernel framebuffer device NO (in your xorg.conf this option should appear as "false")
- 16 bit (instead of the default 24-bit selection)
Restart X and see if you have any improvement.
----------------------
install the new Nvidia drivers using these steps:

0. sudo apt-get remove nvidia*
1. Ctrl-Alt-F1
2. sudo /etc/init.d/gdm stop
3. sudo su
4. sh ./NVIDIA-Linux-x86-173.14.05-pkg1.run
5. go through all the prompts
6. restart
I also found an interesting thread about the new drivers:
http://www.nvnews.net/vbulletin/showthread.php?t=113919
Using the following command should speed up applications like Firefox:

Quote:

nvidia-settings -a InitialPixmapPlacement=2 -a GlyphCache=1 -----------------------------
http://http//ubuntuforums.org/showthread.php?t=819043
http://distrowatch.com/weekly.php?issue=20070903#feature
correct nvidia settings
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildd@vernadsky) Tue Mar 4 20:24:34 UTC 2008

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
EndSection

Section "Module"
Load "glx"
EndSection

Section "ServerFlags"
Option "Xinerama" "0"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Philips PHL 20PF5320"
HorizSync 31.0 - 60.0
VertRefresh 47.0 - 75.0
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "nvidia"
Option "NoLogo" "True"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 7900 GS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Configured Video Device"
Monitor "Configured Monitor"
DefaultDepth 24
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP: 1024x768_70 +0+0; DFP: 1024x768 +0+0"
EndSection
__________________
Source
Black screen on 10.0
So after a lot of problems upgrading to 10.04, eventually a clean install. First in 8.04, 9.10 and now as said in 10.04 for the second time, problems with the screen. It starts, gets a bit grey, then I see the GNU without touching keys, I choose the one at the top, Get's black again, Then some orange shows very short and I can log in, but not in any interface. Just as root in terminal. That's as far as I get.
The machine:
PC1(wired)10.04; ASRock N68; Dual AMD 64 Athlon(tm) II X2 240; RAM: 2048 DDR2; ATA Disk WD320Gb; Atheros AR5001X + W'less Sitecom 300N ; VGA compatible controller C61 [Nvidia GeForce 7025 / nForce 630a]; screen Acer 19'' V193HQ 1280x720 max.
Tried this:
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia
Installed this one
http://www.webupd8.org/2010/06/how-to-install-nvidia-25635-display.html
Worked great for 2 weeks and is now gone with the wind. Nowhere to find. Strange.....
This hereunder is what's on it, I can imagine it will conflict, but what can I get rid of and what not. And how, I can only work from USB-Stick.
ubuntu@ubuntu:~$ apt-cache search nvidia
dmraid - Device-Mapper Software RAID support tool
jockey-common - user interface and desktop integration for driver management
jockey-gtk - GNOME user interface and desktop integration for driver management
jockey-kde - KDE user interface and desktop integration for driver management
libvdpau-dev - Video Decode and Presentation API for Unix (development files)
libvdpau-doc - Video Decode and Presentation API for Unix (documentation)
libvdpau1 - Video Decode and Presentation API for Unix (libraries)
nvidia-173-modaliases - Modaliases for the NVIDIA binary X.Org driver
nvidia-185-modaliases - Transitional package for nvidia-185-modaliases
nvidia-96-modaliases - Modaliases for the NVIDIA binary X.Org driver
nvidia-common - Find obsolete NVIDIA drivers
nvidia-current-modaliases - Modaliases for the NVIDIA binary X.Org driver
nvidia-settings - Tool of configuring the NVIDIA graphics driver
smartdimmer - Change LCD brightness on Geforce cards
xserver-xorg-video-nouveau - X.Org X server -- Nouveau display driver (experimental)
xserver-xorg-video-nv - X.Org X server -- NV display driver
nvidia-173 - NVIDIA binary Xorg driver, kernel module and VDPAU library
nvidia-173-dev - NVIDIA binary Xorg driver development files
nvidia-173-kernel-source - Transitional package for nvidia-glx-173-kernel-source
nvidia-180-kernel-source - Transitional package for nvidia-glx-185-kernel-source
nvidia-180-libvdpau - Transitional package for nvidia-185-libvdpau
nvidia-180-libvdpau-dev - Transitional package for nvidia-185-libvdpau-dev
nvidia-185-kernel-source - Transitional package for nvidia-glx-185-kernel-source
nvidia-185-libvdpau - Transitional package for nvidia-185-libvdpau
nvidia-185-libvdpau-dev - Transitional package for nvidia-185-libvdpau-dev
nvidia-96 - NVIDIA binary Xorg driver, kernel module and VDPAU library
nvidia-96-dev - NVIDIA binary Xorg driver development files
nvidia-96-kernel-source - Transitional package for nvidia-glx-96-kernel-source
nvidia-current - NVIDIA binary Xorg driver, kernel module and VDPAU library
nvidia-current-dev - NVIDIA binary Xorg driver development files
nvidia-glx-173 - Transitional package for nvidia-glx-173
nvidia-glx-173-dev - Transitional package for nvidia-glx-173-dev
nvidia-glx-180 - Transitional package for nvidia-glx-185
nvidia-glx-180-dev - Transitional package for nvidia-glx-185-dev
nvidia-glx-185 - Transitional package for nvidia-glx-185
nvidia-glx-185-dev - Transitional package for nvidia-glx-185-dev
nvidia-glx-96 - Transitional package for nvidia-glx-96
nvidia-glx-96-dev - Transitional package for nvidia-glx-96-dev
nvidia-kernel-common - NVIDIA binary kernel module common files
ubuntu@ubuntu:~$ apt-cache search ppa
apparmor - User-space parser utility for AppArmor
apparmor-docs - Documentation for AppArmor
apparmor-utils - Utilities for controlling AppArmor
lbdb - The little brother's database for the mutt mail reader
libapparmor-dev - AppArmor development libraries and header files
libapparmor-perl - AppArmor library Perl bindings
libapparmor1 - changehat AppArmor library
libneon27 - An HTTP and WebDAV client library
libneon27-gnutls - An HTTP and WebDAV client library (GnuTLS enabled)
libxom-java - A new XML object model for Java
libxom-java-doc - Documentation for the libxom-java package
palo - Linux boot loader for parisc/hppa
pnm2ppa - PPM to PPA converter
texlive-science - TeX Live: Typesetting for natural and computer sciences
type-handling - dpkg architecture generation script
ubuntu@ubuntu:~$ apt-cache search vesa
grub-pc - GRand Unified Bootloader, version 2 (PC/BIOS version)
libxext-dev - X11 miscellaneous extensions library (development headers)
libxext6 - X11 miscellaneous extension library
libxext6-dbg - X11 miscellaneous extensions library (debug package)
xserver-xorg-video-vesa - X.Org X server -- VESA display driver
ubuntu@ubuntu:~$ apt-cache search nouveau
libdrm-nouveau1 - Userspace interface to nouveau-specific kernel DRM services -- runtime
libdrm-nouveau1-dbg - Userspace interface to nouveau-specific kernel DRM services -- debugging symbols
xserver-xorg-video-nouveau - X.Org X server -- Nouveau display driver (experimental)
ubuntu@ubuntu:~$
_________________________________________________________________
This is the Xorg.conf on the moment:
Xorg.conf:
Section "Screen"
   Identifier "Acer HQ19"
   DefaultDepth 24
EndSection
Section "Module"
   Load "glx"
EndSection
Section "Device"
   Identifier "Default Device"
   Driver "nvidia"
   Option "NoLogo" "True"
EndSection
#default screen I removed and put in the screen name , but doesn' t work.
___________________________________________________________
Till a few days ago I worked with this xorg.conf:
Section "Screen"
   Identifier "Default Screen"
   DefaultDepth 24
EndSection
Section "Module"
   Load "glx"
EndSection
Section "Device"
   Identifier "Default Device"
   Driver "nvidia"
   Option "NoLogo" "True"
EndSection
Last time I changed the xorg.conf with the failsafe file and it worked again, now it does not.
I now also edited the kernel, removing quite splash with " nomodeset" . Nothing!
Kernel is the newest as well, ends at .24
The story:
Two days ago, in the evening i just normal stopped, and in the morning it didn' t do anything anymore. The recovery mode even does not work. Everything I did last times, I did it all again and more, nothing works, The grub is the newest, 1Ubuntu7
There are a few weird things I find:
    * The Nvidia seems to been gone. only the common-directory was there.
    * The nvidia was gone and Nouveau is back! I did not and do not understand .....
Now using a Live USB, I can back into it, but:
    * I have removed video Nouveau
    * The Veza is off
    * Current Nvidia installled
    *But once I reboot everything is as it was earlier on. All changes DISiAPPEARED again.
Then I looked at the grub, which looks ok to me. I have the 1.98 1Ubuntu7
    * The terminal does NOT operate from the USB stick yhe command: mount/dev/sda1/mnt sudo "not
    * Similarly, then, sudo grub-install / dev / sda - root-directory = / mnt "says" unknown command "
What happens STARTING UP: : start, pause, image fade equally, without keys, I see then Grub here and can I get a kernel mode (the latest), and sometimes even heavy images, then flash an orange ubuntu color along and then stops the lot, flashing in root (in black) Evil, BUT so I can login. But not IN a nice interface. Any way. Ladies and gentlemen, thank you for the help Another important issue may be, someone suggested doing an update, to remove 2.6.32.21 kernel, which is no more also, Can that be the problem? Even through the live stick or through these kernel booted right? To be sure, the stick is made on Sept. 14.

Problemas de arranque en Linux

Fuente 16 DICIEMBRE 2009

Algunas de las opciones disponibles:
acpi=off

Esta opción desactiva la ACPI, corrige diversos problemas de arranque en varias máquinas. ACPI es responsable de supervisar la carga de la batería, ajuste la frecuencia del procesador y de muchas otras funciones importantes, por lo que se debería dejar para desactivar en último caso.

acpi=ht

(ht de “hyper-thread”). Hace que se desactiven todas las configuraciones ACPI excepto las que necesita un procesador hyper-threading. Lo que sea que causa el problema, aparentemente no es necesario para un procesador de este tipo.

acpi=noirq 

Esta es una versión más ligera de la opción “acpi = off” que, en lugar de deshabilitar por completo el soporte para ACPI, sólo desactiva la asignación dinámica de direcciones, que es la causa de la mayoría de los problemas relacionados con ACPI .

Esta opción corrige problemas en la detección de la tarjeta de red, tarjeta de sonido y tarjeta inalámbrica en varios laptops de Acer, y posiblemente otros fabricantes, así como con la placa base con chipset SiS, debido a errores en la asignación de direcciones de la BIOS .

Una observación importante es que incluso aunque corrija problemas en algunas tarjetas de sobremesa y laptops, esta opción plantea problemas para la detección de componentes y conflictos en otros, causando que no se detecte la tarjeta inalámbrica o periféricos USB. Se debería utilizar sólo como una manera de resolver los problemas, no como una opción de rutina.

noapic

La APIC es una característica utilizada en los micros modernos para asignar direcciones IRQ, evitando conflictos entre los dispositivos. Muchas computaras utilizan BIOS que contienen varios bugs, dando como resultado que algunos periféricos no son detectados por el sistema, por ejemplo la tarjeta de sonido o tarjeta de red.

El uso de esta opción resuelve el problema en muchos casos.

La mayoría de las veces la mejor manera de solucionar de forma definitiva este tipo de problemas esactualizar la BIOS de la placa base, con una versión actualizada se pueden solucionar los problemas directamente.

Muchos fabricantes, como Asus, ofrecen un buen soporte con respecto a esto, vale la pena comprobar si hay una actualización disponible para la tarjeta. Normalmente, la actualización de la BIOS se realiza mediante el uso de un disquete o CD-ROM grabado con una imagen descargada de la página del fabricante. La actualización de la BIOS es potencialmente peligrosa, así debemos asegurarnos de leer las instrucciones del fabricante y comprobar si el archivo descargado corresponde a nuestra placa.

nolapic

El LAPIC (local APCI) es una variante de APIC que se utiliza en las máquinas con los procesadores dual-core o quad-core. Como el “noapic”, el “nolapic” se utiliza para resolver problemas relacionados con el arranque o la detección de los periféricos. Aunque ambos pueden ser utilizados juntos, por lo general sólo se necesita uno.

nosmp

En máquinas con procesadores de doble núcleo, esta opción deshabilita el segundo núcleo, que resuelve muchos problemas de arranque. Naturalmente, sin un núcleo la potencia de la máquina va a ser inferior, pero sirve como una solución temporal hasta que encuentre una solución al problema, que puede ser una actualización de la BIOS, o simplemente, una versión actualizada de la distribución en uso.

pci=biosirq

Esta es otra opción que resuelve los problemas de detección de la tarjeta de red o de sonido en algunas máquinas. Hace que el sistema siga la configuración de las direcciones definidas por el BIOS, en lugar de utilizar el procedimiento normal de detección.

pci=bios

Otra opción para la compatibilidad, esta vez para evitar problemas con la placa base del controlador PCI. Aunque es raro, es necesario utilizarla completar el arranque, en algunos portátiles.

pci=nommconf

Los problemas con MMCONFIG pueden ser debidos a problemas en el núcleo o problemas en el BIOS, o una discrepancia en la interpretación de las especificaciones.

No es necesario en la mayoría de los casos pero puede resolver algunos problemas si la BIOS contiene bugs. Los kernels más modernos parece que son capaces de trabajar con una mala configuración MMCONFIG en la BIOS

La función que utiliza MMCONFIG añade otra forma de describir la configuración de los dispositivos PCI en el sistema operativo.

Utilizar pci=nommconf no puede causar ninguna diferencia notable en las características o el rendimiento.

pci=nomsi

Se utiliza para la instalación, si la máquina tiene un disco duro SATA y al iniciar la instalación no se reconoce el disco duro.

pnpbios=off

Desactiva el soporte para plug-and-play en BIOS de la placa base, dejando que el núcleo se encargue de la detección de todos los componentes. Esta es una opción que soluciona problemas de compatibilidad en algunas placas.

irqpoll

Esta opción cambia la forma en que el sistema detecta los dispositivos de la máquina, corrigiendo problemas en PCs y laptops recientes, especialmente cuando se utiliza conjuntamente con distribuciones antiguas, anteriores a 2008. Necesaria para que el adaptador inalámbrico funciona en algunos portátiles Acer con tarjetas Broadcom, resuelve los problemas con la tarjeta de sonido o tarjeta de red en diversos entornos y soluciona un problema relacionado con la detección de HD SATA en las tarjetas basadas en el chipset K8T890 (como la Asus A8V-E), entre otros. Esta opción causa pocos efectos secundarios en comparación con las otras.

reboot=b

Esta opción hace que sea usada una función alternativa para reiniciar el micro vía software, resolviendo en algunos casos que no se reinicie la máquina usando el comando “reboot”.

all-generic-ide

Esta opción aborda los problemas de compatibilidad con el controlador IDE o SATA de algunas placas base, sobre todo en placas con el chipset SiS 761GX/965L (para utilizar un HD SATA). Esta opción se debe utilizar en los casos en que el sistema no puede detectar el HD de la micro (impide acceder a los archivos, imposibilitando la instalación).

Al utilizar esta opción de arranque, el sistema utiliza un modo genérico para el acceso a los discos duros, que resuelve el problema en la mayoría de los casos.

Esta opción causa una reducción significativa en el rendimiento del sistema, por lo que debe usarse sólo cuando realmente sea necesario.

Una peculiaridad es que el sistema detecta el HD SATA como “/ dev / hde” y no “/ dev / sda” como sería habitual. A pesar de eso, la instalación del sistema transcurre de manera normal.

En algunas placas con chipset VIA puede que sea necesario combinarla con la opción “irqpoll”, solucionando también un problema con la asignación de direcciones.

La mayor parte del artículo es una traducción libre del original de Carlos Morimoto

Una guía de parámetros del Kernel aquí

Defrag With Raid Volumes

thedailyreviewer.com/server/view/defrag-raid-volumes