New user : Install on Dell Inspiron 1525 , Ethernet issues

Help
1

Hi All, Let me start by saying that I have very little familiarity with Haiku or getting any other OS working, but I’m only looking for pointers and I will fafo for myself.

I decided to dig out an old laptop and put Haiku on it just to see, the laptop was running vista and I verified it was Ok before install. There was a minor glitch in install in that I had to disable one line in safe mode (user files 2nd one down) to get it to ‘try’ otherwise it hung on the 3rd icon (a device) (where do I find out what those Icons mean?) . I decided to do the install and after finding the install exe I did and it was happy doing a full install and it booted fine.

In trying it out I realised that the ethernet port existed but the wifi port did not, I parked the wifi and looked at the ethernet port, it was initially leading me down a DNS rabbit hole but I realised using ping that the issue was simply that the ethernet port hardware wasn’t set up and although I could give it a static address I couldn’t ping it and it never came out of ‘configuring’ using DCHP, searching on here for : Marvel_yukon 88E8040 yielded a couple of topics but raised more questions, Where is the outstanding bug list for hardware? How do I find similar topics ? Where is a list of Terminal commands and their format? How would you go about faultfinding this kind of problem? Is it possible to put a shortcut to terminal on the desktop? How do you stop a command running in terminal?

Any pointers welcome, and thanks.

Aviator.

2

Ahoy @aviator

As it happens in the Haiku bootloader - during the boot process - you must find the bootloader description on Haiku site or in User guide.
It is so called ‘Splash Screen’ that communicate boot status with icons instead of streaming log lines - as a power user I would be happier if it would do both, but to select log lines you must initiate to get into
Haiku boot menu hitting Space, just as boot would launch, this is like F8 in case windows, you must really quick to catch the right moment.
However as you wrote, you disabled some stuff you were there already-

Anyway, at the end of the document about bootloader, you can find you are curious about

There is a Haiku site with 2 Haiku services

Mainly knows for

  1. Haiku ticketing system TRAC

to use that you must register there.
However there is

  1. Haiku Wiki system as well, on the First tab titled ‘WIKI’

one line below select ‘Index’ – roll down until
Hardwareinfo → From FreeBSD 14.1

you can be happy, your hardware supported, by ported FreeBSD driver - it is in the list
marvell_yukon (msk, mii)

both Haiku Beta6 and Haiku Nightly should use it.

Anyway such informations are provided on Home page as well, from you had get download link -

There are links to many documentation as well -
Installation Guide, User Gude, etc … all provided to answer your questions above.

===================================

Such DNS issue can be solving by even with restart the router - as it happened for me in case ethernet.
I am on a new place , and router wifi part worked under Linux right away.
In Haiku my Broadcom Wifi is actually not supported, so I plugged in my ethernet under Haiku - there was Ip, but not any name resoution, it was under Linux too. If the cable was plugged the name resolution had not worked, if I plugged out, it worked on Wifi right away.
Finally I annoyed, and as I have no management access to the router , I rebooted.
It solved the think in my case - in Linux and Haiku finally there was name resolution besides the existing LAN IP for ethernet too.
So your issue must investigated - not only in the Haiku machine but on the LAN and the general internet access too.

3

Well if I would answer for your first question sarcastically I would answer , like
– here, in the Haiku forum
– and the Haiku ticketing system

you just have to gather them.

If you want to know to find a specific hardware and what can be know about it, or you want to check your actual machine, there is a site with a Haiku hardware database

This base on voluntarily shared data, so not complete, but you can find wide variety of hardware there.
Full configs as well,and PC parts - both desktop, laptop, and USB, etc variants - to find what you need.
For bugs .. you can find info on forum and in the ticketing system as well. There you can find also, solved or fixed the issue.

Well, to find similar topics - use the search function of the forum - the Magnify icon, upper left corner.

4

Well it is very easy to answer.

You have an icon on your desktop – User guide. Click on it. It will open in Webpositive from your machine, so if you do not have – working – network access it will work for you.

There is a section - at about first 3rd of sections or chapters
file:///boot/system/documentation/userguide//applications.html#cli-apps

was hu for me, replace with your language code to get this position – in your languege ( not mine as in the example below)

Command_line_appsprograms_general_and_Haiku_relatedones_HUN
Command_line_appsprograms_general_and_Haiku_relatedones_HUN1508×167 18.2 KB

It is the offline version of User Guide, that you can find also on the Haiku site as well - by default in English, but you can switch the language there as well, however some parts may not translated on your language. The English version is full , complete - surely in the online version.

=====================

well, I am out of possible 3 answers, so I started to edit my previous answers to give all the answers to your questions

=====================

How would you go about faultfinding this kind of problem?

I would open a ticket about it in TRAC, as you can get advices about commands and directions to investigate too

  1. register a user - I suggest the same as on the forum you made
  2. open a ticket about your issue
    The one and only field is must fill out well the title and description of the problem. Try to find the best category, but the devs will correct your selection in ticket details.
    The is also a document about ticket opening as well
==================================================

Of course, just as in other OS in right click menu on Terminal app within Application forlder you can do the stuff ,
Creating link,
and you will experience drop down list appear at the right end you can select Desktop as how you can create the link ..
Please let me find it yourself this handling UI in User Guide, if you need more understanding
than this description.

==================================================

Just as in other terminals ..

  1. if it still runs in foreground - with {CTRL} + {C} interrupt it.
  2. if it launched, and gave back the prompt ( the place where to write the commands is empty again) then identify the running cli command with ps command and kill it with its identifier using the kill command.
    there is jobs command, if you had launched something in the background - jobs also can be terminated with using jobs command to get jobs’ numbers,
    then kill %{jobnumber}
    ¤¤¤
    Graphically, there is Team Monitor or Process Monitor application - getting with
    {CTRL} + {ALT} + {DEL}.

01__TeamMonitor_ProcessMonitor_raw
01__TeamMonitor_ProcessMonitor_raw650×462 40.3 KB

As you can see, you can roll down - as I did - Terminal and you can kill Terminal sessions, If you need those, but those won’t terminate commands that went into background, from any of those sessions. My sessions are on different Terminal pages than instances. I have one Terminal window with more sessions generally.

I think I answered your all questions - UNTIL NOW.

:cowboy_hat_face:

5

Hello,

I had one of these Inspiron 1525 laptops a long time ago and already at the time the marvell_yukon driver was giving me problems.

To start troubleshooting:

  • First of all, confirm you see the device in Network preferences or in ifconfig
  • Check the syslog in /var/log/syslog, see if there are any errors from the driver (if you don’t know, you can share the whole syslog for us to look at, the bugtracker is a convenient place to share such files)
  • Checking the bugtracker: here is a request corresponding to that driver: Making sure you're not a bot! (you can easily switch to different components from the query page).

The driver we use currently for this device is from FreeBSD, so you could also try installing FreeBSD to see if it gets you the same results. That would mean the bug is in the driver itself, and not in the way it was ported to Haiku.