Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 17 FirstFirst 1234513 ... LastLast
Results 21 to 30 of 165
  1. #21
    Member
    Join Date
    Sep 2017
    Location
    ┼kersberga, Sweden
    Posts
    69
    Quote Originally Posted by chill View Post
    .... and adding the Jivelite start command to /etc/rc.conf makes it start automatically at boot.

    I haven't tackled the command line setup of wifi under this Ubuntu installation yet, and of course it's all running from a USB stick. So my targets now are to get the wifi working, then try all this again with a TinyCore base image running from flash memory (so will have to get my head around writing updated files back to permanent storage, as well as any differences in the steps that worked for Ubuntu), and then maybe see if I can make an image from that installation.
    Install the package that contains the command "nmcli" (for Debian it is network-manager) and use that. Dependencies such as dhcp client etc, should be resolved by any competent package manager.
    Synopsis for connection:
    nmcli dev wifi connect 'MYSSID' password XXXXXXXX
    You can also scan your network with:
    nmcli dev wifi

    Hope this helps
    2 Touch, 1 Picoreplayer 4.1.0 on RaspBerry 3B with 7" display
    LMS latest nightly on Ubuntu 18.04.1 on Intel Core2 Duo E4500 @ 2.20GHz, 2GB
    All wired

  2. #22
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    758
    Great stuff, thank you. I'll try that this evening.

  3. #23
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    2,485
    Quote Originally Posted by chill View Post
    Great stuff, thank you. I'll try that this evening.
    This might help

    https://www.techrepublic.com/article...tion-on-linux/

  4. #24
    Member
    Join Date
    Sep 2017
    Location
    ┼kersberga, Sweden
    Posts
    69
    Quote Originally Posted by chill View Post
    ... then try all this again with a TinyCore base image running from flash memory (so will have to get my head around writing updated files back to permanent storage, as well as any differences in the steps that worked for Ubuntu), and then maybe see if I can make an image from that installation.
    The network-manager/nmcli is probably the easiest way to solve your issue when you have Ubuntu but for TinyCore, wicd is probably a better solution (ie, supported). See
    http://wiki.tinycorelinux.net/wiki:setting_up_wifi
    2 Touch, 1 Picoreplayer 4.1.0 on RaspBerry 3B with 7" display
    LMS latest nightly on Ubuntu 18.04.1 on Intel Core2 Duo E4500 @ 2.20GHz, 2GB
    All wired

  5. #25
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    2,485
    So.. using the base server OS I have just tried following this

    https://askubuntu.com/questions/5211...u-server-14-04

    But I had to keep installing stuff and got confused.

    So gave up and tried the link I posted above

    https://www.techrepublic.com/article...tion-on-linux/

    The download took forever and then systemctl would not start so I rebooted and tried again but it would not work.

    Then found that wpa_supplicant was not installed so did a wget for that

    https://packages.ubuntu.com/trusty/i...icant/download

    installed, rebooted and followed these instructions

    https://www.linuxbabe.com/command-li...wpa-supplicant

    That got me as far as this

    Code:
    joggler@joggler:~$ wpa_passphrase PLUSNET-P7HKNN cebbabf676 | sudo tee /etc/wpa_supplicant.conf
    network={
            ssid="PLUSNET-******"
            #psk="***********"
            psk=4014411e54b751894f91b7fde225a4351fca2e9d4bb9db8d0e1a25ed37b3dc44
    }
    joggler@joggler:~$ sudo wpa_supplicant -c /etc/wpa_supplicant.conf -i wlp3s0
    Successfully initialized wpa_supplicant
    nl80211: 'nl80211' generic netlink not found
    Failed to initialize driver 'nl80211'
    and

    Code:
    joggler@joggler:~$ iwconfig
    lo        no wireless extensions.
    
    wlan0     Ralink STA  ESSID:"11n-AP"  Nickname:"RT2870STA"
              Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated
              Bit Rate:1 Mb/s
              RTS thr:off   Fragment thr:off
              Link Quality=10/100  Signal level:0 dBm  Noise level:0 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0
    
    eth0      no wireless extensions.
    
    joggler@joggler:~$

    It looks like I need a driver, but I'm hungry now and I'm going for lunch.

    I'll make a fresh "base" image and restart.

    ronnie
    Last edited by Man in a van; 2019-01-18 at 07:23.

  6. #26
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    2,485
    Well I have started with another fresh image of the Base system.

    I decided to begin with a minimal desktop (hopefully it will make the wireless set-up easier).

    Code:
    sudo apt-get update
    sudo apt-get install --no-install-recommends lubuntu-desktop
    It's been installing for a while now and I have been browsing around on the thread at the O2 joggler forum and found this



    User avatar
    BuZz
    Site Admin
    Posts: 1446
    Joined: Fri Mar 04, 2011 1:15 am

    Re: Ubuntu / Xubuntu for the O2 Joggler.

    Post by BuZz ╗ Tue Feb 07, 2017 1:48 am
    Thanks.

    The base image doesn't require xserver/emgd blob, but does include them (as it's designed to you can install what you want etc including desktop)


    Then looking about xserver blobs I found this post

    https://askubuntu.com/questions/9370...server-started

    That will do for another day I thought.

    Then the install failed with a segmentation fault so I'm going to start again tomorrow

    It's almost time for a "facepalm"

    some rugger on't tv shortly

  7. #27
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    758
    Quote Originally Posted by Man in a van View Post
    Then looking about xserver blobs I found this post

    https://askubuntu.com/questions/9370...server-started
    Some useful tips in there.

    I've been through the process of starting again from a base/server image several times this evening, and I've kept a log of the steps needed to get JiveLite going under X.

    So I'm pretty sure that the following will get a working system up and running, starting from the Base/Server Ext4 image here. These steps can be entered from a terminal (keyboard and USB stick connected to the Joggler through a USB hub), or through an SSH shell (find the IP address with 'ifconfig -a' from the terminal). In both cases the username and password are both 'joggler'. If using an SSH shell then those commands can be pasted in blocks of multiple commands, to save doing them one by one.

    Code:
    sudo apt-get update
    
    sudo apt-get install  git-core libluajit-5.1-dev libsdl1.2-dev libsdl-ttf2.0-dev libsdl-gfx1.2-dev libsdl-image1.2-dev libexpat1-dev
    
    cd
    mkdir luajit
    cd luajit
    git clone http://luajit.org/git/luajit-2.0.git
    cd luajit-2.0
    make
    sudo make install
    sudo ldconfig
    
    cd
    git clone https://github.com/ralph-irving/jivelite.git
    cd jivelite
    sudo make PREFIX=/usr/local
    
    sudo apt install xinit
    At that point it's worth doing a reboot (otherwise the screen brightness in Jivelite isn't right for some reason).

    Not needed to get JiveLite running, but probably a useful tool (note the hyphen in the package name and the underscore in the executable):
    Code:
    sudo apt-get install xinput-calibrator
    sudo xinit xinput_calibrator
    Start JiveLite with:
    Code:
    sudo xinit /home/joggler/jivelite/bin/jivelite

    I'm not quite there with the wifi though. First of all, load a minimal version of network-manager and start it:
    Code:
    sudo apt-get install --no-install-recommends network-manager 
    
    sudo start network-manager
    Check that it's working by scanning for wifi networks

    Code:
    nmcli dev wifi
    Then connect to your chosen network:
    Code:
    sudo nmcli dev wifi connect MYSSID password XXXXXXXX
    In my case this *appears* to work, and 'ifconfig -a' tells me that the wlan interface has now got an IP address, which I can use to SSH into the Joggler. But for some reason, if I remove the network cable then the wifi connection stops working, which rather defeats the purpose!

    Still lots of loose ends:
    - These steps won't get the Joggler to boot up into Jivelite
    - The 'Quit' option on the Jivelite home screen dumps you out of Jivelite, and in my case leaves a terminal screen with some messy video artefacts along the bottom third of the screen. I think that option should be changed to restart JiveLite, or just be removed altogether.
    - The cursor is still present for ~15 seconds before disappearing.
    Last edited by chill; 2019-01-18 at 17:09.

  8. #28
    Senior Member chill's Avatar
    Join Date
    Mar 2007
    Posts
    758
    Quote Originally Posted by Man in a van View Post

    Then the install failed with a segmentation fault so I'm going to start again tomorrow
    Are you installing to the flash memory? Did you perhaps run out of space? The flash is 1GB, and the base/server image expands to ~2GB, so perhaps your 'minimal desktop' is also too big for the flash storage.

  9. #29
    Senior Member
    Join Date
    Jan 2011
    Location
    Staffordshire. UK
    Posts
    2,485
    Quote Originally Posted by chill View Post
    Are you installing to the flash memory? Did you perhaps run out of space? The flash is 1GB, and the base/server image expands to ~2GB, so perhaps your 'minimal desktop' is also too big for the flash storage.

    No, 8gb usb stick, i had no warning of running out of space (I did the other day, on another attempt). I'm going to use gparted to expand the root partition on all future trials.

    Ronnie

  10. #30
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,054
    Quote Originally Posted by chill View Post
    - The 'Quit' option on the Jivelite home screen dumps you out of Jivelite, and in my case leaves a terminal screen with some messy video artefacts along the bottom third of the screen. I think that option should be changed to restart JiveLite, or just be removed altogether.
    It's easier to just start jivelite from a script which relaunches jivelite on exit.
    You can hide the Quit option, hold the Quit menu item until a popup window displays, then choose Hide from Home Menu.

    Code:
    #!/bin/bash
    export JIVE_NOCURSOR=1
    
    while true; do
        /usr/local/bin/jivelite
        sleep 1
    done
    Quote Originally Posted by chill View Post
    - The cursor is still present for ~15 seconds before disappearing.
    export JIVE_NOCURSOR=1

    Before you start jivelite will prevent the cursor displaying at all.
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 1-UE Radio
    Squeezebox client builds donations always appreciated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •