Re: Serious New Install problem
On 13/01/10 21:09, Troy Dawson wrote: >> >> What we are planning to do till we can get this sorted out is to >> install Open Suse 9.3 as 10.3 screwed up with LVM trash. >> >> Larry Linder If you do go down the Opensuse route the current version is 11.2 and it works quite nicely, even presents you the option of partitioned-based disk layout or LVM-based in the installer (you can choose to completely customise it too). 9.3 was end-of-life nearly 2.5 years ago and 10.3 is also discontinued. http://en.opensuse.org/SUSE_Linux_Lifetime Good luck Tim Edwards
problem and question
Hi,
My problem:
up to now I am still using ipw3845 driver, no look to the fact, that this
one is obsolete, and people use iwl3945. Of course I can able to use both
drivers,
but the wireless situation is not stable now, time to time I am out from wi-fi
connection (seems to randomly).
My present kernel is 2.6.18-164.10.1.el5. When I booting all is ok.,
after some time (randomly) no. The dmesg gave nothing, in really to
restart wi-fi I must to switch-off and switch-on wi-fi hard key.
I think, that the problem can be connect with iwl3945 behaviour and maybe
some crashing with ipw3945, I do not know...
Unfortunately I cannot make rmmod for iwl... drivers if I use ipw3945, and
from another side, if I do not use ipw3945, my using iwl... is still not
stable.
I have Toshiba, Qosmio, G30-155.
Can you look no this problem, please?
I asked Akima Yagi already and he proposed me to make firstly:
for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1
for cmdsubst> }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n;
done
02:00.0 "Ethernet controller" "Intel Corporation" "82573L Gigabit Ethernet
Controller" "Toshiba America Info Systems" "Unknown device 0001"
02:00.0 0200: 8086:109a
05:00.0 "Network controller" "Intel Corporation" "PRO/Wireless 3945ABG
[Golan] Network Connection" -r02 "Intel Corporation" "Unknown device 1041"
05:00.0 0280: 8086:4222 (rev 02)
Regards,
Dusan
Re: dbus and a broken pipe - solved
Hi all I recently posted the following query on this list > I'm running a freshly installed sl51 and on login get a very annoying > message from the gnome-settings-manager about being unable to > contact to socket: /tmp/dbus-kjsdfhjd : connection refused. > : but had no replies -- I post a solution for the sake of the archive. Further research on Google revealed that this problem can be caused by an old bug in dbus, which introduced a race condition on pipes being closed at the time a process wanted to write to them. I tried to update dbus within SL51 but found a cascade of dependencies made this "too interesting" to follow through. A clean install of SL54 on the same hardware (and with the same corporate setup) fixes the problem for me. Cheers Jim -- J.J. Green, Seaview Sensing Ltd., http://seaviewsensing.com/
Serious New Install Problem - 2
We had the same problem on a test box micro atx board with dual core & 2 G Ram when we first installed it. We were doing a few more test and now the 64 bit system works and I can add users with the GUI and it gets done correctly and works. There is a problem with a new rewrite for the login checking script. I found it listed as in BugZilla. Will send you the bug report tomorrow Don't plan to give up on SL is the long term answer to our OS issues. -The only thing I will miss is the neat maintence scheme Open Suse has. Larry Linder
Re: problem and question
On Thu, Jan 14, 2010 at 5:38 AM, Dusan Bruncko wrote:
> Hi,
>
> My problem:
> up to now I am still using ipw3845 driver, no look to the fact, that this
> one is obsolete, and people use iwl3945. Of course I can able to use both
> drivers,
> but the wireless situation is not stable now, time to time I am out from
> wi-fi
> connection (seems to randomly).
> My present kernel is 2.6.18-164.10.1.el5. When I booting all is ok., after
> some time (randomly) no. The dmesg gave nothing, in really to restart wi-fi
> I must to switch-off and switch-on wi-fi hard key. I think, that the problem
> can be connect with iwl3945 behaviour and maybe some crashing with ipw3945,
> I do not know...
> Unfortunately I cannot make rmmod for iwl... drivers if I use ipw3945, and
> from another side, if I do not use ipw3945, my using iwl... is still not
> stable.
> I have Toshiba, Qosmio, G30-155.
>
> Can you look no this problem, please?
>
> I asked Akima Yagi already and he proposed me to make firstly:
>
> for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1
> for cmdsubst> }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n;
> done
> 02:00.0 "Ethernet controller" "Intel Corporation" "82573L Gigabit Ethernet
> Controller" "Toshiba America Info Systems" "Unknown device 0001"
> 02:00.0 0200: 8086:109a
> 05:00.0 "Network controller" "Intel Corporation" "PRO/Wireless 3945ABG
> [Golan] Network Connection" -r02 "Intel Corporation" "Unknown device 1041"
> 05:00.0 0280: 8086:4222 (rev 02)
That information confirms that the e1000e and iwl3945 drivers should
be used with the
2.6.18-164.10.1.el5 kernel (quoting Alan).
This is how you find this out: go to the ELRepo FAQ page at
http://elrepo.org/tiki/FAQ .
FAQ Number 4 provides a detailed description on how to identify the
driver through the Vendor:Device ID pair. In your case, it is
8086:109a for the ethernet controller and 8086:4222 for the wireless
device.
The command:
grep -i 8086 /lib/modules/*/modules.alias | grep -i 109a
returns (among other things)
/lib/modules/2.6.18-164.10.1.el5/modules.alias:alias
pci:v8086d109Asv*sd*bc*sc*i* e1000e
Likewise, the other pair gives you iwl3945.
I realize you have [tried] both ipw3945 and iwl3945. Now that you are
running the current kernel, I think you should use iwl3945. Make sure
you have the correct firmware installed.
Akemi
Re: problem and question
Akemi Yagi wrote:
On Thu, Jan 14, 2010 at 5:38 AM, Dusan Bruncko wrote:
Hi,
My problem:
up to now I am still using ipw3845 driver, no look to the fact, that this
one is obsolete, and people use iwl3945. Of course I can able to use both
drivers,
but the wireless situation is not stable now, time to time I am out from
wi-fi
connection (seems to randomly).
My present kernel is 2.6.18-164.10.1.el5. When I booting all is ok., after
some time (randomly) no. The dmesg gave nothing, in really to restart wi-fi
I must to switch-off and switch-on wi-fi hard key. I think, that the problem
can be connect with iwl3945 behaviour and maybe some crashing with ipw3945,
I do not know...
Unfortunately I cannot make rmmod for iwl... drivers if I use ipw3945, and
from another side, if I do not use ipw3945, my using iwl... is still not
stable.
I have Toshiba, Qosmio, G30-155.
Can you look no this problem, please?
I asked Akima Yagi already and he proposed me to make firstly:
for BUSID in $(/sbin/lspci | awk '{ IGNORECASE=1 } /net/ { print $1
for cmdsubst> }'); do /sbin/lspci -s $BUSID -m; /sbin/lspci -s $BUSID -n;
done
02:00.0 "Ethernet controller" "Intel Corporation" "82573L Gigabit Ethernet
Controller" "Toshiba America Info Systems" "Unknown device 0001"
02:00.0 0200: 8086:109a
05:00.0 "Network controller" "Intel Corporation" "PRO/Wireless 3945ABG
[Golan] Network Connection" -r02 "Intel Corporation" "Unknown device 1041"
05:00.0 0280: 8086:4222 (rev 02)
That information confirms that the e1000e and iwl3945 drivers should
be used with the
2.6.18-164.10.1.el5 kernel (quoting Alan).
This is how you find this out: go to the ELRepo FAQ page at
http://elrepo.org/tiki/FAQ .
FAQ Number 4 provides a detailed description on how to identify the
driver through the Vendor:Device ID pair. In your case, it is
8086:109a for the ethernet controller and 8086:4222 for the wireless
device.
The command:
grep -i 8086 /lib/modules/*/modules.alias | grep -i 109a
returns (among other things)
/lib/modules/2.6.18-164.10.1.el5/modules.alias:alias
pci:v8086d109Asv*sd*bc*sc*i* e1000e
Likewise, the other pair gives you iwl3945.
I realize you have [tried] both ipw3945 and iwl3945. Now that you are
running the current kernel, I think you should use iwl3945. Make sure
you have the correct firmware installed.
Akemi
To make sure you have the correct firmware
yum install iwlwifi-3945-ucode.noarch
rpm -qa | grep iwl | sort
Also, you should completely get rid of the ipw3945 stuff, or it will
keep creeping in and messing things up.
/etc/rc.d/init.d/ipw3945d stop
yum remove "*ipw3945*"
It would be a good idea to reboot after this.
Troy
--
__
Troy Dawson daw...@fnal.gov (630)840-6468
Fermilab ComputingDivision/LSCS/CSI/USS Group
__
Re: dbus and a broken pipe - solved
Jim, Thanks for the update. -connie On Thu, 14 Jan 2010, Jim Green wrote: Hi all I recently posted the following query on this list I'm running a freshly installed sl51 and on login get a very annoying message from the gnome-settings-manager about being unable to contact to socket: /tmp/dbus-kjsdfhjd : connection refused. : but had no replies -- I post a solution for the sake of the archive. Further research on Google revealed that this problem can be caused by an old bug in dbus, which introduced a race condition on pipes being closed at the time a process wanted to write to them. I tried to update dbus within SL51 but found a cascade of dependencies made this "too interesting" to follow through. A clean install of SL54 on the same hardware (and with the same corporate setup) fixes the problem for me. Cheers Jim
