ALSA, AWE32, kernel 2.6 issues?
I recently upgraded my kernel from 2.2 to 2.6; various other problems eventually required a complete OS reinstall. I can't get my sound card (Creative SB AWE 32) to work with ALSA; it worked fine under OSS. Is there anything special about Debian that may require me to configure things differently from the ALSA documentation?
Re: rerunning autodetect
On 5/2/06, Florian Kulzer <[EMAIL PROTECTED]> wrote: On Tue, May 02, 2006 at 05:45:28 -0500, Mark Tilford wrote: > On 5/1/06, Christopher Nelson <[EMAIL PROTECTED]> wrote: > >On Mon, May 01, 2006 at 09:29:21PM -0500, Mark Tilford wrote: [...] > >> The /etc/network/devices lines related to eth0 were: > >> auto eth0 > >> iface eth0 inet dhcp > >> > >> /sbin/ifconfig/eth0 up gives response > >> eth0: ERROR while getting interface flags: No such device. > >> > >> What does this error message mean, and how do I fix it? apt-get is a > >> great program, but it's nearly useless until I can get my internet > >> connection working. > > > >Try just '/sbin/ifconfig' without the eth0 appended to it. What is the > >output of a 'lspci |grep Ethernet'? That should tell you if the new > >box' ethernet controller is recognised by the system. > > /sbin/ifconfig only lists loopback. > lspci | grep Ethernet yields nothing. > The card is a 3c509. Try to modprobe the 3c509 and/or the 3c59x kernel module. Maybe the device will be created then, or you get an error message which gives us a clue. modprobe 3c509 /sbin/ifconfig/eth0 up dhclient and I can connect out! Thank you to all who helped! Now I just have do a long download of everything... Any other likely gotchas that may occur because I installed on a different computer?
Re: rerunning autodetect
On 5/1/06, Christopher Nelson <[EMAIL PROTECTED]> wrote: On Mon, May 01, 2006 at 09:29:21PM -0500, Mark Tilford wrote: > On 4/30/06, James Westby <[EMAIL PROTECTED]> wrote: > >On (30/04/06 18:35), Mark Tilford wrote: > >> On 4/29/06, Mark Tilford <[EMAIL PROTECTED]> wrote: > >> >For various reasons, I had to run the installation on one computer, > >> >then transfer the hard drive to a different computer. How do I rerun > >> >the code that autodetects hardware (specifically the netword card)? > >> > >> >From bootup: > >> (DHCP program runs) > >> eth0: ERROR while getting interface flags: No such device > >> Bind socket to interface: No such device > >> exiting. > >> Failed to bring up eth0. > >> done. > >> > > > >I think that this means that the name of the interface in > >/etc/network/interfaces doesn't equal the name of the device on the > >system. > > > >Compare the output of ifconfig with the line auto eth0 or similar in > >that file. > > > > The /etc/network/devices lines related to eth0 were: > auto eth0 > iface eth0 inet dhcp > > /sbin/ifconfig/eth0 up gives response > eth0: ERROR while getting interface flags: No such device. > > What does this error message mean, and how do I fix it? apt-get is a > great program, but it's nearly useless until I can get my internet > connection working. Try just '/sbin/ifconfig' without the eth0 appended to it. What is the output of a 'lspci |grep Ethernet'? That should tell you if the new box' ethernet controller is recognised by the system. /sbin/ifconfig only lists loopback. lspci | grep Ethernet yields nothing. The card is a 3c509.
Re: rerunning autodetect
On 4/30/06, James Westby <[EMAIL PROTECTED]> wrote: On (30/04/06 18:35), Mark Tilford wrote: > On 4/29/06, Mark Tilford <[EMAIL PROTECTED]> wrote: > >For various reasons, I had to run the installation on one computer, > >then transfer the hard drive to a different computer. How do I rerun > >the code that autodetects hardware (specifically the netword card)? > > >From bootup: > (DHCP program runs) > eth0: ERROR while getting interface flags: No such device > Bind socket to interface: No such device > exiting. > Failed to bring up eth0. > done. > I think that this means that the name of the interface in /etc/network/interfaces doesn't equal the name of the device on the system. Compare the output of ifconfig with the line auto eth0 or similar in that file. The /etc/network/devices lines related to eth0 were: auto eth0 iface eth0 inet dhcp /sbin/ifconfig/eth0 up gives response eth0: ERROR while getting interface flags: No such device. What does this error message mean, and how do I fix it? apt-get is a great program, but it's nearly useless until I can get my internet connection working.
Re: rerunning autodetect
On 4/30/06, James Westby <[EMAIL PROTECTED]> wrote: On (30/04/06 18:35), Mark Tilford wrote: > On 4/29/06, Mark Tilford <[EMAIL PROTECTED]> wrote: > >For various reasons, I had to run the installation on one computer, > >then transfer the hard drive to a different computer. How do I rerun > >the code that autodetects hardware (specifically the netword card)? > > >From bootup: > (DHCP program runs) > eth0: ERROR while getting interface flags: No such device > Bind socket to interface: No such device > exiting. > Failed to bring up eth0. > done. > I think that this means that the name of the interface in /etc/network/interfaces doesn't equal the name of the device on the system. Compare the output of ifconfig with the line auto eth0 or similar in that file. James How do I rerun the program that generated /etc/network/interfaces ?
Re: rerunning autodetect
On 4/29/06, Mark Tilford <[EMAIL PROTECTED]> wrote: For various reasons, I had to run the installation on one computer, then transfer the hard drive to a different computer. How do I rerun the code that autodetects hardware (specifically the netword card)? From bootup: (DHCP program runs) eth0: ERROR while getting interface flags: No such device Bind socket to interface: No such device exiting. Failed to bring up eth0. done.
rerunning autodetect
For various reasons, I had to run the installation on one computer, then transfer the hard drive to a different computer. How do I rerun the code that autodetects hardware (specifically the netword card)?
