Recent Posts

Pages: [1] 2 3 ... 10
1
Installation issues / Re: Gigabit ethernet card runs @ 100
« Last post by posde on Today at 05:31:15 pm »
did you check the speed by copying a large file?
2
Installation issues / Re: Gigabit ethernet card runs @ 100
« Last post by pigdog on Today at 02:53:13 pm »
Hi,

I checked my Core ethernet card connecting @ 1000

05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
       Subsystem: Elitegroup Computer Systems RTL8111/8168 PCI Express Gigabit Ethernet controller
       Kernel driver in use: r8169
       Kernel modules: r8169

I checked my MD

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
       Subsystem: AOPEN Inc. Device 0706
       Kernel driver in use: r8169
       Kernel modules: r8169

So I don't think it would have anything to do with the r8169 driver.

On my Core I used ethtool eth0

Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:    10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:    10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                                         1000base T/Half 1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level:  0x00000033 (51)
         drv probe ifdown ifup
Link detected: yes


So on my MD

Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:    10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:    10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
                         1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level:  0x00000033 (51)
         drv probe ifdown ifup
Link detected: yes

My MD is connected @ 100Mb/s and the link partner isn't showing 1000baseT as an option.

To see if the MD would connect at 1000Mb/s I tried...

ethtool -s eth0 speed 1000 duplex full autoneg on

The ethernet link to the MD drops (no lights or activity at each end).

I pulled out the ethernet cable on the MD and also powered it off.  Reconnect and power up and it comes up @100Mb/s with terminal message Write failed: Broken pipe.

The spec's for the AOpen DE7000 says 10,100,1000.

Any ideas?

Cheers.

3
Hi tompin2,

I went a head and installed the current nvidia driver on my Core, it had a GeForce 8500 GT card.

I could use the current driver because my card was supported.  Older hardware needs different versions.

apt-get update && apt-get install nvidia-current && nvidia -xconfig

When I built my MD's (both could run the current driver) they came up with the nvidia driver.  Whether this happened because I installed the nvidia driver on the Core before creating the MD's, or, the MD get created with the nvidia drivers.

I'm not sure.

MD's use a different process when generated and can even have different kernels.

Cheers.
4
Hi pigdog,

Same happened to me, sound  used to work ok on a previous 1204 release, I logically have no hdmi audio anymore :o. I have a zotac zbox.

Here is my video card info, probably is not listed and thats why is not detected during the boot up

root@moon159:~# lspci -nnk | grep VGA -A3
03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [ION] [10de:0a64] (rev a2)
        Subsystem: ZOTAC International (MCO) Ltd. Device [19da:3100]
        Kernel driver in use: nouveau
        Kernel modules: nouveau, nvidiafb


Cheers,

T
5
Installation issues / Gigabit ethernet card runs @ 100
« Last post by pigdog on April 18, 2014, 10:24:58 pm »
Hi,

Before I get too stupid and spend hours/hours looking into things... would a 1 Gigabit card running r8169 driver get stuck @ 100 speed?

Everything works fine except the speed.

I want to set up jumbo frames on my LMCE network because my MD's are not the fastest CPU's.

I was hoping to increase the frame size, reduce my CPU processing and improve my data transmission speeds.

I have one device in the network which is connecting @ 100Mbps @ the switching hub but "spec-wise" has a gigabyte card.

Other devices are 1Gig at the hub.

Cheers
6
Users / Re: using a script to launch scenarios
« Last post by mikeybs on April 17, 2014, 08:06:12 am »
here is what I see when I click on one of my lighting scenarios in my web orbiter

it just shows the individual messages to each device, it doesn't show what command group was executed...

will I have to send messages to each device individually?

maybe I need to increase the verbosity of my logs in order to see command group information?


DCERouter.log
08   04/17/14 2:00:21.315      Received Message from 56 (myweb2orbiter / ) to 79 (Ceiling Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08   04/17/14 2:00:21.315        Parameter 76(Level): 45 <0x7a18ab40>
08   04/17/14 2:00:21.317      Received Message from 56 (myweb2orbiter / ) to 78 (Daybed Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08   04/17/14 2:00:21.317        Parameter 76(Level): 45 <0x7a18ab40>
08   04/17/14 2:00:21.319      Received Message from 56 (myweb2orbiter / ) to 81 (Lamp / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08   04/17/14 2:00:21.320        Parameter 76(Level): 50 <0x7a18ab40>
08   04/17/14 2:00:21.321      Received Message from 56 (myweb2orbiter / ) to 80 (Window Lights / Home Theater), type 1 id 184 Command:Set Level, retry none, parameters: <0x7a18ab40>
08   04/17/14 2:00:21.321        Parameter 76(Level): 45 <0x7a18ab40>

7
Hi phenigma,

Well...       http://forum.linuxmce.org/index.php?topic=13655.0

From my earlier statement in this post.

Quote
I run LMCE on a dedicated network without username/password access.

....basically don't be lazy and not use username/password credentials on 12.04 NAS drives.

The errors in topic=13655.0 helped a bit.

But why symbolic link errors? - that throws you way off.  At least it did me.

I feel kinda silly being lazy with an unsecured NAS but I at least learned something - I hope.

Thank you very much for your time (that I wasted).

Cheers
8
Installation issues / Re: NAS CIFS errors on April 13 28939 snap
« Last post by pigdog on April 16, 2014, 10:52:00 pm »
Hi Michaeltree,

FYI my smb.conf is exactly the same in 12.04 as it was in 10.04.

security = user   was already set.

My NAS was open (I'm a bad boy) but it was on an internal network where only LMCE devices could access it.

I played around but I could not get 12.04 to connect.

So to fix it I started from scratch, reloading the Core/Hybrid (because of so many things) and then added a username/password to the NAS.

In my smb.conf I had to add     client lanman auth = yes.

My Core/Hybrid upon NAS discovery asked for NAS credentials and everyone is happy.

I guess we can't be lazy anymore and leave storage devices unsecured.

Thanks for your input.

Cheers.
9
Installation issues / Re: Snap April 13 28939 ehci_hcd errors
« Last post by pigdog on April 16, 2014, 10:26:56 pm »
Hi,

I reloaded from scratch and no more error messages.

I went into KDE Desktop and put a USB stick into a port and received...

An error occurred while accessing 'USBNAME', the system responded:
An unexpected error has occurred. : Not Authorized

I have not seen any error messages on the terminal.

I will play with this when I get spare time to see if it can be reproduced and to find out why I'm not authorized.

Cheers
10
Users / Re: Need some dedicated testers.
« Last post by maverick0815 on April 16, 2014, 06:50:29 pm »
No one hates golgoj4...actually I was getting worried, that something might have happened to you...
Anyways, I also looked at the qt5orbiter, which looks pretty good to me too....unfortunately not much seems to be working there yet.
Pages: [1] 2 3 ... 10