Creative Labs X-Fi Xtreme Audio Support
Is this card supported by ALSA yet in F9? /sbin/lspci -v ... 03:00.0 Audio device: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG Subsystem: Creative Labs Unknown device 0018 ... My onboard soundcard recently stopped working and all I get is hissing from it. So I just purchased this card and stupidly forgot to check for Linux support. AFAICT it's a fairly new card and the driver is/was in beta. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Minor GNOME and KDE menu annoyance
While I think of it, it's a minor annoyance, but when I install KDE and am already using GNOME, all of the KDE menu entries are all mixed in together with GNOMES. This has irked me since a few Fedora releases ago. I like to keep them separate and like to have both desktops installed. Is there a way to accomplish this? Correct me if I'm wrong, but I'm sure this wasn't always the case? p.s. Kind of another question and probably deserves another post, but being green and cutting down on list traffic, here goes ... What is the idea of or notion behind firstboot? why can't the questions it asks be done in the installer like it used to be like as was Red Hat 7.3 - just wondering. Thanks. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: FC9: can't find iostat command
Laszlo BERES wrote: [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] rpm -qa | grep sysstat [EMAIL PROTECTED] The above should only work when the sysstat package is installed. [EMAIL PROTECTED] ~]# yum whatprovides "*/iostat" Loaded plugins: fastestmirror, refresh-packagekit Loading mirror speeds from cached hostfile * livna: ftp-stud.fht-esslingen.de * fedora: mirror.karneval.cz * updates: mirror.karneval.cz * spacewalk: spacewalk.redhat.com filelists.sqlite.bz2 | 331 kB 00:00 sysstat-8.0.4-3.fc9.i386 : The sar and iostat system monitoring commands Matched from: Filename: /usr/bin/iostat munin-node-1.2.5-4.fc9.noarch : Network-wide graphing framework (node) Matched from: Filename: /usr/share/munin/plugins/iostat sysstat-8.0.4-4.fc9.i386 : The sar and iostat system monitoring commands Matched from: Filename: /usr/bin/iostat munin-node-1.2.5-5.fc9.noarch : Network-wide graphing framework (node) Matched from: Filename: /usr/share/munin/plugins/iostat I am intregued by the "*/" in your yum command. Is that to make yum match the filename on it's absolute path? The reason I ask this is many times I would like to install a certain program, but can't remember what package provides it. So I run: # yum whatprovides (e.g. sar) And more often or not it never matches any package, even though I know damn well it's in the repo somewhere. I usually google to find out the answer in the end. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: FC9: can't find iostat command
Todd Zullinger wrote: Stewart Williams wrote: I am intregued by the "*/" in your yum command. Is that to make yum match the filename on it's absolute path? Indeed. If yum see the / in the patter, it will consult the file list metadata. Normally, yum tries to avoid using the file list metadata because it is quite large compared to the other metadata. Looks like it's definitely useful to know and I should now get the results I require. Unless I'm mistaken, I don't think I've ever seen this in yum's manpage before. If not then why isn't it in a relevent(tips?) section? Even though the yum manpages are good, I can't help but think manpages as a whole on Linux are not as informative as they used to be; especially newer commands and not to mention missing ones ... but that's for a different thread :-# -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
yum search behaviour
Is there an command-line option for recent yum releases so that it displays package descriptions in a 'yum search'? I do prefer the one line results, but occasionally I'd like to do a search the old way too :-) Or is 'yum info' the only way to go? -- Regards, Stewart Williams -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Installing packages from Fedora repo - is it safe?
I think I know the answer to this, but I'm just clarifying. I have updated to the updates-newkey repo for updates, but there are packages that I want to install, and these are still pulled from the fedora (Everything) repo. Is it safe to use the repo yet or are all the packages in the process of being re-signed? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Upgrade Has Caused A Downgrade
Gene Poole wrote: All, I've just experienced one of the most unnerving situations. I've a custom built machine that WAS running the following: ECS GeForce 6100SM-M mother board AMD 64 X2 Dual core 5600+ 4GB RAM DDR2 800 Mhz nVidia GT7300 PCIE 256MB video card 2 - SATA Hard drives; 1 - 320 GB WD and 1 - 500GB Seagate 550 watt Antec power supply Fedora 9 x86_64 with all of the latest patches As my Xmas present I upgraded the machine to: Gigabyte MA790X-DS4 mother board AMD Phenom Quad core 9550 8GB RAM DDR2 800 Mhz Retained the video card from above 2 - SATA Hard drives; 1 - 500 GB Seagate and 1 - 1TB Seagate 850 watt Antec power supply I attempted to install, from the same DVD used on the original machine, Fedora 9 x86_64 with 4 failures at just about the same place while installing packages. I used my i386 Fedora 9 DVD and all went well during the install so attempted to do a upgrade to x86_64 without luck. I did a test using my Fedora 8 x86_64 DVD and it installed perfectly. I then attempted to do a upgrade to Fedora 9 without any luck (it appeared to fail at about the same place). I then downloaded and burned another copy of the Fedora 9 x86_64 DVD, checked it and attempted to do another install and one again it failed at about the same place. What could possibly be happening? I since reinstalled Fedora 8, but that has reached it's E-O-L. Should I just attempt to go to Fedora 10 x86_64? Should I have entered something in the boot parameters concerning the additional memory? Any help or advice would be great! Thanks, Gene Poole Maybe try a re-spin ISO with updated packages, in case the problem has been fixed or is non-existant with a newer install? http://spins.fedoraunity.org/ Got to be worth a try! -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Creating a Windws XP virtual machine Fedora 11
James Harrison wrote:
> Hi
> I am trying to create a virtual machine and install Windows XP. I am
> using Fedora 11.The system was last fully patched about an hour ago.
>
> selinux is disabled.
>
> r...@pc32 ~]# uname -a
> Linux x.com 2.6.29.6-217.2.16.fc11.i686.PAE #1 SMP Mon Aug 24 17:16:21
> EDT 2009 i686 i686 i386 GNU/Linux
>
> When booting the virtual machine for the first time, the VM hangs with:
> "Booting from hard disk". Nothing else appears.
>
> When I shutdown the VM /var/log/messages has:
> Sep 2 03:42:44 pc32 libvirtd: 03:42:44.714: error : operation failed:
> could not query memory balloon allocation
>
> ... and a dialogue box appears with the same message: here is the trace:
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/engine.py", line 507, in
> shutdown_domain vm.shutdown()
> File "/usr/share/virt-manager/virtManager/domain.py", line 566, in
> shutdown self._update_status()
> File "/usr/share/virt-manager/virtManager/domain.py", line 217, in
> _update_status info = self.vm.info()
> File "/usr/lib/python2.6/site-packages/libvirt.py", line 523, in info
> if ret is None: raise libvirtError ('virDomainGetInfo() failed',
> dom=self)
> libvirtError: operation failed: could not query memory balloon allocation
>
> Thanks,
> James Harrison
>
Could be related to this bug?:
https://bugzilla.redhat.com/show_bug.cgi?id=500968
--
Regards,
Stewart Williams
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Desktop notifications
Hi all, I don't really want to have a moan, I was just wondering "why?" and to get everyone's views. I remember way back when Linux on the desktop was beginning to progress faster and people were discussing how to notify the user of certain system events. Reading various Internet blog posts, articles, websites, etc. at the time people always bitched about how they found Windows' desktop pop-ups/notifications in the system tray annoying while they were working. How come then, has Gnome and KDE both adopted similar notification methods which in my opinion are much bigger and a lot more annoying than any Windows notifications have ever been? The Gnome pop-ups are clean and concise, which I like, but they are way to big and take up too much space, thus blocking what I am doing. In KDE (Fedora 10 + 11), the pop-ups for things such as KpackageKit stack all the way vertically up my screen and are un-tidy, un-polished and un-clear (I can post a screen shot if requested) Don't get me wrong, I love Fedora, used it since FC1, but I cannot understand why the developers have done similar things like this to "other OS's" and IMO made them worse. If I can help with usability in any way, I would be glad to so. I have seen many mockup's before that are much better than the current systems. IIRC Jakub Steiner a.k.a Jimmac has done some very good designs[1]. Sorry for the noise - Just want to make a better desktop(tm) :-) [1] http://jimmac.musichall.cz/guimockups.php?mockup=notifications -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
External hard disk or USB errors
I have an external USB Maxtor OneTouch 160GB hard disk attached to one of my systems and occasionally after the drive has been connected for sometime, randomly it un-mounts and I have to turn it off and on again before I can re-mount it. The following errors are logged (please see attached file for full log): ... Nov 4 17:10:21 server1 kernel: usb 5-7: USB disconnect, address 68 Nov 4 17:10:21 server1 kernel: Buffer I/O error on device sda5, logical block 731 Nov 4 17:10:21 server1 kernel: lost page write due to I/O error on sda5 Nov 4 17:10:21 server1 kernel: Aborting journal on device sda5. Nov 4 17:10:21 server1 kernel: journal commit I/O error Nov 4 17:10:21 server1 kernel: Buffer I/O error on device sda5, logical block 11 Nov 4 17:10:21 server1 kernel: lost page write due to I/O error on sda5 Nov 4 17:10:21 server1 kernel: usb 5-7: new high speed USB device using ehci_hcd and address 69 Nov 4 17:10:21 server1 kernel: usb 5-7: configuration #1 chosen from 1 choice Nov 4 17:10:21 server1 kernel: scsi190 : SCSI emulation for USB Mass Storage devices Nov 4 17:10:21 server1 kernel: usb-storage: device found at 69 Nov 4 17:10:21 server1 kernel: usb-storage: waiting for device to settle before scanning ... Can anyone shine any light on wether it's a power, USB, hard disk (failure pending?) or some other problem. It only does now and again; but it is of concern. Many Thanks. Nov 4 08:53:53 server1 kernel: usb 5-7: USB disconnect, address 67 Nov 4 08:54:08 server1 kernel: usb 5-7: new high speed USB device using ehci_hcd and address 68 Nov 4 08:54:08 server1 kernel: usb 5-7: configuration #1 chosen from 1 choice Nov 4 08:54:08 server1 kernel: scsi189 : SCSI emulation for USB Mass Storage devices Nov 4 08:54:08 server1 kernel: usb-storage: device found at 68 Nov 4 08:54:08 server1 kernel: usb-storage: waiting for device to settle before scanning Nov 4 08:54:13 server1 kernel: scsi 189:0:0:0: Direct-Access Maxtor OneTouch 0201 PQ: 0 ANSI: 0 CCS Nov 4 08:54:13 server1 kernel: sd 189:0:0:0: [sda] 240119808 512-byte hardware sectors (122941 MB) Nov 4 08:54:13 server1 kernel: sd 189:0:0:0: [sda] Write Protect is off Nov 4 08:54:13 server1 kernel: sd 189:0:0:0: [sda] Mode Sense: 1c 00 00 00 Nov 4 08:54:13 server1 kernel: sd 189:0:0:0: [sda] Assuming drive cache: write through Nov 4 08:54:13 server1 kernel: sd 189:0:0:0: [sda] 240119808 512-byte hardware sectors (122941 MB) Nov 4 08:54:14 server1 kernel: sd 189:0:0:0: [sda] Write Protect is off Nov 4 08:54:14 server1 kernel: sd 189:0:0:0: [sda] Mode Sense: 1c 00 00 00 Nov 4 08:54:14 server1 kernel: sd 189:0:0:0: [sda] Assuming drive cache: write through Nov 4 08:54:14 server1 kernel: sda: sda1 < sda5 > Nov 4 08:54:14 server1 kernel: sd 189:0:0:0: [sda] Attached SCSI disk Nov 4 08:54:14 server1 kernel: usb-storage: device scan complete Nov 4 09:00:08 server1 kernel: kjournald starting. Commit interval 5 seconds Nov 4 09:00:08 server1 kernel: EXT3-fs warning: maximal mount count reached, running e2fsck is recommended Nov 4 09:00:08 server1 kernel: EXT3 FS on sda5, internal journal Nov 4 09:00:08 server1 kernel: EXT3-fs: mounted filesystem with ordered data mode. Nov 4 17:10:21 server1 kernel: usb 5-7: USB disconnect, address 68 Nov 4 17:10:21 server1 kernel: Buffer I/O error on device sda5, logical block 731 Nov 4 17:10:21 server1 kernel: lost page write due to I/O error on sda5 Nov 4 17:10:21 server1 kernel: Aborting journal on device sda5. Nov 4 17:10:21 server1 kernel: journal commit I/O error Nov 4 17:10:21 server1 kernel: Buffer I/O error on device sda5, logical block 11 Nov 4 17:10:21 server1 kernel: lost page write due to I/O error on sda5 Nov 4 17:10:21 server1 kernel: usb 5-7: new high speed USB device using ehci_hcd and address 69 Nov 4 17:10:21 server1 kernel: usb 5-7: configuration #1 chosen from 1 choice Nov 4 17:10:21 server1 kernel: scsi190 : SCSI emulation for USB Mass Storage devices Nov 4 17:10:21 server1 kernel: usb-storage: device found at 69 Nov 4 17:10:21 server1 kernel: usb-storage: waiting for device to settle before scanning Nov 4 17:10:26 server1 kernel: scsi 190:0:0:0: Direct-Access Maxtor OneTouch 0201 PQ: 0 ANSI: 0 CCS Nov 4 17:10:26 server1 kernel: sd 190:0:0:0: [sdb] 240119808 512-byte hardware sectors (122941 MB) Nov 4 17:10:27 server1 kernel: sd 190:0:0:0: [sdb] Write Protect is off Nov 4 17:10:27 server1 kernel: sd 190:0:0:0: [sdb] Mode Sense: 1c 00 00 00 Nov 4 17:10:27 server1 kernel: sd 190:0:0:0: [sdb] Assuming drive cache: write through Nov 4 17:10:27 server1 kernel: sd 190:0:0:0: [sdb] 240119808 512-byte hardware sectors (122941 MB) Nov 4 17:10:27 server1 kernel: sd 190:0:0:0: [sdb] Write Protect is off Nov 4 17:10:27 server1 kernel: sd 190:0:0:0: [sdb] Mode Sense: 1c 00 00 00 Nov 4 17:10:27 server1 kernel: sd 190:0:0:0: [sdb] Assuming drive cache: write through Nov 4 17:10:32 server1 kernel: sdb: sdb1 < sdb5 > Nov 4 17:10:32 server
Re: External hard disk or USB errors
On Sun, 2008-11-16 at 15:29 +1000, Da Rock wrote: > What do you turn off and on exactly? The computer or the hard drive? The external hard disk. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Unable to boot Live Fedora on a USB flash drive
I am trying to create a LiveUSB drive using a 2GB USB flash drive, but I'm being unsuccessful for some reason. Ideally I was hoping to create one based on Omega-10, but I get the same problems with Fedora. Here's what I have tried: 1. Creating a LiveCD from omega-10-desktop.iso and boot it (which works fine). Plug in USB stick, fdisk it as one partition, type 6 (fat 16) then format it by running 'mkfs.msdos -F 16 -n usbdisk /dev/sdg1' As root running 'livecd-iso-to-disk /dev/live /dev/sdg1' Seems to complete without error 2. Boot Fedora 9 install on my desktop and prepare the USB stick as above Run liveusb-creator GUI and select /dev/sdg1 as target, and omega-10-desktop.iso as source (Also tried F10-Live-i686.iso as source) Completes without error However when I try and boot of the stick either by physically booting using the BIOS or testing with QEMU I get the following errors: Running 'qemu -hda /dev/sdg -m 256 -std-vga' or booting using a physical PC I get a garbled prompt http://www.freeimagehosting.net/image.php?07644a5805.png Running 'qemu -hda /dev/sdg1 -m 256 -std-vga' I get an error stating that it can find the root filesystem http://www.freeimagehosting.net/image.php?159f02408f.png Does anyone know what I may be doing wrong? Many Thanks. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unable to boot Live Fedora on a USB flash drive
Richard Shaw wrote: > On Sun, Mar 15, 2009 at 6:15 PM, Stewart Williams > wrote: >> I am trying to create a LiveUSB drive using a 2GB USB flash drive, but >> I'm being unsuccessful for some reason. >> >> Ideally I was hoping to create one based on Omega-10, but I get the same >> problems with Fedora. >> >> Here's what I have tried: >> >> 1. Creating a LiveCD from omega-10-desktop.iso and boot it (which works >> fine). >> Plug in USB stick, fdisk it as one partition, type 6 (fat 16) then >> format it by running 'mkfs.msdos -F 16 -n usbdisk /dev/sdg1' >> As root running 'livecd-iso-to-disk /dev/live /dev/sdg1' >> Seems to complete without error >> >> 2. Boot Fedora 9 install on my desktop and prepare the USB stick as above >> Run liveusb-creator GUI and select /dev/sdg1 as target, and >> omega-10-desktop.iso as source (Also tried F10-Live-i686.iso as source) >> Completes without error >> >> However when I try and boot of the stick either by physically booting >> using the BIOS or testing with QEMU I get the following errors: >> >> Running 'qemu -hda /dev/sdg -m 256 -std-vga' or booting using a physical >> PC I get a garbled prompt >> >> http://www.freeimagehosting.net/image.php?07644a5805.png >> >> Running 'qemu -hda /dev/sdg1 -m 256 -std-vga' I get an error stating >> that it can find the root filesystem >> >> http://www.freeimagehosting.net/image.php?159f02408f.png >> >> Does anyone know what I may be doing wrong? >> >> Many Thanks. > > It looks like in the first case it doesn't like the MBR. I get > something similar when I leave my iPod connected to my work laptop on > reboot. One thing, not all usb sticks like all BIOS's. It could be the > stick, it could be your BIOS, no good way to tell that I know of. > > Richard > Hi Richard I don't think it's a BIOS issue, as I've tried to boot from it on 2 different desktops, an eee-pc and qemu. But it could be the stick. I will try another and report back. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unable to boot Live Fedora on a USB flash drive
Mike Cloaked wrote: > > > Stewart Williams wrote: >> I am trying to create a LiveUSB drive using a 2GB USB flash drive, but >> I'm being unsuccessful for some reason. >> >> Seems to complete without error >> >> 2. Boot Fedora 9 install on my desktop and prepare the USB stick as above >> Run liveusb-creator GUI and select /dev/sdg1 as target, and >> omega-10-desktop.iso as source (Also tried F10-Live-i686.iso as source) >> Completes without error >> >> Does anyone know what I may be doing wrong? >> >> > > One thing worth checking - make sure that your stick is un-mounted at the > time you write the liveusb files to it. I have been bitten by that in the > past - there is no error message but the files don't get written to the > stick unless it is umounted. > > I use the method at http://fedoraproject.org/wiki/FedoraLiveCD/USBHowTo > That's the guide I've been following too. And I have made sure it was unmounted before I wrote the image. IIRC it don't let you proceed if the drive is mounted anyway. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Unable to boot Live Fedora on a USB flash drive
Stewart Williams wrote: > I am trying to create a LiveUSB drive using a 2GB USB flash drive, but > I'm being unsuccessful for some reason. > > Ideally I was hoping to create one based on Omega-10, but I get the same > problems with Fedora. > > Here's what I have tried: > > 1. Creating a LiveCD from omega-10-desktop.iso and boot it (which works > fine). > Plug in USB stick, fdisk it as one partition, type 6 (fat 16) then > format it by running 'mkfs.msdos -F 16 -n usbdisk /dev/sdg1' > As root running 'livecd-iso-to-disk /dev/live /dev/sdg1' > Seems to complete without error > > 2. Boot Fedora 9 install on my desktop and prepare the USB stick as above > Run liveusb-creator GUI and select /dev/sdg1 as target, and > omega-10-desktop.iso as source (Also tried F10-Live-i686.iso as source) > Completes without error > > However when I try and boot of the stick either by physically booting > using the BIOS or testing with QEMU I get the following errors: > > Running 'qemu -hda /dev/sdg -m 256 -std-vga' or booting using a physical > PC I get a garbled prompt > > http://www.freeimagehosting.net/image.php?07644a5805.png > > Running 'qemu -hda /dev/sdg1 -m 256 -std-vga' I get an error stating > that it can find the root filesystem > > http://www.freeimagehosting.net/image.php?159f02408f.png > > Does anyone know what I may be doing wrong? > > Many Thanks. > > Solved! Even though I got no errors, I tried this command from the LiveUSB howto: $ cat /usr/lib/syslinux/mbr.bin > /dev/sdg http://fedoraproject.org/wiki/FedoraLiveCD/USBHowTo#SYSLINUX_Boot_Error.21 I still got the error about the root fs not being found, so I used liveusb-creator to transfer the image again and to my amazement it worked! It boots and loads the desktop as expected. Yay! -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
OT: Internet access for old RH machine
I know, I know, but ... I have an old laptop (PII-400MHz) that has RedHat 7.3 installed on it and it works like a dream and it's all setup how I want it. Currently I use it stand-alone and has no LAN or Internet access configured. However occasionally I would really like to access certain web sites on it - so I need to use a web browser, text or GUI. I know it's no longer updated, supported and probably full of security holes, however ... I was wondering if there was a way I could connect it to my router, but segregated some how, such as an encrypted VPN tunnel. So that if it was exploited it couldn't compromise the security of my main LAN. I have plenty of spare hardware lying around, such as 802.11b cards, routers, etc. I'm no expert on (sub?)networks, DMZ's, etc. and was wondering if anyone has any thoughts on if this is pheasable. Thanks. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Gnome open/save dialog preferences
Is it possible to configure the Gnome open/save dialog box layout so that it has the 3 big buttons like in old releases (see random google screenshot) http://www.flexbeta.net/images/suse9.1/suse_gnome24.jpg I am using Fedora 9 and 10. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Display actual speed of ethernet connection
Dave Feustel wrote: > On Sun, Apr 19, 2009 at 05:39:21PM +0200, fedora wrote: >> Hi Dave >> >> /sbin/mii-tool >> eth0: negotiated 100baseTx-FD, link ok > > Thanks for the reference. > Man mii-tool says this utility does not cover 1G nics and is obsolete. > It recommends ethtool instead. '/sbin/ethtool eth0' says that the ic is > running at 100mb/s although it has 1G/s capability. So I am curious why > the nic does not initialize to 1G or light up the port led on the 1G > switch. > >> >> rpm -ql net-tools >> /bin/dnsdomainname > /bin/domainname >> /bin/hostname >> /bin/netstat >> /bin/nisdomainname >> /bin/ypdomainname >> /etc/ethers >> /etc/netplug >> /etc/netplug.d >> /etc/netplug.d/netplug >> /etc/netplug/netplugd.conf >> /etc/rc.d/init.d/netplugd >> /sbin/arp >> /sbin/ether-wake >> /sbin/ifconfig >> /sbin/ipmaddr >> /sbin/iptunnel >> /sbin/mii-diag >> /sbin/mii-tool >> /sbin/nameif >> /sbin/netplugd >> /sbin/plipconfig >> /sbin/route >> /sbin/slattach >> /usr/share/doc/net-tools-1.60 >> /usr/share/doc/net-tools-1.60/COPYING >> /usr/share/doc/net-tools-1.60/README.netplugd >> /usr/share/doc/net-tools-1.60/TODO.netplugd >> /usr/share/locale/cs/LC_MESSAGES/net-tools.mo >> /usr/share/locale/de/LC_MESSAGES/net-tools.mo >> /usr/share/locale/et_EE/LC_MESSAGES/net-tools.mo >> /usr/share/locale/fr/LC_MESSAGES/net-tools.mo >> /usr/share/locale/pt_BR/LC_MESSAGES/net-tools.mo >> /usr/share/man/de/man1/dnsdomainname.1.gz >> /usr/share/man/de/man1/domainname.1.gz >> /usr/share/man/de/man1/hostname.1.gz >> /usr/share/man/de/man1/nisdomainname.1.gz >> /usr/share/man/de/man1/ypdomainname.1.gz >> /usr/share/man/de/man5/ethers.5.gz >> /usr/share/man/de/man8/arp.8.gz >> /usr/share/man/de/man8/ifconfig.8.gz >> /usr/share/man/de/man8/netstat.8.gz >> /usr/share/man/de/man8/plipconfig.8.gz >> /usr/share/man/de/man8/route.8.gz >> /usr/share/man/de/man8/slattach.8.gz >> /usr/share/man/fr/man1/dnsdomainname.1.gz >> /usr/share/man/fr/man1/domainname.1.gz >> /usr/share/man/fr/man1/hostname.1.gz >> /usr/share/man/fr/man1/nisdomainname.1.gz >> /usr/share/man/fr/man1/ypdomainname.1.gz >> /usr/share/man/fr/man5/ethers.5.gz >> /usr/share/man/fr/man8/arp.8.gz >> /usr/share/man/fr/man8/ifconfig.8.gz >> /usr/share/man/fr/man8/netstat.8.gz >> /usr/share/man/fr/man8/plipconfig.8.gz >> /usr/share/man/fr/man8/route.8.gz >> /usr/share/man/fr/man8/slattach.8.gz >> /usr/share/man/man1/dnsdomainname.1.gz >> /usr/share/man/man1/domainname.1.gz >> /usr/share/man/man1/hostname.1.gz >> /usr/share/man/man1/nisdomainname.1.gz >> /usr/share/man/man1/ypdomainname.1.gz >> /usr/share/man/man5/ethers.5.gz >> /usr/share/man/man8/arp.8.gz >> /usr/share/man/man8/ether-wake.8.gz >> /usr/share/man/man8/ifconfig.8.gz >> /usr/share/man/man8/mii-diag.8.gz >> /usr/share/man/man8/mii-tool.8.gz >> /usr/share/man/man8/nameif.8.gz >> /usr/share/man/man8/netplugd.8.gz >> /usr/share/man/man8/netstat.8.gz >> /usr/share/man/man8/plipconfig.8.gz >> /usr/share/man/man8/route.8.gz >> /usr/share/man/man8/slattach.8.gz >> /usr/share/man/pt/man1/dnsdomainname.1.gz >> /usr/share/man/pt/man1/domainname.1.gz >> /usr/share/man/pt/man1/hostname.1.gz >> /usr/share/man/pt/man1/nisdomainname.1.gz >> /usr/share/man/pt/man1/ypdomainname.1.gz >> /usr/share/man/pt/man8/arp.8.gz >> /usr/share/man/pt/man8/ifconfig.8.gz >> /usr/share/man/pt/man8/netstat.8.gz >> /usr/share/man/pt/man8/route.8.gz >> >> >> suomi >> >> >> >> Dave Feustel wrote: >>> I just got a gigabyte switch for my home network and I still >>> haven't figured out how to display the tx/rx data rate of each >>> nic connected to the switch. Also, the leds for the F9 computer >>> is not lighted on the switch, although F9 is accessing the >>> internet. >>> >>> What command will display the rx/tx data rates of each nic? >>> >>> Thanks. >>> Make sure you are using a cat 5e or 6 cable for gigabit. If the cable is old this could be why it only connects at 100Mb/s. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: FC11- getting message about 'battery broken'
Robert Moskowitz wrote: > I am running gnome and when I log in I get: > > Battery may be broken > > Your battery has a very low capacity (2%) , which means that it may be > old or broken. > > > Now I did not get anything like this with FC10 on the system and it > would run a number hours on battery. > > How do I check this out? > > Oh, the system is an ASUS ee701 with a 4Gb SDD drive and a 8Gb SD card. > > Robert, I have an eee 900 and since I installed F11 I've also been getting this broken battery message. I never had the errors on F10 either. The battery status information is also erratic, especially the discharging percentage, it's very buoyant. The battery seems to last a couple of hours, so it's definitely not dead. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: FC11 - Health problems for my SSD drive?
Robert Moskowitz wrote: > Again FC11 newly installed on an ASUS ee 701 that has a 4Gb SSD drive. > Since that is NOT enough space, I have a 8Gb SD card in the slot and the > / and /boot partitions is on the SD card. Swap drive and /home are on > the SSD card. > > Anyway, I just got a drive health warning. Opening the Icon I get it > telling me about potential problems with the SSD drive. It 'passed' the > assessment, but in the details some attributes exceeded the thresholds. > > > Now before I dive into this, I am wondering if SMART can tell this is an > SSD drive and some things WILL be different??? > > I recently had F10 and Mandriva 2009.1 installed and running fine on my eee 900 using the removable 16GB SSD as my /home and swap partitions. I decided to upgrade to F11 and anaconda produced errors during writing the partition layout and/or formatting them. I tried many times and it just kept aborting the install with different errors. I suspected a problem with one of the drives, so with the Live USB install loaded, I ran `dmesg` in a terminal and discovered lots of kernel errors writing to /dev/sdb (the 16GB SSD). ... Buffer I/O error on device sdb1, logical block 1 ... I tried writing files, fdisking, etc. the drive and it just produced more of the above I/O errors, and it seemed extremely so when working on the drive. I was convinced the drive was faulty and was ready to send it to asus for a warranty repair. Before doing this, I restore the factory Xandros image and also thought I'd zero the drive out to clear any of my data off first. I ran: # dd if=/dev/zero of=/dev/sdb1 bs=1K After a while it completed without error. (I didn't take note of how long it took) I ran `dmesg` again to see if there were masses of errors, but there were none. I rebooted and thought I'd try partitioning it again as there were no errors and to my absolute amazement. I managed to partition, create a filesystem, mount and write data to the drive with no I/O errors and it was fast again. Using it for over a week it's still running 100% and F11 even installed first time. Weird or what? I know with normal hard disks I/O errors indicate a dying drive, but not having much experience with SSD drives, are they that different. Is it possible the drive is OK now??? it certainly seems it. BTW. smartctl doesn't seem to be aware of the drive in it's database. So that didn't help much. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: FC11- getting message about 'battery broken'
Jatin K wrote: > On 11/05/2009 04:19 AM, Stewart Williams wrote: >> Robert Moskowitz wrote: >> >>> I am running gnome and when I log in I get: >>> >>> Battery may be broken >>> >>> Your battery has a very low capacity (2%) , which means that it may be >>> old or broken. >>> >>> >>> Now I did not get anything like this with FC10 on the system and it >>> would run a number hours on battery. >>> >>> How do I check this out? >>> >>> Oh, the system is an ASUS ee701 with a 4Gb SDD drive and a 8Gb SD card. >>> >>> >>> >> Robert, I have an eee 900 and since I installed F11 I've also been >> getting this broken battery message. I never had the errors on F10 >> either. >> >> The battery status information is also erratic, especially the >> discharging percentage, it's very buoyant. >> >> The battery seems to last a couple of hours, so it's definitely not dead. >> >> > what is the the output of " cat /proc/acpi/battery/BAT0/info" and > "cat /proc/acpi/battery/BAT0/state " ??? > > Hi Jatin, Sorry for the delay. /proc/acpi/battery/BAT0/info: present: yes design capacity: 5200 mAh last full capacity: 100 mAh battery technology: rechargeable design voltage: 8400 mV design capacity warning: 20 mAh design capacity low: 10 mAh capacity granularity 1: 52 mAh capacity granularity 2: 52 mAh model number:900 serial number: battery type:LION OEM info:ASUS /proc/acpi/battery/BAT0/state: present: yes capacity state: ok charging state: discharging present rate:unknown remaining capacity: 20 mAh present voltage: 7170 mV -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: SB driver in F12 ?
Luc MAIGNAN wrote: > Hi, > > is there any driver available under F12 for Creative Labs SB X-Fi ? > > BR > F12 correctly detects my card and shows that everything *should* be working, however I get no sound and when I try to play an audio CD or mp3 - it doesn't play/start. So there is definitely a driver for it now, but not sure why it doesn't work. Any idea's what I can try anyone? File a bug? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: SB driver in F12 ?
Mikkel wrote: > Check your mixer settings, especially the Pulse Audio settings. > > Mikkel > Anything specific? Because I have already looked at them and could see anything obvious. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: SB driver in F12 ?
Mikkel wrote: > I would check System --> Preferences --> Advanced Volume Control. Sorry, I can't seem to find this on my system. > Then check System --> Preferences --> Sound --> Hardware and make > sure your hardware is available to your user. Make sure the correct > output type is selected analog or digital). I have tried all the different settings here, digital and analog, but to no avail. It shows the card and all the volume controls, etc. are all set OK. Looking at this thread[1] it looks like the card is still not working even though its recognised now, where in earlier Fedora releases it hadn't been. > If your hardware is not showing up, run "aplay -l" and post the output. List of PLAYBACK Hardware Devices card 1: Generic [HD-Audio Generic], device 0: CA0110 Analog [CA0110 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 1: CA0110 Digital [CA0110 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 > Mikkel Thanks for your help Mikkel. [1] http://forums.fedoraforum.org/showthread.php?t=228541 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: SB driver in F12 ?
Mikkel wrote: > Now this is strange - we have a card 1, but no card 0. Card 0 is > normally the default sound card. I have to think about this a bit - > I think the SB card is detected as a sound card, but Alsa is not > able to access it. > > I am going to have to look - I think I have a SB card around here > someplace, so when I get some time I will stick it in a machine and > play. I am sorry I can not be of more help right now. > > Mikkel Could card 0 be the on-board (motherboard) sound card which is currently disabled in the BIOS? It's currently disabled because although it works in Linux, I think it may be faulty as I get popping noises from it occasionally and sometimes it even dies completely ... hence why I purchased the Creative Labs SB X-Fi (not knowing it didn't work on Linux). Thanks. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: SB driver in F12 ?
Marko Vojinovic wrote: > On Friday 11 December 2009 22:11:19 Stewart Williams wrote: >> Mikkel wrote: >>> I would check System --> Preferences --> Advanced Volume Control. >> Sorry, I can't seem to find this on my system. > > I don't use Gnome, but I guess you're talking about Pulseaudio volume control > tool. It is called pavucontrol, you can run it from a terminal, or yum > install > it if it isn't installed already. > > HTH, :-) > Marko > > I installed pavucontrol, though unfortunately it hasn't helped :( -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
F12 USB flash drives not recognised
In F12 any USB flash drives I plug in are not fully recognised (i.e. I cannot mount them) dmesg output: usb 1-5: new high speed USB device using ehci_hcd and address 11 usb 1-5: New USB device found, idVendor=0d7d, idProduct=0100 usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-5: Product: Flash Drive usb 1-5: Manufacturer: usb 1-5: SerialNumber: B7730201070A usb 1-5: configuration #1 chosen from 1 choice (missing sdX info, size, etc) They used to mount on F11 and earlier without any problems. On the same PC I can access them in Windows too, so the USB ports are OK. I have tried them on another machine running F11 and they are recognised an mount too. Where do I start to look or how do I try and get them working? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: SB driver in F12 ?
Frode Petersen wrote: > According to the ALSA soundcard matrix [1] they support PCI versions > (not PC-cards?) from ALSA v.1.0.21 onwards. Does this match your setup? > > I recently read somwhere (can't recall where) that the drivers were not > very good at the time when Creative open sourced their own (a month or > two ago maybe? I'm not sure.) If true, how much could they improve in > that time? I know this sounds a bit woolly... > > [1] http://www.alsa-project.org/main/index.php/Matrix:Vendor-Creative_Labs > > Frode Petersen > Hi Frode, It's a PCI-e (PCI Express) card, and it's not listed on that web page. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: SB driver in F12 ?
Luc MAIGNAN wrote: > Hi, > > i was the "postman" of this topic. It took another way of discussion but > I didn't get an answer for my question... > > Is there a driver available on F12 for the SoundBlaster X-FI card ? > > BR > Sorry Luc, but thought I'd answered your question in my first post and went on to say that although there is, it doesn't seem to work. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Yum command
Jim wrote: > FC12/KDE > > How would I do a yum command to enablerepo=updates-testing to update > python. I did it this way but it won't work. > > yum update --enablerepo=updates-testing python > It should be: yum --enablerepo=updates-testing _update_ python -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F12 USB flash drives not recognised [SOLVED]
Stewart Williams wrote: > In F12 any USB flash drives I plug in are not fully recognised (i.e. I > cannot mount them) > > dmesg output: > > usb 1-5: new high speed USB device using ehci_hcd and address 11 > usb 1-5: New USB device found, idVendor=0d7d, idProduct=0100 > usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > usb 1-5: Product: Flash Drive > usb 1-5: Manufacturer: > usb 1-5: SerialNumber: B7730201070A > usb 1-5: configuration #1 chosen from 1 choice > > (missing sdX info, size, etc) > > They used to mount on F11 and earlier without any problems. On the same > PC I can access them in Windows too, so the USB ports are OK. > > I have tried them on another machine running F11 and they are recognised > an mount too. > > Where do I start to look or how do I try and get them working? > I found out what it was. For some reason the usb-storage module wasn't being loaded because it had been blacklisted by anaconda in /etc/modprobe.d/anaconda.conf -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: How do I get SB X-FI sound card working on Fedora 12
John Nissley wrote: > Back to the subject, is pulseaudio alive? > $ ps -AH | grep pulse > > --->ps -AH | grep pulse > --->1691 ?00:00:09 pulseaudio > >> >> Another point that I probably should have made earlier is that I did >> compile alsa-driver-1.0.22.1.0.g2d697.0.g88788 since I thought I >> would need it. > > Uggghhh > snd-ctxfi is already a part of the built in alsa package (1.0.21) > shipped with Fedora 12. > I assume that you also did a "make install" when compiling the > alsa-driver tarball, right? > (Giving you a hybrid fedora + source installing) > > >I heard the Uggghhh and since this is really a test server I > just reinstalled fedora 12 so I have a clean install now. > >Here is my current RPM list for alsa > alsa-tools-firmware-1.0.20-4.fc12.x86_64 > alsa-utils-1.0.22-1.fc12.x86_64 > alsa-plugins-pulseaudio-1.0.21-2.fc12.x86_64 > alsa-firmware-1.0.20-2.fc12.noarch > alsa-lib-1.0.22-1.fc12.x86_64 > alsa-tools-1.0.20-4.fc12.x86_64 > > Under then Multimedia section of system setting it now shows SB X-Fi > Xtreme Audio which is different than before. > I do not have a pulse audio entry though which is troubling and I do not > have sound. > > Any other ideas? > See the previous thread[1] that I posted to regarding this. I have the same card, and although recognised now in F12, I also cannot get any sound from it. PulseAudio says it's working and is definitely un-muted. [1] https://www.redhat.com/archives/fedora-list/2009-December/msg00767.html -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
