Problem with udev and ethX naming in latest Fedora 19.
by Ben Greear
I'm having all sorts of trouble trying to get udev to rename
my interfaces based on MAC address. Please don't suggest
I use biosdevname or other such things: I really do want names
to be ethX and I want them in a specific order base on MAC address.
[root@localhost ~]# cat /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:e0:ed:1c:ec:e4", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth2"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:e0:ed:1c:ec:e5", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth3"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:30:48:fc:17:a2", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:30:48:fc:17:a3", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth1"
If I change the NAME=ethX to NAME=ethXr, then it seems to work. But, if I leave it as is above,
it does not appear to make any changes at all to the naming. I turned on debugging:
[root@localhost ~]# cat /etc/udev/udev.conf
# see udev(7) for details
udev_log="debug"
But, I never see anything at all about 'ethX'.
I do not see any errors in /var/log/messages about it failing to rename due to 'File Exists'.
I read this thread about similar issue in Fedora 18, but towards the bottom, there is
a claim the bug was fixed. Maybe it came back?
http://comments.gmane.org/gmane.linux.redhat.fedora.general/427615
[root@localhost ~]# rpm -qa|grep systemd
systemd-python-204-9.fc19.x86_64
systemd-204-9.fc19.x86_64
systemd-libs-204-9.fc19.x86_64
systemd-sysv-204-9.fc19.x86_64
I'd be grateful for any help..Fedora 17 has become unstable for us due to gnome-fallback mode crashing,
so I'd like to be able to move forward to Fedora 19, but I really have to get udev working properly
first...
Thanks,
Ben
--
Ben Greear <greearb(a)candelatech.com>
Candela Technologies Inc http://www.candelatech.com
10 years, 9 months
Undetected Fresco Logic FL1000G USB 3.0 controller in Asus N43SN after replace a motherboard
by Marcin Zajączkowski
Hi,
I had no problem with a USB 3.0 port in my Asus N43SN since I bought a
laptop (~2 years). Recently I replaced a motherboard to the new one
(N43SL.413 looked the same as the first one) due to a problem with a
graphical chipset and after that a USB3 controller stopped to be even
detected.
$ lspci | grep -i USB
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 (rev 05)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #1 (rev 05)
(in the past there was also an additional USB3 controller - AFAIR Fresco
Logic FL1000G USB 3.0).
I though it was a problem with a motherboard, but after boot with
different kernel the controller showed up. I started to suspect a bug in
kernel, but after two days (I use it only from time to time with my USB3
hard drive) I noticed that USB3 port/controller is not visible anymore
with any kernel. I don't know if this behavior is normal for a hardware
malfunction.
In /var/log/messages there is no info about the USB3 controller (see log
below). I tried pci=nomsi in Grub, but with no effect. I could try to
replace the mother board to the new one once again (I don't have the old
one), but it could be hard to convince service that this is a problem
with hardware (the port in the new motherboard worked fine twice). I
don't any other OS to test it on it.
Tested with kernels:
kernel-3.10.4-100.fc18.x86_64
kernel-3.9.11-200.fc18.x86_64
kernel-3.9.9-201.fc18.x86_64
and in addition with System Rescue CD.
What could be a reason? Can I force kernel to "see it" (there is no
module xhci_hcd - it is built into kernel)?
Marcin
[ 1.424160] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.424162] ehci-pci: EHCI PCI platform driver
[ 1.424249] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 1.424310] ehci-pci 0000:00:1a.0: new USB bus registered, assigned
bus number 1
[ 1.424327] ehci-pci 0000:00:1a.0: debug port 2
[ 1.428259] ehci-pci 0000:00:1a.0: irq 16, io mem 0xdf008000
[ 1.433314] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 1.433333] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.433335] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.433337] usb usb1: Product: EHCI Host Controller
[ 1.433339] usb usb1: Manufacturer: Linux 3.9.9-201.fc18.x86_64 ehci_hcd
[ 1.433341] usb usb1: SerialNumber: 0000:00:1a.0
[ 1.433438] hub 1-0:1.0: USB hub found
[ 1.433442] hub 1-0:1.0: 2 ports detected
[ 1.433581] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 1.433621] ehci-pci 0000:00:1d.0: new USB bus registered, assigned
bus number 2
[ 1.433638] ehci-pci 0000:00:1d.0: debug port 2
[ 1.437561] ehci-pci 0000:00:1d.0: irq 23, io mem 0xdf007000
[ 1.443310] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 1.443323] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.443325] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.443327] usb usb2: Product: EHCI Host Controller
[ 1.443329] usb usb2: Manufacturer: Linux 3.9.9-201.fc18.x86_64 ehci_hcd
[ 1.443331] usb usb2: SerialNumber: 0000:00:1d.0
[ 1.443414] hub 2-0:1.0: USB hub found
[ 1.443418] hub 2-0:1.0: 2 ports detected
[ 1.443485] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.443495] uhci_hcd: USB Universal Host Controller Interface driver
=== this part is currently missing - START ===
[ 1.443569] xhci_hcd 0000:04:00.0: xHCI Host Controller
[ 1.443608] xhci_hcd 0000:04:00.0: new USB bus registered, assigned
bus number 3
[ 1.572613] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.572616] usb usb3: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.572617] usb usb3: Product: xHCI Host Controller
[ 1.572620] usb usb3: Manufacturer: Linux 3.9.9-201.fc18.x86_64 xhci_hcd
[ 1.572621] usb usb3: SerialNumber: 0000:04:00.0
[ 1.572706] hub 3-0:1.0: USB hub found
[ 1.572712] hub 3-0:1.0: 1 port detected
[ 1.572761] xhci_hcd 0000:04:00.0: xHCI Host Controller
[ 1.572802] xhci_hcd 0000:04:00.0: new USB bus registered, assigned
bus number 4
[ 1.572829] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 1.572831] usb usb4: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 1.572833] usb usb4: Product: xHCI Host Controller
[ 1.572835] usb usb4: Manufacturer: Linux 3.9.9-201.fc18.x86_64 xhci_hcd
[ 1.572837] usb usb4: SerialNumber: 0000:04:00.0
[ 1.572911] hub 4-0:1.0: USB hub found
[ 1.572916] hub 4-0:1.0: 1 port detected
=== this part is currently missing - END ===
[ 1.580289] usbcore: registered new interface driver usbserial
[ 1.580295] usbcore: registered new interface driver usbserial_generic
10 years, 9 months
Problem with Matrox MGA G200eW video driver.
by Ben Greear
I have a fancy and quite new E5 processor server system that has a Matrox VGA port in it:
e:04.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)
This appears to use the mgag200 kernel module.
When this module is loaded, the Xorg log complains saying the module must be unloaded
and I end up running 'llvmpipe' and performance is horrible.
If I blacklist the module, it still runs in emulation mode and performance is horrible.
Here is what I think is the interesting part for the black-list variant:
[ 26.079] (II) Module vgahw: vendor="X.Org Foundation"
[ 26.079] compiled for 1.14.2, module version = 0.1.0
[ 26.079] ABI class: X.Org Video Driver, version 14.1
[ 26.079] (--) MGA(0): Chipset: "mgag200 eW Nuvoton"
[ 26.079] (--) MGA(0): Linear framebuffer at 0xF9000000
[ 26.079] (--) MGA(0): MMIO registers at 0xFB800000
[ 26.079] (--) MGA(0): Pseudo-DMA transfer window at 0xFB000000
[ 26.150] (II) MGA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 26.150] (==) MGA(0): Depth 24, (--) framebuffer bpp 32
[ 26.150] (==) MGA(0): RGB weight 888
[ 26.150] (**) MGA(0): Enabling KVM
[ 26.150] (==) MGA(0): Using HW cursor
[ 26.150] (**) MGA(0): Using "Shadow Framebuffer" - acceleration disabled
[ 26.150] (--) MGA(0): Video BIOS info block at offset 0x07D60
[ 26.150] (==) MGA(0): VideoRAM: 16320 kByte
So, first question: Should I be blacklisting the driver?
And second, any idea on how to either get the acceleration working,
or make gnome work OK w/out it? I don't care at all about 3D affects,
I just need basic desktop functionality to work w/out too much overhead.
Thanks,
Ben
--
Ben Greear <greearb(a)candelatech.com>
Candela Technologies Inc http://www.candelatech.com
10 years, 9 months
Cron job resetting hardware?
by Tom Horsley
This bug:
https://bugzilla.redhat.com/show_bug.cgi?id=958326
has gotten me doing crazy things like setting up my android
camera to take time lapse pictures of the screen every minute
to find out exactly when it happens so I can look in the logs
to see what was going on then :-).
Last night, the screen went funny between 1:16 am and 1:17 am.
In /var/log/messages I found this sort of stuff:
Aug 16 01:17:08 zooty bluetoothd[453]: bluetoothd[453]: Endpoint registered: sender=:1.5382 path=/MediaEndpoint/HFPAG
Aug 16 01:17:08 zooty pulseaudio[17966]: [pulseaudio] module.c: Failed to load module "module-esound-protocol-unix" (argument: ""): initialization failed.
...
Almost like something came around and reset a bunch of
hardware at the same time the screen flaked out (though
I found no messages at all for anything related to the
intel video drivers).
Does anyone know of something that runs in cron (or maybe
systemd) that helpfully resets a lot of hardware nightly?
This whole thing is getting more and more mysterious.
10 years, 9 months
Sound problem on fc 19 - xmms no longer can play
by William W. Austin
Last weekend I did a clean install of Fedora 19 on my main workstation
replacing fc17 which had been there. (As I usually do, I pulled the
drive containing /, /tmp, /var, and swap and replaced it there. That
drive is in another machine and I can compare the diffs.)
Suddenly although alsaplayer works just fine, xmms cannot play anything.
When I attempt to run xmms, I get a show-box with the error message:
"Please check that
Your soundcard is configured properly
You have the correct output plugin selected
No other program is blocking the soundcard"
I've done that and the card is configured correctly, and the correct
output plugin is selected - and no other program that I can find is
blocking the card.
I've even gone so far as to do a "yum remove pulseaudio" (which worked
just fine to solve this same problem up through at least fc17), but that
didn't help either. So I suspect that something else is going on here.
lsof doesn't show anything holding any of the sound devices open.
The rpms all verify correctly
root gets the same result as a non-privileged user.
So any suggestions would be greatly appreciated.
Thanks,
- Bill
--
william w. austin airedad(a)att.net
"life is just another phase i'm going through. this time, anyway ..."`
10 years, 9 months
Two (related?) problems in fresh install of Fedora 19
by William W. Austin
This weekend I did a clean install of fedora 19 on my main workstation
(I pulled the drive containing /, /tmp, and /var (plus swap) running
fedora 17, and it's available to compare).
I didn't care for the installer changes since 17, but I got through it
alive.
HOWEVER, I am now having some network problems (at least 2) and I think
they are related.
The first sounds trivial and isn't. The system thinks its hostname is
"nick" even though the contents of /etc/sysconfig/network say otherwise.
That is, the hostname is set correctly there. Also a recursive grep
through /etc finds no instance of the string "nick" anywhere (nor in
/boot, /boot/grub2, etc).
Setting the hostname manually works up to a point but of course some
things never reference the hostname after boot up and they are somewhat
hosed.
The other main problem may be related - it's a network issue, probably
connected with PackageKit. Every few minutes I am getting a message saying:
No network connection available
cannot refresh cache when offline
So I suspect that PackageKit may be hosed and may be trying to reference
the wrong hostname.
I have a second problem but it's related to sound not network and I'll
put it in a second post.
Thanks in advance for any help - yes I did a bugzilla search but if it's
there I missed it, and I didn't see this problem in any email about fc19
(although I admittedly may have missed it).
- Bill
--
william w. austin airedad(a)att.net
"life is just another phase i'm going through. this time, anyway ..."
10 years, 9 months
systemd-logind unable to create a new session
by Geoffrey Leach
This is the result of running 'at', but I suspect its not related to 'at' per se.
Aug 14 16:00:00 puget systemd-logind[446]: New session 18 of user geoff.
Aug 14 16:00:00 puget atd[2098]: Cannot make/remove an entry for the specified session
Aug 14 16:00:00 puget systemd-logind[446]: Removed session 18.
Environment: Fedora 19, up-to-date. Kernel is 3.10.5-201.fc19.x86_64 #1 SMP
10 years, 9 months
AT fails
by Geoffrey Leach
When I start a job with at(1), /var/log/messages has the following:
Aug 14 16:00:00 puget systemd-logind[446]: New session 18 of user geoff.
Aug 14 16:00:00 puget atd[2098]: Cannot make/remove an entry for the specified session
Aug 14 16:00:00 puget systemd-logind[446]: Removed session 18.
Same problem for root. At worked fine yesterday.
Ideas? Thanks.
10 years, 9 months
nodejs on Fedora 19
by Roger
I yum removed nodejs which removed all v8 s as well
then yum installed nodejs which installed Package v8.x86_64
1:3.14.5.10-1.fc19
Rails requires nodejs which requires v8.
v8 is buggy and will not update with sudo yum update
Resolving Dependencies
--> Running transaction check
---> Package v8.x86_64 1:3.14.5.10-1.fc19 will be updated
--> Processing Dependency: v8 < 1:3.15 for package:
nodejs-0.10.14-1.fc19.x86_64
---> Package v8.x86_64 1:3.17.6.14-2.fc19 will be an update
--> Running transaction check
---> Package v8.i686 1:3.14.5.10-1.fc19 will be installed
---> Package v8.x86_64 1:3.14.5.10-1.fc19 will be updated
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: 1:v8-3.17.6.14-2.fc19.x86_64 !=
1:v8-3.14.5.10-1.fc19.i686
Has anyone managed to solve nodejs crappy requirement for Package
v8.i686 1:3.14.5.10-1.fc19 which seems to cause all the problems, even
when installed.
yum check shows no errors.
Only way I can update Fedora 19 is to yum update --skip-broken
sometimes and --exclude v8 other times.
Seems messy
What's the best way to resolve the v8 dilemma in these times of 4
cylinders or hybrids.
thanks Roger
10 years, 9 months
Moving Thunderbird Mail from WindowsXP to Fedora18
by Mickey
I have retreved the Thunderbird folder from a crashed WindowsXP and now
have it on a Fedora 18 /home/user install.
The Fedora install already has Thunderbird installed and New Emails are
already in Thunderbird, I want import the Emails from the WindowsXP
Thunderbird in with the existing emails already in Fedora Thunderbird.
How do I do that ??
10 years, 9 months
