Hi there
ive been using bodhi and peppermint for a while, but would like to try out the new 2.0 portheus!
I tried the old version but couldnt get i to save changes, so i dropped it.
ive installed 2.0 unto a usb using Unetbootin. but the mouse, and maybe the keyboard, doesnt load on boot? the curser is just in the center of the screen, frosen
nothing possible.
ive tried all options kde, lxde and so on.
im using an old HPpaviliondv9000, and i havent tried this problem before, with other distros.
what to do?
kind regards Gnimmelf
mouse not woorking (solved)
-
- White ninja
- Posts: 7
- Joined: 21 Feb 2013, 17:50
- Distribution: bodhi linux
- Location: denmark
mouse not woorking (solved)
Last edited by gnimmelf on 23 Feb 2013, 20:29, edited 1 time in total.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: mouse not woorking
@gnimmelf
i think you are booting from kernel different than porteus one.
please boot to text mode -> login as root -> run 'uname -r' -> run 'ls /lib/modules' and check if strings matches.
if yes then please run 'psinfo' command and save generated report on your stick -> boot to other OS -> upload report to pastebin.com and post URL here for a review.
if strings does not match then unetbootin did installation incorrectly and i would suggest you using our native installer.
instructions are here:
link
i think you are booting from kernel different than porteus one.
please boot to text mode -> login as root -> run 'uname -r' -> run 'ls /lib/modules' and check if strings matches.
if yes then please run 'psinfo' command and save generated report on your stick -> boot to other OS -> upload report to pastebin.com and post URL here for a review.
if strings does not match then unetbootin did installation incorrectly and i would suggest you using our native installer.
instructions are here:
link
Please add [Solved] to your thread title if the solution was found.
-
- White ninja
- Posts: 7
- Joined: 21 Feb 2013, 17:50
- Distribution: bodhi linux
- Location: denmark
Re: mouse not woorking
hi there
tried to use native installer, that didnt help, same problem. mouse not responding/working.
the other process
i think i will try on my desktop. maybe its an error in my laptop (the dvd drive doesnt work either)
to bad though..... it would have been nice to try on the laptop
thanks for trying to help though
kind regards gnimmelf
tried to use native installer, that didnt help, same problem. mouse not responding/working.
the other process
was to complicated for me. console responded with "no such command" or something in that maner.please boot to text mode -> login as root -> run 'uname -r' -> run 'ls /lib/modules' and check if strings matches
i think i will try on my desktop. maybe its an error in my laptop (the dvd drive doesnt work either)
to bad though..... it would have been nice to try on the laptop
thanks for trying to help though
kind regards gnimmelf
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: mouse not woorking
Just try the command this way:
Code: Select all
root@porteus:~# uname -r
3.4.4-porteus
root@porteus:~#
Prendre son temps, profiter de celui qui passe.
-
- White ninja
- Posts: 7
- Joined: 21 Feb 2013, 17:50
- Distribution: bodhi linux
- Location: denmark
Re: mouse not woorking
ok tried it
uname-r gave "3.7.8 - porteus"
and
ls /lib/modules gave "3.7.1 - porteus"
is this usefull?
kindly gnimmelf
uname-r gave "3.7.8 - porteus"
and
ls /lib/modules gave "3.7.1 - porteus"
is this usefull?
kindly gnimmelf
- Ahau
- King of Docs
- Posts: 1331
- Joined: 28 Dec 2010, 15:18
- Distribution: LXDE & Xfce 32/64-bit
- Location: USA
Re: mouse not woorking
Hi gnimmelf,
yes, this is helpful. Since the two versions do not match, it shows that you are booting the correct kernel for Porteus 2.0 final, but the data that is being used with it is from Porteus 2.0 RC1. You must have another installation of Porteus floating around on this computer or flash drive somewhere (an earlier install through unetbootin, perhaps?).
Whenever porteus starts up, it searches for the data to load and it starts with the lower numbered drives/partitions and works up.
The easiest solution for you would be to delete the other porteus installation. Then, the new data will be found and used, and you'll be all set.
It is perfectly possible to have two installations of Porteus on the same device, but you need to update your bootloader config file to use the "from=" cheatcode so that Porteus knows where the correct data is to use located. You should have a line that reads something like "append initrd=initrd.xz changes=/porteus". To this, you would add, "from=/mnt/sdXY/path/to/porteus", where "sdXY" is the device and partition where your Porteus 2.0 final data is installed, and /path/to/ is the path to the folder "porteus" inside which you'll have the folders "base" "modules" "optional" "rootcopy" and so forth. An example from my boot config: "from=/mnt/sdb2/P64/porteus"
yes, this is helpful. Since the two versions do not match, it shows that you are booting the correct kernel for Porteus 2.0 final, but the data that is being used with it is from Porteus 2.0 RC1. You must have another installation of Porteus floating around on this computer or flash drive somewhere (an earlier install through unetbootin, perhaps?).
Whenever porteus starts up, it searches for the data to load and it starts with the lower numbered drives/partitions and works up.
The easiest solution for you would be to delete the other porteus installation. Then, the new data will be found and used, and you'll be all set.
It is perfectly possible to have two installations of Porteus on the same device, but you need to update your bootloader config file to use the "from=" cheatcode so that Porteus knows where the correct data is to use located. You should have a line that reads something like "append initrd=initrd.xz changes=/porteus". To this, you would add, "from=/mnt/sdXY/path/to/porteus", where "sdXY" is the device and partition where your Porteus 2.0 final data is installed, and /path/to/ is the path to the folder "porteus" inside which you'll have the folders "base" "modules" "optional" "rootcopy" and so forth. An example from my boot config: "from=/mnt/sdb2/P64/porteus"
Please take a look at our online documentation, here. Suggestions are welcome!
-
- White ninja
- Posts: 7
- Joined: 21 Feb 2013, 17:50
- Distribution: bodhi linux
- Location: denmark
Re: mouse not woorking
thanks Worked like a charm
now im up and running and fast to
a little problem arised though.
im used to use this comand to decide witch distro is going to own the bootloader.
now i lost my boddhi install, and porteus owns the loader. how can i get the loader to read both distros? so i can choose between them?
kindly gnimmelf
now im up and running and fast to
a little problem arised though.
im used to use this comand
Code: Select all
sudo dpkg-reconfigure grub-pc
now i lost my boddhi install, and porteus owns the loader. how can i get the loader to read both distros? so i can choose between them?
kindly gnimmelf
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: mouse not woorking (solved)
Are you able to boot bodhi now? Is this still an installation from unetbootin?
A) If it is an installation with unetbootin on your windows disk you may try easybcd:
http://neosmart.net/EasyBCD/
http://old.slax.org/forum.php?action=vi ... ntID=48540
For a usb or hdd install:
Here is an example of menu.lst for bodhi, according to the following link, post 6:
http://forums.bodhilinux.com/index.php? ... o-menulst/
However it has to be modified according to your installation. Please find 1) the right linux entry for vmlinuz and initrd.img, 2) blkid and 3) the structure of your usb key or hdd (as examples here are some of my data, yours will be different):
1) look in the /boot of the partition on which is bodhi (fdisk -l, that follows will give the structure of your disk)
2) use command blkid:
3)
A) If it is an installation with unetbootin on your windows disk you may try easybcd:
http://neosmart.net/EasyBCD/
http://old.slax.org/forum.php?action=vi ... ntID=48540
For a usb or hdd install:
Here is an example of menu.lst for bodhi, according to the following link, post 6:
http://forums.bodhilinux.com/index.php? ... o-menulst/
Code: Select all
title Bodhi Linux
uuid d9416d3d-60bc-4d3e-bba7-bc4f7bc7b974
kernel /boot/vmlinuz-2.6.35-28-generic root=UUID=d9416d3d-60bc-4d3e-bba7-bc4f7bc7b974 ro quiet splash
initrd /boot/initrd.img-2.6.35-28-generic
1) look in the /boot of the partition on which is bodhi (fdisk -l, that follows will give the structure of your disk)
2) use command blkid:
Code: Select all
root@porteus:~# blkid
/dev/sda1: LABEL="System" UUID="289C7CB19C7C7AE0" TYPE="ntfs"
/dev/sda2: LABEL="TI30846800A" UUID="DE62838A628365DD" TYPE="ntfs"
/dev/sda5: LABEL="porteus-slax" UUID="50edcee1-f9da-40ea-a91d-f969a784d748" TYPE="ext2"
/dev/sda6: LABEL="crunchbang" UUID="3f3e5c6f-ddb4-4134-a886-f6cdf0e082eb" TYPE="ext4"
...
Code: Select all
root@porteus:~# fdisk -l
Disk /dev/sda: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf6c5ce6c
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 3074047 1536000 27 Hidden NTFS WinRE
/dev/sda2 3074048 117442559 57184256 7 HPFS/NTFS/exFAT
/dev/sda3 117442560 250068991 66313216 5 Extended
/dev/sda5 117444608 159387647 20971520 83 Linux
/dev/sda6 159389696 220977151 30793728 83 Linux
/dev/sda7 220979200 246145023 12582912 83 Linux
/dev/sda8 246147072 250068991 1960960 82 Linux swap
root@porteus:~#
Prendre son temps, profiter de celui qui passe.