RE: [OFF-TOPIC] debian amd64 wallpaperz?
Try here: http://kde-look.org/ here's one I made: http://kde-look.org/content/show.php?content=19960 :) From: Rafael RodrÃguez <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org CC: [EMAIL PROTECTED] Subject: [OFF-TOPIC] debian amd64 wallpaperz? Date: Tue, 1 Feb 2005 13:39:01 + Hi. Is there any debian / amd / linux /whatever wallpaper with some cool "64 bit powered" banner or so? I'm just too proud of my laptop! =;D Regards, -- Rafael RodrÃguez - http://djclue.no-ip.org -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d- s-: a-- C++ UL++ P++> L++ E--- W+++ N o? K? w--- !O !M V-- PS PE- Y+ PGP+ t--- 5? X R* tv- b- DI- D+ G e++ h! r++ y+ --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
LMSensors Setup and Configuration
Hello. I'm trying to setup Lmsensors so I can monitor my system. I installed lmsensors and ksensors (a KDE frontend for lmsensors). However, it seems that I need i2c. What is this and where can I get it? I tried apt-get install i2c but that didn't work. Thank you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE Themes Missing?
I was able to get KDM working by switching a value in one of the config files from true to false so that it would force KDM to start. Worked great except for the fact that my keyboard didn't work... I looked online and it seems like it's a fairly common problem. I just decided to turn off the graphical login and just use the console and startx. It's easy and probably less CPU intensive. Thanks for the help. :) From: [EMAIL PROTECTED] (Lennart Sorensen) To: Sven Krahn <[EMAIL PROTECTED]> CC: debian-amd64@lists.debian.org, Pat C <[EMAIL PROTECTED]> Subject: Re: KDE Themes Missing? Date: Wed, 19 Jan 2005 12:44:15 -0500 On Wed, Jan 19, 2005 at 06:38:29PM +0100, Sven Krahn wrote: > On Wed, 19 Jan 2005 15:30:55 +, Pat C <[EMAIL PROTECTED]> wrote: > > So my debian system is awesome. I'm using KDE and I love the new KDE 3.3 > > setup. However, I can't seem to be able to change the graphical login when > > the computer starts up. It's this plain drab Debian logo and two boxes. I > > If you prefer the standard console login just de-activate xdm > (unfortunately, 'apt-get remove xdm' has too many dependencies > (complete KDE) which will be affected as well) in /etc/init.d/ by (as > root) > > # update-rc.d -f xdm remove > # echo xdm hold | dpkg --set-selections Why not just: apt-get install kdm, and when it asks, say you want kdm as the default display manager. Or change /etc/X11/default-display-manager file to have the right name. That is what the init.d files for xdm, kdm and gdm look at to decide which one of them should actually start. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE Themes Missing?
So my debian system is awesome. I'm using KDE and I love the new KDE 3.3 setup. However, I can't seem to be able to change the graphical login when the computer starts up. It's this plain drab Debian logo and two boxes. I tried changing the login using the control panel but that didn't work. I noticed I didn't have any themes installed when I go to the themes section so I thought maybe I could download some. I got two off of the alioth server (.deb) but they still don't show up in the list. Are themes installed in another directory that I'm not aware of? Thank you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 DHCP Network Configuration Failure
Wow, that did it! I took the card out and reinstalled and everything worked! Now it gets an IP address and connects to the internet and everything! Thank you so much! LOL. You have no idea how long I have been trying to get it to work. :) From: Dave <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org Subject: Re: AMD64 DHCP Network Configuration Failure Date: Mon, 17 Jan 2005 19:19:56 -0500 Bob Proulx wrote: What does lspci say? lspci | grep Ethernet It seems strange to me that your "DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard" would have a tulip based network interface chip. IIRC that has an nvidia based onboard gigabit lan. But perhaps it is so and it is tulip as I do not have any firsthand information. The lspci will say for sure. I am guessing that your latest install is guessing the wrong driver for your interface. The first thing I would do would be to verify that the right driver module is loaded for your networking. You may need to give the system help in getting that correct. Bob I have the DFI board in question as well and its working flawlessly. I built it with the ~nov 15th-ish 4mb install image. I had a similar problem with the ethernet, but a quick search revealed the solution. Forcedeth module had to be used to get me online. AFAIK I'm still using it. I'm totally screwed if this goes down, as I have lost my printed list on what had to be done at the network setup portion. It was a fairly simple workaround. I liked it better than the Nvidia drivers which seemed to have mucked up the onboard sound once I installed them. I have no output from "lspci | grep Ethernet" (or grep -i eth) but I have forcedeth module loaded on startup. I believe the workaround during instal was to pause at the section configuring the network, alt-f2 into another console, log in as root, and remove the ethernet over firewire, insert forcedeth and the network now detects as normal. I'm currently running 2.6.9-9-amd64-k8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 DHCP Network Configuration Failure
Well, the base systems installs however, DHCP still does not work. Here's what I did: run "dhclient eth0" Here is the output: --- eth1: unkown hardware address type 24 eth1: unkown hardware address type 24 Listening on LPF/eth0/00:20:78:06:02:ed Sending on LPF/eth0/00:20:78:06:02:ed Sending on Socket/fallback/fallback-net DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 5 bad udp checksums in 5 packets DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 No DHCPOFFERS received No working leases in persistant database Sleeping. When I check "lsmod", Tulip shows up so the module is running I assume. Any other thoughts? Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 DHCP Network Configuration Failure
From: David Sawyer <[EMAIL PROTECTED]> Reply-To: David Sawyer <[EMAIL PROTECTED]> To: debian-amd64@lists.debian.org Subject: Re: AMD64 DHCP Network Configuration Failure Date: Mon, 17 Jan 2005 14:58:30 -0500 On Mon, 17 Jan 2005 18:37:21 +, Pat C <[EMAIL PROTECTED]> wrote: > I just put a new system together. Here are the specs: > > AMD64 3200+ CPU > 512MB DDR 3200 RAM > 3DFX 16MB Graphics Card... old, yes I know :) > Standard CD-Drive > 20GB IDE Hard Drive > 550 Watt Power Supply > Antec Case > Bridgecom 10/100 Fast Ethernet NIC > DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard (onboard > 10/100/1000 Ethernet, Audio, USB, and Firewire) > > I am using the SargeAMD64 NetInstall .ISO Everything works until I get to > the network configuration section. My Bridgecom 10/100 card shows up, as > well as firewire (eth1). However, my onboard ethernet on the motherboard > doesn't. Ok I think, I'll just use the older one for now. It goes to get > DHCP information and can't do it. I put in my hostname and it still can't > do it. When I go to configure it manually to see if it works, I put in all > the information and then the system goes blank. What do you do to configure it manually. Did you edit the /etc/network/interfaces file, or just type ifconfig eth0 ip netmask netmask_addr. No, this is during the installation process. There is an option that allows you to manually put in an IP address and gateway and so on. Is there a way to see the linux unpack and load before it gets to choosing a language? It scrolls by too fast for me to read. When exactly does the system go blank. During startup if you changed the above file I mentioned, or after using ifconfig? When I try putting the values in manually, I put in the IP address, netmask, gateway, and nameserver. AHHh... ok, I think I figured it out. If you put in a nameserver and you're not using a nameserver (me) then it hangs. I left the nameserver out and it worked and continued on to the hostname setup. I think it would be beneficial to add a check so that if the nameserver doesn't work it can continue on without one. This might confuse people. Also there is a default value in the nameserver. Maybe just leave it blank? I will continue with the installation and see if I can configure DHCP from the commandline. Thank you. Can you do anything when it goes blank, try switching consoles or Ct-alt-del it. Or Is the system hard frozen? >I know everything should > work because I tried an old version of Debian for i386 and it could find > everything for DHCP easily. Does anyone have any suggestions? Could this > be a bug? Thank you for the help. :) DHCP seems like less of a problem as the system blanking when you try to configure it. If the network card and module are working, you can run dhclient anytime. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
AMD64 DHCP Network Configuration Failure
I just put a new system together. Here are the specs: AMD64 3200+ CPU 512MB DDR 3200 RAM 3DFX 16MB Graphics Card... old, yes I know :) Standard CD-Drive 20GB IDE Hard Drive 550 Watt Power Supply Antec Case Bridgecom 10/100 Fast Ethernet NIC DFI LANPARTY UT nF3 250Gb nForce3 250GB Chipset Motherboard (onboard 10/100/1000 Ethernet, Audio, USB, and Firewire) I am using the SargeAMD64 NetInstall .ISO Everything works until I get to the network configuration section. My Bridgecom 10/100 card shows up, as well as firewire (eth1). However, my onboard ethernet on the motherboard doesn't. Ok I think, I'll just use the older one for now. It goes to get DHCP information and can't do it. I put in my hostname and it still can't do it. When I go to configure it manually to see if it works, I put in all the information and then the system goes blank. I know everything should work because I tried an old version of Debian for i386 and it could find everything for DHCP easily. Does anyone have any suggestions? Could this be a bug? Thank you for the help. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]