[gentoo-user] Error message in Xorg.log for intel xorg driver
Hi, I'm running a gentoo system on a computer with an intel onboard graphics card. lspci says: (snip) 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) 00:02.1 Display controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02) OK - there are TWO PCI IDs for graphics cards here. I used 00:02.0 in my xorg.conf. My monitor is connected to the PC via the digital connector (not the analog VGA connector, which is unused). Everyting is working fine (mostly), BUT in my Xorg.log.0 I always find following error messages (marked EE or WW): (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (EE) intel(0): First SDVO output reported failure to sync (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70. What do they mean? Can I get read of them? Is something wrong with my setup? Furthermore yesterday I had a total lockup when I came to work at the morning --- could not login at kdm, kdm would ignore all keyboard input etc. I had to do a hard restart with the "Magic SysRQ" key (remount ro, hard reboot). What's going on here? - TIA - Wolfgang
[gentoo-user] motherboard died?
Hi all, A few weeks ago there was a discussion about audio interference when running 3d applications. Well mine kept getting worse (it didn't to it at all a month ago) until I got fed up. I opened the side and (gently!) moved some of the power cables away from the data cables to see if that was a cause of interference. Well I did manage to reduce the noise by moving cables around but a couple of minutes later the machine bombed out with a big oops that I can't produce now. I didn't think it was a big problem, I thought I had just pulled an hdd cable a bit too hard or something. Now however, the machine won't post or even power up. It is an Asus Crosshair SKT AM2 nForce 590 SLI DDR2 which has a debug display on the back panel. As soon as you turn on the power to the motherboard, it displays "CPU INIT" which is the very first stage. Now trying to turn on the machine yields absolutely nothing, it just doesn't do a thing. I have removed all additional devices, just leaving 1 hdd. I've also reseated the CPU, RAM and all cables. I can't see how I could have properly killed some hardware just by moving a cable an inch to one side. If anyone has any ideas I'd be so grateful, I really don't want to have to return parts, I should be working on stuff right now :( Thanks Matt
Re: [gentoo-user] RAID0 + LVM2 + XFS : raid0_make_request bug
On Wed, 14 Jan 2009 20:58:53 +0100, Xav' wrote: > Hi everyone ! > > I've setted up a Xen server with kernel 2.6.18-r12 with 2 SATAII disks > of 750Go and with the following partitions scheme : > dom0 ~ # sfdisk -l > > Disk /dev/sda: 91201 cylinders, 255 heads, 63 sectors/track > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 > >Device Boot Start End #cyls#blocks Id System > /dev/sda1 * 0+ 64 65-522081 fd Linux raid autodetect > /dev/sda2 65 586 5224192965 fd Linux raid autodetect > /dev/sda3587 847 2612096482+ 82 Linux swap / Solaris > /dev/sda4848 91200 90353 725760472+ fd Linux raid autodetect > > Disk /dev/sdb: 91201 cylinders, 255 heads, 63 sectors/track > Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 > >Device Boot Start End #cyls#blocks Id System > /dev/sdb1 0+ 64 65-522081 fd Linux raid autodetect > /dev/sdb2 65 586 5224192965 fd Linux raid autodetect > /dev/sdb3587 847 2612096482+ 82 Linux swap / Solaris > /dev/sdb4848 91200 90353 725760472+ fd Linux raid autodetect > > dom0 ~ # cat /proc/mdstat > Personalities : [raid0] [raid1] > md1 : active raid1 sdb1[1] sda1[0] > 521984 blocks [2/2] [UU] > > md2 : active raid0 sdb2[1] sda2[0] > 8385792 blocks 64k chunks > > md3 : active raid0 sdb4[1] sda4[0] > 1451520768 blocks 64k chunks > > dom0 ~ # pvdisplay > File descriptor 3 left open > --- Physical volume --- > PV Name /dev/md3 > VG Name vg > PV Size 1,35 TB / not usable 768,00 KB > Allocatable yes > PE Size (KByte) 4096 > Total PE 354375 > Free PE 271815 > Allocated PE 82560 > PV UUID tJg59C-SN1z-SkYX-Qs5H-1TXV-ynNd-HhGTOZ > > unused devices: > > > I've created some guests using LVM logiccal volumes on /dev/md3 and > formatted with XFS filesystem. Sometimes, i've this messages in dmesg on > dom0 : > raid0_make_request bug: can't convert block across chunks or bigger than > 64k > > After that bugs, there is many Input/Output errors in the guest, and so > broke his gentoo installation so make me impossible to read the guest > system logs. Any help would be greatly appreciated as this server > actually host my primary DNS server and so i can't reinstall it from > scratch. > > Many thanks in advance. No one can help me ? I've already seeked on google for this problem, but this bug seemes to exists from 2003 and for kernel 2.4 or earlier 2.6.0 ... So any idea please ?? > Xavier > -- Xavier
Re: [gentoo-user] motherboard died?
On Thu, 15 Jan 2009 09:32:15 +, Matt Harrison wrote: > I can't see how I could have properly killed some hardware just by > moving a cable an inch to one side. Did you touch a grounded object before putting your hand inside the case. A static discharge could kill the motherboard. -- Neil Bothwick Top Oxymorons Number 40: Same difference signature.asc Description: PGP signature
Re: [gentoo-user] motherboard died?
Neil Bothwick wrote: On Thu, 15 Jan 2009 09:32:15 +, Matt Harrison wrote: I can't see how I could have properly killed some hardware just by moving a cable an inch to one side. Did you touch a grounded object before putting your hand inside the case. A static discharge could kill the motherboard. Thanks for the reply, Ashamed to say no I didn't consciously do that, however the only thing I touched inside the case was insulated cables. If i had zapped it, would it even get as far as it does? I know zapping it can be unpredictable, but up to a point, it works perfectly if you see what I mean. Matt
Re: [gentoo-user] motherboard died?
Matt Harrison wrote: > Hi all, > > A few weeks ago there was a discussion about audio interference when > running 3d applications. > > Well mine kept getting worse (it didn't to it at all a month ago) > until I got fed up. I opened the side and (gently!) moved some of the > power cables away from the data cables to see if that was a cause of > interference. > > Well I did manage to reduce the noise by moving cables around but a > couple of minutes later the machine bombed out with a big oops that I > can't produce now. > > I didn't think it was a big problem, I thought I had just pulled an > hdd cable a bit too hard or something. > > Now however, the machine won't post or even power up. It is an Asus > Crosshair SKT AM2 nForce 590 SLI DDR2 which has a debug display on the > back panel. > > As soon as you turn on the power to the motherboard, it displays "CPU > INIT" which is the very first stage. Now trying to turn on the machine > yields absolutely nothing, it just doesn't do a thing. > > I have removed all additional devices, just leaving 1 hdd. I've also > reseated the CPU, RAM and all cables. > > I can't see how I could have properly killed some hardware just by > moving a cable an inch to one side. > > If anyone has any ideas I'd be so grateful, I really don't want to > have to return parts, I should be working on stuff right now :( > > Thanks > > Matt > > Is it possible that a wire come a loose when you moved it? Maybe a power wire or something? Also, I don't think this could be it but could it be that the CPU fan isn't turning? It doesn't sound like it gets that far so that may not matter. Dale :-) :-)
Re: [gentoo-user] motherboard died?
Dale wrote: Matt Harrison wrote: Hi all, A few weeks ago there was a discussion about audio interference when running 3d applications. Well mine kept getting worse (it didn't to it at all a month ago) until I got fed up. I opened the side and (gently!) moved some of the power cables away from the data cables to see if that was a cause of interference. Well I did manage to reduce the noise by moving cables around but a couple of minutes later the machine bombed out with a big oops that I can't produce now. I didn't think it was a big problem, I thought I had just pulled an hdd cable a bit too hard or something. Now however, the machine won't post or even power up. It is an Asus Crosshair SKT AM2 nForce 590 SLI DDR2 which has a debug display on the back panel. As soon as you turn on the power to the motherboard, it displays "CPU INIT" which is the very first stage. Now trying to turn on the machine yields absolutely nothing, it just doesn't do a thing. I have removed all additional devices, just leaving 1 hdd. I've also reseated the CPU, RAM and all cables. I can't see how I could have properly killed some hardware just by moving a cable an inch to one side. If anyone has any ideas I'd be so grateful, I really don't want to have to return parts, I should be working on stuff right now :( Thanks Matt Is it possible that a wire come a loose when you moved it? Maybe a power wire or something? Also, I don't think this could be it but could it be that the CPU fan isn't turning? It doesn't sound like it gets that far so that may not matter. Dale :-) :-) I think I have reseated all the cables but I am happy to try again for luck :P
Re: [gentoo-user] motherboard died?
Dale wrote: Matt Harrison wrote: Dale wrote: Matt Harrison wrote: Hi all, A few weeks ago there was a discussion about audio interference when running 3d applications. Well mine kept getting worse (it didn't to it at all a month ago) until I got fed up. I opened the side and (gently!) moved some of the power cables away from the data cables to see if that was a cause of interference. Well I did manage to reduce the noise by moving cables around but a couple of minutes later the machine bombed out with a big oops that I can't produce now. I didn't think it was a big problem, I thought I had just pulled an hdd cable a bit too hard or something. Now however, the machine won't post or even power up. It is an Asus Crosshair SKT AM2 nForce 590 SLI DDR2 which has a debug display on the back panel. As soon as you turn on the power to the motherboard, it displays "CPU INIT" which is the very first stage. Now trying to turn on the machine yields absolutely nothing, it just doesn't do a thing. I have removed all additional devices, just leaving 1 hdd. I've also reseated the CPU, RAM and all cables. I can't see how I could have properly killed some hardware just by moving a cable an inch to one side. If anyone has any ideas I'd be so grateful, I really don't want to have to return parts, I should be working on stuff right now :( Thanks Matt Is it possible that a wire come a loose when you moved it? Maybe a power wire or something? Also, I don't think this could be it but could it be that the CPU fan isn't turning? It doesn't sound like it gets that far so that may not matter. Dale :-) :-) I think I have reseated all the cables but I am happy to try again for luck :P I was thinking maybe a wire came loose inside the connector itself. Reseating the cables may not work. Maybe unplug them and look inside to see if they have come loose. I ran into this a while back with my central heater. It came loose where it was crimped inside the connector and I had to solder it back on. May be a long shot tho. Dale :-) :-) Ah I see what you're saying. Yea it will be hard to spot so it'll take a while. I guess that's something to keep me busy. I've contacted Asus as well, so at least I've got some history if I really do have to RMA it. Thanks
Re: [gentoo-user] Network printing
On Wednesday 14 January 2009 08:58:11 Mick wrote: > Peter, ldap is only required if you are authenticating clients on your > LAN/WAN using an ldap server. If you had hundreds of clients and a need > to manage frequently changing client membership and passwds, then ldap > would be desirable to manage them effectively. Yes, I know what ldap is for, and that I have no use for it. I have a vague memory of an earlier version of cups requiring ldap, but the requirement seems to have gone away. I was just clutching at straws - still am. > Increasing the verbosity of the access and error cups logs will show you > what you need to (re)configure. It hasn't shown me yet, but I'll keep on plugging away at running test cases. Thanks to all for help so far. -- Rgds Peter
Re: [gentoo-user] motherboard died?
Matt Harrison wrote: > Dale wrote: >> Matt Harrison wrote: >>> Hi all, >>> >>> A few weeks ago there was a discussion about audio interference when >>> running 3d applications. >>> >>> Well mine kept getting worse (it didn't to it at all a month ago) >>> until I got fed up. I opened the side and (gently!) moved some of the >>> power cables away from the data cables to see if that was a cause of >>> interference. >>> >>> Well I did manage to reduce the noise by moving cables around but a >>> couple of minutes later the machine bombed out with a big oops that I >>> can't produce now. >>> >>> I didn't think it was a big problem, I thought I had just pulled an >>> hdd cable a bit too hard or something. >>> >>> Now however, the machine won't post or even power up. It is an Asus >>> Crosshair SKT AM2 nForce 590 SLI DDR2 which has a debug display on the >>> back panel. >>> >>> As soon as you turn on the power to the motherboard, it displays "CPU >>> INIT" which is the very first stage. Now trying to turn on the machine >>> yields absolutely nothing, it just doesn't do a thing. >>> >>> I have removed all additional devices, just leaving 1 hdd. I've also >>> reseated the CPU, RAM and all cables. >>> >>> I can't see how I could have properly killed some hardware just by >>> moving a cable an inch to one side. >>> >>> If anyone has any ideas I'd be so grateful, I really don't want to >>> have to return parts, I should be working on stuff right now :( >>> >>> Thanks >>> >>> Matt >>> >>> >> >> Is it possible that a wire come a loose when you moved it? Maybe a >> power wire or something? Also, I don't think this could be it but could >> it be that the CPU fan isn't turning? It doesn't sound like it gets >> that far so that may not matter. >> >> Dale >> >> :-) :-) > > I think I have reseated all the cables but I am happy to try again for > luck :P > > > > I was thinking maybe a wire came loose inside the connector itself. Reseating the cables may not work. Maybe unplug them and look inside to see if they have come loose. I ran into this a while back with my central heater. It came loose where it was crimped inside the connector and I had to solder it back on. May be a long shot tho. Dale :-) :-)
Re: [gentoo-user] RAID0 + LVM2 + XFS : raid0_make_request bug
Am Thursday 15 January 2009 10:43:52 schrieb Xav': > On Wed, 14 Jan 2009 20:58:53 +0100, Xav' wrote: > > I've setted up a Xen server with kernel 2.6.18-r12 with 2 SATAII disks > > of 750Go and with the following partitions scheme : > > dom0 ~ # sfdisk -l > > ... > > After that bugs, there is many Input/Output errors in the guest, and so > > broke his gentoo installation so make me impossible to read the guest > > system logs. Any help would be greatly appreciated as this server > > actually host my primary DNS server and so i can't reinstall it from > > scratch. > > > > Many thanks in advance. > > No one can help me ? I've already seeked on google for this problem, but > this bug seemes to exists from 2003 and for kernel 2.4 or earlier 2.6.0 ... > So any idea please ?? No, not really. We're not seeing specifically what you're seeing, but the I/O-error happening in the guest when the guest runs XFS and you do something to the guest in the Dom0 (I presume Soft-RAID counts as "doing something") is just the same (in our case, the I/O errors start happening more or less immediately when you snapshot the DomU in the Dom0 using standard LVM2 snapshots). The only workaround I've found so far is to not use XFS for 2.6.18-based Xen installations (2.6.20 does not seem to have this problem, but those are hard-masked because of not being maintained, and are for an older version of the hypervisor), and to use Ext3 on those systems. To get your data back, simply stop the guest (xm destroy), and mount the partition externally (mounting it in the Dom0 should work fine). Before you mount it, make sure you've run xfs_repair to correct any inconsistencies in the filesystem. After that, reformat the guests harddisk/partition with ext3, and replay the files. HTH! -- Heiko Wundram Gehrkens.IT GmbH FON 0511-59027953 | http://www.gehrkens.it FAX 0511-59027957 | http://www.xencon.net Gehrkens.IT GmbH Strasse der Nationen 5 30539 Hannover Registergericht: Amtsgericht Hannover, HRB 200551 Geschäftsführer: Harald Gehrkens, Daniel Netzer
Re: [gentoo-user] python-2.5.2-r7 build failure
On Tuesday 13 January 2009 22:50:55 Mark Knecht wrote: [...] > Compiling > /var/tmp/portage/dev-lang/python-2.5.2-r7/image//usr/lib/python2.5/zipfile.py >... [???] > make: *** [libinstall] Error 1 > * > * ERROR: dev-lang/python-2.5.2-r7 failed. [...] You've snipped the useful part, where I've indicated above with question marks. You need to find the first mention of an error. That should tell you what the problem is, or at least point to an investigation route. -- Rgds Peter
Re: [gentoo-user] motherboard died?
On Thu, Jan 15, 2009 at 4:32 AM, Matt Harrison wrote: > Hi all, > > A few weeks ago there was a discussion about audio interference when running > 3d applications. > > Well mine kept getting worse (it didn't to it at all a month ago) until I > got fed up. I opened the side and (gently!) moved some of the power cables > away from the data cables to see if that was a cause of interference. > > Well I did manage to reduce the noise by moving cables around but a couple > of minutes later the machine bombed out with a big oops that I can't produce > now. > > I didn't think it was a big problem, I thought I had just pulled an hdd > cable a bit too hard or something. > > Now however, the machine won't post or even power up. It is an Asus > Crosshair SKT AM2 nForce 590 SLI DDR2 which has a debug display on the back > panel. > > As soon as you turn on the power to the motherboard, it displays "CPU INIT" > which is the very first stage. Now trying to turn on the machine yields > absolutely nothing, it just doesn't do a thing. > > I have removed all additional devices, just leaving 1 hdd. I've also > reseated the CPU, RAM and all cables. > > I can't see how I could have properly killed some hardware just by moving a > cable an inch to one side. > > If anyone has any ideas I'd be so grateful, I really don't want to have to > return parts, I should be working on stuff right now :( > > Thanks > > Matt > > Hi Matt, My first guess would be that the audio interference would be a symptom of a bigger problem with the hardware. It is possible that static discharge or a loose connection could manifest these symptoms as well. I would start by verifying that everything is properly and securely plugged into the motherboard. After that, make a complete visual inspection of the board looking for capacitors that are bubbling or distorting outwards on the top (capacitors are the cylindrical components on the board, usually with two leads anchoring it to the PCB). From there, you should find some way of testing your power supply. Either find another machine into which you can plug the PSU to see if it posts the board, or take it to your local computer repair shop, as they should have a device to test it. If your power supply tests alright, begin removing components from the board to see if you can get it to post. Remove PCI cards, sticks of RAM, IDE/SATA connectors, front panel and USB connectors. Everything. If you reach the end of this diagnostic process without a single post, chances are your board is FUBAR and you should replace it. Cheers, D
Re: [gentoo-user] motherboard died?
Dan Cowsill wrote: On Thu, Jan 15, 2009 at 4:32 AM, Matt Harrison wrote: Hi all, A few weeks ago there was a discussion about audio interference when running 3d applications. Well mine kept getting worse (it didn't to it at all a month ago) until I got fed up. I opened the side and (gently!) moved some of the power cables away from the data cables to see if that was a cause of interference. Well I did manage to reduce the noise by moving cables around but a couple of minutes later the machine bombed out with a big oops that I can't produce now. I didn't think it was a big problem, I thought I had just pulled an hdd cable a bit too hard or something. Now however, the machine won't post or even power up. It is an Asus Crosshair SKT AM2 nForce 590 SLI DDR2 which has a debug display on the back panel. As soon as you turn on the power to the motherboard, it displays "CPU INIT" which is the very first stage. Now trying to turn on the machine yields absolutely nothing, it just doesn't do a thing. I have removed all additional devices, just leaving 1 hdd. I've also reseated the CPU, RAM and all cables. I can't see how I could have properly killed some hardware just by moving a cable an inch to one side. If anyone has any ideas I'd be so grateful, I really don't want to have to return parts, I should be working on stuff right now :( Thanks Matt Hi Matt, My first guess would be that the audio interference would be a symptom of a bigger problem with the hardware. It is possible that static discharge or a loose connection could manifest these symptoms as well. I would start by verifying that everything is properly and securely plugged into the motherboard. After that, make a complete visual inspection of the board looking for capacitors that are bubbling or distorting outwards on the top (capacitors are the cylindrical components on the board, usually with two leads anchoring it to the PCB). From there, you should find some way of testing your power supply. Either find another machine into which you can plug the PSU to see if it posts the board, or take it to your local computer repair shop, as they should have a device to test it. If your power supply tests alright, begin removing components from the board to see if you can get it to post. Remove PCI cards, sticks of RAM, IDE/SATA connectors, front panel and USB connectors. Everything. If you reach the end of this diagnostic process without a single post, chances are your board is FUBAR and you should replace it. Cheers, D Thanks for the detailed information. I have some news, but it requires me to put on my embarrassed face. The machine wouldn't turn on because...wait for itI'd pulled out the front panel connector block :P It was difficult to notice until I removed the graphics card because it completely hides it. I know I should have thought to check it. Now, on the subject of the audio problem, I am talking with Asus staff who believe it's (wouldn't you believe it) interference. They're smart cookies. Anyway, thanks for all the tips, I will be examining the board closely to find the source, but at least I can get my uni assignments in now :) Cheers Matt
Re: [gentoo-user] motherboard died?
On Thu, Jan 15, 2009 at 8:01 AM, Matt Harrison wrote: > Thanks for the detailed information. I have some news, but it requires me to > put on my embarrassed face. No need to be embarrassed! I work in the repair industry and I can't tell you how many times I've run into the same thing. The worst is when the button is stuck or there's a short in the block and you just can't figure out why it'll only stay on for a half second. I've given up trying to deal with Asus. Every technical support situation I've been in with them makes me want to visit unreasonable harm on cute fuzzy things. However, I've gotta say they do make some decent hardware. Good luck, D
Re: [gentoo-user] Network printing
2009/1/15 Peter Humphrey : > On Wednesday 14 January 2009 08:58:11 Mick wrote: >> Increasing the verbosity of the access and error cups logs will show you >> what you need to (re)configure. > > It hasn't shown me yet, but I'll keep on plugging away at running test > cases. > > Thanks to all for help so far. You're welcome. If you want help off-list email me your cupsd.conf and client(s).conf and I will look through them in case I find something. -- Regards, Mick
Re: [gentoo-user] Error message in Xorg.log for intel xorg driver
On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich wrote: > Furthermore yesterday I had a total lockup when I came to work at the > morning --- could not login at kdm, kdm would ignore all keyboard > input etc. I had to do a hard restart with the "Magic SysRQ" key > (remount ro, hard reboot). Do you have evdev installed? Without it, you probably won't have any keyboard or mouse. Recent xorg made dramatic changes to the way hardware is detected/configured by using HAL and evdev. xorg.conf is basically unused now when it comes to configuring hardware. I don't even have keyboard or mouse, or video modelines or anything like that in mine. Search the list archives or the gentoo web forums, there are many many people who had the same issues (assuming it's the cause of yours). Thanks, Paul
Re: [gentoo-user] Black Screen of Death
On Thu, 15 Jan 2009 15:38:57 +1030 Rick Harris wrote: > On Thu, 15 Jan 2009 07:32:31 am John wrote: > > Nothing in Xorg logs, system logs > > Lockup is complete - machine is totally unresposive even to ssh/ping > > x11-drivers/nvidia-drivers-177.82 > > Kernel version 2.6.27-gentoo-r7 > > Card is Geforce GO 6100. > > PC is laptop and logout has been working, maybe a update has done > > this and i have missed it. > > Is this common? > > Using syslog-ng, if you could advise on a config that may pick > > something up in logs > > I had a similar problem on my HP Compaq laptop, but not limited to > just logging out of an Xorg session, the hard freeze could occur at > any time. > > The solution for me was to add 'noapic nolapic noirqdebug' to my > kernel's boot parameters in grub.conf > (see /usr/src/linux/Documentation/kernel- parameters.txt). > > How does this relate to the nvidia driver not working and Xorg's 'nv' > driver working you might ask. The nvidia propietary driver > claims/shares an IRQ, the 'nv' driver does not (AFAICT). > > Either the APIC on my laptop or Linux's implementation of using it is > buggy, but the best result for me was to disable it using the above > kernel parameters. > > Something to try anyway, hope it helps :) > > > Cheers, > Rick > > Thanks guys for your suggestions. I tried "noapic nolapic noirqdebug" on boot parameters but no change. Also tried update xorg.conf but no use. Have now reinstalled older driver (173.14.15) and all is now working as expected. Although this is a beta driver. Will try an older driver and see what happens. Thanks for your help -- John D Maunder j...@articwolf.myzen.co.uk
[gentoo-user] e2fsprogs blocking question
Hi, I have a machine I haven't touched in about 6 months that I need to update. I've got one block that tells me (correctly) that it's part of system. It should be as I'm updating system. Anyway, it is OK to remove this block and then proceed with the system emerge, correct? I have already done an emerge -f and fetched everything that will be built. Thanks, Mark MacMini ~ # emerge -pvDuN system These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-devel/gnuconfig-20080123 [20070724] 0 kB [?=>0] [ebuild U ] app-arch/lzma-utils-4.32.7 [4.32.5] USE="-nocxx%" 0 kB [?=>0] [ebuild N] sys-apps/man-pages-posix-2003a 0 kB [0] [ebuild N] sys-libs/e2fsprogs-libs-1.41.3-r1 USE="nls" 0 kB [0] [ebuild U ] sys-apps/util-linux-2.14.1 [2.13.1] USE="crypt nls unicode -loop-aes -old-linux (-selinux) -slang (-uclibc)" 0 kB [0] [ebuild U ] sys-fs/e2fsprogs-1.41.3 [1.40.4] USE="nls (-static%)" 0 kB [0] [blocks b ] >> These are the packages that would be unmerged: !!! 'sys-fs/e2fsprogs' is part of your system profile. !!! Unmerging it may be damaging to your system. sys-fs/e2fsprogs selected: 1.40.4 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. MacMini ~ #
Re: [gentoo-user] e2fsprogs blocking question
On Thu, 15 Jan 2009 13:24:33 -0800, Mark Knecht wrote: >Anyway, it is OK to remove this block and then proceed with the > system emerge, correct? > > Calculating dependencies... done! > [ebuild U ] sys-devel/gnuconfig-20080123 [20070724] 0 kB [?=>0] > [ebuild U ] app-arch/lzma-utils-4.32.7 [4.32.5] USE="-nocxx%" 0 kB > [?=>0] > [ebuild N] sys-apps/man-pages-posix-2003a 0 kB [0] > [ebuild N] sys-libs/e2fsprogs-libs-1.41.3-r1 USE="nls" 0 kB [0] > [ebuild U ] sys-apps/util-linux-2.14.1 [2.13.1] USE="crypt nls > unicode -loop-aes -old-linux (-selinux) -slang (-uclibc)" 0 kB [0] > [ebuild U ] sys-fs/e2fsprogs-1.41.3 [1.40.4] USE="nls (-static%)" 0 > kB [0] [blocks b ] is blocking sys-libs/e2fsprogs-libs-1.41.3-r1) You don't need to remove anything, just let portage handle the block for you. Blocks marked with a b (instead of a B) can be handled by recent portage releases. -- Neil Bothwick Q. Why did the koala fall out of the tree? A. It was dead. signature.asc Description: PGP signature
Re: [gentoo-user] e2fsprogs blocking question
On Thu, Jan 15, 2009 at 1:30 PM, Neil Bothwick wrote: > On Thu, 15 Jan 2009 13:24:33 -0800, Mark Knecht wrote: > >>Anyway, it is OK to remove this block and then proceed with the >> system emerge, correct? >> >> Calculating dependencies... done! >> [ebuild U ] sys-devel/gnuconfig-20080123 [20070724] 0 kB [?=>0] >> [ebuild U ] app-arch/lzma-utils-4.32.7 [4.32.5] USE="-nocxx%" 0 kB >> [?=>0] >> [ebuild N] sys-apps/man-pages-posix-2003a 0 kB [0] >> [ebuild N] sys-libs/e2fsprogs-libs-1.41.3-r1 USE="nls" 0 kB [0] >> [ebuild U ] sys-apps/util-linux-2.14.1 [2.13.1] USE="crypt nls >> unicode -loop-aes -old-linux (-selinux) -slang (-uclibc)" 0 kB [0] >> [ebuild U ] sys-fs/e2fsprogs-1.41.3 [1.40.4] USE="nls (-static%)" 0 >> kB [0] [blocks b ] > is blocking sys-libs/e2fsprogs-libs-1.41.3-r1) > > You don't need to remove anything, just let portage handle the block for > you. Blocks marked with a b (instead of a B) can be handled by recent > portage releases. > > > -- > Neil Bothwick Really? Cool! Thanks Neil. - Mark
Re: [gentoo-user] motherboard died?
On Thu, 15 Jan 2009 08:24:55 -0500 Dan Cowsill wrote: > On Thu, Jan 15, 2009 at 8:01 AM, Matt Harrison > wrote: > > Thanks for the detailed information. I have some news, but it > > requires me to put on my embarrassed face. > > No need to be embarrassed! I work in the repair industry and I can't > tell you how many times I've run into the same thing. The worst is > when the button is stuck or there's a short in the block and you just > can't figure out why it'll only stay on for a half second. > > I've given up trying to deal with Asus. Every technical support > situation I've been in with them makes me want to visit unreasonable > harm on cute fuzzy things. However, I've gotta say they do make some > decent hardware. > > Good luck, > D Just a week or so ago I was switching from an IDE hard drive to SATA, a task which entailed adding SATA port to my kernel, tweaking grub, etc. At one point, when selecting a drive (by switching cables), the mobo end of the SATA cable got detached. Since I was experimenting with software settings I assumed a mistake was why the SATA drive was no longer visible. It was a while before I thought to check the cable. Sigh :-<
Re: [gentoo-user] motherboard died?
On Thu, Jan 15, 2009 at 4:30 PM, David Relson wrote: > On Thu, 15 Jan 2009 08:24:55 -0500 > Dan Cowsill wrote: > >> On Thu, Jan 15, 2009 at 8:01 AM, Matt Harrison >> wrote: >> > Thanks for the detailed information. I have some news, but it >> > requires me to put on my embarrassed face. >> >> No need to be embarrassed! I work in the repair industry and I can't >> tell you how many times I've run into the same thing. The worst is >> when the button is stuck or there's a short in the block and you just >> can't figure out why it'll only stay on for a half second. >> >> I've given up trying to deal with Asus. Every technical support >> situation I've been in with them makes me want to visit unreasonable >> harm on cute fuzzy things. However, I've gotta say they do make some >> decent hardware. >> >> Good luck, >> D > > Just a week or so ago I was switching from an IDE hard drive to SATA, a > task which entailed adding SATA port to my kernel, tweaking grub, etc. > At one point, when selecting a drive (by switching cables), the mobo > end of the SATA cable got detached. Since I was experimenting with > software settings I assumed a mistake was why the SATA drive was no > longer visible. It was a while before I thought to check the cable. > Sigh :-< I did the same thing when building my PC and thought I was doing something wrong. The aftermarket SATA cables I bought were VERY loose (with no locking mechanism), and the drives are packed in very tightly so the slightest bit of a touch on the cables causes them to dislodge.
Re: [gentoo-user] e2fsprogs blocking question
On Thu, Jan 15, 2009 at 10:30 PM, Neil Bothwick wrote: > On Thu, 15 Jan 2009 13:24:33 -0800, Mark Knecht wrote: > >>Anyway, it is OK to remove this block and then proceed with the >> system emerge, correct? >> >> Calculating dependencies... done! >> [ebuild U ] sys-devel/gnuconfig-20080123 [20070724] 0 kB [?=>0] >> [ebuild U ] app-arch/lzma-utils-4.32.7 [4.32.5] USE="-nocxx%" 0 kB >> [?=>0] >> [ebuild N] sys-apps/man-pages-posix-2003a 0 kB [0] >> [ebuild N] sys-libs/e2fsprogs-libs-1.41.3-r1 USE="nls" 0 kB [0] >> [ebuild U ] sys-apps/util-linux-2.14.1 [2.13.1] USE="crypt nls >> unicode -loop-aes -old-linux (-selinux) -slang (-uclibc)" 0 kB [0] >> [ebuild U ] sys-fs/e2fsprogs-1.41.3 [1.40.4] USE="nls (-static%)" 0 >> kB [0] [blocks b ] > is blocking sys-libs/e2fsprogs-libs-1.41.3-r1) > > You don't need to remove anything, just let portage handle the block for > you. Blocks marked with a b (instead of a B) can be handled by recent > portage releases. > Hi, are you sure that his works in this case? This blocking bug was some time before the new Portage went stable and back then you had to resolve it by hand. So if you're unlucky you have to resolve it by hand, but there's an explanation in bugzilla. Geralt.
Re: [gentoo-user] e2fsprogs blocking question
On Fri, 16 Jan 2009 00:00:07 +0100, Geralt wrote: > > You don't need to remove anything, just let portage handle the block > > for you. Blocks marked with a b (instead of a B) can be handled by > > recent portage releases. > are you sure that his works in this case? This blocking bug was some > time before the new Portage went stable and back then you had to > resolve it by hand. That's right, but now the new portage is stable so it is handled on stable systems. The block was handled automatically when it first appeared on ~arch systems. -- Neil Bothwick Is it true that cannibals don't eat clowns because they taste funny? signature.asc Description: PGP signature
[gentoo-user] rebuilding dependent packages
Hi, I recently did an emerge --update --deep world, which resulted in a rebuild of the ffmpeg library. The libavcodec library went from version 51 to 52, which broke transcode. The --deep argument did not find the dependency there and rebuild transcode. On my FreeBSD server, portupgrade has the -r and -R arguments to force rebuilds of dependent and reverse-dependent packages. Is there a way to have emerge do the same? Thanks, Mike -- Michael P. Soulier "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein pgpeIQ1ID8Z0q.pgp Description: PGP signature
Re: [gentoo-user] rebuilding dependent packages
Michael P. Soulier wrote: Hi, I recently did an emerge --update --deep world, which resulted in a rebuild of the ffmpeg library. The libavcodec library went from version 51 to 52, which broke transcode. The --deep argument did not find the dependency there and rebuild transcode. On my FreeBSD server, portupgrade has the -r and -R arguments to force rebuilds of dependent and reverse-dependent packages. Is there a way to have emerge do the same? Thanks, Mike I'm thinking you might want to check out revdep-rebuild from the gentoolkit package. --Joshua Doll
Re: [gentoo-user] rebuilding dependent packages
Joshua D Doll wrote: > Michael P. Soulier wrote: >> Hi, >> >> I recently did an emerge --update --deep world, which resulted in a >> rebuild of >> the ffmpeg library. >> The libavcodec library went from version 51 to 52, which broke >> transcode. The >> --deep argument did not find the dependency there and rebuild transcode. >> On my FreeBSD server, portupgrade has the -r and -R arguments to force >> rebuilds of dependent and reverse-dependent packages. Is there a way >> to have >> emerge do the same? >> >> Thanks, >> Mike >> > I'm thinking you might want to check out revdep-rebuild from the > gentoolkit package. > > --Joshua Doll > > Would --with-bdeps y help here? I'm not sure it would. Just a thought. Dale :-) :-)
Re: [gentoo-user] rebuilding dependent packages
On 15/01/09 Joshua D Doll said: > I'm thinking you might want to check out revdep-rebuild from the gentoolkit > package. I'm not sure that would find the dependency, since transcode dynamically loads said module at runtime, AFAICT. Perhaps that is the issue. Mike -- Michael P. Soulier "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein pgpxhH4PX6LUB.pgp Description: PGP signature
Re: [gentoo-user] e2fsprogs blocking question
2009/1/15 Neil Bothwick > On Fri, 16 Jan 2009 00:00:07 +0100, Geralt wrote: > > > > You don't need to remove anything, just let portage handle the block > > > for you. Blocks marked with a b (instead of a B) can be handled by > > > recent portage releases. > > > are you sure that his works in this case? This blocking bug was some > > time before the new Portage went stable and back then you had to > > resolve it by hand. > > That's right, but now the new portage is stable so it is handled on > stable systems. The block was handled automatically when it first appeared > on ~arch systems. > > > -- > Neil Bothwick > > Is it true that cannibals don't eat clowns because they taste funny? > Which version of portage do this? I am on amd64 stable and have the problem a couple of week ago, and i don/t remember any portage update,,,
Re: [gentoo-user] rebuilding dependent packages
Michael P. Soulier wrote: > On 15/01/09 Joshua D Doll said: > > >> I'm thinking you might want to check out revdep-rebuild from the gentoolkit >> package. >> > > I'm not sure that would find the dependency, since transcode dynamically loads > said module at runtime, AFAICT. Perhaps that is the issue. > > Mike > If the library is broken, it should find it. You can run revdep-rebuild -i -p and just see what it says. It won't do anything until you remove the -p part. Dale :-) :-)
[gentoo-user] uvesafb - does it require use of initramfs/initrd?
Hi, Does anyone here use uvesafb? I followed the instructions to install uvesafb from this page: http://dev.gentoo.org/~spock/projects/uvesafb/ However, it does not work. Is it required to use initrd in order to use uvesafb? (because I don't use it...) the 80x25 looks absolutely horrible and I'd love to have something usable without needing to be in X. I have an nvidia geforce 9600GT card using the latest nvidia-drivers, and am on amd64 if it matters. Thanks, Paul
[gentoo-user] Bash & Server Sockets
Hi all, In Bash /dev/tcp/host/port can be used to write to a TCP socket. This works nicely so I was very curious whether it would work the other way too: is it possible to have a Bash script listen on a particular port as if it were a server? I couldn't find anything in the Bash manual about it. Google does find a few examples but they all use nc. But that's cheating! ;-) Is it possible with just Bash, no extra tools? (If yes, please enlighten me as to how, obviously I could not get it to work.) On a related note, I read some comments about Debian having /dev/tcp disabled in Bash because of security concerns. Would someone knowledgeable about security be able to comment on that? It doesn't make much sense to me. I mean, any Perl, Python, Ruby, etcetera script can write to a socket. Even Debian (with every option deselected) comes installed with Perl. (Yes, I installed Debian just to find out!) :-) So why should /dev/tcp in Bash be deemed such a security risk? Cheers, Hilco P.S. For the curious: #!/bin/bash exec 3<>/dev/tcp/www.google.ca/80 echo -ne "GET / HTTP/1.1\r\n">&3 echo -ne "Host: www.google.ca\r\n">&3 echo -ne "Connection: close\r\n">&3 echo -ne "\r\n">&3 cat <&3
[gentoo-user] Re: uvesafb - does it require use of initramfs/initrd?
Paul Hartman wrote: Hi, Does anyone here use uvesafb? I followed the instructions to install uvesafb from this page: http://dev.gentoo.org/~spock/projects/uvesafb/ However, it does not work. Is it required to use initrd in order to use uvesafb? (because I don't use it...) the 80x25 looks absolutely horrible and I'd love to have something usable without needing to be in X. I have an nvidia geforce 9600GT card using the latest nvidia-drivers, and am on amd64 if it matters. You can use vesafb instead of uvesafb.
Re: [gentoo-user] Error message in Xorg.log for intel xorg driver
On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote: > On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich > wrote: > > Furthermore yesterday I had a total lockup when I came to work at the > > morning --- could not login at kdm, kdm would ignore all keyboard > > input etc. I had to do a hard restart with the "Magic SysRQ" key > > (remount ro, hard reboot). > > Do you have evdev installed? Without it, you probably won't have any > keyboard or mouse. Recent xorg made dramatic changes to the way > hardware is detected/configured by using HAL and evdev. xorg.conf is > basically unused now when it comes to configuring hardware. I don't > even have keyboard or mouse, or video modelines or anything like that > in mine. Search the list archives or the gentoo web forums, there are > many many people who had the same issues (assuming it's the cause of > yours). Evdev is installed, but I configured the kbd driver (I have a MS Natural Keyboard, btw --- what's the best driver for that keyboard?). I still have an xorg.conf (and I'm not very inclined to change it as long as it works :-). Furthermore -- after the reboot everything worked again as before. It seems to have been some fluke, but I want to know where it comes from. TIA, Wolfgang
Re: [gentoo-user] Re: uvesafb - does it require use of initramfs/initrd?
On Fri, Jan 16, 2009 at 12:33 AM, Nikos Chantziaras wrote: > Paul Hartman wrote: >> >> Hi, >> >> Does anyone here use uvesafb? I followed the instructions to install >> uvesafb from this page: >> >> http://dev.gentoo.org/~spock/projects/uvesafb/ >> >> However, it does not work. Is it required to use initrd in order to >> use uvesafb? (because I don't use it...) >> >> the 80x25 looks absolutely horrible and I'd love to have something >> usable without needing to be in X. I have an nvidia geforce 9600GT >> card using the latest nvidia-drivers, and am on amd64 if it matters. > > You can use vesafb instead of uvesafb. I'll try it. I thought there was some conflict between the other framebuffers and nvidia drivers, so i never even attempted the other in-kernel FBs.
Re: [gentoo-user] Error message in Xorg.log for intel xorg driver
Wolfgang Liebich wrote: > On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote: > >> On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich >> wrote: >> >>> Furthermore yesterday I had a total lockup when I came to work at the >>> morning --- could not login at kdm, kdm would ignore all keyboard >>> input etc. I had to do a hard restart with the "Magic SysRQ" key >>> (remount ro, hard reboot). >>> >> Do you have evdev installed? Without it, you probably won't have any >> keyboard or mouse. Recent xorg made dramatic changes to the way >> hardware is detected/configured by using HAL and evdev. xorg.conf is >> basically unused now when it comes to configuring hardware. I don't >> even have keyboard or mouse, or video modelines or anything like that >> in mine. Search the list archives or the gentoo web forums, there are >> many many people who had the same issues (assuming it's the cause of >> yours). >> > > Evdev is installed, but I configured the kbd driver (I have a MS > Natural Keyboard, btw --- what's the best driver for that keyboard?). > I still have an xorg.conf (and I'm not very inclined to change it as > long as it works :-). > > Furthermore -- after the reboot everything worked again as before. It > seems to have been some fluke, but I want to know where it comes from. > > TIA, > Wolfgang > > Someone else like me. I still have my xorg.conf and want to keep it too. I don't have evdev installed but from the way it sounds, me and you may have to change in the future, maybe near future. I'm sort of wondering what pulls in evdev anyway? I got a fully running KDE and this is my new install. Nothing pulled it in here. I may be missing a USE flag or something. Let's hope this works for a while longer yet. ;-) Dale :-) :-)
[gentoo-user] Why is texlive 2008 still masked ~x86
Hi, I've completed my switch from tetex to texlive 2007 now. I'm (normally) running only stable packages, so texlive is still at 2007. What's keeping texlive 2008 from being stable? Just asking... - Wolfgang
[gentoo-user] gcc, two problems
Hi! I use ~amd64. 1. Just after synching I have: emerge -pvDuN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-devel/gcc-4.2.4-r1 [4.2.4] USE="fortran gcj mudflap (multilib) nls openmp (-altivec) -bootstrap -build -doc -gtk (-hardened) -ip28 -ip32r10k -libffi -multislot (-n32) (-n64) -nocxx -objc -objc++ -objc-gc -test -vanilla" 0 kB The building ends with strange errors: /wrk/tmp/portage/portage/sys-devel/gcc-4.2.4- r1/work/gcc-4.2.4/gcc/config/i386/crtfastmath.c:1: error: bad value (core2) for -march= switch /wrk/tmp/portage/portage/sys-devel/gcc-4.2.4- r1/work/gcc-4.2.4/gcc/config/i386/crtfastmath.c:1: error: bad value (core2) for -mtune= switch make[3]: *** [crtfastmath.o] Error 1 Have not found appropriate bug (don't believe I'm the first in upgrading :-)). Thoughts? 2. Here http://packages.gentoo.org/package/sys-devel/gcc gcc-4.3.2 exists for ~amd64 and is unmasked. Why 'emerge -pvDuN world' does not see new gcc version?
Re: [gentoo-user] Error message in Xorg.log for intel xorg driver
On Fri, Jan 16, 2009 at 12:59 AM, Dale wrote: > Wolfgang Liebich wrote: >> On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote: >> >>> On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich >>> wrote: >>> Furthermore yesterday I had a total lockup when I came to work at the morning --- could not login at kdm, kdm would ignore all keyboard input etc. I had to do a hard restart with the "Magic SysRQ" key (remount ro, hard reboot). >>> Do you have evdev installed? Without it, you probably won't have any >>> keyboard or mouse. Recent xorg made dramatic changes to the way >>> hardware is detected/configured by using HAL and evdev. xorg.conf is >>> basically unused now when it comes to configuring hardware. I don't >>> even have keyboard or mouse, or video modelines or anything like that >>> in mine. Search the list archives or the gentoo web forums, there are >>> many many people who had the same issues (assuming it's the cause of >>> yours). >>> >> >> Evdev is installed, but I configured the kbd driver (I have a MS >> Natural Keyboard, btw --- what's the best driver for that keyboard?). >> I still have an xorg.conf (and I'm not very inclined to change it as >> long as it works :-). >> >> Furthermore -- after the reboot everything worked again as before. It >> seems to have been some fluke, but I want to know where it comes from. >> >> TIA, >> Wolfgang >> >> > > Someone else like me. I still have my xorg.conf and want to keep it > too. I don't have evdev installed but from the way it sounds, me and > you may have to change in the future, maybe near future. > > I'm sort of wondering what pulls in evdev anyway? I got a fully running > KDE and this is my new install. Nothing pulled it in here. I may be > missing a USE flag or something. > > Let's hope this works for a while longer yet. ;-) > > Dale > > :-) :-) > > You need "evdev" in your INPUT_DEVICES variable (mine lives in make.conf). In my case I have: INPUT_DEVICES="keyboard mouse joystick evdev" and portage automagically built those packages.
Re: [gentoo-user] Why is texlive 2008 still masked ~x86
Wolfgang Liebich schrieb: > Hi, > I've completed my switch from tetex to texlive 2007 now. I'm (normally) > running only stable packages, so texlive is still at 2007. > What's keeping texlive 2008 from being stable? > Just asking... > - Wolfgang > > http://bugs.gentoo.org/show_bug.cgi?id=253990 signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Error message in Xorg.log for intel xorg driver
Paul Hartman wrote: > On Fri, Jan 16, 2009 at 12:59 AM, Dale wrote: > >> Wolfgang Liebich wrote: >> >>> On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote: >>> >>> On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich wrote: > Furthermore yesterday I had a total lockup when I came to work at the > morning --- could not login at kdm, kdm would ignore all keyboard > input etc. I had to do a hard restart with the "Magic SysRQ" key > (remount ro, hard reboot). > > Do you have evdev installed? Without it, you probably won't have any keyboard or mouse. Recent xorg made dramatic changes to the way hardware is detected/configured by using HAL and evdev. xorg.conf is basically unused now when it comes to configuring hardware. I don't even have keyboard or mouse, or video modelines or anything like that in mine. Search the list archives or the gentoo web forums, there are many many people who had the same issues (assuming it's the cause of yours). >>> Evdev is installed, but I configured the kbd driver (I have a MS >>> Natural Keyboard, btw --- what's the best driver for that keyboard?). >>> I still have an xorg.conf (and I'm not very inclined to change it as >>> long as it works :-). >>> >>> Furthermore -- after the reboot everything worked again as before. It >>> seems to have been some fluke, but I want to know where it comes from. >>> >>> TIA, >>> Wolfgang >>> >>> >>> >> Someone else like me. I still have my xorg.conf and want to keep it >> too. I don't have evdev installed but from the way it sounds, me and >> you may have to change in the future, maybe near future. >> >> I'm sort of wondering what pulls in evdev anyway? I got a fully running >> KDE and this is my new install. Nothing pulled it in here. I may be >> missing a USE flag or something. >> >> Let's hope this works for a while longer yet. ;-) >> >> Dale >> >> :-) :-) >> >> >> > > You need "evdev" in your INPUT_DEVICES variable (mine lives in > make.conf). In my case I have: > > INPUT_DEVICES="keyboard mouse joystick evdev" > > and portage automagically built those packages. > > > So if evdev failed for some reason, it would fall back to the keyboard and mouse drivers you think? That I would be willing to try if that is the case. Dale :-) :-)
[gentoo-user] Re: uvesafb - does it require use of initramfs/initrd?
On Thu, Jan 15, 2009 at 11:49 PM, Paul Hartman wrote: > Hi, > > Does anyone here use uvesafb? I followed the instructions to install > uvesafb from this page: > > http://dev.gentoo.org/~spock/projects/uvesafb/ > > However, it does not work. Is it required to use initrd in order to > use uvesafb? (because I don't use it...) > > the 80x25 looks absolutely horrible and I'd love to have something > usable without needing to be in X. I have an nvidia geforce 9600GT > card using the latest nvidia-drivers, and am on amd64 if it matters. > > Thanks, > Paul > I'm ashamed to admit I made the most basic mistake. I compiled uvesafb as a module. Oops! Compiled it as "Y" instead of "M" and now I have a pair of Tux sitting atop my kernel boot screen and no more 80x25 horror. :) Thanks, Paul
Re: [gentoo-user] gcc, two problems
On Fri, Jan 16, 2009 at 1:14 AM, Andrew Gaydenko wrote: > Hi! > > I use ~amd64. > > 1. Just after synching I have: > > emerge -pvDuN world > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild U ] sys-devel/gcc-4.2.4-r1 [4.2.4] USE="fortran gcj mudflap > (multilib) nls openmp (-altivec) -bootstrap -build -doc -gtk (-hardened) -ip28 > -ip32r10k -libffi -multislot (-n32) (-n64) -nocxx -objc -objc++ -objc-gc -test > -vanilla" 0 kB > > The building ends with strange errors: > > /wrk/tmp/portage/portage/sys-devel/gcc-4.2.4- > r1/work/gcc-4.2.4/gcc/config/i386/crtfastmath.c:1: error: bad value (core2) > for -march= switch > /wrk/tmp/portage/portage/sys-devel/gcc-4.2.4- > r1/work/gcc-4.2.4/gcc/config/i386/crtfastmath.c:1: error: bad value (core2) > for -mtune= switch > make[3]: *** [crtfastmath.o] Error 1 > > Have not found appropriate bug (don't believe I'm the first in upgrading :-)). > Thoughts? > > 2. Here http://packages.gentoo.org/package/sys-devel/gcc gcc-4.3.2 exists for > ~amd64 and is unmasked. Why 'emerge -pvDuN world' does not see new gcc > version? > > it is slotted, gcc:4.3
Re: [gentoo-user] Error message in Xorg.log for intel xorg driver
On Fri, Jan 16, 2009 at 1:36 AM, Dale wrote: > Paul Hartman wrote: >> On Fri, Jan 16, 2009 at 12:59 AM, Dale wrote: >> >>> Wolfgang Liebich wrote: >>> On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote: > On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich > wrote: > > >> Furthermore yesterday I had a total lockup when I came to work at the >> morning --- could not login at kdm, kdm would ignore all keyboard >> input etc. I had to do a hard restart with the "Magic SysRQ" key >> (remount ro, hard reboot). >> >> > Do you have evdev installed? Without it, you probably won't have any > keyboard or mouse. Recent xorg made dramatic changes to the way > hardware is detected/configured by using HAL and evdev. xorg.conf is > basically unused now when it comes to configuring hardware. I don't > even have keyboard or mouse, or video modelines or anything like that > in mine. Search the list archives or the gentoo web forums, there are > many many people who had the same issues (assuming it's the cause of > yours). > > Evdev is installed, but I configured the kbd driver (I have a MS Natural Keyboard, btw --- what's the best driver for that keyboard?). I still have an xorg.conf (and I'm not very inclined to change it as long as it works :-). Furthermore -- after the reboot everything worked again as before. It seems to have been some fluke, but I want to know where it comes from. TIA, Wolfgang >>> Someone else like me. I still have my xorg.conf and want to keep it >>> too. I don't have evdev installed but from the way it sounds, me and >>> you may have to change in the future, maybe near future. >>> >>> I'm sort of wondering what pulls in evdev anyway? I got a fully running >>> KDE and this is my new install. Nothing pulled it in here. I may be >>> missing a USE flag or something. >>> >>> Let's hope this works for a while longer yet. ;-) >>> >>> Dale >>> >>> :-) :-) >>> >>> >>> >> >> You need "evdev" in your INPUT_DEVICES variable (mine lives in >> make.conf). In my case I have: >> >> INPUT_DEVICES="keyboard mouse joystick evdev" >> >> and portage automagically built those packages. >> >> >> > > So if evdev failed for some reason, it would fall back to the keyboard > and mouse drivers you think? That I would be willing to try if that is > the case. > > Dale > > :-) :-) > > I don't know, for me it simply works as intended so... maybe I'll try to remove the keyboard and mouse and see what happens :) but in my case my xorg.conf is virtually empty aside from some fonts and nvidia card options. My display and input devices "just work" without being specified in xorg.conf with drivers, modelines or any of that stuff. I changed monitors yesterday and simply killed X and it restarted in the optimal resolution for the new monitor. I've plugged different mouse/keyboard and it just works automatically. The HAL policies in /etc/hal/fdi/policy contain the same exact settings as xorg.conf only formatted a little differently... you can give device-specific custom settings if you need and I think everything you have done in xorg.conf can be done the new way.
