Bought a license from shopNovell and started a clean install with a DVD
burnt form ISO file located at the Novell Website. Everything went fine.
It seems HP lacks support for SLED. Maybe Updates repositories are
locked because -serial-hp parameter is mandatory in suse_register.
Unfortunately HP doesn’t give SLED licenses anymore (it does some time
ago: ‘How to Register your HP Device (Notebook, Desktop, Workstation)
with SUSE Linux Enterprise Desktop (SLED)’
(http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7002791&sliceId=1&docTypeID=DT_TID_1_1&dialogID=269335979&stateId=0%200%20269339678)
). So they preload SLED, but is a useless version. Very disappointed.
Sorry for your disappointment. But I disagree with your comment on HP
lack of support. HP does provide 2 kinds of SLED license : 90 days trial
period and long term basic support (3 years). I depends on which model
you buy.
There are known issues with NCC. For instance, I tried personally to
register a MSI AP 1920 computer (with SLED 11 OEM). Even if I put the
right infiormation during the NCC registration (email address), I never
saw my product/system on the NCC portal.
There is a team at HP that works closely with SUSE. Bugs are sometimes
hard to replicate.
Regards,
Arnaud
ste615;2144971 Wrote:[color=blue]
Bought a license from shopNovell and started a clean install with a DVD
burnt form ISO file located at the Novell Website. Everything went fine.
It seems HP lacks support for SLED. Maybe Updates repositories are
locked because -serial-hp parameter is mandatory in suse_register.
Unfortunately HP doesn’t give SLED licenses anymore (it does some time
ago: ‘How to Register your HP Device (Notebook, Desktop, Workstation)
with SUSE Linux Enterprise Desktop (SLED)’
(http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7002791&sliceId=1&docTypeID=DT_TID_1_1&dialogID=269335979&stateId=0%200%20269339678)
). So they preload SLED, but is a useless version. Very disappointed.[/color]
If you had registered SLED before you needed to recover the installation
you can find the Activation Code at you Novell Customer Center page.
Then simply download SLED-11 SP1 image from Novell burn it to a disk and
install. After that try to activate it with the code, mentioned above.
Worked great for me.
P.S By the way I speak Russian, so feel free to PM me if you need.
P.P.S. Just a guess… It can be that you have SLED-11 with no service
pack. This SLED has reached it’s EOL (end of life). That’s why you’re
not able to see the repositories…
Yes, you need anyway to reinstall with SLED-11 SP1 image from Novell. I
know that works. My HP notebook is brand-new (less than one month) and
SLED SP1 was factory preloaded.
AlexDudko;2145174 Wrote:[color=blue]
If you had registered SLED before you needed to recover the installation
you can find the Activation Code at you Novell Customer Center page.
Then simply download SLED-11 SP1 image from Novell burn it to a disk and
install. After that try to activate it with the code, mentioned above.
Worked great for me.
P.S By the way I speak Russian, so feel free to PM me if you need.
P.P.S. Just a guess… It can be that you have SLED-11 with no service
pack. This SLED has reached it’s EOL (end of life). That’s why you’re
not able to see the repositories…[/color]
I didn’t notice any reference to the 90-days trial period and long term
basic support on the HP website. I ended up buying a new license from
Novell and doing a clean install with the DVD image, always from
Novell.
Arnaudk93;2145026 Wrote:[color=blue]
Hi !
Sorry for your disappointment. But I disagree with your comment on HP
lack of support. HP does provide 2 kinds of SLED license : 90 days trial
period and long term basic support (3 years). I depends on which model
you buy.
There are known issues with NCC. For instance, I tried personally to
register a MSI AP 1920 computer (with SLED 11 OEM). Even if I put the
right infiormation during the NCC registration (email address), I never
saw my product/system on the NCC portal.
There is a team at HP that works closely with SUSE. Bugs are sometimes
hard to replicate.