Opened 11 years ago
Closed 9 years ago
#10217 closed bug (no change required)
No Networkconnection with SiS900
| Reported by: | Morbid | Owned by: | siarzhuk |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Drivers/Network/sis900 | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | x86 |
Description
Device is an old Laptop from Gericom (Webgine)! Connecting wire to the Laptop and takes 3 Minutes to configure Network. After that Network shows green light. Web+ opens with an error message. Same Machine with WinXP works. Take a look at the Pictures.
Attachments (10)
Change History (27)
by , 11 years ago
| Attachment: | Gericom_listdev1.JPG added |
|---|
by , 11 years ago
| Attachment: | Gericom_Listdev2.JPG added |
|---|
by , 11 years ago
| Attachment: | Haiku_About.JPG added |
|---|
by , 11 years ago
| Attachment: | after3minutes.JPG added |
|---|
by , 11 years ago
| Attachment: | Network_settings1.JPG added |
|---|
by , 11 years ago
| Attachment: | Start_Webpositive.JPG added |
|---|
by , 11 years ago
| Attachment: | Windows_Settings.JPG added |
|---|
comment:1 by , 11 years ago
comment:2 by , 11 years ago
I'm trying to solve the Problem cause nothing works on that Machine! Shall i take a Picture too?
by , 11 years ago
| Attachment: | Syslog_Gericom_part1.rar added |
|---|
by , 11 years ago
| Attachment: | Syslog_Gericom_part2.rar added |
|---|
comment:4 by , 11 years ago
Don't USB sticks work on this machine? Text log files are really preferred.
by , 11 years ago
| Attachment: | syslog1.txt added |
|---|
comment:6 by , 11 years ago
| patch: | 0 → 1 |
|---|
comment:8 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
It seems the audio driver is misbehaving. Did you try with a static IP configuration?
Assigning to siarzhuk for the audio driver problem (which might be unrelated with this bug though). siarzhuk, could it be that installing the interrupt handler in the open hook is too late?
follow-up: 11 comment:9 by , 11 years ago
Replying to korli:
Assigning to siarzhuk for the audio driver problem (which might be unrelated with this bug though). siarzhuk, could it be that installing the interrupt handler in the open hook is too late?
IMO that looks like reason for another ticket.
There should be the way to blacklist sis7018 in latest Haiku builds - just to check if removing it fixes the problem with network.
There are set of sis900-related tickets are already in Track - may be replacing Axel's sis900 driver with FreeBSD ported one will solve all of them? ;-)
2 Morbid: What about sound on this laptop? Does it look functional?
comment:10 by , 11 years ago
Copied a MP3-File to the Haiku-Desktop and trying to open! Mediaplayer starts but no sound. The size of Syslog file climbs continuously without Mediaplayer! Floppy-Drive also doesn't work.
2 Korli: Yes i've tried static IP, too.
comment:11 by , 11 years ago
Replying to siarzhuk:
There are set of sis900-related tickets are already in Track - may be replacing Axel's sis900 driver with FreeBSD ported one will solve all of them? ;-)
I thought we had already done that years ago. While native drivers are a bit more efficient, I certainly don't think anyone would want to maintain that driver anymore to make sure it will support all the SiS 900 hardware out there. So let's just ditch my very first driver :-)
comment:12 by , 11 years ago
Using the FreeBSD sis driver should also give us proper dp83815 support (netgear fa-311/312) - also my first attempt at porting a driver :D
comment:13 by , 11 years ago
Blacklisted sis7018 under latest nightly hrev46642! Same as written above! Sorry for delay!
comment:14 by , 11 years ago
Shall i open a new Ticket about sis7018? Soundcard will be detected as Trident with ALSA under Puppy-Linux and works.
comment:15 by , 10 years ago
| patch: | 1 → 0 |
|---|
comment:17 by , 9 years ago
| Resolution: | → no change required |
|---|---|
| Status: | assigned → closed |
A copy of syslog from that machine would be pretty much required to start troubleshooting, the images really don't help in actually troubleshooting the problem other than showing that DHCP failed for some reason.