ARPORT y
else
define_bool CONFIG_PARIDE_PARPORT m
fi
so, as you can see, CONFIG_PARIDE_PARPORT will be set to "yes" even
if CONFIG_PARPORT="no".
why not simply write:
define_bool CONFIG_PARIDE_PARPORT $CONFIG_PARPORT
instead?
regards,
herbert rosmanith
[EMAIL PROTECT
hello,
when doing a series of insmod/rmmod of af_netlink, I noticed
/proc/net/netlink entries being added each time.
this small patch addresses the problem:
--- snip ---
bash-2.03# diff -u linux-2.4.5.orig/net/netlink/af_netlink.c
linux-2.4.5.new/net/netlink/af_netlink.c
--- linux-2.4.5.orig/
good day,
when setting up a more or less old board, 2.6.22.1 crashes during an
"emerge --sync" (gentoo installation).
first, the screen will start funny - like a crashed C64 (from the "good"
old days). I made a photo, you can look at it here:
http://wildsau.enemy.org/~kernel/epia-crash.
> Checked the RAM on the box? Kinda weird if you're getting VRAM corruption, I
> wonder if this is due to the RAM failing at the point where the framebuffer
> is mapped?
you are probably right... I removed one of the RAMs, no crash
anymore. This is not ... nice. The manual says, that the board c
hi,
I see a strange numbering of ethernet devices with a VIA EPIA EK
board. This board has two ethernet connectors, you can see it
here:
http://www.via.com.tw/en/products/mainboards/motherboards.jsp?motherboard_id=420
I configured the system such that via-rhine is loaded as a module.
When doing
>
> Strange or not, correct or not - depends on the point of view.
>
> The key word here is "udev" - check your udev rules. Since some time
> ago udev on some distros comes with rules to give persistent device
> names for network interfaces. Some time ago you had eth0 and eth1
> with different
>
> On Aug 2 2007 12:42, Herbert Rosmanith wrote:
> There never *were* days when eth0 remained eth0 across such changes.
but there *were* days when eth0 was eth0, if the kernel reports it as such.
now there is no eth0 at all. if I see an "eth0" from dmesg, I expect
it to b
> > cards around), eth0 would also suddenly become a different one. There never
> > *were* days when eth0 remained eth0 across such changes.
>
> but there *were* days when eth0 was eth0, if the kernel reports it as such.
> now there is no eth0 at all. if I see an "eth0" from dmesg, I expect
> it
> Wait, you forget that something may change the name. That dmesg message
> from 1 second ago does not need to be valid anymore, just as anything
> else in this world.
there are many things in this world which are usually very persistent, and
people rely on their persistence. e.g. in my office,
> >And now tell me please how can I connect two messages from dmesg:
> >eth0: Tigon3 [partno(BCM95721) rev 4201 PHY(5750)] (PCI Express)
> >10/100/1000Base-T Ethernet 00:14:5e:5d:18:26
> >nic10: Link is up at 100 Mbps, full duplex.
>
> Generally, the "link is xyz" message comes directly after loa
hello list,
this afternoon I bought a new usb/wlan adapter, which identifies
itself as:
# lsusb
...
Bus 001 Device 017: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU
802.11n WLAN Adapter
the first thing I noticed is that the device name is renamed:
[ .688299] systemd-u
11 matches
Mail list logo
