Sound gone after system crash
I had a system crash and after a reboot my Lenny doesn't seem to be able to find either the GStreamer plugins or the sound device (at least that is the error message I get). Any ideas on how to fix it? André -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
standard libraries
I tried to compile a C code for the first time in a Debian machine and
apparently gcc can't find the standard libraries.
For example, compiling
#include
int main(){
printf("Hello World\n");
return 0;
}
gives the following errors:
hello.c:1:19: error: stdio.h: No such file or directory
hello.c: In function 'main':
hello.c:4: warning: incompatible implicit declaration of built-in
function 'printf'
AFAIK the standard libraries should be in /usr/include. A ls in this
directory returns
autosprintf.h gdict-1.0 gettext-po.h initreq.h python2.3 python2.4 X11
can somebody help me?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing gcc4.1 with synaptic
Thanks for the help, I just commented the CD-ROM entry. On Mon, Aug 4, 2008 at 11:58 AM, Sven Joachim <[EMAIL PROTECTED]> wrote: > On 2008-08-04 16:33 +0200, André Timpanaro wrote: > >> I tried to install gcc4.1 using synaptic and got the following message: >> >> Please insert the disk labeled: >> Debian GNU/Linux 4.0 r3 _Etch_ - Official amd64 NETINST Binary-1 >> 20080218-14:10 >> in drive /cdrom/ >> >> >> I don't get it, is gcc not in the repository? (wtf?) > > It is, but if a package is in multiple repositories, apt will simply > choose the first entry. If you have a fast Internet connection and > don't want to fiddle around with the CD-ROM, just remove the entry for > it from your sources.list and run "apt-get update". > > Sven > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem installing gcc4.1 with synaptic
I tried to install gcc4.1 using synaptic and got the following message: Please insert the disk labeled: Debian GNU/Linux 4.0 r3 _Etch_ - Official amd64 NETINST Binary-1 20080218-14:10 in drive /cdrom/ I don't get it, is gcc not in the repository? (wtf?) André Martin Timpanaro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ethernet configuration
I think I solved it, I deleted the hwaddress line in 'interfaces' and it worked (the GNOME thing still says I don't have a connection though, so I think I'll just assume it doesn't know what it's talking about) André Timpanaro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ethernet configuration
> > If I understand you correctly, you still have network problems even > though udev now reliably assigns eth0 to the nvidia NIC. Can you post > your entire /etc/network/interfaces as well as the output of > "/sbin/ifconfig" and "dmesg | grep forcedeth" (right after boot), so > that we can have a closer look? > Here you go /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static address 143.107.130.137 netmask 255.255.255.0 network 143.107.130.0 broadcast 143.107.130.255 gateway 143.107.130.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 143.107.130.9 hwaddress ether 00:00:6C:B0:BA:A7 /sbin/ifconfig: eth0 Link encap:Ethernet HWaddr 00:00:6C:B0:BA:A7 inet addr:143.107.130.137 Bcast:143.107.130.255 Mask:255.255.255.0 inet6 addr: fe80::200:6cff:feb0:baa7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:147 errors:0 dropped:0 overruns:0 frame:0 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14136 (13.8 KiB) TX bytes:3198 (3.1 KiB) Interrupt:193 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) dmesg | grep "eth": forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56. forcedeth: using HIGHDMA eth0: forcedeth.c: subsystem: 01028:020e bound to :00:07.0 eth0: no IPv6 routers present Also, while I rebooted there was a problem reported about eth5 (wtf?) and SIOCSIFNETMASK (I couldn't read it all) As before, he couldn't find any network devices (according to the GNOME "thing" on the upper-right corner, the one that resembles a net cable plug) despite the result of ifconfig. If I delete my devices in both 'z25_persistent-net.rules' and on '/etc/network/interfaces' I get it working again. The requested outputs look like these at the moment: '/etc/network/interfaces': # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface iface eth0 inet static address 143.107.130.137 netmask 255.255.255.0 gateway 143.107.130.1 auto eth0 /sbin/ifconfig: eth0 Link encap:Ethernet HWaddr 00:00:6C:CD:FD:99 inet addr:143.107.130.137 Bcast:143.107.130.255 Mask:255.255.255.0 inet6 addr: fe80::200:6cff:fecd:fd99/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2887 errors:0 dropped:0 overruns:0 frame:0 TX packets:1349 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1178332 (1.1 MiB) TX bytes:314589 (307.2 KiB) Interrupt:193 Base address:0xc000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) dmesg | grep "eth": forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.56. forcedeth: using HIGHDMA eth0: forcedeth.c: subsystem: 01028:020e bound to :00:07.0 eth0: no IPv6 routers present eth0: no IPv6 routers present -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ethernet configuration
On 7/5/08, Florian Kulzer <[EMAIL PROTECTED]> wrote:
> [ Please turn off the HTML part of your messages (I think the Gmail web
> interface calls it something like "rich format") and please stop
> top-posting (I will fix that for this message). ]
>
Sorry.
> On Fri, Jul 04, 2008 at 11:15:05 -0300, André Timpanaro wrote:
> > On Wed, Jul 2, 2008 at 2:01 PM, Florian Kulzer wrote:
> > > On Wed, Jul 02, 2008 at 10:43:58 +0300, Andrei Popescu wrote:
> > > > On Tue, Jul 01, 2008 at 06:04:17PM -0300, André Timpanaro wrote:
> > > > > I've found the /etc/udev/rules.d/z25_persistent-net.rules file:
>
> [...]
>
> > > > I've heard here that some (all?) nVidia chipsets will change MAC on
> > > > every boot. That's your problem.
>
> [...]
>
> > > > You can look in the BIOS for a setting to have a persistent MAC or
> > > > rewrite the rule to allocate device names based only on the kernel
> > > > module (forcedeth?).
> > >
> > > You could try to use a wildcard in z25_persistent-net.rules. This might
> > > work as long as you don't put a second nvidia network card into this
> > > machine:
> > >
> > > # PCI device 0x10de:0x03ef (forcedeth)
> > > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:*", NAME="eth0"
> >
> > I made the change in 'z25_persistent-net.rules' and it stoped creating new
> > interfaces.
>
> OK, so far, so good. At least the proliferation of ethX devices should
> stop now.
>
> > > To make sure that the rest of your network sees a consistent MAC address
> > > for this computer, try to set it explicitly in the eth0 stanza of
> > > /etc/network/interfaces:
> > >
> > > # The primary network interface
> > > allow-hotplug eth0
> > > iface eth0 inet dhcp
> > >hwaddress ether 00:00:6c:e9:01:77
> >
> > But specifying the MAC address didn't worked (he configured the
> > interface correctly but I still couldn't connect to the internet). Probably
> > it wasn't 00:00:6c:e9:01:77 anymore for eth0 (I suspected that would happen
> > but decided to try it anyway).
>
> You can check the IP address with "ifconfig eth0". Does your DHCP server
> base the DHCP leases on MAC addresses?
>
Forgot to mention, it's a static server (I'm setting the ip adresses
on /etc/network/interfaces though).
> > Isn't there a sure way to retrieve the MAC address correctly?
>
> The suggestion above was inspired by this article:
>
> http://www.debian-administration.org/articles/501
>
> I have no idea if it works for all forcedeth-related problems.
>
> > By the way, my BIOS doesn't allow changes in the settings for the net card,
> > so I can't make the MAC address persistent.
>
> According to the comments in forcedeth.c, the problem with retrieving
> the correct MAC is caused by a buggy BIOS, so a BIOS upgrade might help.
>
ok.
> AFAICT, the forcedeth driver does not allow to set a fixed MAC address
> via a module parameter. If you compile your own kernel then you can try
> to change the code that sets the random address
>
>dev->dev_addr[0] = 0x00;
>dev->dev_addr[1] = 0x00;
>dev->dev_addr[2] = 0x6c;
>get_random_bytes(&dev->dev_addr[3], 3);
>
> to this
>
>dev->dev_addr[0] = 0x00;
>dev->dev_addr[1] = 0x00;
>dev->dev_addr[2] = 0x6c;
>dev->dev_addr[3] = 0xe9;
>dev->dev_addr[4] = 0x01;
> dev->dev_addr[5] = 0x77;
>
> I have no way of testing if this actually works. Google finds some
> recent posts on LKML about patches for the MAC detection of forcedeth,
> so you might want to try the newer code (especially if you are
> currently using the version in Etch).
>
> http://lkml.org/lkml/2008/4/8/391
> http://marc.info/?t=11921571691&r=1&w=2
>
I will take a look at these.
> --
> Regards,| http://users.icfo.es/Florian.Kulzer
> Florian |
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
André Timpanaro
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ethernet configuration
I made the change in 'z25_persistent-net.rules' and it stoped creating new
interfaces. But specifying the MAC address didn't worked (he configured the
interface correctly but I still couldn't connect to the internet). Probably
it wasn't 00:00:6c:e9:01:77 anymore for eth0 (I suspected that would happen
but decided to try it anyway).
Isn't there a sure way to retrieve the MAC address correctly?
By the way, my BIOS doesn't allow changes in the settings for the net card,
so I can't make the MAC address persistent.
On Wed, Jul 2, 2008 at 2:01 PM, Florian Kulzer <
[EMAIL PROTECTED] <[EMAIL PROTECTED]>> wrote:
> On Wed, Jul 02, 2008 at 10:43:58 +0300, Andrei Popescu wrote:
> > On Tue, Jul 01, 2008 at 06:04:17PM -0300, André Timpanaro wrote:
> > > I've found the /etc/udev/rules.d/z25_persistent-net.rules file:
> > >
> > > # This file was automatically generated by the
> /lib/udev/write_net_rules
> > > # program, probably run by the persistent-net-generator.rules rules
> file.
> > > #
> > > # You can modify it, as long as you keep each rule on a single line.
> > > # MAC addresses must be written in lowercase.
> > >
> > > # PCI device 0x10de:0x03ef (forcedeth)
> > > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:e9:01:77",
> > > NAME="eth0"
>
> [ snip: eth1 - eth7 ]
>
> > > # PCI device 0x10de:0x03ef (forcedeth)
> > > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:32:fa:60",
> > > NAME="eth8"
> >
> > I've heard here that some (all?) nVidia chipsets will change MAC on
> > every boot. That's your problem.
>
> IIRC, certain versions of the forcedeth driver have a bug and cannot
> determine the real MAC address of the device. To compensate for this, a
> semi-random MAC address is chosen that is formally correct for nvidia
> (00:00:6c plus three random bytes). The idea is to minimize the chance
> that two nvidia devices on the same local network get the same MAC
> address. This behavior is unfortunately not really compatible with the
> design philosophy of udev.
>
> > You can look in the BIOS for a setting to have a persistent MAC or
> > rewrite the rule to allocate device names based only on the kernel
> > module (forcedeth?).
>
> You could try to use a wildcard in z25_persistent-net.rules. This might
> work as long as you don't put a second nvidia network card into this
> machine:
>
> # PCI device 0x10de:0x03ef (forcedeth)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:*", NAME="eth0"
>
> To make sure that the rest of your network sees a consistent MAC address
> for this computer, try to set it explicitly in the eth0 stanza of
> /etc/network/interfaces:
>
> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet dhcp
>hwaddress ether 00:00:6c:e9:01:77
>
> --
> Regards,| http://users.icfo.es/Florian.Kulzer
> Florian |
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
>
>
André Timpanaro
Re: ethernet configuration
I've found the /etc/udev/rules.d/z25_persistent-net.rules file:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, probably run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:e9:01:77",
NAME="eth0"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:f2:c0:89",
NAME="eth1"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:30:e1:28",
NAME="eth2"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:6f:75:06",
NAME="eth3"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:25:de:d3",
NAME="eth4"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:b5:70:4b",
NAME="eth5"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:06:6c:76",
NAME="eth6"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:db:fb:52",
NAME="eth7"
# PCI device 0x10de:0x03ef (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:00:6c:32:fa:60",
NAME="eth8"
Taking a look on write_net_rules wasn't very useful (I don't understand this
scripting language very well). My best guess is that it has something to do
with this bit:
# If a rule using the current name already exists then find a new name and
# report it to udev which will rename the interface.
basename=${INTERFACE%%[0-9]*}
if interface_name_taken; then
INTERFACE="$basename$(find_next_available "$basename[0-9]*")"
if [ ! -t 1 ]; then
echo "INTERFACE_NEW=$INTERFACE"
fi
fi
# the DRIVERS key is needed to not match bridges and VLAN sub-interfaces
match="DRIVERS==\"?*\", ATTRS{address}==\"$MAC_ADDR\""
if [ $basename = "ath" -o $basename = "wlan" ]; then
match="$match, ATTRS{type}==\"1\"" # do not match the wifi* interfaces
fi
write_rule "$match" "$INTERFACE" "$COMMENT"
What exactly should this script be doing? Will modyfing only
'z25_persistent-net.rules' be enough? (I didn't tried because I didn't
looked for the MAC adress).
André Timpanaro
ethernet configuration
I've installed etch recently and I'm having a real hard time configuring my ethernet connection. Firstly, each time the computer is rebooted it seems to create a new interface (for example, my only ethernet connection at this moment is eth7). Also, the Gnome's Network Settings program (Desktop\Administration\Networking, in the top panel) is not solving the problem. If I try to place the correct IP adresses and after that use 'ifconfig -a' it tells me that the connection is still configured incorrectly (even though, when I go back to Network Settings, they are correct). The only way to correctly configure it is using 'ifconfig' and 'route' (and this must be done every single time the computer is turned on or rebooted). Despite it all, the Network Settings works fine for the DNS server I think there must be something wrong in a configuration file, but I don't have the slightest idea. André Timpanaro
