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 - phenigma

Pages: 1 ... 55 56 [57] 58 59 ... 87
Users / Re: Multi-room Audio - a tad confused
« on: February 21, 2011, 08:35:37 am »
Each media player needs a dedicated "room".

posde, as it is a little confusing, and I don't think I fully understand, could you (or someone else) provide a brief description of how an 'EA' (Entertainment Area) and a 'Room' are similar/different.  I've always thought I could create more than one EA for a Room (say MD and standalone squeezebox).  But to have proper integration I've always had to create a new 'Room' for each media player (MD, squeezebox, etc.).  I don't want to hi-jack the thread (happy if this has to go to a new one) but I've wondered.



Users / Re: Pad Orbiter and WPA2
« on: February 21, 2011, 08:26:42 am »
Great stuff Josh!  Thanks for posting a howto!


Installation issues / Re: realtek 8168 driver issue
« on: February 20, 2011, 07:40:38 pm »
Dan, great to hear it's working!!  Congratulations!

The best piece of advice I can give you now is to put the .ko file(s) aside in case you ever need to do a re-install, I keep them on a usb stick so they're easy to copy over without networking.

You can put your 2nd NIC in, verify it's working, and continue on with the LMCE install now!

Have fun!!


Installation issues / Re: realtek 8168 driver issue
« on: February 19, 2011, 04:25:44 pm »
You need to blacklist 'r8169' not '8169'.  Once properly blacklisted you should not be see the r8169 driver loading at boot.  Blacklisting only prevents the driver from being loaded on boot, it doesn't remove it from the currently running kernel, rmmod does that.  If you blacklist the driver, build the new initramfs and reboot then then driver should not load.  If it does it is not blacklisted properly.

You may need to run the command 'depmod' after installing the new driver files, before modprobe.  If modprobe can't load the r8168 driver then nothing will, this is the place you should concentrate on getting to work.

dmesg shows all device and driver notifications since boot so the r8169 will show in dmesg if it loaded during boot.  rmmod will remove the driver from the kernel but dmesg still shows the messages from when it loaded on boot.

At this point it is not using new r8168 driver and the file size on the r8169 looks like the original file.  At any time you should be able to 'rmmod r8169' and then 'modprobe r8168', until this works the kernel is unable to find your driver.

Change the blacklist entry and could you run 'uname -r' by itself at the command line.  This will tell us which kernel you are running.  The update-initramfs -u -k `uname -r` would update the initramfs for the currently running kernel only, rather than all kernels on your system, I'm concerned that this didn't work.


Installation issues / Re: realtek 8168 driver issue
« on: February 19, 2011, 05:43:30 am »
Well, your NIC is exactly the same pci id as mine if we properly install the net drivers this should all work.

Your output for 'lshw -C Network' is the same both times and shows the 8169 driver is being used.  Your dmesg output also shows the 8169 driver being loaded.  You system is still trying to use the 8169 driver, if my updated driver was in place it shouldn't do this.   I have not blacklisted the 8169 on my machine, I altered it and removed the 8111's pci id so it wouldn't match and therefor not load.  I could just as easily blacklist it though.

Lets specifically unload the 8169 driver and manually load the 8168 driver in it's place. 
Code: [Select]
rmmod r8169
modprobe r8168

Run 'lsmod' or 'lsmod | grep r816' to see if the 8168 or 8169 drivers are loaded.  If the 8168 is loaded then re-run all the previous commands to see if the 8168 driver is working.  If you don't have success then you can try rebuilding your initramfs and reboot your machine. 

You may want to try blacklisting the 8169 driver at this point. 
Code: [Select]
echo "blacklist 8169" >> /etc/modprobe.d/blacklist

Then, type 'cat /etc/modprobe.d/blacklist' to display the file on your text console and make sure the 'blacklist r8169' line shows at the end of the file.  Then rebuild your initramfs.
Code: [Select]
update-initramfs -u -k `uname -r`

These changes only occur on reboot so... Reboot and re-run the earlier tests.  If you're using the driver I provided then this should work.  Good luck and let me know how it goes!


Installation issues / Re: realtek 8168 driver issue
« on: February 18, 2011, 09:57:40 pm »
If you open the driver files with nano and save them when you exit you could alter the driver so it doesn't function.  Don't open the .ko files with nano.  nano is for editing text files only.

This is from mine:

lshw -C Network

Code: [Select]
       description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: eth0
       version: 06
       serial: e0:cb:4e:ce:ce:28
       size: 1GB/s
       capacity: 1GB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.019.00-NAPI duplex=full ip= latency=0 link=yes module=r8168 multicast=yes port=twisted pair speed=1GB/s

Hmm, it looks like it's not associating your card with the driver, notice the driver= and module= parameters in configuration on mine.   Notice my version is 06.  Can you post the output of 'lspci -nn' (two n's) and 'dmesg | grep -i eth'.


Marketplace / Re: WebDT 366s - Brand new still in the box. ** $75.00**
« on: February 18, 2011, 06:53:54 pm »
Fwiw, I bought two units from Ted.   Neither unit will boot/recognize the USB port on it's side.  Specifically, when I plug in a bootable USB drive and turn it on, neither unit will boot from the USB drive.  They both go to a blue screen, then back to black and give the error "Attempting to boot a Hard Drive...  Invalid system disk   Replace the disk, and then press any key."  Also, on one of the units, the first 2 of the 3 lights do not light up at first boot.  I do have a third WebDT 366 (a GX, not purchased from Ted) that has no issues booting from my bootable USB drive, so I know that the USB drive is okay. 

Have you gone into the BIOS and set the boot order to boot from the USB?  None of my units booted straight off the USB they were all set to boot from the internal flash HDD on arrival.

I also had one unit that the BIOS was set to output through some non-existent video device.  Result was nothing but a black screen.  I read a little on and was able to hit the proper keys at the proper times to set BIOS back to defaults so it would show me a display again.  After this I entered BIOS and configured it for USB boot, no problems since.


Marketplace / Re: WebDT 366s - Brand new still in the box. ** $75.00**
« on: February 18, 2011, 06:49:28 pm »

a real orbiter (as the PadOrbiter running on the WebDTs) is much nicer than a Touch Orbiter.

My .02€

A very good point.


Installation issues / Re: realtek 8168 driver issue
« on: February 18, 2011, 06:42:57 pm »
Most commands followed by '--help' will show you all the usage methods.  man is your friend as well it will show you 'Manual' pages relating to the command/software you specify.

What is the result of the 'dhclient' command?

Do you have a dhcp server active on your router to provide an IP?  I assume you can connect other devices and they receive an IP address properly.

Have you tried setting a static IP (on your local subnet) through kubuntu?


Marketplace / Re: WebDT 366s - Brand new still in the box. ** $75.00**
« on: February 18, 2011, 01:52:06 am »
I did get mine replaced...  It was at least 2 weeks after I had paid for the initial units before he shipped anything to me, and that happened because I contacted him.  The defective unit I had arrived with a Windows installation on it that was BSoDing on boot with a licence violation error.  I ultimately determined it had defective RAM.  After I shipped my defective unit back to him he claimed to have copied an operating system onto the flash drive (which I was able to do quite well, it was failing memtest86 over a large chunk of RAM) and he was going to resell it.  He then tried to give me a story about how much money he was losing and wanted me to pay for more shipping after I had received my replacement...  This process was a pain and ultimately took 8-10wks to resolve.

I don't recommend purchasing from him.

I saw the price and gambled.  The DX model he was selling is nice, it's 586 based and very responsive with a nice wireless NIC.  GX units are 486 based and have wireless NICs that really only support WEP encryption (see Thom's & Hari's posts earlier in this thread).  I figured I could get 4 (could actually have got 7) from this guy, with charge cradles, for less than the price of 1 from lmcecompatible (@USD$459.98+tx with a charge cradle) and if only 1 worked... 

If I was to do it again I'd probably go for an Archos 7 Home Tablet and use an Android Touch Orbiter.


Installation issues / Re: realtek 8168 driver issue
« on: February 18, 2011, 12:54:39 am »
Just to confirm the method I used to copy r8168 and 9 was:

 "cp r8169.file.location  /lib/modules/2.6.27-17-generic/kernel/drivers/net"

Okay, the files should be 'r8169.ko' and 'r8168.ko' not 'r8169.file.location', can you confirm that?  And yes, the file would appear to have more 'lines' when viewed in nano.  Instead of using nano to compare file sizes you can use the 'ls' command.  Type 'ls -l' at a command prompt to get a listing of files in the current directory and it will show you exact file sizes counted in bytes, among other things.  Try 'ls --help' or 'man ls' for more information on using ls for file listings, it's very handy.

Back to the issue at hand:
When you plug the ethernet cable in to your on-board NIC do you see the LEDs light up next to the connector?

Have you tried a different Ethernet cable?
I have a cable that works with 100Mb cards but not 1000Mb cards (damaged pair in the cable).


Marketplace / Re: WebDT 366s - Brand new still in the box. ** $75.00**
« on: February 17, 2011, 12:52:27 am »
After my final experiences I wouldn't recommend buying from tbowland.  The model itself is great though if you can find reliable stock.


Installation issues / Re: realtek 8168 driver issue
« on: February 16, 2011, 07:13:58 pm »
Yeah I have just given up smoking as well, which made it so much more enjoyable.

I think I started smoking from my ears at that point.


Installation issues / Re: realtek 8168 driver issue
« on: February 16, 2011, 07:12:18 pm »
Hi phenigma,

Thank you very much for the information. Sorry I have taken so log to follow up your advise. I was having trouble getting onto web admin and after 3 different linuxmce mirrors have finally get my system up and running.

I followed your instructions, managed to download the file from the web site you suggested, tar, make, into net folder but still no connection.

Dan, good to see you're still puligging away at it.  To make things easier all around I recommend you start from scratch and use the drivers I provided for now.

To avoid any conflicts between cards I suggest that you proceed as follows:

Remove your 2nd NIC from the machine.
Do a fresh install of kubuntu from a snapshot dvd.
Put the 8168 AND the 8169 driver I provided in earlier posts in the drivers/net directory. 
You will have to use the 8169 driver I posted or blacklist the 8169 driver that kubuntu provides. (They will conflict).
Reboot your machine.
Your NIC should be detected by kubuntu and work in kubuntu at this point.
If it doesn't work then you should not proceed any further.  Stop here and get this NIC to work before proceeding.

Once the onboard NIC is working shut down the machine and install your 2nd NIC.
Boot the machine and, if the drivers are correct for the 8139, your 2nd NIC should also be active.
If your 8139 doesn't get detected properly you may need to DL & build newer drivers for it as well (I have no experience with the 8139).

Don't proceed with installing LMCE until both NICs are functioning and working in kubuntu.

Let us know how you make out.


Installation issues / Re: realtek 8168 driver issue
« on: February 16, 2011, 06:58:24 pm »
Sorry for my lack of replies, Dan. My core decided to destroy itself with no MDs or orbiters working, so I am having a week or so away from it for the sake of my mental health.

Ahh...  the ol' blew up the core mental health break...  I have taken a few.   ;-)


Pages: 1 ... 55 56 [57] 58 59 ... 87