Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Cryoniq

Pages: [1] 2
1
Installation issues / Re: Wireless no longer works
« on: June 08, 2007, 09:00:53 pm »
I had the same problem and I resolved it with reinstalling KnetworkManager again, since LMCE install fracks that part up.. Problem is, if only having a wireless in box, the whole install fracks up majorly.

2
Submitted this to bug report, but bringing it up here also.

I tried installing LMCE 1.1 Beta 2 with just a Wireless NIC in the box. Had it setup via Knetwork manager for WPA-TKIP and everything was working flawlessly. I figured I maybe only needed 1 NIC and skip the wired ethernet instead. Thus was my thought that LinuxMCE would set it up as ath0 and ath0:0.

Problem is, during install Knetworkmanager is screwed up (which I resolved the other time by reinstalling it after setup) and even if using the cache cd and packages cd so no downloads would be needed, the install still tried download something with security in the URL. This failed of course because it was after Knetworkmanager been pushed out. The install however continued after telling unable to resolve hos for 15 minutes and told me to reboot. So I did...

But.. upon reboot, console bootup screen would start blinking between trying to samba and connect to SQL server. And.. so it went on.. in a loop.. and wouldn't let go of it all. I tried to switch to another console and check network settings, thinking local host might been screwed up as well, but it wouldn't let me. The install clearly was a failure of major disaster.

Anyone might have any suggestions about this, or experienced the same and resolved it, but as it seem, Knetworkmanager or something it depends on have to be left alone for wireless NIC setups.

3
Hi all,

I've got Linux MCE 1.1 beta 2 set up. It's recognizing my other PC's and indexing my media files. However, as soon as I try to play a movie file, I hear sound but get no image (black screen). If I right-click the cursor shows for a split second but I don't get the Linux MCE user interface. So I'm unable to stop it from playing the file and go back to the main menu. This problem (of being unable to stop and go back) also occurs when I listen to music.

I'm suspecting it might have something to do with my videocard settings. I'm using an Nvidia 7600GS. Linux MCE doesn't seem to complain about my drivers. I'm able to run the video tests. (The spinning cube with composite and masking works fine windowed and fullscreen.)

Anyone have a clue what this problem might be?

Have you installed all codecs needed to play the media files? The restricted ones that is.

4
Installation issues / Re: Ati Radeon 9800 issues
« on: May 30, 2007, 02:09:02 pm »

Thanx, man... It is very much appreciated...

I, However, got so sick and tired of that Ati card (have had too much time consuming issues before) that I went and bought me a Nvidia card...


I can totaly understand that. In fact, my next card will be Nvidia. But I have to say that this ATI 9800 Pro served me well. It is a very good card, even if the support of drivers aren't good..  Hopefully ATI will sober up and start hang on to Linux a lot better.

5

I wonder what will happen if I alter it to?
eth0,192.168.1.151,255.255.255.0|ath0,dhcp


I don't think that will do much. Don't you really want to change the ath0/eth0 around so that eth0(your wired card) gets an external address from your IP providers DHCP and ath0(internal wireless) is fixed to an internal address.

Are you just trying to operate this as a standalone hybrid? If so, the I would pull the wireless card/adapter out and reconfigure with single wired network card. From memory (with Pluto, not linuxMCE but probably hasn't changed) the setup will allocate two interfaces on the one card.

Do you intend to have an internal network attached to your Core?

I intend to have media streamed from file server connected to the wireless router on other internal side of the place to the core/media over the 108 mbps wireless card ath0. And then plugin in the wired card eth0 to the second 100 mbps full duplex plugg going to the external and access to the internet (since it is that interface that will RSS auto download TV shows through bittorrent during nights ;P and store temporarily on the cores storage area).

6
You must login in Web Admin with a Master User (can modify configuration)( see if u're user is Master or not in WIzard -> Basic Info -> Users) to be able to modify your network settings from Advanced -> Network -> Network Settings

Only one user in system which have:  Master User (can modify configuration)? *ENABLED*

So that is not the problem either. =/

7
Cryoniq--

What does that page contain in your setup?  Does the line "Number of network adapters: 2" appear?  Does it list both adapters and their current settings (i.e. DHCP or Static IP info)?

I attached a screen shot of the configuration page as it looks in my setup.

"Number of network adapters: 2" is there.
Both adapters are listed and their current settings:
ath0 is set to DHCP, areas below are empty. Guess those are not filled in since it is DHCP on the interface.
eth0 is set to static IP 192.168.1.151, subnet 255.255.255.0

DHCP Server on Core is: Disabled.

I enabled the DHCP Server on Core just to see if that button showed up, and it didn't. =/

Edit:
Hmm I think I might found something here..

Under: Automation > Device Status there is a list over all devices and their status.
On one line it says:
CORE             192.168.1.151 

If one click on CORE a page comes up and in that page there is a text box left of the heading "Network interfaces". In that box is the following:
ath0,dhcp|eth0,192.168.1.151,255.255.255.0

I wonder what will happen if I alter it to?
eth0,192.168.1.151,255.255.255.0|ath0,dhcp

My thinking is that the order of those two interfaces in that line determine the order of the interfaces, this making eth #1 and ath #2 instead.

Any knowledge about this? :)



8
Installation issues / Re: Ati Radeon 9800 issues
« on: May 29, 2007, 04:22:32 am »
I somehow managed to get LinuxMCE 1.1 beta running on Kubuntu 7.04 Feisty. But there are performance issues and the installation didn't go without problems. (During installation LinuxMCE decided to change the network settings to 192.168.0.1 even though I specified a static IP address and told it not to become my DHCP server.)

This is my hardware setup:

P4 2.8Ghz
Ati Radeon 9800
 + flatpanel on CRT
 + PAL television on SVIDEO
Hauppauge PVR 250
 + remote

At the moment I can't seem to get my Radeon 9800 to work properly. Before installing Linux MCE I got the fglrx drivers running under Kubuntu with a dual head setup. (But without proper hardware acceleration.) But the fglrx drivers don't seem to work well with LinuxMCE. I was able to get it running with the drivers that LinuxMCE configured for me automatically. (Is that the default Ati driver??) But performance is unacceptably bad.

Can anyone share how to set up LinuxMCE with an Ati radeon (or similar) card properly?

Here is my xorg.conf for box with ATI Radeon 9800 Pro. Maybe it might help out a bitif you take out the parts needed from it. You might probably need to change screen/monitor settings if it works to fit your sync and resolution. I am using the open drivers for my ATI card. Also, this config is to have the card use direct rendering. And it isn't used for a LMCE box but a desktop with Beryl, thus the use of direct rendering (which makes some 2d not so tough):

Section "Module"
    Load        "dbe"     # Double buffer extension
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection
 
    Load       "freetype"
    Load       "dri"
    Load       "glx"

#   Load       "drm"
EndSection
 
Section "Files"
 
# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
 
#    RgbPath   "/usr/share/X11/rgb"
 
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#
 
    FontPath   "/usr/share/fonts/misc/"
#    FontPath   "/usr/share/fonts/TTF/"
#    FontPath   "/usr/share/fonts/OTF"
#    FontPath   "/usr/share/fonts/Type1/"
#    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/local/"
#    FontPath   "/usr/lib/X11/fonts/misc/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/lib/X11/fonts/Type1/"
#    FontPath   "/usr/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/lib/X11/fonts/freefont/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/100dpi/"
 
# The module search path.  The default path is shown here.
 
#    ModulePath "/usr/lib/modules"
 
EndSection
 
# **********************************************************************
# Server flags section.
# **********************************************************************
 
Section "ServerFlags"
 
# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
 
#    Option "NoTrapSignals"
 
# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.
 
#    Option "DontVTSwitch"
 
# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
 
#    Option "DontZap"
 
# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.
 
#    Option "Dont Zoom"
 
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
 
#    Option "DisableVidModeExtension"
 
# Uncomment this to enable the use of a non-local xvidtune client.
 
#    Option "AllowNonLocalXvidtune"
 
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
 
#    Option "DisableModInDev"
 
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
 
#    Option "AllowNonLocalModInDev"
 
EndSection
 
# **********************************************************************
# Input devices
# **********************************************************************
 
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
 
Section "InputDevice"
 
    Identifier   "Keyboard1"
    Driver   "kbd"
 
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
 
#    Option     "Protocol"      "Xqueue"
 
    Option "AutoRepeat" "500 30"
 
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option   "Xleds"      "1 2 3"
 
#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"
 
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"
 
# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""
 
#    Option "XkbDisable"
 
    Option "XkbRules"   "xorg"
    Option "XkbModel"   "pc104"
    Option "XkbLayout"   "us"
 
EndSection
 
 
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
 
Section "InputDevice"
 
# Identifier and driver
 
    Identifier   "Mouse1"
    Driver   "mouse"
    Option "Protocol"    "Auto"   # Auto detect
    Option "Device"      "/dev/input/mice"
 
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
 
#    Option "Protocol"   "Xqueue"
 
# Mouse-speed setting for PS/2 mouse.
 
#    Option "Resolution"   "256"
 
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
 
#    Option "BaudRate"   "9600"
#    Option "SampleRate"   "150"
 
# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
 
    Option "ZAxisMapping"   "4 5 6 7"
 
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
 
#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"
 
# ChordMiddle is an option for some 3-button Logitech mice
 
#    Option "ChordMiddle"
 
EndSection
 
 
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
 
# **********************************************************************
# Monitor section
# **********************************************************************
 
# Any number of monitor sections may be present
 
Section "Monitor"
 
    Identifier  "My Monitor"
   Option "DPMS"
   HorizSync 30.0-81.0
   VertRefresh 56-75
   Modeline "1280x1024_60.00" 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync
EndSection
 
Section "Device"
    Identifier  "** ATI Radeon (generic)               [radeon]"
    Driver      "radeon"
    BusID       "PCI:1:0:0"
    Option      "AGPMode" "8"   # Changed from 4
    Option      "AGPSize" "64"
#   Option      "AGPFastWrite" "on" # Cause X to freeze!
    Option      "AccelMethod" "XAA"
#    Option      "AccelMethod" "EXA"   # Replaced with the above
    Option   "ColorTiling" "on"
    Option      "DynamicClocks" "on"
    Option      "RenderAccel" "true"
    Option      "TripleBuffer" "true"
    Option      "DRI" "true"
    Option      "EnablePageFlip" "true"    #was commented
    Option      "EnableDepthMoves" "true"
    Option      "XAANoOffscreenPixmaps" "1"
    Option      "BusType" "PCI"   # !!Very Important for direct rendering!
#   Option      "GARTSize" "128"

#    VideoRam     131072
    # Insert Clocks lines here if appropriate

EndSection
 
 
# **********************************************************************
# Screen sections
# **********************************************************************
 
# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "** ATI Radeon (generic)               [radeon]"
    Monitor     "My Monitor"
    DefaultDepth 32
 
    DefaultDepth 24
   SubSection "Display"
   Depth 1
   Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
   Depth 4
   Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
   Depth 8
   Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
   Depth 15
   Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
   Depth 16
   Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
   SubSection "Display"
   Depth 24
   Modes "1280x1024" "1152x864" "1024x768" "832x624" "800x600" "720x400" "640x480"
   EndSubSection
EndSection
 
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
 
# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
 
Section "ServerLayout"
 
# The Identifier line must be present
    Identifier  "Default Layout"
 
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.
 
    Screen "Screen 1"
 
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
 
    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
    Option "AIGLX" "true"
EndSection
 
Section "DRI"
    Mode 0666
EndSection
 
Section "Extensions"
   Option "Composite" "Enable"
   Option "RENDER"
EndSection

9
Point a browser to your core to get the admin interface.
Under Advanced->Network->Network Settings there should be a button called "swap interfaces"

HTH
Darren

I am sorry to report that the button "swap interfaces" is nowhere to be found under Advanced > Network > Network Settings.
Does one have to take it down to offline or something like that in order for that button to appear?

*shrug*

10
Hi!

I have a LMCE 1.1 Beta 2 installed. On this box I have a Netgear wireless card and a ethernet card. Thus ath0 (wireless) and eth0 (wired 10/100 mbps).

At install I made the mistake having ath0 as the default gateway and communication to router and internet. That made ath0 external network device in LMCE. And eth0 became internal.

How do I switch them around so that ath0 is internal and eth0 is external instead?

11
Feature requests & roadmap / Re: Single NIC installation
« on: May 28, 2007, 11:16:02 pm »
The thing to keep in mind is that this system was designed to be THE computing system in a house.  As such, it was assumed that the network for the home could be configured around it.  Actually, having two NICs and having your core act as your router for the devices attached to your LinuxMCE core makes a pretty nice sandbox to play with the system.  At least it does for me.  Jpelzer does bring up an excellent point in that DHCP can be utilized independently of the router (though I'm not sure LinuxMCE can do this right now).  I know Pluto gives the option of a single NIC install when the system is installed.  I guess the LinuxMCE developers removed that in the fork.  Is that correct?
 
To throw my $.02 in:

1) Pluto provided an opportunity for a single NIC install, so performing that with LinuxMCE should be fairly easy to do, but:
2) The PNP functionality of the LinuxMCE system is really neat, and I think important to expand the attractiveness of the system beyond the hardcore tinkerers who are playing with it now.
3) I respectfully disagree with Cryoniq that the voicemail, lighting, security features are not that important.  If I want just a media center with tv and video, I can use Myth and be done.  The strength of LinuxMCE/Pluto lies in the fact that it ties together all the disparate peices of hardware and software to create a cohesive system that makes sense and can allow control of a complex system through a (semi-intuitive) interface.  The fact that there are a lot of issues with the implementation still means that that is where the developers (I hope to be included) should spend their effort, as that is the true magic happens.

Oh that is ok. I am just pointing out that right now there seem to be a need to fix the media functions. Of course voicemail. lighting, security features are important to LMCE as a whole; But we are in beta right now and one have to start somewhere and work from the top and out. The media functions like TV, Video, Music, Pictures, Remotes and mount of information via local drives and shares are what drawn most of the people towards LMCE. I discovered LMCE from a discussion on a IT news resource forum and many people thought it looked awesome and all made remarks about just those parts and issued strong interest for them.

Of course I realise that everyone cannot work on those things and some doesn't have the knowledge and experience of that, which will work and develope the voicemail, security etc. I am not saying those people should drop what they doing and turn on the media features. Just so noone think I am doing that.

I am sure these things are adressed as we.. uhm write.. and that it is a concern and goal of the developers as well naturally. So I point out that I am not ranting, even if it might seem like it. I just think LMCE got huge potential and I would love to see the interest explode around it. But in order for that the install have to be close to flawless and easy and the main parts that draw most people to it need to work.

I might seem irritated from time to time. But that is out of the fact that I discovered LMCE, watched the video and everything was under PR flag that it was just pop in ubuntu, download and install and things would be taken care of and ready for showtime. And that turned out to be very far away. So after spending several days and nights fiddling with it all and headaches it gets very frustrating.
I really hope people haven't been scared away experiencing the same as I have and that they stay tuned and realise this is a work in progress of course. :)

I will try do my best to submit feature requests and bug reports to make LMCE  grow and flourish :) And I will yell when something is wrong, but I do it out of love for LMCE (omg that was covered in pink and fluff!) :P

12
Hi!

It would be very neat to be able to change or switch place of the network devices in LMCE admin page under network.

For example, as I have now, the wireless (ath0) is on external and ethernet 10/100 mbps (eth0) is on internal.

It would be nice to be able to tell LMCE via admin page which interface belongs to what side. For example I would like to switch ath0 to be on internal instead and eth0 on external. At the same time I would be able to tell LMCE that it should not force settings for ath0 since that is using WPA-TKIP (in my case) and is using knetwork-manager handling that and wpasupplicant. It shall in no condition alter such network devices settings, which it seem to do now.

Maybe a detection of available and activated network devices is enough and ability to specify if they are external or internal and let the configuration of these be configured in kubuntu alone as default, and have a checkbox or button for extended advanced features and possibility to specify and alter the network adress configuration as it is now.

13
The main reason I am posting about it here, is that I am not really sure yet if it is a bug or something else.
Therefore I am interested in other peoples experience regarding setting up shares in LMCE 1.1 Beta 2 toward Other computers shares as well as netdisks with smb server built in, so I know it isn't just me, but others as well.

I do not know how the shares are suppose to be set up and if the device numbers under /mnt/device/ should be created by LMCE or if it is a decoy for something else it does. Or if it is a problem with the mount and smbfs or if I got the things wrong.

If someone would be kind enough to post a step by step guide of how to set up a mount to a windows share and/or a share on another ubuntu machine, if they got it working it would be sweet. As I understood I should use cifs with this one. But I also tried mounting this Ubuntu 7.04 machines shares manually from LMCE router and it was same result.

Reason I pointed at:
Dst="/mnt/${NAS_Description}_${NAS_PK_Device}"
mkdir -p "$Dst"

Is that I felt that /mnt alone was a "device" short perhaps. But then again I am not skilled enough in programming (way rusty) to determine if ${NAS_Description} contain /device in it and make the path complete as /mnt/device/.......

When I confirmed that this isn't just a problem of mine, then I'll head on and make a bugreport :)

Edit: I made a bug report about it. But! I noticed this in  the interfaces section in LMCE admin interface:
545     ** DISABLED ** Pluto SmbFS Kernel Module

Can that have something to do with why it is not working? Or is that like it should be. There were more that had disabled in front of them as well.. hmm

14
Now I am confused about this mounting shares in LMCE 1.1 Beta 2.

Syslog i reporting it can't mount the shares to /mnt/device/32 and up to 35 (for the 4 shares).

Reason is a mentioned above that the number dirs doesn't exist under /mnt/device.

Oki; So I tried create those dirs. I get back that file or directory does not exist. I am thus not allowed to make those dirs.

So I reboot and start up recovery mode. Once in it I discover that in recovery mode /mnt/device doesn't exist. That is funny..
/mnt/device is created by LMCE upon initiation then?

So I make a walk on the wild side and create /mnt/device
And then I create /mnt/device/32, /mnt/device/33, /mnt/device/34 and /mnt/device/35
And then I reboot system.

Well as soon as LMCE initiatied it seemed to remove all those modifications because when I check those dirs, they do not exist. Only /mnt/device exist.

And under /home/public/data/other/ there are these red links named  "Windows Share:  PUBLIC [32] ---> /mnt/device/32

Can anyone skilled and experienced please explain what is going on here and how the shares are handled. Is this a bug, or is it something else?

For the record I can still for example mount PUBLIC share manually to a dir outside /mnt/device/ so it works if I do that. Question is why LMCE fails.


Edit: is it Net_Mount.sh that handle the mount part of shares? Looked into it and there is indeed a part with mkdir -p and a variable after that which I assume should be the device number the link later on further down in it will link to.

Quote
Dst="/mnt/${NAS_Description}_${NAS_PK_Device}"
mkdir -p "$Dst"

15
I solved it by not using the ath0 at all and set eth0 to 192.168.1.151 so it became a part of the existing 192.168.1.x network.
DHCP was disabled at install. Can't have 2 DHCP servers at same physical network. Would cause havoc among the existing other devices.

There is a problem with creating shares in LMCE 1.1 Beta 2, just as with Beta 1. It doesn't create the directories which are to be mounted with each share. I am going to reboot and go into safemode and try create those dirs before everything else starts up, somehow. As it is now, I cannot create any dirs at all under /mnt/devices/
I am denied doing that even as root. Even denied creating any dir in that dir. I might not understand smb and mount too much but I do know it has to have a dir existing to what a link points to, and right now the link points to devices/33, 34, 35, 36 for the 4 shares, and those doesn't exist. And then it is no wonder nothing shows up of what is on the shares. There are lots of stuff in them.

Pages: [1] 2