I was running 8.2 on an old Micron Millenia 500 and everything was fine, albeit a little slow considering not only the processor but the 256M memory limitation. I had an external hard drive using the Lava Firewire to IDE controller. (http://www.racoindustries.com/lavafwidecontr.htm) Since I couldn't add memory, I decided to upgrade the memory board. I slipped in a Biostar M7NCD with an AMD Sempron 3000 and a gig of ram. I replaced all the old drives and everything was working fine. In fact, I was so encouraged by the performance that I decided to upgrade to Suse 9.1, which I have been running on my laptop but never put on this old desktop because of the lack of memory. Well the 9.1 installation went fine and I've been able to get everything working but the external drive connected via the above controller. Here's what I've been able to figure out: My internal firewire controller is working and recognized by linux. When I plug in an external LaCie drive, KDE auto-recognizes and linux recognizes the LaCie as /dev/sda, just what I would expect. I plugged the Lava external controller with harddrive into a windows machine, and windows recognized (at least the vfat partition). so I know that the controller, cables and drive are all working. Then I decided to try the Lava controller on my laptop, also running 9.1. It does not recognize the drive. so I say "aha!" this would seem to be a problem with 9.1. My questions are: Is there a fix? Any suggestions on trouble shooting? Would 9.2 "cure" this problem? Any other ideas?
On Saturday 26 March 2005 11:10 am, Paul Grope wrote:
I was running 8.2 on an old Micron Millenia 500 and everything was fine, albeit a little slow considering not only the processor but the 256M memory limitation.
I had an external hard drive using the Lava Firewire to IDE controller.
(http://www.racoindustries.com/lavafwidecontr.htm) [...] so I say "aha!" this would seem to be a problem with 9.1.
My questions are:
Is there a fix?
Any suggestions on trouble shooting?
Would 9.2 "cure" this problem?
Any other ideas?
If you're not averse to building a new kernel (or just modules), I'd suggest getting either 1) the latest kernel or 2) the latest 1394 stuff from http://www.linux1394.org/ (which won't build without the latest kernel - so I guess that's not an either/or). There have been lots o' changes in the 1394 stuff, and all of the features from 2.4 didn't make it into the 2.6 drivers immediately. So, when you switched from a 2.4-based distro to an early 2.6-based distro, you likely actually moved to less featured drivers. If moving to 9.2 is what it takes to get a newer kernel, that may fix it. All you really need, though, is a newer kernel. Probably. --Danny, who just yesterday finally got a multi-bay enclosure to work on a PPC Linux box, and it took the svn 1394 sources with 2.6.bleeding-edge to do it.
On Saturday 26 March 2005 08:10 am, Paul Grope wrote:
Then I decided to try the Lava controller on my laptop, also running 9.1. It does not recognize the drive.
so I say "aha!" this would seem to be a problem with 9.1.
Make sure that hotplug is enabled. (Bet you did that already). Then tail your /var/log/messages while you plug in the drive. Often, if you have a lot of devices, the new device will appear on scsi bus 2 and SuSE scans only scsi bus 0 and 1 by default. If you find that it is showing up on scsi bus 2 or higher, you can as root run this command echo "scsi add-single-device 2 0 0 0" > /proc/scsi/scsi (replacing that 2 with the buss number gleaned from tailing messages). Then run rescan-scsi-bus.sh 2 (again with the two parm). Perhaps someone knowing a lot more about scsi than I can find a way to tell SuSE to always scan more than two busses. I have to do this with my 8.2 firewire disk all the time. Earlier distros of SuSE also had a specific option in /etc/sysconfig/hotplug to enable/disable firewire, but I see this is no longer there in 9.1 -- _____________________________________ John Andersen
Could anyone please email me an ftp 'if one exists' so that I can update my KDE using that as an install source through YaST. Thanks in advance. Also, what to type into the source box would be helpful, I have tried the ftp.kde.org ones and it errors saying that it is missing an install file or something, maybe I am not doing it right.... not sure. Thanks Made with__________________________________________ Linux 2.6.8-24.13-default #1 x86 64 GNU/Linux (SuSE 9.2) William Westfall wgwestfall1@msn.com
On Sat, 2005-03-26 at 16:17 -0700, WILLIAM WESTFALL wrote:
Could anyone please email me an ftp 'if one exists' so that I can update my KDE using that as an install source through YaST. Thanks in advance.
Also, what to type into the source box would be helpful, I have tried the ftp.kde.org ones and it errors saying that it is missing an install file or something, maybe I am not doing it right.... not sure.
Thanks
In the install source select new ftp source. Add the following: ftp.ale.org (actually should be your closest mirror) pub/suse/i386/supplementary/KDE/update_for_9.2/yast-source as the dir Adjust for your SuSE version this is for 9.2. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sat, 26 Mar 2005 18:51:49 -0500, Ken Schneider
On Sat, 2005-03-26 at 16:17 -0700, WILLIAM WESTFALL wrote:
Could anyone please email me an ftp 'if one exists' so that I can update my KDE using that as an install source through YaST. Thanks in advance.
Also, what to type into the source box would be helpful, I have tried the ftp.kde.org ones and it errors saying that it is missing an install file or something, maybe I am not doing it right.... not sure.
Thanks
In the install source select new ftp source. Add the following:
ftp.ale.org (actually should be your closest mirror) pub/suse/i386/supplementary/KDE/update_for_9.2/yast-source as the dir
Adjust for your SuSE version this is for 9.2.
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
* Only reply to the list please*
"The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Anybody noticed that akregator, bookcase and qmatplot are missed?, the links exists, but not the real files lrwxrwxrwx 1 root root 52 2005-03-23 01:12 akregator.rpm -> ../../../applications/akregator-1.0_beta8-5.i586.rpm lrwxrwxrwx 1 root root 46 2005-03-23 01:12 bookcase.rpm -> ../../../applications/bookcase-0.11-3.i586.rpm lrwxrwxrwx 1 root root 49 2005-03-23 01:12 qmatplot.rpm -> ../../../applications/qmatplot-0.4.2-297.i586.rpm CI.-
Here's an update:
I updated the kernal to 2.6 something using the online update feature,
but that made no difference.
John may be on to something. I took a look at my message log and
although it doesn't seem to be a bus problem there is interesting
information that obviously means something, it just doesn't mean a lot
to me. I'll be googling and looking for other help in figuring out
what this means, and in the meantime, maybe somebody more expert than
I can point me to the right place:
Here is the log:
Mar 26 16:58:50 notebook kernel: ieee1394: Node added:
ID:BUS[0-00:1023] GUID[0030e00000000d1b]
Mar 26 16:58:50 notebook /sbin/hotplug[8383]:
/etc/hotplug/ieee1394.agent: line 22: VENDOR_ID: Bad invocation:
$VENDOR_ID is not set
Mar 26 16:58:50 notebook kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023
Mar 26 16:58:50 notebook /sbin/hotplug[8402]:
/etc/hotplug/ieee1394.agent: line 22: VENDOR_ID: Bad invocation:
$VENDOR_ID is not set
Mar 26 16:58:50 notebook /sbin/hotplug[8404]:
/etc/hotplug/ieee1394.agent: line 22: VENDOR_ID: Bad invocation:
$VENDOR_ID is not set
Mar 26 16:58:55 notebook /etc/hotplug/ieee1394.agent[8403]: ... no
drivers for IEEE1394 product 0x000000/0x000000/0x000000
Mar 26 16:58:55 notebook kernel: sbp2: $Rev: 1205 $ Ben Collins
On Saturday 26 March 2005 08:10 am, Paul Grope wrote:
Then I decided to try the Lava controller on my laptop, also running 9.1. It does not recognize the drive.
so I say "aha!" this would seem to be a problem with 9.1.
Make sure that hotplug is enabled. (Bet you did that already). Then tail your /var/log/messages while you plug in the drive. Often, if you have a lot of devices, the new device will appear on scsi bus 2 and SuSE scans only scsi bus 0 and 1 by default.
If you find that it is showing up on scsi bus 2 or higher, you can as root run this command echo "scsi add-single-device 2 0 0 0" > /proc/scsi/scsi (replacing that 2 with the buss number gleaned from tailing messages).
Then run rescan-scsi-bus.sh 2 (again with the two parm).
Perhaps someone knowing a lot more about scsi than I can find a way to tell SuSE to always scan more than two busses.
I have to do this with my 8.2 firewire disk all the time. Earlier distros of SuSE also had a specific option in /etc/sysconfig/hotplug to enable/disable firewire, but I see this is no longer there in 9.1
-- _____________________________________ John Andersen
participants (6)
-
Ciro Iriarte
-
Danny Sauer
-
John Andersen
-
Ken Schneider
-
Paul Grope
-
WILLIAM WESTFALL