Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Marcel_Cox Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

The imaging driver code is always the same and always linux. server platform only influenses where the files for booting the workstation are stored, but the files themselves are the same. The documentation gives the various locations were the boot files are stored.
0 Likes
itddf Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

Does anyone think that Novell will resolve this problem by actually releasing a patch or will everyone be hung out to until the next driver set is released in a month or two? Thank god for all you users who are able to resolve these issues.

Marcel_Cox;1846287 wrote:
I discovered that Novell has included the Realtek r8168 driver in the August driver update. Unfortunately, Novell was sloppy and didn't update the configuration so that the bad r8169 is still being used.
The trick to force the use of the r8168 driver is to edit the file linuxrc.config in the initrd file system and add the following 2 lines:

ForceInsmod: 1
Insmod: r8168

The ZENWorks documentation tells you how to make modifications within initrd:
Novell Doc: Novell ZENworks 7 Desktop Management Administration Guide - Modifying ZENworks Imaging Resource Files
Novell Doc: ZENworks 10 Configuration Management Preboot Services and Imaging Reference - Modifying ZENworks Imaging Resource Files
0 Likes
shaunpond Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

Itddf,

Since this only affects one driver, I expect that it will be in the
September update

--

Shaun Pond


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

Excellent. This works for me.

Many thanks

Paul

Marcel Cox wrote:
> I discovered that Novell has included the Realtek r8168 driver in the
> August driver update. Unfortunately, Novell was sloppy and didn't update
> the configuration so that the bad r8169 is still being used.
> The trick to force the use of the r8168 driver is to edit the file
> linuxrc.config in the initrd file system and add the following 2 lines:
>
> ForceInsmod: 1
> Insmod: r8168
>
> The ZENWorks documentation tells you how to make modifications within
> initrd:
> http://www.novell.com/documentation/zenworks7/dm7admin/data/b2cdjzb.html
> http://www.novell.com/documentation/zcm10/zcm10_preboot_imaging/data/b2cdmbf.html
>
>

0 Likes
dmantz Frequent Contributor.
Frequent Contributor.

Re: imaging drivers for Realtek 8111/8169

Marcel,

I have added the two lines as instructed. Unfortunately, I continue to get the "repository can not be found" after taking a very long time for the Load Installation system. Any suggestions to a possible oversight on my part?

Thanks in advance,
Dean Mantz

Paul Gregory;1847733 wrote:
Excellent. This works for me.

Many thanks

Paul

Marcel Cox wrote:
> I discovered that Novell has included the Realtek r8168 driver in the
> August driver update. Unfortunately, Novell was sloppy and didn't update
> the configuration so that the bad r8169 is still being used.
> The trick to force the use of the r8168 driver is to edit the file
> linuxrc.config in the initrd file system and add the following 2 lines:
>
> ForceInsmod: 1
> Insmod: r8168
>
> The ZENWorks documentation tells you how to make modifications within
> initrd:
> Novell Doc: Novell ZENworks 7 Desktop Management Administration Guide - Modifying ZENworks Imaging Resource Files
> Novell Doc: ZENworks 10 Configuration Management Preboot Services and Imaging Reference - Modifying ZENworks Imaging Resource Files
>
>
0 Likes
adrockk Trusted Contributor.
Trusted Contributor.

Re: imaging drivers for Realtek 8111/8169

Dean,

Can you post back a the ouptut of a few commands? Boot into the maintenance
imaging environment (either from CD or PXE). When it fails, pick the
expertoption, select start shell and run:

lspci
lsmod
ifconfig eth0


--



dmantz spewed:

>
> Marcel,
>
> I have added the two lines as instructed. Unfortunately, I continue to
> get the "repository can not be found" after taking a very long time for
> the Load Installation system. Any suggestions to a possible oversight
> on my part?
>
> Thanks in advance,
> Dean Mantz
>
> Paul Gregory;1847733 Wrote:
> > Excellent. This works for me.
> >
> > Many thanks
> >
> > Paul
> >
> > Marcel Cox wrote:
> > > I discovered that Novell has included the Realtek r8168 driver in

> > the
> > > August driver update. Unfortunately, Novell was sloppy and didn't

> > update
> > > the configuration so that the bad r8169 is still being used.
> > > The trick to force the use of the r8168 driver is to edit the file
> > > linuxrc.config in the initrd file system and add the following 2

> > lines:
> > >
> > > ForceInsmod: 1
> > > Insmod: r8168
> > >
> > > The ZENWorks documentation tells you how to make modifications

> > within
> > > initrd:
> > > 'Novell Doc: Novell ZENworks 7 Desktop Management Administration

> > Guide - Modifying ZENworks Imaging Resource Files'
> > (http://www.novell.com/documentation/zenworks7/dm7admin/data/b2cdjzb.html)
> > > 'Novell Doc: ZENworks 10 Configuration Management Preboot Services

> > and Imaging Reference - Modifying ZENworks Imaging Resource Files'
> > (http://www.novell.com/documentation/zcm10/zcm10_preboot_imaging/data/b2cdmb
> > f.html)
> > >
> > >


0 Likes
dmantz Frequent Contributor.
Frequent Contributor.

Re: imaging drivers for Realtek 8111/8169

adrockk,

lspci = command not found

ifconfig eth0:
Link encap: Ethernet HW (mac address displayed)
inet addr: 10.3.100.59 Bcast: 10.3.255.255 Mask: 255.255.0.0
inet6 addr: (is displayed) Scope:Link
UP Broadcast running multicast MTU:1500 Metric:1
RX packets:5820 errors:0 dropped:0 overruns:0 frame:0
TX packets:4553 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 tzqueue len:1000
RX bytes:2622044 (2.5 Mb) TX bytes 213872 (208.8 Kb)
Interrupt:219 Base address 0x4000

lsmod:
Is too long to type out for you. Are there particular bits of information you need to see from it's display?



adrockk;1848684 wrote:
Dean,

Can you post back a the ouptut of a few commands? Boot into the maintenance
imaging environment (either from CD or PXE). When it fails, pick the
expertoption, select start shell and run:

lspci
lsmod
ifconfig eth0


--



dmantz spewed:

>
> Marcel,
>
> I have added the two lines as instructed. Unfortunately, I continue to
> get the "repository can not be found" after taking a very long time for
> the Load Installation system. Any suggestions to a possible oversight
> on my part?
>
> Thanks in advance,
> Dean Mantz
>
> Paul Gregory;1847733 Wrote:
> > Excellent. This works for me.
> >
> > Many thanks
> >
> > Paul
> >
> > Marcel Cox wrote:
> > > I discovered that Novell has included the Realtek r8168 driver in

> > the
> > > August driver update. Unfortunately, Novell was sloppy and didn't

> > update
> > > the configuration so that the bad r8169 is still being used.
> > > The trick to force the use of the r8168 driver is to edit the file
> > > linuxrc.config in the initrd file system and add the following 2

> > lines:
> > >
> > > ForceInsmod: 1
> > > Insmod: r8168
> > >
> > > The ZENWorks documentation tells you how to make modifications

> > within
> > > initrd:
> > > 'Novell Doc: Novell ZENworks 7 Desktop Management Administration

> > Guide - Modifying ZENworks Imaging Resource Files'
> > (Novell Doc: Novell ZENworks 7 Desktop Management Administration Guide - Modifying ZENworks Imaging Resource Files)
> > > 'Novell Doc: ZENworks 10 Configuration Management Preboot Services

> > and Imaging Reference - Modifying ZENworks Imaging Resource Files'
> > (http://www.novell.com/documentation/zcm10/zcm10_preboot_imaging/data/b2cdmb
> > f.html)
> > >
> > >
0 Likes
itddf Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

Hello dmantz,

I would really prefer if you contacted adrockk about the files. I have no problem providing them to you but it was adrockk who did all the hard work and provided me with the solution. I also see that Marcel Cox seems to have found a resolution that should work as well. Good luck.

itddf

dmantz;1845556 wrote:
itddf,

Would it be possible for me to get those same files from you that adrockk provided? I too am in the same boat as you prior to you having success with adrockk's files. My e-mail is mantzd at usd376 dot com or use a file sharing site and I can download from there.

Thanks in advance!
0 Likes
dmantz Frequent Contributor.
Frequent Contributor.

Re: imaging drivers for Realtek 8111/8169

itddf,

I fully understand and truly respect your point. I will contact adrockk if Marcel Cox's instructions don't work. Thanks for your assistance too.


itddf;1846397 wrote:
Hello dmantz,

I would really prefer if you contacted adrockk about the files. I have no problem providing them to you but it was adrockk who did all the hard work and provided me with the solution. I also see that Marcel Cox seems to have found a resolution that should work as well. Good luck.

itddf
0 Likes
dmantz Frequent Contributor.
Frequent Contributor.

Re: imaging drivers for Realtek 8111/8169

Thomas and Shaun,

I have added the line to my z_maint.cfg as you suggested but I am still getting a very slow "Load Installation System" (when not booting from CD) and the end result is the "Red" Could not find the ZENworks Repository. Activating manual setup program. I have even tried ethtool -s eth0 autoneg off speed 100 duplex full to hopefully increase performance to address the slowness of the installation system but no luck either.

I have also read the link provided by Shaun Pond from opensuse site but that did not make any difference either. The possible reason maybe that we are not dual booting the netbooks.

As for the bootcd.iso I can get netbook to talk with the ZENworks server but the image takes an extremely long time to upload an image. At the bash prompt when booting with the cd I can ping anywhere within our network or to several outside websites.

Thanks in advance for your assistance.

Dean Mantz





spond;1844172 wrote:
Paul,

is it this problem?
SDB:Realtek 8169 driver problem - openSUSE

--

Shaun Pond
0 Likes
janrik Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

We have the same issue here.

Loaded the August 2009 driver update and tried the iso that came with that, same problem.

RTL8111 b/c/d drivers do not work.

Sitting with 500 PC's that will now need to be ghosted in the interim 😞
0 Likes
shaunpond Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

Janrik,

September update should fix that, I'm expecting it soon, maybe today

--

Shaun Pond


0 Likes
janrik Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

Hi Shaun, Seems that the September update is still not working . 😞

Going to try the broken modules workaround.

Not real sure where to add it and the correct syntax for it?

My Z_maint.xmd looks like this at the moment

KERNEL boot/linux
APPEND initrd=boot/initrd vga=0x314 newid="0x8086 0x294c,e1000" newid="0x8086 0x10bd,e1000" install=tftp://$TFTPIP/boot rootimage=/root PROXYADDR=$PROXYADDR TFTPIP=$TFTPIP splash=silent PXEBOOT=YES mode=5

Do I just add brokenmodules=r8169 in there?
0 Likes
Highlighted
janrik Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

janrik;1868815 wrote:
Hi Shaun, Seems that the September update is still not working . 😞

Going to try the broken modules workaround.

Not real sure where to add it and the correct syntax for it?

My Z_maint.xmd looks like this at the moment

KERNEL boot/linux
APPEND initrd=boot/initrd vga=0x314 newid="0x8086 0x294c,e1000" newid="0x8086 0x10bd,e1000" install=tftp://$TFTPIP/boot rootimage=/root PROXYADDR=$PROXYADDR TFTPIP=$TFTPIP splash=silent PXEBOOT=YES mode=5

Do I just add brokenmodules=r8169 in there?


Update: Adding brokenmodules=r8169 worked!

Time to get busy.
0 Likes
shaunpond Absent Member.
Absent Member.

Re: imaging drivers for Realtek 8111/8169

Janrik,

thanks for the report!

--

Shaun Pond


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.