FW: [SLE] Weeping, Sorrow, Sadness, Tears.... the Beast is deathl y ill.
Forgot to CC the list........ Mike ------------------------------------------------------- Cleary_Mike@emc.com x6033 ------------------------------------------------------- We are born naked, wet, and hungry. Then things get worse. -----Original Message----- From: Cleary, Mike Sent: Friday, March 16, 2001 2:18 PM To: 'Jerry Kreps' Subject: RE: [SLE] Weeping, Sorrow, Sadness, Tears.... the Beast is deathly ill. I ran into almost exactly the same problem last night. But I thought it was all because of something stupid I did. Here's what happened: When trying to build a kernel I ran into all kinds of problems - I ended up not being able to boot the machine ( I won't go into that now). So I got mad and reinstalled 7.1. When I first installed I had sound. Then I upgraded to KDE 2.1 and for some reason all sound was lost. Using Yast2 I attempted to reconfigure the soundcard - removed it and added it back in. At this point, the "test" button would produce no sound. So last night I reinstalled again and Yast2 correctly configured the card & I got sound back. Now, I had been trying to get my joystick to work w/ my Soundblaster Live card. I noticed last night in the "configuration" manual that I needed to initialize the gameport using the emu10k1 joystick module. I mistakenly thought that I needed to install a package called emu10k1-joy. There is no such package I found out later. Anyway, I was in Yast1 upgrading to KDE 2.1 & I looked for this package in the snd series. All I found was the emu10k1 package which was shown as NOT being installed. I thought that this was odd since Yast2 said it was using the emu10k1 driver. So I thought I would go ahead and install it & then try to get the joystick going. Stupid, stupid, stupid..... It broke everything. Here's where I had the same problem you ran into: When I rebooted I got all kinds of modprobe errors on sound stuff, and I also got the usbmgr service failure. Also, X would not start at all, and sax2 kept failing (would not start). I finally managed to get sax2 to work and got X started. Of course I had no sound. I tried to use Yast2 to configure the card, but it would not - kept giving me an error about loading the emu10k1 driver. So I then went into Yast1 and removed the emu10k1 package I had installed. Yast2 would then configure the card, but once again, NO SOUND when using even the "test" button!!! No matter what I do, I cannot get sound back now. Unless someone has a fix, I guess I'll be reinstalling again..........:( Mike ------------------------------------------------------- Cleary_Mike@emc.com x6033 ------------------------------------------------------- We are born naked, wet, and hungry. Then things get worse. -----Original Message----- From: Jerry Kreps [mailto:jerrykreps@jlkreps.net] Sent: Thursday, March 15, 2001 10:39 PM To: SLE Subject: [SLE] Weeping, Sorrow, Sadness, Tears.... the Beast is deathly ill. I had it running beautifully Tues night. Spent the last hour Tuesday listing to some of my music CD's through that faboulous SB sound system. I powered down Tues night because I wanted to plug in some cables and add a hub to help connect this machine (the Sony) to the Beast. This evening (Thur) I hooked up the cable (Just plugged it into the eth0 card) and the EN104 hub and turned everything on. Durning the boot process I noticed that I got an ATPI CDROM error but my PlexStor CD-RW seems to be identified and working ok. Kscd makes the CD go round even if sound doesn't come out. Also I was getting a modprobe error on the sound stuff, ... then a usbmgr service failed (I don't use usb and didn't activate it. SuSE must have.) and a msg flew by saying it couldn't configure the eth0 card. I logged on as root and fired YaST2 in the console. Then I reconfigured the sound. It wouldn't offer me the actual card (SB PCI512), just SB16, SB 1.2 + Pro, and SB AWE, none of which make my sound card work. But, if I run YaST2 in KDE2 the correct sound card identity is auto-matically chosen. Why is that SuSE? The bad news is that even though it finds the card, no sound come out during the test. And, I can't fire the sound mixer because the sound card hasn't been installed yet. I rebooted the machine and am running the memtest. It may be time to call my vendor. JLK -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Deja Vue, all over again! I swear we are working on the same machine. So, last night I reinstalled again. It clearned up eveything except the shimmering on my desktop. So, since I needed to get my wheel mouse running, I followed the wheeel mouse install proceedure found on the SuSE support site. In the process I reinstalled my Xserver and downgraded the size to 1240X780. The shimmer went away, eveything is a LOT more crispy, and when I drap the corner of an xterm it doesn't blow me out of KDE back to the console. The CD player and SB PCI512 work nicely to give faboulous sound. An 18 watt woofer really makes the last base thump at the end of the 'Windows Open" music a real chest thumper. So, the Beast is healhy again! Now, all I have to do is get the Beast and the Sony to talk together. They can ping each other but I still can browse the Internet via the Sony and the ADSL. I'm looking int IP Masqs. JLK On Friday 16 March 2001 13:19, you wrote:
Forgot to CC the list........
Mike ------------------------------------------------------- Cleary_Mike@emc.com x6033 ------------------------------------------------------- We are born naked, wet, and hungry. Then things get worse.
-----Original Message----- From: Cleary, Mike Sent: Friday, March 16, 2001 2:18 PM To: 'Jerry Kreps' Subject: RE: [SLE] Weeping, Sorrow, Sadness, Tears.... the Beast is deathly ill.
I ran into almost exactly the same problem last night. But I thought it was all because of something stupid I did. Here's what happened: When trying to build a kernel I ran into all kinds of problems - I ended up not being able to boot the machine ( I won't go into that now). So I got mad and reinstalled 7.1. When I first installed I had sound. Then I upgraded to KDE 2.1 and for some reason all sound was lost. Using Yast2 I attempted to reconfigure the soundcard - removed it and added it back in. At this point, the "test" button would produce no sound. So last night I reinstalled again and Yast2 correctly configured the card & I got sound back. Now, I had been trying to get my joystick to work w/ my Soundblaster Live card. I noticed last night in the "configuration" manual that I needed to initialize the gameport using the emu10k1 joystick module. I mistakenly thought that I needed to install a package called emu10k1-joy. There is no such package I found out later. Anyway, I was in Yast1 upgrading to KDE 2.1 & I looked for this package in the snd series. All I found was the emu10k1 package which was shown as NOT being installed. I thought that this was odd since Yast2 said it was using the emu10k1 driver. So I thought I would go ahead and install it & then try to get the joystick going. Stupid, stupid, stupid..... It broke everything. Here's where I had the same problem you ran into: When I rebooted I got all kinds of modprobe errors on sound stuff, and I also got the usbmgr service failure. Also, X would not start at all, and sax2 kept failing (would not start). I finally managed to get sax2 to work and got X started. Of course I had no sound. I tried to use Yast2 to configure the card, but it would not - kept giving me an error about loading the emu10k1 driver. So I then went into Yast1 and removed the emu10k1 package I had installed. Yast2 would then configure the card, but once again, NO SOUND when using even the "test" button!!! No matter what I do, I cannot get sound back now. Unless someone has a fix, I guess I'll be reinstalling again..........:( Mike ------------------------------------------------------- Cleary_Mike@emc.com x6033 ------------------------------------------------------- We are born naked, wet, and hungry. Then things get worse. -----Original Message----- From: Jerry Kreps [mailto:jerrykreps@jlkreps.net] Sent: Thursday, March 15, 2001 10:39 PM To: SLE Subject: [SLE] Weeping, Sorrow, Sadness, Tears.... the Beast is deathly ill.
I had it running beautifully Tues night. Spent the last hour Tuesday listing to some of my music CD's through that faboulous SB sound system. I powered down Tues night because I wanted to plug in some cables and add a hub to help connect this machine (the Sony) to the Beast. This evening (Thur) I hooked up the cable (Just plugged it into the eth0 card) and the EN104 hub and turned everything on. Durning the boot process I noticed that I got an ATPI CDROM error but my PlexStor CD-RW seems to be identified and working ok. Kscd makes the CD go round even if sound doesn't come out. Also I was getting a modprobe error on the sound stuff, ... then a usbmgr service failed (I don't use usb and didn't activate it. SuSE must have.) and a msg flew by saying it couldn't configure the eth0 card. I logged on as root and fired YaST2 in the console. Then I reconfigured the sound. It wouldn't offer me the actual card (SB PCI512), just SB16, SB 1.2 + Pro, and SB AWE, none of which make my sound card work. But, if I run YaST2 in KDE2 the correct sound card identity is auto-matically chosen. Why is that SuSE? The bad news is that even though it finds the card, no sound come out during the test. And, I can't fire the sound mixer because the sound card hasn't been installed yet. I rebooted the machine and am running the memtest. It may be time to call my vendor. JLK
---------------------------------------- Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: quoted-printable Content-Description: ----------------------------------------
Jerry Kreps on Saturday, March 17, 2001
Now, all I have to do is get the Beast and the Sony to talk together. They can ping each other but I still can browse the Internet via the Sony and the ADSL. I'm looking int
Dear Jerry, Here is a quick solution that Chris Reeves gave me a couple of weeks ago under the thread "Accessing net through LAN - Choices [was PCMCIA MODEM]" <snip> Here are some quick and easy steps. On your laptop (as root): route add default gw <ip address of old pc> You'll also have to set up your /etc/resolv.conf with the IP addresses of your ISP's DNS servers (so that it looks the same as the one on the old PC when it's connected). On your old PC (as root): echo 1 > /proc/sys/net/ipv4/ip_forward ipchains -P forward MASQ This does assume you have a basic network set up such that you can ping each computer from the other. If you don't, and need a hand, let us know and someone will help. Remember, this setup is *not* secure. Hope that helps Chris </snip> It worked for me. Jethro
mmmm... Doesn't seem to work: root@JLKreps:/home/jerry > /sbin/ipchains -P forward MASQ ipchains: Protocol not available The -help doesn't seem to know about 'forward' or 'MASQ' ??? JLK On Friday 16 March 2001 22:33, Jethro Cramp wrote:
Jerry Kreps on Saturday, March 17, 2001
Now, all I have to do is get the Beast and the Sony to talk together. They can ping each other but I still can browse the Internet via the Sony and the ADSL. I'm looking int
Dear Jerry,
Here is a quick solution that Chris Reeves gave me a couple of weeks ago under the thread "Accessing net through LAN - Choices [was PCMCIA MODEM]"
<snip> Here are some quick and easy steps.
On your laptop (as root): route add default gw <ip address of old pc> You'll also have to set up your /etc/resolv.conf with the IP addresses of your ISP's DNS servers (so that it looks the same as the one on the old PC when it's connected).
On your old PC (as root): echo 1 > /proc/sys/net/ipv4/ip_forward ipchains -P forward MASQ
This does assume you have a basic network set up such that you can ping each computer from the other. If you don't, and need a hand, let us know and someone will help.
Remember, this setup is *not* secure.
Hope that helps Chris
</snip>
It worked for me.
Jethro
Hi Jerry, Are you sure IP_FORWARD is enabled in rc.config on Sony ? (try to look it up with yast1) I recommend to set up SuSE firewall. A lot is explained in there. I have a little home network ( 192.168.0.1 --- 192.168.0.14 ) and I remember before setting up the firewall (last september with suse7.0 HEY!!!! that box is up since september !!!!) I use to do : ipchains -A forward -s 192.168.0.0/16 -b -j MASQ Hope this helps, Filip. Le Samedi 17 Mars 2001 07:22, Jerry Kreps a écrit :
mmmm... Doesn't seem to work:
root@JLKreps:/home/jerry > /sbin/ipchains -P forward MASQ ipchains: Protocol not available
The -help doesn't seem to know about 'forward' or 'MASQ' ??? JLK
On Friday 16 March 2001 22:33, Jethro Cramp wrote:
Jerry Kreps on Saturday, March 17, 2001
Now, all I have to do is get the Beast and the Sony to talk together. They can ping each other but I still can browse the Internet via the Sony and the ADSL. I'm looking int
Dear Jerry,
Here is a quick solution that Chris Reeves gave me a couple of weeks ago under the thread "Accessing net through LAN - Choices [was PCMCIA MODEM]"
<snip> Here are some quick and easy steps.
On your laptop (as root): route add default gw <ip address of old pc> You'll also have to set up your /etc/resolv.conf with the IP addresses of your ISP's DNS servers (so that it looks the same as the one on the old PC when it's connected).
On your old PC (as root): echo 1 > /proc/sys/net/ipv4/ip_forward ipchains -P forward MASQ
This does assume you have a basic network set up such that you can ping each computer from the other. If you don't, and need a hand, let us know and someone will help.
Remember, this setup is *not* secure.
Hope that helps Chris
</snip>
It worked for me.
Jethro
On Saturday 17 March 2001 03:08, you wrote:
Hi Jerry,
Are you sure IP_FORWARD is enabled in rc.config on Sony ?
It is set, along with several other IP options. See below. Not only that, any use of the ipchains command gives a 'protocol not available' message. After seeing the mod list I tried to modprob several of them that I found in /lib/modules/2.2.15/ipv4 but they all failed for various reasons. Here are the list of available modules: root@JLKreps:/home/jerry > vdir /lib/modules/2.2.18/ipv4 total 88 -rw-r--r-- 1 root root 9452 Jan 24 07:12 ip_gre.o -rw-r--r-- 1 root root 4784 Jan 24 07:12 ip_masq_autofw.o -rw-r--r-- 1 root root 2656 Jan 24 07:12 ip_masq_cuseeme.o -rw-r--r-- 1 root root 6412 Jan 24 07:12 ip_masq_ftp.o -rw-r--r-- 1 root root 4024 Jan 24 07:12 ip_masq_irc.o -rw-r--r-- 1 root root 6340 Jan 24 07:12 ip_masq_mfw.o -rw-r--r-- 1 root root 4776 Jan 24 07:12 ip_masq_portfw.o -rw-r--r-- 1 root root 3192 Jan 24 07:12 ip_masq_quake.o -rw-r--r-- 1 root root 5208 Jan 24 07:12 ip_masq_raudio.o -rw-r--r-- 1 root root 5048 Jan 24 07:12 ip_masq_user.o -rw-r--r-- 1 root root 3016 Jan 24 07:12 ip_masq_vdolive.o -rw-r--r-- 1 root root 8540 Jan 24 07:12 ipip.o root@JLKreps:/home/jerry > modprobe ip_masq_user modprobe: Invalid line 210 in /etc/modules.conf snd_device_gid modprobe: Invalid line 233 in /etc/modules.conf snd_dma1 modprobe: Invalid line 242 in /etc/modules.conf amixer modprobe: Invalid line 285 in /etc/modules.conf isp16_cdrom_dma modprobe: Invalid line 325 in /etc/modules.conf /sbin/modprobe root@JLKreps:/home/jerry > modprobe ip_masq_autofw modprobe: Invalid line 210 in /etc/modules.conf snd_device_gid modprobe: Invalid line 233 in /etc/modules.conf s nd_dma1 modprobe: Invalid line 242 in /etc/modules.conf amixer modprobe: Invalid line 285 in /etc/modules.conf isp16_cdrom_dma modprobe: Invalid line 325 in /etc/modules.conf /sbin/modprobe root@JLKreps:/home/jerry > Here are the settings in /boot/vmlinuz.config: # # Networking options # CONFIG_PACKET=y CONFIG_NETLINK=y CONFIG_RTNETLINK=y CONFIG_NETLINK_DEV=y CONFIG_FIREWALL=y CONFIG_FILTER=y CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_RTNETLINK=y CONFIG_NETLINK=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_MULTIPATH=y CONFIG_IP_ROUTE_TOS=y CONFIG_IP_ROUTE_VERBOSE=y # CONFIG_IP_ROUTE_LARGE_TABLES is not set CONFIG_IP_ROUTE_NAT=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_IP_PNP_RARP=y CONFIG_IP_FIREWALL=y CONFIG_IP_FIREWALL_NETLINK=y CONFIG_NETLINK_DEV=y CONFIG_IP_ROUTE_FWMARK=y CONFIG_IP_TRANSPARENT_PROXY=y CONFIG_IP_MASQUERADE=y # # Protocol-specific masquerading support will be built as modules. # CONFIG_IP_MASQUERADE_ICMP=y # # Protocol-specific masquerading support will be built as modules. # CONFIG_IP_MASQUERADE_MOD=y CONFIG_IP_MASQUERADE_IPAUTOFW=m CONFIG_IP_MASQUERADE_IPPORTFW=m CONFIG_IP_MASQUERADE_MFW=m I'm stumped, but at 60 yrs old that is getting easier and easier to do. :-) JLK
(try to look it up with yast1) I recommend to set up SuSE firewall. A lot is explained in there. I have a little home network ( 192.168.0.1 --- 192.168.0.14 ) and I remember before setting up the firewall (last september with suse7.0 HEY!!!! that box is up since september !!!!) I use to do : ipchains -A forward -s 192.168.0.0/16 -b -j MASQ Hope this helps, Filip.
Le Samedi 17 Mars 2001 07:22, Jerry Kreps a écrit :
mmmm... Doesn't seem to work:
root@JLKreps:/home/jerry > /sbin/ipchains -P forward MASQ ipchains: Protocol not available
The -help doesn't seem to know about 'forward' or 'MASQ' ??? JLK
On Friday 16 March 2001 22:33, Jethro Cramp wrote:
Jerry Kreps on Saturday, March 17, 2001
Now, all I have to do is get the Beast and the Sony to talk together. They can ping each other but I still can browse the Internet via the Sony and the ADSL. I'm looking int
Dear Jerry,
Here is a quick solution that Chris Reeves gave me a couple of weeks ago under the thread "Accessing net through LAN - Choices [was PCMCIA MODEM]"
<snip> Here are some quick and easy steps.
On your laptop (as root): route add default gw <ip address of old pc> You'll also have to set up your /etc/resolv.conf with the IP addresses of your ISP's DNS servers (so that it looks the same as the one on the old PC when it's connected).
On your old PC (as root): echo 1 > /proc/sys/net/ipv4/ip_forward ipchains -P forward MASQ
This does assume you have a basic network set up such that you can ping each computer from the other. If you don't, and need a hand, let us know and someone will help.
Remember, this setup is *not* secure.
Hope that helps Chris
</snip>
It worked for me.
Jethro
FYI, It was another one of those bad Xserver config problems. Now the Beast appears to be as stable as a rock. All of my favorite apps are loading in easier than ever! JOY! JLK
Congratulations Jerry! On Saturday 17 March 2001 08:26, you wrote:
FYI, It was another one of those bad Xserver config problems.
Now the Beast appears to be as stable as a rock. All of my favorite apps are loading in easier than ever! JOY! JLK
Hi Jerry, Have Fun, HAVE FUN, Jerry !!! filip Le Samedi 17 Mars 2001 17:26, Jerry Kreps a écrit :
FYI, It was another one of those bad Xserver config problems.
Now the Beast appears to be as stable as a rock. All of my favorite apps are loading in easier than ever! JOY! JLK
participants (5)
-
Cleary, Mike
-
filip
-
Jerry Kreps
-
Jerry Van Brimmer
-
Jethro Cramp