Re: [gentoo-user] ntpd crashing
On Tue, 2012-01-10 at 23:57 +, Peter Humphrey wrote: On Tuesday 10 January 2012 21:45:21 Jeff Cranmer wrote: Initially, the RTC options were not enabled in my kernel, but even after setting these, I'm still getting this error. I'm adding all the device drivers as modules and trying again to see if I can remove this error. I suspect it is the root cause of my ntp issues. It's possible that your kernel is creating /dev/rtc0 instead of /dev/rtc. What does ls -d /dev/rt* show? -- Rgds Peter Linux Counter 5290, 1994-04-23 There's nothing in /dev/rt* :-(
Re: [gentoo-user] How to get raid
This is true, however it's a temporary measure only, and I have backups. Once the prices drop again, I'll buy another 1.5TB disk and convert back to a RAID5. On Tue, 2012-01-10 at 13:14 +0700, Pandu Poluan wrote: On Jan 10, 2012 8:48 AM, Jeff Cranmer j...@lotussevencars.com wrote: Me too. mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty. I'm not sure whether it's really faulty, or just that my setup for RAID is screwed up. How do I get rid of an existing /dev/md0? you stop it. Override the superblock with dd.. and lose all data on the disks. I'm thinking that I can try creating a RAID1 array using the two allegedly good disks and see if I can make that work. yeah If that works, I'll get rid of it and try recreating the RAID1 with one good disk and the one that mdadm thinks is faulty. you don't have to. You can migrate a 2 disk raid1 to a 3 disk raid5. Howtos are availble via google. just saying - box in suspend to ram. I change the cable (and connector on mobo) on a disk with two raid 1 partitions on it. One came back after starting the box. The other? Nothing I tried worked. At the end I dd'ed the partition.. and did a complete 'faulty disk/replacement' resync argl. OK, so lesson learned. Just because it builds correctly in a RAID1 array, that doesn't mean that the drive isn't toast. I ran badblocks on the three drive components and, surprise, surprise, /dev/sdc came up faulty. I think I'll just build the two non-faulty drives as a RAID0 array until the hard drive prices come back down to pre-Thailand flood prices and backup regularly. Thanks for all the help. Jeff RAID 0?!?! Please reconsider. With RAID 0, *any* single drive failure will result in *total* data loss. Rgds,
Re: [gentoo-user] ntpd crashing
On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote: Define crashing? This looks more like problems with yout TZ variables than ntpd. try ntpq -p to check if its actually running/locked. If ntpd is freewheeling, it is prpbably because your time is too far from lock so it will silently fail (default config). If ntpd has really crashed (ps aux will confirm), try running the daemon manually from a console - if it segfaults or comes up with a missing library, try ldd /usr/sbin/ntpd to find which lib is needed and fix. BillK ntpd -p returns: ntpq: read: Connection refused /etc/init.d/ntpd status returns: * status: crashed /etc/init.d/ntpd stop returns * Caching service dependencies ... [ ok ] * Stopping ntpd ... * start-stop-daemon: no matching processes found I tried running /usr/sbin/ntpd from a console, and nothing much happens. There now appears to be a process running for ntpd, but my time is still wrong. ps -aux shows root 21470 0.0 0.0 26140 1908 ?Ss 07:22 0:00 /usr/sbin/ntpd ntpq -p now returns remote refid st t when poll reach delay offset jitter == ntp.cox.net .GPS.1 u5 647 42.229 1800133 3.020 235-69-67-68.st 130.88.200.6 3 u4 647 47.125 1800132 1.457 clock.team-cymr 172.16.65.22 2 u3 647 50.691 1800132 0.905 sulfur.mednor.n 164.67.62.1942 u1 647 88.498 1800131 2.870 After a few minutes, I repeated ntpq -p, and got connection refused. The program is crashed. No error messages appear in the command window. The offset is large, which may be why it's crashing. There may be some problem setting the hardware clock, since I had an error on bootup stating that I was unable to set the hardware clock by any method until I set clock_systohc=NO in /etc/conf.d/hwclock (which just prevents it trying to set the hardware clock). hwclock --debug output may be useful: hwclock from util-linux 2.20.1 hwclock: Open of /dev/rtc failed: No such file or directory No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. Jeff
Re: [gentoo-user] ntpd crashing
On Tue, 2012-01-10 at 13:02 -0600, Dale wrote: Florian Philipp wrote: Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Regards, Florian Philipp Two things. One, you need to set the clock manually since it is s far off. I would do this: ntpdate -b -u pool.ntp.org then start ntpd. Second thing, if you are dual booting with windows, you have to edit the config file to set it correctly: It is set in /etc/conf.d/hwclock and it has a message about how to set it. I think it is UTC. It tells you in the file tho. If it is not in yours, let me know and I'll post it. Dale :-) :-) Thanks. ntpdate -b -u pool.ntp.org synchronised my clock. My system is not tainted by Windoze, so no problems there. I'm still a little concerned by the results of hwclock --debug hwclock from util-linux 2.20.1 hwclock: Open of /dev/rtc failed: No such file or directory No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. Initially, the RTC options were not enabled in my kernel, but even after setting these, I'm still getting this error. I'm adding all the device drivers as modules and trying again to see if I can remove this error. I suspect it is the root cause of my ntp issues. Jeff
Re: [gentoo-user] How to get raid
Success - I managed to get a raid1 device operating. I created the final filesystem by using mkfs.xfs -f /dev/md0, then waited for the rebuild to complete before rebooting the system. It appears to be created successfully. Now I'll try the same sequence with sdb and sdc to see if sdc is a good disk. If that works, I'll retry a raid5 array tomorrow night. Hmm - it seems to be a bug in RAID5 creation. I can successfully create a RAID1 array either /dev/sdb1 and /dev/sdc1 or /dev/sdb1 and /dev/sdd1 If, however, I try to create a RAID5 array with all three elements, I get /dev/sdc reporting a failure. cat /proc/mdstat fails with the following report. Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md0 : active raid5 sdd1[3](S) sdc1[1](F) sdb1[0] 2930272256 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/1] [U__] unused devices: none Has anyone else experienced similar problems? Is there an extra diagnostic procedure which I can use to validate the sdc drive? Is there something extra I have to do when I go over the 2TB level which could explain this goofy behaviour?
Re: [gentoo-user] How to get raid
Me too. mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty. I'm not sure whether it's really faulty, or just that my setup for RAID is screwed up. How do I get rid of an existing /dev/md0? you stop it. Override the superblock with dd.. and lose all data on the disks. I'm thinking that I can try creating a RAID1 array using the two allegedly good disks and see if I can make that work. yeah If that works, I'll get rid of it and try recreating the RAID1 with one good disk and the one that mdadm thinks is faulty. you don't have to. You can migrate a 2 disk raid1 to a 3 disk raid5. Howtos are availble via google. just saying - box in suspend to ram. I change the cable (and connector on mobo) on a disk with two raid 1 partitions on it. One came back after starting the box. The other? Nothing I tried worked. At the end I dd'ed the partition.. and did a complete 'faulty disk/replacement' resync argl. OK, so lesson learned. Just because it builds correctly in a RAID1 array, that doesn't mean that the drive isn't toast. I ran badblocks on the three drive components and, surprise, surprise, /dev/sdc came up faulty. I think I'll just build the two non-faulty drives as a RAID0 array until the hard drive prices come back down to pre-Thailand flood prices and backup regularly. Thanks for all the help. Jeff
[gentoo-user] ntpd crashing
Hi, Can anyone give me any pointers as to how to diagnose a problem with ntpd crashing. My time keeps defaulting to 5 hours earlier than it should. There's nothing in dmesg when I do dmesg | grep time, or dmesg | grep ntp, but /etc/init.d/ntpd status tells me that ntpd has crashed. Jeff
Re: [gentoo-user] How to get raid
On Sun, 2012-01-08 at 12:31 -0600, Paul Hartman wrote: What is going on here? (I didn't read this whole thread, sorry if I'm repeating someone else's advice) kernel autodetection only works on old superblock version 0.90, you're using 1.2. Not a big deal, we use mdadm to do it. Define your arrays in /etc/mdadm.conf and start /etc/init.d/mdadm in your boot runscripts with rc-update add mdadm boot, it will bring up the array at boot time. In my mdadm.conf i have a line like this: ARRAY /dev/md1 metadata=1.01 name=black:1 UUID=8e653e72:9d5df6ba:bb66ea8b:02f1c317 (might be word-wrapped, should be all one line) That's all that was needed to bring it up automatically at boot time. Also AFAIR there was a gotcha about the hostname stored in the array's metadata must match your machine's hostname or else mdadm auto-assemble won't accept it (to protect you in case you're plugging disks from another machine for recovery, you don't want it to use them as your main drives), so in that case you must specify it explicitly or set the AUTO parameter in mdadm.conf to accept this condition. If you created the array from within a LiveCD or on another machine, the hostname might not match your system. See the mdadm manpage for more info. mdadm was added to the default level, not boot. My /etc/mdadm.conf file has two active lines DEVICE /dev/sd[bcd]1 ARRAY dev/md0 metadata=1.2 spares=1 name=office-desktop:0 devices=/dev/sdb1,dev/sdc1,/dev/sdd1 It looks like I'm having trouble with a faulty /dev/sdc1, so what I'd like to do is wipe out the existing array and try starting a RAID1 array just with sdb1 and sdd1. I got rid of the old array by using the commands mdadm --manage --fail /dev/md0 mdadm --manage --stop /dev/md0 I then used mdadm --verbose --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb1 /dev/sdd1 The result of this command was dadm: /dev/sdb1 appears to be part of a raid array: level=raid5 devices=3 ctime=Sat Jan 7 08:16:00 2012 mdadm: partition table exists on /dev/sdb1 but will be lost or meaningless after creating array mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90 mdadm: /dev/sdd1 appears to be part of a raid array: level=raid5 devices=3 ctime=Sat Jan 7 08:16:00 2012 mdadm: size set to 1465136400K Continue creating array? y mdadm: Defaulting to version 1.2 metadata mdadm: array /dev/md0 started. The results of cat /proc/mdstat are Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md0 : active raid1 sdd1[1] sdb1[0] 1465136400 blocks super 1.2 [2/2] [UU] [] resync = 2.1% (31838144/1465136400) finish=269.7min speed=88551K/sec unused devices: none Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md0 : active raid1 sdd1[1] sdb1[0] 1465136400 blocks super 1.2 [2/2] [UU] [] resync = 2.1% (31838144/1465136400) finish=269.7min speed=88551K/sec unused devices: none The results of mdadm --detail /dev/md0 are /dev/md0: Version : 1.2 Creation Time : Sun Jan 8 14:47:43 2012 Raid Level : raid1 Array Size : 1465136400 (1397.26 GiB 1500.30 GB) Used Dev Size : 1465136400 (1397.26 GiB 1500.30 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Sun Jan 8 14:48:54 2012 State : active, resyncing Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Rebuild Status : 2% complete Name : office-desktop:0 (local to host office-desktop) UUID : bfc16c6e:4e8cb910:96ff7ed2:6fec32bc Events : 1 Number Major Minor RaidDevice State 0 8 170 active sync /dev/sdb1 1 8 491 active sync /dev/sdd1 When I try to mount this drive, however, I get mount: /dev/md0: can't read superblock What do I need to do to complete the process? Thanks Jeff
Re: [gentoo-user] How to get raid
On Sun, 2012-01-08 at 15:03 -0500, Jeff Cranmer wrote: On Sun, 2012-01-08 at 12:31 -0600, Paul Hartman wrote: What is going on here? (I didn't read this whole thread, sorry if I'm repeating someone else's advice) kernel autodetection only works on old superblock version 0.90, you're using 1.2. Not a big deal, we use mdadm to do it. Define your arrays in /etc/mdadm.conf and start /etc/init.d/mdadm in your boot runscripts with rc-update add mdadm boot, it will bring up the array at boot time. In my mdadm.conf i have a line like this: ARRAY /dev/md1 metadata=1.01 name=black:1 UUID=8e653e72:9d5df6ba:bb66ea8b:02f1c317 (might be word-wrapped, should be all one line) That's all that was needed to bring it up automatically at boot time. Also AFAIR there was a gotcha about the hostname stored in the array's metadata must match your machine's hostname or else mdadm auto-assemble won't accept it (to protect you in case you're plugging disks from another machine for recovery, you don't want it to use them as your main drives), so in that case you must specify it explicitly or set the AUTO parameter in mdadm.conf to accept this condition. If you created the array from within a LiveCD or on another machine, the hostname might not match your system. See the mdadm manpage for more info. mdadm was added to the default level, not boot. My /etc/mdadm.conf file has two active lines DEVICE /dev/sd[bcd]1 ARRAY dev/md0 metadata=1.2 spares=1 name=office-desktop:0 devices=/dev/sdb1,dev/sdc1,/dev/sdd1 It looks like I'm having trouble with a faulty /dev/sdc1, so what I'd like to do is wipe out the existing array and try starting a RAID1 array just with sdb1 and sdd1. I got rid of the old array by using the commands mdadm --manage --fail /dev/md0 mdadm --manage --stop /dev/md0 I then used mdadm --verbose --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb1 /dev/sdd1 The result of this command was dadm: /dev/sdb1 appears to be part of a raid array: level=raid5 devices=3 ctime=Sat Jan 7 08:16:00 2012 mdadm: partition table exists on /dev/sdb1 but will be lost or meaningless after creating array mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90 mdadm: /dev/sdd1 appears to be part of a raid array: level=raid5 devices=3 ctime=Sat Jan 7 08:16:00 2012 mdadm: size set to 1465136400K Continue creating array? y mdadm: Defaulting to version 1.2 metadata mdadm: array /dev/md0 started. The results of cat /proc/mdstat are Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md0 : active raid1 sdd1[1] sdb1[0] 1465136400 blocks super 1.2 [2/2] [UU] [] resync = 2.1% (31838144/1465136400) finish=269.7min speed=88551K/sec unused devices: none Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md0 : active raid1 sdd1[1] sdb1[0] 1465136400 blocks super 1.2 [2/2] [UU] [] resync = 2.1% (31838144/1465136400) finish=269.7min speed=88551K/sec unused devices: none The results of mdadm --detail /dev/md0 are /dev/md0: Version : 1.2 Creation Time : Sun Jan 8 14:47:43 2012 Raid Level : raid1 Array Size : 1465136400 (1397.26 GiB 1500.30 GB) Used Dev Size : 1465136400 (1397.26 GiB 1500.30 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Sun Jan 8 14:48:54 2012 State : active, resyncing Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Rebuild Status : 2% complete Name : office-desktop:0 (local to host office-desktop) UUID : bfc16c6e:4e8cb910:96ff7ed2:6fec32bc Events : 1 Number Major Minor RaidDevice State 0 8 170 active sync /dev/sdb1 1 8 491 active sync /dev/sdd1 When I try to mount this drive, however, I get mount: /dev/md0: can't read superblock What do I need to do to complete the process? Thanks Jeff Success - I managed to get a raid1 device operating. I created the final filesystem by using mkfs.xfs -f /dev/md0, then waited for the rebuild to complete before rebooting the system. It appears to be created successfully. Now I'll try the same sequence with sdb and sdc to see if sdc is a good disk. If that works, I'll retry a raid5 array tomorrow night. Jeff
Re: [gentoo-user] How to get raid
What am I missing? have you set the type to linux raid autodetect? have you tried mdadm --assemble? mdadm --assemble /dev/md0 didn't make any difference. Where do I set the type? after assembling, results of cat/proc/mdstat personalities : [linear] [raid0] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty] md0 : inactive sdb1[0](S) sdd1[3](S) sdc1[1](S) 4395409608 blocks super 1.2 unused devices: none results of mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. results of /etc/init.d/mdadm status * status: started fstab line /dev/md0 /data xfs noatime 0 0 Is there a raid option I need to add to the fstab entry? Is there another service that needs to run, other than mdam? Thanks Jeff
Re: [gentoo-user] How to get raid
On Sat, 2012-01-07 at 10:11 -0500, Jeff Cranmer wrote: What am I missing? have you set the type to linux raid autodetect? have you tried mdadm --assemble? mdadm --assemble /dev/md0 didn't make any difference. Where do I set the type? after assembling, results of cat/proc/mdstat personalities : [linear] [raid0] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty] md0 : inactive sdb1[0](S) sdd1[3](S) sdc1[1](S) 4395409608 blocks super 1.2 unused devices: none results of mdadm --detail /dev/md0 mdadm: md device /dev/md0 does not appear to be active. results of /etc/init.d/mdadm status * status: started fstab line /dev/md0 /data xfs noatime 0 0 Is there a raid option I need to add to the fstab entry? Is there another service that needs to run, other than mdam? Thanks Jeff I tried changing the type of each array element in fdisk to fd (linux raid autodetect. The array is still not being recognised at boot, with the same 'cannot read superblock' error. I also tried re-running mdadm --create /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1 I get the error mdadm: device /dev/sdb1 not suitable for any style of array. What is going on here?
Re: [gentoo-user] How to get raid
I tried changing the type of each array element in fdisk to fd (linux raid autodetect. The array is still not being recognised at boot, with the same 'cannot read superblock' error. I also tried re-running mdadm --create /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1 I get the error mdadm: device /dev/sdb1 not suitable for any style of array. What is going on here? I am thinking ;) LOL! Me too. mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty. I'm not sure whether it's really faulty, or just that my setup for RAID is screwed up. How do I get rid of an existing /dev/md0? I'm thinking that I can try creating a RAID1 array using the two allegedly good disks and see if I can make that work. If that works, I'll get rid of it and try recreating the RAID1 with one good disk and the one that mdadm thinks is faulty. Hopefully that will show me whether I have a hardware problem or a software one. Jeff
Re: [gentoo-user] How to get raid
How do I get rid of an existing /dev/md0? you stop it. Override the superblock with dd.. and lose all data on the disks. I'm thinking that I can try creating a RAID1 array using the two allegedly good disks and see if I can make that work. yeah If that works, I'll get rid of it and try recreating the RAID1 with one good disk and the one that mdadm thinks is faulty. you don't have to. You can migrate a 2 disk raid1 to a 3 disk raid5. Howtos are availble via google. just saying - box in suspend to ram. I change the cable (and connector on mobo) on a disk with two raid 1 partitions on it. One came back after starting the box. The other? Nothing I tried worked. At the end I dd'ed the partition.. and did a complete 'faulty disk/replacement' resync argl. You're assuming I have more knowledge that I do. Can you explain the steps more in layman's terms. I've never used dd before. Jeff
Re: [gentoo-user] How to get raid
On Fri, 2012-01-06 at 13:36 +0100, Volker Armin Hemmann wrote: Am Donnerstag, 5. Januar 2012, 23:44:10 schrieb Jeff Cranmer: On Fri, 2012-01-06 at 02:42 +0100, Volker Armin Hemmann wrote: in your case sfdisk -d /dev/sdb | sfdisk /dev/sdc of course ;) One of the disks had a GPT partition table which I was eventually able to get rid of with gdisk (emerge -av gptfdisk). I'm close. I had a 2.7TiB RAID5 array using genkernal, comprising three 1.5TB disks, using the commands mdadm --create /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1 mdadm --detail --scan /etc/mdadm.conf I formatted this array as an xfs filesystem. After reboot, however, /dev/md0 is still there, but I get a 'can't read superblock' error. What am I missing? have you set the type to linux raid autodetect? have you tried mdadm --assemble? mdadm --assemble /dev/md0 didn't make any difference. Where do I set the type? Thanks Jeff
Re: [gentoo-user] How to get raid
On Thu, 2012-01-05 at 11:22 +0100, Volker Armin Hemmann wrote: Am Mittwoch, 4. Januar 2012, 22:45:45 schrieb Jeff Cranmer: On Thu, 2012-01-05 at 04:01 +0100, Volker Armin Hemmann wrote: the short one: partition one disk with (c)fdisk. Use sfdisk to transfer the partition scheme to the other disks. run mdadm --create /dev/md0 level=whatever you want --raid- devices=thenumberofdevices /dev/sdXY /dev/sdZY ... mdadm --detail --scan /etc/mdadm.conf done OK, but there is active data on the disks, so I don't want to partition them. They should already partitioned, and running fdisk will erase the data. first rule: always mount a scratch monkey In your case: always backup data. No big deal. 99.9% of the data is backed up. I was just hoping to recover the last 0.1% (picky huh?g). Now that I know one of the main drawbacks of fakeraid, I think I'll move ahead with software RAID. OK, so I've partitioned the first disk as a single linux partition (/dev/sdb1, ID 83, Linux). How do I use sfdisk to transfer that partition scheme to the other disks? Is it not sufficient just to partition the other two disks in the same way as the first? Jeff
Re: [gentoo-user] How to get raid
On Fri, 2012-01-06 at 02:42 +0100, Volker Armin Hemmann wrote: in your case sfdisk -d /dev/sdb | sfdisk /dev/sdc of course ;) One of the disks had a GPT partition table which I was eventually able to get rid of with gdisk (emerge -av gptfdisk). I'm close. I had a 2.7TiB RAID5 array using genkernal, comprising three 1.5TB disks, using the commands mdadm --create /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1 mdadm --detail --scan /etc/mdadm.conf I formatted this array as an xfs filesystem. After reboot, however, /dev/md0 is still there, but I get a 'can't read superblock' error. What am I missing?
Re: [gentoo-user] How to get raid
On Tue, 2012-01-03 at 22:21 -0600, Paul Hartman wrote: On 01/03/2012 08:57 PM, Jeff Cranmer wrote: device-mapper: table: 253:0: raid45: unknown target type Maybe a dumb question, but is the raid45 module enabled in your kernel config? genkernel --dmraid all Not sure how to check those details in genkernel.
Re: [gentoo-user] How to get raid
I was using a hardware-based 'fakeRAID'. It used to work on my old OpenSuse install, but that broke and I installed gentoo instead. I wasn't able to get that to work, and then the motherboard died, so I built a new system and reused the 3-drive RAID5 array. While in the first case you see all individual disks with their partitions and a /dev/mdX entry that actually contains the raid failsystem, the second one shows only a /dev/sdX holding the final raid drive. Additionally, for the hardware based raid, you'll need a driver for the controller that supports the raid5. I think this is the configuration you're trying to run, since you mentioned that you created your raid in the RAID BIOS. I'm not sure (I've never tried this) whether there is a driver for Linux supporting raid modes on board-embedded HW raid controllers. Alex
Re: [gentoo-user] How to get raid
On Wed, 2012-01-04 at 14:39 +0100, Volker Armin Hemmann wrote: Am Dienstag, 3. Januar 2012, 21:57:18 schrieb Jeff Cranmer: Hi all, I have recently built a new system, running Gentoo on a Sabertooth 990FX motherboard. The board has a raid controller on which I'm running a 120GB solid state drive for the OS (Raid 0) and a set of three 1.5TB drives which were previously running as a RAID5 array. no, it does not have a raid controller. It is bios raid. AKA fake raid. You will have less trouble if you stop using it. google for mdadm. There are some very nice howto's. Not sure I'd agree with you about the howtos being nice. They mostly deal with trying to boot from a RAID array (don't want that, as I have my OS on a non-RAID 120GB SSD). They're also contradictory, with some saying I need dmraid, and some saying not. Most seem to make no more than a passing nod towards genkernel. So, given that from the links that I've found, here's my starting set of questions. In /etc/genkernel.conf, which options do I need to enable. One guide suggested the following settings DMRAID=no MDADM=yes MDADM_CONFIG=/etc/mdadm.conf MDADM_VER=3.1.4 If this is correct, does it matter that my mdadm version which I emerged is 3.1.5? The tarball in /var/cache/genkernel/src is mdadm-3.1.4.tar.bz2 Should I copy mdadm-3.1.5.tar.bz2 from /etc/portage/distfiles into there and rebuild genkernel. Do I need the dodmraid option compiled into genkernel, or is that only for fakeraid, or situations where I need to boot from a raid partition? Do I need the dodmraid option set true in the grub.conf file, or is 'domdadm' more appropriate? Jeff
Re: [gentoo-user] How to get raid
On Thu, 2012-01-05 at 04:01 +0100, Volker Armin Hemmann wrote: the short one: partition one disk with (c)fdisk. Use sfdisk to transfer the partition scheme to the other disks. run mdadm --create /dev/md0 level=whatever you want --raid- devices=thenumberofdevices /dev/sdXY /dev/sdZY ... mdadm --detail --scan /etc/mdadm.conf done OK, but there is active data on the disks, so I don't want to partition them. They should already partitioned, and running fdisk will erase the data. If I run mdadm --create /dev/md0 level=5 --raid-devices=3 /dev/sdb /dev/sdc /dev/sdd, will that erase data already on the disks? Prior to running this command, there is no /dev/md entry. Is this correct? Looking further by using fdisk, it appears that sdc has a linux partition on sdc1 starting at sector 34, and a GPT partition of size 0+ at /dev/sdc4, sector 0. Nothing else is on that disk (no sdc2 or sdc3). sdd and sdb report invalid partition table flags and do not appear to have active partitions. Does this make sense? Is it possible that I ordered the disks incorrectly when I installed them, and by simply swapping disks b and c at the raid I can get things to start making sense? Is there an order to a set of RAID5 disks? I thought any two of three RAID5 disks could be recovered, regardless of which one dies? there is a reason why I never ever touch genkernel. you should forget that crap. You don't need to copy around anything. If your root is not on some fancy setup, you don't need initramfs. Just make a nice kernel, put it in /boot. Done. OK. The OS disk is non-RAID (120GB SSD), so I don't need any fancy options in my kernel. All the domdadm and dodmraid stuff is needed just when your OS disk is raided. Correct? Thanks Jeff
[gentoo-user] How to get raid
Hi all, I have recently built a new system, running Gentoo on a Sabertooth 990FX motherboard. The board has a raid controller on which I'm running a 120GB solid state drive for the OS (Raid 0) and a set of three 1.5TB drives which were previously running as a RAID5 array. I can see the sda 120GB drive and have installed the operating system on that. I can't see one device for the three disk RAID5 array, even though the RAID BIOS reports it as a healthy 3TB disk. Instead I see three separate devices, sdb, sdc and sdd What do I need to do to mount the 3TB RAID disk? I'm running genkernel, and compiled it with genkernel --dmraid all. It should already have data on it, if I can only get gentoo to recognise it. I can see the RAID controller when I use lspci 00:11.0 RAID bus controller: ATI Technologies Inc SB7x0,SB8x0,SB9x0 SATA Controller [RAID5 mode] (rev 40) One possible clue may be in dmesg, where I get the error device-mapper: table: 253:0: raid45: unknown target type Any assistance gratefully received. Thanks Jeff
Re: [gentoo-user] Problems starting KDE
On Sat, 2011-12-31 at 13:37 -0500, Jeff Cranmer wrote: On Sat, 2011-12-31 at 14:59 -0200, Claudio Roberto França Pereira wrote: On Sat, Dec 31, 2011 at 13:53, Jeff Cranmer j...@lotussevencars.com wrote: I'm attempting to bring up a new system. Processor is AMD Phenom 1055, running on a Sabertooth 990FX motherboard. Graphics card is an NVIDIA GEForce GTX550Ti. \After a little bit of further investigation, I discovered that the kdm.log file was full of old error messages. Deleting this log file did not result in a replacement file when I retried startx dmesg, however, was reporting some 'invalid opcode' errors. After finding a 2-page pdf on the correct compile flags to use with and amdfam10 processors (attached), I had enabled a couple of extra compile flags, -mabm and -msse4a, as well as setting -march=amdfam10. I've deleted the -mabm and -msse4a compile flag options from make.conf and I'm now running a full recompile (emerge -Dav system, emerge -Dav world). If that doesn't work, I'll try changing the architecture flag to -march=amd64 and recompile once more. I changed to -march=k8 in the make.conf file, removed all packages from kde-base to trigger a meta recompile, then re-installed kde-meta and compiled everything else using emerge -Dav system and emerge -Dav world. I still get the same error. from dmesg kded4[16907] trap invalid opcode ip:7fde193e74d7 sp:7fffa5120510 error:0 in libqtGui.so.4.7.4[7fde19226000+a74000] kcminit_startup[16909] trap invalid opcode ip:7fde193e74d7 sp:7fffa5120610 error:0 in libqtGui.so.4.7.4[7fde19226000+a74000] kcmserver[16911] trap invalid opcode ip:7fde193e74d7 sp:7fffa511ff70 error:0 in libqtGui.so.4.7.4[7fde19226000+a74000] So it appears that the problem is in libQtGui.so.4.7.4 How do I know that I've recompiled this? I suspect this is still a hangover from the original compile settings. Jeff
Re: [gentoo-user] Problems starting KDE
Jeff $ qfile libQtGui.so.4.7.4 x11-libs/qt-gui (/usr/lib64/qt4/libQtGui.so.4.7.4) Look at the date time that you built x11-libs/qt-gui (in your emerge.log, or use genlop) and compare with said file. The files match, last compiled in the morning, two days ago, which is before I tried my most recent changes. Success - Recompilation of this file gets me a k desktop. Is there a good way to force-recompile an entire system's code? emerge -Dav system and emerge -Dav world don't seem to go down far enough in the hierarchy to recompile all dependencies. Many thanks. Jeff
[gentoo-user] Error compiling phonon-gstreamer
Hi, I'm getting an error when trying to emerge phonon-gstreamer on my amdfam10 system. The compilation error is 'undefined reference to 'typeinfo for Phonon::StreamInterface' Has anyone else seem this error? I'm trying to clear out all remaining items in an emerge -NDuav world prior to debugging some kde startup problems. Thanks
Re: [gentoo-user] Error compiling phonon-gstreamer
On Sat, 2011-12-31 at 09:59 -0500, Jeff Cranmer wrote: Hi, I'm getting an error when trying to emerge phonon-gstreamer on my amdfam10 system. The compilation error is 'undefined reference to 'typeinfo for Phonon::StreamInterface' Has anyone else seem this error? I'm trying to clear out all remaining items in an emerge -NDuav world prior to debugging some kde startup problems. Thanks PS: I'm not sure what package requires this. By individually updating all the packages in world and system showing as updates, I now have the situation where either an emerge -Duav system or emerge -Duav world only returned new package media-libs/phonon-gstreamer as a requirement. revdep-rebuild returns that my system is consistent without this package. Jeff
[gentoo-user] Problems starting KDE
I'm attempting to bring up a new system. Processor is AMD Phenom 1055, running on a Sabertooth 990FX motherboard. Graphics card is an NVIDIA GEForce GTX550Ti. If I start X with twm, the xserver connection is made, and TWM comes up correctly with three Xterm windows. I note that I get two errors reported, (EE) NVIDIA: Failed to load module dri2 (Module does not exist, 0) /etc/X11/xinit/xinitrc: line 62: xclock: command not found The first error is definitely on startup, but the latter could have appeared on exit. I have a file 20-nvidia.conf in the /usr/share/X11/xorg.conf.d directory with the following information Section Device Identifier Device0 Driver nvidia VendorName NVIDIA Corporation BoardName GeForce GTX550 Ti BusID PCI:5:0:0 Screen 0 EndSection Section Module Disable dri Disable dri2 Load glx EndSection If I add exec startkde to the top of the /etc/X11/xinit/xinitrc file, then startx fails to start. I get the same dri2 error as above, but also get startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(13865): Communication Problem with kded, it probably crashed. Error message was: org.freedesktop.DBus.Error.NoReply : Message did not receive a reply (timeout by message bus) I verified using /etc/init.d/dbus status that the dbus service is running. Same for consolekit. /var/log/kdm.log shows one error, repeated for each startup attempt. KCrash: Appication 'kdmgreet' crashing KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi directly Server Terminated successfully (0). Closing log file. Any assistance gratefully received. Thanks Jeff
Re: [gentoo-user] Error compiling phonon-gstreamer
On Sat, 2011-12-31 at 10:50 -0500, Michael Mol wrote: --tree Sorry - please could you be a little more verbose? :-)
Re: [gentoo-user] Error compiling phonon-gstreamer
On Sat, 2011-12-31 at 11:47 -0600, Dale wrote: Claudio Roberto França Pereira wrote: Maybe some use flag inconsistency? Try adding --newuse or -N to your emerge. Try this: emerge -uavDN world. If this still just pulls phonon-gstreamer, then there should be some problem in the package itself. http://forums.gentoo.org/viewtopic-p-6888730.html#6888730 Dale :-) :-) Thanks for the link. I tried changing the use flags for phonon to -gstreamer vlc, but for some reason I'm still getting gstreamer pulled in as use flag requirement, though it adds vlc. Same error as before. I'll try -makeopts=-j1, since at the moment I'm running makeopts=-j6 Jeff
Re: [gentoo-user] Error compiling phonon-gstreamer
http://forums.gentoo.org/viewtopic-p-6888730.html#6888730 Dale :-) :-) Thanks for the link. I tried changing the use flags for phonon to -gstreamer vlc, but for some reason I'm still getting gstreamer pulled in as use flag requirement, though it adds vlc. Same error as before. I'll try -makeopts=-j1, since at the moment I'm running makeopts=-j6 Jeff No luck with makeopts=-j1 either.
Re: [gentoo-user] Error compiling phonon-gstreamer
On Sat, 2011-12-31 at 14:52 -0500, Michael Mol wrote: On Sat, Dec 31, 2011 at 2:46 PM, Jeff Cranmer j...@lotussevencars.com wrote: http://forums.gentoo.org/viewtopic-p-6888730.html#6888730 Dale :-) :-) Thanks for the link. I tried changing the use flags for phonon to -gstreamer vlc, but for some reason I'm still getting gstreamer pulled in as use flag requirement, though it adds vlc. Same error as before. I'll try -makeopts=-j1, since at the moment I'm running makeopts=-j6 Jeff No luck with makeopts=-j1 either. If you add --tree to your emerge line, you can see what's pulling in gstreamer. If it comes to it, running a command like: emerge -pe --verbose --tree --with-bdeps=y @world will give you a tree view showing the entire dependency tree on your system. From there, you should be able to get a clue as to which packages are pulling in packages you're having difficulty with. doing an emerge -pDv world, I can see the following tree kde-base/kdeedu-meta-4.7.4 kde-base/kmplot-4.7.4 x11-libs/qt-webkit-4.7.4 media-libs/phonon-4.6.0-r1 media-libs/phonon-gstreamer-4.5.1 Phonon reports a use flag of gstreamer, despite me calling -gstreamer in make.conf. The calling packages don't report gstreamer as a use flag.
Re: [gentoo-user] Re: Plasma-runtime compilation problems
On Sun, 2011-08-21 at 11:55 -0700, walt wrote: On 08/20/2011 12:21 PM, Jeff Cranmer wrote: /usr/include/KDE/Plasma/../../plasma/service.h:321: error: previous definition of 'struct QMetaTypeIdPlasma::Service*' Hm, well purely a wild guess, but perhaps /usr/include/plasma/service.h is left over from an earlier plasma package and the compiler really shouldn't be using it. What package does that file belong to? I don't know. Pardon my ignorance, but how do I find out? Thanks Jeff
Re: [gentoo-user] Re: Plasma-runtime compilation problems
On Wed, 2011-08-10 at 16:16 -0700, walt wrote:
On 08/10/2011 03:04 PM, Michael Schreckenbauer wrote:
Hi,
Am Mittwoch, 10. August 2011, 14:40:31 schrieb walt:
On 08/09/2011 08:34 PM, Jeff Cranmer wrote:
Hi all,
I'm trying to upgrade kde from 4.4 to 4.6, and I've run into a problem.
Plasma-runtime-4.6.3 is failing. The error appears to be
redefinition of 'struct QMetaTypeIDPlasma::Service*'
I don't use kde so I can't be specific, but usually a redefinition is
just a warning -- unless the package is compiled with the -Wall flag or
equivalent.
(Of course I meant -Werror, sorry.)
No, this is plain wrong. Redefinition of a struct is an error in C and C++
~$cat foo.c
struct foo {
int i;
};
struct foo {
char* v;
};
~$gcc foo.c -o foo
foo.c:5:8: error: redefinition of 'struct foo'
foo.c:1:8: note: originally defined here
Hm. I know I've seen compiler redefinition messages thousands of times
over the years. Is it really possible that all of those thousands were
errors instead of warnings? If that's true then I've wasted a lot more
time tracking them down than I care to think about :)
I've seen lots of compiler warnings in the past. This one, however, was
flagged as an 'Error', not as a warning. It was the last message before
the compile failed, so I think it's reasonable to assume that therein
lies the problem?
I have emerged all system files, as well as a lot of the world files
that are currently out of date. This particular compilation failure
happened late in an emerge -NDuav kdebase-meta, as the first part of the
upgrade from kde4.4 to kde4.6
Running revdep-rebuild following the emerge didn't help. I still have
some world files that are out of date, but all of those are allegedly
not deep dependencies of kdebase-eta. Last time I tried to do a full
emerge -NDuav world, however, I was then unable to operate my HDPVR
unit, as it suffered a lot of usb failures. I had to recover my system
from an earlier clonezila backup, so now I'm trying to sneak up on the
problem by doing as little as possible each emerge, then checking
everything works and running another OS clone before continuing.
Unfortunately, kde is now broken, so I'm operating my mythtv interface
via gnome while I attempt to recover kde. It's probable that the fault
lies in one of the other packages within world that are still to be
upgraded, but it would be nice to get some clues as to which one is the
culprit, so I can continue to inch up on whatever is breaking my HDPVR
based mythtv.
Jeff
[gentoo-user] Plasma-runtime compilation problems
Hi all, I'm trying to upgrade kde from 4.4 to 4.6, and I've run into a problem. Plasma-runtime-4.6.3 is failing. The error appears to be redefinition of 'struct QMetaTypeIDPlasma::Service*' Has anyone encountered this problem, and is there an easy fix? Thanks Jeff
Re: Re: [gentoo-user] Problems with Nvidia fake raid array
On Tue, 2011-07-26 at 16:55 -0700, Daniel Frey wrote: On 01/-10/37 11:59, Michael Orlitzky wrote: I think this one should have worked? It seems to have found the superblock on /dev/sda, at least. Anyway, I imagine everyone (myself included) is afraid to tell you to do anything at this point that might trash your data. My advice now would be to put it back where it worked, and make a backup. I'm just going through this myself. As far as I know mdadm does *not* support nvraid. It does support imsm, or intel raid, which I'm in the process of setting up on my workstation. I can't find anything in the docs regarding mdadm working with nvraid, you should be trying dmraid for that. If all you have is /dev/control and you are not using a dmraid supported kernel (genkernel requires dodmraid to find and assemble arrays) then execute `dmraid -ay` and check dmesg and /dev/mapper for contents. Dan Thanks Dan, I'm not using genkernel at the moment. I'll try those steps and let you know how it goes. The Raid array worked on the OpenSuse operating system that I blew away to install gentoo, so I should be able to resurrect it without wiping everything out. Jeff
Re: [gentoo-user] Problems with Nvidia fake raid array
On Mon, 2011-07-25 at 10:45 -0400, Michael Orlitzky wrote: On 07/22/11 21:56, Jeff Cranmer wrote: Is there anyone who can help me recover my raid array? Next, I tried commenting out the previously added DEVICE line, and adding ARRAY /dev/md0 devices=/dev/sda,/dev/sdb,/dev/sdc mdadm --assemble --scan returns something different mdadm: /dev/sdb has no superblock - assembly aborted. I think this one should have worked? It seems to have found the superblock on /dev/sda, at least. Anyway, I imagine everyone (myself included) is afraid to tell you to do anything at this point that might trash your data. My advice now would be to put it back where it worked, and make a backup. I already
Re: [gentoo-user] Problems with Nvidia fake raid array
On Mon, 2011-07-25 at 10:45 -0400, Michael Orlitzky wrote: On 07/22/11 21:56, Jeff Cranmer wrote: Is there anyone who can help me recover my raid array? Next, I tried commenting out the previously added DEVICE line, and adding ARRAY /dev/md0 devices=/dev/sda,/dev/sdb,/dev/sdc mdadm --assemble --scan returns something different mdadm: /dev/sdb has no superblock - assembly aborted. I think this one should have worked? It seems to have found the superblock on /dev/sda, at least. Anyway, I imagine everyone (myself included) is afraid to tell you to do anything at this point that might trash your data. My advice now would be to put it back where it worked, and make a backup. I already have a backup of the data (much of it in multiple locations). If it gets trashed, I can recover all critical data. Right now, I just want to get the storage space back. Jeff
Re: [gentoo-user] Problems with Nvidia fake raid array
Is there anyone who can help me recover my raid array? On Wed, 2011-07-20 at 20:43 -0400, Jeff Cranmer wrote: On Tue, 2011-07-19 at 09:06 -0400, Michael Orlitzky wrote: On 07/18/2011 11:08 PM, Jeff Cranmer wrote: Pardon my additional questions before taking the plunge here. So, given that I have three devices, /dev/sda, /dev/sdb and /dev/sdc, if I run the command mdadm --assemble --scan, would this find all the components and create a /dev/md0 disk without damaging the contents of the original RAID array? If you've got the space and time, a backup can't hurt. Using --scan will make it check the config file, but right now, there's probably nothing useful in it. This looks like what you want to do to me: If the --scan option is not given, then only devices and identities listed on the command line are considered. The first device will be the array device, and the remainder will be examined when looking for components. but I'd figure out where that md0 is coming from (below) first. When I tried mdadm --assemble --scan with nothing uncommented in the configuration file, I got mdadm: No arrays found in config file or automatically. Typing dmesg | grep md0 returned no lines. There are a couple of lines in dmesg when I run dmesg | grep md:, but they read md: linear personality registered for level -1 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 md: raid10 personality registered for level 10 md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays md: Scanned 0 and added 0 devices md: autorun... md: ... autorun DONE. I think this means that raid5 is set up correctly in the kernel, but it can't find the raid array. Next I tried adding a line to the config file: DEVICE /dev/sda /dev/sdb /dev/sdc mdadm --assemble --scan returned the same results as before Next, I tried commenting out the previously added DEVICE line, and adding ARRAY /dev/md0 devices=/dev/sda,/dev/sdb,/dev/sdc mdadm --assemble --scan returns something different mdadm: /dev/sdb has no superblock - assembly aborted. The only item in /dev/mapper is th default 'control' entry. There is a /dev/md0 item already listed, but presently when I try to mount it, it reports that it is unable to read the superblock. Would the command above fix this? Depends. Where'd the md0 come from? You probably have something in your logs or dmesg, unless that device was created manually on your old system. Where is the config file mentioned in your e-mail, and do I need to edit it first to add the three raid disks? It's /etc/mdadm.conf. You don't need it to create or use the array, but you'll want to run mdadm when the machine boots and the config file tells it what to do. Once the array is working, you can just do, mdadm --detail --scan /etc/mdadm.conf mdadm --detail --scan returns no output. Also, I just checked /dev and md0 is now gone from the list. Since there are also /dev/sg0, /dev/sg1 and /dev/sg1, I also tried those instead of /dev/sda, /dev/sdb and /dev/sdc in the ARRAY line, but mdadm --assemble --scan returned no output I tried re-booting, but /dev/md0 is now permanently gone. Does this give you any ideas what I can try next?? Thanks Jeff
[gentoo-user] No keyboard or mouse with X after upgrade
Hi All, I recently ran an emerge -NDuav on my system and world lists, and now I can't start X and keep the keyboard or mouse operating. Is this a known issue? Any simple fixes? Thanks in advance Jeff
Re: [gentoo-user] No keyboard or mouse with X after upgrade
On Sat, 2011-07-23 at 10:18 +0800, William Kenworthy wrote: On Fri, 2011-07-22 at 22:00 -0400, Jeff Cranmer wrote: Hi All, I recently ran an emerge -NDuav on my system and world lists, and now I can't start X and keep the keyboard or mouse operating. Is this a known issue? Any simple fixes? Thanks in advance Jeff Did you follow the rebuild instructions for keyboard/mouse etc in the ebuild messages? - yes its a known problem when you dont do that. BillK Thanks. It looks like I've missed that. Where were the ebuild messages? I don't see anything on xorg-server-1.10.2
Re: [gentoo-user] No keyboard or mouse with X after upgrade
On Fri, 2011-07-22 at 22:39 -0400, Jeff Cranmer wrote: On Sat, 2011-07-23 at 10:18 +0800, William Kenworthy wrote: On Fri, 2011-07-22 at 22:00 -0400, Jeff Cranmer wrote: Hi All, I recently ran an emerge -NDuav on my system and world lists, and now I can't start X and keep the keyboard or mouse operating. Is this a known issue? Any simple fixes? Thanks in advance Jeff Did you follow the rebuild instructions for keyboard/mouse etc in the ebuild messages? - yes its a known problem when you dont do that. BillK Thanks. It looks like I've missed that. Where were the ebuild messages? I don't see anything on xorg-server-1.10.2 Got it - xf86-input-evdev needed to be recompiled to recover keyboard and mouse operation. Thanks Jeff
Re: [gentoo-user] Problems with Nvidia fake raid array
On Tue, 2011-07-19 at 09:06 -0400, Michael Orlitzky wrote: On 07/18/2011 11:08 PM, Jeff Cranmer wrote: Pardon my additional questions before taking the plunge here. So, given that I have three devices, /dev/sda, /dev/sdb and /dev/sdc, if I run the command mdadm --assemble --scan, would this find all the components and create a /dev/md0 disk without damaging the contents of the original RAID array? If you've got the space and time, a backup can't hurt. Using --scan will make it check the config file, but right now, there's probably nothing useful in it. This looks like what you want to do to me: If the --scan option is not given, then only devices and identities listed on the command line are considered. The first device will be the array device, and the remainder will be examined when looking for components. but I'd figure out where that md0 is coming from (below) first. When I tried mdadm --assemble --scan with nothing uncommented in the configuration file, I got mdadm: No arrays found in config file or automatically. Typing dmesg | grep md0 returned no lines. There are a couple of lines in dmesg when I run dmesg | grep md:, but they read md: linear personality registered for level -1 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 md: raid10 personality registered for level 10 md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays md: Scanned 0 and added 0 devices md: autorun... md: ... autorun DONE. I think this means that raid5 is set up correctly in the kernel, but it can't find the raid array. Next I tried adding a line to the config file: DEVICE /dev/sda /dev/sdb /dev/sdc mdadm --assemble --scan returned the same results as before Next, I tried commenting out the previously added DEVICE line, and adding ARRAY /dev/md0 devices=/dev/sda,/dev/sdb,/dev/sdc mdadm --assemble --scan returns something different mdadm: /dev/sdb has no superblock - assembly aborted. The only item in /dev/mapper is th default 'control' entry. There is a /dev/md0 item already listed, but presently when I try to mount it, it reports that it is unable to read the superblock. Would the command above fix this? Depends. Where'd the md0 come from? You probably have something in your logs or dmesg, unless that device was created manually on your old system. Where is the config file mentioned in your e-mail, and do I need to edit it first to add the three raid disks? It's /etc/mdadm.conf. You don't need it to create or use the array, but you'll want to run mdadm when the machine boots and the config file tells it what to do. Once the array is working, you can just do, mdadm --detail --scan /etc/mdadm.conf mdadm --detail --scan returns no output. Also, I just checked /dev and md0 is now gone from the list. Since there are also /dev/sg0, /dev/sg1 and /dev/sg1, I also tried those instead of /dev/sda, /dev/sdb and /dev/sdc in the ARRAY line, but mdadm --assemble --scan returned no output I tried re-booting, but /dev/md0 is now permanently gone. Does this give you any ideas what I can try next?? Thanks Jeff
[gentoo-user] Problems with Nvidia fake raid array
Hi all, After cleaning off my Opensuse O.S. and installing Gentoo, I'm having trouble getting my 3-disk nvidia SATA raid5 array back on line. The gentoo OS is on a separate non-raid IDE disk, and I can see the three individual disks which make up the raid array (/dev/sda, /dev/sdb and /dev/sdc). Unfortunately, the system does not seem to be able to detect the raid array, and dmesg shows no md disks detected or mounted. There are a few guides on line for setting up a system which boots to a raid array, but I haven't found any guides for simply mounting a raided disk. I think I've got all the kernel settings right, and the raid array was working before I cleared out the IDE disk. I know that the Nvidia array isn't a true hardware raid array, but it's a data disk only, and while I have a reasonably recent backup, I'm not keen on re-formatting it and setting up a kernel-based raid array. Any suggestions or pointers gratefully received. Thanks in advance. Jeff
Re: [gentoo-user] Problems with Nvidia fake raid array
On Mon, 2011-07-18 at 22:29 -0400, Michael Orlitzky wrote: Make sure your kernel supports RAID, and RAID5 (they're separate options). Then emerge mdadm. Once you get it up and running once, you can dump the current config to /etc/mdadm.conf so you don't have to assemble it again. Then add mdadm to the boot runlevel. I'm Ok so far - Raid and Raid5 options are both already compiled into the kernel, and mdadm is in the boot runlevel. # mdadm --assemble --help Usage: mdadm --assemble device options... mdadm --assemble --scan options... This usage assembles one or more raid arrays from pre-existing components. For each array, mdadm needs to know the md device, the identity of the array, and a number of sub devices. These can be found in a number of ways. The md device is either given on the command line or is found listed in the config file. The array identity is determined either from the --uuid or --super-minor commandline arguments, from the config file, or from the first component device on the command line. The different combinations of these are as follows: If the --scan option is not given, then only devices and identities listed on the command line are considered. The first device will be the array device, and the remainder will be examined when looking for components. If an explicit identity is given with --uuid or --super-minor, then only devices with a superblock which matches that identity is considered, otherwise every device listed is considered. If the --scan option is given, and no devices are listed, then every array listed in the config file is considered for assembly. The identity of candidate devices are determined from the config file. If the --scan option is given as well as one or more devices, then Those devices are md devices that are to be assembled. Their identity and components are determined from the config file. If mdadm can not find all of the components for an array, it will assemble it but not activate it unless --run or --scan is given. To preserve this behaviour even with --scan, add --no-degraded. Note that all of the components means as many as were present the last time the array was running as recorded in the superblock. If the array was already degraded, and the missing device is not a new problem, it will still be assembled. It is only newly missing devices that cause the array not to be started. Pardon my additional questions before taking the plunge here. So, given that I have three devices, /dev/sda, /dev/sdb and /dev/sdc, if I run the command mdadm --assemble --scan, would this find all the components and create a /dev/md0 disk without damaging the contents of the original RAID array? The only item in /dev/mapper is th default 'control' entry. There is a /dev/md0 item already listed, but presently when I try to mount it, it reports that it is unable to read the superblock. Would the command above fix this? Where is the config file mentioned in your e-mail, and do I need to edit it first to add the three raid disks? Thanks Jeff
Re: [gentoo-user] Re: Trying to configure Radeon card
On Sat, 2010-10-16 at 14:28 -0400, Jeff Cranmer wrote: On Sat, 2010-10-16 at 14:51 +1100, Adam Carter wrote: I use an xorg.conf, and have the following; Section Files ModulePath /usr/lib64/xorg/modules ModulePath /usr/lib64/opengl/xorg-x11/extensions/ EndSection Your xorg cant find the dri and dri2 modules because its not looking in the second directory. Also, it might be worth trying the latest driver, so # echo x11-drivers/ati-drivers ~amd64 /etc/portage/package.keywords Then emerge ati-drivers again. If that doesnt help, send the X11 log again after you've made those changes. I made the changes above, and added the fbdev entry to VIDEO_CARDS from Nikos' e-mail. I also added fglrx to my /etc/modules.autoload.d/kernel-2.6 file. It's a bit overkill but next I did emerge -Dav system and emerge -Dav world before running emerge -NDuav system and emerge -NDuav world. I rebooted the machine, ran startx and it looks like success. I reinstalled xdm to the default runlevel, and I have a working graphics card. Thanks all for the advice. There are a couple of issues: (1) Even though the resolution is set to 1920 x 1080, it appears to be scaled so that it doesn't fill the entire screen. It is scaled to about 90% for some reason. (2) Compositing is not supported as it stands. I may need to switch that on in xorg.conf. Does anyone know how to fix the scaling issue or whether it is advisable should turn on compositing in xorg.conf? Jeff In case anyone is suffering the same problem. I fixed the display scaling issue. The ATI Catalyst control center in KDE allows you to change the scaling options. My display was set to about 7% underscaling in the display manager DTV1 menu, on the adjustments tab. All I needed to do was move the scaling slider all the way to the right, and the display scaled perfectly. Now, if only I could get compositing working :-/ Jeff
Re: [gentoo-user] Re: Trying to configure Radeon card
On Sat, 2010-10-16 at 14:51 +1100, Adam Carter wrote: I use an xorg.conf, and have the following; Section Files ModulePath /usr/lib64/xorg/modules ModulePath /usr/lib64/opengl/xorg-x11/extensions/ EndSection Your xorg cant find the dri and dri2 modules because its not looking in the second directory. Also, it might be worth trying the latest driver, so # echo x11-drivers/ati-drivers ~amd64 /etc/portage/package.keywords Then emerge ati-drivers again. If that doesnt help, send the X11 log again after you've made those changes. I made the changes above, and added the fbdev entry to VIDEO_CARDS from Nikos' e-mail. I also added fglrx to my /etc/modules.autoload.d/kernel-2.6 file. It's a bit overkill but next I did emerge -Dav system and emerge -Dav world before running emerge -NDuav system and emerge -NDuav world. I rebooted the machine, ran startx and it looks like success. I reinstalled xdm to the default runlevel, and I have a working graphics card. Thanks all for the advice. There are a couple of issues: (1) Even though the resolution is set to 1920 x 1080, it appears to be scaled so that it doesn't fill the entire screen. It is scaled to about 90% for some reason. (2) Compositing is not supported as it stands. I may need to switch that on in xorg.conf. Does anyone know how to fix the scaling issue or whether it is advisable should turn on compositing in xorg.conf? Jeff Section ServerLayout Identifier aticonfig Layout Screen 0 aticonfig-Screen[0]-0 0 0 EndSection Section Module EndSection Section Files ModulePath /usr/lib64/xorg/modules ModulePath /usr/lib64/opengl/xorg-x11/extensions EndSection Section Monitor Identifier aticonfig-Monitor[0]-0 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true EndSection Section Device Identifier aticonfig-Device[0]-0 Driver fglrx BusID PCI:1:0:0 EndSection Section Screen Identifier aticonfig-Screen[0]-0 Device aticonfig-Device[0]-0 Monitoraticonfig-Monitor[0]-0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.34-gentoo-r6 x86_64 Current Operating System: Linux Media-PC 2.6.34-gentoo-r6 #10 SMP Fri Oct 15 21:26:03 EDT 2010 x86_64 Kernel command line: root=/dev/sda3 Build Date: 16 October 2010 01:18:33PM Current version of pixman: 0.18.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sat Oct 16 14:13:00 2010 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout aticonfig Layout (**) |--Screen aticonfig-Screen[0]-0 (0) (**) | |--Monitor aticonfig-Monitor[0]-0 (**) | |--Device aticonfig-Device[0]-0 (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/TTF/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/OTF does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/Type1/ does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ (**) ModulePath set to /usr/lib64/xorg/modules,/usr/lib64/opengl/xorg-x11/extensions (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. (II) Loader magic: 0x7c3220 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 1002:68be:174b:e148 ATI Technologies Inc rev 0, Mem @ 0xd000/268435456, 0xfdfc/131072, I/O @ 0xee00/256, BIOS @ 0x/131072 (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) extmod will be loaded by default. (II) dbe will be loaded by default. (II) glx will be loaded by default. (II) record will be loaded by default. (II) dri will be loaded by default. (II) dri2 will be loaded by default. (II) LoadModule: extmod (II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension
Re: [gentoo-user] Re: Trying to configure Radeon card
On Thu, 2010-10-14 at 10:32 +0300, Nikos Chantziaras wrote: You mentioned that you used fglrxinfo in your post, which assumes you're using the closed source driver :-/ Another hint was that you're using an HD5000 series card, which is not supported correctly by the open source drivers anyway at this point. Yeah - I realised afterwards that I had left a few things in place from a failed attempt at installing the closed source drivers. Anyway, if you're on open source drivers, I think that's your problem. Only the closed source driver works correctly with 3D for HD5000 cards at this moment. Thanks for the advice. I'll take another crack at the closed source drivers, and if that doesn't work, I'll rip out the $%^ thing and replace it with an Nvidia cardg Jeff
Re: [gentoo-user] Re: Trying to configure Radeon card
OK, so let's have a go at the ATI drivers again. First, get rid of the open source ati drivers emerge --unmerge -av radeon-ucode xf86-video-ati Editing the /etc/make.conf file to change the last line to VIDEO_CARDS=fglrx then running emerge -NDuav system changes the mesa driver so that I have no valid selections for VIDEO_CARDS=, so I'll unmerge mesa emerge --unmerge -av mesa running emerge -NDuav world identified the xorg-drivers and pm-utils packages that have changed, and attempts to re-emerge mesa, so I'll unmerge those two emerge --unmerge -av xorg-drivers pm-utils moving on to the kernel, I verify that I have the correct kernel parameters: Device drivers - Graphics Support - * dev/agpgart (AGP support) None of the other modules below the agpgart appear to be appropriate, so I'll not enable any of these. Disable the direct rendering manager and framebuffer support, so this should take care of the radeon driver module. I'll do a locate search for this before I reboot. Device Drivers - Generic Driver Options - Userspace firmware loading support [ ] Include in-kernel firmware blobs in kernel binary Recompile the kernel and update using grub. emerge ati-drivers It seems this was still present from the previous attempt, so I'll re-emerge it. Running emerge -NDuav system still pulls in mesa, so back in it goes. Running emerge -NDuav world pulls back in xorg-drivers and pm-utils, so these are also reinstalled. emerge --depclean pulls out a few packages, radeontool gst-plugins-v4l gst-plugins-v4l2 gentoo-sources-2.6.34-r6 since gentoo-sources-2.6.34-r6 is the kernel I'm presently operating with, I'll re-emerge that and verify that it is still current via eselect kernel list. revdep-rebuild doesn't add anything else. Prevent boot-up into X-windows, then reboot. rc-update del xdm default reboot run aticonfig --initial to create an xorg.conf file. startx total system crash - hard reset required to reboot. Hmm - the xorg.log file has this error. atiddxDriScreenInit failed, GPS not been initialized. Can anyone shed light on this? Thanks Jeff On Fri, 2010-10-15 at 20:11 -0400, Jeff Cranmer wrote: On Thu, 2010-10-14 at 10:32 +0300, Nikos Chantziaras wrote: You mentioned that you used fglrxinfo in your post, which assumes you're using the closed source driver :-/ Another hint was that you're using an HD5000 series card, which is not supported correctly by the open source drivers anyway at this point. Yeah - I realised afterwards that I had left a few things in place from a failed attempt at installing the closed source drivers. Anyway, if you're on open source drivers, I think that's your problem. Only the closed source driver works correctly with 3D for HD5000 cards at this moment. Thanks for the advice. I'll take another crack at the closed source drivers, and if that doesn't work, I'll rip out the $%^ thing and replace it with an Nvidia cardg Jeff X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.34-gentoo-r6 x86_64 Current Operating System: Linux Media-PC 2.6.34-gentoo-r6 #10 SMP Fri Oct 15 21:26:03 EDT 2010 x86_64 Kernel command line: root=/dev/sda3 Build Date: 12 October 2010 08:15:38PM Current version of pixman: 0.18.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Oct 15 22:10:34 2010 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout aticonfig Layout (**) |--Screen aticonfig-Screen[0]-0 (0) (**) | |--Monitor aticonfig-Monitor[0]-0 (**) | |--Device aticonfig-Device[0]-0 (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/TTF/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/OTF does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/Type1/ does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ (==) ModulePath set to /usr/lib64/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. (II) Loader magic: 0x7c3220 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 7 (--) PCI:*(0:1:0:0) 1002:68be:174b:e148 ATI Technologies Inc rev 0, Mem @ 0xd000/268435456, 0xfdfc/131072, I/O @ 0xee00/256, BIOS @ 0x/131072 (WW) Open ACPI failed (/var/run
Re: [gentoo-user] Re: Trying to configure Radeon card
On Fri, 2010-10-15 at 22:24 -0400, Jeff Cranmer wrote: OK, so let's have a go at the ATI drivers again. First, get rid of the open source ati drivers emerge --unmerge -av radeon-ucode xf86-video-ati Editing the /etc/make.conf file to change the last line to VIDEO_CARDS=fglrx then running emerge -NDuav system changes the mesa driver so that I have no valid selections for VIDEO_CARDS=, so I'll unmerge mesa emerge --unmerge -av mesa running emerge -NDuav world identified the xorg-drivers and pm-utils packages that have changed, and attempts to re-emerge mesa, so I'll unmerge those two emerge --unmerge -av xorg-drivers pm-utils moving on to the kernel, I verify that I have the correct kernel parameters: Device drivers - Graphics Support - * dev/agpgart (AGP support) None of the other modules below the agpgart appear to be appropriate, so I'll not enable any of these. Disable the direct rendering manager and framebuffer support, so this should take care of the radeon driver module. I'll do a locate search for this before I reboot. Device Drivers - Generic Driver Options - Userspace firmware loading support [ ] Include in-kernel firmware blobs in kernel binary Recompile the kernel and update using grub. emerge ati-drivers It seems this was still present from the previous attempt, so I'll re-emerge it. Running emerge -NDuav system still pulls in mesa, so back in it goes. Running emerge -NDuav world pulls back in xorg-drivers and pm-utils, so these are also reinstalled. emerge --depclean pulls out a few packages, radeontool gst-plugins-v4l gst-plugins-v4l2 gentoo-sources-2.6.34-r6 since gentoo-sources-2.6.34-r6 is the kernel I'm presently operating with, I'll re-emerge that and verify that it is still current via eselect kernel list. revdep-rebuild doesn't add anything else. Prevent boot-up into X-windows, then reboot. rc-update del xdm default reboot run aticonfig --initial to create an xorg.conf file. startx total system crash - hard reset required to reboot. Hmm - the xorg.log file has this error. atiddxDriScreenInit failed, GPS not been initialized. Can anyone shed light on this? Thanks Jeff Oops - forgot to eselect opengl set ati Now it's still failing, but a different set of errors, as attached. Any suggestions gratefully received. X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.34-gentoo-r6 x86_64 Current Operating System: Linux Media-PC 2.6.34-gentoo-r6 #10 SMP Fri Oct 15 21:26:03 EDT 2010 x86_64 Kernel command line: root=/dev/sda3 Build Date: 12 October 2010 08:15:38PM Current version of pixman: 0.18.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Oct 15 22:41:42 2010 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout aticonfig Layout (**) |--Screen aticonfig-Screen[0]-0 (0) (**) | |--Monitor aticonfig-Monitor[0]-0 (**) | |--Device aticonfig-Device[0]-0 (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/TTF/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/OTF does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/Type1/ does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ (==) ModulePath set to /usr/lib64/xorg/modules (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. (II) Loader magic: 0x7c3220 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 7 (--) PCI:*(0:1:0:0) 1002:68be:174b:e148 ATI Technologies Inc rev 0, Mem @ 0xd000/268435456, 0xfdfc/131072, I/O @ 0xee00/256, BIOS @ 0x/131072 (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) extmod will be loaded by default. (II) dbe will be loaded by default. (II) glx will be loaded by default. (II) record will be loaded by default. (II) dri will be loaded by default. (II) dri2 will be loaded by default. (II) LoadModule: extmod (II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86
Re: [gentoo-user] Re: Trying to configure Radeon card
On Wed, 2010-10-13 at 17:06 +0300, Nikos Chantziaras wrote: Forgot one last thing. After you do what I described in my other post, make sure to execute: eselect opengl set ati Hi Nikos, Thanks for the advice. I think that the instructions that you're providing, however, are for the closed source ATI driver. I've already battled unsuccessfully with that driver via OpenSUSE, Kubuntu, Fedora and gentoo, so I'm trying to configure using the open source Radeon driver instead, with reference to this wiki here http://en.gentoo-wiki.com/wiki/Radeon Regarding eselect, I used eselect opengl xorg-xll to select the open source driver instead of ati. I think this is correct? The kernel options are configured as follows Device Drivers - Generic Driver Options - * Userspace firmware loading support [*] Include in-kernel firmware blobs in kernel binary Graphics support - * /dev/agpgart (AGP Support) * Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) - * ATI Radeon [*] Enable modesetting on radeon by default When I re-ran emerge radeon-ucode and checked my kernel blobs line in .config, I discovered that I had not included the kernel blobs radeon/R600_rlc.bin and radeon/R700_rlc.bin, so I recompiled the kernel using those options and rebooted after running grub to setup the revised kernel. I also noted the instructions at http://en.gentoo-wiki.com/wiki/Framebuffer#Drivers_with_Kernel_Mode_Setting_.28KMS.29 and recompiled the kernel once more after changing the following settings Device Drivers - Graphics support - [*] Support for frame buffer devices --- [*] Enable firmware EDID [*] Enable Video mode handling helpers Following on further, I found this link http://xorg.freedesktop.org/wiki/radeonBuildHowTo#RemovingAMD.2BAC8-ATIcatalyst.2BAC8-fglrxdriver.28closedsource.29 and discovered that I still had the fglrx.ko module in /lib/modules/2.6.34-gentoo-r6/video, so I deleted it and typed depmod -a After reviewing my /etc/make.conf, I discovered that I had the VIDEO_CARDS=fglrx option set, so I changed that to VIDEO_CARDS=radeon and ran emerge -Dav mesa libdrm xf86-video-ati emerge -NDuav system (nothing to merge) emerge -NDuav world (rebuilt xorg-drivers-1.7 and pm_utils-1.4.1http://xorg.freedesktop.org/wiki/radeonBuildHowTo#RemovingAMD.2BAC8-ATIcatalyst.2BAC8-fglrxdriver.28closedsource.29 I then re-ran grub and tried to boot into the revised kernel, but still no luck getting anything other than software rasteriser. The Xorg.0.log file for this run is attached. I then tried moving the xorg.conf file to another location and restarted with no xorg.conf. I still got only software rasteriser, but now I have errors in Xorg.0.log where fbdev and vesa modules do not exist. This log file is in the second attachment, Xorg.0.log.noXorg.conf Does anyone have any suggestions as to where I go from here? Thanks in advance Jeff X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.34-gentoo-r6 x86_64 Current Operating System: Linux Media-PC 2.6.34-gentoo-r6 #9 SMP Wed Oct 13 20:46:13 EDT 2010 x86_64 Kernel command line: root=/dev/sda3 Build Date: 12 October 2010 08:15:38PM Current version of pixman: 0.18.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Oct 13 21:00:54 2010 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout aticonfig Layout (**) |--Screen aticonfig-Screen[0]-0 (0) (**) | |--Monitor default monitor (**) | |--Device aticonfig-Device[0]-0 (==) No monitor specified for screen aticonfig-Screen[0]-0. Using a default monitor configuration. (**) Option Xinerama off (**) Option AIGLX On (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/cyrillic. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/cyrillic). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/encodings. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/encodings). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/util. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/util). (WW) The directory /usr/share/fonts/TTF/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/OTF does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/Type1/ does not exist. Entry deleted from font path. (**) FontPath set to: /usr/share/fonts/100dpi, /usr/share/fonts/75dpi, /usr/share/fonts/corefonts, /usr/share/fonts/dejavu, /usr/share/fonts/misc, /usr/share/fonts/misc/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ (**)
[gentoo-user] Trying to configure Radeon card
Hi, I have a Sapphire Radeon HD5750 graphics card installed on my Gentoo box, and I'm having some difficulty configuring it. When I run fglrxinfo, I get the OpenGL messages for a basic Mesa driver. I've attached the xorg.conf file, the Xorg.0.log file, and the results of the lspci command. Can anyone tell me what I'm doing wrong? I tried auto-generating an xorg.conf file, but that would result in a totally blank screen. Thanks in advance. Jeff X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.34-gentoo-r6 x86_64 Current Operating System: Linux Media-PC 2.6.34-gentoo-r6 #5 SMP Fri Oct 8 23:13:33 EDT 2010 x86_64 Kernel command line: root=/dev/sda3 Build Date: 08 October 2010 07:45:48PM Current version of pixman: 0.18.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Oct 12 18:51:46 2010 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout aticonfig Layout (**) |--Screen aticonfig-Screen[0]-0 (0) (**) | |--Monitor default monitor (**) | |--Device aticonfig-Device[0]-0 (==) No monitor specified for screen aticonfig-Screen[0]-0. Using a default monitor configuration. (**) Option Xinerama off (**) Option AIGLX On (==) Automatically adding devices (==) Automatically enabling devices (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/100dpi. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/100dpi). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/75dpi. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/75dpi). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/cyrillic. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/cyrillic). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/encodings. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/encodings). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/util. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/util). (WW) The directory /usr/share/fonts/TTF/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/OTF does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/Type1/ does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/100dpi/. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/100dpi/). (WW) `fonts.dir' not found (or not valid) in /usr/share/fonts/75dpi/. Entry deleted from font path. (Run 'mkfontdir' on /usr/share/fonts/75dpi/). (**) FontPath set to: /usr/share/fonts/corefonts, /usr/share/fonts/dejavu, /usr/share/fonts/misc, /usr/share/fonts/misc/ (**) ModulePath set to /usr/lib/xorg/modules,/usr/lib/opengl/xorg-x11/extensions,/usr/lib/dri (**) Extension Composite is enabled (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AutoAddDevices. (II) Loader magic: 0x7c3220 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:1:0:0) 1002:68be:174b:e148 ATI Technologies Inc rev 0, Mem @ 0xd000/268435456, 0xfdfc/131072, I/O @ 0xee00/256, BIOS @ 0x/131072 (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) extmod will be loaded. This was enabled by default and also specified in the config file. (II) dbe will be loaded. This was enabled by default and also specified in the config file. (II) glx will be loaded. This was enabled by default and also specified in the config file. (II) record will be loaded. This was enabled by default and also specified in the config file. (II) dri will be loaded. This was enabled by default and also specified in the config file. (II) dri2 will be loaded. This was enabled by default and also specified in the config file. (II) LoadModule: evdev (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so (II) Module evdev: vendor=X.Org Foundation compiled for 1.7.7, module version = 2.4.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (II) LoadModule: dri (II) Loading /usr/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (II) Loading extension XFree86-DRI (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0
[gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
I have a problem with my gentoo system I am trying to update, and I get a C preprocessor /lib/cpp fails sanity check error on a number of packages. After a bit of searching, the solution that I come across most often is to recompile glibc and gcc. Unfortunately, when I try to compile glibc, I get the same sanity check error. Catch 22. Can anyone help me get around this 'insanity'? Thanks Jeff
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
On Sunday 21 December 2008 11:52:11 am Jeff Cranmer wrote:
On Sunday 21 December 2008 11:11:59 am Justin wrote:
Jeff Cranmer schrieb:
I have a problem with my gentoo system
I am trying to update, and I get a C preprocessor /lib/cpp fails
sanity check error on a number of packages.
After a bit of searching, the solution that I come across most often is
to recompile glibc and gcc. Unfortunately, when I try to compile
glibc, I get the same sanity check error. Catch 22.
Can anyone help me get around this 'insanity'?
Thanks
Jeff
Can you provide some more information please? Logs etc?
Here is the end of the output.
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89...
unsupported checking how to run the C preprocessor... /lib/cpp
configure: error: C preprocessor /lib/cpp fails sanity check
See `config.log' for more details.
*
* ERROR: sys-libs/glibc-2.9_p20081201 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3457: Called eblit-run 'src_compile'
* environment, line 1115: Called eblit-glibc-src_compile
* src_compile.eblit, line 179: Called src_compile
* environment, line 3457: Called eblit-run 'src_compile'
* environment, line 1115: Called eblit-glibc-src_compile
* src_compile.eblit, line 187: Called toolchain-glibc_src_compile
* src_compile.eblit, line 120: Called
glibc_do_configure 'src_compile'
* src_compile.eblit, line 97: Called die
* The specific snippet of code:
* ${S}/configure ${myconf} || die failed to configure glibc
* The die message:
* failed to configure glibc
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located
at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/build.log'.
* The ebuild environment file is located
at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/environment'.
*
* Messages for package sys-libs/glibc-2.9_p20081201:
*
* ERROR: sys-libs/glibc-2.9_p20081201 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3457: Called eblit-run 'src_compile'
* environment, line 1115: Called eblit-glibc-src_compile
* src_compile.eblit, line 179: Called src_compile
* environment, line 3457: Called eblit-run 'src_compile'
* environment, line 1115: Called eblit-glibc-src_compile
* src_compile.eblit, line 187: Called toolchain-glibc_src_compile
* src_compile.eblit, line 120: Called
glibc_do_configure 'src_compile'
* src_compile.eblit, line 97: Called die
* The specific snippet of code:
* ${S}/configure ${myconf} || die failed to configure glibc
* The die message:
* failed to configure glibc
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located
at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/build.log'.
* The ebuild environment file is located
at '/var/tmp/portage/sys-libs/glibc-2.9_p20081201/temp/environment'.
I've attached the build.log, but can't find config.log. Where is this
normally located?
Jeff
After finding this link with a possible solution,
http://www.linux-solved.com/post/gnu-stubs-32-h-No-such-file-or-directory-multilib-SOLVED-564.html
I downloaded binaries of glibc and gcc
I emerged gcc from a binary successfully, but when I tried to install the
glibc binary, it failed because the binary I found was rev 2.6.1, and the
present version is glibc-2.9_p20081201, so emerge would not allow the
downgrade.
The error was
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction
*
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called pkg_setup
* environment, line 3275: Called die
* The specific snippet of code:
* die aborting to save your system;
* The die message:
* aborting to save your system
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located
at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log'.
* The ebuild environment file is located
at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/environment'.
I then tried emerge binutils glibc gcc after running source /etc/profile and
env-update.
binutils emerged successfully, but glibc still failed with the same sanity
check error.
Does anyone know where I can get the latest binary for an amd64 system, or
otherwise get around this issue?
Thanks
Jeff
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
Hmm, if you have a separate machine with the same architecture, you can build those binary packages yourself, just man emerge and take a look at the buildpkg section. Alternatively, you can cross compile binary packages[1]. Or, why not just use a stage tarball? HTH. Joe [1] http://www.gentoo.org/proj/en/base/embedded/cross-development.xml I'm not an expert, and I don't have a second amd64 machine. My laptop runs a different PC processor type. How would I go about cross-compiling an amd64 binary on my laptop, and creating the necessary .tbz2 tarball. If I could do that, I would probably be able to test out the theory that this would fix my broken system. Thanks Jeff
Fwd: Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
On Sunday 21 December 2008 12:43:58 pm Willie Wong wrote: On Sun, Dec 21, 2008 at 11:52:11AM -0500, Penguin Lover Jeff Cranmer squawked: checking whether we are using the GNU C compiler... yes checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... unsupported checking how to run the C preprocessor... /lib/cpp configure: error: C preprocessor /lib/cpp fails sanity check See `config.log' for more details. Try posting config.log in the build directory also. The build log that you posted was virtually identical to this. W where do I find config.log? It wasn't in the same directory as build.log, or in the root directory. Thanks Jeff ---
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
On Sunday 21 December 2008 01:49:41 pm Justin wrote: Jeff Cranmer schrieb: Hmm, if you have a separate machine with the same architecture, you can build those binary packages yourself, just man emerge and take a look at the buildpkg section. Alternatively, you can cross compile binary packages[1]. Or, why not just use a stage tarball? HTH. Joe [1] http://www.gentoo.org/proj/en/base/embedded/cross-development.xml I'm not an expert, and I don't have a second amd64 machine. My laptop runs a different PC processor type. How would I go about cross-compiling an amd64 binary on my laptop, and creating the necessary .tbz2 tarball. If I could do that, I would probably be able to test out the theory that this would fix my broken system. Thanks Jeff Perhaps you should go back to a lower glib version. Latest versions of such important packages might always have issues. What is the approved way to do this? When I tried to install an old version of glibc from a binary, I got the error: The error was * Sanity check to keep you from breaking your system: * Downgrading glibc is not supported and a sure way to destruction * * ERROR: sys-libs/glibc-2.6.1 failed. * Call stack: * ebuild.sh, line 49: Called pkg_setup * environment, line 3275: Called die * The specific snippet of code: * die aborting to save your system; * The die message: * aborting to save your system * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/environment'. The error message Downgrading glibc is not supported and is a sure way to destruction makes me think that going back would not be such a good idea. Jeff
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
Perhaps you should go back to a lower glib version. Latest versions of such important packages might always have issues. What is the approved way to do this? There is no approved way to downgrade glibc. The output message from the error you posted tells you why the devs will not provide you with a method to do it. If you *really* want to do it, your could comment out the if statement between lines 159 and 163 of the latest glibc ebuild. The only correct way I know of is to perform a reinstall. It'll probable be quicker, easier and far less painful than trying to recover from ripping the foundation out from under your OS... However, did you notice that the parent poster mentioned glib and you have attempted to downgrade glibc? The issue that I have is that glibc is broken, probably due to my profile having at some point switched from a 64 bit profile back to i386. After discovering this, I tried to fix this by switching the profile back, and that's when my problems began. glibc appears to be broken, and causes errors when trying to compile (specifically, lib cpp fails the sanity check). Reinstalling glibc from a binary was recommended as a way to fix this, but I don't have access to a binary of the same or more recent vintage as the one already installed on my system. Trying to install an older version that I could find caused the glibc error. emerge -eav system causes the same errors, as glibc appears to require glibc to compile, and since it's not working, I have a circular dependency that I can't resolve. If its OK to do so, and has a chance of working, I could install an older version of glib. All I need to know is how to do this. Any pointers gratefully received. I'd really rather not have to rip out everything and re-install the OS (several days of work), as it's basically working right now - just won't upgrade at the moment. Thanks Jeff Jeff
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
On Sunday 21 December 2008 02:35:56 pm Justin wrote: However, did you notice that the parent poster mentioned glib and you have attempted to downgrade glibc? My fault missed the c. @Jeff Please provide a emerge --info so that we can comment on it. Perhaps this will protect you from some more headache when reinstalling. there ya go :-) Portage 2.1.4.5 (default/linux/amd64/2008.0/desktop, gcc-4.3.2, glibc-2.9_p20081201-r0, 2.6.24-gentoo-r4 x86_64) = System uname: 2.6.24-gentoo-r4 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ Timestamp of tree: Sun, 21 Dec 2008 08:00:01 + app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7-r1, 2.1.6-r1 dev-lang/python: 2.4.4-r13, 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 dev-util/cmake: 2.4.6-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox:1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r2 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS=amd64 CBUILD=x86_64-pc-linux-gnu CFLAGS=-O2 -pipe -march=athlon64 CHOST=x86_64-pc-linux-gnu CONFIG_PROTECT=/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d CXXFLAGS=-O2 -pipe -march=athlon64 DISTDIR=/usr/portage/distfiles FEATURES=distlocks metadata-transfer sandbox sfperms strict unmerge-orphans userfetch GENTOO_MIRRORS=http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo; LDFLAGS=-Wl,-O1 MAKEOPTS=-j3 PKGDIR=/usr/portage/packages PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages PORTAGE_TMPDIR=/var/tmp PORTDIR=/usr/portage SYNC=rsync://rsync.gentoo.org/gentoo-portage USE=X a52 aac acl acpi alsa amd64 asf berkdb bluetooth branding bzip2 cairo cdr cli cracklib crypt cups dar64 dbus doc dri dv dvd dvdr dvdread eds emboss encode esd evo fam firefox foomaticdb fortran gdbm gif gimpprint gnome gpm gstreamer gtk hal iconv ipv6 isdnlog jpeg kde ldap libnotify mad midi mikmod mjpeg mmx mp3 mpeg mudflap multilib ncurses nls nptl nptlonly ogg opengl openmp pam pcre pdf perl png ppds pppd python qt3 qt3support qt4 quicktime readline realmedia reflection scanner sdl session smp spell spl sse sse2 ssl startup-notification svg symlink sysfs tcpd tiff truetype unicode usb vorbis wmf xinerama xml xorg xulrunner xv xvid zlib ALSA_CARDS=hda-intel ALSA_PCM_PLUGINS=adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol APACHE2_MODULES=actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias ELIBC=glibc INPUT_DEVICES=keyboard mouse joystick KERNEL=linux LCD_DEVICES=bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text USERLAND=GNU VIDEO_CARDS=nvidia Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
OK - accepting that my system is broken, I've tried emerge -eav system, and it is failing due to several errors. Other than reformatting the hard drive, how do I reinstall everything? Where do I change the accept keywords variable? It isn't in my make.conf, and if I put an accept keywords line in there, it simply adds to the list of keywords, rather than replacing the amd64 with ~amd64 Jeff On Sunday 21 December 2008 02:49:46 pm Justin wrote: Jeff Cranmer schrieb: On Sunday 21 December 2008 02:35:56 pm Justin wrote: However, did you notice that the parent poster mentioned glib and you have attempted to downgrade glibc? My fault missed the c. @Jeff Please provide a emerge --info so that we can comment on it. Perhaps this will protect you from some more headache when reinstalling. there ya go :-) Portage 2.1.4.5 (default/linux/amd64/2008.0/desktop, gcc-4.3.2, glibc-2.9_p20081201-r0, 2.6.24-gentoo-r4 x86_64) = System uname: 2.6.24-gentoo-r4 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor definitely a 64bit kernel. If you ever switched to a 32bit profile you system is broken and you better reinstall everything. 3800+ Timestamp of tree: Sun, 21 Dec 2008 08:00:01 + app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7-r1, 2.1.6-r1 dev-lang/python: 2.4.4-r13, 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 dev-util/cmake: 2.4.6-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox:1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r2 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS=amd64 You should use ACCEPT_KEYWORDS=~amd64 as long as you don't have alot experience. You can manually enable the usage of masked packages. CBUILD=x86_64-pc-linux-gnu CFLAGS=-O2 -pipe -march=athlon64 CHOST=x86_64-pc-linux-gnu CONFIG_PROTECT=/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c /etc/udev/rules.d CXXFLAGS=-O2 -pipe -march=athlon64 DISTDIR=/usr/portage/distfiles FEATURES=distlocks metadata-transfer sandbox sfperms strict unmerge-orphans userfetch GENTOO_MIRRORS=http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo; LDFLAGS=-Wl,-O1 MAKEOPTS=-j3 PKGDIR=/usr/portage/packages PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages PORTAGE_TMPDIR=/var/tmp PORTDIR=/usr/portage SYNC=rsync://rsync.gentoo.org/gentoo-portage USE=X a52 aac acl acpi alsa amd64 asf berkdb bluetooth branding bzip2 cairo cdr cli cracklib crypt cups dar64 dbus doc dri dv dvd dvdr dvdread eds emboss encode esd evo fam firefox foomaticdb fortran gdbm gif gimpprint gnome gpm gstreamer gtk hal iconv ipv6 isdnlog jpeg kde ldap libnotify mad midi mikmod mjpeg mmx mp3 mpeg mudflap multilib ncurses nls nptl nptlonly ogg opengl openmp pam pcre pdf perl png ppds pppd python qt3 qt3support qt4 quicktime readline realmedia reflection scanner sdl session smp spell spl sse sse2 ssl startup-notification svg symlink sysfs tcpd tiff truetype unicode usb vorbis wmf xinerama xml xorg xulrunner xv xvid zlib ALSA_CARDS=hda-intel ALSA_PCM_PLUGINS=adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol APACHE2_MODULES=actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias ELIBC=glibc INPUT_DEVICES=keyboard mouse joystick KERNEL=linux LCD_DEVICES=bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text USERLAND=GNU VIDEO_CARDS=nvidia Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
To clarify, when I try to run emerge -eav system, the first package which fails is sandbox. It advises me to try FEATURES=-sandbox emerge sandbox in response to the cannot run C compiled programs, but I still get the same error. My research on the web points me back towards gcc not being compiled correctly, which brings me back to the glibc sanity check problem :-( Calculating dependencies... done! Verifying ebuild Manifests... Emerging (1 of 1) sys-apps/sandbox-1.2.18.1-r2 to / * sandbox-1.2.18.1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ...[ ok ] * checking sandbox-1.2.18.1.tar.bz2 ;-) ... [ ok ] Unpacking source... Unpacking sandbox-1.2.18.1.tar.bz2 to /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work * Applying sandbox-1.2.18.1-open-normal-fail.patch ... [ ok ] * Applying sandbox-1.2.18.1-open-cloexec.patch ... [ ok ] Source unpacked. Compiling source in /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/sandbox-1.2.18.1 ... * If configure fails with a 'cannot run C compiled programs' error, try this: * FEATURES=-sandbox emerge sandbox * Configuring sandbox for ABI=x86... * econf: updating sandbox-1.2.18.1/config.guess with /usr/share/gnuconfig/config.guess * econf: updating sandbox-1.2.18.1/config.sub with /usr/share/gnuconfig/config.sub ../sandbox-1.2.18.1//configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib32 --enable-multilib --build=i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-pc-linux-gnu-gcc... no checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log * * ERROR: sys-apps/sandbox-1.2.18.1-r2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2471: Called econf 'src_compile' 'src_compile' * ebuild.sh, line 519: Called die * The specific snippet of code: * die econf failed * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/environment'. * On Sunday 21 December 2008 03:03:59 pm Jeff Cranmer wrote: OK - accepting that my system is broken, I've tried emerge -eav system, and it is failing due to several errors. Other than reformatting the hard drive, how do I reinstall everything? Where do I change the accept keywords variable? It isn't in my make.conf, and if I put an accept keywords line in there, it simply adds to the list of keywords, rather than replacing the amd64 with ~amd64 Jeff On Sunday 21 December 2008 02:49:46 pm Justin wrote: Jeff Cranmer schrieb: On Sunday 21 December 2008 02:35:56 pm Justin wrote: However, did you notice that the parent poster mentioned glib and you have attempted to downgrade glibc? My fault missed the c. @Jeff Please provide a emerge --info so that we can comment on it. Perhaps this will protect you from some more headache when reinstalling. there ya go :-) Portage 2.1.4.5 (default/linux/amd64/2008.0/desktop, gcc-4.3.2, glibc-2.9_p20081201-r0, 2.6.24-gentoo-r4 x86_64) = System uname: 2.6.24-gentoo-r4 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor definitely a 64bit kernel. If you ever switched to a 32bit profile you system is broken and you better reinstall everything. 3800+ Timestamp of tree: Sun, 21 Dec 2008 08:00:01 + app-shells/bash: 3.2_p33 dev-java/java-config: 1.3.7-r1, 2.1.6-r1 dev-lang/python: 2.4.4-r13, 2.5.2-r7 dev-python/pycrypto: 2.0.1-r6 dev-util/cmake: 2.4.6-r1 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox:1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r2 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1-r1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
On Sunday 21 December 2008 03:15:41 pm Justin wrote: Jeff Cranmer schrieb: First avoid top posting OK - accepting that my system is broken, I've tried emerge -eav system, and it is failing due to several errors. Other than reformatting the hard drive, how do I reinstall everything? boot livecd, mount the disc as described in the official manuals [1], extract a propriate tarball, remove all /etc/portage/packages*, review make.conf, emerge -e system, will bring back your system. Where do I change the accept keywords variable? It isn't in my make.conf, and if I put an accept keywords line in there, it simply adds to the list of keywords, rather than replacing the amd64 with ~amd64 Search for it in /etc. I'm afraid you'll need to be a little more specific on the accept keywords variable. Jeff [1] http://www.gentoo.org/doc/en/index.xml?catid=install
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
On Sunday 21 December 2008 03:28:09 pm Justin wrote: Jeff Cranmer schrieb: I'm afraid you'll need to be a little more specific on the accept keywords reinstall and never change this variable. Stick to the many guides out there. Your system is broken and fixing takes the same effort than reinstalling. Except reinstalling raises the specter of losing all my key data. The guides are written for a blank system. That is not what I have. The problem is with glibc. Why can't I fix glibc and then to an emerge -eav from there? Jeff
Re: [gentoo-user] glibc - C preprocessor /lib/cpp fails sanity check
On Sunday 21 December 2008 03:44:37 pm Justin wrote: Jeff Cranmer schrieb: On Sunday 21 December 2008 03:28:09 pm Justin wrote: Jeff Cranmer schrieb: I'm afraid you'll need to be a little more specific on the accept keywords reinstall and never change this variable. Stick to the many guides out there. Your system is broken and fixing takes the same effort than reinstalling. Except reinstalling raises the specter of losing all my key data. The guides are written for a blank system. That is not what I have. The problem is with glibc. Why can't I fix glibc and then to an emerge -eav from there? Jeff boot livecd, mount the disc as described in the official manuals [1], extract a propriate tarball, remove all /etc/portage/packages*, review make.conf, emerge -e system, will bring back your system. OK - since I'm no gentoo expert, I need to define the exact procedure here before I'm going to attempt this, so I have a number of questions: (1) If I remove /etc/portage/packages*, nothing will be removed, as nothing matches that search string, so what exactly should I be removing? Do you mean remove the entire contents of /etc/portage? If I do this, I'll lose all the package.use, keywords, mask information that I have set up. Why is this necessary? It seems that this will just break my system further. (2) In my system, swap is /dev/sda2, boot is /dev/sda5, and root is /dev/sda3 I should skip the fdisk commands, then swapon /dev/sda2 mount /dev/sda3 /mnt/gentoo mount /dev/sda5 /mnt/gentoo/boot cd /mnt/gentoo Is this correct? (3) After extracting the stage3 tarball for an amd64 system, downloaded using links http://www.gentoo.org/main/en/mirrors.xml with the command tar xvjpf stage3-*.tar.bz2, I can then proced with editing make.conf, as I don't need to reinstall a portage snapshot (since I already have one set up from my present install). Is this correct? (4) After editing the make.conf file, verifying that it is correct for a 64 bit system, I then can run the command emerge -e world, and everything should compile correctly? (5) With this method, I will not lose any other key settings such as video, kde etc. Is this correct? Jeff
Re: [gentoo-user] dev-java/sun-jdk-1.6.0.11 Failed to unpack
On Monday 15 December 2008 03:40:00 am Neil Bothwick wrote:
On Sun, 14 Dec 2008 21:48:47 -0500, Jeff Cranmer wrote:
I've also discovered that the /etc/make.profile symlink was pointing at
the x86 default-linux profile set, not the amd64 profile.
I'm attempting a recompile now with the symlink changed, and hopefully
this will fix my problems. I wonder if this latent error is not about
to cost me a whole bunch more though. Is there anything I should do
with the emerge command or any other command in order to correct this
profile problem?
What is your CHOST set to? The output of emerge --info may be helpful
here.
I'd definitely do an emerge -e world once you've got make.conf and your
profile straightened out.
sun-jdk is now installed.
I'm now having problems with gcc, as it fails with an error. I'm guessing
that having an out-of date gcc is probably driving a few more packages to
failure.
* ERROR: sys-devel/gcc-4.1.2 failed.
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 4656: Called toolchain_src_compile
* environment, line 5174: Called gcc_src_compile
* environment, line 2982: Called gcc_do_make
* environment, line 2805: Called die
* The specific snippet of code:
* emake LDFLAGS=${LDFLAGS} STAGE1_CFLAGS=${STAGE1_CFLAGS}
LIBPATH=${LIBPATH} BOOT_CFLAGS=${BOOT_CFLAGS} ${GCC_MAKE_TARGET} ||
die emake failed with ${GCC_MAKE_TARGET};
* The die message:
* emake failed with profiledbootstrap
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located
at '/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log'.
* The ebuild environment file is located
at '/var/tmp/portage/sys-devel/gcc-4.1.2/temp/environment'.
Here's what emerge --info looks like
Portage 2.1.4.5 (default-linux/amd64/2007.0, gcc-4.3.2,
glibc-2.9_p20081201-r0, 2.6.24-gentoo-r4 x86_64)
=
System uname: 2.6.24-gentoo-r4 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor
3800+
Timestamp of tree: Sat, 13 Dec 2008 08:00:01 +
app-shells/bash: 3.2_p33
dev-java/java-config: 1.3.7-r1, 2.1.6
dev-lang/python: 2.4.4-r13, 2.5.2-r7
dev-python/pycrypto: 2.0.1-r6
dev-util/cmake: 2.4.6-r1
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox:1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.61-r2
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2,
1.10.1-r1
sys-devel/binutils: 2.18-r3
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool: 1.5.26
virtual/os-headers: 2.6.23-r3
ACCEPT_KEYWORDS=amd64
CBUILD=x86_64-pc-linux-gnu
CFLAGS=-O2 -pipe -march=athlon64
CHOST=x86_64-pc-linux-gnu
CONFIG_PROTECT=/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
/usr/kde/3.5/shutdown /usr/share/config /var/lib/hsqldb
CONFIG_PROTECT_MASK=/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/
/etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/
/etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild
/etc/terminfo /etc/texmf/web2c /etc/udev/rules.d
CXXFLAGS=-O2 -pipe -march=athlon64
DISTDIR=/usr/portage/distfiles
FEATURES=distlocks metadata-transfer sandbox sfperms strict unmerge-orphans
userfetch
GENTOO_MIRRORS=http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo;
MAKEOPTS=-j3
PKGDIR=/usr/portage/packages
PORTAGE_RSYNC_OPTS=--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --stats --timeout=180 --exclude=/distfiles
--exclude=/local --exclude=/packages
PORTAGE_TMPDIR=/var/tmp
PORTDIR=/usr/portage
SYNC=rsync://rsync.gentoo.org/gentoo-portage
USE=a52 aac acl amd64 asf berkdb cli cracklib crypt cups dar64 doc dri dv
dvdread foomaticdb fortran gdbm gimpprint gpm hal iconv ipv6 isdnlog midi
mjpeg mmx mudflap ncurses nls nptl nptlonly openmp pam pcre pdf perl pppd
python readline realmedia reflection scanner session smp spl sse sse2 ssl
tcpd tiff unicode usb wmf xinerama xorg xulrunner xvid zlib
ALSA_CARDS=hda-intel ALSA_PCM_PLUGINS=adpcm alaw asym copy dmix dshare
dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter
mmap_emul mulaw multi null plug rate route share shm softvol
APACHE2_MODULES=actions alias auth_basic auth_digest authn_anon authn_dbd
authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile
authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd
deflate dir disk_cache env expires ext_filter file_cache filter headers ident
imagemap include info log_config logio mem_cache mime mime_magic negotiation
proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so
speling status unique_id userdir usertrack vhost_alias ELIBC=glibc
INPUT_DEVICES=keyboard mouse joystick KERNEL=linux LCD_DEVICES=bayrad
cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text
USERLAND=GNU VIDEO_CARDS
Re: [gentoo-user] dev-java/sun-jdk-1.6.0.11 Failed to unpack
Thanks, That only adds more questions. My environment is amd64. It appears to have downloaded the i586 binary. Surely this is incorrect? my make.conf file contains the line CFLAGS=-O2 -pipe -march=athlon-xp, which should trigger the 64 bit binaries to be downloaded and acted upon. The CFLAGS variable was previously set to -O2 -pipe -march=athlon64, and I don't think that athlon64 is a valid gcc compile flag, but the response was the same with this set of CFLAGS variables too. Also,since I changed the CFLAGS variable, is there anything I need to do in compilation to correct any errors resulting from the original (I believe invalid) variable? Any suggestions gratefully received. Jeff On Saturday 13 December 2008 06:43:24 pm Jean-Baptiste Mestelan wrote: 2008/12/13 Jeff Cranmer jcranme...@earthlink.net Perhaps it would have done if I knew where the download page was. The file /usr/portage/dev-java/sun-jdk/sun-jdk-1.6.0.11.ebuild will disclose this information, and hints at https://jdk-distros.dev.java.net/developer.html Regards.
Re: [gentoo-user] dev-java/sun-jdk-1.6.0.11 Failed to unpack
Progress: I've discovered that athlon64 is a valid gcc make flag, so I changed it back. I've also discovered that the /etc/make.profile symlink was pointing at the x86 default-linux profile set, not the amd64 profile. I'm attempting a recompile now with the symlink changed, and hopefully this will fix my problems. I wonder if this latent error is not about to cost me a whole bunch more though. Is there anything I should do with the emerge command or any other command in order to correct this profile problem? Thanks Jeff On Sunday 14 December 2008 09:17:22 pm Jeff Cranmer wrote: Thanks, That only adds more questions. My environment is amd64. It appears to have downloaded the i586 binary. Surely this is incorrect? my make.conf file contains the line CFLAGS=-O2 -pipe -march=athlon-xp, which should trigger the 64 bit binaries to be downloaded and acted upon. The CFLAGS variable was previously set to -O2 -pipe -march=athlon64, and I don't think that athlon64 is a valid gcc compile flag, but the response was the same with this set of CFLAGS variables too. Also,since I changed the CFLAGS variable, is there anything I need to do in compilation to correct any errors resulting from the original (I believe invalid) variable? Any suggestions gratefully received. Jeff On Saturday 13 December 2008 06:43:24 pm Jean-Baptiste Mestelan wrote: 2008/12/13 Jeff Cranmer jcranme...@earthlink.net Perhaps it would have done if I knew where the download page was. The file /usr/portage/dev-java/sun-jdk/sun-jdk-1.6.0.11.ebuild will disclose this information, and hints at https://jdk-distros.dev.java.net/developer.html Regards.
Re: [gentoo-user] dev-java/sun-jdk-1.6.0.11 Failed to unpack
It looks like fixing the /etc/make.profile symlink fixed my problem. I'm still a little nervous about whether I need to run any other commands in order to prevent my system going wrong after making this correction. Jeff On Sunday 14 December 2008 09:48:47 pm Jeff Cranmer wrote: Progress: I've discovered that athlon64 is a valid gcc make flag, so I changed it back. I've also discovered that the /etc/make.profile symlink was pointing at the x86 default-linux profile set, not the amd64 profile. I'm attempting a recompile now with the symlink changed, and hopefully this will fix my problems. I wonder if this latent error is not about to cost me a whole bunch more though. Is there anything I should do with the emerge command or any other command in order to correct this profile problem? Thanks Jeff On Sunday 14 December 2008 09:17:22 pm Jeff Cranmer wrote: Thanks, That only adds more questions. My environment is amd64. It appears to have downloaded the i586 binary. Surely this is incorrect? my make.conf file contains the line CFLAGS=-O2 -pipe -march=athlon-xp, which should trigger the 64 bit binaries to be downloaded and acted upon. The CFLAGS variable was previously set to -O2 -pipe -march=athlon64, and I don't think that athlon64 is a valid gcc compile flag, but the response was the same with this set of CFLAGS variables too. Also,since I changed the CFLAGS variable, is there anything I need to do in compilation to correct any errors resulting from the original (I believe invalid) variable? Any suggestions gratefully received. Jeff On Saturday 13 December 2008 06:43:24 pm Jean-Baptiste Mestelan wrote: 2008/12/13 Jeff Cranmer jcranme...@earthlink.net Perhaps it would have done if I knew where the download page was. The file /usr/portage/dev-java/sun-jdk/sun-jdk-1.6.0.11.ebuild will disclose this information, and hints at https://jdk-distros.dev.java.net/developer.html Regards.
Re: [gentoo-user] dev-java/sun-jdk-1.6.0.11 Failed to unpack
Perhaps it would have done if I knew where the download page was. On Saturday 13 December 2008 07:25:36 am Neil Bothwick wrote: On Fri, 12 Dec 2008 23:03:43 -0500, Jeff Cranmer wrote: Failed to extract the files. Please refer to the Troubleshooting section of the Installation Instructions on the download page for more information. Did this help?
[gentoo-user] dev-java/sun-jdk-1.6.0.11 Failed to unpack
I am getting an error when I try to update sun-jdK
/var/tmp/portage/dev-java/sun-jdk-1.6.0.11/distdir/jdk-6u11-dlj-linux-i586.bin:
line 821: ./install.sfx.14482: No such file or directory
Failed to extract the files. Please refer to the Troubleshooting section of
the Installation Instructions on the download page for more information.
*
* ERROR: dev-java/sun-jdk-1.6.0.11 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 2683: Called die
* The specific snippet of code:
* sh ${DISTDIR}/${A} --accept-license --unpack || die Failed to
unpack
* The die message:
* Failed to unpack
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located
at '/var/tmp/portage/dev-java/sun-jdk-1.6.0.11/temp/build.log'.
* The ebuild environment file is located
at '/var/tmp/portage/dev-java/sun-jdk-1.6.0.11/temp/environment'
Can anyone shed any light on this error for me?
Thanks
Jeff
[gentoo-user] Printing to an HPD7400 Series Printer
Can anyone help me with the correct CUPs settings to print to an HP D7400 series printer over a wireless network? I can access the printer's home page via the IP address, but when I set up CUPS with the printer option socket://192.168.2.4, the job fails, and the printer screen returns the error /usr/libexec/cups/filter/foomatic-rip failed. I'm using the HP PhotoSmart D7400 Foomatic/hpijs driver. Any suggestions gratefully received. Thanks Jeff -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] Viewing BBC videos on Gentoo
Has anyone had any luck viewing videos on news.bbc.co.uk using gentoo? I have Firefox and mplayerplug-in installed, however I cannot view videos, either with the embedded player or the standalone. Jeff -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Viewing BBC videos on Gentoo
This PC is a 32 bit OS. It does have flash - all youtube videos work OK. Jeff -Original Message- From: Ian Lee [EMAIL PROTECTED] Sent: Feb 10, 2008 1:04 PM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Viewing BBC videos on Gentoo Ian Lee wrote: Jeff Cranmer wrote: Has anyone had any luck viewing videos on news.bbc.co.uk using gentoo? I have Firefox and mplayerplug-in installed, however I cannot view videos, either with the embedded player or the standalone. Jeff It's a flash based player mplayer wont work If you're using 64 bit firefox net-www/nspluginwrapper is a good way to get flash working or theres firefox-bin -- gentoo-user@lists.gentoo.org mailing list -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Viewing BBC videos on Gentoo
Ah - it appears that if I copy the weblink, then open it in Realplayer, I can successfully view the videos. The question is, how do I get firefox to launch realplayer as the standalone player instead of mplayerplug-in? Jeff -Original Message- From: Jerry McBride [EMAIL PROTECTED] Sent: Feb 10, 2008 1:12 PM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Viewing BBC videos on Gentoo On Sunday 10 February 2008 12:48:44 pm Jeff Cranmer wrote: Has anyone had any luck viewing videos on news.bbc.co.uk using gentoo? I have Firefox and mplayerplug-in installed, however I cannot view videos, either with the embedded player or the standalone. Jeff Works here. Running Gentoo, firefox and the realplayer plugin. When you click on a video, in the next box click on stand-alone player and use realplayer. Takes a while for the stream to start, but once it does it's ok... -- From the Desk of: Jerome D. McBride -- gentoo-user@lists.gentoo.org mailing list -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Viewing BBC videos on Gentoo
From the Desk of: Jerome D. McBride I can use realplayer aswell, I use it to stream BBC radio, though it works better if you click launch as a stand-alone player, the embeded version tends to skip a bit How do I get firefox to use realplayer for bbc audio and video files instead of defaulting to mplayer? -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] Sandisk mounting problems
Try rmmod ehci-hcd, then modprobe ohci-hcd and see what happens. Also, include from /var/log/messages everything printed from when ohci-hcd is modprobed to then end of actually plugging in the Sansa. And again when trying ehci-hcd. -- ohci was not included in my kernel. I recompiled with ehci and uhci as modules, then ran rmmod ehci-hcd Since my wireless ethernet adapter is also a usb module, the output is a little verbose, so my apologies in advance for the length of the dmesg output below. That did seem to get the card working, so I then recompiled a kernel with uhci support only, and I was then able to attach the device. This seems to be a little extreme, however, as I know this device maps correctly on my desktop in ehci mode. Can you discern anything from the dmesg output which might shed some light on the real root cause? Thanks Jeff ehci_hcd :00:1d.7: remove, state 1 usb usb7: USB disconnect, address 1 ehci_hcd :00:1d.7: USB bus 7 deregistered ACPI: PCI interrupt for device :00:1d.7 disabled ehci_hcd :00:1a.7: remove, state 1 usb usb6: USB disconnect, address 1 usb 6-2: USB disconnect, address 2 RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) RX Status Error! RX process aborted due to explicit shutdown (ff94) 4rtl8180_close process rtl8180_down process read_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_word TimeOut! status:ffed read_nic_byte TimeOut! status:ffed write_nic_dword TimeOut! status:ffed write_nic_word TimeOut! status:ffed read_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed read_nic_dword TimeOut! status:ffed write_nic_dword TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed read_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed read_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_dword TimeOut! status:ffed read_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed read_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed write_nic_byte TimeOut! status:ffed read_nic_word TimeOut! status:ffed read_nic_word TimeOut! status:ffed read_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed write_nic_word TimeOut! status:ffed
[gentoo-user] Sandisk mounting problems
I have a new Sansa Sandisk MP3 player. When I plug it in, I get the following dmesg output usb 2-1: new high speed USB device using ehci_hcd and address 3 ehci_hcd :00:1d.7: port 1 reset error -110 hub 2-0:1.0: hub_port_status failed (err = -32) I have been able to successfully mount several other players. Has anyone had similar problems or can offer a potential solution? Thanks Jeff -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
On Saturday 22 December 2007 10:30:45 am Hans-Werner Hilse wrote: I think I'm getting closer now. I removed the driver from the kernel, and installed ndiswrapper. I got the inf driver from a guy from realtek, and used ndiswrapper -i drivername.inf to install it. Now, when I run iwlist wlan0 scanning, I can actually see my access point listed, plus lots of other local wireless networks. That's good. It actually receives. connecting to it is a different matter, however, as the connection always appears to time out. I'm using iwconfig to manually set the ESSID, wep key etc. at the moment, and have tried the trick of setting the speed manually to 5.5M to avoid timeouts. When I try to run dhcpcd wlan0 the first time, I get Error, wlan0: timed out The second time I try to run it, I get an error because dhcpcd is already running. Try the minimal approach first and configure it manually using ifconfig/route and ping some host on your network (or the AP if it does IP). If that does not work, there's something wrong with the driver, if it does, the culprit is dhcpcd (vram USE flag?). Just to clarify, how would I ping a host on my network? I only have one other PC connected to the router. If that is not possible, due to wireless router firewall stealthing (I have a rather crash-prone Belkin wireless router at the moment), the next attempt would presumably be to ping the AP. If I have an AP MAC address, 00:15:E9:19:73:F2 (for example), how would I ping this? I have checked the dhcpcd install, and the vram USE flag is presently unset. Does this flag need to be set? Start with WEP, if that works switch to WPA. I've given up on WPA for now. If I can get WEP to work, I'll be happy at this point, though WPA operation would be the ultimate goal. Is ndiswrapper meant to work with the 2.6.23 kernel? I don't want to have to step down to an earlier kernel, as that causes problems with changing Xorg configurations, but I could go through the pain of this if it were strictly necessary. Thanks Jeff -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
-Original Message- From: Mick [EMAIL PROTECTED] Sent: Dec 22, 2007 2:01 PM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] realtek 8197 wireless card setup On Saturday 22 December 2007, Jeff Cranmer wrote: On Saturday 22 December 2007 10:30:45 am Hans-Werner Hilse wrote: I think I'm getting closer now. I removed the driver from the kernel, and installed ndiswrapper. I got the inf driver from a guy from realtek, and used ndiswrapper -i drivername.inf to install it. Now, when I run iwlist wlan0 scanning, I can actually see my access point listed, plus lots of other local wireless networks. That's good. It actually receives. Yep, you're half way there. The radio communication part of the equation seems to be working. connecting to it is a different matter, however, as the connection always appears to time out. I'm using iwconfig to manually set the ESSID, wep key etc. at the moment, and have tried the trick of setting the speed manually to 5.5M to avoid timeouts. When I try to run dhcpcd wlan0 the first time, I get Error, wlan0: timed out The second time I try to run it, I get an error because dhcpcd is already running. Try to kill it first (dhcpcd -k) and then re-run it. I would run with defaults (re. channel, speed, etc.) and perhaps only add a small delay in your /etc/conf.d/net to allow the device to come up: sleep_scan_wlan0=1 Try the minimal approach first and configure it manually using ifconfig/route and ping some host on your network (or the AP if it does IP). If that does not work, there's something wrong with the driver, if it does, the culprit is dhcpcd (vram USE flag?). Just to clarify, how would I ping a host on my network? I only have one other PC connected to the router. You use the LAN IP address of the router/host. I don't know what options Belkin gives you, can you turn on responses to pings (ICMP packet requests) both on the router and on the other PC? If that is not possible, due to wireless router firewall stealthing (I have a rather crash-prone Belkin wireless router at the moment), the next attempt would presumably be to ping the AP. If I have an AP MAC address, 00:15:E9:19:73:F2 (for example), how would I ping this? You could use arping (net-analyzer/arping) - but that assumes that the router accepts broadcast messages. I have checked the dhcpcd install, and the vram USE flag is presently unset. Does this flag need to be set? Well, it may need to be set depending on your router. Certain dhcpcd server implementations won't play nicely with the latest stable version of the dhcpcd client and you end up getting time outs and no IP address. Re-emerging with vram USE flag set solves this problem. Manually setting up an available/suitable static LAN IP address may also work (e.g. ifconfig wlan0 192.168.0.2). Start with WEP, if that works switch to WPA. I've given up on WPA for now. If I can get WEP to work, I'll be happy at this point, though WPA operation would be the ultimate goal. Is ndiswrapper meant to work with the 2.6.23 kernel? I don't want to have to step down to an earlier kernel, as that causes problems with changing Xorg configurations, but I could go through the pain of this if it were strictly necessary. ndiswrapper works fine with this kernel. I would start with the dhcpcd vram flag to take this time out problem out of the equation and then I would edit the /etc/conf.d/net to set up all necessary parameters instead of having to enter everything via iwconfig at the command line. This will also minimise the chance of typos at the CLI. Following a process of elimination I would start with no encryption whatsoever at the router and if it works I would then gradually add WEP and finally WAP. PS. Assuming you get ndiswrapper going you can retry the in-kernel driver in future versions as it is likely that more and more devices will be added. HTH. -- Regards, Mick I tried recompiling with the vram USE flag set in dhcpcd, but that didn't help. I then uninstalled ndiswrapper, and installed the modified rtl8187 driver from http://www.datanorth.net/~cuervo/blog/2007/09/26/no-more-vista. SUCCESS!! :-D Finally, I have a working wireless card. I've not tried WPA yet, but WEP definitely works. It isn't quite perfect, as knetworkmanager can't recognise the connection, and i haven't quite figured out how to implement the required startup script to run automatically, but it's up, and only requires a single root user command to execute. Jeff I think I'll give it a couple of kernels and see if the built-in RTL driver improves. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
On Friday 21 December 2007 09:21:03 am Hans-Werner Hilse wrote: Hi, On Thu, 20 Dec 2007 18:45:26 -0500 Jeff Cranmer [EMAIL PROTECTED] wrote: The card I have is an 8197, not an 8187. I wonder if this is part of the problem. Could it be that the kernel driver does not support the 8197? [...] At the moment, I think the key line in dmesg is . phy0: RF calibration failed! 0 If I could figure out what this line meant, and what I could do to fix it, I might be on my way to a potential solution. Well, although you managed to bring it to a point where at least the driver recognized the device, there is still the possibility it won't work anyway. My guess here is that the driver does not fully support your device. Probably, some back end mechanics is different. WLAN cards often consist of separate modules, some of them even being small computers running a firmware. I guess at that point your hardware differs from what the driver supports. Did you find indications on the Web that the 8187 driver should work for the 8197? Or did you chose to try based on the similarity of the two numbers? you might also want to try asking on the driver's mailing list. -hwh I think I'm getting closer now. I removed the driver from the kernel, and installed ndiswrapper. I got the inf driver from a guy from realtek, and used ndiswrapper -i drivername.inf to install it. Now, when I run iwlist wlan0 scanning, I can actually see my access point listed, plus lots of other local wireless networks. connecting to it is a different matter, however, as the connection always appears to time out. I'm using iwconfig to manually set the ESSID, wep key etc. at the moment, and have tried the trick of setting the speed manually to 5.5M to avoid timeouts. When I try to run dhcpcd wlan0 the first time, I get Error, wlan0: timed out The second time I try to run it, I get an error because dhcpcd is already running. Also, when I try running /etc/init.d/net.wlan0 start, I get the error WEP key is not set for my_wireless_network_name - not connecting followed by similar errors for other nearby wireless networks, then * Couldn't associate with any access points on wlan0 * Failed to configure wireless for wlan0 Damn, this has to be the most frustrating thing I've tried to do on gentoo. I know I'm close, because the OS can now see the access point. All I need to do is stop it timing out and connect to it :-/ Jeff -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
On Thursday 20 December 2007 03:40:07 am Mick wrote: Hi Jeff, On Wednesday 19 December 2007, Jeff Cranmer wrote: I have checked, and ndiswrapper and the rtl8187 package were uninstalled. I think that the problem I have may be more basic. The card I have is an 8197, not an 8187. I wonder if this is part of the problem. Could it be that the kernel driver does not support the 8197? The attached weblink suggests that this may be the case: http://www.datanorth.net/~cuervo/blog/2007/09/26/no-more-vista/ Does anyone know how I can locate the equivalent code in the kernel and perhaps perform a similar modification? (can you please stop top-posting, it makes reading of threads difficult in this mailing list). Your device may still be supported by the driver. The problem may exist with the wpa_supplicant. You could try commenting out the wpa_supplicant in your /etc/conf.d/net file and using net-wireless/wireless-tools instead. Then try again to see if it a)finds the access point (try iwlist wlan0 scanning), b)associates with it (try iwlist wlan0 accesspoint) . Of course you will need to remove WPA from the AP. Should all this succeed you can work your way up from there. PS. I haven't managed to make wpa_supplicant work with my device rt2570usb for more than a year now, but haven't tried recently. I tried removing any reference to wpa_supplicant. The alternative /etc/conf.d/net configuration that I tried is: essid_wlan0=mynetworkname channel_wlan0=( 2 ) # the channel my wireless card is presently set to key_home=( my_hex_WEP_key enc open ) config_wlan0=( dhcp ) dhcpcd_wlan0=-I '' iwlist wlan0 scanning returns wlan0 Interface does not support scanning : Network is down iwlist wlan0 accesspoint returns wlan0 Interface doesn't have a list of Peers/Access-Points At the moment, I think the key line in dmesg is . phy0: RF calibration failed! 0 If I could figure out what this line meant, and what I could do to fix it, I might be on my way to a potential solution. Jeff -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
On Thursday 20 December 2007 02:00:36 am Hans-Werner Hilse wrote:
Hi,
I cannot really go into details, but maybe I'm competent enough to make
some notes on this:
On Wed, 19 Dec 2007 21:47:55 -0500
Jeff Cranmer [EMAIL PROTECTED] wrote:
I manually edited the file
/usr/src/linux/drivers/net/wireless/rtl8187_dev.c [...]
I added the line
{USB_DEVICE(0x0bda, 0x8197)},
in the /* Realtek */ area of the structure, then ran
make clean, then
make make modules_install etc.
After rebooting into the modified kernel, I now have iwmaster0 and iwlan0
lines showing up when I type iwconfig.
Although that's a good sign, it does not guarantee that the driver
fully supports your device. However, the kernel log should now have
changed significantly and the driver might now tell you there if it's
fully operable. ifconfig showing the correct MAC is also a good sign.
As a side note: My suggestion would be to play with the different
drivers of wpa_supplicant. DHCP won't work if there's no correct WPA
setup anyway.
-hwh
ifconfig only shows the eth0 and lo interfaces, whereas iwconfig shows info on
the wireless interface, but not the MAC address
The MAC address does appear in the dmesg logs, with the line
phy0: hwaddr actual address not put in e-mail, rtl8187 V0 + rtl8225
This is followed by
phy0: RF calibration failed! 0
which I think is the key symptom that I need to address in order to move
forwards.
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
I have checked, and ndiswrapper and the rtl8187 package were uninstalled. I think that the problem I have may be more basic. The card I have is an 8197, not an 8187. I wonder if this is part of the problem. Could it be that the kernel driver does not support the 8197? The attached weblink suggests that this may be the case: http://www.datanorth.net/~cuervo/blog/2007/09/26/no-more-vista/ Does anyone know how I can locate the equivalent code in the kernel and perhaps perform a similar modification? Thanks Jeff On Monday 17 December 2007 06:26:41 pm Jeff Cranmer wrote: I have rtl8187 compiled into the kernel. I could try compiling it as a module, then loading it via modules.autoload, to see if that gives any alternative response. Perhaps the first step would be not to put it in modules.autoload and modprobe it to more easily see the response. Since I was playing around with ndiswrapper and the rtl8187 portage package, it's possible that they may be messing things up, and I can't remember whether or not I unmerged them. I'll check whether these packages are still present and get rid of them if they are. I'm away from my laptop at the moment, so can't run the dmesg command you suggested until tomorrow evening. I'll let you know whether my activities reveal anything interesting then. Thanks Jeff -Original Message- From: Stroller [EMAIL PROTECTED] Sent: Dec 16, 2007 8:13 PM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] realtek 8197 wireless card setup On 16 Dec 2007, at 22:56, Mick wrote: On Sunday 16 December 2007, Stroller wrote: On 16 Dec 2007, at 17:14, Mick wrote: On Sunday 16 December 2007, Jeff Cranmer wrote: Running the command 'dmesg | grep rtl8187' after reboot returns the message usbcore: registered new interface driver rtl8187 All I get for iwconfig is lo no wireless extensions eth0no wireless extensions. This means that the driver has not been loaded yet. Looking at Jeff's previous post (quoted added above) that's not a conclusion I'd jump to. Oops! Sorry, didn't see that. If the driver is loaded then why isn't an interface showing up? Good question. I agree that without seeing that statement I might well have thought the same thing. That's why I wrote: But it would have helped if Jeff had posted `dmesg | grep rtl8187 iwconfig` in the same post to prove the point. Stroller. -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
I've tried to run through the instructions at http://gentoo-wiki.com/HARDWARE_rtl8187. The kernel is configured per that guide, and I get the message: usbcore: registered new interface driver rtl8187 When I try to run ifconfig wlan0 up, however, I get: wlan0: unknown interface: no such device I get the same result if I run ifconfig wlan up (net.wlan is the symlink that I set up in /etc/init.d) The wireless section of my /etc/conf.d/net file reads mode_wlan=managed wpa_supplicant_wlan=-Dwext -c /etc/wpa_supplicant/wpa_supplicant_RTL8187.conf config_wlan=( dhcp ) dhcp_wlan=-R -G wpa_supplicant has been emerged. Jeff On Sunday 16 December 2007 12:14:42 pm Mick wrote: On Sunday 16 December 2007, Jeff Cranmer wrote: All I get for iwconfig is lo no wireless extensions eth0no wireless extensions. This means that the driver has not been loaded yet. In generic terms you'll need to install the necessary driver for your WiFi device (either the new one in the kernel or emerge net-wireless/rtl8187, or ndiswrapper and the MS Windows driver). If you build the driver as a module then you need to modprobe -v rtl8187, while you keep an eye on the logs to see how things go (tail -f /var/log/messages). You have seen this, right? http://gentoo-wiki.com/HARDWARE_rtl8187 I think I need some more info in /etc/conf.d/net, and need somehow to create the necessary /etc/init.d/net.wlan0 or whatever driver. The only 'net.anything' drivers present at the moment are net.lo and net.eth0 You will of course have to manually create a symlink between net.wlan0 - net.lo (or whatever your new WiFi device is recognised as by the kernel) so that you can bring it up by running /etc/init.d/net.wlan0 start. But this is only necessary for autoloading the driver through the runlevel scripts. To try it out follow the instructions in the Wiki page above. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
I made significant progress today.
I manually edited the file /usr/src/linux/drivers/net/wireless/rtl8187_dev.c
There is a static structure near the top of the code,
static struct usb_device_id rtl8187_table[] __devinitdata = {
/* Realtek */
{USB_DEVICE(0x0bda, 0x8187)},
/* netgear */
{USB_DEVICE(0x0846, 0x6100)},
{USB_DEVICE(0x0846, 0x6a00)},
{}
};
I added the line
{USB_DEVICE(0x0bda, 0x8197)},
in the /* Realtek */ area of the structure, then ran
make clean, then
make make modules_install etc.
After rebooting into the modified kernel, I now have iwmaster0 and iwlan0
lines showing up when I type iwconfig.
The applicable lines of iwconfig are
wmaster0no wireless extensions
wlan0 IEEE 802.11g ESSID=mynetworkESSID
Mode:ManagedFrequency=2.417GHz Access Point:
Not associated
Retry min limit 7 RTS thr:off Fragment
thr=2346B
Encryption key:not telling you
Link Quality:0 Signal Level:0 Noise
Level:0
Rx Invalid nwid:0 Rx invalid crypt:0 Rx
invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed
beacon:0
I'm not all the way there yet, but this is significant progress.
wpa_supplicant gui still is blank, with the message 'could not get status from
WPA_supplicant', but at least now I have an interface showing up
It appears that it cannot find an access point. The access point is active,
as I can connect my work laptop to it, but so far, the laptop can't see it.
Any further advice gratefully received.
Jeff
On Wednesday 19 December 2007 06:09:50 pm Jeff Cranmer wrote:
I've tried to run through the instructions at
http://gentoo-wiki.com/HARDWARE_rtl8187.
The kernel is configured per that guide, and I get the message:
usbcore: registered new interface driver rtl8187
When I try to run ifconfig wlan0 up, however, I get:
wlan0: unknown interface: no such device
I get the same result if I run ifconfig wlan up (net.wlan is the symlink
that I set up in /etc/init.d)
The wireless section of my /etc/conf.d/net file reads
mode_wlan=managed
wpa_supplicant_wlan=-Dwext -c
/etc/wpa_supplicant/wpa_supplicant_RTL8187.conf config_wlan=( dhcp )
dhcp_wlan=-R -G
wpa_supplicant has been emerged.
Jeff
On Sunday 16 December 2007 12:14:42 pm Mick wrote:
On Sunday 16 December 2007, Jeff Cranmer wrote:
All I get for iwconfig is
lono wireless extensions
eth0 no wireless extensions.
This means that the driver has not been loaded yet. In generic terms
you'll need to install the necessary driver for your WiFi device (either
the new one in the kernel or emerge net-wireless/rtl8187, or ndiswrapper
and the MS Windows driver). If you build the driver as a module then you
need to modprobe -v rtl8187, while you keep an eye on the logs to see how
things go (tail -f /var/log/messages). You have seen this, right?
http://gentoo-wiki.com/HARDWARE_rtl8187
I think I need some more info in /etc/conf.d/net, and need somehow to
create the necessary /etc/init.d/net.wlan0 or whatever driver.
The only 'net.anything' drivers present at the moment are net.lo and
net.eth0
You will of course have to manually create a symlink between net.wlan0 -
net.lo (or whatever your new WiFi device is recognised as by the kernel)
so that you can bring it up by running /etc/init.d/net.wlan0 start. But
this is only necessary for autoloading the driver through the runlevel
scripts. To try it out follow the instructions in the Wiki page above.
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
Final piece of info for the day.
When I ran dhcpcd wlan0, I get
Error, wlan0: timed out
Error, wlan0: lease information file '/var/lib/dhcpcd/dhcpcd-wlan0.info' does
not exist
Any assistance gratefully received
Jeff
On Wednesday 19 December 2007 09:47:55 pm Jeff Cranmer wrote:
I made significant progress today.
I manually edited the file
/usr/src/linux/drivers/net/wireless/rtl8187_dev.c
There is a static structure near the top of the code,
static struct usb_device_id rtl8187_table[] __devinitdata = {
/* Realtek */
{USB_DEVICE(0x0bda, 0x8187)},
/* netgear */
{USB_DEVICE(0x0846, 0x6100)},
{USB_DEVICE(0x0846, 0x6a00)},
{}
};
I added the line
{USB_DEVICE(0x0bda, 0x8197)},
in the /* Realtek */ area of the structure, then ran
make clean, then
make make modules_install etc.
After rebooting into the modified kernel, I now have iwmaster0 and iwlan0
lines showing up when I type iwconfig.
The applicable lines of iwconfig are
wmaster0 no wireless extensions
wlan0 IEEE 802.11g ESSID=mynetworkESSID
Mode:ManagedFrequency=2.417GHz Access Point:
Not associated
Retry min limit 7 RTS thr:off Fragment
thr=2346B
Encryption key:not telling you
Link Quality:0 Signal Level:0 Noise
Level:0
Rx Invalid nwid:0 Rx invalid crypt:0 Rx
invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed
beacon:0
I'm not all the way there yet, but this is significant progress.
wpa_supplicant gui still is blank, with the message 'could not get status
from WPA_supplicant', but at least now I have an interface showing up
It appears that it cannot find an access point. The access point is
active, as I can connect my work laptop to it, but so far, the laptop can't
see it.
Any further advice gratefully received.
Jeff
On Wednesday 19 December 2007 06:09:50 pm Jeff Cranmer wrote:
I've tried to run through the instructions at
http://gentoo-wiki.com/HARDWARE_rtl8187.
The kernel is configured per that guide, and I get the message:
usbcore: registered new interface driver rtl8187
When I try to run ifconfig wlan0 up, however, I get:
wlan0: unknown interface: no such device
I get the same result if I run ifconfig wlan up (net.wlan is the symlink
that I set up in /etc/init.d)
The wireless section of my /etc/conf.d/net file reads
mode_wlan=managed
wpa_supplicant_wlan=-Dwext -c
/etc/wpa_supplicant/wpa_supplicant_RTL8187.conf config_wlan=( dhcp )
dhcp_wlan=-R -G
wpa_supplicant has been emerged.
Jeff
On Sunday 16 December 2007 12:14:42 pm Mick wrote:
On Sunday 16 December 2007, Jeff Cranmer wrote:
All I get for iwconfig is
lo no wireless extensions
eth0no wireless extensions.
This means that the driver has not been loaded yet. In generic terms
you'll need to install the necessary driver for your WiFi device
(either the new one in the kernel or emerge net-wireless/rtl8187, or
ndiswrapper and the MS Windows driver). If you build the driver as a
module then you need to modprobe -v rtl8187, while you keep an eye on
the logs to see how things go (tail -f /var/log/messages). You have
seen this, right?
http://gentoo-wiki.com/HARDWARE_rtl8187
I think I need some more info in /etc/conf.d/net, and need somehow to
create the necessary /etc/init.d/net.wlan0 or whatever driver.
The only 'net.anything' drivers present at the moment are net.lo and
net.eth0
You will of course have to manually create a symlink between net.wlan0
- net.lo (or whatever your new WiFi device is recognised as by the
kernel) so that you can bring it up by running /etc/init.d/net.wlan0
start. But this is only necessary for autoloading the driver through
the runlevel scripts. To try it out follow the instructions in the Wiki
page above.
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
All I get for iwconfig is lo no wireless extensions eth0no wireless extensions. I think I need some more info in /etc/conf.d/net, and need somehow to create the necessary /etc/init.d/net.wlan0 or whatever driver. The only 'net.anything' drivers present at the moment are net.lo and net.eth0 Jeff On Sunday 16 December 2007 05:50:49 am Florian Philipp wrote: On Sat, 2007-12-15 at 23:19 -0500, Jeff Cranmer wrote: On Tuesday 11 December 2007 09:48:10 am Mick wrote: On Tuesday 11 December 2007, Jeff Cranmer wrote: I believe that I have this enabled, however ieee80211 is still barfing out by asking for CONFIG_NET_RADIO. I'll check and confirm this tonight. Also check bugzilla. I remember reporting a bug with the more recent kernels failing to build kernel drivers. The last kernel that I managed to build rt2570 was 2.6.20-gentoo-r8. Kernel 2.6.23-gentoo-r3 fails to emerge any driver whatsoever. I have now (finally) successfully compiled the latest kernel 2.6.23-gentoo-r3 kernel. Once I enabled the 'Generic IEEE 802.11 Networking Stack (mac80211)' option in Networking -- Wireless, the Realtek RTL8187 USB support option appears in Device Drivers -- Network Device Support -- Wireless LAN section under wireless LAN (IEEE 802.11). With this RTL8187 driver compiled into the kernel, I get some success. Running the command 'dmesg | grep rtl8187' after reboot returns the message usbcore: registered new interface driver rtl8187 There is, however, no /etc/init.d/net.wlan0 on my system, so I'm not quite there yet. There is a net.eth0 (wired network), and a net.lo What do I need to do to get net.wlan0 active? Thanks Jeff Check the output of iwconfig. Maybe the device's got another name like eth1 or rtl0 -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
On Tuesday 11 December 2007 09:48:10 am Mick wrote: On Tuesday 11 December 2007, Jeff Cranmer wrote: I believe that I have this enabled, however ieee80211 is still barfing out by asking for CONFIG_NET_RADIO. I'll check and confirm this tonight. Also check bugzilla. I remember reporting a bug with the more recent kernels failing to build kernel drivers. The last kernel that I managed to build rt2570 was 2.6.20-gentoo-r8. Kernel 2.6.23-gentoo-r3 fails to emerge any driver whatsoever. I have now (finally) successfully compiled the latest kernel 2.6.23-gentoo-r3 kernel. Once I enabled the 'Generic IEEE 802.11 Networking Stack (mac80211)' option in Networking -- Wireless, the Realtek RTL8187 USB support option appears in Device Drivers -- Network Device Support -- Wireless LAN section under wireless LAN (IEEE 802.11). With this RTL8187 driver compiled into the kernel, I get some success. Running the command 'dmesg | grep rtl8187' after reboot returns the message usbcore: registered new interface driver rtl8187 There is, however, no /etc/init.d/net.wlan0 on my system, so I'm not quite there yet. There is a net.eth0 (wired network), and a net.lo What do I need to do to get net.wlan0 active? Thanks Jeff -- [EMAIL PROTECTED] mailing list
[gentoo-user] kernel configuration problems
I am presently having problems compiling suspend2 kernel 2.6.22. It compiles with genkernel, but if I try to use make and customise a special kernel, it will not find my hard drive. The error message reports that the ide-cdrom on hda is the only drive present. The computer is a Toshiba L45-7409 laptop. Can anyone offer me any guidance as to which kernel options to engage, whether to use modules or compiled-in, etc. Thanks Jeff -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] realtek 8197 wireless card setup
I believe that I have this enabled, however ieee80211 is still barfing out by asking for CONFIG_NET_RADIO. I'll check and confirm this tonight. Jeff -Original Message- From: Jacek Szpot [EMAIL PROTECTED] Sent: Dec 11, 2007 7:07 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] realtek 8197 wireless card setup On Mon, 2007-12-10 at 23:09 -0500, Jeff Cranmer wrote: Can anyone point me to a resource for configuration of a realtek 8197 wireless card on a Toshiba laptop? I am running the 2.6.22-suspend2-r2 kernel, and have installed ndiswrapper. Unfortunately, when I try to install ieee80211, I get an error because CONFIG_NET_RADIO is not configured in the kernel. Unfortunately, CONFIG_NET_RADIO does not exist in this kernel, and hence I'm presently a little stuck. When I type lsusb, I get Bus 001 Device 002: ID 0bda:8197 Realtek Semiconductor Corp. I'd like to connect up to my Belkin Router using WPA/PSK if possible. Thanks in advance Jeff 2.6.22 and up use CONFIG_WLAN_80211 instead of CONFIG_NET_RADIO. Jack -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
[gentoo-user] realtek 8197 wireless card setup
Can anyone point me to a resource for configuration of a realtek 8197 wireless card on a Toshiba laptop? I am running the 2.6.22-suspend2-r2 kernel, and have installed ndiswrapper. Unfortunately, when I try to install ieee80211, I get an error because CONFIG_NET_RADIO is not configured in the kernel. Unfortunately, CONFIG_NET_RADIO does not exist in this kernel, and hence I'm presently a little stuck. When I type lsusb, I get Bus 001 Device 002: ID 0bda:8197 Realtek Semiconductor Corp. I'd like to connect up to my Belkin Router using WPA/PSK if possible. Thanks in advance Jeff -- [EMAIL PROTECTED] mailing list
Fwd: Re: [gentoo-user] Kernel 2.6.22-r9 installation problems
On Monday 19 November 2007 12:35:14 am Billy Holmes wrote: Jeff Cranmer wrote: Cannot open root device sda3 or unknown block (0,0) Please append a correct root= boot option. Here are the available partitions run make menuconfig in your new kernel dir. check to ensure ext3 is compiled in. (not sure why it wouldn't be) ext3 journalling file system support, ext3 extended attributes and ext3 posix access control lists are all compiled into the kernel. check to make sure you've got udev or devfs installed properly in both kernels (maybe one isn't defined in the kernel, and the old kernel had it). I'd really try to ensure you're running udev and not devfs, but first things first. IF SATA: Make sure the proper SATA options are the same for each kernel. There's one SATA option that isn't compatible with another SATA option. (it could be fixed in newer kernels by now) From dmesg for the current working kernel, I worked out that the drive which it is having trouble finding is a serial ATA drive, running the sata_nv driver. Vendor: ATA Model: WDC WD2500JS-60N Rev: 10.0 Type: Direct-Access ANSI SCSI revision: 05 I disabled all the SATA drivers except for the nvidia one, and have made some progress. The kernel now finds the drive, but for some reason puts a little 8MB drive at sda, and populates the 'real' 250MB drive at sdb, so the kernel still panics (probably due to fstab wanting to see the main drive at sda, not sdb). I'd like to get a log of this, but dmesg only shows the log of the kernel that boots. Does anyone have any suggestions of how to get at the log for a panicking kernel, or have any suggestions on how to fix this. I suspect the I may be able to play with fstab and get the new kernel to boot, but I'm loath to do this, as that will most likely break the kernel that is working, so if it doesn't simultaneously fix the non-working kernel, I'm toast. Any suggestions gratefully received. --- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Kernel 2.6.22-r9 installation problems
On Monday 19 November 2007 11:46:39 pm Billy Holmes wrote: Jeff Cranmer wrote: The kernel now finds the drive, but for some reason puts a little 8MB drive at sda, and populates the 'real' 250MB drive at sdb, so the kernel still panics (probably due to fstab wanting to see the main drive at sda, not sdb). that's very odd that there is a sda drive. Perhaps sda is a pen drive that you have installed? a USB drive? you can always change your boot options in grub. at the grub prompt, hit [e]dit, select the line which has the kernel line, move the cursor to the end, and change root=/dev/sda1 to /dev/sdb1 hit [b]oot sit back and smile. I already tried that - sit back and sulk, I'm afraid :-( Because fstab still points to /dev/sda, it fails when it tries to map the drives. I could play with fstab, but I'm not ready to break my working OS yet. There are no usb drives connected to the system. In fact, the only USB device attached is the HP PSC750xi printer. When it fails after re-pointing the grub booter to /dev/sdb, it does at least fail so that I can get to a shell as root. dmesg doesn't work from the shell, however. I wonder if there is a command I can use to query the new sda and find out where it is getting it from? Jeff --- -- [EMAIL PROTECTED] mailing list
[gentoo-user] Kernel 2.6.22-r9 installation problems
I have just tried to install the latest 2.6.22-r9 kernel I copied the config file across from the present 2.6.17.r8 installed kernel, then recompiled. The grub line which works for the 2.6.17-r8 kernel is: # For booting GNU/Linux title Gentoo Linux 2.6.17-r8 root (hd0,4) kernel /kernel-2.6.17-gentoo-r8 root=/dev/sda3 #initrd /initrd.img I created the following grub line for the new kernel # For booting GNU/Linux title Gentoo Linux 2.6.22-r9 root (hd0,4) kernel /kernel-2.6.22-gentoo-r9 root=/dev/sda3 #initrd /initrd.img The fstab is as follows # fs mountpointtype optsdump/pass /dev/sda5 /bootext3 noauto,noatime 1 2 /dev/sda3 / ext3noatime 0 1 /dev/sda2 none swap sw 0 0 /dev/dvdrw /mnt/dvdrw iso9660 noauto,user 0 0 #/dev/fd0 /mnt/floppy auto noauto 0 0 /dev/sda7 /mnt/data ext3 noatime 0 1 /dev/hde1 /mnt/backup ext3 noatime 0 1 proc/proc procdefaults 0 0 shm /dev/shmtmpfs nodev,nosuid,noexec 0 0 In other words, the boot directory is at sda5, and the root directory is at sda3. sda3 is the bootable partition. When I try to access the new kernel, I get the following error text (summarised) Cannot open root device sda3 or unknown block (0,0) Please append a correct root= boot option. Here are the available partitions hde driver: ide-disk hde1 hdf driver: ide-disk hdf1 hda driver: ide-cdrom kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0) Can anyone point me in the direction of why the new kernel will not boot, while the old one boots fine? Thanks Jeff -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Kernel 2.6.22-r9 installation problems
On Sunday 18 November 2007 03:42:53 pm b.n. wrote: Jeff Cranmer ha scritto: I have just tried to install the latest 2.6.22-r9 kernel I copied the config file across from the present 2.6.17.r8 installed kernel, then recompiled. [...] Can anyone point me in the direction of why the new kernel will not boot, while the old one boots fine? Didn't you run make oldconfig ? I don't know how safe it is to copy and use a .config directly between different major revisions of the kernel. m. I did not. What is the procedure for doing this, and what exactly does it accomplish? Thanks Jeff -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: Kernel 2.6.22-r9 installation problems
Well, I tried this, and didn't see any additional options which would explain the error. After copying the newly compiled kernel into the boot directory and re-running grub-install, I still get the same kernel panic error. I wonder what else could be going on which could explain this? Jeff On Sunday 18 November 2007 05:00:12 pm »Q« wrote: Jeff Cranmer [EMAIL PROTECTED] wrote: On Sunday 18 November 2007 03:42:53 pm b.n. wrote: Jeff Cranmer ha scritto: I have just tried to install the latest 2.6.22-r9 kernel I copied the config file across from the present 2.6.17.r8 installed kernel, then recompiled. [...] Can anyone point me in the direction of why the new kernel will not boot, while the old one boots fine? Didn't you run make oldconfig ? I don't know how safe it is to copy and use a .config directly between different major revisions of the kernel. I did not. What is the procedure for doing this, and what exactly does it accomplish? Copy the old .config file to /usr/src/[new kernel directory], and run 'make oldconfig' in that directory. It picks out the changes and prompts you to decide what to do about them. After that, IMO it's a good idea to use 'make menuconfig' or 'make xconfig' to make sure the new config makes sense before compiling the new kernel; this is especially important if any of the questions asked by oldconfig didn't quite make sense to you. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] portage update problems due to sane-backends
Progress kind of :-/ I set SANE_BACKENDS to hp, and was able to compile the sane-backends package. Two files were changed and flagged via etc-update. The first was /etc/sane.d/dll.conf, which added a bunch of scanners and commented out hpoj. Since hpoj is part of the hplip package, and I have this package installed, I deleted the comment character to enable this dll The second file was /etc/hotplug/usb/libsane.usermap The PSC 750 usb entry was deleted, so I added this back in # Hewlett-Packard PSC-750 libusbscanner 0x0003 0x03f0 0x1411 0x 0x 0x00 0x00 0x00 0x00 0x00 0x00 0x Unfortunately, sane can no longer find my scanner, even after restarting hotplug. Any assistance gratefully received. Thanks Jeff On Friday 16 November 2007 08:33:14 am Jeff Cranmer wrote: The scanner is an HP PSC-750xi SANE_BACKENDS is set to hpaio in make.conf. What should it be set to? Jeff On Friday 16 November 2007 04:44:54 am Neil Bothwick wrote: On Thu, 15 Nov 2007 19:36:46 -0500, Jeff Cranmer wrote: I do not seem to be able to update a lot of my system, because sane-backends fails to compile. That only stops you updating sane-backends, not the rest of the system. You can skip this and continue a world update with emerge --resume --skipfirst. This is the error I get make[1]: Entering directory `/var/tmp/portage/media-gfx/sane-backends-1.0.18-r4/work/sane-backend s- 1. 0.18/backend' make[1]: *** No rule to make target `libsane-hpaio.la', needed by `all'. Which scanner do you have? What is SANE_BACKENDS set to in /etc/make.conf? -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] portage update problems due to sane-backends
The scanner is an HP PSC-750xi SANE_BACKENDS is set to hpaio in make.conf. What should it be set to? Jeff On Friday 16 November 2007 04:44:54 am Neil Bothwick wrote: On Thu, 15 Nov 2007 19:36:46 -0500, Jeff Cranmer wrote: I do not seem to be able to update a lot of my system, because sane-backends fails to compile. That only stops you updating sane-backends, not the rest of the system. You can skip this and continue a world update with emerge --resume --skipfirst. This is the error I get make[1]: Entering directory `/var/tmp/portage/media-gfx/sane-backends-1.0.18-r4/work/sane-backends- 1. 0.18/backend' make[1]: *** No rule to make target `libsane-hpaio.la', needed by `all'. Which scanner do you have? What is SANE_BACKENDS set to in /etc/make.conf? -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] portage update problems due to sane-backends
Success. I updated hplip, which replaced the /etc/sane.d/dll/conf hpoj line with hpaio. Now all is working once more :-) Thanks for pointing me in the right direction, Neil Jeff On Friday 16 November 2007 09:00:06 am Jeff Cranmer wrote: Progress kind of :-/ I set SANE_BACKENDS to hp, and was able to compile the sane-backends package. Two files were changed and flagged via etc-update. The first was /etc/sane.d/dll.conf, which added a bunch of scanners and commented out hpoj. Since hpoj is part of the hplip package, and I have this package installed, I deleted the comment character to enable this dll The second file was /etc/hotplug/usb/libsane.usermap The PSC 750 usb entry was deleted, so I added this back in # Hewlett-Packard PSC-750 libusbscanner 0x0003 0x03f0 0x1411 0x 0x 0x00 0x00 0x00 0x00 0x00 0x00 0x Unfortunately, sane can no longer find my scanner, even after restarting hotplug. Any assistance gratefully received. Thanks Jeff On Friday 16 November 2007 08:33:14 am Jeff Cranmer wrote: The scanner is an HP PSC-750xi SANE_BACKENDS is set to hpaio in make.conf. What should it be set to? Jeff On Friday 16 November 2007 04:44:54 am Neil Bothwick wrote: On Thu, 15 Nov 2007 19:36:46 -0500, Jeff Cranmer wrote: I do not seem to be able to update a lot of my system, because sane-backends fails to compile. That only stops you updating sane-backends, not the rest of the system. You can skip this and continue a world update with emerge --resume --skipfirst. This is the error I get make[1]: Entering directory `/var/tmp/portage/media-gfx/sane-backends-1.0.18-r4/work/sane-backe nd s- 1. 0.18/backend' make[1]: *** No rule to make target `libsane-hpaio.la', needed by `all'. Which scanner do you have? What is SANE_BACKENDS set to in /etc/make.conf? -- [EMAIL PROTECTED] mailing list
[gentoo-user] portage update problems due to sane-backends
Can anyone help me with an update issue? I do not seem to be able to update a lot of my system, because sane-backends fails to compile. This is the error I get make[1]: Entering directory `/var/tmp/portage/media-gfx/sane-backends-1.0.18-r4/work/sane-backends-1.0.18/backend' make[1]: *** No rule to make target `libsane-hpaio.la', needed by `all'. Stop. make[1]: Leaving directory `/var/tmp/portage/media-gfx/sane-backends-1.0.18-r4/work/sane-backends-1.0.18/backend' make: *** [all-recursive] Error 1 * * ERROR: media-gfx/sane-backends-1.0.18-r4 failed. * Call stack: *ebuild.sh, line 1701: Called dyn_compile *ebuild.sh, line 1039: Called qa_call 'src_compile' *ebuild.sh, line 44: Called src_compile * sane-backends-1.0.18-r4.ebuild, line 109: Called die * The specific snippet of code: * emake || die * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-gfx/sane-backends-1.0.18-r4/temp/build.log'. * * Messages for package media-gfx/sane-backends-1.0.18-r4: * * ERROR: media-gfx/sane-backends-1.0.18-r4 failed. * Call stack: *ebuild.sh, line 1701: Called dyn_compile *ebuild.sh, line 1039: Called qa_call 'src_compile' *ebuild.sh, line 44: Called src_compile * sane-backends-1.0.18-r4.ebuild, line 109: Called die * The specific snippet of code: * emake || die * The die message: * (no error message) * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-gfx/sane-backends-1.0.18-r4/temp/build.log'. Can anyone suggest a workaround? Thanks Jeff -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Networking problems
After reading the comments at the top of the /etc/conf.d/net, a blank file will automatically use DHCP for any net.* scripts in /etc/init.d, so I commented out all the parameters that I'd added. The file then matches the one in the livecd boot-up that I used to install the OS. For the /etc/resolv.conf file, I have: search belkin nameserver 192.168.2.1 nameserver 207.69.188.185 nameserver 207.69.188.186 nameserver 207.69.188.187 route -n returns Kernel IP routing table Destination Gateway Genmask FlagsMetricRef Use Iface 192.168.2.0 0.0.0.0255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0255.0.0.0U 0 00 lo 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0 Comparing this with the equivalent working connection via my Mandriva Linux boot-up, /etc/resolv.conf is the same, but route -n returns Kernel IP routing table Destination Gateway Genmask FlagsMetricRef Use Iface 192.168.2.0 0.0.0.0255.255.255.0 U 10 0 0 eth0 169.254.0.0 0.0.0.0 255.0.0.0U 10 0 0 eth0 127.0.0.0 0.0.0.0255.0.0.0U 0 00 lo 0.0.0.0 192.168.2.1 0.0.0.0 UG 10 0 0 eth0 The main difference is that the metric column is all 0 on my non-working install, and I'm missing the 169.254.0.0 row from route -n I'm not using genkernel. Is it possible that a kernel misconfiguration is responsible for the problems I'm having? Thanks Jeff -Original Message- From: Novensiles divi Flamen [EMAIL PROTECTED] Sent: Nov 3, 2006 10:15 PM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Networking problems On Saturday 04 November 2006 09:57, Jeff Cranmer wrote: I seem to have some network issues with my gentoo install I have /etc/init.0/net.eth0 configured to run at the default runlevel. It appears to startup ok. No firewall has been installed yet. The network appears to startup eth0 correctly, obtaining a dhcp address from my cable provider via the router. Are you getting DNS and default route settings from the DHCP server? Your option 'nodns' means you'd need to have it set manually. cat /etc/resolv.conf should show the value of your DNS server. route -n should show your default gateway. Check that both values are sane. - Noven -- -- Novensiles divi Flamen -- Miles Militis Fons -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Networking problems
Perhaps removing all the lines from the net configuration script was the key after all. It didn't work on the next boot-up cycle, but on the one following that, without performing any extra configuration steps, the network connection was operational :-/ I have a network. Now I can proceed with installing kde :-) The results of ifconfig and route -n are unchanged. Jeff -Original Message- From: Mick [EMAIL PROTECTED] Sent: Nov 4, 2006 8:29 AM To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Networking problems On Saturday 04 November 2006 12:24, Jeff Cranmer wrote: Comparing this with the equivalent working connection via my Mandriva Linux boot-up, /etc/resolv.conf is the same, but route -n returns Kernel IP routing table Destination Gateway Genmask FlagsMetricRef Use Iface 192.168.2.0 0.0.0.0255.255.255.0 U 10 00 eth0 169.254.0.0 0.0.0.0 255.0.0.0U 10 00 eth0 127.0.0.0 0.0.0.0255.0.0.0U 0 00 lo 0.0.0.0 192.168.2.1 0.0.0.0 UG 10 00 eth0 Have you tried only entering config_eth0=( dhcp ) in your /etc/conf.d/net and leaving all the routing and dns setting to dhcpcd to sort out? Have you a complicating LAN arrangement that requires the nodns option? -- Regards, Mick -- gentoo-user@gentoo.org mailing list
