Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet. It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. Any help would be appreciated. thanks, allan Run 'lspci'.
Re: [gentoo-user] emerge -uD world: another obstacle
A likely source of the problem could be when I was advised to compile qt with thread support which I took to mean USE=threads etc. But when I looked at the log it just mentions the verbose switch, nothing about threads. Another might be that qt-4.3.3 is currently on my system and there's no such thing as /usr/qt/4... If anybody needs more to go on I'll attach whatever log you need in my reply. Maxim What does 'emerge -p qt' say? I think it lists the use flags. I think the 'threads' use flag should be something else. I have no idea what though. Maybe I can guess from my use flags. -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Gentoo LiveUSB
On Friday 11 January 2008, Anthony E. Caudel wrote: 2nd question: I must be dense on this one so someone help me out. Since a USB stick is seen as a hard drive, why can't I do a standard install to it? Is it because until lately they haven't been large enough? I'm thinking of using an 8GB one. There's a few reasons: 1. The memory used on those devices has a limited life - about 100,000 writes for the good ones and maybe 10,000 for the bad ones. With a standard install, frequent writes are the norm (think cache and other similar things). This usually ends up at the same spot on the disk, meaning your new install will last about a month if you are lucky. There are ways around this, for instance how a LiveCD does things. 2. Booting off it is a pain. You need drivers for the entire USB stack at boot time, which usually means a ginormous initrd. 3. Size, which you mentioned -- Alan McKinnon alan dot mckinnon at gmail dot com -- gentoo-user@lists.gentoo.org mailing list Does desktop RAM get constantly refreshed while powered and it doesn't need to keep any data when not powered? Is that the difference? -- gentoo-user@lists.gentoo.org mailing list
RE: [gentoo-user] Nvidia users: please sign petition for open/free drivers
-Original Message- From: Enrico Weigelt [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 02, 2008 4:00 PM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Nvidia users: please sign petition for open/free drivers * Neil Bothwick [EMAIL PROTECTED] wrote: On Wed, 2 Jan 2008 11:33:36 -0600, Marzan, Richard non Unisys wrote: Keeping in mind that this petition probably might not work, I think it's a good idea to let Nvidia know how many people are interested in having free drivers. This might lead them to release information on how to write drivers for their hardware. The problem with this is that Nvidia license non-free code for use in their drivers. They are not allowed to distribute the source, or other information about the code, so they have two choices for Linux drivers: They could rewrite it step by step and release the rewritten parts to the community. At least the kernel module, it doesn't seem to be that complex (compared with the open code around it). cu -- - Enrico Weigelt== metux IT service - http://www.metux.de/ - Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ - -- [EMAIL PROTECTED] mailing list They want to protect their intellectual property. They paid for RD and they don't want to give that investment away. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] rejecting I/O to dead device
Hello
On Sun, Dec 30, 2007 at 10:47:42PM +0100, Fred Kastl wrote:
i get this message 2 -3 times within a second. This floods my logfile.
Dec 30 16:54:46 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:47 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:47 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:48 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:48 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:49 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:49 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:50 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:50 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:51 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:51 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:52 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
Dec 30 16:54:52 server kernel: scsi 2:0:0:0: rejecting I/O to dead
device
but there is no scsi device 2.
I get these if I unplug an USB disk while still mounted. Could that be
your case? (Until it is unmounted, programs can try to access it and
then the driver will just reject the read/write there)
## cat /proc/scsi/scsi
It lists only the ones alive, not dead.
--
_(){ __;};_
Michal 'vorner' Vaner
I got this to an internal USB card reader.
It used to shut off and only a system restart would fix it.
I never got it to work right so I took it out.
--
[EMAIL PROTECTED] mailing list
