<![CDATA[Linux-Noob Forums - SUSE]]> https://www.linux-noob.com/forums/ Fri, 01 May 2026 04:29:30 +0000 MyBB <![CDATA[Need quick help Please !]]> https://www.linux-noob.com/forums/thread-459.html Fri, 21 May 2010 21:08:22 +0200 mamado diyara]]> https://www.linux-noob.com/forums/thread-459.html Hello there,

 

I have a Dell Latitude D610 with 1.60GHz, and it was showing a Centerino Mobilty Technology when starting windows XP,

but when I flash the Bios suddenly the Bios changed to intel M.

Actually I tried to install the Bios driver A06 from Dell website but it gave me the same result.

Please if somebody can help me to reback the same driver for my laptop, I mean the Centrino reading in starting Windows so I will be happy.

Thank you so much in advanced

 

mamado diyara

]]> Hello there,

 

I have a Dell Latitude D610 with 1.60GHz, and it was showing a Centerino Mobilty Technology when starting windows XP,

but when I flash the Bios suddenly the Bios changed to intel M.

Actually I tried to install the Bios driver A06 from Dell website but it gave me the same result.

Please if somebody can help me to reback the same driver for my laptop, I mean the Centrino reading in starting Windows so I will be happy.

Thank you so much in advanced

 

mamado diyara

]]> <![CDATA[ow to use a USB stick to install SLES 10 - "No catalog found..."]]> https://www.linux-noob.com/forums/thread-585.html Sat, 22 Aug 2009 15:54:07 +0200 FlatBallFlyer]]> https://www.linux-noob.com/forums/thread-585.html I'm trying to install SLES 10 from a 4Gb USB Stick. I have followed the instructions from Novell to create the bootable USB. I also used information from an openSUSE forum post. Here is the procedure that I have followed to date, it's a hybrid of the above mentioned notes:

 

1. Mount the dvd iso image to drive I: using "Virtual CloneDrive"

2. Copy the entire ISO image I: to the USB stick J:

3. Move all files from J:/boot/i386/loader to J:/

4. Delete J:/isolinux.bin

5. Rename J:/isolinux.cfg to J:/syslinux.cfg

6. Run C:/syslinux/win32/syslinux -ma J:

7. From the J: root, I execute ls -A1 > directory.yast

 

I can now boot my server from this USB stick. When prompted for a boot option, I enter "linux" to start the install. When the install starts it asks "Make sure that CD number 1 is in your drive." I select "Back" and accept defaults until the source medium comes up. There I select "Hard Disk" and then choose "sdb1 : vfat", and leave the "source directory" blank. The installation then loads and runs just fine until I get to the Installation summary screen. Under the Software heading, YaST is reporting the following error:

 

No catalog found at 'hd:///?device=/dev/sdb1&filesystem=auto'.

 

As always, the geek gods will reign favor upon all who answer!

 

Thanks

Mike

]]> I'm trying to install SLES 10 from a 4Gb USB Stick. I have followed the instructions from Novell to create the bootable USB. I also used information from an openSUSE forum post. Here is the procedure that I have followed to date, it's a hybrid of the above mentioned notes:

 

1. Mount the dvd iso image to drive I: using "Virtual CloneDrive"

2. Copy the entire ISO image I: to the USB stick J:

3. Move all files from J:/boot/i386/loader to J:/

4. Delete J:/isolinux.bin

5. Rename J:/isolinux.cfg to J:/syslinux.cfg

6. Run C:/syslinux/win32/syslinux -ma J:

7. From the J: root, I execute ls -A1 > directory.yast

 

I can now boot my server from this USB stick. When prompted for a boot option, I enter "linux" to start the install. When the install starts it asks "Make sure that CD number 1 is in your drive." I select "Back" and accept defaults until the source medium comes up. There I select "Hard Disk" and then choose "sdb1 : vfat", and leave the "source directory" blank. The installation then loads and runs just fine until I get to the Installation summary screen. Under the Software heading, YaST is reporting the following error:

 

No catalog found at 'hd:///?device=/dev/sdb1&filesystem=auto'.

 

As always, the geek gods will reign favor upon all who answer!

 

Thanks

Mike

]]> <![CDATA[HowTo: Transfer old software RAID1 to new disks]]> https://www.linux-noob.com/forums/thread-804.html Mon, 13 Oct 2008 07:22:35 +0200 stefan]]> https://www.linux-noob.com/forums/thread-804.html Hi,

my goal is to substitute two mirrored IDE disks, 160GB each, for 2x 500GB SATA drives - keeping the /dev/md0 layout for rootfs (Suse 10.1) and the Data partition /dev/md1 will just have more space.

 

I'm failing in making the new drives bootable.

(see below, end of the post:

mdadm: no devices found for /dev/md0.)

 

Here's what I did:

 

 

Connect the new disks additionally (sda und sdb)

 

## 1st is to backup the drive partition tables:

 



Code:
mkdir /raidinfo
sfdisk -d /dev/hda > /raidinfo/partitions.hda
sfdisk -d /dev/hdb > /raidinfo/partitions.hdb

# fdisk -l /dev/hda

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1         131     1052226   82  Linux swap / Solaris
/dev/hda2   *         132        4048    31463302+  fd  Linux raid autodetect
/dev/hda3            4049       19456   123764760   fd  Linux raid autodetect

#(hdb is identical to hda)




 

## With "fdisk":

- create sda1 and sdb1 (swap)

- create sda2 and sdb2 (for / type: fd)

- create sda3 and sdb3 (/fileshares type: fd)

- set active partitions sda2 und sdb2.

 



Code:
## fdisk -l /dev/sda
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         131     1052226   82  Linux swap / Solaris
/dev/sda2   *         132        4048    31463302+  fd  Linux raid autodetect
/dev/sda3            4049       60801   455868472+  fd  Linux raid autodetect

#(sdb is identical to sda)




 

## Create both new RAID:



Code:
mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2
mdadm --create /dev/md3 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3

watch cat /proc/mdstat  ## Just to check progress.

mkfs.reiserfs /dev/md2  ## Format can be started
mkfs.reiserfs /dev/md3  ##  during creation of array.

mkdir /mnt/md2
mkdir /mnt/md3




 

mcedit /etc/fstab (add md2 + md3 lines)



Code:
/dev/md0    /           reiserfs   acl,user_xattr  1 1
  /dev/md1    /fileshares reiserfs   acl,user_xattr  1 1
  /dev/md2    /mnt/md2    reiserfs   acl,user_xattr  1 1
  /dev/md3    /mnt/md3    reiserfs   acl,user_xattr  1 1
  /dev/hda1   swap        swap       defaults        0 0
  /dev/hdb1   swap        swap       defaults        0 0




 

## Mount new Arrays:



Code:
mount /dev/md2  /mnt/md2   -o acl  -o user_xattr
mount /dev/md3  /mnt/md3   -o acl  -o user_xattr




 

## rsync copies also ACLs:



Code:
rsync -v --recursive --times --perms --links --exclude "/mnt/" --exclude \
"/proc/"  --exclude "/fileshares/" --exclude "/sys/" -a  /*  /mnt/md2/

cd /mnt/md2/ %% mkdir mnt %% mkdir proc %% mkdir fileshares %% mkdir sys




 

# Copy Data partition:



Code:
rsync -v --recursive --times --perms --links  -a /fileshares/* /mnt/md3/




 

## Set new UUIDs in new mdadm.conf:



Code:
mdadm --detail --scan >> /mnt/md2/etc/mdadm.conf




 

## Install GRUB onto both new disks:



Code:
chroot /mnt/md2
grub
device (hd0) /dev/sda
root (hd0,1)           ## 0,0 = swap, 0,1 = / incl /boot
setup (hd0)
device (hd1) /dev/sdb
root (hd1,1)           ## 1,0 = swap, 1,1 = / incl /boot
setup (hd1)
quit




 

mcedit /mnt/md2/etc/fstab



Code:
/dev/md0    /           reiserfs   acl,user_xattr  1 1
  /dev/md1    /fileshares reiserfs   acl,user_xattr  1 1  
  /dev/sda1   swap        swap       defaults        0 0
  /dev/sdb1   swap        swap       defaults        0 0




 

mcedit /mnt/md2/boot/grub/device.map



Code:
(hd0)   /dev/sda
(hd1)   /dev/sdb




 

mcedit /mnt/md2/boot/grub/menu.lst



Code:
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux 10.1
root (hd0,1)
kernel /boot/vmlinuz root=/dev/md0 vga=0x31a    resume=/dev/sda1  splash=silent showopts
initrd /boot/initrd




 

 

poweroff

 

Remove hda and hdb.

 

Boot from new hard disks:



Code:
...
Loading raid1
md: personality registered for level 1
Loading reiserfs
md: md0 stopped.
mdadm: no devices found for /dev/md0.
resume /dev/sda1 not founf (ignoring)
md: md0 stopped.
mdadm: no devices found for /dev/md0.
md: md1 stopped.
mdadm: no devices found for /dev/md1.
Waiting for device /dev/md0 to appear: ok.
rootfs: major=9 minor=0 devn=2304
/dev/md0: unknown volume type
invalid root filesystem -- exiting to /bin/sh
$_




 

Any suggestions will be appreciated!

 

One thing that might be the problem is that I swapped the SATA cables from sda and sdb by mistake:



Code:
# mdadm --detail /dev/md2
/dev/md2:
    Version : 00.90.03
Creation Time : Sat Oct  4 02:38:41 2008
Raid Level : raid1
Array Size : 31463232 (30.01 GiB 32.22 GB)
Device Size : 31463232 (30.01 GiB 32.22 GB)
  Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent

Update Time : Sun Oct 12 21:24:25 2008
      State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

       UUID : ba1944d9:4539b5bb:0fa8b8d3:3798154c
     Events : 0.1722

Number   Major   Minor   RaidDevice State
   0       8       18        0      active sync   /dev/sdb2
   1       8        2        1      active sync   /dev/sda2




 

If that's the whole problem, how can I fix it now that the users are already writing stuff on /dev/md3 (mounted on: /fileshares)?

]]> Hi,

my goal is to substitute two mirrored IDE disks, 160GB each, for 2x 500GB SATA drives - keeping the /dev/md0 layout for rootfs (Suse 10.1) and the Data partition /dev/md1 will just have more space.

 

I'm failing in making the new drives bootable.

(see below, end of the post:

mdadm: no devices found for /dev/md0.)

 

Here's what I did:

 

 

Connect the new disks additionally (sda und sdb)

 

## 1st is to backup the drive partition tables:

 



Code:
mkdir /raidinfo
sfdisk -d /dev/hda > /raidinfo/partitions.hda
sfdisk -d /dev/hdb > /raidinfo/partitions.hdb

# fdisk -l /dev/hda

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/hda1               1         131     1052226   82  Linux swap / Solaris
/dev/hda2   *         132        4048    31463302+  fd  Linux raid autodetect
/dev/hda3            4049       19456   123764760   fd  Linux raid autodetect

#(hdb is identical to hda)




 

## With "fdisk":

- create sda1 and sdb1 (swap)

- create sda2 and sdb2 (for / type: fd)

- create sda3 and sdb3 (/fileshares type: fd)

- set active partitions sda2 und sdb2.

 



Code:
## fdisk -l /dev/sda
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         131     1052226   82  Linux swap / Solaris
/dev/sda2   *         132        4048    31463302+  fd  Linux raid autodetect
/dev/sda3            4049       60801   455868472+  fd  Linux raid autodetect

#(sdb is identical to sda)




 

## Create both new RAID:



Code:
mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sda2 /dev/sdb2
mdadm --create /dev/md3 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3

watch cat /proc/mdstat  ## Just to check progress.

mkfs.reiserfs /dev/md2  ## Format can be started
mkfs.reiserfs /dev/md3  ##  during creation of array.

mkdir /mnt/md2
mkdir /mnt/md3




 

mcedit /etc/fstab (add md2 + md3 lines)



Code:
/dev/md0    /           reiserfs   acl,user_xattr  1 1
  /dev/md1    /fileshares reiserfs   acl,user_xattr  1 1
  /dev/md2    /mnt/md2    reiserfs   acl,user_xattr  1 1
  /dev/md3    /mnt/md3    reiserfs   acl,user_xattr  1 1
  /dev/hda1   swap        swap       defaults        0 0
  /dev/hdb1   swap        swap       defaults        0 0




 

## Mount new Arrays:



Code:
mount /dev/md2  /mnt/md2   -o acl  -o user_xattr
mount /dev/md3  /mnt/md3   -o acl  -o user_xattr




 

## rsync copies also ACLs:



Code:
rsync -v --recursive --times --perms --links --exclude "/mnt/" --exclude \
"/proc/"  --exclude "/fileshares/" --exclude "/sys/" -a  /*  /mnt/md2/

cd /mnt/md2/ %% mkdir mnt %% mkdir proc %% mkdir fileshares %% mkdir sys




 

# Copy Data partition:



Code:
rsync -v --recursive --times --perms --links  -a /fileshares/* /mnt/md3/




 

## Set new UUIDs in new mdadm.conf:



Code:
mdadm --detail --scan >> /mnt/md2/etc/mdadm.conf




 

## Install GRUB onto both new disks:



Code:
chroot /mnt/md2
grub
device (hd0) /dev/sda
root (hd0,1)           ## 0,0 = swap, 0,1 = / incl /boot
setup (hd0)
device (hd1) /dev/sdb
root (hd1,1)           ## 1,0 = swap, 1,1 = / incl /boot
setup (hd1)
quit




 

mcedit /mnt/md2/etc/fstab



Code:
/dev/md0    /           reiserfs   acl,user_xattr  1 1
  /dev/md1    /fileshares reiserfs   acl,user_xattr  1 1  
  /dev/sda1   swap        swap       defaults        0 0
  /dev/sdb1   swap        swap       defaults        0 0




 

mcedit /mnt/md2/boot/grub/device.map



Code:
(hd0)   /dev/sda
(hd1)   /dev/sdb




 

mcedit /mnt/md2/boot/grub/menu.lst



Code:
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux 10.1
root (hd0,1)
kernel /boot/vmlinuz root=/dev/md0 vga=0x31a    resume=/dev/sda1  splash=silent showopts
initrd /boot/initrd




 

 

poweroff

 

Remove hda and hdb.

 

Boot from new hard disks:



Code:
...
Loading raid1
md: personality registered for level 1
Loading reiserfs
md: md0 stopped.
mdadm: no devices found for /dev/md0.
resume /dev/sda1 not founf (ignoring)
md: md0 stopped.
mdadm: no devices found for /dev/md0.
md: md1 stopped.
mdadm: no devices found for /dev/md1.
Waiting for device /dev/md0 to appear: ok.
rootfs: major=9 minor=0 devn=2304
/dev/md0: unknown volume type
invalid root filesystem -- exiting to /bin/sh
$_




 

Any suggestions will be appreciated!

 

One thing that might be the problem is that I swapped the SATA cables from sda and sdb by mistake:



Code:
# mdadm --detail /dev/md2
/dev/md2:
    Version : 00.90.03
Creation Time : Sat Oct  4 02:38:41 2008
Raid Level : raid1
Array Size : 31463232 (30.01 GiB 32.22 GB)
Device Size : 31463232 (30.01 GiB 32.22 GB)
  Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent

Update Time : Sun Oct 12 21:24:25 2008
      State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

       UUID : ba1944d9:4539b5bb:0fa8b8d3:3798154c
     Events : 0.1722

Number   Major   Minor   RaidDevice State
   0       8       18        0      active sync   /dev/sdb2
   1       8        2        1      active sync   /dev/sda2




 

If that's the whole problem, how can I fix it now that the users are already writing stuff on /dev/md3 (mounted on: /fileshares)?

]]> <![CDATA[SATA in SuSE 11.0 64-bit]]> https://www.linux-noob.com/forums/thread-809.html Tue, 07 Oct 2008 08:04:49 +0200 kabifff]]> https://www.linux-noob.com/forums/thread-809.html I have an ASUS f8VA. When it came, all I wanted to do was install SuSE 11 on it. It took me hours of scouring forums and rebooting and re-burning what I thought were corrupt DVD images, when I learned that I needed to change the IDE setting in my BIOS to "compatibility mode" instead of "enhanced mode". The problem is that when I reboot into Windows, I first need to change the BIOS back into enhanced mode. The same goes for Linux: I need to change BACK to compatibility mode in the BIOS and reboot AGAIN to start Linux.

 

From what I can gather, this is because of problems with Linux and SATA. Google will give me nothing, except more definitions of the problem. Can anybody else help me?

]]> I have an ASUS f8VA. When it came, all I wanted to do was install SuSE 11 on it. It took me hours of scouring forums and rebooting and re-burning what I thought were corrupt DVD images, when I learned that I needed to change the IDE setting in my BIOS to "compatibility mode" instead of "enhanced mode". The problem is that when I reboot into Windows, I first need to change the BIOS back into enhanced mode. The same goes for Linux: I need to change BACK to compatibility mode in the BIOS and reboot AGAIN to start Linux.

 

From what I can gather, this is because of problems with Linux and SATA. Google will give me nothing, except more definitions of the problem. Can anybody else help me?

]]> <![CDATA[suse make question]]> https://www.linux-noob.com/forums/thread-852.html Thu, 28 Aug 2008 07:20:27 +0200 koby]]> https://www.linux-noob.com/forums/thread-852.html Am I doing something wrong?

 

i untarred ndiswrapper and went into that dir, is there a different command i should be using besides make?

 

I have opensuse, kde, in a bash shell

]]> Am I doing something wrong?

 

i untarred ndiswrapper and went into that dir, is there a different command i should be using besides make?

 

I have opensuse, kde, in a bash shell

]]> <![CDATA[Opensuse 10.3 on AMD Phenom 9500]]> https://www.linux-noob.com/forums/thread-1016.html Thu, 28 Feb 2008 05:08:01 +0100 Corkster]]> https://www.linux-noob.com/forums/thread-1016.html my latest<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/monthly_02_2008/post-903-1204171637.jpg" data-fileid="1047">[img]<fileStore.core_Attachment>/monthly_02_2008/post-903-1204171637.jpg[/img]</a>



.jpg   corkydesk.jpg (Size: 293.18 KB / Downloads: 0) ]]> my latest<a class="ipsAttachLink ipsAttachLink_image" href="<fileStore.core_Attachment>/monthly_02_2008/post-903-1204171637.jpg" data-fileid="1047">[img]<fileStore.core_Attachment>/monthly_02_2008/post-903-1204171637.jpg[/img]</a>



.jpg   corkydesk.jpg (Size: 293.18 KB / Downloads: 0) ]]> <![CDATA[Removing Openoffice 2.0]]> https://www.linux-noob.com/forums/thread-1027.html Tue, 12 Feb 2008 13:26:04 +0100 doncorleone]]> https://www.linux-noob.com/forums/thread-1027.html Hello,

I'm trying to to remove my Openoffice 2.0 that was came with my SuSE 10.0. I've installed the Openoffice 2.3 but do not know how to remove the old version so that I can use the new version as default.

Can you please give me tips on how to use Openoffice 2.3 as my default? I can easily remove the old version but I'm skeptical until I'm able to sort out the new version.

 

Thanks

]]> Hello,

I'm trying to to remove my Openoffice 2.0 that was came with my SuSE 10.0. I've installed the Openoffice 2.3 but do not know how to remove the old version so that I can use the new version as default.

Can you please give me tips on how to use Openoffice 2.3 as my default? I can easily remove the old version but I'm skeptical until I'm able to sort out the new version.

 

Thanks

]]> <![CDATA[External Storage in SuSE 10.3]]> https://www.linux-noob.com/forums/thread-1076.html Wed, 05 Dec 2007 21:16:57 +0100 kabifff]]> https://www.linux-noob.com/forums/thread-1076.html I'm having a problem with my external hard drive and SuSE 10.3 . It's a 320 gig hdd in an enclosure running to my USB so I can run it from one laptop to another without any major issues. It's formatted to NTFS and SuSE will read it just fine. It just won't write a dang thing to it.

 

The way I see it, there are a few possible solutions:

Solution 1: Format to FAT32. This would be very effective at solving my problem, but it would erase all my data and split my drive into a bunch of tiny little partitions. I don't want to format my drive because I don't want to lose anything.

 

Solution 2: Make SuSE Write to NTFS. I would love to make THIS solution work, however, since I know so little about how filesystems work, I don't want to screw anything up. Anybody have any ideas on how to make SuSE write to an NTFS disk?

 

Solution 3: Make a new, Linux-only partition on my drive. Again, this would probably work wonders and solve world peace, but it wouldn't let me run data to and from my computers which each have Windows AND Linux running.

 

Anybody have any suggestions?

]]> I'm having a problem with my external hard drive and SuSE 10.3 . It's a 320 gig hdd in an enclosure running to my USB so I can run it from one laptop to another without any major issues. It's formatted to NTFS and SuSE will read it just fine. It just won't write a dang thing to it.

 

The way I see it, there are a few possible solutions:

Solution 1: Format to FAT32. This would be very effective at solving my problem, but it would erase all my data and split my drive into a bunch of tiny little partitions. I don't want to format my drive because I don't want to lose anything.

 

Solution 2: Make SuSE Write to NTFS. I would love to make THIS solution work, however, since I know so little about how filesystems work, I don't want to screw anything up. Anybody have any ideas on how to make SuSE write to an NTFS disk?

 

Solution 3: Make a new, Linux-only partition on my drive. Again, this would probably work wonders and solve world peace, but it wouldn't let me run data to and from my computers which each have Windows AND Linux running.

 

Anybody have any suggestions?

]]> <![CDATA[Wireless and Compiz-Fusion working in SuSE 10.3!!!]]> https://www.linux-noob.com/forums/thread-1130.html Mon, 22 Oct 2007 03:26:11 +0200 kabifff]]> https://www.linux-noob.com/forums/thread-1130.html Wow, talk about a dry board, the last three threads were started by me and span 4 months!

Well, onwards!

I installed SuSE 10.3 the day it was released and I haven't looked back, but I was a little disappointed in the ease of setup for Compiz-Fusion and wireless using NDISWrapper.

 

To get Compiz-Fusion installed, I first downloaded the One-Click installer (links to KDE installer only, Gnome installer can be found here ) from OpenSuse.org and (obviously) ran it. Immediately, I hit my first snag, and it took me forever to realize that for whatever reason, it didn't download any of the XGL packages or the BComp package, so I downloaded those as well. I followed the directions put forth at OpenSuSE.org and there it was! My only gripe is that after a short while (about a half an hour) my system performance slows to about 20% of what it is usually, and I have to reboot.

 

As for wireless in NDISWrapper, I followed the directions graciously provided by Andrewd18, along with his GUI-frontend to NDISWrapper and all was well, for the most part. In both my linux boxes, I had to manually configure when my wireless turned on (I set it to manual) and which firewall zone it was in (it's set to "all traffic blocked" by default, I had to switch it to "external zone). It also required a full reboot, not just an X-Server restart.

 

I hope this helps you guys.

 

Kabifff

]]> Wow, talk about a dry board, the last three threads were started by me and span 4 months!

Well, onwards!

I installed SuSE 10.3 the day it was released and I haven't looked back, but I was a little disappointed in the ease of setup for Compiz-Fusion and wireless using NDISWrapper.

 

To get Compiz-Fusion installed, I first downloaded the One-Click installer (links to KDE installer only, Gnome installer can be found here ) from OpenSuse.org and (obviously) ran it. Immediately, I hit my first snag, and it took me forever to realize that for whatever reason, it didn't download any of the XGL packages or the BComp package, so I downloaded those as well. I followed the directions put forth at OpenSuSE.org and there it was! My only gripe is that after a short while (about a half an hour) my system performance slows to about 20% of what it is usually, and I have to reboot.

 

As for wireless in NDISWrapper, I followed the directions graciously provided by Andrewd18, along with his GUI-frontend to NDISWrapper and all was well, for the most part. In both my linux boxes, I had to manually configure when my wireless turned on (I set it to manual) and which firewall zone it was in (it's set to "all traffic blocked" by default, I had to switch it to "external zone). It also required a full reboot, not just an X-Server restart.

 

I hope this helps you guys.

 

Kabifff

]]> <![CDATA[SuSE 10.3!]]> https://www.linux-noob.com/forums/thread-1152.html Fri, 05 Oct 2007 17:50:52 +0200 kabifff]]> https://www.linux-noob.com/forums/thread-1152.html Has anybody had a chance to play with SuSE 10.3 yet? I'm stoked that it came out but I'm on a slower broadband connection so I've had to wait for it to download.

Also, is it possible to upgrade my other SuSE system with the online updater in the system settings panel? Or would I still need to use a CD/DVD? It has a broken cd drive, that's why I ask.

 

Click here to get SuSE 10.3!

]]> Has anybody had a chance to play with SuSE 10.3 yet? I'm stoked that it came out but I'm on a slower broadband connection so I've had to wait for it to download.

Also, is it possible to upgrade my other SuSE system with the online updater in the system settings panel? Or would I still need to use a CD/DVD? It has a broken cd drive, that's why I ask.

 

Click here to get SuSE 10.3!

]]> <![CDATA[SSL not installed?]]> https://www.linux-noob.com/forums/thread-1258.html Sun, 15 Jul 2007 10:50:32 +0200 hcyuan]]> https://www.linux-noob.com/forums/thread-1258.html Version: SLED 10 SP 1

 

I just recently downloaded Pidgin 2.0.2 and got that all installed correctly (at least I think it's installed correctly). However, when I try to add my MSN, GTalk, and Novell Messenger account, I get errors saying that it can't connect because SSL support was not installed. I went into YaST -> Software Management and did a search for SSL and a bunch of SSL modules are installed. Anybody know why I'm getting this error? Am I missing a SSL module or something?

 

Thanks in advance!!

 

Nuri

]]> Version: SLED 10 SP 1

 

I just recently downloaded Pidgin 2.0.2 and got that all installed correctly (at least I think it's installed correctly). However, when I try to add my MSN, GTalk, and Novell Messenger account, I get errors saying that it can't connect because SSL support was not installed. I went into YaST -> Software Management and did a search for SSL and a bunch of SSL modules are installed. Anybody know why I'm getting this error? Am I missing a SSL module or something?

 

Thanks in advance!!

 

Nuri

]]> <![CDATA[Heh... Windows screwed something up.... AGAIN]]> https://www.linux-noob.com/forums/thread-1283.html Fri, 29 Jun 2007 09:59:33 +0200 kabifff]]> https://www.linux-noob.com/forums/thread-1283.html ]]> ]]> <![CDATA[SUSE 10.0 XGL and Compiz problem]]> https://www.linux-noob.com/forums/thread-1375.html Thu, 24 May 2007 14:51:53 +0200 Armchang]]> https://www.linux-noob.com/forums/thread-1375.html hi,

 

i've already searched and tried to install some of the rpm's of xgl and compiz but there are too many dependencies not in the opensuse.org site, so i ended up with nothing there. I tried to use YOU but it won't find XGL and Compiz packages so I don't have luck there either. What could I do with this problem? I wanted to install XGL and Compiz packages to make my SLED 10.0 cool with it. Any help pls?

]]> hi,

 

i've already searched and tried to install some of the rpm's of xgl and compiz but there are too many dependencies not in the opensuse.org site, so i ended up with nothing there. I tried to use YOU but it won't find XGL and Compiz packages so I don't have luck there either. What could I do with this problem? I wanted to install XGL and Compiz packages to make my SLED 10.0 cool with it. Any help pls?

]]> <![CDATA[linux n00b (instalation]]> https://www.linux-noob.com/forums/thread-1505.html Fri, 23 Mar 2007 09:45:15 +0100 dametalone]]> https://www.linux-noob.com/forums/thread-1505.html i finally decided to try out linux and people told me to try out suse because its easier for newer users. However, since im new to it, i still want to keep my windows just in case so i wanted to do a dual boot system. I was told to make a partician so i made a 500 mg linux-swap partition and made a 30 gig ext3 partition for the linux. After i did that, i popped in the disk and started to rock n roll. Installation went pretty smoothly. However, it deleted the ext3 partition i made and replaced it with its own partitions. Well the dual boot went just fine, when it rooboted, it gave me the option to go with suse and windows. I choose to go with suse and it was up....except for a problem. It seems to freeze or lock up, in a weird way. After a few clicks of the mouse, its becomes unresponsive. I can move the mouse around but it seems the button doesnt work. I also noticed the clock on the bottom right stays in time which leads me to believe its not fully freezing and i type random stuff on the keyboard and brought up a search thing and i typed something random and it did search. I will also like to note that since im using wireless in my room, suse failed to connect to the internet and did not get any updates or anything.

 

Note: if need be, i can take my computer downstairs and connect it to a wired connection

 

um..help?

]]> i finally decided to try out linux and people told me to try out suse because its easier for newer users. However, since im new to it, i still want to keep my windows just in case so i wanted to do a dual boot system. I was told to make a partician so i made a 500 mg linux-swap partition and made a 30 gig ext3 partition for the linux. After i did that, i popped in the disk and started to rock n roll. Installation went pretty smoothly. However, it deleted the ext3 partition i made and replaced it with its own partitions. Well the dual boot went just fine, when it rooboted, it gave me the option to go with suse and windows. I choose to go with suse and it was up....except for a problem. It seems to freeze or lock up, in a weird way. After a few clicks of the mouse, its becomes unresponsive. I can move the mouse around but it seems the button doesnt work. I also noticed the clock on the bottom right stays in time which leads me to believe its not fully freezing and i type random stuff on the keyboard and brought up a search thing and i typed something random and it did search. I will also like to note that since im using wireless in my room, suse failed to connect to the internet and did not get any updates or anything.

 

Note: if need be, i can take my computer downstairs and connect it to a wired connection

 

um..help?

]]> <![CDATA[Wireless in SuSE 10.2: I have a solution!]]> https://www.linux-noob.com/forums/thread-1588.html Wed, 21 Feb 2007 02:07:52 +0100 kabifff]]> https://www.linux-noob.com/forums/thread-1588.html I noticed there were upwards of 800 views to my previous post about wireless in SuSE 10.2, and zero responses. I dug and dug and dug, and finally, at www.opensuse.org of all places, they had a fix for me. I will post it here as verbatim as I can, otherwise you can see it in full by clicking here. . Please note that this will only work with BROADCOM cards, not atheros or any other brand. Be warned.

Situation

 

Situation 1 - You have a Broadcom WLAN card based on BCM4306 chipset but the card is not active because of the missing Linux Driver (Version 9.3 - 10.0). See "ndiswrapper procedure".

 

Situation 2 - You have openSUSE 10.2 and you have a Broadcom bcm43xx series chipset listed in YaST > Network Devices > Network Card. Note: openSUSE 10.2 was distributed with the BCM46xx driver but not the firmware for legal reasons.

 

openSUSE 10.2 Option 1 - You can use the orginal drivers distributed with openSUSE 10.2, however, the bcm46xx drivers only support 11 Mb/s. Users who need/want the original drivers need to load the firmware for the chipset using bcm43xx-fwcutter. See "Original Driver Procedure"

 

openSUSE 10.2 Option 2 - You can maximize your wireless hardware to 54 Mb/s in most cases using the ndiswrapper, however to use this option you will need to remove the bcm46xx drivers and blacklist them from being reloaded again using the "bmc43xx Removal Procedure" then use the "ndiswrapper procedure".

[edit]

ndiswrapper Procedure

 

Note: In 10.2 you must first remove the original bcm43xx driver according to "openSUSE 10.2 Option 2 - bcm43xx Removal Procedure", prior to using ndiswrapper, see below for removal procedure

 

1. You need to check if ndiswrapper is installed through: Yast > Software > Software Installation and search for ndiswrapper. 2. Start the shell console (Kmenu >System > Terminal Program > Terminal) and login as root with the command:

 

sux -

 

and type in the root password. Afterwards create a directory with:

 

mkdir /lib/windrivers

 

You need to download the Windows driver for BCM4306 from the following link: [/url][url=http://www.silfreed.net/download/hpzt3000cto/SP23107A.tar.gz]http://www.silfreed.net/download/hpzt3000cto/SP23107A.tar.gz and place them under /lib/windrivers:

 

mv PATH_TO_DRIVER /lib/windrivers

 

From the console change to the directory with the drivers:

 

cd /lib/windrivers

 

Afterwards execute

 

tar -zxvf NAME_OF_DRIVER.tar.gz

 

for example tar -zxvf SP23107A.tar.gz then

 

cd NAME_OF_DRIVER

 

Check if threre are no other ndiswrapper modules loaded with:

 

ndiswrapper -l

 

if there are some, remove them with:

 

ndiswrapper -e NAME_OF_MODULE

 

After this install the Drivermodule with

 

ndiswrapper -i bcmwl5.inf

 

and load the module with

 

modprobe ndiswrapper

 

Reboot. Now you can configure your WLAN card through YAST > Network devices > Network card and configure a new wireless card and use the module name ndiswrapper. The other options here depend on the network system you want to use. (Fixed IP or DHCP, encryption etc.)

 

You can check if the card is active as from the console [Ctrl] + [Alt] + [F1] as "root" and type in

 

iwconfig

 

or

 

ifconfig

 

to see if the interface is recognized.

[edit]

openSUSE 10.2 Option 1 - Original Driver Procedure

 

1. You need to check if the bcm43xx-fwcutter package is installed through: Yast > Software > Software Installation and search for bcm43xx-fwcutter

 

2. Find the windows driver for your wireless chip. An example windows driver was titled bcmwl5.sys Also note if you can't find yours try doing a google search for wl_apsta.o (SUSE worked with both the orginal windows driver and the wl_apsta.o at the time of this WIKI post). Put the driver file on your desktop in SUSE.

 

3. Start the shell console (Kmenu >System > Terminal Program > Terminal) and login as root with the command:

 

sux -

 

and type in the root password

 

Extract your firmware files from your wireless chip and store them in the firmware file by typing in the following. (Note: Swap out the name of your driver accordingly...in this example it is wl_apsta.o):

 

bcm43xx-fwcutter -w /lib/firmware ~/Desktop/wl_apsta.o

 

Now that the firmware is extracted and ready for the driver to use, load the module by typing the following:

 

modprobe bcm43xx

 

6. Reboot and now you can configure your WLAN card through YAST > Network devices > Network card

[edit]

openSUSE 10.2 Option 2 - bcm43xx Removal Procedure

 

Only use the procedure below if you plan on removing openSUSE 10.2's original bcm43xx driver and installing the unsupported ndiswrapper driver.

 

1. Start the shell console (Kmenu >System > Terminal Program > Terminal) and login as root with the command:

 

sux -

 

and type in the root password

 

See if you have the bcm43xx drivers still installed:

 

lsmod | grep bcm43xx

 

Any response means it's installed, so remove it:

 

rmmod bcm43xx

 

Now blacklist it from being loaded again by adding the line "blacklist bcm43xx" to very bottom of the /etc/modprobe.d/blacklist file. To open the file with Kwrite type:

 

su -c 'kwrite /etc/modprobe.d/blacklist'

 

Also edit /etc/sysconfig/hardware/(your nic card) to change the module. Change 'bcm43xx' to 'ndiswrapper'

 

su -c 'kwrite /etc/sysconfig/hardware/hwcfg-bus-pci-xxx

 

2. Now follow the instructions in the "ndiswrapper procedure" above to setup your wireless card using ndiswrapper.

]]> I noticed there were upwards of 800 views to my previous post about wireless in SuSE 10.2, and zero responses. I dug and dug and dug, and finally, at www.opensuse.org of all places, they had a fix for me. I will post it here as verbatim as I can, otherwise you can see it in full by clicking here. . Please note that this will only work with BROADCOM cards, not atheros or any other brand. Be warned.

Situation

 

Situation 1 - You have a Broadcom WLAN card based on BCM4306 chipset but the card is not active because of the missing Linux Driver (Version 9.3 - 10.0). See "ndiswrapper procedure".

 

Situation 2 - You have openSUSE 10.2 and you have a Broadcom bcm43xx series chipset listed in YaST > Network Devices > Network Card. Note: openSUSE 10.2 was distributed with the BCM46xx driver but not the firmware for legal reasons.

 

openSUSE 10.2 Option 1 - You can use the orginal drivers distributed with openSUSE 10.2, however, the bcm46xx drivers only support 11 Mb/s. Users who need/want the original drivers need to load the firmware for the chipset using bcm43xx-fwcutter. See "Original Driver Procedure"

 

openSUSE 10.2 Option 2 - You can maximize your wireless hardware to 54 Mb/s in most cases using the ndiswrapper, however to use this option you will need to remove the bcm46xx drivers and blacklist them from being reloaded again using the "bmc43xx Removal Procedure" then use the "ndiswrapper procedure".

[edit]

ndiswrapper Procedure

 

Note: In 10.2 you must first remove the original bcm43xx driver according to "openSUSE 10.2 Option 2 - bcm43xx Removal Procedure", prior to using ndiswrapper, see below for removal procedure

 

1. You need to check if ndiswrapper is installed through: Yast > Software > Software Installation and search for ndiswrapper. 2. Start the shell console (Kmenu >System > Terminal Program > Terminal) and login as root with the command:

 

sux -

 

and type in the root password. Afterwards create a directory with:

 

mkdir /lib/windrivers

 

You need to download the Windows driver for BCM4306 from the following link: [/url][url=http://www.silfreed.net/download/hpzt3000cto/SP23107A.tar.gz]http://www.silfreed.net/download/hpzt3000cto/SP23107A.tar.gz and place them under /lib/windrivers:

 

mv PATH_TO_DRIVER /lib/windrivers

 

From the console change to the directory with the drivers:

 

cd /lib/windrivers

 

Afterwards execute

 

tar -zxvf NAME_OF_DRIVER.tar.gz

 

for example tar -zxvf SP23107A.tar.gz then

 

cd NAME_OF_DRIVER

 

Check if threre are no other ndiswrapper modules loaded with:

 

ndiswrapper -l

 

if there are some, remove them with:

 

ndiswrapper -e NAME_OF_MODULE

 

After this install the Drivermodule with

 

ndiswrapper -i bcmwl5.inf

 

and load the module with

 

modprobe ndiswrapper

 

Reboot. Now you can configure your WLAN card through YAST > Network devices > Network card and configure a new wireless card and use the module name ndiswrapper. The other options here depend on the network system you want to use. (Fixed IP or DHCP, encryption etc.)

 

You can check if the card is active as from the console [Ctrl] + [Alt] + [F1] as "root" and type in

 

iwconfig

 

or

 

ifconfig

 

to see if the interface is recognized.

[edit]

openSUSE 10.2 Option 1 - Original Driver Procedure

 

1. You need to check if the bcm43xx-fwcutter package is installed through: Yast > Software > Software Installation and search for bcm43xx-fwcutter

 

2. Find the windows driver for your wireless chip. An example windows driver was titled bcmwl5.sys Also note if you can't find yours try doing a google search for wl_apsta.o (SUSE worked with both the orginal windows driver and the wl_apsta.o at the time of this WIKI post). Put the driver file on your desktop in SUSE.

 

3. Start the shell console (Kmenu >System > Terminal Program > Terminal) and login as root with the command:

 

sux -

 

and type in the root password

 

Extract your firmware files from your wireless chip and store them in the firmware file by typing in the following. (Note: Swap out the name of your driver accordingly...in this example it is wl_apsta.o):

 

bcm43xx-fwcutter -w /lib/firmware ~/Desktop/wl_apsta.o

 

Now that the firmware is extracted and ready for the driver to use, load the module by typing the following:

 

modprobe bcm43xx

 

6. Reboot and now you can configure your WLAN card through YAST > Network devices > Network card

[edit]

openSUSE 10.2 Option 2 - bcm43xx Removal Procedure

 

Only use the procedure below if you plan on removing openSUSE 10.2's original bcm43xx driver and installing the unsupported ndiswrapper driver.

 

1. Start the shell console (Kmenu >System > Terminal Program > Terminal) and login as root with the command:

 

sux -

 

and type in the root password

 

See if you have the bcm43xx drivers still installed:

 

lsmod | grep bcm43xx

 

Any response means it's installed, so remove it:

 

rmmod bcm43xx

 

Now blacklist it from being loaded again by adding the line "blacklist bcm43xx" to very bottom of the /etc/modprobe.d/blacklist file. To open the file with Kwrite type:

 

su -c 'kwrite /etc/modprobe.d/blacklist'

 

Also edit /etc/sysconfig/hardware/(your nic card) to change the module. Change 'bcm43xx' to 'ndiswrapper'

 

su -c 'kwrite /etc/sysconfig/hardware/hwcfg-bus-pci-xxx

 

2. Now follow the instructions in the "ndiswrapper procedure" above to setup your wireless card using ndiswrapper.

]]>