IRC Logs

Network: freenode Channel: #hardware

	Enter your search terms Submit search form
	Web www.irclog.org

[16:14]<rjnd>heh
[16:14]<bfyssnw>Roey: almost surely it has not got VT, and if it has, it should be evident from '/proc/cpuinfo'.
[16:15]<cjrgjulijw>wow you're on a lot of channels
[16:16]<rjnd>Blissex: ahhh ok
[16:16]<rjnd>Blissex: what does the flag look like? Just 'vt' ?
[16:16]<rjnd>CoRnJuLIOx: so am I
[16:17]<rjnd>Blissex: do you log, btw?
[16:17]<rjnd>that must get pretty hefty if you do
[16:19]<rjnd>fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr
[16:19]<rjnd>those are the flag(z).
[16:19]<rjnd>is it vme?
[16:21]<bfyssnw>I don't log...
[16:22]<rjnd>oh
[16:22]<rjnd>ok.
[16:23]<bfyssnw>Roey: a simple web search says it is more like 'vmx'. But given that there are two variants (intel and AMD) who knows.
[16:24]<rjnd>ok
[16:26]<bfyssnw>look at 'arch/i386/kernel/cpu/proc.c' and 'include/asm/cpufeature.h' for the meanings
[16:44]<rjnd>oh, that's it
[16:44]<rjnd>thanks
[16:44]<rjnd>I was scouring google with "/proc/cpuinfo flags" for any tables I could find.
[17:02]<gunsvtqw79>is it normal that laptop battery only last 1 hour
[17:03]<ggpvugg>how old is it?
[17:03]<gunsvtqw79>i don't know
[17:03]<gunsvtqw79>but it's amd k6-3 550
[17:04]<rdnnqc>i have 2x4300mAh and it works at least 5h with a PIII-1000
[17:04]<rdnnqc>usual runtime however is 6-8h
[17:05]<rdnnqc>what OS?
[17:05]<gunsvtqw79>winxp
[17:05]<rdnnqc>hm...
[17:06]<rdnnqc>well you could try a real os from a live CD and see if you get better battery runtime
[17:16]<svjggggwv>Guest52164: depends on the laptop...
[17:30]<gunsvtqw79>but it's amd k6-3 550
[18:28]<svjggggwv>Guest52164: the TFT back light, batery, efficenty of the power system, GPU, powersaving effeciveness etc come into play
[18:44]<rdnnqc>*shrug*
[18:48]<svjggggwv>amee2k: well it's true :p
[18:48]<rdnnqc>i know
[18:49]<rdnnqc>i'm curious why he left
[18:50]<rdnnqc>well, neither my busines nor my problem ^_^
[19:43]<rdnnqc>hm...
[19:45]<rdnnqc>is it safe to assume, the range of I/O addresses on a (hardware) architecture is less or equal to the range of main memory addresses it has?
[19:46]<rdnnqc>like, a system with 32 bit memory addresses and 48 bit I/O addresses makes no sense
[19:58]<rdnnqc_>o.O
[19:58]<rdnnqc_>any thoughts?
[20:13]<bfyssnw>amee2k_: it could have 32 bit virtual memory addresses and 48 bit physical memory addresses.
[20:14]<bfyssnw>amee2k_: also it matters whether it is actual or potential addresses.
[20:19]<rdnnqc_>well, it /could/ have, but does that make sense?
[20:20]<rdnnqc_>what is the difference between actual and potential addresses?
[20:34]<snfmrnc>anyone around ? :|
[20:35]<rdnnqc_>yup
[20:35]<snfmrnc>I've just built a computer.. well.. it's on a table because I don't have the case yet
[20:36]<snfmrnc>and when booting (I make contact with the two power button pins) everything starts.. then stops.. starts. stops.. and so on
[20:36]<snfmrnc>I was hoping maybe the mb detects it's not connected to a case
[20:36]<snfmrnc>but I fear there is something else
[20:37]<rdnnqc_>usually mobos don't care if they are in a case or not
[20:37]<snfmrnc>yeah I thought so
[20:37]<rdnnqc_>i'm running two systems completely caseless here
[20:37]<snfmrnc>I just hoped the contrary..
[20:37]<snfmrnc>anyway, any idea what could do that ?
[20:38]<rdnnqc_>wait until your case arrives, then build it once and build it right
[20:38]<snfmrnc>hm
[20:38]<snfmrnc>I built it right
[20:38]<snfmrnc>at least I think I did
[20:38]<rdnnqc_>hm...
[20:38]<snfmrnc>well I thought, until it failed..
[20:39]<snfmrnc>I can take pics of the whole thing if that helps
[20:39]<rdnnqc_>1) remove /everything/ except PSU, CPU and RAM from the board and try again
[20:40]<rdnnqc_>2a) if you still have problems, it is with one of these three components. replace them to find the one that gives your trouble or start sending them back for RMA
[20:40]<snfmrnc>huh..:/
[20:40]<rdnnqc_>2) if it just runs now, start connecting the devices, one at a time
[20:41]<rdnnqc_>well, that is how i would go about pinning the problem down
[20:42]<snfmrnc>okay
[20:42]<snfmrnc>what about the 12V PCIE on the mb ?
[20:42]<snfmrnc>I guess I leave it there
[20:43]<rdnnqc_>an auxiliary cable from the PSU? leave it there
[20:43]<snfmrnc>hm
[20:43]<snfmrnc>auxiliary ?
[20:43]<snfmrnc>I have a 4pin molex (like hdd) 12V PCIE
[20:44]<snfmrnc>right on top of the main 24pin connector
[20:44]<rdnnqc_>hm...
[20:44]<rdnnqc_>leave it
[20:44]<rdnnqc_>if you have one, read the manual to find out what it is good for
[20:45]<rdnnqc_>(have a manual, that is)
[20:45]<snfmrnc>yeah
[20:45]<snfmrnc>well, "the pcie 12V power connector supplies extra power to the pcie x16 slot. connect this connector depending on your system requirements"
[20:47]<snfmrnc>tried with the molex plugged and unplugged in that thing, failure each time
[20:49]<svjggggwv>Seldaek: got all other conectors sorted too?
[20:49]<snfmrnc>I must go to eat, I'll try with only one ram at a time after that (I've 4gigs in there so there is room for failure)
[20:49]<snfmrnc>what do you mean sorted ?
[20:50]<svjggggwv>located properly
[20:50]<snfmrnc>I've the ATX12V 4pins (square) and ATX 24pins wired right now
[20:50]<snfmrnc>that's about it from the PSU
[20:50]<snfmrnc>by the way, its a gigabyte DS4 with E6600
[20:51]<svjggggwv>good good...
[20:51]<snfmrnc>yeah it if worked:)
[20:51]<svjggggwv>just wondering if you'd checked those that's all..
[20:51]<svjggggwv>gotta jet :)...

Back to #hardware
Or go to some related logs:
#netbsd
#gentoo
#php
#cisco
#gentoo