tomlohave
Forum Replies Created
-
AuthorPosts
-
Hello,
It can’t work because you are using a special version to test.
Please reinstall with the iso downloaded from http://download.geexbox.org/test/x86-64/
then once ready, from a (remote or not) shell, do :
opkg install http://download.geexbox.org/test/x86-64/xf86-video-nvidia_370.28-3_x86_64.opk
It will install the nvidia drivers compiled for this new kernelplease post what you can see on the screen once you have done this command
then rebootCheers !
you can test it here :
http://download.geexbox.org/test/x86-64/
but upload is in progress
(for xf86-video-nvidia and geexbox-devel)
ETL : 1h25min
(yes I know, small speed …..)
How are you testing this ? usb key ? plain install ?
I just found a new bug for usb key, it should be fixed (persistent file was not taken into account)
I can not myself test nvidia kernel module cause I have no more such device …Cheers !
Hi,
the build with the new kernel is quite finished.
Do you have some time to test it ? if Yes, I can upload it.Looking at your lsmod results, nouveau module should not be loaded …
(it should be blacklisted)Hi Skelos.
I have a version of rtorrent without the need of screen. Did you have time to test it ?
Cheers !
Hi Skelos
-> size = 0xF0000000
it seems quite good : 4GB
But Rudi is better than me for thisHi,
Can you post the results of command :
lsmodIt seems the driver is not loaded by xorg at all.
I’m working on a new kernel with a more recent version of nvidia drivers.
I will post a pre compiled version soon.Hey,
We are happy is you use it and if you love it. Thanks to you ?
About your comments :
1) Rudi or I can have a look about the slide show and can try to package it. (I didn’t look for the moment)
2) ffmpeg can do that. I already used it for this purpose. Off course a script that does it is more elegant than doing it by hands. Not sure I will add time to package/create that.
3) Never tested this.
4) I don’t use weather add-on so I can’t help. @rudi ?
5) I see what you are talking about. I use a scrapper only since few days. But right now, everything seems to work well.Hello,
Version 3.1 is quite old. Can you try to switch to devel ?
binaries are here : http://download.geexbox.org/snapshots/
uncompress the img.xz file and use a tool like win32diskimager if you are on windows.I suspect the same problem on devel.
Just connect remotely, and edit /etc/opkg/opkg.conf
the line that starts with “src snapshots http://…..” is maybe incorrect
the good one issrc snapshots http://download.geexbox.org/snapshots/geexbox-kodi-i386-generic/latest/binaries.i386/packages/then do
opkg updateAugust 1, 2016 at 15:08 in reply to: Old link for snapshots does 404 where do get the latest img? #10840No problem to add something in this thread, only if it ‘s completely different, open a new one.
July 31, 2016 at 16:02 in reply to: Old link for snapshots does 404 where do get the latest img? #10838Hi Peter,
that’s not a stupid question; download area for snapshots is : http://download.geexbox.org/snapshots/
for all platforms (kodi or xbmc, it depends … )
For development snapshots, a copy of make-sdcard is provided with each tarball.
I suppose you refer to that in documentation. This file is present.
If you have no linux pc to use it, you can use the *********.img.xz file with win32diskimager or an utility like that on windows (https://sourceforge.net/p/win32diskimager/wiki/Home/)
but don’t forget to uncompress the file first (xz extension)Speaking about the corruption, that’s because you have upgraded from the gui ?
We have done an important update last days, switching from eglibc to glibc, so all packages were upgraded. We have tested locally the switch without problem but ….
Before doing a fresh install, save the content of your sdcard, or (maybe better) burn a new sd-card, restore the ip you want for geexbox, re-enable ftp access (under gui, no problem)
Then you should be able to restore your data from previous install of kodi, copying your saved/old /root/.kodi directory to the new oneok, so if live boot works correctly, try to connect to geexbox remotly (see http://www.geexbox.org/geexbox-advanced-configuration-login-and-administration/ (telnet part) )
and please execute this command line :
cat /proc/mountsThen I can send you what to do exactly to install it
Ok that’s because we boot without the ‘nocache’ option.
Once you boot, send me the results of command line :
cat /proc/mountsedit : found some problem with this method, looking at it …
Hello,
Maybe there is an extra option in bios ?Anyway, if you keyboard works once the system started, you can always install it.
just connect remotely (see documentation) or stop kodi/xbmc (depending of the version you boot with)
then umount the device you want to install on it and start installator
here is what I do ( on a vbox) :thomas@servA:~$ telnet 192.168.1.36 Trying 192.168.1.36... Connected to 192.168.1.36. Escape character is '^]'. geexbox login: root Password: BusyBox v1.24.1 (2016-07-21 16:21:34 CEST) built-in shell (ash) Enter 'help' for a list of built-in commands. root@geexbox:~# cat /proc/mounts tmpfs /.root tmpfs rw,relatime 0 0 /dev/loop0 /.squashfs squashfs ro,relatime 0 0 none /.data tmpfs rw,relatime 0 0 none / aufs rw,relatime,si=20dcd6eb 0 0 tmpfs /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 devtmpfs /dev devtmpfs rw,nosuid,size=1796768k,nr_inodes=209758,mode=755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0 tmpfs /tmp tmpfs rw 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 configfs /sys/kernel/config configfs rw,relatime 0 0 /dev/sda1 /mnt/SATA 40Disk 40#1 40GeeXboX 40(0) ext4 rw,relatime,data=ordered 0 0 /dev/sr0 /media/GEEXBOX iso9660 ro,nosuid,nodev,relatime,uid=0,gid=0,iocharset=utf8,mode=0400,dmode=0500 0 0 root@geexbox:~# umount /dev/sda1 root@geexbox:~# installatorHere I choose to umount /dev/sda1, to install geexbox on it
Sure, let’s continue to talk about this via P.M.
You can find my private email looking here : http://www.geexbox.org/the-team/
as already said, the video card is the most problematic one I think …. -
AuthorPosts