Linux - pitanja i odgovori

  Cek mint si instalirao...

pa zasto to onda tako radis???

Lijepo odes u desktop sucelje... malo gledas tamo po izbornicima i nadjes nesto sto izgleda kao kartica, program se zove Hardware info ili nesto tako i odaberes ACTIVATe na NVIDIA proprietary drivers... I to je to... ono downloada, stavi module...

A to sto ti pokusavas nece ici, cisto jer julia ima drugacije headere od onih kompajlanih, pa nikako ne moze pokrenuti modul kad treba...

  driver je .sh

to mora raditi unutar terminala... ali je lakše ono sto sam ja rekao...

Onda ili pratiš EPove upute ili, kako sam već rekao, u terminalu odeš u direktorij gdje si skinuo drivere pa upišeš:

su

chmod +x imefajla.run

./imefajla.run

  ERROR: nvidia-installer must be run as root  

Jesi li upisao su?

su te logira kao roota. Kad upises su pitat ce te za admin sifru.

lakse ti je

sudo sh ./imefajla.run

trazit ce te pass i sve... i to napravi... to je to...

TAko sam i radio...:)

  PA tu sam i išao i piše mi  Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/e/eglibc/libc6-dev_2.11.1-0ubuntu7.2_i386.deb 404 Not Found [IP: 91.189.92.171 80]....:)

Neda mi se sad s tim petljat..probat ću još hehe danas kad se probudim....ak ne onda tv ide..može?..;))

probaj promijenit fstab - umjesto /dev/sdxy stavi diskove po uuid-u...

znači , da izgleda ovako nekako:

#Entry for /dev/sda4 :
UUID=e7c7481d-cc86-42ca-be76-b6a498c005f9    /    ext4    errors=remount-ro    0    1
#Entry for /dev/sda2 :
UUID=4de499e3-9692-4b70-b891-dbc76b643976    /home    ext4    defaults    0    2
#Entry for /dev/sda1 :
UUID=92cf299f-45a6-4e65-9b88-f1718dc7ec16    none    swap    sw    0    0

a ne :

/dev/sda1 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 0 1
/dev/sda2 /home ext4 defaults 0 1

što znače ovi brojevi pored particija "0 1", "0 2", itd.?

ovo je moj trenutni fstab

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda1 during installation
UUID=385ecae6-bd34-41c3-a524-974b8cd6d17f /               ext3    errors=remount-ro 0       1
# swap was on /dev/sda2 during installation
UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
proc    /proc    proc    nodev,noexec,nosuid    0    0
/dev/sdb2    /    ext4    rw,errors=remount-ro    0    0
/dev/sdb1    swap    swap    sw    0    0

uspio sam postići da mi prilikom svakog boota učita swap particiju tako da sam u /etc/fstab swap particiji pridružio njezin UUID. hvala svima koji su pomogli!

napravio sam dual boot sa sabayonom, s tim da sam sabayon instalirao naknadno i nisam instalirao ponovno grub, već sam iz minta napravio update gruba. problem je što imam više diskova, pa mi niti sabayon neće bootati, onda moram ručno upisivati "/dev/sdx3" i pogađati koji je trenutni "x"kad mi javi grešku pri bootanju i kad pogodim se boota.

sad bi ja pridružio UUID particije sabayona u grubu kad bih znao gdje. pokušao sam u /etc/grub.conf i /boot/grub/grub.conf, ali oba fajla su prazna.

ovo wiki kaže za sustave s više diskova

Note: If your system has more than one hard drive, the installer will default to using UUID rather than the sdx naming scheme, for consistent device mapping. Utilizing UUID has several advantages and may also be preferred to avoid issues if hard disks are added to the system in the future. Due to active developments in the kernel and also udev, the ordering in which drivers for storage controllers are loaded may change randomly, yielding an unbootable system/kernel panic. Nearly every motherboard has several controllers (onboard SATA, onboard IDE), and due to the aforementioned development updates, /dev/sda may become /dev/sdb on the next reboot. (See this wiki article for more information on persistent block device naming. )

promijeniš sadržaj file-a /boot/grub/grub.cfg

https://wiki.archlinux.org/index.php/GRUB2#Combining_the_use_of_UUID.27s_and_basic_scripting 

If you like the idea of using UUID's to avoid unreliable bios mappings or are struggling with grub syntax, here is an example boot menu item that uses UUID's and a small script to direct grub to the proper disk partitions for your system. All you need to do is replace the UUID's in the sample with the correct UUID's for your system. (The example applies to a system with a boot and root partition. You will obviously need to modify the grub configuration if you have additional partitions.)

menuentry "Arch Linux 64" {
set uuid_grub_boot=ece0448f-bb08-486d-9864-ac3271bd8d07 #Enter the UUID of your boot partition (this is where grub and your kernel reside)
set uuid_os_root=c55da16f-e2af-4603-9e0b-03f5f565ec4a #Enter the UUID of the partition containing the root partition of your Arch Linux installation.
#(Note: this may be the same as your boot partition)
search --no-floppy --fs-uuid $uuid_os_root --set=root #Here we set the grub "root" variable by locating the uuid of the root partition identified above
search --no-floppy --fs-uuid $uuid_grub_boot --set=grub_boot #Here we set a custom variable grub_boot by locating the uuid of the boot partition identified above
#Here's the magic. We test to see if the boot and root partitions have the same UUID. If they do we append /boot to the $grub_boot variable. For ex. (hd0,1) becomes (hd0,1)/boot.
if [ $uuid_grub_boot == $uuid_os_root ] ; then
set grub_boot=$grub_boot/boot
fi
# $grub_boot now points to the correct location, so the following will properly find the kernel and initrd
linux ($grub_boot)/vmlinuz26 root=/dev/disk/by-uuid/$uuid_os_root ro
initrd ($grub_boot)/kernel26.img
}