Hello all of you, I have recently become a openSuse user. This does not come with its share of problems, though I’m not sure the SO is the real problem here.
I have purchased a brand new Samsung R580 JS03PT Laptop and I suspect there is an hardware issue here. this is my code for ifconfig at the moment.
lo
Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1540 (1.5 Kb) TX bytes:1540 (1.5 Kb)
I have been up and down trough lots of threads on some forums and the main difference I find on all ifconfig codes is the fact that I have no eth0 or wlan0. I have tried to bring it up but says that there is no such device. I’m clueless what to do.
Any ideas?
On 03/03/2010 08:16 AM, SpikePaws wrote:
>
> Hello all of you, I have recently become a openSuse user. This does not
> come with its share of problems, though I’m not sure the SO is the real
> problem here.
> I have purchased a brand new Samsung R580 JS03PT Laptop and I suspect
> there is an hardware issue here. this is my code for ifconfig at the
> moment.
>
> Code:
> --------------------
> lo
> Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:26 errors:0 dropped:0 overruns:0 frame:0
> TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1540 (1.5 Kb) TX bytes:1540 (1.5 Kb)
> --------------------
>
>
> I have been up and down trough lots of threads on some forums and the
> main difference I find on all ifconfig codes is the fact that I have no
> eth0 or wlan0. I have tried to bring it up but says that there is no
> such device. I’m clueless what to do.
You need to post the PCI ID’s for your network devices. As neither wired nor
wireless devices show, you probably are unlucky enough to have picked a computer
with devices not supported by Linux. Please run the command
/sbin/lspci -nnk
and post the parts that mention “Ethernet” or “Wireless”
Thanks for the reply, here is the code.
Subsystem: Samsung Electronics Co Ltd Device [144d:c06a]
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8192] (rev 01)
Subsystem: Askey Computer Corp. Device [144f:7160]
07:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. Device [11ab:4381] (rev 11)
I was thinking the same thing, that I have no hardware support lets just hope this proves otherwise.
On 03/03/2010 06:46 PM, SpikePaws wrote:
>
> Thanks for the reply, here is the code.
>
> Code:
> --------------------
> Subsystem: Samsung Electronics Co Ltd Device [144d:c06a]
> 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8192] (rev 01)
> Subsystem: Askey Computer Corp. Device [144f:7160]
> 07:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. Device [11ab:4381] (rev 11)
> --------------------
>
>
> I was thinking the same thing, that I have no hardware support lets
> just hope this proves otherwise.
Your wired device uses the sky2 driver. It was added later than 2.6.31 was
released, which is why it is not in the openSUSE kernel on the distribution medium.
Your wireless device is handled by the rtl8192e driver, which was also entered
into the kernel after 2.6.31.
What you need to do is download
http://download.opensuse.org/factory/repo/oss/suse/x86_64/kernel-desktop-2.6.33-5.2.x86_64.rpm
for 64-bit systems or
http://download.opensuse.org/factory/repo/oss/suse/i586/kernel-desktop-2.6.33-3.3.i586.rpm
for 32-bit systems. You can do that download with any other system. Get that
file into Linux, and enter the command:
sudo rpm -iv kernel-desktop-2.6.33-5.2.XXXX.rpm
where XXXX matches the file you need. Once that completes, reboot. There will be
extra entries in the GRUB menu for 2.6.33. Select that kernel, and you should
have both eth0 and wlan0.
I downloaded the 32bit version and installed it. Unfortunately it locked up while booting. I downloaded the previous version and that one seems to be working just fine. Got wired and wireless access. Thanks for the help.
HELP!! I installed OS 11.2 on an old HP ze4900 laptop. Everything works fine EXCEPT for the wireless connection. I did lspci -nnk and this is the entry for the Broadcom wireless adapter:
02:06.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN [103c:12f8]
I’m running 2.6.31.12-0.2-default for the kernel. I tried installing the broadcom-wl firmware but it doesn’t work. The only network devices in the system are eth0 and l0, no wlan0. I’ve searched everywhere and tried all the direction I’ve found with zero success. Has anybody got any ideas? TIA
On 06/10/2010 10:06 PM, leporter37204 wrote:
>
> HELP!! I installed OS 11.2 on an old HP ze4900 laptop. Everything works
> fine EXCEPT for the wireless connection. I did lspci -nnk and this is
> the entry for the Broadcom wireless adapter:
>
> 02:06.0 Network controller [0280]: Broadcom Corporation BCM4306
> 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
> Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN
> [103c:12f8]
>
> I’m running 2.6.31.12-0.2-default for the kernel. I tried installing
> the broadcom-wl firmware but it doesn’t work. The only network devices
> in the system are eth0 and l0, no wlan0. I’ve searched everywhere and
> tried all the direction I’ve found with zero success. Has anybody got
> any ideas? TIA
Yes, the BCM4306 is NOT controlled by the Broadcom-wl driver. FYI,
drivers run on the host computer while firmware runs on the CPU embedded
in the wireless device.
You need to use the command
sudo /usr/sbin/install_bcm43xx_firmware
sudo /sbin/modprobe -rv b43
sudo /sbin/modprobe -v b43
Once the firmware is installed and the driver is unloaded and reloaded,
your device should be able to detect networks and be vonfigured.
Thanx a bunch! That worked. The only issue is the connection seems a little tenuous. When I reboot it goes away and I have to modprobe again to get it working. If that’s the way it is I can live with it. I was manager of unix tech support for a large company 20 years ago but a lot of stuff has changed since then. There weren’t very many laptops you could install V4 on and everything was command line. Linux rocks!
On 06/11/2010 09:06 AM, leporter37204 wrote:
>
> Thanx a bunch! That worked. The only issue is the connection seems a
> little tenuous. When I reboot it goes away and I have to modprobe again
> to get it working. If that’s the way it is I can live with it. I was
> manager of unix tech support for a large company 20 years ago but a lot
> of stuff has changed since then. There weren’t very many laptops you
> could install V4 on and everything was command line. Linux rocks!
I still use the command line for a lot of stuff, and my desktop of
choice is KDE because it preserves my terminal selection - all 9 tabs
with each set to a particular directory. I never did much with AT&T
Unix, but I did a lot of work with IBM’s AIX, DEC’s Unix-like OS for
Alpha, and Cray’s Unicos.
As to the problems with restart - Are you using NetworkManager or ifup?
If the former, make certain that the “Connect Automatically” button is
checked in the wireless connection. If you are using ifup, set the wired
connection to start on cable connection, and the wireless to start on
boot. No modprobe commands should be needed. I gave you those in the
previous post just to get the driver to notice that the firmware was now
available.
I reconfigured but haven’t had a chance to reboot yet to see if everything works. I read in another post, quote: “I saw a post talking about /etc/udev/rules.d/70-persistant.net.rules and changed the line for wlan0 from DRIVERS==”?*" TO DRIVERS==“b43”." If this doesn’t work would that help?
I had some experience with AIX in my job as unix tech support manager. I was impressed with their SMIT tool and the AIX file system. Out of the box it was much faster than the V4 file system. BTW, saw you’re from the KC area. I was raised in Columbia. Lived in Nashville for a little over 20 years now. Keep up the good work. I’m sure I’m not the only one that appreciates your help.
On 06/11/2010 07:16 PM, leporter37204 wrote:
>
> I reconfigured but haven’t had a chance to reboot yet to see if
> everything works. I read in another post, quote: “I saw a post talking
> about /etc/udev/rules.d/70-persistant.net.rules and changed the line for
> wlan0 from DRIVERS==”?*" TO DRIVERS==“b43”." If this doesn’t work would
> that help?
No, that should not matter. Usually, those lines are specific to the MAC
address.
> I had some experience with AIX in my job as unix tech support manager.
> I was impressed with their SMIT tool and the AIX file system. Out of the
> box it was much faster than the V4 file system. BTW, saw you’re from the
> KC area. I was raised in Columbia. Lived in Nashville for a little over
> 20 years now. Keep up the good work. I’m sure I’m not the only one that
> appreciates your help.
Thanks for the kind words.