[ARCHIVED THREAD] - Linux guys: HELP (Page 1 of 2)
Posted: 5/15/2014 3:23:45 PM EDT
|
Ok so I just re-purposed an old XP machine for the garage and there are two problems.
Full Disclosure: I haven't used cmd line in a while and was never really adept in the first place and this is the latest version of Ubuntu. Problems: 1. the backlit keyboard doesn't work found this but I have no idea how to create this type of file or edit the properties: "For example in Ubuntu I tried a few things that worked, some that didn't. In the end I settled on this approach: Create file /etc/xdg/autostart/backlight.desktop Edit the file so it looks something like this: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true Ideally I wanted to get the backlight to activate at the login screen (before any user has logged on) but couldn't get it working. The method above turns on the backlight once any user logs in." 2. The speakers do not work. When I plug the speaker wire into the sound card, you can hear the speakers make a little noise, but no dice on sound. I imagine it is because there aren't drivers on here for the card. This is an Creative Audigy 2 CA0102-IAT. Any help would be awesome. Thanks guys |
|
Quoted:
Ok so I just re-purposed an old XP machine for the garage and there are two problems. Full Disclosure: I haven't used cmd line in a while and was never really adept in the first place and this is the latest version of Ubuntu. Problems: 1. the backlit keyboard doesn't work found this but I have no idea how to create this type of file or edit the properties: "For example in Ubuntu I tried a few things that worked, some that didn't. In the end I settled on this approach: Create file /etc/xdg/autostart/backlight.desktop Edit the file so it looks something like this: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true Ideally I wanted to get the backlight to activate at the login screen (before any user has logged on) but couldn't get it working. The method above turns on the backlight once any user logs in." 2. The speakers do not work. When I plug the speaker wire into the sound card, you can hear the speakers make a little noise, but no dice on sound. I imagine it is because there aren't drivers on here for the card. This is an Creative Audigy 2 CA0102-IAT. Any help would be awesome. Thanks guys For number 1 - In terminal sudo emacs /etc/xdg/autostart/backlight.desktop Copy paste your lines Ctrl-x ctrl-s Ctrl-x ctrl-c Logout and back in and see if it works. Eta for 2 it's been a while since I had to deal with that but just google around to see what some solutions for speakers not working in Ubuntu are. You may be missing drivers for your sound card or there may need to be some workaround. |
|
Quoted: For number 1 - In terminal sudo emacs /etc/xdg/autostart/backlight.desktop Copy paste your lines Ctrl-x ctrl-s Ctrl-x ctrl-c Logout and back in and see if it works. Quoted: Quoted: Ok so I just re-purposed an old XP machine for the garage and there are two problems. Full Disclosure: I haven't used cmd line in a while and was never really adept in the first place and this is the latest version of Ubuntu. Problems: 1. the backlit keyboard doesn't work found this but I have no idea how to create this type of file or edit the properties: "For example in Ubuntu I tried a few things that worked, some that didn't. In the end I settled on this approach: Create file /etc/xdg/autostart/backlight.desktop Edit the file so it looks something like this: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true Ideally I wanted to get the backlight to activate at the login screen (before any user has logged on) but couldn't get it working. The method above turns on the backlight once any user logs in." 2. The speakers do not work. When I plug the speaker wire into the sound card, you can hear the speakers make a little noise, but no dice on sound. I imagine it is because there aren't drivers on here for the card. This is an Creative Audigy 2 CA0102-IAT. Any help would be awesome. Thanks guys For number 1 - In terminal sudo emacs /etc/xdg/autostart/backlight.desktop Copy paste your lines Ctrl-x ctrl-s Ctrl-x ctrl-c Logout and back in and see if it works. vim /etc/xdg/autostart/backlight.desktop
|
|
I haven't had much luck running linux on a notebook, also Ubuntu sucks
Try: sudo gedit /etc/xdg/autostart/backlight.desktop or sudo echo "[Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true ">> /etc/xdg/autostart/backlight.desktop I'm not sure about the ownership or permission on the files though |
|
On the sound:
Simple stuff first. Click on your speaker icon in the toolbar. Make sure the volume is turned up. Does a menu come up that says "Sound Settings"? If not, you may need to right click. In "Output Devices", make sure you have "Speakers" and not "Headphones" selected. Also, open a terminal and type "lspci" without quotes. Copy and paste the output of that message here. We'll see if Ubuntu is finding your sound card. EDIT: Seriously, though, Mint seems to work better for me on almost every computer. If you don't have any luck, I highly recommend it. |
|
Quoted:
Fuck emacs. Use vim. vim /etc/xdg/autostart/backlight.desktop Quoted:
Quoted:
Quoted:
Ok so I just re-purposed an old XP machine for the garage and there are two problems. Full Disclosure: I haven't used cmd line in a while and was never really adept in the first place and this is the latest version of Ubuntu. Problems: 1. the backlit keyboard doesn't work found this but I have no idea how to create this type of file or edit the properties: "For example in Ubuntu I tried a few things that worked, some that didn't. In the end I settled on this approach: Create file /etc/xdg/autostart/backlight.desktop Edit the file so it looks something like this: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true Ideally I wanted to get the backlight to activate at the login screen (before any user has logged on) but couldn't get it working. The method above turns on the backlight once any user logs in." 2. The speakers do not work. When I plug the speaker wire into the sound card, you can hear the speakers make a little noise, but no dice on sound. I imagine it is because there aren't drivers on here for the card. This is an Creative Audigy 2 CA0102-IAT. Any help would be awesome. Thanks guys For number 1 - In terminal sudo emacs /etc/xdg/autostart/backlight.desktop Copy paste your lines Ctrl-x ctrl-s Ctrl-x ctrl-c Logout and back in and see if it works. vim /etc/xdg/autostart/backlight.desktop Fuck vim, I can never remember all the sequences 
I am master of all that is emacs (I use terminal with colors for my sensitive eyes, not that X bullshit  )
|
|
As someone who codes in vim (a newer version of vi), quit telling OP to use vi. emacs isn't much better. He should use gEdit or some other graphical interface.
Also, I think I used to have a box with an audigy 2 card; I don't think I ever got it working in fedora. You may want to try onboard sound if you have it. eta: OP, try typing this at the command prompt to create the file:
|
|
Quoted:
On the sound: Simple stuff first. Click on your speaker icon in the toolbar. Make sure the volume is turned up. Does a menu come up that says "Sound Settings"? If not, you may need to right click. In "Output Devices", make sure you have "Speakers" and not "Headphones" selected. Also, open a terminal and type "lspci" without quotes. Copy and paste the output of that message here. We'll see if Ubuntu is finding your sound card. EDIT: Seriously, though, Mint seems to work better for me on almost every computer. If you don't have any luck, I highly recommend it. on the sound settings window, there isn't an "output devices" section with an option between speakers and headphones; rather only "play sound through" of which "digital output (s/pdif) built-in audio" is selected. No options are muted and sound is turned up all the way. for the "lspci" info: "00:00.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub (rev 02) 00:01.0 PCI bridge: Intel Corporation 82875P Processor to AGP Controller (rev 02) 00:03.0 PCI bridge: Intel Corporation 82875P/E7210 Processor to PCI to CSA Bridge (rev 02) 00:06.0 System peripheral: Intel Corporation 82875P/E7210 Processor to I/O Memory Interface (rev 02) 00:1d.0 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) 00:1d.1 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) 00:1d.2 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) 00:1d.3 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) 00:1d.7 USB controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV360 [Radeon 9600/X1050 Series] 01:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9600/X1050 Series] (Secondary) 02:01.0 Ethernet controller: Intel Corporation 82547EI Gigabit Ethernet Controller 03:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev 80) 03:04.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02) 03:0a.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04) 03:0a.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04) 03:0a.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04) john@Sevier-Johnson:~$ " |
|
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless.
when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? |
|
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? "sudo" is to run the command as root (elevated privileges). If you precede it with "gedit" it will open in a GUI text editor. ex: sudo gedit /etc/xdg/autostart/backlight.desktop |
|
ok this is what I got after trying to run that command:
john@Sevier-Johnson:~$ sudo gedit /etc/xdg/autostart/backlight.desktop [sudo] password for john: (gedit:338): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files |
|
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) So, Ubuntu is recognizing that your card is there. In fact, it looks like there are two: the Audigy and an Intel card. As the other posters said, from the terminal, try "sudo alsamixer" without quotes. When that opens hit "s" and see if your Audigy card is an option there. Use the up and down arrows to highlight it and hit enter to select. |
|
Quoted:
ok this is what I got after trying to run that command: john@Sevier-Johnson:~$ sudo gedit /etc/xdg/autostart/backlight.desktop [sudo] password for john: (gedit:338): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Gedit didn't open? |
|
Quoted: yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? You're not the intended audience.
|
|
Quoted:
"sudo" is to run the command as root (elevated privileges). If you precede it with "gedit" it will open in a GUI text editor. ex: sudo gedit /etc/xdg/autostart/backlight.desktop Quoted:
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? "sudo" is to run the command as root (elevated privileges). If you precede it with "gedit" it will open in a GUI text editor. ex: sudo gedit /etc/xdg/autostart/backlight.desktop a text editor is open, now what? |
|
Once a year for quite a few years I would install Ubuntu to see what they've fixed for me, and what they broke. Each time I'd wipe the install and curse the developers for caring more about how pretty it looks than how it functions. Tried linux mint and loved it. Absolutely no issues and all my hardware worked. |
|
Quoted:
Honestly? I know that everybody and their brother preaches "Linux!!!" like a bunch of evangelists, but - and I'm saying this as somebody who loves Linux - it's misplaced, and I really wish they'd stop. You're not the intended audience. Quoted:
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? You're not the intended audience. I know that, trust me. But for the purpose this will serve and the specs we are dealing with, it makes sense once I get past these few issues. |
|
Quoted: I know that, trust me. But for the purpose this will serve and the specs we are dealing with, it makes sense once I get past these few issues. Quoted: Quoted: Quoted: yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? You're not the intended audience. I know that, trust me. But for the purpose this will serve and the specs we are dealing with, it makes sense once I get past these few issues. |
|
Quoted:
a text editor is open, now what? Quoted:
Quoted:
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? "sudo" is to run the command as root (elevated privileges). If you precede it with "gedit" it will open in a GUI text editor. ex: sudo gedit /etc/xdg/autostart/backlight.desktop a text editor is open, now what? Paste the following into it (from your post above) and save: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true |
|
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? No sudo runs the next command as superuser. So you'd type something like "sudo vi /etc/xdg/autostart/backlight.desktop" (Is look up vi commands before you do. The guy who said you should use a gui text editor was probably right. Posted Via AR15.Com Mobile |
|
Quoted:
Honestly? I know that everybody and their brother preaches "Linux!!!" like a bunch of evangelists, but - and I'm saying this as somebody who loves Linux - it's misplaced, and I really wish they'd stop. You're not the intended audience. Quoted:
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? You're not the intended audience. He has a point here. Posted Via AR15.Com Mobile |
|
Quoted:
So, Ubuntu is recognizing that your card is there. In fact, it looks like there are two: the Audigy and an Intel card. As the other posters said, from the terminal, try "sudo alsamixer" without quotes. When that opens hit "s" and see if your Audigy card is an option there. Use the up and down arrows to highlight it and hit enter to select. Quoted:
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) So, Ubuntu is recognizing that your card is there. In fact, it looks like there are two: the Audigy and an Intel card. As the other posters said, from the terminal, try "sudo alsamixer" without quotes. When that opens hit "s" and see if your Audigy card is an option there. Use the up and down arrows to highlight it and hit enter to select. it is there and I selected it, still no dice on the sound. 
|
|
Quoted:
Paste the following into it (from your post above) and save: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true Quoted:
Quoted:
Quoted:
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? "sudo" is to run the command as root (elevated privileges). If you precede it with "gedit" it will open in a GUI text editor. ex: sudo gedit /etc/xdg/autostart/backlight.desktop a text editor is open, now what? Paste the following into it (from your post above) and save: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true done, will it probably require a restart to work? |
|
Quoted: done, will it probably require a restart to work? Quoted: Quoted: Quoted: Quoted: Quoted: yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? "sudo" is to run the command as root (elevated privileges). If you precede it with "gedit" it will open in a GUI text editor. ex: sudo gedit /etc/xdg/autostart/backlight.desktop a text editor is open, now what? Paste the following into it (from your post above) and save: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true done, will it probably require a restart to work? |
|
Quoted:
More than likely. Quoted:
Quoted:
Quoted:
Quoted:
a text editor is open, now what? Paste the following into it (from your post above) and save: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true done, will it probably require a restart to work? no luck on the keyboard after restart 
|
|
Quoted:
try this: Open a terminal, type "lsmod" and post the output here. This will tell us what drivers are currently loaded. john@Sevier-Johnson:~$ lsmod Module Size Used by ctr 12905 2 ccm 17496 2 bnep 18895 2 rfcomm 53664 0 bluetooth 342263 10 bnep,rfcomm arc4 12536 2 lm63 20812 0 snd_emu10k1_synth 13007 0 ath9k_htc 90038 0 snd_emux_synth 33455 1 snd_emu10k1_synth ath9k_common 13359 1 ath9k_htc ath9k_hw 438205 2 ath9k_common,ath9k_htc snd_seq_midi_emul 13432 1 snd_emux_synth snd_seq_virmidi 13220 1 snd_emux_synth ath 23922 3 ath9k_common,ath9k_htc,ath9k_hw mac80211 545990 1 ath9k_htc radeon 1416373 3 snd_emu10k1 141250 3 snd_emu10k1_synth cfg80211 409394 3 ath,mac80211,ath9k_htc snd_util_mem 13821 2 snd_emux_synth,snd_emu10k1 snd_hwdep 13272 2 snd_emux_synth,snd_emu10k1 snd_intel8x0 33110 2 snd_ac97_codec 105709 2 snd_intel8x0,snd_emu10k1 ac97_bus 12642 1 snd_ac97_codec hid_generic 12492 0 snd_pcm 85501 3 snd_ac97_codec,snd_intel8x0,snd_emu10k1 gpio_ich 13229 0 ttm 72698 1 radeon snd_page_alloc 14230 3 snd_intel8x0,snd_pcm,snd_emu10k1 usbhid 47035 0 snd_seq_midi 13132 0 drm_kms_helper 46907 1 radeon snd_seq_midi_event 14475 2 snd_seq_virmidi,snd_seq_midi snd_rawmidi 25135 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi hid 87604 2 hid_generic,usbhid drm 243792 5 ttm,drm_kms_helper,radeon snd_seq 55383 5 snd_seq_midi_event,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_midi i2c_algo_bit 13197 1 radeon snd_seq_device 14137 5 snd_seq,snd_rawmidi,snd_emu10k1_synth,snd_emu10k1,snd_seq_midi snd_timer 28584 3 snd_pcm,snd_seq,snd_emu10k1 snd 60871 22 snd_ac97_codec,snd_intel8x0,snd_hwdep,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_emu10k1_synth,snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_seq_device,snd_seq_midi_emul,snd_seq_midi emu10k1_gp 12541 0 soundcore 12600 1 snd gameport 15189 2 emu10k1_gp serio_raw 13230 0 lpc_ich 16864 0 shpchp 32128 0 mac_hid 13037 0 parport_pc 31981 1 ppdev 17391 0 lp 13299 0 parport 40836 3 lp,ppdev,parport_pc psmouse 91033 0 firewire_ohci 35529 0 sata_promise 17802 0 firewire_core 61867 1 firewire_ohci crc_itu_t 12627 1 firewire_core floppy 55378 0 e1000 128503 0 john@Sevier-Johnson:~$ edit: thanks again guys, I really appreciate the time and help |
|
Quoted:
no luck on the keyboard after restart Quoted:
Quoted:
Quoted:
Quoted:
Quoted:
a text editor is open, now what? Paste the following into it (from your post above) and save: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true done, will it probably require a restart to work? no luck on the keyboard after restart Run the following command from the terminal, does the backlight turn on? xset led 3 |
|
Quoted:
There will be more. The intended audience (me, for example) looks forward to them. Quoted:
Quoted:
Quoted:
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? You're not the intended audience. I know that, trust me. But for the purpose this will serve and the specs we are dealing with, it makes sense once I get past these few issues. Yep. The "issues"are what makes it fun! |
|
Quoted:
OK... Maybe one more thing to try: In a terminal, type "sudo lshw" This may take a second to run. When it finishes, scroll up and see if it lists your Audigy card as "unclaimed". doesn't appear to be: " *-multimedia description: Multimedia audio controller product: SB Audigy vendor: Creative Labs physical id: a bus info: pci@0000:03:0a.0 version: 04 width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: driver=snd_emu10k1 latency=64 maxlatency=20 mingnt=2 resources: irq:22 ioport:de80(size=64)" |
|
Quoted:
OK good. Try this command in the terminal and then restart your computer: sudo chmod +x /etc/xdg/autostart/backlight.desktop Quoted:
Quoted:
Quoted:
Run the following command from the terminal, does the backlight turn on? xset led 3 yup 
OK good. Try this command in the terminal and then restart your computer: sudo chmod +x /etc/xdg/autostart/backlight.desktop So I ran that, drops to next line with no obvious change in the terminal. Restarted, still nothing automatic |
|
OK.
What could be happening is that Ubuntu is loading the driver for your on board card first and therefore is choosing that as default. Type in "cat /proc/asound/modules" (again, without quotes) It should look something like this: 0 snd_emu10k1 1 snd_intel8x0 but it probably looks like this: 0 snd_intel8x0 1 snd_emu10k1 You want them in the order of the first example. If it doesn't look like either of these, stop here and tell me what's going on. To prevent that Intel from loading first, you have to set the on board Intel driver further down the list of modules to be loaded, so the Audigy card gets loaded first. In a terminal, type "sudo gedit /etc/modprobe.d/alsa-base.conf You'll scroll down and find a bunch of entries that begin with the word "options" Add this entry to them (doesn't matter where in the list, as long as it is in there): options snd_intel8x0 index=-2 This should load the Intel later, after the Audigy is already loaded. If you want, you can mark it for later removal, should it cause problems, by adding this line directly above it: # Modified by (your name) to allow Audigy driver to load (This is not required, but it is a good placeholder so that if you ever go back and need to do further modifications, you know exactly what you've done) When you're happy, save the file, reboot, and test the sound. |
|
Quoted:
Honestly? I know that everybody and their brother preaches "Linux!!!" like a bunch of evangelists, but - and I'm saying this as somebody who loves Linux - it's misplaced, and I really wish they'd stop. You're not the intended audience. Quoted:
Quoted:
yall, imagine that you are teaching this to a bunch of noobs fresh off a lunch break at your local retirement home. I'm about worthless. when I open the terminal and attempt to create a file for the keyboard, is there a command to enter preceding "/etc/xdg/autostart/backlight.desktop"? is that what sudo does? You're not the intended audience. No way, dude. This is gonna be the year of the Linux desktop. |
|
No way, dude. This is gonna be the year of the Linux desktop. Finally! http://www.infoworld.com/d/open-source-software/2014-the-year-of-the-linux-desktop-238358 |
|
Quoted: For number 1 - In terminal sudo emacs /etc/xdg/autostart/backlight.desktop Copy paste your lines Ctrl-x ctrl-s Ctrl-x ctrl-c Logout and back in and see if it works. Eta for 2 it's been a while since I had to deal with that but just google around to see what some solutions for speakers not working in Ubuntu are. You may be missing drivers for your sound card or there may need to be some workaround. Quoted: Quoted: Ok so I just re-purposed an old XP machine for the garage and there are two problems. Full Disclosure: I haven't used cmd line in a while and was never really adept in the first place and this is the latest version of Ubuntu. Problems: 1. the backlit keyboard doesn't work found this but I have no idea how to create this type of file or edit the properties: "For example in Ubuntu I tried a few things that worked, some that didn't. In the end I settled on this approach: Create file /etc/xdg/autostart/backlight.desktop Edit the file so it looks something like this: [Desktop Entry] Type=Application Name=Devastator Backlight Exec=xset led 3 Icon=system-run X-GNOME-Autostart-enabled=true Ideally I wanted to get the backlight to activate at the login screen (before any user has logged on) but couldn't get it working. The method above turns on the backlight once any user logs in." 2. The speakers do not work. When I plug the speaker wire into the sound card, you can hear the speakers make a little noise, but no dice on sound. I imagine it is because there aren't drivers on here for the card. This is an Creative Audigy 2 CA0102-IAT. Any help would be awesome. Thanks guys For number 1 - In terminal sudo emacs /etc/xdg/autostart/backlight.desktop Copy paste your lines Ctrl-x ctrl-s Ctrl-x ctrl-c Logout and back in and see if it works. Eta for 2 it's been a while since I had to deal with that but just google around to see what some solutions for speakers not working in Ubuntu are. You may be missing drivers for your sound card or there may need to be some workaround. emacs? he's fucked lol |
|
Quoted:
OK. What could be happening is that Ubuntu is loading the driver for your on board card first and therefore is choosing that as default. Type in "cat /proc/asound/modules" (again, without quotes) It should look something like this: 0 snd_emu10k1 1 snd_intel8x0 but it probably looks like this: 0 snd_intel8x0 1 snd_emu10k1 You want them in the order of the first example. If it doesn't look like either of these, stop here and tell me what's going on. To prevent that Intel from loading first, you have to set the on board Intel driver further down the list of modules to be loaded, so the Audigy card gets loaded first. In a terminal, type "sudo gedit /etc/modprobe.d/alsa-base.conf You'll scroll down and find a bunch of entries that begin with the word "options" Add this entry to them (doesn't matter where in the list, as long as it is in there): options snd_intel8x0 index=-2 This should load the Intel later, after the Audigy is already loaded. If you want, you can mark it for later removal, should it cause problems, by adding this line directly above it: # Modified by (your name) to allow Audigy driver to load (This is not required, but it is a good placeholder so that if you ever go back and need to do further modifications, you know exactly what you've done) When you're happy, save the file, reboot, and test the sound. It was in the wrong order like you thought it would be. Added your line to the options, pasting this result from the terminal before I restart the machine now 0 snd_intel8x0 1 snd_emu10k1 john@Sevier-Johnson:~$ sudo gedit /etc/modprobe.d/alsa-base.conf [sudo] password for john: (gedit:3157): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (gedit:3157): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files |
